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

[ffkip911]

SIM in or out on this??

[steveholtam]

The phone will autofill them after you save and go back into the sprint apn, but here they are anyway:
MCC = 310
MNC = 995

[ffkip911]

Originally Posted by steveholtam

The phone will autofill them after you save and go back into the sprint apn, but here they are anyway:
MCC = 310
MNC = 995

thanks dude, you rock

[anish88]

god i want to switch to nand but the 3.5mm is the only thing that is stopping me. i cant wait till we have that because i really want to wipe WinMo off my rhod400.

[[ACL]]

Originally Posted by natemcnutty

I also have no data on either FRX04 or FRX05. I've been trying different things with no luck. I had originally tried merging the changes from rootfs directly into initrd and branching things that needed to be mounted to /data. It boots up nice and fast, but it never gets past the animation screen. That animation will play until the battery dies...

So, back to where we are at present, there are a few things that I've noticed that I'd like to clean up.

First, we are still doing the mknod stuff for camera with systinit.rc that should be removed. We are now doing that through MAKEDEVS as it never worked through sysinit.rc

Second, we still do not have /system/bin/su. We used to mount --bind from /bin/su. If we want to do something similar, we will need to copy /bin/su from rootfs into data and bind mount or ln from there.

Finally, we are missing the qwerty keypad and layout files. We just need to copy those from rootfs into the androidupdate:
/system/etc/keymaps/qwerty.kcm.bin
/system/etc/keymaps/qwerty.kl

I'm still working on the modules thing. I thought I had something, but it isn't working for me right now

Yup i noticed your commit about the MKdevs (Thanks good call). I think i will make a new project so we can keep track of these files we need. sysinit.rc is the heart and soul of the boot process so it needs to be on git.

system should have its own su. This way we dont need to link anything from data. Thats what all these roots do anyways, just look at the real root for nexus one

mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
rm /system/xbin/su
rm /system/bin/su
cat /superboot/su>/system/xbin/su
chmod 4755 /system/xbin/su
cat /superboot/Superuser.apk>/system/app/Superuser.apk
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system

This is a simple fix we can actually do over adb or via recovery (whenever i finish lol ).

fu8k the querty.. ill look into that.. Sucks you still have no data. No luck enabling wifi and trying to telnet or something? lets get creative :-p

[Lmiller1708]

Originally Posted by [ACL]

Yup i noticed your commit about the MKdevs (Thanks good call). I think i will make a new project so we can keep track of these files we need. sysinit.rc is the heart and soul of the boot process so it needs to be on git.

system should have its own su. This way we dont need to link anything from data. Thats what all these roots do anyways, just look at the real root for nexus one

mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
rm /system/xbin/su
rm /system/bin/su
cat /superboot/su>/system/xbin/su
chmod 4755 /system/xbin/su
cat /superboot/Superuser.apk>/system/app/Superuser.apk
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system

This is a simple fix we can actually do over adb or via recovery (whenever i finish lol ).

fu8k the querty.. ill look into that.. Sucks you still have no data. No luck enabling wifi and trying to telnet or something? lets get creative :-p

I will try to get the superuser working tonight.

Also Nate Make sure you have etc/ppp linked to data/ppp. Then either reboot or restart your RIL. And it should pop right up.
I think this should be added to the install-seq.sh script.


Just tested my GPS and it works great. But be patient... Very patient...

[natemcnutty]

Originally Posted by Lmiller1708

I will try to get the superuser working tonight.

Also Nate Make sure you have etc/ppp linked to data/ppp. Then either reboot or restart your RIL. And it should pop right up.
I think this should be added to the install-seq.sh script.


Just tested my GPS and it works great. But be patient... Very patient...

Does it have to be /etc/ppp? Because we currently do not have /etc mounted to anything like we did on the rootfs. We could mount /data/etc /etc if we need to.

So we just need this in the install script, right?

ln -s /data/etc/ppp /system/etc/

Note that we do have a file in /system/etc/ppp that may need to move into /data/etc/ppp if we do this.

Edit: Clarification, we do not have /etc mounted during init or the install-seq.sh. I believe it gets mounted in sysinit.rc which I guess we could symlink in there for ppp.

[[ACL]]

Originally Posted by Lmiller1708

I will try to get the superuser working tonight.

Also Nate Make sure you have etc/ppp linked to data/ppp. Then either reboot or restart your RIL. And it should pop right up.
I think this should be added to the install-seq.sh script.


Just tested my GPS and it works great. But be patient... Very patient...

I was trying to be super redundant about it too. We have the initrd making the link, then we have a link already on system.

Hard for nate to do anything without adb. Poor guy man..

nate: hang in there bro.. look how far we come..lol from the good ol days

[natemcnutty]

Originally Posted by [ACL]

I was trying to be super redundant about it too. We have the initrd making the link, then we have a link already on system.

Hard for nate to do anything without adb. Poor guy man..

nate: hang in there bro.. look how far we come..lol from the good ol days

Hehe, I'm taking a look into the ssh over wifi idea. Unfortunately, that doesn't help me any at work, but at least I might be able to do something at home.

[[ACL]]

Originally Posted by natemcnutty

Does it have to be /etc/ppp? Because we currently do not have /etc mounted to anything like we did on the rootfs. We could mount /data/etc /etc if we need to.

So we just need this in the install script, right?

ln -s /data/etc/ppp /system/etc/

In reality it has to be /system/etc/ppp because that gets linked to /etc

So inside /system/etc there needs to be a link to data/ppp

Now we have this link in place. Its on the init.rc and in that tar so i dont know how its getting trashed (if it even is getting trashed)

ln -s /data/ppp /system/etc/ppp will do it.