HTC One (M7) Unroot - One (M7) Q&A, Help & Troubleshooting

Hello people.
I need your help regarding my AT&T HTC One M7.
My phone is rooted, has unlocked bootloader, and stock recovery. I want to unroot it and lock the bootloader
I tried the method with locking the bootloader and flashing stock RUU compatible with my CID and MID, but when I locked the bootloader the device couldn't boot to Android. Instead, it booted to fastboot. Anyways I continouted with the process and I tried to install my RUU, but in the middle of installation it gave me [error 155]. It gave me the same error with any other RUU I tried to install, can you help me?
Here is what i get when i type "getvar all" command:
(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:xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(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: 4294mV
(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

Torcidas1950 said:
Hello people.
I need your help regarding my AT&T HTC One M7.
My phone is rooted, has unlocked bootloader, and stock recovery. I want to unroot it and lock the bootloader
I tried the method with locking the bootloader and flashing stock RUU compatible with my CID and MID, but when I locked the bootloader the device couldn't boot to Android. Instead, it booted to fastboot. Anyways I continouted with the process and I tried to install my RUU, but in the middle of installation it gave me [error 155]. It gave me the same error with any other RUU I tried to install, can you help me?
Here is what i get when i type "getvar all" command:
(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:xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(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: 4294mV
(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
Click to expand...
Click to collapse
I don't know which RUU did you try but here is 3.17.502.3 and 4.18.502.7. You might try these, make sure your bootloader is locked/relocked! Generally, the error 155 is the result of using the wrong RUU for your version. The two I provided are based on you hboot, try version 3 first then version 4.

majmoz said:
I don't know which RUU did you try but here is 3.17.502.3 and 4.18.502.7. You might try these, make sure your bootloader is locked/relocked! Generally, the error 155 is the result of using the wrong RUU for your version. The two I provided are based on you hboot, try version 3 first then version 4.
Click to expand...
Click to collapse
I am pretty much sure I tried both of them, I think it has something to do with the fact it doesn't write down any "version-main" number like the phone doesn't even have it. :/

I am pretty much sure I tried both of them, I think it has something to do with the fact it doesn't write down any "version-main" number like the phone doesn't even have it. :/
majmoz said:
I don't know which RUU did you try but here is 3.17.502.3 and 4.18.502.7. You might try these, make sure your bootloader is locked/relocked! Generally, the error 155 is the result of using the wrong RUU for your version. The two I provided are based on you hboot, try version 3 first then version 4.
Click to expand...
Click to collapse

Torcidas1950 said:
I am pretty much sure I tried both of them, I think it has something to do with the fact it doesn't write down any "version-main" number like the phone doesn't even have it. :/
Click to expand...
Click to collapse
Your missing version number is the result of being overwritten when you flashed a custom recovery. The newer custom recoveries have made changes to avoid that issue. Since, your phone isn't bootlooping then it is just cosmetic. You might try this 3.17.502.3 rom.zip. You would flash it in bootloader/FASTBOOT USB:
In a command window type:
Code:
[B][I]adb reboot bootloader[/I][/B]
After that, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip 3.17.502.3.rom.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip 3.17.502.3.rom.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse

majmoz said:
Your missing version number is the result of being overwritten when you flashed a custom recovery. The newer custom recoveries have made changes to avoid that issue. Since, your phone isn't bootlooping then it is just cosmetic. You might try this 3.17.502.3 rom.zip. You would flash it in bootloader/FASTBOOT USB:
Click to expand...
Click to collapse
Thanks, I will try that. But can I brick my phone or something else like that?

majmoz said:
Your missing version number is the result of being overwritten when you flashed a custom recovery. The newer custom recoveries have made changes to avoid that issue. Since, your phone isn't bootlooping then it is just cosmetic. You might try this 3.17.502.3 rom.zip. You would flash it in bootloader/FASTBOOT USB:
Click to expand...
Click to collapse
Should I maybe try this older RUU.exe
http://www.htc1guru.com/dld/ruu_m7_...20_10-40-1150-04_release_326691_signed_2-exe/

Can you run getvar all so we can see what firmware version you are on? Be sure to remove your IMEI and serial numbers.

MarkBell said:
Can you run getvar all so we can see what firmware version you are on? Be sure to remove your IMEI and serial numbers.
Click to expand...
Click to collapse
(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:xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(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: 4294mV
(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

the 3.17.502.3 ruu should work for you (with a relocked bootloader)
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
http://androidruu.com/getdownload.p...13_10.38j.1157.04_release_334235_signed_2.exe
what error did you get?

nkk71 said:
the 3.17.502.3 ruu should work for you (with a relocked bootloader)
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
http://androidruu.com/getdownload.p...13_10.38j.1157.04_release_334235_signed_2.exe
what error did you get?
Click to expand...
Click to collapse
Error 155, every time with any of these RUU's :/

Torcidas1950 said:
Error 155, every time with any of these RUU's :/
Click to expand...
Click to collapse
can you find the debug log, or use the ROM.ZIP in fastboot:
the usual procedure is:
fastboot oem rebootRUU
fastboot flash zip ROM.ZIP
fastboot flash zip ROM.ZIP <- yes twice!!
fastboot reboot-bootloader
but during the first flash it will throw an error, let's see what it is
to get the ROM.ZIP, run the RUU, once the first screen shows up there will be a new folder in %TEMP%, within it you will find a 1GB file called ROM.ZIP
if it's due to the missing version-main, you can fix that using the misctool http://forum.xda-developers.com/showthread.php?t=1526316

nkk71 said:
can you find the debug log, or use the ROM.ZIP in fastboot:
the usual procedure is:
fastboot oem rebootRUU
fastboot flash zip ROM.ZIP
fastboot flash zip ROM.ZIP <- yes twice!!
fastboot reboot-bootloader
but during the first flash it will throw an error, let's see what it is
to get the ROM.ZIP, run the RUU, once the first screen shows up there will be a new folder in %TEMP%, within it you will find a 1GB file called ROM.ZIP
if it's due to the missing version-main, you can fix that using the misctool http://forum.xda-developers.com/showthread.php?t=1526316
Click to expand...
Click to collapse
Can I do any damage to my phone if the ZIP RUU fails?

Torcidas1950 said:
Can I do any damage to my phone if the ZIP RUU fails?
Click to expand...
Click to collapse
nope, especially with S-ON and a signed/encrypted RUU.ZIP (the one contained in the RUU.EXE is signed/encrypted), so when you try to flash it using fastboot (which is the same thing the RUU.EXE does, but doesn't show textual progress - though there should be a log somewhere), the fastboot flash will start by various checks, if and only if all the checks pass (meaning the signature, MID, CID, etc are correct for your phone), the ruu will begin installation.
the first flash will do the hboot preupdate and say "failed flush again immediately", the second flash would continue flashing all other partitions

nkk71 said:
nope, especially with S-ON and a signed/encrypted RUU.ZIP (the one contained in the RUU.EXE is signed/encrypted), so when you try to flash it using fastboot (which is the same thing the RUU.EXE does, but doesn't show textual progress - though there should be a log somewhere), the fastboot flash will start by various checks, if and only if all the checks pass (meaning the signature, MID, CID, etc are correct for your phone), the ruu will begin installation.
the first flash will do the hboot preupdate and say "failed flush again immediately", the second flash would continue flashing all other partitions
Click to expand...
Click to collapse
So, does that mean it will fail like the RUU.exe did because I'ts the same way of installing, just its showing install wizard instead of CMD?

Torcidas1950 said:
So, does that mean it will fail like the RUU.exe did because I'ts the same way of installing, just its showing install wizard instead of CMD?
Click to expand...
Click to collapse
yes most probably it will fail, the RUU.EXE is basically just a "container" for the ruu.zip (called ROM.ZIP).... the exe will extract fastboot/adb/rom.zip/etc files into a temp directory and then basically do the commands i listed above.
(I do believe the "wizard" does some initial checks just for the sake of visual feedback, but the actual flashing is done using fastboot commands in the background)

nkk71 said:
yes most probably it will fail, the RUU.EXE is basically just a "container" for the ruu.zip (called ROM.ZIP).... the exe will extract fastboot/adb/rom.zip/etc files into a temp directory and then basically do the commands i listed above.
(I do believe the "wizard" does some initial checks just for the sake of visual feedback, but the actual flashing is done using fastboot commands in the background)
Click to expand...
Click to collapse
Then where can I find that debug log from previous attempts? Its too much things to do just to see where is the error

Torcidas1950 said:
Then where can I find that debug log from previous attempts? Its too much things to do just to see where is the error
Click to expand...
Click to collapse
probably in the temp folder i guess, not sure since i haven't used or checked and ruu.exe log in about forever

nkk71 said:
probably in the temp folder i guess, not sure since i haven't used or checked and ruu.exe log in about forever
Click to expand...
Click to collapse
Something like this? I have around 10 of these in my C:\Temp\HTC folder
Start time: 2014/6/22, 13:1:7
Main
readConfig ok
InitInstance
HSM OLD HTC driver 3.0 is not installed.
Check Driver Version = 4.11.0.001
HSM OLD HTC driver 4.0 is needed to be upgraded.
The USB driver is needed to be upgraded
HSM already installed
WMP version = 12.0.7601.18150
Copy Installer folder from H:\ to C:\TEMP\HTCDriver
HSM OLD HTC driver is not existed
Check Driver Version = 4.11.0.001
HSM OLD HTC driver is installed.
Start to uninstall HSM OLD htc driver.
Uninstall HSM OLD htc driver finished.
New Driver Version = 4.3.0.001
Start to execute HTCDriverInstaller.
HTCDriverInstaller is finished.
Delete Installer folder C:\TEMP\HTCDriver
Please replug USB cable before using the USB functions.
HTC Sync Manager autorun,finished
End time: 2014/6/22, 13:3:18

nkk71 said:
probably in the temp folder i guess, not sure since i haven't used or checked and ruu.exe log in about forever
Click to expand...
Click to collapse
Here is the file i found in C:\ruu_log\
I had to .zip it because it didn't want to upload in .log format

Related

I broke it, can you fix it?

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

[Q] Wiped OS and Wiped SDcard

Hello.
I have been trying to repair this by myself for 3 days reading this forum but I just can't do it.
My phone had unlocked bootloader, rooted and SOFF. When I was flashing a rom I don't know what happened but it deleted my OS.
Then I tried to update my firmware and it deleted my SD card. I'm stuck at TWPR recovery.
Now when I try to use a RUU installer it always shows an error, I also tried to use a RUU via fastboot command and it shows error 42. My bootloader is relocked btw.
I cannot sideload anything because my SD was wiped.
I'm now somewhat desperate. I just want my phone to revive.
My MODEL ID is PN0712000 and I got SuperCID 1111111
My firmware is version is 3.17.502.3.
PLEASE help me.
MsDosExe said:
Hello.
I have been trying to repair this by myself for 3 days reading this forum but I just can't do it.
My phone had unlocked bootloader, rooted and SOFF. When I was flashing a rom I don't know what happened but it deleted my OS.
Then I tried to update my firmware and it deleted my SD card. I'm stuck at TWPR recovery.
Now when I try to use a RUU installer it always shows an error, I also tried to use a RUU via fastboot command and it shows error 42. My bootloader is relocked btw.
I cannot sideload anything because my SD was wiped.
I'm now somewhat desperate. I just want my phone to revive.
My MODEL ID is PN0712000 This indicates your phone is AT&T or Developers edition and I got SuperCID 1111111
My firmware is version is 3.63.707.4.
PLEASE help me.
Click to expand...
Click to collapse
What Ruu did you try ?
and can you boot to bootloader and give me the results for
fastboot getvar all
minus your serial no and IEMI, I can help you much better with this info.
If you are s-off it should be no problem getting you up and running
clsA said:
What Ruu did you try ?
and can you boot to bootloader and give me the results for
fastboot getvar all
minus your serial no and IEMI, I can help you much better with this info.
If you are s-off it should be no problem getting you up and running
Click to expand...
Click to collapse
I'm trying RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2
These are my results from getvar:
C:\abd\platform-tools\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4319mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.072s
MsDosExe said:
I'm trying RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2
These are my results from getvar:
C:\abd\platform-tools\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4319mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.072s
Click to expand...
Click to collapse
Everything looks Good !!
Hold the power button and vol down till the phone reboots
continue holding just vol down back to the bootloader
then do
fastboot erase cache
fastboot reboot-bootloader
then to fastboot USB and start the RUU on your PC again (rebooting the PC before doing all this is a good idea also).(If your on windows 7 running the RUU as Administrator is good too)
Also check the md5 of the RUU you downloaded to make sure it's good
clsA said:
Everything looks Good !!
Hold the power button and vol down till the phone reboots
continue holding just vol down back to the bootloader
then do
fastboot erase cache
fastboot reboot-bootloader
then to fastboot USB and start the RUU on your PC again (rebooting the PC before doing all this is a good idea also).(If your on windows 7 running the RUU as Administrator is good too)
Also check the md5 of the RUU you downloaded to make sure it's good
Click to expand...
Click to collapse
I dit everything and the ruu installer keeps saying the same error.
"Error 155 IMAGE ERROR"
How can I check the MD5? Maybe that's the problem.
MsDosExe said:
I dit everything and the ruu installer keeps saying the same error.
"Error 155 IMAGE ERROR"
Click to expand...
Click to collapse
does the phone ever reboot to RUU mode ?
correct file and md5
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
clsA said:
does the phone ever reboot to RUU mode ?
Click to expand...
Click to collapse
When I run the installer it reboots in RUU Mode (the grey HTC letters) then it checks my phone, deletes my user data, and then it says "sending..." after that it fails and shows the 155 IMAGE ERROR and something about getting the right ROM.
How can I check the MD5? Maybe that's the problem.
MsDosExe said:
When I run the installer it reboots in RUU Mode (the grey HTC letters) then it checks my phone, deletes my user data, and then it says "sending..." after that it fails and shows the 155 IMAGE ERROR and something about getting the right ROM.
How can I check the MD5? Maybe that's the problem.
Click to expand...
Click to collapse
The post above yours
extract it to the desktop
go to the other link and copy the listed md5 for your ruu
then find you ruu in the bottom box and check it
if it's red you need to redownload
clsA said:
The post above yours
extract it to the desktop
go to the other link and copy the listed md5 for your ruu
then find you ruu in the bottom box and check it
if it's red you need to redownload
Click to expand...
Click to collapse
I got the wrong MD5 on the RUU. I downloaded the one you provided and my HTC One is back to life again.
Thank you very much. I have never figure it out without you.
MsDosExe said:
I got the wrong MD5 on the RUU. I downloaded the one you provided and my HTC One is back to life again.
Thank you very much. I have never figure it out without you.
Click to expand...
Click to collapse
I'm Glad your back up and running !!

[Q] Really bad brick maybe

Okay, so I'll give as much detail as possible.
Bought broken sprint phone, replaced the body. No issues there. I was trying to clean it up, flash a nice rom for my mom and make it work well. Well, I ended up clearing the OS, system, everything.
What I do have is access to fastboot. No recovery. I've tried a lot of RUUs, but I either get either Error 152, or it hangs on sending at 4%.
Any ideas?
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0515
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.03.651.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Mod edit: removed sensitive info.
(bootloader) imei: Mod edit: removed sensitive info.
(bootloader) meid: Mod edit: removed sensitive info.
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3799mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.054s
Cheers
@handicapped_chap
When you say "tried a bunch of RUU's" ... which ones have you tried?
Did you relock your bootloader before running the RUU's?
You might need to install Microsoft Visual C++ 2008 Dist.
Try installing HTC Sync Manager.
BD619 said:
@handicapped_chap
When you say "tried a bunch of RUU's" ... which ones have you tried?
Did you relock your bootloader before running the RUU's?
You might need to install Microsoft Visual C++ 2008 Dist.
Try installing HTC Sync Manager.
Click to expand...
Click to collapse
I've tried all the ones I've found here for Sprint, I've also gone to htcdev to try theirs. Yes. It is relocked, and I do have HTC Sync installed.
handicapped_chap said:
I've tried all the ones I've found here for Sprint, I've also gone to htcdev to try theirs. Yes. It is relocked, and I do have HTC Sync installed.
Click to expand...
Click to collapse
Anything older then 5.03.651.3 won't work because you are s-on.
Here is a link to the 4 - latest RUU's (3 of them you meed to click Show Content under Previous RUU's
http://forum.xda-developers.com/showthread.php?t=2795856
BD619 said:
Anything older then 5.03.651.3 won't work because you are s-on.
Here is a link to the 4 - latest RUU's (3 of them you meed to click Show Content under Previous RUU's
http://forum.xda-developers.com/showthread.php?t=2795856
Click to expand...
Click to collapse
Alright, cool thanks. I'll try the latest 3, as I tried the 4th I believe.
Any particular way I should flash it? Or just lock the bootloader, and fastboot flash zip firmware.zip like I've been doing?
handicapped_chap said:
Alright, cool thanks. I'll try the latest 3, as I tried the 4th I believe.
Any particular way I should flash it? Or just lock the bootloader, and fastboot flash zip firmware.zip like I've been doing?
Click to expand...
Click to collapse
The first 3 are exe files just click it and it will start
The 5.03.651.3 is a zip here are the instructions for that.
-Download ROM
-extract zip to a folder on your pc
-boot into bootloader (various ways)
-using fastboot, type this cmd: fastboot oem lock this will relock the bootloader (S-ON ONLY)
-from pc, run ARUWizard.exe from the extracted folder. it will run the RUU utility & flash back to stock
BD619 said:
The first 3 are exe files just click it and it will start
The 5.03.651.3 is a zip here are the instructions for that.
-Download ROM
-extract zip to a folder on your pc
-boot into bootloader (various ways)
-using fastboot, type this cmd: fastboot oem lock this will relock the bootloader (S-ON ONLY)
-from pc, run ARUWizard.exe from the extracted folder. it will run the RUU utility & flash back to stock
Click to expand...
Click to collapse
Alright, I'm trying the 5.03.651.3 right now. It's stuck on the sending 1/6. I'll just wait for that until the others download. I'm headed on holiday in about an hour. I'll remote desktop though for as much as I can. Thanks again.

HTC One m7 files ready for flashing

I'm trying to fix my bricked HTC One and I downloaded a file from: http://forum.xda-developers.com/showthread.php?t=2428276
I downloaded this ROM: RUU M7 UL JB43 SENSE50 MR TMOUS 3.24.531.3 Radio 4A.21.3263.03 10.38m.1157.04 Release 336982 Signed 2
How can I make this ROM capable of being flashed? Right now it is a zipped folder and I haven't been able to flash it.
What is your method of flashing? RUUs are not flashed the same way custom ROMs are. To flash a RUU you have to boot into fastboot, then use the command "fastboot oem rebootRUU." Then the screen goes black and you see a grey HTC logo; then you can flash the zip with "fastboot flash zip ------.zip." There's a progress bar on the screen that will never show complete. When your terminal screen on your PC tells you it's complete, you may then reboot with "fastboot reboot."
And when you say it's bricked... more details would be helpful. That could mean a whole lot of different things, some not all that bad (i.e. a bootloop), some could be VERY bad (a phone that won't power up and will never power up again)
And I strongly recommend that you post the output of "fastboot getvar all" before attempting anything since its look like its your first time flashing an HTC phone. The information from that command will tell us what file you need to flash exactly and how to proceed. Also describe your issue like asked above. (dont share your IMEI and Serial number btw)
firejuggler86 said:
What is your method of flashing? RUUs are not flashed the same way custom ROMs are. To flash a RUU you have to boot into fastboot, then use the command "fastboot oem rebootRUU." Then the screen goes black and you see a grey HTC logo; then you can flash the zip with "fastboot flash zip ------.zip." There's a progress bar on the screen that will never show complete. When your terminal screen on your PC tells you it's complete, you may then reboot with "fastboot reboot."
And when you say it's bricked... more details would be helpful. That could mean a whole lot of different things, some not all that bad (i.e. a bootloop), some could be VERY bad (a phone that won't power up and will never power up again)
Click to expand...
Click to collapse
By bricked I mean that when I try to turn the phone on it gets to the screen that says "HTC One" then it will not start. I did the command "fastboot oem rebootRUU" and the screen went black and I got a grey HTC logo. Then I entered the command "fastboot flash zip ROM.zip" and I got "error: cannot load 'ROM.zip'". I opened the command prompt in a folder called "fastboot-win" that I downloaded from htcdev.com. Should I open the command prompt in a different location?
alray said:
And I strongly recommend that you post the output of "fastboot getvar all" before attempting anything since its look like its your first time flashing an HTC phone. The information from that command will tell us what file you need to flash exactly and how to proceed. Also describe your issue like asked above. (dont share your IMEI and Serial number btw)
Click to expand...
Click to collapse
The RUU I downloaded has the same mid and cid as my phone so I think it is the correct one. The problem I am having is I am not able to flash the ROM.zip. It says "error: cannot load 'ROM.zip'". I think the problem is I am not opening the command prompt in the correct location. Where should I open the command prompt?
whitefishx said:
The RUU I downloaded has the same mid and cid as my phone so I think it is the correct one. The problem I am having is I am not able to flash the ROM.zip. It says "error: cannot load 'ROM.zip'". I think the problem is I am not opening the command prompt in the correct location. Where should I open the command prompt?
Click to expand...
Click to collapse
Cannot load "ROM.zip" mean that fastboot can't find the "ROM.zip" file either because your RUU file isn't named "ROM.zip" or because its not in the same folder as fastboot.exe.
The MID and CID must match but there is also some other thing to take in consideration like your current main-version number, your hboot version, S-ON or S-OFF bootloader, Locked, Unlocked or Re-Locked bootloader. So again, better to post your "fastboot getvar all" (don't post your IMEI/serialno)
alray said:
Cannot load "ROM.zip" mean that fastboot can't find the "ROM.zip" file either because your RUU file isn't named "ROM.zip" or because its not in the same folder as fastboot.exe.
The MID and CID must match but there is also some other thing to take in consideration like your current main-version number, your hboot version, S-ON or S-OFF bootloader, Locked, Unlocked or Re-Locked bootloader. So again, better to post your "fastboot getvar all" (don't post your IMEI/serialno)
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.10.531.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4305mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I figured out why it couldn't load; I had to enter "ROM.zip.zip" but unfortunately I got "FAILED (remote: 12 signature verify fail)". then I unlocked bootloader and it had another different error. I then found another RUU .exe file with the same os as my phone and it didn't work. I then tried flashing it through ClockworkMod but it said "Installation aborted." I think the problem is none of these RUU's are compatible with my phone especially since it is in s-on. Any suggestions? And is there any way in which I can get it to s-off?
whitefishx said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.10.531.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4305mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I figured out why it couldn't load; I had to enter "ROM.zip.zip" but unfortunately I got "FAILED (remote: 12 signature verify fail)". then I unlocked bootloader and it had another different error. I then found another RUU .exe file with the same os as my phone and it didn't work. I then tried flashing it through ClockworkMod but it said "Installation aborted." I think the problem is none of these RUU's are compatible with my phone especially since it is in s-on. Any suggestions? And is there any way in which I can get it to s-off?
Click to expand...
Click to collapse
Since your phone is S-ON, you can only flash RUU that are same or newer version than your actual version-main 6.10.531.10 or newer
You can't flash a RUU using a custom recovery
Your bootloader must be locked or re-locked to flash a RUU
So relock your bootloader and flash this ruu:
http://dl3.htc.com/application/RUU_...4_10.33E.1718.01L_release_405711_signed_2.exe
alray said:
Since your phone is S-ON, you can only flash RUU that are same or newer version than your actual version-main 6.10.531.10 or newer
You can't flash a RUU using a custom recovery
Your bootloader must be locked or re-locked to flash a RUU
So relock your bootloader and flash this ruu:
/RUU_M7_UL_K443_SENSE60_MR_TMOUS_6.10.531.10_Radio_4T.28.3218.04_10.33E.1718.01L_release_405711_signed_2.exe[/url]
Click to expand...
Click to collapse
Okay so I relocked my phone and ran the file you said (I already had it downloaded) and it worked. Thank you very much.

possible brickage

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..

Categories

Resources