Database Develop

[Solved] Bricked my One?

Hello,
i'm reading here for some weeks and this forum helped me much so far. Now I made a bad mistake while flashing the latest firmware on my One and it seems that I have bricked it.
What have I done?
I used ARHD 5.1 GE on my One with an older firmware. Before that I was using ARHD 4.1. Data of my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4260mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I changed to SuperCID, before that I had VODAP102. Bootloader is relocked.
After flashing latest firmware, my sdcard got wiped. So I have no backups or any other data on my phone. The phone stops booting after the white screen with the "HTC" logo and shows a turquoise color with little stripes and nothing happens.
I tried to flash another firmware, as you can see in the phone's details. That worked, but changed nothing. I can't install a rom, because adb doesn't find my device, but fastboot does. I tried several HTC-drivers and cables and USB-slots. Nothing.
I read several How-To's but I got stuck with this. Even tried to install the 1.28.401.7 RUU, but that stops with Error 155. After first time that error occured I relocked my bootloader, but that didn't help. I can't push files to the phone, because adb doesn't work.
Now only one thing left: Asking you for help. I'm somewhat frustrated.
Peko

pekomane said:
Hello,
i'm reading here for some weeks and this forum helped me much so far. Now I made a bad mistake while flashing the latest firmware on my One and it seems that I have bricked it.
What have I done?
I used ARHD 5.1 GE on my One with an older firmware. Before that I was using ARHD 4.1. Data of my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
I changed to SuperCID, before that I had VODAP102. Bootloader is relocked.
After flashing latest firmware, my sdcard got wiped. So I have no backups or any other data on my phone. The phone stops booting after the white screen with the "HTC" logo and shows a turquoise color with little stripes and nothing happens.
I tried to flash another firmware, as you can see in the phone's details. That worked, but changed nothing. I can't install a rom, because adb doesn't find my device, but fastboot does. I tried several HTC-drivers and cables and USB-slots. Nothing.
I read several How-To's but I got stuck with this. Even tried to install the 1.28.401.7 RUU, but that stops with Error 155. After first time that error occured I relocked my bootloader, but that didn't help. I can't push files to the phone, because adb doesn't work.
Now only one thing left: Asking you for help. I'm somewhat frustrated.
Peko
Click to expand...
Click to collapse
1- remove IMEI and s/n
2- install latest TWRP 2.6.3.3 (needed for 4.4 roms)
You need TWRP 2.6.3.3 (or later) for 4.4 roms, also if you are using a GPE rom, then you need to be s-off.
Download from here: http://techerrata.com/browse/twrp2/m7 don't use a download manager, it will fail; download normally and check MD5 to make sure file is not corrupt,
go to bootloader/FASTBOOT USB, and flash it:
fastboot flash openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
3- confirm adb working in TWRP now, and unlock using: http://forum.xda-developers.com/showthread.php?t=2475914 or "revone -u"
(you don't need to relock if you're s-off)
4- push, sideload, or OTG a ROM and install
5- error 155 occurs due to hboot 1.55+, you'll need to downgrade to 1.44 to run RUU

nkk71 said:
1- remove IMEI and s/n
2- install latest TWRP 2.6.3.3 (needed for 4.4 roms)
You need TWRP 2.6.3.3 (or later) for 4.4 roms, also if you are using a GPE rom, then you need to be s-off.
Download from here: http://techerrata.com/browse/twrp2/m7 don't use a download manager, it will fail; download normally and check MD5 to make sure file is not corrupt,
go to bootloader/FASTBOOT USB, and flash it:
fastboot flash openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
3- confirm adb working in TWRP now, and unlock using: http://forum.xda-developers.com/showthread.php?t=2475914 or "revone -u"
(you don't need to relock if you're s-off)
4- push, sideload, or OTG a ROM and install
5- error 155 occurs due to hboot 1.55+, you'll need to downgrade to 1.44 to run RUU
Click to expand...
Click to collapse
Step 1 already edited, right after posting...
Thanks for now, I have to try that when I am at home. I will post here, if it worked or not.

pekomane said:
Step 1 already edited, right after posting...
Thanks for now, I have to try that when I am at home. I will post here, if it worked or not.
Click to expand...
Click to collapse
no problem, IF you're gonna end up using RUU, you need to downgrade to this hboot: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
then go to bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip <- just in case the first one says "failed flush again"
fastboot reboot-bootloader
and run the RUU, should work fine.

nkk71 said:
no problem, IF you're gonna end up using RUU, you need to downgrade to this hboot: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
then go to bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip <- just in case the first one says "failed flush again"
fastboot reboot-bootloader
and run the RUU, should work fine.
Click to expand...
Click to collapse
Thanks for that, but using RUU was only one way I thought of to get my phone working again, because adb push and sideload don't work. If the way you mentioned in your first post works, then I will be absolutely fine without using RUU. Otherwise I will try the RUU option.

It worked! Thanks for your help! :good:

pekomane said:
It worked! Thanks for your help! :good:
Click to expand...
Click to collapse
Cool, if everything OK now, could you edit main thread title to include [SOLVED], Danke

Done.
By the way, it was the first option you posted that did the trick.

pekomane said:
Done.
By the way, it was the first option you posted that did the trick.
Click to expand...
Click to collapse
Sent from my HTC One using Tapatalk

Hello nkk7
S-OFF by rumrunners
bootloader 1.55
Version main 3.62.401.1
Cid HTC001
Mid pn0710000
I have tu use ruu to go back to stock can u please give me step by step guide in sequence pls
Pls
And there is no ruu for 3.62.401.1
Thus I will have downgrade that's why I am confused
Pls give me step by step info

shurahbil said:
Hello nkk7
S-OFF by rumrunners
bootloader 1.55
Version main 3.62.401.1
Cid HTC001
Mid pn0710000
I have tu use ruu to go back to stock can u please give me step by step guide in sequence pls
Pls
And there is no ruu for 3.62.401.1
Thus I will have downgrade that's why I am confused
Pls give me step by step info
Click to expand...
Click to collapse
follow my guide in my signature, there is a RUU.EXE available for CID: HTC__001 and MID: PN0710000 (so you can follow the RUU.EXE procedure)
in my opinion do NOT GO S-ON!!

nkk71 said:
follow my guide in my signature, there is a RUU.EXE available for CID: HTC__001 and MID: PN0710000 (so you can follow the RUU.EXE procedure)
in my opinion do NOT GO S-ON!!
Click to expand...
Click to collapse
Done ok ty
Why do not go s-on

Because you will close an avenue of troubleshooting if you are S-ON..

troubles with update firmaware

hi
i have htc one with :
(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-OFF
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
this steps i have follow:
for update from 1.44.0000 to 4.19.401.9
1.Type: fastboot oem lock (if your device is not relocked yet)
2.Type: fastboot oem rebootRUU and wait for device to reboot
3.Type: fastboot flash zip firmware.zip and wait for process to complete
4.Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
5.Type: fastboot flash zip firmware.zip and wait for process to complete
6.Type: fastboot reboot
troubles after the update :/
1/ i get msg from the battery that he is 4% and that is not right.
i be sure that he is 89% is full
2/ now he is bootlocked and cant get twrp2.6.3.3 on it
3/adb is not working only fastboot
question:
1/have i take the wrong firmware?
so yes where can i find the right firmware for 1.29.401.16
2/ how can i get back bootloader unlock in 4.19.401.9
3/ revone is that working under 4.19.401.9?
i have noidea what i need to do now

aater updation phone stuck
MRX_X said:
hi
i have htc one with :
(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-OFF
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
this steps i have follow:
for update from 1.44.0000 to 4.19.401.9
1.Type: fastboot oem lock (if your device is not relocked yet)
2.Type: fastboot oem rebootRUU and wait for device to reboot
3.Type: fastboot flash zip firmware.zip and wait for process to complete
4.Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
5.Type: fastboot flash zip firmware.zip and wait for process to complete
6.Type: fastboot reboot
troubles after the update :/
1/ i get msg from the battery that he is 4% and that is not right.
i be sure that he is 89% is full
2/ now he is bootlocked and cant get twrp2.6.3.3 on it
3/adb is not working only fastboot
question:
1/have i take the wrong firmware?
so yes where can i find the right firmware for 1.29.401.16
2/ how can i get back bootloader unlock in 4.19.401.9
3/ revone is that working under 4.19.401.9?
i have noidea what i need to do now
Click to expand...
Click to collapse
i am having the same problem with a twist. My HTC One duel sim was running on 4.2.2. It is not rooted and is on stock firmware. After updation, the phone is not booting and is stuck on HTC logo. I tried the Power+volume down method(which i read in some other thread) which reveals the bootloader is locked.How and why i dont know. Kindly guide me what to do. Please note that a noob altogather. Regards

MRX_X said:
hi
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
1.Type: fastboot oem lock (if your device is not relocked yet)
i have noidea what i need to do now
Click to expand...
Click to collapse
you don't need to lock bootloader to flash firmware when you are S-Off, those instructions are for S-On!!
Here download this:
fw_TWRP_2.6.3.3_1.26.401.3.zip 8.9 MB
https://mega.co.nz/#!6VcSlICK!lWPl1wgrah43yxom7mLkpPHi71kAXoSk-BdNpaTcxNc
MD5: BF37A63802EB37B37689DE08D133484F
fastboot oem rebootRUU
fastboot flash zip fw_TWRP_2.6.3.3_1.26.401.3.zip
fastboot reboot-bootloader
fastboot erase cache
-> enter recovery
use the following adb commands to unlock your bootloader: http://forum.xda-developers.com/showthread.php?t=2475914
PS: note that the above will change your version-main to 1.26.401.3 (referring to TWRP 2.6.3.3), only the displayed value not the actual firmware, once you flash another firmware, the "displayed" number will change again.
---------- Post added at 12:36 PM ---------- Previous post was at 12:31 PM ----------
asadkhattak said:
i am having the same problem with a twist. My HTC One duel sim was running on 4.2.2. It is not rooted and is on stock firmware. After updation, the phone is not booting and is stuck on HTC logo. I tried the Power+volume down method(which i read in some other thread) which reveals the bootloader is locked.How and why i dont know. Kindly guide me what to do. Please note that a noob altogather. Regards
Click to expand...
Click to collapse
Dual SIM is different that m7_u / ul models, please check Dual SIM threads.

nkk71 said:
you don't need to lock bootloader to flash firmware when you are S-Off, those instructions are for S-On!!
Here download this:
fw_TWRP_2.6.3.3_1.26.401.3.zip 8.9 MB
https://mega.co.nz/#!6VcSlICK!lWPl1wgrah43yxom7mLkpPHi71kAXoSk-BdNpaTcxNc
MD5: BF37A63802EB37B37689DE08D133484F
fastboot oem rebootRUU
fastboot flash zip fw_TWRP_2.6.3.3_1.26.401.3.zip
fastboot reboot-bootloader
fastboot erase cache
-> enter recovery
use the following adb commands to unlock your bootloader: http://forum.xda-developers.com/showthread.php?t=2475914
PS: note that the above will change your version-main to 1.26.401.3 (referring to TWRP 2.6.3.3), only the displayed value not the actual firmware, once you flash another firmware, the "displayed" number will change again.
---------- Post added at 12:36 PM ---------- Previous post was at 12:31 PM ----------
Dual SIM is different that m7_u / ul models, please check Dual SIM threads.
Click to expand...
Click to collapse
i have get the bootloader back in unlock via the link that you have give me.
than i have install TWRP than install the custom rom AR_HDone_52.0
and so far work everything good
thanks for fast respond

MRX_X said:
i have get the bootloader back in unlock via the link that you have give me.
than i have install TWRP than install the custom rom AR_HDone_52.0
and so far work everything good
thanks for fast respond
Click to expand...
Click to collapse
It's just my home-brew of TWRP 2.6.3.3 repackaged in a firmware zip to be able to flash in RUU mode :silly:
you may wanna reconsider reflashing your firmware though, just so your "fastboot getvar all" doesnt show version-main: 1.26.401.3 (a made up version number), the actual firmware is still whatever you flashed, but doesn't show up in the getvar.
the "version-main" is always, the last thing you flashed in ruu mode.
anyway, remember, you don't need to lock with s-off: http://forum.xda-developers.com/showpost.php?p=49832723&postcount=388

nkk71 said:
It's just my home-brew of TWRP 2.6.3.3 repackaged in a firmware zip to be able to flash in RUU mode :silly:
you may wanna reconsider reflashing your firmware though, just so your "fastboot getvar all" doesnt show version-main: 1.26.401.3 (a made up version number), the actual firmware is still whatever you flashed, but doesn't show up in the getvar.
the "version-main" is always, the last thing you flashed in ruu mode.
anyway, remember, you don't need to lock with s-off: http://forum.xda-developers.com/showpost.php?p=49832723&postcount=388
Click to expand...
Click to collapse
I have put your flash ruu in me collection ( have the time is right when i be troubles than i can use it )

MRX_X said:
I have put your flash ruu in me collection ( have the time is right when i be troubles than i can use it )
Click to expand...
Click to collapse
it's very easy to create yourself too, just get whatever recovery you want, rename to recovery.img + an "android-info.txt" with proper MID and CID, and you can even make your "version-main" 6.78.401.9 (as in 6789 but WWE) :silly: in the android-info.txt file (remember it's unix format not dos/windows).
obviously you need to be S-Off to flash it since it's completely unsigned.
only reason you would need it if you locked/relocked bootloader while S-Off, which is completely redundant... no need to lock/relock with s-off

[HELP] my htc one m7 u got relocked an it just boots into bootloader

hi
i restored my phone to flash a stock rom (RUU), i relocked my phone and now the RUU file wont flash . i`ve tested everything on the internet . but device is stuck on bootloader .
hboot 1.57
os version 6.09.4116466
m7 U
sorry for my bad english

volta22 said:
hi
i restored my phone to flash a stock rom (RUU), i relocked my phone and now the RUU file wont flash . i`ve tested everything on the internet . but device is stuck on bootloader .
hboot 1.57
os version 6.09.4116466
m7 U
sorry for my bad english
Click to expand...
Click to collapse
correct ruu ? Same or higher ?
see attached picture

yatindroid said:
correct ruu ? Same or higher ?
see attached picture
Click to expand...
Click to collapse
i couldn`t find same ruu.exe for this version . there is a higher one but its only for m7 UL .
there is a backup for my version, how can i flash that ? (does that even work ? )
------------------
link for same version back up
yadi.sk/d/rQzZ9i0CdmstQ

volta22 said:
i couldn`t find same ruu.exe for this version . there is a higher one but its only for m7 UL .
there is a backup for my version, how can i flash that ? (does that even work ? )
------------------
link for same version back up
yadi.sk/d/rQzZ9i0CdmstQ
Click to expand...
Click to collapse
there is no higher ruu for your phone till maybe you found dev edition Rom which won't flash to your phone
You should flash this backup and update it

yatindroid said:
there is no higher ruu for your phone till maybe you found dev edition Rom which won't flash to your phone
You should flash this backup and update it
Click to expand...
Click to collapse
how am i suppose to flash the backup with no recovery on the phone ?
command with cmd ( or adb ) ? please walk me trough im rookie

volta22 said:
how am i suppose to flash the backup with no recovery on the phone ?
command with cmd ( or adb ) ? please walk me trough im rookie
Click to expand...
Click to collapse
unlock the bootloader, flash twrp recovery, push the backup to your phone and restore it using twrp. Your phone is stuck in bootloader mode because you have re-locked it while it was still running custom software.

alray said:
unlock the bootloader, flash twrp recovery, push the backup to your phone and restore it using twrp. Your phone is stuck in bootloader mode because you have re-locked it while it was still running custom software.
Click to expand...
Click to collapse
i cant unlock the bootloader when i flash unlock.bin device reboots and it stuck in htc logo top of the screen entering recovery mode .

volta22 said:
when i flash unlock.bin device reboots and it stuck in htc logo top of the screen entering recovery mode .
Click to expand...
Click to collapse
Its because you have relocked the bootloader with a custom recovery installed. When unlocking the bootloader, the phone must perform a factory reset and its done from the stock recovery. Because the stock recovery isn't there, it doesn't work.
so you need to reflash the stock firmware first. What is the output of "fastboot getvar all" ? (dont post imei and serialno)

alray said:
Its because you have relocked the bootloader with a custom recovery installed. When unlocking the bootloader, the phone must perform a factory reset and its done from the stock recovery. Because the stock recovery isn't there, it doesn't work.
so you need to reflash the stock firmware first. What is the output of "fastboot getvar all" ? (dont post imei and serialno)
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.28.3218.04
version-cpld: None
version-microp: None
version-main: 6.09.401.111
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__J15
battery-status: good
battery-voltage: 3937mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0

volta22 said:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.28.3218.04
version-cpld: None
version-microp: None
version-main: 6.09.401.111
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__J15
battery-status: good
battery-voltage: 3937mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
download this firmware: https://yadi.sk/d/n7BAQ8vpdqPSS
save it in the same folder were you have adb and fastboot
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
then try to unlock the bootloader again, you might need to redo the whole htcdev procedure (getting e new unlock code)

alray said:
download this firmware: https://yadi.sk/d/n7BAQ8vpdqPSS
save it in the same folder were you have adb and fastboot
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
then try to unlock the bootloader again, you might need to redo the whole htcdev procedure (getting e new unlock code)
Click to expand...
Click to collapse
thank u sooooooooooooooooooo much . it worked . *_*
i unlocked the phone and installed TWRP recovery . device went back to same version i had totally ok .
now i can update to 5 by ota ?

[Q] RUU htc m7 o2 lollipop needed not .zip file

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

Stuck in boot loop.

I have tried to flash the ROM on my M7 with no luck. Just getting a boot. I have used a mates computer and didn't noticed his copy of Hasoons was for the M8 when I changed from TWRP to ClockWorkMod and now I can't get into recovery mode. That's a new problem. The old one is not being able to successfully flash the ROM.
***TAMPERED***
***UNLOCKED***
M7 UL PVT SHIP S-ON RH
HBOOT-1.61.000
OS-7.19.771.21
eMMC-boot 2048MB
adb devises doesn't show up anything anymore but the unit is recognized by Windows.
Thanks in advance. Any help or ideas would be much appreciated.

Out of Boot Loop
OK, I'm out of the boot loop now and just struggling to image the ROM, if nothing I install will not work and I manage to re-install the RUU, is that going to be all I can install?

humback said:
OK, I'm out of the boot loop now and just struggling to image the ROM, if nothing I install will not work and I manage to re-install the RUU, is that going to be all I can install?
Click to expand...
Click to collapse
What rom (name + version) are you trying to flash?
What recovery (name + version) are you using?
What is you "fastboot getvar all" ? (don't post imei / serialno)

alray said:
What rom (name + version) are you trying to flash?
What recovery (name + version) are you using?
What is you "fastboot getvar all" ? (don't post imei / serialno)
Click to expand...
Click to collapse
Hi thanks for your reply:
(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.19.771.21
(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: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4158mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

humback said:
Hi thanks for your reply:
(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.19.771.21
(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: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4158mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Since you only answered 1 of the 3 questions asked, the only thing I can suggest you is to relock your bootloader and flash the 7.19.771.21 RUU http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944

alray said:
Since you only answered 1 of the 3 questions asked, the only thing I can suggest you is to relock your bootloader and flash the 7.19.771.21 RUU http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Click to expand...
Click to collapse
Sorry I didn't relise you asked the other questions, I have been using Hasoon2000 v3.1 and tried both CWM and TWRP. Also multiple ROMS including the reccomended stock one for the preivious carrier for HTCdev and a couple of the latest versions of kitkat and lollipop from this site.
Thanks.

humback said:
Sorry I didn't relise you asked the other questions, I have been using Hasoon2000 v3.1 and tried both CWM and TWRP. Also multiple ROMS including the reccomended stock one for the preivious carrier for HTCdev and a couple of the latest versions of kitkat and lollipop from this site.
Thanks.
Click to expand...
Click to collapse
I would suggest you to avoid using toolkits and instead work directly from a command window using the latest android sdk tools (fastboot and adb). Files that comes with these toolkits, like Hasoon 2000, are outdated.
E.g:
Hasoon 2000 v 3.1
Outdated SU binaries (1.45). Latest is 2.46 and is mandatory for lollipop roms.
Outdated TWRP recovery (2.6.0.1) - Latest twrp recovery for the M7 is 2.8.7.0, all roms requires at least 2.6.3.3, some other like Cyanogenmod requires at lest 2.7.1.1
Outdated CWM recovery (6.0.3.4) - latest cwm for M7 is 6.0.4.8
So setup your android sdk tool folder, download your custom recovery directly from TWRP or CWM website (twrp is preferred for the M7), flash the recovery using fastboot, copy the om to your phone and flash it in recovery.
humback said:
I bought this HTC last Saturday and it was on the 3 network with their software. I am on EE, my intention was to re-image the device with a non branded version O/S and get it unlocked to any network.
Click to expand...
Click to collapse
You need to be on the stock rom to sim unlock the phone so better to relock the bootloader, flash the ruu, unlock the sim using a sim unlock code, unlock the bootloader again and flash the rom you want to use.

alray said:
I would suggest you to avoid using toolkits and instead work directly from a command window using the latest android sdk tools (fastboot and adb). Files that comes with these toolkits, like Hasoon 2000, are outdated.
E.g:
Hasoon 2000 v 3.1
Outdated SU binaries (1.45). Latest is 2.46 and is mandatory for lollipop roms.
Outdated TWRP recovery (2.6.0.1) - Latest twrp recovery for the M7 is 2.8.7.0, all roms requires at least 2.6.3.3, some other like Cyanogenmod requires at lest 2.7.1.1
Outdated CWM recovery (6.0.3.4) - latest cwm for M7 is 6.0.4.8
So setup your android sdk tool folder, download your custom recovery directly from TWRP or CWM website (twrp is preferred for the M7), flash the recovery using fastboot, copy the om to your phone and flash it in recovery.
You need to be on the stock rom to sim unlock the phone so better to relock the bootloader, flash the ruu, unlock the sim using a sim unlock code, unlock the bootloader again and flash the rom you want to use.
Click to expand...
Click to collapse
So I need to use the stock, unlock the sim and then go back and use whatever ROM. That sounds good. Do you know where I could find the command I'm going to need and any examples. So far I only know how to use the all in one tools to move files.

humback said:
So I need to use the stock, unlock the sim and then go back and use whatever ROM. That sounds good. Do you know where I could find the command I'm going to need and any examples. So far I only know how to use the all in one tools to move files.
Click to expand...
Click to collapse
You can find the instructions how to flash the ruu in the link above but here it hus tin case:
lock the bootloader:
Code:
fastboot oem lock
flash the ruu:
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_H3G_UK_7.19.771.21_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430335_signed.zip
htc_fastboot reboot
Then boot the phone and inter your sim unlock code when prompted to after that the sim unlock will be permanent whatever rom you flash.
unlock the bootloader again (instructions at htcdev.com/bootloader):
Code:
fastboot oem get_identifier_token
fastboot flash unlocktoken Unlock_code.bin
then flash the custom recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
Then copy your rom to your phone storage and install it with your recovery.
Don't forget all files you want to flash (RUU, Recovery, Unlock_code) must be saved in the same folder you have adb, fastboot and htc_fastboot installed on your computer.

alray said:
You can find the instructions how to flash the ruu in the link above but here it hus tin case:
lock the bootloader:
Code:
fastboot oem lock
flash the ruu:
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_H3G_UK_7.19.771.21_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430335_signed.zip
htc_fastboot reboot
Then boot the phone and inter your sim unlock code when prompted to after that the sim unlock will be permanent whatever rom you flash.
unlock the bootloader again (instructions at htcdev.com/bootloader):
Code:
fastboot oem get_identifier_token
fastboot flash unlocktoken Unlock_code.bin
then flash the custom recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
Then copy your rom to your phone storage and install it with your recovery.
Don't forget all files you want to flash (RUU, Recovery, Unlock_code) must be saved in the same folder you have adb, fastboot and htc_fastboot installed on your computer.
Click to expand...
Click to collapse
I'm up to the flash zip and getting a error FAILED (remote 02 data lenth is to large) I took this file from the link above 1.6GB

humback said:
I'm up to the flash zip and getting a error FAILED (remote 02 data lenth is to large) I took this file from the link above 1.6GB
Click to expand...
Click to collapse
Are you using the fastboot version linked in the same thread from where you have downloaded the ruu? You must use that version of fastboot, the normal one that comes with the sdk tools can't handle big file like this ruu.

alray said:
Are you using the fastboot version linked in the same thread from where you have downloaded the ruu? You must use that version of fastboot, the normal one that comes with the sdk tools can't handle big file like this ruu.
Click to expand...
Click to collapse
No, I'll re download it when I get home, do I just replace that version in my folder with the other files as an exe?

humback said:
No, I'll re download it when I get home, do I just replace that version in my folder with the other files as an exe?
Click to expand...
Click to collapse
keep both fastboot version, save that one in the same folder as the original fastboot but name it htc_fastboot.exe so you have both fastboot version. When needed, type "htc_fastboot your_command" instead of "fastboot your_command" like when flashing the ruu:
Code:
fastboot oem rebootRUU
htc_fastboot flash zip ruu_file_name.zip
fastboot reboot

alray said:
keep both fastboot version, save that one in the same folder as the original fastboot but name it htc_fastboot.exe so you have both fastboot version. When needed, type "htc_fastboot your_command" instead of "fastboot your_command" like when flashing the ruu:
Code:
fastboot oem rebootRUU
htc_fastboot flash zip ruu_file_name.zip
fastboot reboot
Click to expand...
Click to collapse
Thanks alray, I'm back on stock. Just going to unlock the sim and reload a custom rom.

alray said:
keep both fastboot version, save that one in the same folder as the original fastboot but name it htc_fastboot.exe so you have both fastboot version. When needed, type "htc_fastboot your_command" instead of "fastboot your_command" like when flashing the ruu:
Code:
fastboot oem rebootRUU
htc_fastboot flash zip ruu_file_name.zip
fastboot reboot
Click to expand...
Click to collapse
All done, I got the phone unlocked for a couple of pounds on Ebay, and managed to install the RUU you suggested. Managed to update to a custom ROM today and everything is good. I did try to re-lock the bootloader and ran into another loop, so left it open for now with tampered and security warning for now. Apart from that it's all working fine. Thanks again for your help Alray.