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

**Lmiller1708** · #1 (**permalink**) 02-02-2011, 04:29 PM

Quote:

Originally Posted by [ACL]

yeah. Were you able to write to block2 and 3 yet ? I will to post a tarball of frx4. I just untared it directly onto block2 once i mounted it.

Nope not yet... Just was able to see them.
How do we add the modules during the initramfs? I have a general Idea from the Rootfs, but I'm not getting it to work just yet...

**[ACL]** · #2 (**permalink**) 02-02-2011, 04:36 PM

Quote:

Originally Posted by Lmiller1708

Nope not yet... Just was able to see them.
How do we add the modules during the initramfs? I have a general Idea from the Rootfs, but I'm not getting it to work just yet...

i will have to look into what is missing. i never had to modprobe but im just saying thats how you load it.

For me its all done automatically. when i boot the stuff is already there. You will need to study Dzo's code to see how he is doing everything.

**Lmiller1708** · #3 (**permalink**) 02-02-2011, 08:14 PM

Quote:

Originally Posted by [ACL]

i will have to look into what is missing. i never had to modprobe but im just saying thats how you load it.

For me its all done automatically. when i boot the stuff is already there. You will need to study Dzo's code to see how he is doing everything.

When I run the modprobe command it says my version is off from what my modules should be. This could be because I'm not remaking the whole build every time, just the NBH. I will test this shortly...

Thanks for the HELP NATE!

**Lmiller1708** · #4 (**permalink**) 02-03-2011, 12:13 AM

After playing around with the initramfs I decided to just try the one from the Vogue. So I took the initrd.gz and cooked that into the nbh file.
I then took a androidinstall.tgz file from HERE.... Went though the install process... And it booted on NAND! It looked very different though and as you can imagine nothing really worked.

So I then tried to extract the FRX04 system and place that into the androidinstall.tgz file and was able to get it to install but not boot to android.

Time to call it a night... I'm sure I'm missing something simple.

**natemcnutty** · #5 (**permalink**) 02-03-2011, 02:09 AM

Quote:

Originally Posted by Lmiller1708

After playing around with the initramfs I decided to just try the one from the Vogue. So I took the initrd.gz and cooked that into the nbh file.
I then took a androidinstall.tgz file from HERE.... Went though the install process... And it booted on NAND! It looked very different though and as you can imagine nothing really worked.

So I then tried to extract the FRX04 system and place that into the androidinstall.tgz file and was able to get it to install but not boot to android.

Time to call it a night... I'm sure I'm missing something simple.

Did you modify the initramfs to load your button mappings or something? The replimenu didn't work for me when I tried that. Also, you can try the latest tars from here: Android HTC - Browse Files at SourceForge.net

**Lmiller1708** · #6 (**permalink**) 02-03-2011, 08:17 AM

Quote:

Originally Posted by natemcnutty

Did you modify the initramfs to load your button mappings or something? The replimenu didn't work for me when I tried that. Also, you can try the latest tars from here: Android HTC - Browse Files at SourceForge.net

Nope no modification was necessary. To get to the replimenu hold the Vol Up key. Then the screen can be used instead of the keys... Not perfect but it works. Touch the lower left to go down and lower right to go up, then touch the center for OK.

I just installed the most recent Vogue from the link you gave me above.

How are you guys making your initramfs, I think this is where I'm going wrong? Here is the script that I made...

Code:

cd initramfs
find . | cpio -o -H newc | gzip > ../initrd.gz
cd ../
mv initrd.gz tinboot-linux-msm/kernel/initrd.gz
echo rm initrd.gz

bheremans · #7 (**permalink**) 02-04-2011, 10:44 AM

Quote:

Originally Posted by Lmiller1708

Nope no modification was necessary. To get to the replimenu hold the Vol Up key. Then the screen can be used instead of the keys... Not perfect but it works. Touch the lower left to go down and lower right to go up, then touch the center for OK.

I just installed the most recent Vogue from the link you gave me above.

How are you guys making your initramfs, I think this is where I'm going wrong? Here is the script that I made...

Code:

cd initramfs
find . | cpio -o -H newc | gzip > ../initrd.gz
cd ../
mv initrd.gz tinboot-linux-msm/kernel/initrd.gz
echo rm initrd.gz

I think it is a problem with the files in git. Most files should be links to the busybox executable. If you clone kaisers git, the files are links :

Code:

bhe@HP-dv3500-bhe:/tmp/test/initrd-kaiser/initrd/bin$ ls -ali
total 2544
549794 drwxr-xr-x 2 bhe bhe   12288 2011-02-04 15:40 .
549793 drwxr-xr-x 4 bhe bhe    4096 2011-02-04 15:40 ..
549796 lrwxrwxrwx 1 bhe bhe       7 2011-02-04 15:40 [ -> busybox
549797 lrwxrwxrwx 1 bhe bhe       7 2011-02-04 15:40 [[ -> busybox
549798 -rwxr-xr-x 1 bhe bhe  117460 2011-02-04 15:40 adbd
549799 lrwxrwxrwx 1 bhe bhe       7 2011-02-04 15:40 addgroup -> busybox
549800 lrwxrwxrwx 1 bhe bhe       7 2011-02-04 15:40 adduser -> busybox
549801 lrwxrwxrwx 1 bhe bhe       7 2011-02-04 15:40 adjtimex -> busybox
549802 lrwxrwxrwx 1 bhe bhe       7 2011-02-04 15:40 ar -> busybox
549803 lrwxrwxrwx 1 bhe bhe       7 2011-02-04 15:40 arp -> busybox
549804 lrwxrwxrwx 1 bhe bhe       7 2011-02-04 15:40 arping -> busybox
549805 lrwxrwxrwx 1 bhe bhe       7 2011-02-04 15:40 ash -> busybox
549806 lrwxrwxrwx 1 bhe bhe       7 2011-02-04 15:40 awk -> busybox
549807 lrwxrwxrwx 1 bhe bhe       7 2011-02-04 15:40 basename -> busybox
549808 lrwxrwxrwx 1 bhe bhe       7 2011-02-04 15:40 bbconfig -> busybox
549809 lrwxrwxrwx 1 bhe bhe       7 2011-02-04 15:40 bunzip2 -> busybox
549810 -rwxr-xr-x 1 bhe bhe 1530860 2011-02-04 15:40 busybox
549811 lrwxrwxrwx 1 bhe bhe       7 2011-02-04 15:40 bzcat -> busybox

initrd-kaiser in android-initrd-kaiser - Gitorious

You could download it here as tar.gz to start test building : Tree for initrd-kaiser in android-initrd-kaiser - Gitorious

**[ACL]** · #8 (**permalink**) 02-03-2011, 08:48 AM

havent hand time to mess with this at all last night. I passed out in my chair and never work up. Now i gotta get my ass to work.

Nate: bootenv in Tinboot for linux-msm - Gitorious

That will be our initird repo.

**Lmiller1708** · #9 (**permalink**) 02-03-2011, 09:03 AM

Quote:

Originally Posted by [ACL]

havent hand time to mess with this at all last night. I passed out in my chair and never work up. Now i gotta get my ass to work.

Nate: bootenv in Tinboot for linux-msm - Gitorious

That will be our initird repo.

This is great! Thanks ACL!
But can you build it? If I run the BuildInitrd script my initrd.gz turns out to be like 250 MB...

**natemcnutty** · #10 (**permalink**) 02-02-2011, 06:15 PM

Quote:

Originally Posted by Lmiller1708

Nope not yet... Just was able to see them.
How do we add the modules during the initramfs? I have a general Idea from the Rootfs, but I'm not getting it to work just yet...

I'm assuming you are using XDAndroid's initramfs. They do not mount data or system in initramfs, so you will have to manually add this to init. If you want to use NAND, you will do this and expand FRX04 to system:

Code:

/bin/mount -t yaffs2 /dev/block/mtdblock2 /system
/bin/mount -t yaffs2 /dev/block/mtdblock3 /data

If you want to do off the SD card, do this:

Code:

losetup /dev/block/loop0 $card/data.img
[ $? -eq 0 ] || fail "Failed to find $card/data.img on SD Card"
e2fsck -y /dev/block/loop0
mount -t ext2 -o relatime /dev/block/loop0 /data
losetup /dev/block/loop1 $card/system.ext2
[ $? -eq 0 ] || fail "Failed to reach system.ext2 on SD Card"
e2fsck -y /dev/block/loop1
mount -t ext2 -o relatime /dev/block/loop1 /system

Then you just need to mount lib and etc:

Code:

mount --bind /lib/froyo/hw /system/lib/hw
mount /data/etc /etc
cp -a /system/etc/* /etc
cp -ar /init.etc/* /etc/
cp "/init.cfg/init.$RCSCRIPT.rc" /etc/init.rc

Also, you may need this for CDMA board (put after the etc stuff):

Code:

if [ -d /sys/devices/platform/msm_sdcc.3 ]; then
     /bin/sed -i -e 's:/devices/platform/msm_sdcc\.2:/devices/platform/msm_sdcc.3:g' /etc/vold.fstab
fi

And finally, you can use the code from rootfs to do the rest:

Code:

if [ -e "$card/modules-$(uname -r).tar.gz" ] && ! `strings /data/modules/wlan.ko 2>/dev/null | grep -q "vermagic=$(uname -r)"`; then
    echo "Installing $card/modules-$(uname -r).tar.gz"
    if [ ! -d "/data/modules" ] ; then
        mkdir /data/modules
    fi
    tar xzf $card/modules-$(uname -r).tar.gz -C /data/modules
    ln -s /data/modules /data/modules/`uname -r`
else
    echo "Modules already unpacked for this kernel version -- skipping installation of $card/modules-$(uname -r).tar.gz"
fi

mount --bind /data/modules /lib/modules
mount --bind /data/modules /system/lib/modules

cp -R /etc/wifi/* /data/modules/
depmod
[ -f /etc/wifi/wlan.ko ] && rm /etc/wifi/wlan.ko

sed -i s/^#wifi/wifi/ /tmp/build.prop