Database Develop

[Q] HTC One Vodafone System Update 6.12.161.5

Last night I got a notification for a System Update to version 6.12.161.5.
Has anyone tried this yet? And any problems found?
With the last two updates over the last 3-4 months I have had major problems:
1. When VodaFone forced the Rich Communication Suite / Service upon us; abysmal battery performance and terrible instability problem with phone frequently crashing on incoming calls and texts - which I 'solved' by Disabling RCS.
2. When VodaFone pushed the next update that greyed out the box to Disable RCS (they appeared to fix the instability and battery drain problem, but now I don't even have the option to disable RCS).
After lots of self-help and web searching I now have a stable phone with decent battery life again, and given those past painful experiences I am somewhat reluctant to blindly update.
Has anyone tried this Update yet, and can you comment after a few days of usage, particuarly on stability and battery usage?
Thanks
David

I had the 6.12.161.5 update a few days ago. Ive just had the 6.12.161.8 download now. Whats the difference?

Pilch2k said:
I had the 6.12.161.5 update a few days ago. Ive just had the 6.12.161.8 download now. Whats the difference?
Click to expand...
Click to collapse
Yeah, I also just had the 6.12.161.8 update. I've still not installed the previous one. I'm planning to wait this one out, after problems in the past. Will wait until some other folks try it first

daveingram said:
Yeah, I also just had the 6.12.161.8 update. I've still not installed the previous one. I'm planning to wait this one out, after problems in the past. Will wait until some other folks try it first
Click to expand...
Click to collapse
To be honest i've not noticed any issues yet, or any changes!

needed Ota file 6.12.161.8
Hi!
Would someone be so nice to post a link to his copy of this OTA? I need it desperately to revive my bricked One m7...
I've tryed anything but to flash this one on my s-on device..
Please help to save an Htc's life!! :cyclops:

Seymour2002 said:
Hi!
Would someone be so nice to post a link to his copy of this OTA? I need it desperately to revive my bricked One m7...
I've tryed anything but to flash this one on my s-on device..
Please help to save an Htc's life!! :cyclops:
Click to expand...
Click to collapse
you can not flash OTA to unbrick a phone. You need to flash the complete rom. And btw, OTA can not be flashed manually with S-ON, it must be initiated from the OS .

Flash firmware from OTA...
alray said:
you can not flash OTA to unbrick a phone. You need to flash the complete rom. And btw, OTA can not be flashed manually with S-ON, it must be initiated from the OS .
Click to expand...
Click to collapse
Well reading this sound like different from what you say... http://forum.xda-developers.com/showthread.php?t=2182823; but probably I'm wrong...
The actual thing is there's no Ruu nor OTA nor Zip for CID VODAP405 around... Or does?

Seymour2002 said:
Well reading this sound like different from what you say... http://forum.xda-developers.com/showthread.php?t=2182823;
Click to expand...
Click to collapse
Dont know what you are referring to.
The actual thing is there's no Ruu nor OTA nor Zip for CID VODAP405 around... Or does?
Click to expand...
Click to collapse
Unfortunately, there is not much files for that CID.
I don't understand what you want to attempt with an OTA file. Firmware included in OTA are not complete, it only contain files to be updated in an incremental way. If you manually flash a firmware from an OTA updates and you do it over the wrong version (currently installed on your phone) this could end with a bricked phone (hardbrick)
Flashing the entire OTA zip file will not help either. OTA files are patches that must be installed over a working rom and proper rom version. It also must be flashed using the "software update" option within the OS (unless the phone is s-off)
what you should do imo, is to start over fresh, flash twrp recovery 2.6.3.3 and flash a "close to stock" rom

Flash firmware from OTA...
First I want to thank for your help...
Then just to explain things, here's my awkward situation:
- I have a working rom but with battery that always stays at 1% no matter what, I get an ota update but I can't update since it says there's not enought battery...
the ota It gets is a 4.19.1540.9 which doesn't match with the follwing:
version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.161.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH37WW904203
(bootloader) imei: 357864057367987
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP405
(bootloader) battery-status: good
(bootloader) battery-voltage: 4261mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
To finish the cake: recovery doesn't work and bootloader is relocked and doesn't unlock anymore....
Any suggestion?

Seymour2002 said:
First I want to thank for your help...
Then just to explain things, here's my awkward situation:
- I have a working rom but with battery that always stays at 1% no matter what, I get an ota update but I can't update since it says there's not enought battery...
the ota It gets is a 4.19.1540.9 which doesn't match with the follwing:
version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.161.8
(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: VODAP405
(bootloader) battery-status: good
(bootloader) battery-voltage: 4261mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
To finish the cake: recovery doesn't work and bootloader is relocked and doesn't unlock anymore....
Any suggestion?
Click to expand...
Click to collapse
how did you manage s-on + locked bootloader + no recovery ?
was this phone converted to DE or GPE at one time ?

Flash firmware from OTA...
I actually didn't do anything extraordinary except maybe to have flashed a rom with a different cid which got an update and brought me almost a this situation.
Then I wanted to bring the device to stock, so I flashed the original recovery and relocked the booloader. Nothing else.
I don't know why at the moment there's no way to enter recovery and if I try to unlock the bootloader again I reach the screen where I must agree on the device's screen to unlock, but then It just stuck on htc logo whilw trying to enter recovery..

Seymour2002 said:
I actually didn't do anything extraordinary except maybe to have flashed a rom with a different cid which got an update and brought me almost a this situation.
Then I wanted to bring the device to stock, so I flashed the original recovery and relocked the booloader. Nothing else.
I don't know why at the moment there's no way to enter recovery and if I try to unlock the bootloader again I reach the screen where I must agree on the device's screen to unlock, but then It just stuck on htc logo whilw trying to enter recovery..
Click to expand...
Click to collapse
are you sure your not just going to stock recovery ?
have you done the fastboot erase cache ?
followed by fastboot reboot-bootloader ?
what was the last custom recovery you had on their and what happened to make it gone ? RUU ?

Flash firmware from OTA...
clsA said:
are you sure your not just going to stock recovery ?
have you done the fastboot erase cache ? Yes, several times...
followed by fastboot reboot-bootloader ? Yes....
what was the last custom recovery you had on their and what happened to make it gone ? RUU ?
Click to expand...
Click to collapse
I was usimg twrp recovery, then I'm pretty sure I flashed the stock recovery, I don't know what happened to make it disappear, It just happened! I haven't been able to use any Ruu well since I never found the right one matching my CID., so I always got an error..

Seymour2002 said:
I was usimg twrp recovery, then I'm pretty sure I flashed the stock recovery, I don't know what happened to make it disappear, It just happened! I haven't been able to use any Ruu well since I never found the right one matching my CID., so I always got an error..
Click to expand...
Click to collapse
if you flashed the stock recovery correctly you go to the bootloader choose recovery hit power button
the screen will go black push volume up and tap power again to see the recovery menu, choose format data . factory reset
after it finishes reboot the phone and try again to unlock the bootloader

Flash firmware from OTA...
clsA said:
if you flashed the stock recovery correctly you go to the bootloader choose recovery hit power button
the screen will go black push volume up and tap power again to see the recovery menu, choose format data . factory reset
after it finishes reboot the phone and try again to unlock the bootloader
Click to expand...
Click to collapse
Once I select recovery from the bootloader menu and I press power button the phone reboots the bootloader...

SOLVED! Unbrikked THC ONE M/!!!!!
So thanks to MIke 1986 and his great page link:http://forum.xda-developers.com/showthread.php?t=2182823, I managed to recover my very very hrad brikked phone!!!!!!!!!
Here's what I did:
1- checked all phone's details with fastboot getavar all---> took note of CID - MID - versione OS installed etc.
2- took the OTA update corresponding to the firmware installed and extracted the firmware.zip
3- flashed the firmware.zip via fastboot (fastboot oem rebootRUU - fastboot flash zip firmware.zip [thanks to mike 1986]) ; #Alray: since a phone is S-On there's no risk to flash a wrong firmware and as I did anyone can do it via normal fastboot command with no issue!:angel:
4-In this way I recovered stock recovery and the possibility to unlock the bootloader again!!
5-moved a CWM nand backup to phone sd using sideload push command ( sideload push nandbackupname.zip /sd/cwm/backup/dateof backup - just make a nand backup yourself first to get exact loaction)
6-recovered from nandbackup using proper tool of cwm.
7-enjoyED MY revived device!!!!!! NOT THANKS TO ALRAY....http://cdn4.xda-developers.com/images/icons/icon8.gif

Seymour2002 said:
So thanks to MIke 1986 and his great page link:http://forum.xda-developers.com/showthread.php?t=2182823, I managed to recover my very very hrad brikked phone!!!!!!!!!
Here's what I did:
1- checked all phone's details with fastboot getavar all---> took note of CID - MID - versione OS installed etc.
2- took the OTA update corresponding to the firmware installed and extracted the firmware.zip
3- flashed the firmware.zip via fastboot (fastboot oem rebootRUU - fastboot flash zip firmware.zip [thanks to mike 1986]) ; #Alray: since a phone is S-On there's no risk to flash a wrong firmware and as I did anyone can do it via normal fastboot command with no issue!:angel:
4-In this way I recovered stock recovery and the possibility to unlock the bootloader again!!
5-moved a CWM nand backup to phone sd using sideload push command ( sideload push nandbackupname.zip /sd/cwm/backup/dateof backup - just make a nand backup yourself first to get exact loaction)
6-recovered from nandbackup using proper tool of cwm.
7-enjoyED MY revived device!!!!!! NOT THANKS TO ALRAY....http://cdn4.xda-developers.com/images/icons/icon8.gif
Click to expand...
Click to collapse
Glad you got your phone revived :good:
since a phone is S-On there's no risk to flash a wrong firmware
Click to expand...
Click to collapse
The risk is there, if you flash a firmware patch (ota firmware) over the wrong version (i.e 5.xx.xxx.x over 3.xx.xxx.x), this could brick. Happened many times that's why its mentioned in some threads. There is no risk flashing the same version like you did

[Q] relock/unroot HTC One M7, hboot 1.57

Hi guys, hope you can help me out...
I just rooted my HTC One (unlock bootloader and install TWRP recovery), WITHOUT installing any custom ROM (i just kept the factory OS, because i couldn't S-Off the phone in order to install the google play edition). The OS i had (and still have) is stock Android 4.4.3 with Sense 6.
The problem is that i need to lock the phone back (in order to benefit from the warranty - technical touchscreen problem).
I tried using Revone to lock the phone back, but i get an error: "Failed to open framebuffer device". I understand that revone doesn't work with hboot 1.57.
Could you please help me with the relocking/unrooting the phone (at least give me a link to a guide that is working for my phone configuration - hboot 1.57) ? And also could you tell me if i need a RUU, or i can just wipe/reinstall the current OS (which i never changed in the first place) ? And if i need a RUU, how can i find the one that was initially installed on the phone ?
Oh, and one more thing: at first, when my phone started, i had a Vodafone screen showing up, and some crappy apps preinstalled. After i rooted an installed twrp recovery, i don't get that vodafone screen anymore, an the crappy apps weren't preinstalled anymore.
Cheers and thanks in advance !

andreih8017 said:
Hi guys, hope you can help me out...
I just rooted my HTC One (unlock bootloader and install TWRP recovery), WITHOUT installing any custom ROM (i just kept the factory OS, because i couldn't S-Off the phone in order to install the google play edition). The OS i had (and still have) is stock Android 4.4.3 with Sense 6.
The problem is that i need to lock the phone back (in order to benefit from the warranty - technical touchscreen problem).
I tried using Revone to lock the phone back, but i get an error: "Failed to open framebuffer device". I understand that revone doesn't work with hboot 1.57.
Could you please help me with the relocking/unrooting the phone (at least give me a link to a guide that is working for my phone configuration - hboot 1.57) ? And also could you tell me if i need a RUU, or i can just wipe/reinstall the current OS (which i never changed in the first place) ? And if i need a RUU, how can i find the one that was initially installed on the phone ?
Oh, and one more thing: at first, when my phone started, i had a Vodafone screen showing up, and some crappy apps preinstalled. After i rooted an installed twrp recovery, i don't get that vodafone screen anymore, an the crappy apps weren't preinstalled anymore.
Cheers and thanks in advance !
Click to expand...
Click to collapse
Ok well first off you need s-off to set your bootloader to ***LOCKED*** and to get back to 100% stock. As your on Hboot 1.57 the only way to gain s-off is with Sunshine App. Which will cost $25 to use.
The stock Rom on your Device won't be a complete stock Rom either. When you unlock the bootloader the device is wiped along with some preload data (crappy apps) which is critical if you want the device back to stock. Or to be able to accept OTA updates. If the device is Vodafone I'm not sure there is an RUU but you should be able to get a full stock Rom from somewhere. Please post the output of
Code:
fastboot getvar all
Please remove your imei and serial number before posting. And we can see what is available for you. But if you want to go 100% stock to reinstate your warranty you will need s-off first :good:

Danny201281 said:
Ok well first off you need s-off to set your bootloader to ***LOCKED*** and to get back to 100% stock. As your on Hboot 1.57 the only way to gain s-off is with Sunshine App. Which will cost $25 to use.
The stock Rom on your Device won't be a complete stock Rom either. When you unlock the bootloader the device is wiped along with some preload data (crappy apps) which is critical if you want the device back to stock. Or to be able to accept OTA updates. If the device is Vodafone I'm not sure there is an RUU but you should be able to get a full stock Rom from somewhere. Please post the output of
Code:
fastboot getvar all
Please remove your imei and serial number before posting. And we can see what is available for you. But if you want to go 100% stock to reinstate your warranty you will need s-off first :good:
Click to expand...
Click to collapse
Hey, thanx for the quick answer !
This is the result:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4234mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.054s
What do you mean by "Or to be able to accept OTA updates" ?? At his moment i won't be able to receive any updates anymore ? :crying:
Also, what about Firewater for S-OFF ?

andreih8017 said:
Hey, thanx for the quick answer !
This is the result:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4234mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.054s
What do you mean by "Or to be able to accept OTA updates" ?? At his moment i won't be able to receive any updates anymore ? :crying:
Click to expand...
Click to collapse
Unlocking the bootloader wipes /data partition to prevent unauthorized access to your data. Problem is that HTC packed some of their stock apps in /data/preload which mean you don't have these apps anymore after unlocking the bootloader. When installing an ota update, there is a script verifying the integrity of each files to be patched, inluding apps normally present in /data/preload. After the script will find out that these apps are missing, the ota update installation will abort. So no your phone can't install ota update anymore unless you restore your phone back to stock (which can be done with s-off btw).
Also, what about Firewater for S-OFF ?
Click to expand...
Click to collapse
Its discontinued. Firewater was using online resources no more available to do its magic.
From what I see from your "getvar all" you have the pretty standard version of the M7. Follow nkk71's guide linked in my signature. You want to follow the procedure using the 1.28.401.7 ruu.zip

@alray
@Danny201281
I successfully did the following:
- S-OFF with Sunshine
- I got rid of "tampered" and "unlocked" in bootloader, by using nkk71's guide. Now it just says "locked".
- I flashed the 1.28.401.7 ruu zip
- I updated the software via OTA
Now the only thing left is to get back to S-ON, right ? How can i do this without risking the "tampered" sign (as explained in nkk71's guide) ? Any safer way ?
And btw, the result of getvar all is the same as before, except now is S-OFF instead of S-ON
Thanks,

andreih8017 said:
@alray
@Danny201281
I successfully did the following:
- S-OFF with Sunshine
- I got rid of "tampered" and "unlocked" in bootloader, by using nkk71's guide. Now it just says "locked".
- I flashed the 1.28.401.7 ruu zip
- I updated the software via OTA
Now the only thing left is to get back to S-ON, right ? How can i do this without risking the "tampered" sign (as explained in nkk71's guide) ? Any safer way ?
And btw, the result of getvar all is the same as before, except now is S-OFF instead of S-ON
Thanks,
Click to expand...
Click to collapse
To safely go back to s-on without risking tampered you should have done it before installing the OTA updates as explained in @nkk71 guide.
So now you should downgrade with the ruu again then set s-on then install OTA updates to avoid the tampered flag returning. :good:

andreih8017 said:
@alray
@Danny201281
I successfully did the following:
- S-OFF with Sunshine
- I got rid of "tampered" and "unlocked" in bootloader, by using nkk71's guide. Now it just says "locked".
- I flashed the 1.28.401.7 ruu zip
- I updated the software via OTA
Now the only thing left is to get back to S-ON, right ? How can i do this without risking the "tampered" sign (as explained in nkk71's guide) ? Any safer way ?
And btw, the result of getvar all is the same as before, except now is S-OFF instead of S-ON
Thanks,
Click to expand...
Click to collapse
how far did you go with the OTA's? as long as it's pre 7.xx (ie Lollipop), sunshine will still work, in case you the tampered sign back, you can use sunshine again to s-off, and redo it (the guide)
but as danny said, i (personally) only recommend it on 1.xx or 2.xx firmware.... i don't know the reason for tampered [sometimes/often] reappearing so i dont know what's involved or what triggers it

@Danny201281
@nkk71
i took a leap of faith and eneter the "fastboot oem writesecureflag 3" command. It worked like a charm. Afterwards i rebooted the bootloader 3 times and no "tampered" sign, but S-ON. I also rebooted the phone once and still no "tampered" sign, but S-ON. Guess it worked, right ?
As for the OTAs, i went until the last one available for HTC One - 6.09.401.11.
Thanks guys !

andreih8017 said:
@Danny201281
@nkk71
i took a leap of faith and eneter the "fastboot oem writesecureflag 3" command. It worked like a charm. Afterwards i rebooted the bootloader 3 times and no "tampered" sign, but S-ON. I also rebooted the phone once and still no "tampered" sign, but S-ON. Guess it worked, right ?
As for the OTAs, i went until the last one available for HTC One - 6.09.401.11.
Thanks guys !
Click to expand...
Click to collapse
You need to reboot the ROM three times at least, not the bootloader
Sent from my HTC One_M8 using Tapatalk

@nkk71
I did that also. Still working fine, "locked" and S-ON
Thanx,

andreih8017 said:
@nkk71
I did that also. Still working fine, "locked" and S-ON
Thanx,
Click to expand...
Click to collapse
cool, good to hear :good: :good:

Need to get stock recovery back on modified GPE

I bought HTC one M7 unlocked from HTC.com when it came out. Last year I modified it to get rid of sense and made it "google play edition". I discovered I can't get OTA updates though due to the presence of stock recovery though.
Question: How can I get rid of TWRP and get back to stock recovery? fastboot getvar version-main returns empty

anil_robo said:
I bought HTC one M7 unlocked from HTC.com when it came out. Last year I modified it to get rid of sense and made it "google play edition". I discovered I can't get OTA updates though due to the presence of stock recovery though.
Question: How can I get rid of TWRP and get back to stock recovery? fastboot getvar version-main returns empty
Click to expand...
Click to collapse
Bump - still looking for answers

anil_robo said:
Bump - still looking for answers
Click to expand...
Click to collapse
everything you need is here >> http://forum.xda-developers.com/showthread.php?t=2358781
Do Not Relock your bootloader !! It will never unlock again

That tutorial still converts to GPE. I need one that converts GPE back to Sense.

anil_robo said:
That tutorial still converts to GPE. I need one that converts GPE back to Sense.
Click to expand...
Click to collapse
What is your android version? 5.1? 5.0?

@alray
Android version is 4.4.4.
The phone downloaded an update (to 5+ ) but I am unable to install it because I have TWRP but not the stock recovery.

anil_robo said:
@alray
Android version is 4.4.4.
The phone downloaded an update (to 5+ ) but I am unable to install it because I have TWRP but not the stock recovery.
Click to expand...
Click to collapse
If its 4.4.4 (Build KTU84P) you need the 4.09.1700.1 stock recovery to install the 5.0.1 update (LRX22C). You'll then receive another notification to install the 5.1 update (LMY47O)

alray said:
If its 4.4.4 (Build KTU84P) you need the 4.09.1700.1 stock recovery to install the update.
Click to expand...
Click to collapse
Thanks a lot!
Actually my "goals" have changed. Now I need to convert the phone into "totally stock" because I want to send it to HTC for free camera fix. If you don't mind, is there an instant messenger etc where I can contact you?

anil_robo said:
Thanks a lot!
Actually my "goals" have changed. Now I need to convert the phone into "totally stock" because I want to send it to HTC for free camera fix. If you don't mind, is there an instant messenger etc where I can contact you?
Click to expand...
Click to collapse
im not really using any IM app but i can help you here. Do you remember your original CID and MID ? Also post the output of "fastboot getvar all" (remove imei/serialno before posting)

alray said:
im not really using any IM app but i can help you here. Do you remember your original CID and MID ? Also post the output of "fastboot getvar all" (remove imei/serialno before posting)
Click to expand...
Click to collapse
My wife has the exact same phone (we bought together) but hers is not tampered at all. So I have the original settings in her phone:
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
I have wife's phone (original) with me right now, and need to convert my phone (tampered) into exact same as my wife's.
fastboot getvar all returns this in my (tampered) phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.27.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
Serial and IMEI deleted
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3860mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e02a9046
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

anil_robo said:
My wife has the exact same phone (we bought together) but hers is not tampered at all. So I have the original settings in her phone:
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
I have wife's phone (original) with me right now, and need to convert my phone (tampered) into exact same as my wife's.
fastboot getvar all returns this in my (tampered) phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.27.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
Serial and IMEI deleted
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3860mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e02a9046
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
So it was originally a developer edition phone right?
First download this ruu and save it in the same folder you have fastboot and adb on your computer. Rename the file "ruu" so it will be easier in the command prompt.
Download this tool and save it on the root of your phone storage
Boot in twrp recovery, select "install" and choose "Guru_Bootloader_Reset_1.0.zip" and then "swipe to install"
Follow instruction of the installer to remove tampered from the bootloader. Don't set the bootloader to locked or re-locked. Keep it unlocked as Developer edition phones are factory bootloader unlocked.
Then boot the phone in bootloader / fastboot usb mode
Confirm that tampered is gone and bootloader is still unlocked.
With the phone still in bootloader, open a command window from your adb/fastboot folder
Code:
fastboot oem rebootRUU
phone will reboot in ruu mode, a black screen with silver htc logo
Code:
fastboot flash zip ruu.zip
first flash will report "failed, flush image again immediately, so do the same command again:
Code:
fastboot flash zip ruu.zip
this one will report "flashed successfully"
Code:
fastboot reboot-bootloader
If you want to turn the bootloader back to S-ON for warranty do this command as the final step:
Code:
fastboot oem writesecureflag 3
fastboot reboot-bootloader
and confirm phone is S-ON, Unlocked, no tampered flag.
And a big warning here, do not perform this if you are using a windows 8/8.1 computer as the ruu will downgrade hboot to 1.44. hboot 1.44 is not compatible with windows 8.1 and you'll loose fastboot connectivity after the first "fastboot flash zip ruu.zip" and you'll be stuck in ruu mode. Use windows 7. XP, Linux (Ubuntu for example) or use MacOS

alray said:
So it was originally a developer edition phone right?
First download this ruu and save it in the same folder you have fastboot and adb on your computer. Rename the file "ruu" so it will be easier in the command prompt.
Download this tool and save it on the root of your phone storage
Boot in twrp recovery, select "install" and choose "Guru_Bootloader_Reset_1.0.zip" and then "swipe to install"
Follow instruction of the installer to remove tampered from the bootloader. Don't set the bootloader to locked or re-locked. Keep it unlocked as Developer edition phones are factory bootloader unlocked.
Then boot the phone in bootloader / fastboot usb mode
Confirm that tampered is gone and bootloader is still unlocked.
With the phone still in bootloader, open a command window from your adb/fastboot folder
Code:
fastboot oem rebootRUU
phone will reboot in ruu mode, a black screen with silver htc logo
Code:
fastboot flash zip ruu.zip
first flash will report "failed, flush image again immediately, so do the same command again:
Code:
fastboot flash zip ruu.zip
this one will report "flashed successfully"
Code:
fastboot reboot-bootloader
If you want to turn the bootloader back to S-ON for warranty do this command as the final step:
Code:
fastboot oem writesecureflag 3
fastboot reboot-bootloader
and confirm phone is S-ON, Unlocked, no tampered flag.
And a big warning here, do not perform this if you are using a windows 8/8.1 computer as the ruu will downgrade hboot to 1.44. hboot 1.44 is not compatible with windows 8.1 and you'll loose fastboot connectivity after the first "fastboot flash zip ruu.zip" and you'll be stuck in ruu mode. Use windows 7. XP, Linux (Ubuntu for example) or use MacOS
Click to expand...
Click to collapse
Yes it is a developer edition phone.
Question though: My android version is 4.4.4, and the RUU you linked is 5.0 - does it matter? Won't I run into a "boot loop"?

anil_robo said:
Yes it is a developer edition phone.
Question though: My android version is 4.4.4, and the RUU you linked is 5.0 - does it matter? Won't I run into a "boot loop"?
Click to expand...
Click to collapse
The ruu linked is not 5.0 its 4.1.2 Jelly Bean

anil_robo said:
Yes it is a developer edition phone.
Question though: My android version is 4.4.4, and the RUU you linked is 5.0 - does it matter? Won't I run into a "boot loop"?
Click to expand...
Click to collapse
Wow this was simple! I'm now running stock Jelly Bean, just like a new phone two years ago
I have still left S-OFF and Unlocked - will compare these settings to how my wife's phone is, and then either leave it unlocked or locked to match hers. And then will do S-ON.
Thank you kind sir!

anil_robo said:
Wow this was simple! I'm now running stock Jelly Bean, just like a new phone two years ago
I have still left S-OFF and Unlocked - will compare these settings to how my wife's phone is, and then either leave it unlocked or locked to match hers. And then will do S-ON.
Thank you kind sir!
Click to expand...
Click to collapse
Dev edition are unlocked from factory
Security is set to S-ON from factory
anyway its to late to set the bootloader to locked because the tool to set this requires a custom recovery.

alray said:
Dev edition are unlocked from factory
Security is set to S-ON from factory
anyway its to late to set the bootloader to locked because the tool to set this requires a custom recovery.
Click to expand...
Click to collapse
I'll try this tomorrow: https://aubykhan.wordpress.com/2013...t-into-twrp-or-cwm-recovery-without-flashing/

anil_robo said:
I'll try this tomorrow: https://aubykhan.wordpress.com/2013...t-into-twrp-or-cwm-recovery-without-flashing/
Click to expand...
Click to collapse
Thats right, I forgot about this. fasboot boot recovery.img will work fine since the phone is now on hboot 1.44, but anayway as I said, dev edition are bootloader unlock from the factory so setting it Locked will be suspicious
@anil_robo see the 4th dot: http://blog.htc.com/2013/03/htc-one-developer-edition/

alray said:
Thats right, I forgot about this. fasboot boot recovery.img will work fine since the phone is now on hboot 1.44, but anayway as I said, dev edition are bootloader unlock from the factory so setting it Locked will be suspicious
@anil_robo see the 4th dot: http://blog.htc.com/2013/03/htc-one-developer-edition/
Click to expand...
Click to collapse
Well I checked wife's phone, and it is "LOCKED" to my surprise. So I have to do the same to match those settings. I bought this phone within few days when it became available, and it may not have been the developer edition I initially thought. It must have been the "international" version rather than the "unlocked developer" version.

anil_robo said:
Well I checked wife's phone, and it is "LOCKED" to my surprise. So I have to do the same to match those settings. I bought this phone within few days when it became available, and it may not have been the developer edition I initially thought. It must have been the "international" version rather than the "unlocked developer" version.
Click to expand...
Click to collapse
The international version is MID PN0710000, version base is .401 e.g. 7.19.401.2 and BS_US001 is not a CID for international version...
There a method to know what your phone was originally. Your original CID/MID and firmware/software version are stored in the MFG partition of your phone. If you can dump this partition to your computer and send it to me, we can determine for sure what it was originally. Unfortnately this partition also include your IMEI and Serial number which should be kept private, if you are ok with sharing this with me here how to proceed:
Boot twrp recovery without flashing it to your phone:
reboot your phone in bootloader / fastboot usb mode
Code:
fastboot boot [URL="https://dl.twrp.me/m7/twrp-2.8.6.0-m7.img.html"]twrp-2.8.6.0-m7.img[/URL]
once booted in twrp main menu, type these commands in the command window:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6_bakup.img
exit
exit
Then reboot the phone normally, go to "My Computer --> HTC One --> Internal Storage. You'll find the mmcblk0p6_backup.img file. send it to me via PM only

[Q] M7 softbrick (or not?) - help needed!

Hi guys!
I've been trying to get my dear One M7 alive now for 4-5 evenings. Really thought it was bricked for good, but finally made some progress. Here's what happened:
S-OFF, rooted since always but on stock/OTA from HTC. Been updating through OTAs just flashing back stock recovery before update and then switching back. I've been using CWM. I was already on the Lollipop 5.0.2 with Sense 6.0 (sofware revision 7.19.401.2) but received another minor OTA couple of weeks ago. Didn't make note of the new revision, nor the reason for the update but just followed my usual steps. Everything seemed to go as usual, but once booting back up after the update the phone got stock on the boot animation (the htc one w/beats audio just after the sound).
Immediately tried a restore from a backup I have, but continued in the same situation. Tried several/different wipes (even the data partition in the end), but no luck. Tried the best I could to search for info, but all I could find was what I'd already done. Tried to download some RUU's but the files seems corrupted and I cannot get it working. I tried to switch to TWRP, taking a new backup (of my restored, but still not working CWM-backup). Same situation. Then I tried to flash a Cyanogenmod version, and was close to giving up when it didn't work as well. Luckily I tried a couple of times more (perhaps after throwing the phone in the wall a few times) and just out of nowhere it suddenly booted and seems to be working normally. Full of hope I tried a restore again, but back to boot animation. Tried to download a clean stock install file I found on XDA with the same version as mine, but just get stuck again. Once I restore the Cyanogenmod backup, it boots perfectly.
Perhaps I am missing something obvious, but I've been doing these things for many years know (starting with the Desire @ nikez), and this just seems odd. I could seriously need some help to get it back working again as I like the stock Sense 6.0 with Lollipop.
For info some details (btw; I verified it against the data I noted just after my original Lollipop OTA early this year, and it is still identical, so i don't see any vitals have changed):
(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.401.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: **removed**
(bootloader) imei: **removed**
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4081mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks in advance for any good advice!!

tormagj said:
I was already on the Lollipop 5.0.2 with Sense 6.0 (sofware revision 7.19.401.2) but received another minor OTA couple of weeks ago. Didn't make note of the new revision
Click to expand...
Click to collapse
Its 7.19.401.22
nor the reason for the update
Click to expand...
Click to collapse
bug fixes
but just followed my usual steps.
Click to expand...
Click to collapse
Won't work for this ota, you must be 100% stock.
Thanks in advance for any good advice!![
Click to expand...
Click to collapse
flash the 7.19.401.22 ruu, it will update and fix your phone.
http://forum.xda-developers.com/showpost.php?p=59436794&postcount=2

alray said:
Its 7.19.401.22
flash the 7.19.401.22 ruu, it will update and fix your phone.
http://forum.xda-developers.com/showpost.php?p=59436794&postcount=2
Click to expand...
Click to collapse
Thanks alot alray, I'll test it and report back if I manage to fix my beloved phone. I guess I didn't see that "second generation" in post two

unbricked htc one m7
tormagj said:
Hi guys!
I've been trying to get my dear One M7 alive now for 4-5 evenings. Really thought it was bricked for good, but finally made some progress. Here's what happened:
S-OFF, rooted since always but on stock/OTA from HTC. Been updating through OTAs just flashing back stock recovery before update and then switching back. I've been using CWM. I was already on the Lollipop 5.0.2 with Sense 6.0 (sofware revision 7.19.401.2) but received another minor OTA couple of weeks ago. Didn't make note of the new revision, nor the reason for the update but just followed my usual steps. Everything seemed to go as usual, but once booting back up after the update the phone got stock on the boot animation (the htc one w/beats audio just after the sound).
Immediately tried a restore from a backup I have, but continued in the same situation. Tried several/different wipes (even the data partition in the end), but no luck. Tried the best I could to search for info, but all I could find was what I'd already done. Tried to download some RUU's but the files seems corrupted and I cannot get it working. I tried to switch to TWRP, taking a new backup (of my restored, but still not working CWM-backup). Same situation. Then I tried to flash a Cyanogenmod version, and was close to giving up when it didn't work as well. Luckily I tried a couple of times more (perhaps after throwing the phone in the wall a few times) and just out of nowhere it suddenly booted and seems to be working normally. Full of hope I tried a restore again, but back to boot animation. Tried to download a clean stock install file I found on XDA with the same version as mine, but just get stuck again. Once I restore the Cyanogenmod backup, it boots perfectly.
Perhaps I am missing something obvious, but I've been doing these things for many years know (starting with the Desire @ nikez), and this just seems odd. I could seriously need some help to get it back working again as I like the stock Sense 6.0 with Lollipop.
For info some details (btw; I verified it against the data I noted just after my original Lollipop OTA early this year, and it is still identical, so i don't see any vitals have changed):
(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.401.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: **removed**
(bootloader) imei: **removed**
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4081mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
**************************************************************************************************
hello sir,
I have htc one m7 sprint manufactured in new zealand.The problem started when I by mistake deleted all the partitions like delvin cache,system,internal
storage,etc in the factory reset option of the bootloader.My phone has unlocked bootloader and latest twrp installed before the problem occurred and android
version 4.2 installed which i think has been deleted as it says when rebooting from the bootloader and it rebooted normally just stucks at hTC logo.
I have installed fastboot,adb(not working properly) by sdk tools on windows 7 32 bit pc and also htc sync manager and latest java.
I request you to reply me as soon as possible as i have just lost my all the patience doing all the methods suggested on the like fastboot,etc and
typing the commands.You are my last hope,please help me.
Htc one bootloader details are:
*** TAMPERED ***
*** UNLOCKED ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-1.00.20.0315
OpenDSP-v26.120.274.020
eMMC-boot
May 8 2013,16:30:08:1
I have only basic knowledge of android tools and computer.
Thanks a lot for your time and i am waiting for your reply.
Click to expand...
Click to collapse

tormagj said:
Thanks alot alray, I'll test it and report back if I manage to fix my beloved phone. I guess I didn't see that "second generation" in post two
Click to expand...
Click to collapse
@alray - that freaking worked like a charm! Thanks a lot, a donation is on it's way, really thought my beloved phone was gone.
Installed the RUU version 7.19.401.22 as indicated, and that did the trick. I got an error message about HBOOT while flashing it, tried it twice since I saw it mentioned in several threads but the message continued. However, the phone booted normally afterwards so I couldn't care less right now
Code:
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
For "hboot-preupdate" response, restart the same procedure for device XXXX.
Also tried desperately to restore the data partition from my cwm backup, but then the phone wouldn't boot again. Last resort now will be to manually restore some of the apps through Titanium from my cwm - but what the heck, lost data is better than lost phone.
Although a minor update, seems like HTC did some serious changes since a lot of the normal stuff doesn't work. Any idea of what??
Anyways, thanks again - really appreciated!

rakeshrinawa said:
hello sir,
I have htc one m7 sprint manufactured in new zealand.The problem started when I by mistake deleted all the partitions like delvin cache,system,internal
storage,etc in the factory reset option of the bootloader.My phone has unlocked bootloader and latest twrp installed before the problem occurred and android
version 4.2 installed which i think has been deleted as it says when rebooting from the bootloader and it rebooted normally just stucks at hTC logo.
I have installed fastboot,adb(not working properly) by sdk tools on windows 7 32 bit pc and also htc sync manager and latest java.
I request you to reply me as soon as possible as i have just lost my all the patience doing all the methods suggested on the like fastboot,etc and
typing the commands.You are my last hope,please help me.
Htc one bootloader details are:
*** TAMPERED ***
*** UNLOCKED ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-1.00.20.0315
OpenDSP-v26.120.274.020
eMMC-boot
May 8 2013,16:30:08:1
I have only basic knowledge of android tools and computer.
Thanks a lot for your time and i am waiting for your reply.
Click to expand...
Click to collapse
Hi @rakeshrinawa,
I should probably leave it to the pro's to help you out, but I would suggest the following (sure somebody will correct me if I'm on thin ice here):
- Boot into fastboot, open a command prompt and write "fastboot getvar all". Then you'll see the same variables that I posted above, amongst other the version of your software, your CID and some other information that might be useful for the guys helping.
- Look at the selection posted by @alray here http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944 (either first or second post).
- You need to find the RUU that fits your phone (correct CID and version), and keep in mind the note in the top:
When you update you must go one step at a time. For example if you are on 6.xx.xxx.xx then you can flash 7.xx.xxx.xx . But if you are on 5.xx.xxx.xx then you cannot flash the 7.xx.xxx.xx you must first flash a 6..xx.xxx.xx.
Click to expand...
Click to collapse
- The trick is to find the right file, but I'm not the right guy to tell you which one. Once you have it, just follow the "How to flash" instructions step by step and hopefully you'll have an almost new phone again just like I had.
- I see your S-ON, so take note of the instructions saying you need to relock the bootloader (item 4 in How to flash). Or perhaps you could just as well S-OFF it ​
I am sure it's possible to solve your issue, keep on trying! Good luck!

rakeshrinawa said:
hello sir,
I have htc one m7 sprint manufactured in new zealand.The problem started when I by mistake deleted all the partitions like delvin cache,system,internal
storage,etc in the factory reset option of the bootloader.My phone has unlocked bootloader and latest twrp installed before the problem occurred and android
version 4.2 installed which i think has been deleted as it says when rebooting from the bootloader and it rebooted normally just stucks at hTC logo.
I have installed fastboot,adb(not working properly) by sdk tools on windows 7 32 bit pc and also htc sync manager and latest java.
I request you to reply me as soon as possible as i have just lost my all the patience doing all the methods suggested on the like fastboot,etc and
typing the commands.You are my last hope,please help me.
Htc one bootloader details are:
*** TAMPERED ***
*** UNLOCKED ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-1.00.20.0315
OpenDSP-v26.120.274.020
eMMC-boot
May 8 2013,16:30:08:1
I have only basic knowledge of android tools and computer.
Thanks a lot for your time and i am waiting for your reply.
Click to expand...
Click to collapse
Relock your bootloader
Code:
fastboot oem lock
and flash the old sprint ruu:
Code:
fastboot oem rebootRUU
fastboot flash zip ruu_m7_wls_jb_50_sprint_1.29.651.10.zip
fastboot flash zip ruu_m7_wls_jb_50_sprint_1.29.651.10.zip
fastboot reboot
Then you should update your phone to latest version before unlocking the bootloader, flashing a custom recovery/rom (if you are planning to)

thanks for your reply dear
@alray
Actually this is the only info my bootloader is showing as I have formatted data in the factory reset option.The model no of the phone is PN072(SPRINT) and before this problem,ANdroid 4.2 was installed and now i have installed TWRP 2.6.3.0 and again formatted data and now adb sideload is not working,kindly suggest me the correct softwares which can make my htc one m7 work and do my normal things and can u send me step by step list of softwares to be installed like twrp and adb on my pc as i have 32bit windows 7 on my pc.
Thanks a lot for your reply dear friend and you guys are just amazingly helpful.Keep it on.
---------- Post added at 02:20 AM ---------- Previous post was at 02:07 AM ----------
[/COLOR @alray
I think i have the wrong version of twrp on my phone so adb sideload is not working and i just download your files and simply flash them and will they make my phone work even when i have performed format data and by factory reset in the bootloader?

rakeshrinawa said:
@alray
Actually this is the only info my bootloader is showing as I have formatted data in the factory reset option.The model no of the phone is PN072(SPRINT) and before this problem,ANdroid 4.2 was installed and now i have installed TWRP 2.6.3.0 and again formatted data and now adb sideload is not working,kindly suggest me the correct softwares which can make my htc one m7 work and do my normal things and can u send me step by step list of softwares to be installed like twrp and adb on my pc as i have 32bit windows 7 on my pc.
Thanks a lot for your reply dear friend and you guys are just amazingly helpful.Keep it on.
Click to expand...
Click to collapse
Step you need to do posted above
RUU also posted above
you'll also need adb / fastboot either by downloading the android sdk (SDK Tools only) or minimal adb and fastboot
Save the ruu in the same folder you have installed minimal adb and fastboot or if installed the android sdk, make sure the ruu is in \Android SDK Tools\platform-tools.
Start a command prompt: Start menu --> program --> minimal adb and fastboot --> minimal adb and fastboot.exe or if using the sdk, go to \Android SDK Tools\platform-tools hold shift and right click in the folder and select "start a cmd prompt here".
Reboot your phone in bootloader / fastboot usb mode (make sure "fastboot usb" is shown in red)
then type:
Code:
fastboot oem lock
fastboot reboot-bootloader
This will relock your bootloader, required to flash the ruu
Code:
fastboot oem rebootRUU
once rebooted in ruu mode (black screnn with silver htc logo):
Code:
fastboot flash zip ruu_m7_wls_jb_50_sprint_1.29.651.10.zip
First flash will report "flush image again immediately, so do the same command again:
Code:
fastboot flash zip ruu_m7_wls_jb_50_sprint_1.29.651.10.zip
Wait for the ruu to flash then when you see sucessful message:
Code:
fastboot reboot

HI
@alray
I have HTC ONE M7 sprint variant with model no.PN072 which supports both gsm and cdma and I Was not able to use wcdma or 3g mode when using Android version 4.2.
So keeping all these things,and spending 10 hours in downloaading your files,will they work on my htc and won't create future problems like in google updates etc?
---------- Post added at 05:53 AM ---------- Previous post was at 05:14 AM ----------
[/COLOR @alray
I am sorry to say that before I read your reply,I was actually following instructions from
http://forum.xda-developers.com/showthread.php?t=2503646
and so I have flashed the firmware 5.03.651.3 s-on which is of 39886 bytes and now my new details of bootloader are:
***TAMPERED***
***RELOCKED***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-1.01.20.0515
OpenDSP-v26.120.274.0202
OS-5.03.651.3
eMMC-boot 2048MB
May 15 2014,16:31:22.1
and my fastboot getvar all details are:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 1.01.20.0515
version-cpld: None
version-microp: None
version-main: 5.03.651.3
version-misc: PVT SHIP S-ON
serialno: ***REMOVED***
imei: ***REMOVED***
meid: ***REMOVED***
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: SPCS_001
battery-status: good
battery-voltage: 4262mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
AND when I downloaded the odex file mentioned by him in the 8c step,I got the error of
remote 12:signature verify failed
and tried then,but got the same error again.
My bootloader is still relocked.
now tell me what should I do?
Hope you bear my stubbornness and Reply.....
Thanks

rakeshrinawa said:
@alray
I have HTC ONE M7 sprint variant with model no.PN072 which supports both gsm and cdma and I Was not able to use wcdma or 3g mode when using Android version 4.2.
So keeping all these things,and spending 10 hours in downloaading your files,will they work on my htc and won't create future problems like in google updates etc?
---------- Post added at 05:53 AM ---------- Previous post was at 05:14 AM ----------
[/COLOR @alray
I am sorry to say that before I read your reply,I was actually following instructions from
http://forum.xda-developers.com/showthread.php?t=2503646
and so I have flashed the firmware 5.03.651.3 s-on which is of 39886 bytes and now my new details of bootloader are:
***TAMPERED***
***RELOCKED***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-1.01.20.0515
OpenDSP-v26.120.274.0202
OS-5.03.651.3
eMMC-boot 2048MB
May 15 2014,16:31:22.1
and my fastboot getvar all details are:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 1.01.20.0515
version-cpld: None
version-microp: None
version-main: 5.03.651.3
version-misc: PVT SHIP S-ON
serialno: ***REMOVED***
imei: ***REMOVED***
meid: ***REMOVED***
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: SPCS_001
battery-status: good
battery-voltage: 4262mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
AND when I downloaded the odex file mentioned by him in the 8c step,I got the error of
remote 12:signature verify failed
and tried then,but got the same error again.
My bootloader is still relocked.
now tell me what should I do?
Hope you bear my stubbornness and Reply.....
Thanks
Click to expand...
Click to collapse
flash the 5.03.651.3 ruu posted in that thread.

hi
alray said:
flash the 5.03.651.3 ruu posted in that thread.
Click to expand...
Click to collapse
I flashed it with fastboot and it says signature verify failed,tried again and got the same message.
What should I do now,Please help me,I am totally exhausted.

rakeshrinawa said:
I flashed it with fastboot and it says signature verify failed,tried again and got the same message.
Click to expand...
Click to collapse
Its says signature verify fail because you are trying to flash a rom (stock odexed) using fastboot, you must flash this rom using a custom recovery which will require to unlock the bootloader again so the simplest is to keep your bootloader relocked and flash the RUU

hello
alray said:
Its says signature verify fail because you are trying to flash a rom (stock odexed) using fastboot, you must flash this rom using a custom recovery which will require to unlock the bootloader again so the simplest is to keep your bootloader relocked and flash the RUU
Click to expand...
Click to collapse
****
ok then can you send me the link of ruu file i have to flash as adb is not working in my phone and I can unlock my bootloader if you have a solution after that.
waiting for your reply.

rakeshrinawa said:
****
ok then can you send me the link of ruu file i have to flash
Click to expand...
Click to collapse
lol I think we have some communication issues here :laugh:. The RUU is in the same thread you linked me at post #10. All sprint RUU are listed at the beginning of that thread (in the first few lines of the OP), you need the 5.03.651.3 RUU, download it and lauch it (double click, its an .exe file). Make sure your phone is in bootloader when you launch the ruu.

Flashing different Cid RUU

Hi
Apologies in advance if this is an obvious question; I have looked through the forum but cant find a concise answer to my queries. I am coming from a HOX and my friend gave me his broken screened UK O2 branded LTE M7 as such not yet familiar with the M7. I have replaced the broken screen and fitted a new battery which was a great deal more awkward than working on the HOX!
The CId is 02_001 running HBOOT 1.61 and S-ON, I have unlocked the bootloader via HTC Dev however this is where I become unsure as to what avenues I can explore for flashing.
I'm assuming as I've now unlocked the bootloader I can flash a TWRP recovery but as I'm S-ON I can only flash unencrypted roms and as such cannot flash say the HTC Europe unbranded RUU? I want to try and stay on a stock type unbranded Sense ROM if possible rather than flashing a custom or CM based ROM until I am more familiar with the M7.
There is a plethora of info and hence I'm finding it difficult to get to grips with what ROMs would be suitable.

alangordon73 said:
Hi
Apologies in advance if this is an obvious question; I have looked through the forum but cant find a concise answer to my queries. I am coming from a HOX and my friend gave me his broken screened UK O2 branded LTE M7 as such not yet familiar with the M7. I have replaced the broken screen and fitted a new battery which was a great deal more awkward than working on the HOX!
The CId is 02_001 running HBOOT 1.61 and S-ON, I have unlocked the bootloader via HTC Dev however this is where I become unsure as to what avenues I can explore for flashing.
I'm assuming as I've now unlocked the bootloader I can flash a TWRP recovery but as I'm S-ON I can only flash unencrypted roms and as such cannot flash say the HTC Europe unbranded RUU? I want to try and stay on a stock type unbranded Sense ROM if possible rather than flashing a custom or CM based ROM until I am more familiar with the M7.
There is a plethora of info and hence I'm finding it difficult to get to grips with what ROMs would be suitable.
Click to expand...
Click to collapse
With a S-ON phone you can only flash Signed RUU that are for your phone CID, MID and version-main. You also can't flash older RUU than your version-main.
With S-OFF, you can flash Signed/Un-signed RUU of your choice (you'll have to change your CID and maybe your MID)
Flashing a stock rom (not talking about a RUU here, but a stockish unbranded custom rom) doesn't requires S-OFF, simply flash using custom recovery. ARHD 93 is a good starting point imo.

Many thanks for the reply - I am aware that the question is slightly noobish and as such I am appreciative. I'll install the suggested ROM and work from there.
Again many thanks

Unable to entery custom recovery
okay this is less than ideal... flashed every type of custom recovery to no avail but unable to boot into recovery.
Tried fastboot erase cache before and after flashing recoveries.
When selecting recovery 'entering recovery' appears at the top of the screen, after a few seconds the screen goes black for a second or so then back to the 'entering recovery' which never actually happens - Its like it hangs on loading the recovery.
Result of fastboot allvars query:
(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.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3C6W904988
(bootloader) imei: xxxxxxxxxxxxxxxxx
(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: 4047mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-868a9c98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Does anyone have any ideas?
This phone/brick is vexing to say the least!

alangordon73 said:
okay this is less than ideal... flashed every type of custom recovery to no avail but unable to boot into recovery.
Tried fastboot erase cache before and after flashing recoveries.
When selecting recovery 'entering recovery' appears at the top of the screen, after a few seconds the screen goes black for a second or so then back to the 'entering recovery' which never actually happens - Its like it hangs on loading the recovery.
Result of fastboot allvars query:
(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.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3C6W904988
(bootloader) imei: xxxxxxxxxxxxxxxxx
(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: 4047mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-868a9c98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Does anyone have any ideas?
This phone/brick is vexing to say the least!
Click to expand...
Click to collapse
Flash mdmower's twrp recovery
http://android.cmphys.com/twrp-m7/

Right it seems I've managed to make a mess of this - I've foolishly relocked the booloader on a custom recovery and now I can't get it unlocked again - It reboots to recovery and just hangs and wont unlock the bootloader.
I've tried using the rom.zip from the RUU and flashing it in fastboot to which it reports it cannot allocate the space in bytes.
I've tried running the RUU which fails at checking headers on step 1/5
RUU I'm trying to use is RUU_M7_UL_K44_SENSE55_MR_O2_UK_4.20.206.16_Radio_4A.23.3263.28_10.38r.1157.04L_release_353143_signed_2
Is the recovery partition perhaps corrupt as I'm getting absolutely nowhere with this paperweight?
I'm now at a loss and most peeved!

alangordon73 said:
Right it seems I've managed to make a mess of this - I've foolishly relocked the booloader on a custom recovery and now I can't get it unlocked again - It reboots to recovery and just hangs and wont unlock the bootloader.
I've tried using the rom.zip from the RUU and flashing it in fastboot to which it reports it cannot allocate the space in bytes.
I've tried running the RUU which fails at checking headers on step 1/5
RUU I'm trying to use is RUU_M7_UL_K44_SENSE55_MR_O2_UK_4.20.206.16_Radio_4A.23.3263.28_10.38r.1157.04L_release_353143_signed_2
Is the recovery partition perhaps corrupt as I'm getting absolutely nowhere with this paperweight?
I'm now at a loss and most peeved!
Click to expand...
Click to collapse
You can't flash a RUU version that is older than your actual version-main when the phone is S-ON. To unlock a bootloader that was relocked with a custom recovery installed, you either need to reflash a signed(official) firmware or a ruu since this is the only thing that the phone will accept in this state (locked and s-on).
Unfortunately i can't find any 7.18.206.51 firmware so you'll have to reflash the whole phone using the 7.18.206.51 RUU which will reset everything back to stock and wipe your files.
https://www.androidfilehost.com/?fid=24352994023702662
Code:
fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_O2_UK_7.18.206.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_459056_signed.zip
fastboot reboot-bootloader
than you'll be able to unlock again.
Don't forget to use htc_fastboot.exe for the flash zip command (not the regular fastboot.exe). A quick search on androidfilehost.com for "htc_fastboot" and you'll be able to download it if you don't have it already.

Outstanding... Flashed back and unlocked the boot loader. Spent enough time and frustration this week so early night and will try flash a recovery and ArHD tomorrow.
Can't thank you enough

Grrrr... Flashed the recovery suggested above and the phone just does not want to go into recovery.
I've tried:
Powering down from Android and then going into Bootloader just stops on Entering Recovery.
Power down, entering bootloader then reseting the phone - again stops on Enterng Recovery.
Power down from Android, power back up, master reset - again just stops on entering recovery.
screams...

alangordon73 said:
Grrrr... Flashed the recovery suggested above and the phone just does not want to go into recovery.
I've tried:
Powering down from Android and then going into Bootloader just stops on Entering Recovery.
Power down, entering bootloader then reseting the phone - again stops on Enterng Recovery.
Power down from Android, power back up, master reset - again just stops on entering recovery.
screams...
Click to expand...
Click to collapse
Did you tried the old TWRP 2.6.3.3 version? Ive seen a lot of pple only being able to use this version when newer ones will cause the exact problem you are experiencing. Might worth a try.

Solved! TWRP 2.6.3.3 works.

alray said:
With a S-ON phone you can only flash Signed RUU that are for your phone CID, MID and version-main. You also can't flash older RUU than your version-main.
With S-OFF, you can flash Signed/Un-signed RUU of your choice (you'll have to change your CID and maybe your MID)
Flashing a stock rom (not talking about a RUU here, but a stockish unbranded custom rom) doesn't requires S-OFF, simply flash using custom recovery. ARHD 93 is a good starting point imo.
Click to expand...
Click to collapse
Then I can flash any Ruu I want if I change Cid and Mid to match Ruu with S-off? Even if it's from 4.3 to kit Kat or Lollipop?
Thanks and sorry for hijacking the thread.
Enviado desde mi Nexus 5 mediante Tapatalk

JabboMaster said:
Then I can flash any Ruu I want if I change Cid and Mid to match Ruu with S-off? Even if it's from 4.3 to kit Kat or Lollipop?
Thanks and sorry for hijacking the thread.
Enviado desde mi Nexus 5 mediante Tapatalk
Click to expand...
Click to collapse
not exactly,it depend what phone variant you have. If its a M7_UL or M7_U then you can flash any M7_UL or M7_U RUU youd like by changing the CID and MID. If you want to flash a lollipop RUU you need to have at least hboot 1.57 with a 6.xx.xxx.x firmware already installed on the phone. Firmware can easily be updated if needed when s-off.

alray said:
not exactly,it depend what phone variant you have. If its a M7_UL or M7_U then you can flash any M7_UL or M7_U RUU youd like by changing the CID and MID. If you want to flash a lollipop RUU you need to have at least hboot 1.57 with a 6.xx.xxx.x firmware already installed on the phone. Firmware can easily be updated if needed when s-off.
Click to expand...
Click to collapse
Ok, thanks.
Gonna try flashing first a Kitkat Ruu and then updating via Ota to Lollipop.
Enviado desde mi Nexus 5 mediante Tapatalk