Database Develop

[Q] Wiped OS and Wiped SDcard

Hello.
I have been trying to repair this by myself for 3 days reading this forum but I just can't do it.
My phone had unlocked bootloader, rooted and SOFF. When I was flashing a rom I don't know what happened but it deleted my OS.
Then I tried to update my firmware and it deleted my SD card. I'm stuck at TWPR recovery.
Now when I try to use a RUU installer it always shows an error, I also tried to use a RUU via fastboot command and it shows error 42. My bootloader is relocked btw.
I cannot sideload anything because my SD was wiped.
I'm now somewhat desperate. I just want my phone to revive.
My MODEL ID is PN0712000 and I got SuperCID 1111111
My firmware is version is 3.17.502.3.
PLEASE help me.

MsDosExe said:
Hello.
I have been trying to repair this by myself for 3 days reading this forum but I just can't do it.
My phone had unlocked bootloader, rooted and SOFF. When I was flashing a rom I don't know what happened but it deleted my OS.
Then I tried to update my firmware and it deleted my SD card. I'm stuck at TWPR recovery.
Now when I try to use a RUU installer it always shows an error, I also tried to use a RUU via fastboot command and it shows error 42. My bootloader is relocked btw.
I cannot sideload anything because my SD was wiped.
I'm now somewhat desperate. I just want my phone to revive.
My MODEL ID is PN0712000 This indicates your phone is AT&T or Developers edition and I got SuperCID 1111111
My firmware is version is 3.63.707.4.
PLEASE help me.
Click to expand...
Click to collapse
What Ruu did you try ?
and can you boot to bootloader and give me the results for
fastboot getvar all
minus your serial no and IEMI, I can help you much better with this info.
If you are s-off it should be no problem getting you up and running

clsA said:
What Ruu did you try ?
and can you boot to bootloader and give me the results for
fastboot getvar all
minus your serial no and IEMI, I can help you much better with this info.
If you are s-off it should be no problem getting you up and running
Click to expand...
Click to collapse
I'm trying RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2
These are my results from getvar:
C:\abd\platform-tools\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(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: 4319mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.072s

MsDosExe said:
I'm trying RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2
These are my results from getvar:
C:\abd\platform-tools\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(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: 4319mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.072s
Click to expand...
Click to collapse
Everything looks Good !!
Hold the power button and vol down till the phone reboots
continue holding just vol down back to the bootloader
then do
fastboot erase cache
fastboot reboot-bootloader
then to fastboot USB and start the RUU on your PC again (rebooting the PC before doing all this is a good idea also).(If your on windows 7 running the RUU as Administrator is good too)
Also check the md5 of the RUU you downloaded to make sure it's good

clsA said:
Everything looks Good !!
Hold the power button and vol down till the phone reboots
continue holding just vol down back to the bootloader
then do
fastboot erase cache
fastboot reboot-bootloader
then to fastboot USB and start the RUU on your PC again (rebooting the PC before doing all this is a good idea also).(If your on windows 7 running the RUU as Administrator is good too)
Also check the md5 of the RUU you downloaded to make sure it's good
Click to expand...
Click to collapse
I dit everything and the ruu installer keeps saying the same error.
"Error 155 IMAGE ERROR"
How can I check the MD5? Maybe that's the problem.

MsDosExe said:
I dit everything and the ruu installer keeps saying the same error.
"Error 155 IMAGE ERROR"
Click to expand...
Click to collapse
does the phone ever reboot to RUU mode ?
correct file and md5
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/

clsA said:
does the phone ever reboot to RUU mode ?
Click to expand...
Click to collapse
When I run the installer it reboots in RUU Mode (the grey HTC letters) then it checks my phone, deletes my user data, and then it says "sending..." after that it fails and shows the 155 IMAGE ERROR and something about getting the right ROM.
How can I check the MD5? Maybe that's the problem.

MsDosExe said:
When I run the installer it reboots in RUU Mode (the grey HTC letters) then it checks my phone, deletes my user data, and then it says "sending..." after that it fails and shows the 155 IMAGE ERROR and something about getting the right ROM.
How can I check the MD5? Maybe that's the problem.
Click to expand...
Click to collapse
The post above yours
extract it to the desktop
go to the other link and copy the listed md5 for your ruu
then find you ruu in the bottom box and check it
if it's red you need to redownload

clsA said:
The post above yours
extract it to the desktop
go to the other link and copy the listed md5 for your ruu
then find you ruu in the bottom box and check it
if it's red you need to redownload
Click to expand...
Click to collapse
I got the wrong MD5 on the RUU. I downloaded the one you provided and my HTC One is back to life again.
Thank you very much. I have never figure it out without you.

MsDosExe said:
I got the wrong MD5 on the RUU. I downloaded the one you provided and my HTC One is back to life again.
Thank you very much. I have never figure it out without you.
Click to expand...
Click to collapse
I'm Glad your back up and running !!

[Q] (Q) Cant flash recovery( stock and custom) and cant flash RUU too?

Hi everybody,
i have HTC one M7, and i getvar all that:
(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.12.707.105
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA38WW900067
(bootloader) imei: 356376053563510
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4278mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.046s
1st of all i flash RUU RUU_M7_UL_JB_50_hTC_Asia_WWE_1.29.707.3_R_Radio_4A.14.3250.13_10.33.1150.01_release_311678_signed
when check signature, it failed
also i try to extract rom.zip to flash manually , failed too.( I do relock bootloader to flash RUU)
I flash stock recovery and custom, but when i flash TWRP and CWM then i enter recovey, the screen on HTC said Entering recovery but after that HTC reboot by itself. ( i do unlock bootloader to flash recovery)
Can anyone tell me what to do now?
Thank for your help.

Type fastboot erase cache after flashing custom recovery. Try entering recovery again
Also you can't flash lower version RUU because your device is s-on

Hi SaHiLzZ
I do fastboot erase cache, and it's okay, but i cant enter custom recovery, i try many version and many recovery, but it's not ok.
When i press Recovery, it still show Entering Recovery and restart device, any idea, please?

hoangchaunguyen said:
Hi SaHiLzZ
I do fastboot erase cache, and it's okay, but i cant enter custom recovery, i try many version and many recovery, but it's not ok.
When i press Recovery, it still show Entering Recovery and restart device, any idea, please?
Click to expand...
Click to collapse
same problem here
is anyone can help me and this guy please
My Post Here

same problem
we must wait for ruu exe file 5.12.707.105
Please dont use any zip file for uptae
When exe file of ruu release our problem will end
So please don't updates any zip file

raghav9 9 said:
we must wait for ruu exe file 5.12.707.105
Please dont use any zip file for uptae
When exe file of ruu release our problem will end
So please don't updates any zip file
Click to expand...
Click to collapse
What is the logic behind this number? Is it already planned or is it based on radio number?
I think this could also be a solution for my problem (just started a new thread)

s-on relocked
leoncornelissen said:
What is the logic behind this number? Is it already planned or is it based on radio number?
I think this could also be a solution for my problem (just started a new thread)
Click to expand...
Click to collapse
when locked, relocked, s-on
can't downgrade firmware
only equal or greater firmware can flash

Help returning to 4.4.2 stock from 4.2.2. Nothing works!

Hi guys,
For 5 weeks I've been trying to upgrade my phone to 5.0.2 and nothing works. All I've managed to do is go from 4.4.2 down to 4.2.2 and now I'm stuck here. I've tried RUUs, I've tried fastboot zips, everything fails.
Right now I've got 4.2.2 TWRP, and s-off and this from getvar:
bootloader: 1.54.0000
baseband: 4a.17.3250.14
main 2.24.206.7
cidnum: 11111111
I just want to go back to stock to get OTAs.
Can someone please help me? I've watched so many YouTube videos and read so many threads but nothing has worked. I just keep digging a deeper hole.

download the stock firmware for your phone and flash it with odin

anfalanl said:
download the stock firmware for your phone and flash it with odin
Click to expand...
Click to collapse
Odin? Isn't that for Samsung phones?

SJWackness said:
Hi guys,
For 5 weeks I've been trying to upgrade my phone to 5.0.2 and nothing works. All I've managed to do is go from 4.4.2 down to 4.2.2 and now I'm stuck here. I've tried RUUs, I've tried fastboot zips, everything fails.
Right now I've got 4.2.2 TWRP, and s-off and this from getvar:
bootloader: 1.54.0000
baseband: 4a.17.3250.14
main 2.24.206.7
cidnum: 11111111
I just want to go back to stock to get OTAs.
Can someone please help me? I've watched so many YouTube videos and read so many threads but nothing has worked. I just keep digging a deeper hole.
Click to expand...
Click to collapse
Post the output of "fastboot getvar all" (remove imei and serialno)
"everything fails": can you be more precise please? Sometime it will fail for a simple reason, but without knowing the exact error its hard to tell you why it failed...
---------- Post added at 06:15 PM ---------- Previous post was at 06:12 PM ----------
anfalanl said:
download the stock firmware for your phone and flash it with odin
Click to expand...
Click to collapse
Hummm, no
donkeykong1 said:
Odin? Isn't that for Samsung phones?
Click to expand...
Click to collapse
^^

This is output of getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.206.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxx
(bootloader) imei: xxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3849mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I'f tried using different RUUs (206s and 401s) to get to 4.4.2 but it always fails. The furthest I got was a RUU getting stuck at "Checking Headers ....5%". It sat there for 30 minutes a few different times.
I've tried installing an OTA zip for 5.0.2 (when I was on 4.4.2) through TWRP but that didn't work either.
So I got S-Off and tried all of these again. Still not working.
Ideally what I want is a clean Sense 6 install of 5.0.2 with the latest firmware.
Any help would be very much appreciated. Thanks in advance.

I'm also getting this error from a few RUUs:
An error (-5001 : 0x80070002) has occurred while running the setup.
I've rebooted and run the RUU again and it says the same.

SJWackness said:
This is output of getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.206.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxx
(bootloader) imei: xxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3849mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I'f tried using different RUUs (206s and 401s) to get to 4.4.2 but it always fails. The furthest I got was a RUU getting stuck at "Checking Headers ....5%". It sat there for 30 minutes a few different times.
I've tried installing an OTA zip for 5.0.2 (when I was on 4.4.2) through TWRP but that didn't work either.
So I got S-Off and tried all of these again. Still not working.
Ideally what I want is a clean Sense 6 install of 5.0.2 with the latest firmware.
Any help would be very much appreciated. Thanks in advance.
Click to expand...
Click to collapse
SJWackness said:
I'm also getting this error from a few RUUs:
An error (-5001 : 0x80070002) has occurred while running the setup.
I've rebooted and run the RUU again and it says the same.
Click to expand...
Click to collapse
update your firmware to 7.19.401.2 then flash the 7.19.401.22 ruu. You must use htc_fastboot.exe to flash the ruu <--- important. Save htc_fastboot.exe, the 7.19.401.2 firmware and the 7.19.401.22 ruu in the same folder you have adb.exe and fastboot.exe on your computer.
Code:
fastboot oem rebootRUU
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
fastboot reboot-bootloader
htc_fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.22_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430964_signed.zip
htc_fastboot reboot
First boot can take longer than usual (stuck at HTC splash screen) just wait it will boot eventually.

alray said:
update your firmware to 7.19.401.2 then flash the 7.19.401.22 ruu. You must use htc_fastboot.exe to flash the ruu <--- important. Save htc_fastboot.exe, the 7.19.401.2 firmware and the 7.19.401.22 ruu in the same folder you have adb.exe and fastboot.exe on your computer.
Code:
fastboot oem rebootRUU
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
fastboot reboot-bootloader
htc_fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.22_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430964_signed.zip
htc_fastboot reboot
First boot can take longer than usual (stuck at HTC splash screen) just wait it will boot eventually.
Click to expand...
Click to collapse
THANKS A MILLION! It looks like it's updated! Cheers!!

HTC One (M7) Stuck in ruu mode

Hello.. I have tried to upgrade my os using a RUU file.. The system version was 6.xx.xxx.
That was not matched to radio version or something.. I forgot to check that..
Now im stuck on RUU mode..
My previous OS version was 5.03.651.3
I was searched for that and i found a RUU that matches 5.03.651.3..I have installed it using RUU exe but ita says { Cir - Fail pu
}.
Every other things is ok
what should i do? Plz help me.. I cant get in to recovery or anything.
OS version is showing in Red color
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0515
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.03.651.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA34MS902538
(bootloader) imei: 990001466195989
(bootloader) meid: 99000146619598
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4277mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.086s

MiyuB said:
Hello.. I have tried to upgrade my os using a RUU file.. The system version was 6.xx.xxx.
That was not matched to radio version or something.. I forgot to check that..
Now im stuck on RUU mode..
My previous OS version was 5.03.651.3
I was searched for that and i found a RUU that matches 5.03.651.3..I have installed it using RUU exe but ita says { Cir - Fail pu
}.
Every other things is ok
what should i do? Plz help me.. I cant get in to recovery or anything.
OS version is showing in Red color
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0515
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.03.651.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA34MS902538
(bootloader) imei: 990001466195989
(bootloader) meid: 99000146619598
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4277mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.086s
Click to expand...
Click to collapse
"Cir fail pu" = Consumer infrared - partition update fail
Which basically mean that the RUU was unable to write the CIR.img to your CIR partition, for some reason...
Since your phone is S-OFF you can flash unsigned firmware so the best option would be to download the 5.03.651.3 firmware.zip, remove the CIR.img from it and flash it to your phone (it won't attempt to flash the CIR partition so it won't give you any fail).
Download this one: https://www.androidfilehost.com/?fid=23501681358553240 open it and remove the CIR.img. Then flash it to your phone:
Code:
fastboot oem rebootRUU
fastboot flash zip 5.03.651.3_firmware_RUU.zip
fastboot flash zip 5.03.651.3_firmware_RUU.zip
fastboot reboot

alray said:
"Cir fail pu" = Consumer infrared - partition update fail
Which basically mean that the RUU was unable to write the CIR.img to your CIR partition, for some reason...
Since your phone is S-OFF you can flash unsigned firmware so the best option would be to download the 5.03.651.3 firmware.zip, remove the CIR.img from it and flash it to your phone (it won't attempt to flash the CIR partition so it won't give you any fail).
Download this one: https://www.androidfilehost.com/?fid=23501681358553240 open it and remove the CIR.img. Then flash it to your phone:
Code:
fastboot oem rebootRUU
fastboot flash zip 5.03.651.3_firmware_RUU.zip
fastboot flash zip 5.03.651.3_firmware_RUU.zip
fastboot reboot
Click to expand...
Click to collapse
Ohhhhh you saved my ass.. Thanks buddy...
But os has a problem.. Black lines go though display..
I had a twrp backup.. To restore that backup i installed twrp recovery
but phone cant go to recovery.. It is stuck in the green htc logo display and after that phone restarts..

MiyuB said:
Ohhhhh you saved my ass.. Thanks buddy...
But os has a problem.. Black lines go though display..
I had a twrp backup.. To restore that backup i installed twrp recovery
but phone cant go to recovery.. It is stuck in the green htc logo display and after that phone restarts..
Click to expand...
Click to collapse
Did you erased the cache and restarted bootloader after flashing twrp? What version of twrp? Is that problem with the display only in the OS?
Code:
fastboot flash recovery twrp.img
fastboot erase cache
fastboot reboot-bootloader

alray said:
Did you erased the cache and restarted bootloader after flashing twrp? What version of twrp? Is that problem with the display only in the OS?
Code:
fastboot flash recovery twrp.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
I hav managed that.. I restored that TWRP backup..Now phone works like charm..Thanks alot buddy..You really saved me.
I need a one help.. Can u give me the right RUU for this phone?

MiyuB said:
I hav managed that.. I restored that TWRP backup..Now phone works like charm..Thanks alot buddy..You really saved me.
I need a one help.. Can u give me the right RUU for this phone?
Click to expand...
Click to collapse
6.23.651.10 is the latest version: https://www.androidfilehost.com/?fid=24588232905725176
But you'll probably get the same problem with your CIR partition when flashing that RUU.
You'll either have to do the same procedure (remove the CIR.img from the 6.23.651.10 firmware and flash it) or decrypt the RUU before flashing so you can remove the CIR.img.

alray said:
6.23.651.10 is the latest version: https://www.androidfilehost.com/?fid=24588232905725176
But you'll probably get the same problem with your CIR partition when flashing that RUU.
You'll either have to do the same procedure (remove the CIR.img from the 6.23.651.10 firmware and flash it) or decrypt the RUU before flashing so you can remove the CIR.img.
Click to expand...
Click to collapse
Ok i got it bro..Thank u veryy much

M7 Sprint m7_wls - firmware/update issue

I'm having some issues with getting the firmware updated on my m7 and hoping someone can help.
I had posted some info in another thread of mine, but the thread is now over a year old so I figured I would start a new one.
First, here is my get-var output
C:\DroidTools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0626
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 99000146505640
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4001mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.094s
Not sure why the get-var didn't finish out (Too many links) ?
Anyways I tried updating the firmware with the latest I could find for the sprint variant, but I received this error.
"Target didn't report max-download-size"
sending 'zip' (45578 KB)...
OKAY [2.807s]
writing 'zip' . . .
(bootloader) zip header checking . . .
(bootloader) zip info parsing . . .
FAILED (remote: 99 unknown fail)
finished. total tim: 3.067s
I've tried a few different versions of firmware as well and still no luck.
I can just fastboot reboot bootloader and then reboot after that and I'm back to my normal stuff with no issues though.
I was also able to flash a newer twrp recovery without any hiccups.. so not sure what is up.
I am currently running AICP 12.1 but I am getting allot of crashes on random thing, and I suspect my mega-old firmware may be contributing. I also tried the last CyanogenMod that was available (13...?) but I couldn't get data and calls to work.
I also attempted to re-lock the boot-loader and tried flashing the firmware that way, but I received a different error.
"remote 12 signature verify fail"
After that I had to scramble and remember how to unlock the boot-loader again just to get my phone to boot back up lol. I haven't had my unlock file in years so that was fun.
So I'm stuck at 1.44.0000 for now. I'm starting to wonder if i have to find an older firmware first before I can jump to a newer one?
Also slightly confused on the RUU. I am already running custom recovery and custom ROM. Is updating the RUU still necessary?
All feedback and help is welcomed.
Thanks

cloud66 said:
I'm having some issues with getting the firmware updated on my m7 and hoping someone can help.
I had posted some info in another thread of mine, but the thread is now over a year old so I figured I would start a new one.
First, here is my get-var output
C:\DroidTools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0626
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 99000146505640
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4001mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.094s
Not sure why the get-var didn't finish out (Too many links) ?
Anyways I tried updating the firmware with the latest I could find for the sprint variant, but I received this error.
"Target didn't report max-download-size"
sending 'zip' (45578 KB)...
OKAY [2.807s]
writing 'zip' . . .
(bootloader) zip header checking . . .
(bootloader) zip info parsing . . .
FAILED (remote: 99 unknown fail)
finished. total tim: 3.067s
I've tried a few different versions of firmware as well and still no luck.
I can just fastboot reboot bootloader and then reboot after that and I'm back to my normal stuff with no issues though.
I was also able to flash a newer twrp recovery without any hiccups.. so not sure what is up.
I am currently running AICP 12.1 but I am getting allot of crashes on random thing, and I suspect my mega-old firmware may be contributing. I also tried the last CyanogenMod that was available (13...?) but I couldn't get data and calls to work.
I also attempted to re-lock the boot-loader and tried flashing the firmware that way, but I received a different error.
"remote 12 signature verify fail"
After that I had to scramble and remember how to unlock the boot-loader again just to get my phone to boot back up lol. I haven't had my unlock file in years so that was fun.
So I'm stuck at 1.44.0000 for now. I'm starting to wonder if i have to find an older firmware first before I can jump to a newer one?
Also slightly confused on the RUU. I am already running custom recovery and custom ROM. Is updating the RUU still necessary?
All feedback and help is welcomed.
Thanks
Click to expand...
Click to collapse
The firmware.zip you are trying to flash (the one linked in the other thread) isn't signed so your phone must be s-off. Sorry I should have mentioned that earlier but didn't noticed yours was s-on.

Its actually s-off now, showing "shipped s-on"?
Not sure what that means but the bootloader is definitely unlocked.

cloud66 said:
Its actually s-off now, showing "shipped s-on"?
Not sure what that means but the bootloader is definitely unlocked.
Click to expand...
Click to collapse
bootloader unlocked doesn't mean s-off. If your phone is s-off you should see "PVT SHIP S-OFF" and "Security: OFF" in your fastboot getvar all output
On a S-ON phone you can only flash signed firmware.zip and it must be done with a locked (or re-locked) bootloader
On a S-OFF phone you can flash signed or unsigned firmware.zip and the bootloader status doesn't matters (can be locked, re-locked or unlocked).
The sprint firmware linked in the other thread, the one that you are trying to flash is an unsigned zip so you need s-off first. Otherwise you can try to update the whole phone using the latest sprint RUU from htc's website, not sure it will work on hboot 1.44. Backup important files before trying, the ruu will wipe and update your rom and firmware. Btw you also need to be locked/re-locked to flash a ruu if your phone is s-on.

alray said:
bootloader unlocked doesn't mean s-off. If your phone is s-off you should see "PVT SHIP S-OFF" and "Security: OFF" in your fastboot getvar all output
On a S-ON phone you can only flash signed firmware.zip and it must be done with a locked (or re-locked) bootloader
On a S-OFF phone you can flash signed or unsigned firmware.zip and the bootloader status doesn't matters (can be locked, re-locked or unlocked).
The sprint firmware linked in the other thread, the one that you are trying to flash is an unsigned zip so you need s-off first. Otherwise you can try to update the whole phone using the latest sprint RUU from htc's website, not sure it will work on hboot 1.44. Backup important files before trying, the ruu will wipe and update your rom and firmware. Btw you also need to be locked/re-locked to flash a ruu if your phone is s-on.
Click to expand...
Click to collapse
Can you help me with an M7 that has these details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.60.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxx
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(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-91bb20e1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
The phone won't boot and the version-main is blank. First time I'm handling an M7 since this is a friends and the guides all involve toolkits so kinda lost at the moment. Bootloader is locked
Unlocked the bootloader only to find it has TWRP and no OS

Renosh said:
Can you help me with an M7 that has these details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.60.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxx
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(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-91bb20e1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
The phone won't boot and the version-main is blank. First time I'm handling an M7 since this is a friends and the guides all involve toolkits so kinda lost at the moment. Bootloader is locked
Unlocked the bootloader only to find it has TWRP and no OS
Click to expand...
Click to collapse
You can flash it back to stock rom using a RUU.
The latest version is here: http://dl3.htc.com/application/RUU_...691.655435036.1511537283-936972463.1506975706
Launch the .exe file with the phone in bootloader mode and showing "fastboot usb" in red
If you are not using a Windows PC you can find the .zip version of the same RUU here: https://androidfilehost.com/?fid=24588232905725176
You can flash it using fastboot in ruu mode:
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip PN071IMG_M7WLS_L50_SENSE60_SPRINT_6.23.651.10_signed.zip
htc_fastboot reboot
If you prefer to flash a custom rom instead of stock, just make sure to choose one compatible with the Sprint variant (M7WLS). Push it to your phone memory and flash it using the "install" menu from twrp.
If the phone was sim-unlocked (working on other network than Sprint) you might have to sim-unlock again after flashing a RUU.

alray said:
You can flash it back to stock rom using a RUU.
The latest version is here: http://dl3.htc.com/application/RUU_...691.655435036.1511537283-936972463.1506975706
Launch the .exe file with the phone in bootloader mode and showing "fastboot usb" in red
If you are not using a Windows PC you can find the .zip version of the same RUU here: https://androidfilehost.com/?fid=24588232905725176
You can flash it using fastboot in ruu mode:
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip PN071IMG_M7WLS_L50_SENSE60_SPRINT_6.23.651.10_signed.zip
htc_fastboot reboot
If you prefer to flash a custom rom instead of stock, just make sure to choose one compatible with the Sprint variant (M7WLS). Push it to your phone memory and flash it using the "install" menu from twrp.
If the phone was sim-unlocked (working on other network than Sprint) you might have to sim-unlock again after flashing a RUU.
Click to expand...
Click to collapse
Thanks I actually already managed to fix it using this thread:
https://forum.xda-developers.com/showthread.php?t=2795856
I used the full firmware but had to install this redistributable file for RUU to work (Windows 10) after locking bootloader:
https://npackd.appspot.com/p/com.microsoft.VisualCPPRedistributable/9.0.21022.8
I'll have to search for sim unlock, crap

alray said:
bootloader unlocked doesn't mean s-off. If your phone is s-off you should see "PVT SHIP S-OFF" and "Security: OFF" in your fastboot getvar all output
On a S-ON phone you can only flash signed firmware.zip and it must be done with a locked (or re-locked) bootloader
On a S-OFF phone you can flash signed or unsigned firmware.zip and the bootloader status doesn't matters (can be locked, re-locked or unlocked).
The sprint firmware linked in the other thread, the one that you are trying to flash is an unsigned zip so you need s-off first. Otherwise you can try to update the whole phone using the latest sprint RUU from htc's website, not sure it will work on hboot 1.44. Backup important files before trying, the ruu will wipe and update your rom and firmware. Btw you also need to be locked/re-locked to flash a ruu if your phone is s-on.
Click to expand...
Click to collapse
Thanks for the info. I'm going to try this sometime this week hopefully.
I've been running AICP 7.1.1 for nearly 3 weeks so far with minor hiccups now and then so i'm slightly hesitant to screw something up again :-/
I will update this as soon as I try a signed RUU from HTC.
Will a signed RUU destroy my recovery as well?
Also do I need to unlock after I flash the RUU?
Steps would be
1. relock bootloader
2. Install signed RUU
3. Relock Bootloader
4. Install TWRP
5. Install Rom
6. ?
Assuming I have these correct and everything works that is.

cloud66 said:
Thanks for the info. I'm going to try this sometime this week hopefully.
I've been running AICP 7.1.1 for nearly 3 weeks so far with minor hiccups now and then so i'm slightly hesitant to screw something up again :-/
I will update this as soon as I try a signed RUU from HTC.
Will a signed RUU destroy my recovery as well?
Also do I need to unlock after I flash the RUU?
Steps would be
1. relock bootloader
2. Install signed RUU
3. Re-unlock Bootloader (use www.htcdev.com/bootloader)
4. Install TWRP
5. Install Rom
6. ?
Assuming I have these correct and everything works that is.
Click to expand...
Click to collapse
Stock recovery will overwrite twrp when flashing a RUU, not really a concern since it will take only a few minutes to reflash twrp. And yes you'll need to re-unlock the bootloader after flashing the ruu, before you can install twrp back to your recovery partition. Steps 1 to 5 above are correct.