I sent my oneplus 5 to get the drm level 1 to be able to stream hd in Netflix . After I got it back I unlocked the bootloader and rooted. The cell was working fine for a few months but now netflix won't open. I get network error 9. I open the logs and it says general drm error. The interesting part is that if I lock the bootloader netflix works fine and the videos are in hd. As soon as I unlock the bootloader and root the device with magisk it stops working. Magisk hide is working properly cause I can download Netflix directly from playstore but the app won't work. I am gonna attached a pic of the logs. Can someone please help? Thanks!
This is part of the log
Hello,
I am also facing the same problem. I also have unlocked bootloader, magisk and xposed installed. I have got DRM level 1 activated on my device.
Pls someone suggest any solution other then unrooting and removing xposed .
deepak549 said:
Hello,
I am also facing the same problem. I also have unlocked bootloader, magisk and xposed installed. I have got DRM level 1 activated on my device.
Pls someone suggest any solution other then unrooting and removing xposed .
Click to expand...
Click to collapse
In my case I don't have xposed. I own another oneplus 5 that works fine with unlocked bootloader and the one with the issue was working fine before. I have no idea what happened.
xestan said:
In my case I don't have xposed. I own another oneplus 5 that works fine with unlocked bootloader and the one with the issue was working fine before. I have no idea what happened.
Click to expand...
Click to collapse
I also had the same problem. I got L1 on my 5T, worked fine for some time but stopped. The will work if you use the magisk module that makes the app thinks the phone is L3 and it will work, or you could use 4.x version of the app and it will work. But with any of those solutions netflix won't play in HD.
I heard that netflix is checking is bootloader is unlocked for L1 and blocking it.
harpin14789 said:
I also had the same problem. I got L1 on my 5T, worked fine for some time but stopped. The will work if you use the magisk module that makes the app thinks the phone is L3 and it will work, or you could use 4.x version of the app and it will work. But with any of those solutions netflix won't play in HD.
I heard that netflix is checking is bootloader is unlocked for L1 and blocking it.
Click to expand...
Click to collapse
If netflix is doing that, is not doing it accross all devices or something cause my other oneplus 5 works perfectly. The workaround I found is install the 4.x version and then after opening that version go and update to the latest one, but as you said it will not be in HD.
Related
I unlocked my bootloader and relocked it with flashtool. Now I can only take photos on the camera app (same results with 3rd party apps). Any kind of video recording lags extremely or just gives me a blank screen and the fingerprint scanner doesn't respond. Like it's turned off. Any ideas how to fix this? I'm using the z5 premium e6853.
Thanks.
Mike3009 said:
I unlocked my bootloader and relocked it with flashtool. Now I can only take photos on the camera app (same results with 3rd party apps). Any kind of video recording lags extremely or just gives me a blank screen and the fingerprint scanner doesn't respond. Like it's turned off. Any ideas how to fix this? I'm using the z5 premium e6853.
Thanks.
Click to expand...
Click to collapse
How did you relock bootloader? with TA backup?
Try to use patched kernel.
Thanks for the reply. I actually just was about to report back that I fixed the issue. I flashed over the drm workaround with twrp.
I found it here:
https://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672
Happy to say everything is working perfectly now.
Will this work for 7 nougat on a z5?
I'm not sure. I flashed back to marshmallow to get it working. Then upgraded to the latest official firmware after.
i have even flashed back to marshmallow and still fingerprint is not working - has all the apk but doesnt look like its activating @Mike3009 are you able to give me the steps you used - i have tried numerous different processes
smiley.raver said:
i have even flashed back to marshmallow and still fingerprint is not working - has all the apk but doesnt look like its activating @Mike3009 are you able to give me the steps you used - i have tried numerous different processes
Click to expand...
Click to collapse
I'm pretty new to all of this so I'm not sure if this is the most efficient way to do it but here's what I did.
first I downloaded the official marshmallow firmware from xperiafirm and flashed it over with the latest version of flashtool. If you're bootloader isn't already unlocked, you should unlock it in flashtool. (needs to stay unlocked after too for this to work. I tried relocking it after and lost functionality) after you've flashed it over you need to get a modified kernel for your phone and firmware version. Flash that over and install the latest twrp. After that install the drm fix. Test if everything is working and if it is, download the latest official firmware from xperiafirm and flash over with flashtool.
Mike3009 said:
I'm pretty new to all of this so I'm not sure if this is the most efficient way to do it but here's what I did.
first I downloaded the official marshmallow firmware from xperiafirm and flashed it over with the latest version of flashtool. If you're bootloader isn't already unlocked, you should unlock it in flashtool. (needs to stay unlocked after too for this to work. I tried relocking it after and lost functionality) after you've flashed it over you need to get a modified kernel for your phone and firmware version. Flash that over and install the latest twrp. After that install the drm fix. Test if everything is working and if it is, download the latest official firmware from xperiafirm and flash over with flashtool.
Click to expand...
Click to collapse
Tried all that lol aw well I'm due for a new phone in a few months. I know mine isnt hardware related, but just something missing. Do you remember with MM firmware you got?
smiley.raver said:
Tried all that lol aw well I'm due for a new phone in a few months. I know mine isnt hardware related, but just something missing. Do you remember with MM firmware you got?
Click to expand...
Click to collapse
Try this drm fix. http://www.theandroidsoul.com/restore-drm-xperia-z5/
As for my marshmallow firmware, I'm in Taiwan so I used the only one listed on xperiafirm for Taiwan. Sorry I'm not able to use a Pc now to confirm.
are you on android 7.1.1?
Oops double post...sorry. Look below.
Yes. I didn't know to back up my drm keys before unlocking my bootloader and thought I was screwed. Now I'm on the latest 7.1.1, all drm functions working and I have root access. This drm fix works perfectly on the z5 premium e6853.(other models too but I can't personally verify)
Hello Forum People,
I have my bootloader unlocked, build MHA-L29C432B198, TWRP recovery and I use Magisk v14.5 however I cannot seem to pass SafetyNet with Magisk failing on ctsProfile and basicIntegrity and "SafetyNet Test" (from the Play Store) passing Safety Net Request but failing Response Signature Validation ("Response Payload Validation Failed").
I have a suspicion that this is due to the unlocked bootloader as I have removed Magisk and anything else I think might have tripped SafetyNet but always the same issue.
Can anyone confirm if this is the cause or otherwise and if having my bootloader unlocked is 'causing SafetyNet to fail then is it safe to relock after re-installing Magisk and returning recovery back to stock or is there some kind of work around?
Muchos appreciated in advance!!
It works fine with unlocked bootloader. Check in Playstore - hamburger menu - scroll down - Settings - scroll down - Device certification: can be certified or uncertified.
It's usually uncertified if your firmware is not approved yet by Huawei. And that would make safetynet fail.
What modules are you using? Xposed will also make safetynet fail.
You could try installing the propfix for magisk, found here: https://mega.nz/#!IOAgibSQ!uix7Gku_MY0ETP-zTae03awF_uH_Jgatr1SDEEvw77A
And did you happen to have SuperSU installed prior to Magisk?
ante0 said:
It works fine with unlocked bootloader. Check in Playstore - hamburger menu - scroll down - Settings - scroll down - Device certification: can be certified or uncertified.
It's usually uncertified if your firmware is not approved yet by Huawei. And that would make safetynet fail.
What modules are you using? Xposed will also make safetynet fail.
You could try installing the propfix for magisk, found here: https://mega.nz/#!IOAgibSQ!uix7Gku_MY0ETP-zTae03awF_uH_Jgatr1SDEEvw77A
And did you happen to have SuperSU installed prior to Magisk?
Click to expand...
Click to collapse
I have tried the propfix and that was unsuccessful in my case. Looks like it's because the firmware is uncertified which is confusing since I updated OTA by official means; update manager gave me a notification, I updated.
Is this a likely scenario that it could be uncertified even though they issued the update?
beejkitsune said:
I have tried the propfix and that was unsuccessful in my case. Looks like it's because the firmware is uncertified which is confusing since I updated OTA by official means; update manager gave me a notification, I updated.
Is this a likely scenario that it could be uncertified even though they issued the update?
Click to expand...
Click to collapse
So according to HiSuite I have an official ROM, I have performed a full factory reset and I am still getting uncertified status through Play Store. I cannot understand this as previously everything was working fine, I could use my banking app etc. and then one day everything stopped working and the only thing I can trace it to is this uncertified status.
Can anyone help me at all because short of going to extremes of using FH to rebrand etc I am all out of ideas and not being able to pass SafetyNet is really annoying; I can no longer use my banking app or Android Pay.
beejkitsune said:
So according to HiSuite I have an official ROM, I have performed a full factory reset and I am still getting uncertified status through Play Store. I cannot understand this as previously everything was working fine, I could use my banking app etc. and then one day everything stopped working and the only thing I can trace it to is this uncertified status.
Can anyone help me at all because short of going to extremes of using FH to rebrand etc I am all out of ideas and not being able to pass SafetyNet is really annoying; I can no longer use my banking app or Android Pay.
Click to expand...
Click to collapse
This is infuriating. I cannot seem to fathom why my device would suddenly be unverified.
I have considered locking my bootloader again but with attempts to do that I am given re-locked status. Suggestions, anyone, please?
Sent from my Mate 9 using XDA Labs
beejkitsune said:
This is infuriating. I cannot seem to fathom why my device would suddenly be unverified.
I have considered locking my bootloader again but with attempts to do that I am given re-locked status. Suggestions, anyone, please?
Sent from my Mate 9 using XDA Labs
Click to expand...
Click to collapse
I know my comment comes a little late, but just so you know,
I'm not certified (according to Google play store), and yet I pass SafetyNet. So your problem doesn't seem to be related.
I'm on B197 and Safety Net 14.3, and B197 was also officially pushed to my phone by Huawei.
Surfinette said:
I know my comment comes a little late, but just so you know,
I'm not certified (according to Google play store), and yet I pass SafetyNet. So your problem doesn't seem to be related.
I'm on B197 and Safety Net 14.3, and B197 was also officially pushed to my phone by Huawei.
Click to expand...
Click to collapse
Thanks for the reply. My solution ended up being to. Rebrand and then update to the Oreo release MHA-L29C432 8.0.0.361. Play Store now certified and passing SafetyNet with no issues. I'm still not 100% sure what tripped SafetyNet originally, nothing seems to be consistent with other people's experiences but I have now a resolution albeit not the desired approach, nor solution.
guys, here netflix is showing L3 widevine and with that it supports maximum SD. The device shows L1 in DRM INFO. someone else experiencing the same problem?
Im using last Android 10 January security patch. Bootloader Locked, No Root... ALL STOCK.
That's how it is. Netflix doesn't only require L1, but it also only let's the devices they whitelist to stream HD. Your device is L1 and netflix app is lying about it.
Everything works perfect in the Disney+ app. You'll get beautiful HD and it's clearly using the DRM.
hawkdown77 said:
guys, here netflix is showing L3 widevine and with that it supports maximum SD. The device shows L1 in DRM INFO. someone else experiencing the same problem?
Im using last Android 10 January security patch. Bootloader Locked, No Root... ALL STOCK.
Click to expand...
Click to collapse
So, good news. I recently installed the a11 update and netflix is now working in HD.
(I updated with the "Rescue and Smart Assistant" tool from lenovo for motorola phones, it offered the 11 update as a rescue image. It wipes the phone but atleast i got it in europe before the schedule)
- it was strange thought that play store didn't want to install netflix or disney+, i had to sideload them from apkmirror.
I have a (non-essential) app that I can not make to work on my new phone with the following error message:
Integrity check failed
Modifications on your phone have been detected. The app can not be used due to security reasons.
Details: The device is checked for signs of root access, respectively if the bootloader is unlocked. For these checks only local elements are used, no data is submitted to external services.
Click to expand...
Click to collapse
This is on a POCO X3 NFC with unlocked bootloader, custom ROM (ArrowOS 11) with microG (instead of Google Play Services) and stable Magisk (v22.0) with MagiskHide applied to that app. I have also already tried to freeze Magisk with AirFrozen, which is a trick that works on a problematic banking app, but that did not change anything.
The strange thing is, that the same app (and same app version) does not show that error on a OnePlus 6 with unlocked bootloader, custom ROM (LineageOS 16 for microG) and Magisk with MagiskHide applied to that app.
I have no idea what the difference may be any and how this is possible.
Any ideas?
https://github.com/kdrag0n/safetynet-fix check and download from release section if you want
etahamad said:
https://github.com/kdrag0n/safetynet-fix check and download from release section if you want
Click to expand...
Click to collapse
If you are replying to me, it's definitely not a SafetyNet issue, because my devices haven't passed SafetyNet since it stopped working with microG about a year (?) ago.
Is anyone else having this issue. Started yesterday for me after years of being rooted without fail. Is there a Google Services update that now runs root check for fingerprint login?
Same here did you get it to work?
Same on my OP 8 pro, Magisk hide, reboot and reinstalling etc didn't work either
Ok, I thought I was going crazy, I have the same problem since last couple of updates... Anybody figured out how to fix it? Maybe an older version of chase mobile?
The new chase app update fix the fingerprint started to work again i got root with magisk and edxposed instaled.try to update the app
Doesn't work for me with app version 4.262 (updated December 15, 2021).
Moto G7 Play (channel), LineageOS 18.1 20211226-NIGHTLY, Magisk v23.0.
As far as I can tell, fingerprint login is the only thing that doesn't work. edit: Quick view balances also does not work.
Just for comparison, everything works with the Bank of America app, including fingerprint login.
I had fingerprint working with root by installing older version and then updating but now I can't get it to work anymore.
Can anyone confirm whether the fingerprint works without root (but with bootloader unlocked and custom ROM installed)?
I'm seeing this issue still in Feb 2022. Rest of app works. Funny how whatever it detects isn't reason enough to block access, just block fingerprint.
supeRUUser said:
Can anyone confirm whether the fingerprint works without root (but with bootloader unlocked and custom ROM installed)?
Click to expand...
Click to collapse
Yes. I just reset my device and reinstalled LineageOS. The fingerprint worked. I then flashed Magisk (and enabled Hide for the Chase app), and the fingerprint continues to work. It seems you just need to set it up *before* rooting.