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.
Related
[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.
Did some searching and found a page using Google that linked to this file, RUU_Ace_Cingular_US_1.80.502.3_Radio_12.39.60.19_26.06.04.06_M_release_166557_signed.exe. It's my understanding that all I have to do is run the file and treat it as though it was something like the Odin one click method. What I want to know is the following:
- Is what I have the correct file?
- Are there any other methods to return the phone to stock should I have any warranty issues?
I appologize if this has been covered, I did search and wasn't able to find out any concrete advice.
well if you have s off then you have to run the s on tool.
The way i did it:
used the bubby one click to flash the downgraded rom. thenn in terminal, i typed these certain commands (i forgot what they were but i will get back to you on it). that enables s on. then i flashed the stock att non rooted rom in hboot. i will find the link on those in a little. as far as the ruu above, i bel;ive that it is the correct one.
Thanks a ton, if you have a link to the steps that need to be taken that would be great as well. All and any help is appreciated though.
mindbuRn said:
Did some searching and found a page using Google that linked to this file, RUU_Ace_Cingular_US_1.80.502.3_Radio_12.39.60.19_26.06.04.06_M_release_166557_signed.exe. It's my understanding that all I have to do is run the file and treat it as though it was something like the Odin one click method. What I want to know is the following:
- Is what I have the correct file?
- Are there any other methods to return the phone to stock should I have any warranty issues?
I appologize if this has been covered, I did search and wasn't able to find out any concrete advice.
Click to expand...
Click to collapse
read the MISCELLANEOUS section in this thread --> http://forum.xda-developers.com/showthread.php?t=1033353
Thanks a million Doo Doo. Lock this thread, delete it, put it in a basket and save it for later. Thats all the info I need.
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)
Hey everyone.
Im generally pretty savvy with androids. I rooted and S-offed my HTC Desire, I had a nexus S for a bit until it got ran over... Now im stuck with this Galaxy S 4G, which has been nothing but headaches because for some reason... this thing is impossible to root to me. Ive tried Hemidall, Super1clicks, Odin etc..
Can someone please just point me in the direction of rooting this POS? Im hoping that once its rooted and running stock, I wont hate this thing as much... because so far, Its a horrible purchase.
I just need someone to post a link to where I need to be. Ive searched.. and im absolutely lost. Even the Rootz wiki was useless to me.
Thanks.
Model Number - SGH-T959W
Android Version 2.3.6
You might not have any luck this is the T-959V and your phone might not be supported
Sent from my SGH-T959V using xda app-developers app
http://forum.xda-developers.com/showpost.php?p=28566711&postcount=15
Read that then understand what bhundven means by DONT FLASH BOOTLOADERS!!
You can use the heimdall one clicks he created to get root access and then flash any rom that DOESNT HAVE BOOTLOADERS INCLUDED. That means do not use gremlin remover period. Once you get rooted make a backup and keep it stored in as many places as possible. If you flash the ics variants you will have to use the stock kj6 HOC and then need to flash the HOC for antonx kernel to get root back. At that point you can flash your nandroid or whatever rom you want. AGAIN AS LONG AS IT DOESNT HAVE BOOTLOADERS included.
eollie said:
http://forum.xda-developers.com/showpost.php?p=28566711&postcount=15
Read that then understand what bhundven means by DONT FLASH BOOTLOADERS!!
You can use the heimdall one clicks he created to get root access and then flash any rom that DOESNT HAVE BOOTLOADERS INCLUDED. That means do not use gremlin remover period. Once you get rooted make a backup and keep it stored in as many places as possible. If you flash the ics variants you will have to use the stock kj6 HOC and then need to flash the HOC for antonx kernel to get root back. At that point you can flash your nandroid or whatever rom you want. AGAIN AS LONG AS IT DOESNT HAVE BOOTLOADERS included.
Click to expand...
Click to collapse
I have no idea what youre talking about. Sorry
I used the Hemidall, and only got an unrooted Tmobile rom.. Im not sure where exactly i get root from this
Meh, forget it... im selling this phone. There is no convincing me to ever buy anything from Sammy again unless its a Nexus line.
HTC or Nexus forever.
Thanks guys
Reading is hard
"Can I get step by step directions please?"
Sure, here you are!
"What?! Your not going to remotely root my phone for me? F this place"
Good luck sir, you have the patience of a saint and the drive of a tiger!
OK let's be honest you gave up kinda quick.......
The forum that eollie linked you to was a forum talking about the phone that you bought, which is an apparent offshoot of the t-959v and according to what Masonite found out, "our" roms work on the t-959w but you cannot flash the bootloaders.
Here is the one click link http://forum.xda-developers.com/showthread.php?t=1358498 just boot into download mode and use this but absolutely don't flash bootloaders and it should be OK, no promises.
Eollie was right for linking you there, all the info you needed about your model phone was on that forum, that one click is in the dev sticky which everybody should read.
There has been a flood of people not researching a little bit first before posting and that's why people flamed you but you should not give up, its a good phone and our devs are dedicated and have put in a lot of time on this model, you should be happy your phone can even support all the great roms that are available.
I'm not being mean but seriously, come on, all the info is there, no need to get mad.
Sent from my cm_tenderloin using xda premium
Edit: or Google search how to use heimdall if your confused, I learn off a damn YouTube video..........
Our devs didn't create heimdall and don't support it but it is a great program and the dev has to build the individual one click for the phone, we should be happy to have it that easily available.
Reading the whole thread you got linked to is really hard. Phone-bricking hard
FBis251 said:
Reading the whole thread you got linked to is really hard. Phone-bricking hard
Click to expand...
Click to collapse
Hahaha I know but but I believe in you lmao
Sent from my cm_tenderloin using xda premium
You'll need to flash one of the back to stock files that you got linked to in that thread which will put you on stock GB with no root. DO NOT FLASH THE BOOTLOADERS. You'll very likely brick if you do.
After this download the AntonX kernel from bhundven's one click thread and flash that. That will give you a custom kernel with CWM built in and root.
Needless to say, this is all for the SGH-T959V which theoretically should work on the SGH-T959W. As you'll read any disclaimer on this forum, you're resposible for anything you flash and the damage that may occur to your device.
Thanks for that fb I forgot a few steps if he wants to be on mtd roms, I assumed he could read from that point............ but your right for knowing better
Sent from my cm_tenderloin using xda premium
Thank you very much, and I'm sorry for getting angry. I've had this phone for almost 4 months now, and haven't been able to do anything with it. Quite frustrating.
So, I currently have the Tmobile ROM on my phone, so I'm halfway there it appears!
I'm going to download the other ROM as soon as I get home.
Thanks so much! Next up.. Learning to flash with Odin, and not ROM manager.
It seemed like everything I tried wasn't working with 2.3.6. Superoneclick etc.
I was waiting for a new exploit, but it never came. I tried YouTube tutorials, text directions.. Everything would fail, or give me "read only" errors. I feared bricking, so I stopped.. But I searched the forum and came across the thread he linked me to, but it said no bootloaders, and all the ones I saw had bootloaders. Wasn't until tonight that I noticed it's a 2 part flash process, with the second being the bootloaders.
I think I started this thread at 3am.
Lesson learned.
In heimdall, you can click a little box that says "flash bootloaders" to toggle flashing them on and off! .... or maybe it was odin? I can't remember... been a while since I used them!
After being away for the weekend, I came home, and BAM... fully rooted. Amazing! and FINALLY!!!
Thanks everyone for your help...
I just have another issue.
I wanna flash this ROM http://forum.xda-developers.com/showthread.php?t=1305145
It says its CWM.. but there is a huge disclaimer that we shouldn't use ROM Manager on the development page, which is a bit confusing. Since this ROM isnt Odin flashable... what do i do?
Thanks again.
So I was confused about this when I first started. I'm not at my computer but I can help. In order to flash Roms via cmw you have to turn off your phone hold both volume rockers on the phone then hold the power button and hold till you get into cwm recovery. That will get you into cmw recovery mode. Then wipe data factory rest, from there go back to the main menu and select the install zip from sd card and find the zip file you want to flash and select it and install. Should be good to go.
Sent from my SGH-T959V using xda app-developers app
Nevermind... im a complete goon. I got it, lol.
Thanks
hey all
im pretty new with Androids and flashing.
How can one brick their phone when flashing??
Can you brick it simply by flashing too many roms too many times? Whats the limit?
Or is it just by flashing incorrectly, or incorrect rom/kernel/modem combinations or by flashing and not wiping data or flashing certain roms (how do you know which are safe to flash?)
Most importantly - can you UNbrick a phone? Does it work 100% of the time?
Just trying to figure out the boundaries to play within!
When you modify your handset in any way you risk bricking. The easiest way to brick a phone while flashing is to lose power or disconnect the handset while it's doing it's thing. When your phone is bricked...well its about as useful to make calls as a brick that's why...forget it. If a phone is really bricked its bricked that's it.
Sent from my ADR6350 using xda app-developers app
duleim said:
hey all
im pretty new with Androids and flashing.
How can one brick their phone when flashing??
Can you brick it simply by flashing too many roms too many times? Whats the limit?
Or is it just by flashing incorrectly, or incorrect rom/kernel/modem combinations or by flashing and not wiping data or flashing certain roms (how do you know which are safe to flash?)
Most importantly - can you UNbrick a phone? Does it work 100% of the time?
Just trying to figure out the boundaries to play within!
Click to expand...
Click to collapse
You didn't give a phone model so take this with a grain of salt. The term "bricking" is used differently by a lot of people.
Just flashing a ROM or kernel or mod is generally not likely to brick a phone even if it fails since you should be able to boot into recovery and reflash.
I am not aware of a limit on how many times you can flash or reflash. Some of the newer phone apparently have counters but it looks like XDA'ers are figuring out ways past that already.
A failed flash of a recovery app such as ClockWorkMod or 4EXT or radio or firmware could be a much more serious issue depending on your model phone.
Again, depending on the phone model, unbricking may be possible.
Since every phone is different, the best and most reliable source of information is going to be your phone's forums.
thanks for the replies...
ive got a samsung galaxy s2 GT-I9100.
Does it have a counter??
I change my mind about roms like my gf changes her mind about shoes!
duleim said:
thanks for the replies...
ive got a samsung galaxy s2 GT-I9100.
Does it have a counter??
I change my mind about roms like my gf changes her mind about shoes!
Click to expand...
Click to collapse
No, that is an slightly older phone at this point so no worries. You should be fine, just always remember to verify the MD5 checksums of files when they are provided. There are many PC apps for this and Android apps. I know ClockWorkMod and 4EXT also have this built in as well.
mf2112 said:
No, that is an slightly older phone at this point so no worries. You should be fine, just always remember to verify the MD5 checksums of files when they are provided. There are many PC apps for this and Android apps. I know ClockWorkMod and 4EXT also have this built in as well.
Click to expand...
Click to collapse
are you able to shed a bit of light on how to verify the MD5 check sums?
Also ive seen a few threads about backing up the efs folder - is this vital and necessary and will it help unbrick a phone?
thanks
duleim said:
are you able to shed a bit of light on how to verify the MD5 check sums?
Also ive seen a few threads about backing up the efs folder - is this vital and necessary and will it help unbrick a phone?
thanks
Click to expand...
Click to collapse
Sure, in ES File Explorer or File Expert on your phone, long press the file and then Details or Properties, and you can see the MD5 checksum or the calculate button to get it. It is a long string of letters and numbers and if it matches, you know you have a complete and valid download or copy.
Sorry, not sure on the EFS folder, that might be related to your phone. If it is on the internal memory, then a CWM or 4EXT backup will get it. If it is on your SD, then I recommend backing that up as well by plugging it into a computer and copying all files, including any hidden files.
Sent from my HTC Sensation 4G using xda premium