Got the OTA today. Bog stock not rooted. update failed. After about 30 minutes a retry download button appeared. Pushing it doesn't do anything. Is there a minimum wait between update attempts? Any other ideas?
Same thing happened to me. I have waited 3 days for a repeat but to no avail. I rooted it and installed a custom ROM with the volume fix update in.
http://twitpic.com/7oody4 this?
Mine failed too... mine was just rooted; nothing else
I got the little Android logo with a !
Rebooted again, no update appears; so I decided to just put the update myself.
Twitpik link is broke. Didn't fail during reboot though. Error msg is right in the system update page. The dowload progress bar is grayed out and it says dowload failed instead a percent progress and there is Retry Download button lower right but it doesnt seem to do anything.
texiandave said:
Twitpik link is broke. Didn't fail during reboot though. Error msg is right in the system update page. The dowload progress bar is grayed out and it says dowload failed instead a percent progress and there is Retry Download button lower right but it doesnt seem to do anything.
Click to expand...
Click to collapse
Mine downloaded automatically over night, and asked if I wanted to apply it when I woke up at 6am. Twitpic should work btw, I just looked at it
Mine even said it was downloaded AND verified, but still failed
Rooted on stock rom with CWM.... Without the stock recovery it can't install. Just jumped to a new Rom with the update....I have always hated the auto updates..lol
Is there a way for me to apply this update by itself? Even if I don't have stock recovery? Is it possible to re-set recovery to original without wiping the entire device?
Mine is rooted, stock ROM, CWM recovery.
OTA re-set itself and installed correctly overnight without me doing anything. Not sure why it failed or how it resolved it but it's done.
If you're still having issues try this
http://www.coolsmartphone.com/2011/12/01/galaxy-nexus-ota-patch
Basically its links to the patch (OTA) and how to root/return to stock with a link to the guide on xda
Sent from my Galaxy Nexus using Tapatalk
I eventually received the update. It downloaded and asked for a reboot. I agreed and the phone counted down, then shutdown, but didn't startup. I waited and waited, the power button would not respond, so I removed the battery, and put it back in. It then started up, but still on the old ITL41D software. What did I do wrong? And what do I do now? Is it normal for it to fail to start up aftrr the reboot? Will I get another opportunity?
Sorry for all the questions, but I'm super frustrated
mirilo said:
I eventually received the update. It downloaded and asked for a reboot. I agreed and the phone counted down, then shutdown, but didn't startup. I waited and waited, the power button would not respond, so I removed the battery, and put it back in. It then started up, but still on the old ITL41D software. What did I do wrong? And what do I do now? Is it normal for it to fail to start up aftrr the reboot? Will I get another opportunity?
Sorry for all the questions, but I'm super frustrated
Click to expand...
Click to collapse
Is your phone rooted? If so, I would look at the comment above yours with the link to the patch (and instructions) to flash it manually. If it is not, it will likely allow you to retry in a day or two.
Hope it all works out for you.
EDIT: I just tried flashing the patch manually as per the prior instructions posted and it didn't work. It gave me "Error (Status 7)" and aborted the installation. Although, right when it rebooted back into the home screen, it came up with the official OTA update again. I'm hesitant on trying it again, since it's likely to fail due to whatever reason caused it to fail the first time.
Either way, this is getting aggravating. I really wish there was an easier way to get this patch without needing to lose root and having to re-do things all over again. I have done a TiBu batch run of all of the stuff I need, but still...oh well.
FlareHeart said:
Either way, this is getting aggravating. I really wish there was an easier way to get this patch without needing to lose root and having to re-do things all over again. I have done a TiBu batch run of all of the stuff I need, but still...oh well.
Click to expand...
Click to collapse
Don't think I've ever seen an OTA which left root intact. This occurs when the OTA sets the permissions recursive for the whole directory /system/bin to 755 removing the setuid attribute on the /system/bin/su binary.
The binary will still be there, but will have to have the setuid attribute added back, chdmod 4755, which will then return root.
Does seem odd Google allows the device to be unlocked, but yet unlocked devices get root access wiped. If they claim to want open source and open devices, perhaps they could script an exception for root access and not remove it with every OTA.
Normally, when Error status 7, or any other recovery error, we're in a custom recovery with adb access and can pull the log at /tmp/recovery.log or /cache/recovery.log and examine what caused the issue as more output is stored there than presented on the screen to the user.
Perhaps googling this recovery error code or grabbing the open source from AOSP will show generally what causes it.
Does seem odd the issues other users have had *automatically* cleared themselves after waiting a while.
First idea which comes to mind is perhaps the original OTA had a bug in the scripting and they were slowly replacing and pushing out the updated OTA.
Keep us updated! I'm on the samsung version of ics so I'll probably have to manually push over all the images...but good to keep up with the *official* route.
When trying to install my update, I get signature verification failed in recovery.
Any ideas?
EDIT: Flashed the recovery posted in the Image on Googles site.
Fixed the problem for me.
joeykrim said:
Keep us updated! I'm on the samsung version of ics so I'll probably have to manually push over all the images...but good to keep up with the *official* route.
Click to expand...
Click to collapse
Not technically official, but a MUCH easier way to get the patch and keep all of your settings and root can be done using the slightly modified stock ROM from bigxie (link: http://forum.xda-developers.com/showthread.php?t=1372376)
If you clear just the cache and dalvik, then flash this. You get the patch, SU, and busybox, without losing all of your settings or data.
Worked great for me. Hope that helps!
Related
I am rooted and have an unlocked bootloader but have stock rom and stock kernals and stock radios.... everything else stock.
I get the "new update available" OTA click to restart and the phone restarts. I get the android with a blue spinning something in his back with the progress bar moving. at about 25% it always changes to the android on his back with a red triangle exclamation point. Nothing happens from here.
I can do a battery pull and get the phone to start fine again.
I've seen these problems in other posts, but theres always something thats not the same as my phone for example the person flashed a rom or kernal. I have not.
any help?
kegman913 said:
I am rooted and have an unlocked bootloader but have stock rom and stock kernals and stock radios.... everything else stock.
<snip>
I've seen these problems in other posts, but theres always something thats not the same as my phone for example the person flashed a rom or kernal. I have not.
Click to expand...
Click to collapse
Can't help, I'm in the same boat. Trying to think of anything I've done that could be interfering:
Adfree (changes /etc/hosts)
SecureSettings plugin (installs a helper app)
SQLite Installer for root (failed to get this to work; tried to do it manually, forget if I got it )
Maybe there's something else I did that could be interfering too, I forget. At this point I'm wondering if its time to give up on stock and go CM9?
So you rooted your phone, and installed a custom bootloader then kept everything else stock?
My best guess is the custom bootloader is interfering with some permissions being requested by the update. I would go back 100% stock (un-root and reflash the original bootloader) then apply the update with everything locked down just like Big Red likes it.
Make sure you always backup when playing with bootloaders and rooting!
Hope this helps!
i just unlocked the bootloader, this isn't considered a custom bootloader is it? basically, I never did anything custom to it
Did you change your fonts or changed anything with the UI? How about modifying the build.prop?
If you try it again and see the android guy laying down press volume up + power to show the menu. It should list where the OTA failed. (you might have to press that combo a few times)
Report back.
i'll try it a second time when I get home, but volume up and power do nothing, hitting them together, in sucession, holding them both down, holding volume up, down and power do nothing either.......weird
nope, does nothing, maybe the other guy with this prob can confirm?
Hmmm weird. I'm pretty sure you can get the stock recovery to display with a button combo.
You might have to flash the stock image to get the OTA to apply. Something had to have been changed in /system.
Read Efrant's guide on how to do so. http://forum.xda-developers.com/showpost.php?p=25477039&postcount=1
i read somewhere that it might be due to clockwork recovery being the default recovery. how do I change this?
kegman913 said:
i read somewhere that it might be due to clockwork recovery being the default recovery. how do I change this?
Click to expand...
Click to collapse
You need to flash the stock recovery image. Download the factory image for the build that you are on, extract the recovery.img file, reboot your phone into fastboot, and in a command prompt, type: fastboot flash recovery recovery.img
Have a read of the guide that El Daddy linked to. It may explain some things for you.
Red Triangle - Error info
I'm also having this problem with trying to update.
I have an unlocked bootloader but its still the standard one (I didn't do anything other than unlock it) and I'm rooted but didn't flash any ROMs so it is still stock 4.0.2.
I tried a factory reset, stupidly without making sure everything was backed up, and it didn't change anything, I still get the red triangle, in case anyone was thinking of trying that.
I got to the recovery menu (holding power and pressing volume up) and after Installing the update... and Verifying current system...
Here is the entire error message:
assert failed: apply_patch_check("system/bin/gizp", "51086995a674ab78fd63b49aa7207df466624897", "5ba3b3ecd509cf6cee37b2f27110310a1f55045")
E: Error in /cache/12f767e7a5d0.incremental.zip
(status 7)
Installation aborted
From there, I have no choice but to choose to reboot. Hope this info helps someone come up with a solution.
umataro42 said:
I'm also having this problem with trying to update.
I have an unlocked bootloader but its still the standard one (I didn't do anything other than unlock it) and I'm rooted but didn't flash any ROMs so it is still stock 4.0.2.
I tried a factory reset, stupidly without making sure everything was backed up, and it didn't change anything, I still get the red triangle, in case anyone was thinking of trying that.
I got to the recovery menu (holding power and pressing volume up) and after Installing the update... and Verifying current system...
Here is the entire error message:
assert failed: apply_patch_check("system/bin/gizp", "51086995a674ab78fd63b49aa7207df466624897", "5ba3b3ecd509cf6cee37b2f27110310a1f55045")
E: Error in /cache/12f767e7a5d0.incremental.zip
(status 7)
Installation aborted
From there, I have no choice but to choose to reboot. Hope this info helps someone come up with a solution.
Click to expand...
Click to collapse
Did you use Stericson Busybox installer?
I also get thus error any help would be great
drummynator said:
Did you use Stericson Busybox installer?
Click to expand...
Click to collapse
I think so. If I have it installed, does it automatically get used?
Should I try uninstalling it?
umataro42 said:
I think so. If I have it installed, does it automatically get used?
Should I try uninstalling it?
Click to expand...
Click to collapse
Well, I have it installed too and I did try to uninstall it, but it still didn't work.
Sent from my Galaxy Nexus using Tapatalk 2
Does anyone know where the downloaded update is stored?
Does anybody know where the downloaded updated is stored?
If they do can I please put the location.
I am willing to try to install the updated downloaded file using clock work mod recovery.
Why don't you guys just have a read of this. It tells you how to install it manually (really easy), and what you need to do to have it install automatically.
P.S. For those talking about busybox, it has nothing to do with it...
efrant said:
Why don't you guys just have a read of this. It tells you how to install it manually (really easy), and what you need to do to have it install automatically.
P.S. For those talking about busybox, it has nothing to do with it...
Click to expand...
Click to collapse
I have looked at that and tried Method 1, but the same thing happened. I've also tried toggling asserts. Still no luck. I used the mysid IMM76K from ICL53F.
drummynator said:
I have looked at that and tried Method 1, but the same thing happened. I've also tried toggling asserts. Still no luck. I used the mysid IMM76K from ICL53F.
Click to expand...
Click to collapse
The guide also tells you what the requirements are for it to work, namely that all the original system files need to be there.
The recovery will tell you which file is not stock. In your case, you got:
assert failed: apply_patch_check("system/bin/gizp", "51086995a674ab78fd63b49aa7207df466624897", "5ba3b3ecd509cf6cee37b2f27110310a1f55045")
Which means that your /system/bin/gzip file is not the original one that came with your ROM. Just replace it with the stock one, as per the instructions in the link posted above.
efrant said:
The guide also tells you what the requirements are for it to work, namely that all the original system files need to be there.
The recovery will tell you which file is not stock. In your case, you got:
assert failed: apply_patch_check("system/bin/gizp", "51086995a674ab78fd63b49aa7207df466624897", "5ba3b3ecd509cf6cee37b2f27110310a1f55045")
Which means that your /system/bin/gzip file is not the original one that came with your ROM. Just replace it with the stock one, as per the instructions in the link posted above.
Click to expand...
Click to collapse
That looks like the error I got when I did the VolumeUp/Power combination and attempt the update.
/system/bin/gzip is a symlink for the busybox executable. Is there a way to put back stock files for everything that busybox replaced in one go? I have a feeling if I were to figure out how to get the stock gzip back, and try to do the update, that I'd find another system file was replaced by busybox.
My Dinc is rooted S-off and I'm still getting ota update notification. I tried to run the update and it does nothing....
If you're on a stock (even rooted) ROM, you'll get the ota notification. But it requires stock recovery to flash. I haven't looked into the actual zip, so I don't know if it'll flash via CWM or not. It used to not, and I doubt it's changed.
PonsAsinorem said:
If you're on a stock (even rooted) ROM, you'll get the ota notification. But it requires stock recovery to flash. I haven't looked into the actual zip, so I don't know if it'll flash via CWM or not. It used to not, and I doubt it's changed.
Click to expand...
Click to collapse
That is correct, the ota will not work unless you are complete stock. Meaning stock recovery, all original and unmodified apps and framework files, and you must still be odexed.
If you just want to stop the update nag you can go to /system with a root file explorer and open for editing the build.prop file. Look for a line that starts like this " ro.build.fingerprint= ", change the whole line to look like this without the quotes " ro.build.fingerprint=verizon_wwe/inc/inc:2.3.4/GRJ22/389630.15:user/release-keys ". This tricks the update server into thinking you already have the latest update.
If you want a rom with the new update, there is the Stock 4.08.605.15 Rom and Touch of blue. One is pure rooted stock, and TOB is mostly stock but debloated and lightly themed.
I need to get the latest OTA update, but can I only get it through a new Rom or can I just gets new OTA update to work with my current Rom?
Sent from my PC36100 using xda app-developers app
Richard6292 said:
I need to get the latest OTA update, but can I only get it through a new Rom or can I just gets new OTA update to work with my current Rom?
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
You have to be complete stock to sucessfully update ota. Just flash the stock 4.08.605.15 rom in the dev section. You'd be getting the same thing, without all the hastle of ruu'ing, updating ota, and then rerooting.
Thanks for the info! But after that, if I were to relfash my current Rom I'd just be back in the same situation right?:/ I wish my current Rom would be update but the dev'r went away..
Sent from my PC36100 using xda app-developers app
Richard6292 said:
Thanks for the info! But after that, if I were to relfash my current Rom I'd just be back in the same situation right?:/ I wish my current Rom would be update but the dev'r went away..
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
Right, if your current rom is not based on 4.08.605.15, then you will get the ota notification. Even if you got the actuall ota to install, it would more than likley mess up the rom, and then you would have to reflash the rom and you would be right back where you started. If you want to stay on your current rom but stop the ota notification, do as i said a couple posts above and edit the build.prop file to make the update server think you already have the latest ota. What rom are you currently on?
Ok, thanks for the help!!
Sent from my PC36100 using xda app-developers app
I am using TOB so can I install the update without messing things up?
joeyz400 said:
I am using TOB so can I install the update without messing things up?
Click to expand...
Click to collapse
No tob has stock apps removed and is deodexed. The ota checks to make sure all original apps and files are present and unchanged. If you wabt to get the actuall ota tou need to ruu to stock 4.06.605.3 and then ota to 4.08.695.2 and then ota to 4.08.605.15. However tob V2.1 has been updated to 4.08.605.15 already.
Experience with this OTA update
I can't post yet to the development forums and I saw that cmlusco was on here so just wanted to share my experience. I have an SMOLED Droid Incredible and I'm rooted, S-OFF on the latest CWM recovery and I was using wildstang's stock ROM from the last update back in November 2011. I got the notification, searched the forums, and ended up installing cmlusco's stock deodexed ROM, after doing all the requisite wipes and checking the md5. My initial experience was great, apart from once when the phone simply died with a black screen and was completely unresponsive. Battery pull solved that. After I was done getting all my apps back on there (mostly via downloading and then for some of them just restoring the data from Titanium Backup), I did a Titanium Backup and a nandroid backup in the recovery. After all of these were done, I started having quite a few freeze issues. I think I had three in a row before I had one while in the process of connecting the phone to my computer. Had to do the battery pull method each time but the last time, the phone must have been right in the middle of mounting to my laptop because all of my downloaded apps were "gone". As in, they were not in the app drawer and all the icons were the default Android icon on the home screens. I think something happened with the freeze in the middle of the mount. If I reinstalled an app from the market and tried to restart it, it force closed. Then, if I uninstalled and reinstalled it, it did work. But I was still getting some force closes so I figured it might just be easier to flash the ROM again, which is what I did.
So now I'm back up and running, and mostly everything is okay. I did get another freeze while installing an app and waited for a while but since the phone was still unresponsive, I did the battery pull again. Stuff is working but I thought I'd share my experience and see if anyone else had something similar happen. Oh, by the way, I also updated to the latest radio but hadn't the first time I used this ROM. And cmlusco, thanks a lot for posting that and being very patient in the forums. If this ROM fails again, I might try Touch of Blue.
cmlusco said:
That is correct, the ota will not work unless you are complete stock. Meaning stock recovery, all original and unmodified apps and framework files, and you must still be odexed.
If you just want to stop the update nag you can go to /system with a root file explorer and open for editing the build.prop file. Look for a line that starts like this " ro.build.fingerprint= ", change the whole line to look like this without the quotes " ro.build.fingerprint=verizon_wwe/inc/inc:2.3.4/GRJ22/389630.15:user/release-keys ". This tricks the update server into thinking you already have the latest update.
If you want a rom with the new update, there is the Stock 4.08.605.15 Rom and Touch of blue. One is pure rooted stock, and TOB is mostly stock but debloated and lightly themed.
Click to expand...
Click to collapse
Thanks, I changed that line and the annoying system update is gone
cmlusco said:
That is correct, the ota will not work unless you are complete stock. Meaning stock recovery, all original and unmodified apps and framework files, and you must still be odexed.
If you just want to stop the update nag you can go to /system with a root file explorer and open for editing the build.prop file. Look for a line that starts like this " ro.build.fingerprint= ", change the whole line to look like this without the quotes " ro.build.fingerprint=verizon_wwe/inc/inc:2.3.4/GRJ22/389630.15:user/release-keys ". This tricks the update server into thinking you already have the latest update.
If you want a rom with the new update, there is the Stock 4.08.605.15 Rom and Touch of blue. One is pure rooted stock, and TOB is mostly stock but debloated and lightly themed.
Click to expand...
Click to collapse
So, I edited the "ro.build.fingerprint" line, and I'm still getting the notification... I've tried the "fix" of renaming the /etc/security/otacerts.zip file to otacerts.zip.bak, which some suggest. Hell, I even ended up deleting the whole file. When that didn't work, I froze /system/app/updater.apk. Still nothing, so I deleted that file as well. Nothing is listed in my /cache folder, where some people have noted that the download stores itself. I had the 4.08.605.15 update before, and it caused my phone to freeze a lot, and randomly reboot over and over for hours. During those reboots, half my apps got deleted as well.
Needless to say, I don't want the stupid update!! But nothing I can find on any forum is stopping my phone from getting the notification every 15-20 minutes. I've tried flashing a few different ROMs, but my phone gets stuck in a boot cycle with any of them. Just the other day, I went to flash the newest CyanogenMod through CWM, and it just kept showing the blue android guy on a skateboard for (no joke) about 3 hours. I ended up pulling the battery and flashing my stock recovery.
Please let me know if there's anything else anyone can think of that might stop the notification. I'm still 3 months out from being eligible to upgrade my phone, and I'd rather not deal with the notification popping up over and over and over for that time
Thanks
ggoodman1022 said:
So, I edited the "ro.build.fingerprint" line, and I'm still getting the notification... I've tried the "fix" of renaming the /etc/security/otacerts.zip file to otacerts.zip.bak, which some suggest. Hell, I even ended up deleting the whole file. When that didn't work, I froze /system/app/updater.apk. Still nothing, so I deleted that file as well. Nothing is listed in my /cache folder, where some people have noted that the download stores itself. I had the 4.08.605.15 update before, and it caused my phone to freeze a lot, and randomly reboot over and over for hours. During those reboots, half my apps got deleted as well.
Needless to say, I don't want the stupid update!! But nothing I can find on any forum is stopping my phone from getting the notification every 15-20 minutes. I've tried flashing a few different ROMs, but my phone gets stuck in a boot cycle with any of them. Just the other day, I went to flash the newest CyanogenMod through CWM, and it just kept showing the blue android guy on a skateboard for (no joke) about 3 hours. I ended up pulling the battery and flashing my stock recovery.
Please let me know if there's anything else anyone can think of that might stop the notification. I'm still 3 months out from being eligible to upgrade my phone, and I'd rather not deal with the notification popping up over and over and over for that time
Thanks
Click to expand...
Click to collapse
make sure your file explorer is in r/w (read/write) mode or the changes that you made will not save. there is a button in the upper right part of root explorer if that is that app you are using.
nschiwy said:
make sure your file explorer is in r/w (read/write) mode or the changes that you made will not save. there is a button in the upper right part of root explorer if that is that app you are using.
Click to expand...
Click to collapse
Also you must be s-off, or adb pull edit and push the file while in recovery.
Try flashing this. Got rid of the nagging when I was on GB. Should take care of it.
http://db.tt/zPhTShuA
sorry...I was on the phone...
nschiwy said:
make sure your file explorer is in r/w (read/write) mode or the changes that you made will not save. there is a button in the upper right part of root explorer if that is that app you are using.
Click to expand...
Click to collapse
It is definitely in r/w mode. I restarted the phone, cleared cache, then checked the file again to make sure the edit was still there. And it was...
cmlusco said:
Also you must be s-off, or adb pull edit and push the file while in recovery.
Click to expand...
Click to collapse
I've had s-off since a few days after I got the phone last year.
omniatic said:
Try flashing this. Got rid of the nagging when I was on GB. Should take care of it.
http://db.tt/zPhTShuA
sorry...I was on the phone...
Click to expand...
Click to collapse
I restored from a prior backup to undo all the changes I made, so I'm going to try each of the methods again, and if nothing works, I'll flash this.
Thank you all. I've been relying too much on "one-click" solutions in the past, but I'm now trying to get more into the actual dev side of things, so I can help out with this kind of stuff as well
ggoodman1022 said:
It is definitely in r/w mode. I restarted the phone, cleared cache, then checked the file again to make sure the edit was still there. And it was...
I've had s-off since a few days after I got the phone last year.
I restored from a prior backup to undo all the changes I made, so I'm going to try each of the methods again, and if nothing works, I'll flash this.
Thank you all. I've been relying too much on "one-click" solutions in the past, but I'm now trying to get more into the actual dev side of things, so I can help out with this kind of stuff as well
Click to expand...
Click to collapse
I retried all the methods, and flashed the file mentioned above. Still no luck
Stupid notification pops up over and over and over... Guess I may either have to update, or deal with the notification until October when I can upgrade my phone. Or try flashing a custom ROM, even though I like the stock ROM
You could always flash cmlusco's touch of blue ROM which is an optimized version of the latest OTA, so you wouldn't have to worry about update notifications on that one for sure (at least on the latest version).
http://forum.xda-developers.com/showthread.php?t=1492720
but there are lots of options here
http://forum.xda-developers.com/forumdisplay.php?f=638
Disclaimer: This worked on my phone. I am not responsible if your phone turns into an expensive brick.
I know this isn't quite the update everyone was waiting for I managed to pull the 2.3.6 OTA files. I also managed to figure out how to flash them. Turns out CWM 5 offers root adb access, everything we need to update and root this phone. Note I tried CWM 6 but it said "possible loss of root" so apparently CWM 6 likes to reside on an already rooted phone.
Note this is not the most elegant solution. The most elegant would be a signed update.zip. The second most elegant would be something flashable with CWM or Odin. Too bad I don't know how to do those. I do know how to do this.
The first thing to do is make sure you are on the AT&T stock firmware. It doesn't matter if you've already flashed something else. No need to wipe cache or factory reset or anything (although if you run into problems you should try to do that step). Download it from samfirmware.com. Flash it with Odin. This will put you on stock 2.3.5. Even if you were already on 2.3.6, or rooted, or on Rogers, this will work. After the flash, boot the phone normally, wait a minute or so, and shut it down.
Now for the fun part. AT&T will not push the OTA to a non AT&T customer. The flash will also not work with a modified phone (hence the reflash to stock). How to gain root access to manually flash the OTA? If we install root, it will not install. If we install CWM, we will not have the stock recovery which is required to process the OTA. So...
How about this? We install CWM 5. You can find it here http://forum.xda-developers.com/showthread.php?t=1458153
Then we adb into the phone, and push the OTA files, and then reflash the stock recovery over CWM, and then manually reboot into OTA mode. That sounds crazy... crazy enough to work.
After you've flashed CWM, reboot into it and make sure your phone is still connected to your computer. We won't actually be using CWM, just the root access it provides over adb. Unzip the two zip files below (why use external hosting, I can store zips up to 11 MB on here) into a folder and run fota.bat. Ooo and ahh over your Gingerbread.
But what about root? Well, I posted in another thread a complicated method for rooting 2.3.6 using the root access from CWM, but how about easy? Boot your phone into 2.3.6 and let it sit for a minute or so, and shut it down. Reboot into Odin mode, and reflash CWM over the stock recovery (again). Copy the Superuser zip from the folder you made earlier to your SD card. Flash this with CWM. This is the beta of Superuser 3.2, courtesy of Rom Manager. Download the stericson busybox app from the Market if you want busybox as well.
This was a fun way to kill a weekend
Throws a signature verification failed error.
Try again with the new method
Had a few mild scares. After flashing CWM on stock, it refused to boot into it but after 3 tries and my screen acting up upon boot, it finally booted into CWM. Launched the bat file and it went well. Upon booting up and entering the update process, it froze up at 74% and refused to continue. Rebooted the phone and it once again entered the update process and this time it managed to finish. Phone rebooted and after checking "About phone", my phone is on 2.3.6 stock. When you initially provided the OTA files and the sig check failed, I had a good feeling this would be the only other way to do it as I tried to sign it and it also failed. Thanks for taking the time to post all of this.
Why go to 2.3.6? It´s better than 2.3.5 customized?
Better question: we're getting ICS within the month, so why bother with 2.3.6 when you can just upgrade to 4.x.x when it comes down?
-Ara
AraDreamer said:
Better question: we're getting ICS within the month, so why bother with 2.3.6 when you can just upgrade to 4.x.x when it comes down?
-Ara
Click to expand...
Click to collapse
Because there are some people who will want to stick with 2.3.5/6 . He made this so that those who do, can update to 2.3.6 even when they aren't with AT&T, almost hassle free.
narume said:
Had a few mild scares. After flashing CWM on stock, it refused to boot into it but after 3 tries and my screen acting up upon boot, it finally booted into CWM. Launched the bat file and it went well. Upon booting up and entering the update process, it froze up at 74% and refused to continue. Rebooted the phone and it once again entered the update process and this time it managed to finish. Phone rebooted and after checking "About phone", my phone is on 2.3.6 stock. When you initially provided the OTA files and the sig check failed, I had a good feeling this would be the only other way to do it as I tried to sign it and it also failed. Thanks for taking the time to post all of this.
Click to expand...
Click to collapse
When I was testing this, I saw that behavior if you didn't completely boot up the phone between steps (ie, flash stock firmware, boot phone, flash CWM, boot phone). I don't know what would cause it otherwise. Glad to see your phone made it.
narume said:
Because there are some people who will want to stick with 2.3.5/6 . He made this so that those who do, can update to 2.3.6 even when they aren't with AT&T, almost hassle free.
Click to expand...
Click to collapse
Actually I did it because I've owned this phone for exactly two weeks and discovered all the available ROMs are based on 2.3.5 even though 2.3.6 has been out since December. CWMR with root has been out since January, and since then nobody else has rooted 2.3.6 or found a way to flash it. And I thought, it couldn't be that hard? And even more amazed when I discovered CWMR comes with root out of the box, without even touching /system. The only other missing piece was the stock recovery, which also wasn't out in the wild. 3 birds for one stone
On a side note, if you want to do some cleaning after the OTA and you decide to root, you can delete /cache/fota and /data/fota safely.
Nardholio said:
Actually I did it because I've owned this phone for exactly two weeks and discovered all the available ROMs are based on 2.3.5 even though 2.3.6 has been out since December. CWMR with root has been out since January, and since then nobody else has rooted 2.3.6 or found a way to flash it. And I thought, it couldn't be that hard? And even more amazed when I discovered CWMR comes with root out of the box, without even touching /system. The only other missing piece was the stock recovery, which also wasn't out in the wild. 3 birds for one stone
On a side note, if you want to do some cleaning after the OTA and you decide to root, you can delete /cache/fota and /data/fota safely.
Click to expand...
Click to collapse
Ah, I see. Well, still, being able to flash to 2.3.6 is nice because if anyone ever decides to stick with 2.3.6 they can easily flash the update now. Maybe more people like you will pop up and start pushing out more useful content like this for the Glide so it won't be a dead area of development anymore.
I have been trying to get my S3 to take the update from LG8 to Ll3, and it fails no matter what I try. I am running totally stock LG8 that I rooted using the toolkit posted in the development section. I don't have any APKs that I altered, but every time I try to flash the update, I get a "status 7" error. I tried it on both internal and external SD using CWM recovery. I tried flashing stock recovery via Odin and then let the phone download it over the air and attempt to install itself, and I even tried running the update in TWRP. Every time I get the same status 7 error.
I am coming from HTC phones and have never had these kinds of issues, so I'm pulling out my hair. Can anyone offer any suggestions? I know it must be something stupid I'm overlooking, but I've searched everywhere and can't seem to find the answer.
Sounds like a bad DL. Just grab it from here. http://forum.xda-developers.com/showthread.php?t=1743923
Or here http://forum.xda-developers.com/showthread.php?t=1904099
Or odin flash LI3- http://forum.xda-developers.com/showthread.php?t=1919919
A lot less stressful
The procedure that myn posted over here is pretty staight forward and foolproof too.
Have you solved your issue yet?
I am getting the status 7 error as well even with Myn's procedure. Others are having the problem. Only thing I can think of is the current image file has changed enough to not allow the update to go through. However, I have not removed or modified any stock apks and backed my whole system up with TB right after rooting so no reason for mine to not work. Binary file should be good since it is working for other S3 users.
It's not a bad download. I have tried downloading it multiple times from several sources, and I get the same status 7 failure every time. It even fails when the phone itself downloads the update and it tries to install with the stock recovery.
cfonte100 said:
It's not a bad download. I have tried downloading it multiple times from several sources, and I get the same status 7 failure every time. It even fails when the phone itself downloads the update and it tries to install with the stock recovery.
Click to expand...
Click to collapse
I was able to get mine to work using Myn's method. Seems flashing newest CWM recovery did the trick. Was trying to flash via TWRP and didn't think it would matter but apparently it does. Just followed his post and all upgraded without issue.
Back to your issue.....what state is your phone at currently? What recovery is installed and what version are you running? Surely we can get this resolved for you.
what does the log say when it fails? I mean in addition to status 7. If you don't see anything go under advance>show log. it's probably a failure in the checks it does before the flash. Have u modified your build.prop? is your baseband and build both lg8? That log will tell you what's wrong.or as I mentioned above you could follow 1 of my links and avoid tha headache
I rooted a new aftv last night and all went smooth. Today downgrading and installing cwm very different story.
My aftv now boots to a plain screen displaying the time (incorrectly), a lock symbol and the word "charged" I'm not sure which scared me more. But I'm not bricked. I could still connect with adb and reboot recovery. AND if I hadn't panicked I would've found out sooner that pressing the context menu key on remote takes me right back to the homescreen.
I swear I followed the guides on aftvnews (well done btw!) But every time there was a "if this happens" stipulation in the guides, it happened to me. I can't say it was hard but it was tedious.
Now my issue to I've pushed the correct Rom.zip to my sd card, rebooted recovery but the install fails with this error--Assert failed !less_than_int getprop ro.build.date.utc
I might be missing critical details here to help with diagnosing. Sorry. I've got to work. That process took way longer than expected. I'm hoping it might be enough info to get some ideas. I'll try to check back here later. Thanks.
KLit75 said:
I rooted a new aftv last night and all went smooth. Today downgrading and installing cwm very different story.
My aftv now boots to a plain screen displaying the time (incorrectly), a lock symbol and the word "charged" I'm not sure which scared me more. But I'm not bricked. I could still connect with adb and reboot recovery. AND if I hadn't panicked I would've found out sooner that pressing the context menu key on remote takes me right back to the homescreen.
I swear I followed the guides on aftvnews (well done btw!) But every time there was a "if this happens" stipulation in the guides, it happened to me. I can't say it was hard but it was tedious.
Now my issue to I've pushed the correct Rom.zip to my sd card, rebooted recovery but the install fails with this error--Assert failed !less_than_int getprop ro.build.date.utc
I might be missing critical details here to help with diagnosing. Sorry. I've got to work. That process took way longer than expected. I'm hoping it might be enough info to get some ideas. I'll try to check back here later. Thanks.
Click to expand...
Click to collapse
There's been a few people who have reported the lockscreen oddness. Once you install the update and do a factory reset it will be fine. As for the error, you are not using the correct update. You need to use the prerooted roms.
rbox said:
There's been a few people who have reported the lockscreen oddness. Once you install the update and do a factory reset it will be fine. As for the error, you are not using the correct update. You need to use the prerooted roms.
Click to expand...
Click to collapse
Not being home right now...But following the guide and working from memory...I've got the latest cwm, unlocked boot loader and running 51.1.2.0, my next step would've been to flash
51.1.4.0
If those steps are accurate then from the info I put in the op, I did not install 51.1.4.0 and that's why it failed. I'll bet you're right but I'm pretty sure I pushed the correct version.
It's a bit confusing but doesn't this version require your boot menu. I'm fairly certain the newest cwm does need it. So assuming I pushed the correct version of prerooted fw...would not having boot menu cause the install to fail. Or maybe it's 2 errors on my part but I do remember downloading 51.1.4.0
Thanks a lot! It's in everyone's best interest you don't spend time assisting people like me with something that's probably simple. So if anyone has a comment on my posts please share.
KLit75 said:
Not being home right now...But following the guide and working from memory...I've got the latest cwm, unlocked boot loader and running 51.1.2.0, my next step would've been to flash
51.1.4.0
If those steps are accurate then from the info I put in the op, I did not install 51.1.4.0 and that's why it failed. I'll bet you're right but I'm pretty sure I pushed the correct version.
It's a bit confusing but doesn't this version require your boot menu. I'm fairly certain the newest cwm does need it. So assuming I pushed the correct version of prerooted fw...would not having boot menu cause the install to fail. Or maybe it's 2 errors on my part but I do remember downloading 51.1.4.0
Thanks a lot! It's in everyone's best interest you don't spend time assisting people like me with something that's probably simple. So if anyone has a comment on my posts please share.
Click to expand...
Click to collapse
The only way to get the ro.build.date.utc failure is by using a stock package. My prerooted roms simply do not have that check in them. It fails on that line precisely to prevent people from installing stock packages.
rbox said:
The only way to get the ro.build.date.utc failure is by using a stock package. My prerooted roms simply do not have that check in them. It fails on that line precisely to prevent people from installing stock packages.
Click to expand...
Click to collapse
Thanks a lot! You probably saved me a lot of time trying to figure out where I went wrong. When I get home I'll delete the Rom I pushed, push the correct one, if it installs right I think my next move is your boot menu. But I'll double or triple check that later on tonight.
Edit--install 51.1.4.0 updated version then, if I follow correctly, I can install the latest prerooted fw.
I did everything I said I was going to do and it went smoothly. I'm now running prerooted 51.1.40
There's just one thing. I was certain I unlocked bootloader earlier today. From what I know it's not possible to have the latest cwm with a locked bootloader. But when I clicked unlock bootloader in adbfire (the program I use for my other aftv) it says "bootloader not unlocked"
So I was second guessing myself. But couldn't explain how I missed it and still had the latest cwm. I checked and aftv-unlock was there in my adb folder. I wouldnt have put it there if I didn't transfer it. But to be on the safe side I went back into the terminal and unlocked my bootloader (I believe for the 2nd time). THEN i hit the unlock bootloader on adbfire again and it still returns with "bootloader not unlocked"???
Is it because busybox was not installed through adbfire? If I use it on my other aftv it says "bootloader unlocked" so the software definetly can confirm it. It's just not...
Normally I'd go ahead and install rbox's boot menu then the latest firmware, but many more things have gone wrong in the last 24 hours (not tragically wrong) but just enough for me to wait for an answer on this and maybe stop for the night. Everything's working great (knock-wood) but I assume when rbox finishes android tv I'll need the boot menu. So I'll wait here patiently for both. Thanks.