T-mobile M8 best method to prepare for warranty exchange - One (M8) Q&A, Help & Troubleshooting

I posted this over in the T-Mobile M8 forums but didn't get any answers. Since the T-Mobile forums don't get much attention, I figured I would try over here in the M8 general forums...
I've got the fuzzy lens problem and I want to get the phone replaced (preferably via T-Mobile but I'll go directly to HTC if I have to). I know you can scratch off the coating on the lens and get some camera improvement but I'm not interested in that solution.
My goal: Return the phone to completely stock condition. No root, locked bootloader and preferably S-ON. I've read a few stories where HTC insisted on replacing the motherboard (with an additional full price fee) because the device was S-OFF and I don't want to go there.
Background: I used firewater to S-off the phone as soon as I got it (it was running 1.12 at the time). I have flashed the Harmon Kardon audio stuff (http://forum.xda-developers.com/showthread.php?t=2737498). I have turned off the tamper flag (http://forum.xda-developers.com/showthread.php?t=2708565). I am running the Stock+ rom which is based on 1.57 (http://forum.xda-developers.com/showthread.php?t=2716843).
My plan:
1) Reset my bootloader to locked (http://forum.xda-developers.com/showthread.php?t=2708571)
2) Wipe the phone and restore my very first nandroid backup I made with TWRP. That will get me back to unrooted 1.12 firmware but without the stock bootloader and still S-OFF. Staying with 1.12 will allow me to S-OFF again with firewater if it comes to that. If some kind of emergency came up, I'd hate to spend $25 on sunshine for a one time use on a phone that is going back to HTC forever.
3) Install the stock bootloader that matches 1.12 firmware. Not sure how to do this yet. I'm afraid I won't be able to achieve this with a locked bootloader and no root.
4) Verify everything is back to stock.
5) Set the phone back to S-ON (http://forum.xda-developers.com/showthread.php?t=2758818)
6) Run the 1.57 RUU (http://forum.xda-developers.com/showthread.php?t=2714456)
7) Proceed with the warranty exchange.
I'm not sure running the RUU is 100% necessary, but I figure it's the best bet I have to make the phone completely stock.
Questions: Is this a sane plan? Am I doing anything in the wrong order? Are there any steps that won't work because I've lost root or unlocked bootloader? Am I setting myself up for a brick anywhere?
There is a thread about doing this on a EU M8 (http://forum.xda-developers.com/showthread.php?t=2735235) but I can't tell what, if any, modifications need to be done for the USA T-Mobile version of the M8. There is talk about having to flash a firmware file twice or risk a hard brick when setting S-ON. Do I need to be worried about any of that?

Generally, when you lock bootloader, it says relocked, so they can tell. Maybe reflashing bootloader will work
Sent from my HTC One V using XDA Free mobile app

tzzeri said:
Generally, when you lock bootloader, it says relocked, so they can tell. Maybe reflashing bootloader will work
Click to expand...
Click to collapse
Thanks for the reply. This thread (http://forum.xda-developers.com/showthread.php?t=2708571) appears to give a way to avoid the relocked indicator and shows the proper "locked" text in the screenshot, so I think I am good there.
Any other advice?

I had a similar problem, only I did remove the coating. I wasn't rooted though, haven't seen the need to do so YET. I went into the store and showed the rep there what the problem was, mine wouldn't focus at all anymore. And they sent me a "new" (read refurbished) device, while I held on to mine. I was at the 4 month mark of having the phone and I didn't have insurance on it. No hoop jumping for me at all. If this happens again anytime soon I might have to fight to switch to a different phone. This is just ridiculous. I love the phone but the camera problems are insane for the price of this device. I also told them the problems popped up after I upgraded to 4.4.3 which they did but that's probably just a coincidence.
Sent from my HTC One_M8 using XDA Free mobile app

Gargamel1 said:
I had a similar problem, only I did remove the coating. I wasn't rooted though, haven't seen the need to do so YET. I went into the store and showed the rep there what the problem was, mine wouldn't focus at all anymore. And they sent me a "new" (read refurbished) device, while I held on to mine. I was at the 4 month mark of having the phone and I didn't have insurance on it. No hoop jumping for me at all. If this happens again anytime soon I might have to fight to switch to a different phone. This is just ridiculous. I love the phone but the camera problems are insane for the price of this device. I also told them the problems popped up after I upgraded to 4.4.3 which they did but that's probably just a coincidence.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Wait, you removed the coating and then went into t-mobile? I would think they would say no to a warranty exchange since you tried to do it yourself first. Get rid of the coating that is.
Sent from my HTC One_M8 using Tapatalk

I thought so also but figured it was worth a try. I did a pretty decent job removing it, and unless the person is fully aware of the issue and some of the diy fixes they won't notice.
Sent from my HTC One_M8 using XDA Free mobile app

Success
UPDATE: T-Mobile gave me a warranty replacement to fix the camera lens problem. I did get the old phone back to completely stock with locked bootloader and S-on before sending it back.
I found it was easiest to use the sunshine installer to gain temp root. You don't need to pay anything since you stop before it goes through the whole S-Off process. Just run the APK and select temp root. When sunshine shows you the next screen, you can exit out and still have root. (http://theroot.ninja/)
In the end I didn't bother with the old nandroid and keeping the exploitable version. I also had the order messed up in my initial post. Here is what worked for me:
1) factory reset the phone (in TWRP I did advanced wipe and also wiped internal storage). This step kills root. Rebooted the phone and verified it was back to factory defaults. Go through the setup wizard and skip all the steps. I couldn't find a way to bail out without going through every step in the wizard.
2) flashed stock recovery (the bootloader was unlocked and the phone was S-Off). Root is not necessary for this since it is done in fastboot. (http://forum.xda-developers.com/tmo...l/ota-recovery-ruus-firmware-dumps-t-t2852107). Rebooted the phone.
3) achieved temp root using sunshine APK
4) locked the bootloader (required before running the RUU). You must have root since you need a SU # prompt in the shell. (http://forum.xda-developers.com/showthread.php?t=2708571). I rebooted again for good measure but it's probably not necessary.
5) reset the phone back to completely stock using the latest 2.22.531.5 RUU. This step does not require root. I found it was easiest to put the phone into fastboot mode before running the RUU. (http://www.htcdev.com/devcenter/downloads)
6) Once the phone booted back up, I looked over everything and made sure it is all completely stock. Checked HBOOT said locked (not relocked) and dis not say tampered.
7) OPTIONAL - set S-On. Again root is not required since this is a fastboot command. (http://forum.xda-developers.com/showpost.php?p=52823014&postcount=2)
My actual process wasn't this streamlined. I ended up doing the RUU a couple of times because I didn't flash the stock recovery first and I didn't think the RUU installed the stock recovery right. Turned out I just didn't know what the stock recovery looked like (it was very confusing since I had never actually used a HTC stock recovery).
Thanks to the authors of the various threads I pulled info from. They are the real MVP's.

Related

[Q] S On (and S Off) & "Tampered"

I need to send my HTC One M8 back to HTC because the "vibration" function works intermittently (boo!).
I restored my phone with my backup. Then I turned my attention to getting "Tampered" removed. I followed a tutorial through but only to realize that I'm S On (and not the required S Off).
Can I remove the "Tampered" if I'm S On?
Last question, should I mess with the "Unlocked", i.e., try to "Relock" it.
I just want the HTC Warranty folks to: 1) see that my "vibration" function is not working and 2) send me a new phone or fix it.
Please help and thanks much!!! 
Check this it should help
http://forum.xda-developers.com/showthread.php?t=2708565
Sent from my LG-V500 using XDA Free mobile app
majorcedar said:
I need to send my HTC One M8 back to HTC because the "vibration" function works intermittently (boo!).
I restored my phone with my backup. Then I turned my attention to getting "Tampered" removed. I followed a tutorial through but only to realize that I'm S On (and not the required S Off).
Can I remove the "Tampered" if I'm S On?
Last question, should I mess with the "Unlocked", i.e., try to "Relock" it.
I just want the HTC Warranty folks to: 1) see that my "vibration" function is not working and 2) send me a new phone or fix it.
Please help and thanks much!!! 
Click to expand...
Click to collapse
I just got my phone back from HTC last week, I sent it to them, rooted, unlocked, s-off and having ViperOneM8 rom installed. I figured all they was going to do was replace the camera lens, why would they even start it. It came back unrooted, s-on and stock installed. As a matter of fact, I couldn't use firewater this time to get s-off, I had to pay sunshine. So here is what I figured they did.
1) Unbox phone
2) Plug phone into computer
3) Run a program that installs the latest stock OS in it.
4) Fix problem
5) Ship back...
It has the same EMIE number, and my tempered glass protector was still installed, so I know it was the same phone. I think they do that to just about all phones, I have yet to hear that they rejected a phone because of it being rooted, etc....
Mine was the same, but I did revert everything to stock but left s off, come back with s on ?

[Q] Back to stock from NuSense

Need to take my Verizon One M7 in for a replacement. Reception is killing me (keep dropping to 1X or weak 3G in outlying areas), calls drop more than they don't, and even getting mms generic errors. Tried multiple ROM's, multiple radios, stock recovery/ROM/reset, new SIM card...nothing works.
I did notice something though - when I first got this phone, they had trouble initializing the SIM in the store...thought nothing of it until I went to the corporate store for a replacement SIM and they couldn't get the replacement to activate from the phone...I am thinking I have bad hardware.
The guy was cool (he looked my stats up and was shocked at the dropped calls) but made a point to tell me it was likely behaving badly due to being rooted...would rather walk in with a plain vanilla phone and let them replace it or let me out of my extension and I will go back to my trusty ReZound, because this thing is useless as a phone as-is.
How do I get back to pure stock so I can take this in for a replacement?
ROM is NuSenseSIX-KitKat_m7vzw_RC7.4_071714
Radios from 4.10.605.3_NoBootImg_firmware
TWRP 2.7.08
Rooted (and hboot) using Firewater (have the red warning 'this is only for internal HTC use..." on the boot splash screen)
the_Damaged_one said:
Need to take my Verizon One M7 in for a replacement. Reception is killing me (keep dropping to 1X or weak 3G in outlying areas), calls drop more than they don't, and even getting mms generic errors. Tried multiple ROM's, multiple radios, stock recovery/ROM/reset, new SIM card...nothing works.
I did notice something though - when I first got this phone, they had trouble initializing the SIM in the store...thought nothing of it until I went to the corporate store for a replacement SIM and they couldn't get the replacement to activate from the phone...I am thinking I have bad hardware.
The guy was cool (he looked my stats up and was shocked at the dropped calls) but made a point to tell me it was likely behaving badly due to being rooted...would rather walk in with a plain vanilla phone and let them replace it or let me out of my extension and I will go back to my trusty ReZound, because this thing is useless as a phone as-is.
How do I get back to pure stock so I can take this in for a replacement?
ROM is NuSenseSIX-KitKat_m7vzw_RC7.4_071714
Radios from 4.10.605.3_NoBootImg_firmware
TWRP 2.7.08
Rooted (and hboot) using Firewater (have the red warning 'this is only for internal HTC use..." on the boot splash screen)
Click to expand...
Click to collapse
fastboot ruu would be the easiest way.
once ruu is complete you can write secure flag back to s-on and it will be 100% stock.
synisterwolf said:
fastboot ruu would be the easiest way.
once ruu is complete you can write secure flag back to s-on and it will be 100% stock.
Click to expand...
Click to collapse
Thanks synisterwolf...two questions:
1 - I assume one of these would be what I want for a full RUU (not 100% sure which one)?
(from http://forum.xda-developers.com/showthread.php?t=2485319)
2.10.605.1 Decrypted RUU
2.10.605.1 Signed RUU
Odexed Full Rom (4.10.605.3 4.4.2 Sense 6.0)
2 - I found this guide...if I use the updated RUU, is the rest of this process still valid?
http://forum.xda-developers.com/showthread.php?t=2475216
the_Damaged_one said:
Thanks synisterwolf...two questions:
1 - I assume one of these would be what I want for a full RUU (not 100% sure which one)?
(from http://forum.xda-developers.com/showthread.php?t=2485319)
2.10.605.1 Decrypted RUU
2.10.605.1 Signed RUU
Odexed Full Rom (4.10.605.3 4.4.2 Sense 6.0)
2 - I found this guide...if I use the updated RUU, is the rest of this process still valid?
http://forum.xda-developers.com/showthread.php?t=2475216
Click to expand...
Click to collapse
guide is correct but use this link for RUU:
http://forum.xda-developers.com/showthread.php?t=2765784
the one you posted is a rom that you flash in recovery and not a full RUU
Be sure to follow the "lock bootloader" instructions before you ruu. There is a command either done in adb with root or recovery flashable zip to get "locked" instead of "relocked". As you see above, it requires you to either be rooted our have custom recovery, so do it before ruu and s-on after ruu completes.
Side note: ruu will wipe the whole phone, so be sure to copy your pictures, music, etc to a PC before ruu.
Edit: I recommend the signed 2.x.x.x ruu as it is fully stock. The new one linked above is rooted, so you would have to unroot and all that after you ruu.
Sent from my HTC6500LVW using XDA Free mobile app
Thanks guys...any chance one of you has a link to the signed fully stock RUU?
edit: (or is that the one I found above on santod's thread that says it's signed? I am guessing signed means fully stock, not rooted, etc?)
the_Damaged_one said:
Thanks guys...any chance one of you has a link to the signed fully stock RUU?
edit: (or is that the one I found above on santod's thread that says it's signed? I am guessing signed means fully stock, not rooted, etc?)
Click to expand...
Click to collapse
Correct, the one from santods thread. Signed
means it has been signed and encrypted by HTC.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
Correct, the one from santods thread. Signed
means it has been signed and encrypted by HTC.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
Makes sense...never needed to use an encrypted one before on my DINC or ReZound, so I wasn't up to speed on the differences. Appreciate the guidance on this.
Will also give it a day on stock (keeping s-off) to see if it actually helps...though I suspect it won't.
the_Damaged_one said:
Makes sense...never needed to use an encrypted one before on my DINC or ReZound, so I wasn't up to speed on the differences. Appreciate the guidance on this.
Will also give it a day on stock (keeping s-off) to see if it actually helps...though I suspect it won't.
Click to expand...
Click to collapse
You don't "need" to, but it is always the better option if it is available.
Sent from my HTC6500LVW using XDA Free mobile app
Thanks for the help...
I did get the stock (signed, encrypted) RUU to load...had to back-rev my firmware using santod's post first, but otherwise all went as expected.
After a few updates OTA, I have been on the 4.4.2 for a couple of days - still cruddy signal at my house, so I plan ot s-on and head into the local corporate store to see what's next.
Will post on the other thread for the folks looking for the right RUU link.
Uzephi said:
You don't "need" to, but it is always the better option if it is available.
Click to expand...
Click to collapse
Speaking of better option...want to make sure I avoid a "tampered" issue...
I left my One s-off after the RUU, and updated OTA to latest to see if that helped my issue (it did not).
To go s-on, am I ok to do it now, or do I need to flash back to an older RUU first? Not sure if Verizon built something into a newer update that may catch the flag change.
No. Verizon has no control on that deep of the inner workings of an HTC. Only way to trip a "Tampered" state is messing with the system partition, radio, etc without being s-off. Turning s-off to s-on with everything stock will not trip that flag.
Edit: in my experience with HTC bootloaders, (I have had an Inc, Rezound, DNA, and this m7) they all are different in certain ways. The Inc never had a "Tampered" tag, to my knowledge. The Rezound had "tampered" tripped when a custom recovery was flashed while s-on. We had a special way of utilizing "fastboot boot recovery" command to prevent the tampered from ever being tripped. I didn't have my DNA long enough to worry about "tampered". And to get bootloader unlock for this phone, it did s-off so tampered wasn't tripped for me.
So how are HTC bootloader different by device? When my Inc had to be rooted, it didn't have a "locked" or "unlocked" flag, only s-on/off. The Rezound had to be s-off if you wanted to flash everything of a Rom in recovery (or utilize HTC dumlock or "fastboot boot recovery" command from bootloader) otherwise after a Rom install, tampered would trip and the boot.img wouldn't be flashed and you would have to go to bootloader to flash the boot.img or do the workaround in parentheses... For the DNA and m7, you don't need s-off to flash boot.img in recovery. I do notice on stock bootloader (I have the faux hboot) it will check if radio, hboot, and recovery are stock or not and I think this is what s-on checks for when tripping tampered. (Before I flashed the faux hboot it showed everything green except recovery since I have TWRP and not stock)
For any inaccuracies you can correct me and I will fix. This is from my own experiences with these devices and how they work.
TL/DR: all HTC model bootloader are different, but one thing never changes, if you are completely stock s-off and run the command "fastboot oem writesecureflag 3" it will not trip tampered.
Sent from my HTC6500LVW using XDA Free mobile app

Best method to prepare for warranty exchange

I've got the fuzzy lens problem and I want to get the phone replaced (preferably via T-Mobile but I'll go directly to HTC if I have to). I know you can scratch off the coating on the lens and get some camera improvement but I'm not interested in that solution.
My goal: Return the phone to completely stock condition. No root, locked bootloader and preferably S-ON. I've read a few stories where HTC insisted on replacing the motherboard (with an additional full price fee) because the device was S-OFF and I don't want to go there.
Background: I used firewater to S-off the phone as soon as I got it (it was running 1.12 at the time). I have flashed the Harmon Kardon audio stuff (http://forum.xda-developers.com/showthread.php?t=2737498). I have turned off the tamper flag (http://forum.xda-developers.com/showthread.php?t=2708565). I am running the Stock+ rom which is based on 1.57 (http://forum.xda-developers.com/showthread.php?t=2716843).
My plan:
1) Reset my bootloader to locked (http://forum.xda-developers.com/showthread.php?t=2708571)
2) Wipe the phone and restore my very first nandroid backup I made with TWRP. That will get me back to unrooted 1.12 firmware but without the stock bootloader and still S-OFF. Staying with 1.12 will allow me to S-OFF again with firewater if it comes to that. If some kind of emergency came up, I'd hate to spend $25 on sunshine for a one time use on a phone that is going back to HTC forever.
3) Install the stock bootloader that matches 1.12 firmware. Not sure how to do this yet. I'm afraid I won't be able to achieve this with a locked bootloader and no root.
4) Verify everything is back to stock.
5) Set the phone back to S-ON (http://forum.xda-developers.com/showthread.php?t=2758818)
6) Run the 1.57 RUU (http://forum.xda-developers.com/showthread.php?t=2714456)
7) Proceed with the warranty exchange.
I'm not sure running the RUU is 100% necessary, but I figure it's the best bet I have to make the phone completely stock.
Questions: Is this a sane plan? Am I doing anything in the wrong order? Are there any steps that won't work because I've lost root or unlocked bootloader? Am I setting myself up for a brick anywhere?
There is a thread about doing this on a EU M8 (http://forum.xda-developers.com/showthread.php?t=2735235) but I can't tell what, if any, modifications need to be done for the USA T-Mobile version of the M8. There is talk about having to flash a firmware file twice or risk a hard brick when setting S-ON. Do I need to be worried about any of that?
UPDATE: T-Mobile gave me a warranty replacement to fix the camera lens problem. I did get the old phone back to completely stock with locked bootloader and S-on before sending it back.
I found it was easiest to use the sunshine installer to gain temp root. You don't need to pay anything since you stop before it goes through the whole S-Off process. Just run the APK and select temp root. When sunshine shows you the next screen, you can exit out and still have root. (http://theroot.ninja/)
In the end I didn't bother with the old nandroid and keeping the exploitable version. I also had the order messed up in my initial post. Here is what worked for me:
1) factory reset the phone (in TWRP I did advanced wipe and also wiped internal storage). This step kills root. Rebooted the phone and verified it was back to factory defaults. Go through the setup wizard and skip all the steps. I couldn't find a way to bail out without going through every step in the wizard.
2) flashed stock recovery (the bootloader was unlocked and the phone was S-Off). Root is not necessary for this since it is done in fastboot. (http://forum.xda-developers.com/tmo...l/ota-recovery-ruus-firmware-dumps-t-t2852107). Rebooted the phone.
3) achieved temp root using sunshine APK
4) locked the bootloader (required before running the RUU). You must have root since you need a SU # prompt in the shell. (http://forum.xda-developers.com/showthread.php?t=2708571). I rebooted again for good measure but it's probably not necessary.
5) reset the phone back to completely stock using the latest 2.22.531.5 RUU. This step does not require root. I found it was easiest to put the phone into fastboot mode before running the RUU. (http://www.htcdev.com/devcenter/downloads)
6) Once the phone booted back up, I looked over everything and made sure it is all completely stock. Checked HBOOT said locked (not relocked) and dis not say tampered.
7) OPTIONAL - set S-On. Again root is not required since this is a fastboot command. (http://forum.xda-developers.com/showpost.php?p=52823014&postcount=2)
My actual process wasn't this streamlined. I ended up doing the RUU a couple of times because I didn't flash the stock recovery first and I didn't think the RUU installed the stock recovery right. Turned out I just didn't know what the stock recovery looked like (it was very confusing since I had never actually used a HTC stock recovery).
Thanks to the authors of the various threads I pulled info from. They are the real MVP's.
I flashed the stock HTC RUU via the .EXE and wasn't able to get the "RELOCKED" off the phone. Tried some steps here:
http://www.droidviews.com/restore-att-htc-one-m8-stock-firmware/
however I wasn't able to get "SU" to properly run in terminal.
No w the phone says *** RELOCKED ***
and im S-On
anything I can do?

[Q] Need some advice... confused about stock recovery version necessary (and more!)

Hello fellow TMO brethren....
I just got the M8 maybe a week ago... I was busy and had to wait before I could pull up XDA and start reading about this phone (getting root, etc.). Before this, I unfortunately allowed a few updates (2 maybe?) to install, which I believe will prevent me from using Firewater for S-Off... but no big deal....will get sunshine when I need it. However, though firewater won't work, I had no problem using HTCDev to unlock the bootloader (didn't know of towelroot at the time), flashing TWRP 2.8.0.1, and installing SuperSU....so I am currently rooted with stock Rom...
Further...I have not touched any applications. And although I have unlocked the bootloader using HTCDev, my calculator and flashlight are still available. I have read in this M8 general forum that the flashlight and calculator are deleted when you unlock the bootloader using HTCDev... This did not happen to me. Does anyone know if this is this just a T-Mobile thing? or has this changed for all carriers?
Anyway, I am now getting notice for yet another update...So I might as well install it. As we all know, I need to re-flash the stock recovery to get the OTA. Here is where I am confused. My current firmware is 2.22.531.5. I don't know what firmware I had a week ago when the phone was purchased.
This was the info on the bootloader screen yesterday, immediately prior to unlocking the BL or rooting the phone:
[btw, can someone tell me how to do a info dump from the bootloader?? is it just an option I missed?]
*** LOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
Radio-1.19.213311491.03G
OpenDSP-v38.2.2-00542-M8974.0311
OS-2.22.531.5
eMMC-boot 2048MB
Jul 16 2014,03:33:24.0
1. My first question is what version of the stock recovery do I use?? On the page that contains the stock recoveries, it only shows these two:
Stock Recovery - 1.12.531.19
Stock Recovery - 1.57.531.7
2. Secondly, and I am really irritated about this.... but I never went and accepted the Google Drive free 65GB promo offered by HTC. When I start google drive it states it cannot determine the user (or something like that). I read elsewhere that this is because I unlocked the bootloader. I will do whatever it takes to get HTC to give me this because I think it is pretty low that they would invalidate the offer to anyone who has unlocked the bootloader pursuant to their website, their instructions, and their so-called "open atitude". Obviously I can re-lock the bootloader, but I do not know if that will matter. Plus... if they say that I requested a token .bin file to unlock, I can say that I changed my mind and decided not too. OR, I can get Sunshine, get s-off, and use the s-off ability to relock the bootloader. Does anyone have any advice on any of this?
3. Any general advice from anyone based on the info above??? (lI don't want to foreclose any other options by upgrading or whatever... ).
Thank you very much in advance!
P
NB: Wanted to mention that last night I was about to use Titanium to freeze and/or uninstall some crap software I didn't want, and to that end, disabled Amazon, Facebook, Facebook for HTC, and Kid Zone (and uninstalled Amazon MP3, which is not a system app). Just an FYI... disabling one (or more) of these apps (maybe Kid Zone?) prevented Wifi calling from functioning correctly...it would not let me call and every in-call received while on wifi calling went straight to VM. I have renabled the above apps to get wifi-calling working again, but also because I want to install this update and figured that disabling/freezing any original stock apps might cause problems. I will look around for a thread on safely deleting apps after I get this udpate...
Try this for getting your drive space.
http://forum.xda-developers.com/showthread.php?t=2708571
Its now 100GB so its definitely worth a shot. As for getting back to stock for an update you can always use a RUU since relocking your bootloader will drive space then unlocking it again after will cause a factory reset anyway. Back up everything that isnt already, relock with the instructions from the thread I linked, run a ruu to get back to stock, update the system, then unlock your bootloader again with your unlock code bin file.
phil.culler said:
Try this for getting your drive space.
http://forum.xda-developers.com/showthread.php?t=2708571
Its now 100GB so its definitely worth a shot. As for getting back to stock for an update you can always use a RUU since relocking your bootloader will drive space then unlocking it again after will cause a factory reset anyway. Back up everything that isnt already, relock with the instructions from the thread I linked, run a ruu to get back to stock, update the system, then unlock your bootloader again with your unlock code bin file.
Click to expand...
Click to collapse
OK... that sounds like great info.... But to confirm though... I need S-off to relock bootloader. This is because I am essentially going back to factory default lock (without dealing with HTC at all). And by doing this, and then flashing the RUU (backing up everything first of course), I will be back to square one stock. For one, this will make it tough for HTC to claim I unlocked the bootloader (minimizing potentially any dispute over Google Drive promo). Then I would get any/all outstanding updates. I guess if I need S-off, then I would need to get sunshine, so I could just let that app re-unlock the bootloader. instead of using the .bin file (presuming I need s-off)?
Sorry... just confused as to when and for what specifically I need S-off (as your link emphasizes this).
Thanks a lot!!!!:good:
syntropic said:
OK... that sounds like great info.... But to confirm though... I need S-off to relock bootloader. This is because I am essentially going back to factory default lock (without dealing with HTC at all). And by doing this, and then flashing the RUU (backing up everything first of course), I will be back to square one stock. For one, this will make it tough for HTC to claim I unlocked the bootloader (minimizing potentially any dispute over Google Drive promo). Then I would get any/all outstanding updates. I guess if I need S-off, then I would need to get sunshine, so I could just let that app re-unlock the bootloader. instead of using the .bin file (presuming I need s-off)?
Sorry... just confused as to when and for what specifically I need S-off (as your link emphasizes this).
Thanks a lot!!!!:good:
Click to expand...
Click to collapse
It looks like you will need S-Off to factory lock the bootloader. S-Off allows you to make changes to otherwise protected areas of the file system. To clarify, I haven't tried this method myself as I haven't had a need to factory relock my device yet. I ran full stock for months before I rooted. As for HTC knowing whether or not you unlocked your bootloader, if you used the HTCDEV method then they have record of you receiving an unlock token from them but if they go into bootloader for any reason and see Locked instead of Relocked they shouldnt give you any trouble I would think. I believe you can also reset it to S-On but again I've never tried and I'm not sure its entirely safe. You'll have to look into that.

Quick RUU Question, need to bring my phone back to TMO

I'm done with these issues that my phone is having. It keeps locking up no matter what ROM I use or how little apps I have installed. Something has got to be wrong with my phone and it's time to bring it back to TMO for repair/replacement.
I found this link on HTC to download the RUU: http://www.htc.com/us/support/rom-downloads.html#tmobile
My question is, would this be enough to bring my phone back to stock so that they don't know I've rooted it?
Edit: Also, I just remembered about my bootloader being s-off/unlocked. Would this make a difference or would the RUU set everything back like it should?
Edit again: I found this thread: http://forum.xda-developers.com/showthread.php?t=2735235
So, would I be able to follow his instructions but change the CID to t-mob010 instead of the ones he has listed?
Nobody? I could really use some input on this, I don't want to brick my phone. I have to do this today, I can't take the lockups anymore.
There is a thread dedicated to returning your device to stock. It's intended for European users, but the instructions apply equally well to US users.
The first step is running the RUU, then locking (not relocking) the bootloader using adb commands. Reference http://forum.xda-developers.com/showthread.php?t=2708571 (for instructions on locking your bootloader)
Note that you can run the RUU without locking your bootloader if you are S-off. Once you are back to bone stock (recovery + OS), you can then go back S-on if you are concerned about the warranty, though I strongly advise AGAINST this in general.
Also, you may find that simply re-running the RUU will clear up your issue. I'd run it for a few days after restoring the phone before assuming a hardware fault.
jshamlet said:
There is a thread dedicated to returning your device to stock. It's intended for European users, but the instructions apply equally well to US users.
The first step is running the RUU, then locking (not relocking) the bootloader using adb commands. Reference http://forum.xda-developers.com/showthread.php?t=2708571 (for instructions on locking your bootloader)
Note that you can run the RUU without locking your bootloader if you are S-off. Once you are back to bone stock (recovery + OS), you can then go back S-on if you are concerned about the warranty, though I strongly advise AGAINST this in general.
Also, you may find that simply re-running the RUU will clear up your issue. I'd run it for a few days after restoring the phone before assuming a hardware fault.
Click to expand...
Click to collapse
Yes, I did find that post and am planning on following those instructions. However, you've confused me. According to that thread, they say to lock the bootloader first and then install the RUU; but you said the opposite. Which is it?
http://forum.xda-developers.com/showthread.php?t=2735235
Also, why are you against turning back S-on? I had planned on it because I don't want to take the chance of TMO or HTC having a problem.
ned4spd8874 said:
Yes, I did find that post and am planning on following those instructions. However, you've confused me. According to that thread, they say to lock the bootloader first and then install the RUU; but you said the opposite. Which is it?
http://forum.xda-developers.com/showthread.php?t=2735235
Also, why are you against turning back S-on? I had planned on it because I don't want to take the chance of TMO or HTC having a problem.
Click to expand...
Click to collapse
You are S-off, which means you do NOT have to lock the bootloader first. Most instructions for running an RUU assume you are S-on, however, which does require your bootloader to be locked. It's one of the checks that is disabled by S-off.
Also, S-off is getting harder to obtain, so unless there is a pressing reason to go S-on, it's safer to remain S-off. Warranty support could be that pressing reason.
Time to turn back S-on. Even after the RUU, it's still very buggy. Locking up, slow, lag, etc. Time to bring it back to TMO.
Anyone know what that will work? I do have the warranty service on it. So will they just replace my phone with a refurb M8, will it be sent out, what can I expect?
ned4spd8874 said:
Time to turn back S-on. Even after the RUU, it's still very buggy. Locking up, slow, lag, etc. Time to bring it back to TMO.
Anyone know what that will work? I do have the warranty service on it. So will they just replace my phone with a refurb M8, will it be sent out, what can I expect?
Click to expand...
Click to collapse
If you think your phone has bad hardware, then yeah, at this point you need to go ahead and S-on with the assumption that you will get a refurb - especially now that the M9 has been out a while. Who knows what you will get, though. You might even luck out and get a "new old stock" device with 4.4.2. Or, the refurb place could RUU it up to the latest. It's purely the luck of the draw.
Well this sucks. Can't get adb to recognize my phone in recovery. I can when it's booted into the system, but not recovery or the bootloader....
What a pain this is becoming!!!!!!!!!!!! I'm even trying to get into shell when the phone is booted up and sure I can do that, but I can't su! The binary isn't installed. So, what now I have to f'ing install a different ROM, s-on it and then ruu again????
So I f'ed up and turned S-ON by mistake before I did the commands to clear the bootloader modified messages. And now I can't get S-OFF for the life of me! Sunshine can't get root it says, SuperSU is installed and says a binary needs updating, but when I click on it, it just freezes and won't update the binary. I tried pushing it down via zip/bootloader but that doesn't help. I ran a root checker and it says my phone is rooted, but nothing is working like I expect it to.
I'm still running the stock ROM from the RUU, could that be the issue? Do I have to install a different ROM before I can S-OFF and then RUU again? This is such a pain!!!
ned4spd8874 said:
So I f'ed up and turned S-ON by mistake before I did the commands to clear the bootloader modified messages. And now I can't get S-OFF for the life of me! Sunshine can't get root it says, SuperSU is installed and says a binary needs updating, but when I click on it, it just freezes and won't update the binary. I tried pushing it down via zip/bootloader but that doesn't help. I ran a root checker and it says my phone is rooted, but nothing is working like I expect it to.
I'm still running the stock ROM from the RUU, could that be the issue? Do I have to install a different ROM before I can S-OFF and then RUU again? This is such a pain!!!
Click to expand...
Click to collapse
If you are still bootloader unlocked, install TWRP, restore an appropriate nandroid backup for your device, root that install, and re-run Sunshine.
If you are bootloader locked, restart the phone into bootloader mode and select the RUU option. Then, re-run the RUU. If your bootloader is locked, it should run and restore everything to stock. Note that if you updated to Lollipop, you may have to use Kingroot to get temp root. I meant to suggest you RUU down to the original version (4.4.2) prior to going S-on and forgot - sorry about that.
jshamlet said:
If you are still bootloader unlocked, install TWRP, restore an appropriate nandroid backup for your device, root that install, and re-run Sunshine.
If you are bootloader locked, restart the phone into bootloader mode and select the RUU option. Then, re-run the RUU. If your bootloader is locked, it should run and restore everything to stock. Note that if you updated to Lollipop, you may have to use Kingroot to get temp root. I meant to suggest you RUU down to the original version (4.4.2) prior to going S-on and forgot - sorry about that.
Click to expand...
Click to collapse
Bootloader is still unlocked, but even after installing a couple different ROMs, sunshine just won't work. Says it's incompatible. It says to flash a stock sense or near stock rom. I'm on SkyDragon right now...
I'm at a loss. Anyone have a industrial shredder?
ned4spd8874 said:
Bootloader is still unlocked, but even after installing a couple different ROMs, sunshine just won't work. Says it's incompatible. It says to flash a stock sense or near stock rom. I'm on SkyDragon right now...
I'm at a loss. Anyone have a industrial shredder?
Click to expand...
Click to collapse
There are probably some T-mobile nandroid backups around here somewhere. Get one, put it on an SD card, and use TWRP to flash it. Unfortunately, I only have DevEd and AT&T images.
jshamlet said:
There are probably some T-mobile nandroid backups around here somewhere. Get one, put it on an SD card, and use TWRP to flash it. Unfortunately, I only have DevEd and AT&T images.
Click to expand...
Click to collapse
Things are looking up! Found a ROM called something like Alex V that was stock enough to get SunShine to work. Also, I was using the original version so once I got it to run, it was giving network errors. Once I installed the latest version, that's when I got was able to go S-OFF. So, now I'm S-OFF, the bootloader is saying Official and locked so now I'm going to RUU and throw it in TMO's face!

Categories

Resources