Database Develop

Please help. Phone stuck in purgatory [Resolved]

Okay, so being the wise person that I am, I decided that it would be a good idea to get the 4.2.2 sense update a few days/weeks before my carrier (Rogers) pushes it. I'll write it step by step, in case anyone can help me
- I started by making an ADB Backup, rooting the phone, and installing twrp recovery. No issues there
- When the phone started back up, I tried to restore my data, but the adb backup kept getting stuck on "com.Android.contacts" or something similar, so I decided I might as well try getting S-Off so I could change CID and get the 4.2.2 update.
- I used Revone, but it kept failing (error code -1). I posted in that thread about it, but I decided that in the mean time, I would just factory reset my phone.
I stupidly clicked "format" in twrp!
Now, my phone is on twrp with no OS. I tried downloading the rogers rom from HTC Dev, but it was a Zip file, and it won't install. I restarted the phone, and now I can't push anything to it. It says "error: device not found" when I try push the European 1.28 RUU (which I'm not sure if that would even work, because of CID/MID differences since the phone isn't S-Off.
Any help would be greatly appreciated :crying:

Okay, So I finally got the European RUU to push to the phone, only to realize that it's a ".exe" that can't be flashed from twrp. I have no access to a PC

WhatsAUsername said:
Okay, So I finally got the European RUU to push to the phone, only to realize that it's a ".exe" that can't be flashed from twrp. I have no access to a PC
Click to expand...
Click to collapse
Just flash any stable ROM in the meantime so you can at least boot the phone. Download ARHD, push the zip to your phone, and flash that.

I really don't understand all these people changing CIDs to force updates, especially when they go back to s-on afterward. You're locking your phone into a potentially problematic configuration. I helped another guy this morning who did it and then couldn't boot up but couldn't fix anything because he went back to s-on and locked bootloader.
If you want 4.2.2, do it the right way: S-off, flash firmware, flash rom. If you want stock, there are stock roms. All of this can be done on a Mac.

iElvis said:
I really don't understand all these people changing CIDs to force updates, especially when they go back to s-on afterward. You're locking your phone into a potentially problematic configuration. I helped another guy this morning who did it and then couldn't boot up but couldn't fix anything because he went back to s-on and locked bootloader.
If you want 4.2.2, do it the right way: S-off, flash firmware, flash rom. If you want stock, there are stock roms. All of this can be done on a Mac.
Click to expand...
Click to collapse
Well, I flashed CM 10.1, and finally managed to get S-Off. Now my issue is trying to go back to stock HTC Firmware. I can only get the RUU, which obviously doesn't work on Mac. Even If could extract the Zip, I have twrp recovery. How would I go back to a stock recovery that would allow me to get the OTA? I'm really upset about this whole thing. I mean, come on. HTC should've provided a Mac utility that allows users to go back to stock completely. I understand that they give you warnings about doing this kind of stuff, but I should be able to play around with my device and still be able to get it back to a functional factory state. I got iOS 7, and it was incredibly easy to go back. I've upgraded my Blackberry Z10 a 100 times with firmware from all over the world with no issues. I've also never had to deal with this S-crap stuff on my Nexus 4. It's just frustrating for end users.
Anyways, rant aside, would you happen to know how I can go back to a full factory state? I'm on CM 10.1 right now with twrp recovery.

WhatsAUsername said:
Well, I flashed CM 10.1, and finally managed to get S-Off. Now my issue is trying to go back to stock HTC Firmware. I can only get the RUU, which obviously doesn't work on Mac. Even If could extract the Zip, I have twrp recovery. How would I go back to a stock recovery that would allow me to get the OTA? I'm really upset about this whole thing. I mean, come on. HTC should've provided a Mac utility that allows users to go back to stock completely. I understand that they give you warnings about doing this kind of stuff, but I should be able to play around with my device and still be able to get it back to a functional factory state. I got iOS 7, and it was incredibly easy to go back. I've upgraded my Blackberry Z10 a 100 times with firmware from all over the world with no issues. I've also never had to deal with this S-crap stuff on my Nexus 4. It's just frustrating for end users.
Anyways, rant aside, would you happen to know how I can go back to a full factory state? I'm on CM 10.1 right now with twrp recovery.
Click to expand...
Click to collapse
Without a PC to run the RUU, I'm not sure. You can flash stuff, but if you want to be out of the box stock, you need a RUU.

I finally managed to get my phone to work. In case anyone comes across this, I'll write down what I did.
I had too many problems to list. From not being able to access adb on the phone, to the phone's memory being partitioned incorrectly, to the point where even a recovery like twrp couldn't format or access it in order to flash anything ("Unable to mount internal storage").
The solution to all problems (and if you're a Mac user like I am, this is disheartening), is that you'll need to run RUU on a PC. When doing this, you'll likely run into a few error messages.
Error 170: Make sure the device is in fastboot mode before plugging it in (hold power and volume down on boot, and select fastboot with the power button). You can make sure that the computer can see it by going to your device manager in windows, and make sure that it says "My HTC" under "Android Device." If it has a cryptic name with an exclamation mark, or you can't see it by using "fastboot devices" command, you'll continue to get that error.
Error 171: This error kept occuring when the computer could no longer see the phone after the process had already begun. The reasons this happens are many (ie your USB wire or drive might be faulty), but to me, it was because the phone was not going back to the bootloader on its own, and the computer eventually gave up. To solve this, start RUU.exe and WAIT BESIDE IT. You will come across 2 points where it says waiting for bootloader. Have your computer's device manager open, and hold the phone's power button until you see that the "Android Device" or "My HTC" disappears and reappears. RUU should continue when that happens. Again, you will have to do this twice! If you don't, RUU gives up on the phone as it does not go into the bootloader by itself, and will eventually give you an error.
For anyone going through this, just realize that as long as you can get into the bootloader, there's always a way to get it to work. At times, I thought my phone was completely bricked, but no matter what issue you have (including unable to access the phone's internal memory), you can always solve it if you can get into the bootloader. With that said, this process will erase everything on your phone, unfortunately. Everything is done at your own risk, so please don't blame those who are trying to help you. Good luck, and remember to always post your solution online, if you start a topic discussing the issue. I came across many people with the same issue who never came back with their solution!

Edit the title to solved

Not that it has happened to me but I think you could have just sideloaded a custom Rom from twrp and flashed that.

a box of kittens said:
Edit the title to solved
Click to expand...
Click to collapse
I tried, but I'm unable to do it. Due to the low post count, perhaps? :S
godutch said:
Not that it has happened to me but I think you could have just sideloaded a custom Rom from twrp and flashed that.
Click to expand...
Click to collapse
That was one of the first things I tried. It kept coming back with "unable to mount internal storage" or something like that, as I noted earlier. It was really weird, I couldn't format, mount, or do anything to my storage with tarp, and I couldn't get adb to see the phone. A lot of people have the issue with the One X, but I couldn't find a solution anywhere. I think what made the whole thing trickier than it needed to be is the fact that I changed my CID/MID, and in that guide, it is explained that you have to reboot the phone yourself in RUU, but I didn't realize not doing so would result in errors. I kept thinking it was because my device wasn't being seen in adv, so I was trying to get it to boot into any ROM for that to happen, and the inability to flash anything due to the internal storage error really complicated things. It's good to know that even this can be resolved, as I had all but convinced myself that I was dealing with a brick. I hope anyone coming across this issue in the future can benefit from my ordeal.

WhatsAUsername said:
I tried, but I'm unable to do it. Due to the low post count, perhaps? :S
Click to expand...
Click to collapse
Click edit on the OP, then Go Advanced. You should be able to edit the title at the top.

iElvis said:
Click edit on the OP, then Go Advanced. You should be able to edit the title at the top.
Click to expand...
Click to collapse
Done. Thanks!

WhatsAUsername said:
That was one of the first things I tried. It kept coming back with "unable to mount internal storage" or something like that
Click to expand...
Click to collapse
That's normal since android 4.1 because the sd card is not a fat partition anymore, did you follow this guide?: http://forum.xda-developers.com/showthread.php?t=2325853

[Q] Tried to get my One back to Stock, gone wrong somehwere

Hi, recently the screen broke on my 2 week old HTC One.
Amazon were kind enough to send me a new one, but I had modded the hell out of the first one (using various online tutorials to root and then ROM it), and now have the need to return it.
So I followed various tutorials to try and restore it back to 100% stock. (Didn't bother making it "Locked" rather than "Unlocked").
What I did was I used the HTC One All-In-One Toolkit, and "relocked bootloader". I then tried to flash the RUU, all went well, but when I try to start it up after, it gives a blank black screen. However, after giving it a while, holding the power button, or pressing the back button sometimes results in a vibration, so I'm presuming that it is starting, but not displaying anything. I was hoping that my phone would come up in windows so I could re-flash twrp and flash Sense that way, but it does not appear.
I tried factory resetting in this state, but when I try boot it up after that, a logo comes up which is a phone, with 2 green arrows forming a circle inside it, then a green arrow pointing down inside that.
Also, flashing twrp.img seems to go well, but when select "recovery", nothing happens, it just seems to boot up normally.
I am now at a loss of ideas, as this process was suggested by all the sources I could find, and it works perfectly for them, see no reason for it not to for me.
If anyone has any idea how to fix this, please, please respond as quickly as possible, it has to be with Amazon by the 4th, and I have no clue what to do!
Thanks,
-Accudio

yeah i got the point here, just one question, are you S-OFF or not? if yes, which is you bootloader?

matt95 said:
yeah i got the point here, just one question, are you S-OFF or not? if yes, which is you bootloader?
Click to expand...
Click to collapse
No, I'm S-ON, when I first did it I was a bit of a noob, and none of the tutorials I followed said anything about S-ON/S-OFF. Only just found out about it when researching how to put it back. :/

You can't access recovery because your phone is locked, so first off you need to unlock again your phone

matt95 said:
You can't access recovery because your phone is locked, so first off you need to unlock again your phone
Click to expand...
Click to collapse
Gotta go now, but well do when I next can. Using the "Unlock Bootloader" tool on the HTC Dev website yeah?

Accudio said:
Gotta go now, but well do when I next can. Using the "Unlock Bootloader" tool on the HTC Dev website yeah?
Click to expand...
Click to collapse
Yeah, however you can use the previous Unlockcode.bin that you used to unlock it the first time...

matt95 said:
Yeah, however you can use the previous Unlockcode.bin that you used to unlock it the first time...
Click to expand...
Click to collapse
OK, I have now unlocked it, I'd flash TWRP now yes?
EDIT: Now flashed TWRP, it's working fine, but how can I transfer the ROM zip across without having a version of android that works?

Accudio said:
OK, I have now unlocked it, I'd flash TWRP now yes?
EDIT: Now flashed TWRP, it's working fine, but how can I transfer the ROM zip across without having a version of android that works?
Click to expand...
Click to collapse
adb commands work in recovery too.
either use "adp push rom.zip /sdcard/" or use the sideload method

Thanks a lot guys, you've been a great help! 2 more questions for you if you don't mind:
1. The ROM I found doesn't seem to work properly, so have you got any ideas of ROMs of Sense 5, no root, so it will appear to amazon that it is stock, even if it isn't exactly, or do you know where I can get an RUU and how to flash it to get my phone back to exactly stock?
2. This won't be a big deal, but how could I achieve S-OFF to revert my HTC recovery to say "Locked" rather than "Tampered" and "Relocked"
If they aren't possible, no big deal, just would be nice if I can. Again, thanks a ton, you've saved my neck! xD
EDIT: I am downloading a different ROM to try, so hopefully that will work better.

Accudio said:
Thanks a lot guys, you've been a great help! 2 more questions for you if you don't mind:
1. The ROM I found doesn't seem to work properly, so have you got any ideas of ROMs of Sense 5, no root, so it will appear to amazon that it is stock, even if it isn't exactly, or do you know where I can get an RUU and how to flash it to get my phone back to exactly stock?
2. This won't be a big deal, but how could I achieve S-OFF to revert my HTC recovery to say "Locked" rather than "Tampered" and "Relocked"
If they aren't possible, no big deal, just would be nice if I can. Again, thanks a ton, you've saved my neck! xD
Click to expand...
Click to collapse
1. Just download a stock odexed rom from the development section. There are many to choose from.
OR
Pick a RUU from here. http://forum.xda-developers.com/showthread.php?p=39588860
2. Use this link to do that. Then read the instructions on how to reset the flags.
Did amazon really replace your broken phone for free? Thats what I call customer service. Too bad I bought mine from ATT.
THIRD OPTION:
Download http://forum.xda-developers.com/showthread.php?t=2353083
And remove supersu.apk from the zip file before you flash it.

aooga said:
1. Just download a stock odexed rom from the development section. There are many to choose from.
2. Use this link to do that. Then read the instructions on how to reset the flags.
Did amazon really replace your broken phone for free? Thats what I call customer service. Too bad I bought mine from ATT.
Click to expand...
Click to collapse
Yeah, I dropped it onto my carpet and the screen cracked pretty majorly, so I contacted HTC pretty annoyed (as you can expect), and they said that I must have had a dodgy model for it to have broken so easily. Amazon was reluctant but because I had HTC's word they sent me a free replacement.

Accudio said:
Yeah, I dropped it onto my carpet and the screen cracked pretty majorly, so I contacted HTC pretty annoyed (as you can expect), and they said that I must have had a dodgy model for it to have broken so easily. Amazon was reluctant but because I had HTC's word they sent me a free replacement.
Click to expand...
Click to collapse
Wow. thats nice of them. Read my previous post to answer your questions. I added another option.

aooga said:
1. Just download a stock odexed rom from the development section. There are many to choose from.
OR
Pick a RUU from here. http://forum.xda-developers.com/showthread.php?p=39588860
2. Use this link to do that. Then read the instructions on how to reset the flags.
Did amazon really replace your broken phone for free? Thats what I call customer service. Too bad I bought mine from ATT.
THIRD OPTION:
Download http://forum.xda-developers.com/showthread.php?t=2353083
And remove supersu.apk from the zip file before you flash it.
Click to expand...
Click to collapse
I have HBOOT version 1.54, so as the Revone thread says I cannot use that. Is there any other way or will I just not be able to do it? Had a quick look and couldn't find anything.

Accudio said:
I have HBOOT version 1.54, so as the Revone thread says I cannot use that. Is there any other way or will I just not be able to do it? Had a quick look and couldn't find anything.
Click to expand...
Click to collapse
ohhh..that might be a problem. How did you manage to get on hboot 1.54? I don't think there is a S-off method for that yet. Do you still have the unlockcode.bin from when you unlocked it the first time?

aooga said:
ohhh..that might be a problem. How did you manage to get on hboot 1.54? I don't think there is a S-off method for that yet. Do you still have the unlockcode.bin from when you unlocked it the first time?
Click to expand...
Click to collapse
I don't know, if I remember correctly it was actually on that when I got it, not certain though. I do have my first unlockcode.bin saved.

Accudio said:
I don't know, if I remember correctly it was actually on that when I got it, not certain though. I do have my first unlockcode.bin saved.
Click to expand...
Click to collapse
You should be able to unlock your bootloader again with the unlockcode.
If I'm not mistaken, in order to flash a RUU you need to:
- Flash stock recovery.img through bootloader+fastboot
- Flash stock boot.img through bootloader+fastboot
RUU should flash now whether bootloader is locked, unlocked or relocked.

Accudio said:
I don't know, if I remember correctly it was actually on that when I got it, not certain though. I do have my first unlockcode.bin saved.
Click to expand...
Click to collapse
as long as you used that file to unlock this phone, then it will work.

Ok, I'm getting an error saying:
"Unfortunately, HTC Sense has stopped."
and also
"Unfortunately Contacts Storage has stopped."
I had the Contacts srtorage one with my old S2, which I fixed by clearing data of contacts storage, but the one about HTC sense stops anything from working.

aooga said:
1. Just download a stock odexed rom from the development section. There are many to choose from.
OR
Pick a RUU from here. http://forum.xda-developers.com/showthread.php?p=39588860
2. Use this link to do that. Then read the instructions on how to reset the flags.
Did amazon really replace your broken phone for free? Thats what I call customer service. Too bad I bought mine from ATT.
THIRD OPTION:
Download http://forum.xda-developers.com/showthread.php?t=2353083
And remove supersu.apk from the zip file before you flash it.
Click to expand...
Click to collapse
Sorry if I'm being a bit of a noob, how would I remove superuser.apk?

Accudio said:
Sorry if I'm being a bit of a noob, how would I remove superuser.apk?
Click to expand...
Click to collapse
if you have a pc, before you push the rom to your phone, open the zip file and delete the apk in /system/app/supersu.apk

[Q] Changing CID back to original

Im sending my phone back to HTC for repair.
I have two questions...
Would they look at the CID?
Can I change it back to my original CID if I've already installed a RUU that doesn't allow my CID? (sounds like a dumb question)

stanny2k said:
Im sending my phone back to HTC for repair.
I have two questions...
Would they look at the CID?
Can I change it back to my original CID if I've already installed a RUU that doesn't allow my CID? (sounds like a dumb question)
Click to expand...
Click to collapse
I read your other post http://forum.xda-developers.com/showthread.php?t=2599739 and probably a lot of others too, no answer because I have none.
So here's a small summary:
1- you're S-ON again, so changing CID cannot be done
2- you have a .401. software version which means it cannot be CID H3G, so HTC__001 is correct for that software version
3- you've removed TAMPERED and set to LOCKED (not relocked)
4- I don't know how the service center will react, and whether they would bother checking CID, etc. (from what I've seen the UK centers are quite lenient)
If you really want to go back fully to your carrier version, and "out of the box", you can take a look at my guide: http://forum.xda-developers.com/showthread.php?t=2541082
but that means starting the procedure all the way from the start again, ie
-- unlocking (and you're gonna have to do that with HTCdev)
-- s-off using rumrunner.
then follow the rest of the guide.
Don't know if it's worth the hassle; but if you need help with it, post back there.
cheers

nkk71 said:
I read your other post http://forum.xda-developers.com/showthread.php?t=2599739 and probably a lot of others too, no answer because I have none.
So here's a small summary:
1- you're S-ON again, so changing CID cannot be done
2- you have a .401. software version which means it cannot be CID H3G, so HTC__001 is correct for that software version
3- you've removed TAMPERED and set to LOCKED (not relocked)
4- I don't know how the service center will react, and whether they would bother checking CID, etc. (from what I've seen the UK centers are quite lenient)
If you really want to go back fully to your carrier version, and "out of the box", you can take a look at my guide: http://forum.xda-developers.com/showthread.php?t=2541082
but that means starting the procedure all the way from the start again, ie
-- unlocking (and you're gonna have to do that with HTCdev)
-- s-off using rumrunner.
then follow the rest of the guide.
Don't know if it's worth the hassle; but if you need help with it, post back there.
cheers
Click to expand...
Click to collapse
Thanks for taking the time in responding mate. The issue I have is that I can't get a stock RUU for my H3G CID... It just doesn't seem to exist anywhere... I think a few other people are asking the same question... Which is why I've had to change my CID to HTC__001..

stanny2k said:
Thanks for taking the time in responding mate. The issue I have is that I can't get a stock RUU for my H3G CID... It just doesn't seem to exist anywhere... I think a few other people are asking the same question... Which is why I've had to change my CID to HTC__001..
Click to expand...
Click to collapse
Well if you checked my guide, you'd see that method 3 (CWM Backup), works, and there is a H3G__001 backup out there; as a matter of fact, the example I used was for H3G__001.

nkk71 said:
Well if you checked my guide, you'd see that method 3 (CWM Backup), works, and there is a H3G__001 backup out there; as a matter of fact, the example I used was for H3G__001.
Click to expand...
Click to collapse
In that case, I take that back I'm going to follow your guide again tonight.
The last thing I want is for HTC to say No, they cant do my repair cause I've messed about with my phone...
Oh, and have a "thanks"

stanny2k said:
In that case, I take that back I'm going to follow your guide again tonight.
The last thing I want is for HTC to say No, they cant do my repair cause I've messed about with my phone...
Oh, and have a "thanks"
Click to expand...
Click to collapse
I'm going to recommend this CWM recovery, just cause the newer versions are taking close to an hour to backup/restore:
recovery-clockwork-touch-6.0.3.2-m7--v2.img 7.2 MB
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
MD: 1c6afb14db3f305b0ad7d85d5af80bef
Also, please follow the instruction properly, no jumping, skipping or adding steps
The only slightly tricky part (as mentioned), is in Step 6, where when the phone reboots to "stock recovery" it could hang somewhere between 25% to 50%, and you have to manually reboot, and (possibly) again towards the end, and you have to reboot manually again.
This is a known side effect because stock recovery is not exactly the same as your version, but it's not a problem.
After the FIRST (and only the FIRST) OTA update, should you go back S-On, because hboot 1.55 has a patch that will force TAMPERED to come back if you go from s-off to s-on.
NB: after the first OTA, you're phone will be 100% stock.
If you have any trouble (hopefully not), post back in my thread, as I get instant notifications on that (and if i'm still awake, i'm 2 hours ahead), and I'll try to help out.
Cheers.
---------- Post added at 06:50 PM ---------- Previous post was at 06:48 PM ----------
stanny2k said:
Oh, and have a "thanks"
Click to expand...
Click to collapse
Thanks, I like those

nkk71 said:
I'm going to recommend this CWM recovery, just cause the newer versions are taking close to an hour to backup/restore:
recovery-clockwork-touch-6.0.3.2-m7--v2.img 7.2 MB
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
MD: 1c6afb14db3f305b0ad7d85d5af80bef
Click to expand...
Click to collapse
Ok, I'll grab this!
nkk71 said:
Also, please follow the instruction properly, no jumping, skipping or adding steps
Click to expand...
Click to collapse
Will do! Don't worry, word for word!
nkk71 said:
The only slightly tricky part (as mentioned), is in Step 6, where when the phone reboots to "stock recovery" it could hang somewhere between 25% to 50%, and you have to manually reboot, and (possibly) again towards the end, and you have to reboot manually again.
This is a known side effect because stock recovery is not exactly the same as your version, but it's not a problem.
Click to expand...
Click to collapse
Noted.
nkk71 said:
After the FIRST (and only the FIRST) OTA update, should you go back S-On, because hboot 1.55 has a patch that will force TAMPERED to come back if you go from s-off to s-on.
NB: after the first OTA, you're phone will be 100% stock.
Click to expand...
Click to collapse
When you say "should you go back S-On" do I let the first OTA update install, then manually go back to S-ON, then let the other updates install once I've got S-ON back?
nkk71 said:
If you have any trouble (hopefully not), post back in my thread, as I get instant notifications on that (and if i'm still awake, i'm 2 hours ahead), and I'll try to help out.
Cheers.
Click to expand...
Click to collapse
Appreciate it, thank you

stanny2k said:
When you say "should you go back S-On" do I let the first OTA update install, then manually go back to S-ON, then let the other updates install once I've got S-ON back?
Click to expand...
Click to collapse
yep, exactly, after the 1st OTA, your phone will be 100% "out-of-the-box"; once the OTA updates successfully it will mean
1- your entire firmware was updated (hboot, recovery, kernel, radio, etc)
2- your ROM will also be updated, proving everything is 100%
otherwise, the OTA would not be able to complete.
Now due to a patch in later hboots (in particular 1.55 as far as i know), going from s-off to s-on, will (after a few reboots) result in "tamper detected - rebooting" and TAMPERED is back.
so in summary, if you really need to go S-On, you do so after first successful OTA (using the command mentioned in my guide), and then you can take any OTAs you like.
hope that makes sense

Perfect sense!
I'll have a bash at this tonight! Thanks a lot

Well, that was an eventful evening
Followed your guide to the letter. Everything went ok apart from a few things..
Pushing files via adb whilst in recovery causes me no end of issues... I kept getting no device found, luckily I was able to boot up and transfer the files manually.
I then flashed the wrong stock recovery (recovery 1.28.401.7.img) so I had to unlock the bootloader again to flash a different one, thankfully the one I did flash (recovery 2.24.771.3 - TRE.img), which matched the first OTA update, everything installed fine after that
Thanks a lot mate. I'll happy to send my device away for repair with no worries now.
Regards, Ryan

stanny2k said:
Well, that was an eventful evening
Followed your guide to the letter. Everything went ok apart from a few things..
Pushing files via adb whilst in recovery causes me no end of issues... I kept getting no device found, luckily I was able to boot up and transfer the files manually.
I then flashed the wrong stock recovery (recovery 1.28.401.7.img) so I had to unlock the bootloader again to flash a different one, thankfully the one I did flash (recovery 2.24.771.3 - TRE.img), which matched the first OTA update, everything installed fine after that
Thanks a lot mate. I'll happy to send my device away for repair with no worries now.
Regards, Ryan
Click to expand...
Click to collapse
Sorry to hear you had some troubles , are you on Windows 8 or 8.1, is that why adb wasn't working.
Also have a two questions about stock recovery you used,
1- when you used 1.28.401.7 the OTA didnt work, or you didnt try?
2- when you used 2.24.771.3 did the OTA hang at any point, or did it reboot (twice, I believe), correctly and by itself?
would be nice if you could give me some more info, it would probably be helpful to others too.
Thanks

nkk71 said:
Sorry to hear you had some troubles , are you on Windows 8 or 8.1, is that why adb wasn't working.
Also have a two questions about stock recovery you used,
1- when you used 1.28.401.7 the OTA didnt work, or you didnt try?
2- when you used 2.24.771.3 did the OTA hang at any point, or did it reboot (twice, I believe), correctly and by itself?
would be nice if you could give me some more info, it would probably be helpful to others too.
Thanks
Click to expand...
Click to collapse
I'm on Windows 7 mate. It just seemed really intermittent. May have been my USB lead/port.
1.28.401.7 - Downloaded the OTA fine, when the phone rebooted to install, it just hung on the "Entering Recovery" screen... Didnt get past that.
2.24.771.3 - Downloaded the OTA fine, booted into Recovery fine, hung on the first quarter (had to manually reboot) after that it installed straight away.
Hope this helps.

stanny2k said:
I'm on Windows 7 mate. It just seemed really intermittent. May have been my USB lead/port.
1.28.401.7 - Downloaded the OTA fine, when the phone rebooted to install, it just hung on the "Entering Recovery" screen... Didnt get past that.
2.24.771.3 - Downloaded the OTA fine, booted into Recovery fine, hung on the first quarter (had to manually reboot) after that it installed straight away.
Hope this helps.
Click to expand...
Click to collapse
hmm: it just hung on the "Entering Recovery" screenit just hung on the "Entering Recovery" screen
did you do a "fastboot erase cache", after flashing it? that's usually the only reason it could get stuck (or perhaps a corrupt download, did you check MD5; i've had some issues downloading from dev-host sometimes).
But thanks anyway, glad all worked out, and hope you get your device back soon
cheers.

nkk71 said:
hmm: it just hung on the "Entering Recovery" screenit just hung on the "Entering Recovery" screen
did you do a "fastboot erase cache", after flashing it? that's usually the only reason it could get stuck (or perhaps a corrupt download, did you check MD5; i've had some issues downloading from dev-host sometimes).
But thanks anyway, glad all worked out, and hope you get your device back soon
cheers.
Click to expand...
Click to collapse
Yup, I did fastboot erase cache before and after flashing it, both were successful as well. I didnt check the MD5, I just installed it after I downloaded it.. it was midnight by the time I got that far! I was tired!
Yeah and thanks a lot for your help mate. Really appreciate it.
I'll let you know the outcome with HTC Hopefully they find nothing untoward!

stanny2k said:
I'm on Windows 7 mate. It just seemed really intermittent. May have been my USB lead/port.
1.28.401.7 - Downloaded the OTA fine, when the phone rebooted to install, it just hung on the "Entering Recovery" screen... Didnt get past that.
2.24.771.3 - Downloaded the OTA fine, booted into Recovery fine, hung on the first quarter (had to manually reboot) after that it installed straight away.
Hope this helps.
Click to expand...
Click to collapse
Sorry, one last question, when you manually rebooted, did you have to keep holding VOLDOWN during boot-up, or did it enter stock recovery by itself

nkk71 said:
Sorry, one last question, when you manually rebooted, did you have to keep holding VOLDOWN during boot-up, or did it enter stock recovery by itself
Click to expand...
Click to collapse
I'm not sure if it enters recovery by itself as I just followed your guide of holding VOLDOWN
My thumbs were killing me by the end of the night!

stanny2k said:
I'm not sure if it enters recovery by itself as I just followed your guide of holding VOLDOWN
My thumbs were killing me by the end of the night!
Click to expand...
Click to collapse
finger gymnastics :laugh:

stanny2k said:
Well, that was an eventful evening
Pushing files via adb whilst in recovery causes me no end of issues... I kept getting no device found, luckily I was able to boot up and transfer the files manually.
Click to expand...
Click to collapse
Looks like I have to express my apologies on that, I believe I found the problem; the "quicker way"
I really should avoid those shortcuts, until I've tested them 100% (or at least 98%).... I'll let you know what the problem was / is when i update the guide, and sorry again for the headache!!

nkk71 said:
Looks like I have to express my apologies on that, I believe I found the problem; the "quicker way"
I really should avoid those shortcuts, until I've tested them 100% (or at least 98%).... I'll let you know what the problem was / is when i update the guide, and sorry again for the headache!!
Click to expand...
Click to collapse
:laugh: thats alright mate. No issues.
Let me know once you've updated the guide and I'll take a look at it

stanny2k said:
:laugh: thats alright mate. No issues.
Let me know once you've updated the guide and I'll take a look at it
Click to expand...
Click to collapse
problem is with the CWM i recommended, works just fine when flashed, but when using "fastboot boot CWM.img" looks like 6.0.3.2 doesnt work properly with adb, 6.0.4.5 on the other hand works with "fastboot boot"
I'll update my guide with some more "visuals" whenever I get a chance....

[SOLVED] Got stuck during OTA Update. Cannot do anything, help!

Hey there.
Had a hard time getting my HTC One from S-off to stock o2 Germany (O2___102). After several ours of problems i finally had my phone got working again. It booted up, with the O2 nand backup and stock recovery and it gave me an OTA notification. Was happy like a little kit. Then I started it.
So now thats the problem. It started, but it got stuck in the middle. I cannot do anything, neither power it off nor restarting. Its a mess. What can i do. Is there a special button combo? Wait until battery is fully drained? But what comes after that....
PLS HELP!

CarlosCalderon said:
Hey there.
Had a hard time getting my HTC One from S-off to stock o2 Germany (O2___102). After several ours of problems i finally had my phone got working again. It booted up, with the O2 nand backup and stock recovery and it gave me an OTA notification. Was happy like a little kit. Then I started it.
So now thats the problem. It started, but it got stuck in the middle. I cannot do anything, neither power it off nor restarting. Its a mess. What can i do. Is there a special button combo? Wait until battery is fully drained? But what comes after that....
PLS HELP!
Click to expand...
Click to collapse
Not sure I understand you correctly, but to reboot:
press and hold POWER + VOLDOWN (under a bright light, I'm not kidding!!), when it reboots (about 20 to 30 seconds), let go of POWER but keep holding VOLDOWN, that will get you to bootloader.
(if it doesnt work the first time, try again, sometimes takes me 2 to 3 times to get it working, and remember the bright light is important!!)

Bright light?! You mean under a lamp? Sounds really curious...
Anyway... An update: have been to work and I just left it updating. Battery went low and the phone turned off. Now that I'm back I charged it a bit and the phone turned on and resumed updating. After it had finished, the phone turned itself immediately off. Now it's just black and when I'm trying to turn it on only the capacitive buttons flashes. That's it... Maybe the battery is still too low.
I'm going to sleep now and hope tomorrow there will be hope for my one... But I think it's hard bricked...
Gesendet von meinem Nexus 7 mit Tapatalk

Why would it be hard bricked? Why did you go from S-off to stock when you can have the latest release and update the firmware with S-off anyway? Can you, as asked already, boot into bootloader or not?
Sent from my HTC One

nkk71 said:
(under a bright light, I'm not kidding!!), when it reboots (about 20 to 30 seconds), remember the bright light is important!!)
Click to expand...
Click to collapse
You're the man. This is how I turned it back to life again, after nothing works anymore... Bright light?! Why does it works.... Like magic, but its definitetly weird

CarlosCalderon said:
You're the man. This is how I turned it back to life again, after nothing works anymore... Bright light?! Why does it works.... Like magic, but its definitetly weird
Click to expand...
Click to collapse
The light sensor thingy is no joke, told you I wasn't kidding
I believe it's to avoid reboots, if the phone is in your pocket (for example).

I had to use a kitchen lamp.... So pretty light. Otherwise it didn't work... But now I feel so lucky, I will try the other OTA files also
We will see. Thank you so much!

Last issue to fix this thing.
I'm now fully stock on o2___102 CID. Last thing I have to do is, to lock und remone S-OFF. So I used revone. But I think I need Root. Can i have root without touching the recovery and leave anything stock? How can i remove revone and root afterwards?
Please, help me the last time to fix this beast

CarlosCalderon said:
I had to use a kitchen lamp.... So pretty light. Otherwise it didn't work... But now I feel so lucky, I will try the other OTA files also
We will see. Thank you so much!
Click to expand...
Click to collapse
The bathroom seems a popular place too :silly:
CarlosCalderon said:
Last issue to fix this thing.
I'm now fully stock on o2___102 CID. Last thing I have to do is, to lock und remone S-OFF. So I used revone. But I think I need Root. Can i have root without touching the recovery and leave anything stock? How can i remove revone and root afterwards?
Click to expand...
Click to collapse
can you rephrase, i didnt understand, you want to use revone to S-Off? or you want to lock and remove revone and S-On?? ... careful!!
Please explain in more detail (what, how, and why) you're doing this, thanks

No problem Thanks first for your help.
I have to send the phone in under warranty. At the moment the phone is ***UNLOCKED*** and S-off with stock Germany O2 Firmware (O2___102).
What do I want to do? Get rid of S-Off and the UNLOCKED status. So I tried to push revone via adb push revone /data/local/tmp/
Then I did:
adb shell
cd /data/local/tmp
chmod 755 revone <---This does not work without root, so revone basicly does not work. Now I'm trying to root the phone, without touching anything else, because I'm so happy that it does work right now. So, is there a way to grant root, without touching hboot, recovery, firmware and rom?!
Thank you!

CarlosCalderon said:
No problem Thanks first for your help.
I have to send the phone in under warranty. At the moment the phone is ***UNLOCKED*** and S-off with stock Germany O2 Firmware (O2___102).
What do I want to do? Get rid of S-Off and the UNLOCKED status. So I tried to push revone via adb push revone /data/local/tmp/
Then I did:
adb shell
cd /data/local/tmp
chmod 755 revone <---This does not work without root, so revone basicly does not work. Now I'm trying to root the phone, without touching anything else, because I'm so happy that it does work right now. So, is there a way to grant root, without touching hboot, recovery, firmware and rom?!
Thank you!
Click to expand...
Click to collapse
ah warranty, please check my guide: http://forum.xda-developers.com/showthread.php?t=2541082
This will return to 100% stock (including S-On if YOU choose), but has to be done in exactly in the order I mentioned in the guide, to avoid possible problems.
If you have questions, please feel free to ask

That does not help me.... Because I dont have a fitting recovery for this o2___102 CID. Its everything finished... If I remove unlocked and tempered with the guru method, i need a custom recovery. But i see no way to flash it back to stock... Can you understand, where my problem is? my CID is pretty screwed

CarlosCalderon said:
That does not help me.... Because I dont have a fitting recovery for this o2___102 CID. Its everything finished... If I remove unlocked and tempered with the guru method, i need a custom recovery. But i see no way to flash it back to stock... Can you understand, where my problem is? my CID is pretty screwed
Click to expand...
Click to collapse
A) you just need a stock recovery "close" to your version, http://forum.xda-developers.com/showthread.php?t=2463387
during the 1st OTA update, the stock recovery may get stuck once (possibly twice), perfectly normal, it's cause the "reboot" command isn't able to do it correctly, so you manually reboot (as mentioned above) to let it reboot back to stock recovery and continue it's update.
(possibly twice)
or
B) do you have the 1st OTA file? if so you can extract stock recovery from it.
==> once the first OTA is applied successfully, everything will be 100% stock (including stock recovery for your CID)

I'm starting to hate this phone...why is this so freakin difficult. In your guide you are saying boot a recovery img: fastboot boot CWM.img
but this will just freeze the phone again What a surprise. Too bad i'm on the newest version from o2...
So what is close to stock recovery? My software number is 3.62.206.1...

CarlosCalderon said:
I'm starting to hate this phone...why is this so freakin difficult. In your guide you are saying boot a recovery img: fastboot boot CWM.img
but this will just freeze the phone again What a surprise. Too bad i'm on the newest version from o2...
So what is close to stock recovery? My software number is 3.62.206.1...
Click to expand...
Click to collapse
1- Do you intend on going S-On? If yes, then just for info, this is what is likely going to happen:
you do the S-Off to S-On command, after a few reboots, your phone will say "tamper detected - rebooting" and TAMPERED is back in bootloader.
I cannot confirm this to be 100% of all cases, but it has happened more than a few times, trust me.
2- closest recovery for 3.62.206.1, I would say 3.62.401.1 (unless you can find the OTA file)
3- "fastboot boot <name of recovery>.img" will only work on hboot 1.44
My guide was written in a very specific order, with very specific commands, versions, etc. to avoid any potential problems.
There are always multiple ways of doing things, depending on you situation, and you're free to do it any which way you like.
Good luck

I restarted from the scratch and used your guide. Everything's prefect, locked, removed tempered. But after the first ota it got stuck again. 2 times. The first time I managed it to reboot. After the second is black.
At the moment not even light can turn it on... You have a special trick again?
Gesendet von meinem Nexus 5 mit Tapatalk

CarlosCalderon said:
I restarted from the scratch and used your guide. Everything's prefect, locked, removed tempered. But after the first ota it got stuck again. 2 times. The first time I managed it to reboot. After the second is black.
At the moment not even light can turn it on... You have a special trick again?
Gesendet von meinem Nexus 5 mit Tapatalk
Click to expand...
Click to collapse
under a bright light?
Try holding POWER + VOLDOWN (phone under a bright light, not kidding!!) after about 5 seconds, buttons should start blinking, and after 20 to 30 seconds, phone should reboot.
you may need to try 2 or 3 times, to get it to work.

Thank you for helping me out. That was awesome!
Problem solved, Locked, S-On, Stock O2! Ready for warranty

CarlosCalderon said:
Thank you for helping me out. That was awesome!
Problem solved, Locked, S-On, Stock O2! Ready for warranty
Click to expand...
Click to collapse
:laugh:
Good luck, hope you get it back soon
oh and if you could edit main thread title to include [SOLVED], thanks

[Q] HTC One M7 Soft Brick (Stuck on HTC logo during boot)

Hi everyone,
I'm hoping that someone can provide some assistance with my HTC One that won't load past the HTC One logo. I've never done any rooting or unlocking, the phone was stock when this happened. Last week the battery drained on me (not the first time it happened), I came home and put the phone to charge and when I tried to turn it on it wouldn't load past the HTC logo. I don't have any custom recovery on the phone. I am able to access the bootloader menu. I tried resetting the phone and wiping the cashe but that didn't help.
I downloaded ABD setup but would like some assistance before I try anything. I've been reading and "googling" a lot over the past week but it all seems a little over my head.
I'm a total noob when it comes to cell phones but I'm willing to learn.
Any help is greatly appreciated! Thanks in advance for your time.

xdabrainiak said:
Hi everyone,
I'm hoping that someone can provide some assistance with my HTC One that won't load past the HTC One logo. I've never done any rooting or unlocking, the phone was stock when this happened. Last week the battery drained on me (not the first time it happened), I came home and put the phone to charge and when I tried to turn it on it wouldn't load past the HTC logo. I don't have any custom recovery on the phone. I am able to access the bootloader menu. I tried resetting the phone and wiping the cashe but that didn't help.
I downloaded ABD setup but would like some assistance before I try anything. I've been reading and "googling" a lot over the past week but it all seems a little over my head.
I'm a total noob when it comes to cell phones but I'm willing to learn.
Any help is greatly appreciated! Thanks in advance for your time.
Click to expand...
Click to collapse
Honestly, if this is not a result of tampering, you might want to check into warranty. HTC Sync might have a recovery option, never used it, you could check there. Any solution I would have would void said warranty. It's not entirely uncommon for software to corrupt upon power loss.. rare indeed but it happens. See if you warranty is good have a new one in no time.

How about this ?
MrLizm said:
Honestly, if this is not a result of tampering, you might want to check into warranty. HTC Sync might have a recovery option, never used it, you could check there. Any solution I would have would void said warranty. It's not entirely uncommon for software to corrupt upon power loss.. rare indeed but it happens. See if you warranty is good have a new one in no time.
Click to expand...
Click to collapse
I have pretty much the same issue except the fact that mine was nit battery drained. It just crashed on some app and then device went to boot loop. Deleted the cache and factory reset thing. No luck.
Best bet is warranty get it replaced. Bloody so many devices going blank just like that !!! Htc should now make a statement on this!!
Else there is a long way , Some steps broadly.. if you on the latest android version and with a never tampered device.
Spend some time on this forum for each of those steps.
Unlock Bootloader (htcdev.com)[all data is gone] - Twrp recovery flash (2.7.1 recommended) -> Adb Sideload - Custom Rom (Android revolution 8.1 recommended)- If okay with custom rom stop here. And enjoy your device.
Else continuing ... Custom Rom -> Use firewater to do S-off --> RUU.exe of the latest Stock Build of your CID and MID (htc1) guru.com --> OTA updates to latest builds by HTC.
Notes :
1) RUU doing with S-on on a older version of android will leave you with bricked device.
2)Adb is needed to run the S-off firewater. So you need a working Android OS , thus the custom rom.
3)Once S-off , make sure you clear the tampered flag and relocked flag in bootloader. Just in case you need to visit the HTC service center later.
I want to the above as same situation. Stuck at the adb sideload step.

anirudhgargi said:
I have pretty much the same issue except the fact that mine was nit battery drained. It just crashed on some app and then device went to boot loop. Deleted the cache and factory reset thing. No luck.
Best bet is warranty get it replaced. Bloody so many devices going blank just like that !!! Htc should now make a statement on this!!
Else there is a long way , Some steps broadly.. if you on the latest android version and with a never tampered device.
Spend some time on this forum for each of those steps.
Unlock Bootloader (htcdev.com)[all data is gone] - Twrp recovery flash (2.7.1 recommended) -> Adb Sideload - Custom Rom (Android revolution 8.1 recommended)- If okay with custom rom stop here. And enjoy your device.
Else continuing ... Custom Rom -> Use firewater to do S-off --> RUU.exe of the latest Stock Build of your CID and MID (htc1) guru.com --> OTA updates to latest builds by HTC.
Notes :
1) RUU doing with S-on on a older version of android will leave you with bricked device.
2)Adb is needed to run the S-off firewater. So you need a working Android OS , thus the custom rom.
3)Once S-off , make sure you clear the tampered flag and relocked flag in bootloader. Just in case you need to visit the HTC service center later.
I want to the above as same situation. Stuck at the adb sideload step.
Click to expand...
Click to collapse
How exactly are you stuck at adb sideload?
assuming you have your custom rom, you would:
boot to recovery, select advanced then sideload...
from your pc you goto your ADB folder open cmd and type: adb sideload filename.zip
this pretty much sums it up

So I've been fiddling with the phone trying to fix it, looking at youtube videos and reading the forums but I'm still stuck. It's a Telus phone and it is not under warranty anymore... or it would have gone back already. I almost want to just give it back hahaha :laugh:
I managed to unlock to bootloader... that was pretty simple. The next thing I tried to do was do an adb sideload of twrp... it worked fine until I went into recovery mode and the phone was frozen there. I used an older version of twrp that was suggested 2.7.1 I believe. I noticed on the twrp website that in order to get it on your phone you need to be S-off.
How do I get some sort of custom recovery on my phone? It feels like whatever I do there is always some glitch or little thing that I failed to do.

xdabrainiak said:
So I've been fiddling with the phone trying to fix it, looking at youtube videos and reading the forums but I'm still stuck. It's a Telus phone and it is not under warranty anymore... or it would have gone back already. I almost want to just give it back hahaha :laugh:
I managed to unlock to bootloader... that was pretty simple. The next thing I tried to do was do an adb sideload of twrp... it worked fine until I went into recovery mode and the phone was frozen there. I used an older version of twrp that was suggested 2.7.1 I believe. I noticed on the twrp website that in order to get it on your phone you need to be S-off.
How do I get some sort of custom recovery on my phone? It feels like whatever I do there is always some glitch or little thing that I failed to do.
Click to expand...
Click to collapse
TWRP 2.7.1.1 is here, http://forum.xda-developers.com/showthread.php?t=2173870
Main advise is to follow steps, Do them no matter how trivial. Usually things go wrong for the littlest reason. You want to make sure you have the most current version of fastboot and adb tools on your computer when working with your HTC. Other good things to pay attention is use OEM cables and take note that you are plugged directly into a USB 2.0 on the board, not a port on the front of PC, a hub or extender..

xdabrainiak said:
So I've been fiddling with the phone trying to fix it, looking at youtube videos and reading the forums but I'm still stuck. It's a Telus phone and it is not under warranty anymore... or it would have gone back already. I almost want to just give it back hahaha :laugh:
I managed to unlock to bootloader... that was pretty simple. The next thing I tried to do was do an adb sideload of twrp... it worked fine until I went into recovery mode and the phone was frozen there. I used an older version of twrp that was suggested 2.7.1 I believe. I noticed on the twrp website that in order to get it on your phone you need to be S-off.
How do I get some sort of custom recovery on my phone? It feels like whatever I do there is always some glitch or little thing that I failed to do.
Click to expand...
Click to collapse
Download the latest version of TWRP for your phone
Place in your adb folder
Reboot to bootloader
Fastboot flash recovery "name_of_recovery".img
Fastboot erase cache
Reboot bootloader again and boot into recovery