Related
Hi guys,
i've rooted my girlfriend's Galaxy Ace with the universal v25.zip system.
Now if i run Root Checker it seems to be rooted perfectly, i got all green signs. But when for example i run some Root Needing apps such as System App Remover it says that System is not mounted. On my Optimus Black i can see this software says:
Root: Found
System: Mounted
Busybox: Found (Enabled)
on my GF's Ace it says
Root: Found
System: Not Mounted
Busybox: Found (Enabled)
how to solve this? This thing seems to cause problems to other root needing software like Gemini App Manager, when i try to block the autorun of some apps it hangs... it seems to be related to the same System Not Mounted.
Oh i forgot, another problem that i get is that when i open SuperSU it tries to update the binaries but then it says it's impossible to update...
thank you in advance for your help
[[[[ maybe wrong part of the forum to ask, if so, i ask moderator to close-delete the thread. thank you and sorry for this ]]]]
Root the ace again
Sent from my GT-S5830 using xda app-developers app
same method? or should i try a different root zip? (like that upd1.zip method)?
angelox82 said:
same method? or should i try a different root zip? (like that upd1.zip method)?
Click to expand...
Click to collapse
Try any
Sent from my GT-S5830 using xda app-developers app
at last i did it... dunno why but the V25 method didn't work, whatever i do (it's on stock 2.3.6 rom), so unrooted and then used the upd_1.zip method and now with superuser (the other puts superSU) i got full root and that app i tried to test says the system is mounted.
thank you for the support jumper
Hey there,
this is my first thread ever created by me in a development forum.
I wanted to share my sollution for a adfree Android system, without unlocking the boatloader to get R/W access to /system.
I did try it on my device, everything went fine, but i will not take any kind of reponsibility for your devices. Also your warranty may be void!
What you need:
- rooted XTZ (i tried it on the 16GB Wifi only version)
- busybox installed
- Android SDK or adb.exe
- patched hosts file, I took mine from my HTC ONE with adaway installed (unzip first)
Click to expand...
Click to collapse
How to do it:
- get a patched hosts file from another device, or use mine (attached)
- put the file on the root of your sd card (so it will be /sdcard/hosts)
- connect your tablet to your PC, make sure usb debuggig is turned on
- launch cmd window, where your adb.exe is located
- entering following commands:
Code:
0. adb shell
1. su
2. stop ric
3. busybox pkill -f /sbin/ric
4. mount -ro remount,rw /system
5. busybox cp -af /sdcard/hosts /system/etc/hosts
- if everything went ok, you should now be able to see all the entries in your /system/etc/hosts file
- sadly you have to update the file if there some new adhosts, but it will remove a lot of annoying ads from all apps and the browser
- the changes are permanent, even at a reboot
Click to expand...
Click to collapse
Just let me know, if you have some kind of questions!
thanks @juanyunis for the [TEMPORAL-FIX] Remount RW /system reboot thread, from which i got some ideas.
Greetings from Germany
I have been using the AdAway app continuously since Google decided to eliminate all ad blocking apps from its Play Store and from my experience, AdAway does not require an unlocked boot loader to work, it only requires root access, and AdAway has no problem installing a hosts file in the /system/etc directory, so I am curious about why you have to go through all that.
The problem is, that if you using vroot like i did, and you doing nothing else, you don't have read write access to /system. So adaway, adfree and whatever can't edit the hosts file. Therefore is my little mod to get it done manually
Havoc2k said:
The problem is, that if you using vroot like i did, and you doing nothing else, you don't have read write access to /system. So adaway, adfree and whatever can't edit the hosts file. Therefore is my little mod to get it done manually
Click to expand...
Click to collapse
after vroot, install SuperSU and then all app ad-blocking apps are working good.
nope sorry, i did it, installed vroot, switched to normal superSU and installed busybox. But there is no RW access, so the ad blocking apps will work, but only to the next systemreboot / userswitch
tried all of them, and tried to manually edit the host file, but without access it will not happen
greetings
Havoc2k said:
But there is no RW access
Click to expand...
Click to collapse
strange thing that with root there is no RW access.
Havoc2k said:
nope sorry, i did it, installed vroot, switched to normal superSU and installed busybox. But there is no RW access, so the ad blocking apps will work, but only to the next systemreboot / userswitch
tried all of them, and tried to manually edit the host file, but without access it will not happen
greetings
Click to expand...
Click to collapse
I have tested and have for several months ran AdAway on my XTZ, on which Vroot was used to gain root access and SuperSU is installed, and AdAway has no problem writing a hosts file to the /system/etc directory even though the permissions for the /system and /system/etc directories are set to read-only. So, because I have no problem with AdAway and you apparently have a problem with AdAway, I believe it is likely there is a flaw in your root access setup. But hey, I could be wrong.
Hi,
Tried Everything, But neither ADB works nor root. Only flashing can write to system.
Used all sorts of techniques to mount /system as rw, but failed.
Using latest Rooted stock ROM(4.4.4 - 14.4.A.0.108) on my z1. Xposed Framework is also installed (flashed obviously as the system mount was not working)
As I am not able to write to system, unable to install the modded Google play (MOD EDIT, MENTION OF WAREZ IS STRICTLY FORBIDDEN IN XDA)
The app Busybox Installer was also unable to install the busybox, so flashed the latest busybox.
Used all sort of commands to make system rw using adb but none worked. Neither any app to mount /system in Play store did.
Flash tool was also unable to edit permissions to rw.
Please Help!!
Thanking XDA users and developers in advance
Warm Regards
Niraj
What tool did you use to root your phone?
Perhaps you can try re-rooting using rootkitXperia tool.
pkhrlniraj said:
Hi,
Tried Everything, But neither ADB works nor root. Only flashing can write to system.
Used all sorts of techniques to mount /system as rw, but failed.
Using latest Rooted stock ROM(4.4.4 - 14.4.A.0.108) on my z1. Xposed Framework is also installed (flashed obviously as the system mount was not working)
As I am not able to write to system, unable to install the modded Google play
The app Busybox Installer was also unable to install the busybox, so flashed the latest busybox.
Used all sort of commands to make system rw using adb but none worked. Neither any app to mount /system in Play store did.
Flash tool was also unable to edit permissions to rw.
Please Help!!
Thanking XDA users and developers in advance
Warm Regards
Niraj
Click to expand...
Click to collapse
Hi ,I had the very same problem a few weeks ago.
Solution... for me, was flashed stock 108 ftf and re-rooted using the latest version of Easy Root . I used V11.
Install SDFix: KitKat app from play store. And you should be good.
I would suggest you do not have root.
Check if you have killed the ric.
Goto sys/kernel/security/Sony_ric and see if the file called enable says 0 or 1. Also check it just after a reboot.
If it's a 1 you will lose write permissions to the system partition after a reboot, which explains the symptoms you are talking about.
Sent from my C6903 using XDA Premium 4 mobile app
gregbradley said:
I would suggest you do not have root.
Check if you have killed the ric.
Goto sys/kernel/security/Sony_ric and see if the file called enable says 0 or 1. Also check it just after a reboot.
If it's a 1 you will lose write permissions to the system partition after a reboot, which explains the symptoms you are talking about.
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi, Sorry for mistake in post as I was a bit unaware about the same.
Also, I would request you to help me in in changing the value of Enable to 0 as it is showing 1 now.
Thanking you in advance.
Flash this https://www.dropbox.com/s/hvzh6ztcuur3vzw/disable_ric_file.zip
Sent from my C6903 using XDA Premium 4 mobile app
gregbradley said:
Flash this https://www.dropbox.com/s/hvzh6ztcuur3vzw/disable_ric_file.zip
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the support.
Problem is solved, How can I close this thread?
gregbradley said:
I would suggest you do not have root.
Check if you have killed the ric.
Goto sys/kernel/security/Sony_ric and see if the file called enable says 0 or 1. Also check it just after a reboot.
If it's a 1 you will lose write permissions to the system partition after a reboot, which explains the symptoms you are talking about.
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you. Got my problem sorted out by changing 1 to 0.
Kjaups said:
Thank you. Got my problem sorted out by changing 1 to 0.
Click to expand...
Click to collapse
You will need to see if it sticks after a reboot though... if not you need to flash the disable-RIC zip
gregbradley said:
You will need to see if it sticks after a reboot though... if not you need to flash the disable-RIC zip
Click to expand...
Click to collapse
Somekind Disable_ric i already used and it ended with sdcard unreadable, so reverted and changed 1 to 0 and still rock solid
i was facing the same problem, a solution for it is to download an older version of busybox, the bb frm playstore(latest one) doesn't seems to work, i m using older bb pro....it sorted the issue..mounted rw /system...
hope it will help you.
using bb 9.2 pro though.
I'm rooted with SuperSU 2.79 systemless on OOS 4.1.0 and I can't get permission to write on /system.
I tried using ES FIle Explorer and the option keeps changing to RO. I also tried via recovery. Root permissions are granted and It's properly root.
Any clues?
belumira said:
I'm rooted with SuperSU 2.79 systemless on OOS 4.1.0 and I can't get permission to write on /system.
I tried using ES FIle Explorer and the option keeps changing to RO. I also tried via recovery. Root permissions are granted and It's properly root.
Any clues?
Click to expand...
Click to collapse
I had the same issue. I don't remember what I did. Try uninstalling super su from the app and then install it again.
Migdilu said:
I had the same issue. I don't remember what I did. Try uninstalling super su from the app and then install it again.
Click to expand...
Click to collapse
Did that, I even clean flashed OOS again nothing seems to be working.
belumira said:
I'm rooted with SuperSU 2.79 systemless on OOS 4.1.0 and I can't get permission to write on /system.
I tried using ES FIle Explorer and the option keeps changing to RO. I also tried via recovery. Root permissions are granted and It's properly root.
Any clues?
Click to expand...
Click to collapse
I also had problem with ES File Explorer while writing to system. Try solid Explorer. It's better
Vaibhunk786 said:
I also had problem with ES File Explorer while writing to system. Try solid Explorer. It's better
Click to expand...
Click to collapse
Still nothing. For some reason permissions won't change.
You have systemless root?
If yes I think you can only modify data Partition. Maybe you need a magisk module?
Remove superSU and just go with Magisk. It works much better than SuperSU ever will. It's easily removable and won't adjust partition permissions, including system. Make sure you mount system in twrp before flashing any root access zip file as well. It helps prevent problems like this.
Fix To Grant ES File Explorer SuperSU Access Using Terminal Emulator
Start Terminal Emulator. Type su.
ENTER EXACTLY LIKE THIS: echo "BINDSYSTEMXBIN=true" >> /data/.supersu
Spaces.......................................................................................... ^....^.........
Make a backup first incase ****e goes south... This has worked for me on a couple of devices.
Standard disclaimer... Yada...
I have the same problem.
jhill110 said:
Fix To Grant ES File Explorer SuperSU Access Using Terminal Emulator
Start Terminal Emulator. Type su.
ENTER EXACTLY LIKE THIS: echo "BINDSYSTEMXBIN=true" >> /data/.supersu
Spaces.......................................................................................... ^....^.........
Make a backup first incase ****e goes south... This has worked for me on a couple of devices.
Standard disclaimer... Yada...
Click to expand...
Click to collapse
Sorry but I dont understand what I have to write, I understand type su
and type echo "BINDSYSTEMXBIN=true" >> /data/.supersu
but whats mean:
Spaces.......................................................................................... ^....^.........
Mean: ^ ^
doesnt mean anything? :crying::crying:
Hi, long story short, I want to make some apps system apps with Link2SD.
I tried using LO14 or some other LO14 based rom and just can't. I read som ewhere that it may be because I have no permissions to write on the system folder. I tried starting TWRP wizard again and setting it to be able to write with no success.
Any help?
I am rooted with magisk working just fine.
thanks!
groggycl said:
Hi, long story short, I want to make some apps system apps with Link2SD.
I tried using LO14 or some other LO14 based rom and just can't. I read som ewhere that it may be because I have no permissions to write on the system folder. I tried starting TWRP wizard again and setting it to be able to write with no success.
Any help?
I am rooted with magisk working just fine.
thanks!
Click to expand...
Click to collapse
As I've seen, Some apps don't work well with other SU except for SuperSU. Get rooted using superSU, everything should work just fine. You can always Uninstall and go back to magisk once you're done.
mhrajib said:
As I've seen, Some apps don't work well with other SU except for SuperSU. Get rooted using superSU, everything should work just fine. You can always Uninstall and go back to magisk once you're done.
Click to expand...
Click to collapse
But should I delete magisk, unroot and root again with super su?
Or is it as simple as installing supersu or something?
groggycl said:
But should I delete magisk, unroot and root again with super su?
Or is it as simple as installing supersu or something?
Click to expand...
Click to collapse
It's better to follow the procedure you mentioned Uninstall magisk, install supersu then install magisk again... But only flashing superSU zip will also work I guess. You can give it a try. I've done it once I guess
mhrajib said:
It's better to follow the procedure you mentioned Uninstall magisk, install supersu then install magisk again... But only flashing superSU zip will also work I guess. You can give it a try. I've done it once I guess
Click to expand...
Click to collapse
I managed to install supersu but anyways wasn't able to get the /system partition writable. Used many guides and even apps that should do it with superuser permissions and nothing. Just cant.
Any help?
groggycl said:
I managed to install supersu but anyways wasn't able to get the /system partition writable. Used many guides and even apps that should do it with superuser permissions and nothing. Just cant.
Any help?
Click to expand...
Click to collapse
What kind of error do you get?? Can you do other operations through link2sd??
mhrajib said:
What kind of error do you get?? Can you do other operations through link2sd??
Click to expand...
Click to collapse
the error is the following..
mount: '/dev/block/bootdevice/by-name/system'->':/system': Device or resource busy
Thats the error. Tried with titanium backup pro version and it gets stuck "PROCESING" the thing... It uninstall the app I want to move to system app, but then never finishes processing..
I also used a app called mount "/system ro/rw". I grant it superuser permissions and when I hit the "mount /system rw" a message appears that says; "Your device might not be rooted or is it not compatible!"
groggycl said:
mount: '/dev/block/bootdevice/by-name/system'->':/system': Device or resource busy
Click to expand...
Click to collapse
Do this from terminal emulator (don't use GUI apps for things like this, they hide important errors most of the time):
Code:
$ su
# lsof /system
And watch for processes that hold the mountpoint.
Code:
# kill <that process id, one by one>
if you're sure they're not doing anything important, then try:
Code:
mount -o rw,remount /system
again.
P.S.: you might need to install BusyBox, I don't know if lsof is available out of the box.
leledumbo said:
Do this from terminal emulator (don't use GUI apps for things like this, they hide important errors most of the time):
Code:
$ su
# lsof /system
And watch for processes that hold the mountpoint.
Code:
# kill <that process id, one by one>
if you're sure they're not doing anything important, then try:
Code:
mount -o rw,remount /system
again.
P.S.: you might need to install BusyBox, I don't know if lsof is available out of the box.
Click to expand...
Click to collapse
I've installed busybox and when I try lsof /system it says "toybox: Unknown command lsof", is there any solution?