Database Develop

htc one help

i have a htc one sprint , it was unlocked and rooted and am trying to put back to stock so i relocked it via oem relock , and tried to run ruu and had error 155 any help thanks

sns2k7 said:
i have a htc one sprint , it was unlocked and rooted and am trying to put back to stock so i relocked it via oem relock , and tried to run ruu and had error 155 any help thanks
Click to expand...
Click to collapse
post the output of ''fastboot getvar all'' except the IMEI, MEID and SERIALNO. A picture of the bootloader screen could also help. What ruu are you trying to use (what version - complete file name?)
btw you are in the HTC One GSM forum so be careful not to flash things for a GSM, yours is a sprint variant (CDMA).
http://forum.xda-developers.com/sprint-htc-one

alray said:
post the output of ''fastboot getvar all'' except the IMEI, MEID and SERIALNO. A picture of the bootloader screen could also help. What ruu are you trying to use (what version - complete file name?)
btw you are in the HTC One GSM forum so be careful not to flash things for a GSM, yours is a sprint variant (CDMA).
http://forum.xda-developers.com/sprint-htc-one
Click to expand...
Click to collapse
C:\mni>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.651.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA36KS909525
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3910mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d8b0f7651bb88c960f701ae91477674a
getvar:all FAILED (unknown status code)
finished. total time: 0.101s
i tried the ruu exe from this link http://forum.xda-developers.com/showthread.php?t=2250904 and it did not work , i found another stock rom one but phone has strange reboot after every 30 seconds so imtrying to get stock ruu

sns2k7 said:
C:\mni>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.651.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: remove
(bootloader) imei: remove
(bootloader) meid: remove
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3910mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d8b0f7651bb88c960f701ae91477674a
getvar:all FAILED (unknown status code)
finished. total time: 0.101s
i tried the ruu exe from this link http://forum.xda-developers.com/showthread.php?t=2250904 and it did not work , i found another stock rom one but phone has strange reboot after every 30 seconds so imtrying to get stock ruu
Click to expand...
Click to collapse
remove your IMEI, MEID and SERIALNO from your above post, sensitive data..
don't know which ruu.exe you are trying, can only found ruu.zip in this thread (please link me the correct page)
edit:
Use this ruu.zip 1.29.651.10 ruu .ZIP instead the .exe
with bootloader locked or re-locked:
Code:
fastboot oem rebootRUU
fastboot flash zip ruu_m7_wls_jb_50_sprint_1.29.651.10.zip
fastboot flash zip ruu_m7_wls_jb_50_sprint_1.29.651.10.zip
fastboot reboot
there is also a 1.29.651.10 guru reset rom you could use.

alray said:
don't know which ruu.exe you are trying, can only found ruu.zip in this thread (please link me the correct page)
remove your IMEI, MEID and SERIALNO from your above post, sensitive data...
edit:
Use this ruu.zip 1.29.651.10 ruu .ZIP instead the .exe
with bootloader locked or re-locked:
Code:
fastboot oem rebootRUU
fastboot flash zip ruu_m7_wls_jb_50_sprint_1.29.651.10.zip
fastboot flash zip ruu_m7_wls_jb_50_sprint_1.29.651.10.zip
fastboot reboot
there is also a 1.29.651.10 guru reset rom you could use.
Click to expand...
Click to collapse
I actually tried the ruu exe. and the exncrypted one worked but im still getting the rebooting every 30 seconds, i found one link in the cdma thread but noone has the answer public they just pmed it and went away

sns2k7 said:
I actually tried the ruu exe. and the exncrypted one worked but im still getting the rebooting every 30 seconds, i found one link in the cdma thread but noone has the answer public they just pmed it and went away
Click to expand...
Click to collapse
What have you done with the phone before trying to restore to stock? Did you flashed anything wrong (i.e not for a CDMA variant)?
If you still get reboots after a successful ruu, there is something bad, either an hardware problem or you messed some partitions that are not restored by the ruu.

alray said:
What have you done with the phone before trying to restore to stock? Did you flashed anything wrong (i.e not for a CDMA variant)?
If you still get reboots after a successful ruu, there is something bad, either an hardware problem or you messed some partitions that are not restored by the ruu.
Click to expand...
Click to collapse
yes i accidentally flashed a gsm rom it didnt boot at all, so i restored a old backup and thats when it started

Can't return HTC One to Stock

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

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

alray said:
post the output of "fastboot getvar all" excluding the IMEI and SERIALNO so we can determine what file you need. Btw, do never use the 1.20.401.1 RUU. This version is like a pre-release verison and will not get updated with OTA.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 4161mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks for the tip:good:

Jonymacarrony said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 4161mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks for the tip:good:
Click to expand...
Click to collapse
You can't use a RUU to restore your phone because its S-ON. You can only use older RUU with S-OFF and there are no RUU that match your current version. You could flash a stock odex rom if you can find one You can find it on ARHD website. According to your hboot version, I think you should use a 5.11.401.10 rom + the stock recovery.
or you will need to s-off and use the 1.28.401 ruu

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Q] Stuck in Fastboot RUU mode

So to begin I failed miserably trying to reinstall a stockROM for my HTC. Using an RUU for a Rogers phone the RUU i could find apparently has a corrupted file and has left me stranded with a relocked device without S-OFF in the fastboot RUU menu. The problem is I cant manually flash a zip because fastboot says its too large and its impossible to unlock because a big HTC error screen is up whenever the phone is connected to my PC. I was wondering if anyone had any problems similar to this and could help me out. I have no warranty left and the only people who have had this happen seem to have access to the HBOOT menu which i do not. If anyone can provide some insight it would be appreciated.
GETVAR LOG:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.631.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4120mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU (Hboot PreUpdate)
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

DCaterer said:
So to begin I failed miserably trying to reinstall a stockROM for my HTC. Using an RUU for a Rogers phone the RUU i could find apparently has a corrupted file and has left me stranded with a relocked device without S-OFF in the fastboot RUU menu. The problem is I cant manually flash a zip because fastboot says its too large and its impossible to unlock because a big HTC error screen is up whenever the phone is connected to my PC. I was wondering if anyone had any problems similar to this and could help me out. I have no warranty left and the only people who have had this happen seem to have access to the HBOOT menu which i do not. If anyone can provide some insight it would be appreciated.
GETVAR LOG:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.631.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4120mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU (Hboot PreUpdate)
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Remove your IMEI and Serialno from your above post.
What makes you believe the file is corrupted?
What ruu version are you trying to flash exactly? 4.19.631.9? 7.17.631.7?

alray said:
Remove your IMEI and Serialno from your above post.
What makes you believe the file is corrupted?
What ruu version are you trying to flash exactly? 4.19.631.9? 7.17.631.7?
Click to expand...
Click to collapse
I'm trying to flash 4.19.631.9 because that is the only Rogers RUU i could find and the reason I think it is corrupted is because the ROM file from the RUU temp files was corrupted and empty. I re downloaded the RUU twice but the same things happened. The utility also gave me an Error 152 System image error and on the error screen on my phone when it is unplugged it shows the OS in red (assuming it is deleted) and the an area CIR says FAIL-PU.
If you knew where I could get an updated ROGERS001 CID RUU that would be awesome but I havent been able to :L.
Edit:Managed to unlock device but still stuck in Fastboot RUU mode.

DCaterer said:
I'm trying to flash 4.19.631.9 because that is the only Rogers RUU i could find and the reason I think it is corrupted is because the ROM file from the RUU temp files was corrupted and empty. I re downloaded the RUU twice but the same things happened.
Click to expand...
Click to collapse
Did you checked the MD5 value of the RUU before flashing? Don't forget that rom.zip from the ruu is encrypted and attempting to open this file will output some "file corrupted" error.
The utility also gave me an Error 152 System image error and on the error screen on my phone when it is unplugged it shows the OS in red (assuming it is deleted) and the an area CIR says FAIL-PU.
Click to expand...
Click to collapse
Your phone is stuck in RUU mode as you can see from your "fastboot getvar all" because it failed the pre-update (FAIL - PU). CIR is the partition for the Infrared port (Consumer Infra Red). So looks like this part of the flash failed.
Your OS version in red indicate that the ruu flash didn't complete and that the phone is still waiting to be flashed. The phone will keep rebooting to ruu mode until its flashed correctly.
Were you on 4.19.631.9 before attempting to flash the 4.19.631.9 RUU?
If you knew where I could get an updated ROGERS001 CID RUU that would be awesome but I havent been able to :L.
Click to expand...
Click to collapse
There is a lollipop RUU for Rogers but will not help at this time. Your phone must be at least on hboot 1.57 to flash a lollipop RUU.

alray said:
Did you checked the MD5 value of the RUU before flashing? Don't forget that rom.zip from the ruu is encrypted and attempting to open this file will output some "file corrupted" error.
Your phone is stuck in RUU mode as you can see from your "fastboot getvar all" because it failed the pre-update (FAIL - PU). CIR is the partition for the Infrared port (Consumer Infra Red). So looks like this part of the flash failed.
Your OS version in red indicate that the ruu flash didn't complete and that the phone is still waiting to be flashed. The phone will keep rebooting to ruu mode until its flashed correctly.
Click to expand...
Click to collapse
I'm not sure what I should be looking for in the MD5 : 6ec60cc5e59d4e342a946405471d1218
This RUU was from htcguru the only place i could find it its name is:
RUU M7 UL K44 SENSE55 MR Rogers WWE 4.19.631.9 Radio 4A.23.3263.28 10.38r.1157.04L Release 351317 Signed 2
alray said:
Were you on 4.19.631.9 before attempting to flash the 4.19.631.9 RUU?
Click to expand...
Click to collapse
Yes I was on the same version apparently., at least according to the RUU. I know it sounds silly to flash the same version but my phone is not stock and even TWRP or CWM cant boot as it is waiting to be flashed correctly (according to you). Overlooked that the rom was encrypted silly me :L.

Is their a way to get out of RUU mode or is it required to flash a new RUU. Tried again still no luck cant access phone with adb so its hard to do anything and fastboot oem is just for dev edition so that doesnt work. Do you know of a ROGERS001 RUU zip file or has noone managed to get it into zip format.

DCaterer said:
I'm not sure what I should be looking for in the MD5 : 6ec60cc5e59d4e342a946405471d1218
This RUU was from htcguru the only place i could find it its name is:
RUU M7 UL K44 SENSE55 MR Rogers WWE 4.19.631.9 Radio 4A.23.3263.28 10.38r.1157.04L Release 351317 Signed 2
Click to expand...
Click to collapse
You must check the md5 value on your ocmputer once the file is downloaded. Both value must match (on your computer and that one from htc1guru.com)
Use winmd5.exe to check your md5, use google search, you'll find it easily.

Alright so both md5 match but the same error comes up during RUU, CIR partition continues to fail.

DCaterer said:
Alright so both md5 match but the same error comes up during RUU, CIR partition continues to fail.
Click to expand...
Click to collapse
There might be an issue with your emmc chip (memory). That would explain why the CIR partition can't be flashed. Can you post the output of
Code:
fastboot oem dmesg
and
Code:
fastboot oem last_dmesg

alray said:
There might be an issue with your emmc chip (memory). That would explain why the CIR partition can't be flashed. Can you post the output of
Code:
fastboot oem dmesg
and
Code:
fastboot oem last_dmesg
Click to expand...
Click to collapse
Text lines are huge threw them up on dropbox on txt documents.
Alright here is dmesg:
https://www.dropbox.com/s/0hgxz5wglezex0e/Dmesg.txt?dl=0
and last_dmesg:
https://www.dropbox.com/s/h2z5ddx45vw2zie/last dmesg.txt?dl=0

Ok dont worry about it anymore decided to get an htc one m8 found one for 250$ brand new. But if you figure out the problem let me know so i can avoid my mistakes from the past

DCaterer said:
Ok dont worry about it anymore decided to get an htc one m8 found one for 250$ brand new. But if you figure out the problem let me know so i can avoid my mistakes from the past
Click to expand...
Click to collapse
I don't think you have made any mistakes here. The only thing I can think to get out of ruu mode on a s-on phone is to flash a ruu or a firmware. RUU doesn't work and can't find any firmware of this version. Maybe flashing the firmware.zip from the same version ota update could work, then from there I would try to s-off and try some other things...

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