Seems to have been a run on these!
I have an SPV M5000 that was happily-ish running WM6 (as in my sig), and decided to pass it on to someone and put it back to Orange WM5 firmware.
Well, something went wrong, and now it's stuck with no Radio ROM; I've done the MTTY/Task 28 stuff, I've tried every ROM I can lay my hands on, and I'm having a couple of basic issues:
If I use the generic RUU update, it doesn't want to write the ROM. It just sits there at 0% with the device presumably waiting to get something. Eventually it times out with error 114. Then goes into recovery, and crashes.
If I try any others, including the Orange ROM, it complains that it has an invalid country code. Since this WAS a UK M5000, I used Jwright's M5000 ROM, and I have no idea why this would be changed or broken.
Obviously the bootloader appears to be working, but I don't seem to be able to get a Radio ROM onto it. I'm using an iMac booted into Windows XP since my Vista machine is, well, running Vista.
I really don't want to throw this unit away (and trust me, if I can't make it work by the time I give up it WILL be hurled into the nearest solid object then beaten to a pulp with my iPhone).
Well, I've tried everything on the forum; it's refusing to accept a Radio ROM, even though I've flashed the other parts with success. The only thing I haven't tried is SD-card upload since no-one has actually said "how" this works - how to prepare the SD card for use, for example, what the file should be - so I assume nobody knows this.
I've even tried the MTTY "erase" commands as suggested by Pof, and pretty much the only thing left is trying to update with the Linux tool that won't really help me much as I don't have a Linux setup.
I must admit that with the level of expertise on these forums, I can't find a solution to this, but with all of that - and no doubt if anyone was awake to read this I'd have been told to search (which is, of course, what I've been doing for the past 5 hours, along with flashing, rebooting, trying different cables, etc) - and still no working machine, I can only assume my M5000 is scrap due to some weird bug. Not worth spending money on to repair.
So, how shall I destroy it? Run over it with the car? Switch it on (obviously everything APART from GSM is working fine, with the lovely extended battery) and then set fire too it and see how long it'll run for? Freeze it? Smack it with a large hammer? Drive to Dover and see if I can get a strong enough catapult to send it to France, where it will HAVE to unlock itself by law?
(Edit: Tried it with the FlipStart; clean install of ActiveSync 4.5 - still nothing).
What's that stuff about "device ID not compatible"?
01:56:49:905 [msg] : Version : [2.11].
01:56:49:905 [msg] : Config Info : [857873],[1],[0],[0],[1],[0],[0],[1].
01:56:49:968 [msg] : MSystemFile Not Exist !
01:56:49:968 [msg] : CEFile Not Exist !
01:56:49:999 [msg] : Current in CE Mode.
01:56:54:280 [msg] : Device BL VER : [] [].
01:56:54:280 [err] : Device CID Error.
01:56:54:280 [msg] : Update Image. CE : [0], MSystem : [0], Radio : [1]
01:56:59:046 [msg] : Check Ac in CE mode. AC : [1]
01:56:59:046 [msg] : IsBL. BL : [0]
01:57:03:280 [msg] : Enter BL OK.
01:57:07:296 [msg] : Disconnect ActiveSync .... [2]
01:57:07:296 [msg] : Start Get Connect Port.
01:57:07:468 [msg] : Current in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.
01:57:29:187 [msg] : Get Device Backup ID.
01:57:29:187 [msg] : Device BL VER : [1.01 ] [].
01:57:29:187 [msg] : Device ID Is Incompatible.
01:57:31:187 [msg] : =============================================
01:57:31:187 [msg] : START UpdateRadio !
01:57:40:077 [msg] : Check Radio Level 0 [704].
01:57:41:655 [msg] : RUpgrade 0 : 0 Start.
02:02:22:952 [err] : RWipe Data Error.
02:02:23:421 [err] : BL UpdateRadio Error.
02:02:23:421 [msg] : START UnInitialization !
02:02:23:437 [msg] : END UnInitialization !
02:02:28:812 [msg] : START UnInitialization !
02:02:28:812 [msg] : END UnInitialization !
Click to expand...
Click to collapse
Was the device unlocked before flashing to wm6? You could also try flashing on a Windows XP machine..hope this works for you.
Or try this..Got it from Laurentius
1) The radio stack is screwed, you don't get GSM signal and the phone says unknown SIM status
2) Device won't start after trying to unlock it with HTC Universal Unlocker (HTC_Uni_SIM_Unlock_v1)
Here is how to fix it:
1)Disable activesync on your computer by right click on activesync icon -> connection settings -> uncheck "allow USB connections". (( Done! ))
2)Put your Hermes (( Universal )) in bootloader mode
3) Connect device to computer using USB cable. (( Done with Original Cable ))
4) Open mtty.exe and select USB port, then connect.
Hit enter twice, you will see the "USB>" prompt. (( Okay but i usually get the USB> prompt with single hit of Enter ))
Type the following commands (do not copy paste!!!) (( I type them ))
USB> password 0000000000000000 (( Returns: HTCSPass1.CMˆËHTCEUSB> ))
USB> set 1e 1 (( Returns: USB> ))
USB> erase a0040000 c80000 (( Returns: HTCST ÚÈÒHTCEUSB> ))
USB> erase a0cc0000 c80000 ((Returns: HTCST ÚÈÒHTCEUSB> ))
USB> erase a1940000 640000 (( Returns: HTCST ÚÈÒHTCEUSB> ))
USB> set 1e 0 ((Returns: USB> ))
(( Then i close the window of MTTY and proceed to step 5 ))
5) Reset your phone and put it back in bootloader mode (( Here i take my Universal off the usb cable, soft reset it with the stylus and without letting it to boot i switch it into the bootloader mode again and get "Serial & v1.01" on the screen's header and footer ))
6) If your bootloader version is different than 1.04 then Flash Bootloader version 1.04 (( I simply ignore this step as this could be for Hermes users only not for UNIVERSAL Users - Pls. correct me if i'm wrong ))
7) Flash the patched radio used to simunlock the Hermes (( I do it with HTC_Uni_Unlock_v1 it has radio version 0.00.00 BUT still it gets stuck at 0% and after sometime gives the same error 114. Cannot Update Radio ROM ))
Your phone should be alive again (( Its Not ))
<---]]]]
clemsyn said:
Was the device unlocked before flashing to wm6? You could also try flashing on a Windows XP machine..hope this works for you.
Click to expand...
Click to collapse
Um...
I'm using an iMac booted into Windows XP
The FlipStart is also running Windows XP.
And it was SIM-unlocked by Orange; it wasn't SuperCID, and I flashed the "Orange M5000" version of Jwright's Crossbow ROM with no issues (apart from the Crossbow bugs).
clemsyn said:
Or try this..Got it from Laurentius
1) The radio stack is screwed, you don't get GSM signal and the phone says unknown SIM status
<snip>
Your phone should be alive again (( Its Not ))
<---]]]]
Click to expand...
Click to collapse
Tried that, one of the first ones I found. Now IIRC the bits in brackets are his results as he tried it. The last line says it didn't work. Which is precisely what happened for me, too!
At present the ROM update won't progress at all. Before it would reach 99% then fail. I'm wondering if the battery, despite showing 100%, is actually not charging correctly and it needs more power to erase the Flash.
Well, let it charge all night in case it was a power issue (it has a high-capacity battery), tried the Radio ROM, tried the 'task 28' path, tried Universal_SIM_Unlock with MaUpgradeIt - wiped the ROM, no problem reflashing with CE/ExtROM, but no Radio. Just cannot install it period.
Task 32 gives me FF - CID is corrupted, basically. Can't flash Radio 0.00.00, can't flash any radio at all.
Is there any way around this, or is it (as it seems from extensive forum searches including Buzzdev) scrap now? Is there a way to flash an ID to it, and if so, is there any way that the IMEI is damaged, or if so restorable, or will the phone be useless even if I can get a ROM onto it?
I don't get it, as I did nothing stupid with this; I've flashed loads of devices, I even flashed (and risked bricking in a BIG way) a brand new iPhone without headaches. Seems to be a lot of Universals suffering this lately - what is causing it?
Have u tried task 28 55aa
clemsyn said:
Have u tried task 28 55aa
Click to expand...
Click to collapse
Again, from the first post in the thread:
"Well, something went wrong, and now it's stuck with no Radio ROM; I've done the MTTY/Task 28 stuff, I've tried every ROM I can lay my hands on, and I'm having a couple of basic issues:"
I appreciate the attempts to help, but what I am looking for is some insight into what has gone wrong, not blind attempts to try any solution - I've tried it all already in the hope something would work. I think that the issue is very low-level, and I don't know how it becomes corrupted - but I have a suspicion that many Unis have been bricked in the same way and the reason no-one has posted a definitive solution is that there isn't one.
you did not mention if you were flashing with the SD card inserted into the unit (or have you but I failed to read it).
there is one flashing problem here somewhere and the issue was solved when the SD card was removed from the Uni before flashing.
Good question, and no - no SD card, no SIM card; I think I remembered this from the original Uni_Unlocker stuff which I'd been going to try before finding out Orange would unlock it for me anyway.
In fact, I'd like to try flashing FROM SIM card if anyone could provide a dump, but no-one seems to have been able to in the threads I have read - since the information about how the SD-Flash works is somewhat scarce, the service manual says "you can", but not what format the data should be in, or how the process works. Merely, how it can be initiated.
And I also suspect that with corrupted CID, I couldn't access the flash routines anyway, since all the radio flash tools appear to depend on this Sec level being "open". Some sort of direct hardware flash - maybe via JTAG - may be the only way around it, though I noticed the Hermes solution which runs under Linux would appear to work by "forcing" the data somehow.
I have the same problem. And confirm, can not upgrade...
... by SDCard, because I get and error :
"Update not allowed!"
The situation is:
- All ROms WinCE updated run OK! and function correctly: Wifi, Bluetooth...
- All Extended updated ROMS run OK!
- But any Radio Rom cannot ben updated, include the special Rom of Buzz.
I have the same error 114. Device Display "NO GSM", and not have IMEI, not have Protocol.... The phone is OUT of Service.
The problem is the CID is scratched or the Radio bootloader is broken. After 2 years there is still no solution For the Universal devices, But for devices Hermes If there is solution:
http://forum.xda-developers.com/showthread.php?t=286755
please guys, pof, buzzz, HEEELP for The Universal's brickeds Devices
¡¡pleasee....!!
p.d.: (sorry for my bad english)
Related
Hi all,
last night I decided to update my MDA Pro with the latest I-mate rom and everything went wrong. I got stuck in the bootloader and whenever I try to update the rom with MaUpgradeUt_noID tool the process stops at 7% and returns the error message in the title. Now all I can do is to get to the bootloader, the hard reset does nothing. Moreover I cannot upgrade the extended rom at all giving me Error 113 at the very beginning of the update. All I can do is to upgrade radio rom. This is a copy of my RUU.log (last part):
00:36:34:516 [msg] : =============================================
00:36:34:516 [msg] : START UpdateExtended !
00:36:35:597 [msg] : Upgrade 2 : 0 Start.
00:36:40:845 [err] :
BUF->{HTCSF kEŘ(HTCEUSB>}
00:36:40:845 [err] : Receive Data Error : 609 .
00:36:41:075 [msg] : Retry Write data Start.
00:36:56:788 [err] : Write Data Error.
00:36:56:788 [err] : BL UpdateExtended Error.
00:36:56:788 [msg] : START UnInitialization !
00:36:56:798 [msg] : END UnInitialization !
00:36:56:798 [msg] : IsBL. BL : [1]
I must stress that I unlocked the extended rom before the upgrade and had some software installed there. Could that cause the problem? Do I have a brick now?
One more thing: I did "task 28" in mtty utility and I got that:
USB>task 28
Read data error in tag
DOCInfoTableinitHW+
Binary0 Size: 0x100000
MountVolume:status=23.
FAT0 Size: 0x0
FAT1 Size: 0xA00000
FAT2 Size: 0x2C40000
All Size: 0x3740000
FAT0_ADDR=0x100000,FAT1_ADDR=0x100000,FAT2_ADDR=0xB00000
My FAT0 is f...ed up. Is there any way I can correct this? There must be a tool for overwriting the partition table...
UPDATE: contacted T-Mobile. They're gonna have a look at this and try to fix it, but... there must some way to fix the partitions at home!!! Anyone?
Any help would be greatly appreciated, folks!
I know you have your own problems, guys, but cannot anybody at least say something sensible about my problem?
I don't know but .. seems a problem similar to ...
Vaterland said:
I know you have your own problems, guys, but cannot anybody at least say something sensible about my problem?
Click to expand...
Click to collapse
read this post ...
http://forum.xda-developers.com/viewtopic.php?t=49951
ciaus
T-Mobile contacted me today. Result - a bill for replacing the motherboard = 500 Euro. F-word is the most appropriate here. I can't believe they have no utilities for correcting the problem programmatically. Anyway, told them to go and f-word themselve. Guys, if you think you are MDA Pro gurus then this is the real challenge – make this sucker working. Any ideas how?
Ps. The link from above does not answer my question. The update process stops half way through and never gets completed. Clearly, the problem is the partition table. How to correct that? PLEASEEEEEE
UPDATE: looks like there is no solution to this problem without sending it for motherboard replacement I am not letting T-Mobile scamming me! Why don't they replace just the DOC??
Not everything is lost
I'm not sure what happend. One possibility is a damaged download another a defective flash rom.
If it's the first, download T-Mobiles Update again and try to flash it.
If it's the second, demand repair under waranty.
Upgrading the ROMs with newer software versions is something the user can do and even is encuraged to do. So it should not damage your device.
Just don't mention you tried to upgrade your Universal with software not provided by your network operator. If you did so, that is
Hi, the last software loaded on to the Pro was T-Mobile's. The radio rom upgrade went ok and if they can read DOC, then they should see it. But the "monkeys" in the service only connected it to a computer, tried to flash it and once they saw "Model ID" error they immediately came up with the conclusion that I was trying to upgrade it with "illegal software" (as they call it). The thing is that any attempt to upgrade ROM from different vendors gives "Country ID" error. I won't give up. I'll demand to repair it under warranty. We'll see how this is going to end...
Broken Radio ROM blocks official O2 rom, MaUpgradeUt_noID.exe fails "error 114"....
Hello
I hope someone here is able to help me.
I have spent the whole of the last 48 hours (no sleep) trying to fix my O2 XDA Exec. I *believe* that I have tried everything suggested on this forum and on Buzz's site but there is just so much on here now that I may well have missed something.
History:
Over the last few months, my phone has gradually got more inconsistent - dropping calls, refusing to answer calls, losing signal and so on. On Jan 1st, I turned it on and it had lost all my settings - Opera reg code, Wifi encryption, O2 net settings, etc.
I spent the last week with sometimes having network, sometimes not. Finally it just gave up altogether. In Settings>System>Device Info, "Radio Version", "Protocol version" and "IMEI" are all completely blank. When booting, the red text states "No GSM".
Reading around this site it appeared that I should be able to reinstall the radio ROM from the official O2 download however this errored with the Incorrect Country Code error. I have carried out full hard resets and still cannot get any Radio ROM visible. I assume that the lack of IMEI is affecting the official O2 downloads?
Since then, I have tried most variations on this site of ROM installs using MaUpgradeUt_noID.exe suggested in the wiki (with and without entering mtty code: "set 14 0").
Full three-part ROM and radio-only ROM install attempts all fail with the Error 114 "Radio Rom Update Error" (the radio ROM is always attempted first).
The only success I have seen was an update of Bootloader from 1.00 to 1.01 which worked completely perfectly and proved that the PC can indeed connect to the XDA when it feels like it.
After two days of earning no money ( I am self-employed) and no money to spend on support, I wonder if anybody has another suggestion for me?
In case it helps: ROM version: 1.30.107 WWE, ROM date: 04/11/06, ExtROM version: 1.30.162 WWE
All advice welcome
Thanks
Leapy
extract everything from the exe and do an upgrade without the radio.nbf
did you read what he said? its the radio that's bad and needs replacing
i don't know, sorry
poussin69 said:
extract everything from the exe and do an upgrade without the radio.nbf
Click to expand...
Click to collapse
I am now totally confused.
I know there was a smiley at the end of your comment, I just can't work out if you are being funny or astute (or both?). Can you explain how reinstalling the non-radio ROMs will help? Would that restore the IMEI?
TIA
Leapy
Midget_1990 said:
i don't know, sorry
Click to expand...
Click to collapse
Thanks for responding anyway. At least I am not crying alone in the wilderness.
It would be terrific to find a fix, though.
Try to flash the radio from Buzz's unlocker with MaUpgrade_NoID.exe
http://www.buzzdev.net/index.php?option=com_content&task=view&id=78&Itemid=1
pof said:
Try to flash the radio from Buzz's unlocker with MaUpgrade_NoID.exe
Click to expand...
Click to collapse
Thank you for the suggestion, I just tried as you proposed. "Error 114 - Radio ROM Update Error" *sob*!
It's a real shame. It's actually the ideal phone for my needs.
Leapy
1. Disable Activesync (connection settings -> uncheck "allow USB connections").
2. Put universal in bootloader mode
3. Connect device to computer using USB cable.
4. Start HHD Usb monitor (trial version is OK).
5. File -> New session -> USB Monitor -> Select USB device where your phone is connected -> Check "request view" -> Finish
6. In the upper part there are two tabs: basic and complete. Click on "Complete".
7. Click on MaUpgrade_NoID.exe and start the radio flashing process, if everything went fine you should see all the USB traffic output on USB monitor window.
8. When radio upgrade fails, click on Edit -> Export and Save as type "ANSI Text files".
9. Save the text file and zip it.
10. Attach the output here or upload it to ftp if it's too big.
Only with this we can see exactly why it fails
Good luck!
http://forum.xda-developers.com/showthread.php?p=994444#post994444
first as recomended i disabled usb from activesync
then downloaded mtty 1.42
connected the usb and started mtty
chose usb
white screen.....
typed set 14 0...
some gibrish on the screen....
ran the rom update....but it informed me that the rom is not for my device...
typed task 0 in mtty (not sure bout the command but its on page 2 of the forum)
ran the update....nothing same error....
now i saw that my universals screen was blank....
removed the battery....and then restarted my universal....
this might help you...
rtask 0/1/3/4
pof said:
1. Disable Activesync (connection settings -> uncheck "allow USB connections").
2. Put universal in bootloader mode
3. Connect device to computer using USB cable.
4. Start HHD Usb monitor (trial version is OK).
5. File -> New session -> USB Monitor -> Select USB device where your phone is connected -> Check "request view" -> Finish
6. In the upper part there are two tabs: basic and complete. Click on "Complete".
7. Click on MaUpgrade_NoID.exe and start the radio flashing process, if everything went fine you should see all the USB traffic output on USB monitor window.
8. When radio upgrade fails, click on Edit -> Export and Save as type "ANSI Text files".
9. Save the text file and zip it.
10. Attach the output here or upload it to ftp if it's too big.
Only with this we can see exactly why it fails
Good luck!
Click to expand...
Click to collapse
Thank you. I think I did everything exactly as you instructed.
Please find attached the zipped log file.
I would welcome your advice.
Leapy
Radio is corrupted, and device cannot check SecLevel (wait interpreter timeout), it returns default seclevel=FF (unprivileged) and correct CID (O2___001), however when switching to radio bootloader to upgrade the radio, device doesn't answer to any 'rerase' command, that's why the utility gives out flashing after receiving no response to 3 "rerase 0 10000" commands.
Probably this is a bit "crazy", but if it is your last chance... try the following commands in mtty, and try to upgrade the radio again after this:
Code:
USB> password 0000000000000000
USB> set 1e 1
USB> erase a0040000 c80000
USB> erase a0cc0000 c80000
USB> erase a1940000 640000
USB> set 1e 0
Don't do it if you can fix your device by any other means (warranty, service centre, etc...) because I'm not sure if it will work or not
Error 114: Radio Rom Update Error
WOW I have the same problem.....
but this commands for mtty...did nothing to my problem.
ERROR 114: RADIO ROM UPDATE ERROR
I don't know if that helps you....on my PDA it says Upgrade Radio Stack Please Wait...
I have the perfect phone....but it is not a phone anymore...and I go crazy.
Is there any way to update the radio rom from SD card??
Please Help
posted reply to incorrect post - cannot delete post - ignore. Please see next post.
pof said:
Radio is corrupted, and device cannot check SecLevel (wait interpreter timeout), it returns default seclevel=FF (unprivileged) and correct CID (O2___001), however when switching to radio bootloader to upgrade the radio, device doesn't answer to any 'rerase' command, that's why the utility gives out flashing after receiving no response to 3 "rerase 0 10000" commands.
Probably this is a bit "crazy", but if it is your last chance... try the following commands in mtty, and try to upgrade the radio again after this:
Code:
USB> password 0000000000000000
USB> set 1e 1
USB> erase a0040000 c80000
USB> erase a0cc0000 c80000
USB> erase a1940000 640000
USB> set 1e 0
Don't do it if you can fix your device by any other means (warranty, service centre, etc...) because I'm not sure if it will work or not
Click to expand...
Click to collapse
Well, I too am a little "crazy" so I did as you suggest.
I tried to put Buzz's "unlock" radio v 0.0.0.0 ROM on using MaUpgradeUt_noID.exe. And guess what, it fails again but with a different error!
Error 150: ROM UPGRADE UTILITY ERROR. "This rom upgrade utility is not designed for your device. Please get proper ROM Upgrade Utility and try again!"
I attach the USB Monitor log if it proves any use?
I will try and use the official O2 ROMs and see how that goes.
Thanks again for your assistance, I truly appreciate it.
Leapy
To Leapy...
How did this problem started to you??
I have been using this phone for 1 week, after that I changed my SIM card with another one called MAGIC-SIM card, (programmable) with 8 SIM numbers.
After that day ALL the **** started!!!!!
I had problems during my dialing the number on phonepad...
when I was trying to make a call... it hang up.
After some soft reset...it didn't ask me for PIN.
After a hard reset.... on boot screen it said NO GSM
and then on antenna icon on the top of the screen the antenna had a little x on the right side.
Then the known problem ERROR 114: RADIO ROM UPDATE ERROR
I can update any rom I want but not the Radio ROM
leapy said:
I will try and use the official O2 ROMs and see how that goes.
Click to expand...
Click to collapse
well, I tried the O2 update and just got the generic "CID" error - twice. So I guess I am no nearer fixing this issue...
All advice welcome.
Leapy
leapy said:
Well, I too am a little "crazy" so I did as you suggest.
[...]
I attach the USB Monitor log if it proves any use?
Click to expand...
Click to collapse
Sorry but the capture was from the erase commands... not from the failed radio flash... please try to flash 0.0.0.0 radio again and attach the right capture... also make sure activesync is not running when starting the radio upgrade, and if it fails once, run MaUpgradeUtility twice without disconnecting the device from USB.
my friend got the exact same problem with his EXEC, and send it back to O2, they charge him apprx USD500 for mainboard replacement.....(fiuhh.....)
pof said:
Sorry but the capture was from the erase commands... not from the failed radio flash... please try to flash 0.0.0.0 radio again and attach the right capture... also make sure activesync is not running when starting the radio upgrade, and if it fails once, run MaUpgradeUtility twice without disconnecting the device from USB.
Click to expand...
Click to collapse
Thanks for your continued assistance.
I tried twice with the 0.0.0.0 radio ROM and this time the error has reverted to Error 114 again. With both these attempts, I noticed that the displayed "currently installed" ROM versions were blank - previously I saw the actual on-board version numbers. Not sure if that indicates anything?
Capture logs attached:
leapy said:
Not sure if that indicates anything?
Click to expand...
Click to collapse
That indicates you previously had activesync enabled and now don't.
Exactly same error as before, radio bootloader is not responding when the RUU sends 'rinfo' and 'rerase' commands to it, then the RUU gives up trying.
You can backup the radio ROM from another device with "d2s 60000000 00800000", and theoretically you should be able to load it into yours by using "L" command... but I'm not experienced with universal bootloader and can't say for sure if this will work and the right commands to do it... so please wait until someone reads this and can help you more than me, or research by yourself if you have the time to do it
i wonder if anyone could help me with my problem!
i can't upgrade / Install RADIO ROM (any) in my UNIVERSAL. what happens is that it doesn't starts and when rebooting it says NO GSM where the versions are mentioned in red.
my universal goes in the bootloader mode properly and the update or RADIO ROM Starts; but it stays on 0% and doesn't move ahead. after a while and error comes ERROR 114. Can't update RADIO ROM.
This all happened when i was trying to downgrade my radio rom from 1.14.01 to 1.13.00 this morning and it stopped at 66% with giving this messege.. cannot upgrade radio rom... since then i am unable to re-install radio rom. However i am able to install WIN CE ROM and EXT ROM but not radio ROM.
can you guys help me somehow?
farehmani.
farehmani said:
i wonder if anyone could help me with my problem!
i can't upgrade / Install RADIO ROM (any) in my UNIVERSAL. what happens is that it doesn't starts and when rebooting it says NO GSM where the versions are mentioned in red.
my universal goes in the bootloader mode properly and the update or RADIO ROM Starts; but it stays on 0% and doesn't move ahead. after a while and error comes ERROR 114. Can't update RADIO ROM.
This all happened when i was trying to downgrade my radio rom from 1.14.01 to 1.13.00 this morning and it stopped at 66% with giving this messege.. cannot upgrade radio rom... since then i am unable to re-install radio rom. However i am able to install WIN CE ROM and EXT ROM but not radio ROM.
can you guys help me somehow?
farehmani.
Click to expand...
Click to collapse
Radio rom upgrades are definately more reliable with the original cable. I have read somewhere in these forum that the mode of radio ROM upgrade is different from other ROMs (CE and Ext rom) this is the reason why it takes more time than the CE rom although the later is much larger in size. I suggest you try again if possible on a different PC. For some strange reason I can upgrade my Radio ROM only in my office PC.
d_ranade said:
Radio rom upgrades are definately more reliable with the original cable. I have read somewhere in these forum that the mode of radio ROM upgrade is different from other ROMs (CE and Ext rom) this is the reason why it takes more time than the CE rom although the later is much larger in size. I suggest you try again if possible on a different PC. For some strange reason I can upgrade my Radio ROM only in my office PC.
Click to expand...
Click to collapse
i have tried on 3 different computers but it doesn't work. also with original cable too. it is definately a software problem as no physical damage was made to my device. there must be something that fixes it.
still while upgrading Error 114. (UNABLE TO UPDATE RADIO ROM)
i wish i could find any help with this...
Farehmani
farehmani said:
i have tried on 3 different computers but it doesn't work. also with original cable too. it is definately a software problem as no physical damage was made to my device. there must be something that fixes it.
still while upgrading Error 114. (UNABLE TO UPDATE RADIO ROM)
i wish i could find any help with this...
Farehmani
Click to expand...
Click to collapse
Have you tried putting the unit into Bootloader before you start the upgrade - I find that more reliable?
apd said:
Have you tried putting the unit into Bootloader before you start the upgrade - I find that more reliable?
Click to expand...
Click to collapse
I too find that upgrade in Bootloader is more reliable.
To let you into a little secret.. I ALWAYS flash now in Bootloader mode.. I have only had a couple of "bad flashes" but all of them were direct from a running OS...
I have sent you a pm, that should solve your issue. Please check your pm's...
Take care,
-Jwrightmcps
farehmani said:
i wonder if anyone could help me with my problem!
i can't upgrade / Install RADIO ROM (any) in my UNIVERSAL. what happens is that it doesn't starts and when rebooting it says NO GSM where the versions are mentioned in red.
my universal goes in the bootloader mode properly and the update or RADIO ROM Starts; but it stays on 0% and doesn't move ahead. after a while and error comes ERROR 114. Can't update RADIO ROM.
This all happened when i was trying to downgrade my radio rom from 1.14.01 to 1.13.00 this morning and it stopped at 66% with giving this messege.. cannot upgrade radio rom... since then i am unable to re-install radio rom. However i am able to install WIN CE ROM and EXT ROM but not radio ROM.
can you guys help me somehow?
farehmani.
Click to expand...
Click to collapse
apd said:
Have you tried putting the unit into Bootloader before you start the upgrade - I find that more reliable?
Click to expand...
Click to collapse
yes... i have never tried to flash anything while being in the os. always switch my device to the bootloader first. I have BootLoader 1.01
Please help!!
apd said:
Have you tried putting the unit into Bootloader before you start the upgrade - I find that more reliable?
Click to expand...
Click to collapse
How to put the PPC in Bootloader (Qtek900)?
myname70 said:
How to put the PPC in Bootloader (Qtek900)?
Click to expand...
Click to collapse
Read the wiki - the answers are in there.
apd said:
Read the wiki - the answers are in there.
Click to expand...
Click to collapse
the problem is still there....
i have tried circumvent bootloader password too... and getting error like Win32 Error, Cannot read from the specified device when HEX of password is placed on the memory field of WinDbg.
Tried Another solution for NO GSM but no luck !!
okay here goes; your quoted link had point#5 for no GSM when booting so i followed it as given below.
Pls. see the comments in (( )) for how i conduct these steps and what value is returned.
[[[[--->
Problem 5: Device shows NO GSM when booting (( I'm having this problem ))
1) The radio stack is screwed, you don't get GSM signal and the phone says unknown SIM status
2) Device won't start after trying to unlock it with HTC Universal Unlocker (HTC_Uni_SIM_Unlock_v1)
Here is how to fix it:
1)Disable activesync on your computer by right click on activesync icon -> connection settings -> uncheck "allow USB connections". (( Done! ))
2)Put your Hermes (( Universal )) in bootloader mode
3) Connect device to computer using USB cable. (( Done with Original Cable ))
4) Open mtty.exe and select USB port, then connect.
Hit enter twice, you will see the "USB>" prompt. (( Okay but i usually get the USB> prompt with single hit of Enter ))
Type the following commands (do not copy paste!!!) (( I type them ))
USB> password 0000000000000000 (( Returns: HTCSPass1.CMˆËHTCEUSB> ))
USB> set 1e 1 (( Returns: USB> ))
USB> erase a0040000 c80000 (( Returns: HTCST ÚÈÒHTCEUSB> ))
USB> erase a0cc0000 c80000 ((Returns: HTCST ÚÈÒHTCEUSB> ))
USB> erase a1940000 640000 (( Returns: HTCST ÚÈÒHTCEUSB> ))
USB> set 1e 0 ((Returns: USB> ))
(( Then i close the window of MTTY and proceed to step 5 ))
5) Reset your phone and put it back in bootloader mode (( Here i take my Universal off the usb cable, soft reset it with the stylus and without letting it to boot i switch it into the bootloader mode again and get "Serial & v1.01" on the screen's header and footer ))
6) If your bootloader version is different than 1.04 then Flash Bootloader version 1.04 (( I simply ignore this step as this could be for Hermes users only not for UNIVERSAL Users - Pls. correct me if i'm wrong ))
7) Flash the patched radio used to simunlock the Hermes (( I do it with HTC_Uni_Unlock_v1 it has radio version 0.00.00 BUT still it gets stuck at 0% and after sometime gives the same error 114. Cannot Update Radio ROM ))
Your phone should be alive again (( Its Not ))
<---]]]]
i don't think i'm doing anything wrong here... just the step 5 of bootLoader Update to 1.04...
what comes in your mind ???
i'm desperately missing my pda. its begun to hurt now... please help me rescue my baybee....
farehmani
farehmani said:
i don't think i'm doing anything wrong here... just the step 5 of bootLoader Update to 1.04...
what comes in your mind ???
i'm desperately missing my pda. its begun to hurt now... please help me rescue my baybee....
farehmani
Click to expand...
Click to collapse
Don't worry, mate, you're almost there...
Don't worry about the bootloader version, that is just for the Hermes (Universal will be 1.01 or under for G3, 2.1 for G4). If it's under 1.01 it would be worth upgrading to 1.01 which you can find on the ftp.
SpyderTracks said:
Don't worry, mate, you're almost there...
Don't worry about the bootloader version, that is just for the Hermes (Universal will be 1.01 or under for G3, 2.1 for G4). If it's under 1.01 it would be worth upgrading to 1.01 which you can find on the ftp.
Click to expand...
Click to collapse
glad to know about my being almost there... still i wonder whats keeping me away from retaining my device...
i have already got BootLoader 1.01...
what other method should i apply to get it working again?????
I have the same problem, but not in Universal, but apache, jwright help me.
i have the same problem can smeone help
Try this
"Type "task 28 55aa" and hit enter.
This will restore the DOC partition to its original layout and delete all data
including the ROM!
Once finished you must use the "Original OEM ROM" (i.e. JASJAR WWE
1.30.76) that is made for your device and update with it (CE,Extended
and Radio).
Also if your device bootloader version is lower than "v 1.01" you should
update that first (before installing the OEM ROM, but NOT before "Task
28 55aa").
After this is complete you may then use your device again.
Please let me know how things work out for you...
Take care,
-Jwrightmcps"
It solve me...
i am having the same problem with exec it shows me no gsm and when i go to the device information it does not shows the radio ver and my phone imei is 0 can someoe please tell me how do i solve the problem i had read this tread but not understand it can someone please explane me how do i solve the problem
shedragon said:
"Type "task 28 55aa" and hit enter.
This will restore the DOC partition to its original layout and delete all data
including the ROM!
Once finished you must use the "Original OEM ROM" (i.e. JASJAR WWE
1.30.76) that is made for your device and update with it (CE,Extended
and Radio).
Also if your device bootloader version is lower than "v 1.01" you should
update that first (before installing the OEM ROM, but NOT before "Task
28 55aa").
After this is complete you may then use your device again.
Please let me know how things work out for you...
Take care,
-Jwrightmcps"
It solve me...
Click to expand...
Click to collapse
thanx for your suggestion!
i had tried this already... but the problem is beyon this...
i discussed with pof and he said that somehow i screwed up with the qualcomm chip where the radio bootload resides. so it needs replacement.
anyways... thanx budd... i appreciate your support too...
regards...
my hermes having this problem also ((
I can't up radio with error 114;I tried some radio with Rom 02 2005 ver 1.33.But it's not better.I've read many resolutions and do it on my fone.(use MTTY with command:task 28 55a;set 14 0;rtask 0). Hix,the fone still error.Help me,plz.
Sorry about i can't impress myself very well in English.Thanks alot.
the same problem
Currently I have wm6 with rom ver.2.07.02 ran and radio ver 1.13.00. I would change OS for another one but at the begin of instalation process the error 114 shows up on my computer screen. I've checked many posts and i couldnt find any siutable solution for my situation. Please, be so kind and help what i can do to install another OS. thx in advance.
I too am experiencing the same problem - my attempts at resolution are as above with equally crap results. After attempting to update the ROM and Extended ROM only I find the device no longers gets as far as even the bootscreen.
edit: Okay, so after flashing a new ROM and Extended ROM I tried flashing just the new Radio ROM (1.17) but it still reported a 114 error. On a hunch I stopped using the update files I was using and used the ones from the RANJU_V2 ROM instead (that worked the last time I updated) - I'm now updating with a new Radio ROM, 114 error averted...
-- PROBLEM SOLVED --
Solution: Use a different upgrade utility (one that you know works on your device)
-sf
Hi Starfux
congrats.
but please be more elaborate in terms of :
your device.
your device brand (o2, vodafone etc)
the upgrade utility that worked.
the rom that worked.
many thanks
AB
device = HTC Universal (which is why I'm in this forum...)
brand= O2 Exec
upgrade utility that worked = Upgrade files from RANJU_V2 ROM (as I said previously - at least read my post!) either way, if you have ever flashed a ROM and made it work just replace the ROM file in that set of files and use that - the point here is that it worked for me with a different upgrade util, it's not meant to be a spoonfed step-by-step tutorial.
rom that worked = I don't recall, it was a while ago now (just stumbled back upon my old post and the subsequent question).
I'll make better notes next time but I (a) didn't expect it to work and (b) don't have much time spare to mess about with this stuff, let alone write tutorials - I posted back in case it helps somebody, that's all.
HTH,
-sf 8)
WORKING SOLUTION!!! (at least....for me!)
I was going mad with the Error 114: Radio Stack Update Problem from time to time. Rebooting many times pc or soft/hard resetting my universal didn't solve the problem.
I read maybe hardware problems, but this seemed impossible in my situation
With certain update utilities all went fine, with other I couldn't update, and with the sure to be working utilities I wasn't able to update certain roms........ARRRGGHH.......It was driving me crazy.......
Then I tried to run the wcescomm.exe process manually ........et voila.....problem solved !!!!
I'm currently updating to ranju v7.4 , and retesting 1.18 radio, with 0 problems.
I updated the wiki.....error 114 and 144 was both for the same radio stack update error, but with different utilities (if I can remember correctly!)
Any news to resolve Error 114 ? Dianotea can you explain your procedure more detailed? What do you mean "run the wcescomm.exe process manually" ?
For StarFux, can you give me a link for RANJU_V2 ROM ?
in windows click on start ---> run ----> type "wcescomm" (without the quotes) and then click ok ; if it gives you an error you need to reinstall activesync, if no error is given, and nothing seems to happen (process wcescomm run in background), then there are great chance you resolved the error.
Restart your pda and start again bootloader mode, then reflash....
At least, this worked for me flawlessy.......
Thanks, I try it but don't work. I hope someone can resolve the problem in another way.
Upgrading again uni, and another time the radio 114 error.....argh!!!
After 5 attempts my solution was to connect the uni in normal (non-bootloader) mode. Re-Check it has correct communication and activesync-driver is correctly installed in device manager.
Then just after that (same session-no restart!) I pulled out the usb cable from the uni and restarted in BL mode.
This time the upgrade (noid version) run without errors......
dianotea, please can you wrote how to check activesync-drive in device manager and when you have re-inserted the usb cable in bootloader mode? Thanks.
If you have xp, right click on "my computer"-->manage-->device manager. Check that you have Windows CE USB device (and Microsoft USB sync as sub-device).
This should appear in both normal and bootloader mode.
You should hear the activesync sound when you connect the uni in normal mode.....
I found that when I was receiving the error I did not hear the AS sound when connecting the uni in normal mode.
I re-inserted the cable in BL mode just before flashing, but the main problem is not WHEN you insert the cable, but is checking that your device correctly syncs and "speaks" with the activesync processes.
Hope this helps....
I have not Windows CE USB device in my device manager. What can i do?
Vista or WinXP?
You could try reinstalling activesync (what version is yours, actually?)
i have winxp sp2. I have reinstalled activesync 4.5 again and it works fine but when i click on device manager there is not any windows CE USB device
Could you try another AS version? Do you have AS 4.5.5059 (check in the property of your .exe files....)?
I have 4.5.5096 version of AS. The previuos version 4.2 doesn't work with windows mobile 6. How can i active the window ce usb device?
It's not a problem of ActiveSync. Now i have Windows CE usb device in my device manager but I can't update may radio rom again, it's stop at 0%. This is may log file error:
00:13:24:109 [msg] : Version : [2.11].
00:13:24:140 [msg] : Config Info : [857873],[1],[0],[0],[1],[0],[0],[1].
00:13:28:406 [msg] : Current Not in CE Mode or in CE Mode but ActiveSync Not Connected.
00:13:32:500 [msg] : Disconnect ActiveSync .... [2]
00:13:32:500 [msg] : Start Get Connect Port.
00:13:32:671 [msg] : Current in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.
00:13:33:109 [msg] : Get Device Backup ID.
00:13:33:109 [msg] : Device BL VER : [1.01 ] [].
00:13:33:109 [msg] : Device ID Is Incompatible.
00:13:33:109 [msg] : Update Image. CE : [4], MSystem : [2], Radio : [1]
00:13:34:703 [msg] : Check Ac in BL mode. AC : [1]
00:13:34:718 [msg] : IsBL. BL : [1]
00:13:36:750 [msg] : =============================================
00:13:36:750 [msg] : START UpdateRadio !
00:13:45:671 [msg] : Check Radio Level 0 [704].
00:13:47:250 [msg] : RUpgrade 0 : 0 Start.
00:15:55:562 [err] : RWipe Data Error.
00:15:55:937 [err] : BL UpdateRadio Error.
What "Device ID Is Incompatible" means? How can i resolve it?
Could you try updating with the attached files?
Don't worry if the device picture is not the universal, this is the updater that works most of the time for my uni.
Also with your MaUpgradeUt_noID i can't update radio rom. Device ID Is Incompatible because actually my JasJar doesn't have a ID (from when i got error 114 for the first time). How can i recreate the device ID?
Hi all, I've just inherited an SPV M5000, this is currently locked to Orange (UK), I downloaded the upgrade tool and have used it successfully on Uni's in the past, but this time it won't work.
The bootloader ver reports itself as v2.01, so it's a G4 device. When I try and run the unlock tool I get the following error after I click the "Upgrade" button:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Interestingly, this tool doesn't list any previous radio / version numbers whatsoever but it still offers me the chance to upgrade.
These are the steps I try to get it to install:
1. Hold down the Backlight + Power button and press the reset button
2. "SERIAL" is displayed at the top of the screen with backlight off, "v2.01" at the bottom
3. I connect my Uni to my PC, "Serial" changes to "USB"
4. I run the MaUpgradeUt_noID.exe tool, it welcomes me yadda yadda, I click Next, it says "Checking the information on your device - Please wait"
5. About 10 seconds later, it comes back with the list of version numbers, what's installed, what's going to be installed etc, the only field that lists anything is the last one, "Radio Image Version", which it lists as 0.00.00
6. I click "Upgrade", the "Checking the information.." window pops up briefly, then I see the large upgrading progress bar
7. I see "Stage1: Upgrading Radio. Please wait ..." with an empty progress bar, this stays at 0% for about 60 seconds, and then I see the error above.
When I'm doing this, I"ve made sure the phone is turned on in Windows Mobile, and that there is no SIM card or SD card inserted.
here is my RUU.LOG from C:\
Code:
08:46:47:498 [msg] : Version : [2.11].
08:46:47:508 [msg] : Config Info : [857873],[1],[0],[0],[1],[0],[0],[1].
08:46:47:659 [msg] : MSystemFile Not Exist !
08:46:47:659 [msg] : CEFile Not Exist !
08:46:50:743 [msg] : Current Not in CE Mode or in CE Mode but ActiveSync Not Connected.
08:46:54:819 [msg] : Disconnect ActiveSync .... [2]
08:46:54:819 [msg] : Start Get Connect Port.
08:46:55:029 [msg] : Current in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.
08:47:05:474 [msg] : Device BL VER : [2.01 ] [].
08:47:05:474 [err] : Device CID Error.
08:47:05:474 [msg] : Update Image. CE : [0], MSystem : [0], Radio : [1]
08:47:55:656 [msg] : Check Ac in BL mode. AC : [1]
08:47:57:158 [msg] : IsBL. BL : [1]
08:47:57:198 [msg] : =============================================
08:47:57:208 [msg] : START UpdateRadio !
08:48:04:709 [msg] : Check Radio Level 0 [704].
08:48:05:750 [msg] : RUpgrade 0 : 0 Start.
08:51:06:022 [err] : RWipe Data Error.
08:51:06:383 [err] : BL UpdateRadio Error.
08:51:06:383 [msg] : START UnInitialization !
08:51:06:393 [msg] : END UnInitialization !
08:51:06:403 [msg] : IsBL. BL : [1]
Steps I've also tried:
1. I've tried it with the original orange SIM card inside
2. I've tried it with my T-Mobile SIM card inside
3. I've tried running the tool when the M5000 is booted into Windows Mobile and sat at the Today screen
4. I've flashed Windows Mobile 6.5 to it with a separate updater, THIS UPDATED PERFECTLY FINE, so I know it's possible to flash my M5000, that the cable / drivers are all good etc..
5. I've also tried rebooting my PC
I'm starting to lose faith, please can someone advise?
Well
All the times I have flashed a ROM or radio when I use that tool I always see a picture of an Universal on it...
On your picture there is no Universal, it is another device, so perhaps you do not have the proper radio or ROM
Hope it helped,
Sorry double post
Please delete
orb3000 said:
Well
All the times I have flashed a ROM or radio when I use that tool I always see a picture of an Universal on it...
On your picture there is no Universal, it is another device, so perhaps you do not have the proper radio or ROM
Hope it helped,
Click to expand...
Click to collapse
It's definitely a Uni, although externally it's an o2 XDA Exec, the board is from an Orange SPV M5000 bought within the last 1-2 years, it's a G4 device (Bootloader v2.01), the phone is locked to Orange UK.
Ps. thankyou for getting back to me where no one else would
Is phone on? (Ie, it's not in flight mode)
foxdie said:
It's definitely a Uni, although externally it's an o2 XDA Exec, the board is from an Orange SPV M5000 bought within the last 1-2 years, it's a G4 device (Bootloader v2.01), the phone is locked to Orange UK.
Ps. thankyou for getting back to me where no one else would
Click to expand...
Click to collapse
what orb was referring to is not the device itself but the picture in the upgrading utility, you posted. it shows the magician, meaning you are probably using MAupgradeut_noID.exe to upgrade, while he says, he uses the original universal rom upgrade tool.
Hi, yep I'm sure the GSM modem is turned on / flight mode is turned off.
The unlock tool I used was downloaded from http://buzzdev.net/downloads.php?file=288
In this archive however, it is listed as "MaUpgradeUt_noID.exe", is this wrong?
Here is a screenshot of the files:
I've also tried using a ROM tool for the uni (that flashed one of the 6.5 roms successfully to this device), that fails too.
Where can I find this original ROM upgrade tool? or was this it?
I've also tried using a ROM tool for the uni (that flashed one of the 6.5 roms successfully to this device), that fails too.
Where can I find this original ROM upgrade tool? or was this it?
Chef_Tony said:
what orb was referring to is not the device itself but the picture in the upgrading utility, you posted. it shows the magician, meaning you are probably using MAupgradeut_noID.exe to upgrade, while he says, he uses the original universal rom upgrade tool.
Click to expand...
Click to collapse
Exactly my friend
foxdie said:
I've also tried using a ROM tool for the uni (that flashed one of the 6.5 roms successfully to this device), that fails too.
Where can I find this original ROM upgrade tool? or was this it?
Click to expand...
Click to collapse
I asume you already read the Wiki, over there you can find the tools you need to upgrade correctly
Good luck,
I've tried the tools in the WIKI, I downloaded UniversalRUU.zip, copied the radio_.nbf from Buzz's tool to the folder and tried to flash it with that, that didn't work.
I also tried downloading the latest radio ROM and it's tool, 1.18.00, and the previous versions, 1.15.00, neither of this would flash either.
Bump thanks
Have you tried Doc format?
Doc format?
while the topic is at doc format, i never managed to do that on my universal. there was a file called repart_doc.exe for the blueangel, that not only formatted the extrom, once it was unhidden and unlocked, it would also let you redefine the partitions, so making the storage bigger by reducing the size of the extrom to its minimum of 128kb. however, i always get the same mistake, that the partition i want to work on, was not found, because, obviously the partition's name is a different one for the uni. so, if anyone knows, where to get the repart_doc for the universal, please post it, i can test it and if it happens to work, i will write the tutorial and the wiki for that.
Hello guys,
I seem to be getting the same error (114) over and over. I haven't found a solution yet from the forum.
Foxdie, did you manage to flash the radio eventualy ?
I was wondering if the flash won't go through because my device is locked or something. I have upgraded the CE ROM to WM6 without an issue though. I only get the error when I attempt to flash the radio
Awwwwww... So frustrating...
Nope, still unable to flash, I've got no clue regarding the Doc solution that Chef_Tony is talking about (in particular, how flashing a radio ROM is related to repartitioning a flash disk, I would imagine they're two entirely separate entities).
I hope someone can help, am willing to donate money to XDA Developers and / or Buzz (if it's his tool that ultimately unlocks my Uni).
Have you seen this?:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem5
Problem 5: Device shows NO GSM when booting
* The radio stack is screwed, you don't get GSM signal and the phone says unknown SIM status
* Device won't start after trying to unlock it with HTC Universal Unlocker (HTC_Uni_SIM_Unlock_v1)
Here is how to fix it:
METHOD 1
1. Disable activesync on your computer by right click on activesync icon -> connection settings -> uncheck "allow USB connections".
2. Put your Hermes in bootloader mode
3. Connect device to computer using USB cable.
4. Open mtty.exe and select USB port, then connect.
5. Hit enter twice, you will see the "USB>" prompt.
6.
Type the following commands (do not copy paste!!!)
USB> password 0000000000000000
USB> set 1e 1
USB> erase a0040000 c80000
USB> erase a0cc0000 c80000
USB> erase a1940000 640000
USB> set 1e 0
7. If the password does not work, try password BsaD5SeoA
8. Reset your phone and put it back in bootloader mode
9. If your bootloader version is different than 1.04 then Flash Bootloader version 1.04 (if you can't flash the bootloader version 1.04 (for what ever reason) and you have KITL enabled Rom, then there is final solution - PB_KITL_HERMES))
10. Flash the patched radio used to simunlock the Hermes
11. Your phone should be alive again
METHOD 2
Also, Ive found that Hard-Reseting the device restores GSM.
1. Remove the battery
2. wait 10 second
3. Re-insert Battery
4. Turn the device on
5. Watch for "NO GSM" on boot
6. if you see it. Return to step 1. (sometimes you have to do it up to 20 times)
If you see two lines of text flash up instead of 'No GSM' it means the GSM is functioning. For me this restored my radio in just 4 tries.
This ONLY works if your radio is NOT corrupted, but if you tried to updgrade and stalled between 0% and 15% of the GSM upgrade, it depends on the radio version you were trying to flash. But it's worth a try, the only downside is if your phone crashes, it will more than likely boot up with 'No GSM' so you'll have to do all over again.
Related forum threads
* SPV M3100 back to life at last!!!
* Can't boot after trying to unlock SPV M3100 with HTC Universal unlocker
* Vario II crashed
* Help me!! CID and IMEI missing!
Click to expand...
Click to collapse
i ALSO FOUND THIS:
http://www.4winmobile.com/forums/htc-universal/6930-q-can-iupgrade-rom-another-carrier.html