Database Info

Struck by an MDA brick!!

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

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

I think I fired the MDA
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.?...

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.

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

hey just got back the bootloader screen...

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?

Its showing Serial v1.00...after the reset.
Its been on the USB chatge all along.....

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.

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.

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.

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.

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!

The masupgrateut is throwing up a ruu.dll error?...you seen that one before?

What sort of error? Not found?

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?

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

ran the program multiple times...still getting the COuntry ID error...

Are you running this program? MaUpgradeUt_noID.exe
...with the change in the RUU.conf file?

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.

After rom update some of the programs are not installed

I have a qtek9000 and a 2gb sandisk sd card. i downloaded
http://vidmes.com//Uni/ROMs/BeastyLeo/2.07.04.BL/Vanilla.rar
and installed it with no problems, system rebooted (before reboot i inserted sd card in) and started installing some cabs and finally rebooted once more.
My problem:
after startup i have this error message ""sddaemon cannot be opened. Either it is not signed with a trusted certificate or one of it's componets cannot be found. You might need to reinstall or restore this file"
and when i check programs i see there are programs that are installed but the icons are blank, and they wont launch.. i also tried rom ranju, same thing...
What am i doing wrong? I serached but i couldnt find any links, if it is posted somewhere, can u please send me a link at least
thnx

RE:
Did you unlocked your mobile, goto the sticky note on WM6 that tells you how to unlock your phone first
for the sddaemon message, goto \windows\startup
yo will find a shortcut for sddaemon, just remove it
Thanks

swunk said:
I have a qtek9000 and a 2gb sandisk sd card. i downloaded
http://vidmes.com//Uni/ROMs/BeastyLeo/2.07.04.BL/Vanilla.rar
and installed it with no problems, system rebooted (before reboot i inserted sd card in) and started installing some cabs and finally rebooted once more.
My problem:
after startup i have this error message ""sddaemon cannot be opened. Either it is not signed with a trusted certificate or one of it's componets cannot be found. You might need to reinstall or restore this file"
and when i check programs i see there are programs that are installed but the icons are blank, and they wont launch.. i also tried rom ranju, same thing...
What am i doing wrong? I serached but i couldnt find any links, if it is posted somewhere, can u please send me a link at least
thnx
Click to expand...
Click to collapse
Hi,
Sounds to me as though you have not cleared your storage after having flashed the roms...... did u hold the two soft keys on the keyboard whilst pressing the reset button and then selecting 0 to clear the storage.
Failing that I wouls use MTTY to restore your DOC.

@mehegazy: if my device is locked how did i install wm6 at all? i can install wm6 and wm5 without a problem, and i can install programs manually...works perfect. problem seems to be with specific roms that install programs automated at startup.. Also removing the shortcut from the startup actually doesn't resolve the problem, cause that means that program is not working...
@beast0898: i ve cleared the storage, that can't be the problem..
Funny thing is, after reboot it installs some programs and resets without a problem. But i see that some programs are installed and some of them has blank icons that do not launch..
Also is there a wm6 rom that actually modified for the best performance of system + without apps?
thanks all for helping

Issues loading WM6 rom

I've tried installing the file using the bootloader method countless times now and every time I get a coloured screen with "Serial" at the bottom and some text up the top.
I've tried the card as it was when I got it, Tried it formatted FAT32 with windows, tried it formatted with Resco on the device, etc. It's definitely FAT32.
When I open any of the 3 .exe files from Palm in winzip or winrar there are two .nbh files (CHEEIMG.nbh and CHEEIMG_FW.nbh) one is ~263kb and one is ~85MB.
From everything I have read so far I ignore the correctly named small one (CHEEIMG.nbh) and copy the big one (CHEEIMG_FW.nbh) to the SD card - once thats done I rename it to CHEEIMG.nbh and I should be good to go - start the bootloader and it should work but it's just not happening.
Am I missing something? I just can't get it to work. I've tried the 3, vodafone and generic (ROW) files.
Any help would be greatly appreciated.
EDIT:
I'm currently running TREO750-1.15-ROW
Firmware: 1.27.3b.00
Cheers

As far as I understand all this you have to run Hard-SPL first, otherwise your device won't load "foreign" roms.

hmm ok I'll try that but since it's a ROW to ROW update I thought it's not a foreign ROM?

-MM- said:
As far as I understand all this you have to run Hard-SPL first, otherwise your device won't load "foreign" roms.
Click to expand...
Click to collapse
I think you can flash all official and leaked without Hard-SPL... It's needed for cooked roms.

surely I shouldn't need it for the bootloader method?
Anyone got any ideas that may help me upgrade?

Kaiser Rom downgrade

Hello,
well I have an HTC Kaiser and upgraded it to WM 6.1. However, now I'm experiencing some serious software incompatibility issues. So now I'd really like to downgrade to WM 6 again. I downloaded a German WM 6 custom RUU file with the WM 6.0 ROM, however that didn't work. Could anyone *please* provide some instructions on how to downgrade the device to WM 6 again? Thanks!!!
Robin24

robin24 said:
Hello,
well I have an HTC Kaiser and upgraded it to WM 6.1. However, now I'm experiencing some serious software incompatibility issues. So now I'd really like to downgrade to WM 6 again. I downloaded a German WM 6 custom RUU file with the WM 6.0 ROM, however that didn't work. Could anyone *please* provide some instructions on how to downgrade the device to WM 6 again? Thanks!!!
Robin24
Click to expand...
Click to collapse
Use the search button before posting Bub.
Everything about that was already said.

What "didn't work" with the ROM downgrade? I was able to downgrade to Windows Mobile 6 perfectly

People get confused because they think of it as an upgrade/downgrade. Merely flash a WM6.0 rom as you normally would.

Hi,
first, I wasn't able to find anything usefull with the search function, all the threads I found rever me to the wiki where I can't find anything usefull, lots of information about ROM up and downgrades, but nothing straightforward really.
Second, the RUU program starts the downgrade process and can read the build information on my device, but fails to downgrade and offers me some recovery tips. I hard reset the device, no success...
Robin24

robin24 said:
Hi,
first, I wasn't able to find anything usefull with the search function, all the threads I found rever me to the wiki where I can't find anything usefull, lots of information about ROM up and downgrades, but nothing straightforward really.
Second, the RUU program starts the downgrade process and can read the build information on my device, but fails to downgrade and offers me some recovery tips. I hard reset the device, no success...
Robin24
Click to expand...
Click to collapse
Try flashing the ROM with the Micro SD Card
Instructions
1. Get a MicroSD card that is formatted as Fat32. The card must be formatted as Fat32 otherwise it will not work. It doesn't need to be blank or freshly formatted (but it wont hurt if it is). An easy way to check if youre MicroSD are Fat32 is to use Pocket Mechanic and check "Card Information", Pocket Mechanic are licensed but trial are free.
2. Find the ROM image you would like to use, normally named RUU_Signed.nbh, and rename it to "KAISIMG.nbh". Depending on the source of your ROM file, it may not be named RUU_Signed.nbh, but just rename the nbh file you obtained to KAISIMG.nbh
3. Copy the file KAISIMG.nbh to the root of your microSD card
4. Plug the card into the phone, then enter boot loader mode by pressing down the Camera button, then using the stylus, press and hold the RESET button at the bottom of the phone. Release both buttons once the bootloader screen appears. (Kaiser Resets)
5. You will first see a tri-color screen then the information on the card. Press power button to start flashing.
6. After all these are done, press the reset button located at the bottom of the phone to reset the device.
All this information it's on the wiki

Hi,
thanks for this guide. I found it in the Wiki before, but didn't know where to get an NBH file from. However, I just found one in the custom RUU folder I downloaded. I renamed it to KAISIMG.nbh and copied it to the storage card. I'm not sure about how it is formated as I can't access the PDA to check, but I think these cards come formated as FAT32 by default and I didn't change anything there. When I reset the device while holding the camera button, it shows me some info about the KAISIMG file I think. However, when I press the power button nothing happens. Any ideas? Thanks!
Robin24

QWERTZ bug in danger spl?

Hi, i stumbled upon a problem which noone else seems to notice.
I appplied the danger spl to gain more space for my apps.
Since then im using a qwerty keyboard layout instead of qwertz. Y is replaced with z, umlauts are broken, etc. Took me a while to find out its the spl. First i thought its the rom but the only way to get it fixed was to roll back to hard spl. i have two questions about this: wth has the spl to do with the keyboard layout and is there a way to edit keymap files in /system or something to workaround the problem? Strangely the usual keymap settings there dont seem to do the trick.

You usually need to do a wipe after you apply a new SPL

may i suggest using apps2sd for more space for apps. danger spl is only used to allow larger roms to be flashed.

sHR00m said:
Hi, i stumbled upon a problem which noone else seems to notice.
I appplied the danger spl to gain more space for my apps.
Since then im using a qwerty keyboard layout instead of qwertz. Y is replaced with z, umlauts are broken, etc. Took me a while to find out its the spl. First i thought its the rom but the only way to get it fixed was to roll back to hard spl. i have two questions about this: wth has the spl to do with the keyboard layout and is there a way to edit keymap files in /system or something to workaround the problem? Strangely the usual keymap settings there dont seem to do the trick.
Click to expand...
Click to collapse
Well, i have the same problem. How can i change the layout?

The problems does indeed lie within the "Danger" SPL. But you only need to change the keychars file. No need to switch to another SPL, or install some apps2sd gibberish.
http://www.mediafire.com/?tdnna5atnzn
Download the file and move it into the tools folder of your SDK. Now use adb to push the file to the device.
ex.
Code:
adb remount
adb push trout-keypad-v3.kcm.bin system/usr/keychars/
adb reboot
Done.

shane, of course i did a wipe before
joe, im aware that i can store apps on sd, but i simply dont have a class6 card atm and the danger spl worked fine except for this phenomenon. also i wanted to try a hero rom, which was the first reason to flash it. but since it gives me a double sized data partition, why dont use it anyway? hell even the browser temp files can fill that partition quickly..
ah thanks bavilo. i think i tried that before but maybe i did something wrong
edit: YEP ITS WORKING, thanks! =)