Related
I'm stuck in the bootloader with S-ON Tampered, Locked, and Security Warning flags. Can't find an encrypted RUU or figure out how to encrypt the one I have to get this rolling again, can anybody give me a clue or anything on how to go about doing this or getting this thing functional again?
You can get the ruus at the bottom of this post. http://forum.xda-developers.com/showthread.php?p=46506621
cmlusco said:
You can get the ruus at the bottom of this post. http://forum.xda-developers.com/showthread.php?p=46506621
Click to expand...
Click to collapse
Yes, it always says:
FAILED (status read failed (too many links))
Probably because its 2.10 RUU and mine is on 3.11?
Yeah an s-on phone wont allow you to flash an ruu version older than the one already on the phone. And unfortunatley, we do not have the newest ruu available yet.
So there's nothing I can do but wait? I was pretty sure I had everything flashed back to stock but once I turned S-ON it wouldn't let me go past the bootloader. My phone's sound completely stopped working so I was going to take it in to get it taken care of, but I guess I can't do anything at all now.
You can probably still flash the RUU if you get the correct one i would assume. I've reset the tampered flags before also. I always made it a point to flash the older RUU's before flipping s-on for a warranty return, because it is so much easier to get s-off in case I mess something up, so not sure how being on that newer firmware is going to play out.
ccarr313 said:
You can probably still flash the RUU if you get the correct one i would assume. I've reset the tampered flags before also. I always made it a point to flash the older RUU's before flipping s-on for a warranty return, because it is so much easier to get s-off in case I mess something up, so not sure how being on that newer firmware is going to play out.
Click to expand...
Click to collapse
Yeah I'm just keeping an eye open and checking for the latest RUU. First time getting into this stuff, so lesson learned. Just sucks I'm without a phone even just to text/apps until then.
I have the same issue
GrayFalcon11 said:
Yeah I'm just keeping an eye open and checking for the latest RUU. First time getting into this stuff, so lesson learned. Just sucks I'm without a phone even just to text/apps until then.
Click to expand...
Click to collapse
I was S-Off and unlocked and rooted, I was trying to flash back to stock for a warranty exchange. Now I'm Locked, S-On and flagged Tampered and stuck in the bootloader. I'm on 3.11.605.10 as well. I only have 4 days left to send this back to verizon.. Any suggestions? or I'm I butt ****ed with no lube.
keith7120 said:
I was S-Off and unlocked and rooted, I was trying to flash back to stock for a warranty exchange. Now I'm Locked, S-On and flagged Tampered and stuck in the bootloader. I'm on 3.11.605.10 as well. I only have 4 days left to send this back to verizon.. Any suggestions? or I'm I butt ****ed with no lube.
Click to expand...
Click to collapse
What happen? I have 3 days left to send back to Verizon and I'm still s-off and unlocked and I don't wanna mess it up.
Do an older ruu.
Lock bootloader using fastboot.
Go s-on using fastboot.
Do a signed ruu.
cmlusco said:
Do an older ruu.
Lock bootloader using fastboot.
Go s-on using fastboot.
Do a signed ruu.
Click to expand...
Click to collapse
Why 2 ruu?
Probably not really needed, but just to be sure the phone got wiped out.
Let Me Make sure I understand
cmlusco said:
Probably not really needed, but just to be sure the phone got wiped out.
Click to expand...
Click to collapse
Can I or can I not flash an older RUU?
How do I get a hold of a signed RUU? Is it the one that says decrypted?
Will this at least allow me to wipe the phone to where it does not say tampered?
I could have sworn I have tried these RUU's but I get a remote signature error.
No if you are s-on you can not flash an ruu which is an older version than the phone is currently on.
The signed and decrypted (not signed) ruu's can be found at the bottom of the second post of santods rom radio kernel thread in development. http://forum.xda-developers.com/showthread.php?p=46506621
In order to remove the tampered flag you would need to get s-off again. I believe there is a new exploit for 4.2.2 http://forum.xda-developers.com/showthread.php?p=51481200, if you want to go that route.
Remote sig error is because you were trying to flash an unsigned ruu while s-on.
oh well
cmlusco said:
No if you are s-on you can not flash an ruu which is an older version than the phone is currently on.
The signed and decrypted (not signed) ruu's can be found at the bottom of the second post of santods rom radio kernel thread in development. http://forum.xda-developers.com/showthread.php?p=46506621
In order to remove the tampered flag you would need to get s-off again. I believe there is a new exploit for 4.2.2 http://forum.xda-developers.com/showthread.php?p=51481200, if you want to go that route.
Remote sig error is because you were trying to flash an unsigned ruu while s-on.
Click to expand...
Click to collapse
Welp, a couple seconds in the microwave solved my dilemma. I hope. It won't come back on.
Next question, my replacement device has 4.4.2 on it. Will the current S-off tools work to flip it from S-on to S-off?
keith7120 said:
Welp, a couple seconds in the microwave solved my dilemma. I hope. It won't come back on.
Next question, my replacement device has 4.4.2 on it. Will the current S-off tools work to flip it from S-on to S-off?
Click to expand...
Click to collapse
Yup, just follow the directions on the WeakSauce thread. -> http://forum.xda-developers.com/showthread.php?t=2699091
eman7131 said:
Yup, just follow the directions on the WeakSauce thread. -> http://forum.xda-developers.com/showthread.php?t=2699091
Click to expand...
Click to collapse
Thanks, I'm now S-Off
how would i go about going S-On in fastboot? my fiance device was thought to be returned to stock but we found out that it says Relocked but still says S-Off and when we try to use Firewater it stops after we say Yes cause for some reason its already showing S-off but the bootloader is actually locked.
Stuck Bootloader
Hi i need help. I am stuck in bootloader with s On and relocked. Ive read everything and no go. Please help any one
hi there,
i have searched along the internet a lot time ago and i cant find guide to: how to get back my htc one m8 from s-off to s-on.
if there is a such guide, i would be happy to use it
meido132 said:
hi there,
i have searched along the internet a lot time ago and i cant find guide to: how to get back my htc one m8 from s-off to s-on.
if there is a such guide, i would be happy to use it
Click to expand...
Click to collapse
fastboot oem writesecureflag 3
exad said:
fastboot oem writesecureflag 3
Click to expand...
Click to collapse
that's it?
"writesecureflag 3" i need to write seprate or together?(write secure flag 3)
Nope as I wrote it.
Sent from my HTC One_M8 using Tapatalk
exad said:
Nope as I wrote it.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
and what is gonna happen to the HTC? its gonna delete something(apps games etc)?
meido132 said:
and what is gonna happen to the HTC? its gonna delete something(apps games etc)?
Click to expand...
Click to collapse
Nothing, all the command does is set the phone back to S-ON. You have to be 100% stock, and I mean 100%, otherwise it can possibly brick the phone
EddyOS said:
Nothing, all the command does is set the phone back to S-ON. You have to be 100% stock, and I mean 100%, otherwise it can possibly brick the phone
Click to expand...
Click to collapse
what is 100% stock?
bootloader relock/lock
recovery stock
the original apps
?
meido132 said:
what is 100% stock?
bootloader relock/lock
recovery stock
the original apps
?
Click to expand...
Click to collapse
Yep, everything as when you first got the phone - original everything
Also.. why are you going S-ON? Generally not recommended to do so
@EddyOS: I know, you must hate me, I keep asking you the same questions in different threads.
Why everything stock? Isn't it enough to revert those things protected by the security flag back to stock? (e.g. radio) One can have a custom ROM, recovery and unlocked bootloader staying S-ON, the phone is fine with that, so why should it be important to revert those things to stock?
Thanks.
it is not 100% stock, it throws a security flag on the m8. even running ruu afterwards will not remove it.
EddyOS said:
...it can possibly brick the phone
Click to expand...
Click to collapse
Black Antitoon said:
@EddyOS: I know, you must hate me, I keep asking you the same questions in different threads.
Why everything stock? Isn't it enough to revert those things protected by the security flag back to stock? (e.g. radio) One can have a custom ROM, recovery and unlocked bootloader staying S-ON, the phone is fine with that, so why should it be important to revert those things to stock?
Thanks.
Click to expand...
Click to collapse
Don't ask me why it's just a lot of people have managed to brick their phone cause they've had a custom HBOOT (to remove the red writing), forgot it and bricked the phone
@an0ther: I'm not sure I understand what you said. You mean that even if you reset everything to stock (including s-on and the "tampered" banner) HTC will still be able to read another internal "tampered" flag? Or what else?
@EddyOS: thanks, so you are basically saying I am correct, and reverting everything to stock is a precaution to make sure nothing (like the HBOOT) has been forgotten, right?
Black Antitoon said:
@an0ther: I'm not sure I understand what you said. You mean that even if you reset everything to stock (including s-on and the "tampered" banner) HTC will still be able to read another internal "tampered" flag? Or what else?
@EddyOS: thanks, so you are basically saying I am correct, and reverting everything to stock is a precaution to make sure nothing (like the HBOOT) has been forgotten, right?
Click to expand...
Click to collapse
Yes. If you're certain it's stock then go ahead. Just remember you have been warned so on your head be it
Thank you again. I will say it's your fault when I forget my HBOOT and brick my phone.
SaHiLzZ said:
Also.. why are you going S-ON? Generally not recommended to do so
Click to expand...
Click to collapse
because if i want to get OTA updates, i want that everything will be stock(recovery stock,s-on,unroot)
meido132 said:
because if i want to get OTA updates, i want that everything will be stock(recovery stock,s-on,unroot)
Click to expand...
Click to collapse
You don't need to be S-ON to flash an OTA, just stock with everything else (I know cause I flashed the new OTA manually the other day and it worked fine )
EddyOS said:
You don't need to be S-ON to flash an OTA, just stock with everything else (I know cause I flashed the new OTA manually the other day and it worked fine )
Click to expand...
Click to collapse
where i can find the ota updates to flash them in my htc one m8? and how i can find my ruu of HTC ONE M8?
there is a new ota that size 70 mb with some improvements and i want to flash it like you said
Black Antitoon said:
@an0ther: I'm not sure I understand what you said. You mean that even if you reset everything to stock (including s-on and the "tampered" banner) HTC will still be able to read another internal "tampered" flag? Or what else?
@EddyOS: thanks, so you are basically saying I am correct, and reverting everything to stock is a precaution to make sure nothing (like the HBOOT) has been forgotten, right?
Click to expand...
Click to collapse
Yes, there is no way that HTC will not know that you have messed with the phone. You don't need s-on for ota updates, in fact, if you are s-off, you don't even need to lock your boot loader. Anyways, you can just dl ota updates just as easy.
At&t 1.58.502.1
EddyOS said:
Yes. If you're certain it's stock then go ahead. Just remember you have been warned so on your head be it
Click to expand...
Click to collapse
I have this version of software for AT&T, and I would like to know: If I remove tampered flag and reset to locked and S-ON and then restore using a SIGNED RUU EXE FILE for this software version, will I be ok (as in not get a security warning and look 100% stock)?
Hello guys,
My friend is having a problem with his HTC One M8 camera. It doesn't start. We tried third party camera app, did flashed ViperOneM8 3.2.1 , wiped data, wiped everything even internal memory, wiped camera data cache, don't have installed lastpass.. Before it used to crash when it was on stock but after updating to ViperOneM8 camera app does open but it stays black there and also as you can see there are only two selfie and photobooth options.. missing other options
Phone is unlocked, SuperCID, S Off if anyone could help me?
Edit: Tried safe mode also but still same problem
Ampicillin said:
Hello guys,
My friend is having a problem with his HTC One M8 camera. It doesn't start. We tried third party camera app, did flashed ViperOneM8 3.2.1 , wiped data, wiped everything even internal memory, wiped camera data cache, don't have installed lastpass.. Before it used to crash when it was on stock but after updating to ViperOneM8 camera app does open but it stays black there and also as you can see there are only two selfie and photobooth options.. missing other options
Phone is unlocked, SuperCID, S Off if anyone could help me?
Edit: Tried safe mode also but still same problem
Click to expand...
Click to collapse
Try flashing a full ruu and not a rom, if problem still there its hardware.
For that I'd need to go back to from SuperCID to original CID right? And I'll need to remove TWRP recovery , I'm S OFF will that create any problem? Will I loose S Off if I run RUU?
Sent from my HTC One M8
Ampicillin said:
For that I'd need to go back to from SuperCID to original CID right? And I'll need to remove TWRP recovery , I'm S OFF will that create any problem? Will I loose S Off if I run RUU?
Sent from my HTC One M8
Click to expand...
Click to collapse
you wont lose s off if u run a ruu.
toysoldierq said:
you wont lose s off if u run a ruu.
Click to expand...
Click to collapse
Okay, Thank you. I'll run RUU
Sent from my HTC One M8
Ampicillin said:
Okay, Thank you. I'll run RUU
Sent from my HTC One M8
Click to expand...
Click to collapse
But not just any ruu one that matches your mid and cid.
toysoldierq said:
But not just any ruu one that matches your mid and cid.
Click to expand...
Click to collapse
Yep, I see. My friend and I both having same 0P6B10000 MID and CID but I had a stock backup of mine using TWRP would mine stock backup work in his Phone? If I change folder back up name to his device ID ? Since both the phones are the same. So it might make camera work. I think the problem is "with the wiped internal memory" it caused the problem with the cameraw
Sent from my HTC One M8
Ampicillin said:
Yep, I see. My friend and I both having same 0P6B10000 MID and CID but I had a stock backup of mine using TWRP would mine stock backup work in his Phone? If I change folder back up name to his device ID ? Since both the phones are the same. So it might make camera work. I think the problem is "with the wiped internal memory" it caused the problem with the cameraw
Sent from my HTC One M8
Click to expand...
Click to collapse
Yes it would work once your mid and his mid are the same, a full ruu would fix any problem rather than a back up it could be something mess up in the hboot are other part of the phone causing the issue, thats why i advice using a full ruu but you can try that way first.
toysoldierq said:
Yes it would work once your mid and his mid are the same, a full ruu would fix any problem rather than a back up it could be something mess up in the hboot are other part of the phone causing the issue, thats why i advice using a full ruu but you can try that way first.
Click to expand...
Click to collapse
Okay thank you
Sent from my HTC One M8
Ampicillin said:
For that I'd need to go back to from SuperCID to original CID right? And I'll need to remove TWRP recovery , I'm S OFF will that create any problem? Will I loose S Off if I run RUU?
Click to expand...
Click to collapse
No, no, no and no.
1) No, you don't need to change from SuperCID to run (any) RUU. SuperCID is called "super" for a reason. It will pass CID check for any CID, essentially bypassing CID check.
2) No, you don't need to revert to stock recovery to run RUU. This is only required when installing stock OTA, so folks often get the 2 confused.
3) S-off won't cause an issue with RUU. In fact, it makes it easier as it removes the requirement to relock the bootloader in order to run the RUU (required if s-on).
4) No, RUU will not return you to s-on. Nothing will, except making it s-on manually yourself.
redpoint73 said:
No, no, no and no.
1) No, you don't need to change from SuperCID to run (any) RUU. SuperCID is called "super" for a reason. It will pass CID check for any CID, essentially bypassing CID check.
2) No, you don't need to revert to stock recovery to run RUU. This is only required when installing stock OTA, so folks often get the 2 confused.
3) S-off won't cause an issue with RUU. In fact, it makes it easier as it removes the requirement to relock the bootloader in order to run the RUU (required if s-on).
4) No, RUU will not return you to s-on. Nothing will, except making it s-on manually yourself.
Click to expand...
Click to collapse
So, I just do from unlocked to locked boot loader? Or that also don't require?
Sent from my HTC One M8
I downloaded official RUU from HTCdev site 4.16.401.10 for easteurope can I flash it?
Running viperonem8, unlocked bootloader do I need to lock the bootloader?
Ampicillin said:
So, I just do from unlocked to locked boot loader? Or that also don't require?
Click to expand...
Click to collapse
Since you are s-off, no need to relock the bootloader. And I recommend to leave it unlocked. Having it unlocked won't affect anything (prevent anything from flashing), while relocking it will prevent anything unsigned from flashing until you relock it. So for the most part, there is no benefit to relocking as long as you are s-off.
SORRY, Guys was busy. I couldn't find full .EXE Europe RUU but I found RUU_M8_UHL_L50_SENSE60_MR_hTC_Asia_India_4.18.720.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_417228_signed EXE file.
Can I use this one for HTC One M8 Europe?
Greetings- I have an M8 running CM12 (nightly)
main 4.20.666.1
hboot 3.19.0.0.0000
S-On
CM12 nightly
twrp2.6
SuperSU
I'm hoping to restore to upgrade but the *$$*%*$ S-On issue won't allow me to. My original recovery is corrupt/gone and I just wonder if anyone has any (good) ideas?
Tried Firewater and got the PIE error.
You guys are doing a great job here- I've learned alot lurking and hope to continue...
cheerss
Superflous said:
I'm hoping to restore to upgrade but the *$$*%*$ S-On issue won't allow me to.
Click to expand...
Click to collapse
What exactly are you trying to do, that you think s-on is preventing? Unless I'm missing something, I don't think there is anything you are trying to do, that would be impeded by s-on.
Superflous said:
My original recovery is corrupt/gone and I just wonder if anyone has any (good) ideas?
Click to expand...
Click to collapse
Stock recovery for your main version is posted by ckpv5 here: http://forum.xda-developers.com/showpost.php?p=58947150&postcount=4708
Superflous said:
Tried Firewater and got the PIE error.
Click to expand...
Click to collapse
Firewater was discontinued by the developer 6 months ago (online service, so no longer works).
Sunshine is the only current s-off method, if you really need s-off (not clear that you do).
redpoint73 said:
Stock recovery for your main version is posted by ckpv5 here: http://forum.xda-developers.com/showpost.php?p=58947150&postcount=4708
Click to expand...
Click to collapse
Already moved my stock recovery collection to here : http://forum.xda-developers.com/showpost.php?p=60211779&postcount=4
All in one place and easier to find I guess.
ckpv5 said:
Already moved my stock recovery collection to here : http://forum.xda-developers.com/showpost.php?p=60211779&postcount=4
All in one place and easier to find I guess.
Click to expand...
Click to collapse
Certainly great to have it in one place, and thanks for doing so!
redpoint73 said:
What exactly are you trying to do, that you think s-on is preventing? Unless I'm missing something, I don't think there is anything you are trying to do, that would be impeded by s-on.
Stock recovery for your main version is posted by ckpv5 here: http://forum.xda-developers.com/showpost.php?p=58947150&postcount=4708
Firewater was discontinued by the developer 6 months ago (online service, so no longer works).
Sunshine is the only current s-off method, if you really need s-off (not clear that you do).
Click to expand...
Click to collapse
tx for recovery link, sorry if it wasn't explained right but i want to restore my phone back to Bell firmware and lollipop . I spoke with the Root ninja via email ans Sunshine won't work on my phone(their words). I have tried to install the "firmware_M8SD_4.20.666.1_Modified_Bell_Canada.zip" but it fails and locks me up in the blue CM head until I reset, then reverts back to CM12. I'm just getting into this but if I understand correct you need S-off to flash firmware. If this isn't right I would sure appreciate the path to the correct way to put my phone back to original. Tx for you help
Superflous said:
I have tried to install the "firmware_M8SD_4.20.666.1_Modified_Bell_Canada.zip" but it fails and locks me up in the blue CM head until I reset, then reverts back to CM12. I'm just getting into this but if I understand correct you need S-off to flash firmware.
Click to expand...
Click to collapse
Somewhat correct. If the firmware is official (signed and encrypted) and for your CID, it will flash with s-on.
However, once the firmware has been modified in any way (as the one you tried clearly is) or otherwise not signed, you can't flash it unless you have s-off.
But I don't think flashing firmware is what you really want. You might be mixing up firmware with software (ROM). Firmware are the partitions that don't get changed when you flash a ROM. Firmware includes hboot, radio, and some other modules (WiFi, media, etc.). Since you need s-off to flash an "unofficial" firmware, and you are still s-on, you should still be on the stock firmware. And therefore, no need to "return to stock" since you still are stock.
What I think you mean, is that you want to return to stock ROM (since you are on CM12) and stock recovery. None of which require s-off. After that you can relock the bootloader. But it will always say RELOCKED instead of LOCKED, as the latter requires s-off. If you are selling or giving the phone away, RELOCKED should be sufficient for most folks. Although I highly recommend disclosing that the bootloader was previously unlocked, root, etc. to the new owner.
redpoint73 said:
Somewhat correct. If the firmware is official (signed and encrypted) and for your CID, it will flash with s-on.
However, once the firmware has been modified in any way (as the one you tried clearly is) or otherwise not signed, you can't flash it unless you have s-off.
But I don't think flashing firmware is what you really want. You might be mixing up firmware with software (ROM). Firmware are the partitions that don't get changed when you flash a ROM. Firmware includes hboot, radio, and some other modules (WiFi, media, etc.). Since you need s-off to flash an "unofficial" firmware, and you are still s-on, you should still be on the stock firmware. And therefore, no need to "return to stock" since you still are stock.
What I think you mean, is that you want to return to stock ROM (since you are on CM12) and stock recovery. None of which require s-off. After that you can relock the bootloader. But it will always say RELOCKED instead of LOCKED, as the latter requires s-off. If you are selling or giving the phone away, RELOCKED should be sufficient for most folks. Although I highly recommend disclosing that the bootloader was previously unlocked, root, etc. to the new owner.
Click to expand...
Click to collapse
'
so then I'm looking for a stock ROM from the carrier for firmware 4.20.666.1
tx again Redpoint
redpoint73 said:
Somewhat correct. If the firmware is official (signed and encrypted) and for your CID, it will flash with s-on.
However, once the firmware has been modified in any way (as the one you tried clearly is) or otherwise not signed, you can't flash it unless you have s-off.
But I don't think flashing firmware is what you really want. You might be mixing up firmware with software (ROM). Firmware are the partitions that don't get changed when you flash a ROM. Firmware includes hboot, radio, and some other modules (WiFi, media, etc.). Since you need s-off to flash an "unofficial" firmware, and you are still s-on, you should still be on the stock firmware. And therefore, no need to "return to stock" since you still are stock.
What I think you mean, is that you want to return to stock ROM (since you are on CM12) and stock recovery. None of which require s-off. After that you can relock the bootloader. But it will always say RELOCKED instead of LOCKED, as the latter requires s-off. If you are selling or giving the phone away, RELOCKED should be sufficient for most folks. Although I highly recommend disclosing that the bootloader was previously unlocked, root, etc. to the new owner.
Click to expand...
Click to collapse
As a followup- tx for taking the time to explain- I have set the phone back to stock and happy to have learned some.
You are one of the good ones'
Cheers
Superflous said:
As a followup- tx for taking the time to explain- I have set the phone back to stock and happy to have learned some.
You are one of the good ones'
Cheers
Click to expand...
Click to collapse
You're very welcome. Glad to see it worked out well for you.
Please click the "Thanks" button for any posts you found helpful.
I'm done with these issues that my phone is having. It keeps locking up no matter what ROM I use or how little apps I have installed. Something has got to be wrong with my phone and it's time to bring it back to TMO for repair/replacement.
I found this link on HTC to download the RUU: http://www.htc.com/us/support/rom-downloads.html#tmobile
My question is, would this be enough to bring my phone back to stock so that they don't know I've rooted it?
Edit: Also, I just remembered about my bootloader being s-off/unlocked. Would this make a difference or would the RUU set everything back like it should?
Edit again: I found this thread: http://forum.xda-developers.com/showthread.php?t=2735235
So, would I be able to follow his instructions but change the CID to t-mob010 instead of the ones he has listed?
Nobody? I could really use some input on this, I don't want to brick my phone. I have to do this today, I can't take the lockups anymore.
There is a thread dedicated to returning your device to stock. It's intended for European users, but the instructions apply equally well to US users.
The first step is running the RUU, then locking (not relocking) the bootloader using adb commands. Reference http://forum.xda-developers.com/showthread.php?t=2708571 (for instructions on locking your bootloader)
Note that you can run the RUU without locking your bootloader if you are S-off. Once you are back to bone stock (recovery + OS), you can then go back S-on if you are concerned about the warranty, though I strongly advise AGAINST this in general.
Also, you may find that simply re-running the RUU will clear up your issue. I'd run it for a few days after restoring the phone before assuming a hardware fault.
jshamlet said:
There is a thread dedicated to returning your device to stock. It's intended for European users, but the instructions apply equally well to US users.
The first step is running the RUU, then locking (not relocking) the bootloader using adb commands. Reference http://forum.xda-developers.com/showthread.php?t=2708571 (for instructions on locking your bootloader)
Note that you can run the RUU without locking your bootloader if you are S-off. Once you are back to bone stock (recovery + OS), you can then go back S-on if you are concerned about the warranty, though I strongly advise AGAINST this in general.
Also, you may find that simply re-running the RUU will clear up your issue. I'd run it for a few days after restoring the phone before assuming a hardware fault.
Click to expand...
Click to collapse
Yes, I did find that post and am planning on following those instructions. However, you've confused me. According to that thread, they say to lock the bootloader first and then install the RUU; but you said the opposite. Which is it?
http://forum.xda-developers.com/showthread.php?t=2735235
Also, why are you against turning back S-on? I had planned on it because I don't want to take the chance of TMO or HTC having a problem.
ned4spd8874 said:
Yes, I did find that post and am planning on following those instructions. However, you've confused me. According to that thread, they say to lock the bootloader first and then install the RUU; but you said the opposite. Which is it?
http://forum.xda-developers.com/showthread.php?t=2735235
Also, why are you against turning back S-on? I had planned on it because I don't want to take the chance of TMO or HTC having a problem.
Click to expand...
Click to collapse
You are S-off, which means you do NOT have to lock the bootloader first. Most instructions for running an RUU assume you are S-on, however, which does require your bootloader to be locked. It's one of the checks that is disabled by S-off.
Also, S-off is getting harder to obtain, so unless there is a pressing reason to go S-on, it's safer to remain S-off. Warranty support could be that pressing reason.
Time to turn back S-on. Even after the RUU, it's still very buggy. Locking up, slow, lag, etc. Time to bring it back to TMO.
Anyone know what that will work? I do have the warranty service on it. So will they just replace my phone with a refurb M8, will it be sent out, what can I expect?
ned4spd8874 said:
Time to turn back S-on. Even after the RUU, it's still very buggy. Locking up, slow, lag, etc. Time to bring it back to TMO.
Anyone know what that will work? I do have the warranty service on it. So will they just replace my phone with a refurb M8, will it be sent out, what can I expect?
Click to expand...
Click to collapse
If you think your phone has bad hardware, then yeah, at this point you need to go ahead and S-on with the assumption that you will get a refurb - especially now that the M9 has been out a while. Who knows what you will get, though. You might even luck out and get a "new old stock" device with 4.4.2. Or, the refurb place could RUU it up to the latest. It's purely the luck of the draw.
Well this sucks. Can't get adb to recognize my phone in recovery. I can when it's booted into the system, but not recovery or the bootloader....
What a pain this is becoming!!!!!!!!!!!! I'm even trying to get into shell when the phone is booted up and sure I can do that, but I can't su! The binary isn't installed. So, what now I have to f'ing install a different ROM, s-on it and then ruu again????
So I f'ed up and turned S-ON by mistake before I did the commands to clear the bootloader modified messages. And now I can't get S-OFF for the life of me! Sunshine can't get root it says, SuperSU is installed and says a binary needs updating, but when I click on it, it just freezes and won't update the binary. I tried pushing it down via zip/bootloader but that doesn't help. I ran a root checker and it says my phone is rooted, but nothing is working like I expect it to.
I'm still running the stock ROM from the RUU, could that be the issue? Do I have to install a different ROM before I can S-OFF and then RUU again? This is such a pain!!!
ned4spd8874 said:
So I f'ed up and turned S-ON by mistake before I did the commands to clear the bootloader modified messages. And now I can't get S-OFF for the life of me! Sunshine can't get root it says, SuperSU is installed and says a binary needs updating, but when I click on it, it just freezes and won't update the binary. I tried pushing it down via zip/bootloader but that doesn't help. I ran a root checker and it says my phone is rooted, but nothing is working like I expect it to.
I'm still running the stock ROM from the RUU, could that be the issue? Do I have to install a different ROM before I can S-OFF and then RUU again? This is such a pain!!!
Click to expand...
Click to collapse
If you are still bootloader unlocked, install TWRP, restore an appropriate nandroid backup for your device, root that install, and re-run Sunshine.
If you are bootloader locked, restart the phone into bootloader mode and select the RUU option. Then, re-run the RUU. If your bootloader is locked, it should run and restore everything to stock. Note that if you updated to Lollipop, you may have to use Kingroot to get temp root. I meant to suggest you RUU down to the original version (4.4.2) prior to going S-on and forgot - sorry about that.
jshamlet said:
If you are still bootloader unlocked, install TWRP, restore an appropriate nandroid backup for your device, root that install, and re-run Sunshine.
If you are bootloader locked, restart the phone into bootloader mode and select the RUU option. Then, re-run the RUU. If your bootloader is locked, it should run and restore everything to stock. Note that if you updated to Lollipop, you may have to use Kingroot to get temp root. I meant to suggest you RUU down to the original version (4.4.2) prior to going S-on and forgot - sorry about that.
Click to expand...
Click to collapse
Bootloader is still unlocked, but even after installing a couple different ROMs, sunshine just won't work. Says it's incompatible. It says to flash a stock sense or near stock rom. I'm on SkyDragon right now...
I'm at a loss. Anyone have a industrial shredder?
ned4spd8874 said:
Bootloader is still unlocked, but even after installing a couple different ROMs, sunshine just won't work. Says it's incompatible. It says to flash a stock sense or near stock rom. I'm on SkyDragon right now...
I'm at a loss. Anyone have a industrial shredder?
Click to expand...
Click to collapse
There are probably some T-mobile nandroid backups around here somewhere. Get one, put it on an SD card, and use TWRP to flash it. Unfortunately, I only have DevEd and AT&T images.
jshamlet said:
There are probably some T-mobile nandroid backups around here somewhere. Get one, put it on an SD card, and use TWRP to flash it. Unfortunately, I only have DevEd and AT&T images.
Click to expand...
Click to collapse
Things are looking up! Found a ROM called something like Alex V that was stock enough to get SunShine to work. Also, I was using the original version so once I got it to run, it was giving network errors. Once I installed the latest version, that's when I got was able to go S-OFF. So, now I'm S-OFF, the bootloader is saying Official and locked so now I'm going to RUU and throw it in TMO's face!