Whenever I try running a command shell application i get this error:
"CMD cannot start. There are too many console windows open. Please close some console applications and try again."
I'm certain that no other console apps are running. This error was sporadic in WM2003SE, but in WM2005 I never had any success running the command shell.
Any ideas?
Thanks.
Related
I recently set up Ubuntu Karmic on my laptop's second hard drive, and I finished setting up Eclipse and the Android SDK yesterday. I set up ADB to work directly from the terminal without changing to the SDK Tools directory, and it works... kind of. I can get some ADB commands working, but most others won't. The only things that really work are "adb help" and "adb devices" at the moment. "adb install", "adb push" / "adb pull", and other similar commands seem to register, but then nothing happens after that- the terminal freezes, and inputting keys shows other characters. ]]^A and stuff like that. Can anyone help?
Ubuntu 9.10x64 adb works with sudo
$ sudo adb push...
I usually make sure the first adb command I use is sudo'd so it starts the daemon as root.
adb help - does not send any data to your droid. It's internal
adb device - shows which devices are on the USB bus.
The other adb command need to talk to the devices and depending on how your udev protections, device protections, and your personal group memberships are... it may not work.
sudo works for me always.
Ehud
I've been trying to root my new NOOK TABLET via T-R-I-C-K's method on the forum and I can do everything except get the Macbook Pro to recognize my Nook in ADB mode. I downloaded the Android SDK and I even got an error message saying in the Manager Log stating "ADB SERVER FAILED". Everytime I type in ./go.ph to run script log in T-R-I-C-K's instructions the TERMINAL LOG on my computer states:
Error: did not find a device on USB. Is USB debugging enabled? If so try again. adb seems to need a few attempts to get going. Also, don't use a USB hub!\n
dyld: Symbol not found: ___stack_chk_guard
Referenced from: /Users/IcePick/Desktop/nooktablet-mac-root-0.6/./adb
Expected in: /usr/lib/libSystem.B.dylib
./go.sh: line 67: 919 Trace/BPT trap ./adb kill-server
Click to expand...
Click to collapse
I'm running Mac OS 10.4.11 on a previous generation Macbook Pro...any suggestions? Thanks for any help, I'm trying to get this thing rooted!
After installing ADP and fastbook, after I type a command, the dos window pops up and then disappears. When I open up the task manager, it is running in the background. Could this be a problem with Windows 8?
cnh56 said:
After installing ADP and fastbook, after I type a command, the dos window pops up and then disappears. When I open up the task manager, it is running in the background. Could this be a problem with Windows 8?
Click to expand...
Click to collapse
Its ADB (Android Debug Bridge) not ADP. I'll let it slide on fastbook because you got it right in the title.
Where are you typing these commands at, the Windows Run line or a cmd shell? Sounds like you might be running them from the run line. Nothing should pop-up because you should already be in the shell before you type your commands. You need to run "cmd" then from that shell type your commands. From the shell type "adb devices" to see if your PC can see your device over adb. If successful, the output will be your device SN. From the shell type "exit" to return to Windows (if run maximized) or to close the window (if run floating-whatever that's called, normal I think).
Hello, I hope that this topic can be opened here, if not please move it or let me know and I will delete it.
In adb I am getting the error "failed to check server version: protocol fault (couldn't read status): No error" and I cannot see my device when I use the command "adb devices". Moreover, it seems like my phone is not letting me authorize my laptop for USB debugging despite trying different options to getting it to work. I have tried different trouble shooting methods that I have found online, but nothing has worked so far. If anyone has any ideas, it would be greatly appreciated.
I am using a POCO F2 Pro that has had its bootloader unlocked and I am running Xiaomi.eu version 12.0.4 (stable) and using a Windows 10 machine to connect with my phone. I did not have much problems with the flashing off TWRP, using ADB commands, or flashing the ROM when I did all of these things last month.
Now, however, I have been having some problems. I believe it started when I tries to update the System FW a few days ago in the phone instead of flashing it manually. Because it was the stable version, and because the option existed in my system settings, I thought that I would be able to update it without going through those steps. The update downloaded and I got the correct file, but when I hit install, I did not get the new FW, despite the phone rebooting. I've been having problems with adb since this time, I believe.
Try restarting adb server:
Code:
adb -d kill-server
adb -d start-server
Try re-enabling USB debug stuff in Dev Options too.
Saratoga79 said:
Try restarting adb server:
Code:
adb -d kill-server
adb -d start-server
Try re-enabling USB debug stuff in Dev Options too.
Click to expand...
Click to collapse
Hello, thanks for your reply. I tried that yesterday, but I gave it another try today. This was the error that I received when I ran the command in Powershell:
Program 'adb' failed to run: No application is associated with the specified file for this operationAt line:1 char:1
+ adb -d kill-server
+ ~~~~~~~~~~~~~~~~~~.
At line:1 char:1
+ adb -d kill-server
+ ~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: ) [], ApplicationFailedException
+ FullyQualifiedErrorId : NativeCommandFailed
When I ran the command in Command Prompt, I got the error "failed to read response from server".
Trying to start the server also lead to an error "protocol fault (couldn't read status): No error
---------
Part of my issues may be coming from the fact that I no longer get the authorize USB debugging on my phone, even after I have revoked the authorizations. I've tried different ports, different USB cables, and even factory resetting my phone, to no luck.
Try using the latest platform tools from Google.
batuken said:
Try using the latest platform tools from Google.
Click to expand...
Click to collapse
From what I know, I am using the latest SDK platform tools. I initially downloaded from that site either in late July or early August, and yesterday I deleted the old files and re-installed them from the website. Is there an additional step that I might have missed in removing the old files from my computer?
Additionally, the .android folder in my user profile is now empty (no adb_key file(s) inside).
Background:
On a Nokia G10 I have been using ADB to uninstall unwanted apps to make the phone child-safe, without root being required. I followed steps here using the command:
Code:
.\adb shell pm uninstall -k --user 0 <package_name>
and can reinstall any app using:
Code:
.\adb shell pm install-existing <package_name>
This has been very successful and I have been able to uninstall and reinstall many apps as needed. The final step I took was uninstalling the settings app (com.android.settings) to prevent the user from just enabling the play store and downloading everything again. Whenever I needed to update/change anything, I would connect via ADB and reinstall the settings app and do what I needed to do.
This has been working well for months, no problems, a very elegant and airtight solution.
Problem:
Today I restarted the phone and it got stuck in a loop at the lock screen. Not a boot loop.
It turns on, and loads the lock screen up, then there's about half a second before it freezes, the lock screen crashes (goes black for a second) and the reloads the lock screen.
During that half second I can interact with the screen normally (e.g. swipe down the notifications/settings menu at the top, or open the power options menu) but then it crashes and reloads the lock screen.
Aim:
I need to reinstall com.android.settings . I know this will fix the loop because I encountered this error while setting up the system earlier. However, I was already connected via ADB at that time and could just run the command to reinstall the settings app. This stopped it crashing, it loaded normally and I could login immediately.
But now I cannot connect via ADB for some reason. Running these commands gives the following errors:
Code:
.\adb shell pm install-existing com.android.settings adb.exe: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
.\adb devices
List of devices attached
PT996******************* unauthorized
I have tried the following with no success:
1)
Code:
adb kill-server
adb start-server
2) Starting in safe mode gives the same problem
3) Ideas listed here: https://stackoverflow.com/questions/23081263/adb-android-device-unauthorized/25546300#25546300
I don't get a new prompt to allow access.
4) Trying to start in FASTBOOT mode... I'm not sure I'm doing it right. Holding down the power and -vol key the screen displays "FASTBOOT mode..." but does not progress to a menu screen.
What I need:
A way to install com.android.settings, or, a way to get ADB access.
Any suggestions welcome
Thanks
Some progress trying FASTBOOT:
Using this guide: https://forum.xda-developers.com/t/how-to-enter-recovery-mode-on-nokia-g10-g20.4353903/
I have been able to boot into recovery mode.
Does anyone know how I can use the option "Apply update from ADB" to issue ADB commands like this?
Code:
.\adb shell pm install-existing com.android.settings
According to this thread: https://android.stackexchange.com/questions/94126/adb-shell-in-recovery-mode-errorclosed
adb shell is inaccessible with stock recovery.
Using FASTBOOT in the Windows powershell terminal, can I issue any similar command to install an existing package?
or, can I use adb sideload to reinstall com.android.settings?
as adb is unauthorized you simply have no adb access anymore. if you are using the same PC then RSA key is lost (otherwise check the previously known working PC and copy .android directory to current PC)
fastboot is unrelated to adb and of no use at all.