Widevine dropped to Level 3 caused by official update - OnePlus 8 Pro Questions & Answers

Hi,
who has experienced the same loss of HDR/HD streaming support with update 10.5.5/10.5.6 (Bootloader wasn't unlocked)?
Anyone got a solution to get back Widevine L1?
As far as we found out in the Oneplus forum all model and firmware variants are effected.
I sent logs to Oneplus through the community app but the answers were more or less prepared and only telling me that they research on this issue. Someone got the info from German support that it will be fixed through OTA, but I don't think this will be possible and most likely we have to go for RMA.
To find out about DRM/Widevine level you can use DRM Info app or Netflix in the player properties.
Best regards,
Bernd

This happened to me as well. Noticed the other day on 10.5.8 that Netflix wasn't in HD anymore. Did not unlock bootloader, just did OTA's through the system, no Oxygen Updater .
I tried unlocking and then re locking the bootloader but this did not fix the issue, I still have L3.
Really hoping I don't have to RMA for this.

Okay I was thinking about doing the same, but obviously it didn't fix it for you so I skip it...
Coming from Oneplus 5 with it's DRM drama this really annoys me.

See this post in OnePlus forum:
https://forums.oneplus.com/threads/...int-registration-error.1218379/#post-21604919
As far as I understood, flashing or in our case updating causes the persistent partition (which is encrypted with the first registered fingerprint) to get unreadable, if you removed the first fingerprint data (which I did when I registered my fingerprints freshly, after applying a screen protector) - but I could be also wrong as I used Google Translate read the original post. Maybe someone who is deeper in the rabbit hole can confirm this theory, cause it would be great to know at least where the issue comes from and if a RMA is required or a solution can be achieved via OTA.
Bernd

So removing FP data corrupts the persist partition, correct?
Of that so;
Removing FP breaks FP
Cross flashing breaks FP
Magisk Canary breaks FP
Relocking breaks FP
I did send my phone for RMA after having it for only two days. So I've been reading up on this issue and for now I have this.
Backup your persist partition
Root only with Stable Magisk 20.4
Make your own patched image
Don't relock your bootloader
Altho I can't seem to find how to backup that partition without unlocking the bootloader

I wouldn't had unlocked my bootloader if I knew it's causing so many issues. Honestly I need root just for vanced yt... So it's not worth the troubles I had ?

Balthazard said:
So removing FP data corrupts the persist partition, correct?
Click to expand...
Click to collapse
possible, as said I'm neither that far in the android rabbit hole nor is my Chinese that good but it's possible that FP is the bad guy in this game.
Not possible to backup with ADB or Fastboot?
But as far as I've read through this thread https://forum.xda-developers.com/showpost.php?p=80139723&postcount=26 even a backup/restore doesn't help. For the moment I hope for a workaround the DRM sh*t by OnePlus - I mean who the hell would use an Android Phone for content piracy...

Bootloader still locked on INAA 10.5.8, Im on L1. I had installed and uninstalled fp, now its back in, no changes
Patching your own is the smart move inho

bigjailerman said:
I had installed and uninstalled fp, now its back in, no changes
Patching your own is the smart move inho
Click to expand...
Click to collapse
Didn't touch my bootloader so far. Original FP was with 10.5.4 and deleted/readded with 10.5.6.
Did you mean by re-adding them with 10.5.8 was bringing L1 back? What should be patched?

Although my setup isn't the same as everyone else here, (bl unlocked, rooted & custom kernel. Also on beta 11). Noticed that Netflix had dropped to L3 in the playback settings section. Cleared storage on the app from settings & used magiskhide on Netflix. Seemed to put the app back on L1.

Related

PSA: Configure your fingerprint scanner before flashing any ROM

Earlier today I was mucking about and decided to play around with the fingerprint scanner for the first time. When I went in to settings and clicked the fingerprint manager, I received an error stating that the scanner is borked, and to reset my device to fix it. Rebooting did not fix the issue.
Soon I found another person with the same issue, who said that he was able to fix it by flashing stock NJ7 via Odin. After a bit of chatter we realized that neither he nor I had set up the fingerprint scanner before flashing a ROM. We basically booted the phone and went straight to rooting it, and flashing ROMs on it.
I can confirm that re-flashing the stock ROM via odin allowed me to set up the scanner successfully, and that the functionality has not been affected by any subsequent ROM flashing.
I do not understand the mechanism behind why this happens, it is just my experience. Perhaps there is some sort of validation that is run the first time you use the scanner, making sure you are running official firmware, and then setting a flag somewhere? How then would that flag be saved for all subsequent rom flashes? Hidden partition or some ****? Hardware flag? I dunno I don't get it, but I figured out how to fix it by golly. Hopefully this helps someone else.
If any others can confirm the same issue, we may want to add this as a step in the rooting/romming how-to threads, so that others don't run into the same issue.
One good thing is that when I flashed stock via odin, it didn't wipe my data. I was able to then flash TWRP and then Dynamic Kat again, keeping all of my settings the whole way through. Ended up not being as much of a hassle as I thought it was going to be :good:
Thank you for sharing this, I have to say in my case it is not working now i did get the phone rooted and then added jovys rom then did my setup the fingerprint scanner worked for me, then i installed dynamic rom and then the later update of same rom and then the fingerprint scanner is no longer working for me there is a new update for the rom i am going to flash and see if it works now as in a previous version the bloat from samsu g had been removed and with jovys rom being stock rooted it was still there, so i am wondering if it has to do with some of the bloat from Samsung and it being removed that breaks the fingerprint scanner, i will report after i flash the new version of dynamic.
santos.moreno3 said:
Thank you for sharing this, I have to say in my case it is not working now i did get the phone rooted and then added jovys rom then did my setup the fingerprint scanner worked for me, then i installed dynamic rom and then the later update of same rom and then the fingerprint scanner is no longer working for me there is a new update for the rom i am going to flash and see if it works now as in a previous version the bloat from samsu g had been removed and with jovys rom being stock rooted it was still there, so i am wondering if it has to do with some of the bloat from Samsung and it being removed that breaks the fingerprint scanner, i will report after i flash the new version of dynamic.
Click to expand...
Click to collapse
I first noticed the problem while I was on Dynamic Kat 1.1 and thought the same thing, that it was something to do with the Sammy apps, but it still didn't work after updating to DK 1.2. I've had it both working and non-working whilst running the same ROM (1.2,) and the only thing different between the two instances was the fact that I configured it while I was in stock in one instance.
This is important information. Hopefully the devs will be able to fix this asap. Thanks!!
Wow thank you BotsOne! I'm having the same issue. I'll try this in the morning. Before I rooted, I set up the fingerprint scanner and it worked fine the I switched back to swipe, then rooted. After rooting I installed Jovys rom and lo it hasn't worked since. Does the lock screen have to be set to fingerprint scanner at the time of flashing roms or can you set it up once and move on from that point forward? Thanks again!
android242 said:
Wow thank you BotsOne! I'm having the same issue. I'll try this in the morning. Before I rooted, I set up the fingerprint scanner and it worked fine the I switched back to swipe, then rooted. After rooting I installed Jovys rom and lo it hasn't worked since. Does the lock screen have to be set to fingerprint scanner at the time of flashing roms or can you set it up once and move on from that point forward? Thanks again!
Click to expand...
Click to collapse
Honestly I'm not sure. We need a few more people with the same error to get to the bottom of what's going on here. I could be way off with my assumption. We need a bit more info.
Cool I'll try tomorrow and report back..
BotsOne said:
Earlier today I was mucking about and decided to play around with the fingerprint scanner for the first time. When I went in to settings and clicked the fingerprint manager, I received an error stating that the scanner is borked, and to reset my device to fix it. Rebooting did not fix the issue.
Soon I found another person with the same issue, who said that he was able to fix it by flashing stock NJ7 via Odin. After a bit of chatter we realized that neither he nor I had set up the fingerprint scanner before flashing a ROM. We basically booted the phone and went straight to rooting it, and flashing ROMs on it.
I can confirm that re-flashing the stock ROM via odin allowed me to set up the scanner successfully, and that the functionality has not been affected by any subsequent ROM flashing.
I do not understand the mechanism behind why this happens, it is just my experience. Perhaps there is some sort of validation that is run the first time you use the scanner, making sure you are running official firmware, and then setting a flag somewhere? How then would that flag be saved for all subsequent rom flashes? Hidden partition or some ****? Hardware flag? I dunno I don't get it, but I figured out how to fix it by golly. Hopefully this helps someone else.
If any others can confirm the same issue, we may want to add this as a step in the rooting/romming how-to threads, so that others don't run into the same issue.
One good thing is that when I flashed stock via odin, it didn't wipe my data. I was able to then flash TWRP and then Dynamic Kat again, keeping all of my settings the whole way through. Ended up not being as much of a hassle as I thought it was going to be :good:
Click to expand...
Click to collapse
Yes, I am quoting the entire op...
Give me some more evidence of this and I will edit the Root & Recovery Guide immediately... I have seen conflicting posts on this matter too... Also, is not clear if private mode does continue to work after rooting or not... Can anyone confirm... (without flashing any roms... from original unrooted to rooted) Private mode... does work or not??? (Private mode is not suppose to work after rooting... but some say it does work???)
Nice post! Come on people... help...
Before you back up your rom, disable fingerprint scanner and delete saved fingerprints. If you don't and you go do your backup and ever plan on using the scanner again on that backup, it won't work. One of the guys thinks it has to do with the fingerprints being encrypted so when you restore, it can't decrypt it and locks you out.
I can confirm personally that disabling it before you do your backup then flashing a new rom then restoring your old backup, the fingerprint scanner will still work. Just have to set it up again. But that is a whole lot easier then flashing stock with odin again and starting over.
inphamous36 said:
Before you back up your rom, disable fingerprint scanner and delete saved fingerprints. If you don't and you go do your backup and ever plan on using the scanner again on that backup, it won't work. One of the guys thinks it has to do with the fingerprints being encrypted so when you restore, it can't decrypt it and locks you out.
I can confirm personally that disabling it before you do your backup then flashing a new rom then restoring your old backup, the fingerprint scanner will still work. Just have to set it up again. But that is a whole lot easier then flashing stock with odin again and starting over.
Click to expand...
Click to collapse
I think this may be an additional problem for flashers, but not necessarily the same one I am addressing. The reason I say this is because I hadn't configured the scanner at all previous to when I discovered that mine didn't work, the error completely prevents me from opening the fingerprint manager. I couldn't even enable the fingerprint function to begin with. Does that make sense?
Not trying to argue just trying to make sure we are on the same page =)
Just noticed my fingerprint scanner isn't working. Wtf lol
Sent from my SM-N910T using Tapatalk
i notice this problem as soon as i flashed first rom the only way o get it working again is flashing back to stock odin but no matter what i do as soon as i flash a rom I get a error message ? here the post another member had the same problem
http://forum.xda-developers.com/note-4-tmobile/help/fingerprint-sensor-error-t2918069
inphamous36 said:
Before you back up your rom, disable fingerprint scanner and delete saved fingerprints. If you don't and you go do your backup and ever plan on using the scanner again on that backup, it won't work. One of the guys thinks it has to do with the fingerprints being encrypted so when you restore, it can't decrypt it and locks you out.
I can confirm personally that disabling it before you do your backup then flashing a new rom then restoring your old backup, the fingerprint scanner will still work. Just have to set it up again. But that is a whole lot easier then flashing stock with odin again and starting over.
Click to expand...
Click to collapse
Thats not entirely accurate.
I set up my stock rom with the FP scanner...backed up in twrp as usual and i have flashed 4 roms since then and had to set it up gain each time and never had a problem. Ive never disabled it once.
sent from Canada via my Note 4, 3, 2 or One X+
So what exactly must be done to preserve fingerprint scanner functionality before flashing a custom rom?
force70 said:
Thats not entirely accurate.
I set up my stock rom with the FP scanner...backed up in twrp as usual and i have flashed 4 roms since then and had to set it up gain each time and never had a problem. Ive never disabled it once.
sent from Canada via my Note 4, 3, 2 or One X+
Click to expand...
Click to collapse
Have you tried restoring a backup and using the scanner? That's when it breaks. I can flash roms fine without having to disable it, but it didn't work after I restored a rom that had it enabled. Locked out of it
JawjaBill said:
So what exactly must be done to preserve fingerprint scanner functionality before flashing a custom rom?
Click to expand...
Click to collapse
I can tell you my history. I setup the fingerprint scanner right away before flashing anything as it is a must have feature for me. Later, I flashed a couple different ROM's and never had an issue. Just had to setup the fingerprint again. So my guess is if you set it up before flashing any ROM, you should be good. At least I was. I haven't had to disable before flashing or anything like that.
COCODRILO45 said:
i notice this problem as soon as i flashed first rom the only way o get it working again is flashing back to stock odin but no matter what i do as soon as i flash a rom I get a error message ? here the post another member had the same problem
http://forum.xda-developers.com/note-4-tmobile/help/fingerprint-sensor-error-t2918069
Click to expand...
Click to collapse
force70 said:
Thats not entirely accurate.
I set up my stock rom with the FP scanner...backed up in twrp as usual and i have flashed 4 roms since then and had to set it up gain each time and never had a problem. Ive never disabled it once.
sent from Canada via my Note 4, 3, 2 or One X+
Click to expand...
Click to collapse
JawjaBill said:
So what exactly must be done to preserve fingerprint scanner functionality before flashing a custom rom?
Click to expand...
Click to collapse
inphamous36 said:
Have you tried restoring a backup and using the scanner? That's when it breaks. I can flash roms fine without having to disable it, but it didn't work after I restored a rom that had it enabled. Locked out of it
Click to expand...
Click to collapse
keitht said:
I can tell you my history. I setup the fingerprint scanner right away before flashing anything as it is a must have feature for me. Later, I flashed a couple different ROM's and never had an issue. Just had to setup the fingerprint again. So my guess is if you set it up before flashing any ROM, you should be good. At least I was. I haven't had to disable before flashing or anything like that.
Click to expand...
Click to collapse
And... We ALL agree that Private Mode is Not working...? Right... No Private Mode since rooting... Right? There is absolutely nobody with Private Mode still working after rooting...
TEKHD said:
And... We ALL agree that Private Mode is Not working...? Right... No Private Mode since rooting... Right? There is absolutely nobody with Private Mode still working after rooting...
Click to expand...
Click to collapse
I think once you root the KNOX counter gets tripped preventing private mode.
keitht said:
I think once you root the KNOX counter gets tripped preventing private mode.
Click to expand...
Click to collapse
Yeap I know... but there is this:
http://forum.xda-developers.com/galaxy-s5/development/mod-enable-private-mode-knox-0x1-t2904723
That almost nobody seems to know... It's actually possible to regain Private Mode after a tripped Knox... (Not impossible)
TEKHD said:
And... We ALL agree that Private Mode is Not working...? Right... No Private Mode since rooting... Right? There is absolutely nobody with Private Mode still working after rooting...
Click to expand...
Click to collapse
Well now....never tried it but just did and its working for me. Rooted, jovy23 deodexed stock, twrp.
The day i got my phone i odin'd update then installed twrp, then wiped everything but int & ext sdcard, rebooted to recovery, wiped again then flashed the deodexed stock rom.....just tested fingerprint unlock last night for the first time, no problems and just now tested private mode and again that works for me.
keitht said:
I think once you root the KNOX counter gets tripped preventing private mode.
Click to expand...
Click to collapse

GAPPS and device certification on GSI roms

So on every GSI rom I've tried (currently on phh-treble pie and it's working great btw), I can never get the device google play certified with opengapps. It works fine for a while, but after a few days I get the notification, and some apps become entirely unusable. Reading up about this, apparently it requires the device fingerprint from the build.prop from a stock rom in order to obtain certification (from this thread) - however I didn't back up this before wiping.
If I had to, I could reflash stock, get the fingerprint, and reflash again - but that takes a lot of time and effort. So I'm just wondering if someone could upload a stock build.prop for the P10 lite (hopefully WAS-LX1A) with the fingerprint (if the information it contains isn't too sensitive). Either that, or someone could let me know of an alternate method to get certification (or at least rid of the damn popups and app blocks).
Any help would be appreciated, thanks so much
jekblub said:
So on every GSI rom I've tried (currently on phh-treble pie and it's working great btw), I can never get the device google play certified with opengapps. It works fine for a while, but after a few days I get the notification, and some apps become entirely unusable. Reading up about this, apparently it requires the device fingerprint from the build.prop from a stock rom in order to obtain certification (from this thread) - however I didn't back up this before wiping.
If I had to, I could reflash stock, get the fingerprint, and reflash again - but that takes a lot of time and effort. So I'm just wondering if someone could upload a stock build.prop for the P10 lite (hopefully WAS-LX1A) with the fingerprint (if the information it contains isn't too sensitive). Either that, or someone could let me know of an alternate method to get certification (or at least rid of the damn popups and app blocks).
Any help would be appreciated, thanks so much
Click to expand...
Click to collapse
Here is a fingerprint that I took from my device a few months ago. It's for Was-LX1C432B368. I have never tested it though except for CypherOS which I only got to pass safety net after installing the universal safety net patch.
DeathBell said:
Here is a fingerprint that I took from my device a few months ago. It's for Was-LX1C432B368. I have never tested it though except for CypherOS which I only got to pass safety net after installing the universal safety net patch.
Click to expand...
Click to collapse
Thank you! Set it as fingerprint, but didn't immediately pass safetynet. Once I installed the universal fix it seemed to work, but also seems to break magisk! Well at least my device says it's certified now lol

Fingerprint Scanner Null after Pie ROM Flash - Custom ROM won't fix. Stock Only

Fingerprint Scanner Null after Pie ROM Flash - Custom ROM won't fix. Stock Only
Ok, the story.... Moto G5+ retail, running 8.1 Oreo, Bootloader Unlocked, rooted using Magisk 16.7 and was able to backup my Stock Oreo ROM once rooted, or I'd be dead in the water.
So wanting to stay ahead, I tried my hand at RR v7's Pie version, which, after some troubleshooting, was able to install successfully; but I don't much care for the google bar and other hard-coded "pure android" features. Same thing with Pixel Exp. Not to mention that Pie disallows call recording among a few other things Google decided to stifle its customers with. Deal breaker. So - moving on...or back for that matter.
I proceeded to download RRv6, which is btw running nicely on a 2nd G5+, same GApps, installs perfect except - FingerPrint Reader is not acknowledged. Period. No Security settings, No RR Config to access it, Nada. No matter what ROM I flash outside of the StockROM I backed up, it won't recognize the fp reader upon boot up. Whether I clear Dalvik/Cache, All DATA, do a full Wipe, DATA WIPE, REPAIR, FORMAT, nothing allows me to install RR v6.0 or any other flavor, Oreo or Pie, even while trying a dirty flash over Stock Oreo on this Moto G5+. Tried with several SD Cards, downloading fresh zip files from RR. I even went so far as to image the working G5+, then copy into the 2nd G5's SN folder, and do a restore, just loops - even after repairing the partition. I managed to work around that, Restored the image, but still no FP recognized by the initial Google startup/setup. It's almost as if the phone's been "firmwared" or "tagged".
Any ideas what could be lingering from Android Pie that would survive a F2FS/exT Format? Because something updated some kind of firmware on the phone during a Pie ROM flash, that now won't let me go back to anything below Pie, with a working fingerprint reader. The only difference between the G5 that works and this one is the working one has never seen Android 9. And it's staying that way til we come up with a way to hack the google crap.
Any help would be - awesome to say the least.
Thanks for looking.
Hello,
The issue with fingerprint is that after flashing stock Oreo ROM it replaces some files related to fingerprint sensor.
Hence all the newer custom ROM builds use the Oreo firmware related files. Hence it worked on the Pie ROM.
RR v6 would be still using the old nougat firmware hence you need to flash a file for it work. Which will replace the fingerprint related files for Nougat Stock firmware:
https://androidfilehost.com/?fid=1322778262904029634
In case you want to revert the changes and use Pie ROMs:
https://androidfilehost.com/?fid=1322778262904029635
sharan.nyn said:
Hello,
The issue with fingerprint is that after flashing stock Oreo ROM it replaces some files related to fingerprint sensor.
Hence all the newer custom ROM builds use the Oreo firmware related files. Hence it worked on the Pie ROM.
RR v6 would be still using the old nougat firmware hence you need to flash a file for it work. Which will replace the fingerprint related files for Nougat Stock firmware:
https://androidfilehost.com/?fid=1322778262904029634
In case you want to revert the changes and use Pie ROMs:
https://androidfilehost.com/?fid=1322778262904029635
Click to expand...
Click to collapse
That would make sense if PHONE1 manifested the same thing. But I went from StockOreo to RRv6-Oreo w/out losing anything and having to flash any FP Firmware. I used the RRv6 Official from 18-0911. Which is what's been leading me to believe there's something awry with this 2nd G5. I wonder is it possible PHONE2 has some slight firmware variance that is simply ignoring during the RR flash? Anyway, I'll give this a shot. this is TWRP flash, not fastboot, yes? Just being clear as I'm not proficient at this just yet.
Thanks Sharan!
DJScribe said:
That would make sense if PHONE1 manifested the same thing. But I went from StockOreo to RRv6-Oreo w/out losing anything and having to flash any FP Firmware. I used the RRv6 Official from 18-0911. Which is what's been leading me to believe there's something awry with this 2nd G5. I wonder is it possible PHONE2 has some slight firmware variance that is simply ignoring during the RR flash? Anyway, I'll give this a shot. this is TWRP flash, not fastboot, yes? Just being clear as I'm not proficient at this just yet.
Thanks Sharan!
Click to expand...
Click to collapse
Yeah, give it a try. And yes it's to be flashed via TWRP.
[SOLVED]
sharan.nyn said:
Yeah, give it a try. And yes it's to be flashed via TWRP.
Click to expand...
Click to collapse
Sweet! I had to reflash from scratch as for some reason it wouldn't let me update the ROM already running. But once I re-flashed RRv6-8.1, then flashed FP, it's now back. You rock Sharyn - nice work!
Now if only we found a way to cleanup that Pie - hate the perpetual time stamp, search bar and inability to record voice. Which is why I'm staying on Oreo til further notice. I know it was Google who took it away on v9.
Thanks again Shar!
:good::victory:
DJScribe said:
Sweet! I had to reflash from scratch as for some reason it wouldn't let me update the ROM already running. But once I re-flashed RRv6-8.1, then flashed FP, it's now back. You rock Sharyn - nice work!
Now if only we found a way to cleanup that Pie - hate the perpetual time stamp, search bar and inability to record voice. Which is why I'm staying on Oreo til further notice. I know it was Google who took it away on v9.
Thanks again Shar!
:good::victory:
Click to expand...
Click to collapse
Crap - so turns out this solution was short-lived. FingerPrint Scanner is back to inactive and FPzip isn't fixing it. Only StockOreo brings it back. Tried a plethora of ROMs from Nougat to Oreo, nothing but Pie and stock Oreo. Symptoms say it's the ROM, but a ROM that is currently working on the 1st G5 won't work either. Still looking for solutions, anyone...

September 2019 Security update for Mi A2 is now available

69.5MB in size so no major changes are to be expected...
Downloaded it just now...no major changes...no bugs encountered...
Weird noise while switching camera modes seems to have gone
Patched boot of last update ?
parkpark9999 said:
Patched boot of last update ?
Click to expand...
Click to collapse
Stock and patched (Magisk 19.3) images of /boot partition:
Note: I recommend to
- copy stock image to /downloads,
- patch it with Magisk (thus a copy of stock image will be saved in /data for further "Uninstallation of Magisk")
- copy patched image to PC (or take the one attached)
- boot patched image via fastboot
- make "Direct installation" in Magisk
This method will enable you to "Uninstall Magisk" by <Restore partitions> command when preparing to download next OTA
Darshan28 said:
Weird noise while switching camera modes seems to have gone
Click to expand...
Click to collapse
Yes i can confirm that.
Is seems THat WI-Fi Is more stable now also.
ki69 said:
Yes i can confirm that.
Is seems THat WI-Fi Is more stable now also.
Click to expand...
Click to collapse
No, the sound is still there but a lot quieter (tested with a sound meter )
WARNING: Caused my phone to get stuck in a bootloop during update.
I'm not rooted and haven't unlocked bootloader. Trying to find a solution.
Edit: after a bunch of tries and some time charging, it finally booted and displayed a "Couldn't update" error. I'm back to august patch with a working phone. I guess I'll wait for more people to report on this update.
A question: In case my phone gets stuck in a bootloop for good when updating, should leaving the "OEM Unlocking" option enabled be enough to save it and allow me to flash a fresh iso?
I mean, only leave the option enabled, but not actually unlocking the bootloader (I don't want to reset the phone unless necessary).
Wifi has indeed improved a lot! I have now connection to the WiFi with the September update where it did not even find the network with the August update. Big improvement here! It now shows the same behaviour as an Galaxy S7, which is really good with WiFi. Major thing... Thanks Xiaomi!
Edit: it looks like this was only accidentally. On other places WiFi is still far more worse than on other devices. Where other devices find multiple WiFi networks with decent speeds, the Mi A2 find no network at all. If it finds finally one, then the speeds are dramatic. I ditch the phone and I'll go for the S10.
JassyNL said:
Wifi has indeed improved a lot! I have now connection to the WiFi with the September update where it did not even find the network with the August update. Big improvement here! It now shows the same behaviour as an Galaxy S7, which is really good with WiFi. Major thing... Thanks Xiaomi!
Click to expand...
Click to collapse
I'm not sure but seems the range became reduced. Need to test again.
WiFi speeds seem to have increased, camera noise is gone for me. So far no complaints
danannnn said:
WARNING: Caused my phone to get stuck in a bootloop during update.
I'm not rooted and haven't unlocked bootloader. Trying to find a solution....
Click to expand...
Click to collapse
Used to happen with many previous OTA updates to many people. Why should this update be fully safe? That's why experienced stock MiA2 users recommend to keep bootloader and critical unlocked.
danannnn said:
Edit: after a bunch of tries and some time charging, it finally booted and displayed a "Couldn't update" error. I'm back to august patch with a working phone.
Click to expand...
Click to collapse
Good that this method worked for you.... usually works but needs great patience and dedication.
danannnn said:
A question: In case my phone gets stuck in a bootloop for good when updating, should leaving the "OEM Unlocking" option enabled be enough to save it and allow me to flash a fresh iso?
I mean, only leave the option enabled, but not actually unlocking the bootloader (I don't want to reset the phone unless necessary).
Click to expand...
Click to collapse
Yes, enough, but please consider following:
- now with working phone you can save most of your user data to PC (and to Google), then unlock and then restore data;
- when you will be forced to unlock phone in bootloop, you won't be able to save/restore user data
- after unlocking you will have ability to make TWRP backup of your /data partition
Audio is definitely louder.
Aerobatic said:
Stock and patched (Magisk 19.3) images of /boot partition:
Note: I recommend to
- copy stock image to /downloads,
- patch it with Magisk (thus a copy of stock image will be saved in /data for further "Uninstallation of Magisk")
- copy patched image to PC (or take the one attached)
- boot patched image via fastboot
- make "Direct installation" in Magisk
This method will enable you to "Uninstall Magisk" by <Restore partitions> command when preparing to download next OTA
Click to expand...
Click to collapse
Sorry for the question, i'm on 10.0.13.0, can i boot the 10.0.14.0 patched and update, because i uninstalled magisk and all of the modules and the update fails, says it couldn't update.
Anyone thinks that the screen takes quite a while to light up after the fingerprint is recognised?
tatitar said:
Sorry for the question, i'm on 10.0.13.0, can i boot the 10.0.14.0 patched and update, because i uninstalled magisk and all of the modules and the update fails, says it couldn't update.
Click to expand...
Click to collapse
To answer your question, no, you can't update by doing that.
It is highly probable that your system partition have been remounted rw (read/write). For Android to successfully update, it is important for any of the root apps to never remount system as rw.
To check if this is the cause, check Matlog (an app for logcat) after the error when performing the update. Filter "update engine" and check a message in regards to system mounting.
If this is correct, then, to be successful in updating to the September security level, you will need to flash the August's system partition from a fastboot package, and then try the update once again
---------- Post added at 04:28 AM ---------- Previous post was at 04:23 AM ----------
LeChevalierR said:
Anyone thinks that the screen takes quite a while to light up after the fingerprint is recognised?
Click to expand...
Click to collapse
I see that this have a chance to occur when a person updates to a newer patch level. This is based on the messages i have seen in this forum board though it is unknown if it really the cause.
I read that deleting your fingerprints and add them back as new "fixes" this issue. I recommend you to try it out first
Aerobatic said:
...
Click to expand...
Click to collapse
Thanks for the all the explanations.
I guess I'll just keep "OEM Unlocking" enabled for now if its enough to save me from disaster. I don't mind losing my phone data, I consider it transient anyway. I'm just too lazy to set it all up again unless I really need to.
After making sure OEM Unlocking was enabled, that I got fastboot all set up and working, etc., I went ahead and attempted to update again, this time with no issues.
New bug encountered? I was watching a video from YouTube I opened through a WhatsApp link and all of a sudden my back button was there but home and recent apps buttons disappeared and they didn't come back until I reset my phone!
My screen makes some weird noises when it register touch, like squeking or static noise behind the screen, it is hard to explain. It start to hear when touchscreen register touch and it last about 2-3 seconds, then it stop, and when i touch it again the sound is back and so on. It's very annoying
I can do confirm that the camera sound is gone, although I can still hear it if I concentrate enough. It might be what is used to sound before so I can't really tell.
WiFi is definitely improved and it now searches for available networks faster
Overall system speed is improved specially with those awkward keyboard lags in the previous update.
Also LTE Signal got better I can tell
.
.
But I do have a little doubt about the battery life cause my phone had about 14% of charge last night which I forgot to plug in the charger and it was dead in the morning which has never happened before. It usually had at least 5% when that happened before. Still am not sure if that's the real deal so I'm gonna just wait some more to see battery performance.
But the update itself seems stable and bugless enough so it's definitely recommended to install it especially if you're dealing with camera sound...
P.S. : No camera2API nor ARCore

Fingerprint Issue - Guide does not fix (lost after reboot)

Hi,
So I have had some trouble with the fingerprint scanner on my OnePlus 8 Pro. So I followed the persist.img fix guide but unfortunately the issue was not fixed. I assumed that this would mean the phone had no chance of regaining the use of fingerprint scanner. But I decided to reflash with msm as the guide requires and follow all the steps from the beginning again. Still no luck.
The third time, instead of replacing the data and engineermode (not replacing gf_persist.so) as the guide says, I just tried using the fingerprint scanner. It worked perfectly. I could enroll new fingerprints and even use them to unlock as usual. The issue is that this only lasts until the next shutdown/reboot. After that, I must redo the fingerprint test (and fail it) to regain use of fingerprint.
Can anybody recommend some sort of solution for this. I would like to be able to run lineage on here as I have on other phones in the past but I dont think i'm able to use the fingerprint test in the phone app as I can while running oxygen. Thanks for any help.
I have the same problem. Any solutions?
zioloiso said:
I have the same problem. Any solutions?
Click to expand...
Click to collapse
No, still nothing. Tried following again and again but still no luck.
kaxp said:
No, still nothing. Tried following again and again but still no luck.
Click to expand...
Click to collapse
Its another solution, do you have magisk?
I have the same and on top of that my other sensors seem messed up as well...banging my head against the wall
I have no clean persist backup ...
Can anyone please send me their persist.img if you have Oneplus 8 Pro European version?
I know it might give me problems with the fingerprint sensor but at least the others would work..
Did you ever get your fingerprint scanner working? I know it's a long shot u seeing this reply since it's old lol. But Im having same issue after msm and upgrading to OS 13..

Categories

Resources