Database Develop

[Q] Rooting after 5.03.651.3 OTA Update Questions

Sprint HTC ONE
Background:
Just spent the last 15 hours flashing back to 4.06.651.4 stock rom in order to take the new OTA update 5.03.651.3. Somehow I managed to brick my phone to where it would only stay stuck on the green HTC with white background. The only thing that I was able to get to work was booting into the bootloader and play with fastboot commands. I had CWM recovery installed but could never get adb to discover the phone to sideload a rom onto the memory card. I had no backup, and pretty much had everything wiped and formatted on the phone. I went througt installing back and fourth twrp, cwm, and different stock recoveries, and hours of trying different things to no avail. What got my phone back up and going was at some point changing my cid to 11111111(not sure if this did anything for me), flashing 4.06.651.4_firmware.zip, then running Sprint_HTC_One_m7wls_4.06.651.4_RUU.zip (ARUWizard.exe) while in fastboot oem rebootRUU mode. Since then I have installed the 4.06.651.9 OTA and then the 5.03.651.3 OTA which is where I stand at this point.
That being said, here's the state of my phone currently:
No Root
CID: 11111111 ( I don't remember what it should say incase I need to warranty the phone)
S-off
bootloader unlocked (did lock it but found out I didn't have to since I was s-off and since then unlocked)
hboot went from 1.56 to 1.57
___________________________________________
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0515
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.03.651.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA35RS900979
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4029mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Now this here are my questions.
Can I gain Root on being on 5.03.651.3?
If I have to reinstall a custom recovery to gain root, would I be able to flash back to the current stock recovery?
Having the new ver. of hboot 1.57, would I be able to downgrade back to 1.56 using the 4.06.651.4_firmware.zip, to flash back to stock 4.06.651.4 if I want to factory reset and unroot, s-on, and lock the bootloader if necessary?
And last of all what should the CID show from factory on the new OTA?
Basically what I want is to have factory everything rooted so I can get rid of the bloatware. Nice and simple that's all.
Much appreciated!!!

Rare5spd said:
Sprint HTC ONE
Background:
Just spent the last 15 hours flashing back to 4.06.651.4 stock rom in order to take the new OTA update 5.03.651.3. Somehow I managed to brick my phone to where it would only stay stuck on the green HTC with white background. The only thing that I was able to get to work was booting into the bootloader and play with fastboot commands. I had CWM recovery installed but could never get adb to discover the phone to sideload a rom onto the memory card. I had no backup, and pretty much had everything wiped and formatted on the phone. I went througt installing back and fourth twrp, cwm, and different stock recoveries, and hours of trying different things to no avail. What got my phone back up and going was at some point changing my cid to 11111111(not sure if this did anything for me), flashing 4.06.651.4_firmware.zip, then running Sprint_HTC_One_m7wls_4.06.651.4_RUU.zip (ARUWizard.exe) while in fastboot oem rebootRUU mode. Since then I have installed the 4.06.651.9 OTA and then the 5.03.651.3 OTA which is where I stand at this point.
That being said, here's the state of my phone currently:
No Root
CID: 11111111 ( I don't remember what it should say incase I need to warranty the phone)
S-off
bootloader unlocked (did lock it but found out I didn't have to since I was s-off and since then unlocked)
hboot went from 1.56 to 1.57
___________________________________________
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0515
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.03.651.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA35RS900979
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4029mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Now this here are my questions.
1. Can I gain Root on being on 5.03.651.3?
2. If I have to reinstall a custom recovery to gain root, would I be able to flash back to the current stock recovery?
3. Having the new ver. of hboot 1.57, would I be able to downgrade back to 1.56 using the 4.06.651.4_firmware.zip, to flash back to stock 4.06.651.4 if I want to factory reset and unroot, s-on, and lock the bootloader if necessary?
And last of all what should the CID show from factory on the new OTA?
Basically what I want is to have factory everything rooted so I can get rid of the bloatware. Nice and simple that's all.
Much appreciated!!!
Click to expand...
Click to collapse
Alright, so answering your questions:
1. Yes you can get root being on 5.03.651.3.
2. 99% sure you can't, unless you RUU; but if you RUU you completely lose everything including root.
3. Yeah you can if you're S-OFF.
ROOTING INSTRUCTIONS:
http://download.chainfire.eu/450/SuperSU/UPDATE-SuperSU-v2.00.zip
Try downloading that file and then flashing it in TWRP. I haven't tested this though as the ROM that I'm using is prerooted.
There's a video by fellow member @zedomax that tells you how to do this, although the SuperSU zip in his video is outdated as the video's made in 2013 , so I linked you the latest one above.
EDIT: Oh and the factory CID for the Sprint HTC One is SPCS_001.

Thank you for taking the time to reply to my thread and answering all of my questions. I will try rooting when I get home tonight. Thanks again!!!

Rare5spd said:
Thank you for taking the time to reply to my thread and answering all of my questions. I will try rooting when I get home tonight. Thanks again!!!
Click to expand...
Click to collapse
You could also use these commands if you are S-off
fastboot oem rebootRUU
fastboot flash zip recovery.zip
fastboot reboot
this could flash a recovery since you are S-off and flash back your stock recovery... Make sure you include an android-info.txt file...
In the android-info.txt file include this:
modelid: PN0720000
cidnum: SPCS_001
mainver: 1.29.651.10
hbootpreupdate:3
with that txt file and a recovery be it stock or a custom you can do what you like.

StormyNight said:
Alright, so answering your questions:
1. Yes you can get root being on 5.03.651.3.
2. 99% sure you can't, unless you RUU; but if you RUU you completely lose everything including root.
3. Yeah you can if you're S-OFF.
Click to expand...
Click to collapse
In reference to your answer on #2, Why can't you flash back to current stock recovery?
I'm curious to know because, i'm stocked ROM rooted, TRWP (lastest version), s-On. and i've been updating my firmware OTA.
I download the OTA firmware then flashboot stock recovery, reboot phone and perform the update. Once it's done, i then flashboot custom recovery (TWRP) and flash SuperSU to gain root again. The firmware version I"m on now is 5.03.651.3.
So basically, i'm concerned that i won't be able to flash stock recovery whenever the next firmware update occurs, using the method i've just described.

The Glow said:
In reference to your answer on #2, Why can't you flash back to current stock recovery?
I'm curious to know because, i'm stocked ROM rooted, TRWP (lastest version), s-On. and i've been updating my firmware OTA.
I download the OTA firmware then flashboot stock recovery, reboot phone and perform the update. Once it's done, i then flashboot custom recovery (TWRP) and flash SuperSU to gain root again. The firmware version I"m on now is 5.03.651.3.
So basically, i'm concerned that i won't be able to flash stock recovery whenever the next firmware update occurs, using the method i've just described.
Click to expand...
Click to collapse
Huh, didn't know that. My apologies. By the way, you still be able to do it even when the next firmware update occurs.

Yesterday i tried to update my phone without success
fisrt i tried to install roms but it didnt work
then i tried to update my main version and fail also
then i dont know why i change mi CID number to HTC__001
it started to brick the screen turn gray but i solved it i don´t know how
but i noticed my phone changed to S-ON
i tried many times with many ruus to restore but i can´nt Problems CID and 152 images i locked before doing this
i insert a rom with the same rom 5.03.651.3 success at installing
it started good still the part i have to write language it stayed in HTC logo and then restart
Now im trying to get S-OFF and change my CID to another number but i don´t know wich
and try RUU again but i can not IT gave error and Rumrunner adb didnt find my device
i don´t know what else to do im also 2 days awake :crying:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.60.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.03.651.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA358S900105
(bootloader) imei: 99*****************
(bootloader) meid: 99***************
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4318mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-91bb20e1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
PS sorry im not a native english speaker. try to understand me
i can understand english very well
THANX ALL OF YOU

HTC One M7 GPE won't update from Jellybean

I have an HTC One M7 Google Play Edition running Jellybean (4.2.2). This lags well behind the current version of android for this version of the phone. Unfortunately, I am unable to receive an OTA update (everytime I check, I get a message stating that my phone is up to date). Is there anything I can do to force an OTA update short of rooting the device and manually installing the updates? I am currently on a BYOD plan with T-Mobile if that matters at all.

nocipher said:
I have an HTC One M7 Google Play Edition running Jellybean (4.2.2). This lags well behind the current version of android for this version of the phone. Unfortunately, I am unable to receive an OTA update (everytime I check, I get a message stating that my phone is up to date). Is there anything I can do to force an OTA update short of rooting the device and manually installing the updates? I am currently on a BYOD plan with T-Mobile if that matters at all.
Click to expand...
Click to collapse
Can you please post the output of "fastboot getvar all" (remove your imei and serialno information before posting).

alray said:
Can you please post the output of "fastboot getvar all" (remove your imei and serialno information before posting).
Click to expand...
Click to collapse
C:\adb>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.1700.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4062mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-21fde4b846
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.176s

nocipher said:
C:\adb>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.1700.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4062mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-21fde4b846
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.176s
Click to expand...
Click to collapse
Everything looks good. Is your bootloader locked/unlock/relocked?
You could use a RUU to update your phone, flashing a ruu will wipe everything from the phone, like if it was brand new. Backup your important files before.
If you ever considered S-OFF for your phone, better to do it before updating using rumrunner exploit for free. If you update to the latest version, you will need to use Sunshine s-off which cost 25$.

alray said:
Everything looks good. Is your bootloader locked/unlock/relocked?
You could use a RUU to update your phone, flashing a ruu will wipe everything from the phone, like if it was brand new. Backup your important files before.
If you ever considered S-OFF for your phone, better to do it before updating using rumrunner exploit for free. If you update to the latest version, you will need to use Sunshine s-off which cost 25$.
Click to expand...
Click to collapse
My bootloader is locked. (I pulled the phone out of the unopened box just yesterday).
I tried to get S-OFF using rumrunner so I could update using the HBOOT recovery feature, but there was an issue with my phone not being rooted or something along those lines. Maybe the failure was due to a locked bootloader? (I'm new to all of this.)
If I set my phone to S-OFF, would it be better to just manually apply the updates or use an RUU?

nocipher said:
My bootloader is locked. (I pulled the phone out of the unopened box just yesterday).
I tried to get S-OFF using rumrunner so I could update using the HBOOT recovery feature, but there was an issue with my phone not being rooted or something along those lines. Maybe the failure was due to a locked bootloader? (I'm new to all of this.)
If I set my phone to S-OFF, would it be better to just manually apply the updates or use an RUU?
Click to expand...
Click to collapse
Achieving s-off requires root. Root requires a custom recovery, Custom recovery requires an unlocked bootloader.
Unlocking the bootloader will void your warranty if you have one.
S-OFF is not something everyone needs but its very useful when you have to flash files in case the phone is somehow bricked. If you are not planning to flash custom roms or any other custom files I would recommend staying S-ON. In the worst case, you'll have to pay 25$ for s-off if you really need it later.
better to use the RUU to update the phone imo, much faster than applying all ota updates from your current version. The only downside of using a ruu is that it will wipe your phone data (which shouldn't be a big issue since your phone is 1 day old). Much convenient to update using ota update after so you'll not have to deal with the wipe each time.

alray said:
Achieving s-off requires root. Root requires a custom recovery, Custom recovery requires an unlocked bootloader.
Unlocking the bootloader will void your warranty if you have one.
S-OFF is not something everyone needs but its very useful when you have to flash files in case the phone is somehow bricked. If you are not planning to flash custom roms or any other custom files I would recommend staying S-ON. In the worst case, you'll have to pay 25$ for s-off if you really need it later.
better to use the RUU to update the phone imo, much faster than applying all ota updates from your current version. The only downside of using a ruu is that it will wipe your phone data (which shouldn't be a big issue since your phone is 1 day old). Much convenient to update using ota update after so you'll not have to deal with the wipe each time.
Click to expand...
Click to collapse
I am having trouble finding an RUU for the google play edition. I've been googling and searching the forums for a while now, but most of the RUU's and ROMs I find are for the Sense version. Would the RUU here: http://forum.xda-developers.com/showthread.php?t=2358781 work?

nocipher said:
I am having trouble finding an RUU for the google play edition. I've been googling and searching the forums for a while now, but most of the RUU's and ROMs I find are for the Sense version. Would the RUU here: http://forum.xda-developers.com/showthread.php?t=2358781 work?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B17smFr95pleX29Wamg2c3pRWTQ/view?pli=1

Thanks for the all the help! I used the RUU to update to 5.0.1. That, unfortunately, did not allow an OTA update directly, but I did manage to sideload the 5.1 update via abd.

Black/White Screen and freeze boot up after OTA

Hi guys i had problem, few days ago phone notify me about update, i thought ok it nice, I restored stock recovery and I relocked bootloader in fastboot.
I clicked the install , process ran without errors. in stock recovery and BANG 3-4 first times phone stopped on boot, i tried factory reset after boot phone giving me black screen, next I tried to flash RUU's.
Before update a I had 7.19.401.22, i flashed this version - not working, flashed 7.19.401.2 - not working, flashed 7.19.401.30 - not working although it ,the same version is after update.
I don't know what to do :crying:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.30
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH37RW902282
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 3730mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Flashed RUU's
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.22_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430964_signed.zip
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.30_Radio_4T.35.3218.16_10.33Q.1718.01L_release_449611_combined_signed.zip

Jakqa said:
Hi guys i had problem, few days ago phone notify me about update, i thought ok it nice, I restored stock recovery and I relocked bootloader in fastboot.
I clicked the install , process ran without errors. in stock recovery and BANG 3-4 first times phone stopped on boot, i tried factory reset after boot phone giving me black screen, next I tried to flash RUU's.
Before update a I had 7.19.401.22, i flashed this version - not working, flashed 7.19.401.2 - not working, flashed 7.19.401.30 - not working although it ,the same version is after update.
I don't know what to do :crying:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.30
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH37RW902282
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 3730mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Flashed RUU's
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.22_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430964_signed.zip
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.30_Radio_4T.35.3218.16_10.33Q.1718.01L_release_449611_combined_signed.zip
Click to expand...
Click to collapse
The ota caused a bootloop because you have installed it on a rooted phone. Unlike older updates (6.xx.xxx.x and before), you can't simply reflash the stock recovery to update. Lollipop updates can only be installed on 100% stock and non-rooted rom. That wasn't a problem in the past but its now a well know problem with all newer updates.
Your version-main is now 7.19.401.30 because, unlike the software, the firmware updated fine. You can't flash the 7.19.401.22 RUU because its now a downgrade in version (because your firmware got updated). Downgrading using a RUU requires S-OFF, your phone is S-ON. Same reason why the 7.19.401.2 won't work.
7.19.401.30 ruu is a "combined" RUU so it can't be flashed on a s-on phone.
Your option are:
unlock the bootloader, flash twrp recovery and flash a rom
or achieve s-off using sunshine and flash the .22 or the .30 ruu (you'll need to do option 1 first because you need a working rom to be able to s-off the phone)
Or maybe someone already uploaded a nandroid backup of 7.19.401.30. If you find one you can restore the backup using a custom recovery and then reflash the stock recovery.

alray said:
The ota caused a bootloop because you have installed it on a rooted phone. Unlike older updates (6.xx.xxx.x and before), you can't simply reflash the stock recovery to update. Lollipop updates can only be installed on 100% stock and non-rooted rom. That wasn't a problem in the past but its now a well know problem with all newer updates.
Your version-main is now 7.19.401.30 because, unlike the software, the firmware updated fine. You can't flash the 7.19.401.22 RUU because its now a downgrade in version (because your firmware got updated). Downgrading using a RUU requires S-OFF, your phone is S-ON. Same reason why the 7.19.401.2 won't work.
7.19.401.30 ruu is a "combined" RUU so it can't be flashed on a s-on phone.
Your option are:
unlock the bootloader, flash twrp recovery and flash a rom
or achieve s-off using sunshine and flash the .22 or the .30 ruu (you'll need to do option 1 first because you need a working rom to be able to s-off the phone)
Or maybe someone already uploaded a nandroid backup of 7.19.401.30. If you find one you can restore the backup using a custom recovery and then reflash the stock recovery.
Click to expand...
Click to collapse
1.What Kind of rom? Stock or custom - without s-off?
3.Do You know anyone who could upload a backup of 7.19.401.30?

Jakqa said:
1.What Kind of rom? Stock or custom - without s-off?
3.Do You know anyone who could upload a backup of 7.19.401.30?
Click to expand...
Click to collapse
1.a stock or stockish rom is best if you want to achieve s-off, You don't need s-off to flash a custom rom, only an unlocked bootloader + a custom recovery.
3. No, might want to ask in the update thread in the general section (see sticky threads)

Trying to return to stock, loosing my hair!

Hi all,
So ill try to keep this brief as its long...
Im trying to sell my phone, so i want to return it to stock ROM, please tell me how, i used an RUU last time but nothing now seems to work. My phone is the HTC one M7
*** TAMPERED ***
*** UNLOCKED ***
*** SECURITY (something) ***
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4171mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
TWRP Recovery,
I have the HTC dev unlock, i have rooted in the past but i just cant install the correct version to use OTA's without my phone bricking! it was a UK 3 (H3G) but is now 'unlocked'
in short, can someone please tell me which RUU i need to get stock ROM and be able to use OTA's without bricking!
many thanks

stevey88 said:
Hi all,
So ill try to keep this brief as its long...
Im trying to sell my phone, so i want to return it to stock ROM, please tell me how, i used an RUU last time but nothing now seems to work. My phone is the HTC one M7
*** TAMPERED ***
*** UNLOCKED ***
*** SECURITY (something) ***
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4171mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
TWRP Recovery,
I have the HTC dev unlock, i have rooted in the past but i just cant install the correct version to use OTA's without my phone bricking! it was a UK 3 (H3G) but is now 'unlocked'
in short, can someone please tell me which RUU i need to get stock ROM and be able to use OTA's without bricking!
many thanks
Click to expand...
Click to collapse
Relock your bootloader then flash the 7.19.401.22 ruu. You can find this ruu in the general section of the M7 forum (look at sticky thread, there is a lollipop ruu thread). You'll find the 7.19.401.22 ruu at post #2 of that thread and instructions how to flash it at post #1.
The bootloader will still show ***tampered*** and ***relocked*** (as opposed to ***locked***) even after flashing the ruu. If you want to remove the tampered banner and set the bootloader back to locked instead of relocked, you'll nee to use Sunshine in order to s-off the phone.

alray said:
Relock your bootloader then flash the 7.19.401.22 ruu. You can find this ruu in the general section of the M7 forum (look at sticky thread, there is a lollipop ruu thread). You'll find the 7.19.401.22 ruu at post #2 of that thread and instructions how to flash it at post #1.
The bootloader will still show ***tampered*** and ***relocked*** (as opposed to ***locked***) even after flashing the ruu. If you want to remove the tampered banner and set the bootloader back to locked instead of relocked, you'll nee to use Sunshine in order to s-off the phone.
Click to expand...
Click to collapse
Thanks alray for your quick response! im sorry its taken me so long to reply, i finally managed to get the .zip to the phone (pc not speaking to phone) however when i try to install from zip file in TWRP, it begins to flash the first file and then reboots immediately every time.
I relocked my bootloader as you said but then i can no longer access TWRP to flash the .zip file, also i cant use ADB to flash.
I tried to unlock it again to reflash the latest TWRP recovery, again still cant load the zip file via the install zip option in TWRP, i then tried to use adb sideload, it can see my device but all i get is "adb cannot read sideload", i have made sure i have the correct file name and extension etc.. im out of ideas!
I have managed to transfer it across but i just cannot install this zip!
*update
may have used the wrong zip, but for the life of me i cannot move the correct one to my phone, as far as i know i cannot transfer a .zip with fastboot, adb see's my device as 'offline' (using 1.0.31) and i cannot simply drag and drop using recovery as "Cannot copy item, devices has stopped responding..." seems to be only for files over certain sizes though.
how can i move this file?

stevey88 said:
when i try to install from zip file in TWRP
Click to expand...
Click to collapse
Your problem flashing the ruu is simple: you didn't take the time to read the instructions how to flash (available at post 1 of the same thread from where you have downloaded the ruu) at all, or you wouldn't be talking about twrp. Ruu are flashed using fastboot. Would be to long to rewrite everything since I'm using my phone now, but everything including the appropriate commands are posted there.

alray said:
Your problem flashing the ruu is simple: you didn't take the time to read the instructions how to flash (available at post 1 of the same thread from where you have downloaded the ruu) at all, or you wouldn't be talking about twrp. Ruu are flashed using fastboot. Would be to long to rewrite everything since I'm using my phone now, but everything including the appropriate commands are posted there.
Click to expand...
Click to collapse
you're correct, i completely missed the auto collapse walkthru, i followed it and it worked! many thanks, phone is back to stock and OTA's work again!.
Thanks for your help!

Need help to update firmware.

I'm trying to update my firmware before updating to ARHD 93.0 from 91.0 and I have a few questions. I'm trying to figure out how to update my firmware, but I can't seem to find any firmware.zip for my phone model. What i can find though, are RUUs for it, specifically 7.21.707.5 and 7.21.707.21. I want to know if these are the correct and the latest ones and which one I should use first if they are correct, since I heard that you need to update the firmware incrementally. I'm also not sure if using these would revert my phone back to S-ON and unrooted, so I hope someone can clarify me on this. Thanks and fastboot getvar all results are as follows.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.707.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4177mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Azraelos said:
I'm trying to update my firmware before updating to ARHD 93.0 from 91.0 and I have a few questions. I'm trying to figure out how to update my firmware, but I can't seem to find any firmware.zip for my phone model. What i can find though, are RUUs for it, specifically 7.21.707.5 and 7.21.707.21. I want to know if these are the correct and the latest ones and which one I should use first if they are correct, since I heard that you need to update the firmware incrementally. I'm also not sure if using these would revert my phone back to S-ON and unrooted, so I hope someone can clarify me on this. Thanks and fastboot getvar all results are as follows.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.707.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4177mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
You don't need to flash incrementally when using a RUU and the only thing you need to flash a 7.xx.707.x RUU is a 6.xx.707.x firmware already on the phone (which you have). Install the newer RUU (.21) then take all the ota updates (should have 2, one from .21 to .30 and another one from .30 to .51). Flashing a RUU doesn't affect S-ON/S-OFF status neither the unlocked bootloader but you'll obviously loose root since flashing a RUU will flash the /system partition back to stock which is where are stored the SU binaries. Anyway this is not really an issue since ARHD is a pre-rooted rom so after youv got your firmware updated via the RUU and ota updates, you can reflash TWRP recovery and ARHD so your phone will be on the latest firmware + ARHD + root + S-OFF + unlocked BL.
Btw there are otther way to update your firmware like changing your MID and CID and flashing another firmware.zip version. E.g. MID to PN0710000 and cid to HTC__001 (or supercid) and flash the 7.19.401.2 full firmware.zip then TWRP and finally ARHD.
Both methods will make your phone ready for latest roms like ARHD.

Thanks for the reply For the 1st method, how do I go about getting the OTA updates? Does flashing the RUU mean my phone will have the stock ROM and I can just download them through HTC? For the 2nd method, if I change the MID and CID to what you said, the existing firmware will still be the same right? I thought you could only upgrade the firmware with the same middle numbers, eg. 6.xx.401.x to 7.xx.401.x and not 6.xx.707.x to 7.xx.401.x even when you change the MID and CID.

Azraelos said:
Thanks for the reply For the 1st method, how do I go about getting the OTA updates? Does flashing the RUU mean my phone will have the stock ROM and I can just download them through HTC?
Click to expand...
Click to collapse
Yes.
For the 2nd method, if I change the MID and CID to what you said, the existing firmware will still be the same right?
Click to expand...
Click to collapse
Yes, until you flash another firmware...
I thought you could only upgrade the firmware with the same middle numbers, eg. 6.xx.401.x to 7.xx.401.x and not 6.xx.707.x to 7.xx.401.x even when you change the MID and CID.
Click to expand...
Click to collapse
Not if you change the CID and MID. But it must be a firmware compatible with your variant (M7_UL) and you must convert by using a complete(full) firmware.zip file, not using a firmware.zip that was extracted from an ota update (these kind of firmware.zip must be flashed incrementally). Acomplete firmware.zip (as opposed to a firmware.zip extracted from an OTA) will be about 40-50 Mb like this one. So if going for option #2: Change CID to one of the CID compatible with x.xx.401.x base (or supercid), change MID to PN0710000, flash that 7.19.401.2 firmware, then reflash twrp and finally ARHD.