Question Will unlocking/rooting lead to Widevine DRM downgrade? - OnePlus 11

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?.

Related

Widevine Level 3/ DRM stock and locked bootloader

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

Root your Device without Any Damage/Any Risk to Your Phone by VMOS

I have read something about a new root method.
Is there anyone tried to use this method?
Can it work on our Lg V30?
Here's the link
https://forum.xda-developers.com/android/apps-games/how-to-double-android-free-t3951311
dchinacay said:
I have read something about a new root method.
Is there anyone tried to use this method?
Can it work on our Lg V30?
Here's the link
https://forum.xda-developers.com/android/apps-games/how-to-double-android-free-t3951311
Click to expand...
Click to collapse
1) NO, probably won't work on our V30. Runs on Lollipop, and here's no custom Recovery. Most V30 are up to stock Pie.
2) No we don't need and and don't want it.
Every V30 on the planet can be Bootloader unlocked and rooted.
Why would you need another way to root?
Read the Root Sticky, post #1.
ROOT YOUR V30!
https://forum.xda-developers.com/lg-v30/how-to/root-v30-t3927154
dchinacay said:
I have read something about a new root method.
Is there anyone tried to use this method?
Can it work on our Lg V30?
Here's the link
https://forum.xda-developers.com/android/apps-games/how-to-double-android-free-t3951311
Click to expand...
Click to collapse
You're giving total control to someone in China to run Lollipop.
ChazzMatt said:
You're giving total control to someone in China to run Lollipop.
Click to expand...
Click to collapse
if i use this app for just FUN not for professional,hardcore,sensitive stuf (with new gmail id specifically for vmos) than is it safe? or they will still my data from my main Native OS?
GOOGLE OFFICER said:
if i use this app for just FUN not for professional,hardcore,sensitive stuf (with new gmail id specifically for vmos) than is it safe? or they will still my data from my main Native OS?
Click to expand...
Click to collapse
* It probably won't work and even if it does...
* you probably won't have DTS Surround Sound nor LG camera fixes which both came with later Oreo.
It's up to you, your phone.
If you do really want a root access without losing warranty or bootloader unlock counter goes up. There are plenty virtualization apps which emulates root access, or even xposed system without altering your actual system. I saw on YouTube, someone using that to cheat pubg mobile. You can find that by these keywords: "pubgm cheat no root" or "pubgm cheat virtual"
There's no root option in my phone
What should I do?
(Yes I've turned on my developer options.)
AswinGNath said:
There's no root option in my phone
What should I do?
(Yes I've turned on my developer options.)
Click to expand...
Click to collapse
Why are you trying to use this?
See my answer below. This is what you want, from earlier in the thread:
ChazzMatt said:
1) NO, probably won't work on our V30. Runs on Lollipop, and here's no custom Recovery. Most V30 are up to stock Pie.
2) No we don't need and and don't want it.
Every V30 on the planet can be Bootloader unlocked and rooted.
Why would you need another way to root?
Read the Root Sticky, post #1.
ROOT YOUR V30!
https://forum.xda-developers.com/lg-v30/how-to/root-v30-t3927154
Click to expand...
Click to collapse
ChazzMatt said:
Why are you trying to use this?
See my answer below. This is what you want, from earlier in the thread:
Click to expand...
Click to collapse
It isn't real virtual machine. Just hacked Android runtime running in userspace. :silly:
GOOGLE OFFICER said:
It isn't real virtual machine. Just hacked Android runtime running in userspace. :silly:
Click to expand...
Click to collapse
With REAL root available for ALL V30 variants since mid-2018, I confess I don't really understand why this thread was even started in October 2019 (over a year later) -- or the discussion is still ongoing now almost 2020...
Before mid-2018 only those V30 variants (H930, H930G, secretly Open Market US998 -- but only the 64GB variant) approved by LG could have bootloader unlock code and thus root, but thanks to people here on XDA, ALL V30 can have root. We don't need some "fake" gimmick like this. Maybe for other phones something like this is OK, but all V30 variants can actually be bootloader unlocked and rooted.
For everyone who doesn't know,
Root Sticky, post #1.
ROOT YOUR V30!
https://forum.xda-developers.com/lg-v30/how-to/root-v30-t3927154
Bootloader unlock, install TWRP, root any V30/V30+/V30S on the planet!
https://forum.xda-developers.com/android/apps-games/how-to-double-android-free-t3951311/page6
Yeah....basic fail for anyone who tries this.
Sent from my LG-H932 using XDA Labs

Unlocking the bootloader, anything specific I need to do?

I used to have XZ1 Compact where unlocking bootloader wiped something somewhere and camera stopped working.
Is it the case with XZ2 as well? Do I need to be aware of anything similar?
WalrusInAnus said:
I used to have XZ1 Compact where unlocking bootloader wiped something somewhere and camera stopped working.
Is it the case with XZ2 as well? Do I need to be aware of anything similar?
Click to expand...
Click to collapse
Camera still works of unlocked with newest firmware.
Hello,
First, thanks a lot for the work you made around XZ2 Compact, I come from french forum, and many tutorials quote you.
I wanted to know if there is still a problem to unlock bootloader of the Xperia XZ2 Compact (like losting DRM files and not being able to use camera anymore).
My current build is 52.0.A.11.3, and I would like to unlock bootloader from the developer sony website directly then root my device (I definitely can't imagine using Android without root haha)
So in this following message
MartinX3 said:
Camera still works of unlocked with newest firmware.
Click to expand...
Click to collapse
you're saying that unlocking bootloader isn't a risk anymore, can you confirm it if I'm right, especially with my current build.
Best regards,
stilflip said:
Hello,
First, thanks a lot for the work you made around XZ2 Compact, I come from french forum, and many tutorials quote you.
I wanted to know if there is still a problem to unlock bootloader of the Xperia XZ2 Compact (like losting DRM files and not being able to use camera anymore).
My current build is 52.0.A.11.3, and I would like to unlock bootloader from the developer sony website directly then root my device (I definitely can't imagine using Android without root haha)
So in this following message
you're saying that unlocking bootloader isn't a risk anymore, can you confirm it if I'm right, especially with my current build.
Best regards,
Click to expand...
Click to collapse
Oh thank you
Yeah, unlocking on the newest stock doesn't harm the camera. It changed since PIE. (Maybe change again with Q [to an even better result]).
So don't worry about your camera on unlocking.
If you use a SODP based custom rom the stock DRM is not used for the features. (But the camera there is work in progress and get heavy work over the next months).
MartinX3 said:
Oh thank you
Yeah, unlocking on the newest stock doesn't harm the camera. It changed since PIE. (Maybe change again with Q [to an even better result]).
So don't worry about your camera on unlocking.
If you use a SODP based custom rom the stock DRM is not used for the features. (But the camera there is work in progress and get heavy work over the next months).
Click to expand...
Click to collapse
Oh, that's a really great new !!!
I think I'll stay with the stock rom, I just want to unlock the bootloader, flashing TWRP, then install root (for using Titanium Backup + AdAway + Xposed Framework for XprivacyLua).
Can you just confirm that my wish are possible with the procedure I wrote please ?
stilflip said:
Oh, that's a really great new !!!
I think I'll stay with the stock rom, I just want to unlock the bootloader, flashing TWRP, then install root (for using Titanium Backup + AdAway + Xposed Framework for XprivacyLua).
Can you just confirm that my wish are possible with the procedure I wrote please ?
Click to expand...
Click to collapse
I don't use this stuff except Titanium backup, but if it works for PIE, why not?
MartinX3 said:
I don't use this stuff except Titanium backup, but if it works for PIE, why not?
Click to expand...
Click to collapse
Well, the most important is how to root my device, the use of root I'll do isn't important tho.
But I guess as you didn't say anything about the procedure, I can go for it then
stilflip said:
Well, the most important is how to root my device, the use of root I'll do isn't important tho.
But I guess as you didn't say anything about the procedure, I can go for it then
Click to expand...
Click to collapse
Just follow the twrp instructions.
Magisk is included there

Cant rename Magisk on my Redmi Note 8 PRO

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

How To Guide A23 Unlock Bootloader and Root guides with Video

This is not my work, this simply was found and done by others, so all credit to them
Warning Unlocking and rooting your device is not for everyone, and you risk damaging your device so do it at your own risk.
saw several people asking about, so he is the methods.
to unlock boot loader
to root
video
text Guide by Juhn Wu (Magisk creator)
https://topjohnwu.github.io/Magisk/install.html
Still no any other alternative OS?
Any idea what to install instead of samsung OS?
Rupdabe-GalaxyS6EdgePlus said:
Still no any other alternative OS?
Any idea what to install instead of samsung OS?
Click to expand...
Click to collapse
nothing A23 specific that i know of, but you can try GSI roms
theduke7 said:
nothing A23 specific that i know of, but you can try GSI roms
Click to expand...
Click to collapse
Tnx
will this root method work on the boost variant?
this.guy.lol said:
will this root method work on the boost variant?
Click to expand...
Click to collapse
Nope, any Samsung phone that's sold in the US aka having the letter U or DL "not too sure about ones with U1" cannot be rooted due to having a locked down bootloader and no OEM unlock option, it's been like this ever since the S6 back in 2015. an exploit for the SM-A236U and the SM-S236DL would need to be found to even get close to rooting.
this method works. BUT......
i can root my phone. magisk works fine, but apparently I don't have write permissions on /system
it is unusable because android is annoying me with "service provider update.... the phone needs to be restarted." you can't click away either. over and over again.
SM-A236B
So i unlocked the bootloader and flashed with odin magisk patched boot.img and everything is working fine. Except SELinux, which is in permissive mode now. Jeez.

Categories

Resources