Can't return HTC One to Stock - One (M7) Q&A, Help & Troubleshooting

Hi there.
I'me having problems returning my HTC One to Stock.
I just want to do it so I cant OTA update my HTC to Android 4.4.3, I don't need to return it to factory so no need to erase "Tampered".
I've tried almost everything for almost a week, here's what I have tried already:
Attempt 1- Flash Stock recovery, Relock bootloader and run RUU.zip
Result - 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
ERROR: usb_read failed with status e00002e8
FAILED (status read failed (No such file or directory))
Also...
When I relock the bootloader, appeared the message "Security warning" under "Relocked"
Attempt 2 - Running RUU.exe on Windows
Result - Error, RUU version not correct.
Now, the info of my HTC:
CID: HTC_203
Baseband Version:
4T.27.3218.14_10.33C.1718.01L
Hboot:
1.57
M7_UL PVT SHIP S-ON RH
Radio:
4T.27.3218.14
MID:
PN0710000
Files I'm using:
RUU.exe - RUU M7 UL JB 50 HTC Europe 1.20.401.1 Radio 4A.13.3227.06 10.27.1127.01 Release 308001 Signed 2 4
RUU.zip - RUU Zip M7 UL JB 50 HTC Europe 1.20.401.1 Radio 4A.13.3227.06 10.27.1127.01 Release 308001 Signed 2 4
Stock Recovery - 5.11.401.10
Any help??

Jonymacarrony said:
Hi there.
I'me having problems returning my HTC One to Stock.
I just want to do it so I cant OTA update my HTC to Android 4.4.3, I don't need to return it to factory so no need to erase "Tampered".
I've tried almost everything for almost a week, here's what I have tried already:
Attempt 1- Flash Stock recovery, Relock bootloader and run RUU.zip
Result - 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
ERROR: usb_read failed with status e00002e8
FAILED (status read failed (No such file or directory))
Also...
When I relock the bootloader, appeared the message "Security warning" under "Relocked"
Attempt 2 - Running RUU.exe on Windows
Result - Error, RUU version not correct.
Now, the info of my HTC:
CID: HTC_203
Baseband Version:
4T.27.3218.14_10.33C.1718.01L
Hboot:
1.57
M7_UL PVT SHIP S-ON RH
Radio:
4T.27.3218.14
MID:
PN0710000
Files I'm using:
RUU.exe - RUU M7 UL JB 50 HTC Europe 1.20.401.1 Radio 4A.13.3227.06 10.27.1127.01 Release 308001 Signed 2 4
RUU.zip - RUU Zip M7 UL JB 50 HTC Europe 1.20.401.1 Radio 4A.13.3227.06 10.27.1127.01 Release 308001 Signed 2 4
Stock Recovery - 5.11.401.10
Any help??
Click to expand...
Click to collapse
post the output of "fastboot getvar all" excluding the IMEI and SERIALNO so we can determine what file you need. Btw, do never use the 1.20.401.1 RUU. This version is like a pre-release verison and will not get updated with OTA.

alray said:
post the output of "fastboot getvar all" excluding the IMEI and SERIALNO so we can determine what file you need. Btw, do never use the 1.20.401.1 RUU. This version is like a pre-release verison and will not get updated with OTA.
Click to expand...
Click to collapse
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 4161mV
(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 for the tip:good:

Jonymacarrony said:
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 4161mV
(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 for the tip:good:
Click to expand...
Click to collapse
You can't use a RUU to restore your phone because its S-ON. You can only use older RUU with S-OFF and there are no RUU that match your current version. You could flash a stock odex rom if you can find one You can find it on ARHD website. According to your hboot version, I think you should use a 5.11.401.10 rom + the stock recovery.
or you will need to s-off and use the 1.28.401 ruu

alray said:
You can't use a RUU to restore your phone because its S-ON. You can only use older RUU with S-OFF and there are no RUU that match your current version. You could flash a stock odex rom if you can find one You can find it on ARHD website. According to your hboot version, I think you should use a 5.11.401.10 rom + the stock recovery.
or you will need to s-off and use the 1.28.401 ruu
Click to expand...
Click to collapse
What do I need to do/read in ordem to S-off my device with minimal risk and turn the device to Stock.
If too risky, is ARHD ROM similar to Stock ROM in user interface?

Jonymacarrony said:
What do I need to do/read in ordem to S-off my device with minimal risk and turn the device to Stock.
If too risky, is ARHD ROM similar to Stock ROM in user interface?
Click to expand...
Click to collapse
S-OFF can be a risk if you are not sure of what your are doing. ARHD really looks like the stock rom when speaking about the interface. You should really consider flashing this rom if you want a quick and easy fix to your situation.
S-OFF can be hard to achieve on hboot 1.57. In the worst case, you will need to use sunshine which cost 25$ US

alray said:
S-OFF can be a risk if you are not sure of what your are doing. ARHD really looks like the stock rom when speaking about the interface. You should really consider flashing this rom if you want a quick and easy fix to your situation.
S-OFF can be hard to achieve on hboot 1.57. In the worst case, you will need to use sunshine which cost 25$ US
Click to expand...
Click to collapse
How about Android Revolution HD 81.0 is it any good?
I want something simple, I am going to give my HTC to my girlfriend, so, she doesn't need anything more then what Sense 6 already has to offer. But I want to update the phone to 4.4.3.

Jonymacarrony said:
How about Android Revolution HD 81.0 is it any good?
I want something simple, I am going to give my HTC to my girlfriend, so, she doesn't need anything more then what Sense 6 already has to offer. But I want to update the phone to 4.4.3.
Click to expand...
Click to collapse
ARHD seem to be one of the most popular rom for the M7 so im pretty sure you'll (or your girlfriend) be fine using it. We often recommend it for users who want to use a custom rom for the first time. If your girlfriend is not an advanced android user, she will probably not notice any difference between ARHD and stock Sense rom.
and don't forget to flash it using twrp 2.6.3.3 or you'll get issue booting the rom.

Also, the firmware differences between 4.4.2 and 4.4.3 are minimal. I did not notice any change.

right, only some security fixes, you won't notice any change between 4.4.2 and 4.4.3.

alray said:
ARHD seem to be one of the most popular rom for the M7 so im pretty sure you'll (or your girlfriend) be fine using it. We often recommend it for users who want to use a custom rom for the first time. If your girlfriend is not an advanced android user, she will probably not notice any difference between ARHD and stock Sense rom.
and don't forget to flash it using twrp 2.6.3.3 or you'll get issue booting the rom.
Click to expand...
Click to collapse
Well, I had TWRP 2.8.x.x. and worked nicely, now I've flashed twrp 2.6.3.3 and I'm stuck in "Entering recovery..."

Jonymacarrony said:
Well, I had TWRP 2.8.x.x. and worked nicely, now I've flashed twrp 2.6.3.3 and I'm stuck in "Entering recovery..."
Click to expand...
Click to collapse
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader

alray said:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Stuck...

Jonymacarrony said:
Stuck...
Click to expand...
Click to collapse
have you checked the MD5 value of twrp 2.6.3.3 and are you sure you are using the version or the M7_U/UL?

alray said:
have you checked the MD5 value of twrp 2.6.3.3 and are you sure you are using the version or the M7_U/UL?
Click to expand...
Click to collapse
I have successfully installed both twrp and the custom ROM.
But for some reason I can't log in with my google account in order to restore my android backup. It says that there's a problem in comunication with google servers, but I have wifi internet already working fine on the phone.

As I know, firewater can S-OFF 1.57
Sent from my iPhone using Tapatalk

q3trung said:
As I know, firewater can S-OFF 1.57
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Indeed. The problem is that it's too risky for me.
Now, it might seem too noob but, how the hell do I turn off the update warning???

Jonymacarrony said:
Indeed. The problem is that it's too risky for me.
Now, it might seem too noob but, how the hell do I turn off the update warning???
Click to expand...
Click to collapse
My device had hoot 1.57, made it s-off using firewater. It's safe

Related

[Q] Back to Stock for Bell HTC One

I have been reading a lot of guides and I am still not sure how I can take my Bell phone and bring it back to stock. I have S-OFF and GPE right not which I installed via a zipped RUU.
Now, if I want to get the latest 4.2.2 that Bell made available for the HTC One, I have to somehow be able to get the OTA and have no custom recovery. I could not find an RUU ZIP or EXE for bell (666), only a stock ROM. I could install that but comes the OTA, it won't install because of the custom recovery.
How can I go back to stock from here? I have been told by a few to just stick to the GPE edition but I would like to got back to sense.
Thank you.
Nic2112 said:
I have been reading a lot of guides and I am still not sure how I can take my Bell phone and bring it back to stock. I have S-OFF and GPE right not which I installed via a zipped RUU.
Now, if I want to get the latest 4.2.2 that Bell made available for the HTC One, I have to somehow be able to get the OTA and have no custom recovery. I could not find an RUU ZIP or EXE for bell (666), only a stock ROM. I could install that but comes the OTA, it won't install because of the custom recovery.
How can I go back to stock from here? I have been told by a few to just stick to the GPE edition but I would like to got back to sense.
Thank you.
Click to expand...
Click to collapse
post output of "fastboot getvar all"
remove S/N & IMEI before posting
kamilmirza said:
post output of "fastboot getvar all"
remove S/N & IMEI before posting
Click to expand...
Click to collapse
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3975mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s
Nic2112 said:
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3975mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s
Click to expand...
Click to collapse
your previous CID was BM_001, right?
look into nkk71 SuperGUIDE in my signature
kamilmirza said:
post output of "fastboot getvar all"
remove S/N & IMEI before posting
Click to expand...
Click to collapse
NKK71 helped me bring the phone back to stock GPE, but I'm getting weird problems and I am not sure why, but I remember I didn't have those problems with stock. Stuff like streaming not working over WiFi, MMS messages not sent when I have WiFi enabled, stuff like that.
The problem is that Bell (x.xx.666x.) has no RUU that I can find, only a nandroid which I could use but that won't give me the option to get the OTA (I think)
kamilmirza said:
your previous CID was BM_001, right?
Click to expand...
Click to collapse
I believe so, yes.
Nic2112 said:
NKK71 helped me bring the phone back to stock GPE, but I'm getting weird problems and I am not sure why, but I remember I didn't have those problems with stock. Stuff like streaming not working over WiFi, MMS messages not sent when I have WiFi enabled, stuff like that.
The problem is that Bell (x.xx.666x.) has no RUU that I can find, only a nandroid which I could use but that won't give me the option to get the OTA (I think)
Click to expand...
Click to collapse
yes sadly there is only nandroid of BM right now
I just updated the firmware today, the one I had was for 4.3 so I upgraded that. I'm just not sure if the problems come from the fact that there is no HTC One google edition in Canada and that either my radios or firmware are not working perfectly on bell.
Nic2112 said:
I just updated the firmware today, the one I had was for 4.3 so I upgraded that. I'm just not sure if the problems come from the fact that there is no HTC One google edition in Canada and that either my radios or firmware are not working perfectly on bell.
Click to expand...
Click to collapse
yeah maybe that could be the problem
why not try the nandroid and see how it goes?
Hmm, you are going to have a HBOOT mismatch if you run the Canadian Restock method in my guide posted in my signature, as it uses 1.55HBOOT for 4.3 JB, but you are on 1.56 HBOOT.
However if you run the RUU ZIP file for TELUS, you will get the right HBOOT. http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Download and rename to Telus.zip
See if you can do this:
fastboot oem writecid TELUS001
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip Telus.zip
fastboot flash zip Telus.zip (You will need to run this command twice due to HBOOT downgrade)
fastboot reboot (if it doesn't reboot automatically)
NOTE: I have not personally ran the ZIP file above, but it should be fine.
Oh Wow, there is a guide for Canadian HTC One, didn't know that!
Are you sure that a Telus RUU will work on a Bell phone? They use different networks I think
SaHiLzZ said:
Hmm, you are going to have a HBOOT mismatch if you run the Canadian Restock method in my guide posted in my signature, as it uses 1.55HBOOT for 4.3 JB, but you are on 1.56 HBOOT.
However if you run the RUU ZIP file for TELUS, you will get the right HBOOT. http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Download and rename to Telus.zip
See if you can do this:
fastboot oem writecid TELUS001
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip Telus.zip
fastboot flash zip Telus.zip (You will need to run this command twice due to HBOOT downgrade)
fastboot reboot (if it doesn't reboot automatically)
NOTE: I have not personally ran the ZIP file above, but it should be fine.
Click to expand...
Click to collapse
As I said, i have no personally tested it, but thats the only way to bring your HBOOT down to 1.55.
Other option will be to go all the way down to 1.44 HBOOT. You NEED to be comfortable with using adb/fastboot commands REGARDLESS whichever options you decide to go with.
SaHiLzZ said:
As I said, i have no personally tested it, but thats the only way to bring your HBOOT down to 1.55.
Other option will be to go all the way down to 1.44 HBOOT. You NEED to be comfortable with using adb/fastboot commands REGARDLESS whichever options you decide to go with.
Click to expand...
Click to collapse
I know how to go back to 1.44, I have done that before.
So what you are saying is that if I have the nandroid installed, and stock recovery from your thread, the phone will detect the OTA? It should install no problem because it will be a standard recovery.
Yes 1.44 HBOOT, 1.44 Compatible BELL Nandroid, and Stock recovery will give you future OTAs.
SaHiLzZ said:
Yes 1.44 HBOOT, 1.44 Compatible BELL Nandroid, and Stock recovery will give you future OTAs.
Click to expand...
Click to collapse
Thatk you, one last question before I try this, the OTA, will it replace the radios and firmware as well to Bell's? I guess it depends on what they put in the OTA.
Yes, OTA generally contain new OS, HBOOT, Recovery, and RADIO, practically a full RUU replacement, but not all. IF you are S-ON, you will need to lock bootloader after loading stock recovery, but if you are S-OFF, that doesnt matter, and I will suggest to stay S-OFF!
Please help
I have bell HTC one M7 one Hboot 1.56 the phone boot loader is unlocked rooted and soff the mic is not working on phone I need to set back to stock I can have warranty fix phone can anyone please help me get back to stock so they cant tell it was touched
ginuwine96 said:
I have bell HTC one M7 one Hboot 1.56 the phone boot loader is unlocked rooted and soff the mic is not working on phone I need to set back to stock I can have warranty fix phone can anyone please help me get back to stock so they cant tell it was touched
Click to expand...
Click to collapse
Check the signature block of the previous post (nkk71's SuperGUIDE to returning 100% back to stock) or this one Return to 100% Stock Guide and follow it.
Not sure what file I need
majmoz said:
Check the signature block of the previous post (nkk71's SuperGUIDE to returning 100% back to stock) or this one Return to 100% Stock Guide and follow it.
Click to expand...
Click to collapse
This is my phones Info I am not sure what file to use for it ?
bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.666.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4258mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
ginuwine96 said:
This is my phones Info I am not sure what file to use for it ?
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-main: 4.19.666.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
Click to expand...
Click to collapse
If you're going to follow my guide, you'll need to use CWM method, using this nandroid: http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-bm___001-1-29-666-5-zip/
make sure to have read it once or twice, to be sure you're comfortable with the process

[Q] HTC ONE M7 stuck in boot loop, S-On is back on hboot 1.44.0000

I need help fixing my phone. I was flashing a sense 6 rom and after the aroma installer, my device rebooted into hboot and reboots if i try to reboot, power down, or go into recovery.
I need help please
one_mic_only said:
I need help fixing my phone. I was flashing a sense 6 rom and after the aroma installer, my device rebooted into hboot and reboots if i try to reboot, power down, or go into recovery.
I need help please
Click to expand...
Click to collapse
Please give us a few more information.....
which rom were you flashing ?
Which recovery do you have ?
So you can't acces into recovery ?
Boachti said:
Please give us a few more information.....
which rom were you flashing ?
Which recovery do you have ?
So you can't acces into recovery ?
Click to expand...
Click to collapse
i flashed renovate
i now have 2.7.0.3 recovery
and i'm able to get into recovery and i restored
i'm just trying to get s off and try the bad boys sense 6 rom
one_mic_only said:
i flashed renovate
i now have 2.7.0.3 recovery
and i'm able to get into recovery and i restored
i'm just trying to get s off and try the bad boys sense 6 rom
Click to expand...
Click to collapse
you should be a bit more specific (renovate and 2.7.0.3 could mean a lot of things
1- start by posting a "fastboot getvar all" (excluding IMEI, MEID, and s/n)
2- an actual link to the threads (and downloads) of the files (and versions) you mentioned... cause i don't see TWRP 2.7.0.3 in either the m7_u/ul or the m7_wls models
I'm assuming TWRP, but you know what they say about assumption...
nkk71 said:
you should be a bit more specific (renovate and 2.7.0.3 could mean a lot of things
1- start by posting a "fastboot getvar all" (excluding IMEI, MEID, and s/n)
2- an actual link to the threads (and downloads) of the files (and versions) you mentioned... cause i don't see TWRP 2.7.0.3 in either the m7_u/ul or the m7_wls models
I'm assuming TWRP, but you know what they say about assumption...
Click to expand...
Click to collapse
here's the link
http://forum.xda-developers.com/showthread.php?t=2692922
and yes we all know what they say lol
i'm just trying to s-off now, cause i can't flash any of those roms without being s-off correct?
i alway root my phone, s-off, then fall into the land of the lost when it comes to going thru this process again. at least i saved myself from flat out brick.
one_mic_only said:
here's the link
http://forum.xda-developers.com/showthread.php?t=2692922
and yes we all know what they say lol
i'm just trying to s-off now, cause i can't flash any of those roms without being s-off correct?
i alway root my phone, s-off, then fall into the land of the lost when it comes to going thru this process again. at least i saved myself from flat out brick.
Click to expand...
Click to collapse
i thought only GPE ROMs require S-Off... didnt see anything in the OP about having to be S-Off.
anyway, if you're trying to S-Off best use a ROM which is inline with your firmware (so check your fastboot getvar all), then find a ROM based on the same version (rooted with unsecured kernel) and use firewater to get s-off
at least we now know you're on Sprint... cause you've only linked Sprint stuff ... i'm assuming
yes i'm on sprint lol
and here ya go
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0315
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.651.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA348S905516
(bootloader) imei: 990001465400661
(bootloader) meid: 99000146540066
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4043mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d8b0f7651bb88c960f701ae91477674a
getvar:all FAILED (unknown status code)
finished. total time: 0.069s
any suggestions for a rom that will work? i'm about to try badseed now.
one_mic_only said:
yes i'm on sprint lol
and here ya go
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0315
(bootloader) version-main: 1.29.651.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_wls
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
finished. total time: 0.069s
any suggestions for a rom that will work? i'm about to try badseed now.
Click to expand...
Click to collapse
actually, yes
hboot 1.44
http://forum.xda-developers.com/showpost.php?p=48955645&postcount=250
ARHD 9.4 is Sprint compatible (select Sprint in the installer), it's rooted, it has an unsecured kernel, and you can even use revone to S-Off
http://firewater-soff.com/ and http://rumrunner.us/ should work also, your choice
thanks.
think i'll try rum. revone aint working.

[Q] Downgrading from 4.4. to 4.3

Morning everyone,
I have been reading for days trying to get a handle on downgrading my phone to JB 4.3. I am s-off, unlocked, rooted, with current TWRP installed. I also am using SuperSu. I suspect I am just not using the right combination of programming. My first thought is that I need the correct Hboot to go with the ROM I want. Currently I am on Android 4.4.2 with sense 5.5. Software is 4.18.502.7 CL302626. I have loaded a custom Hboot which removed the developer red text. and have also removed the tampered warning with a bit of help from here. I am quite happy with remaining s-off and unlocked. I am decent with ADB commands. I understand Linux fairly well, and can even use a hex editor in a crude way.
The last 4.3 RUU_exe and RUU_zip would not complete. The EXE stated not compatible. The ZIP failed looking for the Android-info_txt. I looked in the ZIP file thinking it might need modified and did not find the Android-info file at all. Lead me to believe that I may not be hitting the correct file for my use. So, at the risk of asking a repeated question I have finally come here for a push in the right direction.
I have not messed with all of this since I modded my old EVO 4G from Sprint. The new Android system worked well in stock form. I started down this road because of my desire to move back to 4.3
And I did attempt to use the search function but did not find exactly what I want. Appreciate any help I may be able to get.
lonestarmedic said:
My first thought is that I need the correct Hboot to go with the ROM I want.
Click to expand...
Click to collapse
No! you don't have to flash hboot to be able to flash a rom, you can flash a 4.4 Rom even if i.e you are on hboot 1.44.
lonestarmedic said:
Currently I am on Android 4.4.2 with sense 5.5. Software is 4.18.502.7 CL302626. I have loaded a custom Hboot which removed the developer red text and have also removed the tampered warning with a bit of help from here. I am quite happy with remaining s-off
Click to expand...
Click to collapse
I hope so, never turn S-ON with a modded hboot or you will probably brick your phone. Anyway, never S-ON!
lonestarmedic said:
The last 4.3 RUU_exe and RUU_zip would not complete. The EXE stated not compatible.
Click to expand...
Click to collapse
What version of RUU.exe and zip? Please also post the output of fastboot getvar all except IMEI. What was the error code of the ruu.exe and what was the output when attempting to flash the ruu.zip? you were in fastboot ruu mode right? Did you md5 check both the zip and exe?
lonestarmedic said:
The ZIP failed looking for the Android-info_txt. I looked in the ZIP file thinking it might need modified and did not find the Android-info file at all.
Click to expand...
Click to collapse
android-info.txt should be inside ruu.zip, however if you have the correct ruu for your mid/cid you should not have to modify the android-info.txt
Answers
Will do my best to answer.
1) Your example was a newer ROM on an older Hboot. I am going to older ROM on newer Hboot. Any difference.
2) No intention of turning S-on. Understand risks of modified Hboot. I do have stock Hboot if needed.
3) The RUU.exe is RUU_M7_UL_SENSE 5.0_MR_Cingular_US_3.17.502.3_Radio_4A19.3263.13_10.38j.1157.04_release_334235_signed_2
4) The RUU.zip is RUU Zip M7_UL_JB43_Sense50_MR_Cingular_US_3.17.502.3-decrypted
5) I did not copy the prompt screne on the ADB failure. I believe it was a parsing failure 24 on the Android-info.txt
6) Yes, using fastboot mode. Showing Fastboot USB and entering into the screen with the silver HTC logo.
7) I am honestly not sure if I checked both items for md5 sums.
8) I have to copy and paste the get var yet.
Working on the rest.
lonestarmedic said:
Will do my best to answer.
1) Your example was a newer ROM on an older Hboot. I am going to older ROM on newer Hboot. Any difference.
2) No intention of turning S-on. Understand risks of modified Hboot. I do have stock Hboot if needed.
3) The RUU.exe is RUU_M7_UL_SENSE 5.0_MR_Cingular_US_3.17.502.3_Radio_4A19.3263.13_10.38j.1157.04_release_334235_signed_2
4) The RUU.zip is RUU Zip M7_UL_JB43_Sense50_MR_Cingular_US_3.17.502.3-decrypted
5) I did not copy the prompt screne on the ADB failure. I believe it was a parsing failure 24 on the Android-info.txt
6) Yes, using fastboot mode. Showing Fastboot USB and entering into the screen with the silver HTC logo.
7) I am honestly not sure if I checked both items for md5 sums.
8) I have to copy and paste the get var yet.
Working on the rest.
Click to expand...
Click to collapse
1) no
5,7) make sure to md5 check your ruu. Looks like a bad download
3,4,8) still waiting for your getvar
Text files as requested
Getvar results edited out end of serial number and the imei. The meid does come up as all zeros.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT34NW(xxxxxxx)
(bootloader) imei: a very private thing
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4123mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Android-info text from the zip file
modelid: PN0712000
cidnum: CWS__001
mainver: 3.17.502.3
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
Working on back checking md5 sums
Thanks so far.
JB
lonestarmedic said:
Getvar results edited out end of serial number and the imei. The meid does come up as all zeros.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT34NW(xxxxxxx)
(bootloader) imei: a very private thing
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4123mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Android-info text from the zip file
modelid: PN0712000
cidnum: CWS__001
mainver: 3.17.502.3
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
Working on back checking md5 sums
Thanks so far.
JB
Click to expand...
Click to collapse
you should try to flash the stock hboot and flash the zip ruu again
Reflashin
alray said:
you should try to flash the stock hboot and flash the zip ruu again
Click to expand...
Click to collapse
I was using the stock Hboot from the OTA via AT&T. I put in the modified one to drop the ugly tampered stuff. Though that might have had something to do with my problem. And tried again with the modified Hboot.
Checked both md5s and good to go there.
JB
Flash timeframe
Is it possible I am too impatient on the flash of the Zip file? Phone sat with no progress for about 5-10 minutes on the silver HTC screen.
JB
Output on oemRUU attempt
Here is what I get when I attempt to use the zip file to flash the phone.
It is the same whether unlocked or relocked.
:\Android\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Android\platform-tools>fastboot flash zip jelly.zip
sending 'zip' (1114992 KB)...
OKAY [ 57.002s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 68.047s
Think I got it fixed
Very busy right now but will report back and explain what I did.
Mainly due to being unfamiliar with different file types and which uses what method for update/load.
JB
Back to 4.3 succsessfully
Ok, long process of learning. Found my problem was with the RUU that I was using. The md5 was ok. It just was not what was needed for using via fastboot.
Do not know what it is, but it has the following inside the zip file:
1) META INF folder
2)system folder
3)boot.img
Sure does not work for fastboot!!! I found a zip on here that had the right file name and was odexed. Downloaded, checked the md5, then unzipped to read the Android-info.txt file. All looked right. Made a backup of phone and loaded it on in.
Succsess!!! Of course I had to put TWRP back in and root the phone.
So, brief sequence of what I did:
1) OTA update from 4.3 to 4.4.2 caused problems with applications
2) Phone in stock form with Hboot 1.56
3) Unlocked phone - HTCdev website used
4) Rooted phone with SuperSU and installed TWRP
5) Played with ROMS and did not like any of them, decided to revert back to 4,3
6) Phone would not S-off with stock ROM using Rumrunner
7) Ended up with the combination of Android Revolution HD and Firewater. Used my UBUNTU Linux to perform S-off.
8) Back-up performed
9) Used zip file and fastboot to load 4.3
10) Now have Hboot 1.56 with 4.3 unlocked, stock Hboot, and S-off.
Thanks for listening to my rantings.
Maybe this will help someone else with an AT&T HTC One.
JB

Got soft-brick in RUU mode

Earlier i had 6.09.401.5 ROM on my phone. Bootloader showed that main os version is 6.13.708.1
CID was set to 11111111 with S-ON and LOCKED bootloader, HBOOT 1.57
I tried to install 7.17.1540 RUU but got a BRICK with 1.61 HBOOT.
Now main version os shows 6.13.708.1 (7.17.1540.4)
Have only access to fastboot. Screen shows HTC logo with 4 triangles. On USB disconnection shows recovery with only "RUU" text.
Tried to flash through fastboot 401 and 708 firmwares, but getting: SBL1 = Fail-PU or Signature verify failed etc.
By RUU having error 152 or 155 or 12.
Non RUU or ZIP won't flash.
Don't know, what to do, please help!
lyrgo23 said:
Earlier i had 6.09.401.5 ROM on my phone. Bootloader showed that main os version is 6.13.708.1
CID was set to 11111111 with S-ON and LOCKED bootloader, HBOOT 1.57
I tried to install 7.17.1540 RUU but got a BRICK with 1.61 HBOOT.
Now main version os shows 6.13.708.1 (7.17.1540.4)
Have only access to fastboot. Screen shows HTC logo with 4 triangles. On USB disconnection shows recovery with only "RUU" text.
Tried to flash through fastboot 401 and 708 firmwares, but getting: SBL1 = Fail-PU or Signature verify failed etc.
By RUU having error 152 or 155 or 12.
Non RUU or ZIP won't flash.
Don't know, what to do, please help!
Click to expand...
Click to collapse
You must complete the flash of the 7.17.1540 ruu to get out of ruu mode. What is your "fastboot getvar all"? Are you flashing a zip or exe ruu? If you are flashing a zip ruu are you using htc_fastboot.exe instead of fastboot.exe? Is the md5 good on your ruu?
Sent from my HTC One using XDA Labs
alray said:
You must complete the flash of the 7.17.1540 ruu to get out of ruu mode. What is your "fastboot getvar all"? Are you flashing a zip or exe ruu? If you are flashing a zip ruu are you using htc_fastboot.exe instead of fastboot.exe? Is the md5 good on your ruu?
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
Im using simple fastboot.exe. Tried to install through RUU (getting errors 152 and 155) and ZIP (but it won't flash images bigger than 1.5 GB). don't know about md5.
can't get "getvar all". But it has superCID with system image of 6.13.708.1. But came from service with 6.17.401.5 with unability to update by OTA.
lyrgo23 said:
Im using simple fastboot.exe. Tried to install through RUU (getting errors 152 and 155) and ZIP (but it won't flash images bigger than 1.5 GB). don't know about md5.
can't get "getvar all". But it has superCID with system image of 6.13.708.1. But came from service with 6.17.401.5 with unability to update by OTA.
Click to expand...
Click to collapse
You must use htc_fastboot.exe to flash a 7.xx.xxx.x ruu and you must check the md5 value of your ruu to confirm it's integrity. Why can't you post the output of "fastboot getvar all"? Need to know your Cid, mid, version-main, hboot version...
You also need s-off to flash a ruu that doesn't have the same base version. Your phone looks pretty messed up, that's why a complete "fastboot getvar all" would help determine the best way to get everything back to normal
Sent from my HTC One using XDA Labs
alray said:
You must use htc_fastboot.exe to flash a 7.xx.xxx.x ruu and you must check the md5 value of your ruu to confirm it's integrity. Why can't you post the output of "fastboot getvar all"? Need to know your Cid, mid, version-main, hboot version...
You also need s-off to flash a ruu that doesn't have the same base version. Your phone looks pretty messed up, that's why a complete "fastboot getvar all" would help determine the best way to get everything back to normal
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
C:\adb>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: 6.13.708.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3C2W158269
(bootloader) imei: 355859056916623
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3855mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU (Hboot PreUpdate)
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 52(ms)
Tried to install RUU EXE Brightstar. Having error 152.
Tried to install 7.17.708.21 ZIP RUU. having error 51 partition update fail. Picture attached.
lyrgo23 said:
C:\adb>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: 6.13.708.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3855mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU (Hboot PreUpdate)
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 52(ms)
Click to expand...
Click to collapse
Hboot PreUpdate mean that the RUU wasn't flashed completely, it went trough the hboot pre-update (first flash) and is now waiting for the second flash to finish.
lyrgo23 said:
Tried to install RUU EXE Brightstar. Having error 152.
Click to expand...
Click to collapse
Your phone is S-ON, running a x.xx.708.x base, MID PN0710000.
Brightsar US (aka Dev Edititon) is a x.xx.1540.x bas for MID PN0712000
You can't use this ruu unless you achieve S-OFF and change your MID number.
lyrgo23 said:
Tried to install 7.17.708.21 ZIP RUU. having error 51 partition update fail. Picture attached.
Click to expand...
Click to collapse
So now your "fastboot getvar all" isn't the same....
version-main is now: 6.13.708.1 (7.18.708.21)
so you must complete the 7.18.708.21 flash to get out of RUU mode....
and I guess the boot-mode isn't "Hboot PreUpdate" anymore...?
Try to flash the RUU again using htc_fastboot.exe and copy/paste your command window in your next post so we can see everything.
but 7.18.708.21 RUU is for model PN0714000. Mine is PN0710000. shows image error
lyrgo23 said:
but 7.18.708.21 RUU is for model PN0714000. Mine is PN0710000. shows image error
Click to expand...
Click to collapse
Sorry I miss-read your getvar, this explain everything. You either don't have the right MID or the right version installed on your phone. This phone was clearly S-OFF at some point and someone either changed the MID or the firmware version (since they don't match together) and turned back S-ON. Supercid (11111111) also confirm that your phone was s-off. You already have supercid so CID doesn't matters, flash a RUU that match your MID like 7.19.401.xx. If this is still failing you'll need s-off again to fix it.

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.

Categories

Resources