So I just flashed the stock rom got it rooted. My goal is to play Pokemon go and spoof. And I don't really want a custom rom as I've had issues with my pixel and custom roms (compared to my other phones)
Alright so here's what I tried so far.
Use link2sd to move app to the system but I get a error.
Tried using a mounting app for rw but that didn't work.
Cannot install BusyBox just gives a error.
Tried using a terminal but I got this error
sailfish:/ $ su
sailfish:/ # mount -o rw,remount /system
mount: '/system' not in /proc/mounts
1|sailfish:/ #
I even tried just copying to the APK file into system/app/fakegps and did the proper permissions and reboot. The app works but I still can't do the setting for system app mode and Pokemon go won't work with the mock gps either. Anybody have an answer as I googled for a good 3 hours and no solution.
Screenshots here
dropbox.com/sh/geoji93876bvk4w/AAD_rF5FfRPO5mPyLb6cXAcxa?dl=0
Related
Hi,
I just bought a cheap simple ARNOVA84 tablet (for 50 €) with android 2.1 to play a little bit and gather experience regarding rooting before I do this on my acer A511
I came so far, that I got adb shell with root ($ -> #). But to get SuperUser or SuperSU running I need also su in /system/bin. But /system is ro. The command
# mount -o rw,remount /dev/mtdblock4 /system
does not work in any combination. I get no error, but
# mount
still shows /system ro
To remount /system google said, I would need su, which in turn I don't have yet I copied su binary to another folder and changed permission to 755. But nevertheless su seems not to work. It just gives me new line with no # and everything I type in, is repeated. I have to break shell with ctrl-c.
The /system is a cramfs and my latest information is, that cramfs is always ro and can not be changed.
1. Is this true and does it mean I can root my tablet only be upgrading it with a modified update.img containing su etc.?
2. Is there no other more safe way to root such device?
3. Does this also mean more modern tablets have another filesystem for /system?
thanks!
Rainer
I have a Sony xperia M2 D2303 with kitkat 4.4.4 and compilation number 18.3.1.C.1.17.
I have successfully rooted it using KingRoot v4.9.5.
Also I have checked that system is rooted using tools such as root checker and it says rooted.
Now, I am trying to remount /system partition as RW but without succcess.
I have googled and tried several solutions posted here but nothing works for me.
Access to /sys/kernel/security/sony_ric and try to disable sony ric security using:
problem here is that sony_ric folder is empty, I mean, there is no "enable" file and I cannot create it as partition is RO (read-only).
Using ES file explorer or other file explorers as root I have tried to remount partition as RW but it fails.
Code:
echo 0 > enable
Using ROM Toolbox pro, and then from terminal emulator I have tried some commands:
Code:
su
mount -o remount,rw /system
fails.
Code:
su
system/bin/mount -o remount,rw /system
also fails.
Code:
adb shell
su
mount -o rw,remount /system
also fails...
I have tried to install busybox but it fails as well.
I have tried the method explained here but when executing the command:
sh /sdcard/mrw/root.sh
some errors appear as script tries to do things in /system so since it is read-only (not rw) it fails.
Also I have tried the method using SuperSu-me explained here but without success. It completes ok but then SuperSu is executed automatically. SuperSu says to update binaries so I update binaries, then another screen comes saying that another root app was detected, so I press the button to uninstall it and continue installing SuperSu. SuperSu says "Installing ........" and then it crashes, that is, it appears a screen with two buttons, "How to update" and "Reboot". Kingroot, purify apps continued installed and working, and I cannot replace them with SuperSu.
So at this point I have no idea what to do...
My conclusion is that all these tools need to make changes to / and /system but since I have these two partitions set to read-only (cannot make them rw) then all these tools fail. So I think the main cause is that I have / and /system readonly.
Any help will be highly appreciated.
Please, help!
For some reason I have never been able to mount my system r/w through adb or terminal emulator. I'm not quite sure what I'm doing wrong since I've been doing it for years now. I imagine it has to do with root. I can use ES file explorer and modify system to my hearts content just not through adb or terminal emulator. I am on 7.1.1 Pure Nexus with ElementalX 1.08 and SuperSU with 2.79 binaries. I've tried to mount multiple different ways and all result in same error.
Code:
sailfish:/ # mount -o remount,rw /system
mount: '/dev/block/bootdevice/by-name/system_b'->'/system': Device or resource busy
Nvm found it. I guess it's same as Pixel C.
Code:
mount -o rw,remount /system
Geofferey said:
For some reason I have never been able to mount my system r/w through adb or terminal emulator. I'm not quite sure what I'm doing wrong since I've been doing it for years now. I imagine it has to do with root. I can use ES file explorer and modify system to my hearts content just not through adb or terminal emulator. I am on 7.1.1 Pure Nexus with ElementalX 1.08 and SuperSU with 2.79 binaries. I've tried to mount multiple different ways and all result in same error.
Code:
sailfish:/ # mount -o remount,rw /system
mount: '/dev/block/bootdevice/by-name/system_b'->'/system': Device or resource busy
Click to expand...
Click to collapse
Same here but with Oneplus 3T.
I think its kind of encripted "new way" in Android 7.1.1
Also, if you check the magisk thread there is a way to use the mount remount command inside root browser
mate9-109 said:
Same here but with Oneplus 3T.
I think its kind of encripted "new way" in Android 7.1.1
Click to expand...
Click to collapse
Nope just a different mount syntax not encrypted at all. I was kinda thinking same at first like a security feature or root keeping you from so you don't accidentally modifying system.
mount -o rw,remount /system
Instead of
mount -o remount,rw /system
Geofferey said:
Nope just a different mount syntax not encrypted at all. I was kinda thinking same at first like a security feature or root keeping you from so you don't accidentally modifying system.
mount -o rw,remount /system
Instead of
mount -o remount,rw /system
Click to expand...
Click to collapse
Sadly I tried your new syntax, adb did some stuff, but it does not work either.
Anyway thank you very much, your solution almost got it.
:good::good::good::good::good:
Hello,
I have root and busybox on my Pixel, but AdAway is failing to copy the hosts file, and I am unable to modify permissions of the system folder. I just keep getting the error "operation failed" using Solid File Explorer.
Anyone know why? I obviously have root access, why am I being denied?
SubjectGinger said:
Hello,
I have root and busybox on my Pixel, but AdAway is failing to copy the hosts file, and I am unable to modify permissions of the system folder. I just keep getting the error "operation failed" using Solid File Explorer.
Anyone know why? I obviously have root access, why am I being denied?
Click to expand...
Click to collapse
was it working on any other android O developer preview releases ?
my best guess is that android O is using toybox instead of toolbox for mount and it matters in what orders the parameters are passed to the mount command.
mount -o remount,rw /system was working in 7.1.2 , but it is not working on 8.0, it must be mount -o rw,remount /system
the app developers will have to change the command in their apps...
of course this is only a wild guess, because there can be a lot of other reasons, this just something that I stumbled upon and got help with here on XDA. (thanks again @jcmm11 !!!)
Make sure you have the newest version of Chainfires SuperSU for pixel that fixes the system mounting
Just go to preferences and tick " enable systemless mode"
i am trying to remount system as -rw but cannot do so. i want to install a few apps as system but you can see my problem. when i do it through terminal emulator it says "mount: '/dev/block/sda22' ->' /system': Device or resource busy
anyone?