Related
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
Ok so before I begin, I've read everything online and cannot figure this out. I've searched the forums for hours and still no luck.
I have the HTC One M7 with T-Mobile
I've had it since December with no issues at all, and still in mint condition. Never dropped.
I have it rooted, with boot unlocked
ViperOne ROM Installed, stock kernel.
Ok so Tuesday night I was going to bed (phone still on and working) and plugged my phone in to the charger to charge for the night as I usually do every night. Wake up in the morning and hit the power button to unlock the phone and to my surprise the display doesn't come on. As I said I've never dropped this phone in the entire 9 months I've had it, nor has it ever gotten wet.
This is NOT the first time this has happened either. I've had the phone display flicker on/off and after a couple times it will just stay on. It's also went off and I've fixed it by holding a light to the sensor in the top left and it came on. This time I'm not having any luck.
Please help! It's rooted, with custom ROM, and boot unlocked, therefore I cannot send it in for repair as warranty is voided. I've tried restoring it back to stock the best I can via mirror Android to PC program, but it's very difficult. I've restored it once before, I just don't get why it's not working again with me holding the light to the sensor. Any help and/or suggestions would be greatly aprreciated!! Thank you!
Kev_McCall said:
Ok so before I begin, I've read everything online and cannot figure this out. I've searched the forums for hours and still no luck.
I have the HTC One M7 with T-Mobile
I've had it since December with no issues at all, and still in mint condition. Never dropped.
I have it rooted, with boot unlocked
ViperOne ROM Installed, stock kernel.
Ok so Tuesday night I was going to bed (phone still on and working) and plugged my phone in to the charger to charge for the night as I usually do every night. Wake up in the morning and hit the power button to unlock the phone and to my surprise the display doesn't come on. As I said I've never dropped this phone in the entire 9 months I've had it, nor has it ever gotten wet.
This is NOT the first time this has happened either. I've had the phone display flicker on/off and after a couple times it will just stay on. It's also went off and I've fixed it by holding a light to the sensor in the top left and it came on. This time I'm not having any luck.
Please help! It's rooted, with custom ROM, and boot unlocked, therefore I cannot send it in for repair as warranty is voided. I've tried restoring it back to stock the best I can via mirror Android to PC program, but it's very difficult. I've restored it once before, I just don't get why it's not working again with me holding the light to the sensor. Any help and/or suggestions would be greatly aprreciated!! Thank you!
Click to expand...
Click to collapse
Well issues like this are common with custom roms. You would need to pull a log cat or DSM message and send it to the developers.
Kev_McCall said:
Ok so before I begin, I've read everything online and cannot figure this out. I've searched the forums for hours and still no luck.
I have the HTC One M7 with T-Mobile
I've had it since December with no issues at all, and still in mint condition. Never dropped.
I have it rooted, with boot unlocked
ViperOne ROM Installed, stock kernel.
Click to expand...
Click to collapse
If you are not S-OFF, then you will have to relock your bootloader with this command: fastboot oem lock
Then run this RUU 5.14.531.11 That will put you back at stock and if you want to put a custom rom or root you can try it again.
zelendel said:
Well issues like this are common with custom roms. You would need to pull a log cat or DSM message and send it to the developers.
Click to expand...
Click to collapse
Thanks for the reply, so how would I go about pulling log cat and DSM?
majmoz said:
If you are not S-OFF, then you will have to relock your bootloader with this command: fastboot oem lock
Then run this RUU 5.14.531.11 That will put you back at stock and if you want to put a custom rom or root you can try it again.
Click to expand...
Click to collapse
Thanks man! I've tried other RUU's with no luck. So just to be certain, in order to flash an RUU, you need S-Off wit Bootloader locked? Is it not possible to flash RUU with S-On? Going to do this now. I'll let you know. I'll keep you guys updated. Feeling good about this.
Kev_McCall said:
Thanks man! I've tried other RUU's with no luck. So just to be certain, in order to flash an RUU, you need S-Off wit Bootloader locked? No, if you S-OFF you can leave it unlocked.
Is it not possible to flash RUU with S-On? No, if S-ON you can only flash it if your bootloader is locked and the same OS version or higher.
Going to do this now. I'll let you know. I'll keep you guys updated. Feeling good about this.
Click to expand...
Click to collapse
See comments above.
majmoz said:
See comments above.
Click to expand...
Click to collapse
Ok so I succesfully Installed the RUU and back to stock rom, but upon rebooting, my screen did not turn back on. I've read of dozens of other users who have experienced this same thing. I guess the next step would be to fully return it to stock, turning S-On, removing tampered, unrooting, etc, and just returning it for another phone. @majmoz
Kev_McCall said:
Ok so I succesfully Installed the RUU and back to stock rom, but upon rebooting, my screen did not turn back on. I've read of dozens of other users who have experienced this same thing. I guess the next step would be to fully return it to stock, turning S-On, removing tampered, unrooting, etc, and just returning it for another phone. @majmoz
Click to expand...
Click to collapse
If you successfully ran the RUU, then you are stock with a relocked bootloader. The downside is you have to be S-OFF to remove the tampered and to change the "relocked" to "locked".
If you are S-OFF, then you would have to put TWRP 2.6.3.3 or 2.7.1.2 and install this Bootloader Reset Tool. Then flash a stock recovery. You are now completely back to stock.
majmoz said:
If you successfully ran the RUU, then you are stock with a relocked bootloader. The downside is you have to be S-OFF to remove the tampered and to change the "relocked" to "locked".
If you are S-OFF, then you would have to put TWRP 2.6.3.3 or 2.7.1.2 and install this Bootloader Reset Tool. Then flash a stock recovery. You are now completely back to stock.
Click to expand...
Click to collapse
Yea. I turned S-Off before I even ran the RUU. So there's one thing I'm confused about. If I'm trying to return to complete stock state, why would I install Twrp or CWM if those don't come with it? Is there any other way to do this? As I have no back-light and it's been very hard to do all that I've done so far. Screen hasn't come on, so I'm working blind here. Lucky for me I remember where most of the buttons are at and with the help of ADB, I've gotten this far. @majmoz
Kev_McCall said:
Yea. I turned S-Off before I even ran the RUU. So there's one thing I'm confused about. If I'm trying to return to complete stock state, why would I install Twrp or CWM if those don't come with it? Is there any other way to do this? As I have no back-light and it's been very hard to do all that I've done so far. Screen hasn't come on, so I'm working blind here. Lucky for me I remember where most of the buttons are at and with the help of ADB, I've gotten this far. @majmoz
Click to expand...
Click to collapse
Yes, look at nkk71 guide in my signature he has the steps in post 3 or 4. I'm away from the house so I can't post the link.
majmoz said:
Yes, look at nkk71 guide in my signature he has the steps in post 3 or 4. I'm away from the house so I can't post the link.
Click to expand...
Click to collapse
@majmoz
Hey bro thank you so much for the help so far, I really appreciate it. I just have one last problem. I've already talked with HTC and they're going to be sending me a replacement and I have to send my phone back in within 10 days but they said they would be checking for root.
So question 1. When you restore phone to stock ROM via RUU it unroots the phone correct?
Second problem. Now that I've restored the stock rom, usb debugging isn't enabled and I can re-enable it due to not being able to see the screen. So because USB Debugging is not enabled ADB is no longer recognizing it when I run "adb devices"
Because of this I can't turn bootloader, tampered, and lock stats back on. I'm really nervous sending my phone back in like this. I hate to keep bothering you, but you seem to know your stuff a lot more than I, and I'd hate to start a new thread. Thanks again bro.
Kev_McCall said:
@majmoz
So question 1. When you restore phone to stock ROM via RUU it unroots the phone correct?
Second problem. Now that I've restored the stock rom, usb debugging isn't enabled and I can re-enable it due to not being able to see the screen. So because USB Debugging is not enabled ADB is no longer recognizing it when I run "adb devices"
Because of this I can't turn bootloader, tampered, and lock stats back on. I'm really nervous sending my phone back in like this. I hate to keep bothering you, but you seem to know your stuff a lot more than I, and I'd hate to start a new thread. Thanks again bro.
Click to expand...
Click to collapse
1. RUU unroots the phone.
2. Yes, you need USB Debugging enabled and a custom recovery (nkk71 uses CWM).
I have been racking my brain all night. This is a long shot, but if HTC is sending you a replacement before you have to ship yours back then here is an idea. With the replacement phone side by side; memic the commands to open Settings on both phones doing the replacement phone first, then the old phone. The location of the items should be in the same place on both screens. It may take a couple of tries but you seem adapt at reading blank screens. I'm still researching a way to turn it on remotely, but this is the only solution I could come up with presently.
When you get USB Debugging enabled, use nkk71's guide to install CWM on your phone. Then complete the manual steps to remove "Tampered" and to "Locked" the phone. Reboot the phone into bootloader per the instructions. Now we need to put the stock recovery back on the phone. You can get the stock recovery out of the last OTA. Download it to your PC, then open the zip file. Within the zip is the firmware.zip, open it and you will see recovery.img file this is the stock recovery. Just extract it and flash it like you did the custom recovery earlier. Going back to nkk71's guide, complete the fastboot command to return to S-ON. Now you are completely stock with no hint of root.
@majmoz
I'm beast! lol Ok so quick update to my problem. So I got the bright idea to use the Power+Volume Down to take screenshots of my display as I blindly tapped and used that as a guide and moved forward to unlocking developer options, then enabling USB debugging. I can now see my device in ADB once again. Should be pretty cake from here. Thank you so much bro! And also, HTC has agreed to send me a new phone, but I must first send mine in. They would have sent me one first and then I send mine in later, but they wanted to place a $600 credit hold on my card. **** THAT. The rep told me they would be checking for other damages as well as if it rooted.
Kev_McCall said:
@majmoz
I'm beast! lol Ok so quick update to my problem. So I got the bright idea to use the Power+Volume Down to take screenshots of my display as I blindly tapped and used that as a guide and moved forward to unlocking developer options, then enabling USB debugging. I can now see my device in ADB once again. Should be pretty cake from here. Thank you so much bro! And also, HTC has agreed to send me a new phone, but I must first send mine in. They would have sent me one first and then I send mine in later, but they wanted to place a $600 credit hold on my card. **** THAT. The rep told me they would be checking for other damages as well as if it rooted.
Click to expand...
Click to collapse
You are a genius!!! I will have to remember that if this type of situation arises again.
@majmoz
Ok so I've been reading those sites and I know I'm so close to being back to 100% stock, but now I'm stuck. I'm confused as to what order to things.
I restore stock recovery, then lock bootloader, turn S-ON,and remove tampered and return to Locked status?
Here are my fastboot getvar details. Just trying to get this done as soon as possible as I'm also in the process of moving and wont have net here much longer. So as soon as I get this done I can send my phone back in and get the replacement. Really hate being without a phone.
Kev_McCall said:
@majmoz
Ok so I've been reading those sites and I know I'm so close to being back to 100% stock, but now I'm stuck. I'm confused as to what order to things.
I restore stock recovery, then lock bootloader, turn S-ON,and remove tampered and return to Locked status?
Here are my fastboot getvar details. Just trying to get this done as soon as possible as I'm also in the process of moving and wont have net here much longer. So as soon as I get this done I can send my phone back in and get the replacement. Really hate being without a phone.
Click to expand...
Click to collapse
Here I put them in your new post.
Alright cool thanks! I really shouldn't have created a new thread, but I wasn't sure if you would be on for much longer. Reading it now.
Kev_McCall said:
Alright cool thanks! I really shouldn't have created a new thread, but I wasn't sure if you would be on for much longer. Reading it now.
Click to expand...
Click to collapse
it doesn't take 5 threads to fix one problem does it ?
clsA said:
it doesn't take 5 threads to fix one problem does it ?
Click to expand...
Click to collapse
Probably not, you're right. But when other people don't respond to my initial thread it's kind of hard. I'm still stuck And just trying to get this finished up. Would you care to help? It's not much.
Kev_McCall said:
Probably not, you're right. But when other people don't respond to my initial thread it's kind of hard. I'm still stuck And just trying to get this finished up. Would you care to help? It's not much.
Click to expand...
Click to collapse
we all have other lives besides XDA .. you have to be patient
I have a few min where are you now in the recovery process ?
Hi everyone, I 've successfully installed cm11 using Qbking77 tutorial with the CyanogenMod Installer on my htc one but after having some problems with music playback and battery life I've decided to go back to stock.
I've successfully relocked the phone but I can't find the exact Ruu file for my phone and I've tried with other similar ruu but had no luck.
The phone is S On HBBOOT-1.57.000 RADIO -4T.29.3218.08 OS-6.09.401.5
The phone is also stuck in boot loop and recovery mode does not work.
I have found a guy with a similar problem in this site and someone told him to try to run the firmware first and then try to flash TWRP, now the problem is after downloading the firmware file when typing the cmd command adb reboot bootloader it says that it can not find any devices. I'm not really sure what to do now.
Any help appreciated!!!thanks
cesarm96 said:
Hi everyone, I 've successfully installed cm11 using Qbking77 tutorial with the CyanogenMod Installer on my htc one but after having some problems with music playback and battery life I've decided to go back to stock.
I've successfully relocked the phone but I can't find the exact Ruu file for my phone and I've tried with other similar ruu but had no luck.
The phone is S On HBBOOT-1.57.000 RADIO -4T.29.3218.08 OS-6.09.401.5
The phone is also stuck in boot loop and recovery mode does not work.
I have found a guy with a similar problem in this site and someone told him to try to run the firmware first and then try to flash TWRP, now the problem is after downloading the firmware file when typing the cmd command adb reboot bootloader it says that it can not find any devices. I'm not really sure what to do now.
Any help appreciated!!!thanks
Click to expand...
Click to collapse
Firstly, have you enabled usb debugging on your phone? And have you downloaded the most up to date adb drivers and the most up to date HTC drivers?
Because you are s on you cannot flash to downgrade your firmware
Also as your bootloader is now relocked, you cannot flash TWRP either. The bootloader needs to be unlocked to flash custom recovery
There is no RUU available for your phone, so the best option is either a guru reset which will also install stock recovery, or a nandroid backup
stovie_steve said:
Firstly, have you enabled usb debugging on your phone? And have you downloaded the most up to date adb drivers and the most up to date HTC drivers?
Because you are s on you cannot flash to downgrade your firmware
Also as your bootloader is now relocked, you cannot flash TWRP either. The bootloader needs to be unlocked to flash custom recovery
There is no RUU available for your phone, so the best option is either a guru reset which will also install stock recovery, or a nandroid backup
Click to expand...
Click to collapse
about the usb debugging if you are talking before the boot loop happened, yes I had it enable.
I'm gonna try one of those options to see if it works and then I'm gonna report back to let you know what happened.
btw thank you for the reply.
cesarm96 said:
about the usb debugging if you are talking before the boot loop happened, yes I had it enable.
I'm gonna try one of those options to see if it works and then I'm gonna report back to let you know what happened.
btw thank you for the reply.
Click to expand...
Click to collapse
You are welcome, haven't fixed anything yet but come back here again with how things are going
The only way your going to get any function from adb is through recovery, using the sideload method. You should get yourself TWRP and flash using fastboot, then boot to recovery and side load a stockish rom, say viperone or the like. I choose not to run CM or any other AOSP rom for the reasons you listed in OP among others. I currently run ViperOne comming from CM and the battery life is not even comparable. Going back to stock is going to be tough per with your version of hboot s-off is not an easy task as of yet.
MrLizm said:
The only way your going to get any function from adb is through recovery, using the sideload method. You should get yourself TWRP and flash using fastboot, then boot to recovery and side load a stockish rom, say viperone or the like. I choose not to run CM or any other AOSP rom for the reasons you listed in OP among others. I currently run ViperOne comming from CM and the battery life is not even comparable. Going back to stock is going to be tough per with your version of hboot s-off is not an easy task as of yet.
Click to expand...
Click to collapse
I'm quite new to this things so I don't understand much about it, but do you recommend installing a different rom rather then going back to stock? to be honest after all these problems I've had with cm11 I would prefer going back to stock :/
cesarm96 said:
about the usb debugging if you are talking before the boot loop happened, yes I had it enable.
I'm gonna try one of those options to see if it works and then I'm gonna report back to let you know what happened.
btw thank you for the reply.
Click to expand...
Click to collapse
You need to unlock your bootloader first via HTC dev and then flash TWRP recovery
Reboot to recovery and choose to sideload a Rom via adb - download a sense Rom of your choice. There are plenty to chose from
Unfortunately, your going to have a difficult time going back to "Stock." You can use a custom recovery to flash a "Stock" rom, as stovie_steve mentioned, a sense rom. To you the phone will be "Stock" the only difference here is your warranty is void .
108
MrLizm said:
Unfortunately, your going to have a difficult time going back to "Stock." You can use a custom recovery to flash a "Stock" rom, as stovie_steve mentioned, a sense rom. To you the phone will be "Stock" the only difference here is your warranty is void .
Click to expand...
Click to collapse
I unlocked the bootloader and rebooted the phone and everything seems to work fine. But now I don't know what I should do... Now I don't think that I want to go back to stock because it looks a bit difficult and I might end up doing something wrong and brick my phone. Is the viper rom good? I've got cm11 but as I said the battery is draining fast and I still got the music playback problem. Is it hard to install another rom? If it's not I'll probably do it.
cesarm96 said:
I unlocked the bootloader and rebooted the phone and everything seems to work fine. But now I don't know what I should do... Now I don't think that I want to go back to stock because it looks a bit difficult and I might end up doing something wrong and brick my phone. Is the viper rom good? I've got cm11 but as I said the battery is draining fast and I still got the music playback problem. Is it hard to install another rom? If it's not I'll probably do it.
Click to expand...
Click to collapse
Step 1: download a sense based ROM - ARHD, viper one, insertcoin etc onto your phone
Step 2: flash latest TWRP
Step 3: flash the ROM you downloaded
Step 4: **optional** to obtain s off, use firewater or sunshine
Thanks for the help I'm probably gonna try to install the viper one
cesarm96 said:
I unlocked the bootloader and rebooted the phone and everything seems to work fine. But now I don't know what I should do... Now I don't think that I want to go back to stock because it looks a bit difficult and I might end up doing something wrong and brick my phone. Is the viper rom good? I've got cm11 but as I said the battery is draining fast and I still got the music playback problem. Is it hard to install another rom? If it's not I'll probably do it.
Click to expand...
Click to collapse
Personally, ViperOne is the only sense based rom I will use. Its loaded with goodies and stable as they come. But there will be no harm in flashing many roms until you find something you like. Try Viper, do some shopping around, simply do a backup and flash whatever.. dont like it restore your back up. Just remember to have a current back up always. I keep ViperOne and CM installs on the sd as well as backups of both, never know what mood I be in, have the 64GB so I dont mind 5-10GB tied up by these things. Its up to You but Yes I recommend ViperOne,
Okay, so this morning I stupidly wiped my OS on accident (4.4.2 KitKat, Virgin Mobile, Rooted, S-ON) and now I need to install a fresh new one. So far nothing has yielded the results I desire, which is to just get my phone back up and running. I've tried flashing new images with fastboot and restoring from pre-made backups made with TWRP. I'm not sure what to do at this point. Any suggestions?
007manyo said:
Okay, so this morning I stupidly wiped my OS on accident (4.4.2 KitKat, Virgin Mobile, Rooted, S-ON) and now I need to install a fresh new one. So far nothing has yielded the results I desire, which is to just get my phone back up and running. I've tried flashing new images with fastboot and restoring from pre-made backups made with TWRP. I'm not sure what to do at this point. Any suggestions?
Click to expand...
Click to collapse
What happens when restoring from TWRP backup?
Sent from my XT1028 using XDA Free mobile app
rbheromax said:
What happens when restoring from TWRP backup?
Sent from my XT1028 using XDA Free mobile app
Click to expand...
Click to collapse
It gets to roughly 100%, and then claims to have failed. This only solved one issue - Instead of getting to the fist HTC boot screen, it loaded the first, then the VM splash, and then the second HTC screen, but only when rebooting from TWRP. I've tried flashing several other ROMs today, and I have no progress so far.
So. I fixed it myself, but only after trying something I didn't think would work, and it's honestly not something most people talk about when they talk about restoring to stock, as I couldn't find this tidbit anywhere. Sooo... I'll give a little list of what I did.
1 - Wiped System Partition to erase other installed ROMs. Apparently, flashing one ROM doesn't replace the first? Whatever, I did this in case I had flashed a broken ROM at some point or flashed a recovery ROM to the system partition.
2 - Wiped Cache Partition for the same reason as above. Since I had the phone sort of working at one point, I assumed that whatever it was doing had at least written something to the cache.
3 - Wiped Dalvik Cache to get rid of fragments of broken ROMs. I read somewhere that Dalvik cache needs to be wiped before installation of new ROMs in order to keep the old and new ROMs from interfering. With that assumption, and the assumption that wiping my system clean couldn't hurt any more than it did, I did that.
4 - RELOCKED THE BOOTLOADER. I have no idea what possessed me to do this. I figured that it was broken too far for me to fix, and that locking the bootloader might remove the *TAMPERED* and *UNLOCKED* flags from the bootloader. Upon further reading, I know this isn't true.... Anyhow, after using "fastboot oem lock", It locked the bootloader. At least something I did yielded results that time.
Now the one I certainly didn't expect...
5 - Ran the HTC Desire 510 Virgin Mobile RUU. Now, what's weird about this is during the time when my bootloader was unlocked, RUU never detected my phone. After relocking the bootloader, however, RUU detected my phone almost instantly and in ten minutes my OS was back up and running.
The only thing I used TWRP for in this process was wiping my partitions. I didn't have to fastboot flash a ROM or load a recovery. I just think that more people should know that restoring to or installing a factory new OS, with HTC at least, is much easier than most articles or forums make it sound.
Tried, but getting battery error
5 - Ran the HTC Desire 510 Virgin Mobile RUU. Now, what's weird about this is during the time when my bootloader was unlocked, RUU never detected my phone. After relocking the bootloader, however, RUU detected my phone almost instantly and in ten minutes my OS was back up and running.
The only thing I used TWRP for in this process was wiping my partitions. I didn't have to fastboot flash a ROM or load a recovery. I just think that more people should know that restoring to or installing a factory new OS, with HTC at least, is much easier than most articles or forums make it sound.
Click to expand...
Click to collapse
Had root, custom ROM, and removed some bloatware. Called VM to activate Wi-Fi hotspot. (Boy was that a mistake!). It didn't activate so CS Rep said to power down, remove battery for 1 min and she is going to go into phone to re-provision and call me back after she was finished. I never got the call back! After several reboots from VM rep, the phone ended up on the white HTC splash screen. I could get into recovery TWRP where I found the OS was missing.
So I started searching xda and found this post.........
Got everything up to step 5... Went to run the VM RUU and got an error message that the battery was below 30% when in fact it was at 100%. Tried NUMEROUS times with the same result...
HELP!! :crying:
EDIT:
Searching around xda, I gained alot of useful knowledge of this phone and found the "fix". Thank you all so much for everything! I used this link http://forum.xda-developers.com/desire-510/development/virgin-sprint-htc-desire-510-stock-t2961521 to finally fix it. I thought I was going to have to buy a new phone! :victory:
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.