Database Info

[Recovery] Official TWRP for the Xiaomi Mi MIX (lithium)

Team Win Recovery Project 3.0.2-0
This is for the Xiaomi Mi MIX only, do not flash on other models!
WARNING: As of Android Marshmallow, factory boot images have dm-verity enabled, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below in order to allow system modifications without the risk of a boot loop!
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
You can find the device page here:
For official stock/dev firmware: http://teamw.in/devices/xiaomimimix.html
For (slightly newer) firmware: https://build.nethunter.com/test-builds/twrp/xiaomi/twrp-3.0.2-0-rc1-eu-lithium.img
For (the latest EU) firmware: https://build.nethunter.com/test-builds/twrp/xiaomi/twrp-3.0.2-0-rc2-eu-lithium.img
(touchscreen will not respond if not matching firmware)
You can find up to date fastboot & adb binaries here!
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
You must first unlock your device. To do this, follow the instructions on the MIUI forums. (tedious, I know)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Extract adb & fastboot to your computer.
Download TWRP for Xiaomi Mi MIX (lithium).
Reboot your device into fastboot mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Power] buttons while your device reboots.
Once you're in fastboot mode, you're ready to flash TWRP. To do this, run these commands in order:
fastboot flash recovery twrp.img
fastboot boot twrp.img
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you want to be rooted with something else or just want a bootable system:
Download the latest dm-verity and forced encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
This will also allow you to use [Format Data] to completely disable your encryption if desired.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up. (SuperSU will reboot you a few times)
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2-0 - Official release on twrp.me
v3.0.2-0-rc1 - Initial release candidate and first XDA build
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
There's absolutely none that I know of. Rejoice. You even have working hardware encryption!
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree (Official): https://github.com/TeamWin/android_device_xiaomi_lithium (android-6.0)
Device tree (Development): https://github.com/jcadduono/android_device_xiaomi_lithium (android-6.0)
Kernel: Unavailable (waiting on Xiaomi source release, using MIUI stock binary for now)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
Thank you to @wolfgart for requesting device support and reporting feedback on my initial builds.

Great Work
Now Xiaomi MI MIX is the greatest device we can have atm

@jcadduono @wolfgart Wolfgart request your help just because in Italy I've already published italian rom with my recoveryas you see from here
http://forum.hdblog.it/index.php?/topic/55021-xiaomi-mi-mix-official/?p=999961
http://forum.hdblog.it/index.php?/topic/55021-xiaomi-mi-mix-official/?p=1000010
But your official support is obviously better than mine. I follow you in a lot of thread so I know your great work:good::good: Very happy for this

development is starting , great work OP

agriculture said:
development is starting , great work OP
Click to expand...
Click to collapse
Best device now has best TWRP ever made before.
tnx @jcadduono

Looks like it won't be showing up on twrp.me until 3.0.3 or 3.1.0 depending on what's next. There's a few incompatibilities in the device tree and I'd prefer to wait it out till then. Ex. 3.0.2 doesn't support f2fs or ntfs on omnirom trees right now, but our current source does. If I made an official release neither would be supported.
Update: Official release made on newer TWRP build tree.

Wow, a thousand thanks.

I flashed the recovery, but the touch screen was not working, I can't do anything in the recovery, anyone know what's wrong?

mega00 said:
I flashed the recovery, but the touch screen was not working, I can't do anything in the recovery, anyone know what's wrong?
Click to expand...
Click to collapse
did you read the part about needing a different TWRP image for EU vs stock ROM? You will need to boot the ROM you want, then turn off the device completely and boot into the TWRP version that matches it. This is a kernel firmware update issue that I can't fix until Xiaomi releases sources.
mega00 said:
Wow, a thousand thanks.
Click to expand...
Click to collapse
don't quote the entire thread opener.... edit your post and remove it, if you need to make adjustments use the edit button, don't make another post immediately after your own

jcadduono said:
did you read the part about needing a different TWRP image for EU vs stock ROM? You will need to boot the ROM you want, then turn off the device completely and boot into the TWRP version that matches it. This is a kernel firmware update issue that I can't fix until Xiaomi releases sources.
I am on stock rom and using the stock rom version TWRP, the touch screen just don't work.
To be more clear, I am on dev rom 6.11.10 (MIUI8), do I have to change to stable rom V8.0.8.0.MAHCNDI (MIUI8) to make it work?
Update: Yes, I changed to stable rom and it works.
Click to expand...
Click to collapse

mega00 said:
jcadduono said:
did you read the part about needing a different TWRP image for EU vs stock ROM? You will need to boot the ROM you want, then turn off the device completely and boot into the TWRP version that matches it. This is a kernel firmware update issue that I can't fix until Xiaomi releases sources.
I am on stock rom and using the stock rom version TWRP, the touch screen just don't work.
To be more clear, I am on dev rom 6.11.10 (MIUI8), do I have to change to stable rom V8.0.8.0.MAHCNDI (MIUI8) to make it work?
Click to expand...
Click to collapse
you have to flash CN Stable rom V8.0.8.0.MAHCNDI (MIUI8) and use original TWRP for it and if you want Cross-Flash your CN rom with International one Here too .
When you are on International rom up&running you can flash over the EU TWRP .
As explained from @jcadduono this is the only solution for the moment until XIAOMI release his Kernel stuff officially
Click to expand...
Click to collapse

Thanks to the devs for such fast development on this great phone ...
I personally coming from lg so xiaomi is completely new for me ...
I understand the usual steps unlocking bootloader..flashing twrp ...and finally root ....
I don't have the phone yet but when it comes is running the same stock rom for everybody if I'm not wrong?...
What is that with the different roms?...
And how do i know wich twrp have to install?
Thanks again and sorry for the #noob# guestions....
Sent from my LG-D855 using XDA Free mobile app

cultofluna said:
Thanks to the devs for such fast development on this great phone ...
I personally coming from lg so xiaomi is completely new for me ...
I understand the usual steps unlocking bootloader..flashing twrp ...and finally root ....
I don't have the phone yet but when it comes is running the same stock rom for everybody if I'm not wrong?...
What is that with the different roms?...
And how do i know wich twrp have to install?
Thanks again and sorry for the #noob# guestions....
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
cause Stock kernel still was not relased you have to simply flash EU Rom using stock TWRP and after you done you have to change to TWRP EU to make it working again .
We are waiting official sources from Xiaomi

just to make sure i'm understanding this correctly - there is no way to unlock this phone on the day you get it you have to apply and wait upwards of 2 weeks to be able to unlock it?

knives of ice said:
just to make sure i'm understanding this correctly - there is no way to unlock this phone on the day you get it you have to apply and wait upwards of 2 weeks to be able to unlock it?
Click to expand...
Click to collapse
I waited about 4 hours after submitting the application, 2 weeks is a maximum estimation.

knives of ice said:
just to make sure i'm understanding this correctly - there is no way to unlock this phone on the day you get it you have to apply and wait upwards of 2 weeks to be able to unlock it?
Click to expand...
Click to collapse
you have to wait few minutes or at last 24 hours to receive sms unlock approve

:good::good:

wolfgart said:
you have to wait few minutes or at last 24 hours to receive sms unlock approve
Click to expand...
Click to collapse
I am facing the unlock stuck at 50% issue while trying to unlock the bootloader on this phone? any ideas? Thank you.

does anyone know if using TWRP manager will work to install TWRP after you have unlocked?

jim380 said:
I am facing the unlock stuck at 50% issue while trying to unlock the bootloader on this phone? any ideas? Thank you.
Click to expand...
Click to collapse
you have to Log On with your MIUI account on device too and the retry to unlock
---------- Post added at 07:43 AM ---------- Previous post was at 07:42 AM ----------
knives of ice said:
does anyone know if using TWRP manager will work to install TWRP after you have unlocked?
Click to expand...
Click to collapse
it works ! I can confirm. And it works using Flashify too

[RS988][RECOVERY][OFFICIAL] TWRP 3.3.1-0 for LG G5 RS988 [05/21]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank you @shunjou for helping RS988 to go official!
This is the official support thread for TWRP for RS988.
Installation from Stock:
**If your bootloader isn't already unlocked, go to the LG Developer website. You'll need to create an account. You can get the necessary ADB and fastboot tools from the Android SDK Platform Tools.**
If you wish to flash a stock ROM, you MUST flash a root .zip such as SuperSU to disable dm-verity and storage encryption! If you later decide to install a custom ROM, and didn't disable dm-verity on stock, you will have to COMPLETELY FORMAT your internal storage. Don't risk it.
1. Reboot into the bootloader with the command "adb reboot bootloader" and issue the command "fastboot flash recovery twrp-x.x.x-x_rs988.img", replacing "twrp.x.x.x..." with the location of the TWRP image on your drive.
2. Once it is done writing the image and says "finished," detach all power sources and remove the battery. This step is important—if you reboot into the system instead, TWRP will be overwritten by the stock recovery.
3. Reinsert the battery. Then start the phone, holding down both the Volume Down and Power button. When the LG logo appears, quickly release and re-press the Power button, continuing to hold Volume Down. This should bring you to a Factory Data Reset screen.
4. Confirm "Yes" on the two prompts (don't worry, no data will be deleted—we've overwritten the stock recovery) and you will be in TWRP.
Make sure to follow these steps as written, and make backups if necessary. You wouldn't want to risk saying "Yes" and actually wipe your data, right?
Click to expand...
Click to collapse
Working:
It works. If there are any problems, report them here.
Click to expand...
Click to collapse
Downloads:
Builds may be downloaded from the TWRP website.
Production builds: twrp.me/lg/lgg5rs988.html.
Test builds will depend on the current version of TWRP. For example, for v3.2.3.0 : http://build.twrp.me/twrp-3.2.3-0-rs988.img
Click to expand...
Click to collapse
XDA:DevDB Information
[OFFICIAL] TWRP 3.3.1-0 for LG G5 RS988, Tool/Utility for the LG G5
Contributors
NextDroid, shunjou
Source Code: https://github.com/TeamWin/android_device_lge_rs988
Version Information
Status: Stable
Created 2018-06-14
Last Updated 2019-06-11

Reserved?

Encryption not working for Linage 15.1

If you wish to flash a stock ROM, you MUST flash a root .zip such as SuperSU to disable dm-verity and storage encryption! If you later decide to install a custom ROM, and didn't disable dm-verity on stock, you will have to COMPLETELY FORMAT your internal storage. Don't risk it.
Click to expand...
Click to collapse
@NextDroid, Can you elaborate on this a little more? I'm not sure I fully understand.
Do you mean if you're on a stock ROM, you should root your device by flashing a root .zip file (magisk/supersu) to disable dm-verity and storage encryption before you install a custom ROM?
I just unlocked the bootloader and installed this version of TWRP on my RS988. I also installed x86cpu's unofficial 15.1 lineageOS ROM.
What I did was:
1. Unlock the bootloader
2. Installed TWRP
3. *Flashed SuperSU zip
4. Installed LineageOS/Gapps
*I think I may have flashed the wrong file for SuperSU because I tried flashing the same SuperSU .zip file after installing LineageOS and it didn't appear to do anything. Apps weren't giving me root access and there was no SuperSU app in my app drawer. I fear that my device wasn't actually rooted before installing LineageOS. Am I screwed? What do you mean that you will have to format your internal storage?
The SuperSU zip file I flashed was: UPDATE-SuperSU-v2.82-20170528234214
Sorry, I'm not the most educated in this kind of stuff. But everything as of now seems to be working fine. TWRP functions properly. I have since installed magisk and my device appears to be properly rooted. LineageOS 15.1 is working with no issues so far.

djskribbles said:
@NextDroid, Can you elaborate on this a little more? I'm not sure I fully understand.
Do you mean if you're on a stock ROM, you should root your device by flashing a root .zip file (magisk/supersu) to disable dm-verity and storage encryption before you install a custom ROM?
I just unlocked the bootloader and installed this version of TWRP on my RS988. I also installed x86cpu's unofficial 15.1 lineageOS ROM.
What I did was:
1. Unlock the bootloader
2. Installed TWRP
3. *Flashed SuperSU zip
4. Installed LineageOS/Gapps
*I think I may have flashed the wrong file for SuperSU because I tried flashing the same SuperSU .zip file after installing LineageOS and it didn't appear to do anything. Apps weren't giving me root access and there was no SuperSU app in my app drawer. I fear that my device wasn't actually rooted before installing LineageOS. Am I screwed? What do you mean that you will have to format your internal storage?
The SuperSU zip file I flashed was: UPDATE-SuperSU-v2.82-20170528234214
Sorry, I'm not the most educated in this kind of stuff. But everything as of now seems to be working fine. TWRP functions properly. I have since installed magisk and my device appears to be properly rooted. LineageOS 15.1 is working with no issues so far.
Click to expand...
Click to collapse
Hey @djskribbles,
As I prefaced them, these instructions only apply when you wish to flash a stock ROM. This implies that you are coming from a custom ROM. The current LG stock ROMs, when flashed, encrypt the internal storage, and TWRP is currently not able to decrypt it. This is why one should flash Magisk to disable storage encryption beforehand.
Also, you'll be better off if you use Magisk instead of SuperSU. Flash Magisk before LineageOS, because the script used to flash it automatically wipes the /system partition, which is where SuperSU, for example, makes its changes to enable root access.

NextDroid said:
As I prefaced them, these instructions only apply when you wish to flash a stock ROM. This implies that you are coming from a custom ROM. The current LG stock ROMs, when flashed, encrypt the internal storage, and TWRP is currently not able to decrypt it. This is why one should flash Magisk to disable storage encryption beforehand.
Click to expand...
Click to collapse
Actually, decryption should be working for stock now since the last builds. At least that's what was confirmed by someone that made me realize that building with omni 8 broke the old decryption fix. I think someone else mentioned cm14.1 worked too, so any nougat rom should be fine.
The issue now, as mentioned by x86cpu above, is that decryption isn't working with oreo roms. This seems common for a large number of devices (eg 1, 2, 3). It looks like codeworkx's fix for the zl1 here might resolve it, though I haven't tried it since I'm not currently able to test decryption myself.

shunjou said:
Actually, decryption should be working for stock now since the last builds. At least that's what was confirmed by someone that made me realize that building with omni 8 broke the old decryption fix. I think someone else mentioned cm14.1 worked too, so any nougat rom should be fine.
The issue now, as mentioned by x86cpu above, is that decryption isn't working with oreo roms. This seems common for a large number of devices (eg 1, 2, 3). It looks like codeworkx's fix for the zl1 here might resolve it, though I haven't tried it since I'm not currently able to test decryption myself.
Click to expand...
Click to collapse
All right, that's great to hear! I'll admit, I wasn't sure when I made that second comment... it had been a while since I'd heard anything on stock encryption.
I actually just finished cooking up a fix for Oreo encryption from work on the G6... I'll head over to zl1 if it doesn't work out.
We'll see what happens... --fingers crossed--

On the website the only TWRP version is 3.2.1-0. Is this different from the unofficial version I'm currently running? Has the wrong battery percentage bug been rectified?

Awkydee said:
On the website the only TWRP version is 3.2.1-0. Is this different from the unofficial version I'm currently running? Has the wrong battery percentage bug been rectified?
Click to expand...
Click to collapse
The latest unofficial build is the same as the official in terms of functionality. The battery life percentage should now display accurately.

NextDroid said:
The latest unofficial build is the same as the official in terms of functionality. The battery life percentage should now display accurately.
Click to expand...
Click to collapse
Yippie! Flashing now!

can i lock back the bootloader later to install oficial oreo when it comes?
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev

bmanuelangel said:
can i lock back the bootloader later to install oficial oreo when it comes?
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
Click to expand...
Click to collapse
Are you referring to stock? Hopefully you won't need to re-lock the bootloader. When a .kdz package is published, hopefully @Unscedeo will make one of his COMPLETE INSTALLERS for it, and you could just flash it.

Hmm, I ought to keep up with this thread a bit more...
I've made some updates today and created a test build. Here is the link for anyone who wishes to test: http://build.twrp.me/twrp-3.2.3-0-rs988.img

Hello NextDroid, I noticed that the 3.3.1-0 version TWRP has been released.
According the the release's changes information provided by the TWRP website for the release:
https://twrp.me/site/update/2019/05/22/twrp-3.3.1-0-released.html said:
* Fix selinux issues during formatting - dianlujitao
...
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
Click to expand...
Click to collapse
I have noticed that while using x86cpu's UNOFFICIAL LineageOS-15.1 for G5 (lineage-15.1-20190516-X86CPU-rs988.zip) build, the SELinux status is usually "Enforcing", by sometimes changes to "Permissive". Do you think that the change would be due to the formatting bug corrected by this new TWRP build? If so, can a fix be applied after the buggy formatting from a previous TWRP release has happened and in such a way as to not have to reinstall the operating system? Are TWRP backups done raw, file-based, or differently?

Ascii3 said:
Hello NextDroid, I noticed that the 3.3.1-0 version TWRP has been released.
According the the release's changes information provided by the TWRP website for the release:
I have noticed that while using x86cpu's UNOFFICIAL LineageOS-15.1 for G5 (lineage-15.1-20190516-X86CPU-rs988.zip) build, the SELinux status is usually "Enforcing", by sometimes changes to "Permissive". Do you think that the change would be due to the formatting bug corrected by this new TWRP build? If so, can a fix be applied after the buggy formatting from a previous TWRP release has happened and in such a way as to not have to reinstall the operating system? Are TWRP backups done raw, file-based, or differently?
Click to expand...
Click to collapse
That is a good question. Actually, I am not sure. If you are willing to research that, report your findings to us here I'm interested to know.
I have been very busy for the past couple of months, but the G5 hasn't left my mind... I use it every day I'll see when I can update TWRP and my other builds.
Thanks for keeping us updated, @Ascii3!

NextDroid said:
That is a good question. Actually, I am not sure. If you are willing to research that, report your findings to us here I'm interested to know.
Click to expand...
Click to collapse
Maybe, if I have some time, myself. It is looking like something for August 2019.
NextDroid said:
I have been very busy for the past couple of months...I'll see when I can update TWRP and my other builds.
Click to expand...
Click to collapse
I am glad to see that you your are still around.
NextDroid said:
Thanks for keeping us updated, @Ascii3!
Click to expand...
Click to collapse
Sure.

Ascii3 said:
Are TWRP backups done raw, file-based, or differently?
Click to expand...
Click to collapse
I can and shall answer this question that I posed before:
TWRP allows for both RAW and file-based backups. Usually, however, the GUI provides few items for RAW backup; there is typically a backup option for "System Image" which is a RAW backup.
@NextDroid - I noticed that more recent versions of your TWRP do not have the System Image backup option despite it being in your older TWRP 3.2.3-0 build. The System Image backup functionality from TWRP 3.2.3-0 seemed to work OK. Did you deliberately exclude the "System Image" backup option? I the option missing for good reason?

[ROM] [10] OmniRom for OnePlus7T [EXPERT]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download unoficial:
DOWNLOAD Unofficial
Kernel source:
Source
Selinux Status:
Enforcing
flash on your own risk.
FLASHING
This is for experianced people only, because theres no working TWRP yet. If you dont know how to read stop here (funny eh ?). Also if you dont wanna follow steps bellow because u know better. Goodbye. I dont wanna listen to you cry here. I will not help you.
opposite of what happens if you flash in twrp, this procedure will flash to the slot whis is active now. if you know what u r doing u can flash to any slot u like.
Despite the red text theres really no big danger here if you follow the steps. I just wana scare away newbs.
BU!
android 10 shipped devices have fastboot like we know it and its pretty much useless. and they have the new fastbootd (google it).
1st. get into fastbootd.
option a) from old fastboot, type: fastboot reboot fastboot (funny eh ?) another google miracle to not name it fastbootd.
option b) if you have a running os with adb: adb reboot fastboot
this will bring you to OOS chinese recovery look a like, but its fastboot. to test that u r in the right place try a fastboot command. fastboot getvar all for example.
2nd. flash
unzip ROM using payload dumper
option a) if you are on linux
fastboot -w //this will wipe all your data. you need to do this only on first install, not on updates.
sh ./fastboot_flash.sh
option b)
again! fastboot -w // will wipe all your data and is needed only on first flash
Code:
fastboot -w
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash dtbo dtbo.img
fastboot reboot
3rd. enjoy opensource
unfortunately because of the flashing procedure I have included gapps. when twrp exists they will be gone.
Updating: (WILL WORK ONCE OFFICIAL)
Use OTA inside rom for updates
if u did something else. we dont need/wanna know about it in the thread
May the force be with you
Device Maintainers
@maxwen
Official OmniRom Telegram channel
Link
XDA:DevDB Information
OmniRom, ROM for the OnePlus 7T
Contributors
maxwen, maxwen, darkobas
Source Code: https://github.com/omnirom/android_kernel_oneplus_sm8150/tree/android-10
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: 10
Version Information
Status: Beta
Created 2019-11-14
Last Updated 2020-02-02

Check Telegram group for up to date information
Link

Thanks going to try to flash this with twrp wish luck

NickMidd91 said:
Thanks going to try to flash this with twrp wish luck
Click to expand...
Click to collapse
TWRP doesn't currently work for devices shipped with Android 10. Like this OnePlus 7T.

not red enugh

NickMidd91 said:
Thanks going to try to flash this with twrp wish luck
Click to expand...
Click to collapse
I fear your device is in great danger if you continue

Sweeeet

I tried yesterday to build it myself but failed due to lack of knowledge about ROM building, but this is even better ?

Well when this is ready for twrp flashing then I'll try it and will need to flash off of the TMobile build of oxagen os first.

working great! Thx!

josdehaes said:
working great! Thx!
Click to expand...
Click to collapse
how tideous was the flashing process ?
i sorta wanna flash it lol

5 minutes (but I already had a GSI ROM on the device so I knew what to do). Did not use the script but did it manually. Already rooted with Magisk. Totally happy now with the OP7T

josdehaes said:
5 minutes (but I already had a GSI ROM on the device so I knew what to do). Did not use the script but did it manually. Already rooted with Magisk. Totally happy now with the OP7T
Click to expand...
Click to collapse
How can we get root? I just flashed and there is no root.

opethrocks said:
How can we get root? I just flashed and there is no root.
Click to expand...
Click to collapse
Upload the boot.img from the rom to your device. Install magisk manager 7.4. choose install, patch boot image, select your boot image. Copy the magisk patched image to your PC. Fastboot flash boot the patched image. Reboot.

Is anyone else having trouble playing music through the USB C port? I get nothing but static

Appreciate the release man!
---------- Post added at 01:42 PM ---------- Previous post was at 01:40 PM ----------
josdehaes said:
Upload the boot.img from the rom to your device. Install magisk manager 7.4. choose install, patch boot image, select your boot image. Copy the magisk patched image to your PC. Fastboot flash boot the patched image. Reboot.
Click to expand...
Click to collapse
Is this boot.img based off the 10.0.5 OTA?
I had flashed the patched_boot.img from 10.0.3 and , that did not play well at all.
Coming from the Xiaomi redmi note 7 , So I am also unfamilar with have 2 different slots .

hightech316 said:
Appreciate the release man!
---------- Post added at 01:42 PM ---------- Previous post was at 01:40 PM ----------
Is this boot.img based off the 10.0.5 OTA?
I had flashed the patched_boot.img from 10.0.3 and , that did not play well at all.
Coming from the Xiaomi redmi note 7 , So I am also unfamilar with have 2 different slots .
Click to expand...
Click to collapse
This is an AOSP rom so you can't use an oxygen os kernel with it. You can patch the boot.img from the Omni rom zip with magisk then flash it via fastboot.

josdehaes said:
5 minutes (but I already had a GSI ROM on the device so I knew what to do). Did not use the script but did it manually. Already rooted with Magisk. Totally happy now with the OP7T
Click to expand...
Click to collapse
which gsi rom & how did you flash?
Sent from my HD1901 using Tapatalk

rohit83 said:
which gsi rom & how did you flash?
Click to expand...
Click to collapse
Phh AOSP 10. See the treble experimentation wiki,I added a page for the op7t.

josdehaes said:
Phh AOSP 10. See the treble experimentation wiki,I added a page for the op7t.
Click to expand...
Click to collapse
I don't see 7t under devices, but I see 7t pro, can you share the link? Can I DM you for more?
Sent from my HD1901 using Tapatalk

[ROM][13][OOS CAM][OP7Pro] crDroid v9.5 [19.06.2023]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/13.0/README.mkdn
Flashing Instructions:
Pre-installation:
OOS 12 H.38 firmware is mandatory (can update via firmware update tool found on download page, firmware button)
Download recovery (from download page, recovery button)
Optional NikGapps core (download - note that you may also need setup wizard addon if you rely on Google restore)
Optional Magisk (boot.img used to patch with Magisk in order to get root, can be found in recovery folder from download page)
First time installation (clean flash):
Backup your data to PC, OTG flash drive
Make sure you have OOS 12 firmware installed (if used firmware flash tool from download page, proceed straight to install crDroid.zip)
Enter fastboot
Flash our boot.img in fastboot
Code:
fastboot flash boot boot.img
Boot to recovery (can do from bootloader or with buttons from power off state)
Now in recovery go to factory reset and confirm the reset
Reboot to recovery
Choose apply update and Apply from ADB
Now install crDroid zip via sideload
Code:
adb sideload crDroid.zip
Go back to main menu and reboot to recovery to install gapps (if you don't want gapps, reboot to system)
To install gapps, simply reboot to recovery again and sideload gapps.zip the same way you installed crDroid.zip then reboot to system
Update installation:
Via recovery (recommended way):
Boot to recovery
Choose apply update and Apply from ADB
Now install crDroid zip via sideload and reboot
Code:
adb sideload crDroid.zip
If you had gapps, reboot to recovery and sideload gapps.zip and reboot
Via OTA:
Go to Settings -> System -> Updater and download latest build
Choose install and let it finish
If you have Magisk installed, don't click reboot when prompted and go to Magisk and choose install to inactive slot
Reboot
Note: In some cases where incompatible gapps used, may result in boot issues that should get fixed by flashing gapps again in recovery.
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sm8150
Download:
ROM https://crdroid.net/guacamole/9
Visit official website @ crDroid.net
crDroid OnePlus 7 Pro Telegram
crDroid Community Telegram
If you like my work, consider a donation > My Paypal

Hi dev, your rom title date is wrong we still in october . Anyway thanks for the rom. Is there any specific oneplus settings available in this rom?.

yakuzax1 said:
Hi dev, your rom title date is wrong we still in october . Anyway thanks for the rom. Is there any specific oneplus settings available in this rom?.
Click to expand...
Click to collapse
hehe
yeah... sorry about that )

@gwolfu Thanks for the first 13 build.
Is EROFS planned in the future? just curious.

Toutatis_ said:
@gwolfu Thanks for the first 13 build.
Is EROFS planned in the future? just curious.
Click to expand...
Click to collapse
not really
last I tried, had issues with gapps with it

For those not willing to go through the hassle to install OOS 12 on both slots just to update firmware before installing crDroid, I've made a "firmware flash tool" available on download page
Just boot to bootloader and run Update-firmware.sh (linux) or Update-firmware.bat (windows)

Can I upgrade to firmware 12 directly over OOS 9? Or do I need to upgrade over firmware 11?
Solved

gwolfu said:
For those not willing to go through the hassle to install OOS 12 on both slots just to update firmware before installing crDroid, I've made a "firmware flash tool" available on download page
Just boot to bootloader and run Update-firmware.sh (linux) or Update-firmware.bat (windows)
Click to expand...
Click to collapse
Hello Dev, thanks for a new support for android 13. To be root through magisk, is it done as in crdroid v8? that is, is the boot patched with magisk and flashed with fastboot?

gwolfu said:
For those not willing to go through the hassle to install OOS 12 on both slots just to update firmware before installing crDroid, I've made a "firmware flash tool" available on download page
Just boot to bootloader and run Update-firmware.sh (linux) or Update-firmware.bat (windows)
Click to expand...
Click to collapse
Wow that is awesome I was going to ask for clarification on that (if OOS 12 beta was indeed required or if it was a typo). And it seems it really is required but you made it super easy instead of needing to flash the full OOS 12.
MUCH thanks and appreciation for bringing us CRDROID 13 along with an easy to use flash tool for OOS 12 firmware. Been waiting for A13 of crdroid, crdroid being the best with features and stability. + a great dev to boot

Are you talking about the OOS12 H.31 gloabal beta? Either way, the firmware tool does the job and makes it easy.
Also, will features like smart pixels eventually be on A13 like in A12? nvm seems like all features are still here after dirty flash and firmware change. Switched to big fingerprint now, but it's miscentered like in the pic.

Well flashed the firmware update and the new build, everything went smooth. Nice!
I have a few bullet points:
--After flashing the firmware tool, the stupid "warning" that the bootloader is unlocked is now gone that is awesome. I've wanted that gone since I unlocked but I read it's dangerous to mess with...so I did not plan on that happening but love it
--Seems all crDroid settings from A12 are here and maybe a few extra. Sweet! I was thinking there may be a few things missing because it's a new base but nope, think it's all here.
--The "taskbar" for the crDroid launcher? Super amazing! Not sure if that was there on the previous A12 builds? I've been on Nova Launcher for years now so I'm not sure if this is new to the A13 build. But I absolutely love the taskbar idea (everything still works the same, swipe up for home, swipe up far for recents and drag left-right on taskbar for previous app). I'll attach a pic for those wondering incase it's new.
--Speaking of the launcher, is there any topic/place where we can talk about it? Request features, ask things? Like I'd like to request being able to hide drawer icons/apps and be able to put them into folders (in the app drawer). Also any way to back it up? Like the settings and placement of icons? Using nova and having a backup/restore makes it easy to clean flash ROMs and be right back to normal after. But I think I'd like to stick to crDroid launcher because of this taskbar feature - it's so handy!
--I notice the "Smooth Display" (going from 60Hz to 90Hz) works properly in this ROM. That is nice for people that want to save battery (if you don't want that half second delay from the change-over, in dev-tools it can be still forced to 90Hz all the time).
--Not a big deal but I think I notice the status bar icons very high up, almost touching the top bezel. The OCD in me says arrgg lol. WHY does google mess with the dang paddings on these things...
Those are the few things I've noticed so far. A very nice "initial" release! Seems really smooth too! Thanks again @gwolfu

I am having problems with the back gestures on the screen, anyone else having this problem?

Will wait for feedback regarding the Qualcomm crash dump issue many users and I had on v8 before flashing. Hopefully it's gone for good...

Toutatis_ said:
Will wait for feedback regarding the Qualcomm crash dump issue many users and I had on v8 before flashing. Hopefully it's gone for good...
Click to expand...
Click to collapse
That is not ROM related. That is firmware related.
I only had that happen to me once in the past 6 months (and I've tried every ROM possible during that time), I updated my firmware and never had it again on any ROM. So, updating the firmware here (to OOS 12 as instructed) you should be good to go.
If you still don't want to take the chance, I'd recommend sticking with stock OOS for full stability. These ROMs are basically always beta as it's cutting-edge and you'd have to deal with bugs/testing.

SLAlmeida said:
I am having problems with the back gestures on the screen, anyone else having this problem?
Click to expand...
Click to collapse
Like swiping back? Nope all working good here. I've had no bugs yet. Except 'maybe' slight lag in a game while auto brightness was on (I turned it off and there is now 0 lag).

theslam08 said:
That is not ROM related. That is firmware related.
Click to expand...
Click to collapse
I've always flashed latest OOS version available to both slot prior to flashing any crDroid v8 build, but always had the Qualcomm dump crash at some point regardless.
theslam08 said:
I only had that happen to me once in the past 6 months (and I've tried every ROM possible during that time)
Click to expand...
Click to collapse
I used quite a lot of A12 ROMs too (YAAP, KOSP, Bliss, PixelExperience, Project Elixir, EvolutionX, DerpFest) and only had this issue with crDroid.
theslam08 said:
So, updating the firmware here (to OOS 12 as instructed) you should be good to go.
Click to expand...
Click to collapse
Hopefully, I'll try v9 eventually and see how it goes.

gwolfu said:
For those not willing to go through the hassle to install OOS 12 on both slots just to update firmware before installing crDroid, I've made a "firmware flash tool" available on download page
Just boot to bootloader and run Update-firmware.sh (linux) or Update-firmware.bat (windows)
Click to expand...
Click to collapse
keeps "waiting for devices" at fastbootd mode, doesn't detect my device
Whatever it did prior to this stage killed the system and now I have to msm back to oos11 manually...

theslam08 said:
Like swiping back? Nope all working good here. I've had no bugs yet. Except 'maybe' slight lag in a game while auto brightness was on (I turned it off and there is now 0 lag).
Click to expand...
Click to collapse
Yes, but when I enable the bottom navigation bar in in the crDroid settings, it works again.
I just can't use the on-screen gestures without enabling the navigation bar, and one thing has nothing to do with another.

does this rom have a problem with screen wake up/fod with ambient display on? or is that stable on this one
also, anyone who used evolution x (a13), how does the battery life compare?

Toutatis_ said:
I've always flashed latest OOS version available to both slot prior to flashing any crDroid v8 build, but always had the Qualcomm dump crash at some point regardless.
I used quite a lot of A12 ROMs too (YAAP, KOSP, Bliss, PixelExperience, Project Elixir, EvolutionX, DerpFest) and only had this issue with crDroid.
Hopefully, I'll try v9 eventually and see how it goes.
Click to expand...
Click to collapse
Hm yeah I'm not sure then. Something weird going on there - I've personally never had any crash dumps on this ROM (it was on FlamingoOS) and rarely see anyone say they're having crash dumps on it either. The few times I have, they were told to update the firmware which they supposedly did and didn't have any problems after.
Your best bet if possible would be to get a log of it when it happens: https://pastebin.com/GGaRZ2nJ

Development [ROM][UNOFFICIAL][cheetah/panther] LineageOS 20.0 for the Pixel 7 Pro/7

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS 20.0 for the Pixel 7 Pro (cheetah) and Pixel 7 (panther).
Known issues:
NOTE: This is an early-stage build, and may not be the most stable. It works fine for me as a daily driver on a Pixel 7 (panther), however.
The status bar is mis-aligned to the left by a few pixels, but this does not cause any usability issues, fortunately.
Dual eSIM doesn't work (yet), but stock is probably affected too until the feature drop
You tell me.
Install Instructions:
Spoiler
Be sure you're on the latest stock 13 build and have an unlocked bootloader. You may also be able to flash from GrapheneOS, CalyxOS, or another ROM.
Go into fastboot mode (turn off phone and then Power + Volume down)
Make sure you have the adb/fastboot tools
Run fastboot flash --slot all boot boot.img
Run fastboot flash --slot all init_boot init_boot.img
Run fastboot flash --slot all vendor_boot vendor_boot.img
Run fastboot flash --slot all vendor_kernel_boot vendor_kernel_boot.img
Boot into recovery
Press Factory Reset and confirm
Go to Apply Update -> Apply from ADB
Run adb sideload LOS_BUILD (Replace LOS_BUILD with your LOS ZIP file)
To add GApps, go to Advanced -> Reboot to Recovery -> Apply Update -> Apply from ADB
Run adb sideload GAPPS_BUILD (Replace GAPPS_BUILD with your GApps ZIP file, repeat this step if you want Magisk)
Press Reboot System Now
Update Instructions:
Spoiler
Download the latest ZIP
Reboot to recovery
Flash the latest ZIP
Reboot to recovery
If you previously installed it, flash GApps and Magisk
Reboot to system
Passing SafetyNet/Play Integrity:
For some reason, this ROM only needs the Displax SafetyNet Fix and Shamiko (or DenyList) on top of Magisk in order to pass SafetyNet/Play Integrity, which is a nice bonus. As of 11/17, I was able to use GPay with this ROM if you use Magisk, Shamiko, and Displax SafetyNet Fix.
Download:
Pixel 7 Pro (cheetah)
Pixel 7 (panther)
Official MindTheGApps
UPDATE: LineageOS has "experimental" builds for Pixel 7 (and 6) here. They aren't technically mine, but I'm also the reason Google Tensor GKI kernels build there . Fortunately GPay still works with the experimental builds.
Sources:
Kernel
Device Trees
Vendor

ChangeLog:
2022/11/26:
Updated build to 2022/11/27 (arrgh, UTC/PST differences)
2022/11/16:
Initial build for cheetah/panther.
Is stable (for me at least) on a Pixel 7, your experience may vary however

Reserved 1

Reserved 2

Excited and excellent news. Thank you for your time and patience to bring something for a cheeta.

thanks for sharing

Ahhh Yeah! you rock man! I am dropping everything to get this installed now!! Thank you so much!
oh do you know if this build includes the google photos unlimited storage baked in? I Had It with SparkOS on my pixel 6 pro, and its a lifesaver! I guess Ill find out as soon as i get it running. Thank you again!

Heck ya! Finally! I have experience flashing lineage os. Thanks! Hope the battery life is great.

It did not recognize my sim card as the mobile data was greyed out. I had to revert back to stock rom and did everything correctly as you explained how to install it.

UltimateGamer83 said:
It did not recognize my sim card as the mobile data was greyed out. I had to revert back to stock rom and did everything correctly as you explained how to install it.
Click to expand...
Click to collapse
Are you on eSIM or physical SIM? Pro or non-Pro? Which carrier/country? Do you have a T-Mobile or AT&T variant?
On a unlocked non-carrier variant Pixel 7, this ROM recognizes my T-Mobile US eSIM, and also a Verizon MVNO (US Mobile) physical SIM.

MrNegative370 said:
Ahhh Yeah! you rock man! I am dropping everything to get this installed now!! Thank you so much!
oh do you know if this build includes the google photos unlimited storage baked in? I Had It with SparkOS on my pixel 6 pro, and its a lifesaver! I guess Ill find out as soon as i get it running. Thank you again!
Click to expand...
Click to collapse
I don't use Google Photos since I use Nextcloud and am not sure, but it should work since unlike official LOS builds, the ROM fingerprint is the same as stock (also similar to how Play Integrity passes).

MrNegative370 said:
Ahhh Yeah! you rock man! I am dropping everything to get this installed now!! Thank you so much!
oh do you know if this build includes the google photos unlimited storage baked in? I Had It with SparkOS on my pixel 6 pro, and its a lifesaver! I guess Ill find out as soon as i get it running. Thank you again!
Click to expand...
Click to collapse
No lineageos doesnt have this feature. Use the Pixelify.apk and you are good to go.

gapps doesnt have android 13? how do i get gapps after i flash lineageos?

my google playstore doesnt work, tried reflash gapps 3 times.

gapps : https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-T/08-Sep-2022/

SynGreis said:
gapps doesnt have android 13? how do i get gapps after i flash lineageos?
Click to expand...
Click to collapse
The GApps link does show A13 to me, it's the MindTheGapps-13.0.0-arm64-20221025_100653.zip file you need to download and flash for GApps.

SynGreis said:
gapps doesnt have android 13? how do i get gapps after i flash lineageos?
Click to expand...
Click to collapse
You have to reboot to recovery before you install GApps. If you just flash GApps after Lineage without rebooting to recovery, you won't get GApps.
This is an issue with A/B partition devices (basically all modern Android phones).

tried it again. reinstalling from scratch. i have a pixel 7 pro factory unlocked model straight from google.com. i have the bootloader unlocked with oem. my carrier is att with phsyical sim. so it is indeed working this time. maybe the first time didn't work because i forgot to factory reset.

UltimateGamer83 said:
tried it again. reinstalling from scratch. i have a pixel 7 pro factory unlocked model straight from google.com. i have the bootloader unlocked with oem. my carrier is att with phsyical sim. so it is indeed working this time. maybe the first time didn't work because i forgot to factory reset.
Click to expand...
Click to collapse
That's your issue, if you don't factory reset then it obviously won't work.
Well, sometimes I forget it too .

Can you install gcam after? And is it working properly?