Develop Bugs

[question] root after 2.2 RUU

Is it possible to use the 2.1 RUU after using the 2.2 RUU? I want to downgrade to use unrevoked. Thanks for the help.

If you're S-OFF, you can just root by installing a custom recovery using PB31IMG.zip and flashing a root zip.

Berzerker7 said:
If you're S-OFF, you can just root by installing a custom recovery using PB31IMG.zip and flashing a root zip.
Click to expand...
Click to collapse
yes.
if u are not s-off, the older RUUs are there on the forum, i dont see why not.

redd12345 said:
Is it possible to use the 2.1 RUU after using the 2.2 RUU? I want to downgrade to use unrevoked. Thanks for the help.
Click to expand...
Click to collapse
Watch this video, has instructions and the necessary files to download listed in the information section.
http://www.youtube.com/watch?v=eeuiURZZZds&feature=player_embedded
Easy directions, and brings you back to Stock 2.1, .77 HBOOT and 1.xx Radio. Essentially, the way your phone was when you purchased it.
You backup anything you can, this will wipe your device.
After finishing this process, if you want to go back to the 2.2 RUU with Root...
1. Perform unrEVOked Root Process.
2. Flash unrEVOked forever.
3. Flash Stock Recovery
4. Perform 2.2 RUU (you will lose your root... here)
5. Flash ClockworkMod (you can do this because of the S-OFF function being invoked)
6. Flash a root payload containing su and superuser.apk
7. If you want to go ahead and revert to Stock Android 2e recovery (being prepared for other OTAs in the future)
If you need help feel free to PM me.

Full of win!
rdmerck said:
Watch this video, has instructions and the necessary files to download listed in the information section.
http://www.youtube.com/watch?v=eeuiURZZZds&feature=player_embedded
Easy directions, and brings you back to Stock 2.1, .77 HBOOT and 1.xx Radio. Essentially, the way your phone was when you purchased it.
You backup anything you can, this will wipe your device.
After finishing this process, if you want to go back to the 2.2 RUU with Root...
1. Perform unrEVOked Root Process.
2. Flash unrEVOked forever.
3. Flash Stock Recovery
4. Perform 2.2 RUU (you will lose your root... here)
5. Flash ClockworkMod (you can do this because of the S-OFF function being invoked)
6. Flash a root payload containing su and superuser.apk
7. If you want to go ahead and revert to Stock Android 2e recovery (being prepared for other OTAs in the future)
If you need help feel free to PM me.
Click to expand...
Click to collapse
Thank you all so much!! I'm going to try this later tonight. If I want free tethering after 2.2 with root, do I just install the binaries and the old evo tether (pre) or has that changed too? I read something about changing a setting so Verizon doesn't pick it up.

[tutorial] How to upgrade One V with an OTA update / RUU to revert to stock

As there are many questions on how to do OTA update & to revert to stock after a device is rooted and bootloader unlocked; I made this simple guide which I hope will help the newbies especially.
NOTE : always do a backup and a nandroid backup before trying any of these.
OTA update:
A) ROM is stock, bootloader unlocked, stock recovery and not rooted.
- just run the OTA update, there is no need to relock the bootloader
B) ROM is stock, bootloader unlocked, CWM recovery and not rooted.
- flash the stock recovery that comes with your RUU, extract the RUU for the stock recovery.
* boot to bootloader
* fastboot flash recovery recovery_signed.img
* fastboot reboot-bootloader
* fastboot erase cache
* fastboot reboot
- run the OTA update
C) ROM is stock, bootloader unlocked, stock recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- run the OTA update, there is no need to relock bootloader
- Once done, run OTA Rootkeeper and click restore root
D) ROM is stock, bootloader unlocked, CWM recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- no need to relock bootloader
- boot to bootloader and fastboot flash the stock recovery
- run the OTA update
- Once done, run OTA Rootkeeper and click restore root
E) ROM is custom, bootloader unlocked, CWM recovery and rooted and you have a stock nandroid backup
- flash the stock boot.img if after nandroid restore, you have a bootloop
- flash the stock recovery.img
- relock the bootloader - fastboot oem lock
- boot your device and run the OTA update
F) ROM is custom, bootloader unlocked, CWM recovery and rooted and you don't have a stock nandroid backup
- if you dont have the stock nandroid backup, you need to run RUU
- before you can run the RUU you need to:
* flash the stock recovery.img
* flash the stock boot.img (maybe no need)
* relock the bootloader - fastboot oem lock
* run RUU
- run device setup
- run the OTA update
Flashing RUU to revert to stock or to update your One V after you have a custom ROM installed.
- you must have the correct RUU for your device.
- if you are not sure, download CID Getter from Play Store and run it, it will show your CID.
- with your CID, you may be able to find a correct RUU for your device
then
1- in fastboot mode - relock the bootloader : run command fastboot oem lock
2- in fastboot mode - flash/run/double click the RUU; follow the updater instruction - next,update,bla,bla,bla until it finish
Note :
Error 155 - usually wrong recovery.img /wrong boot.img or bootloader not relocked
Error 140 - wrong bootloader / bootloader unlocked
Error 131 - wrong RUU for your device
Credit to all XDA members that posted all the guides in various forum thread and some from own experience which I compiled here for easy reference.

If I have a nandroid backup from my stock (nandroid after it was rooted), how can I get rid of root? I need to lock bootloader also because I need to return my product. Also, I have the kernel img and recovery img (need to flash those also because I have flashed custom kernel and cwm).
So my guess is that:
nandroid restore
go to fastboot and flash boot.img
go to fastboot and flash recovery img
go to fastboot and relock bootloader.
but how do you get rid of root?

1ceb0x said:
If I have a nandroid backup from my stock (nandroid after it was rooted), how can I get rid of root? I need to lock bootloader also because I need to return my product. Also, I have the kernel img and recovery img (need to flash those also because I have flashed custom kernel and cwm).
So my guess is that:
nandroid restore
go to fastboot and flash boot.img
go to fastboot and flash recovery img
go to fastboot and relock bootloader.
but how do you get rid of root?
Click to expand...
Click to collapse
i think u have an option in super su
to completely get rid of root
dnt knw if tht wrks
try it
dont just say thanks hit thanks if i helped
sent from my awesome HTC One V using xda premium

1ceb0x said:
If I have a nandroid backup from my stock (nandroid after it was rooted), how can I get rid of root? I need to lock bootloader also because I need to return my product. Also, I have the kernel img and recovery img (need to flash those also because I have flashed custom kernel and cwm).
So my guess is that:
nandroid restore
go to fastboot and flash boot.img
go to fastboot and flash recovery img
go to fastboot and relock bootloader.
but how do you get rid of root?
Click to expand...
Click to collapse
Are you able to get the RUU for your phone/region?

1ceb0x said:
but how do you get rid of root?
Click to expand...
Click to collapse
Reflash system.img is the no-fail way.

CafeKampuchia said:
Reflash system.img is the no-fail way.
Click to expand...
Click to collapse
System.img is the rom itself right? If yes, by reflashing it, the root will still be there because the nandroid was AFTER it was rooted. And I didn't found my RUU. I have found one which is the same as mine but the last number .x differs from mine (I have .4 and the RUU has .3)...

your going to need the ruu buddy, i have to do the same, the kernel shows up as root blah blah blah. kernel recovery and rom itself need flashing.....

Would you be okay with just removing the superuser.apk or did you also want the binary gone?
One of the possible options is to modify your nandroid backup so that both files are deleted (and not restored), but I'm not sure if CWM complains if the backup has been modified.

1ceb0x said:
If I have a nandroid backup from my stock (nandroid after it was rooted), how can I get rid of root? I need to lock bootloader also because I need to return my product. Also, I have the kernel img and recovery img (need to flash those also because I have flashed custom kernel and cwm).
So my guess is that:
nandroid restore
go to fastboot and flash boot.img
go to fastboot and flash recovery img
go to fastboot and relock bootloader.
but how do you get rid of root?
Click to expand...
Click to collapse
Restore your nandroid backup
Reboot your device.
Open the SuperSU, and click Full unroot (it will remove the app, apk & su library)
Reboot to recovery
Make a new nandroid backup (this time there is no root for safekeeping)
Reboot to bootloader
fastboot flash boot stockboot.img
fastboot erase cache
fastboot flash recovery stockrecovery.img
fastboot erase cache
fastboot oem lock
now you are back to stock rom without root and relocked

Thank you so much, will try it tonight because tomorrow I need to get my unit to replacement. I didn't knew how the process worked since I never did it (I work with android for 3 years now).
But I have a question. If you open su and you click full unroot, why do you need to make a new nandroid and flash that?

1ceb0x said:
Thank you so much, will try it tonight because tomorrow I need to get my unit to replacement. I didn't knew how the process worked since I never did it (I work with android for 3 years now).
But I have a question. If you open su and you click full unroot, why do you need to make a new nandroid and flash that?
Click to expand...
Click to collapse
Because your old nandroid has SuperSU.apk and SU library in it.
New backup will not have those because you already remove them before new nandroid is made.
So you'll have a new stock nandroid without root.

ckpv5 said:
Because your old nandroid has SuperSU.apk and SU library in it.
New backup will not have those because you already remove them before new nandroid is made.
So you'll have a stock nandroid without root.
Click to expand...
Click to collapse
But if I restore the nandroid that has root and then unroot it, I don't see why you need to make a new one and restore that.

1ceb0x said:
But if I restore the nandroid that has root and then unroot it, I don't see why you need to make a new one and restore that.
Click to expand...
Click to collapse
I see your point... I thought that you do want to keep a stock nandroid without root for safekeeping as there is no RUU for .4 yet
The post now updated.

ckpv5 said:
I see your point... I thought that you do want to keep a stock nandroid without root for safekeeping as there is no RUU for .4 yet
Click to expand...
Click to collapse
Well, the point is that I will replace this unit with another one since this one is not working with Orange carriers. My shop was in talks with HTC service to get an unlock code but they failed to do so, so they said it is ok to change the unit. No need to keep a nandroid backup since I don't know what software version I will have on the new phone. Thank you for your help!

I fall under category D (ROM is stock, bootloader unlocked, CWM recovery and rooted)
Can someone tell me in detail how to
boot to bootloader and fastboot flash the stock recovery
Click to expand...
Click to collapse
Do I boot into CWM?
Thanks for your help.

RaskloP said:
I fall under category D (ROM is stock, bootloader unlocked, CWM recovery and rooted)
Can someone tell me in detail how to
Do I boot into CWM?
Thanks for your help.
Click to expand...
Click to collapse
No, not boot into CWM.
Remember how you go to bootloader when you first want to unlock your bootloader ? You press power + volume down, that is boot to bootloader.

1ceb0x said:
Thank you so much, will try it tonight because tomorrow I need to get my unit to replacement. I didn't knew how the process worked since I never did it (I work with android for 3 years now).
But I have a question. If you open su and you click full unroot, why do you need to make a new nandroid and flash that?
Click to expand...
Click to collapse
so that your new nandroid backup doesn't have SuperSU and you can still keep your datas

RaskloP said:
I fall under category D (ROM is stock, bootloader unlocked, CWM recovery and rooted)
Can someone tell me in detail how to
Do I boot into CWM?
Thanks for your help.
Click to expand...
Click to collapse
Please make sure you're flashing to recovery, not boot.
Connect your phone to your computer via USB. I'll assume you have the necessary bootloader/adb drivers installed.
Open up a command prompt to wherever your recovery.img is and type (this assumes you can easily access adb/fastboot from anywhere):
adb reboot bootloader
Phone should reboot into fastboot. From there type:
fastboot flash recovery recovery.img
It should then flash the stock recovery.
I would recommend taking a look at the HTC All-in-One ToolKit in the Development forums. It might simplify it for you.

To get back to you guys, I have followed these instructions and I am back to stock. The only thing that should worry me now is that the bootloader says "RELOCKED" instead of "LOCKED" but I don't think this is a reason why I should loose my warranty since we've done it using HTCDEV method.
It was easy enough because I had my nandroid backup. Such a joy to have one of these at hand!
Thank you all for the infos. Tomorrow I'll get my replacement :yuhuu:

1ceb0x said:
To get back to you guys, I have followed these instructions and I am back to stock. The only thing that should worry me now is that the bootloader says "RELOCKED" instead of "LOCKED" but I don't think this is a reason why I should loose my warranty since we've done it using HTCDEV method.
It was easy enough because I had my nandroid backup. Such a joy to have one of these at hand!
Thank you all for the infos. Tomorrow I'll get my replacement :yuhuu:
Click to expand...
Click to collapse
yea it should be ok buddy, my new handset arrives tomorrow, wish i could had gone to a store to pick it up so i could check it before i left the store :/ i do hate 3 customer services

[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

Is there a rooted MM stock rom available

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.

Setting up an M9 after replacement of an M8.

I want to make sure I understand what I need to do.
My plan was to S-OFF with Sunshine, then allow it it to update itself
to Marshmallow.
Is there any issues with allowing normal OTAs
after S-OFF unlock with Sunshine?
[should I look for an MM RUU instead?]
I mean will updates work on an unlocked,
but otherwise stock phone?
Can anyone point me to the thread for setting
lock / unlock / relock bootloader status, (and how to reset
tampered flag), via echo && dd settings on an S-OFF'd
device?
Thanks

Understanding options
I'm still updating the OS it's gone from lollipop 1 (5.0.1) to MM and now is doing the security patches.
I've used Sunshine to S-OFF and unlock, but not rooted and still otherwise stock.
Will having S-OFF / unlock allow me to do: fastboot boot twrp-3.0.2-0-hima-HTC-M9.img
So I can backup the OEM recovery and system partitions, before installing
SuperSU and Busybox which I think go in /system/xbin/?
Thanks

fuzzynco said:
I'm still updating the OS it's gone from lollipop 1 (5.0.1) to MM and now is doing the security patches.
I've used Sunshine to S-OFF and unlock, but not rooted and still otherwise stock.
Will having S-OFF / unlock allow me to do: fastboot boot twrp-3.0.2-0-hima-HTC-M9.img
So I can backup the OEM recovery and system partitions, before installing
SuperSU and Busybox which I think go in /system/xbin/?
Thanks
Click to expand...
Click to collapse
If you have unlocked the bootloader and are s-off you should be ready to flash a custom recovery. Then backup, then root as planned. Hope that helps