Some of my apps, like goldendict and rootexplorer, can't detect my sdcard, but my phone do detect. In fact, poweramp can read and play songs from it. Already tried resintalling those apps. Problem persist.
I'm on stock firmware 4.3 rooted and with doomlord dual recovery
i'm having a similar problem.
it's not like they don't detect it, they don't go there automaticly, whatsapp didn't look for backups there, bsplayer won't load movies from there, apps-backup don't look for backup files on the sdcard.
but if i try to manually tell any of them to go there some of them find it.
strange thing.. didn't happen in 4.2.2, i use iHackers rom 2.0
Did you tried the apps i said? How do i manually them? They don't have this option.
I'm thinking in going back to 4.2 what's the difference between them? Also, i can't mount /system is this a 4.3 problem or 4.2 have it to?
ffp. said:
Did you tried the apps i said? How do i manually them? They don't have this option.
I'm thinking in going back to 4.2 what's the difference between them? Also, i can't mount /system is this a 4.3 problem or 4.2 have it to?
Click to expand...
Click to collapse
4.2 can mount /system as R/W because if you root it, you get full root but currently on locked bootloaders on android 4.3 you get only partial root.
I have root explorer and it can detect my sd card. Are you sure you are going to the right directory? /sdcard1 or /storage/sdcard1
Regards,
~J2C
But i have unlocked bootloader, what i got wrong? And you don't understand, root explorer don't even open. Goldendict open and says that i have no sdcard, then it closes...
SOLVED!! I just disabled Xprivacy from xposed and now everything works. I didn't configured yet, so it may work. I'll try to enable and configure it to have both working.
Shteren, do you use xprivacy too?
Related
So i'm kinda of stuck here. Pandora for some reason is having trouble installing, gives me error 24. I'm reading that I just need to delete the information for pandora from /data/data but the kitkat 4.4 leak isn't rooted. Is there a way to remove these files without root or am I stuck doing a factory reset? Didn't want to have to do that but I may be out of options..
You need root to see the /data folder or touch it.
I have been trying to get "gsam root companion" to work on my htc one. I've rooted my device just so i could check out the features such as wake lock, etc.
The thing is, it keep saying "The Root Companion application is not installed correctly in /system/priv-app."
I tried manually installing it by copying the "com.gsamlabs.bbm.rootcomanion-1.apk" (whether or not if its the correct file) into the system/priv-app location. That restarted my device, and the file just disappeared from the priv-app location as well, and so the problem persist.
Am i doing everything wrong manually. Wish I could find a tutorial vid =/.
Thank you in advance
elfking7 said:
I have been trying to get "gsam root companion" to work on my htc one. I've rooted my device just so i could check out the features such as wake lock, etc.
The thing is, it keep saying "The Root Companion application is not installed correctly in /system/priv-app."
I tried manually installing it by copying the "com.gsamlabs.bbm.rootcomanion-1.apk" (whether or not if its the correct file) into the system/priv-app location. That restarted my device, and the file just disappeared from the priv-app location as well, and so the problem persist.
Am i doing everything wrong manually. Wish I could find a tutorial vid =/.
Thank you in advance
Click to expand...
Click to collapse
in order to write/modify/delete file in /system, you need an unsecured kernel (/system writeable), otherwise all changes made to /system will be reverted at reboot. I'm not using and never used gsam, maybe there is another option but the only one I know is to flash a custom kernel.
Kernel for the htc one (M7) are listed here
make sure to chose one that is compatible with your rom (sense/gpe based or AOSP based)
elfking7 said:
I have been trying to get "gsam root companion" to work on my htc one. I've rooted my device just so i could check out the features such as wake lock, etc.
The thing is, it keep saying "The Root Companion application is not installed correctly in /system/priv-app."
I tried manually installing it by copying the "com.gsamlabs.bbm.rootcomanion-1.apk" (whether or not if its the correct file) into the system/priv-app location. That restarted my device, and the file just disappeared from the priv-app location as well, and so the problem persist.
Am i doing everything wrong manually. Wish I could find a tutorial vid =/.
Thank you in advance
Click to expand...
Click to collapse
I just fiddled with this the other day, but didn't use the Root Companion app. It's not the Root Companion apk that's moved to /system/priv-app. It's the actual GSam Battery Monitor apk, com.gsamlabs.bbm.apk. The Root Companion app just does the move for you. If you have a file manager with root r/w permission, you should be able to do it yourself. Just move com.gsamlabs.bbm.apk from /data/app to /system/priv-app. Then restart your phone. I actually used an app called Link2SD to convert GSam Battery Monitor from a user app to system app and it accomplished the same thing.
alray said:
in order to write/modify/delete file in /system, you need an unsecured kernel (/system writeable), otherwise all changes made to /system will be reverted at reboot. I'm not using and never used gsam, maybe there is another option but the only one I know is to flash a custom kernel.
Kernel for the htc one (M7) are listed here
make sure to chose one that is compatible with your rom (sense/gpe based or AOSP based)
Click to expand...
Click to collapse
I'm running the stock AT&T 4.4.2 ROM rooted with the stock kernel and haven't had any issues with changes reverting back after a reboot. I use ES File Explorer & set it to have R/W permissions in that app's settings, but I assume that only applies to that app. Yet I've converted a few apps from user apps to system apps (3rd party launcher GSam Battery Monitor & SuperSU are the ones I remember off the top of my head) and never noticed them switching back to user apps. That is until I update them; then they become user apps. I don't know if this is because the apps I'm using to switch them have SU permissions or what, but none have changed back by simply rebooting. And as far as I know, I haven't done anything to modify the stock kernel from the OTA. Is it even possible to unsecure a stock kernel using apps?
alray said:
in order to write/modify/delete file in /system, you need an unsecured kernel (/system writeable), otherwise all changes made to /system will be reverted at reboot. I'm not using and never used gsam, maybe there is another option but the only one I know is to flash a custom kernel.
Kernel for the htc one (M7) are listed here
make sure to chose one that is compatible with your rom (sense/gpe based or AOSP based)
Click to expand...
Click to collapse
Thank you so much. I had this problem for days. Why isn't my unlocked phone writeable in the first place...
sharksfan7 said:
I just fiddled with this the other day, but didn't use the Root Companion app. It's not the Root Companion apk that's moved to /system/priv-app. It's the actual GSam Battery Monitor apk, com.gsamlabs.bbm.apk. The Root Companion app just does the move for you. If you have a file manager with root r/w permission, you should be able to do it yourself. Just move com.gsamlabs.bbm.apk from /data/app to /system/priv-app. Then restart your phone. I actually used an app called Link2SD to convert GSam Battery Monitor from a user app to system app and it accomplished the same thing.
I'm running the stock AT&T 4.4.2 ROM rooted with the stock kernel and haven't had any issues with changes reverting back after a reboot. I use ES File Explorer & set it to have R/W permissions in that app's settings, but I assume that only applies to that app. Yet I've converted a few apps from user apps to system apps (3rd party launcher GSam Battery Monitor & SuperSU are the ones I remember off the top of my head) and never noticed them switching back to user apps. That is until I update them; then they become user apps. I don't know if this is because the apps I'm using to switch them have SU permissions or what, but none have changed back by simply rebooting. And as far as I know, I haven't done anything to modify the stock kernel from the OTA. Is it even possible to unsecure a stock kernel using apps?
Click to expand...
Click to collapse
You just used your stock kernal 0.0
Why isn't mine like that. D=
elfking7 said:
You just used your stock kernal 0.0
Why isn't mine like that. D=
Click to expand...
Click to collapse
I have no idea. I didn't even know about needing an unsecure kernel to be able to write to /system. Nor do I know how the stock kernel became unsecure in the first place. All I've done is root the ROM as I normally would by flashing SuperSU. Then grant root permission to the apps that request it. If something in that process makes the stock kernel unsecured, then I don't know what it was.
You said in your OP that you tried manually moving the com.gsamlabs.bbm.rootcomanion-1.apk to /system/priv-app. First of all, that's the wrong apk. See my original reply for the apk you need to move. Do you even have GSam Battery Monitor installed? Battery Monitor & Root Companion are two separate apps. Battery Monitor needs to be installed before Root Companion will do its thing. At least I assume that's the case, b/c like I said before, I didn't use Root Companion to move Battery Monitor. But the description in Root Companion says all it does is move the Battery Monitor apk to /system/priv-app. Secondly, how did you move the apk? What app did you use?
Like I explained previously I originally used an app called Link2SD. That gives an option to convert user apps to system apps & vice versa. Just now I used it to convert GSam back to a user app. I wanted to test if moving the apk manually made a difference. After I converted it to a user app, I used ES File Explorer to cut & paste the GSam apk from /data/app to /system/priv-app. I then restarted my phone. The apk did not disappear and the app continues to work.
sharksfan7 said:
I have no idea. I didn't even know about needing an unsecure kernel to be able to write to /system. Nor do I know how the stock kernel became unsecure in the first place. All I've done is root the ROM as I normally would by flashing SuperSU. Then grant root permission to the apps that request it. If something in that process makes the stock kernel unsecured, then I don't know what it was.
You said in your OP that you tried manually moving the com.gsamlabs.bbm.rootcomanion-1.apk to /system/priv-app. First of all, that's the wrong apk. See my original reply for the apk you need to move. Do you even have GSam Battery Monitor installed? Battery Monitor & Root Companion are two separate apps. Battery Monitor needs to be installed before Root Companion will do its thing. At least I assume that's the case, b/c like I said before, I didn't use Root Companion to move Battery Monitor. But the description in Root Companion says all it does is move the Battery Monitor apk to /system/priv-app. Secondly, how did you move the apk? What app did you use?
Like I explained previously I originally used an app called Link2SD. That gives an option to convert user apps to system apps & vice versa. Just now I used it to convert GSam back to a user app. I wanted to test if moving the apk manually made a difference. After I converted it to a user app, I used ES File Explorer to cut & paste the GSam apk from /data/app to /system/priv-app. I then restarted my phone. The apk did not disappear and the app continues to work.
Click to expand...
Click to collapse
I followed alray's advice. I installed the elementalx kernel which made my system writeable, since my stock kernel wasn't originally. I then retry using the root companion (I installed gsam battery monitor since last week) which finally worked by using the automatic option that the root companion provided. I didn't notice much difference with the app, after giving the battery monitor privileged access to the system=/.
Hi, are there a rooted FTF 4.4 c6603 for download? so I just have to flash it and it's already rooted?
like this?
http://forum.xda-developers.com/showpost.php?p=52407809&postcount=2
balloontree said:
Hi, are there a rooted FTF 4.4 c6603 for download? so I just have to flash it and it's already rooted?
like this?
http://forum.xda-developers.com/showpost.php?p=52407809&postcount=2
Click to expand...
Click to collapse
You need to have a custom recovery installed to flash a pre rooted rom. It's easier to use Towelroot to root your phone
St.Jimmy90 said:
You need to have a custom recovery installed to flash a pre rooted rom. It's easier to use Towelroot to root your phone
Click to expand...
Click to collapse
thanks!
http://techglen.com/2014/06/17/how-to-root-xperia-z-zl-10-5-a-0-230-firmware-with-locked-bootloader/
now let's see if I am able to do the SDFix
http://techglen.com/2014/06/17/how-to-root-xperia-z-zl-10-5-a-0-230-firmware-with-locked-bootloader
ok, I've followed the above steps and downloaded root checker and it says that my phone is rooted.
then i download SDFix and run it, and restart my phone. I am still unable to access my SD card,
camera to write photos to SD card, delete photos from SD card....
balloontree said:
http://techglen.com/2014/06/17/how-to-root-xperia-z-zl-10-5-a-0-230-firmware-with-locked-bootloader
ok, I've followed the above steps and downloaded root checker and it says that my phone is rooted.
then i download SDFix and run it, and restart my phone. I am still unable to access my SD card,
camera to write photos to SD card, delete photos from SD card....
Click to expand...
Click to collapse
Please install supersu from playstore and root browser
I have superSU but under the Apps tab, it's blank, how do I add "quick pic" there?
I've launched "quick pic" and tried to delete some photos, it can't be done.
I have run the SDFix, it reports that it's been done.
I used root brower and check, the permission for the SDcard is no "777".
I tried to change it to "777" and was told it's not allow by the system.
SuperSU did not pop out at any time to "enable my apps for root access"
how did u guys do it on Sony Xperia Z?
balloontree said:
I have run the SDFix, it reports that it's been done.
I used root brower and check, the permission for the SDcard is no "777".
I tried to change it to "777" and was told it's not allow by the system.
SuperSU did not pop out at any time to "enable my apps for root access"
how did u guys do it on Sony Xperia Z?
Click to expand...
Click to collapse
Did you run supersu and updated your binaries?
St.Jimmy90 said:
Did you run supersu and updated your binaries?
Click to expand...
Click to collapse
I have open up supersu, and pop up saying there new updates, and I allow it to update.
Did I miss anything?
I was using the tr.apk to root, wondering if it's the right way?
balloontree said:
I have open up supersu, and pop up saying there new updates, and I allow it to update.
Did I miss anything?
I was using the tr.apk to root, wondering if it's the right way?
Click to expand...
Click to collapse
Umm, did you run towelroot? If you open the app there is an option to run it.
St.Jimmy90 said:
Umm, did you run towelroot? If you open the app there is an option to run it.
Click to expand...
Click to collapse
yes, i have run tower root, and then root checker confirmed its rooted,
but i still don't have permission (777) to sd card
I used root browser and unable to change to 777, it still says system did not give permission for it
could you tell me how u do yours? maybe i mis a step?
balloontree said:
yes, i have run tower root, and then root checker confirmed its rooted,
but i still don't have permission (777) to sd card
I used root browser and unable to change to 777, it still says system did not give permission for it
could you tell me how u do yours? maybe i mis a step?
Click to expand...
Click to collapse
I guess you mean your external SD Card.... Are you sure you can't write to it?
Btw, both my internal and external sd card are on 777...
St.Jimmy90 said:
I guess you mean your external SD Card.... Are you sure you can't write to it?
Btw, both my internal and external sd card are on 777...
Click to expand...
Click to collapse
yes, i meant my ext sd card.
they are not 777, i tried changing it and it says something like system deny
if i were to set my camera to store to ext sd card, when i take photos, it says it can't save
balloontree said:
yes, i meant my ext sd card.
they are not 777, i tried changing it and it says something like system deny
if i were to set my camera to store to ext sd card, when i take photos, it says it can't save
Click to expand...
Click to collapse
That's odd..... Reflash the firmware and root again.... Something is wrong there..
St.Jimmy90 said:
That's odd..... Reflash the firmware and root again.... Something is wrong there..
Click to expand...
Click to collapse
this is what I did:
1) copy towerroot.apk into phone, run it, and it says rooted
2) use root checker and it says it's rooted
3) using google play, and download superSU
4) load superSU and update binary
5) when using root browser, i can see ext sdcard not in 777
6) tried to change it to 777 and it says system not allow
7) installed titanium backup and it says it's rooted,
8) run titanium backup and back up some files
9) not able to see the titanium backup folder via usb thru the computer
10) only able to see it via the root browser, storage -> emulated -> titanium backup, and it's not 777
reflash the firmware? which one?
i'm thinking of using custom firmware
balloontree said:
this is what I did:
1) copy towerroot.apk into phone, run it, and it says rooted
2) use root checker and it says it's rooted
3) using google play, and download superSU
4) load superSU and update binary
5) when using root browser, i can see ext sdcard not in 777
6) tried to change it to 777 and it says system not allow
7) installed titanium backup and it says it's rooted,
8) run titanium backup and back up some files
9) not able to see the titanium backup folder via usb thru the computer
10) only able to see it via the root browser, storage -> emulated -> titanium backup, and it's not 777
reflash the firmware? which one?
i'm thinking of using custom firmware
Click to expand...
Click to collapse
The one you're currently using. For example .230 .ftf file.
The steps you did are all right. It looks like there's somehow a software issue..
I rooted with kingo and installed Urdriod version 2 via safestrap version 3.75. Then installed Titanium backup pro. Problem is Titanium doesn't work anymore. All the options are not there. It is saying current backup location is inaccessible.
I then noticed that many of my applications that work in conjunction with the sd card do not work. Youtube is broken on 4G. Evernote is broken. Many of my games are broke as well.
I then did a clean install of another Rom Dynamic Kat. It didn't fix anything.
Any suggestions?
Install xposed framework and this module.
http://forum.xda-developers.com/xposed
http://forum.xda-developers.com/xposed/modules/kitkat-sd-card-access-t2790992
Its telling me every time that:
Could not extract Xposed-Disabler-Recovery.zip
Could i do this manually some how?
bloodedemon said:
Its telling me every time that:
Could not extract Xposed-Disabler-Recovery.zip
Could i do this manually some how?
Click to expand...
Click to collapse
You shouldn't need the zip did you try installing the apk?
It looks like its installed with the rom but not active. I cannot activate it and i cant seem to get the module to work either. I tried the apk but it just says that i already have it and it wont install.
Phone is alot less useful if it cant interact with the sd card. Is there another way to get this going or to get the phone to read the sd?
Is superuser installed and working?
yes it is. I don't believe it's that.
bloodedemon said:
yes it is. I don't believe it's that.
Click to expand...
Click to collapse
What error message are you getting when you try to install the framework from the xposed installer app? You might also try uninstalling the xposed installer app then installing the version from the download link
Here is exactly what the message says:
SDcard:/storage/emulated/0/android/data/de.robv.android.xposed.installer/files
Copying Xposed-Disabler-Recovery.zip
Could not extract Xposed-Disabler-Recovery.zip
I know the copy I have isn't working but if I erase it I might never even get a copy on. But the copy I have won't even install or update.
bloodedemon said:
Here is exactly what the message says:
SDcard:/storage/emulated/0/android/data/de.robv.android.xposed.installer/files
Copying Xposed-Disabler-Recovery.zip
Could not extract Xposed-Disabler-Recovery.zip
Click to expand...
Click to collapse
Looks like this came up in the xposed forum here
Sounds like the xposed updater app extracts a backup to the external sd card during installation...which you can't access, hence the error. The consensus seems to be to install this app https://play.google.com/store/apps/details?id=com.devasque.fmount&hl=en to fix the folder permissions then xposed should install properly.
Well I think installing FolderMount did the trick. after i put it on the phone it detected a script error and asked if i wanted to fix it.i agreed and it rebooted and that did it! Thanks everyone!!!!!
Hello,
Something goes wrong at my ROM. I installed an app to fix the writepermission. It works, all things fine. But then I played with some apps to customize my ROM and suddenly an freeze and then an reboot. After this my es Explorer tells me "path not found". The sdcard symlink goes to /mnt/media_rw/sdcard1/. The other path to access the sdcard are /sdcard1/ /storage/sdcard1/
This works but not the symlink. I can also access the sdcard with Apps like Google+, picture Album or other. Only the Explorer won't work.
I try to change the /system/etc/permission/platform.xml but won't work. (I copied the stock file from the rom zip)
Can anyone help me to fix this? I don't want reflash the rom. I'm at Holiday and no wifi to update all the apps again. [emoji33]
Thanks
Greets Lars
Start your phone without sdcard, then put it back. See if this works. Try uninstalling the apps that messed your phone.
Nothing works. I make an Backup of my Apps and data and make an reinstall. Problem solved.