View Single Post
  #1595 (permalink)  
Old 03-09-2011, 09:33 PM
[ACL]'s Avatar
[ACL]
VIP Member
Offline
Location: NY
 
Join Date: Feb 2010
Posts: 1,534
Reputation: 6350
[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community
Mentioned: 2 Post(s)
Tagged: 0 Thread(s)
Re: NAND Boot Testing - 03-08: Full NAND FRX05 Testing (Data not working for some)

Quote:
Originally Posted by natemcnutty View Post
I guess I'll wait until you guys release whatever you are working on. I have a ton of changes that I need to make, but I don't want to overwrite any work

Just a short list of things I noticed:
1) In sysinit.rc, we changed netd from /bin/netd to /system/bin/netd. /bin/netd was a script that we may need to run:
Code:
#!/bin/sh

modprobe ipt_MASQUERADE
modprobe xt_state
modprobe xt_multiport
modprobe iptable_filter
modprobe iptable_nat

/system/bin/netd
2) In initrd, there were no adverse reactions to adding ueventd to /sbin, adding ueventd.rc to root, and changing out init.android for the one from our rootfs. I think it might be a good idea to use an init.android that we know the origin of.

3) I discovered that the qwerty.kcm.bin actually just pointed to microp-keypad.kcm.bin and qwerty.kl pointed to raph_navi_pad.kl. We can just copy the appropriate kl over as qwerty.kl to fix it. I fixed that code in my install-seq.sh

4) I was able to successfully format recovery and mount it and all that using this mtdparts:
Code:
mtdparts=msm_nand:0x20000000@0x0(nand),0x800000@0x8000000(recovery),0x0A000000@0x8800000(system),0xB800000@0x12800000(userdata),0x2000000@0x1E000000(cache)
5) I also made a bunch of changes to create our own installer replacing the replimenu, but I'll see what you guys have first
Lets agree on the mtd parts. Did you fully test this? My mtd parts loads and formats but its broken but i havent tested Lmillers yet since he added a new partition. I guess we could always just ignore that partition and load recovery on that specific offset.

yes please commit that kb bullsh*t on the install script on git . i saw a cp in there but i guess i forgot where the files were. I'll pull them from rootfs for autobuild.

That netd script is useless since all modules need to be loaded by android and not scripts. So dont commit that and see if the init.rc can load the modules for you on boot. Or maybe the modules are already loaded. That looks like a haretized script to me.

For the init.android. We need to just include them in /system. The initrd will check for it and load it if its named "init" (which is the official name). So for frx05, lets included it in there and i'll try to see where i can get the frx4 version. If you have them, then put em up so i can upload them.

This way we can also remove the init.android inside initrd and have the recovery version (which has its own) for more flexibility.

own installer ? ooo.. i was going to use the recovery but if you have something better then share please ..
__________________
Reply With Quote
This post has been thanked 2 times.