Hello,
Using adb pull to recursively copy directories skips files for me. Is this the intended behavior, and if so is there any way to fix it?
Eg,
adb pull /data \bak
Directory of C:\bak
03/22/2013 12:38 PM <DIR> .
03/22/2013 12:38 PM <DIR> ..
03/22/2013 12:38 PM <DIR> .uci
03/22/2013 12:38 PM <DIR> clipboard
03/22/2013 12:38 PM <DIR> misc
03/22/2013 12:38 PM <DIR> system
but there are definitely other directories in /data, including /data/data
adb can see these other directories
>adb ls /data
000041f9 00001000 51468752 .
000041ed 00000000 5146874a ..
000041f8 00001000 00000000 lost+found
000041fd 00001000 514cb171 system
000041f9 00001000 4d1eb514 dbdata
000041fd 00001000 5136df0c clipboard
000041ff 00001000 51468758 .uci
000041e8 00001000 4d1eb514 dontpanic
000041f9 00001000 4d1eb514 gps
000043f9 00001000 503ecdc9 misc
000041f8 00001000 4d1eb547 wifi
000041f9 00001000 4d1eb515 local
000041f9 00002000 51455838 data
000041f9 00001000 4d1eb514 app-private
000041f9 00001000 512d0ac7 app
and the weird thing is if I specificy subdirectories adb will copy them, e.g., I can do adb pull /data/data . So I take this to mean adb isn't skipping them for some reason like attributes, permissions, or their being in use. But why doesn't pulling the parent directory pull all these subdirectories if "pull" is supposed to be recucrive (and why does it pull some subdirectories)? Thanks for any tips guys.
AW: [Q] adb pull behavior
Did you already try the following:
adb pull /data/ c:\bak
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Did you already try the following:
adb pull /data/ c:\bak
Click to expand...
Click to collapse
you mean with trailing backslash and the root c specified? yeah, but no difference. still misses a bunch of files and subdirs (which it gets if I specify them directly).
Can you use the command "adb backup" (details here) to acheve your goal?
UPDATE on 09/23:
Thanks Modding.MyMind for all the hard work!
Finally our beloved MT2-L03 have TWRP recovery...Mission Accomplished!!
Please go here for the recovery thread:
http://forum.xda-developers.com/showthread.php?t=2885144
======================
Now we have the phone rooted, before I dare to try anything dangerous, I really hope we can have a recovery first.
Following is the partition of our phone
Code:
[email protected]:/dev/block/platform/msm_sdcc.1/by-name $ ls -l |sort -k 7
lrwxrwxrwx root root 1970-01-01 07:14 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 07:14 modemst2 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-01 07:14 modem -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-01 07:14 fsg -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-01 07:14 fsc -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-01 07:14 ssd -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-01 07:14 log -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-01 07:14 bkbootup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-01 07:14 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-01 07:14 boot -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-01 07:14 recovery -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-01 07:14 sdi -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 07:14 cust -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-01 07:14 cache -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-01 07:14 misc -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-01 07:14 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-01 07:14 userdata -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-01 07:14 grow -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-01 07:14 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 07:14 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 07:14 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 07:14 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 07:14 pad -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-01 07:14 oeminfo -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 07:14 modemst1 -> /dev/block/mmcblk0p9
And I already dd them out as backup, following is their dd out file size:
Code:
09/05/2014 01:01 PM 524,288 mmcblk0p1.img
09/05/2014 01:02 PM 4,194,304 mmcblk0p10.img
09/05/2014 01:02 PM 100,663,296 mmcblk0p11.img
09/05/2014 01:02 PM 4,194,304 mmcblk0p12.img
09/05/2014 01:03 PM 1,024 mmcblk0p13.img
09/05/2014 01:03 PM 8,192 mmcblk0p14.img
09/05/2014 01:03 PM 33,554,432 mmcblk0p15.img
09/05/2014 01:03 PM 67,108,864 mmcblk0p16.img
09/05/2014 01:03 PM 8,388,608 mmcblk0p17.img
09/05/2014 01:03 PM 12,582,912 mmcblk0p18.img
09/05/2014 01:03 PM 16,777,216 mmcblk0p19.img
09/05/2014 01:01 PM 32,768 mmcblk0p2.img
09/05/2014 01:04 PM 268,435,456 mmcblk0p20.img
09/05/2014 01:04 PM 201,326,592 mmcblk0p21.img
09/05/2014 01:05 PM 4,194,304 mmcblk0p22.img
09/05/2014 01:06 PM 1,073,741,824 mmcblk0p23.img
09/05/2014 02:34 PM 0 mmcblk0p24_toolarge.txt
09/05/2014 02:34 PM 0 mmcblk0p25_toolarge.txt
09/05/2014 01:01 PM 32,768 mmcblk0p3.img
09/05/2014 01:01 PM 512,000 mmcblk0p4.img
09/05/2014 01:01 PM 512,000 mmcblk0p5.img
09/05/2014 01:02 PM 5,726,208 mmcblk0p6.img
09/05/2014 01:02 PM 1,048,576 mmcblk0p7.img
09/05/2014 01:02 PM 67,108,864 mmcblk0p8.img
09/05/2014 01:02 PM 4,194,304 mmcblk0p9.img
09/05/2014 02:17 PM 4,194,304 mmcblk0rpmb.img
09/05/2014 02:34 PM 0 mmcblk1p1_toolarge_4GB.txt
So, maybe someone can help us build a recovery image? I like to learn, but really don't have much experience on these.
http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device
That might help you out if you haven't already looked into it.
Thanks, I will take a look that.
Right now, I am using their online builder:
http://builder.clockworkmod.com/
Still I am wondering, how that online builder (or the manual compile steps in your link) decide which partition is system/data/cache etc? Is that device-by-name is universal?
Also, is that safe to flash the recovery? if recovery image is bad, am I be able to boot normally to phone, and use adb to restore stock recovery?
Thanks.
Man, I wish I could help but I don't know anything about this.
If there's a CWM forum, try asking there. Hopefully we can find someone to help us.
xordos said:
Thanks, I will take a look that.
Right now, I am using their online builder:
http://builder.clockworkmod.com/
Still I am wondering, how that online builder (or the manual compile steps in your link) decide which partition is system/data/cache etc? Is that device-by-name is universal?
Also, is that safe to flash the recovery? if recovery image is bad, am I be able to boot normally to phone, and use adb to restore stock recovery?
Thanks.
Click to expand...
Click to collapse
I will answer my own question..
That online builder looks like is not working.
The build process will extract recovery.fstab from the the ramdisk image inside the recovery image.
The local build of the recovery did went through, but the whole process is so complex, and I have never done this before. I am pretty sure I will miss here and there. So my confident of the generated recovery.img is very low.
-rwxr--r-- 1 16777216 Sep 6 18:36 recovery_mmcblk0p19.img
-rw-r--r-- 1 8456192 Sep 6 21:53 recovery_new.img
Anyway, following command can flash the recovery easily.
Code:
fastboot.exe devices
fastboot.exe flash recovery recovery.img
The things is, with my recovery image flashed, it can't enter the recovery mode, following is detail:
1. "fastboot flash" to flash recovery.
2. hold 10 seconds to reboot ( or use fastboot reboot)
3. The phone will boot normally into android OS.
4. Then I shutdown the phone.
5. Before it completely shutdown, it showed Huawei logo once as usually, then it show the BootLoader screen. means the phone won't shut off completly.
(or In step 4. I use usb adb cmd "adb reboot recovery" it will same result in step 5)
If I flash back the original recovery in step 1, then in step 4, "adb reboot recovery" will easily reboot into recovery without hold any key. So keys holding is not a issue here.
So, I am not sure "always go into bootloader" means what, the recovery image is bad? or the phone has some checksum/sig check before it load recovery.
Anyway, I didn't try fastboot flash system, but looks like fastboot is one way to flash some partitions, following is the help:
Code:
...
flashall flash boot, system, and if found,
recovery, tos
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
.
I also searched some other Chinese varies Mate2 ROM, they are very differnt, the CPU is different, and the kernel command line (which is configured in the recovery partition) is quite different, so I doubt MT2_L03 can use recovery image from others like MT2_C00.
For ROM Developers, please see attachment for the device files.
I only updated BoardConfig.mk on those partition size. ( I double checked the size from /proc/partitions as well as the dd file size, they matching)
The recovery.fstab is original that extract from stock recovery image by the build tool automatically.
I am build on CM souce code branch 10.2.
Please let me know if you have any idea.
Without a working recovery to backup/restore, Having root on the phone is pretty dangerous. That's also the reason I am still not try xposed on my phone yet.
Hope we can have a working recovery soon.
Thanks.
I wouldn't bother with CWM.. Personal preference I guess. I would aim to build TWRP. Also, sync OmniRom. TWRP is officially located within the OmniRom source now.
http://docs.omnirom.org/Setting_Up_A_Compile_Environment
Can someone pull me their boot.img, recovery.img, build.prop and collect all of their "getprop" information. Zip it all up and throw it up on dev host or another cloud service. Would like to review.
hey, i am outside right now,will upload tonight
EDIT: @Modding.MyMind
uploaded....Here is the list of files in the zip:
09/05/2014 01:03 PM 12,582,912 boot_mmcblk0p18.img
09/07/2014 04:19 PM 13,109 build.prop
09/06/2014 02:17 AM 2,966 device_mount.txt
09/06/2014 02:18 AM 9,104 device_names.txt
09/07/2014 04:19 PM 20,936 getprop.txt
09/07/2014 04:14 PM 1,168 md5sum.txt
09/07/2014 04:18 PM 1,194 proc_partition.txt
09/06/2014 06:36 PM 16,777,216 recovery_mmcblk0p19.img
File location:
https://drive.google.com/file/d/0B-nJFDpWA4MdaWFEckVfUERSRk0/edit?usp=sharing
md5: c73da57ebc630a244ec86f15937251ea mt2_l03_upload.zip
Please let me know if you need anything else.
Thanks a lot.
You guys are simply amazing! :good:
Thanks, will be syncing OmniRom to my computer tomorrow after work. Meanwhile, will be looking over the contents inside the zip. Don't remove them on the cloud just yet lol. Won't be able to download it until tomorrow. I will let you know when that happens so if you wish to remove them later on you may.
@xordos and @ScoobSTi, can either of you confirm that you can currently install a recovery to your device now that ya'll are unlocked. Pull your stock recovery and in turn try to install that same recovery to see if the screen reports back successful.
yes, I already did that when i test my cwm recovery. The phone will boot normally into OS, so I dd out new partition image, and verified using bvi or other binary editor. Then i can restore stock recovery back. pls see post #6 for details.
xordos said:
yes, I already did that when i test my cwm recovery. The phone will boot normally into OS, so I dd out new partition image, and verified using bvi or other binary editor. Then i can restore stock recovery back. pls see post #6 for details.
Click to expand...
Click to collapse
Awesome, great news. Just wanted to verify so I had reassurance that if my first TWRP build is buggy you or another tester could get back to your stock recovery .
@xordos, Syncing OmniROm now. Downloaded your zip that you provided. Will begin my work.
Quick question, is the storage sdcard path located at /data/media, or no? Need to know. Reviewing the zip I got and it was giving me mixed feelings on that issue.
Almost done building the device configuration folder.
---------- Post added at 02:33 PM ---------- Previous post was at 02:32 PM ----------
Also, what is ya'lls device resolution? Need that as well lol.
Modding.MyMind said:
Quick question, is the storage sdcard path located at /data/media, or no? Need to know. Reviewing the zip I got and it was giving me mixed feelings on that issue.
Almost done building the device configuration folder.
---------- Post added at 02:33 PM ---------- Previous post was at 02:32 PM ----------
Also, what is ya'lls device resolution? Need that as well lol.
Click to expand...
Click to collapse
/storage/sdcard0 - I think
720x1280
aragon257 said:
/storage/sdcard0 - I think
720x1280
Click to expand...
Click to collapse
Thanks. Makes it easier for me.
---------- Post added at 02:54 PM ---------- Previous post was at 02:52 PM ----------
Is this device CDMA or GSM? Looking at it tells me it is GSM but wanted to verify with you guys.
---------- Post added at 03:00 PM ---------- Previous post was at 02:54 PM ----------
I'm also not seeing a partition for the internal sdcard. I have to assume it's fused with /data/media. Will hit up the build.prop to verify. It will tell me there. And I see there is an external sdcard as well (up to 64 gigs). Useful info for building.
---------- Post added at 03:02 PM ---------- Previous post was at 03:00 PM ----------
And I see it is CDMA with no SIM card according to the build.prop. Also, just so you guys know, the internal sdcard is in fact fused with /data/media.
Modding.MyMind said:
Thanks. Makes it easier for me.
---------- Post added at 02:54 PM ---------- Previous post was at 02:52 PM ----------
Is this device CDMA or GSM? Looking at it tells me it is GSM but wanted to verify with you guys.
---------- Post added at 03:00 PM ---------- Previous post was at 02:54 PM ----------
I'm also not seeing a partition for the internal sdcard. I have to assume it's fused with /data/media. Will hit up the build.prop to verify. It will tell me there. And I see there is an external sdcard as well (up to 64 gigs). Useful info for building.
---------- Post added at 03:02 PM ---------- Previous post was at 03:00 PM ----------
And I see it is CDMA with no SIM card according to the build.prop. Also, just so you guys know, the internal sdcard is in fact fused with /data/media.
Click to expand...
Click to collapse
It is GSM ..Also, very few 64GB microSD cards are compatible with this device. 32GB is preferred.
USHAM2 said:
It is GSM ..Also, very few 64GB microSD cards are compatible with this device. 32GB is preferred.
Click to expand...
Click to collapse
Thanks, knowing if it were GSM or CDMA was very important to me. I looked back at the build.prop and saw that is in fact GSM. Read the info wrong lol. It happens . Working to complete the device configuration before the syncing is complete so I can jump straight in to building TWRP for you guys.
So normally, nexus devices have easy partition names... For example, the /dev/block/platform/by-name directory contains things like system, boot, recovery, data, modem, efs, etc.. Well here is the result of "ls -al" of the partition directory on my nexus 9.
[email protected]_lte:/ # ls -al /dev/block/platform/sdhci-tegra.3/by-name
lrwxrwxrwx root root 2014-12-30 12:10 APP -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2014-12-30 12:10 CAC -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2014-12-30 12:10 CDR -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-12-30 12:10 DIA -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-12-30 12:10 DTB -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-12-30 12:10 EF1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-12-30 12:10 EF2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-12-30 12:10 EKS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-12-30 12:10 EXT -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-12-30 12:10 FST -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-12-30 12:10 GPT -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2014-12-30 12:10 KEY -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-12-30 12:10 LNX -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-12-30 12:10 MD1 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2014-12-30 12:10 MD2 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2014-12-30 12:10 MFG -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-12-30 12:10 MSC -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-12-30 12:10 NCT -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-12-30 12:10 OTA -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2014-12-30 12:10 PG1 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-12-30 12:10 PST -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2014-12-30 12:10 RCA -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-12-30 12:10 RV1 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-12-30 12:10 RV2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-12-30 12:10 RV3 -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2014-12-30 12:10 SER -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-12-30 12:10 SOS -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-12-30 12:10 SP1 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-12-30 12:10 TOS -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-12-30 12:10 UDA -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2014-12-30 12:10 VNR -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-12-30 12:10 WB0 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-12-30 12:10 WDM -> /dev/block/mmcblk0p7
My question is, which is which? How can i tell which is the recovery block, system block, recovery and so on? Is there a list of translations for these partition names? Thanks
Not sure what need you are trying to fulfill but read this http://www.all-things-android.com/content/review-android-partition-layout as a starter.
peterk-1 said:
Not sure what need you are trying to fulfill but read this http://www.all-things-android.com/content/review-android-partition-layout as a starter.
Click to expand...
Click to collapse
For example, nexus 5 has a symlinks like /dev/block/platform/msm_sdcc.1/by-name/boot that is linked to /dev/block/mmcblk0p19. Clearly this is the kernel block. Because its called "boot". Right? So, the nexus 9 is different from most other nexus devices. The by-name folder has 3 character names that dont really translate to "boot" or "system" or "recovery". It has names like "dia" and "vnr". I know that the "vnr" is the Vendor block. So which one is the "boot" block, is it "dia", or is it"svn". Do you understand what im asking? How in the heck is one supposed to figure out which block device is which???
bynarie said:
How in the heck is one supposed to figure out which block device is which???
Click to expand...
Click to collapse
The "clever ****" reply is "google" but I've found that many pages go silent on the key issue and and others are way over my head.
Some pointers:
Reboot your device and look at the dmesg log and :
Search "target=" (6 hits in 1 file)
\\CORSAIR\CorsairG\junk\dmesg.txt (6 hits)
Line 1077: <14>[ 5.168004] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/APP,target=/system,type=ext4)=0
Line 1080: <14>[ 5.172727] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/VNR,target=/vendor,type=ext4)=0
Line 1114: <14>[ 5.507472] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/CAC,target=/cache,type=ext4)=0
Line 1127: <14>[ 5.527126] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/UDA,target=/data,type=f2fs)=-1
Line 1145: <14>[ 5.550663] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/UDA,target=/data,type=ext4)=-1
Line 1488: <14>[ 111.676664] fs_mgr: __mount(source=/dev/block/dm-0,target=/data,type=f2fs)=0
http://newandroidbook.com/Articles/Nexus9.html - note "tegra" names and Nvidia Shield.
https://android.googlesource.com/device/htc/flounder/+/android-5.0.2_r1/fstab.flounder
thanks!
peterk-1 said:
The "clever ****" reply is "google" but I've found that many pages go silent on the key issue and and others are way over my head.
Some pointers:
Reboot your device and look at the dmesg log and :
Search "target=" (6 hits in 1 file)
\\CORSAIR\CorsairG\junk\dmesg.txt (6 hits)
Line 1077: <14>[ 5.168004] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/APP,target=/system,type=ext4)=0
Line 1080: <14>[ 5.172727] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/VNR,target=/vendor,type=ext4)=0
Line 1114: <14>[ 5.507472] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/CAC,target=/cache,type=ext4)=0
Line 1127: <14>[ 5.527126] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/UDA,target=/data,type=f2fs)=-1
Line 1145: <14>[ 5.550663] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/UDA,target=/data,type=ext4)=-1
Line 1488: <14>[ 111.676664] fs_mgr: __mount(source=/dev/block/dm-0,target=/data,type=f2fs)=0
http://newandroidbook.com/Articles/Nexus9.html - note "tegra" names and Nvidia Shield.
https://android.googlesource.com/device/htc/flounder/+/android-5.0.2_r1/fstab.flounder
Click to expand...
Click to collapse
Thanks!! That fstab flounder page is a really good starting list of exactly what i was looking for. {{Presses Thanks Button}}
Is it possible to delete some partitions like system image and resize data partition?
wizzardsk said:
Is it possible to delete some partitions like system image and resize data partition?
Click to expand...
Click to collapse
No, system image system is a partition with android system. Other partitions are too small for redesigning to make sense.
Vartom said:
No, system image system is a partition with android system. Other partitions are too small for redesigning to make sense.
Click to expand...
Click to collapse
I am not sure about the name, but there are 2 system partitions on nexus 9 that i have not seen on other devices.
wizzardsk said:
I am not sure about the name, but there are 2 system partitions on nexus 9 that i have not seen on other devices.
Click to expand...
Click to collapse
you are mistaken, he has one system partitions (APP).
What is this?
wizzardsk said:
What is this?
Click to expand...
Click to collapse
Same thing. One is a regular backup, one is to backup as an image (system.img) pick the way you want to backup.
So both system partitions are necessary?
Edit: i understand, so there is only 1 system partition
wizzardsk said:
So both system partitions are necessary?
Edit: i understand, so there is only 1 system partition
Click to expand...
Click to collapse
Yes there is only 1 system partition. TWRP is offering 2 ways to make a system backup, either a standard backup, or backup as an image.