I have a plain vanilla CM10.1 on my HD+. The included CM File Manager runs fine with root privilege. I've also installed a newer version of Jackpal's Term (terminal emulator) which runs fine as well with root.
However, the current version of ES File Manager will not run with root privilege. When I try to activate this, I just get the message "Sorry, test failed." Interestingly, the app is visible in Settings>Superuser as "allowed", but it still fails to acquire root. (I already uninstalled and reinstalled ES File Manager a couple of times with no success.)
Additionally, another app I tried to install (SambaDroid) gets denied root by the CM Superuser app without me even being able to say yes or no.
So something is not working as it should be...?
Have you tried installing supersu from the market?
Sent from my PG86100 using xda app-developers app
jpisini said:
Have you tried installing supersu from the market?
Click to expand...
Click to collapse
No. I'm not sure whether installing multiple superuser apps is a good idea... I may end up with a system where the two apps slug it out and
I am left without root access. (OK, I do have backups so that wouldn't be a catastrophe.)
Having said that, I would have tried installing another SU if I could get rid of the CM SU in the first place, but these days this thing is baked into the Settings app and I've found no information as to whether (and if so, how) this can be disabled.
Hints anyone?
Seems I am the only one with that specific problem.
The solution (well, not really but probably better than mucking with the CM superuser app): I've removed ES File Manager and installed X-plore File Manager instead. The interface of the latter is not that great but it seems to do most (or all?) of what ES can do (plus it does open password-protected RAR files, a big plus for me). And of course it supports root...
Still I do not understand why ES would not work with the CM superuser but there you go.
Related
I just rooted again after boot looping. 1.3 and using Manual Nooter per instructions in that thread, fixed permissions in RM, USB debugging is checked. I'm up and running just fine, however I can't install Amazon App Store. I click on the .apk in the downloads of my browser and I get two choices to use, " App Installer", and "Package Installer". I try App Installer and I get "The application was not able to install onto your device. Please "Archive" and then "UnArchive" the application to try again. How do I "Archive" and then UrArchive" the application?
I try Package Installer and I get "There is a problem parsing the package".
I've reset and rooted numerous times because of boot loops issue, which I'm pretty sure I've solved, but every previous time I was able to install Amazon App Store.
Any assistance would be greatly appreciated.
Well I am not an expert by any means but it sort of sounds like a bad file have you tried deleting it and re-DLing it? You can DL it right onto the nook via email for example, Amazon will email you the link. If it's any problem other than that then it's way out of my league. Hope that works!
I've downloaded the .apk numerous times with stock browser and Opera Mini, and tried downloading it from the email amazon sent me with the download link. Same issues with all attempts.
Have you tried opening it with a file browser like Astro? Also try downloading the apk to your PC and then copy it to your Nook via USB, the Download on your Nook could be getting screwed up.
Also if you have ADB setup you can try running the command "adb install [insert apk filename here]" to try to install the Amazon Store.
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
reebz said:
I just rooted again after boot looping. 1.3 and using Manual Nooter per instructions in that thread, fixed permissions in RM, USB debugging is checked. I'm up and running just fine, however I can't install Amazon App Store. I click on the .apk in the downloads of my browser and I get two choices to use, " App Installer", and "Package Installer". I try App Installer and I get "The application was not able to install onto your device. Please "Archive" and then "UnArchive" the application to try again. How do I "Archive" and then UrArchive" the application?
I try Package Installer and I get "There is a problem parsing the package".
I've reset and rooted numerous times because of boot loops issue, which I'm pretty sure I've solved, but every previous time I was able to install Amazon App Store.
Any assistance would be greatly appreciated.
Click to expand...
Click to collapse
Did you check the "Unknown Sources" box in Settings -> Applications?
I don't mean to be condescending, but you didn't mention it in the OP.
yes, unknown sources is checked. I figured out how to fix problem. I moved .apk's to system/app using Root Explorer and using Package Installer, they installed just fine.
reebz said:
yes, unknown sources is checked. I figured out how to fix problem. I moved .apk's to system/app using Root Explorer and using Package Installer, they installed just fine.
Click to expand...
Click to collapse
Have the same problem and has heard the same soln. Root explorer is $4 at Android Mkt. Anyway to get it free ?
I paid for it. There may some other file managers that you can use, but I just dropped the dough for Root Explorer.
anilct said:
Have the same problem and has heard the same soln. Root explorer is $4 at Android Mkt. Anyway to get it free ?
Click to expand...
Click to collapse
For what it does it is cheap for $4. We need to pay for apps or else developers will quit building them.
jerrykur said:
For what it does it is cheap for $4. We need to pay for apps or else developers will quit building them.
Click to expand...
Click to collapse
Unless I am mistaken this does nearly everything Root Explorer does. At least I think I've heard that before. Having paid for and more importantly become familiar with Root Explorer, I have't actually tried it. But I do know it comes HIGHLY recommended.
https://market.android.com/details?...sMSwyLDEsImNvbS5lc3Ryb25ncy5hbmRyb2lkLnBvcCJd
Please Help - This doesn't solve my problem
Just rooted 1.3 again with both manual nooters. Everything is working fine now but I want to download Amazon App Store from The web.
It downloads fine but wont install - gives me a "your phone is protected" warning box saying that I should go to Settngs/Application and check the box to allow for outside downloads.
I DON'T HAVE AN APPLICATIONS OPTION UNDER SETTINGS. I had one when I was running cm7 - but not for a simple 1.3 manual nooter.
I have looked everywhere I can think of - can anyone help or have a work-around?
Hey all,
So I recently rooted a Kindle Fire 7" HD. The root itself seems to have been successful, and Superuser shows up in the app list. My main issue is that many apps that require root don't appear to be requesting root. For example, I also installed the Google Play store, and a lot of applications were crashing.
Typically my go-to first solution to such a problem is to fix permissions, so I downloaded ROM Manager and ran the fix permissions routine, but the dialog to approve/deny the superuser escalation never appeared. After a few reboots and futzing around with it I was able to get ES File Explorer, the terminal emulator, and the Busybox Installer to escalate permissions (which is how I got Google Play installed in the first place), but I haven't been successful in getting anything else to escalate to root.
Any suggestions? The tablet isn't mine (!), but when I get my hands on it tomorrow I will probably have the SuperUser app update SU and see if that helps. Any other suggestions? Thanks!
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,
I have the lg optimus l90.
I used the towelroot app to root the phone. i used a terminal app to verify that i do have root. when the app opened, it displayed a $ sign but when i typed "su" and pressed enter it gave me a "#" prompt. so am i rooted?
also i was told to install the superSU app. why do i need this? can't i just uninstall the bloatware right now since i am rooted?
I installed the superSU app but it was not able to install the su binary because i did not reboot the phone after using towelroot. I uninstalled the SuperSU app. anyhow, what do I need to do now to remove those bloatware apps. there is no option to uninstall in the apps section of the android settings application.
finally, I read somewhere that i should use nobloat app to uninstall the bloatware but it is not uninstalling the bloatware. I uninstalled it.
so what do I do now?
any help would be much appreciated.
thanks.
Superuser is needed for apps to have root rights to your phone. Install superuser. Reboot phone and open app. Reboot again if needed. Rooting is useless without superuser installed
Sent from my LG-D410 using Tapatalk
helix3000 said:
Hi,
I have the lg optimus l90.
I used the towelroot app to root the phone. i used a terminal app to verify that i do have root. when the app opened, it displayed a $ sign but when i typed "su" and pressed enter it gave me a "#" prompt. so am i rooted?
also i was told to install the superSU app. why do i need this? can't i just uninstall the bloatware right now since i am rooted?
I installed the superSU app but it was not able to install the su binary because i did not reboot the phone after using towelroot. I uninstalled the SuperSU app. anyhow, what do I need to do now to remove those bloatware apps. there is no option to uninstall in the apps section of the android settings application.
finally, I read somewhere that i should use nobloat app to uninstall the bloatware but it is not uninstalling the bloatware. I uninstalled it.
so what do I do now?
any help would be much appreciated.
thanks.
Click to expand...
Click to collapse
Along with root and SuperSU, you will also need a root App manager or root file manager. I personally prefer to use ES File Explorer as it is both an application manager ( user and system ) as well as an awesome file manager.
There is no list of acceptable system apps to remove. So be very careful as to what you uninstall or you may endup with a soft bricked phone or one that spazzes out whenever it feels like it. I would recommend making backups of any app you want to remove before uninstalling it. At least you might be able to restore them if something goes wrong.
shinobisoft said:
Along with root and SuperSU, you will also need a root App manager or root file manager. I personally prefer to use ES File Explorer as it is both an application manager ( user and system ) as well as an awesome file manager.
There is no list of acceptable system apps to remove. So be very careful as to what you uninstall or you may endup with a soft bricked phone or one that spazzes out whenever it feels like it. I would recommend making backups of any app you want to remove before uninstalling it. At least you might be able to restore them if something goes wrong.
Click to expand...
Click to collapse
thank you both for the replies.
so what exactly is SuperSU for? when I opened it up I saw nothing in the apps list and I did not see anything else in the other lists within the app. also, I did not restart the phone before trying to update the su files and when I did restart the phone nothing updated. So, do I use something like ES file explorer to remove bloatware?
by the way, when I tried to surf the web after installing superSU app, the web browser was extremely slow. the webpages loaded very slowly but when after I uninstalled the superSU app, it was loading the pages fast again as normal. what's up with that?
thanks.
helix3000 said:
thank you both for the replies.
so what exactly is SuperSU for? when I opened it up I saw nothing in the apps list and I did not see anything else in the other lists within the app. also, I did not restart the phone before trying to update the su files and when I did restart the phone nothing updated. So, do I use something like ES file explorer to remove bloatware?
Click to expand...
Click to collapse
SuperSU is a binary executable that grants or denies superuser requests. Without it root is worthless.
You won't see anything in SuperSU permission list until an app asks for superuser permissions. When first opening the SuperSU app you should get prompted to update/install the su binary. Allow that action to happen.
helix3000 said:
by the way, when I tried to surf the web after installing superSU app, the web browser was extremely slow. the webpages loaded very slowly but when after I uninstalled the superSU app, it was loading the pages fast again as normal. what's up with that?
thanks.
Click to expand...
Click to collapse
That's because the su binary was never updated.
shinobisoft said:
SuperSU is a binary executable that grants or denies superuser requests. Without it root is worthless.
Click to expand...
Click to collapse
so in order to run something like the nobloat app I need to grant it permission to be a superuser? I never had to do anything like that when I ran the nobloat app and It actually worked. It still does not make sense to me what supersu is used for.
That's because the su binary was never updated.
Click to expand...
Click to collapse
I ran the towelroot app and it was successful. However, I did not reboot the phone before attempting to update the su binary and the superSU app said i should restart before updating. I restarted the phone but it never updated the su binary when I ran the superSU app again. What do I do now?
thanks.
Gone and bought a locked Pixel 4 XL from my carrier and willing to accept no root but so far struggling to get my apps from my old phone without TiBu.
My problem at the moment is trying to get any app to install an apk.
I've enabled the ability in the special permissions part of settings but cannot get any app to install an APK.
Attempted an APK backed and restore with Solid Explorer and that failed.
You have to give each individual app permission to install from unknown sources. Whether it be installing an apk from solid explorer or chrome.
murphyjasonc said:
You have to give each individual app permission to install from unknown sources. Whether it be installing an apk from solid explorer or chrome.
Click to expand...
Click to collapse
I had done. In the end I did a fresh install of all the apps, downloading from the play store and weirdly the problem solved itself.