Why?? no total flash of droid to tp2

will there ever be a total flash for the tp2 with the droid O.S

stupid question but had to ask.

[thayer]

What is NAND booting?
NAND booting uses code on the NAND to boot directly into Android without having Windows Mobile on the device. Currently, zImage and initrd.gz are stored on the internal NAND while the modules, rootfs, ext2, and data are stored on the SD card.


I'd say thats close enough. In this case, android is the only OS on the device.

[demonlordoftheround]

Wirelessly posted (Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; IEMobile 8.12; MSIEMobile6.0) Sprint T7380)

And of course it is a work in progress, but it is getting closer every day.

[Miami_Son]

The fact that BT is not yet working would probably stop anyone from having XDAndroid as their sole operating system.

[tiger2wander]

Yep, NAND testing is going to get more closer to have a completely Android ROM on TP2. But we have biggest problem is: can not access WinMo Internal Storage, BTW NAND boot project has only zImage and initrd on that ROM, everything else such as: system, rootfs, data still use external SDCard to store.

I'm looking and hoping much on this project to bring my TP2 to have Android work on it, because of I can not find any device with perfect hardware full qwerty keyboard and tilt adjustable screen like TP2 have

[natemcnutty]

Originally Posted by tiger2wander

Yep, NAND testing is going to get more closer to have a completely Android ROM on TP2. But we have biggest problem is: can not access WinMo Internal Storage, BTW NAND boot project has only zImage and initrd on that ROM, everything else such as: system, rootfs, data still use external SDCard to store.

I'm looking and hoping much on this project to bring my TP2 to have Android work on it, because of I can not find any device with perfect hardware full qwerty keyboard and tilt adjustable screen like TP2 have

And I think moving things like ext2 and rootfs to NAND is possible using the NBH creation tool, but the pathing would be all off since everything looks to the SD Card for those files. It would take a lot of re-writing things to point to the right place.

[tiger2wander]

AFAIK put ext2 and rootfs to NAND is posible too and easy to do but the real problem is linux kernel for TP2 is not yet implemented to access that memory, NAND, only kernel and initrd are placed on NAND and it will be put to RAM when the phone is booted then no access anymore to NAND

Another way is some guru can write a bootloader for it to control the way to select what address to load kernel and OS like grub bootloader did on PC. BTW we will have really native Android and everything on TP2, eg. multiple OS on mobile such as WM & Android together and can select to boot. But this way is really hard caused by the bootloader and WM OS is closed source and we must RE it to understand how it work and modify it to do such things!

[arrrghhh]

Originally Posted by tiger2wander

AFAIK put ext2 and rootfs to NAND is posible too and easy to do but the real problem is linux kernel for TP2 is not yet implemented to access that memory, NAND, only kernel and initrd are placed on NAND and it will be put to RAM when the phone is booted then no access anymore to NAND

Another way is some guru can write a bootloader for it to control the way to select what address to load kernel and OS like grub bootloader did on PC. BTW we will have really native Android and everything on TP2, eg. multiple OS on mobile such as WM & Android together and can select to boot. But this way is really hard caused by the bootloader and WM OS is closed source and we must RE it to understand how it work and modify it to do such things!

You hit the nail on the head with that last one. We don't have too many wizards at reverse engineering... It's not a very simple task. Same reason haret progress is so slow.

[tiger2wander]

yep, so we need to get 'head hunting' for some guru in RE to help us

in another side, did you try to use fastboot from HTC, and may we can RE/Disassembly something inside ROM come from official HTC Android's phone, as I see it has a rom.zip contain: (HTC Desire ROM)

boot.img
radio.img
rcdata.img
recovery.img
system.img
userdata.img
hboot_8x50_0.93.0001_20100810.nb0
splash1.nb0
splash2.nb0
android-info.txt

I think we can get some useful information from files such as: boot.img, recovery.img. I'll try to open and see what's damn things inside it. We may get some lucky

And the great tool I recommended to guys want to RE it is DataRescue IDA with Hex-Rays Decompiler plugin. That is a great tool I ever know and use. Get more information here: IDA Pro Disassembler - multi-processor, windows hosted disassembler and debugger

Good luck, guys!