Database Users

Help Unlocking A SX56 from AT&T

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.

N00b Needs help please! RSU upgrade issues...

Hello All!
I just got an XDA that has the oldest version of all three components. I was browsing the rom cooker last night and also found a RSU for 4.21 that i thought i could install (activesync install exe)... Oh boy what a mistake!
So now, after the "programme B" update that was in dutch was completed, i got a continuous pop-up in dutch that came up and stayed on every boot. I managed to remove the items from startup and i dont have that problem any more, but my radio does not work at all, and i cannot connect to active-sync to go back or try another RSU!!! It just seems that the usb on the device is messed up, as the PC tries to connect when i cradle it.
I believe my problem is that i did not use programme A first? i only discovered that program after screwing up the wallaby...
I am on my way to buy an SD card now to aid in the disaster recovery. In the meantime, if anyone would be so kind as to reply with a suggestion for fixing it, and how to properly update the components, i would Greatly appreciate it!
Thanks in advance, and i love the forum! Look foward to spending lots of time here

OK, so i found the GSM error thread and followed the instructions, but when trying to upgrade the RSU, i get the error: "Upgrade Failed! hit ok to reset device"
Any suggestions?

All Fixed! From zero to hero in a day!

gazorp said:
All Fixed! From zero to hero in a day!
Click to expand...
Click to collapse
How have you fixed it?
Maybe we can update the instructions....
Stefan

I followed the instructions here: http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_GSMError
The only difference is that i did not copy to the startup folder and ran the update manually from the windows directory. Allowing the upgrade to run on startup always caused a problem like you described

Help with charmer

Hi,
I seem to have made my MDA compact II a brick. I was having problems hard reseting it (Format FAT failed) so I tried upgrading to a different firmware.
I now have the RUU_Prophet_2151327_21513121_021921_DOP_ASIA_WWE_Ship-NoVendorID
firmware on it. This is not good as it is for the Prophet, although it says in the Wiki that this should work. Anyway I can now hard reset the phone, so all I need to do is flash the TmobileUK firmware back on it. The only problem is that it doesn;t let me do it. It says error:296 upgrade only.
Anyone any ideas?
cheers.

extract the contents of the t mobile package using win rar
download
ftp://xda:[email protected]/Prophet/Tools/ROMUpdateUtility-NoVendorID.zip
and put in the same directory and run.

It gets to 1% then says invalid command, not for this phone.

Latest T-Mobile ROM is at http://www.tm-phonedownloads.com/download_manager_mda_com2.html
very stable, much better than the original shipped ROM

Finally got it back.
If you have a T-mobile MDA II (Charmer), then Flash it with a Prophet ROM, the only way I could get it back was to use the following:
RUU_Charmer_100_100_049_CHS_Ship.rar
typho5 -x nk.nbf
Then created a new nk.nbf with the output using nb2nbf.
I then Flashed this with Wizard_RomUpgradeUtility_noID
And miracle it started. I quickly CID unlocked it and am now flashing with latest T-mobile.
My problem was that the Rom Update programs wouldn;t read version 2.xx ROMS.
Anyway it has just finished and looks fine. Thanks for everyones help, now I just have to get my SD wifi card working.

How do you do it
Hi I just got a MDA compact II from T Mobile UK I would like to upgade the ROM but its all very new to me since you know what you are doing can you post an idiots guide to the process.
Hope you can help

Hi, it depends what Rom you want to upgrade it to, the latest one from T-mobile is pretty good. There is an unbranded one (no T-mobile logos or suchlike) or there are Roms in different languages. It depends why you want to change the firmware and what to.

I suppose I don't really know the problem is as I just got the thing did some searching and came across this site read your post and thought i want to do this maybe you have some suggestion. Also I tried the RUU mentioned in an earlier post but it I can't update when I get to the from/to screen it tells me I will go from 2.6.2.110 to 2.6.2.110 I was expecting to move up.

daveh1171 said:
I suppose I don't really know the problem is as I just got the thing did some searching and came across this site read your post and thought i want to do this maybe you have some suggestion. Also I tried the RUU mentioned in an earlier post but it I can't update when I get to the from/to screen it tells me I will go from 2.6.2.110 to 2.6.2.110 I was expecting to move up.
Click to expand...
Click to collapse
Sounds like you are running the latest version. Is there a problem with the phone? If the phone works fine, I would just unlock it using lokiwiz02b (So you can use any network card) and then EnableRapi (So you can run unsigned code) then CID unlock it using awizard (so you can use any Brand/Language of ROM).
If you have no problem with the firmware I would leave it alone.

Hi,
Yep, I'm in the same situation, why does the prophet firmware load onto the charmer without erroring? !!!
Anyway, I have a copy of RUU.rar but I'm having problems working out what I need to do to it between unpacking and flashing the phone (i.e. the typho5 bit and then the nb2nbf).
Can someone please help me out?
P.S. The phone just sits at a black screen that says 'Dopod' across the front at the moment

Can anyone tell me how to 'force' a downgrade of firmware? I've got what appears to be the right firmware from FTP but it won't over write the incorrect version 2 installation as the uploader software thinks it's later therefore better.
There has got to be a better option from the command line surely?
HELP phone is dead

Chirpy said:
Can anyone tell me how to 'force' a downgrade of firmware? I've got what appears to be the right firmware from FTP but it won't over write the incorrect version 2 installation as the uploader software thinks it's later therefore better.
There has got to be a better option from the command line surely?
HELP phone is dead
Click to expand...
Click to collapse
Progress, but now it works only from the charger so the shipped ROM upgrade won't work as it reports the battery as being at less than 50%.
Anyone know how to force a ROM upgrade or where I can find the right ROM files to use awizard to do this?

Questions About Flashing My TMO Wing

I downloaded the USPL file and followed all the steps, put the ROM that I wanted which was a 6.1 in the RUU folder, made an AS connection and ran the USPL. When I finished the Updater said it had failed with a Code 270 error message, but the RUU screen in the USPL said it had completed successfully. When my phone booted, I had the same ROM, same information as before I flashed it....what am I doing wrong? I am not shy about flashing my phone, I'm just missing a step or something. I removed my SIM and SD card to flash, that is correct also right? Suggestions would be appreciated because now that I have my Wing, I plan to try out many 6.1 ROMS until I find one I like. Also, can anyone tell me how I can get the latest most up to date version of Open Touch....when I click on the link it goes nowhere and ttrans says he's working on it, and then I saw another link where another person has started working on that ROM, Can you provide correct links so I can read about what's going on with that? Thanks!

Typically I have to try a few times before my ROM flashes right usually 2 or 3 tries. I get the same message too just give it another try.

Error (262) for diamond2 wm 6.5

Hi,
Help me please just me and that happens to me the mistakes my God.... I had the original ROM version coming with my diamond2, put the upgrading and went well until the moment he arrived at 9% and restart the pda, re-install I think is normal, however the installation continued until k stopped in 18% and after a long time gave a notice of error (262) made the recovery as recommended and continues to give error ....
I do help me please

This just happened to me too
My phone was hardspl´d
It stuck at 18%, but no error message so far. Did you unplug your phone?

Read this:
http://forum.xda-developers.com/showthread.php?t=425913

I'm not sure. Have you flashed other roms before? Perhaps you have a bad download. I know the servers are overloaded from all of us geeks sucking down the WM6.5 rom... perhaps its bad.
What I normally do is put the phone in bootloader mode first by holding VolDown, while resetting the phone. This will give windows time to install the proper drivers and get situated. Once done, try flashing again.
I think 262 is a connection error. Probably driver related since you said you ran your stock rom. But check your cable. Make sure its secure and reliable. Next try another USB slot. If nothing else try a different computer... sometimes PCs just will not cooperate.

Thank you very much fighter, will try that.

I had Official 6.1 Asia WWE installed, HARDSPLed. Tried to upgrade to 6.5 on my computer and my laptop, nothing worked. Both stops at 9%, disconnects, comes back and stucks at 18% again. Had to go back to 6.1, this time it worked to bring phone to life.
My phone was bought in Taiwan.
Guess I am out of luck

I think the best way to upgrade is as follows:
1. Run the RUU_Topaz_S_HTC_WWE_2.16.405.4_Radio_Sign_Topaz_61.44tc.25.32_4.49.25.17_Ship.exe on your PC/laptop to extract and get the RUU-signed.nbh.
2. Copy the RUU-signed.nbh to topaz SD card and rename to topaimg.nbh
3. Upgrade new ROM from SD card.

I had the same 262 error as well, screen went blank for a second at 9% and finally freezez at 18% with the error message. Heres what you need to do:
Update your HardSPL to 1.83
Flash 6.5 again
????
Profit!

Hello,
already did everything you say and nothing. I liked to tell me where I can get the former Rom wm6.1 because meeting.
help me please

duongla said:
I think the best way to upgrade is as follows:
1. Run the RUU_Topaz_S_HTC_WWE_2.16.405.4_Radio_Sign_Topaz_61.44tc.25.32_4.49.25.17_Ship.exe on your PC/laptop to extract and get the RUU-signed.nbh.
2. Copy the RUU-signed.nbh to topaz SD card and rename to topaimg.nbh
3. Upgrade new ROM from SD card.
Click to expand...
Click to collapse
Would you be so kind as to enlighten me/us on how to extract the nbh file from the executable file.
Thanks

player911 said:
I'm not sure. Have you flashed other roms before? Perhaps you have a bad download. I know the servers are overloaded from all of us geeks sucking down the WM6.5 rom... perhaps its bad.
What I normally do is put the phone in bootloader mode first by holding VolDown, while resetting the phone. This will give windows time to install the proper drivers and get situated. Once done, try flashing again.
I think 262 is a connection error. Probably driver related since you said you ran your stock rom. But check your cable. Make sure its secure and reliable. Next try another USB slot. If nothing else try a different computer... sometimes PCs just will not cooperate.
Click to expand...
Click to collapse
How can u exit bootloader screen? Only by removing the battery or...?
Thanks!

I do not have with me the adapter card to do this
There is also a problem is that the pda now I do not go the menu with the three colors blue, green and red, until I have done a hardreset and nothing ....
at least I no longer ask the solution with the ROM 6.5 we only have as I had before ... and wanted my pda to work help me please

Little history for my friends with same problem here:
1. Bought Diamond in Taiwan with Chinese;
2. HARDSPL 1.33;
3. Install Asia WWE 6.1 ROM;
4. Try update Official WWE 6.5 ROM, no luck, remove battery and put back;
5. Reinstall Asia WWE 6.1 ROM, everything back to normal;
6. Update HARDSPL 1.83; Ask brother to donate
7. Install Duttys ROM or Official ROM works too

Hello,
I already installed the previous ROM with the 6.1 and everything was normal.
I tried to install again the OFFICIAL ROM 6.5 and the problem remains back to the error at 9% and 18% for the progress bar giving an error (262).
not understand some things as:
6. Update HARDSPL 1.83; Ask brother to donate
7. Install Duttys ROM or Official ROM works too
is there any solution?
can help me

Sorry:
1. install Hard-SPL 1.83.OliNex (http://forum.xda-developers.com/showthread.php?t=520312)
2. install 6.5 ROM or Cooked Rom.
It resets 9% again in Official ROM, but reconnects and go to 100% (no stop 18% again).
Dutty ROM no stop at 9% or 18%.

problem solved
thanks for the great help amazing
thank you very much

hello
the memory card is not me out with the official wm 6.5 ROM
what can I do to boot the card?? I have a diamond2
ah no problem of card pk started the card with the adapter to the PC and read it perfectly.
pesquisar

AntonyWatson said:
Would you be so kind as to enlighten me/us on how to extract the nbh file from the executable file.
Thanks
Click to expand...
Click to collapse
When you run the RUU, the RUU-signed.nbh will be extract temporarily to a folder in driver C:
(For me: C:\Users\Duongla\AppData\Local\Temp\pft51D9.tmp)
Just do a search and you'll find it.
And remember to HSPL to 1.83.

i have the same problem too
hello
i have a diamond 2
ihave olinex 1.83 from here http://forum.xda-developers.com/showthread.php?t=520312 and i can not install ANY wm6.5 rom!!! on the other hand EVERY 6.1 rom i have trie (5 different greek and english) work perfect?!?!??
any suggestions?
thanks

i had the same issue
i was running 6.1 (stock rom) which was hard spl'd
i had the same error kept going to 262 and haviong to be recovered
so i re hard spl'd with the latest one, and it worked fine after that,