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
Related
I would have put this in development but I don't have permission yet.
Situation:
I'm using a Chinese tf300t
I tried to root my tablet using the cwm all firmware compatible method. you can find it on youtube as i am not yet allowed to post outside links.
unlocked my tablet. downloaded sdk and all the applications necessary. followed their directions to the letter. I go to cmd to put in the code and when I hit enter after typing: fastboot -i 0x0blah... i get: "waiting on device"
What I think the problem is:
with the sdk fastboot my computer never makes the usb found sound so i thought maybe something with the fastboot driver might be causing a problem so i looked online and someone with the same problem found that a different version of fastboot fixed his waiting problem. I tried what worked for him and now I get a weird stutter version of the usb found sound and i still get a waiting message when i enter the code in cmd. so i think that there might be a problem with the drivers, but my tablet works fine with my comp when its booted up normally.
good news is that I have always been able to reboot device and run normally.
Anybody got any sugestions?
i would like to suggest you to copy these files: fastboot + cwr into 1 new folder, then run fastboot again ( do this while your device is showing ""waiting on device", don't need to reboot it)
So I'm seeing a ton of posts of folks not able to get fastboot to see their devices. I've done some tinkering around and found a set of drivers that work fine for both ADB and Fastboot. (Attached)
Uninstall any ADB drivers you have on your system. Easiest way is to plug your phone in, go into device manager, right click your phone and select uninstall and check the box that says to remove the driver as well.
Then download this package, extract, simply run install.exe as admin. Don't panic, it doesn't do anything visual.
Now plug your phone in and see if adb works, you may need to authorize the computer again on the phone so make sure it's unlocked.
Reboot into bootloader and check if fastboot sees the phone by using
Code:
fastboot devices
If not then go back into device manager and right click on your phone, select update driver, let me select one from a list and you should see "Fastboot interface (Google USB ID)". Select this one.
Check fastboot without unplugging with the same command. Check and see if you can send commands to the phone by using for instance,
Code:
fastboot getvar unlocked
If the command fails, simply plug the phone into a different USB port and the same Google driver should install again and you should be able to send commands to the phone. Alternatively, you can reboot the phone by tapping the battery out and starting it all over again.
Now she chooches.
Lemme know if you're still having problems.
bless up ??
Does this work for sprint variant?
im having problems...damn it i don't get this
---------- Post added at 03:19 PM ---------- Previous post was at 02:42 PM ----------
any help please?
Verizon variant here,
I cannot seem to get this dang V20 in the right mode
(I've seen a bootloader or two in my day):highfive::laugh::silly:
I have used the adb command (several times)
Code:
adb reboot bootloader
to get it into bootloader mode, alas it is to no avail since all the command does is send the phone into "Restart" mode; nor can I get fastboot to recognize it when it is in, what I believe to be , the bootloader for said LG V20 of the
Verizon persuasion!
Suggestions?
You need fastboot, not bootloader... To get it, turn off your phone, plug your LG cable into the computer, ( but not the phone yet) hold the volume down key for 5 seconds then plug it into your cable, do not release the button till your phone boots. It should boot into fastboot... Provided you have turned on USB debugging in developer settings (turn on oem unlock while you are in there too. (this is the way on the tmo V20 at least... If that doesn't work, I would use the dirty Santa guide
Sent from my LG-H918 using Tapatalk
Not sure how I finally got it working for my Verizon variant as I tried like four or five different ways, but someone should definitely make a video.. Perhaps I will since I think visuals are a good aid to go along with written instructions..
Thanks bro works
Very easy
With my t mobile v20
My phone shows as connected in adb devices. I can also get it to reboot bootloader, but once im there.. I cant issue any commands such as fastboot oem device-id. It gives me the dreaded waitng for any device.
can't manage to make this work for H990DS, i don't get the usual authorization window to the computer, only get the window to choose which USB mode (battery charge, file transfer, so on...) I'm trying to get adb to work to activate agressive Doze on Greenify app, any help?
Thanks
Vexamus said:
So I'm seeing a ton of posts of folks not able to get fastboot to see their devices. I've done some tinkering around and found a set of drivers that work fine for both ADB and Fastboot. (Attached)
Uninstall any ADB drivers you have on your system. Easiest way is to plug your phone in, go into device manager, right click your phone and select uninstall and check the box that says to remove the driver as well.
Then download this package, extract, simply run install.exe as admin. Don't panic, it doesn't do anything visual.
Now plug your phone in and see if adb works, you may need to authorize the computer again on the phone so make sure it's unlocked.
Reboot into bootloader and check if fastboot sees the phone by using
Code:
fastboot devices
If not then go back into device manager and right click on your phone, select update driver, let me select one from a list and you should see "Fastboot interface (Google USB ID)". Select this one.
Check fastboot without unplugging with the same command. Check and see if you can send commands to the phone by using for instance,
Code:
fastboot getvar unlocked
If the command fails, simply plug the phone into a different USB port and the same Google driver should install again and you should be able to send commands to the phone. Alternatively, you can reboot the phone by tapping the battery out and starting it all over again.
Now she chooches.
Lemme know if you're still having problems.
Click to expand...
Click to collapse
Perfect and Easy!!!! :good:
thx..ur ma angel
I can't find my phone in Device Manager.
this is great and works like a charm! thanks!
Thanks!
I'm running into an odd issue with using fastboot. For some reason it's not detecting any devices.
I installed, and reinstalled all the drivers (and everything installs and displays correctly in Device Manager)
ADB works properly and displays my device
I have USB Debugging enabled in developer mode
I tried different USB-microusb cables (same thing)
I tried installing PDAnet --> no difference
I also tried downloading the SDK and running the platform tools from there. Once again ADB works fine, but fastboot is just <waiting for any device>
Any thoughts?
As a side note, have a SM-G930T phone. I was able to get TWRP on my phone before, and I'm trying to get it again and I can't seem to recall how I have done it. I do remember I unlocked the bootloader through a website, but I can't remember the steps. Perhaps someone can point me to the right direction. Of course, in order to unlock the bootloader I would need to get fastboot to work, so this is what I'm trying to take care of first.
So here's the background: I have a OnePlus 6, which I had rooted previously. I accidentally updated it without first patching the boot image, so it's not rooted now.
In an attempt to root it again, I need to use fastboot. However, whenever I use
adb reboot bootloader
it reboots the phone to fastboot mode, as expected, but then
fastboot devices
displays nothing. I find this extremely strange, because I have used fastboot commands before on both my windows machine and on my Linux machine (though I recently switched distros and have a new installation on there, so it may be missing some driver or something).
I have tried looking for any necessary drivers (I saw that sometimes usb drivers are different from fastboot drivers, but I don't know if that's the case regarding OnePlus) but after installing everything I found, it still doesn't work.
I have also tried running adb as root (on Linux) and as administrator (on Windows) but neither worked.
I tried to use Tool All In One to root it for me, but it seemed to run into the same problem. It wouldn't detect the phone in fastboot mode.
I'm absolutely baffled as to why this may be; Anyone know why this happens or what I may do to fix it?
I had the similar issue last week when adb command of fastboot devices would not identify the device. I used the fastboot ROM method to reflash the stock rom and everything worked fine afterwards including fastboot devices command identifying the device correctly. Needless to say, it would delete everything on your phone. Here is the link:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Good luck!!
Fastboot version
Update your fastboot, maybe it's an old version.
Also check your device manager and see if the phone is listed there. Sometimes it's necessary to disable driver signature check in Windows 10. Also install the driver before you use your commands - some users reported that for some reason the driver or connection is lost after windows reboot.
A) Check fastboot drivers/reinstall them (adb and fastboot use different drivers). You might want to check if there are unknown devices in your Windows device manager, or the name of the device once fastboot mode is engaged and you plug the cable
B) Plug it in another USB port (less likely to be the problem, since ADB actually works)
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.