[Xiaomi Mi 2] tasadarf:
7 days ago Phone not start because partition corrupt

Hello

First do not panic is not the fault of your script but for you experience with mi2s and partitions are the few people in the world that can save my phone.

I'm playing a game phone(Xiaomi m2s 16GB) hang and one or more partitions are corrupt (I think this is the problem). But all de documentation than i find to delete o edit partition not work. Fastboot rom installation all ok but always only start with white logo. Mirecovery works perfectly and CWM by ivan works but temporally with this command sudo fastboot boot recovery.img

This is the result of your script

check environment

/sbin/mount

/sbin/umount

/sbin/parted

/sbin/tune2fs

/sbin/e2fsck

dump old table

unmount partitions

umount: can't umount /system: Invalid argument

umount: can't umount /system1: No such file or directory

umount: can't umount /data: Invalid argument

umount: can't umount /data_root: Invalid argument

umount: can't umount /sdcard: Invalid argument

change partition table

parted: delete

parted: create

Error: Unable to satisfy all constraints on the partition.

Failed changing table

OTHER TEST

/dev/block # e2fsck -fDp /dev/block/mmcblk0p24

e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p24

/dev/block/mmcblk0p24:

The superblock could not be read or does not describe a correct ext2

filesystem. If the device is valid and it really contains an ext2

filesystem (and not swap or ufs or something else), then the superblock

is corrupt, and you might try running e2fsck with an alternate superblock:

e2fsck -b 8193 <device>

/dev/block # tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p24

tune2fs 1.41.14 (22-Dec-2010)

tune2fs: Bad magic number in super-block while trying to open /dev/block/mmcblk0p24

Couldn't find valid filesystem superblock.

I try to delete partition and create a new one but fail.

(parted) rm 24

rm 24

(parted) mkpartfs primary ext2 872 1409

mkpartfs primary ext2 872 1409

Error: Unable to satisfy all constraints on the partition.

I FOUND THIS IN XDA FORUM BUT I HAVEN'T IMAGE TO TEST

adb push mmcblk0p19_repaired.img /tmp/

adb shell dd if=/tmp/mmcblk0p19_repaired.img of=/dev/block/mmcblk0p19

adb reboot bootloader

MY PARTITION TABLE SYSTEM1 NOT HAVE FILESYSTEM EXT4

tasadar@voyagerB:~/Escritorio/recovery$ sudo adb shell parted -s /dev/block/mmcblk0 print

Model: MMC SEM16G (sd/mmc)

Disk /dev/block/mmcblk0: 15.8GB

Sector size (logical/physical): 512B/512B

Partition Table: gpt

Number Start End Size File system Name Flags

1 17.4kB 89.1MB 89.1MB fat16 modem

2 89.1MB 178MB 89.1MB fat16 modem1

3 178MB 179MB 524kB sbl1

4 179MB 179MB 524kB sbl2

5 179MB 180MB 1049kB sbl3

6 180MB 181MB 1049kB rpm

7 181MB 182MB 1049kB tz

8 182MB 183MB 524kB DDR

9 183MB 187MB 4194kB aboot

10 187MB 188MB 1049kB misc

11 188MB 191MB 2990kB logo

12 191MB 192MB 799kB m9kefs1

13 192MB 193MB 799kB m9kefs2

14 193MB 193MB 1024B m9kefsc

15 193MB 201MB 8501kB bk1

16 201MB 202MB 799kB m9kefs3

17 202MB 268MB 66.3MB bk2

18 268MB 284MB 15.7MB boot

19 284MB 300MB 15.7MB boot1

20 300MB 316MB 15.7MB recovery

21 316MB 327MB 11.5MB bk3

22 327MB 336MB 8389kB ext4 persist

23 336MB 872MB 537MB ext4 system

24 872MB 1409MB 537MB system1

25 1409MB 1812MB 403MB ext4 cache

26 1812MB 5570MB 3758MB ext4 userdata

27 5570MB 15.8GB 10.2GB ext4 storage