Database Develop

MRA58R build?

Alright, so I just flashed MRA58N yesterday, and today there is a new MRA58R image added? What's the difference here? The first build was a security update, but what's this new one? And why only a day difference? Thanks!
Sent from my Nexus 6

Changelogs aren't made readily available.
Perhaps this script will help people who update their local AOSP repo's will help.
https://groups.google.com/forum/#!msg/android-building/0DtsHawjs4k/And8o3Dni_UJ
Obviously some modification will be required

I'm in the same position. Yesterday I flashed the MRA58N build and today I saw they already uploaded the MRA58R build, LOL, so annoying.
http://www.androidpolice.com/androi....0_r2-to-android-6.0.0_r4-AOSP-changelog.html

Quetzalcoalt_Lp said:
I'm in the same position. Yesterday I flashed the MRA58N build and today I saw they already uploaded the MRA58R build, LOL, so annoying.
http://www.androidpolice.com/androi....0_r2-to-android-6.0.0_r4-AOSP-changelog.html
Click to expand...
Click to collapse
Damn, I wonder if it's even worth flashing! I installed MRA58N and then re rooted my phone, reinstalled all my apps, reinstalled multirom, etc. Took a while, wonder if it's worth flashing!
Sent from my Nexus 6

I am currently running 6.0 MRA58R / Rooted / No Encryption. I notice no difference at all between N and R. Not that I would anyways. I'm wondering what the difference is myself.

Rektifying said:
I am currently running 6.0 MRA58R / Rooted / No Encryption. I notice no difference at all between N and R. Not that I would anyways. I'm wondering what the difference is myself.
Click to expand...
Click to collapse
What kernel are you using?

H4X0R46 said:
Damn, I wonder if it's even worth flashing! I installed MRA58N and then re rooted my phone, reinstalled all my apps, reinstalled multirom, etc. Took a while, wonder if it's worth flashing!
Sent from my Nexus 6
Click to expand...
Click to collapse
Did you do a full wipe/flash? You only really need to flash system... You'll need to reroot after, but don't need to mess with your apps and what not...
If you want to be a little more complete, flash boot, bootloader and radio too, none of which will mess with hour apps...
But if you flash boot, you will need to reflash your kernel and if your unencrypted you have to make sure you boot straight to recovery and flash kernel WITHOUT booting android.

scryan said:
Did you do a full wipe/flash? You only really need to flash system... You'll need to reroot after, but don't need to mess with your apps and what not...
If you want to be a little more complete, flash boot, bootloader and radio too, none of which will mess with hour apps...
But if you flash boot, you will need to reflash your kernel and if your unencrypted you have to make sure you boot straight to recovery and flash kernel WITHOUT booting android.
Click to expand...
Click to collapse
I never do a dirty flash just to avoid conflict, but I guess it couldn't hurt to try right? So not wiping userdata should work?
Sent from my Nexus 6

If its just the monthly updates, I wouldn't touch userdata.
If your on completely stock kernel, and encrypt do bootloader, boot, radio and system
If your unencrypted, flashing boot occasionally may help update ramdisk, but you run the risk that someday your tired or otherwise not paying attention and you boot android and it re-encrypts/wipes your device. Never done this so I am not sure if you would have the chance to stop it, or if it would just start formatting userdata out of nowhere...
Always best to take a backup right before. Then if there are issues you can restore backup things individually and install clean.
If I were on stock, most the time I would likely just backup, fastboot flash system.IMG and call it good unless issues popped up. Occasionally I would update bootloader/radios/boot... Maybe every other/every three... When people were talking about benefits of doing so here...

I have always had zero issues applying newer stock images over older stock images on a Nexus device. I do this all the time when the OTA is not available and only the main updated Google Factory image is available.
I think the trick is to always wipe dalvik and cache after a flash of system and use TWRP that supports encryption. When you wipe the dalvik and cache the system acts like an OTA and performs an upgrade on all your apps. I *think* it effectively rebuilds the cache for all apps, but it never touches the app data or user data (sdcard/pictures/etc).
I also always flash the radios and bootloader *IF* they are updated from the last image. I used to flash the stock boot images too, but now that looks like from a going forward point we won't be able to do this and have root. I do look forward to system-less root

scryan said:
If its just the monthly updates, I wouldn't touch userdata.
If your on completely stock kernel, and encrypt do bootloader, boot, radio and system
If your unencrypted, flashing boot occasionally may help update ramdisk, but you run the risk that someday your tired or otherwise not paying attention and you boot android and it re-encrypts/wipes your device. Never done this so I am not sure if you would have the chance to stop it, or if it would just start formatting userdata out of nowhere...
Always best to take a backup right before. Then if there are issues you can restore backup things individually and install clean.
If I were on stock, most the time I would likely just backup, fastboot flash system.IMG and call it good unless issues popped up. Occasionally I would update bootloader/radios/boot... Maybe every other/every three... When people were talking about benefits of doing so here...
Click to expand...
Click to collapse
Cool dude! Thanks for the advice! Yea, I use ElementalX kernel on my device, unencrypted device makes no noticeable difference for performance to me, but the battery life is another story! ElementalX has superb battery life!
Sent from my Nexus 6

Any word on the changes between this and previous build yet?

Surely we expect the security updates to show no visible differences? When my antivirus updates itself I don't ask to see the changelog, since it has no effect whatsoever on the machine's performance or user experience, no...?
If the security update is doing what it's supposed to, the only difference is that one day you won't see your device pwned.

dahawthorne said:
Surely we expect the security updates to show no visible differences? When my antivirus updates itself I don't ask to see the changelog, since it has no effect whatsoever on the machine's performance or user experience, no...?
If the security update is doing what it's supposed to, the only difference is that one day you won't see your device pwned.
Click to expand...
Click to collapse
The security updates were also in the previous build, MRA58N.
All we really know for sure is that the OTA for MRA58R is being pushed out by Verizon. The OTA path skips MRA58N.

Pushed out by big red.... I think that's something I'll definitely wait on.

jbeezley said:
Pushed out by big red.... I think that's something I'll definitely wait on.
Click to expand...
Click to collapse
I've never had a problem with their updates and, realistically, this is actually a Google update. I'm just impressed that they're leading the charge.
I'm on MRA58K after sideloading the first Marshmallow OTA. I just noticed there's an OTA from K to N but there's nothing from any Marshmallow build to R.

I'm on N and haven't seen anything detailing what's different in R. I'm just a bit suspicious of anything pushed by Verizon, although you are correct @GilmourD3. It's Google's update, but why would Verizon spearhead the rollout? I would rather just stay on N awhile until we have someone in the know look over the details of the update to R.

I flashed it and I see no difference, I'm running it rooted with that custom kernel I mentioned earlier, it runs exactly the same as N so my guess is just very small bug fixes that don't change anything on the user end.

H4X0R46 said:
I flashed it and I see no difference, I'm running it rooted with that custom kernel I mentioned earlier, it runs exactly the same as N so my guess is just very small bug fixes that don't change anything on the user end.
Click to expand...
Click to collapse
Anything change from K to N? I might just sideload the N OTA since I'm currently on K and I'm not finding an OTA path from K to R.

R is apparently the OTA update to 6.0 and the November security update for Verizon Nexus 6. My wife got it Thursday and her build and security date both changed.

Device performance problem

Hello, I've got a problem. One day I unlocked bootloader, installed TWRP and I rooted phone with magisk. I didn't like it because battery and performance of the phone was worse. I just uninstalled magisk with app and I flashed magisk removal zip with TWRP and I've done complete wipe. The performance of the phone was bad. I was using my phone and I flashed full oreo open beta zip. I lost TWRP. My phone is really laggy right now. I think that everything is stock except unlocked bootloader. What should I do ?

Determine if there are apps of processes that are using battery or other resources. I have a feeling another app/process is the problem; and Magisk, TWRP, root have little or nothing to do with it. Root/Magisk should have minimal (if any) impact on battery or performance. Might depend on what Magisk modules you installed (if any). But I noticed zero impact on performance or battery with Magisk.
Also, I'm not personally on the Oreo beta. But remember, it is a beta. There are specific performance impacts listed in the changelog and the beta thread, that will be fixed in the future.

maniakunitra1 said:
Hello, I've got a problem. One day I unlocked bootloader, installed TWRP and I rooted phone with magisk. I didn't like it because battery and performance of the phone was worse. I just uninstalled magisk with app and I flashed magisk removal zip with TWRP and I've done complete wipe. The performance of the phone was bad. I was using my phone and I flashed full oreo open beta zip. I lost TWRP. My phone is really laggy right now. I think that everything is stock except unlocked bootloader. What should I do ?
Click to expand...
Click to collapse
Your biggest mistake is using a beta Rom and then blaming root, magisk and what else for the laggy device.
Use a stock Rom and then you can have better results.
Unleashed by ONEPLUS 3T rooted

Go back to the stable branch or the latest nougat beta. The Oreo beta has some issues. I ran magisk/twrp/unlocked bootloader and various modules and root apps with no performance lost on both OOS and LOS. The beta rom is what is causing issues.

Oreo (Audax) to CM13 Downgrade?

Hello forum, a little question......
This is my 2nd time of owning the 3t, now the first time owning a one plus 3t, I used a CM13/marshmallow roms., They were extremely stable, but now my question is.....
Using twrp for the Oreo, I have gone through many many custom roms, Oreo and nougat, oos and lineage etc, but what's the process going back to marshmallow?
Is it just a case of flashing the rom zip like I been doing for last month or so..... or some other way? i.e downgrading something?
I'm currently on Audax 4.0

Just take a Titanium Backup of all your apps first,
Then boot into TWRP, follow the procedure for a clean flash.
Just on a curious note, why would you want to go back to MM?

And also make sure you flash the matching firmware package for the ROM you're planning to run, unless your going for OxygenOS as this does that for you.
Firmware packages can be found in a separate thread in this forum.

thes3usa said:
Just take a Titanium Backup of all your apps first,
Then boot into TWRP, follow the procedure for a clean flash.
Just on a curious note, why would you want to go back to MM?
Click to expand...
Click to collapse
Marshmallow is very stable and battery friendly.

How do I upgrade from an rooted and unencrypted OOS 5.0.4 to OOS 9.0.5?

So recently I've been thinking of upgrading my phone from Oreo to Pie now that it is available and has had a few updates.
Now I haven't updated my phone in a while. The last time was around the summer of 2018. The OxygenOS version my 3T currently is running is 5.0.4 and my TWRP is on version 3.2.3-0.
A while back I was using the custom ROM 'FreedomOS' (for anyone that still remembers) but that ROM hit it's EOL point last year.
After FreedomOS went EOL I switched to stock ROM following this guide to stay decrypted: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Since I switched back to stock I haven't touched the system or recovery at all besides updating Magisk now and then.
Now the question I'm having is how do I update my phone to the latest Pie version of OxygenOS? Which is version 9.0.5 as of writing this post.
Preferably I would like to upgrade with a dirty flash to keep my data (if I run into issues after I'll clean flash) and I also want to stay dencrypted and have Magisk as root.

For your own sakes don't do that. You probably won't be happy unless you want to update to have bigger numer in info screen. (Well if you would like to update to have bigger number in info screen I would suggest editing some conf file to achieve that.)

it's here all the the time, just follow the guide
https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119

First of all, both of you thanks for the replies.
wojtek007pl said:
For your own sakes don't do that. You probably won't be happy unless you want to update to have bigger numer in info screen. (Well if you would like to update to have bigger number in info screen I would suggest editing some conf file to achieve that.)
Click to expand...
Click to collapse
Is the update that bad? If so, what makes Pie so much worse when comparing it to Oreo?
BrahmaGandhi said:
it's here all the the time, just follow the guide
https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Click to expand...
Click to collapse
I've read through the thread a bit and notices this: "Important Note: If your device’s Bootloader is Unlocked, then installing this firmware will factory reset your phone as this is a firmware upgrade. All your personal data and app data will be wiped clean! So backup before flashing!"
Does this mean it will actually reset the entire phone and will wipe all of my apps and files? Is there not a way to dirty flash this new version without losing my apps and such?
Now also in the "Custom ROM" part it says the following: "3. Format Data partition - system will be encrypted (this is a must else system will not boot the new Android version)"
As my device is unencrypted at the moment do I need to let it encrypt for OOS 9 to actually boot up? Or can I just follow the steps in this guide and follow procedure 1 to stay unencrypted? https://forum.xda-developers.com/oneplus-3t/how-to/dm-verity-disable-oxygen-os-t3922324

allard1997 said:
First of all, both of you thanks for the replies.
Is the update that bad? If so, what makes Pie so much worse when comparing it to Oreo?
Click to expand...
Click to collapse
In simple words phone is slower and hotter. Battery isn't better too (battery life for me was decreased from 5 to 3, 3.5 hours screen on time). You can find more on Oneplus forums.

allard1997 said:
First of all, both of you thanks for the replies.
Is the update that bad? If so, what makes Pie so much worse when comparing it to Oreo?
I've read through the thread a bit and notices this: "Important Note: If your device’s Bootloader is Unlocked, then installing this firmware will factory reset your phone as this is a firmware upgrade. All your personal data and app data will be wiped clean! So backup before flashing!"
Does this mean it will actually reset the entire phone and will wipe all of my apps and files? Is there not a way to dirty flash this new version without losing my apps and such?
Now also in the "Custom ROM" part it says the following: "3. Format Data partition - system will be encrypted (this is a must else system will not boot the new Android version)"
As my device is unencrypted at the moment do I need to let it encrypt for OOS 9 to actually boot up? Or can I just follow the steps in this guide and follow procedure 1 to stay unencrypted? https://forum.xda-developers.com/oneplus-3t/how-to/dm-verity-disable-oxygen-os-t3922324
Click to expand...
Click to collapse
i personally would suggest you to stay on oreo or jump to pie custom roms, just skip the oos 9.0.5..
the only thing that really fast and smooth just the face unlock feature :laugh:
as far as i know when you flashed stock oos your data will always be (re)encrypted, unless you do the firmware's patch things like you did before.
jumping (upgrade) from diff. android version it's better to do a clean flash (4 wipes, exclude int. storage will be saved)...and it's mandatory required (from stock to any custom roms). except when you forced to format data you'll lost all data in your phone, for sure.
and if you want to stay unencrypted and disable dm verity for good, it's better to do all that stuffs while on stock oos before you jump onto custom roms.
for more details and assistance i suggest you post on the main thread.

It is slow, slow, slow...

Hi guys,
I'm a bit concerned about my mi8. Since several weeks now the phone is getting so slow to boot, even into recovery mode !
For exemple, today before starting to see the havoc logo spinning I count more than 20 spins. Months ago it took only 5 or 6, 2 weeks ago : more than 8... Etc.
When phone is started first apps tha usualy open really fast (Viper4fx, gsam battery monitor, magisk notifications) are so slow to open. Some other apps same thing the moment I open them.
What do you think about that ? At first I thought my battery is dead. It charges as fast as usual. Discharging is like before I'd way. Not worst for sure So I hope Its nor that.
I'm using battery charge limit (the app, nor from havoc sertings) to stop at 81% and charge it always when the minimum reaches 40%. So for battery life I think I'm doing things well.
I'm still on pie. Please, see the attached picture to look at my version.
I'm wondering what could cause this big issue.
I'm used my make lot of backups with twrp 3.3.1-1. Sometimes 2 per days, sometimes none in 2 or 3 days and so from the day I unlocked the phone and installed my first and only rom : havoc. Sure I installed several updates but no other ROM and I stopped updating it cause it worked really as I expect it should. So...
Also, making twrp backups are Soooo slow. Generaly it tooks depending of the size, between 90 sec and 140. Now it takes more than 6 min !!
So before doing a last backup and do anything I wanted to ask what you all think about that before doing a clean install update/upgrade.
Do you think it worth the try ?
I tried to clear caches (both) in twrp. Nothing :/
I'm afraid I killed my phone memory or battery. Don't really know.
Last thing, maybe an important one but don't know why it would... I installed notify & fitness and sleep as Android for my mi band 4 and I noticed my phone getting slow during this period. About N&F it was on 12.27.2019.
The firmware was updated way after that issue... And of course I cleaned all app caches manualy, not using some weird app to do the job.
Sorry me for this long SOS, and please forgive my bad english. I'm starting to being crazy. OK, the phone works but oooh boy, Its slow.
Cheers

Your rom software is out of date. if you truly want the best experience on a daily basis. There is no doubt in my mind that Xiaomi.EU is still the absolute best experience overall.
It is light years better than the Global stock Rom, all of the bloat has been removed and it has some of the Pixel AOSP features integrated into the Rom. but yes it's still miui. For me that is a good thing because I am a fan. It sounds like you have never tried Xiaomi.EU so give it a shot. I guarantee, that if you keep it installed for a few days, you will not want anything else unless you are just bored. Wait until the new update comes out, it should be late today or tomorrow. by the way, you will average about 7.5 -8.5 hours SOT.
On the other hand, if you are content with Havoc, then migrate to the latest, Its pretty great but the battery SOT time is bad right at 4 hours. This can be improved by changing the kernel. I tested the LawRun_x5.0-60hz kernel and it improves SOT to 5.5 hours, and the OS gennnerally runs better. Other Roms are also good, but lack the abundance of features that Havoc has. A comparable heavily feature rich rom is CRDroid.
If you want to stay on your current rom, then clean your caches, and at least upgrade the kernel. That alone may be enough to improve your recent performance. i dont think you phone is going bad. You likely just have some corruption, or too many processes running in the background.

@tsongming Hi and cheers for replying.
To start, I forget to mention that I'm using a global version.
That being said, I did clean all caches including from all my apps. Manualy of course.
I did use Xiaomi MIUI for very long time. Since I got my first Redmi Note 4. As you well said, I did switch to custom ROMs for what you said.
Regarding SOT... And the reason why I didn't update anything on my Mi8 its because with this version of havoc and this kernel. Gsam bat monitor tells me now : 9h41 (5h58 Max) and before my issue it was 11h !
So, to answer you : before asking here I also trying to update the Rev kernel but lot of things didn't work anymore. Like unlock the phone with my fingers and I think its pretty much normal as Havoc as evolved so kernel did the same and is not compatible with older version I think. At least, mine...
Honestly I tried lot of things to make my havoc super speed, smooth with a great battery and I was happy with that
I do hope I answered to all your questions.
I don't know what to do cause I'm not 100% sure that starting from clean MIUI or custom rom will fix it. What if not ? I'll "forced" to reinstall "everything" (I'm aware of backup apps but dont wanna use them) even if I saved all important stuffs
And if I badly revert to the last MIUI (I never reinstalled MIUI after a custom ROM. I know there is good tuto, but...) I could break it and I'll loose everything. For now it works, slowly OK ^^' but I rather that than taking a risk and found what is the cause of my problem.

Erpe7 said:
@tsongming Hi and cheers for replying.
To start, I forget to mention that I'm using a global version.
That being said, I did clean all caches including from all my apps. Manualy of course.
I did use Xiaomi MIUI for very long time. Since I got my first Redmi Note 4. As you well said, I did switch to custom ROMs for what you said.
Regarding SOT... And the reason why I didn't update anything on my Mi8 its because with this version of havoc and this kernel. Gsam bat monitor tells me now : 9h41 (5h58 Max) and before my issue it was 11h !
So, to answer you : before asking here I also trying to update the Rev kernel but lot of things didn't work anymore. Like unlock the phone with my fingers and I think its pretty much normal as Havoc as evolved so kernel did the same and is not compatible with older version I think. At least, mine...
Honestly I tried lot of things to make my havoc super speed, smooth with a great battery and I was happy with that
I do hope I answered to all your questions.
I don't know what to do cause I'm not 100% sure that starting from clean MIUI or custom rom will fix it. What if not ? I'll "forced" to reinstall "everything" (I'm aware of backup apps but dont wanna use them) even if I saved all important stuffs
And if I badly revert to the last MIUI (I never reinstalled MIUI after a custom ROM. I know there is good tuto, but...) I could break it and I'll loose everything. For now it works, slowly OK ^^' but I rather that than taking a risk and found what is the cause of my problem.
Click to expand...
Click to collapse
The current version of Havoc already uses the Revolution kernel, and its part of the current problem so use something else. The Law kernel that I mentioned is extremely good. but so are the others latest release such as Mipa and Twisted. and no fingerprint issues with these kernels.
As a longtime user you do know that anytime you switch the kernel that you should remove all passkeys, screenlocks, face unlock etc.? This could explain the slowness, you have encryption issues.
Android 10 is much improved over pie, except for the battery 11 hours SOT is unheard of on Android 10. Except for 1 guy claiming 11 hours on the ION rom. I tried the rom and it is good. but I am only getting 7 hours Sot, and the Rom is like Lineage, just the basics. No fingerprint issues.
You truly need a full clean install, including formatting storage. just backup your files first.
Xiaomi Miui? Did you mean Xiaomi.EU? if not Xiaomi.EU , then you really should try it, you wouldn't know from a past experience. This is Miui 11 on Android 10 and its flawless.

thx again @tsongming
Yep, I note all what you said to me. But to be honest last year anytime I switched from kernels to kernels I never had to reset screenlock etc. Last year cause as I said once I found the kernel which suits me I stuck with it.
So I can state its note related to that cause I didn't change it since month trust me, just tried the last kernel one or week ago to be sure if it was the cause or not. Just installed and uninstalled apps since.
look at this screenshot you'll see what I meant about SOT which was better month ago. :/ Maybe I didn't explain well...
I'm not against trying any roms including xiaomi.eu perhaps (I do have links for this I think but any link is appreciated just in case. I just download the lastest stable 11 from xiaomi.eu if its what you have in mind) but I want to be sure if it'll fix what I'm facing. You know ?
I'm afraid that doing a clean install with any rom won't fix my beautiful Mi8 ^^

Erpe7 said:
thx again @tsongming
Yep, I note all what you said to me. But to be honest last year anytime I switched from kernels to kernels I never had to reset screenlock etc. Last year cause as I said once I found the kernel which suits me I stuck with it.
So I can state its note related to that cause I didn't change it since month trust me, just tried the last kernel one or week ago to be sure if it was the cause or not. Just installed and uninstalled apps since.
look at this screenshot you'll see what I meant about SOT which was better month ago. :/ Maybe I didn't explain well...
I'm not against trying any roms including xiaomi.eu perhaps (I do have links for this I think but any link is appreciated just in case. I just download the latest stable 11 from xiaomi.eu if its what you have in mind) but I want to be sure if it'll fix what I'm facing. You know ?
I'm afraid that doing a clean install with any rom won't fix my beautiful Mi8 ^^
Click to expand...
Click to collapse
You posted a question asking for help, but then you dont want to try anything because you tried things before. Yes, its true that Magisk is sometimes persistent, but it depends on the release. it is safer to remove the passkeys.
But if you really think about it, what would cause the phone to cool down, ignore the battery stats especially from Gsam it's often very wrong, I use it too, for years and in your case you are getting good SOT because you have a zero % for the phone. It's almost like a Sim card isn't installed? Every rom will provide extremely fantastic SOT when a sim card isn't being used. If you have an active sim card then something is wrong with the monitoring because Gsam is showing 0%, it should show something even if you havent made a phone call for days.
Do whatever you want it's your phone:
I still think that you have encryption or corruption issues and its bad enough for your to make a post about it. FYI : The battery dying doesnt slow down the phone. Yes, some stock roms, notably Apple intentionally by choice changed the kernel core settings automatically on aging batteries. Hence the huge controversy a couple of years ago, that isn't happening to you.
A dying battery doesn't slow down the phone, evn cold solder joints do not slow down the phone, they keep a phone from booting to system and to recovery. The only thing left is corruption or thermals, which on this phone good luck editing thermals because they are mostly encrypted. The remaining possibility is corruption, post your log files and lets see what's actually going on.
Again, what would slow down your phone even in recovery?
It's always thermals, or corruption. Slow to start up, even in recovery.: We can rule out thermals unless your battery temp or cores temps are extremely high. This leaves corruption. if its slow while booted into the system, then you may have apps or processes crashing and you are not aware of it. If that is true, then eventually the phone may stop booting up altogether. If its thermals causing overheating you should truly resolve this issue immediately before actual heat damage occurs. Did you ever flash display refresh rate mods? If so your DTBO partition could be the issue....corruption.
Use this program to provide an app list : https://play.google.com/store/apps/details?id=de.onyxbits.listmyapps ( Weed out any unknown programs that you may not realise are installed. Post the list along with complete logs. Once you see these crashes, that I am sure the logs will show: Do as I suggested earlier: wipe and "format" your phone. Then later use best practices and remove passwords before changing kernels

Cheers. I'll try what you suggest.
I might have some questions in the future regarding format and some other things.
Never flashes display refresh rate and never noticed any overheat issue on my phone.
Sure, I'll do something like you said as soon as possible.
PS : you said "before remove passwords". You mean in the parameters of the phone like schema/diagram, pin, etc ?
Cheers

Erpe7 said:
Cheers. I'll try what you suggest.
I might have some questions in the future regarding format and some other things.
Never flashes display refresh rate and never noticed any overheat issue on my phone.
Sure, I'll do something like you said as soon as possible.
PS : you said "before remove passwords". You mean in the parameters of the phone like schema/diagram, pin, etc ?
Cheers
Click to expand...
Click to collapse
You could remove password under data/system/locksettings.bin But it's better to just go the settings//security/ *.* < remove whatever you have setup : prints and face unlock first before, pattern or pin.
Another good practice for Android 10, should you go there is :
Extract the boot image from the rom
Place it inside the downloads folder.
When ready to flash root, patch to the boot image first, ( this links the existing system binary credentials into the boot image)
Boot to recovery flash boot to boot
Then flash magisk > then boot to system and you will have no issues whatsoever with root.
Afterwards, if you decide to flash different kernel, Magisk is more likely to stay stay persistent.
I hope everything is good from this point forward take care.

@tsongming Thanks for reminding me the locksettings.bin thing because I used it once on my old phone and I forgot that.
Never installed 10 yet. But I take carefuly your advice.

Hello!
Did you fix it? Because it's happening to my Mi 8 too. It's exactly the same issue, the phone takes a long time to boot up, to open apps and even to boot into TWRP

I have that issues on my mi8
I had this problem with me before and I solved it by flashing the last official ROM, Now the problem happened to me again and I do not know what is the reason behind it @tsongming
Sent from my MI 8 using Tapatalk

ahmadbasher011 said:
I have that issues on my mi8
I had this problem with me before and I solved it by flashing the last official ROM, Now the problem happened to me again and I do not know what is the reason behind it @tsongming
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
I recently had some issues with my phone as well. I was able to get my phone back to normal functioning by flashing the latest stable fastboot rom using the flashall.bat method. (dipper_global_images_V11.0.3.0.QEAMIXM_20200118.0000.00_10.0_global)
I kept everything stock for a few days even recovery, to ensure once that everything was back to normal.
Next I flashed the latest OrangeFox beta recovery, and I highly recommend the latest beta build over any other version of Recovery, it will decrypt when official Twrp will not. It is now more up to date than the LR Team version, and all of the bugs have been solved by DarthJabba. In fact, he even added a script to work around poorly designed startup scripts, which are suprisening not consistent between the wide range of custom roms for the Mi8.
Today, I am still using Orange Fox, ( OrangeFox-R10.1_002-Beta-dipper) and the latest stable Magisk. I no longer have freezing, unexpected shutdowns, slow starts, or poor battery life. My issue was without a doubt corruption, and bugs with the mid february version of Xiaomi.EU. The last 2 releases have been solid.

Since this weekend I face the same problem. Every action seems to bit slower than before. And I don't know what I did that resulted in this problem. The last thing I remember I installed was the new Miui12 live backgrounds. But I deleted them again.
I'm on stock since some weeks.
But I don't want to install everything from the beginning again.
Do you know how to solve the problem without wiping everything?
Edit: As I think about it, it seems as if the caching of the apps doesn't work as good as before and the killing of apps is too aggressiv.
But what did affect it?
Edit: I found the solution for my problem.
With Android Battery Historian was able to find the process that made the trouble.
It was the Miui wallpaper carousel app. After deleting it the problems were gone.

Erpe7 said:
Hi guys,
I'm a bit concerned about my mi8. Since several weeks now the phone is getting so slow to boot, even into recovery mode !
For exemple, today before starting to see the havoc logo spinning I count more than 20 spins. Months ago it took only 5 or 6, 2 weeks ago : more than 8... Etc.
When phone is started first apps tha usualy open really fast (Viper4fx, gsam battery monitor, magisk notifications) are so slow to open. Some other apps same thing the moment I open them.
Click to expand...
Click to collapse
it's a hardware issue and it's going to keep coming back, i spent the last two months trying to resolve it but i gave up.
it seems that UFS chip malfunctions on a lot of F1 and mi8 phones.

danielnavarrowo said:
Hello!
Did you fix it? Because it's happening to my Mi 8 too. It's exactly the same issue, the phone takes a long time to boot up, to open apps and even to boot into TWRP
Click to expand...
Click to collapse
Sorry for repling only now guys...
Thx to all who proposed to solve my issue, I will tell you what I did to fix my mi 8.
I did a crystal clean flash :
- downloaded & installed last miui image using miflash
- used "clean all" at the bottom right (be careful to not choose something else like "lock boot loader ")
- then you'll need to flash recovery (twrp), then format data by typing yes. Then copy from where you want your custom rom, flash it flash magisk and boot.
I did this several months from now and my phone is like just new!
No issue at all since.
I guess installing lot of different kernels like I did before must have broken something and hopefully this could help if you dont have more serious issues.
Ps: battery is more than ok and there is no hardware problem.
Thx again to Dexer125 for his help!
Sent from my dipper using XDA Labs

Erpe7 said:
Sorry for repling only now guys...
Thx to all who proposed to solve my issue, I will tell you what I did to fix my mi 8.
I did a crystal clean flash :
- downloaded & installed last miui image using miflash
- used "clean all" at the bottom right (be careful to not choose something else like "lock boot loader ")
- then you'll need to flash recovery (twrp), then format data by typing yes. Then copy from where you want your custom rom, flash it flash magisk and boot.
I did this several months from now and my phone is like just new!
No issue at all since.
I guess installing lot of different kernels like I did before must have broken something and hopefully this could help if you dont have more serious issues.
Ps: battery is more than ok and there is no hardware problem.
Thx again to Dexer125 for his help!
Sent from my dipper using XDA Labs
Click to expand...
Click to collapse
I can confirm this.
I have been unrooted on stock for a few months now and have had no problems since then.

Hello, I have the slow issue (Androbench app with poor performances) after several dates when I have rooted my phone: Mi8 Chinese version with stock global ROM.
After unroot the phone, several days after, the phone works fine with Androbench app with good performances.
I need root my phone to use Magisk hide for Google Pay in order to avoid the Google block for contactless payment.
Can anybody help me about the understanding of this behaviour?
I do not know the reason why the phone is slow after root and why the phone works fine after several days after rooting.
Thanks in advance. Regards

roberbas said:
Hello, I have the slow issue (Androbench app with poor performances) after several dates when I have rooted my phone: Mi8 Chinese version with stock global ROM.
After unroot the phone, several days after, the phone works fine with Androbench app with good performances.
I need root my phone to use Magisk hide for Google Pay in order to avoid the Google block for contactless payment.
Can anybody help me about the understanding of this behaviour?
I do not know the reason why the phone is slow after root and why the phone works fine after several days after rooting.
Thanks in advance. Regards
Click to expand...
Click to collapse
Hi,
Mine has hardware issue (rooted).
Didn't try to unroot it if there is a difference like you describe.
Can't help you with magisk hide. I don't use it.

I have this issue with my mi 8 guys, just happened yesterday
So flashing the latest official rom via miflash is the way to fix it?

Irish_Dude said:
I have this issue with my mi 8 guys, just happened yesterday
So flashing the latest official rom via miflash is the way to fix it?
Click to expand...
Click to collapse
Hello, yes in my case. Sometimes, with wipe all, internal storage included, the problem it solved.
Recently I have the issue again without root: only with custom rom flashed. Several times the issue was reproduced out of my habitual site during vacances.
Thanks