Hey guys, so recently I've been trying to extract the stock Android 7.1.1 firmware from my AT&T Tab E so that I can package it into a flashable .tar.md5 file for Odin.
So far this is what I have:
First I typed this into the Terminal Emulator app on the tablet:
Code:
ls -al /dev/block/platform/13540000.dwmmc0/by-name
And it spit this out:
Code:
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 BOOT -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 2018-06-02 00:30 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2018-06-02 00:30 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 CACHE -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 2018-06-02 00:30 CARRIER -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 CDMA-RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 2018-06-02 00:30 CPEFS -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2018-06-02 00:30 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 OTA -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 2018-06-02 00:30 PARAM -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 PERSDATA -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 PERSISTENT -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 RADIO -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 RECOVERY -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 RESERVED2 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 SYSTEM -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 TDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 TOMBSTONES -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 USERDATA -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 20 2018-06-02 00:30 m9kefs1 -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2018-06-02 00:30 m9kefs2 -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2018-06-02 00:30 m9kefs3 -> /dev/block/mmcblk0p7
This information lets us know which partition file in /dev/block is for the boot, system, recovery etc.
But when I try using this command to dump any of the files into my internal SD card:
Code:
dd if=/dev/block/mmcblk0pXX of=/sdcard/XXXXXXXX.img bs=4096
or external SD card:
Code:
dd if=/dev/block/mmcblk0pXX of=/storage/C35A-1CE6/XXXXXXXX.img bs=4096
It keeps on spitting out "Permission denied" and it doesn't do anything.
Correct me if I'm wrong, but I think it has something to do with me not having root access on my Tab E :/
Anyways, if somebody can help me with this it would be awesome!
Related
Hi,
i extracted the partition names for you and made a parition dump after unlocking and rooting.
I hope you find this helpful.
I skipped partition 28 since that is userdata.
Where should I host the dumped files?
Code:
/dev/block/platform/msm_sdcc.1/by-name # ls -al
ls -al
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 620 Jan 22 00:29 .
drwxr-xr-x 4 root root 700 Jan 22 00:29 ..
lrwxrwxrwx 1 root root 20 Jan 22 00:29 DDR -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 Jan 22 00:29 DRIVER -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 Jan 22 00:29 LOGO -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 20 Jan 22 00:29 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 22 00:29 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Jan 22 00:29 cache -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 20 Jan 22 00:29 dbi -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Jan 22 00:29 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Jan 22 00:29 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Jan 22 00:29 grow -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 Jan 22 00:29 misc -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 Jan 22 00:29 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Jan 22 00:29 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 22 00:29 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Jan 22 00:29 oppodycnvbk -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Jan 22 00:29 oppostanvbk -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 Jan 22 00:29 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Jan 22 00:29 persist -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Jan 22 00:29 recovery -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Jan 22 00:29 reserve1 -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 Jan 22 00:29 reserve2 -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Jan 22 00:29 reserve3 -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Jan 22 00:29 reserve4 -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 20 Jan 22 00:29 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Jan 22 00:29 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 Jan 22 00:29 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Jan 22 00:29 system -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 20 Jan 22 00:29 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Jan 22 00:29 userdata -> /dev/block/mmcblk0p28
/dev/block/platform/msm_sdcc.1/by-name #
Polarfuchs said:
Hi,
i extracted the partition names for you and made a parition dump after unlocking and rooting.
I hope you find this helpful.
I skipped partition 28 since that is userdata.
Where should I host the dumped files?
Code:
/dev/block/platform/msm_sdcc.1/by-name # ls -al
ls -al
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 620 Jan 22 00:29 .
drwxr-xr-x 4 root root 700 Jan 22 00:29 ..
lrwxrwxrwx 1 root root 20 Jan 22 00:29 DDR -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 Jan 22 00:29 DRIVER -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 Jan 22 00:29 LOGO -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 20 Jan 22 00:29 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 22 00:29 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Jan 22 00:29 cache -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 20 Jan 22 00:29 dbi -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Jan 22 00:29 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Jan 22 00:29 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Jan 22 00:29 grow -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 Jan 22 00:29 misc -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 Jan 22 00:29 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Jan 22 00:29 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 22 00:29 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Jan 22 00:29 oppodycnvbk -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Jan 22 00:29 oppostanvbk -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 Jan 22 00:29 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Jan 22 00:29 persist -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Jan 22 00:29 recovery -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Jan 22 00:29 reserve1 -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 Jan 22 00:29 reserve2 -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Jan 22 00:29 reserve3 -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Jan 22 00:29 reserve4 -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 20 Jan 22 00:29 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Jan 22 00:29 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 Jan 22 00:29 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Jan 22 00:29 system -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 20 Jan 22 00:29 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Jan 22 00:29 userdata -> /dev/block/mmcblk0p28
/dev/block/platform/msm_sdcc.1/by-name #
Click to expand...
Click to collapse
Duplicate post...
See....
http://forum.xda-developers.com/showthread.php?t=2751530
adb shell ls -la /dev/block/platform/f9824900.sdhci/by-name
lrwxrwxrwx root root 2015-01-02 19:51 DDR -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2015-01-02 19:51 aboot -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-01-02 19:51 abootbak -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-01-02 19:51 apdp -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-01-02 19:51 boot -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 2015-01-02 19:51 cache -> /dev/block/mmcblk0p54
lrwxrwxrwx root root 2015-01-02 19:51 carrier -> /dev/block/mmcblk0p47
lrwxrwxrwx root root 2015-01-02 19:51 devinfo -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-01-02 19:51 dpo -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-01-02 19:51 drm -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 2015-01-02 19:51 eksst -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2015-01-02 19:51 encrypt -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2015-01-02 19:51 eri -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 2015-01-02 19:51 factory -> /dev/block/mmcblk0p49
lrwxrwxrwx root root 2015-01-02 19:51 felica -> /dev/block/mmcblk0p48
lrwxrwxrwx root root 2015-01-02 19:51 fota -> /dev/block/mmcblk0p51
lrwxrwxrwx root root 2015-01-02 19:51 fsc -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2015-01-02 19:51 fsg -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2015-01-02 19:51 grow -> /dev/block/mmcblk0p56
lrwxrwxrwx root root 2015-01-02 19:51 hyp -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-01-02 19:51 hypbak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-01-02 19:51 keystore -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2015-01-02 19:51 laf -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 2015-01-02 19:51 limits -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-01-02 19:51 misc -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-01-02 19:51 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-01-02 19:51 modemst1 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2015-01-02 19:51 modemst2 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2015-01-02 19:51 mpt -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 2015-01-02 19:51 msadp -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-01-02 19:51 operatorlogging -> /dev/block/mmcblk0p46
lrwxrwxrwx root root 2015-01-02 19:51 persist -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-01-02 19:51 persistent -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2015-01-02 19:51 pmic -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-01-02 19:51 pmicbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-01-02 19:51 raw_resources -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 2015-01-02 19:51 raw_resourcesbak -> /dev/block/mmcblk0p45
lrwxrwxrwx root root 2015-01-02 19:51 rct -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2015-01-02 19:51 recovery -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 2015-01-02 19:51 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-01-02 19:51 rpmbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-01-02 19:51 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-01-02 19:51 sbl1bak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-01-02 19:51 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-01-02 19:51 sdibak -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-01-02 19:51 sec -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2015-01-02 19:51 sns -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 2015-01-02 19:51 spare1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-01-02 19:51 spare2 -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 2015-01-02 19:51 spare3 -> /dev/block/mmcblk0p50
lrwxrwxrwx root root 2015-01-02 19:51 spare4 -> /dev/block/mmcblk0p52
lrwxrwxrwx root root 2015-01-02 19:51 ssd -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2015-01-02 19:51 system -> /dev/block/mmcblk0p53
lrwxrwxrwx root root 2015-01-02 19:51 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-01-02 19:51 tzbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-01-02 19:51 userdata -> /dev/block/mmcblk0p55
Thx. System dump possible?
Please, adb pull /system.
What are the partitions spare1-4 used for? I've pulled mine using dd, but they appear to be completely empty.
can fix boot loop?
How can i use this to fix my boot loop g4?
please help me run this emmc dumper batch file on your ZE 550KL (it requires adb access on your phone)
and help backup and share your gpt.bin file with me.
The program is here. https://drive.google.com/open?id=0B39xYnt0Q7O0cWQwVlRXVFNIWHM
Thank you.
please can anyone try this application Partitions Backup https://youtu.be/sikZ3IBAdew on their phone to backup all the hidden system partitions like sbl1, tz. etc. and post a screenshot of the partitions that are available for backup?
i'm hoping there's a chance the msimage.mbn and MPRG.mbn may be listed for backup. in which case you would be saving a life.
No one really should upload you full dump of their mmcblk0. It contains very sensitive informations like IMEI, whole /data and more...
BTW there are no msimage and MPRG partitions.
[email protected]:/ # ls -la /dev/block/bootdevice/by-name/
total 0
drwxr-xr-x 2 root root 960 1970-06-23 16:04 .
drwxr-xr-x 4 root root 1040 1970-06-23 16:04 ..
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 ADF -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 APD -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 20 1970-06-23 16:04 DDR -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 aboot -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 abootbak -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 abootdebug -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 asdf -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 asusfw -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 asusgpt -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 asusgpt1 -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 asusgpt2 -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 asuskey -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 asuskey2 -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 asuskey3 -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 asuskey4 -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 asuskey5 -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 boot -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 cache -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 config -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 devinfo -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 factory -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 factorybak -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 fsc -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 fsg -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 20 1970-06-23 16:04 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 1970-06-23 16:04 hypbak -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 keystore -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 misc -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 modem -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 modemst1 -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 modemst2 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 oem -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 persist -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 persistent -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 recovery -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 20 1970-06-23 16:04 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 1970-06-23 16:04 rpmbak -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 1970-06-23 16:04 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 1970-06-23 16:04 sbl1bak -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 sec -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 splash -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 ssd -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 system -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 20 1970-06-23 16:04 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 1970-06-23 16:04 tzbak -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 1970-06-23 16:04 userdata -> /dev/block/mmcblk0p46
Click to expand...
Click to collapse
LuK1337 said:
No one really should upload you full dump of their mmcblk0. It contains very sensitive informations like IMEI, whole /data and more...
BTW there are no msimage and MPRG partitions.
Click to expand...
Click to collapse
I don't want the whole thing. It will be too large anyway. I have the stock rom.
I need the files i already outlined.
BTW i read somewhere that the gpt.bin can be renamed to the msimage as they both contain the same thing i.e. the partition table
Needless to say, what exactly is wrong with my trying to revive my device? i bought this device with my hard earned money just 3 months ago.
if i ask for help and nobody answers, so be it. its my prerogative to ask.
Could have sworn this is XDA and i'm allowed to hack my own device if possible..
It is not your "prerogative" to ask. Where in XDA's terms and services did you get that from? Continuously spamming threads won't suddenly compel someone to do the things you ask.
andrehsu said:
It is not your "prerogative" to ask. Where in XDA's terms and services did you get that from? Continuously spamming threads won't suddenly compel someone to do the things you ask.
Click to expand...
Click to collapse
ok. Noted.
@MikeChannon please close this thread. its served its / its useless
Hello, I was trying to dump my MCU partition into img file. That way I could try to reflash it back within the update mcu settings on device. My goal was to flash it with the dmcu.ext file that controls the resolution. I read I am supposed to flash MCU with text file dmcu.ext "screen:1" in the root of where the mcu image is. When I flash the entire image it does not seem to work, thought it could be because firmware is in one large bin file that contains all of the images like system and boot. I dumped the tee1 and tee2 to image file, would that be mcu? My resolution is showing 1024x600, instead of 800x480.
no matter what mcu img I attempt to update, MCU update says failed to update file. I was reading about mismatch, but don't see that error.
If I am not on the right track here, please correct me.
FF-5000:/ # ls -al /dev/block/platform/soc/11230000.mmc/by-name
total 0
drwxr-xr-x 2 root root 560 2010-01-01 00:01 .
drwxr-xr-x 4 root root 680 2010-01-01 00:01 ..
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 ANDROID -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 ARM2 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 BOOTIMG -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 CACHE -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 DKB -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 EXPDB -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 FRP -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 KB -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 LK -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 LOGO -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 METAZONE -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 MISC -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 NVRAM -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 ODMDTBO -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 PROTECT_F -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 PROTECT_S -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 PRO_INFO -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 RECOVERY -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 SECCFG -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 SEC_RO -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 TEE1 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 TEE2 -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 VENDOR -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 forfanzone -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 tszone -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 userdata -> /dev/block/mmcblk0p26
How to Get a copy of boot.img Lenovo Tab 8
step 1: Download mtk-easy-su From the link Below
step 2: install mtk-easy-su.apk
step 3: open the mtk-easy-su
step 4: press the yellow circle # button
Note: wait for it to say given super user permissions to magisk manager
step 5: go to settings/About Tablet/
step 6: tap build number until it says "Your Now a Developer!" at the bottom of the screen
step 7: go to settings/Developer Options
step 8: enable Usb Debugging
step 9: plug your tablet into your computer
step 10: go to install adb from Here on your computer
step 11: type ls -la /dev/block/platform/soc/11230000.mmc/by-name
Note: It will display something like this:
lrwxrwxrwx 1 root root 20 2021-06-14 15:52 boot -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2021-06-14 15:52 cache -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2021-06-14 15:52 dkb -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2021-06-14 15:52 expdb -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2021-06-14 15:52 flashinfo -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2021-06-14 15:52 frp -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2021-06-14 15:52 kb -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 20 2021-06-14 15:52 lk -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2021-06-14 15:52 logo -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2021-06-14 15:52 metadata -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 20 2021-06-14 15:52 nvram -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2021-06-14 15:52 para -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 2021-06-14 15:52 persist -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2021-06-14 15:52 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2021-06-14 15:52 protect1 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 2021-06-14 15:52 protect2 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2021-06-14 15:52 recovery -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 20 2021-06-14 15:52 seccfg -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 2021-06-14 15:52 secro -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2021-06-14 15:52 system -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2021-06-14 15:52 tee1 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2021-06-14 15:52 tee2 -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2021-06-14 15:52 userdata -> /dev/block/mmcblk0p22
Note : You are looking for boot:
lrwxrwxrwx 1 root root 20 2021-06-14 15:52 boot -> /dev/block/mmcblk0p8
Step 12: Then type dd if=/dev/block/mmcblk0p8 of=/sdcard/Download/boot.img
Note: the if=/dev/block/mmcblk0p8 is what we found in the list of partitions
Step 13: Wait until the copy finishes
If you would like to root follow this guide Posted Here
NOTE: You must use the filename you have from this Guide instead of the MagisBoot.img used in the other guide
I use the wrong filename. And when I reboot the device in the final step in the other guide, it just can't boot any more. The computer can't identify it through the USB. And it can't get into the fastboot mode and recovery mode. What should I do?
lester111 said:
I use the wrong filename. And when I reboot the device in the final step in the other guide, it just can't boot any more. The computer can't identify it through the USB. And it can't get into the fastboot mode and recovery mode. What should I do?
Click to expand...
Click to collapse
You can try to use a tool called flash tool with a scatter plot file which is a txt file and use the stock boot image to reflash the boot partition but idk where if at all you can get a scatter plot for this device however also it’s no guarantee the only success I know was to use the exact method in the guide because I haven’t had this issue I am not entirely sure what to do :/
https://drive.google.com/file/d/1lipGamEnpSJHdQy3f4BjsJGNwvmHvV7d/view
retry downloading that and unzip it and open the scatterplot file in so flash tool and follow this guide
link
you might luck out and unbrick it back to stock but to root will have to repeat the process of the rooting guide in going to suggest using the boot.I’m from the zip you download for so flash tool to create your magical image if you decide to root again if the device is recovered
Thank you , I will give it a try.