Develop Bugs

[Guide][Mi 8 Lite](Global) how to install TWRP + root with Magisk

Disclaimer :
YOU are choosing to make these modifications
and YOU are the only one responsible for any damages done to your device
==== Notes/Prerequisets/Links ====
* you should have already unlocked your bootloader (if not then start the process as soon as possible because it's going to take a while).
* backup your stuff, make sure you have sufficient charge just in case anything went wrong.
* download the unoffical TWRP port from Here (get the latest version)
* get the latest magisk from Here
* install device usb drivers
* set up fastboot properly Method A, Method B (using chocolaty)
- - - - - - - - - - - -
instructions :
1- shutdown your device completely.
2- enter fastboot mode by pressing and holding the Vol Down + Power Button button until you see xiaomi's mi bunny with a blue "fastboot" text underneath it.
3- connect your device to your pc via usb cable.
4- on your pc check if you have fastboot configured properly and your device recognized by typing:
Code:
fastboot devices
if it's detected then you're good to proceed to the next step.
5- flash the twrp recovery image by using the usual fastboot commands.
Code:
fastboot flash recovery recovery.img
in our case it should look something like:
Code:
fastboot flash recovery recovery-TWRP-3.3.0-0517-XIAOMI8LITE-CN-wzsx150.img
6- unplug usb cable and hold the Vol up + Power Button (don't let go of the buttons untill the devices vibrates) and let it boot to the twrp recovery you just installed.
7- if you rebooted successfully, you should be at TWRP splash screen, if greeted with a slider slide it and continue.
8- in the main menu of TWRP, go to "Install" choose the magisk zip file you downloaded and flash it, when done reboot the device.
9- congratulations friend, you're now rooted and have TWRP as your recovery Happy Flashing :highfive:
- - - - - - - - - - - -
Optional : install Orange Fox Recovery from Here (Supports Encryption and MIUI OTA updates).
- - - - - - - - - - - -
2020-02-25 Last upated and working on MIUI Global Stable 11.0.8 Pie

just in case

Is it possible to just accesss the TWRP to edit build.prop enabling camera2 Api?
If I remember is something about:
fastboot boot twrp.img
and then:
setprop persist.camera.HAL3.enabled 1
Without the need of root the device.
Thanks for the guide!

antonioli84 said:
Is it possible to just accesss the TWRP to edit build.prop enabling camera2 Api?
If I remember is something about:
fastboot boot twrp.img
and then:
setprop persist.camera.HAL3.enabled 1
Without the need of root the device.
Thanks for the guide!
Click to expand...
Click to collapse
Sorry for the late reply
No problem
+
I'm not really sure if you could do it with TWRP's built in file manager without root
You could try
I've seen people do it with adb but haven't had the chance to try it yet
take a look here : https://www.google.iq/amp/s/amp.red...gswg/camera2_api_without_root/#ampf=undefined
And here (this has some very useful info)
https://www.google.iq/amp/s/forum.x...o/guide-enable-camera2-api-root-t3690366/amp/

malek_anas_97 said:
Sorry for the late reply
No problem
+
I'm not really sure if you could do it with TWRP's built in file manager without root
You could try
I've seen people do it with adb but haven't had the chance to try it yet
take a look here : https://www.google.iq/amp/s/amp.red...gswg/camera2_api_without_root/#ampf=undefined
And here (this has some very useful info)
https://www.google.iq/amp/s/forum.x...o/guide-enable-camera2-api-root-t3690366/amp/
Click to expand...
Click to collapse
Thank you for the reply. I've done it in Mi A1 but I don't know if it's the same procedure because of the MIUI. One of the links says that we have to change something in kernel to do it.
It would be good expert people try it to see what method works. It's sad that the Mi 8 Lite doesn't have a proper forum until now.

antonioli84 said:
Thank you for the reply. I've done it in Mi A1 but I don't know if it's the same procedure because of the MIUI. One of the links says that we have to change something in kernel to do it.
It would be good expert people try it to see what method works. It's sad that the Mi 8 Lite doesn't have a proper forum until now.
Click to expand...
Click to collapse
i enabled it in stock miui by adding "persist.camera.HAL3.enabled=1" to my build prop and then rebooting

malek_anas_97 said:
i enabled it in stock miui by adding "persist.camera.HAL3.enabled=1" to my build prop and then rebooting
Click to expand...
Click to collapse
Thanks for the reply.
What method did you use to change build.prop?

Can't find a similar guide for the Mi 8, is it the same process as for the lite ?

antonioli84 said:
Thanks for the reply.
What method did you use to change build.prop?
Click to expand...
Click to collapse
i'm rooted with magisk
with a file manager, i use this one https://play.google.com/store/apps/details?id=nextapp.fx&hl=en
+
this addon https://play.google.com/store/apps/details?id=nextapp.fx.rr
the file is in /system/build.prop

webvan said:
Can't find a similar guide for the Mi 8, is it the same process as for the lite ?
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=YI2CtIIPVaI

malek_anas_97 said:
i'm rooted with magisk
with a file manager, i use this one https://play.google.com/store/apps/details?id=nextapp.fx&hl=en
+
this addon https://play.google.com/store/apps/details?id=nextapp.fx.rr
the file is in /system/build.prop
Click to expand...
Click to collapse
Thank you man. I would like to know if anyone can do the trick without root. I've bought a Mi 8 Lite for my wife and it would be nice to her receive the updates from Xiaomi and use the GCam the same way she receives in Mi A1.

malek_anas_97 said:
7- if you rebooted successfully, you should be at TWRP splash screen
you will be greeted with a slider slide it and continue
Click to expand...
Click to collapse
Hi Malek,
When you first boot to TWRP, were you asked for the decryption password? If yes, did you just format data to skip this? I was asked for the password and my screen PIN did not work. Just wondering if there is no other choice that to format data.

Official Xiaomi Mi 8 Lite (Platina) telegram group 24/7 support and latest ROM news posted here first!
Rules :
1 - English only.
2 - Be polite.
3 - Don't spam.
Gp Link : https://t.me/joinchat/DXcdlA0r5XYI-ooJlO8IlQ
Please Join

chan200606 said:
Hi Malek,
When you first boot to TWRP, were you asked for the decryption password? If yes, did you just format data to skip this? I was asked for the password and my screen PIN did not work. Just wondering if there is no other choice that to format data.
Click to expand...
Click to collapse
to this point i don't really understand how encryption works on this device
it's on by default i guess
so what i finally did the other day to be kinda sure of what's happening
i flashed stock rom in Mi Flash with the clean all option checked
i set up the phone for the first time without setting any fingerprint or security or anything
after that i flashed twrp
from twrp i flashed dm verity and encryption disable
get it from here https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
(make aure to read the first post)
then formatted data
after that the booted up and i set it up normally
and then booted to twrp again to flash latest magisk
now when i check if my device is encrypted using this adb command "adb shell getprop ro.crypto.state"
i get "unencrypted"
so i guess it works? i don't know lol

malek_anas_97 said:
i flashed stock rom in Mi Flash with the clean all option checked
i set up the phone for the first time without setting any fingerprint or security or anything
after that i flashed twrp
from twrp i flashed dm verity and encryption disable
Click to expand...
Click to collapse
It looks like your phone was not encrypted (or was encrypted with MIUI's default password) when you flashed TWRP, as you had clean flashed stock then set up without setting security. That you could start TWRP to flash "dm versity and encryption disable", without being asked to input a password first, shows that TWRP was able to handle the default encryption (or no encryption) of the clean MIUI install.
In my case I already have a screen PIN set up on my phone before trying to install TWRP, and this version of TWRP can't handle it. Another difference is that I have not actually flashed TWRP onto the phone but have merely booted to TWRP via fastboot. I wouldn't have thought that this would affect TWRP's ability to decrypt the DATA partition though.
In hindsight I should have just done the minimum setup after the phone was wiped by the bootloader unlocking process before installing TWRP. I guess that unless there is another version of TWRP out that can handle the screen PIN encryption, my only option is to wipe clean the phone so that I can repeat what you did. However, now that I have reinstalled everything on the phone, I am a bit reluctant to do this just to get root. I think I will wait until there is an AOSP ROM available and do the wipe/format at the time of switching. Hopefully I don't have to wait too long!

chan200606 said:
In my case I already have a screen PIN set up on my phone before trying to install TWRP, and this version of TWRP can't handle it. Another difference is that I have not actually flashed TWRP onto the phone but have merely booted to TWRP via fastboot. I wouldn't have thought that this would affect TWRP's ability to decrypt the DATA partition though.
Click to expand...
Click to collapse
An update: I've now got over this encryption thing. It is indeed the screen PIN that was causing me problems. While I had tried removing the PIN and all fingerprints last time, I had powered down the phone immediately after removing the PIN and booted into fastboot mode. Today I thought I better try it one more time: after removing the PIN, reboot the phone to system first before powering it down and restarting in fastboot mode. This cycles the phone system at least once without the PIN so hopefully any traces of the PIN would really be wiped. And indeed it works - the booted TWRP (i.e. not flashed to phone) has no problems reading my phone and I could install Magisk.
So I now have stock recovery + Magisk on my Mi8 Lite, which is the minimum I wished to do to it. Maybe at a later date I would flash TWRP onto the phone as well.

i cant unlock my mi 8 lite, say user portrait scores too low or black, i activate all need, oem, usb, sync device. no work, any help?

Everything is ok for global rom.
For the language twrp asked directly at first launch for it and you don't need anymore magisk, you can install it directly from twrp. ( advance/install root ) it'll install the version 17.1 and you can update it from the app on the phone.
No problem for reboot into twrp ( volume up + power) even with fingerprint.

kax001 said:
i cant unlock my mi 8 lite, say user portrait scores too low or black, i activate all need, oem, usb, sync device. no work, any help?
Click to expand...
Click to collapse
i really have no idea why this is happening to you
i searched online and it seems like you're not the only one having this

vonclutch said:
Everything is ok for global rom.
For the language twrp asked directly at first launch for it and you don't need anymore magisk, you can install it directly from twrp. ( advance/install root ) it'll install the version 17.1 and you can update it from the app on the phone.
No problem for reboot into twrp ( volume up + power) even with fingerprint.
Click to expand...
Click to collapse
yeah i know there's no problem in turning the phone off then rebooting manually with the buttons
but i was talking about using "fastboot reboot recovery" command to reboot to recovery from fastboot directly
anyways glad everything worked for you friend : )

Realme X2 1993 development

I open this thread because in my opinion the development situation of the various versions of the device is very confusing. I seem to have understood that as regards the unlocking of the bootloader with a working fingerprint, the situation is evolving well only on the China and India version while on the European version nothing moves ... In my modest opinion, Realme deciding to treat those who buy its phones in Europe as users of its lower series devices compared to other areas of the world are wrong because little development leads to a few posts in the various forums and few voices in google searches that each of us does when deciding what to buy ... What do you think you realme device owners in Europe?

I have the 1993ex version and the FP is working fine after a16

hammerheading said:
I have the 1993ex version and the FP is working fine after a16
Click to expand...
Click to collapse
Thanks for the information ... What procedure did you use to unlock the bootloader?

I have EU version and what you said is true about Realme but development aspect, most procedures on China version works on EU version but may partially work on Indian version.
I've tweeted Realme EU over 7 times they haven't replied yet.
MY advice for EU and rest of the world is not to buy from Realme if you want active development and OEM response. Otherwise, you can be patient by using Realme OS until there is bigger development for your device

Bolumstar said:
I have EU version and what you said is true about Realme but development aspect, most procedures on China version works on EU version but may partially work on Indian version.
I've tweeted Realme EU over 7 times they haven't replied yet.
MY advice for EU and rest of the world is not to buy from Realme if you want active development and OEM response. Otherwise, you can be patient by using Realme OS until there is bigger development for your device
Click to expand...
Click to collapse
So you too like me, although there is news of the working fingerprint on the EU, believe that it is still not worth unlocking.
I ask it because I repeat following the various treadhs on the forum it gets confused. It is sometimes indicated that the finger epint works and that for example magisk can work in normal mode and not core only ... This would already be a lot, to say yes it could use the viper4android.

surferbyter said:
Thanks for the information ... What procedure did you use to unlock the bootloader?
Click to expand...
Click to collapse
I used this guide, it works the same for X2.

hammerheading said:
I used this guide, it works the same for X2.
Click to expand...
Click to collapse
Excellent, and as regards the installation of the twrp, which vbmeta file did you use?

surferbyter said:
Excellent, and as regards the installation of the twrp, which vbmeta file did you use?
Click to expand...
Click to collapse
First time i flashed the twrp i folowed this but now i simply skip the vbmeta and flash twrp directly from bootloader and it works fine.

Just installed havos os 2.9 gsi, so, it's not that bad rmx1993ex eu

woocashewski said:
Just installed havos os 2.9 gsi, so, it's not that bad rmx1993ex eu
Click to expand...
Click to collapse
never installed a gsi, if I'm not mistaken it takes the image of the vendor ... if you can give me a link to a guide to get started? Thanks in advance...

Howto thread is on this forum...

woocashewski said:
Howto thread is on this forum...
Click to expand...
Click to collapse
I'm doing something wrong because i get bootloop everytime. i tryed to follow the guide with different gsi but no luck. Can you give a quick step how you did it ?

Until the twrp installation everything works perfectly, when I install magisk whether I try to do it from zip recovery or from boot image patched the verification of the integrity of the verity boot sends me to bootloop. You would need the vbmeta, but when I try to flash the vbmeta.img the command:
fastboot flash --disable-verification vbmeta vbmeta.img
On the fastboot cmd he replies that - - disabled verification is unknown ...

surferbyter said:
Until the twrp installation everything works perfectly, when I install magisk whether I try to do it from zip recovery or from boot image patched the verification of the integrity of the verity boot sends me to bootloop. You would need the vbmeta, but when I try to flash the vbmeta.img the command:
fastboot flash --disable-verification vbmeta vbmeta.img
On the fastboot cmd he replies that - - disabled verification is unknown ...
Click to expand...
Click to collapse
I've been there, i think the problem was the adb. I used the Minimal adb and it worked, give it a try

first - check everything with adb prior to installing anything - get most recent version - i'll get v41, check if there is adb connection - by adb devices, if no - troubleshoot as in many threads here on xda until everything works.
at this moment i've got Havoc OS v 3.0 installed, unfortunetely with same limitations as 2.9 - no FP, no lux metering, and weird battery behaviour (sometimes cpu isn't clocked down when screen off - it can be tuned by eg. Kernel adiutor after rooting with magisk flashed from twrp.)
simplified guide:
- unlock bootloader
- flash twrp from fastboot
- select to start recovery on phone's fastboot menu (volume keys+confirm by power)
- enter your password to decrypt data
- flash vbmeta.img from PC by adb command
- at this stage I made a restart to twrp from twrp menu
- there's shouldn't be any prompt about data encryption
- made a cpmplete backup of the phone - backup to SD card, or to internal and at this stage copy entire backup folder to PC
- wipe: dalvik/cache/system/data
- install system img from a file GSI
- reboot to recovery
- install gapps, if error 70 --> goto wipe, advanced, resize system partition, back to install, install gapps
- reboot
if bootloops - format data partition

woocashewski said:
first - check everything with adb prior to installing anything - get most recent version - i'll get v41, check if there is adb connection - by adb devices, if no - troubleshoot as in many threads here on xda until everything works.
at this moment i've got Havoc OS v 3.0 installed, unfortunetely with same limitations as 2.9 - no FP, no lux metering, and weird battery behaviour (sometimes cpu isn't clocked down when screen off - it can be tuned by eg. Kernel adiutor after rooting with magisk flashed from twrp.)
simplified guide:
- unlock bootloader
- flash twrp from fastboot
- select to start recovery on phone's fastboot menu (volume keys+confirm by power)
- enter your password to decrypt data
- flash vbmeta.img from PC by adb command
- at this stage I made a restart to twrp from twrp menu
- there's shouldn't be any prompt about data encryption
- made a cpmplete backup of the phone - backup to SD card, or to internal and at this stage copy entire backup folder to PC
- wipe: dalvik/cache/system/data
- install system img from a file GSI
- reboot to recovery
- install gapps, if error 70 --> goto wipe, advanced, resize system partition, back to install, install gapps
- reboot
if bootloops - format data partition
Click to expand...
Click to collapse
So gsi roms also have fingerprint problems ... However, more than a custom rom, I was interested in coloros with root ...
I can't give up the fingerprint though because some applications of the company I work for use it for authentication ...

I managed to root, magisk 20.3 zip flash on twrp, on the European version a17 with this guide:
https://forum.xda-developers.com/showpost.php?p=81579961&postcount=44
To make the vbmeta flash command work I used the minimal adb version 1.43, with previous versions it doesn't work.
The fingerprint works very well and energy consumption has not changed compared to use with locked boot.
After carrying out all the procedure, the magisk manager indicates the certified safety net unlike the play store which is instead not certified. To have it certified, you need to download the Device ID app, copy the GSF code that gives you the result by opening it and insert it on the page of this link:
https://www.google.com/android/uncertified/?pli=1
After having it delete the data of google service framework and google play store, force the arrest of the second and reopen it ...

hammerheading said:
I used this guide, it works the same for X2.
Click to expand...
Click to collapse
Except the deeptesting apk in that guide isn't compatible with the x2 - at least not with the eu version. Funnily enough the apk for the realme 5 is compatible - see this post: https://forum.xda-developers.com/showpost.php?p=81014949&postcount=63

Sandalwood83 said:
Except the deeptesting apk in that guide isn't compatible with the x2 - at least not with the eu version. Funnily enough the apk for the realme 5 is compatible - see this post: https://forum.xda-developers.com/showpost.php?p=81014949&postcount=63
Click to expand...
Click to collapse
Ok my bad then, i follow more than one guide so im not sure were i got the apk from. anyway good job finding it for future unlocks!

ROM Stock EU Version
Here the ROM Stock EU https:// drive.google.com/file/d/1-GpV3YBMCCCrQPvCKqqK3cYRXmBMzTCy/view?usp=drivesdk
Just copy the link

[TOOL] DualSix - Dual Boot for OnePlus6/6T [25.03.20]

DualSix - Dual Boot for OnePlus 6!
Before You go further, keep in mind that it's mostly recommended for advanced users! And those who can calmly read instructions, preferably twice!
What does this tool do? And what are the benefits? DualSix allows You to boot two ROMs at the same time! You can flash OOS on one slot and AOSP on another or MIUI or GSI etc. How awesome is that? It also gives You as secure virtual mSD Card that will never get encrypted so Your files will be always safe!
How is this Tool different compared to Zackptg5 version for OP7 Pro? Well.. let's be honest.. he's a great Developer and his skills in making scripts and other stuff are a lot better than mine so his version of Dual Boot is definitely better but since he doesn't have OnePlus6 and 7 Pro received great feedback + people wanted me to resurrect DualSix which I made 2 months ago, I decided to finish the project and release it. It will most likely be the last "big project" for this device before 8 Pro.
Now short Q&A:
Q: Can I use on mido, raphael, x00td, vince etc?
A: No! Only use it on OnePlus6 and 6T.
Q: Can I use it with EPR?
A: No. You can't use them on top of each other.
Q: What ROMs does it support?
A: Ports (soon), AOSP ROMs and GSIs.
Known Issues
Storage Settings in ROMs might report incorrect storage size
Currently only 128GB is supported
Shared Storage is sadly only accessible by using any root explorer (/data/media/0/SharedStorage)
This directory is accessible in TWRP as Micro SD Card (keep important files there)
How to Use:
MAKE SURE TO BACKUP EFS, DATA AND PERSIST (if possible) BEFORE USING IT!
MAKE SURE YOU HAVE LATEST OPEN BETA / OOS STABLE IN BOTH SLOTS!
Also make sure You're not currently using EPR!
It is recommended for You to keep most important files in Shared Storage / MicroSD Card.
It won't get corrupted if something goes wrong.
If You mess up and end up without DualSix TWRP. You can also use Emergency DualSix TWRP from Emergency files!
1. Run RUN_BEFORE_DUALSIX.bat/sh in Fastboot Menu.
2. Boot into TWRP of Your choice.
3. Flash dual-six-twrp-3.3.1-x_blu_spark_v9.109_op6.zip
4. Flash Dual Six for Your storage
5. Reboot into recovery
6. Format all new partitions (Data A, Data B, Shared Storage/MicroSD Card)
7. Reboot recovery again, confirm that new TWRP log shows no red error messages
8. Now follow ROM specific guide below
-------- Ports ---------
Because ports are slightly more difficult to patch
Future ports will come with separate DualSix flasher.
REMEMBER. FORCE WIPE ONLY WIPES CURRENT SLOT.
YOUR SECONDARY ROM WILL BE FINE.
--- Once that happens follow ---
1. From fastboot, run flasher.
2. Most flashers auto reboot, if that happens, just boot into TWRP (even if You see boot animation))
3. Now when You're in TWRP, copy Dual Six ROM Patcher to Your MicroSD Card Storage
4. Flash Dual Six ROM Patcher
5. Done! Now reboot into the ROM and once it boots, You can root.
------- AOSP ROMs / GSIs --------
1. Flash AOSP_ROM_NAME.zip
2. Flash dual-six-twrp-3.3.1-x_blu_spark_v9.109_op6/op6T.zip
3. Reboot Recovery
4. Flash Dual Six ROM Patcher
5. Flash GApps (if needed)
6. Reboot and enjoy!
Note: if AOSP ROM / GSI stays on boot animation for longer than 10 minutes, flash a permissiver.zip.
You should apply same guide for both slots.
Download:
DualSix v1.1 - Mar25
If You have any other problems, just ask here on XDA or for the fastest support PM me or ask someone in my group on Telegram
Join my group!
If You want to support this and other projects, buy me a coffee!
https://www.paypal.me/protodevnano
Credits
MounirHero - for 6T support
eng.stk - for his amazing TWRP
CosmicDan - for his sgdisk guide that helped me with EPR and DualSix
My group for motivating me to resurrect this project!
OnePlus for creating this amazing phone!
​
XDA:DevDB Information
DualSix - DUAL BOOT for OnePlus6 & 6T, Tool/Utility for the OnePlus 6
Contributors
ProtoDeVNan0, MounirHero
Source Code: https://github.com/engstk/android_device_oneplus_enchilada
Version Information
Status: Stable
Created 2020-03-24
Last Updated 2020-03-24

What a wonderful thing....!
Thanks Jay! Can't wait to try this out!

Awesome!! Well Done Bro... [emoji16]
Sent from my RMX1971 using Tapatalk

Great job Jay, hoping 64gb comes soon! One of your ports on one slot and GSI on the other would be amazing!

DualSix TWRP not flashing or booting, OnePlus 6T
I cannot get the dualsix twrp to flash to my device. In twrp it says device not compatible and aborts the installation. I also cannot boot the emergency twrp image from the emergency files folder in fastboot mode, when I try it boots back to the rom. I have a OnePlus 6T 128GB model. My guess is that the twrp is only for the OnePlus 6 and that's why it's aborting? But the OP mentions it working on both the 6 and the 6T. I have tried with and without running the "RUN_BEFORE_DUALSIX_WINDOWS.bat" beforehand. Not sure what to try now.
edit: nevermind, the link hadn't updated yet when I first downloaded it earlier so I did have the twrp that was only for OnePlus 6, sorry about that

Nice, will try it when I have time

This is what I thought/hoped the stupid A/B partition nonsense was going to be.
NICE!!

Will this wipes all. Internal storage

Can't wait to try this. Awesome work

Hello everyone, question, just in case if I want to revert back to stock a and b is it just MSM tool? Thanks Dev.

That's terrific ! This sounds promising !
I'll try to get OP6 OOS latest OB and Havoc OS 3.3 alongside

Just updated DualSix to 1.1 which includes external_sd fix which for some reason was missing from previous zip.
Thanks to Lord_Vicky & MounirHero for letting me know.
Edit: Posted a message in my channel where I test ROMs and confirm if they work or not

ProtoDeVNan0 said:
Just updated DualSix to 1.1 which includes external_sd fix which for some reason was missing from previous zip.
Thanks to Lord_Vicky & MounirHero for letting me know.
Click to expand...
Click to collapse
I need access to your g drive to download

david72262 said:
I need access to your g drive to download
Click to expand...
Click to collapse
Oops. Never happened to me before. But fixed it. Enabled file access for everyone. Not sure why mobile uploads have different sharing options

Awesome man. Great going.

What the f*, I though nobody was gonna attempt to do this !
I'll have to try that

oscarmaldonado said:
Hello everyone, question, just in case if I want to revert back to stock a and b is it just MSM tool? Thanks Dev.
Click to expand...
Click to collapse
I was wondering the same thing

Hi...Thank you very much for this mod.
I am willing to do this but i have a few questions regarding it
1st: after we flash this mod...can we go back to the original partition table and if so...could you explain what files to use and in which order.
2nd: if i want to flash OOS on slot a then my current boot slot would have to be active slot b because roms flash to opposite slots right?
3rd: if i have OOS on slot a and a custom rom on slot b...when i have an update for OOS i must be on active slot b and flash the whole OOS full rom zip and flash all the other files like magisk and recovery and patchers or is it a different way?
4th: can we set a password for slot b's rom or will it brick the device like the 7/7Pro' guide section?
5th: does the shared storage have a fixed size or is it dynamic...and if so, if we put photos and media there will the normal apps like gallery and music players be able to access them at all?!
6th: do we have to stay unencrypted?
7th: if we want to flash magisk to slot a....does our active slot has to be slot a or slot b?
8th: if i want to change rom on slot b...then what do i have to wipe to be able to clean install the rom i want?
i know i asked a lot of questions and some may be stupid but i would really like to try this with all the knowledge beforehand so i dont get myself into a perma-brick like the guys over at 7/7Pro's section
Thanks again for this mod and i hope you reply soon .

joepas said:
I was wondering the same thing
Click to expand...
Click to collapse
I tried, I couldn't get it to boot so I was able to revert it back by running DualSix Remover 128GB.zip in the same folder, reformatted everything and reinstalled OOS.

need help
can anybody tell me for certain how bad i just wrecked my phone. So I was on step 4. Flash Dual Six for Your storage, and after it flashed i hit the restart button on accident. My phone was stuck in the op6 3 dot bootloop. Then i might have put the nail in the coffin by fastboot flashing the images out of the 9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_dd26-FASTBOOT.zip. I’m pretty sure im autistic can anyone help me fix my phone?

[CLOSED][RECOVERY] ORANGEFOX R11.0 for OnePlus 5 & 5T (Unofficial, Official soon)

OrangeFox Recovery
Replace TWRP with OrangeFox once and you won't go back
Last update: 22 November 2020. Build 2
Changelog:
- Updated Magisk to 21.1 (now clicking install magisk after rom installation will install magisk 21.1)
- Update Magisk uninstaller to latest build
- fixed a bug where some people couldn't use flashlight option inside recovery
- fastened things up for faster installations and backup
- minor bug fixes
Contents:
Overview
Why OrangeFox?
Features
Screenshots
Links
Installation procedure
OVERVIEW:
Probably the most beautiful recovery out there.
Synced with the latest Teamwin changes.
Designed with latest Material design 2 guidelines.
Included customization.
Inbuilt patches, like Magisk and password reset patch.
Password protection.
Fully open-source.
Frequently updated.
Why OrangeFox?
OrangeFox has been operating for over two years. In that time OrangeFox have improved the quality, stability, and device support of the recovery. Today OrangeFox is the leader in stability, UI design, and UX. Installing OrangeFox means being with the latest code and fastest fixes.
:good: Treble & Non-Treble Support
:good: No compatibility.zip error while flashing OxygenOS
:good: A lot of customisations
:good: Extremely beautiful UI ready to please your eyes.
:good: Dev team is always ready to fix your problems
:good: F2FS support
There were previously 10.1 builds for these devices for these devices and this is how current build is different from them:
New, more modern UI.
Fixed F2FS support
Upstreamed to R11
and many more...
Note: Official soon I've applied for it.
Screenshots
Screenshots at https://imgur.com/a/Ai8KWX9 and on Sourceforge
Links:
Support group: https://t.me/orangefoxop5t
Download: https://github.com/Maitreya29/OrangeFox-OnePlus-5-T/releases
Installation procedure:
There are two methods to install OrangeFox
A) Via a recovery (for those with TWRP installed):
1. To install an OrangeFox zip, flash it with OrangeFox (or any TWRP-compatible custom recovery) without any wipes.
2. Do the same thing if you want to upgrade OrangeFox
3. When you flash an OrangeFox zip, there is no need to flash any DFE or any other such thing
4.To install an OrangeFox img file, boot into fastboot mode, and run the command: fastboot flash recovery OrangeFox-xyz.img
B) Via Fastboot (For those without a recovery):
You need a PC for this. If you do not have a PC, or access to a PC, then you are stuck!
1. Unlock your bootloader (if not already unlocked)
2. Install adb, fastboot and the relevant USB drivers onto your PCs)
3. Download the correct OrangeFox zip file to your phone, and to your PC
4. Extract recovery.img from the OrangeFox zip file, and copy recovery.img to your PC’s adb directory
5. Reboot your phone into fastboot/bootloader mode
6. Open up a command line window / terminal emulator on your PC
7. Change to the adb directory on your PC
8. Flash OrangeFox Recovery by using the fastboot flash recovery recovery.img command
9. Reboot into OrangeFox by pressing the power + volume down keys, until you see the OrangeFox splash screen
11. After OrangeFox has booted up, check that everything is working – eg, that it has mounted the data partition successfully, and that the touchscreen works.
12. Find and select the OrangeFox zip on your phone, tap on it, and swipe to install it (because OrangeFox Recovery needs some files from the zip)
After installation, the phone will automatically reboot into OrangeFox
Enjoy!

Thank you, I just installed it, I have everything set and customized! Not yet tested all the options but it's beautiful! Congratulations...

@Maitreya29 Since this supports both the 5 & 5T, would you like this thread to be moved to the 5 & 5T Cross Device Development forum? We can then close the same thread you created in the 5T forum since there won't be a need for it.

shadowstep said:
@Maitreya29 Since this supports both the 5 & 5T, would you like this thread to be moved to the 5 & 5T Cross Device Development forum? We can then close the same thread you created in the 5T forum since there won't be a need for it.
Click to expand...
Click to collapse
Hi there, thanks. Actually the download links for both the posts is different and I feel like I'd be able to give better support since I'd know which device is getting the error as both the 5 & 5T builds are different.

Maitreya29 said:
Hi there, thanks. Actually the download links for both the posts is different and I feel like I'd be able to give better support since I'd know which device is getting the error as both the 5 & 5T builds are different.
Click to expand...
Click to collapse
Alright, thanks.
Added to the OnePlus 5 Index Thread here.

shadowstep said:
Alright, thanks.
Added to the OnePlus 5 Index Thread here.
Click to expand...
Click to collapse
Thankn you, appreciate it

''IT DOESN'T DOWNLOAD IT JUST REFRESHES AFTER 5 SECONDS/DIRECT DOWNLOAD''. can you please look in to it thank you.

Sparda333 said:
''IT DOESN'T DOWNLOAD IT JUST REFRESHES AFTER 5 SECONDS/DIRECT DOWNLOAD''. can you please look in to it thank you.
Click to expand...
Click to collapse
It works fine for me, you must be having problems downloading. I don't host the download. Sourceforge does. However join the support group I'll share links.

Download links updated

I didn't have any issues downloading or installing... Are is fine now with my op5.

Awesome! Thank you

Finally ?

It seems working very nicely. Many thanks!

This version of OrangeFox cannot decrypt my Android R partition.
I just completed a clean wipe and fresh install of crDroid's R-based builds. I have a 7-digit PIN set for unlock. I am confident the PIN is correct, because it unlocks my phone. I have device encryption enabled. The known-good PIN is not accepted by OrangeFox to decrypt.

Thracks said:
This version of OrangeFox cannot decrypt my Android R partition.
I just completed a clean wipe and fresh install of crDroid's R-based builds. I have a 7-digit PIN set for unlock. I am confident the PIN is correct, because it unlocks my phone. I have device encryption enabled. The known-good PIN is not accepted by OrangeFox to decrypt.
Click to expand...
Click to collapse
Any recovery on android 11 can not decypt data with pin enabled. You need to set pattern for that.

Thracks said:
This version of OrangeFox cannot decrypt my Android R partition.
I just completed a clean wipe and fresh install of crDroid's R-based builds. I have a 7-digit PIN set for unlock. I am confident the PIN is correct, because it unlocks my phone. I have device encryption enabled. The known-good PIN is not accepted by OrangeFox to decrypt.
Click to expand...
Click to collapse
That's android 11 problem, A11 doesn't let recoveries decrypt with pin. Only patterns work.

This Recovery can decrypt the Data with Pattern in Android 11 ?

Thread closed on request of OP @Maitreya29 as the OP doesn't anylonger owns the device and is unable to support. However, thanks very much for your highly appreciated contributions.
Regards
Oswald Boelcke

Question XIaomi 11 lite 5g ne

How do I make a custom recovery? TWRP

Mkasmkas said:
How do I make a custom recovery? TWRP
Click to expand...
Click to collapse
I have shared a link below, follow the steps to do a custom recovery and it looks easy.
https://www.getdroidtips.com/custom-rom-xiaomi-mi-11-lite-5g/

Is OrangeFox recovery recommended for this device?

steveroysston said:
I have shared a link below, follow the steps to do a custom recovery and it looks easy.
https://www.getdroidtips.com/custom-rom-xiaomi-mi-11-lite-5g/
Click to expand...
Click to collapse
Xiaomi 11 Lite 5G NE different

Mkasmkas said:
Xiaomi 11 Lite 5G NE different
Click to expand...
Click to collapse
Yeah, it's my bad sorry for giving the wrong information. Here's the correct link,
Download & Install MIUI ROM for Xiaomi 11 Lite 5G NE - FlashXiaomi
Download & Install MIUI ROM for Xiaomi 11 Lite 5G NE that will help to upgrade or downgrade your Xiaomi smartphone for free
flashxiaomi.com

Xiaomi 11 Lite 5G NE is preparing to be introduced in the Chinese market after the 5G Global market. The launch date of the Xiaomi Mi 11 LE has been announced.
Xiaomi Mi 11 LE box and launch date is leaked! All details here - xiaomiui
Xiaomi 11 Lite 5G NE is preparing to be introduced in the Chinese market after the 5G Global market. The launch date of the Xiaomi Mi 11 LE has been announced.
xiaomiui.net

Mkasmkas said:
How do I make a custom recovery? TWRP
Click to expand...
Click to collapse
There is no TWRP for LISA, don't confuse the files for RENOIR
For this phone, the recovery LOS only works at 100x100:https://drive.google.com/file/d/1gYAVTitz5uSP5_MO4KkXdYOvPmIvC2oJ/view?usp=sharing

Mkasmkas said:
How do I make a custom recovery? TWRP
Click to expand...
Click to collapse
PitchBlack recovery for Lisa:
PitchBlack Recovery V3.1.0 for Xiaomi 11 lite 5G NE
Changelog: • Based on TWRP 3.5.2 • Source upstream • Added 60 FPS patch • Fixes issues with losing recovery when changing firmware Download https://drive.google.com/file/d/1xazL3LlPZPmzKPPiXPWS0RsasJIWAS95/view?usp=sharing
xiaomi.eu
And LOS recovery for Lisa:
https://forum.xda-developers.com/t/lisa-development.4364971/post-86270751

Mkasmkas said:
How do I make a custom recovery? TWRP
Click to expand...
Click to collapse
here is the working one
twrp_lisa.img
drive.google.com

So far, I've not been able to make a full backup with any of the available recoveries for lisa because the data partition can't be mounted. Has anyone had luck with this?

Pebs74 said:
So far, I've not been able to make a full backup with any of the available recoveries for lisa because the data partition can't be mounted. Has anyone had luck with this?
Click to expand...
Click to collapse
I had this problem (did not see the internal memory)
Try the following:
Install any SD card and boot into TWRP.
Then the phone will see both the SD card and internal memory.

WizardPhoenix said:
I had this problem (did not see the internal memory)
Try the following:
Install any SD card and boot into TWRP.
Then the phone will see both the SD card and internal memory.
Click to expand...
Click to collapse
Do you mean to say that twrp_lisa will see then Internal memory (/sdcard)?
Would it also ask for Android unlock pin/pass while booting to TWRP (to be able to decrypt Internal memory)?
Also, how do you permanently install this TWRP:
- fastboot flash recovery twrp_lisa.img
Or
- fastboot boot twrp_lisa.img
and then by flashing twrp_lisa.img to Recovery from inside the TWRP?

Ok, so I tested twrp_lisa img by temporarily booting (fastboot boot)
It asks for Android unlock pin/pass, it successfully decrypts /data but it does not show anything from Internal memory
I put external SD card and it used successfully (but it didn't help for Internal memory).
E.g., screenshots fromTW
All the rest seems to work ok
You can permanently install by following the instructions for similar A/B A11/12 devices with recovery-in-boot, like
TWRP.me, Xiaomi 11 Lite 5G (Renoir), official instructions for permanent flashing:
Xiaomi Mi 11 lite 5G
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
That is, boot temporarily to TWRP, go to Advanced and use:
- Flash current TWRP
or
- Install recovery ramdisk
My Lisa is already rooted - boot.img patched by Magisk and flashed to boot from TWRP
I wanted to see if it was possible to keep Magisk but also to install TWRP permanently
Then I temporarily booted to TWRP (fastboot boot twrp_lisa.img) and tried:
1) Advanced / Flash current TWRP:
It failed (screenshot) complaining that recovery ramdisk was modified (supposidely due to my patching the boot.img by Magisk)
2) Advanced / Install recovery ramdisk:
It flashed successfully my TWRP img file but noted me (screenshot) that root was now overwritten.
Indeed, when I booted to System, Magisk app was showing no Magisk installed and I had to flash once again my patched boot.img (with Magisk then overwriting the TWRP)
All together, TWRP can be installed permanently but cannot (easily?) have Magisk and TWRP, permanently, in parallel - since both patch the Boot