Hey all, I just got a G90 Pro that I want to put a ROM on, but something is up with the fastboot. I have the drivers installed according to what I found online, but when I go to fastboot there is no response from the cmd inputs. Nothing even shows up when I check fastboot devices. Has anyone had luck with these phones? I can't even unlock the bootloader!
If not already done yet, install the suitable BLUE USB Driver for Android:
Download BLU USB Driver for Windows (Latest Driver)
Download the latest and original BLU USB Driver to connect any BLU Smartphone and Tablets to the Windows Computer quickly.
androidmtk.com
jwoegerbauer said:
If not already done yet, install the suitable BLUE USB Driver for Android:
Download BLU USB Driver for Windows (Latest Driver)
Download the latest and original BLU USB Driver to connect any BLU Smartphone and Tablets to the Windows Computer quickly.
androidmtk.com
Click to expand...
Click to collapse
I have done this, but did it again just to be sure, and device manager recognizes the G90 Pro under USB devices, and ADB finds it, but when I do the 'adb reboot bootloader' the fastboot mode text is on the bottom, yet fastboot commands don't do anything, not even 'fastboot devices'.
Edit: Fastboot devices is recognized in fastbootd, but not regular fastboot, yet the other commands don't work.
In your case fastboot is located in Android's user-space, hence you run this command sequence
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot <YOUR-COMMAND-HERE>
fastboot reboot
jwoegerbauer said:
In your case fastboot is located in Android's user-space, hence you run this command sequence
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot <YOUR-COMMAND-HERE>
fastboot reboot
Click to expand...
Click to collapse
Fastboot reboot fastboot just brings up the fastboot command list. Assuming it's expecting me to try reboot bootloader.
That's really weird because your phone is running Android 10.
My info in settings definitely confirms that. Nothing seems to be working as expected though.
jwoegerbauer said:
That's really weird because your phone is running Android 10.
Click to expand...
Click to collapse
Is there any other possible solution? I still can't get fastboot commands to work after rebooting to fastboot mode from fastbootd.
Related
Hi!
I recently got my new Acer Tablet A3-A30. After unlocking developer options and activating debugging I was able to use adb. So I rebooted into bootloader to see if fastboot works - it did not! The output of fastboot devices was empty (this and the following commands were typed as root).
So I killed adb with adb kill-server, disconnected it from my computer and turned it off. After a few moments I turned it on by pressing power while holding Vol[-]-Key. Again the tablet booted into fastboot mode. Now I connected it with my computer and hoped fastboot will recognize the device now. Again, the output was empty.
I noticed, that after connecting the tablet, the text fastboot mode on the display didn't change - all other devices I put into fastboot mode showed fastboot usb mode or similar after I connected them with my computer.
I tried different USB ports - nothing changed.
I'm just wondering, since I'm not familiar with acer devices: Is there a hidden key sequence to get into fastboot usb mode?
Thanks,
Tintom1
Tintom1 said:
Hi!
I recently got my new Acer Tablet A3-A30. After unlocking developer options and activating debugging I was able to use adb. So I rebooted into bootloader to see if fastboot works - it did not! The output of fastboot devices was empty (this and the following commands were typed as root).
So I killed adb with adb kill-server, disconnected it from my computer and turned it off. After a few moments I turned it on by pressing power while holding Vol[-]-Key. Again the tablet booted into fastboot mode. Now I connected it with my computer and hoped fastboot will recognize the device now. Again, the output was empty.
I noticed, that after connecting the tablet, the text fastboot mode on the display didn't change - all other devices I put into fastboot mode showed fastboot usb mode or similar after I connected them with my computer.
I tried different USB ports - nothing changed.
I'm just wondering, since I'm not familiar with acer devices: Is there a hidden key sequence to get into fastboot usb mode?
Thanks,
Tintom1
Click to expand...
Click to collapse
I have an a1-830 and it can be a real pain in the ass to get anything working on them. Try this, since you got adb working, adb reboot bootloader, then wait till it says fastboot cmd waiting or something. If that din't work, reply!
RAZERZDAHACKER said:
I have an a1-830 and it can be a real pain in the ass to get anything working on them. Try this, since you got adb working, adb reboot bootloader, then wait till it says fastboot cmd waiting or something. If that din't work, reply!
Click to expand...
Click to collapse
It worked, I got the fastboot mode with fastboot cmd waiting message!
Tintom1 said:
It worked, I got the fastboot mode with fastboot cmd waiting message!
Click to expand...
Click to collapse
Ayyy, hit thanks if I helped
RAZERZDAHACKER said:
Ayyy, hit thanks if I helped
Click to expand...
Click to collapse
But this is what I already got. It says fastboot mode (now with the waiting message), but not fastboot usb, so fastboot still doesn't see the device
Tintom1 said:
But this is what I already got. It says fastboot mode (now with the waiting message), but not fastboot usb, so fastboot still doesn't see the device
Click to expand...
Click to collapse
And fastboot devices shows...?
RAZERZDAHACKER said:
And fastboot devices shows...?
Click to expand...
Click to collapse
Nothing:
# fastboot devices
#
Tintom1 said:
Nothing:
# fastboot devices
#
Click to expand...
Click to collapse
If you are using Linux, try running fastboot with the sudo command. Also, the drivers might not be properly installed, check out this to download them.
My PC doesn't detect my phone when I use Fastboot Devices when my phone is on Fastboot mode. I get a blank space in return. Can anyone help me with this? ADB works fine, it's only Fastboot. Is there a Fastboot driver that I might be missing?
Thank you.
Edit: I'm trying to unlock the bootloader of my phone.
Me too !
Drivers are here: https://developer.android.com/studio/run/win-usb
These are the ones I use for ADB/Fastboot.
May I ask if anybody solved this already?
Having the same issue, tried various drivers, but fastboot won't find my phone
Help is highly apperciated!
Clock
If you using windows 10 have you disable the drivers signature verification.. And search on here (XDA) for Min ADB & Fastboot tools, easier than using SDK tools unless you modding apks ect..
Okay, I got this working.
When in fastboot mode, you have to go to the device manager, update driver, and manually choose the google fastboot driver. Then the ! is gone and it works.
Fastboot drivers for Xperia XZ1
Redcalibur said:
My PC doesn't detect my phone when I use Fastboot Devices when my phone is on Fastboot mode.
Click to expand...
Click to collapse
I add a hint to the solution that is working for me (Windows 7, 64 bit): https://forum.xda-developers.com/showpost.php?p=79221714&postcount=44
Redcalibur said:
My PC doesn't detect my phone when I use Fastboot Devices when my phone is on Fastboot mode. I get a blank space in return. Can anyone help me with this? ADB works fine, it's only Fastboot. Is there a Fastboot driver that I might be missing?
Thank you.
Edit: I'm trying to unlock the bootloader of my phone.
when u connect phone to pc choose no data transfer then open cmd and write: adb reboot fastboot
Click to expand...
Click to collapse
I am on an older macbook pro running High Sierra. the phone I'm using is a Blu G5 running android 9. I have the developer options unlocked and oem unlocked and usb debugging checked. When i open my terminal i type cd and drag and drop the platform tools folder into the terminal window changing the directory to the folder containing the adb and fastboot files. I can use adb commands such as adb devices and get the serial number and it says devices. So far so good. Then i reboot the phone into the bootloader manually or using command adb reboot bootloader and the phone goes into fastboot mode. I know because it says it on top of the screen in white letters. Then i run into the problem fastboot commands don't work. If I type in fastboot devices nothing but a new command line shows up. When i type in any other command like fastboot device or fastboot oem unlock it says "waiting for any devices." I wait and wait but nothing happens. I have looked on the internet for a solution but all i find is that the driver may not deinstalled properly. I have tried manually installing fastboot driver and used sdk manager to install the fastboot driver and I have tried it using the terminal in android studio but no matter what when i try useing fastboot commands i get the "waiting for any device" message. Does any have a solution or could anyone recommend and forum for android development on MacOSX?
@DimDreams
Seems the Fastboot driver is invalid.
jwoegerbauer said:
@DimDreams
Seems the Fastboot driver is invalid.
Click to expand...
Click to collapse
I have literally tried like 10 different sdk tool downloads just platform tool download basically every thing i can find. By chance would you or anyone out there have a working driver for MacOSX 10.13.6? or link a guide that can help me figure this out. I have made a little progress with a forum on xda about fastboot on macs but i still just keep getting the waiting for any device message.
@DimDreams
May also be that the Fastboot Android mode is not available on the phone in question.
I've had similar issues before and noticed that fastboot mode works better via USB 2.0 than USB 3.0. Maybe check which port you're using and switch. ADB seems to work well either way, however. Hope that helped.
I just had this problem as well and I found this, what worked for me is first boot your phone into bootloader mode with
Code:
adb reboot bootloader
. While in the bootloader fastboot worked for me. Hope this helps someone!
Hello, I don't know if anyone here has been there
Simply no computer recognizes my Mi A3 in fastboot mode, it appears as if there is nothing connected to the PC (I have tested it on other computers, all drivers are right, I tried with other cables, and nothing detected)
The adb works normal (Detects the device), MTP also (I can pass files from the PC to it), Only Fastboot that does not appear devices
My bootloader is unlocked, this happened a few days ago. I'm stuck on MIUI, because anything I do I can't use fastboot to fix.
I'm afraid to try EDL and he dies for good (He detects EDL Mode via the USB cable, holding volume down). Would you have any fix for that, be it opening it, removing the battery, shorting some part of the board?
What is the output when you type
Code:
fastboot devices
Or any fastboot codes you type?
garylawwd said:
What is the output when you type
Code:
fastboot devices
Or any fastboot codes you type?
Click to expand...
Click to collapse
C:\adb>fastboot devices
C:\adb>
My device manager also doesn't recognize the phone in fastboot
Andley302 said:
C:\adb>fastboot devices
C:\adb>
Click to expand...
Click to collapse
Looks like you don't have fastboot installed just adb. Your working from an adb folder are you sure you have the full platform tools installed or just adb?
garylawwd said:
Looks like you don't have fastboot installed just adb. Your working from an adb folder are you sure you have the full platform tools installed or just adb?
Click to expand...
Click to collapse
yes, fastboot is in that same folder, I even installed a Redmi 7A Stock via fastboot for him
Andley302 said:
yes, fastboot is in that same folder, I even installed a Redmi 7A Stock via fastboot for him
Click to expand...
Click to collapse
Only mi a3 does not work on fastboot, does not detect on any computer
Hello.
Today I updated from the Nord 5G to the Nord 2 5G.
DN2103_11_A.14
I have enabled developer mode, oem unlock and adb debug.
I can't access fastboot properly. And recovery is different from the previous Nord. There is no option to reboot to fastboot.
I use adb reboot-fastboot and I enter a sort of fastboot. It says:
fastboot_unlock_verify ok
The device is in fastboot mode which is only for debug Android devices. if you want to exit fastboot mode, please long press volume up nad power buttons simultaneously.
Phone is recognized in windows when in adb-mode (normal booted), but does not recognize it when in this new fastboot mode. Just an Android with an exclamation mark on.
Halp?
krugm0f0 said:
Hello.
Today I updated from the Nord 5G to the Nord 2 5G.
DN2103_11_A.14
I have enabled developer mode, oem unlock and adb debug.
I can't access fastboot properly. And recovery is different from the previous Nord. There is no option to reboot to fastboot.
I use adb reboot-fastboot and I enter a sort of fastboot. It says:
fastboot_unlock_verify ok
The device is in fastboot mode which is only for debug Android devices. if you want to exit fastboot mode, please long press volume up nad power buttons simultaneously.
Phone is recognized in windows when in adb-mode (normal booted), but does not recognize it when in this new fastboot mode. Just an Android with an exclamation mark on.
Halp?
Click to expand...
Click to collapse
Don't own this device but try: "adb reboot bootloader" instead and test fastboot commands from there (don't navigate to Fasboot from bootloader).
krugm0f0 said:
Phone is recognized in windows when in adb-mode (normal booted), but does not recognize it when in this new fastboot mode. Just an Android with an exclamation mark on.
Click to expand...
Click to collapse
This is normal behaviour with the OPN2 afaik. Your PC can access the USERDATA folder whilst in ADB mode (aka booted normally) and whilst in the recovery bios. Your pc CANNOT access the USERDATA folder when your phone is in fastboot, or at least I've never been able to on my Nord 2.
Your op didn't include what exactly you need help with. Everything you described is exactly intended behaviour. From my understanding your seem to have booted into fastboot mode, then noticed your PC can't access userdata. That's normal, you can still use fastboot commands and your PC is still connected to the phone. Your "My Computer" folder on PC not showing the phone shouldn't be any cause for alarm.
Now I'm starting to guess, because you might have failed to mention; Are you unable to send fastboot commands to your phone when its in fastboot mode?
Are you trying to flash a file?
What's the issue?
Zombnombs said:
This is normal behaviour with the OPN2 afaik. Your PC can access the USERDATA folder whilst in ADB mode (aka booted normally) and whilst in the recovery bios. Your pc CANNOT access the USERDATA folder when your phone is in fastboot, or at least I've never been able to on my Nord 2.
Your op didn't include what exactly you need help with. Everything you described is exactly intended behaviour. From my understanding your seem to have booted into fastboot mode, then noticed your PC can't access userdata. That's normal, you can still use fastboot commands and your PC is still connected to the phone. Your "My Computer" folder on PC not showing the phone shouldn't be any cause for alarm.
Now I'm starting to guess, because you might have failed to mention; Are you unable to send fastboot commands to your phone when its in fastboot mode?
Are you trying to flash a file?
What's the issue?
Click to expand...
Click to collapse
I am unable to send fastboot commands. Is not recognized by "fastboot devices". And this fastboot mode looks nothing like my previous phones. 2, X, 5T and Nord 5G. <waiting for device>
I want to do my "usual routine" with my new phones. Unlock, flash twrp or other recovery, and flash magisk for root.
After a "full wipe" of ADB and fastboot drivers, I reinstalled and got it working!
nothing. only recovery mode
vol down+ power =recovery mode
vol up + power = normal boot
I finaly boot into fastboot mode with adb command only (adb reboot bootloader)
With buttons wont work.
But i can't enable Volte/Vowifi (thats why i wanted to boot there).
Can you send adb commands when in recovery mode ?
I'm trying to enable VoLTE too, but adb only detect phone when powered normaly, not when in recovery mode.
i don't know about adb but in fastboot you can.
I can't enable volte/vowifi in fastboot with this commands.
https://androplus.org/wp/wp-content/uploads/2021/08/onr12.jpg
Fastboot commands start with fastboot, those are adb commands.
krugm0f0 said:
After a "full wipe" of ADB and fastboot drivers, I reinstalled and got it working!
Click to expand...
Click to collapse
krugm0f0 said:
Hello.
Today I updated from the Nord 5G to the Nord 2 5G.
DN2103_11_A.14
I have enabled developer mode, oem unlock and adb debug.
I can't access fastboot properly. And recovery is different from the previous Nord. There is no option to reboot to fastboot.
I use adb reboot-fastboot and I enter a sort of fastboot. It says:
fastboot_unlock_verify ok
The device is in fastboot mode which is only for debug Android devices. if you want to exit fastboot mode, please long press volume up nad power buttons simultaneously.
Phone is recognized in windows when in adb-mode (normal booted), but does not recognize it when in this new fastboot mode. Just an Android with an exclamation mark on.
Halp?
Click to expand...
Click to collapse
i am having the same issue can any one help
krugm0f0 said:
After a "full wipe" of ADB and fastboot drivers, I reinstalled and got it working!
Click to expand...
Click to collapse
pls contact me in 9650930525 in this number and help me how u did it
drkanurag said:
i am having the same issue can any one help
Click to expand...
Click to collapse
pankspoo said:
On Android 12 OnePlus removed fastbootmode so no unlocking nothing.
But how did u booted in fastbootmode on oos 12 i can't understand
Click to expand...
Click to collapse
roldev said:
Downgrade to latest A11. Unlock via fastboot. Do what you want, then. All explained here or/and telegram group. Sorry, don't have time to do step by step guide now. Cheers.
Click to expand...
Click to collapse
Follow this guide to downgrade to A11 https://community.oneplus.com/thread/1596759
Then you should be able to access fastboot.
krugm0f0 said:
After a "full wipe" of ADB and fastboot drivers, I reinstalled and got it working!
Click to expand...
Click to collapse
Could you go into more detail on what you did in the entire process exactly? Did you use the drivers and adb install from the 15 sec installer? Did you simply uninstall them in the Windows Device Manager and click on "update drivers" to find the local drivers from the 15 sec installer? Which ones did you choose? Sorry, these might be dumb questions, but I'm admittedly very stupid when it comes to Windows and drivers in particular.
I did the exact thing I described above but I'm still just getting that message. Additionally, "fastboot devices" won't list anything and "fastboot oem unlock" will wait for the device for eternaty. "adb devices" on the other hand will list my device while not in Fastboot.