Showing posts with label Backup. Show all posts
Showing posts with label Backup. Show all posts

Saturday, 6 August 2016

Nandroid backup restored apps but not my other files



Hello guys.
So I created a Nandroid backup and went on to flash a new ROM, but didn't like it so I restored from the Nandroid backup.
All my apps with their settings have been restored, but none of my files have been restored. My Downloads folder, my Screenshots folder, a folder where I stored some nice wallpapers, and so on. None of these folders have been restored. I tried to restore it again, but it gave me the same results. Am I missing something?
Thank you.



Backup doesn't finish



Hi.
I'll try to explain this, but it's not that easy since my english isn't the best. So please, forgive me.
I have the auto-backup for the data on my Z5C, so every night, when I charge it, the backup starts, but that's it. It stops at the beginning and the only way I found to make it complete the backup is opening the notification of the backup (which says it's still doing it) and then, magically, it really starts working and doing the back up. This is so annoying for me and I have no idea on what it depends on.

Any suggestions?

Thank you



Friday, 5 August 2016

Titanium Backup question

With Titanium Backup, when you backup your apps and other files it creates a folder full of files that only it can read. When I flashed Jasmine, I copied those files to my computer and then flashed, then redownloaded Titanium Backup and moved those files as well as the license back into the correct folders. Is this the correct way to use TB, or is there a route that I am missing? It worked fine, just not sure if it is the recommended way of use or not.

Android backup apps - Titanium vs Helium?

So, these two seem to be the two most well known backup apps, and I just wanted people's opinions on them. Especially since I will likely purchase the pro/full version of the one I decide to go with.

Is any particular one better if you don't have root?

What about if you do have root?

Any difference in the amount of content they can back up?

Is there anything any of them still can't backup if you have root? I am particularly interested in app settings/data (not the apks themselves, but the actual data the apps write). I assume backing up contacts, sms, and photos/videos are a given and I wouldn't even need to ask this.

Does any particular one have better features in term of storing your backup on the cloud/google drive?

What about if you need to restore the backup to a different phone?

Any other suggestions or comments about these two? Or even other backup apps?

Tuesday, 2 August 2016

EFS Backup



I need to make an EFS backup, never have before and flashed tonnes of roms, lol. But after reading it's probably a good idea.


Currently on CM13.

However, I've run into an issue. I downloaded Terminal Emulator. I enter "su" and it says on a new line: 255|u0_a104@oneplus3:/

So I then tried to enter: dd if=/dev/block/sdf1 of=/sdcard/modemst1.bin bs=512 - and it says permission denied?

Any help? :]



Which rom has the best battery backup? Plz help!

I bought my Zuk Z1 phone one month ago and I was very upset with the battery backup of the phone for before buying I went through many videos reviews boasting the battery backup of the phone. After using the official CM 13 from the cynogenmod website I was still not satisfied. I then moved to custom rom and I am quite happy with the battery backup. I have tried Dirty Unicorn, MrColdbird Rom and right now I'm using Teamsek rom the latest one. Which Rom has the best battery backup for our device for I want to stick to only one rom less my battery will get affected. Plz help me to decide. Thank you :)

Monday, 1 August 2016

How to backup contacts with broken screen + disabled USB debugging?



Hello everybody,

my wife has just broken the screen (and appearantly the digitizer) of her S3.

Of course the USB debugging has never been enabled ever since I bought this phone for her.

So my question is this: how can I backup the contacts without a working screen and disabled USB debugging? Is there a way? Can I enable USB debugging via ADB? The ROM in question is fully stock.

Thanks in advance for any helpful insight.



Bypass backup pin Verizon Note 4



Looking for some guidance. 2 days ago my "gesture password" didn't work and the phone started asking me for the backup pin, which I really don't remember.
Tried the usual suspects for the pin, but I'm down to the last try and it says after that the phone will be wiped out.
I realize Android 6 has plugged in all previous holes, unreal that "Android Device Manager" doesn't let you unlock the phone.

Since my phone is not rooted and I don't have a custom recovery installed my main question is, any way that I can get access to the phone so that I can delete those .key files and unlock it?
I have tried ADB in Linux and Windows, and neither shows me any devices after I do "adb start-server" and "adb devices".

It feels like the only option is a wipeout, but I wanted to verify any possible way to get adb working or being able to install CWM/TWRP. I realize the verizon version of the Note 4 SM-N910V is fairly locked down, so with an already pin-locked phone, things don't seem too bright.

Any suggestions?



Sunday, 31 July 2016

[TWRP] Restore original backup not working

Hi guys, i have a problem..

I backup my original ROM with twrp and after I installed the cm13..

I backup the cm13 and wanted to restore the original ROM but is not starting up..
It stay fix on the initial Oneplus logo..

Any advice?

Thank you,

Simone

Backup Questions



I have a new phone, Samsung Galaxy J7, with Android 6.01, NOT rooted.I have read a lot of threads about backup, but none that really answer my questions.

Here are some things that I DON"T need backed up--contacts, calendar, e-mail messages, etc. Because I have an Exchange account (also Gmail Imap account), and those items will sync from there. I also would not need a backup app for photos, music, etc. Photos are files on my SD card that I can easily copy to the computer. Music files are first on my computer, that I transfer to the SD card. No need for a backup app for that. Apps themselves need no backup, as they can always get re-downloaded from the app store, and frequently update anyhow.

What I need backup for, is what will not sync from Exchange nor Imap, nor files that can be copied from and to the computer. Mostly settings--the general phone and Android settings, home screens, accounts, etc. (So that if something goes wrong with the phone and all that is lost, I would not have to spend hours setting it all up from scratch, entering account info again, etc. Also helpful-settings for apps.

I installed the Helium app, that reviews say is a good backup app (free version). I do not find it very useful. I have no idea why it makes you connect to the computer, then initiate its desktop app, just to verify the app somehow? But then, it will not backup to the computer! Nor even to the SD card. It does have an option to backup to the cloud with the pro version, but I would rather backup locally. It only backs up to internal phone memory. What use is that if the phone gets messed up and that backup is no longer in internal memory?

Furthermore, I see in Helium no way to backup phone settings, account into, etc. It can backup apps, or only app data. So I backed up the app data, went to a folder in internal memory called Carbon, and I copied that folder to the SD card and external HDD. Yet I do not find that very helpful.

I see that in the OS Settings that Google automatically backs up settings, etc., to one's Google Cloud account. OK. That's good. But I see no way to restore. Only that when one reinstalls an app, it will automatically reinsall the settings for that app. That's good. Perhaps no use for the app settings backup from Helium then. But what if something goes wrong on the phone and my homescreens get messed up? How would automatic restore help that? It is good if Google is automatically saving all my phone settings to the cloud. But if I have no way to manually restore them, what use is that? (Perhaps would work for app settings, as described, but not for phone and OS settings, accounts, etc.)

Could anyone tell me, is there a way to backup the info as I dscribed above, either through an internal feature, or with an external app (that does not requrie root), so that if the phone gets messed up somehow i can quickly and easily restore it to how it was?

(Surprised that Android does not have a feature like System restore in Windows.)

Thank you in advance for any suggestions.



Galaxy S6 - NO NETWORK, No IMEI no baseband NO EFS Backup



On my Samsung Galaxy S6 which was Vodafone before, on 6.0.1 I flashed twrp everything was working perfect fine apart from this time I forgot to backup my efs so now i have an unknown baseband and also an unknown IMEI, on the notification bar there is a prohibited symbol, like a constant silent mode, I was wondering is there any way either somebody can send me there backup, or any way I can get my phone back in to working order?



backup custom roms

how to take backup of custom cm12.1 based rom for galaxy grand 2 . I want to install new ROM on my mobile so I HV done a backup of my old cm 12.1 ROM .now when I restore my backup, it says application error sometimes Google play service not responding

Lenovo Yoga Tab 3 Pro X90 - TWRP Backup - ?

Hallo,
ich habe vergessen vor dem Root ein Backup von meinem X90 mit TWRP zu machen (Recovery, Bootloader).
Kann mir jemand dieses Backup schicken?
Danke im voraus

I forgot to make a backup with twrp from my Yoga 3 X90(recovery, bootloader).
Can anyone send me this files,
Thx

Saturday, 30 July 2016

**backup ta - restore not working on windows 10 {solved}

UNFORTUNATELY I unlocked my z3's bootloader on windows 10, (as I have only this pc available), till I took a backup my TA partition, all the things were going well.. it took the backup as it usually does.
after that when I tried to restore my backup of TA partition, the BackupTA ended on an error.. :confused:
I tried many things but nothing worked.. the only way remained to change my whole OS from windows 10 to windows 7. (as i finally concluded that BackupTA is no more fully compatible with windows 10).
I tried some tricks and finally did it with some googling.

steps i took:
1. installed VM Box
2. Installed VM box extention pack (needed to connect usb 2.0 devices, i.e my z3 to that virtual machine)
3. Installed whole windows 7 using a dvd to that virtual machine. ( youtube it.. it is easy )
4. Copied the BackupTA whole folder (including backups) and Flashtool drivers to a pen drive.
5. Connect the pen drive to my pc and then connect it with virtual machine ( you have to select within virtual machine- devices>usb>*pen drive name* )

6. Installed flashtool drivers. (selected fastboot, flashmode & xperia z3 drivers only)
7. Connected my z3 to virtual machine. ( you have to select within virtual machine- devices>usb>xperia z3 or d6653 )
8. Run BackupTA.bat and followed the instructions to restore backup.
10. :highfive: And restore was complete.

hope will be helpful for all windows 10 users.. who do want to restore their TA backup at 4.00 AM :silly::cool:

links
[/SIZE]

Thursday, 28 July 2016

Pandora Backup apk



Does Anyone have Pandora 7.0 or 7.1 Apks backed up from the amazon app store?



Wednesday, 27 July 2016

Can I make flashable img file for (android tool) from cwm Backup



Hi,
I'm having big problem by low level format of my tablet RK3188(chip) have no idea of model is 10' one.
I'm looking to make a flashable img files from my backup CWM recovery to use with Android tool since my tablet is unknown
china with RK3188 chip.
Since the :recovery, system, boot, kernel are large files in cwm I need to make them smaller (proper size) to use with Android tool. Please correct me if I'm wrong and tell me if its possible or any other way to get to my CWM .I just need to get to recovery. Please help.



TWRP Backup on external SD card not working on Marshmallow



Hi folks,

I recently upgraded my rooted Galaxy S4 (I9505) from CM12.1 to CM13, so I now have Marshmallow installed. Before the upgrade I made a backup on my external sd card with TWRP 3.0.2. Upgrading to Marshmallow went smooth and so I made another backup after installing CM13.
Yesterday I tried to make a backup but the backup on the external sd card failed. I tried it at least ten times. Most of the time I had some errors but sometimes there was no error shown in the log but the backup files were not saved on the external sd card. I've attached the complete recovery.log, here is an excerpt from the log:

Code:


* MD5 erstellt.
Durchschnittliche Sicherungsgeschwindigkeit für Dateisysteme: 13 MB/sek
Durchschnittliche Sicherungsgeschwindigkeit für abgebildete Laufwerke: 10 MB/sek
Fehler beim Öffnen: '/external_sd/TWRP/BACKUPS/a19a120c/2016-07-27--20-28-45_cm_jfltexx-userdebug_6.0.1_MOB30R_251a6113e//�?�Q?^??.?E�' (
I:Real error: Unable to stat '/external_sd/TWRP/BACKUPS/a19a120c/2016-07-27--20-28-45_cm_jfltexx-userdebug_6.0.1_MOB30R_251a6113e//�?�Q?^?
Fehler beim Öffnen: '/external_sd/TWRP/BACKUPS/a19a120c/2016-07-27--20-28-45_cm_jfltexx-userdebug_6.0.1_MOB30R_251a6113e//"�F?�&EQ.|??' (
I:Real error: Unable to stat '/external_sd/TWRP/BACKUPS/a19a120c/2016-07-27--20-28-45_cm_jfltexx-userdebug_6.0.1_MOB30R_251a6113e//"�F?�&E
Fehler beim Öffnen: '/external_sd/TWRP/BACKUPS/a19a120c/2016-07-27--20-28-45_cm_jfltexx-userdebug_6.0.1_MOB30R_251a6113e//����w?@P.?E)
I:Real error: Unable to stat '/external_sd/TWRP/BACKUPS/a19a120c/2016-07-27--20-28-45_cm_jfltexx-userdebug_6.0.1_MOB30R_251a6113e//����w?@
Fehler beim Öffnen: '/external_sd/TWRP/BACKUPS/a19a120c/2016-07-27--20-28-45_cm_jfltexx-userdebug_6.0.1_MOB30R_251a6113e//?rG?????.\N�' (
I:Real error: Unable to stat '/external_sd/TWRP/BACKUPS/a19a120c/2016-07-27--20-28-45_cm_jfltexx-userdebug_6.0.1_MOB30R_251a6113e//?rG????
Fehler beim Öffnen: '/external_sd/TWRP/BACKUPS/a19a120c/2016-07-27--20-28-45_cm_jfltexx-userdebug_6.0.1_MOB30R_251a6113e//k�?�p?�!.?e<' (
I:Real error: Unable to stat '/external_sd/TWRP/BACKUPS/a19a120c/2016-07-27--20-28-45_cm_jfltexx-userdebug_6.0.1_MOB30R_251a6113e//k�?�p?�
Fehler beim Öffnen: '/external_sd/TWRP/BACKUPS/a19a120c/2016-07-27--20-28-45_cm_jfltexx-userdebug_6.0.1_MOB30R_251a6113e//-)


"Fehler beim Öffnen" is German for I guess "Error while opening…"

The sd card works in the way that I can put photos and music on it. It is mounted as follows:

Code:


root@jfltexx:/mnt/sdcard # mount  | grep 2015-1707                                                                                     
/dev/block/vold/public:179_33 on /mnt/media_rw/2015-1707 type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/fuse on /mnt/runtime/default/2015-1707 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/2015-1707 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/2015-1707 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/2015-1707 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other


Yesterday I tried to change permissions on the sd card by setting write permissions like this:

Code:


root@jfltexx:/mnt # chmod g +w media_rw/

Nothing changed.

Furthermore I tried the app "SDFix: KitKat Writable MicroSD" to fix the permission problem. If I had read the description more carefully I would have saved some time. The app had no effect and said that it couldn't fix the permission problem so I uninstalled it immediately. Today I tried the Xposed module "Marshmallow SD fix" and gave permission for Nandroid Manager but that didn't help either. But that was what I expected because I think (!) that this has nothing to do with TWRP.

So my question is: What do I have to do to make TWRP backup my data on the external sc card?

Your help is very much appreciated. If you need further information just let me know.

Greeting, Jens














Attached Files






File Type: 7z recovery.7z -
[Click for QR Code]
(330.7 KB)







Please upload if you have a TWRP backup for B560 European for TL-10 EUROPE DUALSIM



Hi All,

I need TWRP full backup for B560 European for TL-10 if you are having upload on mega ?



Monday, 25 July 2016

[Guide] Backup ,restore imei and fix invalid imei number



Requirements :
Imei number
Mobile unkle tools
Es file explorer

Fixing invalid imei
This method dosent require root

Install and open mobile unkle tools
Go to engeeniring mode (MTK)
Under connectivity open cds information
Click radio indormation

Open phone 1
Type in the box
AT+ EGMR=1,7,"Enter your imei number here"
Press sent command
Reboot

In phone 2
Type
AT+ EGMR=1,10,"Enter your imei number here"
Reboot

Do not forget to add space between AT+and EGMR

And your imei has been added

Backing up imei
Requires root
Open es file manager grant root permissions
Go to /data/nvram/md/nvram/
Copy the whole nvd_imei Filder to your sdcard

And this filder is your imei backup

Another way of backing up imei
Use mobile unkle tools and click in backup imei to sdcard
This creates a imei backup in another format but restoring imei is not allways sucess full using this method


Restoring imei
Requires root

just paste the nvd imei folder in
/data/nvram/md/nvram/

And reboot
Imei restored

Using mobile unkle tools
Click restore imei from sdcard
And then reboot
This method not restore imei allways in higher androod versions like marshmallow


Thanks
Hope you like this guide:good::laugh:



[ROOT] Partitions backup & other partition info :



Before rooting, do backup your /boot and /system partitions via SPFT, as described here (whenever the post is filled in properly :D ) :
http://forum.xda-developers.com/r1-h...oting-t3426041
Since it's pretty tedious to run that for each and every partition, I propose to backup other ones after you get root. But note that copying the partitions back to the device is a lot quicker since all the necessary info can be preset in a scatter file !

I recommend that you follow other threads to get root, such as, for example, here :
http://forum.xda-developers.com/r1-h...-root-t3425677

Some partitions will still be mounted, but I don't think it matters that much. Anyway, here is a list of what is usually mounted :

Code:


Filesystem              Size    Used    Free  Blksize
/dev                  970.2M    84.0K  970.1M  4096
/sys/fs/cgroup        970.2M    12.0K  970.2M  4096
/mnt                  970.2M    0.0K  970.2M  4096
/mnt/runtime/default/emulated    11.2G  522.4M    10.7G  4096
/mnt/runtime/read/emulated    11.2G  522.4M    10.7G  4096
/mnt/runtime/write/emulated    11.2G  522.4M    10.7G  4096
/system                  2.5G    2.0G  516.5M  4096
/data                  11.2G  522.4M    10.7G  4096
/cache                387.4M  988.0K  386.5M  4096
/protect_f              5.8M    60.0K    5.8M  4096
/protect_s              5.8M    56.0K    5.8M  4096
/nvdata                27.5M    2.2M    25.3M  4096
/storage              970.2M    0.0K  970.2M  4096
/storage/emulated      11.2G  522.4M    10.7G  4096
/su                    90.5M  676.0K    89.8M  4096


To backup whatever partitions are out there, run these commands :

Code:


adb shell
su
mkdir /sdcard/images/
cd /sdcard/images
dd if=/dev/block/mmcblk0boot0 of=00_boot0.img
dd if=/dev/block/mmcblk0boot1 of=01_boot1.img
dd if=/dev/block/mmcblk0rpmb of=02_rpmb.img
dd if=/dev/block/mmcblk0p1 of=p1_proinfo.img
dd if=/dev/block/mmcblk0p2 of=p2_nvram.img
dd if=/dev/block/mmcblk0p3 of=p3_protect1.img
dd if=/dev/block/mmcblk0p4 of=p4_protect2.img
dd if=/dev/block/mmcblk0p5 of=p5_lk.img
dd if=/dev/block/mmcblk0p6 of=p6_para.img
dd if=/dev/block/mmcblk0p7 of=p7_boot.img
dd if=/dev/block/mmcblk0p8 of=p8_recovery.img
dd if=/dev/block/mmcblk0p9 of=p9_logo.img
dd if=/dev/block/mmcblk0p10 of=p10_expdb.img
dd if=/dev/block/mmcblk0p11 of=p11_seccfg.img
dd if=/dev/block/mmcblk0p12 of=p12_oemkeystore.img
dd if=/dev/block/mmcblk0p13 of=p13_secro.img
dd if=/dev/block/mmcblk0p14 of=p14_keystore.img
dd if=/dev/block/mmcblk0p15 of=p15_tee1.img
dd if=/dev/block/mmcblk0p16 of=p16_tee2.img
dd if=/dev/block/mmcblk0p17 of=p17_frp.img
dd if=/dev/block/mmcblk0p18 of=p18_nvdata.img
dd if=/dev/block/mmcblk0p19 of=p19_metadata.img
#dd if=/dev/block/mmcblk0p20 of=p20_system.img
#dd if=/dev/block/mmcblk0p21 of=p21_cache.img
#dd if=/dev/block/mmcblk0p22 of=p22_userdata.img
dd if=/dev/block/mmcblk0p23 of=p23_flashinfo.img
md5sum *.img
exit
exit
adb pull /sdcard/images


These are the files that you'll get

Code:


-rw-rw---- root    sdcard_rw  4194304 2016-01-01 18:31 00_boot0.img
-rw-rw---- root    sdcard_rw  4194304 2016-01-01 18:31 01_boot1.img
-rw-rw---- root    sdcard_rw        0 2016-01-01 18:47 02_rpmb.img
-rw-rw---- root    sdcard_rw  3145728 2016-01-01 18:31 p1_proinfo.img
-rw-rw---- root    sdcard_rw  5242880 2016-01-01 18:31 p2_nvram.img
-rw-rw---- root    sdcard_rw 10485760 2016-01-01 18:31 p3_protect1.img
-rw-rw---- root    sdcard_rw 10485760 2016-01-01 18:31 p4_protect2.img
-rw-rw---- root    sdcard_rw  524288 2016-01-01 18:31 p5_lk.img
-rw-rw---- root    sdcard_rw  524288 2016-01-01 18:31 p6_para.img
-rw-rw---- root    sdcard_rw 16777216 2016-01-01 18:31 p7_boot.img
-rw-rw---- root    sdcard_rw 16777216 2016-01-01 18:31 p8_recovery.img
-rw-rw---- root    sdcard_rw  8388608 2016-01-01 18:31 p9_logo.img
-rw-rw---- root    sdcard_rw 10485760 2016-01-01 18:31 p10_expdb.img
-rw-rw---- root    sdcard_rw  524288 2016-01-01 18:31 p11_seccfg.img
-rw-rw---- root    sdcard_rw  2097152 2016-01-01 18:31 p12_oemkeystore.img
-rw-rw---- root    sdcard_rw  6291456 2016-01-01 18:31 p13_secro.img
-rw-rw---- root    sdcard_rw  8388608 2016-01-01 18:31 p14_keystore.img
-rw-rw---- root    sdcard_rw  5242880 2016-01-01 18:31 p15_tee1.img
-rw-rw---- root    sdcard_rw  5242880 2016-01-01 18:31 p16_tee2.img
-rw-rw---- root    sdcard_rw  1048576 2016-01-01 18:31 p17_frp.img
-rw-rw---- root    sdcard_rw 33554432 2016-01-01 18:31 p18_nvdata.img
-rw-rw---- root    sdcard_rw 38797312 2016-01-01 18:32 p19_metadata.img
-rw-rw---- root    sdcard_rw 16777216 2016-01-01 18:32 p23_flashinfo.img


And this is another map of partitions to names :

Code:


lrwxrwxrwx root    root              2016-01-01 17:30 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root    root              2016-01-01 17:30 cache -> /dev/block/mmcblk0p21
lrwxrwxrwx root    root              2016-01-01 17:30 expdb -> /dev/block/mmcblk0p10
lrwxrwxrwx root    root              2016-01-01 17:30 flashinfo -> /dev/block/mmcblk0p23
lrwxrwxrwx root    root              2016-01-01 17:30 frp -> /dev/block/mmcblk0p17
lrwxrwxrwx root    root              2016-01-01 17:30 keystore -> /dev/block/mmcblk0p14
lrwxrwxrwx root    root              2016-01-01 17:30 lk -> /dev/block/mmcblk0p5
lrwxrwxrwx root    root              2016-01-01 17:30 logo -> /dev/block/mmcblk0p9
lrwxrwxrwx root    root              2016-01-01 17:30 metadata -> /dev/block/mmcblk0p19
lrwxrwxrwx root    root              2016-01-01 17:30 nvdata -> /dev/block/mmcblk0p18
lrwxrwxrwx root    root              2016-01-01 17:30 nvram -> /dev/block/mmcblk0p2
lrwxrwxrwx root    root              2016-01-01 17:30 oemkeystore -> /dev/block/mmcblk0p12
lrwxrwxrwx root    root              2016-01-01 17:30 para -> /dev/block/mmcblk0p6
lrwxrwxrwx root    root              2016-01-01 17:30 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root    root              2016-01-01 17:30 protect1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root    root              2016-01-01 17:30 protect2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root    root              2016-01-01 17:30 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx root    root              2016-01-01 17:30 seccfg -> /dev/block/mmcblk0p11
lrwxrwxrwx root    root              2016-01-01 17:30 secro -> /dev/block/mmcblk0p13
lrwxrwxrwx root    root              2016-01-01 17:30 system -> /dev/block/mmcblk0p20
lrwxrwxrwx root    root              2016-01-01 17:30 tee1 -> /dev/block/mmcblk0p15
lrwxrwxrwx root    root              2016-01-01 17:30 tee2 -> /dev/block/mmcblk0p16
lrwxrwxrwx root    root              2016-01-01 17:30 userdata -> /dev/block/mmcblk0p22


And mount output :

Code:


rootfs / rootfs ro,seclabel 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 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,seclabel,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/fuse /mnt/runtime/default/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/read/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/write/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,resuid=10010,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/protect1 /protect_f ext4 rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/protect2 /protect_s ext4 rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/nvdata /nvdata ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/fuse /storage/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/loop1 /su ext4 rw,seclabel,noatime,data=ordered 0 0


And partition sizes in blocks:

Code:


major minor  #blocks  name

  7        0      1254 loop0
  7        1      98304 loop1
 179        0  15392768 mmcblk0
 179        1      3072 mmcblk0p1
 179        2      5120 mmcblk0p2
 179        3      10240 mmcblk0p3
 179        4      10240 mmcblk0p4
 179        5        512 mmcblk0p5
 179        6        512 mmcblk0p6
 179        7      16384 mmcblk0p7
 179        8      16384 mmcblk0p8
 179        9      8192 mmcblk0p9
 179      10      10240 mmcblk0p10
 179      11        512 mmcblk0p11
 179      12      2048 mmcblk0p12
 179      13      6144 mmcblk0p13
 179      14      8192 mmcblk0p14
 179      15      5120 mmcblk0p15
 179      16      5120 mmcblk0p16
 179      17      1024 mmcblk0p17
 179      18      32768 mmcblk0p18
 179      19      37888 mmcblk0p19
 179      20    2736128 mmcblk0p20
 179      21    409600 mmcblk0p21
 179      22  12049920 mmcblk0p22
 179      23      16384 mmcblk0p23
 179      96      4096 mmcblk0rpmb
 179      64      4096 mmcblk0boot1
 179      32      4096 mmcblk0boot0