My device is a One Plus One. I've installed an ADB driver from here: adbdriver (some site I've searched up on google) (Is this even safe? I've never seen anyone use this link before or maybe it's new. It's not a virus is it?)
So once I've installed it, I've typed all commands such as adb while my device is turned on but then when it gets to where I have to press my powerbutton+volume down and then go into the recovery screen, I see "Cyanogen Recovery" or whatever but that's what it says. Suddenly on my computer, the ADB device disappears altogether and I cannot see my One Plus One storage anymore (it's connected and even If I unconnect and reconnect it's still the same). I believe I've unlocked my phone already before so is this why? I just want to make sure and type fastboot oem device-info but when I type that nothing comes up. I've been trying to solve this and I don't know what to do anymore... Is it because I've already unlocked my device (but even I'm not sure if it's still unlocked and that's why I'm trying to confirm it by typing "fastboot oem device-info" which doesn't even work. Help please!
xMTOOLO said:
My device is a One Plus One. I've installed an ADB driver from here: adbdriver (some site I've searched up on google) (Is this even safe? I've never seen anyone use this link before or maybe it's new. It's not a virus is it?)
So once I've installed it, I've typed all commands such as adb while my device is turned on but then when it gets to where I have to press my powerbutton+volume down and then go into the recovery screen, I see "Cyanogen Recovery" or whatever but that's what it says. Suddenly on my computer, the ADB device disappears altogether and I cannot see my One Plus One storage anymore (it's connected and even If I unconnect and reconnect it's still the same). I believe I've unlocked my phone already before so is this why? I just want to make sure and type fastboot oem device-info but when I type that nothing comes up. I've been trying to solve this and I don't know what to do anymore... Is it because I've already unlocked my device (but even I'm not sure if it's still unlocked and that's why I'm trying to confirm it by typing "fastboot oem device-info" which doesn't even work. Help please!
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. To get you the expert help you need, I'm going to move this thread to your specific device Q&A forum.
Good luck!
You need to boot into bootloader by pressing volume up + power.
Then you can use "fastboot devices" to see if your OPO is being recognised.
"fastboot oem device-info" only works when you boot to bootloader
ADB is not fastboot btw.
http://www.androidcentral.com/android-z-what-fastboot
ADB does only work when your phone is booted to the Android system and USB-Debugging is enabled
http://www.androidcentral.com/what-adb
Related
Hi,
I'm kind of a noob at this rooting stuff. I've looked ariund, done my research and everything but it never seems to go smoothly??..
I think the main problem is with the drivers. After following instructions the android drivers still said 'Android 1.0'. So I installed Pda net and then I got 'Android ADB Interface' drivers. Soo the thing is, after searching for 'adb devices' in cmd prompt, It says 'list of devices' but there's nothing in the list....?
For some reason it won't do any commands like 'adb reboot bootloader' or 'fastboot oem lock'. It says not found. I have installed all the sdk and packages...
Would really appreciate some help from you guys. I didn't think rooting would be so complex??...
Thanks
can you post screenshot??
Ok for some reason, after starting the cmd again today and typing adb devices, it has listed my device. But when I type 'fastboot oem lock' (because my bootloader is already unlocked) it says not found as shown in the screenshot.
Am I doing something stupid??...
70 views?... cant anyone help ... please..
soulja786 said:
70 views?... cant anyone help ... please..
Click to expand...
Click to collapse
If adb devices lists your device you're not in the boot loader, the ONLY place fastboot will recognize your device and function or you have a driver issue. You're either in recovery or booted up. Reboot into the boot loader to use fastboot.
If you get into the boot loader and fastboot still doesn't show your device it's a driver issue. Update the driver manually and point it to the SDK USB driver provided with the SDK.
For reference....
Booted into boot loader:
Fastboot OK
ADB NO
Recovery / Fully booted
Fastboot NO
ADB OK
Hi guys,
I really do think this is a driver issue... any idea on how to solve it? I do have PDA Net installed... ?
@krohnjw ... could you please clarify.. Im a bit lost.
Thanks!
Did you try something like oneclickroot?
http://forum.xda-developers.com/showthread.php?t=1138755
Well I also had a lot of issues trying to root my i9020t so let me try to help..
Phone will be recognized with ADB when u select enable debug on developer options. You ll see "Android ADB Interface" on SYS DRV.
On other hand , when U start phone on fasboot mode, it should install something like "Android Bootloader Interface " , if U keep seeing "Android ADB Interface" , its wrong, but took some time to realize that.
That happened to me when I was using WinXP x32 to root my phone, ironically thinking it would be more compatible an less prone to bugs... When done it on W7 x64 , my fastboot driver was discovered correctly (Android bootloader Interface) using x64 PDA drivers, and all went good then!
Hope this may help!
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
I have a Nexus 5, returned to factory specifications (many times) with backup & restore inhibited. I am trying the “very simple” process of unlocking it, without any success. My problem is repeated many times on the web, Fastboot does not work, but ADB does.
I run the following command:
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices
List of devices attached
0315c2d60935c160 device
Then I run the following command:
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot devices
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
ADB sees the phone; Fastboot does not.
The solution is well documented on the web: Install new drivers. I have been installing drivers from just about everywhere for the last week without success. With the phone connected, I get this from Device Manager:
Computer
Android Device
Android Composite ADB Interface
The driver information is as follows:
Driver Provider: Google, Inc.
Driver Date: 7/9/2013
Driver Version: 8.0.0.0
Driver Signer: Google, Inc.
Driver Details:
Driver Files:
C:\Windows\System32\Drivers\Winsub.sys (File Version 6.2.9200.16384(Win8_rtm.120725-1247))
C:\Windows\System32\WdfcoInstaller01009.dll(File Version 1.9.7600.16385 (Win7_rtm.090713-1255)
C:\Windows\System32\WinUSBCoInstaller2.dll (File Version 6.1.7600.16385 (win7_rtm.090713-1255))
I am running a Dell XPS-17 I7 laptop with Windows 8 (not 8.1) 64 bit
If I could find a way to unlock without using Fastboot, that would probably be a good solution, but I can’t. And I have absolutely no success at getting Fastboot to work.
I do notice that the Device Manager lists Android Composite ADB interface (ADB works) but noting about a Fastboot interface. Does that mean anything?
Please help I am at my wit’s end.
For what it is worth, I did read all the tutorials here, and the only thing I could figure out was if I have the right drivers everything works fine. I also reviewed the posts here, including "Diagnosing USB Driver and ADB issues in Windows," which discusses ADB (which I have no problem with)
this article helped me out a bunch. http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode/
you'll have to edit the "android_winusb.inf" with the correct hardware id.
in Device Manager make sure you go to "Android Device" > "Android Composite ADB Interface" go to Properties. on the Details tab and then click on the drop down box and select "hardware ids" you might see 2 ids there. i believe the one you'll need is the bottom one. if you only have one. thats fine too.
so, read the article. grab your hardware id and edit your driver. see if it works. you may have to reboot after you edit the driver. hope this works for you.
krdu said:
I have a Nexus 5, returned to factory specifications (many times) with backup & restore inhibited. I am trying the “very simple” process of unlocking it, without any success. My problem is repeated many times on the web, Fastboot does not work, but ADB does.
I run the following command:
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices
List of devices attached
0315c2d60935c160 device
Then I run the following command:
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot devices
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
ADB sees the phone; Fastboot does not.
Click to expand...
Click to collapse
OK, please don't be offended, but I have to ask a really dumb question. You aren't running the "fastboot devices" command while in recovery, right? I read the above twice and didn't see where you booted into bootloader after running the "adb devices" command. Unless I'm missing something, fastboot won't find any devices unless you are in the bootloader.
Sounds like you need to boot your phone into fastboot mode. Power off the phone and hold volume down and hit the power button.
Then the fastboot devices command should work and you should be able to unlock the boot-loader then. Unlocking the boot-loader will wipe your phone just so you know.
erikivy said:
OK, please don't be offended, but I have to ask a really dumb question. You aren't running the "fastboot devices" command while in recovery, right? I read the above twice and didn't see where you booted into bootloader after running the "adb devices" command. Unless I'm missing something, fastboot won't find any devices unless you are in the bootloader.
Click to expand...
Click to collapse
Actually, the answer to that question is "Yes, and no." I was not aware that Fastboot only worked in the bootloader, but I could never get it to work there either. However, when I copied the previously posted listings I was not in the bootloader, I was in normal booted mode.
I then went and tried it in the bootloader, to copy listings to post, and here's what I got!
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices (In normal Mode)
List of devices attached
0315c2d60935c160 device
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb reboot bootloader (rebooted to Bootloader)
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices
List of devices attached
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot devices
0315c2d60935c160 fastboot
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot oem unlock
...
OKAY [ 41.215s]
finished. total time: 41.215s
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
As you can see it unlocked the phone but I have absolutely no clue why it unlocked this time and never did before. I hope to God I never have to unlock it again.
Also, it appears that in the bootloader, ADT is NOT working but Fastboot is! (now)
You realize that the two command line interfaces (ADB and fastboot) don't work in the same state, right? ADB is for use in recovery and while booted, whereas fastboot only works in bootloader. It sounds to me like everything is working exactly as it should.
I'm no expert or anything, but I always assumed that they were two different ways to interact with your device while it is in different states. If I'm mistaken, someone please correct me.
krdu said:
Actually, the answer to that question is "Yes, and no." I was not aware that Fastboot only worked in the bootloader, but I could never get it to work there either. However, when I copied the previously posted listings I was not in the bootloader, I was in normal booted mode.
I then went and tried it in the bootloader, to copy listings to post, and here's what I got!
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices (In normal Mode)
List of devices attached
0315c2d60935c160 device
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb reboot bootloader (rebooted to Bootloader)
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices
List of devices attached
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot devices
0315c2d60935c160 fastboot
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot oem unlock
...
OKAY [ 41.215s]
finished. total time: 41.215s
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
As you can see it unlocked the phone but I have absolutely no clue why it unlocked this time and never did before. I hope to God I never have to unlock it again.
Also, it appears that in the bootloader, ADT is NOT working but Fastboot is! (now)
Click to expand...
Click to collapse
ADB is used in android and the recovery.
Fastboot is used only in the bootloader.
Hi, I'm trying to unlock my phone so I can install Kali Linux on my A466BG. I've read a lot on the web but came to a problem. I've got Android SDK on my PC and installed platform-tools. My device shows up after entering "adb devices." I've enabled developer mode and usb debugging and OEM unlocking. My problem is...I can't unlock the bootloader and use fastboot. After pressing power and up volume I get into the menu (and I actually reset my phone to factory settings so I'll have more space) but I can't find bootloader. My phone shows up fine on my PC and under devices, but when I switch to the other menu (with reset options) it doesn't show up anymore. Not even under "adb devices." I tried entering "adb reboot-bootloader" but it just restarts and goes to the normal android phone screen. I tried "fastboot -i 0x1bbb oem device-info" and it says "waiting for device." I'm not sure how to boot into fastboot and unlock my bootloader. Or why my phone doesn't show up on my PC after pressing power and up volume. Please reply with instructions. Thank you
Hi, me again. I found a video on YouTube on how to install Kali Nethunter on Android phones. I got it and now I'm installing Metasploit. It's just the command line but that should work. Check You Tube on "Nethunter without root" if you want to know. Thanks
I'm back...Not satisfied with Nethunter on Termux. I would like to know how to root the phone and install Kali. Can anyone look at the above question and reply with how to root my Alcatel A466BG? I'll check back tomorrow. Thanks in advance!
Hopefully someone here can help me through my problem,
Device Details: BLU G60/BLU VIVO X6
Android 9/Pie
OEM Unlocking: Allowed
USB Debugging: Enabled
Hey, I'm pretty new to this way of customizing my phone (adb, root, roms etc), and I'm trying to root my phone with Magisk. I have a patched boot.img, my bootloader is allowed to be unlocked and I'm doing exactly what the root guide says (https://www.mobilewithdrivers.com/magisk-root/blu-g60-64gb-3gb-ram) but it wont work, I keep getting different errors and I see all my fellow droid users so happy with their rooted devices, I want to root mine too. So what I'm asking is; Can someone with an actual brain (Mine wont work) to try and help me out or walk me through step-by-step?
Thanks for reading!
Some of the issues I have:
"adb reboot booter" and "fastboot reboot bootloader" both reboot the device but in the top left corner it says "fastboot mode" and just freezes, when I do any command it just says "device null" but when I reconnect the USB cable, it just powers off.
"fastboot flashing unlock" results in "FAILED (remote: Not implemet.)" Yes, spelt like that.
"fastboot oem unlock" says, unkown cmd...
Wrong driver in use. Use the one provided by BLU suitable to your phone.
i couldnt find any drivers for the exact device, only google ones...
any ideas?
If you have a mac, you could try that. They usually don't require drivers.