Develop Bugs

6.24 radio

guys...still having fun trying to unlock my xda...i will get there! been advised to downgrade 6.25.02 radio down to 6.24 radio as XDA UNlock doesnt work on 25...any idea where to download?

Try this:
http://www.lumpistefan.de/tools/RSU_V6.24.20_PPC.zip
But downgrading RSU is very dangerous.....
Stefan

Thanks
Thanks S...it wouldnt let me do it.

http://www.yorch.net/downloads/ROMS/TMOradiostackupgradeR624 .zip

t-mobile RSU 6.25 SIM unlock prolbem, final solution. XDA I
Error getting connection type
Error getting unlocking code
Upgrade RSU (Radio Stack)
RSU 6.25, RSU 6.24
Those are the keywords I have been using for about a day to get to the bottom of unlocking a t-mobile XDA I (siemens SX56).
I have started with being unable to flash the device with Special Edition ROM, then XDAUnlock unable to unlock the device etc..
Thanks to http://lumpistefan.dyndns.org/tools/ , they guy did a great job showing in details how to evenutally unlock this wild device with RSU 6.25. So look no futher, this is the holy grail! :idea:
I'm quoting from Lumpistefan website:
How to unlock your Device ....
The PDA side of the ppcpe and the radio/phone/gsm side are two totally different animals (not a surprise to some). When you refer to the 'operating system' you're talking about the ROM like the XDA Developers special edition or any of the ROMs from the ROM kitchen at http://lumpistefans.dyndns.org/. The Radio or RSU (for Radio Stack UPgrade) is totally separate from this. The other variable is the bootloader version (Wallaby in my case).
Now my goal was just to use the XDAunlock program. When I ran the program right from the defaults I got 'error getting unlock code.' All the posts I read said put on the Special Edition ROM and you'll be fine but that did not do the trick. Still got the same error message.
Here's what I started out with:
ROM: 4.01.16 ENG
Radio: 6.25.02
Wallaby booatloader: 5.22
What finally worked:
Radio: 6.24.00
ROM: 3.17.03 ENG (XDA special edition)
then upgraded back to 4.01.16 ENG
Wallaby boot loader 5.15
How I did it
--------------
I meandered my way through this to eventual success and since the dratted device now works fine I'm leery about putting it all back to the old way and doing it all over again. Therefore use this process as a guide only, not a definitive instruction set. Also I walked through this as a troubleshooting exercise so some steps may not have been necessary. I eventually succeeded but maybe went the long way around to do it.
References
----------
- Bootloader utilities: Get to this by holding down the power button and pressing soft reset. You may have to hit the contacts button to get into the menu if you don't see it right away (like if you see a simple GSM OK message at the bottom of the bootloader display.
- Cold boot: the reset swtich on the right side bottom of the device with a picture of a red battery with an \ through it. This disconnects the batter from the mainboard and trashes all the data on the device except the Operating System in ROM.
What I grabbed
------------------
- XDAtools
- XDArit
- ActiveSync (I used 3.7.1) and connection by USB cable
- Wallaby bootlolader version 5.15 files
- XDA Developers Special Edition ROM
- RSU 6.24.00 files
- XDAUnlock.exe
- SD Card (mine is 128 MB but I think as long as it's bigger than 64MB or your current memory in the device you're OK)
- pnewbootflash_40116.exe
All of these files are available here, just search for them.
First back up everything. Not just using the sda backup tool, from the boot loader. You can do the SD backup if you want, consider it backing up your data. You can also do the ActiveSync backup if you want to save your data.
Second I'm doing ALL of this with no SIM chip in the device. This may or may not be necessary.
Stick your SD card into the PDA. If it complains about wanting to format it go ahead and let it format the card unless you have stuff on it you want. I'd recommend dropping anything you want from the card onto safe media and just working with it as a blank the rest of the way through because it's easier to just wipe the card in between some steps.
Go to the bootloader utilities. Hit Contacts button and you'll get the boot loader option stuff. If the bootloader utilities you get to right away takes you to a menu with things like Boot+CE-->SD then you don't have to worry about hitting the contacts button. You only need Contacts button if when you get to the bootloader screen you see nothing more than some nice colors, the bootloader version and "GSM OK" message.
Take the Boot+CE-->SD option to back everything up. This will take a few minutes.
Once it's done pull the SD out ofthe ppcpe and stick it into your SD card reader. Bring up XDArit and chose your removeable device.
If you have more than one MMC slot select the different ones until you get one that says 'Wallaby' in the hex codes at the bottom of the XDArit screen. You'll be writing out two files, the first is the NB0 file (which is the bootloader) and the second is the NB1 file (which is the OS or ROM). Name these something like original.nb0 and 1.
Wipe the SD card (format FAT). Stick the SD card back into the pda and soft reset, then cradle it.
Go to a DOS prompt and CD to where you put 'pnewbootflash_40116.exe.' Type 'pnewbootflash_40116 nbl515.nb0' to write the Wallaby 5.15 boot loader to the device. If when you downloaded the 5.15 bootloader you called it something else (like 'wallaby_boot_loader_V5.15.nb0' you should of course use that name instead!
The output looks like this:
D:\XDAtools\binaries>pnewbootloader_40116 bl515.nb0
Copying D:\XDAtools\binaries\itsutils.dll to WCE:\windows\itsutils.dll
in FindFlashInfoOffset
protection found at 8c0d60f8
result: 00000000 00000000
Now..why did I downgrade the bootloader? At this stage I'm troubleshooting why I get the 'error getting unlock code' message running XDAunlock. I've got three variables I know of, bootloader, ROM and Radio Stack. I chose to start with the bootloader because some posts out there say boot loaders 5.17 and higher have some checksum that keeps certain ROMS from working properly. Perhaps if I'd started with the radio stack I'd have been done right away and saved a few hours but all the posts about possible device destruction made me start with the bootloader! Again, your results may vary!
Next I changed the ROM to the XDA Developers special edtion.
Make sure the SD card is in the PDA and cradle it. Run OSIMagetool and load the ROM file in the first box, chose SD Card in the second box.
If you downloaded the Special Edition ROM you might have some luck using the Installer that comes with it but apparently that does not work with ActiveSync 3.7.1. I got messages that said it could not access the device or no connection etc. Instead I used OSImageTool to load the NK.NBF file included in the distribution. Note that to get to this file you DO have to unzip the EXE file you download!
Once complete pull the pda out of the cradle.
Hold power+soft reset to get the boot loader menu. This should show up as 5.15 now. It will automatically detect that the SD card contains a ROM that can be flashed to the device. If for some reason it does not automatically detect this maybe you have to hit Contacts. I did not have to do that, it just told me to hit Action to download the ROM.
Hit Action button (aka the jog button) to write it to the device. This will take a few minutes, go grab a beer or two or three. I took the safe route and connected power to the device while writing the flash.
Once it's finished cold boot the device. I waited 2-3 minutes before re-engaging the battery.
Here's a gotcha. On the right side of the SIM there is a little switch. If the rubber door for the SIM is not totally closed you can't get the device to boot. This switch is real small so it's very possible to miss it. You can see it fine if you take the back off the device (which I determined from a post here that told you how to get the battery out).
When it boots you should have the 5.15 Wallaby booting the XDA special edition. Follow the instructions to calibrate the screen and you're ready to move on.
Now if the radio is 6.25.02 XDAunlock won't work, it just generates the 'error getting unlock code' message. You have to downgrade the radio to have this work.
There's lots of posts around here that say don't screw with the radio because if it errors you've got a fried device. I imagine this is true so balance how bad you want to unlock the device against the possibility of totally frying the device. I've done two radio upgrades in my life on the PPCPE, both were OK but again, caution is advised.
Grab the 6.24 radio zip and unzip into a folder on your computer. Use ActiveSync to copy the files to \windows on the device.
Execute the rsupdate.exe program to reprogram the radio to 6.24. WHen completed soft reset the device and go into start-settings-system-device info to make sure you're at 6.24 radio vesion.
Copy the xdaunlock.exe to the device and execute. It should say 'you're device appears to be SIM Locked, would you like to remedy this?" click Yes to unlock the device.
Now the device is unlocked. You can change the ROM to WM2003 now if you want (which I did). I imagine you can re-upgrade your bootloader and radio stack if you want but I'm leaving well enough alone for now!
End
Thanks
DaKanadian

My grey screen says USB v2.07 I think I killed it!

My grey screen says USB v2.07. I tryed to update the radio to 1.13... I copied the EnterBl.exe over to the Siemens SX66 and executed it. It blinked and then turned off. Then it came back on and displays USB when on the cradel and Serial when removed. I cannot get it to do anything now. Does anyone have any advice?
Thanks,
Bobby
Cingular
Siemens SX 66 ( I have no idea how that translates into blue angel)

same here
if some one has a sulotion please send me instruction or a mail [email protected]
thnx

you are stuck in bootloader mode. just run the setup for rom upgrade/restore for your device and it should work. I think a hard reset will also allow it to reboot into normal mode, but not sure.

Defiant XDA
I cannot seem to get it to reset nor be recognized by the computer when it is placed in the cradle. It will chime as it is placed in the cradle, yet the charging light no longer ignites and the hot-sync program on my WinXP pc does not indicate that they are connected any more.
Thank you for your time!
Bobby

restore the original ROM. I had this issue after I run a defrag on my "Storage" folder using Storage Tools. I could not reset it. Also, upgrade with higher ROM did not work.
You have to restore / setup using original ROM version. Good luck!

Follow this link, download the update and follow through the instructions.
http://t-mobile.iris-global.com/download_manager_mda_3.html

original rom
Does any one has the original rom for the ph20b my son messed it up
\if any one can send it via email or a link will be helpfull
thnx

Another Possible Solution...
This has happened to me numerous times when upgrading to various ROM versions and through experimentation I finally realized that it was related to my storage card. I also remember reading another post like this where this problem can occur if the storage card is on the large side (>= 1GB ).
Just take out the card and reconnect to the cradle and you should be able to flash again.
Hope this helps

XDA Orbit won't boot - possible to extract files from it?

I couldn't find an answer for this so I hope someone can help.
My friend's XDA Orbit won't boot.
It goes to the blue O2 screen (first screen when turning on, showing IPL, SPL etc) waits a short while, and then the screen flickers/shimmers - and that's all it does. No more loading.
I guess this is probably the point where the green Windows logo is normally shown (I have several HTCs but not an Orbit so I am guessing).
Now I know I can try a hard reset but there are valuable things on there so I don't want to try that.
Is there a way to get the information from the phone?
Is there a program/s that will allow me to boot from SD card and recover files?
Is there a way to connect using a pc (and sync program) and browse the phone and copy things over to my pc?
I tried starting up in bootloader mode (holding down voice-recorder button while soft resetting) and that worked fine but as I said, I don't want to install any roms and wipe anything that was already on the phone.
The phone is standard (factory rom), no new apps were added and nothing was changed on the phone.
Any ideas please?

try to reinstall os

I have the same problem: http://forum.xda-developers.com/showthread.php?t=599000
Try to flash new ROM, maybe it helps you.

HTC TP2 bricked? Freezes at Start up!

Please help!
My HTC TP2 freezes at start up with the black screen and the Touch Pro2 Logo and some details in red at the bottom:
B 80
R 4.49.25.17
G 61.44tc.25.32U
D 1.86.67102
No USB connection can be established.
What happened:
1. Tried to update from original WM 6.1 to WM 6.5 by using the official HTC ROM update utility. Seems like USB connection broke during update and update freezed at 42%. Update utility process has stopped by itself (no process visible anymore in the Task Manager).
2. Restarted phone and multicolor screen appeared and stayed. After connecting with USB cable again "USB" appeared at the bottom. Started again the HTC ROM update utility which recognized the phone and started the update process again, but stopped at the beginning with an error message stating something like the ROM is broken.
3. Restarted again (by removing the battery and hit power button) and state reached like described above (HTC TP2 freezes at start up with the black screen and the Touch Pro2 Logo and some details in red at the bottom).
4. Performed a hard reset but did not help.
What can I do to bring the phone back to life?

So you can't or can get in the colored screen now? (the boatloader)
And it's kind of normal that their nothing happens after the tp2 + red information screen, this since their is no rom to startup.
EDIT
Is it possible to tell exactly what error you got?
EDIT
Try to hard reset your device, do you know how to do this?
If not this is how to do it:
To perform a hard reset
1. With the device turned off, press and hold the TALK/SEND, END and POWER buttons until you see this message on the screen.
"This operation will delete all your personal data, and reset all settings to manufacturer default. Press VolUp to restore manufacturer default, or press other keys to cancel."
2. Release the TALK/SEND, END and POWER buttons.
3. Press the VOLUME UP button to perform the hard reset, or press any other button to cancel the reset.
Source: http://forum.xda-developers.com/showthread.php?t=523083
This is just what worked for me..
Had the same issue on my tp...
Hope it will work for you.

Did already the hard reset - but this did not help as nothing changed!
One further info: whenever I insert the battery the device automatically starts up - until it freezes again at the start up.
Can someone please help?

It's normal that the device starts up when the battery is plugged in...
But this is just what I know out of my own experience.
So sorry I can't help you farther.
EDIT
Did some research you might want to try to flash your phone by micro sd... (not for sure if it helps but by some people it did work)
Read the tread about flashing at the top of the rhodium section and you know how to do it.

Did another trial: downloaded and copied a RHODIMG.nbh to the micro sd card, inserted it again and pressed volume up at startup -> colored screen appears shortly, then switches to a white screen telling "Loading..." in blue font color, but nothing more.
Is there anybody out there who can help?
Do I need a specific RHODIMG.nbh to make this approach working? I didn't flash this device before, so it has been still in the original manufacturer's state.

frieder01 said:
Did another trial: downloaded and copied a RHODIMG.nbh to the micro sd card, inserted it again and pressed volume up at startup -> colored screen appears shortly, then switches to a white screen telling "Loading..." in blue font color, but nothing more.
Is there anybody out there who can help?
Do I need a specific RHODIMG.nbh to make this approach working? I didn't flash this device before, so it has been still in the original manufacturer's state.
Click to expand...
Click to collapse
suppose 2 press down volume not up after soft reset

This may help,
Try entering bootloader by switching off device then switch back on holding down the Vol down key.
If you can enter bootloader this way then you wil be able to flash from SD card following the instructions from here
http://forum.xda-developers.com/showthread.php?t=550540
if you want to flash the Official update from HTC you can extract the Nbh from the Exe file you downloaded from them, just use winzip, Zzip or Win RAR to extract the contents from the Exe you are looking for RUU_signed.nbh..follow the above thread instructions to change the name of the file to RHODIMG.nbh.
I DONT KNOW IF YOU NEED TO HARD SPL FOR THIS..Probably better to do it than not. Can Anyone Confirm???
i hope this helps

Device is up and running again !
Could enter bootloader mode and tried first to install again via the official HTC installer -> worked!
Thanks a lot for your support!

great news welldone Bro and welcome to the forum!!!

osrix25 said:
This may help,
Try entering bootloader by switching off device then switch back on holding down the Vol down key.
If you can enter bootloader this way then you wil be able to flash from SD card following the instructions from here
http://forum.xda-developers.com/showthread.php?t=550540
if you want to flash the Official update from HTC you can extract the Nbh from the Exe file you downloaded from them, just use winzip, Zzip or Win RAR to extract the contents from the Exe you are looking for RUU_signed.nbh..follow the above thread instructions to change the name of the file to RHODIMG.nbh.
I DONT KNOW IF YOU NEED TO HARD SPL FOR THIS..Probably better to do it than not. Can Anyone Confirm???
i hope this helps
Click to expand...
Click to collapse
For future info, from what I have gathered you must hardSPl for all ROM flashes. If the ROM you flash is the stock ROM, you can also revert your SPL to stock. For any other ROM, you must leave your device hardSPL'd.
Hope I helped.

how were you able to connect the phone with the pc. i seem to have a similar problem but am finding it difficult to connect the phone to the pc. i have activesync installed but cannot connect to the phone

osrix said:
This may help,
Try entering bootloader by switching off device then switch back on holding down the Vol down key.
If you can enter bootloader this way then you wil be able to flash from SD card following the instructions from here
http://forum.xda-developers.com/showthread.php?t=550540
if you want to flash the Official update from HTC you can extract the Nbh from the Exe file you downloaded from them, just use winzip, Zzip or Win RAR to extract the contents from the Exe you are looking for RUU_signed.nbh..follow the above thread instructions to change the name of the file to RHODIMG.nbh.
I DONT KNOW IF YOU NEED TO HARD SPL FOR THIS..Probably better to do it than not. Can Anyone Confirm???
i hope this helps
Click to expand...
Click to collapse
is it possible to connect to active sync in bootloader, cos my phone cannot even boot, it freezes up with a white screen and htc logo.

After entering bootloader you can flash either way,either by ruu package provided by your ROM's maker or running official ruu release or if you have the renamed file on the root of your sd card....I never use sd card flashing and have never had a failed flash...If in bootloader it will not connect with activesync,but device should be recognized by ruu.exe
WC

Help: Kaiser can't flash NBH anymore!

Following the instrcutions tp flash back to WM:rename RUU_Signed.nbh to KAISimg.nbh and place it on your SD card along with KAISDIAG.NBH. Place the SD into your Kaiser and hold the Power button and camera button down, then take your stylus and hit the reset button.", after I pressed the power button again, tri-color screen changed to a whie screen with "Loading..." showing. There was no progress bar below as usual. After about 5 minutes, I reset it, Kaiser runs android system well: I can even install a new anroid system. Just can't flash any NBH file, even Android small NBH file. Tried with a newly formarted fat32 card also. It always stop at "Loading.. " screen.
Anyboby can help me?

alwayssomewhere said:
Following the instrcutions tp flash back to WM:rename RUU_Signed.nbh to KAISimg.nbh and place it on your SD card along with KAISDIAG.NBH. Place the SD into your Kaiser and hold the Power button and camera button down, then take your stylus and hit the reset button.", after I pressed the power button again, tri-color screen changed to a whie screen with "Loading..." showing. There was no progress bar below as usual. After about 5 minutes, I reset it, Kaiser runs android system well: I can even install a new anroid system. Just can't flash any NBH file, even Android small NBH file. Tried with a newly formarted fat32 card also. It always stop at "Loading.. " screen.
Anyboby can help me?
Click to expand...
Click to collapse
1st
I have never used the stylus reset to flash nbh. (good thing too because I broke it long before switching to android)
just holding the camera button while powering on gets me to the tri-color and then a white screen telling to press power button again to flash.
2nd
I have had freeze-ups on that screen while "loading" and it is usually because of a bad/corrupt nbh file or not making sure all caps in file name KAISIMG.NBH
just a thought...

mnjm9b said:
1st
I have never used the stylus reset to flash nbh. (good thing too because I broke it long before switching to android)
just holding the camera button while powering on gets me to the tri-color and then a white screen telling to press power button again to flash.
2nd
I have had freeze-ups on that screen while "loading" and it is usually because of a bad/corrupt nbh file or not making sure all caps in file name KAISIMG.NBH
just a thought...
Click to expand...
Click to collapse
Tried with KAISIMG.NBH, nothing different!
Anyway, Thanks!

Try clearing everything on the sdcard and leaving only the KAISIMG.nbh and remove the diag file too.
You should have one file (KAISIMG.nbh) on your sd.
NOTE: If the phone is off you only need to hold the camera and press the power button. If the phone is on just hold the camera and press the reset button. There's no need to hold the reset AND power button.

Since you can access the bootloader there is another way to flash, by USB.
You will need to do a little preparation.
If using XP disable Activesync by going to connection settings and uncheck 'Allow USB Connection'.
Then make a temporary folder somewhere handy, I usually use c:\flashtmp, but anything is good.
In this folder goes KaiserCustomRUU.exe, and the NBH renamed to RUU_Signed.NBH.
Once you have all this, put kaiser in Bootloader, it should say Serial at the bottom, attach the USB Lead, and wait until it say USB at the bottom, then run KaiserCustomRUU.exe and follow the instructions.
You should be able to flash Radio, splash, or OS with this method.

i usually do it the way zenity describes...its easier for me to keep up with all of my nbh
the few times i did it from SD i DID NOT have kaisdiag.nbh...other threads said it was unnecessary, so maybe its even bad
btw everyone i found that KaiserCustomRUU.exe will take a nbh named anything as long as its the only one in the DIR. found this by forget full accident

One thing zenity forgot to mention was that you need to remove kaisimg.nbh from your sd before putting into bootloader. Or just remove your sd

loserskater said:
One thing zenity forgot to mention was that you need to remove kaisimg.nbh from your sd before putting into bootloader. Or just remove your sd
Click to expand...
Click to collapse
you can techically leave it there. in spl there is the option to not load the .nbh...after selecting that you can plug in USB like normal

Ah yes, I did forget the removal of the SD card, it may not be necessary in this case, but generally it's a better practice, saves confusion.
Didn't know about customRUU accepting any NBH though, always good to learn things
Regarding KAISdiag, I have never used it, so leaving it out is safe, in fact I'd only use it as a last resort for bad flashes or problems that require it.

zenity said:
Since you can access the bootloader there is another way to flash, by USB.
You will need to do a little preparation.
If using XP disable Activesync by going to connection settings and uncheck 'Allow USB Connection'.
Then make a temporary folder somewhere handy, I usually use c:\flashtmp, but anything is good.
In this folder goes KaiserCustomRUU.exe, and the NBH renamed to RUU_Signed.NBH.
Once you have all this, put kaiser in Bootloader, it should say Serial at the bottom, attach the USB Lead, and wait until it say USB at the bottom, then run KaiserCustomRUU.exe and follow the instructions.
You should be able to flash Radio, splash, or OS with this method.
Click to expand...
Click to collapse
Tried as your instruction with SD card and SIM card removed, when going to step to run KaiserCusomruu.exe, there is always a "communication error showed on PC screen, and recovery didn't make any difference.
I noticed that my SPL is SPL-3.34.0000, instead of SPL-3.34.0000. May it is beacause I flashed stock rom befored. How can I flash Hardspl in android system. I don't know how to copy jumpspl.exe to kaiser in android system.

You should be able to flash a stock winmo rom using the above method, since stock does not need HardSPL.
Sent from my HTC Kaiser using Tapatalk

zenity said:
You should be able to flash a stock winmo rom using the above method, since stock does not need HardSPL.
Sent from my HTC Kaiser using Tapatalk
Click to expand...
Click to collapse
Thank you for your help!
I downloaded the stock rom for my kaiser, and finally I flash back to WM following your instruction. Before, I tried a wrong stock rom.
By the way, the battery problem has been solved for Android system? I have 2 pcs of battery.