Related
Hi,
can anyone help me to revert A520f 2017 Knox to 0x0.
Unfortunately I tried to Root my A5 2017, I am luckily successful to root my phone, but after that I realized that I will not receive OTA nor able to use sHealth app.
So I downloaded stock Rom and Totally re-flash everything(AP, BL, CSC...).... Although it remove the Custom recovery + super user etc. But when I tried to Open sHealth App, it saying that "Due to new Security Policy Samsung Health cannot be opened on a Rooted device. 0x110040581".
So, Is there any way available to reset everything means to bring it to zero position?
qazihamayun said:
Hi,
can anyone help me to revert A520f 2017 Knox to 0x0.
Unfortunately I tried to Root my A5 2017, I am luckily successful to root my phone, but after that I realized that I will not receive OTA nor able to use sHealth app.
So I downloaded stock Rom and Totally re-flash everything(AP, BL, CSC...).... Although it remove the Custom recovery + super user etc. But when I tried to Open sHealth App, it saying that "Due to new Security Policy Samsung Health cannot be opened on a Rooted device. 0x110040581".
So, Is there any way available to reset everything means to bring it to zero position?
Click to expand...
Click to collapse
Sorry cant help you with this but just one curious question. Is samsung pay also not working after rooting?
Sent from my SM-A720F using Tapatalk
cardozclive said:
Sorry cant help you with this but just one curious question. Is samsung pay also not working after rooting?
Click to expand...
Click to collapse
Samsung pay cannot work with knox tripped
ponkz said:
Samsung pay cannot work with knox tripped
Click to expand...
Click to collapse
Can you tell me is there any way available to use Samsung Health App. I am not worried about knox tripped nor warrenty clain... but worried about using default Application, OTA and Patch etc.
Would it possible use all these using root? Or any other way available..
Eg. I was using xposed in LG G3 which having small app like root clock. Which allow to fake those app which were not working on rooted device. But knox case seems different
qazihamayun said:
Can you tell me is there any way available to use Samsung Health App. I am not worried about knox tripped nor warrenty clain... but worried about using default Application, OTA and Patch etc.
Would it possible use all these using root? Or any other way available..
Eg. I was using xposed in LG G3 which having small app like root clock. Which allow to fake those app which were not working on rooted device. But knox case seems different
Click to expand...
Click to collapse
If you want to hide root, use Magisk su instead.
ashyx said:
If you want to hide root, use Magisk su instead.
Click to expand...
Click to collapse
No I dont want to hide root explicitly , I just want to use Samsung Health Application, if there is any way available to by pass the error message
"Due to new Security Policy Samsung Health cannot be opened on a Rooted device. 0x110040581".
Kindly tell me, either by hiding the Root Or Editing any file
qazihamayun said:
No I dont want to hide root explicitly , I just want to use Samsung Health Application, if there is any way available to by pass the error message
"Due to new Security Policy Samsung Health cannot be opened on a Rooted device. 0x110040581".
Kindly tell me, either by hiding the Root Or Editing any file
Click to expand...
Click to collapse
I just told you, to bypass apps that detect root you need Magisk su.
https://forum.xda-developers.com/showpost.php?p=71154562&postcount=4
There is no way to restore knox, so... rip Shealt
Yes eFuse Chip is to blame....
Gesendet von meinem SM-A520F mit Tapatalk
qazihamayun said:
Can you tell me is there any way available to use Samsung Health App. I am not worried about knox tripped nor warrenty clain... but worried about using default Application, OTA and Patch etc.
Would it possible use all these using root? Or any other way available..
Eg. I was using xposed in LG G3 which having small app like root clock. Which allow to fake those app which were not working on rooted device. But knox case seems different
Click to expand...
Click to collapse
You are able to use samsung health after rooting.
you have to be rooted again and i would recommend using TWRP + Magisk to root so it is systemless and you can still pass safetynet after rooting.
you will need to download TWRP, Magisk v12.0, dm-verity patch.
1. put magisk v12.0 and dm-verity patch onto the sdcard in the phone
2. flash TWRP
3. boot into recovery and swipe to allow modifications.
4. under wipe there should be a button to format data (its in the bottom right). you will need to do this to flash magisk and dm verity.
5. flash dm verity and THEN magisk
6a. boot into phone and complete setup to get to home page.
6b. download any systemless root app that you want (adaway works you just have to turn on systemless host files in magisk settings + viper4andriod has a module in magisk that you download for it to work)
(DO NOT TURN ON HIDE MAGISK UNTIL THE END)
7. download the app buildprop editor, open it and grant it root. search for the line ro.config.tima=1 and change the value from 1 to 0.
8. reboot the phone and you should now be able to use s health.
continue following if you wish to pass safetynet and be playstore certified (set up your root apps like viper and adaway before doing this)
9. go into magisk settings and enable the setting Magisk Hide. reboot phone. check that you pass safetynet in magisk manager after booting up again
10. go into app manager, find google play store, tap storage and then clear the data.
11. open app again and you should be certified. (this took me a few tries. not sure if it was play store needing to update the property or me needing to reboot the phone)
12. Yay! your device should now be able to pass safetynet and will be play store certified in the play store app. you should soon be able to see netflix in the play store again.
source: I done this on my a520 just on the weekend to be able to update netflix
Hey is tethering possible without root on oreo? Verizon grandfathered plan, get error when I do it on stock.
thanks
Nblufire12 said:
Hey is tethering possible without root on oreo? Verizon grandfathered plan, get error when I do it on stock.
thanks
Click to expand...
Click to collapse
I don't believe so. (Other than paying for the addition of tethering to your plan) At one time there was a rootless "method" that required removal/insertion of the SIM card and specific timing of launching the hotspot - but not sure if those work anymore. With root, I believe the current method requires editing the build.prop file. That's what I'm currently using and it is working fine - but I am rooted. Good luck.
S
sb1893 said:
I don't believe so. (Other than paying for the addition of tethering to your plan) At one time there was a rootless "method" that required removal/insertion of the SIM card and specific timing of launching the hotspot - but not sure if those work anymore. With root, I believe the current method requires editing the build.prop file. That's what I'm currently using and it is working fine - but I am rooted. Good luck.
S
Click to expand...
Click to collapse
do you still receive OTA's with root??
I usually root and ROM on all my previous phones but this pixel is so damn smooth i figured just KISS
Nblufire12 said:
do you still receive OTA's with root??
I usually root and ROM on all my previous phones but this pixel is so damn smooth i figured just KISS
Click to expand...
Click to collapse
OTA's attempted within android will fail with any modifications to system even "systemless" root. However, it is very easy to simply sideload the OTA that is readily available from Google. This bypasses those "checks" that prevent the OTA from installing from within Android. Essentially, you are just manually installing the OTA via sideloading from within ADB. Entire process is very simple and straightforward. I've been updating my Pixel XL monthly since last December using this method. I did flash factory image (removing -w from flashall.bat) for the upgrade to Oreo. After upgrading via either method, you do need to reinstall root and any mods - but this is fairly quick as well. Other than root, suhide (to allow android pay to work) and the build.prop edit to enable tethering - I am completely stock.
sb1893 said:
OTA's attempted within android will fail with any modifications to system even "systemless" root. However, it is very easy to simply sideload the OTA that is readily available from Google. This bypasses those "checks" that prevent the OTA from installing from within Android. Essentially, you are just manually installing the OTA via sideloading from within ADB. Entire process is very simple and straightforward. I've been updating my Pixel XL monthly since last December using this method. I did flash factory image (removing -w from flashall.bat) for the upgrade to Oreo. After upgrading via either method, you do need to reinstall root and any mods - but this is fairly quick as well. Other than root, suhide (to allow android pay to work) and the build.prop edit to enable tethering - I am completely stock.
Click to expand...
Click to collapse
is your build.prop edit still working on oreo for og pixel xl 1?
Nblufire12 said:
is your build.prop edit still working on oreo for og pixel xl 1?
Click to expand...
Click to collapse
With the January Security update on 8.1, SuperSu 2.82 SR5 / suhide failed to install. It appears that SuperSu requires some changes to allow it to continue working on Jan 2018 Security Update and for whatever reason that work hasn't been completed yet and it is unclear if it is planned to occur. (Chainfire has retired from SuperSu development. And the company he sold the SuperSu and related assets to has not been very communicative on their plans to support going forward.) So based on that, I pulled the trigger to migrate from SuperSu to Magisk/MagiskHide. It was a fairly painless process and I have been pleased with Magisk thus far. I am still able to use Android Pay and hide root as needed from other apps. I am not able to directly edit build.prop (at least haven't figured out how), but Magisk has a tether module which essentially inserts settings contained in build.prop at boot-time and that allows the net.tethering.noprovisioning=true setting to be added and I can confirm that my tethering does work using this method. (That is my layman's understanding of what that module does - apologies if it isn't technically accurate).
Good luck!
S
sb1893 said:
With the January Security update on 8.1, SuperSu 2.82 SR5 / suhide failed to install. It appears that SuperSu requires some changes to allow it to continue working on Jan 2018 Security Update and for whatever reason that work hasn't been completed yet and it is unclear if it is planned to occur. (Chainfire has retired from SuperSu development. And the company he sold the SuperSu and related assets to has not been very communicative on their plans to support going forward.) So based on that, I pulled the trigger to migrate from SuperSu to Magisk/MagiskHide. It was a fairly painless process and I have been pleased with Magisk thus far. I am still able to use Android Pay and hide root as needed from other apps. I am not able to directly edit build.prop (at least haven't figured out how), but Magisk has a tether module which essentially inserts settings contained in build.prop at boot-time and that allows the net.tethering.noprovisioning=true setting to be added and I can confirm that my tethering does work using this method. (That is my layman's understanding of what that module does - apologies if it isn't technically accurate).
Good luck!
S
Click to expand...
Click to collapse
thanks so much for this detailed post! So basically, root my phone, install magisk, install the tether module, profit?!
sb1893 said:
With the January Security update on 8.1, SuperSu 2.82 SR5 / suhide failed to install. It appears that SuperSu requires some changes to allow it to continue working on Jan 2018 Security Update and for whatever reason that work hasn't been completed yet and it is unclear if it is planned to occur. (Chainfire has retired from SuperSu development. And the company he sold the SuperSu and related assets to has not been very communicative on their plans to support going forward.) So based on that, I pulled the trigger to migrate from SuperSu to Magisk/MagiskHide. It was a fairly painless process and I have been pleased with Magisk thus far. I am still able to use Android Pay and hide root as needed from other apps. I am not able to directly edit build.prop (at least haven't figured out how), but Magisk has a tether module which essentially inserts settings contained in build.prop at boot-time and that allows the net.tethering.noprovisioning=true setting to be added and I can confirm that my tethering does work using this method. (That is my layman's understanding of what that module does - apologies if it isn't technically accurate).
Good luck!
S
Click to expand...
Click to collapse
I've been considering switching to the Pixel XL or the 2XL and this is a critical factor for me. From what I gathered from the 2XL forum, this wasn't working. I'm going to see if I can track down if the same Magisk tether module exists for the 2XL. If anyone knows ahead of time, I'd like to know.
Nblufire12 said:
thanks so much for this detailed post! So basically, root my phone, install magisk, install the tether module, profit?!
Click to expand...
Click to collapse
Yes. Installing magisk will root your phone and then you can install the tether module. Good luck!
sb1893 said:
Yes. Installing magisk will root your phone and then you can install the tether module. Good luck!
Click to expand...
Click to collapse
ah ok so we dont have to root before! Just install the apk and itll do all of it for us?!
Nblufire12 said:
ah ok so we dont have to root before! Just install the apk and itll do all of it for us?!
Click to expand...
Click to collapse
I'd recommend following one of the many guides found on XDA. Here is the one I used to get up and running on magisk...you will need to determine which portions of the guide are relevant to your situation and needs.
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
Good luck!
S
I switched from SuperSU to Magisk and it seems that Magisk is way more stable. I kept losing root with SuperSU. I am also able to edit my build.prop with root explorer.
scoobysnack said:
I switched from SuperSU to Magisk and it seems that Magisk is way more stable. I kept losing root with SuperSU. I am also able to edit my build.prop with root explorer.
Click to expand...
Click to collapse
Interesting. I am unable to edit build.prop with Root Explorer (which does have Root Privs). Whenever I open the file for edit in Text Editor within Root Explorer, it allows me to edit the file, but when I "Save Changes and Exit" or "Save Changes" and then exit...those changes are not retained. The timestamp on the build.prop file is unaltered as is the file size. I wonder what the difference is that allows you to edit your build.prop but prevents me from changing mine...I have poked around on the forums and the magisk threads and haven't been able to figure it out. I stopped researching when I discovered the ability to insert those settings at boot time via the magisk modules and decided that was a viable solution (maybe better as it leaves build.prop stock and unchanged.)
Thanks,
S
I click "Save Changes" then I click "Save and Exit" it will say the original file is name .bak
Can the build.prop still be edited to allow tethering without the carrier check?
Yes but you need root and if you have root you have magisk and if you have magisk you can install the tether module which changes the build prop for you.
bigv5150 said:
Yes but you need root and if you have root you have magisk and if you have magisk you can install the tether module which changes the build prop for you.
Click to expand...
Click to collapse
Can i edit it by just unlocking the boot loader and do it through adb? I don't want to root since certain apps don't work with it.
you can root, modify build.prop then unroot...
gatortuba said:
Can i edit it by just unlocking the boot loader and do it through adb? I don't want to root since certain apps don't work with it.
Click to expand...
Click to collapse
I'm pretty sure magisk has a module that hides root or magisk hide root I've never had to hide root so I really don't know but I'm pretty sure you can do that
gatortuba said:
Can i edit it by just unlocking the boot loader and do it through adb? I don't want to root since certain apps don't work with it.
Click to expand...
Click to collapse
If you have time, I would try Magisk with the hide enabled and see if your apps complain. I have not had any detect it yet. Back with supersu even with its hide add on it was a challenge but Magisk is spot on.
With magisk I was able to still use snap chat since it hides the root. YOu should be fine using other apps with magisk.
gatortuba said:
Can i edit it by just unlocking the boot loader and do it through adb? I don't want to root since certain apps don't work with it.
Click to expand...
Click to collapse
You can pull the build.prop through ADB, edit it, push it back and chmod the permissions of the file. There are guides out there with all of the necessary steps. I used to do it this way, but it got to be a pain when they started monthly updates. I went back to rooting the monthly updates and editing the build.prop.
brkshr said:
You can pull the build.prop through ADB, edit it, push it back and chmod the permissions of the file. There are guides out there with all of the necessary steps. I used to do it this way, but it got to be a pain when they started monthly updates. I went back to rooting the monthly updates and editing the build.prop.
Click to expand...
Click to collapse
Do i need to unlock to bootloader to root with magisk?
brkshr said:
You can pull the build.prop through ADB, edit it, push it back and chmod the permissions of the file. There are guides out there with all of the necessary steps. I used to do it this way, but it got to be a pain when they started monthly updates. I went back to rooting the monthly updates and editing the build.prop.
Click to expand...
Click to collapse
How does Magisk work when updates need to be applied?
brkshr said:
You can pull the build.prop through ADB, edit it, push it back and chmod the permissions of the file. There are guides out there with all of the necessary steps. I used to do it this way, but it got to be a pain when they started monthly updates. I went back to rooting the monthly updates and editing the build.prop.
Click to expand...
Click to collapse
Does it work on the latest build?
Hi, are you using pixel 2 xl..? If you are, can you provide me a copy of the build.prop of pixel 2 xl?
brkshr said:
You can pull the build.prop through ADB, edit it, push it back and chmod the permissions of the file. There are guides out there with all of the necessary steps. I used to do it this way, but it got to be a pain when they started monthly updates. I went back to rooting the monthly updates and editing the build.prop.
Click to expand...
Click to collapse
Another, possibly easier option is to install Magisk, download a file explorer from the play store, then scroll down to build.prop and just add the net.tethering.noprovisioning=true. Worked like a boss.
cedargreen said:
Another, possibly easier option is to install Magisk, download a file explorer from the play store, then scroll down to build.prop and just add the net.tethering.noprovisioning=true. Worked like a boss.
Click to expand...
Click to collapse
I can't get the file it needs, all of the files are in a payload.bin file.
Ok don't get mad I need to know if I unlocked device will wipe..
I don't want root
After unlock how. Can edit build prop to get tether working and ones I do will I be getting ota ?
vivrosh said:
Ok don't get mad I need to know if I unlocked device will wipe..
I don't want root
After unlock how. Can edit build prop to get tether working and ones I do will I be getting ota ?
Click to expand...
Click to collapse
If you use Magisk, pretty sure you can just sideload the OTA updates. You will have to go to the TWRP and Magisk threads for the XL 2. Magisk is root, but does not break Android Pay.
Can anyone summarize how best to enable hotspot tethering on the pixel 2 xl? I don't need root, and prefer to not have it enabled. I don't mind rooting it once to enable it, then unrooting, so long as the tethering capability remains and so long as Android updates occur as normal, without the need to re-enable tethering. Is this possible? Thank you.
vinhdizzo said:
Can anyone summarize how best to enable hotspot tethering on the pixel 2 xl? I don't need root, and prefer to not have it enabled. I don't mind rooting it once to enable it, then unrooting, so long as the tethering capability remains and so long as Android updates occur as normal, without the need to re-enable tethering. Is this possible? Thank you.
Click to expand...
Click to collapse
Good question.
vinhdizzo said:
Can anyone summarize how best to enable hotspot tethering on the pixel 2 xl? I don't need root, and prefer to not have it enabled. I don't mind rooting it once to enable it, then unrooting, so long as the tethering capability remains and so long as Android updates occur as normal, without the need to re-enable tethering. Is this possible? Thank you.
Click to expand...
Click to collapse
You can change build prop and then remove root but when you take the ota it may fail I'm not sure I just flash factory images to update. The other issue would be if the ota overwrites the build prop. If that happens you would have to repeat the process after every update.
bigv5150 said:
You can change build prop and then remove root but when you take the ota it may fail I'm not sure I just flash factory images to update. The other issue would be if the ota overwrites the build prop. If that happens you would have to repeat the process after every update.
Click to expand...
Click to collapse
I'm so sorry for the stupid question, but how do you do that? How to edit the build prop? I can't find any guide. I don't see any tethering module in magisk and I can't use my preferred tethering app with magisk (I contacted the dev and he said magisk broke the app). Not being able to tether is the only reason why my new P2X continues in a drawer and in I'm still using my Note 4. Please shed some light on this moron.
Hi I've never wanted to root or custom ROM. I read the instructions and they are pages deep and the issues that come up and are discussed in threads have such confusing back and forth discussions using lingo and abbreviations that make my head spin.
However... Oneplus did their last update on my 5t my fourth oneplus phone... With an already old security update.
Is the only way to not throw away a perfectly working, phone with good Ram and a fairly new battery I paid to have installed just months ago?
If I'm wanting to hold on another year or 2 use the only option custom ROMs that contain security updates?
Is there a way to add security updates without a ROM? Or maybe at least just learn to root and then add just updates or is it only in ROMs?
I could probably happily use my phone as is but worried what effect no security updates really is to my use.
I really tried videos on doing so this myself I'm not comfortable if problems happen. Not very techy.
Any help appreciated
Unfortunately you can no longer get security updates once your device is deemed as old.
Your options will be to get an antivirus app on your phone, install a custom ROM (like LOS or pixel exp), or you can get a new phone.
Since you're new to this stuff I highly recommend you just get a new phone or simply install an antivirus.
Not sure which anti virus is better than which. But I'm confident in Avira, McAfee, and Norton. You may want to purchase their plan though.
Hope I helped.
Thanks alot for the reply. I'll start with an antivirus.
Hello,
I have similar issue, since I would need security patch update to keep running company mails and apps.
I have 2 doubts:
- if I root and install Android 11 custom ROM, security patches will be updated too?
- after this, would I be able to unroot and install company mail apps ( if rooted they will not work) ?
Thanks
Personally I think that your company has put an unfair burden on you to run company mail and apps on your personal phone while expecting you to have an updated phone at the same time. An updated phone should have been "given" to you.
That being said, you can actually flash and run a custom rom without root. Root is optional.
Process is as follows: (you'll need a PC for this)
1. Backup ALL your data
2. Unlock the bootloader
3. Install custom recovery and reboot to recovery
4. Wipe cache & system and format internal memory
5. Copy custom rom & gapps to internal memory
6. Flash custom rom & gapps and reboot system
miloinodense said:
Hello,
I have similar issue, since I would need security patch update to keep running company mails and apps.
I have 2 doubts:
- if I root and install Android 11 custom ROM, security patches will be updated too?
- after this, would I be able to unroot and install company mail apps ( if rooted they will not work) ?
Thanks
Click to expand...
Click to collapse
Yes if you install custom ROM you'll have security updates. It doesn't have to be Android 11 and you don't need root to install a custom ROM.
Also make sure to follow a precise guide about it so you don't encounter any issues. Always make a backup even if you're 100% sure you won't need it.
As far as I know mail apps don't check the integrity or do a SafetyNet check, so even if you root or don't it will work fine.
If you mean banking apps then you can install some modules to bypass the check or just completely remove root. Assuming that you rooted the device.
It shows my lack of knowledge never ever did I think you could Flash a ROM without being rooted.
Thanks
I successfully installed custom ROM w/o root.
But regarding company mail apps, I would need to hide bootloader unlocked status.
maybe it's impossible, if someone has a good idea...
miloinodense said:
I successfully installed custom ROM w/o root.
But regarding company mail apps, I would need to hide bootloader unlocked status.
maybe it's impossible, if someone has a good idea...
Click to expand...
Click to collapse
My banking apps working fine without root with crdroid 7.3 and flamegapps. Might work for your company mail app too.
Some roms readily hide bootloader status
Thanks for the hint, but these company mails apps are checking security patch date too. Last available for oneplus 5t are September 2020, and no further support from oneplus.
miloinodense said:
Thanks for the hint, but these company mails apps are checking security patch date too. Last available for oneplus 5t are September 2020, and no further support from oneplus.
Click to expand...
Click to collapse
Hence that's why the burden should be on the company to provide the "up to date" phone
miloinodense said:
Thanks for the hint, but these company mails apps are checking security patch date too. Last available for oneplus 5t are September 2020, and no further support from oneplus.
Click to expand...
Click to collapse
And that's why the burden should be on the company to provide the "up to date" phone
miloinodense said:
Thanks for the hint, but these company mails apps are checking security patch date too. Last available for oneplus 5t are September 2020, and no further support from oneplus.
Click to expand...
Click to collapse
I think if you change build.prop to some other phone with recent security patches you can bypass this.
XDHx86 said:
I think if you change build.prop to some other phone with recent security patches you can bypass this.
Click to expand...
Click to collapse
Today, I was thinking that this could be good way.
Root, change build.prop, and then unroot.
If you have a link for a good tutorial on change bulid.prop would be nice, thanks.
miloinodense said:
Today, I was thinking that this could be good way.
Root, change build.prop, and then unroot.
If you have a link for a good tutorial on change bulid.prop would be nice, thanks.
Click to expand...
Click to collapse
Just for update:
I tried to Root a stock ROM, edit build.prop (security patch date), unroot, and then lock bootloader.
But even if it was a stock ROM, OP5T was not booting.
Booloader was stopping boot since it was detecting a non-stock ROM.
Indeed, I had to unbrick OP5T since I was not possible to unlock bootloader.
So, still not solved
miloinodense said:
Just for update:
I tried to Root a stock ROM, edit build.prop (security patch date), unroot, and then lock bootloader.
But even if it was a stock ROM, OP5T was not booting.
Booloader was stopping boot since it was detecting a non-stock ROM.
Indeed, I had to unbrick OP5T since I was not possible to unlock bootloader.
So, still not solved
Click to expand...
Click to collapse
Just edit build.prop and use magisk hide module from magisk manager.
XDHx86 said:
Just edit build.prop and use magisk hide module from magisk manager.
Click to expand...
Click to collapse
Edit build.prop w/o root and unlock bootloader is not possible...
Moreover, hiding root will not work with more recent android updates and for sure it will not hide unlock bootloader.
miloinodense said:
Edit build.prop w/o root and unlock bootloader is not possible...
Moreover, hiding root will not work with more recent android updates and for sure it will not hide unlock bootloader.
Click to expand...
Click to collapse
Yeah I assumed you would know that you should root first. But seeing you even attempted to lock bootloader after modifying the device, seems I assumed wrong.
Magisk hide is working fine on later android versions like 8+. And for the bootloader it only trips CTS if your bootloader is using hardware backed key - Which is the case with OP5 - as CTS check also has hardware attestation. But it is possible to bypass said check by using SafetyNet Fix module, of course you will also install that from magisk manager.
Hello!
I will receive a oneplus 9 pro next week and wonder if i shall root it or not. I want to use titanium backup and a few other apps that need root permission, but i also dont want to loose widevine level 1 for netflix and amazon video in hd, want to use my banking app and mcdonalds app.
i havent followed the magisk/root discussion for maybe a year or two (used a unrooted stock phone), so i am not up to date how things are at the moment.
just to be clear, please can someone answer the following questions:
1.) is unlocking bootloader (no root afterwards) enough to loose widevine level 1? can level 1 be gained again when bootloader is locked again or is lost permanent (like triggering knox with samsung).
2.) any problems with mcdonalds app and magisk? google pay?
after reading to the internet on the subject totday, i get the impression that rooting nowadays causes more problems thn benefits, but maybe i get a wrong impression.
flotsch1 said:
Hello!
I will receive a oneplus 9 pro next week and wonder if i shall root it or not. I want to use titanium backup and a few other apps that need root permission, but i also dont want to loose widevine level 1 for netflix and amazon video in hd, want to use my banking app and mcdonalds app.
i havent followed the magisk/root discussion for maybe a year or two (used a unrooted stock phone), so i am not up to date how things are at the moment.
just to be clear, please can someone answer the following questions:
1.) is unlocking bootloader (no root afterwards) enough to loose widevine level 1? can level 1 be gained again when bootloader is locked again or is lost permanent (like triggering knox with samsung).
2.) any problems with mcdonalds app and magisk? google pay?
after reading to the internet on the subject totday, i get the impression that rooting nowadays causes more problems thn benefits, but maybe i get a wrong impression.
Click to expand...
Click to collapse
Use the canary builds of Magisk, enable MagiskHide, and toggle the apps in question, and you're golden. Also, just to be sure, toggle it on for Google stuff like the Google app, Google Play Store, Google Play Services, Google Services Framework, Netflix, McDonald's, GPay, and any other banking or streaming subscription apps. Might want to have Magisk hide its self by changing the app name and signature as well.
GuyInDogSuit said:
Use the canary builds of Magisk, enable MagiskHide, and toggle the apps in question, and you're golden. Also, just to be sure, toggle it on for Google stuff like the Google app, Google Play Store, Google Play Services, Google Services Framework, Netflix, McDonald's, GPay, and any other banking or streaming subscription apps. Might want to have Magisk hide its self by changing the app name and signature as well.
Click to expand...
Click to collapse
thank you for the information.
so i will definitely not loose widevine l1 with unlocking bootloader and root?
to hide magisk itself (change name and signature), i just need to turn this option on in magisk and not need to do this in a manual way?
flotsch1 said:
thank you for the information.
so i will definitely not loose widevine l1 with unlocking bootloader and root?
to hide magisk itself (change name and signature), i just need to turn this option on in magisk and not need to do this in a manual way?
Click to expand...
Click to collapse
Correct, by default it will change to a "default" app icon and rename itself to "Settings" but you can easily still tell it from the device's own system Settings app.
one last question.
following this root instruction https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-11-2-7-7.4252373/ , do i have to use the provided boot images? i feel safer to download the full ota from oneplus official site and extract payload.bin and then use payload dumper to get a boot.img.
flotsch1 said:
one last question.
following this root instruction https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-11-2-7-7.4252373/ , do i have to use the provided boot images? i feel safer to download the full ota from oneplus official site and extract payload.bin and then use payload dumper to get a boot.img.
Click to expand...
Click to collapse
If you are leery of using someone else's boot.img, feel free to do that if you'd like. But regardless, be sure to boot the image, don't flash it. Booting it not only gives you the temporary root access to install Magisk yourself, but also ensures that the patched boot.img is actually valid.
v23 has a fix for SafetyNet API. It looks like that supersedes anything from the last canary/debug builds, so it's probably safe to stick with that. Everything else is the same, though.
GuyInDogSuit said:
v23 has a fix for SafetyNet API. It looks like that supersedes anything from the last canary/debug builds, so it's probably safe to stick with that. Everything else is the same, though.
Click to expand...
Click to collapse
V23?
flotsch1 said:
V23?
Click to expand...
Click to collapse
Latest stable Magisk build. I'm saying you won't need to mess with canary/debug.
When you turn on hide then hide the app the in the settings then your allowed to do anything you like but also hide it in the menu of magisk then your all done don't flash to much crap and magisk hide module is not really finished yet for this device good luck
I rooted it the second i got it
And don't use canary builds of magisk only if you want to run your phone very unstable i recommend the stable version
thanks alot for the information.
i still hazzle to root. i had a oneplus 3 2 years ago and had magisk root/custom rom/twrp, but i also had issues on regular basis and spent alot of time on xda and with flashing. dont know if i want this again or just a phone that works.
and just to be sure:
in case i loose my widevine level 1 because of root or bootloader unlock: will it come back when locking bootloader again and/or unroot. or will it be level 3 forever?
Wildvine L1 is not always retained when unlocking the bootloader. If I unlock mine, I go to L3 every single time, but when I lock it back, I go back to L1. I've tested this 3 times and it happened all 3 times.
flotsch1 said:
thanks alot for the information.
i still hazzle to root. i had a oneplus 3 2 years ago and had magisk root/custom rom/twrp, but i also had issues on regular basis and spent alot of time on xda and with flashing. dont know if i want this again or just a phone that works.
and just to be sure:
in case i loose my widevine level 1 because of root or bootloader unlock: will it come back when locking bootloader again and/or unroot. or will it be level 3 forever?
Click to expand...
Click to collapse
Well to be honest I never had that problem and i need to have my binance hidden as well and everything works well but with some games like slime hunter i really need to hide magisk it self too from the settings but when you do they everything will be working okay. And so far I have seen with magisk hide module what you can download is that there are no keys yet for using in op9p (could be changed didn't check it for a while now)