Develop Bugs

[Q] Very strange recovery issue

I just received my Nexus 7 2013 16gb WiFi from amazon a few days ago, and it's been great. The recovery has had issues though, it tried to do an OTA update the first day I got it, and when it rebooted, it just stayed on a black screen instead of actually going to recovery, so I had to hard reboot it, to get back to the jellybean it came with. This wasn't a major issue at the time, since then I've just unlocked it and flashed kitkat via fastboot (I'll get lollipop once it has gravitybox or something similar). But since then, I've rooted it and installed TWRP, and TWRP runs fine, but has some weird issues. It seems to not actually see the OS at all, or even the storage filesystem. I have to do a hard reboot to even get out of TWRP, as trying to get out normally gives me the error "Warning blah blah no OS installed, are you sure?", to which I tell it I'm sure and it just reboots recovery. But doing a hard reboot boots into the OS just fine. Am I doing something wrong? TWRP was installed AFTER I installed KitKat and the updated bootloader with the official google factory images, is this a problem?
Some images of what I'm seeing:
1
2

Maybe it's because you're running TWRP 2.8.2.0 which is for Lollipop. If it doesn't work with 2.8.1.0, try with the lastest 2.8.2.2. Running Lollipop at least, everyone had the same problem with both 2.8.2.0 and 2.8.2.1.

where can I place the recovery image where twrp will see it?
Thanks for your suggestion LittleConfucy. I was wondering if you can tell me where to put recovery image that TWRP can see it?
Flashing is a problem without being able to access the image to flash in the stripped down rom file system that twrp boots into. No shared directory in /cache.

Nevermind I got it dialed in.
Sent from my Nexus 7 using xda app-developers app

What did you do to fix this? I just had the exact same thing happen. I had a 5.0 rom and tried to flash a different one but once in twrp no files and the no os line when I tried to reboot. I'm on 2.8.2.0

kingston73 said:
What did you do to fix this? I just had the exact same thing happen. I had a 5.0 rom and tried to flash a different one but once in twrp no files and the no os line when I tried to reboot. I'm on 2.8.2.0
Click to expand...
Click to collapse
I just flashed to 2.8.2.2 and twrp started seeing my internal storage again.

el80ne said:
I just flashed to 2.8.2.2 and twrp started seeing my internal storage again.
Click to expand...
Click to collapse
So if I hold power down and force it to reboot it should boot back into the OS? And once in the OS will I be able to use TWRP manager to flash the latest?

kingston73 said:
So if I hold power down and force it to reboot it should boot back into the OS? And once in the OS will I be able to use TWRP manager to flash the latest?
Click to expand...
Click to collapse
That's what I did.
Sent from my SM-G900V using XDA Free mobile app

Does TWRP work on android 7.0?

If I upgrade to 7.0 on my nexus 5x, will i be able to install twrp as i normally would through fastboot?

You need to decrypt the phone for it to work.

Hmm anyone got the 7.0 recovery? I installed it thinking it would work but I want to keep the system encrypted. Does the stock 7.0 recovery mount system? I want to mod my build.prop dpi.

trollyphysicist said:
If I upgrade to 7.0 on my nexus 5x, will i be able to install twrp as i normally would through fastboot?
Click to expand...
Click to collapse
Try TWRP 3.0.2-1, should work properly.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Try TWRP 3.0.2-1, should work properly.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I just tried 3.0.2-1, and it worked. Before that, 3.0.2-0 also got stuck at the splash screen. However, I wasn't able to root. I tried installing SU via TWRP, but it didn't successfully root.

pkadavid said:
I just tried 3.0.2-1, and it worked. Before that, 3.0.2-0 also got stuck at the splash screen. However, I wasn't able to root. I tried installing SU via TWRP, but it didn't successfully root.
Click to expand...
Click to collapse
I had no issues obtaining root with the new twrp on an encrypted phone.

Am I the only one who encounters the flasing of recovery not sticking? After system reboot, then going back to recovery, it reverts to stock.

legendarren said:
Am I the only one who encounters the flasing of recovery not sticking? After system reboot, then going back to recovery, it reverts to stock.
Click to expand...
Click to collapse
Flash twrp, while still in bootloader volume down to reboot bootloader, hit the power button, volume down to reboot recovery, hit the power button. Twrp should stick now.
Sent from my Nexus 5X using Tapatalk

PiousInquisitor said:
Flash twrp, while still in bootloader volume down to reboot bootloader, hit the power button, volume down to reboot recovery, hit the power button. Twrp should stick now.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks, man. But still TWRP still doesn't stick after system reboot.

legendarren said:
Thanks, man. But still TWRP still doesn't stick after system reboot.
Click to expand...
Click to collapse
If you decrypt it first by flashing the modified boot.img, and then flash recovery and reboot it should stick and work right? Can you kindly describe your steps?

Vanschtezla said:
If you decrypt it first by flashing the modified boot.img, and then flash recovery and reboot it should stick and work right? Can you kindly describe your steps?
Click to expand...
Click to collapse
Yes, I forgot about decrypting. It works fine now, thanks!!

legendarren said:
Yes, I forgot about decrypting. It works fine now, thanks!!
Click to expand...
Click to collapse
No problem mate ??

Vanschtezla said:
No problem mate ??
Click to expand...
Click to collapse
Which boot IMG did you use to decrypt the final release of n?

kevtrysmoddin said:
Which boot IMG did you use to decrypt the final release of n?
Click to expand...
Click to collapse
In my case I updated mine from DP5. I had my DP5 decrypted and rooted and update it using the flashfire app to flash the ota. I don't think any of the existing modified boot.img will work on the final release yet idk mate.

Vanschtezla said:
In my case I updated mine from DP5. I had my DP5 decrypted and rooted and update it using the flashfire app to flash the ota. I don't think any of the existing modified boot.img will work on the final release yet idk mate.
Click to expand...
Click to collapse
No probs

trollyphysicist said:
If I upgrade to 7.0 on my nexus 5x, will i be able to install twrp as i normally would through fastboot?
Click to expand...
Click to collapse
Just installed twrp and seeing if flashign super su stuck or not... Have to wait for modified boot images to decrypt, though
---------- Post added at 10:25 AM ---------- Previous post was at 10:14 AM ----------
trollyphysicist said:
If I upgrade to 7.0 on my nexus 5x, will i be able to install twrp as i normally would through fastboot?
Click to expand...
Click to collapse
Update-phone is decrypted after installing twrp, wiping userdate, rebooting twrp, flashing latest super su, rebooting

eggman618 said:
Hmm anyone got the 7.0 recovery? I installed it thinking it would work but I want to keep the system encrypted. Does the stock 7.0 recovery mount system? I want to mod my build.prop dpi.
Click to expand...
Click to collapse
3.0.2-1 TWRP that got released soon after I posted fixed any hanging issues.

eggman618 said:
3.0.2-1 TWRP that got released soon after I posted fixed any hanging issues.
Click to expand...
Click to collapse
-1 installs, but two issues if you're encrypted:
1) TWRP doesn't stick. After a restart, you won't be able to get back into TWRP and need to reflash it.
2) Installing SU via TWRP doesn't work. It runs into an error if you read the responses during the flash in TWRP.
We'll just have to be patient until the devs do their magic on the encrypted version.

pkadavid said:
-1 installs, but two issues if you're encrypted:
1) TWRP doesn't stick. After a restart, you won't be able to get back into TWRP and need to reflash it.
2) Installing SU via TWRP doesn't work. It runs into an error if you read the responses during the flash in TWRP.
We'll just have to be patient until the devs do their magic on the encrypted version.
Click to expand...
Click to collapse
If you root using phh's superuser and magisk, TWRP will stick. His solution also allows you to use Android Pay with root, albeit with a little hoop-jumping
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382

I had the twrp not sticking issue in the past. What has worked is to boot twrp, not flash it, then flash SU. Then boot back into the bootloader and flash twrp.
Sent from my Nexus 9 using XDA-Developers mobile app

Back to stock OxygenOS (OP3)

I found 2 versions of the instruction about going back from custom ROM to stock OxygenOS. First one tells about ADB commands which results with full stock, with standard recovery, unrooted system and locked phone. The second one is shorter, it's just flashing official zip with TWRP.
So my question is: Am I "losing something" after going with the second option, I mean TWRP-way? As I understand the only difference is that I'll keep TWRP itself and my phone will still be unlocked, when everything else will be ok (official camera firmware, kernel, etc.).
Thank you in advance for the answer if I'm wrong

The official zips in most cases also erase your twrp recovery and you will end up with the stock recovery and unlocked bootloader

I'm also thinking about going back to Oxygenos. But haven't done it. Looking for answers for you question.
Besides, could you please give me the link for the first method? Thanks

It's like flashing any other Rom? You clean flash by wiping everything (except Internal) and flash the OxygenOS you want (plus SuperUser).

Heres what you gonna do
Download oos full zip
Flash it on twrp then after that dont do a reboot just flash twrp as recovery then reboot to recovery and then reboot to system
If you wanna lock the bootloader and stay fully stock ( this will wipe your whole phone so backup )
Then flash oos full zip through twrp then reboot to bootloader
Then sideload oos recovery
Then go back to bootloader and relock bootloader thats it
Sent from my ONEPLUS A3003 using Tapatalk

You want to ADB push?
Go to OnePlus site. There you have step by step instructions.

HIshan Pavidu said:
Heres what you gonna do
Download oos full zip
Flash it on twrp then after that dont do a reboot just flash twrp as recovery then reboot to recovery and then reboot to system
If you wanna lock the bootloader and stay fully stock ( this will wipe your whole phone so backup )
Then flash oos full zip through twrp then reboot to bootloader
Then sideload oos recovery
Then go back to bootloader and relock bootloader thats it
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
I want to keep twrp and stay unlocked
1. flash the oos full zip
2. reboot to fastboot mode and flash twrp
3. go to twrp and reboot to system
Is this right?
Besides, I'm using twrp 3.0.4-1. Does it matter?

JonathanKang said:
I want to keep twrp and stay unlocked
1. flash the oos full zip
2. reboot to fastboot mode and flash twrp
3. go to twrp and reboot to system
Is this right?
Besides, I'm using twrp 3.0.4-1. Does it matter?
Click to expand...
Click to collapse
They both works but my way dont need a pc so
Sent from my ONEPLUS A3003 using Tapatalk

HIshan Pavidu said:
They both works but my way dont need a pc so
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Ahh. Got it.

JonathanKang said:
Ahh. Got it.
Click to expand...
Click to collapse
Good luck huh!
Sent from my ONEPLUS A3003 using Tapatalk

HIshan Pavidu said:
Good luck huh!
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
I clean flashed the full zip. When I try to boot to bootloader, it didn't enter bootloader mode. The system boots, and it's been showing boot animation for more than ten minutes. I'll wait patiently.
BTW, how do you flash twrp while you are in twrp?

JonathanKang said:
I clean flashed the full zip. When I try to boot to bootloader, it didn't enter bootloader mode. The system boots, and it's been showing boot animation for more than ten minutes. I'll wait patiently.
BTW, how do you flash twrp while you are in twrp?
Click to expand...
Click to collapse
What i did was
Flashed the full zip
Before rebooting flashed twrp.img through twrp
Then reboot to twrp abd reboot to system i do it every time
Sent from my ONEPLUS A3003 using Tapatalk

HIshan Pavidu said:
What i did was
Flashed the full zip
Before rebooting flashed twrp.img through twrp
Then reboot to twrp abd reboot to system i do it every time
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
What I wanna ask is how do you flash twrp.img through twrp?

JonathanKang said:
What I wanna ask is how do you flash twrp.img through twrp?
Click to expand...
Click to collapse
When your on twrp go to install then to the right corner youll see a tab named flash img clikc that and browse to your twrp flash it then it will ask system , recovery or bootloader click recovery then flash when it finished reboot to recovery
I hope you understand if not just google it
Sent from my ONEPLUS A3003 using Tapatalk

HIshan Pavidu said:
When your on twrp go to install then to the right corner youll see a tab named flash img clikc that and browse to your twrp flash it then it will ask system , recovery or bootloader click recovery then flash when it finished reboot to recovery
I hope you understand if not just google it
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Okay. Never notice that tab in the corner.
So right now, I end up with oxygenos(still booting...) without twrp.

JonathanKang said:
Okay. Never notice that tab in the corner.
So right now, I end up with oxygenos(still booting...) without twrp.
Click to expand...
Click to collapse
Try holding power button till it restart and see if you can load to bootloader then sideload twrp then do what i said
Good luck
If it wont load bootloader i think its bricked or something
Sent from my ONEPLUS A3003 using Tapatalk

HIshan Pavidu said:
Try holding power button till it restart and see if you can load to bootloader then sideload twrp then do what i said
Good luck
If it wont load bootloader i think its bricked or something
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Force shutdown the device and entered fastboot, flashed twrp recovery. And now twrp asks me to input password to decrypt data. I have no idea about what the password is. I also got dm-verity error after flashing the full zip. Help needed.

JonathanKang said:
Force shutdown the device and entered fastboot, flashed twrp recovery. And now twrp asks me to input password to decrypt data. I have no idea about what the password is. I also got dm-verity error after flashing the full zip. Help needed.
Click to expand...
Click to collapse
Im sorry i have to say this but you might wanna sideload oos recovery then sideload oos full zip and see if its boot then try again
Edit :- you might wanna wipe everything before sideload idk try without wiping anything
Sent from my ONEPLUS A3003 using Tapatalk

HIshan Pavidu said:
Im sorry i have to say this but you might wanna sideload oos recovery then sideload oos full zip and see if its boot then try again
Edit :- you might wanna wipe everything before sideload idk try without wiping anything
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
I did a factory reset in twrp, and the system boots well. But unfortunately I lost all my data. Factory reset also formats internal storage?
I have all my photos backed up in google photos. The only loss is the image quality is not original. Anyway it's not end of the world.

JonathanKang said:
I did a factory reset in twrp, and the system boots well. But unfortunately I lost all my data. Factory reset also formats internal storage?
I have all my photos backed up in google photos. The only loss is the image quality is not original. Anyway it's not end of the world.
Click to expand...
Click to collapse
Your good then right? Cuz i gotta go flash rr ?
Sent from my ONEPLUS A3003 using Tapatalk

December update breaks magisk?

Hi all,
I've updated my 3xl to the december update like usual, flash-all.bat without -w. Afterwards, it boots fine, and in settings it clearly states that I'm running the December security patch.
However, when I boot into twrp (not installed) and flash magisk, android boots to just before asking my SIM PIN, says "Shutting Down", then reboots and gives me the message "Can't load Android System. Your data may be corrupt." etc. inside stock recovery.
Did the December update somehow break magisk? Anyone gotten it to work? I'd rather not do a factory reset if it's not needed.

Works fine for me.

Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions

Working fine for me as well.

I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app

You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.

mikepopo99 said:
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Click to expand...
Click to collapse
jd1639 said:
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
TonikJDK said:
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
Click to expand...
Click to collapse
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?

RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Flash the stock boot.img to both slots.
Reboot and check it.
Copy the Magisk zip to your phone.
Fastboot boot the TWRP img file, don't install it.
Use TWRP to install the Magisk zip, and you are done.

RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.

sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!

RogerXIII said:
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
Click to expand...
Click to collapse
Good deal. That is why I always keep a copy of the Magisk uninstaller on the phone itself. As long as I can get to BL/temp TWRP .img, the worst I am out is the time it takes me to reconfigure Magisk.

RogerXIII said:
However, when I boot into twrp (not installed)
Click to expand...
Click to collapse
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1

Shaftamle said:
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Click to expand...
Click to collapse
The TWRP image from the official website, and then simply fastboot boot twrp.img

RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
Ok cool. Wasn't sure if there was an app like fashify or something.
Fire Hound 8.1

sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
you are godsend my friend.

Touz604 said:
you are godsend my friend.
Click to expand...
Click to collapse
Glad you got it figured out.

RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".

bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
You ca't yet.

bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
Thread is from 2018

I am gonna check the official TWRP website for the workable TWRP for my Pixel 3 till I see your post
wangdaning said:
Thread is from 2018
Click to expand...
Click to collapse

10.2.1.0 Global Update Available

Just checked for updates and this popped up. Enjoy.
Link for the download is: http://bigota.d.miui.com/V10.2.1.0.PEEMIXM/miui_MIMIX3Global_V10.2.1.0.PEEMIXM_9dc43870b4_9.0.zip

I just got this too! Do you know how I can update having twrp installed?

I just tried to install the smaller update above, it failed and now I'm downloading a 1.8gb version. Of you have TWRP installed, I'd probably just download the older OTA and fastboot flash boot boot.img from that OTA.

faddys123 said:
I just got this too! Do you know how I can update having twrp installed?
Click to expand...
Click to collapse
You should be able to install it like normal but ensure when your device reboots you enter your password to enter twrp. If that doesn't work just reboot into twrp and install it by selecting it from the downloaded ROM directory (I forget what the folder is called but it's not the normal download folder). You will have to reflash twrp afterwards.

xreactx said:
You should be able to install it like normal but ensure when your device reboots you enter your password to enter twrp. If that doesn't work just reboot into twrp and install it by selecting it from the downloaded ROM directory (I forget what the folder is called but it's not the normal download folder). You will have to reflash twrp afterwards.
Click to expand...
Click to collapse
This *should* would too.
Filename for the big file is: miui_MIMIX3Global_V10.2.1.0.PEEMIXM_9dc43870b4_9.0.zip we should be able to assemble the whole bigota.somethingsomethingsomething.darkside.xiaomi.downloads url using that, but I'm not at a computer and going to be late for work as is.
Sent from my Mi MIX 3 using Tapatalk

Ok got it installed i downloaded the 1.8gb flashed it via twrp then flashed twrp again and installed magisk all it working now ?
Noticed a few new things battery percentage text is now inside the battery icon!
Also there's a new 'suggestions' in the recents view, it can be turned off in the settings

faddys123 said:
Ok got it installed i downloaded the 1.8gb flashed it via twrp then flashed twrp again and installed magisk all it working now
Noticed a few new things battery percentage text is now inside the battery icon!
Also there's a new 'suggestions' in the recents view, it can be turned off in the settings
Click to expand...
Click to collapse
What version of Magisk did you install? I tried 17.3 and have a bootlooping phone.

The URL for the big OTA (1.8gb) is: http://bigota.d.miui.com/V10.2.1.0.PEEMIXM/miui_MIMIX3Global_V10.2.1.0.PEEMIXM_9dc43870b4_9.0.zip

PWn3R said:
What version of Magisk did you install? I tried 17.3 and have a bootlooping phone.
Click to expand...
Click to collapse
Using 17.3 as well mate

faddys123 said:
Using 17.3 as well mate
Click to expand...
Click to collapse
I just tried downloading a fresh copy of the Magisk zip. Same result. The phone starts booting then reboots into recovery. I don't know why this doesn't work. Did you have a "global" version of the phone? If so, can you backup your boot image with TWRP (the Magisk rooted one) and post it so we can try downloading and installing to see if it works on a Chinese phone?

Is it normal for the update size to not be displayed? This is my first update using a Xiaomi device & found it odd to not know how large a update was.

eseanq said:
Is it normal for the update size to not be displayed? This is my first update using a Xiaomi device & found it odd to not know how large a update was.
Click to expand...
Click to collapse
Mine showed the size for the small incremental which failed and for the full OTA which installed sucessfully. I have not been able to root this with Magisk, no matter what I tried. Every attempt at rooting with SuperSU or Magisk caused the device to bootloop and go back to recovery.

PWn3R said:
Mine showed the size for the small incremental which failed and for the full OTA which installed sucessfully. I have not been able to root this with Magisk, no matter what I tried. Every attempt at rooting with SuperSU or Magisk caused the device to bootloop and go back to recovery.
Click to expand...
Click to collapse
Where does the file size show up?

eseanq said:
Where does the file size show up?
Click to expand...
Click to collapse
It showed it in the text right below the MIUI logo on the updates page. Check the screenshot in the OP

PWn3R said:
It showed it in the text right below the MIUI logo on the updates page. Check the screenshot in the OP
Click to expand...
Click to collapse
Oh ****.. I'm guessing its the 599M? For some reason I thought that was part of the build. :laugh: Lmao.

eseanq said:
Oh ****.. I'm guessing its the 599M? For some reason I thought that was part of the build. :laugh: Lmao.
Click to expand...
Click to collapse
Yeah, that's the update download size. Don't be surprised when the 599 one fails to install (if you have stock recovery). It will download a 1.8GB one (the one I linked to in the OP now) and that one will install as expected. I think you can install either with TWRP if you want. GLHF

anyone figured how to root this? I flashed twrp then flash magisk 17.3 but it kept bootlooping to twrp.

No, I've tried everything. I have a suspicion we can root this on the Chinese device after we have fastboot images.
Sent from my Mi MIX 3 using Tapatalk

Great Update! Many things changed that are not mentioned in the changelog! Finaly notifications in the AOD! ?*?*

PWn3R said:
No, I've tried everything. I have a suspicion we can root this on the Chinese device after we have fastboot images.
Sent from my Mi MIX 3 using Tapatalk
Click to expand...
Click to collapse
I think this too.