I had a problem where my Showbox app will consistently display "No connection error", there was also a problem where I couldn't even download to my internal storage using any download program(eg. ttorent, vuze, etc) and would say "invalidate service".
I found this fix through here on xda, but was intended for Galaxy Note 3, but also worked well on my Canadian Galaxy s4. Credit goes to Khizar, bigbiff, and daxgirl for this.
You'll need root, and a terminal emulator(I recommend Jack Palevich's version from Google play) but any version should do.
1)Open up the terminal emulator
2)type "su" ~without quotes~, hit enter
3) Now type this command, "restorecon -v -R /data/media" ~without quotes~
hit enter
4)Restart your phone, now you should be able to download to your internal storage, and use your Showbox app.
Related
Hello Guys,
I'm in great trouble with my MT3G. Last couple of days i'm facing "Superuser Permission" issue with any rooted ROM. After installing the rom with any installed root based software "SU" is just black screen, nothing happens. I'm running Amon Ra's 1.2.3 MT3G version. I've tried formatting the sd as FAT32 and then using the recovery utility to make Fat32/ext2/swap and also tried the built in fix in AR's 1.2.3 looks like nothing is fixing this issue.
Also i've tried clearing the cache through settings>apps>manage apps>su and it didn't help either.Plzzzzzzzzzzz need some help asap.Thanks
do you have any apps that require superuser permissions? because if you dont, then it kinda just chills there, and it SHOULD show a black screen if nothing is accessing those secret files.
to see if its working, go to terminal and type in "su" and hit enter. if nothing happens...then yeah, somthing is wrong. if nothing happens, runn "fix_permissions" in adb shell
oshizzle1991 said:
do you have any apps that require superuser permissions? because if you dont, then it kinda just chills there, and it SHOULD show a black screen if nothing is accessing those secret files.
to see if its working, go to terminal and type in "su" and hit enter. if nothing happens...then yeah, somthing is wrong. if nothing happens, runn "fix_permissions" in adb shell
Click to expand...
Click to collapse
Thanks for the reply. i'm trying to use "setCPU" and "Wifi Tether" and still getting the black screen on "su".I've tried to go through the terminal and after the # su nothing happens.Tried the adb "fix" also but no luck. No idea whats going on.
i suggest removing the su app and then installing it from the market. you can remove it via adb/terminal. i dont remember the code to remove stuff, search around the dream forums for that answer.
Make sure usb debugging is enabled.
How to get Root access of ADB on this CyanogenMod 10.1 (Jelly bean 4.2 version)?
On earlier CM version 10 (Jelly bean 4.1) there was "Developer options" in settings were I could simply change that, in "Root access" section. (Setting -> Developer options -> Root access -> App's and ADB)
My problem is that i get this: (shell has been denied superuser permissions) on my Samsung galaxy tab2 7.0 when trying to install app's wirelessly from my computer using "APK Batch Installer" that I found on the internet, ow and on the tab I use adbWireless app.
Typing "su" in terminal emulator and getting access to it doesn't work.
I am trying to solve this for few days and I just now found out that on CM 10 version everything would work if i would get ADB access, so I ended here asking for help. :fingers-crossed:
see video for accessing Developer Options http://youtu.be/mp07dPusJNA
then do your thing like before.
Legisy said:
How to get Root access of ADB on this CyanogenMod 10.1 (Jelly bean 4.2 version)?
On earlier CM version 10 (Jelly bean 4.1) there was "Developer options" in settings were I could simply change that, in "Root access" section. (Setting -> Developer options -> Root access -> App's and ADB)
My problem is that i get this: (shell has been denied superuser permissions) on my Samsung galaxy tab2 7.0 when trying to install app's wirelessly from my computer using "APK Batch Installer" that I found on the internet, ow and on the tab I use adbWireless app.
Typing "su" in terminal emulator and getting access to it doesn't work.
I am trying to solve this for few days and I just now found out that on CM 10 version everything would work if i would get ADB access, so I ended here asking for help. :fingers-crossed:
Click to expand...
Click to collapse
Ya I was looking for the same thing and came to a dead end so putting up a reply for the others.. You will have to choose the Root Access under developers option to read Apps and ADB only then you can do what you wanted to..
Default is only for apps that have root permissions, you have to choose root for aps + adb or only adb if you prefer...
VanirAOSP 4.4.3 on Samsung Galaxy XCover2 GT-S7710 - Fix "Cannot connect to camera"
I just want to share how to fix camera issues on XCover 2 after flashing to VanirAOSP 4.4.3. I hit a problem already reported multiple times: Launching of any camera like the Google Camera fails reporting "Cannot connect to camera", regardless if you install the camera with the Gapps package or from store.
After some investigation, I got my camera finally work:
- Uninstalled Google Camera from store
- flashed to latest Vanir 4.4.3.061114
- Installed Android Terminal Emulator (Jack Palevich) from store, doesn't rely on BusyBox
- Open Android Terminal Emulator and launch:
su -
mount -o rw,remount /system
ln -s /system/lib/libjhead.so /system/lib/libhead.so
mount -o ro,remount /system
- Reboot phone
- Installed Google Camera from store
I used SuperSU as root application.
Thanks to all of you guys participating in several discussions for help on this.
I'd like to have this in the VanirOS image. But I'm still disabled to reply to more specific threads.
wrong device.
this section is for the samsung galaxy camera, not for samsung devices that happen to have a camera.
I can't get AirMirror to connect to my S820L, either thru AirDroid Web or the Airdroid server app on Win7SP1. Is it working for anyone else?
First I should note I'm using Psilocelium's excellent pared-down v4.4.4 ROM. Whenever AirMirror tries to connect, I get two SuperSu messages on the phone, the first one in two lines. The first line states that "Airdroid has been granted superuser permissions" but the second line reads "kill -15" followed by some process number, which changes each time I make the attempt. Seconds later there's a second message, "Airdroid has been granted superuser permissions for an interactive shell." Then the AirDroid server app shows, "AirDroid failed to get root permissions...."
I also have an LG Optimus Fuel, on which AirMirror works just fine. When I try to use AirMirror with it, I don't get the "kill -15" message, it starts with the interactive shell message, then the chmod and so-on. Originally it was running the same identical version of SuperSU as the Samsung but I've since updated the Samsung to the latest version, which didn't change anything.
So I'm wondering, is AirDroid even known to be compatible with the Core Prime? Or might it be a SuperSU problem, a hiccup in Psilocelium's ROM, or (most likely of all) operator error?
I followed the instructions on this site to uninstall a program (really just disable it) without root. I use ADB on the command line to do it. However, I get an error and nothing happens. When I follow the directions, it says to type "adb devices" to connect your phone. So I do that and my phone connects. Then it says type "adb devices" again to list your devices. It lists two attached devices: My phone and "emulator". Sooooo, when I try to delete an app, I get an error message that I have multiple attached devices and it doesn't delete the app. I used the adb detach command to try to detach an advice. Doesn't work.
Any advice?
Thanks
Why don't you root and finish the job? You can uninstall after root without any problems. I've never heard that someone is able to uninstall application if the root is needed for uninstalling.
Root is the way to go but it's much easier with the Tmobile version and it's a must these days with the Gogole app being a mandatory update with the new Play Store layout.