Made a new thread as seems this is demanded option. Some people already checked this and looks like this works. I can't check right now but if you want, please check and post if it works for you.
Restriction is phone number country code based, can be bypassed. Also looks like its developers left setting to disable country checks at all. To do that, you just need to change android setting 'pixel.oslo.allowed_override' to '1' or 'true'.
Connect Pixel 4 with developer mode and execute command in adb shell:
Code:
adb shell setprop pixel.oslo.allowed_override true
or
Code:
adb shell "setprop persist.pixel.oslo.allowed_override true; setprop ctl.restart zygote"
or edit system/build.prop with some app (eg. MagiskHide Props Config)
You need root to do this.
Also there is Xposed Module in xposed manager to do this automatically called "EnableSoliOnPixel4", here's thread about it https://forum.xda-developers.com/pixel-4-xl/themes/success-enable-soli-china-t3994917
Do I need root permission to execute this command via adb? Thanks
Sent from my Google Pixel 2 using XDA Labs
Monazite said:
Do I need root permission to execute this command via adb? Thanks
Sent from my Google Pixel 2 using XDA Labs
Click to expand...
Click to collapse
Yes, without root you can’t edit system props
Eugnis said:
Yes, without root you can’t edit system props
Click to expand...
Click to collapse
getting failed to set property reply. any idea what i'm doing wrong?
Does it mean that I still can use soli in any country even that country doesn't support for it ?
For example, If I traveled to Japan one day, I still can use soli after enable soli by this xposed module ?
Kris
omar5099 said:
getting failed to set property reply. any idea what i'm doing wrong?
Click to expand...
Click to collapse
Looks like ADB not received root rights on phone. To check this use
Code:
adb shell su
if you receive response ' su: not found ' then you should enable root access for adb on phone (with supersu or similar)
Also you can set this prop with MagiskHide Props Config from phone if you used Magisk to root it
Kris Chen said:
Does it mean that I still can use soli in any country even that country doesn't support for it ?
For example, If I traveled to Japan one day, I still can use soli after enable soli by this xposed module ?
Kris
Click to expand...
Click to collapse
Yes, this setting just disable country check at all. So Soli will work worldwide
Eugnis said:
Looks like ADB not received root rights on phone. To check this use
Code:
adb shell su
if you receive response ' su: not found ' then you should enable root access for adb on phone (with supersu or similar)
Also you can set this prop with MagiskHide Props Config from phone if you used Magisk to root it
Click to expand...
Click to collapse
I've obtained root for ADB shell via this command, however none of those 2 original adb lines are working. I'm still getting the failed to set property reply.
Any help appreciated...
Now I gotta root my phone and lose automatic updates just to be able to use it normally. Thanks a lot, Google!! _l_
You will still get automatic updates, you can root your phone, set the persistent property, and remove the root. Should persist across updates.
Bogega said:
I've obtained root for ADB shell via this command, however none of those 2 original adb lines are working. I'm still getting the failed to set property reply.
Any help appreciated...
Click to expand...
Click to collapse
yes same here, any1 got this to work ? thanks
Pixeling said:
You will still get automatic updates, you can root your phone, set the persistent property, and remove the root. Should persist across updates.
Click to expand...
Click to collapse
So if I set the property and then unroot, it will persist even after OTA updates? No need to root again and set it again after every OTA?
aco.falc said:
So if I set the property and then unroot, it will persist even after OTA updates? No need to root again and set it again after every OTA?
Click to expand...
Click to collapse
That's what I suspect since the property lives in /data which is not changed/erased after OTA. I've not tried it myself however that's probably what I will do when I get the phone.
aco.falc said:
So if I set the property and then unroot, it will persist even after OTA updates? No need to root again and set it again after every OTA?
Click to expand...
Click to collapse
Performing some more reading on the subject, there is a possibility that unlocking the bootloader by itself trips safetynet which in turn prevents OTA. I can't know whether this is true for sure, but in this case keeping Magisk root shall hide that and let you download the OTA.
Before applying the OTA you should use magisk to restore the boot.img, let the OTA install, and then let Magisk install itself to the other inactive flash slot where the OTA is. That will make sure that root is kept intact post update and keep hiding that the bootloader is unlocked. Can anyone confirm?
WORKED
hello, i can confirm its working, steps to follow :
when u flash the magisk_patched image the phone wont boot at first, so u have to flash the boot.img then reflash the magisk_patched.
then the phone will boot normally.
after that, download terminal from play store, and type in it : SU , this will ask u for root permissions
then u need to type these 3 commands within the terminal :
setprop pixel.oslo.allowed_override true
setprop persist.pixel.oslo.allowed_override true
setprop ctl.restart zygote
then motion sense will turn on.
enjoy!
if u need detailed steps about the whole thing let me know
sta3b said:
hello, i can confirm its working, steps to follow :
when u flash the magisk_patched image the phone wont boot at first, so u have to flash the boot.img then reflash the magisk_patched.
then the phone will boot normally.
after that, download terminal from play store, and type in it : SU , this will ask u for root permissions
then u need to type these 3 commands within the terminal :
setprop pixel.oslo.allowed_override true
setprop persist.pixel.oslo.allowed_override true
setprop ctl.restart zygote
then motion sense will turn on.
enjoy!
if u need detailed steps about the whole thing let me know
Click to expand...
Click to collapse
Can confirm that typing these commands in terminal did the trick. Used 'Terminal Emulator for Android' app from playstore.
And I skipped first steps (flashing boot.img etc) as I'm already rooted.
Thanks!
Bogega said:
Can confirm that typing these commands in terminal did the trick. Used 'Terminal Emulator for Android' app from playstore.
And I skipped first steps (flashing boot.img etc) as I'm already rooted.
Thanks!
Click to expand...
Click to collapse
It works for me! Thank you!
Do I need to do this all over again when I reboot my phone?
It seems that when rebooting the phone the soli is disabled again, can someone confirm?
Also I read here something about unrooting? can I really root and unroot everytime I want and retain OTA updates?
chris111111 said:
It works for me! Thank you!
Do I need to do this all over again when I reboot my phone?
Click to expand...
Click to collapse
Soli doesn't survive reboots if you're using this method.
There's a magisk module (non Xposed) which solves this though (https://forum.xda-developers.com/pixel-4-xl/themes/enable-soli-contries-magisk-module-t3997035)
wolfgangam31 said:
It seems that when rebooting the phone the soli is disabled again, can someone confirm?
Also I read here something about unrooting? can I really root and unroot everytime I want and retain OTA updates?
Click to expand...
Click to collapse
correct, rebooting the phone will cause SOLI to get disabled, you need to re-enter the commands in the terminal to get it to work again
Related
So, by going into the settings menu of the FTV and toggling the ADB Debug flag, this allows for installing via a push from ADB.
The text that is displayed when changing this value also says that by enabling the setting, it allows for package installs from unknown sources.
Is this not quite the case though?
Using ES File Manager, when selecting an apk package located in the downloads folder on the device, the message shown in the attached screenshot appears.
Since there's no way to do so from the front-end, I am assuming that we will need root to change the flag to truly allow installing from any source?
Any possible way to do this without root?
mkhopper said:
So, by going into the settings menu of the FTV and toggling the ADB Debug flag, this allows for installing via a push from ADB.
The text that is displayed when changing this value also says that by enabling the setting, it allows for package installs from unknown sources.
Is this not quite the case though?
Using ES File Manager, when selecting an apk package located in the downloads folder on the device, the message shown in the attached screenshot appears.
Since there's no way to do so from the front-end, I am assuming that we will need root to change the flag to truly allow installing from any source?
Any possible way to do this without root?
Click to expand...
Click to collapse
Yeah, this isn't currently possible for the public. There is a root exploit(s) already developed but they have not been released yet. The developer, jcase, said he will release an exploit on the same day the upcoming Fire TV update is pushed (the exploit will not be compatible with the update so if you want it you'll need to follow the instructions in the other thread for blocking OTA updates).
mkhopper said:
Any possible way to do this without root?
Click to expand...
Click to collapse
Are you having issues with ADB? We can probably help you get those resolved.
Chahk said:
Are you having issues with ADB? We can probably help you get those resolved.
Click to expand...
Click to collapse
Thanks, but no. I use the automatic tool to push packages with no problems. I was just looking for other methods of package installation that could be done directly while on the FTV.
mkhopper said:
Thanks, but no. I use the automatic tool to push packages with no problems. I was just looking for other methods of package installation that could be done directly while on the FTV.
Click to expand...
Click to collapse
Not at this time. Amazon disabled side-loading of APKs from the device itself. Root would be the only way to get around that.
mkhopper said:
Thanks, but no. I use the automatic tool to push packages with no problems. I was just looking for other methods of package installation that could be done directly while on the FTV.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2715315
Sent from my MZ617 using XDA Premium 4 mobile app
Kramar111 said:
http://forum.xda-developers.com/showthread.php?t=2715315
Click to expand...
Click to collapse
several days ago it occurred to me to alternatively use sshd for terminal access, because:
-a) I feel a little unsafe leaving adb wifi enabled all the time (ok it's only a small thing to turn it on and off, but still) - and for security reasons there is no way to enable/disable it programmatically e.g. from a script/shell/terminal/app (well theoretically this is not exactly true, but practically it is)
-2) some people (i.e. me) would like to do shell/terminal remotely sometimes, rather than on the AFTV (and other people don't have/want a keyboard)
ssh access makes a great alternative to Term.apk, but the problem is:
- Term.apk and/or (pick your favorite android ssh server) don't have permission to run e.g. "pm install foo.apk" - it will fail. (btw 'pm' is a great command, take a look sometime at all the options. it shares a lot of functions as the adb command itself. 'am' is another fun command...)
- so, the hilarious workaround of enabling adb wifi, "adb connect", and then finally "adb shell" or "adb install" etc., is still required. (b/c the adb user is in the 'shell' group, among others - giving it permission to run /system/bin/pm) - oh well.
for random reference:
Code:
127|[email protected]:/ $ id
uid=2000(shell) gid=2000(shell) groups=1004(input),1007(log),1009(mount),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats)
[email protected]:/ $ exit
[email protected]:/ $ id
uid=10009(app_9) gid=10009(app_9) groups=1015(sdcard_rw),1028,3003(inet),50009(app_40009)
(also note it appears the adb shell user might possibly have 'mount' abilities, but since the /dev/block/sd* nodes permissions' are really locked up, who knows...)
This guide presupposes that you have Supersu installed as systemless, and that you have access to adb.
This will bypass provisioning checks for builtin tether app. The modded apk should work with future updates without touching /system at all.
Installation
Method 1 - Manual install
Download the attached CarrierEntitlement apk.
If you have su.img su:
Code:
adb push CarrierEntitlement.apk /sdcard/CarrierEntitlement.apk
adb shell
su
mkdir /su/CarrierEntitlement
cp /sdcard/CarrierEntitlement.apk /su/CarrierEntitlement/CarrierEntitlement.apk
chmod 644 /su/CarrierEntitlement/CarrierEntitlement.apk
echo "mount -o bind /su/CarrierEntitlement/CarrierEntitlement.apk /system/priv-app/CarrierEntitlement/CarrierEntitlement.apk" > /su/su.d/05TetherMod
chmod +x /su/su.d/05TetherMod
reboot
If you have sbin su (Android 8.0+)
Code:
adb push CarrierEntitlement.apk /sdcard/CarrierEntitlement.apk
adb shell
su
mkdir /sbin/supersu/CarrierEntitlement
cp /sdcard/CarrierEntitlement.apk /sbin/supersu/CarrierEntitlement/CarrierEntitlement.apk
chmod 644 /sbin/supersu/CarrierEntitlement/CarrierEntitlement.apk
echo "mount -o bind /sbin/supersu/CarrierEntitlement/CarrierEntitlement.apk /system/priv-app/CarrierEntitlement/CarrierEntitlement.apk" > /sbin/supersu/su.d/05TetherMod
chmod +x /sbin/supersu/su.d/05TetherMod
reboot
Method 2 - Flashable Zip (su.img only)
Code:
1. Download attached zip.
2. Flash in TWRP (Last tested in alpha 2)
Information
This mod is accomplished by replacing the following function:
Code:
.method public static getCarrierEntitlement(Landroid/content/Context;)Lcom/google/android/carrierentitlement/CarrierEntitlement;
.registers 2
.param p0, "context" # Landroid/content/Context;
.prologue
.line 56
const/4 v0, 0x0
return-object v0
.end method
NOTE: Post install
You may need to edit your APNs to get tethering working for your carrier.
On sprint, where editing APNs is disabled, the fix is here: Sprint Fix
Be sure to thank @Builtfordtough1 for all his help in diagnosing the issue at this post: The Solution!
Be sure to thank sb1893 for sbin su instructions.
Worked Perfectly
This worked perfectly. Fantastic job!
So I am on stock with unlocked bootloader, twrp installed, and rooted with SuperSU. Because this is an apk file, do i just download onto the phone and install as I would with any other .apk file?
coolhandz said:
So I am on stock with unlocked bootloader, twrp installed, and rooted with SuperSU. Because this is an apk file, do i just download onto the phone and install as I would with any other .apk file?
Click to expand...
Click to collapse
The directions clearly state in adb speak that you need to create a directory for the file. Move to said directory, change permissions, etc etc. Nothing about installing via the apk.
pcriz said:
The directions clearly state in adb speak that you need to create a directory for the file. Move to said directory, change permissions, etc etc. Nothing about installing via the apk.
Click to expand...
Click to collapse
well, i can follow basic commands in minimal adb & fastboot. I think this may be above me unless there is an idiots' guide.
coolhandz said:
well, i can follow basic commands in minimal adb & fastboot. I think this may be above me unless there is an idiots' guide.
Click to expand...
Click to collapse
Do you have access to adb? They are pretty straight forward. May need to view them on the website but if you are using an app it may throw the word wrap off and make the commands seem confusing. The directions are pretty word for word.
pcriz said:
Do you have access to adb? They are pretty straight forward. May need to view them actually on the website but if you are using an app it may throw the word wrap off and make the commands seem confusing. The directs are pretty word for word.
Click to expand...
Click to collapse
If by adb you mean minimal adb & fastboot, then yes I have access and I could probably brave it.
coolhandz said:
If by adb you mean minimal adb & fastboot, then yes I have access and I could probably brave it.
Click to expand...
Click to collapse
I wouldn't suggest doing it how I did it but I downloaded the file to my phone. I created the directory using a root enabled file browser (see mkdir command {make directory}). I even used the file properties option in solid explorer to change the permissions (see chmod 644). Every other command I did on the phone from a terminal emulator. Just had to ignore the adb shell command because I am actually doing them on the device and not through a shell on my computer.
pcriz said:
I wouldn't suggest doing it how I did it but I downloaded the file to my phone. I created the directory using a root enabled file browser (see mkdir command {make directory}). I even used the file properties option in solid explorer to change the permissions (see chmod 644). Every other command I did on the phone from a terminal emulator. Just had to ignore the adb shell command because I am actually doing them on the device and not through a shell on my computer.
Click to expand...
Click to collapse
yeah, all that is definitely outside of my comfort zone, but thank you for the info.
Can you normally update your device with OTA-updates like a un-rooted device, without flashfire or connect to your computer?
Is there an advantage to doing this over adding "net.tethering.noprovisioning=true" to the build.prop file?
airmaxx23 said:
Is there an advantage to doing this over adding "net.tethering.noprovisioning=true" to the build.prop file?
Click to expand...
Click to collapse
This mod is systemless, and should survive OTAs. That mod changes the build.prop on the system partition, which could prevent taking OTAs.
njeri123 said:
Can you normally update your device with OTA-updates like a un-rooted device, without flashfire or connect to your computer?
Click to expand...
Click to collapse
Any modification to the boot image *should* prevent OTAs from working at all. However, you can flash back to stock boot images, and take OTAs as long as you have not modified /system, which this mod does not do.
Furthermore, as long as you don't wipe /data/ this mod will live in su.img and survive when you flash newer system software.
Fenny said:
This mod is systemless, and should survive OTAs. That mod changes the build.prop on the system partition, which could prevent taking OTAs.
Any modification to the boot image *should* prevent OTAs from working at all. However, you can flash back to stock boot images, and take OTAs as long as you have not modified /system, which this mod does not do.
Furthermore, as long as you don't wipe /data/ this mod will live in su.img and survive when you flash newer system software.
Click to expand...
Click to collapse
Thanks for the explanation, I removed the build.prop line and used this method and it's working fine. Thank you.
@Fenny
Thank you so much for putting this into a .zip file. It is greatly appreciated!
is there a non root method to bypass the checks? i dont plan on unlocking or rooting since i use android pay...
ddarvish said:
is there a non root method to bypass the checks? i dont plan on unlocking or rooting since i use android pay...
Click to expand...
Click to collapse
I also use Android pay, so I have two boot images ready to fastboot or flash. I have a boot image with root, and a boot image without root running a kernel that hides the bootloader unlocked flag.
So, the way I handle this, I flash the unrooted (bootloader flag hidden) image as my daily driver kernel, this passes safetynet, and allows me to use Android pay.
I make a backup of that boot image. Then, I install TWRP, my custom kernel, and SuperSU. I make a backup of that image as well.
So I have two backed up boot images:
rooted.img
HideBLUnlock.img
I flash HideBLUnlock.img to boot a, and boot b, safetynet passes.
Whenever I need to tether I have my computer with me, so I "fastboot boot rooted.img" which leaves me rooted until my next reboot.
Depending on your usage you might want to reverse that.
All my mods get stored in su.img, so switching out the boot images is all I need to have the best of both worlds.
Is it possible to fastboot boot twrp and flash the zip without being rooted or having twrp actually installed? O unlocked my bootloader but that's been it
Ocelot13 said:
Is it possible to fastboot boot twrp and flash the zip without being rooted or having twrp actually installed? O unlocked my bootloader but that's been it
Click to expand...
Click to collapse
You can use the fastboot twrp image to install this mod but you MUST have SuperSu. I have basic validation to check that in my update.zip. If you don't have a su.img in /cache or /data, this mod cannot be installed.
Flashed via TWRP and now i finally have a fully functioning hotspot!!
Fenny said:
I also use Android pay, so I have two boot images ready to fastboot or flash. I have a boot image with root, and a boot image without root running a kernel that hides the bootloader unlocked flag.
So, the way I handle this, I flash the unrooted (bootloader flag hidden) image as my daily driver kernel, this passes safetynet, and allows me to use Android pay.
I make a backup of that boot image. Then, I install TWRP, my custom kernel, and SuperSU. I make a backup of that image as well.
So I have two backed up boot images:
rooted.img
HideBLUnlock.img
I flash HideBLUnlock.img to boot a, and boot b, safetynet passes.
Whenever I need to tether I have my computer with me, so I "fastboot boot rooted.img" which leaves me rooted until my next reboot.
Depending on your usage you might want to reverse that.
All my mods get stored in su.img, so switching out the boot images is all I need to have the best of both worlds.
Click to expand...
Click to collapse
This is facinating, do you ever think where we can use boot a and boot b in a multiboot like fashion so that when you turn on the device you can choose what to boot?
Anyone have success pushing a system file and having it stick after reboot WITHOUT root? I haven't been successful to have it stick...
808phoneaddict said:
Anyone have success pushing a system file and having it stick after reboot WITHOUT root? I haven't been successful to have it stick...
Click to expand...
Click to collapse
Not sure if it will work, but have you tried it as su in adb?
>adb shell
>su
#
JimSmith94 said:
Not sure if it will work, but have you tried it as su in adb?
>adb shell
>su
#
Click to expand...
Click to collapse
Yeah I tried it didn't recognize su...I'll try again later
808phoneaddict said:
Yeah I tried it didn't recognize su...I'll try again later
Click to expand...
Click to collapse
Sounds like you need to figure out why su isn't working anyway. You might need to update your adb.
JimSmith94 said:
Sounds like you need to figure out why su isn't working anyway. You might need to update your adb.
Click to expand...
Click to collapse
I updated that...hmm otherwise it should be working? Would I need to do command prompt from another window?
If you have root installed and reboot to recovery, then "adb shell" should get you a # prompt.
If it does, then you're already ADB with root.
If you get $ prompt then you don't have root.
I don't think you can push system files without root?
You certainly can't "adb root" without root. That's for sure.
808phoneaddict said:
I updated that...hmm otherwise it should be working? Would I need to do command prompt from another window?
Click to expand...
Click to collapse
I just tried it on my rooted phone and "su" asks for root privileges on the phone, so that won't work, sorry.
JimSmith94 said:
I just tried it on my rooted phone and "su" asks for root privileges on the phone, so that won't work, sorry.
Click to expand...
Click to collapse
You did it in recovery mode? I know u can try to mount as rw in recovery...could U try that and see what happens?
808phoneaddict said:
You did it in recovery mode? I know u can try to mount as rw in recovery...could U try that and see what happens?
Click to expand...
Click to collapse
As I said, my phone is rooted, so of course it would work in recovery for me. Assuming you don't have TWRP already installed, you could try booting into TWRP with "fastboot boot <TWRP img file name>" and see if you can mount system and copy your system file with its file manager.
JimSmith94 said:
As I said, my phone is rooted, so of course it would work in recovery for me. Assuming you don't have TWRP already installed, you could try booting into TWRP with "fastboot boot <TWRP img file name>" and see if you can mount system and copy your system file with its file manager.
Click to expand...
Click to collapse
I actually booted to twrp and change the mount to rw, then I pushed the hosts file successfully (it says 100%) but when I boot up it doesn't work, not sure if I need to prove the old one maybe? Or does having the boot slots make a difference? Am I pushing to the wrong place?
808phoneaddict said:
I actually booted to twrp and change the mount to rw, then I pushed the hosts file successfully (it says 100%) but when I boot up it doesn't work, not sure if I need to prove the old one maybe? Or does having the boot slots make a difference? Am I pushing to the wrong place?
Click to expand...
Click to collapse
Sorry, you'll have to find someone else to help, or just go ahead and root it. You can probably unroot it after you have done your copy, but I don't know why you would bother.
I have always rooted my phones, so I haven't done what you're trying to do. Plus I don't even have my Pixel XL yet, so I don't know anything about the boot slots yet. Over and out!
JimSmith94 said:
Sorry, you'll have to find someone else to help, or just go ahead and root it. You can probably unroot it after you have done your copy, but I don't know why you would bother.
I have always rooted my phones, so I haven't done what you're trying to do. Plus I don't even have my Pixel XL yet, so I don't know anything about the boot slots yet. Over and out!
Click to expand...
Click to collapse
O yeah I rooted, was rooted for a while but I ran into the data drain that others are reporting when there is an OTA update...knowing that December is upon us I was trying to unroot but push modified hosts file so I wouldn't get ads. Honestly, if it wasn't for the ads, I have no problem with a stock pixel xl...there hasn't been much development for it just yet, understandable since it's so new...
Hi, I always ran xposed since getting my op3. But since taking the plunge for 7.1 are there any apps that has these features without xposed.
1- download progress bar,
2- hide ongoing notifications in status bar
Also any app that can set rotation on a per app basis
teostar said:
Also any app that can set rotation on a per app basis
Click to expand...
Click to collapse
Tasker
Sent from my OnePlus3 using XDA Labs
teostar said:
Also any app that can set rotation on a per app basis
Click to expand...
Click to collapse
I use Ultimate Rotation Control for this. Works well.
https://play.google.com/store/apps/details?id=nl.fameit.rotate&hl=en
Prattham said:
Tasker
Click to expand...
Click to collapse
I tried Tasker. But had an issue with it saying I don't have root.
teostar said:
Hi, I always ran xposed since getting my op3. But since taking the plunge for 7.1 are there any apps that has these features without xposed.
1- download progress bar,
2- hide ongoing notifications in status bar
Click to expand...
Click to collapse
Any suggestions on these?
Can you elaborate a bit? I may be able to help you. What were you trying to do that needed root?
Some Tasker tasks require root if you need to run them through Secure Settings, which is kind of a companion app for Tasker for changing certain system settings. You may be able to set up a profile without requiring root for what you want to do.
Redjax said:
Can you elaborate a bit? I may be able to help you. What were you trying to do that needed root?
Some Tasker tasks require root if you need to run them through Secure Settings, which is kind of a companion app for Tasker for changing certain system settings. You may be able to set up a profile without requiring root for what you want to do.
Click to expand...
Click to collapse
I was attempting to setup a scheduled airplane mode. Which needed secure settings, but it's was saying I needed root( which I already have).
teostar said:
I was attempting to setup a scheduled airplane mode. Which needed secure settings, but it's was saying I needed root( which I already have).
Click to expand...
Click to collapse
Do you have systemless root installed? Secure settings doesn't work with systemless root. If you have systemless root, then by doing this in terminal will make secure settings recognize root:
su
mount -o remount,rw /system
touch /system/bin/su
mount -o remount,ro /system
reboot
If you don't have systemless root then I would test remounting system partition with read/write permissions and then re-setting Secure settings again.
Edit: you can use any terminal application from Google Play
Squabl said:
Do you have systemless root installed? Secure settings doesn't work with systemless root. If you have systemless root, then by doing this in terminal will make secure settings recognize root:
su
mount -o remount,rw /system
touch /system/bin/su
mount -o remount,ro /system
reboot
If you don't have systemless root then I would test remounting system partition with read/write permissions and then re-setting Secure settings again.
Edit: you can use any terminal application from Google Play
Click to expand...
Click to collapse
Thanx I'll try this a lil later. To be honest I have no idea if I have systemless root or not I just flash the superuser 2.78 s5 whether it's systemless or not I don't know.
teostar said:
Thanx I'll try this a lil later. To be honest I have no idea if I have systemless root or not I just flash the superuser 2.78 s5 whether it's systemless or not I don't know.
Click to expand...
Click to collapse
It's systemless.
Squabl said:
Do you have systemless root installed? Secure settings doesn't work with systemless root. If you have systemless root, then by doing this in terminal will make secure settings recognize root:
su
mount -o remount,rw /system
touch /system/bin/su
mount -o remount,ro /system
reboot
If you don't have systemless root then I would test remounting system partition with read/write permissions and then re-setting Secure settings again.
Edit: you can use any terminal application from Google Play
Click to expand...
Click to collapse
Gr8 it worked. Thanks again :good:
teostar said:
Thanx I'll try this a lil later. To be honest I have no idea if I have systemless root or not I just flash the superuser 2.78 s5 whether it's systemless or not I don't know.
Click to expand...
Click to collapse
Hey, check out phhSuperuser, and Magisk. It's easy systemless root, no ADB commands or anything
Redjax said:
Hey, check out phhSuperuser, and Magisk. It's easy systemless root, no ADB commands or anything
Click to expand...
Click to collapse
I took a look at that thread and its out of my league for now. #babysteps I just got this, my 1st android device in October.
teostar said:
I took a look at that thread and its out of my league for now. #babysteps I just got this, my 1st android device in October.
Click to expand...
Click to collapse
I'm sorry, just saw this post. Magisk is very easy to install. The thread has a lot of information, but it's as easy as downloading the zip for Magisk and phh superuser, flashing them, and installing the apk files. Then you open the Magisk manager app and follow the steps in the thread! I installed it on my first try, and I agree, it seems complicated...But it works great and isn't hard at all to install if you've flashed things like SuperSU before! It's basically the same process when I'm not on mobile, I may reply with a short guide that follows the steps I took to get it working.
teostar said:
Hi, I always ran xposed since getting my op3. But since taking the plunge for 7.1 are there any apps that has these features without xposed.
1- download progress bar,
2- hide ongoing notifications in status bar
Click to expand...
Click to collapse
1. There's a module called Flat Style Bar Indicators that might help with download progress but it shows just the percentage not a bar.
http://repo.xposed.info/module/com.bocharov.xposed.fsbi
2. For notifications there's a great module called Notify Clean, it can do what you wan an much much more.
http://repo.xposed.info/module/de.defim.apk.notifyclean
I also advise to use a module called UnbelovedHosts, it's an ad blocker for xposed that's much more effective than any other because it just loads it on boot and doesn't need to run in the background.
http://repo.xposed.info/module/de.defim.apk.unbelovedhosts
Sent from my SM-G903F using XDA Labs
MegaArthur said:
1. There's a module called Flat Style Bar Indicators that might help with download progress but it shows just the percentage not a bar.
http://repo.xposed.info/module/com.bocharov.xposed.fsbi
2. For notifications there's a great module called Notify Clean, it can do what you wan an much much more.
http://repo.xposed.info/module/de.defim.apk.notifyclean
I also advise to use a module called UnbelovedHosts, it's an ad blocker for xposed that's much more effective than any other because it just loads it on boot and doesn't need to run in the background.
http://repo.xposed.info/module/de.defim.apk.unbelovedhosts
Click to expand...
Click to collapse
Thanks for the suggestions. But I was looking for regular apps not xposed since xposed doesn't work for nougat just yet.
An app or a module that disables vibration on successful fingerprint authentication? I have nougat and I can't have xposed...
teostar said:
Thanks for the suggestions. But I was looking for regular apps not xposed since xposed doesn't work for nougat just yet.
Click to expand...
Click to collapse
Checkout Download Progress++ in Play Store. It is by the same Dev as GB. It doesn't even need root leave alone Xposed. Checkout this post also: https://forum.xda-developers.com/showpost.php?p=71480102&postcount=293
I am using it and works wonderfully.
tnsmani said:
Checkout Download Progress++ in Play Store. It is by the same Dev as GB. It doesn't even need root leave alone Xposed. Checkout this post also: https://forum.xda-developers.com/showpost.php?p=71480102&postcount=293
I am using it and works wonderfully.
Click to expand...
Click to collapse
Seems it's not available in my country. Thanks. I'll try a VPN tomorrow.
I want to unlock LTE on my phone.
Anyone know how to enable it?
deltadiesel said:
I want to unlock LTE on my phone.
Anyone know how to enable it?
Click to expand...
Click to collapse
Check out this link: https://forum.xda-developers.com/g4/general/guide-enabling-lte-bands-t3137818
if you haven't already.
sdembiske said:
Check out this link: https://forum.xda-developers.com/g4/general/guide-enabling-lte-bands-t3137818
if you haven't already.
Click to expand...
Click to collapse
It says permission denied
I am rooted.
Whats the problem?
Tried that link can't get passed permission denied
What SuperSU everyone using I'm still on 2.,82 says I'm rooted but maybe features are disabled
deltadiesel said:
It says permission denied
I am rooted.
Whats the problem?
Tried that link can't get passed permission denied
Click to expand...
Click to collapse
If you're referring to the link above that I posted, works fine for me. Maybe security setting in your browser - suggest you try looking at the security settings for the browser you're using or try a different browser.
Other option is to go to Google Search (preferably on a PC) and search XDA-Guide: Enabling LTE Bands.
sdembiske said:
If you're referring to the link above that I posted, works fine for me. Maybe security setting in your browser - suggest you try looking at the security settings for the browser you're using or try a different browser.
Other option is to go to Google Search (preferably on a PC) and search XDA-Guide: Enabling LTE Bands.
Click to expand...
Click to collapse
When I go to SuperSU is says denied
I need SuperSU pro I think
What is latest supersu
Its not my browser
I'm talking about when I run the line to enable it
Permission denied
deltadiesel said:
When I go to SuperSU is says denied
I need SuperSU pro I think
What is latest supersu
Click to expand...
Click to collapse
SuperSU doesn't have anything to do with accessing a link. I'm on v2.82, the latest update I've received to-date.
If using Chrome on your phone, turn off Safe Browsing in Settings > (under Advanced heading) > Privacy.
---------- Post added at 10:18 PM ---------- Previous post was at 10:10 PM ----------
deltadiesel said:
Its not my browser
I'm talking about when I run the line to enable it
Permission denied
Click to expand...
Click to collapse
Try enabling setenforce 0 in Terminal Emulator.
Just type in the following (enter each command separately):
su
setenforce 0 (to set permissive) or setenforce 1 (to re-enable enforcing)
and confirm with: getenforce
Failing that, it may be hard coded in your rom which may put you out of luck.
sdembiske said:
SuperSU doesn't have anything to do with accessing a link. I'm on v2.82, the latest update I've received to-date.
If using Chrome on your phone, turn off Safe Browsing in Settings > (under Advanced heading) > Privacy.
---------- Post added at 10:18 PM ---------- Previous post was at 10:10 PM ----------
Try enabling setenforce 0 in Terminal Emulator.
Just type in the following (enter each command separately):
su
setenforce 0 (to set permissive) or setenforce 1 (to re-enable enforcing)
and confirm with: getenforce
Failing that, it may be hard coded in your rom which may put you out of luck.
Click to expand...
Click to collapse
That works through terminal on my phone
Seems like running commands on my compute r it won't switch to root
Either way DFS isn't working now
Can't select my device
deltadiesel said:
Its not my browser
I'm talking about when I run the line to enable it
Permission denied
Click to expand...
Click to collapse
deltadiesel said:
That works through terminal on my phone
Seems like running commands on my computer it won't switch to root
Either way DFS isn't working now
Can't select my device
Click to expand...
Click to collapse
One other thought: failing to first enter adb shell will give that result on your PC.
The following worked for me -i.e., did not get permission-denied, on my laptop.
adb shell
su
echo 1 > /sys/devices/platform/lg_diag_cmd/diag_enable
sdembiske said:
One other thought: failing to first enter adb shell will give that result.
The following worked for me -i.e., did not get permission-denied.
adb shell
su
echo 1 > /sys/devices/platform/lg_diag_cmd/diag_enable
Click to expand...
Click to collapse
This doesn't work for me off my computer
It only works in terminal manager. It switches to root after su
Anyways now that I'm in where is this BAND tab in DFS
deltadiesel said:
This doesn't work for me off my computer
It only works in terminal manager. It switches to root after su
Anyways now that I'm in where is this BAND tab in DFS
Click to expand...
Click to collapse
With respect to the Band tab in DFS - post your questions now to the link I provided in the 1st instance.
If you do not have LGMobileDriver_WHQL_Ver_4.2.0 installed on your PC you will have problems with adb.
sdembiske said:
With respect to the Band tab in DFS - post your questions now to the link I provided in the 1st instance.
If you do not have LGMobileDriver_WHQL_Ver_4.2.0 installed on your PC you will have problems with adb.
Click to expand...
Click to collapse
That is installed
U know what forget this. Probably won't be able to enable band I want anyway
Wasting time