But these drivers are only for a couple of common mobile devices, so what if you have an ARCHOS 8 like me…. you still getting stuck with a nice…. device not found ….
The first part is easy, Archos in my case, offers his own usb drivers .
After downloading the USB driver I got a shiny “Archos 7 ADB” item under “Android Phone” in my windows device manager. But what the hell,…. after restarting the ADB daemon,…. “ADB devices” was only showing annoying … device not found…. mannnn.
Hmm, google is your best friend :-)…… The solution is that the ADB daemon needs also your USB device vendor ID (VID)
If you cannot get it from your device vendor you may look under device manager -> device details -> hardware ID -> USB\VID_xxxx.
The VID for the adb should be placed in a file under {user home}/.android/adb_usb.ini.
Insert the VID in HEX notation {0x0e79}
If this file does not exist, just create it!
have fun
To solve adb device not found errors, you must put kies mode when you conect the usb cable, I habe a i5550l blocked, and i habe just fixed with adb reboot recovery, its the only metod to enter to set factory default and reset all users
Can you give more detail. what is content of adb_usb.ini
still confuse…
thanks
Hi rosibintoro,
You have to insert your VID for example: USB\VID_18D1&PID_2D01&REV_0226&MI_00
0x18D1 in your adb_usb.ini file,
after that restart your adb
Mario
Hell Mahn I Was Trying ADB Since Morning
Finally With Your Fucking Awesome Post I DID IT
:* LOVE YOU MAN
btw you are the first one to get a review on his blog from me
im too lazy to give reviews but i really liked your post
You are Great!
Worked like a charm.
Hi Gaurav
Thx for the flowers 🙂
have fun
Mario
This solved our problems with exotic motorola industrial devices.
Manually editing this adb_usb.ini works fine, but what about comment:
# DO NOT EDIT.
# USE ‘android update adb’ TO GENERATE.
??
Do you know where android tool can be found?
Hi Michael,
The “android update adb” cmd. only scans the SDK for VendorIDs. Others have to be inserted manual.
see -> Resolved Issues, Changes
Editing the “DO NOT EDIT” file means you need to edit it again and again on a regular basis as android runs updates, etc and wipes your edits.
A better way is to find the “add-ons” directory, then create your own directory under that (call it “floodle” if you like, or anything else unlikely to conflict with a genuine add-on).
Now create a file under that directory called “manifest.ini” which is the one the android updater is looking for. Here is an example:
name=Floodle
vendor=Floodle
description=Floodle
api=17
revision=1
usb-vendor=0x2207
Dear Mario
I owe you a beer. You saved me several hours, and also saved me the money I paid for this new Alcatel phone that I bought for testing my apps but couldn’t get working!
With your suggestion my phone shows up in adb!! THANK YOU.
I wish to clarify for other readers the instructions as I was a bit confused.
You need to look at the VID_zzzz entry in device manager, and then just put 0xzzzz in a new line in adb_usb.ini (add 0x and the rest as it is because its already in hex)
CHEERS!
Hi i copied my VID (0x18D1) to the .ini file but it still couldnt find the driver..
there is this note:
# ANDROID 3RD PARTY USB VENDOR ID LIST — DO NOT EDIT.
# USE ‘android update adb’ TO GENERATE.
# 1 USB VENDOR ID PER LINE.
What does this mean? Help.. thankyou
Hi Mina,
This means that some devices from google are added automatically at ADB installation. If you own another device you have to add your device VID by yourself.
have fun
Mario
Hello,
This does not help me with my Alcatel 991. I’ve got two Hardware IDs both beginning with VID_1BBB&PID_00F2&…., there was no adb_usb.ini so I created it with notepad and put in:
0x1BBB
Even restarted the PC, still no devices. Any suggestions,please.
Darin
Hi Darin,
@no adb_usb.ini, do you have installed the Android Developer Tools (ADT)?,…. no adb_usb.ini sounds like that
when i go to device manager i can see two hardware ID’s.What should i put in the adb_usb.ini?
and what do you mean with:”Insert the VID in HEX notation{0X0e79}”?
Hi Sascha,
@Two hardware ID’s, if in doubt take both hardware ID’s
@HEX notation, this means that the value is written with an preceded “0x”,… 0x1234 [hex] = 4660 [dezimal]
I am a noob, and have been struggling with this for a few days now. What do you mean exactly ,by “”Insert the VID in HEX notation” How does one insert the VID. I have the hardware ID’s ,do I need to convert to Hex? And what do I insert it into or onto? A walk through on this point would be much appreciated. Please help Thank You
Hi Billyboyles
One way to get the VID, go to your Windows Device Manager -> select your plugged in S3 -> click proprties -> device details -> under properties select “Hardware-Ids”
In the value field you should see something like “USB\VID_04E8&PID_685c” -> VID = 04E8 in [HEX]
For Android developing you have to insert this value “04E8” with “0x” prefixed -> “0x04E8” right into you {user home}/.android/adb_usb.ini.
hope that helps
Mario
Thanks for your reply Mario. Like I said, I am new to all of this and need to ask many Questions. How do I “insert” it into the folder /.android/adb_usb.ini. ?? Just write it down on a word file?? :)) or??
Thanks very much. I’m learning a lot and I’m hoping that rooting this phone gets easier.
Hi Billyboyles
The adb_usb.ini goes to “%USERPROFILE%\.android\adb_usb.ini”. Be aware this is for the Android development stuff.
If you want to “root” you phone, I would suggest “SuperUser” from the Store 🙂
Mario
Hello Mario….
You are life saver….i was fighting with android sdk and drivers and many other thing from last 7 hours….You Save my more precious hours…Thank you sooo much…..
Just to try to clarify my last post. I am at the point where I my phone is recognized and when I use the Doomlord program it sometimes says that Daemon has started. But, then nothing happens. The advice I get from Rooting Chinese Spreadtrum Phone w/ Android 4.0.3 is that the program doest recognize my VID. I have a Samsung Galaxy S3 replica (clone fake,
Model number: S930.
Hi, Billy! I have the same phone Spreadtrum S930. When I tried doomlord also, at first the computer was saying device is read only. what i did was to go to ADB and type ADB root -d then afterwards I did ADB remount -d. After that, doomlord was able to root my phone. I hope this helps.
I have this phone:
I9300DDKL1
2.6.35.7-I9300XXKL3-CL793489root@DELL136#2
GINGERBREAD.XXKL3
android: 4.1.9
i tried hex in vid and inserted in the adb_usb.ini file
but still adb or doomlord do not reconise my phone.i am so
stuck.to make sure i was doing it right can somone walk me through it.
regards
Hi Mario,
i took my device ID as you mentioned above:USB\VID_04E8&PID_6860&REV_0400&MI_00
and i am using windows 7. where can i find this ini file please?
Regards,
Omer
Hi Omer,
Your .ini should be located under “%USERPROFILE%\.android\adb_usb.ini”. If not just create one.
regards,
Mario
Thank you very much 😀
Hi,
I got the VID from device manager .And I also got that *.ini file inside .android directory But I am not getting the device in eclipse . what should be the way to get device.
Hi,
Have you inserted your VID in your .ini?
What is the output of: “adb devices”
USB\VID_0x109B&PID_9117&REV_0229&MI_00
or
0x109B in a new line seperately i am confused
this is what is seen in my hardware ids
USB\VID_109B&PID_9117&REV_0229&MI_00
USB\VID_109B&PID_9117&MI_00
Hi,
Yes you need to insert 0x109B.
Thnx a lot!
The solution with a adb_usb.ini solve my problem
My devices id is below
i dont have adb_usb.ini file there
Creates new one then,inserted below text still its not not working
is it right method?
USB\VID_1782&PID_5D04&REV_0229&MI_01
USB\VID_1782&PID_5D04&MI_01
0x1782
Hi,
You only need 0x1782.
You also need to install the corresponding ADB driver for your phone.
Search for “UniversalAdbDriver”
regards
Mario
Hi,i have a sprd s930
I did all the steps but I get this in doomlord
adb server is out of date
ADB server didn’t ACK
failed to start daemon
error: unknown host service
Hi,
Sounds like you are using a different version of SDK and ADB.
Have a look at http://forum.xda-developers.com/showthread.php?t=567955
regards
Mario
Hey guys… I am so stumped here. I cannot get ADB to list my device under the “adb devices” command. I have a Cruz PS47 Tablet. I’ve downloaded the latest Android SDK. I’ve tried all usb ports. I cannot get this to work on my Win XP or Win 7 machines.
I’ve read the earlier posts and have modified the adb_usb.ini file (USB\VID_0x2396 is what it’s been switched to). I’ve tried rebooting both the main machine and the Android device.
I’ve stopped the adb server (“adb kill-server”) and then started it again (“adb start-server”). It all appears to go correctly. My device manager correctly recognizes the Android device and lists the device driver as “Android Composite ADB Interface”. My Cruz tablet has “USB debugging” checked. And the tablet also shows that it’s connected, “USB connected”.
Nothing. When I type in adb devices I get,
“List of devices attached”
And that’s it! Your help and expertise is appreciated.
.
Tim
Hi,
Have you also installed the ADB driver for your tablet?
See
regards
Mario
Hi Mario! Thanks for getting back to me…..
.
I have loaded the latest ADB driver from the Cruz website (my tablet is a Cruz PS47 tablet) onto both my xp and windows 7 machines. When you bring up the device manager and click on the listed “Android Phone”, it further lists itself as “Android Composite ADB Interface”. It also lists this title of “Android Composite ADB Interface” under the driver tab within the device manager.
.
Now, I have not installed anything onto the Android Cruz tablet. Is there something additional that needs to be loaded onto the tablet itself.
.
Tim (Atlanta, GA, USA)
Hey Mario, an update on my connections here. It appears that my problem is unique to the Cruz PS47 tablet that I have. What I did is I had an old Huawei Android phone lying around and decided to hook it up to my computers. I wanted to see if this one gives me the same problem as my Cruz tablet. Once I loaded up the usb drivers from Huawei’s web site all worked well and I now have an ADB connection. And this works on both my XP machine and my Win 7 machine.
.
Other than having a unique problem with the Cruz tablet, I think I have solved my problem here on my own. If you think you can give me any other pointers with regards to this specific android tablet, let me know. Nevertheless your website here made me check everything over and also modify that adb-usb.ini file. It has been a big help and I’m thankful for your online presence to assist me if need be.
.
You’ve got my e-mail, I’ve got beers for you in Atlanta, Georgia, USA if ever you’re here. Thank you and drop me a line.
.
Tim
Hi Tim,
Glad to hear it is working for you.
@Beers, thx if I’m anywhere close to your location, I’ll stop by. 🙂
Mario
mario,
i already instal adb composite interface and also edit the
adb usb.ini file , my system properties show correct driver but when i try to root my device , adb device , nothing connected ,
please guide
Hi,
It’s hard to tell without knowing what device and what program you are using for rooting.
spreadtrum mobile sp6820a android 4.0.4.
i am using this process for rooting , i am using windows xp.
http://www.pocketables.com/2011/06/how-to-manually-root-almost-any-android-device.html#comment-176642
I edited the adb_usb file. It worked once.. I restarted and not it does not anymore… what gives??
hey mario, is this correct in the adb_usb.ini?
# ANDROID 3RD PARTY USB VENDOR ID LIST — DO NOT EDIT.
# USE ‘android update adb’ TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1782
Hi Richard,
Yes 0x1782 should be sufficient.
thx but i can’t get adb to recognize the spreadtrum based chinese phone. the pc is recognising it but not adb.
Have you also installed the corresponding ADB driver ?
In Ethiopian Language we say “Betam amesegnalew”, which means thank you very much.
I really desperated! Google, forums, download pdanet and so many adb files, including adb sdk from Google, but can’t solve “no devices attached” message.
But…
Tons of thaaaaaaaaaaaaaaaaaaaankss!!
I really want to hugs you, a really tight one!!!!
Tyia ^_^
🙂
Man please tell me procedure. i am waiting the same arised me on my micromax a57. But still i can’t solve. i download drivers from micromax site and installed. And i have sdk folder that containes platform tools also. adb usb.ini inserted both platform tools & user profile .android folder even when i try to adb devices there is no device listed. Plzzzzzzzzzzzzzzzzz tell me the how to solve. i checked my VID also, the same in hardware id it is in my adb usb.ini. i did all the things. i checked bothe usb debegging & usb tethering. adb interface is showing in device manager. Plzzzz tell me the procedure or mail me vetri.jc1@gmail.com…..
while running the android application in android studio I got an error “ADB not responding. You can wait more, or kill “adb.exe” process manually and click ‘Restart'” like this. how to resolve it..
For my tabled DFP1008R with Rockchip RT2918 helps only one trick. As many people before, I added VID and PID to INI file and correctly installed, but ADB not see device anymore.
I find one special adb.exe (size 161792 bytes) which has probably some special root script inside and when I run adb start-service with this special exe, I can get full access to my tablet, hurray! =)
I downloaded adb.exe in pack from this link.
http://forum.xda-developers.com/showthread.php?p=34006332#post34006332
Add this lines to android_winusb.inf.
;RockChip SDK
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0000&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0001&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0002&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0003&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0004&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0005&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0007&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0010&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0011&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0012&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0013&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0014&MI_01
Thanks for this!
Had been struggling to find a solution for this. Was trying all the drivers in the world.. 🙂
thanks again.
mario hello i have note 3 with galaxy gear i wanted to instal custom flash on my gear so when i looked at youtube they asked me to install ADB and i did when i ran CDM as administrator and i typed Adb reboot device not found and iam sure i plugged em in correctly plz help many drivers i found in the adb manager i just downloaded 4.3 because thats the version on my note3 still same issue what iam supposed to do??
Hello Mario.
You are simply great !! The solution worked for my Videocon A26 mobile . Now it is working like a charm. Thanks a ton.
Hi Mario,
I did all the said things above to get the device list, but i am still not getting the list of devices. I created the “adb_usb.ini” file under .android folder, have put entries like,
USBVID_0x04E8&PID_685E&REV_0400&ADB
USBVID_0x04E8&PID_685E&ADB
USBVid_0x04E8&Pid_685E&MI_03
USBVid_0x04E8&Pid_685E&Class_FF&SubClass_42&Prot_01
When I type in adb devices I get,
“List of devices attached”
I have already installed UniversalAdbDriver and Kies too.
I am using Samsung Galaxy Duos(GT-S7562)
When I change the settings to “Allow Debugger” option, then i am able to get the device list, but I don’t want to change the setting and get the device list with ADB command.
Please help me out, i am struggling for past many days on this.
Regards,
Manoj
Hi Manoj,
You only have to paste tjhe VID id into the adb_usb.ini file.
Insert the VID in HEX notation {0x04e8}
regards
Mario
Hi Mario,
Thanks for reply.
I did the changes as suggested, but still the same issue.
Unless I change the settings of “USB Debugging” under settings->Developer Options, it doesn’t fetch any device list or anything.
Regards,
Manoj
Hi Manjo,
Your Devices has to bee in “Development Mode” to be recognized by ADB.
regards
Mario
Hi Mario,
I have a Prestigio Quad 10.1 tablet and I did all the steps to make it appear via ADB but it does not.
I also have a Samsung phone and the ADB can find it without problem.
I added the necessary lines to the adb_usb.inf file but I can’t see the device in the list.
;rockchip
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0010&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0011&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0012&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0013&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0014&MI_01
;RockChip SDK
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0000&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0001&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0002&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0003&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0004&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0005&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0007&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0010&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0011&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0012&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0013&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0014&MI_01
What else should I do?
wow. Thanks work in my hh
For all you folks with spreadtrum phones, to have adb work you’ll need the development debug drivers which can be found here: http://kiteplans.info/2013/09/25/spreadtrum-adb-android-debug-bridge-drivers-zte-u791-windows-64bit-mac/
You can also find more info there on adb, how to insert the vid and rooting your phone.
Cheers
worked fine on a mapan f10b 2014. I hacked drivers and random stuff to no avail. but this worked.
Hi I’m almost get it, but I have one question, is that the %USERPROFILE%.androidadb_usb.ini is on my sd card or phone? Or its somewhere on adb files?
Hi Man..
Your suggestion work for me….
thanks a lot.
thank you
hi,
Inside the google usb driver i have a an android_winusb.inf file. when i open it the following is inside:
;
; Android WinUsb driver installation.
;
[Version]
Signature = “$Windows NT$”
Class = AndroidUsbDeviceClass
ClassGuid = {3F966BD9-FA04-4ec5-991C-D326973B5128}
Provider = %ProviderName%
DriverVer = 12/06/2010,4.0.0000.00000
CatalogFile.NTx86 = androidwinusb86.cat
CatalogFile.NTamd64 = androidwinusba64.cat
;
; This section seems to be required for WinUsb driver installation.
; If this section is removed the installer will report an error
; “Required section not found in INF file”.
;
[ClassInstall32]
Addreg = AndroidWinUsbClassReg
[AndroidWinUsbClassReg]
HKR,,,0,%ClassName%
HKR,,Icon,,-1
[Manufacturer]
%ProviderName% = Google, NTx86, NTamd64
[Google.NTx86]
; SonyEricsson
%SingleAdbInterface% = USB_Install, USB\VID_0FCE&PID_0DDE
%CompositeAdbInterface% = USB_Install, USB\VID_0FCE&PID_0DDE&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0FCE&PID_0DDE
; HTC Dream
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
; HTC Magic
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C03&MI_01
;
;Moto Sholes
%SingleAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB
%CompositeAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB&MI_01
;
;Google NexusOne
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E22&MI_01
[Google.NTamd64]
; SonyEricsson
%SingleAdbInterface% = USB_Install, USB\VID_0FCE&PID_0DDE
%CompositeAdbInterface% = USB_Install, USB\VID_0FCE&PID_0DDE&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0FCE&PID_0DDE
; HTC Dream
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
; HTC Magic
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C03&MI_01
;
;Moto Sholes
%SingleAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB
%CompositeAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB&MI_01
;
;Google NexusOne
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E22&MI_01
[USB_Install]
Include = winusb.inf
Needs = WINUSB.NT
[USB_Install.Services]
Include = winusb.inf
AddService = WinUSB,0x00000002,WinUSB_ServiceInstall
[WinUSB_ServiceInstall]
DisplayName = %WinUSB_SvcDesc%
ServiceType = 1
StartType = 3
ErrorControl = 1
ServiceBinary = %12%\WinUSB.sys
[USB_Install.Wdf]
KmdfService = WINUSB, WinUSB_Install
[WinUSB_Install]
KmdfLibraryVersion = 1.9
[USB_Install.HW]
AddReg = Dev_AddReg
[Dev_AddReg]
HKR,,DeviceInterfaceGUIDs,0x10000,”{F72FE0D4-CBCB-407d-8814-9ED673D0DD6B}”
[USB_Install.CoInstallers]
AddReg = CoInstallers_AddReg
CopyFiles = CoInstallers_CopyFiles
[CoInstallers_AddReg]
HKR,,CoInstallers32,0x00010000,”WdfCoInstaller01009.dll,WdfCoInstaller”,”WinUSBCoInstaller2.dll”
[CoInstallers_CopyFiles]
WinUSBCoInstaller2.dll
WdfCoInstaller01009.dll
[DestinationDirs]
CoInstallers_CopyFiles=11
[SourceDisksNames]
1 = %DISK_NAME%,,,\i386
2 = %DISK_NAME%,,,\amd64
[SourceDisksFiles.x86]
WinUSBCoInstaller2.dll = 1
WdfCoInstaller01009.dll = 1
[SourceDisksFiles.amd64]
WinUSBCoInstaller2.dll = 2
WdfCoInstaller01009.dll = 2
[Strings]
ProviderName = “Google, Inc.”
SingleAdbInterface = “Android ADB Interface”
CompositeAdbInterface = “Android Composite ADB Interface”
SingleBootLoaderInterface = “Android Bootloader Interface”
WinUSB_SvcDesc = “Android USB Driver”
DISK_NAME = “Android WinUsb installation disk”
ClassName = “Android Phone”
where do i put my VID? i don’t know much about this kind of stuff. help wiil be much appreciated. thanks!
UPDATE
found out i was in the wrong folder. i went to {user home}/.android/ but there was no adb.ini file in it just some files from named adbkey. i already have sdk installed and the platforms and the google usb driver found in the extras but i cant still find the adb.ini file. what should i do? thanks
dude ur just simply awesome 🙂 just one help. My phone has internal storage only and i need it to mount it to install new recover. adb commands is not working im stuck in bootloader. phone is not rooted just had kitkat update and while updating and roboot phone droped and turned off now if i turn it on it boot loop. or Android 3e recover so im trying to use adb as only option to get new recover or new rom.
The biggest beer for you is on the way!!!! 😀
Hi,
I did exactly the same. but still my device is showing in offline mode. Pls help.