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

[Lmiller1708]

Wirelessly posted (TP2: Mozilla/5.0 (Linux; U; Android 2.2.2; en-us; MSM Build/FRX05) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1)

Originally Posted by natemcnutty

Was getting an invalid mount, so I committed loop3 thinking that would fix it. Then got another error that it was an invalid argument. Finally figured out that I simply did sudo apt-get install squashfs-tools and ended up with v4, not 3.4...

Anyway, I did get system.ext2 loop mount off sdcard then cp -a everything over to /system working perfectly. I tried using dd to do a low level copy of everything, but that failed on me for some reason. I'll commit that change to the script in recovery shortly.

Thanks nate!
I didn't even get time to work on it yesterday...
Going to redo my VM today, I did a snapshot so I will try that frist...

What problems are you having with FRXO6? Just not able to get it to boot at all? Did you try mine?

[[ACL]]

i think its safe to say the recovery is 'stable'.

With that said im thinking of releasing the next kernel updates via update.tgz. This way no wipe is needed until the next major release. But since we can back up and restore with no probs now this isnt going to be a big issue.

Im tacking some bugs so there will be plenty of updates.

[natemcnutty]

Originally Posted by [ACL]

i think its safe to say the recovery is 'stable'.

With that said im thinking of releasing the next kernel updates via update.tgz. This way no wipe is needed until the next major release. But since we can back up and restore with no probs now this isnt going to be a big issue.

Im tacking some bugs so there will be plenty of updates.

Yeah, recovery has been perfect for me since your first release. I'm loving it

I'll definitely test out your kernel release via update.tgz. Probably good to get that ironed out early.

Also, there are still a handful of issues with the ROM's that I think we need to find some chef help on. Maybe stinebd might have some ideas on some of this too. I believe all of these are just ROM related things that should be fixable by someone who knows what they are doing:

1) We still don't have real root (despite having su and busybox in /system/bin and /system/xbin)
2) Data never works on first boot
3) App2sd doesn't work (may be root related)
4) Some applications refuse to install (but work on Haret)

[[ACL]]

Originally Posted by natemcnutty

Yeah, recovery has been perfect for me since your first release. I'm loving it

I'll definitely test out your kernel release via update.tgz. Probably good to get that ironed out early.

Also, there are still a handful of issues with the ROM's that I think we need to find some chef help on. Maybe stinebd might have some ideas on some of this too. I believe all of these are just ROM related things that should be fixable by someone who knows what they are doing:

1) We still don't have real root (despite having su and busybox in /system/bin and /system/xbin)
2) Data never works on first boot
3) App2sd doesn't work (may be root related)
4) Some applications refuse to install (but work on Haret)

1) hmm something isnt right with your setup bro. I swear to you i have the root apk, the busybox 1.9 and titanum backup installed. I did notice one of the apks to install busybox requests to mount /system as rw, but the other one does it for you. So try a few out.

2) data on first is worth a look. But since im restoring from my old backup, im never really firsr booting ..lol

3) that i have not tested. Will do tonight

4) need specifics. Each app writes to logcat as to why they cant install. Some even give you a list of things to fix

[Lmiller1708]

Originally Posted by [ACL]

1) hmm something isnt right with your setup bro. I swear to you i have the root apk, the busybox 1.9 and titanum backup installed. I did notice one of the apks to install busybox requests to mount /system as rw, but the other one does it for you. So try a few out.

2) data on first is worth a look. But since im restoring from my old backup, im never really firsr booting ..lol

3) that i have not tested. Will do tonight

4) need specifics. Each app writes to logcat as to why they cant install. Some even give you a list of things to fix

1) I'm also using the same setup at ACL. Works just fine Superuser.apk, dl from the market. The Vogue also has to use this...

2) Same issue for me... (On Last Install)

3) Untested too..

4) *birds will not install for me... Only SD app I have tried.


This should also be added the install-seq.sh:

# Fix build.prop for NAND
sed -i 's/lib\/froyo/system\/lib/' /system/build.prop
sed -i 's/210/240/' /system/build.prop

# Remove system/etc/ppp folder...
rm -R system/etc/ppp

[natemcnutty]

Originally Posted by Lmiller1708

1) I'm also using the same setup at ACL. Works just fine Superuser.apk, dl from the market. The Vogue also has to use this...

2) Same issue for me... (On Last Install)

3) Untested too..

4) *birds will not install for me... Only SD app I have tried.


This should also be added the install-seq.sh:

# Fix build.prop for NAND
sed -i 's/lib\/froyo/system\/lib/' /system/build.prop
sed -i 's/210/240/' /system/build.prop

# Remove system/etc/ppp folder...
rm -R system/etc/ppp

Yeah, so the root is weird. What I mean by a real root is that on first boot, I log into Market, install Titanium Backup, and it tells me I don't have root. I then install Busybox and Titanium is happy, but other programs like ES File Explorer won't let me run as root. Terminal says unknown uid when I type busybox whoami, but it does let me su, then issue commands which works properly.

Haret users don't have to do anything like this, so that's why I'm wondering what we need to do to clean up the ROM. Also, I'm thinking we should toss spare parts into the ROM like Haret used to unless we want to change the value for the End key. Having no Home button is extremely annoying.

As for the install-seq.sh, that is almost the same code as what I had when I was trying to fix up FRX06. I used @ symbols, but I like yours better. For the 210 to 240, I think we should add a little more to that so we don't mess up build values or anything like that.

[Lmiller1708]

Originally Posted by natemcnutty

Yeah, so the root is weird. What I mean by a real root is that on first boot, I log into Market, install Titanium Backup, and it tells me I don't have root. I then install Busybox and Titanium is happy, but other programs like ES File Explorer won't let me run as root. Terminal says unknown uid when I type busybox whoami, but it does let me su, then issue commands which works properly.

Haret users don't have to do anything like this, so that's why I'm wondering what we need to do to clean up the ROM. Also, I'm thinking we should toss spare parts into the ROM like Haret used to unless we want to change the value for the End key. Having no Home button is extremely annoying.

As for the install-seq.sh, that is almost the same code as what I had when I was trying to fix up FRX06. I used @ symbols, but I like yours better. For the 210 to 240, I think we should add a little more to that so we don't mess up build values or anything like that.

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

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

[[ACL]]

Originally Posted by natemcnutty

As for the install-seq.sh, that is almost the same code as what I had when I was trying to fix up FRX06. I used @ symbols, but I like yours better. For the 210 to 240, I think we should add a little more to that so we don't mess up build values or anything like that.

lets wait on this commit. Lmiller and i talked about having a custom script per update like android. So if anything the update-seq script needs to be modded to check for a pre-exec script and a post-exec. This way we can have custom scripts when needed anytime we have an update instead of recompiling all the time.

android does it the say way but with only one script.