Develop Bugs

iMate PDA2K behaving as if no SIM card is inserted

Good evening, kind forum readers.
Per the subject line, I find myself in possession of one misbehaving iMate-branded Blue Angel. Everything was working perfectly until a day and a half ago. Now the device is acting as though there is no SIM card inserted whatsoever.
As you might expect, there is no signal detected whatsoever. The 'Device Information' system applicaton reports no information for the Radio or Protocol version. There is no IMEI number listed on the Identity tab. Launching the 'SIM Manager' tool does nothing - the application never launches. When I do a soft reboot, it correctly lists the ROM verion on the startup screen, but says directly above it "No GSM". I've tried a hard boot and restore from a backup from about a week ago, no luck. I have tried with two SIM cards from two different providers, neither one produces any different results. Both cards work perfectly when inserted into another phone.
I am using the official 1.40.00 WWE ROM from iMate. When I try to reapply the ROM, I receive the "COUNTRY ID ERROR". I tried with an older third-party ROM that I had been using a while back, but that also aborts with the same error message.
Speaking with iMate support netted me the typical "Send it in to a service center" answer.
Hoping that someone else out there might have gone through something similar? Any thoughts/suggestions on how I might recover from this?
Regards,
Shawn.

http://wiki.xda-developers.com/index.php?pagename=BA_1.40.00_Upgrade
Try following the description on the link, go for the MaUpgradeUt_noID option.
Use this on your Original Rom, and try one upgrade at a time, Radio first, then OS, Don't see any reason to flash the Extended Rom

bosjo said:
Try following the description on the link, go for the MaUpgradeUt_noID option.
Use this on your Original Rom, and try one upgrade at a time, Radio first, then OS, Don't see any reason to flash the Extended Rom
Click to expand...
Click to collapse
I just tried this option, and it did progress further this time, but it produced the following error:
Device Software Update Utility - R2500 D1001 - CB2.07 -1
ERROR 114: RADIO ROM UPDATE ERROR
There has been a problem while updating your device software.
To continue the update, please:
1 Disconnect your device and the USB cradle.
2 Perfrom a normal reset by pressing the reset button (as left picture show).
3 Reconnect your device and the USB cradle and run this device software update program again.
Click Exit to quit.
Click to expand...
Click to collapse
Being something of a newbie in such matters, I didn't realize that I had to run GetDeviceData.exe first, so I didn't have a copy of DeviceData.txt. In that the device was not in a bootable state, I wasn't sure how to run the OS upgrade without the Radio upgrade. I ended up going with the decidedly unscientific but seemingly effective solution of just renaming the 'radio_.nbf' file. The OS and extended ROM both upgraded successfully. So now I'm back where I started - the radio is still not functioning.

Run the same upgrade this time with the radio.nbf and remove the other 2 nbfs.
Else ron the radio upgrade only of wiki using those files.

And if what MDAIIIuser says don't work.
Download the latest Rom upgrade from your wendor website,
extract the .exe file with a zip program,
delete the nk, ms, radio files,
Copy the 1.13 radio in there,
Run the BaUpgradeUt.exe
Or try to only delete the ms and nk files leaving what ever radio is in there, and run the BaUpgradeUt.exe

How to Cleanly Uninstall IIWPO

Hi There,
I'm having problem after doing an un-Install of the IIWPO program.
I've checked and ensured that ALL files and registry settings are removed.
But it keeps giving a pop-up whenever the device is turned on.
The error says:
"Notification Error - Cannot Execute \Windows\IIWPO_main.exe"
Worst of all, I thought this error will go away after a ROM flash.
But it didn't even after I re-flashed the ROM for an upgrade.
Please kindly advice on any work around.
Cheers
Fishy

Use this.

WM6 Flash ends with error "cusTSK.exe doesn't exist"

I have tried to flash WM6 ROMs (both english versions available at wiki - pdaviet and orbit) to HTC original Artemis and every flash ends with error msg "The file \windows\cusTSK.exe does not exist", which is displayed after soft reset when it tries to install extrom.
Does anybody know where is the problem ? I have tried this flash several times, but always with this error ...

It sounds like you may have a corrupt extended Rom. I'd try flashing your original carrier ROM to fix it.

The error message is normal.
When I got the error the first time I boot the device (pdamobiz rom) I waited for 5 mins to see what happens. Then I simply made a power-off-power on to the mobile phone and the error never reappeared ever since. It works perfectly now!

I am not sure, but I guess this err msg is displayed when it tries to install apps from extrom, it is displayed after each hard reset. This is no limitation in functionality, everything works fine, only limitation is that there are no extrom apps installed, but these can be installed manually

I think the problem is that the program that changes the background in WM6 is not cusTSK.exe anymore. I don't know what is the program to do that in WM6 but maybe someone here knows. The error happens because on you extended rom there is a reference to cusTSK.exe. We need to know what is the name of the new program and then update our extended rom.

Sounds logically ...

ERROR [260] After upgrading wtih the "official" wm6

I upgraded my 85' with the "official" wm6 rom and now I cannot go to other roms. The process was solid, meaning I was fully charged, no power loss, and it was synced. I've tried every version of rom available and get the same results. I went through the "brick" thread and I'm affraid I don't quite fit into any category. I can get phone calls and everything works, I just happen to like all of the great ROM's everybody is cooking and want to try them to see which one I favor. I tried using the Hard-SPL and all of the other bootloaders out there and I always get that ERROR [206]. I've tried to restart the machine, and hard reset the 85'. Any good idea's.... Maybe I need to search more? I'll try that.
==============================================================================
UPDATE:
What I should really do is rent a gun, and buy a bullet...
I'm not saying I'm some sort of season veteran of flashing... but I've never had to touch anything after I accept all terms. For some reason, when it came down to the last "Next" form, my phone flashes "Accept" super fast. So what to do?... I push "Yes" soft key fast as I can and it runs like grease lightening... I had to choose SS for the boot loader because it couldn't figure it out... Maybe next time around.

Have you tried to flash a coocked ROM using the microSD card?

Hi,
did you try get your phone in the tri color bootloader screen and then running the Hard SPL program again?

I did not try to do flash it woth the MicroSD card... I just found out that I could flash it with the MicroSD card about 2 seconds ago. And I wanted to Hard-SPL at the tri-color as a last result in fear of bricking but everything is okay now. As I said before, I've never had to touch my 85' while flashing the rom, it just did it on it's own, but that "official" rom was not about being neglected. And then when I saw it flash something and say "yes", I pushed it and never looked back. It's alllllllllllllllllll good.
I do have one question, is the SSPL preferred over the other choices? Or is there one that is recommended?

Hi joshkrajnak,
How did you solve this problem exactly cos I dont understand what your saying:

http://forum.xda-developers.com/showthread.php?t=298640
boz said:
I extracted these error codes from a Hermes rom upgrade 'read me' document, these should be of help if you get an error message during a rom upgrade. They should be common to all roms, please correct me if I am wrong.
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 [260] : CONNECTION
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 [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.
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 [262, 276, 284, 302] : 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.
Click to expand...
Click to collapse

To Clarify: Whenever I went to upgrade my 85' to a different ROM, it wouldn't recognize my bootloader, and then after selecting any of the options, it would give the "ERROR [206]" message and fail miserably with any rom.
What I did to correct it was this: On the "official release" whenever I went to upgrade the ROM, the 85' would show a message at the bottom, the same as any "Notification" would giving me the option to either "confirm" or "dismiss". I did not notice the messages up until it caught my attention out of the corner of my eye on the very last attempt. The messages would quickly appear and disappear, so when the time came and it stated:
Current Rom: 3.25.###.###
Upgrade: 1.##.###
I had to press a confirm notification to continue on or I would get the "206" error message. The quote posted by Binyo is correct, but it does not apply in my situation.
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.
Although that may be true that some applications may interfere with the upgrade process, I had turned off all applications and killed any services during this process.

Advanced Config error

Does anyone have this problem?
Everytime I try to load Advanced Config, I get an unexpected error has occured....

ttvl4447 said:
Does anyone have this problem?
Everytime I try to load Advanced Config, I get an unexpected error has occured....
Click to expand...
Click to collapse
could you add more details on error??
Olioaglio

Hi,
I'm running on Schap's 3.54 ROM.
It attempts to load some files or settings, but half way through it says "An unexpected error has occured in AdvancedConfig.exe. Select Quit and then restart this program"
I clicked on Details and copied it as follow:
AdvancedConfig.exe
FormatException
at System.Boolean.Parse()
at System.Convert.ToBoolean()
at System.String.System.IConvertible.ToBoolean()
at System.Convert.ToBoolean()
at AdvancedConfig.Ӓ.֘()
at AdvancedConfig.Ӓ.ը()
at System.Windows.Forms.Form.OnLoad()
at System.Windows.Forms.Form._SetVisibleNotify()
at System.Windows.Forms.Control.set_Visible()
at System.Windows.Forms.Application.Run()
at AdvancedConfig.ִ.ֿ()

i encountered an error during auto-config too.
I was flashing a cooked WM6 rom....it was successfull, then attempts to do some auto-config, but in the middle of the process, during "Running Dopod_Black.tsk... it stops and hangs with a message saying
Windows\custTSK.exe does not exist!
then nag-hang na sya I cant tap OK nor can I click on any hardbuttons...only way is to softreset
any clues?

ttvl4447 said:
Hi,
I'm running on Schap's 3.54 ROM.
It attempts to load some files or settings, but half way through it says "An unexpected error has occured in AdvancedConfig.exe. Select Quit and then restart this program"
I clicked on Details and copied it as follow:
AdvancedConfig.exe
FormatException
at System.Boolean.Parse()
at System.Convert.ToBoolean()
at System.String.System.IConvertible.ToBoolean()
at System.Convert.ToBoolean()
at AdvancedConfig.Ӓ.֘()
at AdvancedConfig.Ӓ.ը()
at System.Windows.Forms.Form.OnLoad()
at System.Windows.Forms.Form._SetVisibleNotify()
at System.Windows.Forms.Control.set_Visible()
at System.Windows.Forms.Application.Run()
at AdvancedConfig.ִ.ֿ()
Click to expand...
Click to collapse
Wasn't something like this discussed HERE
Watch out for post #76 in this thread...
Also watch out for post #85 for the correct value
Olioaglio

Ok I saw the posts. Unfortunately the solution is too advanced for a noob like me.

Just flashed to TNT 2.0 Pro ROM and solved my problem