Hey guys,
when I got the P3XL I unlocked the bootloadeer immediately. Widevine level was still on L1 even though I've installed a custom rom. Then I had to try something, flashed another rom and also flashed the latest factory image and it was changed to L3.
Now even after flashing the factory image and completely locked the bootloader, it still says L3...So in amazon prime and netflix only HDR/UHD works... but not HD for shows and movies which are not netflix/amazon originals.
Did someone had the same issue? If yes is there a fix to it or maybe Google is aware of it already? Some people reported that after a while their Widevine level changed to L3 with custom rom/custom kernel, but it should be back to L1 with completely locked bootloader and full stock rom. It does that way for all other phones (htc U12+, essential PH-1 and many many others)
Is there something in the Pixel which is similar to Samsung's Knox? ... I'm just so disappointed and angry...
I also catched a log, where it says cannot open file /vendor/firmware_mnt/imagine/widevine.mdt. this file is missing in that folder and the Essential PH-1 even with unlocked bootloader, rooted/custom rom has it still there and the phone is also in L1... so google did something, what deleted that file....
DeeZZ_NuuZZ said:
Hey guys,
when I got the P3XL I unlocked the bootloadeer immediately. Widevine level was still on L1 even though I've installed a custom rom. Then I had to try something, flashed another rom and also flashed the latest factory image and it was changed to L3.
Now even after flashing the factory image and completely locked the bootloader, it still says L3...So in amazon prime and netflix only HDR/UHD works... but not HD for shows and movies which are not netflix/amazon originals.
Did someone had the same issue? If yes is there a fix to it or maybe Google is aware of it already? Some people reported that after a while their Widevine level changed to L3 with custom rom/custom kernel, but it should be back to L1 with completely locked bootloader and full stock rom. It does that way for all other phones (htc U12+, essential PH-1 and many many others)
Is there something in the Pixel which is similar to Samsung's Knox? ... I'm just so disappointed and angry...
Click to expand...
Click to collapse
No there is no security measure which trips Pixel 3 as far i am aware of nor is mine tripped.
flashed a lot of custom roms flashed march & april factory images with -w and without -w and i am on custom rom now, bootloader still unlocked, rooted, custom kernel and it's still widevine security is L1.
While doing a search I see that you already posted the issue with Google support lets see if they can say else that unlocking bootloader is the reason.
SacredDeviL666 said:
No there is no security measure which trips Pixel 3 as far i am aware of nor is mine tripped.
flashed a lot of custom roms flashed march & april factory images with -w and without -w and i am on custom rom now, bootloader still unlocked, rooted, custom kernel and it's still widevine security is L1.
While doing a search I see that you already posted the issue with Google support lets see if they can say else that unlocking bootloader is the reason.
Click to expand...
Click to collapse
Yes that is the strange thing, L1 worked fine when I was on aquarios first.
Then tried DU and had to reflash factory image and L1 wasn't working anymore.
I was told by google supported to also issue that to widevine, sent them some logs too. Let's see who can help.
There must be something wrong, because @Freak07 also tried the widevine.mdt file from another pixel 3, but it didn't worked either. The same error 13 was there.
I gonna try the full ota image tomorrow or so. Gonna see if that might help with a locked bootloader. I hope it can be sorted, because it's stupid if a phone like the pixel has such issues
Can you also please check in logcat what it shows for you when you search for widevine and drm?
Also is that file I mentioned above also available in that specific folder? And other widevine files in that folder?
Sent from my Google Pixel 3 XL using XDA Labs
DeeZZ_NuuZZ said:
Yes that is the strange thing, L1 worked fine when I was on aquarios first.
Sent from my Google Pixel 3 XL using XDA Labs
Click to expand...
Click to collapse
Then tried DU and had to reflash factory image and L1 wasn't working anymore. ( have you flashed any vendor.img other than the one's you have extracted from google's full factory.img file )
had to reflash factory image and L1 wasn't working anymore. ( i've flashed factory image with a full wipe and without wipe multiple times including last week while trying to do a clean install with april image along with -w )
Can you also please check in logcat what it shows for you when you search for widevine and drm? (didn't get this question sorry )
Also is that file I mentioned above also available in that specific folder? ( i have vendor/firmware_mnt/image folder but there is no widevine.mdt )
And other widevine files in that folder? (no widevine files in that folder)
SacredDeviL666 said:
had to reflash factory image and L1 wasn't working anymore. ( have flashed mutltiple times factory image including last week while trying to do a clean install with april image along with -w )
Can you also please check in logcat what it shows for you when you search for widevine and drm? (didn't get this question sorry )
Also is that file I mentioned above also available in that specific folder? ( i have vendor/firmware_mnt/image folder but there is no widevine.mdt )
And other widevine files in that folder? (no widevine files in that folder)
Click to expand...
Click to collapse
For the logcat I mean when you use an app like matlog, you can directly use the search function to search for specific words, in that case widevine and drm. Can you attach the screenshot/logs of both ?
Also very strange that there is no such file in the imagine folder and yet L1 works fine for you....
Did you try different ROMs, or only bootleggers? Was it always on L1?
Actually I haven't flashed vendor.img manually, I let the flash script do the job. Do you think this might be the issue?
Also I don't remember if I flashed the April vendor from DU homepage ....
Sent from my Google Pixel 3 XL using XDA Labs
DeeZZ_NuuZZ said:
Sent from my Google Pixel 3 XL using XDA Labs
Click to expand...
Click to collapse
For the logcat I mean when you use an app like matlog, you can directly use the search function to search for specific words, in that case widevine and drm. Can you attach the screenshot/logs of both ? (does the attached screenshot of matlog highlighting the result what i got when searched for widevine.dmt helps? and the error the log states is same as what you said in your initial post )
Also very strange that there is no such file in the imagine folder and yet L1 works fine for you.... ( )
Did you try different ROMs, or only bootleggers? Was it always on L1? ( it was always on L1/AOSIP/Bootleggers/Scorpion these are the roms which i keep shuffling in between/Kernel ElementalX/Kirisakura )
Actually I haven't flashed vendor.img manually, I let the flash script do the job. Do you think this might be the issue? ( no harm in giving a try as flashing vendor image won't mess up your rom setup or installations )
SacredDeviL666 said:
For the logcat I mean when you use an app like matlog, you can directly use the search function to search for specific words, in that case widevine and drm. Can you attach the screenshot/logs of both ? (does the attached screenshot of matlog highlighting the result what i got when searched for widevine.dmt helps? and the error the log states is same as what you said in your initial post )
Also very strange that there is no such file in the imagine folder and yet L1 works fine for you.... ( )
Did you try different ROMs, or only bootleggers? Was it always on L1? ( it was always on L1/AOSIP/Bootleggers/Scorpion these are the roms which i keep shuffling in between/Kernel ElementalX/Kirisakura )
Actually I haven't flashed vendor.img manually, I let the flash script do the job. Do you think this might be the issue? ( no harm in giving a try as flashing vendor image won't mess up your rom setup or installations )
Click to expand...
Click to collapse
Thanks.
Yeah gonna definitely flash full ota img first tomorrow or the day after tomorrow. And maybe unlocking again at the weekend and flash vendor.img on both slots manually
Sent from my Google Pixel 3 XL using XDA Labs
DeeZZ_NuuZZ said:
Thanks.
Yeah gonna definitely flash full ota img first tomorrow or the day after tomorrow. And maybe unlocking again at the weekend and flash vendor.img on both slots manually
Sent from my Google Pixel 3 XL using XDA Labs
Click to expand...
Click to collapse
Let me know if you get that sorted because I too have L3 and I've flashed stock April image with full wipe and relocked the bootloader. Unclear what the issue is...
Dark_Eyes_ said:
Let me know if you get that sorted because I too have L3 and I've flashed stock April image with full wipe and relocked the bootloader. Unclear what the issue is...
Click to expand...
Click to collapse
According to freak07 it might be related to the trustzone, that it doesn't allow to use Level 1...
Gonna try different things this week and also wait for widevine support for an answer ...
Sent from my Google Pixel 3 XL using XDA Labs
My phone is unlocked since day one, I am on Q Beta 2 and before i used to flash 3 different Custom ROMS and back to factory image abt 4 times. i always have L1 on the security level.
driss.sadok said:
My phone is unlocked since day one, I am on Q Beta 2 and before i used to flash 3 different Custom ROMS and back to factory image abt 4 times. i always have L1 on the security level.
Click to expand...
Click to collapse
Yeah there must be some sort of trigger or so, which seems to break Widevine. I probably gonna flash later today the full ota image and then see if it might be working again
Sent from my Google Pixel 3 XL using XDA Labs
DeeZZ_NuuZZ said:
Yeah there must be some sort of trigger or so, which seems to break Widevine. I probably gonna flash later today the full ota image and then see if it might be working again
Sent from my Google Pixel 3 XL using XDA Labs
Click to expand...
Click to collapse
Keep us updated on this. I'm curious too since mine is showing L3 as well and I'm rooted on stock with the latest Kirisakura kernel.
Flyer66 said:
Keep us updated on this. I'm curious too since mine is showing L3 as well and I'm rooted on stock with the latest Kirisakura kernel.
Click to expand...
Click to collapse
okay, so I've flashed the latest full ota image... and guess what?
IT DIDN'T FIXED IT... man I'm so annoyed and tired by this...
really...on every other device which came with L1 out-of-the-box too, will always revert back to L1 when back to full stock/relocked/locked bootloader...only the pixel now has some issue like that ... and somehow I can't find any otherpost about it... is there really no one else who cares about that? paying so much money for a phone and then things like that don't work properly... it's somehow sad...
DeeZZ_NuuZZ said:
okay, so I've flashed the latest full ota image... and guess what?
IT DIDN'T FIXED IT... man I'm so annoyed and tired by this...
really...on every other device which came with L1 out-of-the-box too, will always revert back to L1 when back to full stock/relocked/locked bootloader...only the pixel now has some issue like that ... and somehow I can't find any otherpost about it... is there really no one else who cares about that? paying so much money for a phone and then things like that don't work properly... it's somehow sad...
Click to expand...
Click to collapse
Bro try this post, i didn't read all and it's old, but it may help somehow.
https://forum.xda-developers.com/android/apps-games/app-netflix-hd-widevine-drm-l1-devices-t3307241
driss.sadok said:
Bro try this post, i didn't read all and it's old, but it may help somehow.
https://forum.xda-developers.com/android/apps-games/app-netflix-hd-widevine-drm-l1-devices-t3307241
Click to expand...
Click to collapse
This only works if the device has L1 but is not whitelisted by Netflix (like the HTC u12+, it's L1 but server side not whitelisted, same as Amazon)
I'm still waiting for an answer from the Widevine team... Hopefully they will come back to me soon
Sent from my Google Pixel 3 XL using XDA Labs
DeeZZ_NuuZZ said:
This only works if the device has L1 but is not whitelisted by Netflix (like the HTC u12+, it's L1 but server side not whitelisted, same as Amazon)
I'm still waiting for an answer from the Widevine team... Hopefully they will come back to me soon
Sent from my Google Pixel 3 XL using XDA Labs
Click to expand...
Click to collapse
Did you contact google support or checked google forums? I think it has something only with google devices
driss.sadok said:
Did you contact google support or checked google forums? I think it has something only with google devices
Click to expand...
Click to collapse
Yes posted on google forum/community and also contacted the support. They advised me to contact widevine. Even though it should be an issue by them, not widevine directly...
Sent from my Google Pixel 3 XL using XDA Labs
Very strange. I have Pixel 3 and my level is L1. This even though it is rooted, bootloader unlocked, and running DU rom.
wangdaning said:
Very strange. I have Pixel 3 and my level is L1. This even though it is rooted, bootloader unlocked, and running DU rom.
Click to expand...
Click to collapse
Yeah there must be some sort of trigger or so, where it can end up with L3 all the time.
Sent from my Google Pixel 3 XL using XDA Labs
Related
Just need to know if this is possible and if so what steps to take
Sent from my Pixel XL using Tapatalk
FUZER384 said:
Just need to know if this is possible and if so what steps to take
Click to expand...
Click to collapse
On beta O? I was rooted on beta but I had supersu so Android pay didn't work, but the steps were the same as any other firmware
sakumaxp said:
On beta O? I was rooted on beta but I had supersu so Android pay didn't work, but the steps were the same as any other firmware
Click to expand...
Click to collapse
Yeah Android Pay is a must for me, from researching it it seems like it's possible with Magisk and having 7.1.2 on another slot. I just can't put the right steps together for some reason
Sent from my Pixel XL using Tapatalk
FUZER384 said:
Yeah Android Pay is a must for me, from researching it it seems like it's possible with Magisk and having 7.1.2 on another slot. I just can't put the right steps together for some reason
Click to expand...
Click to collapse
I highly doubt that is possible since you need rc2 to flash magisk and it won't flash if one of your slots has an Android O boot.IMG.
pcriz said:
I highly doubt that is possible since you need rc2 to flash magisk and it won't flash if one of your slots has an Android O boot.IMG.
Click to expand...
Click to collapse
I have RC2 TWRP working fine on mine, problem is I locked my BL as a troubleshooting step and now VZW disabled the OEM unlocking toggle. This is balsy since I have a Google Play Pixel that I'm using on their network. Oh well I might end up just finding a way to buy another GP Pixel since VZW will never loosen their grip on our bootloaders
FUZER384 said:
I have RC2 TWRP working fine on mine, problem is I locked my BL as a troubleshooting step and now VZW disabled the OEM unlocking toggle. This is balsy since I have a Google Play Pixel that I'm using on their network. Oh well I might end up just finding a way to buy another GP Pixel since VZW will never loosen their grip on our bootloaders
Click to expand...
Click to collapse
Could be worse. You couldve bricked it locking your boot loader with modifications...
pcriz said:
Could be worse. You couldve bricked it locking your boot loader with modifications...
Click to expand...
Click to collapse
True
Sent from my Pixel XL using Tapatalk
FUZER384 said:
True
Click to expand...
Click to collapse
Whatever else you might say about the Pixel and how much harder it is to flash on this phone than others it seems to be virtual impossible to hard brick this phone. Any other phone I've ever used you would be screwed now. It sucks that Verizon locked your bootloader even though you have a Google Phone but if you have any flashing experience at all you should have known not to lock your bootloader when you weren't running full stock because on any other phone I know of that would result in an automatic bootloop. You might want to report to Pixel Support that you are having a problem with your phone--overheating and poor battery life are the two most common ones. They will RMA your phone and send you another Google version if that was what you originally bought--you just need to enable OEM unlocking before you accept any updates from Verizon. If you did a factory reset before returning the phone you might end up back on full stock or boot looping the phone--neither of which would really be bad in your case.
jhs39 said:
Whatever else you might say about the Pixel and how much harder it is to flash on this phone than others it seems to be virtual impossible to hard brick this phone. Any other phone I've ever used you would be screwed now. It sucks that Verizon locked your bootloader even though you have a Google Phone but if you have any flashing experience at all you should have known not to lock your bootloader when you weren't running full stock because on any other phone I know of that would result in an automatic bootloop. You might want to report to Pixel Support that you are having a problem with your phone--overheating and poor battery life are the two most common ones. They will RMA your phone and send you another Google version if that was what you originally bought--you just need to enable OEM unlocking before you accept any updates from Verizon. If you did a factory reset before returning the phone you might end up back on full stock or boot looping the phone--neither of which would really be bad in your case.
Click to expand...
Click to collapse
I locked my bootloader ON stock dp3 thinking because I have a GPE it wouldn't matter. For God's sake I got the package from the Google preview site, had nothing to do with Verizon. Big red must've worked something out with Google to allow them to lock the toggle by IMEI. I had not read this in all my research trying to root on dp3
Sent from my Pixel XL using Tapatalk
jhs39 said:
Whatever else you might say about the Pixel and how much harder it is to flash on this phone than others it seems to be virtual impossible to hard brick this phone. Any other phone I've ever used you would be screwed now. It sucks that Verizon locked your bootloader even though you have a Google Phone but if you have any flashing experience at all you should have known not to lock your bootloader when you weren't running full stock because on any other phone I know of that would result in an automatic bootloop. You might want to report to Pixel Support that you are having a problem with your phone--overheating and poor battery life are the two most common ones. They will RMA your phone and send you another Google version if that was what you originally bought--you just need to enable OEM unlocking before you accept any updates from Verizon. If you did a factory reset before returning the phone you might end up back on full stock or boot looping the phone--neither of which would really be bad in your case.
Click to expand...
Click to collapse
Isn't kind of against the rules to suggest users make false reports to return device?
Not to mention what it makes the user look like if they boot up the device and see what is running on it.
Smart thing to do first would be to side load an ota, or attempt to.
Inform them you purchased the one you purchased because you could unlock and youre not happy with the condition of the device.
This narrative may be helpful because it puts op down a path that may get him a true GPE device.
Seems that I have just the opposite with you. I deadly want my XL 8.0 OPP3 to be UNLOCKED......
Has anyone released a modified stock kernel for O Preview that bypasses unlocked bootloader checks? I don't care about root but I like my bootloader unlocked, still want Netflix and Android Pay though.
Hi all,
Pixel 3 XL
Android 10(QP1A.190711.020)
ELEMENTALX-P3-2.05
Have a look at attached screenshots, how would one apply the new update without messing it up, i finally have GPay working, and I really want to keep it that way.
Thanks
I cant seem to be able to upload attachments, "url can not prase" ?
Not sure about keeping Google pay, but I followed A/B slot update from here https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
Everything is working fine on QP1A.190711.020.C3
You will need to reflash the kernel.
Only using systemless hosts and edge sense modules in magisk.
rob42ert said:
Hi all,
Pixel 3 XL
Android 10(QP1A.190711.020)
ELEMENTALX-P3-2.05
Have a look at attached screenshots, how would one apply the new update without messing it up, i finally have GPay working, and I really want to keep it that way.
Thanks
I cant seem to be able to upload attachments, "url can not prase"
Click to expand...
Click to collapse
How'd you get Google Pay working?
I flashed the complete system img removing the -w and re-rooted (pulled boot.img from the zip and had magisk patch it and flash in fastboot)
rquinn19 said:
How'd you get Google Pay working?
I flashed the complete system img removing the -w and re-rooted (pulled boot.img from the zip and had magisk patch it and flash in fastboot)
Click to expand...
Click to collapse
Gpay i got it working with BostonDan method.
Can you please link Boston Dan method?
skaforey said:
Can you please link Boston Dan method?
Click to expand...
Click to collapse
pretty easy to google BostonDan and Google Pay. First result. https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
Edit: Just tried it on my rooted Android 10 3XL and I was able to add my cards. Haven't used it yet but generally if I can add cards I can use it. Thanks
henderjr said:
pretty easy to google BostonDan and Google Pay. First result. https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
Edit: Just tried it on my rooted Android 10 3XL and I was able to add my cards. Haven't used it yet but generally if I can add cards I can use it. Thanks
Click to expand...
Click to collapse
I have been using that method since the day he posted it on a 3 and 3 XL. Both are on 10, and got clean wiped to do so. Both had card reinstalled and have been used at the terminal since the c3 update.
sliding_billy said:
I have been using that method since the day he posted it on a 3 and 3 XL. Both are on 10, and got clean wiped to do so. Both had card reinstalled and have been used at the terminal since the c3 update.
Click to expand...
Click to collapse
Good to hear.! I have a WearOS watch with Google Pay so I haven't had a need to use my phone much.
I have to get rid of ElementalX without losing all my stuff. This kernel has many bugs, my assistent won't start when squeezed anymore.
Is there a way?
rob42ert said:
I have to get rid of ElementalX without losing all my stuff. This kernel has many bugs, my assistent won't start when squeezed anymore.
Is there a way?
Click to expand...
Click to collapse
How exactly have you determined that it is the kernel, and what does "many bug" mean? There are a lot of us who are using ElementalX on 10 with no issues including assistant squeeze. You can start by installing any other kernel available in the "Google Pixel 3 XL ROMs, Kernels, Recoveries, & Other Development" section (you will need to re-root) and see if it makes any difference. It would also be a good idea if you posted in the dedicated thread for ElementalX. Besides getting user answers, @flar2 will be able to answer any questions specific since it is his kernel.
As for possible issues, how you installed could (dirty, clean, OTA/OTA sideload, factory image in BL) make a very possible difference as well as what version you have installed (specifically if you installed the new c3 image). It sounds like you have a bad Android 10 install and are going to end up needing a full clean install. Good luck.
rob42ert said:
I have to get rid of ElementalX without losing all my stuff. This kernel has many bugs, my assistent won't start when squeezed anymore.
Is there a way?
Click to expand...
Click to collapse
There are no bugs in ElementalX kernel.
Installing 2019 system on 2017 shield TV 16g
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
In the end, it is advisable to make fastboot -w (reset to factory)
Disable auto-update after installation, otherwise you will get a brick
A fastboot only works with blocking downloads, until it runs out and is not overloaded until it concludes that they will be software protected. There will be positive results and will work with a closed bootloader on the forum.
Archive
https://cloud.mail.ru/public/36zW/kY8PK6uis
or can download here
https://yadi.sk/d/V0XvRUcxOrk9gA
Are you saying you successfully flashed a 2017 Shield with 2019? Does everything work? Hats off to you!
Drims75 said:
Installing 2019 system on 2017 shield TV 16g
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
In the end, it is advisable to make fastboot -w (reset to factory)
Disable auto-update after installation, otherwise you will get a brick
A fastboot only works with blocking downloads, until it runs out and is not overloaded until it concludes that they will be software protected. There will be positive results and will work with a closed bootloader on the forum.
Archive
https://cloud.mail.ru/public/36zW/kY8PK6uis
or can download here
https://yadi.sk/d/V0XvRUcxOrk9gA
Click to expand...
Click to collapse
starmanj said:
Are you saying you successfully flashed a 2017 Shield with 2019? Does everything work? Hats off to you!
Click to expand...
Click to collapse
I'm curious to know this also. If you have successfully flashed a 2017 with 2019 why aren't there more users interested in this thread.
thanks
If this works....... And I'm sure it won't...... This is amazing!
Sent from my SM-G965F using XDA-Developers Legacy app
starmanj said:
Are you saying you successfully flashed a 2017 Shield with 2019? Does everything work? Hats off to you!
Click to expand...
Click to collapse
Largewoodenspoon said:
If this works....... And I'm sure it won't...... This is amazing!
Sent from my SM-G965F using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'm beginning to think this is bogus because even the original poster has not responded. As I said...something like this would be a very big deal if it was accomplished. Apologies to the OP if I'm wrong.
Only works with an unlocked bootloader.
You didn't answer the question...did you do this yourself? Or are you baiting someone else to do it?
Drims75 said:
Only works with an unlocked bootloader.
Click to expand...
Click to collapse
I uploaded the translator, everything works with the unlocker unlocked, when the bootloader is closed it doesn’t work since the signature of the partitions is checked
Drims75 said:
I uploaded the translator, everything works with the unlocker unlocked, when the bootloader is closed it doesn’t work since the signature of the partitions is checked
Click to expand...
Click to collapse
What do you mean "everything works"? Can you be more specific? Dolby Vision+Atmos works on the Netflix app? The AI sharpening feature and auto-refresh rates features work?
https://nvidia.custhelp.com/app/ans...dolby-atmos,-and-ai-upscaling-become-disabled
What do we gain installing this?
upscaling will not work, everything else works.
Drims75 said:
upscaling will not work, everything else works.
Click to expand...
Click to collapse
Can you please be more specific? Does Netflix work with Dolby Vision+Atmos? How about the Disney+ app? The frame rate matching feature?
Nvidia clearly states that DV+Atmos will not work with the boot loader unlocked.
I don’t really care about the sharpening feature, it’s a useless gimmick anyways.
Drims75 I don't see anyone reporting a successful firmware transplant due to Nvidia disabling the advanced features with unlocked Bootloader.
Flashed it on my Shield 2015 ... the main software was running good, but Netflix said streaming was just not available. No signs of recognizing Dolby Vision, only HDR. Tried with bootloader open and closed, nothing changed
fritzeman said:
Flashed it on my Shield 2015 ... the main software was running good, but Netflix said streaming was just not available. No signs of recognizing Dolby Vision, only HDR. Tried with bootloader open and closed, nothing changed
Click to expand...
Click to collapse
So, pointless.
Just the fact Nvidia knew someone would try this and went out of their way to block it pretty much proves that the 2017 model is almost exactly the same as the 2019 Pro.
Actually it's quite promising you CAN flash onto the older Shields. Someone with skills (I don't) might find a patch to spoof the firmware...!
Wagmans said:
So, pointless.
Just the fact Nvidia knew someone would try this and went out of their way to block it pretty much proves that the 2017 model is almost exactly the same as the 2019 Pro.
Click to expand...
Click to collapse
starmanj said:
Actually it's quite promising you CAN flash onto the older Shields. Someone with skills (I don't) might find a patch to spoof the firmware...!
Click to expand...
Click to collapse
Not me either.
Still can't get over how Nvidia is marketing the 2019 Pro as a new machine when it's really not. They just added software features their user base has been asking for for years and are charging full price for it.
edited
starmanj said:
Actually it's quite promising you CAN flash onto the older Shields. Someone with skills (I don't) might find a patch to spoof the firmware...!
Click to expand...
Click to collapse
not very surprising since bl is unlocked lol.. u can flash android firmware if u want lol.. ppl been porting roms and features since the beginning of time.. only problem is theres not many devs for nstv and the majority r just complaining about not having it bcuz its "not an upgrade" to them.. sounds to me like theyd sure like the new additions lol
Are you saying Netflix doesn't work at all (streaming not available)? Or no atmos? In other words if you flash to 2019 do you LOSE anything.
Also, try deleting and reinstalling Netflix...
fritzeman said:
Flashed it on my Shield 2015 ... the main software was running good, but Netflix said streaming was just not available. No signs of recognizing Dolby Vision, only HDR. Tried with bootloader open and closed, nothing changed
Click to expand...
Click to collapse
Hi!
Like the title said i have an redmi note 8 pro with ANDROID 9 stock firmware rooted but while im try to change the name of magisk
i recive an error and dont let me change the name and also my CTS profile is false....
Someone can help me pls?
You won't be able to get around the CTS false flag now without completely removing Magisk. The requirements have changed recently.
wang1chung said:
You won't be able to get around the CTS false flag now without completely removing Magisk. The requirements have changed recently.
Click to expand...
Click to collapse
so what i need to do right now?
roberto_1986 said:
so what i need to do right now?
Click to expand...
Click to collapse
Use the uninstall feature in the Magisk manager app and reboot. If it still fails the safety net pass, I think you need to lock your bootloader which is dicey. Might want to wait for someone else to confirm the steps as it's unique to your ROM version and may cause a hard brick, but typically flashing an unmodified MiFlash tool ROM and then locking the bootloader after should do it.
wang1chung said:
Use the uninstall feature in the Magisk manager app and reboot. If it still fails the safety net pass, I think you need to lock your bootloader which is dicey. Might want to wait for someone else to confirm the steps as it's unique to your ROM version and may cause a hard brick, but typically flashing an unmodified MiFlash tool ROM and then locking the bootloader after should do it.
Click to expand...
Click to collapse
My bootloader is locked atm because im unlocked for downgrade my android 10 to android 9 then im installed stock firmware
then my bootloader is locked again and now i show u some screenshot below.
wang1chung said:
Use the uninstall feature in the Magisk manager app and reboot. If it still fails the safety net pass, I think you need to lock your bootloader which is dicey. Might want to wait for someone else to confirm the steps as it's unique to your ROM version and may cause a hard brick, but typically flashing an unmodified MiFlash tool ROM and then locking the bootloader after should do it.
Click to expand...
Click to collapse
Sorry i was unable to attach so im uploaded online then shared here
https://ibb.co/Jn3Hf20
https://ibb.co/vQPs9hB
https://ibb.co/rmZF07L
https://ibb.co/g7KX1Zc
https://ibb.co/XV77MnF
https://ibb.co/12K06DY
wang1chung said:
You won't be able to get around the CTS false flag now without completely removing Magisk. The requirements have changed recently.
Click to expand...
Click to collapse
You can get around it by using the "MagiskHide Props Config" module and using it to change your devices fingerprint. At least on Android 10(Pixel Experience, CFW, Used Pixel 4 XL fingerprint)
Images don't appear to be working so here: https://m.imgur.com/a/wZ70wOG
Sapphiress said:
You can get around it by using the "MagiskHide Props Config" module and using it to change your devices fingerprint. At least on Android 10(Pixel Experience, CFW, Used Pixel 4 XL fingerprint)
Images don't appear to be working so here: https://m.imgur.com/a/wZ70wOG
Click to expand...
Click to collapse
already tryed this method and didnt worked...
roberto_1986 said:
already tryed this method and didnt worked...
Click to expand...
Click to collapse
Did you run the script or did you just install the module?
roberto_1986 said:
already tryed this method and didnt worked...
Click to expand...
Click to collapse
Same here, that's why I thought locking was the only way. There was a thread about this somewhere, didn't think magisk hide worked anymore.
I'll try what @Sapphiress mentioned, thanks!
Edit: no dice, didn't work with the GSI option for finger print. Any suggestions on which fingerprint to use for Android 10 GSI Quack?
wang1chung said:
Same here, that's why I thought locking was the only way. There was a thread about this somewhere, didn't think magisk hide worked anymore.
I'll try what @Sapphiress mentioned, thanks!
Edit: no dice, didn't work with the GSI option for finger print. Any suggestions on which fingerprint to use for Android 10 GSI Quack?
Click to expand...
Click to collapse
im tryed doing fingerprint also but didnt worked for my phone too...thats too bad...
and what did u mean for "lock"?
Sapphiress said:
Did you run the script or did you just install the module?
Click to expand...
Click to collapse
what script are u talking about? are u talaking about fingerprint? if yes didnt worked for me
maybe with a custom rom can work?
roberto_1986 said:
im tryed doing fingerprint also but didnt worked for my phone too...thats too bad...
and what did u mean for "lock"?
Click to expand...
Click to collapse
My bootloader is unlocked and I read elsewhere that that can cause the CTS flag to fail. I tried simulating a K20 fingerprint and all it did was disable my sim, lol.
roberto_1986 said:
what script are u talking about? are u talaking about fingerprint? if yes didnt worked for me
maybe with a custom rom can work?
Click to expand...
Click to collapse
He means did you run the "props" script from a terminal
wang1chung said:
My bootloader is unlocked and I read elsewhere that that can cause the CTS flag to fail. I tried simulating a K20 fingerprint and all it did was disable my sim, lol.
He means did you run the "props" script from a terminal
Click to expand...
Click to collapse
yhea i followed the "Didgeridoohan" tutorial but didnt worked for me
also my phone is rooted but my bootloader is locked atm
Must only work on CFW then.
My bootloader is also unlocked.
My exact load out is:
CFW Pixel experience
CFW TWRP
CFW Zentisu kernel
I used the emulate device option in the props script and set it to Pixel 4 XL.
I can confirm that Netflix and Google Play works. At least on global with My setup.
Sapphiress said:
Must only work on CFW then.
My bootloader is also unlocked.
My exact load out is:
CFW Pixel experience
CFW TWRP
CFW Zentisu kernel
I used the emulate device option in the props script and set it to Pixel 4 XL.
I can confirm that Netflix and Google Play works. At least on global with My setup.
Click to expand...
Click to collapse
My bootloader in NOT unlocked
also can u be more specific?
did u have my same phone redmi note 8 pro?
wich android version are u running? mine is 9
both CTS profile and basic security is on true?
did u able to change the name of magisk?
also can u link where did u downloaded your CFW + the guide?
answer all my question pls ty
roberto_1986 said:
My bootloader in NOT unlocked
also can u be more specific?
did u have my same phone redmi note 8 pro?
wich android version are u running? mine is 9
both CTS profile and basic security is on true?
did u able to change the name of magisk?
also can u link where did u downloaded your CFW + the guide?
answer all my question pls ty
Click to expand...
Click to collapse
Yes, I have a Redmi Note 8 Pro(Global)
Android 10 CFW (Pixel Experience)
CTS Profile and basicSec are True, I've already stated that GooglePay and Netflix both work.
No, I haven't, as I don't see a reason too. If it's to hide it from other people then this can be accomplished with a 3rd party launcher, otherwise I don't see the point.
All of these questions have been answered in my previous posts aside from renaming magisk.
Everything you need to know about CFW and flashing custom ROMS is available in the Redmi Note 8 Pro megatread I advise reading it in its entirety and reading the entire comment chain(i know it's a lot buts it's important) before attempting anything, and everything else I'm using is in the Development ROMS, KERNELS, Etc. Section.
I can't really comment links right now as I'm in using the labs app.
Sapphiress said:
Yes, I have a Redmi Note 8 Pro(Global)
Android 10 CFW (Pixel Experience)
CTS Profile and basicSec are True, I've already stated that GooglePay and Netflix both work.
No, I haven't, as I don't see a reason too. If it's to hide it from other people then this can be accomplished with a 3rd party launcher, otherwise I don't see the point.
All of these questions have been answered in my previous posts aside from renaming magisk.
Everything you need to know about CFW and flashing custom ROMS is available in the Redmi Note 8 Pro megatread I advise reading it in its entirety and reading the entire comment chain(i know it's a lot buts it's important) before attempting anything, and everything else I'm using is in the Development ROMS, KERNELS, Etc. Section.
I can't really comment links right now as I'm in using the labs app.
Click to expand...
Click to collapse
well ty so much
anyway the point to change magisk manager name is because to hack some game i need to change this name or it wont work.
Sapphiress said:
Yes, I have a Redmi Note 8 Pro(Global)
Android 10 CFW (Pixel Experience)
CTS Profile and basicSec are True, I've already stated that GooglePay and Netflix both work.
No, I haven't, as I don't see a reason too. If it's to hide it from other people then this can be accomplished with a 3rd party launcher, otherwise I don't see the point.
All of these questions have been answered in my previous posts aside from renaming magisk.
Everything you need to know about CFW and flashing custom ROMS is available in the Redmi Note 8 Pro megatread I advise reading it in its entirety and reading the entire comment chain(i know it's a lot buts it's important) before attempting anything, and everything else I'm using is in the Development ROMS, KERNELS, Etc. Section.
I can't really comment links right now as I'm in using the labs app.
Click to expand...
Click to collapse
last thing....
did u used official twrp 3.4.0?
because atm im using not official twrp
I own 7T Pro and rooting causing to lose L1 was the reason I avoided doing so and then fell off the ROM scene. Willl be getting 11 in a few a days and tried to look up and research but couldn't find a clear specific answer. Is the issue of L1 downgrading to L3 around?. I'll wait to unlock if that's no longer on an issue on the other phones in series. Really don't want to transfer all data and then redo all again cos unlocking wipes everything. I'll just do use the essential apps till we get proper unlocking guides.
hitzzzzzzzz said:
I own 7T Pro and rooting causing to lose L1 was the reason I avoided doing so and then fell off the ROM scene. Willl be getting 11 in a few a days and tried to look up and research but couldn't find a clear specific answer. Is the issue of L1 downgrading to L3 around?. I'll wait to unlock if that's no longer on an issue on the other phones in series. Really don't want to transfer all data and then redo all again cos unlocking wipes everything. I'll just do use the essential apps till we get proper unlocking guides.
Click to expand...
Click to collapse
IIRC Widevine Level is dependant on bootloader status. So rooting shouldn't have tempered the Widevine level. I know it doesn't exactly answer the question, but if unlocking the bootloader retains L1, then you should be good to go for root.
CoinsClassic said:
IIRC Widevine Level is dependant on bootloader status. So rooting shouldn't have tempered the Widevine level. I know it doesn't exactly answer the question, but if unlocking the bootloader retains L1, then you should be good to go for root.
Click to expand...
Click to collapse
Thanks for the reply. Hopefully L1 status stays the same after root. And am I reading wrong or are you saying one can root without unlocking the bootloader?. Cos that's news to me haha.
hitzzzzzzzz said:
Thanks for the reply. Hopefully L1 status stays the same after root. And am I reading wrong or are you saying one can root without unlocking the bootloader?. Cos that's news to me haha.
Click to expand...
Click to collapse
I'm sorry, maybe my text was a little bit misleading...
To root your device, you need to unlock the bootloader first in any case, yes. But it is the bootloader unlock procedure that "could" potentially downgrade to L3, rooting afterwards does not change Widevine Level. That's what I was trying to say.
CoinsClassic said:
I'm sorry, maybe my text was a little bit misleading...
To root your device, you need to unlock the bootloader first in any case, yes. But it is the bootloader unlock procedure that "could" potentially downgrade to L3, rooting afterwards does not change Widevine Level. That's what I was trying to say.
Click to expand...
Click to collapse
Aah. Gotcha yes. I've even read up how some relocked and got their Widevine back. But it was too random.
hitzzzzzzzz said:
I own 7T Pro and rooting causing to lose L1 was the reason I avoided doing so and then fell off the ROM scene. Willl be getting 11 in a few a days and tried to look up and research but couldn't find a clear specific answer. Is the issue of L1 downgrading to L3 around?. I'll wait to unlock if that's no longer on an issue on the other phones in series. Really don't want to transfer all data and then redo all again cos unlocking wipes everything. I'll just do use the essential apps till we get proper unlocking guides.
Click to expand...
Click to collapse
You can flash the firmware again to get l1 back.
shubham412302 said:
You can flash the firmware again to get l1 back.
Click to expand...
Click to collapse
Yessss. I know that but no point to root then.
hitzzzzzzzz said:
Yessss. I know that but no point to root then.
Click to expand...
Click to collapse
I think you misunderstood. On 7t you can reflash the firmware while bootloader unlocked and rooted and keep root and get L1 back.
shubham412302 said:
I think you misunderstood. On 7t you can reflash the firmware while bootloader unlocked and rooted and keep root and get L1 back.
Click to expand...
Click to collapse
It sounds interesting, could you shed more light on this? By "reflashing the firmware and retaining root" did you flash all the firmware files to their respective partitions except for the boot partition as it would have the Magisk patched boot.img? Or you used the "Magisk Install to Inactive Slot after OTA" method?
binary**# said:
It sounds interesting, could you shed more light on this? By "reflashing the firmware and retaining root" did you flash all the firmware files to their respective partitions except for the boot partition as it would have the Magisk patched boot.img? Or you used the "Magisk Install to Inactive Slot after OTA" method?
Click to expand...
Click to collapse
I don't know the details of it but what i know/remember is that you can just root and then relock the bootloader after which gives you L1 back. I knew about it but wasn't sure if I understood it correctly.
hitzzzzzzzz said:
you can just root and then relock the bootloader
Click to expand...
Click to collapse
I don't think that would be a recommended approach as it could actually end up bricking the device. Anyways, thanks for your insights.
On the OP8Pro and previous, Pixel 6/7 Pro (nd probably others) you could unlock the bootloader, do a standard root with Magisk, install few modules (UniversalSafetyNet Fix, MagiskHid Props Config) and get a full play store certified device that passes SaefetyNet, Supports. WIdeVine L1, and runs everything (financial apps, etc.).
One the OP10 series, I don't even think Nteflix would even run without a ton of hacking (forget about L1 vs L3).
I left OP for two reasons, one was lack of 2 SIM support, and the other was the impossible rooting sitation with the OP10 Pro.
The 11 solves the dual SIM issue, but it doesn't look like it is easy to root without giving up anything. Hopefully someone proves me wrong.
Having said, I am a pretty happy Pixel 7 Pro user now...
MetroWestMA said:
On the OP8Pro and previous, Pixel 6/7 Pro (nd probably others) you could unlock the bootloader, do a standard root with Magisk, install few modules (UniversalSafetyNet Fix, MagiskHid Props Config) and get a full play store certified device that passes SaefetyNet, Supports. WIdeVine L1, and runs everything (financial apps, etc.).
One the OP10 series, I don't even think Nteflix would even run without a ton of hacking (forget about L1 vs L3).
I left OP for two reasons, one was lack of 2 SIM support, and the other was the impossible rooting sitation with the OP10 Pro.
The 11 solves the dual SIM issue, but it doesn't look like it is easy to root without giving up anything. Hopefully someone proves me wrong.
Having said, I am a pretty happy Pixel 7 Pro user now...
Click to expand...
Click to collapse
Running banking apps (like Sparkasse pushtan) just fine with root. According to DRM info app, Widevine is on L1, and Netflix is working (at least it loads the main page as opposed to OP10P). I personally do not miss out on anything, even contactless payment is working with third party apps.
CoinsClassic said:
Running banking apps (like Sparkasse pushtan) just fine with root. According to DRM info app, Widevine is on L1, and Netflix is working (at least it loads the main page as opposed to OP10P). I personally do not miss out on anything, even contactless payment is working with third party apps.
Click to expand...
Click to collapse
So you are saying this is all true after doing a magisk root on a OP 11. Was it a USA version? In any case that is encouraging news indeed.
If I recall, I think the entire issue on the OP 10 Pro was bcause they had moved one of the DRM crypto shared library files to a non standard dir that magisk couldn't patch (or something like that).
Can you check if you device is play store certified -- that + safety net and L1 would confirm that everything should work fine after root.
binary**# said:
I don't think that would be a recommended approach as it could actually end up bricking the device. Anyways, thanks for your insights.
Click to expand...
Click to collapse
Yes. It's absolutely not recommended.
CoinsClassic said:
Running banking apps (like Sparkasse pushtan) just fine with root. According to DRM info app, Widevine is on L1, and Netflix is working (at least it loads the main page as opposed to OP10P). I personally do not miss out on anything, even contactless payment is working with third party apps.
Click to expand...
Click to collapse
You already have root on 11?. If yes, you have a link for the steps?.