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

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

[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

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

[[ACL]]

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.

I tried ES explorer for root but its asking for a specific rom (cyano or some other crap). lol

The request for 'root' is a real hack in android. It doesnt work like you think. Most devs try to write to a section they arent allowed to to cause the superuser apk request to pop up and allow it. Thats it..lol. They dont have the power to go to the shell and execute, its all done internally. they dont select the user to run as. Haret runs wide open. They dont have ro set for any partitions. If you want to run the same way, just mount rw for everything in your initrd. Also reorder your path so where ever you have busybox installed is first.

installed angrybirds with no issues.. so i'll leave it up to you gents to figure it out. If i cant replicate, i cant fix . I'll try a fresh install instead of my restored data to test further. Also for spare parts and all that stuff, make an update.tgz and lets put it up. Simple enough to do so. I dont want to included it in the rom itself since.

I was thinking more about this direct conversion from the img and realized that the fixperms script will never run since its not there. Not sure if this is gonna work out well in the long run. God knows what they will change forcing us to update the script.. At this stage its easy enough to update the recovery we do have a work around.

[Lmiller1708]

Originally Posted by [ACL]

I tried ES explorer for root but its asking for a specific rom (cyano or some other crap). lol

The request for 'root' is a real hack in android. It doesnt work like you think. Most devs try to write to a section they arent allowed to to cause the superuser apk request to pop up and allow it. Thats it..lol. They dont have the power to go to the shell and execute, its all done internally. they dont select the user to run as. Haret runs wide open. They dont have ro set for any partitions. If you want to run the same way, just mount rw for everything in your initrd. Also reorder your path so where ever you have busybox installed is first.

installed angrybirds with no issues.. so i'll leave it up to you gents to figure it out. If i cant replicate, i cant fix . I'll try a fresh install instead of my restored data to test further. Also for spare parts and all that stuff, make an update.tgz and lets put it up. Simple enough to do so. I dont want to included it in the rom itself since.

I was thinking more about this direct conversion from the img and realized that the fixperms script will never run since its not there. Not sure if this is gonna work out well in the long run. God knows what they will change forcing us to update the script.. At this stage its easy enough to update the recovery we do have a work around.

Could not agree more about the keys and no home button! Never made sense to my why they changed it... The less haret stuff the better.

Humm... Not sure why angerybirds would install for you...
I have installed the most recent autobuild with no success in getting the modules to load.

I was able to get the 3.4 version of squashfs working. What I had to do was install I the zlib (apt-get install zlib1g)

I also notice that the SDCard does not mount. I have to pull it out and then reinsert it for it to mount... After that it does not even show up in the settings/SDcard.