Unroot M8? Sending back to Verizon... - Verizon HTC One (M8)

Hey guys, I edged up and now need to send my M8 back to VZW. Just wondering do I need to unroot it and re-lock the bootloader before sending back? If so, is there a process to make it quick and easy or is it a pain? Can anyone guide me in the right direction? Thanks!

pettigrew95 said:
Hey guys, I edged up and now need to send my M8 back to VZW. Just wondering do I need to unroot it and re-lock the bootloader before sending back? If so, is there a process to make it quick and easy or is it a pain? Can anyone guide me in the right direction? Thanks!
Click to expand...
Click to collapse
You should read through this entire thread:
http://forum.xda-developers.com/showthread.php?t=2745257
Especially the posts by dottat on the last page where he talks about what to do BEFORE turning s-on. Since you're currently s-off (I assume) and can downgrade, I might recommend returning to stock 4.4.4 since dottat has a full stock s-on ruu. Don't be confused, I think that thread instructs you to flash that ruu BEFORE turning s-on but I haven't been through it in a while. Again, be sure to read the entire thread as I recall the op learned a lesson or two which his first post might not clearly explain.
Whatever you do, ask before doing anything you're not %100 sure is right.

Would you even need to unroot if you're just sending back to Verizon from EDGE'ing up? I am not sending back to HTC for an RMA.

pettigrew95 said:
Would you even need to unroot if you're just sending back to Verizon from EDGE'ing up? I am not sending back to HTC for an RMA.
Click to expand...
Click to collapse
At what point after sending it back would you feel free from the possibility of a charge. It takes literally 10-15 minutes to revert and remove any/all doubt.
leave twrp installed... download the latest s-on RUU and shoot me teamviewer ID and passcode and I will take care of it for you if you want....

Related

[Q] Need to unroot and s-on

Need to do a warranty exchange for my phone - it's rooted and s-off'ed. Can anyone point me to a thread that I missed in my search that would direct me how to do this? Thanks!
Also, is it possible to do a nandroid backup from one phone and restore it to the new one?
1) S-off is permanent, but you should have no problem returning the phone. Just look for the unrooting guide in development.
2) No, you can't restore from another phone's Nandroid. Just use Titanium to restore your apps.
forum.xda-developers.com/showpost.php?p=17424340&postcount=24
Sent from Spaceball One.
eclipsed450 said:
Need to do a warranty exchange for my phone - it's rooted and s-off'ed. Can anyone point me to a thread that I missed in my search that would direct me how to do this? Thanks!
Click to expand...
Click to collapse
It's not hard. Here is a thread that gives a step-by-step:
How to: S-ON from S-OFF
Basically, you take your phone, relock the bootloader, flash the stock image that matches your bootloader, and you are back to factory state. S-ON, unrooted.
---------- Post added at 06:11 PM ---------- Previous post was at 06:06 PM ----------
blackknightavalon said:
1) S-off is permanent, but you should have no problem returning the phone. Just look for the unrooting guide in development.
2) No, you can't restore from another phone's Nandroid. Just use Titanium to restore your apps.
Click to expand...
Click to collapse
I am not sure either statement is correct. The guide by Blue6IX above shows how to go from S-OFF to S-ON. I have done it with two warranty replacement phones. The first I got S-OFF via Revolutionary and the second I got S-OFF via Juounotbear. I was able to S-ON both of them by flashing the correct PG59IMG in the bootloader.
On both of my replacement phones, I simply used the nandroid backup from the original phone. Since I was going back to the same bootloader and kernel, it worked fine.
Yep, I've restored my original nandroid from my first doubleshot to all of the ones I've had.
The big issue there is making sure the clockworkmod version you use matches the nandroid you are restoring from.
A cwm 4.0.0.9 nandroid won't work on the cwm 5.0.2.7 and so on. But a cwm 4.0.0.9 backup will work for any doubleshot with that version cwm on it.
S-ON was a leap of faith and prayer to figure out, considering we didn't (and still don't) have an RUU, but we win and it works anyway. Just follow the instructions and don't skip any steps, you'll be fine.
Sent from a digital distance.
thanks everyone! replacement phone should be here today, will let you know how things go :-D
cparekh said:
It's not hard. Here is a thread that gives a step-by-step:
How to: S-ON from S-OFF
Basically, you take your phone, relock the bootloader, flash the stock image that matches your bootloader, and you are back to factory state. S-ON, unrooted.
Click to expand...
Click to collapse
This worked like a charm. Phone is on it's way back to t-mo. Thanks!!!
eclipsed450 said:
This worked like a charm. Phone is on it's way back to t-mo. Thanks!!!
Click to expand...
Click to collapse
Glad it worked for you. I did the same thing for my warranty replacement number one (vibrate stopped working) and number two (camera never worked on the replacement phone, even when straight out of the box).
My understanding is that since the warranty is direct to and from HTC, no one really cares if the phone is rooted or s-off, but why risk it? Plus, I find it very fun and interesting to perform hacks on the phone.
ehh
Had to return do a warranty exchange not long, my new device came and i shipped my defective device rooted with an ICS rom and s off. I only payed 5 bucks for the shipping. they never said anything about how jacked my phone was. So i would worry much about having s off
h3ktyk said:
Had to return do a warranty exchange not long, my new device came and i shipped my defective device rooted with an ICS rom and s off. I only payed 5 bucks for the shipping. they never said anything about how jacked my phone was. So i would worry much about having s off
Click to expand...
Click to collapse
I sent in about 5 G2s the same way in less than a month lol.

[Q] Returning One S to T-Mobile for service. What is best way to return to stock?

I know there are already a few threads like this around but needed a little more concise answer... so apologies!
I'm returning my phone for issues with the power button being unresponsive and wanted to relock the bootloader and return it to stock software and recovery. I'm good on everything except the recovery. After the latest ota update I can't get any RUU file to work that would relock everything since the 2.35 RUU isn't out yet I guess. What is my best solution for getting this back to day 1 so I can return the phone? Do I need to just manually flash the recovery? Will that get rid of 'tampered' on the bootloader?
Thanks everyone!
fbihawk said:
I know there are already a few threads like this around but needed a little more concise answer... so apologies!
I'm returning my phone for issues with the power button being unresponsive and wanted to relock the bootloader and return it to stock software and recovery. I'm good on everything except the recovery. After the latest ota update I can't get any RUU file to work that would relock everything since the 2.35 RUU isn't out yet I guess. What is my best solution for getting this back to day 1 so I can return the phone? Do I need to just manually flash the recovery? Will that get rid of 'tampered' on the bootloader?
Thanks everyone!
Click to expand...
Click to collapse
Now also having issues with HTC Development text showing up every time you start the phone. Kind of a dead giveaway. Anybody have thoughts?

[Q] can anybody help a noob?

I have a HTC Sensation and running CM10, I urgently need help unrooting my phone and going back to stock so I can send it off for repair.
I am unsure how to do the necessary to revert back and what I need in order for the manufacturer to fix a hardware problem that I have.
Any help would be great. I am having difficulty finding information that I (a noob) can understand,
Thanks in advance!
go here
S.K.O.W said:
I have a HTC Sensation and running CM10, I urgently need help unrooting my phone and going back to stock so I can send it off for repair.
I am unsure how to do the necessary to revert back and what I need in order for the manufacturer to fix a hardware problem that I have.
Any help would be great. I am having difficulty finding information that I (a noob) can understand,
Thanks in advance!
Click to expand...
Click to collapse
HI,
if you want to send it back to htc service center all you can do is to flash a ruu for more details go here
http://forum.xda-developers.com/showthread.php?t=1672425
Are you soff or son
shrex said:
HI,
if you want to send it back to htc service center all you can do is to flash a ruu for more details go here
http://forum.xda-developers.com/showthread.php?t=1672425
Are you soff or son
Click to expand...
Click to collapse
Yes I finally got it back to stock and S-On! was having trouble when flashing the RUU, I kept getting an 155error, all I had to do was manually put my phone in Bootloader and it would continue on there, (I was ment to do that automatically), I am all ready to send off for repair :good:
S.K.O.W said:
Yes I finally got it back to stock and S-On! was having trouble when flashing the RUU, I kept getting an 155error, all I had to do was manually put my phone in Bootloader and it would continue on there, (I was ment to do that automatically), I am all ready to send off for repair :good:
Click to expand...
Click to collapse
Now if you made a nandroid backup before you flashed the RUU, when you get it back from teh rpair shop you can just s-off again and reflash your back up and it'll be just like you left it, only less broken.

[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] 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.

Categories

Resources