Hello,
I have rooted my HTC One m8(No S-OFF). It also has TWRP and it's on Android 5.0.1/HTC Sense 6
I googled and read about reverting to stock recovery and then doing an OTA upgrade of the OS. But I'd rather not go back to stock and then TWRP back again.
Is there any way or instructional to follow that can enable me to update to Android 6 whilst keeping TWRP and my root settings on.
Any help is appreciated
My experience, is that Marshmallow ROMs work fine on Lollipop firmware. I've been doing so since December, for no better reason than I've been too lazy to update my firmware.
So that means you should be able to just restore the proper Marshmallow TWRP backup for your version, and just run that without updating anything else. Although, be sure to leave yourself an escape plan, just in case it doesn't work (either your own LP backup, or be prepared to use one from the collection).
However, for best compatibility, you should really update your firmware. And doing so, either by flashing stock firmware, OTA, or RUU by "official" means (and official/signed means are what you need to use, since you are s-on) will by definition wipe out TWRP.
But honestly, flashing TWRP back to the phone is easy. You just download the .img file to your computer, than flash with a single fastboot command, with the phone connected. This is actually a fast and simple process, when compared to the other stuff you are talking about doing (restoring stock backup and recovery, OTA update).
Plus, since you are updating to Marshmallow, you'll also want to update to TWRP 3.0.2 anyway.
redpoint73 said:
My experience, is that Marshmallow ROMs work fine on Lollipop firmware. I've been doing so since December, for no better reason than I've been too lazy to update my firmware.
So that means you should be able to just restore the proper Marshmallow TWRP backup for your version, and just run that without updating anything else. Although, be sure to leave yourself an escape plan, just in case it doesn't work (either your own LP backup, or be prepared to use one from the collection).
However, for best compatibility, you should really update your firmware. And doing so, either by flashing stock firmware, OTA, or RUU by "official" means (and official/signed means are what you need to use, since you are s-on) will by definition wipe out TWRP.
But honestly, flashing TWRP back to the phone is easy. You just download the .img file to your computer, than flash with a single fastboot command, with the phone connected. This is actually a fast and simple process, when compared to the other stuff you are talking about doing (restoring stock backup and recovery, OTA update).
Plus, since you are updating to Marshmallow, you'll also want to update to TWRP 3.0.2 anyway.
Click to expand...
Click to collapse
Thanks redpoint73.
My chief motivation behind moving to Android 6 is a sound problem I've been having lately. I installed the AcousticX sound mod but when I listen to audiobooks, I hear a clipping sound sometimes.
The developer over @ AcousticX suggested a few things and one of which was making the switch to marshmallow.
thread: http://forum.xda-developers.com/showthread.php?p=68881108#post68881108
From some reading and your suggestions, I gathered the right way to go about this is, is to flash stock recovery(overriding twrp). Do an OTA upgrade(1.6 gb download/install) and afterwards reinstall TWRP and whatever else was previously done.
Am I correct in surmising this?
Thanks
AadilK said:
From some reading and your suggestions, I gathered the right way to go about this is, is to flash stock recovery(overriding twrp). Do an OTA upgrade(1.6 gb download/install) and afterwards reinstall TWRP and whatever else was previously done.
Am I correct in surmising this?
Click to expand...
Click to collapse
Not only the stock recovery, but you also need to restore the unrooted TWRP backup (never rooted ROM, "unrooting" doesn't work). Since having root will prevent OTA.
The full process is described here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
The other option, depending on what M8 version you have, may be to RUU to Marshmallow. That allows you skip a lot of the steps needed in the previous method (restoring a never rooted TWRP backup, restoring stock recovery, OTA updated) but adds a couple other steps (relock bootloader to RUU, unlock it again after RUU to flash TWRP); plus the RUU will wipe all user data on the device.
So its a judgment call for you (if your version has RUU) what path is preferred.
Related
Hi
I'm desperately looking for any Bell mobility stock 1.34.666.5 or Over.
The camera button is not working so I sent my phone to repair but they send it back because I do not have the right rom that was provided with my phone. I was able to unroot and put back 1.34.666.1 (the only one that is available it seems) but the technical support told me that my phone shipped with 1.34.666.5 and that they can't do anything unless I'm putting back this rom.
I tried getting OTA updates for 1.34.666.1 but it's not available. Minimum rom # to get OTA updates have to be 1.34.666.5
I'm screwed.
Regards
I have a nandroid backup of the stock ROM...it's rooted though.
Will I be able to flash using Clockwork Recovery? I can manage to remove root after flashing, I think.
Yes, flashable via Clockwork.
I'll let you know when I have it uploaded.
...and it's up.
https://xda:[email protected]/_xda/Bell.DZ.Stock.ROOTED.7z
Some notes:
- I only included the system and boot portions of the nandroid backup due to privacy concerns
- As such, you should do a system and boot restore (after a full wipe, of course) under "Advanced Restore"
- As mentioned earlier, this is rooted (so you'll need to unroot)
Hope this helps. Let us know how it goes.
Good news, I have been able to return to stock 1.34.666.5. Thank you very much for your backup.
I was thinking going unrooted was to be easy but i'm a little bit stuck.
How can I unroot and put back stock bootloader without flashing a new rom.
If I have to flash a new rom, is there a way to build one based on the backup you provided?
I've look at software update and there's an OTA update available for my phone. I tried to install but because I do not have the right bootloader (I think that's the problem) I'm unable to do the OTA update.
Thanks.
Tonkadan said:
Good news, I have been able to return to stock 1.34.666.5. Thank you very much for your backup.
I was thinking going unrooted was to be easy but i'm a little bit stuck.
How can I unroot and put back stock bootloader without flashing a new rom.
If I have to flash a new rom, is there a way to build one based on the backup you provided?
I've look at software update and there's an OTA update available for my phone. I tried to install but because I do not have the right bootloader (I think that's the problem) I'm unable to do the OTA update.
Thanks.
Click to expand...
Click to collapse
That's good to hear. I'd recommend making your own nandroid backup immediately.
As for the bootloader, you're sure you flashed the ENG HBOOT during the rooting process? If that's the case, I'm not sure where you can find the stock HBOOT...
Yes, I installed the Eng HBoot.
I'm trying now renaming the OTA update.zip, put on the root of sdcard and make recovery to install that update but I got an error about getprop CID?? and the update failed...
Still looking for a solution.
How did you make out Tonkadan? I'm in the same boat. I heard that if you did apply this update that you would not be able to root your phone anymore.
I' still rooted. I'm unable to go back to stock. I'm using cyanogenmod 7 for now but would really want to go back to stock if somone have the official Bell rom over 1.34.666.5.
... Or any way to get OTA updates for RUU 1.34.666.1 that is available on shippedroms.com
I didn't make a nandroid backup before I flashed a custom rom (stupid, I know) and the only stock nandroid backup I can find is a version older than my current firmware. So now I want to flash a stock rom and recovery that is a version older (e.g. current FW: 2.11.708.2, nandroid backup and recovery is 1.60.708.2), is this safe to do?
edit: also would I be able to get official OTA updates this way as well?
Thanks!
Maybe.
It depends on whether all modules are included in the firmware package. Most importantly, hboot consists of 3 modules (sbz 1, 2, and 3). If the firmware zip came from an OTA, its possible only some (not all 3) of the modules were included. Reason being, depending on the OTA, its possible that not all modules needed to be updated depending on what OTA came before it (does that make sense? A bit confusing I know). And in short, if all 3 modules don't play well together, you will have a broken hboot and a hard brick.
At least I've seen this happen on my old One X EVITA. It seems that most of the OTAs for the M8 are complete (and contain all 3 hboot modules), but I can't say that for certain (simply too many different OTAs to keep track of).
Short story, open the firmware zip on your computer using a program like 7zip. If you see sbz1,2,3 in the package, you should be okay. I think hboot is the only thing that comes deployed in "pieces" like that. Otherwise, you should be okay flashing any of the modules back and forth.
But I'm not guaranteeing anything when flashing a firmware zip. To me, its simply a scary thing to do; as any time you flash hboot or radio there is a tiny chance something goes wrong and you get a true brick.
Also, you need s-off to downgrade firmware.
redpoint73 said:
Maybe.
It depends on whether all modules are included in the firmware package. Most importantly, hboot consists of 3 modules (sbz 1, 2, and 3). If the firmware zip came from an OTA, its possible only some (not all 3) of the modules were included. Reason being, depending on the OTA, its possible that not all modules needed to be updated depending on what OTA came before it (does that make sense? A bit confusing I know). And in short, if all 3 modules don't play well together, you will have a broken hboot and a hard brick.
At least I've seen this happen on my old One X EVITA. It seems that most of the OTAs for the M8 are complete (and contain all 3 hboot modules), but I can't say that for certain (simply too many different OTAs to keep track of).
Short story, open the firmware zip on your computer using a program like 7zip. If you see sbz1,2,3 in the package, you should be okay. I think hboot is the only thing that comes deployed in "pieces" like that. Otherwise, you should be okay flashing any of the modules back and forth.
But I'm not guaranteeing anything when flashing a firmware zip. To me, its simply a scary thing to do; as any time you flash hboot or radio there is a tiny chance something goes wrong and you get a true brick.
Also, you need s-off to downgrade firmware.
Click to expand...
Click to collapse
Thanks for the reply redpoint.
I'm S-ON and my current firmware was updated through OTA. So what I'm wondering is would it be okay for me to flash a stock rom (the original one when the M8 was first released) on my HTC M8 WITHOUT downgrading my current firmware version. I'm scared if firmwares are not backwards compatible with roms.
zentenk said:
I'm S-ON and my current firmware was updated through OTA. So what I'm wondering is would it be okay for me to flash a stock rom (the original one when the M8 was first released) on my HTC M8 WITHOUT downgrading my current firmware version. I'm scared if firmwares are not backwards compatible with roms.
Click to expand...
Click to collapse
Yeah, I'm not sure. I haven't heard of anyone "downgrading" the OS and keeping newer (mismatched) firmware. I'd be afraid of lack of backwards compatibility, as well.
redpoint73 said:
Yeah, I'm not sure. I haven't heard of anyone "downgrading" the OS and keeping newer (mismatched) firmware. I'd be afraid of lack of backwards compatibility, as well.
Click to expand...
Click to collapse
Because I couldn't find the corresponding firmware . I found the stock nandroid backup and stock recovery for 1.60.708.2, but not the firmware... So I was thinking I could get away with flashing a stock ROM with earlier version and just let the OTAs do its thing and get everything up to date.
Edit: Also because if I want to get S-OFF I need to be in stock ROM anyway for firewater/sunshine
zentenk said:
Because I couldn't find the corresponding firmware . I found the stock nandroid backup and stock recovery for 1.60.708.2, but not the firmware... So I was thinking I could get away with flashing a stock ROM with earlier version and just let the OTAs do its thing and get everything up to date.
Edit: Also because if I want to get S-OFF I need to be in stock ROM anyway for firewater/sunshine
Click to expand...
Click to collapse
Yes, I understand perfectly what you are asking, and why. I just don't have an answer for you.
Just a suggestion, I would try to restore nandroid and stock recovery, and see what happens.
I think the worst that will happen, is you have to flash back to your current setup because of firmware issues.
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
I have rooted my Nexus 7 wifi 2012 tablet with TWRP
I don't want to keep un-rooting, applying ota updates then re-rooting my tablet. Is there an easy way. Maybe modified images i can use on a rooted tablet which i can install via the install option in twrp recovery loader.
I also notice that Nexus root tool kit has a ota sideload update option in the advanced menue.
So my question is where are the modifies ota update files if they exist as I don't want to keep un-rooting, rerooting each time to apply official ota updates. I have searched the net and can't find modifies ota updates?
My OTA failed due to root and modifications so I extracted system.img and boot.img from the 5.1 tarball and flashed them using Nexus Root Toolkit. Works well.
I'm going through the same issue - I want to keep running stock, but every time an OTA update comes in, it bugs me for an update until I go through the whole process of finding the files elsewhere, using the Toolkit to flash them etc etc.
Is there a better way to do this automatically? Can I find the downloaded OTA package on the Nexus and just flash it from there?
Since Lollipop, you can't take an OTA in any way (official or sideload) if you've modified your system. Rooting, custom recovery or kernel. Unrooting does not help since the system already has been modified.
Easiest way to upgrade and still keep your data is to flash the factory image but leave out userdata.img. This can be easily done through NRT (No wipe mode) if command prompt is scary. Yes you'll have to reroot... But hey, this is a Nexus, it's easy.
I assume that means waiting for someone to post the update?
If you want to wait for someone to make a prerooted image, then yes. Otherwise just download the official factory image (Google it) and go for it.
Google doesn't always release OTAs and factory images at the same time, so some waiting will probably always be involved...
Drives me crazy. TWRP used to be able to intercept a OTA flash, flash the needed images, detect you lost root and ask to restore root.
Somewhere that disappeared.
I just flashed a very old stock and took every OTA to 5.0.2, rooted, setup... now getting bombarded with 5.1.1 update notification. Ugh
Didgeridoohan said:
Since Lollipop, you can't take an OTA in any way (official or sideload) if you've modified your system. Rooting, custom recovery or kernel. Unrooting does not help since the system already has been modified.
Easiest way to upgrade and still keep your data is to flash the factory image but leave out userdata.img. This can be easily done through NRT (No wipe mode) if command prompt is scary. Yes you'll have to reroot... But hey, this is a Nexus, it's easy.
Click to expand...
Click to collapse
I need to flash the latest lollipop image to my rooted nexus with TWRP. I know where to find the images but don't remember how to flash it. What exactly are the steps and how do I leave out userdata.img ?
And what are the steps to reroot lollipop?
Thanks
i keep getting the offer to download the 5.1 update but when i do it dloads it then tries to reboot into recovery to flash it but it obviously boots into TWRP recovery which is no good.
So the question is when it dloads the update where does it dload to?
and could i flash it from TWRP if i find it?
So I found my old M83 the other day. It's running:
S-ON, UNLOCKED BOOTLOADER (NOW RELOCKED) ON TMOBILE.
I decided to try and flash the latest firmware via the sd card method, didn't work. Then tried flashing the firmware via fastboot. Fastboot didn't work either.
Now the phone only boots to the bootloader/hboot screen.
Any attempt at trying to flash firmware, or a recover, customer or otherwise fails.
I'm really hoping I can find a tmobile ruu zip to bring it back to life, however I can't seem to find a tmobile ruu zip anywhere anymore. I don't have a PC so downloading the *exe files doesn't do me much good.
Is there anyone that can please offer some assistance?
Much appreciated in advance!
What I did was to use TWRP and restore my original copy of the ROM (hopefully you still have that), if not you will need to find a TWRP backup of the ROM for the version of firmware you have and then restore the recovery for that same version (it get rid of TWRP). Then let the OTA fix update your phone. This is the route I took. Since Android 6 (MM) is the last release once you get to that stock, you can then replace the recovery (you could backup the recovery also) with TWRP, take a backup and then root or flash a new ROM.
Good luck