I had an error in judgement and installed the OTA on a rooted and xposed out phone. Now the phone keeps booting into recovery to try and install. It but the screen just flashes the installing update bug droid every few seconds. Battery pulling just gets me back to the same screen. Is there a way to abort the installation?
Have you tried clearing cache in recovering mode?
Sent from my SM-N910C using Tapatalk
Couldn't really get into recovery...it would auto boot into the the botched OTA update in recovery. I ended up flashing the firmware over Odin which did the trick.
Related
Ok do I did search first but can't find anyone with the same problem.
Started with stock 4.3 rooted, unlocked,TWRP.
Got the update notification, told it to update. It auto rebooted to TWRP and applied the update with no error. When it was done (assuming it was done progress bar finished) it went to the main TWRP menu. I told it to reboot and it just sits at the new 4.3 splash screen animation. I assumed it may take a bit so I let it sit for about 20min with no change. Rebooted it a couple times, also tried applying the update again via twrp (errors out as i woukd expect). Wiped dalvik and cache. Didn't do a factory wipe because I'd like to avoid that but still no change.
Any suggestions? Should I manually load the full 4.4 package via TWRP?
Thanks!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Same exact setup... Say exact issue... Oh and before rebooting I wiped Dalvik and Cache as "Sandard Operating Proceedure" ... I'm going to just do a clean flash at this point....
Tracy
Hi
I have the same problem. had a rooted 4.3, and after the update the screens remains on the splash thing. restarted a couple of times, did wipe data, factory reset, and it still remains stuck at the boot. What should i do. pls help
step944 said:
I have the same problem. had a rooted 4.3, and after the update the screens remains on the splash thing. restarted a couple of times, did wipe data, factory reset, and it still remains stuck at the boot. What should i do. pls help
Click to expand...
Click to collapse
Prior to the installation of the OTA it is safer to re-install stock recovery. Root is lost but re-installing a custom recovery and SuperSu bring back root.
gunner1937 said:
Prior to the installation of the OTA it is safer to re-install stock recovery. Root is lost but re-installing a custom recovery and SuperSu bring back root.
Click to expand...
Click to collapse
How can i install stock recovery?
You *could* unzip the factory image and then fastboot the recovery.img file. A lot easier is to download the wugfresh nexus root toolkit and use that:
http://www.wugfresh.com/
ty, but do u think it works, because i cant open my nexus 10 memory from the pc, since it is stuck at start up
Wug's toolkit has an option to restore to stock from a bricked system. All you need to be able to do is to get to the bootloader (press the power button while holding down both volume buttons -- you should get a dead android with a red triangle on chest).
SM-N9005 is soft bricked, owner probably went OTA and interrupted the update now when you turn on the phone it goes to the Samsung Galaxy Note 3 logo then loops from there. I tried to flash official stock firmware downloaded from Sammobile (N9005XXUEND6_N9005OLBEND1_XTC) and it passed the flash in ODIN 3.09 then the phone automatically reboots into stock recovery and tries to update package but from I keep getting:
E: Unable to verify whole file signature
E: Signature verification failed
Installation aborted
I have been flashing firmwares on older Samsung via ODIN and as far as I know after flashing via ODIN the firmware is already written in the phone and it doesn't need to reboot into recovery and flash the update again but in NOTE3 it does this and now I'm stuck.
I tried flashing PhilZ custom recovery and disabled signature verification but when I flash the stock firmware via ODIN it overwrites the custom recovery back to stock recovery and then gets stuck again in the verifying signature thing.
Any help and inputs would be greatly appreciated.
re: factory data reset
bcsiy said:
SM-N9005 is soft bricked, owner probably went OTA and interrupted the update now when you turn on the phone it goes to the Samsung Galaxy Note 3 logo then loops from there. I tried to flash official stock firmware downloaded from Sammobile (N9005XXUEND6_N9005OLBEND1_XTC) and it passed the flash in ODIN 3.09 then the phone automatically reboots into stock recovery and tries to update package but from I keep getting:
E: Unable to verify whole file signature
E: Signature verification failed
Installation aborted
I have been flashing firmwares on older Samsung via ODIN and as far as I know after flashing via ODIN the firmware is already written in the phone and it doesn't need to reboot into recovery and flash the update again but in NOTE3 it does this and now I'm stuck.
I tried flashing PhilZ custom recovery and disabled signature verification but when I flash the stock firmware via ODIN it overwrites the custom recovery back to stock recovery and then gets stuck again in the verifying signature thing.
Any help and inputs would be greatly appreciated.
Click to expand...
Click to collapse
If you can get into recovery why not try to do a
"Factory Reset", it may solve your problems.
Good luck!
Misterjunky said:
If you can get into recovery why not try to do a
"Factory Reset", it may solve your problems.
Good luck!
Click to expand...
Click to collapse
I tried to do a factory reset in stock recovery, tried wiping the Dalvik cache as well but the problem is still there it just stays on the Samsung Galaxy Note 3 screen then turns off then turns back on and loops over and over.
bcsiy said:
I tried to do a factory reset in stock recovery, tried wiping the Dalvik cache as well but the problem is still there it just stays on the Samsung Galaxy Note 3 screen then turns off then turns back on and loops over and over.
Click to expand...
Click to collapse
Either nuke the phone via a totally fresh ODIN update or flash Philz recovery, when it loops on you, take out the battery, put it back in then go to recovery mode, wipe the usual dalvik/cache etc then boot up (it should in theory work) (and/or flash a custom ROM just to get it to boot properly)
radicalisto said:
Either nuke the phone via a totally fresh ODIN update or flash Philz recovery, when it loops on you, take out the battery, put it back in then go to recovery mode, wipe the usual dalvik/cache etc then boot up (it should in theory work) (and/or flash a custom ROM just to get it to boot properly)
Click to expand...
Click to collapse
Thanks for the input, the main issue why I need to flash the stock rom is because the phone doesn't boot and is looping in the Samsung Galaxy Note 3 screen then vibrates as if it turns on again and goes into a loop...
Question is can I flash a custom rom over it for example there's no firnware loaded on the phone or the firmware loaded is corrupted?
You can flash a custom ROM yes, so long as you boot Into your custom recovery, do the wipes. Then installing a custom fw should work OK, once you've done that you can go back to stock or change custom fw without issues
I'm UBER Paranoid
bcsiy said:
SM-N9005 is soft bricked, owner probably went OTA and interrupted the update now when you turn on the phone it goes to the Samsung Galaxy Note 3 logo then loops from there. I tried to flash official stock firmware downloaded from Sammobile (N9005XXUEND6_N9005OLBEND1_XTC) and it passed the flash in ODIN 3.09 then the phone automatically reboots into stock recovery and tries to update package but from I keep getting:
E: Unable to verify whole file signature
E: Signature verification failed
Installation aborted
I have been flashing firmwares on older Samsung via ODIN and as far as I know after flashing via ODIN the firmware is already written in the phone and it doesn't need to reboot into recovery and flash the update again but in NOTE3 it does this and now I'm stuck.
I tried flashing PhilZ custom recovery and disabled signature verification but when I flash the stock firmware via ODIN it overwrites the custom recovery back to stock recovery and then gets stuck again in the verifying signature thing.
Any help and inputs would be greatly appreciated.
Click to expand...
Click to collapse
The reason it wants to boot into recovery is to flash the csc. Make sure you get the correct firmware for your device and region from sammobile.com and odin again, let it do its thing. It sounds like the csc wasn't valid.
Sent from my leanKernel 2.5 powered stock 4.4.2 SM-N900T
XT1575 - I unlocked my bootloader, rooted, then installed the OTA update - oops. I didn't realize I could only install OTAs with the official factory recovery. I am now stuck restarting into TWRP. If I restart from there, Android will start up for a minute say "Preparing to update", then restart back into TWRP.
How do I get out of this loop? Any way to roll back those updates that are half installed, or should I restore from my nandroid backup I took before I rooted the device? If I go back to pre-root, should I install OTA updates and THEN re-root, or just forget about the OTA updates?
I tried clearing my cache and dalvik cache from TWRP, and restarted, and android then booted. I did get a message saying "update failed".
Reflash the stock recovery, try to install the OTA, you might get and error message even so you should be able to get out of the loop
Enviado desde mi XT1575 mediante Tapatalk
The current update G930PVPU2APH7 from 9/14/16 is failing at 32% every time I try to update it. It does download fine, reboots into like stock recovery to update, gets to 32% and then fails. I read somewhere that maybe clearing cache in the stock recovery could help, haven't tried that yet, but will. Note that I was rooted, but went back to stock via odin flash method. Does previously being rooted matter? Any idea why? Or any ideas on what to do so I can update? Anyone else having any issues?
I think it has to do with me getting the E:failed to mount /data (Invalid argument)... Anyone confirm that?
EDIT: I know this isn't the issue, since my wifes phone updated just fine and she get the same error when shutting down or rebooting phone in recovery.
Sent from my SM-G930P using Tapatalk
Having the similar issues my phone did update the mic and the camera stopped working, did a hard wipe and now it will not boot past recovery. Ran the most current firmware through odin but will not take the firmware and fails out each time.
Hello,
I recently updated to the latest firmware for my Galaxy S10+ (G975U1UES3DTD5), and it's been stuck on "Finishing System Update..." for 3 days now. Restarting has had no luck on fixing it - it'll just start over and get stuck about halfway again. Any suggestions of what to try, before resorting to a phone reset?
Thanks!
Try wiping the cache from recovery. After that I'd try downloading the update and flash with odin
If that doesn't work try the wipe data from recovery
Was it an Ota update?