Related
CyanogenMod's file manager seems to be stuck in safe mode, even though I have a rooted device and even have a modified kernel. I've not been able to figure out exactly what's happening. It says that only the accessible file systems are the storage volumes.
Anyone else have this problem, or does anyone know how to fix it?
RogueSly said:
CyanogenMod's file manager seems to be stuck in safe mode, even though I have a rooted device and even have a modified kernel. I've not been able to figure out exactly what's happening. It says that only the accessible file systems are the storage volumes.
Anyone else have this problem, or does anyone know how to fix it?
Click to expand...
Click to collapse
The default for the CM file manager is for root access to be turned off. With the file manager open go into settings and allow root access. Once you exit settings you'll have full access.
Nut_House said:
The default for the CM file manager is for root access to be turned off. With the file manager open go into settings and allow root access. Once you exit settings you'll have full access.
Click to expand...
Click to collapse
That's the problem. It won't allow root access, even though the phone has root access. The menu for the access mode is disabled.
RogueSly said:
That's the problem. It won't allow root access, even though the phone has root access. The menu for the access mode is disabled.
Click to expand...
Click to collapse
Have you tried clearing cache and Dalvik and fixing permissions? The other thing to try, if you haven't already, is downloading the latest nightly and performing a clean install rather than dirty flashing. Good luck.
If you accidentally refused root access the first time you have to go into the SU app and clear out the File manager permission and start over.
Nut_House said:
Have you tried clearing cache and Dalvik and fixing permissions? The other thing to try, if you haven't already, is downloading the latest nightly and performing a clean install rather than dirty flashing. Good luck.
Click to expand...
Click to collapse
I've already tried installing the latest nightly version and ran a permission fix on it, but end up with the same result. I'll try clearing cache, dalvik, and then fixing again.
gharlane00 said:
If you accidentally refused root access the first time you have to go into the SU app and clear out the File manager permission and start over.
Click to expand...
Click to collapse
The file manager doesn't have any permissions in SuperSU and never asks for any since it's not in root access mode. :\
Nut_House said:
Have you tried clearing cache and Dalvik and fixing permissions? The other thing to try, if you haven't already, is downloading the latest nightly and performing a clean install rather than dirty flashing. Good luck.
Click to expand...
Click to collapse
Yeah, still the same result. Clearing dalvik and cache didn't work.
Just grab es file explorer.
Sent from my SPH-L720 using xda app-developers app
RogueSly said:
Yeah, still the same result. Clearing dalvik and cache didn't work.
Click to expand...
Click to collapse
same problem.
tried to install supersu, reinstall busy box on bin and xbin, fix permissions, no luck, option still greyed out.
file manager always worked for me as root, both on cm-based ROMs and aosp.
this time it is not working with the combo saberMod and matrix on N4.
(i think this is a device-independent issue)
---------- Post added at 08:20 PM ---------- Previous post was at 08:07 PM ----------
After a lot of tentatives I solved it.
I am not 100% sure of which change made it though
I think it was by using ES root manager and resetting system as R/W.
Sent from my Nexus 4 using xda app-developers app
Alternate fix
I also had the same issue and resolved it by tapping the menu button on the top left corner. when you do this, another menu button appears in the top right corner. Hit that, then settings, and choose root mode. Took me a while to figure out!!!
solved...
Installing busy box should resolve the issue...
Sorry for bumping, I have busybox and su installed, init.d support as well, but Cyanogen's File manager still cannot access root (option is grayed out). I'm on a stock Prestigio rom. It worked previously, but I reflashed firmware and now it doesn't work on this new firmware. Any thoughts?
Hi terirem and everybody,
I had this issue recently and I've managed to fix it. This is what You should do:
Short run:
Type in rooted phone terminal:
su
am start com.cyanogenmod.filemanager.ics
done
Long run:
1. Of course You need rooted phone, I've installed also BusyBox but I am not sure if it's necessary.
2. Install Terminal application
3. Install (if it's not installed yet) and run cyanogenmod file manager then minimize it by pressing home button (make sure You don't do anything else on Your phone to don't kill file manager process, it needs to be alive for 4th point)
4. I will make all commands bold for easier reading. run your terminal app and type: top -n 1 (this command will list all your running applications just once).
5. Find cyanogenmod in last "name" column, mine has name: com.cyanogenmod.filemanager.ics (if you can't find it you can try the one I had for 7th step, should probably work)
6. Type: su You will be asked to give superuser permissions to terminal, agree. Now instead of $ an # should appear, this means all commands from now on have root privilage.
7. Now we will finally rerun filemanager again with superuser permissions, type: am start com.cyanogenmod.filemanager.ics (if you had different name of filemanager just write the one you got after am start)
8. Go to cyanogenmod filemanager general settings and change access mode to root (it should be finally available, if not make sure again You typed am start with root permissions in terminal, if still doesn't work then forget about point 9).
9. Give me a beer, or actually simple thanks is enough, I need to stop drinking.
My SuperSU is kept auto-granting and system storage is kept read-written, also I cleared the every caches.
The CM file manager is still not shown a root mode to me.
I have J-rummy’s ROM toolbox as an alternative root explorer, but sometimes is less readable than CM file manager.
There is a guy forgetting to let the system storage read-written to remind him.
I did this with CM file manager - make sure you have root access not just safe mode in general settings. When you open filemanger it is granted super U access and then you can edit and save without issues
CM Dev Settings
In Dev options is Root access set to Apps and ADB?
For anyone else still having this problem, just erase the File Manager data (Settings | Apps | File Manager | Storage | Clear Data) with SU turned on in developer options. Then press the hamburger icon in the top-right of the app, press the settings icon on the bottom, click on General settings and you will see Access Mode
bsevcenk said:
For anyone else still having this problem, just erase the File Manager data (Settings | Apps | File Manager | Storage | Clear Data) with SU turned on in developer options. Then press the hamburger icon in the top-right of the app, press the settings icon on the bottom, click on General settings and you will see Access Mode
Click to expand...
Click to collapse
I am on CM13, now with SuperSU installed since I couldn't get the root option there to work well with some other apps for some reason.
File Manager now doesn't show any option for 'safe mode' or otherwise at all in settings. I cleared the data. I started it as in the earlier post. Nothing.
In the Developer options root is allowed, although only for ADB (the apps option has gone).
passtim said:
I am on CM13, now with SuperSU installed since I couldn't get the root option there to work well with some other apps for some reason.
File Manager now doesn't show any option for 'safe mode' or otherwise at all in settings. I cleared the data. I started it as in the earlier post. Nothing.
In the Developer options root is allowed, although only for ADB (the apps option has gone).
Click to expand...
Click to collapse
same here for me.
I'm working on a fix for now.
EDIT
If you're on a systemless SuperSU, use a terminal or ADB shell to input the following lines:
Code:
su
mount -o remount,rw /system
ln -s /su/bin/su /system/xbin/su
id74em8 said:
same here for me.
I'm working on a fix for now.
EDIT
If you're on a systemless SuperSU, use a terminal or ADB shell to input the following lines:
Code:
su
mount -o remount,rw /system
ln -s /su/bin/su /system/xbin/su
Click to expand...
Click to collapse
Apologies, but I'm no expert at these things. What is a 'systemless' SuperSU?
Is making a link as you suggest safe?
MOD EDIT @gregbradley
Also, users should be aware that Kingo root sends your IMEI to an unknown IP address in china during the root process, you have been warned. For more information read the whole OP here
XPERIA ANDROID 5 LOLLIPOP EASY ROOT :
ALL LOCKED&UNLOCKED BOOTLOADERS.
1-) Copy ALP folder in phone memory.
2-) Settings >Security > Unknown sources make it open. And Settings > Developer Options > USB debugging make it on. (If developer options exist go Settings > About phone and click Build number (7 times))
3-) Install Root.apk Allow all messages.
4-) Install Recovery.apk
5-) Install Busybox.apk
6-) Open KingRoot and click Root button.
MOD EDIT @gregbradley
Also, users should be aware that Kingo root sends your IMEI to an unknown IP address in china during the root process, you have been warned. For more information read the whole OP here
6-) Wait to complete. İf you see a chinese blue button click it. All of messages you will allow.
7-) When you see blue tick symbol or %100 its ok.
Look to the menu KingUser its in here ok. No problem don't open it.
9-) Open busybox and install it. When you see It looks like busybox installed succesfully congratulations message its ok.
10-) Open XZRecovery and click Install Recovery .
11-) Phone will be reboot and recovery will open.
12-) Install > find ALP folder and select SuperSU.zip then swipe and install it.
13-) Complete the install Wipe Cache/Dalvik and reboot the phone.
14-) You can see SuperSU in menu and check with rootchecker your root access.
15-) Everything OK. You can enjoy with your rooted Android 5 lollipop device.
16-) You can uninstall KingRoot, busybox, Xzrecovery app. (won't delete supersu or ndrutils)
PREPARED BY ALPEREN ÇUBUK.
DOWNLOAD LİNK : https://yadi.sk/d/qMsejobDgedBw
MIRROR :
https://app.box.com/s/86e7vlwfmu5z62lo95vu2kfej38uj01q
NOTE: Extract downloaded zip and copy ALP folder your phone memory.
Thanks for the comprehensive guide. For some reason step 11) Getting my D6653 into recovery is not working (Also tried ADB reboot recovery)
Any ideas?
EDIT: After updating BusyBox, and then re-installing the Recovery, it re-started and is now stuck in a bootloop..
EDIT2: The bootloop is very likely related to this (from this post: http://forum.xda-developers.com/showthread.php?t=2261606):
"@vaisakh7 found a busybox updater which seems to be compatible with XZDualRecovery: Busybox On Rails, which installs a version of busybox created by stericson, which leads me to believe his Busybox installer should also install a version which works together with XZDualRecovery.
Either case, be careful with updating busybox as there still is a possibility it will break your ability to enter recovery or even break full root, which means you might not be able to recover from the broken situation. Your best bet is the installer version, using that to break the lock on the system partition and reinstall the correct busybox."
Recommended to NOT update BusyBox
Busybox can never be installed through this process always failed and there is no other option left once busybox installation failed except to reinstall the whole firmware please add the steps to guide for busybox installation too
Does this method null the waranty?
Sent from my Xperia Z3
I have rooted successfully Desire 626 (At&t) that's on Android Version 5.1, Steps on how to root below:
First Enabled "Unknown sources," Settings->Security->Tick the Check Box and Click yes.
Return to App Drawer, open File Manger and install "KingRoot-4. 1 .0.249.apk" when finish installing open the app
"Ignore any error message" and start root (Internet Connection required) once successfully rooted verify with "Root Checker" app
Now to replace "Kinguser" with "Supersu" install a "Terminal Emulator" app, Extract the file "KS.zip" and place the extracted folder on the root (main) of your Phone Storage, now open terminal emulator app and type the code below:
su
"allow root permission when asked"
sh /sdcard/mrw/root.sh
" after typing the above code ignore any errors til the process is complete, Supersu will open if successful
When asked to update binary select "normal" and reboot if asked.
Done.
N.B. I have package the files needed to do the root here : https://goo.gl/A7BIsD
N.B. Your Bootloader must be Unlocked !
Link to packaged files needed to do the root is broken. Could you please re-post?
Michaela888 said:
Link to packaged files needed to do the root is broken. Could you please re-post?
Click to expand...
Click to collapse
Sorry bout that....link has been Updated.
Thank you for the quick reply. I don't know what I'm doing wrong. I downloaded the zip file, installed KingRoot and opened the app, but the root keeps failing. I've tried multiple times and KingRoot fails at around 60% every time. I updated KingRoot and that failed, too. Based on your screenshots, it seems like we have the exact same phone with AT&T. Would really love to root if you have any suggestions. ("Unknown sources" is enabled and Bootloader is unlocked ) Thank you!
Michaela888 said:
Thank you for the quick reply. I don't know what I'm doing wrong. I downloaded the zip file, installed KingRoot and opened the app, but the root keeps failing. I've tried multiple times and KingRoot fails at around 60% every time. I updated KingRoot and that failed, too. Based on your screenshots, it seems like we have the exact same phone with AT&T. Would really love to root if you have any suggestions. ("Unknown sources" is enabled and Bootloader is unlocked ) Thank you!
Click to expand...
Click to collapse
use the kingroot app provided...if your bootloader is unlocked then it should work.
uninstall kingroot and restart your phone.. connect to WiFi or Data, reinstall kingroot open and try root again..if it fails try again at least 3 more times.
Worked perfect for me
Adrian Dennis said:
I have rooted successfully Desire 626 (At&t) that's on Android Version 5.1, Steps on how to root below:
First Enabled "Unknown sources," Settings->Security->Tick the Check Box and Click yes.
Return to App Drawer, open File Manger and install "KingRoot-4. 1 .0.249.apk" when finish installing open the app
"Ignore any error message" and start root (Internet Connection required) once successfully rooted verify with "Root Checker" app
Now to replace "Kinguser" with "Supersu" install a "Terminal Emulator" app, Extract the file "KS.zip" and place the extracted folder on the root (main) of your Phone Storage, now open terminal emulator app and type the code below:
su
"allow root permission when asked"
sh /sdcard/mrw/root.sh
" after typing the above code ignore any errors til the process is complete, Supersu will open if successful
When asked to update binary select "normal" and reboot if asked.
Done.
N.B. I have package the files needed to do the root here : https://goo.gl/A7BIsD
N.B. Your Bootloader must be Unlocked !
Click to expand...
Click to collapse
hey, i was helping a friend out and see kingroot dose work, but we want to get SU on his phone can you upload that KS.zip as the link dont work
thanks
Hello, I'm on the latest 6.0.1 stock. I've used Nexus Root Toolkit to unlock my bootloader, root (SuperSU), and flash TWRP. I flashed Xposed using the Xposed installer. Now I'm looking to get AdAway up and running. I've done some searching and I see some conflicting reports about whether this needs to be done systemless, and how to get it working. Stuff I've heard is:
1. Just install the apk from XDA and install normally, update hosts, and you're good.
2. Install apk, use a program (like Titanium Backup) to make it a system app, update hosts, done.
3. Install apk, flash some sort of AdAway package in TWRP, update hosts, done.
4. Install apk, do some adb process to create a symlink of some sort, update hosts, done.
5. I haven't heard anyone really mention it, but in Preferences I see an option to "Enable systemless mode" which I haven't seen anyone really mention.
Can someone tell me which way I need to use, please?
>>> I also saw someone say that I need to use a file explorer after updating hosts to manually switch the permissions of the hosts file, in order to improve performance. Can anyone tell me if this is accurate, and if so how to do it?
Thanks!
kwest12 said:
Hello, I'm on the latest 6.0.1 stock. I've used Nexus Root Toolkit to unlock my bootloader, root (SuperSU), and flash TWRP. I flashed Xposed using the Xposed installer. Now I'm looking to get AdAway up and running. I've done some searching and I see some conflicting reports about whether this needs to be done systemless, and how to get it working. Stuff I've heard is:
1. Just install the apk from XDA and install normally, update hosts, and you're good.
2. Install apk, use a program (like Titanium Backup) to make it a system app, update hosts, done.
3. Install apk, flash some sort of AdAway package in TWRP, update hosts, done.
4. Install apk, do some adb process to create a symlink of some sort, update hosts, done.
5. I haven't heard anyone really mention it, but in Preferences I see an option to "Enable systemless mode" which I haven't seen anyone really mention.
Can someone tell me which way I need to use, please?
>>> I also saw someone say that I need to use a file explorer after updating hosts to manually switch the permissions of the hosts file, in order to improve performance. Can anyone tell me if this is accurate, and if so how to do it?
Thanks!
Click to expand...
Click to collapse
Hello... Just allow SU permission, tic "enable systemless mode" in preferences if you use systemless Root. Tap on "disable" next to the red cross and let it download the new host. When prompted, reboot. Done...
Never seen anything about setting extra permissions... I don't read the XDA thread anyway and downloaded the app from here: https://f-droid.org/repository/browse/?fdid=org.adaway
Cheers...
Hi there,
First of all, lemme tell what i did.
Phone model : Huawei p9 lite VNS-L31 ( Dual Sim )
I downgraded my p9lite to andriod 6.0
After that, i unlocked the bootloader, unlocked my Phone etc and installed TWRP.
Phone was still working at this point. Installed the magisk root and Phone still worked.
main reason i wanted to root is to spoof at pokemon go ( yeah it sounds silly, but it is ).
In order to make it work i had to do some stuff, heres a copy paste from the website i followed the tutorial from :
* Step 5- Download a GPS Spoofing app of your choice. I prefer GPS Joystick but I have had great success with Fake GPS Floater. HERE is a known working GPS Joystick apk from my phone to use instead of converting the app over.
Download Service Disabler
Download a root file manager. I use root explorer but I believe its a paid only app, give Root Browser a try from HERE.
Download GPS Test app from HERE
Now its time to convert your spoofing app to a system app. If you downloaded my apk open your root explorer and copy/paste the apk to /system/priv-app and select the file and change permissions to 644 (all read selected and owner write selected), skip the rest of these steps below. If you downloaded from the Play store Open up your root explorer and navigate to /data/app and find the gps spoofing app that you installed and select the entire folder and cut it to /system/priv-app. Now go into the folder that you just moved and delete everything but the apk, All odex files and folders must go. Now long press highlight the apk and change permissions of the file to 644 (all read selected and owner write selected). Back out to the folder that the apk is in and do the same but set permissions to 755 (all read, owner write, and all execute).
Next up is Service Disabler, open the app and go to the system tab, search for location, open fusedlocation and disable it (samsung owners need to do the same for Samsungfusedlocation), search again for google and select google play services, navigate down to fusedlocation and disable it.
Next open GPS Test and go to hamburger menu, AGPS and select clear only.
Reboot to recovery and select wipe, advanced, select dalvic cache and cache. swipe to wipe and then reboot. Boot up time will take a few minutes to optimize all apps.
I followed the steps verry carefully.
My Phone starts to huawei logo, it stays on the logo and it goes to the Huawei eRecovery.
any suggestions?
Restart your phone by holding power button (Hold it until it vibrates).
try this 20 times for example , till it boots into system
FunnkyHD said:
Restart your phone by holding power button (Hold it until it vibrates).
try this 20 times for example , till it boots into systen
Click to expand...
Click to collapse
Tried it, but it does not boot.
solvathus said:
Hi there,
First of all, lemme tell what i did.
Phone model : Huawei p9 lite VNS-L31 ( Dual Sim )
I downgraded my p9lite to andriod 6.0
After that, i unlocked the bootloader, unlocked my Phone etc and installed TWRP.
Phone was still working at this point. Installed the magisk root and Phone still worked.
main reason i wanted to root is to spoof at pokemon go ( yeah it sounds silly, but it is ).
In order to make it work i had to do some stuff, heres a copy paste from the website i followed the tutorial from :
* Step 5- Download a GPS Spoofing app of your choice. I prefer GPS Joystick but I have had great success with Fake GPS Floater. HERE is a known working GPS Joystick apk from my phone to use instead of converting the app over.
Download Service Disabler
Download a root file manager. I use root explorer but I believe its a paid only app, give Root Browser a try from HERE.
Download GPS Test app from HERE
Now its time to convert your spoofing app to a system app. If you downloaded my apk open your root explorer and copy/paste the apk to /system/priv-app and select the file and change permissions to 644 (all read selected and owner write selected), skip the rest of these steps below. If you downloaded from the Play store Open up your root explorer and navigate to /data/app and find the gps spoofing app that you installed and select the entire folder and cut it to /system/priv-app. Now go into the folder that you just moved and delete everything but the apk, All odex files and folders must go. Now long press highlight the apk and change permissions of the file to 644 (all read selected and owner write selected). Back out to the folder that the apk is in and do the same but set permissions to 755 (all read, owner write, and all execute).
Next up is Service Disabler, open the app and go to the system tab, search for location, open fusedlocation and disable it (samsung owners need to do the same for Samsungfusedlocation), search again for google and select google play services, navigate down to fusedlocation and disable it.
Next open GPS Test and go to hamburger menu, AGPS and select clear only.
Reboot to recovery and select wipe, advanced, select dalvic cache and cache. swipe to wipe and then reboot. Boot up time will take a few minutes to optimize all apps.
I followed the steps verry carefully.
My Phone starts to huawei logo, it stays on the logo and it goes to the Huawei eRecovery.
any suggestions?
Click to expand...
Click to collapse
As far as i noticed, on a huawei p9 lite you can't disable a system module, such the fused location module. I know, I did this mistake by myself time ago for the same purpose as yours and i did'nt find a solution. Another strange thing is that after the wipe data and th magisk reflash (reinstall) the safetynet test won't pass. That's strange..