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 natemcnutty

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.

They add the modules with a update.zip file.
We should be able to do the same. Their code is in there initrdfs/init file about 3/4 of the way down...

Are you still planing on using a update system like the vogue?

[natemcnutty]

Originally Posted by 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)



They add the modules with a update.zip file.
We should be able to do the same. Their code is in there initrdfs/init file about 3/4 of the way down...

Are you still planing on using a update system like the vogue?

Yeah, so here is what I have so far.

I am using the bootenv we ported from the Vogue. I can boot into the installer, it formats and extracts the androidinstaller.tar file. It doesn't matter if I pack the modules into the system tar or if I use the androidupdate.tar option, I run out of space and it fails to finish. So I'm stuck where it says I need the modules at this point.

I think I need to add more space on tinboot...

[Lmiller1708]

Originally Posted by natemcnutty

Yeah, so here is what I have so far.

I am using the bootenv we ported from the Vogue. I can boot into the installer, it formats and extracts the androidinstaller.tar file. It doesn't matter if I pack the modules into the system tar or if I use the androidupdate.tar option, I run out of space and it fails to finish. So I'm stuck where it says I need the modules at this point.

I think I need to add more space on tinboot...

I ran into the same problem last night, if I add the modules.
I'm still just using ACL's system and going to test out adding the modules during the update. But not too sure how it is going to work, because it all goes to the same spot... So we might have to add more space.

EDIT: Guess what.... I ran out of space...

[Lmiller1708]

Originally Posted by [ACL]

data as in service you mean or wifi? cant really say without logs

Attached is the Log from tonight. (Had to zip it)
Same issues as before... Couple of them should be easy to solve.
But currently the modules are not getting added.
I'm going to strip down the system as much as possible to save ~15 MB.
Just to get it to load the modules and hopefully get a clean boot.

I also attached my INIT from the initrd. I left most of the stuff from the Vogue in there... Just incase...

Update: After some reading HERE, I decided to change my Command Line code to this:

mtdparts=msm_nand:0x10000000@0x0(nand)ro,0x01500000@0x04000000(root),0x07BA0000@0x05500000(system),0x06f60000@0x0CFA0000(userdata)

This gave me a larger system while keeping the data partition the same. This them allowed me to load in the modules.
I also added the "ro" at the end of the nand partition, not too sure what this does but devices with similar mtdparts cmdline have this. Basically everything but the Vogue.

Also I still can't get my System nor my Data to stick after a reboot. I thought it was just my Data but now it seems to be both. Reading back in the irc logs i see wozzer had this same issue. Might be something with the mtdparts cmdline.

[[ACL]]

Originally Posted by natemcnutty

Well, I think I have all the modifications done that we need, but I can't build the initrd properly. The sbin folder has the same issue as the bin folder, and when I try to recreate all of the links, the tinboot process tells me that it couldn't find readkey and various other programs.

LZMA sees all of the files as identical so it only stores one copy, but I still think that it would expand to run and take up an insane amount of memory. In any case, I have attached a list of changes that I made in case it helps anyone. I just need to merge that into a working initrd and compile.

Edit: I'm an idiot... Everything is linked to busybox, not /bin/busybox :P

I wiped the sbin folder except for adbd but thats already in bin so im not even sure if we need it. i dont know yet.

This is how im installing android right now. Its ugly, but it works.

Bash | #!/bin/sh fail() { echo "Failed" echo - Install-seq

The initrd gives you the option to run your own installer if you dont want to use the volume up option. It looks for a file called install-seq.sh in the andboot folder. The pastebin above is what im using for that file. Its simple, it mounts data and sys and just untars the goodies.

Also i have all the modules in androidupdate.tgz because originally i was going to untar them directly onto the system. Then i realised we would run out of space. So for now i'm dumping them to /data and then later we could mount bind it. However we should extended the /system a bit so we do have room for the modules directly in there.

Once this file is executed, the initrd renames it so it does not run the next time. I'm still missing the rest where we need to do the keyboard mapping and the other nastyness but sounds like you got that all done so now we jsut need to merge the work.

Also the sysinit.rc in xdandroid automounts the partitions so we may need to comment that out. otherwise we may need to unmount it and let android remount it. This is what may be happening with lmiller

Look for these lines and you will see what i mean .

mount yaffs2 mtd@system /system
mount yaffs2 mtd@system /system ro remount

There are other so i guess a little experimenting will help.

[[ACL]]

Originally Posted by Lmiller1708

Attached is the Log from tonight. (Had to zip it)
Same issues as before... Couple of them should be easy to solve.
But currently the modules are not getting added.
I'm going to strip down the system as much as possible to save ~15 MB.
Just to get it to load the modules and hopefully get a clean boot.

I also attached my INIT from the initrd. I left most of the stuff from the Vogue in there... Just incase...

Update: After some reading HERE, I decided to change my Command Line code to this:

mtdparts=msm_nand:0x10000000@0x0(nand)ro,0x01500000@0x04000000(root),0x07BA0000@0x05500000(system),0x06f60000@0x0CFA0000(userdata)

This gave me a larger system while keeping the data partition the same. This them allowed me to load in the modules.
I also added the "ro" at the end of the nand partition, not too sure what this does but devices with similar mtdparts cmdline have this. Basically everything but the Vogue.

Also I still can't get my System nor my Data to stick after a reboot. I thought it was just my Data but now it seems to be both. Reading back in the irc logs i see wozzer had this same issue. Might be something with the mtdparts cmdline.

nahh wozzer never got this far.. he didnt have the driver remember ..lol. nor was yaffs even enabled on the kernel. You issue i think may be android. Once android boots it goes and tries to remount everything. you need to comment those lines out in the rc file and experiment. Read my post below.

Edit: oops so it only happens after reboot? ok thats something else then. odd.. you may need to check the dmesg to see if there are errors writing to nand. Or go over your script and make sure you arent reinstalling each time.. you could be rewiping nand

also how did you handle the directory structure for the rootfs. Your init looks like it just bypassed the whole thing. did you just merge it with the initrd?

[Lmiller1708]

Originally Posted by [ACL]

nahh wozzer never got this far.. he didnt have the driver remember ..lol. nor was yaffs even enabled on the kernel. You issue i think may be android. Once android boots it goes and tries to remount everything. you need to comment those lines out in the rc file and experiment. Read my post below.

Edit: oops so it only happens after reboot? ok thats something else then. odd.. you may need to check the dmesg to see if there are errors writing to nand.

also how did you handle the directory structure for the rootfs. Your init looks like it just bypassed the whole thing. did you just merge it with the initrd?

humm... I guess I read it wrong then. Here is the link. (Look at the bottom of the page) Seems like the same problem...

I do have those line commented out in the init.

Attached is my dmesg after a reboot. It looks like my cmdline is getting reset and losing the mtdparts?

[[ACL]]

Originally Posted by Lmiller1708

humm... I guess I read it wrong then. Here is the link. (Look at the bottom of the page) Seems like the same problem...

I do have those line commented out in the init.

Attached is my dmesg after a reboot. It looks like my cmdline is getting reset and losing the mtdparts?

yeah i see your dmesg doesnt have any parts at all. but its still not the same issue as wozzer. He wasnt able to write to nand at all, so all his writes were on memory. Once reboot, bam writes get wiped. It still doesnt explain the cmd line tho. hmm.. never seen a cmd line dissapear

I need to re-create this issue. So you are 100% sure you arent rewiping tour nand right?

[Lmiller1708]

Originally Posted by [ACL]

yeah i see your dmesg doesnt have any parts at all. but its still not the same issue as wozzer. He wasnt able to write to nand at all, so all his writes were on memory. Once reboot, bam writes get wiped. It still doesnt explain the cmd line tho. hmm.. never seen a cmd line dissapear

I need to re-create this issue. So you are 100% sure you arent rewiping tour nand right?

I didn't think he had the correct drivers... But you never know sometimes.

Yes I 100% sure. It seems to change the cmdline all together to what you see? Very weird!

Does it only get read from the tinboot once?

[[ACL]]

Originally Posted by Lmiller1708

I didn't think he had the correct drivers... But you never know sometimes.

Yes I 100% sure. It seems to change the cmdline all together to what you see? Very weird!

Does it only get read from the tinboot once?

crazy weird.. i'm working on it.. thing is im still partially booting off sd since i havent figured out if im going to bypass rootfs or just try to do it directly.

nope.. reads it all the time.. think about it. our cmd line gets passed down each time we reboot.