Develop Bugs

Broken internal SD card

The partitioning of my internal SD card seems to be horribly broken, I haven't been able to find any solution that works.
When I run fdisk, and press p, this is what is shown:
Code:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 4097 32768 c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 4097 4225 1024 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 4225 4353 1024 51 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 4353 88064 669695+ 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 5121 5248 1024 47 Unknown
/dev/block/mmcblk0p6 6145 6784 5120 45 Unknown
/dev/block/mmcblk0p7 7169 7808 5120 4c Unknown
/dev/block/mmcblk0p8 8193 9472 10240 48 Unknown
/dev/block/mmcblk0p9 10241 10368 1024 46 Unknown
/dev/block/mmcblk0p10 11265 11648 3072 4a Unknown
/dev/block/mmcblk0p11 12289 12672 3072 4b Unknown
/dev/block/mmcblk0p12 13313 14336 8192 83 Linux
/dev/block/mmcblk0p13 14337 16384 16384 60 Unknown
/dev/block/mmcblk0p14 16385 20480 32768 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p15 20481 20864 3072 59 Unknown
/dev/block/mmcblk0p16 21505 21888 3072 5a Unknown
/dev/block/mmcblk0p17 22529 22912 3072 5b Unknown
/dev/block/mmcblk0p18 23553 23936 3072 58 Unknown
/dev/block/mmcblk0p19 24577 24704 1024 5d Unknown
/dev/block/mmcblk0p20 25601 26624 8192 83 Linux
/dev/block/mmcblk0p21 26625 28672 16384 83 Linux
/dev/block/mmcblk0p22 28673 37888 73728 83 Linux
/dev/block/mmcblk0p23 37889 38912 8192 83 Linux
/dev/block/mmcblk0p24 38913 41984 24576 76 Unknown
/dev/block/mmcblk0p25 41985 43008 8192 77 Unknown
/dev/block/mmcblk0p26 43009 43136 1024 78 Unknown
/dev/block/mmcblk0p27 44033 109568 524288 83 Linux
/dev/block/mmcblk0p28 109569 150528 327680 83 Linux
/dev/block/mmcblk0p29 150529 150912 3072 83 Linux
/dev/block/mmcblk0p30 151553 438272 2293760 83 Linux
/dev/block/mmcblk0p31 438273 440320 16384 83 Linux
/dev/block/mmcblk0p32 440321 440576 2048 83 Linux
when I try parted /dev/block/mmcblk10 and type print I get
Code:
Error: Unable to satisfy all constraints on the partition.
Any ideas, preferably a solution that doesn't cost money?

Wow.....if you were trying to format the 16 gb card that came with the phone first you need to Google SDFORMAT, it's a free download. Then pull the memory card it of your phone, put it in a micro sd to sd adapter, insert into a laptop and use the utility that you downloaded. However, those look like android partitions and under no circumstances are you to use Windows fdisk. Unless you want to brick your phone, hopefully you haven't already. If you have a custom recovery use the built in utility to handle the internal memory. Good luck.
Sent from my LG-D800 using XDA Free mobile app

[GENERAL][INFO] Mount Points for Xperia M

Hey guys,
Here is the mountpoint information for Xperia M I am still figuring out which of these goes for which partitions I will update if I find
Code:
PERM UID GID DATE PATH
lrwxrwxrwx root root 1970-07-11 15:19 FOTAKernel -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-07-11 15:19 LTALabel -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-07-11 15:19 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-07-11 15:19 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-07-11 15:19 alt -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-07-11 15:19 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-07-11 15:19 cache -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-07-11 15:19 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-07-11 15:19 modem -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-07-11 15:19 modemst1 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-07-11 15:19 modemst2 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-07-11 15:19 persist -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-07-11 15:19 ramdump -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-07-11 15:19 rpm -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-07-11 15:19 s1sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-07-11 15:19 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-07-11 15:19 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-07-11 15:19 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-07-11 15:19 system -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-07-11 15:19 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-07-11 15:19 userdata -> /dev/block/mmcblk0p27
Huge thanks to @mbc07
Code:
major minor #blocks name
179 0 3866624 mmcblk0
179 1 2048 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 256 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 128 mmcblk0p8
179 9 256 mmcblk0p9
179 10 256 mmcblk0p10
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 512 mmcblk0p13
179 14 512 mmcblk0p14
179 15 512 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 20480 mmcblk0p17
179 18 65536 mmcblk0p18
179 19 3072 mmcblk0p19
179 20 3072 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 5120 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 4096 mmcblk0p24
179 25 1228800 mmcblk0p25
179 26 256000 mmcblk0p26
179 27 2183151 mmcblk0p27
179 32 7822336 mmcblk1
179 33 7821312 mmcblk1p1

Just use ls -l /dev/block/platform/msm_sdcc.1/by-name
Layout:
Code:
PERM UID GID DATE PATH
lrwxrwxrwx root root 1970-07-11 15:19 FOTAKernel -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-07-11 15:19 LTALabel -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-07-11 15:19 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-07-11 15:19 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-07-11 15:19 alt -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-07-11 15:19 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-07-11 15:19 cache -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-07-11 15:19 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-07-11 15:19 modem -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-07-11 15:19 modemst1 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-07-11 15:19 modemst2 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-07-11 15:19 persist -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-07-11 15:19 ramdump -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-07-11 15:19 rpm -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-07-11 15:19 s1sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-07-11 15:19 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-07-11 15:19 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-07-11 15:19 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-07-11 15:19 system -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-07-11 15:19 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-07-11 15:19 userdata -> /dev/block/mmcblk0p27

Here you are a bit more information.
Also I have dumps of all these partitions and GPT backup.
If someone need to restore something – send PM (C1905 btw).
Code:
parted /dev/block/mmcblk0
print
Number Start End Size File system Name
1 131kB 2228kB 2097kB TA
2 2228kB 2359kB 131kB sbl1
3 2359kB 2621kB 262kB sbl2
4 2621kB 2884kB 262kB s1sbl2
5 2884kB 3408kB 524kB sbl3
6 3408kB 3932kB 524kB aboot
7 3932kB 4456kB 524kB tz
8 4456kB 4588kB 131kB alt_sbl1
9 4588kB 4850kB 262kB alt_sbl2
10 4850kB 5112kB 262kB alt_s1sbl2
11 5112kB 5636kB 524kB alt_sbl3
12 5636kB 6160kB 524kB alt_aboot
13 6160kB 6685kB 524kB alt_tz
14 6685kB 7209kB 524kB rpm
15 7209kB 7733kB 524kB alt_rpm
16 8389kB 25.2MB 16.8MB ext4 LTALabel
17 25.2MB 46.1MB 21.0MB boot
18 46.1MB 113MB 67.1MB fat16 modem
19 113MB 116MB 3146kB modemst1
20 117MB 121MB 3146kB modemst2
21 122MB 125MB 3146kB fsg
22 125MB 130MB 5243kB ramdump
23 130MB 147MB 16.8MB FOTAKernel
24 147MB 151MB 4194kB ext2 persist
25 151MB 1514MB 1363MB ext4 system
26 1514MB 1724MB 210MB ext4 cache
27 1724MB 3909MB 2185MB ext4 userdata
---------------
gdisk /dev/block/mmcblk0
p
Disk /dev/block/mmcblk0: 7733248 sectors, 3.7 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Partition table holds up to 27 entries
First usable sector is 34, last usable sector is 7733214
Partitions will be aligned on 256-sector boundaries
Total free space is 103902 sectors (50.7 MiB)
Number Start (sector) End (sector) Size Code Name
1 256 4351 2.0 MiB FFFF TA
2 4352 4607 128.0 KiB FFFF sbl1
3 4608 5119 256.0 KiB FFFF sbl2
4 5120 5631 256.0 KiB FFFF s1sbl2
5 5632 6655 512.0 KiB FFFF sbl3
6 6656 7679 512.0 KiB FFFF aboot
7 7680 8703 512.0 KiB FFFF tz
8 8704 8959 128.0 KiB FFFF alt_sbl1
9 8960 9471 256.0 KiB FFFF alt_sbl2
10 9472 9983 256.0 KiB FFFF alt_s1sbl2
11 9984 11007 512.0 KiB FFFF alt_sbl3
12 11008 12031 512.0 KiB FFFF alt_aboot
13 12032 13055 512.0 KiB FFFF alt_tz
14 13056 14079 512.0 KiB FFFF rpm
15 14080 15103 512.0 KiB FFFF alt_rpm
16 16384 49151 16.0 MiB 8300 LTALabel
17 49152 90111 20.0 MiB FFFF boot
18 90112 221183 64.0 MiB 0700 modem
19 221184 227327 3.0 MiB FFFF modemst1
20 229376 235519 3.0 MiB FFFF modemst2
21 237568 243711 3.0 MiB FFFF fsg
22 243712 253951 5.0 MiB FFFF ramdump
23 253952 286719 16.0 MiB FFFF FOTAKernel
24 286720 294911 4.0 MiB 8300 persist
25 294912 2957311 1.3 GiB 8300 system
26 2957312 3366911 200.0 MiB 8300 cache
27 3366912 7634910 2.0 GiB 8300 userdata
---------------
gdisk /dev/block/mmcblk0
x
o
Disk size is 7733248 sectors (3.7 GiB)
MBR disk identifier: 0x00000000
MBR partitions:
Number Boot Start Sector End Sector Status Code
1 1 7733247 primary 0xEE
---------------
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 3959 MB, 3959422976 bytes
95 heads, 61 sectors/track, 1334 cylinders
Units = cylinders of 5795 * 512 = 2967040 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1335 3866623+ ee EFI GPT
---------------
df
Filesystem Size Used Free Blksize
/dev 430.6M 128.0K 430.4M 4096
/sys/fs/cgroup 430.6M 12.0K 430.5M 4096
/mnt/asec 430.6M 0.0K 430.6M 4096
/mnt/obb 430.6M 0.0K 430.6M 4096
/mnt/fuse 430.6M 0.0K 430.6M 4096
/system 1.3G 374.4M 907.4M 4096
/data 2.0G 1.5G 555.2M 4096
/cache 197.0M 68.2M 128.8M 4096
/persist 3.9M 84.0K 3.8M 4096
/lta-label 15.8M 4.1M 11.7M 4096
/firmware 64.0M 44.1M 19.9M 16384
/mnt/shell/emulated 2.0G 1.5G 555.2M 4096
/storage/emulated/legacy 2.0G 1.5G 555.2M 4096
/mnt/media_rw/sdcard1 14.8G 11.6G 3.3G 8192
/storage/sdcard1 14.8G 11.6G 3.3G 8192
---------------
mount
rootfs / rootfs ro,seclabel,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
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 /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 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
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 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,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/LTALabel /lta-label ext4 ro,seclabel,nosuid,nodev,noexec,noatime,nobarrier,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/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/block/vold/179:33 /mnt/media_rw/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,cod
epage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

[Q] Resize system partitions?

hey i recently tried flashed teamaseks cm12 on my nexus 7 and also tried flashing the full gapps package (~450mb) and the Gapps failed to flash because of "insufficient space in system partition". Is there any way to allocate more disk space to system partition?

goboardindude said:
hey i recently tried flashed teamaseks cm12 on my nexus 7 and also tried flashing the full gapps package (~450mb) and the Gapps failed to flash because of "insufficient space in system partition". Is there any way to allocate more disk space to system partition?
Click to expand...
Click to collapse
Why would you flash some random persons CM12 when there is official CM12? Anyway..... Use a smaller gapps package.

khaytsus said:
Why would you flash some random persons CM12 when there is official CM12? Anyway..... Use a smaller gapps package.
Click to expand...
Click to collapse
Oh lol I just like teamaseks "spare parts" tweaks...
But there is no way to adjust partitions?
Sent from my Moto G 2014 using XDA Free mobile app

I second this question
I want to use the full GAPP package since it has everything I want and replaces stock apps I'd have to remove manually. Lots of saved time
On a 32GB tablet, not being able to install a full GAPP package because of a ~850MB system partition it nuts

Kev13Dd said:
I second this question
I want to use the full GAPP package since it has everything I want and replaces stock apps I'd have to remove manually. Lots of saved time
On a 32GB tablet, not being able to install a full GAPP package because of a ~850MB system partition it nuts
Click to expand...
Click to collapse
It's that small?? My moto g 2014 has only 8 GB and its system partition is around 1.2 GB so that's pretty crazy
Sent from my XT1063/64 using XDA Free mobile app

goboardindude said:
It's that small?? My moto g 2014 has only 8 GB and its system partition is around 1.2 GB so that's pretty crazy
Sent from my XT1063/64 using XDA Free mobile app
Click to expand...
Click to collapse
827MB to be exact
I had to modify the partitions on my Touchpad a lot of times, but I haven't seen a utility to do it on other devices...

Kev13Dd said:
827MB to be exact
I had to modify the partitions on my Touchpad a lot of times, but I haven't seen a utility to do it on other devices...
Click to expand...
Click to collapse
I can't believe there's nothing to change partition sizes... Something like Gparted for android
Unless the manufacturer makes physical partitions or separate disks altogether... That's probably a faster option
Sent from my XT1063/64 using XDA Free mobile app

It should be easy for the developers to let the user choose the size of the partition, it's just a logical partition, a number.
I've seen tutorials to change it after the installation but they are specific to the mobile model and Android version.

skanskan said:
It should be easy for the developers to let the user choose the size of the partition, it's just a logical partition, a number.
I've seen tutorials to change it after the installation but they are specific to the mobile model and Android version.
Click to expand...
Click to collapse
Your sure that the partitions are just logical and not physical? If I were an OEM I'd probably prefer separate physical pieces of memory for /system and user. Its faster and also probably more space efficient
Sent from my XT1063/64 using XDA Free mobile app

goboardindude said:
Your sure that the partitions are just logical and not physical? If I were an OEM I'd probably prefer separate physical pieces of memory for /system and user. Its faster and also probably more space efficient
Sent from my XT1063/64 using XDA Free mobile app
Click to expand...
Click to collapse
I've seen how to resize it on other older mobiles (with ported linux tools), that wouldn't be possible if they were physical. And it doesn't make sense to have many physical partitions.
And more important, it would depend on the brand but all new generation phones I've seen have the same /data partition size.
Anyway I'm not an expert.

Did anyone ever figure this out?
Sent from my SM-N920P using Tapatalk

colormedroid said:
Did anyone ever figure this out?
Click to expand...
Click to collapse
There is nothing mysterious about it, however as this device has no unbricking method I would advise against any repartitioning attempts.

As the Nexus 7 is no longer expected to have new software upgrades, I am working to expand my system partition and move towards CM.
I have done a DD backup of metadata, m9kefscs, DDR, ssd and misc partitions - since I have no idea what they are used for - I intended to recreate them after re-partitioning #22-30 to grant #22, the system partition at least 1.5GB of space.
Code:
Number Start (sector) End (sector) Size Code Name
1 131072 306143 85.4M 0700 radio
2 393216 399359 3072K 0700 modemst1
3 399360 405503 3072K 0700 modemst2
4 524288 554287 14.6M 0700 persist
5 655360 656919 780K 0700 m9kefs1
6 656920 658479 780K 0700 m9kefs2
7 786432 787991 780K 0700 m9kefs3
8 787992 794135 3072K 0700 fsg
9 917504 920503 1500K 0700 sbl1
10 920504 923503 1500K 0700 sbl2
11 923504 927599 2048K 0700 sbl3
12 927600 937839 5120K 0700 aboot
13 937840 938863 512K 0700 rpm
14 1048576 1081343 16.0M 0700 boot
15 1179648 1180671 512K 0700 tz
16 1180672 1180673 1024 0700 pad
17 1180674 1183673 1500K 0700 sbl2b
18 1183674 1187769 2048K 0700 sbl3b
19 1187770 1198009 5120K 0700 abootb
20 1198010 1199033 512K 0700 rpmb
21 1199034 1200057 512K 0700 tzb
22 1310720 3031039 840M 0700 system
23 3031040 4177919 560M 0700 cache
24 4194304 4196351 1024K 0700 misc
25 4325376 4345855 10.0M 0700 recovery
26 4456448 4456463 8192 0700 DDR
27 4456464 4456479 8192 0700 ssd
28 4456480 4456481 1024 0700 m9kefsc
29 4587520 4587583 32768 0700 metadata
30 4718592 61079518 26.8G 0700 userdata
I realized they have a lot of space in between each partition, as evidenced in the sector # above, double checked in parted.
Code:
Model: MMC HBG4e (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 67.1MB 157MB 89.6MB fat16 radio
2 201MB 204MB 3146kB modemst1
3 204MB 208MB 3146kB modemst2
4 268MB 284MB 15.4MB ext4 persist
5 336MB 336MB 799kB m9kefs1
6 336MB 337MB 799kB m9kefs2
7 403MB 403MB 799kB m9kefs3
8 403MB 407MB 3146kB fsg
9 470MB 471MB 1536kB sbl1
10 471MB 473MB 1536kB sbl2
11 473MB 475MB 2097kB sbl3
12 475MB 480MB 5243kB aboot
13 480MB 481MB 524kB rpm
14 537MB 554MB 16.8MB boot
15 604MB 605MB 524kB tz
16 605MB 605MB 1024B pad
17 605MB 606MB 1536kB sbl2b
18 606MB 608MB 2097kB sbl3b
19 608MB 613MB 5243kB abootb
20 613MB 614MB 524kB rpmb
21 614MB 614MB 524kB tzb
22 671MB 1552MB 881MB ext2 system
23 1552MB 2139MB 587MB cache
24 2147MB 2149MB 1049kB misc
25 2215MB 2225MB 10.5MB recovery
26 2282MB 2282MB 8192B DDR
27 2282MB 2282MB 8192B ssd
28 2282MB 2282MB 1024B m9kefsc
29 2349MB 2349MB 32.8kB metadata
30 2416MB 31.3GB 28.9GB userdata
Are there anyone with any idea why these free spaces might be there?

So I took the jump in the name of exploration, and bricked my tablet.
All because I was dreaming and recreated with the wrong partition type. I figure that's the root cause...
Sent from my ONE A2005 using Tapatalk

davewpy said:
So I took the jump in the name of exploration, and bricked my tablet
Click to expand...
Click to collapse
Didn't you read the warning?
Now please check the "Repair Options" section, specifically RIFF JTAG Box which can fix your problem easily.

k23m said:
Didn't you read the warning?
Now please check the "Repair Options" section, specifically RIFF JTAG Box which can fix your problem easily.
Click to expand...
Click to collapse
I have.
Thanks for the advise. I have gotten the chip to respond with some very old info from the community research but need to find some time to look at the low level codes - which i have no experience with.

davewpy said:
So I took the jump in the name of exploration, and bricked my tablet.
All because I was dreaming and recreated with the wrong partition type. I figure that's the root cause...
Click to expand...
Click to collapse
Your tablet can be unbricked now. Please read the guide.

It works. It was out of 9008 mode, then I had to leave it charging in power off mode for a night on my pc - otherwise it was impossible to manage fastboot in low battery state.
As the partition table is corrupted, I had to use fastboot boot <kernel using twrp> to boot to recovery and push parted command and work from there manually in a Linux shell.
I will post further updates in the guide thread.
Sent from my ONE A2005 using Tapatalk

[Q] Unbrick I747M problem

I have an SGH-I747m that I believe is on Bell that I bought used from Ebay. I was assured it was working but when I got it it wouldn't turn on. When I plug it in with the battery in a red light will flash for a second and when I pull the battery with the phone plugged in the red light will be steady even after I replace the battery but go out when I hold the power button. Also, if I pull and replace the battery with the phone unplugged the camera light will flash. Other than that it does nothing. I've tried various debrick images in hopes of getting my phone to download mode both using a 16 and 32 GB class 10 card but it does nothing. I'm not believing that the image is copying right from what I've seen from other people's debrick cards. I've used both dd on linux and win32disk imager on Windows 7. Also a note that when I plug the phone to the computer nothing shows up in device manager. Though that could be that this phone has never been used on my computer so no drivers installed for it.
Using sudo parted /dev/sdd print in Lubuntu 15.04 this is what my debrick SD looks like using a 32GB card.
Code:
Model: Generic- SD/MMC (scsi)
Disk /dev/sdd: 32.0GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 4194kB 67.1MB 62.9MB modem msftdata
2 67.1MB 67.2MB 131kB sbl1
3 67.2MB 67.5MB 262kB sbl2
4 67.5MB 68.0MB 524kB sbl3
5 68.0MB 70.1MB 2097kB aboot
6 70.1MB 70.6MB 524kB rpm
7 70.6MB 81.1MB 10.5MB boot
8 81.1MB 81.7MB 524kB tz
9 81.7MB 82.2MB 524kB pad
10 82.2MB 92.7MB 10.5MB param
11 92.7MB 107MB 14.3MB efs
12 107MB 110MB 3146kB modemst1
13 110MB 113MB 3146kB modemst2
14 113MB 1686MB 1573MB system
15 1686MB 14.8GB 13.1GB userdata
16 14.8GB 14.8GB 8389kB persist
17 14.8GB 15.7GB 881MB cache
18 15.7GB 15.7GB 10.5MB recovery
19 15.7GB 15.7GB 10.5MB fota
20 15.7GB 15.7GB 6291kB backup
21 15.7GB 15.7GB 3146kB fsg
22 15.7GB 15.7GB 8192B ssd
23 15.7GB 15.8GB 5243kB grow
I can't post images so I can't show what it looks like in Windows, but all the partitions are marked unknown save the first one that is FAT16 and contains a folder named image that has a number of files including various dsps, modem and other names. Can anyone help me figure this out to hopefully make a debrick card that works?

[Q] d855 unbricking help :)

OK, I am no noob at rooting, but have drawn a blank with this one. Would very much appreciate some advice.
I have 2 x LG G3 D855s, both running Cloudy G3 ROM. Both have been successfully downgraded to Android 4.4.2 (10L), rooted with purple drake, and Cloudy Lollipop installed. Perfect.
BUT whilst doing a Titanium restore on an app, one of them rebooted this evening, and is now bricked.
- Normal boot - never does anything other than initial LG boot logo;
- TWRP takes about 5 minutes on the splash screen before reaching the main TWRP screen (but has errors, see later);
- LG download mode only shows the initial logo on the phone but the PC does not 'see' it upon cable connection, and the phone never kicks into full download mode. Connecting my other d855 fires up download mode correctly, so PC drivers are OK.
Because download mode never fully starts, I am unable to restore to stock using the kdz / LG flash.
When TWRP DOES start, it is unable to mount /data, /cache, and the log has the following errors:
E: Could not mount /data and unable to find crypto folder
E: Unable to mount /data
E: Unable to recreate /data/media folder
E: Unable to mount /cache
E: Unable to mount storage
... etc.
Within TWRP Internal Storage is shown as (0MB), and /data and /cache are not mounted. My external_sd is mounted OK.
With TWRP running, a device is seen by my PC (Google Nexus ADB Interface) but 'adb devices' shows nothing. This is the same behaviour as the phone that works, so I assume that at least is normal.
I am unable to mount /data manually, or repair within TWRP.
With /data not mounted, I am unable to proceed any further...
So my question - how do I rebuild the screwed up partitions? Or am I barking up the wrong tree?

Some more troubleshooting.
Trying to mount manually in terminal in TWRP gives me a mount unknown error 150.
Running a non-invasive e2fsck gives me:
Code:
e2fsck 1.41.14 (22-Dec-2010)
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Inode 7, i_size is 3082895360, should be 3087097856. Fix? no
Inode 245415, i_blocks is 704, should be 712. Fix? no
Deleted inode 261925 has zero dtime. Fix? no
Pass 2: Checking directory structure
Entry 'net.dinglisch.android.taskerm' in /data (244801) references inode 342934 found in group 42's unused inodes area.
Fix? no
Entry 'net.dinglisch.android.taskerm' in /data (244801) has deleted/unused inode 342934. Clear? no
Entry 'base.apk' in /app/net.dinglisch.android.taskerm-1 (342899) references inode 342932 found in group 42's unused inodes area.
Fix? no
Entry 'base.apk' in /app/net.dinglisch.android.taskerm-1 (342899) has deleted/unused inode 342932. Clear? no
Entry 'lib' in /app/net.dinglisch.android.taskerm-1 (342899) references inode 342933 found in group 42's unused inodes area.
Fix? no
Entry 'lib' in /app/net.dinglisch.android.taskerm-1 (342899) has deleted/unused inode 342933. Clear? no
Entry 'net.dinglisch.android.taskerm' in /dalvik-cache/profiles (1020002) references inode 1020523 found in group 125's unused inodes area.
Fix? no
Entry 'net.dinglisch.android.taskerm' in /dalvik-cache/profiles (1020002) has deleted/unused inode 1020523. Clear? no
Entry '[email protected]@[email protected]@classes.dex' in /dalvik-cache/arm (1020003) references inode 1020522 found in group 125's unused inodes area.
Fix? no
Entry '[email protected]@[email protected]@classes.dex' in /dalvik-cache/arm (1020003) has deleted/unused inode 1020522. Clear? no
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Inode 244801 ref count is 227, should be 226. Fix? no
Inode 342899 ref count is 3, should be 2. Fix? no
Pass 5: Checking group summary information
Block bitmap differences: -(1389467--1390267) -3348514
Fix? no
Free blocks count wrong for group #25 (293, counted=292).
Fix? no
Free blocks count wrong for group #37 (4806, counted=4853).
Fix? no
Free blocks count wrong for group #42 (20629, counted=19028).
Fix? no
Free blocks count wrong (5806109, counted=5471235).
Fix? no
Inode bitmap differences: -261925 -(342932--342935) -(1020522--1020523)
Fix? no
Free inodes count wrong for group #32 (7338, counted=7337).
Fix? no
Free inodes count wrong for group #42 (7950, counted=7945).
Fix? no
Directories count wrong for group #42 (57, counted=58).
Fix? no
Free inodes count wrong for group #125 (7639, counted=7637).
Fix? no
Free inodes count wrong (1692439, counted=1689847).
Fix? no
/dev/block/mmcblk0p43: ********** WARNING: Filesystem still has errors **********
/dev/block/mmcblk0p43: 4841/1697280 files (8.7% non-contiguous), 988001/6794110 blocks
Parted gives me this:
Code:
Model: MMC SDW32G (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 85.5MB 86.0MB 524kB DDR
5 86.0MB 88.1MB 2097kB aboot
6 88.1MB 89.1MB 1049kB rpm
7 89.1MB 90.2MB 1049kB tz
8 90.2MB 90.2MB 4096B pad
9 90.2MB 91.2MB 1049kB sbl1b
10 91.2MB 91.8MB 524kB dbibak
11 91.8MB 92.8MB 1049kB rpmbak
12 92.8MB 93.9MB 1049kB tzbak
13 93.9MB 94.9MB 1049kB rpmf
14 94.9MB 95.9MB 1049kB tzf
15 95.9MB 96.5MB 524kB sdif
16 96.5MB 98.6MB 2097kB abootf
17 98.6MB 101MB 2093kB spare1
18 101MB 117MB 16.8MB boot
19 117MB 151MB 33.6MB ext4 persist
20 151MB 168MB 16.8MB recovery
21 168MB 171MB 3146kB modemst1
22 171MB 174MB 3146kB modemst2
23 174MB 174MB 4096B pad1
24 174MB 177MB 3146kB fsg
25 177MB 178MB 524kB fsc
26 178MB 178MB 524kB ssd
27 178MB 178MB 4096B pad2
28 178MB 179MB 524kB encrypt
29 179MB 179MB 524kB eksst
30 179MB 179MB 8192B rct
31 179MB 185MB 5226kB spare2
32 185MB 201MB 16.8MB misc
33 201MB 235MB 33.6MB laf
34 235MB 268MB 33.6MB fota
35 268MB 285MB 16.8MB spare3
36 285MB 294MB 8389kB ext4 drm
37 294MB 302MB 8389kB ext4 sns
38 302MB 336MB 33.6MB ext4 mpt
39 336MB 369MB 33.6MB factory
40 369MB 2533MB 2164MB ext4 system
41 2533MB 3171MB 638MB ext4 cache
42 3171MB 3439MB 268MB ext4 cust
43 3439MB 31.3GB 27.8GB ext4 userdata
44 31.3GB 31.3GB 513kB grow

Whenever I try and write, repair, or delete the partitions parted tells me:
Code:
Error: Input/output error during write on /dev/block/mmcblk0
I can read partitions. I have backed up EFS and /boot. For what it's worth
I can't delete partitions:
Code:
/ # dd if=/dev/zero of=/dev/block/mmcblk0 bs=512 count=1
1+0 records in
1+0 records out
512 bytes (512B) copied, 0.247840 seconds, 2.0KB/s
/ # parted /dev/block/mmcblk0 print
Model: MMC SDW32G (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 85.5MB 86.0MB 524kB DDR
5 86.0MB 88.1MB 2097kB aboot
6 88.1MB 89.1MB 1049kB rpm
7 89.1MB 90.2MB 1049kB tz
8 90.2MB 90.2MB 4096B pad
...
etc...
So it looks like the whole filesystem has gone read only??? Any way to force reset it? I'd have thought dd would have worked.