Database Info

[RUU] RUU_Hero_C_Sprint_1.56.651.2_signed_release.exe

Today I was reminded that being nice to people can pay off! I was lucky enough to get my hands on the new Sprint RUU thanks to syscrasher13!
What is this?
RUU (radio unit upgrade) is the way that our phones are flashed at the factory. It flashes all the factory images on to your phone.
The 1.29 RUU has always been available, however people that purchased phones that came with 1.56 on them were unable to use that RUU: http://geekfor.me/news/sprint-ruu-fails/
This is the updated version for those people that have "with Google" branded phones that came with software version 1.56 on them.
What can I do with it?
You can use this to "unroot" your phone before sending it in for warranty work.
Use it to flash back to stock if you are having any random issues on your phone that you can't fix.
It can 100% flash your phone back to how it came from the factory. As long as your phone turns on at all (even if it's not booting) then you should be able to save it by using this.
This means your phone is virtually unbrickable, unless you go flashing a radio or SPL or something that you shouldn't.
You can flash this on a phone that originally came with 1.29 on it, just know that once you do you will no longer be able to use the 1.29 RUU. You will have to use this one.
How do I use it?
Download the file below and run the exe.
Go in to the folder that the exe created and run ARUWizard.exe
What else do I need to know?
The phone is still rootable. I tested it successfully using the auto-rooter in the pre-kitchen.
Fresh ROM still works just fine (as should any 1.56 based rom)
You will not be able to use the 1.29 RUU after this one, but I don't know of any reason that you would want to
Although some img's in the RUU have different dates than the original it appears that they are identical other than system.img
You don't need to run this unless you are trying to return your phone to stock. You won't get anything special from running it.
Download here: http://geekfor.me/news/sprint_ruu_156/

Thank you so much flipz!! As always sharing the goods with the comunity!!!
Amazing work

thanks for sharing!

appreciate this very much!

thanks flipzmode....always a chance this could come in handy at some point

THANKS! was worried about having a with Google phone until now

thanks flipz

Many thanks!
Now, with this file on hand, I think it might be time to go ahead and root my new phone. Mostly I just want proper control over the device -- not likely to flash any ROMs until they evolve a little more -- but your work looks real solid and I plan on keeping up with it. Good show!
(on a side note, fwiw -- jumping ship from the Touch Pro to the Hero, after being with WinMo since the i730, has been my most satisfying smartphone experience, ever)

Hey, Thanks!
One minor request, though: Could you include the md5 values to your file releases from now on?
While it does not increase security, it gives assurances that the file has not been altered... and it allows us to verify downloaded files.
I think a RUU file deserves this, don't you?
JohnP
Ooops: You did - on this page. Sorry.

johnp2343 said:
Hey, Thanks!
One minor request, though: Could you include the md5 values to your file releases from now on?
While it does not increase security, it gives assurances that the file has not been altered... and it allows us to verify downloaded files.
I think a RUU file deserves this, don't you?
JohnP
Click to expand...
Click to collapse
I've included md5 values on my releases since fresh 1.0. It's not in this post but if you click the link to go to the download page you'll see it there.

This definitely needs to be stickied...I know myself and others have often referenced the RUU in many troubleshooting posts throughout my (admittedly short) stay at xda so far.
Thank Flipz for getting and posting this stuff!

Thanks for this! Looks like we can root non Sprint CDMA Heroes now. (Cellular South, Bluegrass Cellular)
Any idea exactly how we managed to get this? From HTC? From Sprint?
I really want to find one for Cellular South and might as well try for Bluegrass Cellular since it has its own CID as well.
Doesn't look like the different version radio will be an issue, but would be nice to have the RUU around just in case.

johnp2343 said:
Hey, Thanks!
One minor request, though: Could you include the md5 values to your file releases from now on?
While it does not increase security, it gives assurances that the file has not been altered... and it allows us to verify downloaded files.
Click to expand...
Click to collapse
It's been modified, it won't match Sprint's (or HTC's) md5sum in any case. So having the md5sum for this one doesn't buy you much.

posguy99 said:
It's been modified, it won't match Sprint's (or HTC's) md5sum in any case. So having the md5sum for this one doesn't buy you much.
Click to expand...
Click to collapse
Sprint and HTC aren't exactly providing an md5 on a file that hasn't been officially released. But I did create an md5 when I uploaded it so you know the file downloaded is the same one I uploaded.
Additionally the zip of the images located inside of the RUU are unmodifiable which is why we couldn't modify the old RUU to work with the new phones. When you start the RUU it will push the files to your phone and then check them. If they aren't what they are supposed to be, it will fail.

someone share the direct download link(eg, rapidshare link) to me?
i live in China and i cannot use the bit.ly services(because the gov blocked it)

fyi to those who are wondering this will work on a non google branded phone...however it does not fix the Rev 0 Rev a problem as it does not appear to update the pri to match that of the "with google" phones.
I dont care what sprint says and what htc says. My non google and my wifes google phone have two different speeds...
im exchanging mine for a with google phone today

Thanks!
this saved my phone. I was about to throw it away.

USB Connection Error
Tried running the RUU and got ERROR [170]: USB CONNECTION ERROR. Got in on a Windows XP and 7 laptop. Need help.

nemesys504 said:
Tried running the RUU and got ERROR [170]: USB CONNECTION ERROR. Got in on a Windows XP and 7 laptop. Need help.
Click to expand...
Click to collapse
Just because we always have to ask to rule out the obvious...did you run it as administrator? (Right click on the file, select "Run as Administrator")

Same Problem
I am having same issue as above on Win 7 64 bit. However everything else works from this machine to my phone. Rooting it, usb mount of SD, screen shots, etc. Please help me. I want to flash back to starting point and start over.
Thanks.
Jamie

[32A] Install official sense UI (3.05.401.3) without getting perfect SPL!

Alright, so HTC released the sense UI update to 32A in Europe some days ago. After searching around I figured how to flash it without getting stuck at perfect SPL. Therefore; I'd like to say that this is very little my own work. I only wrote everything I found here.
I'd like to thank these people/sites for learning me this:
Radix999, for his page in the wiki.
TheUnlockr, for fantastic guides about rooting.
cursordroid, for the correct order to flash radio/hboot.
vmaxada, for how to get rom.zip and rom1.zip.
Read everything before trying if you don't want to risk your phone.
You will need engineerings SPL before doing this. Means it won't revert the perfect one.
Disclaimer:
I'm not responsible for anything may happen to your phone during this update.
Only apply this on a sapphire 32A.
There's always a risk when flashing images to your phone, but if you follow the instructions, you should be fine.
This update will give you:
HBOOT-1.76.2007
RADIO-6.35.08.29
ROM version 3.05.401.3
Alright, so what you'll first need is the files. There's two ways to get these. First one, would be to download them (defiantly easiest). The second would be to fetch them from HTC's update file, I'll write this only for learning purposes, so if you're not interested in learning, do it the first way.
opinion 1
Download the files
I've collected everything for you in one file.
RUU_Sapphire_HTC_Europe_3.05.401.3_release_signed_NoDriver(eng spl).rar (mirror) password: for xda
Extract the files to somewhere you'll find them. Like C:\AndroidSDK\tools.
opinion 2
Fetching the files yourself
Doing it this way will take a lot longer than the first, but you'll learn more.
Here you'll need two files:
The official update file, RUU_Sapphire_HTC_Europe_305401 (mirror) and the SPL version, hboot-1.76.2007.
Copy the hboot-1.76.2007 to somewhere you'll find it, like C:\AndroidSDK\tools.
Boot your phone into fastboot mode (back+power) and connect it to your computer using USB. Run the file you downloaded, RUU_Sapphire_HTC_Europe_305401, and continue until it's done displaying "Confirming info about the Android phone" (I'm not sure if it's exactly the same displayed, but it should have the same meaning). When it's done with that, STOP, don't cancel, but don't do anything further.
Keep the update window open, and go to Start - Run, then type in %temp%. Search for "rom*.zip". You should get rom.zip and rom1.zip as results. Copy both the files to your desktop. Cancel the update.
Note: People have reported the files won't open with the built-in zip extractor in Windows, you'll might need WinRAR.
Open the two zip files. Extract the following files to the same place where you putted the hboot-1.76.2007:
Code:
boot.img
radio.img
recovery.img
system.img
userdata.img
After doing this you're done with getting the files.
Flashing
Now you're done with most of the work, everything left is flashing.
Boot your phone to fastboot (back+power), and connect it to your computer. Open up terminal (cmd) and "cd it" to the directory where you have the system files.
Code:
cd C:\AndroidSDK\tools
Then type in this, to check your phone is connected.
Code:
fastboot devices
If you get a serial number, your phone is connected and you can proceed.
Now, type in the following and hit enter after every line:
Code:
fastboot flash radio radio.img
fastboot flash hboot hboot-1.76.2007.img
fastboot flash recovery recovery.img
fastboot erase system –w
fastboot reboot-bootloader
Now your phone should reboot into fastboot. Make sure you have HBOOT-1.76.2007 and RADIO-6.35.08.29. If you have that, you can type in the rest:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot reboot
Now your phone will reboot, and you'll have the official sence UI, but still engineerings SPL!
As you may have noticed, my English isn't perfect. If you see something wrong with my grammar please tell me what's wrong.
If you want a custom recovery, you'll have to install a Hero recovery. I recommend RA-hero-v1.5.2.

First of all this is old news already explained by Cursordroid who, i can see, you didnt not bother to thank! Trying to take credit for something that someone else did is not a good idea.
Secondly, your info is wrong. You will not end up with that version of the radio but with 6.35.08.29, nor is there rom2.zip but rom1.zip (at least for me it was that way). By flashing the new radio, people will be confined to using official 3.03/3.05 ROM, CursorSense, Cursor's t-mobile fender rom and some other roms (1-2 more exist currently) that i did not test. Otherwise a downgrade to the old radio is required! (e.g for running CM you need to downgrade the radio).

Did actually need another post on this topic??

The mirror I'm using is screwed at the moment, uploading takes longer then I expected.
eyegor said:
First of all this is old news already explained by Cursordroid who, i can see, you didnt not bother to thank! Trying to take credit for something that someone else did is not a good idea.
Secondly, your info is wrong. You will not end up with that version of the radio but with 6.35.08.29, nor is there rom2.zip but rom1.zip (at least for me it was that way). By flashing the new radio, people will be confined to using official 3.03/3.05 ROM, CursorSense, Cursor's t-mobile fender rom and some other roms (1-2 more exist currently) that i did not test. Otherwise a downgrade to the old radio is required! (e.g for running CM you need to downgrade the radio).
Click to expand...
Click to collapse
Where did I try to take credits from him? I fixed the wrong info (sorry about that). Also, where did he explain this? I know he explained how to get this radio, SPL and Hero recovery. But nothing about the official sence ROM?
fregor said:
Did actually need another post on this topic??
Click to expand...
Click to collapse
Where's the other topic about this?

He did some time ago make a toping regarding flashing 3.03 without getting stuck with the perfected spl. After making CursorSense however he eventually deleted his 3.03 thread.
You did not directly state that you were to be credited for this work but you did not thank him for doing it either. And all you did was "steal" (steal because you failed to thank the man) his method.

eyegor said:
He did some time ago make a toping regarding flashing 3.03 without getting stuck with the perfected spl. After making CursorSense however he eventually deleted his 3.03 thread.
You did not directly state that you were to be credited for this work but you did not thank him for doing it either. And all you did was "steal" (steal because you failed to thank the man) his method.
Click to expand...
Click to collapse
Alright. I'll thank him, but for what?

In other news, I still can't manage to upload the files (crappy outline I guess). I, however, added links to the same files. They are not uploaded by me though.

perfected spl
can we use this method if we already updated to a perfecter spl (1.76.0010)?

WTF
Hey dude!!!
You forgot to mention me under the thanks to, part that you don't even have!!
I hope you feel good about yourself!
and you searched? No! You asked me!
This is last time I'm helping you!!

Still... this is not for us who have already been stuck with perfected SPL...

Can I use these instructions if I have hboot-1.33.0010 (sapp10000)? or do I need to use goldcard to get 1.33.2010 first?
Thank you

Nope you will need eng spl to fastboot...
But he forgot to write anything about that!!
So you need the 2010 before you can even start...

Yeah, I thought so too...
Thanks

ralle.gade said:
Hey dude!!!
You forgot to mention me under the thanks to, part that you don't even have!!
I hope you feel good about yourself!
and you searched? No! You asked me!
This is last time I'm helping you!!
Click to expand...
Click to collapse
Look at the date I posted this thread, 22th. I asked you my first question the 23rd.
All the info I needed to write this, i found on the wiki (thanks radix), the unlockr, and other places.
What was I supposed to thank you for anyway?

Mine have perfect SPL
SAPPHIRE PVT32A SHIP S-ON H
HBOOT-1.76.0007 (SAPP10000)
If I'm upgrade this rom by using gold card, can I have a new SPL?

guys, after i installed this rom,,,i installed the ra recovery 1.5.2H, and when i tri to acess to the recovery it blocked!!! no way to rebbot....i have to remove the battery..i tried several times...always happen the same...
any idea?

zouky007 said:
guys, after i installed this rom,,,i installed the ra recovery 1.5.2H, and when i tri to acess to the recovery it blocked!!! no way to rebbot....i have to remove the battery..i tried several times...always happen the same...
any idea?
Click to expand...
Click to collapse
What recovery image did you use?
As far as I can tell you need the hero version for this rom/radio. So I'm thinking you used the sapphire version.

muuu said:
What recovery image did you use?
As far as I can tell you need the hero version for this rom/radio. So I'm thinking you used the sapphire version.
Click to expand...
Click to collapse
Yes. Flash the RA-hero-v1.5.2 recovery using:
Code:
fastboot flash recovery recovery-RA-hero-v1.5.2.img
shokuhawan said:
Mine have perfect SPL
SAPPHIRE PVT32A SHIP S-ON H
HBOOT-1.76.0007 (SAPP10000)
If I'm upgrade this rom by using gold card, can I have a new SPL?
Click to expand...
Click to collapse
No. You'll need engineerings SPL. Try this.

Any ideas whats going on with my unit? It seems to be crashing when writing the radio. I see the red bar go all the way to the top, and then it just sits there forever... any ideas?

gunigugu said:
Any ideas whats going on with my unit? It seems to be crashing when writing the radio. I see the red bar go all the way to the top, and then it just sits there forever... any ideas?
Click to expand...
Click to collapse
Did you flash it in the correct order? If not, try flash back to a hboot that suits with your current radio. Then flash this radio.
In other news, I finally managed to upload the files myself.

**SOLVED** Consolidated Info to HOPEFULLY Root Rogers 3.05.631.7 ROM-updating via RUU

(If ROM installed via official HTC RUU- RUU_Sapphire_Rogers_WWE_3.05.631.7_R_release_signed_NoDriver.exe)
UPDATE!! **SOLVED** April 25, 2010
Download new RUU
http://www.multiupload.com/XQEH9NVGY7
Flash with Goldcard method http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
1. Download RUU linked above.
2. Install update using RUU.
3. Turn on phone and connect to computer.
4. Get RA recovery and SPL also linked above and drop them to sdcard root directory.
5. Run SDK: adb shell
6. Install recovery: flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img http://forum.xda-developers.com/showthread.php?t=561124
6. Turn off phone and turn on again holding Power+Home. RA Recovery should appear.
7. Flash zip from sdcard.
8. Use file: update-hboot-1762007-signed
9. Done. PSPL broken.
10. Build a shrine for orange_24
****************************************************
**Not Successfully Rooted: Feb. 2, 2010 (AFAIK)
I decided to start this thread because the info for again obtaining root, for those of us dumb enough to update to the official Rogers ROM 3.05.631.7 via the RUU, is all over the place in about a million different threads. My hope is that we can organize it all in 1 place.
At this point, yes, we all know we were impatient and newbs and everything else. Ok, lesson learned. So, lets move forward and try to get this thing rooted.
If you are a developer who has the talent to help root this ROM and have lost interest in the Magic or moved on to the Nexus One or Droid, we ask that you please try to spend a few moments on this and help out those of us who are really stuck here. Personally, I'm getting pretty desperate and thinking of even replacing the phone.
Please post what you've tried in attempting to again obtain root, your failures and hopefully successes.
*One Click Root: http://theunlockr.com/2009/08/29/how-to-root-the-htc-magic-in-one-click/ Cant' back up Recovery.img Error(Tried clicking the hidden Star next to "Back Up Recovery" and skipping this step...and just flashing recovery-RA-sapphire-v1.5.2H.img. Didn't work either) Tried with Amon_RA Hero recovery.img also, without success.
*Tried downgrading to Rogers' last official ROM via the RUU for (Rogers)_RUU_Sapphire_Rogers_WWE_2.17.631.2_release_signed_NoDriver.exe RUU would not let me proceed because the ROM was older than the one installed. Attempted several times both with and without a goldcard installed.
*ADB: Will see the device, initially, but a command of "adb remount" kills the connect. same with "adb root" **EDIT
*Fastboot: Error- Does not allow access
*Relentless Rooter: http://forum.xda-developers.com/showthread.php?t=556200 No luck obtaining root
*Fix Perfect SPL: http://forum.xda-developers.com/showthread.php?t=548218&highlight=create+gold+card With one GoldCard getting Update Fail error that SAPPIMG is older than one installed. When trying the other GC, get Update Fail Error that Model ID is incorrect. Tried 2 different micro sd cards, one Sandisk and one Patriot. The card was recognized by my pc after I was done creating the GoldCard, so unless I'm doing something wrong the GC was created properly. Is the goldcard.img supposed to dissapear or remain on the card after your copy/paste write/save to the sd card disk?
* Tried RUU for RUU_Sapphire_HTC_Europe_3.04.401.2_HTC_AT_test_signed_NoDriver.exe http://forum.xda-developers.com/showthread.php?t=625108 RUU would not let me proceed because the ROM was older than the one installed or Device ID was wrong. Attempted several times both with and without a goldcard installed.
*Tried RUU for RUU_Sapphire_HTC_Europe_3.05.401.3_release_signed_NoDriver.exe http://forum.xda-developers.com/showthread.php?t=621415 RUU would not let me proceed because the ROM was older than the one installed or Device ID was wrong. Attempted several times both with and without a goldcard installed.
*Tried RUU_Sapphire_HTC_Asia_WWE_2.53.707.2_SEA_test_signed_NoDriver.exe RUU would not let me proceed because the ROM was older than the one installed or Device ID was wrong. Attempted several times both with and without a goldcard installed.
I've probably tried a few more methods to obtain root. Those were all fails, too. I'll post the links, as well, when I find them again.
Hopefully this thread will lead us all in the right direction.
Here is the link to the same topic in the HTC Dream Forum-in case they find out something that might help us out: http://forum.xda-developers.com/showthread.php?t=625732

i guess its time to play doctor with my new phone from rogers and swap the board from my old one.....

considering nothing works, i think any new idea would be a good idea

novadoc said:
considering nothing works, i think any new idea would be a good idea
Click to expand...
Click to collapse
like i said my idea was to swap my old motherboard into the new phone

you can give it a shot
but personally, unless you know exactly what your getting into, i wouldn't mess with the hardware

novadoc said:
you can give it a shot
but personally, unless you know exactly what your getting into, i wouldn't mess with the hardware
Click to expand...
Click to collapse
i already did it lol im more of a hardware then software

I know it might be nothing but when the Rogers RUU unpacks the img file loads as sappdimg and not sappimg. I don't know if the extra d in there means anything or if its something that shows up later.

I also try every method above and not luck also...

is there a possible way of tricking the system... with a higher build number and SPL with a custom installation from files that I see from one of the post where rogers send the user some files because they were running Win7?

I think that's the problem
We have the highest spl# and its perfected
So until someone gets their hands on a higher version than ours that is imperfect or engineering...
We are SOL, although I am hopeful someone is working on this for us.

shael said:
i already did it lol im more of a hardware then software
Click to expand...
Click to collapse
Did it work?

I have an Rogers HTC Magic and I didn't apply any update from Rogers since I bought it on June 2nd.
It's very strange that "adb devices" doesn't see the device?
have you enable the "USB debugging" ?
That part should work (when the devices is started).

novadoc said:
Did it work?
Click to expand...
Click to collapse
pfft ya ofcourse it worked... i have my older motherboard with my old rom and my old info all i did was swap the screen and case.... done deal... 5 min job lol

Would someone please report the radio and SPL versions (for the result of the 3.05.631.7 update)?

feisty_noodle said:
would someone please report the radio and spl versions (for the result of the 3.05.631.7 update)?
Click to expand...
Click to collapse
apphire pvt 32a ship s-on h
hboot-1.76.0010 (sapp50000)
cpld-12
radio-6.35.10.18

feisty_noodle said:
would someone please report the radio and spl versions (for the result of the 3.05.631.7 update)?
Click to expand...
Click to collapse
apphire pvt 32a ship s-on h
hboot-1.76.0010 (sapp50000)
cpld-12
radio-6.35.10.18

Well, until it gets cracked, here's something that will make you feel a little better about being stuck on this ROM.
Google Search by Voice, installable .apk from Euro Android Market. Just run the installer through Astro, etc., and G Search by Voice is back on the Search button of your phone. You might need to launch the app first via the icon in the app tray, then reboot the phone to make the search button recognize its there. But it will be there.
http://www.eclosion-android.com/com.google.android.voicesearch.apk
BTW, not my link in case mods want to get involved.
Enjoy!

i think the first step would be to getting ADB working again
any ideas?

novadoc said:
i think the first step would be to getting ADB working again
any ideas?
Click to expand...
Click to collapse
I can used adb devices to see my connected htc magic.... but other function permission not allow...

Is this thread in the Dream Forum a path to follow to try, or just a good way to brick your Magic? I haven't fully read through it to see if this is to keep root, if you already have it and flash the Rogers Dream ROM for data/ or to regain root if you flashed the official Rogers RUU with a Dream. The post says should work on all Rogers phones, but i feel a brick coming on for me.
http://forum.xda-developers.com/showpost.php?p=5480955&postcount=416

[Q] How do I flash new radio using ace hack kit

Im running Android Revolution and now I would like to flash the recomended radio. However i do not have eng s off so fastboot flash radio radio.img does not work for me.
After reading the effen manual, what i understand is that to flash a new radio I need to
1. rename the desired radio zip file to rom.zip
2. place it in the romzip folder
3. open hack ace cmd menu and select to install my own radio
Heres where im confused. When I follow the link provided to here the instructions seem to conflict each other.
Ive studied this as much as I can over the past two days but havent found much solid info.
I also tried using visionary b4 I even flashed the AR ROM but it did not work.
Could someone confirm that it is as easy as stated above or if im wrong please help a brother out. I just need to flash the recommended radio and havent found a solution im confident with. Please and Thanks to anyone who can help me out.

I personally go by the instructions from the link you provided. Just rename the zip, put it in the root of.your SD card, and flash via hboot. And that's it.
Sent from my TARDIS using XDA App

no no no
this is how it's done for me, minus the links needed to flash the radio, as they are not mine.
You should also flash the matching RIL file (radio interface layer) that HTC pushed out with this new radio. Here are the steps to do all of this:
Below is a link to my dropbox folder containing the P98IMG.zip file containing the new radio. Download this file to your computer. Now we need to check to make sure the file didn't get corrupted during the download process (extremely slight chance of this happening, but we don't want to flash a corrupt file to your phone and risk bricking it). Download md5.exe from below and run it, and browse to the P98IMG.zip you downloaded. The MD5 hash it displays should match this number exactly:
33BAEBAD8B1E7A20F4603AFF0BA66468
You can paste this number into the MD5 program so you can compare them.
Now that we've verified the file is good, copy this file to the root of your SD card and reboot your phone into bootloader mode. Once you're in the hboot/bootloader screen, select bootloader and wait a few seconds and it will automatically find the .zip file and then prompt you to proceed. This process is what flashes the new radio, it takes about 20 seconds or less. Once it's done, reboot into your ROM like normal. Go into settings>>about phone and check your radio version; it should now show 26.06.06.30.
Now we need to flash the matching RIL file. Download the file below and copy it to your SD card. Don't worry about checking the MD5 hash. Reboot your phone into clockwork recovery mode, and then select install zip from sdcard>>choose zip from sdcard then select the RIL .zip file and flash it. Reboot back into your ROM. We are done! Let me how it works for you. You might give it a few days before making any decisions, it seems like some ROMs need to adjust to new radios/RIL files before the battery life settles down to normal (that is my experience anyway).
credit to HenryBravo

My goal is to flash the radio recommended for AR HD. I did so by moving it to root of sd and hboot. But i dont think it took becasue baseband does not match up. It stayed the same after two tries. I would really like to follow the devs instructions for the radio. However I cant seem to successfuly flash it.

NARRRRRRRRRRR did you even read what i typed?
direct instructions

Dude my bad man. Is this the radio for AR HD...radio 12.54.60.25_26.09.04.11_M2 ? the numbers did not match up. I dont see a link for your dropbox though? I really apologize for being dense if i am and I really appreciate your quick reply and patience. thank you

We are going to need more specifics on what you did. But following wdkingerys instructions are exactly what you need to do
Sent from my TARDIS using XDA App
Sent from my TARDIS using XDA App

What I did was
1.rename the radio 12.54.60.25_26.09.04.11_M2 (radio recommended by dev) to PD98IMG.zip
2.boot into hboot it found it i got the progress bar on the right had side it took about 5 seconds or so
3. Then i went into fastboot to select power down and then i turned it back on

I want to follow your directions but I dont see the dropbox links. Like i said earlier I really appreciate your patience

Ok I checked out the AT hd thread and yes 12.54. Is the recommended radio. Wdkingery mentioned the stock ATT radio. When you check the radio/baseball in about phone what does it say? It should match to what your trying to flash
Sent from my TARDIS using XDA App

Thats what I thought but it doesnt. I went in the IRC (dont remember which) and have gotten a copy of everything wdkingery said and will follow his instructions. It currently says baseband# 12.28b.60.140eP_26.03.02.26
-i think the problem was that the AR HD recommended radio is for a DHD not sure

I've flashed dhd radios, so that shouldn't be the problem. Though in my case the dhd radios were never as good as stock. Again that was me as plenty of others have gotten better results with other radios. It more of a trial an error in my opinion and flashing radio does have its risks so I tend to stay away.
Sent from my TARDIS using XDA App

I think your right, apparently that radio required eng s off and again thank you.
Im now rockin 06.06.30 and about to load the RIL. Will follow up with results

Got the RIL installed and im good to go speedtest.net app shows 3 down 1 up. Not great but im gonna bet thats more to do with the tornados that just came through here. The network has been iffy throughout the city anyways. Also ill follow the advice given to wait a couple days b4 makin any real judgments. Thank you again to both of you guys. I think ive managed to get my head wrapped around this a little better.

Glad I could help . I think I might have figured it out . I downloaded the 12.54 radio and compared it to my stock zip. The AR ZIP does not contain Android Info text file. This is the first time I've ever looked I.side the zip, so.this is new to me. I believe this file is needed in the zip. Somebody correct me if I'm wrong.
So from reading the flashing radio thread. They state to replace the radio images (with the one you want)so the txt file is probably important and hence it not working for you.
You should try out the stock like you said, and see if it works for you. If not I with this new Info, we should be able to get you on 12.54
On a slightly different note. Eng s-off is not needed. And is even riskier than hboot, trays why many devs prefer the hboot method
Sent from my TARDIS using XDA App

Great thank you. I might still want to try 12.54 in the future so ill keep that in mind. I would like to know exactly why one radio is better than the other anyways so for now im happy with this one. I was in the AR HD irc for a while but couldnt get anyone. Ill get to the bottom of it sooner or later. Thanks again

<Collaboration><Dev><Ideas> HTC Evo 2.3.3 Gingerbread Root Collaboration.

<Collaboration><Dev><Ideas> HTC Evo 2.3.3 Gingerbread Root Collaboration.
* I love the color orange.​HTC Evo 2.3.3 Gingerbread Root Collaboration​
The Lowdown on Everything​
FASTBOOT
HTC's RUU releases basically run the adb reboot bootloader code, reconnect to the phone, verify the version and run a series of fastboot commands to install the contents of the PC36IMG (detailed below). In the same way it may be possible to run fastboot commands from command prompt with the SDK installed if you can time it just right in the flashing process, or not. The bootloader can be quite picky when it comes to letting anyone or anything flash anything lower than the version on the phone, or unsigned.
Click to expand...
Click to collapse
PC36IMG
The PC36IMG is what is flashed in the bootloader. The contents of the zip include the radio, system, and more. As long as S-ON is present the bootloader won't flash any PC36IMG that isn't signed by HTC themeselves, however with S-OFF you can flash custom PC36IMGs as well as downgrade, because the bootloader doesn't check the firmware version to see if it's newer or not. If someone was however to be a sneaky awesome ninja and steal HTC's secret sauce then we could simply sign any PC36IMG we wanted to and fake a newer version in the android info txt.
Click to expand...
Click to collapse
RECOVERY
From my understanding the stock recovery references alot with the bootloader to check for most of the same checks it looks for in the PC36IMG, but in the update.zip HTC includes for updates. The stock recovery won't flash anything but signed HTC update.zips either, which again you need the special sauce to sign. Custom recoveries like Amon RA or Clockwork remove the security and don't reference with the bootloader (since your phone has to be S-OFF anyways to flash a custom recovery.) A custom recovery is the key in flashing customs roms and kernels, if you can achieve it with the security on (S-ON) the you won't even have to worry about achieving S-OFF. However, that's near impossible due to the security in the bootloader HTC implements with updates. Which is why the bootloader has to be cracked to install anything.
Click to expand...
Click to collapse
RUU
The RUU is an official tool HTC puts out so people can reflash there phone with a stock firmware just like if it is brand new and your turning it on for the first time. The files included inside of the RUU frontend include the PC36IMG which is essentially what is flashed in the process, but in a fancy way I guess you could put it. The same security applies to the RUU, you can't downgrade versions without S-OFF because the bootloader still checks the version on the phone currently to see if it can flash the PC36IMG or not (when security is on [S-ON] )
Click to expand...
Click to collapse
APKS
I'm sure alot of you know of applications such as Visionary or Z4Root, they both use common exploits to root your phone in a simple application, first temp root then permanent root. They push the approiate resources, Superuser, su, busybox, set the permissions for everything to run, and clean up everything in the blink of an eye thanks to simple scripts. The same thing is still quite possible with any exploit, the exploit just has to be found in the software. You find the exploit you gain root. You have root you can do almost anything to your phone, but S-OFF still plays a role in everything with what you can and cannot flash. Sigh. I know right..
Click to expand...
Click to collapse
Our Mission​
The whole purpose of this thread is to collaborate on possible ways to obtain S-OFF and/or root on 2.3.3, either update. We are community, thus we must act like one, and not bash each other for trying. If you have a truthful idea or any questions feel free to post them. You never know, you could very well help with rooting the latest update. This has gone on far to long it's been almost 2 months and no root. This is our time to free each other from the chains of security because we all like to be dangerous sometimes.
Click to expand...
Click to collapse

Possible Rooting Ideas​

What Works What Doesn't​
I encourage everyone to try previous rooting methods, and methods to obtain S-OFF and experiment as much as they feel comfortable with, you never know what you might find. We could be overlooking something.
Click to expand...
Click to collapse

There is no right or wrong answer only better ones than others. Please do not bash users, or slander them for there ideas, everyone has a right to post, but please stay on topic. /end

Am I missing something?
Sent from my PC36100 using XDA Premium App

lil_bono said:
Am I missing something?
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Just give me a few, I'm still typing.
<done></done>

<words>I'll be back on tomorrow, I'm going to go lay down and talk to my friend. Feel free to comment with any ideas. I, myself, am looking into and working very hard to achieve S-OFF and root for the 2.3.3 update, it will come in time. That's just the key; time.</words>

What other phones have you developed, alone or with a group, a rooting and/or s-off type process for? And I don't mean an app that uses an already known exploit such as rageagainstthecage.
I guess at least we have a fancy thread now. Best of luck to everyone.

ill jsut post a small snippet of thanks for thaking this initiative, i dont know about android os myself one bit, so i can hardly contribute, but would there be a way to "fool" the hboot or Ruu version number ?
either fooling the hboot into thinking the ruu one is trying to flash ( to downgrade of course) is a higher version one, or to somehow change the RUU itself to report a different version number? i realize this may sound incredibly stupid as my programming knowledge is very limited, but jst throwing it out there...
once again, thanks for taking this initiative for the evo 4g community

I was wondering if you could force the RUU update. We know it verifies the version on the phone, but surely to could still flash if it was forced. Sort of like doing an nvflash on the tablets. You'd just need to hack the RUU updater to skip the version check and flash anyway. Unfortunately, I'm not a cracker, so...

This should take off
There's a whole thread in Evo General full of ideas due to some kind of "bounty" to whomever achieves root on 2.3.3. At least we could get a start on what does/doesn't work. (This is not meant to deter traffic from this brainstorming thread)
http://forum.xda-developers.com/showthread.php?t=1162671

skatrwannabe3 said:
There's a whole thread in Evo General full of ideas due to some kind of "bounty" to whomever achieves root on 2.3.3. At least we could get a start on what does/doesn't work. (This is not meant to deter traffic from this brainstorming thread)
http://forum.xda-developers.com/showthread.php?t=1162671
Click to expand...
Click to collapse
Hey, great idea. Just so you know, there is no "bounty" on rooting the ota. I dont even know where that term came from. I just started a thread to say that I am desperate for root, I will pay for someone to figure it out. I never asked anyone or expected anyone else to throw money in on it too. It has since grown into a 600+ dollar pot, and I think that its a good thing. The people that take the time to root it should get a pat on the back.
On topic: I see a bunch of people saying to downgrade, isnt temp root gonna come before that? Shouldnt temp root be the thing to focus on first?

I'm not much of a programmer but ill brick my phone as many times as needed lol
Sent from my PC36100 using XDA App

github said:
What other phones have you developed, alone or with a group, a rooting and/or s-off type process for? And I don't mean an app that uses an already known exploit such as rageagainstthecage.
I guess at least we have a fancy thread now. Best of luck to everyone.
Click to expand...
Click to collapse
I've personally never been the leader of a rooting or S-OFF project before, but my knowledge of Android on a whole is pretty vast. I do develop roms and kernels as well as themes and apps for Android in general, so I guess I'm pretty qualified?

fldash said:
I was wondering if you could force the RUU update. We know it verifies the version on the phone, but surely to could still flash if it was forced. Sort of like doing an nvflash on the tablets. You'd just need to hack the RUU updater to skip the version check and flash anyway. Unfortunately, I'm not a cracker, so...
Click to expand...
Click to collapse
I'm not sure that the RUU is anything but a front end user interface for the process, the actual flashing and everything involves the bootloader, which is why it still pushes the PC36IMG temp. to the sdcard. It might however be in the RUU itself and using fastboot flashes? I'll look into it. Good idea, thanks.

Who rated the thread bad?

bubby323 said:
I'm not sure that the RUU is anything but a front end user interface for the process, the actual flashing and everything involves the bootloader, which is why it still pushes the PC36IMG temp. to the sdcard. It might however be in the RUU itself and using fastboot flashes? I'll look into it. Good idea, thanks.
Click to expand...
Click to collapse
but does the RUU update the hboot itself?
the point is , older hboots and android software are already rooted, if we can get back to those , the end result is the same, we get root, then upgrade using a stock rooted rom, problem solved

bubby323 said:
What Works What Doesn't​
Click to expand...
Click to collapse
My recent failures attempts while on 4.24 S-On:
Amon_Ra Recovery PC36IMG.zip flashed from Hboot
Signed 3.70 PC36IMG.zip flashed from Hboot
Signed 4.24 PC36IMG.zip flashed from Hboot (it loads/updates, but is basically a factory reset)
3.70 RUU exe
UnrEVOked3

some chucklehead
bubby323 said:
Who rated the thread bad?
Click to expand...
Click to collapse
Eh, I put in a 5 star vote to make it up, also to show the uselessness of voting.

Has anyone looked at the contents of a PC36IMG.zip? I am still decompliling one, but its a fun task to decipher all of the code. Another thing I need is for someone to tell me which files I should be looking for as far as HTC signing. What I would like to do is maybe strip it from the stock one, and insert it into a custom image.
Sent from the land of motorcycles!