Hi guys, so after having some trouble with my phone randomly rebooting while running ViperXL, I've decided to relock my bootloader, reload the RUU 1.85 firmware, and then re-unlock my bootloader. However, I'm not really sure how to go about doing this.
I've had my phone since it came out on AT&T, and I *think* I was on the 1.85 firmware back when I rooted it. I only recently unlocked the bootloader and installed the ViperXL ROM, so now I'm not too sure as to what RUU I was on before.
So, I have a couple of questions I was hoping somebody would be able to answer:
I looked through the indexed compilation, and I didn't seem to find anything that would help me relock the bootloader. Could someone help lead me in the right direction?
Additionally, on the Stock RUU 1.85 for Cingular forum page, there's a notice saying that it "breaks the current root exploit". I'm not too sure what to make of that, considering that it was last updated in May. However, my phone was rooted back in June-ish, so I'm not sure if that root exploit is the same exploit that they are alluding to. Would i possibly have to re-root my phone afterward?
Lastly, after getting the stock RUU installed, is there a different process that I need to go through to re-unlock the bootloader considering that I was already unlocked before? Or do I need to follow the same exact procedure I did the first time?
Thanks for the help, and I apologize for the length of this forum post.
crazylilazn said:
Hi guys, so after having some trouble with my phone randomly rebooting while running ViperXL, I've decided to relock my bootloader, reload the RUU 1.85 firmware, and then re-unlock my bootloader. However, I'm not really sure how to go about doing this.
I've had my phone since it came out on AT&T, and I *think* I was on the 1.85 firmware back when I rooted it. I only recently unlocked the bootloader and installed the ViperXL ROM, so now I'm not too sure as to what RUU I was on before.
So, I have a couple of questions I was hoping somebody would be able to answer:
I looked through the indexed compilation, and I didn't seem to find anything that would help me relock the bootloader. Could someone help lead me in the right direction?
Additionally, on the Stock RUU 1.85 for Cingular forum page, there's a notice saying that it "breaks the current root exploit". I'm not too sure what to make of that, considering that it was last updated in May. However, my phone was rooted back in June-ish, so I'm not sure if that root exploit is the same exploit that they are alluding to. Would i possibly have to re-root my phone afterward?
Lastly, after getting the stock RUU installed, is there a different process that I need to go through to re-unlock the bootloader considering that I was already unlocked before? Or do I need to follow the same exact procedure I did the first time?
Thanks for the help, and I apologize for the length of this forum post.
Click to expand...
Click to collapse
Your CID should be 11111111, so you can unlock your bootloader again using the same unlock token from your first unlock. You will need HTC drivers installed.
to relock your bootloader,
Fastboot files http://www.mediafire.com/?4dx982z93w8z7wk
download and extract to desktop
open cmd and type cd Desktop
then cd foldername (the folder where fastboot is)
Boot into fast boot on your phone
then type fastboot oem lock
crazylilazn said:
Hi guys, so after having some trouble with my phone randomly rebooting while running ViperXL, I've decided to relock my bootloader, reload the RUU 1.85 firmware, and then re-unlock my bootloader. However, I'm not really sure how to go about doing this.
I've had my phone since it came out on AT&T, and I *think* I was on the 1.85 firmware back when I rooted it. I only recently unlocked the bootloader and installed the ViperXL ROM, so now I'm not too sure as to what RUU I was on before.
So, I have a couple of questions I was hoping somebody would be able to answer:
I looked through the indexed compilation, and I didn't seem to find anything that would help me relock the bootloader. Could someone help lead me in the right direction?
Additionally, on the Stock RUU 1.85 for Cingular forum page, there's a notice saying that it "breaks the current root exploit". I'm not too sure what to make of that, considering that it was last updated in May. However, my phone was rooted back in June-ish, so I'm not sure if that root exploit is the same exploit that they are alluding to. Would i possibly have to re-root my phone afterward?
Lastly, after getting the stock RUU installed, is there a different process that I need to go through to re-unlock the bootloader considering that I was already unlocked before? Or do I need to follow the same exact procedure I did the first time?
Thanks for the help, and I apologize for the length of this forum post.
Click to expand...
Click to collapse
It will break root, but you can get that back with one of the original ways since you will still be on 1.85.
Sent from a slithery smooth phone!
Just flash another rom or wipe and reflash. Ruu will probably not help a random reboot.
Yeah same, I'd try a different ROM without going back to stock just to come to custom ROMs again.
WR
Sent from my One X
crazylilazn said:
Hi guys, so after having some trouble with my phone randomly rebooting while running ViperXL, I've decided to relock my bootloader, reload the RUU 1.85 firmware, and then re-unlock my bootloader. However, I'm not really sure how to go about doing this.
I've had my phone since it came out on AT&T, and I *think* I was on the 1.85 firmware back when I rooted it. I only recently unlocked the bootloader and installed the ViperXL ROM, so now I'm not too sure as to what RUU I was on before.
So, I have a couple of questions I was hoping somebody would be able to answer:
I looked through the indexed compilation, and I didn't seem to find anything that would help me relock the bootloader. Could someone help lead me in the right direction?
Additionally, on the Stock RUU 1.85 for Cingular forum page, there's a notice saying that it "breaks the current root exploit". I'm not too sure what to make of that, considering that it was last updated in May. However, my phone was rooted back in June-ish, so I'm not sure if that root exploit is the same exploit that they are alluding to. Would i possibly have to re-root my phone afterward?
Lastly, after getting the stock RUU installed, is there a different process that I need to go through to re-unlock the bootloader considering that I was already unlocked before? Or do I need to follow the same exact procedure I did the first time?
Thanks for the help, and I apologize for the length of this forum post.
Click to expand...
Click to collapse
this has answers to all your questions http://forum.xda-developers.com/showpost.php?p=26669144&postcount=1
enjoy the read...
I'm used to samsung so please bear with me...
I just came across an at&t one x that is running 1.85 with the hboot 1.9.000
I am kind of confused as to how to go about rooting/unlocking (if possible) this phone
it seems the xfactor/motochopper methods of rooting (which are in the noob friendly toolkit) are not available for this firmware version. All I see is this method http://forum.xda-developers.com/showthread.php?t=1709296
Most importantly, as I profoundly despise sense, I just want to unlock the boot loader, put a custom recovery on and get some Cm 10.1 on here.
I have read methods which require some hex editing, changing the cid to 111111111, etc...
My question is what is the best way to get a custom recovery on this phone now, as some of these methods seem really old (2012)
i'm just confused because it seems i have a pretty old firmware version and i don't want to break anything.
Oogy said:
I'm used to samsung so please bear with me...
I just came across an at&t one x that is running 1.85 with the hboot 1.9.000
I am kind of confused as to how to go about rooting/unlocking (if possible) this phone
it seems the xfactor/motochopper methods of rooting (which are in the noob friendly toolkit) are not available for this firmware version. All I see is this method http://forum.xda-developers.com/showthread.php?t=1709296
Most importantly, as I profoundly despise sense, I just want to unlock the boot loader, put a custom recovery on and get some Cm 10.1 on here.
I have read methods which require some hex editing, changing the cid to 111111111, etc...
My question is what is the best way to get a custom recovery on this phone now, as some of these methods seem really old (2012)
i'm just confused because it seems i have a pretty old firmware version and i don't want to break anything.
Click to expand...
Click to collapse
absolutely nevermind, i figured everything out.
Right, so I wanted to install an OTA update on my rooted EE HTC M8. I followed this guide: "Unbrick/Unroot/Restore HTC One M8 to Stock 4.4.4!" on youtube (won't let me post links yet) and after flashing back to a stock recovery and unrooting the phone through SuperSU I attempted to install the OTA update.
I don't know if I did something wrong or the guide just sucked, but now it gets stuck on the boot screen every time. I can still access the bootloader and get into the stock recovery, but wiping cache/system restore doesn't help, I can't flash anything through adb as it doesn't detect my device and trying any commands just hangs on 'waiting on device'. My only option seems to be flashing an 0P6BIMG.zip from the bootloader by putting it on my SD card, but I can't seem to find a RUU that will work with my ORANG001 CID or 4.19.61.3 OS.
I tried a few when I didn't know RUUs were location/carrier specific and it would load the image fine then reboot but still get stuck on boot screen, and I tried this RUU: "0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417809_signed" but I just get a 'Device halted due to Large Image update fail!' error.
I can't find any advice online specific to my issue, and my tech savvy mate who's also owned an m8 isn't available to help out at the moment, so I thought someone on here might be able to help with my situation. I'm going to take it into an EE store tomorrow but I don't know if they will be able to help.
Hi,
Try posting your question here:
One (M8) Q&A, Help & Troubleshooting
The experts there may be able to help.
Good luck!
Would somebody please advise me about the pro's and cons of changing my HBOOT version.
I can successfully root my phone via The Revolutionary method after downgrading using an earlier RUU etc.
What I am not clear about is whether I then need to flash an ENG HBOOT after this process .... which version.... why I should do this ?
If I have the "wrong" HBOOT installed will that prevent certain ROMs from running correctly ?
Do I need a specific "level" of HBOOT for a GB based ROM to run and another for an ICS based ROM
Choosing your HBOOT Version
I don't know absolutely everything about this, but since you've waited over a month with no replies, I'll tell you what I know. It should be enough to answer your question, if you're looking for something more advanced then you may need to keep looking!
The original HBOOT version is 0.98.00000, this is the HBOOT version that you need if you want to S-OFF your phone as the later version, 2.000.00002, blocks the vulnerability that allows the Revolutionary exploit to work. S-OFF unlocks root level access to the phone permanently, allowing you to flash new ROMs directly from the SD card without having to use ADB and USB Debugging to flash the boot image every time.
Basically, if you want S-OFF you may need to downgrade your HBOOT to 0.98.0000 if that's not the version you already have.
The phone originally shipped with Android Gingerbread 2.3, this can be upgraded to a certain point, beyond which, the newer version of HBOOT is required. I don't know which version is the crossover point but I'm sure a quick search of the forums will provide the answer, I'll leave that up to you (I think the main reason you haven't had any replies is that ALL this info is already available in the various guides in the forum, so people think you're being lazy not looking for it!).
So....
Unless you're trying to do something out of the ordinary, the most common approach is a follows;
Unlock bootloader on HTCDev.
Downgrade to HBOOT 0.98.00000 (f necessary).
Use Revolutionary to gain S-OFF.
Upgrade to HBOOT 2.000.00002 (not necessary for Android 2.3 but later versions require this)
Download and flash new ROMs directly from the SD card using custom recovery, such as TWRP or Clockworkmod.
I hope this helps, I do understand that it's not always easy piecing things together from multiple forum threads to learn about something new, but ALL the info you needed IS already available on here.
There are some excellent guides and tutorials here on XDA Developers, both official and unofficial. I would say if you don't already have a bit of knowledge then stick to the official guides and you can't go wrong.
Hint: Try searching the forum for [Guide]
Hey guys,
I've decided to root for the first time in my life on my HTC U11+. Everything went fine and I unlocked the phone. But now, I'm stuck in this weird loop. I'm currently on the latest Pie version (the final one that the device got), and I cannot find a TWRP for it! I've seen people saying that there aren't any for Pie (or that they are not working), so I wanted to downgrade the version of the device. I downloaded the HTCDev Info Tool, but it just says "Can not get root permission!". So it looks like I need TWRP to downgrade, but I can't get a TWRP for my version! I don't understand many of the stuff, but I know that S-on. I would like to install Magisk, so if there's a way around this entire thing please help me. Thanks.