Database Develop

[Q] HTC One Bricked?

HTC One International : MaximusHD 13.0, Android 4.3 Sense 5 , stock kernel , S-On
So,my HTC One restarted randomly,and it wouldn't turn on.After 30 minutes of button mashing,I managed to get it into bootloader.
All my efforts to unbrick it were unsuccessful.What I've tried so far was:
1)Since I couldn't enter custom recovery (TWRP 2.5 in my case),I tried to reflash it via fastboot,but it was unsuccessful.All it did was making bootloader freeze!
I even tried "fastboot boot recovery recovery.img",but that didn't work either
2)I also tried to format the device,but that also causes bootloader to freeze!
3)After that I decided to try relocking,and unlocking bootloader.I've managed to lock it,but I can't unlock it.It seems that whenever I try flashing anything bootloader just freezes!
4)Since I locked the bootloader,I decided to try installing RUU.Using the .exe RUU,I managed to get as far as restarting bootloader,after which It freezes. I manually restart the phone(power button + volume down).After that RUU proceeds to waiting for bootloader,where it stays for 5+ minutes,and gives me error 171(I always get this fu***** error)
Also,when I try flashing RUU.zip via fastboot,It causes bootloader to freeze,as well !
Can someone please help,I don't know what else to do....Any ideas on how to unbrick it are welcome,thanks in advance
P.S. - Warranty is out of the question,my carrier doesn't accept phones with tampered software...Is there any way to at least remove this sign,if I cant unbrick my phone?

Guys,does anybody have any ideas on what to do?
I'm kinda freaking out,as I don't know what to do :crying:

Try to s off abd then install any ruu
Sent from my HTC One using XDA Premium 4 mobile app

Thank you for your suggestion,but unfortunately I don't have adb access,it doesn't recognize my phone when it's in bootloader
Is there any workaround to this?
Also,does anybody have any other ideas on what to do?
Thanks in advance

filipjablan said:
Thank you for your suggestion,but unfortunately I don't have adb access,it doesn't recognize my phone when it's in bootloader
Is there any workaround to this?
Also,does anybody have any other ideas on what to do?
Thanks in advance
Click to expand...
Click to collapse
you can get into fastboot?
if so, can you try to do factory reset then flash the custom recovery
adb sideload the rom and install using the custom recovery

What is your wondrous version. If it is 8.1 then try to use 7
Sent from my HTC One using Tapatalk

[email protected] said:
you can get into fastboot?
if so, can you try to do factory reset then flash the custom recovery
adb sideload the rom and install using the custom recovery
Click to expand...
Click to collapse
Already tried that,but factory reset causes bootloader to freeze...I left it for an hour like that,and it was still frozen
Thanks for trying to help out,I appreciate it
BTW,the answer to taha198's question is 7

filipjablan said:
Already tried that,but factory reset causes bootloader to freeze...I left it for an hour like that,and it was still frozen
Thanks for trying to help out,I appreciate it
BTW,the answer to taha198's question is 7
Click to expand...
Click to collapse
try fastboot erase cache?

n1234d said:
try fastboot erase cache?
Click to expand...
Click to collapse
I tried it at least 10 times,but it simply isn't working
I also tried formatting & reflashing each partition(there are 6 in total),but fastboot won't let me erase them,let alone flash them
Also,I locked my bootloader,in order to install RUU,but that doesn't work either,as flashing,copying files & restarting causes bootloader to freeze!
In addition to that I can't unlock my bootloader,as bootloader freezes when I try flashing Unlock_Code.bin
So,all in all,I'm royally screwed

filipjablan said:
I tried it at least 10 times,but it simply isn't working
I also tried formatting & reflashing each partition(there are 6 in total),but fastboot won't let me erase them,let alone flash them
Also,I locked my bootloader,in order to install RUU,but that doesn't work either,as flashing,copying files & restarting causes bootloader to freeze!
In addition to that I can't unlock my bootloader,as bootloader freezes when I try flashing Unlock_Code.bin
So,all in all,I'm royally screwed
Click to expand...
Click to collapse
Wow. Lets see if anyone can come up with a solution. Don't lose hope
Was your bootloader unlocked when you tried to clear/flash the partitions?
And absolutely anything you flash freezes your bootloader?
You might want to try an RUU.exe instead of a zip.

17 3528432
n1234d said:
Wow. Lets see if anyone can come up with a solution. Don't lose hope
Was your bootloader unlocked when you tried to clear/flash the partitions?
And absolutely anything you flash freezes your bootloader?
You might want to try an RUU.exe instead of a zip.
Click to expand...
Click to collapse
I know,sucks to be me,right
Anyway,I tried clearing/flashing partition when bootloader was unlocked,and even after it was locked,but nothing seems to work
I also tried using both .zip & .exe RUU,but neither work - .exe always gives me error 171(I tried it on 3 different PC's),and .zip ones causes bootloader to freeze,as soon as it start flashing files
Is there any way to get around errors 170/171 on RUU.exe?

filipjablan said:
I know,sucks to be me,right
Anyway,I tried clearing/flashing partition when bootloader was unlocked,and even after it was locked,but nothing seems to work
I also tried using both .zip & .exe RUU,but neither work - .exe always gives me error 171(I tried it on 3 different PC's),and .zip ones causes bootloader to freeze,as soon as it start flashing files
Is there any way to get around errors 170/171 on RUU.exe?
Click to expand...
Click to collapse
Have a look here http://forum.xda-developers.com/showthread.php?p=46200901
and this http://androidforums.com/incredible-tips-tricks/161463-ruu-error-170-171-solution-windows-7-a.html

Thanks man,I appreciate your help
Anyway,I forgot to mention that orange LED never lights up,even if it's connected to charger or usb port,for a few hours...
I have a question for you - Could all of this be linked to a custom recovery failure,as I had TWRP 2.5 (touchscreen version)?Despite the fact that it worked well for me for 4 months,it is my belief that touchscreen versions of TWRP & CWM,aren't as reliable...
Can a recovery refusing to "stick" f*** up a phone?
Anyway,personal experience is the best teacher...24 hours ago,I was a complete noob that only knew how to unlock bootloader,flash custom recovery & install custom roms..I've come a far way in a short amount of time,at least something good will come out of this
P.S. - And no,I'm not putting blame on TWRP,doing so would be wrong,as they are doing great work - I'm only asking if such a thing is possible

Thanks for trying to help out,I appreciate it,but unfortunately this didn't work...Whatever I do,I still get 170/171 error.
Also,RUU.zip is out of the question,unfortunately,as fastboot can't to flash & copy files,all it manages to do is freeze my bootloader
Still,the fact that I can enter bootloader,and the fact that my PC recognizes it gives me some hope..Hopefully I'll figure something out (I doubt that's gonna happen,but I can at least hope

filipjablan said:
Thanks man,I appreciate your help
Anyway,I forgot to mention that orange LED never lights up,even if it's connected to charger or usb port,for a few hours...
I have a question for you - Could all of this be linked to a custom recovery failure,as I had TWRP 2.5 (touchscreen version)?Despite the fact that it worked well for me for 4 months,it is my belief that touchscreen versions of TWRP & CWM,aren't as reliable...
Can a recovery refusing to "stick" f*** up a phone?
Anyway,personal experience is the best teacher...24 hours ago,I was a complete noob that only knew how to unlock bootloader,flash custom recovery & install custom roms..I've come a far way in a short amount of time,at least something good will come out of this
P.S. - And no,I'm not putting blame on TWRP,doing so would be wrong,as they are doing great work - I'm only asking if such a thing is possible
Click to expand...
Click to collapse
filipjablan said:
Thanks for trying to help out,I appreciate it,but unfortunately this didn't work...Whatever I do,I still get 170/171 error.
Also,RUU.zip is out of the question,unfortunately,as fastboot can't to flash & copy files,all it manages to do is freeze my bootloader
Still,the fact that I can enter bootloader,and the fact that my PC recognizes it gives me some hope..Hopefully I'll figure something out (I doubt that's gonna happen,but I can at least hope
Click to expand...
Click to collapse
I think this could be a hardware fault then.. Maybe your flash memory is just toast, so anything that you flash freezes your phone, and it can't read any partitions either.. If you were s-off you could've tried reflashing the bootloader.. Maybe you could just take it to your carrier after getting it into that state where it takes "button mashing " to boot, and act like a noob.. They aren't great saints either , they'll just see that it doesn't boot, and issue you a replacement
Sent from my iPod touch using Tapatalk

Any ideas on how to f*** it up even more,so it won't even boot?That way the are more likely to exchange it...
If they see ***Tampered*** in bootloader,they will basically escort me to the closest door
Anyway,as hard as it is for me to accept it,I believe you are right - flash memory is probably dead,that's the only thing that explains it...I've been thinking about it since yesterday,and it makes sense,unfortunately
I appreciate for trying to help out,thanks man,I owe you a beer

Have you tried reformatting flash memory ? There's a guide how to do it. There's a good chance you have bad sectors and this can be fixed , gimme a moment to find you a guide.
Edit :
Here this should solve your problems ( I hope )
http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html?m=1
Edit ...
Crap for this to work you need working recovery , damn , sorry mate , there must be a solution somewhere , if you were only s-off you could've reflash the bootloader that could've fixed all of this ****.
Sent from my HTC One using XDA Premium 4 mobile app

filipjablan said:
Any ideas on how to f*** it up even more,so it won't even boot?That way the are more likely to exchange it...
If they see ***Tampered*** in bootloader,they will basically escort me to the closest door
Anyway,as hard as it is for me to accept it,I believe you are right - flash memory is probably dead,that's the only thing that explains it...I've been thinking about it since yesterday,and it makes sense,unfortunately
I appreciate for trying to help out,thanks man,I owe you a beer
Click to expand...
Click to collapse
what happens when you do a "fastboot getvar all" in bootloader? also freezes, or does it give you an output? (if you're going to post it remove IMEI and s/n)

filipjablan said:
Any ideas on how to f*** it up even more,so it won't even boot?That way the are more likely to exchange it...
If they see ***Tampered*** in bootloader,they will basically escort me to the closest door
Anyway,as hard as it is for me to accept it,I believe you are right - flash memory is probably dead,that's the only thing that explains it...I've been thinking about it since yesterday,and it makes sense,unfortunately
I appreciate for trying to help out,thanks man,I owe you a beer
Click to expand...
Click to collapse
Well, what happens when you just boot the phone? Does it get stuck at the boot screen? Boot the phone into the bootloader and keep it on for a night or sth, It'll probably discharge by morning, and you should be back at the button mashing phase Take it to them and say that you were clicking photos and you noticed the purple noise issue, and your phone started heating up, and then it just died. That's a three in one If there are customers around, make a ruckus, and he'll hopefully give you a new phone on the spot
BTW, I'm underage

nkk71 said:
what happens when you do a "fastboot getvar all" in bootloader? also freezes, or does it give you an output? (if you're going to post it remove IMEI and s/n)
Click to expand...
Click to collapse
C:\adt-bundle-windows-x86-20130917\sdk\platform-tools>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: 1.29.401.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 3685mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f188f379dbbfee373cd551f7bc62b8435
getvar:all FAILED (unknown status code)
finished. total time: 0.056s

[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] flash RUU...but no device.

Hi all,
Changed from Samsung S2 to HTC one and installed custom ROM. My kid pulled the USB cable in the middle of something and after that I was stuck in boot. Trying to flash an RUU I re-locked the phone and now I am stuck there. I really tried to find the answer in other threads and it feels I am close (to knowing either how to solve this or get to know it is impossible), but I am not quite there:
Situation:
Tampered-relocked-security warning (comes and goes strangely enough)
S-On
HBOOT 1.44
eMMC-boot
May 3, 2013
Fastboot USB
Problem: whatever I try to do, my PC says there is no device. I installed HTC sync manager but it can not find my phone. It was in USB debugging before the loop....and now I do not know what to do.
Any suggestions for not making 2014 my worst phone-starting year ever....?

cdresor said:
Hi all,
Changed from Samsung S2 to HTC one and installed custom ROM. My kid pulled the USB cable in the middle of something and after that I was stuck in boot. Trying to flash an RUU I re-locked the phone and now I am stuck there. I really tried to find the answer in other threads and it feels I am close (to knowing either how to solve this or get to know it is impossible), but I am not quite there:
Situation:
Tampered-relocked-security warning (comes and goes strangely enough)
S-On
HBOOT 1.44
eMMC-boot
May 3, 2013
Fastboot USB
Problem: whatever I try to do, my PC says there is no device. I installed HTC sync manager but it can not find my phone. It was in USB debugging before the loop....and now I do not know what to do.
Any suggestions for not making 2014 my worst phone-starting year ever....?
Click to expand...
Click to collapse
can you post results from
fastboot getvar all
minus your iemi and serial no
you run it from the bootloader screen you posted above

getvar
clsA said:
can you post results from
fastboot getvar all
minus your iemi and serial no
you run it from the bootloader screen you posted above
Click to expand...
Click to collapse
Thanks. First I got "no device", but I drained the battery (because nothing happened when plugging/unplugging the USB cable), reinstalled drivers on my PC and reconnected the HTC. I got security warning again but I guess it sees my phone, because getvar worked:
bootloader version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.14.3250.13
version-clpd: None
version-microp: None
version-main: 1.29.401.16
version-misc: PUT SHIP S-ON
serialno:
imei:
meid: 000000000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC_Y13
battery-status: low
battery-voltage: 3286 mV
partition-layout: Generic
security: on
build-mode: ship
boot-mode: fastboot
getvar: all FAILED (status read failed (too many links))
finished. Total time 5.188s

Similar position, help me too please
my device HTC 802d china telecom, am based in china, running 4.2.2 upgrade 4.3 available
my phone says
TAMPERED
RELOCKED
SECURITY WARNING - this comes and goes
Phone working well, htc sync manager work well
when i go to bootloader then fastboot, it says fastboot usb but fastboot or adb says no device
pc not detect my phone from bootloader, kindly help

sureshnv said:
my device HTC 802d china telecom, am based in china, running 4.2.2 upgrade 4.3 available
my phone says
TAMPERED
RELOCKED
SECURITY WARNING - this comes and goes
Phone working well, htc sync manager work well
when i go to bootloader then fastboot, it says fastboot usb but fastboot or adb says no device
pc not detect my phone from bootloader, kindly help
Click to expand...
Click to collapse
I will get back to you if I find out what was wrong. Right now though I dare not to touch my phone until I see which help I can get from this forum. My HTC Sync manager says I have no device, most commands say no device but still I got getvar info. So I do not quite understand all of this....but hopefully I will get there. Good luck!

cdresor said:
I will get back to you if I find out what was wrong. Right now though I dare not to touch my phone until I see which help I can get from this forum. My HTC Sync manager says I have no device, most commands say no device but still I got getvar info. So I do not quite understand all of this....but hopefully I will get there. Good luck!
Click to expand...
Click to collapse
yeah we can get you their - Uninstall HTC Sync manager but leave the drivers (it will ask during uninstall)
the date in the bootloader indicates Revone should work to s-off your phone as I can see your on hboot 1.44
Try to get s-off >> http://forum.xda-developers.com/showthread.php?t=2314582
while your reading Download this
http://www.htc1guru.com/dld/ruu-zip...0-01_release_318486_signed_2_4_decrypted-zip/
next step is this from @nkk71
Step 2: Flash your RUU.zip
Download your MID & CID compatible RUU.zip
Rename the downloaded file to ruu.zip (careful about ruu.zip.zip in Windows)
In bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE, the first one will report “failed flush again”, the second one will succeed.
fastboot reboot-bootloader
Click to expand...
Click to collapse

if you're having problems with revone, use the following rom: http://forum.xda-developers.com/showpost.php?p=48955645&postcount=250

clsA said:
yeah we can get you their - Uninstall HTC Sync manager but leave the drivers (it will ask during uninstall)
the date in the bootloader indicates Revone should work to s-off your phone as I can see your on hboot 1.44
Try to get s-off >> http://forum.xda-developers.com/showthread.php?t=2314582
while your reading Download this
http://www.htc1guru.com/dld/ruu-zip...0-01_release_318486_signed_2_4_decrypted-zip/
next step is this from @nkk71
Click to expand...
Click to collapse
Again, thanks for replying.
I uninstalled HTC Sync manager but it never asked about the drivers (I only got install/repair/uninstall) so everything was deleted. I reinstalled.
Nevertheless, trying to push revone I simply got the message "error:device not found". I guess /data/local/tmp/ is the correct dir for my device, or can this be different on different machines somehow?
I am still downloading the ROM, hoping for help.....d/l takes a looong time so don´t hurry

cdresor said:
Again, thanks for replying.
I uninstalled HTC Sync manager but it never asked about the drivers (I only got install/repair/uninstall) so everything was deleted. I reinstalled.
Nevertheless, trying to push s-off I simply got the message "error:device not found". I guess /data/local/tmp/ is the correct dir for my device, or can this be different on different machines somehow?
I am still downloading the ROM, hoping for help.....d/l takes a looong time so don´t hurry
Click to expand...
Click to collapse
you need to be booted into custom recovery when you push with adb

cdresor said:
Again, thanks for replying.
I uninstalled HTC Sync manager but it never asked about the drivers (I only got install/repair/uninstall) so everything was deleted. I reinstalled.
Nevertheless, trying to push revone I simply got the message "error:device not found". I guess /data/local/tmp/ is the correct dir for my device, or can this be different on different machines somehow?
I am still downloading the ROM, hoping for help.....d/l takes a looong time so don´t hurry
Click to expand...
Click to collapse
strange, i always install sync manager, then go back to Control Panel -> Uninstall -> HTC Sync Manager
HTC Drivers stay just fine.
You can use those:
HTCDriver_4.8.0.002.exe 15.1 MB
https://mega.co.nz/#!TAcGAJ7L!YdWM4AIji95b1ow8kVgagggOx5Yh7csRN5G0KJaCo6w
you have to get adb working; you can check by typing "adb devices" either in custom recovery or booted-up ROM (USB debugging enabled), it should show your device serial number.

nkk71 said:
if you're having problems with revone, use the following rom: http://forum.xda-developers.com/showpost.php?p=48955645&postcount=250
Click to expand...
Click to collapse
Sorry for being stupid but will the ROM make my HTC S-Off (as the heading implies) or work with the current S-ON?
I still don´t understand how I am to flash it to my device when everything I do (except getvar) says "device not found". But I will try and might get out of this mess a little bit smarter than I was before.
Thanks!

cdresor said:
Sorry for being stupid but will the ROM make my HTC S-Off (as the heading implies) or work with the current S-ON?
I still don´t understand how I am to flash it to my device when everything I do (except getvar) says "device not found". But I will try and might get out of this mess a little bit smarter than I was before.
Thanks!
Click to expand...
Click to collapse
I would flash the RUU and skip s-off for now till you get your phone working again. From what your saying you don't even have custom recovery any more ?

cdresor said:
Sorry for being stupid but will the ROM make my HTC S-Off (as the heading implies) or work with the current S-ON?
I still don´t understand how I am to flash it to my device when everything I do (except getvar) says "device not found". But I will try and might get out of this mess a little bit smarter than I was before.
Thanks!
Click to expand...
Click to collapse
1- No, the ROM will not make you S-Off, but it's proven to be very compatible with revone
2- you install that using custom recovery (CWM or TWRP)
3- you'll still have to use the revone commands as mentioned in their thread
4- adb vs fastboot:
"fastboot devices" <- works in bootloader screen ONLY (the white screen)
"adb devices" <- works in a booted up ROM (with USB debugging enabled) or in custom recovery (CWM or TWRP), it does NOT work in bootloader
---------- Post added at 04:42 PM ---------- Previous post was at 04:36 PM ----------
cdresor said:
Sorry for being stupid but will the ROM make my HTC S-Off (as the heading implies) or work with the current S-ON?
I still don´t understand how I am to flash it to my device when everything I do (except getvar) says "device not found". But I will try and might get out of this mess a little bit smarter than I was before.
Thanks!
Click to expand...
Click to collapse
clsA said:
I would flash the RUU and skip s-off for now till you get your phone working again. From what your saying you don't even have custom recovery any more ?
Click to expand...
Click to collapse
+1, disregard my previous post, and go with @clsA recommendation of flashing ruu, to get your phone back up and running.

clsA said:
I would flash the RUU and skip s-off for now till you get your phone working again. From what your saying you don't even have custom recovery any more ?
Click to expand...
Click to collapse
Unfortunately you are quite right. I guess there is something fishy with my drivers although getvar gets info from my phone. And although Windows does not show any phone, in device manager there is a "My HTC" which is said to run correctly. Sigh.
I will try to get in contact with my phone and flash a ROM.

cdresor said:
Unfortunately you are quite right. I guess there is something fishy with my drivers although getvar gets info from my phone. And although Windows does not show any phone, in device manager there is a "My HTC" which is said to run correctly. Sigh.
I will try to get in contact with my phone and flash a ROM.
Click to expand...
Click to collapse
just do the stuff in post 6 and skip s-off for now

clsA said:
just do the stuff in post 6 and skip s-off for now
Click to expand...
Click to collapse
Getting there, getting there.....
First I just got "error opening". Changed the long name to "1.zip" and it seemed to work. Finished with these lines though:
writing "zip".....
(bootloader) signature checking....
FAILED (remote: 12 signature verify fail)
And back to where I was before. Should I just retry (download again) or do you have any further advice?

cdresor said:
Getting there, getting there.....
First I just got "error opening". Changed the long name to "1.zip" and it seemed to work. Finished with these lines though:
writing "zip".....
(bootloader) signature checking....
FAILED (remote: 12 signature verify fail)
And back to where I was before. Should I just retry (download again) or do you have any further advice?
Click to expand...
Click to collapse
did you md5 check the file you already have ?

clsA said:
did you md5 check the file you already have ?
Click to expand...
Click to collapse
Hrm...I never understood how I check md5 on my computer so I figured it was faster to d/l it again. I am happy something happens between my computer and the phone though.....I see the light in the tunnel. Hopefully not the headlight on a freight train.

cdresor said:
Thanks. First I got "no device", but I drained the battery (because nothing happened when plugging/unplugging the USB cable), reinstalled drivers on my PC and reconnected the HTC. I got security warning again but I guess it sees my phone, because getvar worked:
bootloader version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.14.3250.13
version-clpd: None
version-microp: None
version-main: 1.29.401.16
version-misc: PUT SHIP S-ON
serialno:
imei:
meid: 000000000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC_Y13
battery-status: low
battery-voltage: 3286 mV
partition-layout: Generic
security: on
build-mode: ship
boot-mode: fastboot
getvar: all FAILED (status read failed (too many links))
finished. Total time 5.188s
Click to expand...
Click to collapse
cdresor said:
Hrm...I never understood how I check md5 on my computer so I figured it was faster to d/l it again. I am happy something happens between my computer and the phone though.....I see the light in the tunnel. Hopefully not the headlight on a freight train.
Click to expand...
Click to collapse
1- I'm assuming you TYPED that getvar ^^ above correct!?!?! (because of the "mistyped" stuff in it)... please confirm!!!! EDIT:: even better, do a "fastboot getvar all" again, and copy/paste output, not typed
2- can you open the ruu.zip and post the contents "android-info.txt" (I could download it and check myself, but that would just take another 1 and half hours)

cdresor said:
Hrm...I never understood how I check md5 on my computer so I figured it was faster to d/l it again. I am happy something happens between my computer and the phone though.....I see the light in the tunnel. Hopefully not the headlight on a freight train.
Click to expand...
Click to collapse
md5 app
all you do is copy the long code of the md5 and the app will take it from the clipboard .. simply browse to the file your checking and it will go

[Q] Help with boot loop on brand new HTC One

So I RMAd my last HTC One Google Play Edition for hardware issues and the new one arrived yesterday. I haven't sent the malfunctioning one back yet, thankfully. I still have a few days before it needs to be in the mail.
Before first boot, I unlocked the bootloader via htcdev. After initial boot, I entered in my google account info, then downloaded all available app and OTA updates (which put me at 4.4.2), etc. By then it was really late so I let it sit overnight with no SIM card in it yet. Today, I flashed CWM and made a nandroid backup, then pushed SuperSU 1.91 to root it. When I finally tried booting into OS again, it started with the boot loop. The desktop shows up for a few seconds then the device reboots. I can get into bootloader and fastboot, but since it's still S-On I have no way to do a proper RUU flash. I can get back into recovery by "fastboot erase cache" followed by "factory reset" from bootloader/hboot screen. The factory reset strangely loads the recovery (or maybe that's what it's supposed to do), but actually choosing recovery from bootloader still tries to boot OS and I'm back in the boot loop. I tried restoring the nandroid backup I made with CWM to no avail. Boot loop persists. I really don't know what else to try here and I'd rather not do the dance with google support again. Any suggestions?
Here's my current fastboot getvar:
$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: (Yes, this is showing as blank.)
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: x
(bootloader) imei: x
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4290mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.042s
(The first malfunctioning device is a touch screen issue, not anything like this. That phone is happily unlocked, S-Off and rooted until I prep it to send it back once the new device is functioning properly.)
Any successful suggestion will get lots of thanks and I'm not above tossing a few bucks of donation money out either.
Thanks in advance for any help you gurus can give.
-/djdead

djdead23 said:
So I RMAd my last HTC One Google Play Edition for hardware issues and the new one arrived yesterday. I haven't sent the malfunctioning one back yet, thankfully. I still have a few days before it needs to be in the mail.
Before first boot, I unlocked the bootloader via htcdev. After initial boot, I entered in my google account info, then downloaded all available app and OTA updates (which put me at 4.4.2), etc. By then it was really late so I let it sit overnight with no SIM card in it yet. Today, I flashed CWM and made a nandroid backup, then pushed SuperSU 1.91 to root it. When I finally tried booting into OS again, it started with the boot loop. The desktop shows up for a few seconds then the device reboots. I can get into bootloader and fastboot, but since it's still S-On I have no way to do a proper RUU flash. I can get back into recovery by "fastboot erase cache" followed by "factory reset" from bootloader/hboot screen. The factory reset strangely loads the recovery (or maybe that's what it's supposed to do), but actually choosing recovery from bootloader still tries to boot OS and I'm back in the boot loop. I tried restoring the nandroid backup I made with CWM to no avail. Boot loop persists. I really don't know what else to try here and I'd rather not do the dance with google support again. Any suggestions?
Here's my current fastboot getvar:
[...]
(The first malfunctioning device is a touch screen issue, not anything like this. That phone is happily unlocked, S-Off and rooted until I prep it to send it back once the new device is functioning properly.)
Any successful suggestion will get lots of thanks and I'm not above tossing a few bucks of donation money out either.
Thanks in advance for any help you gurus can give.
-/djdead
Click to expand...
Click to collapse
Yes, your phone is supposed to enter the recovery after factory reset in bootloader if you have a custom recovery like TWRP or CWM.
Maybe you want to make full wipe within the recovery(I wouldn't remember that you did it)... just wipe everything (including sdcard) except system.
If the bootloop still persists, try flashing a custom ROM... for example ARHD;
http://forum.xda-developers.com/showthread.php?t=2356654
Don't use the stock one... use the altered..
And if you managed to boot your phone -> Go instantaneously S OFF
If this doesn't work, or if you don't understand my explanation, just ask...
P.S.
Remember: only if you quote or mention me, I'll be notified and I'll be able to provide further help

First, thanks for your response. =)
LibertyMarine said:
Yes, your phone is supposed to enter the recovery after factory reset in bootloader if you have a custom recovery like TWRP or CWM.
Maybe you want to make full wipe within the recovery(I wouldn't remember that you did it)... just wipe everything (including sdcard) except system.
Click to expand...
Click to collapse
I did try formatting everything via custom recovery before I restored from my nandroid, even sdcard and system. I have also tried just wiping data and sdcard. No luck. I think I used TWRM, but may have been CWM. I've swapped them out a few times trying to get out of my boot loop. It's a brand new phone so there is no data on it that I care about yet. Is there some other way I should try wiping it? I've looked at most of the soft brick guides that have solutions but they all instruct you to get S-Off first, which I obviously can't do if the OS won't boot up for more than a few seconds. Rumrunner is what I used on my old HTC One with success, but haven't been able to try it yet.
LibertyMarine said:
If the bootloop still persists, try flashing a custom ROM... for example ARHD;
http://forum.xda-developers.com/showthread.php?t=2356654
Don't use the stock one... use the altered..
And if you managed to boot your phone -> Go instantaneously S OFF
Click to expand...
Click to collapse
ARHD says specifically that it requires S-Off to install. Are you suggesting I try it anyway without S-Off? =)
I'm currently downloading both the ARHD Google Edition 6.1 and the v51.0 from their blogspot site. Will have to try them after I get to work. I'll check here first when I get to the office, and will post any results I get, otherwise.
Thanks again!
-/djdead

djdead23 said:
First, thanks for your response. =)
I did try formatting everything via custom recovery before I restored from my nandroid, even sdcard and system. I have also tried just wiping data and sdcard. No luck. I think I used TWRM, but may have been CWM. I've swapped them out a few times trying to get out of my boot loop. It's a brand new phone so there is no data on it that I care about yet. Is there some other way I should try wiping it? I've looked at most of the soft brick guides that have solutions but they all instruct you to get S-Off first, which I obviously can't do if the OS won't boot up for more than a few seconds. Rumrunner is what I used on my old HTC One with success, but haven't been able to try it yet.
Click to expand...
Click to collapse
Ah ok.... maybe you have a corrupt data partition.. then this guide might help you:
http://android-revolution-hd.blogspot.ch/2013/10/fix-data-htc-one.html
As far as I know you don't need s off to do that...
This procedure will delete and reformat(not fakeformat - it will recreate the whole partition) your data partition. Just follow the guide carefully..
ARHD says specifically that it requires S-Off to install. Are you suggesting I try it anyway without S-Off? =)
I'm currently downloading both the ARHD Google Edition 6.1 and the v51.0 from their blogspot site. Will have to try them after I get to work. I'll check here first when I get to the office, and will post any results I get, otherwise.
Thanks again!
-/djdead
Click to expand...
Click to collapse
Sorry... didn't think about that. Yeah. then just install one of the previous versions that don't need s off...
but don't try it without s off... you'll get a even more nasty bootloop.. just don't it's a very very bad idea
good luck :good:

djdead23 said:
First, thanks for your response. =)
I did try formatting everything via custom recovery before I restored from my nandroid, even sdcard and system. I have also tried just wiping data and sdcard. No luck. I think I used TWRM, but may have been CWM. I've swapped them out a few times trying to get out of my boot loop. It's a brand new phone so there is no data on it that I care about yet. Is there some other way I should try wiping it? I've looked at most of the soft brick guides that have solutions but they all instruct you to get S-Off first, which I obviously can't do if the OS won't boot up for more than a few seconds. Rumrunner is what I used on my old HTC One with success, but haven't been able to try it yet.
ARHD says specifically that it requires S-Off to install. Are you suggesting I try it anyway without S-Off? =)
I'm currently downloading both the ARHD Google Edition 6.1 and the v51.0 from their blogspot site. Will have to try them after I get to work. I'll check here first when I get to the office, and will post any results I get, otherwise.
Thanks again!
-/djdead
Click to expand...
Click to collapse
You don't need S-OFF for ARHD! Only unlocked bootloader

Uxepro said:
You don't need S-OFF for ARHD! Only unlocked bootloader
Click to expand...
Click to collapse
Ok. I'm going to give 51.0 a shot without S-Off. Will post results in a bit.

LibertyMarine said:
Ah ok.... maybe you have a corrupt data partition.. then this guide might help you:
As far as I know you don't need s off to do that...
This procedure will delete and reformat(not fakeformat - it will recreate the whole partition) your data partition. Just follow the guide carefully..
good luck :good:
Click to expand...
Click to collapse
Ok. I'll try this before trying ARHD. Will post results in a bit...

djdead23 said:
Ok. I'll try this before trying ARHD. Will post results in a bit...
Click to expand...
Click to collapse
ok.. that thing with s off doesn't seem to be an issue anymore.. so just flash the latest version

LibertyMarine said:
ok.. that thing with s off doesn't seem to be an issue anymore.. so just flash the latest version
Click to expand...
Click to collapse
Ok. I flashed ARHD 51.0, and it's been sitting at the initial "START" for a good 30 seconds without rebooting. Gonna walk through the setup process...
*walks through setup process*
Ok. I have a desktop and it isn't boot looping.
MUCH THANKS!
Should it be possible to go back to stock KitKat now?
Ideally, I'd like to nandroid backup my current HTC One, return it to stock, S-On, locked, etc. Mail it back to google, and restore its nandroid backup to the new device.
-/djdead

djdead23 said:
Ok. I flashed ARHD 51.0, and it's been sitting at the initial "START" for a good 30 seconds without rebooting. Gonna walk through the setup process...
*walks through setup process*
Ok. I have a desktop and it isn't boot looping.
MUCH THANKS!
Should it be possible to go back to stock KitKat now?
Ideally, I'd like to nandroid backup my current HTC One, return it to stock, S-On, locked, etc. Mail it back to google, and restore its nandroid backup to the new device.
-/djdead
Click to expand...
Click to collapse
Yeah you can go back to stock KitKat with the following rom:
http://forum.xda-developers.com/showthread.php?t=2341395
It's not 100% stock... but if you'd like to go 100% stock you mist first go s off then flash a GPE RUU:
http://forum.xda-developers.com/showthread.php?t=2358781
After that you can lock (not relock) your bootloader following this guide
http://forum.xda-developers.com/showthread.php?t=2475914
And to go s on is not recommanded!!! Just don't go back s on...! And because you are GPE I don't know how it'd work... if it works differently.. or something similar.. sry..
But remember:
Going back S-ON with an altered bootloader will inevitably and instantaneously hard brick your device
Click to expand...
Click to collapse
Edit:
I don't understand why you want to return it to google

LibertyMarine said:
Yeah you can go back to stock KitKat with the following rom:
http://forum.xda-developers.com/showthread.php?t=2341395
It's not 100% stock... but if you'd like to go 100% stock you mist first go s off then flash a GPE RUU:
http://forum.xda-developers.com/showthread.php?t=2358781
After that you can lock (not relock) your bootloader following this guide
http://forum.xda-developers.com/showthread.php?t=2475914
And to go s on is not recommanded!!! Just don't go back s on...! And because you are GPE I don't know how it'd work... if it works differently.. or something similar.. sry..
Click to expand...
Click to collapse
Yes, I'm doing S-Off first thing before I make any other changes to it. That is my very next step as soon as I have a few minutes to devote to it.
LibertyMarine said:
Edit:
I don't understand why you want to return it to google
Click to expand...
Click to collapse
I have two HTC One devices. The old one has a touch screen issue, and I am in the process of RMAing it. The new device they sent me to replace it is the one I was having the boot loop issue with. The HTC One with the malfunctioning touchscreen is getting sent back to them, probably tomorrow, as soon as I get the replacement one working properly. I really didn't want to have to call google support again to tell them I was having issues with the new device they sent to replace the old one with. =)
Thanks given where possible. Will post status update later after S-Off attempt and hopefully return to stock kitkat.

djdead23 said:
Yes, I'm doing S-Off first thing before I make any other changes to it. That is my very next step as soon as I have a few minutes to devote to it.
Click to expand...
Click to collapse
Ok, good luck...
djdead23 said:
I have two HTC One devices. The old one has a touch screen issue, and I am in the process of RMAing it. The new device they sent me to replace it is the one I was having the boot loop issue with. The HTC One with the malfunctioning touchscreen is getting sent back to them, probably tomorrow, as soon as I get the replacement one working properly. I really didn't want to have to call google support again to tell them I was having issues with the new device they sent to replace the old one with. =)
Thanks given where possible. Will post status update later after S-Off attempt and hopefully return to stock kitkat.
Click to expand...
Click to collapse
yeah.. that would be annoying to call google a second time... ok I think RUU and then locking the bootloader is the best thing you can do... going back s on is just a risk that won't be compensated by the expectet results.. so my recommandation.. let it be and send it back with s off
Edit: Related to the the thanks... you are awesome... most users don't even show a sing of gratitude.. so don't worry mate !

LibertyMarine said:
Ok, good luck...
Click to expand...
Click to collapse
S-off achieved. Thanks LibertyMarine!
I think I'm good from here. =)
-/djdead

djdead23 said:
S-off achieved. Thanks LibertyMarine!
I think I'm good from here. =)
-/djdead
Click to expand...
Click to collapse
awesome! If you have any further questions don't hesitate to ask me !

LibertyMarine said:
awesome! If you have any further questions don't hesitate to ask me !
Click to expand...
Click to collapse
And we're back to 4.4.2 stock GPE rooted with S-Off. Loading all my apps and data from Titanium Backup now....
Thanks again!

Bricked Phone? PLEASE HELP!

My HTC One decided suddenly to not wake up this morning even though I had left it at 80 percent charge before I went to sleep. I put it to charge for 8 hours and when I came back, it still would not turn on. I can only get into the fastboot menu but my computer will not recognize my phone whatsoever- it says android 1.0 on my windows 7 computer. I know all of the correct drivers are installed because this is the same computer I used to root my phone. I am rooted with ARHD and TWRP. I have also tried holding the volume and power under a bright light and I can only get into the fastboot. Whenever I try to enter recovery, it gets stock on the "entering recovery" sign and when I try to boot the phone, it gets stuck on the splash screen.
I have not changed anything to my phone in the last month or so and this comes completely at random.
Any and all help will be greatly appreciated. Thanks!
EDIT: I can only get fastboot connectivity. Not ADB

xeron72548 said:
My HTC One decided suddenly to not wake up this morning even though I had left it at 80 percent charge before I went to sleep. I put it to charge for 8 hours and when I came back, it still would not turn on. I can only get into the fastboot menu but my computer will not recognize my phone whatsoever- it says android 1.0 on my windows 7 computer. I know all of the correct drivers are installed because this is the same computer I used to root my phone. I am rooted with ARHD and TWRP. I have also tried holding the volume and power under a bright light and I can only get into the fastboot. Whenever I try to enter recovery, it gets stock on the "entering recovery" sign and when I try to boot the phone, it gets stuck on the splash screen.
I have not changed anything to my phone in the last month or so and this comes completely at random.
Any and all help will be greatly appreciated. Thanks!
Click to expand...
Click to collapse
post your getvar all/bootloader information please

moha_moha20106 said:
post your getvar all/bootloader information please
Click to expand...
Click to collapse
Here it is:
(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.1540.17
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA34MW908198
(bootloader) imei: #################### (done intentionally)
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3716mV
(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
I can get fastboot connectivity but no ADB connectivity

xeron72548 said:
I can't get any of that because my phone isn't being picked up by my computer. I don't think it's a driver issue because this is the same computer i used to root the phone.
Click to expand...
Click to collapse
I've had the same problem
I could solve the problem by pushing the power button for few seconds until the buttom start blinking while I was trying to enter the recovery
probably this helps you

xeron72548 said:
I can't get any of that because my phone isn't being picked up by my computer. I don't think it's a driver issue because this is the same computer i used to root the phone.
Click to expand...
Click to collapse
can you check FAQ #2 in my guide if that's the problem.

try nkk71 method, it will resolve your problem
this is your correct RUU.exe

PS: @ OP, please edit and remove IMEI from your posts
---------- Post added at 02:17 AM ---------- Previous post was at 02:11 AM ----------
moha_moha20106 said:
this is your correct RUU.exe
Click to expand...
Click to collapse
I know you're eagerly trying to help, but you should take it easy a little more, before suggesting ruu's at every single point, and in every recent post.
going from 1.29.1540.17 to 4.19.1540.9, with S-On could really be a one way trip ... not necessarily a bad one, but just a one way trip.

moha_moha20106 said:
post your getvar all/bootloader information please
Click to expand...
Click to collapse
nkk71 said:
can you check FAQ #2 in my guide if that's the problem.
Click to expand...
Click to collapse
I can't do that because there is no driver not installed popup. When not in fastboot mode (just in the bootloader), the phone doesn't show up as anything in device manager

nkk71 said:
PS: @ OP, please edit and remove IMEI from your posts
---------- Post added at 02:17 AM ---------- Previous post was at 02:11 AM ----------
I know you're eagerly trying to help, but you should take it easy a little more, before suggesting ruu's at every single point, and in every recent post.
going from 1.29.1540.17 to 4.19.1540.9, with S-On could really be a one way trip ... not necessarily a bad one, but just a one way trip.
Click to expand...
Click to collapse
i know what you mean dear, but there's no RUU.exe between 1.29.1540.17 and 4.19.1540.9 i was found, so i suggest this one to back to stock after use your FAQ#2 method
with my respect, i learned more from you

xeron72548 said:
I can't do that because there is no driver not installed popup. When not in fastboot mode (just in the bootloader), the phone doesn't show up as anything in device manager
Click to expand...
Click to collapse
forget the pop-up!! check Windows Device Manager
your phone has 3 options:
1- bootloader (where you do fastboot commands)
2- custom recovery (TWRP or CWM), (where you can do adb commands)
3- booted ROM, if USB debugging is enabled you can use adb commands
in all three modes, the drivers "need to install", if they dont, you need to manually select them

nkk71 said:
forget the pop-up!! check Windows Device Manager
your phone has 3 options:
1- bootloader (where you do fastboot commands)
2- custom recovery (TWRP or CWM), (where you can do adb commands)
3- booted ROM, if USB debugging is enabled you can use adb commands
in all three modes, the drivers "need to install", if they dont, you need to manually select them
Click to expand...
Click to collapse
I can't get into my recovery. It freezes on the "entering recovery" screen every time. And for number 3, i can't even boot up my phone. I know this might be a bit unorthodox, but would you mind doing a teamviewer session with me?
Also, my phone DOES NOT show up in device manager unless it is in fastboot

xeron72548 said:
I can't get into my recovery. It freezes on the "entering recovery" screen every time. And for number 3, i can't even boot up my phone. I know this might be a bit unorthodox, but would you mind doing a teamviewer session with me?
Click to expand...
Click to collapse
Sorry, just turned off my pc and going to bed soon (it's almost 3am here, and I have to go to work in 4 hours)
Have you tried downloading the recovery again, make sure md5 is correct!! And don't forget to: fastboot erase cache
If that doesn't work, we can do teamviewer tomorrow.
Sorry, too late for me.
Sent from my HTC One using Tapatalk
---------- Post added at 02:49 AM ---------- Previous post was at 02:43 AM ----------
xeron72548 said:
I can't get into my recovery. It freezes on the "entering recovery" screen every time. And for number 3, i can't even boot up my phone. I know this might be a bit unorthodox, but would you mind doing a teamviewer session with me?
Also, my phone DOES NOT show up in device manager unless it is in fastboot
Click to expand...
Click to collapse
U know what, send me teamviewer Id and pass on PM... Booting up, but not more than 20 minutes, okay?
Sent from my HTC One using Tapatalk
---------- Post added at 02:58 AM ---------- Previous post was at 02:49 AM ----------
xeron72548 said:
I can't get into my recovery. It freezes on the "entering recovery" screen every time. And for number 3, i can't even boot up my phone. I know this might be a bit unorthodox, but would you mind doing a teamviewer session with me?
Also, my phone DOES NOT show up in device manager unless it is in fastboot
Click to expand...
Click to collapse
waiting...

moha_moha20106 said:
try nkk71 method, it will resolve your problem
this is your correct RUU.exe
Click to expand...
Click to collapse
Hey. I'm really thinking of using the RUU but the radio on the RUU you gave me doesn't match the one that is on my phone. Would this be a problem?

xeron72548 said:
Hey. I'm really thinking of using the RUU but the radio on the RUU you gave me doesn't match the one that is on my phone. Would this be a problem?
Click to expand...
Click to collapse
no problem for that

moha_moha20106 said:
no problem for that
Click to expand...
Click to collapse
For some reason the download speed is extremely slow. About 50kbs
Is this normal?

xeron72548 said:
For some reason the download speed is extremely slow. About 50kbs
Is this normal?
Click to expand...
Click to collapse
maybe you far from server , so the speed is slow
be patient

moha_moha20106 said:
maybe you far from server , so the speed is slow
be patient
Click to expand...
Click to collapse
I tried running the RUU and it said it was the wrong RUU. Is there another one that I should download?

xeron72548 said:
I tried running the RUU and it said it was the wrong RUU. Is there another one that I should download?
Click to expand...
Click to collapse
Also, my bootloader used to say this but now there is nothing after the version-main. It's blank
(bootloader) version-main: 1.29.1540.17

xeron72548 said:
Also, my bootloader used to say this but now there is nothing after the version-main. It's blank
(bootloader) version-main: 1.29.1540.17
Click to expand...
Click to collapse
does your phone S-off ?
what's your HBoot ver. ?

moha_moha20106 said:
does your phone S-off ?
what's your HBoot ver. ?
Click to expand...
Click to collapse
My phone is s-on and my bootloader version (version-main) is blank whenever I do getvar all