Database Users

Fastboot problem

Hi!
I'm having a weird problem with this device, when i connect IT with USB debugging on and permission for OEM unlock, it shows from the prompt that the device is detected and so i can easily reboot it in fastboot mode. But after this point i'm getting stucked, the device isnt recognized and if i try to do any action it just get stucked in waiting for device screen. Any help? Thank You in andvance

Phone isnt being recognised by fastboot

I have adb and the needed drivers installed on my Windows PC, my phone is a Huawei P9 Lite and im trying to unlock the bootloader but the phone isnt beening detected when its in the fastboot mode. I have looked on XDA forums and nothing has helped so far. When i enter "fastboot devices" into CMD nothing comes up but when i enter "adb devices" my phone comes up so its not being recognised by fastboot. I put my phone into fastboot mode and tried "fastboot devices" and still nothing came up. I need to flash a ROM on it because the EMUI skin is really bad, could someone give me sugestions for a working ROM (I heard that using Cyanogenmod will remove a lot of features like camera and fingerprint)

I know, it's basic, but ( from XDA Forum )
Now we must activate the OEM Unlock option on your phone, go under Settings/Developer Options and tick the "Enable OEM unlock" option. In the same menu check if USB Debbuging mode is enabled, if not do it !
And for the rom, I don't like EMUI very much but Stock Rom with Nova Launcher give a good result

Double check drivers, setting, USB cable etc (Hisuite installed on PC and phone).
On the phone check if USB Debugging and OEM Unlock is cheeked and if USB debugging authorized is accepted.
If the phone is ok, untuched, is no reason for what you say...

sonneper said:
I know, it's basic, but ( from XDA Forum )
Now we must activate the OEM Unlock option on your phone, go under Settings/Developer Options and tick the "Enable OEM unlock" option. In the same menu check if USB Debbuging mode is enabled, if not do it !
And for the rom, I don't like EMUI very much but Stock Rom with Nova Launcher give a good result
Click to expand...
Click to collapse
OK I did that now and when im in fastboot mode the "FRP Unlock" text is now red, before it was green. I wrote "fastboot oem unlock CODETHINGHERE" and its still waiting for device. "fastboot devices" still shows nothing.

I'm not sure I did iy by the same way, I've just follow EXACTLY, step by step this how to :
http://forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701
I did it two times ,the only issu I had was because I forgot OEM unlock.
Read carrefuly the how to from the link, you 'll find what you need

That's most likely because you are on Windows 8.1+. Use the file from this thread - download, remove ".txt" and double-click. Don't worry about the KB update, with 99.99% certainty, you have it installed already. The .reg file will change something in your Windows Registry (no worries, it's safe). Reboot your PC and your phone should be detected by your PC after running fastboot commands Let us know if it helped!

Hey man probably you need to installa manual driver from pc. Connect you phone (in fastboot & and rescue mode) to the PC, than click with right button on Computer ( icon on desktop) and then click on "management" form here try to understand this image: http://prnt.sc/czanve
It's in italian made by me for a friend, I think you can easly understand just look images.
PS. for the moment I think you can find that driver in "kedacom usb device" and not "Android phone" as in picture

Still doesnt work

Windows 10 won't Recognize my Phone in Fastboot Mode but ADB Is working

Hey Guys,
i tried to Root my Moto E4 but Unfortunally i cant get Fastboot to work under Windows 10 Home 64 Bit on Both my Notebook and my PC. I installed The Motorola Device Manager (Since it comes with drivers) and installed ADB and Fastboot but once i Reboot into Fastboot Mode it wont Recognize it for flashing. The CMD Just Says Waiting for Device. I have expierience with Rooting other Phones but i never had this much Trouble getting Fastboot to work properly. Would be awesome if u could show me a Solution to this since i really want a Custom Rom.
Gesendet von meinem SM-A300FU mit Tapatalk

There's no trick, it just works. I have Windows 10 64 bit as well and no issues. Maybe you need to update your platform tools (adb and fastboot). Using old ones can be a problem.
What command are you issuing? Just fastboot devices ?
Make sure you're not using a USB 3.0 port on your computer.

madbat99 said:
There's no trick, it just works. I have Windows 10 64 bit as well and no issues. Maybe you need to update your platform tools (adb and fastboot). Using old ones can be a problem.
What command are you issuing? Just fastboot devices ?
Make sure you're not using a USB 3.0 port on your computer.
Click to expand...
Click to collapse
Few other thoughts:
- try a different cable; a cable that works for charging and adb communication may not work with fastboot
- avoid external hubs if possible
- be sure to reboot both devices after switching drivers if communication isn't immediately established

Marc_Xperia said:
Hey Guys,
i tried to Root my Moto E4 but Unfortunally i cant get Fastboot to work under Windows 10 Home 64 Bit on Both my Notebook and my PC. I installed The Motorola Device Manager (Since it comes with drivers) and installed ADB and Fastboot but once i Reboot into Fastboot Mode it wont Recognize it for flashing. The CMD Just Says Waiting for Device. I have expierience with Rooting other Phones but i never had this much Trouble getting Fastboot to work properly. Would be awesome if u could show me a Solution to this since i really want a Custom Rom.
Gesendet von meinem SM-A300FU mit Tapatalk
Click to expand...
Click to collapse
When you say you booted to fastboot what do you mean ?
Did use adb and your phone was recognized and then you issued adb command or what method are you using ....
You need to ensure you establish USB debugging connection first & grant authorization ...once link with authorization has been established run adb ...from adb check if recognized run command to boot to fastboot
So start from the top && go down
ARE YOU CERTAIN YOU USED CORRECT METHOD TO TURN OFF DRIVER VERIFICATION ON WINDOWS 10 && YOUR DRIVER ACTUALLY INSTALLED
Last noteworthy point ... when unlocking my motoE4 I had to boot to bootloader ONLY to use fastboot NOT "FASTBOOT"
Hold power + volume button

Excellent troubleshooting from our community. OP has not come back yet to confirm, ask another question, or simply a thanks. (Maybe he got it) Hopefully he gets it sorted.
Maybe the junior members underestimate just how quick and helpful our little community can be.

@Marc_Xperia Do not forget to install AndroidBootloaderInterface Driver Software. *android_winusb.inf*

Thats what my Problem is. I installed the Latest Android Studio, i have gone to SDK Manager. Installed the Android 7.1 Files and USB Drivers and this happens everytime i want to unlock my BL. And yes i disabled Driver Signing on Windows 10. I call it Fastboot Mode since im Used to Xperias so im Sorry i confused anyone.

Marc_Xperia said:
Thats what my Problem is. I installed the Latest Android Studio, i have gone to SDK Manager. Installed the Android 7.1 Files and USB Drivers and this happens everytime i want to unlock my BL. And yes i disabled Driver Signing on Windows 10. I call it Fastboot Mode since im Used to Xperias so im Sorry i confused anyone.
Click to expand...
Click to collapse
When you authorize your adb connection do you tick or select always allow connections from this device ...the fact that your device is listed as *unauthorised* is a clear indication in your previous attempts you didn't authorize to "allways allow connections" from this device
#result _when you reboot authorization is revoked
Enter bootloader mode the old skool way using your buttons..
# MAKE SURE TO SELECT "ALLOW OEM UNLOCK OPTION IN DEVELOPS settings
1.AUTHORIZE TO "ALWAYS ALLOW CONNECTIONS FROM THIS DEVICE"
2.enter bootloader using hardware keys
3.plug in usb
4.run fastboot devices to force fastboot to start deamon ...
5.once fastboot can see your device run oem unlock
6.DO NOT USE USB 3 port so try different USB ports on pc
7. Alternatively use a live USB of Ubuntu minimal to do the job
--- doesn't seem like driver problem if adb can see your device
See if that works

KevMetal said:
When you authorize your adb connection do you tick or select always allow connections from this device ...the fact that your device is listed as *unauthorised* is a clear indication in your previous attempts you didn't authorize to "allways allow connections" from this device
#result _when you reboot authorization is revoked
Enter bootloader mode the old skool way using your buttons..
# MAKE SURE TO SELECT "ALLOW OEM UNLOCK OPTION IN DEVELOPS settings
1.AUTHORIZE TO "ALWAYS ALLOW CONNECTIONS FROM THIS DEVICE"
2.enter bootloader using hardware keys
3.plug in usb
4.run fastboot devices to force fastboot to start deamon ...
5.once fastboot can see your device run oem unlock
6.DO NOT USE USB 3 port so try different USB ports on pc
7. Alternatively use a live USB of Ubuntu minimal to do the job
--- doesn't seem like driver problem if adb can see your device
See if that works
Click to expand...
Click to collapse
I did all of that. Next Problem when i boot the device with Vol Down + Power and select meta mode. I will get only the Motorola Logo or a Normal Reboot into System. I set everything up in Developer Settings. Enabled Debugging and Allow Bootloader Unlock.

Marc_Xperia said:
I did all of that. Next Problem when i boot the device with Vol Down + Power and select meta mode. I will get only the Motorola Logo or a Normal Reboot into System. I set everything up in Developer Settings. Enabled Debugging and Allow Bootloader Unlock.
Click to expand...
Click to collapse
Why select meta mode ? When you are in bootloader you use your volume keys to navigate between meta, recovery& factory reset & meta and you use your power key to select different modes ...what do you want to do in meta mode ?
When you are in bootloader you are essentially in fastboot mode too so it isn't necessary to choose any of the other options unless you are trying to get into recovery which is pointless if you haven't flashed custom recovery yet ..

I Succeded. I Booted into Bootloader with ADB and took a look at Device Manager to install the Driver Properly.
i followed this guide https://forum.xda-developers.com/moto-e4/how-to/guide-unlock-moto-e4-bootloader-unique-t3654275.
Thank you for all of your Replys.

Moto e4 magisk manger trying to instal magisk hide props config says install failed

happymedium22026 said:
Moto e4 magisk manger trying to instal magisk hide props config says install failed
Click to expand...
Click to collapse
Download manually and flash inside recovery yourself

Safety net says the response is invalid does that affect ny device being rooted

happymedium22026 said:
Safety net says the response is invalid does that affect ny device being rooted
Click to expand...
Click to collapse
No it doesn't. That's an error in magisk manager when you hide the manager app itself. Just use a different safetynet checker app if you want to check safetynet.
Why are you posting this stuff in this thread?

Unable to use fastboot!

Hi,
I am trying to unlock Google Camera using this guide. It needs me to use the fastboot mode in my ASUS Zenfone Max Pro M1. As far as I can see, I have followed the guide pretty well.
Enabled debugging mode on the phone
Downloaded the adb and fastboot files
Am using cmd with admin privileges
adb drivers are installed
checked connectivity with "adb devices" command and it is showing the serial number
However, none of the fastboot commands seems to be working for me.
As soon as I try to run the command from guide, mobile just goes dark with one line saying Press Any Key to shutdown. Also, if I try
Code:
fastboot devices
command at the CSC Fastboot Mode screen, it just shows
Code:
???????????? fastboot
and goes to the press any key to shutdown. When I try the command to enable the camera, it shows
Code:
fastboot oem enable_camera_hal3 true
...
FAILED (command write failed (No such file or directory))
finished. total time: -0.000s
The build number is OPM1.WW_Phone-15.2016.1901.339-20190108.
Any help is greatly appreciated!
Regards,
pallups

The exact same happened with me. I tried everything but nothing worked, I even tried every single driver and ADB version out there. I only got it to work when I tried to do the same thing on another computer, and it was successful in the first try. Good luck, I hope you manage to get it working!

Use .\fastboot and remember to put whatever file in the same folder where fastboot files are located

farhanshaikh671 said:
Use .\fastboot and remember to put whatever file in the same folder where fastboot files are located
Click to expand...
Click to collapse
This has nothing to do with his problem, I had the same issues. It has to be a driver problem, because switching to another PC solved the issue.

VictorPLopes said:
This has nothing to do with his problem, I had the same issues. It has to be a driver problem, because switching to another PC solved the issue.
Click to expand...
Click to collapse
I agree. I'm using command prompt not PowerShell. So that shouldn't be an issue.
I don't have a second PC. Any idea on how to solve this on my existing one?

I also used CMD. You could try uninstalling every single android related driver, adb program, file, etc. If it doesn't work, probably, only another PC would do the trick. Also, try another USB ports, and make sure you are using the original USB cable that comes with the device.
If you uninstall everything, make sure you install "15 seconds ADB first", then, plug the device.

Go to your computer BIOS Setup and change the USB port to 2.0 and use the original USB cable.

Let me help you.
The problem is the driver.
Shut down your phone, and go to fastboot mode.
Connect to your PC.
Then, open device manager and see "other devices"
There must be an exclamation mark, update the driver and select manually (let me chose from your computer).
Select the fastboot driver, install.
Voila.
You now should be can use "adb devices" command on cmd or powershell.
Sorry for bad English

I found a workaround solution. Use a multi port USB hub regardless is USB 2.0 or 3.0, connect Android devices to USB hub and USB hub to PC. The problem shall solve regardless of how many times you run "fastboot devices"
pallups said:
Hi,
I am trying to unlock Google Camera using this guide. It needs me to use the fastboot mode in my ASUS Zenfone Max Pro M1. As far as I can see, I have followed the guide pretty well.
Enabled debugging mode on the phone
Downloaded the adb and fastboot files
Am using cmd with admin privileges
adb drivers are installed
checked connectivity with "adb devices" command and it is showing the serial number
However, none of the fastboot commands seems to be working for me.
As soon as I try to run the command from guide, mobile just goes dark with one line saying Press Any Key to shutdown. Also, if I try
Code:
fastboot devices
command at the CSC Fastboot Mode screen, it just shows
Code:
???????????? fastboot
and goes to the press any key to shutdown. When I try the command to enable the camera, it shows
Code:
fastboot oem enable_camera_hal3 true
...
FAILED (command write failed (No such file or directory))
finished. total time: -0.000s
The build number is OPM1.WW_Phone-15.2016.1901.339-20190108.
Any help is greatly appreciated!
Click to expand...
Click to collapse

pallups said:
Hi,
I am trying to unlock Google Camera using this guide. It needs me to use the fastboot mode in my ASUS Zenfone Max Pro M1. As far as I can see, I have followed the guide pretty well.
Enabled debugging mode on the phone
Downloaded the adb and fastboot files
Am using cmd with admin privileges
adb drivers are installed
checked connectivity with "adb devices" command and it is showing the serial number
However, none of the fastboot commands seems to be working for me.
As soon as I try to run the command from guide, mobile just goes dark with one line saying Press Any Key to shutdown. Also, if I try
Code:
fastboot devices
command at the CSC Fastboot Mode screen, it just shows
Code:
???????????? fastboot
and goes to the press any key to shutdown. When I try the command to enable the camera, it shows
Code:
fastboot oem enable_camera_hal3 true
...
FAILED (command write failed (No such file or directory))
finished. total time: -0.000s
The build number is OPM1.WW_Phone-15.2016.1901.339-20190108.
Any help is greatly appreciated!
Regards,
pallups
Click to expand...
Click to collapse
The exact same problem occuring with me... any fixes? Please tell me how to solve this

VictorPLopes said:
The exact same happened with me. I tried everything but nothing worked, I even tried every single driver and ADB version out there. I only got it to work when I tried to do the same thing on another computer, and it was successful in the first try. Good luck, I hope you manage to get it working!
Click to expand...
Click to collapse
I tried with everything for 2 days, nothing works. I faced the same issue, everything works, adb works, driver gets loaded, but "fastboot devices" shows "???????????? fastboot".
After applying this method, (using another PC), everything works within 1 minute.
Hope his help, who faced the same issue.

cychau said:
I found a workaround solution. Use a multi port USB hub regardless is USB 2.0 or 3.0, connect Android devices to USB hub and USB hub to PC. The problem shall solve regardless of how many times you run "fastboot devices"
Click to expand...
Click to collapse
Entirely different phone (Redmi Note 5 Pro) but this is the only solution I could find that worked for me. Thank you very much!

Fastboot not finding device

Hey, I just bought an S7 Edge SM-G950U, the att&t version, SM-G950A. I heard some say that it's not possible to unlock its bootloader, but the OEM unlock option turned out to be available in developer options. However, I'm having a hard time properly installing its drivers, whichever adb driver I use, the driver still shows a yellow warning and the error is that the device can't be started. The device shows up with adb devices when the device is on, but it doesn't neither with fastboot devices nor adb devices when it's in download mode. I'm trying to install TWRP, the hero 2 version. Any help would be appreciated. Thanks in advance

If you in Windows Device Manager find any device with yellow mark right on the device, then the driver installed for it isn't suitable: uninstall it, get Samsung USB Driver and install it.
Samsung devices don't know of a Fastboot mode: there it's called Download mode. You can't run any Fastboot command in this mode.
ADB operates on Android OS, not on device's bootloader, hence it's not working when running the device in Download mode.

Thanks for the prompt reply. I used a different laptop and managed to install the drivers properly, no warnings. However, the result is the same. You mention how I can't run fastboot commands in Download mode, where can I run them? Only Odin is working in that mode now, but I gotta try to unlock the bootloader. A lot of people are saying that this model can't be unlocked, even though the OEM unlock checkbook in the Developer settings is there. Any advice is appreciated

Up

Gearninja said:
Up
Click to expand...
Click to collapse
Down