yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] diagdave:
not even up to the stage of beta testing yet. just help with porting :

@
@ Tinboot V 1.0
@ Very simple bootloader for HTC Vogue
@ Martin Johnson - M.J.Johnson@massey.ac.nz
@
.equ	MTYPE,	1553
.equ	RAM_START,	0x10000000
.equ	RAM_SIZE,	0x08000000
.equ	INITRD_START,	RAM_START+0x00800000
.equ	KERNEL_OFFSET, 0x8000
.equ	XIP_END,	0x2ff000

.org 0
b boot

.org 0x40
.word 0x43454345
.word romhdr+0x80000000	@ location of wince romhdr
.word romhdr
.org 0x100
tags:	.word 5,0x54410001,1,0x1000,0	@ ATAG_CORE, pagesize=4K
.word 4,0x54410002,RAM_SIZE,RAM_START	@ ATAG_MEM
.word 4,0x54420005,INITRD_START,fin-initrd	@ ATAG_INITRD2
cmdline_start:	.word (cmdline_end-cmdline_start)/4,0x54410009	@ ATAG_CMDLINE
.ifdef x428
.asciz "mddi.width=320 mddi.height=428 mtdparts=msm_nand:0x00300000@0x1600000(boot),0x00d80000@0x01900000(root),0x05980000@0x02680000(system),0x08000000@0x08000000(userdata)"
.endif
.ifdef x480
.asciz "mddi.width=320 mddi.height=480 mtdparts=msm_nand:0x00300000@0x1600000(boot),0x00d80000@0x01900000(root),0x05980000@0x02680000(system),0x08000000@0x08000000(userdata)"
.endif
.ifdef x320
.asciz "mddi.width=240 mddi.height=320 mtdparts=msm_nand:0x00300000@0x1600000(boot),0x00d80000@0x01900000(root),0x05980000@0x02680000(system),0x08000000@0x08000000(userdata)"
.endif
.align
cmdline_end:	.word 0,0	@ ATAG_END

.org 0x00001000

boot:	ldr r0,initrd_ptr
ldr r3,fin_ptr
ldr r1,ird_start_ptr

copyinitrd:	ldr r2,[r0],#4
str r2,[r1],#4
cmp r0,r3
blo copyinitrd

mov r0,#0
ldr r1,mtype
ldr r2,tags_addr
ldr pc,kernel_start

mtype:	.word MTYPE
initrd_ptr:	.word initrd+RAM_START
fin_ptr:	.word fin+RAM_START
ird_start_ptr:	.word INITRD_START
kernel_start:	.word 0x10008000
tags_addr:	.word 0x10000100

romhdr:
.word 0x0	@ dllfirst
.word 0x0	@ dlllast
.word 0x80000000	@ physfirst
.word 0x80000000+fin	@ physlast
.word 0	@ num mods
.word 0x80000000+fin	@ ramstart
.word 0x80000000	@ ramfree
.word 0x88000000	@ ramend
.word 0	@ copyentries
.word 0x80000000	@ copyoffset
.word 0	@ profilelen
.word 0	@ profileoffset
.word 0	@ numfiles
.word 0	@ flags
.word 0x20	@ fsrampercent
.word 0	@ drvglobstart
.word 0	@ drvgloblen
.word 0x201c2	@ cputype/flags
.word 0x80000000	@ pextensions
.word 0	@ trackingstart
.word 0	@ trackinglen

.org KERNEL_OFFSET
kernel:
.incbin "../arch/arm/boot/zImage"
initrd:
.incbin	"../../bootenv/initrd-mini.gz"
.align
fin:
.org XIP_END-0x20000,0xff
.incbin "emptyimgfs"
@rootfs:
@.incbin "../../bootenv/rootfs.yaffs"
@.org rootfs + 0xd80000

Ive check the partition sizes and they should be ok for the kaiser? so must be something im missing in here?
[Tilt, TyTN II, MDA Vario III Android Development] rzk333:
check bootloader log from mtty, it must say something like this

OEMTranslateBaseAddress 23 80000000 80000000
IPLMSG:0x8:INFO: Loading image ...
IPLMSG:0x9:INFO: Jumping to image...
OEMLaunchImage 80000000
Jump to Physical Address 10300000
*Disconnect*

0x10300000 is your RAM_START,

0x00300000 is shift from Vogue addresses, that dzo catched from logs.

all you need is shift RAM_START, kernel_start and tag_addr addresses in bootloader and change MTYPE, then change prompt to yang to make capable nbh for kaiser.

I now working on tinboot for Nike, it have similar hardware to kaiser. Kernel boots, but now stops on some rpc_call, but that I think I can fix.

sorry for bad english and good luck with tinboot on kaiser (:
[Tilt, TyTN II, MDA Vario III Android Development] diagdave:
Wow thanks for your help, wouldnt have thought of looking there. Thanks
[Tilt, TyTN II, MDA Vario III Android Development] diagdave:
how did you find the tag_addr and kernel_start address for the Nike? - Nerver mind , got it to boot upto the same RPC_Write error now, thank you
[Tilt, TyTN II, MDA Vario III Android Development] diagdave:
managed to get past the rpc_write error, commented it out, now invalid root device, presume a kernel driver problem. thought you might want to know for the nike? /kernel/drivers/ contains the error.
[Tilt, TyTN II, MDA Vario III Android Development] rzk333:
now we must dump a whole NAND and find there a partiton table. there we must find a XIP start address, for vogue it is 0x1600000. we need this to map NAND for this command from cmdline

mtdparts=msm_nand:0x00300000@0x1600000(boot),0x00d80000@0x01900000(root),0x05980000@0x02680000(system),0x08000000@0x08000000(userdata)

this is means: 3MB on x1600000 for kernel, 13.5M for rootfs on 0x01900000 and etc, without that, kernel will panic/freeze due to inaccessible root device in memory.
[Tilt, TyTN II, MDA Vario III Android Development] willou:
hello,

great explain. If you want, i was to posssibility to flash my nand kaiser.

Just write me and i trying your work and report it.

Willou
[Tilt, TyTN II, MDA Vario III Android Development] diagdave:
i beleieve there is also a problem with:

.equ	INITRD_START,	RAM_START+0x00800000

it should load the initrd before trying to switch to rootfs, and it doesnt?

Also the partition data is stored in the generated output.nb.payload so that should actually be the same as starting point
[Tilt, TyTN II, MDA Vario III Android Development] stringbean82:
Thats great news, am able to do beta tests for you guys, as my Kaiser is my secondary phone nowadays. am able to help trouble shoot and search for problems. pm me if you want my gtalk account.
[Tilt, TyTN II, MDA Vario III Android Development] bandur:
Great initiative

Great initiative! I wish I was able to help, but unfortunately my abilities leave much to desire. so all I am able to offer is words of encouragement ...
[Tilt, TyTN II, MDA Vario III Android Development] rzk333:
yup, kernel skips it, because initrd is on wrong shift in rom, that is because RAM_START/NAND start are wrong, I guess.
[Tilt, TyTN II, MDA Vario III Android Development] diagdave:
Do you have the same problem on the nike?
[Tilt, TyTN II, MDA Vario III Android Development] rzk333:
yes, everything are equal on this stage of loading kernel, due to same hardware. I have no progress now.
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
Excellent work. I'm no expert by any means but I'll see if I can help at least port the code over. Yet another bookmarked thread to the list
[Tilt, TyTN II, MDA Vario III Android Development] SnakeMAR:
I there, my Kaiser is just only for personal tests (flashing, testing betas and android)

I can help you with my phone, but i don't writing any code... just for test!

Sorry for my bad english, i'm french
[Tilt, TyTN II, MDA Vario III Android Development] rzk333:
excellent work of dzo :) thanks go to him.

tinboot repo updated for some changes related to kaiser, now pointers are calculated dynamicly and kaiser have own compile script. nand loading turned off cuz we don't now know start address. this should help to pass bug with initrd.
[Tilt, TyTN II, MDA Vario III Android Development] Taluven:
second link worked fine for me. Still messing with getting it to boot. Will let you know how it goes here shortly.
[Tilt, TyTN II, MDA Vario III Android Development] garringm:
I could not get the nbh file to flash, but the tar file worked
[Tilt, TyTN II, MDA Vario III Android Development] Taluven:
Tar worked and was able to get the .nbh to flash, but I went to a different .nbh file that I am used to using for my keyboard type. Everything seems to work so far (Sort of). Having two problems now though, Can't get the microphone to work in Phone Calls, I can hear the caller, but they cannot hear me. This is not specific to this build though, just started recently. And cannot get 3g to sync up on AT&T, working on both of these now trying to get the data connection to work. Will see how it goes.
[Tilt, TyTN II, MDA Vario III Android Development] garringm:
I could not get a data connection to establish, back to the 3 file method for now.
[Tilt, TyTN II, MDA Vario III Android Development] Taluven:
Yeah, same here. Flashing a stock rom back into the phone to make sure all the hardware is working, then will go back to the 3 file load, it worked fine at least. Didn't have much luck with the GPS, but wi-fi and everything else worked, but still had that microphone issue. Still trying to get to the bottom of that problem. Will see if the mic works with a stock wm 6.1 load.
[Tilt, TyTN II, MDA Vario III Android Development] kubino99:
don't know what happened, but I've reuploaded the nbh should be working now :

megaupload.com/?d=P5JFM40J

dataconection I didn't test yet will have a look on, gps shouldn't be problem to fix. Will test it tomorrow.
[Tilt, TyTN II, MDA Vario III Android Development] SnakeMAR:
Sorry, but, can you remake same file in all others resolutions please? i can't open NBH file!

Thx a lot in advance...;)
[Tilt, TyTN II, MDA Vario III Android Development] diagdave:
i can confirm wireless working in this rootfs, seems nice and stable, but still using my nbh. (lol)
[Tilt, TyTN II, MDA Vario III Android Development] kubino99:
ok here you have the rest :-)

240 x 320 panel 1 : megaupload.com/?d=NEU86F6Z

320 x 480 panel 1 : megaupload.com/?d=6BUCT1RP

320 x 480 panel 2 : megaupload.com/?d=T9RIYCLJ
[Tilt, TyTN II, MDA Vario III Android Development] zenity:
Can also confirm working wireless in this build too, went back to diagdave's nbh and my workaround to get GPS and WiFi.

This is starting to look like a way forward though, and hopefully soon a more integrated single NBH solution.

:)
[Tilt, TyTN II, MDA Vario III Android Development] kubino99:
yes but propably you wouldn't be able to start the phone without SD card inserted ;-) there are some changes made in initrd-mini.gz to start without SD mounted.
[Tilt, TyTN II, MDA Vario III Android Development] diagdave:
did people want me to make mine sd card free as well? not a hard change
[Tilt, TyTN II, MDA Vario III Android Development] zenity:
No I can't start it without having the SD inserted, and as a workaround it's a bit involved, I'd prefer not to have to have the SD inserted at boot, but afaik we still don't have the ability to mount after boot anyway.

However don't get the idea that I am saying your work is not good, it's great, and I hope you can get the other initial bugs worked out as well, I hope my workaround solution is just temporary :)
[Tilt, TyTN II, MDA Vario III Android Development] rzk333:
cause BT module is more complicated thing than touchscreen or others, BT have firmware, commands to initiate/transfer/something, and many other things. To make it work we need reverse everything related to BT from winmo.
[Tilt, TyTN II, MDA Vario III Android Development] garringm:
Sure why not I've been using a modified version of your nbh files since you released them, I am more curious of getting a version of donut in an install.tar file to do away with the need of a system.sqsh on my sdcard
[Tilt, TyTN II, MDA Vario III Android Development] Taluven:
Quick Question for someone that may know the answer to this.

I am using an AT&T Tilt, am loading the polyrythmic dark eclair load using the "Workaround" that zenity posted in #148 I believe it is.

When I load dark eclair from Haret.exe, I can get the GPS and Wifi working just fine, but as soon as I add the 3 files and load everything to NAND, GPS Stops working. Dark eclair works great, my charging problems are gone, my microphone problem is gone, wifi works just fine, but for the life of me, I cannot get GPS to load after I put everything in NAND.

I am not sure where to look now, so any suggestions out there would be great.

Tal.
[Tilt, TyTN II, MDA Vario III Android Development] diagdave:
place systemfstonand on your sd card and it will copy to nand, then you can remove the system.sqsh
[Tilt, TyTN II, MDA Vario III Android Development] garringm:
Its just like one big circle these last couple pages, I do this and it works, I am not 100% sold on the fact that its not using this sqsh file as the OS. Now with kubino's nbh It will run 100% out of phone memory great but no data I flash back to your nbh files I have data but it will not run without sdcard or sqsh file
[Tilt, TyTN II, MDA Vario III Android Development] diagdave:
i know its along time to wait but at the weekend i plan on releasing a 'cleaner' rom. better boot splash, n loading splash. and no need to place files on the card.
[Tilt, TyTN II, MDA Vario III Android Development] kubino99:
May be some devices were not created in initrd, shouldn't be a big issue to check, I'll have a look on that at home, and try to fix it.
[Tilt, TyTN II, MDA Vario III Android Development] samtruman:
fix for not enough space

there is also an issue relating to space for application and other stuff inside nand, if i try to download files for use google navigation (eclair by polyrithmics) the system tell me that there isn't enough space.

If i use system from nand all works good and data are stored on sd.

Maybe we should use a promiscous mode for fix the problem: application, downloaded data, music ecc on sd, the other on nand...
[Tilt, TyTN II, MDA Vario III Android Development] Amaranthus:
Can you make a 480 one with the tilt keyboard fix? Thanks for all your work.
[Tilt, TyTN II, MDA Vario III Android Development] j101399j:
I have tried this both ways for Dark Eclare (Method 2 and using kubino99's updated RootFS hack and androidinstall.tar) If I use method 2 with the workaround, battery sucks because I don't have the zImage hack; but data, WiFi and GPS works (well GPS turns on but I don't get a lock; not important). On the other hand, when I use kubino99's method and the workaround, I get WiFi, and kinda GPS, but no Data. So either I get Data and bad battery life, or no Data and great battery life. Anyone else seeing this or have a fix?
[Tilt, TyTN II, MDA Vario III Android Development] JeckyllHavok:
Have you tried to creat one of the new nbh's from vilord?

I always got a failed, no system.img found on sd card
[Tilt, TyTN II, MDA Vario III Android Development] bandur:
I don't know much about this, but could it be that the new method doesn't use system.img/sqsh but androidinstaller.tar?
[Tilt, TyTN II, MDA Vario III Android Development] JeckyllHavok:
You're right, but i used the androidinstaller.tar from mssmission. I think we have to change something in one of the files. i will have a look and compare changes between the new vogue files and our "old" kaiser files
[Tilt, TyTN II, MDA Vario III Android Development] Taluven:
I did a lot of testing with Dark Eclair and regular Eclair Variants on My Tilt, battery is bad but that is due to the fact that the audio drivers in the builds are bad still and the system will not go into sleep. I finally went back to a base ion Donut build, and used the nand image from post 1 in this thread. I had to use adb to pushe the 1.5 libgps.so files from the Vogue thread (http://xdaforums.com/showthread.php?t=616436)to the /lib and /lib/donut folders and now finally have a version running off nand that has full functionality except no bluetooth.

There are a lot of fixes coming down the pipe for eclair builds, best to wait for a more stable build. If I get a chance this weekend, I will be building a development system and will try to compile a working version for the HTC phones, but I am new to the development side of things, so will take me a while to get up to speed. Mainly just lacking the correct environment to do the builds in at the moment.
[Tilt, TyTN II, MDA Vario III Android Development] garringm:
I don't believe that atleast with our phones using the 3 nandto files actually install the system to nand otherwise I would not need these files on my sdcard afterwards, if I remove them or even rename them afterwards I get unable to opn persistent property errors and missing file errors. But even at that I think I have my phone so jacked up its hopeless for me
[Tilt, TyTN II, MDA Vario III Android Development] j101399j:
I am going to try and learn how to create my own nbh files for this and see what happens. All I need to do really is build the hack into an NBH file, use the workaround and method 2 and I should be good to go. If I get it working, I'll post it (but don't hold your breath, this may take me a long time).\

Gonna try to create my own NBH's but wow, that looks way over my head at the moment
[Tilt, TyTN II, MDA Vario III Android Development] mayad79:
NAND and default.txt

So I was thinking since we dont have a config file when loading via NAND can one be created?

Is the default file the equivalent, and if so can one just copy the text?

Did the zimage suspend hack from polyrythmics rom incorporate into the NAND flash, when the .nbh was created?

Just some things running through my head at the moment. I am still trying to get my compiling environment, and am still looking for an (android for dummy's book).

later and thanks, this is fun.

Mo
[Tilt, TyTN II, MDA Vario III Android Development] zenity:
The default.txt file is used by haret to pass the boot command line parameters to the linux kernel at boot time, so when booted from nand the kernel is initialised in a different way, I forget the whole kernel boot procedure, but in short, the kernel parameters are already in the various NBH files we use to flash to nand.

To change them we need to edit the files on our devices, not tried this, but it should be easy enough to track down the files we'd need to edit.

I'm not certain the zImage hack is part of our nand roms yet, but again this should be possible, although it may involve reflashing.

Once you get a compiler environment set up, you'll be able to answer most of these questions for yourself of course :)
[Tilt, TyTN II, MDA Vario III Android Development] Thomy_1:
i don't understand.

is it the Android OS or Windows Mobile with skin?
[Tilt, TyTN II, MDA Vario III Android Development] jamezelle:
its the real deal lol :p:p:p
[Tilt, TyTN II, MDA Vario III Android Development] papatel:
I've found this to be the case as well. I've tried MANY builds for my tilt and all of them are rather unusable except this base build at the top of this thread. I haven't tried your recommended changes, but it sounds promising.

I tried this build: showthread.php?t=625052

and this build: showthread.php?t=591104

using the nbh's on this thread with no luck.

They complain about missing rootfs and stop booting. Obviously its missing, we no long use it... Can someone look into this? Still looks like our kaiser nbh builds are falling behind what the vogue is using and working. See no reason kaiser should be behind vogue in terms of latest andriod builds running from nand flash.
[Tilt, TyTN II, MDA Vario III Android Development] diagdave:
Expert?

Well since you say the kaiser sould be upto the same level as the vogue, you must be right! It obvious from your amazing enlightened post that your an expert in building roms for the kaiser, so how bout you start building them rather then moaning here about the current development of the builds!
[Tilt, TyTN II, MDA Vario III Android Development] Taluven:
@diagdave:

Just a note, I think the progress that has been made on the nand boots for the kaisers has been awesome, wish I knew more about it, would help more instead of always just throwing out questions.

But speaking of questions, I have been running Poly's Dark themed Eclair build from haret, and when it boots, I get DATA, GPS and WIFI. But as soon as I load one of your .nbh files ffrom the first page, it kills the gps. Data and WIFI still work just fine.

I have been poking around in my tilt (HTC 100) for about a week or more now trying to figure out what I can do to get the GPS working. I imagine there is something in the zimage that doesn't exist in your.nbh files. I have tried using adb and pushing libgps.so over, and that helps on some other donut builds that I have worked with, but it won't work with the eclair builds.

Not sure if it is something you can look into or fix, but if you have any suggestions on where I can look, Maybe I can get this thing to work better. Realistically the eclair builds I have tried work very well so far, but just can't get the GPS to work in them unless I boot from winmo.

Thanks in advance.
[Tilt, TyTN II, MDA Vario III Android Development] diagdave:
have you tried this?
[Tilt, TyTN II, MDA Vario III Android Development] Taluven:
Yeah, that is how I managed to get WIFI to work. Have followed those instructions to the tee and gps is still not functioning, I can run GPS Test and it will run and show the gps symbol at the top, but it never locks or even sees the satellites.

Have the exact same problem with donut builds, except for the fact that I can copy libgps.so over to /lib and /lib/donut and normally that will fix the gps issue in donut, no luck doing that in eclair though.
[Tilt, TyTN II, MDA Vario III Android Development] papatel:
confirmed, n00b

Yes, I am a complete novice at this. If I said something blatantly wrong, please correct me. Unfortunately, I do not have time to contribute other than donations. Your kind words do not encourage me to keep investing in these projects.
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
GPS on kaiser works quite differently to vogue and nobody has updated the kaiser kernel interface. I'll take a look at it when I have some time.
[Tilt, TyTN II, MDA Vario III Android Development] samtruman:
I want to say thank you to digdave and dzo for their efforts, i hope the development will continue in the future so we will have an until great phone with all the functionalites of android.

A last thing..with android on nand do you have the battery percentage fixed at 100% with almost all donut buids?
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
I fixed the battery driver today, get one of the latest NBHs from my site and it should work.
[Tilt, TyTN II, MDA Vario III Android Development] duchoang81:
Hi Dzo, is your new KAISIMG file fro NoMoRootfs method or for old method? I tried new way NoMoRootfs but no luck to get it start installer. Pls give us step-by-step solution with your build. Thank for your great support.
[Tilt, TyTN II, MDA Vario III Android Development] Taluven:
@DZO,

I will take a look at your updated nbh today and see how it goes. As for the GPS, I am aware that it works differently on the Tilts, that is kind of why I keep saying something when I can.

I know the build for poly's Dark Eclair works great with the GPS hardware in the tilt, so there is definately something in the files there that at least initiate and talk with the hardware, able to get locks pretty fast and they work really well.

I appreciate you responding and taking the time to look into it, I hope you have some luck.
[Tilt, TyTN II, MDA Vario III Android Development] Taluven:
I was unable to get my tilt to boot with old method files, haven't tried the nomorootfs method yet though. Probably won't at this time, went back to a donut build again that is stable on my phone for now.
[Tilt, TyTN II, MDA Vario III Android Development] garringm:
ATT working Nand bootloader

https://sourceforge.net/projects/and...les/2010-02-04

This is the link with all the new stuff from the crew over on the vogue threads. I am able to install full builds straight to phones internal memory with working data now on my ATT Tilt running on the ATT network. Just to clarify this is for the norootfs builds. I understand that some of you running on other networks have already been able to do this. There are 2 different nbh files one for installing builds in general and one for eclair builds. I have tried them both and they both work but my preference is with the sense tattoo build. These nbh files however do not incorporate the tilt keyboard setting so I am putting out a request for someone to do this. There are also files on there for running through haret I have not tried nor will I try. My goal was to get rid of winmo completely and that has now been accomplished. I may even be able to postpone getting a new phone for a while.

http://xdaforums.com/showpost.php?p=5540600&postcount=158

here is the official post from vilord dealing with this. Maybe we can get #1 post here updated with a NoMoRootfs directory
[Tilt, TyTN II, MDA Vario III Android Development] loserskater:
If somebody doesn't beat me to it, Ill make anoher zip with all resolution/panel/tilt keyboard combos tonight