Code:
/* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or the end of the world. Please do some research
* if you have any concerns about flashing a radio before flashing it!
* YOU are choosing to make these modifications, and if you point the
* finger at me for messing up your device, I will laugh at you. */
How to Flash:
In order for this to work, the HTC Sensation needs to be S-OFF. Flashing the radio with a corrupt file or interrupting the flash, can brick the device, please proceed with caution.
Download the your choice of radio for the HTC Sensation.
Make sure the filename is PG58IMG.zip exactly or it will not work and copy it to the same folder as adb (the /platform-tools folder within the Android SDK folder).
Connect the HTC Sensation to the computer via USB.
On the computer, open terminal and run the following commands:
Code:
adb push PG58IMG.zip /sdcard/PG58IMG.zip
adb shell md5sum /sdcard/PG58IMG.zip
NOTE: The md5 should match up the provide the original download location. If not, redownload & try again.
Code:
adb reboot bootloader
The HTC Sensation will reboot & usually boot into fastboot. Pressing the Power button will put the device into the bootloader.
The bootloader will scan for the radio update. Once it finds the update, select Yes.
Allow the bootloader to finish flashing the updated radio, and reboot the HTC Sensation normally.
Downloads:
From Gingerbread-based RUUs:
From the 1.23.163.1 RUU:
10.38.9007.00P_10.11.9007.06
md5: 9f4146692616cfd34d4c14412eec304a
From the 1.24.161.1 RUU:
10.39.9007.00P_10.11.9007.09
md5: 071ea37012ddce8df250c68f13a38cbb
From the 1.24.162.1 RUU:
has the same radio as the 1.24.161.1 RUU
From the 1.24.163.1 RUU:
has the same radio as the 1.24.161.1 RUU
From the 1.24.166.1 RUU:
has the same radio as the 1.24.161.1 RUU
From the 1.24.401.1 RUU:
has the same radio as the 1.24.161.1 RUU
From the 1.24.468.1 RUU:
has the same radio as the 1.24.161.1 RUU
From the 1.24.911.1 RUU:
has the same radio as the 1.24.161.1 RUU
From the 1.27.161.1 RUU:
10.42.9007.00P_10.11.9007.15
md5: 6e37fb179d2e7b765c1c9b4d5149f983
From the 1.27.168.5 RUU:
has the same radio as the 1.27.161.1 RUU
From the 1.27.187.5 RUU:
has the same radio as the 1.27.161.1 RUU
From the 1.27.401.3 RUU:
has the same radio as the 1.27.161.1 RUU
From the 1.27.531.2 RUU:
has the same radio as the 1.27.161.1 RUU
From the 1.28.707.2 RUU:
10.43.9007.00P_10.11.9007.19
md5: 13a111f7e9b7f5d59d119c75c7fb9627
From the 1.28.708.2 RUU:
has the same radio as the 1.28.707.2 RUU
From the 1.28.709.3 RUU:
has the same radio as the 1.28.707.2 RUU
From the 1.28.720.2 RUU:
has the same radio as the 1.28.707.2 RUU
From the 1.29.531.2 RUU:
has the same radio as the 1.27.161.1 RUU
From the 1.34.206.1 RUU:
10.43a.9007.00U_10.51.9007.27
md5: 81b96fd9db9d37965a698dc02e8a945b
From the 1.34.771.1_R RUU:
has the same radio as the 1.34.206.1 RUU
From the 1.34.841.6 RUU:
has the same radio as the 1.34.206.1 RUU
From the 1.35.61.1 RUU:
has the same radio as the 1.34.206.1 RUU
From the 1.35.75.1 RUU:
has the same radio as the 1.34.206.1 RUU
From the 1.35.401.1 RUU:
has the same radio as the 1.34.206.1 RUU
From the 1.35.666.1 RUU:
10.50.9007.00U_10.12.9007.21_2
md5: 3c2e34200c3a1d78dddc261bd32be850
From the 1.35.707.1 RUU:
has the same radio as the 1.34.206.1 RUU
From the 1.35.708.1 RUU:
has the same radio as the 1.34.206.1 RUU
From the 1.35.709.1 RUU:
has the same radio as the 1.34.206.1 RUU
From the 1.45.401.2 OTA/RUU:
10.56.9035.00U_10.14.9035.01
md5: 64a0383b87b4b780cf516f7d7e43b784
From the 1.45.531.1 OTA:
has the same radio as the 1.45.401.2 OTA/RUU
From the 1.50.401.1 RUU:
has the same radio as the 1.45.401.2 OTA/RUU
From the 1.72.401.1 RUU:
10.58.9035.00U_10.15.9035.02_2
md5: 722549b642a1374964798cc82100855e
From the 1.73.401.2 RUU:
has the same radio as the 1.72.401.1 RUU
From the 1.73.401.4 RUU:
has the same radio as the 1.72.401.1 RUU
From the 2.08.401.1 RUU:
11.59.3504.00U_11.16.3504.16
md5: 5341559678f9f2066315b5214a26cb84
gu1dry said:
In order for this to work, the HTC Sensation needs to be S-OFF.
Click to expand...
Click to collapse
10characters
Due to the impending release of AplhaRev X for the HTC Sensation,
It is not his impending has not yet release date!
Max128 said:
It is not his impending has not yet release date!
Click to expand...
Click to collapse
Impending doesn't meaning it has a release date, just that it's coming soon.
ok i Understand What You meant to say.
Thank you for your work
It kinda means that it's coming REALLY soon.
Thanks very much...
Sent from my HTC Sensation 4G using XDA App
gu1dry said:
Impending doesn't meaning it has a release date, just that it's coming soon.
Click to expand...
Click to collapse
Amazing! Thank you so much for this. Next thing I will do right after True root.
First, thank you for the write up and radio links and contribution to all of this.
Now for my question: Wouldn't fastboot be easier and safer?
1 - Copy the .img to your /sdk/tools folder (or whatever folder depending on computer OS). Verify MD5.
2 - Boot into bootloader (Vol Down + Pwr).
3 - Navigate to Fastboot (Vol down to Fastboot and press Pwr). Make sure your phone says Fastboot USB.
4 - Open command promt (or terminal depending on OS)in folder you put file.
5 - Type:
Code:
fastboot flash radio xxxx.img
xxxx is radio name.
I find this faster and safer. I find SDCards can corrupt the file easier than anything else therefore leaving the file on your computer to flash from is one less transfer and possible issue. As we all know, the 2 things that have the greatest chance of bricking a device are your Radio and Bootloader images.
Just my .02
Fastboot probably won't be available at first, htc locked that down pretty tight for signed packages, this method is certain to work when s-off is released...
When eng s-off arrives, that should be a different story
Sent from my HTC Sensation 4G using XDA App
Solidus_n313 said:
Fastboot probably won't be available at first, htc locked that down pretty tight for signed packages, this method is certain to work when s-off is released...
When eng s-off arrives, that should be a different story
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
Doesn't this link have Eng S-Off Bootloader?
Maybe I'm reading into things too much and not understanding.
setzer715 said:
Doesn't this link have Eng S-Off Bootloader?
Maybe I'm reading into things too much and not understanding.
Click to expand...
Click to collapse
It does contain an Eng s-off but you have to have S-off to flash it
setzer715 said:
First, thank you for the write up and radio links and contribution to all of this.
Now for my question: Wouldn't fastboot be easier and safer?
</snip>
Click to expand...
Click to collapse
Flashing radios via fastboot is actually more dangerous. Due to first, flashing the Engineering Hboot, which that process in itself is pretty dangerous, and second, fastboot will accept anything & during the flash, the radio image can become corrupt & brick the device.
gu1dry said:
Flashing radios via fastboot is actually more dangerous. Due to first, flashing the Engineering Hboot, which that process in itself is pretty dangerous, and second, fastboot will accept anything & during the flash, the radio image can become corrupt & brick the device.
Click to expand...
Click to collapse
i agree 100%, but most ppl who dont understand this will prefer conveinence/speed but risk bricking, over doing it the tried and tested method with minimal risk and maximum effort that reduces the chances of a fancy paperweight...
crackeyes said:
It does contain an Eng s-off but you have to have S-off to flash it
Click to expand...
Click to collapse
I think he was responding to Solidus_n313's comment that 'Fastboot probably won't be available at first'. Once you have radio S-OFF, it's trivial to get ENG S-OFF. It looks to me like AlphaRevX is hboot S-OFF but it's still S-OFF so we should be able to toggle @secuflag to get radio S-OFF without too much trouble. Basically, what I'm saying is that we'll all have ENG S-OFF very soon after AlphaRevX is released.
dazweeja said:
It looks to me like AlphaRevX is hboot S-OFF but it's still S-OFF so we should be able to toggle @secuflag to get radio S-OFF without too much trouble. Basically, what I'm saying is that we'll all have ENG S-OFF very soon after AlphaRevX is released.
Click to expand...
Click to collapse
yeah, alpharev's is hboot, as the radio is locked uber tight for the time being. i also agree that ENG S-OFF will arrive shortly after the release.
the major concern is the extra security protocols implemented in @secuflag on the S4G (dont appear this way for the E3D), and while they will be bypassed/overwritten in time, there appear to be redundant calls to @secuflag than can precede hboot and radio modifications...(from what ive seen and recognize at least)
all i know is that if/when alpharev and teamwin collaborate, all these issues will no longer be a problem, but that seems to be a long shot, as the 2 are having some issues with each other atm :/
Solidus_n313 said:
the major concern is the extra security protocols implemented in @secuflag on the S4G (dont appear this way for the E3D), and while they will be bypassed/overwritten in time, there appear to be redundant calls to @secuflag than can precede hboot and radio modifications...(from what ive seen and recognize at least)
Click to expand...
Click to collapse
If it's S-OFF, eMMC write-protection is not enabled at boot so we can write to radio_config and toggle @secuflag directly. If the eMMC write-protection is still enabled, then I don't see how the phone could be considered S-OFF (or how we could flash custom ROMs for that matter). I guess it will all become clear in time.
gu1dry said:
Flashing radios via fastboot is actually more dangerous. Due to first, flashing the Engineering Hboot, which that process in itself is pretty dangerous, and second, fastboot will accept anything & during the flash, the radio image can become corrupt & brick the device.
Click to expand...
Click to collapse
I can see that, I guess I somehow got it in my head that fastboot was always the safest way to flash images. I bricked a G1 once, LONG time ago, by trying to flash an HBoot in recovery, but that is still different than what you are doing.
crackeyes said:
It does contain an Eng s-off but you have to have S-off to flash it
Click to expand...
Click to collapse
it's funny to me, since doesn't that mean we'd need a signed s-off bootloader?
... hilarious.
Which method of Flashing Radios is Safer....my opinion.
I disagree with the statement that updating the radio through bootloader is safer than fastboot for the following reasons:
First it generally thought that flashing radio.img through bootloader update (PG58IMG.zip for the sensation) method unpacks the radio.img to /cache first then flashes from /cache which makes it susceptible to corruption and there are no checks before the radio.img is flashed
and second there are file checks performed before fastboot flashes the radio.img.
I run the G2/DesireZ radio thread HERE :http://forum.xda-developers.com/showthread.php?t=970809
In which I have seen several bricks from the bootlaoder update (PG58IMG.zip for the sensation) method flashing a corrupt .img file and never any from flashing the radio.img through fastboot. My radio.img's have been downloaded well over 10000 times and this has been my experince with flashing radio's.
Related
There seems to be an awful lot of confusion about radios on the Inspire 4G. Most of the threads out there insist that you need ENG S-OFF to flash a radio. However to root our phones we had to flash a radio without having ENG S-OFF. I am attaching 3 radios known to work on the Inspire, I have prepared them to be flashed without ENG S-OFF and will explain how to make your own in the future. The official radio thread for all our phones(Inspire and Desire HD) is located here:
http://forum.xda-developers.com/showpost.php?p=9891546&postcount=1
More information on Radio S-OFF and ENG S-OFF can be found here:
HTC Vision Wiki
Using ENG S-OFF and fastboot to load radio images is more risky than loading the file on the sdcard and then checking the md5sum of the file because you have verified that the copy to the sdcard was completed correctly, rather than having no check with fastboot loading the file directly.
Quote from HTC Vision Wiki regarding ENG S-OFF:
This is totally optional and dangerous - if the write to the phone partition fails the phone will be bricked. At the moment there is no cure for a phone that has been bricked by a failed hboot install.
***DISCLAIMER***
YOUR WARRANTY IS NOW VOID! I AM NOT RESPONSIBLE IF THIS PROCESS BRICKS YOUR PHONE, CAUSES YOUR GIRLFRIEND/WIFE TO LEAVE YOU, SUMMONS DEMONS, SOILS YOUR IMMORTAL SOUL, ENDS THE WORLD. USE AT YOUR OWN RISK.
***/DISCLAIMER***
Make sure to check that there is no corruption in the process of getting the files and putting them on your sdcard. The best way to check this is to download the file, put it on your phone as PD98IMG.zip and from a command line/terminal, using adb, do:
Code:
adb shell md5sum /sdcard/PD98IMG.zip
*BE VERY CAREFUL WITH THIS PROCESS YOU CAN BRICK YOUR PHONE WITH A CORRUPT RADIO.IMG*
To flash a radio using hboot with radio S-OFF you can simply take the zip file PD98IMG.zip from the hack kit (IN THE RADIO FOLDER) (Thanks ATTN1) and remove the radio.img file from it using winrar or 7zip, and put a new radio.img from elsewhere in the zip named radio.img and using store (NO) compression or Normal compression. Make sure it is named exactly PD98IMG.zip and put it on the root of your sdcard. Reboot your phone into hboot and the new radio will prompt you to load. Press volume up on the phone and it will load automatically and ask you to press power to reboot.
Once you boot up normal you should see the new radio under baseband version in settings/about phone.
If you do not want the radio to flash every time you go into HBOOT you must remove or rename the file at the root of your card to something other than PD98IMG.zip
If you are creating your own PD98IMG.zip files make sure that the radio.img matches the md5sum of the original before placing it in the zip. Here is the md5sum of the 3 radios included in this post:
att - 12.39.60.19_26.06.04.06_M: 99f4994c7b8b193336cad0dc5ffd19b4 radio.img
telus - 12.35d.60.10f_26.06.03.24_M2: edc9b36f3e30b8a3aec0f8e5ebfe9484 radio.img
gb - 12.35d.60.140fU_26.08.03.07_M: b19c70e7d346c9f76ac31e1964fa4238 radio.img
Ace gb s - 12.41.60.19_26.06.04.14_M: 71ba0afe14b1caf5ba29da6f3e2ab755 radio.img
PD98IMG-att-12.39.60.19_26.06.04.06_M.zip
MD5 Checksum: dea534848a9b71fc54878c0111ceed76
PD98IMG-gb-12.35d.60.140fU_26.08.03.07_M.zip
MD5 Checksum: 2cf70fce7c649822bc67a719b0a68d46
PD98IMG-telus-Radio_12.35d.60.10f_26.06.03.24_M2.zip
MD5 Checksum: 64bb83fda93052fcc8c1423b7a433e77
PD98IMG-12.41.60.19_26.06.04.14_M.zip
MD5 Checksum: 9287AB3CE1E84CDCFF634755EA78D1B1
Thanks to clickclickpc for 12.41.60.19_26.06.04.14_M
att - 12.39a.60.19_26.06.06.30_M: 3d1ee5d6ceb4f58c126ffcf956b8fbd7
PD98IMG-att-12.39a.60.19_26.06.06.30_M.zip
MD5 Checksum: 33baebad8b1e7a20f4603aff0ba66468
This is the radio.img and rcdata.img from the newest AT&T ota released today(4/29/2010). I have included the rcdata.img in this for flashing because it apparently has parameters that effect the radio, however I have not found any information regarding what/how/why this all works.
This is the contents of the rcdata.img file in the newest AT&T ota:
Code:
QCT_UMTS_RADIO_VER=1
DisH=2
EnableHTCENS=1
AGPSNVSetting=1
EnDTM=0
MSCMode=10
HSDPACat=10
HSUPACat=6
IMEISVN=3
GEA3=1
QCT_UMTS_RADIO_END=1
For comparison here is the contents of the rcdata.img for the telus, gb, and original att.
Telus 12.35d.60.10f_26.06.03.24_M2:
Code:
QCT_UMTS_RADIO_VER=1
DisH=2
AGPSNVSetting=1
MSCMode=12
HSDPACat=10
HSUPACat=6
IMEISVN=1
GEA3=1
QCT_UMTS_RADIO_END=1
att 12.39.60.19_26.06.04.06_M:
Code:
QCT_UMTS_RADIO_VER=1
DisH=1
EnableHTCENS=1
AGPSNVSetting=1
EnDTM=0
MSCMode=10
HSDPACat=10
IMEISVN=02
QCT_UMTS_RADIO_END=1
GB:
Code:
QCT_UMTS_RADIO_VER=1
MSCMode=10
QCT_UMTS_RADIO_END=1
Downgrade Rom:
Code:
QCT_UMTS_RADIO_VER=1
DisH=2
HSDPACat=10
HSUPACat=6
QCT_UMTS_RADIO_END=1
Good idea. I've been walking people through this for the past week .
Thanks ATTN1 indeed!
How hard would it be to flash a splash screen this way?
Sent from my hmmm the box said Inspire 4G using XDA Premium
App
This should be in the sticky, because it's how radio firmware (aka radios) should always be flashed. It's just safer, and it's not hard. There is just no need to urge people toward eng s-off - when in reality it gets most users absolutely nothing except increased exposure to real trouble.
Excellent.
attn1 said:
This should be in the sticky, because it's how radio firmware (aka radios) should always be flashed. It's just safer, and it's not hard. There is just no need to urge people toward eng s-off - when in reality it gets most users absolutely nothing except increased exposure to real trouble.
Excellent.
Click to expand...
Click to collapse
Agreed. Mods please sticky.
Eng S-off is pretty risky, this is painless.
lrs421 said:
Agreed. Mods please sticky.
Eng S-off is pretty risky, this is painless.
Click to expand...
Click to collapse
so is eng s-off still risky if you don't ever use it? I have installed and flashed a radio that seems to work well with all roms and don't intend on using another one.
Wished I would have been patient
mj0528 said:
so is eng s-off still risky if you don't ever use it? I have installed and flashed a radio that seems to work well with all roms and don't intend on using another one.
Wished I would have been patient
Click to expand...
Click to collapse
The real danger is in the process, if you brick your phone while performing eng s-off you won't be happy. Personally I've never found a need to swap radios, on reflash it. The stock radio is HSUPA with plenty speed.
lrs421 said:
Agreed. Mods please sticky.
Eng S-off is pretty risky, this is painless.
Click to expand...
Click to collapse
Eng S-off should be nonexistent now except for devs. This will save many headaches. Would this help the issue with people having the black screen in CMR? I also think mods should sticky this.
Sent from my Desire HD using XDA Premium App
lrs421 said:
The real danger is in the process, if you brick your phone while performing eng s-off you won't be happy. Personally I've never found a need to swap radios, on reflash it. The stock radio is HSUPA with plenty speed.
Click to expand...
Click to collapse
Is there a way to reverse eng s-off?
mudknot2005 said:
How hard would it be to flash a splash screen this way?
Sent from my hmmm the box said Inspire 4G using XDA Premium
App
Click to expand...
Click to collapse
I believe to update the splash screen you would have to flash hboot, the whole idea of this thread is to not have ENG S-OFF so you don't run the risk of messing up your phone by flashing hboot, whether on purpose or by accident. Barring that, I'm not sure how to flash the splash screen.
mj0528 said:
Is there a way to reverse eng s-off?
Click to expand...
Click to collapse
Yes, flashing back to stock using the PD...zip from the RUU turns it back on.
mj0528 said:
Is there a way to reverse eng s-off?
Click to expand...
Click to collapse
Also, I'm not sure if running the RUU itself puts it back on as I've never tried, maybe someone else can chime in.
I do know that if you extract the rom.zip and rename it to PD98IMG.zip and flash it in hboot it does restore it.
lrs421 said:
Also, I'm not sure if running the RUU itself puts it back on as I've never tried, maybe someone else can chime in.
I do know that if you extract the rom.zip and rename it to PD98IMG.zip and flash it in hboot it does restore it.
Click to expand...
Click to collapse
Running the stock RUU will unroot you, but you'll still be S-Off. Follow the instructions in this (http://forum.xda-developers.com/showthread.php?t=957692) thread to get S-On BEFORE you run the RUU.
Note: If you're flashing the RUU for purposes other than a return, it's not necessary to S-On. You can leave S-Off and still run stock (this is also nice because then you can flash a stock rooted just like they're suggesting flashing the radio, by renaming the ROM's .zip to PD98IMG and flashing through HBoot, rather than going through the whole root process again)
homeslice976 said:
Running the stock RUU will unroot you, but you'll still be S-Off. Follow the instructions in this (http://forum.xda-developers.com/showthread.php?t=957692) thread to get S-On BEFORE you run the RUU.
Note: If you're flashing the RUU for purposes other than a return, it's not necessary to S-On. You can leave S-Off and still run stock (this is also nice because then you can flash a stock rooted just like they're suggesting flashing the radio, by renaming the ROM's .zip to PD98IMG and flashing through HBoot, rather than going through the whole root process again)
Click to expand...
Click to collapse
You're thinking s-on, we're talking about eng s-on. They'e different
lrs421 said:
The real danger is in the process, if you brick your phone while performing eng s-off you won't be happy. Personally I've never found a need to swap radios, on reflash it. The stock radio is HSUPA with plenty speed.
Click to expand...
Click to collapse
Flashing radios and hboots carry the same risks.
This method is safer than using fastboot with eng s-off to flash radios, and it's why I did it this way in the hack kit. If you already have eng s-off, you should still use this method.
lrs421 said:
You're thinking s-on, we're talking about eng s-on. They'e different
Click to expand...
Click to collapse
I was ENG S-Off, and the way I was able to get back to S-On was to rerun steps 2 and 3 of your hack kit, but instead of "./gfree -f" I ran ".g/free -s on" and I was back to S-On. At least that's what bootloader showed. Then I reran the hack kit to obtain S-Off and didn't do the ENG S-Off again.
Towards the middle of the thread I linked was where I got that information. Either way, this is the only way I flash radios anymore.
attn1 said:
Flashing radios and hboots carry the same risks.
This method is safer than using fastboot with eng s-off to flash radios, and it's why I did it this way in the hack kit. If you already have eng s-off, you should still use this method.
Click to expand...
Click to collapse
Thanks, am I correct in saying that flashing back to stock using the rom.zip from the RUU restores it but running the RUU alone will not?
So just having Eng s off and not using it is no danger?
Sent from my Desire HD using XDA Premium App
homeslice976 said:
I was ENG S-Off, and the way I was able to get back to S-On was to rerun steps 2 and 3 of your hack kit, but instead of "./gfree -f" I ran ".g/free -s on" and I was back to S-On. At least that's what bootloader showed. Then I reran the hack kit to obtain S-Off and didn't do the ENG S-Off again.
Towards the middle of the thread I linked was where I got that information
Click to expand...
Click to collapse
That's:
ACE PVT SHIP S-OFF RL
English S-off is not done via the hack kit. It's se[erate from what's above.
http://forum.xda-developers.com/showthread.php?t=994670
Code:
/* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or the end of the world. Please do some research
* if you have any concerns about flashing a radio before flashing it!
* YOU are choosing to make these modifications, and if you point the
* finger at me for messing up your device, I will laugh at you. */
How to Flash:
In order for this to work, the HTC Desire HD needs to be S-OFF. Flashing the radio with a corrupt file or interrupting the flash, can brick the device, please proceed with caution.
Download the your choice of radio for the HTC Desire HD.
Make sure the filename is PD98IMG.zip exactly or it will not work and copy it to the same folder as adb (the /platform-tools folder within the Android SDK folder).
Connect the HTC Desire HD to the computer via USB.
On the computer, open terminal and run the following commands:
Code:
adb push PD98IMG.zip /sdcard/PD98IMG.zip
adb shell md5sum /sdcard/PD98IMG.zip
NOTE: The md5 should match up the provide the original download location. If not, redownload & try again.
Code:
adb reboot bootloader
The HTC Desire HD will reboot & usually boot into fastboot. Pressing the Power button will put the device into the bootloader.
The bootloader will scan for the radio update. Once it finds the update, select Yes.
Allow the bootloader to finish flashing the updated radio, and reboot the HTC Desire HD normally.
Downloads:
From Froyo-based RUUs:
From the 1.15.405.1 RUU:
12.21.60.12_26.02.00.09
md5: 4aba7abfbeb93cd7c0061eb9eb706d97
From the 1.24.405.1 RUU:
has the same radio as the 1.15.405.1 RUU
From the 1.28.405.1 RUU:
12.28.60.140e_26.03.00.04
md5: 3ad11deb26f4b39186dce334d606c130
From the 1.28.405.1_R2 RUU:
12.28a.60.140e_26.03.02.08
md5: 4cf186ce53723a5185fe21e76d82dd38
From the 1.31.207.1 RUU:
12.28b.60.140e_26.03.02.26
md5: f01f7a2b264811636c470c7b530fece9
From the 1.31.1400.1 RUU:
has the same radio as the 1.28.405.1_R2 RUU
From the 1.32.207.1 RUU:
has the same radio as the 1.28.405.1_R2 RUU
From the 1.32.405.3 RUU:
12.28b.60.140e_26.03.02.15
md5: 2e1759eb2308a5ec0910122be9d6b5f0
From the 1.32.405.6 OTA/RUU:
has the same radio as the 1.31.207.1 RUU
From the 1.32.707.1 RUU:
has the same radio as the 1.28.405.1_R2 RUU
From the 1.32.832.6 RUU:
has the same radio as the 1.31.207.1 RUU
From the 1.39.111.1 RUU:
has the same radio as the 1.31.207.1 RUU
From the 1.40.61.2 RUU:
has the same radio as the 1.31.207.1 RUU
From the 1.43.466.2 RUU:
has the same radio as the 1.31.207.1 RUU
From the 1.43.1010.2 RUU:
has the same radio as the 1.31.207.1 RUU
From the 1.60.1400.7 RUU:
12.32.60.140e_26.04.00.05
md5: f6f0f08af1b4afa0ce883041cad736b0
From the 1.72.405.3_R RUU:
12.28e.60.140f_26.04.02.17
md5: 14b8dacee267c9598107339c6001275d
From the 1.72.405.3_R2 OTA/RUU:
has the same radio as the 1.72.405.3_R RUU
From the 1.75.75.2 RUU:
has the same radio as the 1.72.405.3_R RUU
From the 1.75.110.2_R RUU:
has the same radio as the 1.72.405.3_R RUU
From the 1.75.771.2 RUU:
12.28g.60.140f_26.05.02.15
md5: 24ad1d0f9fb48dbd8cdefe4ac4af48ed
From the 1.75.1400.4 RUU:
12.35a.60.140f_26.04.03.30
md5: faf2e82e101907f8587d041b1301a5ed
From the 1.80.502.3 RUU (AT&T Inspire 4G Stock):
12.39.60.19_26.06.04.06
md5: dea534848a9b71fc54878c0111ceed76
From the 1.83.415.4 RUU:
has the same radio as the 1.72.405.3_R RUU
From the 1.84.61.2 RUU:
12.28g.60.140f_26.05.05.27
md5: c7eea236eaaa2edf978934633d58398d
From the 1.84.502.11 RUU:
12.39a.60.19_26.06.06.30
md5: 991dc7acd70fa13d47ca6d0a4b6f857f
From the 1.84.661.1_R RUU:
12.35d.60.140f_26.06.03.24
md5: 64bb83fda93052fcc8c1423b7a433e77
From the 1.84.832.2 RUU:
has the same radio as the 1.84.61.2 RUU
From the 1.89.516.2_R RUU:
has the same radio as the 1.84.61.2 RUU
From Gingerbread-based RUUs:
From the 2.16.0.0 RUU:
12.41.60.19_26.06.04.14
md5: f964b25bda91dd377c78b54ce46fdd7b
From the 2.25.0.0 RUU:
12.35d.60.140f_26.08.03.07
md5: 2cf70fce7c649822bc67a719b0a68d46
From the 2.25.1400.1 RUU:
has the same radio as the 2.25.0.0 RUU
From the 2.31.1400.1 RUU:
has the same radio as the 2.25.0.0 RUU
From the 2.36.405.5 RUU:
12.54.60.25_26.09.04.11
md5: 167130dc3853eae382526fbf5b2a9070
From the 2.36.405.8_R RUU:
has the same radio as the 2.36.405.5 RUU
From the 2.37.707.3 RUU:
has the same radio as the 2.36.405.5 RUU
From the 2.37.762.2 RUU:
has the same radio as the 2.36.405.5 RUU
From the 2.37.832.6 RUU:
has the same radio as the 2.36.405.5 RUU
From the 2.42.415.1 RUU:
has the same radio as the 2.36.405.5 RUU
From the 2.43.661.1 OTA/RUU:
12.56.60.25_26.10.04.03
md5: 73fc5a09b44b4c4367ea75a231ce0818
From the 2.47.502.7 RUU:
has the same radio as the 2.43.661.1 OTA/RUU
From the 2.50.405.2 RUU:
has the same radio as the 2.36.405.5 RUU
From the 2.50.771.2 RUU:
12.56.60.25_26.09.04.28
md5: c760c92ab29ba60249250db0ae71e788
From the 2.52.1010.2 RUU:
12.59.60.26_26.11.04.21
md5: b5062872cf6f2898d74e9f6a0dbb9664
From the 3.06.405.1 RUU:
12.62.60.27_26.13.04.19
md5: 7e3f9b9381209e7643e7e94ea7028ad0
Where is my radio and what is the latest one that u have???
Have anyone test it???
eliashadow said:
Where is my radio and what is the latest one that u have???
Have anyone test it???
Click to expand...
Click to collapse
The 26.08.04.07 radio is not available from a reliable source. And the radio are listed in release order, from oldest to newest. The RUU the 26.09.04.11 radio came from just leaked 4 hours ago.
Beware the Typo:
Code:
adb shell md5sum /sdcard/PD98MG.zip
Nice work
schauol1 said:
Beware the Typo:
Code:
adb shell md5sum /sdcard/PD98MG.zip
Nice work
Click to expand...
Click to collapse
Fix'd, thanks for pointing that out.
rils for Radio 12.54.60.25_26.09.04.11_M2 is include
doudou1206 said:
rils for Radio 12.54.60.25_26.09.04.11_M2 is include
Click to expand...
Click to collapse
No, these are just radios.
you can also just reboot into bootloader and flash. It worked perfect.
klquicksall said:
you can also just reboot into bootloader and flash. It worked perfect.
Click to expand...
Click to collapse
But transferring without verifying the md5sums can cause people to flash corrupted files, which will most likely brick the device.
gu1dry said:
But transferring without verifying the md5sums can cause people to flash corrupted files, which will most likely brick the device.
Click to expand...
Click to collapse
Yes that is possible. Flashing any. Radio is dangerous. People just need to use caution. Still better than fastboot.
Sent from my Desire HD using XDA Premium App
I can't see the point in doing this when you can easily download the radio from the radio thread and check the md5 then drop the radio.img in the folder from my thread then follow the guide on my thread
With how you described to do it this way seems a lot of messing about having to rename radio and typing loads of commands when the guide I created is a lot more simple
Could you please explain the benefits of your method???
Sent from Pluto
klquicksall said:
Yes that is possible. Flashing any. Radio is dangerous. People just need to use caution. Still better than fastboot.
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
Not totally true I flashed a radio from htc desire s Rom by accident on to dhd and all it did was sit on splash screen pulled battery and reflashed correct radio no brick. Also its been mentioned that the dhd has a back up radio that kicks in if you flash the wrong one or a corrupted radio( not tested myself).
Sent from Pluto
leith51 said:
I can't see the point in doing this when you can easily download the radio from the radio thread and check the md5 then drop the radio.img in the folder from my thread then follow the guide on my thread
With how you described to do it this way seems a lot of messing about having to rename radio and typing loads of commands when the guide I created is a lot more simple
Could you please explain the benefits of your method???
Sent from Pluto
Click to expand...
Click to collapse
Well, as a Linux user, I haven't managed to make fastboot work... And this method is completely platform independent. For me it's great
swiftscythe said:
Well, as a Linux user, I haven't managed to make fastboot work... And this method is completely platform independent. For me it's great
Click to expand...
Click to collapse
So its good for Linux users and works fine that's good to know will add link with credits to my thread for Linux users my guide will cover all Windows Linux and mac with links to appropriate threads
Sent from Pluto
This is the best, because it is the simplest.
Just download the zip file, put the downloaded zip file in the root of the sdcard, restart to bootloader, choose bootloader, press volume up button when asked.
Finish!
I've been waiting for something like this since the first time I wanted to update my DHD radio image.
Never use my laptop anymore.
Thx bro.
What is the point of this thread?!?!?
There's already one thread that covers the radios roms for the DHD....
shutdown this please...
Thanks for your nice work..
swiftscythe said:
Well, as a Linux user, I haven't managed to make fastboot work... And this method is completely platform independent. For me it's great
Click to expand...
Click to collapse
leith51 said:
So its good for Linux users and works fine that's good to know will add link with credits to my thread for Linux users my guide will cover all Windows Linux and mac with links to appropriate threads
Click to expand...
Click to collapse
Erm, can we re-phrase that to "it's good for those linux users that can't get fastboot to work". As an Ubuntu user I got fastboot to work without problems and prefer the fastboot method. My personal preference maybe but I just don't like the implication of the above wording. Thank you.
Thanks for this gu1dry. Did you also put these on the cyanogenmod wiki?
To the ones wondering what's the point of these PD98IMG radios:
You don't need fastboot. You don't need an ENG s-off HBOOT, only radio S-off.
It's easier and safer.
sonym4n said:
This is the best, because it is the simplest.
Just download the zip file, put the downloaded zip file in the root of the sdcard, restart to bootloader, choose bootloader, press volume up button when asked.
Finish!
I've been waiting for something like this since the first time I wanted to update my DHD radio image.
Never use my laptop anymore.
Thx bro.
Click to expand...
Click to collapse
+1
There is no need for adb anymore, just drop in the sd root and reboot
Code:
/* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or the end of the world. Please do some research
* if you have any concerns about flashing a radio before flashing it!
* YOU are choosing to make these modifications, and if you point the
* finger at me for messing up your device, I will laugh at you. */
How to Flash:
In order for this to work, the HTC Desire S needs to be S-OFF. Flashing the radio with a corrupt file or interrupting the flash, can brick the device, please proceed with caution.
Download the your choice of radio for the HTC Desire S.
Make sure the filename is PG88IMG.zip exactly or it will not work and copy it to the same folder as adb (the /platform-tools folder within the Android SDK folder).
Connect the HTC Desire S to the computer via USB.
On the computer, open terminal and run the following commands:
Code:
adb push PG88IMG.zip /sdcard/PG88IMG.zip
adb shell md5sum /sdcard/PG88IMG.zip
NOTE: The md5 should match up the provide the original download location. If not, redownload & try again.
Code:
adb reboot bootloader
The HTC Desire S will reboot & usually boot into fastboot. Pressing the Power button will put the device into the bootloader.
The bootloader will scan for the radio update. Once it finds the update, select Yes.
Allow the bootloader to finish flashing the updated radio, and reboot the HTC Desire S normally.
Downloads:
From Gingerbread-based RUUs:
From the Saga Test RUU:
20.23.30.0802U_38.02.01.11
md5: 68b46430f42c07ecdc4f1e68bdaf9123
From the 1.28.401.1 RUU:
20.28b.30.0805U_38.03.02.11
md5: 27d85ee9604584becfa59c213708370a
From the 1.30.110.2_R RUU:
has the same radio as the 1.28.401.1 RUU
From the 1.30.111.1 RUU:
has the same radio as the 1.28.401.1 RUU
From the 1.30.112.1 RUU:
has the same radio as the 1.28.401.1 RUU
From the 1.31.61.1 RUU:
has the same radio as the 1.28.401.1 RUU
From the 1.31.65.1 RUU:
has the same radio as the 1.28.401.1 RUU
From the 1.31.206.1 RUU:
20.28b.30.0805U_38.03.02.14
md5: a898a290eb58ec618ceb3865a90dc878
From the 1.31.351.1 RUU:
20.28b.30.0805U_38.03.02.15
md5: 757cde85b4e8736db93088134f9afc8e
From the 1.31.707.2_R RUU:
has the same radio as the 1.31.351.1 RUU
From the 1.31.720.2_R RUU:
has the same radio as the 1.31.206.1 RUU
From the 1.31.771.1 RUU:
has the same radio as the 1.31.206.1 RUU
From the 1.31.832.3 RUU:
20.28d.30.0805U_3805.04.02.01
md5: 631afebe525a455f34b2238108ac1b43
From the 1.31.950.2_R RUU:
has the same radio as the 1.31.206.1 RUU
From the 1.31.1020.1 RUU:
20.28c.30.0805U_38.03.02.16
md5: 5d82b1d2a70a46eaa93ad10964809f1a
From the 1.32.161.1 RUU:
has the same radio as the 1.31.351.1 RUU
From the 1.35.1113.2 RUU:
has the same radio as the 1.31.832.3 RUU
From the 1.36.415.6 RUU:
has the same radio as the 1.31.832.3 RUU
From the 1.36.841.3 RUU:
has the same radio as the 1.31.832.3 RUU
From the 1.46.1400.8 RUU:
20.28f.30.085AU_3805.04.02.28
md5: f4951ae92f6abd85823d916f46e5312e
From the 1.47.401.4 RUU:
20.28I.30.085AU_3805.06.02.03
md5: 57a3fcc5f72ec928050dbcb32018215f
From the 1.47.832.1 RUU:
has the same radio as the 1.47.401.4 RUU
From the 1.47.950.3 RUU:
has the same radio as the 1.47.401.4 RUU
From the 1.48.707.1 RUU:
has the same radio as the 1.47.401.4 RUU
From the 2.10.401.4 OTA:
20.48.30.0822U_3822.09.08.20
md5: 053544276893dfcc3a7a722c834b6020
From the 2.10.401.5 RUU:
20.4801.30.0822U_3822.10.08.04
md5: 2fddef29eb1f8001d9cad14f48061f54
Thanks for putting these in one place, and even though there's a warning about bricking phone's, I would like to warn everyone that flashing a radio is very rarely necessary, and should not be done on a whim!!! Not enough is known about recovering from a bad flash on the NVRam (radio), and if this happens you could end up with a very expensive calculator.
Thanks a LOT !!!!!!! My radio is here, so i can flash others, and if i find errors, i can come back. Thanks again man.
New Radio from leaked official ROM
This is the Radio that came with the recently leaked official Desire S Sense v3.0 ROM.
20.4130.0818U_3817.07.00.19_M RADIO
so is this linux only or can the terminal be replaced with the command prompt?
dan-fish said:
so is this linux only or can the terminal be replaced with the command prompt?
Click to expand...
Click to collapse
This isn't for linux specifically, this is also possible for windows, where by terminal he means windows command prompt (CMD), assuming that you have the relevant ADB installed.
If you don't download it from here
I have a question: there are some compatibility issue between radio and hboot version?
You can use the new radio with the old hboot.
Any problem for use that.
If you want to install the new hboot while you have already install the new radio, there's no problem of incompatibility
ben_pyett said:
This is the Radio that came with the recently leaked official Desire S Sense v3.0 ROM.
20.4130.0818U_3817.07.00.19_M RADIO
Click to expand...
Click to collapse
Can anyone confirm what the md5sum for this file should be?
Any chance a download link for this radio could be added to the top post?
There is already newer radio available - 20.44.30.0821U_3821.08.00.24_M
uoosuow said:
There is already newer radio available - 20.44.30.0821U_3821.08.00.24_M
Click to expand...
Click to collapse
[RADIO](added ril)New leaked radio:20.44.30.0821U_3821.08.00.24_M
Well done @ben_pyett
Thk's
It would be nice if the top post could be updated with these radios & md5sums
hint hint @gu1dry
runagate17 said:
It would be nice if the top post could be updated with these radios & md5sums
hint hint @gu1dry
Click to expand...
Click to collapse
I only add radios pulled from full RUUs (that I pulled personally) or reliable sources.
gu1dry said:
I only add radios pulled from full RUUs (that I pulled personally) or reliable sources.
Click to expand...
Click to collapse
Fair enough! much safer that way.....you don't get people shouting at you then!
If people want the other leaked RADIO's there are links to them elsewhere!
Question:
Is there somewhere a GUIDE for downgrading Radio if the leaked one will not work how i hope?
Sure. The guide are so simple:
you'll have to use fastboot command but not the PG88IMG flash
Use a simple command : fastboot flash radio your_radio_file.img
And as "your_radio_file.img" i'll take the image file included in PG88IMG.zip.
Am i right?
When you unzipped the PG88IMG, you've found a file "radio.img"
my radio on my HTC DS is 20.28I.30.085AU_3805.06.02.03_M on this post no "_M" on the end. is there a difference on that? thanks!
So I am returning to stock from this build:
ROM: CyanogenMod 9 RC1
FIRMWARE: 3.32.401.x & 3.32.401.10x
Radio:/ 11.22.3504.07_M
Hboot: 1.27.1100
And I have a few questions because reading the guides just didn't help me:
1. I can't understand completely the name of the RUU's: RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe
1.27.401.3 - is this HBOOT version?
10.42.9007.00P_10.11.9007.15 - This is radio but why does it have 2 values?
192183- What is this?
2.
If you have S Off, this doesn't matter, but you should always try to flash the oldest RUU, so that it is easier to S Off later, unless you don't intend to perform S Off again.
Click to expand...
Click to collapse
I am S Off and I want to return my phone to S-on for warranty purposes then S-Off again so I must flash the oldest RUU right? If it is this is the situation how to determine the oldest RUU by HBOOT version?
3. Firmwares? What about them does the RUU overwrites the firmware should I downgrade firmware before flashing older RUU and can it be done? Is there such thing as firmware and RUU compatibility? If there is which firmware corresponds to which RUU, the firmwares have version that are not mentioned anywhere else?
4. Which RUU's I can flash and which I can't? I mean what should I look for to be suitable? Should I install RUU that has the same HBOOT version as mine or I can install older like I am ICS and I want to install GB RUU so I can S-Off easier latter?
So I am a little confused about downgrading and picking suitable versions of everything.
I decided to try without matching anything just downloading the RUU with the oldest hboot and flash it. It's RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe and my device info is in the beggining of the thread. So in FASTBOOT i run .exe and I get
error: -5001. Please make sure you have finished any previous setup and closed other applications.
Click to expand...
Click to collapse
Is the problem with compatibility or something else?
Okay seems I've asked too much. Well I want to understand all those things but for now this is what I need to know:
Will flashing this RUU: RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed.exe
On this Phone:
ROM: CyanogenMod 9 RC1
FIRMWARE: 3.32.401.x & 3.32.401.10x
Radio: 11.22.3504.07_M
Hboot: 1.27.1100
Will be successful and can I S-off and Root again easy latter?
SsBloodY said:
So I am returning to stock from this build:
ROM: CyanogenMod 9 RC1
FIRMWARE: 3.32.401.x & 3.32.401.10x
Radio:/ 11.22.3504.07_M
Hboot: 1.27.1100
And I have a few questions because reading the guides just didn't help me:
1. I can't understand completely the name of the RUU's: RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe
1.27.401.3 - is this HBOOT version?
10.42.9007.00P_10.11.9007.15 - This is radio but why does it have 2 values?
192183- What is this?
2. I am S Off and I want to return my phone to S-on for warranty purposes then S-Off again so I must flash the oldest RUU right? If it is this is the situation how to determine the oldest RUU by HBOOT version?
3. Firmwares? What about them does the RUU overwrites the firmware should I downgrade firmware before flashing older RUU and can it be done? Is there such thing as firmware and RUU compatibility? If there is which firmware corresponds to which RUU, the firmwares have version that are not mentioned anywhere else?
4. Which RUU's I can flash and which I can't? I mean what should I look for to be suitable? Should I install RUU that has the same HBOOT version as mine or I can install older like I am ICS and I want to install GB RUU so I can S-Off easier latter?
So I am a little confused about downgrading and picking suitable versions of everything.
I decided to try without matching anything just downloading the RUU with the oldest hboot and flash it. It's RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe and my device info is in the beggining of the thread. So in FASTBOOT i run .exe and I get Is the problem with compatibility or something else?
Click to expand...
Click to collapse
SsBloodY said:
Okay seems I've asked too much. Well I want to understand all those things but for now this is what I need to know:
Will flashing this RUU: RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed.exe
On this Phone:
ROM: CyanogenMod 9 RC1
FIRMWARE: 3.32.401.x & 3.32.401.10x
Radio: 11.22.3504.07_M
Hboot: 1.27.1100
Will be successful and can I S-off and Root again easy latter?
Click to expand...
Click to collapse
1. RUU naming convention
RUU_Pyramid_<an extra LE in the name if XE>_HTC_<country/cariier>_<rom main version>_Radio_<radio version>_release_<release version>_signed.exe
dont bother about release version ..we dont need that
the only concerns are ..
country/carrier -> which determines the cid
rom main version ->explains whether youy are on GB or ICS (lesser the version ..older it is ...only between same country/carrier RUU's)
radio version -> tells the radio
2.oldest RUU ..ive explained earlier ..the main version should be least ..but this comparison is only valid if the country/carrier matches
eg:
in case of
RUU_pyramid_tmous_1.52.xx
and
RUU_pyramid_europe_1.27.xx (you cant say which one is oldest)
3.no firmware questions when we are talking about RUU (firmware arises when you talk about custom roms)
RUU has everything ...it wipes everything and converts it to stock (RUU cant touch the SOFF and CID though ..they can be changed only manually ..i.e. by we doing it manually by commands)
4.which RUU ..is you decide by CID ...
if you are supercid ..and dont know the original cid
you need to select the RUU based on your country and carrier
there is an excellent guide on RUU and it explains everything
here is the link to it ...do read it
(it helps you in finding right RUU too )
RUU RELEATED INFO AND FLASHING GUIDE
also remember by flashing RUU ..you wont lose SOFF ...unless you change it manually ..to know how to change it please refer the above guide
also i believe this answer ..answers your second post questions too
Thanks a lot! But I still got the problem with error I mentionted in the 1st post (error 5001) I tried with 1.27 and 1.28 HTC-Pyramid-Europe. What should I do is flashing through safe mod possible.
Sent from my HTC Sensation using xda app-developers app
SsBloodY said:
Thanks a lot! But I still got the problem with error I mentionted in the 1st post (error 5001) I tried with 1.27 and 1.28 HTC-Pyramid-Europe. What should I do is flashing through safe mod possible.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
im confused
did you mean you solved it ? or are you asking me how to bypass that error ?
anyways
you need to keep the phone connected to pc in bootloader/fastboot and then run the RUU.exe
Also ..if you did HTC-DEV unlock ..relock the bootloader (fastboot oem lock) and run the RUU.exe
I can't solve the problem. I connect it in bootloader/fastboot and try to run the RUU.exe. And I did revolutionary S-OFF.
Hey no idea that
error: -5001. Please make sure you have finished any previous setup and closed other applications.
is pretty annoying.
What is the CID currently on the phone ?
The RUU with xxx.401.xxxx IRC will require SuperCID (11111111) or a CID of HTC__001.
1.27... will end up installing HBOOT 1.17.0008 (just gone through the process on my replacement replacement phone.
As mentioned earlier you'll keep S-OFF and your existing CID after installing the RUU.
As far as the comms are concerned have you got the latest HTC drivers on the PC ?
---------------snip-------------
anyways
you need to keep the phone connected to pc in bootloader/fastboot and then run the RUU.exe
Also ..if you did HTC-DEV unlock ..relock the bootloader (fastboot oem lock) and run the RUU.exe
---------------snip-------------
I've recently run a few RUUs on my phone to get to a state where I could have a carrier backup, just in case (I forgot to get one immediately after S-OFF/custome recovery, doh). At no point did I re-lock the bootloader, I unlocked it (HBOOT 1.27.0000) and it's stayed unlocked the whole time, always worked perfectly. I also didn't have the phone in bootloader/fastboot mode, it was just on the home screen, again worked perfectly. I guess YMMV.
I am super CID.
gol_n_dal said:
I've recently run a few RUUs on my phone to get to a state where I could have a carrier backup, just in case (I forgot to get one immediately after S-OFF/custome recovery, doh). At no point did I re-lock the bootloader, I unlocked it (HBOOT 1.27.0000) and it's stayed unlocked the whole time, always worked perfectly. I also didn't have the phone in bootloader/fastboot mode, it was just on the home screen, again worked perfectly. I guess YMMV.
Click to expand...
Click to collapse
regarding RUU running normally ..you should have usb debugging enabled ..and need to have proper drivers too to recognize the device ..
running from fastboot no hassle there.. (most 155 errors can be prevented from running from fastboot)
couple of people were thrown error 99 when they ran RUU with unlocked bootloader ..so relock is a safer bet to prevent that error too
Hi, my current version of Baseband is 20.28I.30.085AU_3805.06.02.03_M and i want to install and run ROM ICE DS v 4.4 where i saw that recommended radio is: 20.72.30.0833U_3831.17.00.310..so i am not sure what should i do(how to upgrade it)??, i taught it's better to ask here than to search for some guides etc. coz i read that if something is done wrong , the phone is dead
bobahajduk said:
...i taught it's better to ask here than to search for some guides etc. coz i read that if something is done wrong , the phone is dead
Click to expand...
Click to collapse
Very bad thought and wrong assumption that you'll get better help here by hell knows whom, instead of reading the guides that were written to be understood and executed by thousands of people till today.
See this Guide:
nodeffect said:
HTC Desire S Tutorials/Guides
Click to expand...
Click to collapse
Sent from my Desire S
so i found the list:'' From the Saga Test RUU:
20.23.30.0802U_38.02.01.11
md5: 68b46430f42c07ecdc4f1e68bdaf9123
From the 1.28.401.1 RUU:
20.28b.30.0805U_38.03.02.11
md5: 27d85ee9604584becfa59c213708370a
From the 1.30.110.2_R RUU:
has the same radio as the 1.28.401.1 RUU
From the 1.30.111.1 RUU:
has the same radio as the 1.28.401.1 RUU
From the 1.30.112.1 RUU:
has the same radio as the 1.28.401.1 RUU
From the 1.31.61.1 RUU:
has the same radio as the 1.28.401.1 RUU
From the 1.31.65.1 RUU:
has the same radio as the 1.28.401.1 RUU
From the 1.31.206.1 RUU:
20.28b.30.0805U_38.03.02.14
md5: a898a290eb58ec618ceb3865a90dc878
From the 1.31.351.1 RUU:
20.28b.30.0805U_38.03.02.15
md5: 757cde85b4e8736db93088134f9afc8e
From the 1.31.707.2_R RUU:
has the same radio as the 1.31.351.1 RUU
From the 1.31.720.2_R RUU:
has the same radio as the 1.31.206.1 RUU
From the 1.31.771.1 RUU:
has the same radio as the 1.31.206.1 RUU
From the 1.31.832.3 RUU:
20.28d.30.0805U_3805.04.02.01
md5: 631afebe525a455f34b2238108ac1b43
From the 1.31.950.2_R RUU:
has the same radio as the 1.31.206.1 RUU
From the 1.31.1020.1 RUU:
20.28c.30.0805U_38.03.02.16
md5: 5d82b1d2a70a46eaa93ad10964809f1a
From the 1.32.161.1 RUU:
has the same radio as the 1.31.351.1 RUU
From the 1.35.1113.2 RUU:
has the same radio as the 1.31.832.3 RUU
From the 1.36.415.6 RUU:
has the same radio as the 1.31.832.3 RUU
From the 1.36.841.3 RUU:
has the same radio as the 1.31.832.3 RUU
From the 1.46.1400.8 RUU:
20.28f.30.085AU_3805.04.02.28
md5: f4951ae92f6abd85823d916f46e5312e
From the 1.47.401.4 RUU:
20.28I.30.085AU_3805.06.02.03
md5: 57a3fcc5f72ec928050dbcb32018215f
From the 1.47.832.1 RUU:
has the same radio as the 1.47.401.4 RUU
From the 1.47.950.3 RUU:
has the same radio as the 1.47.401.4 RUU
From the 1.48.707.1 RUU:
has the same radio as the 1.47.401.4 RUU
From the 2.10.401.4 OTA:
20.48.30.0822U_3822.09.08.20
md5: 053544276893dfcc3a7a722c834b6020
From the 2.10.401.5 RUU:
20.4801.30.0822U_3822.10.08.04
md5: 2fddef29eb1f8001d9cad14f48061f54''
But i dont understand which is a right one for me ??
My personal view: until you have learnt more, don't worry about changing radios. Then, if you are having issues that are radio related, then upgrade.
Or, once you are more familiar with changing your phone, then try different radios.
Fyi, I'm on Radio-20.4801.30.0822U_3822.10.08.04
Sent from my Desire S
BillGoss said:
My personal view: until you have learnt more, don't worry about changing radios. Then, if you are having issues that are radio related, then upgrade.
Or, once you are more familiar with changing your phone, then try different radios.
Fyi, I'm on Radio-20.4801.30.0822U_3822.10.08.04
Sent from my Desire S
Click to expand...
Click to collapse
i already had some strange issues with fallout(slow,buggy,youtube not working) than with icecold sandwich (phone restarting)...so i don't know whats the problem ...so i suppose i should upgrade that Radio or whatever..i just want to start using my phone without having always to think about force closing, freezing, restarting etc...
If you want a phone with no issues - then you shouldn't use ICS ROMs yet, until it's officially released.
I Think you Should try and flash the rom and see how it goes...
because there is a good chance it'll work just fine with your current radio.
If not... there is nothing too difficult in flushing a radio, it's a very simple
process if you already unlocked your phone.
maxlieb said:
I Think you Should try and flash the rom and see how it goes...
because there is a good chance it'll work just fine with your current radio.
If not... there is nothing too difficult in flushing a radio, it's a very simple
process if you already unlocked your phone.
Click to expand...
Click to collapse
so if you can answer to my first post it would be very nice
Read the RADIO sticky thread on the development section
Sywepd form my DsereiS