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

[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?

After repartitioning /dev/block/mmcblk0p15 is missing - mount /data (invalid argument

Hello,
I wanted to flash Android 6 on my Xperia S (32GB).
Bootloader + root are unlocked.
I downloaded the image and extracted the .zip file.
=> new cmd:
Code:
fastboot flash boot recovery.img
fastboot reboot
Now the TWRP 3.0 screen appeared.
The problematic part was now the reparitioning.
Here you can see the full output (I followed this steps: http://forum.xda-developers.com/showpost.php?p=64862885&postcount=2)
Code:
~ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 31.9 GB, 31910264832 bytes
4 heads, 16 sectors/track, 973824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 65 2048 f0 Linux/PA-RISC boot
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 65 81 512 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 768 20480 48 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 769 954240 30511104 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 785 800 512 46 Unknown
/dev/block/mmcblk0p6 833 928 3072 4a Unknown
/dev/block/mmcblk0p7 961 1056 3072 4b Unknown
/dev/block/mmcblk0p8 1089 1184 3072 58 Unknown
/dev/block/mmcblk0p9 1217 1376 5120 70 Unknown
/dev/block/mmcblk0p10 1409 1664 8192 83 Linux
/dev/block/mmcblk0p11 1665 2176 16384 f0 Linux/PA-RISC boot
/dev/block/mmcblk0p12 2177 34944 1048576 83 Linux
/dev/block/mmcblk0p13 34945 42944 256000 83 Linux
/dev/block/mmcblk0p14 42945 108480 2097152 83 Linux
/dev/block/mmcblk0p15 108481 954240 27064320 c Win95 FAT32 (LBA)
~ # fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 973824.
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): p
Disk /dev/block/mmcblk0: 31.9 GB, 31910264832 bytes
4 heads, 16 sectors/track, 973824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 65 2048 f0 Linux/PA-RISC boot
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 65 81 512 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 768 20480 48 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 769 954240 30511104 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 785 800 512 46 Unknown
/dev/block/mmcblk0p6 833 928 3072 4a Unknown
/dev/block/mmcblk0p7 961 1056 3072 4b Unknown
/dev/block/mmcblk0p8 1089 1184 3072 58 Unknown
/dev/block/mmcblk0p9 1217 1376 5120 70 Unknown
/dev/block/mmcblk0p10 1409 1664 8192 83 Linux
/dev/block/mmcblk0p11 1665 2176 16384 f0 Linux/PA-RISC boot
/dev/block/mmcblk0p12 2177 34944 1048576 83 Linux
/dev/block/mmcblk0p13 34945 42944 256000 83 Linux
/dev/block/mmcblk0p14 42945 108480 2097152 83 Linux
/dev/block/mmcblk0p15 108481 954240 27064320 c Win95 FAT32 (LBA)
Command (m for help): d
Partition number (1-15): 15
Command (m for help): d
Partition number (1-14): 14
Command (m for help): n
First cylinder (769-954240, default 769): 42945
Last cylinder or +size or +sizeM or +sizeK (42945-954240, default 954240):
Using default value 954240
Command (m for help): t
Partition number (1-14): 14
Hex code (type L to list codes): 83
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
The next step was
Code:
Now we will convert /data and /cache to F2FS.
Ext4 is not supported anymore on nAOSProm. You don't need to take care about the 16384 byte to reserve for encryption. TWRP will do it for you.
Wipe => Advanced Wipe => select Data => Repair or Change File system => Change File System =>F2FS =>Swipe to Change
Code:
Mount Point /data
File system: f2fs
Present: Yes
Size: 0MB
Free: 0MB
Used: 0MB
Changing the file system results in:
Code:
Could not mount /data and unable to find crypto footer.
Failed to mount /data (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount /data (Invalid argument)
...done
Unable to mount storage
Failed to mount /data (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
Failed to mount /data (Invalid argument)
MTP Enabled
Failed to mount /data (Invalid argument)
If I execute
Code:
fdisk -l /dev/block/mmcblk0
I see that /dev/block/mmcblk0p15 is missing.
Code:
~ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 31.9 GB, 31910264832 bytes
4 heads, 16 sectors/track, 973824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 65 2048 f0 Linux/PA-RISC boot
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 65 81 512 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 768 20480 48 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 769 954240 30511104 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 785 800 512 46 Unknown
/dev/block/mmcblk0p6 833 928 3072 4a Unknown
/dev/block/mmcblk0p7 961 1056 3072 4b Unknown
/dev/block/mmcblk0p8 1089 1184 3072 58 Unknown
/dev/block/mmcblk0p9 1217 1376 5120 70 Unknown
/dev/block/mmcblk0p10 1409 1664 8192 83 Linux
/dev/block/mmcblk0p11 1665 2176 16384 f0 Linux/PA-RISC boot
/dev/block/mmcblk0p12 2177 34944 1048576 83 Linux
/dev/block/mmcblk0p13 34945 42944 256000 83 Linux
/dev/block/mmcblk0p14 42945 954240 29161464 83 Linux
Can anyone help me out please?
Thanks in advance.

Kesandal said:
Hello,
I wanted to flash Android 6 on my Xperia S (32GB).
Bootloader + root are unlocked.
I downloaded the image and extracted the .zip file.
=> new cmd:
Code:
fastboot flash boot recovery.img
fastboot reboot
Now the TWRP 3.0 screen appeared.
The problematic part was now the reparitioning.
Here you can see the full output (I followed this steps: http://forum.xda-developers.com/showpost.php?p=64862885&postcount=2)
Code:
~ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 31.9 GB, 31910264832 bytes
4 heads, 16 sectors/track, 973824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 65 2048 f0 Linux/PA-RISC boot
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 65 81 512 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 768 20480 48 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 769 954240 30511104 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 785 800 512 46 Unknown
/dev/block/mmcblk0p6 833 928 3072 4a Unknown
/dev/block/mmcblk0p7 961 1056 3072 4b Unknown
/dev/block/mmcblk0p8 1089 1184 3072 58 Unknown
/dev/block/mmcblk0p9 1217 1376 5120 70 Unknown
/dev/block/mmcblk0p10 1409 1664 8192 83 Linux
/dev/block/mmcblk0p11 1665 2176 16384 f0 Linux/PA-RISC boot
/dev/block/mmcblk0p12 2177 34944 1048576 83 Linux
/dev/block/mmcblk0p13 34945 42944 256000 83 Linux
/dev/block/mmcblk0p14 42945 108480 2097152 83 Linux
/dev/block/mmcblk0p15 108481 954240 27064320 c Win95 FAT32 (LBA)
~ # fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 973824.
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): p
Disk /dev/block/mmcblk0: 31.9 GB, 31910264832 bytes
4 heads, 16 sectors/track, 973824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 65 2048 f0 Linux/PA-RISC boot
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 65 81 512 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 768 20480 48 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 769 954240 30511104 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 785 800 512 46 Unknown
/dev/block/mmcblk0p6 833 928 3072 4a Unknown
/dev/block/mmcblk0p7 961 1056 3072 4b Unknown
/dev/block/mmcblk0p8 1089 1184 3072 58 Unknown
/dev/block/mmcblk0p9 1217 1376 5120 70 Unknown
/dev/block/mmcblk0p10 1409 1664 8192 83 Linux
/dev/block/mmcblk0p11 1665 2176 16384 f0 Linux/PA-RISC boot
/dev/block/mmcblk0p12 2177 34944 1048576 83 Linux
/dev/block/mmcblk0p13 34945 42944 256000 83 Linux
/dev/block/mmcblk0p14 42945 108480 2097152 83 Linux
/dev/block/mmcblk0p15 108481 954240 27064320 c Win95 FAT32 (LBA)
Command (m for help): d
Partition number (1-15): 15
Command (m for help): d
Partition number (1-14): 14
Command (m for help): n
First cylinder (769-954240, default 769): 42945
Last cylinder or +size or +sizeM or +sizeK (42945-954240, default 954240):
Using default value 954240
Command (m for help): t
Partition number (1-14): 14
Hex code (type L to list codes): 83
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
The next step was
Code:
Now we will convert /data and /cache to F2FS.
Ext4 is not supported anymore on nAOSProm. You don't need to take care about the 16384 byte to reserve for encryption. TWRP will do it for you.
Wipe => Advanced Wipe => select Data => Repair or Change File system => Change File System =>F2FS =>Swipe to Change
Code:
Mount Point /data
File system: f2fs
Present: Yes
Size: 0MB
Free: 0MB
Used: 0MB
Changing the file system results in:
Code:
Could not mount /data and unable to find crypto footer.
Failed to mount /data (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount /data (Invalid argument)
...done
Unable to mount storage
Failed to mount /data (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
Failed to mount /data (Invalid argument)
MTP Enabled
Failed to mount /data (Invalid argument)
If I execute
Code:
fdisk -l /dev/block/mmcblk0
I see that /dev/block/mmcblk0p15 is missing.
Code:
~ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 31.9 GB, 31910264832 bytes
4 heads, 16 sectors/track, 973824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 65 2048 f0 Linux/PA-RISC boot
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 65 81 512 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 768 20480 48 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 769 954240 30511104 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 785 800 512 46 Unknown
/dev/block/mmcblk0p6 833 928 3072 4a Unknown
/dev/block/mmcblk0p7 961 1056 3072 4b Unknown
/dev/block/mmcblk0p8 1089 1184 3072 58 Unknown
/dev/block/mmcblk0p9 1217 1376 5120 70 Unknown
/dev/block/mmcblk0p10 1409 1664 8192 83 Linux
/dev/block/mmcblk0p11 1665 2176 16384 f0 Linux/PA-RISC boot
/dev/block/mmcblk0p12 2177 34944 1048576 83 Linux
/dev/block/mmcblk0p13 34945 42944 256000 83 Linux
/dev/block/mmcblk0p14 42945 954240 29161464 83 Linux
Can anyone help me out please?
Thanks in advance.
Click to expand...
Click to collapse
What You have done is correct, The problem is since there is no space available at end of data partition for encryption, it is giving the error. Are You sure the TWRP version is 3.0? Try rebooting to TWRP once and converting the file system. If that doesn't work, I would recommend using recovery from latest version of nAOSP.
Also, /dev/block/mmcblk0p15 is supposed to be missing. This command
Command (m for help): d
Partition number (1-15): 15
deletes the partition.
p14 is the data partition and p15 was the internal storage.
In Marshmallow version, a different type of storage structure is used. There is no concept of separate internal storage in it, the storage is merged with data partition.
Here, p14 is the

GUIDE: How to repartition for vendor and how to use GSIs

Guide to repartition your LG V30 to have a vendor partition
This guide is for people who are willing to repartition their V30 (Tested so far on my H930).
It will make your system partition smaller by 512MB, and create a vendor partition instead.
You will still have enough space for (full) stock ROMs too (they just ignore the new partition then)
Code:
#include "std_disclaimer.h"
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What you need:
The scripts attached in the zip file
TWRP
A PC with working ADB (I doubt you wanna write everything in the TWRP command line)
Oreo firmware recommended (for LOS and GSIs)
Bravery
(should be quite safe though, as I did it myself, and know other people who did it)
Steps
Read this carefully before you execute it, twice! Make sure you understand every step. Learn it to the point of when i wake you up in the middle of the night, and ask you questions about it, you can answer instantly.
Boot into TWRP!!!
Make a backup of EVERYTHING on your phone (system, boot, recovery, data and so on)
Code:
The script will format system again, its important to backup!
Copy the contents of the .zip file to your phone
Open a command line/terminal on your PC (wherever you have access to ADB)
Connect your Phone to your PC
Everything now in command line/terminal
adb shell
cd /path/to/the/script/folder
Code:
e.g.
cd /external_sd/repartition/
./backup_gpt.sh
Code:
This will create a backup of your current gpt table on /external_sd/GPT_orig.bin
Code:
Todo this manually execute:
sgdisk /dev/block/sda --b=/path/to/GPT_orig.bin
./make_vendor.sh
Code:
Follow instructions on screen if you really wanna do this!
To apply the changes, remove the --pretend from the sgdisk commands! Otherwise it will just pretend to apply the changes (so you can check if it would fail or not)
(not an automatic script incase something goes wrong)
Reboot into recovery again
Restore your previous backup
How to revert the changes?
Do everything till step 7
./restore_gpt.sh
Code:
This will take the backup of your gpt table on /external_sd/GPT_orig.bin
Code:
Todo this manually execute:
sgdisk --load-backup=/path/to/GPT_orig.bin /dev/block/sda
Wipe system again
Flash a .kdz (Instructions case be found on XDA)
How to use a GSI (Generic System Image)
Make a backup of EVERYTHING on your phone (system, boot, recovery, data and so on)
Flash treble enabled lineage build: link
Wipe data (if it isnt)
Reboot into bootloader
in commandline/terminal:
fastboot flash system <name_of_gsi>.img
OPTIONAL:
fastboot boot <twrp>.img
Code:
fastboot doesnt provide a way to reboot to recovery directly, you can also optionally do the button dance
flash magisk/gapps
fastboot reboot
Thanks for the original script from here

what happens if it is partitioned and we flash a kdz using lg up (without reverting the partitions)?

iRS_ said:
what happens if it is partitioned and we flash a kdz using lg up (without reverting the partitions)?
Click to expand...
Click to collapse
I believe that it just changes the gpt to its original state, so if everything goes right, nothing will happen except you losing the vendor partition

Will this allow my US998 to be supported by the treble project?

AutinDroid said:
I believe that it just changes the gpt to its original state, so if everything goes right, nothing will happen except you losing the vendor partition
Click to expand...
Click to collapse
Yep, it should do that. The kdz rewrites your GPT, atleast it should. Doesnt contain that for nothing i suppose?
liushangrong said:
Will this allow my US998 to be supported by the treble project?
Click to expand...
Click to collapse
It should work also on your US998 to create a new partition. The treblelized ROM isnt yet built for the US998 though. Dont have any testers that could have tried it out on the US998.

SGCMarkus said:
Yep, it should do that. The kdz rewrites your GPT, atleast it should. Doesnt contain that for nothing i suppose?.
Click to expand...
Click to collapse
so if i make the changes i can safely flash a kdz and revert everything back to stock?

iRS_ said:
so if i make the changes i can safely flash a kdz and revert everything back to stock?
Click to expand...
Click to collapse
Should do the trick
Or, less hassle, you restore the GPT that you should backup before anyway (see guide) ^^
That also works.

i'm trying to repartition my v30+ (h930g).
i've succesfull backup my gpt, but i've problem when trying to format vendor. i have the following error:
/external_sd/repartition # make_ext4fs /dev/block/sda23
filesystem size too small
Click to expand...
Click to collapse
here is complete output:
/external_sd # cd repartition/
/external_sd/repartition #
/external_sd/repartition #
/external_sd/repartition # ./make_vendor.sh
/vendor missing
*********Resize /system to 1505792 = 1585541 - 79750 + 1 (inclusize) = 1505792
To really repartition, copy the following commands, and execute them
e2fsck -f /dev/block/bootdevice/by-name/system
resize2fs /dev/block/bootdevice/by-name/system 1505792
Setting name!
partNum is 17
REALLY setting name!
Setting name!
partNum is 22
REALLY setting name!
Disk /dev/block/sda: 31137792 sectors, 118.8 GiB
Logical sector size: 4096 bytes
Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Partition table holds up to 32 entries
First usable sector is 6, last usable sector is 31137786
Partitions will be aligned on 2-sector boundaries
Total free space is 0 sectors (0 bytes)
Number Start (sector) End (sector) Size Code Name
1 6 12293 48.0 MiB FFFF laf
2 12294 24581 48.0 MiB FFFF lafbak
3 24582 32773 32.0 MiB FFFF mpt
4 32774 35333 10.0 MiB FFFF drm
5 35334 36869 6.0 MiB FFFF sns
6 36870 37125 1024.0 KiB FFFF misc
7 37126 45317 32.0 MiB FFFF ftm
8 45318 62213 66.0 MiB FFFF factory
9 62214 62341 512.0 KiB FFFF encrypt
10 62342 62469 512.0 KiB FFFF eksst
11 62470 62597 512.0 KiB FFFF rct
12 62598 62725 512.0 KiB FFFF ssd
13 62726 62853 512.0 KiB FFFF keystore
14 62854 71045 32.0 MiB FFFF persist
15 71046 73093 8.0 MiB FFFF srtc
16 73094 79237 24.0 MiB FFFF qni
17 79238 79749 2.0 MiB FFFF pstore
18 79750 1585541 5.7 GiB 8300 system
19 1716614 1847685 512.0 MiB FFFF cache
20 1847686 1935749 344.0 MiB 0700 OP
21 1935750 31137785 111.4 GiB FFFF userdata
22 31137786 31137786 4.0 KiB FFFF grow
23 1585542 1716613 512.0 MiB 8300 vendor
sgdisk --pretend --delete=18 --new=18:79750:1585541 --change-name=18:system --new=23:1585542:1716613 --change-name=23:vendor --print /dev/block/sda
This will format system and vendor again, so it can be used
make_ext4fs /dev/block/sda18
make_ext4fs /dev/block/sda23
/external_sd/repartition # e2fsck -f /dev/block/bootdevice/by-name/system
e2fsck 1.43.3 (04-Sep-2016)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
system: 9726/403200 files (0.0% non-contiguous), 1229698/1611326 blocks
/external_sd/repartition # resize2fs /dev/block/bootdevice/by-name/system 1505792
resize2fs 1.43.3 (04-Sep-2016)
Resizing the filesystem on /dev/block/bootdevice/by-name/system to 1505792 (4k) blocks.
The filesystem on /dev/block/bootdevice/by-name/system is now 1505792 (4k) blocks long.
/external_sd/repartition # sgdisk --pretend --delete=18 --new=18:79750:1585541 --change-name=18:system --new=23:1585542:1716613 --change-name=23:vendor --print /dev/block/sda
Setting name!
partNum is 17
REALLY setting name!
Setting name!
partNum is 22
REALLY setting name!
Disk /dev/block/sda: 31137792 sectors, 118.8 GiB
Logical sector size: 4096 bytes
Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Partition table holds up to 32 entries
First usable sector is 6, last usable sector is 31137786
Partitions will be aligned on 2-sector boundaries
Total free space is 0 sectors (0 bytes)
Number Start (sector) End (sector) Size Code Name
1 6 12293 48.0 MiB FFFF laf
2 12294 24581 48.0 MiB FFFF lafbak
3 24582 32773 32.0 MiB FFFF mpt
4 32774 35333 10.0 MiB FFFF drm
5 35334 36869 6.0 MiB FFFF sns
6 36870 37125 1024.0 KiB FFFF misc
7 37126 45317 32.0 MiB FFFF ftm
8 45318 62213 66.0 MiB FFFF factory
9 62214 62341 512.0 KiB FFFF encrypt
10 62342 62469 512.0 KiB FFFF eksst
11 62470 62597 512.0 KiB FFFF rct
12 62598 62725 512.0 KiB FFFF ssd
13 62726 62853 512.0 KiB FFFF keystore
14 62854 71045 32.0 MiB FFFF persist
15 71046 73093 8.0 MiB FFFF srtc
16 73094 79237 24.0 MiB FFFF qni
17 79238 79749 2.0 MiB FFFF pstore
18 79750 1585541 5.7 GiB 8300 system
19 1716614 1847685 512.0 MiB FFFF cache
20 1847686 1935749 344.0 MiB 0700 OP
21 1935750 31137785 111.4 GiB FFFF userdata
22 31137786 31137786 4.0 KiB FFFF grow
23 1585542 1716613 512.0 MiB 8300 vendor
/external_sd/repartition # make_ext4fs /dev/block/sda18
Creating filesystem with parameters:
Size: 6704594944
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 25576
Label:
Blocks: 1636864
Block groups: 50
Reserved block group size: 399
Created filesystem with 11/409600 inodes and 54888/1636864 blocks
/external_sd/repartition #
/external_sd/repartition #
/external_sd/repartition # make_ext4fs /dev/block/sda23
filesystem size too small
Click to expand...
Click to collapse
what i'm wrong?

Having the same issue here

HD1999 said:
Having the same issue here
Click to expand...
Click to collapse
do you own a h930(64gb) or h930g(128gb)?

I own a H930

ah ok, so this happen on 64gb version too

Hmm...
Ok, forgot to add a message to the script ?
you have to remove the --pretend from the commands, otherwise it will just do like it does it, without actually doing it (to see if everything will work the way it should before actually applying the changes)
sorry about that

SGCMarkus said:
Hmm...
Ok, forgot to add a message to the script
you have to remove the --pretend from the commands, otherwise it will just do like it does it, without actually doing it (to see if everything will work the way it should before actually applying the changes)
sorry about that
Click to expand...
Click to collapse
EDIT: i reboted into recovery again and i was able to format /vendor. is normal that i can see vendor partition in backup section of twrp?
now i'm going to flash yoru los
hi markus, i figure it reading the script, but same error here!
this is the comannd ì execute after run ./make_vendor.sh:
e2fsck -f /dev/block/bootdevice/by-name/system
resize2fs /dev/block/bootdevice/by-name/system 1505792
sgdisk --delete=18 --new=18:79750:1585541 --change-name=18:system --new=23:1585542:1716613 --change-name=23:vendor --print /dev/block/sda
make_ext4fs /dev/block/sda18
make_ext4fs /dev/block/sda23
i ran the script and the command above ehn the phone are in twrp(assuming is right to do this!)

okaiuz said:
EDIT: i reboted into recovery again and i was able to format /vendor. is normal that i can see vendor partition in backup section of twrp?
now i'm going to flash yoru los
Click to expand...
Click to collapse
Will also add this, to reboot into recovery again then
Glad it worked. And ehhm, i dont think its normal that TWRP sees it for backups? But if it does, no need for a new TWRP (tbh, during all my testings, i didnt check this, or didnt look if vendor is there or not)

i restore the original gpt and i start from ascratch.
iin restore_gpt.sh you have to change "external_SD" to "external_sd"
don't think need to rebbot, after restoring original gpt, and execute above command, formatting /vendor work on first run!
another problem...i'm trying to flash your los(non treblelized) but i receive:
Updater process ended with ERROR: 7
I:Install took 0 second(s).
Error installing zip file '/sdcard/Download/lineage-15.1-20180516-UNOFFICIAL-h930.zip'
Updating partition details...
Failed to mount '/system' (Invalid argument)
full log attached

okaiuz said:
i restore the original gpt and i start from ascratch.
iin restore_gpt.sh you have to change "external_SD" to "external_sd"
don't think need to rebbot, after restoring original gpt, and execute above command, formatting /vendor work on first run!
another problem...i'm trying to flash your los(non treblelized) but i receive:
Updater process ended with ERROR: 7
I:Install took 0 second(s).
Error installing zip file '/sdcard/Download/lineage-15.1-20180516-UNOFFICIAL-h930.zip'
Updating partition details...
Failed to mount '/system' (Invalid argument)
full log attached
Click to expand...
Click to collapse
EDIT: maybe related to content of META-INF/com/google/android/updater-script file?
i see this :
assert(getprop("ro.product.device") == "v30" || getprop("ro.build.product") == "v30" ||
getprop("ro.product.device") == "joan" || getprop("ro.build.product") == "joan" ||
getprop("ro.product.device") == "h930" || getprop("ro.build.product") == "h930" || abort("E3004: This package is for device: v30,joan,h930; this device is " +
Click to expand...
Click to collapse
my device is h930g, same as h930 but with 128gb of rom (also called v30+). i check with adb and my device show this values:
[ro.build.product]: [joan]
[ro.product.device]: [joan]

okaiuz said:
i restore the original gpt and i start from ascratch.
iin restore_gpt.sh you have to change "external_SD" to "external_sd"
don't think need to rebbot, after restoring original gpt, and execute above command, formatting /vendor work on first run!
another problem...i'm trying to flash your los(non treblelized) but i receive:
Updater process ended with ERROR: 7
I:Install took 0 second(s).
Error installing zip file '/sdcard/Download/lineage-15.1-20180516-UNOFFICIAL-h930.zip'
Updating partition details...
Failed to mount '/system' (Invalid argument)
full log attached
Click to expand...
Click to collapse
Seems like you need to reboot inbetween, or try to format /system before flashing?
I dont encounter that problem :/

SGCMarkus said:
Seems like you need to reboot inbetween, or try to format /system before flashing?
I dont encounter that problem :/
Click to expand...
Click to collapse
i've made several test on it...wiping system data cache & art, reflash your recovery,format system in recovery & via adb..
The only thoing i haven't tested is to flash full kdz and then repartition.
i don't know if this can be useful for debugging,but when i've switched to oreo i don't flash full kdz, but the twrp flashable rom found on v30 section of xda

okaiuz said:
i've made several test on it...wiping system data cache & art, reflash your recovery,format system in recovery & via adb..
The only thoing i haven't tested is to flash full kdz and then repartition.
i don't know if this can be useful for debugging,but when i've switched to oreo i don't flash full kdz, but the twrp flashable rom found on v30 section of xda
Click to expand...
Click to collapse
Hm... that shouldnt matter actually. Its a weird behaviour though you have there. Can you "tick" system in the mount options of TWRP? if no, send me a log of that too. This seems really weird to me.

Unable to Fastboot flash system.img

Tried two offical Xiaomi fastboot Pie images, and system.img doesn't flash. Other smaller in size system images I flashed to see what would happen do go through, but they don't work. Pie image is 2.1 GB. Other partitions are all flashed.
Each attempt via Xiaomi flash tool ends with: Chunk data size exceeds partition size.
Log:
$fastboot -s 08f97d930705 flash system_a C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\daisy_global_images_V10.0.10.0.PDLMIXM_9.0\\images\system.img ||
[10:26:06 AM 08f97d930705]:target reported max download size of 534773760 bytes
[10:26:06 AM 08f97d930705]:sending sparse 'system_a' 1/3 (462332 KB)...
[10:26:06 AM 08f97d930705]KAY [ 59.062s]
[10:26:06 AM 08f97d930705]:writing 'system_a' 1/3...
[10:26:06 AM 08f97d930705]:error:FAILED (remote: Chunk data size exceeds partition size)
[10:26:06 AM 08f97d930705]:flashSuccess False
Fastboot flash_all.bat gives:
fastboot getvar product 2>&1 | findstr /r /c:"^product: *d
aisy" ||
The system cannot find message text for message number 0x8 in the message file f
or System.
Fastboot flash system sends sparse chunks and gives:
data too large
So, what gives? Any ideas greatly appreciated.

MarkR7 said:
Tried two offical Xiaomi fastboot Pie images, and system.img doesn't flash. Other smaller in size system images I flashed to see what would happen do go through, but they don't work. Pie image is 2.1 GB. Other partitions are all flashed.
Each attempt via Xiaomi flash tool ends with: Chunk data size exceeds partition size.
Log:
$fastboot -s 08f97d930705 flash system_a C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\daisy_global_images_V10.0.10.0.PDLMIXM_9.0\\images\system.img ||
[10:26:06 AM 08f97d930705]:target reported max download size of 534773760 bytes
[10:26:06 AM 08f97d930705]:sending sparse 'system_a' 1/3 (462332 KB)...
[10:26:06 AM 08f97d930705]KAY [ 59.062s]
[10:26:06 AM 08f97d930705]:writing 'system_a' 1/3...
[10:26:06 AM 08f97d930705]:error:FAILED (remote: Chunk data size exceeds partition size)
[10:26:06 AM 08f97d930705]:flashSuccess False
Fastboot flash_all.bat gives:
fastboot getvar product 2>&1 | findstr /r /c:"^product: *d
aisy" ||
The system cannot find message text for message number 0x8 in the message file f
or System.
Fastboot flash system sends sparse chunks and gives:
data too large
So, what gives? Any ideas greatly appreciated.
Click to expand...
Click to collapse
It could be an error from the tool or maybe you need to delete some logs that can cause a conflict anyway did you try using just fastboot command to flash just system? if not trying finding which is your current slot and then flash it directly to it.
I guess size image support is around 2,5GB.

SubwayChamp said:
It could be an error from the tool or maybe you need to delete some logs that can cause a conflict anyway did you try using just fastboot command to flash just system? if not trying finding which is your current slot and then flash it directly to it.
I guess size image support is around 2,5GB.
Click to expand...
Click to collapse
I direct fastboot flashed system multiple times, also flash all bat, I also restored Oeeo from TWRP backup multiple timea, Oreo working fine, now that I think of it, Mi Flash tool seems to be from 2017 and it seems old to me, I got it from their link somewhere, but could the newest one be that old? Need to check that.

MarkR7 said:
I direct fastboot flashed system multiple times, also flash all bat, I also restored Oeeo from TWRP backup multiple timea, Oreo working fine, now that I think of it, Mi Flash tool seems to be from 2017 and it seems old to me, I got it from their link somewhere, but could the newest one be that old? Need to check that.
Click to expand...
Click to collapse
This seems to be the latest stable version https://c.mi.com/thread-1329226-1-0.html and although this is newer use the tool from 2017 but ever worked for me https://xiaomifirmware.com/downloads/mif anyway you have too the option to flash through edl

I think someone had a problem due to fastboot being too old.
The partition should be 2.5Gb so unless you or someone else resized partitions, it should be large enough.
I can use fdisk from a running phone to print partition info. If you can't boot, perhaps you can check from twrp?
Code:
# fdisk /dev/block/mmcblk0
Found valid GPT with protective MBR; using GPT
Command (m for help): p
Disk /dev/block/mmcblk0: 122142720 sectors, 2296M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 60 entries
First usable sector is 34, last usable sector is 122142686
Number Start (sector) End (sector) Size Name
1 34 49 8192 fsc
2 50 65 8192 ssd
3 66 81 8192 dpo
4 82 113 16384 sec
5 114 145 16384 bk1
6 146 185 20480 bk2
7 186 249 32768 DDR
8 250 313 32768 limits
9 314 377 32768 config
10 378 505 65536 bk3
11 506 761 128K lksecapp
12 762 1017 128K lksecappbak
13 1018 1529 256K devcfg_a
14 1530 2041 256K devcfg_b
15 2042 2553 256K apdp
16 2554 3065 256K msadp
17 3066 4089 512K sbl1_a
18 4090 5113 512K sbl1_b
19 5114 6137 512K rpm_a
20 6138 7161 512K rpm_b
21 7162 8185 512K mota
22 8186 9209 512K keystore
23 9210 10233 512K syscfg
24 10234 12281 1024K cmnlib_a
25 12282 14329 1024K cmnlib_b
26 14330 16377 1024K cmnlib64_a
27 16378 18425 1024K cmnlib64_b
28 18426 20473 1024K keymaster_a
29 20474 22521 1024K keymaster_b
30 22522 24569 1024K misc
31 24570 26617 1024K aboot_a
32 26618 28665 1024K aboot_b
33 28666 30713 1024K dip
34 30714 32761 1024K bk4
35 32762 36857 2048K tz_a
36 36858 40953 2048K tz_b
37 40954 49145 4096K mcfg
38 49146 65529 8192K devinfo
39 65530 81913 8192K fsg
40 81914 98297 8192K modemst1
41 98298 114681 8192K modemst2
42 114682 131065 8192K bk5
43 131066 163833 16.0M splash
44 163834 196601 16.0M dsp_a
45 196602 229369 16.0M dsp_b
46 229370 262137 16.0M bk6
47 262138 327673 32.0M mdtp_a
48 327674 393209 32.0M mdtp_b
49 393210 458745 32.0M persist
50 458746 524281 32.0M persistbak
51 524288 655359 64.0M boot_a
52 655360 786431 64.0M boot_b
53 786432 917503 64.0M logdump
54 917504 1179647 128M modem_a
55 1179648 1441791 128M modem_b
56 1441792 6684671 2560M system_a
57 6684672 11927551 2560M system_b
58 11927552 13500415 768M vendor_a
59 13500416 15073279 768M vendor_b
60 15073280 122142686 51.0G userdata
Command (m for help): q

a1291762 said:
I think someone had a problem due to fastboot being too old.
The partition should be 2.5Gb so unless you or someone else resized partitions, it should be large enough.
I can use fdisk from a running phone to print partition info. If you can't boot, perhaps you can check from twrp?
Code:
# fdisk /dev/block/mmcblk0
Found valid GPT with protective MBR; using GPT
Command (m for help): p
Disk /dev/block/mmcblk0: 122142720 sectors, 2296M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 60 entries
First usable sector is 34, last usable sector is 122142686
Number Start (sector) End (sector) Size Name
1 34 49 8192 fsc
2 50 65 8192 ssd
3 66 81 8192 dpo
4 82 113 16384 sec
5 114 145 16384 bk1
6 146 185 20480 bk2
7 186 249 32768 DDR
8 250 313 32768 limits
9 314 377 32768 config
10 378 505 65536 bk3
11 506 761 128K lksecapp
12 762 1017 128K lksecappbak
13 1018 1529 256K devcfg_a
14 1530 2041 256K devcfg_b
15 2042 2553 256K apdp
16 2554 3065 256K msadp
17 3066 4089 512K sbl1_a
18 4090 5113 512K sbl1_b
19 5114 6137 512K rpm_a
20 6138 7161 512K rpm_b
21 7162 8185 512K mota
22 8186 9209 512K keystore
23 9210 10233 512K syscfg
24 10234 12281 1024K cmnlib_a
25 12282 14329 1024K cmnlib_b
26 14330 16377 1024K cmnlib64_a
27 16378 18425 1024K cmnlib64_b
28 18426 20473 1024K keymaster_a
29 20474 22521 1024K keymaster_b
30 22522 24569 1024K misc
31 24570 26617 1024K aboot_a
32 26618 28665 1024K aboot_b
33 28666 30713 1024K dip
34 30714 32761 1024K bk4
35 32762 36857 2048K tz_a
36 36858 40953 2048K tz_b
37 40954 49145 4096K mcfg
38 49146 65529 8192K devinfo
39 65530 81913 8192K fsg
40 81914 98297 8192K modemst1
41 98298 114681 8192K modemst2
42 114682 131065 8192K bk5
43 131066 163833 16.0M splash
44 163834 196601 16.0M dsp_a
45 196602 229369 16.0M dsp_b
46 229370 262137 16.0M bk6
47 262138 327673 32.0M mdtp_a
48 327674 393209 32.0M mdtp_b
49 393210 458745 32.0M persist
50 458746 524281 32.0M persistbak
51 524288 655359 64.0M boot_a
52 655360 786431 64.0M boot_b
53 786432 917503 64.0M logdump
54 917504 1179647 128M modem_a
55 1179648 1441791 128M modem_b
56 1441792 6684671 2560M system_a
57 6684672 11927551 2560M system_b
58 11927552 13500415 768M vendor_a
59 13500416 15073279 768M vendor_b
60 15073280 122142686 51.0G userdata
Command (m for help): q
Click to expand...
Click to collapse
I don't know what the hell is going on. Just tried to flash again with newer late 2018 Xiaomi Flash tool and included fastboot. This time the thing didn't run erase commands before flashing partitions and ended up with the same Chunk Size Data exceeds partition size error. I restored to Oreo from my TWRP backups. TWRP shows partition size as normal 2.5 GB. Never touched the partition table. Smaller GSI images flash in there. Oreo is 1.7 GB, I think, it restores. On Oreo everything works, encryption disabler, Magisk. Just can't flash the lousy official Pie system, tried 10.0.03.0 Whatever, tried 10.0.10 from June, same thing. Somebody suggested I convert to ext4 image, but why the hell does it not just work? Like it can't handle the size of the system image somehow. Will try your commands, thanks. Maybe even newer Xiaomi tool. Damn
Thanks for help.
What is really bloody funny is I have puny Redmi Go running Lineage 16 and all set up without any trouble. Just hilarious.

MarkR7 said:
I don't know what the hell is going on. Just tried to flash again with newer late 2018 Xiaomi Flash tool and included fastboot. This time the thing didn't run erase commands before flashing partitions and ended up with the same Chunk Size Data exceeds partition size error. I restored to Oreo from my TWRP backups. TWRP shows partition size as normal 2.5 GB. Never touched the partition table. Smaller GSI images flash in there. Oreo is 1.7 GB, I think, it restores. On Oreo everything works, encryption disabler, Magisk. Just can't flash the lousy official Pie system, tried 10.0.03.0 Whatever, tried 10.0.10 from June, same thing. Somebody suggested I convert to ext4 image, but why the hell does it not just work? Like it can't handle the size of the system image somehow. Will try your commands, thanks. Maybe even newer Xiaomi tool. Damn
Thanks for help.
What is really bloody funny is I have puny Redmi Go running Lineage 16 and all set up without any trouble. Just hilarious.
Click to expand...
Click to collapse
Try the latest rom http://bigota.d.miui.com/V10.0.12.0...0.PDLMIXM_20190717.0000.00_9.0_59368ef014.tgz and try it using edl, edl is a lower level than fastboot and probably might work better.

edl flash fail - identical to fastboot
SubwayChamp said:
Try the latest rom http://bigota.d.miui.com/V10.0.12.0...0.PDLMIXM_20190717.0000.00_9.0_59368ef014.tgz and try it using edl, edl is a lower level than fastboot and probably might work better.
Click to expand...
Click to collapse
This thing is impossible. EDL flash fails the same way, at about the same time in the flash process. Just says error and maybe the device got disconnected. It did not.
Since I got the phone recently, I never run any OTA updates on it and it's on the lastest Oreo 9.6.11 before 10.0.2.0 Pie. System partition is actually 2.4 GB and Vendor is also slightly smaller than a1291762's partition size. Could it be they increased partitio sizes during 10.0.2.0 Pie update and not applying/skipping that update causes the trouble? Honestly I have no idea, anybody who can make something out of this? Should I run 10.0.2.0 to see if it changes partitions? Or does skipping that update cause trouble for some other unfathomable reason? I will just try OTA sooner or later, I guess.
Here's the output:
daisy_sprout:/ $ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/block/mmcblk0p56 2.4G 1.6G 751M 70% /system_root
tmpfs 1.7G 1.4M 1.7G 1% /sbin
tmpfs 1.7G 712K 1.7G 1% /dev
/dev/block/mmcblk0p58 744M 555M 174M 77% /vendor
tmpfs 1.7G 0 1.7G 0% /mnt
/dev/block/mmcblk0p49 27M 2.7M 24M 11% /persist
/dev/block/mmcblk0p54 128M 81M 47M 63% /firmware
/dev/block/mmcblk0p44 12M 6.9M 4.5M 61% /dsp
/sbin/.magisk/block/data 50G 808M 49G 2% /sbin/.magisk/modules
/data/media 50G 808M 49G 2% /storage/emulated
/mnt/media_rw/0403-0201 29G 28G 712M 98% /storage/0403-0201
daisy_sprout:/ $ df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mmcblk0p56 2539312 1754068 768860 70% /system_root
tmpfs 1821960 1500 1820460 1% /sbin
tmpfs 1821960 712 1821248 1% /dev
/dev/block/mmcblk0p58 761776 567948 178100 77% /vendor
tmpfs 1821960 0 1821960 0% /mnt
/dev/block/mmcblk0p49 28144 2772 24720 11% /persist
/dev/block/mmcblk0p54 131008 82464 48544 63% /firmware
/dev/block/mmcblk0p44 12016 7072 4620 61% /dsp
/sbin/.magisk/block/data 52562448 827192 51718872 2% /sbin/.magisk/modules

MarkR7 said:
This thing is impossible. EDL flash fails the same way, at about the same time in the flash process. Just says error and maybe the device got disconnected. It did not.
Since I got the phone recently, I never run any OTA updates on it and it's on the lastest Oreo 9.6.11 before 10.0.2.0 Pie. System partition is actually 2.4 GB and Vendor is also slightly smaller than a1291762's partition size. Could it be they increased partitio sizes during 10.0.2.0 Pie update and not applying/skipping that update causes the trouble? Honestly I have no idea, anybody who can make something out of this? Should I run 10.0.2.0 to see if it changes partitions? Or does skipping that update cause trouble for some other unfathomable reason? I will just try OTA sooner or later, I guess.
Here's the output:
daisy_sprout:/ $ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/block/mmcblk0p56 2.4G 1.6G 751M 70% /system_root
tmpfs 1.7G 1.4M 1.7G 1% /sbin
tmpfs 1.7G 712K 1.7G 1% /dev
/dev/block/mmcblk0p58 744M 555M 174M 77% /vendor
tmpfs 1.7G 0 1.7G 0% /mnt
/dev/block/mmcblk0p49 27M 2.7M 24M 11% /persist
/dev/block/mmcblk0p54 128M 81M 47M 63% /firmware
/dev/block/mmcblk0p44 12M 6.9M 4.5M 61% /dsp
/sbin/.magisk/block/data 50G 808M 49G 2% /sbin/.magisk/modules
/data/media 50G 808M 49G 2% /storage/emulated
/mnt/media_rw/0403-0201 29G 28G 712M 98% /storage/0403-0201
daisy_sprout:/ $ df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mmcblk0p56 2539312 1754068 768860 70% /system_root
tmpfs 1821960 1500 1820460 1% /sbin
tmpfs 1821960 712 1821248 1% /dev
/dev/block/mmcblk0p58 761776 567948 178100 77% /vendor
tmpfs 1821960 0 1821960 0% /mnt
/dev/block/mmcblk0p49 28144 2772 24720 11% /persist
/dev/block/mmcblk0p54 131008 82464 48544 63% /firmware
/dev/block/mmcblk0p44 12016 7072 4620 61% /dsp
/sbin/.magisk/block/data 52562448 827192 51718872 2% /sbin/.magisk/modules
Click to expand...
Click to collapse
Eventually a failed update can do some weird things like this but is unusual or rarely heard.
Don´t wait that OTA comes to your device, choose one from the official site to be flashed through stock recovery if you have some hope that this help.
Also then to try this in TWRP there is an option to restore system partition (I´m not sure if this really works)
And as a last resource maybe you might to re-adjust the size partition http://en.miui.com/thread-183258-1-1.html

OTA ROM update
Thanks for all advice, really appreciated. I got a zillion backups thru TWRP and those not working fastboot ROMs. I am on a crappy limited mobile connection right now and need to get wifi to get all the ROMs, so preferred to store them locally on a laptop, but should have just run an OTA straight away. Anyway, am back on original stock Oreo, fully stock boot system everything. Have last August 10.13 OTA rom zip and wonder how the hell to try that one. Nothing under system update that would let me use locally stored OTA ROM. Renaming it to update.zip and putting in root of internal storage doesn't seem to work for stock recovery.
Never mind. found a way. Still craps out. Says error in package zip Status 1 whatever the hell that is. Thanks anyway.

MarkR7 said:
Thanks for all advice, really appreciated. I got a zillion backups thru TWRP and those not working fastboot ROMs. I am on a crappy limited mobile connection right now and need to get wifi to get all the ROMs, so preferred to store them locally on a laptop, but should have just run an OTA straight away. Anyway, am back on original stock Oreo, fully stock boot system everything. Have last August 10.13 OTA rom zip and wonder how the hell to try that one. Nothing under system update that would let me use locally stored OTA ROM. Renaming it to update.zip and putting in root of internal storage doesn't seem to work for stock recovery.
Never mind. found a way. Still craps out. Says error in package zip Status 1 whatever the hell that is. Thanks anyway.
Click to expand...
Click to collapse
Update from internal storage and from adb sideload are available on stock recovery. Unfortunately TWRP can´t flash stock updates like on other Xiaomi devices using Miui.
Probably you might try the Miui rom ported available in this forum https://forum.xda-developers.com/mi-a2-lite/development/9-miui-rom-t3960704, system image has almost 2,40GB (version 1.1)

Stocl Recovery
SubwayChamp said:
Update from internal storage and from adb sideload are available on stock recovery. Unfortunately TWRP can´t flash stock updates like on other Xiaomi devices using Miui.
Probably you might try the Miui rom ported available in this forum https://forum.xda-developers.com/mi-a2-lite/development/9-miui-rom-t3960704, system image has almost 2,40GB (version 1.1)
Click to expand...
Click to collapse
You don't unserstand. I DO have stock recovery om both slots, everything as stock as possible. Had Full backups and restored them, boot images also. It is stock recovery that gives the error. Supposedly Status 1 has sth to do with setting permissions, but thanks anyway.

EDL finally worked, many thanks for help
:laugh:
SubwayChamp said:
Update from internal storage and from adb sideload are available on stock recovery. Unfortunately TWRP can´t flash stock updates like on other Xiaomi devices using Miui.
Probably you might try the Miui rom ported available in this forum https://forum.xda-developers.com/mi-a2-lite/development/9-miui-rom-t3960704, system image has almost 2,40GB (version 1.1)
Click to expand...
Click to collapse
:fingers-crossed:
After some fails, EDL flash finally worked and the phone is now on Pie. Many thanks for the suggestion. For some seconds after flash I thought it was a total brick, but I think it must have been exiting EDL. Normal fastboot flash of system.img failed each time.
Again, many thanks for help and time you took.