Why?? no total flash of droid to tp2

#1 (**permalink**) 12-02-2010, 02:44 AM

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

stupid question but had to ask.

thayer · #2 (**permalink**) 12-02-2010, 08:23 AM

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.

tiger2wander · #3 (**permalink**) 12-02-2010, 02:46 PM

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** · #4 (**permalink**) 12-02-2010, 06:45 PM

Quote:

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 · #5 (**permalink**) 12-09-2010, 01:32 PM

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** · #6 (**permalink**) 12-09-2010, 01:44 PM

Quote:

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.