yashsingh1/xdaforums huggingface dataset:
[X 2014 Q&A, Help & Troubleshooting] UncleMike:
I'm pretty sure it's a manual process on their end, so I wouldn't expect anything until at least regular office hours in their hq time zone.
[X 2014 Q&A, Help & Troubleshooting] AGISCI:
Usually it's within 24 hours.
[X 2014 Q&A, Help & Troubleshooting] Jostian:
Yip, normally quite fast.
[X 2014 Q&A, Help & Troubleshooting] theoblackhawk:
Sorry, but how can one download an official stock firmware from Motorola's Google drive?
[X 2014 Q&A, Help & Troubleshooting] spartanhooah:
One of the pages in the process of getting your unlock code has a link to the firmware downloads.

Also, my request was granted yesterday.
[X 2014 Q&A, Help & Troubleshooting] pen_sil:
first request i didn't get anything from motorola.

then i requested again, after 15minutes i got email from motorola
[Galaxy S II Q&A, Help & Troubleshooting] tom790:
When I updated Cyanogenmod to CM13 my recovery stopped working (I turned on "update recovery with system"). I didn't can apply ANY updates from SD card and from PHONE STORAGE too.

To fix it I tried to update CM to 13 from 10-02-2016 to 13-02-2016. But... It didnt ANYTHING happened! It was only black screen. But now I can't turn on my phone! Recovery mode is not turning on too! I have only not working phone with not working recovery when it will turn on too!

I need my phone tomorrow, please, HELP ME! What can I do?!

Recovery: CM13 recovery.

It is not bootloop, I have:

BLACK SCREEN

After Samsung logo.

It is very important, does somebody know what to do?

I have new news:

After turning on I have samsung logo and for about one second Updating System message! Without loading bar :(. After it of course black screen!

I didn't do any backups of my phone, but I can wipe all data, but I NEED WORKING PHONE!
[Galaxy S II Q&A, Help & Troubleshooting] noppy22:
[MENTION=7280232]tom790[/MENTION]

Try flashing this kernel I attached with odin. Next try rebooting to recovery. If you get a working TWRP recovery, then flash the rom you want to use as normal. Please read this guide if you want to use CM13 and avoid common issues.
[Galaxy S II Q&A, Help & Troubleshooting] matee89:
Same problem here after trying to update to the newest nightly (also with "update recovery with system" on in developer settings) I assume that this function isn't working correctly. The only alternative is as mentioned above - flash kernel+recovery with Odin and make changes afterwards.
[Galaxy S II Q&A, Help & Troubleshooting] haldo06:
I have same problem. I tried to install this kernel above with ODIN but no luck, after sucessful flash logo and black screen. Any other advice or tips? Is there any chance to recover some data from internal card?
[Galaxy S II Q&A, Help & Troubleshooting] 8xiom:
And exactly the same issue here. Will try the workaround from the first answer by noppy22.

OK, succeeded. I used ODIN with the kernel tar file from noppy22, put the S2 into download mode (that was still possible, recovery mode couldn't be accessed), flashed the kernel. Phone rebooted automatically into recovery and started (continued?!) with the installation of CM 13.0. And here I realize the issue. The OTA was the nightly of CM 13.0 which I inadvertently chose to be flashed over the running CM 12.1. Bad idea!

Caveats: I see the yellow triangle now which didn't show up before. No problem for me - it's more than 4.5 years old. And there is still the error that "Google play service was terminated" which showed before I triggered the OTA update of CM 12.1.
[Xiaomi Mi 4C] AndropaX:
Team Win Recovery Project

WHAT IS TWRP?

Oh come on, you know what it is - don't try to fool me!

In case you're serious, though...

Team Win Recovery Project is a custom recovery for Android devices.

It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.

Read more about TWRP here: https://twrp.me/about/

DOWNLOAD:

1) Install the TWRP app from the Play Store or grab the apk from our website

2) Open the app, agree to the terms, and enable root access

3) Select TWRP Flash

4) Search for your device and select the version you wish to download

5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery

OR:

Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed

1) Download the latest version from our website on your device

2) Reboot to TWRP

3) Hit Install and tap the "Images..." button in the lower right

4) Browse to the location of the TWRP image on your device and select it

5) Select recovery from the partition list and swipe to flash

OR:

You can find more information and download links on our website.

FEATURES:

MTP support

ADB root

Built with android 7.1 tree

SUPPORT:

Live support is available via #twrp on Freenode with your IRC client or just click this link.

CONTRIBUTIONS:

Gerrit for TWRP: http://gerrit.omnirom.org/

Gerrit for officially supported devices: http://gerrit.twrp.me/

XDA:DevDB Information

[libra] TWRP 3.1, Tool/Utility for the Xiaomi Mi 4C

Contributors

AndropaX

Version Information

Status: Testing

Current Beta Version: 3.1.0-0

Beta Release Date: 2017-01-26

Created 2016-02-14

Last Updated 2017-03-10
[Xiaomi Mi 4C] dexxa05:
Hi,

Thx for the work and for the share i will test it !

;)
[Xiaomi Mi 4C] solis_f:
Just tested. 5 min touch issue exists
[Xiaomi Mi 4C] AndropaX:
On my phone with latest dev working immediately after boot

Wysłane z mojego Mi-4c przy użyciu Tapatalka
[Xiaomi Mi 4C] solis_f:
Using 6.1.28 miui eu and it was not responding to touch. I flashed through recovery by cofface 2.8.7.0. How did you flash it?
[Xiaomi Mi 4C] AndropaX:
Through fastboot

Wysłane z mojego Mi-4c przy użyciu Tapatalka
[Xiaomi Mi 4C] solis_f:
Did you check with flashify?

---------- Post added at 12:18 AM ---------- Previous post was at 12:11 AM ----------

Tried with Rashr. Worked like a charm! Thanks a lot! :)
[Xiaomi Mi 4C] VENSTER:
flash with flashify, touch screen invaild。so, no more test
[Xiaomi Mi 4C] dexxa05:
Touche issue for me too ! Flashed with flashify.
[Xiaomi Mi 4C] emfox:
Flashed with flashify, touch screen not work.
[Xiaomi Mi 4C] AndropaX:
I reflashed by flashify, and again touchscreen working. Try reflash with other method.

Wysłane z mojego Mi-4c przy użyciu Tapatalka
[Xiaomi Mi 4C] reddsmokee:
I reflashed with different methods but touch screen problem still exist.
[Xiaomi Mi 4C] AndropaX:
Strange...

Maybe try delete /sdcard/TWRP/.twrps
[Xiaomi Mi 4C] Deleted member 7244376:
touch issue still exists. flashing through fastboot and flashify - same result
[Xiaomi Mi 4C] fays91:
flashing through fastboot and flashify - same result
[Xiaomi Mi 4C] creekerz:
same result for me, no screen touch
[Xiaomi Mi 4C] solis_f:
Use rashr it worked for me. Update over 2.8.7.0 from cofface
[Xiaomi Mi 4C] Sebbo06:
It doesn't work either :(
[Xiaomi Mi 4C] datagutt:
Since it only seems to work on some phones, maybe we have different touchscreen panels? I think adding the correct idc file for all panels would fix this :)
[Xiaomi Mi 4C] AndropaX:
After some dtb repacking and testing I think that this is caused by touchscreen firmware updating in first boot. In second it should work normally.

Wysłane z mojego Mi-4c przy użyciu Tapatalka
[Xiaomi Mi 4C] Sebbo06:
I tried this method, but it still doesn*t work for me.

I rebootet the phone three times after updating via flashify.
[Xiaomi Mi 4C] kevinnol:
Flashed it and had the touchscreen issue for a few minutes, after that nothing. No problems at all

Appreciate your work

*I deleted the twrp folder and used fastboot erase recovery just in case
[Xiaomi Mi 4C] Sebbo06:
Yes it worked now :)

I did the following:

1. Install [TOOL]Minimal ADB and Fastboot [8-28-15]6 and put the twrp.img from here in that folder

2. Run the Phone in fathboot mode

3. Open Minimal ADB and Fastboot

4. Type in: fastboot erase recovery

5. Type in: fastboot flash twrp.img

6. Reboot the phone by holding the power button for some seconds

7. Reboot into recovery and wait 3-5 minutes

8. Done :D

PS. Next reboot into recovery will be without any delay

Update: Delay is back, you have to wait about 1 min to be able to unlock the touch screen.
[Xiaomi Mi 4C] msdx123:
Could you push your device to Github plz?

I'm working on TWRP 3.0 too, but I face some problems with SElinux.

THX.
[Xiaomi Mi 4C] AndropaX:
I using alterbang device tree without any big changes.

Wysłane z mojego Mi-4c przy użyciu Tapatalka
[Xiaomi Mi 4C] Sebbo06:
Please check this out:

http://en.miui.com/forum.php?mod=viewthread&tid=228966&highlight=twrp

This worked for me without any bugs, no delay or something.

Just flash it via flashify.
[Xiaomi Mi 4C] AndropaX:
I updated kernel and dtb from newest mirecovery. This should fix that. Let' see for how long...
[Xiaomi Mi 4C] ermacwins:
http://www.teamsuperluminal.org/ts-twrp-3-0-0-0-recovery-for-xiaomi-mi4c/

I haven't tried it yet
[Xiaomi Mi 4C] msdx123:
Did you change anything about SElinux?

Cz in alterbang's device tree SElinux is disabled

But your recovery set SElinux to permissive.

Once I set SElinux to permissive, my TWRP could not boot.
[Xiaomi Mi 4C] mendocino_610:
I try a many many twrp build everytime touchscreen problem. this version too long touchscreen problem....
[Xiaomi Mi 4C] AndropaX:
If you have newest dev miui r2 version should normally work.

Wysłane z mojego Mi-4c przy użyciu Tapatalka
[Xiaomi Mi 4C] mendocino_610:
No still touch problem

Mi-4c cihazımdan Tapatalk kullanılarak gönderildi
[Xiaomi Mi 4C] fays91:
Hello always touch problem

The only recovery that does not have this problem and that of TS TEAM Version 2.8.7.3

their version 3.0.0.2 Touch prblème

why not this based on this 3.0.0.2 version fixed the bug
[Xiaomi Mi 4C] anandmore:
[MENTION=5868201]AndropaX[/MENTION]

Added to [INDEX] Xiaomi Mi 4C
[Xiaomi Mi 4C] cy-rock:
Perfect with CM12.1 and flashed using flashable zip from previous recovery 2.8
[Xiaomi Mi 4C] ketut.kumajaya:
[MENTION=5868201]AndropaX[/MENTION] I confirm touchscreen firmware "ping-pong" issue the source problem of TWRP touchscreen freeze on boot. If touchscreen driver found a different firmware version, it will flash a "proper" firmware and delayed touchscreen event initialization. Replace your TWRP kernel with my own normal boot kernel fix this issue.
[Xiaomi Mi 4C] AndropaX:
About which kernel do you say?

Wysłane z mojego Mi-4c przy użyciu Tapatalka
[Xiaomi Mi 4C] ketut.kumajaya:
My kernel version:

# cat /proc/version
Linux version 3.10.49-perf-gbd5d555-03937-g649baf6 (root@sq-offline-15436) (gcc version 4.9.x-google 20140827 (prerelease) (GCC) ) #1 SMP PREEMPT Thu Dec 3 23:41:23 CST 2015

from miui_MI4c_V7.1.6.0.LXKCNCK_1debc127a9_5.1.zip
[Xiaomi Mi 4C] Brunnys:
[MENTION=5868201]AndropaX[/MENTION] [MENTION=4021423]ketut.kumajaya[/MENTION]

So it is possible to have a TWRP 3.0 without touch problems? How can we make it?
[Xiaomi Mi 4C] ketut.kumajaya:
Not sure, this TWRP in-kernel touchscreen firmware known different to my normal boot firmware, touchscreen lag on boot because initial firmware flashing process. Two possible solution, change touchscreen driver probe order early or prevent touchscreen driver to flash a firmware update on recovery boot.

No TWRP problem for me, my normal boot and recovery boot will be always use same kernel, same in-kernel touchscreen firmware, no boot delay because of touchscreen firmware flashing process.
[Xiaomi Mi 4C] Ydraulikos:
Can you add F2FS support?
[Xiaomi Mi 4C] Urik26:
Oh yeah, it would be really cool!
[Xiaomi Mi 4C] AndropaX:
Soon:

-New source (6.0 and open kernel)

-New filesystems support (ntfs, f2fs)

-Fix otg

Wysłane z mojego Mi-4c przy użyciu Tapatalka
[Xiaomi Mi 4C] w1ll1m:
Will changing filesystem to f2fs wipe the internal storage?
[Xiaomi Mi 4C] AndropaX:
Changing filesystem always wipe whole partition.

Wysłane z mojego Mi-4c przy użyciu Tapatalka
[Xiaomi Mi 4C] fancccc:
Whats the point of f2fs anyway?
[Xiaomi Mi 4C] solis_f:
Faster I/O requests
[Xiaomi Mi 4C] ajitkatte:
Is touch screen issue still there?
[Xiaomi Mi 4C] TPMJB:
nevermind
[Xiaomi Mi 4C] polovinamozga:
Where is source code?
[Xiaomi Mi 4C] Anesteticus84:
Hi all,

link provided in the first post doesn't work anymore. Could you please help me?

Thanks
[Xiaomi Mi 4C] cobraplayer:
Look in the development forum. There is another thread which contains twrp 3.0.x for libra and aqua
[Xiaomi Mi 4C] amivoytec:
Are you a victim of non-working link? Go here --> http://xdaforums.com/mi-4c/development/recovery-recovery-built-source-t3352286
[Xiaomi Mi 4C] AndropaX:
Project is again live :

https://www.androidfilehost.com/?fid=529152257862699043

Latest TWRP 3.0.3, based on android 7.1 sources
[Xiaomi Mi 4C] Danny94:
Nice, thanks a lot master.
[Xiaomi Mi 4C] caxwan:
[MENTION=5868201]AndropaX[/MENTION] may you can rebuild with this info??

https://xdaforums.com/mi-4c/general/note-dev-information-nougat-t3545771

Twrp from this post can work in all rom also miui nougat..
[Xiaomi Mi 4C] dla5244:
TWRP 3.0.3.0 for all version

https://drive.google.com/open?id=0ByP6S_Z3vDjWY1hhdFhfdnhvVVU
[Xiaomi Mi 4C] arh91:
Bug

Reboot > Recovery.

It does not work, it gets stuck in the MI logo.
[Xiaomi Mi 4C] inafsuwanto:
yes not work, reboot > recovery, only blank screen
[Xiaomi Mi 4C] ViTAMiNCHEG:
Is Mi 4s supported?
[Xiaomi Mi 4C] arh91:
I installed the latest RR build with this recovery.

- Black screen when restarting the recovery.

- The smartphone was turned off by pressing the "Reboot System" button at the end of the installation.

- Right after that, when I turned on the smartphone, it went into recovery instead of starting the OS.

- After: Reboot> Shutdown... the system started normally.

I went back to the official recovery, and reinstalled the ROM.
[Xiaomi Mi 4C] ViTAMiNCHEG:
Working good on mi4s. Sd card supported
[Xiaomi Mi 4C] Guml3y:
It's work smoothly on AICP 20170126
[Xiaomi Mi 4C] Danny94:
For me this recovery works withouth problems ;D Good job!

I flashed with flashify.

Maybe you guys didn't unchecked the checkboxes at the screen after reboot. Was something like "install official twrp app".

Edit:

Nice, sdcard is shown now in the file manager. That was an annoying bug in the other recovery builds.

Everything fine ;D. Awesome!

Edit2:

No error note while installing nougat roms anymore.

And the progress bar is working too now ;D.

Thanks a lot AndropaX.
[Xiaomi Mi 4C] Palm Trees:
Try using Team Superluminal's TWRP version if you're having issues. That did the trick for me :)
[Xiaomi Mi 4C] BlackXhorneT:
No SD card access on Aqua, otherwise working as expected.

Rolling back to Kuma 3.0.2 for SD support for now.

Thanks
[Xiaomi Mi 4C] Kohba:
For me this recovery works withouth problems ;D Good job!:good:

I flashed with flashify.

:(I forgot to try OTG flash drive. Next time.

EDIT: So OTG works.

And even the backups are backward compatible with TWRP 3.0.2. Świetne robota.

Xiaomi Mi4c 2/16
[Xiaomi Mi 4C] Danny94:
Oh first bug i discovered.. "Reboot into recovery" doesn't work.
[Xiaomi Mi 4C] AndropaX:
twrp 3.1

https://www.androidfilehost.com/?fid=673368273298937346

For nougat bootloader (only ?)
[Xiaomi Mi 4C] prazola:
This is the result for me (AICP 03-09):

[root@X3370 mi4c]# fastboot boot TWRP-3.1.0-0-libra.img
downloading 'boot.img'...
OKAY [ 0.571s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.803s

How do I check my bootloader version?
[Xiaomi Mi 4C] Cozzmy13:
You just checked it. You have lollipop bootloader.
[Xiaomi Mi 4C] prazola:
How to update it to nougat?
[Xiaomi Mi 4C] mradermaxlol:
Umm... Are you sure it's really a *boot* image?
[Xiaomi Mi 4C] prazola:
Flashing recovery give the same result. Btw the img size is 17mb, when 3.0.3 is 50mb.

Edit: I just read AICP requires lollipop bl.
[Xiaomi Mi 4C] mradermaxlol:
I have flashed the update via TWRP 3.0.3 and everything's fine, the recovery's installed successfully, so the image is fine.
[Xiaomi Mi 4C] Uzuki:
Flashed twrp-3.1.0.0 from twrp-3.0.3-1, it works. Thank you
[Xiaomi Mi 4C] slimdick:
Here you have a working twrp 3.1 under the old bootlader from android 5.1.1

https://dl.twrp.me/libra/twrp-3.1.0-0-libra.img.html
[Xiaomi Mi 4C] LVroon:
Unfortunately it still have screen freeze bug
[Xiaomi Mi 4C] Vlad Paul:
Flashed from 3.0.3.0 the IMG of 3.1.0.0 recovery, all working fine. Perfectly. Thank you.
[Xiaomi Mi 4C] slimdick:
[MENTION=5868201]AndropaX[/MENTION]

Does this version 3.1.0-0 work adb backup?
[Xiaomi Mi 4C] t830mc:
Andropax, you are doing great work.

I've flashed TWRP 3.1.0 and everything works like a charm.

Since today I'm using system encryption, and there is no TWRP version that is able to mount encrypted partitions.

I'm offered to enter pattern in order to mount encrypted partitions, but I always get pattern failed error.

What am I doing wrong?
[Xiaomi Mi 4C] xyz43:
Data partition decryption does not work for me either with the same symptoms (I'm using passcode though). I spent some time trying to debug the issue and in recovery.log I found "could not open keymaster device in keystore (Operation not permitted)" message. I think it's related to the version of proprietary Qualcomm binaries (like qseecomd, libQSEEComAPI.so, keystore.msm8992.so, etc.), but updating them using blobs from the latest Nougat-based Xiaomi firmware did not solve the problem - with libraries updated there's no error, but TWRP kills the decryption process because of the timeout.

AndropaX, do you have any ideas what might be the cause of decryption issues?
[Xiaomi Mi 4C] miklo01:
Unfortunately doesn't work (with error message: CANNOT LINK EXECUTABLE "/system/bin/dex2oat": "/sbin/libcutils.so" is 64-bit instead of 32-bit)
[Xiaomi Mi 4C] Infernojz:
Hi, Are you interested in porting sailfish os for mi4c?
[Xiaomi Mi 4C] alexvv:
can i flash it on an unlocked 7.1 (miui) mi4c ?
[Xiaomi Mi 4C] Vlad Paul:
Of course.
[Xiaomi Mi 4C] miklo01:
Yes. You can.
[Xiaomi Mi 4C] alexvv:
thank you all, the commands should be, fastboot flash recovery.img and fastboot boot recovery.img ??
[Xiaomi Mi 4C] Vlad Paul:
Yes. And twrp IMG must be on fastboot directory
[Xiaomi Mi 4C] Cozzmy13:
[MENTION=5065300]alexvv[/MENTION]

Actually no.

fastboot flash recovery recovery.img

Cause fastboot doesn't read your thoughts.
[Xiaomi Mi 4C] Vlad Paul:
Sorry

TWRP 7.0 LIBRA https://www.androidfilehost.com/?fid=457095661767135741

fastboot flash recovery twrp.img

fastboot boot twrp.img
[Xiaomi Mi 4C] alexvv:
thank you
[Xiaomi Mi 4C] insomnia11:
So sorry for my stupid question, just still confused. My Mi force running in RR Latest build with twrp latest 3.1.0.1 if I want to move to custom rom based LP firmware (Aicp 12.1/Xosp/Vanir/Commotio/etc) is it will be safe by using twrp 3.1.0.1?? For LP firmware I was save it.

Sorry for my English & big thank's for any advice
[Xiaomi Mi 4C] Vlad Paul:
Nope. 3.1.0.1 is only for hipsters. Safe is 3.1.0.0 by [MENTION=5868201]AndropaX[/MENTION]
[Xiaomi Mi 4C] insomnia11:
Is it means will be safe with this step (full wipe except internal/flash LP firmware/rom/gapps then reb sys directly)?? Or I have to reflash twrp 3.1.0.0 before??

What do u means "3.1.0.1 is only for hipsters"??

Sorry for my many question, btw thanks for ur advice.
[Xiaomi Mi 4C] Maicka:
Hello !

It is possible to install ressurection remix 5.8.2 with this recovery without problem ? (actually cm13.1 superluminal.)

Thanks sorry for my bad english.
[Xiaomi Mi 4C] Aevum:
couldnt get it to work, installed from flashify, got a black screen when going to recovery, did a fastboot erase recovery, flashed from fastboot, no go.

went to 3.0.2.0 and im getting the touchscreen issue,
[Xiaomi Mi 4C] faighter:
Hi guys, I have issues with twrp 3.1.0.0. Touchscreen is not working. Any advice?

I'm download from TWRP-Libra
[Xiaomi Mi 4C] A1EXXX:
3.1.0-1, somthing is missing :mad:
[Xiaomi Mi 4C] jackint:
Do i have to unistall twrp first if i want to downgrade it to previous version, or i can overwrite existing one?
[Xiaomi Mi 4C] Adi393:
Override.
[Xiaomi Mi 4C] NotChinaMobiles:
I have a Problem with my Fastboot mode.

When i start fastboot with Volume down and Power button -> the Fastboot Mode start but disappears after a few seconds.

While the Fastboot logo is shown, i cant Fastboot devices

I tryed to flash a new TWRP via Flashify but that doesnt work. Now i cant boot anymore to recovery mode.

How can i get the Fastboot mode working again?

I realy dont understand what has happen
[Xiaomi Mi 4C] caxwan:
[MENTION=5868201]AndropaX[/MENTION].. thanks for bump version into 3.1.0-2 and also support for Nougat and Lollipop bootloader..

Update : Link
[Xiaomi Mi 4C] qwasy:
Does ADB Backup work?
[Xiaomi Mi 4C] flow2fly:
I am getting the following error

$ fastboot flash recovery TWRP-3.1.0-0-libra.img
target reported max download size of 536870912 bytes
sending 'recovery' (17292 KB)...
OKAY [ 0.570s]
writing 'recovery'...
OKAY [ 0.220s]
finished. total time: 0.790s
$ fastboot boot TWRP-3.1.0-0-libra.img
downloading 'boot.img'...
OKAY [ 0.565s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.796s

any idea?

---------- Post added at 11:18 PM ---------- Previous post was at 11:08 PM ----------

I found that this official version works:

https://dl.twrp.me/libra/

Official version 3.1.0-0 boots but has touchscreen issues.

---------- Post added at 11:28 PM ---------- Previous post was at 11:18 PM ----------

Finally got it running with

TWRP-3.1.0-2-libra-L.img

from the link above

I guess the link on page 1 needs to be updated.
[Xiaomi Mi 4C] PeterMarkoff:
just upgraded from TWRP 3.0.2.0 by Team Superluminal to TWRP 3.1.0.2 for Lollipop by AndropaX directly from inside old TWRP (flash image, recovery), no problem with touch
[Xiaomi Mi 4C] caxwan:
Thanks for update to TWRP 3.1.1-0 but just see for N bootloader only..

https://www.androidfilehost.com/?w=files&flid=149106&sort_by=date&sort_dir=DESC
[Xiaomi Mi 4C] fx3000se:
Slim6 doesn't boot

I am on TWRP 3.1.0-0:

I can install Marshmallow Slim6, BUT the ROM won't boot.

What could be the reason herefore? Is this TWRP related?

Note: I can install and boot RR N
[Xiaomi Mi 4C] fx3000se:
just tried to install RR M which didn't boot neither...
[Xiaomi Mi 4C] Cozzmy13:
Those ROMs are for lollipop bootloader, and you have nougat bootloader.
[Xiaomi Mi 4C] fx3000se:
Thx a lot.

Which TWRP would you recommend? TWRP-3.1.0-2-libra-L.img ?

Can I install the TWRP from within TWRP (recovery) through "Install image"?
[Xiaomi Mi 4C] Cozzmy13:
You need to downgrade the bootloader to use both the ROMs you mentioned and the TWRP you asked me now.
[Xiaomi Mi 4C] fx3000se:
how do I downgrade the bootloader (without locking it)?
[Xiaomi Mi 4C] Cozzmy13:
There's a thread in general section about unlocking bootloader without xiaomi verification, follow the steps and you'll get the same result

.
[Xiaomi Mi 4C] RMB666:
how do I use the OTA
[Xiaomi Mi 4C] slimdick:
[MENTION=5868201]AndropaX[/MENTION]

So this is the same twrp ? Same size. TWRP-3.1.1-0-libra-N.img = twrp-3.1.1-1-libra.img ??
[Xiaomi Mi 4C] AndropaX:
No, second one contains minor fixes.

Wysłane z mojego Mi-4c przy użyciu Tapatalka
[Xiaomi Mi 4C] nineteen86:
twrp-3.1.1-1-libra from the official site only for Nougat bootloader?
[Xiaomi Mi 4C] AndropaX:
Yes

Wysłane z mojego Mi-4c przy użyciu Tapatalka
[Xiaomi Mi 4C] slimdick:
[MENTION=5868201]AndropaX[/MENTION] huge thanks for the adb backup option ;)
[Xiaomi Mi 4C] PeterMarkoff:
3.1.0.2-L seem to have problem with Updater app in official Lineage OS 14.1 by Cozzmy13, I am using this TWRP version, downloaded and started to install from Updater, then it restarted to TWRP, nothing happened and end up in TWRP bootloop with this TWRP version as reported here:

https://xdaforums.com/showpost.php?p=72675107&postcount=389

seem people using 3.0.2 from TS don't have this issue on official LOS14.1 even when using Updater directly
[Xiaomi Mi 4C] Matt4670:
Hello everyone!

Does anyone know why there's so much difference in size between the last 2 versions?

twrp-3.1.1-1-libra.img	20.6M	2017-06-11 16:50:04 EDT

twrp-3.1.1-0-libra.img	48.6M	2017-05-17 18:42:45 EDT

Thanks
[Xiaomi Mi 4C] slimdick:
twrp-3.1.1-1-libra.img	20.6M	2017-06-11 16:50:04 EDT - 7.0 bootloader

twrp-3.1.1-0-libra.img	48.6M	2017-05-17 18:42:45 EDT - 5.1 bootloader