My Sharp Android TV (4T-C70BK2UD) has had an update available for a while. In the spot where it used to say "update now" it said something about new features, which leads me to think it upgraded in the background to Android 11.
The TV now constantly resets, sometimes a google/android error pops up "storage space low"
I'd LOVE to figure out how to launch into safe mode / recovery mode / bootloader and wipe it clean for a fresh restart otherwise it seems like my TV is bricked?
Already reached out to Sharp Customer Service, and waiting for a response--- anybody have any ideas? Thanks!
Related
My daughter has been using this phone, but never backed her photos up. Now it won't boot and she is worried they are lost forever. I've been trying to help, but only seem to make things worse.
1. She never enabled USB debugging, or rooted it
2. She could not tell me whether she had allowed the OTA upgrades.
3. It got into a reboot loop a few days ago. It would start to boot, then say it was optimising a random number of apps (anything between 90 and 158) and then start over. Wileyfox tech support told me that this was due to an incompatibility between Cyanogen and the latest Facebook Update.
4. They sent me a link to the FOTA files with instructions how to progressively upgrade to Android 7 (TOS111B)
5. They couldn't tell me how to determine whether it was running CM12 or CM13 (I now realise that I could have looked at the log files in the recovery partition)
6. I therefore assumed that it was running CM12. I used their instructions to go into recovery and manually update from SD card to ZNH0EAS2NH from there to ZNH2KAS7EB and then to TOS111B
7. Fatally I did not reboot between updates. At the end I had the Wileyfox splash screen black on white, and then got an animation with it red on white. It then got stuck.
8. I then tried using fastboot to go back to the original version of the OS so I could start over. I found the fastboot image and I flashed the boot and system partitions.
9. Now on boot it either gets stuck on the black on white boot screen, or it displays it for a second and then turns off.
Can anyone help me? - I think my daughter will have a nervous breakdown if I don't find a way of recovering her photos. Recovering the photos is more important than unbricking the phone.
jerrytaff said:
My daughter has been using this phone, but never backed her photos up. Now it won't boot and she is worried they are lost forever. I've been trying to help, but only seem to make things worse.
1. She never enabled USB debugging, or rooted it
2. She could not tell me whether she had allowed the OTA upgrades.
3. It got into a reboot loop a few days ago. It would start to boot, then say it was optimising a random number of apps (anything between 90 and 158) and then start over. Wileyfox tech support told me that this was due to an incompatibility between Cyanogen and the latest Facebook Update.
4. They sent me a link to the FOTA files with instructions how to progressively upgrade to Android 7 (TOS111B)
5. They couldn't tell me how to determine whether it was running CM12 or CM13 (I now realise that I could have looked at the log files in the recovery partition)
6. I therefore assumed that it was running CM12. I used their instructions to go into recovery and manually update from SD card to ZNH0EAS2NH from there to ZNH2KAS7EB and then to TOS111B
7. Fatally I did not reboot between updates. At the end I had the Wileyfox splash screen black on white, and then got an animation with it red on white. It then got stuck.
8. I then tried using fastboot to go back to the original version of the OS so I could start over. I found the fastboot image and I flashed the boot and system partitions.
9. Now on boot it either gets stuck on the black on white boot screen, or it displays it for a second and then turns off.
Can anyone help me? - I think my daughter will have a nervous breakdown if I don't find a way of recovering her photos. Recovering the photos is more important than unbricking the phone.
Click to expand...
Click to collapse
Since posting this I have had a partial success. A more complete set of fastboot flashing using the TOS111B fastboot images has got me to a phone that boots. Many of the apps work. However...
a) I get an "unfortunately the process com.android.phone has stopped" appearing almost as fast as I can close the app making it very difficult to get anything off the phone. However, I did manage to set up a google sync to upload the photos.
b) my daughter now tells me that her SMS's are vital.... and the messaging app says " getting message" then closes down
c) I cannot enable developer setting to enable usb debug mode. I can get into the phone status page under settings. Repeated tapping on the android version brings up the nougat splash screen, but the 7 taps (or 700 for that matter) on build number does nothing whatsoever.
Does anyone have any ideas how to recover to a fully working system without doing a factory reset?
I suspect that the sms database would have gone when the cache was cleared. Can anyone confirm that to be the case before I spend any more time trying to recover them?
Hi Jerry ,
Exactly the same problem here. Could you tell me where you've found the TOS111B fastboot images?
Thx!
Have you tried booting into safe mode?
I think you do that by pressing and holding the volume down down button during reboot.
If you can manage that you may be able to dissable the apps that are causing the crash.
Hello guys I hope you can help me. I have a car GPS (Unfortunately I am not allowed to publish links here but is a regular chinnese dash cam with GPS). It comes with a "board" cm84 dvp v2.1. It was working fine until one day I turned it off without knowing it was doing an Android upgrade on the back and after that it started looping while boot. So it shows the splash screen then it says that Android is upgrading - Upgrade 1 of 1 and then it just restart again. My guess is that part of the upgrades files were stored in cache and they now don't allow the GPS to boot. I know normally entering the Recovery boot via Down volume + power button I can clear cahe and even factory reset it, but the thing with this device is that it doesn't have any volume button, the only button it has is the power one so I have no idea how to access that option. Does anyone know how I can do that? Also, just in case, when I plug the device via USB to my Windows 10 laptop I see 2 units (D: and F on device manager but not on Windows Explorer.... in case there is no way to access the recovery boot because of not having a down volume button... is there any way I can just delete the cache folder content from Windows using any software? Thanks a lot in advance for any hand you can give me. I tried Coolmuster Android Eraser which detects an Unknown Android device but asks it to configure it to accept USB debugging which clearly I can't do.
Any solution?
Hello,
I am facing same issue with my device. Did you manage to find any solution to this problem.
SOLVED - Update below.
Hey guys,
I have an S9 (SM-G960F) which appears to have auto-updated during the night and as a result will now not boot. I am making an assumption it was an update of some sort as when I checked the time on it at 1am it was fine, when I woke around 8.30am the phone was off and when powering it on I ran into the issue. To summarise, I power the device on, get the Samsung loading screen, then the black swipe pattern screen to decrypt the phone, followed by the padlock unlocking loading screen, then the phone reboots. Sometimes however, the device gets past the padlock loading screen and says it is optimising apps, which is then followed by a reboot, briefly says it is installing system update before landing me at the Android Recovery screen.
What I've tried:
- Soft reset
- Booting in safe mode (same result as booting normally)
- Clearing cache partition
- Clearing app data
- Lacking storage booting (the device was quite low on storage last time I checked)
Some other (maybe) useful info:
I haven't updated the phone for months, could be why it did an auto update.
I'm on EE in the UK but IIRC the phone is not locked to EE.
Android Recovery has the following info when I load into it
Code:
samsung/starltexx/starlte
9/PPR1.180610.011/G960FXXU2CSB9
(options to try again, erase app data, power off, view rescue log)
#Reboot Recovery Cause is [system_server:12259 RecoverySystemRescueParty]#
Support SINGLE-SKU
Block-Based OTA
Supported API: 3
Viewing the rescue log presents me with a stacktrace , the top of which is
Code:
*** FATAL EXCEPTION IN SYSTEM PROCESS: main
java.lang.RuntimeException: Failed to create service com.android.server.job.JobSchedulerService: service constructor threw an exception
(followed by the rest of the stacktrace I can get a picture of if necessary)
My goal here is to recover the photos on the internal storage as they don't appear to be backed up to Google photos, nor Samsung's alternative - which is particularly painful cause I'm the one usually preaching backups.
Is there anyway to recover the OS to retrieve data, or pull the data off the device without wiping it? I'm open to any suggestions on how to do this, the main goal here is saving my photos, hence why I have avoided a factory reset from the Android Recovery menu.
Hope I've been clear enough, but let me know if I need to clarify anything. I would greatly appreciate any suggestions!
Thanks,
Matt
Hey guys,
After spending all day tearing my hair out with this I managed to fix it, so I guess this thread can be closed. For anyone who gets into a similar situation...
I attempted to solve this by flashing the current firmware using Odin and booting into "download mode", found a copy on sammobile.com. This didn't work, leaving me in the same situation, and as I felt I was running out of options I tried using the latest firmware for my device. I found a copy using a tool I found on these forums - Frija. Fired up Odin and download mode again, selected the AP/BL/CP/HOME_CSC (I understand using HOME_CSC is important so as not to cause a factory reset) and this worked! This left all of my files intact and as a bonus I'm also up-to-date with Android too. I'm backing up my photos as we speak as I would hate to be in this situation again!
Hope that can help someone in the future.
Cheers,
Matt
Which version of Odin did you use?
majormatt said:
Hey guys,
After spending all day tearing my hair out with this I managed to fix it, so I guess this thread can be closed. For anyone who gets into a similar situation...
I attempted to solve this by flashing the current firmware using Odin and booting into "download mode", found a copy on sammobile.com. This didn't work, leaving me in the same situation, and as I felt I was running out of options I tried using the latest firmware for my device. I found a copy using a tool I found on these forums - Frija. Fired up Odin and download mode again, selected the AP/BL/CP/HOME_CSC (I understand using HOME_CSC is important so as not to cause a factory reset) and this worked! This left all of my files intact and as a bonus I'm also up-to-date with Android too. I'm backing up my photos as we speak as I would hate to be in this situation again!
Hope that can help someone in the future.
Cheers,
Matt
Click to expand...
Click to collapse
I would really appreciate it if you post a YouTube tutorial on how to fix this. Because we are facing the same problem right now but I have no idea what solution you prescribed. Thank you and God bless.
Problems with a TCL P6046..
Suddenly the brightness went to "almost black". You can see the image but it is very dark.
The strange thing is that when restarting the TV, the brightness of the TCL brand and the loading of android are very bright.
Tried:
Empty the cache and restart
Disconnect the cable, press the button for 30 "and reconnect
Install the 820 OTA version from scratch, so "implicitly" reset to factory values
Unfortunately, apart from a phenomenal new boot speed (!), the new 820 fw hasn't changed that
The strange thing is that in the first few seconds of boot, until the complete loading of android, the brightness is normal.
But the system saw all settings rewritten with the ota 820 update ..
Kindly ASK
What can it depend on?
Any Ideas on what else to try?
G.
Hello,
An error appeared today while I was trying to update my Samsung Galaxy 20+ 5G (SM-G986B/DS) bought from my operator (La Poste Mobile) which is neither flashed nor rooted.
Small timeline of events:
- The last update installed was on May 24, 2021. Since then, all system updates of the phone have failed
- On October 25, 2022, since the last system update was almost a year and a half old, I searched for a way to try to perform the update. After some research, I came across this thread (https://eu.community.samsung.com/t5/gamme-galaxy-s20/mise-à-jour-impossible/td-p/5000954) which advised to update via Smart Switch
So I downloaded Smart Switch on my Windows PC and plugged my phone into USB-C to perform the update, after which I have a beautiful turquoise screen that says "An error has occurred while updating the device software. Use the Emergency Recovery function in the Smart Switch PC Software."
So I tried to use the Emergency Recovery feature of Smart Switch, but it is impossible to access the recovery mode of the phone (I keep coming back to the turquoise screen with a red "DEBORE : DN_FAIL_SECURE_CHECK_FAIL) and it remains stuck at 93% with "Secure check Fail: (Radio)" in red at the top of the screen when using either USB-C or 2.0 USB.
Is there anything I can do to fix my phone without losing my data? It must be possible to do a factory reset, but I don't want to lose my phone's data (data that I didn't save of course, it would be too easy otherwise)
Thanks in advance for your help/advice!
Hello,
did you find any solution for your problem? I have the same issue on my Galaxy S20 Ultra device.
Thanks in advance!