i thought of re doing doloop's modd for TP2
and here it is fully tested to be working
now we can mtty our TP2 without having the need of MTTY and its drivers
INSTRUCTIONS:
SacTilt said:
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
DOWNLOAD:
From here
http://valkyrie.htc-files.com/downloads/roms/valkyrie/rhodium/task29.zip
CREDIT:
all credit goes to doloop for coming up with the idea
doloop said:
Hi,
I hex edited RomUpdateUtility.exe so it runs task 29 right after flashing ruu_signed.nbh
As every one understand this command format the rom,
Just unzip and run task29.exe . You may replace ruu_signed.nbh with the radio of your choice.
After the phone reset itself, your old rom will be gone, so it won't boot: binfs has been formated, your phone memory is clean.
You'll need to power up in bootloader mode (press vol down right after power key), then use the leocustomruu.exe provided with your favorite rom package, or flash it from memory card using standard procedure.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=5845908&postcount=1
May I ask what this is used for?
petard said:
May I ask what this is used for?
Click to expand...
Click to collapse
off course
when u flash a rom, you are copying files onto the internal memory (like duh!) but if u repeatadly flash different roms, sometimes files from older version stays behind as when u flash a rom, you just copy and sometimes overwrite files without deleting the older ones. hence at times these older files may create bugs\instability. hardrest donot always fix it.so we use MTTY
read this post to know what made me such a firm fan of mtty.http://forum.xda-developers.com/showpost.php?p=5898010&postcount=6085
but the thing is, mtty is and can be hard to use for new users. ... for me,, i was having the worst time installin the drivers needed to run mtty on win7 x64. so u i made this tool for me and for all
agent_47 said:
- run then ROMUpdateUtility.exe and wait for it to finish.....
Click to expand...
Click to collapse
Nice tool.
Is it possible to run this tool from mSD card, since my phone cannot connect to PC via USB?
bookmarked thanks Badwolve1
Thanks for simplifying this process agent_47. One question, can we do a backup using spb, then use the tool, reflash a rom and restore the backup? Or does the backup cause those possibly bad or corrupt files to be copied back to the device? Just wondering if I can save some time of setting the rom back up
TorbenKB said:
Nice tool.
Is it possible to run this tool from mSD card, since my phone cannot connect to PC via USB?
Click to expand...
Click to collapse
nope....that exe is a win32 app....our device is only a win CE
kwill said:
Thanks for simplifying this process agent_47. One question, can we do a backup using spb, then use the tool, reflash a rom and restore the backup? Or does the backup cause those possibly bad or corrupt files to be copied back to the device? Just wondering if I can save some time of setting the rom back up
Click to expand...
Click to collapse
u can, but i don do that. the max i do is backup some regs. with sooo may different form of wm6.5, i would sta y way from entire system back up....
but to answer ur question, spb backup wont through any bugs related to corrupt file/bad sectoring/mirror files
How to flash new stock HTC ROM after Task 29?
Hey, just wondering how I would flash the new stock HTC rom after task 29, as it is just an exe file with no custom RUU?
Thanks!
mmicha said:
Hey, just wondering how I would flash the new stock HTC rom after task 29, as it is just an exe file with no custom RUU?
Thanks!
Click to expand...
Click to collapse
The EXE is probably just an archive. Open it with your favorite archiving app (7-zip, etc) and you will see the NBH
So I would assume you shouldn't have to hard reset after flashing a rom if you first perform this internal format, correct?
agent_47 said:
nope....that exe is a win32 app....our device is only a win CE
Click to expand...
Click to collapse
I think he means can we just flash the nbh file from sd card instead of using the ROMUpdateUtility through USB.
mmicha said:
Hey, just wondering how I would flash the new stock HTC rom after task 29, as it is just an exe file with no custom RUU?
Thanks!
Click to expand...
Click to collapse
use the custumruu provided with ur rom. eberithing uploaded by me in the archive is only to be used for task29
bjevers said:
So I would assume you shouldn't have to hard reset after flashing a rom if you first perform this internal format, correct?
Click to expand...
Click to collapse
ya....but it wont hurt to do so either
bjevers said:
I think he means can we just flash the nbh file from sd card instead of using the ROMUpdateUtility through USB.
Click to expand...
Click to collapse
either ways, the answer is a no
agent_47 said:
either ways, the answer is a no
Click to expand...
Click to collapse
Ok. Thanks. I need to get the USB plug fixed then..
thanks for this! much faster than reverting to stock rom occasionally to "clean up"
agent_47 said:
u can, but i don do that. the max i do is backup some regs. with sooo may different form of wm6.5, i would sta y way from entire system back up....
but to answer ur question, spb backup wont through any bugs related to corrupt file/bad sectoring/mirror files
Click to expand...
Click to collapse
Thanks much Agent_47. I only use the backup after I completely set up a rom the way I like it. That way I can quickly go back to that same setup if I have to (crashes or whatever the cause may be). ONLY on the same exact rom though, build and chef. And to make sure I understand, spb backup doesnt touch sectors of internal memory anyway (just reg entries and actual files) , so it shouldn't matter using a backup copy after using task29?
weird?
got a problem, i used the Task29 internal memory format tool from agent_47 to clean im internal memory. put the nbh file on a blank 2gb formatted sd card. put the card inside the rhodium, held down the vol down button and powered on, im in the boot loader but it hasnt progressed anywhere? the connection type says serial... any ideas?
when i just power on my phone, they only thing that shows is the ATT world phone image
johng75 said:
weird?
got a problem, i used the Task29 internal memory format tool from agent_47 to clean im internal memory. put the nbh file on a blank 2gb formatted sd card. put the card inside the rhodium, held down the vol down button and powered on, im in the boot loader but it hasnt progressed anywhere? the connection type says serial... any ideas?
Click to expand...
Click to collapse
yes. because ur not reading instructions......(remane nbh)
also if ur nbh is less that 20mb, read post 1 again
sorry, i re-read what i wrote, let me rephrase... after i ran your tool from my computer while connected via usb, it finished and rebooted, i them put my rom nbh file (RHODIMG.nbh, 186mb) on a blank sd card, entered boot loader and thats where i am
[SOLUTION FOUND]
i took out the mSD card, loaded into bootloader, and when i plugged in the USB cable, it changed from serial connection to USB and let me flash from my system... ill poke around in the flashing thread for my mSD card issue...
your tool works great!
Awesome tool! Saves me time. Thanks again!
thank you, works excellent
Related
I have O2 XDA III (german), with radio rom v.1.10.0.
I've tried to find the way how to backup that rom and upload it to FTP. Can someone tell me how to do that. I've searched the wiki, but I didn't found the real solution.
Do I need to use XDArit or XDAtools? Can I do it under Win98, or I need WinXP/2000?
I have SD card and SD card reader.
I've described the process here:
http://forum.xda-developers.com/viewtopic.php?t=18128#98117
You can do this under Win98.
mamaich said:
I've described the process here:
http://forum.xda-developers.com/viewtopic.php?t=18128#98117
You can do this under Win98.
Click to expand...
Click to collapse
I've tried this and it doesn't work. When I press ok, I don't get terminal window. I've also tried this using COM2 (thats my modem) and it works fine, but with usb I don't get nothing
you should terminate Activesync before running MTTY. Kill processes wcescomm.exe and wcesmgr.exe with task manager and enter bootloader on your device (press and hold power+camera buttons and reset). The screen would write "serial ...", insert it into cradle, screen would write "USB ...". Run MTTY, select "usb" or "\\.\wcescom01" port and everything should work.
And don.t forget to do a backup, this will hard reset your device.
Thanks in advance for sharing your Radio! I've asked in any Forum, i know, but nobody seemed to cooperate. So it is great hearing somebody helps us.
mamaich said:
you should terminate Activesync before running MTTY. Kill processes wcescomm.exe and wcesmgr.exe with task manager and enter bootloader on your device (press and hold power+camera buttons and reset). The screen would write "serial ...", insert it into cradle, screen would write "USB ...". Run MTTY, select "usb" or "\\.\wcescom01" port and everything should work.
And don.t forget to do a backup, this will hard reset your device.
Click to expand...
Click to collapse
The problem was in win98, in WinXP everything worked fine. So, this stuff doesn't work with win98. When I backuped it, I couldn't transfer the backup on my computer (ntrw transfers 256Mbytes and says that something is wrong with the image). I think the problem is that I have MMC card, not SD card. I should get SD card today, and I hope that everything will work then.
Hope the upload will work, just put it in the root dir, as you can not put it in any of the folders.
Curious to see if this further improves GSM/GPRS etc...cheers!
Can't wait to hear the feedback on the 1.10 radio. I was going to go 1.08 but seems like a waste when this one is so close.
Ok, HappyGoat, do you have the path you saved too for this magic Radio?
1.08 is nice, works fine. Of course I must upgrade for no reason other than insanity, hence Im looking for the file.
Thanks
Rich
Is it also possible to extract the whole ROM from your device, so that I can update my SPV M2000 with your O2 ROM?
Any news about this new radio rom?
ringram said:
Ok, HappyGoat, do you have the path you saved too for this magic Radio?
1.08 is nice, works fine. Of course I must upgrade for no reason other than insanity, hence Im looking for the file.
Thanks
Rich
Click to expand...
Click to collapse
The Radio 1.08.00 is available again on the ftp server. Have a look in the BlueAngel folder, it's in there.
Any progress on getting the radio 1.10.00 version...?
I've borrowed SD card from a friend, and I have to bring it back until saturday. So, I need some quick answers.
It is 256Mbyte SD card. I've done the procedure of backup like instructed. You can see my log in attachment.
After that I put the card in Transcend 7 in 1 card reader. I've used ntrw to backup the SD on my computer, but something is wrong. It creates 256MByte file on my computer. The picture of console window is in attachment. I did like I was instructed, and i've also tried "d2s" (to backup only WinCE) and all combinations (only Radio Rom etc.), but the result is the same.
Any suggestions? I really need to do this quickly.
Try this command in DOS:
Code:
C:\ntrw read XDAIIs.nb1 i:
Just might work, not sure. In either case, thanks alot for trying and sharing this with us...
No ideas?
DreamerNS said:
I've borrowed SD card from a friend, and I have to bring it back until saturday. So, I need some quick answers.
It is 256Mbyte SD card. I've done the procedure of backup like instructed. You can see my log in attachment.
After that I put the card in Transcend 7 in 1 card reader. I've used ntrw to backup the SD on my computer, but something is wrong. It creates 256MByte file on my computer. The picture of console window is in attachment. I did like I was instructed, and i've also tried "d2s" (to backup only WinCE) and all combinations (only Radio Rom etc.), but the result is the same.
Any suggestions? I really need to do this quickly.
Click to expand...
Click to collapse
DreamerNS,
it is normal that you get a 256MB file, because your card has this kind of size!
The ntrw tool makes a full copy of your SD card it don't know how much data on your card is stored.
So make a full backup of your XDA, zip the 256MB file and upload the file to the ftp site.
Greetings
osch
DreamerNS said:
No ideas?
Click to expand...
Click to collapse
My suggestion did not work?
HappyGoat said:
DreamerNS said:
No ideas?
Click to expand...
Click to collapse
My suggestion did not work?
Click to expand...
Click to collapse
No. It is just filename, you can put anything you like there. it can be xdaIIs.nb1 or xdaIII.nb1 or IdontKnow.nb1 it doesnt change things, but thanks anyway.
It's too much for me to upload 256Mbytes. I have only dialup connection. Is there any way to extract radio rom from 256Mbyte file? If everything is allright, why is it says "ReadFile(): xdaIII.nb1 -- parameter is incorect"?
DreamerNS,
The unused bytes in the 256MB file will probably be zeros, and should compress to just a few kb.
Back in the days when mp3 FTP sites were all the rage (before P2P) I used to take advantage of highly compressable data like that. Sometimes you'd get a site where you'd have to upload a certain amount of MP3s before you could download. All you'd have to do is create a huge black .BMP file and rename it .mp3. Thanks to dial up modems automatic compression, you could upload a 10MB "mp3" in seconds! Hehehe
-no1
Going back to the problem, is I: the correct drive letter for your card reader's SD slot?
-no1
Hi,
My Trinity's mini usb has packed up and I need to flash the original Orange rom (Which I have) from the sd card as the 'phone is under warrenty. I've formatted the card in fat32 and renamed the RUU_signed.nbh file to TRINIMG.nbh as per wikki, but I only get the bootloader screen, not the one shown on the wikki page.
Can anyone help me?
Thanks in advance to all the members of this fantastic forum!
eadon said:
Hi,
My Trinity's mini usb has packed up and I need to flash the original Orange rom (Which I have) from the sd card as the 'phone is under warrenty. I've formatted the card in fat32 and renamed the RUU_signed.nbh file to TRINIMG.nbh as per wikki, but I only get the bootloader screen, not the one shown on the wikki page.
Can anyone help me?
Thanks in advance to all the members of this fantastic forum!
Click to expand...
Click to collapse
Make sure your SD Card has no label!
tnyynt said:
Make sure your SD Card has no label!
Click to expand...
Click to collapse
Thanks for the reply.
As far as I know it hhas no label (Just called SD Card in explorer). How can I tell?
i've got the same problem.
SD card has no name (according to windows explorer), and is FAT32.
eadon said:
Thanks for the reply.
As far as I know it hhas no label (Just called SD Card in explorer). How can I tell?
Click to expand...
Click to collapse
Card reader... or WM5toarge
tnyynt said:
Card reader... or WM5toarge
Click to expand...
Click to collapse
Thanks tnyynt, I'm sorry but I've looked at the properties of the card using a card reader in vista and can see no referance to "Lables". I'd really apreciate it if you could spell it out for me.
Thanks so much
eadon said:
Thanks tnyynt, I'm sorry but I've looked at the properties of the card using a card reader in vista and can see no referance to "Lables". I'd really apreciate it if you could spell it out for me.
Thanks so much
Click to expand...
Click to collapse
right click, properties and if it is an empty box at the top it's good.
I'd recommend to save all your files to your PC and format the card to FAT32 in your card reader, then copy the TRINIMG.nbh to your card's root.
tnyynt said:
right click, properties and if it is an empty box at the top it's good.
I'd recommend to save all your files to your PC and format the card to FAT32 in your card reader, then copy the TRINIMG.nbh to your card's root.
Click to expand...
Click to collapse
Thanks again! Done all that, still only boot screen! Info on boot screen:
----------------
Trin100
IPL-0.50
Trin100 MFG
SPL-1.30.Olipro
-----------------
Do I have to worry about this?
"For normal (non preproduction) devices keep in mind that if the CID does not match the flashing will not work. The CID for each ROM is listed on the Trinity Upgrades page. You can see your device's CID using info 2 bootloader command or using GetDeviceData.exe"
Sorry for all this, but phone is F***ed if I cannot gett this sorted
eadon said:
Thanks again! Done all that, still only boot screen! Info on boot screen:
----------------
Trin100
IPL-0.50
Trin100 MFG
SPL-1.30.Olipro
-----------------
Do I have to worry about this?
"For normal (non preproduction) devices keep in mind that if the CID does not match the flashing will not work. The CID for each ROM is listed on the Trinity Upgrades page. You can see your device's CID using info 2 bootloader command or using GetDeviceData.exe"
Sorry for all this, but phone is F***ed if I cannot gett this sorted
Click to expand...
Click to collapse
Maybe it is a problem with the HardSPL. I see you have 1.30, I've heard people reporting some issues. I am using Des' Crash Proof and all is ok!
tnyynt said:
Maybe it is a problem with the HardSPL. I see you have 1.30, I've heard people reporting some issues. I am using Des' Crash Proof and all is ok!
Click to expand...
Click to collapse
I suppose that there is no way of flashing this from sd card if I can't flash anything else. Got a bad feeling!
No resulution yet
try this
copy Des Crash Proof Bootloader and TRINIMG.nbh to the SDCard.
On the phone use a file manager to get to the SDCard and run Des Crash Proof Bootloader.
The phone should restart and use Des instead of Olipro. The ROM should then update.
I've used the same process on my M700 without any problems.
Hope it helps
moodog101 said:
copy Des Crash Proof Bootloader and TRINIMG.nbh to the SDCard.
On the phone use a file manager to get to the SDCard and run Des Crash Proof Bootloader.
The phone should restart and use Des instead of Olipro. The ROM should then update.
I've used the same process on my M700 without any problems.
Hope it helps[/QUOTEThanks Moodog and tnyynt, I feel I'm getting somewhere. The only Des's Crashproof I can find is a zip file named "Crashproof.SPL.TRIN" with the actual file called "RUU_signed.nbh".
I cannot open this file in file explorer on my PPC.
Is there an executable version of Des's Crash Proof Bootloader?
This would solve all my problems.
Thanks again, I have scoured the forum for an answer.
Click to expand...
Click to collapse
eadon said:
moodog101 said:
copy Des Crash Proof Bootloader and TRINIMG.nbh to the SDCard.
On the phone use a file manager to get to the SDCard and run Des Crash Proof Bootloader.
The phone should restart and use Des instead of Olipro. The ROM should then update.
I've used the same process on my M700 without any problems.
Hope it helps[/QUOTEThanks Moodog and tnyynt, I feel I'm getting somewhere. The only Des's Crashproof I can find is a zip file named "Crashproof.SPL.TRIN" with the actual file called "RUU_signed.nbh".
I cannot open this file in file explorer on my PPC.
Is there an executable version of Des's Crash Proof Bootloader?
This would solve all my problems.
Thanks again, I have scoured the forum for an answer.
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=42938&d=1183561237
Click to expand...
Click to collapse
tnyynt said:
eadon said:
http://forum.xda-developers.com/attachment.php?attachmentid=42938&d=1183561237
Click to expand...
Click to collapse
I'm embarresed to keep asking, but...
I've put the contents of "Hard-SPL_ZakMcRofl" (Thanks tynnyt), with the "trinimg.nbh" file I want to use. First of all the "ROMUpdateUtility" will not execute in Windows Mobile. I can start "EnterBootloader", which takes me to the des bootloader screen, but no further, it does not initiate the "trinimg.nbh".
There's probably more wrong with the 'phone than I think, so I wait for the battery to drain, get a replacement from Orange and hope that they just bin it!
Thanks for all your help.
Click to expand...
Click to collapse
Just on the off chance, do you happen to be flashing from a SDHC card? I can't get mine to read NBH files always have to carry my 2GB whenever I want to flash a ROM.
Obviously not the only person that thinks so... here
0. Make sure phone is hard-spl first
1. Make sure SD card is formatted with fat-32
2. rename the image file (ruu_signed.nbh) to rhodimg.nbh, then copy that to the ROOT OF THE MICRO SD CARD, Insert card into phone
3. Set your phone in bootloader (Hold the "volume down" and hold the power on button until you see the tri-color screen.
4. Then follow the on-screen instruction
5. (OPTIONAL) -after flash, make sure to hardreset (pull battery, insert battery then hold green and red PHONE buttons (send/end) and hold powerbutton) follow onscreen instruction.
thanks for the info
I've tried the above and somehow it won't work on my TP2, it stays at "Serial" text in the white box, I'm assuming it already went past the SD slot then? Checking for the image.
I have the Energy rom loaded on the SD card, named as explained in the first post in this topic, it is placed in the root of the SD card, no folders or other files exist on that card. I removed the SIM card from the phone just to be sure. Is there anything I am missing, or is there anyone else who actually used this method to flash his or her device?
Info:
SPL: OliNex 0.85
ROM: |RHOD|6.5|ROM|WWE| ★ EnergyROM "Warhawk" (23016) ★ | Built Aug 21 |Manila 2.5 / 2.1|
SD Card: 4GB MicroSDHC (No brand on card, supplied with the branded T-Mo TP2 (Vario V)
Formatted: fat-32
Thanks
The nbh file needs to be in capital letters! RHODIMG.nbh
And step 5 isnt to be done until the "Tap screen to set up device" screen!
Just reset when your phone says Update successful!
And done, name changed to the correct format. No luck. Reformatting the card now to see if that changes anything. Update in a few.
And that too didn't work sadly. Either someone here notices I'm doing something wrong, or I'll just wait till I get near a machine natively running Windows Running Mac OS here so can't run the executable, and read that it's not quite a good idea to flash it from a virtual OS.
PositiveCreep said:
And done, name changed to the correct format. No luck. Reformatting the card now to see if that changes anything. Update in a few.
And that too didn't work sadly. Either someone here notices I'm doing something wrong, or I'll just wait till I get near a machine natively running Windows Running Mac OS here so can't run the executable, and read that it's not quite a good idea to flash it from a virtual OS.
Click to expand...
Click to collapse
You will want to partition your card so the nbh image is in a partion of at the largest 1G, anything larger makes it hard for the phone to find and read the nbh file! I have a 1G card just for flashing and it works perfect! And it also may be the mac, they never play nice with windows!
It's not the mac screwing it up in this case as I am using a virtual Windows OS to work on the card. (MacOS leaves some folders on the card that I don't want on it)
Will try partitioning the card, cheers. I'll update when I know more. ANd thanks for the help ^_^
Update:
Partioned the MicroSD card to 0.5GB, no change sadly.
thanks for information
Ok, SD update worked now, however, step 5 won't go (Oh crap...) Have the grey screen with "Update Complete" and "UPDATE SUCCESS" However, it won't do anything if I hold down Send/End/Power at the same time for over 10 seconds. How long should that take normally? What's my best option right now? Can't see any other than to unplug the phone and take out the battary, however, will this brick it?
PositiveCreep said:
Ok, SD update worked now, however, step 5 won't go (Oh crap...) Have the grey screen with "Update Complete" and "UPDATE SUCCESS" However, it won't do anything if I hold down Send/End/Power at the same time for over 10 seconds. How long should that take normally? What's my best option right now? Can't see any other than to unplug the phone and take out the battary, however, will this brick it?
Click to expand...
Click to collapse
When is says "UPDATE SUCCESS", just rest with the stylus.
Dave
Thanks for the swift reply! Done it, it's booting up as I am typing this. Didn't quite have the guts to just do that without having read I could when flashing from SD. (Was unsure how the device would react to soft reset then a first booth with the SD present etc)
Anyways, rambling. Thanks!
these post are telling me how to flash while the rom is already on the phone, but i'm missing the step on how to get the rom file on the phone in order to move it to the sd card.......... how do i get the file to the phone? do i put it onto the phone from the computer or do i go to my browser on my phone and download it from there to the phone
htctpII said:
these post are telling me how to flash while the rom is already on the phone, but i'm missing the step on how to get the rom file on the phone in order to move it to the sd card.......... how do i get the file to the phone? do i put it onto the phone from the computer or do i go to my browser on my phone and download it from there to the phone
Click to expand...
Click to collapse
Everything you need to know is HERE. I really suggest you fully read the instructions so you avoid bricking your phone by mistake.
In re: making sure you're hardspl'd first, does that still apply if you're flashing an official ROM? Or just for user cooked ROMs?
I'm about to update my Verizon TP2 with the newly released official 6.5 from verizon. I'm not hard spl'd, and honestly, know very little about that particular modification.
not for official
I dont think you have to be hard SPL'd for an official ROM. I think everything is included in the ROM package. (at least for T-Mobile it is)
btw the .nbh does not have to be named in all capitals. I have personally done it both ways with no problems at all. RHODIMG.nbh works just as well as rhodimg.nbh
kwambewright said:
I dont think you have to be hard SPL'd for an official ROM. I think everything is included in the ROM package. (at least for T-Mobile it is)
Click to expand...
Click to collapse
Thanks for the quick response!
Sadly, the way the install file is set up to work, I can't get to the nbh file. It insists on installing that via an active sync connection. I was hoping it would extract from the exe and schedule it for active sync installation, then I could hunt down the ROM, copy it to my SD card, and run it from there.
fortunz said:
Thanks for the quick response!
Sadly, the way the install file is set up to work, I can't get to the nbh file. It insists on installing that via an active sync connection. I was hoping it would extract from the exe and schedule it for active sync installation, then I could hunt down the ROM, copy it to my SD card, and run it from there.
Click to expand...
Click to collapse
hmm.. sorry for kicking this post, but you can unpack the exe-file with winrar. just grab the biggest file you can find (RUU_signed.nbh, and rename it to rhodimg.nbh), copy it to your root-folder (fast way for accessing bootloader is to also copy the "EnterBootLoader.exe" -file to your SD-card, and to start that file after copying both the files). Now just enter the bootloader, and it works! (don't be scared when the screen goes black for a moment, and the bootloader has reloaded. It's meant to do that )
I still have a little question by the way: is it possible to flash the hardSPL this way? or should i rename it to something else?
No, Hard SPL needs to be done from the PC as it checks IMEI online and IP address. You only get 1 licence, can ask for more or purchase more licences, but it can't be done any other way...
ultramag69 said:
No, Hard SPL needs to be done from the PC as it checks IMEI online and IP address. You only get 1 licence, can ask for more or purchase more licences, but it can't be done any other way...
Click to expand...
Click to collapse
Yeah, it's a pity this has been done (though I understand why...)
My device cannot connect to PC anymore, so cannot use HSPL anymore!
InjecTioN said:
hmm.. sorry for kicking this post, but you can unpack the exe-file with winrar. just grab the biggest file you can find (RUU_signed.nbh, and rename it to rhodimg.nbh), copy it to your root-folder (fast way for accessing bootloader is to also copy the "EnterBootLoader.exe" -file to your SD-card, and to start that file after copying both the files). Now just enter the bootloader, and it works! (don't be scared when the screen goes black for a moment, and the bootloader has reloaded. It's meant to do that )
Click to expand...
Click to collapse
Much obliged. I've actually been scared off the official vzw 6.5 because of issues upgraders have reported, but someday I'll put that to use.
How to update rom for my tilt with macbook pro....i have had tilt for long time and didnt use it for sometime.i have installed 6.1 n wanted to update the latest rom. Responses r appreciated.
Parallels or VM fusion
I dont know of any RUU's written ofr Mac, so I believe you're going to have to boot into windws somehow.
EDIT: You could also update via the SD card. Go to the Kaiser Wiki, and the ROM development forum for details.
Good Luck
spbluffmaster said:
How to update rom for my tilt with macbook pro....i have had tilt for long time and didnt use it for sometime.i have installed 6.1 n wanted to update the latest rom. Responses r appreciated.
Click to expand...
Click to collapse
There is no way to update using OSX. I have all Macs and I flash my Tilt with my Intel iMac by booting into Windows XP using Bootcamp.
I don't believe you can flash " official roms " with the SD card method, but I could be wrong.
denco7 said:
There is no way to update using OSX. I have all Macs and I flash my Tilt with my Intel iMac by booting into Windows XP using Bootcamp.
I don't believe you can flash " official roms " with the SD card method, but I could be wrong.
Click to expand...
Click to collapse
You can download the HTC stock ROM, extract it using any UnRAR program for OS X (a google search will yield plenty of results) and after doing that, rename the extracted file called RUU_Signed.nbh to KAISIMG.nbh. Then, you can move KAISIMG.nbh to your MicroSD card using a card reader, and put that back in your device. Hold the Camera and Power Button at the same time while the device is off to load the bootloader, and if you did everything right, you should be able to follow the instructions from there.
Check out the WIKI page for more info:
http://wiki.xda-developers.com/index.php?pagename=KaiserSDFlash
Credit goes to DaveTheTytnIIGuy for the tip!
krouth said:
You can download the HTC stock ROM, extract it using any UnRAR program for OS X (a google search will yield plenty of results) and after doing that, rename the extracted file called RUU_Signed.nbh to KAISIMG.nbh. Then, you can move KAISIMG.nbh to your MicroSD card using a card reader, and put that back in your device. Hold the Camera and Power Button at the same time while the device is off to load the bootloader, and if you did everything right, you should be able to follow the instructions from there.
Check out the WIKI page for more info:
http://wiki.xda-developers.com/index.php?pagename=KaiserSDFlash
Credit goes to DaveTheTytnIIGuy for the tip!
Click to expand...
Click to collapse
That is the SD card method, but again, if you don't already have Hardspl on your phone ( and you have to do that with a PC ) you can't use the SD card method. And you can't flash a stock rom either using the SD card method either unless you use Hardspl first .
I think the OP was asking to do a normal Kaiser rom update with a Mac.
thnx guys
thnx you for ur responses ppl ....
I have created this post because I was honestly baffled by the NAND install threads for the Vogue that I found, that claimed to be "straightforward" and simple, but the people who wrote them leave a lot of gaps that you have to figure out. Perhaps they have been doing it for so long now, that they just 'assume' you will know stuff, so here are step-by-step instructions for someone who has zero experience with Android, and all they know is that they have a Window mobile phone.
So, Here is the NAND install process (will install Android to your internal memory, which is much better than running from the SD card) for the HTC Vogue (240x320), CDMA or GSM. I believe this is the most straightforward tutorial on this entire site, and all files you need are provided in this post; no file-hunting necessary like with other tutorials. Keep in mind, this process will wipe your internal memory and replace it with Android, so you should backup any personal files you have stored on the phone. If you have a CDMA phone (Verizon, Sprint, etc.) then you should make sure to backup your Contacts using a 3rd party program. GSM phones however (ATT, T-Mobile, etc.), typically store their contacts to a SIM card, which is not altered by this process. You do not need to backup your SD card, since it is also not altered when installing Android.
Dependencies: This process works for any ROM release that provides an "androidinstall.tar" file in their download package.
First and foremost, make sure you have unlocked your phone ("2.31 CoKe" HardSPL for CDMA Vogues). If you have ever flashed a custom Windows ROM from this site or ppcgeeks.com, to your device, then you most likely already have an unlocked phone. If not, perform the steps HERE first, before continuing AND flash to a custom Windows Mobile ROM (non-stock) and make sure your phone is provisioned (you can get and receive calls), and that you can use data (if you have a data plan).
1. Wipe your SD card, and make sure it is formatted FAT32
2. Create a new folder in the root of the SD card called "andboot"
3. Download the ROM release package of your choice (for example, you can download the 240x320 version of Myn’s Warm Donut - [RLS 5 - 04/24/2010] HERE)
4. Extract files from STEP 3 and put ONLY the "androidinstall.tar" file in the andboot folder on the SD card, by itself (no other files are needed)
5. You are DONE putting files on your SD card. At this point, put the SD card into your phone.
6. Download the latest NBH file that begins with "voguimg-240x320-..." (needed for all Vogue Android ROMs): HERE
7. Download the RUU Update Utility (needed for all Vogue Android ROMs): HERE
8. Rename the NBH file to from STEP 6 to "RUU_signed.nbh" and place it inside the folder with all the other files from STEP 7
9. Now, put your Vogue in bootloader mode: Hold down power, camera, and the small reset hole (with your stylus), until you see the tri-color screen, and it says "Serial" at the bottom
10. Plug your phone into your computer, and the "Serial" text should change the "USB"
11. Now, run the "ROMUpdateUtility.exe" from STEP 7, and click the "Next" or "OK" buttons to go through the flash/ROM update process, until your phone shows a progress bar on its screen and is updating.
12. As soon as that progress bar finishes the phone will automatically reboot; at this point unplug the phone from the computer
13. Now, watch carefully during the Linux boot process...there will be a quick message that says "Hold down Volume Up or D Pad". Just press and hold the center D-Pad button until you see the screen change to the installer menu. If you happen to miss it, and it continues loading, then just use your stylus to press the reset button (it will not hurt the phone or any files to try again as many times as you need to.)
14. You will now see a black and white menu. Select option 1, to "Install..."
15. Select "Yes" on the recommended prompt that follows
16. Once it says the Install process is complete and it returns you to the menu, just reboot your phone with the reset button
17. At this point just WAIT. Do NOT press the volume up button again, and do not do anything until you see the Android desktop. You may get an error saying that it could not find a file or something like that, but just ignore it...do not get impatient! Pretty soon the Android progress bar will show on the screen (might take up to 5 minutes), then the Android desktop will load.
DONE. Enjoy Android on your Vogue! You can now delete all the files on the SD card if you wish...Android will recreate anything it needs on boot-up each time.
MASS STORAGE FIX (USB to PC): You can get the Mass Storage fix HERE so that your storage card will show up as a drive on your computer. This is a widget, and not ROM specific, so should work for any Android ROM.
KAISER WI-FI FIX (for the Kaiser phone ONLY!): Download the Wi-Fi fix HERE (intended for use with 'myn's Warm Eclair RLS1', linked in STEP 3)
I do not ask for donations, just say 'Thanks' if this helped you.
***
UPDATE: This Thread is now featured on Wired.com's News Site!! Link: http://www.wired.com/gadgetlab/2010/04/windows-mobile-android/
***
please elaborate on step 8. what are we extracting here
Great post. Just some clarifications I thought would be helpful.
1. reminder to all - you can use SDHC cards for this, those being greater than 2gb, but make sure you format them to FAT32.
5. in some instances there are androidupdate.tar files that go with the build too, in which case that too needs to be placed in the same andboot folder
8. clarification, you'll be replacing the RUU_signed.nbh file with the 320 nbh file you download. So, you'll have to delete the ruu_signed.nbh that came with the update utility, and rename your downloaded 320 nbh to ruu_signed.nbh and place it in the update utility folder so it uses that file instead.
9. to enter bootloader mode you have to press those 3 buttons down for about 2 seconds, not just a quick tap. This bootloader is your failsafe fallback to reinstall if your operating system goes funky.
13. If volume up isn't working for you, try holding down the button in the middle of the directional pad. The last nbh file I used required this instead of the awkward volume-up. Regardless, be sure to do this quickly as soon as the phone reboots itself.
16. After the install process is complete you'll be brought back to the same menu you arrived at by holding down the button on startup, you may then select "update" or "upgrade" from that same menu to activate the androidupdate.tar file you may have copied to your andboot folder. Once done, just select "exit" or reset.
17. He's not kidding, first boot can take a very long time.
If you run into problems and just need a functional phone for a bit, download the nfsfan rom (or any other custom roms), put phone into bootloader and run the nfsfan rom utility from your windows desktop. Don't reinstall a locked carrier-specific rom that you might have used to update your radios otherwise I understand your Coke bootloader gets wiped out and you'll have to do that again. Alternatively, there is an older, dummy-proof Android ION build that will install the entire ION build through the rom update utility to your nand at http://sourceforge.net/projects/androidhtc/files/2009-12-17/androidinstall.zip/download
I'm no super-expert so if I have any misinformation in my post, or there are other shortcuts, please feel free to edit it or let me know and i'll modify it.
MikeMurphy said:
Great post. Just some clarifications.
8. clarification, you'll be replacing the RUU_signed.nbh file with the 320 nbh file you download. So, you'll have to delete the ruu_signed.nbh that came with the update utility, and rename your downloaded 320 nbh to ruu_signed.nbh and place it in the update utility folder so it uses that file instead.
Click to expand...
Click to collapse
where is this file?
CasopoliS said:
where is this file?
Click to expand...
Click to collapse
You're looking for the vogue 320 files, not the vogue eclair 320 files unless you're installing an eclair (2.x) build.
The .nbh files are usually referenced on the build thread in the forums, but if they are not head over to http://sourceforge.net/projects/androidhtc/files/ and download the latest.
(NOTE: I suggest you run at least the Feb 23 build at http://it029000.massey.ac.nz/vogue/files/?C=M;O=D as it enables the openGL support)
MikeMurphy said:
You're looking for the vogue 320 files, not the vogue eclair 320 files unless you're installing an eclair (2.x) build.
The .nbh files are usually referenced on the build thread in the forums, but if they are not head over to http://sourceforge.net/projects/androidhtc/files/ and download the latest.
Click to expand...
Click to collapse
the latest isnt there its here
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
now now, gents, you're both right - dzo's latest are in one spot, vilord's latest are in the other, and they don't always contain everything the other does. vilord mentioned trying to get them in one spot but I don't know if there's been any progress on that.
it keeps hanging up at the progress bar and both stay at 0% it looks like the active sync is gone once in bootloader it goes gray and then its gone from tray in bottom right corner. it seems like once in bootloader mode i have no active sync connection it just hangs Then the updater goes into its recovery any help please
razorr69 said:
it keeps hanging up at the progress bar and both stay at 0% it looks like the active sync is gone once in bootloader it goes gray and then its gone from tray in bottom right corner. it seems like once in bootloader mode i have no active sync connection it just hangs Then the updater goes into its recovery any help please
Click to expand...
Click to collapse
go into bootloader before plugging your phone in by pressing and holding power button, camera button, and then use stylus to hit reset button.
once you get into bootloader, plug your phone in and then run the rom update
incubus26jc said:
go into bootloader before plugging your phone in by pressing and holding power button, camera button, and then use stylus to hit reset button.
once you get into bootloader, plug your phone in and then run the rom update
Click to expand...
Click to collapse
that is the way that i have been doing it as per the instructions, Any other suggestions? I just did a hard reset and restored the phone to out of the box if that helps out any.
thanks
razorr69 said:
that is the way that i have been doing it as per the instructions, Any other suggestions?
thanks
Click to expand...
Click to collapse
the only reason i said that is because active sync should have nothing to do with it. i dont think active sync should come up or shut down during this process. Do you have the RUU_signed.nbh named properly?
razorr69 said:
that is the way that i have been doing it as per the instructions, Any other suggestions?
thanks
Click to expand...
Click to collapse
Activesync has nothing to do with updates via the rainbow screen bootloader and will not sync.
You have already install the Coke bootloader? What OS are you running?
Thank you so much. Been needing something like this since the other NAND tutorials for Android didn't tell you what files to use or had outdated/non-working links.
MikeMurphy said:
Activesync has nothing to do with updates via the rainbow screen bootloader and will not sync.
You have already install the Coke bootloader? What OS are you running?
Click to expand...
Click to collapse
6.1. I followed the inst.
put the tar in andboot folder on sd
renamed the voug img file put it in the androidinstall folder on my desktop
put the rest of the files from myns donut into the androidinstall folder
then bootloader plug in usb then rom updater
everything goes fine intil it hangs on the progress bar at 0%
razorr69 said:
6.1. I followed the inst.
put the tar in andboot folder on sd
renamed the voug img file put it in the androidinstall folder on my desktop
put the rest of the files from myns donut into the androidinstall folder
then bootloader plug in usb then rom updater
everything goes fine intil it hangs on the progress bar at 0%
Click to expand...
Click to collapse
What OS are you running on your computer?
The ROM update utility really just installs the .nbh file which is somewhat of a front-end loader mechanism. Once that file is installed, then the phone resets, you hold down a button and you enter into the menu that lets you actually install android from the androidinstall.tar file in your andboot folder.
Here is a fail-proof method that I think will resolve your goofy androidinstall folder.
Download this
http://74.53.45.2/~evadmin/nfsfan/Public Releases/Vogue 6.5/ROMS/NFSFAN's WM6.5 1.00 FINAL ROM.rar
Then replace the .nbh file with the vogue 320 nbh. Then, run it when your phone is already in the bootloader screen.
Excellent post
I'm linking this from Warm Donut on the first post.
MikeMurphy said:
What OS are you running on your computer?
The ROM update utility really just installs the .nbh file which is somewhat of a front-end loader mechanism. Once that file is installed, then the phone resets, you hold down a button and you enter into the menu that lets you actually install android from the androidinstall.tar file in your andboot folder.
Here is a fail-proof method that I think will resolve your goofy androidinstall folder.
Download this
http://74.53.45.2/~evadmin/nfsfan/Public Releases/Vogue 6.5/ROMS/NFSFAN's WM6.5 1.00 FINAL ROM.rar
Then replace the .nbh file with the vogue 320 nbh. Then, run it when your phone is already in the bootloader screen.
Click to expand...
Click to collapse
Thank you will try it now. Running xp pro on my desktop
razorr69 said:
Thank you will try it now. Running xp pro on my desktop
Click to expand...
Click to collapse
XP Pro always worked well for me. I'm running Win7 x64 ultimate and recently my phone was recognized as a USB Sync Device in the bootloader mode which doesn't work for the rom update utility. This was occurring both with and without the installation of the MS Mobile Device Center app. To solve this I installed XP Mode and attached the usb device to the XP Mode and it recognized correctly as the Qualcomm MSM thing.
Just an FYI.
MikeMurphy said:
XP Pro always worked well for me. I'm running Win7 x64 ultimate and recently my phone was recognized as a USB Sync Device in the bootloader mode which doesn't work for the rom update utility. This was occurring both with and without the installation of the MS Mobile Device Center app. To solve this I installed XP Mode and attached the usb device to the XP Mode and it recognized correctly as the Qualcomm MSM thing.
Just an FYI.
Click to expand...
Click to collapse
when i go into my computer it just says mobile device
razorr69 said:
when i go into my computer it just says mobile device
Click to expand...
Click to collapse
same result error 262 update error. i dont get it this is so simple. 1 of the 4 steps is establish a connection with active sync dont know how to do that once im in bootloader mode it's like there is no connection but the phone shows the progress bar