Database Develop

[Q] Help! Bricked my GPE during 4.4 OTA update!

Guys, I was asking about this on another thread about GPE OTA URL, but since I'm running into trouble, maybe I should post here too. After an OTA update to 4.4, the phone is now in bootloop. I tried to do RUU but I can't since my phone is S-ON. I tried to follow thread of revone, but I can't connect to my phone through adb. I also tried factory reset through recovery. I can see the Welcome screen for a second and it boots again.
Now the phone is bricked. Is there anything I can do to solve it?
My Phone:
- Real HTC ONE GPE from google play store
- TAMPERED, RELOCKED(I tried to unlock it through steps from htcdev. I am not see the disclaimer screen now after I could load the Unlock_code.bin to the device already)
- HBOOT 1.54, S-ON
- Stock recovery.

felix1212 said:
Guys, I was asking about this on another thread about GPE OTA URL, but since I'm running into trouble, maybe I should post here too. After an OTA update to 4.4, the phone is now in bootloop. I tried to do RUU but I can't since my phone is S-ON. I tried to follow thread of revone, but I can't connect to my phone through adb. I also tried factory reset through recovery. I can see the Welcome screen for a second and it boots again.
Now the phone is bricked. Is there anything I can do to solve it?
My Phone:
- Real HTC ONE GPE from google play store
- TAMPERED, RELOCKED(I tried to unlock it through steps from htcdev. I am not see the disclaimer screen now after I could load the Unlock_code.bin to the device already)
- HBOOT 1.54, S-ON
- Stock recovery.
Click to expand...
Click to collapse
try finding a full GPE RUU and try to get your phone back. with relocked bootloader and no S-off and HTCdev no working, this is your only option. Don't know where the GPE RUUs are otherwise I would have linked.
so search very well, and make sure it's for your phone (CID & MID) and try it. and don't rush into things!!!
if you have questions, better to ask and wait for a response, before you have a paperweight.

What was the error when you ran the 4.4 non-rooted RUU from: http://forum.xda-developers.com/showthread.php?t=2358781 ?
Remember you have to run the fastboot flash ruu command twice as per that link.

Same Here
Almost exactly the same thing happened to me, my GPe is locked though. I tried all the 4.4, 4.3, and 4.2.2 RUU and get FAILED (remote: 12 signature verify fail).
I tried unlocking bootloader using "fastboot oem unlock" and get this error:
(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
(bootloader) [PG_ERROR] htc_pg_part_read(1029):
(bootloader) htc_pg_part_traverse failed
(bootloader) [DISPLAY_ERR] sp_custom partition: unlock_disp_buf.img_buf r
(bootloader) ead error!
(bootloader) [DISPLAY_ERR] Can not load custom splash!
(bootloader) Loading custom splash failed!
OKAY [ 0.543s]
finished. total time: 0.543s
Click to expand...
Click to collapse
I tried unlocking using Unlock_code.bin and it shows the following message which looks fine:
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.003s]
Click to expand...
Click to collapse
But the bootloader is still locked.
Super desperate right now...
btw, my getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.58.1700.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) imei: 3xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4183mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse

Just tried 4.4 RUU, and I got below error message.
C:\HTC\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk
\platform-tools>fastboot flash zip RUU-HTC_One_GE-4.4-3.58.1700.5.zip
target reported max download size of 1526722560 bytes
sending 'zip' (506183 KB)...
OKAY [ 23.387s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 68.634s

Can you flash a custom recovery? If so, can your phone boot into it?
fastboot flash ruu is failing due to you being S-On.

SaHiLzZ said:
Can you flash a custom recovery? If so, can your phone boot into it?
fastboot flash ruu is failing due to you being S-On.
Click to expand...
Click to collapse
I'm checking on that too. May I know if I'm okay to do so if my bootloader is relocked?

Unlock it.

SaHiLzZ said:
Unlock it.
Click to expand...
Click to collapse
Tried. As I said before, if I follow instructions from htcdev, somehow I'm not getting the disclaimer screen after I flash the Unlock_code.bin. I also tried fastbook oem unlock but no luck. Couldn't find other ways to unlock the bootloader.
May I know if there's any way I can unlock it?

Fastboot oem unlock

I'm have the same issue as others...
Currently my bootloader says i have OS-3.58.1700.5, but no OS will load, and I am on a neverending loop....
Currently my system is locked. (I stupidly followed HTC's advice for updating and relocked my device).
And i no longer have twrp - once again following advice of others and putting on the stock bootloader.
I do have the stock bootloader, but i cannot install anything, and I cannot get past the google start screen (just cycles between Google and black).
I tried re-unlocking, both with the HTCdev tool - which looked like it was successful, but still reads "relocked".
And the fastboot oem unlock gives me the following error:
(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
(bootloader) [PG_ERROR] htc_pg_part_read(1029):
(bootloader) htc_pg_part_traverse failed
(bootloader) [DISPLAY_ERR] sp_custom partition: unlock_disp_buf.img_buf r
(bootloader) ead error!
(bootloader) [DISPLAY_ERR] Can not load custom splash!
(bootloader) Loading custom splash failed!
OKAY [ 0.538s]
finished. total time: 0.538s
any attempts to flash a stock ROM using fastboot commands gives me the following error:
target reported max download size of 1526722560 bytes
sending 'zip' (428998 KB)...
OKAY [ 18.008s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 51.867s
I should've just kept 4.3.
I was so desperate I contacted HTC - but my phone says "TAMPERED" and "RELOCKED", so they would definitely have issues up-keeping the warranty.
The rest of the info in my bootloader reads:
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4T.21.3218.21
OpenDSP-v32.120.274.0909
OS-3.58.1700.5
eMMC-boot 2048MB
I would simply be happy to get to where i was before on GPe 4.3, and hopefully with twrp re-installed so i can recover my last backup! Please help, if you can!!!

SaHiLzZ said:
Fastboot oem unlock
Click to expand...
Click to collapse
Thanks for your reply. As I stated earlier, I can't unlock it with fastboot. Here is the error.
C:\HTC\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk
\platform-tools>fastboot oem unlock
...
(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
(bootloader) [PG_ERROR] htc_pg_part_read(1029):
(bootloader) htc_pg_part_traverse failed
(bootloader) [DISPLAY_ERR] sp_custom partition: unlock_disp_buf.img_buf r
(bootloader) ead error!
(bootloader) [DISPLAY_ERR] Can not load custom splash!
(bootloader) Loading custom splash failed!
OKAY [ 0.539s]
finished. total time: 0.539s

fastboot boot recovery-clockwork-touch-6.0.4.5-m7ul.img
download this recovery and put it in the fastboot folder and use that fastboot command, if it boot into recovery u then can install a s-on compatible rom that does not bootloop. Credit to nkk71.

SleepingDragon said:
fastboot boot recovery-clockwork-touch-6.0.4.5-m7ul.img
download this recovery and put it in the fastboot folder and use that fastboot command, if it boot into recovery u then can install a s-on compatible rom that does not bootloop. Credit to nkk71.
Click to expand...
Click to collapse
Thanks for your reply!! I went through topics by nkk71. However, I can't find threads about s-on compatible ROM to download. May I know where I can find it? Also, is there any instruction about installing that through clockworkmod recovery?
Really thanks again!

felix1212 said:
Thanks for your reply!! I went through topics by nkk71. However, I can't find threads about s-on compatible ROM to download. May I know where I can find it? Also, is there any instruction about installing that through clockworkmod recovery?
Really thanks again!
Click to expand...
Click to collapse
BTW, thanks for naming me, but if you wanna get my attention use @ as in @nkk71, (like @felix1212) that would show me a mention and I would see it.
So what's your situation, (seems a few cross-posts, so don't wanna mix thinks up, can you give a quick summary, i understand your s-on, but what's your "fastboot getver all" (remove IMEI and s/n), and where did you get stuck.

I'm going through a similar issue right now. I have a HTC one that I had converted to a GPe by changing the CID etc. All was well until the 4.4 OTA update bricked my device. It shows the "GOOGLE" screen, then black then sometimes the screen again, then some error message.
I found a collection of HTC one RUU's here http://forum.xda-developers.com/showthread.php?t=2428276&highlight=4+4
And a little guide on how to flash RUU's here. http://forum.xda-developers.com/showthread.php?t=2251800
Hopefully there is some information in there that will help you out. Keep in mind that when flashing an RUU you will lose all your data. It basically becomes a new phone. But you should be able to do it, no matter what state your phone is in. so long as you have fastboot access.

I appear to be in a similar situation:
- S-ON Google Play Edition HTC One
- Took KitKat 4.4 OTA and ended up in reboot loop
- Cleared all caches + data partition from CWM. Didn't help.
- Decided to try to flash from RUU
- Read that I needed to re-lock my bootloader in order to flash an RUU and get out of this mess
- relocked using fastboot oem lock
- Tried to install several RUUs: 4.4 rooted, 4.4 stock, 4.3 stock.
All of them fail like this:
Code:
[email protected] jb $ fastboot flash zip jb.zip
target reported max download size of 1526722560 bytes
sending 'zip' (388627 KB)...
OKAY [ 17.914s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 53.637s
Tried to re-unlock. That fails like this:
Code:
[email protected] Downloads $ fastboot oem unlock
...
(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
(bootloader) [PG_ERROR] htc_pg_part_read(1029):
(bootloader) htc_pg_part_traverse failed
(bootloader) [DISPLAY_ERR] sp_custom partition: unlock_disp_buf.img_buf r
(bootloader) ead error!
(bootloader) [DISPLAY_ERR] Can not load custom splash!
(bootloader) Loading custom splash failed!
OKAY [ 0.537s]
finished. total time: 0.537s
Here's my getvars all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REDACTED
(bootloader) imei: REDACTED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4053mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Some thoughts:
- Being s-off would bypass the signature error during RUU
- I can't s-off in 1.54 without having a bootable phone
- I might be able to get a bootable phone by installing a 4.3 .zip file using CWM or flashing system.img using fastboot, but I can't do those things with a locked bootloader, and can't re-unlock the bootloader due to the above failures.
Open questions:
- Why do the RUU's fail signature validation? They are being presented as stock RUU's.
- Is there an .exe RUU for the GPE HTC ONE?
- Why doesn't 'fastboot oem unlock' work anymore? I thought that was the method for GPE HTC ONEs
This happened to my phone and also my girlfriend's, which are identical phones with identical OS/update situations. I haven't re-locked her bootloader, so there may be more options there, but I wanted to avoid messing with her phone further until I exhaust every path available on mine.

I had the same problem. I found 4.3 stock ROM for Google Play Edition HTC One, used TWRP to push the ROM to storage then from TWRP recovery installed the 4.3 ROM. It worked then updated to JWR66Y.H1 and now am waiting for 4.4 OTA.
Sent from my HTC One using XDA Premium 4 mobile app

tmanonyx said:
I had the same problem. I found 4.3 stock ROM for Google Play Edition HTC One, used TWRP to push the ROM to storage then from TWRP recovery installed the 4.3 ROM. It worked then updated to JWR66Y.H1 and now am waiting for 4.4 OTA.
Click to expand...
Click to collapse
Thanks, I used your method with CWM and M7_UL_JB43_STOCK_UI_S_Google_WWE_3.06.1700.10.zip and got the gf's phone up and running again on jb.
Unfortunately, my phone was the guinea pig earlier on and it's now stuck with a re-locked bootloader and stock recovery .
Looks like my next step is figuring out how to re-unlock the bootloader. Very frustrating. Unlocking/locking are supposed to be easily reversible on google edition devices.

Good, it took me literally 36 hours to get mine up and running.
Sent from my HTC One using XDA Premium 4 mobile app

guru reset - stuck with no OTG

I have managed to reset my One with this Guru Reset M7 1.27.531.11
.
It's the proper one for my phone, but alas I'm left in need of an OTG cable to further myself to update the OTA.
I don't have one and it's unlikely I'll find one nearby today.
Is there any way forward or am I phoneless until?

metropical said:
I have managed to reset my One with this Guru Reset M7 1.27.531.11
.
It's the proper one for my phone, but alas I'm left in need of an OTG cable to further myself to update the OTA.
I don't have one and it's unlikely I'll find one nearby today.
Is there any way forward or am I phoneless until?
Click to expand...
Click to collapse
Sorry bro, i can't help u with OTG cable but can i ask u something how did u manage to reset and make stock your phone? I want to do the same but i have Hboot 1.56 , unlocked bootloader, s-off and the latest firmware.

HC4Life said:
Sorry bro, i can't help u with OTG cable but can i ask u something how did u manage to reset and make stock your phone? I want to do the same but i have Hboot 1.56 , unlocked bootloader, s-off and the latest firmware.
Click to expand...
Click to collapse
http://www.htc1guru.com
but obviously, be careful

metropical said:
I have managed to reset my One with this Guru Reset M7 1.27.531.11
.
It's the proper one for my phone, but alas I'm left in need of an OTG cable to further myself to update the OTA.
I don't have one and it's unlikely I'll find one nearby today.
Is there any way forward or am I phoneless until?
Click to expand...
Click to collapse
what does an OTG cable have to do with the GURU reset ? and why such an old version your already on 3.xx.xxx.x
If your stuck with no touch screen why did you flash the old software without having the OTG doggle ready ?
I'm going to guess your not s-off ?
here's the RUU
http://www.htc1guru.com/dld/ruu_m7_...3_10-38m-1157-04_release_336982_signed_2-exe/
mirror - http://shipped-roms.com/download.ph...03_10.38m.1157.04_release_336982_signed_2.exe
HC4Life said:
Sorry bro, i can't help u with OTG cable but can i ask u something how did u manage to reset and make stock your phone? I want to do the same but i have Hboot 1.56 , unlocked bootloader, s-off and the latest firmware.
Click to expand...
Click to collapse
their are newer guides for resetting your phone
http://forum.xda-developers.com/showthread.php?t=2541082

clsA said:
what does an OTG cable have to do with the GURU reset ? and why such an old version your already on 3.xx.xxx.x
If your stuck with no touch screen why did you flash the old software without having the OTG doggle ready ?
I'm going to guess your not s-off ?
here's the RUU
http://www.htc1guru.com/dld/ruu_m7_...3_10-38m-1157-04_release_336982_signed_2-exe/
their are newer guides for resetting your phone
http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
coz I misread.
s-off no.
.exe does me no good. should have mentioned on OSX.
I've been unable to S-Off using Firewater, Rumrunner or revone.
Bootloader 1.55

metropical said:
coz I misread.
s-off no.
.exe does me no good. should have mentioned on OSX.
I've been unable to S-Off using Firewater, Rumrunner or revone.
Bootloader 1.55
Click to expand...
Click to collapse
I suggest you find a windows PC if you want to mess with your phone
here's your RUU Zip - rename to rom.zip
http://shipped-roms.com/download.ph...03_10.38m.1157.04_release_336982_signed_2.zip
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip << -- yes 2 times
fastboot reboot

clsA said:
I suggest you find a windows PC if you want to mess with your phone
here's your RUU Zip - rename to rom.zip
http://shipped-roms.com/download.ph...03_10.38m.1157.04_release_336982_signed_2.zip
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip << -- yes 2 times
fastboot reboot
Click to expand...
Click to collapse
Yosemite-Sam:~ fritz$ fastboot devices
FA35YW901363 fastboot
Yosemite-Sam:~ fritz$ fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.158s]
finished. total time: 0.158s
Yosemite-Sam:~ fritz$ fastboot flash zip rom.zip
error: cannot load 'rom.zip'
Yosemite-Sam:~ fritz$ fastboot flash zip rom.zip
error: cannot load 'rom.zip'
Yosemite-Sam:~ fritz$ fastboot reboot
rebooting...
finished. total time: 0.034s
Yosemite-Sam:~ fritz$

metropical said:
Yosemite-Sam:~ fritz$ fastboot devices
FA35YW901363fastboot
Yosemite-Sam:~ fritz$ fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.158s]
finished. total time: 0.158s
Yosemite-Sam:~ fritz$ fastboot flash zip rom.zip
error: cannot load 'rom.zip'
Yosemite-Sam:~ fritz$ fastboot flash zip rom.zip
error: cannot load 'rom.zip'
Yosemite-Sam:~ fritz$ fastboot reboot
rebooting...
finished. total time: 0.034s
Yosemite-Sam:~ fritz$
Click to expand...
Click to collapse
Yeah you didn't rename the file correctly
Sent from my HTC One using Tapatalk

clsA said:
Yeah you didn't rename the file correctly
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
care to offer a little more info?
"rom.zip" is what it's named on the phone.

metropical said:
care to offer a little more info?
"rom.zip" is what it's named on the phone.
Click to expand...
Click to collapse
why is it on the phone ?
we need to start from scratch
did you download the RUU.zip and is it in the same folder as fastboot / adb ?
did you rename the file rom.zip?
is your bootloader locked ?
what file did you download and rename to rom.zip?
what version of recovery do you have installed ?
when was the last time your phone actually worked ?

clsA said:
why is it on the phone ?
we need to start from scratch
did you download the RUU.zip and is it in the same folder as fastboot / adb ?
did you rename the file rom.zip?
is your bootloader locked ?
what file did you download and rename to rom.zip?
what version of recovery do you have installed ?
when was the last time your phone actually worked ?
Click to expand...
Click to collapse
ah ha!
on the phone. but I moved it to the proper folder on the computer.
not locked
the one you pointed to. The original is named what it should be. And renamed as you said.
no recovery installed.
2 days ago before I f'd up.
I have recovery_3.24.531.3_signed.img
and
recovery-twrp-2.7.0.0-m7.img
on the computer.
judging from your dialog the next step is to flash a recovery before the rom.zip?

metropical said:
ah ha!
on the phone. but I moved it to the proper folder on the computer.
not locked
the one you pointed to. The original is named what it should be. And renamed as you said.
no recovery installed.
2 days ago before I f'd up.
I have recovery_3.24.531.3_signed.img
and
recovery-twrp-2.7.0.0-m7.img
on the computer.
judging from your dialog the next step is to flash a recovery before the rom.zip?
Click to expand...
Click to collapse
no if the file is in the fastboot folder
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip << two times
fastboot reboot

clsA said:
no if the file is in the fastboot folder
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip << two times
fastboot reboot
Click to expand...
Click to collapse
still no joy. and now I've managed to lock my Bootloader and can't get it to unlock. cannot load …...
Yosemite-Sam:~ fritz$ fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.177s]
finished. total time: 0.177s
Yosemite-Sam:~ fritz$ fastboot flash zip rom.zip
error: cannot load 'rom.zip'
Yosemite-Sam:~ fritz$ fastboot flash zip rom.zip
error: cannot load 'rom.zip'
Yosemite-Sam:~ fritz$ fastboot reboot
rebooting...
finished. total time: 0.034s
Yosemite-Sam:~ fritz$

unlocked achieved but still no RUU
note that I had to use "cd" to get the Unlock_code.bin to load
but "cd" didn't work for the rom.zip
I do get to the white HTC logo on black each time.
I also tried to install with TWRP 2.7. and it failed twice as well.
Yosemite-Sam:~ fritz$ cd downloads/android
Yosemite-Sam:android fritz$ fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.003s]
finished. total time: 0.144s
Yosemite-Sam:android fritz$ fastboot devices
FA35YW901363 fastboot
Yosemite-Sam:android fritz$ fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.114s]
finished. total time: 0.114s
Yosemite-Sam:android fritz$ fastboot flash zip rom.zip
sending 'zip' (326528 KB)...
OKAY [ 14.550s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 53.453s
Yosemite-Sam:android fritz$ fastboot flash zip rom.zip
sending 'zip' (326528 KB)...
OKAY [ 14.596s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 53.498s
Yosemite-Sam:android fritz$ fastboot reboot
rebooting...
finished. total time: 0.034s
Yosemite-Sam:android fritz$
and if this is of any use:
Yosemite-Sam:~ fritz$ fastboot getvar all
(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: FAxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(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: 4326mV
(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

metropical said:
note that I had to use "cd" to get the Unlock_code.bin to load
but "cd" didn't work for the rom.zip
I do get to the white HTC logo on black each time.
I also tried to install with TWRP 2.7. and it failed twice as well.
Yosemite-Sam:~ fritz$ cd downloads/android
Yosemite-Sam:android fritz$ fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.003s]
finished. total time: 0.144s
Yosemite-Sam:android fritz$ fastboot devices
FA35YW901363 fastboot
Yosemite-Sam:android fritz$ fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.114s]
finished. total time: 0.114s
Yosemite-Sam:android fritz$ fastboot flash zip rom.zip
sending 'zip' (326528 KB)...
OKAY [ 14.550s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 53.453s
Yosemite-Sam:android fritz$ fastboot flash zip rom.zip
sending 'zip' (326528 KB)...
OKAY [ 14.596s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 53.498s
Yosemite-Sam:android fritz$ fastboot reboot
rebooting...
finished. total time: 0.034s
Yosemite-Sam:android fritz$
and if this is of any use:
Yosemite-Sam:~ fritz$ fastboot getvar all
(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: FAxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(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: 4326mV
(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
is your bootloader relocked ?
with s-on the bootloader must be locked/relocked to use the fastboot oem rebootRUU mode
also you can only flash a RUU.zip/rom.zip extracted from RUU, not a rom like viperOne

clsA said:
is your bootloader relocked ?
with s-on the bootloader must be locked/relocked to use the fastboot oem rebootRUU mode
also you can only flash a RUU.zip/rom.zip extracted from RUU, not a rom like viperOne
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=51702010
long story short. I found an early 2014 TWRP back-up. Rebuilt the TWRP directory with TWRP Back-up and dropped my 2014 back-up in place.
5 minutes and Restored to an operating phone.
Next step. My phone is as my sig shows. I would like to get the OTA of 4.4 KK.
How would I go about that?

metropical said:
http://forum.xda-developers.com/showthread.php?p=51702010
long story short. I found an early 2014 TWRP back-up. Rebuilt the TWRP directory with TWRP Back-up and dropped my 2014 back-up in place.
5 minutes and Restored to an operating phone.
Next step. My phone is as my sig shows. I would like to get the OTA of 4.4 KK.
How would I go about that?
Click to expand...
Click to collapse
getting the OTA involves using the RUU and then installing the OTA yourself
I did it myself, I installed the RUU
and the OTA file here >> http://www.filefactory.com/file/41y...3.24.531.3_release_351678n41r1lfticqo8m4c.zip
boot into recovery mode with stock recovery, hold power and volume up until you get a menu with options such as reboot, load from sdcard, load from phone storage, load from cache, etc. Choose load from phone storage and navigate to where you saved the zip.
Click to expand...
Click to collapse
so until you figure out how to install the RUU your pretty much stuck

different RUUs
locked bootloader again and tried the previous sequence you posted with the RUU you pointed to.
signature failed.
what is the difference between the rom.zip that you pointed to:
RUU_M7_UL_JB43_SENSE50_MR_TMOUS_3.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2.zip
and this one at HTC1guru?
RUU Zip M7 UL JB43 SENSE50 MR TMOUS 3.24.531.3 Radio 4A.21.3263.03 10.38m.1157.04 Release 336982 Signed 2 Decrypted
they are different sizes, so there must be some difference.

Trying to be helpful here.
When the bootloader is locked, or unlocked, the RUU will only install if the current firmware is equal or higher then the current installed version. If you want to downgrade firmware version the bootloader need to be S-OFF. However from your posts this seems not to be the case.
The firmware is a collective name for all partition versions on your phone. Lets say you bought it a year ago. It came out of the box with some version of the software installed. Then you installed a custom ROM which replaces the phones system and kernel. Now thats two of the 15+ firmware files already installed on your phone which have been updated but the rest is still lagging behind.
What you need to do in most cases is execute the fastboot command "fastboot getvar all" and check for your firmware version. When you have that sorted then go to, for example Android Revolutions website and download the stock rom for your firmware version. There are also other websites like htc1guru which provides stock ROM resets.
These ROMs will only reset your system and kernel to the same edition as the rest of your firmware and when all of them are the same you should be able to recieve Over The Air updates.

much clearer. thanks.
still S-On, not for trying though.
seems like the HTC1guru stocks won't help me.
ARHD has:
Download stock odexed 4.19.401.11
Download stock de-odexed 4.19.401.11
either or neither?
Yosemite-Sam:~ fritz$ fastboot getvar all
(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: FA35YW901xxx
(bootloader) imei: xxxxxxxxxxxxxxx
(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: 4319mV
(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
all: Done!

Softbrick HtcOne Need Someone To Help Please!!!!!!!!!!!!!!! SOLVED SOLVED

I have Htc One and i need help. I think that i am in softbrick. I unlocked bootloader with htc dev, then i rooted and flashed recovery and finaly flashed some rom. Now i have situation that i do not know what next. He is in boot loop and wont start up, so he is only restarting. My phone is S-on and on top i have Tampered and Unlocked signs.
I cannot go to recovery, phone just return me in first screen of bootloader.
I tried to flash recovery and same thing happens with error: "active cmdline overflow! (1025 Bytes)"
I tried to unlock it again through htc dev than flashing recovery and same thing.
In attachment is picture. Informations of phone are:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.10
(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: 4312mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I am not expert. I am noobie. I used fastboot with usually commands such as flash erase cache flash recovery, simple commands.
I need help to get back my phone and using it like all other people.
Can someone please help me?
Thanks in advance!

dowlabordere said:
I have Htc One and i need help. I think that i am in softbrick. I unlocked bootloader with htc dev, then i rooted and flashed recovery and finaly flashed some rom. Now i have situation that i do not know what next. He is in boot loop and wont start up, so he is only restarting. My phone is S-on and on top i have Tampered and Unlocked signs.
I cannot go to recovery, phone just return me in first screen of bootloader.
I tried to flash recovery and same thing happens with error: "active cmdline overflow! (1025 Bytes)"
I tried to unlock it again through htc dev than flashing recovery and same thing.
In attachment is picture. Informations of phone are:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.10
(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: 4312mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I am not expert. I am noobie. I used fastboot with usually commands such as flash erase cache flash recovery, simple commands.
I need help to get back my phone and using it like all other people.
Can someone please help me?
Thanks in advance!
Click to expand...
Click to collapse
Looks like you flashed something that is not ment for HTC One M7. Read this http://forum.xda-developers.com/showthread.php?t=2739126 and hope nkk can help you.
Can't think of a good sig

Have u flashed boot.img via fastboot? If not do so.

coolplay7 said:
Have u flashed boot.img via fastboot? If not do so.
Click to expand...
Click to collapse
It won't help him. Active cmdline overflow means he flashed wrong kernel which messed up his mmcblk0p19 partition. Only solution is to replace it with fixed one, but I'm not sure he can do that with s-on
Can't think of a good sig

dowlabordere said:
I have Htc One and i need help. I think that i am in softbrick. I unlocked bootloader with htc dev, then i rooted and flashed recovery and finaly flashed some rom. Now i have situation that i do not know what next. He is in boot loop and wont start up, so he is only restarting. My phone is S-on and on top i have Tampered and Unlocked signs.
I cannot go to recovery, phone just return me in first screen of bootloader.
I tried to flash recovery and same thing happens with error: "active cmdline overflow! (1025 Bytes)"
I tried to unlock it again through htc dev than flashing recovery and same thing.
In attachment is picture. Informations of phone are:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.10
(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: 4312mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I am not expert. I am noobie. I used fastboot with usually commands such as flash erase cache flash recovery, simple commands.
I need help to get back my phone and using it like all other people.
Can someone please help me?
Thanks in advance!
Click to expand...
Click to collapse
You are going to need this thread by @nkk71
You flashed the wrong rom for the device and messed the partitions
http://forum.xda-developers.com/showthread.php?t=2739126

mb_guy said:
You are going to need this thread by @nkk71
You flashed the wrong rom for the device and messed the partitions
http://forum.xda-developers.com/showthread.php?t=2739126
Click to expand...
Click to collapse
I said that first :victory:
Joking :laugh:

smee again
C:\adb>fastboot devices
SH*************** fastboot
C:\adb>fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img
target reported max download size of 1514139648 bytes
sending 'recovery' (11278 KB)...
OKAY [ 1.498s]
writing 'recovery'...
OKAY [ 0.952s]
finished. total time: 2.449s
C:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.390s]
finished. total time: 0.390s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
After this i tried to enter in recovery, and nothing. I tried next step adb devices and it should list my device but there is no my device.
C:\adb>adb devices
List of devices attached
I tried
C:\adb>adb shell dd if=/dev/block/mmcblk0p19 of=/tmp/mmcblk0p19_bak.img
error: device not found
What am i missing here ???????

donkeykong1 said:
I said that first :victory:
Joking :laugh:
Click to expand...
Click to collapse
C:\adb>fastboot devices
SH*************** fastboot
C:\adb>fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img
target reported max download size of 1514139648 bytes
sending 'recovery' (11278 KB)...
OKAY [ 1.498s]
writing 'recovery'...
OKAY [ 0.952s]
finished. total time: 2.449s
C:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.390s]
finished. total time: 0.390s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
After this i tried to enter in recovery, and nothing. I tried next step adb devices and it should list my device but there is no my device.
C:\adb>adb devices
List of devices attached
I tried
C:\adb>adb shell dd if=/dev/block/mmcblk0p19 of=/tmp/mmcblk0p19_bak.img
error: device not found
What am i missing here ???????

mb_guy said:
You are going to need this thread by @nkk71
You flashed the wrong rom for the device and messed the partitions
http://forum.xda-developers.com/showthread.php?t=2739126
Click to expand...
Click to collapse
C:\adb>fastboot devices
SH*************** fastboot
C:\adb>fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img
target reported max download size of 1514139648 bytes
sending 'recovery' (11278 KB)...
OKAY [ 1.498s]
writing 'recovery'...
OKAY [ 0.952s]
finished. total time: 2.449s
C:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.390s]
finished. total time: 0.390s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
After this i tried to enter in recovery, and nothing. I tried next step adb devices and it should list my device but there is no my device.
C:\adb>adb devices
List of devices attached
I tried
C:\adb>adb shell dd if=/dev/block/mmcblk0p19 of=/tmp/mmcblk0p19_bak.img
error: device not found
What am i missing here ???????

dowlabordere said:
C:\adb>fastboot devices
SH*************** fastboot
C:\adb>fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img
target reported max download size of 1514139648 bytes
sending 'recovery' (11278 KB)...
OKAY [ 1.498s]
writing 'recovery'...
OKAY [ 0.952s]
finished. total time: 2.449s
C:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.390s]
finished. total time: 0.390s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
After this i tried to enter in recovery, and nothing. I tried next step adb devices and it should list my device but there is no my device.
C:\adb>adb devices
List of devices attached
I tried
C:\adb>adb shell dd if=/dev/block/mmcblk0p19 of=/tmp/mmcblk0p19_bak.img
error: device not found
What am i missing here ???????
Click to expand...
Click to collapse
adb only works when your in custom recovery or booted to the OS

clsA said:
adb only works when your in custom recovery or booted to the OS
Click to expand...
Click to collapse
But how can i achieve it? I flashed but i can not enter.

dowlabordere said:
But how can i achieve it? I flashed but i can not enter.
Click to expand...
Click to collapse
Your problem is s-on. If you had s-off you could run 1.44 h-boot RUU and your phone would boot just fine. I don't know if you can do anything with s-on. Sorry to be barrer of bad news, but I think you have a brick
Can't think of a good sig

Please flash the firmware.zip for the 5.x.401.x
And try to enter stock recovery... See how it goes

SaHiLzZ said:
Please flash the firmware.zip for the 5.x.401.x
And try to enter stock recovery... See how it goes
Click to expand...
Click to collapse
I found some 5.x.401.x but down there someone bricked and someone resolved phone. And also they said that is only for s-on.
So my question SaHiLzZ is, can i brick it with flashing when i am s-on.
Somewhere i found that is impossible. I am full of informations and concerns!
Thanks in advance!

https://www.dropbox.com/s/jig0rs5349ljnqm/0ByQah9nMWV-qYWN1d2RxUHAxUFE.bin
Rename this to recovery and flash it via fastboot. If it works you will be able to flash ROM and boot your phone
Can't think of a good sig

dowlabordere said:
I found some 5.x.401.x but down there someone bricked and someone resolved phone. And also they said that is only for s-on.
So my question SaHiLzZ is, can i brick it with flashing when i am s-on.
Somewhere i found that is impossible. I am full of informations and concerns!
Thanks in advance!
Click to expand...
Click to collapse
I flashed it and nothing. Still can not enter recovery.

donkeykong1 said:
https://www.dropbox.com/s/jig0rs5349ljnqm/0ByQah9nMWV-qYWN1d2RxUHAxUFE.bin
Rename this to recovery and flash it via fastboot. If it works you will be able to flash ROM and boot your phone
Can't think of a good sig
Click to expand...
Click to collapse
Still nothing. Can not get into recovery. Fastboot see my devices, adb wont. Am I annoying?

dowlabordere said:
Still nothing. Can not get into recovery. Fastboot see my devices, adb wont. Am I annoying?
Click to expand...
Click to collapse
adb only works in recovery or to the booted up OS
why do you keep trying it in fastboot ?
can you copy / paste the results of flashing the firmware ?

clsA said:
adb only works in recovery or to the booted up OS
why do you keep trying it in fastboot ?
can you copy / paste the results of flashing the firmware ?
Click to expand...
Click to collapse
I don't want to be rude, but firmware won't help him. I had active cmdline overflow error and only thing that helped me was flashing 1.44 RUU, but I'm s-off. He can't flash that because he's s-on and on latest firmware. So, if that recovery I sent him didn't work he's in trouble because there is no RUU for him and firmware won't help him
Can't think of a good sig

clsA said:
adb only works in recovery or to the booted up OS
why do you keep trying it in fastboot ?
can you copy / paste the results of flashing the firmware ?
Click to expand...
Click to collapse
Sorry but i don't know where else to work with my phone except in fastboot. If i never played with telephone...
results of flashing the firmware are:
C:\Users\anek>cd..
C:\Users>cd..
C:\>cd adb
C:\adb>fastboot devices
SH************ fastboot
C:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.040s]
finished. total time: 0.041s
C:\adb>fastboot flash zip fw_5.11.401.10_custom_nored.zip
target reported max download size of 1514139648 bytes
sending 'zip' (25175 KB)...
OKAY [ 2.200s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 2.449s
C:\adb>fastboot flash zip fw_5.11.401.10_custom_nored.zip
target reported max download size of 1514139648 bytes
sending 'zip' (25175 KB)...
OKAY [ 2.200s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 2.449s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.031s
C:\adb>
And after reboot, the phone says "Process system isn't responding. Do you want to close it?"

[Q] Restart loop

Hi
I know this problem has shown up here before, and I've read through many threads on it on this forum, but I'm still very confused.
I have an HTC One M7 that my friend gave me to try to fix after bricking it. I'm not sure how he bricked it, as far as I know it was running stock system and he hasn't tried to flash it. As he has told me, the phone was working fine, and then suddenly broke.
Currently its stuck in a reboot loop. I can access the bootloader. It will not boot into recovery, choosing recovery mode triggers a reboot loop.
I tried unlocking the bootloader and installing TWRP recovery through fastboot, and it does the same thing.
I've also tried the suggestion of holding it under a light while holding the power button, and holding the power, volume up, and volume down buttons for a really long time as suggested at android.gs/unbrick-htc-one It didn't help.
The phone is from Telus (Canada), and has been carrier-unlocked. Model is PN07120.
I had a look at using the RUU.exe from htc1guru.com The forum won't let me link it, so look for
ruu_m7_ul_k44_sense55_mr_telus_wwe_4-19-661-8_r_radio_4t-24-3218-09_10-26-1718-01l_release_351500_signed_2-exe
for the one I used.
I also tried installing guru_reset_m7_3-22-661-1-zip/ from htc1guru.com's Stock Rom Guru Reset section, but got:
Code:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I guess there's the option of unzipping it and flashing the individual .img files, but I wasn't sure what to do with the rest of the files in that zip, and I didn't want to screw the phone up more, so I didn't touch it.
but so far the download has failed twice while trying to get the file. I'm trying again as I write this post, and if it fails, I'll go to my uni's library and try to download it on a better internet connection tomorrow. I'm also not sure if using this (or any) RUU is the right choice here.
The following is the information on the bootloader screen:
Code:
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OpenDSP-v32.120.274.0909
OS-5.11.661.8
The following is the output of fastboot getvar all (minus IMEI and serial)
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.661.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3854mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
Is there somewhere I can download stock firmware to flash to it aside from using the RUU if the download keeps failing? Anything else you need from me for diagnosis?
Any suggestions would be appreciated.

lnsulans said:
Hi
I know this problem has shown up here before, and I've read through many threads on it on this forum, but I'm still very confused.
I have an HTC One M7 that my friend gave me to try to fix after bricking it. I'm not sure how he bricked it, as far as I know it was running stock system and he hasn't tried to flash it. As he has told me, the phone was working fine, and then suddenly broke.
Currently its stuck in a reboot loop. I can access the bootloader. It will not boot into recovery, choosing recovery mode triggers a reboot loop.
I tried unlocking the bootloader and installing TWRP recovery through fastboot, and it does the same thing.
I've also tried the suggestion of holding it under a light while holding the power button, and holding the power, volume up, and volume down buttons for a really long time as suggested at android.gs/unbrick-htc-one It didn't help.
The phone is from Telus (Canada), and has been carrier-unlocked. Model is PN07120.
I had a look at using the RUU.exe from htc1guru.com The forum won't let me link it, so look for
ruu_m7_ul_k44_sense55_mr_telus_wwe_4-19-661-8_r_radio_4t-24-3218-09_10-26-1718-01l_release_351500_signed_2-exe
for the one I used.
I also tried installing guru_reset_m7_3-22-661-1-zip/ from htc1guru.com's Stock Rom Guru Reset section, but got:
Code:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I guess there's the option of unzipping it and flashing the individual .img files, but I wasn't sure what to do with the rest of the files in that zip, and I didn't want to screw the phone up more, so I didn't touch it.
but so far the download has failed twice while trying to get the file. I'm trying again as I write this post, and if it fails, I'll go to my uni's library and try to download it on a better internet connection tomorrow. I'm also not sure if using this (or any) RUU is the right choice here.
The following is the information on the bootloader screen:
Code:
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OpenDSP-v32.120.274.0909
OS-5.11.661.8
The following is the output of fastboot getvar all (minus IMEI and serial)
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.661.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3854mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
Is there somewhere I can download stock firmware to flash to it aside from using the RUU if the download keeps failing? Anything else you need from me for diagnosis?
Any suggestions would be appreciated.
Click to expand...
Click to collapse
That RUU is a downgrade so can only be used if the device is s-off. To get s-off you require a stable stock Rom so your gonna need to get a recovery working before you can do anything else.
Recovery bootloops are normally caused by dirty cache from a different recovery. Do you erase cache after flashing the TWRP recovery?
So let's start with the most reliable version of TWRP http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
Download this and drop the file in your fastboot folder. Boot to the bootloader and flash the recovery with the following commands
Code:
fastboot erase cache
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot reboot-bootloader
Now select recovery from the bootloader menu and hopefully it should boot to TWRP recovery :good:

Danny201281 said:
<stuff about recovery mode>
Click to expand...
Click to collapse
Code:
macbook:~ andrew$ fastboot erase cache
erasing 'cache'...
OKAY [ 0.057s]
finished. total time: 0.057s
macbook~ andrew$ fastboot flash recovery /Users/andrew/Downloads/openrecovery-twrp-2.6.3.3-m7.img
sending 'recovery' (9184 KB)...
OKAY [ 1.134s]
writing 'recovery'...
OKAY [ 0.702s]
finished. total time: 1.836s
macbook:~ andrew$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.035s]
finished. total time: 0.035s
Then I selected recovery from bootlaoder menu. Result is it shows the htc splash screen, shows "Entering Recovery...." at the top for a minute or so, and then it kicks back into the restart loop.
In addition, the phone doesn't stay turned off. I selected power off from the fastboot menu, and it stays off for a bit, then starts back into the restart loop.

lnsulans said:
Code:
macbook:~ andrew$ fastboot erase cache
erasing 'cache'...
OKAY [ 0.057s]
finished. total time: 0.057s
macbook~ andrew$ fastboot flash recovery /Users/andrew/Downloads/openrecovery-twrp-2.6.3.3-m7.img
sending 'recovery' (9184 KB)...
OKAY [ 1.134s]
writing 'recovery'...
OKAY [ 0.702s]
finished. total time: 1.836s
macbook:~ andrew$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.035s]
finished. total time: 0.035s
Then I selected recovery from bootlaoder menu. Result is it shows the htc splash screen, shows "Entering Recovery...." at the top for a minute or so, and then it kicks back into the restart loop.
In addition, the phone doesn't stay turned off. I selected power off from the fastboot menu, and it stays off for a bit, then starts back into the restart loop.
Click to expand...
Click to collapse
Strange, it might be a firmware problem. Try to flash the stock firmware then reflash twrp 2.6.3.3.
You can extract the stock firmware for your version from this file: https://www.androidfilehost.com/?fid=23487008491962497.
Open the zip file, inside is another zip file (firmware.zip). take that file and move it to you adb/fastboot folder. With the phone in bootloader mode/fastboot usb:
Code:
fastboot oem lock
(s-on phone must be locked/relocked to flash firmware)
Code:
fastboot oem rebootRUU
^^case sensitive
The phone will now reboot in RUU mode, you'll see a black screen with a silver HTC logo. then:
Code:
fastboot flash zip firmware.zip
first flash will report: "failed, flush again immediately!" so go ahead with the same command:
fastboot flash zip firmware.zip
Click to expand...
Click to collapse
Make sure the flash was successful from the output of the command prompt. The green progress bar might not indicate 100% on the phone but its not a problem as long as fastboot reported that everything was okay.
and then reboot in bootloader mode:
Code:
fastboot reboot-bootloader
and finally, retry to flash twrp 2.6.3.3 (re-unlock your bootloader again before flashing twrp)
Code:
fastboot flash recovery twrp.img
fastboot erase cache
fastboot reboot-bootloader
and if it worked, you could than restore the stock rom from twrp using this file: https://www.androidfilehost.com/?fid=23487008491964358

alray said:
Strange, it might be a firmware problem. Try to flash the stock firmware then reflash twrp 2.6.3.3.
You can extract the stock firmware for your version from this file: <removed as forum won't let me post links> Open the zip file, inside is another zip file (firmware.zip). take that file and move it to you adb/fastboot folder. With the phone in bootloader mode/fastboot usb:
Code:
fastboot oem lock
(s-on phone must be locked/relocked to flash firmware)
Code:
fastboot oem rebootRUU
^^case sensitive
The phone will now reboot in RUU mode, you'll see a black screen with a silver HTC logo. then:
Code:
fastboot flash zip firmware.zip
first flash will report: "failed, flush again immediately!" so go ahead with the same command:
Make sure the flash was successful from the output of the command prompt. The green progress bar might not indicate 100% on the phone but its not a problem as long as fastboot reported that everything was okay.
and then reboot in bootloader mode:
Code:
fastboot reboot-bootloader
and finally, retry to flash twrp 2.6.3.3 (re-unlock your bootloader again before flashing twrp)
Code:
fastboot flash recovery twrp.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Tried this, doesn't work.
Code:
amp:~ andrew$ fastboot oem lock
ERROR: could not get pipe properties
...
(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.
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 1.152s
amp:~ andrew$ fastboot oem rebootRUU
ERROR: could not get pipe properties
...
(bootloader) Start Verify: 3
OKAY [ 0.044s]
finished. total time: 0.045s
amp:~ andrew$ fastboot flash zip /Users/andrew/Desktop/OTA_M7_UL_K44_SENSE60_MR_TELUS_WWE_5.11.661.8-4.19.661.8_R_release_370058e1o26e71c5xckuu3.zip
ERROR: could not get pipe properties
sending 'zip' (684644 KB)...
OKAY [ 28.174s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 81.426s
amp:~ andrew$ fastboot flash zip /Users/andrew/Desktop/OTA_M7_UL_K44_SENSE60_MR_TELUS_WWE_5.11.661.8-4.19.661.8_R_release_370058e1o26e71c5xckuu3.zip
ERROR: could not get pipe properties
sending 'zip' (684644 KB)...
OKAY [ 26.648s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 79.900s
amp:~ andrew$
Suggestions? Thanks.

lnsulans said:
Tried this, doesn't work.
Code:
amp:~ andrew$ fastboot oem lock
ERROR: could not get pipe properties
...
(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.
[COLOR="Red"]ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))[/COLOR]
finished. total time: 1.152s
amp:~ andrew$ fastboot oem rebootRUU
[COLOR="red"]ERROR: could not get pipe properties[/COLOR]
...
(bootloader) Start Verify: 3
OKAY [ 0.044s]
finished. total time: 0.045s
amp:~ andrew$ fastboot flash zip /Users/andrew/Desktop/[COLOR="red"]OTA_M7_UL_K44_SENSE60_MR_TELUS_WWE_5.11.661.8-4.19.661.8_R_release_370058e1o26e71c5xckuu3.zip [/COLOR] [COLOR="DarkOrange"]--> I said extract the firmware.zip from the ota and flash it[/COLOR]
[COLOR="red"]ERROR: could not get pipe properties[/COLOR]
sending 'zip' (684644 KB)...
OKAY [ 28.174s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 81.426s
amp:~ andrew$ fastboot flash zip /Users/andrew/Desktop/OTA_M7_UL_K44_SENSE60_MR_TELUS_WWE_5.11.661.8-4.19.661.8_R_release_370058e1o26e71c5xckuu3.zip
ERROR: could not get pipe properties
sending 'zip' (684644 KB)...
OKAY [ 26.648s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail) [COLOR="DarkOrange"] ---> this is because you are not flashing firmware.zip but the ota....[/COLOR]
finished. total time: 79.900s
amp:~ andrew$
Suggestions? Thanks.
Click to expand...
Click to collapse
you should retry but read again my previous post, your are not doing what I have explained...
You can extract the stock firmware for your version from this file: https://www.androidfilehost.com/?fid=23487008491962497.
Click to expand...
Click to collapse
Code:
fastboot flash zip firmware.zip [COLOR="Red"]---> never said to flash the ota, extract the firmware,zip from the ota.zip and flash the firmware.zip[/COLOR]
Click to expand...
Click to collapse
So extract the firmware.zip from the ota and flash it in ruu mode, not the ota itself.
And its also looks like you are having USB issue (ERROR: could not get pipe properties)

HELP! One mini 2 can't unlock bootloader doesn't show splash screen

Okay lots of issues hopefully one easy fix,
I have had a HOM2 given to me to fix for my friend so just want it back to stock , it has no radios it mentions invalid_ver_* , same for another option, the bootloader is LOCKED here is my getvar info
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH466WR01102
(bootloader) imei: 35***********
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: mem_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P8B20000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: be7179e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
, its bootlooping into bootloader, so my first thought was unlock bootloader flash recovery and side load a rom, play with radios and such after, but trying to unlock the bootloader doesn't work I've tried HTC dev twice to check the unlock code but it pushes it to the device and claims it was successful I get this;
**UNLOCK CODE***
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.109s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.016s]
finished. total time: 0.125ss
tried different USB cables and ports but every time I try I don't get the unlock splash screen asking me to unlock, so I went through the forums and tried a few things found that clearing cache or and data gives me
**CLEAR CACHE***
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 5.038ss
I tried flashing recovery (just for kicks) I get
***SEND RECOVERY***
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery-twrp-2.8.5.0.img
sending 'recovery' (11796 KB)...
OKAY [ 10.472s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 11.316sss
Which I guess is to be expected,
I then found an RUU for the device and was thankful the unlocking didn't work so I was still locked, but every one I try to download is corrupt? Anybody have a working link for a UK ee (orange) radios and firmware? And do I have the right idea with this, download, rename, chuck it on an sdcard and bootloader should find it automatically?
Thanks for any advice

martipello86 said:
Okay lots of issues hopefully one easy fix,
I have had a HOM2 given to me to fix for my friend so just want it back to stock , it has no radios it mentions invalid_ver_* , same for another option, the bootloader is LOCKED
Click to expand...
Click to collapse
Since the phone was given to you, Are you using an original HTC cable???? you need that for any flashing to work.

Yes I have an original HTC cable,

martipello86 said:
Yes I have an original HTC cable,
Click to expand...
Click to collapse
kativiti said:
Since the phone was given to you, Are you using an original HTC cable???? you need that for any flashing to work.
Click to expand...
Click to collapse
I have the original cable, just does not want to work, and the RUU says its corrupt when I try to put it on the SD card

kativiti said:
Since the phone was given to you, Are you using an original HTC cable???? you need that for any flashing to work.
Click to expand...
Click to collapse
i found a way to get the ruu onto the sdcard by uploading the file to dropbox and redownloading it straight to the memory card then stuck it in the phone tried an orange ruu it gets half way through updating then stops and spits out a message to say its not the right cid so i got the wwe version that looks like itll work but then fails and tells me 'MAIN VERSION IS OLDER' update failed.
ANY IDEAS WELCOME!!!!!!!