Develop Bugs

HOWTO: Upgrade to other ROM without using NoID tool

(I am not responsible for any damage you might do to your device using this guide)
I tried flashing with the NoID tool several times, yet it always failed, or my Universal would not boot after the flash.
The regular T-Mobile update utility did work like a charm, and never failed on my. Thus I created a little tutorial on how to convert wrong ROMs to ROMs it will accept.
In this Example I will explain how to use an O2 XDA Exec ROM (and a different radio ROM) on a T-Mobile MDA Pro device
It's easiest to start with a clean directory to do all this as else it can get quite messy.
First, get the HTC64 Extended ROM Tool by Bal666 here:
http://buzzdev.net/component/option,com_remository/Itemid,100/func,fileinfo/id,196/
Next get an original ROM for your device, in my case I used the T-Mobile UK ROM as my device was english anyway.
For example, on the T-Mobile MDA Pro UK (or dutch) version, use "UNI_TMUK_11242_126_10002_Ship.exe" (find it yoursef)
Use WinRAR (http://www.rarlabs.com/) to unpack this file to a new directory called "Original", and unpack it again to a directory named "Converted".
The Original directory will be used to check things, and the Converted directory will be used to store all the roms that we have converted
Next we must find the ROMs we want to flash. I got "Xda_Exec_LaunchROM_v113139.exe" and Unpacked it in a directory named "O2", and "UNI_radio_1.08.00.rar" (from buzzdev.net) and unpacked it into "Radio Update".
First we must find out some things about our original ROMs. For each original ROM in the "Original" directory, follow the next steps:
- Open the HTC64 Extended ROM Tool
- Click Decode
- Open the ROM (.nbf file)
- Write down the values after "Operator Name" and "Language"
- Hit Cancel
Now we must modify the ROMs from the other distributions.
From the O2 directory we will use nk.nbf (OS) and ms_.nbf (Extended ROM), and from the Radio Update directory we will use radio_.nbf (Updated Radio ROM).
For each ROM you want to convert, follow the following steps:
- Open HTC64 Extended ROM Tool
- hit Decode
- Open the ROM
- In "Operator Name" and "Language" fill in what you wrote down earlier
- Hit Decode
- (on the begin screen) Hit Encode
- Open the .prj file you just created (same name as ROM, but with extensio .prj)
- Hit Encode
- if asked "Overwrite existing ROM", choose "Yes"
- if asked "Fat16 file is too large", choose "OK"
- When done, copy the over-written .nbf file from the directory you created it in (like O2 or Radio ROM) to the Converted directory. Choose to overwrite the existing file.
When all is done, run the ROMUpgradeUT.exe in the Converted directory, and follow the instructions.
If all goes well, you should have upgraded your ROM without having to CID-Unlock or use NoID tools that were originally made for another device
If before the actual upgrade your PC says it has found an unrecognized USB Device, close the RomUpgradeUT.exe with task manager (ctrl+alt+del), and reset your device (push the stylus in the hole at the backside). Then re-run the ROMUpgradeUT.exe
Credits go to iruja because he helped me find these tool
Let me know if it also worked on your device
EDIT: Stupid me, HTC64 Extended ROM Tool is by bal666
EDIT2: Note on "Unrecognized USB Device"
EDIT3: Added credits

Nice Job! Good, Clear and informative instructions.

he, leuke guide, die ken ik ergens van
Nice people like my way, this is the same way I test different roms for the wizard, without having to cid unlock the phone and loose warranty

Thank you "TheBlasphemer"
wow, I searched this forum for a few hours trying to understand how to install roms from other developers onto my Universal. It was driving me insane cause i kept on recieving country id errors. I found your post and was delighted to find how easy it really is to upgrade roms. Thank you for helping people like me who have no clue. Thanks, Thanks and More thanks. I also give shout outs to all others in this forum who take time to help others. XDA Developers is awesome! I'm surprised that developer sites dont link to xda developers for their customers. It would save them alot of time and money. Peace

Great Instructions
Many thanks for the great instructions.
I tried to flash my T-Mobile MDA Pro to the latest i-Mate rom and it became stuck in the Bootloader mode (I used the No-ID tool, and tried every type of reset). Fortunately this approach works, and I'm now the proud over of an much faster PDA.
Rom: 1.30.68 WWE 02/08/06
Radio: 1.09.00
Protocol: 42.42.P8
ExtRom: 1.30.153 WWE
The original T-Mobile Rom sucks compared to these i-Mate Roms
http://forum.xda-developers.com/viewtopic.php?t=42743

Excellent
Crystal clear instructions. worked like a charm once I found the Orange operator code is ORANG007. The "Orange" ROM on ftp appears to be a hash of 3 other versions as the operator names are QTEK001 and CDC__ something or other....
Thanks again for the excellent, no hassle upgrade method!

This procedure will be working on MDA Vario (QTek9100) ?

I have a QTEK 9000 that is in Spanish OS. There is no available downloadable shipping ROM so how do i get the values of Operator Name and Language? Are they in the registry=?

Tried this on my MDA pro NL which is stuck in boot screen, but no dice
I used however the init UK rom from T-mobile, not the NL which was my official one. I don't have a NL so I maybe if I use that one, it'll work, but Im afraid not

Viper, I also have a NL version and would like to upgrade my MDA...did you have any luck doing so or did you find the original dutch ROM?
(A stupid question: when I upgrade my rom, i assume that all my data is lost, right?)

Just wondering did you all upgrade your devices with the exe that came with the new ROM, or the one that comes from the phone vendor? :roll:
Kinda wondering should I use the one that comes with the QTek ROM, or should I use the one that came with the Dopod ROM (mine's a Dopod)

wow, how easy was that
the orange updater from the net (M5000_email.exe M5000) creates a temp directory called
\Local Settings\Temp\pft3CA.tmp\
run the orange updater program so it extracts the files, DONT CLOSE IT, leave it at the point where you make it update (don't hit next)
now follow the steps of the OP
simply decode your chosen rom, encode them with the correct info, then overwrite the roms in the temp directory with your required ones
then let the orange app install 'em for you!
took me 10 min to make my radio only to 1.09

hi guys
my MDA Pro dead, only show boot mode. i can't turn on my phone. i'm using all rom files. but no result. please help me how repar my phone. i'm use then solution no result. i can't change my phone lang. detect phone show only empty info. help me pleaseeeeeeeeeeeeeeeeeeee

siemens man??
why that name, do you work for 'em?

hi guys
thank you for reply mail. all problem solved. now good working
thanks to Buzz

Thank you verry much i'm verry happy with the Qtek-ROM (radio of Dopod 900) instead of the T-mobile rom
And now I have MSN

Im going to upgrade my MDA PRO tonight using the instrutions in this thread, but which is the best ROM to update it to? i suppose i would like push mail and msn messenger/hotmail.
also is there a slightly more stable internet browser in the ROMS? my current IE is not very good, and opera has the habbit of coming up with a not enough storage memory in dll error!

XDA EXEC is dead
I received my xda exec two days ago. I've tried the ROM upgrade as described. ROMUpgradeUT went OK. When I cold boot my device I get two options - Press 0 to restore factory default Press X to exit. Neither have any effect and the exec seems to be dead. Can someone help out or suggest a fix please?

It's alive !!!
Managed to get the exec in boatloader mode, plugged in usb and reflashed it with an original O2 rom, which, thankfully revived it. I still would like to find out what went wrong with the original ROM upgrade and why it 'killed' the exec. I followed the instructions to the letter. My orignal pre-installed ROM was a 1.13.82 (11/30/05), Radio 1.04.02, XROM 1.13.188. I tried to upgrade to JASJAR ME 1.30.82 171 10900 WWE ship ROM, which effectively turned my exec into (I quote) 'a very expensive paperweight'. I now have got it working with an older O2 original ROM (ROM 1.13.48 (09/19/05), Radio 1.04.02, XROM 1.13.139). When I tried to flash I overwrote the 'original' (ROM 1.13.48 (09/19/05), Radio 1.04.02, XROM 1.13.139) with the modified ROM, RADIO and XROM files from the JASJAR version, I didn't replace any dll files. Could this be the problem or am I way off target? Can anyone spot were I messed up here. Tonight I will try with another JASJAR upgrade, now that I know I can safely reflash with an oringal O2 ROM.

anyone know where i can get ROMUpgradeUT.exe tool from?

O2 Xda Exec ROM update issues

Hi there,
First things first I'm totally a newbie. I owned a treo 650 before I got my Xda Exec, it just for lack of a better word sucked.
I have a very old ROM version (1.13.48 WWE) and the radio ROM is just as old (1.04.02) I did manage to get the device unbranded by soft restarting before I got to the Windows is installing crap that’s gona slow down your device screen.
I know I am not getting the most out of my device with this ROM. So I tried to update I wasn't able to find the latest Qtek Rom (which seems to be the most popular here, on this site) on the ftp, has it been removed? I tried to get the latest O2 ROM from the O2 site but was unable because I didn’t have a O2 Phone number. I did manage to get the Vodaphone (vf-uk_v1640_aku2_v130194_wwe_ship) and T-mobile (UNI_TMUK_12032_120_10600_Ship) ROMs but when I go to install them I get this error message.
ERROR 120: Country ID Error 22-22-44-44-44
I see the there are a few people on this site that have gotten other ROMs to work on the O2's. How was this done?
Also what is the "best" ROM to date and where can I get it?
Thanks,
Tom
PS I’ll likely have many more newbie questions in the future, sorry

Try here for the official O2 ROM (1.30.162)
http://xda.o2.co.uk/downloads/Xda_Exec_Upgrade_v1.30.162.exe
Have a look on the wiki if you want to install the ROM from another operator, or just do a search for country code error and you will see where you are going wrong- this has been posted hundreds of times before!
HTH
Fin

Thanks mate.

Problem after HardSPL upgrading :(

Hi everyone,
I've just upgraded my (french) Diamond's HardSPL with the OliNex version found in the topic "Hard-SPL or how I learned to stop worrying and love the MPU". Everything was OK at this time so I booted and HTC "reinstalled" the TF3D interface files.
Everything is still working but when I tried (several times) to upgrade the Radio version to v1.00.25.05, the program stays at 0% for 3 minutes and then gave me the 262 update error. I tried to connect my Diamond to different USB ports but didn't change anything.
So I decided to download the official update from HTC website and install it (witch I did) but this update doesn't work too (same error)
The strory is not so bad because my Diamond is still working but I want to install an unofficial ROM...
PS: sorry for my english and thanks for your help

@tompim
The first post in the radio thread is worth reading carefully:-
http://forum.xda-developers.com/showthread.php?t=407956
I suspect that your problem is that you need one of the unsigned / developer hardspls for standalone radio upgrades and you are using one of the "signed hardspls"
http://forum.xda-developers.com/showthread.php?t=408621
http://forum.xda-developers.com/showthread.php?t=400950

Thank you very much for your explanation (i read the radio thread before strarting ).
In fact I want to install the Diamond Project Rom that need theses (http://forum.xda-developers.com/showthread.php?t=408621) HardSPL version but I don't know what version number choose (I tried with the 1.34 and the same problem appeared

To remove all doubt and be able flash virtually any rom, flash the developer edition unsigned Hard-SPL from http://forum.xda-developers.com/showthread.php?t=400950. It should do the trick for you.

Works like a chrarm thanks!

All device info gone ???

Hey,
I'm pretty new at this, so I'll explain how i've gotten in to this.
1. Bought a HTC tytn UK and I wanted it in dutch
2. Since I couldn't find an original rom i flashed it to the dutch rom from shap's (wich is actually great)
3. Then i did find an original rom but wasn't able to flash it so i used "HTC Hermes SIM & CID Unlock - v3a"
4. The original dutch rom works fine now, except when i go to device info
Rom version: empty
Rom date: empty
Radio version: empty
Protocol version: empty
CPU: 8 squars
speed: 6 squarsBe...
No imei number and so on.
Can someone please help me, maybe in the future when i try to sell the phone this must be ok.
Thx a lot to all xda developers here !!!
edit: original bootloader and ipl were: SPL-2.05 IPL-1.04 (maybe it has something to do with that?)

roeldm said:
Hey,
I'm pretty new at this, so I'll explain how i've gotten in to this.
1. Bought a HTC tytn UK and I wanted it in dutch
2. Since I couldn't find an original rom i flashed it to the dutch rom from shap's (wich is actually great)
3. Then i did find an original rom but wasn't able to flash it so i used "HTC Hermes SIM & CID Unlock - v3a"
4. The original dutch rom works fine now, except when i go to device info
Rom version: empty
Rom date: empty
Radio version: empty
Protocol version: empty
CPU: 8 squars
speed: 6 squarsBe...
No imei number and so on.
Can someone please help me, maybe in the future when i try to sell the phone this must be ok.
Thx a lot to all xda developers here !!!
edit: original bootloader and ipl were: SPL-2.05 IPL-1.04 (maybe it has something to do with that?)
Click to expand...
Click to collapse
1) you need to flash HardSPL
2) make sure you have flashed a new radio after using the CID/SIM unlocker, due to the fact that it downgrades it to a very old radio for it to work.

I had this issue when I tried a version of HTC Home Customizer that I found somewhere on the net.
To make it all come back, I had to hard reset, and not reinstall the program that caused it. I'm not sure if any other programs could cause that issue, or why it was caused.

I've flashed my device to HardSPL. now wich radio rom should I use?
I've found several radio rom but I don't have a clue wich one is best for me (Belgium, Mobistar)

flash a shipped ROM from here, there is a dutch HTC from there. get to boot loader, pressing the ok on the left, power on right, and stick stylus in at the same time. plug it to active sync, and run the exe file from the WM 6 rom upgrade/downgrade.

How to remove region ID protection to a ROM

Hi guys, I have an HTC Diamond P3700 (DIAM110 64M) and I cannot install any of the HTC 2.03 official roms. I already ran OLIPRO unlocker (dev Hard SPL, Sim Unlock, Security Unlock). I'm trying to run any of the official 2.03 ROMS (tried europe, ME, hong kong) but nothing works. I CAN flash any cooked rom (running AZTOR v10) but I still would like to know how to install any official 2.03 ROMS.
I get the always handy error 244 invalid model ID so it makes me think of invalid region ID issue.
Any pointers greatly appreciated.

You answers will most likely be found here....
http://forum.xda-developers.com/showthread.php?t=409425
Update stops at 5%/Invalid Model ID is displayed
Short answer: The model ID hardcoded in the ROM image doesn't match the ID of your device. Read on for a fix.
Long answer: Don't Panic. Your Device isn't broken
Each Diamond Model has it's own ID. My German MDA Compact IV is a DIAM200. Other models are DIAM150/DIAM300/DIAM100....
Now ROMs might be configured to be flashable to a specific Model ID only, even though technically they would work fine on any Model ID.
In that case the ROM needs to be "reconfigured" - this process works for full ROMs as well as Radios.
* If you are running a foreign Version of Windows or have Regional Settings other than English US configured, please set them to English U.S. temporarily. Otherwise NBHUtil will not function correctly.
* First you'll need OliPro's NBH Util (0.92 works for the Diamond).
* Fire it up, switch to "Extract NBH"
* Select the nbh of the ROM/Radio to be flashed and hit Go
* Extract the components you need. Radio/Splash/OS. If there's an SPL in there, you can safely discard/ignore it. You have HardSPL for that.
* Make note of the Target CID, Version, Language and Chunk Size. FYI the Model ID is the problematic setting here. If it says DIAM10000 and you have a DIAM300 you're screwed.
* Switch to the Build NBH tab and select the Diamond as target
* Note how the Model ID is preset to DIAM*****. The wildcard allows any device
* Change target CID, Version, Lang & Chunk size to the values you wrote down.
* Select each saved component under the NBH items
* Hit Build NBH and save the file as RUU_signed.nbh to a folder of your choice and flash it with the DiamondCustomRUU.exe or ROMUpdateUtility.exe
* Donate to OliPro because he just made your device useful

This is not the case
Update process stops at 1%. I already read that forum at usually you would think of HARD SPL issues, but not. I can flash cooked roms (I'm running AZTOR v10). That's why I'm thinking of region ID protection.

hmm....yes, yes, perhaps.
Ok, well I will see if there are any other post on this outside of this forum.

davidsle said:
Hi guys, I have an HTC Diamond P3700 (DIAM110 64M) and I cannot install any of the HTC 2.03 official roms. I already ran OLIPRO unlocker (dev Hard SPL, Sim Unlock, Security Unlock). I'm trying to run any of the official 2.03 ROMS (tried europe, ME, hong kong) but nothing works. I CAN flash any cooked rom (running AZTOR v10) but I still would like to know how to install any official 2.03 ROMS.
I get the always handy error 244 invalid model ID so it makes me think of invalid region ID issue.
Any pointers greatly appreciated.
Click to expand...
Click to collapse
that error is nothing to do with regionid
however if you flash a rom with high regionid protection, and your device is not from matching region you have to patch the rom, for older roms in 1 place, for newer ones in 2 places. I can give more info if anyone requests it, also I made a patcher for nk.exe (1st patch is in nk.exe), that does it automatically
PS: I noticed you mention mainly english roms. well, english language roms usually never have it. russian and chinese language roms tend to have this

davidsle said:
Update process stops at 1%. I already read that forum at usually you would think of HARD SPL issues, but not. I can flash cooked roms (I'm running AZTOR v10). That's why I'm thinking of region ID protection.
Click to expand...
Click to collapse
probably these roms are DIAM100**
your diamond is DIAM110 so you want a rom with DIAM110** or DIAM***** modelid
cooked roms are usually DIAM***** and stock roms aren't.
so do what band27 said.

is there a prob if my model id is DIAM100 and nbh [email protected] extract nbh i get DIAM10000?
i get this model id from the nbh @ the official ROM downloaded with my sn

cmonex said:
that error is nothing to do with regionid
however if you flash a rom with high regionid protection, and your device is not from matching region you have to patch the rom, for older roms in 1 place, for newer ones in 2 places. I can give more info if anyone requests it, also I made a patcher for nk.exe (1st patch is in nk.exe), that does it automatically
PS: I noticed you mention mainly english roms. well, english language roms usually never have it. russian and chinese language roms tend to have this
Click to expand...
Click to collapse
I am really intresting in it. Can you tell me the detail about how to patch nk.exe and rilphone.dll to remove the region ID protection? THX