Database Info

Root Explorer ICS issue...

No matter what I do, whether it's the 1 click odin or the cwm backup that is rooted/deodexed, root explorer will not allow my /system/ to be r/w.
I have wiped and rebooted and formatted and reflashed a dozen times now, and every time I boot up and get root going, root explorer will flip to r/w for ONE operation. after the first operation it will no longer work, and if i try to toggle the r/w switch it won't move from r/o. Sometimes I don't even get one opeartion, it just doesn't work.
I have superuser installed, i tried checking for updates, i tried fixing permissions, i tried clearing cache. I dont get it!
SOmeone help?

Did you try another rom?
I have Sensation XE with ICS and Sense4 and Root Explorer is working good here.
Flash another Rom and see if it works.
Sent from my Sensation XE powered by InsertCoin Sense 4 with Tapatalk 2

Sirgatory said:
No matter what I do, whether it's the 1 click odin or the cwm backup that is rooted/deodexed, root explorer will not allow my /system/ to be r/w.
I have wiped and rebooted and formatted and reflashed a dozen times now, and every time I boot up and get root going, root explorer will flip to r/w for ONE operation. after the first operation it will no longer work, and if i try to toggle the r/w switch it won't move from r/o. Sometimes I don't even get one opeartion, it just doesn't work.
I have superuser installed, i tried checking for updates, i tried fixing permissions, i tried clearing cache. I dont get it!
SOmeone help?
Click to expand...
Click to collapse
It might be related to this... Read posts 5+
http://forum.xda-developers.com/showthread.php?t=1568382

oops hit thanks by mistake, freebie for you.
This happened to me a lot with the deodexed version and happens every now and then with the rogers cwm file. most times a reboot helps but don't know whats causing it.

No problems with mounting R/W with stock leaked ICS here via Root Explorer.
I just deleted a bunch of .apk's w/out problem.

Yeah, I'm having similar issues. Clockworkmod won't fix permissions either.

Frogacuda said:
Yeah, I'm having similar issues. Clockworkmod won't fix permissions either.
Click to expand...
Click to collapse
For me, ROM Manager won't fix permissions. But CWM does.
Someone else said if you install busybox from Market, that will fix it so ROM Manager will fix permissions also.
edit: confirmed, installing busybox allowed ROM Manager to fix permissions for me.
And it's doing a lot more than the CWM fix permissions did!

I had to reflash su zip from sd card again to get rom manager to fix permissions.
Sent from my SAMSUNG-SGH-I727 using xda premium

CZ Eddie said:
For me, ROM Manager won't fix permissions. But CWM does.
Someone else said if you install busybox from Market, that will fix it so ROM Manager will fix permissions also.
Click to expand...
Click to collapse
Can confirm that this worked for me.. used the app called Busybox (not Busybox Installer) and ROM Manager was able to run through and complete fixing permissions.
-EDIT-
Seems to be kinda hit and miss.. was able to get ROM Manager to fix permissions on mhx's CWR backup by using the Busybox app. Just tried it on tpmullen's ROM and it would hang, so I used the app to reinstall Busybox again and it still hangs.

Go to to romracers kernel thread and try flashing his ics kernel. (Unsecured)
EDIT:
This did not work for me I can freeze apps but not delete.

Why can't I edit build.prop or push to /system/app?

Odd.
In the original firmware I was able to edit build.prop to change my dpi to 120 but now I cannot. It won't save any changes. Also, I tried pasting an .apk into my /system/app folder and it blocked me. Then I tried pushing it with adb and it gave me a read-only error.
I know I am rooted - can run Titanium Backup, etc.
Anyone have any idea?

mitchellvii said:
Odd.
In the original firmware I was able to edit build.prop to change my dpi to 120 but now I cannot. It won't save any changes. Also, I tried pasting an .apk into my /system/app folder and it blocked me. Then I tried pushing it with adb and it gave me a read-only error.
I know I am rooted - can run Titanium Backup, etc.
Anyone have any idea?
Click to expand...
Click to collapse
Did you try another root explorer?
Root explorer can be finicky.
Also try clearing it out of super su and and reallowing it. Or wipe app data.
But from my experience with root explorer, I have always hated it!! Try File Manager HD, It is great and has root explorer and system mountable all the time

BeerChameleon said:
Did you try another root explorer?
Root explorer can be finicky.
Also try clearing it out of super su and and reallowing it. Or wipe app data.
But from my experience with root explorer, I have always hated it!! Try File Manager HD, It is great and has root explorer and system mountable all the time
Click to expand...
Click to collapse
Downloaded File Manager HD. Tried replacing the Snotes.apk. No dice. All attempts do do anything with that .apk fail. Seems pretty well locked down.
Same thing with build.prop. No changes will save.

mitchellvii said:
Downloaded File Manager HD. Tried replacing the Snotes.apk. No dice. All attempts do do anything with that .apk fail. Seems pretty well locked down.
Same thing with build.prop. No changes will save.
Click to expand...
Click to collapse
Hmm..
I will try it on my note and see if it works.
Also did u make sure it was called the right name and have the right permissions?
I will let you know tomorrow or maybe tonight if it works

Yep. I've done all this many times before. They have Snotes locked down tight.
Sent from my GT-N8013 using Tapatalk 2

mitchellvii said:
Yep. I've done all this many times before. They have Snotes locked down tight.
Sent from my GT-N8013 using Tapatalk 2
Click to expand...
Click to collapse
You don't have proper root. Reroot and try again. Works like a charm! See below.
Sent from my GT-N8013 using XDA Premium HD app

Huh that seems odd as everything that requires root to work seems to work just fine. Oh well will give it a shot.
Curious as to which method you used to achieve root?
Sent from my GT-N8013 using Tapatalk 2

did you make sure to mount the system folder as r/w? i've never memorized the command since i just use root explorer.

madsquabbles said:
did you make sure to mount the system folder as r/w? i've never memorized the command since i just use root explorer.
Click to expand...
Click to collapse
Yes I did everything correctly. Just not working. That's OK.
Sent from my GT-N8013 using Tapatalk 2

mitchellvii said:
Huh that seems odd as everything that requires root to work seems to work just fine. Oh well will give it a shot.
Curious as to which method you used to achieve root?
Sent from my GT-N8013 using Tapatalk 2
Click to expand...
Click to collapse
Custom Recovery, root.zip, TriangleAway. Although root access is being granted, there may be an issue with permissions on "/system". Tried fixing permissions yet?
Sent from my GT-I9300 using XDA Premium HD app

Mister_Mxyzptlk said:
Custom Recovery, root.zip, TriangleAway. Although root access is being granted, there may be an issue with permissions on "/system". Tried fixing permissions yet?
Sent from my GT-I9300 using XDA Premium HD app
Click to expand...
Click to collapse
No haven't done that. Will run a permissions fix.

mitchellvii said:
No haven't done that. Will run a permissions fix.
Click to expand...
Click to collapse
I was wondering if you have resolved this issue because im having the same problem now. Do you recall doing anything that may have caused this issue? Everything for me started going heywire once i installed init.d support just a second ago. I Can r/w and r/o in certain parts of the system but i cant paste anything anywhere. I also noticed increase cpu load afterwards. Might i add this is the second time i have had these issues after installing init.d support script. The way i solved this the first time was i had to odin stock firmware and this solved everything. Id like to refrain from doing this again though because ill loose all my stuffs and have to set everything up again.
Sent from my GT-N8013 using Tapatalk 2

How did you achieve root? In other threads, problems with write access to /system are reported when a rooted firmware was flashed. Only the method with CWM (install CWM, flash SuperSU) did work.

akxak said:
How did you achieve root? In other threads, problems with write access to /system are reported when a rooted firmware was flashed. Only the method with CWM (install CWM, flash SuperSU) did work.
Click to expand...
Click to collapse
Oh the first time i rooted with the CWM method. But the second time, i did odin a rooted firmware Now that i think about it, the first time i was able to write to /system but now i can't after a rooted firmware flash. So the init.d script wasnt the problem. I just made an assumption because before, i havent touched anything in /system but when i installed init.d script it was actally the first time i tried to edit /system after the rooted firmware. So yes looks like im going to have to odin a stock non-rooted firmware. Thanks man! Makes alot of since now.
edit: couldn't i just try the cwm method and see it it overwrites, cause the only UEALGB firmware i can find is prerooted. I don't want to switch to UEALH2.
Sent from my GT-N8013 using Tapatalk 2

mitchellvii said:
Odd.
In the original firmware I was able to edit build.prop to change my dpi to 120 but now I cannot. It won't save any changes. Also, I tried pasting an .apk into my /system/app folder and it blocked me. Then I tried pushing it with adb and it gave me a read-only error.
I know I am rooted - can run Titanium Backup, etc.
Anyone have any idea?
Click to expand...
Click to collapse
me to same error

Try Root Explorer(or ES File Explorer) & enable R/W for system files
Check your SuperSU/Superuser app.
See if your access is granted & not denied.
If SuperSU/Superuser asking for update, update it (usually binary update)
If your SuperSU/Superuser is gone, re-install it from Play Store & run it for the first time to update binary.
Retry modifying your system file(s)

Bro I cannot change build.prop product model....
I tried root explorer and es explorer
From yuphoria

Is that cannot or don't know how.
One is no root two is edit.
Sent from my SM-N930F using XDA-Developers mobile app
---------- Post added at 02:13 PM ---------- Previous post was at 01:20 PM ----------
JJEgan said:
Is that cannot or don't know how.
One is no root two is edit.
Sent from my SM-N930F using XDA-Developers mobile app
Click to expand...
Click to collapse
Edit is at the top of the RH side.
Sent from my SM-N930F using XDA-Developers mobile app

I have the same problem...
I can change my build.prop but after a reboot all the changes are gone.
I have rerooted it 2-3 times already. I can just change it sucessfully at the beginning but after some time it doesn't work anymore.
I have a samsung galaxy a3 2017.

Try forum for your phone .
Post lacks any information to help.
Suggest FX Explorer.

Trying to set write permissions on /system ends in bootloop

hi,
i did a big mistake. I wanted to install some vpn apps, which requires write permission on /system. I downloaded root explorer und tried to set all permissions for the system folder. But the app stills lacks the wanted permissions, so i started root explorer again and additionally checked the checkboxes under "special permissions". After doing that android crashed, the "systemui" process crashed and restarted and crashed ...
I rebootet the device, but i only see "google" and then comes a reboot and the device boots into recovery (TWRP 2.6.3.4). I already tried the "fix permissions" under advanced, but it didn't helped.
Is there any way to fix whatever i did wrong and not lose any data?
Any help would be greatly appreciated
Greetings k1x1987

Reflash rom without wiping.
Sent from my Nexus 5 using Tapatalk

d
jyuuken said:
Reflash rom without wiping.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for your help. I don't want to miss something this time and complety brick my device. Could you/anybody tell me exactly what and how do flash to recover my device?
I did all the rooting stuff with the "Nexus Root Toolkit" program and followed strictly guides, except this time
Do i have to flash the rom with ADB? which file(s) should i flash system.img only? Or i have to flash more files?
A short noob guide would be really appreciated :good:
Greetings k1x1987

So you are just rooted on the stock setup? Then you should be able to flash a stock odexed rom that matches your current set up (4.4.1 or 4.4.2) and you should wipe, but just the caches. You'll likely need to adb push rom.zip /sdcard when in recovery. You probably could adb sideload as well, but not sure if that wipes anything else. Never had to mess with sideloading.
For future reference, once you are up and running, I think what you would need to change is the SELinux permissive state. There's an app do that. Then the most you would need is to hit the R/W button when you're in /system with Root Explorer. Or with the newer Root Explorer versions, once you try and make a change that needs R/W permissions, it'll stop and ask you if you want RE to switch it for you to complete the task.

es0tericcha0s said:
So you are just rooted on the stock setup? Then you should be able to flash a stock odexed rom that matches your current set up (4.4.1 or 4.4.2) and you should wipe, but just the caches. You'll likely need to adb push rom.zip /sdcard when in recovery. You probably could adb sideload as well, but not sure if that wipes anything else. Never had to mess with sideloading.
For future reference, once you are up and running, I think what you would need to change is the SELinux permissive state. There's an app do that. Then the most you would need is to hit the R/W button when you're in /system with Root Explorer. Or with the newer Root Explorer versions, once you try and make a change that needs R/W permissions, it'll stop and ask you if you want RE to switch it for you to complete the task.
Click to expand...
Click to collapse
Thanks for your help. Yes, i am complety stock besides root and franco kernel. I already downloaded factory image (4.4.2). Should i flash the zip, which contains all the system.img, userdata.img etc. (i think it was 5 files) or just specific ones? It would be n1 if my data dont get lost.
Thanks in advance.
k1x1987

k1x1987 said:
Thanks for your help. Yes, i am complety stock besides root and franco kernel. I already downloaded factory image (4.4.2). Should i flash the zip, which contains all the system.img, userdata.img etc. (i think it was 5 files) or just specific ones? It would be n1 if my data dont get lost.
Thanks in advance.
k1x1987
Click to expand...
Click to collapse
Just flash the system.img in fastboot.

Most devs recommend wiping /system first.
fastboot erase system
fastboot flash system system.img
I would also erase cache too.
fastboot erase cache
That will clear the cache, not the dalvik, but think that should be enough to get going.

...and once it is fixed, never change system permissions again.... Same a Linux, never change permissions at /root

.. phone works again
thanks at all for the help. But now i cant get any cell service. I looked under settings/about the phone/status and saw that my "IMEI" is "unkown". Could this be the problem? I read about restoring imei, should i try this and it this the cause for me not getting any service?
Thanks

k1x1987 said:
.. phone works again
thanks at all for the help. But now i cant get any cell service. I looked under settings/about the phone/status and saw that my "IMEI" is "unkown". Could this be the problem? I read about restoring imei, should i try this and it this the cause for me not getting any service?
Thanks
Click to expand...
Click to collapse
Using fastboot, flash the cache image from the factory image, fastboot flash cache cache.img

^ That should do the trick. If not, well, let's not go there yet. The cache should fix it. If that does, do yourself a favor and back up your EFS folder and save it somewhere safe. Either use TWRP or flash the EFS backup tool from here: http://forum.xda-developers.com/showthread.php?t=2514095

[Q] Xperia M2 rooted but cant acess system r/w premissions?

Hi,
I have unlocked the bootloader using Sony's method, then rooted by downgrading to 4.3, flashing the recovery, flashing SU then upgrading back to 4.4. Root works fine (Apps like Titanium Backup work normally), but I can't use apps like AdFree or Xposed because I don't have read/write premissions for the /system partition. I found a fix, but that fix requires BusyBox and I can't install that, again, because I can't write to the /system partition.
Can anyone help me, please?

^^Robi said:
Hi,
I have unlocked the bootloader using Sony's method, then rooted by downgrading to 4.3, flashing the recovery, flashing SU then upgrading back to 4.4. Root works fine (Apps like Titanium Backup work normally), but I can't use apps like AdFree or Xposed because I don't have read/write premissions for the /system partition. I found a fix, but that fix requires BusyBox and I can't install that, again, because I can't write to the /system partition.
Can anyone help me, please?
Click to expand...
Click to collapse
Do you know that there is a search engine in this forum ?
http://forum.xda-developers.com/xperia-m2/development/tut-fix-mount-kitkat-root-t2861661

Huh
Oops i didnt saw that one hehe thanks am trying it now

^^Robi said:
Oops i didnt saw that one hehe thanks am trying it now
Click to expand...
Click to collapse
/edit
It worked! Thanks

No problem .

Kzeran said:
Do you know that there is a search engine in this forum ?
http://forum.xda-developers.com/xperia-m2/development/tut-fix-mount-kitkat-root-t2861661
Click to expand...
Click to collapse
Not working for me. In my case sys/kernel/security/sony_ric is empty, no "enable" file exists so what is the solution in this case? why this file does not exist?
Thanks!

need help - how to copy TWRP nandroid backup to device?

how to copy TWRP nandroid backup to device?
I need to restore and I don't know how to copy from my hdd to the phone.
The phone is not booting but I can get to twrp recovery.

Latest TWRP has MTP mode.

but it doesn't allow me to copy one of the backup files which is: data.ext4.win000 and it's 1.5GB

You'll need to give us more information.
Why did it fail? Why did your phone stop booting?

1. flashed bigxie_hammerhead_LRX21O-signed.zip
2. flashed CF-Auto-Root-hammerhead-hammerhead-nexus5
3. booted fine but still had apps like Ti backup & TWRP not working due to root permissions
4. Went to recovery and performed Fix permission.
5. stuck in boot loop

gil80 said:
but it doesn't allow me to copy one of the backup files which is: data.ext4.win000 and it's 1.5GB
Click to expand...
Click to collapse
I have had the same problem with my motox 14 the way I found around it was to copy the file to a different fold and use twrp file explore to move it to the back up folder. That has worked for me and a few others try it out it will work.

how can you copy using twrp while in recovery? are you able to access your PC from recovery?

gil80 said:
1. flashed bigxie_hammerhead_LRX21O-signed.zip
2. flashed CF-Auto-Root-hammerhead-hammerhead-nexus5
3. booted fine but still had apps like Ti backup & TWRP not working due to root permissions
4. Went to recovery and performed Fix permission.
5. stuck in boot loop
Click to expand...
Click to collapse
You'll need to factory reset then reflash the ROM
Fix permissions was not required here. You need titanium beta from his twitter feed.

ok i got the phone working and lost my data but I have it backed on PC.
I just see that 10GB is used but when I browse the phone using file explorer, the device is empty.... what??

Is it a known issue?
when the phone is connected to PC I see that 10GB is used but when I i browse the device it shows as empty

No. Do a full flash of userdata.img

Please explain
What would I achieve by flashing it?

gil80 said:
Please explain
What would I achieve by flashing it?
Click to expand...
Click to collapse
A fix for your problem. I shouldn't really need to explain that.

Thanks!
I got it working now. Only need to figure out why it shows 16GB instead of 32 and why root permissions are not working

gil80 said:
Thanks!
I got it working now. Only need to figure out why it shows 16GB instead of 32 and why root permissions are not working
Click to expand...
Click to collapse
Well the answer in the 100 other threads about space say that you must wipe data and cache.
Root should be fine, but as already mentioned, not with official titanium release.

I already did a wipe data and cache. So I don't understand why I still get this but I'll try again.
The Ti Backup link in the twitter feed is no longer valid, but for example, ES file explorer and clean master and also TWRP app are not performing as if they are rooted.
I'll try to re-install CF-Auto-Root-hammerhead-hammerhead-nexus5

gil80 said:
I already did a wipe data and cache. So I don't understand why I still get this but I'll try again.
The Ti Backup link in the twitter feed is no longer valid, but for example, ES file explorer and clean master and also TWRP app are not performing as if they are rooted.
I'll try to re-install CF-Auto-Root-hammerhead-hammerhead-nexus5
Click to expand...
Click to collapse
ES doesn't work properly, correct. Not all apps have been updated to work with L yet either.
L is much more secure than KK. There are ways to root.
1) chain fire - makes small change in RAMdisk that allows sudaemon to work at boot
2)flash a permissive kernel - this lowers protection within selinux.
More apps work with the 2nd method, but still not all.
New titanium coming to play soon.
https://twitter.com/titaniumbackup