Develop Bugs

Error 112: CE Rom Update Error - corrupted FAT0 - need help

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...

ERROR 113: EXTENDED ROM UPDATE ERROR

while trying to upgrade with UNI_TMUK_130114_130232_11003_WWE_BL101_Ship giving erro 113: also tryed with JASJAR_WWE_11353_137_10301 and also with UNI_CDL_001_13076_164_10900_A2DP_MSFP_WWE_FINAL
The error is same. What could be the problem?.Now it struct in the boot mode (serial on display)
Also found this instruction in another thread "Now connect woth USB cable and open mtty utility" what the mtty utility?

i had the same problem..
i also read somewhere on this forum
that i could be linked to the bootloader version..
I have 1.01 and it should be 0.64 or something or maybe 1.00.
i dont know for certain..
I almost ****ed my mda pro whith the official Tmobile update(NL)
crap i want to update my machine
but now iam afraid to break my new toy

i had the same problem.. but
Code:
SERIAL" version 1.2
and
Code:
ERROR 112: CE ROM UPDATE ERROR
please help

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

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

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

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

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

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

http://forum.xda-developers.com/showthread.php?t=298640
boz said:
I extracted these error codes from a Hermes rom upgrade 'read me' document, these should be of help if you get an error message during a rom upgrade. They should be common to all roms, please correct me if I am wrong.
ERROR [202, 204] : CONNECTION
This error message will appear when the device is not connected to ActiveSync correctly. Make sure you properly connect the device to the PC through ActiveSync before running RUU.
ERROR [260] : CONNECTION
This error occurs when there is an “open port error” before upgrading the CE ROM image.
Solution: You can reset the device and run RUU again. If you still encounter an “OPEN PORT ERROR” again, reset your computer and try again.
ERROR [206] : MEMORY ALLOCATION
ERROR [280] : UPDATE ERROR
When you see any of these error messages, close other running programs on the computer and run RUU again.
ERROR [208] : FILE OPEN
ERROR [210] : FILE READ
These error messages indicate that RUU lacks certain important files and cannot continue with the update. Please get the complete RUU package again.
ERROR [212] : FILE CREATE
ERROR [214] : FILE WRITE
ERROR [222, 224] : DEVICE NOT RESPONDING
These error messages will appear when remote access control has failed. Check the ActiveSync connection and try running RUU again.
ERROR [220] : MAIN BATTERY POWER
This error message will appear when the device’s battery power is not sufficient. Although RUU will instruct you to plug in the AC adapter, it still has to make sure that your device has enough power to upgrade the radio. (Even when you plug in the AC adapter, the device is unable to charge the battery when it is upgrading the radio).
ERROR [238] : FILE READ
This error message may appear when, for some unknown reason, the ROM image on the Mobile Device is corrupt. Download the whole RUU and try again.
ERROR [240] : FILE OPEN
When this error message appears, check whether the downloaded image is placed in the directory of RUU. If, for some unknown reason, you find that the ROM image is not located in the RUU folder, you have to download the RUU and retry again.
ERROR [242] : INVALID LANGUAGE
ERROR [244] : INVALID MODEL ID
ERROR [294] : INVALID VENDER ID
ERROR [296] : UPGRADE ONLY
One of these error messages will appear when you use the wrong RUU to do the upgrade. RUU will check if the Model ID and Language ID are compatible with the device. Make sure you use the appropriate RUU tool to upgrade.
ERROR [246] : DEVICE NOT RESPONDING
This error message indicates that RUU cannot start the update process. Please contact your service provider for assistance.
ERROR [262, 276, 284, 302] : UPDATE ERROR
This error occurs during the CE ROM code upgrade process.
Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue.
Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode.
ERROR [300] : INVALID UPDATE TOOL
This error message will appear when you use the incorrect RUU version to upgrade.
ERROR [330] : ROM IMAGE ERROR
This error message will appear when you use the incorrect RUU to upgrade and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version to upgrade.
Click to expand...
Click to collapse

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

Another bricked Universal

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)

Unable to unlock SPV M5000, error 114 / CID error

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