Database Develop

[Q] Returning to stock now have S-On and locked with no ROM, HELP!

I am trying to return my phone to stock to send it in for replacement (microphone stopped working). I tried to run the Tmo RUU file a couple of times before I found the tutorial on how to properly do it and I am not sure if that may situation worse.
Somehow I wiped the phone and now and am S-On and its locked (showing as tampered). I cannot get the phone to go into any mode that adb can see, although I can access the phone via fastboot commands. What are my options at this point? Is there a way to load a ROM via fastboot? Is there a way to get S-Off and unlock it so I can try the steps to go back to to 100% stock again or am I screwed?
The phone on Tmobile is currently running Hboot 1.44 if that makes a difference.
PLEASE HELP!!!

Can you get to boatloader?

yes, I am in bootloader mode right now. I just successfully unlocked the bootloader from HTCDev. So now I am unlocked with S-On. I also have TWRP 2.6.3.0 and can access recovery. I also was able to set my CID back to T-MOB010.
It seems like I can do anything i want with fastboot commands, but none in adbd. Is there a way to load a rom from fastboot?
an0ther said:
Can you get to boatloader?
Click to expand...
Click to collapse

Your ruu must match your firmware on your phone. If your firmware is higher than your ruu it won't work. What firmware is the stock tmobile and what is your phone os and cid? You can always soff, change cid to stock, rebootRUU and flash stock ruu then s-on and relock.

I am running 3.17 fw and I am not sure what the RUU fw was, most likely 2.17 or something. I did not realize it would be an issue. So what are my options to get it back to stock?
This is what Getvar all says...
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4T.20.3218.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(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: 4255mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 1.930s
an0ther said:
Your ruu must match your firmware on your phone. If your firmware is higher than your ruu it won't work. What firmware is the stock tmobile and what is your phone os and cid? You can always soff, change cid to stock, rebootRUU and flash stock ruu then s-on and relock.
Click to expand...
Click to collapse

You will have to soff to downgrade firmware on phone. Soff, get stock ruu that matches your cid, rebootRUU and flash stock ruu, s-on, and relock

Can I get S-Off through fastboot? I try and run Revone via HTC One Toolkit and it outputs with error: device not found. I am assuming it is because I cant see it in adb.
an0ther said:
You will have to soff to downgrade firmware on phone. Soff, get stock ruu that matches your cid, rebootRUU and flash stock ruu, s-on, and relock
Click to expand...
Click to collapse

Adb devices , you get nothing? Might need newer adb or try another usb port. Reboot phone and computer. Need adb.

Is adb accessible via the bootloader or recovery? I thought adb only worked when you were booted into a rom. I am completely removing the HTC drivers and installing version 3.0.0.007 to see if it helps with adb.
an0ther said:
Adb devices , you get nothing? Might need newer adb or try another usb port. Reboot phone and computer. Need adb.
Click to expand...
Click to collapse

WiKDMoNKY said:
Is adb accessible via the bootloader or recovery? I thought adb only worked when you were booted into a rom. I am completely removing the HTC drivers and installing version 3.0.0.007 to see if it helps with adb.
Click to expand...
Click to collapse
Adb is accessible from recovery. Try updating HTC drivers and your adb. Sometimes using an USB 3 port causes issues.

Ok, I tried a different computer and now the toolkit is detecting the phone in adb and fastboot, but when I try to push revone it says this adb push revone /data/local/tmp/
failed to copy 'revone' to '/data/local/tmp/': Is a directory
WTF?

I have same problem please help......!!!!
HELLO EVERYONE PLEASE HELP..............
My HTC ONE IS
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.20.3263.16
x.xx.666.x - Bell (Canada)
modelid: PN0712000
cidnum: BM___001
I was trying to unroot my device, and i have followed commands as below, i have installed file given at below link
http://arhd.onedroid.net/db_mirror/Firmware/index.php?dir=HTC/HTC_One/666/
1) fastboot oem lock
2) fastboot oem rebootRUU
3) fastboot flash zip (firmware).zip
green bar stopped at round about 90% , after waiting 2 minutes i entered
4) fastboot reboot
now phone rebooted but nothing happens only blank screen appears.
i have again unlocked it, i can access bootloader, somehow i have also managed to install recovery,
I HAVE SYSTEM BACKUP IN MY LAPTOP
but i cannot transfer my backup file from laptop to htc one
---------------------------------------
C:\HTCONE>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.23.666.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34PW904746
(bootloader) imei: 354439053702181
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3816mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-a6a74fd020
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
--------------------------------------------------
WHAT SHOULD I DO ?? PLEASE HELP
MY PREFRENCE IS TO RESOTRE IT WITH SOTCK FIRMWARE UNROOTED.

Your issue is different than mine, go start your own thread please.
vasa_pratik said:
HELLO EVERYONE PLEASE HELP..............
My HTC ONE IS
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.20.3263.16
x.xx.666.x - Bell (Canada)
modelid: PN0712000
cidnum: BM___001
I was trying to unroot my device, and i have followed commands as below, i have installed file given at below link
http://arhd.onedroid.net/db_mirror/Firmware/index.php?dir=HTC/HTC_One/666/
1) fastboot oem lock
2) fastboot oem rebootRUU
3) fastboot flash zip (firmware).zip
green bar stopped at round about 90% , after waiting 2 minutes i entered
4) fastboot reboot
now phone rebooted but nothing happens only blank screen appears.
i have again unlocked it, i can access bootloader, somehow i have also managed to install recovery,
I HAVE SYSTEM BACKUP IN MY LAPTOP
but i cannot transfer my backup file from laptop to htc one
---------------------------------------
C:\HTCONE>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.23.666.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34PW904746
(bootloader) imei: 354439053702181
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3816mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-a6a74fd020
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
--------------------------------------------------
WHAT SHOULD I DO ?? PLEASE HELP
MY PREFRENCE IS TO RESOTRE IT WITH SOTCK FIRMWARE UNROOTED.
Click to expand...
Click to collapse

you have a tmobile htc one? Me too. I had the same error but was able to get S-OFF by following this guide: http://rootzwiki.com/topic/96098-s-offdowngrade-12753111-to-1275318
If that doesn't work I would
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
boot in to recovery
Wipe -> format all data -> Yes
go back to the main menu and go to advanced then ADB sideload. Swipe to start adb sideload
on pc type adb sideload romname.zip I'd use a stock rom since they don't normally use aroma
adb sideload will automatically install the rom and reboot
now that your phone is functioning normally gain s-off using revone like usual.
try downgrading again.

I followed your steps, but I get a failed on installation of the sideload on the phone.
blu9987 said:
I would
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
boot in to recovery
Wipe -> format all data -> Yes
go back to the main menu and go to advanced then ADB sideload. Swipe to start adb sideload
on pc type adb sideload romname.zip I'd use a stock rom since they don't normally use aroma
adb sideload will automatically install the rom and reboot
now that your phone is functioning normally gain s-off using revone like usual.
try downgrading again.
p.s. you have a tmobile htc one? Me too. I had the same error but was able to get S-OFF by following this guide, which would probably let you skip everything I posted above: http://rootzwiki.com/topic/96098-s-offdowngrade-12753111-to-1275318
Click to expand...
Click to collapse

If you reboot recovery the zip will still be there labeled sideload.zip if you want to try to install it again manually.
or you could try the modified ruu in the link. It worked for me but be advised in general RUUs can be dangerous.
edit: that guide says to be on the android homescreen, i've been able to run RUUs from the locked bootloader screen just fine.

Downloading...
blu9987 said:
If you reboot recovery the zip will still be there labeled sideload.zip if you want to try to install it again manually.
or you could try the modified ruu in the link. It worked for me but be advised in general RUUs can be dangerous.
edit: that guide says to be on the android homescreen, i've been able to run RUUs from the locked bootloader screen just fine.
Click to expand...
Click to collapse

I got ARHD 22 to load via sideload (had to boot back into recovery and install form the sideload.zip). The rom boots and works as it should. Now when I try and relock the bootloader to run the RUU downgrader you linked me to revone is giving me revone failed (error code = 1).
adb push revone /data/local/tmp/
3279 KB/s (648208 bytes in 0.193s)
adb shell chmod 755 /data/local/tmp/revone
adb shell /data/local/tmp/./revone -P
revone v0.2.1
revone failed (error code = 1)
Any ideas?
blu9987 said:
If you reboot recovery the zip will still be there labeled sideload.zip if you want to try to install it again manually.
or you could try the modified ruu in the link. It worked for me but be advised in general RUUs can be dangerous.
edit: that guide says to be on the android homescreen, i've been able to run RUUs from the locked bootloader screen just fine.
Click to expand...
Click to collapse

to relock the bootloader you do fastboot oem lock from the bootloader screen, then you run the ruu i linked if you still want to use revone to get s-off.

When I run fastboot OEM lock it shows as re-locked and something about security at the top of the bootloader screen. Will flashing the ruu fix all that?
blu9987 said:
to relock the bootloader you do fastboot oem lock from the bootloader screen, then you run the ruu i linked if you still want to use revone to get s-off.
Click to expand...
Click to collapse
Sent from my Nexus 7 using Tapatalk 4

[Q] HTC One international not working

Hey all. A some time ago I rooted my phone, unlocked bootloader, no S-OFF, and installed HD Revolution, 31.6 or something and it worked great for a good two months. But now my phone got jammed, I booted it and it doesn't work. Can't access recovery or start the phone, when I go to bootloader and try to go to recovery, it says entering recovery and boots again. I've tried to install multiple RUU's via fastboot method but it won't work. I always get the message remote: 24 parsing android info file. Tried to relock bootloader and then it gives the error 12 parsing android info file error.
So where to now? Can't get adb to work, tried multiple ways. It could've been the solution to boot to recovery? Can't boot to recovery via fastboot. Any ideas?

Have you tried reflashing recovery via fastboot?
Can you boot to recovery via fastboot with a recovery img file stored on your PC?

shaitan667 said:
Have you tried reflashing recovery via fastboot?
Can you boot to recovery via fastboot with a recovery img file stored on your PC?
Click to expand...
Click to collapse
I've tried reflashing multiple recoveries multiple times, and always did fastboot erase cache. Couldn't boot to recovery via fastboot command also, phone just jammed for 10minutes.
And I just figured out, I can't get adb working because I can't start my phone. Am I correct?

hessusi said:
I've tried reflashing multiple recoveries multiple times, and always did fastboot erase cache. Couldn't boot to recovery via fastboot command also, phone just jammed for 10minutes.
And I just figured out, I can't get adb working because I can't start my phone. Am I correct?
Click to expand...
Click to collapse
N o as long as it switches on you are fine boot into
You need the info in these threads, read carefully before you make any moves
http://forum.xda-developers.com/showthread.php?t=2365506
http://forum.xda-developers.com/showthread.php?t=2265618

L0rdNels0n said:
N o as long as it switches on you are fine boot into
You need the info in these threads, read carefully before you make any moves
http://forum.xda-developers.com/showthread.php?t=2365506
http://forum.xda-developers.com/showthread.php?t=2265618
Click to expand...
Click to collapse
As said, I can't get adb to work. I think the phone should be started for it to work, but as said, I can't start it. Only available to bootloader etc.
I just want to know why the recovery won't work, I've installed many recoveries many time, everytime it says entering recovery, and then just boots. And boots again for a million times, but what is the reason?
I'm trying to boot the recovery through fastboot, but the phone just freezes. Well I'll wait for 30min and we'll see if it works. I doubt.
Is there any Roms or RUUs I could install straight from fastboot?
So is the problem that I've got hboot 1.55? And I can't downgrade it because I can't use adb. Where to now? Anyone?

According to other One users, this problem occures, if a wrong version recovery is used. I've tried every CWM version for every HTC One, international, verizon, AT&T and so on including touch versions but none of them works. So can anyone help me? I can't use adb at all.Anything to do or should I throw it out of the window?

hessusi said:
According to other One users, this problem occures, if a wrong version recovery is used. I've tried every CWM version for every HTC One, international, verizon, AT&T and so on including touch versions but none of them works. So can anyone help me? I can't use adb at all.Anything to do or should I throw it out of the window?
Click to expand...
Click to collapse
Does anyone have any answers?

What is your fastboot getvar all output ? Remove imei/SN
Have you tried this?
Fastboot flash recovery recover.IMG
Fastboot erase cache
sent from my mobile device

According to other One users, this problem occures, if a wrong version recovery is used. I've tried every CWM version for every HTC One, international, verizon, AT&T and so on including touch versions but none of them works.
Click to expand...
Click to collapse
hessusi said:
Does anyone have any answers?
Click to expand...
Click to collapse
yeah .. if you flashed a cdma recovery on your GSM phone you probably killed the partition structure and it's not easy to fix.
Their are a couple of guys here that can do it, but it's way over my head, ... maybe @nkk71 will help you

hessusi said:
According to other One users, this problem occures, if a wrong version recovery is used. I've tried every CWM version for every HTC One, international, verizon, AT&T and so on including touch versions but none of them works. So can anyone help me? I can't use adb at all.Anything to do or should I throw it out of the window?
Click to expand...
Click to collapse
how about we start with a "fastboot getvar all" (only show us the first two characters of IMEI, MEID, and s/n) and also the link(s) of what you flashed.

nkk71 said:
how about we start with a "fastboot getvar all" (only show us the first two characters of IMEI, MEID, and s/n) and also the link(s) of what you flashed.
Click to expand...
Click to collapse
I installed all CWM recoveries for any HTC One.. verizon at&t, all of them. So I did only more damage huh? Well, let's see if you can help me now. Here's the info you asked: IMEI 35, MEID 00, s/n MB. That's all?

hessusi said:
I installed all CWM recoveries for any HTC One.. verizon at&t, all of them. So I did only more damage huh? Well, let's see if you can help me now. Here's the info you asked: IMEI 35, MEID 00, s/n MB. That's all?
Click to expand...
Click to collapse
no ...like this
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) imei: 35xxxxxxxxxxxxxx
(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: 4314mV
(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.062s
C:\fastboot>fastboot reboot
rebooting...
finished. total time: 0.042s
Click to expand...
Click to collapse

(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: MBxxxxxxxxxxxx
(bootloader) imei: 35xxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4024mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.068s
There you go.

hessusi said:
Hey all. A some time ago I rooted my phone, unlocked bootloader, no S-OFF, and installed HD Revolution, 31.6 or something and it worked great for a good two months. But now my phone got jammed, I booted it and it doesn't work. Can't access recovery or start the phone, when I go to bootloader and try to go to recovery, it says entering recovery and boots again. I've tried to install multiple RUU's via fastboot method but it won't work. I always get the message remote: 24 parsing android info file. Tried to relock bootloader and then it gives the error 12 parsing android info file error.
So where to now? Can't get adb to work, tried multiple ways. It could've been the solution to boot to recovery? Can't boot to recovery via fastboot. Any ideas?
Click to expand...
Click to collapse
I had this issue and is annoying how long it took to me fix. I had to try and get adb to work on several computers and eventually it did, from there I installed everything stock then unlocked the phone and root, install custom recovery and s-off with chosen rom. Now if you install twrp the latest version and sideload a Rom you will be good to go or get a usb otg. I was able to install custom recovery by adb but couldn't do anything else. I was able to sideload using twrp recovery in adb
Sent from my HTC One using XDA Premium 4 mobile app

hessusi said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: MBxxxxxxxxxxxx
(bootloader) imei: 35xxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4024mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.068s
There you go.
Click to expand...
Click to collapse
Well you know how to flash recovery lets try one more time with the correct one.
Download this >>http://techerrata.com/browse/twrp2/m7ul
put it in your fastboot folder and md5 check it - f428caf36c9c337e2ae417fc10fbe165
if it's ok continue
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
after the last step use volume down to select bootloader then volume down to select recovery (power button to select)
can you get into twrp now ?

clsA said:
Well you know how to flash recovery lets try one more time with the correct one.
Download this >>http://techerrata.com/browse/twrp2/m7ul
put it in your fastboot folder and md5 check it - f428caf36c9c337e2ae417fc10fbe165
if it's ok continue
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
after the last step use volume down to select bootloader then volume down to select recovery (power button to select)
can you get into twrp now ?
Click to expand...
Click to collapse
No, didn't work. Instant power off when I press recovery. Tried again and it just keeps saying entering recovery... Aaaand a bootloop again. So same thing with this one. What's next?

hessusi said:
No, didn't work. Instant power off when I press recovery. Tried again and it just keeps saying entering recovery...
Click to expand...
Click to collapse
well maybe a RUU will rebuild your partitions
lets look, Go here and find the RUU that matches
3.62.401.1
PN0710000
HTC__Y13
http://www.htc1guru.com/downloads
Well after looking it seems without s-off your done
Try and get s-off with rumrunner

clsA said:
well maybe a RUU will rebuild your partitions
lets look, Go here and find the RUU that matches
3.62.401.1
PN0710000
HTC__Y13
http://www.htc1guru.com/downloads
Well after looking it seems without s-off your done
Try and get s-off with rumrunner
Click to expand...
Click to collapse
I thought that adb is unavailable if phone can't be powered on? Atleast I can't get it to work.. And I tried RUU and it was correct but couldn't get it to work.

hessusi said:
I thought that adb is unavailable if phone can't be powered on? Atleast I can't get it to work.. And I tried RUU and it was correct but couldn't get it to work.
Click to expand...
Click to collapse
actually adb works fine ...in recovery or booted phone

clsA said:
actually adb works fine ...in recovery or booted phone
Click to expand...
Click to collapse
I can't access recovery.

HTC One (M7) Unroot

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

[SOLVED]HTC one M7 - Not Starting - Issue while updating to Lollipop

I have tried updating the htc one m7 to lollipop and during installation phone went into recovery mode. this is the getvar log from device. currently i have an unlocked bootloader.
(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.07.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4116mV
(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
all: Done!
finished. total time: 0.049s
can some one guide on how to proceed forward?
One more issue is im unable to connect the phone to laptop. i have tried installing a custom ROM.

[email protected] said:
I have tried updating the htc one m7 to lollipop and during installation phone went into recovery mode. this is the getvar log from device. currently i have an unlocked bootloader.
(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.07.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4116mV
(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
all: Done!
finished. total time: 0.049s
can some one guide on how to proceed forward?
One more issue is im unable to connect the phone to laptop. i have tried installing a custom ROM.
Click to expand...
Click to collapse
its very easy to fix, all you have to do is run the dev edition RUU again to make sure everything is fully stock for the update to work, however, your real issue is the fact it wont connect to your laptop, why not ? whats it doing ? what does device manager say ?

Ok. Connecting to computer im least bothered. I need it to be up and running.
I have unlocked bootloader, installed TWRP 2.7.1.1. Where can i get the dev edition RUU? Can i just run it from system by connecting phone in fastboot?

[email protected] said:
Ok. Connecting to computer im least bothered. I need it to be up and running.
I have unlocked bootloader, installed TWRP 2.7.1.1. Where can i get the dev edition RUU? Can i just run it from system by connecting phone in fastboot?
Click to expand...
Click to collapse
your computer needs to see the phone whilst the phone is in fastboot mode in the bootloader for anything to work, but the the updated lollipop RUU is here: http://forum.xda-developers.com/htc-one/general/guide-convert-m7-developer-edition-t2840311

Yeah, system is able to read commands from fastboot. So i have follow the 2nd part of the link above?

[email protected] said:
Yeah, system is able to read commands from fastboot. So i have follow the 2nd part of the link above?
Click to expand...
Click to collapse
yes just the 2nd part as your already on dev edition, if it fails, you may have to download and install the firmware first, due to you running a custom recovery, you can find the firmware here, thanks to @alray https://www.androidfilehost.com/?w=files&flid=20283, you will want the 6.07.1540.2 firmware which matches your version main.

I have connected the device in fastboot and ran the RUU, but it failed saying Recovery, and then it exited the process on computer. But my phone is still in the same silver htc logo, does it mean its installing or it failed to install? And BTW how do i install that firmware and also there a few versions if the same firmware!
If you can help me with sorting out this it would be of great help!! Thanks in advance for all the help till now...

[email protected] said:
I have connected the device in fastboot and ran the RUU, but it failed saying Recovery, and then it exited the process on computer. But my phone is still in the same silver htc logo, does it mean its installing or it failed to install? And BTW how do i install that firmware and also there a few versions if the same firmware!
If you can help me with sorting out this it would be of great help!! Thanks in advance for all the help till now...
Click to expand...
Click to collapse
here you go, easy way, download this: https://www.androidfilehost.com/?fid=95897840722641610 rename it to rom.zip for ease
place it in the same folder as adb and fastboot on your computer, then open a command window there. first you need to get out of RUU mode, so type fastboot reboot-bootloader, your phone should return to the bootloader screen, then enter recovery on your phone, hopefully twrp recovery still, then type adb push rom.zip /sdcard/, takes a while but it will let you know when its done, it will look like its doing nothing whilst its pushing.
unplug your phone and flash the rom, select stock radio and stock recovery when prompted, when the phone starts back up, check for updates, as you are s-on your bootloader will need to be relocked to update.

Thanks man for the help.
let me try and install that thing. Need to know why to relock the boot loader? and how can i relock it?

[email protected] said:
Thanks man for the help.
let me try and install that thing. Need to know why to relock the boot loader? and how can i relock it?
Click to expand...
Click to collapse
just type fastboot oem lock with your phone in fastboot mode, if you need to unlock in the future, just use the unlock token again or goto HTC Dev to get a new one.

Can i locck it belore running RUU or flashing rom?

[email protected] said:
Can i locck it belore running RUU or flashing rom?
Click to expand...
Click to collapse
no, it needs to be unlocked for flashing the reset rom in order to use the custom recovery.
locked / re-locked for running RUU

C:\Users\USER\Desktop\OneDrivers_Fastboot\Fastboot>adb push rom.zip /sdcard/
error: device not found
Im getting this on pushing from recovery mode. How can i resolve this?

[email protected] said:
C:\Users\USER\Desktop\OneDrivers_Fastboot\Fastboot>adb push rom.zip /sdcard/
error: device not found
Im getting this on pushing from recovery mode. How can i resolve this?
Click to expand...
Click to collapse
when your phone is in recovery, have a look in device manager, see what it says for your phone ?

Its not able to find my device properly. Attaching it

[email protected] said:
Its not able to find my device properly. Attaching it
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=52135024
See Question (2 in this faq post to fix your drivers

That worked great man!! I have pushed it to device and now installing.
Its been 10 mins and i can still see the Installing bar running with 0.00%.. Is it correct or abnormal?

[email protected] said:
That worked great man!! I have pushed it to device and now installing.
Its been 10 mins and i can still see the Installing bar running with 0.00%.. Is it correct or abnormal?
Click to expand...
Click to collapse
no that doesnt sound right, has it done anything in aroma, like wipe partitions etc ?

Seanie280672 said:
your computer needs to see the phone whilst the phone is in fastboot mode in the bootloader for anything to work, but the the updated lollipop RUU is here: http://forum.xda-developers.com/htc-one/general/guide-convert-m7-developer-edition-t2840311
Click to expand...
Click to collapse
Seanie280672 said:
no that doesnt sound right, has it done anything in aroma, like wipe partitions etc ?
Click to expand...
Click to collapse
I have choose to wipe partition. Shall i not?

[email protected] said:
I have choose to wipe partition. Shall i not?
Click to expand...
Click to collapse
yes you should, but has the aroma installer done that part yet is what im asking ?

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.