Unable to boot to system after flashing roms

[hollyrogers123]

Hi,

Just got my Mi4c and I was able to flash my recovery to TWRP by (ketut.kumajaya's twrp-3.0.2-0-libra-aqua-20161007.img). From there, I wiped all partitions and uploaded roms (MTP) for installation. However, when installing a rom, the installation finishes without errors but reboot always takes me back to TWRP. I've tried ketut.kumajaya's cm13, xiaobai112220's cm12.1 and AndropaX's Resurrection Remix N but the same thing happens. Under the mount menu System is unchecked.

Does anyone have a clue as to what the problem is, or any suggestions on how to debug the issue?

Any help is appreciated. Thank you!

 

[Sakura_Sa233]

Hi,

Just got my Mi4c and I was able to flash my recovery to TWRP by (ketut.kumajaya's twrp-3.0.2-0-libra-aqua-20161007.img). From there, I wiped all partitions and uploaded roms (MTP) for installation. However, when installing a rom, the installation finishes without errors but reboot always takes me back to TWRP. I've tried ketut.kumajaya's cm13, xiaobai112220's cm12.1 and AndropaX's Resurrection Remix N but the same thing happens. Under the mount menu System is unchecked.

Does anyone have a clue as to what the problem is, or any suggestions on how to debug the issue?

Any help is appreciated. Thank you!

How about flashing a miui rom by using computer and flash again or change a TWRP？

 

[hollyrogers123]

How about flashing a miui rom by using computer and flash again or change a TWRP？

Thanks for the suggestions.

I decided to try another TWRP first since it was the simpler of the two. I fastboot boot-ed an older version of TWRP (3.0.0) and then **** happened =(

When TWRP loaded, the touchscreen did not work. I reset the phone then to my surprise and excitement the CM alien appeared. But that was short-lived because after the rom fully loaded up the touchscreen still wasn't working and I am now stuck in the CM welcome screen (Power, Vol up and down buttons do). It seems like the touchscreen is now completely broken and no amount of resetting and re-flashing recovery would fix it.

Anyone have ideas for my current situation? T.T I'll probably be trying to get back to stock recovery to see if that helps at all

 

[Cozzmy13]

Don't panic, touchscreen should work inside the recovery after 5-10 minutes.
I suggest flashing TS TWRP, though.
http://www.teamsuperluminal.org/ts-twrp-2-8-7-2-mi4c/

 

[hollyrogers123]

Don't panic, touchscreen should work inside the recovery after 5-10 minutes.
I suggest flashing TS TWRP, though.

Having gotten over the initial shock of possibly losing $100 in record time, I'm strangely calm and hardly hopeful at this point.

After leaving the phone for the night, the touchscreen never did return. I put the phone in EDL mode and MiFlash-ed it hoping to return to stock (libra_images_V7.1.4.0.LXKCNCK_20151209.0000.6_5.1_cn), to which MiFlash reported successful but the screen never lit up. The last few lines of the log are as follows:

[00000C60]COM10	131.68	ApplyPatch sector 12, offset 424, value NUM_DISK_SECTORS-34., size 8
[00000C60]COM10	131.68	ApplyPatch sector NUM_DISK_SECTORS-23., offset 424, value NUM_DISK_SECTORS-34., size 8
[00000C60]COM10	131.68	ApplyPatch sector 1, offset 48, value NUM_DISK_SECTORS-34., size 8
[00000C60]COM10	131.68	ApplyPatch sector NUM_DISK_SECTORS-1., offset 48, value NUM_DISK_SECTORS-34., size 8
[00000C60]COM10	131.70	ApplyPatch sector 1, offset 32, value NUM_DISK_SECTORS-1., size 8
[00000C60]COM10	131.70	ApplyPatch sector NUM_DISK_SECTORS-1., offset 24, value NUM_DISK_SECTORS-1., size 8
[00000C60]COM10	131.70	ApplyPatch sector NUM_DISK_SECTORS-1, offset 72, value NUM_DISK_SECTORS-33., size 8
[00000C60]COM10	131.70	ApplyPatch sector 1, offset 88, value CRC32(2,5632), size 4
[00000C60]COM10	131.70	ApplyPatch sector NUM_DISK_SECTORS-1., offset 88, value CRC32(NUM_DISK_SECTORS-33.,5632), size 4
[00000C60]COM10	131.71	ApplyPatch sector 1, offset 16, value 0, size 4
[00000C60]COM10	131.71	ApplyPatch sector 1, offset 16, value CRC32(1,92), size 4
[00000C60]COM10	131.71	ApplyPatch sector NUM_DISK_SECTORS-1., offset 16, value 0, size 4
[00000C60]COM10	131.73	ApplyPatch sector NUM_DISK_SECTORS-1., offset 16, value CRC32(NUM_DISK_SECTORS-1.,92), size 4
[00000C60]GetFactoryObject(1457): The specified service does not exist.(0x800704db)
[00000C60]SaveFlashResult(1478): The specified service does not exist.(0x800704db)

More than touchscreen, I've lost the entire display now. In its bricked state, the phone is most of the time undetected by the computer, and enters EDL mode only when it feels like. I've since been plugging and unplugging the phone hoping to catch it in that state again.

Thanks for the suggestion. Will give TS's TWRP a try if I can ever get the device to fastboot again.

 

[Cozzmy13]

...

So, you only have edl now and it mostly doesn't work.
Does MiFlash detect the phone at least sometimes?
Maybe your download was corrupted, did you check the checksum?
Do adb devices and fastboot devices right after you plug the phone in and check for any life signs.
Does the charging led appear when you plug the phone in?
Did you use Windows 32 bit for flashing? I see that being a problem around the forums.

Try this to enter EDL.

I found this:
You don't have to open phone to make shortcut.
1: Turn off your phone, (must be charged at least 30%)
2: plug cable usb to PC
3: after that it is coming a very FAST two movement: Plug USB to phone and then Vol+ together with Vol- till it blinks red LED.
I did it and it works!! After this you can install driver and recognise your COM port. (Do it with driver signature disabled)
Good Luck!!

I avoid flashing using utilities just because I don't know what incopetent monkey programmed it and how it might randomly destroy my phone.

It you can't fix it and you bought it from a good store, return it claiming that you were prompted to update your software and it never booted back up.

Good luck!

 

[hollyrogers123]

So, you only have edl now and it mostly doesn't work.
Does MiFlash detect the phone at least sometimes?
Maybe your download was corrupted, did you check the checksum?
Do adb devices and fastboot devices right after you plug the phone in and check for any life signs.
Does the charging led appear when you plug the phone in?
Did you use Windows 32 bit for flashing? I see that being a problem around the forums.

Try this to enter EDL.



I avoid flashing using utilities just because I don't know what incopetent monkey programmed it and how it might randomly destroy my phone.

It you can't fix it and you bought it from a good store, return it claiming that you were prompted to update your software and it never booted back up.

Good luck!

The md5 is correct.

Charging LED does not turn on.

fastboot and adb do not detect. lsusb sees it sometimes, most of the time the connection of the device makes lsusb hang with no output and immediately unfreeze the moment I unplug the device.

I'm using Windows 7 64-bit VM for MiFlash on a debian host.

Update:
Holding Vol+ and Vol- for about 1 minute DOES get the device edl!
But it seems the Linux host is causing problems when transferring the connection to the guest. Some qcserial process was using it and VMware disconnecting the device from it and connecting it in the Win 7 guest somehow screws it up. What I did ultimately:
1. Use the key combination to get the device into edl and detected by Linux
2. Connect device to the guest using VMware menu (and not work)
3. While device is connected to the guest, use the key combination to re-enter edl and this time it got detected in the Windows 7 guest!


Hopefully this helps someone who's facing the same issues with getting their device detected by VMs.

Managed to re-flash but I'm still stuck with the same black screen unfortunately.

Thank you once again!

 

[Cozzmy13]

Managed to re-flash but I'm still stuck with the same black screen unfortunately.

What did you flash this time?

Can you get into fastboot at least now?

 

[hollyrogers123]

What did you flash this time?

Can you get into fastboot at least now?

Not into fastboot. After the flashing completes successfully, I'm still unable to turn on the device, it seems to be stuck in edl mode. I've tried:
Lastest China Dev libra_images_6.12.1_20161201.0000.00_5.1_cn
Lastest China Stable libra_images_V8.1.2.0.LXKCNDI_20161120.0000.00_5.1_cn
and an older version libra_images_V7.1.4.0.LXKCNCK_20151209.0000.6_5.1_cn

 

[Cozzmy13]

Not into fastboot. After the flashing completes successfully, I'm still unable to turn on the device, it seems to be stuck in edl mode. I've tried:
Lastest China Dev libra_images_6.12.1_20161201.0000.00_5.1_cn
Lastest China Stable libra_images_V8.1.2.0.LXKCNDI_20161120.0000.00_5.1_cn
and an older version libra_images_V7.1.4.0.LXKCNCK_20151209.0000.6_5.1_cn

I really don't know what could you do next..

 

[weter11]

You need trying install all from beginning.
Sorry, but you trying to install versions, that only compatible with devices, that was unlocked from xiaomi site. There a good instruction, but on Russian language. I also had a device with version that is newer than that version from witch you can unlock bootloader.
Try to install first version before 6.1.14 China.

1. Fastboot on phone.
2. Download any firmware before 6.1.14.
3. Unpack tgz and gz on PC.
4. Execute miflash.
5. Connect phone to PC.
6. miflash - Browse - folder with unpacked firmware - Refresh.
7. Choose flash all except data and storage
8. After uploading device reboot itself.
Next install custom recovery
1. fastboot on device.
2. Download TWRP 2.8.7.1 For MI4C EN v2.7z. In future you can upgrade it to 3.0.2.0, but special for Mi4c.
3. Open archive.
4. Connect phone to PC.
5. Open terminal from admin and execute recovery.bat from archive.
6. Simply press enter in terminal.
7. After all terminal itself would close and phone go to recovery.
PS: wait few minutes, its a problem with this version TWRP.

Maybe this can help you. Sorry my English far from good.

 

[hollyrogers123]

You need trying install all from beginning.
Sorry, but you trying to install versions, that only compatible with devices, that was unlocked from xiaomi site. There a good instruction, but on Russian language. I also had a device with version that is newer than that version from witch you can unlock bootloader.
Try to install first version before 6.1.14 China.

1. Fastboot on phone.
2. Download any firmware before 6.1.14.
3. Unpack tgz and gz on PC.
4. Execute miflash.
5. Connect phone to PC.
6. miflash - Browse - folder with unpacked firmware - Refresh.
7. Choose flash all except data and storage
8. After uploading device reboot itself.
Next install custom recovery
1. fastboot on device.
2. Download TWRP 2.8.7.1 For MI4C EN v2.7z. In future you can upgrade it to 3.0.2.0, but special for Mi4c.
3. Open archive.
4. Connect phone to PC.
5. Open terminal from admin and execute recovery.bat from archive.
6. Simply press enter in terminal.
7. After all terminal itself would close and phone go to recovery.
PS: wait few minutes, its a problem with this version TWRP.

Maybe this can help you. Sorry my English far from good.

Thank you for your input.

I tried libra_images_6.1.7_20151221.0000.11_5.1_cn_b09dac70a0 but after flashing the same thing happens. The screen remains black and I cannot get it to fastboot at all.

 

[weter11]

Can you first access to twrp and restore stock firmware?
If not people wrote that the best firmware to unlock bootloader is 6.5.24 cn-en for fastboot. Maybe now it help. Try to install this version.

 

[tom81042]

Thank you for your input.

I tried libra_images_6.1.7_20151221.0000.11_5.1_cn_b09dac70a0 but after flashing the same thing happens. The screen remains black and I cannot get it to fastboot at all.

what you need is an older mi flash, 2015 Jun or something, that works! (with an official old fb rom)
And don't even think about flash all except storage! just flash ALL!! Then let the phone boot fully at least once.
also, when ib edl mode (press vol- and power for a looonf time) or in fastboot mode you need to plug the phone to a computer with usb cable - try to put it in a different usb port, and different good quality cable is a must! once in edk or fb, you must open command prompt and type: fastboot devices - or press refresh in miflash, otherwise the phone won't stay in those states!

If you can't fix it with all this help found on Internet, then it must be hardware error!

oh, and golden f rule n1: - After flashing twrp always boot from it too! 1. fastboot flash recovery twrp. img
2. fastboot boot twrp.img
3. then un twrp reboot to recovery

 

[nhkhanh068]

i recently have same issue like you, i try to flash many rom and new room via fastboot, but realize that after flash rom via twrp, just boot to fastboot then reboot and you will boot to system
sry for my bad english