Database Develop

[Guide] [Mate 10 Pro] Treble-Compatible ROM installation and Compatibility list

Introduction
This is aimed to be a complete but simple guide for users which want to know what works in the Treble-World on the Mate 10 Pro and 'how to get there', based on other guides and my own findings
Disclaimer: I am not responsible for what you do with your device, you are free, probably old enough to know what you are doing and intelligent enough to read this through.
For the moment I will only speak about my own tests on a BLA L29 as I don't have the possibility to test everything.
Feel free to share your own discoveries via PM (just reuse the same formatting to make things easy)
Requirement
1. PC/Laptop running Windows 10 with adb and fastboot drivers installed
2. Original Huawei USB Type-C Cable
3. Being able to read and use search when a question arises
Summary
0. General Information
I. Unlock the Bootloader
II. Choose your ROM (a.k.a "What works on what")
III. Install your ROM
IV. Miscellaneous / Secondary stuff
V. Bonus : What to do if I am stuck / Bootlooping
0. General Information
To make things easier for everybody, here are some basic informations about your device and some common knowledge :
How do I get in Download / Bootloader / Fastboot Mode ?
Shut down your device, insert your USB cable. Keep the Volume DOWN button pressed and press the Power button, wait.
PRO TIPP : You may also get there from within android, first enable ADB debugging in developer options, then, on your PC open a command prompt and type "adb reboot-bootloader"
How do I get in Recovery Mode ?
While in Download / Bootloader / Fastboot Mode, take the USB cable out, keep the Volume UP button pressed and press the Power button until the phone reboots.
I. Unlock the Bootloader
We allready have a thread by @otonieru perfectly discussing this point, don't forget the Windows 10 fix :
https://forum.xda-developers.com/mate-10/how-to/how-to-huawei-mate-10-pro-standard-t3709535
II. Choose your ROM (a.k.a "What works on what")
This section isn't complete and should be detailed with time. None of these ROMs is specific for the Mate 10 Pro, but thanks to Treble, most images will work. Device-specific modifications are still needed in future, ask your local dev
1. Generic AOSP (Android 8.0 and 8.1) by Phhusson
Link : https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
Description : Really basic ROM (basically pure AOSP) which serves as a basis for most of the other ROMs.
What's working : Everything basic
What's not working : VoLTE, SuperSU and Magisk, Signal strength is reported incorrectly, error message at each start, Play Store tends to hang (solution : wipe the Play Store from recents or force close it)
Actual status : Barebones, can be customized in some ways with overlays.
2. LineageOS 15.1 (Android 8.1) by LuK1337
Link : https://forum.xda-developers.com/honor-view-10/development/rom-lineageos-15-1-t3753000
Description : If you don't know LineageOS, you should have heard about CyanogenMod (CM). This is a super clean, customizable version of Android, based on AOSP
What's working : Everything basic
What's not working : VoLTE, SuperSU and Magisk (system crashes), Signal strength is reported incorrectly,
root works thanks to addon-su (see Miscellaneous)
Actual status : Working as a daily driver (at least in my case) if you can live with some very small drawbacks.
III. Install your ROM
Once you have unlocked your Bootloader and chosen the ROM your heart desires follow these steps :
1. BACK UP YOUR DATA ! -> You will certainly have to do a factory reset and backing up data should be something natural when flashing something on your phone, even before updates.
2. Download the ROM (latest is probably best, but it's best to read what is said in the respective threads before jumping in the hole.
3. Reboot to the Download / Bootloader / Fastboot Mode (see above)
4. Flash the ROM by opening a command prompt and typing :
Code:
fastboot flash system system.img
where "system.img" is the filename of the ROM you downloaded
5. Reboot the phone by typing :
Code:
fastboot reboot
6. The phone will probably get in a bootloop. Don't panic. This should be normal.
After 4-5 reboot the phone will go in Recovery mode. Make a Factory Reset
7. Reboot
8. Profit
IV. Miscellaneous / Device-Specific stuff
This is probably the more interesting part as it is quite hard to find the correct information for our device concerning these points.
Root
ROMs as Lineage don't come prerooted. To root your phone the only viable solution seems to be addon-su for the moment.
To install you will need to install TWRP (follow the instructions in this link by @Dees_Troy : https://forum.xda-developers.com/mate-10/development/recovery-twrp-3-2-1-0-touch-recovery-t3752399 ), boot to TWRP (same as booting to Recovery, as TWRP is the new Recovery). go to advanced -> adb sideload. Connect your phone to your PC and flash the file using
Code:
adb sideload addonsu-15.1-arm64.zip
finally reboot, go to 'developer options' and chose the desired option under 'root options'. Done.
Camera
When flashing a ROM it will probably come with the stock AOSP or Lineage camera which, just say it, sucks on our device form a quality point of view. Here are the answers found to this problem for the moment. Sadly, there isn't one solution which works for everything and everyone.
Google Camera - GCam
Photos work - Gallery works - Videos don't work
Right now his is probably the best compromise if you want something that works, easy to install, while not wanting every little gimmick (in that case you should probably stay on EMUI - The definition of gimmick). Simply install the apk.
Note : there are probably other versions of GCam that work or will work in future, feel free to inform me / us about better working versions.
Link : https://drive.google.com/file/d/1Rw2lXtSHvOUalpA8YKg_kW2Xj_Gu746M/view
More information / discussion :
https://forum.xda-developers.com/mate-10/help/gcam-mod-mate-10-t3729078
Camera Port from the Mate 9 - needs root
Photos work - Videos don't work - Gallery doesn't work - Most filters and gimmicks work
A bit more complicated to install. The easiest way found for now is to root first using addon-su and then copy the system folder inside this zip into the respective folders using a root enables explorer like solid explorer
Link : https://mega.nz/#!7hQDhQAK!p2s7jQp9-nhp2-O1U2s2GrBB9UVBhgKDtFfHTq_CHvI
More information / discussion : https://forum.xda-developers.com/pr...huawei-stock-camera-app-treble-roms-t3735169/
V. Bonus : What to do if I am stuck / Bootlooping
Remember when I said to back up ? Well I hope you did, because if you are really bootlooped and a reflash of the system image hasn't helped. you will have to reflash the whole device, which isn't quick.
Gladly @mankindtv has got you covered with his great guide : https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
I hope I could help a bit. Feel free to add your own findings, simply PM me.
Credits -
@otonieru for the great Bootloader unlocking thread
@phhusson for his many efforts to make Treble awesome
@LuK1337 for his many efforts to get things working on the Lineage side as well as for addon-su
@Dees_Troy for his awesome work on TWRP
@mankindtw for his great guide on recovering from the loops of boots

reserved

It's gonna be one of the most helpful threads for the novices.
---------- Post added at 02:41 AM ---------- Previous post was at 02:39 AM ----------
If possible, please add how to go back to stock rom in simplified form.

mdjishadk said:
It's gonna be one of the most helpful threads for the novices.
Click to expand...
Click to collapse
I have lost three days to get out of bootloops and gather the info... I hope nobody else will have to live the same thing (and maybe this can become a dedicated thread to fix the last missing blocks to have a complete experience)

good job

You can also root Lineageos with magisk. I did it and it works.
https://forum.xda-developers.com/mate-10/how-to/root-huawei-mate-10-pro-magisk-twrp-t3753956

good job on this one OP btw, video on mate 9 camera port is only broken on 8.1, on 8.0 all camera features work fine except opening of the picture from the camera app itself

Good job man!

Gryphie said:
You can also root Lineageos with magisk. I did it and it works.
https://forum.xda-developers.com/mate-10/how-to/root-huawei-mate-10-pro-magisk-twrp-t3753956
Click to expand...
Click to collapse
It might be android 8.1. It worked fine for me when using 20180225 version, didn't test later ones.
What version are you on?

Gryphie said:
You can also root Lineageos with magisk. I did it and it works.
https://forum.xda-developers.com/mate-10/how-to/root-huawei-mate-10-pro-magisk-twrp-t3753956
Click to expand...
Click to collapse
It crashed everything on my 8.1 build (and the developer himself recommended me addon-su) maybe a tad harder to use, but at least you learn something at the same time

You should add that the stereo speakers don't work.

Timate5 said:
You should add that the stereo speakers don't work.
Click to expand...
Click to collapse
"Stereo"... When coming from a Nexus 6P this Sally doesn't sound stereo at all... But you're right !

Android Auto doesn't work also on these ROMs. Phone says its incompatible because of some OMX codec issues

timo.helfer said:
Android Auto doesn't work also on these ROMs. Phone says its incompatible because of some OMX codec issues
Click to expand...
Click to collapse
That's too bad, android auto uses h264 streaming codec I think. I think this issue will have something to do with hardware acceleration. Have you tried messing around with the acceleration option found in the developer options to see if it might work?

Nice guide! Thank you @ChriKn!
Can you add to the "Generic AOSP (Android 8.0 and 8.1) by Phhusson"'s part that we need to use A-ONLY version of this rom?

I will try as soon as I have my PC.
Sad news, I got a good opportunity on a Pixel 2 XL and sold my Mate 10 Pro (I need my Pure Android AND Quality Camera)
Does someone want to take the thread over ?

ChriKn said:
I will try as soon as I have my PC.
Sad news, I got a good opportunity on a Pixel 2 XL and sold my Mate 10 Pro (I need my Pure Android AND Quality Camera)
Does someone want to take the thread over ?
Click to expand...
Click to collapse
Sure i can write some impressions. I just installed Carbon ROM.

I did flash but is not booting at all.
Hello, I did everything as mentioned. And phone is not booting it just bootloops.
i can't do a reset is sends me directly back to recovery and just ask to reboot or shutdown phone...
What do I have to do ?
Can i go to stock rom again ?
Thanks

triconix555 said:
Hello, I did everything as mentioned. And phone is not booting it just bootloops.
i can't do a reset is sends me directly back to recovery and just ask to reboot or shutdown phone...
What do I have to do ?
Can i go to stock rom again ?
Thanks
Click to expand...
Click to collapse
Let it Bootloop until it goes to erecovery and than factory reset it

Timate5 said:
Let it Bootloop until it goes to erecovery and than factory reset it
Click to expand...
Click to collapse
I did that but it is just boolooping again, I did all tge steos over and over and it just bootloops every tipe even after factory resete, it actualy asked le once to resete since then after a couole of reboots it goes straight to te erecovery, wherz it ask to login on a wifi to download latest bootloader and rom or reboot or shutdown device...

[ROM][TMOBILE][S7_SM-G930T][Oreo Rooted]

I created a new ROM with WifiCalling: [ROM][TMOBILE][S7_SM-G930T][Oreo 8.0 Rooted][WifiCalling]
ROM last updated: 9/24/2018
Introduction:
HUGE thanks to the guys that got this going like root & figuring out hybrid stocks! This thread here is just my take and customization on what they already did. Ultimately, I wanted Oreo rooted & modded, but I couldn't find a single guide. And the ROMs that existed weren't exactly what I was looking for. I wanted something exclusive to Tmobile. So I did a ton of reading and compiled it all together into a HOPEFULLY easy guide to follow. PS If you like Samsung bloatware, this is NOT for you!
Description:
EXTREMELY debloated! Nearly bare minimum, while still retaining hardware functionality. Eg, Samsung Gallery & Camera exist so we get 4k recording, and there aren't errors when we pull up the Gallery to edit, etc.
Everything possible I replace Samsung with Google
Solid ROM, very fast
There are very few options in Aroma to limit issues & repeatability. There are many options once booted up after initial setup
If you hate Samsung SW and just want a solid working ROM with very few install options to get you up and running this is for you.
Aroma installer layout is a little wonky, apologies (If anyone knows how to fix this please chime in )
This will delete all of your data! This is the only way so don't ask. Backup your data!
Features:
Optional Tmobile Apps
Optional Google Apps
Root Features: See Downloads->Recommended Root Zip & thank him for his work!!
Debloated
Deodexed
De-Knoxed
Zipalign
Instant Face Unlock mod
Disable signature verification
S9 Dolby Atmos
Memory Saver
OperMax
More Toggles
Mulit User
Private Mode
Unlock Stock NetWork Speed
Build Prop Tweaks
Device Status Official
White Page
CallRecord
Capture and Record Screen
Remove Volume Safe Warning
Remove brightness Warning
Added Bike Mode
Allow fingerprint unlock after a reboot
Google MarkUp
Force always visible Free Form Menu item in notifications
Substratum Theme
Dual speaker
Samsung Weather
Samsung Video Editor and Trimmer
LancControl Mods:
Ui Mods
3Mint Clock
Gradient statusbar
Virtual Lock Home Recent Button
Phone Mods
Clock Face Setting Aod
AdAway
Dpi Changer
Disable/Enable Apps
Kernel Adiutor
TW Mods:
Adaptive Fast Charging
Wireless Fast Charging
Usb Plug in/out Wakeup
OutDoor Mode
HardKey Lights
TouchLight
Recents Menu Mods:
Tasks Changer
Blur recent and Notification Menu
Download Links:
Base.7z & Oreo_Kevin71246Modded_v1.zip
VoLTE Fix
Steps:
This will delete all of your data! If you continue, you acknowledge that the Author is NOT responsible for anything that happens to your phone!
Install Stock Oreo:
Download mode & Setup
Make sure you have latest device drivers setup on your PC
Enable USB Debugging on phone in Developer Settings
Boot phone into Download Mode:
Turn off your device
Press and hold Volume Down + Home + Power button
When you see the warning screen, release buttons & press Vol UP. Phone should say "Downloading..."
Download and unzip Base.7z to PC (This contains stock Oreo, ODIN, & root)
ODIN
Open ODIN on PC (\Base\Odin_313.exe)
Connect USB from PC to phone. ID:COM in Odin should turn Blue with a COM port
Select AP, BL, CP and CSC files from the \Oreo_Stock\Base\ folder for corresponding files
Select HERO2QLTE_USA_VZW.pit
Select Start
Finished: Phone will reboot & show Carrier screen for 3-5mins. Wait until Setup screen & go through quickly (bare minimum) since you'll wipe it again
Root Instructions: (+Flashfire, SuperSU)
Reboot phone into Download mode
Odin
AP: Select \Base\Root\AP_SM_G930_OREO_ENG_BOOT.tar
Start-> Wait for phone to boot to Android OS
Root
Double-click \Base\Root\cmd-here.exe & Type: root.bat [enter]
Option: 1 (Install Root No tweaks) (Or pick whatever you want)
OPTIONAL: (Testing, WIP...) Backup with Titanium Backup (or whatever) at this time the following apps so they work in the end: Visual Voicemail, Wifi...
OPTIONAL: (Testing, doesnt work. Please provide a fix if you know!) VoLTE Icon Fix: via FlashFire app: Flash OREO_VOLTE_ICON_HOTSPOT_FIX.zip (Flashes fine but doesnt fix it!!)
*Note: With this system root, do not update su binary. Disable notifications for SuperSU app. Don't flash any superuser zips in recovery that are not made by jrkruse
Install Custom Hybrid ROM
Download & copy Oreo_Kevin71246Modded_v#.zip to phone
Flashfire
Open Flashfire on phone
Red + symbol->Flash ZIP or OTA-> Select Oreo_Kevin71246Modded_v#.zip-> Default options-> Check mark-> Lighting bolt at bottom-> OK
Phone will reboot to Aroma
Aroma Setup
Choose options as desired (Use vol up/down+power buttons to select! Touch is offset so if you use this touch BELOW your option to select)
Use very Bottom Right "Next" button if you see multiple
*Wait 3-5min on loading screen. If it doesn't boot after 10min: Hold Vol Down+Pwr buttons (~10sec) until phone restarts. After restarts, IMMEDIATELY hold VolUp + Home buttons. Should say Recovery. Wipe Data/Factory & Wipe cache. Restart Phone. Should load to Setup.
OPTIONAL: Root: Follow "Root Instructions" above, again.
Followup-Steps:
Fix Dialer: Phone Settings->Apps->Menu->Default Apps->Calling App->Select Phone
Known Issues:
Wifi Calling not working despite flashing Tmobile Wifi & Tmobile Wifi Settings app
Visual Voicemail not working (disabled until we can figure this out)
VoLTE Icon wont go away despite flashing known working fixes
Changelog:
Version 1: First build
Immediate References:
[Rom][ALL_CARRIERS_G930_CRF1][Stock_Oreo_Hybrid][Safestrap_Preinstalled]
Root For S7/S7Edge Oreo And Nougat
Project L s7 Google/Samsung Oreo Rom CRF1 Base
Credits:
(Im copying/pasting credits from other links since so many people participated I dont want to miss anyone!)
- @jrkruse & @klabit87 for root
- @Lanc-City for ROM base
- @gustco for eng boot.img
- @Raymonf for modified odin
- @afaneh92 for safestrap
- @me2151 for finding this method
- @tytydraco for some instructions
- @mweinbach for some instructions
- @Craz Basics for xposed on non rooted
- @partcyborg for finding the root method!
- @elliwigy for being great help and original S8 root
- @rayan-refoua for boot animation
- @FatalONEM8 - For posting Oreo OTA
- @stang5litre
- @jds3118
- @Krog18
- @klabit87 for S7 Safestrap
- @amarullz Aroma Installer
- @mrRobinson for adaway
- @Chainfire for Flashfire
- @JaeKar99 for Reactor_BootAnimation
- echoe rom and noname rom
- stang5litre Test Group
- Please PM me if you were forgotten!

Reserved1

Reserved2

Reserved3

Ayy mentioned. Good work on the rom ?

Okay I don't know what's going on here but I have never talked to you or never given you permission to reuse my Rom/work this is stealing my rom is still being worked on this thread must come down this is not cool
IF YOU WANT TO share something Make your own Rom My Rom/Work is not to be reused in any type of way I put a lot of time and work into it

Lanc-City said:
Okay I don't know what's going on here but I have never talked to you or never given you permission to reuse my Rom/work this is stealing my rom is still being worked on this thread must come down this is not cool
IF YOU WANT TO share something Make your own Rom My Rom/Work is not to be reused in any type of way I put a lot of time and work into it
Click to expand...
Click to collapse
Meant no offensive at all, I assure you. Did I completely misunderstand the point of the xda community? I clearly gave you credit and didn't say I created this from scratch, rather pieced it together, literally what every Dev here does. I am not doing this for money. I mentioned & thanked you, which is probably how you found this thread. All I am trying to do is give back to the community. I spent a TON of time going through guides, updating what I found, creating a guide, and testing this - I didn't just rebrand it.
That said, I did use part of your work so I'll give you the choice: can I use part of your work and allow the xda community to benefit, or do you want me to remove your segment & Lanc app this comes with?
Btw see the post above yours. And shouldn't this chat be on PM? For reference, what I used from you was your apks so I didn't have to redownload & retest them and aroma script for a starting point, but the script is 90% different at this point.
Again, I did not mean to offend, but please let me know if I have your permission. Thank you

Good news! We got @Lanc-City 's blessing to continue to use his base ROM & LancControl app. This XDA community is AWESOME! Don't forget to go and check out his original Mod'd ROM: Project L s7 Google/Samsung Oreo Rom CRF1

VoLTE icon fix
Not sure if this will work for everyone. Download System UI Tuner by Zach Wander from Play Store. Once in menu, go to TouchWiz, scroll down to IMS VoLTE Icon and toggle on then off. I did not apply the fix that you have the link for above, and I was able to uninstall the app and the icon does not come back.

Hey, I am trying to use your ROM but after I flash the zip file and finish set up with Aroma and reboot, I get stuck in the boot screen where the rainbow colored X symbol is spinning. I followed the guide exactly so I'm not sure what I'm doing wrong. Maybe my default options in flash fire are not correct? All the boxes in that screen are unchecked. Should I mount /system read/write? I just hit the checkmark and flash. Also I did hit Install Root with Interactive Governor, if that makes a difference. Any help? Thanks.

infamouz421 said:
Hey, I am trying to use your ROM but after I flash the zip file and finish set up with Aroma and reboot, I get stuck in the boot screen where the rainbow colored X symbol is spinning. I followed the guide exactly so I'm not sure what I'm doing wrong. Maybe my default options in flash fire are not correct? All the boxes in that screen are unchecked. Should I mount /system read/write? I just hit the checkmark and flash. Also I did hit Install Root with Interactive Governor, if that makes a difference. Any help? Thanks.
Click to expand...
Click to collapse
deleted, wrong thread

infamouz421 said:
Hey, I am trying to use your ROM but after I flash the zip file and finish set up with Aroma and reboot, I get stuck in the boot screen where the rainbow colored X symbol is spinning. I followed the guide exactly so I'm not sure what I'm doing wrong. Maybe my default options in flash fire are not correct? All the boxes in that screen are unchecked. Should I mount /system read/write? I just hit the checkmark and flash. Also I did hit Install Root with Interactive Governor, if that makes a difference. Any help? Thanks.
Click to expand...
Click to collapse
Copying/Pasting PM I sent you for others, and added some things:
Did you let the "rainbow" sit there for at least 10 min? (It should be 3-5 but who knows.) Are you soft-bricked in your current situation? If you start again, at "Install Stock Oreo:" does this at least restore your phone back to stock Oreo? If so, then try again and proceed with ALL the remaining steps again, CAREFULLY reading the instructions again & again.
Also, what phone model do you have? And I admit I haven't tested the CPU governors in the root script ; I ALWAYS chose none - I'll remove those options in the next version since I have tested them and there are plenty of CPU overclocking options once booted inside the ROM.
If you are able to restart this process and get stock Oreo back, AND chose NO CPU governors in the root script, maybe you want to either try "NO" to Google & Tmobile options just to make sure you can get Android booted- If it boots fine, then try the ROM again and pick Google and/or Tmobile to isolate any issues (things that are breaking)
Have you used ONLY what I provided, such as ODIN (version is important), etc?
Re Flashfire: Default options should be fine. The ROM script will set all the partitions, mounts, permissions, etc.
Good luck!
*Above response I guess is for overall troubleshooting the ROM, if any issues present themselves.
On another note: I'm actively working on this ROM as time allows. Trying to ease the install process, correct some issues, further customize, & improve...

kevin71246 said:
Copying/Pasting PM I sent you for others, and added some things:
Did you let the "rainbow" sit there for at least 10 min? (It should be 3-5 but who knows.) Are you soft-bricked in your current situation? If you start again, at "Install Stock Oreo:" does this at least restore your phone back to stock Oreo? If so, then try again and proceed with ALL the remaining steps again, CAREFULLY reading the instructions again & again.
Also, what phone model do you have? And I admit I haven't tested the CPU governors in the root script ; I ALWAYS chose none - I'll remove those options in the next version since I have tested them and there are plenty of CPU overclocking options once booted inside the ROM.
If you are able to restart this process and get stock Oreo back, AND chose NO CPU governors in the root script, maybe you want to either try "NO" to Google & Tmobile options just to make sure you can get Android booted- If it boots fine, then try the ROM again and pick Google and/or Tmobile to isolate any issues (things that are breaking)
Have you used ONLY what I provided, such as ODIN (version is important), etc?
Re Flashfire: Default options should be fine. The ROM script will set all the partitions, mounts, permissions, etc.
Good luck!
*Above response I guess is for overall troubleshooting the ROM, if any issues present themselves.
On another note: I'm actively working on this ROM as time allows. Trying to ease the install process, correct some issues, further customize, & improve...
Click to expand...
Click to collapse
So I did let it sit for a long time, maybe like 30 mins, but nothing happened. So I tried again from installing from stock and repeating each step. I'm using the odin files you supplied. Same thing. I was using install Google Apps and No T-mobile apps, and interactive governor for both situations. Stuck on boot animation screen. I did not try the options you suggested above since I eventually got it to work. So while stuck on the boot animation screen, I just ended up holding the Vol down, power and home until it rebooted and said entering recovery mode and let go before it went into download mode. From there I just wiped data, and cache, which may not be necessary, and then rebooted, and everything works. Thanks.

infamouz421 said:
So I did let it sit for a long time, maybe like 30 mins, but nothing happened. So I tried again from installing from stock and repeating each step. I'm using the odin files you supplied. Same thing. I was using install Google Apps and No T-mobile apps, and interactive governor for both situations. Stuck on boot animation screen. I did not try the options you suggested above since I eventually got it to work. So while stuck on the boot animation screen, I just ended up holding the Vol down, power and home until it rebooted and said entering recovery mode and let go before it went into download mode. From there I just wiped data, and cache, which may not be necessary, and then rebooted, and everything works. Thanks.
Click to expand...
Click to collapse
That's odd since the installer does exactly that. But I added this to the guide. Thanks for the feedback!

Thanks for the tutorial. Deeply appreciate the effort you put in foraging the resources and putting all the pieces together. The rom works great and all but I can't seem to get the lockscreen to display the wallpaper. It's just black lol. The adaptive clock works however. Would be grateful if you could drop a fix for this.

Alkan3 said:
Thanks for the tutorial. Deeply appreciate the effort you put in foraging the resources and putting all the pieces together. The rom works great and all but I can't seem to get the lockscreen to display the wallpaper. It's just black lol. The adaptive clock works however. Would be grateful if you could drop a fix for this.
Click to expand...
Click to collapse
(Not sure why I didn't get an email from XDA for this post.) Mind walking me through the exact place this setting is? Here? PhoneSettings->Lock screen and security->Clock and Facewidgets->Clock Style->Select a style for "Lock screen" tab at top->Done? (Im able to get these to work)
BTW, Im glad you found this thread resourceful! & Im working on another one, which will be better & more original. Takes a TON of time!

Hey i have two questions, if i'm on oreo already do i need to flash base? And, does this need an unlocked bootloader?

nam2amna said:
Hey i have two questions, if i'm on oreo already do i need to flash base? And, does this need an unlocked bootloader?
Click to expand...
Click to collapse
Your stock oreo should work without issues but I always flash his stock firmware just in case(it's smoother too I think). And no, it doesnt require an unlocked bootloader.
Oh and happy modding

Alkan3 said:
Your stock oreo should work without issues but I always flash his stock firmware just in case(it's smoother too I think). And no, it doesnt require an unlocked bootloader.
Oh and happy modding
Click to expand...
Click to collapse
There are a couple ways an installer can work for custom rom mods like this: start with base then remove everything we don't want. OR: delete everything then add in what we want. This rom happens to work with the latter method. You can see why the base would be so important with the first method. (Because if we don't start with a given base then we can't predict the results because we don't know what u froze or deleted). Regardless, for expected & reliable results, I would always start with an Odin flash of stock for a rom like this. Roms like this are different than vanilla AOSPs because we strip what Samsung & tmobile brewed up, and we often then refer to it as a hybrid- as opposed to vanilla aosp which would be google only & only Samsung for drivers, etc. Hope that helps.

Btw I'm working on another rom with tmobile wifi calling working. I had to start from scratch, literally to get it working. Btw I'm curious if anyone else got it to work after the fact with a custom rom. If so, PLEASE chime in & let me know. Thanks!

[GUIDE] Full process of installing Magisk & TWRP on a OnePlus 7 Pro (TMOBILE SUPPORT)

For me, pwning my new phone was a 7-hour process that required incredible learning capacity. Not everyone is prepared to go through a process like that, and it can easily take multiple days or weeks. This is a guide outlining a version of the exact process that got me to this point. It should be easy for anyone to follow, even people without much technical knowledge. (although, do be careful with the resulting root access)
I started with a GM1915, which is the T-Mobile model. You'd think it would require an unlock key from T-Mobile in order to work, but actually it doesn't. That's what they don't want you to know.
A well-known method for bypassing that requirement is to install an international OS and then upgrade it to a certain developer preview, causing the phone to update the bootloader to a non-crippled version that doesn't require an unlock key. So that's what I did.
However, the process is easier said than done. For someone like me who's done it, it's not too hard, but for a beginner it's intensely confusing. I was a beginner just yesterday and struggled with dumb error messages like "packed image not exist".
The guide is below. Sections starting with "T-MOBILE ONLY" and ending with "END OF T-MOBILE ONLY" are only to be performed on T-Mobile phones with T-Mobile firmware and a locked bootloader. If you have an unlocked bootloader then you can skip those steps.
Make sure you have a Windows machine. The Qualcomm drivers are only available for Windows, the programs are only available for Windows, people on this forum only know Windows. I have a Mac, personally, because Unix is awesome, but unfortunately nobody has thought about us and all the tools are Windows-only. I am just as disappointed as you, trust me. I used a virtual machine, but YMMV, depending on how good your hypervisor's USB passthrough is. You may want to use bare metal if you only have VirtualBox; it's not worth the effort. You will be hot plugging A LOT, and your phone will show up as many different types of USB devices.
You must have fastboot installed, but ADB is not required.
--- T-MOBILE ONLY ---
Install the "L2 drivers" for the phone. You can find them here. Just install as many of them as you can by right-clicking every `.inf` file you find and clicking Install on each one of them. Some of them will have missing files. Some of them won't have a signature. It doesn't matter, as long as you try every one of them, something will work. For me it was the 64-bit driver, in the 64 folder. All the others are 32-bit.
--- END OF T-MOBILE ONLY ---
You should probably plug the phone into your computer now and install the official OnePlus drivers as well. This is so that you can easily access the phone storage, which will become very important soon. Reboot your computer to apply the driver updates.
--- T-MOBILE ONLY ---
Download the "MSM Download Tool" from here (same link as above). Place it in its own folder. This is crucial because you must now download the guacamole-whatever.7z file and extract the .ots file into the same folder as the MSM Download Tool.
MSM Download Tool always looks in its folder for the image and pops up a cryptic error message if it's not found ("packed image not exist"). This is not very widely documented because MSM Download Tool is often distributed in the same folder as the image anyway. That's not the case when you are forced to download them as separate files.
Note that this is the only time you will have to use MSM Download Tool and all other updates can be installed by the phone itself. On international variants you don't have to do this because the bootloader will already be unlockable, which is why this is T-Mobile only.
You need to start downloading three updates. This patched version of international OOS is where you will start, the developer beta will upgrade the bootloader, and the full downgrade will roll you back so you can start updating. Start the downloads now, but you do not have to wait for them to finish yet; it will be a few steps before you have to use them.
Now is about the time to back up any data you want to keep. Everything on your phone will be wiped by the next step, including bootloader unlock status, all your data, the entire operating system and so on.
Now it's time to install international OOS. Place it inside the folder with MSM Download Tool and then start it up. Uncheck the SHA-256 checkbox!
Unplug your USB cable and THEN turn off your phone completely. If the USB cable is plugged in while it's turned off, it will automatically boot into the charging mode which is not what you want. Have your USB cable, and computer mouse, on the ready. You don't want to waste any time, because this may be physically painful: Hold down both volume buttons at the same time for at least 5 seconds, and then plug the USB cable into your phone. Make sure some COM port appears in the tool, then click the "Start" button in MSM Download Tool WHILE STILL HOLDING THEM DOWN. You can only let the volume buttons go AFTER you click "Start", or else the phone will drop out of EDL mode into fastboot.
The process will take a few minutes depending on how fast your USB connection is. Leave the phone plugged in until it is complete. This also gives time to download those two updates, which are together about four gigabytes in size.
Once MSM Download Tool is done flashing, you can reboot the phone and set it up using the setup wizard. Feel free to move fast and enable nothing. You don't need internet, you don't need a correct clock, you don't need accounts or telemetry or anything like that. All data will be wiped again later.
Use your computer to copy the developer preview update to the phone. Don't copy it to the Download folder or anything, copy it into the root (just inside the internal storage). Go to settings > local updates > settings icon in the top right > local update and update to the developer preview.
Once you're in the developer preview, enable OEM unlocking in developer options, reboot into fastboot mode (I do this by also enabling advanced reboot in developer options) and use fastboot oem unlock. Your bootloader is now unlocked! But we're not nearly done yet, there's still lots to do.
After rebooting, since the unlock wiped the phone, you'll have to set it up again. Just breeze through like before, then copy the rollback zip to the phone just like you did for the developer preview.
Go to local update again and use the rollback. This is required in order to go back to a stable OS that can accept OTAs. After this your data will be wiped. This is the real setup wizard. You can set it up with real data; your data will not be wiped again for the rest of this guide.
--- END OF T-MOBILE ONLY ---
If your bootloader is not already unlocked, enable OEM unlocking in developer options and then run `fastboot oem unlock` in Fastboot mode.
Next, you will want to install Magisk. This is a slightly complex process but once it's done your phone will become fully untethered.
First download a tool called Payload Dumper. Extract the entire archive into its own folder. Get an OTA update for your version of OxygenOS (if your phone is T-Mobile, that is the rollback update you just installed; if you aren't following the T-Mobile guide, you may have to download an OTA update from Google), and use WinRAR or similar to extract the `payload.bin` inside into the payload dumper's input folder.
Run the payload dumper. You don't need to run all of it; wait for "boot" to show up in the console window, then wait until something else shows up and then close the window. Inside the output folder there should be a `boot.img`; there may be other img files but the boot is what we're interested in.
Transfer this boot.img to your device and use Magisk Manager to patch it. Transfer the magisk_patched.img to your computer, reboot the phone into fastboot mode and use `fastboot flash boot magisk_patched.img`. Reboot the phone into Android.
If you start Magisk Manager you should see that Magisk is installed. Great. Next step is to install TWRP.
In my experience, flashing TWRP or using `fastboot boot twrp.img` didn't work. You're not clever if you try installing OxygenOS 9.5.4 which adds `fastboot boot` support to the bootloader; it still won't work. In my experience the only correct way to install TWRP on the OnePlus 7 Pro is to use Magisk.
(Someone in the replies below stated that you need to upgrade all the way to OOS 10 in order to boot TWRP using fastboot. This guide details the easier method using Magisk Manager.)
On the phone, go to the TWRP downloads page for the OnePlus 7 Pro, and download the latest installer. Then flash the zip using Magisk.
Crucially, at the end of the installer log it says "you are now unrooted". DO NOT IGNORE THIS MESSAGE! If you reboot now, Magisk will be gone and the stock ROM will immediately overwrite TWRP. You must use Magisk Manager to reinstall Magisk using a "Direct Install". That way, your boot.img will be patched again and your Magisk (and TWRP) will persist across reboots.
Go ahead and try it out. Reboot a few times, sometimes into recovery, sometimes into Android to test Magisk.
We're still not done yet. Wouldn't you love to stay rooted and still be running the latest version of OxygenOS? I sure would. Next I'll describe the process of applying an OTA update while keeping your root and everything. Thanks to A/B you can stay untethered.
Please note that, if you'd like to proceed with the EU version of OxygenOS, you should go grab 9.5.4 before proceeding to the next step, for example from here (MD5 fcec14e2ec053d67c793a27bfdef17d0), and use local update to install it. (note GM21BA instead of GM21AA) The EU version is supposed to have better privacy options and less bloatware, so that's what I personally went with. Converting your OxygenOS from GM21AA to GM21BA has no harmful side effects and should work on any phone. It affects the OTA you'll receive in the next step, and this is possibly the only chance you'll get to switch (or not). So choose wisely.
You can find other versions of OOS in this XDA post.
Remember to turn off all auto-updating in the OxygenOS settings. You don't want your phone suddenly losing Magisk and TWRP after any old reboot. Then you can use the OxygenOS updater to accept an official OTA update. It will recognize you're rooted and install an entire fresh new system to your inactive slot, which is exactly what we want.
There are two steps you need to perform before rebooting. The first is TWRP persistence and the second is Magisk persistence. For TWRP persistence you need to go into Magisk Manager and flash a module called "TWRP A/B retention script". Then for Magisk persistence you need to go install Magisk again, but this time to the inactive slot. You must do TWRP persistence first.
After this you should be good to go back to the update screen and hit reboot. You should still have TWRP and Magisk, but now on the very latest version of OxygenOS. Customize your phone to your heart's content now; it's all yours.
Recommended tweaks:
- install a Magisk module called "Debloater (Terminal Emulator)". Install a terminal emulator like Termux and use `su` to enter a root shell. Then you can run `debloat` and go through the list of apps, removing things you don't want. Certain services need to be watched out for, like PlayAutoInstallConfig (lets your carrier silently install apps without your consent). You can find tidbits online explaining what certain things do, like this pastebin, or this one. Houdini is the kernel driver which is very important.
- enable MagiskHide and hide yourself from Netflix and other DRM-enabled apps. Also hide yourself from Google Play's snet service.
- there is a Magisk module called F-Droid Privileged Extension, it's quite nice.
- use MagiskHide Props Config to set `net.tethering.noprovisioning=true`. This will prevent the carrier from knowing when you are using hotspot features, so they will not immediately cut your connection
- don't install a custom ROM. OxygenOS is high quality and everything you could ever want from a phone honestly. It has all the drivers and stuff for the phone and all of that cool stuff.
Small curiosities:
- SMT download mode is a special flashing mode used by the factory and it can overwrite things like the IMEI. Don't mess with it, you do not know what you're doing.
- Now that you have the software, you can literally just install a Dual SIM tray and have dual SIMs. Your phone is essentially the same as the international OP7P
- Feel free to post if you have any issues or need help with something.

Thank you mate. This will help out a lot of people coming to one plus such as myself. Only wonder I have about it all is the dual sim. I have 2 imei now but obviously both are the same. So I'm trying to figure out how that would work.

TheMadScientist said:
Thank you mate. This will help out a lot of people coming to one plus such as myself. Only wonder I have about it all is the dual sim. I have 2 imei now but obviously both are the same. So I'm trying to figure out how that would work.
Click to expand...
Click to collapse
Yeah, same here. Dual SIM phones are required to have two IMEI numbers since they technically have two transceivers, one for each SIM. Maybe one day someone will post a guide on how to change your IMEI numbers? You could keep one and change the other.

Today I had a little incident with SafetyNet.
{
"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"
}
I had installed the magisk modules Riru and Riru - EdXposed. Big mistake. Uninstalling them didn't fix it. Reinstalling the OS didn't fix it. I thought I was totally ****ed. However, toggling MagiskHide off and back on again and clearing Google Play Services' data seems to have fixed it:
Phew. This SafetyNet guide really helped
EDIT: Also make sure to clear Play Store's data so it re-checks your device for certification.

LoganDark said:
Yeah, same here. Dual SIM phones are required to have two IMEI numbers since they technically have two transceivers, one for each SIM. Maybe one day someone will post a guide on how to change your IMEI numbers? You could keep one and change the other.
Click to expand...
Click to collapse
Unfortunately we can't discuss that on xda.

TheMadScientist said:
Unfortunately we can't discuss that on xda.
Click to expand...
Click to collapse
Software spoofing is allowed. EMS flashing is not.

Riru - EdXposed seems to pass SafetyNet if you use HiddenCore module (and DO NOT BLACKLIST GOOGLE SERVICES or else they will not get patched and they will fail you). I haven't checked to see how deep this goes. Perhaps third party apps which do their own SafetyNet check will see through it. Anyone here with experience?
Edit: BAD ADVICE DO NOT USE HIDDENCORE IT WILL BREAK SAFETYNET EVEN MORE

Well I got to say your guide it's good. But the part where you can only install twrp with magisk I got to say no there. All you have to do is use the roll back package and then update your phone with the first update it allows in system update. That should put you on Oxygen os android 10. Then fastboot will work. Did it myself so I know. Best regards

LokifiedMee said:
Well I got to say your guide it's good. But the part where you can only install twrp with magisk I got to say no there. All you have to do is use the roll back package and then update your phone with the first update it allows in system update. That should put you on Oxygen os android 10. Then fastboot will work. Did it myself so I know. Best regards
Click to expand...
Click to collapse
People seem to have mixed luck regarding using fastboot to boot TWRP. I understand upgrading the bootloader can enable additional fastboot capabilities which is why I tried it myself. It didn't work for me so that's why this guide takes the safer/guaranteed approach.
I did only upgrade to a later version of OOS 9, though. It added `fastboot boot` but trying it softlocked the phone.
Note that in either case, the OnePlus 7 Pro's recovery is stored in the boot partition, and flashing a zip using Magisk is easier than flashing one with TWRP.
I have revised the post to acknowledge the alternative method.
(Also, it's worth mentioning that I know anyone following this guide probably knows how to flash a zip in TWRP. I'm not saying that's too complicated, but the guide details the process I followed specifically. There are many other guides online detailing alternative methods, but they did not work for me, which is why I made this one.)

LoganDark said:
People seem to have mixed luck regarding using fastboot to boot TWRP. I understand upgrading the bootloader can enable additional fastboot capabilities which is why I tried it myself. It didn't work for me so that's why this guide takes the safer/guaranteed approach.
I did only upgrade to a later version of OOS 9, though. It added `fastboot boot` but trying it softlocked the phone.
Note that in either case, the OnePlus 7 Pro's recovery is stored in the boot partition, and flashing a zip using Magisk is easier than flashing one with TWRP.
I have revised the post to acknowledge the alternative method.
(Also, it's worth mentioning that I know anyone following this guide probably knows how to flash a zip in TWRP. I'm not saying that's too complicated, but the guide details the process I followed specifically. There are many other guides online detailing alternative methods, but they did not work for me, which is why I made this one.)
Click to expand...
Click to collapse
No worries mate. Just giving you the heads up. Cheers

I'm unsure how to flash twrp using magisk. I used a friend's machine to flash magisk last night but don't have access now. I'm waiting on asusurion to send mine back. I stayed on the beta and updated to the latest. Would flashing or booting into twrp be possible? Thanks for the guide, btw

Leskanic said:
I'm unsure how to flash twrp using magisk. I used a friend's machine to flash magisk last night but don't have access now. I'm waiting on asusurion to send mine back. I stayed on the beta and updated to the latest. Would flashing or booting into twrp be possible? Thanks for the guide, btw
Click to expand...
Click to collapse
Apologies for the late reply.
Download the "twrp-installer" zip file and use Magisk to flash it.
After that, you have to "direct install" Magisk again.

I guess my question is which option do i use in magisk to flash the twrp installer zip file? Do I use the install module from storage option or in the section where you patch files? Could i just use terminal emulator to boot into twrp then flash twrp and magisk while I'm in twrp? Sorry for my ignorance it's been a couple years since I've had Android with an unlocked bootloader and not having my laptop doesn't help

Leskanic said:
I guess my question is which option do i use in magisk to flash the twrp installer zip file? Do I use the install module from storage option or in the section where you patch files? Could i just use terminal emulator to boot into twrp then flash twrp and magisk while I'm in twrp? Sorry for my ignorance it's been a couple years since I've had Android with an unlocked bootloader and not having my laptop doesn't help
Click to expand...
Click to collapse
The TWRP installer zip is just a Magisk module that you can flash by going to the modules section and tapping "install from storage".
Basically, step 1: go into this section and install the twrp-installer zip this way
Step 2: go here
and direct install Magisk like this
Yes, you are installing Magisk again. That is because the TWRP installer overwrote it, and if you rebooted, you would lose root (and the stock ROM would immediately overwrite TWRP, leaving your device completely stock)
As for flashing both things via TWRP, you would probably flash TWRP first and then Magisk. If you can get the phone to boot into TWRP in the first place, yeah it's probably possible and many others have probably installed their TWRP+Magisk that way.

Thanks i didn't realize the twrp installer zip could be flashed as a module. Sorry it's been a while and I'm trying to get back up to speed

I have a few XPrivacyLua hooks that can be used to change your model number to GM1917 (at least to Java apps). It doesn't have any side effects except peace of mind.
Add these using the XPrivacyLua Pro companion app (you don't need to buy Pro to edit hooks), MAKE SURE to enter GM1917 in the model text box and save, enable them for every app including system apps in XPrivacyLua, and reboot.
Enjoy

LoganDark said:
For me, pwning my new phone was a 7-hour process that required incredible learning capacity. Not everyone is prepared to go through a process like that, and it can easily take multiple days or weeks. This is a guide outlining a version of the exact process that got me to this point. It should be easy for anyone to follow, even people without much technical knowledge. (although, do be careful with the resulting root access)
I started with a GM1915, which is the T-Mobile model. You'd think it would require an unlock key from T-Mobile in order to work, but actually it doesn't. That's what they don't want you to know.
A well-known method for bypassing that requirement is to install an international OS and then upgrade it to a certain developer preview, causing the phone to update the bootloader to a non-crippled version that doesn't require an unlock key. So that's what I did.
However, the process is easier said than done. For someone like me who's done it, it's not too hard, but for a beginner it's intensely confusing. I was a beginner just yesterday and struggled with dumb error messages like "packed image not exist".
The guide is below. Sections starting with "T-MOBILE ONLY" and ending with "END OF T-MOBILE ONLY" are only to be performed on T-Mobile phones with T-Mobile firmware and a locked bootloader. If you have an unlocked bootloader then you can skip those steps.
Make sure you have a Windows machine. The Qualcomm drivers are only available for Windows, the programs are only available for Windows, people on this forum only know Windows. I have a Mac, personally, because Unix is awesome, but unfortunately nobody has thought about us and all the tools are Windows-only. I am just as disappointed as you, trust me. I used a virtual machine, but YMMV, depending on how good your hypervisor's USB passthrough is. You may want to use bare metal if you only have VirtualBox; it's not worth the effort. You will be hot plugging A LOT, and your phone will show up as many different types of USB devices.
You must have fastboot installed, but ADB is not required.
--- T-MOBILE ONLY ---
Install the "L2 drivers" for the phone. You can find them here. Just install as many of them as you can by right-clicking every `.inf` file you find and clicking Install on each one of them. Some of them will have missing files. Some of them won't have a signature. It doesn't matter, as long as you try every one of them, something will work. For me it was the 64-bit driver, in the 64 folder. All the others are 32-bit.
--- END OF T-MOBILE ONLY ---
You should probably plug the phone into your computer now and install the official OnePlus drivers as well. This is so that you can easily access the phone storage, which will become very important soon. Reboot your computer to apply the driver updates.
--- T-MOBILE ONLY ---
Download the "MSM Download Tool" from here (same link as above). Place it in its own folder. This is crucial because you must now download the guacamole-whatever.7z file and extract the .ots file into the same folder as the MSM Download Tool.
MSM Download Tool always looks in its folder for the image and pops up a cryptic error message if it's not found ("packed image not exist"). This is not very widely documented because MSM Download Tool is often distributed in the same folder as the image anyway. That's not the case when you are forced to download them as separate files.
Note that this is the only time you will have to use MSM Download Tool and all other updates can be installed by the phone itself. On international variants you don't have to do this because the bootloader will already be unlockable, which is why this is T-Mobile only.
Start the MSM Downloader tool and make sure that it's open and ready. Uncheck the SHA-256 checkbox!
You need to start downloading two updates. The developer beta will upgrade the bootloader, and the full downgrade will give you a reference boot.img to use for Magisk. Start the downloads now, but you do not have to wait for them to finish yet; it will be a few steps before you have to use them.
Now is about the time to back up any data you want to keep. Everything on your phone will be wiped by the next step, including bootloader unlock status, all your data, the entire operating system and so on.
Unplug your USB cable and THEN turn off your phone completely. If the USB cable is plugged in while it's turned off, it will automatically boot into the charging mode which is not what you want. Have your USB cable, and computer mouse, on the ready. You don't want to waste any time, because this may be physically painful: Hold down both volume buttons at the same time for at least 5 seconds, and then plug the USB cable into your phone. Make sure some COM port appears in the tool, then click the "Start" button in MSM Download Tool WHILE STILL HOLDING THEM DOWN. You can only let the volume buttons go AFTER you click "Start", or else the phone will drop out of MSM mode.
The process will take a few minutes depending on how fast your USB connection is. Leave the phone plugged in until it is complete. This also gives time to download those two updates, which are together about four gigabytes in size.
Once MSM Download Tool is done flashing, you can reboot the phone and set it up using the setup wizard. This one will be overwritten, so feel free to move fast and enable nothing. You don't need internet, you don't need a correct clock, you don't need accounts or telemetry or anything like that. All data will be wiped again later.
Use your computer to copy both updates (developer preview & rollback) to the phone. Don't copy them to the Download folder or anything, copy them into the root. Go to settings > local updates > settings icon in the top right > local update and update to the developer preview.
Once you're in the developer preview, enable OEM unlocking in developer options, reboot into fastboot mode (I do this by also enabling advanced reboot in developer options) and use `fastboot oem unlock`. Your bootloader is now unlocked! But we're not nearly done yet, there's still lots to do.
Go to local update again and use the rollback. This is required in order to go back to a stable OS that can accept OTAs. After this your data will be wiped. This is the real setup wizard. You can set it up with real data; your data will not be wiped again for the rest of this guide.
--- END OF T-MOBILE ONLY ---
If your bootloader is not already unlocked, enable OEM unlocking in developer options and then run `fastboot oem unlock` in Fastboot mode.
Next, you will want to install Magisk. This is a slightly complex process but once it's done your phone will become fully untethered.
First download a tool called Payload Dumper. Extract the entire archive into its own folder. Get an OTA update for your version of OxygenOS (if your phone is T-Mobile, that is the rollback update you just installed; if you aren't following the T-Mobile guide, you may have to download an OTA update from Google), and use WinRAR or similar to extract the `payload.bin` inside into the payload dumper's input folder.
Run the payload dumper. You don't need to run all of it; wait for "boot" to show up in the console window, then wait until something else shows up and then close the window. Inside the output folder there should be a `boot.img`; there may be other img files but the boot is what we're interested in.
Transfer this boot.img to your device and use Magisk Manager to patch it. Transfer the magisk_patched.img to your computer, reboot the phone into fastboot mode and use `fastboot flash boot magisk_patched.img`. Reboot the phone into Android.
If you start Magisk Manager you should see that Magisk is installed. Great. Next step is to install TWRP.
In my experience, flashing TWRP or using `fastboot boot twrp.img` didn't work. You're not clever if you try installing OxygenOS 9.5.4 which adds `fastboot boot` support to the bootloader; it still won't work. In my experience the only correct way to install TWRP on the OnePlus 7 Pro is to use Magisk.
(Someone in the replies below stated that you need to upgrade all the way to OOS 10 in order to boot TWRP using fastboot. This guide details the easier method using Magisk Manager.)
On the phone, go to the TWRP downloads page for the OnePlus 7 Pro, and download the latest installer. Then flash the zip using Magisk.
Crucially, at the end of the installer log it says "you are now unrooted". DO NOT IGNORE THIS MESSAGE! If you reboot now, Magisk will be gone and the stock ROM will immediately overwrite TWRP. You must use Magisk Manager to reinstall Magisk using a "Direct Install". That way, your boot.img will be patched again and your Magisk (and TWRP) will persist across reboots.
Go ahead and try it out. Reboot a few times, sometimes into recovery, sometimes into Android to test Magisk.
We're still not done yet. Wouldn't you love to stay rooted and still be running the latest version of OxygenOS? I sure would. Next I'll describe the process of applying an OTA update while keeping your root and everything. Thanks to A/B you can stay untethered.
Please note that, if you'd like to proceed with the EU version of OxygenOS, you should go grab 9.5.4 before proceeding to the next step, for example from here, and use local update to install it. (note GM27BA instead of GM27AA) The EU version is supposed to have better privacy options and less bloatware, so that's what I personally went with. Converting your OxygenOS from GM27AA to GM27BA has no harmful side effects and should work on any phone. It affects the OTA you'll receive in the next step, and this is possibly the only chance you'll get to switch (or not). So choose wisely.
Remember to turn off all auto-updating in the OxygenOS settings. You don't want your phone suddenly losing Magisk and TWRP after any old reboot. Then you can use the OxygenOS updater to accept an official OTA update. It will recognize you're rooted and install an entire fresh new system to your inactive slot, which is exactly what we want.
There are two steps you need to perform before rebooting. The first is TWRP persistence and the second is Magisk persistence. For TWRP persistence you need to go into Magisk Manager and flash a module called "TWRP A/B retention script". Then for Magisk persistence you need to go install Magisk again, but this time to the inactive slot. You must do TWRP persistence first.
After this you should be good to go back to the update screen and hit reboot. You should still have TWRP and Magisk, but now on the very latest version of OxygenOS. Customize your phone to your heart's content now; it's all yours.
Recommended tweaks:
- install a Magisk module called "Debloater (Terminal Emulator)". Install a terminal emulator like Termux and use `su` to enter a root shell. Then you can run `debloat` and go through the list of apps, removing things you don't want. Certain services need to be watched out for, like PlayAutoInstallConfig (lets your carrier silently install apps without your consent). You can find tidbits online explaining what certain things do, like this pastebin, or this one. Houdini is the kernel driver which is very important.
- enable MagiskHide and hide yourself from Netflix and other DRM-enabled apps. Also hide yourself from Google Play's snet service.
- there is a Magisk module called F-Droid Privileged Extension, it's quite nice.
- use MagiskHide Props Config to set `net.tethering.noprovisioning=true`. This will prevent the carrier from knowing when you are using hotspot features, so they will not immediately cut your connection
- don't install a custom ROM. OxygenOS is high quality and everything you could ever want from a phone honestly. It has all the drivers and stuff for the phone and all of that cool stuff.
Small curiosities:
- SMT download mode is a special flashing mode used by the factory and it can overwrite things like the IMEI. Don't mess with it, you do not know what you're doing.
- Now that you have the software, you can literally just install a Dual SIM tray and have dual SIMs. Your phone is essentially the same as the international OP7P
- Feel free to post if you have any issues or need help with something.
Click to expand...
Click to collapse
It isn't very clear what version of OOS you started on. If I'm running OOS10 on stock this should still (in theory) work right?

r4w0ne said:
It isn't very clear what version of OOS you started on. If I'm running OOS10 on stock this should still (in theory) work right?
Click to expand...
Click to collapse
OOPS, fuck, I missed a step. You have to use MSM Download Tool to clean install this patched OOS before installing the developer preview. I'll update the post ASAP
Edit: Post has been updated

LoganDark said:
OOPS, ****, I missed a step. You have to use MSM Download Tool to clean install this patched OOS before installing the developer preview. I'll update the post ASAP
Click to expand...
Click to collapse
Glad I asked lol.

r4w0ne said:
Glad I asked lol.
Click to expand...
Click to collapse
I actually mentioned installing international OOS in the post but for some reason I didn't link it or provide instructions. Silly me...
Edit: Post has been updated

LoganDark said:
I actually mentioned installing international OOS in the post but for some reason I didn't link it or provide instructions. Silly me...
Edit: Post has been updated
Click to expand...
Click to collapse
New problem, OEM unlocking is greyed out in the options on the developer preview...
EDIT: I'm a retard and didn't follow instructions. Ignore.

Is it possible to install gapps on the Android 11 beta?

Have some free time this coming weekend and was considering installing the android 11 beta posted here
Reading around this forum I've seen people have had issues installing gapps.
Has anyone managed to install gapps successfully? If not, I will stay on the NX627J_CNCommon_V2.23 build.
Thanks in advance.
EDIT:
I have now upgraded to Android 11 and installed google apps, here's how I did it.
The usual disclaimers apply: DO NOT DO THIS IF YOU ARE NOT FAMILIAR WITH ADB, FASTBOOT ETC. I will not be held responsible for bricked devices.
If you wish to void your warranty the command to unlock the bootloader and allow flashing with fasboot the command is "fastboot oem nubia_unlock NUBIA_NX627J"
1. Backup the data you want to keep from your phone. Wipe the phone using stock recovery or TWPR
2. Upgrade to 2.24 using full zip. As I had previously rooted my device so the stock recovery wasn't working and I had to flash TWRP.
3. Upgrade to 3.11 using full zip. Either use the stock recovery or TWRP. This will be the last time you can use TWRP for flashing due to changes in Android 11. TWRP does not support Android 11 yet. If I'd have realised this before I would have tried to flashed google apps at this step. Can't confirm if this works but I wish I'd have tried it.
4. If you need root, install the APK for magisk "canary" (or any version that supports patching boot.img)
5. Open the zip for 3.11 and extract boot.img, copy to your device
6. Patch the boot.img using Magisk. I used these instructions. Reboot.
7. Congratluations, you have Android 11 with root!
If you need gapps and didn't install them yet, it's still possible. Flashing without TWRP was a challenge, but after a lot of hours wasted, I found that BiTG apps was working which I downloaded from this page. I flashed using EX Kernel Manager but I would imagine other apps that allow root flashing will work similarly.
Currently, I have not been able to get SafetyNet checks to pass. I will update this thread with details as I uncover them.
For WhatsApp verfication to pass make sure you have granted Google services framework SMS permissions.
Hope this is helpful for some people who are thinking about making the move to Android 11. No major issues to report yet, will update this thread if anything comes up.
EDIT 2021/02/22: I have repeated this process successfully for V3.15.

thais rom support to flash twrp or google app?

someone who helps? very ugly problem that notifications from whatsapp do not arrive

mmason75123 said:
Have some free time this coming weekend and was considering installing the android 11 beta posted here
Reading around this forum I've seen people have had issues installing gapps.
Has anyone managed to install gapps successfully? If not, I will stay on the NX627J_CNCommon_V2.23 build.
Thanks in advance
Click to expand...
Click to collapse
All work fine in this version (NX627J_CNCommon_V2.23 build)? notifications whatsapp? names of calls?

updated OP now, I have finally managed to upgrade to Android 11!

mmason75123 said:
Have some free time this coming weekend and was considering installing the android 11 beta posted here
Reading around this forum I've seen people have had issues installing gapps.
Has anyone managed to install gapps successfully? If not, I will stay on the NX627J_CNCommon_V2.23 build.
Thanks in advance.
EDIT:
I have now upgraded to Android 11 and installed google apps, here's how I did it.
The usual disclaimers apply: DO NOT DO THIS IF YOU ARE NOT FAMILIAR WITH ADB, FASTBOOT ETC. I will not be held responsible for bricked devices.
1. Backup the data you want to keep from your phone. Wipe the phone using stock recovery or TWPR
2. Upgrade to 2.24 using full zip. As I had previously rooted my device so the stock recovery wasn't working and I had to flash TWRP.
3. Upgrade to 3.11 using full zip. Either use the stock recovery or TWRP. This will be the last time you can use TWRP for flashing due to changes in Android 11. TWRP does not support Android 11 yet. If I'd have realised this before I would have tried to flashed google apps at this step. Can't confirm if this works but I wish I'd have tried it.
4. If you need root, install the APK for magisk "canary" (or any version that supports patching boot.img)
5. Open the zip for 3.11 and extract boot.img, copy to your device
6. Patch the boot.img using Magisk. I used these instructions. Reboot.
7. Congratluations, you have Android 11 with root!
If you need gapps and didn't install them yet, it's still possible. Flashing without TWRP was a challenge, but after a lot of hours wasted, I found that BiTG apps was working which I downloaded from this page. I flashed using EX Kernel Manager but I would imagine other apps that allow root flashing will work similarly.
Currently, I have not been able to get SafetyNet checks to pass. I will update this thread with details as I uncover them.
For WhatsApp verfication to pass make sure you have granted Google services framework SMS permissions.
Hope this is helpful for some people who are thinking about making the move to Android 11. No major issues to report yet, will update this thread if anything comes up.
Click to expand...
Click to collapse
how can i unbloat this **** and get the stock rom? Are they going to release a global rom android 11?

B4$Q said:
how can i unbloat this **** and get the stock rom? Are they going to release a global rom android 11?
Click to expand...
Click to collapse
you can uninstall most of the bloat without root, and even more of it with
obviously I don't work for nubia but at this point a global ROM seems a way off, especially given there has been nothing since 2.03
here is the forum post for release 3.11
【2020年11月30日】Android R V311 for Z20 小批量更新公告-努比亚Z20-努比亚/红魔社区 - 手机版

mmason75123 said:
you can uninstall most of the bloat without root, and even more of it with
obviously I don't work for nubia but at this point a global ROM seems a way off, especially given there has been nothing since 2.03
here is the forum post for release 3.11
【2020年11月30日】Android R V311 for Z20 小批量更新公告-努比亚Z20-努比亚/红魔社区 - 手机版
Click to expand...
Click to collapse
I want to make it stock. Is there a tutorial for that? Their rom has too many issues, including the notifications and that ugly skin with their useless chinese features.

B4$Q said:
I want to make it stock. Is there a tutorial for that? Their rom has too many issues, including the notifications and that ugly skin with their useless chinese features.
Click to expand...
Click to collapse
"stock" for this phone is what you have installed now. There is no custom ROM, which is your real complaint. To be honest, I would also much prefer a custom ROM, if you find one let me know! Anyway this is completely off topic for this thread

mmason75123 said:
"stock" for this phone is what you have installed now. There is no custom ROM, which is your real complaint. To be honest, I would also much prefer a custom ROM, if you find one let me know! Anyway this is completely off topic for this thread
Click to expand...
Click to collapse
Yeah, stock is what I have installed right now, which is Android 9. I would like to get the stock Android 11, without their skin. Maybe a GSI rom could fix it, but I was not able to install it. As soon as you flash the gsi rom on nubia ui 8, the system breaks.

B4$Q said:
Yeah, stock is what I have installed right now, which is Android 9. I would like to get the stock Android 11, without their skin. Maybe a GSI rom could fix it, but I was not able to install it. As soon as you flash the gsi rom on nubia ui 8, the system breaks.
Click to expand...
Click to collapse
Yeah I hear you - it's incredibly annoying that you can't set the default launcher to anything else. Well, I'm sure you can probably! But I'm going to leave my phone to settle for a few days at least before messingw ith it any more
Good luck.

mmason75123 said:
Yeah I hear you - it's incredibly annoying that you can't set the default launcher to anything else. Well, I'm sure you can probably! But I'm going to leave my phone to settle for a few days at least before messingw ith it any more
Good luck.
Click to expand...
Click to collapse
I'll stay on Android 9 for the moment, but I will never buy from this brand again. Apple proved me again that their phones are the best from the market. And Google Phones of course.

I have updated my phone from Android 9 to Android 11 V3.11 everything works fine but can I install gapps and how?

mmason75123 said:
Have some free time this coming weekend and was considering installing the android 11 beta posted here
Reading around this forum I've seen people have had issues installing gapps.
Has anyone managed to install gapps successfully? If not, I will stay on the NX627J_CNCommon_V2.23 build.
Thanks in advance.
EDIT:
I have now upgraded to Android 11 and installed google apps, here's how I did it.
The usual disclaimers apply: DO NOT DO THIS IF YOU ARE NOT FAMILIAR WITH ADB, FASTBOOT ETC. I will not be held responsible for bricked devices.
1. Backup the data you want to keep from your phone. Wipe the phone using stock recovery or TWPR
2. Upgrade to 2.24 using full zip. As I had previously rooted my device so the stock recovery wasn't working and I had to flash TWRP.
3. Upgrade to 3.11 using full zip. Either use the stock recovery or TWRP. This will be the last time you can use TWRP for flashing due to changes in Android 11. TWRP does not support Android 11 yet. If I'd have realised this before I would have tried to flashed google apps at this step. Can't confirm if this works but I wish I'd have tried it.
4. If you need root, install the APK for magisk "canary" (or any version that supports patching boot.img)
5. Open the zip for 3.11 and extract boot.img, copy to your device
6. Patch the boot.img using Magisk. I used these instructions. Reboot.
7. Congratluations, you have Android 11 with root!
If you need gapps and didn't install them yet, it's still possible. Flashing without TWRP was a challenge, but after a lot of hours wasted, I found that BiTG apps was working which I downloaded from this page. I flashed using EX Kernel Manager but I would imagine other apps that allow root flashing will work similarly.
Currently, I have not been able to get SafetyNet checks to pass. I will update this thread with details as I uncover them.
For WhatsApp verfication to pass make sure you have granted Google services framework SMS permissions.
Hope this is helpful for some people who are thinking about making the move to Android 11. No major issues to report yet, will update this thread if anything comes up.
Click to expand...
Click to collapse
You may want to add in the instructions the command to unlock the bootloader of the z20 since users wouldn't be able to flash otherwise.
I managed to get this working and trying to de-china-fy to have english only. Will report back if I can somehow replace the default launcher.
Edit: got a my total launcher running by placing the apk inside the folder where the default nubia launcher is sitting. With root, just place the apk under system/app/nubia launcher folder. It's not working 100% perfect for me as nubia edge gestures stop letting me pull up recent apps so I can't multi task anymore

aso89 said:
I have updated my phone from Android 9 to Android 11 V3.11 everything works fine but can I install gapps and how?
Click to expand...
Click to collapse
See OP "If you need gapps", here's the link again to get them again. BiTGApps-arm64-11.0.0-R17_signed-20200923.zip is the name of the file I have.
[GAPPS] Download GApps for Android 11 (JUNE 2021 UPDATE)
Google Apps (GApps) for Android 11 based ROMs needs to be flashed separately. Here is a direct link to download Android 11 compatible GApps.
www.cyanogenmods.org

xda-nitro said:
You may want to add in the instructions the command to unlock the bootloader of the z20 since users wouldn't be able to flash otherwise.
I managed to get this working and trying to de-china-fy to have english only. Will report back if I can somehow replace the default launcher.
Edit: got a my total launcher running by placing the apk inside the folder where the default nubia launcher is sitting. With root, just place the apk under system/app/nubia launcher folder. It's not working 100% perfect for me as nubia edge gestures stop letting me pull up recent apps so I can't multi task anymore
Click to expand...
Click to collapse
Thanks that's a good idea, I'll try it out. Can you explain a little more around the gestures issue, is it that you show the navbar and the nubia controls are now somehow in the way? I've been a fan of the nubia navigation since I gave it a go and became used to it. Having the back button at any point in the screen is useful I find.
I've added the command to unlock the bootloader to the OP btw.

mmason75123 said:
Thanks that's a good idea, I'll try it out. Can you explain a little more around the gestures issue, is it that you show the navbar and the nubia controls are now somehow in the way? I've been a fan of the nubia navigation since I gave it a go and became used to it. Having the back button at any point in the screen is useful I find.
I've added the command to unlock the bootloader to the OP btw.
Click to expand...
Click to collapse
With the stock nubia launcher even with the Chinese app taken out, swiping left always tries to get you to the Chinese google feed like page. I didn't care for that so I replaced the launcher with total launcher which worked.
The problem is that the swipe up gesture that usually pull up the recent apps to allow switching between application is not working. Even switching the navigation from gestures to 3 button navigation and pressing the recent apps button does nothing.
Perhaps I took one too many Chinese system apps out which caused this error or it is somehow tied into system and nubia launcher itself. Will have to test further.

xda-nitro said:
With the stock nubia launcher even with the Chinese app taken out, swiping left always tries to get you to the Chinese google feed like page. I didn't care for that so I replaced the launcher with total launcher which worked.
The problem is that the swipe up gesture that usually pull up the recent apps to allow switching between application is not working. Even switching the navigation from gestures to 3 button navigation and pressing the recent apps button does nothing.
Perhaps I took one too many Chinese system apps out which caused this error or it is somehow tied into system and nubia launcher itself. Will have to test further.
Click to expand...
Click to collapse
Thanks makes sense. Yes it sounds like you've uninstalled the Recents app, either reinstate or there are alternatives out there I believe

mmason75123 said:
Thanks makes sense. Yes it sounds like you've uninstalled the Recents app, either reinstate or there are alternatives out there I believe
Click to expand...
Click to collapse
Just to confirm, I have just tried to set a new default launcher as you suggest above by replacing the APK. Replacing with SmartLauncher I couldn't return to the home screen using the swipe up gesture so have rolled back.

mmason75123 said:
Just to confirm, I have just tried to set a new default launcher as you suggest above by replacing the APK. Replacing with SmartLauncher I couldn't return to the home screen using the swipe up gesture so have rolled back.
Click to expand...
Click to collapse
It's weird, the recent apps and swipe up are linked to the nubia launcher for some reason. Despite this, I'm staying with with my launcher as I can't stand the apple like nature of the nubia launcher. I think I have managed to get rid of all the Chinese apps though so all good for now.

xda-nitro said:
It's weird, the recent apps and swipe up are linked to the nubia launcher for some reason. Despite this, I'm staying with with my launcher as I can't stand the apple like nature of the nubia launcher. I think I have managed to get rid of all the Chinese apps though so all good for now.
Click to expand...
Click to collapse
Do you get notifications from apps? When I had that rom, I was not receiving any notification.

General MIUI 13 Same bad software with new problems

Hello people unfortunately I just updated to MIUI 13.0.1 on my 11t pro to find out that Xiaomi's promise of a good software are still not true. There are some problems that 12.5 had that are still present and there are new ones.
The problem that persist (in my case) are:
- Dark mode per app selection doesn't work. It never lists the apps. (I had a workaround with MIUI 12. If I searched for dark mode on settings and selected "more dark mode..." it listed the apps, but it was removed or bugged with updates)
NEW Problems:
- Wallpaper flickers when unlocking the phone.
- Beautiful blur effect on notification shade (take a look at the screenshots)
- Both problems tested with system launcher and Nova 7.
Of course there might be more, but those are the ones I've noticed just after updating. The blur effect is the most annoying thing, maybe it's a problem with the video driver or something.
Just let me know if you're facing the same issues or if I'm the only one.
Someone suggested, with another problem I had, flashing the Rom or a clean install would be a good idea. But please guide me if you can. I'm not unlocked nor rooted.

https://xiaomi.eu/community/threads/i-cant-change-apps-individually-in-dark-mode.58435/ - Try this for dark mode
Have you tried to update system apps? Might be an update issue with the wallpaper app

bendavidi said:
https://xiaomi.eu/community/threads/i-cant-change-apps-individually-in-dark-mode.58435/ - Try this for dark mode
Have you tried to update system apps? Might be an update issue with the wallpaper app
Click to expand...
Click to collapse
That trick didn't work for me. Tried multi window thing but the app never got listed.
Of course I've already updated everything and in fact there was an update for the wallpaper app, but either way the problems are still there.
Can I downgrade to 12.5 enhanced?

Vaizen said:
That trick didn't work for me. Tried multi window thing but the app never got listed.
Of course I've already updated everything and in fact there was an update for the wallpaper app, but either way the problems are still there.
Can I downgrade to 12.5 enhanced?
Click to expand...
Click to collapse
Yep. If your bootloader is unlocked,
download your fastboot rom from https://xiaomifirmwareupdater.com/miui/vili/
and flash it in fastboot, prolly better to wipe all data before doing this
BE SURE to back up your data
Swift Backup - Apps on Google Play
A simple, fast and smart backup solution for Android smartphones
play.google.com
I use this app to back up my so it would be easy to recover my phone if i mess up anything

bendavidi said:
Yep. If your bootloader is unlocked,
download your fastboot rom from https://xiaomifirmwareupdater.com/miui/vili/
and use https://github.com/Szaki/XiaomiADBFastbootTools to flash it in fastboot
BE SURE to back up your data
Click to expand...
Click to collapse
Thanks dude. I haven't unlocked my bootloader. If I can't find a solution at least for the blur effect I'll have to unlock it.
Xiaomi is making sure that this is my first and last xiaomi device. What a good hardware with such a terrible software.

Vaizen said:
Thanks dude. I haven't unlocked my bootloader. If I can't find a solution at least for the blur effect I'll have to unlock it.
Xiaomi is making sure that this is my first and last xiaomi device. What a good hardware with such a terrible software.
Click to expand...
Click to collapse
Yeah it is a pain in the ass man but it what it is, a dicky move by Xiaomi indeed
Good luck hope you can fix your problem

xiaomi staff is garbage. period. they are the biggest brand out there now and they havent managed to make a single decent version of miui. i hope an aosp based rom comes out soon so i can get rid of this garbage OS and actually use my phone. that is inspite of all the hardware problems those cheap bastards have left in

Note that V13.0.1.0.SKDMIXM is a stable Beta and that it does not change much since in general Xiaomi later renames it Stable without changing anything.

ConstantinosM said:
xiaomi staff is garbage. period. they are the biggest brand out there now and they havent managed to make a single decent version of miui. i hope an aosp based rom comes out soon so i can get rid of this garbage OS and actually use my phone. that is inspite of all the hardware problems those cheap bastards have left in
Click to expand...
Click to collapse
How to install custom roms (GSI) 11T > Pro
How to install a gsi onto your Mi 11t > Pro This will wipe your phone and I'm not responsible for any bricked device's. you can always go back to stock and try again. Clean install suggested! 1.0 Start with downloading things Latest...
forum.xda-developers.com
tried this?

Patched a boot image for the global ROM if you are interested
Root MIUI 13 Global
Rom Used: https://xiaomifirmwareupdater.com/miui/vili/stable beta/V13.0.1.0.SKDMIXM/ Method Used: https://www.droidwin.com/extract-payload-bin-stock-boot-image/#The_Need_to_Extract_payload_bin_File_using_PC Images: Untouched Boot Image...
forum.xda-developers.com

Thank you all for the comments and contribution.
Well as an update first of all I just found another big improvement xiaomi software engineers made to the UI clearly visible on the Spotify app (check the screenshot) all buttons are messed up.
Secondly, well I can without the per app dark mode option and as a workaround for the beautiful blur effect on the notification shade. I switched to the "old version" of the control center and on Developer options disabled "Allow window-level blurs" on the "Hardware accelerated rendering" section.
It's not a perfect solution, but in the meantime it makes the problem manageable.
Probably I'll unlock the bootloader and try some Roms, because waiting for an update and for xiaomi to fix this issue, probably my warranty will expire first so... flashing it is

Vaizen said:
Thank you all for the comments and contribution.
Well as an update first of all I just found another big improvement xiaomi software engineers made to the UI clearly visible on the Spotify app (check the screenshot) all buttons are messed up.
Secondly, well I can without the per app dark mode option and as a workaround for the beautiful blur effect on the notification shade. I switched to the "old version" of the control center and on Developer options disabled "Allow window-level blurs" on the "Hardware accelerated rendering" section.
It's not a perfect solution, but in the meantime it makes the problem manageable.
Probably I'll unlock the bootloader and try some Roms, because waiting for an update and for xiaomi to fix this issue, probably my warranty will expire first so... flashing it is
Click to expand...
Click to collapse
No problem
I use Spotify and have no problems, so try and clean reinstall
- As for Dark Mode:
[APP][ROOT/SHIZUKU][10+][11/Feb] DarQ: Per-app selectable force dark option for Android 10+
DarQ provides a per-app selectable force dark option for Android 10 and above. It uses a root or Shizuku (ADB) service to apply the theme seamlessly and quickly, without needing an accessibility service. DarQ also provides an option to apply...
forum.xda-developers.com
This and LSPosed (https://github.com/LSPosed/LSPosed) [You don't need to install Riru as Magisk 24.1 uses Zygisk instead of it] works perfectly, although it might not work as well as the native MIUI feature on some apps
If you can't force dark from the DarQ menu, try from the LSPosed menu
Hope that helps you

bendavidi said:
No problem
I use Spotify and have no problems, so try and clean reinstall
- As for Dark Mode:
[APP][ROOT/SHIZUKU][10+][11/Feb] DarQ: Per-app selectable force dark option for Android 10+
DarQ provides a per-app selectable force dark option for Android 10 and above. It uses a root or Shizuku (ADB) service to apply the theme seamlessly and quickly, without needing an accessibility service. DarQ also provides an option to apply...
forum.xda-developers.com
This and LSPosed (https://github.com/LSPosed/LSPosed) [You don't need to install Riru as Magisk 24.1 uses Zygisk instead of it] works perfectly, although it might not work on some apps
If you can't force dark from the DarQ menu, try from the LSPosed menu
Hope that helps you
Click to expand...
Click to collapse
Thanks man for your answers is there a way to clean flash without rooting/unlocking.
In order to unlock the bootloader I have to wait some days, 7 if I'm not wrong, and before trying that maybe factory reset or something similar to Odin on samsung devices?
Just reinstalled Spotify app with no avail, buttons still messed up.

/

bendavidi said:
I don't think you need to unlock the bootloader
Magisk can be flashed in fastboot mode
and the rest require root so give it a try
Click to expand...
Click to collapse
Yeah, I thought I could wait a year and "enjoy" stock MIUI, but given the circumstances, guess I'll have to unlock and endure this crapoy software for the next days until I can unlock.

I have returned to 12.5.1.0 . Too many visual bugs on miui13 for me
and some apps don't work well maybe with android 12 (or miui13)

Vaizen said:
Hello people unfortunately I just updated to MIUI 13.0.1 on my 11t pro to find out that Xiaomi's promise of a good software are still not true. There are some problems that 12.5 had that are still present and there are new ones.
The problem that persist (in my case) are:
- Dark mode per app selection doesn't work. It never lists the apps. (I had a workaround with MIUI 12. If I searched for dark mode on settings and selected "more dark mode..." it listed the apps, but it was removed or bugged with updates)
NEW Problems:
- Wallpaper flickers when unlocking the phone.
- Beautiful blur effect on notification shade (take a look at the screenshots)
- Both problems tested with system launcher and Nova 7.
Of course there might be more, but those are the ones I've noticed just after updating. The blur effect is the most annoying thing, maybe it's a problem with the video driver or something.
Just let me know if you're facing the same issues or if I'm the only one.
Someone suggested, with another problem I had, flashing the Rom or a clean install would be a good idea. But please guide me if you can. I'm not unlocked nor rooted.
Click to expand...
Click to collapse
I recommend factory reset the phone right after updating to miui 13, that's exactly what I did, didn't have any problems mentioned above, except for the dark mode option, my guess is this is not a bug but got completely removed instead.

sushuguru said:
I recommend factory reset the phone right after updating to miui 13, that's exactly what I did, didn't have any problems mentioned above, except for the dark mode option, my guess is this is not a bug but got completely removed instead.
Click to expand...
Click to collapse
Yep, I think I'll try factory reset first if it is still a mess then I'll start the unlock process.

1) Dark mode still got issue..u go to system app updater then u know.
2) Open battery setting, u scroll down then kick u out.
3) scan virus cannot go in.
4) WhatsApp voice message putting on my ear still coming out from loudspeaker. proximity sensor F up.
Last, my phone keep rebooting when playing mobile legend..
NOw searching way how to backup stuff in my phone before wipe data.

I got 0 Bugs with MIUI13
i recommend you to unlock bootloader and get
MIUI 13 - MIUI 13 STABLE RELEASE
Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
11T Pro ROM
https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv13/xiaomi.eu_multi_XM11TPro_V13.0.1.0.SKDMIXM_v13-12-fastboot.zip/download
Installation of A12 devices via Fastboot:
- Download our ROM zip file
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system:
--- For Windows OS - windows_fastboot_update_rom.bat
--- For Linux - linux_fastboot_update_rom.sh
--- For MacOS - macos_fastboot_update_rom.sh
but as a first time install, backup your important stuff and run
windows_fastboot_first_install_with_data_format.bat
it will format the data partition which will fix most of the problems when changing roms.