Instruction Guide For The Htc Universal Rom Upgrading - JASJAR, XDA Exec, MDA Pro Software Upgrading

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.

Related

Would like to upgrade ROM but . . .

Hi all,
let me start telling that reading through this frum gives me the feeling that this is a very nice place for information around htc-devices and I thank both creators and users of this site for such a good information-base.
Reading here convinces me that I am able to fulfill my wish to change the language of my VPA-IV (HTC Universal).
I am a Dutch person working in Russia. As I was living in Germany I optained the device there, hence the German language.
For me personally all computer stuff should be English, so I'd also like this device to be so. The fact that the keyboard is German does not disturb me too much.
As a Vodafone user, who has other provider cards as well, I immediately bought the unlock code, so the device is working with other GSM cards as well.
When I asked Vodafone (before I bought the device) if I could switch to English I was told that I should buy myself another Windows Software and they were not able to provide me with it. They were not able to provide any help, nor software for this purpose though.
When reading around the site here (as well as the ftp) I understood that Windows is not provided now. So my first question would be :
-Am I really set to go if I have downloaded the following files :
Jasjar_WWW_11353_137_10301.zip
MaUpgradeUt_noID.zip
Universal_Radinly_UPgrade_1.04.02.zip
Or do I need something more ?
Further I read about extracting the .exe file (f.e. Jasjar_WWW_11353_137_10301.exe) and put some files from there at certain places. I have WinRar but this program does not recognize the .exe file. Can I really extract files from this .exe ? How do I do this.
A lot of talking is here about a bootloader. If the device is in this stage, can I still access it ? (f.e. like seeing a harddrive in my PC's Windows Explorer or something the like)
As I will be stressed like hell (who does not, when he does this first time) when I see the bootloader screen, is there something I SHOULD or should NOT do to make sure all will be OK ?
Last but certainly not least I feel very eager to backup before I do this. Is there a posibility to backup my ROM in some way, save the files on some place for eventual return to the ROM and ExtRom I have now ?
I tried the Program TotalCommander. If I enter the Extended_Rom in the "directory" field of this program I see all files included in the Extended_Rom, same if I enter simply "Rom". Is a backup simply copying these files to my PC or is there more to be done ?
thanks for answering in advance,
Ruud
Hi,
I'm searching a german ROM...
if you have a little of your time to spend on it, i would be very thankful.
but first:
- about extracting the .exe files: Run WinRAR -> Menue: Open file... -> change 'All archives' to 'All files'
- about ROMs: Jasjar_WWW_11353_137_10301.zip is the only rom I would update, not the Radio.
- about bootloader: In this state you can't access your device (only updating the ROM)
- about backup: It is not easy. (How to d2s (dump) the ROM ) but I think Vodafone will shortly relase a update. So it will be possible to restor the device.
How to help me out:
- you will need a Storage Card.
- Download TestWM5.rar
1. Extract TestWM5.exe from TestWM5.rar and place it to you device.
2. At the device, use File Explorer to execute the TestWM5.exe
3. Click "button1" to start the dump process, the file will then be save to \Storage Card\Dump\
4. Copy the Dump folder out and then RAR or Zip it
This will include all files in your windows dictionary -> this is what i need
Where to place exactly ?
Hi bepe,
do not know if You are still available (or again). First your issue.
I logon to FTP from XDA-developers as to upload.
In the upload directory there is only a HTC-Wizard directory, not a wizard. Is this directory the one to place your file on ?
Is there a rule how to name the file ?
I will be dumping in a minute, can upload as soon as I have your answer.
Ruud
Hi bepe,
further to your issue.
1) I do understand that no private information is copied ? or should I do a hard reset before I dump for You ?
2) Whilst running your testwm5.exe from the root-directory of the storage-card I am being asked to agree your program access. This is normal, I allow. But why are there additional programs being opened I never heard about ? I denied them access and let the program run further !
After a lot of files running through the screen (very fast) it looks like the program stopped or finished. Now which file has been created for You ?
Explorer on the Universal does not show it, through my PC I looked as well, but do not see any big file, please explain.
Ruud
Hi Bepe,
one more reply to You :
Even if I allow the file mentioned to run (during the time your program is running), I am being asked again and again if I allow it again. The name is GAC_System.Data_v1_0_5000_0_cneutral_1.dll
Even if allow access all of the occasions I being asked, no file is being created on my storage-card, nothing to dump to You. Not even the dump directory is made.
What do I do wrong here ?
To my issue :
First I noticed that the radio update is available here only as 1.04.02
My system tells me I have 1.04.10 delivered from origin. If I do a ROM-upgrade, do I loose my "radio", or will it not be touched ?
Connected to this, can I dump my "radio"-files seperately ?
WinRAR. Issue solved !
Backup : I was at the buzzdev.net link before. But I actually do not even understand where I can get or see the task32 language he dumped on his screen. And I understand that I will not be able to restore it without help anyway. So this is not really the kind of backup I want.
The information about Vodafone, where does it come from ? when is something expected ?
Ruud
For security sake only.
I am getting nearer to make that final step ;-)
My Winrar was too old, I could unzip the .zip file to a .exex, but I could not unzip the .exe file further. Just downloaded the latest Winrar, now I can see all files included in the provided .exe file.
1) I understood that I should delete the original upgrade-file called ROMUpgradeUt.exe.
2) When I start the MaUpgradeUt_noID.exe in a seperate directory with the rest of the files from the .exe I get to see a different HTC device. When I continue, it will not recognize any of the versions from my Universal. I felt unconfortable to continue.
Can it be done without a problem ??
2a) I renamed the ms_.nbf AND radio_.nbf and restart the Utility, it still shows a photo of the wrong device, but it now does recognize the versions of Device CD image version : 1.13.56 Device Extended image version : 1.13.163 and Device Radio image version : 1.04.10
It confirms to change to CD image version 1.13.53 and leaves the extended image version : "empty" as well as the Radio image version : "empty"
Does this mean that by taking away the ms_.nbf and radio_.nbf files I can stop the device from upgrading the extended rom and the radio ?
Why I ask ? Because if I renamed ms_.nbf back and ONLY radio_.nbf is unavailable now, it shows to change the Extended Rom too, but the Radio image is still empty.
Finally if I rename ALL back, it shows to change all, but all version numbers are older once ;-(
Main question here is, can I leave radio_.nbf away, upgrade and hope for radio to be my version 1.04.10 ?
Ruud
Hi,
I'm back.
I'll PM you Upload information...
private information are not copied.
Only if you have saved private information in your /windows/ folder!
i have never being asked to agree for program access :?
...but I started it of the root-directory of my device.
what is the name of your 'Storage Card' folder?
I not realy have the info from Vodafone, but for all devices before there have been more than one update. But I can't tell when the first update is expected.
If you are trying to make a backup: you will need a terminal program
About dumping
So I have a complete "new" device now.
Did a hard-reset, after which I did not give any new information to the device.
I placed the .exe file You gave me in the \windows\startmenue before, after which it is asking tonloads of access requests.
Now I replaced it in the root-directorym Yes, no additional questions asked anymore, perfect, well NO. As there is no directory made on the storage card. I tried it once with the async active and once with the device seperate. No result.
Any ideas ?
what is the name of your 'Storage Card' folder in your root?
As the device is German, it is called "Speicherkarte"
and renaming is not possible (allowed)
OK this is the problem, I'm trying to get the Source code to change that.
found something: this tool will change the folder name from different languages to "Storage card" which is often needed for different tools
Understood.
About my question, as I am still nervously waiting (cannot start the upgrade before You got your data, can I ;-)
Did I understand correctly, that the file MaUpgradeUt_noID.exe is made for different devices from HTC and therefore I do not get a photo of the universal when I start the software ?
If I start the JASJAR_WWE_11353_137_10301.exe I DO get to see the Universal, but of course get the country error.
Did I also correctly understood I can take away the radio_.nbf from the directory and the update will handle both ROM and ExtROM but leave the Radio untouched ?
Will I be entering this "bootloader" status at all, as I do not need any further updates then ? Are there any resets after the upgrade which I SHOULD or SHOULD NOT make to get the device working again ?
Ruud
Hi bebe,
storage.cab works (be it only after a soft-reset)
The program testwm5.exe is much slower now, so the result is taking minutes now (if not tens of).
Looks like the perfect speed of the program while the storage card (at least for his eyes) was absent, was due to "saving into space"
Will upload asap.
Ruud
I'm loading JASJAR_WWE_11353_137_10301.exe its at 60%
MaUpgradeUt_noID.exe is a hacked version, of another device.
So the photo should not be important. (Please wait until i have downladed the file, I'm not realy sure jet...)
OK, I have to wait anyway, because TestWM5 is very slow now, I can see file after file and calmly read it. Before it was running before my eyes. I am afraid this is going to take ages.
We are on the same frequency that the dump I am making is from a device WITH Extended Rom installed. I was NOT soft-resetting during installation, so all Vodafone add-ons, are to be there now.
If You need the one without ExtRom as well, please tell me.
The upload works OK, I prepared a directory there, but uploading is to be done after longer waiting time.
Are You afraid the JASJAR file is not good ? I downloaded it because this one was proposed on this forum.
Ruud
Its not about the ROM its about the MaUpgradeUt_noID.exe I'm not sure if ths is the exe file to update a Universal.
I dont have a Universal only a Himalaya and my up UpgradeUt starts with HimUpgradeUt... .
Was this file mentioned in the readme of the JASJAR exe?
my download is very slow... 70%
I only downloaded MaUpgradeUt_noID.exe because it was proposed here (for the Universal).
I have no Readme.txt inside the exe
EnterBL.exe
GetDeviceData.exe
ms_.nbf
nk.nbf
radio_.nbf
RUU.conf
RUU.dll
UI.dll
Well and of course the original upgrade file ROMUpgadeUt.exe, but I was suppose to delete it.
Only file which I can read is RUU.conf :
[PLATFORM]=857873
[RADIO_TYPE]=2
[SECURITY_FLAG]=1
[DECODER_KEY]=1
[RADIO_FLAG]=2
[GETADDR_TYPE]=1
[JUMPCODE_TYPE]=1
[FORMAT_TYPE]=2
[SCREEN_TYPE]=2
OK, TestWM5 is finally ready, will do compressing and uploading soon.
Ruud

Why my SPV5000 don't want 1.30 rom ?

Hi, i have a SPV5000 and i can put a lot of kind of 1.13 rom inside, like Qtek or Orange.
But impossible to put any 1.30 rom (orange, qtek french or WWE).
I've tried a lot of solution like "put the radio first" ... rest after.
Do you know if it's possible that my hardware version refuse this 1.30 rom?
I think the guy who sell me the spv sell me a pre-serie .
Thanks
The first question I want to ask is: How do you perform the upgrade? Do you use the No ID Tool? If not, try using it. Here is an instructions I made:
The file is extracted in your computer. Once you run the shipped.exe file, you need to go to:
My Computer
Your Drive (mine is Drive C)
Show the contents of this drive
Documents and Settings
Choose your folder name
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
Now go to TEMP folder
Now you will notice a bunch of folders will show up, tons of them to be exact. What you need to do now is click on the shipped.exe file again and "LOOK" for the folder being created because that folder is what you want to copy. If you did not see it created, you have to manually open each folder and look for the files I listed below.
Assuming you found the folder, you will have these following files inside that folder:
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
If the file MaUpgradeUt_noID is not there. You need to get hold of a copy of this file as you need this.
There you have it, REMEMBER, you need to have the MaUpgradeUt_noID file plus all the rest of the file in one folder if you want to upgrade to the ENTIRE I-Mate ROM, QTEK, O2, or whatever ROM you want.
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" alone and click on the "MaUpgradeUt_noID" file to initiate the Radio installation. Basically those 3 files control what you want to update on your device.
Hope my instructions were clear enough for you. Hope this helps.
Thanks for your complete response
Of course i'm using the MaUpgradeUt_noID ... i have no error message during the process but at the end after the hard reset i have black screen.
and to try to only flash the radio I renames other files .
thanks
I steel don't enderstand ....
Do you think the bootloader version is important ?
i have the O.56
SEB152030 said:
Do you think the bootloader version is important ?
i have the O.56
Click to expand...
Click to collapse
It won't hurt to try and update using Boot Loader Mode.
What do you mean "0.56"?
when I put my spv in bootloader mode, I can see on the screen :
on the top : USB
Botom of the screen V.0.56
SEB152030 said:
when I put my spv in bootloader mode, I can see on the screen :
on the top : USB
Botom of the screen V.0.56
Click to expand...
Click to collapse
You might be right. Your exec must be one of the earlier version. I remeber some time ago, someone asked the same question you did. Maybe someone else can help. Have you tried upgrading it using my instructions?
thank you again and of course I've tryed your method.
every thing works with previous version but not on 1.30
i spent 3 days on it .....
SEB152030 said:
thank you again and of course I've tryed your method.
every thing works with previous version but not on 1.30
i spent 3 days on it .....
Click to expand...
Click to collapse
I believe you need to find out how to upgrade the "Serial USB" application on your Universal for the No_ID Tool to work. Other than that you probably need a version of the No_ID Tool that works at an earlier version of the "Serial USB" version that you have. I'm sorry too, if I didn't help.

How to I install NFSFAN's Bell ROM??

I have downloaded the RAR file, but after taking a look at it I can see that it is not like any ROM updates provided by Bell. Can anyon some instruction or point me to another thread that explains this??
Thanks
1)after you download it just extract the file in a new folder
2) Then goto that folder and u will "ROMUpdateUtility" double click on that.
3) just follow the instructions that appears on your computer screen after.
I'm thinking he probably doesn't have WinRAR.
loll thenn ill add another step:
4) download WINRAR and extract the files.
then follow my other other steps.
Do the CDMA Roms require a HARDSPL to flash them? I want to flash a CMDA NSFAN Rom to my friends Vogue and I dont see an stickies for flashing a CDMA rom. I normally spend most of my time in the Kaiser/Raphael Forums.
Any help is greatly appreciated.
Thanks,
Daniel
So I just did a ton of research on the web because the wiki is useless and might as well not exist.
I am using a Sprint HTC Touch with the official Sprint WM6.1 ROM from HTC.
So after my research, this is what I got (Please correct me if I am wrong):
1. Run 2.31.Coke and unlock the phone via USB/ActiveSync
2. Download NSFAN's latest Sprint WM6.1 Rom and extract to desktop
3. Rename ROMFILE.nbh to voguimg.nbh
4. Copy voguimg.nbh to MicroSD card that has been formatted to FAT32
5. Insert MicroSD card in phone, and enter bootloader via holding down the Power/Camera/Reset buttons all together.
6. Flash ROM
7. Hard Reset Phone
8. Enjoy
So to the everyday flasher here on the Vogue forum, are these steps correct? And if so, why dont you take the time to update the wiki so people dont have to ask the same repetitive question 1000 times?
I just cant believe that this forum has zero ROM flashing stickies, or and updated wiki.
Either way, any help would be greatly appreciated.
Thanks again,
Daniel
atomixpaintball said:
So I just did a ton of research on the web because the wiki is useless and might as well not exist.
I am using a Sprint HTC Touch with the official Sprint WM6.1 ROM from HTC.
So after my research, this is what I got (Please correct me if I am wrong):
1. Run 2.31.Coke and unlock the phone via USB/ActiveSync
2. Download NSFAN's latest Sprint WM6.1 Rom and extract to desktop
3. Rename ROMFILE.nbh to voguimg.nbh
4. Copy voguimg.nbh to MicroSD card that has been formatted to FAT32
5. Insert MicroSD card in phone, and enter bootloader via holding down the Power/Camera/Reset buttons all together.
6. Flash ROM
7. Hard Reset Phone
8. Enjoy
So to the everyday flasher here on the Vogue forum, are these steps correct? And if so, why dont you take the time to update the wiki so people dont have to ask the same repetitive question 1000 times?
I just cant believe that this forum has zero ROM flashing stickies, or and updated wiki.
Either way, any help would be greatly appreciated.
Thanks again,
Daniel
Click to expand...
Click to collapse
You are correct, but you do not need to do steps 3 thru 5. After you extract the ROM on your desktop simply doubleclick the RUU utility and it will update your ROM. (you must still be connected via USB to computer) If you want to flash from your storage card instead then do steps 3 thru 7.
I have a bell phone,
and the color screen says .36 and Security Unlocked.
do i have to unlock the phone still ?
its a bell phone, and it was like that when i got it.
does this mean its unlocked?
latinjig said:
I have downloaded the RAR file, but after taking a look at it I can see that it is not like any ROM updates provided by Bell. Can anyon some instruction or point me to another thread that explains this??
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=3680838&postcount=2
Detroit Doug
By the way, who needs WinRAR when you can get 7-Zip, the best all-around file compression/decompression tool around! And it's free. Opens almost anything out there all in one program.
http://7-zip.org/
hey..
i just had a quick question.. is it possible to switch back to the original BELL rom after you upgrade to NFS rom? i know a lot you might think why would you even wanna do that? But I was just wondering just incase..
Absolutely very easy just flash it like the instruction of a stock rom would require you too

Asus P552w/P565 ROM Decryption !!

For all those who are struggling to extract the contents of the '.abi' file for P552w and P565, here is a good news !!
I found these tools somewhere on a non-English forum, while searching for the decryption tools.
It is a command-line tool that directly works on the '.abi' file, and produces the '.nb0' file.
Part02.nb0 is the OS Image and Part03.nb0 is the ExtROM.
Let me know if you face any difficulties. I have used it on my P565 and successfully dumped the ROM (using imgfs tools on the the OS image). Working on the kitchen now....
Hoping for someone to come up with a kitchen for P552w/P565 soon...lol
cheers,
We also have decrypted P565's rom,and now the problem is how to encrypt the rom.Do you found any tools to encrypt it?
gerry86 said:
We also have decrypted P565's rom,and now the problem is how to encrypt the rom.Do you found any tools to encrypt it?
Click to expand...
Click to collapse
Well, decryption and encryption are both resolved. The only issue is to find where the IMGFS checksum is stored, and update the new checksum there. The '.abi' ROM Header is encrypted using some complicated encrption( not XOR ), and I have not been successful in decoding it as of now.
I see you're all experts here. Maybe you can help me.
I just want to know if it is possible to upgrade my italian ROM with an english one (P552w)?
If not I guess I can throw away my Asus while I don't speak Italian
Thanks for your help,
VanGog said:
I see you're all experts here. Maybe you can help me.
I just want to know if it is possible to upgrade my italian ROM with an english one (P552w)?
If not I guess I can throw away my Asus while I don't speak Italian
Thanks for your help,
Click to expand...
Click to collapse
Sure buddy, no need to throw it away...
Just follow these simple steps :
1. Ensure that your Storage card capacity does not exceed 2GB and is not corrupt.
2. Connect the device using activesync and wait till the connection is established.
3. Go to file explorer on your PC and enable the option to display hidden files and folders.
3. Take your English ROM ( .exe file) and execute it from your PC.
4. Press 'next' till you see the error message that the ROM is not meant for your device. Wait !!
5. While this message is still being displayed, go to the folder which contains your ROM ( .exe file). You will see a file called 'tmp_rom.abi'. Rename this file to 'GM5.abi'.
6. Now close the error message screen.
7. Copy 'GM5.abi' to your Storage card.
8. Now Press the "Navipad down"+ "Reset" buttons and keep them pressed until you see the reboot screen.
9. That's it. The ROM flashing process will begin automatically.
10. Do not press any button till the ROM flashing is in progress. The device wil reboot automatically.
Enjoy your new English ROM.
Disclaimer : Hope you are aware about the risks associated with the ROM flashing process.
First of all, thanks rishi for your help, but in my case something doesn't work.
I get to the boot screen where it says that it can not find the file (but it is on the card).
I followed all the steps (including 1GB storage card) but always the same, no success.
Is it possible that this is because of my Asus which was I suppose unlocked before I bought it. It has an Italian mobile provider logo on boot screen?
Do you have any other solution for my problrm?
Thanks again for your effort,
Van Gog
Found a solution!!!!
The name of *.abi file must be the same as the name of an *.exe file!
WOW!
Thanks a lot, you saved my Asus!!
Greetings,
VanGog
It should be GM2_name.abi and don't forget to clear hidden attribute.
For me it works also on 4GB card.
rishi, you said that "decryption and encryption are both resolved", is it using the same tool? I cannot say I got it...
weiqiix,
You may use this tool: http://forum.xda-developers.com/showthread.php?t=511158
Thank you very much, I'll test it right now.
Then I could even understand what (and how) to do with those *.nb0 files,
and who knows, I could understand my p552w's internals
If anyone can fix the camera and video problem that will be perfect!

[APP - release] general Flashaholic Rom Update Utility - v1

warning: this tool is for flashaholics. The ones who know all risks of flashing roms and like to live in the fast lane
Note for HD2-users: Although this version can be also used for the HD2, you may like this version more (the HD2 version doesn't require that you provide a "preflash" .nbh file - see further).
- Description:
FlashaholicRUU (FRUU) is a customized version of the HTC Rom Update utility that will simplify the rom update proces by:
1. performing a task29 before updating a rom
2. allowing the user to navigate through the dialog windows without having to check checkboxes (s)he has seen a gazillion times before.
3. allowing the user to use only the keyboard to go through the dialog boxes (enter -> next window, esc -> quit fruu)
- Prerequisite
Task 29 is performed by flashing a .nbh file before the (custom) rom file. Because the tool is meant to be general applicable for all devices you need to provide this "pre flashable" .nbh file yourself. In principle you can use any .nbh file for this. To speed up this first step though it is recommended to use a radio for your own device or better yet, a .nbh file containing only the splashscreen for your device. Rename this file (radio, splashscreen ) preflash.nbh and put it in a directory together with your custom rom file (may have any name as long as it has an .nbh extension) and the general_FlashaholicRUU.exe. Make sure there aren't any other files in the directory.
For the rest follow the instructions described in the section Usage
- Usage:
This program will take you through the steps of performing a Task29 (formatting your roms storage memory) and then flashing a new rom. It is not advised to use this if you are totally new to flashing roms as if it is done incorrectly you will end up with no rom on your phone and a permanent look of terror on your face
This is not for noobs!!
1. Make sure your phone is booted up
2. Sync your pc and phone
3. (you may skip this step if you've read the prerequisite) Copy the general_FlashaholicRUU.exe file to a new folder with JUST the roms .nbh file present and a rom you want to flash before you flash your rom. Rename this last rom file, the one you want to flash first, preflash.nbh
4. Run the general_FlashaholicRUU.exe and follow the instructions in the program
5. Click on the "perform task29" button to format your roms memory
6. As soon as the percentage bar reaches 100% hold your "volume down" button and continue holding until the phone reboots and enters the bootloader screen
NOTE: If you get a white screen with "hTC" in the middle then you need to take out your battery and enter bootloader mode manually before continuing (take battery out and put it back in, then hold the volume down button and briefly press the power button. Keep holding the volume down button until the bootloader screen appears).
7. When the white box in the bottom of the bootloader screen says "USB" then click on "Flash Rom" in the Flashaholic program
8. Follow the onscreen instructions and lastly click on "Flash" to flash the rom to your phone
9. You will now have a percentage bar on your phone and your new rom is being flashed
10. Once your Rom has flashed your phone will reboot and you can go through the setup screens.
Run your new Rom for a few hours, search for another one and start again with step 1 (if you want to become a real senior flashaholic)
NOTE: There is no need to perform a Hard Reset after flashing the Rom using this program as the Task29 performs a much more thorough job.
--------------
When you want to flash a rom without performing task 29 (for example when you want to flash a new radio) just hit <ESC> on the first screen of step 1. This will take you right to step 2 in which you can flash your rom
Click to expand...
Click to collapse
(Thanks to mskip for writing this brief but comprehensive manual)
- Video:
Video of the app on a computer of a fellow flashaholic: http://www.youtube.com/watch?v=hn3pGbW-vag. Thank you claub. Keep on flashin'
- Note to chefs:
You can pack FRUU with your Roms. You can even customize FRUU for your Rom series. For example you can use your own images, text, info etc. I have written some general instructions about customizing the RUU here. (Notice that in FRUU ModelID.fig is used for the first task29 step and RUU.fig is used for the second step. The dialogs for the first step are part of RUUResource.dll. Dialogs for the second step you will find in CustomizedRomResource.dll. Instead of the setup.bat and setup.vbs I mentioned in the aforementioned post I used the files run.bat and run.vbs. For exra information you can PM me)
- Donations:
Thank you!
Thanks to: doloop (for his non-mtty task 29 tool)
---------
Note: this tool should work for any (newer) htc device. Nevertheless make sure that your bootloader will support task 29 and that experiments with mtty task 29 has positive results for your device (look at the development section for your device forum)
Devices on which this tool is reported to work:
* Leo (HD2)
* Rhodium (Touch Pro 2, Tilt 2)
* Topaz (Diamond 2, Pure)
* Raphael (Touch Pro, Fuze)
* Diamond
(please pm me or report your device in this thread if the tool worked also for your device and that device is not in this list yet)
Click to expand...
Click to collapse
Happy flashing
appelflap said:
Rename the radio rom file to radio.nhb[/COLOR]
Click to expand...
Click to collapse
Not Radio.nbh? Isnt it typo?
Petulinek said:
Not Radio.nbh? Isnt it typo?
Click to expand...
Click to collapse
Yes, it is a typo. Should be radio.nbh
sure need to test.
what diff between task 32, task 29 and task 28
im on blackstone, so that using only task 29
core7x said:
sure need to test.
what diff between task 32, task 29 and task 28
im on blackstone, so that using only task 29
Click to expand...
Click to collapse
task 28 hard resets the device. It is the default task executed by the shipped romupdateutiliy (RUU). Custom RUU's one find here on xda have replaced task 28 with a task 32 (security level check). That way you can use the custom ruu to flash a radio or a bootscreen. You don't want a hard reset after that
Task 29 formats the device.
It should work on the blackstone. From what I've read the bootloader supports those commands. As far as I know those commands are also supported by the bootloader of other newer HTC devices as well.
Make sure you have HSPL installed. (or how it is called for your platform)
-----
(BTW for anyone who like to experiment with the above util, you can extract the exe and examine run.bat ...
If the RUU's in this package don't work use the RUU for your device. Open it with a hexeditor. search for "task" and change the digits "28" behind it to "29" and save it as "Task29.exe". Do the same again, but now change "28" to "32" and save it as RomUpdateUtil.exe. )
appelflap said:
task 28 hard resets the device. It is the default task executed by the shipped romupdateutiliy (RUU). Custom RUU's one find here on xda have replaced task 28 with a task 32 (security level check). That way you can use the custom ruu to flash a radio or a bootscreen. You don't want a hard reset after that
Task 29 formats the device.
It should work on the blackstone. From what I've read the bootloader supports those commands. As far as I know those commands are also supported by the bootloader of other newer HTC devices as well.
Make sure you have HSPL installed. (or how it is called for your platform)
-----
(BTW for anyone who like to experiment with the above util, you can extract the exe and examine run.bat ...
If the RUU's in this package don't work use the RUU for your device. Open it with a hexeditor. search for "task" and change the digits "28" behind it to "29" and save it as "Task29.exe". Do the same again, but now change "28" to "32" and save it as RomUpdateUtil.exe. )
Click to expand...
Click to collapse
clear, will do that
core7x said:
clear, will do that
Click to expand...
Click to collapse
You naughty boy... naughty naughty naughty
appelflap said:
You naughty boy... naughty naughty naughty
Click to expand...
Click to collapse
joke only, by the way. im flasholic rom person.
core7x said:
joke only, by the way. im flasholic rom person.
Click to expand...
Click to collapse
I kinda hoped that you noticed the ironic undertone of my reply
appelflap said:
task 28 hard resets the device. It is the default task executed by the shipped romupdateutiliy (RUU). Custom RUU's one find here on xda have replaced task 28 with a task 32 (security level check). That way you can use the custom ruu to flash a radio or a bootscreen. You don't want a hard reset after that
Click to expand...
Click to collapse
OK, this sounds like a bad idea taken even further.
Hard reset reloads nvram and ram from flash. Radio and bootscreen are in flash, so a hard reset will do nothing to them.
Unless HD2 is different from all other HTC devices (I seriously doubt it, but do not know), stock ruu should flash radio and bootscreens found in custom roms just fine. This makes sense, of course, because carriers don't release different ruu's just because radio update or bootsplash are included in .nbh.
As to erasing flash before flashing....what a waste of time. I can imagine almost no case where this would be beneficial, and it certainly is wasteful in 99.99% of cases. Why would you want to degrade memory 2x as fast (or more) on a routine basis? Flashing RARELY (like never) fails to overwrite, and when it does, it won't help you to have 0's where it fails.
gguruusa said:
OK, this sounds like a bad idea taken even further.
Hard reset reloads nvram and ram from flash. Radio and bootscreen are in flash, so a hard reset will do nothing to them.
Unless HD2 is different from all other HTC devices (I seriously doubt it, but do not know), stock ruu should flash radio and bootscreens found in custom roms just fine. This makes sense, of course, because carriers don't release different ruu's just because radio update or bootsplash are included in .nbh.
Click to expand...
Click to collapse
Not when you just want to update your radio without updating or resetting the os
As to erasing flash before flashing....what a waste of time. I can imagine almost no case where this would be beneficial, and it certainly is wasteful in 99.99% of cases. Why would you want to degrade memory 2x as fast (or more) on a routine basis? Flashing RARELY (like never) fails to overwrite, and when it does, it won't help you to have 0's where it fails.
Click to expand...
Click to collapse
If i don't do a format before flashing a new rom - time has shown me this again and again - i get some serious battery drain problems. Of couse I like to pass this step... but..
and with respect to your other advice, this is a tool for flashaholics you know. I don't think flashaholics worry very much about the memory of a device they use for 1-2 years max.
appelflap said:
If i don't do a format before flashing a new rom - time has shown me this again and again - i get some serious battery drain problems. Of couse I like to pass this step... but..
Click to expand...
Click to collapse
I totally quote appelflap on this one.
I've never ever had battery drain problems with my flashes, the very first time I had those is when I attempted at flashing just a new radio radio keepin the rom and the data. Before thatm, flashing a new radio always was done when flashing a whole new rom, and after a task29 anyway.
After that "radio only" flash, hell ensued, as no matter the radios I changed thinking it was the radio version's fault, I was getting up to 16% drain overnight, and anyway not lower than 12%, against a normal 4-5%, with a standby drain of 20mA and more, against a normal of 4-7mA.
Next thing I did, task 29 + radio + rom and now I'm getting a whopping 3% drain overnight with my current rom combo, never went so low.
Tested this morning on a Raphael (ATT Fuze). Worked well. Task 29, radio flashed and ROM flashed. No problems at all.
Also tested with a Rhodium(ATT Tilt2). Same results.
Makes ROM flashing much faster. Now if there was just someway of not having to press the down volume button at the end of task 29 it would be perfect.
Good work Appelflap!!!
resqman said:
Tested this morning on a Raphael (ATT Fuze). Worked well. Task 29, radio flashed and ROM flashed. No problems at all.
Also tested with a Rhodium(ATT Tilt2). Same results.
Makes ROM flashing much faster. Now if there was just someway of not having to press the down volume button at the end of task 29 it would be perfect.
Good work Appelflap!!!
Click to expand...
Click to collapse
Thanks for testing! I think you helped a whole lot of flashaholics
BTW: If you have a original nbh file of the first bootscreen of your device(-s) you can use that instead of a radio ... For now, (till I uploaded a new version) just rename the bootscreen to radio.nbh and put it in the folder from where FlashaholicsRUU is run. Flashing a bootscreen in the first task 29 step is so much faster.
EDIT: about putting the device back in bootloader after the first task 29 step: if I only knew the bootloader command for it I could make it work without any problems. So if anybody has any idea, please let me know, I can hexedit the RUU to execute this command right after task 29 is performed.
appelflap said:
Thanks for testing! I think you helped a whole lot of flashaholics
BTW: If you have a original nbh file of the first bootscreen of your device(-s) you can use that instead of a radio ... For now, (till I uploaded a new version) just rename the bootscreen to radio.nbh and put it in the folder from where FlashaholicsRUU is run. Flashing a bootscreen in the first task 29 step is so much faster.
EDIT: about putting the device back in bootloader after the first task 29 step: if I only knew the bootloader command for it I could make it work without any problems. So if anybody has any idea, please let me know, I can hexedit the RUU to execute this command right after task 29 is performed.
Click to expand...
Click to collapse
Might it be possible to have it check for the existence of a radio.nbh file and if it doesn't exist skip that? I know it is handled by a batch file so there must be a way around it.
I flash a lot of ROMs but I rarely flash radio or bootscreen
resqman said:
Might it be possible to have it check for the existence of a radio.nbh file and if it doesn't exist skip that? I know it is handled by a batch file so there must be a way around it.
I flash a lot of ROMs but I rarely flash radio or bootscreen
Click to expand...
Click to collapse
The bootscreen or radio is needed in step 1. Task 29 is performed after flashing one of these. I will look for another solution when my HD2 is repaired.
appelflap said:
The bootscreen or radio is needed in step 1. Task 29 is performed after flashing one of these. I will look for another solution when my HD2 is repaired.
Click to expand...
Click to collapse
I have performed task29 on both Fuze and TP2 without having to flash a radio.
From the task29 section of the Rhodium forum:
Originally Posted by SacTilt
Some of you are making this too difficult. I've posted this before, as this is all that needs to be done. Task29 does not remove your radio or your splash screen. It only clears the ROM, therefore, all you need to do is run Task29 and then flash your ROM. This is how I do it from the PC.
Connect to PC via Active Sync/WMDC.
Execute Task 29.
When phone boots to "Touch Pro 2" screen (or whatever your splash screen happens to be), I hold down the volume down button while hitting the reset button.
Once I'm on the Bootloader screen, and it shows "USB", I flash the new ROM from the PC as I normally would.
When the phone vibrates, indicating the ROM upgrade is complete, I disconnect the phone from the computer.
Click to expand...
Click to collapse
Obviously I am missing something here
resqman said:
I have performed task29 on both Fuze and TP2 without having to flash a radio.
From the task29 section of the Rhodium forum:
Obviously I am missing something here
Click to expand...
Click to collapse
Thanks for your feedback! This was exactly the feedback that I was looking for.
The task29 tool from the rhodium forum flashes a ruu_signed.nbh that is specifically brewed for the rhodium. Indeed flashing this file doesn't touch anything.
Problem is I can't use such device specific files for a universal flashing tool. That's why I use radio nbh. So that I'm sure that the tool runs task 29 with a nbh file that is accepted by the device that is flashed.
The ruu_signed.nbh that task29 uses for the rhodium is 8.5 mb large. This will take more time to flash than a bootscreen (which is 0.7mb) but less than a radio (which is > 10 mb). May I suggest to use this tool with a bootscreen nbh it is soooo much faster.
Anyway when I get my device back I will look if I can brew a small nbh file that doesn't change the bootscreen or radio. I will target it to different devices and wrap it up for each specific device.
Again, thanks for your input.
-------------------------
Edit: I've attached the nbh file that is used by the rhodium task29 tool. Use this one instead of a radio. It doesn't alter you radio nor your bootscreen. Although the file is named radio.nbh it isn't a radio (the current test tool need that filename). You can try this for your rhodium.
appelflap said:
-------------------------
Edit: I've attached the nbh file that is used by the rhodium task29 tool. Use this one instead of a radio. It doesn't alter you radio nor your bootscreen. Although the file is named radio.nbh it isn't a radio (the current test tool need that filename). You can try this for your rhodium.
Click to expand...
Click to collapse
I understand now. It's not really a big deal for me to flash a radio. It would be a lot of work for you to have to create a signed ruu for every device.
Thanks
Thanks!!!!

Categories

Resources