Database Info

unable to install twrp over 3.1.1.1 on mi4c (trying to go from android 7.1 to 8 or 9)

Hey everyone,
i usually don't post questions but i've been on pretty much every forum the web has to offer and am still stuck so i'll try my luck here.
i'm currently running lineage 7.1 on my mi4c, i've used another phone for a while but now that my mi4c has a new battery i wanted to start using it again, is also decided this would be the time to update it to android oreo or pie, this however seems to be impossible.
i can only use twrp up to 3.1.1.1, all higher (and unofficial versions) will not boot via fastboot 'dtb not found' or when flashed via older twrp will freeze on boot screen.
whenever i try to install a new rom it tells me 'error code 7', when i remove the 'assert' lines in the update it gives me 'error code 6'
my device is unlocked, i have checked this in fastboot.
do i have to install miui again before installing another rom? do i have to go back to the standard recovery? i'm currently running out of ideas and hope you guys might be able to help me. maybe i'm overlooking something simple.
kind regards,
Monstreys

Hi! I don't know if this is a coincidence or not, but I was about to start a similar thread.
I try to do exactly what you are doing. I want to install LineageOS 16, unofficial ROM.
For this you need a newer TWRP, like 3.2.3.0, but it doesn't work 'dtb not found' like you said. I found out that this doesn't work because you need to have nougat bootloader. Most probably you have lollipop bootloader like I have, and thats why newer versions of TWRP are not working. I think the only way to update your bootloader to a nougat one is to flash the latest MIUI ROM. But, unfortunately, when you do that the bootloader gets locked, and I can't unlock it via MiUnlock due to Error:20091 when I try to link the phone to the Mi account. In MiUnlock it gives me the "this account cannot unlock the phone" or something like that.
Now I removed the "assert" lines from my rom and flashed it without the error 7 or 6. Some error still apears, but it also apears when I flash LineageOS 14.1, and that version is working even with those 2 errors I can't remember during flash.
After I flashed LineageOS, I flashed gapps and then superSU, and now my mi4c is stuck on mi logo for about 20 minutes, and I think it will remain that way.
So, there are 2 things we need to solve. We need to find a way to install latest MIUI without relocking the bootloader because I can't unlock it via MiUnlock, or to find out why after I flashed LineageOS 16 it gets stuck on MI logo.

I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...

makaveli97 said:
I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...
Click to expand...
Click to collapse
i
i was unable to install the patch file, this nonetheless fixed my problem, thanks!!

if above not working, another method to do it based on my method.
https://forum.xda-developers.com/showpost.php?p=81573941&postcount=199

makaveli97 said:
I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...
Click to expand...
Click to collapse
My MI4C has been successfully flushed into lineage-17.1-20200220-UNOFFICIAL-libra.zip. It has been updated on TWRP 3.1.1 and keeps reporting error 7, and then abandoned TWRP3.1.1 and flashed into OrangeFox-R10.0-1-Stable-libra.zip After brushing libra-aqua_firmware_7.2.9.zip on this REC, you can flash lineage-17.1. I do n’t think it will be impossible to refresh because of partition problems. If you only need to upgrade lineage-17.1, you can refer to this method.:good::good:（Translation is not easy to use）

celrau said:
There is a 3.2.x around. If you don't want to bother go in the zip, /META-INF/com/google/android/ and delete the first lines (the ones starting with "assert") from updater-script, save and flash again.
Click to expand...
Click to collapse
rianawirawan said:
Right now, i'm using 3.1.1 -1 btw
It's latest twrp ver from official
Click to expand...
Click to collapse
TWRP-20190418-3.3.0.0-libra.img for the Xiaomi Mi 4c, by GuaiYiHu :
https://androidfilehost.com/?fid=1395089523397945946
Latest firmware for the Xiaomi Mi 4c libra :
https://github.com/XiaomiFirmwareUp...iui_MI4c_V10.1.1.0.NXKCNFI_13b9b312d0_7.0.zip

Android 11 (LineageOS 18.1) & TWRP

I installed LineageOS 18.1 (Android 11) on my OP7P and want to boot (or flash) TWRP.
There is a lot of different information about the state of TWRP on Android 11.
I hope someone could clearify the following questions:
1. Does TWRP [3.5.2] support Android 11?
the release notes of 3.5.1 state that they "prepared a mini release before Android-11 support."
The release notes of 3.5.2 don't mention android 11 at all.
There are various people in the LOS18.1 thread that can boot twrp, so I assume there is some kind of (partial) support.
2. What if 'fastboot boot twrp.img' doesn't work?
For me I can't boot (or flash) TWRP (on LOS18.1).
So as the twrp/lineage os guide says I do:
fastboot boot twrp.img
Click to expand...
Click to collapse
It finished succesfull, but my phone stays in fastboot and doesn't reboot.
The TWRP guide says the following:
If fastboot boot command doesn't work you need to root your device and flash the TWRP installer (remember that flashing the TWRP installer you will lose the root).
Click to expand...
Click to collapse
I find this a very vague description; what do they mean with "doesn't work"?
(when I flash twrp it results in an unbootable phone, might be related to a/b partitions, but I have not enough knowledge of that)
3. Does TWRP work on encrypted phones?
I found various posts that suggest that TWRP doesn't work on encrypted phones.
I can't find any reliable source that supports that statement.
Twrp says this, but that doesn't clearify things at all.
I hope someone could give me some answers, or guide me to some reliable source so I can find it myself.
I find the documentation of LineageOS and TWRP lacking in that perspective.

For question 1, there's no official TWRP for 11.... YET.
Question 2 - I'm thinking cause TWRP doesn't work for 11, that's your issue.
Besides that, if your trying Android 10(because you don't mention what version your using in question 2), I would suggest re downloading, as that process works fine for this phone I'm typing this reply to you on.
Question 3 - I'm sorry, I've got ideas, but it's above my pay grade... So no hard knowledge I'm comfortable calling advice, to give a fellow OP7P owner.

lenigma1too said:
For question 1, there's no official TWRP for 11.... YET.
Question 2 - I'm thinking cause TWRP doesn't work for 11, that's your issue.
Besides that, if your trying Android 10(because you don't mention what version your using in question 2), I would suggest re downloading, as that process works fine for this phone I'm typing this reply to you on.
Question 3 - I'm sorry, I've got ideas, but it's above my pay grade... So no hard knowledge I'm comfortable calling advice, to give a fellow OP7P owner.
Click to expand...
Click to collapse
I also think there is no official TWRP for android 11, but twrp doesn't make this very clear in their docs.
Multiple people are claiming they are able to (at least) boot twrp on Android 11.
LineageOS 18.1 is Android 11 (but I will clearify the post).
Thank you for your reply

there is now a working TWRP version for Android 11.
Nebrassy version: https://forum.xda-developers.com/t/recovery-11-unofficial-teamwin-recovery-project.4289455/
worked for me with 'fastboot boot TWRP-3.5.1-guacamole-Nebrassy-3.img'

[Oneplus 7 Pro] Soft bricking when upgrading/rooting

Hi,
After ignoring the notification to update to Android 11 for over a month, I finally gave in an tried the update today.
I normally run stock OOS ROM with TWRP and Magisk, and updates are always fairly simple, let the OS update, overwriting the recovery and losing root, plug in to the PC and just `fastboot boot` the TWRP image, and then flash TWRP and Magisk on the phone itself, and bobs your teapot.
Alas, Android 11 shat all over those plans. With all the news out about Android 12 being in Beta, I had forgotten that Android 11 was so new to OP7Pro. Correct me if I wrong, but TWRP doesn't seem to work, which was my first mistake, but now Magisk has moved to a "need to patch the boot.img" model, which I hadn't seen before?
Anyways, after attempting to patch my own boot.img, I can no longer boot anything; phone just gets past the bootloader unlocked warning, then reboots into recovery.
I panicked then and attempted to flash one of the flashable Android 10 images from Mauronofrio's thread, which I think made things worse; now it just reboots repeatedly.
Any help appreciated, thanks!

Woops, I actually have a Oneplus 7 Pro (not a 7T). Can I move a thread myself?
I managed to use the MSM Download Tool from the last time I bricked my phone, which got me back to a bootable Android 10. Not much worse in life than losing all my data but better than a brick.

mc_teo said:
Woops, I actually have a Oneplus 7 Pro (not a 7T). Can I move a thread myself?
(...)
Click to expand...
Click to collapse
You cannot
But we gladly do this for you (as I just did)! Remember that you can always report your own posts for any type of forum maintenance you may need.
At your service and stay safe!
Timmy
Forum Moderator

A fix for your failed patched boot.img is just flashing the stock boot.img.
For upgrading (official OTA) and keep root, after installation finishes don't reboot and go to magisk, select install to the inactive slot and reboot, after reboot your phone will have the lastest update without loosing root.
And the best way to restore your phone is using msmtool

Question Bricked trying to install LineageOS

Hello,
I have a moto G100 I just purchased. I unlocked the bootloader and I tried to install LineageOS but it was being difficult. I could get it to boot into TWRP. Now I tried to restore everything to stock as it wasn't even booting. After flashing the rom back in via fastboot the unit shows up as a serial device but that's it, no picture on the screen or anything.
I need some help to get this working again. Besides the directions on the LineageOS page sucks, steps are missing and things do not work properly.
Any help would be appreciated.
This is Qualcomm HS-USB QDLoader 9008 mode and won't boot.
Can anyone please help so this won't take weeks or months?
Thanks

Hello,
I fixed the brick with the blankflash file blankflash_nio_RRTS31.Q1-84-24-3-6
I was able to then use the official tool to recover the firmware. I was able to get LineageOS working but I wasn't able to do TWRP at all properly.

So I managed to install twrp but couldn't install lineage or anything out of it...

I managed to get TWRP installed but it was essentially useless as I couldn't access the internal flash unless it was setup by the OS already if you format the internal flash storage with TWRP it's useless especially via MTP.
I was able to install LineageOS and I was able to boot it, but I don't understand why it says I do not have enough space to install gapps. Without gapps LineageOS is essentially useless as an OS unless you do not use anything from google at all whatsoever not eve maps or anything.
How do I fix it so I can install gapps? I can't resize the system partition via TWRP as it doesn't even show it.
Thanks

if you have the bootloader unlocked you can try the "tinyflashscript" way and use that to overwrite all partitions with a stock image found here
RET stands for Retail and than the region code follows, just download the latest one for your region
after that your partitions are reset to the start and you could keep it that way or attempt to install lineage again but clean this time
I ran into the exact same situation as you with the storage issues and this fixed it for me

Hello my G100 was fully hard bricked trying to installed LineageOS (not the modded). I followed the following steps:
1. Installed and booted into LineageOS recovery from electimon.
2. Factory reset
3. Install ROM as adb sideload.
However, installation stuck at 47% and aborted. Phone was hard bricked once turned off. It couldn't even boot into booloader.
Luckily, I was able to enter EDL mode by pressing and holding volume and power down together for some time while it was plugged into PC using usb. Then I used blankflash to restore. This saved me from taking it to repair centre.

Hello,
I had the same brick issue and blankflash fixed it for me. I will try writing stock again then install LOSRecovery again and then try sideloading both LineageOS and gapps but I don't think that will work correctly as I think I did try that but we shall see, last time I did an install though after fixing the brick issue I used fastboot to do the stock recovery which should have fixed the partition sizes...
Thanks

It's strange that device becomes hard bricked because I installed LineageOS before and it booted fine. Only thing now changed is that I'm using February stock ROM instead of December one. Did Motorola change anything in Feb update that would cause hard brick when trying to install custom ROM?
Also, I've never did the "Ensuring all firmware partitions are consistent" thing. It worked before but not sure if we need to do it now.

Hello,
Strange indeed I can get LineageOS installed BUT because this is an A/B phone which is so silly, I can't install Gapps into LineageOS so essentially useless as the installer says the partition is too small and I do not have a way to fix that at the moment.
Thanks, and blankflash was able to get me up and running on stock but I cannot use the phone yet just like the DooGee S95 Pro I bought in hopes to use LineageOS... long story. Stuck with my ZTE Axon 7 from 2016 and a crap phone to make calls since my provider killed service to my ZTE Axon 7 so I carry basically 3 phones now. Until there is a fully working TWRP I am essentially screwed and feel like I wasted $400 on another phone.

marcusah123 said:
Hello,
Strange indeed I can get LineageOS installed BUT because this is an A/B phone which is so silly, I can't install Gapps into LineageOS so essentially useless as the installer says the partition is too small and I do not have a way to fix that at the moment.
Thanks, and blankflash was able to get me up and running on stock but I cannot use the phone yet just like the DooGee S95 Pro I bought in hopes to use LineageOS... long story. Stuck with my ZTE Axon 7 from 2016 and a crap phone to make calls since my provider killed service to my ZTE Axon 7 so I carry basically 3 phones now. Until there is a fully working TWRP I am essentially screwed and feel like I wasted $400 on another phone.
Click to expand...
Click to collapse
Using the method I described above I was able to install Lineageos 19.1 and then gapps (mindthegapps) using lineage recovery. it should be entirely possible

Hello,
With the storage not being large enough I was trying to install openGapps ( stock size ) for Android 11 since I was trying to use Lineage 18.1 and not 19/19.1 since 19/19.1 appear to have bugs and 18.1 does not. Anyhow I tried to sideload openGapps and it said there wasn't enough space on the system partition. I suppose I should try mindthegapps instead.
Thanks

So anyone successfully installed it without causing hardbrick? What exact steps did u follow? r u using g100 or edge s and what is the build number of stock rom prior to install? thanks

Windoors said:
So anyone successfully installed it without causing hardbrick? What exact steps did u follow? r u using g100 or edge s and what is the build number of stock rom prior to install? thanks
Click to expand...
Click to collapse
I used the latest stock after doing a recovery with blankflash and the rescue utility from Motorola. I then installed LOSrecovery because TWRP isn't ready. I then booted into LOSrecovery and sideloaded 19.1 latest from this forum. I can't figure out how to resize /system correctly so I cannot install anything other than MindTheGapps which sucks a lot.
Anyhow if we get a working TWRP soon that will allow resize as TWRP can't show the system partition and A/B switching is being worked out then we will be good to go.
If this isn't helpful or you need exact commands then I can do that too for you.

My story and a couple of questions

Hi All,
I have a new-to-me Oneplus 7 Pro. I have been trying to get Lineage with MicroG running. Well it has been quite the adventure and I have it to the point where I have Lineage running fine, and go to reflash TWRP and have bricked the phone, which takes a bit of time to get back to the point of having Linage running again. Specifics:
Lineage version: lineage-19.1-20221219-microG-guacamole.zip
TWRP Versions: I have found that twrp-3.6.1_11-0-guacamole.img works since my phone is at Android 11.
My questions are:
Are TWRP versions tied to Android versions?
When I am trying to get the last version of TWRP installed I have tried 2 approaches:
fastboot flash recovery
fastboot flash boot
Neither worked, phone always ends up bricked. I have used:
TWRP-3.5.1-guacamole-Nebrassy-3.img
twrp-3.6.1_11-0-guacamole.img
twrp-3.6.2_11-0-guacamole.img
I also have tried to boot the images 1st using: fastboot boot twrp-3.6.1_11-0-guacamole.img
and that bricks things.
What am I doing wrong?
Thanks
Ray

rbahr said:
Hi All,
I have a new-to-me Oneplus 7 Pro. I have been trying to get Lineage with MicroG running. Well it has been quite the adventure and I have it to the point where I have Lineage running fine, and go to reflash TWRP and have bricked the phone, which takes a bit of time to get back to the point of having Linage running again. Specifics:
Lineage version: lineage-19.1-20221219-microG-guacamole.zip
TWRP Versions: I have found that twrp-3.6.1_11-0-guacamole.img works since my phone is at Android 11.
My questions are:
Are TWRP versions tied to Android versions?
When I am trying to get the last version of TWRP installed I have tried 2 approaches:
fastboot flash recovery
fastboot flash boot
Neither worked, phone always ends up bricked. I have used:
TWRP-3.5.1-guacamole-Nebrassy-3.img
twrp-3.6.1_11-0-guacamole.img
twrp-3.6.2_11-0-guacamole.img
I also have tried to boot the images 1st using: fastboot boot twrp-3.6.1_11-0-guacamole.img
and that bricks things.
What am I doing wrong?
Thanks
Ray
Click to expand...
Click to collapse
If you look at the official installation page for your phone, you will see that Lineage OS 20 and 19.1 are supported. So you should reinstall Lineage OS 18.1 again, and then follow the steps on this page. Don't bother reinstalling GAPPS until after you upgrade it.
If for whatever reason you don't want an Android version higher than 11, let me know.

I specifically don't want GAPPS or anything remotely Google related. I had tried OS 20 and found that I had a problem installing apps - probably user error, but I don't need the latest and greatest. I am currently at Android 11.
I will read through the instructions, although the number of tutorials I have gone through is craze.
Can you tell me what the relationship between TWRP and Android version is, and are you able to sus out what I did wrong with my efforts to get TWRP loaded over the lineage 19 version I was using?
Thanks
Ray

rbahr said:
I specifically don't want GAPPS or anything remotely Google related. I had tried OS 20 and found that I had a problem installing apps - probably user error, but I don't need the latest and greatest. I am currently at Android 11.
I will read through the instructions, although the number of tutorials I have gone through is craze.
Can you tell me what the relationship between TWRP and Android version is, and are you able to sus out what I did wrong with my efforts to get TWRP loaded over the lineage 19 version I was using?
Thanks
Ray
Click to expand...
Click to collapse
rbahr said:
I have been trying to get Lineage with MicroG running
Click to expand...
Click to collapse
So I guess you don't want GAPPS, just MicroG. Definitely read through the instructions I gave you, as they are the official installation and upgrade instructions.
I would recommend installing Lineage OS 20, because it is the version that is being maintained right now.
I will attempt to guide you through the steps, but I need to know what your situation is right now: Is your bootloader unlocked? What OS do you have installed right now? What recovery are you using? etc.

I appreciate your help. Currently I am looking at a freshly updated phone with Android 11, and Oxygen 11.0.9.1.GM21AA.
The phone is a GM1917
Bootloader is unlocked and I am in developer mode. I have adb and fastboot loaded on my computer. I also have a working version of msm as I have bricked this thing 6 or 7 times...
Several times now, I have done the following:
Install TWRP
Install Lineage
Try and reflash TWRP <-- consistently fails at this point, gets stuck in a boot loop in the bootloader screen
Thanks
Ray

rbahr said:
I appreciate your help. Currently I am looking at a freshly updated phone with Android 11, and Oxygen 11.0.9.1.GM21AA.
The phone is a GM1917
Bootloader is unlocked and I am in developer mode. I have adb and fastboot loaded on my computer. I also have a working version of msm as I have bricked this thing 6 or 7 times...
Several times now, I have done the following:
Install TWRP
Install Lineage
Try and reflash TWRP <-- consistently fails at this point, gets stuck in a boot loop in the bootloader screen
Thanks
Ray
Click to expand...
Click to collapse
"Try and reflash TWRP" what do you mean, update the OS over TWRP?

I mean trying to re-install TWRP after installing Lineage

rbahr said:
I mean trying to re-install TWRP after installing Lineage
Click to expand...
Click to collapse
OK. Can you try following the installation instructions and skip the unlock bootloader step? Do so at your own risk, because the steps say you have to be on Android 12 first. If you do follow them, just make sure you follow them very carefully.

rbahr said:
I mean trying to re-install TWRP after installing Lineage
Click to expand...
Click to collapse
To my knowledge the guides that are provided on the TWRP site don't work for Android 12 and 13. From what I've heard, you have to root your phone and then install TWRP through Magisk.

Honkette1738 said:
To my knowledge the guides that are provided on the TWRP site don't work for Android 12 and 13. From what I've heard, you have to root your phone and then install TWRP through Magisk.
Click to expand...
Click to collapse
The guides I linked to point to the official Lineage OS instructions, right?

ethical_haquer said:
The guides I linked to point to the official Lineage OS instructions, right?
Click to expand...
Click to collapse
Yeah, but I was just saying how they should probably reflash TWRP instead of how TWRP's site says to, which doesn't work

Honkette1738 said:
Yeah, but I was just saying how they should probably reflash TWRP instead of how TWRP's site says to, which doesn't work
Click to expand...
Click to collapse
This build uses Lineage OS Recovery instead of TWRP.

ethical_haquer said:
This build uses Lineage OS Recovery instead of TWRP.
Click to expand...
Click to collapse
I know, but TWRP can be installed with Android 13 custom roms according to the TWRP thread.