Related
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.
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
Hi all guys and gals
I hope this post will help all noobs by giving the most important guidlines for upgrading the ROM, CID unlocking and upgrading SPL & IPL
Please follow the instructions exactly in the order written
1. READ THROUGH XDA-DEVELOPERS.COM.. TRY TO UNDERSTAND WHAT YOU WANT TO DO WITH YOUR DEVICE BEFORE ATTEMPTING ANYTHING SUGGESTED OUT HERE.... This is very important and might save your device
2. Try and find out what to do if something goes wrong.. Its highly likely that something will go wrong if you do something wrong..
3. Now if you still think you want to upgrade your operating system (Windows) then do the following step by step
a) Download the required SPL & IPLs from the forum.. you can find
the most suitable ones in your respective device fora
for elf and elfin you can checkout these threads
http://forum.xda-developers.com/showthread.php?t=408637
http://forum.xda-developers.com/showthread.php?t=445666
http://forum.xda-developers.com/showthread.php?t=408637&page=72
b) Read carefully through those threads
c) Unzip the zip archive containing elf_uspl.exe and other filees
to your computer's c drive
d) Connect your device to your computer using the usb cable.. and in
your device go to settings and open usb to pc tab and disable
advanced networking capability
e) Make sure that the activesync is enabled(appears green in the try)
f) Close any application running on your device and make sure that
your device battery is atleast 50%, disable hibernation and screen
saver option on your computer
g) Open the folder you unzipped already and run the file with a name
which looks like elf_uspl.exe and follow the onscreen instructions
h) Now your device is CID unlocked successfully (your device screen
should go white and then you should be able to see a penguin logo on
your device screen.. if that doesn't happen then you should repeat
the process.. THIS STEP IS THE MOST IMPORTANT ONE.. DO NOT AT ANY
COST PROCEED FURTHER IF THIS DOES NOT HAPPEN...
i) Now run the RUU(ROM UPDATE UTILITY). This can be found in the
unzipped folder(open the unzipped folder and you will see another
folder with a name RUU
j) Follow the instructions on the wizard..
NOTE: DO NOT DISCONNECT/RESET YOUR DEVICE BEFORE OR AFTER THIS
k) Wait for the wizard to finish its job.. do not inturrupt.. If the
wizard gives any error then please hard reset your device(hold down
call & hangup buttons together and push soft reset button and keep
holding the buttons till you get a warning message on the screen).
Restart the whole prpcess again.
l) If the wizard completes the update successfully, then your device
will re-boot..
m) You can hard-reset your device now.
n) Now your IPL & SPL is successfully upgraded and you can move on to
upgrading the Operating System
o) To upgrade your OS you need to search for and download the
appropriate ROM from this forum.. you will get plenty of ROMs
floating around.. so pick yours and extract it the root of one of
the drives on your computer.. Open the unzipped folder.. connect
your device to your system.. follow all the precautions already told
and run the RUU found in the folder.. Follow the onscreen
instructions.. Do not intrrupt the process..
p) If the update wizard gives any error then repeat the whole process
q) After finishing your device will re-boot and you will have a new
device in your hand..
Do not forget to thank all the hard working guys here who made all this
possible.. and please donate to the developers and hackers..
Hope my advice would help all the noobs..
If you find this useful.. you can thnk me and can rate this thread
My Thanks to !Aman! and all other great guys here
One more important thing before CID Unlocking
Sorry guys I forgot to add a little detail...
Before you try to CID unlock your device you need to download and install these 2 small .cab files on your device.. this step is a neccessary one for ELF n ELFIN
you can download these files from here
first download and install this Cert_Spc.cab
And then download and install Enablerapi.cab
DONT FORGET TO THANK AND DONATE TO XDA-DEVELOPERS
Another Note
Please visit this thread for some more details
Read below for updating ROM through sd card
1. First CID unlock your device and flash the coocked USPL & IPL as instructed earlier
2. Copy the .nbh file (THE ROM .nbh) to the root of your storage card and rename it as ELF0IMG.nbh
3. Turn off your device and now hold the CAMERA button and POWER button together and keep them pressed and now push and leave the SOFT RESET button with the stylus and release the other buttons when you see the bootloader screen..
4. Follow the onscreen instructions and choose the appropriate option.. thats it.. your devices' ROM will be updated.. soft reset or hard reset your device after this..
ENJOY
i have same HTC Touch 128/256 but i did mistake and now my touch showing RED,GREEN,BLUE Screen RUU HELP ME
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!!!!
Hi all,
I can't figure it myself, Can anyone from the experts here compile a andboot folder with latest initrd, kernel & Haret, so noobs like me run Android on their Kaiser from SD without deleting original WM.
many thanks in advance,
a) That's really really lazy man!
b) Not every kaiser has the same configurations (panel type, key mapping, etc)
c) Not all the users would like the same build
d) That's really really lazy! (again)
Try this guide: its noobs-proof and I assure you than in less than 15 mins ul be running android on ur kaiser:
http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsHaret
What OS does this guide use? OSX.
what about Windows based PCs? like the one I have?
Is still possible to compile Andriod on Windows? I know the answer OF COURSE NOT.
Alberto, Not everyone see it easy as you did. If you want to help, give a hand. if not thanks.
yassermekled said:
What OS does this guide use? OSX.
what about Windows based PCs? like the one I have?
Is still possible to compile Andriod on Windows? I know the answer OF COURSE NOT.
Alberto, Not everyone see it easy as you did. If you want to help, give a hand. if not thanks.
Click to expand...
Click to collapse
LOL no man! that's why we are here right? to find answer to all our doubts... some months ago I had no idea bout android!! Now im a little more "versed" in this matters but compared to a lot of ppl here i find myself as a noob! But its not that complicated ull see:
First download Haret latest ver:
http://it029000.massey.ac.nz/vogue/files/
download haret-for-kernel-2-6-32.exe file
ull copy it to your SD later...
also look at the forum and search for a build, an example can be this one, its a donut build and i have found it really stable under NAND installation:
http://forum.xda-developers.com/showthread.php?t=796193
its not the latest version of android (froyo) but ull find it easy and reliable, you can try a froyo build too but be carefull, not all builds are made to run in haret.
then download python (needed to run atools, no need of OS X )
http://www.python.org/download/
please be sure to download only the 2.6 or 2.7 version
install it
Downoad version 1.04 of atools from here:
http://sourceforge.net/projects/androidhtc/files/AtoolsRelease/
look for atools-1.0.4.py
Run it
Follow the guide I provided you before,
1. Select haret on the button "D"
2. under device select kaiser
3. select the resolution u prefer, 240 is the native res for our kaisers, but you could try the other ones..
4. select wich version you will install, in my example you would select donut, but you should try different builds and keep the one you prefer.
5. the panel type... well this is a little complicated, kaisers have diferent types of screens and there's no accurate way to now wich panel type u have unless you try out! so basically ull have to try each one of the types (1, 2 or 3) if you see strange colors, or black dots in the screen, ull have to reflash the kernel so lets start with the panel 1, you could try to use the auto option but im not totally sure it would work...
6. key map: if you have a unbranded TyTn II (not the AT&T tilt) select normal, if u got the tilt select this option or one of the other special key mappings
7. ill recomend u to leave all the rest of options unchecked for the first time, but if you want to give it a shot, try reading the guide i posted before.
8. save the file with the diskette button
Format your SD with FAT32, create a folder named andboot
copy the file previously made to it,
copy haret to it too.
download the latest zImage with the world button, save it to the andboot folder.
download latest initrd from the button with a box and an arrow, again copy it to the andboot folder.
lastly copy the androidinstall.tar (could be .tgz too dont worry) of the build u prefer to the andboot folder
insert the SD to your phone, run winmo, go to the file browser, search the andboot folder, run haret, press run, the phone will reboot, and ull se a pretty lil penguin and a lot of text scrolling down, put attention and press d-pad (silver center button) when the system prompts u to do so, select install system and wait for it to return to the main menu, select quit, and voila! remember if you find issues on the display, go back to atools and make another default.txt but this time with panel 2, or panel 3 type.
this is not as good as the guide l1qu1d made, i wrote this in 5 mins, he probably spent a lot more time writing it and testing it, i really suggest you to read that guide before trying anything, m not responsible of anything going wrong, actually the worst thing that could happen is u to NOT run android , thats why i suggested it on my post....
Thank you for this guide, i personaly found the original very hard to understand. I have spent an entire day trying to get android on my phone but to now avail. I did managed to get super froyo on for about 5 mins before it white screened on me and froze. It was also very slow. All other attempts didn't get past the linux screen. I'll keep persevering though!