Ok so I am aware of the thread that was created awhile back on using RUU to return to stock, but that didn't quite answer my questions so I am asking this question here and hopefully others in the future will benefit.
I am in need of getting my phone back to factory shipped conditions to get it replaced by Verizon. My headphone jack does not work at all and I just started getting sim card errors which I cannot deal with. So I need to fix this ASAP. The problem I forsee is that since I used Super CID to unlock the phone it has the red text error on bootup that says "this build is for development purposes.....blah blah" I imagine that Verizon will see this and tell me I voided my warranty and it is not their problem anymore. Here are my questions.
1. If I use RUU will it remove this message from the startup splash screen?
2. I am S-off, do I need to be s-on before I do this or will RUU put me S-on
3. People were saying it says "relocked" instead of "locked" on the bootloader screen. Is this going to be a problem as well?
4. Will I be able to get unlock, root, and s-off on the replacement phone?
I am going to continue searching the forums in case the answer is out there spread throughout many posts, but if anyone knows the answer or can help I would greatly appreciate it. Knowing the answer to this will be very helpful to many people I suspect.
Original return to stock thread
Imacellist said:
Ok so I am aware of the thread that was created awhile back on using RUU to return to stock, but that didn't quite answer my questions so I am asking this question here and hopefully others in the future will benefit.
I am in need of getting my phone back to factory shipped conditions to get it replaced by Verizon. My headphone jack does not work at all and I just started getting sim card errors which I cannot deal with. So I need to fix this ASAP. The problem I forsee is that since I used Super CID to unlock the phone it has the red text error on bootup that says "this build is for development purposes.....blah blah" I imagine that Verizon will see this and tell me I voided my warranty and it is not their problem anymore. Here are my questions.
1. If I use RUU will it remove this message from the startup splash screen?
2. I am S-off, do I need to be s-on before I do this or will RUU put me S-on
3. People were saying it says "relocked" instead of "locked" on the bootloader screen. Is this going to be a problem as well?
4. Will I be able to get unlock, root, and s-off on the replacement phone?
I am going to continue searching the forums in case the answer is out there spread throughout many posts, but if anyone knows the answer or can help I would greatly appreciate it. Knowing the answer to this will be very helpful to many people I suspect.
Original return to stock thread
Click to expand...
Click to collapse
Compliments of Phaded...well for combining everything in a great easy how to and the Scotty guy who originally posted it somewhere...
http://forum.xda-developers.com/showthread.php?t=2293919
bakemcbride21 said:
Compliments of Phaded...well for combining everything in a great easy how to and the Scotty guy who originally posted it somewhere...
http://forum.xda-developers.com/showthread.php?t=2293919
Click to expand...
Click to collapse
Beautiful. This is why I love the android community. So willing to help others. Thank you very much.
And to answer your last question, yes, you will be able to S-Off and Unlock your replacement phone.
There are 2 new methods available as of last week for 2.06 (latest firmware).
Related
I'm 99.9% sold on the Amaze, I will probably be ordering this weekend.
One niggling doubt is the s-off issue. I see that it hasn't been achieved yet, though you can unlock the bootloader via the HTC.com dev code, and that allows perma-rooting and Custom Roms to be installed.
My questions are:
What would S-off achieve? Would there be more impressive roms that use the space and/or resources from /system or somewhere else that can't be touched without S-off? Is a CM 9 possible for the Amaze without S-off? In the CM forums, the "last" word so far is that it hasn't been included on the official list because "it doesn't even have S-off yet".
Is there a difference warranty-wise? I understand the _possible_ implication of asking HTC for the code, they have you in some database that says you unlocked the bootloader. But as for the device itself, is one undoable and the other not?
I understand that flashing kernels would be harder without s-off because it would have to be done via adb, I think I understood. This is no big deal in itself.
Finally: if you unlock the bootloader via the HTC code, and weeks or months down the road an exploit is found to gain S-Off, are you hosed because you used the code and didn't wait?
I'd like to know so I can make my decision before getting the phone. If it's very disadvantageous to use the code rather than wait for S-off, for one reason or another, then I'd have to decide if I can live with only temp-rooting the device.
I am not going to use it on T-Mobile, I'm in Venezuela and will use it with my carrier here, so the unnecessary bloat will be even more of an annoyance, because on top of it sucking, it won't even work; so it would be important for me to at least root to get rid of it.
I'm sorry if my questions are too expansive, I picked up bits and pieces of information in other posts, but none of them answered these questions clearly. Thank you very much to all those who can help me answer them.
el_ochito said:
I'm 99.9% sold on the Amaze, I will probably be ordering this weekend.
One niggling doubt is the s-off issue. I see that it hasn't been achieved yet, though you can unlock the bootloader via the HTC.com dev code, and that allows perma-rooting and Custom Roms to be installed.
My questions are:
What would S-off achieve? Would there be more impressive roms that use the space and/or resources from /system or somewhere else that can't be touched without S-off? Is a CM 9 possible for the Amaze without S-off? In the CM forums, the "last" word so far is that it hasn't been included on the official list because "it doesn't even have S-off yet".
Is there a difference warranty-wise? I understand the _possible_ implication of asking HTC for the code, they have you in some database that says you unlocked the bootloader. But as for the device itself, is one undoable and the other not?
I understand that flashing kernels would be harder without s-off because it would have to be done via adb, I think I understood. This is no big deal in itself.
Finally: if you unlock the bootloader via the HTC code, and weeks or months down the road an exploit is found to gain S-Off, are you hosed because you used the code and didn't wait?
I'd like to know so I can make my decision before getting the phone. If it's very disadvantageous to use the code rather than wait for S-off, for one reason or another, then I'd have to decide if I can live with only temp-rooting the device.
I am not going to use it on T-Mobile, I'm in Venezuela and will use it with my carrier here, so the unnecessary bloat will be even more of an annoyance, because on top of it sucking, it won't even work; so it would be important for me to at least root to get rid of it.
I'm sorry if my questions are too expansive, I picked up bits and pieces of information in other posts, but none of them answered these questions clearly. Thank you very much to all those who can help me answer them.
Click to expand...
Click to collapse
I don't know where to start with all of your questions but I will do my best.
The difference between S-OFF and Unlocked bootloader is that with S-OFF you can flash anything including a radio and supposedly it would give us the ability to update the kernel by recovery. With an unlocked bootloader we cannot update the radio or kernel but can pretty much change everything else. An unlocked bootloader is required to root your device and remove all the bloat that you don't like. You can temp root the device to remove that bloatware however they will re-appear after a reboot. It has been under some debate if in fact using the unlock_code.bin file provided by htcdev is going to void your warranty if your device would require servicing. If it's vital to know that information then call HTC to inquire before unlocking.
Regarding CM9, it is possible but slightly inconvenient since CM9 would almost certainly require a different kernel and since we cannot flash kernels by recovery it would have to be done in a very certain order. Is it currently in the works? To my understanding, yes! Any idea when you can see it as a download here in the forums? Not at this time. Check back daily because things change frequently!
Thanks a lot for your response, Binary. I see you have an Amaze and have indeed unlocked its bootloader, so I guess the real question would be: when and if s-off is achieved, will you be able to do it even though you've already unlocked the bootloader with the .bin file?
Warranty would be terribly hard for me to take advantage of anyways after the initial check. If I don't RMA the unit, then I'm pretty much gambling on the fact that it will work well no matter what, since sending it back to the US from Venezuela would be a major PITA, so I don't really care much about voiding it.
el_ochito said:
Thanks a lot for your response, Binary. I see you have an Amaze and have indeed unlocked its bootloader, so I guess the real question would be: when and if s-off is achieved, will you be able to do it even though you've already unlocked the bootloader with the .bin file?
Warranty would be terribly hard for me to take advantage of anyways after the initial check. If I don't RMA the unit, then I'm pretty much gambling on the fact that it will work well no matter what, since sending it back to the US from Venezuela would be a major PITA, so I don't really care much about voiding it.
Click to expand...
Click to collapse
There is no reason that having an unlocked bootloader will interfere with being able to obtain s-off in the future because we can always relock the bootloader when (or if) it comes down to it.
Binary100100 said:
I don't know where to start with all of your questions but I will do my best.
The difference between S-OFF and Unlocked bootloader is that with S-OFF you can flash anything including a radio and supposedly it would give us the ability to update the kernel by recovery. With an unlocked bootloader we cannot update the radio or kernel but can pretty much change everything else. An unlocked bootloader is required to root your device and remove all the bloat that you don't like. You can temp root the device to remove that bloatware however they will re-appear after a reboot. It has been under some debate if in fact using the unlock_code.bin file provided by htcdev is going to void your warranty if your device would require servicing. If it's vital to know that information then call HTC to inquire before unlocking.
Regarding CM9, it is possible but slightly inconvenient since CM9 would almost certainly require a different kernel and since we cannot flash kernels by recovery it would have to be done in a very certain order. Is it currently in the works? To my understanding, yes! Any idea when you can see it as a download here in the forums? Not at this time. Check back daily because things change frequently!
Click to expand...
Click to collapse
Your words helped me a lot. I was thinking about the diff between s-on/off and lock.unlock bootloader for long. Thanks so much
Hey Guys,
I was wondering if there is a way to reset the phone so it looks like no rooting was done to it or anything along those lines.
I know I can relock the device but it will read "RE-LOCKED" in the boot loader. Is there any fix for that. Also Is there any way to unroot the device and flash the stock verizon boot and recovery images to it?
No way to not have it say relocked because we don't have S-off so even after back to stock ,Hboot will show Relocked instead of Locked.
Can relock by going back into the same folder you have the unlock bin and when you type in the CMD its something like Fastboot oem lock
Once relocked , you can run the stock RUU that is stickied on the forums and it will put it back to the stock Verizon version you had before you unlocked and rooted. There is a guide also on how to relock or else I know the info is on Htcdev site as well.
Thank you for the reply. I was hoping there had been a way to get it to just say locked. I am going to return the phone. Not really my cup of tea. I'm just waiting for the RUU to download then I will put that onto my device and hopefully they don't say anything.
Please let us know
deadheartsbeat said:
Thank you for the reply. I was hoping there had been a way to get it to just say locked. I am going to return the phone. Not really my cup of tea. I'm just waiting for the RUU to download then I will put that onto my device and hopefully they don't say anything.
Click to expand...
Click to collapse
Deadheartsbeat ... it would be appreciated if you would let us know if Verizon checks the phone AND if you ever get charged on your bill for the full value once it gets through Verizon's system and HTC's system (however they do warranty exchange). I have a thread going asking people to please report in (but, of course, 90% of the answers have nothing to do with the question asked):
http://forum.xda-developers.com/showthread.php?t=1453767
PLEASE think about letting the community know how the Verizon warranty return goes once you are Re-Locked. Thanks
jdmba said:
Deadheartsbeat ... it would be appreciated if you would let us know if Verizon checks the phone AND if you ever get charged on your bill for the full value once it gets through Verizon's system and HTC's system (however they do warranty exchange). I have a thread going asking people to please report in (but, of course, 90% of the answers have nothing to do with the question asked):
http://forum.xda-developers.com/showthread.php?t=1453767
PLEASE think about letting the community know how the Verizon warranty return goes once you are Re-Locked. Thanks
Click to expand...
Click to collapse
I'm not warrenty returning. I'm going for a full blown refund. If they try to charge me for the phone after I return it there will be issues. I will not let them charge me and keep the device. If they ask why I unlocked it I'm gunna tell them I thought I had to do that to install the app i made using the sdk.
I will let you know what happens though
Chances are if your returning it in return window and your just telling them it wasn't what you wanted they won't even bother looking in hboot. As long as phone is functioning properly when they turn it on and what not should be fine.
mjh68 said:
Chances are if your returning it in return window and your just telling them it wasn't what you wanted they won't even bother looking in hboot. .
Click to expand...
Click to collapse
LOL, exactly.
Most VZ reps don't even know what hboot means, never mind how to check it.....
~John
Hey everyone. I have to send my device back to HTC and I am unlocked with S-off.
I need to get back to locked and S-on. Not Re-locked but locked.
I have done some searching and am finding various results on how to accomplish this. 1 way was to flash a RUU to achieve locked status. I did that twice and it hasn't worked.
I also saw to redo s-off. So does that mean doing the wire trick over again?
Some help would be appreciated.
brownsfan said:
Hey everyone. I have to send my device back to HTC and I am unlocked with S-off.
I need to get back to locked and S-on. Not Re-locked but locked.
I have done some searching and am finding various results on how to accomplish this. 1 way was to flash a RUU to achieve locked status. I did that twice and it hasn't worked.
I also saw to redo s-off. So does that mean doing the wire trick over again?
Some help would be appreciated.
Click to expand...
Click to collapse
Why do you need to send your device back to HTC? If you're trying to claim warranty repairs, then what you're doing is potentially akin to fraud.
That said...yes, it IS possible to S-ON again, and it is also possible to change the Re-Locked watermark to Locked. But, if you don't do it right, you WILL brick your phone. Not as in "might" as you could do while S-Off, but WILL, as in ANY mistake will result in an unrecoverable phone (unless you have a friend who's extremely handy with JTAG).
Locked not Relocked
There are only 2 ways to remove the Relocked status when S-0ff::
First and the most effort is to S-0n then S-0ff again, yech.
Second, search for and find here on XDA, Scotty's little
flashable zip that changes it. He contributed a lot here.
Bing, bang, boom in one little flash.
p.s. be sure you are on a stock hBoot, not developer ones.
Thanks guys,
Im just going to send it back re-locked. I went back to s-on. I didnt want to just have it SAY locked, I wanted it to be Locked but no thanks to having to go through the s-off process.
Also in case you were interested the reason im sending it back is I think the processor is dying. I get system crashes and will get prompts that it is unresponsive. The phone sort of works but will crash after making phone calls and such.
So I discovered a slight gap on certain edges of my One, which I got a week ago, and want to return it to AT&T for one that hopefully has no issues, but I've rooted, unlocked the bootloader, and flashed CM 10.1 on there. I searched through google and the forums here on XDA to find a method to relock the bootloader and go back to stock, but my search was fruitless. Apparently something called an RUU was needed? And according to the last post in this thread, that isn't available.
Is the RUU available now? Or is it currently impossible to relock the bootloader?
If so, would I be able to pull off just flashing the stock ROM back onto the phone and bringing it into AT&T? I feel like the only way they would realize something was different with the phone would be if they rebooted it, as I highly doubt most of the people in that store could even get into the bootloader screen. They had trouble syncing my google account.
Unless, of course, they send it back to the manufacturer and then THEY say that the warranty is voided because of the unlocked bootloader... but I don't know if they go through all that trouble in this situation?
Thanks for the help.
CAC1291 said:
So I discovered a slight gap on certain edges of my One, which I got a week ago, and want to return it to AT&T for one that hopefully has no issues, but I've rooted, unlocked the bootloader, and flashed CM 10.1 on there. I searched through google and the forums here on XDA to find a method to relock the bootloader and go back to stock, but my search was fruitless. Apparently something called an RUU was needed? And according to the last post in this thread, that isn't available.
Is the RUU available now? Or is it currently impossible to relock the bootloader?
If so, would I be able to pull off just flashing the stock ROM back onto the phone and bringing it into AT&T? I feel like the only way they would realize something was different with the phone would be if they rebooted it, as I highly doubt most of the people in that store could even get into the bootloader screen. They had trouble syncing my google account.
Unless, of course, they send it back to the manufacturer and then THEY say that the warranty is voided because of the unlocked bootloader... but I don't know if they go through all that trouble in this situation?
Thanks for the help.
Click to expand...
Click to collapse
For a quick and easy way, just boot into fast boot and cmd "fastboot oem lock"
The only problem with that is that if they DO boot into the bootlaoder, it will say "RELOCKED" instead of "LOCKED"
The longer way, is to S-OFF (find it in the international forum) and then follow instructions there to put the "LOCKED" text back.
CAC1291 said:
So I discovered a slight gap on certain edges of my One, which I got a week ago, and want to return it to AT&T for one that hopefully has no issues, but I've rooted, unlocked the bootloader, and flashed CM 10.1 on there. I searched through google and the forums here on XDA to find a method to relock the bootloader and go back to stock, but my search was fruitless. Apparently something called an RUU was needed? And according to the last post in this thread, that isn't available.
Is the RUU available now? Or is it currently impossible to relock the bootloader?
If so, would I be able to pull off just flashing the stock ROM back onto the phone and bringing it into AT&T? I feel like the only way they would realize something was different with the phone would be if they rebooted it, as I highly doubt most of the people in that store could even get into the bootloader screen. They had trouble syncing my google account.
Unless, of course, they send it back to the manufacturer and then THEY say that the warranty is voided because of the unlocked bootloader... but I don't know if they go through all that trouble in this situation?
Thanks for the help.
Click to expand...
Click to collapse
Get S-OFF, I was able to remove TAMPERED and change my UNLOCKED to LOCKED. You can also flash a modded HBoot that will take the red letters away and change the text from S-OFF to S-ON this will allow it to look like you never touched a thing
To get S-OFF I recommend http://forum.xda-developers.com/showthread.php?t=2314582
To mod your HBoot go through the post from here http://forum.xda-developers.com/showthread.php?t=2316726 (to download the HBOOT and here http://forum.xda-developers.com/showthread.php?t=1786498 to download the tool to create the modified HBOOT
But to let you know, I have returned 2 HTC Ones with unlocked bootloaders and AT&T did not say anything. Just flash the stock rom, make sure fastboot in enabled and leave it booted to the set up screen. Above is for if you want to be thorough and make sure you cover all your bases.
I wanted to return my HTC One to stock, and it took me hours to do so. I had to search for multiple threads, and it was a big hassle and pretty confusing. I am back to stock now, although I am still S-Off. I figured I would compile a thread helping others in similar situations return to stock. This guide will help you return to sense, lock your bootloader, unroot, hide your tampered banner, as well as prevent your device from showing up as relocked. You're device will still remain S-Off after following these steps.
Here are the steps. I am assuming the recovery is device specific, and I wouldn't recommend flashing the recovery.img on any device other than the AT&T M8.
1. Make sure your device is S-Off. If not, download firewater and S-Off your device.
2. Restore a nandroid of the stock Sense ROM, or find a stock ROM to flash. You'll have to dig around; I used a nandroid.
3. Flash SuperSU.zip in recovery on top of the stock Sense ROM. You can find the SuperSU.zip here: http://download.chainfire.eu/396/SuperSU
4. Use adb to flash the stock recovery.img to your device. You can get the recovery files here. http://forum.xda-developers.com/showthread.php?t=2711814 *ONLY FOR THE AT&T MODEL*
5. Boot back up into sense, and follow this guide to remove the tampered banner in recovery. http://forum.xda-developers.com/showthread.php?t=2708565
6. Follow this guide to lock your boot loader and make it say **LOCKED** instead of **RELOCKED**. http://forum.xda-developers.com/showthread.php?t=2708571
7. Boot your device back up, and open SuperSU. Go into settings and find the "full unroot" option and run that. Reboot your device like it suggests.
8. I would factory reset your device in settings or recovery to make sure everything's clean, although this step isn't necessary.
Enjoy Sense! Hope I was able to help some of you guys! ?
Sent from my HTC One_M8 using Tapatalk
supitsronnie said:
I wanted to return my HTC One to stock, and it took me hours to do so. I had to search for multiple threads, and it was a big hassle and pretty confusing. I am back to stock now, although I am still S-Off. I figured I would compile a thread helping others in similar situations return to stock. This guide will help you return to sense, lock your bootloader, unroot, hide your tampered banner, as well as prevent your device from showing up as relocked. You're device will still remain S-Off after following these steps.
Here are the steps. I am assuming the recovery is device specific, and I wouldn't recommend flashing the recovery.img on any device other than the AT&T M8.
1. Restore a nandroid of the stock Sense ROM, or find a stock ROM to flash. You'll have to dig around; I used a nandroid.
2. Flash SuperSU.zip in recovery on top of the stock Sense ROM. You can find the SuperSU.zip here: http://download.chainfire.eu/396/SuperSU
3. Use adb to flash the stock recovery.img to your device. You can get the recovery files here. http://forum.xda-developers.com/showthread.php?t=2711814 *ONLY FOR THE AT&T MODEL*
4. Boot back up into sense, and follow this guide to remove the tampered banner in recovery. http://forum.xda-developers.com/showthread.php?t=2708565
5. Follow this guide to lock your boot loader and make it say **LOCKED** instead of **RELOCKED**. http://forum.xda-developers.com/showthread.php?t=2708571
6. Boot your device back up, and open SuperSU. Go into settings and find the "full unroot" option and run that. Reboot your device like it suggests.
7. I would factory reset your device in settings or recovery to make sure everything's clean, although this step isn't necessary.
Enjoy Sense! Hope I was able to help some of you guys! ?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Do you think these steps could pass with returning it to an AT&T store for exchange?
chrispyutec said:
Do you think these steps could pass with returning it to an AT&T store for exchange?
Click to expand...
Click to collapse
I am not sure. I haven't tried returning to AT&T. The only thing they can get you for is S-Off, but some devices shipped S-Off so I don't know how likely that is to happen. AT&T shouldn't look into it too much. They don't have access to HTCDev so they can't see you've requested an unlock token.
Sent from my HTC One_M8 using Tapatalk
supitsronnie said:
I am not sure. I haven't tried returning to AT&T. The only thing they can get you for is S-Off, but some devices shipped S-Off so I don't know how likely that is to happen. AT&T shouldn't look into it too much. They don't have access to HTCDev so they can't see you've requested an unlock token.
Click to expand...
Click to collapse
I don't know about your AT&T store reps, but I can't think of a single one from a store local to me that would have any clue whatsoever on how to determine if the device was rooted, unlocked, etc.
Also keep in mind that, unless you've personally irritated one of them, THEY (usually) DON'T CARE. They might be required to check certain things by AT&T corporate, but do you really think that a typical sales rep is going actually exert any extra effort whatsoever to check the device?
Take the steps you mentioned. Leave the device S-OFF, but clear the "tampered" flag (as you mentioned) and any type of red warning that happens on the boot animation. Basically, just fix up the extremely obvious stuff that a sales rep couldn't possible ignore. When you go to bring it back, act like you've never heard of "XDA", and if someone asks if the phone was modified, tell them that you changed the default ringtone or something silly like that. (In other words, play dumb.)
Delete
Delete
Sent from my HTC One_M8 using Tapatalk
I was in a store the other day with a friend who needed something done to his account. Beside us was a rep trying to activate an M8 for a customer. She kept running to the back to get different SIM cards and couldn't figure out why they wouldn't fit. She was trying to put them in the SD card slot
And you're worried about them checking bootloader locks and S-Off? :laugh:
To give an example of how "closely" an AT&T store rep examines a phone for exchange/return:
I noticed a couple days ago that the volume button on my own M8 is quite a bit more.. wiggly.... than the AT&T demo M8's in my local store. It doesn't really bother me, but I figured I was still in my "14 days" so I could get a simple exchange for a more perfect volume button.
So, I spent about an hour backing up my device, changing the CID back to CWS__001, switching the firmware back to AT&T stock, switching the recovery back to stock, patching the bootloader to NOT show "unlocked" or "tampered", etc. Basically, when I was done, it was nearly impossible for even a knowledgeable person to know I had "converted" the phone to a dev edition and so on.
I brought the phone to the store and here's what they did to examine it: NOTHING.
They saw that the screen turned on, and that was it. Nothing else. I was extremely disappointed. (Perhaps it relates that I had just factory reset it, so it was sitting at that stupid AT&T welcome screen... perhaps they didn't want to waste time tapping through all the prompts?)
Oh, and I ended up NOT doing the exchange. They brought a new one up, and it had the same wiggly volume button. So, we opened a couple more boxes and all were wiggly. Being that I didn't see any other defect in my existing phone, I decided to keep my known wiggle instead of risking a different different that wiggled just as much, but might also have some other issue.
Take care
Wiggles Gary
where do we find the stock nandroid to use? Does this work to get back to stock to get the latest OTA update?
jdk2 said:
I was in a store the other day with a friend who needed something done to his account. Beside us was a rep trying to activate an M8 for a customer. She kept running to the back to get different SIM cards and couldn't figure out why they wouldn't fit. She was trying to put them in the SD card slot
And you're worried about them checking bootloader locks and S-Off? :laugh:
Click to expand...
Click to collapse
LOL you laugh. My AT&T girl did the same thing. She had the nano sim sideways in the sd card slot and couldn't figure why it wouldn't go in.
drivel2787 said:
where do we find the stock nandroid to use? Does this work to get back to stock to get the latest OTA update?
Click to expand...
Click to collapse
You can find stock nandroid backups here: http://forum.xda-developers.com/showthread.php?t=2701376. Make sure your CID matches! Instructions are in that thread.
Yes, if you follow this method you will receive OTA updates again.
Sent from my HTC One_M8 using Tapatalk
I have to use HTC's free screen replacement program, im rooted, unlocked, and s-off... soooo, i have to do this before sending them my phone right?
JoSway said:
I have to use HTC's free screen replacement program, im rooted, unlocked, and s-off... soooo, i have to do this before sending them my phone right?
Click to expand...
Click to collapse
There was a poster who claimed they told him he was ineligible for the replacement because they had him on record on HTCdev as unlocking his boot loader. Said he needed the dev edition to be able to do that without voiding his warranty. That was just one person though
I got my device 2 days ago and rooted immediately. Then I noticed I was on the old firmware version, so I used your guide to get unroot and back to stock. It worked well. Now I'm updated and rooted again
deleted
garyd9 said:
To give an example of how "closely" an AT&T store rep examines a phone for exchange/return:
I noticed a couple days ago that the volume button on my own M8 is quite a bit more.. wiggly.... than the AT&T demo M8's in my local store. It doesn't really bother me, but I figured I was still in my "14 days" so I could get a simple exchange for a more perfect volume button.
So, I spent about an hour backing up my device, changing the CID back to CWS__001, switching the firmware back to AT&T stock, switching the recovery back to stock, patching the bootloader to NOT show "unlocked" or "tampered", etc. Basically, when I was done, it was nearly impossible for even a knowledgeable person to know I had "converted" the phone to a dev edition and so on.
I brought the phone to the store and here's what they did to examine it: NOTHING.
They saw that the screen turned on, and that was it. Nothing else. I was extremely disappointed. (Perhaps it relates that I had just factory reset it, so it was sitting at that stupid AT&T welcome screen... perhaps they didn't want to waste time tapping through all the prompts?)
Oh, and I ended up NOT doing the exchange. They brought a new one up, and it had the same wiggly volume button. So, we opened a couple more boxes and all were wiggly. Being that I didn't see any other defect in my existing phone, I decided to keep my known wiggle instead of risking a different different that wiggled just as much, but might also have some other issue.
Take care
Wiggles Gary
Click to expand...
Click to collapse
Believe it or not all you have to do is put the stock rom back on the device. You still have a hardware warranty. If say, your speaker is broken that would have occurred regardless of you flashing the ROM. Flashing the rom is not a punishment for you to live with bad hardware... However try to put back to stock if you can.
thank u for helping
Lil Jones said:
Believe it or not all you have to do is put the stock rom back on the device. You still have a hardware warranty. If say, your speaker is broken that would have occurred regardless of you flashing the ROM. Flashing the rom is not a punishment for you to live with bad hardware... However try to put back to stock if you can.
Click to expand...
Click to collapse
AT&T terms clearly state that they have the "right" to void warranty if the software is modified.
In reality, AT&T will not check or care. Its more important to keep you as a monthly account holder, versus the relatively modest price if a refurb phone. I've seen many reports of successful warranty exchanges with unlocked bootloader, root, even having an obviously custom ROM (like CM) installed.
Return to close as stock as possible/feasible to play it safe. But its likely not going to be a deal breaker.
can i be S-Off and do ATT OTA's?
rahtrip said:
can i be S-Off and do ATT OTA's?
Click to expand...
Click to collapse
Sure. But if you've bothered to s-off, why would you want to?
Sent from my HTC One_M8 using XDA Free mobile app