Related
Help please?? I am trying to RUU my HTC One. I successfully relocked my bootloader.
However, when I start the process, it fails (unknown error). I am told that I need to use the "correct" RUU and try again. My problem is that the one I am using claims to be correct. Sprint_HTD_One_m7wls_1.29651.10_RUU.zip
I have noticed that when I am going through the RUU process I am shown the screen that asks to compare the current version with the new one. The current image version is blank. Nothing there. No current image version at all.
slaldrich said:
Help please?? I am trying to RUU my HTC One. I successfully relocked my bootloader.
However, when I start the process, it fails (unknown error). I am told that I need to use the "correct" RUU and try again. My problem is that the one I am using claims to be correct. Sprint_HTD_One_m7wls_1.29651.10_RUU.zip
I have noticed that when I am going through the RUU process I am shown the screen that asks to compare the current version with the new one. The current image version is blank. Nothing there. No current image version at all.
Click to expand...
Click to collapse
post the output of ''fastboot getvar all'' except imei and sn
alray said:
post the output of ''fastboot getvar all'' except imei and sn
Click to expand...
Click to collapse
Here it is:
version: 0.5
version-bootloader: 1.56.0000
version-baseband: N/A
version-cpld: none
version-microp:none
version- main:
version -misc: PVT SHIP S-ON
serialno: (you asked this not be included) but it is present
meid: number present, not included
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: SPCS_001
battery status: good
battery voltage: 4280mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4dab9d12
hbootpreupdate 11
gencheckpt: 0
I also notice that on the fastboot screen, it reads:
**TAMPERED**
**RELOCKED**
**SECURITY WARNING**
m7_WLS PVT SHIP S-ON RH
HBOOT- 1.56.0000
OpenDSP- v32. 120.274.0909
OS- (blank)
eMMC-boot 2048 MB
Jan.23 2014, 22:11:35.0
thanks for looking at this!
slaldrich said:
Here it is:
version: 0.5
version-bootloader: 1.56.0000
version-baseband: N/A
version-cpld: none
version-microp:none
version- main:
version -misc: PVT SHIP S-ON
serialno: (you asked this not be included) but it is present
meid: number present, not included
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: SPCS_001
battery status: good
battery voltage: 4280mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4dab9d12
hbootpreupdate 11
gencheckpt: 0
thanks for looking at this!
Click to expand...
Click to collapse
The RUU you are trying to flash is a downgrade, thats why you can't flash it. 1.29.651.10 is for hboot 1.44 and you are on 1.56. You need s-off to downgrade with a ruu.
Refer to the sprint htc one forum to see if this is possible to s-off your phone on hboot 1.56 and then downgrade using the ruu
or
flash a rom for sprint htc one.
alray said:
The RUU you are trying to flash is a downgrade, thats why you can't flash it. 1.29.651.10 is for hboot 1.44 and you are on 1.56. You need s-off to downgrade with a ruu.
Refer to the sprint htc one forum to see if this is possible to s-off your phone on hboot 1.56 and then downgrade using the ruu
or
flash a rom for sprint htc one.
Click to expand...
Click to collapse
I understand s-off isn't possible. can you give me direction for getting started with your second suggestion "flash a rom for sprint htc one"?
slaldrich said:
I understand s-off isn't possible. can you give me direction for getting started with your second suggestion "flash a rom for sprint htc one"?
Click to expand...
Click to collapse
first your bootloader is relocked, you'll need to unlock it.
flash twrp recovery for M7WLS (sprint variant)
then download a sprint compatible rom. You can find them here .
push it to your phone and flash it.
If you have questions about how to do any of these steps ask me here, we'll go step by step...
alray said:
first your bootloader is relocked, you'll need to unlock it.
flash twrp recovery for M7WLS (sprint variant)
then download a sprint compatible rom. You can find them here .
push it to your phone and flash it.
If you have questions about how to do any of these steps ask me here, we'll go step by step...
Click to expand...
Click to collapse
My basic problem is that my radios were not connecting with Sprint at all. So, I understand that I need to do a RUU to fix that. Flashing a custom rom won't fix that (?). Now, I am unlocked with S-on. I have TWRP available. When I reboot, I am taken to the HTC lock screen, but if I unlock it, I get a white HTC screen that lets me do nothing.
I just want to get it back to what I had when I took it out of the box. If you can walk me though this, I would appreciate it. I am NH if we can do this vocally.
slaldrich said:
I just want to get it back to what I had when I took it out of the box. If you can walk me though this, I would appreciate it. I am NH if we can do this vocally.
Click to expand...
Click to collapse
With s-on, its not possible to use the available ruu. You could use the latest guru reset rom available for your phone. Select the option to wipe, install stock recovery and stock radio.
http://www.htc1guru.com/dld/guru_reset_m7_sprint_3-04-651-2-zip/
alray said:
With s-on, its not possible to use the available ruu. You could use the latest guru reset rom available for your phone. Select the option to wipe, install stock recovery and stock radio.
Is it possible to get my s-off again? If so, how might I do that?
Click to expand...
Click to collapse
slaldrich said:
alray said:
With s-on, its not possible to use the available ruu. You could use the latest guru reset rom available for your phone. Select the option to wipe, install stock recovery and stock radio.
Is it possible to get my s-off again? If so, how might I do that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2633276
Click to expand...
Click to collapse
alray said:
slaldrich said:
okay, I got s-off. now, how do I downgrade hboot?
or
where do I go from here?
and... I really appreciate this!!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
slaldrich said:
alray said:
slaldrich said:
okay, I got s-off. now, how do I downgrade hboot?
or
where do I go from here?
and... I really appreciate this!!
Click to expand...
Click to collapse
download this ruu.zip http://www.htc1guru.com/dld/ruu-zip-m7_wls_jb_50_sprint_1-29-651-10_ruu_decrypted-zip/
save it in the same folder where adb and fastboot are
reboot your phone in bootloader mode, select fasboot, plug your usb cable.
open your command prompt from fastboot/adb folder
type:
Code:
fastboot oem rebootRUU
(make sure you use capital letter for RUU)
your phone will reboot in ruu mode, a black screen with a silver HTC logo
then type:
Code:
fastboot flash zip <name_of_ruu_you_have_downloaded>.zip (without < and >)
wait for the ruu to flash. It will probably output something like: failed, flush image again so do the same command again
Code:
fastboot flash zip <name_of_ruu_you_have_downloaded>.zip (without < and >)
then
Code:
fastboot reboot
your phone should boot to your stock rom.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
the download link from htcguru is broken... no download available there
Is there anything else I can use? a different link, perhaps?
slaldrich said:
the download link from htcguru is broken... no download available there
Is there anything else I can use? a different link, perhaps?
Click to expand...
Click to collapse
Don't forget to quote me for faster answer
I have just tested the link and it work fine for me, the download speed isn't great atm but you'll be able to get the file in maybe 1 hour (200-300 Kb/sec)
alray said:
Don't forget to quote me for faster answer
I have just tested the link and it work fine for me, the download speed isn't great atm but you'll be able to get the file in maybe 1 hour (200-300 Kb/sec)
Click to expand...
Click to collapse
The download has begun working but all my attempts truncate/stop at around 20MB... Nowhere near 1gb. I will keep trying -- because right now I have an HTC One with working Cyanogenmod... but no connectivity at all with Sprint.
Do you happen to have a copy you can throw in dropbox for me?
And... this is the first time I've ever used these forums, so, I am still learning what I am doing. Thanks for your patience
I did download a rom called
Sprint_HTC_One_3.04.651.2_Stock_Rooted_Odexed.zip
If I flash this, will it fix my radios or will it just put me deeper in the hole?
I am on my 10th try for the htc1guru ... but none has made it past 40mb
alray said:
Don't forget to quote me for faster answer
I have just tested the link and it work fine for me, the download speed isn't great atm but you'll be able to get the file in maybe 1 hour (200-300 Kb/sec)
Click to expand...
Click to collapse
I finally was able to download the entire file. Then, I carefully followed instructions as you sent...
At last step, I received a "failed 32 header error"
so, I repeated the flashboot flash zip command again. same error
repeated a third time. same error
did fastboot reboot and.... nothing still at cyanogenmod with no connectivity. It didn't take.
It went as planned up until the Failed message.
Please tell me you have another idea or a way to deal with this.
alray said:
Don't forget to quote me for faster answer
I have just tested the link and it work fine for me, the download speed isn't great atm but you'll be able to get the file in maybe 1 hour (200-300 Kb/sec)
Click to expand...
Click to collapse
I did finally get the entire file... and did everything you suggested. Unfortunately, I got a Failed remote "32 header error"
I repeated the whole procedure a second time. Still nothing. I checked the MD5 of the file and it apparently was corrupt.
SO... I was back to Cyanogenmod 11 with no Sprint. As a last ditch try before retiring to bed, I came upon a zip file that said it had Sprint radio files. I figured, heck, what have I got to lose? So, I flashed the small zip. and POOF... works! My phone is back AND I didn't have to go back to stock.
I do want to say THANK YOU for all your help. Knowing you were there to help me along encouraged me not to throw my phone under a passing truck. I am sure that once we got that dang file downloaded correctly, it would have worked.
Even though it didn't turn out as we started.... your help was immeasurable for me. Thanks again.
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA34NS902058
(bootloader) imei: 99-------------------1
(bootloader) meid: 99-----------------
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3885mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
after flash custom rom imei & baseband gone plezzzzzz help n i can not flash any RUU or official rom
smrussel said:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA34NS902058
(bootloader) imei: 99-------------------1
(bootloader) meid: 99-----------------
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3885mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
after flash custom rom imei & baseband gone plezzzzzz help n i can not flash any RUU or official rom
Click to expand...
Click to collapse
Did you flashed a sprint compatible custom rom? You can't flash custom roms for the M7_UL on your m7_wls, both phones haves different partitions layout. Reflash a sprint custom Ron using a sprint compatible custom recovery or flash the latest sprint ruu from htc website (Google search: htc support rom download).
Sent from my HTC One using XDA Labs
alray said:
Did you flashed a sprint compatible custom rom? You can't flash custom roms for the M7_UL on your m7_wls, both phones haves different partitions layout. Reflash a sprint custom Ron using a sprint compatible custom recovery or flash the latest sprint ruu from htc website (Google search: htc support rom download).
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
i tried to flash with sprint Ruu but flash could not complete due to an error
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
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.
Earlier i had 6.09.401.5 ROM on my phone. Bootloader showed that main os version is 6.13.708.1
CID was set to 11111111 with S-ON and LOCKED bootloader, HBOOT 1.57
I tried to install 7.17.1540 RUU but got a BRICK with 1.61 HBOOT.
Now main version os shows 6.13.708.1 (7.17.1540.4)
Have only access to fastboot. Screen shows HTC logo with 4 triangles. On USB disconnection shows recovery with only "RUU" text.
Tried to flash through fastboot 401 and 708 firmwares, but getting: SBL1 = Fail-PU or Signature verify failed etc.
By RUU having error 152 or 155 or 12.
Non RUU or ZIP won't flash.
Don't know, what to do, please help!
lyrgo23 said:
Earlier i had 6.09.401.5 ROM on my phone. Bootloader showed that main os version is 6.13.708.1
CID was set to 11111111 with S-ON and LOCKED bootloader, HBOOT 1.57
I tried to install 7.17.1540 RUU but got a BRICK with 1.61 HBOOT.
Now main version os shows 6.13.708.1 (7.17.1540.4)
Have only access to fastboot. Screen shows HTC logo with 4 triangles. On USB disconnection shows recovery with only "RUU" text.
Tried to flash through fastboot 401 and 708 firmwares, but getting: SBL1 = Fail-PU or Signature verify failed etc.
By RUU having error 152 or 155 or 12.
Non RUU or ZIP won't flash.
Don't know, what to do, please help!
Click to expand...
Click to collapse
You must complete the flash of the 7.17.1540 ruu to get out of ruu mode. What is your "fastboot getvar all"? Are you flashing a zip or exe ruu? If you are flashing a zip ruu are you using htc_fastboot.exe instead of fastboot.exe? Is the md5 good on your ruu?
Sent from my HTC One using XDA Labs
alray said:
You must complete the flash of the 7.17.1540 ruu to get out of ruu mode. What is your "fastboot getvar all"? Are you flashing a zip or exe ruu? If you are flashing a zip ruu are you using htc_fastboot.exe instead of fastboot.exe? Is the md5 good on your ruu?
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
Im using simple fastboot.exe. Tried to install through RUU (getting errors 152 and 155) and ZIP (but it won't flash images bigger than 1.5 GB). don't know about md5.
can't get "getvar all". But it has superCID with system image of 6.13.708.1. But came from service with 6.17.401.5 with unability to update by OTA.
lyrgo23 said:
Im using simple fastboot.exe. Tried to install through RUU (getting errors 152 and 155) and ZIP (but it won't flash images bigger than 1.5 GB). don't know about md5.
can't get "getvar all". But it has superCID with system image of 6.13.708.1. But came from service with 6.17.401.5 with unability to update by OTA.
Click to expand...
Click to collapse
You must use htc_fastboot.exe to flash a 7.xx.xxx.x ruu and you must check the md5 value of your ruu to confirm it's integrity. Why can't you post the output of "fastboot getvar all"? Need to know your Cid, mid, version-main, hboot version...
You also need s-off to flash a ruu that doesn't have the same base version. Your phone looks pretty messed up, that's why a complete "fastboot getvar all" would help determine the best way to get everything back to normal
Sent from my HTC One using XDA Labs
alray said:
You must use htc_fastboot.exe to flash a 7.xx.xxx.x ruu and you must check the md5 value of your ruu to confirm it's integrity. Why can't you post the output of "fastboot getvar all"? Need to know your Cid, mid, version-main, hboot version...
You also need s-off to flash a ruu that doesn't have the same base version. Your phone looks pretty messed up, that's why a complete "fastboot getvar all" would help determine the best way to get everything back to normal
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.708.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3C2W158269
(bootloader) imei: 355859056916623
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3855mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU (Hboot PreUpdate)
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 52(ms)
Tried to install RUU EXE Brightstar. Having error 152.
Tried to install 7.17.708.21 ZIP RUU. having error 51 partition update fail. Picture attached.
lyrgo23 said:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.708.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3855mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU (Hboot PreUpdate)
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 52(ms)
Click to expand...
Click to collapse
Hboot PreUpdate mean that the RUU wasn't flashed completely, it went trough the hboot pre-update (first flash) and is now waiting for the second flash to finish.
lyrgo23 said:
Tried to install RUU EXE Brightstar. Having error 152.
Click to expand...
Click to collapse
Your phone is S-ON, running a x.xx.708.x base, MID PN0710000.
Brightsar US (aka Dev Edititon) is a x.xx.1540.x bas for MID PN0712000
You can't use this ruu unless you achieve S-OFF and change your MID number.
lyrgo23 said:
Tried to install 7.17.708.21 ZIP RUU. having error 51 partition update fail. Picture attached.
Click to expand...
Click to collapse
So now your "fastboot getvar all" isn't the same....
version-main is now: 6.13.708.1 (7.18.708.21)
so you must complete the 7.18.708.21 flash to get out of RUU mode....
and I guess the boot-mode isn't "Hboot PreUpdate" anymore...?
Try to flash the RUU again using htc_fastboot.exe and copy/paste your command window in your next post so we can see everything.
but 7.18.708.21 RUU is for model PN0714000. Mine is PN0710000. shows image error
lyrgo23 said:
but 7.18.708.21 RUU is for model PN0714000. Mine is PN0710000. shows image error
Click to expand...
Click to collapse
Sorry I miss-read your getvar, this explain everything. You either don't have the right MID or the right version installed on your phone. This phone was clearly S-OFF at some point and someone either changed the MID or the firmware version (since they don't match together) and turned back S-ON. Supercid (11111111) also confirm that your phone was s-off. You already have supercid so CID doesn't matters, flash a RUU that match your MID like 7.19.401.xx. If this is still failing you'll need s-off again to fix it.
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..