Problem with ROM Kitchen - MDA, XDA, 1010 Software Upgrading

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

Related

stupid, stupid

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.

How to fix failure during upgrading ROM

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..

Problems after Flashing - XDA1

Hi!
I flashed my O2 XDA // Wallaby 5.15
to WM2003SE.
The first Boot worked, after that, I wanted to switch the language to german, I had to reboot, and from there on, my problems began....
i read about the possibility to re-flash my os with an sd card.
everytime i plugin that card to my notebook, winxp says, i have to format that card.
after that, i tried to copy the nk.nb1 file to this card, with success...
and then, i plugged in that card back to my xda.... nothing happens...
if i press the "contactlist" button ( in bootloader ), i come to some backup modes, but not to read an new os-image from sd card.....
i'm getting crazy :/
can someone help me plz ???
You have to use xdatools to copy the Image to the sd-Card. It is written in a special format. Copying with the explorer is useless for flashing...
HTH
Stefan
i tried this some times....
but do i have to save "NK.nb1" to sd-card (( h:\nk.nb1 )) or in another format ?? for example sd-card image ( *.img ) or *.nbf .... etc
my last try for this evening....
must go to work in some minutes.. ;(
damn night-shift ^^ ( but good thing: nothing to do... just sit there and wait )
Download http://lumpistefan.dyndns.org/tools/XDATools.zip unzip it and run osimagetool.
Select the nb1 or nbf file in source and select your card reader with inserted SD-Card as Destination. Press Copy and wait until process has finished.
Insert the card into your xda. If there comes a message to format the card press no or do directly a softreset wirh power button to enter bootloader. Than the image should be recognized ....
HTH
Stefan
doesn't work....
what have i done ? *omg*
if i want to write an image to my sd card, my winxp wants me to format it....
if i do this, the writing works fine, but my xda doesnt recognize the new nb1....
i get no connection to my pc with the cradle ( but there is something being found in windows while my xda is in bootloader mode.... )
hi.
i've read something about problems with winXP, if you want to write a new os to sd card... is that true?
btw. it's still not working....
my pc - sd - card - reader/writer cannot write the file in that way my xda could read it as an new os......
holy ****
i solved the problem i think
the xda os image tool doesnt work with notebook internal sd-card-reader/writer.... or winxp is the problem....
now with win2k3 server it works..... *omg* i'm so happy
thx!!!!!!!!!!!!!!!!!!!!!!!
oppaunke said:
the xda os image tool doesnt work with notebook internal sd-card-reader/writer
Click to expand...
Click to collapse
I think that is the problem heard a few times, that the internal card reader made some trouble.
Glad to hear, that your device is working again....
Stefan

2003se upgrade for a dummy

So, ive read post after post on performing this task and it is still beyond my capabilities. My wallaby is running ppc2002, rom version is 3.20.06, radio version 4.21.01 protocol version 32s54. It's running bootloader 6.22, i havent got active sync, xdatools wont run due to missing dll's or some such thing. Have a 1gig sd and a 512mb mmc,,,,
How can i upgrade with this setup? visited rom kitchen (awesome site) and cooked up a rom, extracted NK.nbf,
Need help! Surely i can upgrade with this equipment,
http://www.romkitchen.de/ make an exe then
Rudegar said:
http://www.romkitchen.de/ make an exe then
Click to expand...
Click to collapse
So is the exe executable from an sd card?
no the exe is only for activesync upgrades
http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_FlashSD
how to flash using sd
if the tool is missing dll's then type in the name of the dll in google and find a place to get the dll and it will work
Rudegar said:
no the exe is only for activesync upgrades
http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_FlashSD
how to flash using sd
if the tool is missing dll's then type in the name of the dll in google and find a place to get the dll and it will work
Click to expand...
Click to collapse
Right, well got active sync which meens the dll's i needed are in system 32 or whatever. But,,, Does bootloader 6.22 cause problems?? Thanks for all the help,, sure this fone is a bit old but who cares. Massive screen, runs office, windows media, touch screen, great fone
Any suggestions? I cant be the only one without a data cable or cradle. At the end of the day i want the fone to run best as possible. I am thinking there is alot more compatable software for wm2003 then ppc2002? @ the moment im running mame and pacman,,,,,,,, Speaking of software, is the media player in 2002 meant to be slow? As far as video go's ive given up there.
what is your problem?
Problem is i dont seem to be able to downgrade from bootloader 6.22 to 5.15 so i can update the rom to 2003. doing ll this without a data cable or cradle.
Bootloader should not cause any problems.
Missing Dll´s for XDATools came as you have ssen correctly form ActiveSync. So you need to install this programm on your PC to use XDATools. Afterwards you will be able to wirte the ROM on your SD-Card and then flash the new ROM on your device.
So if you don´t have any cradle or cable, and don´t sync with ActiveSync, how did you manage your conacts,install software, exchange files, ....?
Stefan
I see the confusion
I have card reader's on the front panel of my pc. So i am using xardit to transfer the bootloader images onto either an sd or an MMC card. So i transfer the patch with the NB2 extension on to the card. Cold reboot xda and it gets to the normal screen telling me i need the keycard.
I can use either xdarit or isoimagetool to transfer the .NB1 file on to an SD.
I have no data cable, so these are the only methods i can use. Just pc with multi card card, sd car, mmc card.
LumpiStefan, the rom kitchen is a damn fine peice of work!
when i had a wallaby i only ever flashed it using a sdcard reader
was pretty easy used ositool put the nbf / nb1 on the sdcard
after which the cardreader could no longer read the sdcard(that mean it's successfully planted)
then i put in the sdcard and entered the bootloader and it autostart upgrading
and when it's don i hardreset and thats it
Hi And thanks
I have tried this with a 1g toshiba sd and a 512 sandisk mmc, neither seem to auto start an update. I have browsed the web a bit and have found different theories on bootloader being a problem. My card reader is a panel on the front of my pc, or using my ngage. tried formatting fat16 or fat32. Im sure it's currently ppc2002 as this is the first screen after the o2 water screen
I think your problems come from your card reader. Many people have reported, that the internal card reader causes problems in writing the ROMs in correct way on the cards. I would s uggest to use an external card reader/writer.....
Stefan
and those are only 10£$€'ish
Thanks guys for your help, all up and running now. I appreciate the advise. Rudegar, my problem was getting the wrong info from elsewhere, the solution was the card reader, Cost me $9.00 au to buy one. I thank you both

Stuck on a basic issue

I was trying to upgrade my Wallaby from WIN CE to Win 2003. I managed to mess up the ROM upgrade using active sync and so am now stuck on the white screen!
I can get to the bootloader screen ok (showing Bootloader 5.17 - soft reset with the power button) but can't get the device to boot from an SD card. I have downloaded XDATools and can run the osimage tool but I don't know what name to give the destination file, or what file extension. If I simply select the destination from the dropdown box, I get an error message when trying to write to the SD card (it's a 1Gb SD). I have also tried with a 64Mb MMC and get the same errors.
I've also tried browsing to the destination (card reader) and using nk.nb1 as the file name but when soft resetting to boot loader I don't get the option to boot from the SD card.
I'm well versed with flashing Universals or Himalayas but the Wallaby has me stumped currently!
Any help please?
I hope this help
I don't know much about updating wallaby because I discovered this forum too late, but I updated the rom via activesync. The rom was in an .exe program cooked from www.romkitchen.de (very easy).
I read somewhere (I can't remember) that other ways of upgrading where difficult, I don't know yours.
If i remember from my wallaby you had to use a program to format and install the image to the sd card. You couldnt just copy the nbf file straight to the card. Once the sd card was created the card was no longer readable by windows. But it contained the image and the wallaby booted but i am sure it would only work with a 32mb card
Found the Problem!
Well I finally found out what was causing the issues. Bloody Windows Vista!!! Ran the XDATools on my XP system and managed to load the sd card without any problems, then proceeded to upgrade (downgrade??) the boot loader to 1.15 and now have it running with Windows 2003SE (I think - can't quite remember as I've zapped it so many times trying to get a ROM I like).

Categories

Resources