Related
So I got my Galaxy Nexus, yay!
And I installed Android Revolution HD which has busybox and init.d script support.
I put Franco's latest kernel, and it goes smokin' fast.
But my undervolt settings dissapear each time I reboot, which makes me to have to reboot several times until it gets them.
I asked and got told to put a script into init.d that set the voltages.
Code:
echo "1250 1225 1175 775 750 750 725 700" > /sys/devices/virtual/misc/customvoltage/mpu_voltages
echo "750 750 600 600" > /sys/devices/virtual/misc/customvoltage/iva_voltages
echo "850 850 800" > /sys/devices/virtual/misc/customvoltage/core_voltages
So I did, but voltages are not set and it keeps overheating.
Does anyone have a better idea or know what's wrong here?
Thanks
try this one. don't forget to change the permission into 777 (rwxrwxrwx)
Code:
#!/system/bin/sh
echo "1250 1225 1175 775 750 750 725 700" > /sys/devices/virtual/misc/customvoltage/mpu_voltages
echo "750 750 600 600" > /sys/devices/virtual/misc/customvoltage/iva_voltages
echo "850 850 800" > /sys/devices/virtual/misc/customvoltage/core_voltages
kurotsugi said:
try this one. don't forget to change the permission into 777 (rwxrwxrwx)
Code:
#!/system/bin/sh
echo "1250 1225 1175 775 750 750 725 700" > /sys/devices/virtual/misc/customvoltage/mpu_voltages
echo "750 750 600 600" > /sys/devices/virtual/misc/customvoltage/iva_voltages
echo "850 850 800" > /sys/devices/virtual/misc/customvoltage/core_voltages
Click to expand...
Click to collapse
Thanks! running smooth!
Hello, I am wondering deciding whether or not I will buy the Fujitsu Arrows X, and it depends on whether I can have root on the phone or not.
I read on the internet that Goroh_Kun got root on the phone, but I am not experienced at rooting phones and ADB, so I cannot understand the source code and binary posted online, nor can I understand a guide of how he got root.
All I could tell was that root was gained for the phone through a vulnerability in "aeswipe" aka the fingerprint scanning thing. However, I cannot follow along with the steps, because I cannot understand it.
I don't know how to use the source code or binary for anything.
Will someone read the pages and summarize the steps for rooting the phone so I can understand it?
I cannot post URLs, so please reply if you need the URLs.
Sarcasticphoenix
Bump
Bumped post, need a reply.
!!!!!!!!!! Caution rooting can be risk your devices. !!!!!!!!!!!
!!!!!!!!!! CAUTION ROOTING CAN BE RISK YOUR DEVICES. !!!!!!!!!!!
YOU MUST HAVE TO KNOW WHAT YOU DO. BEFORE YOU MAKE A THING.
obtain root privileges on the f-10d
Things Require
1. Root Kit
2. ADB Driver For F-10D
3. PC With android SDK
4. Little Knowledge with linux command line
Things to do
Right click on folded you save extract of root kit. that you download
(1) On command prompt put command "adb restore f-10d_2.ab" without "…"
Press OK certification will appear on the screen
(2) You must verify that
(3) after restore is finished. Put command
> adb shell
$ cd / data / data / com.android.settings / a /
$ ls -l-d
drwxrwxrwx system system a
⇒ a directory that exists and is world readable, writable to
$ ls -l
⇒ up to file00 ~ file99 directory exists
(4) Once removed file00 ~ file99
> adb shell
$ cd /data/data/com.android.settings/
$ rm -r a
(Please go but out ※ error)
(5) Make /data permissions to 777. Input command.
$ while:; do ln -s /data a/file99; done
On your screen should infinite run.While doing this, open new command line. Don't closed running windows.
Now input command in new windows
>adb restore f-10d_2.ab
Confirm on your f-10d to complete the restore
After you have finished, exit the old infinite running windows
(6) Check the permissions on the /data
> adb shell
$ ls -l-d /data
drwxrwxrwx system system data
(7) Execute the following command
> adb push mkdevsh /data/local.org/tmp/mkdevsh
> adb shell chmod 777 /data/local.org/tmp/mkdevsh
(8) On or Off Wifi, and then execute
> echo /data/local.org/tmp/mkdevsh>/sys/kernel/uevent_helper
> adb shell
$ ls -l /dev/sh
-rwsr-sr-x root root 151964 2012-08-06 19:34 sh
$ /Dev/sh
# ************ Tempolary insecure root shell ************
(9) Copy lsm_disabler.ko and f10dunlock to /data/local
>adb push f10dunlock /sdcard
>adb push lsm_disabler.ko /sdcard
>dab shell
# dd if=/mnt/sdcard/f10dunlock of=/data/local/f10dunlock
# dd if=/mnt/sdcard/lsm_disabler.ko of=/data/local/lsm_disabler.ko
(10) release LSM lock
********* "x" and "y" is option for f10dunlock
For x=0 if you're on F-10D Build number V16R45C
x=1 if you're ISW13D Device
x=2 if you're on F-10D Build number V18R46F
IF you can't insert module lsm_disabler.ko after execute f10dunlock "x" you can add option "y" at last one example f10dunlock 0 2 or f10dunlock 0 1 and then try to insert module lsm_disabler.ko **********
# cd /data/local
# chmod 777 f10dunlock
# chown root.root / data/local/f10dunlock
# /data/local/f10dunlock x y
/data/local/f10dunlock
fdaes = -1
open aeswipe error, so try to disable LSM without recovery g_lptsAuthContext
fdaes2 = 3
use new F-10D address
# /data/local/f10dunlock 2
/data/local/f10dunlock 2
fdaes = -1
open aeswipe error, so try to disable LSM without recovery g_lptsAuthContext
fdaes2 = 3
# ./f10dunlock
./f10dunlock
fdaes = -1
open aeswipe error, so try to disable LSM without recovery g_lptsAuthContext
fdaes2 = 3
# lsmod
# mount-o rw, remount / system
mount-o rw, remount / system
# cd /system
cd /system
# chmod 777 / system
chmod 777 / system
# mkdir test
mkdir test
# ls-al
(11) Set su busybox
# sync; sync; sync
sync; sync; sync
# dd if=/mnt/sdcard/su of=/system/bin/su
dd if=/mnt/sdcard/su of=/system/bin/su
743 +1 records in
743 +1 records out
380532 bytes transferred in 0.079 secs (4816860 bytes / sec)
# chown root.shell /system/bin/su
chown root.shell /system/bin/su
# chmod 06755 /system/bin/su
chmod 06755 /system/bin/su
# sync; sync; sync
sync; sync; sync
# dd if=/mnt/sdcard/su of=/system/xbin/su
dd if=/mnt/sdcard/su of=/system/xbin/su
743 +1 records in
743 +1 records out
380532 bytes transferred in 0.034 secs (11192117 bytes / sec)
# chown root.shell /system/xbin/su
chown root.shell /system/xbin/su
# chmod 06755 /system/xbin/su
chmod 06755 /system/xbin/su
# sync; sync; sync
sync; sync; sync
# dd if = /data/local.org/tmp/busybox of=/system/xbin/busybox
dd if=/data/local.org/tmp/busybox of=/system/xbin/busybox
2099 +1 records in
2099 +1 records out
1075144 bytes transferred in 0.085 secs (12648752 bytes / sec)
# chown root.shell /system/xbin/busybox
chown root.shell /system/xbin/busybox
# chmod 04755 /system/xbin/busybox
chmod 04755 /system/xbin/busybox
# ls-al
ls-al
drwxr-xr-x root root 2012-09-01 03:31 app
drwxrwxrwx root shell 2012-09-01 23:59 bin
-rw-r - r - root root 4093 2012-09-01 03:31 build.prop
drwxr-xr-x root shell 2012-09-02 01:05 xbin
# cd /system/xbin
cd /system/xbin
# ls -al
ls -al
-rwxr-xr-x root shell 10028 2012-07-07 21:17 agent
-rwsr-xr-x root shell 1075144 2012-09-02 01:05 busybox
-rwxr-xr-x root shell 9780 2012-07-07 21:17 dbus-monitor
-rwxr-xr-x root shell 5708 2012-07-07 21:17 sdptest
-rwsr-sr-x root shell 380532 2012-09-02 01:03 su
#
(12) Set up SuperUser
Install from the market SuperSU etc..
k you must have permission to launch the app root, root authorization confirmation screen will appear if
Remark form me(yes, me not goroh_kun) : if you reboot your device. It's has re-lock /system. Even you have root access you can't remount /system to r/o until you re-execute f10dunlock. So you should think and plan by carefully that you want to move SuperSU.apk form /data/app to/system/app for more safer factory reset in future or not.
Thank you for the dear goroh_kun.
Ugh...what a convoluted process... I'm really on the edge about doing this.
I also heard that this causes the fingerprint reader to stop working. Can anyone confirm this? I use the fingerprint reader a lot so I'd hate to lose that functionality.
Hi,
thanks for the explanation.
But I am stuck at some point:
A. step (8) says on or off WiFi - what does this mean?
B. next, cannot output from mkdevsh to /sys/kernel/udev_helper: permission denied
mkdevsh cannot be executed, says error "syntax error: '^A' unexpected and /bin/sh is not available
C. lsm_disabler.ko is not supplied in ZIP file
Can you please help?`
Thanks
tuxsurfer said:
Hi,
thanks for the explanation.
But I am stuck at some point:
A. step (8) says on or off WiFi - what does this mean?
B. next, cannot output from mkdevsh to /sys/kernel/udev_helper: permission denied
mkdevsh cannot be executed, says error "syntax error: '^A' unexpected and /bin/sh is not available
C. lsm_disabler.ko is not supplied in ZIP file
Can you please help?`
Thanks
Click to expand...
Click to collapse
You manage to get this working? Just wondering as I have an F-10D on the way. I know you can disable a decent bit of bloatware with the ICS disable feature, but I want to disable all of the bloat, if possible.
Anyway, the process does seem simple enough, but the things pointed out above will keep me hesitant on this matter. Does "on or off WiFi", mean turn on and then off?
Thanks
tuxsurfer said:
Hi,
thanks for the explanation.
But I am stuck at some point:
A. step (8) says on or off WiFi - what does this mean?
Ohhhh, Excuse me right thing is " ON and then OFF WIFI" this the hole on android from Sony Ericsson X10
B. next, cannot output from mkdevsh to /sys/kernel/udev_helper: permission denied
mkdevsh cannot be executed, says error "syntax error: '^A' unexpected and /bin/sh is not available
Make sure "echo /data/local.org/tmp/mkdevsh > /sys/kernel/uevent_helper" without quote " " and this can operate after WIFI Hole step
C. lsm_disabler.ko is not supplied in ZIP file
for lsm_disabler.ko not required for the new method just unlocked
Can you please help?`
Thanks
Click to expand...
Click to collapse
I'm So Busy,Sorry for late answer.
tum.osx said:
!!!!!!!!!! CAUTION ROOTING CAN BE RISK YOUR DEVICES. !!!!!!!!!!!
YOU MUST HAVE TO KNOW WHAT YOU DO. BEFORE YOU MAKE A THING.
obtain root privileges on the f-10d
Things Require
1. Root Kit
2. ADB Driver For F-10D
3. PC With android SDK
4. Little Knowledge with linux command line
Things to do
Right click on folded you save extract of root kit. that you download
(1) On command prompt put command "adb restore f-10d_2.ab" without "…"
Press OK certification will appear on the screen
(2) You must verify that
(3) after restore is finished. Put command
> adb shell
$ cd / data / data / com.android.settings / a /
$ ls -l-d
drwxrwxrwx system system a
⇒ a directory that exists and is world readable, writable to
$ ls -l
⇒ up to file00 ~ file99 directory exists
(4) Once removed file00 ~ file99
> adb shell
$ cd /data/data/com.android.settings/
$ rm -r a
(Please go but out ※ error)
(5) Make /data permissions to 777. Input command.
$ while:; do ln -s /data a/file99; done
On your screen should infinite run.While doing this, open new command line. Don't closed running windows.
Now input command in new windows
>adb restore f-10d_2.ab
Confirm on your f-10d to complete the restore
After you have finished, exit the old infinite running windows
(6) Check the permissions on the /data
> adb shell
$ ls -l-d /data
drwxrwxrwx system system data
(7) Execute the following command
> adb push mkdevsh /data/local.org/tmp/mkdevsh
> adb shell chmod 777 /data/local.org/tmp/mkdevsh
(8) On or Off Wifi, and then execute
> echo /data/local.org/tmp/mkdevsh>/sys/kernel/uevent_helper
> adb shell
$ ls -l /dev/sh
-rwsr-sr-x root root 151964 2012-08-06 19:34 sh
$ /Dev/sh
# ************ Tempolary insecure root shell ************
(9) Copy lsm_disabler.ko and f10dunlock to /data/local
>adb push f10dunlock /sdcard
>adb push lsm_disabler.ko /sdcard
>dab shell
# dd if=/mnt/sdcard/f10dunlock of=/data/local/f10dunlock
# dd if=/mnt/sdcard/lsm_disabler.ko of=/data/local/lsm_disabler.ko
(10) release LSM lock
********* "x" and "y" is option for f10dunlock
For x=0 if you're on F-10D Build number V16R45C
x=1 if you're ISW13D Device
x=2 if you're on F-10D Build number V18R46F
IF you can't insert module lsm_disabler.ko after execute f10dunlock "x" you can add option "y" at last one example f10dunlock 0 2 or f10dunlock 0 1 and then try to insert module lsm_disabler.ko **********
# cd /data/local
# chmod 777 f10dunlock
# chown root.root / data/local/f10dunlock
# /data/local/f10dunlock x y
/data/local/f10dunlock
fdaes = -1
open aeswipe error, so try to disable LSM without recovery g_lptsAuthContext
fdaes2 = 3
use new F-10D address
# /data/local/f10dunlock 2
/data/local/f10dunlock 2
fdaes = -1
open aeswipe error, so try to disable LSM without recovery g_lptsAuthContext
fdaes2 = 3
# ./f10dunlock
./f10dunlock
fdaes = -1
open aeswipe error, so try to disable LSM without recovery g_lptsAuthContext
fdaes2 = 3
# lsmod
# mount-o rw, remount / system
mount-o rw, remount / system
# cd /system
cd /system
# chmod 777 / system
chmod 777 / system
# mkdir test
mkdir test
# ls-al
(11) Set su busybox
# sync; sync; sync
sync; sync; sync
# dd if=/mnt/sdcard/su of=/system/bin/su
dd if=/mnt/sdcard/su of=/system/bin/su
743 +1 records in
743 +1 records out
380532 bytes transferred in 0.079 secs (4816860 bytes / sec)
# chown root.shell /system/bin/su
chown root.shell /system/bin/su
# chmod 06755 /system/bin/su
chmod 06755 /system/bin/su
# sync; sync; sync
sync; sync; sync
# dd if=/mnt/sdcard/su of=/system/xbin/su
dd if=/mnt/sdcard/su of=/system/xbin/su
743 +1 records in
743 +1 records out
380532 bytes transferred in 0.034 secs (11192117 bytes / sec)
# chown root.shell /system/xbin/su
chown root.shell /system/xbin/su
# chmod 06755 /system/xbin/su
chmod 06755 /system/xbin/su
# sync; sync; sync
sync; sync; sync
# dd if = /data/local.org/tmp/busybox of=/system/xbin/busybox
dd if=/data/local.org/tmp/busybox of=/system/xbin/busybox
2099 +1 records in
2099 +1 records out
1075144 bytes transferred in 0.085 secs (12648752 bytes / sec)
# chown root.shell /system/xbin/busybox
chown root.shell /system/xbin/busybox
# chmod 04755 /system/xbin/busybox
chmod 04755 /system/xbin/busybox
# ls-al
ls-al
drwxr-xr-x root root 2012-09-01 03:31 app
drwxrwxrwx root shell 2012-09-01 23:59 bin
-rw-r - r - root root 4093 2012-09-01 03:31 build.prop
drwxr-xr-x root shell 2012-09-02 01:05 xbin
# cd /system/xbin
cd /system/xbin
# ls -al
ls -al
-rwxr-xr-x root shell 10028 2012-07-07 21:17 agent
-rwsr-xr-x root shell 1075144 2012-09-02 01:05 busybox
-rwxr-xr-x root shell 9780 2012-07-07 21:17 dbus-monitor
-rwxr-xr-x root shell 5708 2012-07-07 21:17 sdptest
-rwsr-sr-x root shell 380532 2012-09-02 01:03 su
#
(12) Set up SuperUser
Install from the market SuperSU etc..
k you must have permission to launch the app root, root authorization confirmation screen will appear if
Remark form me(yes, me not goroh_kun) : if you reboot your device. It's has re-lock /system. Even you have root access you can't remount /system to r/o until you re-execute f10dunlock. So you should think and plan by carefully that you want to move SuperSU.apk form /data/app to/system/app for more safer factory reset in future or not.
Thank you for the dear goroh_kun.
Click to expand...
Click to collapse
Anything for F-02E??
the same problem
Rudeyllah said:
Anything for F-02E??
Click to expand...
Click to collapse
I have the same problem with the same phone model,i tried to root but i'm stuck at 7.-permision denied and 8.-on and off wifi...i try all but i can't pass this steps......maybe the tutorial need more detail or maybe it is about diferences between versions of phone.
Build
The Root for F-10D has different Command for Rooting,depending BUILD on Device..
Option is different depending on the version and model.
F-10D build number V16R45C: → 0
ISW13D: → 1
F-10D build number V18R46F: → 2
F-10D build number V20R47F: → 3
My Device is V20R47F and the Following Command for V16R45C ... Cannot be use on V20R47F.. i always get Error after -7 ..
Can anyone help for V20R47F ?
CMD
C:> adb restore f-10d_2.ab
~ ~ ~ To allow restore ~ ~ ~ Android terminal
C:> adb shell
shell @ android :/ $ cd / data / data / com.android.settings / a /
cd / data / data / com.android.settings / a /
shell @ android :/ data / data / com.android.settings / a $ ls-l-d
ls-l-d
drwxrwxrwx system system 2011-01-01 09:09.
shell @ android :/ data / data / com.android.settings / a $ ls-l
ls-l
drwxrwxrwx system system 2011-01-01 09:09 file00
drwxrwxrwx system system 2011-01-01 09:09 file01
drwxrwxrwx system system 2011-01-01 09:09 file02
~ ~ ~ ~ ~ ~ Omitted
~ ~ ~ ~ ~ ~ Omitted
drwxrwxrwx system system 2011-01-01 09:09 file97
drwxrwxrwx system system 2011-01-01 09:09 file98
drwxrwxrwx system system 2011-01-01 09:09 file99
shell @ android :/ data / data / com.android.settings / a $ cd / data / data / com.android.settings /
com.android.settings / <
shell @ android :/ data / data / com.android.settings $ ls-l
ls-l
drwxrwxrwx system system 2011-01-01 09:09 a
drwxr-xr-x system system 2011-01-01 09:00 lib
shell @ android :/ data / data / com.android.settings $ rm-ra
rm-r a
rm failed for a, Permission denied
255 | shell @ android :/ data / data / com.android.settings $ while:; do ln-s / data a/file99; done
ln-s / data a/file99; done <
link failed File exists
link failed File exists
link failed File exists
~ ~ ~ Leaving the ~ ~ ~ endlessly
~ ~ ~ Leaving the ~ ~ ~ endlessly
~ ~ ~ ↓ ↓ ↓ ~ ~ ~ to open and run one more command line
C:> adb restore f-10d_2.ab
~ ~ ~ To allow restore ~ ~ ~ Android terminal
~ ~ ~ ↑ ↑ ↑ ~ ~ ~ to open and run one more command line
I made a restore link failed No such file or directory ← here
link failed No such file or directory
link failed No such file or directory
link failed No such file or directory
link failed No such file or directory
link failed No such file or directory
link failed No such file or directory
link failed No such file or directory
link failed No such file or directory
link failed No such file or directory
link failed No such file or directory
link failed No such file or directory
link failed No such file or directory
link failed File exists
link failed File exists
link failed File exists
~ ~ ~ Leaving the ~ ~ ~ endlessly
~ ~ ~ Leaving the ~ ~ ~ endlessly
^ I interrupted by C ← CTRL + C.
C:>
C:> adb shell
shell @ android :/ $ ls-l-d / data
ls-l-d / data
drwxrwxrwx system system 2011-01-01 09:11 data
shell @ android :/ $ exit
exit
C:> adb push mkdevsh / data / local / tmp /
2702 KB / s (648486 bytes in 0.234s)
C:> adb shell
shell @ android :/ $ ls-l-d / data / local
ls-l-d / data / local
drwxr-x - x root root 2011-01-01 09:00 local
shell @ android :/ $ ls-l-d / data / local / tmp
ls-l-d / data / local / tmp
drwxrwx - x shell shell 2011-01-01 09:12 tmp
shell @ android :/ $ ls-l / data / local / tmp
ls-l / data / local / tmp
-Rw-rw-rw-shell shell 648486 2012-09-01 03:47 mkdevsh
shell @ android :/ $ chmod 777 / data / local / tmp / mkdevsh
chmod 777 / data / local / tmp / mkdevsh
shell @ android :/ $ ls-l / data / local / tmp /
ls-l / data / local / tmp /
-Rwxrwxrwx shell shell 648486 2012-09-01 03:47 mkdevsh
shell @ android :/ $ mv / data / local / data / local.org
mv / data / local / data / local.org
shell @ android :/ $ ls-l / data / local.org / tmp
ls-l / data / local.org / tmp
-Rwxrwxrwx shell shell 648486 2012-09-01 03:47 mkdevsh
shell @ android :/ $ mkdir / data / local
mkdir / data / local
shell @ android :/ $ ls-l-d / data / local /
ls-l-d / data / local /
drwxrwxrwx shell shell 2011-01-01 09:12
shell @ android :/ $ ln-s / sys / kernel / uevent_helper / data / local / tmp
ln-s / sys / kernel / uevent_helper / data / local / tmp
shell @ android :/ $ ls-l / data / local / tmp
ls-l / data / local / tmp
lrwxrwxrwx shell shell 2011-01-01 09:12 tmp -> / sys / kernel / uevent_helper
shell @ android :/ $ exit
exit
C:> adb push su / data /
2972 KB / s (380532 bytes in 0.125s)
C:> adb reboot
C:> adb wait-for-device shell
echo / data / local.org / tmp / mkdevsh> / sys / kernel / uevent_helper
echo / data / local.org / tmp / mkdevsh> / sys / kernel / uevent_helper
sh> / sys / kernel / uevent_helper <
shell @ android :/ $
shell @ android :/ $ ls-l / sys / kernel / uevent_helper
ls-l / sys / kernel / uevent_helper
-Rwxrwx - x shell shell 4096 2011-01-01 09:00 uevent_helper
shell @ android :/ $ ls-l / dev / sh
ls-l / dev / sh
-Rwsr-sr-x root root 151964 2011-01-01 09:00 sh
shell @ android :/ $ ls-l / data / su
ls-l / data / su
-Rw-rw-rw-shell shell 380532 2008-02-29 02:33 su
shell @ android :/ $ / dev / sh
/ Dev / sh
# ← root Kita! (It takes a permanent root in the rewritable system area by the mount rw)
# Mount-o rw, remount / system / system
mount-o rw, remount / system / system
# Ls-l / system / bin / su
ls-l / system / bin / su
/ System / xbin / su: No such file or directory
# Dd if = / data / su of = / system / bin / su
dd if = / data / su of = / system / bin / su
743 +1 records in
743 +1 records out
380532 bytes transferred in 0.047 secs (8096425 bytes / sec)
# Chown root.root / system / bin / su
chown root.root / system / bin / su
# Chmod 06755 / system / bin / su
chmod 06755 / system / bin / su
# Ls-l / system / bin / su
ls-l / system / bin / su
-Rwsr-sr-x root root 380532 2011-01-01 09:01 su
# Ls-l / system / xbin / su
ls-l / system / xbin / su
/ System / xbin / su: No such file or directory
# Dd if = / data / su of = / system / xbin / su
dd if = / data / su of = / system / xbin / su
743 +1 records in
743 +1 records out
380532 bytes transferred in 0.045 secs (8456266 bytes / sec)
# Chown root.root / system / xbin / su
chown root.root / system / xbin / su
# Chmod 06755 / system / xbin / su
chmod 06755 / system / xbin / su
# Ls-l / system / xbin / su
ls-l / system / xbin / su
-Rwsr-sr-x root root 380532 2011-01-01 09:02 su
# Mount-o ro, remount / system / system
mount-o ro, remount / system / system
# Dd if = / data / su of = / system / bin / su
dd if = / data / su of = / system / bin / su
/ System / bin / su: cannot open for write: Read-only file system
# Rm / data / local / tmp
rm / data / local / tmp
# Mv / data / local / data / local.ln
mv / data / local / data / local.ln
# Mv / data / local.org / data / local
mv / data / local.org / data / local
# Ls-l-d / data / local *
ls-l-d / data / local *
drwxr-x - x root root 2011-01-01 09:00 local
drwxr-x - x root root 2011-01-01 09:02 local.ln
# Sync; sync; sync
sync; sync; sync
# Reboot
reboot
Click to expand...
Click to collapse
any significant improvements in battery life after rooting?
spec-wise it is a very good phone but i really regret the decision of buying this phone cos it heats up so fast and battery life is non-existent.
Rudeyllah said:
Anything for F-02E??
Click to expand...
Click to collapse
Can you please review this phone F-02E? I am really thinking of buying it.
How is the camera, battery life, screen, is the processor capable of working smoothly even with the full HD display, does it get unneccesarily hot, how is the build quality?
lapucele said:
any significant improvements in battery life after rooting?
spec-wise it is a very good phone but i really regret the decision of buying this phone cos it heats up so fast and battery life is non-existent.
Click to expand...
Click to collapse
I am in the same shoe as you with my F-02E, heat so fast and it restarts from 44 degrees centigrade.
Booting Fujitsu F-10D not powering on
My phone suddenly dosent power on. I tested the battery with a tester and it's fully charged. Anyone had a power problem with an Arrows X? Please help me!
The weird thing is I bought my phone at the same time as a friend and his phone stopped working a week ago also!!
When I press the power button, the red charging light blinks 3 time. Any debugging idea?Help me
Thanks
lythekhang said:
My phone suddenly dosent power on. I tested the battery with a tester and it's fully charged. Anyone had a power problem with an Arrows X? Please help me!
The weird thing is I bought my phone at the same time as a friend and his phone stopped working a week ago also!!
When I press the power button, the red charging light blinks 3 time. Any debugging idea?Help me
Thanks
Click to expand...
Click to collapse
I have the same problem too, mobile doesn't start.
When I press the power button, the red charging light blinks 3 time too.
Don't know what a problem, and how this fix.
can anyone confirm if this is working?
Using F-02E ones may work but don't do this. You can never get back when system files go wrong. I already turned mine to paperweight after reboot.
try this
Hi folks
I have Arrows X F-10D , I tried all methods to root it but no hope, I think the build number V22R49C is unrootable
Anyway I suggest to try this lovely program which I found in this site. http://www.mgyun.com/vroot
I have already attached the program, you can download it and give it a try if your build number is lower than above
try this too
Here is another program I have download it from here
help please
Guys help me please
I need DoCoMo apps system
I lost one app by mistake which is for DoCoMo account numbers
When I create new contact it shows me only Google account to save in, but no phone contacts
Please help
Somebody upload this app for me
This is the instruction originally posted by kevev in the other thread. I am reposting it here for others to find it easier.
--------------------------------------------------------------
1.) Root your device.
2.) Download to your device "overclock.zip" from this thread:
http://forum.xda-developers.com/showthread.php?t=1961989
3.) Install "AndroZip File Manager" from the Play store.
4.) Run AndroZip and browse to overclock.zip. (Probably /mnt/sdcard/Download .)
5.) tap on the file "overclock.zip" and select "Extract file here".
(A new directory named "overclock" is created)
6.) Install "ES File Explorer File Manager" from the Play store.
7.) Run ES File Explorer and press your "menu" button then select "settings".
8.) Change these settings:
Home Directory = /
Root settings --> Check all boxes
9.) Press the "back" button until the app exits.
10.) Run ES File Explorer again.
(Now your root partition "/" should be mounted with read/write permissions.
11.) Browse to the overclock directory. (Probably /mnt/sdcard/Download/overclock/ .)
12.) Long press on the cpu_control.ko file and a menu should open. Select "copy".
13.) Browse to the /system/lib/modules/ directory .
14.) Press "menu" button and select "Operations" then select "Paste" .
15.) Long press on the cpu_control.ko file and a menu should open. Select "Properties".
16.) Press "Change" and check the boxes like this:
User: read write
Group: read
Other: read
17.) Perform steps 12-17 on the symsearch.ko file which is also in the overclock directory.
18.) Install "Rom Toolbox Lite" from the Play store.
19.) Run ROM Toolbox Lite and select "Scripter".
20.) Press the "+" symbol in the top right corner and select "Create" to add the overclock script.
21.) Name it "overclock" or whaterver you wish.
22.) In the "Commands:" field enter this:
insmod /system/lib/modules/symsearch.ko
insmod /system/lib/modules/cpu_control.ko
echo 0 300 980 > /proc/cpu_control/tweak_cpu
echo 1 600 1200 > /proc/cpu_control/tweak_cpu
echo 2 800 1300 > /proc/cpu_control/tweak_cpu
echo 3 1200 1370 > /proc/cpu_control/tweak_cpu
23.) Your phone will overclock to 1.2Ghz.
If you wish to overclock higer you can try changing 1200 in the last line to 1300 for 1.3Ghz.
24.) Press the floppy disk in the top right corner to save the script.
25.) Press the overclock script and a menu will open. Select "Run Script".
If everything worked you should see an "exit valut:0" message.
If you run the script again you will see the same value but with a warning message.
This is normal since the modules are already loaded.
26.) You can load a cpu monitoring app to see if the overclocking works or just create another script that displays cpu clock info.
Here is the command for that script:
cat /proc/cpu_control/opp_table_current
27.) After making sure your device is stable you can have the overclock script run automatically at boot.
Press the "overclock" script and a menu will open.
Press "Set at boot"
Reboot the device and you will see a notification that the script ran in the notification area of the device at top.
All credits go to iodak and the thread created here: http://forum.xda-developers.com/show....php?t=1961989
I have been using slightly different apps to make the phone set to overclock automatically after a boot, I use 'SManager' app to edit and save the script (there is a free version) to run the script after a boot up.
Then I also use "CPU Master"(free version) to control the upper frequency set and the scaling method. I have been using 'interactive'.
With those two apps, the phone will boot up after a reset to the proper frequency and be ready to go automatically.
Try the following script if you want to try to push it to 1300MHz.
Code:
#! /system/bin/sh
insmod /system/lib/modules/symsearch.ko
insmod /system/lib/modules/cpu_control.ko
echo 0 333 830 > /proc/cpu_control/tweak_cpu
echo 1 666 1050 > /proc/cpu_control/tweak_cpu
echo 2 999 1150 > /proc/cpu_control/tweak_cpu
echo 3 1300 1340 > /proc/cpu_control/tweak_cpu
You can try 1220Mhz on 1270mV. For me it is more stable then on 1200Mhz and 1360mV.
luq529 said:
You can try 1220Mhz on 1270mV. For me it is more stable then on 1200Mhz and 1360mV.
Click to expand...
Click to collapse
Were you having problems at 1200MHz and 1360mV? I'm just curious how one determines one set up is more stable than the others.
I have tried running SetCPU stress tests before but that test either runs fine or ends with a lock up.
Thank You csrow for mentioning me.
My P769 would not run stable @ 1200Mhz so I removed the overclock. I may have bad hardware because it has been rebooting randomly at stock clock speeds. This is my 3rd L9. My wife is on her 3rd also.
csrow said:
Were you having problems at 1200MHz and 1360mV? I'm just curious how one determines one set up is more stable than the others.
I have tried running SetCPU stress tests before but that test either runs fine or ends with a lock up.
Click to expand...
Click to collapse
I don't know why. On this settings I have 8200 points in Antutu. Maybe 1220 Mhz is better for our processor.
my current stable voltages
Code:
echo 0 300 830 > /proc/cpu_control/tweak_cpu
echo 1 600 860 > /proc/cpu_control/tweak_cpu
echo 2 800 890 > /proc/cpu_control/tweak_cpu
echo 3 1000 950 > /proc/cpu_control/tweak_cpu
csrow said:
http://forum.xda-developers.com/show....php?t=1961989
Click to expand...
Click to collapse
Link is dead :'[
adixtra said:
my current stable voltages
Code:
echo 0 300 830 > /proc/cpu_control/tweak_cpu
echo 1 600 860 > /proc/cpu_control/tweak_cpu
echo 2 800 890 > /proc/cpu_control/tweak_cpu
echo 3 1000 950 > /proc/cpu_control/tweak_cpu
Click to expand...
Click to collapse
How do you do that ?! That's amazing from 1388 to 950. I will try it soon.
Jrkoffjonson said:
Link is dead :'[
Click to expand...
Click to collapse
Fixed the link. Try again.
Now we have full working CWM 6 for L9, is it by any chance possible to make flashable zip for overclocking and a zip for reverting back to default clock settings?
Which are the best settings to save more battery life??
Any way to overclock also gpu?
Does anyone know the default voltage for L9?
klhk said:
Does anyone know the default voltage for L9?
Click to expand...
Click to collapse
Here the default voltages.
echo 0 300 1025 > /proc/cpu_control/tweak_cpu
echo 1 600 1200 > /proc/cpu_control/tweak_cpu
echo 2 800 1325 > /proc/cpu_control/tweak_cpu
echo 3 1000 1388 > /proc/cpu_control/tweak_cpu
These are my voltages:
Code:
echo 0 300 830 > /proc/cpu_control/tweak_cpu
echo 1 600 830 > /proc/cpu_control/tweak_cpu
echo 2 800 840 > /proc/cpu_control/tweak_cpu
echo 3 1000 860 > /proc/cpu_control/tweak_cpu
They seems crazy low compared to stock but I tested them one by one (set governor to fixed frequency) and they were all stable for 20 minutes of stability test (classic test).
I verified they were successfully applied running "cat /proc/cpu_control/opp_table_current"
I played also fifa 12 for 15 minutes with interactive governor min 300 max 1000 and system was stable.
How can it be?
This is my setting, i will try lower voltage later.
echo 0 300 850 > /proc/cpu_control/tweak_cpu
echo 1 600 880 > /proc/cpu_control/tweak_cpu
echo 2 800 920 > /proc/cpu_control/tweak_cpu
echo 3 1000 1000 > /proc/cpu_control/tweak_cpu
Sent from my LG-P765 using xda app-developers app
I have V10H firmware and now overclock script don't work...It says:
Finished executing script file
exit value: 1
stdout:
null
stderr:
insmod: init_module '/system/lib/modules/symsearch.ko' failed (Exec format error)
insmod: init_module '/system/lib/modules/cpu_control.ko' failed (Exec format error)
/data/data/com.jrummy.liberty.toolboxpro/files/tmp.sh[4]: cannot create /proc/cpu_control/tweak_cpu: No such file or directory
/data/data/com.jrummy.liberty.toolboxpro/files/tmp.sh[5]: cannot create /proc/cpu_control/tweak_cpu: No such file or directory
/data/data/com.jrummy.liberty.toolboxpro/files/tmp.sh[6]: cannot create /proc/cpu_control/tweak_cpu: No such file or directory
/data/data/com.jrummy.liberty.toolboxpro/files/tmp.sh[7]: cannot create /proc/cpu_control/tweak_cpu: No such file or directory
what to do ?
wlado93 said:
I have V10H firmware and now overclock script don't work...It says:
Finished executing script file
exit value: 1
stdout:
null
stderr:
insmod: init_module '/system/lib/modules/symsearch.ko' failed (Exec format error)
insmod: init_module '/system/lib/modules/cpu_control.ko' failed (Exec format error)
/data/data/com.jrummy.liberty.toolboxpro/files/tmp.sh[4]: cannot create /proc/cpu_control/tweak_cpu: No such file or directory
/data/data/com.jrummy.liberty.toolboxpro/files/tmp.sh[5]: cannot create /proc/cpu_control/tweak_cpu: No such file or directory
/data/data/com.jrummy.liberty.toolboxpro/files/tmp.sh[6]: cannot create /proc/cpu_control/tweak_cpu: No such file or directory
/data/data/com.jrummy.liberty.toolboxpro/files/tmp.sh[7]: cannot create /proc/cpu_control/tweak_cpu: No such file or directory
what to do ?
Click to expand...
Click to collapse
Try running the insmod commands from the terminal and let us know what you see. Also, try replacing the modules. Maybe they are corrupt.
well, I downloaded new modules from link in 1st post modules L9 10h 1398mV 3.0.21-00001-gd335ca33.zip
now it works
Well ive done alot of searching and I am unable to find the info specific to the lg l9. Im currently running kumas rom so I am able to use the command
SU
./etc/overclock
This bumps me up to 1.2 ghz. Is there a method to go higher than 1.2ghz on a locked bootloader? If so can someone explain or post a link. It is also very annoying to have to type the command after each boot. Has anyone got this script to successfully run at boot without running it manually? I have used a few programs that auto runs scripts at boot. I gave it SU and boot permissions and It shows it under notifications that it does run at boot however under no frills cpu program it does not make the 1.2 available until after I manually run the script.THANKS!
lwg45714 said:
Well ive done alot of searching and I am unable to find the info specific to the lg l9. Im currently running kumas rom so I am able to use the command
SU
./etc/overclock.THANKS!
Click to expand...
Click to collapse
Write the script to init.d
Lgeob said:
Write the script to init.d
Click to expand...
Click to collapse
Do you have a link that tells how to do that or maybe explain? THAnks!
lwg45714 said:
Do you have a link that tells how to do that or maybe explain? THAnks!
Click to expand...
Click to collapse
Try to open the file overclock as text.What is written?
lwg45714 said:
Do you have a link that tells how to do that or maybe explain? THAnks!
Click to expand...
Click to collapse
Please take a look at this post
Edit: don't know why I miss a link in last post
http://forum.xda-developers.com/showthread.php?t=2096061
Lgeob said:
Try to open the file overclock as text.What is written?
Click to expand...
Click to collapse
IT says:
#!/system/bin/sh
ECHO 0 300 980> /PROC/CPU_CONTROL/TWEAK_CPu
ECHO 1 600 1200>/proc/cpu_control/tweak_cpu
ECHO 2 900 1260> /proc/ cpu_control/ tweak_ cpu
ECHO 3 1200 1340>/proc/cpu_control/ tweak_ cpu
If you use modules,try this,create a filepaste is:
Code:
#!/system/bin/sh
insmod /system/lib/modules/symsearch.ko
insmod /system/lib/modules/cpu_control.ko
echo 0 300 980> /proc/cpu_control/tweak_cpu
echo 1 600 1200> /proc/cpu_control/tweak_cpu
echo 2 900 1260> /proc/cpu_control/tweak_ cpu
echo 3 1200 1340> /proc/cpu_control/tweak_ cpu
Place it in the folder init.d
lwg45714 said:
IT says:
#!/system/bin/sh
ECHO 0 300 980> /PROC/CPU_CONTROL/TWEAK_CPu
ECHO 1 600 1200>/proc/cpu_control/tweak_cpu
ECHO 2 900 1260> /proc/ cpu_control/ tweak_ cpu
ECHO 3 1200 1340>/proc/cpu_control/ tweak_ cpu
Click to expand...
Click to collapse
I don't have it set at boot because the phone "might" lockup/freeze. In addition, some phones don't allow overclocking.
If you want it set at boot type the following in a terminal
Code:
su
mount -o remount /system
cp /etc/overclock /etc/init.d/
chmod 777 /etc/init.d/overclock
Or just use a root browser app to put it (overclock script) in the init.d folder.
Raising the CPU any higher won't improve performance and the phone will more than likely crash. If you dig through the l9 forums you will find a lot more information on the subject.
Oh and don't be afraid to ask questions in my thread
Lgeob said:
If you use modules,try this,create a filepaste is:
Code:
#!/system/bin/sh
insmod /system/lib/modules/symsearch.ko
insmod /system/lib/modules/cpu_control.ko
echo 0 300 980> /proc/cpu_control/tweak_cpu
echo 1 600 1200> /proc/cpu_control/tweak_cpu
echo 2 900 1260> /proc/cpu_control/tweak_ cpu
echo 3 1200 1340> /proc/cpu_control/tweak_ cpu
Place it in the folder init.d
Click to expand...
Click to collapse
I already have the modules loaded in another script.
Sent from my LGMS769 using XDA Premium 4 mobile app
I've had a few issues with Android 11. It actually temporarily bricked my device. There were certain root features I use that weren't working (mock location and such)... I used MSM to get back to 10, but now my device just auto updated to 11 even though I had auto updates disabled in the settings.
How do I completely block updates? I don't want 11 on this thing
KaptinBoxxi said:
I've had a few issues with Android 11. It actually temporarily bricked my device. There were certain root features I use that weren't working (mock location and such)... I used MSM to get back to 10, but now my device just auto updated to 11 even though I had auto updates disabled in the settings.
How do I completely block updates? I don't want 11 on this thing
Click to expand...
Click to collapse
I am in the same boat. Auto updated without any interaction from me, despite also freezing all system update related apps via debloater.
I am not opposed to updates, but I am opposed to FORCED updates that silently install without my permission or intervention.
I read somewhere that the updates are coming through Google Play SVCS. I am currently MSM'ing my phone back to 10 for the 5th day in a row and plan on immediately revoking all permissions and backround usage for Play SVCS - however, I am guessing this will severely limit the device.
Notes: Also unchecked Auto Updates in Dev options.
Anyone have any ideas to prevent and block these forced shenanigans?
Remove system updater apk from the system. Simple. Freezing alone doesn't work.
Mohamedkam000 said:
Remove system updater apk from the system. Simple. Freezing alone doesn't work.
Click to expand...
Click to collapse
Last time I removed any system priv-app apk, my device bricked lol and I think it was the updater.
I'll give that a shot. Right now, everything is working that wasn't before when I was 11, but If I go back, i'll do that
How do you have RW to the system? Every time I try I get errors via adb
asuhoops8628 said:
How do you have RW to the system? Every time I try I get errors via adb
Click to expand...
Click to collapse
Use a Root System App Uninstaller app. That should do it better than an adb uninstall
KaptinBoxxi said:
Use a Root System App Uninstaller app. That should do it better than an adb uninstall
Click to expand...
Click to collapse
It'll cause errors, too. Since the file system change in 10, and 11, I the System App Uninstaller is not compatible with R, it'll not work.
Use Root Explorer, I use it to manually erase what is not necessary. At least it's guaranteed.
so, it appears blocking redirector.gvt1.com in pihole and adaway prevents play svcs from resolving the DL links for the update.
All other solutions suggested here have not worked for me. I will update tomorrow morning if I am still on android 10 (my phone has been updating while I sleep from 12-3am every night).
Shoot, I too had auto update disabled, and my phone updated last night.
I lost root AND SafetyNet!
adb shell pm disable-user --user 0 com.oneplus.opbackup
I believe com.oneplus.opbackup is the package name for system updater apk.
and above command will disable, aka freeze it.
After that "system update" in settings->system will be grayed out.
This seems to work on many other 1+ phones per various xda/reddit posts,
so I hope it would be good for N10.
This event has led an almost two-week-now jihad against forced updates for me. I've definitely killed it (the auto-update) but took out GS as well. Can't confirm exactly which it is, but I am happy to show my work:
First, get NetGuard: https://f-droid.org/en/packages/eu.faircode.netguard/ NO ROOT REQUIRED and you can filter apps that phone home.
If you are comfortable re-flashing, some trial and error will get it. This is my list (assumes you know how to do ADB shell and have root) (you could also delete rather than move to SDCard, but I had some I killed that bricked it and wanted to revert w/o reflash):
Bash:
su
mount -o rw,remount /
mount -o rw,remount /product
mkdir /storage/emulated/0/bye
mv /product/app/Account /storage/emulated/0/bye/
mv /product/app/CalendarGoogle /storage/emulated/0/bye/
mv /product/app/Chrome /storage/emulated/0/bye/
mv /product/app/Drive /storage/emulated/0/bye/
mv /product/app/Duo /storage/emulated/0/bye/
mv /product/app/DynamicDDSService /storage/emulated/0/bye/
mv /product/app/Gmail2 /storage/emulated/0/bye/
mv /product/app/GoogleContacts /storage/emulated/0/bye/
mv /product/app/GoogleContactsSyncAdapter /storage/emulated/0/bye/
mv /product/app/GoogleLocationHistory /storage/emulated/0/bye/
mv /product/app/GooglePay /storage/emulated/0/bye/
mv /product/app/GoogleTTS /storage/emulated/0/bye/
mv /product/app/Maps /storage/emulated/0/bye/
mv /product/app/Messages /storage/emulated/0/bye/
mv /product/app/Photos /storage/emulated/0/bye/
mv /product/app/Videos /storage/emulated/0/bye/
mv /product/app/YTMusic /storage/emulated/0/bye/
mv /product/app/YouTube /storage/emulated/0/bye/
mv /product/app/remoteSimLockAuthentication /storage/emulated/0/bye/
mv /product/app/remotesimlockservice /storage/emulated/0/bye/
mv /product/priv-app/AndroidAutoStub /storage/emulated/0/bye/
mv /product/priv-app/CarrierServices /storage/emulated/0/bye/
mv /product/priv-app/ConfigUpdater /storage/emulated/0/bye/
mv /product/priv-app/GoogleDialer /storage/emulated/0/bye/
mv /product/priv-app/GoogleFeedback /storage/emulated/0/bye/
mv /product/priv-app/GoogleOneTimeInitializer /storage/emulated/0/bye/
mv /product/priv-app/GooglePartnerSetup /storage/emulated/0/bye/
mv /product/priv-app/GoogleRestore /storage/emulated/0/bye/
mv /product/priv-app/HotwordEnrollmentOKGoogleHEXAGON /storage/emulated/0/bye/
mv /product/priv-app/HotwordEnrollmentXGoogleHEXAGON /storage/emulated/0/bye/
mv /product/priv-app/OPAppLocker /storage/emulated/0/bye/
mv /product/priv-app/SetupWizard /storage/emulated/0/bye/
mv /product/priv-app/Velvet /storage/emulated/0/bye/
mv /product/priv-app/Wellbeing /storage/emulated/0/bye/
mv /product/priv-app/OobConfig /storage/emulated/0/bye/
mv /product/priv-app/Turbo /storage/emulated/0/bye/
mv /product/priv-app/Phonesky /storage/emulated/0/bye/
mv /product/priv-app/GmsCore /storage/emulated/0/bye/
mv /system/app/BackupRestoreRemoteService /storage/emulated/0/bye/
mv /system/app/CompanionDeviceManager /storage/emulated/0/bye/
mv /system/app/OPLocalUpdate /storage/emulated/0/bye/
mv /system/app/GoogleAssistant /storage/emulated/0/bye/
mv /system/app/GooglePrintRecommendationService /storage/emulated/0/bye/
mv /system/app/NVBackupUI /storage/emulated/0/bye/
mv /system/app/OPAppUpgrader /storage/emulated/0/bye/
mv /system/app/OPOnlineConfig /storage/emulated/0/bye/
mv /system/app/OPPush /storage/emulated/0/bye/
mv /system/app/PlayAutoInstallConfig /storage/emulated/0/bye/
mv /system/app/TSDM /storage/emulated/0/bye/
mv /system/app/OPBreathMode /storage/emulated/0/bye/
mv /system/priv-app/DynamicSystemInstallationService /storage/emulated/0/bye/
mv /system/priv-app/OnePlusGallery /storage/emulated/0/bye/
mv /system/priv-app/OnePlusWizard /storage/emulated/0/bye/
mv /system/priv-app/AmazonMDIP /storage/emulated/0/bye/
mv /system/priv-app/TagGoogle /storage/emulated/0/bye/
mv /system/priv-app/OPDeviceManager /storage/emulated/0/bye/
mv /system/priv-app/OPDeviceManagerProvider /storage/emulated/0/bye/
mv /system/reserve/OPBackupRestore /storage/emulated/0/bye/
mv /system/reserve/OPForum /storage/emulated/0/bye/
mv /system/reserve/OPNote /storage/emulated/0/bye/
mv /system/reserve/OPSoundRecorder /storage/emulated/0/bye/
mv /system/reserve/OnePlusPods /storage/emulated/0/bye/
Now the reason this took so long is I have a bunch of (paid) apps that all link to GS and verify I bought it... so I need to find OSS replacements (F-droid et al) for a lot of them. Additionally, most of the custom roms come with AOSP apps for dialer, contacts, etc... the list above kills the OnePlus ones but does not replace them.
Hope the above helps someone!
@arda99 Definitely can confirm that having system updates greyed out does NOT prevent this upgrade! This is with the SIM out of the phone (but WiFi connected), so can't be a carrier push.
Google Services was giving me update nags, but they could be ignored (nothing forced successfully until the A11 reflash).
SomeRandomGuy said:
@arda99 Definitely can confirm that having system updates greyed out does NOT prevent this upgrade! This is with the SIM out of the phone (but WiFi connected), so can't be a carrier push.
Google Services was giving me update nags, but they could be ignored (nothing forced successfully until the A11 reflash).
Click to expand...
Click to collapse
You're right...my phone upgraded to 11 few days ago when on charger. Did another MSM back to 10 and this time I uninstalled the package instead of disable.
Frustrating, isn't it, @arda99 ? I turned it into a game. Wasted almost two weeks of calendar time, but i just sped up the inevitable... a nearly 100% FOSS fone now, free from forced upgrades for the moment. I'd still bet it is a GS thing.
Now I just need to figure out how carriers can push stuff (like how APNs get set automatically after plugging in a different SIM... what else can they set, modify, or disable?)
Got update notice again...Found another update service in Google Play Service. Need root to disable it.
Code:
adb shell
su
pm disable com.google.android.gms/com.google.android.gms.update.SystemUpdateActivity
But see, here's the thing that terrifies me. If you have a fully functional, logged in (to Google) running phone, you can go to the play store online, and push something to your phone. Think about that. Poof, a minute later, there is code on your phone without any confirmation needed.
So what is stopping OTHER stuff from coming down that way? The kind hearts and souls keeping integrity at our dear billionaire company ?
I'm loving that MicroG lets you un-register applications from getting messages. Still tweaking my install - some of the OnePlus stuff seems to be miles ahead of the f-droid options (like dialer... damn, does no one that writes dialer software ever get a spam call and have a blocklist? Ditto for messages... QKSMS is nice but blacklist blacklist blacklist.... sigh)... but I will get there.
Lets all be thankful for an actual OSS community, and that we still have options for sideloading unlike that OTHER phone ecosystem with no freedom at all...
arda99 said:
Got update notice again...Found another update service in Google Play Service. Need root to disable it.
Code:
adb shell
su
pm disable com.google.android.gms/com.google.android.gms.update.SystemUpdateActivity
Click to expand...
Click to collapse
My phone auto-updated itself to Android 11 at the beginning of August. Went through and disabled what I could right then and thought that was the end of it.
Today I saw another one of those white "Your system is out of date" prompts and sat right down to do some more digging.
Just disabled this service and the com.oneplus.opbackup you mentioned higher in the thread via ADB. Hopefully this time I got it all.
thanks everyone for the answers. I've disabled everything here and haven't had a popup in awhile
Although I might be switching to a OP7 Plus 5G GM1925 if I can get it rooted... everything I flash to it freezes it and bricks it. I gotta figure out why