I have been trying to change write permissions for an app called SecondScreen so i can change the resolution in Desktop mode.
I keep getting a adb version number error when trying to change the permission
"adb server version (39) does'nt match this client (41);killing"
It will still display my phone afterward, but i keep geting the same error when typing in the command..
abd shell pm grant com.farmerbb.secondscreen.free android.permission.WRITE_SECURE_SETTINGS
i read the cable and even the USB port can cause an issue...i was able to get powershell to change the settings once but started over because the app didnt work well with Desktop mode so my Taskbar is now stuck looking huge...
Sorry, i am new to ADB, and just want to try to get this one app working.
pm grant com.farmerbb.secondscreen.free android.permission.WRITE_SECURE_SETTINGS
Related
ok so on most roms this happens. i need a SU request but my phone freezes obn a black screen and on the top in gray it says SU request. i wait paciently and maybe 1-2 mins later is asks to FC because its not responding. is there a fix or what am i doing wrong. usb debugging is on and so is install nonmarket apps idk wtf im doing wrong or if somthing is just not working. any input??
I've heard su is not working properly until you activate it once via adb. In your teriminal (cmd or similar)
Code:
adb shell
$su
You should get a working super user request after which all other su requests should work fine.
Marisa said:
I've heard su is not working properly until you activate it once via adb. In your teriminal (cmd or similar)
Code:
adb shell
$su
You should get a working super user request after which all other su requests should work fine.
Click to expand...
Click to collapse
yes same thing happens to me
plug in your phone
goto your android sdk tools
and input adb shell
now go back to your phone and try it while still plugged
thats what i have been doing...
the same thing is happening for me and the instructions of simply input adb shell into terminal arent helping really. if someone could tell me exactly where to be aiming the command prompt and what the exact commands are in order to fix this I would greatly appreciate it.
WalkingTaco said:
the same thing is happening for me and the instructions of simply input adb shell into terminal arent helping really. if someone could tell me exactly where to be aiming the command prompt and what the exact commands are in order to fix this I would greatly appreciate it.
Click to expand...
Click to collapse
Are you getting the same crshes and things, but when you do the adb shell # pops up instead of $?
whenever i do adb shell I get #, so that means SU is already activated, but it's actually not on my phone, so i have no idea what's going on and no one seems to know how to fix it.
no. my Su permissions always force close after a minute of black screen. there is a fix posted above but my nerd level is not high enough to.infer the rest
Sent from my Eris using the XDA mobile application powered by Tapatalk
I don't know the exact command prompt setup, I'm running linux. However, when you originally rooted your phone you used the Android SDK correct?
With your phone plugged in, and USB Debugging enabled on your phone (Settings -> Applications -> Development -> USB Debugging) Open command prompt and get to the tools directory you used during rooting, I don't know where you installed it, so I cannot guide you through that part. If you used Ivan's guide http://forum.xda-developers.com/showthread.php?t=647707 it's probably best to refresh yourself there.
Once you've found your SDK /tools/ in command prompt, it should be as easy as running the code I mentioned earlier
Code:
adb shell
$su
in the command prompt.
The superuser prompt should show up on your phone, tell it to allow it and it should work without fail until you flash a new ROM that has the bug.
thanks very much. I used Ivans guide. I rooted it yesterday when o got my replacement from Verizon in store. I had been using the 2.1 leak on my old one and complained in store for thirty seconds. they didn't even look at it gave me a replacement in ten minutes
Sent from my Eris using the XDA mobile application powered by Tapatalk
Rock out thanks for the Super Help
Sorry for the noob question, but I am having some troubles doing a backup with adb. I have my phone rooted and can connect with adb, however I cant do a "adb pull / d:\whereveriwantit" without it just saying skipping special file for everything. I'm assuming because it is not pulling as root. So I try "adb shell" then "su" and I get root privileges, but then I cant figure out how to copy everything to say /sdcard/temp/ for me to then copy to my laptop (my unix command knowledge is lacking). Any help would be appreciated.
[EDIT] After some more playing around. I guess I can pull some things using the adb pull / <dir> , but alot of files are skipped "skipping special file" or "permission denied". Would using the proper commands in the shell after switching to root user be a better way to get the files copied?
SuperSU works fine and grants permission to Root Explorer which also works fine.
But 'getprop: permission denied' is shown in front of most of the headings in 'Phone information' tab in MTK Droid Tools.
And when I click 'Root' button in MTK Droid Tools the following message is shown 'ERROR: SU inaccessible'.
I have granted permission to ADB Shell in SuperSU.
If I manually open adb shell I get $ prompt and then I type su to get # prompt.
I think that maybe permissions of some files are not ok.
Please help!
threatalive said:
SuperSU works fine and grants permission to Root Explorer which also works fine.
But 'getprop: permission denied' is shown in front of most of the headings in 'Phone information' tab in MTK Droid Tools.
And when I click 'Root' button in MTK Droid Tools the following message is shown 'ERROR: SU inaccessible'.
I have granted permission to ADB Shell in SuperSU.
If I manually open adb shell I get $ prompt and then I type su to get # prompt.
I think that maybe permissions of some files are not ok.
Please help!
Click to expand...
Click to collapse
I know I am bumping this thread, but someone recently asked me the solution for this issue.
So, for anyone who might face the same problem: this error occurs due to broken symlinks of toolbox or busybox etc.
To fix it, you need to create the missing symlinks.
A simple solution is to re-root your mobile.
Device won't respond to "adb shell wm" even though "wm" exists in /system/bin
I'm trying to change the pixel density on my unrooted RN3P using the "adb shell wm density XXX" command.
I'm running Krexus-CAF ROM.
ADB is set up and working, and I can open a shell on the device.
The problem is that `wm` cannot be found, even though it exists on the device at `/system/bin/wm`. I cannot do this with the "adb shell wm density XXX" command, nor if I open a shell on the device and type "wm density"
The output is:
Code:
~/Library/Android/sdk/platform-tools $ adb shell wm density 400
/system/bin/sh: /system/bin/wm: /bin/sh: No such file or directory
Has anyone had success with this, or can tell me why the "wm" command cannot be found, even though it exists in the directory that the device looks in?
Cheers
DoubleDroz said:
I'm trying to change the pixel density on my unrooted RN3P using the "adb shell wm density XXX" command.
I'm running Krexus-CAF ROM.
ADB is set up and working, and I can open a shell on the device.
The problem is that `wm` cannot be found, even though it exists on the device at `/system/bin/wm`. I cannot do this with the "adb shell wm density XXX" command, nor if I open a shell on the device and type "wm density"
The output is:
Has anyone had success with this, or can tell me why the "wm" command cannot be found, even though it exists in the directory that the device looks in?
Cheers
Click to expand...
Click to collapse
First check for "adb devices". If it doesn't show then check for the drivers. After that set path of adb in windows to default. Try again with debugging enabled.
mehulchirania said:
First check for "adb devices". If it doesn't show then check for the drivers. After that set path of adb in windows to default. Try again with debugging enabled.
Click to expand...
Click to collapse
thank you for taking time out to try help.
i'd just say that your solution isn't what the OP is looking for.
mainly because if you read the post he tried adb shell wm.....
but also tried on the phone inside terminal app typing the command..
i personally don't have a solution but i thought i'd try help you try maybe another suggestion?
for example, i can now go and tell the OP to download and install angry bird or busybox etc but it won't make a difference.
mehulchirania said:
First check for "adb devices". If it doesn't show then check for the drivers. After that set path of adb in windows to default. Try again with debugging enabled.
Click to expand...
Click to collapse
As noted in the question, I can definitely find my device, as I was running the shell on the device with ADB. The problem was that I could not execute `wm`, even though it was listed in the directory.
I ended up switching ROMs, and could use `wm` without issue - I'm not sure what it was about the ROM I was using that meant I couldn't use the files listed.
Oh well.
Hi, I hope I am posting in the right section? I found the site really difficult to navigate having never used the site before. If its in the wrong place please can a mod move it.
Ok so I have an Android Set Top Box (STB) and I am trying to extract all the data from it. It is an mxp pro 4k. I don't want a backup of the data I want to extract full images of the device for analysing with forensic tools. The problem is I can't seem to communicate with it. I have the full SDK that is up to date, once navigated to the platform tools folder I opened a command line and typed
Code:
adb devices
after plugging in a USB cable to the OTG port. No prompts appeared on the screen to trust any connections like my iPhone does when I connect it. Adb devices returns no results. So I tried wireless adb, I typed
Code:
adb connect 192.168.x.x
and it said connected. Then when running the devices command I had the ip and port then the word device. I then get a shell by using
Code:
adb shell
Which i then elevate to root by using
Code:
su
. Then when i try an adb pull or adb backup I get a message saying error device offline.
Im new to Android so not even sure I am doing it right. I have done a lot of reading and research but seem to be stuck with the basics. To confirm USB debugging is turned on.