Looking for help on botched update attempt.... - T-Mobile HTC One (M9)

Hello, haven't used this site in years but I'm hoping someone could help out. I believe my HTC One M9 (T-Mobile) is in a bad state and not sure if I'm going to be able to recover it.
Current Status: The phone only boots into the bootloader, attempting to goto recovery it states there isn't one. S-ON **Relocked**
What was done: I'm sure I screwed it all up by doing a 'fastboot oem lock', which was done from my understanding that the phone wouldn't be able get OTA updates unless it was. I assume that was the culprit as before that I had TWRP and a rooted OS. I've read through this thread here (https://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022) quite a bit. But I know I messed something up and now just looking for help getting it back.
I've tried an RUU(RUU_HIMA_UL_M60_SENSE70_TMUS_MR_TMOUS_3.39.531.7), but it said my battery was under 30% yet its over 80%, trying to charge and maybe try again. Also tried the 4.27.531.6 RUU, though Error132 (assuming that didn't work because of the firmware being a 3.x and not 4.x from my reading). Current OS says " 3.39.531.7 " in download mode. This is a longshot honestly. But I don't really have any other options, kinda need the phone and want to believe there's still hope in restoring it. I'm able to do fastboot commands. I'm just not sure what I can do because I'm not able to flash due to s-on, no recovery (that i know of, that happened after the fastboot oem lock command) i can get in to, no system to boot into. Almost tried using the Unlock_code.bin, but I wasn't even able to use the fastboot oem get_identifier_code (that failed as well) in order to generate another one from htcdev. So I'm at a loss here, I've spent hours and hour on reading and not getting anywhere. ANY help would be greatly appreciated. I can give any more info that would help to restoring, but again, I can ONLY access the bootloader screen/download mode...and that's about it Fingers crossed someone could assist/guide me in getting this thing running again.
Edit: Well I managed to get the bootloader unlocked again using the code from HTC (I found out I was on the wrong screen, was in the bootloader when I needed to be in Download mode for the get_identifier_code to work.) Now that's done, it rebooted and TWRP is still there and booted back into the system. I'm probably gonna say F*@# it to OTA updates unless someone could still help out with that. Have 2.8.6.4 TWRP installed. But as is, the phone is working again so that's good enough for now.

Hello all,
Sorry to bother u all. I tried to find answer myself by reading posts but couldnt find one . I have a HTC One-M9 phone with Bootloader Unlocked,S-OFF,Rooted and on Kitkat Sense 51 2.7.531.6. I found some bugs on my phone and i want to reflash with this https://androidfilehost.com/?fid=673368273298918830 which is exactly my version. If i flash with this using fastboot
(i) Will my unlocked bootloader will be locked/relocked
(ii) Will my S-OFF turns to S-ON. I dont want this to happen because i have to install a software which needs to modify kernel.
Right now I made a Nandroid Backup using TWRP. If anything goes wrong how to restore from nandroid. Please answer my questions and help me.

After a long a arduous journey, I've finally managed to get the phone updated to Nougat, back to root with the TWRP recovery. I was able to run the 3.xx RUU after removing HTC Sync and going to Device Manager and picking the HTC Driver from list. Made a backup after the fresh install of Nougat, but I figured I could run the 4.x RUU if I ever need to OTA again. But for now, I've got the phone updated as far as I can and back to root so I'm good. Mods feel free to delete this thread, apologies if it was in the wrong section. @bsskkd, sorry but I'm not too sure, maybe someone with more knowledge will be able to help out.

Related

[Q] AlphaRevX S-OFF, Clockwork recovery and want to upgrade to WWE_2.30.405.1

All,
I want to install the WWE_2.30.405.1 OTA upgrade that arrived yesterday but when I tried, it failed, so I need some help.
I have an IncS that came with Froyo and which I then upgraded OTA to gingerbread when it arrived.
I later unlocked with AplhaRevX and installed Clockwork Recovery, then rooted by following the great guide in the dev section.
I don't really care about S-OFF, clockwork or root anymore, been there done that, didn't really make much difference to what I want to do with my phone, so if I have to reset to a stock S-On phone with standard recovery etc then thats fine.
Can anyone help?
This is what I tried, but it didn't work...
Last night I got an OTA notification that there was an update, so went ahead and tried the install.
When it rebooted I got a a boot screen with an exclamation mark in a triangle and the Android guy. Then nothing..
After about 20 minutes I decided to take out the battery and reboot, that got me back in and my phone is working now, but without the upgrade, so now I'm here looking for help.
You can upgrade with the RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20 .2808.30.085AU_3805.06.03.03_M_release_199308_signed.
Donwload link on the forums.
Thanks, just found the link, but the hosting server is currently down so I can't test. Will post results when I can get the file and know what to do with it.
Some more questions...
The link is in the form of a windows EXE which makes me somewhat nervous.
I've only ever installed andoid rom's via the OTA update process, and so I'm not sure what I should do with this file.
I'll download later and see if I can figure it out, but have you explicitly tried this with the combination I have listed above?
I have a working phone right now so I'm not interested in anything that is untested.
Looking at other threads with the combination I have listed above, but applied in a different order, people have needed to resort to XTC-Clips to recover, I won't be able to do that so I need to fix this in software only.
abcprice said:
Thanks, just found the link, but the hosting server is currently down so I can't test. Will post results when I can get the file and know what to do with it.
Some more questions...
The link is in the form of a windows EXE which makes me somewhat nervous.
I've only ever installed andoid rom's via the OTA update process, and so I'm not sure what I should do with this file.
I'll download later and see if I can figure it out, but have you explicitly tried this with the combination I have listed above?
I have a working phone right now so I'm not interested in anything that is untested.
Looking at other threads with the combination I have listed above, but applied in a different order, people have needed to resort to XTC-Clips to recover, I won't be able to do that so I need to fix this in software only.
Click to expand...
Click to collapse
what you need to do is just to download the latest Ruu v2.30.405.1, connect ur phone to computer, double click the EXE file that you downloaded to run the Ruu program on a winxp/win7, click the confirm or ok button ,then you'll get what you want in about 15mins...remember not to do anything on ur phone or computer during this period.
OK Great. Will do as soon as I can download from filefactory again.
Again though I want to know has anyone tested this process and what will state will my phone be in when it is complete?
Just want a bit of reasurance that someone has actually done this with an AlpharevX S-Off phone and clockwork recovery installed.
abcprice said:
OK Great. Will do as soon as I can download from filefactory again.
Again though I want to know has anyone tested this process and what will state will my phone be in when it is complete?
Just want a bit of reasurance that someone has actually done this with an AlpharevX S-Off phone and clockwork recovery installed.
Click to expand...
Click to collapse
Those that were able to download the 2.30 RUU before the file server went down have reported that after upgrading to 2.30 AlphaRevX is no longer able to successfully run and S-OFF this version even though the HBOOT loader appears to be identical to the 2.12 RUU. If you currently have S-OFF and wish to retain it, then you shouldn't install the 2.30 RUU. You should wait for someone to build a rooted version of this ROM.
Or S-OFF with old rom, install ARHD 1.1.0 (2.30.405.1 based) and after the radio .06.03.03_M.
This is the right way.
tpbklake said:
Those that were able to download the 2.30 RUU before the file server went down have reported that after upgrading to 2.30 AlphaRevX is no longer able to successfully run and S-OFF this version even though the HBOOT loader appears to be identical to the 2.12 RUU. If you currently have S-OFF and wish to retain it, then you shouldn't install the 2.30 RUU. You should wait for someone to build a rooted version of this ROM.
Click to expand...
Click to collapse
OK Thanks.
Do you have a link to someone 'reporting' that they tried the RUU on a phone with AlphaRevX S-Off and Clockwork?
Not worried about losing my S-Off status or root, I want my phone to be able to take OTA updates again, in fact if I could restore to the state it was in before I unlocked, then that would be best of all.
Also anyone willing to post a copy of the RUU somewhere else for download, cos the filefactory link still seems to be down.
abcprice said:
OK Thanks.
Do you have a link to someone 'reporting' that they tried the RUU on a phone with AlphaRevX S-Off and Clockwork?
Not worried about losing my S-Off status or root, I want my phone to be able to take OTA updates again, in fact if I could restore to the state it was in before I unlocked, then that would be best of all.
Also anyone willing to post a copy of the RUU somewhere else for download, cos the filefactory link still seems to be down.
Click to expand...
Click to collapse
Here is a thread that discusses flashing the RUU and the attempts of AlphaRevX:
http://forum.xda-developers.com/showthread.php?t=1153871
OK That thread is all about how it didn't work, and the download site is still broken, so I'm not going to try anything for now.
I'll be away with work next week and need my phone to work, so I'll look in again when I get back and see if anything has changed.
Thanks for all your help anyway, I don't think this thread actually got even close to answering my question, but at least you tried.
If I try flashingthe RUU file then I'll be sure to let you know how it turned out.
Bye for now.
abcprice said:
OK That thread is all about how it didn't work, and the download site is still broken, so I'm not going to try anything for now.
I'll be away with work next week and need my phone to work, so I'll look in again when I get back and see if anything has changed.
Thanks for all your help anyway, I don't think this thread actually got even close to answering my question, but at least you tried.
If I try flashingthe RUU file then I'll be sure to let you know how it turned out.
Bye for now.
Click to expand...
Click to collapse
The point of mentioning that thread was that these users had previously used AlphaRevX to gain S-OFF and when they installed the 2.30 RUU and they lost root and S-OFF and they are now attempting to get S-OFF back which is the part that is failing.
OK So I'm back from my trip and today I had a chance to play with this a bit.
I downloaded this RUU http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1033922&v=1&libid=1310921120143&out=http%3A%2F%2Fwww.filefactory.com%2Ffile%2Fcc2d60f%2Fn%2FRUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe&title=%5BROMs%5DIncredible%20S%20Shipped%20ROMs%20Collection%20-%20xda-developers&txt=http%3A%2F%2Fwww.filefactory.com%2Ffile%2Fcc2d...308_signed.exe and tested an install.
I got what I wanted more or less, I have the update and all looks good..
However for those of you following from home, these are the trade-offs.
All data on my phone was erased. I had an 'out of box' experience when I booted the phone.
I lost S-Off status
I Lost root
I seem to have a corrupt recovery partition. (When I select recovery from the boot menu it hangs at a screen with a red triangle and an exclamation mark. Only way to boot the phone after that is to remove the battery and re-insert).
4 in particular bothers me a bit, as I'm not sure how to recover that and I'm not sure if I may need it in future. If you remember, what I originally wanted was to be able to get OTA updates in future, from reading around, I don't think that will be possible with a corrupt recovery image, so any tips on fixing that would be great.
Just download the latest or if you wanna keep s off a previous RUU from your carrier. And run the program it will return the phone to stalk
Sent from my HTC Incredible S using XDA Premium App
Hmm, thats what I think I've done.
My device is not tied to a carrier, so the WWE RUU Should have been the right one.
I have now also tried using fastboot to flash the recovery, but I get the following error
C:\Phone\>fastboot.exe flash recovery recovery.img
sending 'recovery' (3658 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
I tried with an older recovery from WWE 212 as well, but got the same error. Don't really know where to go next, but any help gladly recieved.
abcprice said:
OK So I'm back from my trip and today I had a chance to play with this a bit.
I downloaded this RUU http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1033922&v=1&libid=1310921120143&out=http%3A%2F%2Fwww.filefactory.com%2Ffile%2Fcc2d60f%2Fn%2FRUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe&title=%5BROMs%5DIncredible%20S%20Shipped%20ROMs%20Collection%20-%20xda-developers&txt=http%3A%2F%2Fwww.filefactory.com%2Ffile%2Fcc2d...308_signed.exe and tested an install.
I got what I wanted more or less, I have the update and all looks good..
However for those of you following from home, these are the trade-offs.
All data on my phone was erased. I had an 'out of box' experience when I booted the phone.
I lost S-Off status
I Lost root
I seem to have a corrupt recovery partition. (When I select recovery from the boot menu it hangs at a screen with a red triangle and an exclamation mark. Only way to boot the phone after that is to remove the battery and re-insert).
4 in particular bothers me a bit, as I'm not sure how to recover that and I'm not sure if I may need it in future. If you remember, what I originally wanted was to be able to get OTA updates in future, from reading around, I don't think that will be possible with a corrupt recovery image, so any tips on fixing that would be great.
Click to expand...
Click to collapse
That's not corrupt, that's what happens on stock
Ahh OK, if that is normal then how do I test that my recovery partition is good? I don't want to get buggered when the next OTA comes along.

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

EMEI is 00000000 after upgrade to 4.3, what is my next step

Hi there,
I have searched high & low on the interwebs for a possible solution to my problem but have yet to yield any significant results.
I was on 4.2.2 Stock, Rooted, with bulletproof, and I had started to get random reboots and then 4 nights ago during the night it decided to get into a reboot loop. It would power up for about 20 mins and then restart again & again so when I woke up it was super hot.
So I thought it was time to update it to 4.3 now in the hope that this would resolve the issue but it didn't. I obtained the relevant RUU (Guru Reset M7 2.24.980.2 for HTC__039) from htc1guru and since I was only wanting to get the OTA in the hope that this would fix any other software issues, I only flashed the recovery. I then proceeded to do the large OTA update. This was successful. Then the reboots started again.
Time for a factory reset now, (which I realise I should have just done in the first place) but after setting up my details in the phone I am unable to get network over 3G/4G and when I go into look at the APNs, it says that no sim card is installed when it definitely is. When I go into Phone Info, it states that my EMEI is 00000000.
After looking around for what feels like hours, I read somewhere that I might need to flash the radio but I only have the radio from the previous RUU(Guru Reset M7 2.24.980.2) or can I use that since I can not find anything around RUUs for 3.63.980.2.? I don't want to make the situation any worse than it already is.
I am hoping that there is a simple explanation and fix & any help or guidance would be much appreciated.
Thanks in advance :good:
So you think the problem is that your software is upgraded and not your firmware? If so, you can solve that by dowgrading your software. If you can't find an updated RUU (nothing except a signed file from HTC should be called a RUU), there is still a solution:
- Find a system dump from a phone that is your CID and the version of Android you want. It will be a CWM or TWRP backup.
- Flash the appropriate custom recovery.
- Push the files to your phone in the appropriate directory (you may need to make a backup just to see what the right directory is).
- Restore the backup you just pushed to your phone.
Then factory reset and install the stock recovery. You may need to re-lock the bootloader (I'm not sure). Try to get the correct OTA. If you can't find it, try to download one and save as /sdcard/update.zip. Use the stock recovery to flash it. (You'll need to search for instructions on how to do that. It involves key combinations.) Finally, unlock the bootloader, make a backup, and (optionally) root. Don't install a custom kernel. If your problem persists, you likely have a hardware problem.
Thanks for your reply.
I have no idea if its software/firmware but its showing its on 4.3. I was speculating on the radio possibly needing to be reflashed due to one comment I read on a forum I randomly came across?
So I could use my very first backup I used through TWRP and push that to the phone?
While I am fairly new to Android(had to switch for the HTC ONE), I have been around idevices for a long time and have learnt to always keep multiple backups just in case
I left the bootloader unlocked as most guides say that you don't need to have it locked to get the OTA. I actually tried to find the manual OTA file and do it the way you suggested but at the time I had no luck.
I'll see what I can accomplish tonight.
Apologies on the noobness in regards to RUU.
Is it possible to use a RUU for lets say T-Mobile on an international variant? I see HTC released an RUU for T-Mobile for 4.3 but as far as I can see there isn't any others.
[email protected] said:
So I could use my very first backup I used through TWRP and push that to the phone?
Click to expand...
Click to collapse
That's the first thing I'd try, yes. But I'm guessing just as much as you are.
fenstre said:
That's the first thing I'd try, yes. But I'm guessing just as much as you are.
Click to expand...
Click to collapse
Hahahaha Well I trust your guess way more then mine
Would I need s-off to copy the previous backup back onto the phone or would I only need s-off if I had to push something to system(which I do not need to do)?
I tried last night to run rumrunner and it continually failed and basically told me I had 2 different scenarios to resolve it(the following is coming from memory and its very hazy). One was to use a different kernel and the other was to use another ROM, but that wasn't the preferred option.
At work now so will try and restore my original backup tonight at home. Thanks for your help.
[email protected] said:
Would I need s-off to copy the previous backup back onto the phone or would I only need s-off if I had to push something to system(which I do not need to do)? .
Click to expand...
Click to collapse
Sorry for my late response. You only need s-off to flash firmware that is older, for a different phone CID, or modified by a third party. Or to change other hidden partitions, like to modify the "TAMPERED" flag or to change the CID. Unlocking the bootloader is for changing partitions from fastboot mode: recovery, and maybe also system and boot. You do not need an unlocked bootloader to change these partitions from recovery if you already have a custom recovery installed. (You can definitely modify system and boot, but I'm not sure about modifying recovery with a locked bootloader.)
fenstre said:
Sorry for my late response. You only need s-off to flash firmware that is older, for a different phone CID, or modified by a third party. Or to change other hidden partitions, like to modify the "TAMPERED" flag or to change the CID. Unlocking the bootloader is for changing partitions from fastboot mode: recovery, and maybe also system and boot. You do not need an unlocked bootloader to change these partitions from recovery if you already have a custom recovery installed. (You can definitely modify system and boot, but I'm not sure about modifying recovery with a locked bootloader.)
Click to expand...
Click to collapse
No need to apologise, I'm just happy that someone has been able to assist me.
I have used one of my previous TWRP backups, unfortunately I couldn't use my very very first one as it was missing some files, it obviously didn't copy it all across for some reason
I now have my EMEI back (woohoo) but I think the backup I used has something wrong in the kernel as I think it has bulletproof installed. I am going to return it to stock but following a procedure here as I need to return it to HTC as the phone will not read any sim cards. I have tried 3 different sim cards and have also tested them in a firends HTC ONE and they all work in his. SO it looks like I do have an actual hardware issue with the phone which isn't cool just before Xmas.
I already have major withdrawals from being able to play ingress :crying:
Thanks heaps for your help.

[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

stock recovery for vzw?

Hello everyone. I don't know a whole lot about HTCs, but I want one badly after rooting one for a friend. I have another friend that tried to root a 626 verizon version on 6.0 with a tutorial on the HTC site for a different phone (he didn't ask me, I assure you and I gave him a scolding) and his recovery is broken. He's not sure if he fastbooted TWRP onto it or not but I think he may have without unlocking the bootloader. Is there possibly a stock recovery that he could fastboot back on there? His system is still booting and adb and fastboot are still connecting, I just don't know if there is a stock recovery for his and since it's not mine, I don't want to spend hours looking. Also, he doesn't have a lot of understanding yet as this was his first root attempt so I'm asking for him. Thanks so much for any help with this. Any Android down makes me sad. I told him if he wants to root get something non-verizon. He just ordered an unlocked S5 and I told him thats a very good place to start. But, if possible, I hope we can get his HTC right again. I also told him not to factory reset EVER if we can't get his recovery back. Thanks so much for any help.

Categories

Resources