Hi there,
I have searched for this problem and found various suggestions involving xdarit etc but none seem to help.
I am getting the above message following a ROM flash, using sd card writen with xdarit. I have tried 3 different roms all producing the same result. Originally tried flashing with a w2003 rom but would be grateful to get anything working!!
The xda will now only show bootloader and some checks.
Wallaby bootloader 5.15
Anyone able to help?
Kind regards
Have you tried another SD-Card? MAybe there is a problem...
Flashed my device about 50 times, and had sometimes (about 2 or 3 times) the same problem.
Reflashing worked then fine...
Stefan
Thanks
I have tried anther sd card with the same result.
FYI I am formating sd cards FAT before writing rom to them
Could I be using the wrong rom?
Kind regards
maybe a corrupt file sometimes files taken from the internet gets damaged on their way to you
Where should I obtain a bog standard rom?
bog ? as in a swamp ?
not sure what a bog rom is but here he have many roms
http://lumpistefan.dyndns.org/
bog standard AKA original basic unaltered rom
Thanks for the link, I have been using these roms but will try try again.
Q Should xda be on mains power when flashing or does it make no difference ?
yes it should have power from the cradle or the power connetor
Thanks
I am downloading another rom will try again.
Kind regards
Hi
I have just downloaded a new rom and written to sd with xdarit, flashed and received following message again.
"CHECKSUM is not correct"
Could this have anything to do with the formatting of the sd card?
Anyone have any more suggestions
Kind regards
should not as far as i know iso tool should give the sdcard it's own format which only the xda can read
and of cause the sd card have to be 64MB or over a 32MB card will not do
Hi
I am using 64Mb SD cards.
Just failed again, here's what I did.
Downloaded ROM, copied it to SD with axdrit, message "xdarit successfully copied image of 65026 blocks.
Inserted card into xda, got :-
Wallaby Bootloader v5.15 GSM OK screen then:-
SD Download
Card Type:
CE OS
Press Action to Download or REC to Exit.
Pressed action and got:-
Please wait for download
PRG 00000000
END 02000000
"Flash Writing"
Followed by :-
Download completed
CheskSum is not correct
COLD BOOT TO RESET
What is going wrong?
is that a problem? i remember getting the checksum is not correct problem as well in the end. but after cold reset, the device worked fine. or so it seems to. should i be worried?
Related
My PC's activesync crashed and hanged while flashing the ROM. Now the xda is stuck with Updating screen.
Can someone please tell me which file to download from Jeff's kitchen (nk.nb1 or nk.nbf or anything else) and how to write it to SD card for flashing.
I tried to write nb1 and nbf both, using xda-tools, but it is not copied in the format required by the bootloader. In fact, in either case it is copied as a file which is not identified by the bootloader (my version is 5.15). boootloader starts with GSM OK message, and does not give me option to flash the ROM.
Can someone please please tell me how to do it?
you need SD card writer or a SD backup from another XDA.
cgigate said:
you need SD card writer or a SD backup from another XDA.
Click to expand...
Click to collapse
Thanks.
I was about to go to the service centre for rom image from another xda, but I decided to give it a try using usb cradle, and ran the original upgrade program. It came out with error and asked me to soft reset the device and try again, which I did, and it worked. I now have a working xda!
hi,
well i tried to upgrade my xda1 to windows 2003,
here is the description of the problem i m facing....
i used xda tools(osimage tool) to transfer nk.nbf file to my sd card-> go into bootloader(wallaby bootloader 5.17)
->says gsm ok and starts taking test(like tap test, recording test, sd card test etc) which it should not...
and is not loading the os software. (getting stuck in one of the test like sd card test)
well following things i tried:
1. transfered nk.nbf file, tried both from siemens site as well as from yorche.net site--->both giving same problem.------->using xdatools.
2. tried loading the sd ,tried both destinations -->xda slot and as well as the card reader.
3. using drop down only to choose the destination.
4. also after loading sd the current rom asks to format (which means sd is loaded properly)
5. initially it was not loading the bootloader then i fixed it using xda tools , after that i started getting wallaby bootloader 5.17
6. now after going to bootloader it starts taking various test and shows no sign of loading the new os.
--------------
now i have moved as per the instruction and tried everything mentioned above to install wk3 but all in vain....
dont know where the problem seems to lie....
need suggestions desperately...
--------------
current rom:3.17.03
stack:4.21
--------------
current rom working ok.
--------------
maybe it's a problem with the nbf file content ... did u try burning the nbf file directly to the ROM using the XDAtools ?
You arent hitting any other button when entering bootloader are you? Just press the stylus in reset while holding power, it shouldnt go into test mode unless another button is pushed, maybe you have a button stuck or something.
any more suggestions............
well if burning means choosing source to nk.nbf and destination to drop down
to sd card using xda tools then yes i did burning....
also i m sure no other buttons are pressed or thing like that....
any more suggestions............
I meant by burning to make the destination to be the XDA flash ROM
any more..
ya i tried burning to.,...
same problem.
can your sdcard reader read whats on the sdcard (it's not suppose to be able to read after it's been flashed with the rom)
also are you 100% sure that your nbf file is valid ? maybe it's broken
more suggestions ....
well after loading sd card , i cant browse to read it, moreover xda asks to format, which is the sign that card is loaded ok.
secondly i have tried nk.nbf file from siemens as well as yorche.net,
both should not give same problem, which it is.
this mention the 5.17 bootloader you should read it
http://wiki.xda-developers.com/wiki/WallabyBootloader
Rudegar said:
this mention the 5.17 bootloader you should read it
http://wiki.xda-developers.com/wiki/WallabyBootloader
Click to expand...
Click to collapse
The best way that I've found is to find somebody with a XDA that has the 5.15 bootloader then do a CE+BOOT TO SD then do a SD restore.
Sounds like a good project for some of the ROM Kitchen owners doesn't! :wink:
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..
:evil:
Hi everyone,
am deperately needing your advice!!!
Just yesterday I rechieved an exchange mdac from tmobile showing serial version v1.02 when put in bootloader mode(previously v1.01).
When trying to flash whatever rom once transferred via ntrw to my sd card, my mdac does simply nothing but stay in bootloader showing serial v1.02. No flashing like in my old one starts.
On removing the sd card it comes out freshly formatted, before it definately was formatted with raw as usual once working with ntrw.
Result : I can not upgrade my system to mksbigstorage or any other rom like i could with my" old one". (same sd card!!!)
Tried downgrading to an older rom version via original upgrade routine and from there flashing via sd card: same problem!, tried other sd card: no solution either!
Any ideas, solutions, people with the same problems?
:?:
Appreciate your help
Thanx
romflashing
Seems to have nothing to do with flashing routine.
Card simply gets formatted once inserted.
Any way to stop this?
Hi! I have had many problems after flashing and re-flashing my rom.
Try boot loader mode and USB then execute (from your PC)MaupgradeUT_noid with a Shipped_rom on XDA ftp. It may work.
Have a look at this link: http://www.mtekk.com.au/forums/viewtopic.php?p=32876
Regards
Try to write SD card with winhex not ntrw. Simply choose open disc feature and write file directly do SD it works every time for me (with ntrw it was roulette). I have 1.02 bootloader
Thanks Shamus but can you explain in details how do you do this with Winhex? my bootloader is 1.00
SPV_M500, ROM 1.12.02 FRE
RADIO 1.12.10
EXTRom no more