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

[steveholtam]

The build two nights ago had working wi-fi. So either the system files since then have broke wi-fi or it is user error.

From my tests, I have not found a need to Task29 at all. I do quick format my sd card between tests, just to make sure I don't get any odd issues, but I have not had a single problem caused by flashing over another flash to NAND.

[Lmiller1708]

Originally Posted by steveholtam

The build two nights ago had working wi-fi. So either the system files since then have broke wi-fi or it is user error.

From my tests, I have not found a need to Task29 at all. I do quick format my sd card between tests, just to make sure I don't get any odd issues, but I have not had a single problem caused by flashing over another flash to NAND.

As ACL stated there will be something tonight.
I have only used Task29 once and it did not fix anything... So I will not use it again. Also if you format your card just once that should be good enough.
Biggest thing is that you have you are using the correct package.
Meaning the androidupdate.tar/tgz and the NBH (what you flash) come from the same place (Nate, ACL, or myself).
My androidupdate.tar had a bunch of apks added to the data/app folder, this is how the cooks will be doing it also. (For the most part)...

ACL is working on the recovery to replace the replimenu! It should be great!

@ Nate, here is my latest MTDParts:

mtdparts=msm_nand:0x400000@0x4000000(boot),0x800000@0x4400000(recovery),0x8C00000@0x4C00000(system),0x10800000@0xD800000(userdata),0x2000000@0x1E000000(cache)

[natemcnutty]

Originally Posted by Lmiller1708

As ACL stated there will be something tonight.
I have only used Task29 once and it did not fix anything... So I will not use it again. Also if you format your card just once that should be good enough.
Biggest thing is that you have you are using the correct package.
Meaning the androidupdate.tar/tgz and the NBH (what you flash) come from the same place (Nate, ACL, or myself).
My androidupdate.tar had a bunch of apks added to the data/app folder, this is how the cooks will be doing it also. (For the most part)...

ACL is working on the recovery to replace the replimenu! It should be great!

@ Nate, here is my latest MTDParts:

mtdparts=msm_nand:0x400000@0x4000000(boot),0x800000@0x4400000(recovery),0x8C00000@0x4C00000(system),0x10800000@0xD800000(userdata),0x2000000@0x1E000000(cache)

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:

#!/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:

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

[[ACL]]

Originally Posted by natemcnutty

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:

#!/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:

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

[natemcnutty]

Originally Posted by [ACL]

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

For the mtdparts I posted, I am able to format it without any issues, but I haven't attempted to write anything to the recovery partition. LMiller's recent mtdparts just replaces the nand reference size thing for a boot partition. Not really sure if we even need either really.

Cool, I just wanted to check on some of that stuff. For the keyboard crap, I'll get that taken care of when I get home.

I thought the netd script was interesting. Didn't know if it was needed or not.

I like the idea of moving it into system as /system/init and then using the recovery version in initrd. I haven't tested it, but I should

And by installer, I just meant I have a chunk of code that checks for /sdcard/andboot/androidupdate.tgz. If found, it applies it and then renames the file to androidupdate-disabled.tgz. I saw it as a way to update system or data partition files while being able to remove replimenu, but it won't help with kernel updates or anything like that.

[iiinycboi]

what time will you be releasing your new version? just wondering if i should just go ahead and flash the nand android onto my touch pro 2 now or wait for the new release with updates.

[Counterfeit]

Originally Posted by iiinycboi

what time will you be releasing your new version? just wondering if i should just go ahead and flash the nand android onto my touch pro 2 now or wait for the new release with updates.

I'm guessing wait. I'm ready to join the testing soon, won't have free time until Friday however Thanks to all involved. Very excited to try.



Sent from my MSM using Tapatalk

[steveholtam]

Looking forward to testing the new files tonight!

[ffkip911]

I completely agree with the gods here on the noob-flashing. I've been flashing for 3 years but android different than WM....unlike wm where you can say "keyboard is no worky" that really doesnt help the gods out too much. I've come to the conclusion (withing 5 min of a successful flash) to keep my mouth shut because I have no idea what I'd be talking about anyway----bogs down the thread, and keeps the gods answering questions instead of fixing problems.
Like I said, been around the block a while, but I am not qualified to test and report----therefor, I'll just watch and read

[steveholtam]

Up and running on all of the new files. Still no data. Logs coming soon.