I have all drivers, pc is recognizing my phone and when I type adb device it's here. But when I boot it to bootloader and try fastboot devices it's not there and when I type any commant it says "< waiting for device >". I tried reinstalling drivers, different usb ports, cables and everything I saw on the internet but nothing helped at all. I tried reinstalling fastboot and restarting my pc but that didn't work either.
Fastboot? On a j5?
garylawwd said:
Fastboot? On a j5?
Click to expand...
Click to collapse
It's on P9 lite
VectoDesigns said:
It's on P9 lite
Click to expand...
Click to collapse
This is galaxy j5 questions and answers though.
But anyway you do have OEM unlock and USB debugging enabled in developer options yes?
Related
guys I'm in a bad situation, phone is without OS and I can only access to recovery or bootloader, I have a twrp installed and I can't access to an USB otg (simple usb doesn't even blink like they are not working, If I connect an hdd it doesn't recognize it but gives it power) and I can't access to the phone as MTP or with adb devices or adb sideload. Even on bootloader mode device isn't showed when I try the command "fastboot devices" and it says "download mode = DISABLED".
so I only have access to twrp with those limitations, I need a big help, phone is with BTL unlocked and with expired warranty.
thanks in advance
parodiniccolo said:
guys I'm in a bad situation, phone is without OS and I can only access to recovery or bootloader, I have a twrp installed and I can't access to an USB otg (simple usb doesn't even blink like they are not working, If I connect an hdd it doesn't recognize it but gives it power) and I can't access to the phone as MTP or with adb devices or adb sideload. Even on bootloader mode device isn't showed when I try the command "fastboot devices" and it says "download mode = DISABLED".so I only have access to twrp with those limitations, I need a big help, phone is with BTL unlocked and with expired warranty.
thanks in advance
Click to expand...
Click to collapse
Download mode=disabled is the default (normal) displayed in bootloader mode. You seem to infer that is what fastboot returned when you typed devices? MTP works in TWRP automatically when it loads. Sounds like you may have a PC driver/cable issue. When you plug the device into your PC, how is it recognized?
v12xke said:
Download mode=disabled is the default (normal) displayed in bootloader mode. You seem to infer that is what fastboot returned when you typed devices? MTP works in TWRP automatically when it loads. Sounds like you may have a PC driver/cable issue. When you plug the device into your PC, how is it recognized?
Click to expand...
Click to collapse
I'm on mac so I don't have any driver issues and other phones works fine with mtp in TWRP
Up please
parodiniccolo said:
I'm on mac so I don't have any driver issues and other phones works fine with mtp in TWRP
Click to expand...
Click to collapse
You are using OSX, right? Fastboot commands should start with ./ before each command. For example: ./fastboot devices, or ./fastboot flash, or ./fastboot reboot bootloader. Same applies for adb commands. If you are already familiar with flashing images, read my post below about OSX and fastboot.
Do not click into the thread because it is for the Nexus 5X new users guide.
Edit: Whoops! Initially shared the wrong link above. Follow this link instead:
https://forum.xda-developers.com/showpost.php?p=68758793&postcount=3
Sent from my Nexus 5X using Tapatalk
So i decided to root my A1. But fastboot isn't working for me.
Tried with previous adb files.
Adb works properly.
But when device is rebooted into fastboot mode. Fastboot isn't and to talk to it.
Updated adb and fastboot (sdk tools and even in AIO tool)
Just adb works.
Reboot to fastboot and my device is not detected.
Disabled driver signature enforcement in windows 10
OEM unlocking allowed.
Usb debugging on.
Tried multiple times.
Nothing seems to work.
Maybe driver problem but since adb works i don't think that's the problem and i have installed it again from AIO Toolkit.
Try different usb cable or usb 2.0 port
I had similar issue, fastboot was detected but haven't been able to do any command. So when the phone was powered on with selected usb to transfer files, in device manager the phone was listed as "Android phone - Android Composite ADB Interface", I updated the driver to "ADB Interface", rebooted in bootloader and was able to communicate through fastboot.
bpodnar said:
Try different usb cable or usb 2.0 port
Click to expand...
Click to collapse
I would if i could get my hands on one. But i can't not for few more weeks.
Adb is working fine. File transfer is working fine. Charging is working fine.
So I don't think cable is at fault
alkesh95 said:
So i decided to root my A1. But fastboot isn't working for me.
Tried with previous adb files.
Adb works properly.
But when device is rebooted into fastboot mode. Fastboot isn't and to talk to it.
Updated adb and fastboot (sdk tools and even in AIO tool)
Just adb works.
Reboot to fastboot and my device is not detected.
Disabled driver signature enforcement in windows 10
OEM unlocking allowed.
Usb debugging on.
Tried multiple times.
Nothing seems to work.
Maybe driver problem but since adb works i don't think that's the problem and i have installed it again from AIO Toolkit.
Click to expand...
Click to collapse
I hope drivers are up to date.
alkesh95 said:
I would if i could get my hands on one. But i can't not for few more weeks.
Adb is working fine. File transfer is working fine. Charging is working fine.
So I don't think cable is at fault
Click to expand...
Click to collapse
Did u tested this? Reboot to fastboot mod and connect mobile to pc. then right click my computer then device manager. Then check for A1 port. Update /install driver Automatically from internet. May be it will help , may be not.
ADB drivers are different than fastboot. If you can detect with ADB and not fastboot, I would suspect you have a driver problem. Boot into fastboot, then check device manager for your device. It might not have any drivers installed and be an unrecognized device, or it could have incorrect drivers installed. My device needed fastboot drivers, I had the same problem as you.
Thanks all of you. Fastboot driver was the issue.
alkesh95 said:
Thanks all of you. Fastboot driver was the issue.
Click to expand...
Click to collapse
I have the same problem, can you send me the fastboot driver please?
vu2pmc said:
I have the same problem, can you send me the fastboot driver please?
Click to expand...
Click to collapse
Follow the step. Windows will download correct driver automatically
Hi there,
i'd Like to flash the Ressurection Remix Oreo Rom, but i don't get it to unlock the bootloader. I'm on Stock A2017GV1.2.0B10 Nougat. TWRP and Backups are done, but when i try to unlock the Bootloader i geht this message in cmd:
adb: error: connect failed: no devices/emulators found
Tried with Zadigs Drivers, ADB divers are installed and it is showed as QS_Bulk.
Are there still some drivers missing or what am I doing wrong there???
Did you enable USB Debugging on your phone?
Victor13f said:
Did you enable USB Debugging on your phone?
Click to expand...
Click to collapse
Yes, i have OEM unlock and USB Debugging enabled. Dont understand why this is not working at all. Tried it many times, but every Try I get this message in the CMd. Sideload isn't working too...
Have you installed the Google USB drivers and checked in Device manager if everything is working okay? Here's a link to a guide: https://www.drivereasy.com/knowledge/solved-adb-device-not-found-error-on-windows/
HeikoNote3 said:
Yes, i have OEM unlock and USB Debugging enabled. Dont understand why this is not working at all. Tried it many times, but every Try I get this message in the CMd. Sideload isn't working too...
Click to expand...
Click to collapse
Just use the EDL Tool from @djkuz, install it, put your phone into EDL mode and unlock.
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
raystef66 said:
Just use the EDL Tool from @djkuz, install it, put your phone into EDL mode and unlock.
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
Click to expand...
Click to collapse
So, Tried this one too. Doesn't work, phone isn't found, error adb interface not found...
HeikoNote3 said:
So, Tried this one too. Doesn't work, phone isn't found, error adb interface not found...
Click to expand...
Click to collapse
Uninstall all drivers you see relating to your phone (adb, usb...)
Try install : http://adbdriver.com/downloads/
And https://androidfilehost.com/?fid=24588232905723896
And see if you can perform with the EDL Tool again or adb
raystef66 said:
Uninstall all drivers you see relating to your phone (adb, usb...)
Try install : http://adbdriver.com/downloads/
And https://androidfilehost.com/?fid=24588232905723896
And see if you can perform with the EDL Tool again or adb
Click to expand...
Click to collapse
Installed the ADB Drivers but in EDL tool the Phone is not recognised. Dont know what could the Problem...
HeikoNote3 said:
Installed the ADB Drivers but in EDL tool the Phone is not recognised. Dont know what could the Problem...
Click to expand...
Click to collapse
First boot into twrp, connect your phone, run the EDL Tool. Normaly the tool should reboot itself into EDL mode
Or try : run EDL tool, instead of power off phone, hold vol down+power, connect usb, just do the same by holding the 3 buttons ( i did that once when my phone was in a state of 'shock' and the 2 button way didn't work)
Btw, did you install the 2 drivers i gave you ?
raystef66 said:
First boot into twrp, connect your phone, run the EDL Tool. Normaly the tool should reboot itself into EDL mode
Or try : run EDL tool, instead of power off phone, hold vol down+power, connect usb, just do the same by holding the 3 buttons ( i did that once when my phone was in a state of 'shock' and the 2 button way didn't work)
Btw, did you install the 2 drivers i gave you ?
Click to expand...
Click to collapse
Yes they're installed. I'm wondering that edl tool shows first ZTE ADB handset etc. And after boot into edl mode it shows no ADB interface... With axon7tool I can choose unlock Bootloader, then MI flash starts and then I don't know the files to flash for an unlock...
HeikoNote3 said:
Yes they're installed. I'm wondering that edl tool shows first ZTE ADB handset etc. And after boot into edl mode it shows no ADB interface... With axon7tool I can choose unlock Bootloader, then MI flash starts and then I don't know the files to flash for an unlock...
Click to expand...
Click to collapse
MiFlash? Where did you read that you had to use MiFlash? ?
You need to use EDL Tool
Edit: Okay, I think I got it. You thought "EDL Tool" was actually axon7toolkit. Well, it isn't. Axon7toolkit, axon7tool, and EDL Tool are 3 different things
Choose an username... said:
MiFlash? Where did you read that you had to use MiFlash?
You need to use EDL Tool
Edit: Okay, I think I got it. You thought "EDL Tool" was actually axon7toolkit. Well, it isn't. Axon7toolkit, axon7tool, and EDL Tool are 3 different things
Click to expand...
Click to collapse
OK, then which tool should I prefer now? In EDL tool I was on a good way to unlock the Bootloader, but when I choose Yes, the unlock begins with load programmer something and stucks until I reboot EDL mode. Then it gives me an error message with: your device could be in Sahara mode. I don't understand anything anymore. Tried every driver, every tool but nothing will work. That drives me crazy...
HeikoNote3 said:
OK, then which tool should I prefer now? In EDL tool I was on a good way to unlock the Bootloader, but when I choose Yes, the unlock begins with load programmer something and stucks until I reboot EDL mode. Then it gives me an error message with: your device could be in Sahara mode. I don't understand anything anymore. Tried every driver, every tool but nothing will work. That drives me crazy...
Click to expand...
Click to collapse
Did you enable OEM unlock and USB debugging?
If you did and it still does that error, just use the manual method and follow Controllerboy's guide. That one uses axon7tool, which is much more finicky and ran by commands, but it works
Thanks for all Tipps. Finally did it. Running RR Oreo!
i'm trying to unlock my bootloader to be able to root by device with magisk but my device can't be recognize in fastboot mode, any idea of what's happening?
What exactly have you done? More information is necessary to help you.
Madd Vybzz said:
i'm trying to unlock my bootloader to be able to root by device with magisk but my device can't be recognize in fastboot mode, any idea of what's happening?
Click to expand...
Click to collapse
Sounds like a simple drivers issue
https://forum.xda-developers.com/es...nofficial-usb-drivers-essential-ph-1-t3678231
Sent from my Gemini 4G using Tapatalk
Have you enabled developer options, debugging, and authorized the computer you're plugging your phone into?
You are using an out of date version of fastboot.
https://developer.android.com/studio/releases/platform-tools
To use your version, you'd need to manually specify the usb vid: fastboot -i 0x2e17
Just bought a used Pixel 4 to try and flash lineage 17.1 but can't get OEM unlocking to actually work. The enable switch is in the on position and adb recognizes the device but when I try to enter fastboot either by adb reboot bootloader or volume down + power on, the device status comes up in green text "locked." The phone is a G020I and came to me running android 11 with a build number RP1A.20005.004. Is this too new of a phone and wont be able to be flashed? From what I understand, if the bootloader stays locked, I can't even flash a factory image of android 10, correct?
You have to unlock bootloader using fastboot command from pc...
gpvecchi said:
You have to unlock bootloader using fastboot command from pc...
Click to expand...
Click to collapse
Fastboot commands wont work. adb commands will but as soon as I try adb reboot bootloader to get to the point where I can enter fastboot flashing unlock, I get the result in the pics below.
You need to install Google usb driver to use Fastboot
2WildFirE said:
You need to install Google usb driver to use Fastboot
Click to expand...
Click to collapse
Ok, in trying to do that, I get the message from windows that their driver is the most up to date and won't let me install from the file I try to choose. See the pics below.
I had the same issue, updating the USB drivers rc13 did the trick.
GTOJim said:
I had the same issue, updating the USB drivers rc13 did the trick.
Click to expand...
Click to collapse
LInk for that update?
Here you go: https://www.thecustomdroid.com/google-android-usb-drivers/
Finally got it. Windows had to recognize it as a generic device in order to force a driver. If it saw it as Pixel 4 it would stop. Now that I have lineage flashed on it, just need to figure out how to get mms to work. Apparently that is a common problem too.