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

stuck on erasing storage (long)

heres my story.
i have an x50v that was running wm5. was having the usual problems with wm5 and tried sd flash to go back to 2003. ended up with the following on my screen after it went through the process of reading sd card, writing flash, etc, during the image updating process the unit gets stuck/stops/freezes at erasing storage at 50% through it.
My screen showed the following from top to bottom
SD Image Update A02
WM50_k_A01_x50v_WM5_en_nbo
Image Updating
erasing storage.....
ram checksum: 0x40d5291a
crc checksum: 0x40d5291a
\ (progress icon stopped/frozen)
Now this happened to me about 5 months ago, then the unit just shut down completely, no combination of buttons did anything, only sign of life was when it was cradeled, the power button would lite up. figuring i bricked my axim, i stuck it in a drawer and left it there.
this week i took it out, recharged the battery, put it all back together, tried the self diagnostic feature (rec/power/reset) and it went into self diagnostic and all checked out ok. Then i did the sd flash and was able to get back to windows mobile 2003. used it for about a day and wanted to go back to wm5/wm6, so since i have the wm5 cd from dell, i proceed to use it for my upgrade from 2003 to wm5, the unit begins the update process and i'm back to where my story starts, as it froze during the update process. Since i was no longer able to connect to my pc via usb cable, i had to do an sd flash so after trying various different nbo files to see if any would work, none have, my unit is stopped/frozen here again
My screen shows the following from top to bottom
SD Image Update A02
WM50_k_A05_x50v_WM3k3_eng_nbo
Image Updating
erasing storage.....
ram checksum: 0xC4C94BEB
crc checksum: 0xc4c94beb
\ (progress icon stopped/frozen)
Now i can get it to load any nbo file which in turn would give me differnt lines in the above noted screen lines, but the result is always the same, it freezes at 50% of the erasing storage.
Now i know everyones advise is that if you dont know what your doing, dont do it, but i'm fairly capable and this shouldn't be happening should it? Do i have some sort of memory problem with my axim, or am i doing something wrong?
ANY help would be appreciated.

ok, i was able to get 2003 back up and running. I had to rename the dima bootloader file to wm50 and load the bootloader, then reload the flashed image of 2003.
now the question is should i try this again to see if it will freeze again at the erasing storage area again doing the update from the dell cd (from 2003 to wm5-a01). This is how it went wrong last time. I was originally able to install wm5 from the disc, and tried to sd flash to wm5-a02, and thats when my axim froze up during the erasing storage image update. here is what i plan on doing now
use dell cd to go from wm2003 to wm50-a01 (this should update my bootloader)
then go from wm5a01 to wm50-a02 using sd flash (do i need any other bootloader?)
then load wm6 via sd flash
all this should go well but it hasn't yet.

An unrelated question, how did you recover your Axim after "bricking" it? I tried the rec/power/reset combo but nothing happens.

Official Diamond ROM 2.03 update - HELP

Hey guys,
I have no idea what's going on. I appreciate your suggestions. I flashed my Diamond many times (and other phones as well) with most of the ROM available. Unit a month ago or so I've been using the official 1.93 ROM with previously installed hard SPL 1.40. When I attempted to install a new 2.03 ROM I went through the whole procedure same way as always with a little exception. Right after completion - 100% the unit reboots, shows the rainbow screen with a message "Upgrade ROM code error" - try again. What is the world is this? I also have a message on my desktop "Error 270-update error" - The image file is corrupted. My unit is european and I downloaded the ROM from both US and Euro sites. From this point I managed to downgrade again to version 1.93. Then I ran again the hard SPL 1.40 and reattempted to upgrade to 2.03 - SAME THING!
I don't know what to do next. Why I cannot flush it with the latest ROM? Any ideas or similar situations? Please see picture.
Thanks

Same Thing happened to me :S wtf??

xevier69 said:
Hey guys,
I have no idea what's going on. I appreciate your suggestions. I flashed my Diamond many times (and other phones as well) with most of the ROM available. Unit a month ago or so I've been using the official 1.93 ROM with previously installed hard SPL 1.40. When I attempted to install a new 2.03 ROM I went through the whole procedure same way as always with a little exception. Right after completion - 100% the unit reboots, shows the rainbow screen with a message "Upgrade ROM code error" - try again. What is the world is this? I also have a message on my desktop "Error 270-update error" - The image file is corrupted. My unit is european and I downloaded the ROM from both US and Euro sites. From this point I managed to downgrade again to version 1.93. Then I ran again the hard SPL 1.40 and reattempted to upgrade to 2.03 - SAME THING!
I don't know what to do next. Why I cannot flush it with the latest ROM? Any ideas or similar situations? Please see picture.
Thanks
Click to expand...
Click to collapse
Hi have you tried to flash from the internal storage?

Have you tried flashing with internal storage method?

Exactly the same problem here, so I tried to flash to a really old original HTC ROM after the failure and it flashed fine
So I thought I would try upgrading over the top of an original ROM, had the same error , bloody HTC

So, any ideas how to resolve this issue? Are we stuck with the old ROM? I'm glad that I'm not the only one experiencing the same problem.
No, I have never tried to flash from internal storage. How can this be done? do I copy the whole .exe file to storage and run from there? Any pre-cautions?
Thanks

Though I bricked my phone when it happened, never seen that error before despite many ROM flashes
I have now tried tommytaos ROM which is supposed to be very close to the original but some with some tweaks.
http://forum.xda-developers.com/showthread.php?t=479049
It installed just fine on my phone. Seems HTC have broken their ROM

xevier69 said:
So, any ideas how to resolve this issue? Are we stuck with the old ROM? I'm glad that I'm not the only one experiencing the same problem.
No, I have never tried to flash from internal storage. How can this be done? do I copy the whole .exe file to storage and run from there? Any pre-cautions?
Thanks
Click to expand...
Click to collapse
it's the best way to flash the rom and the safest...
From Suiller thread:
the standard procedure to cook a ROM is made trough activesync program, I mean that the .nbh file is pushed into the phone trough activesync, across the usb cable, but this procedure can give some troubles:
1. it takes long time, about 10 minutes
2. it's a bit unsafe (even if the procedure can be always restored safely)
3. it's possible only with Windows OS (NO Linux nor *BSD, et cetera...)
I don't know why this is not well known but ALL producers (like HTC) give the possibility to upgrade the rom/firmware without having MS windows (thanks GOD someone knows that there aren't only windows users).
This faster procedure can be done also with *nix variants (or whatever you use) because the ROM update is made directly by the phone.
The procedure is very simple, it will take just 2 minutes, can be done everywhere & is good for cooking radios too (very fast in this case)
-= COOKING ROMs & Radios from phone =-
1. open from your PC the rar or zip archive and extract only the BIG .nbh file
2. rename as DIAMIMG.NBH
3. copy the renamed file into the root dir of your "Storage Card" or "Internal Storage" (the one of 4Gb... NOT to the internal phone memory!)
4. reset your device and within 3 seconds push together the Vol_Down + Back button (the one on the right above the hangup button) and keep pressed until the boot loader appears (the one with the color stripes)
5. soon as you see the bootloader stop to press those poor buttons
6. a very simple gray menu will appear asking you what to do, simple press the power button to perform the ROM/Radio upgrade
7. while the upgrade runs be patient and don't press again the power button, reset the device or play with it until it finishes, when finished a message "UPDATE SUCCESS" will appear, now you can safely reset your device
8. who prefer can perform a hard reset after the fresh cook (soon after reset simply press Vol_Down + Circle button, then when you see another simple gray menu choose Vol_Up to confirm format), even if this has no-sense because internal memory is pre-formatted during flash, but... there is always a but... for some unknown "scientific" reason sometimes an hard-reset can save time & headache
notes:
* be sure to have at least 10/20% of charge, anyway the whole procedure will take about 2 minutes, so you must be ensure that your mobile will stay turned on for at least those 2 dirty minutes (just in case you can attach the power AC/DC too), don't panic if something goes wrong... read few lines below
* like told you above the same procedure is good for cooking Radio too, of course Radio are smaller and it will be really fast (about one minute!)
* you don't need windows anymore or activesync, is enough just to copy the file into the storage card (transfers WITHOUT activesync are faster)
* it's possible to make a reset simply by getting off the stylus and pressing the small red button under the stylus carrier
* don't worry if something goes wrong... any cook failure can be always restored, the important thing is that you don't fail hardspl flash... but you have to do it just one time in your life
special note about hard-spl:
if you have signed-only hard-spl I strongly suggest to upgrade to an un-signed one, personally I tested many & I can confirm that the "good ones", at least in my experience, are the Olinex 1.37 or 1.93, you can find a copy here
remember also that you can NOT brick your device if you have a good hard-spl (like the ones I mentioned above) & flashing directly from phone is really faster (also good for flashing radio)
so the only one thing you should take care is when you change/upgrade the hard-spl, but you have to do this step just once, I'm using this hard-spl from about 6 months & I was able to flash everything (plus dozen recovers for failed flash)
for rom/radio upgrades you can safely also reboot/remove cable/turn off your phone while flashing ...every lost flash can be always restored safely, it's enough to restart your device in boot mode & restart flashing, also with cable trough the classic RUU (to put device in boot mode simply reset & keep pressed Vol_Down button)
In the hope this procedure can be useful at least to save time

if you have the official rom which is a exe file you can extract the rom file using winrar.

EUREKA!!! Done Deal!!!
Flashed from Internal Storage as per following directions:
-= COOKING ROMs & Radios from phone =-
1. open from your PC the rar or zip archive and extract only the BIG .nbh file
2. rename as DIAMIMG.NBH
3. copy the renamed file into the root dir of your "Storage Card" or "Internal Storage" (the one of 4Gb... NOT to the internal phone memory!)
4. reset your device and within 3 seconds push together the Vol_Down + Back button (the one on the right above the hangup button) and keep pressed until the boot loader appears (the one with the color stripes)
5. soon as you see the bootloader stop to press those poor buttons
6. a very simple gray menu will appear asking you what to do, simple press the power button to perform the ROM/Radio upgrade
7. while the upgrade runs be patient and don't press again the power button, reset the device or play with it until it finishes, when finished a message "UPDATE SUCCESS" will appear, now you can safely reset your device
8. who prefer can perform a hard reset after the fresh cook (soon after reset simply press Vol_Down + Circle button, then when you see another simple gray menu choose Vol_Up to confirm format), even if this has no-sense because internal memory is pre-formatted during flash, but... there is always a but... for some unknown "scientific" reason sometimes an hard-reset can save time & headache
THANKS! THANKS! THANKS!

Flashing using the Internal Method is the safest and most convenient way to flash. Spread the word.......

xevier69, Thanks for your thread
Having just purchased Oli's security unlocker... I was annoyed about this problem with a HTC official rom!
But your method has solved this issue!
Thanks again

Thanks guys it works perfect!

This just happened to me too and the only roms i have ever flashed:
1.37 official spanish: came with the phone
1.37 official WWE
1.93 official WWE
and now 2.03 official WWE fails.
WTF... One would expect the upgrade not to fail, right?
I wonder if they are checking for HardSPL to be original too!?
Anyway thanks for the workaround

This worked for me to
Cheers
xevier69 said:
EUREKA!!! Done Deal!!!
Flashed from Internal Storage as per following directions:
-= COOKING ROMs & Radios from phone =-
1. open from your PC the rar or zip archive and extract only the BIG .nbh file
2. rename as DIAMIMG.NBH
3. copy the renamed file into the root dir of your "Storage Card" or "Internal Storage" (the one of 4Gb... NOT to the internal phone memory!)
4. reset your device and within 3 seconds push together the Vol_Down + Back button (the one on the right above the hangup button) and keep pressed until the boot loader appears (the one with the color stripes)
5. soon as you see the bootloader stop to press those poor buttons
6. a very simple gray menu will appear asking you what to do, simple press the power button to perform the ROM/Radio upgrade
7. while the upgrade runs be patient and don't press again the power button, reset the device or play with it until it finishes, when finished a message "UPDATE SUCCESS" will appear, now you can safely reset your device
8. who prefer can perform a hard reset after the fresh cook (soon after reset simply press Vol_Down + Circle button, then when you see another simple gray menu choose Vol_Up to confirm format), even if this has no-sense because internal memory is pre-formatted during flash, but... there is always a but... for some unknown "scientific" reason sometimes an hard-reset can save time & headache
THANKS! THANKS! THANKS!
Click to expand...
Click to collapse

Thers some other option
Install twice from activesync 1st time = error, run for the second time the same version and OK it updates.
At least with my Diamond had worked
Cheers

Hi!
The same thing happend to me too... I think it's because of the serial number we have entered when we have downloaded that 100 MB ROM Update file from the HTC support site... well i think it doesn't match with the serial and IMEI of the phone that the upgraded rom checks at the end of the update process... so i think it's kind of a protection against piracy developed by htc... taiwanese idiots!

Hi!
pls anyone send any information about an rom update file that works and doesn't report errors after it installed 100%. pls specify it's rom version too! 2.03 would be great
thanks in advance

miriamscorob said:
pls anyone send any information about an rom update file that works and doesn't report errors after it installed 100%. pls specify it's rom version too! 2.03 would be great
thanks in advance
Click to expand...
Click to collapse
read all posts please
works like a charm folks! thank you!

g0x said:
Thers some other option
Install twice from activesync 1st time = error, run for the second time the same version and OK it updates.
At least with my Diamond had worked
Click to expand...
Click to collapse
I made this too for testing First flash: Error, Second time: Ok

Error 270

Hi All,
I did some search, but it seems there's no Error 270 topic for a Touch Diamond. And surprisingly that's the problem I have. Here's the deal.
For a whole duration of the day I've been trying to upgrade to 2.03 ROM, which would my first ROM upgrade. I tried the ROM from the phone's importer site, the HTC site, xda site, all lof them with the same result. After the RRU reaches 100% the mobile goes to Tricolor with "Upgrade ROM code error" message and the RRU shows says Error 270.
I searched the forum and saw that some of the people suggested to burn different HardSPL versions, so I tried burning the 2.03 with various HardSPL versions, 1.24, 1.30, 1.93 are the few I remember, there were more, both signed and unsigned, the last is SPL-1.93.OliNex unsigned -> all of them installed nicely, with a clean reset after them but the following upgrade to 2.03 failed every time the same way, Error 270, as usual.
I use an original USB cable and an XP OS that, at the moment of RUUing, runs nothing but the RUU.
By the way, I also tried doing the upgrade from the internal storage. I renamed the ~100MB file to the name specified in the Noob Guide (DIAMIMG.NBH) and put it at the root of the storage device, but the bootloader gray screen says no image found (or something similar and goes directly to trying to find a USB host).

OK an Update (for whoever gets this problem after me).
I'm not sure why the installation from PC failed time after time - this is something for smarter people to find out.
I solved it by eventually managing to copy one of the numerous RUU_signed.nbh I tried, to the Internal storage, renaming it to the DIAMIMG.NBH and running the bootloader procedure.
Why didn't this work for a 6-10 times I did this before, I donno, the important thing that now it did, and I'm going to enjoy my diamond starting this moment.

Error Code 270
Dear Hunter_I
i have HTC Touch Diamond
i m facing the same problem. and i even dont know how to find the file and how to copy it in HTC internal storage
it is totally un accessible for me
can u help me in this regard
regards
Khurram

Dear Hunter_I
i have HTC Touch Diamond
i m facing the same problem. and i even dont know how to find the file and how to copy it in HTC internal storage
it is totally un accessible for me
can u help me in this regard
regards
Khurram

Hello,
I'll be happy to help to the extent I can.
But can you please specify where you stand right now?
I mean, what steps did you take already and where did you stop?
For example,
Do you have Hard SPL installed already?
What's the ROM you currently have?
Can your phone boot up correctly? Can it sync with your PC?
Is your phone locked?
Let me know some details.

Sprint Vogue troubles AGAIN flashing at 29% then stopping???

I am using the 2.31 unlocker and I am attempting to flash the sprint update 6.1 rom from the sprintpcs web site.... and my phone keeps stopping at 29% and freezes there....
The ROM on my lap top has a recover procedure ... which I have followed several times .... with no luck
OH! and thanx to TMZ, for saving my phone last time around!
thanx
Kevie
So, I just flashed from the boot screen, this ROM "Sprint Vogue ROM. exe and what happened is .... runs up to 29% then gives me a ' 262 ' error message.
When I run the un-locker it seems to run that rom correctly also, I can load
23506_v4 ROM
this rom seems to load fine, then when it runs it continually will RESTART the Phone... ???
There have been times when this ROM ran for a while and I thought it was because of battery issues...??? because when I would take it off either the SYNC or the Charger... the RESTARTing would begin.... again I have NO IDEA... what is going on here....
Seems to me that I have not WIPED the Phone clean enough for these roms
I have also tried...
updater_htc_touch
via the sprint web site to the HTC website
same thing it stops at 29%
I thank anyONE in ADVANCE

Have you only tried flashing USB?
What happens when you try to flash the roms via the micro-sd card?
These phones usually came with a little 512MB card.
Format that card Fat-32, 1024 bytes/sector.
If you open up the Sprint.exe rom upgrader (with 7-zip), you'll see a folder.
Inside there are 2 .nbh files. 1.nbh I believe updates the system and phone.
The 2.nbh is the main rom file that flashes all the software.
Copy the 2.nbh file to the 512MB micro-sd and name it voguimg.nbh
Soft-reset until you see the 2.31 coke loader, and it should auto-detect
the voguimg.nbh file and say 'press power' to start flashing.
Best suggestion I can offer - micro-sd flashing is MUCH faster and
has much much less chance of connection errors over the usb cable.

OK I will try that... I had done that already... meaning I have the file on my MICRO SD already but the post I think I learned it from was all about capital letters in the name ... I have renamed it and here we go....???

Doesn't matter the lower-case or upper case for the file name.
it just has to be called: voguimg.nbh or VOGUIMG.NBH
Most important is the name.
Could also try a hard reset first:
Send, End, and push in the reset button, then follow the screen directions.
Once the hard reset is completed, pull out the battery for a minute,
then put the battery back in, and when you power on the phone, immediately
do the soft-reset to get to the tri-color coke screen and then try and
re-flash one of those images.
--------------------
http://forum.xda-developers.com/showthread.php?t=605590
Might also try the NFSFan 1.12 Sprint image in that post.
That one is based off the original 6.1 Sprint download.

seems like you may have the wrong sprint rom..
Even if your phone was locked you should be able to load the sprint update with no problem..
but the fact that you can load a custom rom tells me your phone is most likely unlocked, the resetting is most likely due to the fact that you have a non-gps radio from not having the sprint update.
go to the htc website, then to support, touch (sprint), downloads then finally click the download link on the rev a 6.1 update
After you flash that update rom you should be able to load any custom 6.1 or 6.5 rom
hope that helps

I've had the same problem in the past. Flash a Sprint WinMo6 ROM and unlock it to 2.31. Then you'll be able to flash a Sprint 6.1 ROM. Hope this helps

I had the same exact problem once and it was because I had a bad battery. Changing the battery should resolve your issue.