I have a HTC M8 HK edition that I havn't picked up in quite some time, now to be my daily driver. It's on Android 4.4.2, and firmware version 1.54.654.13 (Sense 6.0). Last I picked it up, I unlocked the bootloader and rooted it. Since then I've also toggled S-Off and gotten TWRP (version 3.0.2) installed as recovery. All that being said, I am unfamiliar with the nuances of upgrading this device separate from official OTAs, having gotten used to Sony and Nexus devices... Tried replacing the firmware with an up-to-date version, though was getting errors upon attempting to flash a newer ROM afterwards, so reverted to the backup. Any suggestions on how to proceed?
"getvar all" relevant output?
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.654.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_004
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Since you already flashed the latest firmware you best bet would be to run the latest RUU and start fresh.
So I've reflashed firmware version 6.20.654.3 (no_recovery_no_boot), however I get various errors upon attempting to flash the corresponding RUU (tried both 0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU and Sprint_M8_HK_6.20.654.3_SuperSU_CPTB-signed).
The first time I tried flashing OP6BIMG_Sprint.... (renamed OP6BIMG.zip) I got "FAILED (remote: 32 header error)"
Upon a second attempt I received the following:
"Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 33551578 is not a multiple of the block size 4096
fastboot: libsparse/sparse.c:153: write_all_blocks: Assertion `pad >= 0' failed."
I then attempted to flash Sprint_M8_HK_6.20.654.3_SuperSU_CPTB-signed.zip
Which resulted in "FAILED (remote: 24 parsing android-info fail)"
A second attempt with this file gave the same "Invalid sparse file format...." output.
Related
Hi guys,
I have HTC One dual sim phone (PN0771000 HTC__A48).
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.49.0000
(bootloader) version-baseband: U3.14.3509.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.21.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HC3B4W900771
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7cdug
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0771000
(bootloader) cidnum: HTC__A48
(bootloader) battery-status: good
(bootloader) battery-voltage: 4099mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f6d46eca
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
I was on STOCK ROM and I received OTA 'over the air', I agreed to installed and now I see a message at my homescreen. saying: Unauthorized device. This app is not compatible with your phone.
My homescreen is black i can't swipe etc. I can just normally type in my pin. I can still slide down the notification bar and go to my settings.
My phone is rooted but it is still with S-ON.
I've flashed stock bootloader and lock it.
I've tried to flash PN07IMG_M7C_DUG_JB_50_S1_HTC_Europe_2.19.401.1_Radio_1237.21.28.0627_release_326125.zip with fastboot but it failed with error:
(bootloader) read zipped android_info fail
FAILED (status read failed (Too many links))
I've tried to ignore it, just do reboot but nothing has changed.
Then I've tried to flash PN07IMG_M7C_DUG_K44_SENSE60_MR_HTC_Nordic_5.17.402.6_Radio_E1237.29.35.0108_release_381671_combined_signed.zip but it failed with error:
FAILED (remote: 12 signature verify fail)
Please advise what should I do?
I advise you remove your imei from that info
Sent from my HTC One using XDA Premium 4 mobile app
Where did You found PN07IMG_M7C_DUG_K44_SENSE60_MR_HTC_Nordic_5.17.402 .6_Radio_E1237.29.35.0108_release_381671_combined_ signed.zip ??
Share
If you are bootloader locked you should see if there is a full factory RUU image available at htcdev. This will put you back to fresh out of the box condition. What's your carrier? What is your Cid?
wostrikov said:
Hi guys,
I have HTC One dual sim phone (PN0771000 HTC__A48).
Please advise what should I do?
Click to expand...
Click to collapse
The first RUU will failed because it is an older version than yours and the second failed because it was the wrong version number .402 vs .401. Since, you are S-ON you can only run RUU that are the same version or higher. You also need to have a stock rom (which you have) and stock recovery before running the OTA. If you had a custom recovery installed then you need to install the stock recovery for your version. If you don't have one, you can get one from this site by downloading an OTA for your version and extracting the recovery.img from the firmware.zip file in the OTA.
Hi everyone,
I have come across a friend's phone which is stuck in a bootloop since the battery died during an update. I am unable to run the Telus RUU (the only one I can find, from the collection thread, and it's very old). The RUU fails and I can not flash the zip from it manually using fastboot either. I can restore the TWRP backup from the collection but then the touch screen doesn't work (the backup must be much older).
So I am hoping someone on here has or can make me a TWRP backup of their latest stock HTC/Telus setup?
I am also going to see if I can get S-OFF and SuperCID so that I can try other RUUs. Thought that finding a backup would be a lot simpler/safer, though.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.661.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4231mV
(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
Thanks!
There is a 7.17.661.7 RUU for Telus here. To use this RUU, the phone firmware must be at least 6.xx.661.x and not newer than 7.17.661.7. Read instructions how to flash the RUU in the OP (you must use htc_fastboot to flash it, not the normal fastboot). Post the output of "fastboot getvar all" (remove imei and serialno) if you need more help.
Thanks! I don't have the phone near me at the moment to get the vars however I do know that fw is 5.xx.661.x range
I've added the getvar output. Since it's not my phone I am trying to avoid S-OFF using Sunshine. Didn't think it would be so difficult to find an RUU or TRWP backup
Try the 7.17.661.7 ruu, it might work since the phone is already on hboot 1.57. Otherwise you'll need s-off to either update your firmware and flash this ruu or downgrade your hboot and flash the 4.19.661.8 ruu.
I might be able to provide you a nandroid backup of 5.11.661.8 if I have some spare time. I will need to flash the the 4.19.661.8 ruu on my phone, update it to 5.11.661.8 so I can make a backup and upload it for you. But I won't have the time to do it this week...
Thanks I'll give it a shot. I was hesitant since I heard that jumping more than 1 firmware version could be bad.. but I'll see what happens and let you know.
This firmware thing does not apply to ruu, only apply to firmware update extracted from ota updates . In the worst case, the pre check will fail and nothing will be flashed on the phone
I finally had a chance to try this out and the 7.17.661.7 RUU fails to flash. Guess I'll have to S-OFF.
C:\Users\ryan\Downloads\HTC One M7>htc_fastboot flash zip "C:\Users\ryan\Downloads\HTC One M7\TELUS ROMs\7.17.661.7 (RUU Zip)\PN07IMG_M7_UL_L50_SENSE60_MR_TELUS_WWE_7.17.661.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420202_signed.zip"
sending 'zip'... (43286 KB) OKAY
sending time = 2.633 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 8(s)
Well if you can s-off this phone it will be indeed possible to flash the ruu after updating the firmware.
I'm trying to flash Stock RUU.
Now i have access only to Fastboot.
This the error log when i tried to flash RUU.zip
Code:
sending 'zip'... (50277 KB) OKAY
sending time = 3.213 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
FAILED (status read failed (Too many links))
Execution time is 10(s)
Device Info:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4316mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ea0bccbd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
svprm said:
I'm trying to flash Stock RUU.
Now i have access only to Fastboot.
This the error log when i tried to flash RUU.zip
Code:
sending 'zip'... (50277 KB) OKAY
sending time = 3.213 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
FAILED (status read failed (Too many links))
Execution time is 10(s)
Device Info:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4316mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ea0bccbd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
And what ruu version are you trying to flash?
7.21.707.121 LP 5.0.2 Sense 6
Indian version
svprm said:
7.21.707.121 LP 5.0.2 Sense 6
Indian version
Click to expand...
Click to collapse
Your firmware is too old to flash a 7.xx.xxx.xx RUU. To flash it you must be at least on a 6.xx.xxx.x firmware with hboot 1.57
alray said:
Your firmware is too old to flash a 7.xx.xxx.xx RUU. To flash it you must be at least on a 6.xx.xxx.x firmware with hboot 1.57
Click to expand...
Click to collapse
I tried to flash Stock Reset Rom
6.13.707.106 KK 4.4.3 Sense 6
From this thread:
http://forum.xda-developers.com/showthread.php?t=2778404
It stopped at Signature Verify Failed.
svprm said:
I tried to flash Stock Reset Rom
6.13.707.106 KK 4.4.3 Sense 6
From this thread:
http://forum.xda-developers.com/showthread.php?t=2778404
It stopped at Signature Verify Failed.
Click to expand...
Click to collapse
Signature Verify Failed? So you are trying to flash a rom using fastboot if I understand correctly? A rom must be flashed using a custom recovery. Only RUU/Firmware are flashed using fastboot. If you flash a ruu, it must be done using fastboot (in ruu mode) with a locked bootloader (because your phone is s-on). If flashing a rom, like the stock reset rom, it mus tbe done from twrp recovery with an unlocked bootloader.
alray said:
Signature Verify Failed? So you are trying to flash a rom using fastboot if I understand correctly? A rom must be flashed using a custom recovery. Only RUU/Firmware are flashed using fastboot. If you flash a ruu, it must be done using fastboot (in ruu mode) with a locked bootloader (because your phone is s-on). If flashing a rom, like the stock reset rom, it mus tbe done from twrp recovery with an unlocked bootloader.
Click to expand...
Click to collapse
When i try to flash files from TWRP recovery,it showing an error:
Unable to mount cache.
To solve this problem,i want to get back to Stock.
svprm said:
When i try to flash files from TWRP recovery,it showing an error:
Unable to mount cache.
To solve this problem,i want to get back to Stock.
Click to expand...
Click to collapse
Go in twrp recovery, select the "wipe" menu then select "Format Data" and type "Yes" to confirm. Once formatted, reboot twrp then push the reset rom to your phone storage, select "install" and flash the reset rom.
alray said:
Go in twrp recovery, select the "wipe" menu then select "Format Data" and type "Yes" to confirm. Once formatted, reboot twrp then push the reset rom to your phone storage, select "install" and flash the reset rom.
Click to expand...
Click to collapse
I tried all the ways i can not mount any partition on recovery system,data,cache.
Don't know why?
Again i tried to flash RUU.zip.
So i tried to lock the device again:
It showing following error:
Code:
... (bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
Execution time is 1(s)
I have decided to switch my AT&T Htc One M7 from GPE back to Sense. This device is S-Off and Bootloader Unlocked. This m7 was originally used on AT&T with Sense 4.4 Kitkat before being converted it to GPE.
My setup:
Windows 10 Pro
Latest HTC Drivers with USB 3.0 and 2.0 working correctly (Tested and working with fastboot commands)
HTC Sync Disabled.
Latest Android SDK (Updated)
New HTC Cable (Old one works too)
HTC One M7 - getvar all
C:\asdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.36.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.04.1700.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT38ZW900702
(bootloader) imei: 354439056913306
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4187mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0ddc65a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.113s
To continue, I have tried two different HTC RUU.exe. They both give the same error code.
ERROR [155]: Unknown Error
RUU_M7_UL_L50_SENSE60_MR_BrightstarUS_WWE_7.17.1540.51.exe
RUU_M7_UL_L50_SENSE60_MR_BrightstarUS_WWE_7.17.1540.35_Radio_4T.35.3218.16_10.33Q.1718.01L_release_448825_signed_2.exe
I also tried two AT&T RUU's. These had the same results as the above two.
RUU_M7_UL_L50_SENSE60_MR_Cingular_US_7.23.502.4_Radio_4M.32.3218.06_10.46.1718.01L_release_449059_signed_2.exe
RUU_M7_UL_L50_SENSE60_MR_Cingular_US_7.23.502.1_Radio_4M.32.3218.06_10.46.1718.01L_release_424933_signed_2.exe
I extracted the Rom.zip from both of these RUU's and tried flashing them thru fastboot oem rebootRUU. It failed to flash giving me this error; target reported max download size of 1526722560 bytes
target reported max download size of 1526722560 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 25202263 is not a multiple of the block size 4096
sending sparse 'zip' (1490936 KB)...
error: write_sparse_skip_chunk: don't care size 25202263 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 25202263 is not a multiple of the block size 4096
OKAY [106.289s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 106.624s
-------------------------------------------------------
I have read a lot of information from XDA and the internet. But I feel I am missing a step At this point I figure all of these flashing errors are due to the difference in filesystem sizes between Sense and GPE. If you have any suggestions I'd really appreciate it. Please include links and files if possible. Thanks
*** I have included pics in the attachments.
LightWeight_CO said:
I have decided to switch my AT&T Htc One M7 from GPE back to Sense. This device is S-Off and Bootloader Unlocked. This m7 was originally used on AT&T with Sense 4.4 Kitkat before being converted it to GPE.
My setup:
Windows 10 Pro
Latest HTC Drivers with USB 3.0 and 2.0 working correctly (Tested and working with fastboot commands)
HTC Sync Disabled.
Latest Android SDK (Updated)
New HTC Cable (Old one works too)
HTC One M7 - getvar all
C:\asdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.36.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.04.1700.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4187mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0ddc65a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.113s
Click to expand...
Click to collapse
At this point you are 90% there :good:
I'll give you the last 10% you need
In order to flash a 7.xx.xxx.x RUU (exe or zip) you must have at least hboot 1.57
And finally, to flash a 7.xx.xxx.x ruu.zip you must use the fastboot version that comes inside the ruu.exe (on the forum we call this one htc_fastboot but inside the ruu.exe it will simply be named "fastboot.exe"). Google's fastboot version can't handle files as big as the newer 7.xx.xxx.x RUUs. Anyway, that was just for your information since after flashing hboot 1.57 or 1.61, you should be able to flash the 7.17.154051 RUU.exe without any problem.
Here is the 1.61 hboot: https://www.androidfilehost.com/?fid=24269982087014709
to flash it:
Code:
fastboot oem rebootRUU
fastboot flash zip 7.17.1540.51_hboot_signedbyaa.img
fastboot flash zip 7.17.1540.51_hboot_signedbyaa.img
fastboot reboot-bootloader
then launch your RUU.exe or flash the ruu.zip using htc_fastboot
and don't panic if your phone is stuck at the white "HTC" splash screen for a while when booting for the fist time after the flash, the first boot can be a little longer than usual.
My One M7 is converted to GPE too, version HBOOT is 1.54, can i flash HBOOT 1.61 above?
Hello,
My phone recently soft bricked itself while I was attempting to check a message. The system locked up, then went into a reboot where it hung on the HTC logo. The usual steps of trying a factory reset did not seem to fix the logo hang. The phone was never modified, it was running only stock firmware with S-ON and the boot loader locked. As this is my first attempt at recovering from a soft brick, the learning curve has been steep. At this point I am somewhat stuck as I don't understand why I cannot flash the stock RUU that i have. What I have done:
-unlocked boot loader (1.61.000)
-flashed to TWRP for recovery (3.0.2.0)
-Attempted to use ADB sideload to push RUU files. This failed because ADB only sees the device every few attempts and then sideload commands fail saying "error: closed"
-Attempted to flash RUU as per this post https://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
*The RUU that I am trying to flash is the 7.19.401.51 signed version
Here is a getvar readout from my phone:
(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.401.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3833mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I am really confused as to how it soft bricked itself in the first place during normal use and if I am doing something incorrect in flashing it.
C:\mini-sdk>htc_fastboot flash zip RUU.zip
sending 'zip'... (50228 KB) OKAY
sending time = 3.030 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 9(s)
I dont see a reason why it fails but i dont know much about using ruu files. But if you have unlocked your phone and twrp is working you should be able to just restore a Stock twrp backup. You can find them here in the m7 forum, download the one that is matching your device, restart your device into twrp connect it to your computer and copy the twrp backup from your computer into your twrp backup folder on the phone, go in twrp to restore and you should see the backup, select it and slide to start.
All fixed
So I actually managed to fix it last night using the RUU file. I didn't realize that I had to re-lock my boot loader for a signed RUU file to work properly. Once I ran the "fastboot oem lock" command, the file installed normally by running "fastboot oem bootRUU" and then flashing it with "fastboot flash RUU.zip"
I wasn't able to even move files with twrp loaded, my device showed up as an MTP device on my computer, but any file movements gave an error that the device stopped responding.