Database Develop

Fingerprint Hardware not available

How is that possible?
I did read I am not the only one, though in his case it might be a hardware issue.... which I would hope it is not.
What I did with a brand new 3T:
1. Installed TWRP 3.0.3, wiped phone (format system, format data)
2. uploaded and restored an image from my so far daily driver OnePlus3 (Sultan's CM 13) - (TWRP was complaining about the backup image being ext4, while the 3T is on F2FS) - I know not the clean way... but it seemed fine
3. I meant to install a fresh CM13 over it and SuperSU (I thought if there are difference, it would be recognized by the installer) but I forgot, bootet and..... Oops, it works
4. I encountered a problem with the Fingerprint Sensor.... on this CM13 install *crapshoot*
5. Thought it might have restored the Firmware of the 3 as well (it didn't) and crapped my pants.
6. Installed the current OnePlus 3T OxygenOS 3.5.4 (2016-12-19) via ADB sideload to get the original Firmware and everything back (which seemed not necessary but hey, I tried)
7. I even tried the OOS 4.0.1 Beta 9 (or 10) via sideload in the hope it would give me the correct firmware that is able to talk to the Fingerprint sensor. It is a newer firmware though... no luck though.
8. Neither a) OOS 3.5.4, b) OOS 4.0.1 or c) CM 13 gave me a working sensor. CM 13 just cancels the fingerprint enrollment, OOS gives me at least a message (see picture) "Fingerprint Hardware not available".
9. The rest was working well... very well...
Internal Tests of *#808# let me test the Fingerprint sensor and it say it works well (aside from the 'quality test' in chinese I can't read)... see attached pictures
I am frustrated... did I kill it, is it broken, is something wrong? Any ideas?
Edit:
Physical buttons (left, center, right) work with haptic feedback. The moment I get to the point of the first pic (Recording Fingerprint) the whole button bar stops working. Not haptic feedback, not even getting back or the Task manager. I have to push the power button, and again, get to inset PIN to unlock and are back in the phone, one step back in the Fingerpring enrollment process and the HW button bar works again. I klick 'Next' to get to the step it was unresponsive before... and they stop working again.
In my opinion that shows the sensor itself is not broken...

Update:
Desperately doing every step again... this happend:
After sideloading 3.5.4 and 4.0.1 images from OnePlus again.... tadaaaa... a wipe/fresh install of 4.0.1 (OnePlus3TOxygen_28_OTA_037_all_1701041831_a2ba632ce9) got me a working Fingerprint Sensor.
Now I am in the process of sideloading the latest stable 3.5.4 with the aim of getting the proper firmware in the device to run Sultan's CM13 - he did implement a firmware check in hist install script. I assume this was to force people with an outdated FW to update... unfortunately it also denies installation with a newer Firmware.
Let's see if we are going somewhere...

Try the unbrick tool
You could always try the unbrick tool by Haris K, this is the link --> https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306

ayush2901 said:
You could always try the unbrick tool by Haris K, this is the link --> https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
How can you brick a device these days? Not as long as you get somehow a bootloader running and that is damn hard to kill - if not impossible.
So thank you for the tip. I just do not see what a tool can do that you can't do with a fastboot / adb command line. And I prefer to understand what is happening. A magic 'black box' is not really helping to improve your understanding of your device. That is just my thought.

Conclusion time
As is turned out, the fingerprint sensor is NOT broken. It did work in the sideloaded 4.0.1 OOS. This gave me fresh energy to examine more circumstances... and why it did not work before, when I did the same thing. It took hours to repeatedly install various image, siedloading 1.5 GB + install procedure takes forever. But knowing that the sensor itself works, it would be just a matter of time and correct installation (which I seemed to **** up in the first place).
1. siedload OOS 4.0.1 worked
2. after that 3.5.4 was in order... and Yes! it also worked
(I have no clue what kept it before from working, as I did all these steps before already)
3. with Firmware of 3.5.4 -> Format System & Data -> Switch Data to ext4 (i was highly annoyed the up to 10 mins delay of TWRP)
4. Install Sultan's CM13 + nano GApps + SuperSU 2.79 -> boot -> FP sensor works!
YEAH - happy
I can't say for sure but it seems very likely that it was indeed the firmware that caused the trouble.
But it seems initially the FW was somehow botched up... and later when the Firmware was corrected it still didn't work due to my wrongful OS recovery (CM13 which I assume still run drivers for OnePlus3 and not 3T) that was the cause.
Lesson learned: Don't be greedy when it comes to installing a new phone and do the hard work of reinstalling, copying and setting up every single ****. Not really a surprise but I guess it needs to be learned over and over. It ****ing bugs me, since I can't not Titanium restore crucial setting / apps like my Exchange account and Line to a new phone. That means I loose months of transactions (contacts, chats, pics in LINE, which is the predominant App here in Asia).
I would welcome any hint how to streamline copying apps that are not willing to work on a new device as a 1:1 copy - particular LINE that does refuse to work even with adjusted device ID.

Problem with lockup / display not turning on across various roms, rooted droid

I successfully rooted my droid (that came with lollipop), using this guide
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
installed twrp backed up the stock OS and installed resurrection remix lollipop rom. I did not install any different modems or radios as I planned to stay on lollipop.
Everything worked great yet after a day or two the display/phone would appear to lock up. I can press power, the display doesn't come on and when (usually) moving the the volume up/down I do hear sounds. Sometimes at this point it will reboot by itself, other times I have to reboot it.
When it comes up it goes through the android is upgrading thing, and sometimes works fine after, sometimes not, regardless eventually this problem repeats.
Thinking it was perhaps RR I tried straight Cyanogenmod, and eventually the rooted stock OS, both have this same problem.
I've tried using it with very minimal installed in the way of apps, same issue.
I've tried saving the log to SD to peer at later, but going through it I don't really see anything obvious to show what the problem is.
I"m wondering if there's a problem with the phone itself (it's a refurb) and am considering unrooting it and returning it.
Anyone seen this or thoughts on what might be the issue?
p.s.
if you happen to have a good link handy to an unrooting guide you might shoot it my way thanks.
thanks in advance!

What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
There are ways to grab logs after a reboot, but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.

thanks for the reply
ChazzMatt said:
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
Click to expand...
Click to collapse
I tried the last released CM lollipop snapshot, as well as the last nightly.
For RR it was last released, "ROM OS Version: 5.1.x Lollipop"
ChazzMatt said:
There are ways to grab logs after a reboot,
Click to expand...
Click to collapse
Yeh I've been saving it to the SD so I can view it after a reboot, I've looked at 4 or 5 of them after the problem occurred and at least to me nothing really stood out
ChazzMatt said:
but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
Click to expand...
Click to collapse
Yeh I expect it might periodically need a reboot but if it's just unpredictiably locking up or rebooting on its own it's not very usable.
I think I'm just going to have to try to unroot and return, maybe I'll go with a LG V20 as I don't want to have pay to re-root another one of these and possibly have same issue. Also the whole pay to have some app do something secret to my phone does leave me a bit uneasy.
Kind of a bummer as I'm actually pretty impressed with this device, fast, good battery, takes nice photos, only drawbacks for me are no removable SD and lack of LED notification, but I was willing to live without those given how good everything else was.
thanks

Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Android Version: 7.1.2
Current Rom: AOKP
Kernel: 3.10.107-Stock-bhb27-nougat-kerneL

MrN00b said:
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Click to expand...
Click to collapse
FWIW and in case it helps you or someone else, I seem to have fixed mine finally, here's what I did.
First I installed latest twrp (mod 4) https://androidfilehost.com/?w=files&flid=39562 (there's a thread on this twrp if you want tor read on it). That in itself didn't fix the issue but did finally let me format and got rid of an 'mkfs.f2fs: invalid option -- r, ERROR=1' type error I used to get.
I installed this stock zip from twrp as described in thread:
https://forum.xda-developers.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041
It would never actually boot it would shut my phone off not long after showing the boot screen, and I'm not sure if doing that was necessary or not.
Taking some suggestions from here:
https://forum.xda-developers.com/droid-turbo/help/help-request-custom-rom-phone-unlocked-t3767070
I dug up the last official CM 13 snapshot:
https://www.google.com/search?q=cm-13.0-20161221-SNAPSHOT-ZNH5YAO3Y5-quark.zip
sha1: 9a219dd487c27e51b0c5c4922812838f394099c5
Wipe and installed with no gapps and voilà it would boot consistently. Without reinstalling I tried installing pico gapps and it would still boot though it took maybe 15 mins initially.
I want Nougat so I wiped and installed lineage-14.1-20180612-UNOFFICIAL-quark.zip from https://forum.xda-developers.com/moto-maxx/development/rom-t3494646 again no gapps and it also booted fine, whereas previously it would hang on booting. Without reinstalling ROM I tried installing opengapps nano and it would just hang.
I could then no longer get it to boot again, so I reinstalled CM13 no gapps, which booted fine, wipe and install lineage-14.1-20180612-UNOFFICIAL-quark.zip no gapps, and now it boots fine though currently it's taking a while.
I should perhaps note I took twrp backups inbetween steps whenever I had a working boot, (ex before installing gapps), but once the phone went back to hanging on boot, those restores didn't help. Only reflashing CM13 seemed to clear things up.
My ultimate goal is a LOS ish Nougat/Oreo ROM with no gapps using microg, and running tmobile, I'll see what I end up with.

Just ordered razer phone 2 looking for custom os instructions.

So from what i gathered TWRP doesnt work yet on the razer phone 2 and lineage os doesnt have a build for this phone yet i gotta ask what is available for modding razer and what is the step by step to make that happen. i seen some instructions but other than root there isnt much to do.

SynGreis said:
So from what i gathered TWRP doesnt work yet on the razer phone 2 and lineage os doesnt have a build for this phone yet i gotta ask what is available for modding razer and what is the step by step to make that happen. i seen some instructions but other than root there isnt much to do.
Click to expand...
Click to collapse
TWRP works just fine on this device. It's installed when you fastboot flash arter97 kernel and it works perfect. He just updated it to r10. Good luck!!
Edit: as far as ROMs look around in this forum you'll find a couple of different ones in the same section as arter97 :good:

which one do you suggest? i dont see much of a selection.

SynGreis said:
which one do you suggest? i dont see much of a selection.
Click to expand...
Click to collapse
Right now there really aren't any, although there are a few in development, such as AOSP. I think the initial high price, specialized hardware & relative unpopularity has not helped attract any serious development.
I've noticed that ROM development has decreased significantly in the last few years. I remember the days of the Samsung Galaxy Nexus & the HTC Evo 4G where it seemed as if there was a new ROM released every week. I think its because (a) recent Android operating systems are offering greater customization out of the box, & (b) with the new A/B partitioning scheme, it makes ROM development more difficult.

Cancel your order. Get your money back. This phone while it is awesome at gaming and has a great screen. The OS is ****ty to say the least. I have had more issues with it freezing up. Not wanting to download apps from the play store. Not allowing me to install apps that I have already downloaded on my device. Now it's showing up as the Asus Rog II. This phone is the biggest heaviest piece of **** I've ever had. I promise you if everyone knew the issues this phone has you couldn't give it away free.

mattwheat said:
Cancel your order. Get your money back. This phone while it is awesome at gaming and has a great screen. The OS is ****ty to say the least. I have had more issues with it freezing up. Not wanting to download apps from the play store. Not allowing me to install apps that I have already downloaded on my device. Now it's showing up as the Asus Rog II. This phone is the biggest heaviest piece of **** I've ever had. I promise you if everyone knew the issues this phone has you couldn't give it away free.
Click to expand...
Click to collapse
Mine showed as in rog 2 the last time I reloaded the OS. It's because it searches for "phone 2" and randomly guesses. No biggie, just fix it in the settings. No issues here from playstore, if you do it's common on every Android phone and fixable by clearing the data from the app. Maybe you should reflash the stock firmware? I don't see why you would call this phone ****ty. It's basically running AOSP stock except some theming from Razer. I fixed some freezing issues by reseating the Sim and SD card that I have. This thing rocks, just saying.

I've cleared the play stores cache, data, and dalvic in every method imaginable. Even google play services. I've restored backups, flashed stock .imgs, and flashed the stock odex Ron and the deodexed rom. It doesn't start failing to install play store apps till after I initially install most the apps I normally use then a while later when I think of one I forgot I'll go and try to install. That's when it starts messing up. If I watch a video threw some websites built in player on the webpage I'm viewing... about 15 to 20 seconds into the video everything but sound freezes. And will not correct itself. I have to hold the power button till it reboots. Only videos I can watch without issue is from the YouTube app. It's ridiculous. I've unlocked, rooted, and crack flashed tons of roms on all of my pixel and Nexus devices without any issue besides the random freeze. Which can be quickly fixed by toggling the screen on and off. This **** is ridiculous. So over this phone.

matt that might be just you i havent experienced any issues with this phone whatsoever.
"I think its because (a) recent Android operating systems are offering greater customization out of the box, & (b) with the new A/B partitioning scheme, it makes ROM development more difficult."
can you provide more info on this A/B partition? id love to see what customizable stuff i can do with this.

mattwheat said:
I've cleared the play stores cache, data, and dalvic in every method imaginable. Even google play services. I've restored backups, flashed stock .imgs, and flashed the stock odex Ron and the deodexed rom. It doesn't start failing to install play store apps till after I initially install most the apps I normally use then a while later when I think of one I forgot I'll go and try to install. That's when it starts messing up. If I watch a video threw some websites built in player on the webpage I'm viewing... about 15 to 20 seconds into the video everything but sound freezes. And will not correct itself. I have to hold the power button till it reboots. Only videos I can watch without issue is from the YouTube app. It's ridiculous. I've unlocked, rooted, and crack flashed tons of roms on all of my pixel and Nexus devices without any issue besides the random freeze. Which can be quickly fixed by toggling the screen on and off. This **** is ridiculous. So over this phone.
Click to expand...
Click to collapse
The freezing is due to a bug in Google Chrome. All you have to do to fix this issue is roll back the app version to 72 because version 76 doesn't work on our RP2.
Edit: uncheck auto update

Only freeze I had so far was with the infamous switch switch to the tele lens. Not a single other issue with software.

Other question, if you put the display at 120hz, and you scroll something, does it 'feel' like your finger sticks to text/icons?
I mean, is there no delay like you normally would have at 60hz?
On the Oneplus 7 Pro the 90hz is already a big improvement (less delay) but 120 should really be kickass... anyone?

MasterThiefGarrett said:
Other question, if you put the display at 120hz, and you scroll something, does it 'feel' like your finger sticks to text/icons?
I mean, is there no delay like you normally would have at 60hz?
On the Oneplus 7 Pro the 90hz is already a big improvement (less delay) but 120 should really be kickass... anyone?
Click to expand...
Click to collapse
Take this with a grain of salt, as I just got the RP2, but its the most responsive, "sticky" feeling Android phone I've used. 120hz is like night and day to me.
On a related note, Firefox Fenix with webrender enabled feels significantly more responsive than Chromium atm, as it seemingly renders the whole page instead of stuttering as you scroll like Chrome.

JDBarlow said:
TWRP works just fine on this device. It's installed when you fastboot flash arter97 kernel and it works perfect. He just updated it to r10. Good luck!!
Edit: as far as ROMs look around in this forum you'll find a couple of different ones in the same section as arter97 :good:
Click to expand...
Click to collapse
how can you get twrp in? Everytime i try to flash twrp in i get stuck at powered by android logo.

SynGreis said:
how can you get twrp in? Everytime i try to flash twrp in i get stuck at powered by android logo.
Click to expand...
Click to collapse
Which version of Android are you running currently?
MR1 will be arter97 r11
MR2 will be arter97 r12
http://arter97.com/browse/aura/kernel/

duplicate post

JDBarlow said:
Which version of Android are you running currently?
MR1 will be arter97 r11
MR2 will be arter97 r12
http://arter97.com/browse/aura/kernel/
Click to expand...
Click to collapse
i havent flashed either of those arter because im worried that its gonna screw things up again.
Im sitting on the 9.0 MR1 stock image from razer.
https://developer.razer.com/razer-ph...actory-images/

SynGreis said:
i havent flashed either of those arter because im worried that its gonna screw things up again.
Im sitting on the 9.0 MR1 stock image from razer.
https://developer.razer.com/razer-ph...actory-images/
Click to expand...
Click to collapse
So are you on the global version? If so let it update to MR2 and fastboot flash boot arter97 r12 and you'll be just fine.
Which version are you running then to get stuck on boot logo?
Edit: if you want to stay on MR1 then flash arter97 r11

i tried updating to mr2 but says installation failed.
all i do is
faatboot flash boot kernal.img?

I just rooted MR2 to show you. It took me less than 5 minutes to do the whole process of fastboot flashing kernel booting straight into TWRP recovery which is included then installing magisk immediately rebooting into system and updated magisk. Done

JDBarlow said:
I just rooted MR2 to show you. It took me less than 5 minutes to do the whole process of fastboot flashing kernel booting straight into TWRP recovery which is included then installing magisk immediately rebooting into system and updated magisk. Done
Click to expand...
Click to collapse
My only question is, which version zip of magisk did you use in TWRP to flash? 20 or the latest beta? I'm rooted now with a modded boot.img that someone else used the canary/latest beta. Just don't want to screw myself and end up having to flash mr1 again then taking the update.

Root galaxy S10 (July security patch update)

hi to all, has anyone managed to root on galaxy s10 with the July security patch update? I tried the same method with magisk but there is nothing to do, every time it gives me a different error. In the last attempt I made during the boot phase, in the upper left corner, it was written: "only official released binaries are allowed to be flashed" or something like that.

You didnt do it right. I would suggest youtube the magisk rooting process

Same tried to root it
I, was able to get it to root but the camera still makes my device rebooted
And tried to do it with ap file by changing recovery inside to the patched twrp that didn't work just booted into stock recovery instead

Cristian-104 said:
hi to all, has anyone managed to root on galaxy s10 with the July security patch update? I tried the same method with magisk but there is nothing to do, every time it gives me a different error. In the last attempt I made during the boot phase, in the upper left corner, it was written: "only official released binaries are allowed to be flashed" or something like that.
Click to expand...
Click to collapse
I have already tried EVERYTHING, in download mode I can not get the> Prenormal <to> Check ing <. The option of OEM lockdown is there, has always been there.

TheUndertaker21 said:
Same tried to root it
I, was able to get it to root but the camera still makes my device rebooted
And tried to do it with ap file by changing recovery inside to the patched twrp that didn't work just booted into stock recovery instead
Click to expand...
Click to collapse
TWRP ≠ Root.
With the latest patch the camera crashes if TWRP is flashed. With stock recovery everything should work fine.
I'm on Exynos ASG8 without any issues, except slow wifi in apps (not browser).

Jannomag said:
TWRP ≠ Root.
With the latest patch the camera crashes if TWRP is flashed. With stock recovery everything should work fine.
I'm on Exynos ASG8 without any issues, except slow wifi in apps (not browser).
Click to expand...
Click to collapse
OH that's a known issue then?
I need my custom rom and twrp lol

TheUndertaker21 said:
OH that's a known issue then?
I need my custom rom and twrp lol
Click to expand...
Click to collapse
It is...nearly everytime Samsung throws out a new security patch TWRP is crashing the camera.
This is what I found out after having the same issue. I don't know if there's a new version for the latest patch.
Aren't the custom roms based on One UI? Shouldn't the stock recovery still work? (I really don't know)

Jannomag said:
It is...nearly everytime Samsung throws out a new security patch TWRP is crashing the camera.
This is what I found out after having the same issue. I don't know if there's a new version for the latest patch.
Aren't the custom roms based on One UI? Shouldn't the stock recovery still work? (I really don't know)
Click to expand...
Click to collapse
TWRP is good to have if something goes wrong.
I can have custom rom without twrp but that's not the whole of it.
Hope it gets patch soon

TheUndertaker21 said:
TWRP is good to have if something goes wrong.
I can have custom rom without twrp but that's not the whole of it.
Hope it gets patch soon
Click to expand...
Click to collapse
It's easy to flash it, even without running system.

Hi everyone, I'm still ASD4 and basically haven't update since because everything is a hassle these days. Now I thought maybe it's time to update, but keep reading things like this and camera, wifi bootloops problems etc.
Are these issues a real thing? or just some individual cases where it happens?

It's real like a $2 dollar bill.

bininga59 said:
I have already tried EVERYTHING, in download mode I can not get the> Prenormal <to> Check ing <. The option of OEM lockdown is there, has always been there.
Click to expand...
Click to collapse
You have to turn off all data ( wi-fi and 4g) and manually set the date to 7 days back.

FlatOutRU said:
You have to turn off all data ( wi-fi and 4g) and manually set the date to 7 days back.
Click to expand...
Click to collapse
I have already made. As I said, I unlock the bootloader and lock (developer option or download mode) as I want,> prenormal <does not go away.

Did a root today without issues on my S10 with ASG8

ru_dimka said:
Did a root today without issues on my S10 with ASG8
Click to expand...
Click to collapse
everything works? twrp installed? magisk etc.?

chieco said:
everything works? twrp installed? magisk etc.?
Click to expand...
Click to collapse
There is no twrp for ASG8. Others stuff works well!

ru_dimka said:
There is no twrp for ASG8. Others stuff works well!
Click to expand...
Click to collapse
I'm always afraid that I install something or make a small change and end up in a bootloop... I wish twrp and everythign work just fine like before and I could make a backup after installing a rom and doing the most basic stuff.

Since this is the first post that comes on Google for "only official released binaries" "s10".
I had this problem again and again, and it seems that it was caused by one of the reboot not being done with the correct timing with the 3 buttons.
The thing I was missing was after flashing the patched AP files (and the other files).
When you restart, keep the 3 buttons pressed until you see the blue screen and then release only power (keep vol up + bixby) to get into reset mode.
I think I didn't keep them pressed long enough.
If the device restarts, keep pressing the 3 buttons (never let it restart without pressing them).
Once the factory wipe has been done: Restart with the 3 buttons, and keep them pressed until 1 to 2 sec after the screen that asks you to press the power button to continue.

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