Im update to 1.85 and now i can't root my phone, help me please...
Currently there is no 1.85 root method..
I'm stuck in the same boat [and theres NO big flags saying "Upgrading to 1.85 means no root unless you do this first!"] and modified my CID from 11111111 [superCID] to the stock one so yeah. We'll either have to wait for the bootloader unlock // A force CID Method // and-or a root method to bypass the 1.85 issue or until a new update comes out with its own method(s).
Some people have had luck doing this though;
http://forum.xda-developers.com/showthread.php?t=1671396
By following the 12th step and attempting to use HTCDev.com.
I've tried everything to no avail on 1.85. Other ICS exploits such as Mempodroid have also been patched.
HELP!
TKTAB911 said:
Currently there is no 1.85 root method..
I'm stuck in the same boat [and theres NO big flags saying "Upgrading to 1.85 means no root unless you do this first!"] and modified my CID from 11111111 [superCID] to the stock one so yeah. We'll either have to wait for the bootloader unlock // A force CID Method // and-or a root method to bypass the 1.85 issue or until a new update comes out with its own method(s).
Some people have had luck doing this though;
http://forum.xda-developers.com/showthread.php?t=1671396
By following the 12th step and attempting to use HTCDev.com.
Click to expand...
Click to collapse
...
TKTAB911 said:
...
Click to expand...
Click to collapse
I was agreeing with you... I was also just saying that instead of waiting around, I've tried all of the other ICS exploits to see if anything was overlooked.
TKTAB911 said:
theres NO big flags saying "Upgrading to 1.85 means no root unless you do this first!"
Click to expand...
Click to collapse
True, the thread in which the RUU is posted has no such warning. But my index thread (sticky at the top of Development) is your friend. I even put it in boldface:
[STOCK] AT&T RUU_Evita_UL_Cingular_US-1.85.502 Warning: Can only be rooted if SuperCID before running this RUU. Details here
Also, as a rule, never update to a new official firmware, until you have done thorough research on whether a root method exists or still works. Its fairly common for new official ROMs to break existing root methods.
Root 1.85
crazydai said:
Im update to 1.85 and now i can't root my phone, help me please...
Click to expand...
Click to collapse
Could we try to reinstall RUU 1.73... or 1.82...? I have not attempted this but wondering if we could do that then root and so on?
Thanks,
David
djcortes said:
Could we try to reinstall RUU 1.73... or 1.82...? I have not attempted this but wondering if we could do that then root and so on?
Thanks,
David
Click to expand...
Click to collapse
I've tried doing this to no avail. I've tried both. I've even extracted the rom.zip and tried to replace it but I still the get the 140 bootloader error.
robertatl said:
I've tried doing this to no avail. I've tried both. I've even extracted the rom.zip and tried to replace it but I still the get the 140 bootloader error.
Click to expand...
Click to collapse
Well that blows!
thanks for answering the question though
robertatl said:
I've tried doing this to no avail. I've tried both. I've even extracted the rom.zip and tried to replace it but I still the get the 140 bootloader error.
Click to expand...
Click to collapse
What about replacing System.IMG inside of the %temp% folder with System.IMG from 1.82 with the /data/local/tmp exploit?
mbaran said:
What about replacing System.IMG inside of the %temp% folder with System.IMG from 1.82 with the /data/local/tmp exploit?
Click to expand...
Click to collapse
hmm.. I would be willing to try this but would need some guidance with the exploit.
meaning how to do it!
-David
djcortes said:
hmm.. I would be willing to try this but would need some guidance with the exploit.
meaning how to do it!
-David
Click to expand...
Click to collapse
I don't even know if it's possible, but when you start the RUU in windows it extracts it's whole working set of data to %temp% on Windows.
No idea if one System.IMG could be substitutes for the other, since it's all signed.
djcortes said:
hmm.. I would be willing to try this but would need some guidance with the exploit.
meaning how to do it!
-David
Click to expand...
Click to collapse
I just tried that exploit as well but it fails due to permission denied error
redpoint73 said:
True, the thread in which the RUU is posted has no such warning. But my index thread (sticky at the top of Development) is your friend. I even put it in boldface:
[STOCK] AT&T RUU_Evita_UL_Cingular_US-1.85.502 Warning: Can only be rooted if SuperCID before running this RUU. Details here
Also, as a rule, never update to a new official firmware, until you have done thorough research on whether a root method exists or still works. Its fairly common for new official ROMs to break existing root methods.
Click to expand...
Click to collapse
You did put a warning in the thread, but it's misleading and lead me to be stuck in stock 1.85. May I suggest that you re-word it "Can only be rooted if SuperCID -> Unlocked -> Relocked" so other people don't get confused. I set up SuperCID but did not unlock, and that's what screwed me.
red3gunner said:
You did put a warning in the thread, but it's misleading and lead me to be stuck in stock 1.85. May I suggest that you re-word it "Can only be rooted if SuperCID -> Unlocked -> Relocked" so other people don't get confused. I set up SuperCID but did not unlock, and that's what screwed me.
Click to expand...
Click to collapse
Can't you just unlock the bootloader now, since you already have SuperCID?
If not, that's news to me, and the reason my index thread is worded the way it is.
Yes, that worked! Thanks, sorry for the noobism.
red3gunner said:
Yes, that worked! Thanks, sorry for the noobism.
Click to expand...
Click to collapse
Ha, no worries! I was confused there for a second.
Related
I created a double-clickable script for Mac users to allow them to unlock the bootloader on their AT&T or Rogers HTC One XL using the SuperCID. This is really a combination of the Linux script from JeepFreak and the Windows script from designgears (via kennethpnn) with some tweaks of my own. All of these are based on the exploit grankin01 found.
Requirements
root (acquiring it varies based on your firmware version)
USB Debugging enabled (Settings -> Developer Options) on your device
Fast boot disabled (Settings -> Power) on your device
Installation
Download OneXL_SuperCID_Mac_v1_1.zip (sha1 available here if you want to verify download zip)
Locate the OneXL_SuperCID_Mac_v1_1.zip file and double-click it
Open the OneXL_SuperCID_Mac_v1_1 folder it creates
Double click the OneXL_SuperCID_Mac file in that folder
Follow the instructions on the screen
Additional Notes
Verified working on 1.73 and 1.85 but should really work on any firmware version as long as it's rooted already.
This script has two main parts: 1) Modifying the CID on your device to be the Super CID and 2) Unlocking the bootloader using an unlock code from htcdev.com. You can certainly stop the script after it finishes the first step if all you want is Super CID (maybe Rogers folks that are already unlocked but want Super CID). You can also run the script on a device that already has Super CID if you mainly want the script to do the actual bootloader unlock.
Many thanks to the xda users mentioned above that made this possible. I also wanted to thank cvv1984, aafevo and kaijuman for helping me test this on their own devices. If this is helpful to you please hit the Thanks button on this post and/or a post from the xda users mentioned above.
Can confirm this works like a charm! Thanks a lot to jnichols it made doing everything on my Mac a much easier experience. Very grateful.
Nicely done sir!
Billy
JeepFreak said:
Nicely done sir!
Billy
Click to expand...
Click to collapse
That's too kind of you, seeing how your work (part of which is in http://forum.xda-developers.com/showthread.php?t=1673878) was the basis for much of my mac-tweaked script. You all might send some thanks JeepFreak's way at the link above for the Linux version that helped make this one that much easier.
Thanks man, been waiting for this. Gonna try it out when I get home from the grind today.
jnichols959 said:
I created a double-clickable script for Mac users to allow them to unlock the bootloader on their AT&T or Rogers HTC One XL using the SuperCID. This is really a combination of the Linux script from JeepFreak and the Windows script from designgears (via kennethpnn) with some tweaks of my own. All of these are based on the exploit grankin01 found.
Installation
You're going to need USB Debugging enabled (Settings -> Developer Options) and Fast boot disabled (Settings -> Power) on your device.
Download OneXL_SuperCID_Mac_v1_0.zip (sha1 available here if you want to verify download zip)
Locate the OneXL_SuperCID_Mac_v1_0.zip file and double-click it
Open the OneXL_SuperCID_Mac_v1_0 folder it creates
Double click the OneXL_SuperCID_Mac file in that folder
Follow the instructions on the screen
Additional Notes
This script has two main parts: 1) Modifying the CID on your device to be the Super CID and 2) Unlocking the bootloader using an unlock code from htcdev.com. You can certainly stop the script after it finishes the first step if all you want is Super CID (maybe Rogers folks that are already unlocked but want Super CID). You can also run the script on a device that already has Super CID if you mainly want the script to do the actual bootloader unlock.
Many thanks to the xda users mentioned above that made this possible. I also wanted to thank cvv1984 and aafevo for helping me test this on their own devices. If this is helpful to you please hit the Thanks button on this post and/or a post from the xda users mentioned above.
Click to expand...
Click to collapse
great. thanks man. Had used both these scripts in terminal but never had the time to merge. Great someone is doing some mac support.
How about RUU ??
Crappyvate said:
great. thanks man. Had used both these scripts in terminal but never had the time to merge. Great someone is doing some mac support.
How about RUU ??
Click to expand...
Click to collapse
Yeah, I'd *love* to be able to run RUUs from a mac without virtualization but sadly I don't have any bright ideas for that one...
jnichols959 said:
Yeah, I'd *love* to be able to run RUUs from a mac without virtualization but sadly I don't have any bright ideas for that one...
Click to expand...
Click to collapse
Was able to extract rom.zip out of the .exe on my mac but that's as far as I went, never had the balls to attempt to try to flash it in fastboot. Apparently you would need to "cook it" through a rom kitchen.
If anyone has thoughts on this please chime in...
Awesome to have mac support! I just upgraded to the One X from an iPhone 3GS that I held on to for three years.
Question: Is this compatible with the OTA update that went out last night? I'm running 1.85 now.
I keep getting this error. My phone is an AT&T phone.
"We don't recognize your current CID as a Rogers, AT&T or Super CID
and can not continue."
edit..
I tried changing usb cables and ports. Also rebooted both phone and computer. Double checked that debugging and fastboot are correct. The only thing i've done with this phone is flash the leaked ruu a couple weeks ago that AT&T is now pushing out.
I'm assuming 1.85 isn't supported yet.
If you don't have root this tool won't work.
DOH! And theres my sign.. Thanks. Didn't realize root was needed.
phxblue said:
DOH! And theres my sign.. Thanks. Didn't realize root was needed.
Click to expand...
Click to collapse
yeah, i didn't mention it in the OP but added it now. thanks gunnyman.
phxblue said:
I keep getting this error. My phone is an AT&T phone.
"We don't recognize your current CID as a Rogers, AT&T or Super CID
and can not continue."
edit..
I tried changing usb cables and ports. Also rebooted both phone and computer. Double checked that debugging and fastboot are correct. The only thing i've done with this phone is flash the leaked ruu a couple weeks ago that AT&T is now pushing out.
I'm assuming 1.85 isn't supported yet.
Click to expand...
Click to collapse
Try downloading this dump_misc script, running the dump_misc script inside the zip, then PM me the mmcblk0p4.txt file it creates so I can see what your CID is.
EDIT: turns out there is some other problem for phxblue. i don't think it's actually that he has a non-att/rogers/super CID but i'm still working on it via PM and will update in this post with any info that might be useful to others.
jnichols959 said:
Yeah, I'd *love* to be able to run RUUs from a mac without virtualization but sadly I don't have any bright ideas for that one...
Click to expand...
Click to collapse
Don't want to hijack your thread but did you see this:
http://forum.xda-developers.com/showthread.php?t=1656068
that means we can now script flashing ruu's on mac...
Crappyvate said:
Don't want to hijack your thread but did you see this:
http://forum.xda-developers.com/showthread.php?t=1656068
that means we can now script flashing ruu's on mac...
Click to expand...
Click to collapse
Veeerrry interesting. I imagine he cracked open the rom.zip from the unpacked RUU and figured out how to work with the innards. Earlier today I figured out how to fastboot flash the boot_secured.img from an unpacked RUU to allow downgrading from (for example) a CleanROM unsecured boot to one of the stock RUUs - so it's great to see more mac-friendly dev stuff on these forums! Thanks for the heads up.
phxblue said:
I keep getting this error. My phone is an AT&T phone.
"We don't recognize your current CID as a Rogers, AT&T or Super CID
and can not continue."
edit..
I tried changing usb cables and ports. Also rebooted both phone and computer. Double checked that debugging and fastboot are correct. The only thing i've done with this phone is flash the leaked ruu a couple weeks ago that AT&T is now pushing out.
I'm assuming 1.85 isn't supported yet.
Click to expand...
Click to collapse
Turns out the problem was that he was running the script from inside his dropbox folder, and it doesn't behave like regular Mac folders, breaking the script. Lesson learned!
lordgregus said:
Awesome to have mac support! I just upgraded to the One X from an iPhone 3GS that I held on to for three years.
Question: Is this compatible with the OTA update that went out last night? I'm running 1.85 now.
Click to expand...
Click to collapse
Yes, this should work on 1.85 but you need root so 1.85 can complicate things until we get a solid 1.85 root. I believe you need to have the bootloader unlocked on 1.85 in order to get root so it seems all this will do for you on 1.85 is allow you to change an unlocked bootloader with the 1.85 CID to the Super CID. I'm waiting to see an unconditional root for 1.85 and at that point folks that got a bootloader locked 1.85 will be able to use this to both unlock the bootloader and set CID to Super CID (after acquiring root of course).
I just rooted 1.85, can anyone confirm that it's safe to use this script?
lordgregus said:
I just rooted 1.85, can anyone confirm that it's safe to use this script?
Click to expand...
Click to collapse
Yes, it's safe to use on a rooted 1.85. I ran the 1.85 RUU on my relocked 1.73 HOX, then verified this script works as expected.
Can someone help me out? Im trying to unlock my bootloader on my one x and when I go to submit the unlock token on htcdev, it keeps failing and will never go through. Does anyone know a way around it? A different way of unlocking the bootloader? I would really appreciate it if I can get some help with this.
Thanks in advance
iLToRReNT said:
Can someone help me out? Im trying to unlock my bootloader on my one x and when I go to submit the unlock token on htcdev, it keeps failing and will never go through. Does anyone know a way around it? A different way of unlocking the bootloader? I would really appreciate it if I can get some help with this.
Thanks in advance
Click to expand...
Click to collapse
Its a real pain in the ass. What I did is cut and paste the key into a text editor. You have to remove leading spaces from the top make sure you include the lines that have the >>> on the top and the bottom. Make sure the numbers all line up it's a ***** to get right.
Thanks, I'll give it a shot and post back if it works.
gunnyman said:
Its a real pain in the ass. What I did is cut and paste the key into a text editor. You have to remove leading spaces from the top make sure you include the lines that have the >>> on the top and the bottom. Make sure the numbers all line up it's a ***** to get right.
Click to expand...
Click to collapse
Not quite sure I understood what you said, and if I did, I did it wrong. Do you think i could send you the token and you do what is needed? Then you could send it back to me. I don't mean to be a bother about it.
Sorry no can do. I'm on vacation no computer.
gunnyman said:
Sorry no can do. I'm on vacation no computer.
Click to expand...
Click to collapse
Ok well thanks anyways.
Did you manage to get it? PM me your token if you still need help and i'll take a quick look at it.
I have the same issue.. Mine says it's too long.. It's a pain in the ass..
Sent from my HTC One X using xda premium
iLToRReNT said:
Can someone help me out? Im trying to unlock my bootloader on my one x and when I go to submit the unlock token on htcdev, it keeps failing and will never go through. Does anyone know a way around it? A different way of unlocking the bootloader? I would really appreciate it if I can get some help with this.
Thanks in advance
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1709424
Follow these instructions. Only works on 1.85
I know what you're talking about there. I made sure I right-clicked on the first < on the line to mark. THen, clicked where I marked exactly to select. Cntrl C, Cntrl V and it works. I know it's a PITA...took me a few tries before I got it.
Still a problem
subarudroid said:
http://forum.xda-developers.com/showthread.php?t=1709424
Follow these instructions. Only works on 1.85
Click to expand...
Click to collapse
Yeah that's another one of my problems, I'm on 2.20, which is not root capable . Do you know a way of downgrading to 1.85?
iLToRReNT said:
Yeah that's another one of my problems, I'm on 2.20, which is not root capable . Do you know a way of downgrading to 1.85?
Click to expand...
Click to collapse
Wait your on 2.20...... You can't root or unlock your bootloader because you need root to change your cid so that you can unlock your bootloader from HTC dev. There is no current exploit to root 2.20 unless you were already unlocked prior to the update. You re going to have to sit tight till someone comes up with a new exploit for 2.20.
Sent from my Nocturnalized Beast
...
E.Cadro said:
Wait your on 2.20...... You can't root or unlock your bootloader because you need root to change your cid so that you can unlock your bootloader from HTC dev. There is no current exploit to root 2.20 unless you were already unlocked prior to the update. You re going to have to sit tight till someone comes up with a new exploit for 2.20.
Sent from my Nocturnalized Beast
Click to expand...
Click to collapse
Yeah, that's why I was wondering if anyone knew a way of downgrading. I posted this thread before I found out that you root before unlocking bootloader on this phone. I thought that just running a 1.85 RUU would downgrade it but that failed. So do you have a way of downgrading?
There's no way to downgrade either.
...
gunnyman said:
There's no way to downgrade either.
Click to expand...
Click to collapse
FUUUUCK! Well thanks for any information you people gave me.
Hi all,
I was hoping I could get updated on the lastest as I just recieved an AT&T One X and I am also on 2.20...Have we had any progress toward Root or Unlocking the Bootloader?
Appreciate any information you may have?
maddie01 said:
Hi all,
I was hoping I could get updated on the lastest as I just recieved an AT&T One X and I am also on 2.20...Have we had any progress toward Root or Unlocking the Bootloader?
Appreciate any information you may have?
Click to expand...
Click to collapse
Just go over the the 2.20 root think tank thread, instead of digging up a 2 month old thread.
Yes, I have searched all over this forum, but since 2.20 was released, a lot of threads and methods are out of date. I got my AT&T One XL back when everyone pre-ordered it, but I've just now come around to creating an account now that I have a question.
I rooted 1.73 about a month ago and was content, but now that CM10 nightlies are out, I want to try CM10. My HOX is my first ever Android phone, and so I've been trying to learn terms like 'flash' and 'boot into', but it's all still a bit fuzzy, even after research. However, I do know how to read, and so if instructions are specific, I'll be able to do it.
So, can someoneexplain an up to date method of how to go from rooted 1.73 to rooted and unlocked 1.85 to me, it would be much appreciated. I really don't want to mess it up! Thanks in advance for any help you can give me.
no need to go to 1.85 at all. your phone is rooted so now just run the oneclick superCID tool to unlock the bootloader on HTCDev
after that install twrp recovery and then the rom of your choice.
gunnyman said:
no need to go to 1.85 at all. your phone is rooted so now just run the oneclick superCID tool to unlock the bootloader on HTCDev
after that install twrp recovery and then the rom of your choice.
Click to expand...
Click to collapse
Oh, thanks! I've successfully unlocked my phone's bootloader using that method. However, upon the first boot, an AT&T update automatically started downloading. I have not installed it. Should I delete it or go ahead with it?
Don't take the update.
gunnyman said:
Don't take the update.
Click to expand...
Click to collapse
Okay, is there any way to delete it? It downloaded, and will 'remind me later' to update. Is there any way to stop that? Thanks again!
I'm sure you can delete it but I don't know where to tell you to look. I have never taken an ota update.
gunnyman said:
I'm sure you can delete it but I don't know where to tell you to look. I have never taken an ota update.
Click to expand...
Click to collapse
I found it in download on my sdcard, might check there.
Will someone post the correct 1.85 RUU for this phone, or send a link to it? Having a little trouble trying to find it. Or maybe I did?
RUU_Evita_Cingular_US_1.85.502.3_R2_Radio_0.71.32.09.12_10.86.32.08L_release_262092_signed
I'm trying to downgrade via this guide: http://forum.xda-developers.com/showpost.php?p=33914948&postcount=65
Edited the mmcblk0p23 just fine, placed it back on my phone and tried to run the RUU but it says that it wasn't able to run, which leads me to the conclusion it's the wrong RUU.
Any input would be fantastic.
Edit: just tried again and this is the error that I am getting.
Here: http://forums.team-nocturnal.com/showthread.php/1005-RUU-One-X-XL-LTE-RUU-s
Here: http://forum.xda-developers.com/showthread.php?t=1670238
Or also here: http://forum.xda-developers.com/showthread.php?t=1671237
I believe that since you are editing the version number on your phone, it shouldn't matter what RUU version, as long as the CID is correct (which SuperCID should also render a moot point).
redpoint73 said:
Here: http://forums.team-nocturnal.com/showthread.php/1005-RUU-One-X-XL-LTE-RUU-s
Here: http://forum.xda-developers.com/showthread.php?t=1670238
Or also here: http://forum.xda-developers.com/showthread.php?t=1671237
I believe that since you are editing the version number on your phone, it shouldn't matter what RUU version, as long as the CID is correct (which SuperCID should also render a moot point).
Click to expand...
Click to collapse
Well, quick on the draw with 3 links... I have the correct one. Now it's just a matter of finding out why it's not working. I'll look at my CID and see what's going on.
Did you reboot into fast boot and relock the boot loader after applying the edit?
Im trying this right now but my hex file is all zeros? Why is this and what should I do to resolve this?
absolutelygrim said:
Did you reboot into fast boot and relock the boot loader after applying the edit?
Click to expand...
Click to collapse
Yeah. Ran the 2.20 RUU just fine
mlaws90 said:
Im trying this right now but my hex file is all zeros? Why is this and what should I do to resolve this?
Click to expand...
Click to collapse
The place you have to edit will be on the right side, You'll find the line 0x0a0 on the left.
Myrder said:
The place you have to edit will be on the right side, You'll find the line 0x0a0 on the left.
Click to expand...
Click to collapse
Screenshot:
Is this all I do?:
mlaws90 said:
Is this all I do?
Click to expand...
Click to collapse
Yeah
Wait, that's your mmcblk0p23? That's wrong, that should have your CID and Clearimage what not above the 0x0a0 line...
Grim, what do?
Myrder said:
Yeah
Wait, that's your mmcblk0p23? That's wrong, that should have your CID and Clearimage what not above the 0x0a0 line...
Grim, what do?
Click to expand...
Click to collapse
Yeah, I only have the unlocked bootloader, not SuperCID, I THINK, I did it a long time ago, I got the phone on release day. Could this be why? I am getting an RUU Error 154 or 155 I think why I do try it it will go about 2 min then fail.
mlaws90 said:
I only have the unlocked bootloader, not SuperCID, I did it a long time ago, I got the phone on release day. Could this be why? I am getting an RUU Error 154 or 155 I think why I do try it it will go about 2 min then fail.
Click to expand...
Click to collapse
Oh, that makes sense.. I got the phone two weeks after release, and finally decided to root about 3 weeks ago-ish? so me being dumb I didn't even think to look here before I did the OTA update from AT&T. So I had to do the x factor exploit to get rooted. That might be why yours isn't like mine...? I'm not 100% sure on that one.
mlaws90 said:
Yeah, I only have the unlocked bootloader, not SuperCID, I THINK, I did it a long time ago, I got the phone on release day. Could this be why? I am getting an RUU Error 154 or 155 I think why I do try it it will go about 2 min then fail.
Click to expand...
Click to collapse
That was the same way mine was. I got the 155 error. Going to run some errands after I get my phone back working again.. and give it another go later.
mlaws90 said:
Yeah, I only have the unlocked bootloader, not SuperCID, I THINK, I did it a long time ago, I got the phone on release day.
Click to expand...
Click to collapse
You can't have an unlocked bootloader without SuperCID on the AT&T branded version. Or possibly another CID besides the AT&T CID, since AT&T's CID is not allowed on HTCDev.com.
Should look like this
absolutelygrim said:
Should look like this
Click to expand...
Click to collapse
But why doesnt mine look like that , can someone upload a mmcblk0p23 for me to use, if that is possible. Mine is all Zeros and I get the 154 or 155 error on RUU.
mlaws90 said:
But why doesnt mine look like that , can someone upload a mmcblk0p23 for me to use, if that is possible. Mine is all Zeros and I get the 154 or 155 error on RUU.
Click to expand...
Click to collapse
Try extracting p23 with your phone plugged into a computer and USB debugging on
I'll give this another go later tonight, If it doesn't work I'll just downgrade my hboot and leave it alone. lol.
Myrder said:
I'll give this another go later tonight, If it doesn't work I'll just downgrade my hboot and leave it alone. lol.
Click to expand...
Click to collapse
I drowngraded hboot, changed main version and then ran the RUU just now with no problems. Weird that it isn't working for you.
mbh87 said:
I drowngraded hboot, changed main version and then ran the RUU just now with no problems. Weird that it isn't working for you.
Click to expand...
Click to collapse
First time I got ahead of myself and didn't save the mmcblk0p23... The next time, idk wtf happened. I'll downgrade hboot in a bit and then try again to see what that will do.
Myrder said:
First time I got ahead of myself and didn't save the mmcblk0p23... The next time, idk wtf happened. I'll downgrade hboot in a bit and then try again to see what that will do.
Click to expand...
Click to collapse
If you tried running it over the top of 2.20 without downgrading hboot then that would be a problem too.
I'm giving my phone to my dad and I need to return it back to stock, but I can't seem to find a tutorial/guide to get me back to stock?
Can anyone with experience point me in the right direction?
This is easy to do on Samsung phones lol, this is just my first time doing so on HTC phones. Thanks! :good:
relock the bootloader via command fastboot oem lock in fb. Then run ruu according to the firmware of your phone.
WhatTheAndroid? said:
relock the bootloader via command fastboot oem lock in fb. Then run ruu according to the firmware of your phone.
Click to expand...
Click to collapse
what is ruu? is this something i have to download?
sorry i'm such a noob
EDIT: Found out that ruu seems to be the firmware version or stock"rom" sorta. it's the executable correct?
afrojoc said:
what is ruu? is this something i have to download?
sorry i'm such a noob
EDIT: Found out that ruu seems to be the firmware version or stock"rom" sorta. it's the executable correct?
Click to expand...
Click to collapse
What software were you on before you rooted, 2.20. Because i think i have the 2.20 ruu version.
WhatTheAndroid? said:
What software were you on before you rooted, 2.20. Because i think i have the 2.20 ruu version.
Click to expand...
Click to collapse
2.20 I also used the newest root method if that matters.
htc_one_x_RUU_2.20.502.7_att_us_08022012
This should be the name of it. and this is the link i downloaded it from when i needed to ruu back to stock. If you have the all in one v 1.1 one x toolkit you should be able to lock bootloader from the command there and THEN run ruu:
this is if you are on att htc one x(evita)
Edit: link not working just go to my old thread and install ruu from the link there on post 19. http://forum.xda-developers.com/showthread.php?t=1956258&page=2
WhatTheAndroid? said:
htc_one_x_RUU_2.20.502.7_att_us_08022012
This should be the name of it. and this is the link i downloaded it from when i needed to ruu back to stock. If you have the all in one v 1.1 one x toolkit you should be able to lock bootloader from the command there and THEN run ruu:
this is if you are on att htc one x(evita)
Edit: link not working just go to my old thread and install ruu from the link there on post 19. http://forum.xda-developers.com/showthread.php?t=1956258&page=2
Click to expand...
Click to collapse
Ahh okay I see you actually do have experience xD thanks i found a link!
thank you very much man!:good:
As usual, my index thread has most anything you will ever need: http://forum.xda-developers.com/showthread.php?t=1671237
Specifically, link in Xs Magicals RUU collection under "Stock RUUs and Related" seems to be working fine.
redpoint73 said:
As usual, my index thread has most anything you will ever need: http://forum.xda-developers.com/showthread.php?t=1671237
Specifically, link in Xs Magicals RUU collection under "Stock RUUs and Related" seems to be working fine.
Click to expand...
Click to collapse
Okay last question I hope.. how exactly do i relock my bootloader using the toolkit? I can't seem to find the option. And i've searched for this too... :crying:
EDIT: FOUND A WAY!!
afrojoc said:
Okay last question I hope.. how exactly do i relock my bootloader using the toolkit? I can't seem to find the option. And i've searched for this too... :crying:
EDIT: FOUND A WAY!!
Click to expand...
Click to collapse
Did you get your phone back to stock ok?
WhatTheAndroid? said:
Did you get your phone back to stock ok?
Click to expand...
Click to collapse
Well i gotta charge it first.. doing all this exploring made my battery drop lol.
WhatTheAndroid? said:
Did you get your phone back to stock ok?
Click to expand...
Click to collapse
Worked perfectly. Thank you very much man!!