Develop Bugs

Would like to upgrade ROM but . . .

Hi all,
let me start telling that reading through this frum gives me the feeling that this is a very nice place for information around htc-devices and I thank both creators and users of this site for such a good information-base.
Reading here convinces me that I am able to fulfill my wish to change the language of my VPA-IV (HTC Universal).
I am a Dutch person working in Russia. As I was living in Germany I optained the device there, hence the German language.
For me personally all computer stuff should be English, so I'd also like this device to be so. The fact that the keyboard is German does not disturb me too much.
As a Vodafone user, who has other provider cards as well, I immediately bought the unlock code, so the device is working with other GSM cards as well.
When I asked Vodafone (before I bought the device) if I could switch to English I was told that I should buy myself another Windows Software and they were not able to provide me with it. They were not able to provide any help, nor software for this purpose though.
When reading around the site here (as well as the ftp) I understood that Windows is not provided now. So my first question would be :
-Am I really set to go if I have downloaded the following files :
Jasjar_WWW_11353_137_10301.zip
MaUpgradeUt_noID.zip
Universal_Radinly_UPgrade_1.04.02.zip
Or do I need something more ?
Further I read about extracting the .exe file (f.e. Jasjar_WWW_11353_137_10301.exe) and put some files from there at certain places. I have WinRar but this program does not recognize the .exe file. Can I really extract files from this .exe ? How do I do this.
A lot of talking is here about a bootloader. If the device is in this stage, can I still access it ? (f.e. like seeing a harddrive in my PC's Windows Explorer or something the like)
As I will be stressed like hell (who does not, when he does this first time) when I see the bootloader screen, is there something I SHOULD or should NOT do to make sure all will be OK ?
Last but certainly not least I feel very eager to backup before I do this. Is there a posibility to backup my ROM in some way, save the files on some place for eventual return to the ROM and ExtRom I have now ?
I tried the Program TotalCommander. If I enter the Extended_Rom in the "directory" field of this program I see all files included in the Extended_Rom, same if I enter simply "Rom". Is a backup simply copying these files to my PC or is there more to be done ?
thanks for answering in advance,
Ruud

Hi,
I'm searching a german ROM...
if you have a little of your time to spend on it, i would be very thankful.
but first:
- about extracting the .exe files: Run WinRAR -> Menue: Open file... -> change 'All archives' to 'All files'
- about ROMs: Jasjar_WWW_11353_137_10301.zip is the only rom I would update, not the Radio.
- about bootloader: In this state you can't access your device (only updating the ROM)
- about backup: It is not easy. (How to d2s (dump) the ROM ) but I think Vodafone will shortly relase a update. So it will be possible to restor the device.
How to help me out:
- you will need a Storage Card.
- Download TestWM5.rar
1. Extract TestWM5.exe from TestWM5.rar and place it to you device.
2. At the device, use File Explorer to execute the TestWM5.exe
3. Click "button1" to start the dump process, the file will then be save to \Storage Card\Dump\
4. Copy the Dump folder out and then RAR or Zip it
This will include all files in your windows dictionary -> this is what i need

Where to place exactly ?
Hi bepe,
do not know if You are still available (or again). First your issue.
I logon to FTP from XDA-developers as to upload.
In the upload directory there is only a HTC-Wizard directory, not a wizard. Is this directory the one to place your file on ?
Is there a rule how to name the file ?
I will be dumping in a minute, can upload as soon as I have your answer.
Ruud

Hi bepe,
further to your issue.
1) I do understand that no private information is copied ? or should I do a hard reset before I dump for You ?
2) Whilst running your testwm5.exe from the root-directory of the storage-card I am being asked to agree your program access. This is normal, I allow. But why are there additional programs being opened I never heard about ? I denied them access and let the program run further !
After a lot of files running through the screen (very fast) it looks like the program stopped or finished. Now which file has been created for You ?
Explorer on the Universal does not show it, through my PC I looked as well, but do not see any big file, please explain.
Ruud

Hi Bepe,
one more reply to You :
Even if I allow the file mentioned to run (during the time your program is running), I am being asked again and again if I allow it again. The name is GAC_System.Data_v1_0_5000_0_cneutral_1.dll
Even if allow access all of the occasions I being asked, no file is being created on my storage-card, nothing to dump to You. Not even the dump directory is made.
What do I do wrong here ?
To my issue :
First I noticed that the radio update is available here only as 1.04.02
My system tells me I have 1.04.10 delivered from origin. If I do a ROM-upgrade, do I loose my "radio", or will it not be touched ?
Connected to this, can I dump my "radio"-files seperately ?
WinRAR. Issue solved !
Backup : I was at the buzzdev.net link before. But I actually do not even understand where I can get or see the task32 language he dumped on his screen. And I understand that I will not be able to restore it without help anyway. So this is not really the kind of backup I want.
The information about Vodafone, where does it come from ? when is something expected ?
Ruud

For security sake only.
I am getting nearer to make that final step ;-)
My Winrar was too old, I could unzip the .zip file to a .exex, but I could not unzip the .exe file further. Just downloaded the latest Winrar, now I can see all files included in the provided .exe file.
1) I understood that I should delete the original upgrade-file called ROMUpgradeUt.exe.
2) When I start the MaUpgradeUt_noID.exe in a seperate directory with the rest of the files from the .exe I get to see a different HTC device. When I continue, it will not recognize any of the versions from my Universal. I felt unconfortable to continue.
Can it be done without a problem ??
2a) I renamed the ms_.nbf AND radio_.nbf and restart the Utility, it still shows a photo of the wrong device, but it now does recognize the versions of Device CD image version : 1.13.56 Device Extended image version : 1.13.163 and Device Radio image version : 1.04.10
It confirms to change to CD image version 1.13.53 and leaves the extended image version : "empty" as well as the Radio image version : "empty"
Does this mean that by taking away the ms_.nbf and radio_.nbf files I can stop the device from upgrading the extended rom and the radio ?
Why I ask ? Because if I renamed ms_.nbf back and ONLY radio_.nbf is unavailable now, it shows to change the Extended Rom too, but the Radio image is still empty.
Finally if I rename ALL back, it shows to change all, but all version numbers are older once ;-(
Main question here is, can I leave radio_.nbf away, upgrade and hope for radio to be my version 1.04.10 ?
Ruud

Hi,
I'm back.
I'll PM you Upload information...

private information are not copied.
Only if you have saved private information in your /windows/ folder!
i have never being asked to agree for program access :?
...but I started it of the root-directory of my device.
what is the name of your 'Storage Card' folder?

I not realy have the info from Vodafone, but for all devices before there have been more than one update. But I can't tell when the first update is expected.
If you are trying to make a backup: you will need a terminal program

About dumping
So I have a complete "new" device now.
Did a hard-reset, after which I did not give any new information to the device.
I placed the .exe file You gave me in the \windows\startmenue before, after which it is asking tonloads of access requests.
Now I replaced it in the root-directorym Yes, no additional questions asked anymore, perfect, well NO. As there is no directory made on the storage card. I tried it once with the async active and once with the device seperate. No result.
Any ideas ?

what is the name of your 'Storage Card' folder in your root?

As the device is German, it is called "Speicherkarte"
and renaming is not possible (allowed)

OK this is the problem, I'm trying to get the Source code to change that.

found something: this tool will change the folder name from different languages to "Storage card" which is often needed for different tools

Understood.
About my question, as I am still nervously waiting (cannot start the upgrade before You got your data, can I ;-)
Did I understand correctly, that the file MaUpgradeUt_noID.exe is made for different devices from HTC and therefore I do not get a photo of the universal when I start the software ?
If I start the JASJAR_WWE_11353_137_10301.exe I DO get to see the Universal, but of course get the country error.
Did I also correctly understood I can take away the radio_.nbf from the directory and the update will handle both ROM and ExtROM but leave the Radio untouched ?
Will I be entering this "bootloader" status at all, as I do not need any further updates then ? Are there any resets after the upgrade which I SHOULD or SHOULD NOT make to get the device working again ?
Ruud

Hi bebe,
storage.cab works (be it only after a soft-reset)
The program testwm5.exe is much slower now, so the result is taking minutes now (if not tens of).
Looks like the perfect speed of the program while the storage card (at least for his eyes) was absent, was due to "saving into space"
Will upload asap.
Ruud

I'm loading JASJAR_WWE_11353_137_10301.exe its at 60%
MaUpgradeUt_noID.exe is a hacked version, of another device.
So the photo should not be important. (Please wait until i have downladed the file, I'm not realy sure jet...)

OK, I have to wait anyway, because TestWM5 is very slow now, I can see file after file and calmly read it. Before it was running before my eyes. I am afraid this is going to take ages.
We are on the same frequency that the dump I am making is from a device WITH Extended Rom installed. I was NOT soft-resetting during installation, so all Vodafone add-ons, are to be there now.
If You need the one without ExtRom as well, please tell me.
The upload works OK, I prepared a directory there, but uploading is to be done after longer waiting time.
Are You afraid the JASJAR file is not good ? I downloaded it because this one was proposed on this forum.
Ruud

Its not about the ROM its about the MaUpgradeUt_noID.exe I'm not sure if ths is the exe file to update a Universal.
I dont have a Universal only a Himalaya and my up UpgradeUt starts with HimUpgradeUt... .
Was this file mentioned in the readme of the JASJAR exe?
my download is very slow... 70%

I only downloaded MaUpgradeUt_noID.exe because it was proposed here (for the Universal).
I have no Readme.txt inside the exe
EnterBL.exe
GetDeviceData.exe
ms_.nbf
nk.nbf
radio_.nbf
RUU.conf
RUU.dll
UI.dll
Well and of course the original upgrade file ROMUpgadeUt.exe, but I was suppose to delete it.
Only file which I can read is RUU.conf :
[PLATFORM]=857873
[RADIO_TYPE]=2
[SECURITY_FLAG]=1
[DECODER_KEY]=1
[RADIO_FLAG]=2
[GETADDR_TYPE]=1
[JUMPCODE_TYPE]=1
[FORMAT_TYPE]=2
[SCREEN_TYPE]=2
OK, TestWM5 is finally ready, will do compressing and uploading soon.
Ruud

ASUS P525 ROM Tool - Cooking your own ROMs

The attached utility will allow to extract .NB0 OS image from ASUS P525 "galaxy.cap" complete rom update packages, and also to update CRC on modified NB0 ROM image, to pass the flasher validity check and flash the modified ROM. Also it will allow to unpack compressed kernel partition.
The application dynamically linked to Visual C runtime libraries. They used by myriads of applications, and most likely you already have them on your system installed. If you are not (on a clean PC for example) and P525ROMTool complains about lack of needed libraries,- download and install this - http://www.microsoft.com/downloads/details.aspx?familyid=32BC1BEE-A3F9-4C13-9C99-220B62A191EE
For you technical people, the utility source is included too. You can see the basic layout, and that ASUS used Adler32 algorithm to calculate the checksum on ROMs (with slight modification that base sum was initialized to zero instead of one).
The basic procedure for cooking your own custom P525 rom is:
1) P525ROMTool -d galaxy.cap
This will extract the ROMGalaxy.NB0 OS-only image. For custom ROMs I recommend working with NB0 OS images only - no danger of corrupting bootloader & IPL this way.
2) prepare_imgfs ROMGalaxy.NB0 -nosplit
3) DelFile / AddFile
Iam not sure if you can truly fully rebuild the ROM and not to break anything (ROM tools were made for HTC platform, not for ASUS). So I recommend using DelFile/AddFile method at least for the start.
There are a lot of different ROM editing tools around, but I can not give you exact directions what is better and in which conditions - ASUS ROM cooking is less charted area then for HTCs.
I assume you know what you actually need to change on file basis for your ROM customization. If you dont know what I am talking about, this is not for you (read disclaimer at the end of the post, and think over it).
4) make_imgfs ROMGalaxy.NB0 -nosplit
5) P525ROMTool -s ROMGalaxy.NB0
it will ask about changed checksum. Enter "y" to update it. You can run P525"ROMTool -s ROMGalaxy.NB0" again to be sure that checksum was updated properly - it should'nt ask to change it second time.
6) Flash ROMGalaxy.NB0 via bootloader (copy it to SD card root, press "camera" fully, press reset).
Techincally, you can make the .cap file to flash via "autorun" loader, hovewer, I must warn you that .cap file will flash not only OS image, but also the IPL+bootloader. If something goes wrong, bootloader can be corrupted and device will be bricked.
If you flash ROMGalaxy.NB0, it will not flash over bootloader+IPL, so its a lot safer - if something goes wrong, you still must be able to flash emergency rom via bootloader.
Take note that any activity that involves the ROM updating is dangerous. Even if you understand everything, there is some risk. If you have only basic understanding of ROM mechanics, risk increases tenfold - you better consider before screwing up perfectly working and expensive device.
You have been warned.

Ingvarr, thanks a million time. I love yr WM5 Storage and I think I will love this tool also. I will start building my rom based on Sorg's build 6 since it does provide some very useful tools for us.

Ingvarr thank you for your cool tools.
But when I DIY my ROM, I can't make make_imgfs.exe work correctly. It returns some symbols I can't understand.
Even I run make_imgfs.exe just after finish running prepare_imgfs.exe, it returns the err.
Could you help me with this?

make_imgfs ROMGalaxy.NB0 -nosplit
NOT "nk.nba"
It writes the modified filesystem back in the original image, so it should remain the same. You dont want to mix the ASUS and HTC ROMs and then flash it to your device, trust me
I recommend you to read HTC ROM Tools instructions and forum threads and be sure you've got right how it works, before you screw something up

sir,
Bad news，it can't work with CHS ROM （ROMgalaxy.nb0） checksum error！～～～

Does it correctly verify the checksum on original ROM?
I will try to look over it, maybe I've missed something.
Btw, if you can, write down what does writes on screen _exactly_, down to the point of failure (including error message).

Ingvarr said:
Does it correctly verify the checksum on original ROM?
I will try to look over it, maybe I've missed something.
Btw, if you can, write down what does writes on screen _exactly_, down to the point of failure (including error message).
Click to expand...
Click to collapse
i have tried it too.
i updated the checksum in sorgs rom, and then i found, that the checksum from ur SW is diffrent with the original Checksum in sorgs ROM

harlemyin said:
i have tried it too.
i updated the checksum in sorgs rom, and then i found, that the checksum from ur SW is diffrent with the original Checksum in sorgs ROM
Click to expand...
Click to collapse
You mean, it claims that checksum is wrong even when you have not modified NB0 yet?
I may look over this NB0, can you host it somewhere? But better not at rapidshare, Iam already topped my limit

Ingvarr said:
You mean, it claims that checksum is wrong even when you have not modified NB0 yet?
I may look over this NB0, can you host it somewhere? But better not at rapidshare, Iam already topped my limit
Click to expand...
Click to collapse
yes
and it happens by official P525_V3320_WWE2nd too
checksum in official P525_V3320_WWE2nd is 79AB7436
ur SW changed it to EF722461----not modified NB0
u can download official P525_V3320_WWE2nd with www.asus.com or
ftp://dlsvr02.asus.com/pub/ASUS/IA/P525/P525_V3320_WWE2nd.zip

Thats odd, because I've just checked it with WWE 3.32 and at least checksum calculation defenitely works ok...
This roms are in .CAP package. Have you actually extracted .NB0 from .CAP?
I have uploaded version 1.01 - it has additional sanity checks to make sure that you try to run it on NB0 with structure it expects.
Try it on WWE 3.32 and write what the original checksum and calculated checksums will be.

sorry
our mistake
i tested ur SW with a *.nb0, which extracted with xda3nbftool.exe------*.nb0 with ipl and bootloader.
and now i find, that *.nb0 should be and must be extracted with ur P525ROMTool -d galaxy.cap,------that means *.nb0 without ipl and bootloader
everything is fine, when *.nb0 is extracted with ur P525ROMTool
i think creazy2000 just made the same mistake like me.

o
thanks a lot.

Thanks. The tool works perfectly on my P525.

Ingvarr said:
Thats odd, because I've just checked it with WWE 3.32 and at least checksum calculation defenitely works ok...
This roms are in .CAP package. Have you actually extracted .NB0 from .CAP?
I have uploaded version 1.01 - it has additional sanity checks to make sure that you try to run it on NB0 with structure it expects.
Try it on WWE 3.32 and write what the original checksum and calculated checksums will be.
Click to expand...
Click to collapse
I make a mistake, thanks!

harlemyin said:
sorry
our mistake
i tested ur SW with a *.nb0, which extracted with xda3nbftool.exe------*.nb0 with ipl and bootloader.
and now i find, that *.nb0 should be and must be extracted with ur P525ROMTool -d galaxy.cap,------that means *.nb0 without ipl and bootloader
everything is fine, when *.nb0 is extracted with ur P525ROMTool
i think creazy2000 just made the same mistake like me.
Click to expand...
Click to collapse
Oh, I know !
I make a mistake !
thanks

Is it a seperate tools that the imgfs? Need I find this tool to finish the whole things? Where can I find this tool?

P525_V3320_WWE2
I have P525_V3.29.0 WWE3
Can someone tell the difference between them it looks that the first one is newer but I am confused by the WWE which is newer
Thanks all

Night Runner said:
Is it a seperate tools that the imgfs? Need I find this tool to finish the whole things? Where can I find this tool?
Click to expand...
Click to collapse
Everything about complete process is in the first post. What is you dont understand from here?

jmfa59 said:
P525_V3320_WWE2
I have P525_V3.29.0 WWE3
Can someone tell the difference between them it looks that the first one is newer but I am confused by the WWE which is newer
Thanks all
Click to expand...
Click to collapse
WWE means "world wide english".
First is 3.32, therefore, its newer.

Ingvarr
Thanks Buddy,
can you explain WW2 and WWE3 it seems that the latter is newer but the version V3.29 is older or is ment for different country

getting vendor id errore while upgrading the official wm6

im using a tytn and getting errore message
dows the official upgrade is for tytn or doopod ?
anyone can help ??
i try using hard sspl and still .. same

I think it may be because it is a rom for Asian networks... I got a similar error, and will have to manually import the settings for my network providor... other than that, everything else went fine...
I believe there are cabs kicking about this forum to auto setup for various providors.. I think it is trying to auto detect your vendor, and if not Asian, is returning the error
I think thats all the error is showing...

If you've downloaded one of the other cooked ROMs on this site, you should have an exe file called RUU_wrapper.exe.
Now, install WINRAR and right click on the dopod rom and choose extract and it will extract various files, one of which will be another exe file. Extract this exe file again and you should end up with a file RUU_Signed.nbh - this is th only file you'll need out of the lot.
You can delete all the other files from the dopod ROM now, just keeping the RUU_signed.nbh. Copy the RUU_wrapper.exe file into the same folder and run it and you will flash the dopod rom to your phone nicely - just make sure you're HARDSPL first!
Now, you could be even smarter at this point and use dutty's good nbhtool if you like to "unwrap" RUU_signed file and remove the IPL \ SPL (though with HARDSPL, I'm not sure this is necessary) and the Radio part if you like (and the boot splash screens if you're so inclined and then use it to wrap it all back up again.
HTH,
Smiffy.

Backing Up and Restoring ROM Image

Hi there.
The HTC Diamond has recently been released in Canada under Rogers and I'd like to backup the stock rogers ROM for safe keeping (and sharing).
I've been trying to find instructions on how to do this and found:
http://forum.xda-developers.com/showpost.php?p=2370527
Which is great, but after creating the RAW rom dumps, how do I flash the ROM backup back to the device?
Thanks!
noob edit: I apologize if this has been covered in the past. I have tried searching but surprisingly, I haven't found anything...

In my continuing research, I found this tool: HTC ROM Tool
http://forum.xda-developers.com/showthread.php?t=311909
I recall seeing this on a diamond wiki page. Is there an updated version that has Diamond rom support?
Thanks,

No one here can help a lonely noob trying to learn? Is what I'm asking even possible? Thanks!

I'm a noob too, but what you do is, you get one of the kitchens, put the extracted files in baserom (or similar folder) extract all sys and OEM packages, then adjust it as you wish (by deleting), and create new rom with HTC rom tool, and then you flash it back.
I'm beginner myself, but this should work.
Make sure you have all Visual C++ and NET. packages installed on your PC, and try to install the kitchen directly on C:/ drive. It helps.

I got the Rogers Diamond last night as well. I extracted the Part0x.raw files (as per Pof's instructions), then used a kitchen to extract the SYS/OEM from Part02.raw and the XIP from Part01.raw.
I haven't cooked them yet to test, but will try tonight hopefully and maybe post it if I'm successful. I got a brick when I tried making the OS ROM out of an existing ROM, as described in the Hermes and Elf DumpRom wikis. So I guess cooking it instead is the safest way to go.
Also remember to flash the unsigned Hard SPL 1.93 by OliNex after you back up the SPL.

hello,
one possible solution is to use a kitchen. for example:
http://forum.xda-developers.com/showthread.php?t=452184
put your raw's to BASEROM-folder.
put your original provider-rom in the same folder.
start !BEGIN
now you can select between two EXTRACT-MODEs.
first mode is extract ruu_signed.nbh only.
the second is for raw's with ruu_signed.nbh.
USE THE SECOND and wait until its finished.
now you can change or tweaks something - if you want.
follow the instructions and than you have your flashable rom.
BUT THE BACKUP/COPY - ROM is not for 100% the same like on your device.
for example: you have installed some programs with serial-key or activating by internet.
after restoring you have to enter/activating again.
some files will be changed back by original rom-files like the registry.
your personilized startmenu goes away - tweakees will lost.
the reult:
you will be angry.
after some experimantells now i used a combination of own cooked rom (with tweeks and buyed programs) and a backup-file which is not so big in MB.
okokur

[android] NAND flashale android !!USER!! Questions UPDATED MANY HOW TO'S

Hi there, as many of you may know dzo or simple god makes a flashable version of android for our KAISERs.
But vefore here are some rules:
THIS THREAD IS MADE TO KEEP THE FLASHING ANDROID ON KAISER DEV THREAD CLEAN FROM USERQUESTIONS!!!
DON'T ASK USER QUESTIONS IN THE DEV THREAD!!!
This Thread is for experienced Kaiser users who aren't in development but wan't to see android running native from NAND.
THIS IS AT THE CURRENT STATE VERY VERY VERY BETA, THERE MAY BE A HIGH RISC TO BRICK YOUR DEVICE. THIS WILL COMPLETLY WIPE WINDOWS MOBILE. JUST USE IT IF YOU CAN ANSWER YOURSELF THE FOLLOWING QUESTIONS: (without search function)
-What is an .nbh file
-how to flash a kaiser
-What is HardSPL /Security unlock
-How to recover a bad rom flash?
-What to do if your device won't start anymore?
-Do you have basic android skills?
Ok Guys, little cleanup and updates:
INDEX:
-Post one:
Different flashing methods
Things to take care off
-Post two:
How to creat your own nbh files
How to make custom splash screens
-Post three:
Working Systems/rootfs
Bugs
Usefull Links
Thanks
HOW TO START ANDROID FROM NAND
Method one:
1-Download one of the nbh's here http://www.megaupload.com/?f=SA71F1MT, you'll have to look for the right panel type, Key layout and resolution needed for the rom you're flashing, just like your default.txt from sd boot.
2-Download http://www.mediafire.com/?zldjhfnkzk2
3-Copy the androidinstall.tar from the androidinstall.zip file to the root of your sdcard
4-delete/rename any old android files on your sdcard
5-Unzip the androidinstall.zip and replace the ruu_signed.nbh in it with the one you downloaded in the first link. (must be named ruu_signed.nbh)
-6Run the custom ruu.exe - thats all after reboot you'll have a flashed Cupcake android.
Method two:
1-delete/rename any old android files on your sdcard
2-Download one of the nbh's here http://www.megaupload.com/?f=SA71F1MT, you'll have to look for the right panel type, Key layout and resolution needed for the rom you're flashing, just like your default.txt from sd boot.
3-Create three empty files on your sdcard wihout any extension:
-datafstonand
-systemfstonand
-rootfstonand
4-Copy your prefered rootfs.img, system(img,ext2,sqsh) and an empty data.img to sdcard root
5-Copy the nbh file you downloaded to the root of your sdcard and rename to kaisimg.nbh
6-Reboot your device using restart button and cam button, then when it tells you, press power key to flash the new nbh.
-Reboot by pulling the battery - Thats it ( First start may take a while and may reboot randomly, just give it some time)
Different Tricks and hints (collected in the forums):
-Change Panel Type:
Run: "echo 1 > /sys/module/board_htckaiser/parameters/panel_type" through adb or init
-Experimental GPS:
For working, gps you need to replace libgps.so with the one from the vogue gps thread.
Experimental openGL Drivers ( Eclair Only)
-Download this one and flash your prefered nbh: http://rapidshare.com/files/345432577/kasiandroid_nbh_with_opengl.zip
-Install the included script sheduler, and replace the afterboot.txt with the one included in the zip file
This will install an app that will run the afterboot.txt after every boot and fix file permissions.
-Or you can open the afterboot.txt and run it in terminal after every boot.
To see if it works install the included gallery3d.apk, iff you see thumbnails, it worked

Not tested by me, yet through no time.. (Thanks to quitlahok and rzk333 for this manual)
THIS IS JUST FOR THOOSE WHO ARE MORE IN DEVELOPMENT AND LINUX
HOW TO CREATE YOUR OWN NBH FILES:
1- Set up your prefered Linux Setup, i use Debian.
2-Build kaiser kernel with wiki manual
3-git clone git://androidhtc.git.sourceforge.net/gitroot/androidhtc/tinboot
4-git clone git://androidhtc.git.sourceforge.net/gitroot/androidhtc/bootenv
5-cd bootenv
6-cp buildInitrd buildInitrd-mini
7-nano (or whatever your favorite editor is) buildInitrd-mini
8-change all instances (2 of them) of initrd to initrd-mini
9-sh buildInitrd-mini
10-cd tinboot
11-nano tinboot.S
12-the paths to fix are at the bottom of the file, it's pretty self-explanatory. higher up in the file you'll see the kernel cmdline under an .ifdef kaiser line
13-after that you'll need to download and extract any windows kitchen, and install wine however your linux distro requires and make a note of the path you extract nbhmerge.exe to as you'll need it in your tinboot.S file, along with the path to your kernel zImage and initrd-mini.gz
after that if you've got everything else in place, go ahead and run the compilekaiser script in the tinboot dir and you should have an nbh
if the nbh won't flash (i had this issue) copy the output.nb file, boot into windows, and use nbhutil.exe to convert it to an nbh and flash that one. for some reason yang doesn't work right for me personally
HOW TO CREATE CUSTOM SPLASH SCREENS: (this is a manual by POV)
1. Install HardSPL.
2. Create a BMP file in paint, size must be 240x320, save it as BMP 24bit.
3. Download SplashTool
4. Load your BMP on nb_image_converter (included in SplashTool's zip) and save it as splash.nb
5. Open SplashTool.exe and convert splash.nb to new format.
6. Pack the resulting splash.nb into a NBH file using htc rom tool.
7. Flash your cusotm NBH using CustomRUU.
This will not harm your installed android

WORKING SYSTEMS / ROOTFS'S: ( Collected in the forums)
- http://forum.xda-developers.com/showthread.php?t=587116 ION Donut, reuploaded by 160bpm
- http://forum.xda-developers.com/showthread.php?t=619980 MYNs warm Donut
- http://forum.xda-developers.com/showthread.php?t=619718 Jamezelles Sense Tattoo
- http://forum.xda-developers.com/showthread.php?t=591104 Plemens Donut AOSP
- http://forum.xda-developers.com/showthread.php?t=603028 Jamezelles Sense Hero
- http://forum.xda-developers.com/showthread.php?t=619285 Shidells Android 2.1
rootfs 2010-01-06 works best for me get it here: http://sourceforge.net/projects/androidhtc/files/
Bugs:
NOT WORKING: WiFi, GPS, Voice Call, Bluetooth
(GPS experimental with the files from first post)
Usefull Links:
Android on Sourceforge:
http://sourceforge.net/projects/androidhtc/files/
Android on htc Website:
http://www.androidonhtc.com
dzo's page:
http://it029000.massey.ac.nz/vogue/
Android SDK:
http://developer.android.com/sdk/
Tinboot dev thread:
http://forum.xda-developers.com/showthread.php?t=614275
Thanks:
dzo, plemen, jamezelle, zenulator, enatefox, mssmision, vilord, rzk333, diagdave
SORRY IF I'LL FORGET ANYONE

Here's a couple boot screens I made.

Thanks i'll add this to the first post

Thanks JeckyllHavok, good idea I keep posting over here am not into kernel things anyway

Ok after a few attempts I finally got Android flashed, and running, using my backup kaiser, which has no network connection, so the lack of wifi is a bit of a problem, but seems to be working fine so far, and fast
Just wondering if it would be possible to flash other versions, like eclair or even flan, since polyrhythmic's eclair version seems to be nice and stable, or is this going to fast to soon?

Just tested this with sshidels nexus rom, but itjust ends in bootscreen loops. Maybe other roms work

Looks like in need to learn to read. I found these instructions in the Vouge forum:
Method 2:
------------------------------------------------------------------
Check here for NBH files containing a linux kernel and initrd to allow you to flash android to your vogue and wipe windows completely.
The ROMs are dated and there are three versions.
They are identical except the resolution; 240x320, 320x428 and 320x480.
This rom will copy your rootfs, system and data to nand (the internal storage of the phone) so you will only be running from nand. To do this, make sure you have a working setup (using system.sqsh and data.img without partitions) and install the new rootfs. Make sure it still works.
Make sure you have a carrier rom to go back to. Android currently doesn't let you change any of the radio parameters so you would have to flash back to a carrier rom to re-provision your phone.
Now create 3 empty files in the root of your sd card called:
rootfstonand
systemfstonand
datafstonand
These must be all lower case with no extensions and they will be deleted once each fs has been copied.
Now flash the rom corresponding to your resolution and wait.
Click to expand...
Click to collapse

Buried for stupidity. Works great so far.

Flashing now.
1st edit: We have Android .
2nd edit:26 min it just turned itself off ... creepy ... soft reset ....I'll post back results.
3rd:39 min later Actual Phone screen came up No SIM ..Opps rebooted waiting agian.

What is working/not working with this flash.

From what I've read everything except.
Blutooth
wifi
GPS
Still waiting back at ANDROID screen

I have successfully flashed THIS BUILD using the following method:
dzo said:
...create 3 empty files in the root of your sd card called:
rootfstonand
systemfstonand
datafstonand
These must be all lower case with no extensions and they will be deleted once each fs has been copied.
Click to expand...
Click to collapse
It's a little small and awkward due to the set resolution, but it's possible to flash different builds!
Another note: When flashing builds it takes a very long time, but when it gets to the setup android screen it has a system FC and the screen doesnt respond. This has happened everytime. I had to pull the battery and when I boot it up a second time it boots just fine.

loserskater said:
I have successfully flashed THIS BUILD using the following method:
It's a little small and awkward due to the set resolution, but it's possible to flash different builds!
Another note: When flashing builds it takes a very long time, but when it gets to the setup android screen it has a system FC and the screen doesnt respond. This has happened everytime. I had to pull the battery and when I boot it up a second time it boots just fine.
Click to expand...
Click to collapse
Hi
Can you please send me the files on the sdcard. I am having an issue with every build.
Thanks

Did wifi work with any builds?

I think no, not now

Tilt
Hey all,
Working great on my tilt except the ringer just rings in the earpiece at like phone call volume. You can't really hear it unless you have your ear against it. Any thoughts?
I used DZO's build of 1.5 and one of the NBH filwa from Ra333 as the DZO one did not work.

Jaguarius said:
Hey all,
Working great on my tilt except the ringer just rings in the earpiece at like phone call volume. You can't really hear it unless you have your ear against it. Any thoughts?
I used DZO's build of 1.5 and one of the NBH filwa from Ra333 as the DZO one did not work.
Click to expand...
Click to collapse
Are the keys on the slide keyboard working correctly

OK now got two nand flashed kasiers, (both kais130), first using the 'original' flash method, ( dzo nbh, androidinstall.tar), and the other method from the vogue threads, with polyrhythmics Eclair build, which is much slower, ( uses SD card rather than Nand?).
Both seem to be working as well as can be expected at this early stage of Nand flashing.
What I would like to know is how to 'upgrade' our zImage, since some builds have a different zImage version than the one we are currently flashing with, ( I am assuming our zImage is in the NBH flash), since this may help enable wifi/gps which we are presently lacking.