I am getting quite frustrated after spending the last 6-7 hours combing the net for answers only to have a bunch of failed attempts, please help.
I am trying to root my Xoom which is running 3.2.1 and I installed the SDK manager (C:\android-sdk-windows) and Java JDK (C:\Program Files\Java\jdk1.7.0_02) but everytime I open SDK, the cmd window closes just as fast as it opens. I have completely reinstalled everything multiple times, trying multiple locations for SDK, and different values for the environmental variables (run - sysdm.cpl - advanced - environmental variables - system variables - PATH).
I had it working earlier today and installed adb but could not find the device when I ran cmd - "adb reboot bootloader". So I tried a few other methods and it crashed.
What am I doing wrong?
I am trying to root it using this http://forum.xda-developers.com/showthread.php?p=17135571&posted=1#post17135571
Is there a better way that won't run the risk of killing my wifi like I say on another post?
Thanks,
-SrgCano
*****To all newebies(as quite a few new people are at this forum because they got their first device! (TFP)) any anyone who wants to learn, let’s get educated about our devices!*****
ADB (Android Debug Bridge) is an extremely useful tool that WILL help you in all of your customizing needs! You may see the need to use ADB commands to help root your device, change ROMS, or send your device a fix. Without the knowledge here, you could easily be left in the dark.
ADB is a necessity for developers and general consumers alike. Knowing this tool is a great advantage to you to help your device at the best quality possible.
Installation
Download Google SDK
Choose the correct operating system and install!
The installation REQUIRES Java JDK which can be downloaded from Here
If during installation it asks for JDK (and you have installed it) Press the back button and next again, sometimes that will fix the error.
**Note** The SDK installs to C:\Program Files (x86)\Android\android-sdk standard, chose any directory for you
Start the SDK and immediately, you will notice a few checkboxes. For the standard user, just make sure Android SDK Platform-tools (under Tools) and Google USB Driver package (under Extras) – the drivers are always good to have, latest ADB drviers.
Click install 2 packages and wait. Once installed go to your installation directory and find the platform-tools folder. This directory is your ADB and will be your lifeline!
**Do you want ADB accessible through any command prompt directory?**
You are in luck. (For Windows 7)
Right click on My Computer > Properties > Advanced System Settings >Advanced (Tab) > Environment Variables > Under System Variables scroll and dbl click on Path
TO THE END of the Variable value line add
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools
Or whatever the directory you installed to + platform-tools
Open CMD and type ADB, if you did it right, you will see proper ADB jargon regardless if you are in the correct directory or not!
Congratulations! ADB is installed!
**Make sure your device is using the latest drivers (that you just downloaded) or other ADB drivers provided by ASUS to access ADB. When connected in Debugging mode, device manager will have: ASUS Android Composite ADB Interface**
ADB Usage
**I will be talking mainly about commands/arguments that the general end-user may use or come across**
**Make sure your tablet is in USB Debugging Mode to be able to connect to ADB (Settings > Applications)**
ADB Devices : This command shows all connected android devices that will respond to an ADB command. It is useful for making sure your device is connected.
ADB Connect [IPORT] : This command will connect to your device over personal WIFI connection if your device is setup for ADB over WIFI (Requires root and NOT recommended)
ADB Push [local_file] [remote_file] : This command will push any local file to the device (only if the device is Read/Writable. Stock /system/ folders are only Readable.
ADB Pull [Remote_file or Directory] [Save file or Directory] : This command take files or an entire directory and save it to your desired location. This command only works when directory is read/Writable.
ADB Shell [command] : This command will perform most UNIX commands on the device. Without a command, you can enter several shell commands before you ‘exit’. Most will not work unless SU is applied (# instead of $). Must be rooted for SU. Only play with these commands if they are known by you or exactly copied from instructions.
ADB Logcat [ > file.txt ] : This command will display (or save per > file.txt) a log of what’s happening on the device. If you are receiving errors, turn on logcat, reproduce error, turn off, and send logcat to the developer.
ADB Install [-r][-s] [local_apk] : This command force installs (or reinstalls –r or –s installs on SD-Card) any APK provided.
ADB Uninstall [-k] [APK_Name] : This command uninstalls any APK Name provided (app.apk) and will even keep cache and other data with the –k tag.
ADB start-server : This command will start the server if the server is off or killed. (Normally server will auto-start when ADB command is used)
ADB kill-server : This command will close ADB server. Useful if ADB server is acting up or not connecting to any devices.
ADB remount : This command will mounts the /system/ partition Read/Writable pending the device is allow to. Stock TFP will NOT.
ADB root : This command will restart ADB with root permissions if the build allows for it. Stock TFP will NOT.
ADB usb : This command will restart ADB on device to use USB connection for ADB communication.
ADB tcpip [port] : This command will restart ADB on device to use TCPIP connection for ADB. Standard port is 5555. Again, this connect not recommended for file transfers.
ADB reboot [recovery/bootloader] : This command will restart your device. If either of the two options are given, the device will boot into that mode (sadly TFP does not support the two options.. yet)
ADB Tips/Tricks
When following ADB instructions, follow them WORD-BY-WORD in the EXACT ORDER GIVEN. If copy and pasting their commands (one line at a time) makes it easier, then do so.
If you have root access, do not mess around in ADB shell unless you know what you are doing
Connecting over IP can be beneficial for you for quick ADB access, but for file transfers, speed is slow and you ALWAYS risk corruption (check the md5!) One bad file and you have boot-loops!
ADB Logcat is an amazing command. If anything is wrong with your device, 9/10 you can see it in logcat. If you can find the exact problem, fixes can happen much easier. USE LOGCAT TO YOUR ADVANTAGE!
ADB reboot can be a quick reboot, sometimes you don’t feel like waiting!
Use the environmental variables! It helps exponentially, and keeps from having multiple instances of ADB running.
When multiple instances of ADB are running (different directories) ADB can get messed up! (ADB not up-to-date restarts, and connect problems). ASUS Sync service has and ADB setup. Turn it off if you are not using it. Try to stick to only ONE instance of ADB
Eventually, we may have root access in our recovery kernel. Then and only then can our devices be truly customizable!
The GUIDE is not finite. Please post anything you feel should be added/corrected to the guide. Please take notice from this, as the understanding of these simple commands could help save your device(s)!
Thanks and 5 star would make me feel good inside too!
Wow... Nice post. Lots of time went into this lol. Thanks can't give the five stars in the app though:-(
Sent from my Transformer Prime TF201 using xda premium
The link in step #1 is whack - I think you want tis? http://developer.android.com/sdk/index.html
Lock-N-Load said:
The link in step #1 is whack - I think you want tis? http://developer.android.com/sdk/index.html
Click to expand...
Click to collapse
hmm thats what was in there, i re-saved and it works now ... maybe xda error
thanks tho!
biggem001 said:
hmm thats what was in there, i re-saved and it works now ... maybe xda error
thanks tho!
Click to expand...
Click to collapse
before you fixed it, it was trying to use this http://http://developer.android.com/sdk/index.html"
note the extra parens at the end and the double http call
i noticed that too, all i did was re-save and it worked. how weird.
Thanks! I've seen a few tutorials on this but this one was by far the easiest to follow and best organized. Short and sweet. Worked on my desktop great, I've never managed to install it right D:
Re posting to give 5 stars. Thanks again OP
Quick question: Is it normal for PTP mode to be required for adb to work? Because as soon as I switch to MTP I can no longer use adb.
cmat1120 said:
Quick question: Is it normal for PTP mode to be required for adb to work? Because as soon as I switch to MTP I can no longer use adb.
Click to expand...
Click to collapse
i can do either at once.. thats weird
GPS, Wifi and BT Testing
Could someone write some basic tutorials on how to verify/test GPS, wifi and BT funtions? For those of us who are new to Android it would helpful in verifying which problems are truly present. Also perhaps show how to find the serial number - for example: some don't know you have to click status - because there are a some erroneous posts out there. There may be users who assume something works or doesn't work, based on limited knowledge and these inaccurate findings only serve to muddy up the works.
There's a lot of animosity about the influx of newbies (and trust me, as a newbie it doesn't feel good). I think the first step is to educate. If some of these troubleshooting steps are laid out, more people can contribute in an intelligent way.
I thought this would be a good thread for the Guides thread, but it is closed and I cannot send PMs.
Thanks - Great Info
One thing you can add for all us amateurs is how to use ADB to install off market apps, stuff like that. Things the non-power user can benefit from. Some simple command line structure would be great.
theandies said:
One thing you can add for all us amateurs is how to use ADB to install off market apps, stuff like that. Things the non-power user can benefit from. Some simple command line structure would be great.
Click to expand...
Click to collapse
i wont add it to the guide, because adb install is pretty self explanatory but this
make sure you can install non-market apps
Code:
adb install app.apk
jonalisa said:
Could someone write some basic tutorials on how to verify/test GPS, wifi and BT funtions? For those of us who are new to Android it would helpful in verifying which problems are truly present. Also perhaps show how to find the serial number - for example: some don't know you have to click status - because there are a some erroneous posts out there. There may be users who assume something works or doesn't work, based on limited knowledge and these inaccurate findings only serve to muddy up the works.
There's a lot of animosity about the influx of newbies (and trust me, as a newbie it doesn't feel good). I think the first step is to educate. If some of these troubleshooting steps are laid out, more people can contribute in an intelligent way.
I thought this would be a good thread for the Guides thread, but it is closed and I cannot send PMs.
Click to expand...
Click to collapse
for GPS, use GPS Test app on the market
for BT and wifi testing, i'll just connect my device via BT or adhoc wifi and do the testing on my PC itself, more accurate and better programs
Excellent howto, thanks
I have trouble connecting to my prime with adb. In the Win7 Device Manager the correct device shows up, no exclamation mark at all, but adb just won't see the Prime.
USB debugging mode is on, no Asus Sync software on the PC. I have no clue why ADB won't see my device.
Now many of us can really shoot ourself in the foot.
by far the best and quickest adb install/setup ever. thanks OP!
neo1738 said:
by far the best and quickest adb install/setup ever. thanks OP!
Click to expand...
Click to collapse
aw shucks!
THANKS!
biggem001 said:
ADB Devices : This command shows all connected android devices that will respond to an ADB command. It is useful for making sure your device is connected.
ADB Connect [IPORT] : This command will connect to your device over personal WIFI connection if your device is setup for ADB over WIFI (Requires root and NOT recommended)
ADB Push [local_file] [remote_file] : This command will push any local file to the device (only if the device is Read/Writable. Stock /system/ folders are only Readable.
ADB Pull [Remote_file or Directory] [Save file or Directory] : This command take files or an entire directory and save it to your desired location. This command only works when directory is read/Writable.
ADB Shell [command] : This command will perform most UNIX commands on the device. Without a command, you can enter several shell commands before you ‘exit’. Most will not work unless SU is applied (# instead of $). Must be rooted for SU. Only play with these commands if they are known by you or exactly copied from instructions.
ADB Logcat [ > file.txt ] : This command will display (or save per > file.txt) a log of what’s happening on the device. If you are receiving errors, turn on logcat, reproduce error, turn off, and send logcat to the developer.
ADB Install [-r][-s] [local_apk] : This command force installs (or reinstalls –r or –s installs on SD-Card) any APK provided.
ADB Uninstall [-k] [APK_Name] : This command uninstalls any APK Name provided (app.apk) and will even keep cache and other data with the –k tag.
Click to expand...
Click to collapse
Just a small suggestion, adb won't accept commands if they are capitalized.
For example "ADB devices" will work perfectly, but "ADB Devices" won't.
So, in order to help the newest of newbies, you might want to put the commands in lowercase in the first post.
All,
Based on some work I was already doing on another app of mine (Juice for Roku), I threw together an basic web server to run on the Nexus Q that can be used to launch packages and intents. You can download it here: http://greggreno.com/test/JuiceReceiver.apk
Steps to install:
Make sure the Nexus Q is recognized by ADB using the ADB DEVICES command. If not, look at the Running Apps thread that shows how to get the USB driver to recognize the Q.
Download the apk file (above)
Use this command to install it: "adb install JuiceReceiver.apk"
Use this command to run it: "adb shell am start -a android.intent.action.MAIN -n com.jigawattlabs.juicereceiver/.MainActivity"
The background web server service SHOULD auto start when the Q boots, so you shouldn't have to manually start the service again, unless it crashes.
When the app launches, it will show the URL of the web server running on the Q. Just go to that link and it will show you the list of currently supported commands. Since I don't have a keyboard or mouse hooked up, I auto close the front end app after 30 seconds to get it out of the way.
The /showimage and /playvideo commands don't seem to work yet because there doesn't seem to be any default player for them. The /playmusic command seems to work (you see an activity playing it), but I can't hear anything.
Please share any suggestions for how I can get the media playback working and any other commands you need. Consider this a buggy alpha release.
works for me
Nice! Didn't try too many things, but was able to launch a couple of the built in apps (settings, downloads).
greno1 said:
Please share any suggestions for how I can get the media playback working and any other commands you need. Consider this a buggy alpha release.
Click to expand...
Click to collapse
How do you uninstall if necessary???
treaklet said:
How do you uninstall if necessary???
Click to expand...
Click to collapse
Code:
adb shell pm uninstall com.jigawattlabs.juicereceiver
Juice Receiver is the way I call the Launcher on my Nexus Q, since I could not assign any key, or combination key to open the launcher I use the browser to do it. Thank you very much, other wise I'll be stucked at the adb commands for that!
Hello
I don't know why but I cannot use ADB since android Q. (Option is of course enabled for USB and also network)
When I connect a computer with adb binary (windows, linux and live linux) the mido detect it because I get a notification in notification bar, but the computer is always unautorised, and I believe there is a problem in displaying the authorisation RSA popup. Never show this popup in android Q !!!
No problem with android 9 I see the autorisation popup and ADB work correctly.
But with android 10, there is no popup for authorisation ! --> the computer is alwas unauthorized .
I try a lot Android Q rom (system-roar-arm64-aonly-floss.img, caos-v224-201029-arm64-avN.img, Havoc-OS-v3.8-20200821-Official-arm64, RROS-Q-8.6.4-20201111-mido-Official) all have the same problem. No popup for ADB authorisation.
I reinstall android 9 (AOSP Extended) and no problem !!!! All is working correctly.
- I always wipe all partitions with mido flash_all or flash_factory, every time I flash a new ROM. (I can do it more because there is no important data for the time)
- On computer I restart and remove adbpub keys also without result.
What can I do more ? Any idea ? (I cannot debug the local debuger without adb )
Thanks
neo_mat said:
Hello
I don't know why but I cannot use ADB since android Q. (Option is of course enabled for USB and also network)
When I connect a computer with adb binary (windows, linux and live linux) the mido detect it because I get a notification in notification bar, but the computer is always unautorised, and I believe there is a problem in displaying the authorisation RSA popup. Never show this popup in android Q !!!
No problem with android 9 I see the autorisation popup and ADB work correctly.
But with android 10, there is no popup for authorisation ! --> the computer is alwas unauthorized .
I try a lot Android Q rom (system-roar-arm64-aonly-floss.img, caos-v224-201029-arm64-avN.img, Havoc-OS-v3.8-20200821-Official-arm64, RROS-Q-8.6.4-20201111-mido-Official) all have the same problem. No popup for ADB authorisation.
I reinstall android 9 (AOSP Extended) and no problem !!!! All is working correctly.
- I always wipe all partitions with mido flash_all or flash_factory, every time I flash a new ROM. (I can do it more because there is no important data for the time)
- On computer I restart and remove adbpub keys also without result.
What can I do more ? Any idea ? (I cannot debug the local debuger without adb )
Thanks
Click to expand...
Click to collapse
Very interesting. I don't remember to have this issue on my previous A10 roms, which were CrDroid and DerpFest. However, just two days ago I switched to official Resurrection Remix and I didn't have the need to grant ADB permission yet. So when I saw your post, I searched for cable and tested ADB, and yes - no popup at all! It might suggest the issue is yet ROM/source-related and you just had a bad luck
The solution I found after searching a while on XDA:
[SOLVED] ADB 'unauthorized', no RSA prompt, and no 'Revoke USB debugging' option
After fighting with this for nearly a month and reading dozens of threads on xda, stack-overflow, etc... I finally figured out this issue, so I'm putting it here in hopes it saves someone else the frustration. The issue presented itself on my...
forum.xda-developers.com
Just tried and worked. No popup, but device is authorized now.
Yes !!! it's working with PC !! thanks
Effectively I think it's a regression in adb source.
Now I must find the public key of the mido itself because I use applications that work in loopback network ADB in order to monitor RUN_IN_BACKGROUD permission and BOOTUP permission.
Hi, I have been trying to “debloat” my Samsung TabA8 and have been trying to do it for some days now. Have done everything according to online directions )Developer Options, debugging, etc.)
My problem:
When opening ADB power shell, I get only the list of some of the installed apps on my laptop with Windows 10, but no apps on the Samsung Tablet. Win10 apps then ask me how I want to open those apps. Some of my choices are: Notepad, Open Office,Google Drive, Internet Explorer.
I have tried all of them. Nothing is working.
How do I get a list of Samsung full apps list on the desktop power shell window??
Just entering for instance: “adb shell pm list packages“ or: “com.samsung.android.apps.spage” is not recognized. I have tried several others also.
I have done all of the online remedies and tried the same thing with another tablet-same problem. Nothing seems to help. There is probably something really easy I am missing...(I hope)
If anybody has any suggestions/advice, I would appreciate it very, very much.
uses platform tools then uses adb from inside them not powershell.
read it here https://developer.android.com/studio/releases/platform-tools
Thank you very much for taking the time to reply. Yes, I have been using the platform tools app. Also, made sure that the drivers are up to date. My problem starts in the platform tools power shell. Samsung apps are not visible there. In the past, before adb + develpoper options ,etc.,connecting the tablet to the laptop via usb, I can see the content and can delete pictures, etc.
So, I'm doing something wrong somewhere with adb.... I would really like to disable and render invisible some of those pesky Samsung apps without rooting. Have rooted my Nexus several years ago. It was great. I just don't want to lose the warranty for now.
Again, thank you. If you have any other suggestions, I will appreciate it very much.
Update...I just realized that the problem is probably with adb and power shell. At opening at the top it reads:
"PS C:\ User's \Ann\ Desktop\adb setup"
Is it not completly set up?
A few days ago,I have unzipped, and agreed to install Fastboot, ADB system-wide and installed Device Drivers. If I right click, it wants me to install again. Have done it a couple of times.... Still, it just isn't working...
Again...thank you!
Oh, one more thing I failed to mention is that this tablet is WiFi only. Does it make any difference? I want to debloat it first before doing it on my Samsung S22 phone.
-Device Driver installation problem (your wins)
-Platform tools (adb,fastboot) run with CMD from inside this folder.
you known howto fix it. wins problem.!
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
You should also replace your adb with the latest binaries by Google.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Download the platform tools for windows zip file. Find out where your current adb.exe file is located. Extract the zip into that location, overwrite the old file(s).