Database Develop

(Solved) Need help, Bricked HTC One on OTA ?

Hello,
I´m afraid I´ve bricked the HTC One
I have a S-Off and unlocked HTC one. Stock bootloader, CWM recovery.
Today the OTA 2.19.401.1 popped up, but when trying to install it, the phone just reboot, and the OTA appeared again, and again.
I guesses the problem whas the CWM recovery, so i flashed Stock recovery , and whan entered into recovery, the OTA just started to install.
Never ends... It has been installing for more than 1 hour, progress bar stuck arround 20%
I think the problem is:
Before the big OTA 2.19.401.1 (released today in my country) a small OTA (preparation for next update) also poped up, i downloaded and installed ( At this point I still had CWM). No error at any point, just like a reboot of the phone. I think the small OTA didnt install fine becouse of the CWM, then the big OTA popped up (weird because the small one did not install properly) , changed recovery because i noticed something was not going fine.
Right now, I have my HTC one on the table, with the updating screen ( green arrouws with blue phone) stuck at 20%, no progress in the last hour. The phone is hot.
Pluging the charger does nothing (does not light the led)
Trying to power off is not also possible, even trying to long press the power button for 30+ seconds does nothing.
Any ideas? :crying:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA34xxxxxxxx
(bootloader) imei: 3544360xxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 4001mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT

Finally I managed to reset the device by pressing VolUp + VolDown + Power for 20+ seconds.
I have entered into bootloader and factory reset the device.
It bootep then, with some errors and the rom doesnt working, but finally it was detected by the comupter and chargind, so I´m flashing right now a RUU. I guess i will have no more problems, I will confirm when is finally solved.

OK, I can breath now , Restored with RUU and now the system is running fine again, updating riht now.
Can be marked as solved.

[Q] Stuck at boot screen after update - factory reset doesn’t work

Hi,
yesterday I tried to update my phone and it got stuck on the triangle with a red exclamation point symbol. After I while I tried to force the reboot and it just started to endlessly reboot…
I read some stuff over this forum, but all involved an attempt to root the phone, or to install a custom rom, which is not my case. I also tried to factory reset the phone with the power + volume down menu, but nothing to do, it still happen… Impossible to get my phone to work.
Should I try to root the phone or something ? Or is it better to just ask htc/give it back to the store ?
Thanks, have a nice day.
SilverDuck

How did you update?
What exactly did you do?
Mike

Here’s exactly what I did*:
-Notification for update, I say ok
-It restart, I got the dark screen with the phone with the update symbol
-It turns red, I wait a long time
-I long press the power button, and it won’t start anymore
Later I tried to factory reset…
Should I try to flash a stock rom ?

SilverDuck said:
Here’s exactly what I did*:
-Notification for update, I say ok
-It restart, I got the dark screen with the phone with the update symbol
-It turns red, I wait a long time
-I long press the power button, and it won’t start anymore
Later I tried to factory reset…
Should I try to flash a stock rom ?
Click to expand...
Click to collapse
hoping you're on windows 7,
force reboot youre phone,
so before it starts pull vol - plus power button to get into bootloader, now scroll using volume buttons and select fastboot using power
now plug it to the pc
wait and hope to drivers to install
in the meantime download the RUU that matches with your country (take it here: http://forum.xda-developers.com/showthread.php?p=39588860)
now execute as administrator the ruu (is an .exe)
wait untill it finishes and now start using phone again
edit: sorry for my bad english, i do not speak it

any nwes?

Hi, thanks.
I wanted to try an RUU, but I can’t find it… links on your page are down.
Any idea where I could find one for that :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *********************
(bootloader) imei: ******************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: low
(bootloader) battery-voltage: 3532mV
(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!
See you !

SilverDuck said:
Hi, thanks.
I wanted to try an RUU, but I can’t find it… links on your page are down.
Any idea where I could find one for that :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *********************
(bootloader) imei: ******************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: low
(bootloader) battery-voltage: 3532mV
(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!
See you !
Click to expand...
Click to collapse
edit: sorry, forgott that bugsylawson had to give up his thread..
i'd have a matching ruu for you, but i have no idea where i could upload such a big file...

herwegan said:
edit: sorry, forgott that bugsylawson had to give up his thread..
i'd have a matching ruu for you, but i have no idea where i could upload such a big file...
Click to expand...
Click to collapse
somwhere like dropbox...or maybe you can tell us which RUU it is and we'll find it

OsarcotL said:
somwhere like dropbox...or maybe you can tell us which RUU it is and we'll find it
Click to expand...
Click to collapse
new thread just opened! you can find RUU's here: http://forum.xda-developers.com/showthread.php?t=2428276
aww sh**.. sorry, have just seen you're s-on with hboot 1.54... :/ you can't downgrade hboot with s-on (and due to 1.54 you can't get s-off). so you're stuck with this until we get a RUU from 1.54 (the ones that are available are 1.44)..
sorry for you

Okay, thanks a lot guys !
I guess I'll just wait for a while to see if someone releases it…
Also, to be sure, what should I pay attention to ? The hboot version and the baseband ?
@++

SilverDuck said:
Okay, thanks a lot guys !
I guess I'll just wait for a while to see if someone releases it…
Also, to be sure, what should I pay attention to ? The hboot version and the baseband ?
@++
Click to expand...
Click to collapse
Yes, now i'm looking for any RUU that can be istalled on your hd2

OsarcotL said:
hoping you're on windows 7,
force reboot youre phone,
so before it starts pull vol - plus power button to get into bootloader, now scroll using volume buttons and select fastboot using power
now plug it to the pc
wait and hope to drivers to install
in the meantime download the RUU that matches with your country (take it here: http://forum.xda-developers.com/showthread.php?p=39588860)
now execute as administrator the ruu (is an .exe)
wait untill it finishes and now start using phone again
edit: sorry for my bad english, i do not speak it
Click to expand...
Click to collapse
hi, I have a similar problem and have tried this advice but the drivers will not install onto my computer. the factory reset does not work. have you any advice for what to try next?

joshrob said:
hi, I have a similar problem and have tried this advice but the drivers will not install onto my computer. the factory reset does not work. have you any advice for what to try next?
Click to expand...
Click to collapse
If you want help read some threads of others asking for help.
We need your phone carrier / PC OS version / last android update installed / info from the bootloader and fastboot getvar all (minus your Serial no. and IMEI).

joshrob said:
hi, I have a similar problem and have tried this advice but the drivers will not install onto my computer. the factory reset does not work. have you any advice for what to try next?
Click to expand...
Click to collapse
are you running windows 7?

[SOLVED] htc one m7 (won't boot)

Hey everyone,
So I turned my phone off today, then when i tried to start it, it wouldn't start. I press and hold the power button for about 3 seconds, then the lights flash, and that's it.
It's is worth mentioning that the phone does indeed charge though when plugged in.
But what can I do to fix this problem?

I'd hold it longer. For like a minute as an example. Had the same issue. Held the buttons longer and it rebooted.
Sent from my HTC One using Tapatalk

pacmanandre said:
Hey everyone,
So I turned my phone off today, then when i tried to start it, it wouldn't start. I press and hold the power button for about 3 seconds, then the lights flash, and that's it.
It's is worth mentioning that the phone does indeed charge though when plugged in.
But what can I do to fix this problem?
Click to expand...
Click to collapse
try in a bright light (in front of sensors)

bbinder said:
I'd hold it longer. For like a minute as an example. Had the same issue. Held the buttons longer and it rebooted.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
That was interesting. I held it long, and the lights continously flashed, but it eventually booted up. So my current problem is solved! Thanks for the help.
However, even though I got my phone rebooted, I have some concerns because this is not normal.
Why did it take that long to boot the phone?
Can this be a sign of a larger problem?
How can I prevent it from taking this long?

Help needed
Hey friend,
I have a HTC one M7_U which is rooted but S-On. I had installed custom rom on it...and all was working fine.
Yesterday i tried something with Xposed installer and phone restarted and now its stuck at the HTC beats audio white screen.
Please help...?
Steps already done so far
> Tried installing Xposed disaber recovery----It gave error in flashing
> No recovery made before
> Tried to use adb shell command but its giving error :closed. Same error for adb usb. adb devices show the device and allows to sideload too.
> Tried resetting to factory --- Didn't worked
My device details are as follows
M7_U PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.63.707.4
eMMC-boot 2048MB
(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.63.707.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35PW904368
(bootloader) imei: 354435054280904
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4007mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ea0bccbd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please help me mate.
Thanks.

pacmanandre said:
That was interesting. I held it long, and the lights continously flashed, but it eventually booted up. So my current problem is solved! Thanks for the help.
However, even though I got my phone rebooted, I have some concerns because this is not normal.
Why did it take that long to boot the phone?
Can this be a sign of a larger problem?
How can I prevent it from taking this long?
Click to expand...
Click to collapse
Don't forget to hit the thanks button. Chalk it up as a 1-off incident if it doesn't happen to you again. If the issue is considered resolved for now, be sure to mark it as such in the title by renaming it as recommended. I wouldn't say it's the sign of a larger problem if it has only happened once. Holding down those buttons for a longer period of time is really "working as advertised". Sometimes it just takes longer to make the restart happen. I've *thought* I turned my phone off but it crashed on the way down and it was really on but the screen was black. Holding in the buttons for a longer period of time took care of the reboot operation and I just had to undo what was done before I tried shutting the phone down. In my case I was messing with a few settings that conflicted with another module.
---------- Post added at 01:19 PM ---------- Previous post was at 01:17 PM ----------
er.ajeet said:
Hey friend,
I have a HTC one M7_U which is rooted but S-On. I had installed custom rom on it...and all was working fine.
Yesterday i tried something with Xposed installer and phone restarted and now its stuck at the HTC beats audio white screen.
Please help...?
Steps already done so far
> Tried installing Xposed disaber recovery----It gave error in flashing
> No recovery made before
> Tried to use adb shell command but its giving error :closed. Same error for adb usb. adb devices show the device and allows to sideload too.
> Tried resetting to factory --- Didn't worked
My device details are as follows
M7_U PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.63.707.4
eMMC-boot 2048MB
(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.63.707.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35PW904368
(bootloader) imei: 354435054280904
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4007mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ea0bccbd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please help me mate.
Thanks.
Click to expand...
Click to collapse
Make a new thread for this. All I can offer is that I've had it happen and using CWM or TWRP for recovery, you can simply uninstall Xposed from Recovery. Once you do, your phone should reboot just fine after a 1-2 minute delay. But be patient when waiting for the screen to advance.

[Q] Bricked Phone? blue/purple screen

I was trying to get my HTC one from Rogers back to stock to take advantage of their suretap promotion that is running right now.
I had gotten to the point where I had installed the Rogers RUU RUU_M7_UL_K44_SENSE55_MR_Rogers_WWE_4.19.631.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_351317_signed_2.
From what I was reading once I had that I could flash a stock recovery and that would allow me to use OTA updates again. Everything was ok up to the point where I tried to install the OTA update. The update failed and when I rebooted my phone it showed a blue screen with little darker blue lines on it, then a purple screen with little yellow lines on it before it stops on the HTC one screen and doesn't do anything else.
I can boot into fastboot and recovery but can't seem to get anything to work from there.
Has anyone had this happen to them or can anybody help me get my phone working again? Thanks in advance!
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.631.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4290mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.105s

Kowaliszyn said:
I was trying to get my HTC one from Rogers back to stock to take advantage of their suretap promotion that is running right now.
I had gotten to the point where I had installed the Rogers RUU RUU_M7_UL_K44_SENSE55_MR_Rogers_WWE_4.19.631.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_351317_signed_2.
From what I was reading once I had that I could flash a stock recovery and that would allow me to use OTA updates again. Everything was ok up to the point where I tried to install the OTA update. The update failed and when I rebooted my phone it showed a blue screen with little darker blue lines on it, then a purple screen with little yellow lines on it before it stops on the HTC one screen and doesn't do anything else.
I can boot into fastboot and recovery but can't seem to get anything to work from there.
Has anyone had this happen to them or can anybody help me get my phone working again? Thanks in advance!
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.631.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4290mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.105s
Click to expand...
Click to collapse
Are you able to re-run the ruu from fastboot?
Your version-main in bootloader reads as 1.29.631.4, yet the ruu is 4.19.631.9?

stovie_steve said:
Are you able to re-run the ruu from fastboot?
Your version-main in bootloader reads as 1.29.631.4, yet the ruu is 4.19.631.9?
Click to expand...
Click to collapse
I had tried a couple of times with no luck but since you asked I tried again and it worked! Thanks!

I had those screens also and then it would sit at the HTC logo screen. I rebooted the device by pressing the power and up button or maybe both volume button and power then on the third try when i clicked power and down it went to the bootloader whoohoo I thought I would have to wait for it to die. Was not repsonding to adb or fastboot queries.

[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