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
Related
First time post ...
I recently downloaded the 1.13.53 WWE ROM update from the Imate site and attempted to install it on my JasJar. The update failed leaving my JasJar in boot loader mode. No reset method seemed to work to bring it back up. Subsequent attempts to load the ROM update gave me the dreaded "Country Code" error. Here are the steps I followed to get the ROM update to succeed:
1. Uninstalled ActiveSync 4.0 and installed ActiveSync 4.1 as downloaded from XDA FTP site. Disabled firewall and Anti-virus. Rebooted machine. I am not sure whether this step was neccessary or not but noted that others had some success with this. At this point I was still getting the country code error when trying to install ther update.
2. Run the update but once you get to the first screen that asks you if you want to proceed, switch to the Windows file system using Explorer and set the current directory to your TEMP directory. If you are not sure where this is, open a command prompt (Start - Run - CMD - OK) and type SET. This will display environment variables. Look for the one called TEMP - that is where you want to go.
3. Search for a file called ROMUpgradeUT.exe or RUU.conf anywhere in the TEMP directory or its subdirectories. When you find the correct directory, copy the files to a new location.
4. In the new location, edit the RUU.conf file and add the following text at the end of the file:
[CHECKCEID_TYPE]=1
5. Save the file and then run ROMUpgradeUT.exe
At this point I was able to get past the country code error and the update began. The radio upgrade was the first component and it took the most time (about 10-15 minutes). The other 2 components upgraded the extended ROM and the OS but only took about 5 minutes each.
After getting the completion message on my PC I also noted a "100% complete" message on the JasJar screen. After a hard reset (soft keys and reset) the JasJar came up with the upgraded ROM in place and I was REALLY HAPPY!
I don't know if this will work for anyone else - use at your own risk but I wanted to share what has worked for me.
BTW - many thanks to all the previous posters who left "breadcrumbs" for me to follow in getting my JasJar back. This community is SUPERB!
Thanks again.
Rick
Did like u said.
Still country id error
works now
thanks
my device t-mobile mda pro jasjar bootloader nope
rsteel1 said:
First time post ...
I recently downloaded the 1.13.53 WWE ROM update from the Imate site and attempted to install it on my JasJar. The update failed leaving my JasJar in boot loader mode. No reset method seemed to work to bring it back up. Subsequent attempts to load the ROM update gave me the dreaded "Country Code" error. Here are the steps I followed to get the ROM update to succeed:
1. Uninstalled ActiveSync 4.0 and installed ActiveSync 4.1 as downloaded from XDA FTP site. Disabled firewall and Anti-virus. Rebooted machine. I am not sure whether this step was neccessary or not but noted that others had some success with this. At this point I was still getting the country code error when trying to install ther update.
2. Run the update but once you get to the first screen that asks you if you want to proceed, switch to the Windows file system using Explorer and set the current directory to your TEMP directory. If you are not sure where this is, open a command prompt (Start - Run - CMD - OK) and type SET. This will display environment variables. Look for the one called TEMP - that is where you want to go.
3. Search for a file called ROMUpgradeUT.exe or RUU.conf anywhere in the TEMP directory or its subdirectories. When you find the correct directory, copy the files to a new location.
4. In the new location, edit the RUU.conf file and add the following text at the end of the file:
[CHECKCEID_TYPE]=1
5. Save the file and then run ROMUpgradeUT.exe
At this point I was able to get past the country code error and the update began. The radio upgrade was the first component and it took the most time (about 10-15 minutes). The other 2 components upgraded the extended ROM and the OS but only took about 5 minutes each.
After getting the completion message on my PC I also noted a "100% complete" message on the JasJar screen. After a hard reset (soft keys and reset) the JasJar came up with the upgraded ROM in place and I was REALLY HAPPY!
I don't know if this will work for anyone else - use at your own risk but I wanted to share what has worked for me.
BTW - many thanks to all the previous posters who left "breadcrumbs" for me to follow in getting my JasJar back. This community is SUPERB!
Thanks again.
Rick
Click to expand...
Click to collapse
this method how?my jasjar can open normal ?
help me
error 101 problem
error 150 problem
MaUpgradeUt_noID trying in my jasjar error problem 150 .whats saying ? problm where? usb dont recognize xp .what must ı do?
please help me im using Vista and cant get connection with my imate to my pc... and what is a radio update if you can help me add my msn!
i dont want to update anymore i just want to get my wm5!
Have a look here:
http://wiki.xda-developers.com/index.php?pagename=FlashVista
Hope it helps,
I have an Atom Exec with ROM 20060721B1WWE, Radio RS00011. In the seeO2 website I saw an upgrade (Xda Atom Exec ROM Upgrade (ENG) 20060721B1WWE_RS00013) which is the same ROM but different Radio, supposed to improve quality of calls.
Anyway I went to upgrade it, followed the steps until it said it was uploading it and it would take up to 30 minutes. I went to do something else and when came back the pc screen was saying that the process finished successfully, saying that I had to do a hard reset of the Atom, wait for 30 seconds and then soft restart. I did all of that and all I got it's the O2 screen and doesn't go any further.
Following indication on this forum I launched the bootloader (camera button+reset), conected the usb cable, killed activesync and run again the updater.
The DSUU can see the Atom, says 'Device CE image version:0, Device Radio Image version: (blank) to CE Image version: 7210621, Radio Image version: R060822N_MN2ARC_RS00013.
When I click on Upgrade I get an Error message: Connection error, also on the Atom says '!!! Please use DSUU in OS mode and sync with Pc first !!! USB transfer Fail'
The only backup I did prior to this was using SPB Backup, nothing for the ROM. Is there any other way to upload the ROM?
From the Windows/Temp folder I got the files used by the DSUU:
Device Software Update Utility.exe
diskimage_Ver.nb0
EBOOT.nb0
ExtenderRom.img
nova_pda_033105.mot
vl1d_pda_Ver.mot
I've seen in other forums people recovering iPaqs or Axims using these files and software like romupdate, but I'm afraid it could get worse uploading the diskimage_Ver.nb0 as it is.
Anybody knows a workaround for this?
I ended copying diskimage_Ver.nb0 and eboot.nb0 to an miniSD card. Inserted it in the Atom and lauch the bootloader. It recognized the card and Rom file, started downloading it. After that I got few messages saying some files were missing.
Screen went blank and that's it. Now is completly dead, it won't restart or anything.
I'll have to send it to Hong Kong I guess.
I have a TyTN with official Russian WM6 onto it, which includes 1.16 radio version. I want a newer one, because this seems unstable, so i decided to update just radio (i don't want any cooked ROM or whatever for now).
Each new version of radio I found here failed earlier or later on a Vista x64 computer with error 260. What I have tried is 1.54.07.00 and 1.54.00.10 and 1.50.
To my surprise, packaging is different, but the effect is the same: after "Verifying the image on your device" (i can hear USB disconnecting and connecting back as the device enters bootloader) they time out with 260.
Right now I'm trying to revert what have I done to Vista as it won't allow me to turn off driver signing, as advised.
Ah, this doesn't work either (same error 260).
What am I doing wrong? My bootloader is, as said on that screen:
Code:
HERM200
IPL-1.01
HERM200
SPL-1.40.Olipro
Yes, I have installed some...er...thing before, maybe it was called "HardSPL", but it didn't come handy and wasn't any use to me as I decided against cooking a ROM.
Update: What I like the most is, despite all my attempts the device still works! Other than the radio troubles, that is.
I've updated from an SD card.
Try this my friend... http://www.mrvanx.org
Thank you, I did.
Please note the x64 drivers are unsigned so to use them successfully you must disable driver signing.
Click to expand...
Click to collapse
This is what I'm unable to do, but I suppose is beyond this forum.
Hi
I have had the same problem with my x64 vista pc and the 260 error msg. It took me hours but what seemed to finally fix it for me was to:
1. completely remove WMDC from the pc, reboot the pc,
2. reinstall WMDC plus upgrade,
3. uncheck the allow USB connections option on your 8525, exit out of the window, then do a soft reset
4. now make a USB connection w the PC
Let us know how it works
Sorry, you'll have to wait till my next upgrade Everything is working so far - so until I need something that can't be achieved using SD flashing I'll stick to this technique. Thanks for the advice anyway.
Hi
I have a HTC Cruise(Polaris), I tried a view roms from the Polaris section, but I prefered goig back to my old rom. So when I tried to flash the Dutch Dumped Rom I got stuck at 15% I rebooted the pda. So now all I see are tree colors.
When I try to upgrade the phone to the WWE release version I get: "error 294 invalid vender ID". After it hits 1%.
- How can I CID unlock this phone?
- Joe
With Polaris_WWE_B_20273_1_3_3_V09_Lt_Swtos I get a ERROR [262] : UPDATE ERROR. Even when I retry. Also with the RUU_Polaris_HTC_NLD_SEA_1.28.404.2_radio_sign_25.69.30.05H_1.58.25.14_Ship
anyone can help me out?
Extract the RUU_Signed.nbh file from the downloaded ROM and try flashing from a microSD card. Directions can be found on the boards.
Extract the RUU_Signed.nbh file from the downloaded ROM and try flashing from a microSD card. Directions can be found on the boards.
Click to expand...
Click to collapse
i renamed the RUU_Signed.nbh and pushed down the camera button and rebooted, but doesn't work. Could you shed some light on this?
I have a completely different suggestion. Have you tried a hard reset BEFORE you attempt the burn?
I do not know or have experience of your hardware. I have burned new ROMs on two other makes of PDA and experienced the same problem. A hard reset or return to factory state works.
I have concluded that a burn often fails because the new image does not have enough memory space on the PDA to load the new ROM image and the small program that executes the burn. If you don't go back to the "factory state" by removing all your own installed programs and data first, then there may be insufficient memory to complete the burn. Precisely where it fails in the burn depends upon how much spare memory is available, so in other cases it will fail at a different percentage of the burn.
Worth a try?
solved it with mtty
Okay, I've searched alot to get this thing solved. When I try to update my rom, the update starts normally, but then my telephone screen turns black, my gets disconnected, windows tells me it has found new hardware. The update failes and returns error 260 (connection lost). When I soft-reset the telephone afterwards, it returns to it's old shape.
Info about my telephone.
Rom: 1.93.404.1 NLD
Radio: 1.0025.05
PC: Windows XP SP 3, Active Sync 4.5
I tried to update with this rom: RUU_Diamond_HTC_NLD_2.03.404.3_Radio_Signed_Diamond_52.51.25.26_1.09.25.23_Ship.exe
I also tried to update to Hard-SPL but that gave me the same error.
PLease guys does anyone of you know how to fix this? (personally I think it's windows xp which is screwing up).
Thanks in advance, I appreciate all help.
Yours, Martijn.
Even the tiniest tip may help (A)
I had the same trouble with that rom, I tried from internal memory and it worked. Search the wiki I am sure the info is there.
"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."
This is what the WIKI tells me. But I have tried that. How did you manage to perform the update on the internal storage? Because I tried that with hard-spl but it wouldn't work.
Besides I only have .exe files for the Hard-Spl and the official rom from HTC.
Thanks for your reply though.
EDIT PART, just read this on another thread in the wiki:
ERROR 260 (Update Error):
"Your phone is not connected to ActiveSync. Check your connection or restart the phone. Also make sure in ActiveSync that "Allow USB connections" is checked (under File->Connection Settings). If this still doesn't help, then remove the memory card and SIM card before flashing."
I'm going to try this now, if it worked, I'll let you know
Just found out I have a CDMA version or something, I'll try google for the problem now.
Get the rom image from your temp directory and look here, found in the wiki
http://wiki.xda-developers.com/index.php?pagename=Diamond_FlashfIS
Does the hardware install incorrectly? My laptop did this on XP.
XP would find the new hardware, my bootloader would say USB. Then it'd tell me new hardware could not be installed properly and from there my phone suffered those symptoms - Back to where I was. Funnily enough it eventually fixed itself.
dickenz said:
Does the hardware install incorrectly? My laptop did this on XP.
XP would find the new hardware, my bootloader would say USB. Then it'd tell me new hardware could not be installed properly and from there my phone suffered those symptoms - Back to where I was. Funnily enough it eventually fixed itself.
Click to expand...
Click to collapse
It looks alot like your problem yes. But last time the hardware installed correctly, then the patch I found for CDMA models on ppcgeeks failed, and my telephone got bricked. So I'll need to get that fixed first. After that I'll sure think twice before I try another rom update :/
Thanks for all the help though, and I have to advice everyone to not use the hard-spl for cmda users from ppcgeeks unless you're 100% sure it fits your model!