PDA

View Full Version : Struck by an MDA brick!!


suyesh
25th July 2005, 04:28 PM
Made a huge error.....didnt go through forums and read instructions before trying to Flash a German T-Mobile MDA Compact to a English ROM....

The device is completely dead....

Followed all the steps required to get it back up...It is refusing to do so though....

Used this thread:

http://forum.xda-developers.com/viewtopic.php?t=19500

One thing to note is that I am not using the AC charger, am using the USB cable to charge the phone.

Can someone please helpme...

Haven't got past the bootloader mode...

ppc4
25th July 2005, 05:48 PM
If you followed the instructions from the other thread, it should have started flashing.

Some things to check on:
1) Did you do a full d2s before you attempted the upgrade? It's always good to have something to fall back on.
2) If you can get to a bootloader screen, all is definitely not lost.
3) Sometimes, it takes 4 or 5 minutes for the "Press to flash" comes up on the screen so be patient with that.
4) Make sure you did exactly a 416 byte copy from the original rom file in to the new flash file.
5) You can only write an nb1 file from the pc AFTER it has been created from the pocket pc. If the SD card has been pc formatted, the nb1 file will write to it but the pocket pc won't recognize it and will just sit there at the bootloader screen.

HTH

suyesh
25th July 2005, 06:12 PM
Well I did not create the nbf file from the ppc, downloaded it from the the forum FTP. I do not have the backup of the nbf file. As I mentioned I did not read the forums before trying the update.

I just downloaded the T-Mobile ROM update and tried installing it. Obivousioly it didn't work, Game the dreaded the 112 error in the 3rd step.

Am not even getting the bootlader screen now..

Any ideas on how I can get this device up and running.?...

ppc4
25th July 2005, 06:17 PM
ok, need some clarification here. "What" are you trying to load (nbf files or nb1 files) and how are you trying to load them (SD flash or the standard USB based upgrade)?

Easy enough to check to see if your device can still get to bootload mode....hold the camera and power switches in at the same time and hit soft reset with your stylus. After letting go of those and you see either "Serial" or "USB" at the top of the screen, you should still be able to recover from this.

suyesh
25th July 2005, 06:23 PM
Tried with the nb1 files not nbf (sorry abt teh error)..

The bootloader screen was showing up ...unitll I tried the T-Mobile MDAcompact_vers11201

After the 112 error while updating...the device now refusing to get to the bootloader mode.

Have I fried the device and made it unusable....?

suyesh
25th July 2005, 06:24 PM
hey just got back the bootloader screen...

ppc4
25th July 2005, 06:26 PM
Take the SD card out, disconnect the USB and tell me what happens when you hold the power and camera buttons in at the same time, then hit the soft reset.

Also, has the unit been charged recently?

suyesh
25th July 2005, 06:29 PM
Its showing Serial v1.00...after the reset.

Its been on the USB chatge all along.....

ppc4
25th July 2005, 06:38 PM
Great. If you get Serial at the top, this can be recovered.

If you want a good T-Mobile 1.12 rom file, go here and use this one:
ftp://ftp.xda-developers.com/Uploads/Magician/tmobile-uk_wwe_ROM_1.12.00(thereapermanl).rar

Unpack it and follow all the procedures about copying the 416 bytes, rewriting the file, etc. from the other thread. I have tested this rom file and it installs ok.

suyesh
25th July 2005, 06:45 PM
Thanks for the encouraging words...

Will it work even if I do not have a backup of the original ROM on my machine?....I only have the tmobile.nb1 file which I got from the XDA forums.

Lemme try using that and editing it.

Thanks a ton for your help.

ppc4
25th July 2005, 06:50 PM
You might be a little stuck for an nb1 flash if you don't have an original flash back up but don't fear. You can go here and get this WWE1.12 file and just do a USB type upgrade:
ftp://ftp.xda-developers.com/Magician/Shipped_ROMS/WWE_11200_128_11210_ship.exe

I know this one works too. It's ROM 1.12, Radio 1.12 and Ext_ROM 1.12. When you try to run the upgrade program though, it might give you a Country ID error. If so, use the attached upgrade program instead. If this one gives you a Country ID error again, close the program and just run it again. I've been down all these roads already. :)

suyesh
25th July 2005, 06:58 PM
Lemme get this right this time: I will be doing the following

1. Install the ROM as you have mentioned. With the country id hack if necessary

2. Hopefully by now the device would be alive. If so will take a backup of the ROM on the SD card

3. From then on follow the instruction given in the doc.

Hope I get it righ this time else Its going to be a long night for me.


Lemme know if I have to do anything else.

ppc4
25th July 2005, 07:20 PM
Either ROM will work fine for you. It just depends on whether or not you want I-Mate stuff on it or T-Mobile stuff on it.

Doing the USB upgrade will put the I-Mate ROM on but after that, it should be working and you can then do an SD backup, follow the SD flashing procedures and get the T-Mobile ROM on.

Good Luck!

suyesh
25th July 2005, 07:28 PM
The masupgrateut is throwing up a ruu.dll error?...you seen that one before?

ppc4
25th July 2005, 07:38 PM
What sort of error? Not found?

suyesh
25th July 2005, 07:52 PM
yup...

I extracted the ROM exe and found teh file...copied it to the windows folder..and ran the no id program...no error this time round but the update is still giving a COuntry ID error...

Been looking at various posts...specially this one...
http://forum.xda-developers.com/viewtopic.php?t=14973

Thinks thats gonna help?

ppc4
25th July 2005, 07:59 PM
ok...two things.....just run it again. The no ID program sometimes does that on the first time 'round so just run it again.

Second, stick this at the end of the RUU.conf file:
[CHECKCEID_TYPE]=1

suyesh
25th July 2005, 08:18 PM
ran the program multiple times...still getting the COuntry ID error...

ppc4
25th July 2005, 08:32 PM
Are you running this program? MaUpgradeUt_noID.exe

...with the change in the RUU.conf file?

ppc4
25th July 2005, 08:34 PM
I just noticed something....did you extract all the files to a single directory and just run it from there or did you just pull a few out?

ALL the files have to be in the same directory. This is also where you need to execute the installer program.

suyesh
25th July 2005, 08:43 PM
well for starters somegood news....I was getting nowhere with the upgrade...

I tried a upgrade with the T-Mobile ROM again....and it worked...

The device is back and alive...

I guess now to change it to the english ROM I will have to follow the update path step by step....


Thanks a ton for everything.....Will let you know if I am successful in changing it to english....

suyesh
25th July 2005, 09:04 PM
Now SD card is bust!!...after the ROM backup..

Cant read it anymore on my machine..

well pain never ends..!! :wink:

ppc4
25th July 2005, 10:17 PM
Can only read a ROM backup on SD card through bootloader on pocket pc. If the pocket pc doesn't recognize that it's a flash ROM card, then it wasn't created correctly and the 416 bytes wasn't copied right.

mo-ca
29th March 2007, 03:06 PM
Hi,
Ive got the same problem with that "stuck in bootloader" thingy ....

the device is showing serial and if connected to usb, usb, but none of the flashing methods works. no flasher finds the device.

now the question: can i use the nk.nbf out of the genuine t-mobile package with ntrw for the SD-card-based romflash to debrick my mdac ?

thanks in advance

/edit: extra question: why is there a high-frequent sound coming out of the device, when it reads the sd card ?