(Solved) Need help, Bricked HTC One on OTA ? - One (M7) Q&A, Help & Troubleshooting

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.

Related

[Q] Screwed up boot?

Hello everybody,
following problem.
I have a unbranded One (.401) and used the OIA Tool to unlock the bootloader and flash recovery.
Then I installed ARHD 10.0 wich was working like a charm. Also when i wanted to upgrade to 10.2 everything was fine.
The the trouble started.
Yesterday my phone hung up, well no big deal I thought so I did a soft reset but from now on my phone was in bootloop. Ok so I went in Recovery and wiped cache nothing changed no boot.
Then I decided to completely reflash the rom and rebotet the device after half an hour in start logo (htc logo after the red warning) i decided to redo the whole procedure nothing changed it wont boot up (wiped and formated everything possible each time)
Then wanted to bring it into "out of the Box" mode to start from zero
So i picked my RUU (RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed) and installed it. No errors nothing.
First startup worked but when I wanted to call somebody the "whole" system crashed and reboted itself.
After this i just got after the HTC logo with the red warning just a black screen (its still iluminated but its just black).
I tried the ruu a couple times more but still the same.
I am still able to acces bootloader and fastboot and recovery.
Does anybody has a clue what i coould do now except bring it in to HTC?
Here a couple more Informations
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.401.7
(bootloader) version-misc: PVT SHIP S-OFF
(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: 3916mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT

HTC One Stuck on OTA Update Screen - Bricked?

Hi Guys,
I'm having some serious issues with the HTC One.
It is stuck on the OTA Update on about one third progress. Doesn't respond to anything right now.
My Device was rooted and the bootloader was unlocked. I also had flashed a Custom Recovery (TWRP).
Today I received an OTA notification for the new 2.24 Version. I downloaded it, but obviously I couldn't update because of the TWRP recovery. So I gathered the information of my device with fastboot, because I needed to flash the correct RUU:
(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.161.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35FW918759
(bootloader) imei: 354436052474242
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP120
(bootloader) battery-status: good
(bootloader) battery-voltage: 3829mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status malformed (0 bytes))
finished. total time: 5.557s
The 1.29.161.16 Version was nowhere available so I downloaded the OTA_M7_UL_JB_50_Vodafone_UK_1.29.161.11-1.28.161.7_release_315813_signedoj2qp335qmm8qjso.z ip from this Thread.
After flashing the RUU and booting up the phone again, everything seems to be alright. It showed me the OTA notification again, ready for installing. I then started the Update and it has been stuck for about one hour since then. I can't reboot the device. Nothing of the button combination seems to be working. The progress bar is about one third completed.
Has the update probably failed because I downloaded the OTA before flashing the RUU?
Can anyone please help? Am really freaked out right now and I hope the device is still usable
A thousand thanks!
Cheers,
Martin
Hold the phone under / Near a bright Light... and press and hold the power button for a few seconds... the capacitive lights would start blinking and your phone would restart...
Thanks for your reply, I just tried your advice. The capacitive lights on the buttons are starting to blink but I can hold the power button for ages, nothing happens.
EDIT: I did WORK!! I had to go to the bathroom were the brightest lights are xD
Had to do this twice. OTA Update went through the second time but then the phone was stuck on a black screen again. after doing it the second time it completed the update. HTC One is running 4.2.2 2.24.161.1 right now.
Thank you so much!!
You saved my evening and probably my whole week
mmetnitzer said:
Thanks for your reply, I just tried your advice. The capacitive lights on the buttons are starting to blink but I can hold the power button for ages, nothing happens.
EDIT: I did WORK!! I had to go to the bathroom were the brightest lights are xD
Click to expand...
Click to collapse
lesson learned : flashing and flushing should be done in the bathroom
Deleted

[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] Phone won't boot regardless

Ok, so two days ago, I had flashed beanstalk rom. Everything went well, after i changed a couple beanstalk specific settings and then i attempted to reboot. However, it refused to boot, just got stuck on the boot animation. In addition to not booting, twrp wont fully load. It shows the logo but then restarts only to go nowhere. I flashed cwm touch, used an otg cable to try to install viper rom again, but randomly restart towards the end of the installation. It doesn't let me wipe data. It just restarts. i can get to bootloader/fastboot. But that's pretty much it .. recovery is barely any help. If someone can steer me in the right direction to get this thing up and running again, i'd appreciate it. I tried to do everything in my knowledge to restore it, but i've ran out ideas.
(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) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3730mV
(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
no matter what i try to flash, the phone just reboots..
update: i flashed the stock recovery and i get the red triangle with a picture of a phone. What can i do from here?
Try to flash stock rom
Ayoodannyx said:
Ok, so two days ago, I had flashed beanstalk rom. Everything went well, after i changed a couple beanstalk specific settings and then i attempted to reboot. However, it refused to boot, just got stuck on the boot animation. In addition to not booting, twrp wont fully load. It shows the logo but then restarts only to go nowhere. I flashed cwm touch, used an otg cable to try to install viper rom again, but randomly restart towards the end of the installation. It doesn't let me wipe data. It just restarts. i can get to bootloader/fastboot. But that's pretty much it .. recovery is barely any help. If someone can steer me in the right direction to get this thing up and running again, i'd appreciate it. I tried to do everything in my knowledge to restore it, but i've ran out ideas.
(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) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3730mV
(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
have you made a backup?
if yes restore your phone
or move an other rom zip file to your phone using adb commands and try to flash it
I had gotten it to work again by flashing the stock recovery and letting it sit for a few mins, then it booted. But now i have a new problem, and it just happened. I was using my phone normally (fb messenger) and the phone just shut off randomly and refuses to turn on. Battery is good, it wont even boot into bootloader...nothing.
Ayoodannyx said:
I had gotten it to work again by flashing the stock recovery and letting it sit for a few mins, then it booted. But now i have a new problem, and it just happened. I was using my phone normally (fb messenger) and the phone just shut off randomly and refuses to turn on. Battery is good, it wont even boot into bootloader...nothing.
Click to expand...
Click to collapse
sounds like your motherboard just died ...did it get wet ?
clsA said:
sounds like your motherboard just died ...did it get wet ?
Click to expand...
Click to collapse
no sir, no water damage, no falls, same condition physically as i got it
i ended up calling tmobile for a replacement, will get it monday afternoon, thanks for the help
Ayoodannyx said:
i ended up calling tmobile for a replacement, will get it monday afternoon, thanks for the help
Click to expand...
Click to collapse
good deal ..I hope you get a good one the first try

Help. Please. M7 ota update fail after guru reset.

Hi Guys.
I really need some help here and would really appreciate it as it's driving me up the wall for the past week. And I have combed through the forum looking for a solution before posting. So here goes.
I have a One M7 running on ARHD84 with 6.13.707.1 firmware. Learning of the coming OTA update for Lollipop, I decided to return to stock the best I can S-ON. Thus my nightmare begins.
1) I did a nandroid backup restore with a file named 2014-09-15--13-39-50 KTU84L release-keys (I don't have a nandroid backup of my own). It worked fine. Then I did the OTA update (6.13.707.4). It pops an error "Variant System Version".
2) Thinking it must be the nandroid issue, I went for guru reset 3.63.707.4 ROM and it installed with stock recovery and radio. Startup okay then I did the OTA update. It installed halfway and stopped to show a red exclamation error. I hard reset the phone and it went into a bootloop. It loops at the HTC logo. I went into fastboot, flashed twrp and got my phone back with the nandroid backup.
** Stock recovery goes into black screen.
3) Tried the nandroid again. Still Variant System Version.
4) Tried a lower guru reset 2.24.707.1 and it installed with stock recovery and radio. Startup okay and did the OTA update. It installed 1/3 and went into bootloop. This time it took me many many many tries to get back into bootloader.
** Stock recovery never happens, it just goes to black screen
5) Scoured the internet, came back a little wiser and tried the gurureset 3.63.707.4 again. This time I flashed the stock recovery again just to be sure. And this time, guess what.... same thing. Installs 1/3 and goes into the red exclamation mark. Only advancement was it did not go into bootloop.
My getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: pewpewpew
(bootloader) imei: blablablablabla
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3868mV
(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
Would really appreciate if someone could help me out here. At my wit's end.
Thanks!
mojo1ne said:
Hi Guys.
I really need some help here and would really appreciate it as it's driving me up the wall for the past week. And I have combed through the forum looking for a solution before posting. So here goes.
I have a One M7 running on ARHD84 with 6.13.707.1 firmware. Learning of the coming OTA update for Lollipop, I decided to return to stock the best I can S-ON. Thus my nightmare begins.
1) I did a nandroid backup restore with a file named 2014-09-15--13-39-50 KTU84L release-keys (I don't have a nandroid backup of my own). It worked fine. Then I did the OTA update (6.13.707.4). It pops an error "Variant System Version".
2) Thinking it must be the nandroid issue, I went for guru reset 3.63.707.4 ROM and it installed with stock recovery and radio. Startup okay then I did the OTA update. It installed halfway and stopped to show a red exclamation error. I hard reset the phone and it went into a bootloop. It loops at the HTC logo. I went into fastboot, flashed twrp and got my phone back with the nandroid backup.
** Stock recovery goes into black screen.
3) Tried the nandroid again. Still Variant System Version.
4) Tried a lower guru reset 2.24.707.1 and it installed with stock recovery and radio. Startup okay and did the OTA update. It installed 1/3 and went into bootloop. This time it took me many many many tries to get back into bootloader.
** Stock recovery never happens, it just goes to black screen
5) Scoured the internet, came back a little wiser and tried the gurureset 3.63.707.4 again. This time I flashed the stock recovery again just to be sure. And this time, guess what.... same thing. Installs 1/3 and goes into the red exclamation mark. Only advancement was it did not go into bootloop.
My getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: pewpewpew
(bootloader) imei: blablablablabla
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3868mV
(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
Would really appreciate if someone could help me out here. At my wit's end.
Thanks!
Click to expand...
Click to collapse
Try this TWRP backup https://www.bloglovin.com/blogs/xda-developers-5233323/stock-rom-6137071-asia-twrp-backup-3430002891 do not use the modified firmwqare, it will brick your phone as your s-on.
Give up with the Guru resets, they are failing because your bootloader is too new and even the OTA cant back flash your bootloader, those OTA's will be trying to install HBOOT 1.54 or something like that.
Seanie280672 said:
Try this TWRP backup do not use the modified firmwqare, it will brick your phone as your s-on.
Give up with the Guru resets, they are failing because your bootloader is too new and even the OTA cant back flash your bootloader, those OTA's will be trying to install HBOOT 1.54 or something like that.
Click to expand...
Click to collapse
Thanks for the reply man.
Unfortunately, that's the exact same backup I used in step 1. Get's the variant system error.

Categories

Resources