Database Develop

[Q] Followed steps to take my HTC One back to Stock.... :(

:crying::crying:
And the steps have ruined my phone. I can still use the phone, but I can no longer access TWRP. I can get in to the bootloader, and select "Recovery", but it just reboots the bootloader. I'm not getting anywhere trying to flash the stock boot image. I keep getting file signature errors. adb is worthless, it never has recognized any device I've every tried to use with it. ANd yes, I've tried it on multiple computer's running multiple OS's with multiple phones. I'm not a dev, so it sucks....period.
Now, again, I cannot even revert my phone back to it's factory condition. I relocked the bootloader as I was following the tutorials from MANY different high level forum posters. I cannot unlock the bootloader again which is going to make flashing TWRP again impossible. I don't know what to do. I was doing this because when that OTA update came about I had accidentally told it to install. Well, it couldn't, it would go straight to TWRP and fail immediately. But when that happened a couple of days ago my friends and colleagues have only been able to receive the last part of any SMS message I send. The first two parts disappear.
This is what I get running "fastboot getvar all"....obviously. Lol!
C:\adt-bundle-windows-x86_64-20130917\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0626
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA34BS901308
(bootloader) imei: 990001465704088
(bootloader) meid: 99000146570408
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4197mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.194s
Click to expand...
Click to collapse
Anyway, the devs here are the best and I know here is a way to get my phone back to proper working order again. As far as I can tell, without being able to unlock the bootloader, I'll never be able to flash another custom recovery therefore I will never be able to restore from a NANDROID.
I don't want to sound like every n00b or whatever who comes to these forums but I need some serious help. My requests for help in the forum threads have largely gone unanswered. So until someone on here has the time to help me I'm screwed. I mean damn, maybe I'll just sell the phone and get one of the 64GB models. I don't know what I'm going to do.
I need serious help until then... I've got to recovery my bootloader and must "re-unlock" my bootloader. If I could do that I'm pretty sure I could flash TWRP again and restore from one of my NANDROIDS. But until then... Well, all I can do is beg for someone who knows more than I do about this device to help me. I would be forever grateful.
Please, any advice, techniques, snippets of code, adb commands (if it will recognize my device), fastboot commands (fastboot always recognizes my device) or anything to get my phone back to normal, working order.
I mean I don't give a damn about root access, custom ROM's or Kernel's any longer. I just want my phone back that I paid so very much for and waited for weeks and possibly months on the waiting list just so I could pre-order.
If it's ruined then there's not much I can do about that. But it isn't bricked and I can still use the phone for the most part. But the bootloader is what has been destroyed basically.
Help, help, help!!!! :crying:

PAinguINx said:
:crying::crying:
And the steps have ruined my phone. I can still use the phone, but I can no longer access TWRP. I can get in to the bootloader, and select "Recovery", but it just reboots the bootloader. I'm not getting anywhere trying to flash the stock boot image. I keep getting file signature errors. adb is worthless, it never has recognized any device I've every tried to use with it. ANd yes, I've tried it on multiple computer's running multiple OS's with multiple phones. I'm not a dev, so it sucks....period.
Now, again, I cannot even revert my phone back to it's factory condition. I relocked the bootloader as I was following the tutorials from MANY different high level forum posters. I cannot unlock the bootloader again which is going to make flashing TWRP again impossible. I don't know what to do. I was doing this because when that OTA update came about I had accidentally told it to install. Well, it couldn't, it would go straight to TWRP and fail immediately. But when that happened a couple of days ago my friends and colleagues have only been able to receive the last part of any SMS message I send. The first two parts disappear.
This is what I get running "fastboot getvar all"....obviously. Lol!
Anyway, the devs here are the best and I know here is a way to get my phone back to proper working order again. As far as I can tell, without being able to unlock the bootloader, I'll never be able to flash another custom recovery therefore I will never be able to restore from a NANDROID.
I don't want to sound like every n00b or whatever who comes to these forums but I need some serious help. My requests for help in the forum threads have largely gone unanswered. So until someone on here has the time to help me I'm screwed. I mean damn, maybe I'll just sell the phone and get one of the 64GB models. I don't know what I'm going to do.
I need serious help until then... I've got to recovery my bootloader and must "re-unlock" my bootloader. If I could do that I'm pretty sure I could flash TWRP again and restore from one of my NANDROIDS. But until then... Well, all I can do is beg for someone who knows more than I do about this device to help me. I would be forever grateful.
Please, any advice, techniques, snippets of code, adb commands (if it will recognize my device), fastboot commands (fastboot always recognizes my device) or anything to get my phone back to normal, working order.
I mean I don't give a damn about root access, custom ROM's or Kernel's any longer. I just want my phone back that I paid so very much for and waited for weeks and possibly months on the waiting list just so I could pre-order.
If it's ruined then there's not much I can do about that. But it isn't bricked and I can still use the phone for the most part. But the bootloader is what has been destroyed basically.
Help, help, help!!!! :crying:
Click to expand...
Click to collapse
so basically if i understood you, you want to unlock bootloader and flash customer recovery twrp
first go to htcdev to do the unlocking of your bootloader then after that you will be able to flash twrp
adb do not run if your One is on fastboot mode
adb will recognize your device only on recovery or open rom
---------- Post added at 05:32 PM ---------- Previous post was at 05:27 PM ----------
and also, after successfully doing the flashing
try to do s-off before you return to stock and update to 4.3

PAinguINx said:
:crying::crying:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
Help, help, help!!!! :crying:
Click to expand...
Click to collapse
Hey, careful there!!! You have a SPRINT variant, this forum is mostly for GSM version of the HTC One (M7_U and M7_UL). Head over to the Sprint HTC One forum, I'm sure someone will help you out.
http://forum.xda-developers.com/sprint-htc-one

nkk71 said:
Hey, careful there!!! You have a SPRINT variant, this forum is mostly for GSM version of the HTC One (M7_U and M7_UL). Head over to the Sprint HTC One forum, I'm sure someone will help you out.
http://forum.xda-developers.com/sprint-htc-one
Click to expand...
Click to collapse
Uh oh, I've wandered in to strange territory here. Lol!
I'll head over to the other forums.
I have made some progress though. I've unlocked the bootloader once again. TWRP is still in tact, thus indicating the structural integrity of my partition table remains stable and consistent with what it should be after I rooted my device.
Thank you guys for responding. I still need to return to stock. My main issue is that when I send texts messages only 1/x are being received. Usually the last part of a long message will be received.
Quick question though, why are their such significant differences between the Sprint M7 and AT&T's or any other carriers?

[email protected] said:
so basically if i understood you, you want to unlock bootloader and flash customer recovery twrp
first go to htcdev to do the unlocking of your bootloader then after that you will be able to flash twrp
adb do not run if your One is on fastboot mode
adb will recognize your device only on recovery or open rom
---------- Post added at 05:32 PM ---------- Previous post was at 05:27 PM ----------
and also, after successfully doing the flashing
try to do s-off before you return to stock and update to 4.3
Click to expand...
Click to collapse
So I need to S-Off before going back to stock. I'm assuming that I will be unable to do so after flashing? I tried pushing revone earlier yesterday but I had no luck. Also, why has the HTC One AIO tool from Samsoon been removed? Not only has it been removed, but I cannot find any "legit" downloads on the internet for it either...
Thanks!

Help with Sim-Unlock

Hi all,
I have the revolution HD Rom installed on my device and I got an unlock code online from a site I trust and bought from in the past (I say that to point out that I don't think that the problem is with the key itself)
When I tried to apply it though, it said that it is wrong...
I know it sounds weird, but my research shows that it might be related to me having a custom rom installed - something about changing the baseband?
Either way, I'd love for some community help on this - is this possible?
If so, what is the quickest/painless way to get back to stock? will that require a full factory reset?
will I lose the unlock again when I switch back to the rom?
Please help as I'm currently out of the country and have no phone
Thanks!!!

eladkatz said:
Hi all,
I have the revolution HD Rom installed on my device and I got an unlock code online from a site I trust and bought from in the past (I say that to point out that I don't think that the problem is with the key itself)
When I tried to apply it though, it said that it is wrong...
I know it sounds weird, but my research shows that it might be related to me having a custom rom installed - something about changing the baseband?
Either way, I'd love for some community help on this - is this possible?
If so, what is the quickest/painless way to get back to stock? will that require a full factory reset?
will I lose the unlock again when I switch back to the rom?
Please help as I'm currently out of the country and have no phone
Thanks!!!
Click to expand...
Click to collapse
You can either restore a nandroid of your stock ROM or flash an RUU. Try your code again after going to stock and it'll work.

eladkatz said:
Hi all,
I have the revolution HD Rom installed on my device and I got an unlock code online from a site I trust and bought from in the past (I say that to point out that I don't think that the problem is with the key itself)
When I tried to apply it though, it said that it is wrong...
I know it sounds weird, but my research shows that it might be related to me having a custom rom installed - something about changing the baseband?
Either way, I'd love for some community help on this - is this possible?
If so, what is the quickest/painless way to get back to stock? will that require a full factory reset?
will I lose the unlock again when I switch back to the rom?
Please help as I'm currently out of the country and have no phone
Thanks!!!
Click to expand...
Click to collapse
You posted in the wrong section. That's what Q&A is for.
Sent from my HTC One using XDA Premium 4 mobile app

gamer765 said:
You can either restore a nandroid of your stock ROM or flash an RUU. Try your code again after going to stock and it'll work.
Click to expand...
Click to collapse
Thanks for the reply man, I was going to follow the instructions on http://forum.xda-developers.com/showthread.php?t=2265618 but they link to more info on RUUs and the link is broken
How do I know which ruu do I need?
Thanks again!

eladkatz said:
Thanks for the reply man, I was going to follow the instructions on http://forum.xda-developers.com/showthread.php?t=2265618 but they link to more info on RUUs and the link is broken
How do I know which ruu do I need?
Thanks again!
Click to expand...
Click to collapse
What region is the phone from and what carrier? It's probably better if you can post your CID, which you can obtain by using the CID Getter app on the play store.

gamer765 said:
What region is the phone from and what carrier? It's probably better if you can post your CID, which you can obtain by using the CID Getter app on the play store.
Click to expand...
Click to collapse
I have a US AT&T phone, my CID is CWS_001
Thanks

eladkatz said:
I have a US AT&T phone, my CID is CWS_001
Thanks
Click to expand...
Click to collapse
You don't need to do all that, just use a Guru Reset ROM for your firmware, that will work (confirmed from several other users, with the same situation as yours). can you post a "fastboot getvar all" (remove IMEI and s/n) and I'll point you in the right direction

eladkatz said:
I have a US AT&T phone, my CID is CWS_001
Thanks
Click to expand...
Click to collapse
Just restore a stock AT&T nandroid and you should be good to go. Afterwards, you can install custom ROMs, your unlock will stick.
EDIT: You can restore this nandroid http://www.htc1guru.com/dld/htcone-32gb-att-1-26-502-10-twrp-stock-zip/
Make a nandroid of your current ROM first if you want to return to it afterwards. The above is a TWRP nandroid.

nkk71 said:
You don't need to do all that, just use a Guru Reset ROM for your firmware, that will work (confirmed from several other users, with the same situation as yours). can you post a "fastboot getvar all" (remove IMEI and s/n) and I'll point you in the right direction
Click to expand...
Click to collapse
Thanks, see below, not sure if it worked...
(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.26.502.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REDACTED
(bootloader) imei: REDACTED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4082mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
finished. total time: 0.041s

eladkatz said:
Thanks, see below, not sure if it worked...
(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.26.502.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REDACTED
(bootloader) imei: REDACTED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4082mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
finished. total time: 0.041s
Click to expand...
Click to collapse
Try this one: http://www.htc1guru.com/dld/guru_reset_m7_1-26-502-12-zip/
It's slightly newer than your version but I think it should work, you can deselect "stock recovery" and "stock radio" during the install, as you won't need those.
BTW: why don't you S-Off? (just a question, I'm in no way implying you do anything you're not comfortable with!!)

gamer765 said:
Just restore a stock AT&T nandroid and you should be good to go. Afterwards, you can install custom ROMs, your unlock will stick.
EDIT: You can restore this nandroid http://www.htc1guru.com/dld/htcone-32gb-att-1-26-502-10-twrp-stock-zip/
Make a nandroid of your current ROM first if you want to return to it afterwards. The above is a TWRP nandroid.
Click to expand...
Click to collapse
I have clockwork mod recovery, can I use that to do the twrp nandroid recovery?
Also, in the url you are directing to, it says:
This Nandroid should not be needed. I have
a Stock ROM + Recovery Reset Installer which can
reset stock ROM and allow OTA updates. See Here:
http://www.htc1guru.com/dld/guru_reset_m7_1-26-502-12-zip
Click to expand...
Click to collapse
Should I use that one instead?

eladkatz said:
I have clockwork mod recovery, can I use that to do the twrp nandroid recovery?
Also, in the url you are directing to, it says:
Should I use that one instead?
Click to expand...
Click to collapse
Sorry, I didn't get your question, and lots of different approaches to the same thing. If you want my opinion:
1- do a nandroid backup of your current setup
2- copy (or pull) everything to your PC, just in case
3- use the Guru Reset (http://www.htc1guru.com/dld/guru_reset_m7_1-26-502-12-zip/), that's a flashable zip in custom recovery, do not select "stock recovery" (actually you have to uncheck it)
4- do not take any OTAs
5- use your SIM unlock code
6- restore your nandroid backup
if in step 5 the SIM unlock code doesn't work, then you can explore other options
That's my humble opinion.
Hit the Thanks button if I've helped

nkk71 said:
BTW: why don't you S-Off? (just a question, I'm in no way implying you do anything you're not comfortable with!!)
Click to expand...
Click to collapse
I guess because I'm not sure what that is, I've seen it mentioned as something that allowes to install custom RUUs but I'm not sure how that would help here...

eladkatz said:
I guess because I'm not sure what that is, I've seen it mentioned as something that allowes to install custom RUUs but I'm not sure how that would help here...
Click to expand...
Click to collapse
I guess the stock reset is fine, the main goal is to get you back to the stock carrier ROM for the unlock code to work.

nkk71 said:
Sorry, I didn't get your question, and lots of different approaches to the same thing. If you want my opinion:
1- do a nandroid backup of your current setup
2- copy (or pull) everything to your PC, just in case
3- use the Guru Reset (http://www.htc1guru.com/dld/guru_reset_m7_1-26-502-12-zip/), that's a flashable zip in custom recovery, do not select "stock recovery" (actually you have to uncheck it)
4- do not take any OTAs
5- use your SIM unlock code
6- restore your nandroid backup
if in step 5 the SIM unlock code doesn't work, then you can explore other options
That's my humble opinion.
Hit the Thanks button if I've helped
Click to expand...
Click to collapse
Thanks for the tip,
I followed the instructions to the letter and now it seems like I'm stuck on the HTC ONE boot screen...
I tried restarting once (after letting it idle for a good 10 minutes I think)
now I'm just staring at it, not really sure what my next step should be... could it just be that I need to wait?
On a positive note, I can still access fastboot/recovery so I guess worst case, I can do a factory reset - that oughta fix it, right?
Question about that - if I do that, will I still be able to do the nandroid restore and go back to my original state?
Thanks

eladkatz said:
Thanks for the tip,
I followed the instructions to the letter and now it seems like I'm stuck on the HTC ONE boot screen...
I tried restarting once (after letting it idle for a good 10 minutes I think)
now I'm just staring at it, not really sure what my next step should be... could it just be that I need to wait?
Click to expand...
Click to collapse
What's up with that, 2nd person today (out of 2) having problems with the Guru Resets
did you wipe in the Installer? did you make sure the download is not corrupt (MD5 sum)?
The way I usually know if the bootup is stuck or not, is: after a few minutes (something like 2 or 3 minutes, maybe less) the screen will change brightness, if it does I know it's not stuck, if the brightness doesn't change, I force a reboot and reflash.
I recommend you reboot to recovery, and restore your backup, just to have a functioning phone, then check the MD5 sum of your download to make sure it's OK.
I'm about to flash the Guru Reset that also got the other guy "stuck", to see if it works or not....

eladkatz said:
Thanks for the tip,
I followed the instructions to the letter and now it seems like I'm stuck on the HTC ONE boot screen...
I tried restarting once (after letting it idle for a good 10 minutes I think)
now I'm just staring at it, not really sure what my next step should be... could it just be that I need to wait?
On a positive note, I can still access fastboot/recovery so I guess worst case, I can do a factory reset - that oughta fix it, right?
Question about that - if I do that, will I still be able to do the nandroid restore and go back to my original state?
Thanks
Click to expand...
Click to collapse
FYI: http://forum.xda-developers.com/showpost.php?p=47085377&postcount=44
(it's a different Guru Reset, but same principle applies)

nkk71 said:
FYI: http://forum.xda-developers.com/showpost.php?p=47085377&postcount=44
(it's a different Guru Reset, but same principle applies)
Click to expand...
Click to collapse
I eventually just restored to factory defaults, proceeded to unlock and then went back to the nandroid backup, worked like a charm!
Thanks for all the help and support

HTC ONE M7 Google Play Conversion

Hey all,
I have looked and i seriously can't find anything, Maybe i didn't look hard enough??
But anyway i was wondering is there a way i can fully convert my HTC ONE M7 to the google play edition jus tlike you can with the M8?
And receive OTA as well?
If this is possible could someone please link me to the thread? Thanks will be awarded!!!
Thank you!

Gizzy666 said:
Hey all,
I have looked and i seriously can't find anything, Maybe i didn't look hard enough??
But anyway i was wondering is there a way i can fully convert my HTC ONE M7 to the google play edition jus tlike you can with the M8?
And receive OTA as well?
If this is possible could someone please link me to the thread? Thanks will be awarded!!!
Thank you!
Click to expand...
Click to collapse
Read again.. In the development thread

Understand that everything you do is at your own risk and none of these modifications are guaranteed to work by their authors. This will wipe all of the contents of your phone, so consider backing up any files that aren't on cloud storage.
You will need to do the following in this order:
1.) Unlock your device's bootloader, either through http://www.htcdev.com or by other means. If you are on HBOOT 1.44 or earlier (unlikely,) you can do this "off the grid." For convenience's sake, you can safely unlock your bootloader via the aforementioned website, but it may have implications on your warranty.
2.) Install a custom recovery of your choice (CWM or TWRP) and obtain root on your device.
3.) Create a backup of your current OS in the event that anything goes wrong. Immediately transfer this backup to your PC/Mac storage.
(These three steps are detailed here.)
4.) S-OFF (security off) your device via Firewater, see here.
5.) Download either the pre-rooted or non-rooted 4.4.2 Google Play Edition RUU from here, and be sure your MID and CID (ex. PN07140, T-MOB010) are listed and supported before continuing. (RUU is short for ROM Upgrade Utility; think of the file as an OS install DVD that you will be putting into your phone, much like you would a freshly formatted computer.)
6.) If your bootloader is unlocked, custom recovery is installed, rooted, backup created, S-OFF, Google Play Edition RUU is downloaded, and you are successfully connected to your phone via adb, continue with the installation steps in the last linked thread exactly as they are listed, beginning with "adb reboot bootloader". Again a reminder that this will wipe your phone's storage and, once rebooted, will be running the Google Play Edition OS.

Thank you, for giving me an actual reply. I would have been just happy with a link. You've done more than that I've hit the thanks button.
ericiidx said:
Understand that everything you do is at your own risk and none of these modifications are guaranteed to work by their authors. This will wipe all of the contents of your phone, so consider backing up any files that aren't on cloud storage.
You will need to do the following in this order:
1.) Unlock your device's bootloader, either through http://www.htcdev.com or by other means. If you are on HBOOT 1.44 or earlier (unlikely,) you can do this "off the grid." For convenience's sake, you can safely unlock your bootloader via the aforementioned website, but it may have implications on your warranty.
2.) Install a custom recovery of your choice (CWM or TWRP) and obtain root on your device.
3.) Create a backup of your current OS in the event that anything goes wrong. Immediately transfer this backup to your PC/Mac storage.
(These three steps are detailed here.)
4.) S-OFF (security off) your device via Firewater, see here.
5.) Download either the pre-rooted or non-rooted 4.4.2 Google Play Edition RUU from here, and be sure your MID and CID (ex. PN07140, T-MOB010) are listed and supported before continuing. (RUU is short for ROM Upgrade Utility; think of the file as an OS install DVD that you will be putting into your phone, much like you would a freshly formatted computer.)
6.) If your bootloader is unlocked, custom recovery is installed, rooted, backup created, S-OFF, Google Play Edition RUU is downloaded, and you are successfully connected to your phone via adb, continue with the installation steps in the last linked thread exactly as they are listed, beginning with "adb reboot bootloader". Again a reminder that this will wipe your phone's storage and, once rebooted, will be running the Google Play Edition OS.
Click to expand...
Click to collapse

I'm excited
ericiidx said:
Understand that everything you do is at your own risk and none of these modifications are guaranteed to work by their authors. This will wipe all of the contents of your phone, so consider backing up any files that aren't on cloud storage.
You will need to do the following in this order:
1.) Unlock your device's bootloader, either through http://www.htcdev.com or by other means. If you are on HBOOT 1.44 or earlier (unlikely,) you can do this "off the grid." For convenience's sake, you can safely unlock your bootloader via the aforementioned website, but it may have implications on your warranty.
2.) Install a custom recovery of your choice (CWM or TWRP) and obtain root on your device.
3.) Create a backup of your current OS in the event that anything goes wrong. Immediately transfer this backup to your PC/Mac storage.
(These three steps are detailed here.)
4.) S-OFF (security off) your device via Firewater, see here.
5.) Download either the pre-rooted or non-rooted 4.4.2 Google Play Edition RUU from here, and be sure your MID and CID (ex. PN07140, T-MOB010) are listed and supported before continuing. (RUU is short for ROM Upgrade Utility; think of the file as an OS install DVD that you will be putting into your phone, much like you would a freshly formatted computer.)
6.) If your bootloader is unlocked, custom recovery is installed, rooted, backup created, S-OFF, Google Play Edition RUU is downloaded, and you are successfully connected to your phone via adb, continue with the installation steps in the last linked thread exactly as they are listed, beginning with "adb reboot bootloader". Again a reminder that this will wipe your phone's storage and, once rebooted, will be running the Google Play Edition OS.
Click to expand...
Click to collapse
Hello Eric, and hello fellow HTC One users. Up until now I was frustrated with my old android (stupid Micromax) running on 4.2.1. I can't think of a single night when I didn't sleep praying for an update. From inside I knew that was never happening, but I was hopeful. And today, I just received two of my friends from home (that feeling when you receive someone from your home country after being by yourself for 5 months) and turns out my sweet elder brother had sent a little surprise for me with them. It was an AT&T HTC One M7. I know some of you must be more excited for the upcoming M9 just like me, but I can't imagine myself being happier. I know its almost 2 years old, but its here, its mine and I love it.
And I know perhaps your this response is suppose to be elaborate enough already, I'm really scared that I would go wrong. And I wouldn't be able to forgive myself if such a thing did happen. I'm very new to the whole adb thing, I'll be frank. But I'm crazy enough about stock android to know that I want that over any OEM skin (Touchwiz, Sense) without offence to anyone who likes them. It would mean a lot to me if you could help me convert this AT&T HTC One M7 to the GPE version. If you (or anyone else) can spare a little of your valuable time and help me, please PM me. I wouldn't want to disturb everyone by adding unnecessary posts after posts on the thread. Excitingly awaiting a response as I sleep tonight not praying but thanking cause someone's up there definitely listening to you!

deepesh_p said:
Hello Eric, and hello fellow HTC One users. Up until now I was frustrated with my old android (stupid Micromax) running on 4.2.1. I can't think of a single night when I didn't sleep praying for an update. From inside I knew that was never happening, but I was hopeful. And today, I just received two of my friends from home (that feeling when you receive someone from your home country after being by yourself for 5 months) and turns out my sweet elder brother had sent a little surprise for me with them. It was an AT&T HTC One M7. I know some of you must be more excited for the upcoming M9 just like me, but I can't imagine myself being happier. I know its almost 2 years old, but its here, its mine and I love it.
And I know perhaps your this response is suppose to be elaborate enough already, I'm really scared that I would go wrong. And I wouldn't be able to forgive myself if such a thing did happen. I'm very new to the whole adb thing, I'll be frank. But I'm crazy enough about stock android to know that I want that over any OEM skin (Touchwiz, Sense) without offence to anyone who likes them. It would mean a lot to me if you could help me convert this AT&T HTC One M7 to the GPE version. If you (or anyone else) can spare a little of your valuable time and help me, please PM me. I wouldn't want to disturb everyone by adding unnecessary posts after posts on the thread. Excitingly awaiting a response as I sleep tonight not praying but thanking cause someone's up there definitely listening to you!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2358781

Intimidating
alray said:
http://forum.xda-developers.com/showthread.php?t=2358781
Click to expand...
Click to collapse
Hello @alray thanks for the response. and for the link. I went through the post and every bit of it came to me as intimidating. Again no offence, but it did sound like the OP was frustrated with helping people like me (noobs as he would refer) which is exactly what I said about myself. Yes, I don't know much about ADB and the process of conversion to GPE seems quite different from the one I had to go through about 2 years ago when someone just like you was kind enough to extend help in installing Omnirom on my Original Note. I am a noob and hence I want help. If I wasn't, I wouldn't have asked for it in the first place. As much as I would want to post their and mention your name, it didn't sound like a very inviting place. Thanks for the help, I can understand if you wouldn't want to help here. I guess, as he blatantly puts, I'll have to figure it out myself if I want to convert or just continue to be a noob who has to settle for whatever the company offers through OTA. Thanks again. I shall try on my own

Go step by step and ask your questions here we will help you. Is your phone s-off? You'll need s-off to change your CID and maybe also your MID. Post the output of "fastboot getvar all" so we can tell you what you need exactly to convert it.

alray said:
Go step by step and ask your questions here we will help you. Is your phone s-off? You'll need s-off to change your CID and maybe also your MID. Post the output of "fastboot getvar all" so we can tell you what you need exactly to convert it.
Click to expand...
Click to collapse
Thanks @alray. I tried using these instructions today and before starting I had to to stop cause the instructions were for a MAC. I am on Windows 8.1. And no I don't have anything on this phone. It's new and I am on the screen where it would generally ask for the first start up. I have so far disabled fastboot from the battery Manager and enabled USB Debugging after unlocking the developers options. I was about to follow the instructions then and the video and the written tutorial says MAC. Now what?
P.S. - I have also downloaded the HTC sync software so that the latest drivers are installed and then I uninstalled the sync software so that I'm left with only the drivers and the sync software wont interfere in the steps to come (as I saw and read in one of the posts too).

deepesh_p said:
Thanks @alray. I tried using these instructions today and before starting I had to to stop cause the instructions were for a MAC. I am on Windows 8.1. And no I don't have anything on this phone. It's new and I am on the screen where it would generally ask for the first start up. I have so far disabled fastboot from the battery Manager and enabled USB Debugging after unlocking the developers options. I was about to follow the instructions then and the video and the written tutorial says MAC. Now what?
P.S. - I have also downloaded the HTC sync software so that the latest drivers are installed and then I uninstalled the sync software so that I'm left with only the drivers and the sync software wont interfere in the steps to come (as I saw and read in one of the posts too).
Click to expand...
Click to collapse
install minimal adb and fastboot, then the latest htc drivers.
open minimal adb and fastboot, connect your phone to your computer.
reboot your phone in bootloader mode/fastboot usb (hold power and volume down until the phone is rebooted in bootloader)
in the minimal adb and fastboot command prompt, enter this command:
Code:
fastboot getvar all
copy paste the output here (remove imei and serialno before posting)

output
alray said:
install minimal adb and fastboot, then the latest htc drivers.
open minimal adb and fastboot, connect your phone to your computer.
reboot your phone in bootloader mode/fastboot usb (hold power and volume down until the phone is rebooted in bootloader)
in the minimal adb and fastboot command prompt, enter this command:
Code:
fastboot getvar all
copy paste the output here (remove imei and serialno before posting)
Click to expand...
Click to collapse
Hi @alray
This is the output-
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Minimal ADB and Fastboot>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *removed*
(bootloader) imei: *removed*
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4260mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.204s
Thanks again

deepesh_p said:
Hi alray
This is the output-
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Minimal ADB and Fastboot>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *removed*
(bootloader) imei: *removed*
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4260mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.204s
Thanks again
Click to expand...
Click to collapse
Ok so first step is to achieve s-off using sunshine. You can get sunshine at http://theroot.ninja
Sunshine cost 25$ and there is no alternative to s-off hboot 1.57

What about moonshine?
alray said:
Ok so first step is to achieve s-off using sunshine. You can get sunshine at http://theroot.ninja
Sunshine cost 25$ and there is no alternative to s-off hboot 1.57
Click to expand...
Click to collapse
Hi @alray, thanks for replying. I was seeing the videos which I was led to from those links you had sent and there was something called the moonshine in one of the videos. Is it different? That too i guess was on 4.4.2 just like my phone.
P.S.- will htc dev website not work to unlock the bootloader?

deepesh_p said:
Hi @alray, thanks for replying. I was seeing the videos which I was led to from those links you had sent and there was something called the moonshine in one of the videos. Is it different?
Click to expand...
Click to collapse
Moonshine is for hboot 1.44.
So again, the only way to achieve s-off on hboot 1.57 is Sunshine s-off and cost 25$
Btw im not affiliated with them, im not trying to make money on you.
P.S.- will htc dev website not work to unlock the bootloader?
Click to expand...
Click to collapse
Yes but you also need s-off = you'll need sunshine anyway so better to use sunshine to unlock and s-off at the same time.

Downloading Sunshine
alray said:
Moonshine is for hboot 1.44.
So again, the only way to achieve s-off on hboot 1.57 is Sunshine s-off and cost 25$
Btw im not affiliated with them, im not trying to make money on you.
Yes but you also need s-off = you'll need sunshine anyway so better to use sunshine to unlock and s-off at the same time.
Click to expand...
Click to collapse
Hey @alray, sorry I didn't not mean to imply that you were making money on me. I did read about how HTC has tried to prevent devices from getting s-off. I'm downloadng the apk now. Will get back to you soon.

deepesh_p said:
Hey @alray, sorry I didn't not mean to imply that you were making money on me. I did read about how HTC has tried to prevent devices from getting s-off. I'm downloadng the apk now. Will get back to you soon.
Click to expand...
Click to collapse
Hi again @alray, as you can see (attachment) the apk just isn't downloading. It got cancelled 3 times already and now its stuck at 0.3 mbs downloaded. It was showing 2 hours left before that. Any other mirror that I could use?
Edit : Have been trying again and again. No luck

deepesh_p said:
Hi again @alray, as you can see (attachment) the apk just isn't downloading. It got cancelled 3 times already and now its stuck at 0.3 mbs downloaded. It was showing 2 hours left before that. Any other mirror that I could use?
Click to expand...
Click to collapse
You probably have a bad internet connection, it took me 8 seconds to download it from sunshine website .
https://www.androidfilehost.com/?fid=95916177934536294

No luck with androidfilehost too
alray said:
You probably have a bad internet connection, it took me 8 seconds to download it from sunshine website .
https://www.androidfilehost.com/?fid=95916177934536294
Click to expand...
Click to collapse
This also doesn't seem to work. Tried the main download link as well as a France Mirror thinking it might work since its near but no luck. Started fast and then got stuck again. And I tried opening up links and youtube videos. They were both quick to open, load and play! I'll keep trying. Just don't get what the problem might be. Have unlimited download limit.

deepesh_p said:
This also doesn't seem to work. Tried the main download link as well as a France Mirror thinking it might work since its near but no luck. Started fast and then got stuck again. And I tried opening up links and youtube videos. They were both quick to open, load and play! I'll keep trying. Just don't get what the problem might be. Have unlimited download limit.
Click to expand...
Click to collapse
so you have a bad internet connection.

I guess so @alray. But its still funny that it can download a youtube video to stream but not a file. In the meanwhile I was checking other posts on the HTC One development thread where some people have reported having successfully converted AT&T to International version saying that they have the same internals. Will that improve our odds of getting s-off? Also the international version is already receiving 5.0.2 I read. Can we try this? This is killing me. I have the phone for 5 days now and I'm still stuck with my old phone. I just want lollipop and I didn't think that would be such a pain in the ass to achieve.

[Q] Active cmdline overflow, bootloop, can't access recovery/boot

Hello , My main goal before starting this whole process was to put the phone back to 100% stock, back to **LOCKED**, so that I could get my phone repaired under warranty.
My main problem came with that my HBOOT version was 1.57.0000 and "S-On".
I have now come to this error in the FASTBOOT screen that says "Active cmdline overflow!" after trying to install a stock rom on my phone after reading somewhere that a person had managed to obtain S-Off after putting a stock + bulletproof kernel and running Firewater.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.27.3263.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4307mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-660ef031
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I have read countless threads about this error, attempted to flash countless recovery images to try and gain access back to recovery mode from FASTBOOT but I get the same error. Which is after attempting to access Recovery when having flashed a new recovery image, it tries to go in but loops back round to FASTBOOT screen with the same "Active cmdline overflow! (1025 Bytes)
If someone please, has any fix to this problem, I would be greatly appreciated.
If there is any information you need to know please ask!

Jimmyy9 said:
Hello , My main goal before starting this whole process was to put the phone back to 100% stock, back to **LOCKED**, so that I could get my phone repaired under warranty.
My main problem came with that my HBOOT version was 1.57.0000 and "S-On".
I have now come to this error in the FASTBOOT screen that says "Active cmdline overflow!" after trying to install a stock rom on my phone after reading somewhere that a person had managed to obtain S-Off after putting a stock + bulletproof kernel and running Firewater.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.27.3263.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4307mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-660ef031
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I have read countless threads about this error, attempted to flash countless recovery images to try and gain access back to recovery mode from FASTBOOT but I get the same error. Which is after attempting to access Recovery when having flashed a new recovery image, it tries to go in but loops back round to FASTBOOT screen with the same "Active cmdline overflow! (1025 Bytes)
If someone please, has any fix to this problem, I would be greatly appreciated.
If there is any information you need to know please ask!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2739126

alray said:
http://forum.xda-developers.com/showthread.php?t=2739126
Click to expand...
Click to collapse
Hi thank you for your reply, unfortunately I have read this topic almost back to front and have tried every recovery image that was posted, but none have been successful in allowing me into recovery mode.

Jimmyy9 said:
Hi thank you for your reply, unfortunately I have read this topic almost back to front and have tried every recovery image that was posted, but none have been successful in allowing me into recovery mode.
Click to expand...
Click to collapse
then you'll probably need to send your phone for a motherboard replacement.

alray said:
then you'll probably need to send your phone for a motherboard replacement.
Click to expand...
Click to collapse
I was thinking this may come down to this. I know that my phone is still under warranty until April next year, however if I send this phone back to them in the state it is in surely they will throw it back at me saying it's been messed about with?
The current status of the phone is **Tampered** and **Unlocked**. I'm afraid I do not know the command to print the information from the top of FASTBOOT.

Jimmyy9 said:
I was thinking this may come down to this. I know that my phone is still under warranty until April next year, however if I send this phone back to them in the state it is in surely they will throw it back at me saying it's been messed about with?
The current status of the phone is **Tampered** and **Unlocked**. I'm afraid I do not know the command to print the information from the top of FASTBOOT.
Click to expand...
Click to collapse
If you already tried everything it the guide I have posted above then there is probably nothing more you can do. You can not remove TAMPERED and UNLOCKED flags from the bootloader screen with S-ON and this void your warranty. They will probably charge you to replace the main board.

alray said:
If you already tried everything it the guide I have posted above then there is probably nothing more you can do. You can not remove TAMPERED and UNLOCKED flags from the bootloader screen with S-ON and this void your warranty. They will probably charge you to replace the main board.
Click to expand...
Click to collapse
Thank you for your swift replies.
This further question goes beyond my knowledge of android development. Is there a way at all to make the device look like it is a hard brick to remove the evidence of Tampering and Unlocking? I can see this can be perceived as quite a bad thing to do morally, but I can see the coming quote from HTC for them to fix the motherboard as being quite high in price!

Jimmyy9 said:
Is there a way at all to make the device look like it is a hard brick to remove the evidence of Tampering and Unlocking?
Click to expand...
Click to collapse
With S-ON and not able to boot in recovery, I don't know how.

alray said:
With S-ON and not able to boot in recovery, I don't know how.
Click to expand...
Click to collapse
Thank you very much for your replies and help
I did see in this thread http://forum.xda-developers.com/showthread.php?t=2781953 that @nkk71 was able to fix what seems to be an exact copy of the problem I have here. However what nkk71 actually did is very vague since he assisted the person through PM/Teamviewer. It would be great to hear what fixed the problem!

Jimmyy9 said:
Thank you very much for your replies and help
I did see in this thread http://forum.xda-developers.com/showthread.php?t=2781953 that @nkk71 was able to fix what seems to be an exact copy of the problem I have here. However what nkk71 actually did is very vague since he assisted the person through PM/Teamviewer. It would be great to hear what fixed the problem!
Click to expand...
Click to collapse
Hi Jimmyy9,
unfortunately, it's a question of luck... i didnt post what we did, because it was (and still is) inclusive (otherwise i would have posted the solution).
in that particular instance, we were able to flash the noBCB recovery to the kernel partition and were able to access it.
i've tried the same (and a lot more) a couple of days ago, but without any success
it still eludes me what/when/why would allow a custom recovery to boot with S-ON on higher hboots, why it sometimes works, and most of the time it doesn't, so i really have very little to offer
unless you can get to a custom recovery (even a rooted ROM), i honestly can't help
just for info, i did a similar procedure on the HTC Butterfly S, but it also required an hboot downgrade to be able to get to recovery.
sorry, but unless you are able to get to any custom recovery or rooted ROM, i don't have any ideas

nkk71 said:
Hi Jimmyy9,
unfortunately, it's a question of luck... i didnt post what we did, because it was (and still is) inclusive (otherwise i would have posted the solution).
in that particular instance, we were able to flash the noBCB recovery to the kernel partition and were able to access it.
i've tried the same (and a lot more) a couple of days ago, but without any success
it still eludes me what/when/why would allow a custom recovery to boot with S-ON on higher hboots, why it sometimes works, and most of the time it doesn't, so i really have very little to offer
unless you can get to a custom recovery (even a rooted ROM), i honestly can't help
just for info, i did a similar procedure on the HTC Butterfly S, but it also required an hboot downgrade to be able to get to recovery.
sorry, but unless you are able to get to any custom recovery or rooted ROM, i don't have any ideas
Click to expand...
Click to collapse
Thank you for the detailed reply. I had been up for 30+ hours finding fixes and reading information regarding bricking phone and how to restore them. So my situation now is to either send it back to HTC repairs and confess to them I bricked my phone and cough up the costs for them to fix it,
Or
Attempt to fix the corrupt binary which I understand is the "misc" partition. I do however understand this may not be possible without s-off or recovery access. My only option would be if there existed a RUU h-boot 1.57 exploit? It might also be interesting to test the recovery img you used to fix the previous problem, obviously this is getting into desperation but I'm willing to try absolutely everything before I give in to sending HTC a bricked phone to fix.

Jimmyy9 said:
Thank you for the detailed reply. I had been up for 30+ hours finding fixes and reading information regarding bricking phone and how to restore them. So my situation now is to either send it back to HTC repairs and confess to them I bricked my phone and cough up the costs for them to fix it,
Or
Attempt to fix the corrupt binary which I understand is the "misc" partition. I do however understand this may not be possible without s-off or recovery access. My only option would be if there existed a hboot 1.57 exploit? It might also be interesting to test the recovery img you used to fix the previous problem, obviously this is getting into desperation but I'm willing to try absolutely everything before I give in to sending HTC a bricked phone to fix.
Click to expand...
Click to collapse
fixing the misc partition, doesn't actually require s-off, just "somewhere" where you have access to "dd" partitions.... the problem is that [adb commands with root and busybox], are only available in:
* a booted rooted ROM with USB debugging enabled
or
* a custom recovery
unfortunately, (at least to the best of my knowledge and efforts), fastboot is not able to flash to the misc partition... i tried a lot of different things, but could not get fastboot to flash to the misc.
as i mentioned, a couple of days ago, i spent a good 3 to 4 hours on teamviewer with another user in the same situation as yours (except he had an international unbranded edition, which has a lot more signed firmwares than your model), and we went through a lot of permutations to try to get somewhere but unfortunately with no success
maybe if i have some time over the weekend, i'll do a teamviewer session with you, but i fear it will also end up in failure
if there is somebody close to you who has a jtag (or other hardware), i guess this could be fixed easily, but with software only there are only so many things you can do.

nkk71 said:
fixing the misc partition, doesn't actually require s-off, just "somewhere" where you have access to "dd" partitions.... the problem is that [adb commands with root and busybox], are only available in:
* a booted rooted ROM with USB debugging enabled
or
* a custom recovery
unfortunately, (at least to the best of my knowledge and efforts), fastboot is not able to flash to the misc partition... i tried a lot of different things, but could not get fastboot to flash to the misc.
as i mentioned, a couple of days ago, i spent a good 3 to 4 hours on teamviewer with another user in the same situation as yours (except he had an international unbranded edition, which has a lot more signed firmwares than your model), and we went through a lot of permutations to try to get somewhere but unfortunately with no success
maybe if i have some time over the weekend, i'll do a teamviewer session with you, but i fear it will also end up in failure
if there is somebody close to you who has a jtag (or other hardware), i guess this could be fixed easily, but with software only there are only so many things you can do.
Click to expand...
Click to collapse
I appreciate you offering your free time to help with my problem but if you think it will produce the same results as your previous tests then I wouldn't want you to waste your time. I have heard about this JTag process and it looks very convincing @ www.funphoneshop.com.
I see 2 paths.
The first would be to go with the JTag process and hope that it works (since m7 is not listed on their model list)
or
Seeing as my phone is still under HTC warranty until 2016, I could attempt to further brick the phone (hard-brick not turning on at all) and go through the repair process to get a replacement phone. If I did do this I would need to do something that gives no proof that this phone was ever rooted/unlocked.
In your knowledge would a simple flash of a ROM from another model or device corrupt hboot/bootloader?

Hello again, I've done some more research about what other users did when they had unfortunately hard-bricked their phone and I came across this thread that you had also posted in a few weeks ago (http://forum.xda-developers.com/htc-one/help/htc-one-m7-hard-brick-t2876273).
According to your post flashing this recovery will corrupt one of the main partitions and therefore make the device unable to switch on and then cause it to appear as "QUALCOMM HS6USB QDLOADER 9008".
My question is that are HTC able to see any proof of tampering once the device is in Qualcomm mode?

Jimmyy9 said:
I appreciate you offering your free time to help with my problem but if you think it will produce the same results as your previous tests then I wouldn't want you to waste your time. I have heard about this JTag process and it looks very convincing @ www.funphoneshop.com.
I see 2 paths.
The first would be to go with the JTag process and hope that it works (since m7 is not listed on their model list)
Click to expand...
Click to collapse
you should give them a call, with the proper hardware they can S-OFF your device and a lot more, so since you know what the problem is it should be easy to fix for them.
even if they only s-off the phone, that would be enough to continue the software solution (downgrade hboot and use the noBCB recovery)

Relock Bootloader

Hello Folks
My bootloader of my Desire 510 is unlocked and i want it back locked, but dont know how to do it
i hope someone can help me
Regards Marco

Addicted2Bass said:
Hello Folks
My bootloader of my Desire 510 is unlocked and i want it back locked, but dont know how to do it
i hope someone can help me
Regards Marco
Click to expand...
Click to collapse
Hello Marco,
Here is how to relock your bootloader:
1. Power the phone down
2. Hold "Down" button then hold "Power" key while still holding "Down" button until you get into the bootloader
3. Release "Down" and "Power" button
A different way to do it other than steps 1 - 3 is follow steps 6 - 8 and type in a command prompt
Code:
adb reboot bootloader
4. Tap "Power" key once and it will change from "HBOOT" in white letters with blue background to "FASTBOOT" in white letters with red background
5. Connect your USB cable and it will say "FASTBOOT USB"
6. Navigate to the folder you have your adb.exe, fastboot.exe stuff from Android Studio or wherever you obtained it from (Mine is in C:\myusername\Android\sdk\platform-tools)
7. Hold the "Shift" key then right click in any empty space in that folder
8. Select "Open command window here"
9. Type
Code:
fastboot devices
in the command window, then press Enter just to make sure it is picking up your phone
10. You should see something like: "HT42PXU99475 fastboot" if you don't make sure your USB cable is inserted all the way and you are in "FASTBOOT USB"
11. Type
Code:
fastboot oem lock
in the command window
You should see something like:
Code:
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 596539196 (0x1FFFFD6C)
(bootloader) Start Verify: 3
(bootloader) WARM RESET: 9
(bootloader) [INFO] Reset reason in IMEM is 0x77665800
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.110s
Your phone will automatically reboot and your bootloader will be locked
You can check by booting into the bootloader and it should say *** RELOCKED *** at the top in white letters and purple background

Thanks Dude!
Its locked indeed!!

Do i need to use this step in order to return to stock? and what are the steps to return to stock,i have stock image?
is there a certain kernal to flash along with stock image,if someone could provide steps to return to stock,id be grateful! thanks

donthateme702 said:
Do i need to use this step in order to return to stock? and what are the steps to return to stock,i have stock image?
is there a certain kernal to flash along with stock image,if someone could provide steps to return to stock,id be grateful! thanks
Click to expand...
Click to collapse
You only need to follow those steps if you plan to use the RUU from here.
If you have a stock recovery, you can use TWRP. If you have the file boot.emmc.win in the recovery folder, that is the stock kernel. Just put the stock image on your sdcard and Restore it in TWRP.

It worked... A little too well.
blaqueknight said:
You only need to follow those steps if you plan to use the RUU from "I can't post links yet, but you get the idea..."
If you have a stock recovery, you can use TWRP. If you have the file boot.emmc.win in the recovery folder, that is the stock kernel. Just put the stock image on your sdcard and Restore it in TWRP.
Click to expand...
Click to collapse
I had been bricked, or at least I'm pretty sure I was. However... Upon trying to unlock the bootloader via the WinDroid deal offered here in xda, the bootloader now won't re-unlock.
The word *RELOCKED* has been frickin' glaring at me for over 3 hours now, and I can't seem to find the answer or help anywhere. :crying:

MN-StormChaser said:
I had been bricked, or at least I'm pretty sure I was. However... Upon trying to unlock the bootloader via the WinDroid deal offered here in xda, the bootloader now won't re-unlock.
The word *RELOCKED* has been frickin' glaring at me for over 3 hours now, and I can't seem to find the answer or help anywhere. :crying:
Click to expand...
Click to collapse
Do you have adb on your computer? This is one reason why I don't trust the one click root methods. You can fix this by downloading the rom for your phone from the HTC website. If you tell me what carrier you have I can get you the link to download a RUU to use on your computer to fix this and return the phone to stock.

MrMike2182 said:
Do you have adb on your computer? This is one reason why I don't trust the one click root methods. You can fix this by downloading the rom for your phone from the HTC website. If you tell me what carrier you have I can get you the link to download a RUU to use on your computer to fix this and return the phone to stock.
Click to expand...
Click to collapse
I do have abd and, fortunately, I still have the RUU I used to unbrick my phone. I really was optimistic about WinDroid working, but I guess that's just how it goes. Hopefully I can get it unlocked and, at least, rooted before noon. Big day today, might chase a few tornadoes!!! :fingers-crossed: I'll post another reply to say whether or not manually re-unlocking it works.
On second thought, it would be very wise to be proactive and see if my RUU is the same as the one you're thinking of... I may have just made myself look like an idiot, but with this rooting and rom and kernel stuff I am a complete newbie. If you could post that link, I would greatly appreciate it. Thanks!!!

MN-StormChaser said:
I do have abd and, fortunately, I still have the RUU I used to unbrick my phone. I really was optimistic about WinDroid working, but I guess that's just how it goes. Hopefully I can get it unlocked and, at least, rooted before noon. Big day today, might chase a few tornadoes!!! :fingers-crossed: I'll post another reply to say whether or not manually re-unlocking it works.
On second thought, it would be very wise to be proactive and see if my RUU is the same as the one you're thinking of... I may have just made myself look like an idiot, but with this rooting and rom and kernel stuff I am a complete newbie. If you could post that link, I would greatly appreciate it. Thanks!!!
Click to expand...
Click to collapse
WinDroid is a great tool. The only problem with it comes when you have adb installed already and you install the drivers that come with WinDroid. They cause a conflict.
I hope the manual method of unlocking works for you. It has always worked for me, unless I made a mistake. When I correct the mistake, it goes off without a hitch.
You can find the RUU here for your respective carrier.

MN-StormChaser said:
I do have abd and, fortunately, I still have the RUU I used to unbrick my phone. I really was optimistic about WinDroid working, but I guess that's just how it goes. Hopefully I can get it unlocked and, at least, rooted before noon. Big day today, might chase a few tornadoes!!! :fingers-crossed: I'll post another reply to say whether or not manually re-unlocking it works.
On second thought, it would be very wise to be proactive and see if my RUU is the same as the one you're thinking of... I may have just made myself look like an idiot, but with this rooting and rom and kernel stuff I am a complete newbie. If you could post that link, I would greatly appreciate it. Thanks!!!
Click to expand...
Click to collapse
If you need help with manually unlocking it let us know because it's really easy.

More details...
I may need some more help, pertaining the specific step-by-step stuff... Downloading the stock ... Rom/RUU?... from the HTC website. I'll be up all night trying to get this fixed, mainly due to needing my phone for my new job early this week. My end goal through all of this is to get a rom/kernel, or whatever else is needed, installed on it and either have it with write-protection removed or just completely blank so I don't have to worry about Boost hacking my phone and installing a bunch of crap and changing my screen setup. I really appreciate your help, guys. I will admit that, yes, I am slow to catch on to this stuff, but once I completely get the hang of this I want to be a big contributor to XDA and start helping others and developing/testing roms, etc.

Unlocking
MN-StormChaser said:
I may need some more help, pertaining the specific step-by-step stuff... Downloading the stock ... Rom/RUU?... from the HTC website. I'll be up all night trying to get this fixed, mainly due to needing my phone for my new job early this week. My end goal through all of this is to get a rom/kernel, or whatever else is needed, installed on it and either have it with write-protection removed or just completely blank so I don't have to worry about Boost hacking my phone and installing a bunch of crap and changing my screen setup. I really appreciate your help, guys. I will admit that, yes, I am slow to catch on to this stuff, but once I completely get the hang of this I want to be a big contributor to XDA and start helping others and developing/testing roms, etc.
Click to expand...
Click to collapse
If you go to http://www.htcdev.com/bootloader/ create an account, then they will walk you right through the method to unlock, and it is exactly the same method used to reunlock.

Hey do u know how to find which carrier the mobile is ??
Bcoz when i bought it,,the cover is of boostmobile...so is my carrier boost??

deepak oli said:
Hey do u know how to find which carrier the mobile is ??
Bcoz when i bought it,,the cover is of boostmobile...so is my carrier boost??
Click to expand...
Click to collapse
If that's what the cover says then that's what it is.. Boost Mobile. Where did you buy this phone from?

My relatives bought it from u.s!

deepak oli said:
My relatives bought it from u.s!
Click to expand...
Click to collapse
I'm pretty sure I can fix the phone now, since I finally have all the information I've needed for the last week!
Do you have a Boost Mobile over there in your Country? If not it's going to be pretty hard to use the phone since it's locked to Boost..
Hey, yooo hooo @deepak oli Answer me!!
---------- Post added at 10:09 PM ---------- Previous post was at 09:37 PM ----------
Fine don't answer me then, do it when you want to..
Ok here we go, you need to flash twrp from right here ---> twrp-2.8.7.0-a11.img This is going to be flashed after you unlock your boot loader so go use your unlock token and unlock the boot and then from a computer flash the twrp by doing fastboot flash recovery twrp-2.8.7.0-a11.img after you flash that go to the HBoot and tell it to reboot to recovery and while you're in recovery tap backup to make a backup because it needs to be done to move certain files/folders... Then go to the XDA thread and download the modded cm11 by me and follow the directions on which file to put it in and after this your phone will boot... CM11 Modded on XDA

Will this work and will i be able to use my phone again???
If yes then thhhaaaannnnkkkk uuuuuu!!!!!!

deepak oli said:
Will this work and will i be able to use my phone again???
If yes then thhhaaaannnnkkkk uuuuuu!!!!!!
Click to expand...
Click to collapse
It should have worked already if you did what I told you.

RUU for htc desire 510
MrMike2182 said:
Do you have adb on your computer? This is one reason why I don't trust the one click root methods. You can fix this by downloading the rom for your phone from the HTC website. If you tell me what carrier you have I can get you the link to download a RUU to use on your computer to fix this and return the phone to stock.
Click to expand...
Click to collapse
hey can you by any chance get a RUU for me. I have been searching for days (literally).
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1372.19.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA49GY405962
(bootloader) imei: 123456789231654
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a11_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0PCV22000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
Thats the phone info. i NEED it because i cant use my phones mobile data

Dopekyd said:
hey can you by any chance get a RUU for me. I have been searching for days (literally).
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1372.19.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA49GY405962
(bootloader) imei: 123456789231654
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a11_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0PCV22000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
Thats the phone info. i NEED it because i cant use my phones mobile data
Click to expand...
Click to collapse
Is your carrier Cricket or something else?