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] 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

[Q] HTC One M7 got into Bootloop, S-On, unrooted, Debug mode is off, only Fastboot

Hey guys, this is my first thread in XDA have quite some experience with samsung android but pretty new with HTC.
So, I dropped my HTC one day and it got stuck in a bootloop after few days. I havent change anything, stock, unrooted, never flashed any ROM into it, etc. I tried flashing RUU into it using fastboot command but it ddnt work since its still S-on.
Im working on mac as a platform and i dont think this is a major issue?
I am able to access recovery mode and fastboot mode, but wasnt able to push any file into it since debugging mode is off before the bootloop. ./adb devices command wont detect the phone. I also have HTC Sync installed on my mac but again, it wont detect the phone.
I also printed the getvar all result here:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.631.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36xxxxxxx7
(bootloader) imei: 3544xxxxxx23453
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3876mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
also attached is screenshot of bootloader mode.
please help. my phone have been like this for 2-3 weeks now

RoyalChalksHere said:
Hey guys, this is my first thread in XDA have quite some experience with samsung android but pretty new with HTC.
So, I dropped my HTC one day and it got stuck in a bootloop after few days. I havent change anything, stock, unrooted, never flashed any ROM into it, etc. I tried flashing RUU into it using fastboot command but it ddnt work since its still S-on.
Im working on mac as a platform and i dont think this is a major issue?
I am able to access recovery mode and fastboot mode, but wasnt able to push any file into it since debugging mode is off before the bootloop. ./adb devices command wont detect the phone. I also have HTC Sync installed on my mac but again, it wont detect the phone.
I also printed the getvar all result here:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.631.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36xxxxxxx7
(bootloader) imei: 3544xxxxxx23453
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3876mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
also attached is screenshot of bootloader mode.
please help. my phone have been like this for 2-3 weeks now
Click to expand...
Click to collapse
First of all is there any warranty left on the device. If there is it would be a good idea to take advantage of that before tampering with it. Especially as this happened after you dropped the phone. So there's a good chance it's a hardware problem.
I assume you've tried to factory reset from stock recovery?
If there's no warranty your best option is to unlock the bootloader. This will allow you to flash a Custom recovery. Then you can push a Rom to the phone, as adb will work in a custom recovery weather debugging is enabled or not.
I recommend TWRP 2.6.3.3 recovery it's not the latest twrp but is the most stable.

Danny201281 said:
First of all is there any warranty left on the device. If there is it would be a good idea to take advantage of that before tampering with it. Especially as this happened after you dropped the phone. So there's a good chance it's a hardware problem.
I assume you've tried to factory reset from stock recovery?
If there's no warranty your best option is to unlock the bootloader. This will allow you to flash a Custom recovery. Then you can push a Rom to the phone, as adb will work in a custom recovery weather debugging is enabled or not.
I recommend TWRP 2.6.3.3 recovery it's not the latest twrp but is the most stable.
Click to expand...
Click to collapse
yes ive tried factory reset too. I bought it in september 2013 from someone else and i think i lost the receipt, so i dont think I can take advantage of the warrant. i will keep looking though. is there any good link to unlock the bootloader?

RoyalChalksHere said:
yes ive tried factory reset too. I bought it in september 2013 from someone else and i think i lost the receipt, so i dont think I can take advantage of the warrant. i will keep looking though. is there any good link to unlock the bootloader?
Click to expand...
Click to collapse
www.htcdev.com to unlock the bootloader. You'll need to register an account. Then go to the Unlock my Bootloader section. Follow the instructions to get the Unlock code

I tried resetting rooted device... it rebooted in trwp... so i wiped it from there
when i reboot it doesn't move from the htc logo screen
when i try to power off, the soft keys blink and thats it.. nothing more.. i don't know what else to

@CallMe_Y_C said:
I tried resetting rooted device... it rebooted in trwp... so i wiped it from there
when i reboot it doesn't move from the htc logo screen
when i try to power off, the soft keys blink and thats it.. nothing more.. i don't know what else to
Click to expand...
Click to collapse
When you say you wiped it in twrp, did you Factory Reset or did you Format Data?
If you used Format Data then you wiped your entire device including the installed Rom. You should be able to force the device to power of by holding the power button for 60secs.
Then power on while holding volume down to get to the bootloader. Then you can boot to recovery and push a Rom with adb. :good:

awesome, thanks @Danny201281 i got TWRP to work on my HTC one. now on to custom rom. Which one is the best for HTC One? Any suggestion anyone? =)

RoyalChalksHere said:
awesome, thanks @Danny201281 i got TWRP to work on my HTC one. now on to custom rom. Which one is the best for HTC One? Any suggestion anyone? =)
Click to expand...
Click to collapse
Hehe I will always recommend Android Revolution HD because it's my favorite
But honestly is depends what you want from a Rom. ARHD is close to stock. It's very stable with no real bugs. It also has xposed support so you can make your own modifications. For me this gives a more personal experience.
MaximusHD is also a very popular close to stock Rom.
Or then you have the likes of Viper Rom or insertcoin which are more heavily modified.
But either way you look at it ARHD is a good place to start. It should be flashed with TWRP 2.6.3.3 TO avoid problems installing as most newer versions of TWRP don't seem to agree with the Aroma installer the Rom is packaged with :good:

Danny201281 said:
Hehe I will always recommend Android Revolution HD because it's my favorite
But honestly is depends what you want from a Rom. ARHD is close to stock. It's very stable with no real bugs. It also has xposed support so you can make your own modifications. For me this gives a more personal experience.
MaximusHD is also a very popular close to stock Rom.
Or then you have the likes of Viper Rom or insertcoin which are more heavily modified.
But either way you look at it ARHD is a good place to start. It should be flashed with TWRP 2.6.3.3 TO avoid problems installing as most newer versions of TWRP don't seem to agree with the Aroma installer the Rom is packaged with :good:
Click to expand...
Click to collapse
hey. ok so i downloaded AICP and installed them through TWRP and everything works fine. BUT, when i got to my homepage and use the phone for a couple of minutes, it restarted on its own. Any idea on why this is happening?

RoyalChalksHere said:
hey. ok so i downloaded AICP and installed them through TWRP and everything works fine. BUT, when i got to my homepage and use the phone for a couple of minutes, it restarted on its own. Any idea on why this is happening?
Click to expand...
Click to collapse
Go to Setting>About>Phone Identity
Is your IMEI displayed properly there?
Also check Setting>About>Software Information>More
Is your Baseband displayed correctly here?

Danny201281 said:
Go to Setting>About>Phone Identity
Is your IMEI displayed properly there?
Also check Setting>About>Software Information>More
Is your Baseband displayed correctly here?
Click to expand...
Click to collapse
oh they are both unknown. what should I do?

RoyalChalksHere said:
oh they are both unknown. what should I do?
Click to expand...
Click to collapse
9 times out of 10 this is a Hardware problem. You can try and flash a Firmware package and after that the only thing left Is to s-off and try an ruu. But if firmware doesn't fix it an ruu probably won't either.
As the phone had been dropped there's a high chance it's a hardware problem.
But I'll see if I can find a firmware package you can try. It's worth a go before writing it off.

Danny201281 said:
9 times out of 10 this is a Hardware problem. You can try and flash a Firmware package and after that the only thing left Is to s-off and try an ruu. But if firmware doesn't fix it an ruu probably won't either.
As the phone had been dropped there's a high chance it's a hardware problem.
But I'll see if I can find a firmware package you can try. It's worth a go before writing it off.
Click to expand...
Click to collapse
oh. so i guess warranty is the only way to go. or new phone. =( i even lost pictures from internal storage.

I couldn't find a firmware package but I did find this OTA. It contains the firmware we need. Download it and open the zip on your pc. Extract the firmware.zip and put the firmware.zip in your fastboot folder.
http://www.htc1guru.com/dld/ota_m7_...-19-631-9_release_372926h4tumwerl14wrs0u-zip/
Reboot the phone to the bootloader and Connect fastbootusb. Now open your Fastboot command line and type
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Code:
fastboot oem rebootRUU
< --- case sensitive. ---^^^
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip firmware.zip
The second flash will take a little longer and this time it 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 completed its output the flash is done.
Code:
fastboot reboot-bootloader
Now you will need to unlock the bootloader again with your Unlock_code.bin
Flash TWRP and Flash your Rom again before the phone will boot. Then reboot the phone. :fingers-crossed:
If that doesn't do it Warranty is a possibility but you will need s-off to remove the signs the phone was tampered with.
---------- Post added at 10:01 AM ---------- Previous post was at 09:59 AM ----------
Yeah unfortunately Unlocking the Bootloader Wipes the device.

Danny201281 said:
I couldn't find a firmware package but I did find this OTA. It contains the firmware we need. Download it and open the zip on your pc. Extract the firmware.zip and put the firmware.zip in your fastboot folder.
http://www.htc1guru.com/dld/ota_m7_...-19-631-9_release_372926h4tumwerl14wrs0u-zip/
Reboot the phone to the bootloader and Connect fastbootusb. Now open your Fastboot command line and type
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Code:
fastboot oem rebootRUU
< --- case sensitive. ---^^^
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip firmware.zip
The second flash will take a little longer and this time it 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 completed its output the flash is done.
Code:
fastboot reboot-bootloader
Now you will need to unlock the bootloader again with your Unlock_code.bin
Flash TWRP and Flash your Rom again before the phone will boot. Then reboot the phone. :fingers-crossed:
If that doesn't do it Warranty is a possibility but you will need s-off to remove the signs the phone was tampered with.
---------- Post added at 10:01 AM ---------- Previous post was at 09:59 AM ----------
Yeah unfortunately Unlocking the Bootloader Wipes the device.
Click to expand...
Click to collapse
so, it failed and shows this:
Mustafas-MacBook-Airlatform-tools mustafafarhanarifin$ ./fastboot flash zip OTA_M7_UL_K44_SENSE60_MR_Rogers_WWE_5.11.631.8_R-4.19.631.9_release_372926h4tumwerl14wrs0u.zip
target reported max download size of 1514139648 bytes
sending 'zip' (720552 KB)...
OKAY [ 28.648s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 111.120s

RoyalChalksHere said:
so, it failed and shows this:
Mustafas-MacBook-Airlatform-tools mustafafarhanarifin$ ./fastboot flash zip OTA_M7_UL_K44_SENSE60_MR_Rogers_WWE_5.11.631.8_R-4.19.631.9_release_372926h4tumwerl14wrs0u.zip
target reported max download size of 1514139648 bytes
sending 'zip' (720552 KB)...
OKAY [ 28.648s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 111.120s
Click to expand...
Click to collapse
You flashed the wrong zip. The firmware zip is inside the OTA
Open the OTA_M7_UL_K44_SENSE60_MR_Rogers_WWE_5.11.631.8_R-4.19.631.9_release_372926h4tumwerl14wrs0u.zip On your pc inside it is a firmware.zip extract the firmware.zip and flash it with the previous procedure

Danny201281 said:
I couldn't find a firmware package but I did find this OTA. It contains the firmware we need. Download it and open the zip on your pc. Extract the firmware.zip and put the firmware.zip in your fastboot folder.
http://www.htc1guru.com/dld/ota_m7_...-19-631-9_release_372926h4tumwerl14wrs0u-zip/
Reboot the phone to the bootloader and Connect fastbootusb. Now open your Fastboot command line and type
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Code:
fastboot oem rebootRUU
< --- case sensitive. ---^^^
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip firmware.zip
The second flash will take a little longer and this time it 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 completed its output the flash is done.
Code:
fastboot reboot-bootloader
Now you will need to unlock the bootloader again with your Unlock_code.bin
Flash TWRP and Flash your Rom again before the phone will boot. Then reboot the phone. :fingers-crossed:
If that doesn't do it Warranty is a possibility but you will need s-off to remove the signs the phone was tampered with.
---------- Post added at 10:01 AM ---------- Previous post was at 09:59 AM ----------
Yeah unfortunately Unlocking the Bootloader Wipes the device.
Click to expand...
Click to collapse
Danny201281 said:
You flashed the wrong zip. The firmware zip is inside the OTA
Open the OTA_M7_UL_K44_SENSE60_MR_Rogers_WWE_5.11.631.8_R-4.19.631.9_release_372926h4tumwerl14wrs0u.zip On your pc inside it is a firmware.zip extract the firmware.zip and flash it with the previous procedure
Click to expand...
Click to collapse
youre amazing man. looks fine so far. baseband and IMEI is registered. im currently on android lollipop, and couldnt find any suitable gapps file. do you happen to know?

ok, so I shut down the phone to get back into fastboot mode with the button combo, but now it is not even turning on. black screen, not even charging. wtf.

Danny201281 said:
When you say you wiped it in twrp, did you Factory Reset or did you Format Data?
If you used Format Data then you wiped your entire device including the installed Rom. You should be able to force the device to power of by holding the power button for 60secs.
Then power on while holding volume down to get to the bootloader. Then you can boot to recovery and push a Rom with adb. :good:
Click to expand...
Click to collapse
i think i did both
i will try that after i get some charge on it
battery died last night
---------- Post added at 12:49 PM ---------- Previous post was at 12:23 PM ----------
@CallMe_Y_C said:
i think i did both
i will try that after i get some charge on it
battery died last night
Click to expand...
Click to collapse
can i get a suggested rom or supm to follow?
steps
thanks

RoyalChalksHere said:
youre amazing man. looks fine so far. baseband and IMEI is registered. im currently on android lollipop, and couldnt find any suitable gapps file. do you happen to know?
Click to expand...
Click to collapse
RoyalChalksHere said:
ok, so I shut down the phone to get back into fastboot mode with the button combo, but now it is not even turning on. black screen, not even charging. wtf.
Click to expand...
Click to collapse
Sorry man I had to get some sleep, So it was looking good for while then
What happened exactly? You flashed the firmware and Rom and all was ok. Then you just power off to go to bootloader and it never came back on? Did you flash anything in between that or that was it? You say you had a lollipop Rom can you provide a link to it please?
Is the device detected when you connect it to your pc? Does it show on device manager, maybe as Unknown device or QHSUSB_DLOAD?
---------- Post added at 04:09 PM ---------- Previous post was at 03:59 PM ----------
@CallMe_Y_C said:
i think i did both
i will try that after i get some charge on it
battery died last night
---------- Post added at 12:49 PM ---------- Previous post was at 12:23 PM ----------
can i get a suggested rom or supm to follow?
steps
thanks
Click to expand...
Click to collapse
I'd be happy to make a suggestion but can you post your getvar all? Not all roms are compatible with all devices.
It's kind of important to know what I'm recommending a Rom for

I have bricked my phone and i need help

I did a factory reset it didn't help. My phone was rooted, I did everything to the point where it was rooted, and it was woorking fine. After that I installed xposed framework, and that`s when it happened right after when I restarted the phone. The phones screen goes black after HTC logo shows. I also have the usb debug off at this point.

Keomas said:
I did a factory reset it didn't help. My phone was rooted, I did everything to the point where it was rooted, and it was woorking fine. After that I installed xposed framework, and that`s when it happened right after when I restarted the phone. The phones screen goes black after HTC logo shows. I also have the usb debug off at this point.
Click to expand...
Click to collapse
...Look for:< ` xposed disabler` zip file >,and flash it via recovery,
or...try to reboot one more time,
or...restore yor latest backup
or...reflash the rom (dirty flash perhaps- the softer way)
try to be creative, thys is not the end of the world

asgardr said:
...Look for:< ` xposed disabler` zip file >,and flash it via recovery,
or...try to reboot one more time,
or...restore yor latest backup
or...reflash the rom (dirty flash perhaps- the softer way)
try to be creative, thys is not the end of the world
Click to expand...
Click to collapse
None of this works, i have no backup files.

Keomas said:
None of this works, i have no backup files.
Click to expand...
Click to collapse
then -depending on your device`s firmware version,
find a RUU-if you feel you`re in a big trouble,
or someone`s nandroid backup,stock rom reset,
usb debbuging on, is essential in the process of recovering from a bootloop,
but if you `ll find a way to navigate between bootloader and recovery,
then with that in hand, one could already achieve wonders...
...still in the first place should you not sheed some light on your device:
software version, (stock or custom)
kind and release of device`s recovery (stock or custom)
bootloader version
and the like?

asgardr said:
then -depending on your device`s firmware version,
find a RUU-if you feel you`re in a big trouble,
or someone`s nandroid backup,stock rom reset,
usb debbuging on, is essential in the process of recovering from a bootloop,
but if you `ll find a way to navigate between bootloader and recovery,
then with that in hand, one could already achieve wonders...
...still in the first place should you not sheed some light on your device:
software version, (stock or custom)
kind and release of device`s recovery (stock or custom)
bootloader version
and the like?
Click to expand...
Click to collapse
The device was locked to a Swedish carrier which I unlocked it, it had lolipop 5.0.2.
M7_UL PVT SHIP S-ON RH
HBOOT-161.0000
RADIO-4T.35.3218.16
OpenDSP-V35.120.274.0718
OS-7.19.771.21
eMMC-BOOT 2048MB
CID H3G_G04
Is there a chance to turn the usb debug on when the phone is at this state?
How do i push files to the phone, "adb device" can't find any devices because usb debug is off?

Keomas said:
The device was locked to a Swedish carrier which I unlocked it, it had lolipop 5.0.2.
M7_UL PVT SHIP S-ON RH
HBOOT-161.0000
RADIO-4T.35.3218.16
OpenDSP-V35.120.274.0718
OS-7.19.771.21
eMMC-BOOT 2048MB
Is there a chance to turn the usb debug on when the phone is at this state?
How do i push files to the phone, "adb device" can't find any devices because usb debug is off?
Click to expand...
Click to collapse
You don't need usb debug, its a widespread misconception. USB debug is only needed if you want to use adb commands when the phone is booted in the OS. fastboot commands will still work fine when booted in bootloader mode, and adb commands will still work fine when booted in a custom recovery even is usb debug is off.
relock your bootloader and flash the 7.19.771.21 ruu that i have posted ealier this week in this thread. See post #2 for the file and post #1 for instructions how to flash.

alray said:
You don't need usb debug, its a widespread misconception. USB debug is only needed if you want to use adb commands when the phone is booted in the OS. fastboot commands will still work fine when booted in bootloader mode, and adb commands will still work fine when booted in a custom recovery even is usb debug is off.
relock your bootloader and flash the 7.19.771.21 ruu that i have posted ealier this week in this thread. See post #2 for the file and post #1 for instructions how to flash.
Click to expand...
Click to collapse
How do I lock my bootloader when the phone is in this state, I don't want to give my self further problems?
Edit: I asked the above question and then locked the bootloader with Hasoon2000*s all in one toolkit, allthoug it was saying you need usb degub on. But now it says bootloader relocked.

alray said:
You don't need usb debug, its a widespread misconception. USB debug is only needed if you want to use adb commands when the phone is booted in the OS. fastboot commands will still work fine when booted in bootloader mode, and adb commands will still work fine when booted in a custom recovery even is usb debug is off.
relock your bootloader and flash the 7.19.771.21 ruu that i have posted ealier this week in this thread. See post #2 for the file and post #1 for instructions how to flash.
Click to expand...
Click to collapse
The link to the htc fastbot.exe in the instructions doesn't work.

alray said:
You don't need usb debug, its a widespread misconception. USB debug is only needed if you want to use adb commands when the phone is booted in the OS. fastboot commands will still work fine when booted in bootloader mode, and adb commands will still work fine when booted in a custom recovery even is usb debug is off.
relock your bootloader and flash the 7.19.771.21 ruu that i have posted ealier this week in this thread. See post #2 for the file and post #1 for instructions how to flash.
Click to expand...
Click to collapse
I get this errors when I use winrar to unpack the RUU file: C:\Users\xxxx\Downloads\PN07IMG.zip: The archive is corrupt
C:\Users\xxxx\Downloads\PN07IMG.zip: Checksum error in C:\Users\Kemal\Downloads\PN07IMG\dzdata_32g.img. The file is corrupt
C:\Users\xxxx\Downloads\PN07IMG.zip: Checksum error in C:\Users\Kemal\Downloads\PN07IMG\dzdata_64g.img. The file is corrupt

Keomas said:
I get this errors when I use winrar to unpack the RUU file: C:\Users\xxxx\Downloads\PN07IMG.zip: The archive is corrupt
C:\Users\xxxx\Downloads\PN07IMG.zip: Checksum error in C:\Users\Kemal\Downloads\PN07IMG\dzdata_32g.img. The file is corrupt
C:\Users\xxxx\Downloads\PN07IMG.zip: Checksum error in C:\Users\Kemal\Downloads\PN07IMG\dzdata_64g.img. The file is corrupt
Click to expand...
Click to collapse
I said instructions how to flash at post #1, so go ahead and read what said a post #1 of the linked thread above.
Let's start with the warning:
This is a collection of lollipop ruu.zip files for our beloved htc one m7 801.
I cannot test all of these files so any feedback will be welcome.
Also I have no responsibility if you phone explodes after flashing any of these files, I am just the uploader.
As many in this thread, ask about zip corruption, zip are not corrupted they are encrypted and can't open normally , they need decryption check md5 and dont try to unzip them.
When you update you must go one step at a time. For example if you are on 6.xx.xxx.xx then you can flash 7.xx.xxx.xx . But if you are on 5.xx.xxx.xx then you cannot flash the 7.xx.xxx.xx you must first flash a 6..xx.xxx.xx.
Click to expand...
Click to collapse
Then the instructions how to flash:
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
Click to expand...
Click to collapse
---------- Post added at 06:22 PM ---------- Previous post was at 06:20 PM ----------
Keomas said:
The link to the htc fastbot.exe in the instructions doesn't work.
Click to expand...
Click to collapse
take this one form my dropbox https://dl.dropboxusercontent.com/u/77459918/htc_fastboot.exe
---------- Post added at 06:24 PM ---------- Previous post was at 06:22 PM ----------
Keomas said:
locked the bootloader with Hasoon2000*s all in one toolkit, allthoug it was saying you need usb degub on. But now it says bootloader relocked.
Click to expand...
Click to collapse
Here is another example of this misconception, usb debug is only needed when booted in the OS.

alray said:
I said instructions how to flash at post #1, so go ahead and read what said a post #1 of the linked thread above.
Let's start with the warning:
Then the instructions how to flash:
---------- Post added at 06:22 PM ---------- Previous post was at 06:20 PM ----------
take this one form my dropbox https://dl.dropboxusercontent.com/u/77459918/htc_fastboot.exe
---------- Post added at 06:24 PM ---------- Previous post was at 06:22 PM ----------
Here is another example of this misconception, usb debug is only needed when booted in the OS.
Click to expand...
Click to collapse
Thank you very much for helping me.
In the adb folder i got the normal fasboot.exe, should i remove that one when renaming the htc fastboot.exe to fastboot, or when not renaming it should i remove the normal one anyway?

Keomas said:
Thank you very much for helping me.
In the adb folder i got the normal fasboot.exe, should i remove that one when renaming the htc fastboot.exe to fastboot, or when not renaming it should i remove the normal one anyway?
Click to expand...
Click to collapse
You can keep the normal fastboot.exe in the folder and place htc_fastboot.exe in the same folder without renaming it. Just make sure to start your commands with htc_fastboot
Code:
htc_fastboot <option> <command> [ <filename> ]
so in this case do:
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip
htc_fastboot reboot
instead of
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot reboot

alray said:
You can keep the normal fastboot.exe in the folder and place htc_fastboot.exe in the same folder without renaming it. Just make sure to start your commands with htc_fastboot
Code:
htc_fastboot <option> <command> [ <filename> ]
so in this case do:
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip
htc_fastboot reboot
instead of
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot reboot
Click to expand...
Click to collapse
When i run the second command, htc_fastboot flash zip RUU.zip, i get this errors:
FAIL42 custom id check fail
FAILED (remote: 42 custom id check fail)

Keomas said:
When i run the second command, htc_fastboot flash zip RUU.zip, i get this errors:
FAIL42 custom id check fail
FAILED (remote: 42 custom id check fail)
Click to expand...
Click to collapse
post the output of "fastboot getvar all" remove imei before posting

alray said:
post the output of "fastboot getvar all" remove imei before posting
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 1.61.0000
version-baseband: 4T.35.3218.16
version-cpld: None
version-microp: None
version-main: 7.19.771.21
version-misc: PVT SHIP S-ON
serialno: HT354W901116
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: H3G__G04
battery-status: good
battery-voltage: 4313mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0e2a13e5
hbootpreupdate: 11
gencheckpt: 0
al time: 0.044s
stboot getvar all
version: 0.5

Keomas said:
version: 0.5
version-bootloader: 1.61.0000
version-baseband: 4T.35.3218.16
version-cpld: None
version-microp: None
version-main: 7.19.771.21
version-misc: PVT SHIP S-ON
serialno: HT354W901116
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: H3G__G04
battery-status: good
battery-voltage: 4313mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0e2a13e5
hbootpreupdate: 11
gencheckpt: 0
al time: 0.044s
stboot getvar all
version: 0.5
Click to expand...
Click to collapse
are you sure your have downloaded the right RUU 7.19.771.21?
---------- Post added at 07:06 PM ---------- Previous post was at 06:59 PM ----------
gtg working, will try to log on from work in maybe an hour otherwise ill be back later.

alray said:
are you sure your have downloaded the right RUU 7.19.771.21?
Click to expand...
Click to collapse
It was the wrong version, but now i used the right version. It zipped ,flashed and copied everything, flash zip was complete. But now there is a problem, the green bar that showed up in the phone stopped before it was full. Also when i execute the last command, htc_fastboot reboot-bootloader, thi9s shows up:C:\Android>8htc_fastboot reboot-bootloader
'8htc_fastboot' is not recognized as an internal or external command,
operable program or batch file.
Edit: repeated everything and now it worked Thank you very much. "Android is upgrading..." I will skip rooting it for now.

Stuck on Bootloader and can't access recovery.

Hi
I'm running XENON HD and tried to do an OTA upgrade. When I came back to my phone, it was in the bootloader screen. After every reboot, it goes there.
This wouldn't normally be a problem except that my volume keys are damaged and I can't select any option from the bootloader screen.
I tried a #fastboot boot twrp.img but it doesn't reboot the phone.
Is there any way I can access recovery another way? I did a backup (on the sd card ) so I really just need to get into recovery.
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.61.0000
Any help/ideas is appreciated.
Thanks!

Perf_engineer said:
Hi
I'm running XENON HD and tried to do an OTA upgrade. When I came back to my phone, it was in the bootloader screen. After every reboot, it goes there.
This wouldn't normally be a problem except that my volume keys are damaged and I can't select any option from the bootloader screen.
I tried a #fastboot boot twrp.img but it doesn't reboot the phone.
Is there any way I can access recovery another way? I did a backup (on the sd card ) so I really just need to get into recovery.
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.61.0000
Any help/ideas is appreciated.
Thanks!
Click to expand...
Click to collapse
fastboot boot twrp.img was only working on hboot 1.44 back in 2013, this command was disabled with 1.54 and all newer hboot.
There is no command to make your phone reboot in recovery from the bootloader so i'm afraid you will not be able to go back in recovery. If at least your phone is in bootloader mode with "fastboot usb" in red you can relock your BL and restore using a RUU. Once the ruu is flashed the phone will reboot to the OS by itself.

alray said:
fastboot boot twrp.img was only working on hboot 1.44 back in 2013, this command was disabled with 1.54 and all newer hboot.
There is no command to make your phone reboot in recovery from the bootloader so i'm afraid you will not be able to go back in recovery. If at least your phone is in bootloader mode with "fastboot usb" in red you can relock your BL and restore using a RUU. Once the ruu is flashed the phone will reboot to the OS by itself.
Click to expand...
Click to collapse
Crap.. At least it isn't dead. Thanks for your help

alray said:
fastboot boot twrp.img was only working on hboot 1.44 back in 2013, this command was disabled with 1.54 and all newer hboot.
There is no command to make your phone reboot in recovery from the bootloader so i'm afraid you will not be able to go back in recovery. If at least your phone is in bootloader mode with "fastboot usb" in red you can relock your BL and restore using a RUU. Once the ruu is flashed the phone will reboot to the OS by itself.
Click to expand...
Click to collapse
Hi alray.
I downloaded what i thought was the right RUU but I am getting an error message saying it can't verify the signature.
How can I tell which RUU I should use? I don't care what goes on it as I will be unlocking the bootloader again and putting back on a custom rom.
Thanks
./fastboot flash zip RUU.zip
sending 'zip' (1463809 KB)... OKAY
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)

Perf_engineer said:
Hi alray.
I downloaded what i thought was the right RUU but I am getting an error message saying it can't verify the signature.
How can I tell which RUU I should use? I don't care what goes on it as I will be unlocking the bootloader again and putting back on a custom rom.
Thanks
./fastboot flash zip RUU.zip
sending 'zip' (1463809 KB)... OKAY
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
Click to expand...
Click to collapse
Nevermind. I found the CID and MID of my phone. Downloading now. hopefully it will work

Perf_engineer said:
Nevermind. I found the CID and MID of my phone. Downloading now. hopefully it will work
Click to expand...
Click to collapse
Nope
Any thoughts?
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3AHW902491
(bootloader) imei: 359405051005401
(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: 4204mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
No version main.
I can't find an exe for my model. Apparently zip files won't work when you are missing the verison

Fastboot reboot
Fastboot flash recovery
Fastboot reboot
Fastboot reboot recovery
If you have a kik. Feel free to contact me under the same name for quick assistance

Tony the noob :D said:
Fastboot reboot
Fastboot flash recovery
Fastboot reboot
Fastboot reboot recovery
If you have a kik. Feel free to contact me under the same name for quick assistance
Click to expand...
Click to collapse
Thanks for the offer. Don't have kik unfortunately.
Current state I'm in is that I have relocked my phone, but the version_main is blank.
flashing from zip doesn't work in RUU.
I tried to flash the recovery again but keep getting the signature failed message

Perf_engineer said:
Thanks for the offer. Don't have kik unfortunately.
Current state I'm in is that I have relocked my phone, but the version_main is blank.
flashing from zip doesn't work in RUU.
I tried to flash the recovery again but keep getting the signature failed message
Click to expand...
Click to collapse
Your trying to do a HTC OTA Update?

pardon me for stealing the thread. In a related issue.
https://forum.xda-developers.com/htc-one-tmobile/development/recent-zip-ruu-t-mo-t3662241
which RUU or rom to install?

Perf_engineer said:
I can't find an exe for my model. Apparently zip files won't work when you are missing the verison
Click to expand...
Click to collapse
Yes zip version will work even if your version-main is blank, since you don't know your version-main, use the latest ruu for your cid/mid. If the latest version ruu isn't available in the ruu collection thread, you'll probably have to download it from easy-firmware.com or a similar website.
---------- Post added at 06:48 AM ---------- Previous post was at 06:46 AM ----------
Perf_engineer said:
Thanks for the offer. Don't have kik unfortunately.
Current state I'm in is that I have relocked my phone, but the version_main is blank.
flashing from zip doesn't work in RUU.
I tried to flash the recovery again but keep getting the signature failed message
Click to expand...
Click to collapse
you can't flash the recovery partition when the BL is locked. The BL must be locked to flash the ruu.

Tony the noob :D said:
Your trying to do a HTC OTA Update?
Click to expand...
Click to collapse
Is that possible? I can't load any rom at the moment.

Tony the noob :D said:
Fastboot reboot
Fastboot flash recovery
Fastboot reboot
Fastboot reboot recovery
If you have a kik. Feel free to contact me under the same name for quick assistance
Click to expand...
Click to collapse
I thought you can't fastboot into recovery?
At least I never could. If I can I could have solved this ages ago

alray said:
Yes zip version will work even if your version-main is blank, since you don't know your version-main, use the latest ruu for your cid/mid. If the latest version ruu isn't available in the ruu collection thread, you'll probably have to download it from easy-firmware.com or a similar website.
---------- Post added at 06:48 AM ---------- Previous post was at 06:46 AM ----------
you can't flash the recovery partition when the BL is locked. The BL must be locked to flash the ruu.
Click to expand...
Click to collapse
crap crap crap.
I just tried to unlock the bootloader again. Remember when I said the volume keys were damaged? I should have been more specific.. The phone fell and damaged the volume up key and it is pressed in. This doesn't allow me to use the power button to select. So I can't unlock the bootloader now :\ (unless I can give it a default acceptance?)
So I think my only options are to put on the stock and leave it as is
Or open the phone up so the case isn't pressing on the volume key.
This was the RUU I tried. It seems to be the latest and the right version.
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
can anyone confirm?
Thanks

Perf_engineer said:
I thought you can't fastboot into recovery?
At least I never could. If I can I could have solved this ages ago
Click to expand...
Click to collapse
no you can't
---------- Post added at 03:01 PM ---------- Previous post was at 03:00 PM ----------
Perf_engineer said:
crap crap crap.
I just tried to unlock the bootloader again. Remember when I said the volume keys were damaged? I should have been more specific.. The phone fell and damaged the volume up key and it is pressed in. This doesn't allow me to use the power button to select. So I can't unlock the bootloader now :\ (unless I can give it a default acceptance?)
So I think my only options are to put on the stock and leave it as is
Or open the phone up so the case isn't pressing on the volume key.
This was the RUU I tried. It seems to be the latest and the right version.
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
can anyone confirm?
Thanks
Click to expand...
Click to collapse
use the 7.18.206.51 ruu, it's the latest one for o2

alray said:
no you can't
---------- Post added at 03:01 PM ---------- Previous post was at 03:00 PM ----------
use the 7.18.206.51 ruu, it's the latest one for o2
Click to expand...
Click to collapse
FAILED (remote: 02 data length is too large)

Update:
The data too large message was when I used the latest HTC fastboot Linux version.
I switched to Windows and it worked. Back at stock.
Thanks to everyone for their help, especially alray

Ok...so I'm never happy.. Anyway to unlock the bootloader again without the power button?

Perf_engineer said:
Ok...so I'm never happy.. Anyway to unlock the bootloader again without the power button?
Click to expand...
Click to collapse
sunshine

alray said:
sunshine
Click to expand...
Click to collapse
Thanks for the tip but it didn't work.
It was unable to get temporary root access.
I tried iRoot and towelroot but they also failed.
Guess I'm stuck