Database Develop

[Q] HTC One relocked, can't flash (signature error)

Hey All,
I hope you guys can help me, I'm completely lost in all these threads and posts. I've spent hours on this, literally hours...
I have a HTC One M7 (bought in Belgium) which I wanted to return to stock because of a faulty speaker (I just rooted the standard image). So I relocked the bootloader to flash an RUU. I tried flashing several European RUUs from the xda collection, but nothing worked. I also tried a zipped firmware, and it also fails. I always get this error:
FAILED remote: 12 signature verify fail
I'm stuck in fastboot, it doesn't boot into the OS anymore, only fastboot.
Getvar output:
C:\ADT\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4024mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.051s
I try to flash the RUU Zip M7_UL_JB_50_HTC_Europe_1.29.401.16_R_Radio_4A.14.3250.13_10.33.1150.01_release_318486_signed_2_4_decrypted.zip
Strange thing is, when I check the zip's android-info:
modelid: PN0710000
cidnum: HTC__001
cidnum: HTC__E11
...
So I don't get anymore why it would fail a signature check...
I also tried flashing a newer version, this didn't work either. What makes matters worse, the battery keeps uncharging as I continue to struggle...
Tell it to me straight, doctor... Is my HTC doomed to be a paperweight?

What do you mean "flash a RUU" ? Is it you try to fastboot flash the RUU ? It won't work that way.
Checking this : http://www.androidruu.com/?developer=M7
I see there is only one RUU that may work for you : RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
What you need to do:
1- in fastboot mode - relock the bootloader : run command fastboot oem lock (you did this already)
2- in fastboot mode - flash/run/double click the RUU; follow the updater instruction - next,update,bla,bla,bla until it finish

ckpv5 said:
What do you mean "flash a RUU" ? Is it you try to fastboot flash the RUU ? It won't work that way.
Checking this :
I see there is only one RUU that may work for you : RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
What you need to do:
1- in fastboot mode - relock the bootloader : run command fastboot oem lock (you did this already)
2- in fastboot mode - flash/run/double click the RUU; follow the updater instruction - next,update,bla,bla,bla until it finish
Click to expand...
Click to collapse
First of all, thanks a bunch for taking the time to respond.
I'm currently downloading the proposed RUU and will try flashing it.
I don't understand, however, why my downloaded RUUs wouldn't work since the CID and model corresponded?
I tried both methods: using the RUU to flash and using the fastboot oem rebootRUU > flash zip.

dwarfstrider said:
First of all, thanks a bunch for taking the time to respond.
I'm currently downloading the proposed RUU and will try flashing it.
I don't understand, however, why my downloaded RUUs wouldn't work since the CID and model corresponded?
I tried both methods: using the RUU to flash and using the fastboot oem rebootRUU > flash zip.
Click to expand...
Click to collapse
When your device is S-ON, you need a correct version RUU i.e 1.29.401.16 (which is not available, I believe), so you should go for a higher version not lower version.
I'm new to HTC One too so not so sure about fastboot oem rebootRUU, but I believe it needs a S-OFF device to work but yours is S-ON.
More info : http://forum.xda-developers.com/showthread.php?t=2358738

ckpv5 said:
When your device is S-ON, you need a correct version RUU i.e 1.29.401.16 (which is not available, I believe), so you should go for a higher version not lower version.
I'm new to HTC One too so not so sure about fastboot oem rebootRUU, but I believe it needs a S-OFF device to work but yours is S-ON.
[/url]
Click to expand...
Click to collapse
That RUU doesn't work, after checking the signature I get: ERROR [158]: IMAGE ERROR...

dwarfstrider said:
That RUU doesn't work, after checking the signature I get: ERROR [158]: IMAGE ERROR...
Click to expand...
Click to collapse
Search for ERROR 158 may help you.
What I understand ERROR 158 maybe because the bootloader is not relocked, not using USB2.0, maybe also a modified hboot (usually the one that remove the red text warning) is installed prior to running the RUU, not running the RUU in Admin Privilege mode.
Maybe someone else have better idea, have to wait for that.

What I understand ERROR 158 maybe because the bootloader is not relocked, not using USB2.0
- No, I locked using fastboot oem lock with USB cable.
maybe also a modified hboot (usually the one that remove the red text warning) is installed prior to running the RUU
- Afaik, I never installed a custom hboot myself. I get the red text warning at the white HTC screen.
not running the RUU in Admin Privilege mode.
- Nope, the RUU runs with admin privileges in Win 7
Maybe someone else have better idea, have to wait for that.
- Let's hope so :laugh:

This is what my phone looks like atm:
i.imgur.com/ bX9MFM3.jpg
(can't post pics/links yet, sorry)
Please guys, help a fella out... I will be forever grateful

Update: I unlocked my phone again with the unlock bin from HTCDev and now it boots again...
I suppose I need to do S-OFF with revone since I'm at 1.44, but unsure. Damn this stuff is confusing.

You will need to flash new firmware I saw a hierarchy of htc one's Ruu firmware list on android revolution site.
Just check in the name of the correct ruu you downloaded and try to match the numbers of your Ruu with the list given there. I hope it may help you or if you get confused Pm me.
Sent from my HTC One using XDA Premium 4 mobile app

OK, I solved it.
So I did an S-OFF with revone, then locked and removed tampered (also revone).
Then I flashed a good RUU. It took ages to find a good one, followed another thread (2325010) on the forum which I can't link because of the restrictions .
Then I used thread 1672425 to put S-ON again and now my One it back to full stock!

[Q] Can't S-ON?

After the struggle of finding a way to revert my Vodafone Australia branded HTC One back to it's former, virgin glory..
I have finally locked the bootloader, set my CID back and got a stock ROM and recovery - thanks to Guru Stock Reset ROMs, which is the closest thing I could get to being stock as there are no available RUU's.
But the last and final hurdle is S-ON. My Googling tells me all it takes is this fastboot command: "fastboot oem writesecureflag 3"
But when I throw that in a command prompt, all I get is an error:
(bootloader) partition hboot signature error
(bootloader) writesecureflag: partitions siganture failed
OKAY [ 1.624s]
finished. total time: 1.625s
Could anyone please help? I have to return my diseased pink/purple-tinted, crappy camera issue!

Jikstah said:
After the struggle of finding a way to revert my Vodafone Australia branded HTC One back to it's former, virgin glory..
I have finally locked the bootloader, set my CID back and got a stock ROM and recovery - thanks to Guru Stock Reset ROMs, which is the closest thing I could get to being stock as there are no available RUU's.
But the last and final hurdle is S-ON. My Googling tells me all it takes is this fastboot command: "fastboot oem writesecureflag 3"
But when I throw that in a command prompt, all I get is an error:
(bootloader) partition hboot signature error
(bootloader) writesecureflag: partitions siganture failed
OKAY [ 1.624s]
finished. total time: 1.625s
Could anyone please help? I have to return my diseased pink/purple-tinted, crappy camera issue!
Click to expand...
Click to collapse
wow, brick alert!
you have a modded hboot in there, so you're obviously not as stock as you'd like to think. better you rethink your strategy, and/or check my guide http://forum.xda-developers.com/showthread.php?t=2541082

nkk71 said:
wow, brick alert!
you have a modded hboot in there, so you're obviously not as stock as you'd like to think. better you rethink your strategy, and/or check my guide http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
Damn dude, how far am I from a brick? :S
and you are absolutely correct, I completely forgot about my hboot being modified at 1.55.
It's been awhile since I tampered around with my phone.
Is it then possible to downgrade my hboot to 1.44, with my current set-up? and continue to s-on?
I thank you immensely.

Jikstah said:
Damn dude, how far am I from a brick? :S
and you are absolutely correct, I completely forgot about my hboot being modified at 1.55.
It's been awhile since I tampered around with my phone.
Click to expand...
Click to collapse
Luckily the signature check kept you away from a brick, had you been able to S-On with a modded hboot, then you would have had a brick.
Jikstah said:
Is it then possible to downgrade my hboot to 1.44, with my current set-up? and continue to s-on?
Click to expand...
Click to collapse
I'm not sure what method you used to return to stock, but obviously hboot is not stock, and so could other things as well; I would recommend following my guide, especially if you intend on going S-On.
If you do want to follow my guide, post a "fastboot getvar all" (excluding IMEI and s/n), and I'll let you know which files you need.

nkk71 said:
I'm not sure what method you used to return to stock, but obviously hboot is not stock, and so could other things as well; I would recommend following my guide, especially if you intend on going S-On.
If you do want to follow my guide, post a "fastboot getvar all" (excluding IMEI and s/n), and I'll let you know which files you need.
Click to expand...
Click to collapse
I mean no offence in not wanting to follow your guide, it's great - especially for those less knowledgeable, and in need.
So here's my getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 3782mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.067s
Surely I'm close?! Thanks again.

Jikstah said:
I mean no offence in not wanting to follow your guide, it's great - especially for those less knowledgeable, and in need.
So here's my getvar:
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
Surely I'm close?! Thanks again.
Click to expand...
Click to collapse
no offense taken
but you have PN0714000 + VODAP021 and firmware 3.62.401.1 (.401. = WWE unbranded), so you need to get your firmware correct too; inline with the ROM you are now on.
and personally, I don't recommend going S-Off to S-On on hboot 1.55, sometimes it works fine, but sometimes it triggers "tamper detected" and the tampered is back (can't say when/if it will happen to you)

nkk71 said:
no offense taken
but you have PN0714000 + VODAP021 and firmware 3.62.401.1 (.401. = WWE unbranded), so you need to get your firmware correct too; inline with the ROM you are now on.
and personally, I don't recommend going S-Off to S-On on hboot 1.55, sometimes it works fine, but sometimes it triggers "tamper detected" and the tampered is back (can't say when/if it will happen to you)
Click to expand...
Click to collapse
Ugh, more complications.. back to the drawing board it is!
So looks like all I need is firmware and hboot?
But do you reckon, the repair center will pay any attention to these attributes? I've heard all they check is S-ON, tamper flags and unlocked bootloaders?

Jikstah said:
Ugh, more complications.. back to the drawing board it is!
So looks like all I need is firmware and hboot?
But do you reckon, the repair center will pay any attention to these attributes? I've heard all they check is S-ON, tamper flags and unlocked bootloaders?
Click to expand...
Click to collapse
hboot will be part of the firmware.zip,
and I don't know what they will check, but you may have a problem when it comes back -> if you're S-On, LOCKED bootloader with firmware not matching your MID and CID, then chances are high that HTCDev won't unlock your phone.

nkk71 said:
hboot will be part of the firmware.zip,
and I don't know what they will check, but you may have a problem when it comes back -> if you're S-On, LOCKED bootloader with firmware not matching your MID and CID, then chances are high that HTCDev won't unlock your phone.
Click to expand...
Click to collapse
Okay, well that simplifies things..
Now I just have to find a firmware.zip
You're pretty well-versed, I must thank you again for your foresight.

Jikstah said:
Okay, well that simplifies things..
Now I just have to find a firmware.zip
You're pretty well-versed, I must thank you again for your foresight.
Click to expand...
Click to collapse
I'm assuming you used Guru ROM 2.24.980.2 ? i made a quick search but came up empty on the firmware for that. you could pull it from the OTA file if you find it; within the OTA.ZIP is another firmware.zip <- that's signed original firmware

nkk71 said:
I'm assuming you used Guru ROM 2.24.980.2 ? i made a quick search but came up empty on the firmware for that. you could pull it from the OTA file if you find it; within the OTA.ZIP is another firmware.zip <- that's signed original firmware
Click to expand...
Click to collapse
Rejoice! For I have found the exact firmware for the ROM - http://forum.xda-developers.com/showpost.php?p=44452049&postcount=438
Google is truly a wonderful thing, and you Mr. nkk71.

Jikstah said:
Rejoice! For I have found the exact firmware for the ROM - http://forum.xda-developers.com/showpost.php?p=44452049&postcount=438
Google is truly a wonderful thing, and you Mr. nkk71.
Click to expand...
Click to collapse
Nice find :good: :good:
don't forget to flash it twice:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
and since firmware & ROM are 2.xx (hboot 1.54), going from S-Off to S-On should be safe

nkk71 said:
Nice find :good: :good:
don't forget to flash it twice:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
and since firmware & ROM are 2.xx (hboot 1.54), going from S-Off to S-On should be safe
Click to expand...
Click to collapse
Oh jeez, here we go. I put the firmware.zip into my sd card, pulled up a cmd, entered rebootRUU mode, and tried to flash firmware zip.
And...
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (28294 KB)...
OKAY [ 2.210s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 2.701s
What's wrong with my CID? I even changed it from VODAP021 to HTC__039 to see if it would run, still the same error.. :|
EDIT: Okay so I SuperCID'ed, it worked however my bootloader is still 1.55? wut.
Don't tell me I need an unlocked bootloader, I need an unlocked bootloader right? -_-
I believe you said HTCdev won't unlock it if I had a non-matching firmware to my CID/MID? ugh.
EDIT: NOPE, no luck either with an unlocked bootloader - same result.

Jikstah said:
Oh jeez, here we go. I put the firmware.zip into my sd card, pulled up a cmd, entered rebootRUU mode, and tried to flash firmware zip.
And...
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (28294 KB)...
OKAY [ 2.210s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 2.701s
What's wrong with my CID? I even changed it from VODAP021 to HTC__039 to see if it would run, still the same error.. :|
EDIT: Okay so I SuperCID'ed, it worked however my bootloader is still 1.55? wut.
Don't tell me I need an unlocked bootloader, I need an unlocked bootloader right? -_-
I believe you said HTCdev won't unlock it if I had a non-matching firmware to my CID/MID? ugh.
EDIT: NOPE, no luck either with an unlocked bootloader - same result.
Click to expand...
Click to collapse
You do realize those errors/safe-guards are actually saving you!!
There's nothing wrong with your CID, so set it back to what it's supposed to be.
And the reason it's not working (actually it is), you are flashing the wrong firmware.zip, the one you are flashing is 28294 KB (probably a modded one), whereas the one you should be flashing (from the link you posted earlier) is 41197KB.
now put the correct firmware.zip in your adb/fastboot folder and flash it, fastboot doesn't use anything from your sdcard, it uses the files on your PC.

nkk71 said:
You do realize those errors/safe-guards are actually saving you!!
There's nothing wrong with your CID, so set it back to what it's supposed to be.
And the reason it's not working (actually it is), you are flashing the wrong firmware.zip, the one you are flashing is 28294 KB (probably a modded one), whereas the one you should be flashing (from the link you posted earlier) is 41197KB.
now put the correct firmware.zip in your adb/fastboot folder and flash it, fastboot doesn't use anything from your sdcard, it uses the files on your PC.
Click to expand...
Click to collapse
Gosh, you are too good. This is definitely the big break.
But nope, freakin' adb decides to bail on me and my device can no longer be detected. WTF?! What have I done to deserve such trouble.. -_-

HTC one M7 continuously reboots till battery drains

I am having problem with my htc one. It continuously reboots. Displays HTC Logo then O2 then Beats audio and then restart.
The things which I have tried doing are
after volume down and pressing power button factory reset, in fast boot rebooted the boot loader. When I go into the recovery it gives red triangle with an exclamation mark in the middle.
I tried connecting it with adb but it says
List of devices attached and then empty no device
adb shell gives
error: device not found
I tried fastboot devices -> this displays
W910109 fastboot
D:\adb>fastboot getvar all
(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.24.206.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA386W910109
(bootloader) imei: 357864053760359
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.117s
Can anyone help me in the matter. My device warranty is void. All I want it to go back to factory reset.
thanks

hammaad110 said:
I am having problem with my htc one. It continuously reboots. Displays HTC Logo then O2 then Beats audio and then restart.
The things which I have tried doing are
after volume down and pressing power button factory reset, in fast boot rebooted the boot loader. When I go into the recovery it gives red triangle with an exclamation mark in the middle.
I tried connecting it with adb but it says
List of devices attached and then empty no device
adb shell gives
error: device not found
I tried fastboot devices -> this displays
W910109 fastboot
D:\adb>fastboot getvar all
(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.24.206.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA386W910109
(bootloader) imei: 357864053760359
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.117s
Can anyone help me in the matter. My device warranty is void. All I want it to go back to factory reset.
thanks
Click to expand...
Click to collapse
Did you do a factory reset? If so you will need to reflash the rom.

zelendel said:
Did you do a factory reset? If so you will need to reflash the rom.
Click to expand...
Click to collapse
i have tried doing factory reset but it stops giving a red triangle with an exclamation mark.
i would be glad if you can guide me to the steps regarding reflashing the rom.

hammaad110 said:
I am having problem with my htc one. It continuously reboots. Displays HTC Logo then O2 then Beats audio and then restart.
The things which I have tried doing are
after volume down and pressing power button factory reset, in fast boot rebooted the boot loader. When I go into the recovery it gives red triangle with an exclamation mark in the middle.
I tried connecting it with adb but it says
List of devices attached and then empty no device
adb shell gives
error: device not found
I tried fastboot devices -> this displays
W910109 fastboot
D:\adb>fastboot getvar all
(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.24.206.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA386W910109
(bootloader) imei: 357864053760359
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.117s
Can anyone help me in the matter. My device warranty is void. All I want it to go back to factory reset.
thanks
Click to expand...
Click to collapse
waiting for assistance

hammaad110 said:
waiting for assistance
Click to expand...
Click to collapse
Search the site. Everything you need has already been posted.

zelendel said:
Search the site. Everything you need has already been posted.
Click to expand...
Click to collapse
I have downloaded the RUU file
htc1guru.com/dld/ruu_m7_ul_k44_sense55_mr_o2_uk_4-20-206-16_radio_4a-23-3263-28_10-38r-1157-04l_release_353143_signed_2-exe
for modelid: PN0710000
cidnum: O2___001
I executed the file while in Fastboot usb mode. The file gave different messages and told me that going to urgrade the ROM to 4.xx. Then it asked me to press next. When I pressed next it restarted the phone and it again went into the infinite loop on restating. while the PC screen was saying waiting for the bootloader and then after 2 or 3 min it said that error in the USB connection.
the phone says MY HTC in Android USB devices when its in Fastboot mode while in normal boot loader mode its not detected. Also adb does not gives anything when i give command adb devices. However Fastboot devices gives serial number if the device.

hammaad110 said:
I have downloaded the RUU file
htc1guru.com/dld/ruu_m7_ul_k44_sense55_mr_o2_uk_4-20-206-16_radio_4a-23-3263-28_10-38r-1157-04l_release_353143_signed_2-exe
for modelid: PN0710000
cidnum: O2___001
I executed the file while in Fastboot usb mode. The file gave different messages and told me that going to urgrade the ROM to 4.xx. Then it asked me to press next. When I pressed next it restarted the phone and it again went into the infinite loop on restating. while the PC screen was saying waiting for the bootloader and then after 2 or 3 min it said that error in the USB connection.
the phone says MY HTC in Android USB devices when its in Fastboot mode while in normal boot loader mode its not detected. Also adb does not gives anything when i give command adb devices. However Fastboot devices gives serial number if the device.
Click to expand...
Click to collapse
I would remove all the drivers and start from scratch. FIrst thing you will need to get working is your adb drivers on your PC. Make sure to be running windows 7, uninstall all android drivers, reboot PC, then plug in the android in bootloader mode and let the OS install the needed drivers.

zelendel said:
I would remove all the drivers and start from scratch. FIrst thing you will need to get working is your adb drivers on your PC. Make sure to be running windows 7, uninstall all android drivers, reboot PC, then plug in the android in bootloader mode and let the OS install the needed drivers.
Click to expand...
Click to collapse
Done that. it only detects a hardware in fastboot mode and no device is detected in bootloader mode.

hammaad110 said:
Done that. it only detects a hardware in fastboot mode and no device is detected in bootloader mode.
Click to expand...
Click to collapse
Then something is wrong with your driver set up. Check the threads in this section of other ways to get it working. I know that if you had HTC sync installed that it would cause these issues. I have never had this issue where what I discribed above didnt fix

hammaad110 said:
Done that. it only detects a hardware in fastboot mode and no device is detected in bootloader mode.
Click to expand...
Click to collapse
could you define the difference between "fastboot mode" and "bootloader mode"?
if you are in bootloader and it says FASTBOOT USB (in red), it will detect your device

nkk71 said:
could you define the difference between "fastboot mode" and "bootloader mode"?
if you are in bootloader and it says FASTBOOT USB (in red), it will detect your device
Click to expand...
Click to collapse
Yes my device is detected in FASTBOOT USB but is not detected in ADB devices even in BOOTLOADER
since my bootloader is LOCKED. I had tried unlocking it through htcdev procedure but after the procedure and pressing ok on device it again says LOCKED
so I cannot UNLOCK the bootloader and thus cannot install custom recovery.
What should I do now

hammaad110 said:
Yes my device is detected in FASTBOOT USB but is not detected in ADB devices even in BOOTLOADER
since my bootloader is LOCKED. I had tried unlocking it through htcdev procedure but after the procedure and pressing ok on device it again says LOCKED
so I cannot UNLOCK the bootloader and thus cannot install custom recovery.
What should I do now
Click to expand...
Click to collapse
you should redo all the unlocking procedure try that

hammaad110 said:
Yes my device is detected in FASTBOOT USB but is not detected in ADB devices even in BOOTLOADER
since my bootloader is LOCKED. I had tried unlocking it through htcdev procedure but after the procedure and pressing ok on device it again says LOCKED
so I cannot UNLOCK the bootloader and thus cannot install custom recovery.
What should I do now
Click to expand...
Click to collapse
not sure what you mean, but:
fastboot commands work in bootloader (FASTBOOT USB on the phone screen), adb does not
adb commands work in custom recovery
adb commands work in booted up phone with USB debuggin enabled

hammaad110 said:
Yes my device is detected in FASTBOOT USB but is not detected in ADB devices even in BOOTLOADER
since my bootloader is LOCKED. I had tried unlocking it through htcdev procedure but after the procedure and pressing ok on device it again says LOCKED
so I cannot UNLOCK the bootloader and thus cannot install custom recovery.
What should I do now
Click to expand...
Click to collapse
As I explained in our pm's you need to be on hboot 1.55 to use that ruu.
To get your phone unlocked I think you need to flash firmware to refresh your hboot. But unfortunately there isn't any available any where unless @nkk71 knows where you might find it.
With your phone in its current state there is no way for you to use adb, since it won't work in stock recovery. I'm considering going out of my way to help you out here but let's see if nkk71 has anything first.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk

Danny201281 said:
As I explained in our pm's you need to be on hboot 1.55 to use that ruu.
To get your phone unlocked I think you need to flash firmware to refresh your hboot. But unfortunately there isn't any available any where unless @nkk71 knows where you might find it.
With your phone in its current state there is no way for you to use adb, since it won't work in stock recovery. I'm considering going out of my way to help you out here but let's see if nkk71 has anything first.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
I haven't looked much, but didn't see any 2.24.206.7 or higher firmware.zip in the usual places... it may be out there but i didn't see it.
hammaad110 said:
since my bootloader is LOCKED. I had tried unlocking it through htcdev procedure but after the procedure and pressing ok on device it again says LOCKED
so I cannot UNLOCK the bootloader and thus cannot install custom recovery.
What should I do now
Click to expand...
Click to collapse
wait, i guess i misunderstood, are you saying HTCdev bootloader unlock is no longer working?? (can you copy/paste command prompt output of that, don't forget to get a new token)
can you also copy/paste the command prompt output of "fastboot oem rebootRUU", do you actually get to ruu mode:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if you can get to RUU mode, you should try to get the RUU to work.
the 4.xx RUUs are OK, but are very picky about PC configuration, USB ports, etc.

nkk71 said:
I haven't looked much, but didn't see any 2.24.206.7 or higher firmware.zip in the usual places... it may be out there but i didn't see it.
wait, i guess i misunderstood, are you saying HTCdev bootloader unlock is no longer working?? (can you copy/paste command prompt output of that, don't forget to get a new token)
can you also copy/paste the command prompt output of "fastboot oem rebootRUU", do you actually get to ruu mode:
if you can get to RUU mode, you should try to get the RUU to work.
the 4.xx RUUs are OK, but are very picky about PC configuration, USB ports, etc.
Click to expand...
Click to collapse
Hi nkk71, I had the same problem with my friends O2uk m7, When it comes helpful files there doesn't seem to be anything for O2.
The bootloader unlocking goes fine up untill the the point he selects "yes" to unlock on the phone. The phone reboots but is still locked.
The RUU in question is an exe I used it myself after many hours of of failing with error 12 signature verification failed, with hboot 1.57. it's the same with this situation. Eventually my friend decided to pay for the sunshine app so I could s-off the device and I finally got the ruu to work by, changing the cid to HTC__001 I then manipulated the firmware using 401 WWE firmware to bring the phone to hboot 1.55. I then changed the cid back to O2__001 and the RUU worked.
So I think he needs the 3.xx.206.x firmware to run the ruu.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk

Danny201281 said:
Hi nkk71, I had the same problem with my friends O2uk m7, When it comes helpful files there doesn't seem to be anything for O2.
The bootloader unlocking goes fine up untill the the point he selects "yes" to unlock on the phone. The phone reboots but is still locked.
The RUU in question is an exe I used it myself after many hours of of failing with error 12 signature verification failed, with hboot 1.57. it's the same with this situation. Eventually my friend decided to pay for the sunshine app so I could s-off the device and I finally got the ruu to work by, changing the cid to HTC__001 I then manipulated the firmware using 401 WWE firmware to bring the phone to hboot 1.55. I then changed the cid back to O2__001 and the RUU worked.
So I think he needs the 3.xx.206.x firmware to run the ruu.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
ah, yes, i think you're right, HTC did change some "stuff" between earlier releases and later ones, so that would explain the signature fail.
but how did the OP end up in this situation? could very well be a hardware problem... do you have any info on that? considering he's S-On / LOCKED (ie never messed with his phone), and a "semi-successful" HTCdev unlock (ie token is fine, but unlock doesn't unlock) does sound awfully familiar to a hardware problem
* what's the command output of "fastboot oem rebootRUU"? does it go to ruu mode?
* how did this happen?? (is it one of those "it happened suddenly" things?)

nkk71 said:
ah, yes, i think you're right, HTC did change some "stuff" between earlier releases and later ones, so that would explain the signature fail.
but how did the OP end up in this situation? could very well be a hardware problem... do you have any info on that? considering he's S-On / LOCKED (ie never messed with his phone), and a "semi-successful" HTCdev unlock (ie token is fine, but unlock doesn't unlock) does sound awfully familiar to a hardware problem
* what's the command output of "fastboot oem rebootRUU"? does it go to ruu mode?
* how did this happen?? (is it one of those "it happened suddenly" things?)
Click to expand...
Click to collapse
From our pm's
Then it may be because you need to update hboot first.
Are you running the ruu to fix a bootloop problem?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
Yes exactly. I want to clear the boot loop problem. The cellphone is of my client and I dont know exactly what he has done wrong with it. As far as he says that he only cleared some junk files and phone is in this condition.
Click to expand...
Click to collapse
I'll be honest I was considering converting my phone to O2 stock and capturing the ota's and making a few stock nandroids. A lot of trouble to help one person especially as you think it could be hardware. But it would help the O2 community as a whole so maybe worth the effort.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk

Danny201281 said:
From our pm's
Yes exactly. I want to clear the boot loop problem. The cellphone is of my client and I dont know exactly what he has done wrong with it. As far as he says that he only cleared some junk files and phone is in this condition.
Click to expand...
Click to collapse
I'll be honest I was considering converting my phone to O2 stock and capturing the ota's and making a few stock nandroids. A lot of trouble to help one person especially as you think it could be hardware. But it would help the O2 community as a whole so maybe worth the effort.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
Well not knowing the background is a real problem.
Do you happen to know the colour of the bootloader? is it a GPE bootloader... this could be another badly done Sense to GPE back to Sense conversion... therefore missing the necessary files/partitions for htcdev unlock to work (even if it's a HTC bootloader)
There is a 4.xx firmware that he could flash (has hboot 1.56 dd Nov 29 2013), though I will not recommend it, as chances of unlocking bootloader will be slim if the O2 RUU fails.
and yeah, capturing all those OTAs for O2, is going to be a bit of work... don't wanna sound selfish, but i'm in no mood for that atm... maybe if i have time on weekend i might consider it, though that is a big maybe

nkk71 said:
Well not knowing the background is a real problem.
Do you happen to know the colour of the bootloader? is it a GPE bootloader... this could be another badly done Sense to GPE back to Sense conversion... therefore missing the necessary files/partitions for htcdev unlock to work (even if it's a HTC bootloader)
There is a 4.xx firmware that he could flash (has hboot 1.56 dd Nov 29 2013), though I will not recommend it, as chances of unlocking bootloader will be slim if the O2 RUU fails.
and yeah, capturing all those OTAs for O2, is going to be a bit of work... don't wanna sound selfish, but i'm in no mood for that atm... maybe if i have time on weekend i might consider it, though that is a big maybe
Click to expand...
Click to collapse
I don't know the bootloader color sorry maybe @hammaad110 can post a picture for us?
I may have a go at capturing the otas if I can make time for it. I won't be capturing them all though may be just the 2.xx and 3.xx with Stock nandroids that would be enough for using the RUU at least and possibility of a reset zip.
Besides I already have the necessary files to make the change to O2. So I wouldn't trouble yourself with that. It was my idea so I wouldn't expect you to go to the trouble of making it happen
As for the bootloader unlocking problem I remember a similar case, although weather we came to a solution is sketchy in my memory. I seem to remember flashing the current firmware fixed the problem. I'll look through my posts and pm's to try to find it so I can clarify it. If that was the case I'll probably capture the ota's to help this guy out and maybe a few others.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk

[Q] Trouble unrooting my M7

Hello,
So I am trying to unroot my M7 and i have encountered and I thought I have overcome a number of issues. I feel that I should start from the beginning to give you all the best picture of my situation.
I purchased the phone used and it came with the pink camera issue. So after asking Mr. Google, who said that updating might solve the problem. I went ahead to try to update but only to discover that I cant because the phone is rooted.
Okay, so at that point, i decided that since I wont be benefiting from the rootedness of the phone, and spurred on with the news of a new update coming out soon, I decided to unroot and I found this guide.
htc-one (dot) wonderhowto (dot) com/how-to/return-your-rooted-unlocked-htc-one-back-factory-settings-for-warranty-repairs-0149204/
First problem I encountered was that was that adb could not find the device, so I installed the drivers. (took me a few hours)
After that I followed the guide and locked the device and turned S-on. up to this point, it is going smoothly.
Then I downloaded the RUU RUU_M7_UL_K44_SENSE55_MR_TELUS_WWE_4.19.661.8_R_Radio_4T.24.3218.09_10.26.1718.01L_release_351500_signed_2,
Problem was that it was really slow to load and after i accepted the legal contract, it would suddenly shut down with no warning or explanation.
So I jumped into the literature and installed all the C++ things and then it worked. Sounds great. Big smile on my face, until it starts to freeze at 5% header 1/5.
Great. so that is where I am stuck.
When i am at cmd and type in
C:\Users\Andrew Lee\Downloads\Desktop>cd htcone
C:\Users\Andrew Lee\Downloads\Desktop\htcone>adb push revone /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Users\Andrew Lee\Downloads\Desktop\htcone>adb push revone /data/local/tmp/
error: device not found
C:\Users\Andrew Lee\Downloads\Desktop>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Users\Andrew Lee\Downloads\Desktop>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Users\Andrew Lee\Downloads\Desktop>fastboot getvar all
(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.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4307mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
also I cannot quit bootloader on the phone. and when i go into device manager, it is under android USB devices, named my HTC and under other devices, there is two base system devices and both have the yellow icons next to it.
I have installed HTC sync in an effort to install the proper drivers and that did not work.
So I am in a pickle. I would prefer to unroot it but atp I dont care anymore, I just want to use the phone.
I have tried to use the zip RUU way of installing the RUU but because it cannot find the device, it is futile. When I plug in the phone, I do here the sound.
I am on Windows 7. I also have a Mac as an alternative.

If you have a Mac, I would use that! You don't have to deal with any driver issues on the Mac or on Linux, like the saying goes... It just works!(tm)
From what you posted, I see that you are S-ON with SuperCID, but I'm not sure what system you originally had, android version, ROM, etc. I assume you are on Telus, since you are trying to flash a Telus RUU. I also see you are trying to run revone.. Are you trying to get S-OFF, or unroot, or get the entire phone completely back to stock? What recovery do you have installed?
Also, FYI - adb doesn't work while you are in the bootloader.

commandaria said:
Hello,
So I am trying to unroot my M7 and i have encountered and I thought I have overcome a number of issues. I feel that I should start from the beginning to give you all the best picture of my situation.
I purchased the phone used and it came with the pink camera issue. So after asking Mr. Google, who said that updating might solve the problem. I went ahead to try to update but only to discover that I cant because the phone is rooted.
Okay, so at that point, i decided that since I wont be benefiting from the rootedness of the phone, and spurred on with the news of a new update coming out soon, I decided to unroot and I found this guide.
htc-one (dot) wonderhowto (dot) com/how-to/return-your-rooted-unlocked-htc-one-back-factory-settings-for-warranty-repairs-0149204/
First problem I encountered was that was that adb could not find the device, so I installed the drivers. (took me a few hours)
After that I followed the guide and locked the device and turned S-on. up to this point, it is going smoothly.
Then I downloaded the RUU RUU_M7_UL_K44_SENSE55_MR_TELUS_WWE_4.19.661.8_R_Radio_4T.24.3218.09_10.26.1718.01L_release_351500_signed_2,
Problem was that it was really slow to load and after i accepted the legal contract, it would suddenly shut down with no warning or explanation.
So I jumped into the literature and installed all the C++ things and then it worked. Sounds great. Big smile on my face, until it starts to freeze at 5% header 1/5.
Great. so that is where I am stuck.
When i am at cmd and type in
C:\Users\Andrew Lee\Downloads\Desktop>cd htcone
C:\Users\Andrew Lee\Downloads\Desktop\htcone>adb push revone /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Users\Andrew Lee\Downloads\Desktop\htcone>adb push revone /data/local/tmp/
error: device not found
C:\Users\Andrew Lee\Downloads\Desktop>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Users\Andrew Lee\Downloads\Desktop>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Users\Andrew Lee\Downloads\Desktop>fastboot getvar all
(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.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4307mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
also I cannot quit bootloader on the phone. and when i go into device manager, it is under android USB devices, named my HTC and under other devices, there is two base system devices and both have the yellow icons next to it.
I have installed HTC sync in an eff noort to install the proper drivers and that did not work.
So I am in a pickle. I would prefer to unroot it but atp I dont care anymore, I just want to use the phone.
I have tried to use the zip RUU way of installing the RUU but because it cannot find the device, it is futile. When I plug in the phone, I do here the sound.
I am on Windows 7. I also have a Mac as an alternative.
Click to expand...
Click to collapse
Did you run the command fastboot oem writesecureflag 3 and lock the bootloader? You will have to unlock the bootloader again using htc's unlock token, install custom recovery and install a guru reset (can be found on here) for version 2.24.401.1 which is what your current software is according to your fastboot getvar all
In order to send your phone for repairs, your phone must read as LOCKED and tampered message removed from your bootloader. Your CID must also be reset to the original. To do this you need s off though
To get s off follow the guides for rumrunner or firewater
Do NOT update your firmware past 1.54, its harder to obtain s off. You CAN still get it using sunshine, it costs $25 tho but is awesome and works with stock ROMs
Finally, i wouldnt do the command fastboot oem writesecureflag 3 again on later hboots ie 1.55 or above. This can reset the tamper message on the bootloader
Good luck

synt3k said:
If you have a Mac, I would use that! You don't have to deal with any driver issues on the Mac or on Linux, like the saying goes... It just works!(tm)
From what you posted, I see that you are S-ON with SuperCID, but I'm not sure what system you originally had, android version, ROM, etc. I assume you are on Telus, since you are trying to flash a Telus RUU. I also see you are trying to run revone.. Are you trying to get S-OFF, or unroot, or get the entire phone completely back to stock? What recovery do you have installed?
Also, FYI - adb doesn't work while you are in the bootloader.
Click to expand...
Click to collapse
I cant remember what is the original system it had But i think it was xposed.. It was the last application when it was listed alphabetically. The phone was originally telus, but I am on rogers. i was not sure with RUU to use so I used Telus because I read somewhere that because it is not gsm but cmda I needed to use telus (the article said sprint but I assumed that I would use telus) But, as I am on rogers, would I than need to have s-off and then install the RUU
I am trying to get it back to stock. Not for warranty purposes.
Also I do not know about recovery because when I chose recovery in bootloader, nothing happens.
Also thanks for replying, I really appreciate it,
stovie_steve said:
Did you run the command fastboot oem writesecureflag 3 and lock the bootloader? You will have to unlock the bootloader again using htc's unlock token, install custom recovery and install a guru reset (can be found on here) for version 2.24.401.1 which is what your current software is according to your fastboot getvar all
In order to send your phone for repairs, your phone must read as LOCKED and tampered message removed from your bootloader. Your CID must also be reset to the original. To do this you need s off though
To get s off follow the guides for rumrunner or firewater
Do NOT update your firmware past 1.54, its harder to obtain s off. You CAN still get it using sunshine, it costs $25 tho but is awesome and works with stock ROMs
Finally, i wouldnt do the command fastboot oem writesecureflag 3 again on later hboots ie 1.55 or above. This can reset the tamper message on the bootloader
Good luck
Click to expand...
Click to collapse
Thank you for replying, I did run writesecureflag 3 as per the instructions I was following (really regret it now, should have came here first)
I do not need to send in the phone for repair, the post just sounded more legitimate, I just want to have stock because all i do with my phone is the basic functions, I never saw a need to fettle around with it .
So, I assume from reading both posts that I need to unlock my bootloader again? Do i need s-off if I want to do stock RUU? Do i also need s-off if I want to use rogers on a telus phone?
Also, would sunshine allow me to install the stock RUU? It seems to only unlock and s-off
Thank you all for replying, I really appreciate it.

stovie_steve said:
Did you run the command fastboot oem writesecureflag 3 and lock the bootloader? You will have to unlock the bootloader again using htc's unlock token, install custom recovery and install a guru reset (can be found on here) for version 2.24.401.1 which is what your current software is according to your fastboot getvar all
In order to send your phone for repairs, your phone must read as LOCKED and tampered message removed from your bootloader. Your CID must also be reset to the original. To do this you need s off though
To get s off follow the guides for rumrunner or firewater
Do NOT update your firmware past 1.54, its harder to obtain s off. You CAN still get it using sunshine, it costs $25 tho but is awesome and works with stock ROMs
Finally, i wouldnt do the command fastboot oem writesecureflag 3 again on later hboots ie 1.55 or above. This can reset the tamper message on the bootloader
Good luck
Click to expand...
Click to collapse
Hi,
So i followed your instructions, and low and behold, it worked. I used Guru_Reset_M7_2.24.401.1
But problem is I cannot update, when i press update, it says that it is already updated.
How would I fix it so I can update?
Thank youuu

commandaria said:
Hi,
So i followed your instructions, and low and behold, it worked. I used Guru_Reset_M7_2.24.401.1
But problem is I cannot update, when i press update, it says that it is already updated.
How would I fix it so I can update?
Thank youuu
Click to expand...
Click to collapse
Are you now s off with an unlocked bootloader and did you run the sunshine app? If you did, you can run almost any RUU

Need to get stock recovery back on modified GPE

I bought HTC one M7 unlocked from HTC.com when it came out. Last year I modified it to get rid of sense and made it "google play edition". I discovered I can't get OTA updates though due to the presence of stock recovery though.
Question: How can I get rid of TWRP and get back to stock recovery? fastboot getvar version-main returns empty

anil_robo said:
I bought HTC one M7 unlocked from HTC.com when it came out. Last year I modified it to get rid of sense and made it "google play edition". I discovered I can't get OTA updates though due to the presence of stock recovery though.
Question: How can I get rid of TWRP and get back to stock recovery? fastboot getvar version-main returns empty
Click to expand...
Click to collapse
Bump - still looking for answers

anil_robo said:
Bump - still looking for answers
Click to expand...
Click to collapse
everything you need is here >> http://forum.xda-developers.com/showthread.php?t=2358781
Do Not Relock your bootloader !! It will never unlock again

That tutorial still converts to GPE. I need one that converts GPE back to Sense.

anil_robo said:
That tutorial still converts to GPE. I need one that converts GPE back to Sense.
Click to expand...
Click to collapse
What is your android version? 5.1? 5.0?

@alray
Android version is 4.4.4.
The phone downloaded an update (to 5+ ) but I am unable to install it because I have TWRP but not the stock recovery.

anil_robo said:
@alray
Android version is 4.4.4.
The phone downloaded an update (to 5+ ) but I am unable to install it because I have TWRP but not the stock recovery.
Click to expand...
Click to collapse
If its 4.4.4 (Build KTU84P) you need the 4.09.1700.1 stock recovery to install the 5.0.1 update (LRX22C). You'll then receive another notification to install the 5.1 update (LMY47O)

alray said:
If its 4.4.4 (Build KTU84P) you need the 4.09.1700.1 stock recovery to install the update.
Click to expand...
Click to collapse
Thanks a lot!
Actually my "goals" have changed. Now I need to convert the phone into "totally stock" because I want to send it to HTC for free camera fix. If you don't mind, is there an instant messenger etc where I can contact you?

anil_robo said:
Thanks a lot!
Actually my "goals" have changed. Now I need to convert the phone into "totally stock" because I want to send it to HTC for free camera fix. If you don't mind, is there an instant messenger etc where I can contact you?
Click to expand...
Click to collapse
im not really using any IM app but i can help you here. Do you remember your original CID and MID ? Also post the output of "fastboot getvar all" (remove imei/serialno before posting)

alray said:
im not really using any IM app but i can help you here. Do you remember your original CID and MID ? Also post the output of "fastboot getvar all" (remove imei/serialno before posting)
Click to expand...
Click to collapse
My wife has the exact same phone (we bought together) but hers is not tampered at all. So I have the original settings in her phone:
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
I have wife's phone (original) with me right now, and need to convert my phone (tampered) into exact same as my wife's.
fastboot getvar all returns this in my (tampered) phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.27.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
Serial and IMEI deleted
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3860mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e02a9046
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

anil_robo said:
My wife has the exact same phone (we bought together) but hers is not tampered at all. So I have the original settings in her phone:
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
I have wife's phone (original) with me right now, and need to convert my phone (tampered) into exact same as my wife's.
fastboot getvar all returns this in my (tampered) phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.27.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
Serial and IMEI deleted
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3860mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e02a9046
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
So it was originally a developer edition phone right?
First download this ruu and save it in the same folder you have fastboot and adb on your computer. Rename the file "ruu" so it will be easier in the command prompt.
Download this tool and save it on the root of your phone storage
Boot in twrp recovery, select "install" and choose "Guru_Bootloader_Reset_1.0.zip" and then "swipe to install"
Follow instruction of the installer to remove tampered from the bootloader. Don't set the bootloader to locked or re-locked. Keep it unlocked as Developer edition phones are factory bootloader unlocked.
Then boot the phone in bootloader / fastboot usb mode
Confirm that tampered is gone and bootloader is still unlocked.
With the phone still in bootloader, open a command window from your adb/fastboot folder
Code:
fastboot oem rebootRUU
phone will reboot in ruu mode, a black screen with silver htc logo
Code:
fastboot flash zip ruu.zip
first flash will report "failed, flush image again immediately, so do the same command again:
Code:
fastboot flash zip ruu.zip
this one will report "flashed successfully"
Code:
fastboot reboot-bootloader
If you want to turn the bootloader back to S-ON for warranty do this command as the final step:
Code:
fastboot oem writesecureflag 3
fastboot reboot-bootloader
and confirm phone is S-ON, Unlocked, no tampered flag.
And a big warning here, do not perform this if you are using a windows 8/8.1 computer as the ruu will downgrade hboot to 1.44. hboot 1.44 is not compatible with windows 8.1 and you'll loose fastboot connectivity after the first "fastboot flash zip ruu.zip" and you'll be stuck in ruu mode. Use windows 7. XP, Linux (Ubuntu for example) or use MacOS

alray said:
So it was originally a developer edition phone right?
First download this ruu and save it in the same folder you have fastboot and adb on your computer. Rename the file "ruu" so it will be easier in the command prompt.
Download this tool and save it on the root of your phone storage
Boot in twrp recovery, select "install" and choose "Guru_Bootloader_Reset_1.0.zip" and then "swipe to install"
Follow instruction of the installer to remove tampered from the bootloader. Don't set the bootloader to locked or re-locked. Keep it unlocked as Developer edition phones are factory bootloader unlocked.
Then boot the phone in bootloader / fastboot usb mode
Confirm that tampered is gone and bootloader is still unlocked.
With the phone still in bootloader, open a command window from your adb/fastboot folder
Code:
fastboot oem rebootRUU
phone will reboot in ruu mode, a black screen with silver htc logo
Code:
fastboot flash zip ruu.zip
first flash will report "failed, flush image again immediately, so do the same command again:
Code:
fastboot flash zip ruu.zip
this one will report "flashed successfully"
Code:
fastboot reboot-bootloader
If you want to turn the bootloader back to S-ON for warranty do this command as the final step:
Code:
fastboot oem writesecureflag 3
fastboot reboot-bootloader
and confirm phone is S-ON, Unlocked, no tampered flag.
And a big warning here, do not perform this if you are using a windows 8/8.1 computer as the ruu will downgrade hboot to 1.44. hboot 1.44 is not compatible with windows 8.1 and you'll loose fastboot connectivity after the first "fastboot flash zip ruu.zip" and you'll be stuck in ruu mode. Use windows 7. XP, Linux (Ubuntu for example) or use MacOS
Click to expand...
Click to collapse
Yes it is a developer edition phone.
Question though: My android version is 4.4.4, and the RUU you linked is 5.0 - does it matter? Won't I run into a "boot loop"?

anil_robo said:
Yes it is a developer edition phone.
Question though: My android version is 4.4.4, and the RUU you linked is 5.0 - does it matter? Won't I run into a "boot loop"?
Click to expand...
Click to collapse
The ruu linked is not 5.0 its 4.1.2 Jelly Bean

anil_robo said:
Yes it is a developer edition phone.
Question though: My android version is 4.4.4, and the RUU you linked is 5.0 - does it matter? Won't I run into a "boot loop"?
Click to expand...
Click to collapse
Wow this was simple! I'm now running stock Jelly Bean, just like a new phone two years ago
I have still left S-OFF and Unlocked - will compare these settings to how my wife's phone is, and then either leave it unlocked or locked to match hers. And then will do S-ON.
Thank you kind sir!

anil_robo said:
Wow this was simple! I'm now running stock Jelly Bean, just like a new phone two years ago
I have still left S-OFF and Unlocked - will compare these settings to how my wife's phone is, and then either leave it unlocked or locked to match hers. And then will do S-ON.
Thank you kind sir!
Click to expand...
Click to collapse
Dev edition are unlocked from factory
Security is set to S-ON from factory
anyway its to late to set the bootloader to locked because the tool to set this requires a custom recovery.

alray said:
Dev edition are unlocked from factory
Security is set to S-ON from factory
anyway its to late to set the bootloader to locked because the tool to set this requires a custom recovery.
Click to expand...
Click to collapse
I'll try this tomorrow: https://aubykhan.wordpress.com/2013...t-into-twrp-or-cwm-recovery-without-flashing/

anil_robo said:
I'll try this tomorrow: https://aubykhan.wordpress.com/2013...t-into-twrp-or-cwm-recovery-without-flashing/
Click to expand...
Click to collapse
Thats right, I forgot about this. fasboot boot recovery.img will work fine since the phone is now on hboot 1.44, but anayway as I said, dev edition are bootloader unlock from the factory so setting it Locked will be suspicious
@anil_robo see the 4th dot: http://blog.htc.com/2013/03/htc-one-developer-edition/

alray said:
Thats right, I forgot about this. fasboot boot recovery.img will work fine since the phone is now on hboot 1.44, but anayway as I said, dev edition are bootloader unlock from the factory so setting it Locked will be suspicious
@anil_robo see the 4th dot: http://blog.htc.com/2013/03/htc-one-developer-edition/
Click to expand...
Click to collapse
Well I checked wife's phone, and it is "LOCKED" to my surprise. So I have to do the same to match those settings. I bought this phone within few days when it became available, and it may not have been the developer edition I initially thought. It must have been the "international" version rather than the "unlocked developer" version.

anil_robo said:
Well I checked wife's phone, and it is "LOCKED" to my surprise. So I have to do the same to match those settings. I bought this phone within few days when it became available, and it may not have been the developer edition I initially thought. It must have been the "international" version rather than the "unlocked developer" version.
Click to expand...
Click to collapse
The international version is MID PN0710000, version base is .401 e.g. 7.19.401.2 and BS_US001 is not a CID for international version...
There a method to know what your phone was originally. Your original CID/MID and firmware/software version are stored in the MFG partition of your phone. If you can dump this partition to your computer and send it to me, we can determine for sure what it was originally. Unfortnately this partition also include your IMEI and Serial number which should be kept private, if you are ok with sharing this with me here how to proceed:
Boot twrp recovery without flashing it to your phone:
reboot your phone in bootloader / fastboot usb mode
Code:
fastboot boot [URL="https://dl.twrp.me/m7/twrp-2.8.6.0-m7.img.html"]twrp-2.8.6.0-m7.img[/URL]
once booted in twrp main menu, type these commands in the command window:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6_bakup.img
exit
exit
Then reboot the phone normally, go to "My Computer --> HTC One --> Internal Storage. You'll find the mmcblk0p6_backup.img file. send it to me via PM only