Problem occured during ROM upgrade. - MDA, XDA, 1010 Software Upgrading

Hi all.
When I was upgrading my ROM (using LumpiStefans ROM kitchen). Unfortunatelly, some problem occured and now, all I can see is the progress bar that appeared during upgrading.
I've read a lot of topics on the forum, but I didn't find a complete solution on this topic.
I've read that I should boot from SD card. But I couldn't find a description on how to do it. Where do I get the image to do it? I have 64 MB SD card from my camera. Can I just copy file(s) on the card using regular Windows interface (thru camera cable) or do I need specific SD card reader/writer?
I have MDA from Era (Poland).
I appreciate any help.

http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_FlashSD
Stefan

Thanks a lot, for this link.
I've downloaded XDA Developers v12 ROM.
In it I found a file NK.nbf, judging by it's size (32MB) this is the image I'm looking for. Your ROM distributions also have the same file.
Can I use this file, or should I get a proper image somewhere else?
Thanks for the help

This image is well....
Please do not use an internal Card-reader/writer. They make often problems...
Stefan

It worked!!!!
Thanks SO much.

Related

Xdarit doesn't write with new .nbf files ?

I use the Xdarit to read & write the Rom image from my MDA.
I managed to read from the SD card and stored on my harddisk.
When I create back with a new rom .nbf files to the SD card and read back again to the harddisk, the SD show the original files size that from my MDA not the one that I'm going to upgrade to ? I rename the files to .nb1 extension.
Do I need to reformat the SD Card ? Do I need a new SD Card for the download ?
Dear XDA developer #..., please advice. I have been posting and yet to get some good advice and replies.
I would appreciate very much of your expertise in this matter.
Thanks again
they should be the same size, nb1, and nb0 files always are fixed size
more answer:
- when using xdarit you never have to format sd cards.
- renaming files will probably confuse XDARit, since this
is how xdarit recognizes what kind of file it has.
What I meant original file sizes.
1. Read from SD Card ( backup from MDA )
bootloader 5-15.nb0 256 K
WindowsCE 5-15.nb1 32,512 K
2. Write to SD Card ( with new ruu extract from O2 ie )
bootloader 5-15.nb0 256 K
WindowsCE NK_Wallaby31413wee_O2_Fulll.nbf 31,745 K
3. Read back the backup step 2.
bootloader 5-15v1.nb0 256 K
WindowsCE 5-15v1.nb1 32,512 K
As you mentioned, the files size are fixed, therefore my files of
the 5-15v1.nb1 should have the content of the NK-Wallaby.....
and I should had leave the file extention as .nbf without rename it to .nb1
Or should i had wite back using the step 1 files name ?
Please advice, many thanks
if you rename an .nbf file to .nb1, you will burn an incorrect os image
to your xda. making it unbootable in OS mode.
( your bootloader will still work )
also, be careful updating your bootloader, if it fails somehow
it is very difficult to restore your xda
if you just want to update your OS, only write the ..nb1 file
or select the .nbf from your distribution, without renaming it.
this http://openwince.sourceforge.net/jtag/iPAQ-3600/ might
give you an impression on what you would have to do, to repair
your xda after you've trashed your bootloader
Bootloader still appear but buttons not working ?
Thanks XDA developers,
My case is that I might accidently overwrite the bootloader.
The bootloader still be able to appear and the GSM OK showed but none of the functions button be able to work.
Do you think there is a way to work around ?
Many thanks for your replies
can u tell about bootloader version?
Bootloader v 5.15 on a T-Mobile MDA with 3.13.12 GER & Radio T310.
i think u can try to make sd card that contain wallaby path (.nb2) using xdarit... logically u can access "action button" to flash the rom.... this is only way to activate "action button"
after insert sd card u can go on bootloader and see wallaby path, press action button, if it work u can flash the rom (may be u should find exact rom that installed before xda died, more work?)
hope u can fix this prob
regards
Hello All,
I can't write new ROM image to SD card with XDArit: I can read image from card, but when I try write new ROM image, I get "Failed to open device \\Physical device12" error message. I try both USB and PCMCIA card readers, but don’t work… What is the problem? (My PC is an Asus P4 notebook with WinXP Pro)
Thx your help & sorry my bad English
Hanzy
try to change device "mass storage device" with driver from manufacture, use one of xdarit executable 180kb or 1.39mb (find out in other thread)
Hello,
I install manufacturer's drivers, but isn't work
I download (found) only 180kb version of XDArit (and source code, but my C++ knowledge... khm...)
Can you write the 1,3mb version's link from me?
Thx
from http://xda-developers.com/forum/viewtopic.php?t=1094&highlight=xdarit
found this link, try it
http://givemebeer.com:8080/warez/XDA/xdarit.exe
Hi,
thx your help...
I read on another thread, XDArit work only with USB 1.1 ports... My laptop have only USB 2.0 ports... :roll: I changed my laptop with one old IBM Thinkpad and XDArit work correctly...
Regadrs & thanks
Hanzy
Not really, coz im using usb 2.0 and its work normally
I only have USB 2.0 ports too and it worked fine.
fastblazer said:
try to change device "mass storage device" with driver from manufacture, use one of xdarit executable 180kb or 1.39mb (find out in other thread)
Click to expand...
Click to collapse
Just searching for why I couldn't get XDArit to work with my system - seems the larger (presumably debug) build of XDArit has what's needed to work with the v4 nbf's - thanks for the pointer!

Cannot copy rom image to SD card

Hi there, thanx again and again for your eccellent work!
I got into a heavy rain the other day and when I picked my toy from the waterproof compartement of my backback it was completely soaked! :shock:
And after a lot of fancy flashing and ringing, that I could only stop by hard resetting it, it went dead altogether.
Now it dried up again I'm kind of surprised to find it actually works again only it obviously lost all it's memory. And after honestly following every single thread and reading every post, I give up and finally post a question.
Used to be Rom 3.14 and Radio Stack 3.16.xx (I don't remember) all german O2. Bootloader 5.15.
My problem is, that whenever I try to get a rom image (the newest version of the german Programm A - which is an .nbf file after extracting)
onto my SD card (Scandisk 256 MB), it will stop immediately after I hit the OK Button in the XDArite App, outputting 'Successfully copied image of 65538 blocks'. Obviously it didn't because I figure it would need quite some minutes to copy 30 MB of data onto the SD card. And the bootloader doesn't recognise anything on the card.
In the beginning I could read the card under XP and could save all my data, but now after trying XDArit a couple of times I can't read the card anymore under XP (it still shows up as a removable Harddisk in the explorer but Windows can't even format the card anymore). :?
Does anybody have any suggestions on that matter, I would very much appreciate that!!
Have you recently downloaded the new version of XDArit? If so: be advised that there's now two other people that seem to be having problems they did not have on the first version. So you could try the old version, still around at http://xda-developers.com/XDArit/old
You may to also read the page for the warning on the old version.
(We created /old/ subdirs for all our software, by the way)
XDArit needs a rehaul, and we know it. We currently don't have much time, and this would be a good project for a coding volunteer. We have plenty of good ideas as to what should be in there.
Same problem, It doesn't actualy write to the card ?
Same problem... this is how I fixed it... the old version may work better for you (but I've never used it). http://www.xda-developers.com/forum/viewtopic.php?t=1451
Thanks for your reply, Ive requested assistance from the author of the post you suggest, but i`ll ask you the same question. Any chance of the recompiled file so that I could try it.
Many thanks in advance BORIS.

BIG PROBLEM ! I probably damage my SX56 upon his upgrade

Hey everyone. I have big problem and i need a help or somebody who can help me fix my problem. When i use XDA-developers-SER-v12 to upgrade my SX56 my PC freeze up and upgrade wasn't finish . Now i can see on my display only black and white line. Nothing more or less. PPC is not working with my PC
Anybody can help my or give me any adress i can send PPC to fixed (if it's possible) ? Or i don't know what can i do ........... :roll:
Thank for hepl !
sorry my english :?
You need to use sd card flashing method, your phone will be ok, just look around the forum look for sd card flashing.
BIG PROBLEM ! I probably damage my SX56 upon his upgrade
cruisin-thru said:
You need to use sd card flashing method, your phone will be ok, just look around the forum look for sd card flashing.
Click to expand...
Click to collapse
OK but how can i reflash my SX56 with SD cadr if I don't have any back up ?
plus everybody has bootloader 5.17 or older but my is 5.22 :-(
Hello,
you have 2 options both use SD card:
1. get ROM backup from any other working XDA.
2. get SD card reader/writer. change the extention of the ROM file you cooked to .zip and use winzip to extract a file named NK.nbf under \english directory. use the SD writer to copy this file to the SD card.
in both cases, insert the SD card into your XDA and use the bootloader.
good luck ...
similar problem last year
Hiya Mike2001,
I had a similar problem last year. I found that while the ActiveSync monitor shows no connectivity you will still be able to transfer an OS image. One hiccup I did find, and I am running wallaby 5.17 by the way, is a version conflict with the proposed rom and existing header information. This is a windows registry problem on your PC caused by the crash which needs to be deleted prior to attempting the upgrade.
Hope this helps,
Cheers,
David A. Booth

CHECKSUM does not match

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?

how works a bootloader(sd) image (SD > 64MB)

Hi all !
My Question ist, how the bootloader saves the image, if the used card is bigger than the rom? The image doesn't seam to be empty after the first 64Mbytes....
anybody knows something?
greetz MatteZ
The non-emptiness after 64MB is just the garbage what was present before dumping your rom.
You can check it by writing a specific pattern to your SD & then dump your rom.
Regards, M
after some testing i came to the same result^^
But, thanks for answering! I'm sure you wasn't the only one who knows this!
MatteZ
Probably most readers had a 'well that's obvious dude' experience.
I found out that some people on the board are really inexperienced with any kind of computers & can be helped with a small explanation.
Cheers, M
??? im not to good with my ppc, are you sayin that you can install ur rom on to an sd card??? if so, does his meen that there is the 64mb fre on the ppc storage?
if this is right, can u tell me how?
Unfortunately not. You can dump your rom on a SD-Card & save that to your hard-disk or what-ever. The magician won't boot from your SD in a way that you can free up your internal rom-memory. Man I wish it would.
You can supply a new rom to your magician in two ways: the first is with active sync and the second is via a rom-image on a sd-card. The bootloader will recognize the rom-image on the sd & start flashing it into it's internal rom memory.
So Mattezh question was about dumping his internal rom on a sd-card. If you do this & save the rom image on your PC the program to read the image from your sd will not know where the rom image ends. So it just copy every bit from your sd to your PC & that's why there's a lot of garbage in the saved image after the 64MB size of the image.
Understandable? I hope cause I know I sometimes tend to write a bit weird, I know

Categories

Resources