1st STEP: You need the MaUpgradeUt_NoID.exe File. The purpose of this file is to avoid any ERRORS while upgrading any part of the ROM.
2nd STEP: You need to get a hold of the ROM file so you can extract the necessary files from it. This is provided by the phone manufacturer.
****To extract the file, someone recomended WinRAR. If you don't have it, follow this: Go to
My Computer
Your Drive (mine is Drive C: )
Show the contents of this drive
Documents and Settings
Choose your folder name
Local Settings
Look for the "Temp" Folder
Choose "TOOLS" from the menu bar
Choose "FOLDER OPTIONS"
Click on the "VIEW" tab
Click on "HIDDEN FILES AND FOLDERS"
YOU WANT TO SHOW ALL HIDDEN FILES AND FOLDERS
3rd STEP: You need to extract the following files namely and add the MaUpgradeUt_NoID.exe File. These 10 files are found in one of the folders within the "TEMP" folder after running the file you got from Step 2.
ms_.nbf----------------------this file is responsible for EXT ROM Version
nk.nbf------------------------this file is responsible for Windows Mobile Version
radio.nbf---------------------this file is responsible for Radio Version
EnterBL
GetDeviceData
readme
ROMUpgradeUt
RUU.conf
RUU.dll
UI.dll
MaUpgradeUt_noID
*****You need these 11 files if you want to upgrade the ENTIRE ROM.
*****If you only want to upgrade to the RADIO VERSION then you need to delete 2 files namely: "ms_.nbf" and "nk.nbf". Leave "radio.nbf". So there are 9 files on it.
NOTE: The "TEMP" folder has many folders within it. It is your job to look which folder was created upon running the .exe file from step 2. You need to copy those 10 files and paste them on a new folder.
4th STEP: After gathering the necessary files and choosing which part you want to upgrade and keep, you need to put your device to boot loader mode by pressing 3 buttons simultaneously:
Power Button
Backlight Button
Reset Pin
5th STEP: Plug your Universal via USB. Wait for your computer to recognize a newly plugged device.
6th STEP: Now you are ready to upgrade. Double click the MaUpgradeUt_NoID.exe File to run it and follow the on screen instructions.
Hope this helps. Good luck.
Hi...
Nice guide indeed..but u forgot one important step....that is hard resetting after the complete upgrade... :lol:
I saw a thread somewhere which advised against hard resetting at the end of the procedure, so I did a soft reset instead. All worked perfectly.
Thanks for the input guys. I also remember, I did not perform a hard reset myself, just a soft reset at the end. But I choose not to include that on the steps as the computer will show a window as to what you're supposed to do or press during the upgrade anyway.
great post!
AG
radio version? Windows Mobile version? and EXT Rom?
cktlcmd, You wrote in your first post about deleting one or 2 of the files to tailor which or all 3 of the versions you want to upgrade? I don't get it? What are the differences between the three? Who wouldn't want to upgrade everything? I have an o2 Exec in the USA. I changed the ROM to I-Mate, but it is still so bad. I have to reset the phone all day long. I am trying to reload the Jasjar rom or the other ROMs to just try something to maybe see if it will perform better. I have downloaded and used Pocket Mechanic and done a few other things recommended but nothing has seemed to have an improvement over freezes I get all day long. Have any advice? Thanks,
Re: radio version? Windows Mobile version? and EXT Rom?
tmglobe2004 said:
cktlcmd, You wrote in your first post about deleting one or 2 of the files to tailor which or all 3 of the versions you want to upgrade? I don't get it? What are the differences between the three? Who wouldn't want to upgrade everything? I have an o2 Exec in the USA. I changed the ROM to I-Mate, but it is still so bad. I have to reset the phone all day long. I am trying to reload the Jasjar rom or the other ROMs to just try something to maybe see if it will perform better. I have downloaded and used Pocket Mechanic and done a few other things recommended but nothing has seemed to have an improvement over freezes I get all day long. Have any advice? Thanks,
Click to expand...
Click to collapse
I have tried all ROMs that came out on this site. The ones I recommend are only 2:
1st: QTEK's latest ROM
2nd: JWright's Modified ROM
From my post above these 3 files determine which part you want to upgrade:
ms_.nbf----------------------this file is responsible for EXT ROM Version
nk.nbf------------------------this file is responsible for Windows Mobile Version
radio.nbf---------------------this file is responsible for Radio Version
If you look at my signature below. I am using TMobile's Radio while using JWright's Modified ROM. It all depends on you which combination you feel is more stable. On my Universal, I never had any troble no matter what ROM I used, but these 2 I listed above surpasses any ROM released by other manufacturers on my opinion.
Pantaloonie said:
I saw a thread somewhere which advised against hard resetting at the end of the procedure, so I did a soft reset instead. All worked perfectly.
Click to expand...
Click to collapse
Yeah I heard the same thing, I did a soft reset after installation and it worked fine.
error 120 country id
Ok, so which of the three files is responsible for the country id error 120?
I am trying to upgrado my os xda exec to the latest JASJAR_WWE_19096_19505_11300_AKU_3_2_ship rom but I keep getting the same error again.
Please, I need help.
Thanks. Antonio Mota
artcsmota said:
Ok, so which of the three files is responsible for the country id error 120?
I am trying to upgrado my os xda exec to the latest JASJAR_WWE_19096_19505_11300_AKU_3_2_ship rom but I keep getting the same error again.
Please, I need help.
Thanks. Antonio Mota
Click to expand...
Click to collapse
What 3 files? If you are referring to the .nbf files, none of them are responsible. Follow the instructions above and keep repeating them, sometimes it takes more than one try for the Error 120 to disappear according to some who experienced it.
cktlcmd said:
1st STEP: You need the MaUpgradeUt_NoID.exe File. The purpose of this file is to avoid any ERRORS while upgrading any part of the ROM.
Click to expand...
Click to collapse
A great post, Upgraded my O2 Exec using your procedure, worked a treat, Thank you!
Wooky
cktlcmd said:
ms_.nbf----------------------this file is responsible for EXT ROM Version
nk.nbf------------------------this file is responsible for Windows Mobile Version
radio.nbf---------------------this file is responsible for Radio Version
EnterBL
GetDeviceData
readme
ROMUpgradeUt
RUU.conf
RUU.dll
UI.dll
MaUpgradeUt_noID
Click to expand...
Click to collapse
I'm being really thick today and struggling here. I've downloaded
JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.zip
MaUpgradeUt_noID.zip
T-Mobile_ExtROM.zip
and unzipped them.
The .nbf files are not present, althought the _ship.zip was 70mb before unzipping so I guess this contains everything :s
Is there an idiot's guide for installing this acclaimed ROM on an MDA Pro?
When I run the maupgrade tool, the wizard shows an image of an imate Jam (or something like that, not a Universal) but tells me it runs OK.
The T Mobile ext rom also shows the "wrong" HTC device but claims to run OK.
The main JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.exe just gives the "120" error complaining of the wrong device (although the picture is of a universal this time at least)
Please tell me what I'm doing wrong, I'm going quite mental here
resetting
Please excuse a noob question, but earlier the discussion was about the type of reset to do after the ROM upgrade. As per instructions in the s/ware, I did the cold boot. All is perfect - thanks.
If I needed to perform a hard reset at any point in the future, am I correct in assuming this would just reload the new ROM or would this reload the old O2.
Many thanks
Mav
xiasma said:
I'm being really thick today and struggling here. I've downloaded
JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.zip
MaUpgradeUt_noID.zip
T-Mobile_ExtROM.zip
and unzipped them.
The .nbf files are not present, althought the _ship.zip was 70mb before unzipping so I guess this contains everything :s
Is there an idiot's guide for installing this acclaimed ROM on an MDA Pro?
When I run the maupgrade tool, the wizard shows an image of an imate Jam (or something like that, not a Universal) but tells me it runs OK.
The T Mobile ext rom also shows the "wrong" HTC device but claims to run OK.
The main JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.exe just gives the "120" error complaining of the wrong device (although the picture is of a universal this time at least)
Please tell me what I'm doing wrong, I'm going quite mental here
Click to expand...
Click to collapse
Actually, you are on the right track. Now you need to run the HUGE FILE you mentioned that is about 70MB. That is the REAL file you want to extract which contains the 10 files necessary for upgrading listed on my procedure. Follow my instructions once you run this file. Follow the instructions on where you will find the files.
mavrik64 said:
Please excuse a noob question, but earlier the discussion was about the type of reset to do after the ROM upgrade. As per instructions in the s/ware, I did the cold boot. All is perfect - thanks.
If I needed to perform a hard reset at any point in the future, am I correct in assuming this would just reload the new ROM or would this reload the old O2.
Many thanks
Mav
Click to expand...
Click to collapse
YES, if you perform a hard reset. The new upgraded ROM will be the default ROM restored on your device.
cktlcmd said:
Actually, you are on the right track. Now you need to run the HUGE FILE you mentioned that is about 70MB. That is the REAL file you want to extract which contains the 10 files necessary for upgrading listed on my procedure. Follow my instructions once you run this file. Follow the instructions on where you will find the files.
Click to expand...
Click to collapse
Thanks, but I have tried running
JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.exe
and it's still giving the 120 error.
OK, from scratch.
I've just run the MAUpgrade exe and that ran *very* quickly.
I've now ran the T-mobile ext ROM upgrade, hard reset.
When the \extrom autoruns, should I just select T Mobile UK? Or cancel?
xiasma said:
Thanks, but I have tried running
JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.exe
and it's still giving the 120 error.
OK, from scratch.
I've just run the MAUpgrade exe and that ran *very* quickly.
Click to expand...
Click to collapse
I think you are doing what I was when it finaly clicked.
By the way, thanks to cktlcmd for the breakdown of the process.
The bit you will need to understand is that when you run the .exe, it unpacks the files into a folder in the Temp directory cktlcmd mentions. All i did then was to search for one of the files listed and i found the folder that way. I then copied the files into a more convinient folder and added the MAUpgrade as per the instructions. Once i did this, running the MAUpgrade does as described.
I know this may seem a bit long winded, but I got there in the end. Also, by saving the contents of the folder elsesware means I can play with it later as also discribed by cktlcmd.
The JASJAR rom is sofar great.
Thanks for all your hard work cktlcmd
regards
Mav
i have tried several Universal ROMS and all the upgrading is halting/freezing at Stage3: CE ROM upgrading... at 19%
all the ROMS (ivan beta14 - 1.90.96) are frozen at same level at 19%
what can be the problem or which way should i use to flash my MDA Pro ?
thanks
fuhayer said:
i have tried several Universal ROMS and all the upgrading is halting/freezing at Stage3: CE ROM upgrading... at 19%
all the ROMS (ivan beta14 - 1.90.96) are frozen at same level at 19%
what can be the problem or which way should i use to flash my MDA Pro ?
thanks
Click to expand...
Click to collapse
Have you tried my instructions yet? Try downloading the files again. Sometimes they get corrupted.
it is fixed by flashing with original t-mobile 1.30.232 rom.
but when i flash ivanb14 it is again freezing at 19% of stage3.
what can be the problem ? i have downloaded the ivanb14 rom 3 times and i receive the same error message.
im using a tytn and getting errore message
dows the official upgrade is for tytn or doopod ?
anyone can help ??
i try using hard sspl and still .. same
I think it may be because it is a rom for Asian networks... I got a similar error, and will have to manually import the settings for my network providor... other than that, everything else went fine...
I believe there are cabs kicking about this forum to auto setup for various providors.. I think it is trying to auto detect your vendor, and if not Asian, is returning the error
I think thats all the error is showing...
If you've downloaded one of the other cooked ROMs on this site, you should have an exe file called RUU_wrapper.exe.
Now, install WINRAR and right click on the dopod rom and choose extract and it will extract various files, one of which will be another exe file. Extract this exe file again and you should end up with a file RUU_Signed.nbh - this is th only file you'll need out of the lot.
You can delete all the other files from the dopod ROM now, just keeping the RUU_signed.nbh. Copy the RUU_wrapper.exe file into the same folder and run it and you will flash the dopod rom to your phone nicely - just make sure you're HARDSPL first!
Now, you could be even smarter at this point and use dutty's good nbhtool if you like to "unwrap" RUU_signed file and remove the IPL \ SPL (though with HARDSPL, I'm not sure this is necessary) and the Radio part if you like (and the boot splash screens if you're so inclined and then use it to wrap it all back up again.
HTH,
Smiffy.
So I have a .nb0 file I need to load on my hermes device and the instructions I have say to use the lnbms command to do it. Sadly I have HardSPL installed and lnbms does not seem to be recognized as a command. Does anyone know how to load a .nb0 file if I have HardSPL installed?
Thanks,
LouisK
Um ya that makes not that much sence. Do you have a ROM.nbh or Radio.nbh? since you need to have a file type that is compatable with the hermes and I dont think the one your talking about is.
rm -rf *
-fluxist
louisk said:
So I have a .nb0 file I need to load on my hermes device and the instructions I have say to use the lnbms command to do it. Sadly I have HardSPL installed and lnbms does not seem to be recognized as a command. Does anyone know how to load a .nb0 file if I have HardSPL installed?
Thanks,
LouisK
Click to expand...
Click to collapse
Last time I checked, .nb0 files don't go on Hermes devices.
I am in the same boat. I have an os.nb0 that was extracted from a hermes. I want to get it onto my device.... lnbms is the command but it's locked in the bootloader. Anyone know how to get around this?
so, just checking, you've extracted the nb0 file out of a hermes rom and are trying to put it into a loaded os????
Sounds to me like you need to be cooking your own os if you want to do that...
And then reflash time....
I figured it out. The reason that you can not flash a .nb0 with MTTY is the bootloader is locked. Even though the phone may be CID or Super-CID or SSPL or whatever... you MUST have a bootloader that is unlocked and will allow the lnbms command to pass. I have not seen any information yet on this and the hermes. I was able to do this on my htc Wizard though Know that doesn't help but it does atleast tell you why you can't do this action
ok heres what happened first i installed hardspl and then i changed my radio to 1.27.14.09 and when i restarted my att tilt the att stuff went on then nothing it never went to the main screen, now how can i reinstall a radio or just the att stock software without using activesync
Go to the bootloader - check the wiki for instructions. Connect your computer to the Tilt - you should see "USB" below the tri-color screen. Install the new ROM or radio. PM me if you have problems.
P.S. The answers to any problems you find are readily accessible in the Kaiser section.
shrshr429 said:
ok heres what happened first i installed hardspl and then i changed my radio to 1.27.14.09 and when i restarted my att tilt the att stuff went on then nothing it never went to the main screen, now how can i reinstall a radio or just the att stock software without using activesync
Click to expand...
Click to collapse
Check the wiki for sd flash. You kan rename the nbh file to KAISIMG.nbh and put it on a sd then goto bootloader and it asks you to install.
im sorry what's wiki and also I can't find software that will let me download the software without activesync does anyone have a link I can use
http://wiki.xda-developers.com/index.php?pagename=HTC_Kaiser
You should be able to find everything you need here.
i tried everything there, theirs just one problem i cant find a rom that i can use without activesync does anyone have one
When you attach the cable and go to bootloader - does it say "USB" below the tri-color screen? If so, you have communication and can flash.
What do your three lines say at the top of the bootloader (red section)?
it does say usb my computer is reading the phone i just cant find a rom that doesnt use activesync, nothing with RUU_Sign.nbh, i did use hardspl the 3 lines say
KAIS1*0 MFG
SPL-1.0.01iPof
CPLD-8
i do have a microsd card i can try and upload it through their but there is stil the problem with no activesync
so can anyone help me here
ok, since i never really seen this question answered directly anywhere, you get this freebie
how to extract the RUU_Signed.nbh file
If its a cooked rom, the file you download will *usually* be a .rar file, extract the contents with winrar. depending on how the cook packaged it, it may not be named RUU_Signed.nbh, but it will still be a .nbh file
If its an original shipped rom, the file you download will be a .exe file, again, extract the contents with winrar. There will be a bunch of files and the RUU_Signed.nbh will be one of them.
if i downlaod the original rom it just opens up a program to install it how can i extract it without using the program to connect to my phone
omg!!!!!
1. install winrar
2. right click on the file you downloaded
3. choose "extract here"
then do the flashing using the microsd card
I Read and Read and Read. The surprising part is that, what I need the most there is no video nor any instruction to fix the problem.
I'm trying to flash a ROM on my tilt 2 GSM phone.
I have already HSPL it,
I did task 29 using RhodiumWAdvancedRUU.zip because I couldn't get regular task 29 to work.
Now I get a white screen with HTC on it and it doesnt pass it. So I enter bootloader and make sure that at the bottom it shows USB. (yes I do see SPL-0.85. OliNex)
Now I try to install the ROM and here is where the problem starts.
My ROM:
I dled NRG MAXSENSE ROM which is Energy.RHODIUM.29022.Sense2.5.MaxSense.Jul.08.7z
My Rhodium Update Utility (RUU) is
Rhodium_CustomRUU_v1.1.zip
I Open it and I see
CustomRUU.exe
Here is where I don't know what to do. Some instructions say that I need a .NBH file. Where do I get this file. They say it should be with my ROM.
All I get when I dl the ROM is
Energy.RHODIUM.29022.Sense2.5.MaxSense.Jul.08.7z
Format 7z not .nbh
I get the Error [240] File Open when I run CustomRUU.exe. To fix it they say
"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."
What is the "DIRECTORY" of RUU"? Whats a directory? I never heard that term before.
Of which RUU? CustomRUU.exe?
Do I make a folder and put CustomRUU.exe in it with the Energy.RHODIUM.29022.Sense2.5.MaxSense.Jul.08.7z ?
Where is the .nbh file? Do I rename the ROM IMAGE to .nbh?
Please give me step by step. Ive read so much already and I dont know what to do anymore. Thank you for your help.
-___- I cannot believe I spent all this time for something so dumb. We should put this on the Help for NOOBS thread. The file " .7z " cannot be opened with Winzip. To open the file you have to use WINRAR. And from there we can see the Rhodium_SoftwareUpgrade.exe (RUU) and the RHODIMG.nbh files. And double clicking the Rhodium_SoftwareUpgrade.exe the software will start walking you through the process for flashing. I think it would be a good idea to add on the HOW TO FLASH A ROM that the 7z file requires WINRAR to be opened.
But thanks to the Lord I learned how to flash the Rom successfully.
--------------------
He who provides for this life but takes no care for eternity is wise for a moment but a fool forever.
-John Tillotson
Or use 7-zip!
-Jonny- said:
Or use 7-zip!
Click to expand...
Click to collapse
Too easy lol