So I can't write or remove anything in the root folder. I've tried various file explorers without success. I'm on the AEX 8.1 Rom with Hellsgate 2.2 kernel. What could be the issue?
Related
Hi, I'm pretty inexperienced when it comes to Acer devices, although I've successfully installed roms on my Samsung Galaxy Player. I've been reading around and everyone's saying that you have to delete or rename the recovery-from-boot.p from my Acer a500 before flashing a recovery, but it never gives me permission to write in the /system folder. I have root and I'm using ES file explorer (although i tried basically every other root explorer). I can read / write in every other folder but just not the /system folder. What can i do? Thanks~
ryukiri said:
Hi, I'm pretty inexperienced when it comes to Acer devices, although I've successfully installed roms on my Samsung Galaxy Player. I've been reading around and everyone's saying that you have to delete or rename the recovery-from-boot.p from my Acer a500 before flashing a recovery, but it never gives me permission to write in the /system folder. I have root and I'm using ES file explorer (although i tried basically every other root explorer). I can read / write in every other folder but just not the /system folder. What can i do? Thanks~
Click to expand...
Click to collapse
If you have root (which you can download a root verify app from the market), then in ES Explorer, you must set the /system to R/W.
If you can't change to R/W, then you only have half root, and need to fastboot a modified boot.img (kernel) that has the security removed. This of course depends on if you have the v8 bootloader installed.
Basically, to get the full luxury of everything, you need to have the V8 unlocked bootloader, install CWM, Without booting to the OS, boot into recovery and install one of the custom roms. Some of them are stock with the bloat removed (also the recovery.p and install.recovery.sh removed).
Check the sticky threads and you'll find several methods for doing this. But remember, get and write down your UID number before installing anything.
MD
Moscow Desire said:
If you have root (which you can download a root verify app from the market), then in ES Explorer, you must set the /system to R/W.
If you can't change to R/W, then you only have half root, and need to fastboot a modified boot.img (kernel) that has the security removed. This of course depends on if you have the v8 bootloader installed.
Basically, to get the full luxury of everything, you need to have the V8 unlocked bootloader, install CWM, Without booting to the OS, boot into recovery and install one of the custom roms. Some of them are stock with the bloat removed (also the recovery.p and install.recovery.sh removed).
Check the sticky threads and you'll find several methods for doing this. But remember, get and write down your UID number before installing anything.
MD
Click to expand...
Click to collapse
In order to get full root, is it okay if i re-root the device again? I can't seem to install the v8 bootloader to work..
I'm on stock rooted MDL and I can't seem to put my filesystem into read/write. I have tried ES explorer, Solid explorer, and even tried the remount rw command in Terminal Emulator. No joy.
Anyone come across this our have an idea? Haven't tried adb copy yet.
Sent from my SPH-L720 using xda app-developers app
I am also having a similar problem, I just rooted my S4(SPH-L720) running 4.3 MK2(Stock Recovery and ROM) with CF-Auto-Root and when i try to use "SystemApp Remover" it shows system as not mounted. If I use Root File Manager I can change it to R/W and do whatever. But other then that I can not get /system mounted with R/W.
BlackoutX90 said:
I am also having a similar problem, I just rooted my S4(SPH-L720) running 4.3 MK2(Stock Recovery and ROM) with CF-Auto-Root and when i try to use "SystemApp Remover" it shows system as not mounted. If I use Root File Manager I can change it to R/W and do whatever. But other then that I can not get /system mounted with R/W.
Click to expand...
Click to collapse
Meh, I couldn't figure it out and never found anything on it. Ended up flashing (Odin) a rooted Stock ROM (4.3 MK2) with philz recovery.
I wanted to keep my phone as close to stock as possible and just have root but inevitably I always go to a custom ROM. So my middle ground was the rooted stock ROM and I've had no issues so far.
So Hello everyone, i got interesting problem...
I bricked my phone
Phone: SM-9005
OS: Android 4.4.2
Firmware: N9005XXUGNG1
Recovery: TWRP 3.0 installed.
Root software installed which may be interesting "Xposed Additions, Lucky Patcher, SuperSu, Greenify"
Step by step.
// maybe helpful - cache / dalvik cache wiped and after reboot i started playing stuff
I used Root Browser (com.jrummy.root.browserfree) to copy 2 directories from my /downloads to /system.
There were /lib & /bin which contained unique libs and one executable so this would not affect system if everything went ok, but i didn't
After i started coping, root explorer asked me that "File already exist, overwrite or make a copy"? i pressed overwrite, in same second all apps in android started to generate "unexpected error", i tried to reboot and got boot into recovery
after i watched /system i found that what i tried to copy actually copied not to /system/lib & /system/app but to /system/system/lib & /system/system/app.
So i think there was some folder or file called system in /system directory which was overwritten. Or any kind of problem with dir / file permissions.
Any ideas of how to fix this / what was in /system/system / where to get bootlog to find after what "kernel panic" takes place or any other help?
Thanks.
// maybe somebody with same model version, same os version can upload zip file of own /system folder without /apps, /priv-apps and build.prop so i can compare whats lost compared to my data?
Fixed myself, root browser set wrong permissions to /system while was coping files... set back to 755 and it works
Hey people!
I just got a nexus 7 2012 and i am wanting to mount it in my car. So i wanted to do a few things before that.
I updated to official 5.1.1 via OTA. Everything is STOCK
First step was rooting which SEEMED to work (DID it via WUGS). It installed SU and busybox. Next step was to create my own bootanimation
This is where the issues have started. I can not change permissions or move any files to the system directory even with W/R option turned on
I can delete the files but can not copy files to the directories. I can no change permissions in ANY directory.
I have tried in root explorer mounting r/w ES file explorer R/W ... i tried to install a new busy box and it installs then immediately says "you installed but it seems there is an older version on the system" i can not uninstall busybox. I tried mounting in terminal and it says all partitions are EXT 4. I have tried rerooting. Root check says everything is fine. SU seems to be working fine (it elevates permissions for all the root apps).
But for the life of me it will not copy anything into / or /system. :crying:
Should i just forget it and install another rom, WIPE everything and start again? If ROM which one is the best at the moment (nexus 2012)
After 2-3 hours of messing about... I just TWRP and flashed a different SU and it starting working.
I'm running stock Moto G4 plus firmware (Android 7.0, Nougat) on my XT1644 with TWRP 3.1.1-0 recovery, ElementalX 1.04 kernel and root with SuperSU 2.82. I'm not sure how relevant the android version is because I've noticed the same thing on every build of stock android version with root that I've tried so far.
When I go into the TWRP directory within android using a file explorer (I've tried Root Browser File Manager, ES File Explorer, Root Explorer), I can never see any of the contents of the TWRP folder. I can get into the TWRP folder, but it is just empty. The only way I can get access to the contents of the TWRP folder is to mount the phone's drive in TWRP. Also, when an OTA update downloads, I go to the cache folder in root to look for it but it is not there. I'm guessing it's the same issue that's preventing me from seeing the OTA file. However, I can't access the root directory through TWRP's mounting so I cannot grab the OTA file at all.
Is this the intended behaviour? I can see the contents of these folders on my Nexus 5. Is there any way to change/fix this?