Related
Preamble
What I write here is what I did. BUT I am not responsible of damages you could do your phones. Be careful and safe. If you do not know what you are doing, do not do this.
This is not a method to unbrick your phone. Unfortunately, I did not succeed to do that. It is a method to unroot: to cleanse any trace of rooting. In my case, it was to give it back to my store.
The rooting method I used is the "Universal Gingerbread Root (by StoneBoyTony)" I found here: http://forum.xda-developers.com/showthread.php?t=1192122 (scroll down a bit). This method is to root your Gingerbread phone through the recovery mode by unpacking a zip file (keep this file in mind). Thus, this tutorial is concerning this rooting method. I did not try with other rooting methods. So take care.
Code:
something to write
is what you have to type.
something to expect/read
Click to expand...
Click to collapse
is what you should read at your side.
Read before writing. Like students (should) do in classes.
My computer runs Windows XP SP3. Just saying.
This is my first thread. Please, be cool with me
Finally, do not confuse rooting and unlocking.
To root a phone is to allow the user to be a super-user on the phone, which means: to have greeeaaaat powers.
To unlock means to use any carrier with the phone by getting the unlock code.
Hence, to get the unlock code, you often have to root your phone to access to sensible data (cf. stl5 story).
I - Introduction
(= useless blabla but informative)
I bought some Samsung Gio cellphones (Bell prepaid, Canada) at a pretty good price ($80, thanks redflagdeals for the deal!), in order to go with another carrier (Chatr).
Characteristics of the Bell's Samsung Gio prepaid cell:
GT-S5660M
Gingerbread 2.3.4
S5660MUGKG3
GT-S5660DSMBMC
Click to expand...
Click to collapse
For the first one, I retrieved the unlock code through what I call the "stl5 way". It worked without any issue. Cool. Next!
For the second one... Oh snap.
Issues began after getting the unlock code and a rebooting. Kinda weird since I exactly did like the first one. Problems were:
No sound at the Samsung animation
Too many minutes to initialize
When I could reach the pad to call a number, the pad was so laaaaggggyyyy
Fly mode is stuck
No more IMEI (nooooooooooooo)
Doing *#7465625# does not display any information about the network lock, sp/cp lock (it displays labels but no values at all)
Turning off the cellphone was very long too...
...but it was not a shutdown: the cellphone was rebooting, weird
Random warnings (even got a warning from "com.android.phone"!)
Putting another SIM card from another carrier did not even notice me to unlock the phone
And so on. Like some folks, I did not really brick it, but like some others, the phone became... unusable.
What I call the "stl5 way" is the unlocking method which can succeed... or not, it depends. Weird isn't it? Unfortunately, I didn't know.
xda and rfd links which explain the stl5 unlocking method:
http://forum.xda-developers.com/showthread.php?t=1204705
http://forum.xda-developers.com/showthread.php?t=1192122
I absolutely advise against this method. BEWARE.
It seems that the /dev/stl5 partition is madly protected. When we use/read/smurf it, it corrupts some data of the phone which could lead to (partially) brick your phone.
Thus, the safest way (nobody failed) so far to unlock your phone is the "bml5 way":
http://forum.xda-developers.com/showpost.php?p=17148825&postcount=334
http://forum.xda-developers.com/showthread.php?p=17247878
II - Plat de résistance
Ok, you used the stl5 way and your phone just took 80yo: it is slow, forgot a lot of information, and some other symptoms I wrote earlier.
Or you just want to unroot your phone, because it's cool.
If there is still no method to unbrick (or it did not succeed), you can give it back to your store or to use the Samsung warranty. You may have to unroot it (get all chances on your side).
- Tools/weapons you will need:
Android Platform Tools, last version (don't need older ones)
Your Samsung Gio in debugging mode
Samsung Kies
Click to expand...
Click to collapse
Explanations:
Android Platform Tools
Click to expand...
Click to collapse
We will use the "adb" program, in order to use the phone terminal. You can also use an embedded terminal (free ones in the android market) or through ssh. It's your call.
Your Samsung Gio in debugging mode
Click to expand...
Click to collapse
Go to : Menu -> Applications -> Development -> USB debugging (green cross it). It will allow "adb" to be connected to the phone.
Samsung Kies
Click to expand...
Click to collapse
Download it here: www.samsung.com/ca/support/mobilesoftwaremanual/mobilesoftwaremanual.do?page=MOBILE.SOFTWARE.MANUAL
Kies is the iTunes-like by Samsung. This may be needed for your computer to detect your phone. But we do not need to launch it. Just install it but do not launch it while doing your stuff.
Step #1
In a Windows shell, go to your .\android-sdk\platform-tools directory (for the example: C:\Android\android-sdk\platform-tools>). Type:
Code:
> adb shell
This will link the computer to your phone and display a remote Android shell. At this point, you should see something like this:
C:\>Documents and Settings\superpizon>cd C:\Android\android-sdk\platform-tools
C:\Android\android-sdk\platform-tools>adb shell
$
Click to expand...
Click to collapse
($ is the prefix of the Android shell, do not type it)
(> is the one for the Windows shell, do not type it too)
Note : if your phone is not in debugging mode, the Windows shell will write:
error: device not found
Click to expand...
Click to collapse
Step #2
After madly browsing the xda method to unroot my phone, I found this post: http://forum.xda-developers.com/showpost.php?p=17078367&postcount=34. Interesting.
If you open the Universal_GB_ROOT.zip file, you have:
META-INF/
-com/
--google/
---android/
----update-binary
----updater-script
-CERT.RSA
-CERT.SF
-MANIFEST.MF
system/
-app/
--Superuser.apk
-xbin/
--busybox
--sh
--sqlite3
--su
--su-v1
--su-v2
--su-v3
Click to expand...
Click to collapse
If you did not notice, after rooting your phone, an unremovable application appeared in the menu application (the icon is a dead skull): this is the visible part of the iceberg that we want to remove.
Ok, your Android shell is waiting. Let's type:
Code:
$ ls /system/xbin
It should display:
dexdump
busybox
sh
sqlite3
su
su-v1
su-v2
su-v3
Click to expand...
Click to collapse
Happenstance? I don't think so. Now type:
Code:
$ ls /system/app/S*.apk
/system/app/SamsungApps.apk
/system/app/SamsungAppsUNAService.apk
/system/app/SamsungWidget_ProgramMonitor.apk
/system/app/SamsungWidget_StockClock.apk
/system/app/ScreenCaptureService.apk
/system/app/SecDownloadProvider.apk
/system/app/SecurityProvider.apk
/system/app/SelfTest.apk
/system/app/SerialNumberLabelIndicator.apk
/system/app/Settings.apk
/system/app/SettingsProvider.apk
/system/app/SetupWizard.apk
/system/app/Setup_Wizard.apk
/system/app/SisoDrmProvider.apk
/system/app/SnsAccount.apk
/system/app/SnsProvider.apk
/system/app/Stk.apk
/system/app/Street.apk
/system/app/Superuser.apk
/system/app/Swype.apk
/system/app/SystemUI.apk
Click to expand...
Click to collapse
(I wrote S*.apk to shorter this logfile).
Oh god, what did we see? The content of the Universal_GB_ROOT.zip file.
Step #3
What do we do now? Well, let's delete these files. Simply.
Good idea. But not so quick to do.
If you "rm" (*nix remove command) files we pointed at, the shell will answer:
rm failed for /system/app/Superuser.apk, Read-only file system
Click to expand...
Click to collapse
Why? Type:
Code:
$ cat /proc/mounts
You should have (it depends of apps you installed):
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/stl14 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/stl13 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/stl12 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0
Click to expand...
Click to collapse
As you can see (or guess ^^), /system (where apps are installed) is mounted as ro (read-only).
As you can wonder, there is a "trick" to bypass that. Go being super-user:
Code:
$ su
Then:
Code:
$ mount -o rw,remount /dev/stl12 /system
This command will remount /dev/stl12 to /system in rw (read-write).
Step #4
NOW, you can remove files. But please, do ONLY remove files of the Universal_GB_ROOT.zip file like this way:
Code:
$ rm /system/xbin/busybox
$ rm /system/xbin/sqlite3
$ rm /system/xbin/sh
$ rm /system/xbin/su-v1
$ rm /system/xbin/su-v2
$ rm /system/xbin/su-v3
$ rm /system/xbin/su
$ rm /system/app/Superuser.apk
(obviously, *nix folks would prefer to go into the xbin folder and remove each file to write less).
Remember: 7 files in the xbin/ folder and only one in the app/ folder.
And this is it! Now quit the su role:
Code:
$ exit
And the Android shell:
Code:
$ exit
You are now back to the Windows shell.
Note : we did not umount anything because it is not needed. We did a remount. Thus, the usual mount of /system/stl12 to /system will happen again at startup. No worries.
Reboot your phone and go back to the application menu. The unremovable root application disappeared! *clap clap*
III - Going further
Since this unrooting method works with the "Universal Gingerbread Root (by StoneBoyTony)" (as a recall, you will find here: http://forum.xda-developers.com/showthread.php?t=1192122), this unrooting method may work on other devices (Mini, Ace, Pop, Fit) which have been rooted the same way.
Note we got access to the /system/app folder, where some unremovable applications of your carrier could be located. Take a look here. You will probably be able to remove them!
But you must root your phone
Since Sh is in the root package as well, don't you remove it too?
and after I unroot, I can safely OTA update correct? Or is unrooting necessary for safe OTA update.
Can this rooting method work for the Samsung Admire (SCH-R70)?????
I have tried flashing the Universal_BG_ROOT via recovery but I get stock at signature verification.
Can this other method work?
TriXin said:
Since Sh is in the root package as well, don't you remove it too?
Click to expand...
Click to collapse
True. I forgot to write it down. Thank you.
TriXin said:
and after I unroot, I can safely OTA update correct? Or is unrooting necessary for safe OTA update.
Click to expand...
Click to collapse
Rooting a phone (at least, for Android phones) means to allow user to be super-user => to use great powers on the phone.
I don't understand what do you mean by OTA update. But if the OTA update worked before rooting your phone, then unrooting your phone won't stop the OTA update to work.
marcos.lennis said:
Can this rooting method work for the Samsung Admire (SCH-R70)?????
Click to expand...
Click to collapse
If you used the Universal GB Root method, yes.
marcos.lennis said:
I have tried flashing the Universal_BG_ROOT via recovery but I get stock at signature verification.
Can this other method work?
Click to expand...
Click to collapse
stl5 (blaaaaah) or bml5, you have to root your phone. Check the first post, i say a word about rooting and unlocking. I think you have not made the difference yet.
If I use Root Explorer and remove those files then uninstall Root Explorer, would that work?
lypang said:
If I use Root Explorer and remove those files then uninstall Root Explorer, would that work?
Click to expand...
Click to collapse
I never used Root Explorer.
The goal here is to remove files contained in the zip file. If you can do that, so yes it should work.
I've downloaded the Andriod SDK but I have no idea how to do the adb shell. Where do I type this in? Sorry I'm new to this stuff.
I almost got it but it say's permission denied when I type "su" so I can't delete those files. Any reason why I'm getting this?
nevermind got it working. I had to allow the superuser on the phone.
Although the unroot was successful the phone still seems to be unlock. My sim card still works on it even though it should be locked to a different carrier.
Niitsu said:
I've downloaded the Andriod SDK but I have no idea how to do the adb shell. Where do I type this in? Sorry I'm new to this stuff.
Click to expand...
Click to collapse
Use CMD of windows! and search here for tutorials there are enaugh of it
unroot?
I've rooted my gio (gingerbread 2.3.5) with the update.zip method: http://forum.xda-developers.com/showthread.php?t=1111414. Can I unroot it with this method, or can I unroot it by just uninstalling superuser with titanium backup and then reboot? Maybe someone have another idea?
Has anyone been able to access the USB diagnostics on the 10? Usually it's ##3424## but it either changed or it's blocked. I tried multiple ROMs with same results.
Cakeor314 said:
Has anyone been able to access the USB diagnostics on the 10? Usually it's ##3424## but it either changed or it's blocked. I tried multiple ROMs with same results.
Click to expand...
Click to collapse
Use *#*#3424#*#*
purple patch said:
Use *#*#3424#*#*
Click to expand...
Click to collapse
Tried it. This gives you the functions test, not USB diagnostics.
Cakeor314 said:
Tried it. This gives you the functions test, not USB diagnostics.
Click to expand...
Click to collapse
Oh cool, that was just in memory lol. Can you use an app for diagnostic, not sure what you want to test. The only other one is *#*#4636#*#* I think.
purple patch said:
Oh cool, that was just in memory lol. Can you use an app for diagnostic, not sure what you want to test. The only other one is *#*#4636#*#* I think.
Click to expand...
Click to collapse
I don't think an app will work, thanks though. I'm trying to unlock the Canadian LTE bands. I just need to put the phone in USB diagnostics mode so I can use the modem tools on it.
Cakeor314 said:
Has anyone been able to access the USB diagnostics on the 10? Usually it's ##3424## but it either changed or it's blocked. I tried multiple ROMs with same results.
Click to expand...
Click to collapse
dude, i have the same question as you. i wanna enable the band 12 on my htc 10 unlocked version since i convert it to verizon RUU and sometimes wanna switch between my verizon and Tmobile sim cards. if i flash verizon RUU i cannot get band 12 but if i flash unlocked ruu i cannot get CDMA!!
---------- Post added at 09:21 AM ---------- Previous post was at 09:16 AM ----------
i am not sure whether this rom flash will work on that band problem but it says all carrier support
http://forum.xda-developers.com/htc-10/development/rom-21-02-viper10-1-0-0-tweaks-hub-t3379151
Has anyone figured out how to enable DM mode on the US Unlocked model? On Sprint and Verizon ##3424# works just fine.
Cakeor314 said:
Has anyone been able to access the USB diagnostics on the 10? Usually it's ##3424## but it either changed or it's blocked. I tried multiple ROMs with same results.
Click to expand...
Click to collapse
any luck on enabling diag mode on HTC 10?
i've tried the command bellow but its no luck.
Code:
adb shell
su
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/func_en
kenter said:
any luck on enabling diag mode on HTC 10?
i've tried the command bellow but its no luck.
Code:
adb shell
su
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/func_en
Click to expand...
Click to collapse
adb shell "su -c 'setprop sys.usb.config rndis,diag,modem'"
or
adb shell "su -c 'setprop sys.usb.config adb,diag,acm'"
b8engl said:
adb shell "su -c 'setprop sys.usb.config rndis,diag,modem'" or adb shell "su -c 'setprop sys.usb.config adb,diag,acm'"
Click to expand...
Click to collapse
thanks mate. but already move from HTC 10. i do appreciate that
b8engl said:
adb shell "su -c 'setprop sys.usb.config rndis,diag,modem'"
or
adb shell "su -c 'setprop sys.usb.config adb,diag,acm'"
Click to expand...
Click to collapse
that worked for my htc 10 being recognized by nvr tools
but how do i revert this command? or better say, how do i turn off diag mode, magisk seems to crash at viewing my logs because of this
cigarpill said:
that worked for my htc 10 being recognized by nvr tools
but how do i revert this command? or better say, how do i turn off diag mode, magisk seems to crash at viewing my logs because of this
Click to expand...
Click to collapse
just replace the last entries...
adb shell "su -c 'setprop sys.usb.config adb,diag,acm'"
adb shell "su -c 'setprop sys.usb.config mtp,adb'"
i want to enter diagnostic mode in LOS14.1, i use command:
setprop sys.usb.config diag,adb
but it didn't work, pls help me,thk
kirtikhurana said:
Use this
Click to expand...
Click to collapse
i have try,but nothing change
kirtikhurana said:
you should be rooted unless it won't work.
Click to expand...
Click to collapse
i rooted,but these command work for lenovo offical rom,such as 048,062,232,244,251,not on los,any suggestion?
kirtikhurana said:
before that command i told. write the two.
adb shell
su
then diag commands.
during these commands your phone will prompt to grant permissions. Tap OK/Yes on phone
*remember to check Android bebugging Is ON in developer settings.
Even if you're unsuccessful you're probably doing wrong.
Click to expand...
Click to collapse
bro,setprop should be root,i know it,i use successful in lenovo offical rom, i told you,my question is: why not work for los,can you check it?
Hi
I accedently pressed the update button, and it started downloading the s9 firmware update.
I paused it, but I can't seem to cancel it.
I tried restarting the phone, but it won't go away.
Cant find a way to remove the annoying notification.
Help?
Boot to recovery and clear CACHE
Necromancer3 said:
Hi
I accedently pressed the update button, and it started downloading the s9 firmware update.
I paused it, but I can't seem to cancel it.
I tried restarting the phone, but it won't go away.
Cant find a way to remove the annoying notification.
Help?
Click to expand...
Click to collapse
dont forget , Developer options and activate USB debugging
use adb shell (no need root) to uninstall this file com.wssyncmldm.apk
use this comands
adb start-server
adb shell
pm uninstall -k --user 0 com.wssyncmldm.apk
PeterParker said:
dont forget , Developer options and activate USB debugging
use adb shell (no need root) to uninstall this file com.wssyncmldm
use this comands
adb start-server
adb shell
pm uninstall -k --user 0 com.wssyncmldm
Click to expand...
Click to collapse
I did exactly as you instructed and got back
Failure [not installed for user 0]
Click to expand...
Click to collapse
Is there another file to uninstall?
overclockxp said:
I did exactly as you instructed and got back
Is there another file to uninstall?
Click to expand...
Click to collapse
Sorry, file name is com.wssyncmldm.apk, try it work very well for me
PeterParker said:
dont forget , Developer options and activate USB debugging
use adb shell (no need root) to uninstall this file com.wssyncmldm.apk
use this comands
adb start-server
adb shell
pm uninstall -k --user 0 com.wssyncmldm.apk
Click to expand...
Click to collapse
PeterParker said:
Sorry, file name is com.wssyncmldm.apk, try it work very well for me
Click to expand...
Click to collapse
I dont have anything with wssyncmldm in the name. I even paid for package Disabler pro and it said nothing existed with that in the name.
What version of the S9 are you using? I have the Verizon S9 model.
Thank you for your help with this.
overclockxp said:
I dont have anything with wssyncmldm in the name. I even paid for package Disabler pro and it said nothing existed with that in the name.
What version of the S9 are you using? I have the Verizon S9 model.
Thank you for your help with this.
Click to expand...
Click to collapse
My version is SM-G960F
I used Package disable pro and disabled anything that said system update and never had an update notification. The section for system update in settings even disappeared.
PeterParker said:
My version is SM-G960F
Click to expand...
Click to collapse
You have the European version. Lucky you can cancel the update.
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