Related
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
hello,
so i recently accidentally removed my android OS from my htc one (m7) and the backup i took , and now im stuck with a bricked phone.
it is still unlocked , S-on however and i have the Twrp custom recovery.
I have the stock RUU for my phone but i can't use ADB push command to forward it to my phone.
It might be because my usb debugging is off ( probably not ) but i cant open my phone , it keeps stuck at the bootscreen.
i also couldnt flash it with fasboot flash zip command.
If anyone could help me out with this, i would be so happy.
Thanks in advance
angizwa said:
hello,
so i recently accidentally removed my android OS from my htc one (m7) and the backup i took , and now im stuck with a bricked phone.
it is still unlocked , S-on however and i have the Twrp custom recovery.
I have the stock RUU for my phone but i can't use ADB push command to forward it to my phone.
It might be because my usb debugging is off ( probably not ) but i cant open my phone , it keeps stuck at the bootscreen.
i also couldnt flash it with fasboot flash zip command.
If anyone could help me out with this, i would be so happy.
Thanks in advance
Click to expand...
Click to collapse
What RUU are you trying to flash? Here is alray's procedure for your situation. You might want to check the prerequisites on installed drivers. Also, is there a RUU.exe file to use instead of a zip file?
If these procedures don't work, then post a fastboot getvar all except for the imei and serialno.
@majmoz
The ruu im using is a zip ( i used it before and it works, ) its the guru reset M7 3.62.401.1, my drivers work too , it recognizes my phone when plugged into my pc
here is my getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4070mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.165s
angizwa said:
@majmoz
The ruu im using is a zip ( i used it before and it works, ) its the guru reset M7 3.62.401.1, my drivers work too , it recognizes my phone when plugged into my pc
here is my getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4070mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.165s
Click to expand...
Click to collapse
angizwa said:
hello,
so i recently accidentally removed my android OS from my htc one (m7) and the backup i took , and now im stuck with a bricked phone.
it is still unlocked , S-on however and i have the Twrp custom recovery.
I have the stock RUU for my phone but i can't use ADB push command to forward it to my phone.
It might be because my usb debugging is off ( probably not ) but i cant open my phone , it keeps stuck at the bootscreen.
i also couldnt flash it with fasboot flash zip command.
If anyone could help me out with this, i would be so happy.
Thanks in advance
Click to expand...
Click to collapse
guru reset M7 3.62.401.1 is not a RUU, its a ROM (stock rom) and must be installed using a custom recovery, not using "fastboot flash zip" command which is only used to flash RUU.zip or Firmware.zip
However, 3.62.401.1 is no longer the version you need (your hboot is 1.57) so you probably need the 5.11.401.10 or 6.09.401.5 rom.
Also usb debugging have nothing to do with using adb from custom recovery, its only to enable adb when booted in the OS.
make sure to use twrp 2.6.3.3 with latest adb 1.0.31 and latest htc drivers installed and push the correct stock rom to your phone using adb push or sideload.
@alray
oohh okay thanks, ill get that twrp, but do i have to change twrp version ? mine is 2.7-something, i'll download the correct ruu... i feel so stupid right now thanks, i really hope this works
angizwa said:
@alray
oohh okay thanks, ill get that twrp, but do i have to change twrp version ? mine is 2.7-something, i'll download the correct ruu... i feel so stupid right now thanks, i really hope this works
Click to expand...
Click to collapse
There is no RUU you can flash for that version with s-on. Find a stock rom for your version. And better to use twrp 2.6.3.3
Sent from my HTC One using XDA Free mobile app
you can sideload a rom through adb while you're in twrp super easy and fast
@alray
oh okay ill look for a stock rom then
@2B_4G10
i know i tried sideload and push, but for some reason ADB doesnt want to work
i typed adb devices in command and it did show an empty list, no idea why...
hmm i tried flashing the stock rom,
i got this error
http://i.imgur.com/XzOOJYE.jpg
what does this mean ?
oh and after relocking, it gave me a signature check (remote : 12 ) fail... :/
angizwa said:
hmm i tried flashing the stock rom,
i got this error
http://i.imgur.com/XzOOJYE.jpg
what does this mean ?
oh and after relocking, it gave me a signature check (remote : 12 ) fail... :/
Click to expand...
Click to collapse
look back at post #4, already explained why
@alray
oh... so its not a stock rom ? adb doesnt work on my device anymore... adb devices gives me an empty list...
and i cant flash the other TWRP version ... it gives me this problem :
target reported max download size of 1514139648 bytes
sending 'customrecovery' (10854 KB)...
OKAY [ 1.767s]
writing 'customrecovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.709s
angizwa said:
@alray
oh... so its not a stock rom ?
Click to expand...
Click to collapse
Only RUU (Rom Update Utility) can be flashed with fastboot flash zip commands, not ROM even if the rom is a STOCK rom. RUUs and ROMS are 2 differents things. The RUU is a package containing the system(ROM), kernel, radio, bootloader, touch screen drivers and much more. It must be signed with HTC encrypted key to be flashed using "fastboot flash zip"
A ROM is a package including the system (/system) and the kernel (boot.img) and MUST be flashed from custom recovery, even if its a stock rom (like a guru reset rom or a stock odexed rom)
adb doesnt work on my device anymore... adb devices gives me an empty list...
Click to expand...
Click to collapse
Probably because your drivers are not installed correctly. this can be verified from Windows device manager. When the phone is booted in recovery, check that the phone is listed as a "android ADB interface".
and i cant flash the other TWRP version ... it gives me this problem :
target reported max download size of 1514139648 bytes
sending 'customrecovery' (10854 KB)...
OKAY [ 1.767s]
writing 'customrecovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.709s
Click to expand...
Click to collapse
FAILED (remote: signature verify fail) = Locked or Relocked bootloader, you must have an unlocked bootloader to flash recovery.
@angizwa follow procedure linked at post #2
nope, no android ADB in my driver list when in recovery oO , but i can see android usb devices when in fastboot... i guess i have the wrong drivers... ill see if i can find them, i really hope that was the problem oO
angizwa said:
hmm i tried flashing the stock rom,
i got this error
http://i.imgur.com/XzOOJYE.jpg
what does this mean ?
oh and after relocking, it gave me a signature check (remote : 12 ) fail... :/
Click to expand...
Click to collapse
you flash roms with custom recovery (TWRP) not with fastboot. Why did you relock the bootloader ? unlock it reflash TWRP 2.6.3.3 then sideload / Push the rom
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
@clsA
yes i tried sideload before, but as i said, my adb doesnt work... adb devices does show me an empty list ...
angizwa said:
@clsA
yes i tried sideload before, but as i said, my adb doesnt work... adb devices does show me an empty list ...
Click to expand...
Click to collapse
Then you need to fix your drivers
see post 2 of the superguide
http://forum.xda-developers.com/showthread.php?t=2541082
@clsA
ok thanks, ill try fixing them
Hello,
Okay so I had an HTC one that was stuck on the boot screen. Well I had a feeling it was rooted but was not sure because clorkworkmod always said boot with "root access" which I ignored. So first off I found something called guru reset 2.24.401.8 which was my version of my phone. So I used adb side load to move to my device then installed it. It worked fine and I was excited however it booted to a black screen with only the battery status, reception meter, and time bar. When I tried using recovery again the phone would show a green sign and then a red exclamation mark sign. I tried for so long going into recovery, but to no avail. I used fast boot to flash recovery and erase cache but did not work. I am terribly stuck and need help.
MIDN0710000
Version:2.24.401.8
Please help a brother in need.
Thank you
Sorry for any mistake wrote this really late.
kobster98 said:
Hello,
Okay so I had an HTC that was stuck on the boot screen. Well I had a feeling it was rooted but was not sure because clorkworkmod always say boot with "root access" which I ignored. So first off I found something called guru reset 2.24.401.8 which was my version of my phone. So I use adb side load to move to my device then install it. It worked fine and I was excited however it booted a black screen with only the battery status reception meter and time. When I tried using recovery again the phone would show a green sign and then a red exclamation mark sign. I tried for so long going in recovery to no avail. I use fast boot to flash recovery and erase cache but did not work. I am terribly stuck and need help.
MIDN0710000
Version:2.24.401.8
Please help a brother in need.
Thank you
Sorry for any mistake wrote this really late.
Click to expand...
Click to collapse
When you flashed the Guru Reset you must have selected "stock recovery" because that is the black screen with green or red triangle. Follow these steps:
Get TWRP 2.6.3.3 from: http://techerrata.com/browse/twrp2/m7
(make sure MD5 is correct, that site does not play nice with download managers)
in bootloader/FASTBOOT USB:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Thanks
I have been able to do it and thank you, but i am having issue with adb my fastboot work and is able to find my devices but adb does not.
kobster98 said:
I have been able to do it and thank you, but i am having issue with adb my fastboot work and is able to find my devices but adb does not.
Click to expand...
Click to collapse
ADB works in OS/Android with USB Debugging enabled in Developer Options and in Recovery Mode. It will not work if the phone is in bootloader/FASTBOOT USB.
About to give up
Okay you have been great help, and i need major help i have tried every thing, my phone doesn't boot up properly and just has a black screen, i have tried using guru reset 2.24.401.8 to reset and it doesnt work, i tried with an unlocked bootloader, but with S-On and i read an article saying guru reset should work regardless if it is s-on or s-off. im not sure though. I am not stuck because my phone Hboot is 1.54 and i have tried using rumrunner but doesnt work because my adb only work in recovery. I would like to S-off my phone to be able to install the guru reset. rom. I have tried using RUU's but cant find my radio version. is there any possible way to S-off my phone without an OS to install unto. Or is there any way to re-install my OS i am running out of ideas. Thank you very much!!
kobster98 said:
Okay you have been great help, and i need major help i have tried every thing, my phone doesn't boot up properly and just has a black screen, i have tried using guru reset 2.24.401.8 to reset and it doesnt work, i tried with an unlocked bootloader, but with S-On and i read an article saying guru reset should work regardless if it is s-on or s-off. im not sure though. I am not stuck because my phone Hboot is 1.54 and i have tried using rumrunner but doesnt work because my adb only work in recovery. I would like to S-off my phone to be able to install the guru reset. rom. I have tried using RUU's but cant find my radio version. is there any possible way to S-off my phone without an OS to install unto. Or is there any way to re-install my OS i am running out of ideas. Thank you very much!!
Click to expand...
Click to collapse
There is no way to s-off without a Rom on the phone.
You can push a Rom to the phone using adb in recovery. Which recovery are you using. You should use TWRP 2.6.3.3 to avoid any problems installing the Guru Reset Rom.
Put the Rom in your adb/fastboot folder and rename it to rom.zip. Connect adb in recovery and in the command window type.
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push completes several minutes. When it's done install the Rom with twrp recovery.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
rom install
i tried and installed a guru reset rom,however when i installed it just boots to a plain blackscreen with only the battery status, time, and reception bar showing, yes i am using twrp 2.6.3.3.
thank you for reply
kobster98 said:
i tried and installed a guru reset rom,however when i installed it just boots to a plain blackscreen with only the battery status, time, and reception bar showing, yes i am using twrp 2.6.3.3.
thank you for reply
Click to expand...
Click to collapse
Did you install the reset Rom with Twrp 2.6.3.3 your first post indicates you used CWM
Can you please post the out put from
Code:
fastboot getvar all
Please remove imei and serial numbers before posting.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Help
Thanks,
Yea i have twrp 2..6.3.3 installed as recovery, i did have clorkworkmod previously but guru reset wiped my data after installation. So i switched to twrp recovery. What Rom or RUU should i install?
Thanks for your time. Info you need is below.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4319mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
kobster98 said:
Thanks,
Yea i have twrp 2..6.3.3 installed as recovery, i did have clorkworkmod previously but guru reset wiped my data after installation. So i switched to twrp recovery. What Rom or RUU should i install?
Thanks for your time.
Info you need is below.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4319mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Here is the only RUU I could find that is a higher version than yours. There have been people who have bricked their phone by jumping version so I have provide the firmware for the version from 2.24.401.8 to RUU 4.19.401.9.
Firmware 3.62.401.1
Firmware 4.19.401.8
RUU 4.19.401.9
To flash the firmware, place the firmware in your adb/fastboot folder, open a command window in your adb/fastboot folder:
Code:
[B][I]adb reboot bootloader[/I][/B]
After that, type:
Code:
fastboot oem lock
Type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip [COLOR="Purple"]name_of_firmware.zip[/COLOR][/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip [COLOR="Purple"]name_of_firmware.zip[/COLOR][/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot-bootloader[/I][/B]
Click to expand...
Click to collapse
After the last firmware reboots, then run the RUU.
Follow @majmoz instructions, but for the record the RUU should work fine after flashing 3.62.401.1 firmware. As the RUU will contain the full firmware up to 4.19.401.9. So no risk of firmware mismatch.
majmoz said:
Here is the only RUU I could find that is a higher version than yours. There have been people who have bricked their phone by jumping version so I have provide the firmware for the version from 2.24.401.8 to RUU 4.19.401.9.
Firmware 3.62.401.1
Firmware 4.19.401.8
RUU 4.19.401.9
To flash the firmware, place the firmware in your adb/fastboot folder, open a command window in your adb/fastboot folder:
After the last firmware reboots, then run the RUU.
Click to expand...
Click to collapse
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Thanks
So i should use the 4.19.401.9 RUU, but why am i locking the bootloader, doesnt it need to be unlocked. I will try your process. I am very grateful.
kobster98 said:
So i should use the 4.19.401.9 RUU, but why am i locking the bootloader, doesnt it need to be unlocked. I will try your process. I am very grateful.
Click to expand...
Click to collapse
Flash the 3.62.401.1 firmware as per majmoz instructions. Then you can use the RUU to update your phone to kit Kat.
You have to be unlocked to flash Custom software. But the RUU and Firmware are signed Stock files. Because your s-on you must be relocked to flash them
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Thanks
okay so i tried running the steps but my phone did not reboot once, and bootloader say successful, but i get an error.
Here:
C:\Users\Family\Desktop\root\adt-bundle-windows-x86_64-20140702\sdk\platform-too
ls>Fastboot oem rebooutruu
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.002s]
finished. total time: 0.002s
C:\Users\Family\Desktop\root\adt-bundle-windows-x86_64-20140702\sdk\platform-too
ls>fastboot flash zip 3.62.401.1_full_stock_sense_firmware.zip
sending 'zip' (97331 KB)...
OKAY [ 5.001s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 15.428s
C:\Users\Family\Desktop\root\adt-bundle-windows-x86_64-20140702\sdk\platform-too
ls>fastboot flash zip 3.62.401.1_full_stock_sense_firmware.zip
sending 'zip' (97331 KB)...
OKAY [ 5.026s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 15.452s
kobster98 said:
okay so i tried running the steps but my phone did not reboot once, and bootloader say successful, but i get an error.
Here:
C:\Users\Family\Desktop\root\adt-bundle-windows-x86_64-20140702\sdk\platform-too
ls>Fastboot oem rebooutruu
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.002s]
finished. total time: 0.002s
Click to expand...
Click to collapse
Your command to rebootRUU is incorrect it is case sensitive. You also appear to have an extra "u" in there
Code:
fastboot oem rebootRUU
After this command your phone will reboot to a screen with a silver HTC logo. This is RUU mode
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Misunderstanding
Sorry but the problem is that i get Failed (remote:12 signature verify fail) and it does not flash says finished.
kobster98 said:
Sorry but the problem is that i get Failed (remote:12 signature verify fail) and it does not flash says finished.
Click to expand...
Click to collapse
Yes because your phone is not in ruu mode. You cannot flash the firmware in the bootloader.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Misunderstanding
I am in RUU mode, its a black screen with the HTC logo, but when i type the command to flash the firmware it gives me "failed: 12 signature verify"
kobster98 said:
I am in RUU mode, its a black screen with the HTC logo, but when i type the command to flash the firmware it gives me "failed: 12 signature verify"
Click to expand...
Click to collapse
Ok strange, try this firmware zip instead http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/3.62.401.1.zip
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Thank you bro it worked your a life saver
Help needed to bring my htc m 7 uk on o2 back to stock tried every thing bar the kitchen sink using adb fastboot etc
device is showing tampered relocked tried unlocking using token from htc dev but gets stuck on white screen entering recovery,
have managed to find ruu,zip file but when i try to flash it shows cannot load ruu.zip not enough space .
BOOTLOADER 1.57.0000
BASEBAND 4T.28.3218.04
CPLD NONE
MAIN 6.14.206.2
PUT SHIP S ON
HBOOT -8064
MODELID PN0710000
CID 02 001
I CANNOT SEEM TO FIND A STOCK RUU FILE TO FLASH . WHY IS IT HTC DEV USA HAVE RUU`S TO DOWNLOAD BUT NOT HTC DEV UK
ANY POSITIVE HELP WOULD BE APPRECIATED
robbo2 said:
tried unlocking using token from htc dev but gets stuck on white screen entering recovery
Click to expand...
Click to collapse
This is a well known issue caused by a re-locked bootloader + custom firmware/recovery still installed on the phone. Always reflash stock recovery before re-locking the bootloader. To solve this issue you must reflash the 6.14.206.2 firmware.
Code:
fastboot oem rebootRUU
fastboot flash zip 6.14.206.2.zip
fastboot flash zip 6.14.206.2.zip
fastboot reboot-bootloader
then get a new unlock token:
Code:
fastboot oem get_identifier_token
Submit token to htcdev.com and wait for your Unlock_code.bin in your e-mail. Once reveiced copy your Unlock_code.bin in the same folder where adb and fastboot are.
Code:
fastboot flash unlocktoken Unlock_code.bin
^^case sensitive, so don'T forget the capital U
have managed to find ruu,zip file but when i try to flash it shows cannot load ruu.zip not enough space .
Click to expand...
Click to collapse
Which version exactly? How are you trying to flash it? Can not really help regarding this as you are not giving much information. A screenshot of your command prompt while trying to flash this file would help.
I CANNOT SEEM TO FIND A STOCK RUU FILE TO FLASH
Click to expand...
Click to collapse
So the ruu you were trying to flash above isn't a stock RUU? With s-on, you can only flash 100% stock (signed) ruu same or higher version (6.14.206.2 or above).
After unlocking the bootloader with instructions above, you can flash twrp recovery, restore this 6.14.206.2 nandroid backup, re-flash the 6.14.206.2 stock recovery. Your phone will then be stock rom and firmware and ready to take ota update. Bootloader will still show tampered and unlocked.
or
you can stay re-locked and flash the 7.18.206.2 ruu.zip. Use htc_fastboot.exe to flash:
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
fastboot reboot
and again your phone will be 100% stock firmware and software except the re-locked and tampered flags in the bootloader.
WHY IS IT HTC DEV USA HAVE RUU`S TO DOWNLOAD BUT NOT HTC DEV UK
Click to expand...
Click to collapse
RUUs are not officially available for customers, they don't have to release a RUU for every versions and they never did so.
robbo2 said:
Help needed to bring my htc m 7 uk on o2 back to stock tried every thing bar the kitchen sink using adb fastboot etc
device is showing tampered relocked tried unlocking using token from htc dev but gets stuck on white screen entering recovery,
have managed to find ruu,zip file but when i try to flash it shows cannot load ruu.zip not enough space .
BOOTLOADER 1.57.0000
BASEBAND 4T.28.3218.04
CPLD NONE
MAIN 6.14.206.2
PUT SHIP S ON
HBOOT -8064
MODELID PN0710000
CID 02 001
I CANNOT SEEM TO FIND A STOCK RUU FILE TO FLASH . WHY IS IT HTC DEV USA HAVE RUU`S TO DOWNLOAD BUT NOT HTC DEV UK
ANY POSITIVE HELP WOULD BE APPRECIATED
Click to expand...
Click to collapse
There is no RUU for O2 lollipop the latest is 4.4.2 kitkat. If you just want to return to stock for the OTA you can use my stock nandroid here https://www.androidfilehost.com/?fid=95864024717074289
To get around the bootloader unlock problem you need to flash the firmware
https://www.androidfilehost.com/?fid=95864024717074526
Download and put the zip in your fastboot folder and boot your device to the boot loader and flash the firmware
CODE]fastboot erase cache
fastboot oem rebootRUU[/CODE] **--- Case sensative ---^^^
Your device should boot to a black screen with a Silver HTC logo. This is RUU mode. We can now flash the firmware. In the command window type
Code:
fastboot flash zip firmware.zip
The first flash will be short, and will appear to fail. Thats normal its just a pre update preparing the hboot for the firmware. The phone screen will go black then return to RUU mode. So now we need to do the same command again.
Code:
fastboot flash zip firmware.zip
The second flash will take a little longer and will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal. As long as the command window has finished its output its done. Reboot to the bootloader.
Code:
fastboot reboot-bootloader
When that's done get a new unlock code.bin from htcdev to unlock your bootloader. Flash TWRP and use it to restore the stock backup. Then flash the stock recovery to get the OTA :good:
Danny201281 said:
There is no RUU for O2 lollipop the latest is 4.4.2 kitkat.
Click to expand...
Click to collapse
Looks like there is a ruu for O2 lollipop, see my post above.
Thanks sorted
When i was trying to flash the code from htc devs i have been using lower case as soon as i used upper case for the u in unlock everything fell into place thanks again for your help.
alray said:
This is a well known issue caused by a re-locked bootloader + custom firmware/recovery still installed on the phone. Always reflash stock recovery before re-locking the bootloader. To solve this issue you must reflash the 6.14.206.2 firmware.
Code:
fastboot oem rebootRUU
fastboot flash zip 6.14.206.2.zip
fastboot flash zip 6.14.206.2.zip
fastboot reboot-bootloader
then get a new unlock token:
Code:
fastboot oem get_identifier_token
Submit token to htcdev.com and wait for your Unlock_code.bin in your e-mail. Once reveiced copy your Unlock_code.bin in the same folder where adb and fastboot are.
Code:
fastboot flash unlocktoken Unlock_code.bin
^^case sensitive, so don'T forget the capital U
Which version exactly? How are you trying to flash it? Can not really help regarding this as you are not giving much information. A screenshot of your command prompt while trying to flash this file would help.
So the ruu you were trying to flash above isn't a stock RUU? With s-on, you can only flash 100% stock (signed) ruu same or higher version (6.14.206.2 or above).
After unlocking the bootloader with instructions above, you can flash twrp recovery, restore this 6.14.206.2 nandroid backup, re-flash the 6.14.206.2 stock recovery. Your phone will then be stock rom and firmware and ready to take ota update. Bootloader will still show tampered and unlocked.
or
you can stay re-locked and flash the 7.18.206.2 ruu.zip. Use htc_fastboot.exe to flash:
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
fastboot reboot
and again your phone will be 100% stock firmware and software except the re-locked and tampered flags in the bootloader.
RUUs are not officially available for customers, they don't have to release a RUU for every versions and they never did so.
Click to expand...
Click to collapse
Thanks
@alray you sir have just saved my bacon... Been looking for a Nandroid for the partners phone as the one i did got corrupted. decided to search again and this thread come up Thanks a million :good:
Hi everybody, maybe you can help me...
I'm stuck with the HTC M7 which should be from O2 UK (CID 02__001). I can't flash the official Lollipop, these are the steps I followed:
- cehcked for s-on or s-off...it is S-ON
- put phone in fastboot and sent command fastboot oem lock...it was already locked
- sent command fastboot erase cache
- sent command fastboot oem rebootRUU
- flashed file 6.14.206.zip (43mb more or less)
- sent command fastboot reboot-bootloader
Phone didn't boot, so I took the zip file named PN07IMG_M7_UL_L50_SENSE60_MR_O2_UK_7.18.206.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_423416_combined_signed.zip from above post and repeated the procedure above and in the end I got this:
sending 'zip'... (368766 KB) OKAY
sending time = 16.964 secs
writing 'zip'... (bootloader) adopting the signature containted in this image
(bootloader) signature checking...
FAIL12 signature verify fail
FAILED (remote: 12 signature verify fail)
I read twice your instructions but I don't find any mistakes in my steps...could you please help me? :highfive:
Thanks in advance!!!
slimhunter said:
Hi everybody, maybe you can help me...
Click to expand...
Click to collapse
What was the problem initially? Also post the output of "fastboot getvar all".
alray said:
What was the problem initially?
Click to expand...
Click to collapse
Hi alray, thanks for your quick reply.
Phone was not booting, it looped between the HTC green logo and the red triangle (i don't know the cause, my uncle wasn't clear when explaining what he did for causing the mess), so I decided to get rid of all of these problems by starting from a fresh install with the latest release...and still i can't get it to work
slimhunter said:
Hi alray, thanks for your quick reply.
Phone was not booting, it looped between the HTC green logo and the red triangle (i don't know the cause, my uncle wasn't clear when explaining what he did for causing the mess), so I decided to get rid of all of these problems by starting from a fresh install with the latest release...and still i can't get it to work
Click to expand...
Click to collapse
But the file you have flashed (43MB) is only the firmware not the software. Flashing the firmware can solve some issues but generally a non-booting device will need to flash a full RUU or at least a custom recovery + a rom.
Still waiting for the "fastboot getvar all" to guide you. (post above edited probably at the same time you were answering)
alray said:
But the file you have flashed (43MB) is only the firmware not the software. Flashing the firmware can solve some issues but generally a non-booting device will need to flash a full RUU or at least a custom recovery + a rom.
Click to expand...
Click to collapse
That's why I got the other, bigger file which is flashed all the way through but fails the last signature check
Here's the result of the command (made after the failed flash of PN07IMG_M7_UL_L50_SENSE60_MR_O2_UK_7.18.206.2_Radi o_4T.35.3218.16_10.33Q.1718.01L_release_423416_com bined_signed.zip
C:\ADB>fastboot getvar all
< waiting for device >
(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.18.206.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36EW906996
(bootloader) imei: 357864050372414
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4273mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-4deaef41
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
slimhunter said:
That's why I got the other, bigger file which is flashed all the way through but fails the last signature check
Here's the result of the command (made after the failed flash of PN07IMG_M7_UL_L50_SENSE60_MR_O2_UK_7.18.206.2_Radi o_4T.35.3218.16_10.33Q.1718.01L_release_423416_com bined_signed.zip
C:\ADB>fastboot getvar all
< waiting for device >
(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.18.206.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36EW906996
(bootloader) imei: 357864050372414
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4273mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-4deaef41
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
are you using htc's version of fastboot or the version from the android sdk?
The htc fastboot, renamed as "fastboot" (i kept the other .exe renaming it "old_fastboot").
slimhunter said:
The htc fastboot, renamed as "fastboot" (i kept the other .exe renaming it "old_fastboot").
Click to expand...
Click to collapse
try this run a RUU exe
when it asks connect phone
go to temp folder replace rom.zip to your zip file renaming it Rom.zip
proceed
I don't have a valid ruu exe. since the problem could be related to s-on (because of signature verification(, can you please help me in putting this phone in S-OFF? it's urgent, please :crying:
EDIT> i also tried your method, still error on signature check
slimhunter said:
I don't have a valid ruu exe. since the problem could be related to s-on (because of signature verification(, can you please help me in putting this phone in S-OFF? it's urgent, please :crying:
EDIT> i also tried your method, still error on signature check
Click to expand...
Click to collapse
S on + locked bootloader
S Off is difficult + cost $25 sunshine
So is there anything else i can do before spending money on that? thx for your support so far!
HTC_Android_Phone_RUU_2.0.16.2014.zip
slimhunter said:
That's why I got the other, bigger file which is flashed all the way through but fails the last signature check
Here's the result of the command (made after the failed flash of PN07IMG_M7_UL_L50_SENSE60_MR_O2_UK_7.18.206.2_Radi o_4T.35.3218.16_10.33Q.1718.01L_release_423416_com bined_signed.zip
Click to expand...
Click to collapse
I have this file to and it hasn't a typical signature. It's modificated, I think...
slimhunter said:
I don't have a valid ruu exe.
Click to expand...
Click to collapse
Here you can download a complete HTC M7 RUU exe folder:
HTC_Android_Phone_RUU_2.0.16.2014.zip
HTC One M7 Hboot 1.61 S-ON, how to make S-OFF on HTC One M7
slimhunter said:
Hi everybody, maybe you can help me...
I'm stuck with the HTC M7 which should be from O2 UK (CID 02__001). I can't flash the official Lollipop, these are the steps I followed:
- cehcked for s-on or s-off...it is S-ON
- put phone in fastboot and sent command fastboot oem lock...it was already locked
- sent command fastboot erase cache
- sent command fastboot oem rebootRUU
- flashed file 6.14.206.zip (43mb more or less)
- sent command fastboot reboot-bootloader
Phone didn't boot, so I took the zip file named PN07IMG_M7_UL_L50_SENSE60_MR_O2_UK_7.18.206.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_423416_combined_signed.zip from above post and repeated the procedure above and in the end I got this:
sending 'zip'... (368766 KB) OKAY
sending time = 16.964 secs
writing 'zip'... (bootloader) adopting the signature containted in this image
(bootloader) signature checking...
FAIL12 signature verify fail
FAILED (remote: 12 signature verify fail)
I read twice your instructions but I don't find any mistakes in my steps...could you please help me? :highfive:
Thanks in advance!!!
Click to expand...
Click to collapse
relock your bootloader and flash the 7.18.206.21 RUU
http://forum.xda-developers.com/htc-...ction-t3053944
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?