Related
Hi guys I really need some help here. Last night I set out to simply find a way to tether wifi from my GS3 for free. From my understanding that required me to root + download tether app with root admin rights. Apparently it appears to be more in depth than that unless I’m missing something simple. I’ll just start by giving you my specs and tell you what I’ve done so far. Sorry for the long post.
Sprint
Galaxy S3
SPH-L710
JellyBean 4.3
Hardware L710.14
Stock kernel and rom
Followed the steps in this link to root it. It pretty much walks me through using Odin to root the phone. Looks like it also installs SuperSU for superuser access. I like the fact that it’s not too invasive, which is great because I simply want wifi tethering and am not looking for a custom kernel or rom. http://honai-android.blogspot.com/20...-sph-l710.html
Supersu
When I start the phone it says “Unfortunately SuperSU has stopped”
Downloaded the apk, ran it, launched ok, asked me to disable knox and said yes, rebooted phone, got same msg that supersu stopped, runs fine after install apk but fails after every reboot. Maybe knox is screwing with it?
No supersu update on the play store
Regardless I installed root checker and says the device has root access…
I downloaded a bunch of tethering apps I thought had root access but none actually enabled tethering.
Foxfi
When I use CDMA only (used this for troubleshooting purposes) Launch Foxfi, activate wifi hotspot, “unable to connect to data network, turning off hotspot. Your plan may not have hotspot service”’
When I use LTE/CDMA the popup message is you are not subscribed to the Hotspot service. Do you want to see subscription options?”
When I cancel out of that popup it says FoxFI hotspot ready and has the wifi icon on the notification bar but can’t find the wifi network on devices
Also it never requests superuser
1 click wifi tethering free
Launch, click enable, the notification bar says hotspot connected but then I get the same error “unable to connect to data network, turning off hotspot. Your plan may not have hotspot service”, still can’t see the network on other devices
When I use LTE/CDMA the popup message is you are not subscribed to the Hotspot service. Do you want to see subscription options?”
Also it never requests superuser
Wifi Tether TrevE Mod v3.3
Launch, opens fine, asks for superuser access, click button to enable tethering, get an error in the app that says “tethering started with errors! Please check ‘show log’”
Clicking show log gives me an error of “Unable to open log file. File does not exist.”
It still shows a message “Tethering is currently running…” under the “ongoing apps” section but still can’t find wifi network on other devices
Jtether
Launch, “says turning Wifi AP on” requests superuser access, eventually gets to the same message that says “unable to connect to data network, turning off hotspot. Your plan may not have hotspot service”
When I use LTE/CDMA the popup message is you are not subscribed to the Hotspot service. Do you want to see subscription options?”
Oddly when I launch Jtether with FoxFI on I can see the FoxFI network for literally 1 second, but not long enough to connect. This only happens when I use CDMA only. When I use LTE/CDMA it never shows up at all.
.
I’ve uncovered a lot of issues but I don’t know where to start troubleshooting. Do I start with SuperSU errors or can they be omitted? Do I start with FoxFI error troubleshooting? Maybe start with finding out why TrevE’s tether mod has errors but log file can’t be found? Maybe the root method I used wasn’t ‘deep’ enough? If so what method should I use? I thought this would be way easier but hours and hours later, here I am with no wifi tethering. I hope you guys can help.
Thnx in advance!
Use the odexed mk3 file from here. (You will need a custom recovery to install. )
http://forum.xda-developers.com/showthread.php?t=2224083
Sent from my iPhone using Tapatalk
dcharleyultra said:
Use the odexed mk3 file from here. (You will need a custom recovery to install. )
http://forum.xda-developers.com/showthread.php?t=2224083
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Thanks for the quick reply! What exactly is this file? Is it a new kernel? Or does it simply edit the configurations relating to tethering? Also can I go back to 100% stock after flashing it?
Also will this prevent me from being able to update the OS via Samsung push updates?
evo20110 said:
Thanks for the quick reply! What exactly is this file? Is it a new kernel? Or does it simply edit the configurations relating to tethering? Also can I go back to 100% stock after flashing it?
Click to expand...
Click to collapse
It is not new firmware. It's just a modified services.jar file. Since it's a hack, you will not be 100% stock after installing it. (You can get back to it by restoring the stock files (.jar and .odex files).
Sent from my iPhone using Tapatalk
dcharleyultra said:
It is not new firmware. It's just a modified services.jar file. Since it's a hack, you will not be 100% stock after installing it. (You can get back to it by restoring the stock files (.jar and .odex files).
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Awesome. Ok I installed CWM and I'm about to download the MK3 Odex file. Shouldn't be too hard to figure out how to "flash" it within the app. Wish me luck!
evo20110 said:
Awesome. Ok I installed CWM and I'm about to download the MK3 Odex file. Shouldn't be too hard to figure out how to "flash" it within the app. Wish me luck!
Click to expand...
Click to collapse
How did it go?
Sent from my iPhone using Tapatalk
dcharleyultra said:
How did it go?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Worked like a CHARM! Thanks so much for the help! You have no idea
http://download.chainfire.eu/631/CF-Root1/Root-Nexus-Player-fugu.zip
Thanks. Looks to have worked flawlessly.
Works great! Thanks!
Chainfire said:
http://download.chainfire.eu/631/CF-Root1/Root-Nexus-Player-fugu.zip
Click to expand...
Click to collapse
Works great. As a thank you I used my play credit from the NP Promo to upgrade to SuperSU Pro. hopefully you see that money!
Chainfire said:
http://download.chainfire.eu/631/CF-Root1/Root-Nexus-Player-fugu.zip
Click to expand...
Click to collapse
Thank you. Simplest root evar I will also buy SU Pro
Worked perfectly, of course. Thanks as always.
Just saw this today but had already used the other root method here to get it. Either way, thanks for all the hard work you do on everything
Chainfire said:
http://download.chainfire.eu/631/CF-Root1/Root-Nexus-Player-fugu.zip
Click to expand...
Click to collapse
Is this assured to work with both LRX21M and LRX21V?
Worked perfectly, and now StickMount is working too. Just played a video off USB in XBMC.
Does anyone know a way to remove the su app from showing in the leanback launcher. Can't find it in the settings anywhere.
Pardon my ignorance, but what does this do exactly? ...aside from the obvious "gives you root"...I mean how, what does it do to the system?
Boblank said:
Does anyone know a way to remove the su app from showing in the leanback launcher. Can't find it in the settings anywhere.
Click to expand...
Click to collapse
Well be in next version, if you set icon to invisible, it will also disappear from leanback launcher.
Zip attachment
volwrath said:
Thank you. Simplest root evar I will also buy SU Pro
Click to expand...
Click to collapse
Do you just download to phone or PC and put the extraction on the Nexus Player to gain root?
Boblank said:
Does anyone know a way to remove the su app from showing in the leanback launcher. Cant find it in the settings anywhere.
Click to expand...
Click to collapse
Are you referring to the launcher settings or SuperSU settings there should be an option in SuperSU settings to set the SuperSU icon to invisible.
I just happened to check my system today and had the OTA update from LRX21M to LRX21V waiting. I tried installing it but Recovery stopped halfway through the install with an Error. I got back into Android with a power-cycle, so things are fine, but it's still on 21M.
I'm guessing this was due to having rooted the device. Is there a proper way to remove SuperSU to allow for a system update? I see there are 3 different options for cleaning up; does it particularly matter which one I choose? I could just pick one and try it but I'm kind of curious what the differences are between the options. Anybody know?
Update: I tried the second and third cleanup options (new superuser app and full unroot) and neither got me into a state where the OTA was successful. So I just downloaded the factory image and flashed the system.img from it, then reapplied the original root process.
xBIGREDDx said:
Update: I tried the second and third cleanup options (new superuser app and full unroot) and neither got me into a state where the OTA was successful. So I just downloaded the factory image and flashed the system.img from it, then reapplied the original root process.
Click to expand...
Click to collapse
probably a full unroot and flashing the stock boot.img would fully unroot, I wonder when LRX22C (5.0.1) will hit the nexus player
The root is fundamental in all devices for many things, and thanks to Chainfire and others independent developers we can consider Android a semi-open platform. (semi-open because not all is open source)
We don't want Android like the Apple walled garden, but we are not even against the sale of the software, we just want a common garden in which the user can choose and is not obliged.
For example with the root, it was easier to start this project:
Nexus Player with a Full Version of Android Lollipop https://plus.google.com/103019026671039069038/posts/V5XaLxK3vN8
This is just the base rom with all hardware components working, on this base that is very usable, i want add many other options. like external usb webcam and mic, improving the audio part that have fixed volume and many other things useful for the use in TV.
Nexus Player is not just Android TV, but is the first Nexus device with an intel cpu. Is a milestone in the evolution of Android.
This is just the start and I am very open to sharing and collaboration on this project.
Thanks Chainfire for the root and for your "How-To SU" guidelines.
Out of interest will rooting prevent OTA updates from installing in the future?
Chainfire said:
Well be in next version, if you set icon to invisible, it will also disappear from leanback launcher.
Click to expand...
Click to collapse
I did this, despite the warning it gave me. Now although I still get permission dialogs etc, I can not run the main program to delete apps etc from SU access. Is there anyway to go back to the main screen? I went to the apps sections of the NP and unlike other apps it didnt have an open command.
To get it back do I need to uninstall and then re-CFroot?
Thanks. I should pay better attention to dialog boxes but its not a huge deal.
This thread is started to accommodate Q&A regarding CM13 by @TheStrix. Enjoy!
akhilkumarco007 said:
is dooze working? I opened battery optimisation list and turn it on for all apps but after i come back its getting restored to no apps anyone having similar issue"?
Click to expand...
Click to collapse
Yes, it didn't stick to app-optimization option. Regardless, it's still stable enough for daily use.
dtechgeek said:
I can't get root permission. Titanium backup is not able to get root permissions.
I have flashed SuperSU beta zip. In supersu app TB is shown to have root permissions.
WTH. There is no meaning without TB.
Click to expand...
Click to collapse
SuperSU itself is still WIP for Android M. Similarly, I couldn't get a working SuperSU without enabling the root option in the Developer Option. I ended up using native root option instead of SuperSU. After rooting, data and wifi may not working; just turn on the airplane mode for a while and turn it off, data and wifi will work again.
Upgrading to 7.1.1. kills your ability to use the old Network Signal Refresh trick to quickly enable your hotspot. The fix for this is now to just pop out your simcard, and when you stuff it back in, immediately activate your hotspot in settings. What I'm doing is just keeping the simcard "key" inbetween my phone and my case, so when I need to activate my hotspot it's a quick pop out pop in throw the switch. 5 seconds max from start to finish and I'm up and running.
I upgraded to 7.1.1. right away w/ out even looking at the forums and learned the hard way that they killed off the non-root method of tethering (Network Signal Refresh)
I believe they also killed of the airplane mode to tether trick as well as I had that down and now it isn't working for me at all.
Pop out the sim, shove it back in, flip the tether switch and your in business.
You may now hit the "Thanks" button lol :angel:
This trick isn't working for me...I'm able to turn on hotspot once I put the SIM card back in but as soon as LTE is about to pop up, it shuts off my hotspot. Sigh...had I only known, I wouldn't have updated..
You are a lifesaver!
---------- Post added at 11:48 AM ---------- Previous post was at 11:46 AM ----------
ninotorpedo said:
This trick isn't working for me...I'm able to turn on hotspot once I put the SIM card back in but as soon as LTE is about to pop up, it shuts off my hotspot. Sigh...had I only known, I wouldn't have updated..
Click to expand...
Click to collapse
It's a timing issue. I had trouble the first few tries too but I can confirm that it worked. Pop in Sim first and immediately activate hotspot.
Thread scrubbed clean.
This thread isn't about the definition of "unlimited data", this thread is intended to be a guide to fix an issue. If you dont find it useful just dont post? Remember to stay respectful to everyone on this site.
Thanks
Wolf
ninotorpedo said:
This trick isn't working for me...I'm able to turn on hotspot once I put the SIM card back in but as soon as LTE is about to pop up, it shuts off my hotspot. Sigh...had I only known, I wouldn't have updated..
Click to expand...
Click to collapse
Reboot your phone and try again. Pretty much w/ in less than half a second of snapping the SIM card back into place I hit the tether button and it turns on and stays on.
I can confirm this works. Hotspot has been running since yesterday.
Anyone find a software fix for this yet? Glad we have a solution, but would love to not have to pop my sim out all the time!
snickersicecream said:
Anyone find a software fix for this yet? Glad we have a solution, but would love to not have to pop my sim out all the time!
Click to expand...
Click to collapse
if rooted just do the build.prop edit
Work around
Go to the pdanet icon (bottom right) with your phone tethered to your computer,
left click on the icon and choose "Wifi Share (Beta)
another authentication (activation) window appears and will ask for a Wifi name and password
activate and your wifi network should be activated and accessible.
Hope this works for others.
I am using a Google Pixel (32gb) phone and laptop.
Verizon UDP
lucky_strike33 said:
if rooted just do the build.prop edit
Click to expand...
Click to collapse
Yeah, that's what I finally went ahead and did. Build.prop edit complete. Hotspot working flawlessly again.
New update - update?
The last update killed the network refresh workaround, does the newest update kill the SIM card trick? Scared to update.
Do you people not have a legal
How much ?
memillh said:
Yeah, that's what I finally went ahead and did. Build.prop edit complete. Hotspot working flawlessly again.
Click to expand...
Click to collapse
Can you provide a link with full instructions on how to do this?
With 6.0 I used to follow these rough instructions but they don't seem to be working anymore...
adb devices
adb reboot bootloader
fastboot boot twrp-2.8.7.0-bullhead.img
adb pull /system/build.prop
add following to build.prop with txteditor: net.tethering.noprovisioning=true
adb push build.prop /system/
adb shell chmod 644 /system/build.prop
adb shell settings put global tether_dun_required 0
adb reboot
garrettc134 said:
Can you provide a link with full instructions on how to do this?
With 6.0 I used to follow these rough instructions but they don't seem to be working anymore...
adb devices
adb reboot bootloader
fastboot boot twrp-2.8.7.0-bullhead.img
adb pull /system/build.prop
add following to build.prop with txteditor: net.tethering.noprovisioning=true
adb push build.prop /system/
adb shell chmod 644 /system/build.prop
adb shell settings put global tether_dun_required 0
adb reboot
Click to expand...
Click to collapse
So I rooted and it seemed to work. Wonder why it used to work without the root...
garrettc134 said:
So I rooted and it seemed to work. Wonder why it used to work without the root...
Click to expand...
Click to collapse
The kernel now had dm-verity that will revert any changes to /system that you make. Rooting disables dm-verity and allows modifications to /system to "stick."
I just got my Pixel. It's running 7.1.1 NMF26U.
Like many others, I want to bypass the check and get tethering hotsopt to work but I am afraid to do anything that might cause Android Pay to stop working.
I have been trying to get the SIM pop method to work without success. It does enable Hotspot and stay enabled. I can get computers to connect to the SSID. They do get a 192.168.43.x IP address. They can ping the 192.168.43.1 hotspot GW IP. However they cannot ping anything on the Internet nor do DNS lookups. No throughput to the Internet at all. The phone shows Hotspot running and it shows I have LTE signal. The Pixel itself has working Internet via LTE while Hotspot is on. I've also rebooted the Pixel and tried several more times with the same results.
Any suggestions on what I'm doing wrong?
Are there any ways to edit build.prop that does not involve doing something that would kill Android Pay?
Thanks.
DanTron said:
I just got my Pixel. It's running 7.1.1 NMF26U.
Like many others, I want to bypass the check and get tethering hotsopt to work but I am afraid to do anything that might cause Android Pay to stop working.
I have been trying to get the SIM pop method to work without success. It does enable Hotspot and stay enabled. I can get computers to connect to the SSID. They do get a 192.168.43.x IP address. They can ping the 192.168.43.1 hotspot GW IP. However they cannot ping anything on the Internet nor do DNS lookups. No throughput to the Internet at all. The phone shows Hotspot running and it shows I have LTE signal. The Pixel itself has working Internet via LTE while Hotspot is on. I've also rebooted the Pixel and tried several more times with the same results.
Any suggestions on what I'm doing wrong?
Are there any ways to edit build.prop that does not involve doing something that would kill Android Pay?
Thanks.
Click to expand...
Click to collapse
Are you running a VPN for adblocking without root? If so, turn it off while tethering. Just a guess.
mwalt2 said:
Are you running a VPN for adblocking without root? If so, turn it off while tethering. Just a guess.
Click to expand...
Click to collapse
No VPN. Basically fresh out of the box phone.
Having a problem as well, up until I got the Pixel I was able to use unlimited tethering on tmobile by adding ",dun" you the apn. This no longer works. Any workaround?
lucky_strike33 said:
if rooted just do the build.prop edit
Click to expand...
Click to collapse
Hi. Here you say to edit build.prop. I checked the whole thread but
How should I edit build.prop. What do I have to add or edit?
Inviato dal mio SM-N9005 utilizzando Tapatalk
Hi all,
Joining Team Pixel tomorrow after my debacle with the Huawei Mate 20 Pro and the green screen fiasco.
Just wondering if its still worth rooting the Pixel? If i do it i wanna do it straight away to save wiping my data again when unlocking the BL. My main reasons would be for Adaway, Removing the Nav Bar, Swift theme installer and Viper.
Most of these can be done via ADB now so is it still worth rooting?
Rooting this phone is pretty easy and it doesn't impact the updating process much if you know what you're doing, so I vote that it is definitely worth rooting.
I don't use a lot of root apps, but the two main ones are worth it to me. I use AdAway for ads (VPN ad blockers are slower and have several cons) and an app called Sa2ration to compensate for the screen's weak color.
I have everything working the way I want without any compromises. Very happy with my setup.
It's soooo easy to root, I'm not sure why anyone wouldn't. My main reason is viper 4 android, but adaway, pixel launcher mods (changes icons and has a system UI tuner), and sd maid pro having deeper access for cleanup as well.
I've always had an Android phone that has been able to be rooted. Adaway, V4A, Substratum, Sa2ration, Titanium Backup and removing the stock navigation buttons are the biggest things for me currently with the Pixel 3 XL.
I always recommend unlocking the bootloader right out of the box, even if you never plan to root. The sole reason for this is if at any point something goes awry and you end up in a bootloop or somehow end up soft bricked, with an unlocked bootloader you can be back up and running like new with a very quick flash-all script from the latest factory image on Google's support site. However, with a locked bootloader, if you find yourself in one of those bad situations, you're at the mercy of Google support to either get you a new device or go days without a phone while they try and fix it.
So, in my opinion, unlocking the bootloader is a no brainer on these phones, right from the get-go.
With that said, rooting is much more user preference. I found no reason to root my OnePlus 6. However, with the 3 XL my sole reason for rooting is to edit the build.prop to properly hide the nav bar at the system level, allowing me to use gesture controls without issue. You can use ADB commands to achieve this as well. But my experience in trying to hide the nav bar with ADB commands on this phone has caused some wonky things to happen, such as status bar notifications not going away and volume controls getting cut off when watching something in landscape mode. Rooting the phone and editing the build.prop was the only solution that worked for me to hide the nav bar without running into unforeseen issues.
If you are one to do other things like use Magisk modules and such, then rooting will be a no brainer for you. Also, as someone else mentioned, rooting this phone is the most straight forward/simple experience I've had rooting a phone in years.
Thanks guys thats it decided then. Is it best to OTA to november then root via twrp after ul bootloader.
Yeah nav bar is a pet hate of mine, I used to love LMT launcher, might try the OP gestures though on this one
Guitarfreak26 said:
Thanks guys thats it decided then. Is it best to OTA to november then root via twrp after ul bootloader.
Yeah nav bar is a pet hate of mine, I used to love LMT launcher, might try the OP gestures though on this one
Click to expand...
Click to collapse
Try this: [Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + by Homeboy76 do #4 then #8 if you want root. Also, Prerequisites has a link to download SDK Platform tools r28.0.1, if it needs updating.
gettinwicked said:
It's soooo easy to root, I'm not sure why anyone wouldn't. My main reason is viper 4 android, but adaway, pixel launcher mods (changes icons and has a system UI tuner), and sd maid pro having deeper access for cleanup as well.
Click to expand...
Click to collapse
I'm perfectly happy with the stock experience on this phone. I have no need for anything that requires root. I've rooted a lot of phones in the past, but there's something about this one that I just feel no need to do so. To me that says a lot for how far Google has come.
I'm getting my pixel 3 xl in a few hours today and I've been up all night watching pixel 3 xl videos. I was just about to post a question like this, but thanks to you I don't have to! The wonders of searching.
Anyways, I agree for adway and maybe even mods.
What bothers me is if I decide to use Google pay, Pokemon go or using my bank app, because I was told rooting can stop them from allowing me to use them.
I also want to do it out the box.
Also don't know about the new gesture stuff, so if I don't like it, I'd probably want to mod it.
Guitarfreak26 said:
Thanks guys thats it decided then. Is it best to OTA to november then root via twrp after ul bootloader.
Yeah nav bar is a pet hate of mine, I used to love LMT launcher, might try the OP gestures though on this one
Click to expand...
Click to collapse
That is exactly what I did with both a Pixel 3 and a Pixel 3 XL. Just don't do a permanent install of TWRP on the XL unless you want to lose your touch screen in TWRP with no way out of TWRP when it boots back in there. I ended up having to hold the power button down until I forced the device off. Booted back into bootloader and ran the temp TWRP (which strangely works fine for touch) and then ran Magisk again to get back to the OS. Strange, the regukar Pixel 3 took permanent TWRP after Magisk, rebooted to TWRP was still able to use touch commands and ran Magisk again to get back to the proper boot image. I can even go to TWRP normally, and touch is functioning normally. I'll have to write the stock boot image when I get home today so I can get back to stock recovery until TWRP for XL is fixed.
GunToYoMouth123 said:
What bothers me is if I decide to use Google pay, Pokemon go or using my bank app, because I was told rooting can stop them from allowing me to use them.
Click to expand...
Click to collapse
Magisk has a hide feature built-in that has been working for me. I have several apps that normally detect root and Magisk blocks their detection 100%. My banking app works (normally detects root) and Google Pay is working just fine with Magisk hide.
I've been learning to live with stock ROMS, BUT, I still need my root. Adaway, TiBu, Substratum, LMT Launcher. I can't give 'em up.
Sevael said:
Magisk has a hide feature built-in that has been working for me. I have several apps that normally detect root and Magisk blocks their detection 100%. My banking app works (normally detects root) and Google Pay is working just fine with Magisk hide.
Click to expand...
Click to collapse
Ohh okay, thanks for that input !
My pixel 3 XL just got here !
Going to see what's up !
Sevael said:
Magisk has a hide feature built-in that has been working for me. I have several apps that normally detect root and Magisk blocks their detection 100%. My banking app works (normally detects root) and Google Pay is working just fine with Magisk hide.
Click to expand...
Click to collapse
My banking apps work fine but i can't get google pay to work. Even with magisk hide still not work. "This account already exists on your device" wheni try to sign in
J32A said:
My banking apps work fine but i can't get google pay to work. Even with magisk hide still not work. "This account already exists on your device" wheni try to sign in
Click to expand...
Click to collapse
Not sure, I haven't encountered this.
I find that when an app has detected root, sometimes they retain this information even through reboots. In those situations, clearing all data from the app often fixes it.
Something else to be aware of is that if you have a widget for an app that detects root, it's not uncommon for the widget to load before Magisk finishes loading and hiding after a reboot. On my Pixel 2 I had one app where after each reboot it would load first (due to a widget being present) and would detect root and block itself. I had to remove the widget and just just use a normal shortcut to the app instead, as I would never manually open it before Magisk finished loading up fully.
I just got pixel 2 xl this thing is a beast came with 5g and unlimted data when I got tablets for kids literally no download it's all instant. every phone I have had b4 is rooted most still work. My question will I improve anything by rooting with this speed? I don't think a VPN blckr would slow it down. How hard is it to reverse root if I need warranty? Is this speed the 5g or just Google built a great product?
sn0warmy said:
I always recommend unlocking the bootloader right out of the box, even if you never plan to root. The sole reason for this is if at any point something goes awry and you end up in a bootloop or somehow end up soft bricked, with an unlocked bootloader you can be back up and running like new with a very quick flash-all script from the latest factory image on Google's support site. However, with a locked bootloader, if you find yourself in one of those bad situations, you're at the mercy of Google support to either get you a new device or go days without a phone while they try and fix it.
<snip>
Click to expand...
Click to collapse
Unlocking the bl is problematic in some instances. Detection for apps and things like that. Why would you just not check off the "allow the bootloader to be unlocked" option in OEM unlocking? Then you get to fastboot and can unlock if needed without actually being unlocked and compromised.
bobby janow said:
Unlocking the bl is problematic in some instances. Detection for apps and things like that. Why would you just not check off the "allow the bootloader to be unlocked" option in OEM unlocking? Then you get to fastboot and can unlock if needed without actually being unlocked and compromised.
Click to expand...
Click to collapse
It is my understanding, and correct me if I'm wrong, that apps recognize root but not bootloader locked status. As long as you don't root, you should be fine with all apps.
Sent from my Pixel 3 XL
Eudeferrer said:
It is my understanding, and correct me if I'm wrong, that apps recognize root but not bootloader locked status. As long as you don't root, you should be fine with all apps.
Click to expand...
Click to collapse
No I don't think so. If you bl unlock it will be detected. There are kernels that will fix that but stock unlocked is a trigger.
Eudeferrer said:
It is my understanding, and correct me if I'm wrong, that apps recognize root but not bootloader locked status. As long as you don't root, you should be fine with all apps.
Click to expand...
Click to collapse
Yes. As @bobby janow said, some apps treat bootloader unlock as having root. DirecTV Now is a prime example. Also, Netflix won't even appear in the app store and would have to be sideloaded. Although, all of those can be worked around it is sometimes a pain.