Database Develop

Bricked Bootloader

Hey guys,
slowly I really get in trouble. I think the bootloader is bricked and i can use the phone as a door stopper.
I tell you what happens:
Long time ago i decided to root my phone. so I unlocked it via htcdev.com. After success I wanted to S-Off the bootloader with revone. But it failed, because of hboot 1.54.
Then I installed ARHD via TWRP and flashed boot.img via fastboot.
Long time every thing went fine, until yesterday it stoped to work and started bootloops. I managed to start the bootloader but nothing else. No ROM, no recovery (stucks on first twrp screen).
bootloader info says:
Code:
(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: 24Ð161Ð╬
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH34PW905197
(bootloader) imei: XXXXXXXXXXX7434 --> deleted just in this thread
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3794mV
(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.043s
Link to photo of the bootloader
What i tried until now (without any results):
"fastboot erase cache" to get access to recovery
"fastboot oem reboot RUU" to install a new hboot --> boots to white "quietly brilliant" screen, reboots then to bootloader
It would be great if someone can help me or can give me some tipps to unbrick this phone.
Thanks to all helpers.
Greetings Bulaktos

What RUU did you flash? Seeing as you're S-off you need to be extremely careful with RUUs and you might have flashed the wrong one, if you've flashed a downgrade then your device is bricked.

I didn't flashed any ruu. I only flashed the recovery and the boot.img for Arhd.
Until now I didn't flashed any firmware.
Sent from my Nexus 4 using xda app-developers app

Bulkatos said:
I didn't flashed any ruu. I only flashed the recovery and the boot.img for Arhd.
Until now I didn't flashed any firmware.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
We dont flash boot.img anymore the bootloader 1.54 does not will the command fastboot flash boot.img. flash ARHD again

Bulkatos said:
Hey guys,
slowly I really get in trouble. I think the bootloader is bricked and i can use the phone as a door stopper.
I tell you what happens:
Long time ago i decided to root my phone. so I unlocked it via htcdev.com. After success I wanted to S-Off the bootloader with revone. But it failed, because of hboot 1.54.
Then I installed ARHD via TWRP and flashed boot.img via fastboot.
Long time every thing went fine, until yesterday it stoped to work and started bootloops. I managed to start the bootloader but nothing else. No ROM, no recovery (stucks on first twrp screen).
bootloader info says:
Code:
(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: 24Ð161Ð╬
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH34PW905197
(bootloader) imei: XXXXXXXXXXX7434 --> deleted just in this thread
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3794mV
(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.043s
Link to photo of the bootloader
What i tried until now (without any results):
"fastboot erase cache" to get access to recovery
"fastboot oem reboot RUU" to install a new hboot --> boots to white "quietly brilliant" screen, reboots then to bootloader
It would be great if someone can help me or can give me some tipps to unbrick this phone.
Thanks to all helpers.
Greetings Bulaktos
Click to expand...
Click to collapse
Just
fastboot erase cache
fastboot flash recoveryname.zip
fastboot reboot-bootloader
Select recovery
Flash any rom
Sent from my iPod touch using Tapatalk

@n1234d
Thats all? I will gave it a try, when I have time. What about the bootloader? It seems to me that it is broken on a strange way.
Can I repair it on any way?
Sent from my Nexus 4 using xda app-developers app

Bulkatos said:
@n1234d
Thats all? I will gave it a try, when I have time. What about the bootloader? It seems to me that it is broken on a strange way.
Can I repair it on any way?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Your bootloader is absolutely fine, it's just your recovery/rom. Just reflash both and you'll be good to go.

n1234d said:
Your bootloader is absolutely fine, it's just your recovery/rom. Just reflash both and you'll be good to go.
Click to expand...
Click to collapse
Okay, sounds good.
Another question:
I've read that I need the hboot 1.55 for Android 4.3, and Arhd 30 is based on 4.3. So I have to update the bootloader anyway?
Sent from my Nexus 4 using xda app-developers app

Bulkatos said:
Okay, sounds good.
Another question:
I've read that I need the hboot 1.55 for Android 4.3, and Arhd 30 is based on 4.3. So I have to update the bootloader anyway?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Nope, you don't *need* 1.55 for a 4.3 rom, you'll be good with 1.54. If you OTA or RUU, it'll update automatically.
Sent from my iPod touch using Tapatalk

mh, seems more difficult to be.
fastboot erase cache -> says okay
fastboot flash recovery cwm.img -> says "okay"
fastboot reboot-bootloader -> reboots phone to white HTC bootscreen, then I reboot to hboot manually and choose recovery. twrps want to boot (but freeze)
It seems to me, that the command to flash the recovery didn't worked very well. What can I still do?

Bulkatos said:
mh, seems more difficult to be.
fastboot erase cache -> says okay
fastboot flash recovery cwm.img -> says "okay"
fastboot reboot-bootloader -> reboots phone to white HTC bootscreen, then I reboot to hboot manually and choose recovery. twrps want to boot (but freeze)
It seems to me, that the command to flash the recovery didn't worked very well. What can I still do?
Click to expand...
Click to collapse
try flashing the latest TWRP recovery. It can be found somewhere around here....
You can always try just restoring via RUU too, you just need to be in fastboot mode in order for it to work.

chenchen399 said:
try flashing the latest TWRP recovery. It can be found somewhere around here....
You can always try just restoring via RUU too, you just need to be in fastboot mode in order for it to work.
Click to expand...
Click to collapse
I did so. same results.
Fastboot reboot-bootloader -> reboots phone normal
fastboot flash recovery twrp.img -> twrp won't start

Try re flashing the hboot then, but you have to be s-off to do this. The only other way I can think of is RUU

Bulkatos said:
I did so. same results.
Fastboot reboot-bootloader -> reboots phone normal
fastboot flash recovery twrp.img -> twrp won't start
Click to expand...
Click to collapse
move the twrp.img file on adb folder.. and try again

Bulkatos said:
I did so. same results.
Fastboot reboot-bootloader -> reboots phone normal
fastboot flash recovery twrp.img -> twrp won't start
Click to expand...
Click to collapse
try this version of cwm it's a non touch version
https://www.dropbox.com/s/kbrzunsw0c17cyw/cwmclassic.zip

Slim Shady said:
try this version of cwm it's a non touch version
https://www.dropbox.com/s/kbrzunsw0c17cyw/cwmclassic.zip
Click to expand...
Click to collapse
how to flash a zip in fastboot? flashing the img-file via "fastboot flash recovery name.img" don't work (like all other commands).

Bulkatos said:
how to flash a zip in fastboot? flashing the img-file via "fastboot flash recovery name.img" don't work (like all other commands).
Click to expand...
Click to collapse
ur experiencing problems so try these two methods:
1.) Extract the zip and flash the recovery the usual way
fastboot erase cache
fastboot flash recovery recoveryname.img
fastboot reboot-bootloader
2.) open the zip file and edit the android text file in accordance to ur mid cid and mainver save and save it.You will need stock recovery for this method if dont have it here is the link https://www.dropbox.com/s/wq2t9fctnn9186j/stockrecovery.img
to flash stock recovery follow the steps in method 1 then follow the steps given below :
fastboot erase cache
fastboot reboot oemRUU
fastboot flash zip zipfilename.zip
then it will fail once
again the same command
fastboot flash zip zipfilename.zip
when it shows it is finished in cmd type
fastboot reboot-bootloader
either of them should lead to a working recovery

Bulkatos said:
how to flash a zip in fastboot? flashing the img-file via "fastboot flash recovery name.img" don't work (like all other commands).
Click to expand...
Click to collapse
yep:
fastboot flash recovery <name of recovery>.img
fastboot erase cache <- if you dont do this after flashing a recovery, it will most like either freeze or reboot without entering recovery
fastboot reboot-bootloader
-> enter RECOVERY
BTW: I took a look at the screenshot, does it really say in red text OS-2.24X161XX (!RR!XXXX) ??
---------- Post added at 01:56 PM ---------- Previous post was at 01:52 PM ----------
Slim Shady said:
2.) open the zip file and edit the android text file in accordance to ur mid cid and mainver
fastboot erase cache
fastboot reboot oemRUU
fastboot flash zip zipfilename.zip
when it shows it is finished in cmd type
fastboot reboot-bootloader
either of them should lead to a working recovery
Click to expand...
Click to collapse
He has S-ON so careful flashing firmware! It has to be signed and it's a one way ticket with S-On, no downgrade possible. And remember "fastboot flash zip zipfilename.zip" usually has to be done twice (the first one usually fails and says "FAILED flush again immediately" the second time it should show success)

nkk71 said:
yep:
fastboot flash recovery <name of recovery>.img
fastboot erase cache <- if you dont do this after flashing a recovery, it will most like either freeze or reboot without entering recovery
fastboot reboot-bootloader
-> enter RECOVERY
BTW: I took a look at the screenshot, does it really say in red text OS-2.24X161XX (!RR!XXXX) ??
---------- Post added at 01:56 PM ---------- Previous post was at 01:52 PM ----------
He has S-ON so careful flashing firmware! It has to be signed and it's a one way ticket with S-On, no downgrade possible. And remember "fastboot flash zip zipfilename.zip" usually has to be done twice (the first one usually fails and says "FAILED flush again immediately" the second time it should show success)
Click to expand...
Click to collapse
thanks for pointing it out actually forgot to mention it again and he is s-on that's why the second method cause that usually works.

Slim Shady said:
thanks for pointing it out actually forgot to mention it again and he is s-on that's why the second method cause that usually works.
Click to expand...
Click to collapse
you mean "edit the android text file in accordance to ur mid cid and mainver save and save it"? He can give it a try but I don't think it will work, as soon as he edits the android.txt file, the firmware.zip will become unsigned, and won't pass with S-On.

[Q] HTC One Goole Edition Stuck in Bootloop after 4.4 update. Help please!

Hello-
Here is the fast version:
HTC One GPE with stock JB rom and clockwork mod recovery.
Last night I flashed the recovery to a stock version I found on the boards here. This morning the most recent JB update was ready for installation on the phone. A while after that KitKat was ready and I installed. As soon as I did, the phone entered a boot loop and will not stay on. I've cleared the cache and factory reset with no luck. A kind individual on another thread attempted to help resolve the issue but no such luck.
I tried reinstalling 4.4 (having to relock my bootloader was the only way I could successfully attempt reloading, but it did not work. S-off is ON.
Now, I cannot enter a custom recovery (nor a recovery of any kind at this moment). Any time I select recovery it just reboots the phone.
Here are previous errors I received while attempting fastboot flash:
bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
FAILED (remote: 24 parsing android-info fail)
Here is my fastboot getvar all:
c:\And>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(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: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4241mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I appreciate any help you may be able to offer. I've never had this much trouble with a phone before (somewhat of a novice, but this is beyond me).
Thank you!!!

unlock the bootloader again and install a custom recovery
then install the zip from here using adb sideload: http://forum.xda-developers.com/showthread.php?t=2341395

Right, so your bootloader is locked or unlocked? If locked, are you able to unlock it?

SaHiLzZ said:
Right, so your bootloader is locked or unlocked? If locked, are you able to unlock it?
Click to expand...
Click to collapse
I use the command "fastboot oem lock" and "fastboot oem unlock" to lock and unlock the device (since it's google play edition), unless that is for unlocking something else besides the bootloader.
I cannot open the recovery so I don't know what is on there. I've loaded TWRP with fastboot but every time I select recovery from the menu on the phone it reboots the phone.
Here is what I get when I search for the phone. I assume the adb is not seeing it since I have not set up the phone for that option?
c:\And>adb devices
List of devices attached
c:\And>fastboot devices
HT36JW912382 fastboot

Can you download either CWM or TWRP and try the following from bootloader:
fastboot boot nameofrecovery.img
For example: If you get http://flyhalf205.com/recoveries/recovery-clockwork-touch-6.0.4.5-m7ul.img
then fastboot boot recovery-clockwork-touch-6.0.4.5-m7ul.img in fastboot mode
Does the phone reboot into recovery now?

c:\And>fastboot boot openrecovery-twrp-2.6.3.3-m7.img
downloading 'boot.img'...
OKAY [ 1.202s]
booting...
OKAY [ 0.001s]
This just froze the phone.
It will NOT boot into recovery. Just turns on and shows "Google"
QUOTE=SaHiLzZ;47949555]Can you download either CWM or TWRP and try the following from bootloader:
fastboot boot nameofrecovery.img
For example: If you get http://flyhalf205.com/recoveries/recovery-clockwork-touch-6.0.4.5-m7ul.img
then fastboot boot recovery-clockwork-touch-6.0.4.5-m7ul.img in fastboot mode
Does the phone reboot into recovery now?[/QUOTE]

Try the recovery linked and twrp 2.6.3.0?

fastboot erase cache

damon7620 said:
fastboot erase cache
Click to expand...
Click to collapse
SaHiLzZ said:
Try the recovery linked and twrp 2.6.3.0?
Click to expand...
Click to collapse
I have cleared the cache before and after loading the custom recovery. and I loaded the CWR recovery. Still will not load into recovery. Just turns off and boots to Google.

i was able to successfully re-load the stock recovery. Any suggestions from this point?

How? What recovery did you use?
Go to bootloader and a do a factory reset from bootloader, it should boot into stock recovery and wipe , (should not just get kicked out right away)
What's the result after doing this.?

SaHiLzZ said:
How? What recovery did you use?
Go to bootloader and a do a factory reset from bootloader, it should boot into stock recovery and wipe , (should not just get kicked out right away)
What's the result after doing this.?
Click to expand...
Click to collapse
I used one I found somewhere in this thread. http://forum.xda-developers.com/showthread.php?t=2358781&highlight=recovery
I cannot recall the exact one. It is the same one I installed last night before this morning's update.
I did the wipe and loaded into bootloader. Rebooted the phone and is now in a boot loop.

Hi @The_Doctor_Who here's what I would recommend:
- fastboot oem unlock (if not already in the unlocked state)
- download the latest official ClockworkMod touch recovery for m7ul directly from here: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.3-m7ul.img
- fastboot boot recovery-clockwork-touch-6.0.4.3-m7ul.img
Note the use of 'boot' instead of 'flash' for the last command... let's narrow this down and see if you can just boot a well-known/official recovery for this model without flashing anything. Sorry if these steps seem repetitive at this point, but it's a little hard to know what all has been done.

goldenratio said:
Hi @The_Doctor_Who here's what I would recommend:
- fastboot oem unlock (if not already in the unlocked state)
- download the latest official ClockworkMod touch recovery for m7ul directly from here: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.3-m7ul.img
- fastboot boot recovery-clockwork-touch-6.0.4.3-m7ul.img
Note the use of 'boot' instead of 'flash' for the last command... let's narrow this down and see if you can just boot a well-known/official recovery for this model without flashing anything. Sorry if these steps seem repetitive at this point, but it's a little hard to know what all has been done.
Click to expand...
Click to collapse
Hey! Thank!
I understand re: not knowing. I've tried using that recovery and cannot get into it. I also tried the fastboot boot and it froze the phone (someone motioned HTC removed the ability to use 'boot' with the hboot 1.54). I tried leting the phone sit in the frozen state but it would not do anything.

The_Doctor_Who said:
I've tried using that recovery and cannot get into it. I also tried the fastboot boot and it froze the phone.
Click to expand...
Click to collapse
I see. Do I understand the the sequence of events correctly:
- you flashed a stock JB ROM
- then flashed the stock recovery (which file exactly? was it for m7ul?)
- the phone booted okay at this point and prompted you for 2 over-the-air system updates:
= an update for JB
= an update to KitKat
- things broke at this point?
The_Doctor_Who said:
someone motioned HTC removed the ability to use 'boot' with the hboot 1.54.
Click to expand...
Click to collapse
Do you have a link for that thread handy? I wonder if it's trivial or not to downgrade the radio (HBOOT)... I haven't tried before.

goldenratio said:
I see. Do I understand the the sequence of events correctly:
- you flashed a stock JB ROM
- then flashed the stock recovery (which file exactly? was it for m7ul?)
I will have to find the file. I believe it was. It was indicated that the stock recovery was from the GPE One.
- the phone booted okay at this point and prompted you for 2 over-the-air system updates:
= an update for JB
= an update to KitKat
- things broke at this point?
The update for JB was fine. I was checking twitter, facebook, etc. Then the KitKat update came in. I selected download and install and that is where the problem started.
Do you have a link for that thread handy? I wonder if it's trivial or not to downgrade the radio (HBOOT)... I haven't tried before.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=47972147&postcount=16
From what I have seen downgrading is not an option, but I could be wrong.

@The_Doctor_Who thanks for the link. It doesn't specifically say you can't use 'fastboot boot' on the GPE version of HBOOT. I'm pretty sure you can (assuming things are working otherwise). At least, I had a version of the 1.54 HBOOT on m7ul which didn't seem to have this restriction... I don't know the exact version number unfortunately.
That aside, it does seem that the recovery partition may be corrupted or in a bad state somehow. I'm going to reply on the other thread since those guys seem to have some good info and have been super helpful. I have a couple of ideas I'll post there.

At this point what I would recommend is to use the factory images for it and attempt to restore it to full stock before trying to go any further.

[Q] possible to s-off or unlock bootloader with usb debug off???

Hello
I have HTC one m7_u cid 332 hboot 1.55
For my phone there is no stock RUU searched every where
Phone is hang on HTC logo
I can go to fast boot menu tryed to unlock bootloader with htcdev but not work
My question is there any way to s-off or unlock boot loader without USB debugging on ?????
Tanx

afghan-gsm-mastermind said:
Hello
I have HTC one m7_u cid 332 hboot 1.55
For my phone there is no stock RUU searched every where
Phone is hang on HTC logo
I can go to fast boot menu tryed to unlock bootloader with htcdev but not work
My question is there any way to s-off or unlock boot loader without USB debugging on ?????
Tanx
Click to expand...
Click to collapse
bootloader is unlocked with fastboot not adb, so usb debugging is not required. Btw usb debugging only affect the usb connection when the phone is booted in the OS so its does not affect bootloader unlocking, fastboot commands or adb commands from recovery.

alray said:
bootloader is unlocked with fastboot not adb, so usb debugging is not required. Btw usb debugging only affect the usb connection when the phone is booted in the OS so its does not affect bootloader unlocking, fastboot commands or adb commands from recovery.
Click to expand...
Click to collapse
I tried unlocking bootloader with htcdev all thing gose OK but after restart phone is lock again I should say phone is dead and hang on HTC logo

Waiting for help .......

afghan-gsm-mastermind said:
Waiting for help .......
Click to expand...
Click to collapse
how are we suppose to help you with a locked bootloader ?

clsA said:
how are we suppose to help you with a locked bootloader ?
Click to expand...
Click to collapse
I've told him this in a previous thread. . Without an unlocked bootloader he is stuck.. He has to unlock first...
Sent from my GT-I9505 using XDA Premium 4 mobile app

s-on, No Os, unlocked, got twrp. Cant install stock RUU!!
Hi. Im a little bit confused with my HTC__016 One M7, My phone is currently S-On with no Os and no recovery image. I cant transfer a stock ruu to my phone or twrp to install. I have tried using adb and fastboot, I have cleared all caches too. If i boot into recovery and i use twrp to fix permissions it says E: Unable to mount data and cache. I have tried adb sideload aswell and it seems to work but then always fails at the certificate verification.. I assume that this is S-On's fault. How should i proceed? I dont want to hard brick my device, i still have my basebands too thank goodness..
What can I do to fix my phones file system or how can i transfer the stock RUU.. I have tried 3 diferent stock RUUs and they all fail at certificate verification. I would really appreciate the help..
Thanks A lot

AnonZA said:
Hi. Im a little bit confused with my HTC__016 One M7, My phone is currently S-On with no Os and no recovery image. I cant transfer a stock ruu to my phone or twrp to install. I have tried using adb and fastboot, I have cleared all caches too. If i boot into recovery and i use twrp to fix permissions it says E: Unable to mount data and cache. I have tried adb sideload aswell and it seems to work but then always fails at the certificate verification.. I assume that this is S-On's fault. How should i proceed? I dont want to hard brick my device, i still have my basebands too thank goodness..
What can I do to fix my phones file system or how can i transfer the stock RUU.. I have tried 3 diferent stock RUUs and they all fail at certificate verification. I would really appreciate the help..
Thanks A lot
Click to expand...
Click to collapse
Post a fastboot getvar all minus imei no and serial no. Post links to recovery's you have tried and links to RUU'S. and also commands you have tried to flash recovery and RUU's
Sent from my GT-I9505 using XDA Premium 4 mobile app

AnonZA said:
Hi. Im a little bit confused with my HTC__016 One M7, My phone is currently S-On with no Os and no recovery image. I cant transfer a stock ruu to my phone or twrp to install. I have tried using adb and fastboot, I have cleared all caches too. If i boot into recovery and i use twrp to fix permissions it says E: Unable to mount data and cache. I have tried adb sideload aswell and it seems to work but then always fails at the certificate verification.. I assume that this is S-On's fault. How should i proceed? I dont want to hard brick my device, i still have my basebands too thank goodness..
What can I do to fix my phones file system or how can i transfer the stock RUU.. I have tried 3 diferent stock RUUs and they all fail at certificate verification. I would really appreciate the help..
Thanks A lot
Click to expand...
Click to collapse
sounds like your trying to sideload a RUU.zip .. that won't work
to flash RUU.zip use
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip <<yes two times
fastboot reboot
you just need the rom.zip in the same folder as fastboot

HTC__016
bored_stupid said:
Post a fastboot getvar all minus imei no and serial no. Post links to recovery's you have tried and links to RUU'S. and also commands you have tried to flash recovery and RUU's
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__016
(bootloader) battery-status: good
(bootloader) battery-voltage: 3847mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(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.045s
---------- Post added at 04:00 PM ---------- Previous post was at 03:55 PM ----------
clsA: I tried those command million of times. It kept coming back with "boot loader signature verification..." My phone is WIPED as you can see. So usb debugging is off presumably..
Click to expand...
Click to collapse

You have the international M7 ul so download and install this rom. Follow the guide on installing
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
Sent from my GT-I9505 using XDA Premium 4 mobile app

I Formatted partition using "How to: Fix a corrupted DATA partition on the HTC One" Then tried these commands (1) fastboot oem rebootRUU (2) fastboot flash zip rom.zip
{C:\Users\####\Desktop\Mini SDK>fastboot flash zip rom.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1239446 KB)...
OKAY [ 46.879s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 61.244s
I think my next step is a stock stock RUU right?
Thanks a lot for the help..

Wrong one Apparently..
bored_stupid said:
You have the international M7 ul so download and install this rom. Follow the guide on installing
(LINK)
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I ran with admin rights, went through all the windows till i said update.. then i get error code 155, and that error code means incorrect ROM according to the programs readme!
What other ROM should I try?
Sorry to be such a pain.. I just need to use my device again.. lol

AnonZA said:
I Formatted partition using "How to: Fix a corrupted DATA partition on the HTC One" Then tried these commands (1) fastboot oem rebootRUU (2) fastboot flash zip rom.zip
{C:\Users\####\Desktop\Mini SDK>fastboot flash zip rom.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1239446 KB)...
OKAY [ 46.879s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 61.244s
I think my next step is a stock stock RUU right?
Thanks a lot for the help..
Click to expand...
Click to collapse
Basically you are trying to flash a file in the bootloader that is not intended to be flashed that way. Use custom recovery or it may be an update, in that case it needs stock recovery.
Sent from my GT-I9505 using XDA Premium 4 mobile app

HTC One M7 Stuck in a Boot Loop

Alright, I recently purchased a phone that was stuck at the screen with the download icon in the arrow circle (http://forum.xda-developers.com/album.php?albumid=11886). When it is like this is can not be put into hboot. I then somehow got the phone into a boot loop. I did wipe the cache and that did not fix the problem. I did a factory reset via hboot, and it sent me back to the screen I mentioned before (http://forum.xda-developers.com/album.php?albumid=11886). I've now gotten the phone back into boot looping so I can access hboot. Recovery does work and you can access all the options. This phone is basically a stock HTC One M7. Has not been rooted, is locked, and it S-ON. Any help would be appreciated.
Thank you!

Flash a RUU

jdgreat4 said:
Flash a RUU
Click to expand...
Click to collapse
Could you link me to a tutorial? Apparently I need to know my MID and CID, and the video I did find to do that, needed usb debugging turned on in the settings which I don't even know if that is on. Can you link me to a how to tutorial for how to do this?

CloudHD said:
Could you link me to a tutorial? Apparently I need to know my MID and CID, and the video I did find to do that, needed usb debugging turned on in the settings which I don't even know if that is on. Can you link me to a how to tutorial for how to do this?
Click to expand...
Click to collapse
post the output of "fastboot getvar all", remove your imei and serialno before posting it

alray said:
post the output of "fastboot getvar all", remove your imei and serialno before posting it
Click to expand...
Click to collapse
Do I need a computer to do this? There's no option for this under fastboot in hboot. Currently don't have a computer available to me.

CloudHD said:
Do I need a computer to do this? There's no option for this under fastboot in hboot. Currently don't have a computer available to me.
Click to expand...
Click to collapse
Yes you need a computer with the latest android sdk installed and latest HTC drivers installed.
Btw, why did you buy this phone?

alray said:
Yes you need a computer with the latest android sdk installed and latest HTC drivers installed.
Btw, why did you buy this phone?
Click to expand...
Click to collapse
I bought it for a friend. He wanted something other than his locked up att samsung s4 active. He doesn't have much money and he figured he could fix this one and if he could't, he would just sell it again. I am personally used to iPhones (typing this on a jailbroken 4s right now) so this is all pretty new to me. We started troublesing it yesterday and he seemed to get stumped. He hates forums so I went ahead and signed up and made this post for him. Currently I have no access to a computer right now (at least one where I can install sdk and so on), but will have access later today. Will post when I have it.

CloudHD said:
I bought it for a friend. He wanted something other than his locked up att samsung s4 active. He doesn't have much money and he figured he could fix this one and if he could't, he would just sell it again. I am personally used to iPhones (typing this on a jailbroken 4s right now) so this is all pretty new to me. We started troublesing it yesterday and he seemed to get stumped. He hates forums so I went ahead and signed up and made this post for him. Currently I have no access to a computer right now (at least one where I can install sdk and so on), but will have access later today. Will post when I have it.
Click to expand...
Click to collapse
Latest HTC driver here: http://www.mediafire.com/download/8pawcxm9walwras/HTC_Driver_4.14.0.001.exe
You can install minimal adb and fastboot instead of the complete sdk, will be easier to use for you: http://forum.xda-developers.com/showthread.php?t=2317790
Once you have both installed, connect the phone to your computer, make sure its booted in bootloader mode --> fastboot mode and showing "fastboot usb" in red.
On your computer: Start menu --> Programs --> Minimal adb and fasboot --> minimal adb and fastboot
in the command prompt, type:
Code:
fastboot getvar all
copy and paste the output here (except the imei and s/n)
see you later

alray said:
Latest HTC driver here: http://www.mediafire.com/download/8pawcxm9walwras/HTC_Driver_4.14.0.001.exe
You can install minimal adb and fastboot instead of the complete sdk, will be easier to use for you: http://forum.xda-developers.com/showthread.php?t=2317790
Once you have both installed, connect the phone to your computer, make sure its booted in bootloader mode --> fastboot mode and showing "fastboot usb" in red.
On your computer: Start menu --> Programs --> Minimal adb and fasboot --> minimal adb and fastboot
in the command prompt, type:
Code:
fastboot getvar all
copy and paste the output here (except the imei and s/n)
see you later
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3921mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

CloudHD said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3921mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Ok well there is no RUU you can use with s-on so while the bootloader is locked all you can do is try to flash the current firmware. If the phone doesn't boot after that you will need to unlock the bootloader.
Download the firmware here https://www.androidfilehost.com/?fid=23501681358543602 put the zip in your fastboot folder on your pc and rename it "firmware.zip" Now with fastboot usb connected in the bootloader flash the firmware with the following fastboot commands
Code:
fastboot erase cache
fastboot oem rebootRUU
case sensitive
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
Now try to reboot the phone. If it doesn't boot you should now at least be able to do a factory reset. But you will need to unlock the bootloader at www.htcdev.com register an account and follow the instructions in the Unlock My Bootloader section. :good:

Danny201281 said:
Ok well there is no RUU you can use with s-on so while the bootloader is locked all you can do is try to flash the current firmware. If the phone doesn't boot after that you will need to unlock the bootloader.
Download the firmware here https://www.androidfilehost.com/?fid=23501681358543602 put the zip in your fastboot folder on your pc and rename it "firmware.zip" Now with fastboot usb connected in the bootloader flash the firmware with the following fastboot commands
Code:
fastboot erase cache
fastboot oem rebootRUU
case sensitive
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
Now try to reboot the phone. If it doesn't boot you should now at least be able to do a factory reset. But you will need to unlock the bootloader at www.htcdev.com register an account and follow the instructions in the Unlock My Bootloader section. :good:
Click to expand...
Click to collapse
Followed your instructions. Everything went good. I did a factory reset and the phone actually ended up rebooting. It's now just sitting here, and seems to be stuck at the htc logo. Going to go ahead and follow the steps to unlock my bootloader then report back.

@Danny201281 Boot loader is now unlocked!

CloudHD said:
@Danny201281 Boot loader is now unlocked!
Click to expand...
Click to collapse
Now the bootloader is unlocked you will need to flash a custom recovery and install a new Rom.
Download this http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.8.5.0-m7.img *<<<<< Put this in your fastboot folder and rename it recovery.img
Download this https://www.androidfilehost.com/?fid=23501681358545274
Boot the device to the bootloader and connect fastboot usb. Flash the recovery with fastboot
Code:
fastboot erase cache
fastboot flash recovery recovery.img
fastboot reboot-bootloader
When back in the bootloader select Recovery from the menu to load TWRP recovery. Before we do anything else a little spring cleaning. Select "Wipe" from the TWRP menu the "Format Data" You will be prompted to type yes to continue. When its done Select "Reboot" then "Reboot Recovery" You will see a message "No OS Installed" Reboot anyway and say No when asked to install supersu.
Now back in TWRP recovery you should be able to see the Internal Storage on your PC. Copy the rom file to the Internal Storage then from the TWRP menu select install and choose the rom .zip :good:
During the install with Aroma choose these options
Stock Radio = Yes
Stock Recovery = Yes
Root = No
When the install is completed reboot the device and hopefully it should boot up normally without any problems :good: :fingers-crossed:
P.S The first boot after a new flash can take an extended amount of time. Don't be supprised if it's stuck on the HTC logo screen for 15 minutes+ Just be patient

Danny201281 said:
Now the bootloader is unlocked you will need to flash a custom recovery and install a new Rom.
Download this http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.8.5.0-m7.img *<<<<< Put this in your fastboot folder and rename it recovery.img
Download this https://www.androidfilehost.com/?fid=23501681358545274
Boot the device to the bootloader and connect fastboot usb. Flash the recovery with fastboot
Code:
fastboot erase cache
fastboot flash recovery recovery.img
fastboot reboot-bootloader
When back in the bootloader select Recovery from the menu to load TWRP recovery. Before we do anything else a little spring cleaning. Select "Wipe" from the TWRP menu the "Format Data" You will be prompted to type yes to continue. When its done Select "Reboot" then "Reboot Recovery" You will see a message "No OS Installed" Reboot anyway and say No when asked to install supersu.
Now back in TWRP recovery you should be able to see the Internal Storage on your PC. Copy the rom file to the Internal Storage then from the TWRP menu select install and choose the rom .zip :good:
During the install with Aroma choose these options
Stock Radio = Yes
Stock Recovery = Yes
Root = No
When the install is completed reboot the device and hopefully it should boot up normally without any problems :good: :fingers-crossed:
P.S The first boot after a new flash can take an extended amount of time. Don't be supprised if it's stuck on the HTC logo screen for 15 minutes+ Just be patient
Click to expand...
Click to collapse
Thank you! My friend wanted to ask about soff and root for his device

CloudHD said:
Thank you! My friend wanted to ask about soff and root for his device
Click to expand...
Click to collapse
For s-off he will have to use Sunshine App it's the only working method for hboot 1.57. It does cost $25 but It's very easy. Just install and run the app :good:
Rooting can be done a number of ways the 2 easiest are to allow TWRP to install SupeSu when leaving recovery. Or you can install root with the Guru reset rom by selecting root during the installer. Also if he want's to keep the TWRP recovery don't take the stock recovery during the rom install.

Danny201281 said:
For s-off he will have to use Sunshine App it's the only working method for hboot 1.57. It does cost $25 but It's very easy. Just install and run the app :good:
Rooting can be done a number of ways the 2 easiest are to allow TWRP to install SupeSu when leaving recovery. Or you can install root with the Guru reset rom by selecting root during the installer. Also if he want's to keep the TWRP recovery don't take the stock recovery during the rom install.
Click to expand...
Click to collapse
alright. when formatting, I have been getting an unable to mount /cache and /system. should i be worries. Also, so when I do install the supesu? Can you give me some more detailed instructions like you have been doing? They're very helpful!!2220

CloudHD said:
alright. when formatting, I have been getting an unable to mount /cache and /system. should i be worries. Also, so when I do install the supesu? Can you give me some more detailed instructions like you have been doing? They're very helpful!!2220
Click to expand...
Click to collapse
Unable to mount /cache and /system happens during format or after? Did you reboot recovery after the format?
When you exit recovery TWRP will detect wheather or not the device is rooted. If it's not rooted TWRP will ask if you want to install supersu to root the phone. Say yes and TWRP will install root.
Although you could just install root when you install the rom. Just install with these options instead
Stock = Recovery No
Stock = Radio Yes
Root = Yes

Danny201281 said:
Unable to mount /cache and /system happens during format or after? Did you reboot recovery after the format?
When you exit recovery TWRP will detect wheather or not the device is rooted. If it's not rooted TWRP will ask if you want to install supersu to root the phone. Say yes and TWRP will install root.
Although you could just install root when you install the rom. Just install with these options instead
Stock = Recovery No
Stock = Radio Yes
Root = Yes
Click to expand...
Click to collapse
It seems to say this while it is updating partition details. Havent rebooted it as I wasn't sure about the cache and everything. So I guess before.

CloudHD said:
It seems to say this while it is updating partition details. Havent rebooted it as I wasn't sure about the cache and everything. So I guess before.
Click to expand...
Click to collapse
Reboot Recovery and then copy over and install the rom :good:
When you format data it is like repartitioning the phone. All the partitions are gone until you reboot. That's the reason they won't mount

Danny201281 said:
Reboot Recovery and then copy over and install the rom :good:
Click to expand...
Click to collapse
Alright, Thank you very much!!!
Will update how it all wetn when finished.

[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