Is there a rooted MM stock rom available - One (M8) Q&A, Help & Troubleshooting

I'm upgrading my wife's euro unlocked M8 to MM and she would prefer it if it was kept stock, but rooted so I don't need to S-ON and relock the boorloader. So is there such a beast as a rooted stock image?

Just root the stock ROM?
ICE M9

As I said, I don't want to have to restore S-ON and relock the bootloader, then have to root all over agin.

mickrick said:
As I said, I don't want to have to restore S-ON and relock the bootloader, then have to root all over agin.
Click to expand...
Click to collapse
You don't have to restore S-On and relock bootloader to root. S-On/S-Off doesn't matter and you need a unlocked bootloader to install TWRP then install SuperSU zip to root.
Just restore a stock nandroid and root it or install MaximusHD or ARHD .. they are basically stock ROM with root.
Am I missing something with your problem ?
Anyway, requesting moderator to move this to correct section Q&A

Ok, makes sense now. I wasn't aware there was a nandroid backup. Now that I am, it should be pretty straight forward. Thanks.

There is the Developer's Edition stock ROM posted, with AROMA installer which gives option to root or not: http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
But ckpv5's suggestion to restore a stock TWRP backup gives specific CID options.
Or to ensure complete firmware compatibility, restore stock LP TWRP backup and stock recovery, OTA update to MM (which will also update to MM firmware), then flash TWRP (3.0) back on the phone and flash SuperSU 2.76 to root.

Related

[Q] OTA after flashing interim CWM

Hi,
first, my former device was a Samsung Galaxy S and i'm quite familiar with flashing ROMs and such on that device. The HTC One X is my first HTC device so i'm new in flashing and HTCs.
I used the method described in the below thread to flash CWM to my HTC One X
http://forum.xda-developers.com/showthread.php?t=1579797
My question now is this, can i receive OTAs with CWM flashed on my device? It is implied in the thread that i need the stock recovery to do so.
There is a stock recovery image supplied in this thread. Can i flash it to any strock ROM version or do i need the specific one for my ROM version and if so where can i get this version?
In order to flash CWM i had to unlock the bootloader, do i need to revert this for OTAs?
Thanks for your answers.
Hey,
with Clockworkmod flashed, you cant install OTA updates, you have to flash stock recovery and relock your bootloader.
If you have a custom rom, you have to install Stock RUU to recieve and install OTAs.
Greetz SoLdieR9312
You need stock rom and stock recovery. If your stock rom is just rooted, that's fine, but if you deleted system apps or modded, it might not work.
To install stock recovery you need to be unlocked, but unless you relocked, you're good to go.
You don't need to relock to install OTA.
To install RUU, you need to be relocked, but you don't need to install the stock recovery.
Edit: Urgh, that was quite a bump from the guy above. But the correction is still useful.

Installing OTA - noob questions

I'm on stock 1.54.401.10, rooted, s-off and with twrp.
I'd like to go to stock recovery to install OTA.
Need answers for some questions first:
What do I need to install update?
I know about recovery, do I need to relock bootloader?
Also there was an issue with custom hboots on m7, so can I relock bootloader, update software, etc, if I don't have red text during boot? Gone after using firewater.
Not sure if this is related, just want to be sure, I won't brick my phone during update.
Or maybe it is better to flash firmware and newer rom manually?
wor3q said:
I'm on stock 1.54.401.10, rooted, s-off and with twrp.
I'd like to go to stock recovery to install OTA.
Need answers for some questions first:
What do I need to install update?
I know about recovery, do I need to relock bootloader?
Also there was an issue with custom hboots on m7, so can I relock bootloader, update software, etc, if I don't have red text during boot? Gone after using firewater.
Not sure if this is related, just want to be sure, I won't brick my phone during update.
Or maybe it is better to flash firmware and newer rom manually?
Click to expand...
Click to collapse
With stock recovery and stock rom you can install official updatea, no need for relocking bootloader.
Because you're s-off you can also do it manually, see this post.

[Q] 2.10.401.1 RUU.exe or how to get back to full Stock ROM

Hi Folks,
Well, I'm S-OFF and running ViperROM with 2.10.401.1 firmware (from sneakyghost thread) and TWRP Recovery on an international device with unlocked bootloader and SuperCID.
Now I want to play again with a full fresh and clean stock experience. How to accomplish this?
The easiest way would be to run a 2.10.401.1 RUU exe, but I couldn't find one. I guess it's not available and maybe never will be.
So, after reading threads I would assume the way I have to go is to run an 1.32 RUU exe and then I should get the 2.10 OTA
Is that right or do I have to relock the bootloader to get stock OTAs ? (Cos of S-OFF)
Hope you could help me out on that one and point me in the right direction.
Thx
You have to be 100% stock to get OTAs successfully. Since you're s-off, just running an earlier RUU exe should do it, but you may need to relock.
Under no circumstances should you go back to s-on.
DroidShift79 said:
Hi Folks,
Well, I'm S-OFF and running ViperROM with 2.10.401.1 firmware (from sneakyghost thread) and TWRP Recovery on an international device with unlocked bootloader and SuperCID.
Now I want to play again with a full fresh and clean stock experience. How to accomplish this?
The easiest way would be to run a 2.10.401.1 RUU exe, but I couldn't find one. I guess it's not available and maybe never will be.
So, after reading threads I would assume the way I have to go is to run an 1.32 RUU exe and then I should get the 2.10 OTA
Is that right or do I have to relock the bootloader to get stock OTAs ? (Cos of S-OFF)
Hope you could help me out on that one and point me in the right direction.
Thx
Click to expand...
Click to collapse
Hi
Did you check this thread...
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
MAX 404 said:
Hi
Did you check this thread...
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
Click to expand...
Click to collapse
Yes, did that. But the full ZIP that is there doesn't touch the /system partition, so it's not the clean way I want to go.
THX anyway.
DroidShift79 said:
Yes, did that. But the full ZIP that is there doesn't touch the /system partition, so it's not the clean way I want to go.
THX anyway.
Click to expand...
Click to collapse
Hi
I see....guess the only way for now is as you point out earlier RUU and upgrade from there.
good luck
MAX 404 said:
Hi
I see....guess the only way for now is as you point out earlier RUU and upgrade from there.
good luck
Click to expand...
Click to collapse
Thought of this,
just not sure if I need to relock bootloader to get official otas
DroidShift79 said:
Thought of this,
just not sure if I need to relock bootloader to get official otas
Click to expand...
Click to collapse
If you're S-OFF you don't need to relock to get OTAs. I converted my carrier handset to unbranded and received OTA updates after flashing a RUU without relocking.
Sent from my HTC One M9 using Tapatalk
THX kingvortex. I just do it and report back.
Thanks all of you.
DroidShift79 said:
Thought of this,
just not sure if I need to relock bootloader to get official otas
Click to expand...
Click to collapse
kingvortex said:
If you're S-OFF you don't need to relock to get OTAs. I converted my carrier handset to unbranded and received OTA updates after flashing a RUU without relocking.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
hi mates
I do not think S-OFF , S-ON or locked bootloaders are much of an issue to get OTA, check points 8, 9 and 10 from this thread
EDIT : kingvortex you are right oem locked is necessary with s-on
http://forum.xda-developers.com/one...ery-twrp-touch-recovery-t3066720/post59745198
8. How do I restore stock system so that I can accept an OTA?
Check the "Mount system as read-only" box in the Mount menu.
Restore stock "System Image" backup (This will only work if you've made a System Image backup prior to making any modifications to /system like root it). As of the official 2.8.6.1 version, it is no longer necessary to fastboot flash the stock system image.
NOTE: If you made a stock system backup with one of the Beta TWRP versions, you will have to rename the backup file in the backup folder manually from "system.emmc.win" to "system_image.emmc.win" for the new official TWRP to see it as a "System Image" backup rather than a "System" backup. Otherwise, you'll get an error that the backup can't be restored because system is read-only.
Fastboot flash stock recovery (fastboot flash recovery recovery_signed.img)
NOTE: It is also possible to restore stock recovery via the TWRP GUI. Rename the stock recovery file to "recovery.emmc.win" and place in the backup folder with the stock system image. Recovery will then show as a restore option. MAKE SURE YOU REALLY WANT TO DO THIS, AS TWRP WILL BE GONE WHEN YOU REBOOT OUT OF RECOVERY!!
Reboot to system, install OTA.
9. What if I have an RUU? Do I need to worry about all this OTA nonsense?
Not if you don't care about losing all your data. If you're S-ON and have an RUU available for your exact variant (model ID and CID must match) and software number (main version must be the same or newer), then you can get back to a fully stock state by relocking (fastboot oem lock) and flashing an RUU. However, if you'd prefer to take an OTA to keep your data intact, the method stated above is how to do so. Or, you can just run a custom ROM and wait for your ROM chef to update their ROM to the latest software (though you'll still have to find a way to update your firmware if you're not S-OFF)
10. After I go through all this and successfully apply an OTA, how do I make sure I have a clean starting point again?
After the OTA is applied and TWRP is flashed, it will once again detect an untouched system, which will mount system read-only and allow you to make a fully stock backup and start the process over again, this time with the new base.
Well, what I did so far, was to use the 1.32.401.17 ruu.exe
Flash went fine, but no OTA did show up.
So I wanted to flash the 1.32.401.8 ruu zip.
But putting it on sdcard or using fastboot flash zip failed.
Wonder why!?
Later on I'll try Max 404 find.
MAX 404 said:
hi mates
I do not think S-OFF , S-ON or locked bootloaders are much of an issue to get OTA, check points 8, 9 and 10 from this thread
EDIT : kingvortex you are right oem locked is necessary with s-on
http://forum.xda-developers.com/one...ery-twrp-touch-recovery-t3066720/post59745198
8. How do I restore stock system so that I can accept an OTA?
Check the "Mount system as read-only" box in the Mount menu.
Restore stock "System Image" backup (This will only work if you've made a System Image backup prior to making any modifications to /system like root it). As of the official 2.8.6.1 version, it is no longer necessary to fastboot flash the stock system image.
NOTE: If you made a stock system backup with one of the Beta TWRP versions, you will have to rename the backup file in the backup folder manually from "system.emmc.win" to "system_image.emmc.win" for the new official TWRP to see it as a "System Image" backup rather than a "System" backup. Otherwise, you'll get an error that the backup can't be restored because system is read-only.
Fastboot flash stock recovery (fastboot flash recovery recovery_signed.img)
NOTE: It is also possible to restore stock recovery via the TWRP GUI. Rename the stock recovery file to "recovery.emmc.win" and place in the backup folder with the stock system image. Recovery will then show as a restore option. MAKE SURE YOU REALLY WANT TO DO THIS, AS TWRP WILL BE GONE WHEN YOU REBOOT OUT OF RECOVERY!!
Reboot to system, install OTA.
9. What if I have an RUU? Do I need to worry about all this OTA nonsense?
Not if you don't care about losing all your data. If you're S-ON and have an RUU available for your exact variant (model ID and CID must match) and software number (main version must be the same or newer), then you can get back to a fully stock state by relocking (fastboot oem lock) and flashing an RUU. However, if you'd prefer to take an OTA to keep your data intact, the method stated above is how to do so. Or, you can just run a custom ROM and wait for your ROM chef to update their ROM to the latest software (though you'll still have to find a way to update your firmware if you're not S-OFF)
10. After I go through all this and successfully apply an OTA, how do I make sure I have a clean starting point again?
After the OTA is applied and TWRP is flashed, it will once again detect an untouched system, which will mount system read-only and allow you to make a fully stock backup and start the process over again, this time with the new base.
Click to expand...
Click to collapse

New update GPE but fail to update

New update GPE but fail to update due to E: error..
I think you have to relock the bootloader to get the update but I could be wrong...
Also make sure you're not on superuser CID (11111111)
Can't conclude at all where the error is based on. The provided info is absolutely not enough !
You need stock rom (read never rooted) and stock recovery. Boot loader being unlocked or relocked has for an ota no effect, neither does supercid.
kullum79 said:
I think you have to relock the bootloader to get the update but I could be wrong...
Also make sure you're not on superuser CID (11111111)
Click to expand...
Click to collapse
Wrong on both counts. Neither unlocked bootloader, nor SuperCID will prevent OTA.
As i said
redpoint73 said:
Wrong on both counts. Neither unlocked bootloader, nor SuperCID will prevent OTA.
Click to expand...
Click to collapse
I'm in a similar position.
My M8 was a Rogers once upon a time.
I went through the process of converting it to GPE. It is S-Off, & rooted with the systemless root.
I have TWRP 2.8.7 (iirc - the latest twrp for m8).
I have the same 'an update is available' as OP.
When i tell it to install the phone reboots to recovery and the update fails. I assume this is a TWRP issue.
Not sure what my best approach for getting the update installed is? Can I every to stock Recovery, install the update, and reinstall TWRP? Do I even need TWRP now I'm rooted...?
the_darkwing_duck said:
Not sure what my best approach for getting the update installed is? Can I every to stock Recovery, install the update, and reinstall TWRP? Do I even need TWRP now I'm rooted...?
Click to expand...
Click to collapse
You need stock (never rooted) ROM and matching stock recovery.
Then yes, after you update you will need to reinstall TWRP to root again. OTA update will almost always wipe out root, so its irrelevant that you have root presently. Then root, noting that root on MM is more complicated than past builds: http://forum.xda-developers.com/htc-one-m8/general/root-root-marshmallow-gpe-supersu-t3242210
Or you can just run the MM RUU (see Development section), keeping in mind that it will wipe the phone (so backup any personal data you want to keep accordingly, before RUU).
Also should be noted, it seems that lots of folks have had to flash MM firmware, then OTA or RUU to Marshmallow, if you get an unexplained Error 155.

How to Update a Rooted HTC One M8 to Marshmallow (Currently 4.4.4 Kit Kat)

Hello, i have red so many forums of how to update a rooted htc one m8, but there are so many opinions i'm left very confused. Some say you only need to flash stock recovery (never clarified which version of the recovery, the one in the update you are going to install or the one your device is currently at, mine is at 3.29.161.9), other say you need to Install Stock Nandroid Backup, flash the stock recovery and relock the bootloader. When i rooted my phone i unlocked the bootloader, installed TWRP and from TWRP I installed SuperSU. So what is the actual procedure for updating a rooted HTC One M8?
1. You can install current firmware stock recovery or the version that you're going to update.
Doesn't matter, both work.
2. You need a clean stock non-rooted system which normally you can get from stock non-rooted nandroid backup. Restore the backup, install stock recovery then do OTA update... no need to relock bootloader.

Categories

Resources