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

[[ACL]]

Originally Posted by vistazifta

yea i noticed ur android itself doesnt support it although im hoping u will one day but it goes further than it used to i actually get it booted up into android its when it starts lookin for service that makes it reboot now so it aint that bad

Edit: and acl if i dont have service do u still want my logs because i doubt it would make a difference if all u want is ril info?

i think i see the issue.. the android update on the autobuild already had a ppp directory in system which is preventing it from making a link. so give me 10 mins and redownload the android upate.tgz.

Ok done: redownload the android update and install. sorry bout that fellas. Maybe the picture below will get you to forgive me

[arrrghhh]

Originally Posted by [ACL]

Ok done: redownload the android update and install. sorry bout that fellas. Maybe the picture below will get you to forgive me

I see CM NAND in our future!

[natemcnutty]

Originally Posted by [ACL]

i think i see the issue.. the android update on the autobuild already had a ppp directory in system which is preventing it from making a link. so give me 10 mins and redownload the android upate.tgz.

Ok done: redownload the android update and install. sorry bout that fellas. Maybe the picture below will get you to forgive me

That looks awesome ACL. Any chance you can push all of your changes to bootenv (feel free to overwrite my commits)? I pulled down your changes and a few things were missing. I was initially not getting the cache partition to format and mount because it was not created yet. Once I did that, it got me further to where Android started initializing, but then it keeps rebooting.

Your files from the autobuild seem to boot up just fine, so I'm thinking there is something not committed in initrd or something like that. Also, no data for me either, but not real way to show anything without ADB. I'm sure it still has to do with pppd, but I'm just not quite sure where to begin on that.

Edit: Also, your androidinstall does not have a /system/bin/su

[[ACL]]

Originally Posted by natemcnutty

That looks awesome ACL. Any chance you can push all of your changes to bootenv (feel free to overwrite my commits)? I pulled down your changes and a few things were missing. I was initially not getting the cache partition to format and mount because it was not created yet. Once I did that, it got me further to where Android started initializing, but then it keeps rebooting.

Your files from the autobuild seem to boot up just fine, so I'm thinking there is something not committed in initrd or something like that. Also, no data for me either, but not real way to show anything without ADB. I'm sure it still has to do with pppd, but I'm just not quite sure where to begin on that.

wow i didnt realize git didnt have my cache directory. Thats some buggy shit. I made a directory and addeded but git does not have it. So when you check the gz. its there .. odd. Thanks for the fixes bro.. I guess its smarter to have the script create it. So these are good commits.

I have a BIG todo for you..

when we install new modules we just put em in data/modules. Thing is they should really be in data/modules/<uname of kernel>. Then link it back to data modules. This is so we can have different versions of modules for more than one kernel. This is a must since if you upgrade a kernel and wipe your old modules you wont be able to go back incase its a bad kernel. Also we cant use mount bind like we do now. Sometimes it locks the partition busy so we need to implement this and use links for the final product. You can do it

hmm.. maybe we need lmiller to adb and verify. Can you ssh into your phone once wifi is enabled? should give u full shell.


Edit: thanks to this im going to re-push out a new autobuild. shortly. Cache is important for cyanogen. they use it for alot.. so good call on that partition.

[natemcnutty]

Originally Posted by [ACL]

wow i didnt realize git didnt have my cache directory. Thats some buggy shit. I made a directory and addeded but git does not have it. So when you check the gz. its there .. odd. Thanks for the fixes bro.. I guess its smarter to have the script create it. So these are good commits.

I have a BIG todo for you..

when we install new modules we just put em in data/modules. Thing is they should really be in data/modules/<uname of kernel>. Then link it back to data modules. This is so we can have different versions of modules for more than one kernel. This is a must since if you upgrade a kernel and wipe your old modules you wont be able to go back incase its a bad kernel. Also we cant use mount bind like we do now. Sometimes it locks the partition busy so we need to implement this and use links for the final product. You can do it

hmm.. maybe we need lmiller to adb and verify. Can you ssh into your phone once wifi is enabled? should give u full shell.


Edit: thanks to this im going to re-push out a new autobuild. shortly. Cache is important for cyanogen. they use it for alot.. so good call on that partition.

Sounds great. I also added the installer script to git so we can keep that consistent. I'll look into the uname stuff tomorrow. I almost always prefer ln -s or cp -a over mount --bind.

[[ACL]]

Originally Posted by natemcnutty

Sounds great. I also added the installer script to git so we can keep that consistent. I'll look into the uname stuff tomorrow. I almost always prefer ln -s or cp -a over mount --bind.

thanks dood.. also if you can test with the cache directory that would be awesome. I havent been able to replicate the issue of corruption yet.. (edit: just recreated it.. looks like cache seems to get corrupt).

I do know we cant format the recovery parititon table. Something about it being protected .. :-\

anwyays off to bed.. thanks for the commit..

21.352783] msm_nand_read_oob 1ff31000 800 10 failed -74, corrected 0
to
[ 62.875152] msm_nand_read_oob 1ff3f800 800 10 failed -74, corrected 0

[Lmiller1708]

Originally Posted by natemcnutty

That looks awesome ACL. Any chance you can push all of your changes to bootenv (feel free to overwrite my commits)? I pulled down your changes and a few things were missing. I was initially not getting the cache partition to format and mount because it was not created yet. Once I did that, it got me further to where Android started initializing, but then it keeps rebooting.

Your files from the autobuild seem to boot up just fine, so I'm thinking there is something not committed in initrd or something like that. Also, no data for me either, but not real way to show anything without ADB. I'm sure it still has to do with pppd, but I'm just not quite sure where to begin on that.

Edit: Also, your androidinstall does not have a /system/bin/su

Nate if you keep getting your Android install stuck in a bootloop it means you are most likely having some permission issues.
Specifically this file: /system/etc/dbus.conf
Here is what the Vogue changes them too...
chown 1002:1002 /system/etc/dbus.conf
chmod 0444 /system/etc/dbus.conf


@ACL,
How are you creating your andriodinstall.tgz?
I'm thinking we are having issues with permissions coming right from the tgz.

Here is mine... Probably not right but it works once I run the fixperm script

echo "Making androidupdate.tar"
cd androidupdate
chown -R 0:0 *
tar -cvzf ../androidupdate.tar *
chown -R lance:lance *
cd ..
echo "Moving androidupdate.tar"
cp androidupdate.tar ~/Desktop/Android/1.Complete_Build/ANDROID/

echo "Making androidinstall.tar"
cd androidinstall
chown -R 0:0 *
tar -cvzf ../androidinstall.tar *
chown -R lance:lance *
cd ..
echo "Moving androidinstall.tar"
cp androidinstall.tar ~/Desktop/Android/1.Complete_Build/ANDROID/

cp install-seq.sh ~/Desktop/Android/1.Complete_Build/ANDROID/

echo "Completed..."

[[ACL]]

Originally Posted by Lmiller1708

So you guys still can't write to the cache partition?
If so try changing this line on the MAKEDEV's

mknod -m 0666 /dev/mtd/mtd4 c 90 6
to
mknod -m 0666 /dev/mtd/mtd4 c 90 8

I stated this before but never looked at the push, but I was also uncertain about it... Sorry about that.

But maybe the cache getting corrupt is something different... Kinda like the losing of some widgets on the Android home screen?

As for not being able to write to the recovery partition are you still using the same starting place as before. 0x4000000?

I won't be able to test for a while today for I forgot my phone at home.

I say test it out. move the dalvik cache to the cache partition and beat it up.. . im using the default mtdparts on git. But i cant format the recovery partition it since it keeps saying its protected. So we may need to shift stuff around a bit.

Originally Posted by Lmiller1708

Nate if you keep getting your Android install stuck in a bootloop it means you are most likely having some permission issues.
Specifically this file: /system/etc/dbus.conf
Here is what the Vogue changes them too...
chown 1002:1002 /system/etc/dbus.conf
chmod 0444 /system/etc/dbus.conf


@ACL,
How are you creating your andriodinstall.tgz?
I'm thinking we are having issues with permissions coming right from the tgz.

Here is mine... Probably not right but it works once I run the fixperm script

echo "Making androidupdate.tar"
cd androidupdate
chown -R 0:0 *
tar -cvzf ../androidupdate.tar *
chown -R lance:lance *
cd ..
echo "Moving androidupdate.tar"
cp androidupdate.tar ~/Desktop/Android/1.Complete_Build/ANDROID/

echo "Making androidinstall.tar"
cd androidinstall
chown -R 0:0 *
tar -cvzf ../androidinstall.tar *
chown -R lance:lance *
cd ..
echo "Moving androidinstall.tar"
cp androidinstall.tar ~/Desktop/Android/1.Complete_Build/ANDROID/

cp install-seq.sh ~/Desktop/Android/1.Complete_Build/ANDROID/

echo "Completed..."

Hmm bootloop you say ? we need logs bro. Permissions issues are easy to spot since android bitches about it. So yes you could be right, the android may have bad permissions on the tgz which we need to fix. I havent had a boot loop in ages tho so that my be something else.