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

HELP - Restore HTC One (M7) to Stock ROM

Hey guys, What's up?
Some months ago, my friend suggested that he can upgrade my phone to Lollipop and instal another ROM...after that, my phone is so so buggy! It's always crashing, constantly rebooting and many others problems.
So, I decided to go back to the Stock ROM, but it's seems a little difficult to me.
Can anyone please help me get my phone back to Stock ROM?
Tell me what to do first and help me find the right files for my phone?
Here it's the info about my phone:
C:\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA362W900989
(bootloader) imei: 354436052980347
(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: 3848mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Thanks alot!!!

EliSoares said:
Hey guys, What's up?
Some months ago, my friend suggested that he can upgrade my phone to Lollipop and instal another ROM...after that, my phone is so so buggy! It's always crashing, constantly rebooting and many others problems.
So, I decided to go back to the Stock ROM, but it's seems a little difficult to me.
Can anyone please help me get my phone back to Stock ROM?
Tell me what to do first and help me find the right files for my phone?
Here it's the info about my phone:
Thanks alot!!!
Click to expand...
Click to collapse
Flashing the 7.19.401.51 RUU will bring your phone back to stock
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
follow instructions from post #1
RUU at post #2

alray said:
Flashing the 7.19.401.51 RUU will bring your phone back to stock
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
follow instructions from post #1
RUU at post #2
Click to expand...
Click to collapse
Hey! Thanks!!!
I'm trying do flash, but appears this error:
FAIL02 data length is too large
FAILED (data size is too large(1641983 KB) for device to download ZIP file 'RUU.
zip'
Click to expand...
Click to collapse
What i have to do ?

EliSoares said:
Hey! Thanks!!!
I'm trying do flash, but appears this error:
What i have to do ?
Click to expand...
Click to collapse
Make sure you are using the fastboot version provided by the OP and that you are using the signed version of 7.19.401.51 not the decrypted one.

Hi,
I bought the HTC One M7 from other person, I found the Software Information is:
- Android Version: 5.0.2
- HTC Sense Version: 6.0
- Software number: ViperOne 8.0.0
When I check the my bootloader variable is show below
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: SH39WW903924
(bootloader) imei: 35786**********
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4305mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
How can I turn to the Stock ROM? Because of the the orginal "cidnum" was changed, so how to find the right Stock ROM with my device?
Please help me.
Thank you very much

NomercyB said:
Hi,
I bought the HTC One M7 from other person, I found the Software Information is:
- Android Version: 5.0.2
- HTC Sense Version: 6.0
- Software number: ViperOne 8.0.0
When I check the my bootloader variable is show below
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: SH39WW903924
(bootloader) imei: 35786**********
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4305mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
How can I turn to the Stock ROM? Because of the the orginal "cidnum" was changed, so how to find the right Stock ROM with my device?
Please help me.
Thank you very much
Click to expand...
Click to collapse
You can pretty much use any RUU you'd like to brink it back to stock, just make sure the MID match the RUU. If you really need it to be on the same exact rom it came with, for an obscure reason, you canf ind the original CID stored on the MFG partition. You'll need to dump the MFG to your computer and explore it using HxD. Or simply flash the 7.19.401.51 RUU

CID stored on the MFG partition
alray said:
You can pretty much use any RUU you'd like to brink it back to stock, just make sure the MID match the RUU. If you really need it to be on the same exact rom it came with, for an obscure reason, you canf ind the original CID stored on the MFG partition. You'll need to dump the MFG to your computer and explore it using HxD. Or simply flash the 7.19.401.51 RUU
Click to expand...
Click to collapse
Thank you very @alray.
As you know I am a newbie on this issue, so I really don't know how to find CID stored on the MFG partition.
Could you give me your hand to how to find it?
Thank you.

NomercyB said:
Thank you very @alray.
As you know I am a newbie on this issue, so I really don't know how to find CID stored on the MFG partition.
Could you give me your hand to how to find it?
Thank you.
Click to expand...
Click to collapse
From a rooted rom or from a custom recovery execute theses commands:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6_bakup.img
exit
then copy mmcblk0p6_backup.img from your sdcard to your computer and open it with HxD, look at position 1209C

position 1209C
alray said:
From a rooted rom or from a custom recovery execute theses commands:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6_bakup.img
exit
then copy mmcblk0p6_backup.img from your sdcard to your computer and open it with HxD, look at position 1209C
Click to expand...
Click to collapse
Sorry, sir @alray I don't know how to find the position 1209C. When I press F3 on HxD and find the the 1209C it couldn't find, maybe I don't know how to find it, how should I do?

NomercyB said:
Sorry, sir @alray I don't know how to find the position 1209C. When I press F3 on HxD and find the the 1209C it couldn't find, maybe I don't know how to find it, how should I do?
Click to expand...
Click to collapse
scroll down to offset 12090 and then look at column 0C. That's the first byte of your original CID, most likely x48 for the letter "H" if your phone had a common CID (ie starting with HTC__)
Just after that, at 120AB you can find your MID.
btw you would be fine with 7.19.401.51, just saying again...

mmcblk0p6_bakup.img
alray said:
From a rooted rom or from a custom recovery execute theses commands:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6_bakup.img
exit
then copy mmcblk0p6_backup.img from your sdcard to your computer and open it with HxD, look at position 1209C
Click to expand...
Click to collapse
alray said:
scroll down to offset 12090 and then look at column 0C. That's the first byte of your original CID, most likely x48 for the letter "H" if your phone had a common CID (ie starting with HTC__)
Just after that, at 120AB you can find your MID.
btw you would be fine with 7.19.401.51, just saying again...
Click to expand...
Click to collapse
Thank you so much for you kindly guide me. My mmcblk0p6_bakup.img couldn't find the number 12090 as you mentioned.
Anyway, I downloaded Stock ROM Version 7.19.401.51, If I flash it my mobile can receive OTA update?

Flash Stock ROM 7.19.401.51
alray said:
scroll down to offset 12090 and then look at column 0C. That's the first byte of your original CID, most likely x48 for the letter "H" if your phone had a common CID (ie starting with HTC__)
Just after that, at 120AB you can find your MID.
btw you would be fine with 7.19.401.51, just saying again...
Click to expand...
Click to collapse
When I flash Stock ROM 7.19.401.51 I found the message below:
F:\HTC\HTCOneRoot\fastboot_adb(1.0.32)_071114_r21>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.043s]
finished. total time: 0.044s
F:\HTC\HTCOneRoot\fastboot_adb(1.0.32)_071114_r21>fastboot flash zip RUU.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 165469715 is not a multiple of the block size 4096
sending sparse 'zip' (1478649 KB)...
error: write_sparse_skip_chunk: don't care size 165469715 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 165469715 is not a multiple of the block size 4096
OKAY [ 58.964s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 59.169s
F:\HTC\HTCOneRoot\fastboot_adb(1.0.32)_071114_r21>fastboot reboot
rebooting...
finished. total time: 0.036s
How should I do?

NomercyB said:
Thank you so much for you kindly guide me. My mmcblk0p6_bakup.img couldn't find the number 12090 as you mentioned.
Anyway, I downloaded Stock ROM Version 7.19.401.51, If I flash it my mobile can receive OTA update?
Click to expand...
Click to collapse
Ota update? Device reached EOL Last year. 7.19.401.51 is the final version. I wouldnt expect any update but if there is one, yes youll be able to install it.
NomercyB said:
When I flash Stock ROM 7.19.401.51 I found the message below:
F:\HTC\HTCOneRoot\fastboot_adb(1.0.32)_071114_r21>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.043s]
finished. total time: 0.044s
F:\HTC\HTCOneRoot\fastboot_adb(1.0.32)_071114_r21>fastboot flash zip RUU.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 165469715 is not a multiple of the block size 4096
sending sparse 'zip' (1478649 KB)...
error: write_sparse_skip_chunk: don't care size 165469715 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 165469715 is not a multiple of the block size 4096
OKAY [ 58.964s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 59.169s
F:\HTC\HTCOneRoot\fastboot_adb(1.0.32)_071114_r21>fastboot reboot
rebooting...
finished. total time: 0.036s
How should I do?
Click to expand...
Click to collapse
You must use htc_fastboot.exe to flash the ruu, not the regular version from Google.

Flash Stock ROM 7.19.401.51
alray said:
Ota update? Device reached EOL Last year. 7.19.401.51 is the final version. I wouldnt expect any update but if there is one, yes youll be able to install it.
You must use htc_fastboot.exe to flash the ruu, not the regular version from Google.
Click to expand...
Click to collapse
Thank you very much for your good suggestion, I tried many times for flashing but it's not complete, I also used htc_fastboot.exe. Maybe it happens with my Windows OS.
I try again with Windows OS that is lower than Windows 10 Enterprise 64 bit.

NomercyB said:
Thank you very much for your good suggestion, I tried many times for flashing but it's not complete, I also used htc_fastboot.exe. Maybe it happens with my Windows OS.
I try again with Windows OS that is lower than Windows 10 Enterprise 64 bit.
Click to expand...
Click to collapse
With Hboot 1.57 windows 10 shouldn't be a problem, only if you were on hboot 1.44.
Can you copy/paste the output of your command windows after executing "fastboot flash zip ruu.zip" so I can see why it's failing...

Same problem
alray said:
With Hboot 1.57 windows 10 shouldn't be a problem, only if you were on hboot 1.44.
Can you copy/paste the output of your command windows after executing "fastboot flash zip ruu.zip" so I can see why it's failing...
Click to expand...
Click to collapse
I still face the same problem when I flash RUU.zip from the original file "PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_unsigned.zip". It shows the error message:
C:\HTC FASTBOOT>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.043s]
finished. total time: 0.044s
C:\HTC FASTBOOT>fastboot flash zip ruu.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 167235091 is not a multiple of t
he block size 4096
sending sparse 'zip' (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 167235091 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 167235091 is not a multiple of t
he block size 4096
OKAY [ 93.787s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 93.991s
C:\HTC FASTBOOT>fastboot reboot-bootloader
Please help me to find out the problem.
Thank you very much

NomercyB said:
I still face the same problem when I flash RUU.zip from the original file "PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_unsigned.zip". It shows the error message:
C:\HTC FASTBOOT>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.043s]
finished. total time: 0.044s
C:\HTC FASTBOOT>fastboot flash zip ruu.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 167235091 is not a multiple of t
he block size 4096
sending sparse 'zip' (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 167235091 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 167235091 is not a multiple of t
he block size 4096
OKAY [ 93.787s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 93.991s
C:\HTC FASTBOOT>fastboot reboot-bootloader
Please help me to find out the problem.
Thank you very much
Click to expand...
Click to collapse
Might want to try to signed version? Not sure why you are trying to flash this one.

alray said:
Might want to try to signed version? Not sure why you are trying to flash this one.
Click to expand...
Click to collapse
I will try to use signed version from you suggestion. You want to know why I am trying to use this one. Because I could not find out the original CID number and you ever suggested me to use 7.19.401.51 RUU, so I downloaded 7.19.401.51 RUU to flash my rom to restore to the stock ROM.
Okay, if you have any good solution to suggest me please help me to the stock ROM. The reason why I try to return to stock rom because my phone flashed with viper rom and now WIFI signal is stuck on "Turning WIFI on" then give the error message.
That's why, I would like to return to stock rom.
---------- Post added at 04:00 AM ---------- Previous post was at 03:01 AM ----------
alray said:
Might want to try to signed version? Not sure why you are trying to flash this one.
Click to expand...
Click to collapse
I tried with signed version but it still show the error as the message below
C:\HTC FASTBOOT>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.109s]
finished. total time: 0.109s
C:\HTC FASTBOOT>fastboot flash zip ruu.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 174325923 is not a multiple of t
he block size 4096
sending sparse 'zip' (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 174325923 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 174325923 is not a multiple of t
he block size 4096
OKAY [106.361s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 106.564s
C:\HTC FASTBOOT>fastboot reboot
rebooting...
finished. total time: 0.109s
Please help me.
Thanks.

Guidance needed (S-OFF, SIM unlock)

I've got an HTC One M7 on EE in the UK (was TMobile I think originally).
I flashed it with LineageOS, which seemed to work great except it didn't recognise the SIM card. I gather I'll need to S-OFF it first to unlock the SIM? And that Sunshine is the way to go for my 1.61 hboot version.
Despite flashing with a stock ROM though Sunshine's test complains the kernel or ROM aren't close enough to stock. Any ideas? Thanks in advance.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.61.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxx
(bootloader) imei: xxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4194mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

This is the stock RUU I've tried.
M7 CWM Nandroid Backup CID ORANG001 2.24.61.1

htconer said:
This is the stock RUU I've tried.
M7 CWM Nandroid Backup CID ORANG001 2.24.61.1
Click to expand...
Click to collapse
This file is not a RUU, it's a cwm backup and it's also way to old to fit your device.
I know 3 methods to sim-unlock,
1-the first one consist of entering the sim unlock code (you must purchase one) when booting the phone. The foreign sim card must be inserted to be prompted to enter the code, the phone must also run a stock (or close to stock) rom.
2- Sieempi's method, requires S-OFF and some hardware (external hard drive, usb otg y-cable, 5v power source)
3- Sunshine experimental sim-unlock, not really sure if it's working, never heard about anyone using this method.
The lastest RUU version I was able to find for your phone is 7.19.61.10 and since your version-main is higher than that you'll either need s-off to flash it or to edit your version-main in your misc partition.
https://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
RUU at post #2 of that thread, instructions how to edit your version-main at the end of post #2. Instructions how to flash ruu at post #1

Thanks.
Sounds like you'd suggest putting a foreign SIM in and getting an unlock code over Sunshine then? I guess if I can pass the Sunshine checks though I'll be in a better place for doing that.
The version-main change seems to have worked. Haven't been able to flash the RUU though, am I doing something wrong?
Code:
$ fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.235s]
finished. total time: 0.235s
$ fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_Orange_UK_7.19.61.10_Radio_4T.35.3218.16_10.33Q.1718.01L_release_428118_signed.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 184138016 is not a multiple of the block size 4096
sending sparse 'zip' 1/2 (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 184138016 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 184138016 is not a multiple of the block size 4096
OKAY [ 60.996s]
writing 'zip' 1/2...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 202.278s
I've tried running the flash zip command multiple times. Thought it sounded like a file corruption issue, but the MD5 seems ok to me.
Code:
$ md5 PN07IMG_M7_UL_L50_SENSE60_MR_Orange_UK_7.19.61.10_Radio_4T.35.3218.16_10.33Q.1718.01L_release_428118_signed.zip
MD5 (PN07IMG_M7_UL_L50_SENSE60_MR_Orange_UK_7.19.61.10_Radio_4T.35.3218.16_10.33Q.1718.01L_release_428118_signed.zip) = 95a5ad2186235bc346d55ef9d8530dce

htconer said:
Thanks.
Sounds like you'd suggest putting a foreign SIM in and getting an unlock code over Sunshine then? I guess if I can pass the Sunshine checks though I'll be in a better place for doing that.
The version-main change seems to have worked. Haven't been able to flash the RUU though, am I doing something wrong?
Code:
$ fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.235s]
finished. total time: 0.235s
$ fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_Orange_UK_7.19.61.10_Radio_4T.35.3218.16_10.33Q.1718.01L_release_428118_signed.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 184138016 is not a multiple of the block size 4096
sending sparse 'zip' 1/2 (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 184138016 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 184138016 is not a multiple of the block size 4096
OKAY [ 60.996s]
writing 'zip' 1/2...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 202.278s
Click to expand...
Click to collapse
Answer to your question is written in red in the instructions/post #1 of the RUU collection thread
You can buy a sim unlock code online for less than 10$ if you don't want to s-off with Sunshine.

Ah. Bit slow getting used to the expanding bits on this forums posts. Guess I need htc_fastboot.exe then?
Unfortunately, sort of, I don't have a Windows machine or know anyone with one I can borrow and the htc fastboot for mac complains the file is too big.

Rom by fastboot?

Hi
I have a problem because i did wipe system for some reasons and now my m7 stuck in bootloop (htc logo)
adb doesnt work (pc doesnt see my phone), fastboot works
is there any posiblity to install system without adb only fastboot?
i have s-off and twrp-3.0.0-2-m7
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

piechu15 said:
Hi
I have a problem because i did wipe system for some reasons and now my m7 stuck in bootloop (htc logo)
adb doesnt work (pc doesnt see my phone), fastboot works
is there any posiblity to install system without adb only fastboot?
i have s-off and twrp-3.0.0-2-m7
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
adb will only work from a custom recovery or from a booted rom, not in the bootloader. Use twrp to flash a rom or flash a ruu using fastboot.

alray said:
adb will only work from a custom recovery or from a booted rom, not in the bootloader. Use twrp to flash a rom or flash a ruu using fastboot.
Click to expand...
Click to collapse
thanks, but my adb doesnt work for a long time and i cant push any file to memory
otg doesnt work too.
I tired to use fastboot to flash ruu but something is wrong
D:\Android\sdk\platform-tools>fastboot flash zip C:\Users\Karol\Downloads\PN07IM
G_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01
L_release_458803_unsigned.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 167243283 is not a multiple of t
he block size 4096
sending sparse 'zip' 1/2 (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 167243283 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 167243283 is not a multiple of t
he block size 4096
OKAY [ 66.451s]
writing 'zip' 1/2...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 230.729s

piechu15 said:
thanks, but my adb doesnt work for a long time and i cant push any file to memory
otg doesnt work too.
I tired to use fastboot to flash ruu but something is wrong
D:\Android\sdk\platform-tools>fastboot flash zip C:\Users\Karol\Downloads\PN07IM
G_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01
L_release_458803_unsigned.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 167243283 is not a multiple of t
he block size 4096
sending sparse 'zip' 1/2 (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 167243283 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 167243283 is not a multiple of t
he block size 4096
OKAY [ 66.451s]
writing 'zip' 1/2...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 230.729s
Click to expand...
Click to collapse
If fastboot commands are working but not adb, you have a driver problem. Make sure you have the latest version installed. ADB sideload can sometime be less reliable than using the old adb push method. If you have a recent TWRP version installed, you shouldn't even have to use adb push or adb sideload to transfer the rom to your phone since the recovery is now taking advantage of the MTP protocol (you should see your phone storage, like a usb drive, when the phone is booted in recovery).
Flashing a Lollipop RUU (version starting with 7.xx.xxx.x) requires the use of htc_fastboot.exe. The regular fastboot.exe from the android sdk tools can't handle the 7.xx.xxx.x RUU because of the file size. You can find the correct fastboot version in the ruu collection thread (linked in my signature) at post #1 under the "How to flash" spoiler or search for "htc_fastboot.exe" on androidfilehost.com

alray said:
If fastboot commands are working but not adb, you have a driver problem. Make sure you have the latest version installed. ADB sideload can sometime be less reliable than using the old adb push method. If you have a recent TWRP version installed, you shouldn't even have to use adb push or adb sideload to transfer the rom to your phone since the recovery is now taking advantage of the MTP protocol (you should see your phone storage, like a usb drive, when the phone is booted in recovery).
Click to expand...
Click to collapse
Yes I think the same, it is driver problem. But in my opinion it is problem with the phone drivers.
I tired to connect my m7 to 4 diffrent pc with cables which works good with diffrent phones.
I changed usb port to the new too but still the same, any pc doesnt see my htc.
alray said:
Flashing a Lollipop RUU (version starting with 7.xx.xxx.x) requires the use of htc_fastboot.exe. The regular fastboot.exe from the android sdk tools can't handle the 7.xx.xxx.x RUU because of the file size. You can find the correct fastboot version in the ruu collection thread (linked in my signature) at post #1 under the "How to flash" spoiler or search for "htc_fastboot.exe" on androidfilehost.com
Click to expand...
Click to collapse
which wersion of RUU i should install?
i thought that 7.19.401.2 should work but it isnt.
D:\Android\sdk\platform-tools>fastboot2 flash zip RUU.zip
sending 'zip'... (43286 KB) OKAY
sending time = 3.121 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 10(s)
== edit
Ok, i managed to flash the ruu
I had to relock bootloader previously.
Thanks for the help @alray

Htc one (m7) can not boot anymore

Hello,
as you already mentioned from the title, my old Phone isnt able to boot anymore.
It all started with that I did a factory reset in my phone settings. I had a custom rom installed (ViperOne...)
after that my phone was able to start and I selected all the settings that u get asked at the start of every new reset.
But my phone wasnt able to complete it all. After I finished it up the process always stoped working.
So I decided to get into the bootloader and clean up everything in there. Now im stuck at the HTC Logo.
Information about my Device: Bootloader is unlocked (now it says "Relocked");
Fastboot should be activated; S-ON;
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH35TW900451
(bootloader) imei: 354436059098929
(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: 4052mV
(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
I dont have a backup file for my phone, but I put the latest ViperOne+ update on my phone (I can install it via recovery but it isnt working either)
If I type in "fastboot oem rebootRUU" in the ADB & Fastboot cmd it brings me up to another logo (working perfectly)
but when I wanna flash the firmware on it. It doesnt work at all.
fastboot flash zip firmware.zip
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 162706427 is not a multiple of the block size 4096
sending sparse 'zip' 1/2 (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 162706427 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 162706427 is not a multiple of the block size 4096
OKAY [ 54.330s]
writing 'zip' 1/2...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 218.103s
here it just says signature verify fail...
I even downloaded another firmware and it was the same problem.
Hopefully I didnt miss any Information about my Phone.
It would be really great if you guys can help me. I wouldnt do this post If I havent tried so much
btw. sry for my bad english hehe

If you want to flash a custom rom you must unlock bootloader and flash twrp.
custom roms can be flashed only from twrp.
If you want to revert to stock, this is the right ruu for your m7: https://androidfilehost.com/?fid=962021903579482012

okay thank you very much, this was more than helpful!
yes I want to install a custom rom. I was able to install twrp. But I dont know how to proceed now.
Should I install the custom rom with the cmd or just going into bootloader and select it on my phone to install ?
//edit: just went into the factory restore settings in the bootloader and twrp showed up - trying to install my custom rom now with it.
My phone is now showing up on my pc hehe
//edit²: Android is upgrading - guess its working
Thank you very much