Database Develop

[Q] [Help] Brick help needed [Solved!]

I was trying to flash a ROM earlier today and didn't realize that I was S-on... This threw me into a Boot loop, I thought no problem i'll just wipe and flash a rom that doesn't need s-off. found one and it booted but I got force close errors all over the place. Then I decided I should just bring it back to stock.. which I was somewhat able to using GURU RUU. I have the phone able to boot 100% into the OS but due to a Firmware difference (that he mentions in his video...) My touch screen isn't functioning. My current state is able to boot into stock rom with no error but no touch screen, I can Load bootloader, fastboot, and recover (I have TWRP but CWM works as well). I have fastboot operations but no adb functionality with the one exception that I can run sideload in twrp and cwm. Not sure if it is a pc issue or a phone issue, although I have tried reinstalling drivers both with and with out sync installed. What is my next move? Do i get a OTG USB cable and do an OTA using a mouse? Or do I do something else? wanted to check with you guys before I jump out of the frying pan and into the fire... seems like i have been making one mistake after another on my own accord. thanks for you time and help. Here is a copy of my fastboot getvar all (with my imei censored of course)
Code:
getvar all
(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: HT3C5W902089
(bootloader) imei: XXXXXXXXXXXXXXXX
(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: 4297mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-a85199f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.109s

Use otg cable +USB mouse to control the phone
sent from my mobile device

update
I have my otg cable and im able to use the usb mouse with it but I am unable to check for the at&t software update... i click on it and it puls up for a second and then goes away... any ideas?

Idea
I read somewhere that I can flash firmware with s-on as long as i re-lock the bootloader and the mid and cid match on the firmware that i flash to it... this would be done in the ruu flash boot? does that sound right and would this allow me to either get the ota update or flash the correct ruu OR would it possible get my adb functionality back to my bootloader so i can s-off and flash a stock ruu?

medicsizzle said:
I was trying to flash a ROM earlier today and didn't realize that I was S-on... This threw me into a Boot loop, I thought no problem i'll just wipe and flash a rom that doesn't need s-off. found one and it booted but I got force close errors all over the place. Then I decided I should just bring it back to stock.. which I was somewhat able to using GURU RUU. I have the phone able to boot 100% into the OS but due to a Firmware difference (that he mentions in his video...) My touch screen isn't functioning. My current state is able to boot into stock rom with no error but no touch screen, I can Load bootloader, fastboot, and recover (I have TWRP but CWM works as well). I have fastboot operations but no adb functionality with the one exception that I can run sideload in twrp and cwm. Not sure if it is a pc issue or a phone issue, although I have tried reinstalling drivers both with and with out sync installed. What is my next move? Do i get a OTG USB cable and do an OTA using a mouse? Or do I do something else? wanted to check with you guys before I jump out of the frying pan and into the fire... seems like i have been making one mistake after another on my own accord. thanks for you time and help. Here is a copy of my fastboot getvar all (with my imei censored of course)
Code:
getvar all
(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: HT3C5W902089
(bootloader) imei: XXXXXXXXXXXXXXXX
(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: 4297mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-a85199f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.109s
Click to expand...
Click to collapse
You need to flash your touch drivers.

You are in a bit of pickle, as you can't flash anything. Can you run this RUU? http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/

SaHiLzZ said:
You are in a bit of pickle, as you can't flash anything. Can you run this RUU? http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
Click to expand...
Click to collapse
I can try but I am stuck in S-on would this be an issue? and I can flash from cwm and twrp would a stock nandroid help?

What GURU Reset file did you use? If it is same as nandroid for ATT, then it wont help.
You will need to lock the bootloader and run the RUU file I linked. If RUU doesn't like something on your phone (CID/MID/MAIN-ver mismatch) it will fail before flashing. If it starts flashing you should have a working device at the end.

SaHiLzZ said:
What GURU Reset file did you use? If it is same as nandroid for ATT, then it wont help.
You will need to lock the bootloader and run the RUU file I linked. If RUU doesn't like something on your phone (CID/MID/MAIN-ver mismatch) it will fail before flashing. If it starts flashing you should have a working device at the end.
Click to expand...
Click to collapse
You are the BEST! Thank you so much.. I have been racking my head trying to get this fixed... I am up and running again! My process
1. I had my phone unlocked bootloader, s-on, and twrp recovery
2. booted into trwp, and adb pushed the Guru stock installer
3. installed the zip, selecting to wipe data, no super user, and then I put the stock recovery and radios on
4. rebooted into bootloader and locked my bootloader
5. rebooted phone
6. ran the RUU that you provided me. (Thanks again)
7. phone booted up 100% working!!!!
8. Gave credit where credit was due!

[Q] HTC One From Amazon Warehouse - Received unlocked and a bit messed up - Pls help

Hello everyone,
Firstly, I’d just like to say that I’m a bit of a noob. However, I’ve spent hours and hours reading through the forum, googling, reading guides, and generally trying to inform myself before writing this. So hopefully I won’t annoy people with my questions
My phone is a factory unlocked HTC One from Amazon Warehouse Germany (ie. second hand, but direct from Amazon themselves). The phone looks great and seemed to work fine, but after deciding that I’d like to go rooted, I had my first encounter with the bootloader. This is where I realised that something wasn’t right….
If I access the bootloader (Power+Vol-), it will always perform a factory reset when I exit. It doesn’t matter whether I try to exit using the Reboot or the Power Down options from the fastboot menu. As soon as I power the phone back on, it will always boot up like it’s a brand new phone that needs setting up from scratch. This is a real pain, because I have to complete that basic phone setup every time - just to know whether or not it happens next time.
At one point I noticed that the botloader already has the **Unlocked** message in the top left corner, so I then followed the relevant guides to clear the cache and flash a custom recovery… When I do this (using fastboot flash recovery command) I always get the message that the recovery was sent and flashed OK. But if I try to access the custom recovery, I just come to a screen with a red exclamation mark inside a triangle. The phone will then eventually reboot its self (in a factory reset state again). From what info I can find, the triangle with the red exclamation mark means that the recovery isn’t actually there.
As a last resort I thought I’d try to fix the phone with an RUU, but for that I need a relocked bootloader. So I tried to do this with the “fastboot oem lock” command and got the following message:
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.165s
Afted the above message shows, the phone restarts its self automatically and boots up in a factory reset state again. The bootloader also remains unlocked.
I’ve attached a screenshot of my bootloader and here are some details of the phone that I got by using “fastboot getvar all” (I removed the IMEI):
(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: **************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4295mV
(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.047s
After Googling some of the info from the bootloader screen, I noticed that one of the top results is a htc1guru.com guide to resetting your phone back to stock. For that reason I’m thinking that the previous owner might have messed around with the phone, flashed a few custom roms, and then tried to restore the device back to stock before sending it to Amazon for a refund.
I know that I could complain and send the phone back to amazon myself, but the phone is in such immaculate condition (for a used device) that I’d really like to keep it if possible.
Can anyone help me? please?
Thank you,
Craig.

craighumphries said:
Hello everyone,
Firstly, I’d just like to say that I’m a bit of a noob. However, I’ve spent hours and hours reading through the forum, googling, reading guides, and generally trying to inform myself before writing this. So hopefully I won’t annoy people with my questions
My phone is a factory unlocked HTC One from Amazon Warehouse Germany (ie. second hand, but direct from Amazon themselves). The phone looks great and seemed to work fine, but after deciding that I’d like to go rooted, I had my first encounter with the bootloader. This is where I realised that something wasn’t right….
If I access the bootloader (Power+Vol-), it will always perform a factory reset when I exit. It doesn’t matter whether I try to exit using the Reboot or the Power Down options from the fastboot menu. As soon as I power the phone back on, it will always boot up like it’s a brand new phone that needs setting up from scratch. This is a real pain, because I have to complete that basic phone setup every time - just to know whether or not it happens next time.
At one point I noticed that the botloader already has the **Unlocked** message in the top left corner, so I then followed the relevant guides to clear the cache and flash a custom recovery… When I do this (using fastboot flash recovery command) I always get the message that the recovery was sent and flashed OK. But if I try to access the custom recovery, I just come to a screen with a red exclamation mark inside a triangle. The phone will then eventually reboot its self (in a factory reset state again). From what info I can find, the triangle with the red exclamation mark means that the recovery isn’t actually there.
As a last resort I thought I’d try to fix the phone with an RUU, but for that I need a relocked bootloader. So I tried to do this with the “fastboot oem lock” command and got the following message:
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.165s
Afted the above message shows, the phone restarts its self automatically and boots up in a factory reset state again. The bootloader also remains unlocked.
I’ve attached a screenshot of my bootloader and here are some details of the phone that I got by using “fastboot getvar all” (I removed the IMEI):
(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: FA399W906494
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4295mV
(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.047s
After Googling some of the info from the bootloader screen, I noticed that one of the top results is a htc1guru.com guide to resetting your phone back to stock. For that reason I’m thinking that the previous owner might have messed around with the phone, flashed a few custom roms, and then tried to restore the device back to stock before sending it to Amazon for a refund.
I know that I could complain and send the phone back to amazon myself, but the phone is in such immaculate condition (for a used device) that I’d really like to keep it if possible.
Can anyone help me? please?
Thank you,
Craig.
Click to expand...
Click to collapse
The red triangle is stock recovery. Can you post a fastboot getvar all output, What custom recovery are you trying to flash. Do not relock the boot loader with a custom recovery.

mb_guy said:
The red triangle is stock recovery. Can you post a fastboot getvar all output, What custom recovery are you trying to flash. Do not relock the boot loader with a custom recovery.
Click to expand...
Click to collapse
Thanks. I've tried flashing CWM Touch and TWRP during my various attempts.
I always get the message that the file was sent to the phone and flashed ok,
but when I try to access recovery it still goes to the triangle (stock recovery).
The Getvar all readout is in my first post, but I ran it again just in case:
(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: *************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4329mV
(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.047s

craighumphries said:
Thanks. I've tried flashing CWM Touch and TWRP during my various attempts.
I always get the message that the file was sent to the phone and flashed ok,
but when I try to access recovery it still goes to the triangle (stock recovery).
The Getvar all readout is in my first post, but I ran it again just in case:
(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: *************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4329mV
(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.047s
Click to expand...
Click to collapse
Did you try fastboot clear cache, after flashing twrp

mb_guy said:
Did you try fastboot clear cache, after flashing twrp
Click to expand...
Click to collapse
Yes, I flashed the recovery and then used the command "fastboot erase cache" (fastboot clear cache doesn't seem to do anything) . It does not report any problems at all, but it still goes to the same red triangle when i try to enter recovery. And as usual, the phone will then boot up and is completely factory reset again. I'm so confused :crying:

craighumphries said:
Yes, I flashed the recovery and then used the command "fastboot erase cache" (fastboot clear cache doesn't seem to do anything) . It does not report any problems at all, but it still goes to the same red triangle when i try to enter recovery. And as usual, the phone will then boot up and is completely factory reset again. I'm so confused :crying:
Click to expand...
Click to collapse
I may have missed this, but what does it say in the system settings about the rom

mb_guy said:
I may have missed this, but what does it say in the system settings about the rom
Click to expand...
Click to collapse
I've attached a couple of pics. Is this what you mean?

The thing that I find so odd with this phone, is that I can't go into the bootloader without it deleting everything and effectively performing a factory reset of the phone. I don't have to do anything in there at all. Just going into the bootloader screen and rebooting is enough to cause it to do this.

craighumphries said:
The thing that I find so odd with this phone, is that I can't go into the bootloader without it deleting everything and effectively performing a factory reset of the phone. I don't have to do anything in there at all. Just going into the bootloader screen and rebooting is enough to cause it to do this.
Click to expand...
Click to collapse
You might try fix permissions from TWRP

I would suggest attempting to get s-off via firewater using the temp root method. This should allow you to flash an RUU that has a downgraded hboot, which might fix your problems. Alternatively, if you don't want to get s-off, flash an RUU that has an updated hboot, which should do the same thing.

mb_guy said:
You might try fix permissions from TWRP
Click to expand...
Click to collapse
I'm not sure how I can do that, because as I was mentioning before - I can flash a recovery, but when I try to access it the phone still goes to the red triangle. It's as if the custom recovery didn't flash, even though it says that it was flashed successfully.

LightSpeedIII said:
I would suggest attempting to get s-off via firewater using the temp root method. This should allow you to flash an RUU that has a downgraded hboot, which might fix your problems. Alternatively, if you don't want to get s-off, flash an RUU that has an updated hboot, which should do the same thing.
Click to expand...
Click to collapse
Thanks. I haven't tried firewater before, so I will have a read up on how to do that. Unfortunately I can't flash any ruu as things are at the moment, because fastboot oem lock command won't work for some reason. I do ultimately want to be s-off though, so I guess I will have to be careful with newer RUU's.
I will post back my results.

Send it back. Your phone is dead.

craighumphries said:
Thanks. I haven't tried firewater before, so I will have a read up on how to do that. Unfortunately I can't flash any ruu as things are at the moment, because fastboot oem lock command won't work for some reason. I do ultimately want to be s-off though, so I guess I will have to be careful with newer RUU's.
I will post back my results.
Click to expand...
Click to collapse
OK, well I knew that it wasn't going to work as soon as I executed the first "adb reboot" command. The phone rebooted as expected, but it had also performed a factory reset in the process. Despite this I continued with the instructions, managed to copy the files and obtain temp root, but then the firewater process just terminated at bottle 6. Oh well...

SaHiLzZ said:
Send it back. Your phone is dead.
Click to expand...
Click to collapse
I guess that must be true, so I will create a return tomorrow.
It just seems so strange that I can boot the device, install apps and otherwise use the device completely normally. I guess it's time to admit defeat and send it back though.

(SOLVED) M7 UL won't root, Unable to mount /Data /Cache

Hey guys,
My HTC One M7 UL (PN07120) is driving me nuts. I was trying to obtain root so I proceeded to unlock it through htcdev and did it sucessfully. My phone can boot normally. However I cannot root it. I checked to see whether it had damaged partition tables and got no errors after using the mkfs.ext4 solution. I tried installing several RUUs but when they don't failed with the "incorrect RUU" error, they just don't go past the "getting header 1/5)" step of the process.
I have explored several threads with issues that might look like mine, but they end up not being. I will post my getvar info and the names of the RUUs I've been using hoping to find someone kind enough to give me a hand.
Code:
fastboot getvar all
(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: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36M********(ERASED BY ME)
(bootloader) imei: ERASED BY ME
(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: 4302mV
(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
Files names used:
1)RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2
2)RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2
3)RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2
4)ATT_442.OTAPkg
Thanks in advance.

shadowhacker27 said:
Hey guys,
My HTC One M7 UL (PN07120) is driving me nuts. I was trying to obtain root so I proceeded to unlock it through htcdev and did it sucessfully. My phone can boot normally. However I cannot root it. I checked to see whether it had damaged partition tables and got no errors after using the mkfs.ext4 solution. I tried installing several RUUs but when they don't failed with the "incorrect RUU" error, they just don't go past the "getting header 1/5)" step of the process.
I have explored several threads with issues that might look like mine, but they end up not being. I will post my getvar info and the names of the RUUs I've been using hoping to find someone kind enough to give me a hand.
Code:
fastboot getvar all
(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: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36M********(ERASED BY ME)
(bootloader) imei: ERASED BY ME
(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: 4302mV
(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
Files names used:
1)RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2
2)RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2
3)RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2
4)ATT_442.OTAPkg
Thanks in advance.
Click to expand...
Click to collapse
Post a screenshot of your bootloader
The RUU's wont install because your S-On and it will only allow same version or higher
the RUU you require is this one...
http://dl3.htc.com/application/RUU_M...5_signed_2.exe
However since your bootloader is unlocked, you could flash a recovery and root from there..
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
Put the recovery in your adb folder and from there
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then enter recovery and make a backup of your rom.
when you exit TWRP, you will be prompted to root your device

How are you trying to root, and how does it fail? Please provide all the detail you can.

fenstre said:
How are you trying to root, and how does it fail? Please provide all the detail you can.
Click to expand...
Click to collapse
It just doesn't root because the files (su.zip or superuser.zip) are not to be found anywhere thanks to my inability to write /data. I am going to try @bored_stupid approach and see what it does.
EDIT:
I had flashed this recovery before with success. The problem is it says "Unable to mount /Cache" or "/data" whenever I try to either backup or install a rom respectively. It does offer to install Su.zip when exit, but it fails to do it because when I check it with root requiring apps, o root checkers, they all say the same: No Root.
EDIT #2:
I was able to install a custom rom!!!!!! All problems got fixed after @bored_stupid approach. Thank you very very much. However, before trying the custom rom I did try to install su.zip when exiting TWRP and, differently to the other tries, it did partially write (confirming that /data was finally writable.) I couldn't, thou, install the Binary when phone booted. I will be trying some other roms and have some fun with the device.
One again. Thanks a lot!!!

shadowhacker27 said:
It just doesn't root because the files (su.zip or superuser.zip) are not to be found anywhere thanks to my inability to write /data. I am going to try @bored_stupid approach and see what it does.
EDIT:
I had flashed this recovery before with success. The problem is it says "Unable to mount /Cache" or "/data" whenever I try to either backup or install a rom respectively. It does offer to install Su.zip when exit, but it fails to do it because when I check it with root requiring apps, o root checkers, they all say the same: No Root.
EDIT #2:
I was able to install a custom rom!!!!!! All problems got fixed after @bored_stupid approach. Thank you very very much. However, before trying the custom rom I did try to install su.zip when exiting TWRP and, differently to the other tries, it did partially write (confirming that /data was finally writable.) I couldn't, thou, install the Binary when phone booted. I will be trying some other roms and have some fun with the device.
One again. Thanks a lot!!!
Click to expand...
Click to collapse
Glad i could help
It might be worth downloading the RUU too, Just in case you ever need to go back to stock.
Enjoy the new freedom rooting brings

bored_stupid said:
Glad i could help
It might be worth downloading the RUU too, Just in case you ever need to go back to stock.
Enjoy the new freedom rooting brings
Click to expand...
Click to collapse
Yes. Thank you very much, my friend. I was about to toss this phone and buy a Motorola V9. hehehehe! Thanks.
By the way, How can I change the title so that I can type (SOLVE) and help others find this?

shadowhacker27 said:
Yes. Thank you very much, my friend. I was about to toss this phone and buy a Motorola V9. hehehehe! Thanks.
By the way, How can I change the title so that I can type (SOLVE) and help others find this?
Click to expand...
Click to collapse
When you press edit, press on "go advanced.
Sent from my Nexus 7 using XDA Premium 4 mobile app

My HTC one is also driving me mad as I can't install any roms even the original or customs , get always a fault at the end , just boots and is stuck on the boot logo
Sent from my Lumia 1320 using Tapatalk

[Q] Need help returning to stock to receive updates again

I'm trying to setback to factory settings. I'd like tampered/unlocked are gone again but I don't really need it. I just want to be able to receive normal updates again. I tried to follow a guide but it just told me my image could not be updated. I've spent a long time now trying to figure this out reading different guides and questions but haven't found anything that helps me. Something I'm confused about is my Version-Main is blank. Someone told me to try a method which required me to go s-off. In that attempt I tried 2 different methods. Rumrunner didn't work so I tried revone. But that gave me error = 1 so in my attempt to follow directions to fix that, I installed a rom that doesn't work. Now I can't boot up! My phone will just show the HTC logo then restart. I tried to go to recovery but it just loads me into fastboot in the bootloader and won't go anywhere else. So I can't even get to my recovery now. I don't know what I need to do, what recovery file I need. If anyone could Help i would really appreciate it. And please be noob friendly! I'm very new to this. I have viewed all the tutorials, all varietys of them, and to no avail. I'm extremely desperate as I need my phone for work and I'm suppose to get a call for a new job tomorrow
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 1.00.20.1108
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3873mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
G:\Backup\OneDrivers_Fastboot\OneDrivers_Fastboot\ Fastboot>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.206s

You have the HTC One Sprint version, post here instead, they will be able to help you better, this is the GSM forum, your partition layout and rom's etc are different.
http://forum.xda-developers.com/sprint-htc-one

RRaczak said:
I'm trying to setback to factory settings. I'd like tampered/unlocked are gone again but I don't really need it. I just want to be able to receive normal updates again. I tried to follow a guide but it just told me my image could not be updated. I've spent a long time now trying to figure this out reading different guides and questions but haven't found anything that helps me. Something I'm confused about is my Version-Main is blank. Someone told me to try a method which required me to go s-off. In that attempt I tried 2 different methods. Rumrunner didn't work so I tried revone. But that gave me error = 1 so in my attempt to follow directions to fix that, I installed a rom that doesn't work. Now I can't boot up! My phone will just show the HTC logo then restart. I tried to go to recovery but it just loads me into fastboot in the bootloader and won't go anywhere else. So I can't even get to my recovery now. I don't know what I need to do, what recovery file I need. If anyone could Help i would really appreciate it. And please be noob friendly! I'm very new to this. I have viewed all the tutorials, all varietys of them, and to no avail. I'm extremely desperate as I need my phone for work and I'm suppose to get a call for a new job tomorrow
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 1.00.20.1108
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3873mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
G:\Backup\OneDrivers_Fastboot\OneDrivers_Fastboot\ Fastboot>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.206s
Click to expand...
Click to collapse
1. Download TWRP 2.6.3.0 here: http://techerrata.com/browse/twrp2/m7wls and flash it
2. Download the guru reset for your device here: http://www.htc1guru.com/dld/guru_reset_m7_sprint_3-04-651-2-zip/ and install it
3. Try using firewater to acquire S-Off
4. Download the RUU for your device here for .exe: http://www.htc1guru.com/downloads/ruu-file-downloads/
And here for .zip: http://www.htc1guru.com/downloads/ruu-zip-downloads/
Just follow the instructions below the page you chose
Hope this helps
Sent from my HTC One using XDA Premium 4 mobile app

SBColasito said:
1. Download TWRP 2.6.3.0 here: http://techerrata.com/browse/twrp2/m7wls and flash it
2. Download the guru reset for your device here: http://www.htc1guru.com/dld/guru_reset_m7_sprint_3-04-651-2-zip/ and install it
3. Try using firewater to acquire S-Off
4. Download the RUU for your device here for .exe: http://www.htc1guru.com/downloads/ruu-file-downloads/
And here for .zip: http://www.htc1guru.com/downloads/ruu-zip-downloads/
Just follow the instructions below the page you chose
Hope this helps
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sadly I can't get ADB to recognize my device. The fixes for that I've read haven't seemed to work but I don't know whats causing this. I know it used to recognize my device when I first rooted my phone...That was only a couple of months ago.

RRaczak said:
Sadly I can't get ADB to recognize my device. The fixes for that I've read haven't seemed to work but I don't know whats causing this. I know it used to recognize my device when I first rooted my phone...That was only a couple of months ago.
Click to expand...
Click to collapse
check FAQ #2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
if that's the problem

Yes! that worked! I didn't notice it because if I'm in fastboot its recognized as My HTC, but in recovery it did change it to other device. So now I can try these methods! thanks a bunch!

So I was able to push guru to my phone now. But it fails to instal via twrp. It just spams
updating partition details
unable to mount /data
unable to mount internal storage
unable to mount /data
Error flashing zip /sdcard/guru.zip

RRaczak said:
So I was able to push guru to my phone now. But it fails to instal via twrp. It just spams
updating partition details
unable to mount /data
unable to mount internal storage
unable to mount /data
Error flashing zip /sdcard/guru.zip
Click to expand...
Click to collapse
corrupted partitions, you will need to format data partition
boot in twrp recovery, select "wipe" then "format data". When format data is completed you'll need to push the reset rom again (get wiped during the data partition format) and then try to install it again.

alray said:
corrupted partitions, you will need to format data partition
boot in twrp recovery, select "wipe" then "format data". When format data is completed you'll need to push the reset rom again (get wiped during the data partition format) and then try to install it again.
Click to expand...
Click to collapse
worked perfectly! I got Guru installed but now after a few second of booting up it goes to the white HTC logo screen and after 2-3mins restarts or if I try to unlock the screen. But If I don't care about getting the Tampered/Relocked flags to go away can I just install the RUU and start receiving the official updates again?

RRaczak said:
worked perfectly! I got Guru installed but now after a few second of booting up it goes to the white HTC logo screen and after 2-3mins restarts or if I try to unlock the screen. But If I don't care about getting the Tampered/Relocked flags to go away can I just install the RUU and start receiving the official updates again?
Click to expand...
Click to collapse
Afaik, the only ruus available for sprint are 1.29.651.X and will require S-OFF to flash because it a downgrade in version.
What recovery and version # is on your phone and what guru reset version have you installed?

alray said:
Afaik, the only ruus available for sprint are 1.29.651.X and will require S-OFF to flash because it a downgrade in version.
What recovery and version # is on your phone and what guru reset version have you installed?
Click to expand...
Click to collapse
The recovery I 'was' using was TWRP v2.6.3.0 but ever since Guru installed(Guru_Reset_M7_Sprint_3.04.651.2) I haven't been able to get back into recovery. I imagine I would just need to flash recovery again to fix it but not sure.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4301mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s

RRaczak said:
The recovery I 'was' using was TWRP v2.6.3.0 but ever since Guru installed(Guru_Reset_M7_Sprint_3.04.651.2) I haven't been able to get back into recovery. I imagine I would just need to flash recovery again to fix it but not sure.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4301mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
Click to expand...
Click to collapse
well twrp recovery is replaced by the stock recovery if you have selected the option when installing the guru reset rom. Maybe you could try to restore from a nandroid backup or flash a sprint rom. Better to ask in the sprint forum for that

alray said:
well twrp recovery is replaced by the stock recovery if you have selected the option when installing the guru reset rom. Maybe you could try to restore from a nandroid backup or flash a sprint rom. Better to ask in the sprint forum for that
Click to expand...
Click to collapse
Will any of these work? I don't know what a nandroid backup is :L http://www.htc1guru.com/downloads/stock-nandroid-downloads/ and is a RUU a rom? I was never clear on that

RRaczak said:
Will any of these work? I don't know what a nandroid backup is :L http://www.htc1guru.com/downloads/stock-nandroid-downloads/
Click to expand...
Click to collapse
There is no backup for you phone there (.651) and .651 RUU are older version and require s-off.
and is a RUU a rom? I was never clear on that
Click to expand...
Click to collapse
RUU are used to flash the whole phone, Software (rom) + firmware(bootloader, recovery, radio, etc etc).
maybe there are some backup posted in the sprint htc one forum. you can also ask someone to upload their backup for you
not that I don't want to help you, but from there I highly suggest you to ask in the sprint htc one forum.

alray said:
There is no backup for you phone there (.651) and .651 RUU are older version and require s-off.
RUU are used to flash the whole phone, Software (rom) + firmware(bootloader, recovery, radio, etc etc).
maybe there are some backup posted in the sprint htc one forum. you can also ask someone to upload their backup for you
not that I don't want to help you, but from there I highly suggest you to ask in the sprint htc one forum.
Click to expand...
Click to collapse
Thanks for clearing that up for me! I'll try to hunt down one of these nandroid backups. Getting close to a week trying to fix this now and i'm losing hair! lol thanks again for the info

I got a ROM to work, it constantly restarts but i think it will stay on long enough to get an S-Off program to run. I tried doing it a few times but it kept trying to instal HTC MTP Drivers and failing causing the connection to cease of course. I've tried installing HTC Sync to get the drivers and uninstal it but it didn't work. Still kept trying to install the driver. I downloaded the drivers just themselves but the only ones I found came as a .cab and I don't know what to do with that or where to put it. Any ideas?
***I seemed to fix the constant driver problem. Rumrunner pours 8 times and tells me to pray and try again. I tried to do firwater but as soon as it says 'Chugging' It boots me out back to fastboot and stops. I tried Revone and I get Error Code 1 still and trying to fix that error is what caused me all this trouble in the first place so I aint messing with that. I'm using the Viper ROM does that cause an issue?

M7 - boots to fastboot and recovery, can't boot custom ROMs, errors in RUUs

Hello everybody!
I am loosing my mind with this, would be grateful if someone could help me!
Received an HTC One M7 Nordic (HTC__Y13) version, HBOOT 1.61.0000, radio 4T.35.3218.16, ODSP 35.120.274.0718 OS.
Firstly, I unlocked the bootloader via HTCdev, then, as I did with other devices, installed CWM which I used to wipe just about everything and I installed LineageOS. (S-ON, Tampered, Unlocked bootloader). To my surprise, LOS didn't boot, booting back to fastboot. I gave it another try, reinstalling it, failed to boot again. Then I started trying the RUUs, and the farthest I could reach was the signature rejection at 4%. I am using a Mac with both Sierra and a windows XP SP3 VM in Parallels, which I also used to try with a myriad of toolkits made for this phone. In HTC Sync, although the phone is recognised, all info, like OS version, are blank.
Well, here I am with a device without OS which boots to fastboot and TWRP/CWM. Since the beginning of this adventure, I couldn't boot once to a ROM, and I lost 3 long nights on this already. I believe the only things I could have missed are: using the right RUU.exe or zip, or someway getting the phone S-OFF without using an OS, since I don't have one.
When trying to "fastboot flash -zip ruu.zip", I always have some kind of error like "remote 02 data length is too large" or a variant of this.
I am getting kinda afraid I may have bricked the phone. Could someone help me?
Thanks!
here is the "getvar" dump
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3BRWxxxxxx
(bootloader) imei: XXXXXXXXXXXXXX
(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: 4278mV
(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
all: Done!

wasserprojekt said:
When trying to "fastboot flash -zip ruu.zip", I always have some kind of error like "remote 02 data length is too large" or a variant of this.
Click to expand...
Click to collapse
You must use htc_fastboot.exe from a Windows pc, not the regular fastboot. Make sure you have the latest RUU for your cid/mid

Thanks for your answer. I was about to give up on this, but then I finally found the right RUU. There are so many variants it becomes a nightmare finding the adequate one, eve worse if version is not one of the best selling.
But, as someone may need this advice in the future, I'll leave a summary of the important steps in here:
Return to stock ROM (for S-ON & unlocked bootloader & tampered):
- relock your device;
fastboot oem lock
Click to expand...
Click to collapse
-find the adequate RUU;
(for HTC__Y13, it's the RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.exe)
-close all programs which may connect to phone (includes HTC sync, any fastboot or adb command window...), otherwise there will be no progress in the RUU;
-start the RUU with phone connected (VMs work - at leaset in Parallels with XP SP3).
Thanks to everyone.