Related
Hey y'all,
It's great to see all the development for our device. I feel like I'm a few short steps from getting Samsung pay to work but I'm just exhausted. Asking for some help.
I was able to flash the stock marshmallow PaulPizz provided for us and Full unroot, then flash Magisksu and Magisk. Currently I've passed root checks, Safetynet and My knox status even lists 0x0. AndroidPay is currently working but let's not stop there. My problem is google no longer lists SamPay as compatible for our device. Looks like I need to get my phone to show up as a Note5. Tried changing the buildprop but still not letting me download them from play. Sideloading SamPay triggers something called DroidX protection.
Anybody pull this off yet?
Thanks to @PaulPizz
LumberjackZac said:
Hey y'all,
It's great to see all the development for our device. I feel like I'm a few short steps from getting Samsung pay to work but I'm just exhausted. Asking for some help.
I was able to flash the stock marshmallow PaulPizz provided for us and Full unroot, then flash Magisksu and Magisk. Currently I've passed root checks, Safetynet and My knox status even lists 0x0. AndroidPay is currently working but let's not stop there. My problem is google no longer lists SamPay as compatible for our device. Looks like I need to get my phone to show up as a Note5. Tried changing the buildprop but still not letting me download them from play. Sideloading SamPay triggers something called DroidX protection.
Anybody pull this off yet?
Thanks to @PaulPizz
Click to expand...
Click to collapse
Did android pay actually work? Modest v6 I can get the same results, but using android pay.. The NFC will not connect or work for a transaction
hmltnjrmy7 said:
Did android pay actually work? Modest v6 I can get the same results, but using android pay.. The NFC will not connect or work for a transaction
Click to expand...
Click to collapse
I recently tested paulpizz rom/kernel with magisk at staples. It worked fine. If safetynet passes and you can add cards to android pay, nfc will work. Otherwise it is an hardware issue.
Hi, I rooted my pixel, after that I tried to install Netflix all from the web but it says that my device is not supported. I tried to hide magisk and even google play and google play services and it didn't worked. How can I install the latest Netflix app on my device ? Thanks
You can't at the moment. It looks like the Play Store is seeing something that neither Magisk Hide or even a cloaked unlocked bootloader can hide. My guess is that it is an attestation similar to how Google Pay is working to fight root and unlocked bootloaders. Clearly, the Netflix help page that claims that certification is the kicker is dead wrong at this point and as of a moth or two ago. Maybe a return to stock, re-lock of your bootloader and facory reset (which locking your BL would do anyways) might get you there, but I am not about to do that. For now, sideload the most recent one off of APK Mirror and if you need to update due to some lost functionality, use one from there when it becomes available.
install netflix then root
pacman photog said:
install netflix then root
Click to expand...
Click to collapse
True, but Play Store will not update Netflix after that one time. I have 4 devices installed that way, and since the Play Store version with 3.14 in it the updates will not show. One of the devices hadn't got 3.14 when the others had and it got the Netflix update two ago. The others didn't get it. That device did not get the last update nor did the others. I suggested in another thread possibly uninstalling the Play Store o get it to revert to the original version and then checking to see if Netflix is available. Even if it works, I am not about to keep an older version of Play Store or have to do that every time Netflix updates. The older version of Netflix is working fine.
My Netflix is on version 7. Not sure what you speaking about version 3
pacman photog said:
My Netflix is on version 7. Not sure what you speaking about version 3
Click to expand...
Click to collapse
I was talking about the Play Store version itself (Play Store>settings).
#1 wait for final q and root.
#2 Netflix doesn't need update lol
#3 my bad lol
What I find fascinating about this is I assumed it was because the bootloader was unlocked. But, flashing the Android Q Beta, allows you to install Netflix with no issues unlocked. But, if you go back and flash P? It's no longer an option. So my theory is out the window..
jbarcus81 said:
What I find fascinating about this is I assumed it was because the bootloader was unlocked. But, flashing the Android Q Beta, allows you to install Netflix with no issues unlocked. But, if you go back and flash P? It's no longer an option. So my theory is out the window..
Click to expand...
Click to collapse
Rooted both ways, neither way? Safetynet?
sliding_billy said:
Rooted both ways, neither way? Safetynet?
Click to expand...
Click to collapse
Rooted, and non rooted. SafetyNet passes fine. I observed this on fresh installations. If I do a fresh factory install of P, I can't install Netflix even before rooting. If I flash stock P, and lock the bootloader? I can install Netflix.
Now with Q? Bootloader unlocked, factory flash Q, can install Netflix. It's very interesting that this doesn't happen with a factory flash of P..
jbarcus81 said:
Rooted, and non rooted. SafetyNet passes fine. I observed this on fresh installations. If I do a fresh factory install of P, I can't install Netflix even before rooting. If I flash stock P, and lock the bootloader? I can install Netflix.
Now with Q? Bootloader unlocked, factory flash Q, can install Netflix. It's very interesting that this doesn't happen with a factory flash of P..
Click to expand...
Click to collapse
This is leading me to believe my previous thoughts about Netflix on the Play Store. I think the Play Store is looking at SafetyNet/Device Certified 1st regardless of device. If that passes, move to the device/OS and see if it is listed for additional checking. Since Q has not been released publicly yet, I am guessing that the check goes no further and shows Netflix. This will probably change at public Q release if not sooner, and updates will cease even if the program is installed already. I believe my Tab S2 713 simply is not listed for additional checking since it is rooted and has an unlocked BL but passes SafetyNet. Play Store shows available and provides updates.
The big question is what additional testing is being performed. I doubt it is checking for unlocked BL unless the kernel masking of unlocked BL simply doesn't work anymore. I tend to think it is a database attestation check similar to what GPay does. Finding that or using MagiskHide Props Config module to set a working fingerprint might work long term, but since older versions of Netflix (already installed on all of my devices) are working OK without updating I am in no hurry to do too much testing.
sliding_billy said:
This is leading me to believe my previous thoughts about Netflix on the Play Store. I think the Play Store is looking at SafetyNet/Device Certified 1st regardless of device. If that passes, move to the device/OS and see if it is listed for additional checking. Since Q has not been released publicly yet, I am guessing that the check goes no further and shows Netflix. This will probably change at public Q release if not sooner, and updates will cease even if the program is installed already. I believe my Tab S2 713 simply is not listed for additional checking since it is rooted and has an unlocked BL but passes SafetyNet. Play Store shows available and provides updates.
The big question is what additional testing is being performed. I doubt it is checking for unlocked BL unless the kernel masking of unlocked BL simply doesn't work anymore. I tend to think it is a database attestation check similar to what GPay does. Finding that or using MagiskHide Props Config module to set a working fingerprint might work long term, but since older versions of Netflix (already installed on all of my devices) are working OK without updating I am in no hurry to do too much testing.
Click to expand...
Click to collapse
Same here.. it's not a deal breaker, it's just frustrating. There's another app from the Playstore that does this from T-Mobile. T-Mobile Device Unlock (or whatever it's called). What made me really raise my eye-brows is during the initial setup of the phone after a fresh flash. In P, during initial setup, when you get to 'install additional apps' it's not listed. If I flash Q, go through setup, it's listed in additional apps.. It's very strange.
jbarcus81 said:
Same here.. it's not a deal breaker, it's just frustrating. There's another app from the Playstore that does this from T-Mobile. T-Mobile Device Unlock (or whatever it's called). What made me really raise my eye-brows is during the initial setup of the phone after a fresh flash. In P, during initial setup, when you get to 'install additional apps' it's not listed. If I flash Q, go through setup, it's listed in additional apps.. It's very strange.
Click to expand...
Click to collapse
Too funny about the T-Mobile device unlock. I had that show up on my phone a few weeks ago, and I deleted it. I have 5 devices on T-Mobile, and that was the only one that it showed up on. I have seen that app before since my boys had a prepaid T-Mobile phone years ago that had that app. The app not showing in additional apps makes sense since it doesn't show up in Play Store from the device and if you search it on the PC it will say not compatible with any of your devices or compatible with some of your devices. I actually chatted with Netflix a little while ago and played stupid about the whole thing. The agent seemed to think that as long as your device was certified the app would show.
jbarcus81 said:
Rooted, and non rooted. SafetyNet passes fine. I observed this on fresh installations. If I do a fresh factory install of P, I can't install Netflix even before rooting. If I flash stock P, and lock the bootloader? I can install Netflix.
Now with Q? Bootloader unlocked, factory flash Q, can install Netflix. It's very interesting that this doesn't happen with a factory flash of P..
Click to expand...
Click to collapse
Glad I found you. That's exactly what I came on here to find -- glad someone else noticed like I did.
vonDubenshire said:
Glad I found you. That's exactly what I came on here to find -- glad someone else noticed like I did.
Click to expand...
Click to collapse
Where did you get the Netflix app? Play store says not compatible with my device. Rooted QB5.
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 07:43 PM ---------- Previous post was at 07:27 PM ----------
Daisymae said:
Where did you get the Netflix app? Play store says not compatible with my device. Rooted QB5.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Forget above. My bad.
Sent from my [device_name] using XDA-Developers Legacy app
yeh appareently APK Mirror doesn't host the Netflix app anymore either, so get it from another site.
Something interesting... Did a clean install of July Pie.. Was using Q but was having some random issues with GPS.. Anyways, I installed the APK and now I'm being told by the application itself that it's not compatible with my device.. WTH!?!?!?? Can't even side-load now??
Pretty sure the Android DRM (Digital Rights Management) Framework does the Netflix locking. There's a magisk module for DRM Bypassing for Netflix
jbarcus81 said:
Something interesting... Did a clean install of July Pie.. Was using Q but was having some random issues with GPS.. Anyways, I installed the APK and now I'm being told by the application itself that it's not compatible with my device.. WTH!?!?!?? Can't even side-load now??
Click to expand...
Click to collapse
You also may need to spoof the device fingerprint. I am on Q so it lets me download right now no matter what. I just spoofed fingerprint for G Pay on top of the database
Just stumbled upon this thread and just wanted to comment. I'm rooted with an unlocked bootloader and I've had no issues with installing Netflix of having it update when needed. I've even had to uninstall and reinstall once with no issue.
Probably been asked thousand times before but I want to get a samsung A7050FN specific answer to this query.
What features and functions would stop working once I unlock bootloader and root with the mentioned procedure on A70 thread?
This phone is near perfect for everyday driver except It needs some Titanium backup and viper4android along with few minor UI tweaks.
If some nice smartsian provide a list, I can peace fully proceed with rooting and bootloader unlocking
secure folder will stop working, also you will need to update your device with Odin.
Since Knox will be tripped, you won't be able to use "Knox features" like Secure Folder (there's 3rd party apps that do the same), Samsung Flox, Samsung Pay (if applicable), Samsung Pass, Samsung Health (there's a workaround for this one?). I've also read there could be problems with some apps like banking and Netflix. (Magisk hide root status feature is your friend) . If you're outside the EU tripping Knox will also void warranty.
xomikron said:
Since Knox will be tripped, you won't be able to use "Knox features" like Secure Folder (there's 3rd party apps that do the same), Samsung Flox, Samsung Pay (if applicable), Samsung Pass, Samsung Health (there's a workaround for this one?). I've also read there could be problems with some apps like banking and Netflix. (Magisk hide root status feature is your friend) . If you're outside the EU tripping Knox will also void warranty.
Click to expand...
Click to collapse
Don't care about secure folder or Samsung pay or warranty or loosing ability to update OTA. I can use odin for that
Can samsung pass and health be bypassed via the technique of changing ro.xxxx.tima= 1 to 0 in build prop file?
Don't use Netflix so don't care. Nor use any banking apps
Would fingerprint, face unlock, ar emoji and other camera features and Samsung themes kepp working?
Once you are rooted and your bootloader is unlocked does your boot screen changes to show tripped knox etc?
I rooted my A705MN. Samsung health does not work for me after tima change to 0. I read somewhere that you would have to modify the apk somehow. Never looked into it too much. You can read about it here https://forum.xda-developers.com/s10-plus/how-to/guide-samsung-health-root-device-t3946881
I am bummed that about the secure folder. I used it a lot with my unrooted S8. You can modify the build.prop to pass the SafetyNet check to be able to use banking and Netflix apps again.
Edit: here is another place to read https://forum.xda-developers.com/galaxy-s9/how-to/guide-s-health-knox-0x1-t3843483
fizzingbees said:
Don't care about secure folder or Samsung pay or warranty or loosing ability to update OTA. I can use odin for that
Can samsung pass and health be bypassed via the technique of changing ro.xxxx.tima= 1 to 0 in build prop file?
Don't use Netflix so don't care. Nor use any banking apps
Would fingerprint, face unlock, ar emoji and other camera features and Samsung themes kepp working?
Once you are rooted and your bootloader is unlocked does your boot screen changes to show tripped knox etc?
Click to expand...
Click to collapse
Samsung Pass uses biometrics to log-in and such, it won't work if the device is rooted. I don't know of any bypasses but I've found this https://forum.xda-developers.com/general/rooting-roms/samsung-pass-knox-tripped-devices-t3687977
I don't see why emoji and general camera features would stop working, they're not really security features, not that the stock camera is very useful. GCam is a better option for photography.
For now, I haven't rooted my device. From my understanding to enter a rooted state with Magisk you need to turn on your phone with a certain key combination, otherwise I don't think anything is displayed when the phone boots, why is that important?
banking? so like logging on to chase online app may not work if i unlock boot and root? that would be just dumb, i mean my nexus 6 was rooted and custom rom-ed and chase worked
xomikron said:
Samsung Pass uses biometrics to log-in and such, it won't work if the device is rooted. I don't know of any bypasses but I've found this https://forum.xda-developers.com/general/rooting-roms/samsung-pass-knox-tripped-devices-t3687977
I don't see why emoji and general camera features would stop working, they're not really security features, not that the stock camera is very useful. GCam is a better option for photography.
For now, I haven't rooted my device. From my understanding to enter a rooted state with Magisk you need to turn on your phone with a certain key combination, otherwise I don't think anything is displayed when the phone boots, why is that important?
Click to expand...
Click to collapse
Our Samsung A70 is very finicky with root and unlocked bootloader. And the rooting method we use is not so very official and stable for us.
So we need to use a certain key combination to keep root and magisk app when rebooting phone.
You mentioned gcam. Which version and config file are you using?
leo5111 said:
banking? so like logging on to chase online app may not work if i unlock boot and root? that would be just dumb, i mean my nexus 6 was rooted and custom rom-ed and chase worked
Click to expand...
Click to collapse
Actually its a security feature.
Many banking and enterprise applications don't work if your bootloader is compromised and your system rooted. They believe that by rooting and gaining administrative status, any hacker can bypass banking app security thereby compromising consumer safety
cealaska said:
I rooted my A705MN. Samsung health does not work for me after tima change to 0. I read somewhere that you would have to modify the apk somehow. Never looked into it too much. You can read about it here https://forum.xda-developers.com/s10-plus/how-to/guide-samsung-health-root-device-t3946881
I am bummed that about the secure folder. I used it a lot with my unrooted S8. You can modify the build.prop to pass the SafetyNet check to be able to use banking and Netflix apps again.
Edit: here is another place to read https://forum.xda-developers.com/galaxy-s9/how-to/guide-s-health-knox-0x1-t3843483
Click to expand...
Click to collapse
It's not like a70 has heart rate sensor and oximeter that I will. Be mad about Samsung health.
Still Samsung makes very stupid decision sometimes.
back to previous statement i NEVER have rooted my phone and then Chase app didnt work, so trying to see before bothering to try and root...EDIT...anyone here with rooted a70 and chase mobile app does it work? that and paypal
fizzingbees said:
It's not like a70 has heart rate sensor and oximeter that I will. Be mad about Samsung health.
Still Samsung makes very stupid decision sometimes.
Click to expand...
Click to collapse
I never really used Samsung Health with my unrooted S8. Fingerprint reader does not work to unlock my rooted A70 on Q (Android 10). It accepts the fingerprint but does not unlock the phone. It goes into a loop where it locks the phone again even I press the fingerprint sensor. I hate the ultrasonic reader lol. Does not work with screen protectors to prevent it from being scratched.
Can't use private mode in Samsung Internet anymore A lot of the features from Samsung seems to be disabled after tripping Knox. I used to love Samsung but with rooting now is a pain in the neck. The build.prop is different than 9 which sucks because I liked "overclocking" kind of making the CPU use all cores, it is not there anymore in Q. I am not sure that the Net improvements hacks for the build prop works anymore. Internet connection does not seem to be as fast for me as 9 was. Edit: I am not sure why the hell we can't use them because it erases the phone when we unlock the bootloader. Even if we re-flash stock they will not work because efuse is already tripped.
back to previous statement i NEVER have rooted my phone and then Chase app didnt work, so trying to see before bothering to try and root...EDIT...anyone here with rooted a70 and chase mobile app does it work? that and paypal
Click to expand...
Click to collapse
I am sorry I do not use those apps. You will have to edit your build.prop to get it to pass the SafetyCheck most likely. If Chase still does not work for you unrooted try contact their support and see if they can help you make it work. I am not liking rooted Q as much as rooted 9 was.
Okay so it means that t rooting and unlocking bootloader leads to Samsung secure folder, Samsung health, Samsung pay, secure login, banking apps and Netflix not working anymore.
Moreover specifically for A70, rebooting phone require specific key combination.
What about boot screen? Does it show any new text after rooting?
My note 4 after rooting shows kernal booting system or kernal booting recovery which is indication thst device has been tempered with.
I have a problem with the making phone calls after rooting. The sounds leak out as if it's on speaker (when it's not) and when on speaker it makes a very shape echo in the back ground.
P.S. havoc os
M.Sam90 said:
I have a problem with the making phone calls after rooting. The sounds leak out as if it's on speaker (when it's not) and when on speaker it makes a very shape echo in the back ground.
P.S. havoc os
Click to expand...
Click to collapse
Turn off voice enhancement in call settings. Or noise reduction in call settings
These settings are known to cause echo or static noise issues during call.
Also try turning off any sound mods you may have done after rooting
Report this issue at hovac os thread. Maybe it's a known issue with that Rom
Headset and sound issues
fizzingbees said:
Turn off voice enhancement in call settings. Or noise reduction in call settings
These settings are known to cause echo or static noise issues during call.
Also try turning off any sound mods you may have done after rooting
Report this issue at hovac os thread. Maybe it's a known issue with that Rom
Click to expand...
Click to collapse
Thanks for the reply but the issues is still the same any other adjustments to recommend ?
fizzingbees said:
Don't care about secure folder or Samsung pay or warranty or loosing ability to update OTA. I can use odin for that
Can samsung pass and health be bypassed via the technique of changing ro.xxxx.tima= 1 to 0 in build prop file?
Don't use Netflix so don't care. Nor use any banking apps
Would fingerprint, face unlock, ar emoji and other camera features and Samsung themes kepp working?
Once you are rooted and your bootloader is unlocked does your boot screen changes to show tripped knox etc?
Click to expand...
Click to collapse
fizzingbees said:
Our Samsung A70 is very finicky with root and unlocked bootloader. And the rooting method we use is not so very official and stable for us.
So we need to use a certain key combination to keep root and magisk app when rebooting phone.
You mentioned gcam. Which version and config file are you using?
Click to expand...
Click to collapse
Sorry for the late reply. I'm using GCam version 7.3.018 by Urnx05 (v1.4) with the config file by dotsx, you can check the file in Telegram by joining the group from this link.
xomikron said:
Sorry for the late reply. I'm using GCam version 7.3.018 by Urnx05 (v1.4) with the config file by dotsx, you can check the file in Telegram by joining the group from this link.
Click to expand...
Click to collapse
Can you kindly post direct link to gcam apk here along with config file as attachment
M.Sam90 said:
Thanks for the reply but the issues is still the same any other adjustments to recommend ?
Click to expand...
Click to collapse
Ask this question in havoc OS thread.
They can help you better than us
xomikron said:
Sorry for the late reply. I'm using GCam version 7.3.018 by Urnx05 (v1.4) with the config file by dotsx, you can check the file in Telegram by joining the group from this link.
Click to expand...
Click to collapse
I found your version but the auxiliary cameras cause the app to crash.
How do you fix this. Any help
Hello,
Yesterday, I successfully rooted my Samsung Galaxy S10+. But since I still had some questions about it, I went on and posted a thread here. User Spaceminer then pointed out that my original post was in the wrong subforum and linked me here. Naturally, I looked at some of the most popular posts in hopes to find answers to my questions. But what I found confused me more than it gave me answers.
Since 2014 with the Samsung Galaxy S5 I got used to rooting in order to disable bloatware, protect my data and customize my phone. I continued doing that with the S8+ until I recently got my hands on the S10. Now, my main reason for rooting are still the same; I want disable (not necessarily uninstall) bloatware, protect my privacy and customize my phone (such as changing the background of the dial when calling someone). But that thread made me wonder if it is even essential to root. I also found a similar post on reddit and most answers seem to agree that it is not necessary to root your phones.
Now, my situation is a bit different. For one, I already rooted my phone. Second, I don't care about warranty nor custom ROMs. But I do want to install a banking app. Also, it is a bit cumbersome to not only have to manually update your phone with every update but the booting requirements with the warning screen are also a bit annoying. So, my question is the following:
What are the advantages of rooting that are not possible without? I have 3 main concerns: Bloatware, Privacy and Customization.
The reason why I posted this in a separate threat is that I was not able to come to a definitive conclusion on my own and most discussion threads are over a year old. By now, the whole process of rooting and what is possible changed since then, so I want to get a more recent insight. I hope you can help me out.
With kind regards,
DasMalzbier
Tbh root is not needed, unless you want to use a custom rom. Most things are already in the android now.
Calyx os not make for samsung Galaxy series and 12 update also comes this year so i think rooting is unnecessary for s10 series
Root is 100%, absolutely necessary for using the phone. I cannot use any phone without it. Critical root-only capabilities:
full system backups (in twrp)
titanium backup
disable updates permanently (update ONLY when want to)
app freezers (app quarantine)
disable/remove bloatware
disable google play services/google play
automate/tasker
cf lumen
adblockers
wifi tether
busybox
superuser
ssh tunnel
update android to later version / install custom roms
optimize system
button mapper
custom theming / substratum
nav gestures
tidypanel
xposed
root explorer
app privacy customizations
3c all-in-one toolbox
more
Without root, the phone is unusable to me. I will never buy any phone without root capability. I am willing to go to different carriers just to get root on the device, or go to different manufacturers if root is blocked. For example, I will never buy a huawei device - they are locked.
I would like to say yes but I can't. the stock apps are very well designed.
The biggest concern is that custom Roms are released faster than modded apps.
For example I tried about ten GCAMs and all of them have a bug... and it becomes more complicated with Exynos.
OpenGcam is not worth samsung app.
Unable to get voice match to work.
Alarms that you can't set to a specific day with the google app.
And so on.
Root is useful when the manufacturer no longer updates the devices.
I regret having Root mine because I lost Samsung Pay and other things.
DemotionFR said:
I would like to say yes but I can't. the stock apps are very well designed.
The biggest concern is that custom Roms are released faster than modded apps.
For example I tried about ten GCAMs and all of them have a bug... and it becomes more complicated with Exynos.
OpenGcam is not worth samsung app.
Unable to get voice match to work.
Alarms that you can't set to a specific day with the google app.
And so on.
Root is useful when the manufacturer no longer updates the devices.
I regret having Root mine because I lost Samsung Pay and other things.
Click to expand...
Click to collapse
The only one that would have any consequence of rooting is Samsung Pay.
xbt- said:
Root is 100%, absolutely necessary for using the phone. I cannot use any phone without it. Critical root-only capabilities:
full system backups (in twrp)
titanium backup
disable updates permanently (update ONLY when want to)
app freezers (app quarantine)
disable/remove bloatware
disable google play services/google play
automate/tasker
cf lumen
adblockers
wifi tether
busybox
superuser
ssh tunnel
update android to later version / install custom roms
optimize system
button mapper
custom theming / substratum
nav gestures
tidypanel
xposed
root explorer
app privacy customizations
3c all-in-one toolbox
more
Without root, the phone is unusable to me. I will never buy any phone without root capability. I am willing to go to different carriers just to get root on the device, or go to different manufacturers if root is blocked. For example, I will never buy a huawei device - they are locked.
Click to expand...
Click to collapse
can you carrier /network unlock with the root >?
NickosD said:
Tbh root is not needed, unless you want to use a custom rom. Most things are already in the android now.
Click to expand...
Click to collapse
No, even if you wanna use custom rom you don't need to root. Just pick the rom with the apps you want or just use the gapps packages you want, if want essential to work gapps then use pico or nano. If there is still something you want to remove and the romdoesn't allow, just use adb shell commands and thats it. Less issues with banks not working because of Magisk (root). I know Magisk has a feature to hide itself, change its name but depending on the app, the libs can be found and know that is Magisk, so for security purposes some apps don't work and some aren't even shown in the Google Play Store just because you rooted the device.
logandavid said:
maybe now the root is not needed but later down the road when your phone will get obsolete and newer android OS updates will be halted for S10+ then you'll be more attracted towards custom roms. Actually it is just personal preference.
Click to expand...
Click to collapse
It's happening right now, I doubt S10+ will receive Android 13 and now just security and bug fix updates are being shipped by Samsung.
Haknor said:
It's happening right now, I doubt S10+ will receive Android 13 and now just security and bug fix updates are being shipped by Samsung.
Click to expand...
Click to collapse
It won't get any new Android upgrades AFAIK.
But appart from tripping knox, what else do I lose if I unlock my bootloader? I read once, quite a while ago, that the battery is limited to 80% of its full capacity. Is that true?
io_gh0st said:
It won't get any new Android upgrades AFAIK.
But appart from tripping knox, what else do I lose if I unlock my bootloader? I read once, quite a while ago, that the battery is limited to 80% of its full capacity. Is that true?
Click to expand...
Click to collapse
Depending on the version, you'll notice stock camera to be limited or not work as expected, secure folder, dual messenger either not working, it can trigger some banks or payment apps (especially if you root), no more ota updates (if you keep using stock rom), drm content can stop working, samsung pay, Play Store might limited the apps you see and so on... Not sure about the battery, for me unlocking the bootloader and switching to another rom made my battery last more than stock, but it depends on the rom, the device, it's not a rule of thumb.
Hi!
Didn't rooted a phone since a long time, I discovered I couln't afterward install Netflix from the Playstore. Found out it's because of the unlocked bootloader, and also found the link to download the APK from Netflix directly: https://help.netflix.com/en/node/12983#android
Unfortunatelly, after installing it with adb, it still refuse to open, "this device isn't supported"
Is there any workaround?
EDIT: the netflix.com version didn't worked, but the latest "nodpi" beta one (v8.7.0_build_8_40058-40058) from apkmirror worked perfectly withtout the need for SafetyNet or anything else.
I think this is a question that really needs confirming by having a rooted user check the playback settings in the Netflix app for the Widevine L1 indicator.
look for an apk that you can manually install. I had to do that with the sammy s 20
Sine. said:
Hi!
Didn't rooted a phone since a long time, I discovered I couln't afterward install Netflix from the Playstore. Found out it's because of the unlocked bootloader, and also found the link to download the APK from Netflix directly: https://help.netflix.com/en/node/12983#android
Unfortunatelly, after installing it with adb, it still refuse to open, "this device isn't supported"
Is there any workaround?
Click to expand...
Click to collapse
You need to be able to pass safety net. There are threads about the topic on here. Once you achieve that, simply wipe data from Play Store and Play Services. Reboot and Play Store should be certified and Netflix should install.
eg1122 said:
You need to be able to pass safety net. There are threads about the topic on here. Once you achieve that, simply wipe data from Play Store and Play Services. Reboot and Play Store should be certified and Netflix should install.
Click to expand...
Click to collapse
This is was I was fearing, but...
lucky_strike33 said:
look for an apk that you can manually install. I had to do that with the sammy s 20
Click to expand...
Click to collapse
It didn't worked with the apk from netflix.com.
Meanwhile, I tried again with one from apkmirror, took the lastest beta "nodpi" one (8.7.0_build_8_40058-40058), and it now works perfectly
When I was bootloader unlocked but root wasn't out yet I couldn't find Netflix and Disney+ in the app store. I had to get them from apkmirror. At that time I still had L1. Now I'm rooted and passing SN and I can see them both in the app store and I'm still L1.
Superxdaer said:
I think this is a question that really needs confirming by having a rooted user check the playback settings in the Netflix app for the Widevine L1 indicator.
Click to expand...
Click to collapse
It says L1 while rooted in Netflix.
You can also use an app called DRM Info to see the widevine status
Sine. said:
This is was I was fearing, but...
It didn't worked with the apk from netflix.com.
Meanwhile, I tried again with one from apkmirror, took the lastest beta "nodpi" one (8.7.0_build_8_40058-40058), and it now works perfectly
Click to expand...
Click to collapse
Can confirm apk from apkmirror with version 8.7.0 build 9 nodpi works with my pixel 6 pro with open bootloader but no root. Thanx for the tip!
Indeed ... I also installed from APK mirror ... version 8.7.0build94006 ... I'm rooted (with Safetynet failing ... but I don't care so much about safetynet as I don't use GPay).