Need help renaming Partitions in Dual Boot kernel!! Please Help!!

mknod /dev/block/mmcblk0p13 b 179 9
mknod /dev/block/mmcblk0p16 b 179 12

Click to expand...

Click to collapse

“I have edited all the files in the ramfs, apart from two files.
In the files /sbin/init and /sbin/ueventd the is 2 partitions referenced thru out them, they are:
mknod /dev/block/mmcblk0p13 b 179 9
mknod /dev/block/mmcblk0p16 b 179 12v
On the Galaxy S3, thoses partition names are un-used (as far as i know)
But on the Galaxy Note 2, thoses partitions are the /DATA and /SYSTEM partitions.
can i just change the partition names in thoses 2 files to soemthing like:
mknod /dev/block/mmcblk0p17 b 179 9
mknod /dev/block/mmcblk0p18 b 179 12v
or do i need to do something else to rename thoses two partitions?.”

Click to expand...

Click to collapse

“block devices are created using the major and minor id's specific to your device (those do not change normally but you need to check anyway). so if they are mounted and needed you create them. if they are not needed in the script you don't have to create them. you have to try to keep the same functionality in the script. if you mount /system then you will need the block device that corresponds to /system with the correct major and minor numbers.”

Click to expand...

Click to collapse

#!/sbin/busybox sh
cd /

busybox mount -t proc proc /proc
busybox mount -t sysfs sysfs /sys

if busybox grep -q 1 /sys/class/power_supply/battery/batt_lp_charging ; then
# low power mode
echo 0 > /proc/sys/kernel/rom_feature_set
cp -a /res/misc/init.41/* /
chmod 755 /innt
chmod 644 /*.rc
chmod 644 /*.prop
exec /sbin/init2
fi

SECONDROM=1
NOBOOTLOGO=0
mkdir -p /dev/block
mkdir /dev/input
mkdir /dev/graphics
mknod /dev/graphics/fb0 c 29 0
mknod /dev/input/event1 c 13 65
mknod /dev/input/event2 c 13 66
mknod /dev/input/event8 c 13 72
mknod /dev/input/event9 c 13 73
mknod /dev/ashmem c 10 60
mknod /dev/block/mmcblk0p13 b 179 9
mknod /dev/block/mmcblk0p16 b 179 12
mknod /dev/block/loop0 b 7 0

mkdir /mnt
chmod 755 /mnt
mkdir /.secondrom
mount -t ext4 /dev/block/mmcblk0p16 /.secondrom

NEXTBOOT=`cat /.secondrom/media/.nextboot`
rm -f /.secondrom/media/.nextboot
DEFAULTROM=`cat /.secondrom/media/.defaultrom`

if grep -q bootmode=2 /proc/cmdline ; then
NEXTBOOT=0
fi

if [ "$NEXTBOOT" == "0" ]; then
mv -f /res/etc /
umount /.secondrom
echo 0 > /proc/sys/kernel/rom_feature_set
mv -f /res/misc/init.41/* /
mv -f /res/misc/recovery/* /
chmod 755 /innt
chmod 644 /*.smdk4x12
chmod 644 /*.rc
chmod 644 /*.prop
chmod -R 755 /lib
exec /sbin/init2
fi

SECONDROM=1
NOBOOTLOGO=0
[ -f /.secondrom/media/.secondrom/system.img ] || SECONDROM=0
[ -f /.secondrom/media/.nobootlogo ] && NOBOOTLOGO=1

if [ "$SECONDROM" == "0" ];then
if [ "$NOBOOTLOGO" == "0" ];then
/sbin/choose_rom $SECONDROM
fi
else
if [ "$NEXTBOOT" == "1" ];then
SECONDROM=0;
elif [ "$NEXTBOOT" == "2" ];then
SECONDROM=1;
else
if [ "$NOBOOTLOGO" == "1" ];then
SECONDROM=$DEFAULTROM
elif [ "$DEFAULTROM" == "1" ];then
/sbin/choose_rom $SECONDROM
if [ "$?" == "1" ]; then
SECONDROM=0
else
SECONDROM=1
fi
else
/sbin/choose_rom $SECONDROM
if [ "$?" == "1" ]; then
SECONDROM=1
else
SECONDROM=0
fi
fi
fi
fi

if [ "$SECONDROM" == "1" ]; then
mount -t ext4 /.secondrom/media/.secondrom/system.img /system
else
mount -t ext4 /dev/block/mmcblk0p13 /system
fi


AOSP=0
MIUI=0
CM10=0
JB=0

[ -f /system/framework/framework2.jar ] || AOSP=1
[ -f /system/framework/miui-framework.jar ] && MIUI=1
[ -f /system/lib/ssl/engines/libkeystore.so ] && JB=1
[ -f /system/framework/seccamera.jar ] || CM10=1

if [ "$JB" == 1 ];
then
if [ "$CM10" == 1 ];
then
echo 3 > /proc/sys/kernel/rom_feature_set
mv -f /lib/modules/dhd_cm.ko /lib/modules/dhd.ko
mv -f /res/misc/init.cm10/* /
else
echo 2 > /proc/sys/kernel/rom_feature_set
mv -f /res/misc/init.41/* /
fi
fi

if [ "$SECONDROM" == "1" ];then
mv /init.smdk4x12.rc.2 /init.smdk4x12.rc
mv /init.rc.2 /init.rc
mv /fstab.smdk4x12.2 /fstab.smdk4x12
else
rm -f /init.rc.2 /init.smdk4x12.rc.2 /fstab.smdk4x12.2
fi

umount -f /system
umount -f /.secondrom

rm -rf /res/misc/init*
chmod 755 /innt
chmod 644 /*.smdk4x12
chmod 644 /*.rc
chmod 644 /*.prop
chmod -R 755 /lib

# misc mods for i9300
insmod /lib/modules/m0_mods.ko
# cpu undervolting interfaces
insmod /lib/modules/cpu_undervolting.ko
# mali (gpu) interfaces
insmod /lib/modules/mali_control.ko
# additional CPU governors
insmod /lib/modules/cpufreq_hotplug.ko
insmod /lib/modules/cpufreq_lulzactiveq.ko
# additional I/O schedulers
insmod /lib/modules/sio-iosched.ko
insmod /lib/modules/vr-iosched.ko
# audio enhancements
insmod /lib/modules/kscoobydoo.ko devicename=scoobydoo_sound

exec /sbin/init2

Click to expand...

Click to collapse

PARTITION: ` Galaxy S3 Galaxy Note 2
/BOOT mmcblk0p5 mmcblk0p8
/BOTA0 mmcblk0p1 mmcblk0p1
/BOTA1 mmcblk0p2 mmcblk0p2
/CACHE mmcblk0p8 mmcblk0p12
/EFS mmcblk0p3 mmcblk0p3
/HIDDEN mmcblk0p10 mmcblk0p14
/OTA mmcblk0p11 mmcblk0p15
/PARAM mmcblk0p4 mmcblk0p7
/RADIO mmcblk0p7 mmcblk0p10
/RECOVERY mmcblk0p6 mmcblk0p9
/SYSTEM mmcblk0p9 mmcblk0p13
/TOMBSTONES unknown mmcblk0p11
/USERDATA mmcblk0p12 mmcblk0p16

Click to expand...

Click to collapse

sda.171 said:

Any success bro? Lot of people looking forward to this !

Click to expand...

Click to collapse

fishingfon said:

Hi,
Yes i didnt think of that, i will try that later.
Thanks

Corey






Hi,
Yes I found out what the contents of choose_ROM is, and its a symbolic link to busy box.
But I can't find anything wrong with the choose ROM thing ect.

I fixed the first problem of not being able to select the second ROM on boot, but now I have a new problem.
When I boot The phone up, with the value of 2 in .nextboot, and select the second ROM, the second ROM trys to boot, but it freezes as soon as I select the second ROM.

I am thinking something might be wrong with my second system.img
Cos I created a 1gb ext4 system img, and placed it in /data/media/.secondrom
But when I clone the second ROM to it, instead of using the 1gb of space already created, it seems to try and expand the system img, so if I clone a 500mb ROM to the IMG the system IMG will expand to 1.5gb.

I know the second system.img is getting mounted, cos if I leave the img empty, the phone will loop on the choose rom screen, but if I put a system.img with a cloned rom, the choose ROM screen freezes when it trys to boot the second rom.
I really need someone with a s3 to install a n2 ROM with the s3 update script etc as there second rom, and then send me the system.IMG but I can't seem to find anyone

Cheers
Corey



Sent from my GT-N7100

If I helped you, please hit Thanks..

Click to expand...

Click to collapse

zacharysblubaugh said:

Ok the last 5-10 post are very confusing....do I understand right that you have dualboot working

It was easier for me to understand the code you was posting and my development skills are limited to mainly apps

Sent from my GT-N7100 using xda app-developers app

Click to expand...

Click to collapse