Related
As this post: http://forum.xda-developers.com/showthread.php?t=1043541
I would like to go back Stock and get OTA updates. My problem is I can't use the unrooting tutorial on the G2/Z wiki as it require to flash a stock Rom and the only available stock ROM for my carrier is too old to get the OTA update (1.34.666.1 and OTA is looking for 1.34.666.5)
TheSPam gave me is nandroid backup so now I have the 1.34.666.5 Version but I'm still rooted. I'm trying to get back 100% stock.
When I'm trying to do the OTA update, after rebooting to flash the update clockworkmod recovery interfere and the OTA update Fail.
I've tried renaming the Update to update.zip, put this on the root of my sdcard and get clockworkmod to install the update from sdcard but I get an error like getprop CID and the update fail.
how can I get back to 100% Stock, unrooted and be able to get the OTA update?
Tonkadan said:
As this post: http://forum.xda-developers.com/showthread.php?t=1043541 I would like to go back Stock and get OTA updates. My problem is I can't use the unrooting tutorial on the G2/Z wiki as it require to flash a stock Rom and the only available stock ROM for my carrier is too old to get the OTA update (1.34.666.1 and OTA is looking for 1.34.666.5) TheSPam gave me is nandroid backup so now I have the 1.34.666.5 Version but I'm still rooted. I'm trying to get back 100% stock. When I'm trying to do the OTA update, after rebooting to flash the update lockworkmod recovery interfere and the OTA update Fail. I've tried renaming the Update to update.zip, put this on the root of my sdcard and get clockworkmod to install the update from sdcard but I get an error like getprop CID and the update fail. how can I get back to 100% Stock, unrooted and be able to get the OTA update?
Click to expand...
Click to collapse
What makes you think opening a new tread is going to solve your issue http://forum.xda-developers.com/showthread.php?t=1043541 quicker?
Absolutely nothing. I started a new thread because the issue in the original post is resolved and i'm facing a complete new problem. Because the initial issue was very specific to my carrier I tough starting a new thread for the new issue may get more answers cause its more generic.
It is that bad?
OK Short Update,
I've been able to install the OTA Update using Recovery. I got the update notification then downloaded the update. I opened the zip file and modified the updater-script to bypass CID check adding || 1 == 1 (So the CID check will always return true then I click ok on the System Update notification.
Phone rebooted and in recovery I selected install ZIP from sdcard. Pointed to the OTA update and everything went fine.
So I'm unrooted now but i'm still S-Off and because I installed the OTA update over a rooted nandroid backup, SuperUser is still in the rom and I can't delete it.
I'm still not able to return the phone for repair and still don't know what to do.
And the last problem, Wifi doesn't work anyore on my phone. It says wifi error and I can't get the mac Adress on Info about your phone, nor the bluetooth address.
Any solution?
Any news about that? I'm still stuck with stock rom but no wifi and bluetooth and can not delete superuser from apps drawer. Thanks
You cannot delete superuser as its embedded in your ROM. Superuser doesn't magically appear when you get root, its put on ROMs for your use or put on during the root process for certain devices.
Now anyways, onto your predicament. You should search your vendors website for an update RUU (eg. vodafone website) or in the android development section. Once you find one to your liking you just follow the Vision Wiki guide to unrooting. There really is no easier way to remove all the aspects of a root without following those steps. Ultimately following that guide will help you restore your Desire Z/G2 to a normal one with no superuser, superCID or secu-flag unlock.
Just a side note, it will be rather difficult for you to obtain a stock ROM from any other user because since they don't have root access or clockworkmod they can't make you a backup of their 1.72 based ROMs.
if i manually update from 4.0.4 takju to the jb 4.1.1 through cmw, will i still get OTA updates in future. also, if the i do the update, will it lock the bootloader and erase cwm? thanks
wasya152 said:
if i manually update from 4.0.4 takju to the jb 4.1.1 through cmw, will i still get OTA updates in future. also, if the i do the update, will it lock the bootloader and erase cwm? thanks
Click to expand...
Click to collapse
OK to get a few things right here, you need to have stock recovery to install OTA, no it won't relock boot loader, yes it will erase CWM. Your rom needs to be 100% stock (including boot loader, kernel and radio aswell as rom and recovery).
The way I just went to 4.1.1 (takju) I was running the preview JB Google IO rom anyway so in CWM I reflashed that to undo any system changes I made. Then using Mskips nexus tool kit I used it to flash stock recovery and then BOOT (NOT FLASH) to CWM. Find the update and flash it. Before you do all this use titanium to back up your stuff, do a nandroid and get voodoo OTA root keeper so you get root back after the update.
Then using the tool kit again I used it to flash CWM back. Then your done. I won't give further instructions but for further reading efrant has very good posts about this stuff, mskip has very good instructions on his tool kit in the thread
http://forum.xda-developers.com/showthread.php?t=1419170
http://forum.xda-developers.com/showthread.php?t=1392310
Sent from my Galaxy Nexus
i'm still a little confused. my phone is completely stock. it's a takju 4.0.4. i don't want to wait for the OTA for jb 4.1.1. i was going to use the nexus tool kit to unlock the bootloader ( i believe that's required to boot it into cwm) then run the OTA update that people posted for my version to update it. I don't care about keeping cwm or bootloader, just want the update now and keep the phone still stock. i also want to make sure that i'll get OTA updates in the future. It looks like I can just boot it into cwm without flashing it, so that's what i'm going to do.
wasya152 said:
i'm still a little confused. my phone is completely stock. it's a takju 4.0.4. i don't want to wait for the OTA for jb 4.1.1. i was going to use the nexus tool kit to unlock the bootloader ( i believe that's required to boot it into cwm) then run the OTA update that people posted for my version to update it. I don't care about keeping cwm or bootloader, just want the update now and keep the phone still stock. i also want to make sure that i'll get OTA updates in the future. It looks like I can just boot it into cwm without flashing it, so that's what i'm going to do.
Click to expand...
Click to collapse
can anyone confirm that i can just boot into custom recovery and apply the update zip and still keep everything stock?
wasya152 said:
can anyone confirm that i can just boot into custom recovery and apply the update zip and still keep everything stock?
Click to expand...
Click to collapse
Yeah you can but you need to unlock the boot loader to do it, which wipes your entire phone so back up any thing you want to keep like photos or music. When the bootloader is open you can just leave it and just lock it if you need to send for warranty. Or if you already have root but locked boot loader there is a free app to unlock it on play store
Sent from my Galaxy Nexus
The Gingerbread Man said:
Yeah you can but you need to unlock the boot loader to do it, which wipes your entire phone so back up any thing you want to keep like photos or music. When the bootloader is open you can just leave it and just lock it if you need to send for warranty. Or if you already have root but locked boot loader there is a free app to unlock it on play store
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
once, i update the file using the nexus toolkit to boot into custom recovery, once it updates, it will lock the bootloader and the phone will be back to stock right? or is the bootloader going to stay open.
also, will i still get future OTA updates if i just do the update by booting into recovery and not flashing cwm?
wasya152 said:
once, i update the file using the nexus toolkit to boot into custom recovery, once it updates, it will lock the bootloader and the phone will be back to stock right? or is the bootloader going to stay open.
also, will i still get future OTA updates if i just do the update by booting into recovery and not flashing cwm?
Click to expand...
Click to collapse
Once you unlock it the bootloader stays open until you choose lock I again. You can still get ota but remember you need the matching bootloader, kernel, radio and unmodified system and recovery. So just booting cwm is fine to apply and then after its applied the patch you can flash what ever you want again. I find its always a good idea to make a back up of a 100% stock rom and keep it on the pc just in case. This is all simple and quick with the tool kit
Sent from my Galaxy Nexus
The Gingerbread Man said:
Once you unlock it the bootloader stays open until you choose lock I again. You can still get ota but remember you need the matching bootloader, kernel, radio and unmodified system and recovery. So just booting cwm is fine to apply and then after its applied the patch you can flash what ever you want again. I find its always a good idea to make a back up of a 100% stock rom and keep it on the pc just in case. This is all simple and quick with the tool kit
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Hey, first, thanks for the replies. Second, if I unlock the bootloader to install update, make no other changes, meaning everything else is stock and the update is googles stock update, them once the update is done, can I run the toolkit again to lock the bootloader. Doing this will it bring my phone to same everything as a stock ota updated one? Or is me unlocking and then locking bootloader going to cause me to have a different version for the next ota
wasya152 said:
Hey, first, thanks for the replies. Second, if I unlock the bootloader to install update, make no other changes, meaning everything else is stock and the update is googles stock update, them once the update is done, can I run the toolkit again to lock the bootloader. Doing this will it bring my phone to same everything as a stock ota updated one? Or is me unlocking and then locking bootloader going to cause me to have a different version for the next ota
Click to expand...
Click to collapse
No worries its fine. Yes after you have successfully applied a stock OTA patch onto a stock rom then you are running the same as everyone. Their are minor regional differences, like takju and yakuto (what ever lol) toro, toro plus etc but flashing a ota patch from a different build won't work on a rom that doesn't match.
You can go to the Google developer site and search for the full ROM and you know definitely its 100% as its meant to be, the patches just write over the bits which change in updates. The thing to bear in MIMD about flashing the whole ROM from Google site is that it will wipe your entire phone
https://developers.google.com/android/nexus/images (keep looking through for the build you want and you can flash it using the flash tool. Back up your stuff like music photos etc first)
Sent from my Galaxy Nexus
Hello, first of all, I'm sorry for the noob question. I tried to search for the answer but I got more confused than when I started. I have rooted my SGS3 just to be able to use the Wifi hotspot, I'm not into other modifications or anything, I just wanted the hotspot. Now the phone wants me to update through OTA, but of course it's not working. My questions are:
-Should I go back to stock (following the videos from qbking77) and then apply the OTA? Is it safe?
-Should I go back to stock and MANUALLY update the phone?
-Is LF9 the latest OFFICIAL update?
-Is there anything else I should consider?
I don't care about custom roms or any other modifications, I like the phone vanilla BUT with the hotspot enabled. I was looking through a lot of videos and threads but I could't find a good answer.
Thanks in advance!
The latest official release is LJ7. You have a couple of options to get the update.
- You could go back to stock to accept the update. The key is that you need the stock recovery installed for the update to work normally. You could then reflash the custom recovery if you like.
- You could manually apply the update from the recovery. If you phone is bugging you to apply the update it then you probably already have the update ZIP in your \cache\ folder. You could also download it. The normal OTA update will only work in the CWM recovery (not TWRP) but there are modified versions posted here that remove the check to allow it to work from TWRP.
Other considerations: If you are using the WiFi Tether for Root users it will no longer work one you update to Jelly Bean (LJ7). You will need to unisntall that and get version that was modified by TrevE.
m20120 said:
The latest official release is LJ7. You have a couple of options to get the update.
- You could go back to stock to accept the update. The key is that you need the stock recovery installed for the update to work normally. You could then reflash the custom recovery if you like.
- You could manually apply the update from the recovery. If you phone is bugging you to apply the update it then you probably already have the update ZIP in your \cache\ folder. You could also download it. The normal OTA update will only work in the CWM recovery (not TWRP) but there are modified versions posted here that remove the check to allow it to work from TWRP.
Other considerations: If you are using the WiFi Tether for Root users it will no longer work one you update to Jelly Bean (LJ7). You will need to unisntall that and get version that was modified by TrevE.
Click to expand...
Click to collapse
Thanks for the help! Yes I think I have CWM on. I followed a video from qbking77 (I think) and installed it. Or at least it was something like custom recovery or something the like. Do you think I can apply the update directly from CWM? Or it would be easier (and cleaner) to go back to stock recovery and do it "officially". Also, are all stock recovery the same? I ask because there are some different files in qbking77's website. I don't know if the version of stock recovery matters at all. Also, thanks for the tip on the modified app.
You probably have CWM recovery. You only need the stock recovery if you want to let the phone apply the OTA (i.e. it prompts you to accept the update). You also have to have the phone in a completely stock state (root is ok). You can not have any modified system files.
If you want to apply the update manually you can also do that with CWM. You can copy the file (something like eec955eb4a5b.update_SPH-L710_LI3_to_LJ7.zip) from the \cache folder to the internal sdcard of your phone. You can then boot into CWM recovery and apply flash the ZIP update. You must have stock system files in order for this update to work also.
If you have modified any system files (I removed the system version of Swype) you have to get back to stock in either case.
m20120 said:
You probably have CWM recovery. You only need the stock recovery if you want to let the phone apply the OTA (i.e. it prompts you to accept the update). You also have to have the phone in a completely stock state (root is ok). You can not have any modified system files.
If you want to apply the update manually you can also do that with CWM. You can copy the file (something like eec955eb4a5b.update_SPH-L710_LI3_to_LJ7.zip) from the \cache folder to the internal sdcard of your phone. You can then boot into CWM recovery and apply flash the ZIP update. You must have stock system files in order for this update to work also.
If you have modified any system files (I removed the system version of Swype) you have to get back to stock in either case.
Click to expand...
Click to collapse
Ok, so the only thing I did is install the wfi hotspot app after rooting, I didn't touch anything else. So I shouldn't worry about system files, right?
You mentioned that since my phone is bothering me with updates notifications, it is because it already downloaded the update into the "cache," right? So I should just find that file, put it in the sdcard and flash from CWM? It's really that easy?
nahuelarg86 said:
Ok, so the only thing I did is install the wfi hotspot app after rooting, I didn't touch anything else. So I shouldn't worry about system files, right?
You mentioned that since my phone is bothering me with updates notifications, it is because it already downloaded the update into the "cache," right? So I should just find that file, put it in the sdcard and flash from CWM? It's really that easy?
Click to expand...
Click to collapse
It is probably there if it is prompting you to update.
One step that I almost forgot about. When you do the update you will reinstall the script that detects a custom recovery and it will install the stock recovery.
There is a good procedure here that gives you the step by step process, including flashing the Team Epic file to prevent the updated ROM from restoring the stock recovery. If you do not flash the Team Epic file the update will still be successful and you will still have root, you will just end up with the stock recovery.
The process is really easy and it is the one that I used to update from LI3 to LJ7.
I currently have my bootloader unlocked, S-OFF, TWRP recovery, and rooted stock verizon software (Most recent mini-update pushed from VZW around Thanksgiving). My question is whether my current configuration will allow me to accept the new 4.3 OTA update from verizon when it starts to roll out. Is custom recovery going to be a problem? I haven't messed with the stock software, other than adding superuser app. Thanks.
For all the other updates, stock recovery was necessary. I wouldn't see why the 4.3 update would be any different.
I still suggest waiting until the devs take the update and make a flashable Rom from it.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
kdj67f said:
For all the other updates, stock recovery was necessary. I wouldn't see why the 4.3 update would be any different.
I still suggest waiting until the devs take the update and make a flashable Rom from it.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Is it possible to flash or adb stock recovery back?
Yes, the stock recovery and files are posted here. I have reflashed the stock recovery and ota'd myself. As easy as flashing a custom recovery. You might want to read all the other ota threads here...
Sent from my HTC6500LVW using XDA Premium 4 mobile app
flyinfool2 said:
Is it possible to flash or adb stock recovery back?
Click to expand...
Click to collapse
yes, very.
search you'd find this thread.. http://forum.xda-developers.com/showthread.php?t=2485319
there you find this:
"
Arrow 1.10.605.10 Stock [Firmware/Radio] [Kernel] zips
Full Firmware, Boot.img, and Radio updates
Ok, so you now have the latest stock software.
You likely want to have the firmware and radios updated that came along with the OTA.
If that is the case, I have supplied the firmware.zip here that will update the firmware and radios to the latest version.
How to flash the Full firmware/radio zip:
Separate Radios, Recoveries, and Kernels are also available below,
if you are on a custom rom or don't need/want the full firmware!
Download the appropriate firmware version for your stock based rom:
1.10.605.10 firmware.zip
1.10.605.15 firmware.zip
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip
It will say that the update did not finish, to flush again, repeat the above step:
fastboot flash zip firmware.zip
Quote:
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot!
The bar will only fill up to 100% once you type the following command:
fastboot reboot-bootloader (this reboots the device to bootloader)
That's it, you're done. You can now reboot and will be running the latest firmware and radios.
If you have any questions or issues, let me know.
Stock m7vzw
Kernels, Radios, Recoveries!
Kernel Only!!!__>>>>>>
(included in the above firmware zips as well, if you flash those, you do not need this too)
****In case anyone wants just the stock kernel and modules:
1.10.605.10 stock kernel
1.10.605.15 Insecure stock kernel - R/W enabled
Flash in Recovery, wipe cache and dalvik, reboot.
Radio Only!!!__>>>>>>
(included in the above firmware zips as well, if you flash those, you do not need this too)
I went ahead and made these baseband zips as well.
Basebands/Fastboot Flashable:
These radio.zips must be flashed the same way as the firmware zip at the top of this post.
With the exception that it will not need to be reflushed/reflashed a second time during the process."
http://www.androidfilehost.com/?fid=23212708291682230 - flash in recovery
Great info, Thanks!
flyinfool2 said:
I currently have my bootloader unlocked, S-OFF, TWRP recovery, and rooted stock verizon software (Most recent mini-update pushed from VZW around Thanksgiving). My question is whether my current configuration will allow me to accept the new 4.3 OTA update from verizon when it starts to roll out. Is custom recovery going to be a problem? I haven't messed with the stock software, other than adding superuser app. Thanks.
Click to expand...
Click to collapse
You have to have stock recovery to OTA. But can I ask why you'd want to OTA anyway? Devs will have a rooted stock zip in no time after the update is pushed. There is literally no reason to OTA. A lot of ppl, for whatever the reason, think it's important to have the official OTA. If you want stock unrooted backups I get that. I do that sometimes in case of emergencies. Other than that you really don't need to OTA. You can reflash stock recovery easy enough and OTA if you want but I wouldn't. Since you have an unlocked bootloader and all then at most you would have to flash superuser again but the general rule is never OTA.
---------- Post added at 09:25 AM ---------- Previous post was at 09:24 AM ----------
andybones said:
yes, very.
search you'd find this thread.. http://forum.xda-developers.com/showthread.php?t=2485319
there you find this:
"
Arrow 1.10.605.10 Stock [Firmware/Radio] [Kernel] zips
Full Firmware, Boot.img, and Radio updates
Ok, so you now have the latest stock software.
You likely want to have the firmware and radios updated that came along with the OTA.
If that is the case, I have supplied the firmware.zip here that will update the firmware and radios to the latest version.
How to flash the Full firmware/radio zip:
Separate Radios, Recoveries, and Kernels are also available below,
if you are on a custom rom or don't need/want the full firmware!
Download the appropriate firmware version for your stock based rom:
1.10.605.10 firmware.zip
1.10.605.15 firmware.zip
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip
It will say that the update did not finish, to flush again, repeat the above step:
fastboot flash zip firmware.zip
Quote:
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot!
The bar will only fill up to 100% once you type the following command:
fastboot reboot-bootloader (this reboots the device to bootloader)
That's it, you're done. You can now reboot and will be running the latest firmware and radios.
If you have any questions or issues, let me know.
Stock m7vzw
Kernels, Radios, Recoveries!
Kernel Only!!!__>>>>>>
(included in the above firmware zips as well, if you flash those, you do not need this too)
****In case anyone wants just the stock kernel and modules:
1.10.605.10 stock kernel
1.10.605.15 Insecure stock kernel - R/W enabled
Flash in Recovery, wipe cache and dalvik, reboot.
Radio Only!!!__>>>>>>
(included in the above firmware zips as well, if you flash those, you do not need this too)
I went ahead and made these baseband zips as well.
Basebands/Fastboot Flashable:
These radio.zips must be flashed the same way as the firmware zip at the top of this post.
With the exception that it will not need to be reflushed/reflashed a second time during the process."
http://www.androidfilehost.com/?fid=23212708291682230 - flash in recovery
Click to expand...
Click to collapse
Well damn andy. Dropped the knowledge bomb on him
Yeah it's not worth OTA'ng, especially given the experience vzw S4 owners had with getting their root exploits and such closed...
Flashable OTA update question
So my One is unlocked and S-off. I manually updated to firmware version .15, however, my ROM is still version .10. (I could not download the version .15 ROM version as it was taking way too long) I keep getting the constant nag about the software update. I want to stay current, but dont want to lose ROOT or worse.
First, how do you use a flashable rom file to update your current rom? I dont what to have to backup and flash a new rom and restore all my settings everytime if I can avoid it. Is there a way to just update like what the OTA does?
Here was my thought. I would make a backup and clean install the current version (.15) of a custom, stock ROM. This would prevent future OTA's correct? Then, I would just update with flash-able files as they are released to keep my ROM up to date and ROOT privileges, etc safe?
Or would it be possible to update my current .10 ROM to .15, disable all OTA's and then flash updates as they are released?
BreakingVZW said:
You have to have stock recovery to OTA. But can I ask why you'd want to OTA anyway? Devs will have a rooted stock zip in no time after the update is pushed. There is literally no reason to OTA. A lot of ppl, for whatever the reason, think it's important to have the official OTA. If you want stock unrooted backups I get that. I do that sometimes in case of emergencies. Other than that you really don't need to OTA. You can reflash stock recovery easy enough and OTA if you want but I wouldn't. Since you have an unlocked bootloader and all then at most you would have to flash superuser again but the general rule is never OTA.
---------- Post added at 09:25 AM ---------- Previous post was at 09:24 AM ----------
Click to expand...
Click to collapse
This is my wifes phone, so she is not concerned with having any custom operating ROM. For me however, I have always been a hacker at heart, and I love to run different ROMS on my own phone. For her phone, I just want the ability to run the most recent stock software, with root, so that I can make backups and freeze unnecessary apps to my liking. If a rooted stock zip is just around the corner, then I see no need to take the OTA update as you stated. Thanks for the insight. I just didn't realize that I could get the same result (an updated stock, rooted update) without taking the OTA. I appreciate the help! :good:
What can I do in the meantime to prevent my wife from accidentally accepting the OTA (it just began pushing on her phone)? I know the update wont take without stock recovery installed, but is there an easy way to prevent the repeated download and prompt for install?
EDIT: I found another thread with a flashable file to stop OTA...thanks all
For whatever reason I can't get the OTA to apply. It gets about 25 to 30% of the way through the installation and then gives me the red Triangle/Exclamation point. I first tried after flashing back to the 1.10.605.15 recovery and after that failed I flashed the full 1.10.605.15 firmware with the same result. Any ideas?
wpsantennas said:
For whatever reason I can't get the OTA to apply. It gets about 25 to 30% of the way through the installation and then gives me the red Triangle/Exclamation point. I first tried after flashing back to the 1.10.605.15 recovery and after that failed I flashed the full 1.10.605.15 firmware with the same result. Any ideas?
Click to expand...
Click to collapse
I have that. Haven't figured it out yet either. I did the stock recovery too. s-off and unlocked.
Had the same exact problem as WPSantennas and paganhobbit. Endded up using this thread http://forum.xda-developers.com/showthread.php?t=2475216 to return to S-On, Locked Bootloader at 1.10.605.8 (For mine to work right on this tutorial I had to skip the 2nd 'fastboot oem rebootRUU' after failing for it work.) I think the latest OTA doesn't really like if you have modified or deleted their stock bloat apps for some reason. IMO, The update is not impressive at all and I'd advise to stay at 4.2.2 but this is may be good to do if you want to bump to KitKat in the future. Hope this helps!
EDIT: Here's the link to the RUU I used since the link on the original was dead: http://www.android-edge.com/Login/uploads/PN017IMG_M7_1.10.605.8.zip
I ended up RUU-ing as well, going back to .10. Then it updated to .15 and the 4.3 update without a problem. I didn't re-lock or go S-On to do this. I had tried three different "official stock recovery" files I found, but 4.3 wouldn't update successfully with any of them.
A new problem is it doesn't seem to want to remember my WiFi connections for some reason now. If I go out of range and come back, I have to re-enter the WPA2 key all over again. I suspect it's Verizon's ploy to make me use more data
I recently unlocked the bootloader of an HTC One (M8) running Kitkat, installed TWRP then flashed a .ZIP file to root the phone. Now Lollipop has been released there's an OTA available on the phone but I'm not able to update through it. I've seen different posts all over the place about how you have to just install the stock recovery or how you have to use an RUU or how you have to use a NANDroid backup so the opinions are quite conflicting.
I basically just want the phone to run the stock unrooted version of Android so I'm able to perform the official OTA updates to Lollipop so how do I go about this? Any help is greatly appreciated!
Charlular said:
I recently unlocked the bootloader of an HTC One (M8) running Kitkat, installed TWRP then flashed a .ZIP file to root the phone. Now Lollipop has been released there's an OTA available on the phone but I'm not able to update through it. I've seen different posts all over the place about how you have to just install the stock recovery or how you have to use an RUU or how you have to use a NANDroid backup so the opinions are quite conflicting.
I basically just want the phone to run the stock unrooted version of Android so I'm able to perform the official OTA updates to Lollipop so how do I go about this? Any help is greatly appreciated!
Click to expand...
Click to collapse
No need to unroot. You just need a stock recovery.
Charlular said:
I basically just want the phone to run the stock unrooted version of Android so I'm able to perform the official OTA updates to Lollipop so how do I go about this? Any help is greatly appreciated!
Click to expand...
Click to collapse
Let me try to clarify the confusion based on my experience with the Lollipop OTA update. First, you need to remember that, during the OTA update, the software checks for two things: 1) the version of the recovery; and 2) whether any system files has been modified (described in my earlier post).
As a result, you only need stock recovery (from 4.4.4 or 5.0.1) to initiate the OTA update (as mentioned by the other poster). If no system files were altered as a result of your root access, your OTA should finish without errors.
However, root itself and what people do after they have root access often mean some system files were altered. Hence, they need to use either RUU or TWRP backup to restore they all files back to the factory version.
Finally, as for RUU vs. TWRP:
The RUU or TWRP version must match that to your carrier version of M8. The RUU is the better option, but not available for all carrier versions. When RUU is not available, people rely on TWRP nandroid backup generated by other users.
Bottom line or my advice:
First do a TWRP backup before you start anything. If anything goes wrong, you can always revert back to the working status as it is now.
To begin, go back to stock recovery, and see if the OTA update will go through. If not, you will see red triangle. Then hold Vol + and tap power button once to see the error messages. See my post above. If you ran into the same error as I did, you'll know what to do (RUU or TWRP backup to return to stock).
ikeny said:
Let me try to clarify the confusion based on my experience with the Lollipop OTA update. First, you need to remember that, during the OTA update, the software checks for two things: 1) the version of the recovery; and 2) whether any system files has been modified (described in my earlier post).
As a result, you only need stock recovery from (4.4.4 or 5.0.1) to initiate the OTA update (as mentioned by the other poster). If no system files were altered as a result of your root access, your OTA should finish without errors.
However, root itself and what people do after they have root access often mean some system files were altered. Hence, they need to use either RUU or TWRP backup to restore they all files back to the factory version.
Finally, as for RUU vs. TWRP:
The RUU or TWRP version must match that to your carrier version of M8. The RUU is the better option, but not available for all carrier versions. When RUU is not available, people rely on TWRP backup generated by other users.
Bottom line or my advice:
First do a TWRP backup before you start anything. If anything goes wrong, you can always revert back to a work status as it is now.
To begin, go back to stock recovery, and see if the OTA update will go through. If not, you will see red triangle. Then hold Vol + and tap power button once to see the error messages. See my post above. If you ran into the same error as I did, you'll know what to do (RUU or TWRP backup to return to stock).
Click to expand...
Click to collapse
A very well-worded answer