Hey,
I recently got a HTC One X+ from o2 and have been researching unlocking the bootloader, rooting and installing a custom ROM. Unfortunately, I've been unable to fully understand all of the details.
1.) The RUU is a Rom update utility. Is this unique to each carrier and phone?
2.) If it is unique, where can i find the version required for my phone. I found 1.29 RUU on these forums, but it's from late last year.
3.) are RUU's issued by the carrier? Is it an automatic update we receive on the phone when using the stock RUU, or is it something we have to go and look for each time an update is issued.
I have tried searching both here and on google, but have only found bits and pieces of information (such as HTCRUU.com being down). My aim is to install a custom rom, but i'm trying to cover all my basis on information, incase something goes wrong. I'm also looking to make sure that if something other than bricking the phone goes wrong, i can return it to stock to either fix the error, or unvoid the warranty.
I have seen several mentions of codenames for various phones. On wikipedia, the one x+ is listed as HTC Endeavor C2 which I looked for on Androidfiles.org. However, theres no Endeavor listed.
Xander567 said:
Hey,
I recently got a HTC One X+ from o2 and have been researching unlocking the bootloader, rooting and installing a custom ROM. Unfortunately, I've been unable to fully understand all of the details.
1.) The RUU is a Rom update utility. Is this unique to each carrier and phone?
2.) If it is unique, where can i find the version required for my phone. I found 1.29 RUU on these forums, but it's from late last year.
3.) are RUU's issued by the carrier? Is it an automatic update we receive on the phone when using the stock RUU, or is it something we have to go and look for each time an update is issued.
I have tried searching both here and on google, but have only found bits and pieces of information (such as HTCRUU.com being down). My aim is to install a custom rom, but i'm trying to cover all my basis on information, incase something goes wrong. I'm also looking to make sure that if something other than bricking the phone goes wrong, i can return it to stock to either fix the error, or unvoid the warranty.
I have seen several mentions of codenames for various phones. On wikipedia, the one x+ is listed as HTC Endeavor C2 which I looked for on Androidfiles.org. However, theres no Endeavor listed.
Click to expand...
Click to collapse
1)+2) yes, name of RUU contains carrier , phone name, android version and software version aka base and radio version(baseband)
(ENRC2B/RUU_ENRC2B_U_JB_45_O2_UK_1.14.206.13_Radio_3.1204.167.31_release_289474_signed.exe x.xx.206.xx means O2UK
3) HTC is issuing RUU, using not touched stock after RUU will be updated via OTA updates
HTC ONE X+ code name is ENRC2B not HTC Endeavor C2 (just check it on your hboot/fastboot screen)
Endeavor is HTC One X
RUU can be found here
Thanks, that's perfect.
Related
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
Sorry if this comes across as noobish, I mainly just need a steer in the right direction and a file link or two.
Recently I started having problems with my HTC One M7 (I won't go into details, suffice to say its definitely a hardware issue). It's covered under warranty, but the problem is that my phone has been rooted and the bootloader unlocked for quite some time now. I understand that I need an RUU file to unroot the phone, however the website that every tutorial links me to (htc1guru.com) seems to have been down for quite some time. My phone has (according to my bootloader screen) need of the RUU file 4T.28.3218.04 (I live in Australia and the phone has always shown a Telstra logo, if that's any help). If someone can provide the RUU exe I need for that I can be on my way. I managed to track down from another thread on this forum the file "T-Mobile Radio 4T.28.3218.04_10.33E.1718.01L.zip" which contains a "radio.img" file among other folders. Does anyone know if I can use this somehow to just revert to stock firmware? All the tutorials I've managed to track down thus far have required RUU executables all located at htc1guru at some stage or another.
Any help appreciated of course. And a few more questions below:
-Is "Relocked" bootloader the same (for warranty purposes) as "locked"?
-I've noticed that most of the RUU files listed have 4A rather than 4T, are the two interchangeable or will the 4A one brick my phone?
Cheers, Daniel
I just bought an AT&T HTC One M8 that came with android 4.4.2 KitKat. It apparently doesn't have any available android lollipop updates since checking for updates using the "AT&T Software Update" option in settings returns a "no updates available" which was weird, but I didn't mind since I was planning to root this and flash a custom rom.
I read up on guides on rooting and unlocking the bootloader which was pretty standard for most android devices. However, S-on/S-off and hboot are 2 things that are confusing me a bit right now despite doing quite a lot of searching on XDA. To my understanding, S-on/S-off is some kind of HTC protection that needs to be disabled to flash certain roms, and hboot seems to be what people are calling the HTC Bootloader (someone correct me if I'm wrong). If I'm correct, I seem to have hboot version 3.16 according to CPU-Z (I checked the Bootloader version number).
After enough reading, it seems like having the latest hboot version is relatively important for flashing many roms (3.18-3.19 I believe), but I have found no guides on how to do this. My only lead so far is the following thread with 1 reply: http://forum.xda-developers.com/att-htc-one-m8/help/update-hboot-3-18-3-19-t3236897
"Backup any personal data you want to keep (off phone, it will be wiped). Relock the bootloader, run the latest AT&T RUU."
So ok, I guess it's a good thing I'm doing this before rooting the device. However, What's the AT&T RUU? My closest guess was using the HTC Sync Manager on windows to find firmware updates manually, but upon trying this (installing htc sync manager and connecting my HTC One M8) and on the menu clickling "Check for updates", I just get an error message saying "Unable to connect to the live update service".
Then, after some more searching I found this thread: http://forum.xda-developers.com/att-htc-one-m8/help/how-update-bootloader-to-3-18-0-0000-t3006738 which said the following:
"Follow instruction on the following thread for updating firmware, and select the 3.28.1540 firmware file: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-n"
So, here I am. Unsure whether to follow this instructions since I have no idea what that firmware is or if it will brick my device, or whether it will work since I still haven't rooted or unlocked my device's bootloader and I don't have S-Off (and that thread clearly states S-Off is mandatory for flashing to work). Any ideas?
---------------------------------------------------
edit: I just found out what RUU stands for, but I have been unable to find this "Rom Update Utility". It's spoken as Windows software, but I can't find where to download it. Any help would be very appreciated
sarxion said:
I just bought an AT&T HTC One M8 that came with android 4.4.2 KitKat. It apparently doesn't have any available android lollipop updates since checking for updates using the "AT&T Software Update" option in settings returns a "no updates available" which was weird
Click to expand...
Click to collapse
Are you connected to the AT&T network?
sarxion said:
I read up on guides on rooting and unlocking the bootloader which was pretty standard for most android devices. However, S-on/S-off and hboot are 2 things that are confusing me a bit right now despite doing quite a lot of searching on XDA. To my understanding, S-on/S-off is some kind of HTC protection that needs to be disabled to flash certain roms.
Click to expand...
Click to collapse
S-off is not needed to flash any ROMs. S-off is one way to update the firmware needed to run a ROM (more on what "firmware" is in a bit), but s-off isn't strictly need to update firmware either (other ways to do it s-on).
s-off is needed to modify (hack) certain partitions that are protected even with the bootloader unlocked. Such as hboot, radio, and some others. But its only needed for those specific things; and not needed to flash custom recovery or ROMs. And note that you can still update hboot, radio, and other firmware by "official" means even with s-on.
sarxion said:
hboot seems to be what people are calling the HTC Bootloader (someone correct me if I'm wrong).
After enough reading, it seems like having the latest hboot version is relatively important for flashing many roms (3.18-3.19 I believe)
Click to expand...
Click to collapse
Yes, hboot and bootloader are the same thing, as far as HTC devices are concerned.
Not only is the latest hboot needed to flash the current ROMs, but its important to update the entire firmware package. Firmware includes not only hboot, but also a number of other critical modules such as radio, WiFi, Bluetooth, and others; that all need to be updated in order for the current ROMs to function properly.
Good news, you are on the right track, and the proper RUU will update not only hboot, but all the firmware.
sarxion said:
What's the AT&T RUU?
edit: I just found out what RUU stands for, but I have been unable to find this "Rom Update Utility". It's spoken as Windows software, but I can't find where to download it.
Click to expand...
Click to collapse
I've created an AT&T index thread to catalog such things (sticky to the top of the General AT&T M8 section). It explains what an RUU is, and has links to all AT&T RUUs. You will want the latest RUU (4.28.502.1 or 4.28.502.2 - they are mainly the same except the latter has the Stagefright fix):
http://forum.xda-developers.com/showthread.php?t=2751432
The RUU is rather self-explanatory. As mentioned previously in this thread (and on the Index) your phone will be wiped by the RUU. So backup anything you want to keep by your method of choice. Then simply download the RUU to a PC, connect the phone. Then run the RUU program, and it will walk you through the process (you basically just need to confirm a couple dialogue boxes, and the RUU will do the rest and automatically update all the software/firmware).
After that, what you want to do in short is:
1) Unlock the bootloader using HTCDev.com
2) Install TWRP 2.8.7
3) Flash your custom ROM of choice
4) Beer