Database Develop

HTC One stuck at HTC quietly brilliant

To start off, I have had my htc one for about 4 months and around December my battery died and I charged it back up. I was then shown the boot loader screen which I never had seen before. Ever since then when I restart my phone it randomly goes to that screen sometimes so I just then did fast boot and booted into the android os. Yesterday my phone froze so I attempted to restart it and then I was stuck with the htc quietly brilliant screen. I have let the battery die like that and charged it back up but nothing happens. I tried to factory reset it in the boot loader but that does not work either. The boot loader currently shows this:
Tampered
Locked
S-ON
Keep in mind I have never tried to install custom roms or anything else I have left it purely at stock. I also got it straight from a T-mobile store. Help is appreciated.
-Thanks!

maxt95 said:
To start off, I have had my htc one for about 4 months and around December my battery died and I charged it back up. I was then shown the boot loader screen which I never had seen before. Ever since then when I restart my phone it randomly goes to that screen sometimes so I just then did fast boot and booted into the android os. Yesterday my phone froze so I attempted to restart it and then I was stuck with the htc quietly brilliant screen. I have let the battery die like that and charged it back up but nothing happens. I tried to factory reset it in the boot loader but that does not work either. The boot loader currently shows this:
Tampered
Locked
S-ON
Keep in mind I have never tried to install custom roms or anything else I have left it purely at stock. I also got it straight from a T-mobile store. Help is appreciated.
-Thanks!
Click to expand...
Click to collapse
So if you got it straight from T-mo and never flashed stuff, why is the bootloader tampered?
post your ''fastboot getvar all'' minus imei/sn

alray said:
So if you got it straight from T-mo and never flashed stuff, why is the bootloader tampered?
post your ''fastboot getvar all'' minus imei/sn
Click to expand...
Click to collapse
I'm not sure why. Heres the info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxx
(bootloader) imei: xxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3828mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

maxt95 said:
I'm not sure why. Heres the info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxx
(bootloader) imei: xxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3828mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
ok, the bootloader tampered flag mean someone already unlocked it. If you are 100% sure you did not attempted to mod anything, this mean your phone wasn't new when you bought it and you should consider returning it back to store. The main problem is that they will probably deny the warranty because of this tampered flag. They will probably assume that you have tampered the phone.
You can also try to reset back to 100% stock with an ruu.exe. Be sure to use a windows 8.0, 7 or xp computer. not a windows 8.1. Connect the phone to your computer and boot it to bootloader mode then, lauch the ruu.exe.
This is the ruu you need
edit: note that it will completely wipe your data.
edit2: note that the ruu will not remove the tampered flag unless you want to go trough many other steps.

alray said:
ok, the bootloader tampered flag mean someone already unlocked it. If you are 100% sure you did not attempted to mod anything, this mean your phone wasn't new when you bought it and you should consider returning it back to store. The main problem is that they will probably deny the warranty because of this tampered flag. They will probably assume that you have tampered the phone.
You can also try to reset back to 100% stock with an ruu.exe. Be sure to use a windows 8.0, 7 or xp computer. not a windows 8.1. Connect the phone to your computer and boot it to bootloader mode then, lauch the ruu.exe.
edit: note that it will completely wipe your data.
edit2: note that the ruu will not remove the tampered flag unless you want to go trough many other steps.
Click to expand...
Click to collapse
Ok I'll do that and see what happens. Thanks for the help!

@maxt95
If your phone still have issue after the ruu (freeze/reboot) then we can assist you to s-off, remove tempered flag etc etc... make the device looks like if it had never been tampered with and you'll be able to send it under warranty
if you screwed this yourself don't be shy to admit it. Much easier to assist when we know all the details.

alray said:
@maxt95
If your phone still have issue after the ruu (freeze/reboot) then we can assist you to s-off, remove tempered flag etc etc... make the device looks like if it had never been tampered with and you'll be able to send it under warranty
if you screwed this yourself don't be shy to admit it. Much easier to assist when we know all the details.
Click to expand...
Click to collapse
I finally got it to work. I had to try multiple computers to do it though haha. Anyways thanks for helping out!

I need your help!
maxt95 said:
I finally got it to work. I had to try multiple computers to do it though haha. Anyways thanks for helping out!
Click to expand...
Click to collapse
Hey it seems like you got your phone workin. I am having the same issue, I understand we need to reset the rom or something. Will you be able to tell me the steps required? Thanks bro

kingk3n said:
Hey it seems like you got your phone workin. I am having the same issue, I understand we need to reset the rom or something. Will you be able to tell me the steps required? Thanks bro
Click to expand...
Click to collapse
please post the output of ''fastboot getvar all'' minus IMEI/SN and explain a little more your situation.

im using htc one
alray said:
please post the output of ''fastboot getvar all'' minus IMEI/SN and explain a little more your situation.
Click to expand...
Click to collapse
Hi thanks for your response. I am using HTC one and, I'm not sure how to execute the fastboot getvar all command. I know how to get to the bootloader w/c is holding the power button down and, holding volume down at the same time

kingk3n said:
Hi thanks for your response. I am using HTC one and, I'm not sure how to execute the fastboot getvar all command. I know how to get to the bootloader w/c is holding the power button down and, holding volume down at the same time
Click to expand...
Click to collapse
You will need to have fastboot/adb tools installed on your computer ----> HERE
and you'll need latest HTC drivers installed. This can be done by installing HTC sync software you can find HERE
then reboot in bootloader mode, select fastboot, open minimal adb and fastboot and enter the cmd.
btw you still didn't described your issue ...

alray said:
You will need to have fastboot/adb tools installed on your computer ----> HERE
and you'll need latest HTC drivers installed. This can be done by installing HTC sync software you can find HERE
then reboot in bootloader mode, select fastboot, open minimal adb and fastboot and enter the cmd.
btw you still didn't described your issue ...
Click to expand...
Click to collapse
My issue is that my phone is stuck at the "HTC Quiently Brilliant" screen. I tried reboot, recovery and reset factory settings, I still get stuck at the htc screen.. Let me try what you've suggested.
And, by the way my bootloader says ****LOCKED*** (Pink Font) on top of the menu.. Not sure if that helps...

kingk3n said:
My issue is that my phone is stuck at the "HTC Quiently Brilliant" screen. I tried reboot, recovery and reset factory settings, I still get stuck at the htc screen.. Let me try what you've suggested.
And, by the way my bootloader says ****LOCKED*** (Pink Font) on top of the menu.. Not sure if that helps...
Click to expand...
Click to collapse
ok waiting for your ''fastboot getvar all'' can you also post a picture of your bootloader screen or write down all info?

alray said:
ok waiting for your ''fastboot getvar all'' can you also post a picture of your bootloader screen or write down all info?
Click to expand...
Click to collapse
Here it is brother... Please see below & attached screen shot of my bootloader
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.666.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4112mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s

kingk3n said:
Here it is brother... Please see below & attached screen shot of my bootloader
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.666.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4112mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
Click to expand...
Click to collapse
So it looks like your phone is completely stock and you never tampered it. Since you already did a factory reset, there is not much you can do... you should try to erase cache and see if the phone can boot properly:
reboot phone in bootloader/fastboot mode and type this command:
Code:
fastboot erase cache
fastboot reboot
if your phone still don't boot you should consider go back to a bell mobility store and ask for a repair/replacement if your phone is still under warranty. If not under waranty you can try the guide linked in my signature below (return stock for canadian user by SaHiLzZ). The guide require to flash a custom recovery which need an unlocked bootloader. Unlocking the bootloader will wipe the phone and may void your warranty.

alray said:
So it looks like your phone is completely stock and you never tampered it. Since you already did a factory reset, there is not much you can do... you should try to erase cache and see if the phone can boot properly:
reboot phone in bootloader/fastboot mode and type this command:
Code:
fastboot erase cache
fastboot reboot
if your phone still don't boot you should consider go back to a bell mobility store and ask for a repair/replacement if your phone is still under warranty. If not under waranty you can try the guide linked in my signature below (return stock for canadian user by SaHiLzZ). The guide require to flash a custom recovery which need an unlocked bootloader. Unlocking the bootloader will wipe the phone and may void your warranty.
Click to expand...
Click to collapse
No Luck !!!! Thanks for helping me though. I will call HTC and ask them to fix it for me.
Damnnn HTC !!!!

alray said:
So it looks like your phone is completely stock and you never tampered it. Since you already did a factory reset, there is not much you can do... you should try to erase cache and see if the phone can boot properly:
reboot phone in bootloader/fastboot mode and type this command:
Code:
fastboot erase cache
fastboot reboot
if your phone still don't boot you should consider go back to a bell mobility store and ask for a repair/replacement if your phone is still under warranty. If not under waranty you can try the guide linked in my signature below (return stock for canadian user by SaHiLzZ). The guide require to flash a custom recovery which need an unlocked bootloader. Unlocking the bootloader will wipe the phone and may void your warranty.
Click to expand...
Click to collapse
Hey, is there a way for me to recover all my pictures while its on the bootloader? I need to get those pictures copied. Please advise.
Thanks

[Q] HTC One From Amazon Warehouse - Received unlocked and a bit messed up - Pls help

Hello everyone,
Firstly, I’d just like to say that I’m a bit of a noob. However, I’ve spent hours and hours reading through the forum, googling, reading guides, and generally trying to inform myself before writing this. So hopefully I won’t annoy people with my questions
My phone is a factory unlocked HTC One from Amazon Warehouse Germany (ie. second hand, but direct from Amazon themselves). The phone looks great and seemed to work fine, but after deciding that I’d like to go rooted, I had my first encounter with the bootloader. This is where I realised that something wasn’t right….
If I access the bootloader (Power+Vol-), it will always perform a factory reset when I exit. It doesn’t matter whether I try to exit using the Reboot or the Power Down options from the fastboot menu. As soon as I power the phone back on, it will always boot up like it’s a brand new phone that needs setting up from scratch. This is a real pain, because I have to complete that basic phone setup every time - just to know whether or not it happens next time.
At one point I noticed that the botloader already has the **Unlocked** message in the top left corner, so I then followed the relevant guides to clear the cache and flash a custom recovery… When I do this (using fastboot flash recovery command) I always get the message that the recovery was sent and flashed OK. But if I try to access the custom recovery, I just come to a screen with a red exclamation mark inside a triangle. The phone will then eventually reboot its self (in a factory reset state again). From what info I can find, the triangle with the red exclamation mark means that the recovery isn’t actually there.
As a last resort I thought I’d try to fix the phone with an RUU, but for that I need a relocked bootloader. So I tried to do this with the “fastboot oem lock” command and got the following message:
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.165s
Afted the above message shows, the phone restarts its self automatically and boots up in a factory reset state again. The bootloader also remains unlocked.
I’ve attached a screenshot of my bootloader and here are some details of the phone that I got by using “fastboot getvar all” (I removed the IMEI):
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: **************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4295mV
(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.047s
After Googling some of the info from the bootloader screen, I noticed that one of the top results is a htc1guru.com guide to resetting your phone back to stock. For that reason I’m thinking that the previous owner might have messed around with the phone, flashed a few custom roms, and then tried to restore the device back to stock before sending it to Amazon for a refund.
I know that I could complain and send the phone back to amazon myself, but the phone is in such immaculate condition (for a used device) that I’d really like to keep it if possible.
Can anyone help me? please?
Thank you,
Craig.

craighumphries said:
Hello everyone,
Firstly, I’d just like to say that I’m a bit of a noob. However, I’ve spent hours and hours reading through the forum, googling, reading guides, and generally trying to inform myself before writing this. So hopefully I won’t annoy people with my questions
My phone is a factory unlocked HTC One from Amazon Warehouse Germany (ie. second hand, but direct from Amazon themselves). The phone looks great and seemed to work fine, but after deciding that I’d like to go rooted, I had my first encounter with the bootloader. This is where I realised that something wasn’t right….
If I access the bootloader (Power+Vol-), it will always perform a factory reset when I exit. It doesn’t matter whether I try to exit using the Reboot or the Power Down options from the fastboot menu. As soon as I power the phone back on, it will always boot up like it’s a brand new phone that needs setting up from scratch. This is a real pain, because I have to complete that basic phone setup every time - just to know whether or not it happens next time.
At one point I noticed that the botloader already has the **Unlocked** message in the top left corner, so I then followed the relevant guides to clear the cache and flash a custom recovery… When I do this (using fastboot flash recovery command) I always get the message that the recovery was sent and flashed OK. But if I try to access the custom recovery, I just come to a screen with a red exclamation mark inside a triangle. The phone will then eventually reboot its self (in a factory reset state again). From what info I can find, the triangle with the red exclamation mark means that the recovery isn’t actually there.
As a last resort I thought I’d try to fix the phone with an RUU, but for that I need a relocked bootloader. So I tried to do this with the “fastboot oem lock” command and got the following message:
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.165s
Afted the above message shows, the phone restarts its self automatically and boots up in a factory reset state again. The bootloader also remains unlocked.
I’ve attached a screenshot of my bootloader and here are some details of the phone that I got by using “fastboot getvar all” (I removed the IMEI):
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA399W906494
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4295mV
(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.047s
After Googling some of the info from the bootloader screen, I noticed that one of the top results is a htc1guru.com guide to resetting your phone back to stock. For that reason I’m thinking that the previous owner might have messed around with the phone, flashed a few custom roms, and then tried to restore the device back to stock before sending it to Amazon for a refund.
I know that I could complain and send the phone back to amazon myself, but the phone is in such immaculate condition (for a used device) that I’d really like to keep it if possible.
Can anyone help me? please?
Thank you,
Craig.
Click to expand...
Click to collapse
The red triangle is stock recovery. Can you post a fastboot getvar all output, What custom recovery are you trying to flash. Do not relock the boot loader with a custom recovery.

mb_guy said:
The red triangle is stock recovery. Can you post a fastboot getvar all output, What custom recovery are you trying to flash. Do not relock the boot loader with a custom recovery.
Click to expand...
Click to collapse
Thanks. I've tried flashing CWM Touch and TWRP during my various attempts.
I always get the message that the file was sent to the phone and flashed ok,
but when I try to access recovery it still goes to the triangle (stock recovery).
The Getvar all readout is in my first post, but I ran it again just in case:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4329mV
(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.047s

craighumphries said:
Thanks. I've tried flashing CWM Touch and TWRP during my various attempts.
I always get the message that the file was sent to the phone and flashed ok,
but when I try to access recovery it still goes to the triangle (stock recovery).
The Getvar all readout is in my first post, but I ran it again just in case:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4329mV
(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.047s
Click to expand...
Click to collapse
Did you try fastboot clear cache, after flashing twrp

mb_guy said:
Did you try fastboot clear cache, after flashing twrp
Click to expand...
Click to collapse
Yes, I flashed the recovery and then used the command "fastboot erase cache" (fastboot clear cache doesn't seem to do anything) . It does not report any problems at all, but it still goes to the same red triangle when i try to enter recovery. And as usual, the phone will then boot up and is completely factory reset again. I'm so confused :crying:

craighumphries said:
Yes, I flashed the recovery and then used the command "fastboot erase cache" (fastboot clear cache doesn't seem to do anything) . It does not report any problems at all, but it still goes to the same red triangle when i try to enter recovery. And as usual, the phone will then boot up and is completely factory reset again. I'm so confused :crying:
Click to expand...
Click to collapse
I may have missed this, but what does it say in the system settings about the rom

mb_guy said:
I may have missed this, but what does it say in the system settings about the rom
Click to expand...
Click to collapse
I've attached a couple of pics. Is this what you mean?

The thing that I find so odd with this phone, is that I can't go into the bootloader without it deleting everything and effectively performing a factory reset of the phone. I don't have to do anything in there at all. Just going into the bootloader screen and rebooting is enough to cause it to do this.

craighumphries said:
The thing that I find so odd with this phone, is that I can't go into the bootloader without it deleting everything and effectively performing a factory reset of the phone. I don't have to do anything in there at all. Just going into the bootloader screen and rebooting is enough to cause it to do this.
Click to expand...
Click to collapse
You might try fix permissions from TWRP

I would suggest attempting to get s-off via firewater using the temp root method. This should allow you to flash an RUU that has a downgraded hboot, which might fix your problems. Alternatively, if you don't want to get s-off, flash an RUU that has an updated hboot, which should do the same thing.

mb_guy said:
You might try fix permissions from TWRP
Click to expand...
Click to collapse
I'm not sure how I can do that, because as I was mentioning before - I can flash a recovery, but when I try to access it the phone still goes to the red triangle. It's as if the custom recovery didn't flash, even though it says that it was flashed successfully.

LightSpeedIII said:
I would suggest attempting to get s-off via firewater using the temp root method. This should allow you to flash an RUU that has a downgraded hboot, which might fix your problems. Alternatively, if you don't want to get s-off, flash an RUU that has an updated hboot, which should do the same thing.
Click to expand...
Click to collapse
Thanks. I haven't tried firewater before, so I will have a read up on how to do that. Unfortunately I can't flash any ruu as things are at the moment, because fastboot oem lock command won't work for some reason. I do ultimately want to be s-off though, so I guess I will have to be careful with newer RUU's.
I will post back my results.

Send it back. Your phone is dead.

craighumphries said:
Thanks. I haven't tried firewater before, so I will have a read up on how to do that. Unfortunately I can't flash any ruu as things are at the moment, because fastboot oem lock command won't work for some reason. I do ultimately want to be s-off though, so I guess I will have to be careful with newer RUU's.
I will post back my results.
Click to expand...
Click to collapse
OK, well I knew that it wasn't going to work as soon as I executed the first "adb reboot" command. The phone rebooted as expected, but it had also performed a factory reset in the process. Despite this I continued with the instructions, managed to copy the files and obtain temp root, but then the firewater process just terminated at bottle 6. Oh well...

SaHiLzZ said:
Send it back. Your phone is dead.
Click to expand...
Click to collapse
I guess that must be true, so I will create a return tomorrow.
It just seems so strange that I can boot the device, install apps and otherwise use the device completely normally. I guess it's time to admit defeat and send it back though.

HTC ONE M7 Endless Bootloop - No Recovery

Hi,
My HTC ONE M7 suddenly stopped working. I had everything stock, no custom firmware or anything else on it. Suddenly it powered off, powered back on again and from that on its in an endless bootloop. I only get the "HTC - powered by android" screen for ca. 10s, then it turns black and starts again. I can get into the bootloader and can enable fastboot, but when i try to start the recovery i'm back in the bootloop. Tried flashing CWM and TWRP recoverys, but non of them are working. I just get the screen "ENTERING RECOVERY" but then it shuts off and powers on again back into the bootloop.
Here are the device datas, it's a german T-Mobile:
fastboot getvar all
(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.16.111.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Removed
(bootloader) imei: removed
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 3838mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
S-ON, Bootloader Unlocked.
Hope anybody can help me with this.

dbassix said:
Hi,
My HTC ONE M7 suddenly stopped working. I had everything stock, no custom firmware or anything else on it. Suddenly it powered off, powered back on again and from that on its in an endless bootloop. I only get the "HTC - powered by android" screen for ca. 10s, then it turns black and starts again. I can get into the bootloader and can enable fastboot, but when i try to start the recovery i'm back in the bootloop. Tried flashing CWM and TWRP recoverys, but non of them are working. I just get the screen "ENTERING RECOVERY" but then it shuts off and powers on again back into the bootloop.
Here are the device datas, it's a german T-Mobile:
fastboot getvar all
(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.16.111.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: removed
(bootloader) imei: removed
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 3838mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
S-ON, Bootloader Unlocked.
Hope anybody can help me with this.
Click to expand...
Click to collapse
Please remove your imei and serialno in your first post!
While in bootloader, try a factory reset since you are completely stock. Custom recoveries will not work with a locked bootloader. Actually, if the factory reset doesn't work, you might try returning it for repair since it is basically stock.

majmoz said:
Please remove your imei and serialno in your first post!
While in bootloader, try a factory reset since you are completely stock. Custom recoveries will not work with a locked bootloader. Actually, if the factory reset doesn't work, you might try returning it for repair since it is basically stock.
Click to expand...
Click to collapse
Tried everything so far. even Factory Reset brings me to the bootloop. Don't know if i can return it for repair as the bootloader says "Tempered"

dbassix said:
Tried everything so far. even Factory Reset brings me to the bootloop. Don't know if i can return it for repair as the bootloader says "Tempered"
Click to expand...
Click to collapse
I think you need to flash a stock firmware but unfortunately I can not find one for your version 5.16.111.4. This is a long shot and I would not recommend it but you can go to this site and download both OTA files and the nandroid zip file. Open up both OTA files then double click on the firmware.zip if it is similar to the DevEd or TMOUS then the OTA going from 4.11 to 5.11 is the most complete. Extract that firmware from the OTA. We are going to flash that one and hope that it will correct the bootloop. Generally it is not recommended to flash just the firmware out of the OTA because sometimes there are some files missing but in this case you are already in a boot loop and you unlocked your bootloader. If the firmware looks similar to the attachment then it should be safe to flash. Your bootloader needs to be relocked and place the firmware.zip in your fastboot folder. You need to connect your phone to the computer and put the phone in bootloader/FASTBOOT USB mode:
Code:
[B][I]fastboot oem lock[/I][/B]
When complete, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
Hopefully, the bootloops have stopped. And you should be completely back to stock with the exception of "Tampered" and "Relocked".

dbassix said:
Hi,
My HTC ONE M7 suddenly stopped working. I had everything stock, no custom firmware or anything else on it. Suddenly it powered off, powered back on again and from that on its in an endless bootloop. I only get the "HTC - powered by android" screen for ca. 10s, then it turns black and starts again. I can get into the bootloader and can enable fastboot, but when i try to start the recovery i'm back in the bootloop. Tried flashing CWM and TWRP recoverys, but non of them are working. I just get the screen "ENTERING RECOVERY" but then it shuts off and powers on again back into the bootloop.
Here are the device datas, it's a german T-Mobile:
fastboot getvar all
(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.16.111.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Removed
(bootloader) imei: removed
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 3838mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
S-ON, Bootloader Unlocked.
Hope anybody can help me with this.
Click to expand...
Click to collapse
Hi
I have the same issue now with my One M7UL (Bouygues france).
Have you managed to fix this issue?
Thanks

[Q] need help to resurrect phone QHSUSB_DLOAD

hello everyone,i recently bought a used verizon htc one m7 (m7_wlv) in great physical condition but it would not boot into the os and just hung at the white htc android screen.
i have spent nearly 2 whole days trying to fix this, but i finally decided i need some help.:silly:
here is what its doing:
from power off state; press power button for a few seconds till it turns on, vibrates shortly and shows white "htc powered by android screen". after about 20 seconds it will go to a blank screen and the computer will recognize it as QHSUSB_DLOAD and continue to register as that for however long i leave it plugged in. i then have to hold down the power and vol- buttons until i see the bootloader then i can shut it down under the fastboot menu. it will charge when plugged into either usb or wall plug power unless in qhsusb mode
the phone is s-on and bootloader is locked
here is results from fastboot getvar all:
C:\Windows\system32>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA37WS900240
(bootloader) imei: censored
(bootloader) meid: censored
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4306mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.116s
it appears to me that this phone has never been tampered with and may have died from an update?
i have tried doing dexter's revive.sh script in both virtual machine ubuntu and ubuntu installed allongside windows and only get 'device not found aborting' messages (adb and fastboot were installed on both)
it seems to me that if only i could get s-off i could then install a custom recovery and then install a rom and be good to go. or at least unlock the bootloader and get a custom recovery. is there any way to unlock the bootloader with no adb access/ no os bootable? or is jtag my only option now? java card perhaps?
thanks again i look forward to any help:laugh:

persom55 said:
hello everyone,i recently bought a used verizon htc one m7 (m7_wlv) in great physical condition but it would not boot into the os and just hung at the white htc android screen.
i have spent nearly 2 whole days trying to fix this, but i finally decided i need some help.:silly:
here is what its doing:
from power off state; press power button for a few seconds till it turns on, vibrates shortly and shows white "htc powered by android screen". after about 20 seconds it will go to a blank screen and the computer will recognize it as QHSUSB_DLOAD and continue to register as that for however long i leave it plugged in. i then have to hold down the power and vol- buttons until i see the bootloader then i can shut it down under the fastboot menu. it will charge when plugged into either usb or wall plug power unless in qhsusb mode
the phone is s-on and bootloader is locked
here is results from fastboot getvar all:
C:\Windows\system32>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA37WS900240
(bootloader) imei: censored
(bootloader) meid: censored
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4306mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.116s
it appears to me that this phone has never been tampered with and may have died from an update?
i have tried doing dexter's revive.sh script in both virtual machine ubuntu and ubuntu installed allongside windows and only get 'device not found aborting' messages (adb and fastboot were installed on both)
it seems to me that if only i could get s-off i could then install a custom recovery and then install a rom and be good to go. or at least unlock the bootloader and get a custom recovery. is there any way to unlock the bootloader with no adb access/ no os bootable? or is jtag my only option now? java card perhaps?
thanks again i look forward to any help:laugh:
Click to expand...
Click to collapse
the phone is most likely dead (needs a new Motherboard) no jtag will help you
QHSUSB_DLOAD only happens on a bad firmware flash or a dead motherboard

Oh. From what I've read, I had assumed that since I could still access the bootloader it wasn't completely dead

persom55 said:
Oh. From what I've read, I had assumed that since I could still access the bootloader it wasn't completely dead
Click to expand...
Click to collapse
no that's even worse, with a bad firmware flash the phone is pitch black nothing on screen at all
no lights work nothing

So if I understand correctly, you're saying that since it is not a case of no lights/no response at all that my problem is not firmware related.
Darn I guess it's time to find a good motherboard then.
Well thanks for clearing it up so quickly

persom55 said:
So if I understand correctly, you're saying that since it is not a case of no lights/no response at all that my problem is not firmware related.
Darn I guess it's time to find a good motherboard then.
Well thanks for clearing it up so quickly
Click to expand...
Click to collapse
yes I did mine with a bad firmware flash and was able to fix it with dexter fix .. my phone was completely dead only sign of life was the Q mode when you plugged it into the PC (driver install error). what you have is a dead motherboard that still has a working bootloader
read more here it's only 3 pages >> http://forum.xda-developers.com/showthread.php?t=2599083

Semi Bricked Phone? Any Ideas

Good Morning Everyone,
first of all, thanks for everything I am a member since the HTC Touch HD times, where XDA enabled me to keep that device until 2015!!
Now I have a problem with the Desire 500 single sim of my wife... I just want to restore the phone to full stock to lend it to her mother so she can stay in contact with 21th-century technology (Whatsapp, ...).
Some time ago a messed a little with this device unlocking the bootloader and installing TWRP recovery, the idea was (as probably all the owners know) to install a light version ROM to have a little more space for applications, time wasn't on my side and therefore I had to leave the phone for a while, but as I can remember in working condition (still with the stock ROM).
I had some time to finish the work and a week ago a took out the phone again having a not very good surprise:
I can access now only the bootloader
Recovery send me in fastboot mode
Factory Reset send me in fastboot mode
Classic boot get me to the HTC green logo on white background without doing nothing
Fastboot commands are correctly taken
I am unable to flash whatsoever
I have to charge the phone with the batch file, but with manual booting in bootloader, otherwise, the script does not work
I am unable to relock the bootloader (the fastboot OEM lock throws a "too many links" error and fails)
The command fastboot OEM rebootRUU reboot the device, but not in RUU mode.
The bootloader is still unlocked 1.03.0001
The phone is S-ON
The OS line in the bootloader is empty
Flashing recovery throws "remote:image updated error"
Bootloader INFO
Code:
*** UNLOCKED ***
Z4U PVT SHIP S-ON RL
HBOOT-1.03.0001
RADIO-14.16.36Q4.22
OS-
eMMc-boot
Jul 8 2014, 19:15:10.0
fastboot getvar all
Code:
C:\Users\xxx>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.03.0001
(bootloader) version-baseband: 14.16.36Q4.22
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH449WE0XXXX
(bootloader) imei: XXX
(bootloader) meid:
(bootloader) product: z4u
(bootloader) platform: HBOOT-8x25Q
(bootloader) modelid: 0P3Z11200
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4040mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e9f20193
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
I think I almost checked all the internet, any suggestion simply does not work.
I tried to flash different recoveries, ROMs, RUUs... nothing works.
I need to consider the device bricked or do you guys have some other idea to try resolving the problem?
Thanks even if you spend some time for reading...
Bye
NP