Originally when I tried rooting my Kindle Fire HD on 7.2.3, ADB Devices wasn't showing my Kindle Fire HD device. So, a solution to my problem was installing the Google USB Driver from my Android SDK Manager. After the installation, I was able to open up CMD (Administrator) and see if ADB Devices would show my Kindle Fire HD. Bingo! It appeared!
Before:
{
"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"
}
After:
-
I'll probably be asking what method I used, and I was using this thread:
http://forum.xda-developers.com/showthread.php?t=2049288
My computer is:
WINDOWS 7 X64
--
Proof of my root:
ADB Server Out of Date
Great post. I If updating the driver does not do the trick, update the ADB daemons. Here are the latest versions:
https://dl.dropbox.com/u/54456659/ADB%20Update.zip
if updating adb doesn't work...
prokennexusa said:
Great post. I If updating the driver does not do the trick, update the ADB daemons. Here are the latest versions:
https://dl.dropbox.com/u/54456659/ADB%20Update.zip
Click to expand...
Click to collapse
And if updating ADB daemons doesn't work try this -> (this is the problem I had)
I was also having trouble getting adb to see the device, even though Composite ADB Interface was there in the Device Manager. After much searching, I found that I needed to put 0x1949 in C:\Users\<my name>\.android\adb_usb.ini. Neither the file nor the directory existed on my system, so I created them both and put that number on a line by itself, saved the file, unplugged/replugged the Fire, and it worked!
found here: http://androidforums.com/kindle-fir...6683-root-kindle-fire-hd-7-a.html#post5363515
ADB Communication Issues
bbanghyung said:
And if updating ADB daemons doesn't work try this -> (this is the problem I had)
I was also having trouble getting adb to see the device, even though Composite ADB Interface was there in the Device Manager. After much searching, I found that I needed to put 0x1949 in C:\Users\<my name>\.android\adb_usb.ini. Neither the file nor the directory existed on my system, so I created them both and put that number on a line by itself, saved the file, unplugged/replugged the Fire, and it worked!
found here: http://androidforums.com/kindle-fir...6683-root-kindle-fire-hd-7-a.html#post5363515
Click to expand...
Click to collapse
bbanghyung,
Great work and informative, thank you.
I love this community, we work together
for everyone's benefit. Keep up the great
work.
Related
So for the first time I've set up my ADB since I will getting a MT3G tomorrow. Environment variables (PATH) set correctly, etc.
When I type adb shell in recovery model, it says *daemon not running. starting it now, daemon started successfully, error: device not found*
"Android Compsite ADB Interface" shows up in my USB devices. So what's the problem.
Then when I load up "emulator -data c:\", it starts up and gives me this error. msvcrt.dll? I've dealt with that .dll file before for other apps and it is in my system32 folder.
So what's going on here.
{
"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"
}
try reinstalling the usb driver.
mine identifies as HTC Dream Composite ADB Interface.
did you install the usb driver that comes in the SDK?
what if you navigate to the location you have the sdk installed? does it work then? maybe the path is not set up as correct as you think? (i had this problem when trying to do fastboot. everything else worked fine except for fastboot. to get that working i had to navigate to the sdk directory.)
I sure did, and it reads exactly that.
Even adb devices doesn't bring a device up. Or adb remount.
Other thing is under Hard Drives Tree, the HTC Android USB Phone Device has a Microsoft driver. I tried to install drivers from the android/usb_driver/ and nothing. Do I have to do this in the Home Screen for the first time so it brings up the permission screen where I click on "Allow Always" for root? Cause I'm not getting that there, so I rebooted into recovery....nothing there as well.
i did have an issue recently where i couldn't get the usb driver to change over.
what i had to do to get it to change was disable and then re-enable usb debugging while the phone was connected to the computer.
it triggers a hardware change in windows and this allowed me to reinstall the correct driver.
uninstalling the current drivers might also help.
I've tried both things.
Same issue.
What Windows Services need to be enabled in order to get ADB to work? I did some tweaking of the services.msc for XP. I think that might be the reason adb shell isn't working.
Same problem I have:
I have TWO rooted G1s, Cyanogen 4.0.4 modified devices with identical Software releases.
The one (rooted by the Golcard Method) is recognized by ADB - the other one (rooted by the One Click Method) is not.
Troubled !
Oh Sorry -this is a Sapphire forum ... I apologize
Hi Folks,
I am running Mac OS X 10.8.2 and I have ran into the following issues. I am trying to root a friend's Nexus 4 that's on 4.2.2, unlocked bootloader and USB debugging enabled/on.
I can easily root this on my Windows desktop but I thought I'd try out the Mac. Do note that I am not getting the "Allow USB Debugging" message that pops up on the phone when you connect it to a computer normally and you select Allow for the respective RSA key. The one that shows up after 4.2.2 is updated from 4.2.1.
I am not getting the above prompt when hooking up the phone to my Mac. *PS I removed the name of my MBP pro and the user name.
Okay so here are the two issues/scenarios:
1) I downloaded the latest ADB and Fastboot Mac OS X 64 bit files from the ADB dev tools website, etc. The files are "adb" and "fastboot"
When I type "./adb devices" since the "./" command is for Mac on the terminal, I get the following message and it does not show up any device listed.
{
"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"
}
Then when I type "./adb reboot-bootloader", I get the following:
__________________________________________________________________________________________________________
2) When I use an older adb and fastboot files from last year: "./adb_Mac" , "./fastboot_Mac" and "ADB-Install-Mac.sh", I get the following:
When I type in the adb devices command and the adb reboot-bootloader command:
The serial # shows up this time (Again I have crossed out half of it lol)
When typing in the reboot-bootloader command:
Now to my knowledge, I know that I am getting the device offline mode based on using the old ADB and Fastboot files. So the way to fix it, is to download the updated files but it doesn't result in anything at all.
With the updated ADB and fastboot files, and by booting into fastboot mode manually and then typing in ".fastboot devices", I get the Error Could Not Get Pipe Properties error in a loop.
Would appreciate the help folks!
T.I.A
Try this command
adb kill server
adb start server
scream4cheese said:
Try this command
adb kill server
adb start server
Click to expand...
Click to collapse
Beauty! I didn't know that it has to be done for the same in OS X. Query, does this have to be done every time or?
Hi!
Whre can I find the Android ID for my S5 ? Need it for Racoon (updates without playstore installed). Tried device ID app but it shows nothing
michael-oc said:
Hi!
Whre can I find the Android ID for my S5 ? Need it for Racoon (updates without playstore installed). Tried device ID app but it shows nothing
Click to expand...
Click to collapse
What ID do you mean? (Samsung) serialnumber or IMEI?
In an ADB shell:
settings get secure_id
russ18uk said:
In an ADB shell:
settings get secure_id
Click to expand...
Click to collapse
Not working for me. Settings not found error.
michael-oc said:
Not working for me. Settings not found error.
Click to expand...
Click to collapse
Sorry, my bad.
settings get secure android_id
russ18uk said:
Sorry, my bad.
settings get secure android_id
Click to expand...
Click to collapse
Also not working. I have to do this in recovery right? Tried it in downloader mode but got an error "device not found". In windows device manager it´s labeled as modem?!
michael-oc said:
Also not working. I have to do this in recovery right? Tried it in downloader mode but got an error "device not found". In windows device manager it´s labeled as modem?!
Click to expand...
Click to collapse
Boot up normally. Make sure you have enabled debugging. If you haven't, follow the guide here.
After that download ADB:
USB drivers required;
ADB interface.
Install the drivers and ADB. You can find ADB in your Start Menu or you can open CMD and cd to c:\adb
When you connect your phone to the computer in your CMD window type adb shell. You may get a security prompt on your phone to allow or deny. Tap on allow or similar.
Retype adb shell if needed and you should see:
{
"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"
}
If good type "settings get secure android_id".
Ask if you get stuck anywhere.
Thanks for all your help! It´s working now. This suggested adb drivers are older than mine and working. Strange
I'm 63 years old & could do with some help - trying to flash my Moto G4 but no luck
Hello folks.
I apologise in advance. I thought something was a good idea, and I said to myself I would give it a try and I won't give up, but I have been at this for about 5 hours now and no progress.
I have a Moto G4 which my wife gave about a year ago. I don't like stock Android and want to install Lineage OS onto it. I understand that first I need to:
1. Unlock my bootloader (done)
2. Install ADB Driver Installer onto my Dell (done)
3. Install Minimal ADB and Fastboot onto my Dell (done)
4. Plug my G4 into my Dell using the correct cable. It seems to work as the ADP Driver Installer / APK Installer recognises it as per the image below
/https://imgur.com/a/NBfrIcZ
5. Open up the command promt in the Minimal ADB and Fastboot folder, type adb devices - the device is recognised
6. Here is where the problems start!
(a) At this stage, as soon as I type adb reboot bootloader, the G4 reboots but as it does so it disappears from the ADB Diver Installer / APK Installer
(b) Soon after when I type fastboot flash recovery twrp.img then nothing is found, no files or directory or anything. I don't understand what I am doing wrong and am very stuck sadly
{
"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"
}
Would really appreciate some help!
Great, my pictures don't work. I don't understand why. But basically when I write fastboot flash recovery twrp.img (it is in the same folder as Minimal ADB and Fastboot), it says not found to a bunch of things and no such file or directory.
George425 said:
Great, my pictures don't work. I don't understand why. But basically when I write fastboot flash recovery twrp.img (it is in the same folder as Minimal ADB and Fastboot), it says not found to a bunch of things and no such file or directory.
Click to expand...
Click to collapse
Ask your question here in moto g4 forum you will gets answers correctly ,because that's where you should have asked, buts it OK here is the link https://forum.xda-developers.com/mo...hread-question-noob-friendly-t3526598/page175
And upload the photos in Google drive and turn on the link sharing feature and post the link there there are many people there to help you out. Don't worry, everything will be fine.
Thank you Dhanush-raj I will do that now.
TL;DR: Noob needs to stock flash a device that won't boot into OS.
Here's how the recovery looks (without and interaction):
{
"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"
}
Boot loader:
Splash screen:
I have acquired a YB1-X90F that just shows the orange Lenovo splash screen and or a blank and does nothing.
I'm a novice when it comes to flashing, etc.
I can access Fast Boot and Recovery Mode.
What should I be trying?
I've got several links I'm going through but I'm rather confused. For example, I've been trying to set up ADB, Fastboot and Drivers. Struggling with drivers.
My first setup was with platform-tools_r32.0.0-windows.zip but I'd just have a missing 'Cherry Trail Tablet' driver in Device Manager.
I then tried 15 seconds ADB Installer v1.4.3 but still no driver. 'Cherry Trail Tablet' in Device Manager.
I also tried ADBDriverinstaller.exe and IntelAndroidDrvSetup1.10.0.exe.
I looked through this thread, but no joy:
Missing USB driver "Cherry Trail Tablet" while on bootloader
Hello everyone ! First post here. :) I've bought yesterday this amazing machine, and bought the Android version. But I wished to directly install a Windows 10 version to replace Android, but I didn't thought it would be this... complicated. >.
forum.xda-developers.com
In the end, I had to manually add 'Android ADB Interface' as mentioned in the 15 seconds ADB Installer v1.4.3 page under Notes:
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
I seem to have activity in cmd prompt now:
C:\WINDOWS\system32>fastboot devices
YETIDD2E4EC8 fastboot
Click to expand...
Click to collapse
This guide/links seem to assume your device is already working?
Yoga Book YB1-X90F (Android) - How to Flash back to Stock Rom 6.0.1 /downgrade
hello all i spent last few hours looking for solution to how to flash Stock Rom to my YB1-X90F and i found steps here and there and finally i got it. so i gathered all the steps in one thread to help whoever want to flush back to stock or...
forum.xda-developers.com
Where do I go from here?
How do I unlock the bootloader without access to the OS on the device to 'Enable USB debugging' and 'OEM Unlock'?
Solved. I ran 'flash_update_from_user.json
Just waiting for the battery to charge to 30% to hopefully enable the Halo Keyboard.
Here are the files needed in case other links void in the future: https://drive.google.com/drive/folders/1gD9FyA03GbLZ7ZcjkyMDlhVPs4_em2rY?usp=sharing