Hello,
At the beggining I had SDK Tools Only and everything was ok, after typing adb logcat I got logs. Then I installed ADT Bundle and run eclipse -> DDMS and in logcat tab I got logs. Then I installed a couple of programs to make screencasts. The next day I run eclipse -> DDMS and I got this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
[2013-05-18 08:46:16 - ddms] ADB rejected shell command (getprop): closed
[2013-05-18 08:46:29 - ddms] ADB rejected shell command (logcat -v long): closed
[2013-05-18 08:46:29 - Unexpected error while launching logcat. Try reselecting the device.] closed
com.android.ddmlib.AdbCommandRejectedException: closed
at com.android.ddmlib.AdbHelper.executeRemoteCommand(AdbHelper.java:381)
at com.android.ddmlib.Device.executeShellCommand(Device.java:462)
at com.android.ddmuilib.logcat.LogCatReceiver$1.run(LogCatReceiver.java:110)
at java.lang.Thread.run(Unknown Source)
When I run adb logcat from console I got this message: waiting for device.
adb devices detect my phone
I have windows vista home premium
android 4.1.2
What I did:
- uninstalled SDK Tools Only
- reset adb / unplug and plugin my device
- I tried this one: adb -s emulator-5037 logcat but still waiting for device
- adt bundle - sdk manager -
- windows task manager - there is just one adb.exe running
but still I get waiting for device and the exception in eclipse.
thx in advance
c'mon guys help me out with this
Related
When I connect my Note 2, it's not seen by the PC. When I list the devices, nothing's there. I tried adding vendor and model ids in udev (I'm on Linux), but it didn't help. Anyone knows how to fix this?
Update your adb.
You need 1.0.32
First check if your version is older (e.g. 1.0.31):
Code:
$ adb version
Android Debug Bridge version 1.0.32
Then upgrade, following #3 from this guide: Ubuntu 14.04 - Install Android Tools
Tried on a Windows PC and I get the same result, adb version 1.0.32. However, I was able to flash TWRP before, but now it doesn't see the device at all. I'm on xiaomi.eu dev 5.9.24.
Edit: Just realized that this happens on Windows:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Apparently, the drivers are not installed, however I DID install adb drivers, but whenever I try to install Xiaomi USB drivers (manual installation through Device Manager), Windows say they didn't find any compatible drivers for my device. But they ARE there in the folder specified. This is driving me crazy.
Edit edit: found solution for adb drivers problem here, however, I still cannot install drivers for "Redmi".
Anyway, adb works now on this Windows machine, the question is whether I'll be able to achieve this on my Linux PC, too.
I.nfraR.ed said:
Update your adb.
You need 1.0.32
First check if your version is older (e.g. 1.0.31):
Code:
$ adb version
Android Debug Bridge version 1.0.32
Then upgrade, following #3 from this guide: Ubuntu 14.04 - Install Android Tools
Click to expand...
Click to collapse
Thanks a lot! Worked perfectly.
For clarity, my OS is Lubuntu 17.04 (Zesty)
Due to my phone's apparent obscurity, I'm unable to find any resources pertaining to it, so I've been trying to be as 'manual' as I can by unlocking it through fastboot commands. I really want to unlock my phone's bootloader in order to root it and install a custom recovery and then custom ROM.
However, I've run into an issue. Whenever I run 'fastboot oem unlock', as well as most other fastboot commands, I get stuck at an ellipsis('...') and it stays there until I shut off my phone. Ctrl+C and Ctrl+Z can't close it. So far, I've successfully installed ADB and fastboot tools.
For troubleshooting, I have:
- double checked if my device is listed whenever I run either the 'adb devices' command or the 'fastboot devices' command and it is listed for both
- I've set up my udev rules and adb_usb.ini
- changed usb ports/cables
- rebooted my phone and PC many times
- looked for official and unofficial unlocking instructions (to no avail)
If there is anyway you can help me or guide me to a resource which may be of use to me, please do so. It's been a real struggle having such an obscure phone, but it's what I can afford at the moment.
tl;dr: 'fastboot oem unlock' not working. stuck at ellipsis('...'). device is listed under 'adb devices' and 'fastboot devices' command.
Unfortunately, I can't post outside links yet, so please PM me for a link to my dropbox folder containing my .rules, adb_usb.ini, and CPU-Z information.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bolded for skimmers.
Hello guys ,
Thanks in advance for any help that I may receive.
Im trying to compile a kernel for my HTC One M8, based on the LineageOS-Kernel (from Github; android_kernel_htc_msm8974), with binfmt_misc support.
My approach:
1. Getting the Kernel Source with the git clone command and downloading+unzip the ndk toolset (r14b)
2. Moving both Extracted "Source Code" and "NDK Folders" to "Testing" folder
3. cd ~/Testing, then: export CROSS_COMPILE=/home/canberk/Testing/ndk/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/arm-linux-androideabi-
4. cd htc ( folder with kernel source)
5. make clean && make mrproper
6. export ARCH=arm
7. make msm8974_defconfig
8. make gconfig, in order to configure the kernel with a graphical menu
9. make –j4
But after starting the process, im getting this error.... (Error: arch/arm/boot/dts/msm8974-fluid.dtsi:721.2-3 label or path, 'dsi_tosh_720_vid', not found)
I have no idea, what that means or did i just forget a command ? I need your help :crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
UPDATE 16.01.2019:
By installing the device-tree-compiler (available in the ubuntu repos), my first problem was solved.
I did compile my kernel successfully (without any errors), but now i cant boot it, by typing : fastboot boot zImage.
I have no idea what to do now. My phone just simply restarts, but still uses the default kernel.
Hi all, as the title says, I'm unable to install twrp recovery.
Before proceeding on Android:
- USB debugging enabled
- Bootloader unlocked
- All screen security disabled
Befor proceeding on Windows:
- ADB tools & fastboot downloaded
- Z5C drivers downloaded
- General Google driver downloaded
- TWRP recovery downloaded
First connection pc the phone shows up at portable devices as Xperia Z5 Compact.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Opened command prompt -> ADB devices
command prompt -> ADB reboot bootloader
Phone goes into black screen + blue led
Moves from "portable devices" to "other devices" and shows up as S1Boot Fastboot
command prompt -> ADB reboot bootloader
fastboot flash recovery recovery.img -> stuck into "waiting for device"
I tried installing drivers via different methods with no luck.
Any help is much appreciated
PD: Can't post links to pics
Disconnect the device and shut it down.
Wait a few seconds.
Press volume up and hold it and connect usb cable.
Flash recovery.
Would be nice if you give a feedback!
Google has made it easy to use ADB in Windows these days, but the ADB commands can only be used in a directory. This a Powershell script for Windows that will download the latest ADB from the Official repositories and install it System-wide or User-Wide, this script will also install latest Google drivers also from from the Official repositories. This script will help to install ADB and the drivers in an easy way. Most ADB installers come in exe format where you cannot see exactly what they do exactly. So I decided to write the whole thing as a Windows Poweshell script.
On my github page you can download the script and you can also find an explanation how to use the script. The big difference to others is that ADB & Fastboot drivers are updated in real time when this tool is used. For the drivers i have to update a link I'll do my best when a new driver comes out to update the link as soon as possible.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Notes:
System-wide: ADB and Fastboot are installed to HOMEDRIVE\ADB directory, and added system-wide path.
HOMEDRIVE=C:\ so in case of the system-wide install option ADB will copy over to C:\ADB
Current user only: ADB and Fastboot are installed to UserProfile\ADB directory, and added path for current user. UserProfile=%SystemDrive%\Users{username} so in case of the Userwide-wide install option ADB will copy over to C:\Users\username\ADB
CMD or Powershell can use ADB and Fastboot from any directory.
If you are using this tool and you having problems leave a comment and I will try to help you
ķANKAN