Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,772,571 Members 51,313 Now Online
XDA Developers Android and Mobile Development Forum

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

Tip us?
 
fishingfon
Old
(Last edited by fishingfon; 20th December 2012 at 12:13 PM.)
#1  
fishingfon's Avatar
Senior Member - OP
Thanks Meter 253
Posts: 712
Join Date: Feb 2012
Location: Brisbane, QLD, Australia
Default Need help renaming Partitions in Dual Boot kernel!! Please Help!!

Hi all,

I am in the process of porting the dual boot ramfs from the Galaxy S3 Siyah kernel to our Note II smartphones.

I have finished editing the ramfs, and changing the init files ect.
But the is still two files I have left to edit, and I am a bit stuck on them.

In the files /sbin/init and /sbin/ueventd the is quite a few references to theses partitions:





Quote:
mknod /dev/block/mmcblk0p13 b 179 9
mknod /dev/block/mmcblk0p16 b 179 12
the problem is this, on the Galaxy S3 (which is what that ramfs was designed for) those partitions dont exist as far as I can see.
But on the note 2, those partitions are the /DATA and /SYSTEM partitions.

So I need to change thoses partitions to something else, but I dont know what.
I have copied the contents of the two files which thoses partitions are referenced in, and a table showing the Note 2 partitions and the coresponing S3 partitions, below

Could someone please help me find out what I should do here, as I cant do any more on the dual boot kernel till I get that sorted.

Here is the question I asked gokhan moral:





Quote:
“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?.”
And here is Gokhan Morals Response:





Quote:
“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.”
but I still dont understand what I am supposed to do (I am not really a developer, I am more of a web designer ect)


Could someone please explain in simpler steps what I should do to rename thoses two partitions.



Here are the file contents (both files have the same contents, so i have only copied one here)

INIT:





Quote:
#!/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

And here is the partition layouts:





Quote:
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
I think i copied thoses partitions right from my pc, but i may have got one mixed up or something



Please can someone help, as i have been searching for days, and asking lots of different people on xda, but no response

Thanks in advance

Cheers
Corey
My Current Devices:
Galaxy Note II N7100
HTC 8x Windows Phone 8
Samsung Galaxy S2 I9100
Nexus 7


The Following 6 Users Say Thank You to fishingfon For This Useful Post: [ Click to Expand ]
 
garyd9
Old
#2  
garyd9's Avatar
Recognized Developer
Thanks Meter 1976
Posts: 1,951
Join Date: Sep 2006
Location: Pittsburgh, PA
First, if "herbew" is a friend of yours, please ask him to never send me a PM asking me to help someone ELSE. That's just spam.

On the i9300 (and Note2) devices, I'm surprised to see any calls at all to mknod. Most of the device files are created automatically these days. However, I'm NOT familiar with Gokhan's dual boot thing (I've never used it and I don't have an i9300 anymore to tinker with it.) I'm assuming that you'd like to reverse engineer what Gokhan has done and it's often more fun to work backwards than to just nag him until he helps. So, I can't answer how to make it work, but I might be able to help you to reverse engineer or understand what is going on.

To find out more about your device nodes for mmcblk devices, you can run the following command (rooted, of course):
Code:
ls -l /dev/block/mmc*
The output will contain several lines similar to:
Code:
brw-rw----    1 system   root      179,   7 Dec 18 22:28 mmcblk0p7
In this case, the device major id is 179 and the minor id is 7. To see what those major ID's are, run "cat /proc/devices". (This doesn't show ALL device ID's used by the system, but covers most of them.) Another way to see all the partitions within the system is "cat /proc/partitions".

Doing the above on a i9300 both with and without the dual boot stuff might give some hints as to what changes the dualboot thing is making. You might also consider taking a look at whatever is used to install that dualboot stuff. Is it ONLY a kernel, or something more? Is it re-partitioning the device?

From what I could see of that init file, p16 is a partition used to store the secondary boot related flags and a system image. p13 appears to be the "primary" /system image partition.

Some questions to ask yourself:

What is the /system partition on a normal (non-dualboot) i9300? Is it p13 or something else? Does p16 exist in /proc/partitions on a non-dualboot system? In that non-dual boot setup, is there ANY device with a major of 179 and minor of 12? (My first thought would be it would be named mmcblk0p12)

Disclaimer: I'm going to try to avoid solving this for you. I'd prefer if I can guide you to solving it yourself and then sharing the results.

Donations: I don't accept donations, but if you are feeling charitable, help a child by going to http://www.shrinershospitalsforchildren.org/
and click the "Donate Now" link at the top.
 
fishingfon
Old
#3  
fishingfon's Avatar
Senior Member - OP
Thanks Meter 253
Posts: 712
Join Date: Feb 2012
Location: Brisbane, QLD, Australia
Quote:
Originally Posted by garyd9 View Post
First, if "herbew" is a friend of yours, please ask him to never send me a PM asking me to help someone ELSE. That's just spam.

On the i9300 (and Note2) devices, I'm surprised to see any calls at all to mknod. Most of the device files are created automatically these days. However, I'm NOT familiar with Gokhan's dual boot thing (I've never used it and I don't have an i9300 anymore to tinker with it.) I'm assuming that you'd like to reverse engineer what Gokhan has done and it's often more fun to work backwards than to just nag him until he helps. So, I can't answer how to make it work, but I might be able to help you to reverse engineer or understand what is going on.

To find out more about your device nodes for mmcblk devices, you can run the following command (rooted, of course):
Code:
ls -l /dev/block/mmc*
The output will contain several lines similar to:
Code:
brw-rw----    1 system   root      179,   7 Dec 18 22:28 mmcblk0p7
In this case, the device major id is 179 and the minor id is 7. To see what those major ID's are, run "cat /proc/devices". (This doesn't show ALL device ID's used by the system, but covers most of them.) Another way to see all the partitions within the system is "cat /proc/partitions".

Doing the above on a i9300 both with and without the dual boot stuff might give some hints as to what changes the dualboot thing is making. You might also consider taking a look at whatever is used to install that dualboot stuff. Is it ONLY a kernel, or something more? Is it re-partitioning the device?

From what I could see of that init file, p16 is a partition used to store the secondary boot related flags and a system image. p13 appears to be the "primary" /system image partition.

Some questions to ask yourself:

What is the /system partition on a normal (non-dualboot) i9300? Is it p13 or something else? Does p16 exist in /proc/partitions on a non-dualboot system? In that non-dual boot setup, is there ANY device with a major of 179 and minor of 12? (My first thought would be it would be named mmcblk0p12)

Disclaimer: I'm going to try to avoid solving this for you. I'd prefer if I can guide you to solving it yourself and then sharing the results.
Hi,
Yes Herbew is a friend of mine, but i didn't tell him to start private messaging people like that lol, I think he just gets a bit carried away, I will tell him to stop :P.

I will try running thoses commands on my note 2 to get the device id ect tomorrow thanks.

And on a normal S3, the is no partitions past p12 (I think the /system partition is either p7 or p9, i will check tomorrow) hence why I am stuck :P

I don't have a galaxy S3, so i can't run thoses commands u said, is the any other way I can work it out?, without spending $500 on a s3?. Thanks.


Thanks for your help.



Sent from my GT-N7100
My Current Devices:
Galaxy Note II N7100
HTC 8x Windows Phone 8
Samsung Galaxy S2 I9100
Nexus 7


 
garyd9
Old
#4  
garyd9's Avatar
Recognized Developer
Thanks Meter 1976
Posts: 1,951
Join Date: Sep 2006
Location: Pittsburgh, PA
Quote:
Originally Posted by fishingfon View Post
I don't have a galaxy S3, so i can't run thoses commands u said, is the any other way I can work it out?, without spending $500 on a s3?. Thanks.
If I wanted that info, I'd probably post a message in the i9300/General section titled "Need a rooted user to help" and containing a message body similar to:
Quote:
Can someone who is rooted, comfortable with a shell prompt, and NOT running any kind of dualboot, please run the following commands and send me (or reply with) the results? "ls -l /dev/block/mmc*", "cat /proc/devices", and "cat /proc/partitions"

Thank you,
YourNameHere
You might also ask that a person who IS running dualboot do the same thing so you can compare them. Just be sure that they tell you if they are/aren't doing dualboot so you don't get mixed up which is which. Another thing that might be helpful is to compare the init scripts of a non-dualboot kernel's initramfs with the ones you already have. Understanding what is different might be the key to understanding what you'll have to change on the note2.

Gary

Donations: I don't accept donations, but if you are feeling charitable, help a child by going to http://www.shrinershospitalsforchildren.org/
and click the "Donate Now" link at the top.
 
fishingfon
Old
#5  
fishingfon's Avatar
Senior Member - OP
Thanks Meter 253
Posts: 712
Join Date: Feb 2012
Location: Brisbane, QLD, Australia
Quote:
Originally Posted by garyd9 View Post
If I wanted that info, I'd probably post a message in the i9300/General section titled "Need a rooted user to help" and containing a message body similar to:
You might also ask that a person who IS running dualboot do the same thing so you can compare them. Just be sure that they tell you if they are/aren't doing dualboot so you don't get mixed up which is which. Another thing that might be helpful is to compare the init scripts of a non-dualboot kernel's initramfs with the ones you already have. Understanding what is different might be the key to understanding what you'll have to change on the note2.

Gary
Ok thanks, I will make a thread in the s3 section tomorrow.

I have already replaced all the init files in /res/misc/init.41 with the stock ones from the root of the ramfs from a stock boot img (when the phone starts, if it detects a jb stock rom, it will move all the init files from init.41 to the root of the ramfs). So they are already stock.

I will have another look thru the stock Sammy ramfs tomorrow, and see if I can find a init file in /sbin (where the one i am having trouble with came from).
I can't get on my pc right now, as the is about 200 ants that have decided to move in to the laptop, so i need to figure out how to remove them before I can look :P

Thanks again for your help.

Corey

Sent from my GT-N7100
My Current Devices:
Galaxy Note II N7100
HTC 8x Windows Phone 8
Samsung Galaxy S2 I9100
Nexus 7


 
fishingfon
Old
#6  
fishingfon's Avatar
Senior Member - OP
Thanks Meter 253
Posts: 712
Join Date: Feb 2012
Location: Brisbane, QLD, Australia
Still no luck

http://forum.xda-developers.com/show....php?t=2058538



Cheers
Corey

Sent from my GT-N7100
My Current Devices:
Galaxy Note II N7100
HTC 8x Windows Phone 8
Samsung Galaxy S2 I9100
Nexus 7


 
fishingfon
Old
(Last edited by fishingfon; 22nd December 2012 at 01:56 AM.)
#7  
fishingfon's Avatar
Senior Member - OP
Thanks Meter 253
Posts: 712
Join Date: Feb 2012
Location: Brisbane, QLD, Australia
Quote:
Originally Posted by garyd9 View Post
If I wanted that info, I'd probably post a message in the i9300/General section titled "Need a rooted user to help" and containing a message body similar to:
You might also ask that a person who IS running dualboot do the same thing so you can compare them. Just be sure that they tell you if they are/aren't doing dualboot so you don't get mixed up which is which. Another thing that might be helpful is to compare the init scripts of a non-dualboot kernel's initramfs with the ones you already have. Understanding what is different might be the key to understanding what you'll have to change on the note2.

Gary
Hi,
I have got the results from typing 2 of the things in the terminal on the s3, and I will compare them when I get home, but i havent got the results from typing "ls -l /dev/block/mmc*" tho, do i really need the results from that command, or are the ones from the other 2 commands enough?.

Thanks

Cheers
Corey

EDIT: i have found someone to get me the results from "
ls -l /dev/block/mmc" so ignore the message above :P
Sent from my GT-N7100
My Current Devices:
Galaxy Note II N7100
HTC 8x Windows Phone 8
Samsung Galaxy S2 I9100
Nexus 7


 
fishingfon
Old
#8  
fishingfon's Avatar
Senior Member - OP
Thanks Meter 253
Posts: 712
Join Date: Feb 2012
Location: Brisbane, QLD, Australia
Hi,
I have got the results from thoses 3 commands u said to run in the terminal, and u can see the is 3 extra devices when the dual boot kernel is installed on the S3. theses are the devices:
brw------- root root 179, 16 2012-12-22 12:53 mmcblk0boot0
brw------- root root 179, 32 2012-12-22 12:53 mmcblk0boot1
7 1 1572864 loop1

Here are the full results from the terminal:

Code:
 "Siyah Dual boot 1.8.4,booted in to 2nd Rom ParanoidAndroid 2.54"

u0_a40@android:/ $ su
u0_a40@android:/ # ls -l /dev/block/mmc*
brw------- root     root     179,   0 2012-12-22 12:53 mmcblk0
brw------- root     root     179,  16 2012-12-22 12:53 mmcblk0boot0
brw------- root     root     179,  32 2012-12-22 12:53 mmcblk0boot1
brw------- root     root     179,   1 2012-12-22 12:53 mmcblk0p1
brw------- root     root     179,  10 2012-12-22 12:53 mmcblk0p10
brw------- root     root     179,  11 2012-12-22 12:53 mmcblk0p11
brw------- root     root     179,  12 2012-12-22 12:53 mmcblk0p12
brw------- root     root     179,   2 2012-12-22 12:53 mmcblk0p2
brw------- root     root     179,   3 2012-12-22 12:53 mmcblk0p3
brw-rw---- system   system   179,   4 2012-12-22 12:53 mmcblk0p4
brw------- root     root     179,   5 2012-12-22 12:53 mmcblk0p5
brw------- root     root     179,   6 2012-12-22 12:53 mmcblk0p6
brw-rw---- system   radio    179,   7 2012-12-22 12:53 mmcblk0p7
brw------- root     root     179,   8 2012-12-22 12:53 mmcblk0p8
brw------- root     root     179,   9 2012-12-22 12:53 mmcblk0p9
brw------- root     root     179,  48 2012-12-22 12:53 mmcblk1
brw------- root     root     179,  49 2012-12-22 12:53 mmcblk1p1
u0_a40@android:/ # cat /proc/devices
Character devices:
  1 mem
  4 /dev/vc/0
  4 tty
  4 ttyS
  5 /dev/tty
  5 /dev/console
  5 /dev/ptmx
  7 vcs
 10 misc
 13 input
 21 sg
 29 fb
 81 video4linux
 89 i2c
108 ppp
116 alsa
128 ptm
136 pts
153 spi
180 usb
188 ttyUSB
189 usb_device
204 ttySAC
216 rfcomm
243 ump
244 mali
248 ttyGS
249 roccat
250 BaseRemoteCtl
251 media
252 usbmon
253 tzic
254 rtc

Block devices:
  1 ramdisk
259 blkext
  7 loop
  8 sd
 65 sd
 66 sd
 67 sd
 68 sd
 69 sd
 70 sd
 71 sd
128 sd
129 sd
130 sd
131 sd
132 sd
133 sd
134 sd
135 sd
179 mmc
254 device-mapper
u0_a40@android:/ # cat /proc/partitions
major minor  #blocks  name

   7        0    1572864 loop0
   7        1    1572864 loop1
 179        0   15388672 mmcblk0
 179        1       4096 mmcblk0p1
 179        2       4096 mmcblk0p2
 179        3      20480 mmcblk0p3
 179        4       8192 mmcblk0p4
 179        5       8192 mmcblk0p5
 179        6       8192 mmcblk0p6
 179        7      32768 mmcblk0p7
 179        8    1048576 mmcblk0p8
 179        9    1572864 mmcblk0p9
 179       10     573440 mmcblk0p10
 179       11       8192 mmcblk0p11
 179       12   12091392 mmcblk0p12
 179       32       2048 mmcblk0boot1
 179       16       2048 mmcblk0boot0
 179       48   30657536 mmcblk1
 179       49   30653440 mmcblk1p1
u0_a40@android:/ #
Code:
"Siyah DualBoot 1.8.4,booted in to 1st rom XXELKC Samsung Rom"


u0_a111@android:/ $ su
u0_a111@android:/ # ls -l /dev/block/mmc*
brw------- root     root     179,   0 2012-12-22 12:10 mmcblk0
brw------- root     root     179,  16 2012-12-22 12:10 mmcblk0boot0
brw------- root     root     179,  32 2012-12-22 12:10 mmcblk0boot1
brw------- root     root     179,   1 2012-12-22 12:10 mmcblk0p1
brw------- root     root     179,  10 2012-12-22 12:10 mmcblk0p10
brw------- root     root     179,  11 2012-12-22 12:10 mmcblk0p11
brw------- root     root     179,  12 2012-12-22 12:10 mmcblk0p12
brw------- root     root     179,   2 2012-12-22 12:10 mmcblk0p2
brw------- root     root     179,   3 2012-12-22 12:10 mmcblk0p3
brw-rw---- system   system   179,   4 2012-12-22 12:11 mmcblk0p4
brw------- root     root     179,   5 2012-12-22 12:10 mmcblk0p5
brw------- root     root     179,   6 2012-12-22 12:10 mmcblk0p6
brw-rw---- system   radio    179,   7 2012-12-22 12:10 mmcblk0p7
brw------- root     root     179,   8 2012-12-22 12:10 mmcblk0p8
brw------- root     root     179,   9 2012-12-22 12:10 mmcblk0p9
brw------- root     root     179,  48 2012-12-22 12:10 mmcblk1
brw------- root     root     179,  49 2012-12-22 12:10 mmcblk1p1
u0_a111@android:/ # cat /proc/devices
Character devices:
  1 mem
  4 /dev/vc/0
  4 tty
  4 ttyS
  5 /dev/tty
  5 /dev/console
  5 /dev/ptmx
  7 vcs
10 misc
13 input
21 sg
29 fb
81 video4linux
89 i2c
108 ppp
116 alsa
128 ptm
136 pts
153 spi
180 usb
188 ttyUSB
189 usb_device
204 ttySAC
216 rfcomm
243 ump
244 mali
248 ttyGS
249 roccat
250 BaseRemoteCtl
251 media
252 usbmon
253 tzic
254 rtc

Block devices:
  1 ramdisk
259 blkext
  7 loop
  8 sd
65 sd
66 sd
67 sd
68 sd
69 sd
70 sd
71 sd
128 sd
129 sd
130 sd
131 sd
132 sd
133 sd
134 sd
135 sd
179 mmc
254 device-mapper
u0_a111@android:/ # cat /proc/partitions
major minor  #blocks  name

   7        0       2111 loop0
179        0   15388672 mmcblk0
179        1       4096 mmcblk0p1
179        2       4096 mmcblk0p2
179        3      20480 mmcblk0p3
179        4       8192 mmcblk0p4
179        5       8192 mmcblk0p5
179        6       8192 mmcblk0p6
179        7      32768 mmcblk0p7
179        8    1048576 mmcblk0p8
179        9    1572864 mmcblk0p9
179       10     573440 mmcblk0p10
179       11       8192 mmcblk0p11
179       12   12091392 mmcblk0p12
179       32       2048 mmcblk0boot1
179       16       2048 mmcblk0boot0
179       48   30657536 mmcblk1
179       49   30653440 mmcblk1p1
254        0       2110 dm-0
u0_a111@android:/ #
Code:
"Stock Kernel (ELK4) + XXELKC Samsung Rom"


u0_a111@android:/ $ su
u0_a111@android:/ # ls -l /dev/block/mmc*
brw------- root     root     179,   0 2012-12-22 12:57 mmcblk0
brw------- root     root     179,   1 2012-12-22 12:57 mmcblk0p1
brw------- root     root     179,  10 2012-12-22 12:57 mmcblk0p10
brw------- root     root     179,  11 2012-12-22 12:57 mmcblk0p11
brw------- root     root     179,  12 2012-12-22 12:57 mmcblk0p12
brw------- root     root     179,   2 2012-12-22 12:57 mmcblk0p2
brw------- root     root     179,   3 2012-12-22 12:57 mmcblk0p3
brw-rw---- system   system   179,   4 2012-12-22 12:58 mmcblk0p4
brw------- root     root     179,   5 2012-12-22 12:57 mmcblk0p5
brw------- root     root     179,   6 2012-12-22 12:57 mmcblk0p6
brw-rw---- system   radio    179,   7 2012-12-22 12:57 mmcblk0p7
brw------- root     root     179,   8 2012-12-22 12:57 mmcblk0p8
brw------- root     root     179,   9 2012-12-22 12:57 mmcblk0p9
brw------- root     root     179,  16 2012-12-22 12:57 mmcblk1
brw------- root     root     179,  17 2012-12-22 12:57 mmcblk1p1
u0_a111@android:/ # cat /proc/devices
Character devices:
  1 mem
  4 /dev/vc/0
  4 tty
  4 ttyS
  5 /dev/tty
  5 /dev/console
  5 /dev/ptmx
  7 vcs
10 misc
13 input
21 sg
29 fb
81 video4linux
89 i2c
108 ppp
116 alsa
128 ptm
136 pts
153 spi
180 usb
188 ttyUSB
189 usb_device
204 ttySAC
216 rfcomm
243 ump
244 mali
248 roccat
249 BaseRemoteCtl
250 media
251 ttyGS
252 usbmon
253 tzic
254 rtc

Block devices:
  1 ramdisk
259 blkext
  7 loop
  8 sd
65 sd
66 sd
67 sd
68 sd
69 sd
70 sd
71 sd
128 sd
129 sd
130 sd
131 sd
132 sd
133 sd
134 sd
135 sd
179 mmc
254 device-mapper
u0_a111@android:/ # cat /proc/partitions
major minor  #blocks  name

   7        0       2111 loop0
179        0   15388672 mmcblk0
179        1       4096 mmcblk0p1
179        2       4096 mmcblk0p2
179        3      20480 mmcblk0p3
179        4       8192 mmcblk0p4
179        5       8192 mmcblk0p5
179        6       8192 mmcblk0p6
179        7      32768 mmcblk0p7
179        8    1048576 mmcblk0p8
179        9    1572864 mmcblk0p9
179       10     573440 mmcblk0p10
179       11       8192 mmcblk0p11
179       12   12091392 mmcblk0p12
179       16   30657536 mmcblk1
179       17   30653440 mmcblk1p1
254        0       2110 dm-0
u0_a111@android:/ #

And here is the results I got from typing the commands in my Note
II

Code:
u0_a160@android:/ $ export PATH=/data/local/bin:$PATH
 u0_a160@android:/ $ su
 u0_a160@android:/ # ls -l /dev/block/mmc*
 brw------- root     root     179,   0 2012-12-22 08:35 mmcblk0
 brw------- root     root     179,   1 2012-12-22 08:35 mmcblk0p1
 brw-rw---- system   radio    179,  10 2012-12-22 08:35 mmcblk0p10
 brw-rw---- system   radio    179,  11 2012-12-22 08:35 mmcblk0p11
 brw------- root     root     179,  12 2012-12-22 08:35 mmcblk0p12
 brw------- root     root     179,  13 2012-12-22 08:35 mmcblk0p13
 brw------- root     root     179,  14 2012-12-22 08:35 mmcblk0p14
 brw------- root     root     179,  15 2012-12-22 08:35 mmcblk0p15
 brw------- root     root     259,   0 2012-12-22 08:35 mmcblk0p16
 brw------- root     root     179,   2 2012-12-22 08:35 mmcblk0p2
 brw------- root     root     179,   3 2012-12-22 08:35 mmcblk0p3
 brw-rw---- system   radio    179,   4 2012-12-22 08:35 mmcblk0p4
 brw-rw---- system   radio    179,   5 2012-12-22 08:35 mmcblk0p5
 brw-rw---- system   radio    179,   6 2012-12-22 08:35 mmcblk0p6
 brw-rw---- system   root     179,   7 2012-12-22 08:35 mmcblk0p7
 brw------- root     root     179,   8 2012-12-22 08:35 mmcblk0p8
 brw------- root     root     179,   9 2012-12-22 08:35 mmcblk0p9
 brw------- root     root     179,  16 2012-12-22 08:35 mmcblk1
 brw------- root     root     179,  17 2012-12-22 08:35 mmcblk1p1
 u0_a160@android:/ # cat /proc/devices
 Character devices:
   1 mem
   4 /dev/vc/0
   4 tty
   4 ttyS
   5 /dev/tty
   5 /dev/console
   5 /dev/ptmx
   7 vcs
 10 misc
 13 input
 21 sg
 29 fb
 81 video4linux
 89 i2c
 108 ppp
 116 alsa
 128 ptm
 136 pts
 153 spi
 180 usb
 188 ttyUSB
 189 usb_device
 204 ttySAC
 216 rfcomm
 243 ump
 244 mali
 248 roccat
 249 BaseRemoteCtl
 250 media
 251 ttyGS
 252 usbmon
 253 tzic
 254 rtc

Block devices:
   1 ramdisk
 259 blkext
   7 loop
   8 sd
 65 sd
 66 sd
 67 sd
 68 sd
 69 sd
 70 sd
 71 sd
 128 sd
 129 sd
 130 sd
 131 sd
 132 sd
 133 sd
 134 sd
 135 sd
 179 mmc
 254 device-mapper
 u0_a160@android:/ # cat /proc/partitions
 major minor  #blocks  name

   7        0      47849 loop0
    7        1      12506 loop1
    7        2      14585 loop2
    7        3       2111 loop3
    7        4       3150 loop4
    7        5      35375 loop5
    7        6      34335 loop6
    7        7       2111 loop7
 179        0   15388672 mmcblk0
 179        1       4096 mmcblk0p1
 179        2       4096 mmcblk0p2
 179        3      20480 mmcblk0p3
 179        4       4096 mmcblk0p4
 179        5       4096 mmcblk0p5
 179        6       4096 mmcblk0p6
 179        7       8192 mmcblk0p7
 179        8       8192 mmcblk0p8
 179        9       8192 mmcblk0p9
 179       10      90112 mmcblk0p10
 179       11       4096 mmcblk0p11
 179       12    1400832 mmcblk0p12
 179       13    2097152 mmcblk0p13
 179       14     573440 mmcblk0p14
 179       15       8192 mmcblk0p15
 259        0   11141120 mmcblk0p16
 179       16   62367744 mmcblk1
 179       17   62351360 mmcblk1p1
 254        0      47848 dm-0
 254        1      12505 dm-1
 254        2      14584 dm-2
 254        3       2110 dm-3
 254        4       3150 dm-4
 254        5      35374 dm-5
 254        6      34335 dm-6
 254        7       2110 dm-7
    7        8      13545 loop8
 254        8      13545 dm-8
    7        9      16664 loop9
 254        9      16663 dm-9
    7       10       2111 loop10
 254       10       2110 dm-10
    7       11      43691 loop11
 254       11      43690 dm-11
    7       12       8348 loop12
 254       12       8347 dm-12
    7       13       9387 loop13
 254       13       9387 dm-13
    7       14      21861 loop14
 254       14      21861 dm-14
 u0_a160@android:/ #

Do u know how I would get thoses two extra partitions on the note 2?. are thoses the same partitions that I mentioned in the first post (p13 and p16)??.

Thanks again for your help.

Corey
My Current Devices:
Galaxy Note II N7100
HTC 8x Windows Phone 8
Samsung Galaxy S2 I9100
Nexus 7


 
fishingfon
Old
#9  
fishingfon's Avatar
Senior Member - OP
Thanks Meter 253
Posts: 712
Join Date: Feb 2012
Location: Brisbane, QLD, Australia
Ps,
The /system and /data partitions on a stick non-dual boot s3 are p9 and p12, and they have the minor of 9 and 12, just like the partitions p13 and p16 I mentioned in the first post. But the partitions on the first post have different names. Do u have any idea why that could be?.

Cheers
Corey

Sent from my GT-N7100
My Current Devices:
Galaxy Note II N7100
HTC 8x Windows Phone 8
Samsung Galaxy S2 I9100
Nexus 7


 
garyd9
Old
#10  
garyd9's Avatar
Recognized Developer
Thanks Meter 1976
Posts: 1,951
Join Date: Sep 2006
Location: Pittsburgh, PA
What I'm NOT seeing is the mmcblk0p13 and mmcblk0p16 devices that are supposedly made by the init script on the dual boot s3. Any idea why not?

Donations: I don't accept donations, but if you are feeling charitable, help a child by going to http://www.shrinershospitalsforchildren.org/
and click the "Donate Now" link at the top.

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes