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!

[ON HOLD] Stuck in boot screen (not bootloader, rooted)

Hi, after searching through many posts and trying different things which didn't solve my problem for ours, I decided to just ask...
I have a rooted HTC (Switzerland / Europe version) and I tried to unroot it with different "europe" RUU's from this forum, none worked but I saw in the comments that some of those RUU's required S-OFF. So without any experience whatsoever my mastermind decided to just give it a try and turn S-OFF with the moonshine method. I guess I chose the wrong file (again?) and it didnt work, it always ran 10 restarts in the moonshine method at the end and then the error message "don't drink and shine" popped up. So I gave up and just started the phone.
After starting, I realised that the WIFI and the camera wasn't working anymore (tried all I could) and again I came to this forum and looked for solutions. I tried to wipe everything on the phone, including data wipe and all the wiped I found in twrp. After I did that, I chose the option reboot and well, the phone didnt shut off anymore and I was stuck in the starting screen ( HTC - quitly brilliant -- with the text below: this build is for development....) I tried all the shut down methods with sound button down and so on, also to keep a fleshlight on it (found: http://forum.xda-developers.com/showthread.php?t=2418404 )
I don't know what else to do and I'm pretty much lost. I shouldn't have tried all this without the knowledge damn -.-
please help!

Enion said:
Hi, after searching through many posts and trying different things which didn't solve my problem for ours, I decided to just ask...
I have a rooted HTC (Switzerland / Europe version) and I tried to unroot it with different "europe" RUU's from this forum, none worked but I saw in the comments that some of those RUU's required S-OFF. So without any experience whatsoever my mastermind decided to just give it a try and turn S-OFF with the moonshine method. I guess I chose the wrong file (again?) and it didnt work, it always ran 10 restarts in the moonshine method at the end and then the error message "don't drink and shine" popped up. So I gave up and just started the phone.
After starting, I realised that the WIFI and the camera wasn't working anymore (tried all I could) and again I came to this forum and looked for solutions. I tried to wipe everything on the phone, including data wipe and all the wiped I found in twrp. After I did that, I chose the option reboot and well, the phone didnt shut off anymore and I was stuck in the starting screen ( HTC - quitly brilliant -- with the text below: this build is for development....) I tried all the shut down methods with sound button down and so on, also to keep a fleshlight on it (found: http://forum.xda-developers.com/showthread.php?t=2418404 )
I don't know what else to do and I'm pretty much lost. I shouldn't have tried all this without the knowledge damn -.-
please help!
Click to expand...
Click to collapse
If you can restart and get into bootloader by holding power and vol. down, flash TWRP, put your RUU zip on your phone storage, and then flash it.

kibmikey1 said:
If you can restart and get into bootloader by holding power and vol. down, flash TWRP, put your RUU zip on your phone storage, and then flash it.
Click to expand...
Click to collapse
Hi, thanks for your advice. The problem is that, after recharging the phone again and trying several times, I just can't get into bootloader. When I hold the power button and vol. down the home and "arrow" touch-buttons at the bottom of the phone just start blinking. As long as I hold these two buttons the blinking doesn't stop, I did hold them for a full minute and nothing happend on the screen itself. After releasing the blinking stopped but the screen remained on it's state...

Enion said:
Hi, thanks for your advice. The problem is that, after recharging the phone again and trying several times, I just can't get into bootloader. When I hold the power button and vol. down the home and "arrow" touch-buttons at the bottom of the phone just start blinking. As long as I hold these two buttons the blinking doesn't stop, I did hold them for a full minute and nothing happend on the screen itself. After releasing the blinking stopped but the screen remained on it's state...
Click to expand...
Click to collapse
Blinking is good, just hold POWER + VOLDOWN with the phone sensors under a bright light (not kidding!!), it should reboot after 30sec to 2 minute. If it doesn't reboot, let go and try again; the bright light is important!!
Once it reboots, keep holding VOLDOWN so it reboots to bootloader.

Thank you guys, I tried it and it strangely worked (literally 2minutes with a light on it). I'm in the bootloader now and will try to
flash TWRP, put your RUU zip on your phone storage, and then flash it.
Click to expand...
Click to collapse
as kibmikey1 wrote. I hope I'll find the right files and manuals this time. Will report back

Enion said:
Thank you guys, I tried it and it strangely worked (literally 2minutes with a light on it). I'm in the bootloader now and will try to as kibmikey1 wrote. I hope I'll find the right files and manuals this time. Will report back
Click to expand...
Click to collapse
You can't flash a RUU zip through recovery.
Most important question: What's your final goal?? Where do you want to get with your phone??
also post a "fastboot getvar all" (remove IMEI and s/n), and date of bootloader.
PS: hit the thanks button if we helped

nkk71 said:
You can't flash a RUU zip through recovery.
Most important question: What's your final goal?? Where do you want to get with your phone??
also post a "fastboot getvar all" (remove IMEI and s/n), and date of bootloader.
PS: hit the thanks button if we helped
Click to expand...
Click to collapse
Didn't know about the thank you, my bad there.
My final goal is to have an up-to-date phone. I couldn't update my phone while it was rooted and therefore tried to unroot it and ran into all these complications.
I tried the command you wrote and the result was:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.161.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP110
(bootloader) battery-status: good
(bootloader) battery-voltage: 4218mV
(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.062s
thanks!

Enion said:
Didn't know about the thank you, my bad there.
My final goal is to have an up-to-date phone. I couldn't update my phone while it was rooted and therefore tried to unroot it and ran into all these complications.
I tried the command you wrote and the result was:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.161.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH35xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP110
(bootloader) battery-status: good
(bootloader) battery-voltage: 4218mV
(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.062s
thanks!
Click to expand...
Click to collapse
hey mate, edit your post and remove IMEI and s/n we don't need to see those.
can you confirm your hboot is dated before June 2013. I'll post your options after that

Hi, thanks for noticing, I removed it, please dit your post aswell
If you're talking about the date at the top of the bootloader, it says May 3

Enion said:
Hi, thanks for noticing, I removed it, please dit your post aswell
Click to expand...
Click to collapse
I already did when quoting you, changed them all to XXXXXXXXXXX, or is it showing up on your computer?
Enion said:
If you're talking about the date at the top of the bootloader, it says May 3
Click to expand...
Click to collapse
gimme a few minutes while I write down all the options
BTW: Easy on the thanks button, you only have 8 per day

nkk71 said:
I already did when quoting you, changed them all to XXXXXXXXXXX, or is it showing up on your computer?
gimme a few minutes while I write down all the options
BTW: Easy on the thanks button, you only have 8 per day
Click to expand...
Click to collapse
My bad again, it doesn't show up. I need to learn to read the forum rules first before posting stuff I guess.

Enion said:
My bad again, it doesn't show up. I need to learn to read the forum rules first before posting stuff I guess.
Click to expand...
Click to collapse
Code:
(bootloader) version-bootloader: 1.44.0000 (May 3)
(bootloader) version-main: 1.29.161.16
OK, so you have two primary choices:
A) Stay S-On
B) Get S-Off: with the above hboot and firmware, you can easily get s-off using revone
Now, with an unlocked bootloader but S-ON, you can
---- flash custom or stock ROM
---- flash different radios (ie baseband)
---- flash custom kernel
---- flash custom recovery
you cannot:
---- you cannot flash unsigned firmware
---- you cannot downgrade (firmware and hboot)
---- you cannot remove TAMPERED
---- you cannot LOCKED your phone, at best it will say RELOCKED
---- you cannot run a downgrade RUU
With S-Off, you can do ALL of these and more, e.g. you can reset your phone to 100% out-of-the box, and you can even change your phone from a Vodafone phone to ANY other variant (eg unbranded European, US Developer, 100% Google Play Edition, etc.)
I'm in no way encouraging you to go S-Off, unless YOU are comfortable with the thought and procedure.
If you're looking at always having the latest releases, then I personally would stick with custom ROMs, these get updated way quicker (even if sometimes based on a leak), than carrier dependent OTAs.
Should you stay S-On, the only way to upgrade the firmware, will be using an official Vodafone OTA, in one of two methods:
1- go back to stock rom & stock recovery, download and install, and then reinstall custom ROM
2- get your hands on the OTA file (either by downloading it yourself, or if you find it on the net), then extract "firmware.zip" and flash it in fasboot RUU mode (this will work cause the OTA contains a signed firmware specifically for your phone)
[and you cannot downgrade if for some reason you would want to]
On the other hand, if you are S-Off, you can use an unsigned firmware package found in various threads.
Ok, that's enough for now, even my head is spinning LOL.
Let me know what you think, and if you need more explanations. Then rethink your ultimate goal, and we can proceed from there.
(Now all this writing deserves a thanks )

nkk71 said:
Code:
(bootloader) version-bootloader: 1.44.0000 (May 3)
(bootloader) version-main: 1.29.161.16
OK, so you have two primary choices:
A) Stay S-On
B) Get S-Off: with the above hboot and firmware, you can easily get s-off using revone
Now, with an unlocked bootloader but S-ON, you can
---- flash custom or stock ROM
---- flash different radios (ie baseband)
---- flash custom kernel
---- flash custom recovery
you cannot:
---- you cannot flash unsigned firmware
---- you cannot downgrade (firmware and hboot)
---- you cannot remove TAMPERED
---- you cannot LOCKED your phone, at best it will say RELOCKED
---- you cannot run a downgrade RUU
With S-Off, you can do ALL of these and more, e.g. you can reset your phone to 100% out-of-the box, and you can even change your phone from a Vodafone phone to ANY other variant (eg unbranded European, US Developer, 100% Google Play Edition, etc.)
I'm in no way encouraging you to go S-Off, unless YOU are comfortable with the thought and procedure.
If you're looking at always having the latest releases, then I personally would stick with custom ROMs, these get updated way quicker (even if sometimes based on a leak), than carrier dependent OTAs.
Should you stay S-On, the only way to upgrade the firmware, will be using an official Vodafone OTA, in one of two methods:
1- go back to stock rom & stock recovery, download and install, and then reinstall custom ROM
2- get your hands on the OTA file (either by downloading it yourself, or if you find it on the net), then extract "firmware.zip" and flash it in fasboot RUU mode (this will work cause the OTA contains a signed firmware specifically for your phone)
[and you cannot downgrade if for some reason you would want to]
On the other hand, if you are S-Off, you can use an unsigned firmware package found in various threads.
Ok, that's enough for now, even my head is spinning LOL.
Let me know what you think, and if you need more explanations. Then rethink your ultimate goal, and we can proceed from there.
(Now all this writing deserves a thanks )
Click to expand...
Click to collapse
Thanks for the help. I will try to get S-Off then. I hope I can do it this time though. I'll report when I get it Off or need help again. Looking forward

Enion said:
Thanks for the help. I will try to get S-Off then. I hope I can do it this time though. I'll report when I get it Off or need help again. Looking forward
Click to expand...
Click to collapse
No problem mate, remember for revone to work your firmware is good ((bootloader) version-main: 1.29.161.16), but you will need a ROM based on 4.1.2 preferably (I have one - which worked for me and two others) in case you can't find one.
Also read here: http://forum.xda-developers.com/showthread.php?t=2431515
here: http://forum.xda-developers.com/showthread.php?t=2365506
and of course: http://forum.xda-developers.com/showthread.php?t=2314582
Let me know if you need any more help.
Once you are S-Off, you can easily upgrade/downgrade firmware in @vomer's guide (same as before, but down in the firmware section): http://forum.xda-developers.com/showthread.php?t=2365506

Enion said:
Thanks for the help. I will try to get S-Off then. I hope I can do it this time though. I'll report when I get it Off or need help again. Looking forward
Click to expand...
Click to collapse
Hey @Enion, you all good now?

nkk71 said:
Hey @Enion, you all good now?
Click to expand...
Click to collapse
Hi, sry for the late reply, didn't have much time today. I flashed the rom (4.2.1) that nkk71 gave me in a PM and the phone is working just fine now. I decided to just stay in this state for the moment and think about getting S-Off later. I want to thank everyone involved in this thread and especially nkk71, really quick & reliable message board.
//Enion

Enion said:
Hi, sry for the late reply, didn't have much time today. I flashed the rom (4.2.1) that nkk71 gave me in a PM and the phone is working just fine now. I decided to just stay in this state for the moment and think about getting S-Off later. I want to thank everyone involved in this thread and especially nkk71, really quick & reliable message board.
//Enion
Click to expand...
Click to collapse
I know what you mean, just got back from work myself, and didnt have a minute to scratch my head all day :silly:
Just for your info, it took me less than ten minutes to get S-Off using my setup (that ROM and firmware 1.28.61.7), worked like a charm from the first time.
Anyway, until you decide to do it, could you edit the main thread title to include something like [ON HOLD], I usually prefer [SOLVED], but [ON HOLD] should do for now, until you revive your thread

nkk71 said:
I know what you mean, just got back from work myself, and didnt have a minute to scratch my head all day :silly:
Just for your info, it took me less than ten minutes to get S-Off using my setup (that ROM and firmware 1.28.61.7), worked like a charm from the first time.
Anyway, until you decide to do it, could you edit the main thread title to include something like [ON HOLD], I usually prefer [SOLVED], but [ON HOLD] should do for now, until you revive your thread
Click to expand...
Click to collapse
I tried to set in "on hold" but I think I'm missing some rights in this forum, it just doesn't work. I tried http://forum.xda-developers.com/showthread.php?p=27117213 this method aswell.

Enion said:
I tried to set in "on hold" but I think I'm missing some rights in this forum, it just doesn't work. I tried http://forum.xda-developers.com/showthread.php?p=27117213 this method aswell.
Click to expand...
Click to collapse
didnt read the the link you sent, usually you just go to the first post, click EDIT then at the bottom of the edit window, click GO ADVANCED and it would show the main thread title.
anyway don't worry about, most people (unfortunately) never bother to [CLOSE] [SOLVED] etc. no wonder the forum is hard to navigate through
take care
---------- Post added at 07:29 PM ---------- Previous post was at 07:24 PM ----------
nkk71 said:
didnt read the the link you sent, usually you just go to the first post, click EDIT then at the bottom of the edit window, click GO ADVANCED and it would show the main thread title.
anyway don't worry about, most people (unfortunately) never bother to [CLOSE] [SOLVED] etc. no wonder the forum is hard to navigate through
take care
Click to expand...
Click to collapse
Thank you sir!

[Q] HTC One Bootlooping after Google Edition ARHD 6.0 installation

At this time I am pretty much hopeless... Seriously, nothing works, but if a miracle happens and I get my HTC One back to life it will be thanks to you guys.
So... This is my story:
Today I was using my HTC One M7_UL like any other day, I had Android OneDroid BETA 15 (a CyanogenMod with a few tweaks) installed and I got bored of it, so I decided to flash a Google Edition ROM. Came to the forum and looked for the thread with most replies on "Custom Android HTC One ROMs" and found the winner of the Google Edition ones, the ARHD 6.0 Google Edition. Fine, I thought, let's flash this [email protected]%#. So I started by downloading the latest version (roughly 550 MB) and connecting my HTC One to my Windows 8.1 Pro computer. The HTC drivers don't work with my 8.1 Pro Windows but since I only needed it to send the .zip file to my Internal Storage I gave it a shot. Copied everything, disconnected and proceeded to my recovery (TWRP) where I Wiped it up and flashed ARHD 6.0 GE. After installing, still on the recovery, restored the phone to factory presets and rebooted it. A Google logo appeared and some Nexus-like balls started to spin, some weird sh%t. Until there, everything absolutely fine, but it stood there with the balls spinning for 3~4 minutes and I thought it was normal because it was the first boot after flashing the new ROM. Got to Language Settings on the Android Welcome screen but then it quickly turned black and reeboted. HTC Logo appeared for roughly 1 second and it got black and rebooted again, this time starting back up but when I got to the Language setup it would do the same thing, over and over again.
So I started looking into it and didn't find many answers, then I decided to try and flash another Google Edition ROM, SkyDragon, but as I am a COMPLETE NOOB in this rooting and wobbly wobbly thingies I had no idea how I would get the .zip file to the Internal Storage, since the HTC One HAS NO SD CARD!!! I researched a bit and found sth called ADB Sideloading, which I am certain you know what it is, but the thing is, since my computer doesn't quite work with HTC Drivers I had to use my sister's PC, with Windows 7 and HTC One All-in-One kit. I could access my bootloader and recovery despite of the bootloop, which I think is a good thing, so I put it to fastboot mode, connected the cable to her computer and on the phone it changed from "fastboot" in red to "fastboot usb" in red also, so I thought, oh ok, it will work now. But when I tried ADB commands or tried any of the commands on the All-in-One thing it would just say "NO DEVICES FOUND" or something among those lines.
Anyway, if someone got this far I already thank you for trying to help but I am pretty certain I got a bricked device. I don't even now what to do, should I try to ADB Sideload this other ROM or should I try a Sense ROM, cuz I read somewhere that Google Edition ROMs only work when migrating from Sense ROMs, and if I am supposed to flash a Sense ROM how would I do so? Please try to be as simple as possible, I don't know much and I am pretty noob, anyways, thank you so much, and I hope you can help me!
(Also, before this bootloop it was S-OFF and now it shows as S-ON)
Waiting for a response,
John B.

You need TWRP 2.6.33 or newer.
You need to be S-Off.
You need to have wiped cache and dalvik and probably a full format (except sdcard) wouldn't go amiss before installing. It sounds to me like it wasn't wiped properly.
The device doesn't S-On on its own, you probably did it with the toolkit or something.
ADB doesn't work in fastboot mode, fastboot mode is for fastboot command, such as flashing recovery.
Are you still unlocked?
Give us the output of
fastboot getvar all
Without IMEI and Serial Number.

BenPope said:
You need TWRP 2.6.33 or newer.
You need to be S-Off.
You need to have wiped cache and dalvik and probably a full format (except sdcard) wouldn't go amiss before installing. It sounds to me like it wasn't wiped properly.
The device doesn't S-On on its own, you probably did it with the toolkit or something.
ADB doesn't work in fastboot mode, fastboot mode is for fastboot command, such as flashing recovery.
Are you still unlocked?
Give us the output of
fastboot getvar all
Without IMEI and Serial Number.
Click to expand...
Click to collapse
Yeah I am unlocked and untempered.
Here is my fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxx
(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: 4309mV
(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.077s
And I am ABSOLUTELY SURE that before all of this it was S-OFF, ABSOLUTELY!

BenPope said:
You need TWRP 2.6.33 or newer.
You need to be S-Off.
You need to have wiped cache and dalvik and probably a full format (except sdcard) wouldn't go amiss before installing. It sounds to me like it wasn't wiped properly.
The device doesn't S-On on its own, you probably did it with the toolkit or something.
ADB doesn't work in fastboot mode, fastboot mode is for fastboot command, such as flashing recovery.
Are you still unlocked?
Give us the output of
fastboot getvar all
Without IMEI and Serial Number.
Click to expand...
Click to collapse
Also my TWRP is 2.6.3.3 so I should be good about that right?

Jvov said:
Also my TWRP is 2.6.3.3 so I should be good about that right?
Click to expand...
Click to collapse
Yes, but as far as I know, you need to be S-Off for GPE KitKat ROMs.
Do you really have no version-main?
If your hboot is 1.44 and dated prior to June, you should be able to use revone to S-Off, but you'll need a booting ROM of Android 4.2.2.

BenPope said:
Yes, but as far as I know, you need to be S-Off for GPE KitKat ROMs.
Do you really have no version-main?
If your hboot is 1.44 and dated prior to June, you should be able to use revone to S-Off, but you'll need a booting ROM of Android 4.2.2.
Click to expand...
Click to collapse
Can you explain exactly how can I do that?

Just flash back to another ROM for the moment that has root then use rumrunner to get S-OFF then flash ARHD GPE again. You'll be fine then.
Sent from my One using XDA Premium 4 mobile app

Also don't do a reset after flashing the rom. It will boot loop every time.
Bat cave One

zelendel said:
Also don't do a reset after flashing the rom. It will boot loop every time.
Bat cave One
Click to expand...
Click to collapse
Solved, thanks to all!

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?

HTC One M7 - can not update to android 5.

Hello everyone
First of all sorry for my english. I'm not a native english so please forgive me if I say something wrong. Second - this is my first thread here (since now, reading informations from here was enough to handle all of my problems but at this moment well... I surrender and need some advice) so please be understanding.
I have a problem with HTC M7. My friend gave it to me for a little hardware fix and software update. I fixed the hardware but I'm stuck on firmware update.
I wanted to update firmware to 5.05.651.2 with automatic updates but it crashes somewhere in the middle with red triangle sign.
So I started to read. First I've read that I need to unlock bootloader, so I made it with fastboot - nothing changed. Later found some info that I need a stock firmware to enable updates. So I downloaded some firmware but failed to install it (tried with fastboot). Next info I found that to install stock firmware I need to root the device. So I've rooted it. Still nothing. Trying to flash in "rebootRUU" mode with fastboot gave me info that no "android-info.txt" was found. Some more reading and searching and I've noticed that my HTC is probably Sprint version (to be honest I do not know what is the difference). So I downloaded some Sprint firmware. Still no effect... Ehh I'm depressed and I'm begging for help:crying:
So at this moment I have:
Android ver. 4.4.2
HTC Sense ver. 6.0
Software ver. 5.03.651.3
Kernel ver. 3.4.10-gf22c859
(translated from Polish menu)
Info from bootloader:
*** RELOCKED ***
M7_WLS PVT SHIP S-OFF RH
CID-11111111
HBOOT - 1.44.0000
RADIO-1.00.31.0603
OpenDSP-v31.120.274.0617
eMMC-BOOT
Jul 5 2013, 17:19:22:3
Custom recovery installed from file: openrecovery-twrp-2.5.0.0-m7wls
Root made with iRoot app.
Also I don't know if it was earlier, but now lockscreen on android is in Chinese while all the rest is in Polish :/
Maybe it's important - friend told me that phone is from Shanghai (I don't know where does he have that info from).
If any additional information is needed please write and I will post it asap.
What I would like to achieve? I would like to install latest available stock firmware (without any changes, cool apps or any additional software). Just an basic android with Google store available. My friend is not advanced android user. He just want latest software.
I would probably fight with this device more but also a big problem are dead links all over the forums (htc1guru etc). I'm counting that maybe some of you here have backups of roms. Or maybe I just don't know how to find a proper one.
Full step-by-step manual what should I do would be great but of course I appreciate any other suggestions or advice. Just need some help.
(one more thing - for those who want to write "use search, there are a lot of manuals on the web, we won't make it for you etc" please, I spent couple of hours searching and reading and I don't understand or I don't know how to use info's I found. I'm not an Android user for last couple of years)
Thank you in advance for any help

See comment in red below
qwe1234 said:
Hello everyone
First of all sorry for my english. I'm not a native english so please forgive me if I say something wrong. Second - this is my first thread here (since now, reading informations from here was enough to handle all of my problems but at this moment well... I surrender and need some advice) so please be understanding.
I have a problem with HTC M7. My friend gave it to me for a little hardware fix and software update. I fixed the hardware but I'm stuck on firmware update.
I wanted to update firmware to 5.05.651.2 with automatic updates but it crashes somewhere in the middle with red triangle sign. Indicating that your software partition isn't 100% stock. The ota update will only replace the required files to be updated, not the whole system. Before updating, the updater-script check integrity of all files to be updated. If only one of these file isn't as expected, the updater-script will abort and the update will not install ----> red triangle
So I started to read. First I've read that I need to unlock bootloader bootloader lock/unlock status isn't related to ota update, so I made it with fastboot - nothing changed. Later found some info that I need a stock firmware to enable updates. So I downloaded some firmware but failed to install it (tried with fastboot). Next info I found that to install stock firmware I need to root the device You don't need root to install firmware. So I've rooted it. Still nothing. Trying to flash in "rebootRUU" mode with fastboot gave me info that no "android-info.txt" was found indicating that you are not using the correct file. Some more reading and searching and I've noticed that my HTC is probably Sprint version (to be honest I do not know what is the difference The sprint variant is a CDMA phone). So I downloaded some Sprint firmware. Still no effect... Ehh I'm depressed and I'm begging for help:crying:
So at this moment I have:
Android ver. 4.4.2
HTC Sense ver. 6.0
Software ver. 5.03.651.3
Kernel ver. 3.4.10-gf22c859
(translated from Polish menu)
Info from bootloader:
*** RELOCKED ***
M7_WLS PVT SHIP S-OFF RH
CID-11111111
HBOOT - 1.44.0000 old bootloader version not matching your software version
RADIO-1.00.31.0603
OpenDSP-v31.120.274.0617
eMMC-BOOT
Jul 5 2013, 17:19:22:3
Custom recovery installed from file: openrecovery-twrp-2.5.0.0-m7wls twrp 2.5.0.0 is really outdated and won't work with recent files. Not a problem for now since you will not need to use twrp to fix it, just fyi
Root made with iRoot app.
Also I don't know if it was earlier, but now lockscreen on android is in Chinese while all the rest is in Polish :/
Maybe it's important - friend told me that phone is from Shanghai (I don't know where does he have that info from).
If any additional information is needed please write and I will post it asap.
What I would like to achieve? I would like to install latest available stock firmware (without any changes, cool apps or any additional software). Just an basic android with Google store available. My friend is not advanced android user. He just want latest software.
I would probably fight with this device more but also a big problem are dead links all over the forums (htc1guru etc). I'm counting that maybe some of you here have backups of roms. Or maybe I just don't know how to find a proper one.
Full step-by-step manual what should I do would be great but of course I appreciate any other suggestions or advice. Just need some help.
(one more thing - for those who want to write "use search, there are a lot of manuals on the web, we won't make it for you etc" please, I spent couple of hours searching and reading and I don't understand or I don't know how to use info's I found. I'm not an Android user for last couple of years)
Thank you in advance for any help
Click to expand...
Click to collapse
download these 3 files and save it in the folder where you already have fastboot.exe and adb.exe on your computer.
https://androidfilehost.com/?fid=24052804347850182
https://androidfilehost.com/?fid=24588232905725176
https://androidfilehost.com/?fid=24341993505161791
First update your firmware:
Code:
fastboot oem rebootRUU
fastboot flash zip 6.23.651.10_full_firmware.zip
fastboot flash zip 6.23.651.10_full_firmware.zip
fastboot reboot-bootloader
You need to do the "fastboot flash zip" command twice. First time you'll get the "remote: 90 hboot pre-update! Please flush image again immediately" error. Second time the firmware will flash completely and should see a "OK/ flash sucessful" message. You can disregard the progress bar on the phone screen, it might not indicate 100% but if fastboot tell you "OK/ flash sucessful" it's alright
Then you can confirm everything is alright with
Code:
fastboot getvar all
your version-main should now be 6.23.651.10 and your hboot 1.61 instead of 1.44
Now you can flash the RUU, similar process but you must use the fastboot version linked above (htc_fastboot.exe):
Code:
fastboot oem rebootRUU
htc_fastboot flash zip PN071IMG_M7WLS_L50_SENSE60_SPRINT_6.23.651.10_signed.zip
fastboot reboot
Your phone might reboot by itself once, just wait until fastboot reports "OK". Again you can disregard the progress bar on your phone.
Make sure the phone is fully charged before doing all that and if something goes wrong post here and wait (do not skip any steps).
If everything went ok, the phone should reboot to the latest stock android version and the old twrp version replaced with the stock recovery. If the phone was sim-unlocked it might be relocked to Sprint again and you'll have to sim-unlock again (you can find the procedure in the "Sprint htc one" forum section, in the "general" sub-section.

My friend Thank You very much for all the instructions... but...
Last step:
Now you can flash the RUU, similar process but you must use the fastboot version linked above (htc_fastboot.exe):
Code:
fastboot oem rebootRUU
htc_fastboot flash zip PN071IMG_M7WLS_L50_SENSE60_SPRINT_6.23.651.10_signed.zip
fastboot reboot
Your phone might reboot by itself once, just wait until fastboot reports "OK". Again you can disregard the progress bar on your phone.
Click to expand...
Click to collapse
ended with error ;(
fastboot gave following:
processing file 2/5...
error: cannot load 'C:\Users\x101ch\AppData\Local\Temp\tmpp6r0paxd'
htc_fastboot finished. total time: 297.909s
Phone restarted once in the middle like you said.
I rebooted with "fastboot reboot" . Startup screen show up and now there is a black screen with dimmed backlight. Power button doesn't do anything. Any of commands in fasboot also don't work. Ahh...
One more thing. I haven't noticed that you changed command from fastboot to htc_fastboot so I changed htc_fastboot file name to just fastboot and used command fastboot. Don't know if it matters...

qwe1234 said:
I rebooted with "fastboot reboot" . Startup screen show up and now there is a black screen with dimmed backlight. Power button doesn't do anything. Any of commands in fasboot also don't work. Ahh...
Click to expand...
Click to collapse
Now you probably understand why I said
if something goes wrong post here and wait (do not skip any steps).
Click to expand...
Click to collapse
Rebooting after a failed/incomplete flash can hard brick your phone. If you can't get fastboot connectivity again, there is not much you can do. Sorry

Ahhh. My bad;( I didn't want to leave everything turned on for so many hours. Well nevermind.
What do you think if I open up the phone nad reset it manually by unplugging the battery? Is there a chance to boot it to bootloader? Like I mentioned te start screen appeared so it looks like the phone hangs later. Am I thinking right?

qwe1234 said:
Ahhh. My bad;( I didn't want to leave everything turned on for so many hours. Well nevermind.
What do you think if I open up the phone nad reset it manually by unplugging the battery? Is there a chance to boot it to bootloader? Like I mentioned te start screen appeared so it looks like the phone hangs later. Am I thinking right?
Click to expand...
Click to collapse
maybe or let the battery drain then plug the phone again and try to boot in bootloader with vol down and power.

Ok. I will try to do that tomorrow and will post the result. Thanks again

Ufff...
I'm in bootloader again.
Unplugged battery directly on mainboard and connected again rebooted the phone. So... whats next? I promise I won't do anything more without a consult

qwe1234 said:
Ufff...
I'm in bootloader again.
Unplugged battery directly on mainboard and connected again rebooted the phone. So... whats next? I promise I won't do anything more without a consult
Click to expand...
Click to collapse
:good::good:
Can you post an update of your "fastboot getvar all" please (hide your imei and serialno before posting)

alray said:
:good::good:
Can you post an update of your "fastboot getvar all" please (hide your imei and serialno before posting)
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.02.20.0922
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXX
(bootloader) meid: 99000146554636
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4285mV
(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
all: Done!
finished. total time: 0.077s
htc_fastboot finished. total time: 0.623s

qwe1234 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.02.20.0922
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXX
(bootloader) meid: 99000146554636
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4285mV
(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
all: Done!
finished. total time: 0.077s
htc_fastboot finished. total time: 0.623s
Click to expand...
Click to collapse
try to flash the ruu again and post a screenshot of your cmd window if it doesn't work

alray said:
try to flash the ruu again and post a screenshot of your cmd window if it doesn't work
Click to expand...
Click to collapse
Alray... I don't know how to thank you. You're the best
Second flash went with a success at every step. Now everything seems to be absolutely ok. Firmware is updated.
Tomorrow I will check sim-lock and I will try to make a phone call and if everything will be ok I think it's gonna be the end
Thank you very much again

qwe1234 said:
Alray... I don't know how to thank you. You're the best
Second flash went with a success at every step. Now everything seems to be absolutely ok. Firmware is updated.
Tomorrow I will check sim-lock and I will try to make a phone call and if everything will be ok I think it's gonna be the end
Thank you very much again
Click to expand...
Click to collapse
:good:
you're welcome!

So I checked and the phone probably has a sim-lock. It shows notification that the simcard is wrong (translated from polish so in english it may be in some other words). I checked the subforum like you said in first reply and I found threads: [GUIDE] [fixed] SIM UNLOCK after lollipop and [GUIDE] Sprint sim unlock & Flash. I don't want to mess up anything (again) so could you please tell me which one is right for me?

qwe1234 said:
So I checked and the phone probably has a sim-lock. It shows notification that the simcard is wrong (translated from polish so in english it may be in some other words). I checked the subforum like you said in first reply and I found threads: [GUIDE] [fixed] SIM UNLOCK after lollipop and [GUIDE] Sprint sim unlock & Flash. I don't want to mess up anything (again) so could you please tell me which one is right for me?
Click to expand...
Click to collapse
So it looks like I'm stupid.
I tried to unlock the phone. Again bootloader unlocked, phone rooted. I wanted to unlock it with terminal commands using HtcOMADM_SPCS but I cannot install it. I've installed twrp (this time version 3.1.1.0) but it keeps saying that footer is wrong and signature verification failed...
Any more help, please? ;(

Hey sorry, don't mean to hijack this thread.
But would the same instructions apply for updating any older HTC m7 as far as the firmware and RUU is concerned?
I'm getting crickets on my thread, and just needed a general confirmation on the process again since it's been awhile.
I'm looking to flash a more current ROM and newer twrp recovery(or whatever is the best out there now).
Just confirming the process you described would still work the same way.
Thanks!
alray said:
See comment in red below
download these 3 files and save it in the folder where you already have fastboot.exe and adb.exe on your computer.
https://androidfilehost.com/?fid=24052804347850182
https://androidfilehost.com/?fid=24588232905725176
https://androidfilehost.com/?fid=24341993505161791
First update your firmware:
Code:
fastboot oem rebootRUU
fastboot flash zip 6.23.651.10_full_firmware.zip
fastboot flash zip 6.23.651.10_full_firmware.zip
fastboot reboot-bootloader
You need to do the "fastboot flash zip" command twice. First time you'll get the "remote: 90 hboot pre-update! Please flush image again immediately" error. Second time the firmware will flash completely and should see a "OK/ flash sucessful" message. You can disregard the progress bar on the phone screen, it might not indicate 100% but if fastboot tell you "OK/ flash sucessful" it's alright
Then you can confirm everything is alright with
Code:
fastboot getvar all
your version-main should now be 6.23.651.10 and your hboot 1.61 instead of 1.44
Now you can flash the RUU, similar process but you must use the fastboot version linked above (htc_fastboot.exe):
Code:
fastboot oem rebootRUU
htc_fastboot flash zip PN071IMG_M7WLS_L50_SENSE60_SPRINT_6.23.651.10_signed.zip
fastboot reboot
Your phone might reboot by itself once, just wait until fastboot reports "OK". Again you can disregard the progress bar on your phone.
Make sure the phone is fully charged before doing all that and if something goes wrong post here and wait (do not skip any steps).
If everything went ok, the phone should reboot to the latest stock android version and the old twrp version replaced with the stock recovery. If the phone was sim-unlocked it might be relocked to Sprint again and you'll have to sim-unlock again (you can find the procedure in the "Sprint htc one" forum section, in the "general" sub-section.
Click to expand...
Click to collapse

cloud66 said:
Hey sorry, don't mean to hijack this thread.
But would the same instructions apply for updating any older HTC m7 as far as the firmware and RUU is concerned?
Click to expand...
Click to collapse
Since yours is also a Sprint HTC One, yes the same procedure should work.
I'm getting crickets on my thread
Click to expand...
Click to collapse
quote me next time and I'll be notified, just like you did in this thread.
I'm looking to flash a more current ROM and newer twrp recovery(or whatever is the best out there now).
Click to expand...
Click to collapse
Don't forget that only Sprint roms and Sprint recovery will work on your phone (roms or recovery for the gsm/m7ul won't work). Make sure the custom rom you want to flash is compatible with the Sprint variant (it will be mentioned in the OP of the rom thread if it's compatible with Sprint/M7_WLS). Flash the Sprint TWRP version:
twrp-3.1.1-0-m7wls.img not twrp-3.1.1-0-m7.img

alray said:
quote me next time and I'll be notified, just like you did in this thread.
Click to expand...
Click to collapse
Hey again. Alray can I ask you for a little bit more help? I've tried every way to sim unlock i found but without any success. Last method I used was from this video: https://www.youtube.com/watch?v=e6hHUae1TMs but when I want to run Unlock helper it crashes. Have no idea what am I doing wrong...;(

alray said:
Since yours is also a Sprint HTC One, yes the same procedure should work.
quote me next time and I'll be notified, just like you did in this thread.
Don't forget that only Sprint roms and Sprint recovery will work on your phone (roms or recovery for the gsm/m7ul won't work). Make sure the custom rom you want to flash is compatible with the Sprint variant (it will be mentioned in the OP of the rom thread if it's compatible with Sprint/M7_WLS). Flash the Sprint TWRP version:
twrp-3.1.1-0-m7wls.img not twrp-3.1.1-0-m7.img
Click to expand...
Click to collapse
Hey so looks like I'm running into an issue when updating my firmware.
I'm getting this:
"Target didn't report max-download-size"
sending 'zip' (45578 KB)...
OKAY [2.807s]
writing 'zip' . . .
(bootloader) zip header checking . . .
(bootloader) zip info parsing . . .
FAILED (remote: 99 unknown fail)
finished. total tim: 3.067s
I've tried a few different versions of firmware and no luck.
I can just fastboot reboot bootloader and then reboot after that and I'm back to my normal stuff with no issues.
Also flashed twrp recovery without any issues.
Rom is still working, everything is still normal....
Thoughts?

Also wanted to add that I was able to update TWRP to 3.1 and flash ICE ROM 7.1.1 and gapps without any issues. So far running semi-stable.
Tried updating firmware with s-on after i re-locked my bootloader, but that did not work either. I was still getting some weird error so I unlocked my bootloader again and then was able to flash the nougat rom just fine. It's strange that it's working with such an older version of the firmware... oh well.
Will still hold out for any suggestions. I'm sure I will run into some issues soon with the firmware being that out-of-date. Signal issues, battery issues, etc.