How to upgrade ATT HTC ONE M7 without losing root
Hello all, I have an AT&T HTC ONE M7 that is currently running Android 4.4.2 with HTC Sense 6.0 (software # 5.03.651.3). I have rooted it with TWRP and SuperSU and need some guidance to update my phone without losing the root (or unroot/upgrade/re-root). Can't seem to find anything. I want to stick with the factory ROM ideally, but would be happy to take a look at any other that is comparable. Not looking for added capability, just want to get my phone up to date.
Thanks in advance!!
Signaldog
I'm not an expert on these things, so hopefully someone will correct me if I'm wrong, but isn't software # x.xx.651.x for Sprint devices? The AT&T factory software is x.xx.502.x. So either you don't have an AT&T version of the M7 or you're not running the factory ROM. It's definitely not the AT&T factory ROM.
But to answer you question, since you're already rooted with a custom recovery, there probably has been enough changes to the system that will prevent the OTA's from installing, even if you reflash stock recovery. And if you are in fact running the Sprint ROM while on the AT&T network, you probably wouldn't get the OTA's anyway. So in order to get the latest updates you'll need to flash a ROM clean. Since you want to stay factory stock, that means the RUU, which you can download directly from HTC. You'd definitely want to confirm which variant of the M7 you have and make sure you get the right RUU. Pretty sure the AT&T RUU won't flash to a Sprint branded device unless you're S-Off w/ Super CID. And there may be some other incompatibilities in this situation. You may want to look into custom roms at this point.
However, once the RUU is complete and the clean ROM is up and running, it's a simple process of flashing TWRP and installing SuperSU to root.
You'll then need to spend time setting up all your apps and customizing everything to your liking, so make sure to set aside a block of time to do that. And be sure to backup any personal files onto your computer before running the RUU. It will wipe the sdcard.
So, yes, as it turns out, my brain was not working correctly and I do indeed have a SPRINT M7, not an AT&T one. I'm not sure why I confused that. Regardless, thanks for the help, sounds like I can do what I need to do without any significant risks, minus the time involved.
Thanks.
Related
Okay, so I ordered a USED Thunderbolt on ebay last week and it should be here tomorrow. I'm not entirely new to rooting and such as I have a droid 2 global now, but that's motorola which seems to be fairly different from HTC. Anyway I've been reading threads and have come up with a few questions.
For instance if my phone is rooted when I get it, how can I get back to stock. I won't know how it was rooted, and some guides say it matters, while others don't. Plus many guides say not to just flash an RUU over a rooted phone, but if it replaces the bootloader, radio, and system, why not. Isn't that basically like an SBF on a motorola phone? Can I then also do a data wipe from the hboot bootloader thing on my phone and end up with a perfect stock device without any risk? From what I understand some roots block this entirely on the phone though so maybe I can't. I'm not really sure how to know what is safe to do on a phone that I didn't previously own and would love a guide to how to check these things and what to do so I don't brick the phone.
Also I can't seem to find a functional link to any of the latest radios, does anyone have a working link, and do people recommend the leaked radio from the most recent leaked build, or an official radio? and if so what radio is official? the one ending in 906 seems to be the most recent that I think is official but I'm not sure, though I am almost certain the 916 one isn't official, it appears to have been released in january on rootzwiki, while the most recent leaked build was less than a week ago from what I understand, but I don't know if it has a new radio or not.
Aside from that I think I've got it all down. figure out how to get phone to most recent stock OTA update. get 4g lte sim card, activate, root using this method.
http://rootzwiki.com/topic/20864-tool-root-2116059-and-19-no-downgrade-or-data-wipe/
then if I don't have the most recent radio I can flash it in the hboot thing, and can use cwm to flash any rom I want and a recommended kernel (I'm thinking thundershed 1.5 for starters though wouldn't mind some recommendations. I love Cyanogenmod)
Does this sound about right?
Also I'm not sure how hboot on htc phones works aside from booting on power+vol down button, but does the hboot allow for clearing data and cache as well as flashing things? On my droid 2 global there is a bootloader than can only be used to flash sbf files to get back to stock ota, and then there is a motorola stock recovery on the phone that is used for flashing updated ota updates that are signed or wiping data/cache. Are these the same on htc or are there a 2 different ones on that phone as well? I do understand that no PC is required for the htc as the tool to flash an ruu is built into the phone even if it is an older one than what the phone is currently on right?
I'm trying to return my HTC One back to being unrooted because I wanna update it and almost everywhere I read, you need to unroot to get over the air updates. So I got S-Off and I relocked my bootloader, but whenever I try running the RUU, it always fails. I tried flashing it and I tried running the exe file. Why does it keep failing? Also, is it true you can't get OTA updates while being rooted? The RUU I use is for Cingular (which from my understanding is the one AT&T uses) and I have Super CID. Lastly, if anyone knows an easier way to return my phone to being completely stock and unrooted that would be great. Thanks in advance!
Which RUU did you use? Apparently the last official one was JB 4.3 w/ Sense 5.0, ver. 3.17.502.3. The one for KK4.4.2 w/ Sense 5.0, ver. 4.18.502.7 was apparently not actually released by ATT and many people were having problems with it.
clsA said:
Well near as I can tell the RUU did not originate from HTC, someone was able to create it and sign it same as HTC would. But the files behave differently than the "Real" HTC RUU. The only solution I found was to use the True HTC RUU from 3.xx.502.x and OTA to 4.xx.502.x to 5.xx.502.x. It requires s-off to flash the OTA's so it's not the perfect solution for everyone.
Click to expand...
Click to collapse
So if you tried with the KK4.4.2 RUU, download the JB4.3 RUU from http://www.htc1guru.com/. Since you're S-OFF, you can use either the .exe or the decrypted .zip. I used the decrypted .zip before and it worked fine. Once you get that flashed you can then take the OTAs to update to KK4.4.2 w/ Sense 6. You'll need to be on the AT&T network to get those OTA. Otherwise you'll need to manually flash the updates, as clsA states in his post that I quoted above.
As for not getting OTAs while being rooted....
It's not so much that being rooted prevents getting OTAs. It's the process of getting to root that modifies or deletes system files that need to be intact for the OTA to work. OTA need to be installed through stock recovery. If you're rooted, it's most likely that you have a custom recovery. Also, unlocking the bootloader deletes some files the OTA checks for. If those files not there, the OTA will not install.
Flashing an RUU is the easiest way to get completely stock. It resets the phone to an out-of-the-box state. Whereas a factory reset done from bootloader or recovery basically just wipes the data partition, which will remove any apps you installed and user data. But any modifications to the system partition that are done remain. You don't get back the files that are deleted when you unlocked the bootloader.
Also, since you are S-OFF, there's no need to relock your bootloader to run an RUU. That's only required if you're S-ON. And once you get S-OFF, there is no reason to go back to S-ON.
Since I just want to get the new OTA update, do you recommend I just flash the update as opposed to going back to stock recovery because I don't mind having a rooted phone? Also, my phones camera suddenly became blurry, is it possible that the rooting had something to do with it? If it did, would flashing the OTA update fix it or would I need to go back to stock recovery or would neither fix it? Sorry for so many questions.
First off, what version is currently on your phone? Depending on where you're currently at you may need to flash more than one update in order to get it to the latest version. And no matter what, you'll need to flash stock recovery in order for the updates to flash. OTA updates, whether taken OTA or flashed manually, require stock recovery, as I mentioned before. Also, again as I mentioned before, the process of rooting your phone (more specifically, the process of unlocking your bootloader) most likely deleted files from your system partition that need to be in place in order for the OTA updates to install. If they are not there, the update will fail. So to answer your question...No, I don't recommend "just flash the update as opposed to going back to stock recovery". It won't work.
Since you didn't answer my question and state which RUU you tried, I don't know if you tried a bad 4.4.2 RUU or if there are other issues with your device and/or computer that's preventing any RUU from installing. If you just don't want to flash the RUU, then you can try flashing the update in the phone's current state and when it fails, you can analyze the error report, try to track down stock versions of the files you're missing and restore them if you find them, then try the update again, hoping you found everything. That's a lot more of a hassle than just flashing the RUU, flashing the updates, rooting, and setting up your phone.
Another option is to just flash a custom ROM. Most of them will bring the phone up to the latest version. Some will even take it higher than what is officially available from AT&T.
As for your camera problem, can't see how just rooting would cause that, but maybe it did. Without knowing the cause of the issue, I can't say if just flashing the OTA would fix it. If it's a software issue, then possibly it would. If it's a hardware issue, then probably not. Focus on updating the phone and worry about the camera issue if it still persists once updated.
Sorry, I forgot about your question. First of all, I got it working using RUU Zip M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3-decrypted. The one that didn't work for me is RUU Zip M7 UL JB 50 Cingular - 1.26.502.12. Second, I am running 4.4.2. Thats for anyone who comes across this and was wondering. Thanks for your help sharksfan7. Also, in case you were wondering, my camera is still blurry, but I'll start a different thread for that.
I just bought a new at&t HTC One (M8) and I'd like to have a fresh stock backup in case of return/warranty problems. I'd like to make this myself so I can ensure that I'll be able to put the exact software that came with my phone back if need be. Also I'd just like to know how to do this in general. What I've found via search has been for rooted phones or different brands. Is it possible to use ADB or any other tool to do this? I guess I'm confused because I see posts for flashing back to stock. How do devs get these stock roms? If someone could point me to a good guide/tutorial it would be much appreciated.
Not without a rooted device or an unsecure [email protected] backup...there is an ruu posted for the 1.58.502.1, thats as close to being a backup without altering the phone in anyway
As long as you are a current account holder, AT&T does not give a crap what software is on your phone, bootloader unlocked, even a custom ROM installed in regards to warranty service based on many reports on XDA.
If you are still wondering about returning to stock, as mentioned in the above, your version (AT&T) if fortunate enough to have a 1.58 RUU. The ROM Update Utility is a useful means of installing a full stock image (ROM, radio, recovery, etc.) via connection to a PC.
But it can still be determined the bootloader is unlocked, no matter what you do to the phone to return it to stock. Your IMEI is tracked by HTCDev.com when you unlock the bootloader. But again, as long as you go through AT&T for warranty service (highly recommended for this reason) they don't care if the phone is modded.
I believe the stock ROMs you mention are system dumps done after bootloader unlock.
Hello. Thanks in advance for your time and advice.
I've got a brand new HTC One M8, AT&T, firmware says 4.4.2 with no available updates.
I want to create an initial backup. I'm a computer technician, and just dabbling in Android, and it's important for me to make a "clone" of my phone before I proceed to wreck things. (This is a replacement phone, the last one had a hardware issue... I swear... I managed to install ViperOne onto it, for a week before the screen faded to white and died.)
I assume I'll need root access to make a proper backup. I also assume I should use Nandroid. I've not used the app before, but I'm sure I can figure it out. As far as root goes, I previously used Hasoon2000's HTC One 2014 (M8) All-In-One Toolkit, which worked well, as far as I could tell. (It's a visual basic program with scripts to download drivers, register at htcdev, get token id, submit it, unlock bootloader, flash recovery, and lots of nice ADB commands. Is this a good option to use? I hear many people use S-Off, but I don't really see a need... ?
So, I assume I'll need a new token ID from HTC, as the previous one I got corresponds to the old, malfunctioning phone.
After it's unlocked, I'd use the toolkit to grant perm root. That would be a great place to be for now. I plan to wait until the 4.4.4 update is pushed, then worry about installing a new rom.
Am I on the right track?
For the AT&T version (and most the major US carrier versions) we are lucky enough to have RUUs. So really, no need to backup the stock configuration. If you like, grab the RUUs and save them to your computer so you have them ready if and when it is needed.
Nandroid isn't a specific app, its just a generic term for a backup made with recovery. The custom recovery is your choice: TWRP, Clockworkmod, Philz.
Just a personal opinion, I would actually strongly recommend against using the toolkit for a couple reasons: most importantly using the toolkit robs you of an important learning opportunity. Doing the steps "manually" is a key way to learning your way around fastboot/adb. Doing the steps manually isn't that hard, and shortcutting the process with the toolkit really doesn't gain you much. Another key issue, is the toolkit introduces an additional point of failure. In fact, I've seen folks have trouble doing some of the steps with the toolkit; where doing the steps "manually" worked without a hitch. And the toolkit hasn't been updated for a long time, and will install an obsolete version of TWRP recovery, which in itself can cause issues.
If you used the toolkit before, you can certainly use it again. This is likely the path of "least" resistance, the the "easy" way to do things. But I wouldn't necessarily call it the "best" way to do it. If you don't already know your way around adb, I would do the steps manually. Since you have a background in computers, you will probably even find the manual process more enjoyable.
Yes, you would need to unlock the bootloader again via HTCDev.com, as the unlock bin code in based on the phone's unique IMEI.
The process would be as simple as unlocking the bootloader using HTCDev.com (very easy, the website is self-explanatory). Use fastboot to install custom recovery. Then to gain root, just flash SU or SuperSU in recovery. If you need a step-by-step guide, there is an excellent one here: http://forum.xda-developers.com/showthread.php?t=2799796
But also be aware that once the 4.4.4 OTA rolls out, you will need to return to stock recovery, and also restore any system files modifed by root, in order to install the OTA.
Thanks, redpoint73
Exactly the answer I was looking for. The guide looks great. Looks like there's a lot of useful information about reverting to stock, too. I guess I'll have a go at it now, as opposed to waiting for the update. Like you say, it's good to know things. Thanks much.
@redpoint73
Now I'm only asking cause I don't know everything. Couldn't those who have S-off just RUU the update once available instead of reverting to complete stock state(no root,no custom recovery, locked Bootlaoder)?
AT&T HTC ONE M8
jball said:
@redpoint73
Now I'm only asking cause I don't know everything. Couldn't those who have S-off just RUU the update once available instead of reverting to complete stock state(no root,no custom recovery, locked Bootlaoder)?
Click to expand...
Click to collapse
Absolutely. In fact S-off is not even required to run an RUU intended for your version (AT&T). If s-on, the added step of relocking the bootloader is all that is needed to run the RUU.
HTC seems to have gotten better about releasing the RUUs promptly. In fact, the previous (ill fated) 4.4.3 update saw the RUU and OTA roll out on the same day. Although this hasn't always been the case. On past devices, the RUUs were not released for weeks (sometimes longer) after the OTA started to roll out. And many folks don't want to wait that long.
Also, relocking the bootloader is not required to OTA, only to RUU.
I've posted in 2 Dev threads, and its like everyone passed right over them w/o any kind of answer of any sorts. What I've included below is a copy of my build.prop I've pulled. If you notice I am on 2.12.1700.1...I ran a ruu to GPE convert, but now that 5.0 is dropping like wildfire. I believe I've come across an issue. You see, I do not have access to a computer so everything I do must be done through my phone or my galaxy tab 4 tablet. I've superCID my device;however, the build.prop line ro.aa.cidlist gibes multiple cid's. These "other" cids don't show in bootloader.
In order to receive OTA..you must be
1. GPE cid (mid-im not sure)
2. On the appropriate firmware
3. Stock recovery
Right now, as it sits I'm on 2.12.1700.1 with philz recovery. I'll make the change to stock when the 5.0 OTA drops...
All I'm trying to figure out is:
Does anyone think I'll have problems based off what my build.prop is displaying ?
I can not change my CID (Unless you/someone knows of a way without a computer can do so)
ro.aa.romver=2.12.1700.1
ro.aa.maincid=GOOGL001
ro.aa.modelid=0P6B10000,0P6B50000,0P6B60000,0P6B12000,0P6B13000,0P6B11000,0P6B15000,0P6B16000,0P6B17000
ro.aa.cidlist=GOOGL001,11111111,T-MOB010,CWS__001,HTC__001,HTC__102,HTC__203,HTC__E11,HTC__405,HTC__Y13,HTC__304,HTC__A07,HTC__032,HTC__J15,HTC__016,HTC__M27,HTC__K18,HTC__A48,HTC__002,BS_US001,BS_US002,ROGER001
Some lines I've copied from my build.prop...my bootloader says superCID (1111111);however, this build prop seems to tell me that it looks like I'd be ready for the 5.0 OTA (When I flash stock recovery,which I'm still using philz)...I've asked entirely too much, even helped a few users with the things I understand, but I haven't received a complete answer...I'm s-off, GPE converted, 2.12.1700.1, rooted, superCID..I can not change my cid (no computer-no access to fastboot commands)...
Bump
Well now I can add some insight.
If in fact your completely converted than you must have the matching "CID"/" MID" as the out of box GPE HTC one m8 .no solid facts as far as the MID but I changed mine to match as I'm ready for the official GPE update. I'll just have to flash the stock recovery back when it's time.also I wouldn't use Xposed framework or anything like it just in case 5.0 rejects it.
I will add that the MID didn't matter for past OTA .I uses the 4.4.3 ruu so I could take the official 4.4.4 update
(easy as pie)
Well I believe I have completely converted to GPE...I followed graffixnyc thread for doing so, and got insight from HolyAngel. I'm still not even a 100% sure if I'm all good to go. I understand that I need to flash stock recovery, but I wasn't planning on doing so til the 5.0 OTA drops. I have searched everywhere for info about changing CIDs w/o the use of a computer,but to no avail...
Currently as it sits..I'm still on 2.12.1700.1, still superCID with philz recovery and bliss ROM...I'm switching back to skydragon 3.0.1 because the battery life is much better
Ultimately your going to need a computer at some point or wait till the ruu is released .
There needs to be more organization in this thread though. I'm not entirely stupid nor am I new to android. The reason I wanted GPE...I never used Sense based ROMs anyways. Partition is smaller with GPE too...
GOOGL001 is the CID, 0P6B17000 is MID for outta box GPE M8...I'm superCID, but never have done anything with MIDs as I let the RUU 2.12.1700.1 flash the MIDs included with the android info text of the RUU zip
I agree to e certain degree but with people making new threads about things that have already been covered definitely don't help.I'm in and out of all kinds of device forums to help because I like the challenges thrown out by all kinds of users.I realize you know what needs to be done and also realize your without a computer to get were you need to be.I hope I've not come off offensive in any way cause I am trying to help.
You didn't come off as offensive...I've gone against the grain of how things are done because after a few days of researching thread after thread after thread. I never found what I was looking for, and I still haven't...I guess I'll just wait til I get a computer to rewrite the CID. I'll just wait til 5.0 ota drops, flash the 3.09.1700.2 fw and see what happens..if anything I'll just reRUU to 2.12.1700.1...it seems to me that my phones ready for the ota anyways considering my build.prop suggests I have 1111111 and GOOGL001..
Am sure I'll see you around.good luck
I'm not going anywhere...nychitman quit supporting DU, so I'm looking into taking over in the near future...my computers still screwed til I get another hard drive put in it
@jxcorex28
Here you go man,I only hope GPE is a choice in aroma.
This is what found
http://www.droidviews.com/change-cid-mid-htc-one-devices/
MID tool zip below
http://d-h.st/w9V
I wonder if cid matters than ? I appreciate it, as it sits my mid is 0PB6B12000..Ill switch to whatever GPE MID is needed
jxcorex28 said:
I wonder if cid matters than ? I appreciate it, as it sits my mid is 0PB6B12000..Ill switch to whatever GPE MID is needed
Click to expand...
Click to collapse
Yes cid matters
So do you think superCID matters. From what I understand it doesn't because of being able to flash any ROM neantvfor any HTC m8 (as long as its GSM)
jxcorex28 said:
So do you think superCID matters. From what I understand it doesn't because of being able to flash any ROM neantvfor any HTC m8 (as long as its GSM)
Click to expand...
Click to collapse
Yes but what I've read 5.0 will check for everything. It's not worth the risk if you ask me.
To make 100% sure everything goes right just change everything to match.
Like I said all I have to do is flash stock recovery and except the OTA