4.2.2 OTA and ClockWorkMod Recovery - Samsung Galaxy Nexus

I have a Yakju Maguro which is currently running JOP40D. I recently installed the ClockWorkMod v6.0.2.3 recovery, and rooted my phone. Now I received the notification for the 4.2.2 OTA update, but as expected CWM gives me an error when attempting to install it. It says "Install Untrusted Package?" and gives me Yes or No as options. Until now, I've always been weary to try the Yes option, so I've always gone for No, and the update obviously didn't install.
So my question is, will it actually work if I select Yes? And if it doesn't, in what condition will my phone be after it fails? Will it boot into the old OS, or will I have to manually re-flash a ROM?
I've tried googling the problem but no one seems to be facing the same exact condition as me. Eveyone reports that the installation simply fails with CWM, and I've never seen any mention of a Yes/No prompt. Also, I haven't found any thread that mentions in what condition the phone will be after the failure, so I'm trying to figure out what's going on.
In addition, I've manually downloaded the "07501b11ad3b.signed-yakju-JDQ39-from-JOP40D.07501b11" zip file from the Google website. Will I be able to flash that instead from CWM, make things simpler?
Thanks for any help.

Related

OTA 2.12.110.4, is it possible to install?

Hi,
I just noticed this was ready to download on my phone today. I downloaded and went to install, but the ClockWordMod Recovery doesn't let me install the update saying, "Image Verification Failed". I assume the problem is that the phone is rooted, and searching through the forums I heard this update isn't really anything big, just removing some German apps or something.
Is there anyway I can stop this update from notifying me? Or anyway to install? My phone is rooted but I'm not bothered about keeping it rooted as at the moment, there is nothing I need the phone to be rooted for. So, either way is fine for me.
Thanks!
If you want to unroot it, just flash generic ruu, more info here http://theunlockr.com/2010/06/07/how-to-unroot-the-htc-desire/
Than simply check for updates and update it
Or wait for few hours for rooted version of this rom
Hi!
I have a branded Desire and installed the update via Recovery. I had to disable the verification to do that (Goldcard inside). But all I got was a boot loop and my phone was derooted. I tried much (e.g. delete my data) and after a couple of hours I found the simple solution: Simply install the update again. Then I rooted my phone and restored the NANDROID Backup I made before I started the update because all of my data was gone.
Then I installed the Update again and this time it worked at the first time. All data was still there. I rooted it again and everything is fine. Don't know why my phone got a boot loop after first try but second try was perfect!
My suggestion: copy the zip from the download folder to the SDcard (made to a Goldcard!!!!) root and to the PC. Just if you need it more than once. Then make a Backup in the Bootloader. Then Install the update via Recovery. If anything goes wrong install the update again!

Verizon Nexus OTA 4.0.4 red triangle exclamation point

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.

[Q] Ll3 update fails no matter what

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

Official Firmware Update trying to install on CWM

I totally forget if I am running CWM on my device right now I know I rooted it, and I am quite sure I put on CWM when I rooted it as well, but it is android version 4.0.4. Anyway, I keep getting an update message to get the latest version. I did press update once, and it downloaded the file and said it failed to update (which is why I am pretty sure I am on CWM). Is there anyway to disable this message?
Another problem I am having is that the phone always forgets the APN name whenever I power off the device. Someone said rebooting fixed it for them, doesn't work for me. Does anyone else have this problem/fix?
Regards,
404

[Q] Quick question about stock recovery

Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
ericksonline said:
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
Click to expand...
Click to collapse
Yes you can go to software number to get the info you need. To do an OTA you need a stock sense ROM (NO CHANGES TO ANY SYSTEM APPS) you then need to flash the correct recovery for your software number and [IMPORTANT] relock the bootloader. You then can reboot into your system and take the OTA while still being able to unlock the bootloader and flash a custom recovery afterwards.
No need to relock the bootloader for an ota. People should stop spreading that info
Thanks for the replies!
Just to check my understanding, since I simply unlocked the bootloader, used the TWRP recovery, added SuperSU, installed then uninstalled Xposed framework, that means that I should still be on a stock sense ROM (with no changes to any system apps), right?
There is a lot to learn with all of this when you are first starting out. I'm reading a lot, but sometimes you do find conflicting information. I'd rather be a little cautious than do something stupid!
Thanks again!
ericksonline said:
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
Click to expand...
Click to collapse
ericksonline said:
Thanks for the replies!
Just to check my understanding, since I simply unlocked the bootloader, used the TWRP recovery, added SuperSU, installed then uninstalled Xposed framework, that means that I should still be on a stock sense ROM (with no changes to any system apps), right?
There is a lot to learn with all of this when you are first starting out. I'm reading a lot, but sometimes you do find conflicting information. I'd rather be a little cautious than do something stupid!
Thanks again!
Click to expand...
Click to collapse
Yup you're good ROM wise. Just flash the stock recovery and you should be good to go.
You can be unlock and have OTA.
You just need a stock recovery.
HTC ONE M8 fails to load up after failed software update
Hello guys, this is my first post. I really need your help as I'm at risk of loosing all my phone data. My phone internal memory had been exhausted and I bought an external SD card. I am unable to transfer data to the external SD card. I was doing a software update on my phone that failed to install, there was a warning sign on the phone screen for a few minutes then it try to power on but has failed, as it's seem to stuck on the screen that display htc powered by android. I tried the recovery holding down the power button and the column up button, the phone power off and back on but is still stuck on this screen (htc powered by android). I tried connecting the phone to my laptop to try and recover my data, but it's not mounting to the laptop. Please can someone help me. Thanks in advance.
Similar to the post above ie rooted and kept on stock. Also loaded a few Xposed modules but when I connected to my wifi I had over 30 updates so loaded all of them and once loaded the old bootloop started. I restored my nandroid backup from TWRP (this is an essential backup) and I was back in action. Phew!!!! I no longer had Xposed. So I did the updates again and the same thing happened. I am now updating one at a time which is painful when you've got so many. I also tried wiping the caches but that didn't work.
I noticed there were a lot of HTC apps eg HTC sense input, service pack, blinkfeed etc. I also notice a super SU update. ericksonlines post above said he had a problem with superSU. What kind of problem? What does he mean by reapplying? Flashing from TWRP?
So the big question. Which app(s) update did the damage???
Any apps I shouldn't update eg HTCs?
Has this happened to anyone else? What did you then do? Is the new updated superSU the problem
Apologies for cross posting on an Australian site but I'm a bit frazzled with all of this.
jbarr3 said:
Similar to the post above ie rooted and kept on stock. Also loaded a few Xposed modules but when I connected to my wifi I had over 30 updates so loaded all of them and once loaded the old bootloop started. I restored my nandroid backup from TWRP (this is an essential backup) and I was back in action. Phew!!!! I no longer had Xposed. So I did the updates again and the same thing happened. I am now updating one at a time which is painful when you've got so many. I also tried wiping the caches but that didn't work.
I noticed there were a lot of HTC apps eg HTC sense input, service pack, blinkfeed etc. I also notice a super SU update. ericksonlines post above said he had a problem with superSU. What kind of problem? What does he mean by reapplying? Flashing from TWRP?
So the big question. Which app(s) update did the damage???
Any apps I shouldn't update eg HTCs?
Has this happened to anyone else? What did you then do? Is the new updated superSU the problem
Apologies for cross posting on an Australian site but I'm a bit frazzled with all of this.
Click to expand...
Click to collapse
Hello! It is possible that an update came through that caused my phone to start into the boot loop. I'm not sure because it worked fine for a few hours before the problem started happening all of the sudden. My guess is that something updated that broke SuperSU. As soon as something would try to use SuperSU (or maybe the rights granted by SuperSU), the phone would crash and reboot. To fix the problem, I rebooted into the bootloader (TWRP) and re-installed SuperSU from there. After I re-installed, everything began working nicely again. I have not had a problem since and the problem occurred a few months ago now. I have also recently updated to the new version of SuperSU with no problems at all.
I hope this helps!
Ron
ericksonline said:
Hello! It is possible that an update came through that caused my phone to start into the boot loop. I'm not sure because it worked fine for a few hours before the problem started happening all of the sudden. My guess is that something updated that broke SuperSU. As soon as something would try to use SuperSU (or maybe the rights granted by SuperSU), the phone would crash and reboot. To fix the problem, I rebooted into the bootloader (TWRP) and re-installed SuperSU from there. After I re-installed, everything began working nicely again. I have not had a problem since and the problem occurred a few months ago now. I have also recently updated to the new version of SuperSU with no problems at all.
I hope this helps!
Ron
Click to expand...
Click to collapse
You're dead right Ron. Supersu was the culprit. Just simply updating from the playstore caused this. I restored an android backup which got me back. I went into the old SuperSu (V1.94) and clicked "clean up when updating from google play" or similar, did the update again (v 2.04 from google) and while this didn't cause rebooting, I couldn't install the binary. I chose "normal" (maybe I should have chosen TWRP) and it didn't work. So I flashed my old v1.94 from TWRP and that got me back. So some questions on updating SuperSu.
1. Is flashing the zip file through TWRP the best way to install a new version?
2. Should I delete or uninstall the old version or will flashing do that for me? Did you simply flash over the top of the other one?
3. Should I stick with 1.94, which works, or should I update to a new and improved version?
4. I think 2.16 is the latest. What version are you running, is it stable and do you recommend it ?
5. I assume I get the zip file from chainfire. They are way ahead of the google playstore for updates
jbarr3 said:
You're dead right Ron. Supersu was the culprit. Just simply updating from the playstore caused this. I restored an android backup which got me back. I went into the old SuperSu (V1.94) and clicked "clean up when updating from google play" or similar, did the update again (v 2.04 from google) and while this didn't cause rebooting, I couldn't install the binary. I chose "normal" (maybe I should have chosen TWRP) and it didn't work. So I flashed my old v1.94 from TWRP and that got me back. So some questions on updating SuperSu.
1. Is flashing the zip file through TWRP the best way to install a new version?
2. Should I delete or uninstall the old version or will flashing do that for me? Did you simply flash over the top of the other one?
3. Should I stick with 1.94, which works, or should I update to a new and improved version?
4. I think 2.16 is the latest. What version are you running, is it stable and do you recommend it ?
5. I assume I get the zip file from chainfire. They are way ahead of the google playstore for updates
Click to expand...
Click to collapse
I'm no expert, but I'm happy to share my experience. I do believe that flashing from TWRP is the best way to install. That is what I did to fix my reboot problems. I don't recall uninstalling the previous version in any way. I think the old file was still on there. I browsed to it in TWRP and installed it. I'm not sure what version I was on when I did this. Recently, a new update (2.16) was available that downloaded through the Play Store. When I went to update, it recommended that I use TWRP to install. I didn't go this route because I had already switched back to the default bootloader and didn't want to reinstall TWRP if I didn't have to. So, I just used the "normal" method. It updated successfully and I've had no problems. I am now running 2.16.
ericksonline said:
I'm no expert, but I'm happy to share my experience. I do believe that flashing from TWRP is the best way to install. That is what I did to fix my reboot problems. I don't recall uninstalling the previous version in any way. I think the old file was still on there. I browsed to it in TWRP and installed it. I'm not sure what version I was on when I did this. Recently, a new update (2.16) was available that downloaded through the Play Store. When I went to update, it recommended that I use TWRP to install. I didn't go this route because I had already switched back to the default bootloader and didn't want to reinstall TWRP if I didn't have to. So, I just used the "normal" method. It updated successfully and I've had no problems. I am now running 2.16.
Click to expand...
Click to collapse
Thanks erick but given what's happened I don't think I'll ever update from the playstore again. I'll load 2.16 using TWRP and report back. I can't stress enough how important it is to have a nandroid backup. I reckon its the best reason to load a custom recovery. Its got me out of trouble twice now and gives me piece of mind. I've actually gone overboard on this and I have two backups on my phone which I have copied to my PC..
vm54 said:
You can be unlock and have OTA.
You just need a stock recovery.
Click to expand...
Click to collapse
And stock ROM.
Updated to v 2.16. Piece of cake!!!
Loaded through TWRP, rebooted and that was it. It didn't even ask about installing the binary. Same binary I guess.
It worried me, however, when I saw over 700 pages on this version xda. Most with problems.
jbarr3 said:
Updated to v 2.16. Piece of cake!!!
Loaded through TWRP, rebooted and that was it. It didn't even ask about installing the binary. Same binary I guess.
It worried me, however, when I saw over 700 pages on this version xda. Most with problems.
Click to expand...
Click to collapse
Awesome! I'm glad to hear that it worked!

Categories

Resources