i attempted to unlock bootloader on my wife's old HTC M7 (Australian/Vodafone), i was able to unlock the bootloader, but had to do some serious trial and error to get a custom recovery installed, eventually got an older twrp loaded, but the phone just refused to boot into recovery.
i then relocked the bootloader (no S-OFF), and when i try and unlock he bootloader now, the phone attempts to boot into the recovery, and is failing...
i've been trying to find an RUU from somewhere, just to blat the phone back to an old state, and try again.
are there RUUs available anywhere? i dont' care if its not for the local carrier, i just want to get a basic android rom on the thing.
However, im curious if i need to s-off to do this (wasnt the case with my previous HTC)
help!
<<<I NOW KNOW WHAT THE ISSUE WAS, I WAS FLASHING RECOVERY FROM THE HTC M8, NOT M7>>>
any ideas?
gjw00 said:
i then relocked the bootloader (no S-OFF), and when i try and unlock he bootloader now, the phone attempts to boot into the recovery, and is failing...
Click to expand...
Click to collapse
Really bad idea to relock the bootloader with a custom recovery, well you shouldn't relock at all if there is anything "custom" installed on your phone.The process of unlocking bootloader requires the stock recovery. The only way to flash the recovery partition is when the bootloader is unlocked or by flashing a signed firmware.zip or ruu.zip. The firmware.zip or ruu.zip must match your version-main, CID and MID.
i've been trying to find an RUU from somewhere, just to blat the phone back to an old state, and try again.
are there RUUs available anywhere? i dont' care if its not for the local carrier, i just want to get a basic android rom on the thing.
Click to expand...
Click to collapse
Its not working like that. If your phone is S-ON the ruu must be made for your carrier (must match CID and MID, must be same or newer version-main)
post the output of "fastboot getvar all" (remove your imei and serialno)
alray said:
Really bad idea to relock the bootloader with a custom recovery, well you shouldn't relock at all if there is anything "custom" installed on your phone.The process of unlocking bootloader requires the stock recovery. The only way to flash the recovery partition is when the bootloader is unlocked or by flashing a signed firmware.zip or ruu.zip. The firmware.zip or ruu.zip must match your version-main, CID and MID.
Its not working like that. If your phone is S-ON the ruu must be made for your carrier (must match CID and MID, must be same or newer version-main)
post the output of "fastboot getvar all" (remove your imei and serialno)
Click to expand...
Click to collapse
ok, i've been trying with a bunch of RUUs i found on the web, and trying to flash inside RUU (wasnt 100% sure what rebooting to RUU was for actually)
the CID is VODAP021, i will need to check when i get back home to see what the MID is, its not the GPE of the m7, if that helps, you reckon if i find an OTA update, and extract out the ruu.zip, it might blat a stock recovery on? will i need to use htc_fastboot, or just the standard fastboot?
my nexus 5 has finally shat it (small child cracked screen, now screen has crapped itself), just want to get a basic android build onto the m7 in the final few weeks before the new pixel phones are out...
gjw00 said:
ok, i've been trying with a bunch of RUUs i found on the web, and trying to flash inside RUU (wasnt 100% sure what rebooting to RUU was for actually)
the CID is VODAP021, i will need to check when i get back home to see what the MID is, its not the GPE of the m7, if that helps, you reckon if i find an OTA update, and extract out the ruu.zip, it might blat a stock recovery on? will i need to use htc_fastboot, or just the standard fastboot?
my nexus 5 has finally shat it (small child cracked screen, now screen has crapped itself), just want to get a basic android build onto the m7 in the final few weeks before the new pixel phones are out...
Click to expand...
Click to collapse
You can extract a firmware.zip (not an ruu) from an ota update and flash it to restore the stock recovery. You must use the right version. Waiting for your fastboot getvar all.
Sent from my HTC One using XDA Labs
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: 7.21.980.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
gjw00 said:
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: 7.21.980.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
7.21.980.51 is the latest version for vodap021 and can't find a 7.21.980.51 firmware.zip or ota.zip.
At least there is a 7.21.980.51 ruu on ir-file.com, bad news is that you must register to this website to be able to download (20$ for 30 days)
http://ir-file.com/show.php?token=32375
i can load the phone into the OS btw, i've a feeling that OTA might on the device, you think its' accessible using a non-root browser? i could maybe get the ota zip off the device and try flashing that in RUU?
gjw00 said:
i can load the phone into the OS btw, i've a feeling that OTA might on the device, you think its' accessible using a non-root browser? i could maybe get the ota zip off the device and try flashing that in RUU?
Click to expand...
Click to collapse
Yes, if you can capture the ota this is the best option (because its free). Look in your /download folder, you're looking for a long file name starting with "OTA_M7_UL_L50_SENSE60" and ending with ".zip". Save it on your computer and extract the "firmware.zip" file from it. Then reboot in RUU mode and flash the firmware:
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then you should be able to unlock again.
it worked! thank you..
Related
I've flashed multiple ROMS but I don't know what what's up now.
I was stuck on FTS Rom and couldn't flash any other ROMS- they wouldn't take. It would always reboot in FTS.
So in TWRP, I did an advanced wipe... everything was gone including the multiple various ROMS and backups in both TWRP and CLKmod. Trouble is, now I can get as far as flashing various new recoveries from the bootloader, but I can't push any rom to it or flash anything from the bootloader.
Extra kicker- I can NOT mount the phone on my computer. This has been the case for a while, not from any ROM. Not from FTS Rom, not from any recovery... can not mount the phone and transfer files.
HTC Dumlock also did not work.
Specs-
HTC One- unlocked, rooted, HBoot 1.55, S-On, Radio 4%.20.3218.13
Any help would be appreciated.
I did s-off since you're unlocked. Probably the issue. Then I would go into fast boot to either ruu or transfer a rom
I think rumrunner is what works on 1.55 hboot
Sent from my HTC One
krankenator said:
I've flashed multiple ROMS but I don't know what what's up now.
I was stuck on FTS Rom and couldn't flash any other ROMS- they wouldn't take. It would always reboot in FTS.
So in TWRP, I did an advanced wipe... everything was gone including the multiple various ROMS and backups in both TWRP and CLKmod. Trouble is, now I can get as far as flashing various new recoveries from the bootloader, but I can't push any rom to it or flash anything from the bootloader.
Extra kicker- I can NOT mount the phone on my computer. This has been the case for a while, not from any ROM. Not from FTS Rom, not from any recovery... can not mount the phone and transfer files.
HTC Dumlock also did not work.
Specs-
HTC One- unlocked, rooted, HBoot 1.55, S-On, Radio 4%.20.3218.13
Any help would be appreciated.
Click to expand...
Click to collapse
do you know how to use fastboot commands?
post your results from (minus your iemi and serial no)
fastboot getvar all
we can use this info to direct you to the correct RUU to fix your phone
clsA said:
do you know how to use fastboot commands?
post your results from (minus your iemi and serial no)
fastboot getvar all
we can use this info to direct you to the correct RUU to fix your phone
Click to expand...
Click to collapse
Not pro, but I hobble by. Results:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4350mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
krankenator said:
Not pro, but I hobble by. Results:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4350mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Edit your post to match mine.
you have AT&T phone here's the link to the RUU
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
Edit: Keep in mind that resetting your phone with RUU is full wipe and starting from scratch
after it's done you will need to unlock bootloader, flash recovery and Root. Same as if your phone was brand new
clsA said:
Edit your post to match mine.
you have AT&T phone here's the link to the RUU
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
Edit: Keep in mind that resetting your phone with RUU is full wipe and starting from scratch
after it's done you will need to unlock bootloader, flash recovery and Root. Same as if your phone was brand new
Click to expand...
Click to collapse
Thanks. I don't suppose there is a Mac version for this? I don't currently have Windows installed. If not, I"ll just have to fix this later.
Thanks for all your help.
krankenator said:
Thanks. I don't suppose there is a Mac version for this? I don't currently have Windows installed. If not, I"ll just have to fix this later.
Thanks for all your help.
Click to expand...
Click to collapse
yes here
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
-rom.zip can be flashed using
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip (yes do this 2 times)
fastboot reboot
Click to expand...
Click to collapse
files needed >> http://forum.xda-developers.com/showthread.php?t=2390995
clsA said:
yes here
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
files needed >> http://forum.xda-developers.com/showthread.php?t=2390995
Click to expand...
Click to collapse
Thanks for your help. Downloading the RUU now but before I flash this I just want to be clear.
Do I first need to S-Off using Rumrunner? I can't find a mac version, just Linux and Win.
Then do I need to re-lock my bootloader? (I read that step here http://forum.xda-developers.com/showthread.php?t=2251800)
Then at that point I can flash the RUU or can I just flash the RUU without S-Off or re-locking the bootloader
-rom.zip can be flashed using
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip (yes do this 2 times)
fastboot reboot
krankenator said:
Thanks for your help. Downloading the RUU now but before I flash this I just want to be clear.
Do I first need to S-Off using Rumrunner? I can't find a mac version, just Linux and Win.
Then do I need to re-lock my bootloader? (I read that step here http://forum.xda-developers.com/showthread.php?t=2251800)
Then at that point I can flash the RUU or can I just flash the RUU without S-Off or re-locking the bootloader
-rom.zip can be flashed using
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip (yes do this 2 times)
fastboot reboot
Click to expand...
Click to collapse
I don't think that file requires s-off
but yes a locked boot loader is needed
fastboot oem lock
Well, time to try something else.
Any ideas anyone?
krankenator said:
Something didn't work. It only reboot to the bootloader.
Pro-Mac-Jesseesktop jesse$ ./fastboot oem lock
Click to expand...
Click to collapse
FAILED (remote: 12 signature verify fail)
I'll take a guess this means you need s-off
or a windows PC to run the RUU.exe I posted first
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
Hello I have a bit of a situation on my hands, basically while attempting to root my friends Htc One (M7) I may of flashed the kernel before flashing the recovery and now I have at the top of the fastboot screen *** TAMPERED *** & *** RELOCKED *** (very scary) and now while trying to re-unlock bootloader I get halfway and then it get's to a screen with the HTC logo with a white background and then it has in small pink text Entering Recovery and it stays like that for ages and does nothing Is there anything that I can do to fix this?
[QRCODE][/QRCODE]
Hipratboy said:
Hello I have a bit of a situation on my hands, basically while attempting to root my friends Htc One (M7) I may of flashed the kernel before flashing the recovery and now I have at the top of the fastboot screen *** TAMPERED *** & *** RELOCKED *** (very scary) and now while trying to re-unlock bootloader I get halfway and then it get's to a screen with the HTC logo with a white background and then it has in small pink text Entering Recovery and it stays like that for ages and does nothing Is there anything that I can do to fix this?
Click to expand...
Click to collapse
you need stock recovery to unlock the bootloader, and as you have relocked the bootloader for reasons unknown, you will have to find the correct firmware for your phone and flash that in order to put the stock kernel and stock recovery back on the phone, never lock the bootloader with anything custom on the phone what so ever.
Seanie280672 said:
[QRCODE][/QRCODE]
you need stock recovery to unlock the bootloader, and as you have relocked the bootloader for reasons unknown, you will have to find the correct firmware for your phone and flash that in order to put the stock kernel and stock recovery back on the phone, never lock the bootloader with anything custom on the phone what so ever.
Click to expand...
Click to collapse
Do you know where I can find my firmware information, and with that information where would I download the correct files and roughly how big are they because I don't have the best internet also what would be the steps required for flashing the correct firmware on the phone? (Btw I have S-On)
Hipratboy said:
Do you know where I can find my firmware information, and with that information where would I download the correct files and roughly how big are they because I don't have the best internet also what would be the steps required for flashing the correct firmware on the phone? (Btw I have S-On)
Click to expand...
Click to collapse
can youpost your fastboot getvar all please without imei and serial number, that will tell use which firmware you are on, depending on which firmware you are on depends on the file size, but they are between 40 - 60mb generally, we will go through flashing procedure once we find the firmware package.
next time you try to root, you unlock the bootloader, flash a custom recovery, flash the supers.zip, reboot and complete root setup, and then flash a kernel if that's what you want, never relock the bootloader with any of that on your phone.
Seanie280672 said:
can youpost your fastboot getvar all please without imei and serial number, that will tell use which firmware you are on, depending on which firmware you are on depends on the file size, but they are between 40 - 60mb generally, we will go through flashing procedure once we find the firmware package.
next time you try to root, you unlock the bootloader, flash a custom recovery, flash the supers.zip, reboot and complete root setup, and then flash a kernel if that's what you want, never relock the bootloader with any of that on your phone.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4189mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
This any good?
Hipratboy said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4189mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
This any good?
Click to expand...
Click to collapse
easy one to sort out, firmware is here (47.5mb): http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/7.19.401.2.zip
htc fastboot is here: https://www.androidfilehost.com/?fid=95916177934550031
download them both and put in the same folder as your adb and fastboot files, rename the 7.19.401.2.zip to firmware.zip for ease then issue these commands:
fastboot oem rebootRUU (case sensitive, phone screen goes black with silver HTC logo)
htc_fastboot flash zip firmware.zip (if it says something about pre hboot update you will have to issue this command again, however I think htc_fastboot does it all for you)
htc_fastboot flash zip firmware.zip
make sure it says successful at the end and OKAY then
fastboot reboot-bootloader
now when your in the bootloader, unlock your bootloader the usual way using the HTC Dev token.
now download TWRP recovery 2.8.6.0 and flash it: https://dl.twrp.me/m7/twrp-2.8.6.0-m7.img.html
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
now boot into twrp main screen only, keep your phone plugged into the computer and the internal storage should open on your computer, if it doesn't then you have a driver problem, check device manager, if it does then download the below link file and copy to your internal storage, unplug your phone and install the file. https://download.chainfire.eu/696/SuperSU
now fully reboot your phone and check that its correctly rooted.
you may now flash a kernel, rom's etc, do not lock or relock your bootloader unless you want to have to do all of this again.
That's it! THANK YOU SO MUCH!!!!!!!!!!! :highfive:
Just one last thing, how can I check if it is rooted or not?
Hipratboy said:
That's it! THANK YOU SO MUCH!!!!!!!!!!! :highfive:
Just one last thing, how can I check if it is rooted or not?
Click to expand...
Click to collapse
download root checker from play store, but when the phone 1st restart, open SuperSU from the app draw and just check to see if it asks you to update the binaries first.
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!!
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.