Bricked Mi3 (wcdma Version)

Discussion in 'Xiaomi Mi 3' started by Bart4Fun, May 12, 2015.

  1. Bart4Fun

    Bart4FunMembers

    Aug 15, 2014
    2
    0
    11
    I have a Mi3 16GB WCDMA version that quit on me last week Friday.

    It seems that some partitions are corrupted and the phone hangs at start up. I have tried starting system 1/2, wipe & factory reset, flashing another rom using MiFlash tool (which results in an error). So I am getting pretty desparate.

    From adb, I got maybe some useful info (see below)? It would be nice if someone can post the outputs of the same commands in adb that I executed so I have a reference to work on.

    Does anyone know whether this is a hardware or software related issue?

    df command:
    Code:
    root@cancro:/ # df
    df
    df
    Filesystem              Size    Used    Free  Blksize
    /dev                  800.0M  132.0K  799.9M  4096
    /sys/fs/cgroup        910.2M    0.0K  910.2M  4096
    /mnt/asec              910.2M    0.0K  910.2M  4096
    /mnt/obb              910.2M    0.0K  910.2M  4096
    /system                629.5M  597.2M    32.3M  4096
    /data                  128.0M    43.9M    84.1M  4096
    /cache                377.8M    8.6M  369.2M  4096
    /persist                15.7M    4.1M    11.6M  4096
    /firmware              64.0M    52.4M    11.6M  16384
    /mnt/shell/emulated    78.0M    43.9M    34.1M  4096
    /storage/emulated/legacy    78.0M    43.9M    34.1M  4096
    root@cancro:/ #
    mounts:
    Code:
    shell@android:/ $ cat /proc/mounts
    cat /proc/mounts
    rootfs / rootfs rw 0 0
    tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=819200k,nr_inodes=175216,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,size=932060k,nr_inodes=175216,mode=750,gid=1000 0 0
    none /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
    tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=932060k,nr_inodes=175216,mode=755,gid=1000 0 0
    tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=932060k,nr_inodes=175216,mode=755,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
    shell@android:/ $
    dmesg grepped for errors:
    Code:
    root@cancro:/ # dmesg| grep error
    dmesg| grep error
    <6>[    0.004156] C0 [      swapper/0, 1] Configuring XPU violations to be fatal errors
    <3>[    0.138890] C0 [    kworker/0:1, 23] msm_thermal:msm_thermal_get_freq_table error reading cpufreq table
    <4>[    0.463490] C1 [      swapper/0, 1] mdss_dsi_ctrl: probe of fd922e00.qcom, mdss_dsi failed with error 31
    <3>[    0.495283] C1 [      swapper/0, 1] spi_qsd f9966000.spi: msm_spi_request_gpios: gpio_request for pin 56 failed with error -16
    <3>[    0.495299] C1 [      swapper/0, 1] spi_master spi7: spi_device register error /soc/spi@f9966000/epm-adc@0
    <3>[    3.869948] C0 [        mmcqd/0, 166] end_request: I/O error, dev mmcblk0,sector 25166600
    <3>[    3.869959] C0 [        mmcqd/0, 166] Buffer I/O error on device mmcblk0p28, logical block 2621537
    <4>[    3.869966] C0 [        mmcqd/0, 166] lost page write due to I/O error on mmcblk0p28
    <3>[    3.869984] C0 [        mmcqd/0, 166] end_request: I/O error, dev mmcblk0, sector 25166648
    <3>[    3.869992] C0 [        mmcqd/0, 166] Buffer I/O error on device mmcblk0p28, logical block 2621543
    <4>[    3.869999] C0 [        mmcqd/0, 166] lost page write due to I/O error on mmcblk0p28
    <3>[    3.870013] C0 [        mmcqd/0, 166] Buffer I/O error on device mmcblk0p28, logical block 2621544
    <4>[    3.870020] C0 [        mmcqd/0, 166] lost page write due to I/O error on mmcblk0p28
    <3>[    3.870037] C0 [        mmcqd/0, 166] end_request: I/O error, dev mmcblk0, sector 25166672
    <3>[    3.870045] C0 [        mmcqd/0, 166] Buffer I/O error on device mmcblk0p28, logical block 2621546
    <4>[    3.870052] C0 [        mmcqd/0, 166] lost page write due to I/O error on mmcblk0p28
    <3>[    3.870068] C0 [        mmcqd/0, 166] end_request: I/O error, dev mmcblk0, sector 25167296
    <3>[    3.870076] C0 [        mmcqd/0, 166] Buffer I/O error on device mmcblk0p28, logical block 2621624
    <4>[    3.870082] C0 [        mmcqd/0, 166] lost page write due to I/O error on mmcblk0p28
    <3>[    3.870098] C0 [        mmcqd/0, 166] end_request: I/O error, dev mmcblk0, sector 25170736
    <3>[    3.870106] C0 [        mmcqd/0, 166] Buffer I/O error on device mmcblk0p28, logical block 2622054
    <4>[    3.870112] C0 [        mmcqd/0, 166] lost page write due to I/O error on mmcblk0p28
    <3>[    3.870128] C0 [        mmcqd/0, 166] end_request: I/O error, dev mmcblk0, sector 25171128
    <3>[    3.870136] C0 [        mmcqd/0, 166] Buffer I/O error on device mmcblk0p28, logical block 2622103
    <4>[    3.870144] C0 [        mmcqd/0, 166] lost page write due to I/O error on mmcblk0p28
    <3>[    3.870160] C0 [        mmcqd/0, 166] end_request: I/O error, dev mmcblk0, sector 25171352
    <3>[    3.870177] C0 [        mmcqd/0, 166] end_request: I/O error, dev mmcblk0, sector 25172976
    <3>[    3.870194] C0 [        mmcqd/0, 166] end_request: I/O error, dev mmcblk0, sector 25428232
    <3>[    3.870212] C0 [        mmcqd/0, 166] end_request: I/O error, dev mmcblk0, sector 25428312
    <3>[    3.870523] C1 [          init, 184] EXT4-fs (mmcblk0p28): error loading journal
    <3>[    4.198335] C1 [          init, 184] EXT4-fs (mmcblk0p28): error loading journal
    <6>[    4.749268] C0 [      swapper/0, 0] pil-q6v5-lpass fe200000.qcom,lpass: Subsystem error monitoring/handling services are up
    <6>[    6.524327] C0 [      swapper/0, 0] pil_pronto fb21b000.qcom,pronto: Subsystem error monitoring/handling services are up
    <6>[    6.605197] C0 [      swapper/0, 0] pil-q6v5-mss fc880000.qcom,mss: Subsystem error monitoring/handling services are up
    <3>[    7.100125] C0 [    mediaserver, 239] msm_routing_get_dolby_dap_param_to_get_control, port_id not set, returning error
    <3>[  10.055051] C0 [        mmcqd/0, 166] error 0 requesting status 0x80900
    <3>[  10.109596] C0 [        mmcqd/0, 166] error 0 requesting status 0x80900
    <3>[  10.109614] C0 [        mmcqd/0, 166] end_request: I/O error, dev mmcblk0, sector 3706880
    <3>[  28.952221] C0 [      swapper/0, 0] adm_callback: cmd = 0x10335 returned error = 0x2
    root@cancro:/ #
     
  2. Acid

    AcidScripting Ninja
    Staff Member

    Aug 20, 2011
    2,726
    743
    245
    Male
    Yea the /data partition is screwed. 128M...

    Wysłane z MI Note
     
  3. shell

    shellMembers

    Apr 28, 2014
    11
    1
    13
    Male
  4. Corbe

    CorbeMembers

    May 19, 2015
    8
    0
    11
    i have the same problem , i tried almost all but no sucess.Everytime get unlabelet partition label. Any solution????
     
  5. Corbe

    CorbeMembers

    May 19, 2015
    8
    0
    11
    recreate partition tutorial on Xiaomi Mi3???
     
  6. Bart4Fun

    Bart4FunMembers

    Aug 15, 2014
    2
    0
    11
    This is the partition information of a good phone:

    Code:
    root@android:/ # cat /proc/partitions
    cat /proc/partitions
    major minor  #blocks  name
    
     179        0   15388672 mmcblk0
     179        1       2031 mmcblk0p1
     179        2       1024 mmcblk0p2
     179        3       1024 mmcblk0p3
     179        4       1024 mmcblk0p4
     179        5       1024 mmcblk0p5
     179        6       1024 mmcblk0p6
     179        7       4096 mmcblk0p7
     179        8       5120 mmcblk0p8
     179        9       4096 mmcblk0p9
     179       10       8192 mmcblk0p10
     179       11      36864 mmcblk0p11
     179       12       1536 mmcblk0p12
     179       13       1536 mmcblk0p13
     179       14          1 mmcblk0p14
     179       15      62463 mmcblk0p15
     179       16       1536 mmcblk0p16
     179       17      31232 mmcblk0p17
     179       18      32768 mmcblk0p18
     179       19      16384 mmcblk0p19
     179       20      16384 mmcblk0p20
     179       21      16384 mmcblk0p21
     179       22      16384 mmcblk0p22
     179       23      65536 mmcblk0p23
     179       24      65536 mmcblk0p24
     179       25     655360 mmcblk0p25
     179       26     655360 mmcblk0p26
     179       27     393216 mmcblk0p27
     179       28   13291503 mmcblk0p28
     179       32        512 mmcblk0rpmb
    root@android:/ # cat /proc/mounts
    cat /proc/mounts
    rootfs / rootfs rw 0 0
    tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=819200k,nr_inodes=175216,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,size=932060k,nr_inodes=175216,mod
    e=750,gid=1000 0 0
    none /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
    tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=932060k,nr_inodes=175216,mode=75
    5,gid=1000 0 0
    tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=932060k,nr_inodes=175216,mode=755
    ,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
    root@android:/ #
    
    The mounts of my faulty phone are already listed above. The partitions of my faulty phone are:
    Code:
     
    root@android:/ # cat /proc/partitions
    cat /proc/partitions
    major minor  #blocks  name
    
     179        0   15388672 mmcblk0
     179        1       2031 mmcblk0p1
     179        2       1024 mmcblk0p2
     179        3       1024 mmcblk0p3
     179        4       1024 mmcblk0p4
     179        5       1024 mmcblk0p5
     179        6       1024 mmcblk0p6
     179        7       4096 mmcblk0p7
     179        8       5120 mmcblk0p8
     179        9       4096 mmcblk0p9
     179       10       8192 mmcblk0p10
     179       11      36864 mmcblk0p11
     179       12       1536 mmcblk0p12
     179       13       1536 mmcblk0p13
     179       14          1 mmcblk0p14
     179       15      62463 mmcblk0p15
     179       16       1536 mmcblk0p16
     179       17      31232 mmcblk0p17
     179       18      32768 mmcblk0p18
     179       19      16384 mmcblk0p19
     179       20      16384 mmcblk0p20
     179       21      16384 mmcblk0p21
     179       22      16384 mmcblk0p22
     179       23      65536 mmcblk0p23
     179       24      65536 mmcblk0p24
     179       25     655360 mmcblk0p25
     179       26     655360 mmcblk0p26
     179       27     393216 mmcblk0p27
     179       28   13291503 mmcblk0p28
     179       32       4096 mmcblk0rpmb
    root@android:/ #
    
    The only difference is the last one, but I suspect that only the filesystem may be corrupted
     
  7. Corbe

    CorbeMembers

    May 19, 2015
    8
    0
    11
    well tutorial of recreation partitions on Xiaomi MI3 will be nice!!!
     
  8. Be6i4

    Be6i4Members

    Nov 19, 2012
    9
    2
    15
    Male
    A guy brought such a phone to me maybe a six months ago and I couldn't fix it at that time, so he sent the phone back to *******.com and I think that they have replaced his phone with a new one.
     

Share Our Site