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.

Error while loading ROM from CoreProKitchen... (not "HELP! I'M STUCK IN BOOTLOADER!")

Error while loading ROM from CoreProKitchen... (not "HELP! I'M STUCK IN BOOTLOADER!")
Okay, so I added my packages, etc and followed all the steps, everything worked up until the point where I flashed my phone. When it get's to 98% my computer pops up with the following error message:
-----------------------------------------
The instruction at "0x00405e9b" referenced memory at "0x0018a000". The memory could not be "written".
Click on OK to terminate the program
Click on CANCEL to debug the program
-----------------------------------------
I'm back up and running, but I would really like to use my rom. Any idea how to clear up this error and get this baby flashed?

inneyeseakay said:
Okay, so I added my packages, etc and followed all the steps, everything worked up until the point where I flashed my phone. When it get's to 98% my computer pops up with the following error message:
-----------------------------------------
The instruction at "0x00405e9b" referenced memory at "0x0018a000". The memory could not be "written".
Click on OK to terminate the program
Click on CANCEL to debug the program
-----------------------------------------
I'm back up and running, but I would really like to use my rom. Any idea how to clear up this error and get this baby flashed?
Click to expand...
Click to collapse
Mabe you put too many files in the ROM ... how big is the nk.nbf ?

The nk.nbf is 60,161KB... that's smaller than some of the other nk.nbf's I have seen.
Anything else it could be? Redid the whole process, flashing again...

For an OS only nbf the file should be around 57/58MB - sounds to me like you over filled the ROM.

On XP if you put your mouse over the nk.nbf and it shows its bigger than 57.3meg then you will not be able to flash it as its too big (thats for a rom with OS, and splash screens. If you don't have splash screens I think its like 57.1). The other way to check is right click and choose properties on the nk.nbf. Look at the size (not the on disk size).

Thanks... I guess I overstuffed it... I didn't think it had all that much in it... oh well.

inneyeseakay said:
Thanks... I guess I overstuffed it... I didn't think it had all that much in it... oh well.
Click to expand...
Click to collapse
Try to optimise some big executables. That will surely give you couple of spare MB

Up and running now!

-[Sticky] maybe - Flashing RUU Error/Solution & Explanation List-

I realize this information is on the HTC website but I have seen alot of questions lately regarding these errors. I decided that maybe, just maybe it might help someone with an error when flashing a rom, radio or splash and they can't quite figure out what the error is referring to. I also figured that this might lighten the load that GSLEON3 has been seeing lately with all of the "HELP, I think I BRICKED my phone" threads that keep popping up. Maybe it will help and maybe it won't but I thought it might be worth a try. I'd like to say thanks to OLI, Jocky, all of the rom cookers, GSLEON3 and XDA. You people make this fun.
I hope this helps someone.
? ERROR [202, 204] : CONNECTION
? This error message will appear when the device is not connected to ActiveSync correctly. Make sure
you properly connect the device to the PC through ActiveSync before running RUU.
? ERROR [206] : MEMORY ALLOCATION
? ERROR [280] : UPDATE ERROR
? When you see any of these error messages, close other running programs on the computer and run RUU again.
? ERROR [208] : FILE OPEN
? ERROR [210] : FILE READ
? These error messages indicate that RUU lacks certain important files and cannot continue with the update. Please get the complete RUU package again.
? ERROR [212] : FILE CREATE
? ERROR [214] : FILE WRITE
? ERROR [222, 224] : DEVICE NOT RESPONDING
? These error messages will appear when remote access control has failed. Check the ActiveSync connection and try running RUU again.
? ERROR [220] : MAIN BATTERY POWER
? This error message will appear when the device's battery power is not sufficient. Although RUU will instruct you to plug in the AC adapter, it still has to make sure that your device has enough power to upgrade the radio. (Even when you plug in the AC adapter, the device is unable to charge the battery
when it is upgrading the radio).
? ERROR [238] : FILE READ
? This error message may appear when, for some unknown reason, the ROM image on the Mobile Device is corrupt. Download the whole RUU and try again.
? ERROR [240] : FILE OPEN
? When this error message appears, check whether the downloaded image is placed in the directory of RUU. If, for some unknown reason, you find that the ROM image is not located in the RUU folder, you have to download the RUU and retry again. Check that the contents of the folder is a KaiserCustomRUU.exe file and an RUUSigned.nbh file. If you put the os-new.nb file in by mistake instead of the .nbh, this is the error that shows up. Thanks ConfusedSTU.
? ERROR [242] : INVALID LANGUAGE
? ERROR [244] : INVALID MODEL ID
? ERROR [294] : INVALID VENDER ID
? ERROR [296] : UPGRADE ONLY
? One of these error messages will appear when you use the wrong RUU to do the upgrade. RUU will check if the Model ID and Language ID are compatible with the device. Make sure you use the appropriate RUU tool to upgrade.
? ERROR [246] : DEVICE NOT RESPONDING
? This error message indicates that RUU cannot start the update process. Please contact your service provider for assistance.
? ERROR [260] : UPDATE ERROR
? This error occurs when there is an "open port error" before upgrading the CE ROM image. Solution: You can reset the device and run RUU again. If you still encounter an "OPEN PORT ERROR" again, reset your computer and try again.
? ERROR [262] : UPDATE ERROR
? This error occurs during the CE ROM code upgrade process.
Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue.
Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode.
? ERROR [300] : INVALID UPDATE TOOL
? This error message will appear when you use the incorrect RUU version to upgrade.
? ERROR [330] : ROM IMAGE ERROR
? This error message will appear when you use the incorrect RUU to upgrade and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version to upgrade.

Nice one mate, at leat this will give people who flash some idea what to do when or if they get errors flashing.

great find thanks for posting this will be useful for everyone.

Obligatory "thank you" post.

haha ok ok mistake now i see the solutions xD!

edit...............

Thanks P1T.
Just to put one in laymans terms from real life experience:
ERROR 240
Check that the contents of the folder is a KaiserCustomRUU.exe file and an RUUSigned.nbh file. If you put the os-new.nb file in by mistake instead of the .nbh, this is the error that shows up!!

I thought everyone knew that these error codes were included in the .doc files that come with shipped ROMs (and removed within custom_ruu.exe).
Guess not Great post P1tater!

Confused Stu said:
Thanks P1T.
Just to put one in laymans terms from real life experience:
ERROR 240
Check that the contents of the folder is a KaiserCustomRUU.exe file and an RUUSigned.nbh file. If you put the os-new.nb file in by mistake instead of the .nbh, this is the error that shows up!!
Click to expand...
Click to collapse
I'll add this to the post. Thanks Stu.
_Alex_ said:
I thought everyone knew that these error codes were included in the .doc files that come with shipped ROMs (and removed within custom_ruu.exe).
Guess not Great post P1tater!
Click to expand...
Click to collapse
I thought so to but I have had to answer a couple of these lately and was hoping that this might help to clear a few things up.

Bump (keeping it on the first page) & +1 for sticky
Oh, i would change the name to start with "Flash error codes" or at least include that in the title.

RPG0 said:
Bump (keeping it on the first page) & +1 for sticky
Oh, i would change the name to start with "Flash error codes" or at least include that in the title.
Click to expand...
Click to collapse
I can make that change.

Thanks for the info pal

helpful! thankx

Wiki
Ported to the Wiki
http://wiki.xda-developers.com/index.php?pagename=RUU_Errors
Ta
Dave

Thanks dude. Great work. You put a lot of effort in this kind of handy things.
Oh, by the way, do you have a social live?

iXiR said:
Thanks dude. Great work. You put a lot of effort in this kind of handy things.
Oh, by the way, do you have a social live?
Click to expand...
Click to collapse
I Can't speak for P1, but nope, I work, go home, play with my Son and either relax in front of the Telly or play on my PC.
Everynow and again on a weekend I'm forced into meeting something called friends by my better half
Dave

DaveShaw said:
I Can't speak for P1, but nope, I work, go home, play with my Son and either relax in front of the Telly or play on my PC.
Everynow and again on a weekend I'm forced into meeting something called friends by my better half
Dave
Click to expand...
Click to collapse
That's similar to my own schedule. P1 got to have a secret in finding time for this kind of things

ERROR 200
I got this error 200 "get newer update utility" I am using windows vista 32 bit.
where can i get a newer update utility? thanks

I-mate JasJam upgrade error
hey guys no matter what i do even if i do a reset on the phone and restart the computer i keep getting the 260 error when doing the rom upgrade. i am using windows 7 and have had no errors with anything ever with it.
Any ideas?
Josh

rumjar86 said:
hey guys no matter what i do even if i do a reset on the phone and restart the computer i keep getting the 260 error when doing the rom upgrade. i am using windows 7 and have had no errors with anything ever with it.
Any ideas?
Josh
Click to expand...
Click to collapse
Try resetting the phone and the computer to make sure that no other processes are running. Then try putting phone into bootloader, and when sync'd try flashing from there.

Upgrading to 6.1

Hi,
I'm sorry about this post but there seems to be an anormous amount of information which doesn't make a lot of sense to me.
All I want to do is upgrade my palm treo 750 from win5.0 to 6.1.
I've downloaded the rom but it doesn't upgarade. So I need to figure out a way to flash this phone so it can be upgraded to any roms.
I have tried the Cheetahunlocker which doens't work. It gets stuck on 0% then times out.
Could someone please give me some basic instructions on the best way to do this on the treo.
I've done this on the TYTN2 whith no issues however on this phone, it seems to be a lot harder.
Thanks in advance.

Your device needs to be unlocked. You can do this by calling ATT and getting unlock code or by using Magic_Unlocker.
search
Also you will need to have the HardSPL installed which is Step 1 only of the CheetahUnlocker
I just did it yesterday so I know it works.
After you get the phone unlocked, name the ROM .nbh file CHEEIMG.nbh and then put it on the SD card
The start the CheetahUnlocker process as it enters the HardSPL process it will go ahead and run the CHEEIMG file and flash your ROM
(it works ! ) DON"T CHANGE THE RADIO !!!!
After doing that be sure and reclaim your ROM space - search web for Removing Ext ROM and do that process, hard reset and you are ready to go
Takes about 15 min!

jcrompton said:
After you get the phone unlocked, name the ROM .nbh file CHEEIMG.nbh and then put it on the SD card
Click to expand...
Click to collapse
Thanks for your info.
sigh..
The rom is an exe file...
I downloaded 7-zip, extracted the rom to a folder.
Looking through it, I am unable find the ROM.nbh file!
CHEEMING.nbh is already there..
What am I doing wrong?
Thanks.

artii said:
Thanks for your info.
sigh..
The rom is an exe file...
I downloaded 7-zip, extracted the rom to a folder.
Looking through it, I am unable find the ROM.nbh file!
CHEEMING.nbh is already there..
What am I doing wrong?
Thanks.
Click to expand...
Click to collapse
Sorry I forgot it was already named CHEEIMG.nbh -- just use it like I said above.
Copy it to the SD card, put the SD card in the device and after you have used Magic_Unlocker , connect via Active Sync and start the CheetahUnlocker process. This will start the three step CheetahUnlock process (really all you need is step one which will put the HardSPL in place) as that process fails the CHEEIMG file on your SD card will get flashed.
Hope this makes sense
Bottom line is that you will be doing an SD flash of the CHEEIMG.nbh file but it takes HardSPL for that to work. Step one of the CheetahUnlocker installs HardSPL (that will be all you need of that process)

remember!
THE SD FLASHING METHOD TAKES A REALLY LONG TIME. SO LONG YOU MIGHT THINK IT'S BROKEN. BUT IT'S NOT!!!!
caps with bold and red= great way to emphasize an important point.

Thanks for the info but I'm still running into trouble.
I copied the file to the SDcard but when running the cheetahunlocker, it give the same error at 0% ( error 206) something about the connection..
I notice that active sync turns off when the cheetah unlocker goes to the coloured screen.
Edit:
Also, should I be moving the CHEEIMG.nbh or just copying it to the SD card?
Thanks.

artii said:
Thaks for the info but I'm still running into trouble.
I copied the file to the SDcard but when running the cheetahunlocker, it give the same error at 0% ( error 206) something about the connection..
I notice that active sync turns off when the cheetah unlocker goes to to the coloured screen.
Click to expand...
Click to collapse
Did you run the MagicUnlocker first?
Is the CHEEIMG.nbh file in the root of your SD card? Try re-formatiing your SD card (FAT32 important!) and then putting the CHEEIMG.nbh file in place on the root of the SD card.
After starting the CheetahUnlocker the TriColor screen should come on and then it should go to a standard White boot scan. It will ask if you want to flash and you will be asked to confirm by pushing the Power button.
If you can ever get Step One to complete on teh Cheetah Unlocker you should be able to confirm that the HardSPL is installed by turing off Today screen (Red, end button) , then hold the left side button while then pushing the reset button. You will get a tricolor screen that lists your SPL version. If it is HardSPL on an unlocked device and there is a CHEEIMG.nbh file on an inserted SD card it will then automatically go to a White boot screen .....
If any of this sounds foreign to you then you need to familiarize yourself in the Wiki re SD flashing
PS do you have the NetFramework 2.0 installed on your PC? When you start the CheetahUnlocker are you getting the Treo device confirmation to install the 2 boot exe files that let the Treo go to the boot screen (you have to answer yes to both of these) - are you making it that far?

Yes I ran the unlocker which worked fine.
I formatted the SD card, copied the CHEEMING.NBH to it so it's the only file there.
No I run the CheetahUnlocker.exe , yes to disclaimer , then STEP 1 - I click FLASH SPL, then next, next etc.. I hit Update - next - next then the phone msg comes up asking if I want to run jumpSPL.exe - I hit yes and it goes to the tri colour screen, the active sync dissapears, the screen on the pc stays at 0% and then I get the error 260: Connection, check cable etc..
How is it suppoed to maintain a connection when Active sync turns off?
I did check and framework2.0 is present.
Thanks.

artii said:
Yes I ran the unlocker which worked fine.
I formatted the SD card, copied the CHEEMING.NBH to it so it's the only file there.
No I run the CheetahUnlocker.exe , yes to disclaimer , then STEP 1 - I click FLASH SPL, then next, next etc.. I hit Update - next - next then the phone msg comes up asking if I want to run jumpSPL.exe - I hit yes and it goes to the tri colour screen, the active sync dissapears, the screen on the pc stays at 0% and then I get the error 260: Connection, check cable etc..
How is it suppoed to maintain a connection when Active sync turns off?
I did check and framework2.0 is present.
Thanks.
Click to expand...
Click to collapse
I'm not sure exactly what is happening in your case but I do know that once a device of any kind enters the bootloader - Active Sync dies - AS is part of the OS and that no longer exists after the bootloader starts, I.e. Windows Mobile isn't really running any longer. the AS connection just gets it started.

I'm not too sure either.
I've unlocked the phone which worked fine.
When I run the cheetahunlocker, it doensn't get past the first step.
Should I be running Hardspl first?

What rom works best with the Treo 750? Link please!!!
What rom are you wanting to use? I have Treo750_WM6.1_WWE_Lite, looking for a more stable rom. Please list some or link them.

I tried both roms
the lite one and the normal one. I must say that the normal one is more stable - with the lite I had to do a reset at least one per day. with the normal version I did not do a reset at all...

Hi, did you resolve this CONNECTION issue? I'm having exactly the same problem.
Anyone?

hey everyone... i have a problem similar to these i think. I'll explain
i've done the magic_unlocker and i can do the 1st step of the cheetahunlocker. treo reset automatically and when i try to flash the rom the trilinear screen doesn't change to the blue screen which is the screen of the rom flash
anybody now why?
i have cracked my head the hole day and a still can't do it :S

artii said:
Yes I ran the unlocker which worked fine.
I formatted the SD card, copied the CHEEMING.NBH to it so it's the only file there.
No I run the CheetahUnlocker.exe , yes to disclaimer , then STEP 1 - I click FLASH SPL, then next, next etc.. I hit Update - next - next then the phone msg comes up asking if I want to run jumpSPL.exe - I hit yes and it goes to the tri colour screen, the active sync dissapears, the screen on the pc stays at 0% and then I get the error 260: Connection, check cable etc..
How is it suppoed to maintain a connection when Active sync turns off?
I did check and framework2.0 is present.
Thanks.
Click to expand...
Click to collapse
If it goes into the bootloader then you should be good to go. Both 750s i unlocked did this. However, if done correctly, the phone should go to a light blue screen where you will press the power button and flashing should begin.

na1kkkk said:
hey everyone... i have a problem similar to these i think. I'll explain
i've done the magic_unlocker and i can do the 1st step of the cheetahunlocker. treo reset automatically and when i try to flash the rom the trilinear screen doesn't change to the blue screen which is the screen of the rom flash
anybody now why?
i have cracked my head the hole day and a still can't do it :S
Click to expand...
Click to collapse
Are you doing the SD method or Desktop? DO the SD method and it should begin flashing right away after the 1st step of cheetahunlocker.

A Problem after installing a ROM - RESCUE Options

A couple day ago I've installed a new ROM (Touch FLO Manila 2D) on my Herald using "FLASH CENTER". It has worked for some time, but after one rebooting the system didn't start any more - after turning on it appears a green screen for a pair seconds, then my Herald goes automatically down. And it repeats again and again... And it is not possible to restore the system though ActiveSync, because the Herald doesn't start at all.
I have looked through in this forum for possible rescue options. one of them seemed to be FLASHING FROM SD CARD. But this had no effect - a tricolor has appeared, but it happened nothing more. Probably there is possible to install a ROM this way on working WINDOWS MOBILE' s and not at broken.
I thought - may be it is possible to install a Windows Mobile on SD CARD (something like portable version) and so boot a system from SD Card ???
I hope you can help me.
Thanks.

radjapost said:
A couple day ago I've installed a new ROM (Touch FLO Manila 2D) on my Herald using "FLASH CENTER". It has worked for some time, but after one rebooting the system didn't start any more - after turning on it appears a green screen for a pair seconds, then my Herald goes automatically down. And it repeats again and again... And it is not possible to restore the system though ActiveSync, because the Herald doesn't start at all.
I have looked through in this forum for possible rescue options. one of them seemed to be FLASHING FROM SD CARD. But this had no effect - a tricolor has appeared, but it happened nothing more. Probably there is possible to install a ROM this way on working WINDOWS MOBILE' s and not at broken.
I thought - may be it is possible to install a Windows Mobile on SD CARD (something like portable version) and so boot a system from SD Card ???
I hope you can help me.
Thanks.
Click to expand...
Click to collapse
This is the wrong forum for this. I have written a few guides on how "unbrick" the Herald.
You can flash just fine from the tricolor screen. (That's where the phone takes you automatically when you flash "from" windows mobile.) So no worries, you aren't out of luck. Worse case scenario, you search for the GoldCard method if nothing else works.

Hello!
Thank you for your help.
You say, I am on right way with my "tricolor screen". But why doesn't happen anything? May be:
- should I just take another SD Card? My is 1 GB - is it OK, too big, too small?
- did I something wrong with "flashing" methods? I did it 2 ways:
- just with any ROM-File in NBH-Format, which was renamed to HERAIMG.NBH and placed alone to the formated SD Card
- in addition to HERAIMG.NBH also other files (like "EnterBootloader.exe"), which are often inclusive in ROM- ZIPs.
- I should be more patient and wait more than 1 hour with a hope that anything will change?
Could you give me the links for "unbricking" the Herald?
Thanks a lot.

You misunderstood me. You don't flash with the SD card through the tricolor screen. You flash through the regular flash center. If you're not hardSPL you have to flash the stock ROM.
As far as the flashing through SD goes, it should give you a countdown before the tricolor screen appears. If it doesn't, or if it's too fast to read, then your SD card is too slow.

As it loads this tricolor screen I see the following data:
IPL 1.08.0001
SPL 1.08.0001
Perhaps it means, that I indeed need a GOLDCARD method.
You don't flash with the SD card through the tricolor screen. You flash through the regular flash center.
Click to expand...
Click to collapse
But the FLASH CENTER works only on WINDOWS. So I can't use the regular flash center, because my Herald doesn't start up and ActiveSync doesn't see him.
If you're not hardSPL you have to flash the stock ROM.
Click to expand...
Click to collapse
Where do I get the original ROM, may be even WM5? In your FTP- server I have found some "ship.exe"- Files, but I can't extract ".nbh" files from them.
it should give you a countdown before the tricolor screen appears. If it doesn't, or if it's too fast to read, then your SD card is too slow.
Click to expand...
Click to collapse
May be that is the point!!! My SD is too slow. Will be in this case "GoldCard" an ideal solution for me?
Thanks.

radjapost said:
As it loads this tricolor screen I see the following data:
IPL 1.08.0001
SPL 1.08.0001
Perhaps it means, that I indeed need a GOLDCARD method.
Click to expand...
Click to collapse
This means that you attempted to flash a HardSPL or another SPL when your SPL did not meet the state requirements. You NEED to create a Goldcard.
radjapost said:
But the FLASH CENTER works only on WINDOWS. So I can't use the regular flash center, because my Herald doesn't start up and ActiveSync doesn't see him.
Click to expand...
Click to collapse
No, the flash center doesn't only work in Windows. It works on the bootloader mode. ActiveSync's icon turning green doesn't mean that activesync saw the phone, it means that it can synchronize your information with the computer.
radjapost said:
Where do I get the original ROM, may be even WM5? In your FTP- server I have found some "ship.exe"- Files, but I can't extract ".nbh" files from them.
Click to expand...
Click to collapse
If you broke your SPL like I mentioned above, you will have to use the Goldcard first then you will be able to flash any stock Herald/Tmobile Wing ROM.
radjapost said:
May be that is the point!!! My SD is too slow. Will be in this case "GoldCard" an ideal solution for me?
Thanks.
Click to expand...
Click to collapse
I don't know if it will be too slow for that, too. But if you broke your SPL, the goldcard is the ONLY way to fix it.

The problem is - for GOLD Card I need a working WINDOWS Mobile Handy... and I don't have such one at the moment.
Is it possible to become a standard GOLD Card, which would be suitable for most of Heralds?
Thanks

radjapost said:
The problem is - for GOLD Card I need a working WINDOWS Mobile Handy... and I don't have such one at the moment.
Is it possible to become a standard GOLD Card, which would be suitable for most of Heralds?
Thanks
Click to expand...
Click to collapse
You don't need a windows mobile phone. You can also create one using linux.
http://forum.xda-developers.com/showthread.php?t=485364
Obviously, make it for the Herald not the Dream.

Hi.
You don't need a windows mobile phone. You can also create one using Linux.
Click to expand...
Click to collapse
I've installed Linux on my computer, but i can't find a correct command to read a CID of my SD Card. My SD is located in Linux under "/media/disk-1" and I try to write something like "cat /media/disk-1:*/cid", but the Linux doesn't recognize CID command at all.
Actually, I hope, that after getting CID it will not be difficult to obtain a goldcard.img through QMAT. Am I right?
Thanks.