If you wanna know the partition mount points, I think I found them.
Code:
[email protected]:/ $ ls -al /dev/block/platform/msm_sdcc.1/by-name
ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 2013-06-28 18:24 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-06-28 18:24 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-06-28 18:24 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2013-06-28 18:24 boot -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2013-06-28 18:24 cache -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2013-06-28 18:24 carrier -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2013-06-28 18:24 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-06-28 18:24 fota -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2013-06-28 18:24 fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2013-06-28 18:24 hidden -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2013-06-28 18:24 m9kefs1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2013-06-28 18:24 m9kefs2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2013-06-28 18:24 m9kefs3 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2013-06-28 18:24 mdm -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-06-28 18:24 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-06-28 18:24 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-06-28 18:24 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-06-28 18:24 param -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2013-06-28 18:24 persdata -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2013-06-28 18:24 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2013-06-28 18:24 recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2013-06-28 18:24 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-06-28 18:24 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-06-28 18:24 sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-06-28 18:24 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-06-28 18:24 ssd -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2013-06-28 18:24 system -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2013-06-28 18:24 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-06-28 18:24 userdata -> /dev/block/mmcblk0p29
Thanks to this thread in XDA-University: http://forum.xda-developers.com/showthread.php?t=2102283 (and post #4)
Cheers.
I had an idea to mount the hidden OTA partition and use it for Dalvik cache and/or folder mount data.
Any pointers I've done this sort of scripting before but forget the command syntax
Sent from my GT-I9505 using Tapatalk 2
rlorange said:
I had an idea to mount the hidden OTA partition and use it for Dalvik cache and/or folder mount data.
Any pointers I've done this sort of scripting before but forget the command syntax
Sent from my GT-I9505 using Tapatalk 2
Click to expand...
Click to collapse
I have absolutely no idea.
Pawitp is the i9000 CM maintainer dev. He changed the partition layout of that phone a few times by CWM. It seemed easy. Maybe he can help us out.
Sent from my GT-I9505 using Tapatalk 4 Beta
Thanks I'll dig up my old Siyahmods tasker backups... Should be able to free up some wasted space
Sent from my GT-I9505 using Tapatalk 2
---------- Post added at 09:31 PM ---------- Previous post was at 09:30 PM ----------
Probably stop short of repartitioning. Lol!
Sent from my GT-I9505 using Tapatalk 2
cwm includes parted, and if you enter the print command you get this:
Code:
Number Start End Size File system Name Flags
1 4194kB 17.3MB 13.1MB apnhlos
2 17.3MB 71.3MB 54.0MB mdm
3 71.3MB 71.4MB 131kB sbl1
4 71.4MB 71.7MB 262kB sbl2
5 71.7MB 72.2MB 524kB sbl3
6 72.2MB 74.3MB 2097kB aboot
7 74.3MB 74.8MB 524kB rpm
8 74.8MB 75.4MB 524kB tz
9 75.4MB 92.7MB 17.3MB pad
10 92.7MB 107MB 14.3MB ext4 efs
11 107MB 110MB 3146kB modemst1
12 110MB 113MB 3146kB modemst2
13 113MB 114MB 799kB m9kefs1
14 114MB 115MB 799kB m9kefs2
15 115MB 116MB 799kB m9kefs3
16 116MB 3010MB 2894MB ext4 system
17 3010MB 3018MB 8389kB persist
18 3018MB 5189MB 2171MB ext4 cache
19 5189MB 5195MB 6291kB param
20 5195MB 5205MB 10.5MB boot
21 5205MB 5216MB 10.5MB recovery
22 5216MB 5226MB 10.5MB fota
23 5226MB 5233MB 6291kB backup
24 5233MB 5236MB 3146kB fsg
25 5236MB 5236MB 8192B ssd
26 5236MB 5245MB 9437kB ext4 persdata
27 5245MB 5770MB 524MB ext4 hidden
28 5770MB 5791MB 21.0MB carrier
29 5791MB 15.8GB 9961MB ext4 userdata
This is from a 16Gb model, so the hardware mount points of the partitions are /dev/block/mmcblk0p[Number]
Could anyone here explain the use/function of each the partitions? system, data, cache, boot, recovery, modem, efs,... is all clear, but for what do I need m9kefs1-3, persist, param, fota, backup, fsg, ssd, perdata, hidden, carrier on cm10.1?
L
Does this phone use the unified emulated /storage/sdcard0 and /data partition?
Related
I'm trying to create a partition dump, specifically to have a backup of my efs partition. My first 6p had it's efs partition corrupted (while stock, unrooted, locked bl). I've got my new 6p in hand, bl unlocked, twrp installed, and chainfires systemless root up and running. I was trying to follow this guide:
http://forum.xda-developers.com/showthread.php?t=2450045
but i cannot access / using any file explorer. The SU prompt never appears. I tried running cat /proc/emmc, and that was a no go as well. I was able to get the partition list, but only in mmcblkxxxx format. I would like the names, so that i can properly organize the dump. If anybody could point me in the right direction, that'd be awesome! Thanks in advance.
Never mind, I've found it. For other's reference, the correct path is:
/dev/block/platform/soc.0/f9824900.sdhci/by-name.
Hope this helps someone in the future
beats4x said:
Never mind, I've found it. For other's reference, the correct path is:
/dev/block/platform/soc.0/f9824900.sdhci/by-name.
Hope this helps someone in the future
Click to expand...
Click to collapse
I don't have a 6p, but I've been looking for someone to post the list by-name. Would you mind sharing?
makers_mark said:
I don't have a 6p, but I've been looking for someone to post the list by-name. Would you mind sharing?
Click to expand...
Click to collapse
Will have to be when I get home from work, but yeah I definitely can
Sent from my Nexus 6P using Tapatalk
makers_mark said:
I don't have a 6p, but I've been looking for someone to post the list by-name. Would you mind sharing?
Click to expand...
Click to collapse
Here you go bro. Sprry for the delay. Been a crazy couple of days at work.
[email protected]:/ # ls -al /dev/block/platform/soc.0/f9824900.sdhci/by-name
lrwxrwxrwx root root 1970-01-26 16:23 DDR -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-26 16:23 aboot -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-26 16:23 abootbak -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-26 16:23 apdp -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-26 16:23 boot -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-26 16:23 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-26 16:23 cmnlib -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-26 16:23 cmnlibbak -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-26 16:23 devinfo -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-26 16:23 dpo -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-26 16:23 frp -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-26 16:23 fsc -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-26 16:23 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-26 16:23 hyp -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-26 16:23 hypbak -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-26 16:23 keymaster -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-26 16:23 keymasterbak -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-26 16:23 keystore -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-26 16:23 limits -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-26 16:23 metadata -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-26 16:23 misc -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-26 16:23 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-26 16:23 modemst1 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-26 16:23 modemst2 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-26 16:23 msadp -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-26 16:23 oem -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-26 16:23 oeminfo -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-26 16:23 persist -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-26 16:23 persistent -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-26 16:23 pmic -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-26 16:23 pmicbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-26 16:23 recovery -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-26 16:23 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-26 16:23 rpmbak -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-26 16:23 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-26 16:23 sbl1bak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-26 16:23 sdi -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-26 16:23 sec -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-26 16:23 ssd -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-26 16:23 system -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-01-26 16:23 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-26 16:23 tzbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-26 16:23 userdata -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-01-26 16:23 vendor -> /dev/block/mmcblk0p37
beats4x said:
...
Click to expand...
Click to collapse
I've been looking since they released the images, I think you may of been the first to post it anywhere that I have access to, thanks!!:good:
makers_mark said:
I've been looking since they released the images, I think you may of been the first to post it anywhere that I have access to, thanks!!:good:
Click to expand...
Click to collapse
No problem, glad I could assist!
Sent from my Nexus 6P using Tapatalk
Device- Xiaomi Redmi2 running CM 12.1
Here's the partition info of my device
HTML:
lrwxrwxrwx root root 2016-01-11 17:56 DDR -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2016-01-11 17:56 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2016-01-11 17:56 abootbak -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2016-01-11 17:56 boot -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2016-01-11 17:56 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2016-01-11 17:56 config -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2016-01-11 17:56 fsc -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2016-01-11 17:56 fsg -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2016-01-11 17:56 hyp -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2016-01-11 17:56 hypbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2016-01-11 17:56 keystore -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2016-01-11 17:56 misc -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2016-01-11 17:56 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2016-01-11 17:56 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2016-01-11 17:56 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2016-01-11 17:56 oem -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2016-01-11 17:56 pad -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2016-01-11 17:56 persist -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2016-01-11 17:56 recovery -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2016-01-11 17:56 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2016-01-11 17:56 rpmbak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2016-01-11 17:56 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2016-01-11 17:56 sbl1bak -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2016-01-11 17:56 sec -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2016-01-11 17:56 splash -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2016-01-11 17:56 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2016-01-11 17:56 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2016-01-11 17:56 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2016-01-11 17:56 tzbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2016-01-11 17:56 userdata -> /dev/block/mmcblk0p30
As you can see "mmcblk0p18" belongs to splash partiton.
I used "dd" command to dump splash.img on sdcard with adb shell.
But now what?
How to edit it?
I've searched for many hours but came up with mediatek or HTC thereads which is pretty annoying
Tools I've tried so far--> Android Kitchen, Kernel Kitchen, Logo Builder.
Please help me through this.. I desperately want to make a splash image for my device.
Thanks.
I was an idiot and attempted to flash the DP4 OTA zip file in TWRP. It started and progressed for a little bit then failed, and then it couldn't see any of my partitions. I tried to reboot into bootloader, but now the phone will literally not do anything (no LED, no screen, no vibrate), except sometimes give me some USB Com3 device in device manager.
Apparently I'm the second one on XDA that this has happened to, but the other guy just RMA'd his phone and didn't try and solve it using QPST or anything. I've got an RMA started with huawei, but they indicate it will take 10-14 business days from the day they receive my phone through UPS ground. Uggghhh...
Any alternatives?
ok, so I believe I could actually fix this myself if I had access to the contents of the bootloader. there are lots of utilities to restore "fastboot ROMs" to qualcomm SoC phones.
would someone mind running this for me on their 6p via an adb shell (then copying and pasting the results here)?
parted /dev/block/mmcblk0
all it does is print out the partition list from your phone
I'm kind of curious about how to solve this, so keep me posted on any updates. I'll do what I can to help.
Running parted in an adb shell isn't going to do anything, as parted is a CLI partition manager that doesn't exist on android. You can run parted on the majority of linux systems, but not on adb shell. What exactly are you trying to find out about the partitions? From the research I've done, it looks like you'd need a particular tool and file to flash from Huawei. According to my understanding, you'd need direct access to the SoC to directly flash firmware to it without a bootloader of any type, but my reading is suggesting that some devices have a backup bootloader. It may be best to go with the RMA, but if you want me to run any tools over here and post the results I can.
Morganmachine91 said:
I'll do what I can to help.
Click to expand...
Click to collapse
Thank you sir.
Morganmachine91 said:
Running parted in an adb shell isn't going to do anything, as parted is a CLI partition manager that doesn't exist on android. You can run parted on the majority of linux systems, but not on adb shell.
Click to expand...
Click to collapse
parted will run just fine in adb shell, just needs to be put in the /system/bin folder and chmod 0755 (see this post)
Morganmachine91 said:
What exactly are you trying to find out about the partitions?
Click to expand...
Click to collapse
I'm trying to possibly extract files from a functional 6p that I can then get on to my bricked device through QPST or another similar utility, as the 6p isn't the only Snapdragon 810 device out there, and a number of manufacturers of other 810 devices have provided flash utilities that utilize the Qualcomm emergency mode serial connection. I haven't found one from huawei yet though (a utility).
Morganmachine91 said:
From the research I've done, it looks like you'd need a particular tool and file to flash from Huawei. According to my understanding, you'd need direct access to the SoC to directly flash firmware to it without a bootloader of any type, but my reading is suggesting that some devices have a backup bootloader.
Click to expand...
Click to collapse
Exactly. So i caved, and went and bought another 6p from Bestbuy as their return policy is very liberal. This way I can try and fix my phone and cancel the RMA I've started (waiting for prepaid label from Huawei/UPS). I think i found the backup bootloader at /dev/block/mmcblk0p16, see my post below for more details.
Following the link I posted above, i learned how to get a partition listing without using parted.
Code:
[email protected]:/dev/block/platform/soc.0/f9824900.sdhci # ls -al by-name
lrwxrwxrwx root root 1970-04-24 07:44 DDR -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-04-24 07:44 aboot -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-04-24 07:44 abootbak -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-04-24 07:44 apdp -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-04-24 07:44 boot -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-04-24 07:44 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-04-24 07:44 cmnlib -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-04-24 07:44 cmnlibbak -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-04-24 07:44 devinfo -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-04-24 07:44 dpo -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-04-24 07:44 frp -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-04-24 07:44 fsc -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-04-24 07:44 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-04-24 07:44 hyp -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-04-24 07:44 hypbak -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-04-24 07:44 keymaster -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-04-24 07:44 keymasterbak -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-04-24 07:44 keystore -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-04-24 07:44 limits -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-04-24 07:44 metadata -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-04-24 07:44 misc -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-04-24 07:44 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-04-24 07:44 modemst1 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-04-24 07:44 modemst2 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-04-24 07:44 msadp -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-04-24 07:44 oem -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-04-24 07:44 oeminfo -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-04-24 07:44 persist -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-04-24 07:44 persistent -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-04-24 07:44 pmic -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-04-24 07:44 pmicbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-04-24 07:44 recovery -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-04-24 07:44 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-04-24 07:44 rpmbak -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-04-24 07:44 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-04-24 07:44 sbl1bak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-04-24 07:44 sdi -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-04-24 07:44 sec -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-04-24 07:44 ssd -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-04-24 07:44 system -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-04-24 07:44 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-04-24 07:44 tzbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-04-24 07:44 userdata -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-04-24 07:44 vendor -> /dev/block/mmcblk0p37
here is the parted output:
Code:
[email protected]:/sdcard/download # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Model: MMC 032G74 (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 8389kB 92.3MB 83.9MB fat16 modem
2 92.3MB 93.3MB 1049kB sbl1
3 93.3MB 93.4MB 98.3kB sdi
4 93.4MB 94.5MB 1049kB tz
5 94.5MB 95.0MB 512kB rpm
6 95.0MB 95.5MB 524kB hyp
7 95.5MB 95.6MB 131kB pmic
8 95.6MB 96.7MB 1049kB DDR
9 96.7MB 96.8MB 131kB sec
10 96.8MB 101MB 4485kB aboot
11 101MB 101MB 131kB pmicbak
12 101MB 102MB 1049kB sbl1bak
13 102MB 104MB 1049kB tzbak
14 104MB 104MB 512kB rpmbak
15 104MB 105MB 524kB hypbak
16 105MB 109MB 4485kB abootbak
17 109MB 109MB 1024B devinfo
18 117MB 122MB 4194kB fsg
19 126MB 126MB 1024B limits
20 134MB 138MB 4194kB modemst1
21 138MB 143MB 4194kB modemst2
22 143MB 143MB 262kB apdp
23 143MB 143MB 262kB msadp
24 143MB 143MB 262kB keymaster
25 143MB 144MB 262kB cmnlib
26 144MB 144MB 262kB keymasterbak
27 144MB 144MB 262kB cmnlibbak
28 144MB 144MB 1024B dpo
29 144MB 144MB 1024B fsc
30 144MB 144MB 8192B ssd
31 144MB 151MB 6806kB oeminfo
32 151MB 159MB 8389kB ext4 persist
33 159MB 176MB 16.8MB metadata
34 176MB 210MB 33.6MB boot
35 210MB 243MB 33.6MB recovery
36 243MB 310MB 67.1MB oem
37 310MB 520MB 210MB ext4 vendor
38 520MB 625MB 105MB ext4 cache
39 625MB 626MB 1049kB misc
40 626MB 627MB 524kB keystore
41 627MB 627MB 524kB frp
42 627MB 628MB 512kB persistent
43 628MB 3849MB 3221MB ext4 system
44 3849MB 31.3GB 27.4GB userdata
Research so far...
http://forum.xda-developers.com/showthread.php?t=1884417&page=2
http://kernel-develop.blogspot.com/2012/05/emmc-partition-tools-usage-for.html
http://kernel-develop.blogspot.com/2012/05/how-to-generate-8660msimagembn.html
http://forum.xda-developers.com/win...ate-rawprogram0-xml-ffu-file-extract-t3385201
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
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!