Related
How to root Jelly Bean
(galaxy nexus gsm yakju)
Full post here:
http://www.androidpolice.com/2012/0...-jelly-bean-heres-a-method-that-works-how-to/
Short form:
1. adb push CWM-SuperSU-vXXX.zip /sdcard/
2. adb reboot bootloader
3. fastboot flash recovery recovery-clockwork-5.5.0.2-maguro.img
4. install zip from sdcard (CWM-SuperSU-vXXX.zip)
After reboot clockwork will no longer be available.
UPDATE 2nd October 2012:
Originally Posted by efrant
The newer versions of CWM will ask you if you want to disable the automatic re-flashing of the stock recovery, once you click reboot (if it sees that /system/etc/install-recovery.sh and/or /system/recovery-from-boot.p are present).
Click to expand...
Click to collapse
UPDATE 20th July 2012:
Delete /system/recovery-from-boot.p. You don't need to keep it.
Original Fix (outdated):
To fix this rename /system/recovery-from-boot.p to /system/recovery-from-boot.p.bkp EDIT: (filename doesn't matter) ###
Download supersu from this link (recent version)
http://forum.xda-developers.com/showthread.php?t=1538053
Have fun
+1
works great!
qByte said:
How to root Jelly Bean
(galaxy nexus gsm yakju)
Full post here:
h**p://***.androidpolice.com/2012/07/01/having-trouble-rooting-the-galaxy-nexus-on-jelly-bean-heres-a-method-that-works-how-to/
(sry for stars but I can't post links)
Short form:
1. adb push JB-SuperSU.zip /sdcard/
2. adb reboot bootloader
3. fastboot flash recovery recovery-clockwork-5.5.0.2-maguro.img
4. install zip from sdcard (JB-SuperSU.zip)
After reboot clockwork will no longer be available.
To fix this rename /system/reboot-from-recovery.p to /system/reboot-from-recovery.p.bkp
JB-SuperSU.zip
md5: 4b3973aae9b7fb734f83f680da5f4ddb
sha1: 35caff48e17c7f65a7616814ad9afd8cb0998b58
Have fun
Click to expand...
Click to collapse
wonderful, my root was wonky after upgrading to 4.1.1
thanks a lot!
Great guide.
There is a small mistake,rename reboot-from-recovery.p to reboot-from-recovery.bak (not p.bkp)
And that will work.
Cheers.
Hello everyone,
I have been having problems trying to install the root. When i try to run the command "fastboot oem unlock" it says "waiting for device". Is this because i installed an update that was pushed out on Friday? Or am i doing something wrong? Also Windows 7 detects my nexus tablet as a portable media player. Are there any drivers avail be for the nexus tab for windows users?
Thanks
hitsndc said:
Hello everyone,
I have been having problems trying to install the root. When i try to run the command "fastboot oem unlock" it says "waiting for device". Is this because i installed an update that was pushed out on Friday? Or am i doing something wrong? Also Windows 7 detects my nexus tablet as a portable media player. Are there any drivers avail be for the nexus tab for windows users?
Thanks
Click to expand...
Click to collapse
I'm on OSX so I don't know all the fine details but it sounds to me like you are missing the correct USB drivers from Samsung for ADB to recognize your device. Not sure if you can get the drivers separately but I'm pretty sure the right ones are included with Samsung Kies.
Hello!
why my nexus is losing the recovery ClockworkMod every time it restarts?
I am using this version: touch-recovery-clockwork-5.8.0.2-maguro.img
thanks
maicoalvim said:
Hello!
why my nexus is losing the recovery ClockworkMod every time it restarts?
I am using this version: touch-recovery-clockwork-5.8.0.2-maguro.img
thanks
Click to expand...
Click to collapse
Read the OP....
"After reboot clockwork will no longer be available.
To fix this rename /system/reboot-from-recovery.p to /system/reboot-from-recovery.p.bkp"
cymru said:
Read the OP....
"After reboot clockwork will no longer be available.
To fix this rename /system/reboot-from-recovery.p to /system/reboot-from-recovery.p.bkp"
Click to expand...
Click to collapse
thank you! it worked!
Ok I feel retarded, why can't I find /system/reboot-from-recovery.p? I used my root explorer and even searched for it
Xg3nFatality said:
Ok I feel retarded, why can't I find /system/reboot-from-recovery.p? I used my root explorer and even searched for it
Click to expand...
Click to collapse
I am having same problem
Sent from my Galaxy Nexus
This one works! Thanks so much!
Srirama said:
Great guide.
There is a small mistake,rename reboot-from-recovery.p to reboot-from-recovery.bak (not p.bkp)
And that will work.
Cheers.
Click to expand...
Click to collapse
filename doesn't matter...
qByte said:
[snip]
After reboot clockwork will no longer be available.
To fix this rename /system/reboot-from-recovery.p to /system/reboot-from-recovery.p.bkp EDIT: (filename doesn't matter)
Click to expand...
Click to collapse
You have the wrong file name to begin with. It is NOT reboot-from-recovery.p. It is recovery-from-boot.p...
efrant said:
You have the wrong file name to begin with. It is NOT reboot-from-recovery.p. It is recovery-from-boot.p...
Click to expand...
Click to collapse
thx4info. fixed it
qByte said:
thx4info. fixed it
Click to expand...
Click to collapse
You still have a mistake there there is no "i" at the end. It is recovery-from-boot.p
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
You still have a mistake there there is no "i" at the end. It is recovery-from-boot.p
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
fixed 2.0
how would I delete recovery-from-boot.p in adb or cwm before I have to reboot and wipe out the option of having root? I can't find the command for terminal. Thanks!
harpoongill said:
how would I delete recovery-from-boot.p in adb or cwm before I have to reboot and wipe out the option of having root? I can't find the command for terminal. Thanks!
Click to expand...
Click to collapse
1. Root Explorer or
2. adb shell > rm
harpoongill said:
how would I delete recovery-from-boot.p in adb or cwm before I have to reboot and wipe out the option of having root? I can't find the command for terminal. Thanks!
Click to expand...
Click to collapse
In cwm/adb:
adb shell
mkdir -p /system
mount -o rw /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system
rm /system/recovery-from-boot.p
reboot
Sent from my i9250
UPDATED 7-8-13
WHAT THIS TOOL DOES:
1.ROOTS YOUR GALAXY S4 (motochopper exploit created by djrbliss)
2. PREPS FOR RECOVERY
3. INSTALLS CWM OUDHS 1.0.3.4 (7/8) RECOVERY(credit to shabbypenguin)
4. INSTALLS TWRP 2.6.0.0 (credit to dees_troy)
5. Flash phone back to stock using odin
(Full Version Only)
#FOR AT&T I337 ONLY WARNING MADE#
Heres a pretty amateur video I threw together:
https://www.youtube.com/watch?v=NlK3r81kQPw&feature=youtube_gdata_player
Ive updated this to a 3 way all in one tool. Tool can root device (using motochopper by djrbliss) and install either cwm or twrp. Great tool for all those just getting started. Both CWM OUDHS 1.0.3.5 and TWRP 2.5.0.2 are auto loki. They will apply loki patch to all compatible roms and kernels flashed. You can also flash back to stock via Odin
##EDIT I HAVE RECEIVED VERIFICATION THAT TWRP WILL NOT AUTO PATCH. THIS CAME FROM DEES_TROY HIMSELF. IF YOU USE TWRP BE SURE TO FLASH A LOKI KERNEL AFTER ANY NON LOKI ROM FLASH##
A huge thanks to djrbliss for his genius
And huge thanks to dees_troy and shabbypenguin for the recoveries
Also thanks to mostyle for the script help
Instructions:
1. Download 3way tool zip
2. Unzip on desktop and open tool.
3. Connect I337 via usb with usb
debugging enabled.
4. Click Run_Me.bat select number for option you desire and enjoy!
Use this tool at your own risk. I am not responsible for any level of destruction to your phone blah blah blah
Downloads:
Full Version
https://mega.co.nz/#!o0dXHLoY!BNo2eFNQsuPN2-ivpVGo7Vk_V7ckHorY9WlK0PTqbSM
Slim Version (no odin to stock)
https://mega.co.nz/#!Q9FByZrD!CUK7RTDUzzzrH-n3rXjylhkOyy9B1gx9zHNfaKkbVJg
#EDIT# ADDED PREP FOR RECOVERY OPTION. WILL REMOVE KNOX APKS AND install-recovery.sh FOR YOU.Mirrors are welcome. Have a nice day! Dont forget to hit the THANKS button!
If youd like to buy me a beer:beer: I wont complain
Thanks for the beer:beer:list:
Scanss2k
LSUtigers03
O.K
I like to try it :fingers-crossed:
I installed the OUDHS Recovery yesterday and now either one of these will install.I'd love to have Loki'd TWRP. My phone has the same UCUAMDL
If you use either of these please let me know if it works for you.
Respond to sholsten
You mean Neither will work,
It didn't work on mine.
Ill recheck script when I get home. Worked on test devices prior to posting. Please post error messages here. ^^^^ already have yours
pakxelaos said:
Respond to sholsten
You mean Neither will work,
It didn't work on mine.
Click to expand...
Click to collapse
Neither seemed to have have installed on mine. It has the same one I installed in my above post yesterday.
sholsten said:
Neither seemed to have have installed on mine. It has the same one I installed in my above post yesterday.
Click to expand...
Click to collapse
What message did you get on tool after it ran
pakxelaos said:
Respond to sholsten
You mean Neither will work,
It didn't work on mine.
Click to expand...
Click to collapse
Did uninstall the recovery.sh file?
Fixed
On the line that issues the remount command there occurs 'Permission denied.'
In your batch file change line 25:
adb remount
Click to expand...
Click to collapse
so that it reads:
adb shell su -c "mount -o rw,remount /system"
Click to expand...
Click to collapse
Of course this assumes you are rooted..
EDIT:
Still getting an error 'Failed to open aboot for reading'
I'm investigating.. Hang on.
Will change and repost in a few
You could just install goomanger and install twrp thats been lokified directly from your rooted s4
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
bhp090808 said:
What message did you get on tool after it ran
Click to expand...
Click to collapse
Finished Rebooting into TWRP
Have a nice day!
adb is not recognized as an internal or external command, operable program or batch file.
Press any key to continue
Here's the fixed script..
Just had to su -c all of your commands...
db kill-server
adb start-server
adb shell su -c "mount -o rw,remount /system"
adb wait-for-device
adb push loki_flash /data/local/tmp
adb push openrecovery.lok /data/local/tmp
ECHO.
ECHO Doing the hard stuff.............
ECHO.
adb shell su -c "mount -o rw,remount /system"
adb shell su -c "chmod 755 /data/local/tmp/loki_flash"
adb shell su -c "./data/local/tmp/loki_flash recovery /data/local/tmp/openrecovery.lok"
Click to expand...
Click to collapse
Hope that helps. Tested it here and it works fine..
mostyle said:
Just had to su -c all of your commands...
Hope that helps. Tested it here and it works fine..
Click to expand...
Click to collapse
Will update and repost in a few thx
EDIT
Ok updated script new links are up let me know if its working for you now
MrPlNK said:
You could just install goomanger and install twrp thats been lokified directly from your rooted s4
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
How do you find the correct TWRP?
Just tried this with TWRP worked beautifully, thank you very much!! :good:
djoutrages said:
Just tried this with TWRP worked beautifully, thank you very much!! :good:
Click to expand...
Click to collapse
Make sure to thank mostyle for the script assist. Thanks bro
Tested both on my 32GB S4. Both working with no issues at all. Appreciate the work that went into this.
So if I understand this will allow you to flash a Rom that has not been Loki'd and it will loki it and allow it to boot with either TWRP or CWM?
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...
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
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