NAND Testing - 05-25 Update: New LK, Recovery.img, Kernel Updates through Recovery

[Lmiller1708]

Wirelessly posted (Vogue: Mozilla/5.0 (Linux; U; Android 2.2.1; en-us; MSM Build/FRX03) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1)

Originally Posted by [ACL

]Moving to the hd2 nand driver seems to make the errors go away. but i still cant write onto the partitions.

So far this is what i've done

# cat /dev/mtd/mtd0 > /sdcard/mtd0.img
# cat /dev/mtd/mtd1 > /sdcard/mtd1.img
# cat /dev/mtd/mtd2 > /sdcard/mtd2.img
# cat /dev/mtd/mtd3 > /sdcard/mtd3.img

mtd0 is the only one that has data. The rest are just empty. I'm assuming its because i wiped the whole phone ? i should have left winmo partially in there to check.

After trying to flash_image one of the partitions i tried to mount it and i get the following.

[ 518.155426] msm_nand_read_oob: unsupported ops->len, 512
[ 518.155517] end_request: I/O error, dev mtdblock3, sector 0

This doesnt look good. i know the 512 error is common but not sure why it's happening. So this is where im at..

ACL,
Great job on the progress!
Let me know if there is anything I can help with.

[[ACL]]

i dunno if i would consider this progress :-\

all of the sudden i cant boot into android. It seems that the data.img and system.img no longer mount.

grrr this is hard to figure out since i cant adb anymore. Have to just constantly butcher the init to find out where its dying. I guess we can begin to mod the initrd to make this more friendly.. im sure nate is ahead of me and prob has that all written already :-p

update: ok looks like android itself (not rootfs) is trying to mount the system and data from nand. since i havent been successful in writing to nand yet, it craps out..

[Lmiller1708]

Well... I guess being worked on is progress!

Where can I get the files to compile the drivers?

Thanks!

[[ACL]]

Originally Posted by Lmiller1708

Well... I guess being worked on is progress!

Where can I get the files to compile the drivers?

Thanks!

the only thing holding me back from commiting them is that i cant verify if i can write to nand yet. I need to know how to disable android from automouting the yaffs partitions.

[Lmiller1708]

Originally Posted by [ACL]

the only thing holding me back from commiting them is that i cant verify if i can write to nand yet. I need to know how to disable android from automouting the yaffs partitions.

To stop auto mounting try commenting out this line of code in your Rootfs init. It's about 15 lines from the top.

/bin/mount | grep mtd
notnand=$?

if [ $notnand = "0" ] ; then
  echo "running from NAND"
  /bin/mount -t yaffs2 /dev/block/mtdblock2 /system
  /bin/mount -t yaffs2 /dev/block/mtdblock3 /data
fi

[[ACL]]

Originally Posted by Lmiller1708

To stop auto mounting try commenting out this line of code in your Rootfs init. It's about 15 lines from the top.

/bin/mount | grep mtd
notnand=$?

if [ $notnand = "0" ] ; then
  echo "running from NAND"
  /bin/mount -t yaffs2 /dev/block/mtdblock2 /system
  /bin/mount -t yaffs2 /dev/block/mtdblock3 /data
fi

I commented all that out.

This actually happens when androuid loads. The console shows yaffs trying to mount block2 and 3. And boom.. death to boot up since it cant find anything. so so close.

[Lmiller1708]

Originally Posted by [ACL]

I commented all that out.

This actually happens when androuid loads. The console shows yaffs trying to mount block2 and 3. And boom.. death to boot up since it cant find anything. so so close.

Ok.
Could be in the init of the initramfs.
What does your command line look like?

[[ACL]]

Originally Posted by Lmiller1708

Ok.
Could be in the init of the initramfs.
What does your command line look like?

whatver is on the git plus the mtd parts i put in. everything else is the same.

If you want to get started and testing. You can try to download the hd2-nand.c file from the nand tree. Just remove everything in our msm-nand.c with the stuff from that file. Once you have that you should be where im at.

[natemcnutty]

Originally Posted by [ACL]

i dunno if i would consider this progress :-\

all of the sudden i cant boot into android. It seems that the data.img and system.img no longer mount.

grrr this is hard to figure out since i cant adb anymore. Have to just constantly butcher the init to find out where its dying. I guess we can begin to mod the initrd to make this more friendly.. im sure nate is ahead of me and prob has that all written already :-p

update: ok looks like android itself (not rootfs) is trying to mount the system and data from nand. since i havent been successful in writing to nand yet, it craps out..

Well, I had been in the process of testing moving to the Vogue's bootenv/tinboot setup when my USB died on me. Still haven't gotten USB functions back, and I've seriously tried everything I can think of.

Vogue's tinboot has some really awesome changes since wozzer ported it over for us. They now have working data during boot, ADB enabled by initramfs, and lots of other great changes.

They use bootenv git for building their initrd which they've changed to lzma instead of gzip: SourceForge - androidhtc/bootenv.git/summary

And their tinboot is here: SourceForge - androidhtc/bootenv.git/summary

[[ACL]]

Originally Posted by natemcnutty

Well, I had been in the process of testing moving to the Vogue's bootenv/tinboot setup when my USB died on me. Still haven't gotten USB functions back, and I've seriously tried everything I can think of.

Vogue's tinboot has some really awesome changes since wozzer ported it over for us. They now have working data during boot, ADB enabled by initramfs, and lots of other great changes.

They use bootenv git for building their initrd which they've changed to lzma instead of gzip: SourceForge - androidhtc/bootenv.git/summary

And their tinboot is here: SourceForge - androidhtc/bootenv.git/summary

so what you are trying to tell me is that its time to pillage code.. :-p.. you wanna champion this? im busy so if you can prep a patch ill commit.