S-Off on 1.54.651.8? - One (M8) Q&A, Help & Troubleshooting

Hi all,
I’ve searched around on a few forums for this but haven’t found a direct answer. I received my M8 on Wednesday and promptly unlocked the bootloader.*Then, like an idiot, I took the 1.54 OTA and proceeded to install TWRP/root, completely forgetting to do S-Off.
I tried the Firewater method last night several times with no success. I got the standard “whelp, this sucks…” failure message. In case it matters, I’m on the Sprint M8, but I decided to post here since the Firewater method appeared to have success with almost all variants.
ROM: rooted stock
Android 4.4.2
Sense 6.0
Kernel version 3.4.0-g255057cd
Software version: 1.54.651.8
Thanks!
Sent from my 831C using Tapatalk

subhumanderelict said:
Hi all,
I’ve searched around on a few forums for this but haven’t found a direct answer. I received my M8 on Wednesday and promptly unlocked the bootloader.*Then, like an idiot, I took the 1.54 OTA and proceeded to install TWRP/root, completely forgetting to do S-Off.
I tried the Firewater method last night several times with no success. I got the standard “whelp, this sucks…” failure message. In case it matters, I’m on the Sprint M8, but I decided to post here since the Firewater method appeared to have success with almost all variants.
ROM: rooted stock
Android 4.4.2
Sense 6.0
Kernel version 3.4.0-g255057cd
Software version: 1.54.651.8
Thanks!
Sent from my 831C using Tapatalk
Click to expand...
Click to collapse
As far as I'm aware version doesn't matter.
At least from what I read of the thread from when I was trying to S-Off my own. I must have tried a good 20/30 times to get mine to work. In the end I did the trick, whereby you drop a file, like a ROM or Video file (Something large) while Firewater does it business. This made mine work almost instantly, even after so many fails.
Warning: Apparently the above method could cause damage to your device.

I had issues but i think it was hw related. i have a new device. made in taiwan. got soff first try without moving files. now i just need to find thread on how to remove tampered

E_n_T said:
I had issues but i think it was hw related. i have a new device. made in taiwan. got soff first try without moving files. now i just need to find thread on how to remove tampered
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2708565

Tiann said:
As far as I'm aware version doesn't matter.
At least from what I read of the thread from when I was trying to S-Off my own. I must have tried a good 20/30 times to get mine to work. In the end I did the trick, whereby you drop a file, like a ROM or Video file (Something large) while Firewater does it business. This made mine work almost instantly, even after so many fails.
Warning: Apparently the above method could cause damage to your device.
Click to expand...
Click to collapse
Do you happen to know if it's something that could be recovered from with a Nandroid backup since we don't have an RUU yet?
E_n_T said:
I had issues but i think it was hw related. i have a new device. made in taiwan. got soff first try without moving files. now i just need to find thread on how to remove tampered
Click to expand...
Click to collapse
This was on 1.54?
Sent from my 831C using Tapatalk

subhumanderelict said:
Do you happen to know if it's something that could be recovered from with a Nandroid backup since we don't have an RUU yet?
This was on 1.54?
Sent from my 831C using Tapatalk
Click to expand...
Click to collapse
yes. 1.54

E_n_T said:
yes. 1.54
Click to expand...
Click to collapse
And you used Firewater? Anything else special, like a custom ROM or something?
Sent from my 831C using Tapatalk

subhumanderelict said:
And you used Firewater? Anything else special, like a custom ROM or something?
Sent from my 831C using Tapatalk
Click to expand...
Click to collapse
actually. i unlocked device with htcdev. installed phils recovery. installed SU and used stock with SuperSU installed and followed instructions at firewater site. i had very small hopes but it worked. so my wild guess is that chinamade phones like my previous was will not work due to the hardware. cause i tried with several. all made in china. this made in taiwan worked first time. flawless.

subhumanderelict said:
Hi all,
I’ve searched around on a few forums for this but haven’t found a direct answer. I received my M8 on Wednesday and promptly unlocked the bootloader.*Then, like an idiot, I took the 1.54 OTA and proceeded to install TWRP/root, completely forgetting to do S-Off.
I tried the Firewater method last night several times with no success. I got the standard “whelp, this sucks…” failure message. In case it matters, I’m on the Sprint M8, but I decided to post here since the Firewater method appeared to have success with almost all variants.
ROM: rooted stock
Android 4.4.2
Sense 6.0
Kernel version 3.4.0-g255057cd
Software version: 1.54.651.8
Thanks!
Sent from my 831C using Tapatalk
Click to expand...
Click to collapse
If you get that message, there's nothing you can do.
S-off isn't currently compatible with all M8s, as it seems yours Isn't at present.
All you can do is wait for the exploit to be updated.
Sent from my HTC One_M8 using XDA Premium 4 mobile app

shorty1483 said:
http://forum.xda-developers.com/showthread.php?t=2708565
Click to expand...
Click to collapse
i actually missed your post. got it sorted thru google but great thanks

subhumanderelict said:
Hi all,
I’ve searched around on a few forums for this but haven’t found a direct answer. I received my M8 on Wednesday and promptly unlocked the bootloader.*Then, like an idiot, I took the 1.54 OTA and proceeded to install TWRP/root, completely forgetting to do S-Off.
I tried the Firewater method last night several times with no success. I got the standard “whelp, this sucks…” failure message. In case it matters, I’m on the Sprint M8, but I decided to post here since the Firewater method appeared to have success with almost all variants.
ROM: rooted stock
Android 4.4.2
Sense 6.0
Kernel version 3.4.0-g255057cd
Software version: 1.54.651.8
Thanks!
Sent from my 831C using Tapatalk
Click to expand...
Click to collapse
I saw several folks that were having this issue as well on Sprint thread. I got my Sprint device last night and while I didn't take the update I did chronicle the steps I took and had no issues getting s-off.
Ultimately you might try different methods of root. I just loaded ViperOne right out of the box, while it is my preferred ROM I also read in the Sprint forums that one of the MODs wasn't able to get it to work with some of the other rooted ROMs so I just started there.
While you've done the update all may not be lost. I'd try a couple different rooted ROMs, do full wipes, and see if you can make it work.
MG

Related

Just got my HOX - what now?

Hey guys,
Before I get teared apart limb from limb, I tried searching for rooting on the new software and didn't really come up with any guides.
So, anyway. I just got my upgrade HOX in the mail, and I'm so excited! Of course, I've been on XDA before and rooted and customized and flashed to my heart's content, but I need some help.
Would someone lead me to a guide for rooting HOX on the NEW software? I just got my new kit today, I don't know if it automatically updates or not. I pretty much want to learn how to get to flashing a ROM.
Thanks!
C
i used this no problems.
http://forum.xda-developers.com/showthread.php?t=1577671
cappyandroid said:
Hey guys,
Before I get teared apart limb from limb, I tried searching for rooting on the new software and didn't really come up with any guides.
So, anyway. I just got my upgrade HOX in the mail, and I'm so excited! Of course, I've been on XDA before and rooted and customized and flashed to my heart's content, but I need some help.
Would someone lead me to a guide for rooting HOX on the NEW software? I just got my new kit today, I don't know if it automatically updates or not. I pretty much want to learn how to get to flashing a ROM.
Thanks!
C
Click to expand...
Click to collapse
Use it as stock for a few weeks at least to rule out any manufacturer hardware issues.
Update via the OTA check for updates in settings. (2.17 is the latest)
------
The when you want to play with custom, root of etc....
Install Android SDK
1st step is unlocking the bootloader via HTCdev
Then flashing clockworkmod touch recovery
Then flashing a rom of choice, all which have root I think.
Sent from my HTC One X using XDA Premium HD app
chrisjcks said:
Use it as stock for a few weeks at least to rule out any manufacturer hardware issues.
Click to expand...
Click to collapse
I would actually emphasize this. So many people have had hardware issues and it will be a struggle to get the phone repaired after rooting via HTCDEV. Spare yourself trouble and give some time to rule out those problems.
Besides you can use that time to get to know the available roms, issues with them and the rooting/flashing process
chrisjcks said:
Use it as stock for a few weeks at least to rule out any manufacturer hardware issues.
Click to expand...
Click to collapse
I also came here to post exactly this
akselic said:
I would actually emphasize this. So many people have had hardware issues and it will be a struggle to get the phone repaired after rooting via HTCDEV. Spare yourself trouble and give some time to rule out those problems.
Besides you can use that time to get to know the available roms, issues with them and the rooting/flashing process
Click to expand...
Click to collapse
Sorry I'm just trying to learn here but here I go. Are their any complications of using HTC to unlock the bootloader meaning can't the boot loader be relocked if he is trying to send it in for repairs?
Sent from my Nexus S using Tapatalk 2
TG2708 said:
Sorry I'm just trying to learn here but here I go. Are their any complications of using HTC to unlock the bootloader meaning can't the boot loader be relocked if he is trying to send it in for repairs?
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
It can be relocked but unlocking the first time sends HTC a notion that your device has been unlocked. And there are several people that are having a tough time getting their phones repaired even though the issues are hardware.
Depending on the country and law it is possible to force them to repair or replace a faulty device but trust me, that process will be a lot faster and simpler if you haven't tampered with the bootloader.
An irrelevant response but that's why I will always go the nexus route when buying android so I could avoid most if not all these issues.
Sent from my Nexus S using Tapatalk 2
Help with HTC One X ATT version
Hi Guys,
So I have unlocked my HTC One X ATT version using the HTCDev.com site. Now I want to install clockworkmod so I can proceed with custom ROM installations. But all the links that I find to CWM are dead.
Can someone point me to the live links please? I am itching to get the CM10 rom installed on my HOX.
Please note there are plenty of sites and links for international version of HOX but I want for ATT.
Thanks,
jhawk_007
jhawk_007 said:
Hi Guys,
So I have unlocked my HTC One X ATT version using the HTCDev.com site. Now I want to install clockworkmod so I can proceed with custom ROM installations. But all the links that I find to CWM are dead.
Can someone point me to the live links please? I am itching to get the CM10 rom installed on my HOX.
Please note there are plenty of sites and links for international version of HOX but I want for ATT.
Thanks,
jhawk_007
Click to expand...
Click to collapse
Can CWM version on HOX Tegra 3 international work on an AT&T model?
I'd supply you my CWM touch, but i don't want to if it won't work.
As I'm unsure, I'll leave this up to you to decide.
Sent from my Nexus 7 using XDA Premium HD app
chrisjcks said:
Can CWM version on HOX Tegra 3 international work on an AT&T model?
I'd supply you my CWM touch, but i don't want to if it won't work.
As I'm unsure, I'll leave this up to you to decide.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I tried CWM version but it does not work. The phone goes into loop when I try to boot it into recovery mode.
Thanks for the response though...
jhawk_007
jhawk_007 said:
I tried CWM version but it does not work. The phone goes into loop when I try to boot it into recovery mode.
Thanks for the response though...
jhawk_007
Click to expand...
Click to collapse
You'd be better off asking in the AT&T One X section of this forum. I didn't think you could even use htcdev with it.
jhawk_007 said:
I tried CWM version but it does not work. The phone goes into loop when I try to boot it into recovery mode.
Thanks for the response though...
jhawk_007
Click to expand...
Click to collapse
This is what you're looking for:
http://techerrata.com/file/twrp2/evita/openrecovery-twrp-2.2.2.0-evita.img
Found it through this thread:
http://forum.xda-developers.com/showthread.php?t=1677447
And these are the forums where you should go for an AT&T HTC One X:
http://forum.xda-developers.com/forumdisplay.php?f=1538
If you have a ATT HTC One X, get off this forum, go to the proper section, and never come back here. Flashing any rom here will permanently brick your device.
Sent from my Inspire 4G using Tapatalk 2

HTC One 4.4.2 OTA rumrunner?

I didn't feel like browsing through a ton of pages on the rumrunner forum. And I'm posting this in the Q&A section as this is a question.
Has rumrunner been updated to work with the Verizon HTC One with OTA 4.4.2? I am aware that I probably should have rooted before I accepted the OTA 4.4.2 update, but if I knew that it'd be awhile before I was able to root, I would've rooted and installed a 4.4.2 stock ROM.
Thanks.
nikalsaki said:
I didn't feel like browsing through a ton of pages on the rumrunner forum. And I'm posting this in the Q&A section as this is a question.
Has rumrunner been updated to work with the Verizon HTC One with OTA 4.4.2? I am aware that I probably should have rooted before I accepted the OTA 4.4.2 update, but if I knew that it'd be awhile before I was able to root, I would've rooted and installed a 4.4.2 stock ROM.
Thanks.
Click to expand...
Click to collapse
No it has not and it mostly likely will not untill August.
In the same vein...
In the same vein, does anyone know if Firewater is supposed to work with the same version (4.4.2, Hboot 1.56)? I haven't had any luck, but I'm not sure if that's because of my set up or just because it's not supported.
kashev said:
In the same vein, does anyone know if Firewater is supposed to work with the same version (4.4.2, Hboot 1.56)? I haven't had any luck, but I'm not sure if that's because of my set up or just because it's not supported.
Click to expand...
Click to collapse
it wont work, the temp root that firewater uses was patched int he 4.4.2 release.
for firewater to work we need an unlocked bootloader from HTC (which VZW asked nicely to remove)
Going to have to wait for another exploit to surface.
synisterwolf said:
it wont work, the temp root that firewater uses was patched int he 4.4.2 release.
for firewater to work we need an unlocked bootloader from HTC (which VZW asked nicely to remove)
Going to have to wait for another exploit to surface.
Click to expand...
Click to collapse
Yeah I've tried every thing and nothing works, I got my HTC One exchanged a couple of weeks ago because the one I had just shut off and fried itself, I got the new one with 4.3 not realizing that it was actually rootable and I ended up taking the 4.4.2 update since I figured it wouldnt matter, sucks I was wrong and now have to wait quite a while as well. shame that something is there but they are waiting almost 5 months to do anything with it, but what can you do?
What ticks me off the most is Verizon, every other carrier has no issues with rooting the HTC One, why does Verizon care? I'll just never get it, its our fault and we void the warranty and we know this, other carriers know this and dont care, why Verizon WHY?
Vidfreek said:
Yeah I've tried every thing and nothing works, I got my HTC One exchanged a couple of weeks ago because the one I had just shut off and fried itself, I got the new one with 4.3 not realizing that it was actually rootable and I ended up taking the 4.4.2 update since I figured it wouldnt matter, sucks I was wrong and now have to wait quite a while as well. shame that something is there but they are waiting almost 5 months to do anything with it, but what can you do?
What ticks me off the most is Verizon, every other carrier has no issues with rooting the HTC One, why does Verizon care? I'll just never get it, its our fault and we void the warranty and we know this, other carriers know this and dont care, why Verizon WHY?
Click to expand...
Click to collapse
you could do what I'm leaning forward to doing, just call verizon and say that you have a purple camera tint problem and its really annoying, they should send u a refurbished one free or charge. of course, you have to send your current one in but it's not like they check or anything so it's pretty much full proof. got many refurbished phones that way, but it was not to get 4.3 or any other "rootable" software.the phones actually had problems.
nty123 said:
you could do what I'm leaning forward to doing, just call verizon and say that you have a purple camera tint problem and its really annoying, they should send u a refurbished one free or charge. of course, you have to send your current one in but it's not like they check or anything so it's pretty much full proof. got many refurbished phones that way, but it was not to get 4.3 or any other "rootable" software.the phones actually had problems.
Click to expand...
Click to collapse
this plan has worked for some members here. remember to tell them that you would not like them to update the software because that was the root cause to the purple tint ( not the truth but they will honor your request)
synisterwolf said:
this plan has worked for some members here. remember to tell them that you would not like them to update the software because that was the root cause to the purple tint ( not the truth but they will honor your request)
Click to expand...
Click to collapse
Ha ok sure will, thanks.
Kitkat can now be unlocked for the vzw using the weaksauce exploit to get temp root. After getting temp root firewater will work.
Sent from my HTC6525LVW using Tapatalk
disconnecktie said:
Kitkat can now be unlocked for the vzw using the weaksauce exploit to get temp root. After getting temp root firewater will work.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Can confirm. Did it a few hours ago.
GrayTheWolf said:
Can confirm. Did it a few hours ago.
Click to expand...
Click to collapse
I've been trying for days to get it to work. Temproot works(verified with Root Checker), push and chmod works, but then when trying to run temproot I get this error:
[*] Attempting to acquire root. This will take 5-10 minutes, be patient
error in setsockopt().
Failed to get prepare_kernel_cred address.
Failed to get commit_creds address.
Failed to get ptmx_fops address.
Failed to setup variables.
1|[email protected]:/ $
Click to expand...
Click to collapse
The fact that it worked for you gives me hope, but any idea why I'm having trouble?
Youngtusk said:
I've been trying for days to get it to work. Temproot works(verified with Root Checker), push and chmod works, but then when trying to run temproot I get this error:
The fact that it worked for you gives me hope, but any idea why I'm having trouble?
Click to expand...
Click to collapse
are you running the temp-root method? weak sauce is the "temp-root" therefore you should be using the normal method of firewater s-off
Youngtusk said:
I've been trying for days to get it to work. Temproot works(verified with Root Checker), push and chmod works, but then when trying to run temproot I get this error:
The fact that it worked for you gives me hope, but any idea why I'm having trouble?
Click to expand...
Click to collapse
Install weaksauce apk, get it here - http://forum.xda-developers.com/showthread.php?t=2699091
Then use firewater to get s-off. Profit.
ccarr313 said:
Install weaksauce apk, get it here - http://forum.xda-developers.com/showthread.php?t=2699091
Then use firewater to get s-off. Profit.
Click to expand...
Click to collapse
I've tried both methods, with weak sauce and without it using the temproot method. So far, no Bueno.
Think it would make a difference if I reset my device to factory? Maybe I've messed with it too much for these simple processes to work?
Sent from my HTC6500LVW using xda app-developers app
Youngtusk said:
I've tried both methods, with weak sauce and without it using the temproot method. So far, no Bueno.
Think it would make a difference if I reset my device to factory? Maybe I've messed with it too much for these simple processes to work?
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Might not be a bad idea. You can always backup the sd card before you do that.

[Q] Should I accept the OTA update?

I'm sitting here with my Verizon HTC One on the "Software update ready to install" screen. I'm not sure if I should select "Install Later" or "Install Now". I guess my main question is, has there been any indication that someone will come up with a workable root solution for the M7 with the OTA KitKat update? I know there isn't one for Jellybean.
Sorry if this is a n00b question. If it has been asked and answered before, please point me in the direction of the thread. Thanks!
Edit: I see a couple of folks have asked about this in the Q&A forum (where I probably should have, heh). Mods, please delete.
lennyjaxn said:
I'm sitting here with my Verizon HTC One on the "Software update ready to install" screen. I'm not sure if I should select "Install Later" or "Install Now". I guess my main question is, has there been any indication that someone will come up with a workable root solution for the M7 with the OTA KitKat update? I know there isn't one for Jellybean.
Sorry if this is a n00b question. If it has been asked and answered before, please point me in the direction of the thread. Thanks!
Edit: I see a couple of folks have asked about this in the Q&A forum (where I probably should have, heh). Mods, please delete.
Click to expand...
Click to collapse
If you are s-off dont take the OTA. you can get the firmware here and it would be like you took the OTA.
synisterwolf said:
If you are s-off dont take the OTA. you can get the firmware here and it would be like you took the OTA.
Click to expand...
Click to collapse
Thanks for your reply. Unfortunately, I bought my phone from eBay about three weeks after it became (I think) unrootable, so I am s-on.
lennyjaxn said:
Thanks for your reply. Unfortunately, I bought my phone from eBay about three weeks after it became (I think) unrootable, so I am s-on.
Click to expand...
Click to collapse
if you want root, it will cost you $25 for the license from Sunshine. I would do sunshine before taking the OTA because it might not work on the latest OTA.
if you dont care about root, just take the ota.
synisterwolf said:
if you want root, it will cost you $25 for the license from Sunshine. I would do sunshine before taking the OTA because it might not work on the latest OTA.
if you dont care about root, just take the ota.
Click to expand...
Click to collapse
Ah, gotcha. I've read conflicting reports about Sunshine's success with the Verizon HTC One, so I wasn't sure if it was still a valid method. Thanks for the tip. I'll do that before the OTA update.
synisterwolf said:
if you want root, it will cost you $25 for the license from Sunshine. I would do sunshine before taking the OTA because it might not work on the latest OTA.
if you dont care about root, just take the ota.
Click to expand...
Click to collapse
You should never have to pay for Rooting. Android is a better community than that. Setup bounties, but never force payment. My opinion.
lennyjaxn said:
Ah, gotcha. I've read conflicting reports about Sunshine's success with the Verizon HTC One, so I wasn't sure if it was still a valid method. Thanks for the tip. I'll do that before the OTA update.
Click to expand...
Click to collapse
Sunshine will tell you if the phone can be s-off before buying the license.
I actually just sunshined my M7 this am. Is there any way to block the OTA notification/checking/downloading?
patracy said:
I actually just sunshined my M7 this am. Is there any way to block the OTA notification/checking/downloading?
Click to expand...
Click to collapse
Yeah, flash the file I posted here: LINK
Any way to do it without flashing roms?
Has anyone noticed HTC Clock and HTC Lockscreen updates in Google Play after the new OTA? If so, have you installed and had any issues? I'm reading the comments and some say HTC Clock update causes alarms to no longer work and HTC Lockscreen update causes reboot loop.
hytekjosh said:
Has anyone noticed HTC Clock and HTC Lockscreen updates in Google Play after the new OTA? If so, have you installed and had any issues? I'm reading the comments and some say HTC Clock update causes alarms to no longer work and HTC Lockscreen update causes reboot loop.
Click to expand...
Click to collapse
Updated both and it works fine. Fwiw
Sent from my iPhone 5s using Tapatalk
synisterwolf said:
Updated both and it works fine. Fwiw
Sent from my iPhone 5s using Tapatalk
Click to expand...
Click to collapse
Just bit the bullet. Everything is working OK so far.
I was able to successfully S-off via SunShine, flash TWRP and root. Then, after making a complete backup, I accepted the OTA update. It didn't mess up any of those things.
lennyjaxn said:
I was able to successfully S-off via SunShine, flash TWRP and root. Then, after making a complete backup, I accepted the OTA update. It didn't mess up any of those things.
Click to expand...
Click to collapse
How? You said you are on twrp. You need stock recovery to take an ota
Sent from my HTC6500LVW using XDA Free mobile app
Oops, sorry. You're right. I remembered my steps wrong. I did S-off, then OTA, then TWRP.

[Q] Unlocked Sprint update

Hello everyone!
I would greatly appreciate if someone could show the right way to get my phone fully functional;
SPRINT HTC ONE M8
GSM SIM UNLOCKED for use on GSM networks
S-OFF
Rooted
TWRP
HBOOT 3.18.0.0000
RADIO 1.08.20.0612_4
CID-11111111
software version: 2.16.654.4
android: 4.4.3.
Issue:
1. I can not install any OTA updates, and the notification keeps popping out.
2. Mobile data is just not working properly even though I did everything as said here;
http://forum.xda-developers.com/sprint-htc-one-m8/general/enabling-3g-umts-countries-t2847461
As I did my research, it was some kind of a major bug on this series of Sprint M8 phones with breakdowns in mobile data. However, since I can not get any updates, the problem perists.
I tried installing custom ROM's, but so far ARHD 22 didn't even boot and LiquidSmooth couldn't detect the SIM card at all.
I know there are quite a few tutorials and "how-to" threads explaining all you need to know about RUU, cusotm ROM's, etc. However if someone could tell me what exactly to do and in which order (return to stock, then update?) I would greatly appreciate it.
Many many thanks!
domt91 said:
Hello everyone!
I would greatly appreciate if someone could show the right way to get my phone fully functional;
SPRINT HTC ONE M8
GSM SIM UNLOCKED for use on GSM networks
S-OFF
Rooted
TWRP
HBOOT 3.18.0.0000
RADIO 1.08.20.0612_4
CID-11111111
software version: 2.16.654.4
android: 4.4.3.
Issue:
1. I can not install any OTA updates, and the notification keeps popping out.
2. Mobile data is just not working properly even though I did everything as said here;
http://forum.xda-developers.com/sprint-htc-one-m8/general/enabling-3g-umts-countries-t2847461
As I did my research, it was some kind of a major bug on this series of Sprint M8 phones with breakdowns in mobile data. However, since I can not get any updates, the problem perists.
I tried installing custom ROM's, but so far ARHD 22 didn't even boot and LiquidSmooth couldn't detect the SIM card at all.
I know there are quite a few tutorials and "how-to" threads explaining all you need to know about RUU, cusotm ROM's, etc. However if someone could tell me what exactly to do and in which order (return to stock, then update?) I would greatly appreciate it.
Many many thanks!
Click to expand...
Click to collapse
You need a stock recovery to flash the OTA.
domt91 said:
Hello everyone!
I would greatly appreciate if someone could show the right way to get my phone fully functional;
SPRINT HTC ONE M8
GSM SIM UNLOCKED for use on GSM networks
S-OFF
Rooted
TWRP
HBOOT 3.18.0.0000
RADIO 1.08.20.0612_4
CID-11111111
software version: 2.16.654.4
android: 4.4.3.
Issue:
1. I can not install any OTA updates, and the notification keeps popping out.
2. Mobile data is just not working properly even though I did everything as said here;
http://forum.xda-developers.com/sprint-htc-one-m8/general/enabling-3g-umts-countries-t2847461
As I did my research, it was some kind of a major bug on this series of Sprint M8 phones with breakdowns in mobile data. However, since I can not get any updates, the problem perists.
I tried installing custom ROM's, but so far ARHD 22 didn't even boot and LiquidSmooth couldn't detect the SIM card at all.
I know there are quite a few tutorials and "how-to" threads explaining all you need to know about RUU, cusotm ROM's, etc. However if someone could tell me what exactly to do and in which order (return to stock, then update?) I would greatly appreciate it.
Many many thanks!
Click to expand...
Click to collapse
Easiest way to get it back to stock is just flash the Sprint H/K RUU. You can download it from HERE. Just run it and connect your phone when prompted and follow the instructions (I'd probably change your CID back to the Sprint one first to be on the safe side but as you're S-OFF it shouldn't be needed). You might also need HTC Sync Manager installed. If so, you can get it HERE
This process will wipe the phone completely so back up any data first but other than that you'll at least be back to stock and then troubleshoot any issues from there
Thanks
Many thanks to everyone.
Any chances of loosing the SIM UNLOCK when going back to stock completely?
Nope, that shouldn't be touched but as I've not had a SIM-locked device in years I can't say for certain
EddyOS said:
Nope, that shouldn't be touched but as I've not had a SIM-locked device in years I can't say for certain
Click to expand...
Click to collapse
OK, many thanks!
:good:
domt91 said:
:good:
Click to expand...
Click to collapse
Mine did the same this morning just flash twrp recovery and boot into it and you should be fine I don't know why it did this since I'm used to it popping up with a screen asking if I want to unlock boot loader but if it told you it was good then push twrp and you're good
tjeeeeee said:
Mine did the same this morning just flash twrp recovery and boot into it and you should be fine I don't know why it did this since I'm used to it popping up with a screen asking if I want to unlock boot loader but if it told you it was good then push twrp and you're good
Click to expand...
Click to collapse
Yeah, I just did that, no problems at all.
Tried to delete the previous post, but you got ahead of me
Let's see if I can get the mobile data to work without flaws.
domt91 said:
Yeah, I just did that, no problems at all.
Tried to delete the previous post, but you got ahead of me
Let's see if I can get the mobile data to work without flaws.
Click to expand...
Click to collapse
Are you trying to run any specific roms? I know with Sprint it's a bit limited
tjeeeeee said:
Are you trying to run any specific roms? I know with Sprint it's a bit limited
Click to expand...
Click to collapse
I want to try ARHD v22
domt91 said:
I want to try ARHD v22
Click to expand...
Click to collapse
Why not 34? Lol Sprint is up to date on its software you could just update to the lollipop firmware, and I could pull some of the files I've got to see if I can help you get it running, I'm on Leedroid right now so the process should be the same for ARHD.
tjeeeeee said:
Why not 34? Lol Sprint is up to date on its software you could just update to the lollipop firmware, and I could pull some of the files I've got to see if I can help you get it running, I'm on Leedroid right now so the process should be the same for ARHD.
Click to expand...
Click to collapse
Sorry if some of my questions are a bit dum, I just got from a long trip and have been out of this all rooting busines for a while...
Do i need to install a new stock firmware from Sprint with Lolipop to get the 34 runing?
I have been told v34 won't be working with this software I have right now on the phone.
domt91 said:
Sorry if some of my questions are a bit dum, I just got from a long trip and have been out of this all rooting busines for a while...
Do i need to install a new stock firmware from Sprint with Lolipop to get the 34 runing?
I have been told v34 won't be working with this software I have right now on the phone.
Click to expand...
Click to collapse
You can or you can go to the Sprint android development and flash the updated recovery since you are s-off and it'll permit you to flash lollipop roms without many issues but there is still the files that need to be modified for ARHD to work correctly like the boot.img and a few others.
tjeeeeee said:
You can or you can go to the Sprint android development and flash the updated recovery since you are s-off and it'll permit you to flash lollipop roms without many issues but there is still the files that need to be modified for ARHD to work correctly like the boot.img and a few others.
Click to expand...
Click to collapse
I just installed ARHD, everything went well and when it rebooted, the phone won't turn on... just black screen.
Any ideas??
domt91 said:
I just installed ARHD, everything went well and when it rebooted, the phone won't turn on... just black screen.
Any ideas??
Click to expand...
Click to collapse
Power+vol up for about 15 seconds then power+vol down to get into recovery. You cant flash it unless you swap out Sprint specific files otherwise you'll get what just happened or boot directly into boot loader.
Like I mentioned I can pull the files together and see if I can get it working for Sprint tonight when I get home but until then flash either fluent Rom or stock if you want lollipop or just flash bad boyz if you don't mind kitkat
tjeeeeee said:
Power+vol up for about 15 seconds then power+vol down to get into recovery. You cant flash it unless you swap out Sprint specific files otherwise you'll get what just happened or boot directly into boot loader.
Like I mentioned I can pull the files together and see if I can get it working for Sprint tonight when I get home but until then flash either fluent Rom or stock if you want lollipop or just flash bad boyz if you don't mind kitkat
Click to expand...
Click to collapse
I will go with installation of
Sprint_HTC_One_M8_non-HK_4.20.651.2_RUU
Sounds good?
domt91 said:
I will go with installation of
Sprint_HTC_One_M8_non-HK_4.20.651.2_RUU
Sounds good?
Click to expand...
Click to collapse
Yes and ill put the Sprint ARHD together tonight and test
tjeeeeee said:
Yes and ill put the Sprint ARHD together tonight and test
Click to expand...
Click to collapse
Many thanks!
For me, the biggest issue is the mobile data breakdowns... I know I read somewhere a while ago it was an issue with some Sprint M8 models. I would like to get everything working w/o problems since it is GSM unlocked, and via QPST I unlocked all the bands.
domt91 said:
Many thanks!
For me, the biggest issue is the mobile data breakdowns... I know I read somewhere a while ago it was an issue with some Sprint M8 models. I would like to get everything working w/o problems since it is GSM unlocked, and via QPST I unlocked all the bands.
Click to expand...
Click to collapse
Also, I just found some official EU RUU's with different radio's as far as I can tell from the filename.
Maybe that could be the final solution to all the problems?

updating t-mo ruu manually.

So i was trying to install the latest nougat roms and realized i need to be on 4.xx for them.
I am on 3.xx
So i tried to update via the latest ruu from htc.
http://www.htc.com/us/support/rom-downloads.html
Did not work.
Then i realized that the rom was for a developers edition phone which mine is not.
So i downloaded the latest 3.xx rom. for the non developer phone.
After i downloaded it, I realized it was the same 4.xx ruu that i downloaded before. So i thought my mistake.
Go back and download AGAIN and yup, the link they provide in the "details and instuctions" section for the 3.xx rom is definitely for the 4.xx ruu.
When i click the download link without going into details. the link does not work.
Weird thing. on this page http://www.htc.com/us/support/updates.aspx
They do not specify developer edition.
So now the question is. IS 4.xx the latest update for all t-mo m9 phones and i am just having a problem installing.
Or do i need to find the 3.xx rom from a different source.
So i checked on a friends stock m9 and indeed it has the 4.47 update.
So i guess i am just doing something wrong. I am rooted but i never chose the option in twrp to modify files.
I can connect to the ruu in download mode. I tells me the correct rom that i have on the phone and offers to update. Once i choose update it seems to work fine. Reboots my phone then gives me error 123.
I cant seem to find a zip for it. Or a copy of the older ruu.
If anybody can point me in the direction of a database somewhere that would be super helpful. I know the mods used to keep them stickied at the top.
I do have a ruu and zip on my computer from a couple years ago that i will try too.
Tried to flash the last ruu i flashed before. got error 155 and now am stuck in flashing mode. With a half flashed phone. no way to reset it. 10 second power button does not work. cant pull the battery as the ruu advises me to do.
Guess im waiting for the phone to die from 100%
I think the problem is simple and something i totally forgot in the last couple years.
I NEED TO RE LOCK MY BOOTLOADER. but who knows. apparently its just me on here.
SO LONG FOR GOOD ADVICE FROM XDA.
BOOOO.
Please don't forget that this is a forum and not a support-hotline/-chat where people get payed for replying immediately. Most of us are doing this as their hobby and aren't able to be online 24/7. It might take some time till you get a reply. Especially if you post in a section that shows almost no activity aside from some new questions being asked. Most (former) users have already moved on to other devices due to the age of the M9 and many devs left the development scene due to the end users on xda that became more and more toxic and demanding during the last couple of years.
myphonesbetter said:
So i was trying to install the latest nougat roms and realized i need to be on 4.xx for them.
I am on 3.xx
Click to expand...
Click to collapse
You actually don't need firmware 4.x. Firmware 3.x is compatible with the latest custom roms, as well. They only run "better" on firmware 4.x.
myphonesbetter said:
So i tried to update via the latest ruu from htc.
http://www.htc.com/us/support/rom-downloads.html
Did not work.
Then i realized that the rom was for a developers edition phone which mine is not.
So i downloaded the latest 3.xx rom. for the non developer phone.
After i downloaded it, I realized it was the same 4.xx ruu that i downloaded before. So i thought my mistake.
Go back and download AGAIN and yup, the link they provide in the "details and instuctions" section for the 3.xx rom is definitely for the 4.xx ruu.
When i click the download link without going into details. the link does not work.
Click to expand...
Click to collapse
HTC is a bit lazy in regard to updating their webpage. You're always only able to download the latest RUU. However, you don't mention which variant you own. There is more than just one non-dev edition variant. Nevermind, you mentioned it in one if your following posts.
myphonesbetter said:
Weird thing. on this page http://www.htc.com/us/support/updates.aspx
They do not specify developer edition.
So now the question is. IS 4.xx the latest update for all t-mo m9 phones and i am just having a problem installing.
Or do i need to find the 3.xx rom from a different source.
Click to expand...
Click to collapse
Firmware 4.x is the latest version for all SKUs/variants and there won't be any further updates since the M9 reached the EOL stage almost a year ago.
myphonesbetter said:
So i checked on a friends stock m9 and indeed it has the 4.47 update.
Click to expand...
Click to collapse
Is that a typo? I only know about firmware 4.27.531.6 for the T-Mobile US variant.
myphonesbetter said:
So i guess i am just doing something wrong. I am rooted but i never chose the option in twrp to modify files.
Click to expand...
Click to collapse
It's possible to break the OTA-update function by modifying the system via a root file explorer, as well.
myphonesbetter said:
I can connect to the ruu in download mode. I tells me the correct rom that i have on the phone and offers to update. Once i choose update it seems to work fine. Reboots my phone then gives me error 123.
Click to expand...
Click to collapse
Is that another typo? I'd have expected error 132 since firmware 3.x and 4.x are using different encryption keys. You can't update using a RUU. You need to use the software update function of the system settings.
myphonesbetter said:
I cant seem to find a zip for it. Or a copy of the older ruu.
If anybody can point me in the direction of a database somewhere that would be super helpful. I know the mods used to keep them stickied at the top.
Click to expand...
Click to collapse
The "database" is still stickied (in not only one but two subforums of the M9 section - the general and the q&a section). Therefore, I'm a bit surprised that you weren't able to find what you're looking for. In addition the thread I'm talking about is not only a database, it even contains all information you would have needed for solving your issues, already.
myphonesbetter said:
I do have a ruu and zip on my computer from a couple years ago that i will try too.
Click to expand...
Click to collapse
If the RUU is older than your current firmware then you won't be able to use it.
myphonesbetter said:
Tried to flash the last ruu i flashed before. got error 155 and now am stuck in flashing mode. With a half flashed phone. no way to reset it. 10 second power button does not work. cant pull the battery as the ruu advises me to do.
Guess im waiting for the phone to die from 100%
Click to expand...
Click to collapse
Error 155 means that you either try to flash a RUU that is too old or made for a different variant than the one you own. The key combination you're looking for is the power button plus volume down up and you need to keep them pressed for about 30 seconds. HTC changed that on one of the devices that came out before the M9. Letting the battery die is a bad idea, though. You'll damage it this way.
myphonesbetter said:
I think the problem is simple and something i totally forgot in the last couple years.
I NEED TO RE LOCK MY BOOTLOADER. but who knows. apparently its just me on here.
Click to expand...
Click to collapse
No you don't. I can't discourage people enough from relocking this phone's bootloader if the phone is S-ON and not 100% stock and you don't have a RUU at hand that you already used successfully on your phone. HTC's security checks will prevent the device from booting if anything is modified (e.g. TWP being installed) while the bootloader is locked or relocked. They don't differentiate between "broken" and "custom" files and think that the modified software is broken. Therefore, the checks are trying to prevent the hardware from getting damaged by preventing the device from booting. In addition, if OEM Unlock isn't activated in the developer settings of the currently installed rom then there is no way to re-unlock the phone. That's an FRP (factory reset protection) Google introduced with android 5.1 (which equals firmware 2.x of the M9).
Flippy498 said:
Please don't forget that this is a forum and not a support-hotline/-chat where people get payed for replying immediately. Most of us are doing this as their hobby and aren't able to be online 24/7. It might take some time till you get a reply. Especially if you post in a section that shows almost no activity aside from some new questions being asked. Most (former) users have already moved on to other devices due to the age of the M9 and many devs left the development scene due to the end users on xda that became more and more toxic and demanding during the last couple of years.
Click to expand...
Click to collapse
Yah. I get it. Was kind of just shouting to get some attention.
Ive noticed that not just this forum but many other forums that i used to use have lossed a lot of popularity.
I think because facbook groups and things like reddit that cover all subjects.
The problem with those places is that they are so unorganized.
Maybe thats also part of why its become so unorganized here. just what people are used to.
I honestly wasnt expecting actual info. Thank you.
Flippy498 said:
You actually don't need firmware 4.x. Firmware 3.x is compatible with the latest custom roms, as well. They only run "better" on firmware 4.x.
Click to expand...
Click to collapse
Well i was afraid to brick it so i figured out (accidentally) how to update.
Flippy498 said:
Firmware 4.x is the latest version for all SKUs/variants and there won't be any further updates since the M9 reached the EOL stage almost a year ago.
Is that a typo? I only know about firmware 4.27.531.6 for the T-Mobile US variant It's possible to break the OTA-update function by modifying the system via a root file explorer, as well..
Click to expand...
Click to collapse
Yes that was. it is 4.27.
I could not find any older ruu's on their site. Or anywhere for that matter. none with active links at least.
Flippy498 said:
Is that another typo? I'd have expected error 132 since firmware 3.x and 4.x are using different encryption keys. You can't update using a RUU. You need to use the software update function of the system settings.
Click to expand...
Click to collapse
Yes 132. I did not realize that. Do you mean i would need to update via ota? by searching for updates.
Flippy498 said:
If the RUU is older than your current firmware then you won't be able to use it.
Error 155 means that you either try to flash a RUU that is too old or made for a different variant than the one you own. The key combination you're looking for is the power button plus volume down and you need to keep them pressed for about 30 seconds. HTC changed that on one of the devices that came out before the M9. Letting the battery die is a bad idea, though. You'll damage it this way.
Click to expand...
Click to collapse
So i was originally trying to flash the latest frimware 4.27.xxx but i kept getting error 132.
And on the htc website it has 2 sections for ruu's m9 ans m9 developer. So i just figured it was the wrong one.
So i figured i would try the last ruu that i flashed before installing the rom that i ran for almost 2 years (lee droid)
when i flashed that, it got halfway through and gave me error 155. but left my phone in the middle of an update. Apparently the power button is disabled during this process.
it tell you to pull the battery or hold the power button for 10 seconds then try to recover from the boot using the ruu.
Well i could not reboot the phone so i just started the recover process. This rebooted my phone a few times then just started flashing the rom. To my surprise it worked.
It also re-locked my phone.
After that, now that im stock, i tried to flash the 4.27 ruu. still 132.
So i tried to run the ota's and they worked.
Took about 4 hours and 7 updates or so. probably 5 gigs on the data plan but finally it finshed with a 1.1 gig update to 4.27.
Im not sure why the first flash failed or why it worked, but eventually it did work.
Flippy498 said:
No you don't. I can't discourage people enough from relocking this phone's bootloader if the phone is S-ON and not 100% stock and you don't have a RUU at hand that you already used successfully on your phone. HTC's security checks will prevent the device from booting if anything is modified (e.g. TWRP being installed) while the bootloader is locked or relocked. They don't differentiate between "broken" and "custom" files and think that the modified software is broken. Therefore, the checks are trying to prevent the hardware from getting damaged by preventing the device from booting. In addition, if OEM Unlock isn't activated in the developer settings of the currently installed rom then there is no way to re-unlock the phone. That's an FRP (factory reset protection) Google introduced with android 5.1 (which equals firmware 2.x of the M9).
Click to expand...
Click to collapse
Ive always relocked my htcs before running an ruu. If not then they never seem to work. I dont mind it because it takes about 10 seconds. and i already hae the token. I actually remembered the majority of the commands.
Maybe its causing another problem that i dont know about.
I did see the oem unlock in developer options if that is what you are talking about.
I was using the last ruu that i had used. but i also flashed a rom and it was a long time in between.
Also i installed the old version of lee droid on 4.27.xxx and it seemed to work fine. I did this on accident though. Flashed the wrong zip. Re-flashed the latest 4.0 and it seems to be working great. Noticing a couple little lags. Might go to the stock rom just rooted and debloated. It seemed to run a little smoother than leedroid for the time i was using it. but i felt like they were trying to extract my stem cells via confusing TOS agreements.
myphonesbetter said:
Apparently the power button is disabled during this process.
it tell you to pull the battery or hold the power button for 10 seconds then try to recover from the boot using the ruu.
[...]
It also re-locked my phone.
After that, now that im stock, i tried to flash the 4.27 ruu. still 132.
So i tried to run the ota's and they worked.
Ive always relocked my htcs before running an ruu. If not then they never seem to work. I dont mind it because it takes about 10 seconds. and i already hae the token. I actually remembered the majority of the commands.
Maybe its causing another problem that i dont know about.
I did see the oem unlock in developer options if that is what you are talking about.
Click to expand...
Click to collapse
The power button isn't disabled. As said in my last post, you need to press the power button and the volume down button for 30 seconds. It's always been like that on the M9 since HTC already changed that on the M7 or M8 (can't tell you which one exactly it was).
Relocking was only needed on HTC phones that are older than the M9. HTC changed that with the M9. And as said in my last post, re-locking the M9 if you don't have a RUU at hand that you already used successfully is more than dangerous due to Google's FRP. You might end with a non-booting non-unlockable phone.
In addition, a relocked dootloader doesn't change the fact, that your phone is missing the needed encryption keys. That's why the 4.x RUU still failed.
However, it's nice to hear that you could solve your problems now. ?
Sent from my HTC One M9 using XDA Labs
Ah, I made a mistake while writing my posts. It's power and volume up. Not power and volume down. :silly:

Categories

Resources