[Q] Unpacking otter2 CyanogenMod initramfs

[spudowiar]

OK that is very odd, I never asked hashcode the number for otter2's, I assumed it was the same. Weird.

Sent from my Amazon Kindle Fire HD using Tapatalk[/QUOT

 

[spudowiar]

OK that is very odd, I never asked hashcode the number for otter2's, I assumed it was the same. Weird.

Sent from my Amazon Kindle Fire HD using Tapatalk

It was trial and error (with powers of 2).

 

[spudowiar]

The progress

Upload rootfs-20140411.tar.gz to /sdcard

adb shell
su
busybox mount -o remount,suid,dev /data
busybox rm -rf /data/rootfs
mkdir /data/rootfs
cd /data/rootfs
busybox tar zxvpf /data/media/rootfs-20140411.tar.gz
stop
cd /data/media
busybox nohup cat /proc/kmsg &
cd /data/rootfs
busybox nohup busybox chroot /data/rootfs /init &

adb will disconnect but on the screen it should say

A N D R O I D _

Then it will power off (it tries to reboot into recovery). Power it on.

adb shell
su
chmod 777 /data/media/nohup.out
exit
exit

Then run:

adb pull /sdcard/nohup.out log.txt

log.txt is the dmesg.

 

[stunts513]

Upload rootfs-20140411.tar.gz to /sdcard

adb shell
su
busybox mount -o remount,suid,dev /data
busybox rm -rf /data/rootfs
mkdir /data/rootfs
cd /data/rootfs
busybox tar zxvpf /data/media/rootfs-20140411.tar.gz
stop
cd /data/media
busybox nohup cat /proc/kmsg &
cd /data/rootfs
busybox nohup busybox chroot /data/rootfs /init &

adb will disconnect but on the screen it should say

A N D R O I D _

Then it will power off (it tries to reboot into recovery). Power it on.

adb shell
su
chmod 777 /data/media/nohup.out
exit
exit

Then run:

adb pull /sdcard/nohup.out log.txt

log.txt is the dmesg.

oh thats wonderful, 2 imports failed, couldn't access a selinux directory, and the system process (zygote) is committing suicide, lovely...

 

[spudowiar]

oh thats wonderful, 2 imports failed, couldn't access a selinux directory, and the system process (zygote) is committing suicide, lovely...

The imports and selinux don't actually matter but the suicide... I think we need DCI Hashcode!

EDIT: I think I've got it: it looks for init.omap4blazeboard.rc, we've got init.omap4430.rc!

 

[spudowiar]

The imports and selinux don't actually matter but the suicide... I think we need DCI Hashcode!

EDIT: I think I've got it: it looks for init.omap4blazeboard.rc, we've got init.omap4430.rc!

Looking at the log after

mv init.omap4430.rc init.omap4blazeboard.rc

a chroot is gonna need a lot of work!

EDIT: You remember what I said about modules? Lots of errors!!!

 

[stunts513]

Looking at the log after

mv init.omap4430.rc init.omap4blazeboard.rc

a chroot is gonna need a lot of work!

EDIT: You remember what I said about modules? Lots of errors!!!

good to see this is making process, and just for the record hashcode is back from vacation in the irc.

 

[spudowiar]

good to see this is making process, and just for the record hashcode is back from vacation in the irc.

Nice! Anyway, let's move into development threads...