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
Related
I know my phone isn't bricked...but I'm stuck.
I wanted to restore the Verizon stock ROM (for reasons I'll post in a different thread).
I was originally at DCD 2.1.0 with the Radio 3.17.
I got the Verizon Stock Rom from ftp://up.ppcgeeks.com/Titan/Users/vboyz
I ran the Titan unlocker, and changed the nbh to the verizon one and flashed it.
Now I'm stuck on the white Verizon screen.
I know I did it wrong, but I couldn't find a consistent post with all the links and instructions how to do it.
HELP!
For starters you might want to use an actual Verizon Stock ROM:
http://forum.xda-developers.com/showpost.php?p=1845171&postcount=13
THANK YOU! I am downloading those now.
What steps do I need to follow
I have the relocker, and the verizon files. All I can get to is the SPL2.4 Olipro screen and the white verizon screen...help!
I just reloaded the dcd rom, ran the unlocker, loaded the verizon rom, and it all works now
Please give exact steps used
dkreifus said:
THANK YOU! I am downloading those now.
What steps do I need to follow
I have the relocker, and the verizon files. All I can get to is the SPL2.4 Olipro screen and the white verizon screen...help!
I just reloaded the dcd rom, ran the unlocker, loaded the verizon rom, and it all works now
Click to expand...
Click to collapse
Please post the exact steps you used as these 'stock' verizon ROMs do not as yet exist. I will explain: The ROM you used is an image taken of a phone, a full image of someone's phone, and not really the factory 'out of box' software that is available for the Sprint unit. The reason that this is important is that it could lead possibly to a problem, or at least I would like to see if it does, before I mess with it. The phone comes stock with the 1.6 bootloader and is keyed to look for valid signed by the vendor software, and if it is not signed by the vendor it will not get past 0% and if it is signed by Sprint and you try to load it on a verizon unit it goes 1 % and gets a 'invalid vendor id' error and stops. On a Sprint unit if you mess up and get the wrong radio/ROM combo and maybe get the 1.6 bootloader back on by mistake then you can fix it with the stock 2.09 Sprint RUU because it exists and is signed. If you do this on a Verizon unit at the moment you might have trouble with the 1.6 bootloader as it is looking for signed software and I wonder if that image file satisfies this ?????? So I guess the long and the short of it is to know if you re-locked the phone (bootloader shows 1.6) BEFORE you ran back in the stock Verizon image ??? Did you have the unlocked (OliPro 2.4 bootloader) on the phone when you restored that stock image ???? Thanks.
madman34 said:
Please post the exact steps you used as these 'stock' verizon ROMs do not as yet exist. I will explain: The ROM you used is an image taken of a phone, a full image of someone's phone, and not really the factory 'out of box' software that is available for the Sprint unit. The reason that this is important is that it could lead possibly to a problem, or at least I would like to see if it does, before I mess with it. The phone comes stock with the 1.6 bootloader and is keyed to look for valid signed by the vendor software, and if it is not signed by the vendor it will not get past 0% and if it is signed by Sprint and you try to load it on a verizon unit it goes 1 % and gets a 'invalid vendor id' error and stops. On a Sprint unit if you mess up and get the wrong radio/ROM combo and maybe get the 1.6 bootloader back on by mistake then you can fix it with the stock 2.09 Sprint RUU because it exists and is signed. If you do this on a Verizon unit at the moment you might have trouble with the 1.6 bootloader as it is looking for signed software and I wonder if that image file satisfies this ?????? So I guess the long and the short of it is to know if you re-locked the phone (bootloader shows 1.6) BEFORE you ran back in the stock Verizon image ??? Did you have the unlocked (OliPro 2.4 bootloader) on the phone when you restored that stock image ???? Thanks.
Click to expand...
Click to collapse
I was stuck at the OliPro 2.4 bootloader. It would freeze at the white screen, or I could get to the bootloader. So I reloaded the DCD 2.x image.
Once it was up and running, I used the relocker, and downgrader the bootloader.
From there, I loaded the 'stock' verizon image, and presto, it all took like magic.
I was fortunate enough to not panic, and realize that its not bricked. Just a matter of trial/error and patience.
Coolness
dkreifus said:
I was stuck at the OliPro 2.4 bootloader. It would freeze at the white screen, or I could get to the bootloader. So I reloaded the DCD 2.x image.
Once it was up and running, I used the relocker, and downgrader the bootloader.
From there, I loaded the 'stock' verizon image, and presto, it all took like magic.
I was fortunate enough to not panic, and realize that its not bricked. Just a matter of trial/error and patience.
Click to expand...
Click to collapse
Ok so it is nice to know that this image will store back,,,,thanks.
You totally wrote complete misinformation. The ROM I linked is not a dump of a running ROM. It's a complete Ship ROM from VZW. The link I provided is from a complete thread where this was discussed. You might want to actually look at the files before posting about them. If you would have extracted the NBH you would have noticed that it was a complete ROM not just the OS.nb.
Just what blazingwolf said,,,,,,,
jrebeiro said:
You totally wrote complete misinformation. The ROM I linked is not a dump of a running ROM. It's a complete Ship ROM from VZW. The link I provided is from a complete thread where this was discussed. You might want to actually look at the files before posting about them. If you would have extracted the NBH you would have noticed that it was a complete ROM not just the OS.nb.
Click to expand...
Click to collapse
Anyway, it is acknowledged as a ship ROM, but Blazingwolf said that that since there has been no release from HTC for the Verizon as there was for the Sprint that these ROMs were actually extracted from a unit out-of-box and compiled correctly, and do contain all data that they are supposed to contain. If you look at the utstar.com downloads section you will see that there is no RUU for the VZW unit but there is for the Sprint unit, this being because Sprint released 2.17 and had broken some stuff and had to release 2.09 which you do find there. So I did not mean that I was worried about completeness, as I did de-compile and look, but just was curious to see someone get it done with these because they were obtained in a different way than usual. I think it is a cool way to do it and would like to have the tool used to pull a ROM from a unit so that I could do the same with mine configured as it is and return to it anytime I wanted to.
dude... the ROM I linked to is digitally signed by Verizon.
If you are suggesting that someone was capable of fully ripping the IPL/SPL/Radio/Splash/ExtROM/OS from a running Titan AND getting VZW's digital certificate to sign the NBH then I want to meet the person who did it so we won't need to Hard SPL our devices anymore!
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.
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.
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"
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