Related
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
I honestly can't believe I am asking such a rudimentary question with how long I've been here, but it's always been "htcdev root then s-off exploit" before.
Now though, I have the option of just simply installing Weaksauce to get a temproot... then running that Firewater adb script with that temproot to get S-OFF, essentially getting S-OFF without needing a (permanent) root first.
To be honest, the only reason I even want root right now is to install that app/patcher that removes the SD card restrictions KitKat added. Again, before since I had to use htcdev first I would root, then install a rooted rom, then get S-OFF, so I already had a permrooted rom before I gained S-OFF. If I already have S-OFF(that means I have full access to the entire flashrom right?), would I still not have root access because the rom itself doesn't give me that access? And if so, can I just modify a permissions file or something similar, or would I need to flash a rooted version of the stock rom? I know those exist, but since I just got this phone I don't want to heavily modify it's software just yet. I know it will still have bloatware, and as much as I hate it, almost all of it is uninstallable on the stock Sprint M8 rom (wish I coudl get rid of Sprint Zone and Sprint ID though).
Well, that, and the other reason is because this phone basically came out less than a month ago, and already had a firmware update from Sprint, it is sure to get more updates down the road. Would rooting and getting S-OFF prevent me from installing official updates? (I don't want to have to wait for a modified version to become available, and if I was going to go down that route, I might as well just use a custom rom). Or could an official update lock me back to S-ON and require me to run the exploit again (providing they didn't also patch said exploit in the update)?
Oh, and oen final thing, because I constantly hear that changing the battery (admittedly, not an issue with the M8) or doing this or that breaks Google Wallet for security purposes, would doing any of this stop Google Wallet and it's NFC features from working?
Weaksauce doesn't work on the Sprint M8.
And of course you can still take OTA updates while S-OFF (as long as your system is completely stock and you have the stock recovery).
Captain_Throwback said:
Weaksauce doesn't work on the Sprint M8.
Click to expand...
Click to collapse
Oh, I was under the impression that it could
So then my only option is the htcdev unlock? I really want to avoid basically telling HTC "Don't let this IMEI have any warranty service" if I can. I still won't have any issues getting S-OFF if I use the htcdev method though, right?
Cyber Akuma said:
Oh, I was under the impression that it could
So then my only option is the htcdev unlock? I really want to avoid basically telling HTC "Don't let this IMEI have any warranty service" if I can. I still won't have any issues getting S-OFF if I use the htcdev method though, right?
Click to expand...
Click to collapse
No, HTC Dev won't interfere with you gaining S-off.
So, does anybody know about the Google Wallet thing?
Cyber Akuma said:
So, does anybody know about the Google Wallet thing?
Click to expand...
Click to collapse
What "thing" are you referring to?
Sent from my HTC device
FinZ28 said:
What "thing" are you referring to?
Sent from my HTC device
Click to expand...
Click to collapse
Last line in my original post:
Oh, and oen final thing, because I constantly hear that changing the battery (admittedly, not an issue with the M8) or doing this or that breaks Google Wallet for security purposes, would doing any of this stop Google Wallet and it's NFC features from working?
Click to expand...
Click to collapse
Google Wallet and all its features should work just fine.
Sent from my HTC device
FinZ28 said:
Google Wallet and all its features should work just fine.
Sent from my HTC device
Click to expand...
Click to collapse
Fin is correct, that was an issue with the EVO LTE when it first came out, people were not first disabling Wallet before they flashed, and this caused an issue with app reinstallation. I believe that was resolved many updates ago for wallet.
03orlandor6 said:
Fin is correct, that was an issue with the EVO LTE when it first came out, people were not first disabling Wallet before they flashed, and this caused an issue with app reinstallation. I believe that was resolved many updates ago for wallet.
Click to expand...
Click to collapse
Thank you for the detailed response, It's a great help when people also explain why something does or doesn't work in some way.
So basically, to summarize, for a Sprint M8 I can only use the official dev unlock, and even the temporarily root methods don't work, but after I use the dev unlock I can run firewater to get S-Off?
I am going to have to install a rom with root access after I use the dev unlock though and not be able to rely on the Stock rom through aren't I? I can still get a rom that is 100% the stock rom, just with root access though, right?
Would I have to worry about anything or an OTA resetting me to S-ON? Especially if it can fix the exploit that currently allows for S-Off?
Cyber Akuma said:
Thank you for the detailed response, It's a great help when people also explain why something does or doesn't work in some way.
So basically, to summarize, for a Sprint M8 I can only use the official dev unlock, and even the temporarily root methods don't work, but after I use the dev unlock I can run firewater to get S-Off?
I am going to have to install a rom with root access after I use the dev unlock though and not be able to rely on the Stock rom through aren't I? I can still get a rom that is 100% the stock rom, just with root access though, right?
Would I have to worry about anything or an OTA resetting me to S-ON? Especially if it can fix the exploit that currently allows for S-Off?
Click to expand...
Click to collapse
Yes, use HTC Dev to unlock, install a custom recovery, then flash SuperSU for root access. You can then use Firewater to gain S-off. You can stay on the stock ROM, just be warned that you'll get update notifications if you aren't on the latest OTA update. Having said that, you won't be able to install said update unless you reinstall the stock recovery.
Sent from my HTC device
FinZ28 said:
Having said that, you won't be able to install said update unless you reinstall the stock recovery.
Click to expand...
Click to collapse
It's only the recovery that matters? Not the S-Off or having Dev unlock or anything else? And only for installing a stock update, not running it after it's been installed?
Isn't that easy to flash and re-flash? Can't I just easily re-flash back to a stock recovery, install the OTA, then flash back?
Oh, and can I lose S-Off in a future update or something this way? Or is it permanent once applied? (Although I know you can hex-exit the bootloader to make it look like it's still S-On, not sure if I want to do that since it sounds extremely risky).
Cyber Akuma said:
It's only the recovery that matters? Not the S-Off or having Dev unlock or anything else? And only for installing a stock update, not running it after it's been installed?
Isn't that easy to flash and re-flash? Can't I just easily re-flash back to a stock recovery, install the OTA, then flash back?
Oh, and can I lose S-Off in a future update or something this way? Or is it permanent once applied? (Although I know you can hex-exit the bootloader to make it look like it's still S-On, not sure if I want to do that since it sounds extremely risky).
Click to expand...
Click to collapse
It's that easy, yes, and no, you can't lose S-off by applying an OTA update. Take a look at the thread in the link below for more info:
http://forum.xda-developers.com/showthread.php?t=2720558
Sent from my HTC device
Hello!
I just bought this phone. I have the HTC One HKE. I bought yesterday, and today I rooted it. I had no reason to wait.
So I was wondering, currently I'm on the Viper ROM 2.4.0, and I thought it would increase the performance but it has rather slightly hampered it. I want one that will increase the performance of the phone, so which ROM would you recommend? Also, please do make a kernel recommendation that goes along with it, too.
I prefer staying with Sense 6.0.
Not sure how you "slightly hampered" the performance of your phone by flashing Viper, other than the fact the version of Viper you flashed is outdated. I'm running Viper 3.2.1 with MassStash's Hypernova kernel and my phone runs great. To each his own, though. "Best ROM/kernel" threads are subjective at best because what works well for one person may not work well for another.
Magnum_Enforcer said:
Not sure how you "slightly hampered" the performance of your phone by flashing Viper, other than the fact the version of Viper you flashed is outdated. I'm running Viper 3.2.1 with MassStash's Hypernova kernel and my phone runs great. To each his own, though. "Best ROM/kernel" threads are subjective at best because what works well for one person may not work well for another.
Click to expand...
Click to collapse
I'm very well aware that this my rom is outdated, but I cannot seem to be able to return to stock to update the firmware in order to install the latest versions. When I do, my WiFi does not work and that's a real problem.
Can anyone direct me to the correct thread that explains how I can do this? Note that I have tried updating the firmware in many different ways - through the command prompt, and using the generic RUU update with replacing the rom.zip file. I do not know what I need to do first, I just relocked the device and had a little panic attack because I couldn't do anything else. I had to unlock it again using the HTC dev code.
Can somebody please tell me what I need to do to get the latest firmware? I'm on the HK device with firmware version 2.16.654.4
Take a look at the thread linked below:
http://forum.xda-developers.com/showthread.php?t=2729173
I tried to do this, as I previously stated. I tried to do it over fastboot. I tried using Generic RUU. Each time I get an error. At first it was error 99, but then I relocked the bootloader and got error 12 (signature verification failed).
Would you mind posting a link to the RUU you attempted to use? We were actually having a discussion in another thread about some similar issues folks were having.
I tried them all.
I tried the HK version, the non-HK version. I tried the ones with boot.img and the ones without. I even tried to download the entire image (1.6GB) and flash it with the program and that did not work either. I tried them all, believe me. I would not let something like that (wrong version) get in the way.
I have:
cidnum: SPCS_004
version-main: 2.16.654.4
I even tried running the SuperCID command, and that didn't do anything.
You won't be able to get SuperCID while S-on. My suggestion at this point would be to unlock your bootloader again, flash a stock rooted ROM and then get S-off with the Sunshine exploit. You can then update your firmware without having to mess with any of the RUU or FUU stuff.
Where could I find a stack rooted ROM that matches my version?
I looked them all up in the other thread and most of their versions are 1.xxx while my mainver is 2.16.xx
Amer28 said:
Where could I find a stack rooted ROM that matches my version?
I looked them all up in the other thread and most of their versions are 1.xxx while my mainver is 2.16.xx
Click to expand...
Click to collapse
Post #3 under "Old Downloads":
http://themikmik.com/showthread.php?16276-SPRINT-ROM-BeyondStockᵀᴹ-v1-2-0-amp-Stock-Rooted
Okay. Right now, I am on stock rooted. I am not quite sure how to proceed with the update. I have been going to the menu, and checking for an update but it says that no update is availible at this time.
Do I try running the RUU, or just wait for it to arrive?
I should also tell you that I am still on TWRP and unlocked. Should relock and install stock recovery as well?
Amer28 said:
Okay. Right now, I am on stock rooted. I am not quite sure how to proceed with the update. I have been going to the menu, and checking for an update but it says that no update is availible at this time.
Do I try running the RUU, or just wait for it to arrive?
I should also tell you that I am still on TWRP and unlocked. Should relock and install stock recovery as well?
Click to expand...
Click to collapse
You can go one of two routes. Either S-off and manually update your firmware, or install the stock Android system recovery, which will allow you to take the update.
So, I did it.
I'm currently on the latest firmware, running the latest Venom too with the WiFi working. I have root access.
You told me earlier that I should do sunshine s-off. I was wondering, why is that? I already have everything I wanted. What is the benefit of S-OFF, when I already have root?
I don't want to sound ignorant, but I really don't know. I feel like a big noob right now.
Amer28 said:
So, I did it.
I'm currently on the latest firmware, running the latest Venom too with the WiFi working. I have root access.
You told me earlier that I should do sunshine s-off. I was wondering, why is that? I already have everything I wanted. What is the benefit of S-OFF, when I already have root?
I don't want to sound ignorant, but I really don't know. I feel like a big noob right now.
Click to expand...
Click to collapse
Read this:
http://forum.xda-developers.com/showthread.php?t=1680928
Just got a new m9 been away from htc and rooting for a long time. just upgraded from my trusty galaxy s3. Is there any thing i should be aware of before unlocking boot loader and rooting. the phone is bone stock on 5.0.2 Should i let it update before unlocking boot loader and rooting. To my understanding i should unlock boot loader install twrp and don't mount the system before making a back up. Then install supersu and root or use sunshine to get root and do both.
tw39515 said:
Just got a new m9 been away from htc and rooting for a long time. just upgraded from my trusty galaxy s3. Is there any thing i should be aware of before unlocking boot loader and rooting. the phone is bone stock on 5.0.2 Should i let it update before unlocking boot loader and rooting. To my understanding i should unlock boot loader install twrp and don't mount the system before making a back up. Then install supersu and root or use sunshine to get root and do both.
Click to expand...
Click to collapse
Welcome back to HTC
It really depends on what you plan to do with your M9.
If you plan on using custom roms then yes unlock and install TWRP. Root is not required to flash roms.
Sunshine does not root or unlock but removes secure write (S-Off) which allows you to install different firmware's etc.
With S-on you can only move forward with firmware's. Lots of people complain about the 25.00, But its well worth it.
If you are not concerned about the cost, then unlock, twrp, flash superSu, and install sunshine and S-off then your free to do anything.
backup if you like but there is a thread with stock backups etc...
hope this helps
My main concern was if i want to use the phone first with out unlocking and it receives the tmobile update that i can unlock and root later.
tw39515 said:
My main concern was if i want to use the phone first with out unlocking and it receives the tmobile update that i can unlock and root later.
Click to expand...
Click to collapse
Yes you can still unlock and root and S-off on the current OS 5.1 - 2.11.531.19, but I would do it before MM comes out for this device.
will do viperone had issues on initial firmware so i flashed the latest ruu, sunshine is next. thanks for the advice.
Hi everyone,
I need some help if you may please. I bought an HTC One M9 phone and for a while it's been telling me to update to the newest android version. However, this was impossible because even when I downloaded de update from TMobile, when restarting, TWRP would kick in and wouldn't let me go through the whole setup. So, I got to some tutorials and I found some guidance but it's all so confusing and I've gotten to a point where I have no idea what to do next.
Phone is from:
-TMobile
What I did:
-Got rid of TWRP
-Got it back to unroot
Phone status as of now:
It works fine, but it's still not updated.
When going into the HTC Download mode screen, i get the following info:
-UNLOCKED
-htc_himaul PVT S-ON
-OS-1.32.531.24
-Warning: Security checking failed NOT_FIND_SMARTIO
FILE /mnt/media_rw/ext_sd/0PJAIMG.zip
File NOT FOUND
ADB is not reading my device when in download mode, I was trying to install stock recovery by following a tutorian in android soul: how to install stock recovery on htc one m9 (sorry but the forum won't let me post the link.
What do I need to do? There are so many tutorials out ther with so many different instructions that I'm totally confused now as to what to install or not to install . I'd like to install the Developer version but if I have to deal with the Tmobile one, that's ok.
Thanks in advance
Umang jain
[email protected]
umangilu said:
Hi everyone,
I need some help if you may please. I bought an HTC One M9 phone and for a while it's been telling me to update to the newest android version. However, this was impossible because even when I downloaded de update from TMobile, when restarting, TWRP would kick in and wouldn't let me go through the whole setup. So, I got to some tutorials and I found some guidance but it's all so confusing and I've gotten to a point where I have no idea what to do next.
Phone is from:
-TMobile
What I did:
-Got rid of TWRP
-Got it back to unroot
Phone status as of now:
It works fine, but it's still not updated.
When going into the HTC Download mode screen, i get the following info:
-UNLOCKED
-htc_himaul PVT S-ON
-OS-1.32.531.24
-Warning: Security checking failed NOT_FIND_SMARTIO
FILE /mnt/media_rw/ext_sd/0PJAIMG.zip
File NOT FOUND
ADB is not reading my device when in download mode, I was trying to install stock recovery by following a tutorian in android soul: how to install stock recovery on htc one m9 (sorry but the forum won't let me post the link.
What do I need to do? There are so many tutorials out ther with so many different instructions that I'm totally confused now as to what to install or not to install . I'd like to install the Developer version but if I have to deal with the Tmobile one, that's ok.
Thanks in advance
Umang jain
[email protected]
Click to expand...
Click to collapse
You say you got rid of twrp and tried to flash the stock recovery but adb is not working, so what recovery is currently on the phone?
I think the simplest solution would be to run the latest RUU from your sd card since you have adb issues (most likely a driver).
This will bring you to current stock 2.11.531.19. This will wipe the device and you must use a 4-32GB sd card.
Place it on the root of the sd card and boot into download mode, vol up to update and let it run.
you can get the RUU here
tw39515 said:
My main concern was if i want to use the phone first with out unlocking and it receives the tmobile update that i can unlock and root later.
Click to expand...
Click to collapse
kc6wke said:
Yes you can still unlock and root and S-off on the current OS 5.1 - 2.11.531.19, but I would do it before MM comes out for this device.
Click to expand...
Click to collapse
Wait. I just picked up an M9 myself, and my current plan is to wait until the official T-Mobile Marshmallow OTA is released before I unlock bootloader and S-OFF. My logic being that I could create then create a backup point in TWRP if I can't find a custom ROM that suitably handles T-Mobile specific features (WiFi calling, etc.) and just restore to the stock T-Mobile image.
Are you saying that updating OTA to Marshmallow could limit my ability to use Sunshine for S-OFF?
I suppose I could just S-OFF now and then RUU back to Stock T-Mobile Marshmallow once released?
edit: I'm already on Lollipop 5.1 on my M9. Am I already ****-out-of-luck for Sunshine?
Miguel_Lancaster said:
Wait. I just picked up an M9 myself, and my current plan is to wait until the official T-Mobile Marshmallow OTA is released before I unlock bootloader and S-OFF. My logic being that I could create then create a backup point in TWRP if I can't find a custom ROM that suitably handles T-Mobile specific features (WiFi calling, etc.) and just restore to the stock T-Mobile image.
Are you saying that updating OTA to Marshmallow could limit my ability to use Sunshine for S-OFF?
I suppose I could just S-OFF now and then RUU back to Stock T-Mobile Marshmallow once released?
edit: I'm already on Lollipop 5.1 on my M9. Am I already ****-out-of-luck for Sunshine?
Click to expand...
Click to collapse
Sunshine will work on the current version. We never know what will come when a new OTA's come out.
An OTA wont relock the bootloader or return it to S-ON. That is why I would recommend to do the S-off before an OTA.
kc6wke said:
Sunshine will work on the current version. We never know what will come when a new OTA's come out.
An OTA wont relock the bootloader or return it to S-ON. That is why I would recommend to do the S-off before an OTA.
Click to expand...
Click to collapse
Makes sense.
But won't unlocking the bootloader, flashing TWRP, then going S-OFF with Sunshine make it so that the newest OTA won't be accepted as an actual over-the-air update due to the altered filesystem? I know that I can still RUU, but will RUU not revert my S-OFF back to S-ON and re-lock the bootloader? Or are those things unaffected by RUU, even as an executable RUU?
Miguel_Lancaster said:
Makes sense.
But won't unlocking the bootloader, flashing TWRP, then going S-OFF with Sunshine make it so that the newest OTA won't be accepted as an actual over-the-air update due to the altered filesystem? I know that I can still RUU, but will RUU not revert my S-OFF back to S-ON and re-lock the bootloader? Or are those things unaffected by RUU, even as an executable RUU?
Click to expand...
Click to collapse
The RUU will not relock bootloader or rewrite S-On. To accept OTA, you need to have stock unmodified device.
You could run the RUU again or just unroot and flash stock recovery. The OTA will not wipe the device but the RUU will.
Hope this helps.
kc6wke said:
You say you got rid of twrp and tried to flash the stock recovery but adb is not working, so what recovery is currently on the phone?
I think the simplest solution would be to run the latest RUU from your sd card since you have adb issues (most likely a driver).
This will bring you to current stock 2.11.531.19. This will wipe the device and you must use a 4-32GB sd card.
Place it on the root of the sd card and boot into download mode, vol up to update and let it run.
you can get the RUU here
Click to expand...
Click to collapse
Thanks for this! Im having trouble with my computer and have been looking for a ruu zip all day lol. Will give this a shot on my TMOUS S-Off M9 tomorrow so I can jump to my next device.
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?