guys.anyone here is an ADB expert ?
got something to ask
im using a Mac OSX. ADB & Fastboot works fine with my previous phone (Nexus 4)
i just got my Nexus 5 2 days ago but then, i ran into a bit of "problem" with ADB when i plug into my mac and run "adb devices"
ADB did detect my phone but the status is offline
Tried to enter fastbot boot and flash some stuff(recovery etc), it works fine no problem.Fastboot can detect my phone.
I tried to enter recovery,leave my phone in recovery mode and try adb devices, ADB can detect my phone,no problem at all and even the ADB status is correct which is recovery.
Is it normal that ADB status is offline if we run "adb devices" outside out recovery mode ?
i've tried
1. revoke usb debugging authorization
2. restart phone
3. switch on/off usb debugging
4. reinstall back ADB & Fastboot
no go.ADB still detects my phone as offline
Any idea ?
Did you try a different cable? I screwed around for hours and it was the dam cable
Sent from my Nexus 5 using XDA Premium 4 mobile app
ilostmypistons said:
Did you try a different cable? I screwed around for hours and it was the dam cable
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
really ? it's a new cable & somemore it works on fastboot & other ADB mode
It worked on my osx with N5.
Sent from my Nexus 5 using Tapatalk
fitree said:
really ? it's a new cable & somemore it works on fastboot & other ADB mode
Click to expand...
Click to collapse
I started out using a old cable that I leave plugged in then switched to the new one that came with the nexus and presto it worked
Sent from my Nexus 5 using XDA Premium 4 mobile app
Related
I missed out something i think.
I have my sdk, with those files.
I went to cmd and type the commant
bla bla bla
fastboot devices >>> no error, means connected
fastboot oem unlock
>>>> it is connected but why it still waiting for my device?
I added the path to the system too, but still cant get rid of
I search the net and I cant get the solution.
Any idea anyone?
What drivers did you install? And yes, I read the "fastboot devices"
installed everyhing...
samsung adb + google package
samsung driver
pdanet
Phone has to be in bootloader mode?
Sent from my Nexus S using XDA App
yup.. it is in volume up + on mode.
If you plug your NS in and look in the Device Manager, do you see an unknown device with the question mark? If so, you should try to manually install the driver located in android-sdk-windows\extras\google\usb_driver
And when you issue the command
Code:
fastboot devices
It should display your NS device id, not just a blank line.
melvinchng said:
installed everyhing...
samsung adb + google package
samsung driver
pdanet
Click to expand...
Click to collapse
"samsung" driver... no
you use the drivers obtained from the Android SDK or PDAnet
Pretty much what suksit said.
Try pdanet! Last place i go y find drivers
Sent from my Nexus S using XDA Premium App
I tried sdk driver, pdanet driver. I can't unknown driver, it is listed as android. Means my phone is found by computer
I have android 2. 3. 4. Does it effect?
Sent from my Nexus S using XDA Premium App
Just curious, did you enabled the option in Settings > Applications > Development > USB debugging?
In Device Manger it should say something like "Android Composite ADB Interface"
I enabled it too... maybe I will try to reinstall and root it via my XP in VM.
I rooted my wildfire with this pc last time, maybe the drive mixed up.
Sent from my Nexus S using XDA Premium App
Just noticed that your location is in Malaysia. Could it happen that you have the i9023 (SLCD) model? If that's the case then I think you should try this.
Ya, I bought slcd set.
I will try it tomorrow at night and report back to you guys.
--------------------------------
It is really strange. Tried everything and won't work.
Pdanet detected my device that it is connected to computer, but it just show wait for device.
----------------------------------------
Edit: my full charge is 95%, it is normal right?
Sent from my Nexus S using XDA Premium App
melvinchng said:
Ya, I bought slcd set.
Edit: my full charge is 95%, it is normal right?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Yeah thats normal, Samsung did some weird battery calibration thing!
However people here have found to get 100% or close to it.
When charging just leave screen on for 1 hour and have tethered wifi On, so far im charging full up to 98%, just waiting to squeeze in the last 2%.....could take awhile.
and yeah the 95% charge is normal. heres a explanation in further detail
Your battery gauge is lying to you (and it's not such a bad thing)
make sure u have following dlls in fastboot folder
AdbWinUsbApi
AdbWinApi
j0l6 said:
make sure u have following dlls in fastboot folder
AdbWinUsbApi
AdbWinApi
Click to expand...
Click to collapse
i have these in tools. and still waiting for device.
anyone any idea?
I forgot to tell you guys that my windows is 64-bit
Sent from my Nexus S using XDA Premium App
Try this or this then (the latter is quite hard to read anyway, I think they messed up the code formatting)
Unlocked bootloader!
thanks!
Sent from my Nexus S using XDA Premium App
melvinchng said:
I haven't root yet.
After I root, my storage and Rom will be wipe? So I need to install new Rom?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Rooting will add su binary and Superuser app to your NS. But your data will be wiped (both on phone and SD card) when you unlock the bootloader -- it's the same as doing a factory reset. However, your system partition will not be affected so no need to install new ROM if you prefer using stock.
Okay so I did read up on another post about the same issue but it didn't really explain what fixed it. I only have a windows xp or vista or something computer. Its a 32 bit. I have installed and uninstalled drivers from SDK manager, manually installed Google drivers, universal drivers. All of it. I originally tried rooting using cf auto. Than tried to do it manually. That is when I realized it was a fastboot issue. I'm in fastboot mode during my attempts. Should it say fastboot USB when plugged in?
Sent from my Nexus 5 using xda app-developers app
whozilla said:
Okay so I did read up on another post about the same issue but it didn't really explain what fixed it. I only have a windows xp or vista or something computer. Its a 32 bit. I have installed and uninstalled drivers from SDK manager, manually installed Google drivers, universal drivers. All of it. I originally tried rooting using cf auto. Than trues to do it manually. That is when I realized it was a fastboot issue. I'm in fastboot mode during my attempts. Should it say fastboot USB when plugged in?
Click to expand...
Click to collapse
Have you endabled USB debugging under Developer options in your Settings?
Yep. More details
I have uninstalled and re installed all drivers from
lgs driver .exe
From the universal. Driver.
And google drivers
via sdk manager.exe.
I did that after i re set up android SDK in the c drive,s root. and ran the commands from directly in the platforms folder. Still my device is only seen under adb devices. Not fastboot devices. I just type in fastboot in the promt and it shows all the commands listed so I assume it has been set up.
Now it seems SDK manager won't open. A promt pops up and closes with no program open thereafter. I wanted to retry googles drivers because I uninstalled and re set up android SDK. I wanted to re download the packages and start fresh.
Sent from my Nexus 5 using xda app-developers app
whozilla said:
Yep. More details
I have uninstalled and re installed all drivers from
lgs driver .exe
From the universal. Driver.
And google drivers
via sdk manager.exe.
I did that after i re set up android SDK in the c drive,s root. and ran the commands from directly in the platforms folder. Still my device is only seen under adb devices. Not fastboot devices. I just type in fastboot in the promt and it shows all the commands listed so I assume it has been set up.
Now it seems SDK manager won't open. A promt pops up and closes with no program open thereafter. I wanted to retry googles drivers because I uninstalled and re set up android SDK. I wanted to re download the packages and start fresh.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Google tool adb fastboot drivers xda. That should get them working
Nice. gonna try as soon as I get home from work. I'll report back with result :thumbup:
Sent from my Nexus 5 using xda app-developers app
You're still thinking of HTC phones...
When in fastboot it will no change on the phone itself, you check by running 'fastboot devices' in the command prompt. If you see your serial number, it's fine. If you don't, go into Device Manager and manually update the driver
If you run 'adb devices' when connected in fastboot nothing will happen as adb is ONLY FOR WHEN ANDROID IS RUNNING (how many more times does this need to be said??).
whozilla said:
Nice. gonna try as soon as I get home from work. I'll report back with result :thumbup:
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I'm sorry eddy. It seems you misread my posts. Im not having an issue understanding the difference between adb and fastboot. Allow me to clarify. While phone is on. With USB debugging enabled. I type
adb devices
in the command prompt under platform tools.. My device shows up and I have authorized it
When my phone is in the bootloader in fastboot mode. I type
fastboot devices
Nothing. That is my issue. Feel free to scroll back up and read the details. Any help is good help :beer:
Sent from my Nexus 5 using xda app-developers app
EddyOS said:
You're still thinking of HTC phones...
When in fastboot it will no change on the phone itself, you check by running 'fastboot devices' in the command prompt. If you see your serial number, it's fine. If you don't, go into Device Manager and manually update the driver
If you run 'adb devices' when connected in fastboot nothing will happen as adb is ONLY FOR WHEN ANDROID IS RUNNING (how many more times does this need to be said??).
Click to expand...
Click to collapse
I quoted myself by mistake haha. PS
I have manually updated drivers. After uninstalling them to be clear. That's what I meant when I said I tried the universal drivers. For the record. All attempts I have made to get fastboot to recognize my device have been done using forums with detailed instructions.
Sent from my Nexus 5 using xda app-developers app
Sounds like Windows isn't wanting to use the driver. Manually update the driver and point it to the *.inf file in the SDK. It should then work fine
Solved. Such a small detail. Eddy you were right. Before I could see your post I realized. Vuala! I needed to update the drivers manually with the phone plugged in in fastboot mode!. That was my mistake. Cf root did the rest.
In device manager you will see a yellow triangle under other devices when the nexus is plugged in on fastboot mode. I installed drivers from the .exe found in this thread.tool adb fastboot drivers. I let the computer search on its own for updates. Done. Rooted
Sent from my Nexus 5 using xda app-developers app
jd1639 said:
Google tool adb fastboot drivers xda. That should get them working
Click to expand...
Click to collapse
Thank you sir. You lead me in the right path
Sent from my Nexus 5 using xda app-developers app
Has anyone ever had an issue where the phone would charge when connected to a PC or MAC, but will not connect to do any file transferring or to use fastboot or adb?
My drivers are all up to date and my Nexus 7 connects perfectly fine. My nexus 5 used to connect and something happened where my phone got stuck in a boot loop so I flashed the factory image and since than it won't connect.
USB debugging is checked. Everything is the way is supposed to. Like I said my nexus 7 connects just fine. MTP is checked, I have tried with both options.
Thanks for any help.
Sent from my Nexus 5 using xda app-developers app
Also when I boot into fastboot and I run fastboot devices it give me this error
"Could not get pipe properties"
Sent from my Nexus 5 using xda app-developers app
For mac, you just need to install android file transfer. To use the fastboot and adb commands you need to download the sdk. When you flashed the factory image, did you format the cache?
Sent from my Nexus 5 using Tapatalk
I have all of that installed and my phone used to connect. My nexus 7 connects with no issues. Yes I did wipe cache after I flashed the stock images.
Sent from my Nexus 5 using xda app-developers app
on windows OS, and when boot phone in TWRP, does your nexus show up on device manager? as "unknown device" or "AOSP hammerhead"?
When I connect to the PC it doesn't show up under device manager. When I boot into the bootloader or stock recovery it doesn't show up either. But it charges
Sent from my Nexus 5 using xda app-developers app
DROIDNP said:
When I connect to the PC it doesn't show up under device manager. When I boot into the bootloader or stock recovery it doesn't show up either. But it charges
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
smells like data pin/coil in the micro usb/charging port failing
When you connect your phone, does a notification about USB debugging appear or not? If not, then RMA time. If it does, I have no clue
I can't get my droid ultra to be recognized other than offline and can't flash it back to try the root method it says i need the fastboot o bake driver .RSD lite doesn't recoginze it in fastboot can anyone suggest a fix i have installed moto device manager 5 times each differet downloads
If I boot it up in bp mode red lite see the phone until it reboots to fastboot the it says it didn't switch modes but it seems to
Sent from my XT1080 using XDA Premium 4 mobile app
Make sure USB debug is enabled. Make sure the phone is not on the lock screen while plugged in. Unplug and replug the device. Restart the adb service (adb kill-server, then adb start-server).
These are the easiest things to try that come to mind.
Debugging is on ,lockscreen is not on . unplugged my phone and killed and restarted the server and still showing offline. Just used the same computer to unlock a HTC droid incredible 2 today and restore a lg optimus elite from a bootloop cycle. So I am pretty sure its not a issue with the computer I am using ,but I guess its time to try another computer and see if it changes anything. Any ideas or help is much appreciated and thanks nimdae for the input
Sent from my XT1080 using XDA Premium 4 mobile app
Make sure you have updated adb to the latest
Sent from my XT1080 using XDA Free mobile app
akellar said:
Make sure you have updated adb to the latest
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
Glad you mentioned that has been quite some time since I updated it. Will get it done when this lg p930 is finished and be back .with good news I hope
Sent from my XT1080 using XDA Premium 4 mobile app
Yes, if it reports offline, then you don't have ADB 1.0.31. Type "adb version" and make sure it's 1.0.31.
kcipopnevets said:
Yes, if it reports offline, then you don't have ADB 1.0.31. Type "adb version" and make sure it's 1.0.31.
Click to expand...
Click to collapse
OK your right . how do I get the new one download it from the android SDK website? Well that's what I'm going to do tonight thanks all for the great help
Sent from my XT1080 using XDA Premium 4 mobile app
dogie425 said:
OK your right . how do I get the new one download it from the android SDK website? Well that's what I'm going to do tonight thanks all for the great help
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You should be able to update the tools through the manager, though I've been having trouble using the latest manager myself (it doesn't load). Otherwise, you can go to dev.android.com and download the latest package which includes the tools.
Got the new version install . and I plan to flash back to 4.4 version 19.5.3 for my phone. RSD lite is still not detecting the phone when it switches to fastboot so that brought up the question in my mind do I need to update fastboot or was this done when I updated the adb and is there anything else I might be forgetting to do b4 I start this since I will be using the manual method to flash this in fastboot? Any and all feedback is greatly appreciated. This is my everyday driver and I'm still paying for it thru the edge plan.
Sent from my XT1080 using XDA Premium 4 mobile app
Have you tried putting your phone in fastboot mode then connecting it to pc
TRIED Flashing thru fast boot
so i got the nerve to try downgrading my ultra with fastboot since rsd won't detect my phone when it switches to fastboot using this tutorial http://forum.xda-developers.com/showthread.php?t=2580060 all went well except on the mfastboot command i got this responce
C:\ANDROID PWNAGE\adt-bundle-windows-x86_64-20130917\adt-bundle-windows-x86_64-2
0140321\sdk\platform-tools>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'system' (574208 KB)...
OKAY [ 36.243s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 59.547s
and it said on the screen mfastboot error invalid piv image size for system
now the phone won't boot just jumps right back to the bootloader screen
tried it 2 more times and still no joy same out come so what do i do now? download the file again and try once more . and do i need to repeat all the steps b4 this command or will just running this command alone be fine to fix me HELP pls
Lordomn said:
Have you tried putting your phone in fastboot mode then connecting it to pc
Click to expand...
Click to collapse
yes i tried that but found out my adb was an older version and need to be updated its seeing the phone fine now. just have to figure out my latest problem
GOOD NEWS i unzipped a second download i had in my downloads folder and used that system img file to try flashing and it when through. phone is rebooting now. time to clam down and try me some pie in a bit
(thanks jcase for the pie)
You need to update your adb and fastboot files if your devices is shown as offline...
joel_sinbad said:
You need to update your adb and fastboot files if your devices is shown as offline...
Click to expand...
Click to collapse
Pretty sure we established that roughly 3 weeks ago
Sent from my XT1080 using XDA Free mobile app
akellar said:
Pretty sure we established that roughly 3 weeks ago
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
Lol
usb debugging is not necessary for fastboot commands, only ADB; however, it sounds to me like you do not have the proper drivers installed for the device if RSD is not detecting it. I would delete all Motorola drivers and Motorola Device manager, reboot computer with device unplugged, reinstall Device Manager, and then connect device. You can also download Minimal ADB and Fastboot (Google search) and it is a lot less hassle than trying to use the SDK.
You may also try using a different USB cable on a different USB port (not USB 3.0). Sometimes that causes problems.
In the end my problem was my SDK was not updated ,so the device was only seen as offline as for why rsd doesn't detect it in fastboot I do not know ,but I was able to manually flash it in the end. Now I'm loving w/p off and root with safe strap installed despite the locked bl
Sent from my XT1080 using XDA Premium 4 mobile app
Hi all,
Before explaining what the problem is, I want to state I have searched Google, XDA and various other websites to solve it myself. I do know the #1 rule of XDA
Today I've tried to use ADB Sideload to install a rom on my Nexus 5. I've done this before one time, when I accidentally formatted my entire phone, and it worked. Currently my phone is in TWRP Recovery, and ADB does recognize my phone when I type in 'adb devices' in the command prompt. However, when I click ADB Sideload on TWRP to sideload the rom from my laptop, the phone disconnects from my laptop (I hear the 'ding' from Windows), and I can't sideload anything at all.
I did update all possible drivers (ADB and Google), tried all USB-ports available, and even tried another laptop, but nothing worked.
Can you guys help me out, or provide new information about the issue?
Thanks in advance
With your device connected to your pc and booted into to twrp, go to device manager on your pc. Do you see an icon with a yellow exclamation mark? If so go to where you can choose from a list on your computer. Choose Android adb composite driver.
Sent from my Nexus 9 using XDA Free mobile app
Or just scrap off adb. Download stock img's from Google and fastboot em in bootloader to get your phone up and running again
Sent from my Nexus 5 using Tapatalk
jd1639 said:
With your device connected to your pc and booted into to twrp, go to device manager on your pc. Do you see an icon with a yellow exclamation mark? If so go to where you can choose from a list on your computer. Choose Android adb composite driver.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
So far I did this, and ADB finally allows my phone and laptop to sideload files (so thanks a lot). I did install two seperate roms at two seperate moments via sideload, but after booting up and showing the 'android' logo for a couple of minutes, the screen stays black (for both roms). I know the first boot takes a while, but this never happened to me before, and the phone won't start up anything further. Any new ideas?
Edit: tried it again with a third rom, and this one does install completely (Cataclysm, with AROMA). Even my laptop recognizes my phone and automatically starts Dropbox, but the screen stays black. Did I kill my phone?
Ben36 said:
Or just scrap off adb. Download stock img's from Google and fastboot em in bootloader to get your phone up and running again
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Edit: it worked. I apparently followed the wrong tutorial, because it did flash it after all. Thanks!