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

[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!

[[ACL]]

Index of /files/xdandroid/

This has the rc in there like the initrd expects it (sysinit.rc)

also i think i moved all the libs there .. forgot.

also you need to rename it :-p

[Lmiller1708]

Originally Posted by [ACL]

Index of /files/xdandroid/

This has the rc in there like the initrd expects it (sysinit.rc)

also i think i moved all the libs there .. forgot.

also you need to rename it :-p

Thanks ACL, I'm able to mount it this way. What command did you use to tar it? Here is what I was using...

tar -cvzf androidinstall.tar androidinstall/

Also I can't seem to get my data to stick after a reboot, any Ideas?
I was able to get Android to boot with the basic init from the Vogue, but a lot did not work correctly. I have added the code to the init that Nate posted above and some from the rootfs along with some files but I haven't yet got past the boot screen... Still crossing my fingers though...

EDIT: Maybe this for the androidinstall (inside the folder of course)

tar -cvzf ../androidinstall.tar *

Update: Was able to get it to boot to Andorid, touch screen and buttons all work. But I have no service and it will reboot after ~45 seconds.

[[ACL]]

Originally Posted by Lmiller1708

Thanks ACL, I'm able to mount it this way. What command did you use to tar it? Here is what I was using...

tar -cvzf androidinstall.tar androidinstall/

Also I can't seem to get my data to stick after a reboot, any Ideas?
I was able to get Android to boot with the basic init from the Vogue, but a lot did not work correctly. I have added the code to the init that Nate posted above and some from the rootfs along with some files but I haven't yet got past the boot screen... Still crossing my fingers though...

EDIT: Maybe this for the androidinstall (inside the folder of course)

tar -cvzf ../androidinstall.tar *

Update: Was able to get it to boot to Andorid, touch screen and buttons all work. But I have no service and it will reboot after ~45 seconds.

i think you are ahead of me. Ive yet to boot fully off nand. I'm still partially going through the sdcard for the rootfs part.

The initrd from the vogue is good but has to be modded alot still. the /bin/MAKEDEVS needs to be examined because i'm not sure if that matches what we need.

Also the whole setup modem part can be ignored for now.

if you got some logs about the crash, that would help

[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)

Sounds good! I will post some logs in a bit. Was able to get them from the droid explorer.
Any idea why the data isn't sticking?

[[ACL]]

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)

Sounds good! I will post some logs in a bit. Was able to get them from the droid explorer.
Any idea why the data isn't sticking?

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

[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

]

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

Nope sorry. Haven't gotten that far yet!
Data as in \data on mtd3.
My system sticks and I can remount it just fine, but data just doesn't... Might be a bit on the logs though, won't be by my laptop for a while.

[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

[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.