Hello,
I picked up a Meizu MX2 while I was in Hong Kong last week. I've succesfully rooted the device, but now I'm trying to compile CWM for it and need to save a boot.img file.
Unfortunately, I can't seem to find the boot partition at all. Any ideas would be appreciated.
Code:
1|[email protected]:/ # cat /proc/partitions
major minor #blocks name
7 0 34335 loop0
7 1 13545 loop1
7 2 34335 loop2
7 3 9387 loop3
179 0 31162368 mmcblk0
179 1 27951104 mmcblk0p1
179 2 778240 mmcblk0p2
179 3 2097152 mmcblk0p3
179 4 204800 mmcblk0p4
254 0 34335 dm-0
254 1 13545 dm-1
254 2 34335 dm-2
254 3 9387 dm-3
Code:
127|[email protected]:/ # mount
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
/dev/block/mmcblk0p2 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p3 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p4 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/dm-0 /mnt/asec/com.ea.games.nfs13_row-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-1 /mnt/asec/com.touchtype.swiftkey-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-2 /mnt/asec/com.vectorunit.green-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/vold/179:1 /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:1 /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
/dev/block/dm-3 /mnt/asec/com.wordsmobile.musichero-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
Code:
[email protected]:/ # df
Filesystem Size Used Free Blksize
/dev 929M 32K 929M 4096
/mnt/asec 929M 0K 929M 4096
/mnt/obb 929M 0K 929M 4096
/system 748M 289M 458M 4096
/data 1G 629M 1G 4096
/cache 196M 10M 186M 4096
/mnt/asec/com.ea.games.nfs13_row-1 32M 31M 1M 4096
/mnt/asec/com.touchtype.swiftkey-1 13M 10M 2M 4096
/mnt/asec/com.vectorunit.green-1 32M 31M 1M 4096
/mnt/sdcard 26G 2G 24G 16384
/mnt/secure/asec 26G 2G 24G 16384
/mnt/asec/com.wordsmobile.musichero-1 9M 7M 1M 4096
Code:
[email protected]:/ # ls -la
drwxr-xr-x root root 2013-01-07 18:28 acct
drwxrwx--- system cache 2013-01-07 06:16 cache
dr-x------ root root 2013-01-07 18:28 config
lrwxrwxrwx root root 2013-01-07 18:28 d -> /sys/kernel/debug
drwxrwx--x system system 2012-12-29 08:14 data
-rw-r--r-- root root 125 1970-01-01 07:00 default.prop
drwxr-xr-x root root 2013-01-07 18:28 dev
lrwxrwxrwx root root 2013-01-07 18:28 etc -> /system/etc
-rwxr-x--- root root 105152 1970-01-01 07:00 init
-rwxr-x--- root root 2344 1970-01-01 07:00 init.goldfish.rc
-rwxr-x--- root root 7139 1970-01-01 07:00 init.mx2.rc
-rwxr-x--- root root 2145 1970-01-01 07:00 init.mx2.usb.rc
-rwxr-x--- root root 19772 1970-01-01 07:00 init.rc
-rwxr-x--- root root 1637 1970-01-01 07:00 init.trace.rc
-rwxr-x--- root root 3915 1970-01-01 07:00 init.usb.rc
drwxrwxr-x root system 2013-01-07 18:28 mnt
dr-xr-xr-x root root 1970-01-01 07:00 proc
drwx------ root root 2012-12-19 16:28 root
drwxr-x--- root root 1970-01-01 07:00 sbin
lrwxrwxrwx root root 2013-01-07 18:28 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2013-01-07 18:28 sys
drwxr-xr-x root root 2012-12-30 23:01 system
-rw-r--r-- root root 272 1970-01-01 07:00 ueventd.goldfish.rc
-rw-r--r-- root root 1703 1970-01-01 07:00 ueventd.mx2.rc
-rw-r--r-- root root 3879 1970-01-01 07:00 ueventd.rc
lrwxrwxrwx root root 2013-01-07 18:28 vendor -> /system/vendor
Any luck with this?
finding boot image partition
[
QUOTE=bakedjake;36394241]Hello,
I picked up a Meizu MX2 while I was in Hong Kong last week. I've succesfully rooted the device, but now I'm trying to compile CWM for it and need to save a boot.img file.
Unfortunately, I can't seem to find the boot partition at all. Any ideas would be appreciated.
179 1 27951104 mmcblk0p1
179 2 778240 mmcblk0p2
179 3 2097152 mmcblk0p3
179 4 204800 mmcblk0p4
/dev/block/mmcblk0p2 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p3 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p4 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
Click to expand...
Click to collapse
Based on the information you have provided, you have four visible partitions on the flash. With three used by system, data, and cache, I would expect the remaining partition to be boot ( mmcblk0p1 ). I would do a dump of all partitions as back-ups for a future restore if necessary.
dump the partitions with "cat /dev/block/mmcblk0p1 > /sdcard/mmcblk0p1.img"
substitute the names of the partitions accordingly. I recommend you install an external sdcard larger than the built in and save the images there.
If you do look at the image files with a hex editor, the boot image partition will have the boot command string usually in the beginning of the file.
Good luck
mccabet said:
[
Based on the information you have provided, you have four visible partitions on the flash. With three used by system, data, and cache, I would expect the remaining partition to be boot ( mmcblk0p1 ). I would do a dump of all partitions as back-ups for a future restore if necessary.
dump the partitions with "cat /dev/block/mmcblk0p1 > /sdcard/mmcblk0p1.img"
substitute the names of the partitions accordingly. I recommend you install an external sdcard larger than the built in and save the images there.
If you do look at the image files with a hex editor, the boot image partition will have the boot command string usually in the beginning of the file.
Good luck
Click to expand...
Click to collapse
download the boot partition app from google play and click on the middle lower button after open then you can click on the partitions to tell you the label number and what it is ass boot or recovery or sbl1
michaelway67 said:
download the boot partition app from google play and click on the middle lower button after open then you can click on the partitions to tell you the label number and what it is ass boot or recovery or sbl1
Click to expand...
Click to collapse
What is the name of the app?
mccabet said:
[
Based on the information you have provided, you have four visible partitions on the flash. With three used by system, data, and cache, I would expect the remaining partition to be boot ( mmcblk0p1 ). I would do a dump of all partitions as back-ups for a future restore if necessary.
dump the partitions with "cat /dev/block/mmcblk0p1 > /sdcard/mmcblk0p1.img"
substitute the names of the partitions accordingly. I recommend you install an external sdcard larger than the built in and save the images there.
If you do look at the image files with a hex editor, the boot image partition will have the boot command string usually in the beginning of the file.
Good luck
Click to expand...
Click to collapse
I agree. This is the correct method. No need for crappy apps from the playstore for such a simple proceedure. And you remain in control.
yes but some rather play it safe and not mess with commands but the app is partition table
here
mccabet said:
[
Based on the information you have provided, you have four visible partitions on the flash. With three used by system, data, and cache, I would expect the remaining partition to be boot ( mmcblk0p1 ). I would do a dump of all partitions as back-ups for a future restore if necessary.
dump the partitions with "cat /dev/block/mmcblk0p1 > /sdcard/mmcblk0p1.img"
substitute the names of the partitions accordingly. I recommend you install an external sdcard larger than the built in and save the images there.
If you do look at the image files with a hex editor, the boot image partition will have the boot command string usually in the beginning of the file.
Good luck
Click to expand...
Click to collapse
This seems a pretty difficult way to go about this.
The easiest way is to use adb:
Code:
adb pull /tmp/recovery.log
If using Windows and you want to pull out to your desktop
Code:
adb pull /tmp/recovery.log C:\Users\Your Name\Desktop
Open the recovery text file using notepad++ (you can use notepad but it's not at all organized) and the first dozen lines or so tell you specifically which each partition is (boot, data, system, cache, etc) relative to it's mmcblk0p_ . This was the only way I could find my boot partition after trying every cat /proc, fdisk, parted, command I could think of. Hope it helps!
Try looking at /proc/mtd , on some devices it usually contains names and descriptions of each MTD device present on the system.
Hello XDA-Developers!
I want to install Back Track 5 ARM in my AllWinner A10 based tablet, I followed the lesson for Galaxy and I downloaded the boot script for Galaxy and the bt5.img(3.25G). I changed some of the codes to launch BT5 in external sdcard and suit my ROM,then launched it, only to find some errors. Well, the source code of the boot script(modified by myself to suit my device) like this:
perm=$(id|busybox cut -b 5)
if [ "$perm" != "0" ];then echo "This Script Needs Root! Type : su";exit;fi
mount -o remount,rw /dev/block/mmcblk0p1 /system
export kit=/mnt/extsd/BT5
export bin=/system/bin
export mnt=/mnt
mkdir -p $mnt
export PATH=$bin:/usr/bin:/usr/local/bin:/usr/sbin:/bin:/usr/local/sbin:/usr/games:$PATH
export TERM=linux
export HOME=/
if [ -b /dev/loop2 ]; then
echo "Loop device exists"
else
busybox mknod /dev/loop2 b 7 0
fi
busybox mount -o loop,noatime -t extsd $kit/bt5.img $mnt
busybox mount --bind /dev/pts $mnt/dev/pts
busybox mount --bind /proc $mnt/proc
busybox mount --bind /sys $mnt/sys
busybox sysctl -w net.ipv4.ip_forward=1
echo "nameserver 8.8.8.8" > $/etc/resolv.conf
echo "127.0.0.1 localhost bt5" > $/etc/hosts
busybox chroot $/bin/bash
echo "Shutting down BackTrack ARM For Xoom"
umount $/dev/pts
umount $/proc
umount $/sys
umount $mnt
when I launch the script(bootbtV) in Terminal Emulator, only to find some errors like this:
[email protected]:/ $ su
[email protected]:/ # cd mnt/extsd/BT5
[email protected]:/mnt/extsd/BT5 # sh bootbtV
Loop device exists
mount: mounting /dev/loop8 on /mnt failed: No such device
mount: mounting /dev/pts on /mnt/dev/pts failed: No such file or directory
mount: mounting /proc on /mnt/proc failed: No such file or directory
mount: mounting /sys on /mnt/sys failed: No such file or directory
net.ipv4.ip_forward = 1
bootbtV[23]: can't create $/etc/resolv.conf: No such file or directory
bootbtV[24]: can't create $/etc/hosts: No such file or directory
chroot: can't change root directory to $/bin/bash: No such file or directory
Shutting down BackTrack ARM For Xoom
failed: No such file or directory
failed: No such file or directory
failed: No such file or directory
failed: Invalid argument
1|[email protected]:/mnt/extsd/BT5 #
Well, In my opinion, according to the errors "No such file or directory", I think it is the difference between my device and Galaxy that causes the errors. In my device, the file structure is different from what the boot script means, such is the file structure of my device's root directory:
drwxr-xr-x root root 2013-01-16 11:22 acct
drwxrwx--- system cache 2013-01-16 09:51 cache
dr-x------ root root 2013-01-16 11:22 config
lrwxrwxrwx root root 2013-01-16 11:22 d -> /sys/kernel/debug
drwxrwx--x system system 2013-01-13 17:14 data
-rw-r--r-- root root 116 1970-01-01 08:00 default.prop
drwxr-xr-x root root 2013-01-16 11:27 dev
lrwxrwxrwx root root 2013-01-16 11:22 etc -> /system/etc
-rwxr-x--- root root 105268 1970-01-01 08:00 init
-rwxr-x--- root root 2344 1970-01-01 08:00 init.goldfish.rc
-rwxr-x--- root root 19030 1970-01-01 08:00 init.rc
-rwxr-x--- root root 2644 1970-01-01 08:00 init.sun4i.rc
-rwxr-x--- root root 2230 1970-01-01 08:00 init.sun4i.usb.rc
-rwxr-x--- root root 1637 1970-01-01 08:00 init.trace.rc
-rwxr-x--- root root 3915 1970-01-01 08:00 init.usb.rc
-rwxr-x--- root root 1536000 1970-01-01 08:00 initlogo.rle
drwxrwxr-x root system 2013-01-16 11:22 mnt
-rw-r--r-- root root 782728 1970-01-01 08:00 nand.ko
dr-xr-xr-x root root 1970-01-01 08:00 proc
drwx------ root root 2012-10-11 13:57 root
drwxr-x--- root root 1970-01-01 08:00 sbin
lrwxrwxrwx root root 2013-01-16 11:22 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2013-01-16 11:22 sys
drwxr-xr-x root root 2013-01-13 17:59 system
-rw-r--r-- root root 272 1970-01-01 08:00 ueventd.goldfish.rc
-rw-r--r-- root root 3879 1970-01-01 08:00 ueventd.rc
-rw-r--r-- root root 1313 1970-01-01 08:00 ueventd.sun4i.rc
lrwxrwxrwx root root 2013-01-16 11:22 vendor -> /system/vendor
I think, the only way to launch BT5 in my device successfully is to modify the boot script so that it can suit my device, especially the file structure. But I am a green hand in Linux, I don't know what does some of the codes mean, if you are good at Linux script, would you please give me some advice?
Thank you very much!
Hi, someone else get this problem?
my galaxy p7500 have a peculiar problem.
it boots and works, but when i install some app or unnistal, create/delete file or do a factory reset.
all back to the old defect state, like this tab gets frozen in time.
So, i try to use odin, and then:
use the files:
P7500_P7510_android_fastboot_emmc_full_p4_16G_32G.pit
and
stock rom P7500ZTOLP4_P7500UBLP9_P7500UBLP3_HOME.tar
but when I put to flash, it goes and fail, this is what show on the tab: pls see the pics
I think I have a permissions trouble.
The tablet is working for about 10 minutes, then stop, if i check the volume space the tab freeze.
so... I'm using adb from recovery, and acessing tab's shell.
If I use : ll -a
shows->
drwxr-xr-x root root 2015-08-02 15:23 cache
drwxr-xr-x root root 1970-01-01 00:00 data
-rw-r--r-- root root 2302 1970-01-01 00:00 default.prop
drwxr-xr-x root root 2015-08-02 15:23 dev
drwxr-xr-x root root 2015-08-02 15:23 efs
drwxr-xr-x root root 1970-01-01 00:00 etc
-rwxr-x--- root root 148088 1970-01-01 00:00 init
-rwxr-x--- root root 1431 1970-01-01 00:00 init.rc
drwxr-xr-x root root 1970-01-01 00:00 lib
-rw-r--r-- root root 1861 1970-01-01 00:00 lpm.rc
drwxr-xr-x root root 2015-08-02 15:23 preload
dr-xr-xr-x root root 1970-01-01 00:00 proc
drwxr-xr-x root root 1970-01-01 00:00 res
drwx------ root root 2012-10-15 13:06 root
drwxr-x--- root root 1970-01-01 00:00 sbin
drwxr-xr-x root root 2015-08-02 15:23 sdcard
drwxr-xr-x root root 2015-08-02 15:23 sdcard1
drwxr-xr-x root root 2015-08-02 15:23 sys
drwxr-xr-x root root 2014-02-10 03:52 system
drwxr-xr-x root root 2015-08-02 15:23 tmp
-rw-r--r-- root root 272 1970-01-01 00:00 ueventd.goldfish.rc
-rw-r--r-- root root 1276 1970-01-01 00:00 ueventd.p3.rc
-rw-r--r-- root root 3825 1970-01-01 00:00 ueventd.rc
I tried to usb adb sideload too, but this apear not working, it keep loading: 'update.zip"
The odin gets btc_sync error, nvflash 0x04 error,
someone know what can I do??
i got this using dmesg, someone can bring some light?
3>[ 3.342022] init: [disk_config] ext_check -> /system/bin/e2fsck -v -y /dev/block/platform/sdhci-tegra.3/by-num/p5
<3>[ 3.469928] init: [disk_config] Error ::execute :: Error in (Status 8)
<3>[ 3.470261] init: [disk_config] Error ::* failed to check -1
<6>[ 3.492495] EXT4-fs (mmcblk0p5): recovery complete
<6>[ 3.494914] EXT4-fs (mmcblk0p5): mounted filesystem with writeback data mode. Opts: journal_async_commit,data=writeback,nodelalloc,errors=panic
<3>[ 3.496302] init: Device Encryption status is (0)!!
<3>[ 3.496402] init: [disk_config] :::: fsck -> /dev/block/platform/sdhci-tegra.3/by-num/p8 (ext4):::::
<3>[ 3.496764] init: [disk_config] ext_check -> /system/bin/e2fsck -v -y /dev/block/platform/sdhci-tegra.3/by-num/p8
<3>[ 6.611433] init: [disk_config] Error ::execute :: Error in (Status 8)
<3>[ 6.611779] init: [disk_config] Error ::* failed to check -1
First I'm on 7.1.1 LineageOS v20, I have my SD card formated using ext2 since I need 4+ GB files for TWRP backups. This works and I can create files and folder ..., however I've found that if I pull the SD card and on a computer set the permission to say 777 all is fine, but on the Phone, I can for instance create a directory using root-explorer, but can not set permission or copy files into it. If I create the folder on the computer I can copy files into it however. Next say I backup using Ti-backup to the external SDcard it works fine, but of I install a new ROm I can not access the previous backup files. I can not change the permissions on the file to 777 either from a terminal.
Really this is what upsets me, as root in a terminal I can not set permissions on a file as it does nothing, for instance on /storage/emulated/0 I have:
h918:/storage/emulated/0 # ls
drwxrwx--x 3 root sdcard_r 4096 Mar 14 19:35 .rr
-rw-rw---- 1 root sdcard_r 1369542927 Apr 1 22:28 01update.zip
-rw-rw---- 1 root sdcard_r 884357956 Apr 1 22:34 02update.zip
-rw-rw---- 1 root sdcard_r 1057588047 Apr 1 22:41 03update.zip
drwxrwx--x 2 root sdcard_r 4096 Mar 9 23:06 3DMarkAndroid
drwxrwx--x 2 root sdcard_r 4096 Mar 4 18:20 Alarms
....
as root I execute:
h918:/storage/emulated/0 # chmod 777 *.zip
h918:/storage/emulated/0 # chmod 777 *.zip
h918:/storage/emulated/0 # ls -al
drwxrwx--x 43 root sdcard_r 4096 Apr 1 22:35 .
drwx--x--x 4 root sdcard_r 4096 Jan 1 2016 ..
-rw-rw---- 1 root sdcard_r 2557 Apr 1 20:20 .bash_history
drwxrwx--x 3 root sdcard_r 4096 Mar 14 19:35 .rr
-rw-rw---- 1 root sdcard_r 1369542927 Apr 1 22:28 01update.zip
-rw-rw---- 1 root sdcard_r 884357956 Apr 1 22:34 02update.zip
-rw-rw---- 1 root sdcard_r 1057588047 Apr 1 22:41 03update.zip
drwxrwx--x 2 root sdcard_r 4096 Mar 9 23:06 3DMarkAndroid
drwxrwx--x 2 root sdcard_r 4096 Mar 4 18:20 Alarms
...
The permissions remain unchanged, why I'm root I should be able to change permissions.
looking at mount the options are:
/dev/fuse on /storage/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
The SD card looks similar:
/dev/fuse on /storage/ea8c26be-fcbc-4773-b799-5e64ef33f641 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/ea8c26be-fcbc-4773-b799-5e64ef33f641 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/ea8c26be-fcbc-4773-b799-5e64ef33f641 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
Nothing here should block ROOT from change the permissions. I simply want as root or as any root application to be able to create a directory change file permission and access data written as another root app, all of which make it possible to use the phone and backup/restore safely.
I can only assume something is blocking me form using the device the way I want and operating on files, since pulling the card to a computer allows setting 777 and then it works as I want, what I want is to set the umask to 777 for everything, as for security that can be damned as I need to be able to backup and restore safely first, something I can not do now as Tibackup can not access it's own files on restore unless I first pull the card and set the permissions on a computer, which is unacceptable.
Files created on the phone have permissions 700 or something similar, even though on the phone they are listed as having more, this explains the issue as it is not for instance: -rw-rw---- but -rw-------, however root should still be able to access the file and can not, nor can root change the settings.
ERIC