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

[natemcnutty]

Originally Posted by Lmiller1708

Yeah I was thinking about doing the same thing for the 210 to 240 version...
I will leave it up to you.

Cool, I'll get that code committed when I get home today and have a chance to test it one more time.

Also, anyone care to try this out for root?

rm /system/xbin/su
ln -s /system/bin/su /system/xbin/su

[Lmiller1708]

Originally Posted by natemcnutty

Cool, I'll get that code committed when I get home today and have a chance to test it one more time.

Also, anyone care to try this out for root?

rm /system/xbin/su
ln -s /system/bin/su /system/xbin/su

Ok Thanks!

It should not matter if the su is in the xbin or system... or even linked... Since the path includes them both.

[natemcnutty]

Originally Posted by Lmiller1708

Ok Thanks!

It should not matter if the su is in the xbin or system... or even linked... Since the path includes them both.

Ahh, I was thinking /system/xbin was before /system/bin in the PATH, and the su in /system/xbin isn't the right one. Guess it really doesn't matter, but I noticed that was a common theme in most root programs and thought it might fix some of the issues. Guess not :P

I guess all we really need to do is copy su and busybox from /bin to /system/bin during the first time script.

I agree with ACL that we should move anything ROM related out of the install-seq.sh and move it into the scripts that are run on the ROM's first launch. Any ideas or commits you have for that, let me know

[Lmiller1708]

Originally Posted by natemcnutty

Ahh, I was thinking /system/xbin was before /system/bin in the PATH, and the su in /system/xbin isn't the right one. Guess it really doesn't matter, but I noticed that was a common theme in most root programs and thought it might fix some of the issues. Guess not :P

I guess all we really need to do is copy su and busybox from /bin to /system/bin during the first time script.

I agree with ACL that we should move anything ROM related out of the install-seq.sh and move it into the scripts that are run on the ROM's first launch. Any ideas or commits you have for that, let me know

Just used the system.ext2 method with FRX06 and it worked great!
Booted up with no issues except data... Here is my log: 03-29 22:19:37.280: INFO/DEBUG(173): debuggerd: Mar 1 2011 18:59:25 03-29 22:1 - Pastebin.com

For the install-seq.sh:

sed -i 's/ro.sf.lcd_density = 210/ro.sf.lcd_density = 240/' /system/build.prop

EDIT: No data on second boot either... My modules are not loaded...
Still looking at it...

But I do not like the new keylayout! How can I get back to the other? Thanks!!!


EDIT2:
I get a invalid arg with this command: mount -t squashfs -o ro,relatime /dev/block/loop3 /system/lib/modules

[natemcnutty]

Originally Posted by Lmiller1708

Just used the system.ext2 method with FRX06 and it worked great!
Booted up with no issues except data... Here is my log: 03-29 22:19:37.280: INFO/DEBUG(173): debuggerd: Mar 1 2011 18:59:25 03-29 22:1 - Pastebin.com

For the install-seq.sh:

sed -i 's/ro.sf.lcd_density = 210/ro.sf.lcd_density = 240/' /system/build.prop

EDIT: No data on second boot either... My modules are not loaded...
Still looking at it...

But I do not like the new keylayout! How can I get back to the other? Thanks!!!


EDIT2:
I get a invalid arg with this command: mount -t squashfs -o ro,relatime /dev/block/loop3 /system/lib/modules

For the first part, I see this in your log, and later on it says the radio is disabled. I don't know enough to explain why, but that's what sticks out to me.

03-29 22:23:37.770: INFO//system/bin/tc(172): Cannot find device "rmnet0"
03-29 22:23:37.770: INFO/logwrapper(172): /system/bin/tc terminated by exit(1)
03-29 22:23:37.780: INFO/ActivityManager(219): Force stopping package com.android.provision uid=10040
03-29 22:23:37.800: INFO/Process(219): Sending signal. PID: 419 SIG: 9
03-29 22:23:37.890:  INFO/ActivityManager(219): Starting activity: Intent {  act=android.intent.action.MAIN cat=[android.intent.category.HOME]  flg=0x10000000 cmp=com.android.launcher/com.android.launcher2.Launcher }
03-29 22:23:37.910: INFO//system/bin/tc(172): Cannot find device "rmnet0"

For keylayout, you can try modifying the rhod400 navipad file and flip the power/home buttons. If that doesn't work, you may have to make the adjustment in the kernel's gpiokeys and then comment out the navipad part.

Finally, the squashfs issue is because you probbaly used squashfs-tools from apt-get which installs version 4. You have to go to their site, grab 3.4, unzip, then go to the squashfs-tools folder, do MAKE, then sudo MAKE INSTALL. Get the 3.4 version here: Official Squashfs LZMA

[Lmiller1708]

Originally Posted by natemcnutty

For the first part, I see this in your log, and later on it says the radio is disabled. I don't know enough to explain why, but that's what sticks out to me.

03-29 22:23:37.770: INFO//system/bin/tc(172): Cannot find device "rmnet0"
03-29 22:23:37.770: INFO/logwrapper(172): /system/bin/tc terminated by exit(1)
03-29 22:23:37.780: INFO/ActivityManager(219): Force stopping package com.android.provision uid=10040
03-29 22:23:37.800: INFO/Process(219): Sending signal. PID: 419 SIG: 9
03-29 22:23:37.890:  INFO/ActivityManager(219): Starting activity: Intent {  act=android.intent.action.MAIN cat=[android.intent.category.HOME]  flg=0x10000000 cmp=com.android.launcher/com.android.launcher2.Launcher }
03-29 22:23:37.910: INFO//system/bin/tc(172): Cannot find device "rmnet0"

For keylayout, you can try modifying the rhod400 navipad file and flip the power/home buttons. If that doesn't work, you may have to make the adjustment in the kernel's gpiokeys and then comment out the navipad part.

Finally, the squashfs issue is because you probbaly used squashfs-tools from apt-get which installs version 4. You have to go to their site, grab 3.4, unzip, then go to the squashfs-tools folder, do MAKE, then sudo MAKE INSTALL. Get the 3.4 version here: Official Squashfs LZMA

Ahh... Could not get the 3.4 version installed? When I do a make I get can't find the zlib.h file...

Also I grabbed the squash file from the autobuild and have it mounted...
But when I do a depmod I get: depmod: chdir:2.6.27.46-01268-ga175a7c: No such file or directory

Any Idea?

[pts69666]

Sorry for the late response; however reflashing the radio fixed my data issues. I don't know if the radio was corrupted or if it was just bad luck on my part. Just sharing experiences!