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.
Related
Hello,
Wondering if anyone has got an Australian Vodafone stock rom (RUU) for my Sensation in case something goes wrong, and I need to un-root, un-flash etc.
I didn't backup my rom, when i initially flashed a custom rom -.-
Thanks in advance!
AND yes, I have used the search function and Googled.
Me too! Keen to root and explore the goodies available but would like the stock rom just in case....
Any suggestions for an alternative rom which I might subsitutue (perhaps UK Vodafone?) would be appreciated. BTW my phone: Build 1.45.862.3 CL157335 Radio 10.56.9035.00U_10.14.9035.01
OMG EPIC SAUCE! Please could you make a backup of your current ROM! Your my only hope of getting a stock rom, you'll need to follow the guide in this link until it tells you to make a backup of your current ROM using CWM (ClockWorkMod)
http://forum.xda-developers.com/showthread.php?t=1192300
This is your mission, if you choose to accept it. Backing up is crucial, you might end up in the same boat as me!
If you have ANY questions ask me or Google it, do not continue unless you know exactly what your doing.
It may seem a bit daunting but just follow the steps, word for word, and you'll get there easily. Thank you!
Don't let me down
Sent from my TripNiCE Pyramid using xda premium
Jikstah said:
OMG EPIC SAUCE! Please could you make a backup of your current ROM! Your my only hope of getting a stock rom
Click to expand...
Click to collapse
Jitkstah, the ease of backing up my current rom is not my concern, its being able to put things back the way they are if I have a warranty issue. Backing up my current rom after s-off and installing a custom recovery looks like a walk in the park compared to the process I went through rooting my last phone - a Legend...
AFAIK I'm not able to get back to s-on without the stock RUU for Vodafone Australia (or a rom which is similar). So I'll keep looking and asking for a bit longer... I may just bite the bullet and root, in which case I'll be happy to share my backed up stock rom but I don't think this will help you if you are trying to get back to s-on.
Cheers
EpicSauce said:
Jitkstah, the ease of backing up my current rom is not my concern, its being able to put things back the way they are if I have a warranty issue. Backing up my current rom after s-off and installing a custom recovery looks like a walk in the park compared to the process I went through rooting my last phone - a Legend...
AFAIK I'm not able to get back to s-on without the stock RUU for Vodafone Australia (or a rom which is similar). So I'll keep looking and asking for a bit longer... I may just bite the bullet and root, in which case I'll be happy to share my backed up stock rom but I don't think this will help you if you are trying to get back to s-on.
Cheers
Click to expand...
Click to collapse
Hmm, I didn't realize we needed the actual RUU to get back to S-ON. Thanks for pointing that out! Although I have been approached by one person, who shall not be named, who has offered me an official Vodafone RUU in exchange for the IMEI number the phone shipped with and a price of 11 Euros, I had to turn it down as I am not able to pay through PayPal. Perhaps you are able to do this? And hopefully be generous one day, to maybe, hand it on to me?
IF you are interested contact me via PM and i'll get you in contact with the "dealer".
You don't need the RUU at all. Once you've restored your backup you just run the command for S-ON via fastboot.
The reason an RUU is helpful is it flashes the complete ROM to the phone so the bootloader and recovery are also replaced with stock versions. Without an RUU you have to do it all manually and then S-ON again
Beautiful, thanks Eddy! So I just have to find the stock boot loader and recovery. Any ideas where? And EpicSauce are you able to backup your ROM or do you still want to continue finding an RUU, which is impossible
Sent from my TripNiCE Pyramid using xda premium
EddyOS said:
The reason an RUU is helpful is it flashes the complete ROM to the phone so the bootloader and recovery are also replaced with stock versions. Without an RUU you have to do it all manually and then S-ON again
Click to expand...
Click to collapse
Thanks EddyOS, I didn't realise you could S-ON after restoring a nandroid backup... but that makes sense. As you say, after restoring the stock ROM you would be left with a different bootloader and custom recovery. How difficult (and risky) is it to restore the stock bootloader and recovery manually?
If I needed to return the phone for warranty I would want to remove all evidence the phone had been rooted. Jikstah - if I go this route I'm happy to share my backed up ROM.
EpicSauce said:
Thanks EddyOS, I didn't realise you could S-ON after restoring a nandroid backup... but that makes sense. As you say, after restoring the stock ROM you would be left with a different bootloader and custom recovery. How difficult (and risky) is it to restore the stock bootloader and recovery manually?
If I needed to return the phone for warranty I would want to remove all evidence the phone had been rooted. Jikstah - if I go this route I'm happy to share my backed up ROM.
Click to expand...
Click to collapse
Okay then, keep in contact for the meanwhile!
Thanks man
EddyOS said:
You don't need the RUU at all. Once you've restored your backup you just run the command for S-ON via fastboot.
The reason an RUU is helpful is it flashes the complete ROM to the phone so the bootloader and recovery are also replaced with stock versions. Without an RUU you have to do it all manually and then S-ON again
Click to expand...
Click to collapse
But will the Vodafone Australia know that it has been rooted that way?
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!
First off I have to say this is my first post here. I am a long time user of these forums and I cannot praise them for all the great stuff here. I have used them for my Galaxy Nexus and now my Nexus 4. However, my wife's One S is having some problems.
With the OTA of JB it started to act funny, losing and disabling WiFi. So naturally I decided to root the phone and try some other ROMs and see how that worked out. I did take a nan droid backup at almost every step, except just before I rooted it. I attempted to send it back for repair and they denied it saying the phone was tampered, naturally.
I would like to try running it on stock rom, but I do not have the ruu and do not have a nandroid backup before I rooted it. My rooted nandroid back is throwing errors on start up and generally acting not very nice.
Anyone having a bell stock nandroid willing to share with me would be appreciated. I wish I never did the ota of jb... Hind sight is always 20-20 I guess.
Any help would be appreciated.
RTNetwork
RTNetwork said:
First off I have to say this is my first post here. I am a long time user of these forums and I cannot praise them for all the great stuff here. I have used them for my Galaxy Nexus and now my Nexus 4. However, my wife's One S is having some problems.
With the OTA of JB it started to act funny, losing and disabling WiFi. So naturally I decided to root the phone and try some other ROMs and see how that worked out. I did take a nan droid backup at almost every step, except just before I rooted it. I attempted to send it back for repair and they denied it saying the phone was tampered, naturally.
I would like to try running it on stock rom, but I do not have the ruu and do not have a nandroid backup before I rooted it. My rooted nandroid back is throwing errors on start up and generally acting not very nice.
Anyone having a bell stock nandroid willing to share with me would be appreciated. I wish I never did the ota of jb... Hind sight is always 20-20 I guess.
Any help would be appreciated.
RTNetwork
Click to expand...
Click to collapse
Tell you what, I have the same problem and even the same carrier phone, BELL HTC One S.
The missing RUU for JB is such a pain. Though I didn't face any problems with WiFi or data connection.
I have rooted my phone and don't have a pre-root nandroid backup.
But here is what you can do to bring it back top stock ICS/JB.
1. S-OFF using moonshine method. (It supports BELL firmware 3.16.666.9 JB)
2. Run an ICS RUU which is present there for BELL.
Afterwards, you can decide whether you want to stay on ICS or update to JB via OTA on phone. Then you can make a nandroid backup too and S-ON back again.
Good luck.
Sent from my Nexus 7 using Tapatalk HD
khan.orak said:
Tell you what, I have the same problem and even the same carrier phone, BELL HTC One S.
The missing RUU for JB is such a pain. Though I didn't face any problems with WiFi or data connection.
I have rooted my phone and don't have a pre-root nandroid backup.
But here is what you can do to bring it back top stock ICS/JB.
1. S-OFF using moonshine method. (It supports BELL firmware 3.16.666.9 JB)
2. Run an ICS RUU which is present there for BELL.
Afterwards, you can decide whether you want to stay on ICS or update to JB via OTA on phone. Then you can make a nandroid backup too and S-ON back again.
Good luck.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I was not aware we had a method to s-off once we moved to jb. I'll look into that. Thank you!
Is it worthwhile to super cid, then?
RTNetwork said:
I was not aware we had a method to s-off once we moved to jb. I'll look into that. Thank you!
Is it worthwhile to super cid, then?
Click to expand...
Click to collapse
No no, we don't need to superCID at all. And i would definitely advise against it for any reason add many people have reported bricks with SuperCID. Moonshine method is good, try that.
Though it has been reported successful with Ubuntu and other Linux distro's more often than with windows. HTC Sync Manager poses problem.
Study the thread, you'll get ample info.
Good luck
Sent from my Nexus 7 using Tapatalk HD
---------- Post added at 04:51 AM ---------- Previous post was at 04:30 AM ----------
RTNetwork said:
I was not aware we had a method to s-off once we moved to jb. I'll look into that. Thank you!
Is it worthwhile to super cid, then?
Click to expand...
Click to collapse
You might also want to study this http://forum.xda-developers.com/showthread.php?t=2164783 thread.
Couple of guys recently reported they had success flashing the OTA.zip which is available for BELL JB. The guide is for the S3 variant but the principle is same since you are on stock JellyBean.
Though if you want to revert to ICS you have to follow the method I advised in my previous post.
Sent from my Nexus 7 using Tapatalk HD
I had problems (even before rooting) where my wifi would simply not work. If I go into settings and try to switch it from On to Off, it would simply say there was an "Error". Earlier in 2013, I had rooted and installed a Cyanogenmod Rom on my phone (I forget which one exactly, but it was JB). After a while, I went back to stock. A week or so later, the problem happened again. I did a factory reset. It fixed the problem for a day. Then it happened again and not even a factory reset would fix it.
I got a Nexus 5 for Christmas, so I'm looking to sell this phone but want to fix the wifi before I do so. I've seen a couple of people with a similar problem but no fixes. Does anyone know what is the cause of this problem and how to fix it?
Thanks.
Um, how did you return to stock? Ruu or a backup?
Sent from my One Xl using xda premium
If it was happening while your phone was completely stock I don't think there's anything you can do that's going to be worth it. It'll likely have to go to a repair centre and the cost would be more than you can sell the phone for. You could list the phone on Swappa, there may be people who require only the display, motherboard etc.
You could try running an RUU as a last attempt saving though.
Sent from my Evita
magnetboard said:
Um, how did you return to stock? Ruu or a backup?
Click to expand...
Click to collapse
A nandroid is only going to put you back on the stock ROM, not stock recovery, etc. You may also have s-off, unlocked bootloader, SuperCID, etc. that would make the phone "not stock", but you have given zero details for us to answer your question.
Going back to stock should only be necessary for selling the device or returning for warranty (not necessary for AT&T).
Well, a nandroid, as stated by Tim, only gibes you the stock ROM. An ruu wipes anything that might have messed with anything.
Sent from my One Xl using xda premium
I used an RUU to go back to stock.
The details for my phone are:
S-Off
CID-11111111
HBoot-2.14.0000
If there is any other information that would be helpful, let me know and I can try to provide it. I'm planning on selling it on Swappa...my hope was to fix the wifi before doing so.
If you've done an RUU and still no WiFi then you've run out of options.
Sent from my Evita
Thanks. That's what I was expecting...just wanted to make sure.
Is there a way to do this? I've gone through forums, and haven't seen anything concrete.
ericerk said:
Is there a way to do this? I've gone through forums, and haven't seen anything concrete.
Click to expand...
Click to collapse
If you're S-OFF (if not you can gain it by using Sunshine you can do an RUU, that will take you back to about as stock as you can get e.g stock firmware, stock ROM, stock recovery stock etc.
This thread will tell you most of the things you'd need to do.
I highly advise against attempting to go S-ON or re-locking your bootloader as S-ON has a high probability of failure and or bricking your device.
My personal recommendation would be to just take the RUU and if if I remember correctly you can make your ***UNLOCKED*** tag falsely show ***LOCKED*** instead, not sure though so if that interests you just Google it or ask.
EDIT: Here is the link to the tutorial on setting your UNLOCKED tag to LOCKED. Warning though I have not tested this or heard of anyone testing it so DO THIS AT YOUR OWN RISK.
S1L3nTShaDoWz said:
If you're S-OFF you can do an RUU, that will take you back to about as stock as you can get e.g stock firmware, stock ROM, stock recovery stock etc.
This thread will tell you most of the things you'd need to do.
I highly advise against attempting to go S-ON or re-locking your bootloader as S-ON has a high probability of failure and or bricking your device.
My personal recommendation would be to just take the RUU and if if I remember correctly you can make your ***UNLOCKED*** tag falsely show ***LOCKED*** instead, not sure though so if that interests you just Google it or ask.
EDIT: Here is the link to the tutorial on setting your UNLOCKED tag to LOCKED. Warning though I have not tested this or heard of anyone testing it so DO THIS AT YOUR OWN RISK.
Click to expand...
Click to collapse
I need to to return this device to Verizon.
ericerk said:
I need to to return this device to Verizon.
Click to expand...
Click to collapse
As far as I know they do not care if your phone is S-OFF or unlocked, only that it is running the stock firmware, ROM & recovery. Reason behind this is some of their phones are manufactured and shipped already S-OFF on 'accident', so as long as you do the RUU you should be perfectly fine, at least that is what everyone has said thus far.
S1L3nTShaDoWz said:
As far as I know they do not care if your phone is S-OFF or unlocked, only that it is running the stock firmware, ROM & recovery. Reason behind this is some of their phones are manufactured and shipped already S-OFF on 'accident'. So as long as you do the RUU you should be perfectly fine, at least that is what everyone has said thus far.
Click to expand...
Click to collapse
Are you willing to risk $800 bucks on this?
ericerk said:
Are you willing to risk $800 bucks on this?
Click to expand...
Click to collapse
Your risk not mine, if you're unsure then read through some other threads until you feel confident enough or wait for another person to answer.
& Sorry if I made you a bit unconfident with my last post, I have never had to return another phone to them so all I'm offering you is what I know and or have read from others who have done what you want to do. I'm quite sure that will work as many other people have claimed it worked for them but as with anything I could be wrong which is why I did not include a "*100% GUARANTEED!*" sign. Just offering support, always do your own research too, just as I had done to find that out.
S1L3nTShaDoWz said:
Your risk not mine, if you're unsure then read through some other threads until you feel confident enough or wait for another person to answer.
& Sorry if I made you a bit unconfident with my last post, I have never had to return another phone to them so all I'm offering you is what I know and or have read from others who have done what you want to do. I'm quite sure that will work as many other people have claimed it worked for them but as with anything I could be wrong which is why I did not include a "*100% GUARANTEED!*" sign. Just offering support, always do your own research too, just as I had done to find that out.
Click to expand...
Click to collapse
Bummer there's no official RUU's floating out there.
ericerk said:
Bummer there's no official RUU's floating out there.
Click to expand...
Click to collapse
I can vouch for the RUU I'm gonna link further in this post, I recently used it and successfully RUU'D my phone to stock.
http://www.droidviews.com/restore-verizon-htc-one-m8-to-stock-rom-with-ruu/2
ericerk said:
Are you willing to risk $800 bucks on this?
Click to expand...
Click to collapse
YOU have already done that the moment you modded your phone lol
S1L3nTShaDoWz said:
I can vouch for the RUU I'm gonna link further in this post, I recently used it and successfully RUU'D my phone to stock.
http://www.droidviews.com/restore-verizon-htc-one-m8-to-stock-rom-with-ruu/2
Click to expand...
Click to collapse
That's my ruu they link to. Stay on xda and get less shady stuff ?. Below is my thread on it..
http://forum.xda-developers.com/showthread.php?t=2727831
Amazing what some sites will do...
dottat said:
That's my ruu they link to. Stay on xda and get less shady stuff ?. Below is my thread on it..
http://forum.xda-developers.com/showthread.php?t=2727831
Amazing what some sites will do...
Click to expand...
Click to collapse
Since it's your RUU, is this RUU returning us to stock or stock-rooted?
tdnookhd said:
Since it's your RUU, is this RUU returning us to stock or stock-rooted?
Click to expand...
Click to collapse
Stock rooted.