Develop Bugs

Magisk Can't Pass Safety Net

This guide is for "ctsProfile: false" and "basicIntegrity: true".
First download "busybox for android ndk" and "magiskhide props cofig" from magisk repo
after reboot type to adb
adb shell-su-props-1-f-18-10-y-n
and finished, reboot your phone and now safety net is completely passed
CHANGEABLE THINGS:
for another device owners
adb shell-su-props-1-f-18-<avaible devices>-y-n then reboot
At least it worked for me

mihhut said:
This guide is for "ctsProfile: false" and "basicIntegrity: true".
First download "busybox for android ndk" and "magiskhide props cofig" from magisk repo
after reboot type to adb
adb shell-su-props-1-f-18-10-y-n
and finished, reboot your phone and now safety net is completely passed
CHANGEABLE THINGS:
for another device owners
adb shell-su-props-1-f-18-<avaible devices>-y-n then reboot
At least it worked for me
Click to expand...
Click to collapse
you can also just install the SafetyPatch module in Magisk

InfinityXDA said:
you can also just install the SafetyPatch module in Magisk
Click to expand...
Click to collapse
I tried that module but it didn't work.

Im having this problem now, ive tried changing fingerprint, cts and other one fail even with magisk safetynet.

[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

"Enable" camera2api Android 10

# Mi8Lite # Android10 # Camera2api Requirements: –Bootloader Unlocked –TWRP installed, does not work with other recoverys –The recovery must not be encrypted –Not have root ADB COMMAND METHOD IN TWRP * Start in TWRP and connect to PC * On the PC, open a command window inside the adb or platform-tools folder * Type these commands: (after each command hit Enter)
-adb devices adb shell
-setprop persist.camera.HAL3.enabled 1
-setprop persist.camera.eis.enable 1
-setprop persist.vendor.camera.HAL3.enabled 1
-setprop persist.vendor.camera.eis.enable 1
-exit adb reboot
"Adb devices" is not recognized: If after placing the first command, the PC does not recognize your device in Recovery mode; in TWRP go to the MOUNT box and look for the 'Disable MTP' option, press and it should show you 'Enable MTP'; try again with "adb devices" and continue * If camera 2api was not activated, try one more time with these commands: adb devices adb shell
setprop persist.camera.stats.test 5
setprop persist.vendor.camera.stats.test 5
exit adb reboot
–Check with "Manual Camera compatibility test" the status of camera 2api –After this I could try to root and check if camera 2api stays activated –It is possible that activating camera 2api will stop working the front camera of the native camera. –Added commands will be erased with a factory reset.
note: I saw it in a group of Xiaomi Mi 8 Lite and I wanted to share it here to find out if anyone knows the veracity of this

Any other module?

not working. Tested with last xiaomi.eu, with and no root. twrp 3.3.2b

MIUI 12, MIUI EU ROM not working either

CongMinhVN said:
MIUI 12, MIUI EU ROM not working either
Click to expand...
Click to collapse
Here is a solution:
https://yadi.sk/d/K97naZ2Zg5xwUw

kennethstarr said:
Here is a solution:
https://yadi.sk/d/K97naZ2Zg5xwUw
Click to expand...
Click to collapse
Thanks bro

Can someone give me the link of twrp for xiaomi this device (mi 8 lite).

Ubaid2003 said:
Can someone give me the link of twrp for xiaomi this device (mi 8 lite).
Click to expand...
Click to collapse
Only need to search a bit...
https://forum.xda-developers.com/mi-8-Lite/how-to/mi-8-lite-stock-recovery-one-t4168539

Ubaid2003 said:
Can someone give me the link of twrp for xiaomi this device (mi 8 lite).
Click to expand...
Click to collapse
Pls dont ask people before trying to solve it yourself first. Giving you hate from me

PDC without ROOT on android 11

Activation VoLTE without ROOT on android 11:
1. adb reboot ftm
2. adb shell
3. setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
4. Change profile QPST PDC
5. adb reboot

Hi a big thank you to you for this tutorial. It works perfectly without ROOT. wonderful and again a big thank you @zloynavseh
For PDC I used the command in mod FTM
setprop sys.usb.config diag,serial_cdev,rmnet,adb

Appreciate the tutorial here! cheers

galaxys said:
Appreciate the tutorial here! cheers
Click to expand...
Click to collapse
1. adb reboot ftm
2. adb shell
3. setprop sys.usb.config diag,serial_cdev,rmnet,adb
4. Change profile PDC
5. adb reboot
Volte and PDC no root.

when installing the qualcomm drivers, be sure to choose the wwan option.

I can't get past step 1. I get the initial OnePlus splash screen, but nothing more.

How to boot to normal?

after I reboot to ftm and adb reboot I got no connection.
anyone can help me to fix it?

zloynavseh said:
Activation VoLTE without ROOT on android 11:
1. adb reboot ftm
2. adb shell
3. setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
4. Change profile QPST PDC
5. adb reboot
Click to expand...
Click to collapse
hello
i see the phone on the PDC list but when choosing it
qmi connection not ready please use usb driver version 1.00.32 -
i updated my driver - same...

angeloamorato said:
How to boot to normal?
Click to expand...
Click to collapse
adb reboot

i'm failling on step 4 : "/system/bin/sh: Change: inaccessible or not found" (oneplus 7T/Android 11 official). Any idea or just not doable ?

the procedure works on other pc/laptop version.

any method for Android 12?

I use this method and working in realme gt2 pro, the problem is the step es temporary, if you reboot the phone you lost the change... how i can made permanent change?

I am not able to pass adb reboot ftm command. Device is always rebooting in system. Any idea why?

Is it working on Android 13?

Question Anyone else having issues getting 120hz running on Brave or Kiwi with OOS 12?

I have tried ADB commands and 3 different apps(AutoHZ, SmartHertz) but the the browsers will not run faster than 60hz. This wasn't an issue on OOS 11.

422415 said:
I have tried ADB commands and 3 different apps(AutoHZ, SmartHertz) but the the browsers will not run faster than 60hz. This wasn't an issue on OOS 11.
Click to expand...
Click to collapse
No root needed.
Just run these in adb shell (after enable "Disable Permission Monitoring" in developer options):
Code:
settings put system peak_refresh_rate 1
settings put system min_refresh_rate 1

Do these settings stick after reboot or we have to do this every time the device is rebooted
brmbjn said:
No root needed.
Just run these in adb shell (after enable "Disable Permission Monitoring" in developer options):
Code:
settings put system peak_refresh_rate 1
settings put system min_refresh_rate 1
Click to expand...
Click to collapse

gulshanstrider said:
Do these settings stick after reboot or we have to do this every time the device is rebooted
Click to expand...
Click to collapse
Repeat after reboot
Please try.
always Work 120