Related
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
So i downloaded WM6 Black 2.0, and its constantly crashing, so i wanted to re-install it and see if that helped.
now whenever i try to launch the file, i get an error message that states
"custom RUU has encountered a problem and needs to close. we are sorry for the inconvenience."
So im wondering what changed that wont allow me to run the ruu file? Im kinda freaking out here because i need to get my phone working! its constantly crashing on me!
i hope someone knows a fix for this, i tried to search but came up with nothing
newnoise1024 said:
So i downloaded WM6 Black 2.0, and its constantly crashing, so i wanted to re-install it and see if that helped.
now whenever i try to launch the file, i get an error message that states
"custom RUU has encountered a problem and needs to close. we are sorry for the inconvenience."
So im wondering what changed that wont allow me to run the ruu file? Im kinda freaking out here because i need to get my phone working! its constantly crashing on me!
i hope someone knows a fix for this, i tried to search but came up with nothing
Click to expand...
Click to collapse
Looks like a problem on your PC... (I mena for the Customruu crashing)
newnoise1024 said:
So i downloaded WM6 Black 2.0, and its constantly crashing, so i wanted to re-install it and see if that helped.
now whenever i try to launch the file, i get an error message that states
"custom RUU has encountered a problem and needs to close. we are sorry for the inconvenience."
So im wondering what changed that wont allow me to run the ruu file? Im kinda freaking out here because i need to get my phone working! its constantly crashing on me!
i hope someone knows a fix for this, i tried to search but came up with nothing
Click to expand...
Click to collapse
Had this happen to me. I downloaded .net framework 3.0 from the M$ site and then it worked fine.
Maybe that will help you.
Jim
Need more info?
newnoise1024 said:
So i downloaded WM6 Black 2.0, and its constantly crashing, so i wanted to re-install it and see if that helped.
now whenever i try to launch the file, i get an error message that states
"custom RUU has encountered a problem and needs to close. we are sorry for the inconvenience."
So im wondering what changed that wont allow me to run the ruu file? Im kinda freaking out here because i need to get my phone working! its constantly crashing on me!
i hope someone knows a fix for this, i tried to search but came up with nothing
Click to expand...
Click to collapse
Ok, first off, this is not a flame. It's an education, ok?
When posting a problem, it's best practice to let us know your:
Model of phone
Radio version
Boot Loader version
OS on your PC
ActiveSync version (s/b 4.5 by now)
Then, and only then, will you be able to get some intelligent answers. You also need to follow the link in my signature and there you will find answers.
If you're still stuck, usually re-downloading the RUU will result in a working ROM patch, unless you have other PC issues. You really need to fix that first, and the guides posted here are FULL of the diagnostic and troubleshooting steps that will propel you to a successful resolution.
Please read those posts, add your info, and you may be extremely pleased with the results.
Good reading!
newnoise1024 said:
So i downloaded WM6 Black 2.0, and its constantly crashing, so i wanted to re-install it and see if that helped.
now whenever i try to launch the file, i get an error message that states
"custom RUU has encountered a problem and needs to close. we are sorry for the inconvenience."
So im wondering what changed that wont allow me to run the ruu file? Im kinda freaking out here because i need to get my phone working! its constantly crashing on me!
i hope someone knows a fix for this, i tried to search but came up with nothing
Click to expand...
Click to collapse
First off; relax. At least the problem isn't with your phone. It's a heck of a lot easier to fix a PC.
I assume you've already tried to re-download the file?
Did you completely reboot your PC? Shut it down to power down, then restart. Make sure you don't have any extra USB stuff plugged in (like cameras, etc). If you have a PS/2 mouse and KB, use those, and not USB versions. One trick is to have the USB bus on your computer completely empty except for your phone.
Head over to Microsoft's site and download a fresh version of Compact Framework .NET (3.0 is the current version). Reboot after installing it -- even though it doesn't tell you to.
Run Windows Update. Make sure you're OK on those.
If that doesn't work, try downloading another ROM (OS only) -- like the Cingular Black 2.02 or the LVSM ROM, and see if that works.
You can also strip it apart -- use WinRAR to open the EXE file that you've been executing and extract the .nbh file from the EXE. Then go and download this guy: http://wiki.xda-developers.com/index.php?pagename=Hermes_CustomRUU and extract it into its own folder. Copy that .nbh file into that directory, and execute the executable -- it will flash your phone with a known good flasher.
But.... stepping all of the way back ... if the ROM doesn't work on your phone, it's very likely reflashing it won't help a single bit. Those ROM's are checksummed when they go on the phone -- if they're corrupted, they won't load right in the first place (and you'd end up with a boot-loader only phone). Soo... uh.. first, reboot/clean USB, then try a different ROM.
Last resort will be completely reinstalling Windows XP. I've had to do this several times because Windows will get in some weird state and it refuses to flash my phone. I finally gave up and started flashing on my Mac using a Windows virtual machine -- it's a lot easier to restore my Windows system to a working point when I do that.
Thanks to everyone who gave a response!
Here's all the information i was asked to post ( i will remember this for next time)
Cingular 8525 HERM100
Radio version: 1.40.30.00
Boot Loader version: (Not quite sure what this is?)
OS on your PC: Pro Black 2.0
ActiveSync version 4.5
I have redownloaded the ruu about 3 times and it has failed everytime.
Restarted the PC, disconnected everything from my laptop, realized that i havent installed Framework .NET 3.0, ( although i have it on my phone as i needed it to run hitchhiker)
So i'm going to download framework .NEt 3.0 and run it.
As for my phone, i uninstalled all the apps, hard resetted and everything is working fine right now, hasn't froze at all since yesteray, so im going to wait it out and see if something happens again.
Thanks again to everyone!! This forum is really really helpful.
-Matthew
How to determine the bootloader version
newnoise1024 said:
Boot Loader version: (Not quite sure what this is?)
-Matthew
Click to expand...
Click to collapse
You need to have a look at your user guide, as it states how to enter bootloader and check the version. Otherwise press and hold the left OK button and the power button at the same time, then hit the reset button with your stylus. You will enter a tri-color screen. This is bootloader mode. Jot down the numbers and compare against the below link.
Exiting is simple, press the reset button with your stylus.
Here's a valuable link for updating your bootloader.
Bootloader Version: SPL-1.40.01pro
IPL-1.01
i just tried to install Framework .NET 3.0 and got this error message
[04/20/07,08:50:20] Windows Communication Foundation: [2] Error: Installation failed for component Windows Communication Foundation. MSI returned error code 1603
[04/20/07,08:57:35] Windows Communication Foundation: [2] Error: Installation failed for component Windows Communication Foundation. MSI returned error code 1603
[04/20/07,08:57:54] WapUI: [2] DepCheck indicates Windows Communication Foundation is not installed.
[04/20/07,08:57:54] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0 was not attempted to be installed.
i uninstalled any previous version, is there something i'm missing?
.Net Framework co-existence
newnoise1024 said:
Bootloader Version: SPL-1.40.01pro
IPL-1.01
i just tried to install Framework .NET 3.0 and got this error message
[04/20/07,08:50:20] Windows Communication Foundation: [2] Error: Installation failed for component Windows Communication Foundation. MSI returned error code 1603
[04/20/07,08:57:35] Windows Communication Foundation: [2] Error: Installation failed for component Windows Communication Foundation. MSI returned error code 1603
[04/20/07,08:57:54] WapUI: [2] DepCheck indicates Windows Communication Foundation is not installed.
[04/20/07,08:57:54] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0 was not attempted to be installed.
i uninstalled any previous version, is there something i'm missing?
Click to expand...
Click to collapse
You're probably missing version 2.0 of the .NET framework. .NET Framework is to be left in place once installed. You should have left V 2.0 installed and added .NET 3.0. Go to www.microsoft.com/net and get version 2.0 redistributable re-installed on your machine. (If you can). If you cannot, search the KB and you may get by without rebuilding your OS.
"Head over to Microsoft's site and download a fresh version of Compact Framework .NET (3.0 is the current version). To be extra safe, go into Add/Remove Programs and uninstall any existing versions -- reboot -- then install the new CF Framework. Reboot after installing it -- even though it doesn't tell you to."
this is the advice i was given in this thread, so i uninstalled version 2.0 before installing version 3.0.
So am i screwed now? lol
Well, version 3.0 just installed successfully... does that mean i still need to install 2.0? or am i fine just running 3.0?
Sorry for all the questions, i just want this fixed :/
You should be good. Give it a go.
If not, just dl .Net CF2 and install that. I think you are fine now though.
Edit: never mind
version 2.0 installed fine
Thanks everyone
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!
hi i have a htc touch pro2 from us cellular and im having a problem running emulators on my phone. Ive tried running now both the pocketgba and the pocketgnuboy and i keep getting the same error for both. The error is "The file 'Pocketgnuboy' cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannot be found. If the Proble persists, try reinstaling or restoring the file." Ive saved both of them to my SD card and im not sure if thats the problem.
So if anyone can help and show me what to do to fix this problem and how to do install etc. then it would be greatly appreciated thankxx..
Thread moved to correct section.
I'm pretty sure others will help out soon with advice re. app unlocking (or whatever it is called on modern devices), or sdkcerts or similar, however that error message rings a bell for a different reason... On my previous phone I was using a util to alter shortcut's properties (sorry, it was a while ago now, but the specifics won't matter.) Upon seeing the error msg, I was initially convinced I had somehow restored the phone to it's original status of not trusting unsigned CABs, or not allowing certain software. HOWEVER, I eventually noticed that running the EXEs directly (File Explorer/Resco Explorer/Total Commander) meant the apps would work fine, it was just the start menu's shortcuts that gave that error, but not even on all shortcuts.
Short version, while you wait for a more knowledgeable person to come along and guide you through the more likely/common issues, is try navigating to \program files\YOUR APP NAME\your_app_name.exe , run it. If the program works fine, all you'll need to do is navigate to \windows\start menu\ and delete the non-functioning shortcut, and create a new one.
HIH
Hey guys. After many frustrated days searching for a solution to "The timer ran out on what we were trying to do.", I found today an official solution posted by Microsoft.
So, for those with either:
800705B4: The timer ran out on what we were trying to do.
OR
80180080: We couldn't update your phone because your operating system might be corrupt.
search for "WPSupportTool" in google (Article ID: 2530409) and download for your Windows PC. (Sorry; can't post links!)
This is the best solution so far to update without erasing/reseting your phone. Enjoy!
From their article:
"Try using the Windows Phone Support Tool. The Windows Phone Support Tool is an application that fixes problems that prevent your Windows Phone 7 from updating successfully. The tool only works for the two error codes listed in the Symptoms section."
How can I use the WP Support Tool on Leo - HD2 > it doesn't have "camera button"
I've also been stuck with 800705B4 for months now. Very frustrating.
I believe I've tried everything...
I can't even unlock my SD card because I also get the 800705B4 error when I try to send the unlocker file via cab sender.
Well, I guess we just have to hope until there's a fix for the 800705B4 on HD2
if i use this tool (WPSupportTool) is it going to erase my phone ?
what about interop-unlock ? am i going to loose it ?
i'll really appreciate your answers
Erase phone: REALLY?? Read the first post:
"This is the best solution so far to update without erasing/reseting your phone."
Remove interop-unlock: highly unlikely, although a few updates do that for anybody.
The obvious answer is make sure you have a backup/restore point (if possible) so you can roll back if something gets messed up.