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)
I have a Verizon Samsung galaxy S5 G900V in which I am locked out of, im trying to flash CWM recovery to because I am locked out and the stock recovery will not allow me to install any zips or anything that I need to install. When I do try to install anything I get “signature verification failed” and “wrong foot header”. I have tried ABD also but it will only go into Sideloader mode and those commands are limited so I cannot delete the passcode file. A friend told me my variant had a locked bootloader and I need that unlocked before I can flash it but, I can’t unlock It or root it because I don’t have access to the phone. I have really important files on here, stuff that is beyond important. Is there any other way to get into the phone or is there something I can do to flash the CWM recovery?
Thanks, Addison
Hi Guys
Just got a used VZW G3, it currently has software version VS98512B. I am confused if I need to restore it to an earlier version or if there is a way to root and flash the latest recovery to start flashing a debloated rom?
I know the previous owner had rooted before and the recovery does say modified but I think it is all the stock recovery now as I could not get into TWRP or anything.
What should I be doing to avoid bricking lol
It does tell me a software update is available but I keep canceling
Thanks
Check with app root checker and if not rooted then use king root for rooting and flashify for latest recovery TWRP 2.8.7.0
but i cant remember how to install stock rom with twrp or how to remove twrp to go stock
i updated to latest twrp and tried to install cygon 13 i get error booloader unknown?
im on stock 5.1 how do i root?
kingroot is the DEVIL it rooted my phone but installed enough junkware to choke a horse, or a MT2 in this case so i reinstalled stock
i fastboot installed recovery it shows it installs it i calick fastboot reboot and try to get into the recovery i just installed and NOTHING i cant get in it
incase anyones wondering i unlocked the bootloader like first day i got it and it shows as "unlocked" so i think bootloader is still unlocked
Stickies in the general forum are your friend. There are a couple of posts in there that will explain how to get to stock ROM then install TWRP and use it to root.
Sent from my MT2L03 using XDA-Developers Legacy app
I'm having major problems with TWRP, and I need help.
I have a Samsung Galaxy S4 with a properly unlocked bootloader (MDL), rooted, that has had a working version of TWRP 2.8.7.0 and running an older version of Cyanogen.
I'm overhauling the phone, so the first thing I tried to do was to update TWRP.
Since TWRP v2.8.7 supports flashing itself, I booted into recovery and flashed the TWRP update (v3.2.1.0) directly through TWRP. No errors that I saw.
But when I try to boot into recovery, I now get "System Software Not Authorized By AT&T Has Been Found On Your Phone". Fortunately, I can still boot normally - it's only recovery that I'm locked out of.
In trying to fix this, I tried re-flashing TWRP with three different methods:
1. I tried to flash TWRP again through the TWRP app. But I get "Flash Failed".
2. I tried Odin and got "FAIL! (Auth)"
3. I tried flashing v3.2.2.0 using the dd method. This I was able to do without any errors, but I'm still locked out of recovery mode with that same "System Software Not Authorized By AT&T Has Been Found On Your Phone" error.
Help?
Try connect to computer and execute:
adb reboot bootloader
fastboot flash recovery twrp-xxxx-xxx.img
Everything should be good to go.
Note: ALL TWRP settings will be reset.
HippoInWindow said:
Try connect to computer and execute:
adb reboot bootloader
fastboot flash recovery twrp-xxxx-xxx.img
Everything should be good to go.
Note: ALL TWRP settings will be reset.
Click to expand...
Click to collapse
ADB works fine for me, but fastboot does not. It says "waiting for any device". From what I understand, this is a common issue with Samsung phones. I'm using Windows 10, if that helps.
However, I came across a bug report for TWRP here, that reports the exact same problem from 3.0.0.0, and it's still open. That tells me that this may be a general issue with TWRP that they never bothered to fix.
So on a hunch, I tried re-flashing v2.8.7 using the dd method (since that's the only one I can get to work). And SUCCESS! I can now boot into recovery again!
So here's what I need to know:
1. Is there any way to get the latest version of TWRP to work on this phone?
2. Is it safe to flash a current version of LineageOS using this version of TWRP (v2.8.7)?
I'm really wary about that second question, because the last thing I want to do is brick my phone because an old version of TWRP doesn't know how to work with a new version of Lineage/Android. (This phone currently has KitKat on it)
You need Rashr to do this. You can find this app on the Google Play Store which can flash images in your system.
1. This version of TWRP should be able to flash modern LineageOS.
2. Using the above method provided should get you up and running the latest TWRP.
HippoInWindow said:
You need Rashr to do this. You can find this app on the Google Play Store which can flash images in your system.
1. This version of TWRP should be able to flash modern LineageOS.
2. Using the above method provided should get you up and running the latest TWRP.
Click to expand...
Click to collapse
I finally found an explanation and solution - it would appear that TWRP 3.x does not have the Loki exploit applied. So nothing 3.0+ will work unless it's been Lokied.
Fortunately, the current versions can be Loki patched, so once that's done, they'll install and work properly. Whew!