Related
I need to uninstall swype and reinstall it. Ive tried over writing it with the default apk but its not removing a theme I installed with metamorph. If I can uninstall it, a fresh install should fix it.
I just dont know how to remove it
I don't know if you want to go to this extreme, but I did. I fudged up the phone real good by removing and installing stuff. I finally got fed up and flashed it back to stock and applied root again. This time I'll keep my fingers out of it. I hated touchwiz in the beginning, but now it's kinda growing on me. I've never had an iphone but the home and drawer remind me of iphone wannabe. It's okay for now.
Sent from my SPH-D700 using XDA App
There a tool over at sdx-developers that can remove that when root explorer can't. I forget the name of it. There's also a pay app in the market that I think is called root manager that can successfully remove crap too. I didn't have much luck putting the general swype 1.61 in. It refused to install. That's when I think I just flashed it back to factory image. A full reset/wipe wouldn't fix it either.
Sent from my SPH-D700 using XDA App
I had to do this a few days ago for similar reasons. This is what I did:
First, you have to open your browser or other app with a text field. Select the text field then long press the text field again and switch the input method to the stock android kb.
Next, you have to make sure /system is mounted as r/w. The early versions of the the rooting scripts did not remount correctly but the newer ones supposedly fix it. I just looked in the initial rooting .bat file (on the PC) for the remount command and used adb to remount /system.
You can test if it's remounted correctly by renaming Swype.apk to Swype.bak with Root Explorer then going up a level and back to /system/app. If it's not mounted correctly it will show as Swype.apk again. If it shows as Swype.bak still, then you just have to copy the original Swype.apk to /system/app and then switch input method back to Swype!
Sent from my Epic 4G using XDA App
yea its mounting in r-r, thats def my problem, cant change swype.apk with root explorer
so i need to re-root?
I don't know what's causing it but root explorer doesn't seem to work properly on the phone (not sdcard) filesystem in the system app folder. It's stuck in rw mode. People have said different things why but I forgot. I did noobnl's latest flash and it's still not working right. His script is removing the old root and my phone doesn't have that on there. I don't know what to tell ya. Maybe I should look for another root file manager.
kennethlongshaw said:
yea its mounting in r-r, thats def my problem, cant change swype.apk with root explorer
so i need to re-root?
Click to expand...
Click to collapse
I don't know if re-rooting will fix it or not. You could try. Here's the exact steps I took using adb from the PC:
Code:
adb shell
su
ls /system/app/S* (just shows Swype.apk is in fact in /system/app)
mount -t rfs -o remount,rw /dev/block/stl9 /system
mv /system/app/Swype.apk /system/app/Swype.bak
ls /system/app/S* (just to confirm Swype.apk is now Swype.bak)
cp /sdcard/download/Swype.apk /system/app/Swype.apk (or replace first argument with path of the good Swype.apk on your phone)
ls /system/app/S* (just to confirm Swype.apk and Swype.bak are both there)
reboot (reboots the phone, dunno if its really necessary)
dwyw42 said:
I don't know if re-rooting will fix it or not. You could try. Here's the exact steps I took using adb from the PC:
Code:
adb shell
su
ls /system/app/S* (just shows Swype.apk is in fact in /system/app)
mount -t rfs -o remount,rw /dev/block/stl9 /system
mv /system/app/Swype.apk /system/app/Swype.bak
ls /system/app/S* (just to confirm Swype.apk is now Swype.bak)
cp /sdcard/download/Swype.apk /system/app/Swype.apk (or replace first argument with path of the good Swype.apk on your phone)
ls /system/app/S* (just to confirm Swype.apk and Swype.bak are both there)
reboot (reboots the phone, dunno if its really necessary)
Click to expand...
Click to collapse
mmmm. That fixed. it. I owe you a beer
kennethlongshaw said:
mmmm. That fixed. it. I owe you a beer
Click to expand...
Click to collapse
Hi guyz.
I cant delete swype.apt file from /system/app/*
i am using SUFBS program (reed/write option enabled)
i tried use command in terminal:
Code:
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
but i get only;
Code:
permission denied
z4root show info that my phone is rooted
PDA i5800XXJI2
any ideas how to del that file? :]
OK... so I am trying to get the Internet up and running for this Samsung Epic. I almost have it down, but there is something that I know is wrong from the other Android phones that I have flashed before.
For Metropcs internet to work we have to install a script: u2nl and autostart file.
Here is my problem: I can put the autostart file into the data/opt folder, but when I try and paste the u2nls file into /system/bin it tells me that it is only a read only....
Now when I try in commond prompt and I try and do adb remount it now tells me No such file or directory or remount failed.
If I can get that u2nl file to stick in there I know I will be good to go.
I dont know much about adb commands, so here is what I did:
I plugged phone in on charge only mode. USB debug is checked.
cd c:\android\tools
adb remount **wont work either...it will fail, which probably why I cant write into the system/bin file.
adb push c:\autostart.sh /data/opt/autostart.sh
adb push c:\android\tools\u2nl /system/bin/u2nl **wont work
Adb shell
su
chmod 0755 /system/bin/u2nl **gives me an error
chmod 0755 /data/opt/autostart.sh
Please help!!!!!
Thanks.
I have one bad and one good news for you
First the good one...
Reboot into clockwork recovery and mount /system...retry
Bad news...
That method or the anycut method does not work...I already spent 2 days trying so many settings and it just doesn't work.
Do u have mms working?
Sent from my SPH-D700 using XDA App
My MMS does not work since my Internet does not work.
There are people that have gotten this to work on Metro already with everything at my local metro shop in CA.
I am pretty sure once I get this u2nl file to stick, it will work. The 3G arrows starts up and then it seems like it will start to run the autostart script and then errors out.
Let me try what you said and I am also going to try another rom.
under clockwork recovery which mount do I do? mount /sd-ext
What is suppose to be mounted and unmounted?
it says: unmount /system **meaning its already mounted right?
if its says unmount /system..its already mounted
just go to cmd and
adb remount
adb push c:\android\tools\u2nl /system/bin/u2nl
ect..ect..
if the remount doesnt work..download busybox installer and update busybox to the latest version and retry
autostart\u2nl its not required to be able download\send mms..you need to have the right apn settings and the 3g arrows dancing lol,,
ok so when I hit adb remount it says "remount failed: No such file or directory
I downloaded the busybox, when I open it it says:
Busybox 1.17.1 is what I have in phone
Busybox 1.18.0 git (unofficial) I can download
Below that it says where do I want to install busybox:
/system/xbin/ or /sbin/
Where do I install and should I install that unofficial version?
tosh1 said:
ok so when I hit adb remount it says "remount failed: No such file or directory
I downloaded the busybox, when I open it it says:
Busybox 1.17.1 is what I have in phone
Busybox 1.18.0 git (unofficial) I can download
Below that it says where do I want to install busybox:
/system/xbin/ or /sbin/
Where do I install and should I install that unofficial version?
Click to expand...
Click to collapse
should be /system/bin (no x or s before bin)
1.17.1 is fine
try again if that doesnt work..in clockwork recovery try this
adb shell
su
remount rw
exit
exit
and try again..im running out of options here..lol
hey did it work? how is it going with full flash?
also make sure you root with the new zip version..some previous versions dont have the remount scripts
adb commands
u2nl does not need to be run in /system/bin. just edit the autostart.sh to reflect your location change. if u insist on running from /system/bin, then do this
adb shell
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
exit
exit
then push u2nl to /system/bin
Thanks buddy it looks like it worked....
Now I have the data arrows showing but something is not kicking in yet. I think I am missing something. I changed all the right settings on Qpst have the right passwords now (msl - whiterabbit.org) all files in the right place.
I have done this on Eris full flash, evo full flash, incredible full flash, but this Epic is driving me nuts...
kinda stuck right now.
Lol and now we are 2 stuck in the same place. I had flash tons of droids, evos, but this epic is making me going nuts..I don't know what's going on either..I had seen epics on cricket full flashed with no problem..but seems samsungs don't like metropcs' proxy
Sent from my SPH-D700 using XDA App
What rom r u using bro? Maybe the epic rom I'm using desnt support iptables for some reason..
I'm going to try another rom tomorrow.. either way keep me updated as well.
Sent from my SPH-D700 using XDA App
stock (rooted of coutse) with the iptables file in the bin folder . that used to work in my old droid, just set the correct permissions, andromeda v1.1.x, mixupkernel DI18-voodoo, and epic experience (dont remember which version) and none worked
I have some ultrasecret info..lol..supposedly the normal autostart.sh file does not work with samsungs, there is different modified version for the moment and the fascinate but i cant find it
i cant test this anymore cus i dont have metro but thanks to chimstar in the mo-fi forum, dial ##3282# go to edit mmsc url, type your msl, and edit the mmsc server to the metropcs one
if that doesnt work, download the apn back and restore app, delete all apns and restore metropcs working, if you dont have one, edit the xlm file to match all the correct info
make sure you reboot
see if that gets your mms working..i didnt need to have the autostart method running for my droid to get mms
so im stuck and can not figure this out. for some reason the permissions for the download folders on my sd card do not have any user permissions checked. i can not download anything at all but the market is fine as it is on the internal memory i suppose. the only reason i came across the user permissions issue was because i found another post where someone had the same problem with downloading and corrected the issue by using root explorer and manually adding user permissions to any folder he used for downloading. now... here is my problem... i used root explorer and when i try to add user permissions to these folders, the settings that changed do not stick. i check mark the 3 boxes and accept the changes but if i go back into that folders specific permissions, they are unchecked once again. how can i get it to not revert back or better yet how can i just resolve the issue in whole so i dont have to keep fixing folder permissions on the sd card for app that downloads? i dont see why the sd card of all places would start having these permission issues. the guys post i came across tried to tie this issue to the fix permissions option in rom manager saying it may have caused the problem but i didnt use rom manager to fix permissions until this problem started. i was on liberty 1.5 rom then reverted back to rooted stock where i still have the problem with all downloading except the market again. any help would be greatly appreciated!
58 views and not a single response? wow.... so very shocking to see that, i bet if i had post this in the dev forum i would have gotten 15+ responses just to say that im in the wrong section then anther 30 for people to argue back and fourth on how everyone is being rude or that this is the reason devs stay in irc...
Give this a try if you have the sdk and adb set up.
from a command prompt:
1) adb devices (make sure that your phone shows up)
2) adb shell
3) su (assuming you have rooted your phone)
4) cd /mnt/sdcard/download (or whatever the folder on your sdcard for downloads is called)
5) chmod 777 /mnt/sdcard/download (or whatever your download folder is called)
this should change the permissions on your sdcard to have full permissions.
thanks for your reply! im grateful, but wouldnt that only change the permissions for the "download" folder? which is mostly only a default location for apps such as the browser?
The way sysadmin-x is suggesting makes the permissions way different than they are by default, I wouldn't recommend doing it that way.
If you want to change permissions on the entire sd card to what they are by default, try running(as root)
Code:
chown -R system:sdcard_rw /mnt/sdcard && chmod -R 075 /mnt/sdcard
Edit: that code messes up the permissions on one folder, after running that you should also run
Code:
chown -R root:root /mnt/sdcard/.android_secure && chmod -R 000 /mnt/sdcard/.android_secure
Just do this: download a terminal emulator from the market. Open the app. Type su and press enter. Give it root access. Type chmod 777 /sdcard and press enter.
Please note you need root to do this
For those having problems with bluetooth not working on the new 4.2 OTA from Asus....they screwed up permissions on /system/vendor/lib/libbt-vendor.so. It's permissions are wrong and need to be changed to rw-r-r. This can only be done on rooted tablets....locked or unlocked:
Open a terminal
su to root
Make /system rw with: mount -o rw,remount /system
chmod 644 /system/vendor/lib/libbt-vendor.so
reboot
Now if only I can get my root issue fixed.
Sent from my PG86100 using xda app-developers app
Actually you can wait till ASUS releases the whole firmware file on their webpage. Then you should be able to reflash your firmware without wiping data using that image by moving the image on the SD card. So there is no need for root.
bluetooth fix
bads3ctor said:
For those having problems with bluetooth not working on the new 4.2 OTA from Asus....they screwed up permissions on /system/vendor/lib/libbt-vendor.so. It's permissions are wrong and need to be changed to rw-r-r. This can only be done on rooted tablets....locked or unlocked:
Open a terminal
su to root
Make /system rw with: mount -o rw,remount /system
chmod 644 /system/vendor/lib/libbt-vendor.so
reboot
Click to expand...
Click to collapse
That did it for me and saved me a trip to the Asus repair shop. Thank you.
I just did it using RootExpoler. system/vendor/lib/ longpress libbt-vendor.so and select permissions, Owner should be RW, Group tick Read, Others tick Read. hit Ok and reboot tablet. Done
Thank you. Bluetooth is back again
tbdawg said:
Now if only I can get my root issue fixed.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Hi,
I had to factory reset my device (4.1) before updating to 4.2, I thought I have lost root. But managed to restore root quite easily.
If you have preserved root via VooDoo OTA RootKeeper before updating to 4.2 you can give these instructions a try. They work if su-backup copy is not disturbed by OTA, which is mostly the case (like yours).
bads3ctor said:
For those having problems with bluetooth not working on the new 4.2 OTA from Asus....they screwed up permissions on /system/vendor/lib/libbt-vendor.so. It's permissions are wrong and need to be changed to rw-r-r. This can only be done on rooted tablets....locked or unlocked:
Open a terminal
su to root
Make /system rw with: mount -o rw,remount /system
chmod 644 /system/vendor/lib/libbt-vendor.so
reboot
Click to expand...
Click to collapse
i tryed, but with me not work..
I did the following:
open the terminal
write /system rw with: mount -o rw,remount /system ==> start
write chmod 644 /system/vendor/lib/libbt-vendor.so ==> start
Write reboot ==> start
at reboot, bluetooth whe i actived, the tablet stuck for few second ( 30sec/1min) and continue to not work...
PLease help me...
Thank's
Try this
stevtec86 said:
i tryed, but with me not work..
I did the following:
open the terminal
write /system rw with: mount -o rw,remount /system ==> start
write chmod 644 /system/vendor/lib/libbt-vendor.so ==> start
Write reboot ==> start
at reboot, bluetooth whe i actived, the tablet stuck for few second ( 30sec/1min) and continue to not work...
PLease help me...
Thank's
Click to expand...
Click to collapse
Install: https://play.google.com/store/apps/details?id=com.estrongs.android.pop&feature=related_apps
Make sure ES File Explorer has root permissions. In settings->root settings, check Root Explorer, Up to Root, and Mount File System. Change directories to /system/vendor/lib. Long tap libbt-vendor.so and click properties. Change permissions: check read for User, Group, and Other. Check write for User. Tap OK. Reboot.
bads3ctor said:
Install: https://play.google.com/store/apps/details?id=com.estrongs.android.pop&feature=related_apps
Make sure ES File Explorer has root permissions. In settings->root settings, check Root Explorer, Up to Root, and Mount File System. Change directories to /system/vendor/lib. Long tap libbt-vendor.so and click properties. Change permissions: check read for User, Group, and Other. Check write for User. Tap OK. Reboot.
Click to expand...
Click to collapse
Done, but the permission was to rw-r-r, but bluetooth not work
stevtec86 said:
Done, but the permission was to rw-r-r, but bluetooth not work
Click to expand...
Click to collapse
The only way I know to diagnose such a problem is logcat. If you post the error, maybe someone has seen the error and can help.
bads3ctor said:
For those having problems with bluetooth not working on the new 4.2 OTA from Asus....they screwed up permissions on /system/vendor/lib/libbt-vendor.so. It's permissions are wrong and need to be changed to rw-r-r. This can only be done on rooted tablets....locked or unlocked:
Open a terminal
su to root
Make /system rw with: mount -o rw,remount /system
chmod 644 /system/vendor/lib/libbt-vendor.so
reboot
Click to expand...
Click to collapse
Hi bads3oct,
for the bluetooth problem, are you talking about bluetooth address missing in system info and it couldn't be enabled in setting(I slid the bluetooth switch from OFF to ON, but it rebounds back to OFF immediately)? my bluetooth worked fine with 4.1.1 several weeks ago and i haven't used it until yesterday. During the time, i just upgraded it to offical 4.2.1.
I've rebooted thousands times and switch the laucher from new 4.2 UI back 4.1 , all didn't help.
my tf300 is still running with locked bootloader and unrooted.
I want to know if the problem you guys are talking is same phenomenon as mine
abczhou said:
Hi bads3oct,
for the bluetooth problem, are you talking about bluetooth address missing in system info and it couldn't be enabled in setting(I slid the bluetooth switch from OFF to ON, but it rebounds back to OFF immediately)? my bluetooth worked fine with 4.1.1 several weeks ago and i haven't used it until yesterday. During the time, i just upgraded it to offical 4.2.1.
I've rebooted thousands times and switch the laucher from new 4.2 UI back 4.1 , all didn't help.
my tf300 is still running with locked bootloader and unrooted.
I want to know if the problem you guys are talking is same phenomenon as mine
Click to expand...
Click to collapse
Yes...the bluetooth toggle rebounds back to OFF immediately when the permissions are wrong after an update from 4.1.1 to 4.2.1. If you are not rooted then I think the only way to fix it is to unlock and root. Maybe you could manually reinstall the update while locked and unrooted using the Asus zip file but I don't know if this is possible.
thanks for your quick reply, Asus should notice their mistake and fix it soon.
Sent from my LG-P990 using xda app-developers app
Interesting side-note to this thread. I implemented the fix as prescribed and it worked perfectly. So much so that I am typing this reply on a generic BT Keyboard.
But before I could do this, I had to restart the tablet to re-enable bluetooth. This was after using BT all day with this keyboard. The only thing I did was connect the tablet to the charger, and after it finished charging the BT stack behaved like it did before I implemented the fix. I checked the permissions on the file, and the Owner permissions were still preserved, so I'm at a loss to explain it.
Not sure if there is something else going on here, or if it is pure coincidence. The issue was easily fixed with a restart.
Works for my TF700 - change permission by root browser
my mistake after change permision I do not make reboot and think solution is not working for me - but easy easy
after restart pad - bluetooth works again
great job, many thanks bads3ctor
Fixed my bluetooth problems on my rooted TF300TG by changing the permissions with X-Plore file explorer. Thanks
Sent from my ASUS Transformer Pad TF300TG using xda app-developers app
I don't know if this is due to the BT stack on our devices, but when you disconnect a paired BT device, some apps really hate it.
I did this while playing Pinball Arcade, and the app crashed.
There is a noticeable system pause when within an app when you turn off the paired device (my Logitech Tablet Keyboard has an Off switch, rather than a soft-off feature).
Has anyone else noticed this behavior?
There's another horrific problem with bluetooth A2DP quality. It seems to be hindered by this bug: http://code.google.com/p/android/issues/detail?id=39632
I haven't tried this yet, but if someone can replicate what was done here, it should fix this: http://forum.xda-developers.com/showthread.php?t=2184333
will I still be able to recieve OTA's if I fix the permission problem?
edit: I went ahead anyway, for reference original permissions 600
Everything was good until I started messing with the 4.4 roms. Now no matter what I do. Full Wipe, Factory Image restore, try different Roms/Kernels, etc, my MAC Address will reset after every reboot. This is an issues as I use Mac Filtering on my router. Any Ideas?
The same is happening to me and I can't find a way to fix it!
It sucks because my main connection (my University wifi) doesn't let me connect if I have a different MAC Address.
I'm using this app to change my MAC (temporarily) https://play.google.com/store/apps/details?id=com.jworksbr.macspoofer
You need root to make it works.
Anyway, I'm still trying to find a way to get my original MAC address back.
joaocadide said:
The same is happening to me and I can't find a way to fix it!
It sucks because my main connection (my University wifi) doesn't let me connect if I have a different MAC Address.
I'm using this app to change my MAC (temporarily) https://play.google.com/store/apps/details?id=com.jworksbr.macspoofer
You need root to make it works.
Anyway, I'm still trying to find a way to get my original MAC address back.
Click to expand...
Click to collapse
I ended up using http://forum.xda-developers.com/showthread.php?t=2347060
For mac address:
- In /persist directory create wifi directory. In the new directory create a file named .macaddr (don't miss the dot!)
Edit the file and put 12 random hex numbers in it (0-9, A-F), save.
- Set execute and read permissions for everybody on /persist/wifi directory and change owner of .macaddr to wifi:wifi and permission to 660 (read/write for owner and group and nothing else).
In command line:
Code:
chown root:root /persist/wifi
chmod 755 /persist/wifi
chown wifi:wifi /persist/wifi/.macaddr
chmod 660 /persist/wifi/.macaddr
- run /system/bin/conn_init program. Can be run in root explorer(choose Linux Script Handler when you open it), or in adb shell:
Code:
su
/system/bin/conn_init
Then reboot and check if the changes got applied in settings
I cant get my original one back but at least I have a static MAC.
..
chainup said:
For me it's only the last 6 numbers/letters that keep changing on reboot. For both Wifi and Bluetooth. Is it the same for you guys?
Click to expand...
Click to collapse
Yeah first are always 11:22:33
Thank you, bandit97!
It's working fine now! =D
bandit97 said:
I ended up using http://forum.xda-developers.com/showthread.php?t=2347060
For mac address:
- In /persist directory create wifi directory. In the new directory create a file named .macaddr (don't miss the dot!)
Edit the file and put 12 random hex numbers in it (0-9, A-F), save.
- Set execute and read permissions for everybody on /persist/wifi directory and change owner of .macaddr to wifi:wifi and permission to 660 (read/write for owner and group and nothing else).
In command line:
Code:
chown root:root /persist/wifi
chmod 755 /persist/wifi
chown wifi:wifi /persist/wifi/.macaddr
chmod 660 /persist/wifi/.macaddr
- run /system/bin/conn_init program. Can be run in root explorer(choose Linux Script Handler when you open it), or in adb shell:
Code:
su
/system/bin/conn_init
Then reboot and check if the changes got applied in settings
I cant get my original one back but at least I have a static MAC.
Click to expand...
Click to collapse
i came from your link too but this didn't work for me
anyone know why?
Hi. This has been driving me crazy! My Nexus 4 also gets a new Mac address on each reboot. My local WiFi hotspot thinks i am a new customer every time I visit (as it uses Mac address filtering) which is frustrating. I got onto Google about it but they said i should return the phone to the retailer (didn't get it on the Play store). I tried reverting the phone to Android 4.3, resetting etc but nothing works. I the phone was fine at first so I can only assume it is a hardware fault. Does anyone have any more incite into this or a solution?
Could someone explain how I run the commands in an adb shell? I'm familiar with adb and android toolkit etc. Many thanks! PS. I tried it using root explorer and it did not work
Sent from my Nexus 4 using xda app-developers app
Where is /persist directory?
bandit97 said:
I ended up using http://forum.xda-developers.com/showthread.php?t=2347060
For mac address:
- In /persist directory create wifi directory. In the new directory create a file named .macaddr (don't miss the dot!)
Edit the file and put 12 random hex numbers in it (0-9, A-F), save.
- Set execute and read permissions for everybody on /persist/wifi directory and change owner of .macaddr to wifi:wifi and permission to 660 (read/write for owner and group and nothing else).
In command line:
Code:
chown root:root /persist/wifi
chmod 755 /persist/wifi
chown wifi:wifi /persist/wifi/.macaddr
chmod 660 /persist/wifi/.macaddr
- run /system/bin/conn_init program. Can be run in root explorer(choose Linux Script Handler when you open it), or in adb shell:
Code:
su
/system/bin/conn_init
Then reboot and check if the changes got applied in settings
I cant get my original one back but at least I have a static MAC.
Click to expand...
Click to collapse
Where is the /persist directory found? Does this work on unrooted phones? I have the Chinese S5 phone which changed Mac address every time I reboot or turn off and on the wifi. This has me logging in to my router to add a new mac every time.
You DO need to be rooted
ayonbaxter said:
Where is the /persist directory found? Does this work on unrooted phones? I have the Chinese S5 phone which changed Mac address every time I reboot or turn off and on the wifi. This has me logging in to my router to add a new mac every time.
Click to expand...
Click to collapse
Hello, you need not only root access, but a file manager capable of mounting read-write permissions, like ES File Explorer (free on Google Play).
If you have a Terminal Emulator, this will help. If not, find one on the Play Store. My favorite is from developer Jack Palevich, found here.
Otherwise, you won't see the directory on a stock file manager, especially if you're NOT rooted. Although I am on CM 10.2, this has plagued me as well when I was running CM11.
Good luck!
furboom1240 said:
Hello, you need not only root access, but a file manager capable of mounting read-write permissions, like ES File Explorer (free on ).
If you have a Terminal Emulator, this will help. If not, find one on the Play Store. My favorite is from developer Jack Palevich, found .
Otherwise, you won't see the directory on a stock file manager, especially if you're NOT rooted. Although I am on CM 10.2, this has plagued me as well when I was running CM11.
Good luck!
Click to expand...
Click to collapse
i have the same problem, i cant find the /persist directory. i installed ES file exloprer but on / there is no /persist folder only these folders:
acct, cache, config, custom, d, data , dev, etc, mnt, proc ,protect_f,protect_s, root, sbchk, sbin, sdcard, sys,system, vendor
can i create a persist folder or do i have a bigger problem with my system?
Lack of Details
tommy0014 said:
i have the same problem, i cant find the /persist directory. i installed ES file exloprer but on / there is no /persist folder only these folders:
acct, cache, config, custom, d, data , dev, etc, mnt, proc ,protect_f,protect_s, root, sbchk, sbin, sdcard, sys,system, vendor
can i create a persist folder or do i have a bigger problem with my system?
Click to expand...
Click to collapse
First of all, do you have Superuser-managed root access? In order for me to assist, you need to answer that. The /persist directory should certainly exist, as it was so on all devices I own, rooted or not. When browsing the filesystem, please be careful what you mess with. Even with root access, you must exercise judgment in what you modify.
As always, Root Responsibly.
Stay custom, my friends...