[GUIDE] Root, flash a custom recovery and/or S-OFF your Desire HD the "easy" way!
PLEASE DO NOT HOST MY FILES ELSEWHERE ALSO REPORT ERRORS ABOUT IT HERE AND NOT IN ANY OTHER THREADS!
UPDATE: Uploaded a new version with a temporary fix for if not working properly on the latest OTA?
!!!WARNING!!!
ONLY flash the bootloader (HBOOT) aka "S-OFF" if you understand what it is, what it does, what it can do and how it can brick your phone if flashing it fails.
I can not be held responsible if your phone bricks, makes nukes drop from the sky and/or makes your wife pregnant.
Assuming you have the Android SDK (adb) in working order, some basic knowledge of how to use it and experience using the console for those cases something does go tits up.
=====
Requirements: Android Terminal Emulator (from market), the archive attached to this post and a way to extract it to your SD card (file manager, PC, etc).
VISIONairy+ r12 (or higher) is as of v0.5 ONLY needed for rooting your phone, if you already have root you can skip this!
Download and extract the archive to the root of your SD card and read the included instructions (RTFM.txt).
If the first and second MD5 sums match, HBOOT is flashed correctly.
If the first and third MD5 sums match, HBOOT is not flashed at all and your phone still works like nothing happened.
If the first does not match second or third, something went wrong and you should NOT reboot your phone but seek help on the forums here!
In the last case, you could first try the hboot script again if that doesn't work something went awfully wrong and you should report back here ASAP but whatever you do ... DO NOT TURN OFF YOUR PHONE
=====
Credits goto all who made this possible: Scotty, tmzt (eMMC write), Paul (MoDaCo) (VISIONairy+ root) and adwinp (first working S-OFF post).
(If I left some person out of it just sent me a message and I will correct it)
CHANGELOG (new to old):
Revised scripts.
Failproof way of making kernel module.
Added check to see if the kernel module actually loaded correctly.
Reworked the scripts, more fail and fool proof
Updated the check script to check the kernel module first.
Added scripts to flash/restore recovery.
Got rid of not found errors for good?
Reflected the error message from loading the module is actually ok, polished the first post and RTFM.
Changed the way md5sum is invoked, now trough busybox and this should work for people who had problems with "md5sum: not found".
Fixed a major typo.
Updated with versioning, corrected some textual output and added some extra info to RTFM.
Cleaned up the first post.
Changed hboot script to reflect the original MD5 sum.
Removed recovery, get it yourself.
Revised scripts to be more fail proof.
TODO:
Polish textual output properly.
Proper check to see if kernel module loaded or is loaded already.
Good morning
What recovery.img are you flashing in the process btw?! care to let us know?
since you take a backup of the original bootloader, maybe it would be handy to create a "revert" script also, where you flash back the original recovery and original bootloader in the event that we may need to you know...
the script would then go like this
Code:
dd if=/sdcard/DHD/hboot_orig.bin of=/dev/block/mmcblk0p18
dd if=/dev/block/mmcblk0p18 of=/sdcard/DHD/hboot_check.nb0
dd if=/sdcard/DHD/recovery_orig.bin of=/dev/block/mmcblk0p21
md5sum /sdcard/DHD/hboot_orig.bin
md5sum /sdcard/DHD/hboot_check.nb0
at least thats what i think... unless the file .nb0 and .bin matters in the if=-- of--- command
EDIT**
Read and check everything at least 4 times, ask before you reboot your DHD if unsure about absolutely anything. This process worked for me after some stupidity on my part.
Again, this works but CHECK everything step of the way.
afrcom15 said:
FFS guys, read this carefully and double check everything you do B4 you reboot.
I've ended up with a 450 quid paperweight.
Dunno what I can do, probably nothing
Click to expand...
Click to collapse
did that happen using this guys script? or another way?
im holding off flashing hboot till things are a bit more settled. its hard to resist though.
i have modified the script used by sfjuocekr (so that it doesnt flash the recovery, as I see no point in that at the moment) and would rather flash from fastboot
and the script works and I can confirm s-off success
I think it's safer doing it via the VISIONary method. That's how I.did mine, and zero issues. I don't like how this says don't reboot if the checksums don't match. That's just asking for trouble.
Sent from my Desire HD using XDA App
afrcom15 said:
FFS guys, read this carefully and double check everything you do B4 you reboot.
I've ended up with a 450 quid paperweight.
Dunno what I can do, probably nothing
Click to expand...
Click to collapse
Yeah too many people rush into dangerous stuff like flashing to hboot without understanding the risks properly. I was one of those people. I am very lucky that my flash went smoothly. Feel for you.
madindehead said:
I think it's safer doing it via the VISIONary method. That's how I.did mine, and zero issues. I don't like how this says don't reboot if the checksums don't match. That's just asking for trouble.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
actually, thats BS, excuse my french.
The checksum is an extra security measure implemented to verify that the data flashed and the data that should have been flashed remain integrity. this way, you can verify in 2 steps:
1. The file you downloaded is not currupted in any way
2. The file (bootloader) flashed has flashed correctly, prior to reboot.
so actually, it is something ON TOP of the usual scripts seen here to ensure you dont brick. I need to side with the creator here.
afrcom15 said:
FFS guys, read this carefully and double check everything you do B4 you reboot.
I've ended up with a 450 quid paperweight.
Dunno what I can do, probably nothing
Click to expand...
Click to collapse
Take it back to the shop saying it died and get a replacement :3?
Well I used this method and the checksums returned were both "not found" and everything started force closing, I started to accept the fact that my phone could be bricked, but on reboot I was fine!
Sent from my Desire HD using XDA App
does this work as reliably as the first method?
i modified the scripts and included 2 more tests as well as deleted the flash of the recovery.
I can confirm the pricinple works fine, but i didnt see the point of flashing the recovery i must say. as I will fastboot flash the recovery when we have a "proper" one
I've done the permaroot and deleted visionary, so when my phone boots up now it is rooted and i have access to setcpu and such and i can change it, like the sliders, i can also use other rooted programs too.
What benefits do i stand to receive if i perform this s - off root? please.
And from what i've said am i set to do this?
Thanks.
S-Off is needed for a custom recovery image and custom roms. Essentially it turns off the MMC write protection and signature checking permanently.
Sent from my Desire HD using Tapatalk
Thyrus said:
i modified the scripts and included 2 more tests as well as deleted the flash of the recovery.
I can confirm the pricinple works fine, but i didnt see the point of flashing the recovery i must say. as I will fastboot flash the recovery when we have a "proper" one
Click to expand...
Click to collapse
Where can the modified script be found?
There seems to be little take up on this so far, I guess because it's so risky still?
Andy,
I have composed a comprehensive how-to in german for my "home-forum" after testing it.... so not sure how useful it would be for you non-german speaking ppl. but here is the link for convenience
http://www.android-hilfe.de/root-hacking-modding-fuer-htc-desire-hd/53959-guide-permant-root-mit-austauschen-des-bootloaders-visionary.html
you can manually edit the script from the creator here and delete THIS line
Code:
dd if=/sdcard/DHD/recovery.img of=/dev/block/mmcblk0p21
to avoid flashing the recovery
Here's an update on my sorry situation
CPW say send it direct to HTC, there gonna know aren't they. Phone is completely dead, no options left I'm afraid.
afrcom15 said:
Here's an update on my sorry situation
CPW say send it direct to HTC, there gonna know aren't they. Phone is completely dead, no options left I'm afraid.
Click to expand...
Click to collapse
a) Send it to HTC, they fix it for free
b) Send it to HTC, they fix it and charge you
c) Send it to HTC, they say they won't fix it
afrcom15 said:
Here's an update on my sorry situation
CPW say send it direct to HTC, there gonna know aren't they. Phone is completely dead, no options left I'm afraid.
Click to expand...
Click to collapse
Statutory consumer rights may come into play here my boy. I know that you broke it, but if you're comfortable with lying to them then I suggest you bring this up:
The retailer’s obligations
If there is an obvious fault with the item at any time within the first 6 months and it has not been caused by wear and tear or misuse, your first port of call must be the shop you bought it from. They have the responsibility to put the matter right, and should not evade this responsibility by referring you to the manufacturer in the context of a guarantee or warranty.
EDIT: This is one of the main reasons I take out insurance on my phones. If it breaks, tell them you lost it. Technically still lying but I'm paying for the privilege of that lie, and I have never had to lie to them.
Related
I had been looking into Flashing the NEW Radio recently and was put off by people saying you can easily brick your device "CAUTION" and use ADB and push this here and push this there and it gave alot of people an uneasy fealing. So now that I was schooled on how to do it the EASY WAY I figured I would pass this on to anyone needing the correct info. Always Verify your MD5 SUM Prior to installation.
1: Find the new radio of your choice. Make sure it is named PD15IMG!! ( It should be allready )
2: Use an MD5Sum tool, such as ManD5 from the Android Market to compare the MD5 hash of the original download to the MD5 of your downloaded radio image. FLASHING A CORRUPTED RADIO IMAGE WILL BRICK YOUR PHONE.
3: Place the PD15IMG radio zip file onto your SD card (just like you would a new ROM).
4: Boot into H-BOOT. I use quick boot from the market (just push Bootloader button)
5: Once in H-BOOT select BootLoader. it will ask you to apply update? Yes
6: Let file load completely. you will see a status bar on top right of screen.
7: It will prompt you to reboot... do so and let it load. you will now have a new radio.
This turned out to be so easy.
But as with all the different ways to do somthing, you do this @ your own risk. I cant be responsible if YOU F-UP!!
With that being said, Happy EASY Radio Flashing.
I used this exact Method on my MT4G and it worked Flawless. NOTE: I did Delete the PD15IMG file on SD after proper install, so I would not have any issues with the file after installation. Also so it would'nt get confused with other radio files.
NOTE: It doesnt matter if you used G-Free Method to ROOT, or VISIONary/ROOT.SH method. This will work. I do recommend that you have the ENG. BOOTLOADER.
Correct MD5's for the New Radio's:
•26.03.00.04
md5: ea7a58f16a6f9a7d8ffe96d42db10485
•26.03.02.26 (Stock)
md5: e4e7cb2e5bf58a5222cb1f8ae91499e1
•26.08.04.30
md5: 3d054d4bdbb0e6b81954e5742c8ba24f
•26.09.04.26
md5: f27e4686302fa7e6a72965f80495df44
It's not that people are trying to scare you by going the adb route to install the radio, it's just that you can check md5sum easily that way. If you download a corrupted file and try to flash it, YOU WILL BRICK YOUR PHONE. This method is fine for people who are familiar with flashing on android but to noobs it's very dangerous. I think you should add to op that you can download an app from the market like Android File Verifier for free to check md5sum, that way someone doesn't try your method and end up bricking their phone. And believe me, it its very possible to download a corrupted file. Just the other day I went to flash the newest radio, I downloaded, checked the md5sum and it wasn't even close, so I deleted it, downloaded from the same link and got the correct one on second try. If I would have flashed without verifying, I would have an expensive paper weight on my hands. Better to be safe than sorry!
Sent from my HTC Glacier using XDA Premium App
I been wanting to flash a new radio, but I'm not sure if I can because I went with the visionary and root.sh route and I read that s-off with radio is different with being just s-off. So, Im wondering, is still possible to flash a radio without going thru the g-free way?
vabeach454 said:
1: Find the new radio of your choice. Make sure it is named PD15IMG!!
2: Place the PD15IMG radio zip file onto your SD card (just like you would a new ROM).
3: Boot into H-BOOT. I use quick boot from the market (just push Bootloader button)
4: Once in H-BOOT select BootLoader. it will ask you to apply update? Yes
5: Let file load completely. you will see a status bar on top right of screen.
6: It will prompt you to reboot... do so and let it load. you will now have a new radio.
Click to expand...
Click to collapse
That is horrible advice. Your steps skip verifying the files MD5 signature. If you try to flash a radio from a corrupt file, you will brick your phone. The chances of a bad download a low, but I would never ever risk it...
Also, the method above is the exact same actual flashing method as what's in the official radio thread in the Dev section. You just use another method to move the file to your SD and skip the MD5 verification. If ADB scares you so much, you can always use an app like ManD5 instead. Whatever method you use, verify the MD5 before flashing!
Yes visionary will allow for radio flashing. I'm running sense 3.0 virtuous, newest videotron radio. All with visionary, never touched gfree on this device.
Sent from my HTC Vision using XDA App
I totally agree with doing it the easy way, but not at the risk of skipping the step on verifying md5. Adb is essentially doing the same thing as dropping the file onto root of sd anyways. Run the verifier and then complete original steps. Happy flashing!
Sent from my HTC Glacier using XDA App
TeeJay3800 said:
That is horrible advice. Your steps skip verifying the files MD5 signature. If you try to flash a radio from a corrupt file, you will brick your phone. The chances of a bad download a low, but I would never ever risk it...
Also, the method above is the exact same actual flashing method as what's in the official radio thread in the Dev section. You just use another method to move the file to your SD and skip the MD5 verification. If ADB scares you so much, you can always use an app like ManD5 instead. Whatever method you use, verify the MD5 before flashing!
Click to expand...
Click to collapse
I been having this app for a while now and never figured out how to use it lol.
TeeJay3800 said:
That is horrible advice. Your steps skip verifying the files MD5 signature. If you try to flash a radio from a corrupt file, you will brick your phone. The chances of a bad download a low, but I would never ever risk it...
Also, the method above is the exact same actual flashing method as what's in the official radio thread in the Dev section. You just use another method to move the file to your SD and skip the MD5 verification. If ADB scares you so much, you can always use an app like ManD5 instead. Whatever method you use, verify the MD5 before flashing!
Click to expand...
Click to collapse
ADB doesnt scare me!! It sure does scare alot of people that are unsure how to use it. You guys are correct and I will add to the OP The APP that shows how to find your MD5 SUM.
But really Bashing me for this EASY WAY to do things is pathatic!! Go Troll somewhere else.
The Method here is not the same as the radio OP. That OP is ADB specific!! Get your FACTS Straight!! I was done in 2 Minutes doing it this way.
The only thing I ever really used ADB for was to Flash new splashscreens and even now you can do it with terminal emulator.
Thanks! I, myself was afraid to flash it but your way totally was a piece of cake! Don't mind the simple people.
Sent from my HTC Glacier using XDA Premium App
vabeach454 said:
ADB doesnt scare me!! It sure does scare alot of people that are unsure how to use it. You guys are correct and I will add to the OP The APP that shows how to find your MD5 SUM.
But really Bashing me for this EASY WAY to do things is pathatic!! Go Troll somewhere else.
The Method here is not the same as the radio OP. That OP is ADB specific!! Get your FACTS Straight!! I was done in 2 Minutes doing it this way.
The only thing I ever really used ADB for was to Flash new splashscreens and even now you can do it with terminal emulator.
Click to expand...
Click to collapse
I really hope you were talking about the other guy and not me. I wasn't bashing or trolling, just stating facts. Android File Verifier is really easy to use, just open app, find file, then long press the file and select check md5sum. I agree that your way is easier, just not as safe, unless you add some sort of way to verify the file.
Edit: I now see that you quoted the other guys post lol
Edit again: lol just seen updated op too!
I'm trying to protect users from screwing up their phones and you accuse me of trolling? Give me a break.
YOU need to get your facts straight. The official radio thread uses the exact same method of flashing as your instructions (through hboot). The only difference is you omit the important step of verifying the MD5.
Sent from my HTC Vision using XDA Premium App
sckboy78 said:
Thanks! I, myself was afraid to flash it but your way totally was a piece of cake! Don't mind the simple people.
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Thanks... I am glad I could help. This way is the easiest I know of and I hope it will help alot of people to flash the new Radio's we have the EASY WAY.
TeeJay3800 said:
I'm trying to protect users from screwing up their phones and you accuse me of trolling? Give me a break.
YOU need to get your facts straight. The official radio thread uses the exact same method of flashing as your instructions (through hboot). The only difference is you omit the important step of verifying the MD5.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Go to another thread allready. Your negativity is not needed here. I am trying to HELP People With this thread. Read the OP it is updated for Users to Verify There MD5.
vabeach454 said:
Go to another thread allready. Your negativity is not needed here. I am trying to HELP People With this thread. Read the OP it is updated for Users to Verify There MD5.
Click to expand...
Click to collapse
I'm glad I was able to spare users from bricking their phones as per your original instructions.
AHHHH finally got the courage to do it. I'm now on 26.08.04.30, I'll do a bit of testing over a couple days and see how it goes.
I used a simple MD5 checker on my pc and then android file verifier on my phone, then did it. I notice that I'm getting 2 bars of H in my room, usually get weak 3g or edge.
kimbernator said:
AHHHH finally got the courage to do it. I'm now on 26.08.04.30, I'll do a bit of testing over a couple days and see how it goes.
I used a simple MD5 checker on my pc and then android file verifier on my phone, then did it. I notice that I'm getting 2 bars of H in my room, usually get weak 3g or edge.
Click to expand...
Click to collapse
Did you use this method? I am trying to show everyone ( New & Experienced ) how easy it really is. I am using the Newest Radio 26.09.04.26 and getting Full bars on H.
vabeach454 said:
Did you use this method? I am trying to show everyone ( New & Experienced ) how easy it really is. I am using the Newest Radio 26.09.04.26 and getting Full bars on H.
Click to expand...
Click to collapse
That's not a bad idea. I want you to know the only reason I said anything is because skipping the file integrity verification is a bad idea. There's nothing wrong with avoiding using ADB if you can accomplish the same thing with other methods, but I know people who have bricked their phones by flashing a radio from a file that was corrupt (they didn't check the MD5, one guy with an OG Droid and one with an Incredible). The guy who posted the original radio thread knows what he's talking about, that's why he included that very important step in his procedure. So all I was doing was pointing out what missing, and probably came across too harsh.
I wasn't trying to troll or start a flame war or anything. Just trying to help others in the same way as I've been helped over the years. As it stands now, your procedure is indeed easier and safe as well.
vabeach454 said:
Did you use this method? I am trying to show everyone ( New & Experienced ) how easy it really is. I am using the Newest Radio 26.09.04.26 and getting Full bars on H.
Click to expand...
Click to collapse
You can flaunt this method all you want, but it's really just the same as the ADB one, just no commands and a different form of checking the MD5. Not to detract from the fact that you made doing this much more understandable and a little less daunting which was very good of you to do. But in any case, yes. I used this method.
TeeJay3800 said:
That's not a bad idea. I want you to know the only reason I said anything is because skipping the file integrity verification is a bad idea. There's nothing wrong with avoiding using ADB if you can accomplish the same thing with other methods, but I know people who have bricked their phones by flashing a radio from a file that was corrupt (they didn't check the MD5, one guy with an OG Droid and one with an Incredible). The guy who posted the original radio thread knows what he's talking about, that's why he included that very important step in his procedure. So all I was doing was pointing out what missing, and probably came across too harsh.
I wasn't trying to troll or start a flame war or anything. Just trying to help others in the same way as I've been helped over the years. As it stands now, your procedure is indeed easier and safe as well.
Click to expand...
Click to collapse
Cool... I should have added it from the start because I do know better, but I was reminded to add to check MD5 Promptly. I am not trying to upstage anyone saying it's the only method, but IMHO is the most easy & fastest way I have seen. As you can see a couple of people have tried it and agree. I think we should all be able to get along in this thread as its is only an attempt at Helping people out. Mainly newer members. Peace...
Sent from my HTC GLACIER using XDA Premium App
I agree. There is a way to say things and a way to help people without being pompous and rude. Maybe post "important correction" instead of telling someone they're giving "horrible" advice in italics.
I am poking around the latest official OTA update (get it here).
I am trying to see if there is anything useful for aftermarket roms. I will post
here my findings, if any, and all the questions that pop to my mind. Hopefully
someone in the community will have answers.
The updating script does the following:
1) several checks on bootloader/recovery/cid/device version
2) copy fotaBoot to /data/system/fotaBoot to trigger some changes at reboot
3) checks on files to be patched
4) delete several files from /data (notably adio_checksum, DxDr,
SuplRootCert_injected)
5) delete lots of files form /system
6) apply patches
7) copy files into /system
8) set permissions
9) flash firmware.zip via
Code:
write_firmware_image("PACKAGE:firmware.zip", "zip");
Among the files being modified there are a couple of firmwares (yamato_pfp.fw
yamato_pm4.fw). I do not have them on my system (I run CM7) and I have no idea
which piece of hardware they refer to. There is also an app whose purpose I
ignore (HTC-DPM-GB-2.3-48637-11.1.apk) and a mysterious recovery.img in /system
(more on this later).
Does anyone know the exact procedure by which firmware.zip is flashed? Will any
check be performed on it? Its content is the following:
* android-info.txt: ASCII file with some version numbers.
* boot.img: should be the new kernel+ramdisk; I tried booting it with few
expectations and indeed it wont boot with a non-sense /system
* hboot_8x60_DOT_1.45.0013_20111121_signedbyaa.nb0: the new bootloader; I see no
reason to flash this unless it provides some new features.
* radio.img: fat image with radio files (should be safe to flash)
* rcdata.img: ???
* recovery.img: this won't boot; may it require the above mentioned recovery.img?
Anyway this is completely useless
* rpm.img: ???
* sbl1.img: ???
* sbl2.img: ???
* sbl3.img: ???
* tz.img: ???
Anyone has ideas on what the other files are? I assume that if we avoid flashing
hboot we will always have fastboot available to us and S-OFF to flash anything
we would like to, correct? Revolutionary team can you please explain how you
make the phone S-OFF once your exploit gives you the right privileges? Will any
of those files affect it? Has anyone here any idea of which partitions should
they be flashed to?
As I said I tried to boot both recovery.img and boot.img to get a config.gz and
kernel version with scarce success. I'd like to see whether they made some modifications to the
kernel which improved battery life. I think I will repack the new kernel with
CWM recovery and get the info from there.
Ideas of things to poke at? Comments? Helpful insights?
Related info: here .
sbl*.img might be the boot loader. (secured/secondary boot loader???) but why in 3 separate chunks?
More info: here
rcdata.img is text; it should be the configuration of the radio but if I check the content of the corresponding partition (mmcblk0p18) on my phone there is a lot of binary junk together with the small amount of text. The options are the same except for one (AGPSNVSetting) that is missing in the updated rcdata.img
Code:
# cat /dev/block/mmcblk0p18 | strings | tail -n 9
QCT_UMTS_RADIO_VER=1
DisH=2
AGPSNVSetting=1
EnDTM=0
MSCMode=10
HSDPACat=10
HSUPACat=6
GEA3=0
QCT_UMTS_RADIO_END=1
I know probably the biggest request from the community is to figure out how to root the update; it seems that the Rev. team has been notified that the exploit they used before seems to have been patched in this update.
Also very profitable would probably be zips for the new kernel and radio, if possible. Early reports have indeed been of better battery life, and also higher quadrant scores.
Anyway, many thanks for this thread, and for looking at the update
Etn40ff said:
Among the files being modified there are a couple of firmwares (yamato_pfp.fw
yamato_pm4.fw).
Click to expand...
Click to collapse
Just a shot in the dark, but Yamato is refered to here:
http://code.google.com/p/synergy-ki.../system/etc/adreno_config.txt?spec=svn41&r=41
It seems to have something to do with the adreno chipset...
There's a Pre Rooted Version of the OTA Update on Rootzwiki. I would imagine those on XDA would be rooted all ready. I understand trying to find a way to Root the OTA Update for those who had it before they could root. But wouldn't a simple Temp Root, then Downgrade work? That's what I had to do with my G2 and G1.
Sent from my MyTouch_4G_Slide using xda premium
Litesorrows said:
There's a Pre Rooted Version of the OTA Update on Rootzwiki. I would imagine those on XDA would be rooted all ready. I understand trying to find a way to Root the OTA Update for those who had it before they could root. But wouldn't a simple Temp Root, then Downgrade work? That's what I had to do with my G2 and G1.
Sent from my MyTouch_4G_Slide using xda premium
Click to expand...
Click to collapse
the version on Rootzwiki isn't the newest update, the one that just came out 3 days ago. and the newest update has proven impervious even to temp-root so far. the only way to downgrade is if you were S-OFF before updating. there is a thread on this in the general section.....
If you updated, please view this thread.
http://forum.xda-developers.com/showthread.php?t=1405859
I had pulled the new google talk app and made it flashable on request, here's the link:
Gtalk update
There are a couple others if anyone wants them - deskclock, wifi calling, t-mo mall and carbon backup, netflix, and two logging utilities.
The rest is all small updates to a lot - what I wanted to look into first were the GPS updates to make sure my patch stays as current as possible.
You can either pull apart the package directly, or flash the update and do an adb pull to grab new stuff - backup guide in my sig tells you all about using the adb pull command.
Now that we know you can rewind the changes and get root back after the update, either should be fine. I've been going through the download zip, but haven't had much time at my workstation.
I have a couple emergency shifts to work, kept me offline yesterday & today, I'll check back on a break later and see if I have anything else to add.
Sent from my Bulletproof_Doubleshot using xda premium
Blue6IX said:
I had pulled the new google talk app and made it flashable on request, here's the link:
Gtalk update
There are a couple others if anyone wants them - deskclock, wifi calling, t-mo mall and carbon backup, netflix, and two logging utilities.
The rest is all small updates to a lot - what I wanted to look into first were the GPS updates to make sure my patch stays as current as possible.
You can either pull apart the package directly, or flash the update and do an adb pull to grab new stuff - backup guide in my sig tells you all about using the adb pull command.
Now that we know you can rewind the changes and get root back after the update, either should be fine. I've been going through the download zip, but haven't had much time at my workstation.
I have a couple emergency shifts to work, kept me offline yesterday & today, I'll check back on a break later and see if I have anything else to add.
Sent from my Bulletproof_Doubleshot using xda premium
Click to expand...
Click to collapse
could i get deskclock, wifi calling, and netflix
Yamato is gpu proprietary files. U would use them in a compile against source code for the improvements. I would say kernel fixes would be the main thing if reports are better quadrant and battery life
Sent from my MB525 using XDA App
I flashed the t-mobile signed stock rom PP59IMG.zip through the bootloader then proceeded to download the OTA's. After that I placed the new recovery image in the appropriate place and rebooted bootloader to prepare pushing the recovery through fastboot. What I noticed is that even after installing the OTA in a unrooted totally stock rom, S-off remains, however where "revolutionary" once was written now displays "**Locked**" , so apparently HTC has managed to relock the bootloader even though it shows S-off. It's not totally locked, as I had to reflash the PP59IMG.zip to downgrade hboot again so that I could reuse the revolutionary tool to flash the 4.0.0.8 recovery, then install CWM to update the recovery. As long as "Locked" was sitting where "revolutionary" normally is, I found it impossible to use fastboot, so my guess is security remains off but fastboot is locked. Just my guess anyway.
Where did you get the stock/signed T-Mo PP59IMG.zip? Can't find it anywhere here. Thanks.
monakh said:
Where did you get the stock/signed T-Mo PP59IMG.zip? Can't find it anywhere here. Thanks.
Click to expand...
Click to collapse
Link in quote below:
yogi2010 said:
sure Blue, it is pretty much the usual...
To undo the update/restore the stock firmware that came with the phone:
(Note: this will only work if you are still S-OFF even tho you have the new HBOOT version. If you are S-ON with the new HBOOT, then at this time there is no known way to revert... hopefully we can get the devs. of Revolutionary, etc, to update the root methods. Also, if you want to update just to check it out, make sure to turn S-OFF first if you'd like to give yourself the option to revert later.)
1. Download the stock firmware package from here: http://forum.xda-developers.com/showthread.php?t=1178082
2. Rename it PG59IMG.zip and put it on the root of your sdcard.
3. Boot into the bootloader('adb reboot bootloader' or power down the phone then hold volume down + power), let it read the update package, and press 'volume up' to update when prompted.
4. At the end it will prompt you to press Power to reboot. It scared me because when i pressed Power, the screen went off and seemed to not come back on, so i pressed power once again, and it booted into the system.
That's it! Just remember that if you do this, it will of course erase all your data... your phone will be like it was out of the box.
Click to expand...
Click to collapse
I'm not sure if this helps anyone, but here is the boot.img taken from my nandroid of the newest OTA ROM:
http://db.tt/GHfzWNIj
come to think of it, looks like you might already have this in the OTA zip... although this one is a bigger file...
Two questions:
1. How do you flash this update? When I click the HTC Update, it gave me the ~5MB update, however not the ~40MB one. So is there a way to manually flash it?
2. Is there a way to doing so without loosing the recovery and root?
Sinfamy said:
Two questions:
1. How do you flash this update? When I click the HTC Update, it gave me the ~5MB update, however not the ~40MB one. So is there a way to manually flash it?
2. Is there a way to doing so without loosing the recovery and root?
Click to expand...
Click to collapse
You can download the update and run it manually. I can't remember if I renamed it update.zip and flashed it through stock recovery or used the bootloader.
If it was the bootloader, rename the downloaded zip to PG59IMG.zip, put it on the root of your sdcard and boot into the bootloader. The device's screen should prompt you with install instructions.
As for keeping root and recovery, no. As long as you are S-OFF *before* doing this, however, you can re-flash a custom recovery and re-root using these instructions: http://forum.xda-developers.com/showthread.php?t=1433805
Yeah, the update flashed nicely thru the stock recovery. I learned once you get to the recovery screen, you press volume up + power to get the options to show up.
This is coming from an apprehensive stock HTC Sensation user. I long to have AOSP ICS or CM9, but I must have a 100% success rate. I just can't mess things up, as there is no time to have the phone down for even an hour.
So what causes them to brick? I hear you all say to follow the directions, but what if they aren't clear? It's like when you try to teach someone something you have done for a long time; there are things that you just assume you do that are not spoken of.
What are things that are always assumed when you are in the process of rooting and changing ROMs? Trying a new kernel? (For instance, always superwipe here, but only a dalvik there...)
Thank you very much.
The directions dont leave out any steps. The guides are very thorough.
Bricking is caused basically when you screw up the ability of the phone to boot into the bootloader or accept commands from a computer. Many other things will prevent the phone from working, but other stuff is usually easily fixed. The big problems are caused by something going wrong while the bootloader is being altered. If you kill the bootloader, there is no bootloaderrr to get to where you can fix things.
But on the sensatio you almost have to try to do that by doing something stupid like pulling the battery while the bootloader is being modified. The software you use to root this phone is fairly idiot proof and does all the work for you.
However.....the first time you root a phone you will go really slowly (as you should) and your down time will be at least an hour from the time you first start to the time when you have a working phone again.
It can be done in as little as 15 minutes, but for your first time you will be super meticulous about everything and itll take an hour.
Sent from a rebel ship by storing the message in an R2 unit. (Help me, XDA. You're my only hope)
Honestly, just don't mess up any commands in revolutionary.io - seriously, double, triple, then quadruple check those commands - those who are inexperienced in command line tend to miss a thing or two.
Then, if for whatever reason you have to update the firmware, make sure you flash the right thing, and make sure you don't pull the battery while you're doing it.
Those two things should give you that 100% success rate, then again, nothing's ever 100% certain.
What are things that are always assumed when you are in the process of rooting and changing ROMs? Trying a new kernel? (For instance, always superwipe here, but only a dalvik there...)
Click to expand...
Click to collapse
When changing roms, wipe data + cache. If you want, you can also wipe system and boot but it's not necessary. When flashing a kernel, wipe cache + dalvik cache. When it comes to rooting and what not in general, anything you flash in recovery is 100% safe. As in, worst case scenario, you'll have to reinstall your current rom. However, you'll never accidentally flash something from recovery that will kill your bootloader. Think of it like so:
BOOTLOADER > RECOVERY > ROM
The bootloader is the lowest level interaction you have. It's like your PCs BIOS. Recovery is kind of like a mini OS that can change the main OS. The rom is the OS you have installed.
Oh man, you guys are great! Starting to lose my anxiety about rooting now...
In what cases would you be altering the bootloader, or have the opportunity to corrupt it?
When you have a file you want, do you always flash it? To where? What files need to be under /root? I have heard of flashable zip files; flashable as opposed to what?
What is the best method of data backup (Besides a full nandroid)? Do you recommend Titanium Backup (Pro)? Does it always work? Is this a smarter alternative?
I really do apologize for the amount of questions. I want to be totally confident of knowledgeable of what I am doing.
Much thanks!
Titanium is great. Use is.
You will modify the bootloader during thevs off process. (Takes just seconds)
You may have to downgrade the bootloader if you have version 1.27.
Dont use the htc unlocker. Use revolutionary (search for more details)
Flashable zips are what you will use to install roms and kernels. You will install these from the recovery module.
The bootloader is where you will install new firmware or radios.
Sent from a rebel ship by storing the message in an R2 unit. (Help me, XDA. You're my only hope)
forum.xda-developers.com/showthread.php?t=1192300
Everything you need to know.
But use 4ext instead of Clockwork when you are done. (Simple market download)
Sent from a rebel ship by storing the message in an R2 unit. (Help me, XDA. You're my only hope)
Thank you so much Skipjacks! I plan on using 4ext if I root. So, when would there be non-flashable zip files? I have heard people say "I'll wait until their is a flashable zip file". So what is the difference? (I hope I have enough thanks left to thank you after this. )
So I know there's been some controversy and scares going around about the US version, since it JUST came out. I'm here to calm you guys down. I have now rooted mine, flashed an interim CWM touch version (not permanent) and have flashed a ROM......ALL successfully.
Here's what I did:
UNLOCKING:
Unlock your bootloader by registering at HTCdev.com and following the unlock instructions. Under device, choose "All other devices", as the One S is not yet listed. It'll walk you through getting your unlock token and flashing it.
ROOTING
Follow Paul O Brien's instructions on rooting your phone. I flashed the r3 superboot file he had. The first time it didnt take and just booted the phone back up. Second time it took, and seems to have stuck, at least for apps. Please note that my phone says *TAMPERED* along with the *UNLOCKED* notification. I have no idea what that means exactly, but everything works great for me.
This means if you dont want to leave Sense but want to get the tons of useless and annoying T-Mobile and other bloatware apps out, you can. T-Mo are dicks and make almost 100% of the apps on it by default SYSTEM apps, therefore unremovable. So you'll need root and Titanium Backup to freeze or delete them. I'd recommend freezing the non-TMo one's just in case.
FLASHING ROMS
1. Flash Paul O Brien's intermin CWM touch version. You MUST use this interim CWM version for the moment, as the others do not work properly. Some things like USB mount dont work in this interim version, but the important functions like wipe and flash, backup and restore, and restart do work. The CWM recovery seems permanent, based on my initial trials, so no worries about reflashing it each restart.
2. Flash your ROM of choice from Clockworkmod Recovery. I'm using Black Dragon right now, but there are others out there as well. I'm personally looking forward to CM9, but its a little ways away, usability-wise.
So there you have it, all you US guys. Don't be afraid to mod your phone. Remember all the warranty void disclaimers as always. I'm not responsible for you bricking your phone. This is just my experience in just under 24hrs of use. Things are looking good for the One S.
bump... i see US users still asking.
Mods, can we perhaps sticky this post of mine? I don't want to take credit for the actual methods of rooting, since Paul O Brien and others deserve that credit, but I think it'd be helpful for US users, since many don't know whether or not the international method works.
That, or perhaps editing the Intl guides to make it clear that the US version accepts the same methods and ROMs.
Worked great for me
Sent from my HTC VLE_U using xda premium
So if we root and flash a custom ROM is there any way to get the phone back to factory state, and get rid of the *TAMPERED* and *UNLOCKED* notification??
Did anyone else get a bit of a sad chuckle out of the first step in the instructions being "remove and reinsert battery"?
cyberchuck9000 said:
Did anyone else get a bit of a sad chuckle out of the first step in the instructions being "remove and reinsert battery"?
Click to expand...
Click to collapse
Great, now my blisters on my fingers will heal.
But still.... I cannot imagine not needing a batt pull.
nickmv said:
Mods, can we perhaps sticky this post of mine? I don't want to take credit for the actual methods of rooting, since Paul O Brien and others deserve that credit, but I think it'd be helpful for US users, since many don't know whether or not the international method works.
That, or perhaps editing the Intl guides to make it clear that the US version accepts the same methods and ROMs.
Click to expand...
Click to collapse
+1
androidcues said:
Great, now my blisters on my fingers will heal.
But still.... I cannot imagine not needing a batt pull.
Click to expand...
Click to collapse
If you need to perform a hard reset on the One S, you hold down the power button for about 7-10 secs.
First of all, thanks for this thread...I used the HTC One S All in one tool kit to unlock my phone, unfortunately I miss understood one of the directions(#5) and stopped using the tool kit and followed another thread, much to my surprise, my bootloader is unlocked, hooray My question is, how do I get back to the original state if that is possible? The reason I ask, is I would like to go back and do it correctly...I used better terminal emulator to see if I had root, but all I got was the $ sign instead of the # sign So I would like to start over...
Thanks in advance for the help
I'm honestly not sure what the procedure is for relocking an HTC bootloader. Perhaps do some Google research on some of the latest models, and I bet you'll find something.
That being said, once you unlock the bootloader a single time, the best you can do is go to **RELOCKED** state. You'll never get back **LOCKED**. Once it's gone it's gone. I'm curious about the **TAMPERED** message though. That's an ugly word.
not sure what exactly went wrong.
somehow flashed CWM and now thats the only thing my phone will boot to, even after re-flashing the stock recovery.
can't get the phone to turn on, only CWM every single time.
suhailtheboss said:
not sure what exactly went wrong.
somehow flashed CWM and now thats the only thing my phone will boot to, even after re-flashing the stock recovery.
can't get the phone to turn on, only CWM every single time.
Click to expand...
Click to collapse
Uh oh that doesn't sound good
Sent from my HTC VLE_U using xda premium
yeah, tried reflashing both CWM & stock recovery. phone still boots to CWM everytime.
Luckily i can still access the phone via ADB, (while in recovery) so i'm sure i'll be able to sort it out. just need to take a fresh crack at it tomorrow. gonna switch back to my galaxy nexus tonight. (oh wait, i dont have any other phones that use microsim)
haha.
Hmm, interesting. Did you flash the interim recovery that Paul O Brien posted, and not another version? Just wanna make sure. I've heard of this happening in my past experience with the Nexus S, but I can't recall what the deal was. Regardless, I don't think you're in trouble. As with your GNex, it's very hard to completely brick the device unless you flash perhaps a bad hboot file, however I'm not really familiar with HTC devices.
This is my first HTC so I'm still trying to learn how the hboot and other processes work together. Sry to hear you had bad luck.
UPDATE: You should try the root install script. It tells the phone to boot after install. That might get you booted atleast.
Some thoughts:
1. Flash the stock recovery back and reflash CWM
2. Clear cache and dalvik within CWM, and make sure to use the 'Reboot System' option if you aren't already.
From what I can tell, your "boot-to-recovery" flag is set on the phone, and isn't getting cleared.
nickmv said:
So I know there's been some controversy and scares going around about the US version, since it JUST came out. I'm here to calm you guys down. I have now rooted mine, flashed an interim CWM touch version (not permanent) and have flashed a ROM......ALL successfully.
Here's what I did:
UNLOCKING:
Unlock your bootloader by registering at HTCdev.com and following the unlock instructions. Under device, choose "All other devices", as the One S is not yet listed. It'll walk you through getting your unlock token and flashing it.
ROOTING
Follow Paul O Brien's instructions on rooting your phone. I flashed the r3 superboot file he had. The first time it didnt take and just booted the phone back up. Second time it took, and seems to have stuck, at least for apps. Please note that my phone says *TAMPERED* along with the *UNLOCKED* notification. I have no idea what that means exactly, but everything works great for me.
This means if you dont want to leave Sense but want to get the tons of useless and annoying T-Mobile and other bloatware apps out, you can. T-Mo are dicks and make almost 100% of the apps on it by default SYSTEM apps, therefore unremovable. So you'll need root and Titanium Backup to freeze or delete them. I'd recommend freezing the non-TMo one's just in case.
FLASHING ROMS
1. Flash Paul O Brien's intermin CWM touch version. Some things like USB mount dont work, but the important functions like wipe and flash and restart do. The CWM recovery seems permanent, based on my initial trials, so no worries about reflashing it each restart. I cant speak for the non-interim solutions, but from what I can gather, they are problematic, so avoid them for now.
2. Flash your ROM of choice from Clockworkmod Recovery. I'm using Black Dragon right now, but there are others out there as well. I'm personally looking forward to CM9, but its a little ways away, usability-wise.
So there you have it, all you US guys. Don't be afraid to mod your phone. Remember all the warranty void disclaimers as always. I'm not responsible for you bricking your phone. This is just my experience in just under 24hrs of use. Things are looking good for the One S.
Click to expand...
Click to collapse
Is this part a must? Would you mind PM'ing me with how to do this part if it's a must? I have Unlocked and rooted my phone, just waiting for a good ROM to come by.
Thongvilay said:
Is this part a must? Would you mind PM'ing me with how to do this part if it's a must? I have Unlocked and rooted my phone, just waiting for a good ROM to come by.
Click to expand...
Click to collapse
That step is only if you want to flash ROMs, or need to wipe cache, dalvik, etc. CWM is used for flashing and recovery/backup purposes. If you're not using ROMs yet, then you have no need for it.
nickmv said:
Hmm, interesting. Did you flash the interim recovery that Paul O Brien posted, and not another version? Just wanna make sure. I've heard of this happening in my past experience with the Nexus S, but I can't recall what the deal was. Regardless, I don't think you're in trouble. As with your GNex, it's very hard to completely brick the device unless you flash perhaps a bad hboot file, however I'm not really familiar with HTC devices.
This is my first HTC so I'm still trying to learn how the hboot and other processes work together. Sry to hear you had bad luck.
UPDATE: You should try the root install script. It tells the phone to boot after install. That might get you booted atleast.
Some thoughts:
1. Flash the stock recovery back and reflash CWM
2. Clear cache and dalvik within CWM, and make sure to use the 'Reboot System' option if you aren't already.
From what I can tell, your "boot-to-recovery" flag is set on the phone, and isn't getting cleared.
Click to expand...
Click to collapse
thanks for the tips, i had tried clearing cache/dalvik within CWM and it still would not work. and yes i did flas the interim CWM from paulobrien
luckily the phone would work via ADB while in CWM. So i pushed three different ROMS to the phone, at first each oen would lock up and reboot within 20 seconds of doing anything. I then went back into recovery & wiped data/cache/dalvik maybe 10 times out of sheer frustration. Then re-flashed a fresh copy of black_dragon_v4.0, didnt do anything after boot. just let it sit there till this morning.
now the phone seems to be working perfectly...
so hopefully if anyone encounters this problem my last couple posts will help them out!
suhailtheboss said:
thanks for the tips, i had tried clearing cache/dalvik within CWM and it still would not work. and yes i did flas the interim CWM from paulobrien
luckily the phone would work via ADB while in CWM. So i pushed three different ROMS to the phone, at first each oen would lock up and reboot within 20 seconds of doing anything. I then went back into recovery & wiped data/cache/dalvik maybe 10 times out of sheer frustration. Then re-flashed a fresh copy of black_dragon_v4.0, didnt do anything after boot. just let it sit there till this morning.
now the phone seems to be working perfectly...
so hopefully if anyone encounters this problem my last couple posts will help them out!
Click to expand...
Click to collapse
Wow, I have no idea dude. That sounds kinda crazy. Hopefully all will be well in the future and you won't come across it again.
the only variable i can think of is that i did have the phone about a week before launch. HTC mailed it to me directly.
I thought maybe that had somethign to do with it, but as far as i can tell the phone was the final shipping version.
I sent you a PM, trying to find a solution.
OUT OF DATE USE THE ONE CLICK 1.85 ROOT TOOL IN THE FORUMS
As the ROM chefs go to work, we want to be sure that we are ready to flash the ROMs when they come to be available! This guide will help you set up your phone so that you can flash custom ROMs.
After this process you will have a phone on the latest firmware (1.85 at the moment) with bootloader unlock, rooted, and busybox installed.
This guide assumes you are on a root friendly firmware (as of now, it is firmwares 1.82.502.3 and below).
This is really going to be done in a four step process. First we need to root the device in order to access the place where the CID is stored so that we can change it and get unlocked. After changing the CID, we can unlock via htcdev.com. Then we can go on to installing a custom recovery and finally rooting!
From there I will give you some tips on installing ROMs.
NOTE: THIS PROCESS IS EXTREMELY DANGEROUS. IT MAY BE A BIT CONFUSING. READ OVER THE STEPS BEFORE STARTING. IF YOU DO NOT THINK YOU WANT TO RISK YOUR DEVICE BECOMING A BRICK THEN DO NOT ATTEMPT THIS. THIS VERY EASILY COULD RUIN YOUR DEVICE.
BACKUP EVERYTHING BEFORE STARTING AS EVERYTHING ON YOUR DEVICE WILL PROBABLY BE WIPED.
I, XDA, AND THE ORIGINAL TOOL CREATORS DO NOT TAKE RESPONSIBILITY FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. IT IS SOLELY YOUR RESPONSIBILITY FOR WHAT YOU DO TO YOUR DEVICE.
Click to expand...
Click to collapse
Your warranty will be void if you unlock the bootloader. If you just root though then you can return to 100% stock by running the RUU.
This guide is for Windows only at the moment though I will try to post Mac and Linux guides at some point.
ORIGINAL TOOL THREADS:
One Click Root for 1.82 and below: http://forum.xda-developers.com/showthread.php?t=1644167
Spoof CID Script: http://forum.xda-developers.com/showthread.php?t=1672284
I will try to keep this as up to date as possible! Taking a visit to the index of the development forums (http://forum.xda-developers.com/showthread.php?t=1671237) is also a good idea!
Last Updated: 5/28/12
0. Getting the prerequisites:
Download the package at the bottom of the first post to get started.
Extract the package somewhere you will remember (like on your desktop).
Connect your device via USB and make sure you have USB Debugging enabled under settings.
Click to expand...
Click to collapse
1. Root your device
1. Open the folder you downloaded and navigate to the "root" directory.
2. Double click on the root-windows.bat file
3. Let the root run and do not touch your device. It will reboot several times- do not touch it or you may brick your device. Just let it do its thing and eventually after around 3 minutes you will have a rooted device in your hand.
Click to expand...
Click to collapse
2. Get the unlock token
In order to unlock the bootloader we will need to change a value called the CID. This will allow the htcdev.com site to unlock our phones.
1. Go to the downloaded folder and go to the "change_cid" folder.
2. Click on the "Spoof-CID.bat" file. Follow the instructions. Your CID will change from CWS__001 (stock AT&T CID) to 11111111 (called "SuperCID," will allow you to flash anything)
3. Log in to htcdev and go here: http://www.htcdev.com/bootloader/unlock-instructions (NOTE: This skips the agreements you need to click through as some of the buttons on their website are wonky. Doing this assumes you agree to their policies that are listed there)
4. Follow the instructions very carefully (they are written very well) untill the point where you get the file "Unlock_code.bin" via email. Stop there.
5. You should now have the file for bootloader unlock. MAKE SURE TO SAVE THAT FILE "Unlock_code.bin" TO THE "generic" FOLDER IN THE PACKAGE YOU DOWNLOADED! YOU WILL NEED IT LATER.
Click to expand...
Click to collapse
3. Run the RUU to update to latest firmware
1. Download the latest RUU from the xda forums (should be an .exe file)
Currently it is version 1.85.502.3 and you can download it here:
http://briefmobile.com/download-htc-one-x-att-1-85-update
2. Follow its instructions very carefully. It will take approximately 20 minutes to complete. BE PATIENT. IF YOU UNPLUG YOUR PHONE HERE YOU WILL GET A BRICK.
3. Let your phone reboot and go through initial setup again
Click to expand...
Click to collapse
4. Unlock your bootloader using Unlock Token
1. Navigate to the "generic" folder in cmd (you should have added the Unlock_code.bin file to this folder already) and plug your phone in in fastboot mode. To do this, first shut off your phone. Wait for it to turn off. Then hold the volume down button. Press the power button for 3 seconds while still holding the volume down key. Let go of the power button but keep holding the volume down button untill you see a white screen with a bunch of small text on it. Use the volume up and down keys and the power button to select the FASTBOOT option. Plug your phone into your computer. Then wait for the FASTBOOT text to turn into FASTBOOT USB.
2. Type the following into cmd on your computer:
fastboot flash unlocktoken Unlock_code.bin
NOTE: This step might take quite a few tries. For some it works on the first time. For others, it may take around 20 times. Just keep typing in the command until you get a sucessful flash. We aren't sure why it does this at the moment but just keep trying and don't give up.
3. Use the volume keys to say that you do want to unlock your bootloader and wait for reboot
4. Bootloader should be unlocked! Congrats, most of the grunt work is done! Go to Settings - Developer Options - Enable USB Debugging. This will allow us to continue
5. Re-set up phone and enable USB debugging again
Click to expand...
Click to collapse
5. Install a custom recovery so that we can gain root access
1. Currently there are two recovery options: ClockWorkMod Touch and TWRP (TeamWinRecoveryProject). Both are pretty much the same as they both use touch input but TWRP does have some other nice features like a built in file browser and more. It is also more touch optimized. ClockWorkMod is more "old school" and I personally feel more comfortable using it, but using TWRP is fine as well. It doesn't really matter which recovery your choose, both are good choices. Download whichever one you want below:
CWM Touch: http://forum.xda-developers.com/showthread.php?t=1677304
TWRP: http://forum.xda-developers.com/showthread.php?t=1677447
2. Drag the .img recovery file you just downloaded into the "generic" folder
3. Connect your phone via fastboot
4. Type the following:
fastboot flash recovery <insert name of recovery .img file here>
Replace the stuff between the <> with the name of the file you just downloaded
5. Wait for your device to reboot. Then type into cmd which is cd'ed to the "generic" folder:
adb reboot recovery
6. Make sure your recovery works as soon as it is done loading and then press "reboot system"
7. Follow its instructions
Click to expand...
Click to collapse
6. Root your system
1. Connect your phone as a "Disk Drive" and drag the "root.zip" file in the "root" folder to your phone's memory
2. Reboot into recovery with the adb command (adb reboot recovery)
3. Go to install zip from sdcard and navigate to the zip file you downloaded. Say "yes" and watch it flash
4. Reboot system now
5. Go to the play store and download any app that has "Busybox installer" in its name (the one by JRummy16 works good I believe)
Click to expand...
Click to collapse
If all goes well, you should be sitting at an AT&T HTC One X which is on the latest RUU leaked firmware (1.85.502.3 at this moment), rooted, busyboxed, and unlocked.
Congrats!
If you want to flash any ROMs, download the .zip file of the ROM, place it on your phones memory, and then install the zip like you did to the root.zip file.
Enjoy your AT&T HTC One X!
CREDITS:
kennethpenn: For initial root, getting all the RUUs from the "source" and for giving the HTC One X's situation prime press appearance on his website, BriefMobile.com
grankin01: For finding out how to edit the CID originally
designgears: For creating the One Click Super CID tool for bootloader unlock
paulobrien: For porting CWM Touch to our device
sk08: For leading the way in terms of MODs and organizing an S-OFF thread to get this thing fully ours
JSLEnterprises: For initially being there to help organize a bootloader unlock
Team Nocturnal: For their awesome ROM
Click to expand...
Click to collapse
If you want to thank or donate to someone, please do not do so to me. The people above are the ones that deserve the thanks and the donations to encourage them to keep doing the fantastic work they have been doing! I'm just a high school student
Some common terminology:
Deoxdexed: OEMs package their apps with .odex files because they are more optimized for your device. However, this makes the file uneditable by developers and things like mods cannot be used with odexed ROMs. A ROM with "deodexed" as a feature means it is easier to use mods with that ROM
Busybox: A collection of linux tools that are helpful for flashing ROMs and doing other basic Android tasks
RUU: ROM Update Utility, made by HTC, completely reflashes device firmware, useful if you get bricks. Only for Windows.
Root: Allows you to edit system level files
S-OFF: (currently unattainable) Security-OFF, it is a "feature" in HTC phones that allows us to modify almost any part of your system.
Unlocked Bootloader: Allows us to flash custom images to the device.
Click to expand...
Click to collapse
As I understand and appreciate the work put in this thread, do we need another how to? Using the index sticky alone anyone should be able to root/unlock/flash their device. There's already scripts for everything and virtually no ADB required for nubs.
I would assume with the other info already in this section if someone can't figure out how to flash their phone, then they don't need to flash at all.
HydroSkillet said:
As I understand and appreciate the work put in this thread, do we need another how to? Using the index sticky alone anyone should be able to root/unlock/flash their device. There's already scripts for everything and virtually no ADB required for nubs.
I would assume with the other info already in this section if someone can't figure out how to flash their phone, then they don't need to flash at all.
Click to expand...
Click to collapse
Wasnt sure, there are still a few people asking how to do it since it is a bit complicated with the 1.85 update breaking root so I just compiled everything into a master one.
And yeah, I use a lot of the scripts in the package I put for download.
Anyway, mods do what you think with this thread! And this might be in the wrong section, wasnt sure if it goes in general or development.
Please keep this up. As it is the most aggregated list of instructions, I'm sure it will help many who have just gotten their phone. Great work by the way.
HydroSkillet said:
As I understand and appreciate the work put in this thread, do we need another how to? Using the index sticky alone anyone should be able to root/unlock/flash their device. There's already scripts for everything and virtually no ADB required for nubs.
I would assume with the other info already in this section if someone can't figure out how to flash their phone, then they don't need to flash at all.
Click to expand...
Click to collapse
As I agree with you, a "one stop shop" that can be pointed out to for the noobs who got their mommy's to buy them their cool phone should at least keep the redundant questions to a minimum.
you cant ruu WITH a UNLOCKED bootloader these directions are wrong there would need to be a relock step added in.
ALSO THE CWM STEP NEED A ROOT FOR IT TO WORK LOOK AT THE PAGES
READ UP ON THE STUFF BEFORE YOU MAKE A GUIDE BECAUSE THIS IS WRONG
squishy5 said:
you cant ruu WITH a UNLOCKED bootloader these directions are wrong there would need to be a relock step added in.
ALSO THE CWM STEP NEED A ROOT FOR IT TO WORK LOOK AT THE PAGES
READ UP ON THE STUFF BEFORE YOU MAKE A GUIDE BECAUSE THIS IS WRONG
Click to expand...
Click to collapse
Locked boot loader yes.
Root for cwm no.
Sent from my HTC One X using xda premium
squishy5 said:
you cant ruu WITH a UNLOCKED bootloader these directions are wrong there would need to be a relock step added in.
ALSO THE CWM STEP NEED A ROOT FOR IT TO WORK LOOK AT THE PAGES
READ UP ON THE STUFF BEFORE YOU MAKE A GUIDE BECAUSE THIS IS WRONG
Click to expand...
Click to collapse
Why don't you read before you comment on things like this?
I never "Unlock the bootloader"
I simply get the Unlock token from HTC.
So stop acting like you know everything, because you dont
Don't ever use caps with me and expect me to come back with a nice response. I put this out for the community, not for some kid who thinks he knows it all to come back and say that I did it wrong when he didn't even read the post properly.
And you don't need root to install CWM, just an unlocked bootloader.
Stop calling my stuff wrong if you yourself don't even know what is right
rohan32 said:
Why don't you read before you comment on things like this?
I never "Unlock the bootloader"
I simply get the Unlock token from HTC.
So stop acting like you know everything, because you dont
Don't ever use caps with me and expect me to come back with a nice response. I put this out for the community, not for some kid who thinks he knows it all to come back and say that I did it wrong when he didn't even read the post properly.
And you don't need root to install CWM, just an unlocked bootloader.
Stop calling my stuff wrong if you yourself don't even know what is right
Click to expand...
Click to collapse
He put his foot in his mouth, apology should be coming oh and Good job man, Good job. Thanks for the work, this should be a sticky.
This is a great write up and would have been extremely helpful last night. I will admit I have done a lot of reading before I unlocked the bootloader and updated to 1.85, but it was still very confusing at some points. The htcdev site actually gave me the most trouble because I didn't realize most of the steps were completed and I could skip all the way to entering the token and the site was simply used for entering the token and getting the unlock file.
And yes, I almost said the same thing about the relock step. I had to read it twice to realize you didn't unlock yet. That's another thing that confused me last night was unlocking/relocking immediately.
I think this should be a sticky and all the other tutorials and such should be deleted. This is a perfect summary IMO and will use it when I unlock my friends one x
Sent from my HTC One X
My problem with this is that you packaged it all up while the individual threads for each thing are updating and you are severing up potentially outdated scripts.
designgears said:
My problem with this is that you packaged it all up while the individual threads for each thing are updating and you are severing up potentially outdated scripts.
Click to expand...
Click to collapse
I agree. While it is nice to have a all-in-one, you should be linking to the threads since they are updating them on a daily basis instead of linking to their scripts. Ive already had to change JeepFreaks script this morning as he updated it. It would make your world a lot easier if you did it that way, and also not risk giving some new user outdated scripts.
I think this should go in the General section as the first few pages should redirect to the original threads anyway.
Red5 said:
I agree. While it is nice to have a all-in-one, you should be linking to the threads since they are updating them on a daily basis instead of linking to their scripts. Ive already had to change JeepFreaks script this morning as he updated it. It would make your world a lot easier if you did it that way, and also not risk giving some new user outdated scripts.
I think this should go in the General section as the first few pages should redirect to the original threads anyway.
Click to expand...
Click to collapse
Sure thing, I will add to the original post for the links.
Also I will try to keep this updated, but yeah I might not catch all the updates
Thank you so much Rohan! Really appreciate it! Took me about 4 hours to get this done but it was worth it. Now to install cleanrom. Thanks again. This is my first time doing something like this.
Duse ijuat saw this and I'm going to do this and flash clean from when I get home and I read through this I honestly love you for doing this it helps more than you think thanks a lot
Deffinitlet should be stickied
Sent from my HTC One X using XDA
These are the best instructions! Wish i had them when all this shenanigans started. Thx
ethantarheels123 said:
Please keep this up. As it is the most aggregated list of instructions, I'm sure it will help many who have just gotten their phone. Great work by the way.
Click to expand...
Click to collapse
I agree. This guide is very helpful for me. I consider myself to be fairly computer literate and have flashed ROMs on previous phones, but I am a complete n00b to android and linux. Looking around some of the other threads -- it appears to me that there are many people who could have much confusion resolved by reading this. Thanks for the thread.
-- Jon
Not quite sure what's going on with my update...
I'm using the exe that updates the RUU and it gets stuck on the "sending to phone" step. Reboots the bootloader once, gets stuck again (as far as I can tell , nothing is ever sent) and then gives me an error telling me "The ROM Update Utility cannot update your Android Phone. Please get the correct ROM Update Utility and try again"
i've got the correct drivers installed (was having some trouble related to that a couple days ago but have since figured it all out ) would it be better to just do the update manually? (On my evo you just change the update file to Update.zip and it automatically installs it for you when you boot into bootloader)
maybe I'll have to look into it further, but just curious if anyone's run into this issue or figured out how to get past it as of yet...
Edit: Just an update- I'm betting its because I forgot to relock my bootloader before updating. So anyone who's already completed SOME of the steps in the second post here, make sure you relock your bootloader if you haven't already done so.
Edit1.5: This assumption was correct and the bootloader is now unlocked.
Edit 2- Almost done here... Busybox wont install. Tried two different apps, neither one worked. No indication as to why (got very vague error messages to the effect of "busybox was not installed")
Edit 3- FIXED- Ok, figured it out. As far as I can tell, the process should be Root first, THEN install busybox. It doesn't work without root privelages (at least that was my experience here)