I tried to do an ota update and after the download and reboot it comes back with 'update is fail' at the install screen. System then reboots and says the install was interrupted. Would being rooted cause this? All I did was run doom's batch script. I have not changed the kernel or anything else. Should be completely stock still. I even tried to unroot using superoneclick. But it still failed after unrooting. Can anyone throw some suggestions out?
Sent from my SAMSUNG-SGH-I777 using xda premium
Check here - http://forum.xda-developers.com/showthread.php?t=1390715&highlight=failed+update
In short, no update it was for Skyrocket.
Related
Ok where do i start? Gonna try and be brief as possible. So today i was gonna update to ICS ota. I uninstalled safestrap first cause i was gonna reinstall the ics version using the Razr Utility ver. 1.7, as well as use to reroot. After i uninstalled the safestrap app i tried to install the ota i just took. Well it failed. I rebooted my phone and the Safestrap (SS) splash screen still popped up. I tried to reinstall the SS app using Razr Utility 1.6 (that i used to install in the first place) and it failed saying "failed to find path" or something similar. Weird caused it worked to install before. So now i cant get the SS app back to try and uninstall the actual recovery. Make sense? I was gonna try and load a Nandroid, but it was made back when i was still on .173. Can i go back to .173 and then reupdate to .181 and try again? Can anyone help me sort this out? I know its a lot to swallow Thanks in advance to anyone willing.
Edit: I am a moron. Trying to install Safestrap failed because I temp. unrooted with Voodoo before trying the update and forgot to allow root again. Thought I was past the noob stage.
Sent from my GT-P3113 using xda app-developers app
Sent from my ADR6425LVW using xda app-developers app
I have an s-off'd custom rom with AmonRa recovery... offered update??
I just want to have it ignore the update.
Apparently, the software doesn't know the
recovery system is not stock ... so it tries
and fails. I wonder if there is a way to extract
the new fingerprint to trick the update process
into thinking the updates already applied?
Or is there a way to just suppress it all together?
Well I'm pretty much chicken so I'm basically stock but rooted but the ota update keeps falling. I tried unrooting so the update could work but it still failed. Not sure why...
Sent from my ADR6425LVW using xda app-developers app
Same here
I am having the same issue, as well. Rooted, debloated stock sense. Recovery is Amon-Ra.
So I read another thread that made it seem like I needed to re-lock the bootloader so I did that and now when I try to update it goes into the bootloader menu instead of starting the update. Do I need to unroot or do another step for this to work?
Sent from my ADR6425LVW using xda app-developers app
Did you debloat at all? I was stock+root (no debloating) and the install went fine.
Sent from my ADR6425LVW using xda premium
Well, when the ota update downloads and you press the button to update, the updater immediately begins to check the system utilizing a checksum system for any modification, such as a deodexed system/app folder or binaries that weren't originally present. It wants to make sure all system/apps are still there and untouched and all the binaries are still kosher. If it detects something is "off" it will usually abort. If everything checks out it will boot to bootloader and attempt to install the update in the stock recovery. It will fail here of course if a custom recovery is installed.
You can kill your phone from even attempting to check for any otas by using Root Explorer or something similar, go to system/app and add bak to the end of each of these files:
HtcCOTAClient.apk
HtcCOTAClient.odex
You want them to look like:
HtcCOTAClient.apkbak
HtcCOTAClient.odexbak
You could also remove them.
I have an s-off'd custom rom with AmonRa recovery... offered update??
wildstang83 said:
Well, when the ota update downloads and you press the button to update,
the updater immediately begins to check the system utilizing a checksum system for any modification,
such as a deodexed system/app folder or binaries that weren't originally present. It wants to make sure
all system/apps are still there and untouched and all the binaries are still kosher. If it detects something
is "off" it will usually abort. If everything checks out it will boot to bootloader and attempt to install the
update in the stock recovery. It will fail here of course if a custom recovery is installed.
You can kill your phone from even attempting to check for any otas by using
Root Explorer or something similar, go to system/app and add bak to the en
d of each of these files:
HtcCOTAClient.apk
HtcCOTAClient.odex
You want them to look like:
HtcCOTAClient.apkbak
HtcCOTAClient.odexbak
You could also remove them.
Click to expand...
Click to collapse
I froze that with TiBu but it still shows up
as a pending update.
Experimenting, I tried freezing HtcDM
apk and service and the notices went away.
Is that safe to leave DM frozen, (what else does it do)?
My intent is to just prevent this a future OTA
updates auto-installing while I asleep. i woke
to find myself looking at a failed attempt
and hung in AmonRA, I rebooted to normal
and everything runs as normal.
fuzzynco said:
I froze that with TiBu but it still shows up
as a pending update.
Experimenting, I tried freezing HtcDM
apk and service and the notices went away.
Is that safe to leave DM frozen, (what else does it do)?
My intent is to just prevent this a future OTA
updates auto-installing while I asleep. i woke
to find myself looking at a failed attempt
and hung in AmonRA, I rebooted to normal
and everything runs as normal.
Click to expand...
Click to collapse
Not to be a PIA, but why freeze if you can just add bak to the end of the file name and you will achieve the same thing? If you ever want to go back you just delete the bak?
So for me it sounds like I need to get back to a stock recovery to be able to successfully perform the update?
Sent from my ADR6425LVW using xda app-developers app
Gee thanx for the help people...
Sent from my ADR6425LVW using xda app-developers app
You must be on the stock recovery to take an OTA. The stock recovery performs the update. So flash the stock recovery and then do the update or deal with no update.
Is there a way to flash the stock recovery without it wiping my phone?
Sent from my ADR6425LVW using xda app-developers app
Unless you're running a completely stock rom (with nothing removed), you won't be able to install the update anyway...
If you want to stop it from trying to come down, delete or rename /system/etc/security/otacerts.zip.
As for re-installing the stock recovery, you probably would need to RUU your phone unless it's s-off.
So if I do a back up, then go back to stock recovery which will wipe my phone, then perform the ota update, will a restore revert the ruu back and I'm back to square one, or does the ruu not roll back?
Sent from my ADR6425LVW using xda app-developers app
fivedezs said:
So if I do a back up, then go back to stock recovery which will wipe my phone, then perform the ota update, will a restore revert the ruu back and I'm back to square one, or does the ruu not roll back?
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
If you are on a stock rom you should be able to flash the stock recovery from fastboot without wiping the phone. Just find the recovery.IMG from the 605.12 ruu and flash it in fast boot to your phone. Then take the update and when complete flash your custom recovery in fast boot again and flash su zip.
Sent from my Nexus 7 using Tapatalk HD
fivedezs said:
So if I do a back up, then go back to stock recovery which will wipe my phone, then perform the ota update, will a restore revert the ruu back and I'm back to square one, or does the ruu not roll back?
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
A restore would not overwrite any of the firmware on the phone, just the rom.
As dottat pointed out, you can download the latest RUU, extract the recovery image from it and flash that via fastboot. I'd still back up your rom with your custom recovery first in case the rom pieces in the update bork something...
Can anyone point me in the direction of where I can find the stock ruu?
Sent from my ADR6425LVW using xda app-developers app
fivedezs said:
Can anyone point me in the direction of where I can find the stock ruu?
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Check androidpolice.com, it's over there, should be able to search for it...
Need a copy of the stock recovery
I am S-On and unlocked. I need to reflash the stock recovery to apply the OTA firmware update, right? I cannot find a copy of it anywhere. Anyone know where I can get this? I downloaded the stock RUU and tried to pull it out, but I cannot unzip the file. I would be grateful for any help. Thanks.
I was rooted so I flashed stock ROM and recovery but still the update is failing when trying to install....any Idea of what I would have to do to get completely back to stock and install the update?
I would way +/- with updating at this point. It looks like the new update is blocking the previous rooting exploit.
Overall though, in order to get the update its my understanding you need to be in stock recovery
Flash-oholic on my SCH-I545
Be glad you can't take the update. The ota licks down the bootloader so the Motochopper want give u root.
Sent from my SCH-I545 using xda app-developers app
If you use the kies program from Samsung you can flash it back to the original firmware. In the tools menu there's an emergency recovery option.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Same problem here. Getting error 402 trying to OTA update.
Emergency Firmware Recovery in Kies requires a "recovery code from the previous PC".
I had a custom recovery before flashing the stock image. Should I need to flash the stock recovery in addition to the stock rom?
You would have lost root anyway..
Sent from my SCH-I545 using xda premium
I was able to do it through VZW software, regretting it lol I was hoping more bugs were fixed
Yes, I was only able to update using USB via Kies. Something still seems off, as wiping cache in recovery gives an error and reboots.
I haven't been able to update and have given up for now. I did two factory resets, and used Odin to flash back to stock twice, both without any luck. I went ahead and just set everything back up the way it was for now.
I was rooted with TWRP. I flashed stock using VRUAMDK_NoWipe.tar. Phone boots and runs fine, but when in stock recovery I see a red triangle in the androids belly, When trying to install the new update, I get a update failed, error 402. Any ideas?
edlowjr said:
I was rooted with TWRP. I flashed stock using VRUAMDK_NoWipe.tar. Phone boots and runs fine, but when in stock recovery I see a red triangle in the androids belly, When trying to install the new update, I get a update failed, error 402. Any ideas?
Click to expand...
Click to collapse
All I know is that you need to be COMPLETELY STOCK. My assumption would be that NoWipe is leaving something behind that may be causing the problem. Otherwise it could be the flash count. I was getting the same problem and didn't want to risk trying triangle away so I called it quits.
Sent from my SCH-I545 using xda app-developers app
edlowjr said:
I was rooted with TWRP. I flashed stock using VRUAMDK_NoWipe.tar. Phone boots and runs fine, but when in stock recovery I see a red triangle in the androids belly, When trying to install the new update, I get a update failed, error 402. Any ideas?
Click to expand...
Click to collapse
I was stock rooted with cwm....I was also getting 402 after using no wipe..I wound up biting the bullet and flashed the full stock kernel...lost all my settings...hooked up the phone to the pc and installed the verizon update program...the new update came down with no problem....I did of course have to re customize my phone..no biggie since im a firm believer that you should do a factory restore after each update anyway
I was completely stock and rooted and updated whole retaining root.
Sent from my SCH-I545 ME7 Rooted using xda app-developers app
I'm having the same issue. Had the pre-release kernel and stock root just to freeze apps. Got the error on the update so did no wipe which didn't work. Tried doing complete .tar and .pit restore then update and still getting the error. Checked the count in TA and it was at 0. Tried tether update and failed. Now i'm trying the tether repair tool which is currently running.
Forgot i even tried installing just the stock kernel as well with no effect.
Delakit said:
I was completely stock and rooted and updated whole retaining root.
Sent from my SCH-I545 ME7 Rooted using xda app-developers app
Click to expand...
Click to collapse
Luck of the draw I guess. Not sure why it would work for me and no one else.
...sent from my SCH-I545 ME7 Rooted using xda app-developers app
Well last night I got the new it's 531.11
It download and try to install. It fail since I'm on custom recovery but stock rooted Rom.
I remember last time I just installed the other ota via clockworks.
But this in keeps stopping.
Is there a way to unpack it and repack it to use?
Or must I load stock recovery, flash then re root?
Sent from my HTC One using xda app-developers app
Won't even flash on stock recovery. Keep getting red triangle.
Sent from my HTC One using xda app-developers app
Same thing happened to me. Went completely back to stock and it wouldn't work. S off broader locked, sock recovery, Rom, kennel, ect. I kept getting a red triangle too
Sent from my HTC One using xda app-developers app
andybfmv96 said:
Same thing happened to me. Went completely back to stock and it wouldn't work. S off broader locked, sock recovery, Rom, kennel, ect. I kept getting a red triangle too
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
yea wish there was a fix i have no clue why it keeps doing this. The .8 update hung but rebooting fix it. but this one just keeps giving the triangle and not sure how to fix it.
Found the FIX
So found out if you hit vol + and power it will bring up the menu for the stock recovery.
I flash the update using that and came up with and error and red triangle.
It said that tmobile iq was missing and it was trying to patch it.
Which is probably why it stops and throws the Red error.
I added it back to my /system/app/ and it fix it but then came up with another error about another missing app. (i debloated the rom and deleted all the crap)
I added back all the stock boat ware files from Nocturnal_1.27.531.7_Odex_TmoStock rom
Then try to flash 531.11 but came up with some errors for some mix match odex files.
So flash the update 531.8
hangs on running bug_fix1 tool but just reboot phone with vol - and power
try to flash again and it . It finally flash and ended up with a fresh copy of 531.8
So now since all those files are there i flash the 531.11
Went throught withotu problems. Reboot on its own a few times tho.
once it loaded it came up and told me to update the camera and i did so.
I didnt have to re root but probably because i have super su set to stay with ota updates. I did flash back cwmod
Headache and a lot of rebooting lol but i guess its just how it works. The script is written to abort if it doesnt find or is a mix match ver of the file its trying to patch.
look on my signature, made a fresh stock odex rom, nothing added.. not rooted rom,
if u want root, just flash the SU and download from the google playstore busybox 9.6.
no files are added or taken out.