Hello,
I am not new to the process of rooting, unlock bootloader or flashing ROM. But, this is the first time that I need to root a HTC phone, the HTC One M8. I don't usually care much for stock ROM, but this is my girlfriend's phone and I think stock ROM works best for her. It is more stable, even though it will be a bit slow and has a lot of bloatware. I plan to root it then manually go in and disable most of the bloated apps. Then, I will install Xposed Module and add some useful modules. However, the release of Lollipop is around the corner. I want to know if rooting it will affect the ability of doing OTA upgrade.
Base on what I have read, in order to root, you have to unlock the bootloader, then replace the stock recovery with custom recovery like CWM/TWRP, then you flash the supersu.zip file to grant root permission. I am familiar with the process, but I am a bit confused at this part. Since we use a custom recovery to flash the supersu.zip file, it is more likely that OTA upgrade will fail since most OTA upgrade rely on stock recovery.
1/ Then, how do I upgrade to Lollipop 5.0 once I have rooted the phone?
The current ROM is Kitkat I think.
2/ I mean, is there a stock recovery file that I can flash back to replace the custom recovery once the phone has been rooted? or the OTA process will work with the custom recovery, which is very unlikely in my opinion.
3/ Also, once I have upgraded to Lollipop, I can do the same process to gain root again, (flash custom recovery, then flash supersu.zip to gain root). Is that correct?
4/ Is there any other method of gaining root without losing OTA update? As long as I don't have to wipe everything and restore it for every OTA update. I am fine with it.
Please let me know. Thank you all for your help.
After you root, flash back your stock recovery. As long as you are running stock the ota will attempt to download. Even when running non-stock recovery - what will happen is the ota will download and when you accept the update the phone will reboot into your custom recovery and the update won't be applied because the ota relies on the stock recovery being there.
So anyway, you can root, replace custom recovery back with stock and allow the update. You will most likely loose root once the update is applied, but then as long as there are custom recoveries available for the new android version you can flash back to custom recovery, reroot and you should be set.
I did this for a while, but the downside is that if SuperSU updates (or whichever root method you use) and requires a bin update, you won't be able to apply the root bin update unless you are running the custom recovery.
Hope that makes sense, typing from my phone while on a train.
What I do is this
Unlock Bootloader via HTC DEV website.
Dl a custom recovery I prefer TWRP Recovery flash that via Fastboot.
Then boot into custom recovery on your phone and create a New backup of the stock rom b4 you install SuperSU for root, name it something like (Stock untouched) .
Then flash superSU update zip in recovery.
Once superuser is working do what you want.
Note: I'd go ahead and find and Dl the stock recovery and keep it on hand for when you ready to go back Stock for the OTA update.
Go back to stock
Boot into custom recovery wipe system /data/cache. Then restore the Stock (untouched) backup you made.
Fastboot flash the stock recovery back.
Then relock Bootloader and now you back to Stock and ready to do the OTA update.
Note : this is what I do, everybody got their own way of doing things
Sent from my HTC One_M8 using Tapatalk
tommy_riley said:
After you root, flash back your stock recovery. As long as you are running stock the ota will attempt to download. Even when running non-stock recovery - what will happen is the ota will download and when you accept the update the phone will reboot into your custom recovery and the update won't be applied because the ota relies on the stock recovery being there.
So anyway, you can root, replace custom recovery back with stock and allow the update. You will most likely loose root once the update is applied, but then as long as there are custom recoveries available for the new android version you can flash back to custom recovery, reroot and you should be set.
I did this for a while, but the downside is that if SuperSU updates (or whichever root method you use) and requires a bin update, you won't be able to apply the root bin update unless you are running the custom recovery.
Hope that makes sense, typing from my phone while on a train.
Click to expand...
Click to collapse
Ok, thank you for the reply. That clears up a little. I can just flash stock recovery every time I want to update. I was able to find a thread that has all the stock recovery file. I have a quick question. Does any version of stock recovery will work? or you want the one that match your current stock recovery. Also, what is Non-WWE-Recoveries?
Here is the thread with all the stock recoveries:
http://forum.xda-developers.com/showthread.php?t=2701376
Let me know. Thank you
scoot0073 said:
What I do is this
Unlock Bootloader via HTC DEV website.
Dl a custom recovery I prefer TWRP Recovery flash that via Fastboot.
Then boot into custom recovery on your phone and create a New backup of the stock rom b4 you install SuperSU for root, name it something like (Stock untouched) .
Then flash superSU update zip in recovery.
Once superuser is working do what you want.
Note: I'd go ahead and find and Dl the stock recovery and keep it on hand for when you ready to go back Stock for the OTA update.
Go back to stock
Boot into custom recovery wipe system /data/cache. Then restore the Stock (untouched) backup you made.
Fastboot flash the stock recovery back.
Then relock Bootloader and now you back to Stock and ready to do the OTA update.
Note : this is what I do, everybody got their own way of doing things
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Hello,
I understand your concept for going back to stock. But, I don't get why I have to relock the bootloader. What I mean is, is that necessary for the OTA to work? I thought you only need the stock recovery for the OTA to work. Also, once you have done OTA update, and you want to root the phone again. The downsize is you have to unlock the bootloader again, which will wipe the phone completely and you will have to restore everything, which wastes times.
I like the idea of just restoring the stock recovery, do the OTA upgrade, then flash custom recovery to gain root again. I don't mind repeating that process for each update. But to relock/unlock the bootloader, having to wipe everything is a hassle. Please clarify. Thank you for your help.
I don't believe you need to relock boot loader for OTA. You do need locked bootloader for RUU full install, but only if S-ON (s-off you can do RUU w/boot loader locked or unlocked) - but that's not what were talking about here - OTA w/ unlocked boot loader = All good.
I believe WWE recovery refers to Europe versions of the recovery, so if in US go for the non-WWE.
I'd stick with trying to lineup stick recovery versions with version of OS software you have installed - so if you are running stock 4.4.2 or 4.4.3 grab the latest stocl recovery available.
vi6s said:
Hello,
I understand your concept for going back to stock. But, I don't get why I have to relock the bootloader. What I mean is, is that necessary for the OTA to work? I thought you only need the stock recovery for the OTA to work. Also, once you have done OTA update, and you want to root the phone again. The downsize is you have to unlock the bootloader again, which will wipe the phone completely and you will have to restore everything, which wastes times.
I like the idea of just restoring the stock recovery, do the OTA upgrade, then flash custom recovery to gain root again. I don't mind repeating that process for each update. But to relock/unlock the bootloader, having to wipe everything is a hassle. Please clarify. Thank you for your help.
Click to expand...
Click to collapse
Lol.. Yea if S-On relock Bootloader for RUU.
But no you don't need to relock the Bootloader for OTA updates S-On or s-off Sorry for the confusion I was going back n forth with another user and got you mixed up.
Sent from my HTC One_M8 using Tapatalk
vi6s said:
Ok, thank you for the reply. That clears up a little. I can just flash stock recovery every time I want to update. I was able to find a thread that has all the stock recovery file. I have a quick question. Does any version of stock recovery will work? or you want the one that match your current stock recovery.
Click to expand...
Click to collapse
You need the stock recovery that correspond to your stock software. AT&T software is x.xx.502, and I don't see any corresponding recoveries in exocet's stock nandroid collection, but 1.12.502 and 1.58.502 stock recoveries are posted here: http://forum.xda-developers.com/att-htc-one-m8/development/att-stock-backups-recoveries-otas-t2855966
Also, while eluded to above, it should be clearly stated, no /system files may be modified, in order for OTA to install. So depending on what you intend to change with root, you will either need to put it back to stock (if you modded any system files), restore the stock ROM with a nandroid you made, or a stock ROM posted on XDA.
Alternately, you can quickly return to stock by RUU. Although you either need to relock the bootloader or have s-off to run the RUU. And RUU will also wipe the phone.
So to sum it up, in order to OTA you need:
/system to be returned to stock (stock ROM)
stock recovery
Unlocked bootloader is OK
Root is okay (you will lose root after the OTA)
With all the hype on the lp launch, I just realized I have no idea what to do : I got the rom through xpirifirm, and I'm just sitting there like "now what?"
Originally when I got the phone, I created a KK pre-rooted rom and used that on my phone, later on down the line I unlocked the boot loader to use a custom kernel and try different roms, but the pre-rooted rom how-to says it's for "locked" bootloader only, for now I figure I should be fine making the rom following the same process and then flashing the resulting zip to my phone, but I have a few questions :
is this the proper way to do it on UB ? to create a prerooted rom and use the zip file to flash the LP update ?
will I keep my root if I do this ? (I'll use the latest SU binary)
will I have recovery ? (I'll use the latest dual recovery)
I just updated my Verizon GS4 to 5.0.1 using the OTA updates and I can now boot into both the recovery and download modes. If I can boot into these what's stopping me from just flashing a new ROM in the download mode (it explicitly says this mode is used to install a custom OS) or applying an update from my external storage in the recovery mode? I believe the recovery mode was how I flashed new roms on previous devices. When I was on Jellybean I don't remember having these options (or at least the recovery mode had far fewer options in it), but now that I do whats stopping me from using them to obtain custom roms and or root?
peterfran2112 said:
I just updated my Verizon GS4 to 5.0.1 using the OTA updates and I can now boot into both the recovery and download modes. If I can boot into these what's stopping me from just flashing a new ROM in the download mode (it explicitly says this mode is used to install a custom OS) or applying an update from my external storage in the recovery mode? I believe the recovery mode was how I flashed new roms on previous devices. When I was on Jellybean I don't remember having these options (or at least the recovery mode had far fewer options in it), but now that I do whats stopping me from using them to obtain custom roms and or root?
Click to expand...
Click to collapse
If you took the OTA update to Lollipop 5.0.1 you are locked into the OC1 bootloader.
Unfortunately there still is not a ROOT exploit available for OC1. Also, you can not revert to a previous level ROM or load a custom ROM with OC1.
For those that did not take the OTA there is a workaround to update to Lollipop 5.0.1 and stay on the NK4 Boot Loader
http://forum.xda-developers.com/gal...-to-update-to-i545oc1-5-0-1-keeproot-t3096558
Using this process would have allowed you to downgrade or install other ROMS.
You should never take a OTA update until you verify that a ROOT process is available or a workaround is available.
Hi, I am new and I have rooted my z5C of version 32.2.A.0.305 - 6.0.1 and customized kernel (https://forum.xda-developers.com/z5...omized-stock-kernel-32-2-0-305-6-0-1-t3477464) and TWRP. I feel some battery drain issues and would like to flash back the stock kernel to see can it be solved.
1. Is it just flash back the stock boot.img by adb is fine?
2. I changed some systems files, e.g. fonts and host files etc. I have removed other apps need root, can the changed system files - fonts and host files keep using without problems after I flashed the stock boot.img?
3. Will the TWRP removed after I flash back the stock boot.img by adb
Thanks
If you unroot, flashing back to the stock boot.img should be fine. All configurations that you have set before should remain the same unless they require root, in which they won't work at all. Also, reverting back to stock boot.img would remove DRM features and TWRP unless you get a custom built boot.img.
dlee390 said:
If you unroot, flashing back to the stock boot.img should be fine. All configurations that you have set before should remain the same unless they require root, in which they won't work at all. Also, reverting back to stock boot.img would remove DRM features and TWRP unless you get a custom built boot.img.
Click to expand...
Click to collapse
thanks! So, after I flashed the stock boot.img, I will lose TWRP.
1. would the recovery return to stock or I will have no recovery?
2. If I re-root again in future I just flash the rooted kernel boot.img by adb is fine?
au.terrykp said:
thanks! So, after I flashed the stock boot.img, I will lose TWRP.
1. would the recovery return to stock or I will have no recovery?
2. If I re-root again in future I just flash the rooted kernel boot.img by adb is fine?
Click to expand...
Click to collapse
If you return to stock, you would get the stock recovery and if you want to re-root you would have flash through adb.
Hello,
I have been trying to install Android 11 on my phone (Galaxy S9 SM-G960U1) for a while. I have realized that in order to flash new firmware onto my phone, it must be signed or the bootloader won't accept it. When I flash non-signed custom firmware, Odin returns an error about authorization.
Only OEMs/Carriers sign Stock ROMs / OTAs provided by them. ODIN works with Stock ROMs only.
To flash a Custom ROM you need TWRP or similar.
jwoegerbauer said:
Only OEMs/Carriers sign Stock ROMs / OTAs provided by them. ODIN works with Stock ROMs only.
To flash a Custom ROM you need TWRP or similar.
Click to expand...
Click to collapse
I cannot use TWRP without rooting my phone, which will take some time. I will use the Extreme Syndicate method (https://forum.xda-developers.com/ga...pment/root-t4041815/post81608559#post81608559) to root my phone, then install TWRP.
jwoegerbauer said:
Only OEMs/Carriers sign Stock ROMs / OTAs provided by them. ODIN works with Stock ROMs only.
To flash a Custom ROM you need TWRP or similar.
Click to expand...
Click to collapse
I tried using TWRP, but I got the error:
Security Error: This phone has been flashed with unauthorized software & is locked. Call your mobile operator for additional support. Please note that repair/return for this issue may have additional cost.