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

    # Directory for putting things only root should see.

    mkdir /mnt/secure 0700 root root



    # Directory for staging bindmounts

    mkdir /mnt/secure/staging 0700 root root



    # Directory-target for where the secure container

    # imagefile directory will be bind-mounted

    mkdir /mnt/secure/asec  0700 root root



    # Secure container public mount points.

    mkdir /mnt/asec  0700 root system

    mount tmpfs tmpfs /mnt/asec mode=0755,gid=1000

But /mnt doesn't exist in initrd like it did in rootfs, and it isn't mounted to anything elsewhere.

fawk.. so you want to create mnt in the init ? We could always let the rc make it also. But we will need to mod the rc anyways to not RO / and let android do it. sounds risky. what u think ?

m4f1050

03-17-2011 02:28 PM

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)

I tried mount and didn't work, had to use /bin/mount but it still errored out, same error...
Failure [INSTALL_FAILED_CONTAINER_ERROR]

natemcnutty

03-17-2011 02:32 PM

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)

Quote:

Originally Posted by [ACL] (Post 2069832)

fawk.. so you want to create mnt in the init ? We could always let the rc make it also. But we will need to mod the rc anyways to not RO / and let android do it. sounds risky. what u think ?

After looking through it, it looks like rc is already making mnt. The question I have is where are those mounts being stored? I'm assuming this is going directly to memory rather than having the files stored on NAND. I was thinking we could create /mnt under either system or data. I think it needs to be rw, so data probably makes the most sense (otherwise I'd say put it in /system).

[ACL]

03-17-2011 02:40 PM

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)

Quote:

Originally Posted by natemcnutty (Post 2069835)

well the mount points are just empty directories. nothing is stored in there. Once the device is mounted, then you can save stuff. But since this is for SD, it shouldnt save anywhere on the system or data. /mnt has to be in root.

Also right now i think we mount the sdcard to /sdcard instead of the /mnt/blablha/sdcard. then link it back.

m4f1050

03-17-2011 02:41 PM

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)

Downloading 3-16 FRX5 and 3-17 files.... :)

natemcnutty

03-17-2011 02:51 PM

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)

Quote:

Originally Posted by [ACL] (Post 2069840)

well the mount points are just empty directories. nothing is stored in there. Once the device is mounted, then you can save stuff. But since this is for SD, it should save anywhere on the system or data. /mnt has to be in root.

Also right now i think we mount the sdcard to /sdcard instead of the /mnt/blablha/sdcard. then link it back.

So all we're really missing is mounting /mnt somewhere. It is created, the links are set up properly with rc, but it is never mounted to the fs somewhere so files can be stored. So, I guess we have to add it to initrd then ln -s it to somewhere else?

[ACL]

03-17-2011 02:52 PM

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)

Quote:

Originally Posted by natemcnutty (Post 2069847)

nahh, all this should be androided somewhow. Ill check the cyanongen rc tonight since they have it all setup internally.

neopeek

03-17-2011 03:14 PM

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)

Using latest 3-17 files (NBH + Rest) I got in a bootloop. Just seeing always "Waiting for Sdcard" for some milliseconds and then it reboots my Rhod300.

m4f1050

03-17-2011 03:25 PM

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)

Just installed FRX5 (3-16) and /andboot (3-17) all worked.

NOTES:

Iinstead of installing BUSYBOX from TITANIUM BACKUP I created a link from /bin/busybox to /system/bin/busybox and SU started working. :)

Code:

ln -s /bin/busybox /system/bin/busybox

I then installed BUSYBOX

Code:

mount -o rw,remount x /system

rm -R /system/bin/cat

rm -R /system/bin/df

rm -R /system/bin/ls

busybox --install -s /system/bin

I also installed su.3.6.1.whatever.it.is...apk <== Is this just to "ask" for permission? If not installed it assumes it's ok and grants SU?

[ACL]

03-17-2011 03:29 PM

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)

Quote:

Originally Posted by m4f1050 (Post 2069857)

Code:

ln -s /bin/busybox /system/bin/busybox

I then installed BUSYBOX

Code:

mount -o rw,remount x /system

rm -R /system/bin/cat

rm -R /system/bin/df

rm -R /system/bin/ls

busybox --install -s /system/bin

I also installed su.3.6.1.whatever.it.is...apk

ahh man.. sounds like you can write an android update just with your commands ..lol. good shit..

since ur able to boot. Try to get into the recovery and test the backup and restore.

All times are GMT -4. The time now is 05:45 PM.

Page 183 of 274

183

Show 40 post(s) from this thread on one page

Content Relevant URLs by vBSEO 3.6.0