Develop Bugs

[bricked device] OP3 shows yellow screen

Hey guys,
I think I'm a little bit in trouble: I just got a OP3 and wanted to root it as I'm used to it from the OPO.
But there were problems because of Force Encyption... After a few trys and flashs, I flashed Stock OOS (
OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
) from TWRP and after rebooting...
THE SCREEN IS YELLOW AND FULL OF PIXELS (like an olt TV).
You can feel it works from vibrations but you can't see what's going on... I tried this for unbricking but no success.
I think my phone's display drivers might be broken but idk.
Does anyone maybe know what to do here?

Peybro said:
Hey guys,
I think I'm a little bit in trouble: I just got a OP3 and wanted to root it as I'm used to it from the OPO.
But there were problems because of Force Encyption... After a few trys and flashs, I flashed Stock OOS (
OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
) from TWRP and after rebooting...
THE SCREEN IS YELLOW AND FULL OF PIXELS (like an olt TV).
You can feel it works from vibrations but you can't see what's going on... I tried this for unbricking but no success.
I think my phone's display drivers might be broken but idk.
Does anyone maybe know what to do here?
Click to expand...
Click to collapse
Unbrick guide method 2 should fix it, otherwise ask Oneplus support.

Peybro said:
Hey guys,
I think I'm a little bit in trouble: I just got a OP3 and wanted to root it as I'm used to it from the OPO.
But there were problems because of Force Encyption... After a few trys and flashs, I flashed Stock OOS (
OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
) from TWRP and after rebooting...
THE SCREEN IS YELLOW AND FULL OF PIXELS (like an olt TV).
You can feel it works from vibrations but you can't see what's going on... I tried this for unbricking but no success.
I think my phone's display drivers might be broken but idk.
Does anyone maybe know what to do here?
Click to expand...
Click to collapse
Which TWRP are you using? Try using the latest from eng.stk's (Blue Spark).
If you want MM, the more stable and improved version is 3.2.8. What you downloaded is 3.2.4. So, download 3.2.8 and boot into recovery, wipe system, dalvik cache, cache and data including internal storage (you will lose all your files including photos, videos etc). Boot the phone into the bootloader mode and push the ROM to the phone and flash it from recovery or flash the ROM from PC using adb commands. Flash TWRP again and boot into recovery and if ok, boot into system. If everything is ok, you can flash SuperSU/Magisk, if you need root. A couple of wipes of both the caches in between may also be done.
If this doesn't sort out the issue, use Method 2 from the Mega Unbrick Guide in XDA and follow every instruction scrupulously, especially relating to drivers.
If even this fails, it is a hardware issue.
EDIT: I see that Puddi Puddin beat me to it.

Puddi_Puddin said:
Unbrick guide method 2 should fix it, otherwise ask Oneplus support.
Click to expand...
Click to collapse
tnsmani said:
If this doesn't sort out the issue, use Method 2 from the Mega Unbrick Guide in XDA and follow every instruction scrupulously, especially relating to drivers.
If even this fails, it is a hardware issue.
Click to expand...
Click to collapse
Step 8 doesn't work for me...
I guess the phone goes back to the repair company then
tnsmani said:
Which TWRP are you using? Try using the latest from eng.stk's (Blue Spark).
If you want MM, the more stable and improved version is 3.2.8. What you downloaded is 3.2.4. So, download 3.2.8 and boot into recovery, wipe system, dalvik cache, cache and data including internal storage (you will lose all your files including photos, videos etc). Boot the phone into the bootloader mode and push the ROM to the phone and flash it from recovery or flash the ROM from PC using adb commands. Flash TWRP again and boot into recovery and if ok, boot into system. If everything is ok, you can flash SuperSU/Magisk, if you need root. A couple of wipes of both the caches in between may also be done.
Click to expand...
Click to collapse
I am using the newest (twrp-3.1.1-2-oneplus3.img) but the problem is that I can't see anything in recovery or elsewhere :/

Peybro said:
Step 8 doesn't work for me...
I guess the phone goes back to the repair company then
Click to expand...
Click to collapse
Well you have really messed up something it seems.. This shouldnt be happening by rooting and stuff, I think it is pure coincidence

Peybro said:
Hey guys,
I think I'm a little bit in trouble: I just got a OP3 and wanted to root it as I'm used to it from the OPO.
But there were problems because of Force Encyption... After a few trys and flashs, I flashed Stock OOS (
OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
) from TWRP and after rebooting...
THE SCREEN IS YELLOW AND FULL OF PIXELS (like an olt TV).
You can feel it works from vibrations but you can't see what's going on... I tried this for unbricking but no success.
I think my phone's display drivers might be broken but idk.
Does anyone maybe know what to do here?
Click to expand...
Click to collapse
What exactly did you flash other than OOS and recovery? Why did you need a few flashes? You flashed SuperSU or Magisk? Root still works on an encrypted system so not understanding some things from your post

Puddi_Puddin said:
Well you have really messed up something it seems.. This shouldnt be happening by rooting and stuff, I think it is pure coincidence
Click to expand...
Click to collapse
I hope so - maybe the repair company messed the screen connection up and they fix it for free... :angel:
Renosh said:
What exactly did you flash other than OOS and recovery? Why did you need a few flashes? You flashed SuperSU or Magisk? Root still works on an encrypted system so not understanding some things from your post
Click to expand...
Click to collapse
First I flashed newest TWRP and Paranoid Android but it wasn't as good as expected and so I flashed back to OOS (_008 I think) and everything worked but when I wanted to flash Magisk (because SafetyNet) via TWRP I couldn't because the phone wanted a pattern to unlock encryption.
I read that it would be the same as I used to unlock my phone (btw the only 1 I use) but it didn't work...
Before I found a guide with the right order to remove the encryption I tried different ways by myself (that's because I flashed a few times) (Toolkit, "Fastboot format userdata", TWRP format) but nothing removed it.
Then I wanted to follow that guide but meanwhile there was no OS at all and img Install via fastboot didn't work but I managed to get the newest stable OOS (_16 I think) on the phone, installed it with TWRP aaaaaand...
YELLOW-ORANGEish PIXEL SCREEN
fastboot and everything works - I just can't see what's going on

Peybro said:
I hope so - maybe the repair company messed the screen connection up and they fix it for free... :angel:
First I flashed newest TWRP and Paranoid Android but it wasn't as good as expected and so I flashed back to OOS (_008 I think) and everything worked but when I wanted to flash Magisk (because SafetyNet) via TWRP I couldn't because the phone wanted a pattern to unlock encryption.
I read that it would be the same as I used to unlock my phone (btw the only 1 I use) but it didn't work...
Before I found a guide with the right order to remove the encryption I tried different ways by myself (that's because I flashed a few times) (Toolkit, "Fastboot format userdata", TWRP format) but nothing removed it.
Then I wanted to follow that guide but meanwhile there was no OS at all and img Install via fastboot didn't work but I managed to get the newest stable OOS (_16 I think) on the phone, installed it with TWRP aaaaaand...
YELLOW-ORANGEish PIXEL SCREEN
fastboot and everything works - I just can't see what's going on
Click to expand...
Click to collapse
I already asked you to use the TWRP from eng.stk
The official 3.1.1-2 works well with OOS but is cranky with custom ROMS. eng.stk's works both with OOS and custom ROMs.

tnsmani said:
I already asked you to use the TWRP from eng.stk
The official 3.1.1-2 works well with OOS but is cranky with custom ROMS. eng.stk's works both with OOS and custom ROMs.
Click to expand...
Click to collapse
I can give it a try later (and in the future when everything works again) but I do not think (at least I can't imagine) that the problem I have comes from recovery.

I know the reason!
I found other people who also had a static screen and they said they could fix it by pressing the screen back on its contacts...
I did so and it worked!... A bit... For a few minutes...
So the static definitely wasn't the result of rooting and stuff but the repair company's fault.
I hope they accept their mistake and fix it. Thx for everyone here trying to hel me!
P.S.
tnsmani said:
I already asked you to use the TWRP from eng.stk
The official 3.1.1-2 works well with OOS but is cranky with custom ROMS. eng.stk's works both with OOS and custom ROMs.
Click to expand...
Click to collapse
And as soon as I can I will try this TWRP
-------------------------------- Edit: --------------------------------
(Just in case people get same problem)
[after Mega Unbrick Method 2 finally worked (I put the stock zip in the tool's folder)]
This morning I restarted the phone just because and I could see what was going on on the phone - but the display was still crazy with yellow tint and colorful stripes etc.). After setup it asked me to download & install newest stock rom; I did and after reboot everything was fine again....
Don't know what happened here but it seems to work again.

How to flash PE ROM in MI MIX2S device?

Dear every one, I really like this ROM, but how to flash this ROM?
I try to flash to use fastboot and TWRP with IMG flashIng, but after flashing them, the mobile phone will jump to Bootloader page, but when I use the same method in other ROM(like PHH and RR6.1.0)it works. My last ROM version is MIUI10-8.7.12 Globle.
details here
1.formate data
2.4 wipe
3.install and choose img file with system type.
4.wipe again
5.reboot
THanks.

If supported you can flash the image in bootloader mode.
Type in this command.
fastboot flash system nameofimage.img and reboot.

PE just wont boot for some devices. There is a whole different thread about fixing this, it may be for Huawei, but it could work for more devices. Apparently flashing a patched boot from Magisk works.

flash magisk 16.6 it will boot. but then you will have to also format data(not wipe) in twrp to disable encryption.

It finally works!
The steps I took to get it working are the following:
1. Boot to TWRP (I used version 3.2.0.1/v5 from here: https://forum.xda-developers.com/xiaomi-mi-mix-2s/development/recovery-twrp-mix-2s-t3790922
2. Format data, confirm with "yes"
3. Wipe data, system, cache, dalvik
4. Install latest Pixel Experince.img (GSI) from the thread on XDA
5. Flash magisk 16.6 directly after the image. Didn't do a reboot before flashing magisk
6. Rebooted system
7. Got many warnings that the device is not Google certified. Search for this terms and you'll find a tutorial to get rid of the messages. Simply downloaded the "device+ID.apk" from XDA and installed it. Wrote down the GSF ID and visited the mentioned page and got my device registered. Warnings are gone, play services are running perfectly fine. Here's the link to the article https://www.google.at/amp/s/www.xda...fix-device-not-certified-by-google-error/amp/
8. Rebooted system again
Works like a charm. Got everything set up to my needs. Only thing I had to configure was the navigation bar as it was hidden from the beginning. Just opened settings and toggled the navigation bar settings from one setting to the other and it appeared.
Will definitely be my daily driver from no on. Finally we can have a "Pixel" for half the price!
I'm so happy right now. Thanks to all the people who supported me and answered all my questions!

kleinholzinferno said:
It finally works!
The steps I took to get it working are the following:
1. Boot to TWRP (I'm using version 3.2.0.1)
2. Format data, confirm with "yes"
3. Wipe data, system, cache, dalvik
4. Install latest Pixel Experince.img (GSI) from the thread on XDA
5. Flash magisk 16.6 directly after the image. Didn't do a reboot before flashing magisk
6. Rebooted system
7. Got many warnings that the device is not Google certified. Search for this terms and you'll find a tutorial to get rid of the messages. Simply downloaded the "device+ID.apk" from XDA and installed it. Wrote down the GSF ID and visited the mentioned page and got my device registered. Warnings are gone, play services are running perfectly fine. Here's the link to the article https://www.google.at/amp/s/www.xda...fix-device-not-certified-by-google-error/amp/
9. Rebooted system again and it works like a charm. Got everything set up to my needs. Only thing I had to configure was the navigation bar as it was hidden from the beginning. Just opened settings and toggled the navigation bar settings from one setting to the other and it appeared.
Will definitely be my daily driver from no on. Finally we can have a "Pixel" for half the price!
I'm so happy right now. Thanks to all the people who supported me and answered all my questions!
Click to expand...
Click to collapse
didnt worked for me rebooted into recovery i used 3.2.1-0 can you link me yours?

From this thread
https://forum.xda-developers.com/xiaomi-mi-mix-2s/development/recovery-twrp-mix-2s-t3790922
I used version 5 because in version 6 usb MTP mode is disabled.
Which rom did you come from? I came from a working official resurrection remix gsi. But I don't know if this matters as you wipe everything from the device.
Have you ever had a treble gsi running on your device? I remember installing RR after the android P beta from Xiaomi failed. I then started from scratch and installed the latest official global stable miui rom for the MiMix2S from Xiaomi without magisk and all and went from there. Don't know why but this fixed the problem with the RR gsi.
Maybe theres a problem with older mods you have done. You could try and start from zero and get the device back into the original state.
Hope it works out for you! Let us know how it turned out. Could be anyone else has some more input for you.
I know it's frustrating to flash a rom that works for others and not on your device although you have the same as them and followed every step in the tutorial. I've been there so many times that I lost count but it's always the little things that cause problems. Take your time, read some more about this whole stuff. I had to read a lot to get into this topic. Maybe theres a nother method of flashing that works for you.

kleinholzinferno said:
From this thread
https://forum.xda-developers.com/xiaomi-mi-mix-2s/development/recovery-twrp-mix-2s-t3790922
I used version 5 because in version 6 usb MTP mode is disabled.
Which rom did you come from? I came from a working official resurrection remix gsi. But I don't know if this matters as you wipe everything from the device.
Have you ever had a treble gsi running on your device? I remember installing RR after the android P beta from Xiaomi failed. I then started from scratch and installed the latest official global stable miui rom for the MiMix2S from Xiaomi without magisk and all and went from there. Don't know why but this fixed the problem with the RR gsi.
Maybe theres a problem with older mods you have done. You could try and start from zero and get the device back into the original state.
Hope it works out for you! Let us know how it turned out. Could be anyone else has some more input for you.
I know it's frustrating to flash a rom that works for others and not on your device although you have the same as them and followed every step in the tutorial. I've been there so many times that I lost count but it's always the little things that cause problems. Take your time, read some more about this whole stuff. I had to read a lot to get into this topic. Maybe theres a nother method of flashing that works for you.
Click to expand...
Click to collapse
i started from 0 flashed in order global official miui rom after rr and after pixel experience all ok without strange messages

PITTAR said:
i started from 0 flashed in order global official miui rom after rr and after pixel experience all ok without strange messages
Click to expand...
Click to collapse
Very good, great it works for you now.
Enjoy the new phone! I have it running for a few days now and so far I love it! I'm never going back to miui again! Never!
Some things are not working at the moment like Bluetooth audio to car stereo. Although it shows the song playing with the title and the correct time on the car head unit I hear no sound. Hands free calls work without any problems.
In band ringing doesn't work so I don't hear my ringtone over the car stereo. I can activate this in developer options but it doesn't stay on and doesn't work. Nevermind, this isn't important.
Haven't found many other things that I need at the moment.
Great rom, hope it gets maintained in the future and there will be a device specific rom for the MiMix2S in the near future.
Hopefully Android P in fall/winter?

kleinholzinferno said:
It finally works!
The steps I took to get it working are the following:
1. Boot to TWRP (I'm using version 3.2.0.1/v5 from here: https://forum.xda-developers.com/xiaomi-mi-mix-2s/development/recovery-twrp-mix-2s-t3790922
2. Format data, confirm with "yes"
3. Wipe data, system, cache, dalvik
4. Install latest Pixel Experince.img (GSI) from the thread on XDA
5. Flash magisk 16.6 directly after the image. Didn't do a reboot before flashing magisk
6. Rebooted system
7. Got many warnings that the device is not Google certified. Search for this terms and you'll find a tutorial to get rid of the messages. Simply downloaded the "device+ID.apk" from XDA and installed it. Wrote down the GSF ID and visited the mentioned page and got my device registered. Warnings are gone, play services are running perfectly fine. Here's the link to the article https://www.google.at/amp/s/www.xda...fix-device-not-certified-by-google-error/amp/
8. Rebooted system again
Works like a charm. Got everything set up to my needs. Only thing I had to configure was the navigation bar as it was hidden from the beginning. Just opened settings and toggled the navigation bar settings from one setting to the other and it appeared.
Will definitely be my daily driver from no on. Finally we can have a "Pixel" for half the price!
I'm so happy right now. Thanks to all the people who supported me and answered all my questions!
Click to expand...
Click to collapse
Thanks for sharing so much...but I wanna know flashing Magisk 16.6 is significant or not? Why should I must flash that..caz I use bank App which is not allowed root device..Oh, I try to flash Omin ROM, but it can't get into the system..and Magisk16.6 can't be flashed in with error..

jayxiao171735 said:
Thanks for sharing so much...but I wanna know flashing Magisk 16.6 is significant or not? Why should I must flash that..caz I use bank App which is not allowed root device..
Click to expand...
Click to collapse
Magisk was mandatory for me because otherwise it ended up booting only to recovery.
I haven't tried what happens when you uninstall magisk after successfully setting up the device.
If you need to hide root use magisk hide, maybe that helps?

How to install LineageOS on the Mi 10T Lite

Hey guys, if you're a noob or you haven't flashed a custom ROM to an android device since the likes of the Galaxy S2 like me, this guide is made for you!
Disclaimer: I am by no means taking credit for any links posted, credits to the creators of anything mentioned! And a special thank you to the creators of the TWRP and the ROM, hopefully development will grow for such an awesome device! I am not responsible if you brick your device (by not following my tutorial :/)
The only complaints I have about this ROM is the camera quality but install the GCAM port for the Mi10T Lite, it may help!
You will need:
A Mi10T Lite (duh) or any other supported device with MIUI Installed (Android 10)
A SD card
A laptop with fastboot installed ( [OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 | XDA Developers Forums (xda-developers.com) )
A Mi account
TWRP (https://www.mediafire.com/file/qaea...0I_3.5.A10_05-01-2021_BL-L-fixsdcard.img/file)
The ROM (https://forum.xda-developers.com/t/rom-unofficial-10-0-gauguin-lineageos-17-1.4224633/)
GApps (I used this one: Download NikGapps from SourceForge.net)
B*lls
First (Ignore this if you already unlocked your bootloader):
Download MiFlash_Unlock (http://miuirom.xiaomi.com/rom/u1106245679/4.5.813.51/miflash_unlock-en-4.5.813.51.zip)
Make sure you have a Mi account and a SIM
Go to settings, enable developer options
Once you have done this, go to developer options (additional settings, scroll down)
Enable OEM Unlocking
Enable USB Debugging (not sure if this is necessary but I like to have it enabled anyway)
Click on Mi Unlock status and add your account, remember your details! (You may need to sign out and sign back in again)
It should say account linked to device successfully or something along those lines
Grab a cable (the included cable worked for me but other cables didn't)
OPTIONAL: YOU MAY WANT TO BACK UP ALL OF YOUR DATA
Open MiFlash_Unlock which you previously downloaded and connect your phone in fastboot mode (if it doesn't show up follow this tutorial: Fixed: Fastboot not detecting your Android device (qasimtricks.com) )
Click on unlock device! It should automatically reboot when it's done
Complete the set-up process, input your Mi account details and you should be good to go!
Enable developer options again and enable USB debugging
Installing TWRP (Ignore this if you already have TWRP installed!):
Turn off your device and boot into fastboot, connect and verify that it is connected by opening command prompt then typing "fastboot devices", it should show up
Point command prompt to the folder where your TWRP is downloaded (if it is located in downloads, type cd c:/users/(your username)/downloads
Then type fastboot flash recovery "twrp".img (replace "twrp" with the name of the recovery installed)
It should say successful, then type fastboot reboot and hold volume up + power
You've booted into TWRP! Hooray!
If it asks for the password to decrypt put it in, if it doesn't then no worries
You will notice that your internal storage is encrypted, not to worry!
Installing the ROM:
Connect your phone to your laptop (it can be in TWRP) and move the ROM to your SD card
Boot into TWRP if you haven't already, click wipe, advanced wipe and wipe Dalvik Cache/ART, Data and Cache
Once this has completed, go to install, then change the storage to SD Card
Locate the ROM file and swipe to flash!
Once the flash has completed, DO NOT REBOOT
Go to wipe and click format data, then type yes
Reboot to system! Done!
Installing GApps (Optional):
Move the GApps file provided to your phone
Boot to TWRP
It will prompt you to enter your passcode, this will decrypt the internal storage!
Click on install and locate GApps, swipe and flash!
Reboot
Congratulations! You have installed the first custom ROM made specifically for the device You can install Magisk if you want, I'm in the UK and my metro bank app didn't work but by using Magisk hide and changing the name of the Magisk manager everything worked (hide every Google app)
Enjoy! I hope you found this useful

thanks, after installing it can i go back to stock with locked bootloader?

jeuxtype said:
thanks, after installing it can i go back to stock with locked bootloader?
Click to expand...
Click to collapse
yes you can using xiaomi flash tool

Might want to confirm when to install gapps as if it's done after a boot it's not going to work!

Chari69 said:
yes you can using xiaomi flash tool
Click to expand...
Click to collapse
so it's safe to flash lineage, i want to use it but i need to get back to stock to watch netflix and for google pay?

jeuxtype said:
so it's safe to flash lineage, i want to use it but i need to get back to stock to watch netflix and for google pay?
Click to expand...
Click to collapse
Yes its safe, download the stock fastboot ROM online and use miFlash as mentioned, before you start flashing make sure the setting at the bottom right of the app is set to wipe + lock, I've already done it once and it worked fine

benfleet5 said:
Might want to confirm when to install gapps as if it's done after a boot it's not going to work!
Click to expand...
Click to collapse
Hey, that's awfully weird. When I tried flashing alongside the ROM I kept getting an error, but after I booted and done initial set up and tried installing it worked fine

Good guide a++++

deanlee121 said:
Good guide a++++
Click to expand...
Click to collapse
Thanks Dean!

Google pay works on this?

Xts7 said:
Google pay works on this?
Click to expand...
Click to collapse
Yeah just changed the magisk package name, enabled magisk hide and used gpay sqlite fix and it was all working. Metro Bank worked too

The only thing I'd say is that Open GApps Micro is the package you want to install; anything larger won't fit in the system partition - you get an Error 70! JT

jdtanner said:
The only thing I'd say is that Open GApps Micro is the package you want to install; anything larger won't fit in the system partition - you get an Error 70! JT
Click to expand...
Click to collapse
Hey, I've just been made aware that that works too, but NikkGapps also works! Also, ArrowOS comes pre-built with GApps and it's better imo, only thing is bluetooth audio doesn't work and the speaker crackles occasionally.

fizzy900 said:
Hey, I've just been made aware that that works too, but NikkGapps also works! Also, ArrowOS comes pre-built with GApps and it's better imo, only thing is bluetooth audio doesn't work and the speaker crackles occasionally.
Click to expand...
Click to collapse
Waiting until these bugs are sorted before trying that ROM. Bluetooth and general audio are fairly important to me

jdtanner said:
Waiting until these bugs are sorted before trying that ROM. Bluetooth and general audio are fairly important to me
Click to expand...
Click to collapse
Same somewhat lol, its annoying but thank God my headphones have a 3.5mm jack too!

Thanks for the guide, I recently got a redmi note 9 pro 5g from chinaland shipped to the uk then followed this guide pretty much, but instead of going twrp and lineage I went Orangefox and Arrow OS
I wasn't sure how all would go so was grateful of the guide as my first flashing on the new beasty..
I used this guide + info from the arrow thread before I jumped in..
just for info's it worked flawlessly
Steps I did
1. Unlocked bootloader ofcourse
2. installed Orangefox via fastboot
3. flashed latest version of china android 10 from sdcard (no reboot)
4. flashed arrow OS android 11 from sdcard
5. wiped data
To my amazement it booted first go and real fast like in under 5min!
can somebody explain why we need to wipe data after flashing ? surely wiping data means wiping ? but I guess it is not somehow wiping the good flash data..?
Where does all the data go when I flashed the first chinarom and why is it required to flash chinarom first ?
I have one bug bar the odd crackle, has anyone else noticed keyboard issues ? When i type sometimes it shows up backwards
ie google will appear as elgoog ?
I tried swiftkey keyboard + changing languages still the issue persists..
Thanks again @ Fizzy900

Jonny5isalivetm said:
Thanks for the guide, I recently got a redmi note 9 pro 5g from chinaland shipped to the uk then followed this guide pretty much, but instead of going twrp and lineage I went Orangefox and Arrow OS
I wasn't sure how all would go so was grateful of the guide as my first flashing on the new beasty..
I used this guide + info from the arrow thread before I jumped in..
just for info's it worked flawlessly
Steps I did
1. Unlocked bootloader ofcourse
2. installed Orangefox via fastboot
3. flashed latest version of china android 10 from sdcard (no reboot)
4. flashed arrow OS android 11 from sdcard
5. wiped data
To my amazement it booted first go and real fast like in under 5min!
can somebody explain why we need to wipe data after flashing ? surely wiping data means wiping ? but I guess it is not somehow wiping the good flash data..?
Where does all the data go when I flashed the first chinarom and why is it required to flash chinarom first ?
I have one bug bar the odd crackle, has anyone else noticed keyboard issues ? When i type sometimes it shows up backwards
ie google will appear as elgoog ?
I tried swiftkey keyboard + changing languages still the issue persists..
Thanks again @ Fizzy900
Click to expand...
Click to collapse
Hey bro, nice glad you enjoyed! So you have to format data after flashing a custom ROM from what I know in order to remove encryption, if you don't it'll show your internal files in a strange way and if you further tinker with it and do something it might stop you from installing apps full stop (happened to me cause I was being a tw*t lol). You need to flash the latest stock firmware (if the ROM requires you to) so you get the latest vendors which work with the custom ROM, although I believe there is a method to just flash vendor images themselves (fastboot flash vendor nameofvendorfile.img).
Yeah so arrowOS has notification crackles for some reason, most of the bugs are audio related (BT audio doesn't work either).
My typing was backwards too sometimes, it's because you're touching the fingerprint slightly which goes to the first element on a page or something (when you're typing it goes to the start of the box where you enter text). To understand what I mean go onto your launcher and tap the fingerprint scanner, it should highlight something.
I just flashed dotOS from arrow, works a charm! No audio related bugs afaik and BT audio works (lifesaver, phew).
Any other questions feel free to drop me a message on Telegram, @stillw0rking.
Take care! Also how in the world did you import the device from China hahahaha

epic fast reply!
<3
ahha the fingerprint!! I was wondering why I got random white box appearing on my home screen (and at random times) can it be disabled ?
So we got another rom already lol how excellent, I would like a rom that is stripped to the bone so we can install what we like, aka the least amount of crap running in the backround the merrier I am
Yea I just ordered from one of the china phone shops, got a note 9 pro 5g for £ 211 including postage, when I saw the price I just had to buy even tho my trusty oneplus 3t is still fine but but had the upgrade bug hehe, was from giztop, risked the custom charge and succeeded haha
Finally thanks for explaining the Encryption bit, yes I did read that but it seemed to go in one ear...
Guessing you are on the mainland somewhere, Greetings from across the pond

Jonny5isalivetm said:
epic fast reply!
<3
ahha the fingerprint!! I was wondering why I got random white box appearing on my home screen (and at random times) can it be disabled ?
So we got another rom already lol how excellent, I would like a rom that is stripped to the bone so we can install what we like, aka the least amount of crap running in the backround the merrier I am
Yea I just ordered from one of the china phone shops, got a note 9 pro 5g for £ 211 including postage, when I saw the price I just had to buy even tho my trusty oneplus 3t is still fine but but had the upgrade bug hehe, was from giztop, risked the custom charge and succeeded haha
Finally thanks for explaining the Encryption bit, yes I did read that but it seemed to go in one ear...
Guessing you are on the mainland somewhere, Greetings from across the pond
Click to expand...
Click to collapse
Haha yes I'm from near London! You must be the first English person I've actually bumped across on XDA ever lol. Aah yes, as far as I know it can't be disabled, it'll be stuck w that until the dev fixes it... ROMs have started to release quite quickly for the phone ever since the mi10i got dropped thank God, hopefully this is a good sign!
DotOS seems to be pretty light, heavy on the customizing side but when I started from fresh I had the basic google apps but gmail wasn't even installed lol. Dot is giving me the same sort of sot as Arrow, so really its up to you, but if the BT audio bug is a major thing for you (thank God one of my headphones can be used with a 3.5mm jack too lol) then I'd recommend Dot, but otherwise they're both extremely similar in terms of performance
And I was gna try and order the mi9T Pro like that but didn't bother, read some bad stories lol.
And no worries But yeah I'm pretty sure that is all it is, when you modify /system or something, the internal storage encrypts so you can't access it on stock ROM with TWRP but with custom you can decrypt easily
Take care mate!

Does lineage for mi 10t lite support 120 hz on screen ? Is it adaptive or locked?

Bluetooth problem after flashing TWRP

Hi,
I flashed TWRP on my unlocked Redmi Note 8T with MIUI Global 12.5.5. Everything was great until I rebooted it and saw Bluetooth error which pops every time I try to turn Bluetooth on or just randomly during usage of the device. I also tried to re-flas TWRP with Orange fox but it unfortunatelly did not help. Now I have no idea what to do but there are also some other people with this problem (for example:
https://www.reddit.com/r/Xiaomi/comments/y9zsak
).
Does anybody know any solution? Thanks!
Btw Orange fox is for ginko devices, I did not find version for willow

I had the exact same problem when I tried to root my stock rom in ginkgo. I was getting a lot of "app keeps stopping" pop ups, and that also included bt. My bt was completely broken until I changed rom. Also I'm guessing this had happened when I had rooted my phone with magisk, not by flashing recovery itself. Perhaps you could try to uninstall magsik, and see it it resolves the issue for you. If that would be the case, then you would have found your problem, and maybe you can flash a custom rom to safely root your phone.

Thanks for reply, but i did not have magisk flashed on my phone. I only had installed the app, prepared apk file and did nothing in TWRP (Orange fox) , just flashed a recovery with my PC, checked that it is working and rebooted device. Anyway I tried to do it only because of acces to NFC and Gpay which is now blocked.
As you also said, I would like to try custom rom (like LineageOS) because it seems like bad idea to have a stock room on an unlocked phone. Only the problem is how to backup data like data from apps, games etc.
So now it tried one of my ideas, which was to install Magisk (root) and uninstall it but it also did not help (I expected that)

vasik006 said:
Thanks for reply, but i did not have magisk flashed on my phone. I only had installed the app, prepared apk file and did nothing in TWRP (Orange fox) , just flashed a recovery with my PC, checked that it is working and rebooted device. Anyway I tried to do it only because of acces to NFC and Gpay which is now blocked.
As you also said, I would like to try custom rom (like LineageOS) because it seems like bad idea to have a stock room on an unlocked phone. Only the problem is how to backup data like data from apps, games etc.
Click to expand...
Click to collapse
To backup data simply copy your personal files in pc or sdcard. And to backup data in apps, take back-up of only those apps and where you need to backup. Don't take a complete backup using some app. That consumes a lot of space and make the newly rom feel "not so new". Most apps don't require you to take back-up offline these days. I usually backup only my personal files before flashing rom.

Yeah, that's true. But don't you know how to backup data from these "offline" apps? I was trying to solve this also before unpocking bootloader like a year ago but unsuccessfuly.
Also, which rom should I choose? I'm deciding between LineageOS and Pixel experience.
So I have LOS installed but I can´t install other zip files (like Google apps). Im only getting error: signature verification failed while. Im using LOS recovery so where is the problem?
Solved it!

Hey @vasik006 ! I know this is very late and you might have found the solution yourself, but I found the solution to this problem. Since yesterday I was trying to root my ginkgo with twrp, using magisk delta and had exact same issue. Joyose and bluetooth keeps stopping, and don't work. Simply factory reset ( I also formatted data) in twrp, and in next boot bluetooth should work. Then you can simply install the magisk apk and let it do its thing. No need to flash again since it has already made changes to boot file that can't be overriden by resetting phone.

Thanks, this might help someone else with this problem. I have already formatted my phone, installed Lineage OS and everything is ok

For me, the problem with BT and Joyose occurs only with TWRP v3.7.x. I went back to TWRP v3.6.1_9-0 but now backups are not working.

Jatin Verma x821 said:
Hey @vasik006 ! I know this is very late and you might have found the solution yourself, but I found the solution to this problem. Since yesterday I was trying to root my ginkgo with twrp, using magisk delta and had exact same issue. Joyose and bluetooth keeps stopping, and don't work. Simply factory reset ( I also formatted data) in twrp, and in next boot bluetooth should work. Then you can simply install the magisk apk and let it do its thing. No need to flash again since it has already made changes to boot file that can't be overriden by resetting phone.
Click to expand...
Click to collapse
I have the same problem with the Redmi note 8. Did you unroot first or did the factory reset directly? Tks

ennev said:
I have the same problem with the Redmi note 8. Did you unroot first or did the factory reset directly?
Click to expand...
Click to collapse
no need to unroot. simple factory reset the device and you're done.

Jatin Verma x821 said:
To backup data simply copy your personal files in pc or sdcard. And to backup data in apps, take back-up of only those apps and where you need to backup. Don't take a complete backup using some app. That consumes a lot of space and make the newly rom feel "not so new". Most apps don't require you to take back-up offline these days. I usually backup only my personal files before flashing rom.
Click to expand...
Click to collapse
TWRP is invaluable for backing up the system before making changes like theming etc. and I can take a TWRP backup to any of my (all the same) devices and restore the whole thing in just a few minutes. So convenient! I really couldn't imagine life without TWRP. TWRP enables me to clone my device in case of hardware failure. All my settings and all my apps and all my custom configurations which would otherwise take hours/days to setup - BAM! Presto! on the new device and running perfectly.
TWRP + NeoBackup are essential. TWRP as described, and NeoBackup to roll back breaking updates to apps when devs butcher them, break them, and/or just remove really useful features. I also disconnect apps that get ruined by an update from the Play Store so they don't keep coming up when I check for updates.

Alpha_Geek1 said:
TWRP is invaluable for backing up the system before making changes like theming etc. and I can take a TWRP backup to any of my (all the same) devices and restore the whole thing in just a few minutes. So convenient! I really couldn't imagine life without TWRP. TWRP enables me to clone my device in case of hardware failure. All my settings and all my apps and all my custom configurations which would otherwise take hours/days to setup - BAM! Presto! on the new device and running perfectly.
TWRP + NeoBackup are essential. TWRP as described, and NeoBackup to roll back breaking updates to apps when devs butcher them, break them, and/or just remove really useful features. I also disconnect apps that get ruined by an update from the Play Store so they don't keep coming up when I check for updates.
Click to expand...
Click to collapse
I would advise you to read the posts again. They were asking about how to take backup of "personal apps" which twrp can't do, and if they are changing ROM then twrp backup won't be of any use to them. Therefore, whatever you're trying to tell here doesn't really help the discussion.

Jatin Verma x821 said:
I would advise you to read the posts again. They were asking about how to take backup of "personal apps" which twrp can't do, and if they are changing ROM then twrp backup won't be of any use to them. Therefore, whatever you're trying to tell here doesn't really help the discussion.
Click to expand...
Click to collapse
TWRP does backup personal apps and their settings. Once you restore a TWRP backup, you have everything back except media files - images, videos, documents, etc. The launcher icons, the apps, the system settings - everything is a perfect clone which you can restore on a new device (same model, of course).
I actually came across this thread searching to see if others had a problem where merely flashing TWRP caused Bluetooth to crash (and Atmos).

Use OrangeFox

is there anyone use BT-fix-for-PE-20190618.zip to fix this problem ?

I'm on an ROG Phone II with the same issue.
The "fix" is to wipe in TWRP and install Magisk BEFORE you leave for your first boot and NEVER come back to TWRP as the issue will return the second recovery is booted.
s3rv said:
For me, the problem with BT and Joyose occurs only with TWRP v3.7.x. I went back to TWRP v3.6.1_9-0 but now backups are not working.
Click to expand...
Click to collapse
From what I can tell, this is correct. 3.6_XX-X allows me to come and go from TWRP as much as I please without incurring the bug, however, I haven't tested backup though I can't see a reason why they wouldn't work.
Are these existing backups that aren't working or the whole backup function in general?
starkshadow said:
is there anyone use BT-fix-for-PE-20190618.zip to fix this problem ?
Click to expand...
Click to collapse
It looks like this guy didn't have any luck with it either. It may be divice specific

Dredead said:
I'm on an ROG Phone II with the same issue.
The "fix" is to wipe in TWRP and install Magisk BEFORE you leave for your first boot and NEVER come back to TWRP as the issue will return the second recovery is booted.
From what I can tell, this is correct. 3.6_XX-X allows me to come and go from TWRP as much as I please without incurring the bug, however, I haven't tested backup though I can't see a reason why they wouldn't work.
Are these existing backups that aren't working or the whole backup function in general?
It looks like this guy didn't have any luck with it either. It may be divice specific
Click to expand...
Click to collapse
amazing, I have do nothing, just reboot my device, and yesterday the bluetooth also has problem, but today I open bluetooth, it is no problem. I'm still confused about that.

starkshadow said:
amazing, I have do nothing, just reboot my device, and yesterday the bluetooth also has problem, but today I open bluetooth, it is no problem. I'm still confused about that.
Click to expand...
Click to collapse
It seems to be a twrp issue. What version do you have? And what version of magisk do you have?
I have recently flashed miui 12 (android 10) after bricking the phone using qtel. I noticed the Bluetooth problem last week and didn't find a fix. I have twrp 3.6.2 and magisk 25.1. I had twrp 3.7.1 but if failed to decrypt data using pattern so I rolled back to 3.6.2. And I thought that magisk had to do with the Bluetooth problem so I rolled back to 25.1 from 26.
I still can't use the Bluetooth, and I don't have time to reset the phone, I just finished restoring everything

I CAN CONFIRM
go back to the previous twrp 3.6.2 version + wipe factory reset or simply format data solve sucesfuly solve installation issue of Magisk 26.1 or Magisk Delta 25210

Olfason said:
I CAN CONFIRM
go back to the previous twrp 3.6.2 version + wipe factory reset or simply format data solve sucesfuly solve installation issue of Magisk 26.1 or Magisk Delta 25210
Click to expand...
Click to collapse
I can't afford resetting my phone right now , don't have enough time. I'll let it like that for some months.
Edit : I have miui 12.0.6 installed (android 10) and I'm not planning to upgrade since I have much better battery life (even better than every mod I tried). I wander if I flash miui rom from recovery can fix it?
Edit 2: flashing the rom from recovery didn't fix it

Question Very Weird Encryption/Bootloop issue

Greetings!
An interesting and strange situation has appeared on the Poco F3.
Unlocked device, installed xiaomi.eu dev latest with their own TWRP, Magisk 25.2 (latest stable). I didn't install any DFE or other vbmeta etc patches.
After installing all this, after a couple of days of using the device, I get a bootloop (when I reboot the device it gets stuck on the MIUI logo), just with nothing. Before that, bootloop do not appear (I did a reboot on purpose and loaded into the system). Then, I thought the problem was in the recovery, I flashed orangefox - but the result is still the same. No any Magisk modules installed (specially tested without them). There is also a backup when everything works, it is restored, but it still does not load into the system, it just remains on the MIUI logo. In the recovery itself (what is skkk, what is ofox) is nothing red, without errors during firmware/actions. BTW, there is a problem on other ROMs based on MIUI: like Pulse, MiuiSR I tried to install on it.
I tried option to install a clean stock through miflash, and then put it through fastboot xiaomi.eu - but it also did not work.
I restored the backup when everything worked except for the data section and made data format, and only then it turned on according to the factory settings with the settings down. So the format data allows to revive it to the initial state, but this is not the way out.
On a local forum, I was told that this is some kind of problem with the encryption of the /data partition or android party rescue in recovery (red line) and it met on XDA, but no one found a clear solution.
Why does the bootloop appear only after some time (2-3 days)? This is some kind of hell and misunderstanding that this occurs specifically after a couple of days of using the device, and not right away. Where to dig and in what sequence? Thank you.

eduaaard said:
Greetings!
An interesting and strange situation has appeared on the Poco F3.
Unlocked device, installed xiaomi.eu dev latest with their own TWRP, Magisk 25.2 (latest stable). I didn't install any DFE or other vbmeta etc patches.
After installing all this, after a couple of days of using the device, I get a bootloop (when I reboot the device it gets stuck on the MIUI logo), just with nothing. Before that, bootloop do not appear (I did a reboot on purpose and loaded into the system). Then, I thought the problem was in the recovery, I flashed orangefox - but the result is still the same. No any Magisk modules installed (specially tested without them). There is also a backup when everything works, it is restored, but it still does not load into the system, it just remains on the MIUI logo. In the recovery itself (what is skkk, what is ofox) is nothing red, without errors during firmware/actions. BTW, there is a problem on other ROMs based on MIUI: like Pulse, MiuiSR I tried to install on it.
I tried option to install a clean stock through miflash, and then put it through fastboot xiaomi.eu - but it also did not work.
I restored the backup when everything worked except for the data section and made data format, and only then it turned on according to the factory settings with the settings down. So the format data allows to revive it to the initial state, but this is not the way out.
On a local forum, I was told that this is some kind of problem with the encryption of the /data partition or android party rescue in recovery (red line) and it met on XDA, but no one found a clear solution.
Why does the bootloop appear only after some time (2-3 days)? This is some kind of hell and misunderstanding that this occurs specifically after a couple of days of using the device, and not right away. Where to dig and in what sequence? Thank you.
Click to expand...
Click to collapse
Hello. To suggest in detail why this happened, unfortunately, is not advertising. but can be used in the reserve of the manufacturer of this phone?

Olesya13 said:
Hello. To suggest in detail why this happened, unfortunately, is not advertising. but can be used in the reserve of the manufacturer of this phone?
Click to expand...
Click to collapse
Hi,
What was meant and what is the meaning of your question?
Regards,
Eduard

developers still improving f2fs file system. I could imagine it's some unpatched bug (without knowing exactly if there is one)

alecxs said:
developers still improving f2fs file system. I could imagine it's some unpatched bug (without knowing exactly if there is one)
Click to expand...
Click to collapse
Hi, no idea but from some sources this indicates that the culprit is vbmeta when installing the initial twrp. But this is still being tested. A bug with a custom font in MIUI is also possible, many people know that this caused bootloops after a while in theme manager.