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

[steveholtam]

Big time props to ACL, Nate, and Lmiller for the continued work on the NAND stuff. This is the future for our TP2's. Not that the masses know or care, but they will someday when you guys get done.

Keep up the good work!

[tpdjr]

Man this is exciting. Sounds like things are really moving forward on nand keep up the work acl and all the other devs. Thank you so much

[[ACL]]

Sorry vfellas .. at a rooftop ripped drunk... I won't be able to look into anything till tomottow.

[natemcnutty]

Originally Posted by [ACL]

Sorry vfellas .. at a rooftop ripped drunk... I won't be able to look into anything till tomottow.

Haha, have fun

[natemcnutty]

Well, this is going better than I expected. Unless someone tells me otherwise, I'm modifying the new bootenv/tinboot for the following:

1) Full NAND only (at least initially until it is stable)
2) Rhodium support only (taking out detection of other phones)
3) build.prop is now responsible for setting lcd density (currently 240 in FRX04 and makes our cmdline is redundant...)
4) Incorporating stinebd's OTA update.zip method
5) Froyo libs moved into system (see note below)

I've learned that you can't bind mount onto an initrd, so you have to use links and copy the data that way. Unfortunately, this poses a problem for our method of copying hw lib files based on the build type. For now, I am going to cook the libs into the system. This means we need to cook the libs and stuff into system for each build type (i.e. froyo, gingerbread, cynogen, etc.) that you want to try.

Here's the code I'm talking about:

RCSCRIPT=""
RCCONFIG=""

echo "Checking for build type..."
if [ -f /system/hero.build ] ; then
    echo "Hero build detected"
    RCSCRIPT="hero"
    RCCONFIG="hero"
    ln /data/app_s /system/app

elif [ -f /system/eclairhero.build ] ; then
    echo "HERO 2.1 BUILD DETECTED -- ECLAIR"
    RCSCRIPT="eclairhero"
    RCCONFIG="eclairhero"
    mount --bind /lib/eclair/hw /system/lib/hw

elif [ -f /system/eclair.build ] ; then
    echo "Eclair build detected"
    RCSCRIPT="eclair"
    RCCONFIG="eclair"
    mount --bind /lib/eclair/hw /system/lib/hw

elif [ -f /system/froyo.build ] ; then
    echo "Froyo build detected"
    RCSCRIPT="froyo"
    RCCONFIG="froyo"
    ln -s /lib/froyo/hw /system/lib/hw

    # vold: Fix sdcard device location for CDMA boards (thanks paalsteek)
    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

elif [ -f /system/gingerbread.build ] ; then
    echo "Gingerbread build detected"
    RCSCRIPT="gingerbread"
    RCCONFIG="gingerbread"
    ln -s /lib/froyo/hw /system/lib/hw

    # vold: Fix sdcard device location for CDMA boards (thanks paalsteek)
    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

elif [ -f /system/tattoo.build ] ; then
    echo "Tattoo build detected"
    RCSCRIPT="tattoo"
    RCCONFIG="tattoo"

elif [ -f /system/donut.build ] ; then
    echo "Donut build detected"
    RCSCRIPT="donut"
    RCCONFIG="donut"
    mount --bind /lib/donut/hw /system/lib/hw

elif [ -d /system/lib/donut ] ; then
    echo "Donut build detected"
    RCSCRIPT="donut"
    RCCONFIG="donut"

elif [ -f /system/xrom.build ] ; then
    echo "xROM build detected"
    RCSCRIPT="xrom"
    RCCONFIG="xrom"

elif [ -f /system/rogers.build ] ; then
    echo "Rogers build detected"
    RCSCRIPT="rogers"
    RCCONFIG="rogers"

elif [ -f /system/cyanogen.build ] ; then
    echo "cyanogen experimental detected.....eating donuts"
    RCSCRIPT="cyanogen"
    RCCONFIG="cyanogen"

elif [ -f /system/custom.build ] ; then
    echo "Custom init.rc detected"
    cp /system/sysinit.rc /build.cfg/init.sysinit.rc
    RCCONFIG="hero"
    RCSCRIPT="sysinit"
    
else
    echo "Unknown Android build. Assuming Ion variant"
    RCSCRIPT="ion"
    RCCONFIG="ion"

    # for the fake sensors library
    mount /lib/hw /system/lib/hw -o loop
    chmod 666 /dev/input/event0
fi

echo "using /init.$RCSCRIPT.rc as init.rc"
echo "using $card/conf/$RCCONFIG.user.conf"
cp "/init.cfg/init.$RCSCRIPT.rc" /etc/init.rc

Edit: We also need to cook the rootfs file /lib/froyo/libhardware_legacy.so into system.

[Lmiller1708]

Great work Nate.

For the LCDDENSITY this line of code won't work anymore?

LCDDENSITY=`/bin/grep -o "lcd.density=.*" /proc/cmdline | /bin/sed -e "s/.*lcd.density=//g" -e "s/ .*//g"`

if [ "$LCDDENSITY" != "" ] ; then
    echo "ro.sf.lcd_density=$LCDDENSITY" >> /etc/default.prop
    echo Setting ro.sf.lcd_density=$LCDDENSITY
fi

Also were you able to get Android booted?
And how did you make your initramfs?

[[ACL]]

Originally Posted by natemcnutty

Well, this is going better than I expected. Unless someone tells me otherwise, I'm modifying the new bootenv/tinboot for the following:

1) Full NAND only (at least initially until it is stable)
2) Rhodium support only (taking out detection of other phones)
3) build.prop is now responsible for setting lcd density (currently 240 in FRX04 and makes our cmdline is redundant...)
4) Incorporating stinebd's OTA update.zip method
5) Froyo libs moved into system (see note below)

I've learned that you can't bind mount onto an initrd, so you have to use links and copy the data that way. Unfortunately, this poses a problem for our method of copying hw lib files based on the build type. For now, I am going to cook the libs into the system. This means we need to cook the libs and stuff into system for each build type (i.e. froyo, gingerbread, cynogen, etc.) that you want to try.

Here's the code I'm talking about:

Full nand is the only way to go.. you know my old saying ? "give me nand or give me death".. :-p

The other phones are so far behind nand its good if we wipe em out ..

Lets face it. Each build from now on will most likely need tweaking so moving the libs so we dont need to mount bind isnt a bad idea. Plus once the cookers get their hands on our precious code, bam they will release builds like wild fire. It will be up to them to move the modules to the right place. An alternative is to create a thin slice to hold the modules so we can mount bind them that way. But a new partition just for modules? i dunno if thats a good idea.

What about the rc files ? having a directory dedicated to just rc files like the haret rootfs limits us to builds. So we should just do the same as vogue (and every other build) and have the rc in the build itself.

i got so drunk last night and i had to call in sick. So im doing some small changes here and there to help out, but it sounds like you got it all under control. I'll have to commit the links for bin directly instead of the binaries and any patches you want to tinboot itself, let me know.

Also i'm uploading the frx04 now.. i'll post a link later.

Edit: Forgot about the screen calibration. ideas ?.

[Lmiller1708]

Originally Posted by [ACL]

Full nand is the only way to go.. you know my old saying ? "give me nand or give me death".. :-p

The other phones are so far behind nand its good if we wipe em out ..

Lets face it. Each build from now on will most likely need tweaking so moving the libs so we dont need to mount bind isnt a bad idea. Plus once the cookers get their hands on our precious code, bam they will release builds like wild fire. It will be up to them to move the modules to the right place. An alternative is to create a thin slice to hold the modules so we can mount bind them that way. But a new partition just for modules? i dunno if thats a good idea.

What about the rc files ? having a directory dedicated to just rc files like the haret rootfs limits us to builds. So we should just do the same as vogue (and every other build) and have the rc in the build itself.

i got so drunk last night and i had to call in sick. So im doing some small changes here and there to help out, but it sounds like you got it all under control. I'll have to commit the links for bin directly instead of the binaries and any patches you want to tinboot itself, let me know.

Also i'm uploading the frx04 now.. i'll post a link later.

Edit: Forgot about the screen calibration. ideas ?.

Great ACL!
Hope to see your frx04, I found my system is not extracting correctly. It was making a folder in the root called androidinstall with my system and data there...

Wish I had more time to work on this and not just hack away here and there... You and Nate are doing a much better job so I will just wait to test!

Glad you had a good time last night! We need to do that every now and then!

For screen calibration can we just add a generic one for now? And then have a program change it from there. I'm pretty sure that's what is done with the Vogue. But I'm not sure of the program just yet...

By the way I was able to get the initramfs working correctly once I extracted the initrd.gz files.

Happy Flashing!

[coolsilver]

Wow you guys have been making some killer progress.

[natemcnutty]

Originally Posted by coolsilver

Wow you guys have been making some killer progress.

The progress has really been made by the Vogue guys. We've just moved a bunch of our stuff into their environment and are trying to make it work.

That being said, I've fixed the sbin folder, but I can't commit until I fix the changes I've made in init. We use a lot of mount --binds which we can no longer do. Also, I had to build the drivers into /system/lib/modules to get it to recognize the modules. I think Vogue might be cooking them into the kernel, but I don't know how you would go about doing that.