Database Develop

[Q] Bricked my HTC ONE AT&T

I have a US AT&T HTC ONE M7 that shipped to me.
I unrooted it fine using htcdev and getting the unlock_code.bin. Then I uploaded a recovery TWRP just fine and got in there and saw that it worked fine. Rebooted into normal and copyed the Revolution HD zip to my phone, but reading the thread it said that i needed to update my firmware.
I followed the guide it refferenced http://forum.xda-developers.com/showthread.php?t=2183023
To here http://forum.xda-developers.com/showthread.php?t=2182823
And it said to do the command to get your cid, which I did and got idnum: CWS__001
So I looked and found that I needed to get firmware.zip from 1.29.206.11
But the link on that page takes you to a firmware of 3.06.1700.01 or something close to that. I didn't notice the numbers were different so I did the flash with fimware 3.06.1700.01 instead of the 1.29.206. 11.
Booting the phone does nothing, it sits on the HTC one screen with Beats audio. Also the AT&T chimes no longer chime when on that page and then it just sits there. When booting with the down volume button I get a black screen instead of white screen. With a dead android on the bottom instead of the 3 little androids dancing (or whatever they are doing).
I was able to get recovery back and boot into recovery but I am not sure what to do.
WIth finding instructions I have tried to download a stock RUU which I found here.
http://forum.xda-developers.com/showthread.php?t=2428276
But without any instructions to use it. I assume you need to run it from TWRP recovery but I cannot get the computer to recognize the phone anymore as a drive in order to put the RUU on the phone
I just got this phone today and wanted to root it right away and I think I broke it already.
PLEASE HELP

Are you s-off?
Sent from my One using XDA Premium 4 mobile app
---------- Post added at 11:43 PM ---------- Previous post was at 11:41 PM ----------
When you flashed that firmware it also flashed a kernel so try to flash a working kernel
Sent from my One using XDA Premium 4 mobile app

dirtbikerr450 said:
Are you s-off?
Sent from my One using XDA Premium 4 mobile app
---------- Post added at 11:43 PM ---------- Previous post was at 11:41 PM ----------
When you flashed that firmware it also flashed a kernel so try to flash a working kernel
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Honestly I have no idea what that means. I have seen S-off and s-on but I am still a n00b. I have also edited my post above as I was able to get recovery installed again. It didn't before because I had relocked it and I unlocked it again
Now the issue is that I cannot get my computer to recognize the phone as a drive to put the RUU on it

Hold power and volume down and get to fastboot/bootloader
Sent from my One using XDA Premium 4 mobile app

dirtbikerr450 said:
Hold power and volume down and get to fastboot/bootloader
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I can get into that fastboot/bootloader but then what? I am here and again - it is a black screen with a dead android on the bottom which is not the same as the white screen I had before. Which clearly tells me something is wrong.
How do I load a stock kernel? Again, I have no access to the filesystem to put files onto the phone, only have access to using the commands like fastboot

I found a file on the internet
RUU_M7_UL_JB_50_Cingular.exe
Which i guess is for AT&T even thought it haven't been Cingular for years. And I go into this which says it is the HTC Android Phone ROM update utility 2.0.4.2013. Say yes to everything. It says it is going to go from 3.06.1700.10 to image version 1.26.502.12
Which is also an issue I think because the guide I found this on said that these numbers should be the same. This goes back to me flashing the 3.06.1700.10 instead of the correct firmware. I tell it to do it's thing but it errors out.
It says it will take about 10 minutes, so I wait - after about 5 minutes I get an error error [155] the ROM update utility cannot update your android phone. Please get the correct ROM update ulitity and try again.

Its an issue since 3.06 firmware is for Google play edition try to flash any other firmware to do the RUU
Sent from my One using XDA Premium 4 mobile app
---------- Post added at 12:15 AM ---------- Previous post was at 12:11 AM ----------
http://forum.xda-developers.com/showthread.php?t=2316726
Sent from my One using XDA Premium 4 mobile app

dirtbikerr450 said:
Its an issue since 3.06 firmware is for Google play edition try to flash any other firmware to do the RUU
Sent from my One using XDA Premium 4 mobile app
---------- Post added at 12:15 AM ---------- Previous post was at 12:11 AM ----------
http://forum.xda-developers.com/showthread.php?t=2316726
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just tried another firmware from that page I referenced in the OP for "x.xx.401.x - World Wide English (WWE)"
http://forum.xda-developers.com/showthread.php?t=2182823
Which came out as 2.24.401.1 and when flashing it gives me the error. failed (remote: 41 model id check fail)
I also tried to get kernels from htcdev.com/devcenter/downloads
Downloaded 1.26.502.12 and 1.26.502.10 from this page and neither worked. Giving me the error failed (remote: 12 signature verify fail)

Flash this one http://click.xda-developers.com/api...l unmodified&jsonp=vglnk_jsonp_13785283880456
Sent from my One using XDA Premium 4 mobile app

dirtbikerr450 said:
Its an issue since 3.06 firmware is for Google play edition try to flash any other firmware to do the RUU
Sent from my One using XDA Premium 4 mobile app
---------- Post added at 12:15 AM ---------- Previous post was at 12:11 AM ----------
http://forum.xda-developers.com/showthread.php?t=2316726
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
dirtbikerr450 said:
Flash this one http://click.xda-developers.com/api...l unmodified&jsonp=vglnk_jsonp_13785283880456
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK, this file I downloaded - 1.29.401.12.zip
And it gave me the error FAILED (remote: 41 model id check fail)

I googled S-OFF and I am not S-OFF, my top of my phone says S-ON. I followed a guide to root my phone which the last step was to install SuperSU and it worked fine. SuperSU worked fine as well so I thought I was rooted. I don't know if I was S-OFF before I flashed the firmware that caused this whole thing or not.

AMDZen said:
OK, this file I downloaded - 1.29.401.12.zip
And it gave me the error FAILED (remote: 41 model id check fail)
Click to expand...
Click to collapse
You are s-on. You should not be able to flash any firmware that's not for your phone, but because the Google edition has the same model ID as the AT&T it allowed it. I've seen a few people do this. You can not go back because on hboot 1.54 there is no s-off. The firmware you've flashed is newer than AT&T's, and you can't downgrade without s-off.
Use the custom recovery to flash a custom ROM. It will work and your phone will be fine.
You will be stuck on the Google edition firmware until AT&T releases newer firmware, or someone accomplishes s-off on 1.54 Hboot.
In the future don't flash anything that you don't fully understand.
Edit:
I should also add that I also have an AT&T One. I'm running the newest InsertCoin on the 4.3 leaked base, and my phone also has Google's firmware on it from when I did the full conversion a while back, I can testify that everything works perfectly with the firmware.
Sent from my HTC One using XDA Premium 4 mobile app

AMDZen said:
OK, this file I downloaded - 1.29.401.12.zip
And it gave me the error FAILED (remote: 41 model id check fail)
Click to expand...
Click to collapse
Ok, I followed your info and found that you just flashed the 3.06 firmware package that has the stock Google Play kernel in it.
Everything is fine with your device, but that kernel is why your system won't boot. Since you already have AHRD installed simply flashing the stock kernel from ARHD will get your phone back to booting.
Do this:
Open the AHRD.zip (the rom you installed)
Inside that zip you should see boot.img (if it is not at the root of the zip search for it, windows can search through a zip file)
Extract that file to your fastboot/adb folder.
Then flash that kernel by connecting the USB while the dark bootloader screen is up and it should say Fastboot USB on the phone.
Now issue this command:
Code:
fastboot flash boot boot.img
If you do not have ADB/fastboot setup then just install this toolkit:
http://forum.xda-developers.com/showthread.php?t=2183942
Then open the tool and choose Flash a kernel from the Extra's section. It will want to reboot the phone into fastboot, so just close that window since you are already there and then it should prompt you for the location of that boot.img file I referenced earlier. It will then issue the fastboot command to flash the kernel. After that I bet your phone will boot normally.
If you have issues or questions, just let me know. If needed I could teamviewer into your system and have you running in a few minutes.
Best of luck.
Crush

crushalot said:
Ok, I followed your info and found that you just flashed the 3.06 firmware package that has the stock Google Play kernel in it.
Everything is fine with your device, but that kernel is why your system won't boot. Since you already have AHRD installed simply flashing the stock kernel from ARHD will get your phone back to booting.
Do this:
Open the AHRD.zip (the rom you installed)
Inside that zip you should see boot.img (if it is not at the root of the zip search for it, windows can search through a zip file)
Extract that file to your fastboot/adb folder.
Then flash that kernel by connecting the USB while the dark bootloader screen is up and it should say Fastboot USB on the phone.
Now issue this command:
Code:
fastboot flash boot boot.img
If you do not have ADB/fastboot setup then just install this toolkit:
http://forum.xda-developers.com/showthread.php?t=2183942
Then open the tool and choose Flash a kernel from the Extra's section. It will want to reboot the phone into fastboot, so just close that window since you are already there and then it should prompt you for the location of that boot.img file I referenced earlier. It will then issue the fastboot command to flash the kernel. After that I bet your phone will boot normally.
If you have issues or questions, just let me know. If needed I could teamviewer into your system and have you running in a few minutes.
Best of luck.
Crush
Click to expand...
Click to collapse
Wow. This is confusing. OK the thing I flashed that messed this up was the zip file 3.06.1700.10.zip - so I am assuming that is what you mean by my AHRD. I took that, took the boot.img file out of it by itself and did as you said
fastboot flash boot boot.img
sending 'boot' (5794 KB)...
OKAY [ 0.919s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.416s
EDIT: I realized I didn't do the reboot so I did
fastboot oem rebootRUU
And then did it again, but I still got an error
fastboot flash boot boot.img
< waiting for device >
sending 'boot' (5794 KB)...
OKAY [ 0.916s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 1.412s
CoryTallman said:
You are s-on. You should not be able to flash any firmware that's not for your phone, but because the Google edition has the same model ID as the AT&T it allowed it. I've seen a few people do this. You can not go back because on hboot 1.54 there is no s-off. The firmware you've flashed is newer than AT&T's, and you can't downgrade without s-off.
Use the custom recovery to flash a custom ROM. It will work and your phone will be fine.
You will be stuck on the Google edition firmware until AT&T releases newer firmware, or someone accomplishes s-off on 1.54 Hboot.
In the future don't flash anything that you don't fully understand.
Edit:
I should also add that I also have an AT&T One. I'm running the newest InsertCoin on the 4.3 leaked base, and my phone also has Google's firmware on it from when I did the full conversion a while back, I can testify that everything works perfectly with the firmware.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I thought I did understand though. I didn't just dive into this, I researched everything all day and thought I had everything worked out. I first read teh instructions on Android Revolution HD which said that I needed to update the firmware, I followed those instructions as well and got:
fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.06.1700.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36KW901887
(bootloader) imei: 354439051471532
(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: 3890mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
The cidnum that the page clearly references as needing the firmware I downloaded. Everything checked out. And now I am stuck.
Any way - I have done as you say and tried to install a ROM using fastboot as well. Keep in mind that I cannot load a ROM onto the phone and load the ROM using TWRP like all the guides I've seen say to do. I did
fastboot flash zip ROM.zip - the ROM being TrickDroid_10.0.0 and it didn't work:
fastboot flash zip ROM.zip
sending 'zip' (1068303 KB)...
OKAY [ 38.982s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 52.508s

crushalot said:
Ok, I followed your info and found that you just flashed the 3.06 firmware package that has the stock Google Play kernel in it.
Everything is fine with your device, but that kernel is why your system won't boot. Since you already have AHRD installed simply flashing the stock kernel from ARHD will get your phone back to booting.
Do this:
Open the AHRD.zip (the rom you installed)
Inside that zip you should see boot.img (if it is not at the root of the zip search for it, windows can search through a zip file)
Extract that file to your fastboot/adb folder.
Then flash that kernel by connecting the USB while the dark bootloader screen is up and it should say Fastboot USB on the phone.
Now issue this command:
Code:
fastboot flash boot boot.img
If you do not have ADB/fastboot setup then just install this toolkit:
http://forum.xda-developers.com/showthread.php?t=2183942
Then open the tool and choose Flash a kernel from the Extra's section. It will want to reboot the phone into fastboot, so just close that window since you are already there and then it should prompt you for the location of that boot.img file I referenced earlier. It will then issue the fastboot command to flash the kernel. After that I bet your phone will boot normally.
If you have issues or questions, just let me know. If needed I could teamviewer into your system and have you running in a few minutes.
Best of luck.
Crush
Click to expand...
Click to collapse
OK Update. I was able to flash the boot after unlocking my phone again:
fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.047s]
finished. total time: 0.048s
fastboot flash boot boot.img
sending 'boot' (5794 KB)...
OKAY [ 0.912s]
writing 'boot'...
OKAY [ 0.612s]
finished. total time: 1.529s
So I got that part done. I downloaded the tool and couldn't get that portion of your instructions to work. If you have the time, I installed teamviewer and set it up in my firewall so I would like to give that a try. Never used it before but I am desperate.
EDIT AGAIN: OK I got the ALL IN ONE Tool working. Apparently that doesn't run correctly if its in a folder that has a space in it. I changed the folder name that all this stuff was in to just one word no space and got it working:
sending 'boot' (5794 KB)...
OKAY [ 0.914s]
writing 'boot'...
OKAY [ 0.614s]
finished. total time: 1.530s
However the phone still doesn't boot - it still has no sound on the AT&T part of booting and then the next screen just sits there and does nothing
EDIT 2: OHHHHHHHHHHHH Light bulb went off. By AHRD you meant ARHD - meaning the custom ROM. Sadly - I never got this custom ROM installed. I was following the instructions on that site on what I needed:
Code:
You need:
HTC One unlocked with htcdev.com (S-ON) or S-OFF
Custom recovery
[B]Firmware package from here (recommended but not needed for now)[/B]
Read this flashing guide - [GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock
It said recommended but not needed for now. I thought it was best to do it and that's what got me in the mess. The ROM on the phone is still whatever came from the factory.

AMDZen said:
Wow. This is confusing. OK the thing I flashed that messed this up was the zip file 3.06.1700.10.zip - so I am assuming that is what you mean by my AHRD. I took that, took the boot.img file out of it by itself and did as you said
fastboot flash boot boot.img
sending 'boot' (5794 KB)...
OKAY [ 0.919s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.416s
EDIT: I realized I didn't do the reboot so I did
fastboot oem rebootRUU
And then did it again, but I still got an error
fastboot flash boot boot.img
< waiting for device >
sending 'boot' (5794 KB)...
OKAY [ 0.916s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 1.412s
I thought I did understand though. I didn't just dive into this, I researched everything all day and thought I had everything worked out. I first read teh instructions on Android Revolution HD which said that I needed to update the firmware, I followed those instructions as well and got:
fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.06.1700.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36KW901887
(bootloader) imei: 354439051471532
(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: 3890mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
The cidnum that the page clearly references as needing the firmware I downloaded. Everything checked out. And now I am stuck.
Any way - I have done as you say and tried to install a ROM using fastboot as well. Keep in mind that I cannot load a ROM onto the phone and load the ROM using TWRP like all the guides I've seen say to do. I did
fastboot flash zip ROM.zip - the ROM being TrickDroid_10.0.0 and it didn't work:
fastboot flash zip ROM.zip
sending 'zip' (1068303 KB)...
OKAY [ 38.982s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 52.508s
Click to expand...
Click to collapse
Hold on now. You are doing a lot things wrong, but the good news is since you are s-on, you can't screw up bad. I was talking about the kernel from the rom (Android_Revolution_HD-One_20.1.zip) which I thought you had installed already.
So do I understand correctly that you did the firmware update first before flashing the Android Revolution rom, so you have the stock software (rom) installed?
However you don't have the rom file (Android_Revolution_HD-One_20.1.zip) or any others on your sdcard?
You can't flash a rom (TrickDroid) in fastboot mode.
Why exactly can't you sideload or push a rom to install from TWRP which it sounds like you have installed? Does your touch interface work in TWRP recovery?
If it doesn't then you just need to flash the latest version. Sideload is ok but you might have better luck by putting the rom file in your adb folder and issue this command while the system is booted into twrp recovery:
Code:
adb push TrickDroid.zip /data/media/0/
Then the rom will be on the root of your sdcard partition and you can install with TWRP.
---------- Post added at 03:02 AM ---------- Previous post was at 02:59 AM ----------
I saw your edit, but I didn't have mine posted in time to let you know about the kernel. Your best bet now is to install a custom rom. I didn't realize you had relocked.
Let me know where your recovery stands and if you have a rom file on the sdcard.

crushalot said:
Hold on now. You are doing a lot things wrong, but the good news is since you are s-on, you can't screw up bad. I was talking about the kernel from the rom (Android_Revolution_HD-One_20.1.zip) which I thought you had installed already.
So do I understand correctly that you did the firmware update first before flashing the Android Revolution rom, so you have the stock software (rom) installed?
However you don't have the rom file (Android_Revolution_HD-One_20.1.zip) or any others on your sdcard?
You can't flash a rom (TrickDroid) in fastboot mode.
Why exactly can't you sideload or push a rom to install from TWRP which it sounds like you have installed? Does your touch interface work in TWRP recovery?
If it doesn't then you just need to flash the latest version. Sideload is ok but you might have better luck by putting the rom file in your adb folder and issue this command while the system is booted into twrp recovery:
Code:
adb push TrickDroid.zip /data/media/0/
Then the rom will be on the root of your sdcard partition and you can install with TWRP.
---------- Post added at 03:02 AM ---------- Previous post was at 02:59 AM ----------
I saw your edit, but I didn't have mine posted in time to let you know about the kernel. Your best bet now is to install a custom rom. I didn't realize you had relocked.
Let me know where your recovery stands and if you have a rom file on the sdcard.
Click to expand...
Click to collapse
Yes on the highlighted in both cases. I'm in LUCK. Thanks so much for your help. I took the boot.img out of the stock RUU - RUU_M7_UL_JB_50_Cingular - 1.26.502.12 - Decrypted.img and ran fastboot to flash that and it booted up. I am now on a working HTC ONE
:victory::highfive:

AMDZen said:
Yes on the highlighted in both cases. I'm in LUCK. Thanks so much for your help. I took the boot.img out of the stock RUU - RUU_M7_UL_JB_50_Cingular - 1.26.502.12 - Decrypted.img and ran fastboot to flash that and it booted up. I am now on a working HTC ONE
:victory::highfive:
Click to expand...
Click to collapse
Glad your back up.

crushalot said:
Glad your back up.
Click to expand...
Click to collapse
So now I have installed ARHD custom ROM using TWRP as well.
Based on everything that has happened and the things the other person was saying about being on a newer firmware. Are there any issues I should be aware of for having this going forward?

AMDZen said:
So now I have installed ARHD custom ROM using TWRP as well.
Based on everything that has happened and the things the other person was saying about being on a newer firmware. Are there any issues I should be aware of for having this going forward?
Click to expand...
Click to collapse
Just that you can't gain s-off until a new hack is discovered for hboot 1.54. Also I am not sure if it will allow you switch back to the HTC firmware (as opposed to the Google Edition which is an unbranded bootloader) when a new base is release since you have s-on. Shouldn't be a big deal. You will probably be able to run most roms on that firmware for a long time.

[Q] No android, no recovery, only bootloader... :(

Dear XDA,
I wanted to update my HTC One to Revolution HD. But there where some requirements before i could install that. Like updating the firmware and installing TWRP recovery. I needed to RELOCK my phone in order to update my firmware. So i did that using a tutorial. After that i only had to push the RUU and i would be back @ stock. And then i could flash Revolution HD to get 4.4!
But!... it went horribly wrong. As of right now, i can only enter fastboot. I cannot enter recovery, and there is no Android installed, so basically i'm screwed.
I do have some flashing experience and I'm not a complete newb, but this is out of my league. Perhaps there are some nice persons here that could help me out. I will try to summarise my phone settings:
My current settings in Fastboot:
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
May 3 2013,17:22:59:-1
CID: HTC_E11
MID: PN0710000
I have a nandroidback, but i can't get into recovery. I tried using ADB but my device is not recognised.... I get the feeling that S-ON needs to change to S-OFF. But if i use a toolkit (from Squabbi) i can't get my device S-OFF (device not recognised..).
As of right now, I'm sitting with my hands in my hair thinking i bricked my phone.
If someone could help me, you would save my day.
Lennard Breevaart.
ps: I'm using windows xp

len.asdf said:
Dear XDA,
I wanted to update my HTC One to Revolution HD. But there where some requirements before i could install that. Like updating the firmware and installing TWRP recovery. I needed to RELOCK my phone in order to update my firmware. So i did that using a tutorial. After that i only had to push the RUU and i would be back @ stock. And then i could flash Revolution HD to get 4.4!
But!... it went horribly wrong. As of right now, i can only enter fastboot. I cannot enter recovery, and there is no Android installed, so basically i'm screwed.
I do have some flashing experience and I'm not a complete newb, but this is out of my league. Perhaps there are some nice persons here that could help me out. I will try to summarise my phone settings:
My current settings in Fastboot:
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
May 3 2013,17:22:59:-1
CID: HTC_E11
MID: PN0710000
I have a nandroidback, but i can't get into recovery. I tried using ADB but my device is not recognised.... I get the feeling that S-ON needs to change to S-OFF. But if i use a toolkit (from Squabbi) i can't get my device S-OFF (device not recognised..).
As of right now, I'm sitting with my hands in my hair thinking i bricked my phone.
If someone could help me, you would save my day.
Lennard Breevaart.
ps: I'm using windows xp
Click to expand...
Click to collapse
is your bootloader unlocked ? do that first
what version of TWRP do you have (exact name)
do you have fastboot/adb on your pc and do you know how to use them ?

is your bootloader unlocked ? do that first
==> I think so, how can i check?
what version of TWRP do you have (exact name)
==> I have no recovery installed on my phone. But i have TWRP version 2.6.3.3. img on my computer, ready to push it to my phone (but it gives the error: device not found)
do you have fastboot/adb on your pc and do you know how to use them ?
==> I think i do. When i try to do adb shell in command window it replies with either device not found, or adb server out of date. Killing...
Thanks for replying btw!

len.asdf said:
is your bootloader unlocked ? do that first
==> I think so, how can i check?
what version of TWRP do you have (exact name)
==> I have no recovery installed on my phone. But i have TWRP version 2.6.3.3. img on my computer, ready to push it to my phone (but it gives the error: device not found)
do you have fastboot/adb on your pc and do you know how to use them ?
==> I think i do. When i try to do adb shell in command window it replies with either device not found, or adb server out of date. Killing...
Thanks for replying btw!
Click to expand...
Click to collapse
take these files
extract fastboot.zip to c:\fastboot
and install these drivers
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
MD5: e2a21d71954d4164c1a116abb926a363
and see if you can get:
fastboot getvar all
and post the results minus you serial no and IEMI

clsA said:
take these files
extract fastboot.zip to c:\fastboot
and install these drivers
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
MD5: e2a21d71954d4164c1a116abb926a363
and see if you can get:
fastboot getvar all
and post the results minus you serial no and IEMI
Click to expand...
Click to collapse
Thanks! This is what i did to get my results:
1. Downloaded both the fastboot.zip and the drivers (and installed ofcourse).
2. Opened a command window on c:\fastboot
3. typed: fastboot getvar all
Results:
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.16
(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__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4222mV
(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: 0.047s
C:\fastboot>

len.asdf said:
Thanks! This is what i did to get my results:
1. Downloaded both the fastboot.zip and the drivers (and installed ofcourse).
2. Opened a command window on c:\fastboot
3. typed: fastboot getvar all
Results:
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.16
(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__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4222mV
(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: 0.047s
C:\fastboot>
Click to expand...
Click to collapse
Your phone is basically still stock andriod version 4.1.2
(this is good you can s-off pretty easy)
what RUU were you going to flash ?
this is the version of recovery you need
http://techerrata.com/browse/twrp2/m7ul
download it and put it in your fastboot folder
then to flash it:
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
now you can enter recovery correct ?

clsA said:
Your phone is basically still stock andriod version 4.1.2
(this is good you can s-off pretty easy)
what RUU were you going to flash ?
Click to expand...
Click to collapse
The RUU i tried was this one: RUU M7 U JB 50 HTC Europe 1.29.401.2 R Radio 4A.14.3250.13 10.33.1150.01 Release 311663 Signed 2 4
(from: http://forum.xda-developers.com/showthread.php?t=2428276)
While installing the RUU it gave me an an error that my CID and MID didn't match.

clsA said:
Your phone is basically still stock andriod version 4.1.2
(this is good you can s-off pretty easy)
what RUU were you going to flash ?
this is the version of recovery you need
http://techerrata.com/browse/twrp2/m7ul
download it and put it in your fastboot folder
Click to expand...
Click to collapse
Downloaded the recovery and put in the the fastboot folder

clsA said:
Your phone is basically still stock andriod version 4.1.2
(this is good you can s-off pretty easy)
what RUU were you going to flash ?
this is the version of recovery you need
http://techerrata.com/browse/twrp2/m7ul
download it and put it in your fastboot folder
then to flash it:
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
now you can enter recovery correct ?
Click to expand...
Click to collapse
While in ADB it gave this error:
C:\fastboot>fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
sending 'recovery' (9840 KB)...
OKAY [ 1.297s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.891s
C:\fastboot>
edit: I cannot enter recovery yet. Just tried it

len.asdf said:
While in ADB it gave this error:
C:\fastboot>fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
sending 'recovery' (9840 KB)...
OKAY [ 1.297s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.891s
C:\fastboot>
edit: I cannot enter recovery yet. Just tried it
Click to expand...
Click to collapse
your bootloader is still locked

clsA said:
your bootloader is still locked
Click to expand...
Click to collapse
I checked the md5 (f428caf36c9c337e2ae417fc10fbe165) with the file i downloaded. And it matches

len.asdf said:
I checked the md5 (f428caf36c9c337e2ae417fc10fbe165) with the file i downloaded. And it matches
Click to expand...
Click to collapse
yeah i realize that your bootloader is still locked
you need to go to htcdev and unlock again
then flash recovery

clsA said:
yeah i realize that your bootloader is still locked
you need to go to htcdev and unlock again
Click to expand...
Click to collapse
Ah ok, I will be doing that then . I will update this topic when i'm done.

len.asdf said:
Ah ok, I will be doing that then . I will update this topic when i'm done.
Click to expand...
Click to collapse
be warned unlocking will wipe the phone you'll be starting from nothing

clsA said:
be warned unlocking will wipe the phone you'll be starting from nothing
Click to expand...
Click to collapse
I know! But don't worry, it's the least of my problems now

Unlocked my phone, and gonna flash the recovery aswell!
But to not make the same mistake twice. What is the best way to update my phone to 4.4?
I wanted to install Revolution HD. But maybe you have a better alternative?

And how can i properly thank you? I mean, you just saved my ass!

len.asdf said:
And how can i properly thank you? I mean, you just saved my ass!
Click to expand...
Click to collapse
it's no problem
you should try and get s-off next
http://forum.xda-developers.com/showthread.php?t=2314582 - revone
ARHD is great .. I also use ViperOne
just use the sideload feature in twrp being your phone is wiped
Quote:
Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
From the command line, type adb sideload name_of_rom.zip
or
adb push Rom.zip /data/media/0/
Click to expand...
Click to collapse

clsA said:
it's no problem
you should try and get s-off next
http://forum.xda-developers.com/showthread.php?t=2314582 - revone
ARHD is great .. I also use ViperOne
just use the sideload feature in twrp being your phone is wiped
Click to expand...
Click to collapse
I will get s-off through the HTC One All in one toolkit. But on the ARHD topic, this was posted aswell:
You need:
HTC One unlocked with htcdev.com (S-ON) or S-OFF
Custom recovery
Firmware package from here (recommended but not needed for now)
Read this flashing guide - [GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock
So i tried to get the latest firmware, and that's where the problems started. But shouldn't it be better to have the latest firmware? I mean it stands there for a reason, right? Or am I wrong?
Anyway, i will try ARHD for now, it looks nice
Thanks again!

len.asdf said:
I will get s-off through the HTC One All in one toolkit. But on the ARHD topic, this was posted aswell:
You need:
HTC One unlocked with htcdev.com (S-ON) or S-OFF
Custom recovery
Firmware package from here (recommended but not needed for now)
Read this flashing guide - [GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock
So i tried to get the latest firmware, and that's where the problems started. But shouldn't it be better to have the latest firmware? I mean it stands there for a reason, right? Or am I wrong?
Anyway, i will try ARHD for now, it looks nice
Thanks again!
Click to expand...
Click to collapse
firmware comes after s-off
and ARHD 31.6 is your best bet for now till your s-off

[Q] possible to s-off or unlock bootloader with usb debug off???

Hello
I have HTC one m7_u cid 332 hboot 1.55
For my phone there is no stock RUU searched every where
Phone is hang on HTC logo
I can go to fast boot menu tryed to unlock bootloader with htcdev but not work
My question is there any way to s-off or unlock boot loader without USB debugging on ?????
Tanx

afghan-gsm-mastermind said:
Hello
I have HTC one m7_u cid 332 hboot 1.55
For my phone there is no stock RUU searched every where
Phone is hang on HTC logo
I can go to fast boot menu tryed to unlock bootloader with htcdev but not work
My question is there any way to s-off or unlock boot loader without USB debugging on ?????
Tanx
Click to expand...
Click to collapse
bootloader is unlocked with fastboot not adb, so usb debugging is not required. Btw usb debugging only affect the usb connection when the phone is booted in the OS so its does not affect bootloader unlocking, fastboot commands or adb commands from recovery.

alray said:
bootloader is unlocked with fastboot not adb, so usb debugging is not required. Btw usb debugging only affect the usb connection when the phone is booted in the OS so its does not affect bootloader unlocking, fastboot commands or adb commands from recovery.
Click to expand...
Click to collapse
I tried unlocking bootloader with htcdev all thing gose OK but after restart phone is lock again I should say phone is dead and hang on HTC logo

Waiting for help .......

afghan-gsm-mastermind said:
Waiting for help .......
Click to expand...
Click to collapse
how are we suppose to help you with a locked bootloader ?

clsA said:
how are we suppose to help you with a locked bootloader ?
Click to expand...
Click to collapse
I've told him this in a previous thread. . Without an unlocked bootloader he is stuck.. He has to unlock first...
Sent from my GT-I9505 using XDA Premium 4 mobile app

s-on, No Os, unlocked, got twrp. Cant install stock RUU!!
Hi. Im a little bit confused with my HTC__016 One M7, My phone is currently S-On with no Os and no recovery image. I cant transfer a stock ruu to my phone or twrp to install. I have tried using adb and fastboot, I have cleared all caches too. If i boot into recovery and i use twrp to fix permissions it says E: Unable to mount data and cache. I have tried adb sideload aswell and it seems to work but then always fails at the certificate verification.. I assume that this is S-On's fault. How should i proceed? I dont want to hard brick my device, i still have my basebands too thank goodness..
What can I do to fix my phones file system or how can i transfer the stock RUU.. I have tried 3 diferent stock RUUs and they all fail at certificate verification. I would really appreciate the help..
Thanks A lot

AnonZA said:
Hi. Im a little bit confused with my HTC__016 One M7, My phone is currently S-On with no Os and no recovery image. I cant transfer a stock ruu to my phone or twrp to install. I have tried using adb and fastboot, I have cleared all caches too. If i boot into recovery and i use twrp to fix permissions it says E: Unable to mount data and cache. I have tried adb sideload aswell and it seems to work but then always fails at the certificate verification.. I assume that this is S-On's fault. How should i proceed? I dont want to hard brick my device, i still have my basebands too thank goodness..
What can I do to fix my phones file system or how can i transfer the stock RUU.. I have tried 3 diferent stock RUUs and they all fail at certificate verification. I would really appreciate the help..
Thanks A lot
Click to expand...
Click to collapse
Post a fastboot getvar all minus imei no and serial no. Post links to recovery's you have tried and links to RUU'S. and also commands you have tried to flash recovery and RUU's
Sent from my GT-I9505 using XDA Premium 4 mobile app

AnonZA said:
Hi. Im a little bit confused with my HTC__016 One M7, My phone is currently S-On with no Os and no recovery image. I cant transfer a stock ruu to my phone or twrp to install. I have tried using adb and fastboot, I have cleared all caches too. If i boot into recovery and i use twrp to fix permissions it says E: Unable to mount data and cache. I have tried adb sideload aswell and it seems to work but then always fails at the certificate verification.. I assume that this is S-On's fault. How should i proceed? I dont want to hard brick my device, i still have my basebands too thank goodness..
What can I do to fix my phones file system or how can i transfer the stock RUU.. I have tried 3 diferent stock RUUs and they all fail at certificate verification. I would really appreciate the help..
Thanks A lot
Click to expand...
Click to collapse
sounds like your trying to sideload a RUU.zip .. that won't work
to flash RUU.zip use
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip <<yes two times
fastboot reboot
you just need the rom.zip in the same folder as fastboot

HTC__016
bored_stupid said:
Post a fastboot getvar all minus imei no and serial no. Post links to recovery's you have tried and links to RUU'S. and also commands you have tried to flash recovery and RUU's
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__016
(bootloader) battery-status: good
(bootloader) battery-voltage: 3847mV
(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.045s
---------- Post added at 04:00 PM ---------- Previous post was at 03:55 PM ----------
clsA: I tried those command million of times. It kept coming back with "boot loader signature verification..." My phone is WIPED as you can see. So usb debugging is off presumably..
Click to expand...
Click to collapse

You have the international M7 ul so download and install this rom. Follow the guide on installing
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
Sent from my GT-I9505 using XDA Premium 4 mobile app

I Formatted partition using "How to: Fix a corrupted DATA partition on the HTC One" Then tried these commands (1) fastboot oem rebootRUU (2) fastboot flash zip rom.zip
{C:\Users\####\Desktop\Mini SDK>fastboot flash zip rom.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1239446 KB)...
OKAY [ 46.879s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 61.244s
I think my next step is a stock stock RUU right?
Thanks a lot for the help..

Wrong one Apparently..
bored_stupid said:
You have the international M7 ul so download and install this rom. Follow the guide on installing
(LINK)
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I ran with admin rights, went through all the windows till i said update.. then i get error code 155, and that error code means incorrect ROM according to the programs readme!
What other ROM should I try?
Sorry to be such a pain.. I just need to use my device again.. lol

AnonZA said:
I Formatted partition using "How to: Fix a corrupted DATA partition on the HTC One" Then tried these commands (1) fastboot oem rebootRUU (2) fastboot flash zip rom.zip
{C:\Users\####\Desktop\Mini SDK>fastboot flash zip rom.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1239446 KB)...
OKAY [ 46.879s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 61.244s
I think my next step is a stock stock RUU right?
Thanks a lot for the help..
Click to expand...
Click to collapse
Basically you are trying to flash a file in the bootloader that is not intended to be flashed that way. Use custom recovery or it may be an update, in that case it needs stock recovery.
Sent from my GT-I9505 using XDA Premium 4 mobile app

Need help with a HTC one M7

Hello friends
I hope you can help me with my problem, now I have lived without a mobile in 1.5 weeks.
I have tried s-off it and root it but it has deleted firmware and i cant not install anything on it after what I have done ..
in boot it says
*** Tampered ***
*** UNLOCKED ***
M7_PVT SHIP S_ON RH
HBOOT - 1.61.0000
RADIO-4T.35.3218.16
OpenDSP-v35.120274.0718
OS 7.19.401.30
eMMC boot 2048MB
Recover:
Team Win Recovery Project v2.6.3.3 when i get out off recovery it says that it is not rootet
I have tried everything when I try and install a ROM but it will not because it says there is no MD5 files but there are MD5 files I try to ...
Are there any of you who may link or tell me how I get on so I can use my mobile again
Thanks in advance

Ricki1977 said:
Hello friends
I hope you can help me with my problem, now I have lived without a mobile in 1.5 weeks.
I have tried s-off it and root it but it has deleted firmware and i cant not install anything on it after what I have done ..
in boot it says
*** Tampered ***
*** UNLOCKED ***
M7_PVT SHIP S_ON RH
HBOOT - 1.61.0000
RADIO-4T.35.3218.16
OpenDSP-v35.120274.0718
OS 7.19.401.30
eMMC boot 2048MB
Recover:
Team Win Recovery Project v2.6.3.3 when i get out off recovery it says that it is not rootet
I have tried everything when I try and install a ROM but it will not because it says there is no MD5 files but there are MD5 files I try to ...
Are there any of you who may link or tell me how I get on so I can use my mobile again
Thanks in advance
Click to expand...
Click to collapse
You have opened a thread in thw wrong section

simon27gr said:
You have opened a thread in thw wrong section
Click to expand...
Click to collapse
Ohhhhh sorry whot to do

Ricki1977 said:
Ohhhhh sorry whot to do
Click to expand...
Click to collapse
I've moved the thread to the M7 Q&A section for you, that's where questions go. In future please don't post in the development sections unless you're actually providing development. Thanks!

Heisenberg said:
I've moved the thread to the M7 Q&A section for you, that's where questions go. In future please don't post in the development sections unless you're actually providing development. Thanks!
Click to expand...
Click to collapse
ohh thanks Heisenberg

Ricki1977 said:
Hello friends
I hope you can help me with my problem, now I have lived without a mobile in 1.5 weeks.
I have tried s-off it and root it but it has deleted firmware and i cant not install anything on it after what I have done ..
in boot it says
*** Tampered ***
*** UNLOCKED ***
M7_PVT SHIP S_ON RH
HBOOT - 1.61.0000
RADIO-4T.35.3218.16
OpenDSP-v35.120274.0718
OS 7.19.401.30
eMMC boot 2048MB
Recover:
Team Win Recovery Project v2.6.3.3 when i get out off recovery it says that it is not rootet
I have tried everything when I try and install a ROM but it will not because it says there is no MD5 files but there are MD5 files I try to ...
Are there any of you who may link or tell me how I get on so I can use my mobile again
Thanks in advance
Click to expand...
Click to collapse
relock your bootloader and flash the 7.19.401.51 RUU
Instructions how to flash here

How do i relock my bootloder
Sendt fra min D6603 med Tapatalk

Ricki1977 said:
How do i relock my bootloder
Sendt fra min D6603 med Tapatalk
Click to expand...
Click to collapse
read the instructions (step 4)

Thx m8
Sendt fra min D6603 med Tapatalk

Ricki1977 said:
Thx m8
Sendt fra min D6603 med Tapatalk
Click to expand...
Click to collapse
alray it did not work
:\Program Files\Android\Android Studio>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 46(ms)
C:\Program Files\Android\Android Studio>fastboot flash zip RUU.zip
sending 'zip'... (50228 KB) OKAY
sending time = 3.448 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 10(s)
C:\Program Files\Android\Android Studio>fastboot reboot-bootloader
rebooting into bootloader... OKAY
Execution time is 31(ms)
C:\Program Files\Android\Android Studio>

Ricki1977 said:
alray it did not work
:\Program Files\Android\Android Studio>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 46(ms)
C:\Program Files\Android\Android Studio>fastboot flash zip RUU.zip
sending 'zip'... (50228 KB) OKAY
sending time = 3.448 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 10(s)
C:\Program Files\Android\Android Studio>fastboot reboot-bootloader
rebooting into bootloader... OKAY
Execution time is 31(ms)
C:\Program Files\Android\Android Studio>
Click to expand...
Click to collapse
Are you using the fastboot version porivded in that thread and are yo uusig the correct RUU?

Yes them you have link to

Ricki1977 said:
Yes them you have link to
Click to expand...
Click to collapse
Ok so try the 7.19.401.22 RUU insteand of the .51 one. You will need to follow instructions at the end of post #2 before flashing the RUU (re-unlock the bootloader, flash twrp recovery and use the tool I have made so you can change your version-main number and flash the 7.19.401.22 ruu)

It Works thanks alray.. Now alray can you help with the next step to root and what rom is the best for HTC one m7..
Sendt fra min D6603 med Tapatalk

Ricki1977 said:
It Works thanks alray.. Now alray can you help with the next step to root and what rom is the best for HTC one m7..
Sendt fra min D6603 med Tapatalk
Click to expand...
Click to collapse
There isn't any best rom, all roms are different. You'll have to try some yourself before knowing which one is the best for you. If you want to flash a custom rom, unlock your bootloader, flash twrp recovery, copy the zip file to your phone storage and install using twrp recovery. Most custom roms are pre-rooted so you don't need to flash supersu. If you only want to root your stock rom, simply unlock our bootloader, flash twrp and flash the latest supersu.zip

Managed to soft-brick my HTC One m7, need help to recover

Hi everyone, I inherited a used HTC One m7 from my son after my iPhone 4 died. This is my first android device. The phone worked perfect with the stock OS, except the green tint issue after a factory pink tint camera fix. My son never had the time to address the issue, but I decided to try to fix the problem by replacing the awb_cal file. I'm not a Linux guy, so I started from scratch.
Unlocked, installed TWRP, rooted. Because of my inexperience with not only TWRP, but Linux, during the process I managed to wipe clean my HTC. I read lots of instructions to get back in business, but some of them caused more trouble than help. Now, I ended up with a nonfunctioning beautiful piece of technology.
This is where I'm now:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.661.52
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34RW911052
(bootloader) imei: 354439053805232
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4330mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.137s
Using Windows 7 Pro, have installed the fastboot/ADB drivers, installed HTC Sync Manager.
TWRP 3.0.2-0 installed, but not working, can't get into twrp recovery from fastboot-usb mode, it returns to fastboot-usb. In this mode fastboot recognizes the device in cmd. The only way to get ADB recognize my device is to go through the Unlock_code routine. The phone boots right into TWRP, but stops responding at the Running OpenRecoveryScript screen, "Updating partition details... done - Full SELinux support is present. - Running Recovery Commands - Formatting Cache using make_ext4fs... - Wiping data without wiping /data/media ... - Done. - Done processing script file". It hangs here, but now ADB recognizes my device. After rebooting manually into fastboot, it shows Tampered - Relocked, so the unlocking not finishing.
I tried to flash the PN07IMG_M7_UL_L50_SENSE60_MR_TELUS_WWE_7.17.661.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420202_signed.zip file in Relocked, with htc_fastboot in rebootRUU mode, but after the first writing I cannot start the second flashing, because it doen't stop but starts sending 'zip' ... (43286 KB) by itself and gets unresponsive at that line:
sending 'zip'... (43286 KB) OKAY
sending time = 3.097 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
For "hboot-preupdate" response, restart the same procedure for device HT34RW9110
52...
sending 'zip'... (43286 KB)
Since that in the Bootloader it says in red: OS-7.17.661.52 (7.17.661.7)
I tried to give as much detail as I can, and now I need help please, what should I do. Thanks

vik919 said:
After rebooting manually into fastboot, it shows Tampered - Relocked, so the unlocking not finishing.
Click to expand...
Click to collapse
Unlocking the bootloader requires the stock recovery, not a custom recovery because when unlocking the bootloader, the phone must first make a factory reset using the stock recovery before the bootloader can be unlocked (this is to prevent unauthorized access to your data). If you don't have the stock recovery, your phone will try to boot it, custom recovery will boot instead of the stock one, unlock process will fail because the script is made for the stock recovery, phone will reboot to bootloader mode with the phone still in the locked/relocked state. Unfortunately, you can not boot custom software (recovery/rom/kernel) if the bootloader is locked/relocked. Flashing the recovery partition also requires an unlocked bootloader. You're kinda stock in an endless loop... You need to unlock the bootloader, bootloader unlock requires stock recovery, flashing back the stock recovery requires an unlocked bootloader... Long story short, never relock if custom software is installed.
When the phone is S-ON and (re)Locked, you can only flash signed files (official HTC files) that are same or newer version than what is already on your phone. You'll need to find either the 7.17.661.52 RUU or a 7.17.661.52 firmware.zip. (firmware.zip can be extracted from an ota update.zip so the 7.17.661.52 update file would be ok).

alray said:
Unlocking the bootloader requires the stock recovery, not a custom recovery because when unlocking the bootloader, the phone must first make a factory reset using the stock recovery before the bootloader can be unlocked (this is to prevent unauthorized access to your data). If you don't have the stock recovery, your phone will try to boot it, custom recovery will boot instead of the stock one, unlock process will fail because the script is made for the stock recovery, phone will reboot to bootloader mode with the phone still in the locked/relocked state. Unfortunately, you can not boot custom software (recovery/rom/kernel) if the bootloader is locked/relocked. Flashing the recovery partition also requires an unlocked bootloader. You're kinda stock in an endless loop... You need to unlock the bootloader, bootloader unlock requires stock recovery, flashing back the stock recovery requires an unlocked bootloader... Long story short, never relock if custom software is installed.
When the phone is S-ON and (re)Locked, you can only flash signed files (official HTC files) that are same or newer version than what is already on your phone. You'll need to find either the 7.17.661.52 RUU or a 7.17.661.52 firmware.zip. (firmware.zip can be extracted from an ota update.zip so the 7.17.661.52 update file would be ok).
Click to expand...
Click to collapse
Thanks alray for your response.
So, that PN07IMG_M7_UL_L50_SENSE60_MR_TELUS_WWE_7.17.661.7_ Radio_4T.35.3218.16_10.33Q.1718.01L_release_420202 _signed.zip file can't flash somehow my 7.17.661.52 firmware? I was not able to find any other file for my phone then this one. I don't use the phone on the Telus network anymore. is there any workaround?

vik919 said:
Thanks alray for your response.
So, that PN07IMG_M7_UL_L50_SENSE60_MR_TELUS_WWE_7.17.661.7_ Radio_4T.35.3218.16_10.33Q.1718.01L_release_420202 _signed.zip file can't flash somehow my 7.17.661.52 firmware? I was not able to find any other file for my phone then this one. I don't use the phone on the Telus network anymore. is there any workaround?
Click to expand...
Click to collapse
There is a 7.17.661.52 ruu on ir-file.com but downloading from this website requires a paid subscription
Sent from my HTC One using XDA Labs

alray said:
There is a 7.17.661.52 ruu on ir-file.com but downloading from this website requires a paid subscription
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
Is this the one you mean?
pn07img_m7_ul_l50_sense60_mr_telus_wwe_7.17.661.52_radio_4t.35.3218.16_10.33q.1718.01l_release_460209_signed.zip

vik919 said:
Is this the one you mean?
pn07img_m7_ul_l50_sense60_mr_telus_wwe_7.17.661.52_radio_4t.35.3218.16_10.33q.1718.01l_release_460209_signed.zip
Click to expand...
Click to collapse
Yes
Sent from my HTC One using XDA Labs

alray said:
Yes
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
I wouldn't mind to pay that 20 bucks if I knew that it would get me through the first steps to fix my phone. My only concern is that I already tried the
PN07IMG_M7_UL_L50_SENSE60_MR_TELUS_WWE_7.17.661.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420202_signed.zip
file and it did not work. This is the one which went in once, but I didn't get the opportunity to flash second time. It is now hanging in brackets in my bootloader beside the 7.1.7.661.52 firmware number.
Also, I checked this file and I can't see any zip file in it I could extract. Wouldn't it be with that paid one which looks pretty much the same except the firmware version number?
PN07IMG_M7_UL_L50_SENSE60_MR_TELUS_WWE_7.17.661.52_Radio_4T.35.3218.16_10.33Q.1718.01l_release_46020 9_signed.zip
Wait a minute!
I just double checked and found at IR-File.com under Firmware an other file for my phone.
pn07img_m7_ul_l50_sense60_mr_telus_wwe_7.17.661.7_radio_4t.35.3218.16_10.33q.1718.01l_release_420202_signed_hboot.zip
This file ending with _hboot.zip only 493.0 MB in size compare to the other two files which are both about 1.5 GB. Is it possible that this latter one has the firmware.zip in it I could extract?
Please, advise, which one do I need?