I got this phone off a friend, and I have a opportunity to trade my M8 for a M9 plus cash. The problem is that the guy won't trade without the phone being completely stock with no root or any signs.
I've searched quite a bit on this forum for answers and everything is for older versions of Android. I can't find what RUU I would need or if it's even available. I seen a guide and tutorial from theunlckr, but it's from mid 2014.
I'm looking for a complete guide from start to end that will put this phone back to stock. This would be my first time and I don't know jack about what to do when it comes to this stuff. I'm very computer savvy so it shouldn't be a issue.
The info is following when I boot into recovery:
First off, the HTC logo will appear saying it's property of HTC and something about developers in red.
Software Status : Modified
Unlocked
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.0000
[email protected]
OPENDSP-v47.2.2-00564-M8974_FO.1024
OS-4.28.502.1
eMMC-boot 2048MB
4/20/15
There is also a Team Win application or recovery when I choose to do a factory reset.
Please if someone can help, I need to do this soon.
rlockwich said:
I've searched quite a bit on this forum for answers and everything is for older versions of Android. I can't find what RUU I would need or if it's even available.
Click to expand...
Click to collapse
You want the Lollipop (Android 5.0.2) AT&T RUU (software number 4.28) which is linked on my Index thread at the top of the General AT&T M8 forum section: http://forum.xda-developers.com/showthread.php?t=2751432
Relock the bootloader (command: fastboot oem lock) then just run the RUU (Windows executable).
rlockwich said:
I got this phone off a friend, and I have a opportunity to trade my M8 for a M9 plus cash. The problem is that the guy won't trade without the phone being completely stock with no root or any signs.
Click to expand...
Click to collapse
What "completely" stock means is a bit complicated (and may vary depending on the person). You can relock the bootloader and run the RUU. Everything will be stock, except that the phone will say RELOCKED in bootloader instead of UNLOCKED (which is the factory condition).
The only way to make it say LOCKED is to s-off by sunshine ($25) then change the flag to LOCKED. Then go back to s-on. But IMO, its not worthwhile to spend money to sell/trade a phone; and not worth the money, time and effort for something that is very minor.
Functionally, there is no difference between RELOCKED and LOCKED. The only reason anyone would care, is if they want to make a warranty claim with HTC. In that case, they may deny any claim anyway, since there is already a record of the bootloader being unlocked via HTCDev.com (tracked by the phone's IMEI). Not even sure if the warranty (1 year from purchase) would be valid, anyway for a device that has changed hands 2 times.
I would recommend you ask the buy/trade partner if RELOCKED bootloader is okay. Otherwise, find someone else to trade with.
rlockwich said:
First off, the HTC logo will appear saying it's property of HTC and something about developers in red.
Click to expand...
Click to collapse
This, and TWRP recovery will be gone once you RUU.
RUU will re-image the entire phone to stock factory (Lollipop) condition. So it will be stock ROM, stock recovery, no root, etc.
You should also remove your SD card (if one is inserted), then go into phone settings and wipe all storage, to make sure the internal storage/virtual SD is wiped of your personal data.
Will this make him be able to do OTA updates for when 5.1 comes?
rlockwich said:
Will this make him be able to do OTA updates for when 5.1 comes?
Click to expand...
Click to collapse
Yes. The only requirements for OTA are stock ROM and stock recovery, which post-RUU state satisfies both.
Note that OTA updates for the AT&T version are only available when connected to AT&T's network. So if the buyer is asking if he will get OTAs, and he happens to be using another carrier, the answer is NO. And in that case, the RUU for the next update is his best option.
It was a success! Thank you for taking the time to help me out. I really appreciate everything you've done!
Do you think it's necessary to wipe from the settings in backup/restore after doing the RUU?
I read somewhere that there are files left behind from the root, after unrooting....does the RUU wipe all of this away, so there won't be a need to do a 2nd reset after the RUU completes?
rlockwich said:
Do you think it's necessary to wipe from the settings in backup/restore after doing the RUU?
I read somewhere that there are files left behind from the root, after unrooting....does the RUU wipe all of this away, so there won't be a need to do a 2nd reset after the RUU completes?
Click to expand...
Click to collapse
Can never remember for certain; but I think RUU just wipes user data, and normally leaves internal storage intact. Not just files used for root, but personal files, too. So you will want to make sure internal storage is wiped.
Therefore, I do recommend going to Backup & Reset in Settings, pick Reset phone in order to make sure internal storage is wiped.
Related
Hey guys. Need a big hand here. So I have a HTC One on contract from Three in the UK.
I rooted the phone and all that jazz and decided on putting a custom ROM on my device.
However while in TWRP I wiped the phone and seemingly all the contents on it, including TWRP.
Now I have a bricked phone that boots into recovery/ the bootloader only. I've tried flasing
RUU files on but it fails with the error code 140? I don't know much about this I'm quite a noob.
In recovery the information is as follows:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_UL PVT SHIP S-ON RH
HBOOT- 1.54.0000
RADIO-4A. 17. 3250. 14
OpenDSP-v31.120.274.0617
OS-2.24.401.0
eMMC-boot 2048MB
Please help me. I've read through wonderful guides by other patrons on this website but nothing seems to work.
I'm at my wits end.
Thank you in advance for any help.
I know very little about this, but just to brainstorm (and confirm a few basic facts):
When you rooted originally, did you use HTC's bootloader unlocker or a different method to unlock the bootloader?
How are you flashing ROMS? Are you doing everything through the phone (example, using one-touch-root apps) or are you using the Android Debug Bridge?
The bootloader typically comes with options to reboot, boot into recovery, factory reset, etc. Can you confirm that these options have disappeared (or never existed in the first place)?
My knee-jerk reaction is that you didn't use an HTC bootloader unlocker and, therefore, the HTC GUU detects a bootloader mismatch and aborts. Therefore, you need to see if there's a way to flash a stock HTC bootloader (which, I can tell you from experience, is usually a one-way-trip to super-bricking) or see if the bootloader you already have installed can be unlocked through the ADB.
In my very limited experience and understanding of Android, it's generally pretty difficult to wipe the recovery partition from within the phone - one generally as to flash it from ADB or screw with the bootloader in some way to wipe it. I wonder, therefore, whether the recovery partition is just fine but maybe the bootloader is throwing a fit because it's not the HTC default.
I'm sure you've tried or thought of all of this, but since nobody else is stepping up, I thought I'd help brainstorm a bit and keep the thread fresh.
Borden Rhodes said:
I know very little about this, but just to brainstorm (and confirm a few basic facts):
When you rooted originally, did you use HTC's bootloader unlocker or a different method to unlock the bootloader?
How are you flashing ROMS? Are you doing everything through the phone (example, using one-touch-root apps) or are you using the Android Debug Bridge?
The bootloader typically comes with options to reboot, boot into recovery, factory reset, etc. Can you confirm that these options have disappeared (or never existed in the first place)?
My knee-jerk reaction is that you didn't use an HTC bootloader unlocker and, therefore, the HTC GUU detects a bootloader mismatch and aborts. Therefore, you need to see if there's a way to flash a stock HTC bootloader (which, I can tell you from experience, is usually a one-way-trip to super-bricking) or see if the bootloader you already have installed can be unlocked through the ADB.
In my very limited experience and understanding of Android, it's generally pretty difficult to wipe the recovery partition from within the phone - one generally as to flash it from ADB or screw with the bootloader in some way to wipe it. I wonder, therefore, whether the recovery partition is just fine but maybe the bootloader is throwing a fit because it's not the HTC default.
I'm sure you've tried or thought of all of this, but since nobody else is stepping up, I thought I'd help brainstorm a bit and keep the thread fresh.
Click to expand...
Click to collapse
I unlocked the bootloader originally by getting a specific code from HTC and using it through the command prompt I think. I can go into the bootloader and it has all the fastboot, recovery, factory reset business there. Trying factory reset does nothing. I've downloaded HTC toolkit 2.2 and I tried initially pushing ROMS to flash to TWRP, but it would never detect my phone. Then I stupidly did a full wipe through TWRP and now that's disappeared. All that's left is the bootloader now. I've tried forcing RUU updates through the HTC toolkit but it always fails. So does running the normal RUU process. I can't seem to find the correct one for Three UK. The most I've been able to do is re-lock the bootloader and I'm running out of ideas. Thank you for your reply. I feel so helpless!.
If I've read your message correctly, you are doing everything through the HTC toolkit and not through the Android SDK. Frankly, I don't know how the former works. Especially if the HTC Toolkit isn't detecting your phone, you may want to run over to http://developer.android.com/sdk/ and fetch the SDK for your system and set it up. You don't need the ADT Bundle, just the SDK Tools link at the bottom. This may make it easier for other, more knowledgeable people debug your phone, since they all use the SDK. The weaponry you'll be using is all in the <sdk install location>/tools directory, so get a command prompt window pointed there (by the by, are you using Windows, Mac or Linux?)
If you already have your SDK up, or once you do, you'll want to get familiar with the fastboot command, described in this post: forum.xda-developers.com/showthread.php?t=2277112 . What we want to do is see whether we can flash a new recovery ROM.
As long as you don't attempt to flash over the bootloader, you shouldn't super-brick your phone. Based on the message in your original post, your bootloader may have relocked itself. If your first attempt at installing a new recovery ROM doesn't work, then you'll have to use the procedure you used originally to unlock your bootloader. If you've forgotten how to do that, then these instructions (which assume you're using the SDK) should help: http://wiki.cyanogenmod.org/w/Install_CM_for_m7.
You're currently using TWRP, which I've personally found buggy. Until you have a functioning phone again, you may want to use ClockworkMod (CWM) Recovery instead: http://www.clockworkmod.com/rommanager. It has fewer features, but at least they work properly. If flashing ROMs over fastboot is new to you, there are plenty of guides on the Interwebs to help you. I'll also try to walk you through it if you let me know where you're getting stuck. The critical thing, considering that there are many types of HTC One, is to make sure that you flash the ROM that exactly matches your phone. If you flash the wrong ROM, you probably won't break your phone any more than it is, but let's try not to test that theory. If you're not positive which phone you have, say so and we'll help you find out.
Let us know once you have CWM on your phone or where you got stuck. The advantage of using the SDK, too, is that you can copy and paste the output right back to the forum.
I hope I understood everything correctly. Let me know if I haven't.
I recently unlocked my bootloader and rooted my phone. I installed TWRP and flashed a couple of custom roms ( GPE & Revolution HD ) I decided i want to go back to stock. I understand so far i gotta unroot, flash stock rom and re lock bootloader. I read something about RUU files. Any one have suggestion or help how i go about this? Again, i have AT&T varient, currently on Revolution HD Rom
Famous22 said:
I recently unlocked my bootloader and rooted my phone. I installed TWRP and flashed a couple of custom roms ( GPE & Revolution HD ) I decided i want to go back to stock. I understand so far i gotta unroot, flash stock rom and re lock bootloader. I read something about RUU files. Any one have suggestion or help how i go about this? Again, i have AT&T varient, currently on Revolution HD Rom
Click to expand...
Click to collapse
There is currently no RUU available as of right now. I think the best you can do for now is to a TWRP restore. There is a stock rooted TWRP in the Android Dev forum. Although this won't un-root you, its closest to stock that you will get. For the future, always make a backup before you root and then you won't have to worry
TheEmpyre said:
There is currently no RUU available as of right now. I think the best you can do for now is to a TWRP restore. There is a stock rooted TWRP in the Android Dev forum. Although this won't un-root you, its closest to stock that you will get. For the future, always make a backup before you root and then you won't have to worry
Click to expand...
Click to collapse
I just ordered my device and still waiting on it to be delivered. I'm already debating on whether or not to root as I've never owned an android phone that i didn't root. From what i understand, the bootloader needs to be unlocked, then s-off, flash recovery and then root. Now, if i'm to do a nandroid of the stock ROM before I root, will I be able to lock the bootloader again, nandroid and s-on in case I need to utilize the warranty? Also, will any warranty bits show up or a tampered flag or any other problem arise that'll indicate it's been farked with? Is there a way to undo those flags? Thanks in advance to TheEmpyre or whomever else can shed some light on this.
EDIT: If the s-off is the only step that will trip the flag, is it possible to leave S, er, ON?
brianray14 said:
I just ordered my device and still waiting on it to be delivered. I'm already debating on whether or not to root as I've never owned an android phone that i didn't root. From what i understand, the bootloader needs to be unlocked, then s-off, flash recovery and then root. Now, if i'm to do a nandroid of the stock ROM before I root, will I be able to lock the bootloader again, nandroid and s-on in case I need to utilize the warranty? Also, will any warranty bits show up or a tampered flag or any other problem arise that'll indicate it's been farked with? Is there a way to undo those flags? Thanks in advance to TheEmpyre or whomever else can shed some light on this.
EDIT: If the s-off is the only step that will trip the flag, is it possible to leave S, er, ON?
Click to expand...
Click to collapse
Unlocking the bootloader trips a flag. When you relock it gets rid of one flag but trips the relocked flag. Soff can get rid of all flags but you have to leave it soff. Turning it back on throws a security flag.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
If you are current AT&T customer, and can go through them for warranty, they do not care in the least whether you are bootloader unlocked, rooted, s-off, etc.
I know AT&T written policy says otherwise (they have the right refuse warranty on modded phones) but in reality they cherish you paying that nice monthly bill every month over the modest cost of a refurb phone.
I've come over from the One X (EVITA) forum, and there were many (possibly dozens) of report from XDA users successfully returning their devices for warranty with bootloader RELOCKED, UNLOCKED, and in some cases even with custom ROMs installed! And I haven't seen any reports otherwise (AT&T denying warranty due to modded phone).
If you are not a current AT&T customer, and have to go through HTC, that is a different story.
But if you are an AT&T customer, my personal opinion is that you do not need to care about being able to return to stock, tripping flags, etc. Just mod away.
redpoint73 said:
If you are current AT&T customer, and can go through them for warranty, they do not care in the least whether you are bootloader unlocked, rooted, s-off, etc.
I know AT&T written policy says otherwise (they have the right refuse warranty on modded phones) but in reality they cherish you paying that nice monthly bill every month over the modest cost of a refurb phone.
I've come over from the One X (EVITA) forum, and there were many (possibly dozens) of report from XDA users successfully returning their devices for warranty with bootloader RELOCKED, UNLOCKED, and in some cases even with custom ROMs installed! And I haven't seen any reports otherwise (AT&T denying warranty due to modded phone).
If you are not a current AT&T customer, and have to go through HTC, that is a different story.
But if you are an AT&T customer, my personal opinion is that you do not need to care about being able to return to stock, tripping flags, etc. Just mod away.
Click to expand...
Click to collapse
I can second this. I just had to replace my m8 because the speakers were crackling like crazy, my bootloader showed relocked and they told me straight up that they didn't care about that as long as it was a hardware problem and not a software problem and replaced it on the spot.
I was under the impression that if you were in your first year of owning the device that faulty hardware would be covered under HTC's factory warranty and not AT&T?
brianray14 said:
I was under the impression that if you were in your first year of owning the device that faulty hardware would be covered under HTC's factory warranty and not AT&T?
Click to expand...
Click to collapse
Looking at the return info, I can see where the confusion might come from. It says "Return directly to manufacturer" for 15 days or more:
http://www.att.com/shop/wireless/returnpolicy.html#fbid=KMGdewZyG_f
But AFAIK, all warranty returns go to AT&T when you work through their warranty department. You send them your defective phone, and they send you a refurb. I haven't had to go through this process myself, but this is what has been reported many times on XDA and other forums.
Any update on this how to lock bootloader for HTC M8 AT&T with 4.4.3 InsertCoin 4.1.1 Rom S-On of course.
How do I lock the bootloader in order to upgrade to stock 4.4.4?
im2c0ol said:
Any update on this how to lock bootloader for HTC M8 AT&T with 4.4.3 InsertCoin 4.1.1 Rom S-On of course.
How do I lock the bootloader in order to upgrade to stock 4.4.4?
Click to expand...
Click to collapse
No "update" on this issue is required. The process has been the same for a couple years or more. Further, you've posted the same/similar question to multiple places, and its been answered already in multiple places.
Connect phone to computer in fastboot mode.
Open command prompt, and type: fastboot OEM lock
From there, you can run the RUU.
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
Good evening,
I am reaching out to all developers and android enthusiasts here on XDA as I am completely stuck at this point. This post may get a little bit long winded but I wouldn't post if I didn't legitimately need the assistance.
So here is my situation. I have an ATT HTC ONE and I originally rooted this phone thinking that it would improve the devices battery life as I've experienced with any other android device that I've rooted. All my Samsung devices respond miraculously to rooting and couldn't imagine not having a rooted android. Well after a few short weeks I found myself in need of unrooting the device and restoring back to stock(for personal reasons). Upon attempting to relock the bootloader and then reflash stock firmware back to the device I was successful at getting the bootloader relocked but somehow managed to completely delete all;the System partition on the device. I CAN still however boot the phone into the bootloader(into fastboot,recovery, etc) I have TWRP recovery installed on the device but now the phone says that its got 0mb of storage on the phone. Ive spent countless hours trying to figure out how to get the phones original firmware back on the device with absolutely no luck. My current Hboot version is 1.55 and i have S-ON as well. Can someone point me in the direction of a thread where I can some how recreate the system(and other neccessary partitions) to restore the firmware?? Does HTC have anything like KIES that Samsung has where i can reflash my phone?
COrootking4life said:
Good evening,
I am reaching out to all developers and android enthusiasts here on XDA as I am completely stuck at this point. This post may get a little bit long winded but I wouldn't post if I didn't legitimately need the assistance.
So here is my situation. I have an ATT HTC ONE and I originally rooted this phone thinking that it would improve the devices battery life as I've experienced with any other android device that I've rooted. All my Samsung devices respond miraculously to rooting and couldn't imagine not having a rooted android. Well after a few short weeks I found myself in need of unrooting the device and restoring back to stock(for personal reasons). Upon attempting to relock the bootloader and then reflash stock firmware back to the device I was successful at getting the bootloader relocked but somehow managed to completely delete all;the System partition on the device. I CAN still however boot the phone into the bootloader(into fastboot,recovery, etc) I have TWRP recovery installed on the device but now the phone says that its got 0mb of storage on the phone. Ive spent countless hours trying to figure out how to get the phones original firmware back on the device with absolutely no luck. My current Hboot version is 1.55 and i have S-ON as well. Can someone point me in the direction of a thread where I can some how recreate the system(and other neccessary partitions) to restore the firmware?? Does HTC have anything like KIES that Samsung has where i can reflash my phone?
Click to expand...
Click to collapse
Yes HTC has a RUU (Rom Update Utility) You posted in the AT&T forums so I'm going to assume you need the AT&T RUU
You can download it directly from HTC Here
The RUU requires s-off or Relocked bootloader
you relock it with this command
fastboot oem lock
fastboot reboot-bootloader
I've tried that before the ruh fails BC the phone shows no operating system. I've tried several different ones. The one thing that I see in relation to all the ruu threads all say you should see a os version in the current field and in dont. Unless there's some other order of operations Im not aware of when trying to use them.
Sent from my GT-N7105 using XDA Free mobile app
I've solved this without an RUU. I will post a "SOLVED" thread in the development page.
Sorry for the delay folks
COrootking4life said:
Good evening,
I am reaching out to all developers and android enthusiasts here on XDA as I am completely stuck at this point. This post may get a little bit long winded but I wouldn't post if I didn't legitimately need the assistance.
So here is my situation. I have an ATT HTC ONE and I originally rooted this phone thinking that it would improve the devices battery life as I've experienced with any other android device that I've rooted. All my Samsung devices respond miraculously to rooting and couldn't imagine not having a rooted android. Well after a few short weeks I found myself in need of unrooting the device and restoring back to stock(for personal reasons). Upon attempting to relock the bootloader and then reflash stock firmware back to the device I was successful at getting the bootloader relocked but somehow managed to completely delete all;the System partition on the device. I CAN still however boot the phone into the bootloader(into fastboot,recovery, etc) I have TWRP recovery installed on the device but now the phone says that its got 0mb of storage on the phone. Ive spent countless hours trying to figure out how to get the phones original firmware back on the device with absolutely no luck. My current Hboot version is 1.55 and i have S-ON as well. Can someone point me in the direction of a thread where I can some how recreate the system(and other neccessary partitions) to restore the firmware?? Does HTC have anything like KIES that Samsung has where i can reflash my phone?
Click to expand...
Click to collapse
Sorry for the sluggish delay, due to some scheduling conflicts and other hurdles came into play but nevertheless Im posting my solved post now. head over to the ATT HTC ONE ANDROID DEVELOPMENT FORUM TO FIND THE POST LABELED "SOLVED"
Software up to date issue
HI all, just got this M8 and it is an ATT Version. but I believe it is unlocked because I am using it with cricket.
When trying to update Android Tells me software is up to date ?
Android version 5.0.2
HTC Sense Version 6.0
Software Number 4.28.502.1
HTC SDK API Level
I am pretty sure that ATT has updated to Marshmallow by now / So why can't I update? I am on wifi and 4G/LTE Could it be because I am using a Cricket Sim Card in the Phone ?
I have downloaded the RUU for Marshmallow software version 6.20.502.5. Should I continue with the Manual update ?
I believe this phone was originally purchased from ATT on May of 2016 if it makes any difference , figured I post it. since it could be a newer version of HTC M8.
Also is there a way to back up my current stock rom, without Rooting phone ? Thanks for all your help.
As I cannot root my phone, because when I go into developer option and search for S-off That option is not there and I can't Continue.
My responses below in red font:
ELEVO said:
HI all, just got this M8 and it is an ATT Version. but I believe it is unlocked because I am using it with cricket.
When trying to update Android Tells me software is up to date ?
I am pretty sure that ATT has updated to Marshmallow by now / So why can't I update? I am on wifi and 4G/LTE Could it be because I am using a Cricket Sim Card in the Phone ?
That is correct, the AT&t version (and most US versions) can only OTA update if connected to the proper branded carrier (AT&T in this case). Therefore, the RUU is your best option to update.
I have downloaded the RUU for Marshmallow software version 6.20.502.5. Should I continue with the Manual update ?
You can. But you need to flash the 6.20.502.5 firmware first, before you can flash the RUU. See instructions to flash the firmware here: https://forum.xda-developers.com/showpost.php?p=67123738&postcount=7
Then run the RUU. Keep in mind, that RUU will wipe the phone. So backup your data to an off-phone location (cloud, computer, etc.) before RUU.
Also is there a way to back up my current stock rom, without Rooting phone ? The current Lollipop ROM? No, there will be no way to revert to LP by official means, once you RUU to Marshmallow. I doubt you will find the need or desire to "downgrade" to obsolete LP version. If for some reason you did want to, there are options, but would require unlocking the bootloader (to install custom recovery and flash a Lollipop ROM), or s-off (which would allow you to "downgrade" by RUU - which is not allowed with s-on).
As I cannot root my phone, because when I go into developer option and search for S-off That option is not there and I can't Continue.
You are misunderstanding a couple things:
1) s-off is not a setting in Developer Options. s-off can only be obtained with sunshine app ($25)
2) You don't need s-off to root this device. Simply unlock the bootloader, install TWRP, and flash SuperSU to root
Click to expand...
Click to collapse
Detailed
redpoint73 said:
My responses below in red font:
Click to expand...
Click to collapse
Thanks for the detailed reply, really helpful and greatly appreciated :good:
Two more Questions, Can I upgrade to an official DEV Edition RUU on this ATT Device? or would I have to use a Custom Dev ROM ? as I am trying to Tether with my phone, just like my official Developer HTC M8 I purchased in 2014 , Seems AT&T phone wont allow me to Tether ?
Also once I flash firmware and upgrade to official RUU will need to Unlock and Root Loader? Will doing upgrading to official Marshmallow Relock bootloader and Un Root Phone ? Back to Stock ? Thanks again, I will be attempting this pretty soon. Thanks again
For the Record, I have made a back up of my Lollipop via TWRK. I also backed it up using Titanium back up, just in case.
Again, my responses in red font:
ELEVO said:
Thanks for the detailed reply, really helpful and greatly appreciated :good:
You're welcome. Always happy to help!
Two more Questions, Can I upgrade to an official DEV Edition RUU on this ATT Device?
You can't flash the Dev Edition RUU with s-on. Even though the versions are very similar (same model ID - MID) the two versions have different carrier ID (CID). Wrong carrier ID will make the Dev Ed RUU fail, by definition. And the only way to change CID is with s-off. Further, its not really necessary to flash the Dev Ed RUU (and not worth spending money of s-off) to accomplish what you want (see more below)
or would I have to use a Custom Dev ROM ? as I am trying to Tether with my phone, just like my official Developer HTC M8 I purchased in 2014 , Seems AT&T phone wont allow me to Tether ?
Its correct that the AT&T stock ROM disables tethering. Flashing most custom ROMs (or the Dev Ed ROM) will enable tethering - as well as remove annoying AT&T branding and bloat apps. Flashing the Dev Ed RUU is not necessary to accomplish this.
Also once I flash firmware and upgrade to official RUU will need to Unlock and Root Loader? Will doing upgrading to official Marshmallow Relock bootloader and Un Root Phone ? Back to Stock ? Thanks again, I will be attempting this pretty soon. Thanks again
You need to relock the bootloader in order to flash firmware and RUU (command: fastboot oem lock). Once the RUU is complete, the phone will be on a fully stock "factory" image. So you will be unrooted. You will also be back to stock recovery (no longer have TWRP installed). From there, what you want to do:
1) Unlock the bootloader again. Either use the same unlock bin code you used to unlock BL before. Or get a new code from HTCDev.com
2) Flash TWRP back to the phone with fastboot. TWRP 3.0.2 is recommended for compatibility with MM firmware.
3) Flash the desired custom ROM. The custom ROM will be rooted (if you flash the Dev Ed ROM, you can select root in the AROMA installer).
For the Record, I have made a back up of my Lollipop via TWRK. I also backed it up using Titanium back up, just in case.
Always good to make backups. Although be aware, that RUU will wipe the phone, including internal storage. So if you picked internal storage as your backup location, you'll want to move/copy to another location (removable SD is okay, otherwise to computer or cloud).
Also note that restoring app data (as well as call logs, SMS) using Titanium, after RUU or ROM flash should be okay. But don't restore any system data, as this can cause problems.
Click to expand...
Click to collapse
redpoint73 said:
Again, my responses in red font:
Click to expand...
Click to collapse
Ok i came back to this old post. I forgot all about it, it really is helping me alot.
My questioin is after i Relock the bootloader can i do a factory wipe? will this remove everything from my phone and bring it back to stock?
I relocked my phone, but all my apps and contacts are their.
Bricked ?
ELEVO said:
Ok i came back to this old post. I forgot all about it, it really is helping me alot.
My questioin is after i Relock the bootloader can i do a factory wipe? will this remove everything from my phone and bring it back to stock?
I relocked my phone, but all my apps and contacts are their.
Click to expand...
Click to collapse
I think i may have bricked my phone? I went and installed an RUU firmware file for Marshmallow as most instruct to do via Fastboot. All went well, installation completed and i was able to send command to phone to reboot. when it tried to reboot. white screen with HTC Comes on and then goes almost black with a very light dark grey background.
Phone would not reboot into anything but dark screen. even when i restarted it with power button. the only thing that worked for me, was Holding Down Power/Volume and quickly hit the volume down button before device would vibrate to reboot, that took me into recovery. Below is what i see in Recovery.
Phone now has new software
***RELOCKED***
m8_UL_CA PVT SHIP S-ON
HBOOT-3.1.0.0000
RADIO-4.0 [email protected]
OpenDSP-V56.2.2-00593-M8974_FO.0126
0S-6.20.502.5
eMMC-boot 2048MB
APR 14 2016,19:39:46.0
HBOOT
<Vol UP> to previous item
<Vol Down> to next item
<Power> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
I was able to run and "IMAGE CRC" via boot loader. it gave me alot of numbers after calculating. not sure if that is a good sign ?
Things I've tried in Recovery.
1. Recovery goes back to black screen.
2. SHOW BARCODE Works- 3 bar codes showed up.
3. Fastboot works. but when i try command "adb devices" it says list of devices attached. but nothing shows up
4. Tried to do a factory reset and tries to do it, then a black phone pops up on screen with green arrow sgoing in circles for like 10 seconds. then reboots to dark screen.
Please Help :crying: Thanks
Can anyone help me with this? I bought the phone with me on vacation and now using an HTC Developer Edition that the button down doesn't work and Volume down button us sunk in But at least i have my phone with all my contacts and apps , For now ?
I would like to know if i can unbrick my other HTC . Thanks.
Late in responding, as I was on work travel myself, and not on XDA for over a week.
ELEVO said:
I think i may have bricked my phone?
Click to expand...
Click to collapse
It's basically impossible for you to do anything with an s-on M8 that will actually brick it. That is the good thing about s-on.
ELEVO said:
I went and installed an RUU firmware file for Marshmallow as most instruct to do via Fastboot. All went well, installation completed and i was able to send command to phone to reboot. when it tried to reboot. white screen with HTC Comes on and then goes almost black with a very light dark grey background.
Click to expand...
Click to collapse
I think you only flashed the firmware.zip and not the RUU. Based on the condition here, and your other thread you created here: https://forum.xda-developers.com/htc-one-m8/help/htc-one-e-m8-fastboot-issues-t3757628
I clearly described above to flash the firmware.zip then the RUU. They are 2 completely different things. Firmware is about 80 MB and only contains hboot, radio, and a few other things. RUU is a full image that is 1.5 GB.
No boot after flashing signed firmware is normal, as it expects the RUU to be run afterwards.
ELEVO said:
Fastboot works. but when i try command "adb devices" it says list of devices attached. but nothing shows up
Click to expand...
Click to collapse
adb doesn't work in fastboot mode. Only fastboot commands will work in fastboot mode. You can only use adb when booted to OS (not an option for you, obviously) or alternately in custom recovery TWRP. So what you describe (adb not working) is normal and expected.
However, fastboot is enough to get the phone working from the described condition.