Database Users

[Q] borked internal sd card on Atrix

Hi all,
I posted this in the Atrix Q&A but it doesn't seem to have had many hits, thought I'd try my luck here (here is the original thread: http://forum.xda-developers.com/showthread.php?t=1594675) ...basically my Atrix emmc internal memory card is borked and I am trying to find a way to restore it other than SBFing to factory (which is risky and a hassle...).
rickywyatt kindly told me to execute these commands in an adb shell and to post the results:
adb shell
# cat /proc/partitions
# fdisk /dev/block/mmcblk0
p
q
well my results are as follows:
1|[email protected]:/ $ su
su
[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
7 0 2048 loop0
253 0 98304 zram0
179 0 15541760 mmcblk0
179 1 3584 mmcblk0p1
179 2 512 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 327680 mmcblk0p12
179 13 786432 mmcblk0p13
179 14 20480 mmcblk0p14
179 15 655360 mmcblk0p15
179 16 2097152 mmcblk0p16
179 17 353280 mmcblk0p17
179 18 11233792 mmcblk0p18
179 32 7772160 mmcblk1
179 33 7771136 mmcblk1p1
[email protected]:/ # fdisk /dev/block/mmcblk0
fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 1942720.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): ←[6np
p
Disk /dev/block/mmcblk0: 15.9 GB, 15914762240 bytes
1 heads, 16 sectors/track, 1942720 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 65 512 3584 83 Linux
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 513 576 512 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 577 832 2048 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 833 1937856 15496192 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 897 1024 1024 83 Linux
/dev/block/mmcblk0p6 1025 1088 512 83 Linux
/dev/block/mmcblk0p7 1089 1152 512 83 Linux
/dev/block/mmcblk0p8 1153 1280 1024 83 Linux
/dev/block/mmcblk0p9 1281 1536 2048 83 Linux
/dev/block/mmcblk0p10 1537 2560 8192 83 Linux
/dev/block/mmcblk0p11 2561 3584 8192 83 Linux
/dev/block/mmcblk0p12 3585 44544 327680 83 Linux
/dev/block/mmcblk0p13 44545 142848 786432 83 Linux
/dev/block/mmcblk0p14 142849 145408 20480 83 Linux
/dev/block/mmcblk0p15 145409 227328 655360 83 Linux
/dev/block/mmcblk0p16 227329 489472 2097152 83 Linux
/dev/block/mmcblk0p17 489473 533632 353280 83 Linux
/dev/block/mmcblk0p18 533633 1937856 11233792 83 Linux
Command (m for help): ←[6nq
q
[email protected]:/ #​
anyone know what I need to do next? If anyone can interpret the output for me I'd be so grateful.
Thanks,
Mark

I'd say flashing an sbf is alot easier then that haha.
Sent from my MB860 using XDA

If i where you i'd try to leave it as if was new and take it to motorola service, they change it to a new one. If you did unlocked the bootload (i guess you did) i think that there was a way to hidde the unlocked at boot.
GL with that!

[Q] [L5] [E612F] Can KDZ update change (apparent) internal SD size?

Hello!
TL/DR version: I updated a L5 (E612F - Vivo BR) with a V20 KDZ file and the internal storage, that was 8GB is seen by fdisk as ~3GB. There seems to be something wrong with the partition table. Is it possible to revert it back to the original value?
Detailed version:
My girlfriend bought a L5 (E612F - Vivo BR) and urged me to remove all the LG crap that came with the phone.
E612f is known for not being easily rootable and so on, so it was a struggle to put CM10.x in it. After many attempts and a few boot loops, I managed to use an E610 KDZ + E610 recovery and other images from this thread: http://forum.xda-developers.com/showthread.php?t=2186161
The problem is that fdisk reports that the internal SD has only ~3GB of size, but the device ghas 8GB internal SD. Because of that, she gets low space errors all the time:
Code:
1|[email protected]:/ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 3909 MB, 3909091328 bytes
1 heads, 16 sectors/track, 477184 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 3 20 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 3 128 1003+ 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 256 1024 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 257 465152 3719168 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 8193 8704 4096 47 Unknown
/dev/block/mmcblk0p6 8705 9216 4096 2c Unknown
/dev/block/mmcblk0p7 9217 9728 4096 58 Unknown
/dev/block/mmcblk0p8 9729 12800 24576 77 Unknown
/dev/block/mmcblk0p9 12801 13824 8192 48 Unknown
/dev/block/mmcblk0p10 13825 14336 4096 4a Unknown
/dev/block/mmcblk0p11 14337 14848 4096 4b Unknown
/dev/block/mmcblk0p12 14849 18432 28672 49 Unknown
/dev/block/mmcblk0p13 18433 22016 28672 6c Unknown
/dev/block/mmcblk0p14 22017 100096 624640 83 Linux
/dev/block/mmcblk0p15 100353 101376 8192 83 Linux
/dev/block/mmcblk0p16 101377 114176 102400 83 Linux
/dev/block/mmcblk0p17 114177 115200 8192 60 Unknown
/dev/block/mmcblk0p18 115201 116224 8192 83 Linux
/dev/block/mmcblk0p19 116225 117760 12288 6b Unknown
/dev/block/mmcblk0p20 117761 470656 2823168 83 Linux
/dev/block/mmcblk0p21 471041 471552 4096 ff Unknown
/dev/block/mmcblk0p22 471553 471680 1024 ff Unknown
/dev/block/mmcblk0p23 472065 474112 16384 83 Linux
Could the KDZ from another version (E610) be the culprit for this? Any idea how to deal with it? Thanks!

Working on unbricking hard bricked Moto E

UPDATE:
Working on QPST tools now:
* Need to find prog_emmc_firehose_8x10.mbn
The goal of this project is to gather all the information and tools required in unbricking a hard bricked Moto E (1st Generation).
Possible methods:
1. Blankflash
Requires: singleimage_8x10.mbn, qboot utility for Moto E, programmer_8x10.mbn
2. MiFlash
Requires: fastboot script, fastboot or mfastboot, MPRG8x10.hex, 8x10_msimage.mbn, rawprogram0.xml, patch0.xml
3. QPST
Requires: QPST tool, rawprogram0.xml, patch0.xml, prog_emmc_firehose_8x10.mbn, flat build/single image, multi build/sparse images.
Click to expand...
Click to collapse
XDA:DevDB Information
Unbrick Moto E, Tool/Utility for the Moto E
Contributors
206bone
Version Information
Status: Testing
Created 2016-02-02
Last Updated 2016-02-05

Reserved
Creating partition.xml file:
1. Post from senior member darkspr1te:
http://forum.xda-developers.com/showpost.php?p=36019312&postcount=13
2. Another post from a blog.

Reserved
For reference:
eMMC Partition tool (QPST tools)
Qcom Partition Type Cross Reference (To find Partition IDs for creating partition.xml)
Moto G blank flash tutorial
Creating PIT
Moto E PITs
Moto G PIT
R&D on using Qualcomm
Unbrick Qualcomm Snapdragon devices
Decompiler
GPT Parser
PartitioningTool.py
Moto E source code distros
Sparse Converter
R&D Building Qualcomm Bootloaders
GUID Partition Table (GPT)
Master Boot Record (MBR)
EFI System Partition
Unified Extensible Firmware Interface (UEFI)
UEFI Programming
Test Boot loader
X86_Assembly/Bootloaders

Tell me how I can help and i'll try my best dude

iTudorS said:
Tell me how I can help and i'll try my best dude
Click to expand...
Click to collapse
Thank you so much bro... Could you please provide me the full partition information table? More the information, more better..
Here's the link on how to do it: Partition table
I've just dissected a 8x10_msimage.mbn file. And I found 4 partitions:
1. SBL1
2. DDR (No info on DDR.)
3. RPM
4. TZ
I don't know what this DDR file is. I'd like to see the size of this file(in Kb) on the partition table.

206bone said:
Thank you so much bro... Could you please provide me the full partition information table? More the information, more better..
Here's the link on how to do it: Partition table
I've just dissected a 8x10_msimage.mbn file. And I found 4 partitions:
1. SBL1
2. DDR (No info on DDR.)
3. RPM
4. TZ
I don't know what this DDR file is. I'd like to see the size of this file(in Kb) on the partition table.
Click to expand...
Click to collapse
Hi, I love to help and more in electronics field. Here's my contribution for MotoE XT1022 Condor Device.
Code:
major minor #blocks name
7 0 85648 loop0
7 1 22980 loop1
7 2 32380 loop2
7 3 91916 loop3
7 4 27160 loop4
7 5 4180 loop5
7 6 15668 loop6
7 7 3136 loop7
253 0 524288 zram0
179 0 3866624 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 32 mmcblk0p3
179 4 512 mmcblk0p4
179 5 200 mmcblk0p5
179 6 400 mmcblk0p6
179 7 32 mmcblk0p7
179 8 512 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 2332 mmcblk0p10
179 11 512 mmcblk0p11
179 12 200 mmcblk0p12
179 13 400 mmcblk0p13
179 14 32 mmcblk0p14
179 15 512 mmcblk0p15
179 16 1052 mmcblk0p16
179 17 1536 mmcblk0p17
179 18 1536 mmcblk0p18
179 19 488 mmcblk0p19
179 20 32 mmcblk0p20
179 21 1536 mmcblk0p21
179 22 1 mmcblk0p22
179 23 8 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 128 mmcblk0p25
179 26 3072 mmcblk0p26
179 27 4096 mmcblk0p27
179 28 4096 mmcblk0p28
179 29 8192 mmcblk0p29
179 30 512 mmcblk0p30
179 31 10200 mmcblk0p31
259 0 10280 mmcblk0p32
259 1 465024 mmcblk0p33
259 2 917504 mmcblk0p34
259 3 8192 mmcblk0p35
259 4 2350464 mmcblk0p36
179 32 512 mmcblk0rpmb
179 64 30466048 mmcblk1
179 65 30465024 mmcblk1p1
254 0 85648 dm-0
254 1 22980 dm-1
254 2 32380 dm-2
254 3 91916 dm-3
254 4 27160 dm-4
254 5 4180 dm-5
254 6 15668 dm-6
254 7 3136 dm-7
7 8 20892 loop8
254 8 20892 dm-8
7 9 61628 loop9
254 9 61628 dm-9
7 10 19848 loop10
254 10 19848 dm-10
7 11 36560 loop11
254 11 36560 dm-11
7 12 35516 loop12
254 12 35516 dm-12
7 13 7312 loop13
254 13 7312 dm-13
Here is the detailed partition info obtained from msm_sdcc.1:
Code:
DDR -> /dev/block/mmcblk0p3
aboot -> /dev/block/mmcblk0p4
abootBackup -> /dev/block/mmcblk0p11
boot -> /dev/block/mmcblk0p31
cache -> /dev/block/mmcblk0p33
cid -> /dev/block/mmcblk0p25
clogo -> /dev/block/mmcblk0p28
dhob -> /dev/block/mmcblk0p20
fsc -> /dev/block/mmcblk0p22
fsg -> /dev/block/mmcblk0p21
hob -> /dev/block/mmcblk0p19
kpan -> /dev/block/mmcblk0p35
logo -> /dev/block/mmcblk0p27
logs -> /dev/block/mmcblk0p9
misc -> /dev/block/mmcblk0p30
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p17
modemst2 -> /dev/block/mmcblk0p18
padA -> /dev/block/mmcblk0p10
padB -> /dev/block/mmcblk0p16
pds -> /dev/block/mmcblk0p26
persist -> /dev/block/mmcblk0p29
recovery -> /dev/block/mmcblk0p32
rpm -> /dev/block/mmcblk0p5
rpmBackup -> /dev/block/mmcblk0p12
sbl1 -> /dev/block/mmcblk0p2
sdi -> /dev/block/mmcblk0p7
sdiBackup -> /dev/block/mmcblk0p14
sp -> /dev/block/mmcblk0p24
ssd -> /dev/block/mmcblk0p23
system -> /dev/block/mmcblk0p34
tz -> /dev/block/mmcblk0p6
tzBackup -> /dev/block/mmcblk0p13
userdata -> /dev/block/mmcblk0p36
utags -> /dev/block/mmcblk0p8
utagsBackup -> /dev/block/mmcblk0p15
Here is the detailed partition info obtained from msm_sdcc.2:
Code:
mmcblk1 -> /dev/block/mmcblk1
mmcblk1p1 -> /dev/block/mmcblk1p1
DDR partition contain DDR.bin. This image addresses the Physical RAM Memory in the device... common on Elpida Ram Powered Devices. Correct me if I'm wrong please.
Tell me anything that you need.

try this files

206bone said:
Can you please help me out with finding the IDs of each partition in mmcblk0 in the boot record?...
Click to expand...
Click to collapse
Hi friend, as requested:
IDs from mmcblk0:
Code:
Disk /dev/block/mmcblk0: 7733248 sectors, 3776M
Logical sector size: 512
Partition table holds up to 36 entries
First usable sector is 34, last usable sector is 7733214
Number Start (sector) End (sector) Size Code Name
1 256 131327 64.0M 0700 modem
2 131328 132351 512K 0700 sbl1
3 132352 132415 32768 0700 DDR
4 132608 133631 512K 0700 aboot
5 135608 136007 200K 0700 rpm
6 136608 137407 400K 0700 tz
7 137608 137671 32768 0700 sdi
8 137672 138695 512K 0700 utags
9 138696 142791 2048K 0700 logs
10 142792 147455 2332K 0700 padA
11 147456 148479 512K 0700 abootBackup
12 150456 150855 200K 0700 rpmBackup
13 151456 152255 400K 0700 tzBackup
14 152456 152519 32768 0700 sdiBackup
15 152520 153543 512K 0700 utagsBackup
16 153544 155647 1052K 0700 padB
17 155648 158719 1536K 0700 modemst1
18 158720 161791 1536K 0700 modemst2
19 161792 162767 488K 0700 hob
20 162768 162831 32768 0700 dhob
21 163072 166143 1536K 0700 fsg
22 166144 166145 1024 0700 fsc
23 166146 166161 8192 0700 ssd
24 166162 168209 1024K 0700 sp
25 168210 168465 128K 0700 cid
26 168466 174609 3072K 0700 pds
27 174610 182801 4096K 0700 logo
28 182802 190993 4096K 0700 clogo
29 191232 207615 8192K 0700 persist
30 207616 208639 512K 0700 misc
31 208640 229039 9.9M 0700 boot
32 229040 249599 10.0M 0700 recovery
33 249600 1179647 454M 0700 cache
34 1179648 3014655 896M 0700 system
35 3014656 3031039 8192K 0700 kpan
36 3031040 7731967 2295M 0700 userdata
Info from mmcblk0p1:
Code:
Disk /dev/block/mmcblk0p1: 67 MB, 67108864 bytes
4 heads, 16 sectors/track, 2048 cylinders, total 131072 sectors
Info from mmcblk0p2:
Code:
Disk /dev/block/mmcblk0p2: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders, total 1024 sectors
Info from mmcblk0p3:
Code:
Disk /dev/block/mmcblk0p3: 0 MB, 32768 bytes
4 heads, 16 sectors/track, 1 cylinders, total 64 sectors
Info from mmcblk0p4:
Code:
Disk /dev/block/mmcblk0p4: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders, total 1024 sectors
Info from mmcblk0p5:
Code:
Disk /dev/block/mmcblk0p5: 0 MB, 204800 bytes
4 heads, 16 sectors/track, 6 cylinders, total 400 sectors
Info from mmcblk0p6:
Code:
Disk /dev/block/mmcblk0p6: 0 MB, 409600 bytes
4 heads, 16 sectors/track, 12 cylinders, total 800 sectors
Info from mmcblk0p7:
Code:
Disk /dev/block/mmcblk0p7: 0 MB, 32768 bytes
4 heads, 16 sectors/track, 1 cylinders, total 64 sectors
Info from mmcblk0p8:
Code:
Disk /dev/block/mmcblk0p8: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders, total 1024 sectors
Info from mmcblk0p9:
Code:
Disk /dev/block/mmcblk0p9: 2 MB, 2097152 bytes
4 heads, 16 sectors/track, 64 cylinders, total 4096 sectors
Info from mmcblk0p10:
Code:
Disk /dev/block/mmcblk0p10: 2 MB, 2387968 bytes
4 heads, 16 sectors/track, 72 cylinders, total 4664 sectors
Info from mmcblk0p11:
Code:
Disk /dev/block/mmcblk0p11: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders, total 1024 sectors
Info from mmcblk0p12:
Code:
Disk /dev/block/mmcblk0p12: 0 MB, 204800 bytes
4 heads, 16 sectors/track, 6 cylinders, total 400 sectors
Info from mmcblk0p13:
Code:
Disk /dev/block/mmcblk0p13: 0 MB, 409600 bytes
4 heads, 16 sectors/track, 12 cylinders, total 800 sectors
Info from mmcblk0p14:
Code:
Disk /dev/block/mmcblk0p14: 0 MB, 32768 bytes
4 heads, 16 sectors/track, 1 cylinders, total 64 sectors
Info from mmcblk0p15:
Code:
Disk /dev/block/mmcblk0p15: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders, total 1024 sectors
Info from mmcblk0p16:
Code:
Disk /dev/block/mmcblk0p16: 1 MB, 1077248 bytes
4 heads, 16 sectors/track, 32 cylinders, total 2104 sectors
Info from mmcblk0p17:
Code:
Disk /dev/block/mmcblk0p17: 1 MB, 1572864 bytes
4 heads, 16 sectors/track, 48 cylinders, total 3072 sectors
Info from mmcblk0p18:
Code:
Disk /dev/block/mmcblk0p18: 1 MB, 1572864 bytes
4 heads, 16 sectors/track, 48 cylinders, total 3072 sectors
Info from mmcblk0p19:
Code:
Disk /dev/block/mmcblk0p19: 0 MB, 499712 bytes
4 heads, 16 sectors/track, 15 cylinders, total 976 sectors
Info from mmcblk0p20:
Code:
Disk /dev/block/mmcblk0p20: 0 MB, 32768 bytes
4 heads, 16 sectors/track, 1 cylinders, total 64 sectors
Info from mmcblk0p21:
Code:
Disk /dev/block/mmcblk0p21: 1 MB, 1572864 bytes
4 heads, 16 sectors/track, 48 cylinders, total 3072 sectors
Info from mmcblk0p22:
Code:
Disk /dev/block/mmcblk0p22: 0 MB, 1024 bytes
4 heads, 16 sectors/track, 0 cylinders, total 2 sectors
Info from mmcblk0p23:
Code:
Disk /dev/block/mmcblk0p23: 0 MB, 8192 bytes
4 heads, 16 sectors/track, 0 cylinders, total 16 sectors
Info from mmcblk0p24:
Code:
Disk /dev/block/mmcblk0p24: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders, total 2048 sectors
Info from mmcblk0p25:
Code:
Disk /dev/block/mmcblk0p25: 0 MB, 131072 bytes
4 heads, 16 sectors/track, 4 cylinders, total 256 sectors
Info from mmcblk0p26:
Code:
Disk /dev/block/mmcblk0p26: 3 MB, 3145728 bytes
4 heads, 16 sectors/track, 96 cylinders, total 6144 sectors
Info from mmcblk0p27:
Code:
Disk /dev/block/mmcblk0p27: 4 MB, 4194304 bytes
4 heads, 16 sectors/track, 128 cylinders, total 8192 sectors
Info from mmcblk0p28:
Code:
Disk /dev/block/mmcblk0p28: 4 MB, 4194304 bytes
4 heads, 16 sectors/track, 128 cylinders, total 8192 sectors
Info from mmcblk0p29:
Code:
Disk /dev/block/mmcblk0p29: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders, total 16384 sectors
Info from mmcblk0p30:
Code:
Disk /dev/block/mmcblk0p30: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders, total 1024 sectors
Info from mmcblk0p31:
Code:
Disk /dev/block/mmcblk0p31: 10 MB, 10444800 bytes
4 heads, 16 sectors/track, 318 cylinders, total 20400 sectors
Info from mmcblk0p32:
Code:
Disk /dev/block/mmcblk0p32: 10 MB, 10526720 bytes
4 heads, 16 sectors/track, 321 cylinders, total 20560 sectors
Info from mmcblk0p33:
Code:
Disk /dev/block/mmcblk0p33: 476 MB, 476184576 bytes
4 heads, 16 sectors/track, 14532 cylinders, total 930048 sectors
Info from mmcblk0p34:
Code:
Disk /dev/block/mmcblk0p34: 939 MB, 939524096 bytes
4 heads, 16 sectors/track, 28672 cylinders, total 1835008 sectors
Info from mmcblk0p35:
Code:
Disk /dev/block/mmcblk0p35: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders, total 16384 sectors
Info from mmcblk0p36:
Code:
Disk /dev/block/mmcblk0p36: 2406 MB, 2406875136 bytes
4 heads, 16 sectors/track, 73452 cylinders, total 4700928 sectors
Hope it helps!

Thanks dude...

Ready To Help
Hey Friend I dont know how to make this files But I hav trust on You so Please If you Make this File I have a hard Bricked Moto E and I an Ready to Test jst Give Me File And Instructions What to Do ... Thank You

206bone said:
Thanks dude...
Click to expand...
Click to collapse
You're welcome. :good:

Maybe its helpfull
Will this method mentioned for LG G2 with Qualcomm(QHSB BULK) fix the file or here it's totally different thing? I am really keen in this project because my device has been dead since 5 months.

Have you got a solution?

I would like to participate in this project
Can i be of some use in this project ? Ive tried all possible ways to get my phone to life but failed .

Keep it up Guys..... We all are waiting. ..

Thanks guyzz to start the project of reviving moto e back to life i too bricked it 2-3 month ago. ill help u guzz in testing and collecting data and giving it here.lets unbrick our device....
[Edit]- if u need files from moto e tell me ..... i have a spare working moto e also.

You can recreate all the files needed, but you can't sign them. Non-signed files won't pass verification and it won't work.
Don't let that demotivate you though, you may come up with something that we didn't see when the first Moto G bricks came around more than year ago.

Try and report back
Did anyone try this method for One Plus, please report back.

Klock2 said:
Did anyone try this method for One Plus, please report back.
Click to expand...
Click to collapse
those files are for one plus one, wont work on moto e

iTudorS said:
those files are for one plus one, wont work on moto e
Click to expand...
Click to collapse
Its not even proper for OnePlus One but ColorOS plays is its role here. So I think it might work as Qualcomm Device i.e QHSBULK

broken partition table, please help - newbie

Hi, I recently decided to dust off my old nexus 10 and install a current version of android on it. With some guides I unlocked the bootloader, installed TWRP, installed AOSP Android 9.0 Pie and then when I wanted to install open gapps I got an not enough space error. After some searching I found a post with a repit file, which should automatically increase the size of my system partition. Unfortunatelly while this repit thing was running the display flickered for a second and the resize failed. (Stupid as I am I didnt make screenshot of the error :/) I think the screen flickering thing is a hardware problem, as it did this even without cutum recovery/rom from time to time. But i always thought it was only a problem with the the screen backlight, as it had no impact on any running software before. (I replaced the battery now to maybe fix this.) But my main problem now is, that TWRP cant mount any partitions. I think the partition table is broken.
fdisk -l doesnt output anything
fdisk -l /dev/block/mmcblk0
Code:
warning: GPT array CRC is invalid
Found valid GPT with protective MBR; using GPT
Disk mmcblk0: 61071360 sectors, 1148M
Logical sector size: 512
Disk identifier (GUID): 52444e41-494f-2044-4d4d-43204449534b
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 61071326
Number Start (sector) End (sector) Size Code Name
1 8192 49151 20.0M 0700 efs
2 49152 65535 8192K 0700 param
3 65536 98303 16.0M 0700 boot
4 98304 163711 31.9M 0700 recovery
5 163712 163839 65536 0700 metadata
6 163840 172031 4096K 0700 misc
7 172032 376831 100M 0700 cache
8 2301952 2826239 256M 0700
9 2891776 61063167 27.7G 0700 userdata
I think 8 should be the corrupted system partition. But isnt there also "data" missing?
Should I resize 8 to 376832 - 2891775 and fix the missing name?
ls /dev/block
Code:
loop0 loop5 mmcblk0boot1 ram11 ram2 ram7
loop1 loop6 platform ram12 ram3 ram8
loop2 loop7 ram0 ram13 ram4 ram9
loop3 mmcblk0 ram1 ram14 ram5 zram0
loop4 mmcblk0boot0 ram10 ram15 ram6
There mmcblk0p7, mmcblk0p8, etc. are missing. How can I fix this?
Can someone help me please? I dont want to break it even further :/

I think I solved it. I downloaded the factory image and ran flash-all. Now the stock rom is running again and I can try flashing a custom rom again.

How to resize a partition table ?

I'm trying to fix my messed up partition table in my Meizu 5 PRO for Ubuntu Touch installation.
Using ADB and fdisk I've managed to get this print out:
Code:
~ # fdisk /dev/block/sda
Note: sector size is 4096 (not 512)
Found valid GPT with protective MBR; using GPT
Command (m for help): p
Disk /dev/block/sda: 122142720 sectors, 1984M
Logical sector size: 4096
Disk identifier (GUID): 00042021-0408-4601-9dcc-a8c51255994f
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 15267834
Number Start (sector) End (sector) Size Code Name
1 1024 1279 1024K 0700 private
2 1280 1343 256K 0700 proinfo
3 1344 1407 256K 0700 misc
21 2048 3071 4096K 0700 param
22 3072 5119 8192K 0700 efs
23 5120 5631 2048K 0700 pnv
24 5632 6655 4096K 0700 ldfw
25 6656 7679 4096K 0700 dtb
26 7680 13823 24.0M 0700 bootimg
27 13824 22015 32.0M 0700 recovery
28 22016 30207 32.0M 0700 bootlogo
29 30208 35327 20.0M 0700 rstinfo
30 35328 40447 20.0M 0700 mnv
31 40448 45567 20.0M 0700 reserved1
32 45568 50687 20.0M 0700 reserved2
33 50688 55807 20.0M 0700 reserved3
41 65536 720895 2560M 0700 system
42 720896 851967 512M 0700 custom
43 851968 15267834 [B]54.9G 0700 cache[/B]
44 55808 65535 [B]38.0M 0700 userdata[/B]
I bolded partitions in question. Cache is taking up all the storage whereas "userdata" gets only 38MB. I need to resize "userdata" partition to take up most of the storage and leave about 2 GB for cache. I noticed cache partition is formatted in ext4 and "userdata" is vfat.
option "d" selects partition 1 for some reason.
after running
Code:
disk /dev/block/sda43
(which is the partition with 60GB) I get:
Code:
Command (m for help): p
Disk /dev/block/sda43: 59.0 GB, 59047391232 bytes
64 heads, 32 sectors/track, 7038 cylinders
Units = cylinders of 2048 * 4096 = 8388608 bytes
Device Boot Start End Blocks Id System
Someone more experienced, can you guide me ? I don't wanna mess it up more than it is.
Thank you in advance.
Update:
Have learned that the best tool for resizing a filesystem is resize2fs thus I ran:
Code:
~ # resize2fs /dev/block/sda43 1G
However even after resizing the filesystem to 1GB I still get:
Code:
43 851968 15267834 [B]54.9G 0700 cache[/B]
Shouldn't it be reading 1GB now ???

Oh boy. Maybe parts of this guide could help you:
https://forum.xda-developers.com/meizu-pro-5/how-to/tutorial-how-to-upgrade-to-ubuntu-touch-t4021397
You *need* the correct fdisk version for this, as stated in the guide.
Do not just copy the bold parts. Sectors for your current table are below the next code box):
Code:
Command (m for help): d
Partition number (1-3,21-33,43,44, default 44): 43
Partition 43 has been deleted
Command (m for help): d
Partition number (1-3,21-33,44, default 44): 44
Partition 44 has been deleted.
Command (m for help): n
Partition number (4-20,34-40,43-128, default 4): 43
First sector (6-15267834, default 1769472): [B]1769472[/B]
Last sector, +sectors or +size{K,M,G,T,P} (1769472-15267834, default 15267834): [B]2293775[/B]
Created a new partition 43 of type 'Linux filesystem' and of size 2 GiB.
Command (m for help): n
Partition number (4-20,34-40,44-128, default 4): 44
First sector (6-15267834, default 2294016): [B]2293776[/B]
Last sector, +sectors or +size{K,M,G,T,P} (2293776-15267834, default 15267834): [B]15267824[/B]
Created a new partition 44 of type 'Linux filesystem' and of size 49.5 GiB.
When creating partition 43 sector should be first 851969 - last 1376271 for 2GB cache
and for partition 44 first 1376272 - last 15267824 to assign the remaining space to userdata.
Next change the partition types to "Microsoft basic data"
Code:
Command (m for help): t
Partition number (1-3,21-33,41-44, default 44): 43
Partition type (type L to list all types): 11
Changed type of partition 'Linux filesystem' to 'Microsoft basic data'.
Command (m for help): t
Partition number (1-3,21-33,41-44, default 44): 44
Partition type (type L to list all types): 11
Changed type of partition 'Linux filesystem' to 'Microsoft basic data'.
Check again with "p", if the types are correct. If not, search correct type number with "t" and "L" and try again.
Afterwards, you need to continue to give the partitions names:
Code:
Command (m for help): x
Expert command (m for help): n
Partition number (1-3,21-33,41-44, default 44): 43
New name: cache
Partition number (1-3,21-33,41-44, default 44): 44
New name: userdata
Expert command (m for help): r
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
If the table has been successfully altered, you can now continue to install the filesystem:
Code:
~ # mke2fs -t ext4 -m 0 /dev/block/sda43
~ # mke2fs -t ext4 -m 0 /dev/block/sda44
This should fix your current dilemma. Its a lengthy guide and if you actually want the most recent ubuntu touch you might as well do it completely, resizing your system partition too. In that case ignore above changes.