Hi All!!
I have a Qmoible A5Classic and I want to develop its CWM Recovery. I want to fetch its recovery by
Code:
dd if=etc of=abc
but the problem is i cannot find which partition is my recovery partition.
Code:
cat proc/partitions
shows:
Code:
major minor #blocks name
7 0 1254 loop0
179 0 3815552 mmcblk0
179 1 1 mmcblk0p1
179 2 163840 mmcblk0p2
179 3 1064960 mmcblk0p3
179 4 2028784 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 524288 mmcblk0p6
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
179 24 1949696 mmcblk1
179 25 1948672 mmcblk1p1
and
Code:
cat proc/mounts
show these:
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
[email protected] /system ext4 rw,relatime,user_xattr,commit=1,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/loop0 /mnt/cd-rom iso9660 ro,relatime 0 0
[email protected] /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
[email protected] /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/vold/179:4 /mnt/sdcard2 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:25 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:25 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Can anyone please point out the right partition?
PS: It is rooted.
Regards
ssm14293 said:
Hi All!!
Can anyone please point out the right partition?
PS: It is rooted.
Regards
Click to expand...
Click to collapse
I would recommend running the following command as root from terminal emulator:
Code:
cat /cache/recovery/last_log
This should tell you which partition is your recovery partition that you can then dump a copy of the stock recovery.img to your device. Let me know if you still have questions.
Sent from my SCH-I535 using xda premium
cmd says /recovery emmc recovery (null) 0
shimp208 said:
I would recommend running the following command as root from terminal emulator:
Code:
cat /cache/recovery/last_log
This should tell you which partition is your recovery partition that you can then dump a copy of the stock recovery.img to your device. Let me know if you still have questions.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
This is what I get upon running your command:
Code:
Partition Information:
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000004000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x000000000005c000 0x0000000000004000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000060000 2 /dev/block/mmcblk0
nvram 0x0000000000300000 0x0000000000460000 2 /dev/block/mmcblk0
seccfg 0x0000000000020000 0x0000000000760000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000000780000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x00000000007e0000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000000de0000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x00000000013e0000 2 /dev/block/mmcblk0p5
misc 0x0000000000060000 0x00000000019e0000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000001a40000 2 /dev/block/mmcblk0
expdb 0x00000000000a0000 0x0000000001d40000 2 /dev/block/mmcblk0
ebr2 0x0000000000004000 0x0000000001de0000 2 /dev/block/mmcblk0
android 0x0000000020100000 0x0000000001de4000 2 /dev/block/mmcblk0p6
cache 0x000000000a100000 0x0000000021ee4000 2 /dev/block/mmcblk0p2
usrdata 0x0000000041100000 0x000000002bfe4000 2 /dev/block/mmcblk0p3
fat 0x0000000000000001 0x000000006d0e4000 2 /dev/block/mmcblk0p4
bmtpool 0x000000007bafbfff 0xffffffffffa00000 2 /dev/block/mmcblk0
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc boot (null) 0
2 /cache ext4 /dev/block/mmcblk0p2 (null) 0
3 /data ext4 /dev/block/mmcblk0p3 (null) 0
4 /misc emmc misc (null) 0
5 /recovery emmc recovery (null) 0
6 /sdcard vfat /dev/block/mmcblk1 /dev/block/mmcblk0p4 0
7 /sdcard2 vfat /dev/block/mmcblk0p4 (null) 0
8 /system ext4 /dev/block/mmcblk0p6 (null) 0
ssm14293 said:
This is what I get upon running your command:
Code:
Partition Information:
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000004000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x000000000005c000 0x0000000000004000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000060000 2 /dev/block/mmcblk0
nvram 0x0000000000300000 0x0000000000460000 2 /dev/block/mmcblk0
seccfg 0x0000000000020000 0x0000000000760000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000000780000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x00000000007e0000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000000de0000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x00000000013e0000 2 /dev/block/mmcblk0p5
misc 0x0000000000060000 0x00000000019e0000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000001a40000 2 /dev/block/mmcblk0
expdb 0x00000000000a0000 0x0000000001d40000 2 /dev/block/mmcblk0
ebr2 0x0000000000004000 0x0000000001de0000 2 /dev/block/mmcblk0
android 0x0000000020100000 0x0000000001de4000 2 /dev/block/mmcblk0p6
cache 0x000000000a100000 0x0000000021ee4000 2 /dev/block/mmcblk0p2
usrdata 0x0000000041100000 0x000000002bfe4000 2 /dev/block/mmcblk0p3
fat 0x0000000000000001 0x000000006d0e4000 2 /dev/block/mmcblk0p4
bmtpool 0x000000007bafbfff 0xffffffffffa00000 2 /dev/block/mmcblk0
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc boot (null) 0
2 /cache ext4 /dev/block/mmcblk0p2 (null) 0
3 /data ext4 /dev/block/mmcblk0p3 (null) 0
4 /misc emmc misc (null) 0
5 /recovery emmc recovery (null) 0
6 /sdcard vfat /dev/block/mmcblk1 /dev/block/mmcblk0p4 0
7 /sdcard2 vfat /dev/block/mmcblk0p4 (null) 0
8 /system ext4 /dev/block/mmcblk0p6 (null) 0
Click to expand...
Click to collapse
Very interesting from looking at your partition layout I can see that that /dev/block/mmcblk0 contains your recovery partition. However it appears /dev/block/mmcblk0 is a combined partition that also contains many critical parts of the phones file system such u-boot, /boot, and other bootloader related components. I would recommend running the following commands as root from either ADB shell:
Code:
cd /dev/block/platform
Then from the platform directory list the contents of the directory with the "ls" command. Once you have done that you should see a platform name (Or multiple platform names) for example on my Verizon Galaxy S3 it shows:
Code:
msm_sdcc.1
msm_sdcc.3
Cd into each of the platform directories (Or if there is only one platform directory "cd" into that) and list the contents of the platform directory using the "ls" command and look to see if it list a directory "by-name". If the platform directory your in contains the "by-name" folder run the following command:
Code:
ls -l /dev/block/platform/{platform directory name here}/by-name
If that command returns an output take note of the the block number that contains the recovery partition.
Another suggestion would be to run the following command to try and isolate the recovery.img from the larger /dev/block/mmcblk0 contents:
Code:
dd if=/dev/block/mmcblk0 of=mnt/sdcard/recovery.img bs=1 skip=6291456 count=8257536
Additionally you could try dumping the whole /dev/block/mmcblk0 partition using the command:
Code:
cat /dev/block/mmcblk0 > /mnt/sdcard/recovery.img
Let me know how the above commands work out for you .
shimp208 said:
[/HIDE]
Very interesting from looking at your partition layout I can see that that /dev/block/mmcblk0 contains your recovery partition. However it appears /dev/block/mmcblk0 is a combined partition that also contains many critical parts of the phones file system such u-boot, /boot, and other bootloader related components. I would recommend running the following commands as root from either ADB shell:
Code:
cd /dev/block/platform
Then from the platform directory list the contents of the directory with the "ls" command. Once you have done that you should see a platform name (Or multiple platform names) for example on my Verizon Galaxy S3 it shows:
Code:
msm_sdcc.1
msm_sdcc.3
Cd into each of the platform directories (Or if there is only one platform directory "cd" into that) and list the contents of the platform directory using the "ls" command and look to see if it list a directory "by-name". If the platform directory your in contains the "by-name" folder run the following command:
Code:
ls -l /dev/block/platform/{platform directory name here}/by-name
If that command returns an output take note of the the block number that contains the recovery partition.
Another suggestion would be to run the following command to try and isolate the recovery.img from the larger /dev/block/mmcblk0 contents:
Code:
dd if=/dev/block/mmcblk0 of=mnt/sdcard/recovery.img bs=1 skip=6291456 count=8257536
Additionally you could try dumping the whole /dev/block/mmcblk0 partition using the command:
Code:
cat /dev/block/mmcblk0 > /mnt/sdcard/recovery.img
Let me know how the above commands work out for you .
Click to expand...
Click to collapse
Jahan panha tussi great ho taufa qabul karo!
Click to expand...
Click to collapse
Translation: Dude!!!! Ur great!! please accept my humble gift :victory:
I dont have a by-name folder but only by-num, which really doesnt help. So now I will try your second method, extracting a part of the main image!! I'll tell you the result!!!
Regards
I did what you asked me to and it gave me a 7.87mb img file, but I cannot extract it using the unpack-mt65xx.pl. Invalid file. Can you please point me in the right direction please.
Regards
ssm14293 said:
I did what you asked me to and it gave me a 7.87mb img file, but I cannot extract it using the unpack-mt65xx.pl. Invalid file. Can you please point me in the right direction please.
Regards
Click to expand...
Click to collapse
In that case I would recommend trying to dump the whole /dev/block/mmcblk0 partition and seeing if you can unpack it then.
Some Luck with it...
shimp208 said:
In that case I would recommend trying to dump the whole /dev/block/mmcblk0 partition and seeing if you can unpack it then.
Click to expand...
Click to collapse
Hi I tried to extract the recovery.img created from your command using unmkboot in my Ubuntu VM. I got two files from it, a zImage file and an initramfs.cpio.gz files with this output:
Code:
unmkbootimg version 1.2 - Mikael Q Kuisma <[email protected]>
File ./images/recovery.img not a plain boot image, seeking for embedded image ... found!
Kernel size 3248084
Kernel address 0x10008000
Ramdisk size 506660
Ramdisk address 0x11000000
Secondary size 0
Secondary address 0x10f00000
Kernel tags address 0x10000100
Flash page size 2048
Board name is "1354555027"
Command line ""
This image is built using standard mkbootimg
Extracting kernel to file zImage ...
Extracting root filesystem to file initramfs.cpio.gz ...
All done.
---------------
To recompile this image, use:
mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --board '1354555027' -o new_boot.img
---------------
Now what can i do from here. I cannot extract the cpio.gz file, how will I do that.
Thanks for helping out!
I cannot dump the whole mmcblk0 because I dont have a memory card large enough for the dump, which is roughly 4gb.
Regards
Few Questions
shimp208 said:
In that case I would recommend trying to dump the whole /dev/block/mmcblk0 partition and seeing if you can unpack it then.
Click to expand...
Click to collapse
There is one thing I noted in the partition list. the stating point for boot, recovery and sec_ro is same i.e:
Code:
0x0000000000600000
but they end at different blocks, would that be a problem?
I think the over all partition type is ext4 which is supported by Ubuntu 13.04, can i do something to read the partition directly, like mount it in some way?
ssm14293 said:
Hi I tried to extract the recovery.img created from your command using unmkboot in my Ubuntu VM. I got two files from it, a zImage file and an initramfs.cpio.gz files with this output:
Code:
unmkbootimg version 1.2 - Mikael Q Kuisma <[email protected]>
File ./images/recovery.img not a plain boot image, seeking for embedded image ... found!
Kernel size 3248084
Kernel address 0x10008000
Ramdisk size 506660
Ramdisk address 0x11000000
Secondary size 0
Secondary address 0x10f00000
Kernel tags address 0x10000100
Flash page size 2048
Board name is "1354555027"
Command line ""
This image is built using standard mkbootimg
Extracting kernel to file zImage ...
Extracting root filesystem to file initramfs.cpio.gz ...
All done.
---------------
To recompile this image, use:
mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --board '1354555027' -o new_boot.img
---------------
Now what can i do from here. I cannot extract the cpio.gz file, how will I do that.
Thanks for helping out!
I cannot dump the whole mmcblk0 because I dont have a memory card large enough for the dump, which is roughly 4gb.
Regards
Click to expand...
Click to collapse
To unpack the cpio.gz file I would recommend downloading these Linux boot.img tools, they will allow you to unpack and repack the cpio.gz ramdisk file. Make sure after you download those tools you put them in your ~/bin folder and that the folder in your PATH or else the tools won't work as they rely on each other to function properly.
ssm14293 said:
There is one thing I noted in the partition list. the stating point for boot, recovery and sec_ro is same i.e:
Code:
0x0000000000600000
but they end at different blocks, would that be a problem?
I think the over all partition type is ext4 which is supported by Ubuntu 13.04, can i do something to read the partition directly, like mount it in some way?
Click to expand...
Click to collapse
I thought this offset for the partitions was very interesting, instead of going from one offset to another that would make it clear which parts of the /dev/block/mmcblk0 is recovery, boot, etc. they all seem to overlap. If you can find to dump the full partition and then transfer it to your computer you should be able to mount it in Ubuntu if it's ext4 and then read it's contents.
Found a way!
shimp208 said:
To unpack the cpio.gz file I would recommend downloading these Linux boot.img tools, they will allow you to unpack and repack the cpio.gz ramdisk file. Make sure after you download those tools you put them in your ~/bin folder and that the folder in your PATH or else the tools won't work as they rely on each other to function properly.
I thought this offset for the partitions was very interesting, instead of going from one offset to another that would make it clear which parts of the /dev/block/mmcblk0 is recovery, boot, etc. they all seem to overlap. If you can find to dump the full partition and then transfer it to your computer you should be able to mount it in Ubuntu if it's ext4 and then read it's contents.
Click to expand...
Click to collapse
Hi again!!
I just got myself an 8GB memory card. I also searched more about nandroid backups for non-CWM phones. I got across onandroid, it creates img files of all partitions. It was created by someone from XDA Forums, can't remember the name. So at the moment it is generating MD5 Checksum.
After this I will create my OWN Rom and CWM for this phone :victory: , well after my finals .
Thanks for your help! :highfive:
For all Qmobile Rooted users, use onandroid to create backups, but at your own risk. I can confirm for QMobiel A5 Classic
where to copy symphony CWM recovery.img using dd command
I am Moniruzzaman from Dhaka, Bangladesh...
Please forgive me for my weak English.
I have created a CWM recovery img (Latest Touch Version) for my rooted Symphony W85. My device partitions is similar to the Qmoible A5Classic. Now I have failed to copy it to the recovery partition as i could not figure out which is my recovery partition.
Partition Information:
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000004000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x000000000005c000 0x0000000000004000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000060000 2 /dev/block/mmcblk0
nvram 0x0000000000300000 0x0000000000460000 2 /dev/block/mmcblk0
seccfg 0x0000000000020000 0x0000000000760000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000000780000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x00000000007e0000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000000de0000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x00000000013e0000 2 /dev/block/mmcblk0p5
misc 0x0000000000060000 0x00000000019e0000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000001a40000 2 /dev/block/mmcblk0
expdb 0x00000000000a0000 0x0000000001d40000 2 /dev/block/mmcblk0
ebr2 0x0000000000004000 0x0000000001de0000 2 /dev/block/mmcblk0
android 0x0000000020100000 0x0000000001de4000 2 /dev/block/mmcblk0p6
cache 0x000000000a100000 0x0000000021ee4000 2 /dev/block/mmcblk0p2
usrdata 0x0000000041100000 0x000000002bfe4000 2 /dev/block/mmcblk0p3
fat 0x0000000000000001 0x000000006d0e4000 2 /dev/block/mmcblk0p4
bmtpool 0x000000007bafbfff 0xffffffffffa00000 2 /dev/block/mmcblk0
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc boot (null) 0
2 /cache ext4 /dev/block/mmcblk0p2 (null) 0
3 /data ext4 /dev/block/mmcblk0p3 (null) 0
4 /misc emmc misc (null) 0
5 /recovery emmc recovery (null) 0
6 /sdcard vfat /dev/block/mmcblk1 /dev/block/mmcblk0p4 0
7 /sdcard2 vfat /dev/block/mmcblk0p4 (null) 0
8 /system ext4 /dev/block/mmcblk0p6 (null) 0
I have flashed the recovery.img using dd if=mnt/sdcard/recovery.img of=/dev/recovery. Everything was fine except my gsm signal was gone.
Then I tried flashed stock recovery.img using dd if=mnt/sdcard/recovery.img of=/dev/recovery - everything works fine again.
I have come so far and now i can't fine the right partitions. I am very frustrated.
Can any one please help me how to flash my CWM recovery img (Latest Touch Version) to my device as it is combined partitions.
shimp208 said:
.
Click to expand...
Click to collapse
What about this: this is from Lenovo TAB S8-50 (USA/BestBuy) Wifi version....
Starting recovery on Thu Dec 4 03:55:45 2014
recovery filesystem table
=========================
0 /reserved hidden /dev/block/platform/intel/by-label/reserved 0
1 /ESP vfat /dev/block/platform/intel/by-label/ESP 0
2 /boot hidden /dev/block/platform/intel/by-label/boot 0
3 /recovery hidden /dev/block/platform/intel/by-label/recovery 0
4 /fastboot hidden /dev/block/platform/intel/by-label/fastboot 0
5 /reserved_1 hidden /dev/block/platform/intel/by-label/reserved_1 0
6 /panic raw /dev/block/platform/intel/by-label/panic 0
7 /factory ext4 /dev/block/platform/intel/by-label/factory 0
8 /misc emmc /dev/block/platform/intel/by-label/misc 0
9 /config ext4 /dev/block/platform/intel/by-label/config 0
10 /cache ext4 /dev/block/platform/intel/by-label/cache 0
11 /system ext4 /dev/block/platform/intel/by-label/system 0
12 /data ext4 /dev/block/platform/intel/by-label/data -16384
13 /sdcard vfat /dev/block/mmcblk1p1 0
14 /tmp ramdisk ramdisk 0
jazzespresso said:
What about this: this is from Lenovo TAB S8-50 (USA/BestBuy) Wifi version....
Starting recovery on Thu Dec 4 03:55:45 2014
recovery filesystem table
=========================
0 /reserved hidden /dev/block/platform/intel/by-label/reserved 0
1 /ESP vfat /dev/block/platform/intel/by-label/ESP 0
2 /boot hidden /dev/block/platform/intel/by-label/boot 0
3 /recovery hidden /dev/block/platform/intel/by-label/recovery 0
4 /fastboot hidden /dev/block/platform/intel/by-label/fastboot 0
5 /reserved_1 hidden /dev/block/platform/intel/by-label/reserved_1 0
6 /panic raw /dev/block/platform/intel/by-label/panic 0
7 /factory ext4 /dev/block/platform/intel/by-label/factory 0
8 /misc emmc /dev/block/platform/intel/by-label/misc 0
9 /config ext4 /dev/block/platform/intel/by-label/config 0
10 /cache ext4 /dev/block/platform/intel/by-label/cache 0
11 /system ext4 /dev/block/platform/intel/by-label/system 0
12 /data ext4 /dev/block/platform/intel/by-label/data -16384
13 /sdcard vfat /dev/block/mmcblk1p1 0
14 /tmp ramdisk ramdisk 0
Click to expand...
Click to collapse
I would recommend running the following command to dump your recovery partition:
Code:
cat /dev/block/platform/intel/by-label/recovery > /mnt/sdcard/recovery.img
Let me know if you still have questions, happy to help you out.
shimp208 said:
I would recommend running the following command to dump your recovery partition:
Code:
cat /dev/block/platform/intel/by-label/recovery > /mnt/sdcard/recovery.img
Let me know if you still have questions, happy to help you out.
Click to expand...
Click to collapse
thank you very much...what about boot.img?
jazzespresso said:
thank you very much...what about boot.img?
Click to expand...
Click to collapse
For boot you would run the command:
Code:
cat /dev/block/platform/intel/by-label/boot > /mnt/sdcard/boot.img
Hope this helps you!
Can anyone help me ? I ran the script bellow trying to expand my system partition to solve a problem and now I've lost my recoverymode. I get a 2 min blackscreen and then it starts.
COde that got me lost:
Code:
#!/sbin/sh
OUTFD=$2
ui_print() {
echo -n -e "ui_print $1\n" > /proc/self/fd/$OUTFD
echo -n -e "ui_print\n" > /proc/self/fd/$OUTFD
}
ui_print ""
ui_print "###########################"
ui_print "# audahadi #"
ui_print "# modded from forumber2's #"
ui_print "# Repartition script #"
ui_print "# Mi 3W /system 1.2G #"
ui_print "# only! #"
ui_print "###########################"
ui_print ""
ui_print "Unmounting systems partiton..."
umount -l /system
umount -l /system1
umount -l /dev/block/mmcblk0p25
umount -l /dev/block/mmcblk0p26
ui_print ""
ui_print "WARNING! System is ready, repartitioning will start in
2 seconds"
sleep 2
ui_print ""
ui_print "Removing partitions..."
parted /dev/block/mmcblk0 rm 25
parted /dev/block/mmcblk0 rm 26
ui_print "Removing partitions...COMPLETED"
ui_print ""
ui_print "Creating new partitions..."
parted /dev/block/mmcblk0 mkpart primary 403MB 1740MB
parted /dev/block/mmcblk0 mkpart primary 1740MB 1745MB
parted /dev/block/mmcblk0 name 25 system
parted /dev/block/mmcblk0 name 26 system1
ui_print "Creating new partitions...COMPLETED"
ui_print ""
ui_print "Unmounting systems partitions again..."
umount -l /system
umount -l /system1
umount -l /dev/block/mmcblk0p25
umount -l /dev/block/mmcblk0p26
ui_print "Unmounting systems partitions again...COMPLETED"
ui_print ""
ui_print "Formatting new partitions..."
mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p25
mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p26
ui_print "Formatting new partitions...COMPLETED."
ui_print ""
ui_print "ALL DONE!..."
ui_print ""
ui_print "Rebooting to recovery in 5 seconds..."
ui_print "Thanks to forumber2 for his original GT-i9300
repartition script"
sleep 5
reboot recovery
fi
Follow info:
Code:
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 2048 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 24576 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 780 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8 mmcblk0p17
179 18 16384 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 512 mmcblk0p20
179 21 512 mmcblk0p21
179 22 1556480 mmcblk0p22
179 23 819200 mmcblk0p23
179 24 26714112 mmcblk0p24
179 27 24576 mmcblk0p27
179 28 3072 mmcblk0p28
179 29 8 mmcblk0p29
179 30 32768 mmcblk0p30
179 31 32768 mmcblk0p31
259 0 512 mmcblk0p32
259 1 512 mmcblk0p33
259 2 16384 mmcblk0p34
259 3 879599 mmcblk0p35
[email protected]:/ $
Code:
[email protected]:/dev/block/platform/msm_sdcc.1/by-name # ls -l
ls -l
lrwxrwxrwx root root 2015-07-20 22:30 DDR -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2015-07-20 22:30 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-07-20 22:30 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-07-20 22:30 cache -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-07-20 22:30 drm -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-07-20 22:30 eksst -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-07-20 22:30 encrypt -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-07-20 22:30 factory -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-07-20 22:30 fota -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2015-07-20 22:30 fsg -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2015-07-20 22:30 grow -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2015-07-20 22:30 m9kefs1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-07-20 22:30 m9kefs2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-07-20 22:30 m9kefs3 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-07-20 22:30 misc -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-07-20 22:30 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-07-20 22:30 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-07-20 22:30 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-07-20 22:30 mpt -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2015-07-20 22:30 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-07-20 22:30 recovery -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2015-07-20 22:30 reserved -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2015-07-20 22:30 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-07-20 22:30 rpmbak -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2015-07-20 22:30 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-07-20 22:30 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-07-20 22:30 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-07-20 22:30 sns -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-07-20 22:30 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-07-20 22:30 system -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-07-20 22:30 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-07-20 22:30 tzbak -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2015-07-20 22:30 userdata -> /dev/block/mmcblk0p24
[email protected]:/dev/block/platform/msm_sdcc.1/by-name #
Code:
[email protected]:/dev/block $ cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,
data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,node
v,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,no
dev,noatime,noauto_da_alloc,data=ordered 0 0
[email protected]:/dev/block $
dihhedessa said:
Can anyone help me ? I ran the script bellow trying to expand my system partition to solve a problem and now I've lost my recoverymode. I get a 2 min blackscreen and then it starts.
COde that got me lost:
Code:
#!/sbin/sh
OUTFD=$2
ui_print() {
echo -n -e "ui_print $1\n" > /proc/self/fd/$OUTFD
echo -n -e "ui_print\n" > /proc/self/fd/$OUTFD
}
ui_print ""
ui_print "###########################"
ui_print "# audahadi #"
ui_print "# modded from forumber2's #"
ui_print "# Repartition script #"
ui_print "# Mi 3W /system 1.2G #"
ui_print "# only! #"
ui_print "###########################"
ui_print ""
ui_print "Unmounting systems partiton..."
umount -l /system
umount -l /system1
umount -l /dev/block/mmcblk0p25
umount -l /dev/block/mmcblk0p26
ui_print ""
ui_print "WARNING! System is ready, repartitioning will start in
2 seconds"
sleep 2
ui_print ""
ui_print "Removing partitions..."
parted /dev/block/mmcblk0 rm 25
parted /dev/block/mmcblk0 rm 26
ui_print "Removing partitions...COMPLETED"
ui_print ""
ui_print "Creating new partitions..."
parted /dev/block/mmcblk0 mkpart primary 403MB 1740MB
parted /dev/block/mmcblk0 mkpart primary 1740MB 1745MB
parted /dev/block/mmcblk0 name 25 system
parted /dev/block/mmcblk0 name 26 system1
ui_print "Creating new partitions...COMPLETED"
ui_print ""
ui_print "Unmounting systems partitions again..."
umount -l /system
umount -l /system1
umount -l /dev/block/mmcblk0p25
umount -l /dev/block/mmcblk0p26
ui_print "Unmounting systems partitions again...COMPLETED"
ui_print ""
ui_print "Formatting new partitions..."
mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p25
mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p26
ui_print "Formatting new partitions...COMPLETED."
ui_print ""
ui_print "ALL DONE!..."
ui_print ""
ui_print "Rebooting to recovery in 5 seconds..."
ui_print "Thanks to forumber2 for his original GT-i9300
repartition script"
sleep 5
reboot recovery
fi
Follow info:
Code:
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 2048 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 24576 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 780 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8 mmcblk0p17
179 18 16384 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 512 mmcblk0p20
179 21 512 mmcblk0p21
179 22 1556480 mmcblk0p22
179 23 819200 mmcblk0p23
179 24 26714112 mmcblk0p24
179 27 24576 mmcblk0p27
179 28 3072 mmcblk0p28
179 29 8 mmcblk0p29
179 30 32768 mmcblk0p30
179 31 32768 mmcblk0p31
259 0 512 mmcblk0p32
259 1 512 mmcblk0p33
259 2 16384 mmcblk0p34
259 3 879599 mmcblk0p35
[email protected]:/ $
Code:
[email protected]:/dev/block/platform/msm_sdcc.1/by-name # ls -l
ls -l
lrwxrwxrwx root root 2015-07-20 22:30 DDR -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2015-07-20 22:30 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-07-20 22:30 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-07-20 22:30 cache -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-07-20 22:30 drm -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-07-20 22:30 eksst -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-07-20 22:30 encrypt -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-07-20 22:30 factory -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-07-20 22:30 fota -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2015-07-20 22:30 fsg -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2015-07-20 22:30 grow -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2015-07-20 22:30 m9kefs1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-07-20 22:30 m9kefs2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-07-20 22:30 m9kefs3 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-07-20 22:30 misc -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-07-20 22:30 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-07-20 22:30 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-07-20 22:30 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-07-20 22:30 mpt -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2015-07-20 22:30 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-07-20 22:30 recovery -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2015-07-20 22:30 reserved -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2015-07-20 22:30 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-07-20 22:30 rpmbak -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2015-07-20 22:30 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-07-20 22:30 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-07-20 22:30 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-07-20 22:30 sns -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-07-20 22:30 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-07-20 22:30 system -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-07-20 22:30 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-07-20 22:30 tzbak -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2015-07-20 22:30 userdata -> /dev/block/mmcblk0p24
[email protected]:/dev/block/platform/msm_sdcc.1/by-name #
Code:
[email protected]:/dev/block $ cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,
data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,node
v,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,no
dev,noatime,noauto_da_alloc,data=ordered 0 0
[email protected]:/dev/block $
Click to expand...
Click to collapse
@shimp208 and @jazzespresso maybe you guys could please help me? I am desperate!
Hi there,
I've the same problem, recovery is in mmcblk0, someone can help me please ? I can't find any solutions.
AndroGeek
Partion info of a my 6735 rooted android device
How can I get "dumchar_info", or "Part_Name ,Size ,StartAddr,Type,Map,To" info with adb command of a rooted mt6735 device with 5.1 lollipop? Thanks a lot in anticipation.