Help Unlocking A SX56 from AT&T - MDA, XDA, 1010 Software Upgrading

I have a SX56
ROM Ver: A.20.17ENG
ROM Date: 5/15/03
radio Ver A.20.10
Protocol ver: 324e4
& one thats
ROM: 3.14.03 ENG
Radio: 6.12
How would I go about unlocking them. I could ot usse that program. I got error mess error getting unlockcode. Is there any other way to unlock them.

Try to upgrade the ROM to 3.17 from this site and it will unlock your device with the first boot
www.xda-developers.com/SER/
Good luck ...

I'm sure this is a dum ? but do see a link to download the update. I saw the part that talked about having a box and dont have all of that. Could someone hook me up with the update.

Joker said:
I'm sure this is a dum ?
Click to expand...
Click to collapse
Actually, there's enough smoke and mirrors involved in all of this that you'll quickly learn there are no dumb questions.
First, go to a site that is running a "ROM kitchen" and cook up a ROM, such as:
http://kitchen.romanweb.com/kitchen/index.php
Create a 3.17.03 ROM with no config data and uncheck all of the optional software, so you have an absolutely bare-bones 3.17.03 OM with no frills.
Second, Find some way to back up your existing ROM, either onto an SD card or onto your computer.
Third, install the 3.17 ROM on your XDA. Many here prefer the SD card method of loading; I took my chances just using the .exe with the device in the USB cradle with no problems. Once loaded, when you boot up, it will say "Your Device's SIM appears to be locked, would you like to unlock it?" You simply select "yes" and that's that... I literally had the 3.17 ROM on my device for all of one boot and no more than 20 seconds. Then load your existing ROM or a newly "cooked" feature-laden ROM from one of the kitchens back on to your device and you're back in "bidness."
I too made the journey from ATTWS to T-Mo and with a little luck, and a little help from people here, it went very smoothly.
Everyone here has a different level of experience, both on matters technical and matters XDA, so don't be afraid to ask any questions you might have so you have a clear picture of the whole process before you start.
-Max

Thanks for all of your help guys. Got it too work

Kitchen ROM Errors
Hello all,
I have been reading all day on the forum, as am an SX56 owner (former AT&T) now with T-Mobile and want to get it working and unlocked on their network.
I cooked up the 3.17 ROM as an executable, and downloaded the rom.exe file.
Each time I run it, it starts up the DOS window, then the Uploader Software, then gives me an Error 007 Dialog window, Cannot find the ROM image to upgrade your Pocket PC. Please download and try again.
I have tried this three times now, but cannot get to the 3.17 so I can unlock, and get to WM2003 and the new radio stack for T-Mobile.
HELP!!!! Thanks

Hello ..
It seems you do need to try the SD card method. Either to get SD card and reader/writer and cook your new ROM as .nb1 file, or to get a SD backup for the ROM from any other t-mobile device.

Mad Max,
1st, how do you back up your current ROM? Please provide step by step procedure.
2nd, How do you load your original ROM back in? When you load back your original ROM, does the phone get locked again?
3rd, it looks like you've done what I want to do, can you please provide a step by step on how you installed the 3.17 ROM on the XDA using the USB cradle?
Thanks in advance.

Related

WANTED: AT&T SX56 virgin ROM file

Can somebody please help me.
As I posted in this post, I scr3wed up my buddy's AT&T SX56.
I have got the thing past being dead, by putting a custom ROM on it.
However, I really need to get this thing back into AT&T mode, with either 2002 or 2003 on it. I will then upgrade to 2003.
Does anyone know where I can get a virgin AT&T ROM so that I can re-flash his system.
Thanks.
-=Nick=-
nickpoore said:
Can somebody please help me.
As I posted in this post, I scr3wed up my buddy's AT&T SX56.
I have got the thing past being dead, by putting a custom ROM on it.
However, I really need to get this thing back into AT&T mode, with either 2002 or 2003 on it. I will then upgrade to 2003.
Does anyone know where I can get a virgin AT&T ROM so that I can re-flash his system.
Thanks.
-=Nick=-
Click to expand...
Click to collapse
Check out Yorch.net
Okay, I'm making SOME progress.
Firstly thanks for the youch referral from kwlandry.
I had found the rom kitchens this afternoon while looking for solutions...
I'm busy flashing the ROM from SD for the umpteenth time.
It seems that whenever I flash the SX56 with an AT&T 30.09 ROM, then I get a hang on reboot.
I am currently trying the 4.00.05 ENG ppc2003 from yourch as it seemed to be non-specific (and a non-TMobile) one.
I seem to have the latest Radio stack (RA.33.02), and have been able to get a couple of ROM's to work.
Does anyone have ANY idea why the AT&T 30.09 ROM would fail in the same place every time? This is definately an AT&T unit, at is has the logo on the front. The phone was originally locked, but has been unlocked during the process.
I'm busy reading/searching the forum, but haven't seem to find this problem anywhere.
Thanks for ANY help.
-=Nick=-
I fixed many XDAs with your problem!
you could send the XDA to Siemens to repair/exchange.
Try flashing back to the original ROM via sd method then upgrading to wm2003.
You can get a copy of the 2002PPC ROM at siemens website. Cut & Paste the following link.
http://www.my-siemens.com/MySiemens...%2FMC%2FMC%2FSX56POCKETPCPHONE%2Fdesc,00.html
Extract the file to a directory, then use the XDA OSimage tool to write to SD card then use bootloader to write to ROM.
After a successful flash follow the same to upgrade to wm2003
You can also try this kitchen http://lumpistefan.dyndns.org/
BTW - the phone has to be fully charged. That might be the cause of your hanging issue.
I have posted this in answer to your other post, try using a diferent memory card for upgrade to wm2003, I had this problem when using an mmc memory card to upgrade to WM2003, it hung every time even though it seemed to complete correctly, I changed to a different memory card and had instant success.
Yes! I agree also. But, though "mmc" and "sd" cards are similar, in this case the process calls for an sd card. The size doesn't seem to matter, I use a 512mb, however some people have had issues with device detection. So, a 64mb card is recommended. Make sure it is formated before use. And again a fully charged phone is unlikely to have problems so save your battery till all requirements are in place. Also DO NOT DO A HARD RESET! untill you have a successful install. You could lose you GSM ROM.
Thanks for all the replies.
I have successfully flashed back to the original rom; I downloaded it from yorc.
Having got the device back up and running, I tried the upgrade to 2003 again; using the Siemens software in the cradle solution. Didn't work.
The battery was definately fully charged (90% or higher) at all times.
I will look to try another SD card, and see if that makes a difference, it just seems strange that the card works to restore WM2002, and either card or USB approaches to upgrading to WM2003 fail.
The card I've been using is a very generic 128MB MMC card.
Again, thanks to everyone for their suggestions.

Have SX56 - upgrade to 2003 - now fried

Newbie here...
Got a SX56 (used) and it was working fine. Saw that there was an upgrade to 2003 and like the moron I am, I jumped in with both feet. Now the device will only go to the initial screen where it shows the rom/radio versions.
I downloaded the tool, and tried to restore from SD but it still doesn't work.
My bootloader is v5.15 it seems.
At this point, I just want the thing to work again in 2002 or 2003. If someone has some ideas or a ROM image to go back, please let me know
dbrady
Maybe you´ve got the same problem than an other guy here in this forum. He have big problems to install WM2003 on his device.
Since you´re getting message of ROM AND Radio version it looks quite good.
I would suggest that you get a new ROM maybe from my kitchen (http://lumpistefan.dyndns.org and install it on your device using an SD-Card and the XDATools.....
HTH
Stefan
Thanks. I tried earlier but I wasn't sure what one to choose. I have an English Version SX56 that was sold through AT&T. It shows Wallaby Bootloader 5.15 now. It shows the correct rom/radio info for Win2003 but won't boot.
What version should I try? I'd like to get 2003 if I can, but would be willing to go back to 2002 to get a function phone again.
Thanks for all the help
P.S. - I was using Mozilla and it never actually downloaded anything when I tried.
Dean
Downloaded a new ROM - thanks - but same problem. Now the unit shows new ROM version but still never goes any further than the boot screen.
Any other ideas?
Steps please...
How did you load your new rom? Please post the steps so that we can try and figure out what went wrong.

Cannot upgrade to Windows Mobile 2003 on SX56

Okay, I've had it. I've spent all weekend trying multiple configurations to get my system upgraded. I was originally running bootloader 5.22 and went to Lumpistefans' kitchen and cooked multiple ROMs but none of them brought up a working system. I first cooked the Siemens A.30.09 but that didn't work, then I tried the 4.01.16 ENG T-mobile (since that the service provider I'm using) but that didn't work also. I went back to my orignal and it's working fine, no problems.
I then thought that maybe it was my bootloader, so I downgraded to 5.15 and then tried flashing the same ROMs again, but still they didn't work! I even tried the 4.01.12 EURO 02, but that didn't work either.
After I flash to a new ROM I get the ROM's boot screen (not the one with the different band colors, but the actual ROM screen image just as if it were going to boot fine, then in the lower right hand corner all the version stuff pops up, but then that's it. NOTHING HAPPENS! It just sits there fore EVAR!!!
I'm about to go bald by ripping my hair out if I can't figure it out.
BTW, I was sure to make a backup of the bootloader 5.22 just in case.
My XDA info:
Model: PW10B1
ROM: 3.17.03
Date: 05/15/03
Radio stack version: A.20.10
Protocol version: 324e4
Lower right-hand corner:
G324e4
RA.20.10
3.17.03
Does anybody have a ROM, or tell me what ROM, to use so I get get the latest WM and "get with it"?
THANK YOU!
P.S. Someone please remove the thread started as GUEST, I forgot to login.
ARe you using memory card for upgrade? I had this problem using mmc memory card but when I used a different memory card everything worked fine for sd flashing.
Yes, I've been using the same memory flash sd card for backing up and upgrading. I've used the same card to back up my ROM and then restore my original ROM in working condition. So, I don't think it's the card, but I'll try another card just in case.
Does anyone have another suggestion?

Problem unlocking Wallaby-Error message inside

1st off, let me say how great I think this forum is. I apologize in advance if this topic has been covered, but I've searched here and can't find it.
I was given a T-Mobile PW10B1 with the following device info...
ROM 4.01.16 ENG
ROM date 02/04/04
Radio 6.25.02
Protocol 324e4
I need to unlock it to work with Cingular. It currently has no SIM or SD card in it, although I've ordered a SIM card that I should have by Friday.
When I put XDAULOCK.exe on it to run, I get the "error getting unlock code" message. When I try to flash the ROM using XDA-DEVELOPERS-SER-V12.exe, here's what I get in a DOS window..."ErrorGetConnectionType An existing connection was forcibly closed by the remote host. Error getting connection type".
The pda WILL sync up, but can't copy these files over.
Is this enough info for anyone to offer suggestions? Any ideas? Thanks in advance.
D
kdn82 said:
ROM 4.01.16 ENG
Click to expand...
Click to collapse
This ROM only allows downgrading to another ROM via SD-Card.....
Instructions for this you can get here:
http://lumpistefan.dyndns.org/tools/sd_flash.htm
kdn82 said:
Radio 6.25.02
Click to expand...
Click to collapse
This may be your next problem. This Radio Version do not work with the xdaunlock tool. You have to downgrade Radio Stack first Instructions can be found here:
http://lumpistefan.dyndns.org/tools/manual2_unlock.htm
Have you already checked if the device is really locked?
I would suggest that you wait for your sim-card and try it, before you reflash your device....
HTH
Stefan
Thanks
LS,
Great info-thanks! I'm not sure if it's truly locked or not. How can I tell for sure? Right now, I'm on an OLD TDMA phone/plan, so when I'm SURE I have it unlocked, I'm upgrading my plan to a GSM plan. So the danger there is, if I have to have Cingular try to activate my new pda/phone, I'll have to change plans first, and if it's not unlocked, I can't use my old TDMA phone!
I think I'll get as SD card and try the 1st suggestion, and try to leave the radio alone for now-what do you think?
D
You can borrow a SIM-Card of a friend of your. The process just took a few miuntes. Insert the SIM in the Wallaby, start the device, enter SIM Code and watch the display. If you get connected to the network all is fine. Otherwise, when you have to insert a SID-Code, the phone is locked.
For unlocking you have to follow the process described in the second link. First link is just for changing the ROM....
Stefan

Please help upgrade Prophet/ overcome CID (VendorID) error

First of all THANK YOU all of the Great Minds of XDA Developers for all the support and great work you do for us!
a lot of your work, support and software and advice has been priceless help!
Any way no ass kissing here, just wanted to say thank you. ...and ask for help. As you probably know, there has been a lot of problems and issues with Prophet. (and very little or NO support and from manufacture and from providers. and there is not much available from xda developers forum users on this device. Though there has been great amount of support on any other devices. which has made me a happy user of Magician. But to cut it short, PLEASE HELPPPPPPP with Prophet!!! I can't reflash my XDA Neo with new WWE rom due to CID (vendor ID) error! It comes with german rom and I don't read german but love the phone! (and stuck with 2 year contract!) I tried aWisard utility numerus times in hopes that it would work despite the design for different device. I tried all kinds of roms available out there with no luck. and ofcourse HTC or O2 wouldn't help in any way! (different O2 support
techs said to me that I couldn't flash my Magician with WWE rom becouse it would kill the device! And I had it flashed in all the possible languages!) Any way, my magician is now a history (sold) and my new prophet is great pain in a ass!
Do you guys think you could help all of the xda community (and unlucky suckers) out here and help us overcome CID error so we can update/change our roms? (and screw the HTC, Qtek, Imate and O2 for such a poor support!)
I would greatly appreciate it! and it goes from all of us!
hi aleksandr
Just go the link below and follow the instruction to unlock the CID.
I just upgraded my 818 Pro to JAMin ROM, run very smoothly.
http://forum.xda-developers.com/viewtopic.php?t=37386
Hi, thank you very much for the reply! I did try this option but I have a little problem with Wisard program. I ran all the commands, enabled rapi,backed up my rom, ran unlock CID command, it returned "success" line, but when I try option -w- to write new rom into my prophet and get to "select OS rom file" where it saids to enter numbers only I don't know what to enter in the command line since the program doesn't have any roms listed in the command line screen. I've tried entering the rom release number, I even tried renaming rom to a number and I have placed the rom nk.nbf file in all the possible folders including "rom" in the program directory. but stil, once I hit enter, the command line window shuts down. could you advise?
and I did put the aWizard folder and rom file in the root directory on c:... tried d: too... stil, no result
Hi Alek,
Try this....
You now have a device that is CID unlocked, exit aWizard and locate the downloaded RUU update you now wish to load to your device. You should not need to use aWizard to do the flashing, just use the aWizard program to unlock the CID from the device.
I too have a Dopod 818Pro and I successfully flashed it to the new I-Mate JAMin ROM. All I used aWizard for was to unlock the CID on the Dopod 818Pro then exited aWizard and just used the downloaded RUU update.
Regards,
voyager
Thanks voyager, I guess you're very fast typist :lol:
Hi aleksandr,
Did you did an ActiveSync with your Prophet first then run the aWizard? For me I just run aWizard to enable RAPI and unlock the CID on my 818 Pro. Then I just double click on the latest JAMin ROM exe file, it detect my 818 Pro without any problem.
ualvoyager said:
Hi Alek,
Try this....
You now have a device that is CID unlocked, exit aWizard and locate the downloaded RUU update you now wish to load to your device. You should not need to use aWizard to do the flashing, just use the aWizard program to unlock the CID from the device.
I too have a Dopod 818Pro and I successfully flashed it to the new I-Mate JAMin ROM. All I used aWizard for was to unlock the CID on the Dopod 818Pro then exited aWizard and just used the downloaded RUU update.
Regards,
voyager
Click to expand...
Click to collapse
First of all thank you guys for getting involved and helping! I really appreciate it!
well, I tried just to CID unlock it with aWisard, got "successful" message and then I ran about 10 different upgrades from different providers, qtek, Imate, etc, and still got the wrong vender message!
hey mamakap,
you're right on the fast typing, my fingers are still burning...hee hee
voyager
mamakap said:
Thanks voyager, I guess you're very fast typist :lol:
Hi aleksandr,
Did you did an ActiveSync with your Prophet first then run the aWizard? For me I just run aWizard to enable RAPI and unlock the CID on my 818 Pro. Then I just double click on the latest JAMin ROM exe file, it detect my 818 Pro without any problem.
Click to expand...
Click to collapse
I usualy ran after sync, since the aWisard said it has to be fully ran. I will try it now!
Thank you! hopefully with all of your support I'll get the nedded results! Thanx!!
ok, just tried enable rapi with active sync off, the aWisard reopened and reastablished connection, but it still not finding the rom file.
wait a minute, does the rom file has to be in .nbf format or .nba?!
I'm looking right now for Extend Tool (64HTC Extended ROM Tool) and will convert the rom rom to nba file and see what happends.
man, I wonder how it worked for you just running unlock CID command and upgrading with the upgrade file!
Alek,
You already unlocked the CID from your device did you not? Your first post said you got a success message.
Put your device on the cradle or plug in the usb cable. Let ActiveSync do its thing then after the sync just double click on the RUU update you want to install. Follow the install wizard (NOT aWIZARD) of the RUU update. You do not need aWizard any longer to update the ROM, just use the RUU update you downloaded.
post if you need further help.
voyager
ualvoyager said:
Alek,
You already unlocked the CID from your device did you not? Your first post said you got a success message.
Put your device on the cradle or plug in the usb cable. Let ActiveSync do its thing then after the sync just double click on the RUU update you want to install. Follow the install wizard (NOT aWIZARD) of the RUU update. You do not need aWizard any longer to update the ROM, just use the RUU update you downloaded.
post if you need further help.
voyager
Click to expand...
Click to collapse
I've tried that several times and its still returnes the error!
Alek, one more thing ... you do realize that by doing this, you will wipe your device clean (hard reset) and you will need to load everything from scratch. If you use a back up program like Sprite or SPB backup YOU CAN NOT USE THAT BACKUP once you do this!!! You will be loading everything from scratch.
Just letting you know!!
voyager
OK Alek,
Tell me EVERYTHING you have done up to this point. I need to know what device you have, what ROM is currently on it and what ROM you want to flash with. Give me 5-10mins and I'll check back....lets try to get this resolved for you tonight.
voyager
yep! I do know this.. thank you though! I had an experience with Magician on that but I guess it's not much help with prophet though!
I haven't installed anything on this device yet.. just played with ExtRom, unlocked it and deleted O2 staff out of it just to see if I can do it But I do want to get the right OS in here first and then I'll worry about the rest of programs..
you guys wouldn't happen to have Extend Tool (64HTC Extended ROM Tool)would you? I'm visiting my family and I'm on my brothers PC dont have all my staff with me,and can't seem to find it on the XDA FTP
:?: What 64HTC Extended ROM tool are you referring to? If you're on your brothers computer do you have an ActiveSync connection to YOUR device? If so, is all synced up with your Outlook profile etc...?
First I need to know which Prophet you have (Dopod 818Pro, I-Mate JAMin or Q-Tek S200).
First let me say this, if you have a Q-Tek S200, I don't think you are going to be able to upgrade the ROM. I have seen several threads here that indicate that somehow Q-Tek S200 is permanently locked and that the aWizard program will NOT work on it no matter what, (or at least until some geneius here figures it out
Please let me know
voyager
ualvoyager said:
OK Alek,
Tell me EVERYTHING you have done up to this point. I need to know what device you have, what ROM is currently on it and what ROM you want to flash with. Give me 5-10mins and I'll check back....lets try to get this resolved for you tonight.
voyager
Click to expand...
Click to collapse
Hey, thank you so much! I really appreciate it!
ok, I have XDA Neo, German Version
rom 2.9.4.30 GER
rom date 2.14.06
protocol 413.1.03
ExtRom 2.9.4.120
First I have unlocked ExtRom with Wizards Utility
Then I tried to reflash the device to WWE rom with different upgrade utilities from different venders, tried Qtek s200,it didn't work, reterned wrong Vender ID error, then Imate- same result, then Dopod, using diferent RUU wizards, including Wizard Rom Upgrade Utility NoID.
still, no luck..
then I tried aWizard,
first I ran Rapi enable
second I made a back up of my own rom,
then Unlock CID,
then tried writing rom using aWisard, didnt work, aWizard doesn't finds any roms(and the program and rom are in the root directory of c
then tried just unlocking the CID and use Upgrade Wizards again, still, no luck!
tried praying, that didn't help either!
thinking about beer now! But I don't think that would help either
I did sync with PC and outlook.. activeSync4.1
I even tried flashing it with Danish rom, that I couldn't install it either..(I've read on XDA that flashing danish rom first than and only than I could try it to put WWE in to it. well, that didn't work either)
I tried running all possible rom upgrades that are available, and always got wrong vender id error.
even after aWizard reported that my rom was unlocked!
so I have no Idea what else I can try!
may be getting drunk and "sync it in the toilet"!
If we get this to work, you owe me a beer!!! OK, here's what I need you to do...
1) I tried researching this board for any signs of the O2 Neo being permanently locked like the Q-Tek S200, could find NOT anything. (edited, could NOT find anything)
2) Do you have a copy of the I-Mate JAMin RUU update on your brothers computer? If so great, if not, go get it. Try the latest one that came out yesterday.
3) Once you have this I-Mate JAMin ROM (save it to the Desktop for easy finding later) let me know.
4) Also, make sure you have ActiveSync 4.1 and it is set up and you have synced at least once with it. It doesn;t matter at this point what PIM info is on it since its going buh bye ina while, I just need it synced with a REAL partnership, not Guest.
Let me know when you have all these things done...
voyager
you've got the deal on bear! all you can drink! I'll bring you the german staff on my next visit to states!
any way, got it all! Imate jamin rom and sync has been done!
OK,
1) do a soft reset on the device. Once the device is fully up again, plug the usb cable in and let ActiveSync do its thing.
2) Open aWizard. Run the Rapi deal again. After that run the unlock CID.
3) If you get a success message after the unlock CID, CLOSE aWizard.
DO NOT UNPLUG THE NEO FROM THE USB!!! Let me know when this is done.
I found your 64HTC Tool:
http://buzzdev.net/component/option,com_remository/Itemid,100/func,fileinfo/id,196/

Categories

Resources