Related
after a upgrade that didn't work (RSU) my xda is dead, after a cold boot the message appears
"wallaby bootloader v5.15" GSM ERROR
after a search in this forum, i found the yorch.net link and bakked a ROM.
What are the protocols to put everything back again, i bought a cardreader and a SD Card, and put the ROM in the card reader and put the copy on the Card. Nothing is working, and now the card reader cannot read the card again,
Did i maked 2 horreble mistakes, a dead xda and card?
sa a you can see i'm a dumbo with these things.
Please help me, of a link to a posting thats working out for me
grettings Jaap de Ridder
[email protected]
To be honest, I think you may have ****ed it. If it says GSM error, I'd presume that you screwed the radio stack, so it's be tuned to a different network/GSM, (e.g. 900, 1800, 1900 etc) I'm still a beginner but if you edit the radio stack, you can't downgrade which would mean it's been set to a different GSM country/code thingy.
I've tried upgrading ROM once but it screwed up first time, but I made sure it wouldn't modify the radio stack. With the ROM's you can downgrade but with the radio stack it's permanent.
Good luck, getting it working...I just hope you haven't killed the stack, but me being a learner still, I only know so much.
I have an SD/MMC card arriving to try to get mine back in action, but time will tell if it's possible.
so ****ed up
hereby i understand that there is no posibillity to work again with my XDA
I have no idea what to now, my knowledge about these things is over my head.
I tryed to make a new rom, but from what and where to ??
In the trashcan with it.
Not so fast. I'm not an expert on this but I have found that almost anything on this unit can be fixed.
I have done what I am telling you nelow and it worked for me.
Download the XDA OS Image Tools application from the xda-developers site (http://www.xda-developers.com/XDAtools). Burn your rom to an sd card using the XDA OS Image Tools application and your card reader (the application won't work with the card reader on windows 98 but xp and 2000 works fine). Next put the sd card in your xda and go into bootloader mode. It should recognize the OS on the sd card and allow you to flash the xda. Afterward, pull the card out and hard reboot the xda. This should get you up and running. Next, you need to get the radio stack back. This can be done by first determining what stack you want/need to put on the phone (there are a few on http://www.yorch.net in the Upgrades section). Once you've downloaded a radio stack you need to extract out the four files (monitor_ul_bs.m0, monitor_us_bl.map, RSUpgrade.cp64, RSUpgrade.exe). Connect your xda to your pc via activesync and copy the 4 files to your windows directory on the xda. You can also reformat your sd card and copy the four files to the sd card and transfer them to your xda using the sd card slot on the xda. In any event, once you copied the files onto your xda, go into file explorer on your xda find the RSUpgrade.exe file and double click it. It should begin upgrading your radio stack. Afterward, reset your phone and you should have a completely functional xda (oS and radio stack).
Regards,
I forgot to mention that you should make sure the phone portion of your xda is off when you upgrade the radio stack. I caused myself problems upgrading the stack with the phone portion on and it took me a while to get it back working.
and now I'm very confused, because i downloaded the latest XDAtools.exe , i have install these and then, if i go to the OSImageTool, i can browse to.......?? it seams it looking for a file *.nb1 (windows CE) where is that file, i have never made a backup (ROM) from my XDA.
So how i am makeing a booteble ROM
greeting
jaap
Using win2000 prof. NL
Where can i (or from who) download a copy of a working OS PPC 2002 O2-NL in a NB1 format, this to save my XDA
thanks
jaap de ridder
[email protected]
Go to www.yorch.net, choose your rom, uncheck all the additional software, at the bottom left of screen are all options for download, choose the sd card method, once downloaded, write it to your card reader/writer using xdatools then follow instructions from previous person posting.
I did bakked a rom at yorch.net, the XDA downloaded it and after a cold boot, the only screen i get is a blank screen with an icon of a keybord in the right corner in the bottom. nothing is working and the configurationscreen of windows is also not there.
what have i done wrong???
i'm getting deperate now.
greetings
jaap
Can you advise what was happening on the xda while you were flashing the rom? You should have seen numbers at the bottom of your xda increasing incrementally while the flashing process was in progress. Also once the actual flashing was done you should have seen something like "checksum ok" and "cold reboot" (or cold reset). Did you see that?
I think the battery wasn't in full charghe, because during the updateproces the screen was off, he was on 18% of the update that time.
After that, everything is going wrong.
From the sound of it, you didn't flash it using the bootloader process. Using the booloader process the xda should not be connected to the pc at all and the flashing process doesn't show percentages of completion. If your xda screen was off and you saw 18% complete I assume you saw 18% complete on your pc. If so, you were not flashing it via the bootloader. The bootloader process doen't rely onn the pc at all as your xda is never connected to the pc during the process and the screen is always on during the process.
Using xdatools browse and locate your downloaded rom (nb1 file) as your source file.
Then, the destination should be the sd card (not the xda card slot but the sd card reader that you connected - it should show up as a choice if it's properly connected and you're not using windows 98)
Hit the copy button. Once it's done, you have a bootable sd card.
Put the sd card into your xda.
Go into booloader by pressing the power button and soft resetting at the same time.
xda should recognize the sd card and allow you to flash the os.
Try this and see if you can get this far. you have to get to that point to proceed.
I have tried everything under the sun to upgrade my T-Mob PPPC/PE with Yorch's T-Mobile unofficial Upgrade to WM2003. I can't get it to work. Tried: loading ROM to SD card and soft reset, using XDATools OSImagetool, etc... :x
I believe it is tough for any one to advice if you don't state what exactly you did and what error messages you got .....
Are you trying bootloader method. or other method. Please present more detail regarding your problem including current rom/radio etc and things that you have tried already.
Sorry. First, loaded the file, NK.NBF onto my SD card using OSImagetool.exe. Then per instructions that were given to me, did a soft boot on the device. It simply rebooted and after it came up, there was a message on the screen asking my if I wanted to format the SD card for use with the device and telling me that if I hit "yes", the card would be erased and all data lost on the card.
The next thing I tried was to use OSImagetool.exe directly. Source- nk.nbf (on my desktop) and Destination: Device memory (via Programme A). The error I got was "Programme A not found - run with "--register" error opening target device.
I even tried to run OSImagetool.exe from the command prompt using --register as an argument and got the same exact error.
Then, I loaded the NK.NBF file to the SD card then ran OSImagetool with source: SD card, destination: Device memory. Then got the same error: "Programme A not found - run with "--register" error opening target device."
Hope that helps.
i dont know the program OSImagetool
but when i updated my xda to 2003 i used xdatools to transfer the rom to the sdcard and then i DIDENT! softreset but went into the bootloader and it started to update
Rudegar said:
i don't know the program OSImagetool
but when i updated my xda to 2003 i used xdatools to transfer the rom to the sdcard and then i DIDENT! softreset but went into the bootloader and it started to update
Click to expand...
Click to collapse
They are the same program OSImagetool is just the name of the .exe file.
@jhug whats your bootloader version? Sounds like it might be 5.17 or newer!
HTH
When the xda asked you if you wanted to format the sd card you should answer no, it means the rom has in fact been written to the card, you then need to enter bootloader mode, a soft reset is no good, just push the stylus in the reset hole while holding down the power button, it will then ask you to push the action button which is the centre of the 4 way pad, your rom will then be programmed, make sure the battery is charged also. When the process is complete, unscrew your stylus, then insert the top half of the stylus in the hole on the bottom right of your xda, just push once, after one minute push again, this turns the battery off, then on again, you should then have a working system.
my bootloader is 5.22 btw
I wanted to check and see if the ROM was in fact on the SD card, so I did a soft reset and the notification came up and asked me if I wanted to format the SD card. I clicked no and assumed the nk.nbf file was on the card. I then did a soft reset while pressing the power button and went into bootloader mode. It did not ask me to push the action button, so I did anyways and it went into diagnostics mode. Ideas???
I'll try reloading the ROM on the SD card and try it again. I'll keep everyone posted. Thanks for your help! BTW, bootloader version is 5.15.
Rudegar said:
my boot loader is 5.22 btw
Click to expand...
Click to collapse
Consider yourself luck if you haven't had any problems upgrading
using the SD card boot loader method then!
Also most of the RS upgrade failures that I seen / fixed and tried to fix had boot loader 5.17 or higher, so keep that in mind. :wink: Lucky, Lucky you!
jhug said:
I'll try reloading the ROM on the SD card and try it again. I'll keep everyone posted. Thanks for your help! BTW, bootloader version is 5.15.
Click to expand...
Click to collapse
Please do!
Also whats the size and make of your SD card?
Well, I tried it again and the same thing happened. It went into bootloader mode and did not ask me if I wanted to install the new OS. I tried pressing the volume button and it said to connect the USB cable. I also pressed the contacts button and it went into Diagnostic mode. Aaaaaarrrrrgh!
BTW, it's a 256MB Sandisk card. (Great for holding about 200 songs! :lol: )
jhug said:
BTW, it's a 256MB Sandisk card. (Great for holding about 200 songs! :lol: )
Click to expand...
Click to collapse
Some how I knew you where going to say a "256MB Sandisk"!
For some unknown reason had the same problem using the same card,
if you can try using a 64MB or a 128MB card and see what happens. :wink:
HTH
It finally worked! I loaded the ROM to the 256mb Sandisk SD card while in the unit, removed the SD card, inserted the SD card, then did a warm boot while pressing the power button and the ROM image loaded! I did the usual battery cutoff and then rebooted it and it works fine. Thanks everyone who gave me advice with this. :lol: :lol:
Where there is a well there is a way, great job!
But how in the hell did you figure that one though? :wink:
I decided to get creative. Dangerous when you're working in Wallaby, but it worked! :shock:
I have a siemens sx56 with AT&T. I was trying to upgrade the ROM version to unlock it. Using XDA developer software and during this process, somehow the connection between the computer and the phone stopped (active Sync). Now the phone is not responding and the screen still displaying the upgrading process. I tried to reconnect but the Active sync does not recognize the devise. I read in this forum that you can solve this problem by using SD card with a good ROM version. Here is what I did. I copied the NK.nbf to the SD card using my computer SD read/write slot. I inserted the SD card in the phone and did the boot loader mode. What I got is "Wallaby boot loader v5.22 GSM OK" that set. Does the phone will automatically ask to press action to start flashing or I have to press a certain key. I tryed all the keys but they give me different tests that they work fine. So far I am not able to find the key that will install the the cooked rom. After that, when I tried to use the SD card in the computer, it did not recognize the card and ask me to format the SD card. I tried the fat and the fat 32 format and download NK.nb1 and/or NK.nbf and again I got the samething. Do I need to down load the ROM file using the XDAtool or just copying the file from the computer to sd directory will do it. I would really appreciate it if someone points out the best way of handling this problem (i.e. get the phone to work with the appropriate ROM and unlocking it) thanks.
Seif said:
I have a siemens sx56 with AT&T. I was trying to upgrade the ROM version to unlock it. Using XDA developer software and during this process, somehow the connection between the computer and the phone stopped (active Sync). Now the phone is not responding and the screen still displaying the upgrading process. I tried to reconnect but the Active sync does not recognize the devise. I read in this forum that you can solve this problem by using SD card with a good ROM version. Here is what I did. I copied the NK.nbf to the SD card using my computer SD read/write slot. I inserted the SD card in the phone and did the boot loader mode. What I got is "Wallaby boot loader v5.22 GSM OK" that set. Does the phone will automatically ask to press action to start flashing or I have to press a certain key. I tryed all the keys but they give me different tests that they work fine. So far I am not able to find the key that will install the the cooked rom. After that, when I tried to use the SD card in the computer, it did not recognize the card and ask me to format the SD card. I tried the fat and the fat 32 format and download NK.nb1 and/or NK.nbf and again I got the samething. Do I need to down load the ROM file using the XDAtool or just copying the file from the computer to sd directory will do it. I would really appreciate it if someone points out the best way of handling this problem (i.e. get the phone to work with the appropriate ROM and unlocking it) thanks.
Click to expand...
Click to collapse
Bro, you shouldn't change the Sd fat you erased what's written on it anyway your unit is still on the safe side and you can bring it to normal.
First of all downgrade your bootloader to 5.15 >>>
goto this http://forum.xda-developers.com/viewtopic.php?t=3274
Hi,
I also have exactly the same problem with my Siemens SX56 as those of Seif's. My Wallaby's boot loader version is 5.22. Ramram said that the first thing to do is to downgrage bootloader. But I couldn't understand how to downgrade the bootloader because I do not have a copy of old bootloader. Should I use 'OSImageTools' or 'XDArit' to write backed up CE image to SD card?
Seif, how did you solve your problem?
Best Regards
rafia said:
Hi,
I also have exactly the same problem with my Siemens SX56 as those of Seif's. My Wallaby's boot loader version is 5.22. Ramram said that the first thing to do is to downgrage bootloader. But I couldn't understand how to downgrade the bootloader because I do not have a copy of old bootloader. Should I use 'OSImageTools' or 'XDArit' to write backed up CE image to SD card?
Seif, how did you solve your problem?
Best Regards
Click to expand...
Click to collapse
You need XDArit to write the rom to your SD read the past post on how to copy rom to your SD which is the safest way of installing the rom into the device, by using XDAtools press on FIX BROKEN BOOTLOADER this will downgrade you bootloader to 5.15 don't forget to connect your unit to the cradle when you want to downgrade.
I recommend 1rst of all to make a quick search in threads to be totaly ready for this
this would help :
http://forum.xda-developers.com/viewtopic.php?t=6581&highlight=downgrade+bootloader
http://forum.xda-developers.com/viewtopic.php?t=2068&highlight=downgrade+bootloader
Good Luck now.
Update : How to fix failure during upgrading ROM
The problem was solved. Here is what I did. I copied the NK.nbf file to the SD card using the XDAtools. It seems that the XDAtools uses special format for the bootloader that well recognize the ROM file on the SD card. Rafia your bootloader (v5.22) is fine you do not need to downgrade it.
You should follow this procedure:
1. Install ActiveSync that comes with the device.
2. download XDAtools from this site and install it in your computer.
3. Cook the ROM ( or get it by extracting the zip file from the XDA developers special edition ROM.)
4. Use the XDAtools to copy the cooked NK.nbf file from your computer to the directory of the SD card
5. Insert the SD card in the dead device and go to the bootloader mode (soft reset while pressing power key). Make sure it has more than 80% battery before starting.
6. If it is still working and the bootloader ver. is older than 6.22, it will ask you to press action to start flasing.
7. Once finished, remove the SD card and hard reset, wait 60 sec and hard reset again.
Good Luck and special thanks to Biso for his help.
Re: Update : How to fix failure during upgrading ROM
Seif said:
The problem was solved. Here is what I did. I copied the NK.nbf file to the SD card using the XDAtools. It seems that the XDAtools uses special format for the bootloader that well recognize the ROM file on the SD card. Rafia your bootloader (v5.22) is fine you do not need to downgrade it.
You should follow this procedure:
1. Install ActiveSync that comes with the device.
2. download XDAtools from this site and install it in your computer.
3. Cook the ROM ( or get it by extracting the zip file from the XDA developers special edition ROM.)
4. Use the XDAtools to copy the cooked NK.nbf file from your computer to the directory of the SD card
5. Insert the SD card in the dead device and go to the bootloader mode (soft reset while pressing power key). Make sure it has more than 80% battery before starting.
6. If it is still working and the bootloader ver. is older than 6.22, it will ask you to press action to start flasing.
7. Once finished, remove the SD card and hard reset, wait 60 sec and hard reset again.
Click to expand...
Click to collapse
Thanks a MILLION for this info. I'm in the same boat, with bootloader 5.22. One question though, when I'm in bootloader mode, which option do I choose from the menu to transfer the ROM to my device from the SD card? Will there be something automatically coming up? Or will I use one of the options listed below:
1. CE ROM TO SD
2. BOOT TO SD
3. CE + BOOT TO SD
4. GSM ROM TO SD
5. CE + GSM TO SD
By the way, so I never do anything to ruin my device again, can someone please explain what each option does?? I really don't have a clue.
as you can read from the menu you type in all these options are to the SD card
and they are to backup i suppose
rom upgrading should start automatic when a sd card with valid rom is in the sdport
and you are in the bootloader
maybe it ask you i forget but it's not something you have to find browsing
the menu's
Rudegar said:
as you can read from the menu you type in all these options are to the SD card
and they are to backup i suppose
rom upgrading should start automatic when a sd card with valid rom is in the sdport
and you are in the bootloader
maybe it ask you i forget but it's not something you have to find browsing
the menu's
Click to expand...
Click to collapse
Thanks for answering my question. Now I simply need to find a really good ROM to use to load back onto my device. What I would like to do is end up with Windows Mobile 2003, but the device is locked at the moment.
Can someone recommend a ROM for me to load onto the device so that I can then unlock it and THEN upgrade to 2003? Or is there a 2003 ROM out there that will also unlock? Originally, I ended up in this predicament by upgrading to the 2003 upgrade from Rogers AT&T, but that locked the device on me. I then tried to use a cooked 2003 ROM, and that's where I am now, without a useable device.
Thanks for all replies!
Linger1974 said:
Rudegar said:
as you can read from the menu you type in all these options are to the SD card
and they are to backup i suppose
rom upgrading should start automatic when a sd card with valid rom is in the sdport
and you are in the bootloader
maybe it ask you i forget but it's not something you have to find browsing
the menu's
Click to expand...
Click to collapse
Thanks for answering my question. Now I simply need to find a really good ROM to use to load back onto my device. What I would like to do is end up with Windows Mobile 2003, but the device is locked at the moment.
Can someone recommend a ROM for me to load onto the device so that I can then unlock it and THEN upgrade to 2003? Or is there a 2003 ROM out there that will also unlock? Originally, I ended up in this predicament by upgrading to the 2003 upgrade from Rogers AT&T, but that locked the device on me. I then tried to use a cooked 2003 ROM, and that's where I am now, without a useable device.
Thanks for all replies!
Click to expand...
Click to collapse
First of all get the "Special Edition Rom" to your device Unlock it then cook any other Rom you prefer
Special Edition Rom at http://cuba.calyx.nl/~jsummers/XDA/XDA-developers-SER-v12.exe
Good luck
First of all get the "Special Edition Rom" to your device Unlock it then cook any other Rom you prefer
Special Edition Rom at http://cuba.calyx.nl/~jsummers/XDA/XDA-developers-SER-v12.exe
Good luck[/quote]
Thanks, Ramram. I'm sure I'll have more success this time, but it's just odd that I went from a 2002 ROM, which was unlocked, to the Rogers 2003 ROM, and the phone was locked after that.
I guess I should stay away from that Rogers ROM then?
Linger1974 said:
First of all get the "Special Edition Rom" to your device Unlock it then cook any other Rom you prefer
Special Edition Rom at http://cuba.calyx.nl/~jsummers/XDA/XDA-developers-SER-v12.exe
Good luck
Click to expand...
Click to collapse
Thanks, Ramram. I'm sure I'll have more success this time, but it's just odd that I went from a 2002 ROM, which was unlocked, to the Rogers 2003 ROM, and the phone was locked after that.
I guess I should stay away from that Rogers ROM then?[/quote]
Why to worry about the Rogers Rom you know now a way to unlock your phone.
I assume the Rogers rom is based like the At&t rom which it has the sound clipping bug , so I'd rather say that you could cook a T-mobile rom 4.01.16 WM2003 and try it it does not have the sound clipping bug..
I have been trying to cook a ROM for my XDA 1 using Pocket PC 2002 o2 3.17.03 and a few other programmes. I end up with about 250K vacant in my Rom.
When I burn and download it I download a file of about 15.8MB named rom but whenever I try to execute it nothing happens.
I have previously SER 1.2 installed. I have active synch up and running as well but as soon as I double click a black window appears for a few seconds and disappears.
Could you tell me what is the problem. I have noticed that such behaviour doesnt exist when I try Win mobile 2003.
FYI i am using a Windows XP machine to access internet with 256MB RAM.
make the rom as nbf or nb1 and not exe is my advice
here is a guide as to how you get it to the xda after that
http://forum.xda-developers.com/viewtopic.php?t=10698
sd way is much more safe
Will I need a card reader?
Hi,
I dont have a card reader with me. Do proceed by the suggested method would I need a card reader or anyother hardware other than my SD card (which by the way is a 64MB MMC card)
Will the existing information in the card be deleted? Would I need to backup that Info?
Regards,
download XDAtools.exe from here and you can use your XDA as a card reader/writer ... I 'm not sure the MMC can be used instead of SD
Hi you geniuses out there,
My 1 yr old 8gig SanDisk (SDHC, Class 2) suddenly ceased to work, using the card reader/adapter and plugged it into my USD slot on my PC won't be detected either.
I've flashed a lot for the last year and never ONCE faced this weird problem, not on my Topaz (Touch Diamond 2), or my previous Raphael (Touch Pro).
(1) For troubleshooting's sake, I plugged into the Topaz another card which is working on the Raphael as well as on the PC (4gig Sandisk SDHC, Class 6), IT WON'T WORK EITHER!
(2) The only difference I did was when this strange thing occurred, I was using the mtty v1.4.2.0 HEREto get a total cleanup before flash, following the instruction (cmd> task 29). I'm using HSPL 1.83 Olinex of course.
Any way I can retrieve the now defunct SD card?
It won't detect on my phone, it won't detect on my PC.
The other working card now won't detect on my phone (Topaz) either.
Have I screwed up my Topaz' card slot?
HELP, please!
Bump.
Any living soul, please?
Bump. Again.
Hi,
Firstly have you tried a second card reader/adapter for the PC?
Does your partners phone recognise your SD Card?
Have you tried to flash a different ROM, OEM ROM as the issue may be ROM based?
Have you also tried checking with the creator of "mtty1_1_.42_538"?
-Sie- said:
Hi,
Firstly have you tried a second card reader/adapter for the PC?
Does your partners phone recognise your SD Card?
Have you tried to flash a different ROM, OEM ROM as the issue may be ROM based?
Have you also tried checking with the creator of "mtty1_1_.42_538"?
Click to expand...
Click to collapse
Somehow I second question the mtty1_1_.42_538, I'm sorry but that utility is the prime suspect. I used to religiously do hard-reset > stock ROM > hard reset > wanted ROM > hard reset kind of cumbersome ritual. But not once did my SD card fails me when I did it the long way.
I hard reset my phone this morning, and suddenly it can detect any working SD(HC) card.
Thanks.