Database Info

[Q] playstation app error 0x82E01003

Hi, I'm new and I don't know if this is the right place to make this question. I have a sony xperia z3 and I can't log in with my psn account into playstation app because I get the error 0x82E01003. I saw on the Internet that the reason could be the unlocked bootloader. I did that and I rooted my phone. Can you please tell me how to solve this problem? Thanks a lot

I had a similar error after rooting mine. The only way i found to make it work was by removing supersu app. I still have root, just can't control permissions.
I don't know if the unlocked bootloader will make a difference or not (mine is still locked).

BenTescort said:
I had a similar error after rooting mine. The only way i found to make it work was by removing supersu app. I still have root, just can't control permissions.
I don't know if the unlocked bootloader will make a difference or not (mine is still locked).
Click to expand...
Click to collapse
Thank you for your answer, I uninstalled super supersu, and the error is still there. I think that the reason could be the custom recovery or the unlocked bootloader. I'll wait for lollipop update to try solving this problem.

Unistall supersu by going into settings>reinstall
This is how it works for me but I only have root. If it's still not working then it must be the unlocked bootloaders fault. If you still want it to work then there's a modified remote play app on google that should work on any smartphone.
If i were you Id just restore my drm keys. There's not much to do atm with an unlocked bootloader.
Sent from my D6603 using XDA Free mobile app

Yes I'd like to restore my dorm keys. Can you tell me how can I do?

migly93 said:
Yes I'd like to restore my dorm keys. Can you tell me how can I do?
Click to expand...
Click to collapse
You restore the back up of them you took before unlocking the bootloader.
If you did not take a backup of them then they are lost forever.

Try removing the app and installing this one: http://forum.xda-developers.com/android/apps-games/ps4-remote-play-t2929147
That's what I did and it works great on my rooted device. Added bonus, this one skips the connection check so you can use it when not on WiFi (though, obviously it needs a fast connection like 4G).

3Shirts said:
Try removing the app and installing this one: http://forum.xda-developers.com/android/apps-games/ps4-remote-play-t2929147
That's what I did and it works great on my rooted device. Added bonus, this one skips the connection check so you can use it when not on WiFi (though, obviously it needs a fast connection like 4G).
Click to expand...
Click to collapse
Can you confirm if ds4 still works? I cannot get the ds4 working on my note 2. My z3 will be here tomorrow and I would like to run cm12 on it but only if I can fully use remote play with a ds4.

I've not tried it yet. I'll have a go when I get home and let you know.

Use version 0.6.1 its flawless works great for me

Frazer Scott said:
Can you confirm if ds4 still works? I cannot get the ds4 working on my note 2. My z3 will be here tomorrow and I would like to run cm12 on it but only if I can fully use remote play with a ds4.
Click to expand...
Click to collapse
Sorry for the delay, finally tried this and can confirm it works fine on rooted stock rom. Played some GTAV with it and it was gravy.

If you unlock boot loader you will need to use the current version. 0.6.1 is only if you have DRM keys still intact.

BenTescort said:
I had a similar error after rooting mine. The only way i found to make it work was by removing supersu app. I still have root, just can't control permissions.
I don't know if the unlocked bootloader will make a difference or not (mine is still locked).
Click to expand...
Click to collapse
The better way is to install xposed framework (just Google it, it really is quite easy) and install the rootcloak module. That way you can manage your root rights with supersu and hide root for the PlayStation app. (you really don't want root without a superuser app, malware really can take advantage of that)

crazymister said:
The better way is to install xposed framework (just Google it, it really is quite easy) and install the rootcloak module. That way you can manage your root rights with supersu and hide root for the PlayStation app. (you really don't want root without a superuser app, malware really can take advantage of that)
Click to expand...
Click to collapse
That was the first thing I tried. I have xposed framework and rootcloak installed but remote play wouldn't play ball.
Have you tried it and have you got it to work? Or anybody else for that matter?

I did , and it works. Just don't forget to activate the module and add remote play to the list (might even reboot before adding to the list to be safe)

Android Pay

Just wondering if anyone had any luck with the workarounds for our device? If so please post what ROM's work and which workaround worked. Also post whether the boot loader needed to be locked or not. I have been working since I found the official app last night, but So far no luck. I'm trying many custom ROMS as I don't really want another stock ROM, Hence why I am rooted. Anyway, any help would be boss! Thanks!

For me, it just has Google Play Services crashing whenever I try to add a card. This was after disabling SuperSU.

walkwithdeath said:
Just wondering if anyone had any luck with the workarounds for our device? If so please post what ROM's work and which workaround worked. Also post whether the boot loader needed to be locked or not. I have been working since I found the official app last night, but So far no luck. I'm trying many custom ROMS as I don't really want another stock ROM, Hence why I am rooted. Anyway, any help would be boss! Thanks!
Click to expand...
Click to collapse
did you try stock rooted thats my next attempt after I charge phone up a little. I been reading up and it seems stock rooted with supersu removing stock or xposed rootcloak work. Just nandroid and try it out nobody says you have to use it but if that works it may give us an insight on what to target for getting it to work

Yes, so far I believe thats what I read. At this point I have read a lot. The two methods involve unchecking enable superuser in supersu and then the root cloak method via xposed. Neither have worked in every custom ROM so far. I may try CM nightlies tho.

just an fyi i tried stock for the hell of it and it worked with just unchecking supersu root option. Maybe a buildprop edit to trick it to think its a basic stock rom may work

http://forum.xda-developers.com/oneplus-one/development/rom-cyanogen-os-12-1-rooted-cleaned-t3187016
Update. I have found a mothod that works, haven't tried the "pay" part, but I have Android Pay activated and working. The above link is the a rooted ROM with some mods that works. Its CM OS 12.1 and seems pretty stable, etc.
The method I used
1 Bootloader is locked. Just so you know. But all operations will function that you need.
1 Install ROM (use the link above for details, NO GAPPS NEEDED)
2 DENY ROOT/SUPERSU installation.
3 Boot ROM as normal
4 Open SuperSU
5 Click Enable SuperSU (This disables it/Unchecks the box. You will see a prompt saying uninstalling SuperSU)
6 Reboot
7 Install Google Play Services then Android Pay (APK's found on the web, GPS is 8.1.13)
8 Open Android Pay and follow prompts to install cards
9 Open SuperSU and recheck Enable SuperSU
At this point the phone is rooted and Android Pay is set up. I tried to do another card but got the same old error "cannot verify Android bs."
My conclusions:
If the ROM has a root option under developer settings, then Android Pay will not work. This ROM does NOT have that but instead has SuperSU installed. ROMS that have both will NOT function, I tried 3 or 4 today that did not work. I imagine they need to be CM based at this time as well. I bet someone better than me will come up with a better solution. This combination works for me. If anyone needs help, PM me. Also, If anyone has anything to add, Please do! Thanks!!!

walkwithdeath said:
http://forum.xda-developers.com/oneplus-one/development/rom-cyanogen-os-12-1-rooted-cleaned-t3187016
Update. I have found a mothod that works, haven't tried the "pay" part, but I have Android Pay activated and working. The above link is the a rooted ROM with some mods that works. Its CM OS 12.1 and seems pretty stable, etc.
The method I used
1 Bootloader is locked. Just so you know. But all operations will function that you need.
1 Install ROM (use the link above for details, NO GAPPS NEEDED)
2 DENY ROOT/SUPERSU installation.
3 Boot ROM as normal
4 Open SuperSU
5 Click Enable SuperSU (This disables it/Unchecks the box. You will see a prompt saying uninstalling SuperSU)
6 Reboot
7 Install Google Play Services then Android Pay (APK's found on the web, GPS is 8.1.13)
8 Open Android Pay and follow prompts to install cards
9 Open SuperSU and recheck Enable SuperSU
At this point the phone is rooted and Android Pay is set up. I tried to do another card but got the same old error "cannot verify Android bs."
My conclusions:
If the ROM has a root option under developer settings, then Android Pay will not work. This ROM does NOT have that but instead has SuperSU installed. ROMS that have both will NOT function, I tried 3 or 4 today that did not work. I imagine they need to be CM based at this time as well. I bet someone better than me will come up with a better solution. This combination works for me. If anyone needs help, PM me. Also, If anyone has anything to add, Please do! Thanks!!!
Click to expand...
Click to collapse
basicaly what I was saying it works on stock ONEPlus roms only it seems and you just have to deny root when adding cards. I tried to use lil while ago but it said my cards were not available yet to use with Android Pay

Just wanted to chime in with my post from another thread to consolidate threads:
I am running COS 12.1, rooted, with an unlocked bootloader. I recently upgraded to Android Pay after using Google Wallet for NFC payments for years on my old GS4 and my OnePlus One.
At first, I was unable to add my payment card due to being rooted. Easily fixed, I unrooted using SuperSU to do a full unroot and was able to add my card and complete the app setup.
The showstopper is that whenever I try to use it at a merchant, I end up with a screen that says Confirm your password - you must unlock to use Android Pay. No matter how many times I enter my password it just keeps asking over and over. I disabled the quick unlock feature under lock screen settings just in case that was the issue, but it made no difference. An ongoing support case with Google just came back with the following:
"The specific error message that you saw means that your device can't support Android Pay's advanced security. It seems that the phone manufacturer has modified the operating system to the point where it is no longer compatible with our software. You may want to use Android Pay on a different device for the most secure payments."

just as an update i re-flashed stock rom and realized using xposed and make any additional changes to the system folder causes it not to work whether I have supersu checked off or not. Now with that said i have it working fine with stock and having supersu loaded from twrp and play store nothing else. I also set up a tasker command to uncheck supersu prior to me using Android Pay. 1 click I guess I waas being lazy

Is your bootloader unlocked?
Sent from my Nexus 10 using XDA Premium 4 mobile app

playya said:
just an fyi i tried stock for the hell of it and it worked with just unchecking supersu root option. Maybe a buildprop edit to trick it to think its a basic stock rom may work
Click to expand...
Click to collapse
I have tried disabling root and root cloak. I am on Exodus rom and it has "morph mode" where I tried both methods in Exodus mode and AOSP mode. If this helps narrow down the problem.

For me on Exodus (haven't tried any of the morph modes), the unlocked bootloader seems to be the culprit. Hopefully someone figures out a workaround.

Hurricane Andrew said:
Is your bootloader unlocked?
Sent from my Nexus 10 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes... if you are asking me
---------- Post added at 02:29 PM ---------- Previous post was at 02:27 PM ----------
Digil said:
For me on Exodus (haven't tried any of the morph modes), the unlocked bootloader seems to be the culprit. Hopefully someone figures out a workaround.
Click to expand...
Click to collapse
bootloader is not the problem. Android Pay is looking for more than likely specific files in your system that are missing in AOSP or custom roms. I flashed stock and as long as I uncheck SuperSu its been working fine for me. I have added several cards over the past week

Deleted
---------- Post added at 10:57 PM ---------- Previous post was at 10:56 PM ----------
playya said:
yes... if you are asking me
---------- Post added at 02:29 PM ---------- Previous post was at 02:27 PM ----------
bootloader is not the problem. Android Pay is looking for more than likely specific files in your system that are missing in AOSP or custom roms. I flashed stock and as long as I uncheck SuperSu its been working fine for me. I have added several cards over the past week
Click to expand...
Click to collapse
What Rom are you Using ?!?

Hurricane Andrew said:
Is your bootloader unlocked?
Sent from my Nexus 10 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No need for a locked bootloader on 1+ it works fine but strictly with stock

Skitts said:
Deleted
---------- Post added at 10:57 PM ---------- Previous post was at 10:56 PM ----------
What Rom are you Using ?!?
Click to expand...
Click to collapse
I am running a stock rooted rom I found here. I tried to do it with Calkulins rom but it failed install for me. also no xposed or anything extra in system that may not need to be there. Its been working fine like this for a week now. I just used it again last night. I turn off SuperSu prior to using just for good measure

playya said:
I am running a stock rooted rom I found here. I tried to do it with Calkulins rom but it failed install for me. also no xposed or anything extra in system that may not need to be there. Its been working fine like this for a week now. I just used it again last night. I turn off SuperSu prior to using just for good measure
Click to expand...
Click to collapse
Thank Man I'll Give it A try see if I get the same results. As Of right now I'm Running Blisspop And I keep On getting the error.

Skitts said:
Thank Man I'll Give it A try see if I get the same results. As Of right now I'm Running Blisspop And I keep On getting the error.
Click to expand...
Click to collapse
So was I and I left them for crdroid which has a lot less issues. But I flashed stock to try out Android Pay and I have been surprisingly pleased. It will work just don't flash SuperSU but use built in version or update via TWRP option if asked after flashing rom

Does anyone have the apk for the version of Google Wallet right before the update to Android Pay? I'd like to at least have something that works.

rbrugman said:
Does anyone have the apk for the version of Google Wallet right before the update to Android Pay? I'd like to at least have something that works.
Click to expand...
Click to collapse
android authority has it and if you do a google search for it you will find it. also know that you have to un-tick auto updates in Google Play. I wiped data in Google play, Google Play Services prior to installing the now outdated version. I had to do this so that when I loaded the older version it will try and update the moment you try and set it up.

Rooting Pixel, any drawbacks or missing features since its still 'new/beta'

So I just finally received my phone and of course want to root it and switch over from my htc one m7.
are there any features of rooting that still are in the process of being worked out?
main concern does titanium backup work fully

kazemitsui said:
So I just finally received my phone and of course want to root it and switch over from my htc one m7.
are there any features of rooting that still are in the process of being worked out?
main concern does titanium backup work fully
Click to expand...
Click to collapse
Titanium Backup works fine. Any apps that use SafetyNet(Android Pay, Snapchat, etc) won't work once you unlock your bootloader/root.

Obaterista93 said:
Titanium Backup works fine. Any apps that use SafetyNet(Android Pay, Snapchat, etc) won't work once you unlock your bootloader/root.
Click to expand...
Click to collapse
is there a list of the most common SafetyNet apps? I use neither of the two you listed. I just know pkmn go doesnt work but any others or you have a link to the list?

kazemitsui said:
is there a list of the most common SafetyNet apps? I use neither of the two you listed. I just know pkmn go doesnt work but any others or you have a link to the list?
Click to expand...
Click to collapse
Snapchat, and most banking apps. Except simple and chase that I know of.

There are still tons of warnings of permanent bad things happening if you relock the bootloader without stock software installed. I know no details but I recommend you research that first before starting anything.

What if you just root to modify the hosts file, then into it and lock? Seems like that should be fine

I know one workaround for Snapchat used to be unlocking the bootloader, installing the app and logging in, then rooting. Any word on if that still applies? I'm using a 2014 Moto X still on Lollipop, so I'm afraid I'm a touch out of the loop.

NegativeOne said:
What if you just root to modify the hosts file, then into it and lock? Seems like that should be fine
Click to expand...
Click to collapse
Test and find out if you still get yellow warning at boot. If no warning... Maybe you won't be potentially bricked by red lockout if you lock.
If you you see yellow warning, certainly that is not fine.
Sent from my sailfish using XDA Labs

Apparently, as I've been informed, to lock the BL again, you will have to do a wipe, so no good.

Just flash a custom kernel, they bypass the bootloader unlock check for safetynet. Doesnt' help you with root though

Yeah, I might end up doing that. So SafetyNet detects systemless root now?

sovanyio said:
Just flash a custom kernel, they bypass the bootloader unlock check for safetynet. Doesnt' help you with root though
Click to expand...
Click to collapse
So either one of the 2 kernel's listed here will bypass the bootloader unlock check which will make Android Pay work?

JAYNO20 said:
So either one of the 2 kernel's listed here will bypass the bootloader unlock check which will make Android Pay work?
Click to expand...
Click to collapse
Yeah I'm running franco and have AP working
Edit: And snapchat, for that matter

sovanyio said:
Yeah I'm running franco and have AP working
Edit: And snapchat, for that matter
Click to expand...
Click to collapse
Any issues from using that kernel? I am hoping for stock or better than stock.

JAYNO20 said:
Any issues from using that kernel? I am hoping for stock or better than stock.
Click to expand...
Click to collapse
Nothing I've noticed so far

sovanyio said:
Nothing I've noticed so far
Click to expand...
Click to collapse
Awesome. I might give it a shot then.

Is there a way to get root without resetting the phone? I am told if you the supported BL unlock, it wipes you.

sovanyio said:
Yeah I'm running franco and have AP working
Edit: And snapchat, for that matter
Click to expand...
Click to collapse
Did you have to enable something to make AP work after loading that kernel? It isn't working for me.

JAYNO20 said:
Did you have to enable something to make AP work after loading that kernel? It isn't working for me.
Click to expand...
Click to collapse
No.. are you running at least r2? I didn't root or anything that will still trip safetynet

sovanyio said:
No.. are you running at least r2? I didn't root or anything that will still trip safetynet
Click to expand...
Click to collapse
Oh I didn't know that. I did root. Any way to hide that too?

Google pay error

Running stock ROM not rooted, getting this error? .. bootloader is unlocked though

Google has Google pay check for an unlocked bootloader. If you are unlocked it will fail, you do not have to be rooted just bootloader unlocked for Safteynet to fail. You might as well install Magisk and let it hide that you are unlocked and rooted if you wish to use Google Pay. If you do not want to root, then just relock the bootloader, JUST MAKE SURE YOU HAVE THE STOCK RECOVERY AND NO CUSTOM RECOVERY INSTALLED. Otherwise you will brick your device. Also, be aware that relocking your bootloader will wipe all internal data off the phone so backup any photos, files, anything of importance before relocking bootloader.

Eric214 said:
Google has Google pay check for an unlocked bootloader. If you are unlocked it will fail, you do not have to be rooted just bootloader unlocked for Safteynet to fail. You might as well install Magisk and let it hide that you are unlocked and rooted if you wish to use Google Pay. If you do not want to root, then just relock the bootloader, JUST MAKE SURE YOU HAVE THE STOCK RECOVERY AND NO CUSTOM RECOVERY INSTALLED. Otherwise you will brick your device. Also, be aware that relocking your bootloader will wipe all internal data off the phone so backup any photos, files, anything of importance before relocking bootloader.
Click to expand...
Click to collapse
Magisk hide won't hide it. Alot of apps not able to avail of the hide function.

hallo dare said:
Magisk hide won't hide it. Alot of apps not able to avail of the hide function.
Click to expand...
Click to collapse
Strange... on my OP 6 with unlocked bootloader and Magisk root, Google Pay runs fine. And even Magisk Hide was not enabled for Google Pay (now it is).

hallo dare said:
Magisk hide won't hide it. Alot of apps not able to avail of the hide function.
Click to expand...
Click to collapse
What are you talking about? I've been using Magisk with passing safetynet since it came out a couple years ago. I just used Google Pay times today with no issues.
The issue is Google will fail Safetynet if you just have an unlocked bootloader and no magisk installed to pass the safetynet checks.

Eric214 said:
What are you talking about? I've been using Magisk with passing safetynet since it came out a couple years ago. I just used Google Pay times today with no issues.
The issue is Google will fail Safetynet if you just have an unlocked bootloader and no magisk installed to pass the safetynet checks.
Click to expand...
Click to collapse
What I'm talking about is what I'm experiencing. I've magisk installed, Google Pay is ticket to magisk hide, along with other apps, and they all detect root

hallo dare said:
Magisk hide won't hide it. Alot of apps not able to avail of the hide function.
Click to expand...
Click to collapse
please dont give users the wrong impression
Magisk DOES hide it.
i have an unlocked bootloader, TWRP, MAGISK, and a custom kernel installed
and ive been using google pay for the past week without issues.

Why would I give users wrong impression? It's happening to me!!! Just because it doesn't happen to you or others then it cannot be true?
I've also an unlocked bootloader, TWRP and Magisk installed and Magisk is not hiding specific apps. Simple as that.

hallo dare said:
What I'm talking about is what I'm experiencing. I've magisk installed, Google Pay is ticket to magisk hide, along with other apps, and they all detect root
Click to expand...
Click to collapse
Then Magisk must not be installed properly. You must have done something wrong is all I can think of. I use Google pay 2-5 times a day without issue and on the OnePlus 6 since launch, zero issues.

Eric214 said:
Then Magisk must not be installed properly. You must have done something wrong is all I can think of. I use Google pay 2-5 times a day without issue and on the OnePlus 6 since launch, zero issues.
Click to expand...
Click to collapse
I've gone and done a complete format and re-installation of everything and the same issue is present.

hallo dare said:
I've gone and done a complete format and re-installation of everything and the same issue is present.
Click to expand...
Click to collapse
Maybe delete the Magisk APK/zip you have and download a fresh copy then.

Eric214 said:
Maybe delete the Magisk APK/zip you have and download a fresh copy then.
Click to expand...
Click to collapse
Done that, but made no difference. Just reading on another thread that it appears to be an issue for many.

Magisk Hide works fine out of the box (no alterations) with Google Pay for me.
Historically, when it fails it's because Magisk is out of date.
hallo dare, if you want help, post your Magisk Manager's landing page, then another of your test results. Past that, you should head over to the Magisk XDA thread.
Edit:
I guess I forgot to mention I am on the BETA channel - so not exactly without alteration.

Orito said:
Magisk Hide works fine out of the box (no alterations) with Google Pay for me.
Historically, when it fails it's because Magisk is out of date.
hallo dare, if you want help, post your Magisk Manager's landing page, then another of your test results. Past that, you should head over to the Magisk XDA thread.
Edit:
I guess I forgot to mention I am on the BETA channel - so not exactly without alteration.
Click to expand...
Click to collapse
Thanks Orito,
Yeah I'll do just that. Can you please post the magisk you flashed and I'll try it please.
I flashed the 16.4.

I'm running 16.42. In Magisk.
Open Magisk Manager.
Menu.
Settings.
Update Channel -> Beta
Check for Updates -> Enabled
Close Magisk Manager completely.
Reopen.

Orito said:
I'm running 16.42. In Magisk.
Open Magisk Manager.
Menu.
Settings.
Update Channel -> Beta
Check for Updates -> Enabled
Close Magisk Manager completely.
Reopen.
Click to expand...
Click to collapse
Exactly what I've been doing. Thanks

General Latest ROW march update for TB-J706F solved my Netflix Widevine L1 problem.

Only to inform that after updating the row rom with march update, my problem with Netflix not working with widevine L1 was solved.
Before the update I had to install an old Netflix version (7.8) in order to work in full hd.

Great news!
thank you

Good news! May try my luck flashing this on my Chinese J706F in the near term.

blagoon52 said:
Only to inform that after updating the row rom with march update, my problem with Netflix not working with widevine L1 was solved.
Click to expand...
Click to collapse
Full HD is not working anymore in any version and this OTA (220312) does not contain any fix for Netflix, according to Lenovo technicians.
You are only seeing L1 and it's the same I can see with my tablet not updated but if you try to play test patterns you will see that definition played is 960x540.
We need to wait for the next OTA for a fix.
Is there still the "join Lenovo experience program" notification everytime tablet is restarted with this OTA?

I'm on TB-J706F_S210002_201015_ROW with bootloader unlocked + rooted, when trying to update to last OTA it just says "ota package installation failed", any solution?

MrCrayon said:
Full HD is not working anymore in any version and this OTA (220312) does not contain any fix for Netflix, according to Lenovo technicians.
You are only seeing L1 and it's the same I can see with my tablet not updated but if you try to play test patterns you will see that definition played is 960x540.
We need to wait for the next OTA for a fix.
Is there still the "join Lenovo experience program" notification everytime tablet is restarted with this OTA?
Click to expand...
Click to collapse
It is not showing since I made de update, but it comes with a new app called Tablet Center.

A bit off topic but I'd suggest everyone concerned with privacy to install NetGuard
It works kind of like a firewall without having root using a local VPN.
I am using it with whitelist so only apps and services I choose can access internet.
Not as powerful as AFWall+ but best alternative without root.

melones22 said:
I'm on TB-J706F_S210002_201015_ROW with bootloader unlocked + rooted, when trying to update to last OTA it just says "ota package installation failed", any solution?
Click to expand...
Click to collapse
OTA updates are not going to work if the system is modified, sometimes just unlocking bootloader will stop them I am not sure what's the case for this tablet.
I think the quicker way for you to update is to download the full ROM, make a backup of apps and data with something like Migrate, flash new ROM, restore apps.

MrCrayon said:
OTA updates are not going to work if the system is modified, sometimes just unlocking bootloader will stop them I am not sure what's the case for this tablet.
I think the quicker way for you to update is to download the full ROM, make a backup of apps and data with something like Migrate, flash new ROM, restore apps.
Click to expand...
Click to collapse
too bad, would have been great to avoid reflashing the rom again.
So from what I've understood no widevine L1 even with latest update?

melones22 said:
So from what I've understood no widevine L1 even with latest update?
Click to expand...
Click to collapse
With bootloader unlocked no.
With bootloader locked Widevine is L1 but the problem with Netflix not playing Full hd it's not solved yet.
They are testing the fix and OTA update should have been released end of March but has been delayed.

MrCrayon said:
With bootloader unlocked no.
With bootloader locked Widevine is L1 but the problem with Netflix not playing Full hd it's not solved yet.
They are testing the fix and OTA update should have been released end of March but has been delayed.
Click to expand...
Click to collapse
so widevine L1 but useless in a nutshell :/
is it possible to patch boot.img to get root and then lock the bootloader again? (might sound like a stupid question but it's been years since I hadn't get my hands on an android device)

melones22 said:
is it possible to patch boot.img to get root and then lock the bootloader again? (might sound like a stupid question but it's been years since I hadn't get my hands on an android device)
Click to expand...
Click to collapse
Nope, bootloader locked is a guarantee that nothing has been changed so it wouldn't make much sense.
I always unlock and root my phones but for this tablet I am still holding, what do you need root for?
NetGuard works sufficiently well as a Firewall but sure backups suck without root.

MrCrayon said:
Nope, bootloader locked is a guarantee that nothing has been changed so it wouldn't make much sense.
I always unlock and root my phones but for this tablet I am still holding, what do you need root for?
NetGuard works sufficiently well as a Firewall but sure backups suck without root.
Click to expand...
Click to collapse
I see!
My phone is an iphone jailbroken, so it would be sad if I would not be able to mess with android too adblocking is one of many examples ! hadn’t checked what magisk permits but I assume it’s similar to Cydia in a way

Ad blocking works with NetGuard, but if you want to have fun messing around (I totally understand the feeling) I would suggest to:
Unroot and lock bootloader again
Make a full backup with QFIL or edl
Unlock again and install a GSI rom
Have fun

BTW I never had an iphone but for what I remember Cydia just let you install software that is not in the app store, you can do that with Android without any effort.
Magisk is totally another level of personalization at system level.

Well Cydia is like Magisk then, you can customize whatever you want, like adding live weather particles on your homescreen, replace the phone app ui, put a cool live equalizer effect when a music plays on your lockscreen/homescreen/control center... anything!

if anyone needs a guide to get bootloader+twrp+root without having a headache (i haven't been able to found latest update rom file online so I dumped boot.rom myself) :
0. Dowload , unzip and rename img file to twrp.img https://www.mediafire.com/file/wdpxfr5t2z4mrye/TWRP-3.4.2B-1208-LENOVO_TBJ706F.zip/file
1. Enable OEM unlock in developers settings
2. Reboot in bootloader (adb reboot bootloader)
3. In bootloader enter :
Code:
fastboot flashing unlock
and answer yes when you're ready
WARNING: UNLOCK BOOTLOADER WILL WIPE YOUR DEVICE!!!!!
4. Run LMSA/RSA rescue to update your ROM as well as grab boot to patch
5. Do initial setup. DO NOT RESTORE
6. Install Magisk
7. Enter fastboot and enter :
Code:
fastboot flash recovery twrp.img
8. Reboot to TWRP (Vol up + Vol down + Power)
9. Get in shell (adb shell) and enter dd if="/dev/block/bootdevice/by-name/boot_b" of="/sdcard/boot.img"
12. Reboot and open Magisk, hit Install and select your boot.img freshly dumped
13. Transfer patched img to your pc and rename it to patched_boot.img
14. Go back to fastboot, enter :
Code:
fastboot flash boot patched_boot.img
15. Reboot and add riru and safety net fix on Magisk (you have to reboot 2-3 times)
16. Run safety net check and it should pass. If not, enable Magisk Hide and try again
17. Wipe Play Store and Google Play Services and reboot
18. Restore and add app onto hide list if the app detected root
Troubleshoot :
- TWRP will ask for a password if your device has pin/pattern to unlock, disable it to get access to user data
- wtf why my touch screen is glitched after going to TWRP? idk it's odd but just reboot and it'll be fixed
- Play store not installing apps? Format your SD card to external storage
- Can't install Netflix and other apps claiming to be uncompatible ? add play store in magisk hide then clear play store & google play services cache/data
(modified guide from https://forum.xda-developers.com/t/...-if-running-android-11.4374645/#post-86108685)

Great, I was looking for a guide like this for rooting since I may do it later on with my p11 pro, thanks!

frogduck said:
Great, I was looking for a guide like this for rooting since I may do it later on with my p11 pro, thanks!
Click to expand...
Click to collapse
no problem! it took me a lot of time to figure out everything since it's the first time i'm using adb and stuff, but i'm so happy with the final result :d

I saw this tutorial on 4pda to return Widevine from L3 to L1, i didnt tried yet.
https://4pda.to/forum/index.php?showtopic=1018820&st=1000#entry113135411 (use google translate)