just starting a thread with some of the things we will need when unlocked or to help devs with unlocking this is also a discussion thread pertaining to bootloader development/hacks
these are from retail Verizon Note3 with build VRUBMI9
partition info:
Code:
lrwxrwxrwx root root 1969-12-31 22:37 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1969-12-31 22:37 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1969-12-31 22:37 backup -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1969-12-31 22:37 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1969-12-31 22:37 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1969-12-31 22:37 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1969-12-31 22:37 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1969-12-31 22:37 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1969-12-31 22:37 fota -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1969-12-31 22:37 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1969-12-31 22:37 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1969-12-31 22:37 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1969-12-31 22:37 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1969-12-31 22:37 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1969-12-31 22:37 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1969-12-31 22:37 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1969-12-31 22:37 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1969-12-31 22:37 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1969-12-31 22:37 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1969-12-31 22:37 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1969-12-31 22:37 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1969-12-31 22:37 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1969-12-31 22:37 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1969-12-31 22:37 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1969-12-31 22:37 userdata -> /dev/block/mmcblk0p25
PIT Analysis:
Code:
Started by user anonymous
[EnvInject] - Loading node environment variables.
Building in workspace /var/lib/jenkins/workspace/Analyze PIT File
Copying file to ./part.pit
[Analyze PIT File] $ /bin/bash +x /tmp/hudson5599640215980603364.sh
-----BEGIN PIT ANALYSIS-----
PIT Name: MSM8974
Entry Count: 29
File Type: COM_TAR2
--- Entry #0 ---
ID: 1 Partition Name: APNHLOS
Filename: NON-HLOS.bin
Block Size: 30720 (15.7MB)
Block range: 8192 - 38911 (hex 0x2000 - 0x97ff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The APNHLOS partition, identified as partition number 1, is 15.7MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as NON-HLOS.bin.
--- Entry #1 ---
ID: 2 Partition Name: MODEM
Filename: modem.bin
Block Size: 117632 (60.2MB)
Block range: 38912 - 156543 (hex 0x9800 - 0x2637f)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The MODEM partition, identified as partition number 2, is 60.2MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as modem.bin.
--- Entry #2 ---
ID: 3 Partition Name: SBL1
Filename: sbl1.mbn
Block Size: 1024 (524.3kB)
Block range: 156544 - 157567 (hex 0x26380 - 0x2677f)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The SBL1 partition, identified as partition number 3, is 524.3kB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as sbl1.mbn.
--- Entry #3 ---
ID: 4 Partition Name: DBI
Filename: sdi.mbn
Block Size: 64 (32.8kB)
Block range: 157568 - 157631 (hex 0x26780 - 0x267bf)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The DBI partition, identified as partition number 4, is 32.8kB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as sdi.mbn.
--- Entry #4 ---
ID: 5 Partition Name: DDR
Filename:
Block Size: 64 (32.8kB)
Block range: 157632 - 157695 (hex 0x267c0 - 0x267ff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The DDR partition, identified as partition number 5, is 32.8kB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC.
--- Entry #5 ---
ID: 6 Partition Name: ABOOT
Filename: aboot.mbn
Block Size: 4096 (2.1MB)
Block range: 157696 - 161791 (hex 0x26800 - 0x277ff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The ABOOT partition, identified as partition number 6, is 2.1MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as aboot.mbn.
--- Entry #6 ---
ID: 7 Partition Name: RPM
Filename: rpm.mbn
Block Size: 1024 (524.3kB)
Block range: 161792 - 162815 (hex 0x27800 - 0x27bff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The RPM partition, identified as partition number 7, is 524.3kB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as rpm.mbn.
--- Entry #7 ---
ID: 8 Partition Name: TZ
Filename: tz.mbn
Block Size: 1024 (524.3kB)
Block range: 162816 - 163839 (hex 0x27c00 - 0x27fff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The TZ partition, identified as partition number 8, is 524.3kB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as tz.mbn.
--- Entry #8 ---
ID: 9 Partition Name: PAD
Filename:
Block Size: 20480 (10.5MB)
Block range: 163840 - 184319 (hex 0x28000 - 0x2cfff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The PAD partition, identified as partition number 9, is 10.5MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC.
--- Entry #9 ---
ID: 10 Partition Name: PARAM
Filename: param.bin
Block Size: 20480 (10.5MB)
Block range: 184320 - 204799 (hex 0x2d000 - 0x31fff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The PARAM partition, identified as partition number 10, is 10.5MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as param.bin.
--- Entry #10 ---
ID: 11 Partition Name: EFS
Filename: efs.img.ext4
Block Size: 28672 (14.7MB)
Block range: 204800 - 233471 (hex 0x32000 - 0x38fff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The EFS partition, identified as partition number 11, is 14.7MB in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as efs.img.ext4.
--- Entry #11 ---
ID: 12 Partition Name: MODEMST1
Filename: nvrebuild1.bin
Block Size: 6144 (3.1MB)
Block range: 233472 - 239615 (hex 0x39000 - 0x3a7ff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The MODEMST1 partition, identified as partition number 12, is 3.1MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as nvrebuild1.bin.
--- Entry #12 ---
ID: 13 Partition Name: MODEMST2
Filename: nvrebuild2.bin
Block Size: 6144 (3.1MB)
Block range: 239616 - 245759 (hex 0x3a800 - 0x3bfff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The MODEMST2 partition, identified as partition number 13, is 3.1MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as nvrebuild2.bin.
--- Entry #13 ---
ID: 14 Partition Name: BOOT
Filename: boot.img
Block Size: 22528 (11.5MB)
Block range: 245760 - 268287 (hex 0x3c000 - 0x417ff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The BOOT partition, identified as partition number 14, is 11.5MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as boot.img.
--- Entry #14 ---
ID: 15 Partition Name: RECOVERY
Filename: recovery.img
Block Size: 26624 (13.6MB)
Block range: 268288 - 294911 (hex 0x41800 - 0x47fff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The RECOVERY partition, identified as partition number 15, is 13.6MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as recovery.img.
--- Entry #15 ---
ID: 16 Partition Name: FOTA
Filename:
Block Size: 26624 (13.6MB)
Block range: 294912 - 321535 (hex 0x48000 - 0x4e7ff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The FOTA partition, identified as partition number 16, is 13.6MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC.
--- Entry #16 ---
ID: 17 Partition Name: BACKUP
Filename:
Block Size: 14318 (7.3MB)
Block range: 321536 - 335853 (hex 0x4e800 - 0x51fed)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The BACKUP partition, identified as partition number 17, is 7.3MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC.
--- Entry #17 ---
ID: 18 Partition Name: FSG
Filename:
Block Size: 6144 (3.1MB)
Block range: 335854 - 341997 (hex 0x51fee - 0x537ed)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The FSG partition, identified as partition number 18, is 3.1MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC.
--- Entry #18 ---
ID: 19 Partition Name: FSC
Filename:
Block Size: 2 (1.0kB)
Block range: 341998 - 341999 (hex 0x537ee - 0x537ef)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The FSC partition, identified as partition number 19, is 1.0kB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC.
--- Entry #19 ---
ID: 20 Partition Name: SSD
Filename:
Block Size: 16 (8.2kB)
Block range: 342000 - 342015 (hex 0x537f0 - 0x537ff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The SSD partition, identified as partition number 20, is 8.2kB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC.
--- Entry #20 ---
ID: 21 Partition Name: PERSIST
Filename: persist.img.ext4
Block Size: 16384 (8.4MB)
Block range: 342016 - 358399 (hex 0x53800 - 0x577ff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The PERSIST partition, identified as partition number 21, is 8.4MB in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as persist.img.ext4.
--- Entry #21 ---
ID: 22 Partition Name: PERSDATA
Filename: persdata.img.ext4
Block Size: 18432 (9.4MB)
Block range: 358400 - 376831 (hex 0x57800 - 0x5bfff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The PERSDATA partition, identified as partition number 22, is 9.4MB in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as persdata.img.ext4.
--- Entry #22 ---
ID: 23 Partition Name: SYSTEM
Filename: system.img.ext4
Block Size: 5554176 (2.8GB)
Block range: 376832 - 5931007 (hex 0x5c000 - 0x5a7fff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The SYSTEM partition, identified as partition number 23, is 2.8GB in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as system.img.ext4.
--- Entry #23 ---
ID: 24 Partition Name: CACHE
Filename: cache.img.ext4
Block Size: 2097152 (1.1GB)
Block range: 5931008 - 8028159 (hex 0x5a8000 - 0x7a7fff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The CACHE partition, identified as partition number 24, is 1.1GB in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as cache.img.ext4.
--- Entry #24 ---
ID: 25 Partition Name: USERDATA
Filename: userdata.img.ext4
Block Size: 0 (0B)
Block range: 8028160 - 8028159 (hex 0x7a8000 - 0x7a7fff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA: remained
The USERDATA partition, identified as partition number 25, is 0B in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as userdata.img.ext4. The partition will expand to fill the remainder of the EMMC.
--- Entry #25 ---
ID: 70 Partition Name: PGPT
Filename: pgpt.img
Block Size: 34 (17.4kB)
Block range: 0 - 33 (hex 0x0 - 0x21)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The PGPT partition, identified as partition number 70, is 17.4kB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as pgpt.img.
--- Entry #26 ---
ID: 71 Partition Name: PIT
Filename: MSM8974.pit
Block Size: 16 (8.2kB)
Block range: 34 - 49 (hex 0x22 - 0x31)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The PIT partition, identified as partition number 71, is 8.2kB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as MSM8974.pit.
--- Entry #27 ---
ID: 72 Partition Name: MD5
Filename: md5.img
Block Size: 32 (16.4kB)
Block range: 50 - 81 (hex 0x32 - 0x51)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The MD5 partition, identified as partition number 72, is 16.4kB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as md5.img.
--- Entry #28 ---
ID: 73 Partition Name: SGPT
Filename: sgpt.img
Block Size: 33 (16.9kB)
Block range: 61071327 - 61071359 (hex 0x3a3dfdf - 0x3a3dfff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The SGPT partition, identified as partition number 73, is 16.9kB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as sgpt.img.
-----END PIT ANALYSIS-----
Finished: SUCCESS
aboot: http://www.androidfilehost.com/?fid=23159073880936456
pit: http://www.androidfilehost.com/?fid=23159073880936457
unbrick image for vzw n3: http://www.androidfilehost.com/?fid=23159073880937014 use in combo with design gears/shabbypenguins method just use this image instead of the one in his thread http://forum.xda-developers.com/showthread.php?t=2476353
Glad to see you here. Dumped the htc, huh? About time
Sent from my SM-N900V using Tapatalk
beanstown106 said:
just starting a thread with some of the things we will need when unlocked or to help devs with unlocking this is also a discussion thread pertaining to bootloader development/hacks
these are from retail Verizon Note3 with build VRUBMI9
partition info:
Code:
lrwxrwxrwx root root 1969-12-31 22:37 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1969-12-31 22:37 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1969-12-31 22:37 backup -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1969-12-31 22:37 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1969-12-31 22:37 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1969-12-31 22:37 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1969-12-31 22:37 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1969-12-31 22:37 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1969-12-31 22:37 fota -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1969-12-31 22:37 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1969-12-31 22:37 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1969-12-31 22:37 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1969-12-31 22:37 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1969-12-31 22:37 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1969-12-31 22:37 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1969-12-31 22:37 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1969-12-31 22:37 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1969-12-31 22:37 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1969-12-31 22:37 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1969-12-31 22:37 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1969-12-31 22:37 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1969-12-31 22:37 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1969-12-31 22:37 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1969-12-31 22:37 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1969-12-31 22:37 userdata -> /dev/block/mmcblk0p25
aboot:
pit:
Click to expand...
Click to collapse
So excited to see a bootloader unlock in the works. It's nice to see people/devs taking the time to try to benefit the community, via bootloader unlock.
aerichards1977 said:
Glad to see you here. Dumped the htc, huh? About time
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
ya returned it today and got the retail note3 still planning on getting the dev edition though
vampire5003 said:
So excited to see a bootloader unlock in the works. It's nice to see people/devs taking the time to try to benefit the community, via bootloader unlock.
Click to expand...
Click to collapse
dont think there is one in the works but a workaround for recovery most likely is. getting a true unlock on this device is highly unlikely.
Im waiting on that dev edition too!
Sent from my SM-N900V using Tapatalk
Oh man, I hope we will see a beans note 3 rom...
Sent from my SM-N900V using XDA Premium 4 mobile app
beanstown106 said:
ya returned it today and got the retail note3 still planning on getting the dev edition though
dont think there is one in the works but a workaround for recovery most likely is. getting a true unlock on this device is highly unlikely.
Click to expand...
Click to collapse
Beans
Sent you a donation for your great sammy support sir.
22 updates from you on note 2.
Can't wait 4 dev edt.
Thanks
---------- Post added at 10:11 PM ---------- Previous post was at 10:10 PM ----------
drsoftich said:
Oh man, I hope we will see a beans note 3 rom...
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Me too
Thanks for posting this! Pit file will definitely be useful for recovering from a soft brick!
Great to see you here too....Just got a Note 3 today!
Glad to see you beans...
Sent from my SM-N900V using Tapatalk now Free
Just to add if you so well please....wrote this up last week as a reference when I was gonna pull system dumps, but then the factory images got posted up for grabs and made them useless.....same sh1t, with small additions, plus partition sizes
Code:
major minor #blocks name Label
7 0 21861 loop0
7 1 3150 loop1
7 2 26019 loop2
7 3 9387 loop3
7 4 2111 loop4
7 5 4190 loop5
7 6 26019 loop6
179 0 30535680 mmcblk0
179 1 15360 mmcblk0p1 apnhlos
179 2 58816 mmcblk0p2 modem
179 3 512 mmcblk0p3 sbl1
179 4 32 mmcblk0p4 dbi
179 5 32 mmcblk0p5 ddr
179 6 2048 mmcblk0p6 aboot
179 7 512 mmcblk0p7 rpm
179 8 512 mmcblk0p8 tz
179 9 10240 mmcblk0p9 pad
179 10 10240 mmcblk0p10 param
179 11 14336 mmcblk0p11 efs
179 12 3072 mmcblk0p12 modemst1
179 13 3072 mmcblk0p13 modemst2
179 14 11264 mmcblk0p14 boot
179 15 13312 mmcblk0p15 recovery
179 16 13312 mmcblk0p16 fota
179 17 7159 mmcblk0p17 backup
179 18 3072 mmcblk0p18 fsg
179 19 1 mmcblk0p19 fsc
179 20 8 mmcblk0p20 ssd
179 21 8192 mmcblk0p21 persist
179 22 9216 mmcblk0p22 persdata
179 23 2777088 mmcblk0p23 system
179 24 1048576 mmcblk0p24 cache
179 25 26521583 mmcblk0p25 userdata
179 32 512 mmcblk0rpmb
179 64 30702592 mmcblk1
179 65 30701568 mmcblk1p1
254 0 21861 dm-0
254 1 3150 dm-1
254 2 26019 dm-2
254 3 9387 dm-3
254 4 2110 dm-4
254 5 4189 dm-5
254 6 26019 dm-6
AS A SIDE NOTE:
Now if other people feel like doing the same thing I WAS gonna do before the images got posted, and pull your own stuff for safe-keeping, you can do the following commands in adb:
(Root required for this method)
Code:
> adb shell
> su
> dd if=/dev/block/mmcblk0p15 of=/sdcard/recovery.img
This will pull the factory stock recovery image and place it on your internal sd-card for you to do what you please with. Note for others, you need replace location and file name.
Beans..
Great to see you with n3. I still have to take your 22 off my n2 and go back to factory so I can put it on eBay.
Looking forward to some great roms from you in the future.
Sent from my SM-N900V using xda app-developers app
imbolc said:
Beans..
Great to see you with n3. I still have to take your 22 off my n2 and go back to factory so I can put it on eBay.
Looking forward to some great roms from you in the future.
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
Same here on all points!
My coworker also a Note 2 and was considering a HTC One Max but when I told him Beans was hanging out in the Note 3 forums he picked up the Note 3 instead. Can't wait for Beans on Note 3!
Beans + note 3= Best phone ever. However you are right Beans, unlock unlikely. I might sell mine and get the dev edition too. Are you going to make a rom for the dev edition?
Sent from my SM-N900V using Tapatalk
Just waiting on either the dev edition or the unlocked bootloader. Glad to see you here man. Thanks for this.
Sent from my SPH-L900 using Xparent BlueTapatalk 2
Team Nocturnal Member
Always RoCkIn GoOdNeSs
[email protected]
cool beans
glad to see beans on this too... was using his rom for my s3 for the longest time... a dev N3 isnt in my future so i hope you guys can get something working
From all the notes i see regarding bootloader unlock it doesn't appear that anyone is optimistic. Someone correct me if you have seen otherwise? If this is going to likely remain locked down, i'm gonna have a hard decision to make. For those that are gonna jump ship before to another device, which are you considering?
760hacker said:
From all the notes i see regarding bootloader unlock it doesn't appear that anyone is optimistic. Someone correct me if you have seen otherwise? If this is going to likely remain locked down, i'm gonna have a hard decision to make. For those that are gonna jump ship before to another device, which are you considering?
Click to expand...
Click to collapse
Pretty sure we'll get bootloader bypass and recovery at the very least. Unlock may not be possible but with a bypass you can still install roms and kernels and functions almost the same for the most part.
Sent from my SM-N900V using Tapatalk
Right but using kexec?
Sent from my SM-N900V using Tapatalk
I have seen It happen with Amazons second gen. Kindle Fire @Hashcode rocked right through that issue good chance he could be an asset in the search. I can not speak for the Devs but I can say these guys twist up the ball of adversity that companies try to push at us and over hand pitch it back at them. It can be done when is the only question, now just patience is required. Power to the Devs!!
Related
To run this commands you need a rooted device with BusyBox and parted.
Code:
[email protected]:/ #[COLOR="Blue"] [B]cat /proc/partitions[/B][/COLOR]
major minor #blocks name
179 0 30535680 mmcblk0
179 1 65536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 1024 mmcblk0p6
179 7 16384 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 1 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 1 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 32768 mmcblk0p14
179 15 16384 mmcblk0p15
179 16 3072 mmcblk0p16
179 17 512 mmcblk0p17
179 18 512 mmcblk0p18
179 19 1 mmcblk0p19
179 20 512 mmcblk0p20
179 21 8192 mmcblk0p21
179 22 8192 mmcblk0p22
179 23 32768 mmcblk0p23
179 24 32768 mmcblk0p24
179 25 32768 mmcblk0p25
179 26 512 mmcblk0p26
179 27 1024 mmcblk0p27
179 28 1024 mmcblk0p28
179 29 8 mmcblk0p29
179 30 2834432 mmcblk0p30
179 31 622592 mmcblk0p31
259 0 81920 mmcblk0p32
259 1 16384 mmcblk0p33
259 2 49152 mmcblk0p34
259 3 26460160 mmcblk0p35
259 4 61423 mmcblk0p36
179 32 4096 mmcblk0rpmb
Code:
[email protected]:/ # [B][COLOR="Blue"]ls -l /dev/block/platform/msm_sdcc.1/by-num/[/COLOR][/B]
lrwxrwxrwx root root 1970-01-15 23:14 p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-15 23:14 p10 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-15 23:14 p11 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-15 23:14 p12 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-15 23:14 p13 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-15 23:14 p14 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-15 23:14 p15 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-15 23:14 p16 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-15 23:14 p17 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-15 23:14 p18 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-15 23:14 p19 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-15 23:14 p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-15 23:14 p20 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-15 23:14 p21 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-15 23:14 p22 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-15 23:14 p23 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-15 23:14 p24 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-15 23:14 p25 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-15 23:14 p26 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-15 23:14 p27 -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-15 23:14 p28 -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-15 23:14 p29 -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-15 23:14 p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-15 23:14 p30 -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-15 23:14 p31 -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-15 23:14 p32 -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-15 23:14 p33 -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-15 23:14 p34 -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-15 23:14 p35 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-15 23:14 p36 -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-15 23:14 p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-15 23:14 p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-15 23:14 p6 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-15 23:14 p7 -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-15 23:14 p8 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-15 23:14 p9 -> /dev/block/mmcblk0p9
Code:
[email protected]:/ # [B][COLOR="Blue"]ls -l /dev/block/platform/msm_sdcc.1/by-name/[/COLOR][/B]
lrwxrwxrwx root root 1970-01-15 23:14 DDR -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-15 23:14 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-15 23:14 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-15 23:14 cache -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-15 23:14 cust -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-15 23:14 dbi -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-15 23:14 dbibak -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-15 23:14 drm -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-15 23:14 encrypt -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-15 23:14 fota -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-15 23:14 fsc -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-15 23:14 fsg -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-15 23:14 grow -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-15 23:14 laf -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-15 23:14 misc -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-15 23:14 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-15 23:14 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-15 23:14 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-15 23:14 mpt -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-15 23:14 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-15 23:14 pad1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-15 23:14 pad2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-15 23:14 persist -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-15 23:14 rct -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-15 23:14 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-15 23:14 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-15 23:14 rpmbak -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-15 23:14 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-15 23:14 sns -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-15 23:14 spare -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-15 23:14 ssd -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-15 23:14 system -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-15 23:14 tombstones -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-15 23:14 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-15 23:14 tzbak -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-15 23:14 userdata -> /dev/block/mmcblk0p35
Code:
[email protected]:/ # [B][COLOR="Blue"]parted /dev/block/mmcblk0[/COLOR][/B]
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 032GE4 (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 16.8MB 83.9MB 67.1MB fat16 modem
2 83.9MB 84.9MB 1049kB sbl1
3 84.9MB 85.5MB 524kB dbi
4 101MB 101MB 524kB DDR
5 117MB 118MB 1049kB aboot
6 118MB 120MB 1049kB rpm
7 134MB 151MB 16.8MB boot
8 151MB 152MB 1049kB tz
9 152MB 152MB 1024B pad
10 168MB 171MB 3146kB modemst1
11 171MB 174MB 3146kB modemst2
12 174MB 174MB 1024B pad1
13 185MB 201MB 16.8MB misc
14 201MB 235MB 33.6MB ext4 persist
15 235MB 252MB 16.8MB recovery
16 252MB 255MB 3146kB fsg
17 268MB 269MB 524kB fsc
18 269MB 269MB 524kB ssd
19 269MB 269MB 1024B pad2
20 269MB 270MB 524kB encrypt
21 285MB 294MB 8389kB ext4 drm
22 294MB 302MB 8389kB ext4 sns
23 302MB 336MB 33.6MB laf
24 336MB 369MB 33.6MB fota
25 369MB 403MB 33.6MB ext4 mpt
26 403MB 403MB 524kB dbibak
27 403MB 404MB 1049kB rpmbak
28 404MB 405MB 1049kB tzbak
29 405MB 405MB 8192B rct
30 419MB 3322MB 2902MB ext4 system
31 3322MB 3959MB 638MB ext4 cache
32 3959MB 4043MB 83.9MB tombstones
33 4043MB 4060MB 16.8MB spare
34 4060MB 4110MB 50.3MB ext4 cust
35 4110MB 31.2GB 27.1GB ext4 userdata
36 31.2GB 31.3GB 62.9MB grow
Code:
[email protected]:/ # [B][COLOR="Blue"]mount[/COLOR][/B]
rootfs / rootfs ro,relatime 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
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,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,resuid=1000,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/sns /sns ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/drm /persist-lg ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/mpt /mpt ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/cust /cust ext4 ro,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Code:
[email protected]:/ # [B][COLOR="Blue"]df[/COLOR][/B]
Filesystem Size Used Free Blksize
/dev 926.51M 128.00K 926.39M 4096
/sys/fs/cgroup 926.51M 12.00K 926.50M 4096
/mnt/asec 926.51M 0.00K 926.51M 4096
/mnt/obb 926.51M 0.00K 926.51M 4096
/system 2.66G 2.17G 495.23M 4096
/data 24.80G 20.77G 4.03G 4096
/sns 7.83M 4.03M 3.80M 4096
/persist-lg 7.83M 4.35M 3.48M 4096
/mpt 31.46M 12.96M 18.49M 4096
/cache 597.97M 9.59M 588.38M 4096
/persist 31.46M 4.05M 27.41M 4096
/firmware 63.95M 52.36M 11.59M 16384
/cust 46.22M 8.18M 38.04M 4096
/storage/emulated 926.51M 0.00K 926.51M 4096
/mnt/shell/emulated 24.80G 20.77G 4.03G 4096
/storage/emulated/legacy 24.80G 20.77G 4.03G 4096
/storage/emulated/0 24.80G 20.77G 4.03G 4096
/storage/emulated/0/Android/obb 24.80G 20.77G 4.03G 4096
/storage/emulated/legacy 24.80G 20.77G 4.03G 4096
/storage/emulated/legacy/Android/obb 24.80G 20.77G 4.03G 4096
Code:
[email protected]:/ # [B][COLOR="Blue"]find /dev/block/platform/msm_sdcc.1/ -name 'mmc*' -exec fdisk -l {} \;[/COLOR][/B]
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p36: 62 MB, 62897664 bytes
4 heads, 16 sectors/track, 1919 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p36 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p35: 27.0 GB, 27095203840 bytes
4 heads, 16 sectors/track, 826880 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p35 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p34: 50 MB, 50331648 bytes
4 heads, 16 sectors/track, 1536 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p34 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p33: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p33 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p32: 83 MB, 83886080 bytes
4 heads, 16 sectors/track, 2560 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p32 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p31: 637 MB, 637534208 bytes
4 heads, 16 sectors/track, 19456 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p31 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p30: 2902 MB, 2902458368 bytes
4 heads, 16 sectors/track, 88576 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p30 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p29: 0 MB, 8192 bytes
4 heads, 16 sectors/track, 0 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p29 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p28: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p28 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p27: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p27 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p26: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p26 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p25: 33 MB, 33554432 bytes
4 heads, 16 sectors/track, 1024 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p25 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p24: 33 MB, 33554432 bytes
4 heads, 16 sectors/track, 1024 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p24 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p23: 33 MB, 33554432 bytes
4 heads, 16 sectors/track, 1024 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p23 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p22: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p22 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p21: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p21 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p20: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p20 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p19: 0 MB, 1024 bytes
4 heads, 16 sectors/track, 0 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p19 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p18: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p18 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p17: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p17 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p16: 3 MB, 3145728 bytes
4 heads, 16 sectors/track, 96 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p16 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p15: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p15 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p14: 33 MB, 33554432 bytes
4 heads, 16 sectors/track, 1024 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p14 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p13: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p13 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p12: 0 MB, 1024 bytes
4 heads, 16 sectors/track, 0 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p12 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p11: 3 MB, 3145728 bytes
4 heads, 16 sectors/track, 96 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p11 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p10: 3 MB, 3145728 bytes
4 heads, 16 sectors/track, 96 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p10 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0rpmb: 4 MB, 4194304 bytes
4 heads, 16 sectors/track, 128 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0rpmb doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p9: 0 MB, 1024 bytes
4 heads, 16 sectors/track, 0 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p9 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p8: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p8 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p7: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p7 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p6: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p6 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p5: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p5 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p4: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p4 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p3: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p3 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p2: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p2 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p1: 67 MB, 67108864 bytes
4 heads, 16 sectors/track, 2048 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/platform/msm_sdcc.1/mmcblk0p1p1 ? 12158374 29994462 570754815+ 72 Unknown
Partition 1 does not end on cylinder boundary
/dev/block/platform/msm_sdcc.1/mmcblk0p1p2 ? 2635774 32886216 968014120 65 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/platform/msm_sdcc.1/mmcblk0p1p3 ? 29216898 59467339 968014096 79 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/platform/msm_sdcc.1/mmcblk0p1p4 ? 1 56831664 1818613248 d Unknown
Partition 4 does not end on cylinder boundary
Partition table entries are not in disk order
Disk /dev/block/platform/msm_sdcc.1/mmcblk0: 31.2 GB, 31268536320 bytes
256 heads, 63 sectors/track, 3786 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes
Device Boot Start End Blocks Id System
/dev/block/platform/msm_sdcc.1/mmcblk0p1
Additional links:
[GUIDE] Making Dump Files Out of Android Device Partitions
parted from cyanogenmod repo
The 4 partitions modified by AutoRec are the following, so backup with dd before applying.
bender_007 said:
^ aboot, boot, laf + recovery
Click to expand...
Click to collapse
I had this question elsewhere as well - can we force our phone into QH-USB 9006 mode ? This shows all the other partitions like aboot, boot, recovery etc and is directly flashable using "dd" . I recovered my bricked phone through this method, but I was in QH USB 9008 mode... not sure how to get this for people who are stuck in LG boot screen (and can neither get to download mode or fastboot)
sandys1 said:
I had this question elsewhere as well - can we force our phone into QH-USB 9006 mode ? This shows all the other partitions like aboot, boot, recovery etc and is directly flashable using "dd" . I recovered my bricked phone through this method, but I was in QH USB 9008 mode... not sure how to get this for people who are stuck in LG boot screen (and can neither get to download mode or fastboot)
Click to expand...
Click to collapse
Didn't try either using dd to write a custom recovery being root either. Gor the QH USB 9008 mode here's a guide.
[FIX] Unbrick LG G2 stuck in Qualcomm HS-USB QDLoader 9008 mode
so what's grow partition function? i managed to delete it to give some extra space on userdata.
hyperionx7 said:
so what's grow partition function? i managed to delete it to give some extra space on userdata.
Click to expand...
Click to collapse
You deleted a system partition that you don't know what's for to get 62.9MB more space?
When I look inside /dev/block, I see a lot of partitions on mmcblk0 (and I have confirmed, just to be certain, the combined size of all partitions almost exactly equals the size of mmcblk0 on its own):
Code:
~ # ls mmcblk0*
mmcblk0
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p13
mmcblk0p14
mmcblk0p15
mmcblk0p16
mmcblk0p17
mmcblk0p18
mmcblk0p19
mmcblk0p2
mmcblk0p20
mmcblk0p21
mmcblk0p22
mmcblk0p23
mmcblk0p24
mmcblk0p25
mmcblk0p26
mmcblk0p27
mmcblk0p28
mmcblk0p29
mmcblk0p3
mmcblk0p30
mmcblk0p31
mmcblk0p32
mmcblk0p33
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
What is even more bizarre is I get even more partitions listed when I use fdisk:
Code:
~ # fdisk -l -u /dev/block/mmcblk0
Warning: deleting partitions after 60
Disk /dev/block/mmcblk0: 2432 MB, 2432696320 bytes
1 heads, 16 sectors/track, 296960 cylinders, total 4751360 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 1000 500 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 1001 1128 64 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 1129 10128 4500 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 10129 4751358 2370615 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 10130 70129 30000 49 Unknown
/dev/block/mmcblk0p6 70131 95130 12500 50 Unknown
/dev/block/mmcblk0p7 95132 99227 2048 51 Unknown
/dev/block/mmcblk0p8 99229 105372 3072 52 Unknown
/dev/block/mmcblk0p9 105374 109469 2048 53 Unknown
/dev/block/mmcblk0p10 109471 111518 1024 54 Unknown
/dev/block/mmcblk0p11 111520 113567 1024 56 Unknown
/dev/block/mmcblk0p12 113569 131071 8751+ 55 Unknown
/dev/block/mmcblk0p13 131073 139264 4096 4a Unknown
/dev/block/mmcblk0p14 139266 147457 4096 4b Unknown
/dev/block/mmcblk0p15 147459 149506 1024 74 Unknown
/dev/block/mmcblk0p16 149508 163326 6909+ 75 Unknown
/dev/block/mmcblk0p17 163328 163839 256 76 Unknown
/dev/block/mmcblk0p18 163841 165888 1024 47 Unknown
/dev/block/mmcblk0p19 165890 167937 1024 34 Unknown
/dev/block/mmcblk0p20 167939 170498 1280 36 Unknown
/dev/block/mmcblk0p21 170500 187901 8701 71 Unknown
/dev/block/mmcblk0p22 187903 196094 4096 48 Unknown
/dev/block/mmcblk0p23 196096 196607 256 73 Unknown
/dev/block/mmcblk0p24 196609 200702 2047 26 Unknown
/dev/block/mmcblk0p25 200704 1835006 817151+ 83 Linux
/dev/block/mmcblk0p26 1835008 3833854 999423+ 83 Linux
/dev/block/mmcblk0p27 3833856 4095998 131071+ 83 Linux
/dev/block/mmcblk0p28 4096000 4452350 178175+ 83 Linux
/dev/block/mmcblk0p29 4452352 4456446 2047+ 33 Unknown
/dev/block/mmcblk0p30 4456448 4504942 24247+ 19 Unknown
/dev/block/mmcblk0p31 4504944 4505085 71 90 Unknown
/dev/block/mmcblk0p32 4505087 4505598 256 23 Unknown
/dev/block/mmcblk0p33 4505600 4702191 98296 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p34 10130 70129 30000 49 Unknown
/dev/block/mmcblk0p35 70131 95130 12500 50 Unknown
/dev/block/mmcblk0p36 95132 99227 2048 51 Unknown
/dev/block/mmcblk0p37 99229 105372 3072 52 Unknown
/dev/block/mmcblk0p38 105374 109469 2048 53 Unknown
/dev/block/mmcblk0p39 109471 111518 1024 54 Unknown
/dev/block/mmcblk0p40 111520 113567 1024 56 Unknown
/dev/block/mmcblk0p41 113569 131071 8751+ 55 Unknown
/dev/block/mmcblk0p42 131073 139264 4096 4a Unknown
/dev/block/mmcblk0p43 139266 147457 4096 4b Unknown
/dev/block/mmcblk0p44 147459 149506 1024 74 Unknown
/dev/block/mmcblk0p45 149508 163326 6909+ 75 Unknown
/dev/block/mmcblk0p46 163328 163839 256 76 Unknown
/dev/block/mmcblk0p47 163841 165888 1024 47 Unknown
/dev/block/mmcblk0p48 165890 167937 1024 34 Unknown
/dev/block/mmcblk0p49 167939 170498 1280 36 Unknown
/dev/block/mmcblk0p50 170500 187901 8701 71 Unknown
/dev/block/mmcblk0p51 187903 196094 4096 48 Unknown
/dev/block/mmcblk0p52 196096 196607 256 73 Unknown
/dev/block/mmcblk0p53 196609 200702 2047 26 Unknown
/dev/block/mmcblk0p54 200704 1835006 817151+ 83 Linux
/dev/block/mmcblk0p55 1835008 3833854 999423+ 83 Linux
/dev/block/mmcblk0p56 3833856 4095998 131071+ 83 Linux
/dev/block/mmcblk0p57 4096000 4452350 178175+ 83 Linux
/dev/block/mmcblk0p58 4452352 4456446 2047+ 33 Unknown
/dev/block/mmcblk0p59 4456448 4504942 24247+ 19 Unknown
/dev/block/mmcblk0p60 4504944 4505085 71 90 Unknown
Partition table entries are not in disk order
The thing is, those extra partitions don't seem to be in use. Running mount only lists the following partitions as mounted somewhere (irrelevant mounts excluded from the output)
Code:
/dev/block/mmcblk0p25 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p26 /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p28 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p30 /devlog ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
What are all these extra partitions for?
Is this specific to my particular device (HTC One V, with firmware for Cricket Wireless), or do all Android devices have this sheer number partitions?
I am getting a Galaxy View on Monday but in the mean time i have made a basic twrp tree can someone run these commands on there device so i can get the partition sizes .
Code:
adb shell
ls -al /dev/block/platform/13540000.dwmmc0/by-name
deadman96385 said:
I am getting a Galaxy View on Monday but in the mean time i have made a basic twrp tree can someone run these commands on there device so i can get the partition sizes .
Click to expand...
Click to collapse
Do you still need this done..?.. I have the Verizon Version of the Galaxy View.
justjayhere said:
Do you still need this done..?.. I have the Verizon Version of the Galaxy View.
Click to expand...
Click to collapse
I have gotten the sizes still working on getting twrp to boot.
deadman96385 said:
I have gotten the sizes still working on getting twrp to boot.
Click to expand...
Click to collapse
I am looking forward to getting root for Galaxy View.
justjayhere said:
I am looking forward to getting root for Galaxy View.
Click to expand...
Click to collapse
@ashyx and I have gotten the wifi variant to boot twrp can you grab the partition sizes for your tablet just run these commands and paste there output here or in a pastebin
Code:
adb shell
ls -al /dev/block/platform/13540000.dwmmc0/by-name
cat /proc/partitions
deadman96385 said:
@ashyx and I have gotten the wifi variant to boot twrp can you grab the partition sizes for your tablet just run these commands and paste there output here or in a pastebin
Click to expand...
Click to collapse
I will do so later today...currently out of town.
Verizon 4G 64GB version Partition Info
deadman96385 said:
I am getting a Galaxy View on Monday but in the mean time i have made a basic twrp tree can someone run these commands on there device so i can get the partition sizes .
Code:
adb shell
ls -al /dev/block/platform/13540000.dwmmc0/by-name
Click to expand...
Click to collapse
Verizon 4G 64GB version...
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ ls -al /dev/block/platform/13540000.dwmmc0/by-name
ls -al /dev/block/platform/13540000.dwmmc0/by-name
lrwxrwxrwx root root 2016-10-06 15:51 BOOT -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2016-10-06 15:51 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2016-10-06 15:51 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2016-10-06 15:51 CACHE -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2016-10-06 15:51 CARRIER -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2016-10-06 15:51 CDMA-RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2016-10-06 15:51 CPEFS -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2016-10-06 15:51 DNT -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2016-10-06 15:51 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2016-10-06 15:51 OTA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2016-10-06 15:51 PARAM -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2016-10-06 15:51 PERSDATA -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2016-10-06 15:51 PERSISTENT -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2016-10-06 15:51 RADIO -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2016-10-06 15:51 RECOVERY -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2016-10-06 15:51 RESERVED2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2016-10-06 15:51 SYSTEM -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2016-10-06 15:51 TOMBSTONES -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2016-10-06 15:51 USERDATA -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2016-10-06 15:51 m9kefs1 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2016-10-06 15:51 m9kefs2 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2016-10-06 15:51 m9kefs3 -> /dev/block/mmcblk0p7
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 61071360 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 4096 mmcblk0p7
259 0 15360 mmcblk0p8
259 1 8192 mmcblk0p9
259 2 32768 mmcblk0p10
259 3 38912 mmcblk0p11
259 4 8192 mmcblk0p12
259 5 4096 mmcblk0p13
259 6 90112 mmcblk0p14
259 7 1024 mmcblk0p15
259 8 1024 mmcblk0p16
259 9 512 mmcblk0p17
259 10 12288 mmcblk0p18
259 11 2560 mmcblk0p19
259 12 3072000 mmcblk0p20
259 13 1048576 mmcblk0p21
259 14 56676352 mmcblk0p22
179 24 4096 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
253 0 1048576 vnswap0
[email protected]:/ $
justjayhere said:
Verizon 4G 64GB version...
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ ls -al /dev/block/platform/13540000.dwmmc0/by-name
ls -al /dev/block/platform/13540000.dwmmc0/by-name
lrwxrwxrwx root root 2016-10-06 15:51 BOOT -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2016-10-06 15:51 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2016-10-06 15:51 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2016-10-06 15:51 CACHE -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2016-10-06 15:51 CARRIER -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2016-10-06 15:51 CDMA-RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2016-10-06 15:51 CPEFS -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2016-10-06 15:51 DNT -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2016-10-06 15:51 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2016-10-06 15:51 OTA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2016-10-06 15:51 PARAM -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2016-10-06 15:51 PERSDATA -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2016-10-06 15:51 PERSISTENT -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2016-10-06 15:51 RADIO -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2016-10-06 15:51 RECOVERY -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2016-10-06 15:51 RESERVED2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2016-10-06 15:51 SYSTEM -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2016-10-06 15:51 TOMBSTONES -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2016-10-06 15:51 USERDATA -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2016-10-06 15:51 m9kefs1 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2016-10-06 15:51 m9kefs2 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2016-10-06 15:51 m9kefs3 -> /dev/block/mmcblk0p7
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 61071360 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 4096 mmcblk0p7
259 0 15360 mmcblk0p8
259 1 8192 mmcblk0p9
259 2 32768 mmcblk0p10
259 3 38912 mmcblk0p11
259 4 8192 mmcblk0p12
259 5 4096 mmcblk0p13
259 6 90112 mmcblk0p14
259 7 1024 mmcblk0p15
259 8 1024 mmcblk0p16
259 9 512 mmcblk0p17
259 10 12288 mmcblk0p18
259 11 2560 mmcblk0p19
259 12 3072000 mmcblk0p20
259 13 1048576 mmcblk0p21
259 14 56676352 mmcblk0p22
179 24 4096 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
253 0 1048576 vnswap0
[email protected]:/ $
Click to expand...
Click to collapse
I would say try the wifi build but i can't recommend it due to there not being any firmware builds for the Verizon variant so i can't get a stock recovery image from it in case it doesn't work.
ValueError: malformed recovery.fstab line: "/boot emmc /dev/block/platform/sprd-sdhci
I need help with compiling CM-13 for my device, I've been following AlaskaLinuxUser's guide for building the device tree from scratch. I'm stuck at one point when building that I just can't figure out though, can anyone help me please?
Made recovery image: /home/raid/android/system/out/target/product/goyave3g/recovery.img
Target build info: /home/raid/android/system/out/target/product/goyave3g/system/build.prop
Construct recovery from boot
mkdir -p /home/raid/android/system/out/target/product/goyave3g/obj/PACKAGING/recovery_patch_intermediates/
PATH=/home/raid/android/system/out/host/linux-x86/bin:$PATH /home/raid/android/system/out/host/linux-x86/bin/imgdiff /home/raid/android/system/out/target/product/goyave3g/boot.img /home/raid/android/system/out/target/product/goyave3g/recovery.img /home/raid/android/system/out/target/product/goyave3g/obj/PACKAGING/recovery_patch_intermediates/recovery_from_boot.p
build/tools/generate-notice-files.py /home/raid/android/system/out/target/product/goyave3g/obj/NOTICE.txt /home/raid/android/system/out/target/product/goyave3g/obj/NOTICE.html "Notices for files contained in the filesystem images in this directory:" /home/raid/android/system/out/target/product/goyave3g/obj/NOTICE_FILES/src
failed to reconstruct target deflate chunk 1 [(null)]; treating as normal
chunk 0: type 0 start 0 len 5230602
chunk 1: type 2 start 5230602 len 1732096
chunk 2: type 0 start 6193783 len 269705
Construct patches for 3 chunks...
Combining NOTICE files into HTML
Combining NOTICE files into text
patch 0 is 206 bytes (of 5230602)
patch 1 is 1730987 bytes (of 963181)
patch 2 is 196 bytes (of 269705)
chunk 0: normal ( 0, 5230602) 206
chunk 1: deflate ( 5230602, 3389635) 1730987 (null)
chunk 2: normal ( 8620237, 270131) 196
Installing recovery patch to system partition
Traceback (most recent call last):
File "./build/tools/releasetools/make_recovery_patch", line 55, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/make_recovery_patch", line 37, in main
OPTIONS.info_dict = common.LoadInfoDict(input_dir)
File "/home/raid/android/system/build/tools/releasetools/common.py", line 201, in LoadInfoDict
d["fstab"] = LoadRecoveryFSTab(read_helper, d["fstab_version"], d["device_type"])
File "/home/raid/android/system/build/tools/releasetools/common.py", line 285, in LoadRecoveryFSTab
raise ValueError("malformed recovery.fstab line: "%s"" % (line,))
ValueError: malformed recovery.fstab line: "/boot emmc /dev/block/platform/sprd-sdhci.3/by-name/KERNEL"
build/core/Makefile:1074: recipe for target '/home/raid/android/system/out/target/product/goyave3g/system/bin/install-recovery.sh' failed
make: *** [/home/raid/android/system/out/target/product/goyave3g/system/bin/install-recovery.sh] Error 1
make: Leaving directory '/home/raid/android/system'
#### make failed to build some targets (03:18 (mm:ss)) ####
Click to expand...
Click to collapse
This is what is in my recovery.fstab
/boot emmc /dev/block/platform/sprd-sdhci.3/by-name/KERNEL
/system ext4 /dev/block/platform/sprd-sdhci.3/by-name/system
/data ext4 /dev/block/platform/sprd-sdhci.3/by-name/userdata flags=length=-16384
/cache ext4 /dev/block/platform/sprd-sdhci.3/by-name/CSC
/recovery emmc /dev/block/platform/sprd-sdhci.3/by-name/RECOVERY
/efs emmc /dev/block/platform/sprd-sdhci.3/by-name/efs flags=backup=1;display=EFS
/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/usb-otg vfat /dev/block/sda1 /dev/block/sda flags=removable;storage;display=USB-OTG
Click to expand...
Click to collapse
EDIT:
Here is some partition information from my device
Number Start End Size File system Name Flags
1 4194304B 6291455B 2097152B SBOOT msftdata
2 6291456B 8388607B 2097152B SBOOT2 msftdata
3 8388608B 9437183B 1048576B wfixnv1 msftdata
4 9437184B 10485759B 1048576B wfixnv2 msftdata
5 10485760B 11534335B 1048576B tdfixnv1 msftdata
6 11534336B 12582911B 1048576B tdfixnv2 msftdata
7 12582912B 16777215B 4194304B WDSP msftdata
8 16777216B 25165823B 8388608B MODEM msftdata
9 25165824B 33554431B 8388608B MODEM2 msftdata
10 33554432B 37748735B 4194304B TDDSP msftdata
11 37748736B 38797311B 1048576B FOTA_SIG msftdata
12 38797312B 39845887B 1048576B wruntimenv1 msftdata
13 39845888B 40894463B 1048576B wruntimenv2 msftdata
14 40894464B 41943039B 1048576B tdruntimenv1 msftdata
15 41943040B 42991615B 1048576B tdruntimenv2 msftdata
16 42991616B 45088767B 2097152B PARAM msftdata
17 45088768B 66060287B 20971520B ext4 efs msftdata
18 66060288B 71303167B 5242880B ext4 prodnv msftdata
19 71303168B 72351743B 1048576B RESERVED2 msftdata
20 72351744B 89128959B 16777216B KERNEL msftdata
21 89128960B 105906175B 16777216B RECOVERY msftdata
22 105906176B 315621375B 209715200B ext4 CSC msftdata
23 315621376B 1888485375B 1572864000B ext4 system msftdata
24 1888485376B 1901068287B 12582912B ext4 HIDDEN msftdata
25 1901068288B 7802454015B 5901385728B ext4 userdata msftdata
Click to expand...
Click to collapse
lrwxrwxrwx root root 2019-05-20 19:56 CSC -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2019-05-20 19:56 FOTA_SIG -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2019-05-20 19:56 HIDDEN -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2019-05-20 19:56 KERNEL -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2019-05-20 19:56 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2019-05-20 19:56 MODEM2 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2019-05-20 19:56 PARAM -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2019-05-20 19:56 RECOVERY -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2019-05-20 19:56 RESERVED2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2019-05-20 19:56 SBOOT -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2019-05-20 19:56 SBOOT2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2019-05-20 19:56 TDDSP -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2019-05-20 19:56 WDSP -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2019-05-20 19:56 efs -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2019-05-20 19:56 prodnv -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2019-05-20 19:56 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2019-05-20 19:56 tdfixnv1 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2019-05-20 19:56 tdfixnv2 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2019-05-20 19:56 tdruntimenv1 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2019-05-20 19:56 tdruntimenv2 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2019-05-20 19:56 userdata -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2019-05-20 19:56 wfixnv1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2019-05-20 19:56 wfixnv2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2019-05-20 19:56 wruntimenv1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2019-05-20 19:56 wruntimenv2 -> /dev/block/mmcblk0p13
Click to expand...
Click to collapse
Any help would be greatly appreciated!
Thanks!
Hello everyone!
I'd like to better understand my smartphone's Partitions Layout...
At the moment I'm inside TWRP and I managed to enter into Shell as root:
Code:
\platform-tools>adb.exe shell
~ #
So... I'm gathering these infos:
~ # fdisk /dev/block/mmcblk0
Code:
Found valid GPT with protective MBR; using GPT
Command (m for help): p
Disk /dev/block/mmcblk0: 30535680 sectors, 2622M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 52 entries
First usable sector is 34, last usable sector is 30535646
Number Start (sector) End (sector) Size Code Name
1 131072 303103 84.0M 0700 modem
2 393216 393217 1024 0700 fsc
3 393218 393233 8192 0700 ssd
4 393234 394257 512K 0700 sbl1
5 394258 395281 512K 0700 sbl1bak
6 395282 396305 512K 0700 rpm
7 396306 397329 512K 0700 rpmbak
8 397330 401425 2048K 0700 tz
9 401426 405521 2048K 0700 tzbak
10 405522 406033 256K 0700 devcfg
11 406034 406545 256K 0700 devcfgbak
12 406546 439313 16.0M 0700 dsp
13 439314 442385 1536K 0700 modemst1
14 442386 445457 1536K 0700 modemst2
15 524288 524351 32768 0700 DDR
16 524352 527423 1536K 0700 fsg
17 527424 527455 16384 0700 sec
18 655360 677887 11.0M 0700 splash
19 786432 788479 1024K 0700 aboot
20 788480 790527 1024K 0700 abootbak
21 790528 921599 64.0M 0700 boot
22 921600 1052671 64.0M 0700 recovery
23 1052672 1054719 1024K 0700 devinfo
24 1054720 7346175 3072M 0700 system
25 7471104 7995391 256M 0700 cache
26 7995392 8060927 32.0M 0700 persist
27 8060928 8062975 1024K 0700 misc
28 8062976 8063999 512K 0700 keystore
29 8064000 8064063 32768 0700 config
30 8064064 8588351 256M 0700 oem
31 8650752 8650815 32768 0700 limits
32 8781824 8782847 512K 0700 mota
33 8782848 8784895 1024K 0700 dip
34 8784896 8850431 32.0M 0700 mdtp
35 8850432 8851455 512K 0700 syscfg
36 8851456 8859647 4096K 0700 mcfg
37 8912896 8913151 128K 0700 lksecapp
38 8913152 8913407 128K 0700 lksecappbak
39 8913408 8913919 256K 0700 cmnlib
40 8913920 8914431 256K 0700 cmnlibbak
41 8914432 8914943 256K 0700 cmnlib64
42 8914944 8915455 256K 0700 cmnlib64bak
43 8915456 8915967 256K 0700 keymaster
44 8915968 8916479 256K 0700 keymasterbak
45 9043968 9044479 256K 0700 apdp
46 9044480 9044991 256K 0700 msadp
47 9044992 9045007 8192 0700 dpo
48 9045008 9176079 64.0M 0700 logdump
49 9176080 30535646 10.1G 0700 userdata
~ # mount
Code:
rootfs on / type rootfs (rw,seclabel,size=853376k,nr_inodes=134849)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=936796k,nr_inodes=138672,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime,size=936796k,nr_inodes=138672)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/mmcblk0p25 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk1p1 on /external_sd type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/block/mmcblk0p24 on /system type ext4 (rw,seclabel,relatime,data=ordered)
~ # ls -lh /dev/block/platform/soc/7824900.sdhci/ | sort -g
Code:
drwxr-xr-x 2 root root 1020 Feb 17 19:54 by-name
drwxr-xr-x 2 root root 1020 Feb 17 19:54 by-num
lrwxrwxrwx 1 root root 18 Feb 17 19:54 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx 1 root root 20 Feb 17 19:54 mmcblk0p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Feb 17 19:54 mmcblk0p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Feb 17 19:54 mmcblk0p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 Feb 17 19:54 mmcblk0p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Feb 17 19:54 mmcblk0p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Feb 17 19:54 mmcblk0p6 -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Feb 17 19:54 mmcblk0p7 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Feb 17 19:54 mmcblk0p8 -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Feb 17 19:54 mmcblk0p9 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p10 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p11 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p12 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p13 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p14 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p15 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p16 -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p17 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p18 -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p19 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p20 -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p21 -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p22 -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p23 -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p24 -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p25 -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p26 -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p27 -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p28 -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p29 -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p30 -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p31 -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p32 -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p33 -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p34 -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p35 -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p36 -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p37 -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p38 -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p39 -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p40 -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p41 -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p42 -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p43 -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p44 -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p45 -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p46 -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p47 -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p48 -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p49 -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 22 Feb 17 19:54 mmcblk0rpmb -> /dev/block/mmcblk0rpmb
~ # ls -lh /dev/block/platform/soc/7824900.sdhci/by-name | sort -f -k6
Code:
lrwxrwxrwx 1 root root 21 Feb 17 19:54 aboot -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Feb 17 19:54 abootbak -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Feb 17 19:54 apdp -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 Feb 17 19:54 boot -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Feb 17 19:54 cache -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Feb 17 19:54 cmnlib -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 Feb 17 19:54 cmnlib64 -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 Feb 17 19:54 cmnlib64bak -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 Feb 17 19:54 cmnlibbak -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 Feb 17 19:54 config -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 Feb 17 19:54 DDR -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Feb 17 19:54 devcfg -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Feb 17 19:54 devcfgbak -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Feb 17 19:54 devinfo -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 Feb 17 19:54 dip -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 Feb 17 19:54 dpo -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 Feb 17 19:54 dsp -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 Feb 17 19:54 fsc -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 Feb 17 19:54 fsg -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Feb 17 19:54 keymaster -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 Feb 17 19:54 keymasterbak -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 Feb 17 19:54 keystore -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 Feb 17 19:54 limits -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 Feb 17 19:54 lksecapp -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 Feb 17 19:54 lksecappbak -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 Feb 17 19:54 logdump -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mcfg -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mdtp -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 Feb 17 19:54 misc -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 20 Feb 17 19:54 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Feb 17 19:54 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Feb 17 19:54 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mota -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 Feb 17 19:54 msadp -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 Feb 17 19:54 oem -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 Feb 17 19:54 persist -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Feb 17 19:54 recovery -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 20 Feb 17 19:54 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Feb 17 19:54 rpmbak -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Feb 17 19:54 sbl1 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Feb 17 19:54 sbl1bak -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 Feb 17 19:54 sec -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Feb 17 19:54 splash -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 Feb 17 19:54 ssd -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Feb 17 19:54 syscfg -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 Feb 17 19:54 system -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 Feb 17 19:54 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Feb 17 19:54 tzbak -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Feb 17 19:54 userdata -> /dev/block/mmcblk0p49
~ # find / -iname "*fstab*"
Code:
/cache/recovery/recovery.fstab
/cache/recovery/storage.fstab
/system/etc/vold.fstab
/system/vendor/etc/fstab.qcom
find: /sys/kernel/slab/L2TP/IPv6: No such file or directory
find: /sys/kernel/slab/L2TP/IP: No such file or directory
/etc/fstab
/etc/twrp.fstab
Contents of ~ # find / -iname "*fstab*"
Code:
/cache/recovery/recovery.fstab
### EMPTY FILE ###
\\\
/cache/recovery/storage.fstab
/data/media;Internal Storage;
/external_sd;External SD;
/usb-otg;USB OTG;
\\\
/system/etc/vold.fstab
# Copyright (c) 2013, The Linux Foundation. All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are
# met:
# * Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# * Redistributions in binary form must reproduce the above
# copyright notice, this list of conditions and the following
# disclaimer in the documentation and/or other materials provided
# with the distribution.
# * Neither the name of The Linux Foundation nor the names of its
# contributors may be used to endorse or promote products derived
# from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT
# ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS
# BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
# BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
# OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
# IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
dev_mount sdcard /storage/sdcard1 auto /devices/msm_sdcc.2/mmc_host
# MTP
#dev_mount sdcard2 /mnt/sdcard/external_sd auto /devices/platform/msm_sdcc.3/mmc_host
\\\
/system/vendor/etc/fstab.qcom
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
#/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1,discard wait, verify
/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,noauto_da_alloc,discard wait,resize,forceencrypt=footer,quota
/devices/platform/soc/7864900.sdhci/mmc_host* /storage/sdcard1 vfat nosuid,nodev wait,voldmanaged=sdcard1:auto,noemulatedsd,encryptable=footer
/devices/soc/7864900.sdhci/mmc_host* /storage/sdcard1 vfat nosuid,nodev wait,voldmanaged=sdcard1:auto,noemulatedsd,encryptable=footer
/devices/platform/soc/78db000.usb/msm_hsusb_host* /storage/usbotg vfat nosuid,nodev wait,voldmanaged=usbotg:auto
/devices/soc/78db000.usb/msm_hsusb_host* /storage/usbotg vfat nosuid,nodev wait,voldmanaged=usbotg:auto
/dev/block/bootdevice/by-name/config /frp emmc defaults defaults
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
/dev/block/bootdevice/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1 wait
/dev/block/bootdevice/by-name/modem /firmware vfat ro,shortname=lower,uid=1000,gid=1000,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 wait
/dev/block/bootdevice/by-name/dsp /dsp ext4 ro,nosuid,nodev,barrier=1 wait
\\\
/etc/fstab
/dev/block/mmcblk0p25 /cache ext4 rw 0 0
/dev/block/mmcblk0p24 /system ext4 rw 0 0
/dev/block/dm-0 /data ext4 rw 0 0
/dev/block/mmcblk1p1 /external_sd vfat rw 0 0
/usb-otg vfat rw 0 0
\\\
/etc/twrp.fstab
/cache ext4 /dev/block/bootdevice/by-name/cache
/system ext4 /dev/block/bootdevice/by-name/system
/system_image emmc /dev/block/bootdevice/by-name/system
/data ext4 /dev/block/bootdevice/by-name/userdata flags=encryptable=footer;length=-16384
/boot emmc /dev/block/bootdevice/by-name/boot
/recovery emmc /dev/block/bootdevice/by-name/recovery
/misc emmc /dev/block/bootdevice/by-name/misc
/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="External SD";storage;wipeingui;removable
/usb-otg vfat /dev/block/sda1 /dev/block/sda flags=display="USB OTG";storage;wipeingui;removable
And now... Questions time!
Which fstab should I trust? Why there are so many different ones?
Why my smartphone has the by-name/ directory inside this path: /dev/block/platform/soc/7824900.sdhci/ ?
In case I would use ddto backup or restore or reflash partitions, can i use dd within ADB Shell while I'm into Recovery (TWRP)?
Will dd be capable of reflashing .bin and .img and .mbn partitions even if I am OEM locked-out from Fastboot?
Why I cannot mount /datawhile inside TWRP?
Code:
~ # mount -o noatime,nosuid,nodev,barrier=1,noauto_da_alloc,discard,wait,resize,forceencrypt=footer,quota /dev/block/bootdevice/by-name/userdata /data \\\ mount: mounting /dev/block/bootdevice/by-name/userdata on /data failed: Device or resource busy
Many thanks guys!!
1. vold fstab is for external storage managed by StorageManagerService in android mode.
vendor/etc fstab is fstab for emmc storage provided by vendor. other fstabs are generated by and only used by TWRP.
2. android partitions are always referenced by it's symlinks generated from kernel. for example on A/B devices the /dev/block/bootdevice/by-name/system is linked to either /dev/block/bootdevice/by-name/system_a or /dev/block/bootdevice/by-name/system_b depending on active slot. in android mode you will see /dev/block/dm-0 instead as the partition is protected by dm-verity.
3. we don't care about real block partition, you can just dd its symlink. (Note, it requires exFAT MicroSD Card, FAT32 has 4 GB file size limit.) it's even more comfortable to just adb pull partition btw.
4. /data is already mounted in TWRP (Device or resource busy) except for failed decrypts (check /tmp/recovery.log)
if /dev/block/bootdevice/by-name/userdata is decrypted successfully, a new (decrypted) block device /dev/block/dm-0 is created by dm-crypt and mounted to /data.
/proc/partitions is maintained in realtime by kernel.
aIecxs said:
4. /data is already mounted in TWRP (Device or resource busy) except for failed decrypts (check /tmp/recovery.log)
if /dev/block/bootdevice/by-name/userdata is decrypted successfully, a new (decrypted) block device /dev/block/dm-0 is created by dm-crypt and mounted to /data.
/proc/partitions is maintained in realtime by kernel.
Click to expand...
Click to collapse
Hey... I'm doing some testing... Here's the steps I've done so far:
wipe / reformat all partitions
entirely re-flash the whole Stock ROM
reboot
completed the Startup Wizard
set a PIN when requested (instead of a Password or a Pattern)
boot into Android
reboot
boot again into Android
reboot to Bootloader
Bash:
fastboot flash recovery twrp.img
reboot into Android
reboot into TWRP
[V] Never show this screen during boot again
Swipe to Allow Modifications
TWRP is NOT asking me the PIN to decrypt /data
/data is NOT mounted, but with different error now (see logs down below)
every time I boot into TWRP, it always keeps me asking Swipe to Allow Modifications!!!
recovery.log
Bash:
[...]
Data successfully decrypted, new block device: '/dev/block/dm-0'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
Updating partition details...
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
Unable to mount storage
/data | /dev/block/dm-0 | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Can_Be_Encrypted Is_Encrypted Is_Decrypted Has_Data_Media Can_Encrypt_Backup Use_Userdata_Encryption Is_Storage Is_Settings_Storage
Symlink_Path: /data/media
Symlink_Mount_Point: /sdcard
Primary_Block_Device: /dev/block/mmcblk0p49
Decrypted_Block_Device: /dev/block/dm-0
Crypto_Key_Location: footer
Length: -16384
Display_Name: data
Storage_Name: Internal Storage
Backup_Path: /data
Backup_Name: data
Backup_Display_Name: Data
Storage_Path: /data/media
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
MTP_Storage_ID: 65537
I:Unmounting main partitions...
Successfully decrypted with default password.
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
Updating partition details...
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
Unable to mount storage
I:Unmounting main partitions...
[...]
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
Failed to mount '/data' (No such process)
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount /data/media during GUI startup.
[...]
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Copying file /cache/recovery/log to /cache/recovery/last_log
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
Unable to mount /data/media/TWRP/.twrps
I:Attempt to load settings from settings file...
I:InfoManager file '/data/media/TWRP/.twrps' not found.
I:Backup folder set to '/data/media/TWRP/BACKUPS/WF012646'
I:Copying file /etc/recovery.fstab to /cache/recovery/recovery.fstab
I:Version number saved to '/cache/recovery/.version'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:TWFunc::Set_Brightness: Setting brightness control to 128
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/en.xml' directly
parsing languageFile
parsing languageFile done
I:Translating partition display names
[...]
Failed to mount '/data' (No such process)
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:TWFunc::Set_Brightness: Setting brightness control to 5
I:TWFunc::Set_Brightness: Setting brightness control to 0
~ # dmesg
Bash:
[...]
[ 5.628850] SELinux: initialized (dev mmcblk0p25, type ext4), uses xattr
[ 5.658433] EXT4-fs (mmcblk0p49): VFS: Can't find ext4 filesystem
[ 5.658777] EXT4-fs (mmcblk0p49): VFS: Can't find ext4 filesystem
[ 5.667880] EXT4-fs (mmcblk0p49): VFS: Can't find ext4 filesystem
[ 5.668184] EXT4-fs (mmcblk0p49): VFS: Can't find ext4 filesystem
[...]
[ 8.417484] device-mapper: req-crypt: req_crypt_ctr: Mapping block_device /dev/block/mmcblk0p49 to dm-req-crypt ok!
[...]
[ 14.258270] EXT4-fs (dm-0): warning: maximal mount count reached, running e2fsck is recommended
[ 14.259729] EXT4-fs warning (device dm-0): ext4_enable_quotas:5282: Failed to enable quota tracking (type=0, err=-3). Please run e2fsck to fix.
[ 14.259840] EXT4-fs (dm-0): mount failed
[ 14.261825] EXT4-fs (dm-0): warning: maximal mount count reached, running e2fsck is recommended
[ 14.263192] EXT4-fs warning (device dm-0): ext4_enable_quotas:5282: Failed to enable quota tracking (type=0, err=-3). Please run e2fsck to fix.
[ 14.263286] EXT4-fs (dm-0): mount failed
[...]
[ 56.822575] EXT4-fs (dm-0): warning: maximal mount count reached, running e2fsck is recommended
[ 56.824051] EXT4-fs warning (device dm-0): ext4_enable_quotas:5282: Failed to enable quota tracking (type=0, err=-3). Please run e2fsck to fix.
[ 56.824153] EXT4-fs (dm-0): mount failed
[ 56.826017] EXT4-fs (dm-0): warning: maximal mount count reached, running e2fsck is recommended
[ 56.827383] EXT4-fs warning (device dm-0): ext4_enable_quotas:5282: Failed to enable quota tracking (type=0, err=-3). Please run e2fsck to fix.
[ 56.827477] EXT4-fs (dm-0): mount failed
[...]
~ # e2fsck /dev/block/dm-0
Bash:
e2fsck 1.42.9 (28-Dec-2013)
/dev/block/dm-0 has unsupported feature(s): quota
e2fsck: Get a newer version of e2fsck!
No such process is known issue with disk quota. try to mount dm-0 read-only with ro,noexec,noload,noatime flags.
(Unrelated) for changing default_password try this app (may be outdated)
Cryptfs Password - Apps on Google Play
Easily set a complex disk encryption password different from the lockscreen one
play.google.com
aIecxs said:
try to mount dm-0 read-only with ro,noexec,noload,noatime flags.
Click to expand...
Click to collapse
Code:
~ # mount -o ro,noexec,noload,noatime /dev/block/dm-0
~ # mount | grep dm-0
/dev/block/dm-0 on /data type ext4 (ro,seclabel,noexec,noatime,norecovery)
And what if I completely disable /data encryption? Is it a viable option?
Are there some infos on how to disable Android encrypting /data? Can Stock ROMs be patched to disable encryption?
disable avb/dm-verity to allow modification on /system.
in vendor/etc fstab replace forceencrypt= flag with encryptable= and format userdata partition.
there exist flashable zip for this
no-verity-opt-encrypt.zip
(recommended for FDE)
Disable_Dm-Verity_ForceEncrypt.zip
(can also remove disk quota, read instructions)