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'
Related
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
Delete as I'm idiot twrp not available for android 10
funkyirishman said:
Delete as I'm idiot twrp not available for android 10
Click to expand...
Click to collapse
It's been available since maybe a week after Android 10 came out (fixed the problem with fastboot boot). But you may be looking at the "official" TWRP website. You need to use an "unofficial" version TWRP (current version is -76) from the dev's thread here:
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
First of all i want to thank every developer who made it possible for us to experience such cool things on which they spend their sleepless nights , endless hours for which "thank you " is just not enough. I want to aware beginners that what they enjoy in their hand, the smooth satisfying hassle-free seamless experience on phones is result of rigorous hours of hardworking consisting several phases of development (coding , porting , patching etc ).
Always Respect Developers
I am Tech enthusiast. Following this community since last year. Reading and learning about software development.
Here in this post i have contributed nothing. i am just sharing their work with their credits and also making it easier for you guys to follow the instructions and and procedure for entering into the new horizons of customization.
Realme is working really hard to push its development community to compete with MI. If this post will help it to grow it stronger even in 0.1% i will be happy
Note: upgrade device to latest firmware.
Step:1 Unlocking Bootloader
Here you can find full procedure of unlocking written by @Sun Lee
https://c.realme.com/in/post-details/1101401810746212352
Step:2 Installing Twrp
https://sourceforge.net/projects/realme1/files/twrp-9.0/
use adb commands for booting into recovery(this version requires adb commands otherwise manually entering through hard keys is always recommeded.)
Flashing instruction for are:
https://www.xda-developers.com/how-to-install-twrp/
step:3 Installing custom rom
Read and follow procedure carefully as given in OP
https://forum.xda-developers.com/realme-1/development/rom-lineageos-17-1-t4107019 OP By @Invincible-Venom and his whole team
optional : Rooting
you can download magisk manager . it is most widely used and trusted su manager with tons of modding modules.
but always look up to exceptions and NOTE from rom maintainers. In case of latest lineage 17.1 you can only use magisk 20.1 , magisk 20.3
this guide is for very novice kids who are new in this world . i would recommend you to know basic things before doing any stuff written above.
Step:2 Installing Twrp
https://sourceforge.net/projects/realme1/files/twrp-9.0/
i will recommend you download this version of twrp as you will need this for only stable custom rom made by @Invincible-Venom (again thank-you sir)
Click to expand...
Click to collapse
Once again read LineageOS 17.1 post for TWRP instructions.
note: dont reboot to twrp from cmd , it can soft brick your device . always perform it manually through keys.
Click to expand...
Click to collapse
This is ColorOS 5/5.2 issue. In ColorOS 6 the only way to enter recovery (after unlocking bootloader) is using command. So modify this statement.
In case of latest lineage 17.2 you can only use magisk 20.1
Click to expand...
Click to collapse
They can also use Magisk v20.3.
Naveen56 said:
Once again read LineageOS 17.1 post for TWRP instructions.
This is ColorOS 5/5.2 issue. In ColorOS 6 the only way to enter recovery (after unlocking bootloader) is using command. So modify this statement.
They can also use Magisk v20.3.
Click to expand...
Click to collapse
ok brother
Ishan303 said:
ok brother
Click to expand...
Click to collapse
Once check you are using Lineage 17.3 and other numbers for 17.1.
correct Lineage version numbers.
Hello,
I have a question, is it possible to root without flashing any custom rom? I'd like to stay with the current rom but have SU privileges. Is it possible with this phone right now?
luccifyer said:
Hello,
I have a question, is it possible to root without flashing any custom rom? I'd like to stay with the current rom but have SU privileges. Is it possible with this phone right now?
Click to expand...
Click to collapse
Yes you can!
Ishan303 said:
Step:2 Installing Twrp
https://sourceforge.net/projects/realme1/files/twrp-9.0/
use adb commands for booting into recovery(this version requires adb commands otherwise manually entering through hard keys is always recommeded.)
Click to expand...
Click to collapse
Correct this, booting to recovery via hard keys isn't possible in the latest Frimware ( ColourOS 6 ). update it correctly. Hard keys are only possible in ColourOS 5.0/2
Realme stopped support for Realme 1 on unlocking bootloader, In depth test app fails to submit application,
If anyone found a solution please share!
Hi, I did something stupid and need some help please.
I got the bootloader unlock code for my KB2007 - Unlock went well, no issues.
Then I proceeded to download and install the latest official TWRP - Also no issues, I was in the custom recovery, created some backups etc.
After that, I followed the instructions to install Lineage OS as posted here:
Install LineageOS on kebab | LineageOS Wiki
wiki.lineageos.org
I flashed the dtbo and vbmeta partitions as instructed and proceeded with adb sideloading the copy-partitions-20220613-signed.zip file - Somewhere around here is where things went south.
I was not able to access/read my data partition anymore, and attempted to flash the lineage-recovery. After a reboot, I'm now stuck in the bootloader (fastboot). When I select Recovery mode, the phone just goes black. I also can no longer "fastboot boot twrp.img" - Error: "Failed to load/authenticate boot image: Load Error".
After checking the guide one more time I noticed it says the device has to be on Android 12, which mine was not (it was still in factory condition - Android 11). So that was likely the problem.
So now the big question is can I recover from this state? If yes, what's the best way to do so?
Thanks so much!
FreeDee said:
Hi, I did something stupid and need some help please.
I got the bootloader unlock code for my KB2007 - Unlock went well, no issues.
Then I proceeded to download and install the latest official TWRP - Also no issues, I was in the custom recovery, created some backups etc.
After that, I followed the instructions to install Lineage OS as posted here:
Install LineageOS on kebab | LineageOS Wiki
wiki.lineageos.org
I flashed the dtbo and vbmeta partitions as instructed and proceeded with adb sideloading the copy-partitions-20220613-signed.zip file - Somewhere around here is where things went south.
I was not able to access/read my data partition anymore, and attempted to flash the lineage-recovery. After a reboot, I'm now stuck in the bootloader (fastboot). When I select Recovery mode, the phone just goes black. I also can no longer "fastboot boot twrp.img" - Error: "Failed to load/authenticate boot image: Load Error".
After checking the guide one more time I noticed it says the device has to be on Android 12, which mine was not (it was still in factory condition - Android 11). So that was likely the problem.
So now the big question is can I recover from this state? If yes, what's the best way to do so?
Thanks so much!
Click to expand...
Click to collapse
Restore to stock via MSM.
You must update to OxygenOS 12 before installing lineageos 19.1 or you will brick.
The lineagsos guide is wrong and I bricked my device by following it too.
For now, you can only unbrick it with msmtool.
[OP8T][OOS TMO KB09CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Then OTA to OOS 12, then install LOS19.1.
Thanks guys! I was able to restore the device using the MSM tool
I intend to keep it on OOS 11 (and potentially flash LOS18.1), because KB2007 is the T-Mobile variant and based on what I read dual sim only works with OOS 11.
The problem is it is becoming increasingly difficult to find instructions (or even downloads) for anything but the very latest versions :/
FreeDee said:
Thanks guys! I was able to restore the device using the MSM tool
I intend to keep it on OOS 11 (and potentially flash LOS18.1), because KB2007 is the T-Mobile variant and based on what I read dual sim only works with OOS 11.
The problem is it is becoming increasingly difficult to find instructions (or even downloads) for anything but the very latest versions :/
Click to expand...
Click to collapse
You can also use KB2007 OOS 13 beta 1 which works with dual sims.
Rootk1t said:
You can also use KB2007 OOS 13 beta 1 which works with dual sims.
Click to expand...
Click to collapse
Thanks! Yeah, I also read about that, and it does indeed sound like a potential way to go.
Do you know if anyone has figured out yet what makes this "beta 1" special in that it allows dual sims? I think I also read it's no longer possible with beta 2.
FreeDee said:
Do you know if anyone has figured out yet what makes this "beta 1" special in that it allows dual sims? I think I also read it's no longer possible with beta 2.
Click to expand...
Click to collapse
As far as i know, it's still unknown what makes beta 1 work in dual-sim mode.
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.