Related
I already rooted my First on 1.05 and want to update to 1.08 since I want to go S-OFF and I saw in that thread it's for 1.08.
I tried the RUU dozens of times on 2 completely different Windows 7 x64 PCs. It sat at the Sending...... step for awhile with the phone on an HTC logo screen, and then ended in Error 155. I also tried booting into FASTBOOT USB and trying it. Same thing. Has anyone got the RUU to work? If so, what's your MD5 hash? Mine is 425MB and I would think it's a good copy since it was able to extract itself into Appdata\Local\Temp folder with no errors.
I saw in the RUU thread there's also just the OTA .zip. It won't install with TWRP. I'd have to flash to stock recovery to install it, but I couldn't find any place to get the stock recovery.
Any solutions?
GnatGoSplat said:
I already rooted my First on 1.05 and want to update to 1.08 since I want to go S-OFF and I saw in that thread it's for 1.08.
I tried the RUU dozens of times on 2 completely different Windows 7 x64 PCs. It sat at the Sending...... step for awhile with the phone on an HTC logo screen, and then ended in Error 155. I also tried booting into FASTBOOT USB and trying it. Same thing. Has anyone got the RUU to work? If so, what's your MD5 hash? Mine is 425MB and I would think it's a good copy since it was able to extract itself into Appdata\Local\Temp folder with no errors.
I saw in the RUU thread there's also just the OTA .zip. It won't install with TWRP. I'd have to flash to stock recovery to install it, but I couldn't find any place to get the stock recovery.
Any solutions?
Click to expand...
Click to collapse
I have a related problem, after bricking the phone I flashed the RUU and I cannot re unlock the bl again, anyway try to flash cwm instead of twrp and then retry with the Ota.zip. I don't know if this can solve your problem, but I've noticed that with twrp some roms did not work to me. I think also that the RUU does not work with unlocked bl, so you have first to relock, but if you do this you could have the same problem I have, that is you can't re unlock the bl... I am not an expert so I cannot assure you that these procedures are ok...
GnatGoSplat said:
I already rooted my First on 1.05 and want to update to 1.08 since I want to go S-OFF and I saw in that thread it's for 1.08.
I tried the RUU dozens of times on 2 completely different Windows 7 x64 PCs. It sat at the Sending...... step for awhile with the phone on an HTC logo screen, and then ended in Error 155. I also tried booting into FASTBOOT USB and trying it. Same thing. Has anyone got the RUU to work? If so, what's your MD5 hash? Mine is 425MB and I would think it's a good copy since it was able to extract itself into Appdata\Local\Temp folder with no errors.
I saw in the RUU thread there's also just the OTA .zip. It won't install with TWRP. I'd have to flash to stock recovery to install it, but I couldn't find any place to get the stock recovery.
Any solutions?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2287811
just flash 1.08 odexed or deodexed
Sent from my HTC first using xda premium
HarryCustom said:
I have a related problem, after bricking the phone I flashed the RUU and I cannot re unlock the bl again, anyway try to flash cwm instead of twrp and then retry with the Ota.zip. I don't know if this can solve your problem, but I've noticed that with twrp some roms did not work to me. I think also that the RUU does not work with unlocked bl, so you have first to relock, but if you do this you could have the same problem I have, that is you can't re unlock the bl... I am not an expert so I cannot assure you that these procedures are ok...
Click to expand...
Click to collapse
Thanks, that was the problem; I had to relock the bootloader and then the RUU worked. I was able to re-unlock the bootloader with no problems though. I used the All-In-One kit to do it and reused the Unlock_code.bin that I used on 1.05.
kornklown69 said:
http://forum.xda-developers.com/showthread.php?t=2287811
just flash 1.08 odexed or deodexed
Click to expand...
Click to collapse
I must be blind, I swear I looked for flashable zips but couldn't find them. Too late since I already flashed the RUU, but hopefully that will help someone else who runs into this issue.
GnatGoSplat said:
Thanks, that was the problem; I had to relock the bootloader and then the RUU worked. I was able to re-unlock the bootloader with no problems though. I used the All-In-One kit to do it and reused the Unlock_code.bin that I used on 1.05.
I must be blind, I swear I looked for flashable zips but couldn't find them. Too late since I already flashed the RUU, but hopefully that will help someone else who runs into this issue.
Click to expand...
Click to collapse
So the kornklown69 theory that also mine is correct, is S-OFF the problem. To re-unlock probably the phone must be S-ON.
So the procedure could be: Relock -> S-ON -> Re-unlock -> S-OFF.
But I don't understand how to obtain S-ON again.
Anyway my phone is Relocked and I can install custom roms, kernels and root it... Very strange!
That makes sense. With my original Droid Incredible, an S-OFF hack came out before HTC official BL unlocking and there was never any reason to unlock it since S-OFF was all you needed to install custom ROMs and root. So if you're S-OFF, there's probably no need to re-unlock it.
Having the same issue. In another thread, jmz said:
In my stock Rom thread there are new files up. They are the ota roms. So if you are running stock, download the odex one ending in 1.08 and flash in recovery, no need to wipe data. Then pull boot.img and fastboot flash it. You now have the ota software. I will post instructions to upgrade the firmware that came with the ota
Click to expand...
Click to collapse
I know what the odexed rom is, but can someone explain how to get the boot.img and fastboot flash it? Or should I just relock the bootloader?
I am relatively new to the HTC. I am running a Stock rooted image with TWRP 2.6.3.0 recovery.
The OTA for 4.3 came down and whenever I start the install the phone reboots and ends up in twrp recovery and I do not know where to go from there. I tried searching the forums but the search is down at the moment.
Here comes the Noob question : A little help please as I am not sure where to go next?
I just asked almost the same question. One thing everyone says is don't take the OTA update.
I found a few places with the pre-rooted stock ROM update, but it does not include the firmware update, that is a separate flashable zip, but I'm not sure how to update the "Full Firmware w/o hboot, boot, recovery" without S-off. I don't know if doing the "full firmware update" will mess up my recovery/root.
http://forum.xda-developers.com/showthread.php?t=2467607
http://forum.xda-developers.com/showthread.php?p=46110767
generosity21 said:
I just asked almost the same question. One thing everyone says is don't take the OTA update.
I found a few places with the pre-rooted stock ROM update, but it does not include the firmware update, that is a separate flashable zip, but I'm not sure how to update the "Full Firmware w/o hboot, boot, recovery" without S-off. I don't know if doing the "full firmware update" will mess up my recovery/root.
http://forum.xda-developers.com/showthread.php?t=2467607
http://forum.xda-developers.com/showthread.php?p=46110767
Click to expand...
Click to collapse
I have been all over the forums looking at this and came up with squat.
If I take the OTA will I loose root? Can't seem to find an answer to that.
I was running an earlier version of twrp and thought that might be the issue but after updating twrp I am still at the same place. The sprint update notifications are still coming.
If I find something I will post it here.
Must be on stock firmware and recovery to take the update guys.... It has been posted numerous times. You must also ahve the stock kernel.
Yes you will lose root if you take the OTA, you always do. Also TWRP appears to be broken with 4.3, no responsive, etc, etc
jziggy101 said:
I am relatively new to the HTC. I am running a Stock rooted image with TWRP 2.6.3.0 recovery.
The OTA for 4.3 came down and whenever I start the install the phone reboots and ends up in twrp recovery and I do not know where to go from there. I tried searching the forums but the search is down at the moment.
Here comes the Noob question : A little help please as I am not sure where to go next?
Click to expand...
Click to collapse
you can't flash the update with custom recovery installed, you need thev stock recovery image which is posted numerous times in this forum
jziggy101 said:
The OTA for 4.3 came down and whenever I start the install the phone reboots and ends up in twrp recovery and I do not know where to go from there.
Click to expand...
Click to collapse
You have to have stock recovery to take the OTA
generosity21 said:
I just asked almost the same question. One thing everyone says is don't take the OTA update.
Click to expand...
Click to collapse
You can take the OTA if you are prepared for, and know what to do - also, don't take it if you are currently S-ON and ever want S-OFF because it comes with a new hboot.
jziggy101 said:
If I take the OTA will I loose root? Can't seem to find an answer to that.
Click to expand...
Click to collapse
Yes, you will probably lose root unless you are using the OTA preservation function of SuperSU and it works for you, but either way, it is easy to get it back.
Bottom line, how you take the OTA depends on whether you are S-ON or S-OFF, the latter is much easier. Assuming you are S-ON and running the Sprint stock ROM, here is what you need to do.
1. Flash stock recovery.
2. Lock the bootloader
3. Take the OTA update
4. Unlock the bootloader
5. Flash custom recovery (TWRP)
6. Flash root (SuperSU)
If you are S-off you can skip numbers 2 and 4.
Aldo101t said:
you can't flash the update with custom recovery installed, you need thev stock recovery image which is posted numerous times in this forum
Click to expand...
Click to collapse
Thanks for the replies. It's very confusing whether people are referencing the OTA update, or the tweaked, rooted downloadable update (http://forum.xda-developers.com/showthread.php?p=46110767). This forum should be friendly to questions when things are confusing.
Even with the two replies on this thread, it's still not clear to me if the downloadable (NOT OTA) updates can be flashed with a custom recovery, or what the procedure is for an S-On device regarding firmware and ROM updates. Sorry to offend anyone if they feel this has been answered somewhere in the forums, but it's still unclear to some of us.
EDIT:
@PillowMetal Thanks for the very helpful reply. I guess the next question is, is it possible to get S-Off on 1.31.651.2 without losing everything?
Kraizk said:
Must be on stock firmware and recovery to take the update guys.... It has been posted numerous times. You must also ahve the stock kernel.
Yes you will lose root if you take the OTA, you always do. Also TWRP appears to be broken with 4.3, no responsive, etc, etc
Click to expand...
Click to collapse
If your not stock ota will mess you up big time. I just rooted my HTC one on sprint with the update that was on a swap out for bad speakers . Twrp isn't responsive if you use the one in toolkit. I downloaded 2.6.3 loaded it in the data folder of toolkit installed through the toolkit and bam... I got response out of Twrp. I'll find the link and post for you guys.
Sent from my SGH-M919 using Tapatalk 4
generosity21 said:
@PillowMetal Thanks for the very helpful reply. I guess the next question is, is it possible to get S-Off on 1.31.651.2 without losing everything?
Click to expand...
Click to collapse
Not without losing everything because it requires tricking your bootloader by writing to your misc partition, then running the 1.29 RUU - http://forum.xda-developers.com/showthread.php?t=2390821
http://techerrata.com/browse/twrp2/m7wls
This is the link for people who are stock and unlocking their phone. If you're using the toolkit put it in the data folder and rename to twrp. Be careful though the other files are the same name but in capital letters! Flash it and u will have responsive twrp and rooted 4.3 ota
Sent from my SGH-M919 using Tapatalk 4
---------- Post added at 02:10 PM ---------- Previous post was at 01:34 PM ----------
Anyone having poor reception?
Sent from my SGH-M919 using Tapatalk 4
PillowMetal said:
Not without losing everything because it requires tricking your bootloader by writing to your misc partition, then running the 1.29 RUU - http://forum.xda-developers.com/showthread.php?t=2390821
Click to expand...
Click to collapse
Tried this once more, and successfully got S-off without downgrading anything, as a few others have reported.
http://forum.xda-developers.com/showthread.php?t=2314582
Brand new device Stock 1.29 Rom Uninstalled SuperSU Unrooted for Updates
PillowMetal said:
You have to have stock recovery to take the OTA
You can take the OTA if you are prepared for, and know what to do - also, don't take it if you are currently S-ON and ever want S-OFF because it comes with a new hboot.
Yes, you will probably lose root unless you are using the OTA preservation function of SuperSU and it works for you, but either way, it is easy to get it back.
Bottom line, how you take the OTA depends on whether you are S-ON or S-OFF, the latter is much easier. Assuming you are S-ON and running the Sprint stock ROM, here is what you need to do.
1. Flash stock recovery.
2. Lock the bootloader
3. Take the OTA update
4. Unlock the bootloader
5. Flash custom recovery (TWRP)
6. Flash root (SuperSU)
If you are S-off you can skip numbers 2 and 4.
Click to expand...
Click to collapse
Think I messed up a step in my attempt to return to unroot to be ready to get the 4.3 jellybean update. I was stock rom 1.29, rooted, SuperSU, twerp 2.6.3. Unlocked sim. I unistalled SuperSU using the full unroot option and relocked the bootloader. When the phone attempts to update it reboots into the bootloader straight into fastboot. Will not reboot and stay in hboot. Recovery option does nothing. Do I even want the ota 1.31? Do I just skip the OTA 1.31 and get the 4.3 jellybean update. I'm new first Android phone. Sorry for the idiocy I have portrayed here. Hope someone can help with knowledge of OTA's and Jellybean update. My problem seems so simple compared to all the other posts I read but I can't seem to figure it out on my own. Thanks everyone
upowersystems said:
Think I messed up a step in my attempt to return to unroot to be ready to get the 4.3 jellybean update. I was stock rom 1.29, rooted, SuperSU, twerp 2.6.3. Unlocked sim. I unistalled SuperSU using the full unroot option and relocked the bootloader. When the phone attempts to update it reboots into the bootloader straight into fastboot. Will not reboot and stay in hboot. Recovery option does nothing. Do I even want the ota 1.31? Do I just skip the OTA 1.31 and get the 4.3 jellybean update. I'm new first Android phone. Sorry for the idiocy I have portrayed here. Hope someone can help with knowledge of OTA's and Jellybean update. My problem seems so simple compared to all the other posts I read but I can't seem to figure it out on my own. Thanks everyone
Click to expand...
Click to collapse
Did you flash stock recovery? The OTA needs that. You did not need to unroot though. Also not sure if having an unlocked SIM interferes with OTA, never performed that myself. Since we don't have RUUs for anything later than 1.29, then yes, you will need to take the 1.31 OTA update first, then the 3.04 update.
Twerp to Stock recovery
PillowMetal said:
Did you flash stock recovery? The OTA needs that. You did not need to unroot though. Also not sure if having an unlocked SIM interferes with OTA, never performed that myself. Since we don't have RUUs for anything later than 1.29, then yes, you will need to take the 1.31 OTA update first, then the 3.04 update.
Click to expand...
Click to collapse
Darn, no I did not flash the stock recovery. Also I read another thread said I needed to unroot!lol So I was back tracing my steps to unroot, so I thought.. I did save the original backup before installing Twerp 2.6.3 and rooting so its in there if I can get to it. I really dont know how to proceed from here. There are no options in the bootloader to proceed.
Twerp vs Stock recovery
PillowMetal said:
Did you flash stock recovery? The OTA needs that. You did not need to unroot though. Also not sure if having an unlocked SIM interferes with OTA, never performed that myself. Since we don't have RUUs for anything later than 1.29, then yes, you will need to take the 1.31 OTA update first, then the 3.04 update.
Click to expand...
Click to collapse
Do I need to figure out how to flash or return to stock recovery from Twerp or can I simploy flash the 1.29 ruu back in to the device for a return to stock?
Twerp 2.6.3
PillowMetal said:
Did you flash stock recovery? The OTA needs that. You did not need to unroot though. Also not sure if having an unlocked SIM interferes with OTA, never performed that myself. Since we don't have RUUs for anything later than 1.29, then yes, you will need to take the 1.31 OTA update first, then the 3.04 update.
Click to expand...
Click to collapse
Kraizk said:
Must be on stock firmware and recovery to take the update guys.... It has been posted numerous times. You must also ahve the stock kernel.
Yes you will lose root if you take the OTA, you always do. Also TWRP appears to be broken with 4.3, no responsive, etc, etc
Click to expand...
Click to collapse
Maybe you can help. Will a re-install of the stock ruu 1.29 without removing twerp 2.6.3 and reverting to stock recovery cause issues.. Will this just completely re-install everything including stock Recovery or will twerp remain. I am running stock 1.29 rom, did save an original backup when I loaded twerp. How would I get in it to load it. Then I would not need to load the complete ruu. When I try for the ota it used to reboot to twerp. Since I unrooted it reboots to bootloader and there are NO options for load, Recovery option doesnt work. I have asked this question on several threads no one seems to know or its too simple for them to reply since I'm a newb. Thanks
upowersystems said:
Maybe you can help. Will a re-install of the stock ruu 1.29 without removing twerp 2.6.3 and reverting to stock recovery cause issues.. Will this just completely re-install everything including stock Recovery or will twerp remain. I am running stock 1.29 rom, did save an original backup when I loaded twerp. How would I get in it to load it. Then I would not need to load the complete ruu. When I try for the ota it used to reboot to twerp. Since I unrooted it reboots to bootloader and there are NO options for load, Recovery option doesnt work. I have asked this question on several threads no one seems to know or its too simple for them to reply since I'm a newb. Thanks
Click to expand...
Click to collapse
Are you S-Off? Is so, the easiest way to to get up to date for you would be to RUU back to 1.29 which will restore everything on your phone back to stock including recovery. Make sure you copy anything you want to keep off your phone's internal memory (/sdcard) because it will wipe that too.
But from there, you can then easily take the OTA update for 1.31, then take the update for 3.04. Now you have the latest and greatest and can now flash TWRP, SuperSU, and any 4.3 ROM you want. With S-Off, you do not need the bootloader unlocked, but if you want to, you can flash an old hboot 1.29 from May or earlier and use revone -u, or go through htcdev to unlock. But like I said, totally unnecessary and more of a pain for me than it is worth.
Now, if you are S-ON, that is a totally different story, you cannot flash back to 1.29 RUU unless you still on 1.29 and have not updated to 1.31 yet. If you are currently on 1.31 you will have to try and restore the backup you said you had through TWRP, flash stock recovery from fastboot, re-lock your bootloader and all kinds of other crap to get to 3.04 and unlocked and rooted again.
You would have to tell me more about what condition your phone is currently in. hboot version? recovery custom or stock? ROM version installed? S-On or S-Off, etc.
Current State
PillowMetal said:
Are you S-Off? Is so, the easiest way to to get up to date for you would be to RUU back to 1.29 which will restore everything on your phone back to stock including recovery. Make sure you copy anything you want to keep off your phone's internal memory (/sdcard) because it will wipe that too.
But from there, you can then easily take the OTA update for 1.31, then take the update for 3.04. Now you have the latest and greatest and can now flash TWRP, SuperSU, and any 4.3 ROM you want. With S-Off, you do not need the bootloader unlocked, but if you want to, you can flash an old hboot 1.29 from May or earlier and use revone -u, or go through htcdev to unlock. But like I said, totally unnecessary and more of a pain for me than it is worth.
Now, if you are S-ON, that is a totally different story, you cannot flash back to 1.29 RUU unless you still on 1.29 and have not updated to 1.31 yet. If you are currently on 1.31 you will have to try and restore the backup you said you had through TWRP, flash stock recovery from fastboot, re-lock your bootloader and all kinds of other crap to get to 3.04 and unlocked and rooted again.
You would have to tell me more about what condition your phone is currently in. hboot version? recovery custom or stock? ROM version installed? S-On or S-Off, etc.
Click to expand...
Click to collapse
Was told if I un-rooted and relocked the bootloader I should be able to update. This is a brand new phone. No data to worry about losing.
Currently:
Stock ROM 1.29, S-On, (Was rooted) Now Unrooted
Hboot 1.44 (Bootloader relocked)
Twerp Recovery (although with attempt to update to 1.31 twerp did not open as it did in prior attempts to update before unroot)
Now You have opened an interesting subject. Do I need to S-off before any updates to defeat the new hboot? New stuff is being written for the new hboot as we speak right? Read a thread last night about it. Sounded like they could s-off a 1.31 and I wouldn't need to worry about s-off'ing before upgrading. It also seems like I should be able to re load the backup of the stock recovery somehow and skip the complete load of the ruu 1.29 since I am already running it. I am probably making somethong more difficult than it needs to be but I would like to learn the little details. My first Android here. Want to learn quickly here as I Also bought the New 4g LTE Nexus 7 tablet with jelly bean. I get 4g LTE from T-mobile and just hotspot my phone.
upowersystems said:
Was told if I un-rooted and relocked the bootloader I should be able to update. This is a brand new phone. No data to worry about losing.
Currently:
Stock ROM 1.29, S-On, (Was rooted) Now Unrooted
Hboot 1.44 (Bootloader relocked)
Twerp Recovery (although with attempt to update to 1.31 twerp did not open as it did in prior attempts to update before unroot)
Now You have opened an interesting subject. Do I need to S-off before any updates to defeat the new hboot? New stuff is being written for the new hboot as we speak right? Read a thread last night about it. Sounded like they could s-off a 1.31 and I wouldn't need to worry about s-off'ing before upgrading. It also seems like I should be able to re load the backup of the stock recovery somehow and skip the complete load of the ruu 1.29 since I am already running it. I am probably making somethong more difficult than it needs to be but I would like to learn the little details. My first Android here. Want to learn quickly here as I Also bought the New 4g LTE Nexus 7 tablet with jelly bean. I get 4g LTE from T-mobile and just hotspot my phone.
Click to expand...
Click to collapse
If you don't want to go the RUU route, then the condition your phone is currently in would only require you to flash stock recovery from 1.29.651.10 (which I got from the actual OTA file). The problem is that your bootloader is now locked and your are S-ON, so you will not be able to flash stock recovery unless you unlock again. If you still have the unlock.bin file from htcdev, that will still work if was done on your current hboot version, otherwise, you would have to visit the site again. Then flash stock recovery, and relock bootloader again. Then the 1.31 update will succeed followed by the 3.04 update.
As far as S-OFF, if you ever want it, you should get it now before updating to anything - even 1.31 (as long as the date on your hboot is May 2013 or earlier). Because, you WILL get the new hboots when you update to 1.31 and 3.04 and since you are S-ON, you will be stuck with it. There is no guarantee that you will ever be able to get S-OFF again with the new hboots. People on hboot 1.54 have been waiting and clamoring for months and there has been no progress and other phones have never even been able to get S-OFF.
Using revone to S-OFF will not wipe your phone or remove anything, it does not require root, and it you do not need to be unlocked. I have performed it from the computer 3 times on Sprint phones and even have made a post about how to make it succeed. There is also a video showing how it can be done on the phone too via terminal emulator, but that method requires root.
Having S-OFF just makes life so much easier, but with it carries great responsibility because security has been turned off and you need to know what you are flashing or you can run into trouble. But as long as you can get to the bootloader, you can recover.
PillowMetal said:
You have to have stock recovery to take the OTA
You can take the OTA if you are prepared for, and know what to do - also, don't take it if you are currently S-ON and ever want S-OFF because it comes with a new hboot.
Yes, you will probably lose root unless you are using the OTA preservation function of SuperSU and it works for you, but either way, it is easy to get it back.
Bottom line, how you take the OTA depends on whether you are S-ON or S-OFF, the latter is much easier. Assuming you are S-ON and running the Sprint stock ROM, here is what you need to do.
1. Flash stock recovery.
2. Lock the bootloader
3. Take the OTA update
4. Unlock the bootloader
5. Flash custom recovery (TWRP)
6. Flash root (SuperSU)
If you are S-off you can skip numbers 2 and 4.
Click to expand...
Click to collapse
On the att variant you don't need to relock the boot loader to ota.
Sent from my XT1058 using Tapatalk 2
Hello,
I seem to have gotten myself into a bind, and looking ahead to the 4.4 KitKat release, I am not sure how to get myself out of it. I've already done a lot of research and troubleshooting on my own, but can't seem to resolve the problem.
I purchased an HTC One Google Play edition, and decided to root to apply a quick fix with utilizing the Nexus 5 launcher. To that end, I unlocked my bootloader and rooted. I had a Windows 7 partition on my Mac at the time, but it was giving me trouble. Since the root, I became dissatisfied with the performance of the phone, and attempted to restore to factory.
I flashed stock recovery again, and relocked the bootloader. Now the bootloader shows as "relocked" and "tampered." However, in between root and unroot attempts, I upgraded my partition to Windows 8.1. Suddenly, when in fastboot, my HTC One shows up as "USB Device not Recognized," meaning I cannot issue any commands using ADB. If I don't get "waiting for device" I get "device offline," and my device is still rooted.
Whenever I uninstall Super SU, it's right back upon reboot.
I currently have S-ON. I am unable to get S-OFF because my computer doesn't recognize the phone when in fastboot. I tried updating and downloading different HTC Drivers to no avail.
I want to attempt to get my device back to its exact status when I bought the phone. Meaning, I want to have my bootloader as locked, keep S-ON (although I don't mind having S-OFF temporarily), and flash the stock RUU/Recovery. Upon Google Search, this seems easy, but there is not much out there for the GPE. A lot of the guides I have found are for Sense versions. My phone is not a GPE conversion. It is an actual GPE phone purchased on the Play Store.
Phone is functional, but I am concerned when 4.4 comes out, the update will fail or brick.
Sorry if this thread is long. I wanted to be as detailed as possible when asking for help. Thanks again to anyone on XDA who can assist.
mikhailov1 said:
Hello,
I seem to have gotten myself into a bind, and looking ahead to the 4.4 KitKat release, I am not sure how to get myself out of it. I've already done a lot of research and troubleshooting on my own, but can't seem to resolve the problem.
I purchased an HTC One Google Play edition, and decided to root to apply a quick fix with utilizing the Nexus 5 launcher. To that end, I unlocked my bootloader and rooted. I had a Windows 7 partition on my Mac at the time, but it was giving me trouble. Since the root, I became dissatisfied with the performance of the phone, and attempted to restore to factory.
I flashed stock recovery again, and relocked the bootloader. Now the bootloader shows as "relocked" and "tampered." However, in between root and unroot attempts, I upgraded my partition to Windows 8.1. Suddenly, when in fastboot, my HTC One shows up as "USB Device not Recognized," meaning I cannot issue any commands using ADB. If I don't get "waiting for device" I get "device offline," and my device is still rooted.
Whenever I uninstall Super SU, it's right back upon reboot.
I currently have S-ON. I am unable to get S-OFF because my computer doesn't recognize the phone when in fastboot. I tried updating and downloading different HTC Drivers to no avail.
I want to attempt to get my device back to its exact status when I bought the phone. Meaning, I want to have my bootloader as locked, keep S-ON (although I don't mind having S-OFF temporarily), and flash the stock RUU/Recovery. Upon Google Search, this seems easy, but there is not much out there for the GPE. A lot of the guides I have found are for Sense versions. My phone is not a GPE conversion. It is an actual GPE phone purchased on the Play Store.
Phone is functional, but I am concerned when 4.4 comes out, the update will fail or brick.
Sorry if this thread is long. I wanted to be as detailed as possible when asking for help. Thanks again to anyone on XDA who can assist.
Click to expand...
Click to collapse
try this http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
it worked for some users
Thanks. Will try when I get home. I was able to use my Win 7 computer at work to unlock the boot loader again, but I cannot get S Off. I ran rumrunner and it looked like it was working, but then said FATAL: download update. Is there no rumrunner for GPE?
Sent from my HTC One using Tapatalk
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
mikhailov1 said:
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
You got stock rom and stock recovery ryt... lock the bootloader and check for update
Prash8429 said:
You got stock rom and stock recovery ryt... lock the bootloader and check for update
Click to expand...
Click to collapse
Yeah I have stock rom and I removed TWRP and flashed stock recovery. Because I did two factory restores from bootloader, I'm assuming the stock recovery is working properly, but I'm a noob at this stuff so I could be wrong.
Going to relock the bootloader, remove SuperSU, and attempt the update when it hits. Hopefully it will work.
Thanks for your help! Since I'm a new member, how do I add to your thanks meter? Want to make sure you're properly....thanked.
mikhailov1 said:
Yeah I have stock rom and I removed TWRP and flashed stock recovery. Because I did two factory restores from bootloader, I'm assuming the stock recovery is working properly, but I'm a noob at this stuff so I could be wrong.
Going to relock the bootloader, remove SuperSU, and attempt the update when it hits. Hopefully it will work.
Thanks for your help! Since I'm a new member, how do I add to your thanks meter? Want to make sure you're properly....thanked.
Click to expand...
Click to collapse
you can still get OTA with a rooted phone, as long as you have stock recovery and flashed stock ruu.... tip if your having trouble with flashing ruu change the zip file name to something simple like ruu.zip worked for me.:good:
mikhailov1 said:
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Can you tell me if your bootloader was 1.54 or 1.55? I have been unable to get Windows 8.1 to recognize the 1.54 bootloader. It always says "device not recognized" If yours was 1.54.0000 I will try this fix. Thanks.
I am 1.54.
Sent from my Nexus 5 using Tapatalk
Thanks for this, helped me out alot
Sent from my HTC One using XDA Premium 4 mobile app
Hello, I have rooted (s-on) my Htc one m8 Harmon/Kardon edition. I have seen a lot of threads and guides showing how to do this but none of them seem to apply to my specific cid, which is SPCS_004. I haven't been able to find any compatible nandroid backups. I think maybe im just in over my head and I don't want to mess anything up....can anyone point me in the right direction?
darth_skater said:
Hello, I have rooted (s-on) my Htc one m8 Harmon/Kardon edition. I have seen a lot of threads and guides showing how to do this but none of them seem to apply to my specific cid, which is SPCS_004. I haven't been able to find any compatible nandroid backups. I think maybe im just in over my head and I don't want to mess anything up....can anyone point me in the right direction?
Click to expand...
Click to collapse
Just to be clear, I have installed a custom rom and I am now wanting to go back to the original stock rom.....and also the stock recovery if possible so I can install OTA updates.
darth_skater said:
Just to be clear, I have installed a custom rom and I am now wanting to go back to the original stock rom.....and also the stock recovery if possible so I can install OTA updates.
Click to expand...
Click to collapse
RUU is the easiest way to return to stock
BD619 said:
RUU is the easiest way to return to stock
Click to expand...
Click to collapse
So if i just run that, i will be completely back to stock? and if I have the hk model, it is definitely compatible?
darth_skater said:
So if i just run that, i will be completely back to stock? and if I have the hk model, it is definitely compatible?
Click to expand...
Click to collapse
Yes it will wipe your phone just like it came from the factory, so backup anything important to your PC.
Yes there a HK RUU's and non HK RUU's in the thread I linked.
You can download the RUU directly from HTC:
http://www.htc.com/us/support/htc-one-m8-harman-kardon-edition-sprint/news/
It is located at the bottom of the page. But you might want to wait a few days and download the Lollipop RUU when it releases. It will replace the current KK version once approved and FOTA is pushed out.
BD619 said:
Yes it will wipe your phone just like it came from the factory, so backup anything important to your PC.
Yes there a HK RUU's and non HK RUU's in the thread I linked.
Click to expand...
Click to collapse
It threw me an error. ERROR [155]: UNKNOWN ERROR the ROM update utility cannot update your android phone. Please get the correct ROM update utility and try again. This is what I was trying to avoid. Now my phone won't boot at all.
darth_skater said:
It threw me an error. ERROR [155]: UNKNOWN ERROR the ROM update utility cannot update your android phone. Please get the correct ROM update utility and try again. This is what I was trying to avoid. Now my phone won't boot at all.
Click to expand...
Click to collapse
Here are some things to try.
Did you re-lock your bootloader?
Try a different USB port (USB2 work best)
Try a different PC.
To get back to bootloader press power vol up until the screen turns black then hold vol down.
If you know how to use adb/fastboot commands you can open a cmd and type
fastboot reboot-bootloader
BD619 said:
Here are some things to try.
Did you re-lock your bootloader?
Try a different USB port (USB2 work best)
Try a different PC.
To get back to bootloader press power vol up until the screen turns black then hold vol down.
If you know how to use adb/fastboot commands you can open a cmd and type
fastboot reboot-bootloader
Click to expand...
Click to collapse
I did not re lock my bootloader. I tried a different usb port, with no luck. I don't have another PC to try it with. What should I do to at least get my phone working in the meantime? even if it isn't stock? Can I just flash a rom through recovery?
darth_skater said:
I did not re lock my bootloader. I tried a different usb port, with no luck. I don't have another PC to try it with. What should I do to at least get my phone working in the meantime? even if it isn't stock? Can I just flash a rom through recovery?
Click to expand...
Click to collapse
If you are s-on you have to re-lock the bootloader for it to work.
You should be able to flash a rom thru recovery.
BD619 said:
If you are s-on you have to re-lock the bootloader for it to work.
You should be able to flash a rom thru recovery.
Click to expand...
Click to collapse
I AM BACK IN BUSINESS! Thank you so much for your help.
darth_skater said:
I AM BACK IN BUSINESS! Thank you so much for your help.
Click to expand...
Click to collapse
Glad I could help
Hey guy
So i need to update firmware currently on 1.32.531.33 on my t mobile htc one m9 s-on. I was gonna use ruu.exe from herehttp://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022. To my understading this will unroot and flash stock rom and i will be able update via OTA. Am I suppose to use the 1.32.531.33exe or 2.7.531.6exe(since on trying to update it)? Do I need to be s-off to use? Will this relock my bootloader? Is there any other changes in adb I need to make. Anything else I should be on the lookout for? Planning on rerooting after update. I couldnt find a guide with this info so any help is much appreciated. Thanks!
Accidental Genius said:
Hey guy
So i need to update firmware currently on 1.32.531.33 on my t mobile htc one m9 s-on. I was gonna use ruu.exe from herehttp://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022. To my understading this will unroot and flash stock rom and i will be able update via OTA. Am I suppose to use the 1.32.531.33exe or 2.7.531.6exe(since on trying to update it)? Do I need to be s-off to use? Will this relock my bootloader? Is there any other changes in adb I need to make. Anything else I should be on the lookout for? Planning on rerooting after update. I couldnt find a guide with this info so any help is much appreciated. Thanks!
Click to expand...
Click to collapse
If you are looking to upgrade to the latest 2.11.531.19, you can get the RUU here.
You do not need to S-Off unless you plan on flashing older or intl firmware, Ruu will not relock the bootloader.
keep in mind, running RUU will completely wipe the phone, so Backup.
I would
1. Run latest RUU let it boot and set up.
2. Reboot to bootloader, flash Twrp (fastboot flash recovery twrp-2.8.7.0-hima.img)
3. Reboot to recovery and flash SuperSU here.
Unless you are going to flash roms then you only need to flash the firmware and twrp and rom
You can get the firmware in my thread here
Hope this helps
kc6wke said:
If you are looking to upgrade to the latest 2.11.531.19, you can get the RUU here.
You do not need to S-Off unless you plan on flashing older or intl firmware, Ruu will not relock the bootloader.
keep in mind, running RUU will completely wipe the phone, so Backup.
I would
1. Run latest RUU let it boot and set up.
2. Reboot to bootloader, flash Twrp (fastboot flash recovery twrp-2.8.7.0-hima.img)
3. Reboot to recovery and flash SuperSU here.
Unless you are going to flash roms then you only need to flash the firmware and twrp and rom
You can get the firmware in my thread here
Hope this helps
Click to expand...
Click to collapse
Thanks! I took a chance yesterday and ran the 1.32.531.33.exe to play it safe and updated via OTA to 2.7.531.6. But for future reference is it's okay to run RUUs that are above current firmware or do you have to use the one your current firmware matches (for instance running 2.7.531.6.exe when the device firmware is on 1.32.531.33). Also will roms running on older firmware work if device firmware is on 2.11.531.19?
Accidental Genius said:
Thanks! I took a chance yesterday and ran the 1.32.531.33.exe to play it safe and updated via OTA to 2.7.531.6. But for future reference is it's okay to run RUUs that are above current firmware or do you have to use the one your current firmware matches (for instance running 2.7.531.6.exe when the device firmware is on 1.32.531.33). Also will roms running on older firmware work if device firmware is on 2.11.531.19?
Click to expand...
Click to collapse
With S-on you can only use current of newer firmware.
They might, depends the roms base.
Hey guys,
I just got HTC ONE M9 T-Mobile version. I'm trying to unlock it. Saw a bunch of stuff online and keep trying everything what is out there. Tried to unlock it from htcdev but it says token is too long. I copied it multiple times the way it was described, still nothing happened. Copied it piece by piece, typed it... nothing worked same thing. Questions is this, I can't get it to root, unlock bootloader, s-off or any of that so what's going to happen if I install a RUU which is rooted so at least I'll have a start cause now I can't do ANYTHING. Whatever ideas you have, please let me know.
I tried htcdev, sunshine, kingroot, kingoroot, supersu, root apps.... nothing. The tmobile unlock app, no chance... Thanks
dohcvtec said:
Hey guys,
I just got HTC ONE M9 T-Mobile version. I'm trying to unlock it. Saw a bunch of stuff online and keep trying everything what is out there. Tried to unlock it from htcdev but it says token is too long. I copied it multiple times the way it was described, still nothing happened. Copied it piece by piece, typed it... nothing worked same thing. Questions is this, I can't get it to root, unlock bootloader, s-off or any of that so what's going to happen if I install a RUU which is rooted so at least I'll have a start cause now I can't do ANYTHING. Whatever ideas you have, please let me know.
I tried htcdev, sunshine, kingroot, kingoroot, supersu, root apps.... nothing. The tmobile unlock app, no chance... Thanks
Click to expand...
Click to collapse
I'm still an amateur myself but here is my understanding and recommendations.
RUU will update firmware and flash stock rom basically bringing you back to square one. You should be able to use it with a locked bootloader. If you can't do anything with the phone I would suggest to to use RUU dot exe of the latest firmware and update all OTAs. I used a video guide on youtube by "sakitech" when I rooted mine. Just search "root HTC One m9" it should be the first link. Make sure you're copying no more no less than your token ID. Hope this helps
You're way ahead of yourself, RUU is not rooted. It's a completely stock system. Like if you were to buy a brand new phone. It will wipe your phone completely too, nothing on sdcard.
Sent from my SM-N920T using Tapatalk
Hey guys,
Thank you very much for responding.
So what would be the best thing for me to do?