I upgraded...so I thought to this version...
Rom Version 4.01.16 eng
Rom Date 02/04/01
Radio Version 4.21.00
Protocol version 32s54 now I cant get into bootloader, cant use the phone, or internet on my SX-56...nor can I boot by flashing....What Have I done wrong should I just use it as a paper weight? Remeber If I press the power button and soft reset to just goes back to the Tmobile screen an continue to boot as a normal Alt-Ctrl-delete. I have tried xdairt and himayla..cant get it to work...
someone plz guide me through this I want my pda!!!!
Try the option fix-bootloader from the XDATools.
Then you should be able to enter the bootloader, and reflash your device...
HTH
Stefan
after XDA1 ugrade to 4.01.16 not able to do up/downgrade !
Have upgraded my XDA1 to ROM-version 4.01.16 Eng.
Now I wanted to install a different version, but I failed.
The PDA is working so far, but I can't upgrade/downgrade anymore.
When I use OSImageTool, there is a connection error displayed in the black command window:
ERROR: GetConnectionType - An existing connection was forcibly closed by the remote host. error getting connection type.
Can somebody please help me ?
Re: after XDA1 ugrade to 4.01.16 not able to do up/downgrade
Stefan_PDA said:
Have upgraded my XDA1 to ROM-version 4.01.16 Eng.
Now I wanted to install a different version, but I failed.
The PDA is working so far, but I can't upgrade/downgrade anymore.
When I use OSImageTool, there is a connection error displayed in the black command window:
ERROR: GetConnectionType - An existing connection was forcibly closed by the remote host. error getting connection type.
Can somebody please help me ?
Click to expand...
Click to collapse
There are many postings concerning this problem.....
You have to flash via SD-Card....
HTH
Stefan
Cant get into bootloader via pressing pwr botton and soft reset. I've have also hard reset the device and i still get nothing
Have you tried the fix-bootloader option from the xda-Tools?
Stefan
yes...but all i get is tthe command prompt...and i click yes is there something else i must do...tried edit2003 but still nothing
Cannot execute
Cannot execute "C:\DOCUME~1\Ovynten\LOCALS~1\Temp\Rar$EX00.203\RSUpgrade.exe"
wHAT THE [email protected]#$ DOES THIS MEANS? If uI could only understand this maybe I could get mt PDA working again.
Hiya, :roll: :roll:
I start off by sincerely apologising; this is another one of those already posted items but I just can't seem to resolve this problem.
I have read through many of the already existing posts within this forum and tried the remedies suggested, but still I am having no success with my below problem. Does anyone out there have a bedtime solution for my re-ocurring nightmare.
These are my Hardware specifications:
PC: Running Wins 2000 Pro
Device: PW10B1
Pocket PC: WM2003
ROM: 4.01.16ENG
ROM DATE: 02/04/04
Radio Version: 6.25.02
I have just recently purchased a (Wallaby) T-Mobile Pocket PC Phone Edition from the USA for usage in the UK. I understand from reviewing this website that the model I have is GSM900/1900. I currently use a T-Mobile SIM here in the UK but I have since learnt that T-Mobile runs on GSM1800, therefore I have two options:
1.) Try and change the Band to 1800 in order to use the current T-Mobile SIM or
2.) Unlock this device in order to use an O2 SIM which runs on GSM900.
I have already obtained a NEW O2 SIM but when I put it in the device it says SIM Lock; Please input unlock code: SID:.
I have contacted T-Mobile first in order to see whether I can simply receive the unlock code; but unfortunately these Fat Cat; Blue Chip Companies do well on the Stock Market but don't do as well when it comes to resolving the little man's difficulties, such as this one.
Hence therefore; I have tried to follow the guide within: http://wiki.xda-developers.com/index.php?pagename=UnlockWiz
But had no success, I then tried http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_Unlock2
Again to no sucsess; simply because I could not access DOS within my Wins 2000 Pro.
I do not know where to start and how to go about resolving this; I have already downloaded the following onto my Desktop on my PC:
ActiveSYNC version 4.71.1015.0
Bandswitch WCE version 1.0.0.1
XDAtools
XDA-developers-SER-v12
RSU_V6.24.20_PPC
XDAunlock version 1.0.0.1
If anyone out there can SEE what it is that I am doing wrong or it is blatantly obvious to what I should be doing, I would be most highly grateful for any suggestions and or remedies either; for fixing the unlocking issue or fixing the GSM band issue.
Thanking you kindly in advance.
bigFOOT_3000
Further update
Further update to my above problem :shock:
I can confirm that the device has 'Wallaby Bootloader 5.15' installed, so therefore I tried to carry on from the explanations found on http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_Unlock2
I have since connected my device via the USB cradle and then tried to install the XDA Special Edition ROM v1.2 but everytime I try to execute within the C:\WINDOWS\System32\cmd.exe box, it has this error message:
"ERROR: GetConnetctionType-Unspecifiederror"
"error getting connectiontype"
then the 'Programme A v1.09' appears, it takes me through from Step 1 to Step 2 but then when I click next this message appears:
"Error011: EXECUTE REMOTE COMMUNICATION PROGRAMME cannot execute the remote communication program make sure the USB is connected"
The USB is connected at it is Synchronizing my device without any problems.
Can anyone help me from this stage please.
Thank you.
bigFOOT_3000
You have to downgrade your ROM via SD-Card....
Extract the XDA-Developers ROM EXE file with winzip or something similiar. Than you get a file NK.nbf (about 32 MB) This is the ROM
Than follow this:
http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_FlashSD
Stefan
Broken Radio ROM blocks official O2 rom, MaUpgradeUt_noID.exe fails "error 114"....
Hello
I hope someone here is able to help me.
I have spent the whole of the last 48 hours (no sleep) trying to fix my O2 XDA Exec. I *believe* that I have tried everything suggested on this forum and on Buzz's site but there is just so much on here now that I may well have missed something.
History:
Over the last few months, my phone has gradually got more inconsistent - dropping calls, refusing to answer calls, losing signal and so on. On Jan 1st, I turned it on and it had lost all my settings - Opera reg code, Wifi encryption, O2 net settings, etc.
I spent the last week with sometimes having network, sometimes not. Finally it just gave up altogether. In Settings>System>Device Info, "Radio Version", "Protocol version" and "IMEI" are all completely blank. When booting, the red text states "No GSM".
Reading around this site it appeared that I should be able to reinstall the radio ROM from the official O2 download however this errored with the Incorrect Country Code error. I have carried out full hard resets and still cannot get any Radio ROM visible. I assume that the lack of IMEI is affecting the official O2 downloads?
Since then, I have tried most variations on this site of ROM installs using MaUpgradeUt_noID.exe suggested in the wiki (with and without entering mtty code: "set 14 0").
Full three-part ROM and radio-only ROM install attempts all fail with the Error 114 "Radio Rom Update Error" (the radio ROM is always attempted first).
The only success I have seen was an update of Bootloader from 1.00 to 1.01 which worked completely perfectly and proved that the PC can indeed connect to the XDA when it feels like it.
After two days of earning no money ( I am self-employed) and no money to spend on support, I wonder if anybody has another suggestion for me?
In case it helps: ROM version: 1.30.107 WWE, ROM date: 04/11/06, ExtROM version: 1.30.162 WWE
All advice welcome
Thanks
Leapy
extract everything from the exe and do an upgrade without the radio.nbf
did you read what he said? its the radio that's bad and needs replacing
i don't know, sorry
poussin69 said:
extract everything from the exe and do an upgrade without the radio.nbf
Click to expand...
Click to collapse
I am now totally confused.
I know there was a smiley at the end of your comment, I just can't work out if you are being funny or astute (or both?). Can you explain how reinstalling the non-radio ROMs will help? Would that restore the IMEI?
TIA
Leapy
Midget_1990 said:
i don't know, sorry
Click to expand...
Click to collapse
Thanks for responding anyway. At least I am not crying alone in the wilderness.
It would be terrific to find a fix, though.
Try to flash the radio from Buzz's unlocker with MaUpgrade_NoID.exe
http://www.buzzdev.net/index.php?option=com_content&task=view&id=78&Itemid=1
pof said:
Try to flash the radio from Buzz's unlocker with MaUpgrade_NoID.exe
Click to expand...
Click to collapse
Thank you for the suggestion, I just tried as you proposed. "Error 114 - Radio ROM Update Error" *sob*!
It's a real shame. It's actually the ideal phone for my needs.
Leapy
1. Disable Activesync (connection settings -> uncheck "allow USB connections").
2. Put universal in bootloader mode
3. Connect device to computer using USB cable.
4. Start HHD Usb monitor (trial version is OK).
5. File -> New session -> USB Monitor -> Select USB device where your phone is connected -> Check "request view" -> Finish
6. In the upper part there are two tabs: basic and complete. Click on "Complete".
7. Click on MaUpgrade_NoID.exe and start the radio flashing process, if everything went fine you should see all the USB traffic output on USB monitor window.
8. When radio upgrade fails, click on Edit -> Export and Save as type "ANSI Text files".
9. Save the text file and zip it.
10. Attach the output here or upload it to ftp if it's too big.
Only with this we can see exactly why it fails
Good luck!
http://forum.xda-developers.com/showthread.php?p=994444#post994444
first as recomended i disabled usb from activesync
then downloaded mtty 1.42
connected the usb and started mtty
chose usb
white screen.....
typed set 14 0...
some gibrish on the screen....
ran the rom update....but it informed me that the rom is not for my device...
typed task 0 in mtty (not sure bout the command but its on page 2 of the forum)
ran the update....nothing same error....
now i saw that my universals screen was blank....
removed the battery....and then restarted my universal....
this might help you...
rtask 0/1/3/4
pof said:
1. Disable Activesync (connection settings -> uncheck "allow USB connections").
2. Put universal in bootloader mode
3. Connect device to computer using USB cable.
4. Start HHD Usb monitor (trial version is OK).
5. File -> New session -> USB Monitor -> Select USB device where your phone is connected -> Check "request view" -> Finish
6. In the upper part there are two tabs: basic and complete. Click on "Complete".
7. Click on MaUpgrade_NoID.exe and start the radio flashing process, if everything went fine you should see all the USB traffic output on USB monitor window.
8. When radio upgrade fails, click on Edit -> Export and Save as type "ANSI Text files".
9. Save the text file and zip it.
10. Attach the output here or upload it to ftp if it's too big.
Only with this we can see exactly why it fails
Good luck!
Click to expand...
Click to collapse
Thank you. I think I did everything exactly as you instructed.
Please find attached the zipped log file.
I would welcome your advice.
Leapy
Radio is corrupted, and device cannot check SecLevel (wait interpreter timeout), it returns default seclevel=FF (unprivileged) and correct CID (O2___001), however when switching to radio bootloader to upgrade the radio, device doesn't answer to any 'rerase' command, that's why the utility gives out flashing after receiving no response to 3 "rerase 0 10000" commands.
Probably this is a bit "crazy", but if it is your last chance... try the following commands in mtty, and try to upgrade the radio again after this:
Code:
USB> password 0000000000000000
USB> set 1e 1
USB> erase a0040000 c80000
USB> erase a0cc0000 c80000
USB> erase a1940000 640000
USB> set 1e 0
Don't do it if you can fix your device by any other means (warranty, service centre, etc...) because I'm not sure if it will work or not
Error 114: Radio Rom Update Error
WOW I have the same problem.....
but this commands for mtty...did nothing to my problem.
ERROR 114: RADIO ROM UPDATE ERROR
I don't know if that helps you....on my PDA it says Upgrade Radio Stack Please Wait...
I have the perfect phone....but it is not a phone anymore...and I go crazy.
Is there any way to update the radio rom from SD card??
Please Help
posted reply to incorrect post - cannot delete post - ignore. Please see next post.
pof said:
Radio is corrupted, and device cannot check SecLevel (wait interpreter timeout), it returns default seclevel=FF (unprivileged) and correct CID (O2___001), however when switching to radio bootloader to upgrade the radio, device doesn't answer to any 'rerase' command, that's why the utility gives out flashing after receiving no response to 3 "rerase 0 10000" commands.
Probably this is a bit "crazy", but if it is your last chance... try the following commands in mtty, and try to upgrade the radio again after this:
Code:
USB> password 0000000000000000
USB> set 1e 1
USB> erase a0040000 c80000
USB> erase a0cc0000 c80000
USB> erase a1940000 640000
USB> set 1e 0
Don't do it if you can fix your device by any other means (warranty, service centre, etc...) because I'm not sure if it will work or not
Click to expand...
Click to collapse
Well, I too am a little "crazy" so I did as you suggest.
I tried to put Buzz's "unlock" radio v 0.0.0.0 ROM on using MaUpgradeUt_noID.exe. And guess what, it fails again but with a different error!
Error 150: ROM UPGRADE UTILITY ERROR. "This rom upgrade utility is not designed for your device. Please get proper ROM Upgrade Utility and try again!"
I attach the USB Monitor log if it proves any use?
I will try and use the official O2 ROMs and see how that goes.
Thanks again for your assistance, I truly appreciate it.
Leapy
To Leapy...
How did this problem started to you??
I have been using this phone for 1 week, after that I changed my SIM card with another one called MAGIC-SIM card, (programmable) with 8 SIM numbers.
After that day ALL the **** started!!!!!
I had problems during my dialing the number on phonepad...
when I was trying to make a call... it hang up.
After some soft reset...it didn't ask me for PIN.
After a hard reset.... on boot screen it said NO GSM
and then on antenna icon on the top of the screen the antenna had a little x on the right side.
Then the known problem ERROR 114: RADIO ROM UPDATE ERROR
I can update any rom I want but not the Radio ROM
leapy said:
I will try and use the official O2 ROMs and see how that goes.
Click to expand...
Click to collapse
well, I tried the O2 update and just got the generic "CID" error - twice. So I guess I am no nearer fixing this issue...
All advice welcome.
Leapy
leapy said:
Well, I too am a little "crazy" so I did as you suggest.
[...]
I attach the USB Monitor log if it proves any use?
Click to expand...
Click to collapse
Sorry but the capture was from the erase commands... not from the failed radio flash... please try to flash 0.0.0.0 radio again and attach the right capture... also make sure activesync is not running when starting the radio upgrade, and if it fails once, run MaUpgradeUtility twice without disconnecting the device from USB.
my friend got the exact same problem with his EXEC, and send it back to O2, they charge him apprx USD500 for mainboard replacement.....(fiuhh.....)
pof said:
Sorry but the capture was from the erase commands... not from the failed radio flash... please try to flash 0.0.0.0 radio again and attach the right capture... also make sure activesync is not running when starting the radio upgrade, and if it fails once, run MaUpgradeUtility twice without disconnecting the device from USB.
Click to expand...
Click to collapse
Thanks for your continued assistance.
I tried twice with the 0.0.0.0 radio ROM and this time the error has reverted to Error 114 again. With both these attempts, I noticed that the displayed "currently installed" ROM versions were blank - previously I saw the actual on-board version numbers. Not sure if that indicates anything?
Capture logs attached:
leapy said:
Not sure if that indicates anything?
Click to expand...
Click to collapse
That indicates you previously had activesync enabled and now don't.
Exactly same error as before, radio bootloader is not responding when the RUU sends 'rinfo' and 'rerase' commands to it, then the RUU gives up trying.
You can backup the radio ROM from another device with "d2s 60000000 00800000", and theoretically you should be able to load it into yours by using "L" command... but I'm not experienced with universal bootloader and can't say for sure if this will work and the right commands to do it... so please wait until someone reads this and can help you more than me, or research by yourself if you have the time to do it
I am trying to upgrade my Tytn to WM6. I have installed the latest version of SPL (using MrVanX's upgrade guide). When I try and install the laterst Radio version, I get the following error message "Error, unknown version! You should pick SSPL". I am connected via ActiveSync, and the connection is good, so I don't understand why I am getting this error. Can someone please let me know if they understand this. Thanks
it means you should pick 'FORCE USING SSPL' in the rom update utility .. sheesh
the new RUU wrapper should have an option to pick the new spl7 so just select that one this is not rocket science stuff people
Hey y'all,
Thanks for taking out the time to help me
So, thanks to a friend, I got a beta release of WM flashed on my Hermes a few months ago. I didn't realize that it was a time-limited beta, and I can't use my device anymore.
Current Status --
1. ActiveSync can't connect to the device, so can't use RUU directly.
2. Similarly, I can't use the CID unlock utility, because it requires an AS connection
3. I can access the BL and connect to it from mtty. I see the USB> prompt.
4. Dump of the BL tri-color screen --
HERM200
IPL-1.00
SPL-1.10
5. Dump of "task 32" command in mtty
Level = FF (i.e. CID locked)
Hence, I can't flash BL 1.01 MPG and install an OS. (nor can I install CID unlocker, see #2 above)
6. Dump of "info 7" command in mtty
HTC Integrated Re-Flash Utility, Common Base Version : 1.50a S024
Device Name: H, Bootloader Version : 1.10
.....
Question --
I want to get a working OS on the device. (With that, AS should connect and I will be able to CID unlock the device.) Any ideas?