[Completed] ./adb devices Command: Permission Denied - XDA Assist

I'm trying to get my computer set up for when my Nexus 6 arrives so that I can just flash the factory images onto it as sort of a learning experience. I'm using my 2014 Moto X Pure (XT1095) to try to get it to be recognized in Terminal using ./adb devices but it just keeps returning permission denied. I have USB debugging enabled and I'm following TechnoBuffalo's guide on YouTube but I can't seem to get it to work.
I'm using a 2014 Moto X Pure Edition (XT1095), stock, unrooted 5.1.1, 2015 rMBP OS X El Capitan 10.11.1, both Android Studio and Standalone Android SDK Tools installed with all of the tools and packages installed.

Update: Today I uninstalled Android Studio, all SDK files, and then reinstalled just the Standalone tools (Android 6.0 tools and the entire Platform Tools package) and after changing the directory and running ./adb devices, it is still returning this: "-bash: ./adb: Permission denied" every single time. I can't do anything with su or sudo commands because it keeps returning "su: sorry" after I type my admin password. I really can't do anything because it looks as if I have no permissions on my own computer. Is there any way I can gain root/super user privileges on my computer so I can use ADB/Fastboot?

Hi,
Here are a few threads about ADB,
Beginner’s Guide to the Android Debug Bridge
[GUIDE] ADB Workshop and Guide for everyone
[GUIDE] ADB For Beginners (Setup, Use, and More!)
[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.2
[TOOL]Minimal ADB and Fastboot [11-6-14]
I think your system is read only at the moment, and ADB will not work if so.
You can ask in one of the above threads if you still have issues. But read the first couple posts of each one, and it may help you.
Good luck!

Related

Newbie help with rooting Asus Transformer Prime via ViperMOD

I have never rooted an android device before and this is my first time. The reason I'm rooting is so I can enable the Virtuous Prime ROM (the guide for Virtuous Prime suggested to use ViperMOD to root first)
[ROOT] [TOOL][Updated 2.22.12]viperMOD PrimeTime v4.5 | Auto Root/Unroot/Busybox/CMW - xda-developers
^I'm following the instructions from the link above word for word. So far I've met the following Criteria:
-Enabled USB Debugging
-Running build 9.4.2.15
-Have "ASUS Android Composite ADB Interface" drivers installed and updated
I downloaded the ViperMOD 4.5 zip and extracted it to my PC. I opened the folder and right clicked on "viperMOD Primer Tool v4.5 - copy.bat". A cmd popped up with several different options; I pressed 1 to root, and pressed enter to skip the following two prompts (that ask if USB debugging is enabled and asus usb drivers are installed).
The CMD then showed the following message:
*daemon not running. starting it now on port 5037*
*daemon started successfully*
However the CMD just stopped there. It didn't show the following flood of text that should show up when rooting w/ ViperMod (like shown in this video: http://www.youtube.com/watch?v=C3OQkxmUyLc at 2:35)
I'm not sure if I'm missing something here. The guide however did say that I needed to "Kill Asus Sync and Splashtop" though I'm not exactly sure what it means by "kill". I don't have Splashtop running on my Prime nor Splashtop remote running on my PC. I also don't have ASUS Sync software installed on my PC and I disabled Auto-Sync on my Prime (HOWEVER, the ASUS Sync icon is still visible in my Prime's notification bar when I connect it via USB to my PC).
Any advice?
I had a similar problem
I tried to use superoneclick to root my Samsung Gravity and it hung on waiting for phone. I used the adb commands to load the zergRush exploit. So you need to find which exploit works on your phone, adb push the exploit, busybox, and su to your phone and use adb shell to do the root.
** DISCLAIMER: I'm pulling this command sequence out of my memory... you should find a better guide but this stuff may give you clues as to what to google for, or if you're familiar with shell you may see the gist of what you're trying to do **
The commands will look something like this:
adb push exploitfilename
adb push busybox.apk
adb push su
adb shell
chmod 755 exploitfilename
./exploitfilename
(wait for the exploit to finish)
pm install busybox.apk
pm install su.apk
reboot
Once it rebooted, I installed terminal through the market so I could do cool stuf like so:
su
mount -o remount,rw /dev/whateverdevhasyoursystemfolder /system
rm /system/app/Vendorgarbagebloatapp.apk
and so forth. Knowledge of linux and shell commands is your friend here for sure. Basically, you should know what you're doing or don't do it. I'm no fan of one-clicks for anything like this, it's too hard to figure out what went wrong if it goes wrong, plus this way you can learn new skills.
Can't seem to run Vipermod
I am trying to run vipermod on my computer but when I try to run it, it flashes on the screen for less than a second and then re-closes.
For a little extra info I have a tf101 running the 9.2.1.17 build
My computer is running the window 8 developers copy( no i'm not a dev just love testing new things before most other people.)
I've tried running it as an admin and in compatibility mode but have had no success as of yet any help would be greatly appreciated.
sasori563 said:
I am trying to run vipermod on my computer but when I try to run it, it flashes on the screen for less than a second and then re-closes.
For a little extra info I have a tf101 running the 9.2.1.17 build
My computer is running the window 8 developers copy( no i'm not a dev just love testing new things before most other people.)
I've tried running it as an admin and in compatibility mode but have had no success as of yet any help would be greatly appreciated.
Click to expand...
Click to collapse
U should tried on another comp with windows seven imo
I would if i had one but my laptop got stolen so my only computer besides my desktop is my transformer, Are their any .bat files out their that i can use to run it from? I found out that its a problem with windows 8 not allowing .exe files to open command prompts, but if its a .bat file it will run.

[S-Off] and Device Offline for PJ831000

This was answered a little bit in the S-Off thread and I would like to post it for everyone that has the PJ8310000 device and they are running into device "offline" when using adb devices. This is for Windows 8 only. I had the same problem in OSX, but I believe the solution is the same. I cannot post in the thread in the developer section yet, that is why this is here.
First, if you can't see your device in your device manager, make sure you have the latest HTC Device drivers installed or install the latest version of HTC Sync. This is very important for Windows 8.
Second, you will need to download and install the latest Android SDK. Just "Download From Other Platforms" and choose the appropriate SDK installation. You will need to run the SDK Manager.exe to install the latest tools. Note: ADB and Fastboot have been moved from the "tools" folder to "platform-tools".
Make sure your phone is in debugging mode by going into the Developer Options and choosing "Android debugging."
Find your SDK installation and make sure you are under "platform-tools" folder. You can ctrl-shift-right click on that folder to open a command prompt at that folder location. Saves you time.
Type in the command prompt:
Code:
adb devices
Your device should be listed and probably says Offline. This is normal. Take a look at your phone, you should get a prompt on your phone asking you if you trust the device that is trying to connect to it (this should be your computer). Allow it.
Type in the command prompt:
Code:
adb devices
This time, your device should be listed with the word "device" instead of offline.
To restart the daemon, type the following separately:
Code:
adb kill-server
adb start-server
This is the best I can do for everyone and it solved my problems with no further issues. I am not an expert and this is the only solution that has worked for me.
Thanks, this worked for me.
I did this in Windows 7 SP1 no problem. All I had to so was get the latest Android SDK and replace all the adb/fastboot files I already had and it worked no problems.
If you get permission denied when doing the last "adb shell" command, get adbd insecure from the forums here and run debugging mode insecurely from there.
Sent from my One X using xda app-developers app
Desertman123 said:
If you get permission denied when doing the last "adb shell" command, get adbd insecure from the forums here and run debugging mode insecurely from there.
Click to expand...
Click to collapse
I had this problem because SU was only allowing apps in CM10.1 (4.2.1). I found the solution by enabling the Dev Options via multiple clicks on the Build number until dev options was enabled, then changed Root access to Apps adn ADB.
FYI for anyone else that gets lost like I was.
ok so i can s-off now?
yes get some, 9 steps to s0ff
Ponarona said:
ok so i can s-off now?
Click to expand...
Click to collapse
Yes, you can use the HTC One XL link in the S-Off thread with no issues. I made this to help people with Win8 and trying to get their phones to appear properly in their device manager and to list it under adb devices.
If you get device offline, my issue, I was running android 4.2.2 but had an outdated adb. Just update adb if you still have problems
I know this is exceedingly random, but if you run a mac and can't see your device in adb, and in the past you tried sharing your phone internet with your mac via usb try running this:
sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext
./adb kill-server
I need to do that before every adb session.
I'd be amazed someone actually has those conditions, but hey, it might help someone.
Sent from my HTC One X using xda app-developers app

[Completed] Frustrated. ADB Device unauthorized. No solutions work

Hello xda-members,
I've been searching for 4 hours now and every time I try to use ADB along with my device I get the "unauthorized" message and can't use it.
I've been searching for answers all across the internet and tried nearly everything I could find, e.g.:
1. In windows cmd:
Code:
adb kill-server
Code:
abd start-server
2. Unplug phone
3. Reinstall drivers
4. Reboot phone / PC
5. Disable and Enable USB-Debugging-Mode
I read in several threads on other sites, that the adb key is the problem (there's no "authorization"-pop-up appearing on my phone, when connecting it via usb, furthermore I can't revoke debug permissions in developer settings), so I tried also:
1. delete .android. folder on my PC (C://User/me/.android.)
2. Copy the adb_key file to my phone (/data/misc/adb)
None of that worked. None.
I'm really desperate since I need ADB for several important reasons (to me important). I don't know when this problem occured first. When I bought the phone ADB worked fine. I don't know what to do anymore.
Technical information:
- Windows 10 PC
- Latest LG drivers, latest adb version
Phone:
- LG G4 H815 V20C (Marshmallow)
- Rooted, TWRP installed, SuperSU working without problems
So please, if anybody out there has had the same problems help me!!!
Follow_and_Feel said:
Hello xda-members,
I've been searching for 4 hours now and every time I try to use ADB along with my device I get the "unauthorized" message and can't use it.
I've been searching for answers all across the internet and tried nearly everything I could find, e.g.:
1. In windows cmd:
Code:
adb kill-server
Code:
abd start-server
2. Unplug phone
3. Reinstall drivers
4. Reboot phone / PC
5. Disable and Enable USB-Debugging-Mode
I read in several threads on other sites, that the adb key is the problem (there's no "authorization"-pop-up appearing on my phone, when connecting it via usb, furthermore I can't revoke debug permissions in developer settings), so I tried also:
1. delete .android. folder on my PC (C://User/me/.android.)
2. Copy the adb_key file to my phone (/data/misc/adb)
None of that worked. None.
I'm really desperate since I need ADB for several important reasons (to me important). I don't know when this problem occured first. When I bought the phone ADB worked fine. I don't know what to do anymore.
Technical information:
- Windows 10 PC
- Latest LG drivers, latest adb version
Phone:
- LG G4 H815 V20C (Marshmallow)
- Rooted, TWRP installed, SuperSU working without problems
So please, if anybody out there has had the same problems help me!!!
Click to expand...
Click to collapse
Greetings,
Please read the sticky threads for this forum. XDA Assist is for helping NEW members find their way, not a help desk for Senior members who should know where to ask for help.
Thread closed.

Using Android device to run adb and fastboot commands

To make this a short as possible I successfully unlocked my Motorola G7 power using an Android device rather than a PC I need help rooting my G7 power with magisk using my designated Android device rather than a PC
ADB⚡OTG - Android Debug Bridge - Apps on Google Play
⚡ Run ADB commands without a computer [No Need ROOT] ⚡
play.google.com
Thank you I appreciate your reply but I use another application for this purpose bugjaeger premium
@Sativa33
Either in magisk manager from device or you can also get the magisk module from Osm0sis' Odds and Ends- (multiple devices scripts) XDA thread. If you go there https://forum.xda-developers.com/t/...-and-ends-multiple-devices-platforms.2239421/
Scroll down halfway oe maybe 2/3 of fge way and click his "adb and fastboot " magisk module and install via magisk manager. Then use termux terminal and type "su" (enter) for root and place files you wish to install in ter
Termux's directory which it will show you after you tape sy and push enter on the screen in terminal just after you grant it root. Then you use an otg cable and connect two Android devices together throw files in Termux's directory and send fastboot and adb commands whenever. I've used this method on two phones so unlock my bootloader ad well. The only prerequisite being you need another (2nd) Android device that is bporloader unlocked and rooted so you can send commands to other device and an OTG cable which are $3-5 USD online. Sure does come in handy when you need it through. Like years ago when my laptop was stollen!! Life saver FR!!!
After reading it that sounds like a reasonable option. But wouldn't it be easier just to download the bugjaeger premium app on a second Android device. And that's basically all you need and a double ended USB c cord. No need for all this other programs or downloades . It's basically running fast boot commands it's purest form one Android device talking to the other using the same language no need to download packets drivers nothing because you're already in the Android shell talking to another Android

Op7pro not responding to fastboot commands

Hey, im having trouble finding working ways to root my op7pro GM1913 (OOS 11.0.4.1 GM21BA)
Ive been trying this https://www.xda-developers.com/unlock-bootloader-root-oneplus-7-pro/
Currently trying to unlock bootloader. (Step 2)
I can connect via adb but when i go to bootloader/fastboot i lose connection to the phone.
Ive tried regular adb command tools and "TOOL ALL IN ONE" When the phone is on it responds to adb commands but when i need fastboot commands its not working and i can see the device id dissapear from the all in one tool.
I have tried multiple usb ports (2.0 and 3.0) and multiple usb C cords (Op oem + Samsung) Tried removing Windows signature verification and installing oneplus usb drivers, but it gets stuck at "Execute the commands..." (99% or so) When i try again it finds some installation files. When im in bootloader, Windows device manager still shows a generic android phone. Oem unlocking and usb debugging is on, also set default usb configuration to file transfer. No help.
I want to keep Oxygen os, but i want to be rooted and have magisk, preferably TWRP too but im open to other ways.
Windows 10 20H2 if that matters. (Latest update for me)
Oneplus 7pro GM1913 (Eu nordic)
Oxygen os 11.0.4.1 GM21BA
Download a Linux distro and install adb and fastboot like this: https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/
Just download adb and fastboot tools package from Google, extract it,open command prompt inside where you extract it and enter these in terminal:
sudo install adb dmtracedump e2fsdroid etc1tool fastboot hprof-conv make_f2fs mke2fs mke2fs.conf sload_f2fs sqlite3 /usr/local/bin
sudo mkdir -p /usr/local/lib64
sudo install lib64/libc++.so /usr/local/lib64
Then adb --version (enter) fastboot --version (enter) like Nathan says in guide. Super easy and I guarantee you if you go this route you won't have any hiccups. Sounds like stupid windblows driver issues or outdated adb/fastboot tools. One of the two. Are you flipping on dev options and check marking little box that pops up on your phone to allow it to communicate with PC? A simple : adb devices (enter) should make it appear on phone screen. You don't even have to install Linux, you can boot it off a live USB. Takes about one minute to make one. If you make one you can boot the live USB , download adb and fastboot, and install as Nathan's guide says then reboot when you are done and your back in windblows. IDK why anyone wouldn't want Linux installed though. Best decision I ever made was switching from windows to Linux about 9 years ago. It really makes anything you do to your devices MUCH easier to do!! This may sound stupid but have you rebooted your PC? Because you will definitely need to , probably more than once on windblows to get it to work.
Thank you for the reply. No stupid questions, yes i tried rebooting pc/phone. Ill try your way and report in a couple days.
Solution is simple. From Android 11 on, OnePlus (and Android phones in general) uses the universal drivers, you just need to install them in Windows in order to use fastboot commands. See my answer in this post.
There are a few things you can try if your OP7 Pro is not responding to fastboot commands:
1. Make sure you have the latest drivers installed for your phone.
2. Try using a different USB cable.
3. If you're using Windows, try running the fastboot commands from a command prompt with administrator privileges.
4. Try booting your phone into recovery mode and running the fastboot commands.

Categories

Resources