Database Develop

Bricked Bootloader

Hey guys,
slowly I really get in trouble. I think the bootloader is bricked and i can use the phone as a door stopper.
I tell you what happens:
Long time ago i decided to root my phone. so I unlocked it via htcdev.com. After success I wanted to S-Off the bootloader with revone. But it failed, because of hboot 1.54.
Then I installed ARHD via TWRP and flashed boot.img via fastboot.
Long time every thing went fine, until yesterday it stoped to work and started bootloops. I managed to start the bootloader but nothing else. No ROM, no recovery (stucks on first twrp screen).
bootloader info says:
Code:
(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: 24Ð161Ð╬
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH34PW905197
(bootloader) imei: XXXXXXXXXXX7434 --> deleted just in this thread
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3794mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
Link to photo of the bootloader
What i tried until now (without any results):
"fastboot erase cache" to get access to recovery
"fastboot oem reboot RUU" to install a new hboot --> boots to white "quietly brilliant" screen, reboots then to bootloader
It would be great if someone can help me or can give me some tipps to unbrick this phone.
Thanks to all helpers.
Greetings Bulaktos

What RUU did you flash? Seeing as you're S-off you need to be extremely careful with RUUs and you might have flashed the wrong one, if you've flashed a downgrade then your device is bricked.

I didn't flashed any ruu. I only flashed the recovery and the boot.img for Arhd.
Until now I didn't flashed any firmware.
Sent from my Nexus 4 using xda app-developers app

Bulkatos said:
I didn't flashed any ruu. I only flashed the recovery and the boot.img for Arhd.
Until now I didn't flashed any firmware.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
We dont flash boot.img anymore the bootloader 1.54 does not will the command fastboot flash boot.img. flash ARHD again

Bulkatos said:
Hey guys,
slowly I really get in trouble. I think the bootloader is bricked and i can use the phone as a door stopper.
I tell you what happens:
Long time ago i decided to root my phone. so I unlocked it via htcdev.com. After success I wanted to S-Off the bootloader with revone. But it failed, because of hboot 1.54.
Then I installed ARHD via TWRP and flashed boot.img via fastboot.
Long time every thing went fine, until yesterday it stoped to work and started bootloops. I managed to start the bootloader but nothing else. No ROM, no recovery (stucks on first twrp screen).
bootloader info says:
Code:
(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: 24Ð161Ð╬
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH34PW905197
(bootloader) imei: XXXXXXXXXXX7434 --> deleted just in this thread
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3794mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
Link to photo of the bootloader
What i tried until now (without any results):
"fastboot erase cache" to get access to recovery
"fastboot oem reboot RUU" to install a new hboot --> boots to white "quietly brilliant" screen, reboots then to bootloader
It would be great if someone can help me or can give me some tipps to unbrick this phone.
Thanks to all helpers.
Greetings Bulaktos
Click to expand...
Click to collapse
Just
fastboot erase cache
fastboot flash recoveryname.zip
fastboot reboot-bootloader
Select recovery
Flash any rom
Sent from my iPod touch using Tapatalk

@n1234d
Thats all? I will gave it a try, when I have time. What about the bootloader? It seems to me that it is broken on a strange way.
Can I repair it on any way?
Sent from my Nexus 4 using xda app-developers app

Bulkatos said:
@n1234d
Thats all? I will gave it a try, when I have time. What about the bootloader? It seems to me that it is broken on a strange way.
Can I repair it on any way?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Your bootloader is absolutely fine, it's just your recovery/rom. Just reflash both and you'll be good to go.

n1234d said:
Your bootloader is absolutely fine, it's just your recovery/rom. Just reflash both and you'll be good to go.
Click to expand...
Click to collapse
Okay, sounds good.
Another question:
I've read that I need the hboot 1.55 for Android 4.3, and Arhd 30 is based on 4.3. So I have to update the bootloader anyway?
Sent from my Nexus 4 using xda app-developers app

Bulkatos said:
Okay, sounds good.
Another question:
I've read that I need the hboot 1.55 for Android 4.3, and Arhd 30 is based on 4.3. So I have to update the bootloader anyway?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Nope, you don't *need* 1.55 for a 4.3 rom, you'll be good with 1.54. If you OTA or RUU, it'll update automatically.
Sent from my iPod touch using Tapatalk

mh, seems more difficult to be.
fastboot erase cache -> says okay
fastboot flash recovery cwm.img -> says "okay"
fastboot reboot-bootloader -> reboots phone to white HTC bootscreen, then I reboot to hboot manually and choose recovery. twrps want to boot (but freeze)
It seems to me, that the command to flash the recovery didn't worked very well. What can I still do?

Bulkatos said:
mh, seems more difficult to be.
fastboot erase cache -> says okay
fastboot flash recovery cwm.img -> says "okay"
fastboot reboot-bootloader -> reboots phone to white HTC bootscreen, then I reboot to hboot manually and choose recovery. twrps want to boot (but freeze)
It seems to me, that the command to flash the recovery didn't worked very well. What can I still do?
Click to expand...
Click to collapse
try flashing the latest TWRP recovery. It can be found somewhere around here....
You can always try just restoring via RUU too, you just need to be in fastboot mode in order for it to work.

chenchen399 said:
try flashing the latest TWRP recovery. It can be found somewhere around here....
You can always try just restoring via RUU too, you just need to be in fastboot mode in order for it to work.
Click to expand...
Click to collapse
I did so. same results.
Fastboot reboot-bootloader -> reboots phone normal
fastboot flash recovery twrp.img -> twrp won't start

Try re flashing the hboot then, but you have to be s-off to do this. The only other way I can think of is RUU

Bulkatos said:
I did so. same results.
Fastboot reboot-bootloader -> reboots phone normal
fastboot flash recovery twrp.img -> twrp won't start
Click to expand...
Click to collapse
move the twrp.img file on adb folder.. and try again

Bulkatos said:
I did so. same results.
Fastboot reboot-bootloader -> reboots phone normal
fastboot flash recovery twrp.img -> twrp won't start
Click to expand...
Click to collapse
try this version of cwm it's a non touch version
https://www.dropbox.com/s/kbrzunsw0c17cyw/cwmclassic.zip

Slim Shady said:
try this version of cwm it's a non touch version
https://www.dropbox.com/s/kbrzunsw0c17cyw/cwmclassic.zip
Click to expand...
Click to collapse
how to flash a zip in fastboot? flashing the img-file via "fastboot flash recovery name.img" don't work (like all other commands).

Bulkatos said:
how to flash a zip in fastboot? flashing the img-file via "fastboot flash recovery name.img" don't work (like all other commands).
Click to expand...
Click to collapse
ur experiencing problems so try these two methods:
1.) Extract the zip and flash the recovery the usual way
fastboot erase cache
fastboot flash recovery recoveryname.img
fastboot reboot-bootloader
2.) open the zip file and edit the android text file in accordance to ur mid cid and mainver save and save it.You will need stock recovery for this method if dont have it here is the link https://www.dropbox.com/s/wq2t9fctnn9186j/stockrecovery.img
to flash stock recovery follow the steps in method 1 then follow the steps given below :
fastboot erase cache
fastboot reboot oemRUU
fastboot flash zip zipfilename.zip
then it will fail once
again the same command
fastboot flash zip zipfilename.zip
when it shows it is finished in cmd type
fastboot reboot-bootloader
either of them should lead to a working recovery

Bulkatos said:
how to flash a zip in fastboot? flashing the img-file via "fastboot flash recovery name.img" don't work (like all other commands).
Click to expand...
Click to collapse
yep:
fastboot flash recovery <name of recovery>.img
fastboot erase cache <- if you dont do this after flashing a recovery, it will most like either freeze or reboot without entering recovery
fastboot reboot-bootloader
-> enter RECOVERY
BTW: I took a look at the screenshot, does it really say in red text OS-2.24X161XX (!RR!XXXX) ??
---------- Post added at 01:56 PM ---------- Previous post was at 01:52 PM ----------
Slim Shady said:
2.) open the zip file and edit the android text file in accordance to ur mid cid and mainver
fastboot erase cache
fastboot reboot oemRUU
fastboot flash zip zipfilename.zip
when it shows it is finished in cmd type
fastboot reboot-bootloader
either of them should lead to a working recovery
Click to expand...
Click to collapse
He has S-ON so careful flashing firmware! It has to be signed and it's a one way ticket with S-On, no downgrade possible. And remember "fastboot flash zip zipfilename.zip" usually has to be done twice (the first one usually fails and says "FAILED flush again immediately" the second time it should show success)

nkk71 said:
yep:
fastboot flash recovery <name of recovery>.img
fastboot erase cache <- if you dont do this after flashing a recovery, it will most like either freeze or reboot without entering recovery
fastboot reboot-bootloader
-> enter RECOVERY
BTW: I took a look at the screenshot, does it really say in red text OS-2.24X161XX (!RR!XXXX) ??
---------- Post added at 01:56 PM ---------- Previous post was at 01:52 PM ----------
He has S-ON so careful flashing firmware! It has to be signed and it's a one way ticket with S-On, no downgrade possible. And remember "fastboot flash zip zipfilename.zip" usually has to be done twice (the first one usually fails and says "FAILED flush again immediately" the second time it should show success)
Click to expand...
Click to collapse
thanks for pointing it out actually forgot to mention it again and he is s-on that's why the second method cause that usually works.

Slim Shady said:
thanks for pointing it out actually forgot to mention it again and he is s-on that's why the second method cause that usually works.
Click to expand...
Click to collapse
you mean "edit the android text file in accordance to ur mid cid and mainver save and save it"? He can give it a try but I don't think it will work, as soon as he edits the android.txt file, the firmware.zip will become unsigned, and won't pass with 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

[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

[Q] Htc one (M7) s-off ,re-locked problem

hello , i have this problem my bootloader is S-of and re-locked i bacame like this in my attempt to lock my bootloader so i can update my android , but i ended up re-locked and s-off and i tried to unlock it back and no result can any one help me ? and my device is rooted.

nortixis said:
hello , i have this problem my bootloader is S-of and re-locked i bacame like this in my attempt to lock my bootloader
Click to expand...
Click to collapse
mkay your bootloader is relocked because you locked it, whats the problem here?
so i can update my android
Click to expand...
Click to collapse
Bootloader status (S-ON/S-OFF/LOCKED/UNLOCKED/RE-LOCKED) doesn't matter when updating
i tried to unlock it back and no result
Click to expand...
Click to collapse
Be more precise here, what happened when you tried to unlock it again?
can any one help me ?
Click to expand...
Click to collapse
Pos tthe output of "fastboot getvar all" (do not post IMEI). It will be easy to fix with s-off.

alray said:
mkay your bootloader is relocked because you locked it, whats the problem here?
Bootloader status (S-ON/S-OFF/LOCKED/UNLOCKED/RE-LOCKED) doesn't matter when updating
Be more precise here, what happened when you tried to unlock it again?
Pos tthe output of "fastboot getvar all" (do not post IMEI). It will be easy to fix with s-off.
Click to expand...
Click to collapse
well i used there was a software that gives all kind of access on you device it was on my pc but cant find it any more , there was s-off, s-on , unlock, lock and everything to for htc one but everything i tried from there still no result same stats and every time i try to update my android it just enters boot loader and stays there does nothing...if i try to instal one manually from pc with bootloader i doesn't work cant enter further then bootloader ... this is kinda the problem, any advice? all i want is to make it s-on and unlocked so i can instal manually the latest version of android if not at least regular update

nortixis said:
well i used there was a software that gives all kind of access on you device it was on my pc but cant find it any more , there was s-off, s-on , unlock, lock and everything to for htc one but everything i tried from there still no result same stats and every time i try to update my android it just enters boot loader and stays there does nothing...if i try to instal one manually from pc with bootloader i doesn't work cant enter further then bootloader ... this is kinda the problem, any advice? all i want is to make it s-on and unlocked so i can instal manually the latest version of android if not at least regular update
Click to expand...
Click to collapse
post the output of "fastboot getvar all" and most important: DO NOT MAKE IT S-ON, KEEP IT S-OFF.
http://forum.xda-developers.com/showthread.php?t=2317790

alray said:
post the output of "fastboot getvar all" and most important: DO NOT MAKE IT S-ON, KEEP IT S-OFF.
http://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
ok i used adb before and no result like i said , and i cant enter recovery mode its just restarts back to bootloader , and installing android 5.0.2 manualy i could use a tutorial ...

nortixis said:
ok i used adb before and no result like i said , and i cant enter recovery mode its just restarts back to bootloader , and installing android 5.0.2 manualy i could use a tutorial ...
Click to expand...
Click to collapse
Boot the phone in bootloader, connect it to your computer, select "fastboot" and make sure "fastboot usb" is shown in red.
Then open your command prompt from your "minimal adb and fastboot" folder
then in the command prompt type:
Code:
fastboot getvar all
Copy/paste the output here except for your IMEI/Serial number.

alray said:
Boot the phone in bootloader, connect it to your computer, select "fastboot" and make sure "fastboot usb" is shown in red.
Then open your command prompt from your "minimal adb and fastboot" folder
then in the command prompt type:
Code:
fastboot getvar all
Copy/paste the output here except for your IMEI/Serial number.
Click to expand...
Click to collapse
could we speak on skype or something? my is darkphoenix1994 it would make this much easier

nortixis said:
could we speak on skype or something? my is darkphoenix1994 it would make this much easier
Click to expand...
Click to collapse
I don't use skype unfortunately.
I can't really help if you don't post the output of "fastboot getvar all"
So go ahead, install HTC drivers, install minimal adb and fastboot, boot your phone in bootloader mode, connect it to your computer, make sure "fastboot usb" is shown in red. Launch the command prompt from your "minimal adb and fastboot" folder and type
Code:
fastboot getvar all

alray said:
I don't use skype unfortunately.
I can't really help if you don't post the output of "fastboot getvar all"
So go ahead, install HTC drivers, install minimal adb and fastboot, boot your phone in bootloader mode, connect it to your computer, make sure "fastboot usb" is shown in red. Launch the command prompt from your "minimal adb and fastboot" folder and type
Code:
fastboot getvar all
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(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: 5.16.111.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3ABW906804
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 3980mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.064s

nortixis said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(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: 5.16.111.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3ABW906804
(bootloader) imei: delete
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 3980mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.064s
Click to expand...
Click to collapse
Like I said at post #2, don't post your IMEI so edit your above post and remove it.
You said that your phone was S-OFF but I can see Its S-ON? You turned back S-ON?
Unlock your bootloader
Flash TWRP recovery
Restore the 5.16.111.4 twrp nandroid backup
flash the 5.16.111.4 stock recovery
boot the phone in the system check for ota updates and install all ota updates from 5.16.111.4 to 7.18.111.2

alray said:
Like I said at post #2, don't post your IMEI so edit your above post and remove it.
You said that your phone was S-OFF but I can see Its S-ON? You turned back S-ON?
Unlock your bootloader
Flash TWRP recovery
Restore the 5.16.111.4 twrp nandroid backup
flash the 5.16.111.4 stock recovery
boot the phone in the system check for ota updates and install all ota updates from 5.16.111.4 to 7.18.111.2
Click to expand...
Click to collapse
it was s-on my mistake...

nortixis said:
it was s-on my mistake...
Click to expand...
Click to collapse
Anyway above instructions will get you back to stock and you'll be able to update.

alray said:
Like I said at post #2, don't post your IMEI so edit your above post and remove it.
You said that your phone was S-OFF but I can see Its S-ON? You turned back S-ON?
Unlock your bootloader
Flash TWRP recovery
Restore the 5.16.111.4 twrp nandroid backup
flash the 5.16.111.4 stock recovery
boot the phone in the system check for ota updates and install all ota updates from 5.16.111.4 to 7.18.111.2
Click to expand...
Click to collapse
and how i instal the last 2 steps? i mean 3 and 4, i just don't want to mess up

as far as i can see i don't have to re-instal recovery it works now but what i do next the steps 3 and 4 how do i instal them?

nortixis said:
and how i instal the last 2 steps? i mean 3 and 4, i just don't want to mess up
Click to expand...
Click to collapse
Download the nandroid back and extract all files to your desktop. Boot in custom recovery (TWRP) a make a backup of "boot" only (this is only to generate the backup path on your phone). once done go to "my computer --> HTC One --> Internal Storage --> TWRP --> Backups --> Your serial number --> today's date backup" Erase all file in this folder (these are your boot backup files) and replace them with the files previously extracted on your desktop. Once done go in twrp "restore" menu and restore the backup, select all partition available to restore (system, boot, data).
Flashing the stock recovery is the same process as flashing a custom one
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
---------- Post added at 08:40 PM ---------- Previous post was at 08:38 PM ----------
nortixis said:
as far as i can see i don't have to re-instal recovery it works now
Click to expand...
Click to collapse
But what is the TWRP version installed?

alray said:
Download the nandroid back and extract all files to your desktop. Boot in custom recovery (TWRP) a make a backup of "boot" only (this is only to generate the backup path on your phone). once done go to "my computer --> HTC One --> Internal Storage --> TWRP --> Backups --> Your serial number --> today's date backup" Erase all file in this folder (these are your boot backup files) and replace them with the files previously extracted on your desktop. Once done go in twrp "restore" menu and restore the backup, select all partition available to restore (system, boot, data).
Flashing the stock recovery is the same process as flashing a custom one
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
---------- Post added at 08:40 PM ---------- Previous post was at 08:38 PM ----------
But what is the TWRP version installed?
Click to expand...
Click to collapse
i dont know the version its like 1 year old but doesn't matter it worked u solved my problem that i was strangling with for half of the year

HTC ONE M7 Bricked Doesn't boot any rom...

hey,i received yesterday a htc one m7 from my cousin he sent it to me to take it to a specialist,the problem here he turned off his phone one night the next day he turned on his phone it got stuck in a bootloop he has twrp and bootloader unlocked,i tried flashing custom roms such as lineage os and RR based on cm 13 and android revolution the phone doesn't run any rom,but i can access twrp and hboot 1.55 anytime please help me with this and thank you.
This was "SOLVED" (special thank to alray),read below if you have the same issue goodluck.

Khalid47 said:
hey,i received yesterday a htc one m7 from my cousin he sent it to me to take it to a specialist,the problem here he turned off his phone one night the next day he turned on his phone it got stuck in a bootloop he has twrp and bootloader unlocked,i tried flashing custom roms such as lineage os and RR based on cm 13 and android revolution the phone doesn't run any rom,but i can access twrp and hboot 1.44 anytime please help me with this and thank you.
Click to expand...
Click to collapse
Please post the output of "fastboot getvar all" (do not post the imei number)
If the phone is still on hboot 1.44, the firmware might be to old to run newer roms. Also what version of twrp is installed on the phone?

okay

alray said:
Please post the output of "fastboot getvar all" (do not post the imei number)
If the phone is still on hboot 1.44, the firmware might be to old to run newer roms. Also what version of twrp is installed on the phone?
Click to expand...
Click to collapse
first thank you for replying,i just saw your comment in a htc one m7 topic i wished you would answer hah,okay btw correction the hboot is 1.55 sorry i wrote it wrong
fastboot getvar all gave me this :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.16.3250.24
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP304
(bootloader) battery-status: good
(bootloader) battery-voltage: 4241mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ea0bccbd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
twrp version: twrp-3.1.0-0-m7univ

alray said:
Please post the output of "fastboot getvar all" (do not post the imei number)
If the phone is still on hboot 1.44, the firmware might be to old to run newer roms. Also what version of twrp is installed on the phone?
Click to expand...
Click to collapse
please help with this problem today i flashed cm11 and it's the only rom that can boot but it saw "type password to decrypt storage" at least i can see the keyboard i saw some people in the forums saying format user data i tried but no success what should i do and can you tell me which firmware was this phone on so i can upgrade or whatever i'm on hboot 1.55 does that mean i can't flash 7.19 stock? and what is the difference between firmware that always has like 30 mbs or close and ruu zip

Khalid47 said:
please help with this problem today i flashed cm11 and it's the only rom that can boot but it saw "type password to decrypt storage" at least i can see the keyboard i saw some people in the forums saying format user data i tried but no success what should i do and can you tell me which firmware was this phone on so i can upgrade or whatever i'm on hboot 1.55 does that mean i can't flash 7.19 stock? and what is the difference between firmware that always has like 30 mbs or close and ruu zip
Click to expand...
Click to collapse
VODAP304 is firmware base x.xx.161.x. There is a recent ruu for this version (7.18.161.51). In order to flash this ruu, you'll probably have to update the firmware first (7.18.161.2 firmware).
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
fastboot oem rebootRUU
htc_fastboot_flash zip PN07IMG_M7_UL_L50_SENSE60_MR_Vodafone_UK_7.18.161.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_459048_signed.zip
fastboot reboot
If your bootloader is unlocked you will need to relock it before doing the above commands. You can find htc_fastboot.exe here https://www.androidfilehost.com/?fid=24341993505161791

alray said:
VODAP304 is firmware base x.xx.161.x. There is a recent ruu for this version (7.18.161.51). In order to flash this ruu, you'll probably have to update the firmware first (7.18.161.2 firmware).
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
fastboot oem rebootRUU
htc_fastboot_flash zip PN07IMG_M7_UL_L50_SENSE60_MR_Vodafone_UK_7.18.161.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_459048_signed.zip
fastboot reboot
If your bootloader is unlocked you will need to relock it before doing the above commands. You can find htc_fastboot.exe here https://www.androidfilehost.com/?fid=24341993505161791
Click to expand...
Click to collapse
i managed to get in cm11 now i can use cm11 but i want stock,the problem is i can't see main-version it's blank anyways
oem lock then flash firmware first then ruu zip? same method?

alray said:
VODAP304 is firmware base x.xx.161.x. There is a recent ruu for this version (7.18.161.51). In order to flash this ruu, you'll probably have to update the firmware first (7.18.161.2 firmware).
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
fastboot oem rebootRUU
htc_fastboot_flash zip PN07IMG_M7_UL_L50_SENSE60_MR_Vodafone_UK_7.18.161.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_459048_signed.zip
fastboot reboot
If your bootloader is unlocked you will need to relock it before doing the above commands. You can find htc_fastboot.exe here https://www.androidfilehost.com/?fid=24341993505161791
Click to expand...
Click to collapse
Thank you so much, i managed to flash it after,i just realized i was flashing without firmware before and it was failing,you saved my cousins device thank you