Database Info

[Q] Return to as close to stock as possible

Hi all,
I have an AT&T One X. The bootloader is unlocked but is S-ON. I want to return this phone to as close as stock as possible. This phone is destined to go to another user who knows nothing of rooting and such so I don't care if it is rooted or not.
I understand I have to relock the bootloader to be able to flash an RUU right? Hboot is currently at 1.14.002, Radio is at 0.19as.32.09.11_2. TWRP 2.3.1.0 is installed.
The phone is currently running Cleanrom 6.5 and all works fine. I just want this back to as close to AT&T stock as possible so that the user I am giving the phone to will not have any problems.
If I relock the bootloader can I return this to stock via the most recent AT&T 3.18 RUU located here: http://forum.xda-developers.com/showthread.php?t=2191477 or is there something else I need to do first?
Thanks for all your help.

Tersanyus said:
Hi all,
I have an AT&T One X. The bootloader is unlocked but is S-ON. I want to return this phone to as close as stock as possible. This phone is destined to go to another user who knows nothing of rooting and such so I don't care if it is rooted or not.
I understand I have to relock the bootloader to be able to flash an RUU right? Hboot is currently at 1.14.002, Radio is at 0.19as.32.09.11_2. TWRP 2.3.1.0 is installed.
The phone is currently running Cleanrom 6.5 and all works fine. I just want this back to as close to AT&T stock as possible so that the user I am giving the phone to will not have any problems.
If I relock the bootloader can I return this to stock via the most recent AT&T 3.18 RUU located here: http://forum.xda-developers.com/showthread.php?t=2191477 or is there something else I need to do first?
Thanks for all your help.
Click to expand...
Click to collapse
You'll need to S-OFF first or you'll brick.
There's a howto on the original android development section.

exad said:
You'll need to S-OFF first or you'll brick.
There's a howto on the original android development section.
Click to expand...
Click to collapse
Just flash a stock rooted Rom. Most users won't even know it's rooted. And having a custom recovery (even if they don't know they have it) can help if there is ever an issue. S-off so in the future if there's a update it won't brick the phone.
Sent from my HTC One X using xda premium

31ken31 said:
Just flash a stock rooted Rom. Most users won't even know it's rooted. And having a custom recovery (even if they don't know they have it) can help if there is ever an issue. S-off so in the future if there's a update it won't brick the phone.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I agree, except for leaving it rooted. I would leave just the bootloader unlocked and S-OFF and RUU, this way the buyer doesn't get shocked or confused if an app asks for root access, but has the option to do whatever they want to their phone if they so decide.

exad said:
I agree, except for leaving it rooted. I would leave just the bootloader unlocked and S-OFF and RUU, this way the buyer doesn't get shocked or confused if an app asks for root access, but has the option to do whatever they want to their phone if they so decide.
Click to expand...
Click to collapse
I forgot about su access prompt. That could be a shocker lol
Sent from my HTC One X using xda premium

exad said:
I would leave just the bootloader unlocked and S-OFF and RUU.
Click to expand...
Click to collapse
I agree. Couple reasons (both related to RUU). If the new user for some reason needs to recover the phone, and runs the RUU (not unheard of, HTC support will sometimes direct customers to do this), that person will either:
1) Brick the phone, if its left as SuperCID and S-on
2) If S-on (but CID is changed back), and bootloader is left unlocked, the RUU won't run. The person will have no idea why, and will likely be stuck.
S-off solves both of these potential issues. If you are at all worried about the next user. I would S-off, then run the RUU to return the phone to stock. The only thing that would be "not stock" is unlocked bootloader and S-off. But neither of these will mean anything or affect a less experienced user.

I'm going to disagree with the above.
If this person knows nothing of rooting and doesn't care, you should give them a stock phone. Being s-off is a potential security risk that should only be taken by someone who a) knows about it, and b) knows what it means. If you're selling this phone, it's arguably deceptive to give them something with a lurking vulnerability.

iElvis said:
I'm going to disagree with the above.
If this person knows nothing of rooting and doesn't care, you should give them a stock phone. Being s-off is a potential security risk that should only be taken by someone who a) knows about it, and b) knows what it means. If you're selling this phone, it's arguably deceptive to give them something with a lurking vulnerability.
Click to expand...
Click to collapse
Fair point. Switching the phone back to the AT&T CID and locking the bootloader might be the best alternative. Then run the RUU to get it back on stock recovery and ROM.
Giving/selling the phone to an unsuspecting noob with SuperCID and S-on just seems like a bad idea. Worse than S-off.

iElvis said:
I'm going to disagree with the above.
If this person knows nothing of rooting and doesn't care, you should give them a stock phone. Being s-off is a potential security risk that should only be taken by someone who a) knows about it, and b) knows what it means. If you're selling this phone, it's arguably deceptive to give them something with a lurking vulnerability.
Click to expand...
Click to collapse
I've seen bricks after RUUing, even after changing the CID back to default.. It's a toss up I guess. Typically, when I sell my phone or hacked device, I just sell it as being hacked this way people know what they are getting into. Advertising as such has never hindered my ability to sell it either.

redpoint73 said:
Fair point. Switching the phone back to the AT&T CID and locking the bootloader might be the best alternative. Then run the RUU to get it back on stock recovery and ROM.
Giving/selling the phone to an unsuspecting noob with SuperCID and S-on just seems like a bad idea. Worse than S-off.
Click to expand...
Click to collapse
I didn't mean leaving it supercid--that is obviously a risk.
exad said:
I've seen bricks after RUUing, even after changing the CID back to default.. It's a toss up I guess. Typically, when I sell my phone or hacked device, I just sell it as being hacked this way people know what they are getting into. Advertising as such has never hindered my ability to sell it either.
Click to expand...
Click to collapse
That's kind of my point. Selling it rooted is fine, just represent it for what it is. You shouldn't give a modified phone to someone who doesn't know what that even means.

The phone is going to a friend who has a Pantech Burst currently. As someone mentioned I didn't want them to get a SuperSU prompt for root access and have no idea what that means. I tried a stock rooted rom but it kept rebooting. I did factory reset/data wipe and reloaded the rom twice but still kept doing it. I thought it odd too. Cleamrom is acting just fine though.
After hard bricking a Droid DNA which I don't know if it was due to being unlocked and such I'm starting to feel rooting and custom roms isn't for me anymore. The Droid DNA was replaced and the replacement was never unlocked (and since it has most recent software it couldn't be unlocked. Don't get me wrong, I love not running stock devices. It's such a great feeling to get rid of all that carrier added bloat that I most liked.
I've actually moved on from the DNA as well. I'm on a One now from AT&T as my primary phone. And I so hate all that AT&T bloat in there. It's all disabled but still seeing it there just sends chills down my spine.
So now I am not so sure what to do about the One X now. My original thought was RUU back to factory and relock the bootloader and keep S-ON. That way if someone did look they'd only see "RELOCKED".
Makes me miss the easy days when I used a Captivate and Note 1. Those were so easy to use custom roms on.

iElvis said:
I didn't mean leaving it supercid--that is obviously a risk.
Click to expand...
Click to collapse
Your previous post didn't explicitly say anything about that, one way or another. So I was just clarifying for the benefit of the OP. I knew what you meant, but wanted to make sure the OP did, too!

[Q] Hard BRICK Help Please!!

Hi Im a complete Noob for doinf this :silly:
Coming from Htc One there was a method posted on the Htc one forums to get the bootloader locked.
http://forum.xda-developers.com/showthread.php?t=2475914
And stupid me without thinking I used the command echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
to reset the unlocked to lock stats.
Well now the phone doesnt even turn on no booloader no recovery nothing, pc detects it as an unkown device but I dont know what to do with it.
is there anyway possible to bring this brick back to life or do i have send it back to google?
Any suggestions or Advice is welcome.
Thanks

If it doesn't turn on I think you're hosed. You messed up one the partitions running the commands you did Please read the pinned (stickies) threads on the general forum before you do anything on your new device.

You wiped an important partition of the phone, and now it won't boot. Looks like you are out of luck. You can probably call Google and tell them your phone won't turn on, but technically that would be lying because you broke it without reading.
If you do get a replacement, and want to unlock the bootloader just get fastboot and type 'fastboot oem unlock'. That's it. This is a Nexus.

You kinda asked for it by attempting to follow a guide that is not for your device. HTC One =/= Nexus 5.
Like the above said, you wiped a partition essential to the function of your device. No way to fix it. Gonna have to send it back to Google, hopefully when you do they won't charge you and will just send you another. They might be used to having a million returns because when a device launchers there is a massive amount of nitpicking customers trying to get replacements and/or their are legit issues with the devices and they won't bother to check whats wrong with your phone. Most likely they will though, and who knows what you'll be charged. Good luck!

xXxG0dzRAgexXx said:
You kinda asked for it by attempting to follow a guide that is not for your device. HTC One =/= Nexus 5.
Like the above said, you wiped a partition essential to the function of your device. No way to fix it. Gonna have to send it back to Google, hopefully when you do they won't charge you and will just send you another. They might be used to having a million returns because when a device launchers there is a massive amount of nitpicking customers trying to get replacements and/or their are legit issues with the devices and they won't bother to check whats wrong with your phone. Most likely they will though, and who knows what you'll be charged. Good luck!
Click to expand...
Click to collapse
I hope I do get a replacement , Im in the Uk so i cant get in contact with Google support till Monday now. I was stupid for doing that and I have learned a valuable lesson.

That's what happens when you do not read. Good luck.

xXxG0dzRAgexXx said:
You kinda asked for it by attempting to follow a guide that is not for your device. HTC One =/= Nexus 5.
Like the above said, you wiped a partition essential to the function of your device. No way to fix it. Gonna have to send it back to Google, hopefully when you do they won't charge you and will just send you another. They might be used to having a million returns because when a device launchers there is a massive amount of nitpicking customers trying to get replacements and/or their are legit issues with the devices and they won't bother to check whats wrong with your phone. Most likely they will though, and who knows what you'll be charged. Good luck!
Click to expand...
Click to collapse
this just scares me about android. I am getting a nexus 5 soon, and love tweaking with my phones, so im pretty sure theres nothing to worry about, but still.... not trying to troll or anything, but on iPhone, its ridiculously hard to "hard brick". I've seen posts online, but most of the time its just users who end up thinking they've done a fix with no result, when in reality, ive had to fix plenty of iphones in the past, and some have come in horribly screwed up. always been able to fix them and restore though, even if it meant wiping a users data. With android, while I understand there are options to restore and such, it still seems rather easy to totally brick if you miss a step or something were to happen.
hoping I will never have this issue.... :-\

unvaluablespace said:
this just scares me about android. I am getting a nexus 5 soon, and love tweaking with my phones, so im pretty sure theres nothing to worry about, but still.... not trying to troll or anything, but on iPhone, its ridiculously hard to "hard brick". I've seen posts online, but most of the time its just users who end up thinking they've done a fix with no result, when in reality, ive had to fix plenty of iphones in the past, and some have come in horribly screwed up. always been able to fix them and restore though, even if it meant wiping a users data. With android, while I understand there are options to restore and such, it still seems rather easy to totally brick if you miss a step or something were to happen.
hoping I will never have this issue.... :-\
Click to expand...
Click to collapse
iPhone's are pretty much impossible to hard brick. Was in the jailbreak scene for 2 and a half years, and there is no way to hard brick one. Very early on it was possible, but not anymore. Android devices are pretty hard to brick usually. Just make sure you follow a guide for your device and all should be well. Only risky thing really is flashing the wrong firmware or radio on a device. Flashing roms, mods, or wiping the entire device is always fixable (not important partitions though, but that's only possible via command terminal like in this case). I was at first scared with my HTC One since it was my first android device, but realized as long as you know what your doing all should go well.

unvaluablespace said:
this just scares me about android. I am getting a nexus 5 soon, and love tweaking with my phones, so im pretty sure theres nothing to worry about, but still.... not trying to troll or anything, but on iPhone, its ridiculously hard to "hard brick". I've seen posts online, but most of the time its just users who end up thinking they've done a fix with no result, when in reality, ive had to fix plenty of iphones in the past, and some have come in horribly screwed up. always been able to fix them and restore though, even if it meant wiping a users data. With android, while I understand there are options to restore and such, it still seems rather easy to totally brick if you miss a step or something were to happen.
hoping I will never have this issue.... :-\
Click to expand...
Click to collapse
Don't be too scared. Honestly bricking a nexus device is quite hard as long you are somewhat literate. With most situations (if you have access to the bootloader) you have the option of flashing the factory images which will get your phone up and running 95% of the time. Basically if you can access the bootloader, there is nothing to panic or worry about.
The only reason this guy bricked his phone is because he thought it was a good idea to root his nexus 5 using a guide that teaches you how to unlock the bootloader on an HTC One.
Just make sure you read a bit, understand what you are doing, and don't blindly follow random instructions that you find on the interwebz. If you follow that advice i doubt you will have any problems.
Sent using xda-developers app

uronfire said:
Hi Im a complete Noob for doinf this :silly:
Coming from Htc One there was a method posted on the Htc one forums to get the bootloader locked.
http://forum.xda-developers.com/showthread.php?t=2475914
And stupid me without thinking I used the command echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
to reset the unlocked to lock stats.
Well now the phone doesnt even turn on no booloader no recovery nothing, pc detects it as an unkown device but I dont know what to do with it.
is there anyway possible to bring this brick back to life or do i have send it back to google?
Any suggestions or Advice is welcome.
Thanks
Click to expand...
Click to collapse
Still having issues? I've got a couple of ideas you could try. I managed to fix my nexus after I completely screwed up the bootloader, willing to share how I fixed it

daniel.kusy said:
Still having issues? I've got a couple of ideas you could try. I managed to fix my nexus after I completely screwed up the bootloader, willing to share how I fixed it
Click to expand...
Click to collapse
How did you manage to fix yours? Mine's still bricked but can only get access to the bootloader. Have tried every option of flashing factory but still no luck.

How do you brick a Nexus?
I wish I could feel pity but man....
Tell them it won't turn on. Send it back I'm sure they won't know. Hope they don't at least. Better than keeping a paperweight.
sent from my Nexus 5

jphilippon said:
How do you brick a Nexus?
I wish I could feel pity but man....
Tell them it won't turn on. Send it back I'm sure they won't know. Hope they don't at least. Better than keeping a paperweight.
sent from my Nexus 5
Click to expand...
Click to collapse
I used ChainFires auto root and it quite simply did not work and bricked my phone. Nothing else to it… it just bricked my N5. No interruptions, all correct drivers installed. Now I'm stuck with a phone displaying unlocked boot loader (which I can lock temporarily using fast boot command.) but when the device restarts into fast boot it's back saying unlocked. Nightmare really.

Meakii said:
I used ChainFires auto root and it quite simply did not work and bricked my phone. Nothing else to it… it just bricked my N5. No interruptions, all correct drivers installed. Now I'm stuck with a phone displaying unlocked boot loader (which I can lock temporarily using fast boot command.) but when the device restarts into fast boot it's back saying unlocked. Nightmare really.
Click to expand...
Click to collapse
there is a person in the franco's thread who even corrupted the bootloader he managed to recover using some lg flsh tool something like kdz
it was some kind of methord used to unbrick nexus 4

Meakii said:
How did you manage to fix yours? Mine's still bricked but can only get access to the bootloader. Have tried every option of flashing factory but still no luck.
Click to expand...
Click to collapse
have you tried the flash-all.bat (factory image using command prompt from the sdk/platform-tools folder )?
Sent from my Nexus 5 using Tapatalk

floxrin said:
have you tried the flash-all.bat (factory image using command prompt from the sdk/platform-tools folder )?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yea mate. No luck.

Meakii said:
Yea mate. No luck.
Click to expand...
Click to collapse
If you can get into bootloader does fastboot work? If you can get into the bootloader virtually anything can be fixed. What happens when you click the flash all.bat file?

Try LG download mode
Sent from my Nexus 5 using Tapatalk

daniel.kusy said:
If you can get into bootloader does fastboot work? If you can get into the bootloader virtually anything can be fixed. What happens when you click the flash all.bat file?
Click to expand...
Click to collapse
See the attached. I can't do anything. Every attempt to write anything to the internal SD fails. I wish it could be fixed but have tried everything. Worst part is even after fastboot oem lock cmd when it restarts it's unlocked again. Meaning when I return it warranty will probably be void.

This guy has the same problem. http://forum.xda-developers.com/showthread.php?p=315800
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

[Q] broken screen, absolutely broken.. s-off to s-on

My friend has give me his vzw m8 with a cracked and non working screen (lcd is too, broken, no display whatsoever) to stock up to return.
However, he needs to have s-on. I have just flashed the 0P6BIMG ruu via fastboot. I'm having difficulty understanding how to finish up the phone. From what I can tell from reading, it's still S-OFF after flashing this ruu. What else should i know for returning the phone?

http://forum.xda-developers.com/showthread.php?t=2745257
This may or may not help you lol hopefully it does though.
Sent from my HTC6525LVW using Tapatalk

mfungah said:
My friend has give me his vzw m8 with a cracked and non working screen (lcd is too, broken, no display whatsoever) to stock up to return.
However, he needs to have s-on. I have just flashed the 0P6BIMG ruu via fastboot. I'm having difficulty understanding how to finish up the phone. From what I can tell from reading, it's still S-OFF after flashing this ruu. What else should i know for returning the phone?
Click to expand...
Click to collapse
as suggested in the above post, in the thread it explains, that after you flash the RUU,
You must first RE lock the bootloader
this is done by this method:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recommend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now locked (if you can still see on the screen?)
Then you may do "fastboot oem writesecureflag 3" to put S-ON

andybones said:
as suggested in the above post, in the thread it explains, that after you flash the RUU,
You must first RE lock the bootloader
this is done by this method:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recommend you copy/paste this)
Click to expand...
Click to collapse
So at the moment I need to figure out how to obtain su, at least shell then. Seeing as I just flashed the ruu and the LCD is completely black/blank, do you have any suggestions?
And thank you very much for the detailed reply step by step.

Also, it's probably helpful to mention that I am still in fastboot mode from flashing the RUU.

mfungah said:
Also, it's probably helpful to mention that I am still in fastboot mode from flashing the RUU.
Click to expand...
Click to collapse
if the RUU took as successful then you should reboot it to the new RUU ROM (should take about 5 mins, since you can't see.. plug cable into computer and once you can access SD-Card you are booted, you should be able to then get an su in a cmd prompt. from what I've read the RUU has supersu icon so it should have root? not positive but doing this will absolutely not hurt, you would only not be able to get SU privs to turn the flag back to S-ON. if you get su, great you should then be good to go.
I don't know but you may even be able to do fastboot devices then echo, BUT do NOT try that yet anyway as I don't know what will happen, if you do it, it's at own risk.. since going back for refurb, i don't really think a brick would matter though.

andybones said:
if the RUU took as successful then you should reboot it to the new RUU ROM (should take about 5 mins, since you can't see.. plug cable into computer and once you can access SD-Card you are booted, you should be able to then get an su in a cmd prompt. from what I've read the RUU has supersu icon so it should have root? not positive but doing this will absolutely not hurt, you would only not be able to get SU privs to turn the flag back to S-ON. if you get su, great you should then be good to go.
I don't know but you may even be able to do fastboot devices then echo, BUT do NOT try that yet anyway as I don't know what will happen, if you do it, it's at own risk.. since going back for refurb, i don't really think a brick would matter though.
Click to expand...
Click to collapse
That's correct andy....The ruu I made does have su. I'm not sure how he would be able to answer the su prompts for adb access though. Maybe hdmi out?
For what it's worth this device is pretty hard to truly brick. I tried once to help brick one and even with bootloader wiped it still went straight to ruu mode.
Sent from my SM-T320 using Tapatalk

I suppose that adb debugging isn't enabled by default, I'm booted up but that's about it. Any specific information that could be helpful or as I'm assuming, theres nothing much i can do except fastboot to S-ON. I mean it is getting sent in, I just really hope it gets accepted.

He got a new device for him all sorted out. I really appreciate your time and help, I did find your step by step very easy to understand.

[Q] Recently Locked Bootloader, S-ON & Unrooted TAMPERED FLAG

So, I needed to return my phone back to stock recently (yes, HTC ONE M8 VERIZON).
Followed the directions posted here and all went perfect. Did have to purchase the "Universal Unroot" app to get SuperSU to uninstall.
About 20 minutes later, I get a notification stating there was an update from Verizon for OTA. I follow the onscreen prompts (figured, what does it matter, phone is stock again) after the install, I get a prompt stating the phone has been tampered (or something to that affect), so I load the bootloader and I see the *** TAMPERED *** flag on the top.
Is there anyway to get that removed now that I am no longer rooted, on S-OFF and my bootloader is locked again... Before turning the phone back in to Verizon?

Did you take a nandroid backup after rooting? If so just flash that. As for the ota, they are more trouble than they are worth most of the time. You can just grab the radio and firmware from it, posted in the development area, then flash nusense6 custom Rom to get 4.4.3. It's mostly stock.

deefster said:
Did you take a nandroid backup after rooting? If so just flash that. As for the ota, they are more trouble than they are worth most of the time. You can just grab the radio and firmware from it, posted in the development area, then flash nusense6 custom Rom to get 4.4.3. It's mostly stock.
Click to expand...
Click to collapse
I can't remember honestly.
I have 2 folders in my TWRP backup folder on ext_sd.
The problem right now is I am no longer rooted so, I am a bit stuck...
Correct me if I'm wrong but, I don't think there is a root method for Verizon 4.4.3... Is there?

TH3 ST1G said:
I can't remember honestly.
I have 2 folders in my TWRP backup folder on ext_sd.
The problem right now is I am no longer rooted so, I am a bit stuck...
Correct me if I'm wrong but, I don't think there is a root method for Verizon 4.4.3... Is there?
Click to expand...
Click to collapse
Check out this thread. It should help you. You are still on 4.4.2 cause the update stopped.
http://forum.xda-developers.com/showthread.php?t=2708565

jsaxon2 said:
Check out this thread. It should help you. You are still on 4.4.2 cause the update stopped.
http://forum.xda-developers.com/showthread.php?t=2708565
Click to expand...
Click to collapse
The update did go through though... I'm on 4.4.3 stock S-ON, no root and locked bootloader... And now SuperSU is reinstalled.

TH3 ST1G said:
The update did go through though... I'm on 4.4.3 stock S-ON, no root and locked bootloader... And now SuperSU is reinstalled.
Click to expand...
Click to collapse
I believe the only option for you now would be to use Sunshine to achieve s-off again and then reset your flag. That will cost $25 unless someone has anything else I haven't been able to find.

jsaxon2 said:
I believe the only option for you now would be to use Sunshine to achieve s-off again and then reset your flag. That will cost $25 unless someone has anything else I haven't been able to find.
Click to expand...
Click to collapse
I downloaded the sunshine apk. It installed but tells me it needs root access to run...

TH3 ST1G said:
I downloaded the sunshine apk. It installed but tells me it needs root access to run...
Click to expand...
Click to collapse
Where did you download from? The new version is supposed to temp root by itself.
Check out their website: http://theroot.ninja/

jsaxon2 said:
Where did you download from? The new version is supposed to temp root by itself.
Check out their website: http://theroot.ninja/
Click to expand...
Click to collapse
First off, thank you for responding so often trying to help me out with this...
That is the link I downloaded the APK from, it was named "Sunshine_latest.apk" or something to that affect...

I actually just noticed that I still have a few older TWRP backups stored on my ext_sd, saved under /TWRP/BACKUPS/**DEVICESERNO**...
Can I flash an older backup although I am on the below?
Stock Recovery
S-ON
Locked Bootloader
No root?

TH3 ST1G said:
First off, thank you for responding so often trying to help me out with this...
That is the link I downloaded the APK from, it was named "Sunshine_latest.apk" or something to that affect...
Click to expand...
Click to collapse
I'm sorry, but I have never used sunshine so I don't really know what to tell you from here. I used firewater back in April when the phone first came out.
Best thing I could tell you is to check out their irc chat http://webchat.freenode.net/?channels=sunshine-support to see if someone in there can help you out. @jcase and @beaups are the ones that created the program and they are usually in there to help.

jsaxon2 said:
I'm sorry, but I have never used sunshine so I don't really know what to tell you from here. I used firewater back in April when the phone first came out.
Best thing I could tell you is to check out their irc chat http://webchat.freenode.net/?channels=sunshine-support to see if someone in there can help you out. @jcase and @beaups are the ones that created the program and they are usually in there to help.
Click to expand...
Click to collapse
thanks for the tip, there may be a light at the end of the tunnel, tomorrow I may be all good.

I can tell you 100% for sure that Sunshine does work with stock Verizon 4.4.3. They updated their thread with that information. You'll probably have to pay the 25$ (if you haven't already paid it before) but it is seriously the easiest S-OFF exploit there is. You just install the apk, open it, you get a prompt for payment either paypal or credit card, then it runs compatibility tests and then S-OFFs. You literally have to do nothing but install the apk. You don't even need root to use it. It does it all itself. After you run Sunshine, fastboot flash the latest TWRP, then flash SuperSU zip for root. (you can get that here: http://download.chainfire.eu/420/SuperSU/UPDATE-SuperSU-v1.99.zip ) and your are good to go. Resetting the tampered flag may be difficult though. I'm sure someone has done it somewhere though.

nicholi2789 said:
I can tell you 100% for sure that Sunshine does work with stock Verizon 4.4.3. They updated their thread with that information. You'll probably have to pay the 25$ (if you haven't already paid it before) but it is seriously the easiest S-OFF exploit there is. You just install the apk, open it, you get a prompt for payment either paypal or credit card, then it runs compatibility tests and then S-OFFs. You literally have to do nothing but install the apk. You don't even need root to use it. It does it all itself. After you run Sunshine, fastboot flash the latest TWRP, then flash SuperSU zip for root. (you can get that here: http://download.chainfire.eu/420/SuperSU/UPDATE-SuperSU-v1.99.zip ) and your are good to go. Resetting the tampered flag may be difficult though. I'm sure someone has done it somewhere though.
Click to expand...
Click to collapse
I tried running sunshine on my phone... It wouldn't run because for whatever reason, it couldn't gain root access to the phone.

TH3 ST1G said:
I tried running sunshine on my phone... It wouldn't run because for whatever reason, it couldn't gain root access to the phone.
Click to expand...
Click to collapse
Then go grab Weak sauce ask out of the original development forum, install it, open it, then run sunshine again. That's what I had to do when I used it. It was before they built root into it.

nicholi2789 said:
Then go grab Weak sauce ask out of the original development forum, install it, open it, then run sunshine again. That's what I had to do when I used it. It was before they built root into it.
Click to expand...
Click to collapse
I thought weaksauce didn't work on 4.4.3?

TH3 ST1G said:
I thought weaksauce didn't work on 4.4.3?
Click to expand...
Click to collapse
Your prolly right. I would still try it tho. If you paid for Sunshine I would definitely contact Jcase on IRC.

alright, so jcase just worked his magic on my phone...
he typed some stuff, it worked, i'm happy...
i am now back to stock ROM, S-OFF, Unlocked bootloader, stock recovery & rooted
i followed the instructions here once jcase got me all sorted out with the above...
what i see becoming an issue is, I am on verizon software version 2.21.605.2...
all I want to do is get my phone to a state where I can return it to verizon from here...
I have read the 2 major write ups I have found on returning a phone to stock but, they are all for previous versions of verizon software...
anyone have any ideas/links to give a brother a hand?

TH3 ST1G said:
alright, so jcase just worked his magic on my phone...
he typed some stuff, it worked, i'm happy...
i am now back to stock ROM, S-OFF, Unlocked bootloader, stock recovery & rooted
i followed the instructions here once jcase got me all sorted out with the above...
what i see becoming an issue is, I am on verizon software version 2.21.605.2...
all I want to do is get my phone to a state where I can return it to verizon from here...
I have read the 2 major write ups I have found on returning a phone to stock but, they are all for previous versions of verizon software...
anyone have any ideas/links to give a brother a hand?
Click to expand...
Click to collapse
Well they will work. You could use the RUU and return to 1.55.605.2. Doesn't matter what version you are on now, it will work. It will put you at almost 100% stock. Just re-lock the bootloader with a command and you can send it back.

[Q] Can't take off supersu and re-lock.

Yup, I know total newb question. I decided to unroot my phone a while back because honestly I knew I wasn't going to have time to mess around with the phone like I have in the past. I unrooted it and thought I did everthing right. Root checker says it's not rooted. However my phone has since messed up and broken and HTC is going to help me out under warranty and send me a refurbished one.
The phone is urooted but says it's unlocked and Supersu will not uninstall. When I turn it on using Power and volume down it says it's MODIFIED. I've since deleted everthing that helped me root the phone through the mack, all the files, etc.
Any help on how to get this back to normal? I've heard in a few places that they don't particularly care but I didn't want them to charge me once they receive the item.
Thanks for the help.

Ciresamor said:
Yup, I know total newb question. I decided to unroot my phone a while back because honestly I knew I wasn't going to have time to mess around with the phone like I have in the past. I unrooted it and thought I did everthing right. Root checker says it's not rooted. However my phone has since messed up and broken and HTC is going to help me out under warranty and send me a refurbished one.
The phone is urooted but says it's unlocked and Supersu will not uninstall. When I turn it on using Power and volume down it says it's MODIFIED. I've since deleted everthing that helped me root the phone through the mack, all the files, etc.
Any help on how to get this back to normal? I've heard in a few places that they don't particularly care but I didn't want them to charge me once they receive the item.
Thanks for the help.
Click to expand...
Click to collapse
Are you s-on?

I am, I remember I used this video but it did not lock and the supersu never uninstalled.
I'm trying to use these steps but it doesn't work, even though it finds my device:
http://www.andromods.com/unroot-locking/reset-unlocked-to-locked-htc-one-m8-bootloader-status.html

Ciresamor said:
I am, I remember I used this video but it did not lock and the supersu never uninstalled.
I'm trying to use these steps but it doesn't work, even though it finds my device:
http://www.andromods.com/unroot-locking/reset-unlocked-to-locked-htc-one-m8-bootloader-status.html
Click to expand...
Click to collapse
The best you can do then for now is to fastboot oem lock
And then run an s-on ruu that is the same or higher than what you have.

Will I be able to take off the supersu app at some point during this process? It will not uninstall

Ciresamor said:
Will I be able to take off the supersu app at some point during this process? It will not uninstall
Click to expand...
Click to collapse
The s-on ruu will wipe that puppy out lol

Okay thanks, I'm looking for an s-on ruu for the mac right now...

Ciresamor said:
Okay thanks, I'm looking for an s-on ruu for the mac right now...
Click to expand...
Click to collapse
Just do the zip method. I have them all posted in one thread.

Here:
http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
Nice, thanks! I'm running the fast boot oem right now, I'll let you know how it goes.

Hmm, I put the zip file and it says it can't open it...

Success, I wish it didn't say relocked but it no longer says modified, it states official on the banner.

Ciresamor said:
Success, I wish it didn't say relocked but it no longer says modified, it states official on the banner.
Click to expand...
Click to collapse
If the ruu wasn't lollipop and you paid for sunshine in the past you could do sunshine again and fix it

It was on lollipop and I didn't have the sunshine app.

is there any other way to fix that? What's the general consensus, will HTC void the warranty?

Ciresamor said:
is there any other way to fix that? What's the general consensus, will HTC void the warranty?
Click to expand...
Click to collapse
Locked is locked. Whether relocked or locked. You cannot fix that without being s-off. If you are still on kitkat you could pay $25 via sunshine to s-off and fix it to say locked and then turn s back on.

Well I'm going to send the phone out and see what happens. Thanks for your help in this thread.