Database Develop

[Q] No android, no recovery, only bootloader... :(

Dear XDA,
I wanted to update my HTC One to Revolution HD. But there where some requirements before i could install that. Like updating the firmware and installing TWRP recovery. I needed to RELOCK my phone in order to update my firmware. So i did that using a tutorial. After that i only had to push the RUU and i would be back @ stock. And then i could flash Revolution HD to get 4.4!
But!... it went horribly wrong. As of right now, i can only enter fastboot. I cannot enter recovery, and there is no Android installed, so basically i'm screwed.
I do have some flashing experience and I'm not a complete newb, but this is out of my league. Perhaps there are some nice persons here that could help me out. I will try to summarise my phone settings:
My current settings in Fastboot:
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
May 3 2013,17:22:59:-1
CID: HTC_E11
MID: PN0710000
I have a nandroidback, but i can't get into recovery. I tried using ADB but my device is not recognised.... I get the feeling that S-ON needs to change to S-OFF. But if i use a toolkit (from Squabbi) i can't get my device S-OFF (device not recognised..).
As of right now, I'm sitting with my hands in my hair thinking i bricked my phone.
If someone could help me, you would save my day.
Lennard Breevaart.
ps: I'm using windows xp

len.asdf said:
Dear XDA,
I wanted to update my HTC One to Revolution HD. But there where some requirements before i could install that. Like updating the firmware and installing TWRP recovery. I needed to RELOCK my phone in order to update my firmware. So i did that using a tutorial. After that i only had to push the RUU and i would be back @ stock. And then i could flash Revolution HD to get 4.4!
But!... it went horribly wrong. As of right now, i can only enter fastboot. I cannot enter recovery, and there is no Android installed, so basically i'm screwed.
I do have some flashing experience and I'm not a complete newb, but this is out of my league. Perhaps there are some nice persons here that could help me out. I will try to summarise my phone settings:
My current settings in Fastboot:
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
May 3 2013,17:22:59:-1
CID: HTC_E11
MID: PN0710000
I have a nandroidback, but i can't get into recovery. I tried using ADB but my device is not recognised.... I get the feeling that S-ON needs to change to S-OFF. But if i use a toolkit (from Squabbi) i can't get my device S-OFF (device not recognised..).
As of right now, I'm sitting with my hands in my hair thinking i bricked my phone.
If someone could help me, you would save my day.
Lennard Breevaart.
ps: I'm using windows xp
Click to expand...
Click to collapse
is your bootloader unlocked ? do that first
what version of TWRP do you have (exact name)
do you have fastboot/adb on your pc and do you know how to use them ?

is your bootloader unlocked ? do that first
==> I think so, how can i check?
what version of TWRP do you have (exact name)
==> I have no recovery installed on my phone. But i have TWRP version 2.6.3.3. img on my computer, ready to push it to my phone (but it gives the error: device not found)
do you have fastboot/adb on your pc and do you know how to use them ?
==> I think i do. When i try to do adb shell in command window it replies with either device not found, or adb server out of date. Killing...
Thanks for replying btw!

len.asdf said:
is your bootloader unlocked ? do that first
==> I think so, how can i check?
what version of TWRP do you have (exact name)
==> I have no recovery installed on my phone. But i have TWRP version 2.6.3.3. img on my computer, ready to push it to my phone (but it gives the error: device not found)
do you have fastboot/adb on your pc and do you know how to use them ?
==> I think i do. When i try to do adb shell in command window it replies with either device not found, or adb server out of date. Killing...
Thanks for replying btw!
Click to expand...
Click to collapse
take these files
extract fastboot.zip to c:\fastboot
and install these drivers
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
MD5: e2a21d71954d4164c1a116abb926a363
and see if you can get:
fastboot getvar all
and post the results minus you serial no and IEMI

clsA said:
take these files
extract fastboot.zip to c:\fastboot
and install these drivers
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
MD5: e2a21d71954d4164c1a116abb926a363
and see if you can get:
fastboot getvar all
and post the results minus you serial no and IEMI
Click to expand...
Click to collapse
Thanks! This is what i did to get my results:
1. Downloaded both the fastboot.zip and the drivers (and installed ofcourse).
2. Opened a command window on c:\fastboot
3. typed: fastboot getvar all
Results:
C:\fastboot>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: -
(bootloader) imei: -
(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: 4222mV
(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.047s
C:\fastboot>

len.asdf said:
Thanks! This is what i did to get my results:
1. Downloaded both the fastboot.zip and the drivers (and installed ofcourse).
2. Opened a command window on c:\fastboot
3. typed: fastboot getvar all
Results:
C:\fastboot>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: -
(bootloader) imei: -
(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: 4222mV
(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.047s
C:\fastboot>
Click to expand...
Click to collapse
Your phone is basically still stock andriod version 4.1.2
(this is good you can s-off pretty easy)
what RUU were you going to flash ?
this is the version of recovery you need
http://techerrata.com/browse/twrp2/m7ul
download it and put it in your fastboot folder
then to flash it:
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
now you can enter recovery correct ?

clsA said:
Your phone is basically still stock andriod version 4.1.2
(this is good you can s-off pretty easy)
what RUU were you going to flash ?
Click to expand...
Click to collapse
The RUU i tried was this one: RUU M7 U JB 50 HTC Europe 1.29.401.2 R Radio 4A.14.3250.13 10.33.1150.01 Release 311663 Signed 2 4
(from: http://forum.xda-developers.com/showthread.php?t=2428276)
While installing the RUU it gave me an an error that my CID and MID didn't match.

clsA said:
Your phone is basically still stock andriod version 4.1.2
(this is good you can s-off pretty easy)
what RUU were you going to flash ?
this is the version of recovery you need
http://techerrata.com/browse/twrp2/m7ul
download it and put it in your fastboot folder
Click to expand...
Click to collapse
Downloaded the recovery and put in the the fastboot folder

clsA said:
Your phone is basically still stock andriod version 4.1.2
(this is good you can s-off pretty easy)
what RUU were you going to flash ?
this is the version of recovery you need
http://techerrata.com/browse/twrp2/m7ul
download it and put it in your fastboot folder
then to flash it:
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
now you can enter recovery correct ?
Click to expand...
Click to collapse
While in ADB it gave this error:
C:\fastboot>fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
sending 'recovery' (9840 KB)...
OKAY [ 1.297s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.891s
C:\fastboot>
edit: I cannot enter recovery yet. Just tried it

len.asdf said:
While in ADB it gave this error:
C:\fastboot>fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
sending 'recovery' (9840 KB)...
OKAY [ 1.297s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.891s
C:\fastboot>
edit: I cannot enter recovery yet. Just tried it
Click to expand...
Click to collapse
your bootloader is still locked

clsA said:
your bootloader is still locked
Click to expand...
Click to collapse
I checked the md5 (f428caf36c9c337e2ae417fc10fbe165) with the file i downloaded. And it matches

len.asdf said:
I checked the md5 (f428caf36c9c337e2ae417fc10fbe165) with the file i downloaded. And it matches
Click to expand...
Click to collapse
yeah i realize that your bootloader is still locked
you need to go to htcdev and unlock again
then flash recovery

clsA said:
yeah i realize that your bootloader is still locked
you need to go to htcdev and unlock again
Click to expand...
Click to collapse
Ah ok, I will be doing that then . I will update this topic when i'm done.

len.asdf said:
Ah ok, I will be doing that then . I will update this topic when i'm done.
Click to expand...
Click to collapse
be warned unlocking will wipe the phone you'll be starting from nothing

clsA said:
be warned unlocking will wipe the phone you'll be starting from nothing
Click to expand...
Click to collapse
I know! But don't worry, it's the least of my problems now

Unlocked my phone, and gonna flash the recovery aswell!
But to not make the same mistake twice. What is the best way to update my phone to 4.4?
I wanted to install Revolution HD. But maybe you have a better alternative?

And how can i properly thank you? I mean, you just saved my ass!

len.asdf said:
And how can i properly thank you? I mean, you just saved my ass!
Click to expand...
Click to collapse
it's no problem
you should try and get s-off next
http://forum.xda-developers.com/showthread.php?t=2314582 - revone
ARHD is great .. I also use ViperOne
just use the sideload feature in twrp being your phone is wiped
Quote:
Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
From the command line, type adb sideload name_of_rom.zip
or
adb push Rom.zip /data/media/0/
Click to expand...
Click to collapse

clsA said:
it's no problem
you should try and get s-off next
http://forum.xda-developers.com/showthread.php?t=2314582 - revone
ARHD is great .. I also use ViperOne
just use the sideload feature in twrp being your phone is wiped
Click to expand...
Click to collapse
I will get s-off through the HTC One All in one toolkit. But on the ARHD topic, this was posted aswell:
You need:
HTC One unlocked with htcdev.com (S-ON) or S-OFF
Custom recovery
Firmware package from here (recommended but not needed for now)
Read this flashing guide - [GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock
So i tried to get the latest firmware, and that's where the problems started. But shouldn't it be better to have the latest firmware? I mean it stands there for a reason, right? Or am I wrong?
Anyway, i will try ARHD for now, it looks nice
Thanks again!

len.asdf said:
I will get s-off through the HTC One All in one toolkit. But on the ARHD topic, this was posted aswell:
You need:
HTC One unlocked with htcdev.com (S-ON) or S-OFF
Custom recovery
Firmware package from here (recommended but not needed for now)
Read this flashing guide - [GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock
So i tried to get the latest firmware, and that's where the problems started. But shouldn't it be better to have the latest firmware? I mean it stands there for a reason, right? Or am I wrong?
Anyway, i will try ARHD for now, it looks nice
Thanks again!
Click to expand...
Click to collapse
firmware comes after s-off
and ARHD 31.6 is your best bet for now till your s-off

Stuck in bootloader/recovery

Hi, i've bought an htc one m7 stuck in bootloader, trying to fix it.. this is what I see in bootloader
** TAMPERED **
** UNLOCK **
** Security Warning **
M7_U PVT SHIP S-ON RH
HBOOT-1.57.000
RADIO-4T.28.3218.04
OpenDSP-V32.120.274.0909
eMMC-boot 2048MB
i've tried to unlock bootloader, succesfully and after the reboot it access directly in twrp 2710 recovery (maybe the previous owner flashed it)..
so, i go in advanced, then in adb sideload to transfert a custom rom (eg. revolution) but my phone switch off the screen and my pc try to install qhsusb_dload driver, without success.. so, I press the power button for 20sec (circa) and switch off completly.. and back again in bootloader, that relock automatically every reboot...
how can i fix it? :crying:
Thanks!

Angel2k6 said:
Hi, i've bought an htc one m7 stuck in bootloader, trying to fix it.. this is what I see in bootloader
** TAMPERED **
** UNLOCK **
** Security Warning **
M7_U PVT SHIP S-ON RH
HBOOT-1.57.000
RADIO-4T.28.3218.04
OpenDSP-V32.120.274.0909
OS- (THIS ROW IS BLANK AFTER "OS-"!)
eMMC-boot 2048MB
i've tried to unlock bootloader, succesfully and after the reboot it access directly in twrp 2710 recovery (maybe the previous owner flashed it)..
so, i go in advanced, then in adb sideload to transfert a custom rom (eg. revolution) but my phone switch off the screen and my pc try to install qhsusb_dload driver, without success.. so, I press the power button for 20sec (circa) and switch off completly.. and back again in bootloader, that relock automatically every reboot...
how can i fix it? :crying:
Thanks!
Click to expand...
Click to collapse
Unlock bootloader
flash TWRP 2.6.3.3
Enter TWRP / Wipe / Format Data / Type yes
Reboot to Recovery and push the rom to the phone
adb push rom.zip /sdcard/
Install / rom.zip

clsA said:
Unlock bootloader
flash TWRP 2.6.3.3
Enter TWRP / Wipe / Format Data / Type yes
Reboot to Recovery and push the rom to the phone
adb push rom.zip /sdcard/
Install / rom.zip
Click to expand...
Click to collapse
the problem is that a cannot flash twrp .. how can i do it?
When i unlock the bootloader through the unlock_code.bin (taken from htcdev) the phone reboots automatically in recovery twrp 2.7.1.1 .. and if i reboot the phone again in bootloader it's again in RELOCKED mode..

Angel2k6 said:
the problem is that a cannot flash twrp .. how can i do it?
When i unlock the bootloader through the unlock_code.bin (taken from htcdev) the phone reboots automatically in recovery twrp 2.7.1.1 .. and if i reboot the phone again in bootloader it's again in RELOCKED mode..
Click to expand...
Click to collapse
when it boots to TWRP just follow the rest of the steps

clsA said:
when it boots to TWRP just follow the rest of the steps
Click to expand...
Click to collapse
If i do a wipe from twrp it says "unable to mount /cache" and "unable to mount /system".. Anyway.. After this wipes have I to reboot again in the same recovery? And then? When have I to type adb commands?

Angel2k6 said:
If i do a wipe from twrp it says "unable to mount /cache" and "unable to mount /system".. Anyway.. After this wipes have I to reboot again in the same recovery? And then? When have I to type adb commands?
Click to expand...
Click to collapse
tried it .. but "unable to mount /system /data /cache" .. and when i do reboot>recovery .. the phone doesn't reboot.. it switch down and i have to press for 10-15 seconds to switch completly off.. and than again in relocked bootloader..

Angel2k6 said:
tried it .. but "unable to mount /system /data /cache" .. and when i do reboot>recovery .. the phone doesn't reboot.. it switch down and i have to press for 10-15 seconds to switch completly off.. and than again in relocked bootloader..
Click to expand...
Click to collapse
post your fastboot getvar all
maybe you can flash stock recovery and factory reset

Í
clsA said:
post your fastboot getvar all
maybe you can flash stock recovery and factory reset
Click to expand...
Click to collapse
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***********
(bootloader) imei: ****************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: TIM__401
(bootloader) battery-status: good
(bootloader) battery-voltage: 4311mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.201s
Thank you!
Ah.. Another thing that I have noticed is that in twrp the driver isn't installed by windows.. In "device management" I see a "one" device with a yellow exclamation (I've installed htc sync) .. Windows can't find any compatible driver in my PC.. if i look into hardware details, this is the id:
USB\VID_18D1&PID_D001&REV_0228
EDIT: about the driver i've installed it modifying android_winusb.inf adding this lines:
;HTC ONE(MOD)
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0228
Click to expand...
Click to collapse
in x64 section .. i don't know if i done it well but now when i'm in twrp windows recognize phone, seen as "Android Phone - Android Composite ADB inteface" without the exclamation mark and if I do "adb devices" in prompt it sees my device (seen as it's serial number) and near it "recovery"..
P.S. Why every time the phone is rebooted it relock the bootloader automatically and I have to unlock again to access the recovery?

Angel2k6 said:
Í
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***********
(bootloader) imei: ****************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: TIM__401
(bootloader) battery-status: good
(bootloader) battery-voltage: 4311mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.201s
Thank you!
Ah.. Another thing that I have noticed is that in twrp the driver isn't installed by windows.. In "device management" I see a "one" device with a yellow exclamation (I've installed htc sync) .. Windows can't find any compatible driver in my PC.. if i look into hardware details, this is the id:
USB\VID_18D1&PID_D001&REV_0228
EDIT: about the driver i've installed it modifying android_winusb.inf adding this lines:
in x64 section .. i don't know if i done it well but now when i'm in twrp windows recognize phone, seen as "Android Phone - Android Composite ADB inteface" without the exclamation mark and if I do "adb devices" in prompt it sees my device (seen as it's serial number) and near it "recovery"..
P.S. Why every time the phone is rebooted it relock the bootloader automatically and I have to unlock again to access the recovery?
Click to expand...
Click to collapse
Do you remember your Version Main only its not present in the getvar?

Danny201281 said:
Do you remember your Version Main only its not present in the getvar?
Click to expand...
Click to collapse
Nope.. I've bought this phone as it is.. :/

Angel2k6 said:
Nope.. I've bought this phone as it is.. :/
Click to expand...
Click to collapse
Well I'm thinking flashing a firmware package may help, But i just can't find anything. What is country of Origin, Italy?

Danny201281 said:
Well I'm thinking flashing a firmware package may help, But i just can't find anything. What is country of Origin, Italy?
Click to expand...
Click to collapse
Yes, Italy.. But reading around, in Italian forums it seems that there isn't any ruu for cid tim__401 ..
EDIT :
I don't know if this one could help but here http://www.androidiani.com/forum/modding-htc-one/405113-ritorno-stock-tim.html
there is a TIM backup (he says already rooted) android version 4.4.2..

up
if i try to do this from recovery (using a cm11 rom)
adb devices
List of devices attached
************ recovery
adb push rom1.zip /sdcard/
protocol failure
Click to expand...
Click to collapse
screen switch off and windows tries to install qhsusb_dload drivers..
any ideas? :crying:
Could i try with an otg cable?

Angel2k6 said:
up
if i try to do this from recovery (using a cm11 rom)
screen switch off and windows tries to install qhsusb_dload drivers..
any ideas? :crying:
Could i try with an otg cable?
Click to expand...
Click to collapse
You need to flash a firmware package, or at very least a stock recovery. I have searched all over the net but I can't find any thing not even an OTA.zip
I think your version main would be 5.12.901.3 since that appears to be the latest version with hboot 1.57. But there simply aren't any files for that.
Best suggestion I have for now is, as your able to unlock. Unlock the bootloader
Code:
fastboot flash unlocktoken Unlock_code.bin
fastboot erase cache
fastboot reboot-bootloader
and flash an unbranded stock recovery this one maybe https://www.androidfilehost.com/?fid=95864024717070745
Then use that to do a factory reset. Reboot and see if its locked. If it is unlock again with
Code:
fastboot flash unlocktoken Unlock_code.bin
fastboot erase cache
fastboot reboot-bootloader
Check to see if problem is resolved.

Danny201281 said:
You need to flash a firmware package, or at very least a stock recovery. I have searched all over the net but I can't find any thing not even an OTA.zip
I think your version main would be 5.12.901.3 since that appears to be the latest version with hboot 1.57. But there simply aren't any files for that.
Best suggestion I have for now is, as your able to unlock. Unlock the bootloader
Code:
fastboot flash unlocktoken Unlock_code.bin
fastboot erase cache
fastboot reboot-bootloader
and flash an unbranded stock recovery this one maybe https://www.androidfilehost.com/?fid=95864024717070745
Then use that to do a factory reset. Reboot and see if its locked. If it is unlock again with
Code:
fastboot flash unlocktoken Unlock_code.bin
fastboot erase cache
fastboot reboot-bootloader
Check to see if problem is resolved.
Click to expand...
Click to collapse
I'll try later..
But, every time that I unlock bootloader the phone automatically goes in recovery, so I can't type the second command "fastboot erase cache", because if I reboot again in bootloader is again relocked.. :/

Angel2k6 said:
I'll try later..
But, every time that I unlock bootloader the phone automatically goes in recovery, so I can't type the second command "fastboot erase cache", because if I reboot again in bootloader is again relocked.. :/
Click to expand...
Click to collapse
Ok I see, only option is to flash firmware then since that can be done while it's relocked. First we need to find it

Danny201281 said:
Ok I see, only option is to flash firmware then since that can be done while it's relocked. First we need to find it
Click to expand...
Click to collapse
And then it's the only way? If i try using an otg cable flashing a cm11? Could I do more damage?

Angel2k6 said:
And then it's the only way? If i try using an otg cable flashing a cm11? Could I do more damage?
Click to expand...
Click to collapse
But how can you boot a custom rom with a relocked bootloader? Are you able to unlock flash a rom then boot to Android? Or does it relock when you reboot after flashing the rom?

Danny201281 said:
But how can you boot a custom rom with a relocked bootloader? Are you able to unlock flash a rom then boot to Android? Or does it relock when you reboot after flashing the rom?
Click to expand...
Click to collapse
But when I unlock bootloader and the phone reboots directly in recovery, in that session, while I'm in recovery, they bootloader isn't unlocked?
I've never tried to flash a rom because adb sideload or adb push seems that don't work..

Angel2k6 said:
But when I unlock bootloader and the phone reboots directly in recovery, in that session, while I'm in recovery, they bootloader isn't unlocked?
I've never tried to flash a rom because adb sideload or adb push seems that don't work..
Click to expand...
Click to collapse
It must be unlocked otherwise the custom recovery wouldn't load. So you could push and install a rom, but after its installed the rom you will need to reboot. If the bootloader locks it won't boot the custom rom.
You could also try to dd (direct dump) a stock recovery while your in custom recovery. Maybe that would help?

[Q] RUU htc m7 o2 lollipop needed not .zip file

Help needed to bring my htc m 7 uk on o2 back to stock tried every thing bar the kitchen sink using adb fastboot etc
device is showing tampered relocked tried unlocking using token from htc dev but gets stuck on white screen entering recovery,
have managed to find ruu,zip file but when i try to flash it shows cannot load ruu.zip not enough space .
BOOTLOADER 1.57.0000
BASEBAND 4T.28.3218.04
CPLD NONE
MAIN 6.14.206.2
PUT SHIP S ON
HBOOT -8064
MODELID PN0710000
CID 02 001
I CANNOT SEEM TO FIND A STOCK RUU FILE TO FLASH . WHY IS IT HTC DEV USA HAVE RUU`S TO DOWNLOAD BUT NOT HTC DEV UK
ANY POSITIVE HELP WOULD BE APPRECIATED

robbo2 said:
tried unlocking using token from htc dev but gets stuck on white screen entering recovery
Click to expand...
Click to collapse
This is a well known issue caused by a re-locked bootloader + custom firmware/recovery still installed on the phone. Always reflash stock recovery before re-locking the bootloader. To solve this issue you must reflash the 6.14.206.2 firmware.
Code:
fastboot oem rebootRUU
fastboot flash zip 6.14.206.2.zip
fastboot flash zip 6.14.206.2.zip
fastboot reboot-bootloader
then get a new unlock token:
Code:
fastboot oem get_identifier_token
Submit token to htcdev.com and wait for your Unlock_code.bin in your e-mail. Once reveiced copy your Unlock_code.bin in the same folder where adb and fastboot are.
Code:
fastboot flash unlocktoken Unlock_code.bin
^^case sensitive, so don'T forget the capital U
have managed to find ruu,zip file but when i try to flash it shows cannot load ruu.zip not enough space .
Click to expand...
Click to collapse
Which version exactly? How are you trying to flash it? Can not really help regarding this as you are not giving much information. A screenshot of your command prompt while trying to flash this file would help.
I CANNOT SEEM TO FIND A STOCK RUU FILE TO FLASH
Click to expand...
Click to collapse
So the ruu you were trying to flash above isn't a stock RUU? With s-on, you can only flash 100% stock (signed) ruu same or higher version (6.14.206.2 or above).
After unlocking the bootloader with instructions above, you can flash twrp recovery, restore this 6.14.206.2 nandroid backup, re-flash the 6.14.206.2 stock recovery. Your phone will then be stock rom and firmware and ready to take ota update. Bootloader will still show tampered and unlocked.
or
you can stay re-locked and flash the 7.18.206.2 ruu.zip. Use htc_fastboot.exe to flash:
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
fastboot reboot
and again your phone will be 100% stock firmware and software except the re-locked and tampered flags in the bootloader.
WHY IS IT HTC DEV USA HAVE RUU`S TO DOWNLOAD BUT NOT HTC DEV UK
Click to expand...
Click to collapse
RUUs are not officially available for customers, they don't have to release a RUU for every versions and they never did so.

robbo2 said:
Help needed to bring my htc m 7 uk on o2 back to stock tried every thing bar the kitchen sink using adb fastboot etc
device is showing tampered relocked tried unlocking using token from htc dev but gets stuck on white screen entering recovery,
have managed to find ruu,zip file but when i try to flash it shows cannot load ruu.zip not enough space .
BOOTLOADER 1.57.0000
BASEBAND 4T.28.3218.04
CPLD NONE
MAIN 6.14.206.2
PUT SHIP S ON
HBOOT -8064
MODELID PN0710000
CID 02 001
I CANNOT SEEM TO FIND A STOCK RUU FILE TO FLASH . WHY IS IT HTC DEV USA HAVE RUU`S TO DOWNLOAD BUT NOT HTC DEV UK
ANY POSITIVE HELP WOULD BE APPRECIATED
Click to expand...
Click to collapse
There is no RUU for O2 lollipop the latest is 4.4.2 kitkat. If you just want to return to stock for the OTA you can use my stock nandroid here https://www.androidfilehost.com/?fid=95864024717074289
To get around the bootloader unlock problem you need to flash the firmware
https://www.androidfilehost.com/?fid=95864024717074526
Download and put the zip in your fastboot folder and boot your device to the boot loader and flash the firmware
CODE]fastboot erase cache
fastboot oem rebootRUU[/CODE] **--- Case sensative ---^^^
Your device should boot to a black screen with a Silver HTC logo. This is RUU mode. We can now flash the firmware. In the command window type
Code:
fastboot flash zip firmware.zip
The first flash will be short, and will appear to fail. Thats normal its just a pre update preparing the hboot for the firmware. The phone screen will go black then return to RUU mode. So now we need to do the same command again.
Code:
fastboot flash zip firmware.zip
The second flash will take a little longer and will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal. As long as the command window has finished its output its done. Reboot to the bootloader.
Code:
fastboot reboot-bootloader
When that's done get a new unlock code.bin from htcdev to unlock your bootloader. Flash TWRP and use it to restore the stock backup. Then flash the stock recovery to get the OTA :good:

Danny201281 said:
There is no RUU for O2 lollipop the latest is 4.4.2 kitkat.
Click to expand...
Click to collapse
Looks like there is a ruu for O2 lollipop, see my post above.

Thanks sorted
When i was trying to flash the code from htc devs i have been using lower case as soon as i used upper case for the u in unlock everything fell into place thanks again for your help.
alray said:
This is a well known issue caused by a re-locked bootloader + custom firmware/recovery still installed on the phone. Always reflash stock recovery before re-locking the bootloader. To solve this issue you must reflash the 6.14.206.2 firmware.
Code:
fastboot oem rebootRUU
fastboot flash zip 6.14.206.2.zip
fastboot flash zip 6.14.206.2.zip
fastboot reboot-bootloader
then get a new unlock token:
Code:
fastboot oem get_identifier_token
Submit token to htcdev.com and wait for your Unlock_code.bin in your e-mail. Once reveiced copy your Unlock_code.bin in the same folder where adb and fastboot are.
Code:
fastboot flash unlocktoken Unlock_code.bin
^^case sensitive, so don'T forget the capital U
Which version exactly? How are you trying to flash it? Can not really help regarding this as you are not giving much information. A screenshot of your command prompt while trying to flash this file would help.
So the ruu you were trying to flash above isn't a stock RUU? With s-on, you can only flash 100% stock (signed) ruu same or higher version (6.14.206.2 or above).
After unlocking the bootloader with instructions above, you can flash twrp recovery, restore this 6.14.206.2 nandroid backup, re-flash the 6.14.206.2 stock recovery. Your phone will then be stock rom and firmware and ready to take ota update. Bootloader will still show tampered and unlocked.
or
you can stay re-locked and flash the 7.18.206.2 ruu.zip. Use htc_fastboot.exe to flash:
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
fastboot reboot
and again your phone will be 100% stock firmware and software except the re-locked and tampered flags in the bootloader.
RUUs are not officially available for customers, they don't have to release a RUU for every versions and they never did so.
Click to expand...
Click to collapse

Thanks
@alray you sir have just saved my bacon... Been looking for a Nandroid for the partners phone as the one i did got corrupted. decided to search again and this thread come up Thanks a million :good:

Hi everybody, maybe you can help me...
I'm stuck with the HTC M7 which should be from O2 UK (CID 02__001). I can't flash the official Lollipop, these are the steps I followed:
- cehcked for s-on or s-off...it is S-ON
- put phone in fastboot and sent command fastboot oem lock...it was already locked
- sent command fastboot erase cache
- sent command fastboot oem rebootRUU
- flashed file 6.14.206.zip (43mb more or less)
- sent command fastboot reboot-bootloader
Phone didn't boot, so I took the zip file named PN07IMG_M7_UL_L50_SENSE60_MR_O2_UK_7.18.206.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_423416_combined_signed.zip from above post and repeated the procedure above and in the end I got this:
sending 'zip'... (368766 KB) OKAY
sending time = 16.964 secs
writing 'zip'... (bootloader) adopting the signature containted in this image
(bootloader) signature checking...
FAIL12 signature verify fail
FAILED (remote: 12 signature verify fail)
I read twice your instructions but I don't find any mistakes in my steps...could you please help me? :highfive:
Thanks in advance!!!

slimhunter said:
Hi everybody, maybe you can help me...
Click to expand...
Click to collapse
What was the problem initially? Also post the output of "fastboot getvar all".

alray said:
What was the problem initially?
Click to expand...
Click to collapse
Hi alray, thanks for your quick reply.
Phone was not booting, it looped between the HTC green logo and the red triangle (i don't know the cause, my uncle wasn't clear when explaining what he did for causing the mess), so I decided to get rid of all of these problems by starting from a fresh install with the latest release...and still i can't get it to work

slimhunter said:
Hi alray, thanks for your quick reply.
Phone was not booting, it looped between the HTC green logo and the red triangle (i don't know the cause, my uncle wasn't clear when explaining what he did for causing the mess), so I decided to get rid of all of these problems by starting from a fresh install with the latest release...and still i can't get it to work
Click to expand...
Click to collapse
But the file you have flashed (43MB) is only the firmware not the software. Flashing the firmware can solve some issues but generally a non-booting device will need to flash a full RUU or at least a custom recovery + a rom.
Still waiting for the "fastboot getvar all" to guide you. (post above edited probably at the same time you were answering)

alray said:
But the file you have flashed (43MB) is only the firmware not the software. Flashing the firmware can solve some issues but generally a non-booting device will need to flash a full RUU or at least a custom recovery + a rom.
Click to expand...
Click to collapse
That's why I got the other, bigger file which is flashed all the way through but fails the last signature check
Here's the result of the command (made after the failed flash of PN07IMG_M7_UL_L50_SENSE60_MR_O2_UK_7.18.206.2_Radi o_4T.35.3218.16_10.33Q.1718.01L_release_423416_com bined_signed.zip
C:\ADB>fastboot getvar all
< waiting for device >
(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.18.206.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36EW906996
(bootloader) imei: 357864050372414
(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: 4273mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-4deaef41
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

slimhunter said:
That's why I got the other, bigger file which is flashed all the way through but fails the last signature check
Here's the result of the command (made after the failed flash of PN07IMG_M7_UL_L50_SENSE60_MR_O2_UK_7.18.206.2_Radi o_4T.35.3218.16_10.33Q.1718.01L_release_423416_com bined_signed.zip
C:\ADB>fastboot getvar all
< waiting for device >
(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.18.206.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36EW906996
(bootloader) imei: 357864050372414
(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: 4273mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-4deaef41
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
are you using htc's version of fastboot or the version from the android sdk?

The htc fastboot, renamed as "fastboot" (i kept the other .exe renaming it "old_fastboot").

slimhunter said:
The htc fastboot, renamed as "fastboot" (i kept the other .exe renaming it "old_fastboot").
Click to expand...
Click to collapse
try this run a RUU exe
when it asks connect phone
go to temp folder replace rom.zip to your zip file renaming it Rom.zip
proceed

I don't have a valid ruu exe. since the problem could be related to s-on (because of signature verification(, can you please help me in putting this phone in S-OFF? it's urgent, please :crying:
EDIT> i also tried your method, still error on signature check

slimhunter said:
I don't have a valid ruu exe. since the problem could be related to s-on (because of signature verification(, can you please help me in putting this phone in S-OFF? it's urgent, please :crying:
EDIT> i also tried your method, still error on signature check
Click to expand...
Click to collapse
S on + locked bootloader
S Off is difficult + cost $25 sunshine

So is there anything else i can do before spending money on that? thx for your support so far!

HTC_Android_Phone_RUU_2.0.16.2014.zip
slimhunter said:
That's why I got the other, bigger file which is flashed all the way through but fails the last signature check
Here's the result of the command (made after the failed flash of PN07IMG_M7_UL_L50_SENSE60_MR_O2_UK_7.18.206.2_Radi o_4T.35.3218.16_10.33Q.1718.01L_release_423416_com bined_signed.zip
Click to expand...
Click to collapse
I have this file to and it hasn't a typical signature. It's modificated, I think...
slimhunter said:
I don't have a valid ruu exe.
Click to expand...
Click to collapse
Here you can download a complete HTC M7 RUU exe folder:
HTC_Android_Phone_RUU_2.0.16.2014.zip

HTC One M7 Hboot 1.61 S-ON, how to make S-OFF on HTC One M7
slimhunter said:
Hi everybody, maybe you can help me...
I'm stuck with the HTC M7 which should be from O2 UK (CID 02__001). I can't flash the official Lollipop, these are the steps I followed:
- cehcked for s-on or s-off...it is S-ON
- put phone in fastboot and sent command fastboot oem lock...it was already locked
- sent command fastboot erase cache
- sent command fastboot oem rebootRUU
- flashed file 6.14.206.zip (43mb more or less)
- sent command fastboot reboot-bootloader
Phone didn't boot, so I took the zip file named PN07IMG_M7_UL_L50_SENSE60_MR_O2_UK_7.18.206.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_423416_combined_signed.zip from above post and repeated the procedure above and in the end I got this:
sending 'zip'... (368766 KB) OKAY
sending time = 16.964 secs
writing 'zip'... (bootloader) adopting the signature containted in this image
(bootloader) signature checking...
FAIL12 signature verify fail
FAILED (remote: 12 signature verify fail)
I read twice your instructions but I don't find any mistakes in my steps...could you please help me? :highfive:
Thanks in advance!!!
Click to expand...
Click to collapse
relock your bootloader and flash the 7.18.206.21 RUU
http://forum.xda-developers.com/htc-...ction-t3053944

[Q] HTC One M7 - GPE - NO Command

Hi Everyone
This is somewhat urgent and random. I literally woke up today and my phone has had the "No Command" Dialogue.. I do not know how it came about, the phone was working fine the night before, so I am not sure if the phone tried to update. The phone keeps on restarting back to the No Command dialogue. Your Help will be greatly appreciated!
I have an HTC One M7 GPE. It says LOCKED and S-On

LATOKYO said:
Hi Everyone
This is somewhat urgent and random. I literally woke up today and my phone has had the "No Command" Dialogue.. I do not know how it came about, the phone was working fine the night before, so I am not sure if the phone tried to update. The phone keeps on restarting back to the No Command dialogue. Your Help will be greatly appreciated!
I have an HTC One M7 GPE. It says LOCKED and S-On
Click to expand...
Click to collapse
So your phone is rebooting to the stock recovery.
First, try to erase cache
Code:
fastboot erase cache
fastboot reboot
If that doesn't work, try a factory reset
And finally you might be able to restore the phone using a RUU, you'll have to post the output of "fastboot getvar all" so we can direct you to the correct one.

Thank you so much for your response.
Questions:
How and where do I type those commands, and how do I use the "getvar"
alray said:
So your phone is rebooting to the stock recovery.
First, try to erase cache
Code:
fastboot erase cache
fastboot reboot
If that doesn't work, try a factory reset
And finally you might be able to restore the phone using a RUU, you'll have to post the output of "fastboot getvar all" so we can direct you to the correct one.
Click to expand...
Click to collapse

LATOKYO said:
Thank you so much for your response.
Questions:
How and where do I type those commands, and how do I use the "getvar"
Click to expand...
Click to collapse
already explained how yesterday to someone else in this thread http://forum.xda-developers.com/htc-one/help/htc-one-tampered-unlocked-t3150682

alray said:
already explained how yesterday to someone else in this thread http://forum.xda-developers.com/htc-one/help/htc-one-tampered-unlocked-t3150682
Click to expand...
Click to collapse
OK. I have both the Driver and SDK Installed.

LATOKYO said:
OK. I have both the Driver and SDK Installed.
Click to expand...
Click to collapse
ok so first try
Code:
fastboot erase cache
fastboot reboot

alray said:
ok so first try
Code:
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
OK.
I have some questions about what I installed, and If i installed the correct programs. I installed the SDK and the Drivers. Do I need to to install the packages with in the SDK? Do I also need to install the minimal ADB fastboot? Also, how do I access the command window, is it just the basic command prompt. I am a noob. I apologize.

alray said:
ok so first try
Code:
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
I am typing the command in the ADB fastboot command prompt window. I am also typing the command at the "No Command" dialogue. Is that where/when I should be typing the commands? Or at the boot loader?
I typed in the first command, and it say's it's waiting for device.
How do I know if it's reading via USB.

alray said:
ok so first try
Code:
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
OK. So i typed the commands. It responded. It Rebooted. But now it reboots back to the error triangle, but this time it doesn't say anything. Just the Android on its back.

LATOKYO said:
I am typing the command in the ADB fastboot command prompt window. I am also typing the command at the "No Command" dialogue. Is that where/when I should be typing the commands? Or at the boot loader?
I typed in the first command, and it say's it's waiting for device.
Click to expand...
Click to collapse
The phone must be booted in bootloader / fastboot usb mode like explained in the link posted above.
How do I know if it's reading via USB.
Click to expand...
Click to collapse
using the command
Code:
fastboot devices
will output the device serial number if the computer detects it.

alray said:
The phone must be booted in bootloader / fastboot usb mode like explained in the link posted above.
using the command
Code:
fastboot devices
will output the device serial number if the computer detects it.
Click to expand...
Click to collapse
OK. So i typed the commands. It responded. It Rebooted. But now it reboots back to the error triangle, but this time it doesn't say anything. Just the Android on its back. I also have the GetVAR if you want that? I shouldn't post the IMEI and Serial Number, right?

LATOKYO said:
OK. So i typed the commands. It responded. It Rebooted. But now it reboots back to the error triangle, but this time it doesn't say anything. Just the Android on its back. I also have the GetVAR if you want that? I shouldn't post the IMEI and Serial Number, right?
Click to expand...
Click to collapse
yes post it but remove the imei and s/n.
you might want to try a factory reset meanwhile

alray said:
yes post it but remove the imei and s/n.
you might want to try a factory reset meanwhile
Click to expand...
Click to collapse
Since I never backed anything up, I am royally screwed? Or is there a way to back things up as of now?
Here is the GetVAR.
C:\Program Files (x86)\Minimal ADB and Fastboot>
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1700.3
(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: 4305mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.093s

LATOKYO said:
Since I never backed anything up, I am royally screwed? Or is there a way to back things up as of now?
Here is the GetVAR.
C:\Program Files (x86)\Minimal ADB and Fastboot>
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1700.3
(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: 4305mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.093s
Click to expand...
Click to collapse
If you didn't synced your files with a cloud service like dropbox/google drive you'll loose everything on the phone. The only way to backup files from a phone in this state is by using adb from a custom recovery but since your bootloader is locked you can't do that (unlocking the bootloader to flash a custom recovery will wipe the phone).
You can use the 5.11.1700.3 RUU to restore your phone. This will also wipe everything from the phone like if it was brand new.
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
make sure to use the fastboot.exe version posted in that thread to flash the ruu.

alray said:
If you didn't synced your files with a cloud service like dropbox/google drive you'll loose everything on the phone. The only way to backup files from a phone in this state is by using adb from a custom recovery but since your bootloader is locked you can't do that (unlocking the bootloader to flash a custom recovery will wipe the phone).
You can use the 5.11.1700.3 RUU to restore your phone. This will also wipe everything from the phone like if it was brand new.
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
make sure to use the fastboot.exe version posted in that thread to flash the ruu.
Click to expand...
Click to collapse
This is quite tragic. Do you know why my phone is in the state it's in? Originally, it kept trying to install 5.1, but it kept getting an error and stopping, would this have been the cause? I don't even understand why it did that.
So, If I do do the RUU to restore. can I go back to install the 5.1. Or will it do it automatically for me?
I really appreciate your help! I wish more people could answer.

alray said:
If you didn't synced your files with a cloud service like dropbox/google drive you'll loose everything on the phone. The only way to backup files from a phone in this state is by using adb from a custom recovery but since your bootloader is locked you can't do that (unlocking the bootloader to flash a custom recovery will wipe the phone).
You can use the 5.11.1700.3 RUU to restore your phone. This will also wipe everything from the phone like if it was brand new.
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
make sure to use the fastboot.exe version posted in that thread to flash the ruu.
Click to expand...
Click to collapse
Also,
Should I take this opportunity to do anything with my phone, like Unlock or S-Off? Is it worth it. Since I may have to wipe it clean, I might as well make it fully unlocked and s-off? Your thoughts?

LATOKYO said:
This is quite tragic. Do you know why my phone is in the state it's in?
Click to expand...
Click to collapse
It could be because of corrupted files, failed ota updates or even hardware failure.
Originally, it kept trying to install 5.1, but it kept getting an error and stopping, would this have been the cause?
Click to expand...
Click to collapse
Its possible
So, If I do do the RUU to restore. can I go back to install the 5.1. Or will it do it automatically for me?
Click to expand...
Click to collapse
The ruu will install the same version you were on before the phone died, you should be able to update to 5.1 after (6.04.1700.6).
LATOKYO said:
Also,
Should I take this opportunity to do anything with my phone, like Unlock or S-Off? Is it worth it. Since I may have to wipe it clean, I might as well make it fully unlocked and s-off? Your thoughts?
Click to expand...
Click to collapse
The phone must be able to boot in order to achieve s-off and since its s-on the bootloader must be locked or re-locked to flash the RUU.
Once it can boot then you can achieve s-off if you want before updating it.

alray said:
It could be because of corrupted files, failed ota updates or even hardware failure.
Its possible
The ruu will install the same version you were on before the phone died, you should be able to update to 5.1 after (6.04.1700.6).
The phone must be able to boot in order to achieve s-off and since its s-on the bootloader must be locked or re-locked to flash the RUU.
Once it can boot then you can achieve s-off if you want before updating it.
Click to expand...
Click to collapse
OK.
For the RUU Install, since I am an idiot and afriad:
Step by Step:
- I install the RUU for 5.11.1700.3 (since that's what my GetVar says I have)
- I follow these steps afterwards:
1. Rename file to RUU.zip
2. Place it in adb folder
3. Reboot phone to fastboot mode
4. S On need to relock bootloader (fastboot oem lock) , S Off lock not needed
5. Also use the htc_fastboot.exe not the normal fastboot.exe
get the htc_fastboot.exe : Here
Rename htc_fastboot to fastboot or if you don't rename it, then the command will be "htc_fastboot flash zip RUU.zip"
Run the following commands from your adb folder:
6.htc_fastboot oem rebootRUU
7.htc_fastboot flash zip RUU.zip
8.htc_fastboot reboot-bootloader
And then I am done?

LATOKYO said:
OK.
For the RUU Install, since I am an idiot and afriad:
Step by Step:
- I install the RUU for 5.11.1700.3 (since that's what my GetVar says I have)
- I follow these steps afterwards:
1. Rename file to RUU.zip
2. Place it in adb folder
3. Reboot phone to fastboot mode
4. S On need to relock bootloader (fastboot oem lock) , S Off lock not needed
5. Also use the htc_fastboot.exe not the normal fastboot.exe
get the htc_fastboot.exe : Here
Rename htc_fastboot to fastboot or if you don't rename it, then the command will be "htc_fastboot flash zip RUU.zip"
Run the following commands from your adb folder:
6.htc_fastboot oem rebootRUU
7.htc_fastboot flash zip RUU.zip
8.htc_fastboot reboot-bootloader
And then I am done?
Click to expand...
Click to collapse
Yes no need to do step 4 as your bootloader is already locked.
Don't forget you need to use fastboot.exe version provided in this thread
And careful when renaming the file to "ruu.zip". If the .zip is hidden before renaming the file "ruu" do not add .zip because you'll have double file extensions (ruu.zip + the hidden .zip = ruu.zip.zip). If you want to avoid double file extension, configure Window so it will never hide file extension.
If you have any problem during this process, post a screenshot of your command window so we can see what is wrong exactly.

@alray
Yes no need to do step 4 as your bootloader is already locked.
Don't forget you need to use fastboot.exe version provided in this thread
And careful when renaming the file to "ruu.zip". If the .zip is hidden before renaming the file "ruu" do not add .zip because you'll have double file extensions (ruu.zip + the hidden .zip = ruu.zip.zip). If you want to avoid double file extension, configure Window so it will never hide file extension.
If you have any problem during this process, post a screenshot of your command window so we can see what is wrong exactly.
Click to expand...
Click to collapse
Also, Can I do all this on MAC, or can this only be done on Windows?

[Q] hboot 1.44.00 and can't move forward nor backwards

Hi everyone
Been on Cyanogenmod 11-20140424-NIGHTLY-M7 for far too long and wanted to either upgrade Cyanogenmod or, better yet, move to Viper. I'm somewhat skilled with Windows and Linux, but I can't seem getting things to work.
What I've got:
HTC One M7 (unbranded, bought in Switzerland)
Unlocked S-ON
hboot: 1.44.0000
M7-UL PVT SHIP S-ON RH
RADIO-4A.14.3250.13
OpenDSP-v26-120-274-0202
CID: HTC_102
It's rooted and got CWM ROM-Manager installed
Notebook with Windows 8.1, USB 3.0 all around
What I've tried so far:
Getting S-OFF
- Did not work. revone throws an ERROR=1 at me when I try to ./revone -P. I've tried like a hundred times, with su and all.
Then I tried to relock and get an RUU on it:
- Relocking did not work. Neither with revone (./revone -l or -r is successful on the CLI, but does nothing, i.e. still says *** UNLOCKED *** in the bootloader), nor with fastboot...
- ... as fastboot does not work, either. Tried different drivers and all, but fastboot always says < waiting for device >. So fastboot oem lock achieved nothing, either.
Then I just tried to install an RUU to get to JB and hboot 1.55 to then continue with rumrunner. This got stuck at some boot-image showing the HTC logo and the .exe cancelled.
Is USB3.0 breaking my neck here or do I have any other options to get to ViperOne?
Thanks in advance...

From what i've read in here many times, hboot 1.44 isn't compatiable with windows 8. 1. You need to use a windows 7 machine.

dorsetqpr said:
From what i've read in here many times, hboot 1.44 isn't compatiable with windows 8. 1. You need to use a windows 7 machine.
Click to expand...
Click to collapse
Correct
Hoelli169 said:
Hi everyone
Been on Cyanogenmod 11-20140424-NIGHTLY-M7 for far too long and wanted to either upgrade Cyanogenmod or, better yet, move to Viper. I'm somewhat skilled with Windows and Linux, but I can't seem getting things to work.
What I've got:
HTC One M7 (unbranded, bought in Switzerland)
Unlocked S-ON
hboot: 1.44.0000
M7-UL PVT SHIP S-ON RH
RADIO-4A.14.3250.13
OpenDSP-v26-120-274-0202
CID: HTC_102
It's rooted and got CWM ROM-Manager installed
Notebook with Windows 8.1, USB 3.0 all around
What I've tried so far:
Getting S-OFF
- Did not work. revone throws an ERROR=1 at me when I try to ./revone -P. I've tried like a hundred times, with su and all.
Then I tried to relock and get an RUU on it:
- Relocking did not work. Neither with revone (./revone -l or -r is successful on the CLI, but does nothing, i.e. still says *** UNLOCKED *** in the bootloader), nor with fastboot...
- ... as fastboot does not work, either. Tried different drivers and all, but fastboot always says < waiting for device >. So fastboot oem lock achieved nothing, either.
Then I just tried to install an RUU to get to JB and hboot 1.55 to then continue with rumrunner. This got stuck at some boot-image showing the HTC logo and the .exe cancelled.
Is USB3.0 breaking my neck here or do I have any other options to get to ViperOne?
Thanks in advance...
Click to expand...
Click to collapse
Windows 8 and hboot 1.44 are not compatible. You should use Windows 7 or better still Linux (preferably ubuntu 32bit)
Sent from my M7 ARHD 84-Kitkat

OK, got my hands on a Linux notebook and managed the relock the bootloader. This led to only being able to boot into Bootloader, Recovery and ROM did always boot into Bootloader.
Then I tried to get a RUU with JB4.3 on the device to be able to run rumrunner on hboot 1.55.
#sudo fastboot flash zip RUU.zip
sending 'zip' (1065710 KB)...
OKAY [ 59.411s}
writing 'zip' ...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 171.238s
Now I unlocked the bootloader again to at least be able to boot into CYM again.
Meh, I'm kinda lost here. I feel confused about RUUs, CIDs, Nandroid Backups and where to go from here.
Any ideas?
Edit:*Here's the fastboot-info
(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.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4128mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Edit2:*OK, I'm stuck in the CYM*launcher. Really kinda lost now D:

Hoelli169 said:
OK, got my hands on a Linux notebook and managed the relock the bootloader. This led to only being able to boot into Bootloader, Recovery and ROM did always boot into Bootloader.
Then I tried to get a RUU with JB4.3 on the device to be able to run rumrunner on hboot 1.55.
#sudo fastboot flash zip RUU.zip
sending 'zip' (1065710 KB)...
OKAY [ 59.411s}
writing 'zip' ...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 171.238s
Now I unlocked the bootloader again to at least be able to boot into CYM again.
Meh, I'm kinda lost here. I feel confused about RUUs, CIDs, Nandroid Backups and where to go from here.
Any ideas?
Edit:*Here's the fastboot-info
(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.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4128mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Edit2:*OK, I'm stuck in the CYM*launcher. Really kinda lost now D:
Click to expand...
Click to collapse
Download this recovery. http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
Put the file in your fastboot folder.
Download this Rom. Put the zip in your fastboot folder and rename it rom.zip
http://www.htc1guru.com/dld/guru_reset_m7_1-29-401-13-zip/
Flash the recovery with fastboot
Code:
fastboot erase cache
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot reboot-bootloader
Select recovery from the bootloader menu. While in TWRP recovery. Push the Rom. Type
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push us complete. Do a full wipe and install the Rom. During the install setup choose these options.
Stock recovery = yes
Stock radio = yes
Root = No
You will now have full stock Rom and recovery. Reboot the device and go to settings>about>Software Updates. Download and install the OTA update. Repeat process untill your on JB 3.xx.401.x firmware. Then use rumrunner to gain s-off. :good:
Sent from my M7 ARHD 84-Kitkat

Danny201281 said:
Download this recovery.
Put the file in your fastboot folder.
Download this Rom. Put the zip in your fastboot folder and rename it rom.zip
Flash the recovery with fastboot
Code:
fastboot erase cache
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
Worked!
Select recovery from the bootloader menu. While in TWRP recovery. Push the Rom. Type
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push us complete. Do a full wipe and install the Rom. During the install setup choose these options.
Click to expand...
Click to collapse
This didn't work. While in TWRP, adb was not able to connect. Funnily enough, flashing TWRP*allowed me to boot into CYM again. Activated USB*Debugging and allowed the Host to connect, but still no luck in TWRP.
But since I*had access again I* just copied the Guru image over USB*to the Sdcard, booted back into TWRP*and installed the ROM*manually.
Stock recovery = yes
Stock radio = yes
Root = No
You will now have full stock Rom and recovery. Reboot the device and go to settings>about>Software Updates. Download and install the OTA update. Repeat process untill your on JB 3.xx.401.x firmware.
Click to expand...
Click to collapse
219486214 reboots later... JB*3.62.401.1, hooray!
Then use rumrunner to gain s-off. :good:
Click to expand...
Click to collapse
Another adventure... In the official instructions it says unlocked OR*rooted, so I*did not bother with rooting.
rumrunner then failed and damaged Recovery leading to not being able to boot into TWRP*and thus being unable to install SuperSu zip.
Had to reflash recovery, install SuperSu and run rumrunner again... Which again failed (becuase the screen was off, I did not see that ADB*Shell requested root).
After a couple of tries now it worked ^_^
Thanks a lot for your explanations.
Now I just have to find out how to get to Firmware 5.0.2 to install the latest ViperOne.
Edit:*When I try to run the OTA*update to 4.19.401.11 it just boots into Recovery

Hoelli169 said:
Worked!
This didn't work. While in TWRP, adb was not able to connect. Funnily enough, flashing TWRP*allowed me to boot into CYM again. Activated USB*Debugging and allowed the Host to connect, but still no luck in TWRP.
But since I*had access again I* just copied the Guru image over USB*to the Sdcard, booted back into TWRP*and installed the ROM*manually.
219486214 reboots later... JB*3.62.401.1, hooray!
Another adventure... In the official instructions it says unlocked OR*rooted, so I*did not bother with rooting.
rumrunner then failed and damaged Recovery leading to not being able to boot into TWRP*and thus being unable to install SuperSu zip.
Had to reflash recovery, install SuperSu and run rumrunner again... Which again failed (becuase the screen was off, I did not see that ADB*Shell requested root).
After a couple of tries now it worked ^_^
Thanks a lot for your explanations.
Now I just have to find out how to get to Firmware 5.0.2 to install the latest ViperOne.
Edit:*When I try to run the OTA*update to 4.19.401.11 it just boots into Recovery
Click to expand...
Click to collapse
You need stock rom and recovery to install OTA updates. You can just flash the rom again with stock recovery to take further OTAs.
But as your now s-off you can just flash the firmware manually. You don't need to re lock the bootloader again. That's only for s-on users.
You can download the rest of the firmware updates here https://www.androidfilehost.com/?w=files&flid=32777
You must flash at least one zip for each firmware version. I.e if your on 3.xx.401.x then you have to flash
4.xx.401.x
5.xx.401.x
6.xx.401.x
7.xx.401.x
Then you can flash twrp and install a lollipop rom. You should have the rom on the internal storage before you start as the device won't boot after flashing the firmware as it will replace the stock boot.img. So you will need to flash a rom before it will boot. :good:
Commands for flashing the firmware zip as follows.
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip "name-of-firmware".zip
fastboot flash zip "name-of-firmware".zip
fastboot reboot-bootloader
Flash TWRP, Install Rom, Done :good:
Sent from my SM-T230 using Tapatalk

Danny201281 said:
You need stock tom and recovery to install OTA updates. You can just flash the rom again with stock recovery to take further OTAs.
But as your now s-off you can just flash the firmware manually. You don't need to re lock the bootloader again. That's only for s-on users.
You can download the rest of the firmware updates here
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
I thought I had to adhere to some upgrade path when handling firmwares but if that's not the case I'll be happy to use the latest, thanks!

Hoelli169 said:
I thought I had to adhere to some upgrade path when handling firmwares but if that's not the case I'll be happy to use the latest, thanks!
Click to expand...
Click to collapse
See my edited post above. You can't just flash the latest firmware. It might work but there's a risk of bricking your phone if you skip firmware versions
Sent from my SM-T230 using Tapatalk

Danny201281 said:
See my edited post above. You can't just flash the latest firmware. It might work but there's a risk of bricking your phone if you skip firmware versions
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
Ahh yes. Well, another interesting one going through the firmware updates. Going from 5.xx to 6.xx nearly killed my phone. Screen went black no matter how long I*pressed the power button and connecting through USB*mounted some strange folders on the device.
Luckily found Dexter's thread and his unbricking script solved the problem:
http://forum.xda-developers.com/showthread.php?t=2770684
Now ViperOne is updating, yay ^__^

Hoelli169 said:
Ahh yes. Well, another interesting one going through the firmware updates. Going from 5.xx to 6.xx nearly killed my phone. Screen went black no matter how long I*pressed the power button and connecting through USB*mounted some strange folders on the device.
Luckily found Dexter's thread and his unbricking script solved the problem:
http://forum.xda-developers.com/showthread.php?t=2770684
Now ViperOne is updating, yay ^__^
Click to expand...
Click to collapse
[emoji28] few!! Yeah firmware can be tricky. Glad you got it sorted though. Dexter's thread is a life saver. . Enjoy lollipop :good:
Sent from my SM-T230 using Tapatalk