at first, let me explain my situation.
I just wipe my phone with JF 1.51 CBR43 also got a newest spl and radio.
I succeed to install G1's driver in window XP as like 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"
}
but when I'm in cmd mode and use the adb, it shows as like this
I don't know why I can't find device in cmd mode even though I install driver.
what shall I do now?
system3rd said:
at first, let me explain my situation.
I just wipe my phone with JF 1.51 CBR43 also got a newest spl and radio.
I succeed to install G1's driver in window XP as like this
but when I'm in cmd mode and use the adb, it shows as like this
I don't know why I can't find device in cmd mode even though I install driver.
what shall I do now?
Click to expand...
Click to collapse
did you install Haykuro's updated drivers?
H's updated drivers for 32bit Windows
I used another which is in tutorial.
and Haykuro's updated driver doesn't work out in my PC.
it shows as like this
"there is no information about hardware in where you selected."
<- translated in English. should be different message with yours
http://developer.android.com/guide/developing/tools/adb.html
Check this link...I had the same issue...still not sure I fully understand ADB, but have at least got my connection working after digging through this site...
Related
{
"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"
}
Was looking for this for a very long while.Found them here to save the strain!!:victory:
Do you think these drivers will work on older xp computer?
uploading for xp ASAP!!
edit here
With this tool is very simple !
...........................http://forum.xda-developers.com/showthread.php?t=1983470
adb devices
Hey
I have installed about every driver package I could find of the Oppo find 5, but when I execute the "adb devices" command the device isn't being listed. The device is recognized in device manager and I am able to "see" my other devices (htc one s, nexus 7) in adb. Usb debugging is enabled altough it doesn't show warn me about it in the notification bar.
I got the same problem, my oppo find 5 is not recognized as a device in eclipse on my Mac. Though I can see it as an external storage, so I guess the drivers are installed.
USB Debugging is on of course.
Any idea what I could try so it's gonna be recognized in eclipse?
I am currently experiencing the same issue..i tried installing PDANet and it didnt work.. I will try and see if I can find a resolution.
Here I uploaded the drivers: https://dl.dropboxusercontent.com/u/21558454/Oppo_Find5_x909_drivers.zip
This is for Windows
Hey,
Im using the Google ROM from Jamal for some time now, it works perfectly. Except for one thing, my ADB via WiFi is not working anymore..
Now im wondering, is this Google ROM specific, or is this a problem of Kitkat(4.4)?
Im using this app for ADB wifi (https://play.google.com/store/apps/details?id=com.ttxapps.wifiadb&hl=en)
I've used this app since i have an Android device. It always worked, but not after i installed the Google ROM.
When i try to connect i always get the message "unable to connect to xx.xx.xx.xx:5555" (this happens either on Linux or Windows)
I've tried the tcpip 5555, or any other port. (in the past i've never had to do this anyway!)
I also tried to install any other Wifi ADB app, they are all failing.
If any one could help me out, or experiencing the same problem, let me know.
Thanks!
am i the only one? ;\
I've tried this ROM also: http://forum.xda-developers.com/showthread.php?t=2557353
yet, im still unable to connect :|
{
"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"
}
can any1 at least confirm he has adb over wifi working on a google/kitkat rom?
does no one develop apps on a kitkat rom?
bump
huhu
{
"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"
}
the drivers cannot be found when you boot your phone from the bootloader using BP Tools. From the looks of it if drivers were found for the modem we could access the phone through CDMA workshop which could help us?
anyone know where to find these drivers
You can use motorola drivers and install manually
DireWolfAlpha said:
View attachment 3121755
the drivers cannot be found when you boot your phone from the bootloader using BP Tools. From the looks of it if drivers were found for the modem we could access the phone through CDMA workshop which could help us?
anyone know where to find these drivers
Click to expand...
Click to collapse
Don't forget just getting root isn't your biggest worry. We need a way to get rid of write protection so any changes that are made with root will survive a reboot.
lafont28 said:
Don't forget just getting root isn't your biggest worry. We need a way to get rid of write protection so any changes that are made with root will survive a reboot.
Click to expand...
Click to collapse
If you get a BL-unlock, there's a fastboot command to disable write-protection.
Code:
fastboot oem wptest disable
is the code I believe.
A raging clue
so I was trying to install a custom rom for my nexus 6p like I used to do on my nexus 5 alot...
now i set up my adb and fastboot environment (throgh google's site) as I used to do and it all worked fine
then i tried to unlock the bootloader and it got stuck (only cmd not phone) in "adb devices" i got the device ID
and 2 lines of offlines emulators that i have no idea what they are... i dont run bluestacks btw.. i do run Virtualbox though it has windows 10 on it..
(main PC has windows 10 too)
the emulator names are:
emulator-5576
emulator-5574
added a screenshot attachment
{
"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"
}
anyway is there a way to remove those emulator devices for good? I did try "adb kill-server" but it just restarts the adb server...
then after a few seconds the emulators are coming back... any idea?
any help would be MUCH appreciated, trying to resolve this problem for quite a while now...
Wow wait adb emulator work on bootloader"fastboot"??
wonderdroid87 said:
Wow wait adb emulator work on bootloader"fastboot"??
Click to expand...
Click to collapse
I really dont know much about these things :/ I'm not running any android emulators... not that I know of atleast..
Hi guys, i've bought note 20 ultra recently, i have to flash stock rom to my note fan edition phone but there is a problem.
I've tried several versions of odin in order to flash but no luck.
I had floydq v6.0 before, now phone doesnt even booting it says only "official released binaries are allowed"
Here is my steps:
- I downloaded binaries for N935F from sammobile,
- Tried to flash but no luck it stucks at SetupConnection or NAND Write Start or Set Partition part
- Then i came across with a thread that says i have to enable OEM Unlock but the thing is i couldnt see that switch in my developer settings page, i tried several things
- Now i am trying oem-unlock with fastboot but the thing is fastboot does not recognize my phone, but before the brick adb could see my phone idk what am i doing wrong
- I think i successfully installed the right drivers such as (Google Driver, Samsung OEM driver)
{
"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"
}
Can anyone help me about that problem?
Using odin v3.13.1 solved my problem.