Related
So I'm not a novice ADB user and have used it to root at least 5 or 6 phones. I'm attempting to root my kindle fire right now and running into problems. I built a new PC since the summer and never bothered to reinstall ADB. I just downloaded the Google SDK and from my memory that includes ADB and you can usually get it going from there. I read some tutorials on how to set it up but after following them perfectly I can't get it to even start the ADB server. Anytime I type any ADB commands in it says adb.exe not found or it not being a valid command.
Any quick advice?
Get_Out_and_Push said:
So I'm not a novice ADB user and have used it to root at least 5 or 6 phones. I'm attempting to root my kindle fire right now and running into problems. I built a new PC since the summer and never bothered to reinstall ADB. I just downloaded the Google SDK and from my memory that includes ADB and you can usually get it going from there. I read some tutorials on how to set it up but after following them perfectly I can't get it to even start the ADB server. Anytime I type any ADB commands in it says adb.exe not found or it not being a valid command.
Any quick advice?
Click to expand...
Click to collapse
Download Kindle Fire Utility...
http://forum.xda-developers.com/showthread.php?t=1399889
It has a batch file that will install the necessary ADB drivers and you'll find the fastboot/adb executables in the tools directory.
That's what I thought was weird. I ran the drivers.bat, it says they're all installed and I still can't start the adb server or communicate with it. And the kindle shows up as it's supposed to when the adb drivers are installed under devices.
PS thanks for the quick response.
Get_Out_and_Push said:
That's what I thought was weird. I ran the drivers.bat, it says they're all installed and I still can't start the adb server or communicate with it. And the kindle shows up as it's supposed to when the adb drivers are installed under devices.
PS thanks for the quick response.
Click to expand...
Click to collapse
That's a new one to me. I think the adb server should be able to start even without the device attached. Maybe your original SDK install went wrong and it did something funny to your system? Sorry... I got nothing.
kinfauns said:
That's a new one to me. I think the adb server should be able to start even without the device attached. Maybe your original SDK install went wrong and it did something funny to your system? Sorry... I got nothing.
Click to expand...
Click to collapse
Don't want to sound too simple, but have you changed to the directory that adb.exe is installed in before trying to run it?
Yeah I changed the directory. I got it up and running kind of but now when I try the adb devices command it pops up as "connected devices" with nothing showing under it. The kindle fire utility also shows the adb server as not running always. Odd?
This happened to me its supposed to show up as Android composite adb interface its just a problem in that .android hidden file
Sent from my R800a using Tapatalk
Sorry I dont have my laptop with me and this happened like 2 months ago so my memorys rusty
Sent from my R800a using Tapatalk
---------- Post added at 10:09 PM ---------- Previous post was at 09:53 PM ----------
my adb_usb.ini http://www.box.com/s/e74b32cff87b7c9363fb
http://www.box.com/s/d785bcc0969b7c0999f0 -androidwin.cfg
http://www.box.com/s/da267d41c04c6284f084 -ddms.cfg
http://www.box.com/s/242c14da6a4fa8f2664d -repositories.cfg
to use these click my computer then at the search bar on the top left type in %userprofile% make sure hidden folders are sshown go to the .android folder and put these files in their. if it still doesnt work try superoneclick connect your kindle and go to the advanced tab and click update drivers
if none of this works follow the first half of this tutorial-http://www.youtube.com/watch?v=f409qNgpzSA
jeffbud98 said:
Sorry I dont have my laptop with me and this happened like 2 months ago so my memorys rusty
Sent from my R800a using Tapatalk
---------- Post added at 10:09 PM ---------- Previous post was at 09:53 PM ----------
my adb_usb.ini http://www.box.com/s/e74b32cff87b7c9363fb
http://www.box.com/s/d785bcc0969b7c0999f0 -androidwin.cfg
http://www.box.com/s/da267d41c04c6284f084 -ddms.cfg
http://www.box.com/s/242c14da6a4fa8f2664d -repositories.cfg
to use these click my computer then at the search bar on the top left type in %userprofile% make sure hidden folders are sshown go to the .android folder and put these files in their. if it still doesnt work try superoneclick connect your kindle and go to the advanced tab and click update drivers
if none of this works follow the first half of this tutorial-http://www.youtube.com/watch?v=f409qNgpzSA
Click to expand...
Click to collapse
Thanks I appreciate the help. Once I get home I'll try this and report back on how it works. I'm glad someone else experienced the same problem a d got around it.
The youtube video did it for me. I appreciate the time taken to help point me in the right direction.
This is useful to anybody trying to get ADB going. I can confirm it works.
https://developer.amazon.com/sdk/fire/connect-adb.html
No OTG support as far as I can tell. Or at least, it doesn't power the bus. It did lock when I added a powered hub. That might mean it works, but doesn't supply power.
I'm not getting ADB to recognize the KFHD.
Yes, I have debugging turned on.
Yes, in Device Manager, I see the Kindle Fire as a Composite ADB Interface
Yes, my AndroidSDK is up to date
Yes, I installed the Amazon drivers
Yes, I killed and restarted the adb server
I cannot figure out why it's not talking. It looks as if it should be working. Any ideas?
I had to go to:
C:\Users\myusername\.android and edit the adb_usb.ini and add the following line:
0x1949
Then I killed and restarted adb and it saw it and I was able to install some apks.
Hope this helps!
reverendkjr said:
I'm not getting ADB to recognize the KFHD.
Yes, I have debugging turned on.
Yes, in Device Manager, I see the Kindle Fire as a Composite ADB Interface
Yes, my AndroidSDK is up to date
Yes, I installed the Amazon drivers
Yes, I killed and restarted the adb server
I cannot figure out why it's not talking. It looks as if it should be working. Any ideas?
Click to expand...
Click to collapse
Thread Moved
As the contains no development.
How activate USB Debugging on Kindle Fire HD 7 ? Or this option activated by default ?
androitri said:
How activate USB Debugging on Kindle Fire HD 7 ? Or this option activated by default ?
Click to expand...
Click to collapse
from the notification area click on more , security , ADB on
ADB doesn't see my Kindle HD 7
androitri said:
Awesome, want to try it when I receive my HD 7 this week...
Click to expand...
Click to collapse
I picked up the downloads for the Qmenuroot. Installed the ADB drivers referred to in the OP. In my Win7 system's devices manager, I see the ADB driver for the Kindle Fire HD listed as working correctly. Also, the USB driver is in & working, and I can transfer files to/from the kindle. (though I had to re-install the USB driver after I installed the ADB driver)
The problem now is that when I type "ADB devices", it tells me that there are no devices available. Unplug/plug in the USB connection, wait for a bit, "ADB kill-server", "ADB devices" and still no devices available. I have a CMD prompt open in the correct directory. Tried rebooting the kindle, unplug/plug in the USB connector, all kinds of combinations.
I'd like to root this, in anticipation of a JB build for it, (or even ICS) but without ADB, I don't see how.
Has anyone had an issue like this that they have solved? I haven't mastered ADB in any sense, though I've used it to good effect before to un-brick my TF101.
TIA;
Patrick
---------- Post added at 09:23 AM ---------- Previous post was at 08:55 AM ----------
tansy said:
I had to go to:
C:\Users\myusername\.android and edit the adb_usb.ini and add the following line:
0x1949
Then I killed and restarted adb and it saw it and I was able to install some apks.
Hope this helps!
Click to expand...
Click to collapse
Well, I added the magic line you suggested, and this now works for me. I'm surprised that running "C:\android-sdk\tools\android.bat update adb" (the corrct directory for me) didn't fix this.
Ah well - so many things to learn. Thanks for your guidance.
Pat
tansy said:
I had to go to:
C:\Users\myusername\.android and edit the adb_usb.ini and add the following line:
0x1949
Then I killed and restarted adb and it saw it and I was able to install some apks.
Hope this helps!
Click to expand...
Click to collapse
This didn't do anything for me. Any other ideas?
Driver install problem
dotvezz said:
This didn't do anything for me. Any other ideas?
Click to expand...
Click to collapse
Hi,
I just had the same problem, added the line in the ini file, checked everything. One thing that was a little off was that the driver name was "Android ADB Interface" not "Android Composite ADB Interface". I left the Kindle HD plugged into the computer by mistake when I deleted the driver, and the driver reinstalled itself in about 30 seconds (plug and play). It installed as the "Android Composite ADB Interface". After that it was easy going to root it and get to my google play account.
I hope that helps someone!
Zimblotnik said:
Hi,
I just had the same problem, added the line in the ini file, checked everything. One thing that was a little off was that the driver name was "Android ADB Interface" not "Android Composite ADB Interface". I left the Kindle HD plugged into the computer by mistake when I deleted the driver, and the driver reinstalled itself in about 30 seconds (plug and play). It installed as the "Android Composite ADB Interface". After that it was easy going to root it and get to my google play account.
I hope that helps someone!
Click to expand...
Click to collapse
This worked for me, thank you. ADB can now 'see' my KFHD 7, and I was able to revert a file from backup to get it to boot again.
PMcHargue said:
This worked for me, thank you. ADB can now 'see' my KFHD 7, and I was able to revert a file from backup to get it to boot again.
Click to expand...
Click to collapse
USB hubs cause problems, just sayin'.
I went round and round with this until I decided to plug directly into the PC and avoid the hub. Worked perfectly.
---------- Post added at 05:37 PM ---------- Previous post was at 05:33 PM ----------
If you have tried everything and still no workie, make sure you aren't using a USB hub. ADB wasn't listing it as a device but yet I was able to see it in Device Manager and even transfer files to/from it. Once I eliminated the USB hub, all was well. ADB now sees it.
dburckh said:
This is useful to anybody trying to get ADB going. I can confirm it works.
https://developer.amazon.com/sdk/fire/connect-adb.html
No OTG support as far as I can tell. Or at least, it doesn't power the bus. It did lock when I added a powered hub. That might mean it works, but doesn't supply power.
Click to expand...
Click to collapse
Thank you so much for this, I was fially able to get ADB to recognize my Fire and root it.
reverendkjr said:
I'm not getting ADB to recognize the KFHD.
Yes, I have debugging turned on.
Yes, in Device Manager, I see the Kindle Fire as a Composite ADB Interface
Yes, my AndroidSDK is up to date
Yes, I installed the Amazon drivers
Yes, I killed and restarted the adb server
I cannot figure out why it's not talking. It looks as if it should be working. Any ideas?
Click to expand...
Click to collapse
Mine was doing the same thing
Follow the link that the OP gives(i'll also post it)
Follow the instructions in BOTH the links below. The second link are instructions to get kindle fire add-ons(including usb drivers) for SDK.
https://developer.amazon.com/sdk/fire/connect-adb.html
https://developer.amazon.com/sdk/fire/setup.html#step6
I had the same problem, with adb, not finding my Kindle Fire. I downloaded the current Android SDK und used that ADB without changing anything. Works fine for me I also just copied the adb.exe in the same directory as rootqemu.bat and replaced the old one ( old ~159kb new ~796kb ).
Very helpful
Hello All,
I could use some assistance. I have ADB installed properly and the drivers for the Kindle Fire HD from this thread installed also. My issue is the Kindle Fire HD driver states:
Android Composite ADB Interface
The device cannot start (Code 10).
I am using the driver from 12/3/2012 version 1.2.0.0 and I get this error code if I have the Fire directly connected to the usb port on the pc or through the usb hub. Same issue over and over. Even if I attempt to use other Kindle Fire HD drivers.
Also, I have made the change in the adb_usb.ini file.
Zimblotnik said:
Hi,
I just had the same problem, added the line in the ini file, checked everything. One thing that was a little off was that the driver name was "Android ADB Interface" not "Android Composite ADB Interface". I left the Kindle HD plugged into the computer by mistake when I deleted the driver, and the driver reinstalled itself in about 30 seconds (plug and play). It installed as the "Android Composite ADB Interface". After that it was easy going to root it and get to my google play account.
I hope that helps someone!
Click to expand...
Click to collapse
This ABSOLUTELY helped me! Was bangin' my head against the wall for a WHILE before I this little nugget got me going! THANK YOU!
My issue is fastboot takes commands but says flashing not allowed
Hi, I have no issue connecting to my Kindle Fire using ADB under Ubuntu using a USB cable, no drivers were needed.
However I'm trying to get ADB over WIFI to work, but I get "unable to connect to 192.168.1.234:5555"
Has anyone managed to do ADB over WIfi or is it not implemented on the Kindle Rom? Thanks
Hi, I'm currently struggling to get kfu to work on my KF2, i've got access to the root thanks to Qemu but kfu keeps saying <waiting for device>.
I've read and read and read post after post and I'm pretty sure I'm confusing myself now,
I have the Android SDK software installed including the Kindle Fire drivers, in Windows 7 Device Manager I have "Kindle Fire > Android Composite ADB Interface" (Amazon 1.2 driver) and Portable Devices > Kindle" ( Microsoft 6.7.7600) after modifying "android_winusb.inf" and "adb_usb.ini"
Nothing I do seems to put it into fastboot mode, is there something i'm missing, do I need to copy something to to the kindle??
Thanks for any help in advance
Factory USB Cable
crankyy said:
Hi, I'm currently struggling to get kfu to work on my KF2, i've got access to the root thanks to Qemu but kfu keeps saying <waiting for device>.
I've read and read and read post after post and I'm pretty sure I'm confusing myself now,
I have the Android SDK software installed including the Kindle Fire drivers, in Windows 7 Device Manager I have "Kindle Fire > Android Composite ADB Interface" (Amazon 1.2 driver) and Portable Devices > Kindle" ( Microsoft 6.7.7600) after modifying "android_winusb.inf" and "adb_usb.ini"
Nothing I do seems to put it into fastboot mode, is there something i'm missing, do I need to copy something to to the kindle??
Thanks for any help in advance
Click to expand...
Click to collapse
You need a Factory USB Cable: http://forum.xda-developers.com/showthread.php?t=1392693
There is a link to purchase one.
Is there no other way?
Sent from my GT-I9100 using xda app-developers app
Kindle Fire 2 Fastboot
crankyy said:
Is there no other way?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Maybe. If the Kindle Fire 2 has been rooted and you have the Android SDK Installed.
Try plugging the Kindle Fire 2 to USB:
Code:
adb kill-server
adb start-server
adb devices
adb shell
su
reboot bootloader
Respond with the results.
Well that got it into fastboot but in "Device Manager" it came up as "Otter2-Prod-04" with a yellow exclamation mark.
It couldn't find the correct drivers, what should it be displayed as in device manager?
Sent from my GT-I9100 using xda app-developers app
I've just reslised fbmode will not run ftom shell it comes up with an error
Sent from my GT-I9100 using xda app-developers app
Android Composite ADB Interface
crankyy said:
Well that got it into fastboot but in "Device Manager" it came up as "Otter2-Prod-04" with a yellow exclamation mark.
It couldn't find the correct drivers, what should it be displayed as in device manager?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
If you have installed the correct driver, you will see Android Composite ADB Interface
In the Windows Device Manager. If you need a driver, here: https://dl.dropbox.com/u/54456659/usb_driver.zip is the latest ADB Composite Driver
Offered by Android SDK Community. This driver is Universal to over 1,000
Android Devices, including the Kindle Fire 2. If you do mind me asking
what are you trying to accomplish exactly?
---------- Post added at 03:39 PM ---------- Previous post was at 03:36 PM ----------
crankyy said:
I've just reslised fbmode will not run ftom shell it comes up with an error
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Yes, I see. This is due to two problems:
1) Your ADB Composite Driver is not installed: https://dl.dropbox.com/u/54456659/usb_driver.zip
2) You do not have Root Permissions Installed on the Kindle Fire 2 http://forum.xda-developers.com/showthread.php?t=2069117
I will try the drivers you suggested but my KF2 is definatly rooted
Sent from my GT-I9100 using xda app-developers app
I've made a little progress, I tried the drivers above but the only way I could make them install was to edit the android_winusb.inf but they detected the device as a Samsung Android Phone, I tested with KFU and still no joy, so I uninstalled.
I then decided to follow the Amazon step-by-step guide (https://developer.amazon.com/sdk/fire/connect-adb.html)
This gave me the newest drivers I've had, I then ran:
Code:
adb kill-server
adb start-server
adb devices
adb shell
su
reboot bootloader
My KF2 went into Fastboot and windows installed a driver so I then saw an ADB device in Device Manager.
However KFU still will not run fbmode and I definatly have root access as I have the ability to push files to the root/change permissions in system etc.
crankyy said:
I've made a little progress, I tried the drivers above but the only way I could make them install was to edit the android_winusb.inf but they detected the device as a Samsung Android Phone, I tested with KFU and still no joy, so I uninstalled.
I then decided to follow the Amazon step-by-step guide (https://developer.amazon.com/sdk/fire/connect-adb.html)
This gave me the newest drivers I've had, I then ran:
Code:
adb kill-server
adb start-server
adb devices
adb shell
su
reboot bootloader
My KF2 went into Fastboot and windows installed a driver so I then saw an ADB device in Device Manager.
However KFU still will not run fbmode and I definatly have root access as I have the ability to push files to the root/change permissions in system etc.
Click to expand...
Click to collapse
When you say "KFU“ I hope you do not mean kindle fire utility. That program/tool is for the original kindle fire, you are lucky you have not gotten it to work. It will definitely brick your device should you successfully run it.
Sent from my KFJWI using xda premium
Follow Up
crankyy said:
I've made a little progress, I tried the drivers above but the only way I could make them install was to edit the android_winusb.inf but they detected the device as a Samsung Android Phone, I tested with KFU and still no joy, so I uninstalled.
I then decided to follow the Amazon step-by-step guide (https://developer.amazon.com/sdk/fire/connect-adb.html)
This gave me the newest drivers I've had, I then ran:
Code:
adb kill-server
adb start-server
adb devices
adb shell
su
reboot bootloader
My KF2 went into Fastboot and windows installed a driver so I then saw an ADB device in Device Manager.
However KFU still will not run fbmode and I definatly have root access as I have the ability to push files to the root/change permissions in system etc.
Click to expand...
Click to collapse
crankyy,
This is why I keep asking "what are you trying to accomplish exactly"?
If I know, then we can give you exact step-by-step, thus get you back in
business. Onemeila is correct "I hope you do not mean Kindle Fire Utility....".
This utility will Brick your Kindle Fire 2, it was designed for the Kindle Fire HD 7"
ONLY. Do not attempt to PUSH the system.img from KFU, it will permanently
Brick your Kindle. So, what are you trying to accomplish, exactly?
i'm a noob, please go easy on me. (this is my first post)
i rooted my kindle 2 days ago with qemu and bin4ry root, then installed twrp recovery. being an idiot, i wiped the system before i put the cm10 zip on the kindle, so i had no os. i tried sideloading the cm10 file onto the kindle, but my computer would not recognize the ADB, even though it had drivers installed and was working previously when the kindle was in the normal boot mode.
i read in this thread (http://forum.xda-developers.com/showthread.php?t=2117224) that you can put your kindle into fastboot mode from the twrp command prompt, so i did that, thinking that the adb drivers would work if it was in fastboot mode. they did not.
i have tried installing the adb drivers through the kfu, the android sdk, and every other way i have seen. when my kindle is plugged in, device manager calls it "otter2-prod-4" i have the fastboot with the blinking green light. i do not have a fastboot cable, though one is on its way. if i could get it to show up in adb, i could at least get it to boot into recovery and start again from there, but none of the methods i've seen are working for adb driver installation. can anyone help?
p.s. i am running windows 8 x64
Drivers ok, ADB doesn't show my KF2
Hi, my KF2 is bricked and i'm using a fastboot cable, i think the driver is ok but running the command adb devices i don't see any device connected.
{
"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"
}
ktron said:
Hi, my KF2 is bricked and i'm using a fastboot cable, i think the driver is ok but running the command adb devices i don't see any device connected.
Click to expand...
Click to collapse
You are using a "fastboot" cable, aren't you? You may want to use fastboot commands as well.
Right Driver / no devices attached
soupmagnet said:
You are using a "fastboot" cable, aren't you? You may want to use fastboot commands as well.
Click to expand...
Click to collapse
I have the right driver but i don't see any device, how can you help me?
C:\Users\Admin\Desktop\KFFirstAide100>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Users\Admin\Desktop\KFFirstAide100>
---------- Post added at 01:17 PM ---------- Previous post was at 01:11 PM ----------
prokennexusa said:
crankyy,
This is why I keep asking "what are you trying to accomplish exactly"?
If I know, then we can give you exact step-by-step, thus get you back in
business. Onemeila is correct "I hope you do not mean Kindle Fire Utility....".
This utility will Brick your Kindle Fire 2, it was designed for the Kindle Fire HD 7"
ONLY. Do not attempt to PUSH the system.img from KFU, it will permanently
Brick your Kindle. So, what are you trying to accomplish, exactly?
Click to expand...
Click to collapse
Hi, i have the Fastboot cable, right driver but when i run the command Adb Devices i don't see my KF2, how can you help me??
C:\Users\Admin\Desktop\KFFirstAide100>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Users\Admin\Desktop\KFFirstAide100>
ktron said:
I have the right driver but i don't see any device, how can you help me?
C:\Users\Admin\Desktop\KFFirstAide100>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Users\Admin\Desktop\KFFirstAide100>
---------- Post added at 01:17 PM ---------- Previous post was at 01:11 PM ----------
Hi, i have the Fastboot cable, right driver but when i run the command Adb Devices i don't see my KF2, how can you help me??
C:\Users\Admin\Desktop\KFFirstAide100>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Users\Admin\Desktop\KFFirstAide100>
Click to expand...
Click to collapse
You quoted my post. Didn't you read it as well?
adb reboot bootloader
After I run adb shell su -c "reboot bootloader" it will put KF2 into fastboot mode and try to install usb drivers again and then fastboot can't find the device. The device is visible as a otter2-prod-04 in device manager. I've got windows 7 installed. Any idea appreciate it.
Thanks
If it still says otter2 then the drivers arent installed. Try updating the drivers to the ones in my signature, I believe I added kf2 support to them.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
If it still says otter2 then the drivers arent installed. Try updating the drivers to the ones in my signature, I believe I added kf2 support to them.
Click to expand...
Click to collapse
Thanks for that, I had to install drivers again when I was in fastboot mode and yours worked great. Appreciate your reply.
stunts513 said:
If it still says otter2 then the drivers arent installed. Try updating the drivers to the ones in my signature, I believe I added kf2 support to them.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Hi, this issue sounds just like the one I am having.
I have tried your drivers with no luck.
My KF2 shows up in device manager as OTTER2-PROD-04
And:
USB\VID_1949&PID_000A&REV_0100
USB\VID_1949&PID_000A
I took your drivers and copied them over the drivers in the programme files \ amazon \ drivers folder, rebooted and reconnected but still shows up as this OTTER2
android 4.2.1 worked fine until i updated to android 4.2.2 which was causing so much trouble to me
the pc will detect the phone as offline device seems like the pc unable to recognize the device, but usb tethering still worked fine
after some reading this is due to the adb thingy i suppose? since the 4.2.2 updates the adb for new security purposes but the at the computer side, the adb is not updated
seeing articles http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/ my phone wont detect the rsa on mypc...
i used mskip's toolkit to reinstall the usb drivers but i suppose it is still the old one(maybe still compatible with 4.2.1 but not 4.2.2)
guys please help, if there is some method i can manually update my adb to the newest version which can support my nexus 4
i also updated my Android SDK, all the files included under android 4.2 but still, the computer wont detect it...
jasonmiracle said:
android 4.2.1 worked fine until i updated to android 4.2.2 which was causing so much trouble to me
the pc will detect the phone as offline device seems like the pc unable to recognize the device, but usb tethering still worked fine
after some reading this is due to the adb thingy i suppose? since the 4.2.2 updates the adb for new security purposes but the at the computer side, the adb is not updated
seeing articles http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/ my phone wont detect the rsa on mypc...
i used mskip's toolkit to reinstall the usb drivers but i suppose it is still the old one(maybe still compatible with 4.2.1 but not 4.2.2)
guys please help, if there is some method i can manually update my adb to the newest version which can support my nexus 4
i also updated my Android SDK, all the files included under android 4.2 but still, the computer wont detect it...
Click to expand...
Click to collapse
Hi if you're using the Android sdk and it's all configured properly then make sure that tools and platform tools are up to date. rev 21.1. It's in a separate category in the sdk manager to the base sdk.
jasonmiracle said:
android 4.2.1 worked fine until i updated to android 4.2.2 which was causing so much trouble to me
the pc will detect the phone as offline device seems like the pc unable to recognize the device, but usb tethering still worked fine
after some reading this is due to the adb thingy i suppose? since the 4.2.2 updates the adb for new security purposes but the at the computer side, the adb is not updated
seeing articles http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/ my phone wont detect the rsa on mypc...
i used mskip's toolkit to reinstall the usb drivers but i suppose it is still the old one(maybe still compatible with 4.2.1 but not 4.2.2)
guys please help, if there is some method i can manually update my adb to the newest version which can support my nexus 4
i also updated my Android SDK, all the files included under android 4.2 but still, the computer wont detect it...
Click to expand...
Click to collapse
Try opening the "platform-tools" folder and press SHIFT+right click and open the command prompt with device connected.
Type in "adb devices" and a prompt should show up on your device for allowing usb debugging between your pc and you device.
If you already did this then you can trying removing Nexus 4 drivers from pc, and reinstalling them.
---------- Post added at 03:38 PM ---------- Previous post was at 03:11 PM ----------
AJ Bryant said:
Try opening the "platform-tools" folder and press SHIFT+right click and open the command prompt with device connected.
Type in "adb devices" and a prompt should show up on your device for allowing usb debugging between your pc and you device.
If you already did this then you can trying removing Nexus 4 drivers from pc, and reinstalling them.
Click to expand...
Click to collapse
Also, if you want to unlock and root your device on 4.2.2, use the guide on this forum http://forum.xda-developers.com/showthread.php?t=2147413. Just make sure you use the .img file specific for your device. Hope this helps.
DrFredPhD said:
Hi if you're using the Android sdk and it's all configured properly then make sure that tools and platform tools are up to date. rev 21.1. It's in a separate category in the sdk manager to the base sdk.
Click to expand...
Click to collapse
yup it is r21.1 i checked it... in fact i downloaded all components in android sdk and they are all updated
thats why im puzzled why the adb still not updated(not detecting device)
AJ Bryant said:
Try opening the "platform-tools" folder and press SHIFT+right click and open the command prompt with device connected.
Type in "adb devices" and a prompt should show up on your device for allowing usb debugging between your pc and you device.
If you already did this then you can trying removing Nexus 4 drivers from pc, and reinstalling them.
---------- Post added at 03:38 PM ---------- Previous post was at 03:11 PM ----------
Also, if you want to unlock and root your device on 4.2.2, use the guide on this forum http://forum.xda-developers.com/showthread.php?t=2147413. Just make sure you use the .img file specific for your device. Hope this helps.
Click to expand...
Click to collapse
thanks bryant, your first post helped
seems like we need to use the command prompt to let the pc know our device code?
just felt strange why google implement 4.2.2 update and not telling users to update their adb on their pc as well..
AJ Bryant said:
Try opening the "platform-tools" folder and press SHIFT+right click and open the command prompt with device connected.
Type in "adb devices" and a prompt should show up on your device for allowing usb debugging between your pc and you device.
If you already did this then you can trying removing Nexus 4 drivers from pc, and reinstalling them.
---------- Post added at 03:38 PM ---------- Previous post was at 03:11 PM ----------
Also, if you want to unlock and root your device on 4.2.2, use the guide on this forum http://forum.xda-developers.com/showthread.php?t=2147413. Just make sure you use the .img file specific for your device. Hope this helps.
Click to expand...
Click to collapse
I finally managed thanks to you ..
hey guys
my phone (LG d295F [d290n]) is very very hard bricked but when I connect it to PC is detecting now as "QHUSB_BULK" and a lot of parition are beeing monted on disk tools but I tried to install (all the ways possible) the drivers of QHUSB_BULK, it's done but the driver still with the exclamation sign...
DinhoStork said:
hey guys
my phone (LG d295F [d290n]) is very very hard bricked but when I connect it to PC is detecting now as "QHUSB_BULK" and a lot of parition are beeing monted on disk tools but I tried to install (all the ways possible) the drivers of QHUSB_BULK, it's done but the driver still with the exclamation sign...
Click to expand...
Click to collapse
Did you completely uninstall QHUSB_BULK before installing Qualcomm mobile drivers?
Edit: Oh sorry, you tried all the ways
---------- Post added at 09:23 PM ---------- Previous post was at 09:11 PM ----------
Download ADB http://adbdriver.com/downloads/ (I haven't use this webpage so I can't tell if this work) and in directory where will be ADB, shift + right click -> open command there. Enter "fastboot devices" and tell me is this working
DavRei said:
Did you completely uninstall QHUSB_BULK before installing Qualcomm mobile drivers?
Edit: Oh sorry, you tried all the ways
---------- Post added at 09:23 PM ---------- Previous post was at 09:11 PM ----------
Download ADB http://adbdriver.com/downloads/ (I haven't use this webpage so I can't tell if this work) and in directory where will be ADB, shift + right click -> open command there. Enter "fastboot devices" and tell me is this working
Click to expand...
Click to collapse
Problem Sloved
I changed the OS of my computer to W8 then manually installed the QC Driver
DinhoStork said:
Problem Sloved
I changed the OS of my computer to W8 then manually installed the QC Driver
Click to expand...
Click to collapse
Nice