Develop Bugs

[FIX] Wifi Sleep Policy

So I'm sure you all have noticed, especially if downloading something, when the screen turns off the Wifi on the Fire "sleeps" until the screen comes back on. So you try to change that setting. But low and behold....ITS MISSING!?
I come with a fix. I'll warn ya, its messy.
ADB:
Connect the Kindle Fire to your computer using a USB cable and tap "Disconnect Now"
Connect to the Fire using adb and open a shell and type adb shell (or your operating system's equivalent) and hit enter
run
Code:
su
run
Code:
cd /data/data/com.android.providers.settings/databases
run
Code:
cp settings.db settings.db.bak
run
Code:
cp settings.db /mnt/sdcard
Mount the Kindle Fire on the computer
Copy settings.db off your sdcard and onto your desktop
Open SQLite Browser and open the settings.db file that you just placed on your desktop
In the SQLite Browser, open the "Browse Data" tab, select "system" from the table list; scroll to the bottom.
Click the "New Record" button.
Double-click the first blank entry area to bring up the value editor.
Type
Code:
wifi_sleep_policy
Click Apply.
Double click the second blank entry area.
Type one of these integers in (Whichever you prefer) :
Sleep When Screen is Off -----> 0
Sleep When NOT Plugged In ---> 1
Never Sleep --------------------> 2
Click Apply.
Click Save.
Copy the settings.db file you just modified back onto your Kindle Fire.
Click the Disconnect button on your Fire.
Open your shell window and type
Code:
adb shell
(if you are no longer in shell or closed your shell window)
run
Code:
su
run
Code:
cp /mnt/sdcard/settings.db /data/data/com.android.providers.settings/databases/settings.db
run
Code:
cd /data/data/com.android.providers.settings/databases
run
Code:
chmod 660 settings.db
run
Code:
chown system.system settings.db
run
Code:
ls -l
The last command verifies that your modified settings.db matches the same user and group and has the same permissions as your original (settings.db.bak)
Reboot and Enjoy!

Wouldn't be easier to just use on of the apps that does this from market that way it's easy to switch between them
Sent from my DROID2 GLOBAL using Tapatalk

CrackMonkey91 said:
Wouldn't be easier to just use on of the apps that does this from market that way it's easy to switch between them
Sent from my DROID2 GLOBAL using Tapatalk
Click to expand...
Click to collapse
Some people have had issues with said apps. If the User wants yo use the apps and they work, fine. If they want to use this method, fine. I'm just offering this as an option. Not saying anyone has to do this...

Hmmm....my kindle cannot boot up after applying the change stuck on the "kindle fire" screen
---------- Post added at 11:06 PM ---------- Previous post was at 10:19 PM ----------
ipccheng said:
Hmmm....my kindle cannot boot up after applying the change stuck on the "kindle fire" screen
Click to expand...
Click to collapse
Got it fixed - step 26 should be "chown system.system settings.db" ("." instead of ":")

works great, thanks for the info and the other posters mentioning the invalid colon.

ipccheng said:
Hmmm....my kindle cannot boot up after applying the change stuck on the "kindle fire" screen
---------- Post added at 11:06 PM ---------- Previous post was at 10:19 PM ----------
Got it fixed - step 26 should be "chown system.system settings.db" ("." instead of ":")
Click to expand...
Click to collapse
thanks for noticing the typo/issue.
edited op. its now fixed

I need to root my Fire first to do this correct?

tried this last week and have "mixed" results.
sometimes wifi seems to be in after turning screen on. sometimes the wifi is off and going inti the status menu shows its turned off. the setting has to be toggled.
since then I've been thinking, doesn't spare parts have this option? the setting is already there since I modified the file. I'm wondering if spare parts would successfully do this.

Never thought of that!
Try it. It cant hurt!
Won't have to worry about this much longer though.

Just broke my Kindle reverting the mods. I didn't set the permissions DOH!

Spare parts seems to work on my KF. Just installed it from the market and let it go to sleep. Turned it back on, and wifi was still connected.
EDIT: Never mind. I guess I didn't give it enough time. Spare parts did not work to keep wifi from going to sleep.

This is an 'issue' they could correct with a software update right?

For those who don't want to chance this mod, I downloaded "Wifi Keep Alive" from the market and it worked like a charm.

baj24 said:
For those who don't want to chance this mod, I downloaded "Wifi Keep Alive" from the market and it worked like a charm.
Click to expand...
Click to collapse
Do you have an apk for this? Thanks! (I only ask because I have yet to root my KF and would like to sideload it and I can't seem to find a proper apk searching google...crazy I know, lol)

sqlite3 tools
It can edit settings.db on kindle fire. You do not need copy out .
sqlite3 /data/data/com.android.providers.settings/databases/settings.db
insert into system (name, value) values ("wifi_sleep_policy", “2” );
ctrl+d
It will be ok.

likeitnot said:
Do you have an apk for this? Thanks! (I only ask because I have yet to root my KF and would like to sideload it and I can't seem to find a proper apk searching google...crazy I know, lol)
Click to expand...
Click to collapse
I attached the WiFi Keep Alive apk. It's been working great for me.

So, I thought I set permissions correctly on my settings.db.bak file before deleting my new settings.db and renaming the backup, but apparently I did not because I am in a boot loop. Anyone know of a way out of this situation?

Nvm, used zergRush to tmp root and change permissions.

It would be nice if we could have wifi stay on only if plugged in.

CptanPanic said:
It would be nice if we could have wifi stay on only if plugged in.
Click to expand...
Click to collapse
WiFi Keep alive has three modes:
1. WiFi off if screen off (White widget)
2. WiFi on if screen off (Green Widget)
3. WiFi on if screen off & charging (Amber Widget)
I keep it on Green personally...

[NOW WORKS] Obtaining root with master key vulnerability

One click root with impactor now works. Works on <4.3. No need for unlocked bootloader. Does not wipe data.
http://www.saurik.com/id/17

Copy over the superuser.apk and the such binary onto your phone, then use the MV command to move it to /system/app and /system/xbin respectively.
Beamed from my Grouper

Mach3.2 said:
Copy over the superuser.apk and the such binary onto your phone, then use the MV command to move it to /system/app and /system/xbin respectively.
Beamed from my Grouper
Click to expand...
Click to collapse
What should the permissions on each be?
EDIT: Can you alternatively only push the su binary and download superuser from gplay?

krackers said:
What should the permissions on each be?
EDIT: Can you alternatively only push the su binary and download superuser from gplay?
Click to expand...
Click to collapse
If the binary is wrong, the one from play store may not work.
Permission should be rw-r-r(0644) for the su.apk and rwsr-sr-x(0645) for the su binary.
Beamed from my Maguro.

I tried it myself and while it appears that commands do run, they don't appear to work. I think it might have to do with running as system vs running as root. Why else would saurik use an indirect method of gaining root (using ro.kernel.quemu) as opposed to directly pushing the su binaries.

krackers said:
I tried it myself and while it appears that commands do run, they don't appear to work. I think it might have to do with running as system vs running as root. Why else would saurik use an indirect method of gaining root (using ro.kernel.quemu) as opposed to directly pushing the su binaries.
Click to expand...
Click to collapse
This is correct: sometime in the Android 4.1 release cycle, they removed the ability to use /data/local.prop as an attack vector to go from system->root. The signature bug lets you modify the code of any APK, but the most powerful user an app can ever run as is system, not root.
However, in an update to Impactor today, I've added a system->root escalation. This allows one-click rooting, and even though the system->root I'm using has already been patched in AOSP (the idea was not to waste something to go along with a shell->system that is already long burned) it works on my 4.2.2 Nexus 4 (and so I'd imagine will also work fine on a Galaxy Nexus) as Android sucks at getting patches to real devices ;P.

Using Impactor on my Panasonic Eluga dl01 does somehow not work.
(Android 4.0.4)
I get following error message:
/data/local/tmp/impactor-6[3]: /data/local/tmp/impactor-4: Operation not permitted
I also tried and played around with the command line in Impactor.
"adb devices" won't list my phone
But when I use the adb from the current Android SDK I just installed, it will display my phone with "adb devices".
I also downloaded a ICS 4.04 root zip file with a script and adb files inside. When using that adb version, my phone won't be displayed too. Now when I run adb from the android SDK, it will say something like "server is outdated" then something like "kill and restart with new server" --> "adb devices" lists my phone correctly again.
May be the adb version used in Impactor is outdated and responsible for the error message?
I would really appreciate any help with this topic, because the Panasonic Eluga phone was never rooted until now and no known root method is available. I always kinda hoped that someone would use the masterkey thing to make a universal rooting tool

saurik said:
This is correct: sometime in the Android 4.1 release cycle, they removed the ability to use /data/local.prop as an attack vector to go from system->root. The signature bug lets you modify the code of any APK, but the most powerful user an app can ever run as is system, not root.
However, in an update to Impactor today, I've added a system->root escalation. This allows one-click rooting, and even though the system->root I'm using has already been patched in AOSP (the idea was not to waste something to go along with a shell->system that is already long burned) it works on my 4.2.2 Nexus 4 (and so I'd imagine will also work fine on a Galaxy Nexus) as Android sucks at getting patches to real devices ;P.
Click to expand...
Click to collapse
Do you need to have an unlocked bootloader for the root exploit to work? I am hoping to get root without having to wipe the device by unlocking.
To the poster above me: Try using a different computer and if that doesn't work, switch operating systems.

krackers said:
Do you need to have an unlocked bootloader for the root exploit to work? I am hoping to get root without having to wipe the device by unlocking.
Click to expand...
Click to collapse
That's the whole point in securing Android, not that people have easier ways instead of unlocking a device.

Tested and works great. I now have root. Yay!

Does it show any of the problems that chainfire's superSU 1.41 shows?
Sent from my Galaxy Nexus using xda app-developers app

The root exploit only places the su binary and sets the right permissions. You can use any root manager you want (I used clockworkmod's superuser app).

mercuriussan said:
Using Impactor on my Panasonic Eluga dl01 does somehow not work.
(Android 4.0.4)
Click to expand...
Click to collapse
The feature of installing su will not work on every device: a lot of emphasis is put on "rooting" Android devices, but on many devices even root can't do things like modify the files in /system; I'd use the term "jailbreak" as to being what people really want to do with their device, but Android people seem to have that term ;P. What this means is that you really need a kernel exploit, not just a shell->system->root escalation.
mercuriussan said:
I get following error message:
/data/local/tmp/impactor-6[3]: /data/local/tmp/impactor-4: Operation not permitted
Click to expand...
Click to collapse
This error message actually indicates that Impactor succeeded in obtaining root control over your phone. However, when it tried to then, as root, remount /system writable so it could copy the su binary in place, it wasn't allowed to do so. A future version of Impactor will make it easier to drop to a root shell so you can test things out manually, but this means that while you can run code as root, you won't be able to install su.
However, if you have the time to play with it, get a copy of busybox and use adb to push it to /data/local/tmp (this is also something Impactor should help you do, but does not yet). (You will also need to make it executable, don't forget: "chmod 755 /data/local/tmp/busybox".) Then run the suggested Impactor command involving telnetd. Finally, via a shell, run "/data/local/tmp/busybox telnet 127.0.0.1 8899": you are now root.
You can verify that you are root because you will now have a # as a prompt instead of a $. Then run "mount -o remount,rw '' /system" (<- note, that's two single quotation marks as an argument between remount,rw and /system). This is the command that should fail with the "Operation not permitted" message. You are, however, root, so maybe there's something you want to do on the device at that point ;P.
mercuriussan said:
I also tried and played around with the command line in Impactor.
"adb devices" won't list my phone
But when I use the adb from the current Android SDK I just installed, it will display my phone with "adb devices".
Click to expand...
Click to collapse
The "Open Shell" in Impactor connects you to the device via adb: if you run adb on the device and ask for a list of devices attached to the device--something I didn't even realize was possible until you pointed it out here ;P I tested it, though, and wow: that actually is possible--you will get a blank list. However, suffice it to say that if you were able to type that at all, it can see your device.

Thanks for the suggestion, I'll try my luck in finding some exploit I can use...

So since Google patched this in 4.3, does this mean almost all devices before 4.2.2 can be rooted with this method?

bmg1001 said:
So since Google patched this in 4.3, does this mean almost all devices before 4.2.2 can be rooted with this method?
Click to expand...
Click to collapse
Yup - assuming they haven't been patched against the methods used (most haven't been).

Very interesting read. Thanks saurik & OP.

Eluga DL1
Hi there,
this post is in some ways a duplicate but different people seem to follow this thread because it is directly involving sauriks impactor.
Is there anything available that i can throw at Elugas 4.0.4 kernel to get r/w on the system partition?
I will try everything that is suggested to me.

[Q] How to install from unknown sources without ADB?

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

Is it possible to block AFV stick from updating ?

I've seen that Amazon firesticks have updated their software which has effected Firestarter. I just wanted to know three things:
Is it possible to block amazon updates? I've got a virgin superhub router.
Is there a way to backup the entire firestick and not just Kodi?
Can you previous firmwares versions be restored/downgraded on firesticks?
The last thing I think anyone wants is for an update that wipes of Kodi altogether :crying:

Yes, you can block updates. See my guide here: http://www.aftvnews.com/block
If the device is rooted and running TWRP custom recovery, you can backup and restore the entire device at once. There is no TWRP for the Fire TV Stick currently, but rbox is working on it. For now, all you can do is backup individual files and folders, like app data, but depending on where the data is stored, you may still need to be rooted. App data in /sdcard can be backed up without root, but app data in /data requires root to access.
You can only downgrade if the device is rooted and running TWRP custom recovery. There is an old downgrading method that requires root and uses the default recovery, but I have not tested it on Fire OS 5 devices.

Hey thanks for that, I think I managed to prevent the firestick from any updates using adb + terminal from you pointing me on the right track.

hi AFTVnews.
is the adb shell pm hide com.amazon.device.software.ota command still works ? i have tried yesterday and it worked fine, and today i try again the same commend on second device (fire stick) and i get : unknown command 'hide'

scofield27 said:
hi AFTVnews.
is the adb shell pm hide com.amazon.device.software.ota command still works ? i have tried yesterday and it worked fine, and today i try again the same commend on second device (fire stick) and i get : unknown command 'hide'
Click to expand...
Click to collapse
I'm on a firestick with 5.0.5 and ran the command no problem, and disconnected properly. I had issues though after a few fire stick reboots where my firestick was connected to my router and had an ip, but had no internet connection. Basically it seemed like the command blocked the firestick from doing anything. I used the unhide command and rebooted a few more times and then ran the command to hide it once more and rebooted a few more times. Now it appears it is blocking updates and i can still use kodi.
I also have been having router issues, so it could be my router.

AFTVnews.com said:
Yes, you can block updates. See my guide here: http://www.aftvnews.com/block
If the device is rooted and running TWRP custom recovery, you can backup and restore the entire device at once. There is no TWRP for the Fire TV Stick currently, but rbox is working on it. For now, all you can do is backup individual files and folders, like app data, but depending on where the data is stored, you may still need to be rooted. App data in /sdcard can be backed up without root, but app data in /data requires root to access.
You can only downgrade if the device is rooted and running TWRP custom recovery. There is an old downgrading method that requires root and uses the default recovery, but I have not tested it on Fire OS 5 devices.
Click to expand...
Click to collapse
Hi Aftvnews, how do you delete the update cache on the firestick? I got a new firestick but it was downloading update before I could stop it. It's there but if I can get into the folder to delete it that would be great. I saw mention how to do it but didn't show the command lines. Thanks!

scofield27 said:
hi AFTVnews.
is the adb shell pm hide com.amazon.device.software.ota command still works ? i have tried yesterday and it worked fine, and today i try again the same commend on second device (fire stick) and i get : unknown command 'hide'
Click to expand...
Click to collapse
The command only works on software version 5.0 and up. If that Stick is on 54.1.2.3 or older, then the only way to block updates is externally through a router or OpenDNS (method 3 and 4 in my guide).
eore227 said:
Hi Aftvnews, how do you delete the update cache on the firestick? I got a new firestick but it was downloading update before I could stop it. It's there but if I can get into the folder to delete it that would be great. I saw mention how to do it but didn't show the command lines. Thanks!
Click to expand...
Click to collapse
Your Stick must be rooted to delete the update file from /cache. Here's how to do it:
Code:
adb shell
su
rm -f /cache/*.bin

AFTVnews.com said:
The command only works on software version 5.0 and up. If that Stick is on 54.1.2.3 or older, then the only way to block updates is externally through a router or OpenDNS (method 3 and 4 in my guide).
Your Stick must be rooted to delete the update file from /cache. Here's how to do it:
Code:
adb shell
su
rm -f /cache/*.bin
Click to expand...
Click to collapse
Hi aftvnews can you show me how this command works for a mac? I just rooted a fire stick right now using king root. It says root was sucessful but I don't want to reboot as the update is on there. If I could delete this update before the update that would be good but I'm using mac terminal and typed in your command but it's not working. Thanks
---------- Post added at 02:09 AM ---------- Previous post was at 01:50 AM ----------
eore227 said:
Hi aftvnews can you show me how this command works for a mac? I just rooted a fire stick right now using king root. It says root was sucessful but I don't want to reboot as the update is on there. If I could delete this update before the update that would be good but I'm using mac terminal and typed in your command but it's not working. Thanks
Click to expand...
Click to collapse
Ok I have root access I typed adb shell then I did su to get root access. Now it shows [email protected] montoya: #
After the # i typed rm -f/cache/*.bin
Is this correct? I don't see anything happened

eore227 said:
Hi aftvnews can you show me how this command works for a mac? I just rooted a fire stick right now using king root. It says root was sucessful but I don't want to reboot as the update is on there. If I could delete this update before the update that would be good but I'm using mac terminal and typed in your command but it's not working. Thanks
---------- Post added at 02:09 AM ---------- Previous post was at 01:50 AM ----------
Ok I have root access I typed adb shell then I did su to get root access. Now it shows [email protected] montoya: #
After the # i typed rm -f/cache/*.bin
Is this correct? I don't see anything happened
Click to expand...
Click to collapse
First, be sure there is a space after the "f"
You won't see anything come up on the screen. I also just learned a few hours ago that there is an alternate location for the update file. So do the following to clear out both locations:
Code:
adb shell
su
rm -f /cache/*.bin
rm -f /sdcard/Android/data/com.amazon.device.software.ota/files/*.bin

Perfect that did the trick the update was deleted. I rebooted and still have root and uodate is gone. Thanks!

[ROOT] Enable Soli in any country

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