All kinds of fun stuff here.
Ive updated drivers and restarted the computer. I cant get ADB to list any devices. I also flashed a recovery inside of a toolkit and now my recovery is a android with a triangle. I also cant seem to connect to google play servers anymore as all of my app downloads are just hanging.
Any ideas?
Related
hello,
I'm hoping someone here can help me sort out my current problem.
I've been trying to root so I can install the latest ICS port, but having problems at the Fastboot screen.
I apologize in advance if some of the references/names I'm using are incorrect.
So, I had originally unlocked my Nexus S sometime early this year. When I restart the phone, the "unlocked" lock picture shows up under the "Google" words, and when I go into fastboot mode, the Lock State is Unlocked.
I'm running 2.3.6 right now on the Tmobile version of the phone.
When the phone is on (not in fastboot mode), I can execute ADB commands and the device is recognized. As soon as I go into fastboot it isn't.
I'm running 64bit Win 7, and I have gone through the various threads that have listed this issue, and installed PDA Net drivers and still there is no solution.
In Fastboot mode, while connected to computer under device manager, it shows up under Universal Serial Bus Controllers as an Unknown Device... I'm unable to update any drivers for it, and even when I try to manually update the drivers by going to the PDANet drivers it does not allow it.
When the phone is on in regular mode in device manager it shows up as Android Phone and within that it has a listing called Android Composite ADB Interface.
As mentioned above, when phone on in regular mode everything is detected.
I installed clockwork app from market, assuming that the phone was "rooted" based on the "unlock state" in fastboot mode, but it immediately says that phone needs to be rooted because it was unable to find SuperUser file etc etc.
I've spent the better part of a few days trying to figure this out by checking all sorts of links, but I haven't found a solution. The main issue is that the phone is not being recognized when in fastboot mode when connected by USB. And I'm unable to install the proper drivers for fastboot mode.
Hopefully this makes sense, and someone can provide some insight.
Thanks in advance!
I'm not positive about this but couldn't you adb push the su binary and apk? I don't own the Nexus but I would think since its unlocked you could just push the files. If this would work I would think it's just a temporary solution to allow superuser permission. As I understand it, fastboot is the preferred method for the Nexus.
Sent from my PG06100 using Tapatalk
Did you try a fastboot command like fastboot devices?
Don't know if this applies to you but I had a similar sounding problem when trying to root my Nexus S where everytime I booted into fastboot mode I had an error message at the bottom of the screen saying something like 'fastboot status-fail Invalid command' and so I couldn't use any fastboot functions.
To get around it I used this one-click root . For some reason I got an error message halfway through for whatever reason and it wouldn't complete the root for me but it booted me into fastboot without receiving the error message and then once I was in I went and rooted manually.
The CWM is out of date on that site though (possibly the super-user zip too) so I replaced them with the latest versions and popped it in my dropbox for you, if you wanna try it out.
http://dl.dropbox.com/u/47770734/One-Click-Nexus-S.zip
Edit: just had a little look through the bat script and the initial commands that got me into fastboot properly is (with your phone in debugging mode):
adb start-server
adb reboot bootloader
Click to expand...
Click to collapse
So you could try that first if you wanna go through manually.
Know that you can't run adb command while in fastboot mode. Boot into your CWM and then you can start an adb shell and you'll be able to push all the files you want and execute all the commands you need.
Fastboot mode is for running fastboot indeed. Try 'fastboot devices' while you're in the bootloader and see if devices pop up. If not, you really have to figure out your drivers issue. Maybe remove the device completely from your PC (including driver files) and reinstall it using the PDAnet drivers.
Greetz
After tying and failing to update my sky im-a650s via online self update I'm now stuck at bootloader. The phone can still be detected by sky's online update page but as soon as the activeX application starts to connect to my phone internet explorer crashes. It can still be detected by computer but i cant access it via fastboot and adb to try to install rom. any help would be greatly apreciated.
things i tried to do:
tried to update using different os/computer
tried different key combinations to invoke recovery and fastboot
tried different drivers
Just after updating to lollipop I completly smashed my screen. It doesn't show any usefull information and touch is not working.
Since I'm not in the mood to buy a new screen because I already bought a Note 4, I wanted to pull the data from the phone. It's pin protected but fastboot is still working, adb however is not.
After reading up a bit I found that going into cwm recovery I would still be able to acces adb.
So I with fastboot I booted cwm recovery (fastboot boot recovery.img) only to find that adb still won't find my devices.
Is there any way left to pull the data from my phone? I also have acces to a external keyboard/mouse with a otg cable but that won't seem to work either.
Boot into recovery and with your device plugged into your pc go to device manager. Do you see your device there?
Sent from my Nexus 9 using XDA Free mobile app
In recovery it doesn't show up.
On a normal boot it does, only no files are showing because of the pin lock.
Wiisper said:
In recovery it doesn't show up.
On a normal boot it does, only no files are showing because of the pin lock.
Click to expand...
Click to collapse
Google 15 second adb install xda. It has drivers as well as sets up adb and fastboot on your pc which you'll need if you can get your device detected
Edit, also download the twrp image from here and boot into it fastboot boot twrp.img (use the full name of the twrp image file) cwm sucks. http://techerrata.com/browse/twrp2/hammerhead
Sent from my Nexus 9 using XDA Free mobile app
I think I got it working, I already had adb working but it wouldn't find the correct drivers for the nexus 5.
I tried to update the drivers from google but windows said that it didn't find any correct drivers for the devices so I had to get "naked drivers" from somewhere.
After that it showed up as galaxy nexus adb interface in the device managers and adb was able to find it.
It's now pulling all the data.
Thanks you for your help!
I will report back when it's done pulling.
Wiisper said:
I think I got it working, I already had adb working but it wouldn't find the correct drivers for the nexus 5.
I tried to update the drivers from google but windows said that it didn't find any correct drivers for the devices so I had to get "naked drivers" from somewhere.
After that it showed up as galaxy nexus adb interface in the device managers and adb was able to find it.
It's now pulling all the data.
Thanks you for your help!
I will report back when it's done pulling.
Click to expand...
Click to collapse
Np, glad it seems to be working
Sent from my Nexus 9 using XDA Free mobile app
Okay got all the files from the phone!
Thanks for helping.
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!
Hi
Noob alert here.
I'm trying to flash a custom recovery (twrp) on a very old phone which has its bootloader unlocked. (the phone currently runs android 6.0, yes, that old...)
I read on the forums here that I need to use ADB from windows (Win10 here) in order to flash twrp onto the phone (to replace the stock recovery).
I DLed the neccessary files (platform tools), but it's just a bunch of files with nothing to actually install AFAICT...
MAny tutorials mention that I should just launch a CLI from within the folder containing the tools and then run ADB to flash twrp.
However, I get stuck at < waiting for any device > which, according to other tutorials, isa sign that drivers are not installed for my device in windows.
Some tutorial mention that I should INSTALL ADB (rather than just run it from CLI), so I'm starting to wonder what I am missing here.
- Should I INSTALL ADB? how?
- Should I install drivers for my device? It seems like my device is properly detected by Win10 and I couldn't find any driver to install anywhere.
I'm confused about what's going on.
Could you please help me out here?
Thanks a lot for your advice.
Best,
-a-
OK, I made a little progress I think. I'm not sure my issue is actually related to windows drivers but maybe I'm wrong.
Here's the deal:
When my phone is booted and connected to my PC,
adb device
spits up something : the phone is detected. Now after running
adb reboot bootloader
the phones reboots into bootloader mode (and displays the info that the bootloader is unlocked. But from now on,
adb device
in windows CLI outputs nothing : the phone is no longer detected.
Plus now the phone shows up as an unnknown device (fastboot2.0) in windows device manager. So? Missing driver I guess?
Running windows update found a driver for
Google Android Bootloader Interface
So I guess now it should work
I'll post the results
Thanks a lot
-a-
nope...
No luck
ADB still cannot see my device when in bootloader mode
asheenlevrai said:
nope...
No luck
ADB still cannot see my device when in bootloader mode
Click to expand...
Click to collapse
Actually it works!
Even though
adb devices
would not list anything when the phone wwas in bootloader mode, I was able to flash twrp
problem solved!
In the future some commands in Bootloader Mode require fastboot oppose to ADB.