Probs flashing any rom via ntrw with my NEW mdacompact - JAM, MDA Compact, S100 General

: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

Related

Bootloader 5.22 to 5.15

I have a 5.22 Bootloader and wondering how to back it up before downgrading to 5.15 from Jeff's tools.
Thanks. !
I tried with the XDATools but does not give option for Bootloader only ROM!
we made xdatools as safe as possible, no option to screw around with bootloaders.
I did create some other tools that you can use to backup your bootloader.
if you download these tools http://www.xs4all.nl/~itsme/projects/xda/tools.html
and run
Code:
pmemdump 0x80000000 0x40000 bootloader.nb0
that will save your bootloader in bootloader.nb0.
or you can use this pocketpc tool: http://www.xs4all.nl/~itsme/download/savebootloader.exe
it runs on your xda, and save your bootloader to a file in the root of your xda
Great thanks this works fine.... but when I run
pnewbootloader bootloader_v5_15.nb0 I get
Unable to find flash info offset, cannot disable bootloader writeprotect
I wish to upgrade to rom 4.0.x but would like to have a 5.15 wallaby before doing so. In case I need to downgrade back to 3.17.
Any help appreciated. Thanks. !
If their is no solution to this... Can I upgrade to 4.0.x and still be able to downgrade again later using another method!.
Hello,
this is the same error message I got when I tried to downgrade bootloader from 5.22 to 5.15. I was not sure if I am doing something wrong or what. I hope there is a fix to this.
Is the problem the Rom version or is it the 5.22 issue?
Use the old xdarit which gives an option to create a boot flash card. I have used this but as the developers warn this will "brick" your XDA if it goes wrong. My guess would be that you can downgrade to 3.17 on a 5.22 bootloader anyway. My advise would be to try that first because if it works theres no point in risking your bootloader and if it doesn't work you only have to reflash a 4.x image or try the old xdarit.
Richard
Thx for the reply, but the issue is how to downgrade to 3.17?
Program A is not working with this bootloader version (5.22) and I am not sure if XDArit will work with it.
Has anyone used XDArit with bootloader 5.22?
Perhaps I didn't make myself clear. I have bootloader 5.22 and have loaded 4.x images via flash using xdarit. I have also re-loaded bootloader 5.15 using the old xdarit to write a bootloader file.
Richard
Many thx Richard,
I do have an SD card reader (6 in 1) and I am not sure if this is the reason for the many errors I am getting when I try to use it. Recently posted posts say it could be.
I have also an image for the 5.15 bootloader.
Do I need the SD card reader to do the bootloader downgrade?
I have a six in one card reader and have the same problem you and many others have. In my case my SD card reader is disk six but I have to select disc 5 to get xdarit to see it. The bit to watch out for is to make sure that in selecting another disk it doesn't pick up your hard drive. The best way to be sure is to use the rom image tool to write a an image to your disk. Then using the old xdarit from the strat screen use the drop down list for the drives and you will see a load of data apear when you hit a valid drive you can recognise you have the right disk because you will see "Wallaby HTC" or simmilar. Then select write to disk and select 3.5k header and your 5.15 bootloader and write the file. when you put this disk in your XDA and enter bootloader mode it will offer to write it for you.
As I have said before I think you should try to write a 3.17 image to the disk first and try that. At the end of the day a corrupted rom is easy to recover from a corrupted bootloader = brick.
Also I have no problem with Program A and bootloader 5.22
Richard
No luck till now
Not sure what happened so far but I am unable to use my card reader now. Even when I connect it to a different laptop and insert an SD card from my camera, it says the card needs to be formated and even when I say ok format it, it says can't format.
When you right to the SD card using XDArit, my understanding that it will generate a file taht has the header required for bootloaders greater than 5.15. I am now ONLy trying to downgrade the bootloader. SO, the created file should be small. If you make this file available, would it be then easy to copy and pase it to a different SD card without using any tools?
Thanking yoy for your pateince
When you put your card in the SD card reader it is Windows that is offering to format it. xdarit does not need the card to be formated. If you put the card in and open xdarit can you see a string of data in the box ? If not use the drop down menu and try a different drive.
You can't (to the best of my knowledge) create a file that can be copied direct to the card because of the header required. i.e i can't email you one.
If you are having no joy reading from the card i.e you can't see the data as above try a different card perhaps the one you are using is duff.
Richard
It seems my card reader now has a problem.
I got an SD backup from an XDA that has bootloader 5.15 and the Rom CE
Now my Boatloader is 5.22 but this is what I am trying to get rid from. So, when I insert it in my device, it asks me if I want to press the action item to boot from SD. I am afraid that this will screw up my machine!
Is there a need that this file be written to the PC first then moved again to the SD card after checking the higher than 3.15 boatloader box?
Regards
If the backup you took was just the CE image then go ahead and restore the image. If you took a CE+bootloader image then you may want to transfer to your desktop and reload just the CE image but if your card reader is down I guess you can't do that. So if you have access to another XDA just redo a backup making sure you just have the CE image.
Why are you so determined to loose the 5.22 bootloader ? if it works on a 3.x image just leave it there its not doing any harm. If you are really nervous I will try a 3.x image on my XDA with 5.22 and let you know before you try on yours.
Let me know soon I live in Australia and its Friday night and the pub is calling.
Richard
You bet that I am nervous.
I would greatly appreciate your help in trying this first.
You can also e-mail me at [email protected]
Regards
I did try it and the Rom is downgraded now.
I still need to downgrade the bootloader so I can use XDAtools easily.
Will the same method work if I backup both the Win CE and Boot?
You don't need to HONHESTLY all the tools work fine on 5.22 BELEIVE me
If you must then yes is the simple answer but there is always a risk that it will go wrong and screw your XDA
Richard
Off to the pub now
OK got it all figured out!
I had:
A Rogers ATT (Canadian phone) running the Rogers ATT ROM.
Rom: R.20.x (don't remember) probably a 3.x
Radio Version: A.20.10
Bootloader: 5.22
Here are my steps. I will skip everything that went wrong on my journey and go straight to the point.
First I tried to use the new XDATools to upgrade the rom via Program A but with no sucess so used on method. !
NOTE: Their is not need in Canada to upgrade radio version cause the phone is already shipped with the latest. !
1- Used the old version of XDArit 1.0 to burn Wallaby Bootloader 5.15 from JEff's tools on my SD card (32Mb) with a Dazzle SD card reader
2- Inserted the card in my XDA and started the actual bootloader 5.22 and pressed action to download boot image.
3- Used XDATools (New version/product) to burn the SN40016wwe_vs.bin (see 4.0.16 rom is here post). (XDARit failed to get that one on the SD).
3- Inserted the card in my XDA and started the actual bootloader NOW 5.15 and pressed action to download CE image.
4- Did a soft reset and got T Mobile prompt... !
5- That's it phone works A1. !
Thanks for the info Yanick
So now u have 5.15?
What is SN40016wwe_vs.bin and where to get it from?
Is it specific to the ROm version you are upgrading to?
Hello,
I have to say I am kinda of lost now (not unusal :lol: )
I was thinking that the problem is in the boatloader but when I followed your method, my XDA seems to run 5.15 now.
Why an I still unable to use the XDAtools to write a new Rom file?
When I try to, I go as far as seeing upgrading in the laptop and on the XDA screem but then the connection (I use USB) is lost between the laptop and the XDA
When I try to upgrade the RSU (an excutable file), it goes as far as downloading the file to my XDA and restarting it to get a button saying start on my xda screen. When I press it I get the error message saying "als Failed " after 1% downloading?
If it is not the bootloader that was the problem, what is it?
Or am I having a non 100% functional bootloader now (5.15) or what?
:shock:
OK so you are running Bootloader 5.15...
Now download 4.0.16 ROM CE from
refer to this topic for download
http://xda-developers.com/forum/viewtopic.php?t=2354
Then Use XDATools to burn image on a 64MB or greater SD card. Then Reset your PDA using (RESET + POWER) combination with the SD card already in the machine and it should prompt you to download CE .. Press Action and here you go !

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

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 to get a Wallaby to read the rom from the SD Card!

problem: radio stack upgrade failed (using the siemens upgrade) and now I get a GSM error and eventually a partial pocket pc desktop with no start menu or access to an explorer window.
OK, I used XDA tools to copy the rom to the SD card (1GB card), inserted in the Wallaby, held the power and soft reset the device, I get the boot loader v5.15 and then a GSM Error. From there, nothing. Any suggestions as to what I am doing wrong? Does the SD card need additional files or should it be formatted a certain way? Any help would be greatly appreciated.
No additonal files are required. Thr progress you describe is the normal....
Are you using an internal SD-Card Writer? They make often problems.
YOu can try dumping your old ROM to SD and check if it will work with this backup. If this is the case the problem is your Card writer.....
Instructions to do this could be found here:
http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_FlashSD2
Fixing GSM error could be found here:
http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_GSMError
Stefan
Siemens SX56 Upgrade Issue GSM Error - Upgrade failed
so I should try using a different card writer? If so, I have an external one that I can try. Should the boot loader still show the GSM Error with the rom on the SD card?

How to flash ROM from Bootloader?

Hi all,
I have some trouble. I tried to flash new ROM from romkitchen.de, but there was an error on 98%. Now the mda, starts to bootloader (wallaby bootloader v5.15). I don't know what to do now. I found this> http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_FlashSD , So I cooked rom (NK.nb1) and via osimagetool it wrote to SD (is it same like ctrl c + ctrl v ?). But when mda starts, nothing happens - onlz bootloader starts. What's wrong?
thanks for your answers and sorry for my english
you can check if you did it correct by putting the sd card in the pc
if it's containing a rom the pc cant even read the card
if the card have a rom it should flash automaticly when you enter bootloader
it's incorrect. I don't know how to dwrite rom to sd...What format of ram (.nb1 , .nbf) can be written to sd by osimage?
one choose the sdcard reader as distination
and osi should be able to work with both nb1 and nbf
well...but sd card still can be read in pc. SD i ve god sd reader in my ntb... :/
where did you get the nb1 or nbf ?
only wallaby roms will work
yes, i know it. rom is from romkitchen.de
What for Cardreader are you using? Internal devices often causes problems....
If you have another person that has a wallaby you could backup his rom on the sd-card and install it on your device....
The ROM in nb1 or nbf have to be written via osimagetool. I is written in special format and it is complete different from ctrl + c -> ctrl +v.....
Stefan
i use cardreader in my notebook asus a9n. I'll try it on another pc

Categories

Resources