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
Related
My device is not listed in fastboot devices. However it can be seen in adb mode. I have tried doing:-
1)entering in fasboot manually as well as via "adb reboot bootloader" command.
2)Updating drivers or installing them manually(tried several of them, but none works)
List of drivers that i have tried
1.Universal adb driver by koushik dutta
2.Samsung adb driver
3.Google sdk drivers
4. Installing some random unsigned driver(Last method done)
Please help me i want to revert back to miui by flashing it clean via Flash tool but device isnt detected what to do?
cypherx1998 said:
My device is not listed in fastboot devices. However it can be seen in adb mode. I have tried doing:-
1)entering in fasboot manually as well as via "adb reboot bootloader" command.
2)Updating drivers or installing them manually(tried several of them, but none works)
List of drivers that i have tried
1.Universal adb driver by koushik dutta
2.Samsung adb driver
3.Google sdk drivers
4. Installing some random unsigned driver(Last method done)
Please help me i want to revert back to miui by flashing it clean via Flash tool but device isnt detected what to do?
Click to expand...
Click to collapse
You try install mi pc suite
cypherx1998 said:
My device is not listed in fastboot devices. However it can be seen in adb mode. I have tried doing:-
1)entering in fasboot manually as well as via "adb reboot bootloader" command.
2)Updating drivers or installing them manually(tried several of them, but none works)
List of drivers that i have tried
1.Universal adb driver by koushik dutta
2.Samsung adb driver
3.Google sdk drivers
4. Installing some random unsigned driver(Last method done)
Please help me i want to revert back to miui by flashing it clean via Flash tool but device isnt detected what to do?
Click to expand...
Click to collapse
had experienced this before. Do you use Windows 10 ?
Install MiPc suit
N u r done!
kpratama24 said:
had experienced this before. Do you use Windows 10 ?
Click to expand...
Click to collapse
Yes..i do use windows 10....the solution that worked for me this time is to delete every driver of my phone present in my pc and connecting it....by every driver i mean each and every one(inclusive of adb and fastboot and also usb drivers)...so pc installs a driver by itself and surprisingly it works
cypherx1998 said:
Yes..i do use windows 10....the solution that worked for me this time is to delete every driver of my phone present in my pc and connecting it....by every driver i mean each and every one(inclusive of adb and fastboot and also usb drivers)...so pc installs a driver by itself and surprisingly it works
Click to expand...
Click to collapse
Good to hear that.
cypherx1998 said:
My device is not listed in fastboot devices. However it can be seen in adb mode. I have tried doing:-
1)entering in fasboot manually as well as via "adb reboot bootloader" command.
2)Updating drivers or installing them manually(tried several of them, but none works)
List of drivers that i have tried
1.Universal adb driver by koushik dutta
2.Samsung adb driver
3.Google sdk drivers
4. Installing some random unsigned driver(Last method done)
Please help me i want to revert back to miui by flashing it clean via Flash tool but device isnt detected what to do?
Click to expand...
Click to collapse
Download Adb and fastboot.rar from google.
Extract it to desktop.
Then install Miflash , downloaded from google.
And for fastboot watch video from youtube.
If you are again unable to found or for any type of help.
I'll provide you the files with the video.
cypherx1998 said:
My device is not listed in fastboot devices. However it can be seen in adb mode. I have tried doing:-
1)entering in fasboot manually as well as via "adb reboot bootloader" command.
2)Updating drivers or installing them manually(tried several of them, but none works)
List of drivers that i have tried
1.Universal adb driver by koushik dutta
2.Samsung adb driver
3.Google sdk drivers
4. Installing some random unsigned driver(Last method done)
Please help me i want to revert back to miui by flashing it clean via Flash tool but device isnt detected what to do?
Click to expand...
Click to collapse
download MI Pc suit http://pcsuite.mi.com/
and you won't be needing drivers. and your device would be listed.
I've checked other threads but other similar threads were able to get the phone detected in Device Manager so...
I went to factory reset my old Nexus 4 after using it whilst my LG G4 was being repaired. Instead of wiping the data, I accidentally wiped the entire phone, OS included. I wasn't paying attention to what i was doing due to working at the same time and as a result the phone now only boots into TWRP and fastboot mode, but nothing else.
I tried to connect it to my windows 10 laptop so I could flash a new ROM but my laptop can't find the nexus 4 at all. Not when in recovery or when in fastboot.
Opening device manager shows that it is not there at all. There is no ACER usb device driver, nothing that resembles the nexus 4 at all. I've attached an image showing what device manager shows when the nexus 4 is connected and in recovery mode.
As you can see, there are no drivers I can uninstall. I have installed the google USB drivers from Android SDK manager. Still doesn't show. ADB doesn't work either.
I have tried multiple USB cables and every USB port. The phone charges when using an AC adaptor and charges when connected to the laptop. I can't try a different computer because I do not have access to one. Frankly I'm at a loss as to what to do.
When my nexus 4 was previously unable to connect I was able to see the device and just had to uninstall/reinstall/update drivers to get it working. This time, I can't seem to do anything. My LG G4 connects fine and without issue.
Anyone able to help?
The only way to really tell if it is a software or hardware issue would be to try another computer with Win7.
You may be able to flash a custom ROM with a OTG drive as well.
I had the same problem. When using adb and fastboot I get errors about like "error: device '(null)' not found".
Youtube video with id t0pV2pSw2N0 (sorry I am not yet allowed to post external urls) was helpfull and now I can see Android Composite ADB Interface again in the device manager. I still can not use commands adb and fastboot with exception of adb sideload. Unfortunately I have not yet succeeded to flash an image succesfully with sideload.
first try 2 remove any current drivers that are installed.
then u should experiment with different drivers.
the SkipSoft ToolKit have a huge selection, try each one of them (one of them should work).
begin with the ULTIMATE drivers and Adb/Fastboot Installer and if it don't work use the toolkit drivers.
https://skipsoft.net/download-page/
For me it turned out that MTP was enabled by default. After each restart MTP was enabled again. Now I have disabled MTP and my device is found by normal adb command.
Steps:
1) Start your device in twrp recovery mode
2) In main menu go to mount and tap "Disable MTP"
3) In main menu go to advanced -> adb sideload. Wipe caches and slide to start sideload
4) On your pc go to the command shell
5) Start "adb sideload <image_name.zip>" (replace image_name.zip with a valid image). It does not matter whether this fails or succeeds. Only thing important is that adb connects to your device.
6) Start "adb shell getprop persist.sys.usb.config". As result you will see the actual setting of the USB configuration your device when starting up. In my case it responded with "mtp,adb".
7) Start "adb shell setprop persist.sys.usb.config adb" to enable only "adb" configuration
8) Repeat step 6 to check result
9) Restart your device in recovery mode
10) Start "adb devices" to check if your device is now listed.
i_need_some_help said:
For me it turned out that MTP was enabled by default. After each restart MTP was enabled again. Now I have disabled MTP and my device is found by normal adb command.
Steps:
1) Start your device in twrp recovery mode
2) In main menu go to mount and tap "Disable MTP"
3) In main menu go to advanced -> adb sideload. Wipe caches and slide to start sideload
4) On your pc go to the command shell
5) Start "adb sideload <image_name.zip>" (replace image_name.zip with a valid image). It does not matter whether this fails or succeeds. Only thing important is that adb connects to your device.
6) Start "adb shell getprop persist.sys.usb.config". As result you will see the actual setting of the USB configuration your device when starting up. In my case it responded with "mtp,adb".
7) Start "adb shell setprop persist.sys.usb.config adb" to enable only "adb" configuration
8) Repeat step 6 to check result
9) Restart your device in recovery mode
10) Start "adb devices" to check if your device is now listed.
Click to expand...
Click to collapse
Thanks, I will give this a try!
elad.g said:
first try 2 remove any current drivers that are installed.
then u should experiment with different drivers.
the SkipSoft ToolKit have a huge selection, try each one of them (one of them should work).
begin with the ULTIMATE drivers and Adb/Fastboot Installer and if it don't work use the toolkit drivers.
https://skipsoft.net/download-page/
Click to expand...
Click to collapse
I tried removing all USB drivers and then using the toolkit and tried installing each driver. None of them allowed my PC to detect the nexus 4. As you can see in the attachment, nothing in device manager remotely resembling my nexus 4. This is after uninstalling and reinstalling and also updateing the LG G4 drivers (it makes no difference).
i_need_some_help said:
I had the same problem. When using adb and fastboot I get errors about like "error: device '(null)' not found".
Youtube video with id t0pV2pSw2N0 (sorry I am not yet allowed to post external urls) was helpfull and now I can see Android Composite ADB Interface again in the device manager. I still can not use commands adb and fastboot with exception of adb sideload. Unfortunately I have not yet succeeded to flash an image succesfully with sideload.
Click to expand...
Click to collapse
Alas, this did not work.
audit13 said:
The only way to really tell if it is a software or hardware issue would be to try another computer with Win7.
You may be able to flash a custom ROM with a OTG drive as well.
Click to expand...
Click to collapse
Unfortunately I don't have access to any other PC for this purpose. I can't connect download software or connect USB devices to the PCs at work due to security. I tried an OTG drive but TWRP wouldn't let me mount it, apparently OTG is not enabled by default for the nexus 4.
I've tried all 3 USB ports, several different cables but no luck. I guess that's it for this nexus 4 then?
If the phone is not booted into its ROM, ADB commands won't work. You need to use "fastboot devices" with the phone in bootloader mode.
You android device will reboot in several different boot modes (fastboot, recovery, normal). For each of these boot modes a separate device drive might be installed on your Windows. So check the device drive after each change of boot mode. If needed uninstall and reinstall the correct device driver.
Hi, I've my new essential.
I can't flash a factory image, my device is dectected in fastboot, I have unlocked the bootloader, but when I click on flash-all in the image files, I have "waiting for device". I can't understand why because ALL OTHER COMMANDS have worked : fasboot flashing unlock, USB debugging, fastboot devices...
What can I do ? (In the control panel, device is detected without a yellow mark or something else. Everything should be fine.
basongwe said:
Hi, I've my new essential.
I can't flash a factory image, my device is dectected in fastboot, I have unlocked the bootloader, but when I click on flash-all in the image files, I have "waiting for device". I can't understand why because ALL OTHER COMMANDS have worked : fasboot flashing unlock, USB debugging, fastboot devices...
What can I do ? (In the control panel, device is detected without a yellow mark or something else. Everything should be fine.
Click to expand...
Click to collapse
Still seems like a driver issue. While in bootloader, you could confirm this by trying the command "fastboot devices". If nothing shows then check your device manager. If you are seeing Mata, it's your issue. For some reason every few times I plug in, it'll default back to that and have to manually update the driver to the bootloader driver. Just choose from list of installed drivers as the update method.
Also, if you have USB 2 ports, try one of those. I couldn't get anything to flash when I had it plugged in one of my USB 3 ports.
Could be cable issue, USB port issue, driver issue or you can try updating your adb setup etc... I used the Minimal ADB and Fastboot. Mine was out of date and wouldn't recognize device in fastboot after the Oreo sideload.
Works perfectly with the Essential official drivers in Win8.1Pro now.
The cable is brand new by anker, and works perfectly. Drivers and adb are updated.
mrcooter said:
Still seems like a driver issue. While in bootloader, you could confirm this by trying the command "fastboot devices". If nothing shows then check your device manager. If you are seeing Mata, it's your issue. For some reason every few times I plug in, it'll default back to that and have to manually update the driver to the bootloader driver. Just choose from list of installed drivers as the update method.
Click to expand...
Click to collapse
and fastboot devices works properly. But i've noticed that I wanna flash the same build that I had, maybe that ?
basongwe said:
and fastboot devices works properly. But i've noticed that I wanna flash the same build that I had, maybe that ?
Click to expand...
Click to collapse
Something that was odd that may help (assumed it was just my environment setup). I had adb installed to C:\adb and only way fastboot will work consistently for me is to run commands from that directory. Could be unrelated but thought I would mention it.
basongwe said:
Hi, I've my new essential.
I can't flash a factory image, my device is dectected in fastboot, I have unlocked the bootloader, but when I click on flash-all in the image files, I have "waiting for device". I can't understand why because ALL OTHER COMMANDS have worked : fasboot flashing unlock, USB debugging, fastboot devices...
What can I do ? (In the control panel, device is detected without a yellow mark or something else. Everything should be fine.
Click to expand...
Click to collapse
Try copying fastboot to the folder that has the flash all.bat
What operating system?
Where did you get your driver's?
Reason I ask is at first I had driver's auto install from a Samsung device that I used previously. Caused an issue where it wouldn't start the fastboot process and device got stuck at first step.
Take the system driver of your operating system from essential homepage... Was the trick for me
Link: https://www.essential.com/developer/current-builds
vergilbt said:
Take the system driver of your operating system from essential homepage... Was the trick for me
Link: https://www.essential.com/developer/current-builds
Click to expand...
Click to collapse
This also did the trick for me
You're welcome...
Edit : I have it(drivers from essential website)
Try "fastboot -i 0x2e17 <whatever command here>" it worked for me I wasn't able to unlock my bootloader until I found that command in a random website.
723i said:
Try "fastboot -i 0x2e17 <whatever command here>" it worked for me I wasn't able to unlock my bootloader until I found that command in a random website.
Click to expand...
Click to collapse
That did the trick.
723i said:
Try "fastboot -i 0x2e17 <whatever command here>" it worked for me I wasn't able to unlock my bootloader until I found that command in a random website.
Click to expand...
Click to collapse
command result: "fastboot: unknown option -- i"
not worked for me
mine is on the latest pie update
un1ocked said:
command result: "fastboot: unknown option -- i"
not worked for me
mine is on the latest pie update
Click to expand...
Click to collapse
It's always recommended to use the adb/fastboot provided by Essential (gets installed along with the Windows driver). From the error message, it looks like you are using a different fastboot executable. If you have more than one adb/fastboot package installed on your PC, make sure to use the one from Essential. You can see the path to the executable by running "fastboot --version".
kt-Froggy said:
It's always recommended to use the adb/fastboot provided by Essential (gets installed along with the Windows driver). From the error message, it looks like you are using a different fastboot executable. If you have more than one adb/fastboot package installed on your PC, make sure to use the one from Essential. You can see the path to the executable by running "fastboot --version".
Click to expand...
Click to collapse
fastboot version 28.0.3-5475833
Installed as C:\Program Files (x86)\Essential\ADB\fastboot.exe
EDIT:
problem solved by switching to an old PC with a pure usb 2.0 port
un1ocked said:
problem solved by switching to an old PC with a pure usb 2.0 port
Click to expand...
Click to collapse
Ahh... Yeah, that's often the issue. Still doesn't make a lot of sense to me, because your error msg was "unsupported option". Well, good that it worked for you.
Hi,
I just bought Mi A1.
Now, I wanted to install oreo.
So I was trying to root and install twrp.
Now I'm no expert, I just follow the provided steps and have been successful with past devices.
Note :
1) Developer enabled
2) oem unlocking enabled
3) usb debugging enabled
So I'm using this https://forum.xda-developers.com/mi...l-one-driversunlocktwrpfactory-t3695256/page2
But, there are two issues :
1) When I click on Reboot in fastboot/bootloader mode , it shows this in command prompt : http://prntscr.com/i2sn1o
and in the app, it automatically disconnects from the device http://prntscr.com/i2sncw
2) While this is happening and I leave my device, it automatically goes out from fastboot to power off charging mode.
I tried on another pc too, and followed the steps according to video, still no luck.
And I tried manual methods too, like https://www.youtube.com/watch?v=tRcYUMBgvaI
no luck there either.
Please help.
your adb driver is not installed correctly i guess, happened to me too.
try "adb devices" and will show no devices, if this happen, is the adb driver issue.
this fixed for me.
https://forum.xda-developers.com/showthread.php?p=75163858#post75163858
riccetto80 said:
your adb driver is not installed correctly i guess, happened to me too.
try "adb devices" and will show no devices, if this happen, is the adb driver issue.
this fixed for me.
https://forum.xda-developers.com/showthread.php?p=75163858#post75163858
Click to expand...
Click to collapse
I don't know if there is issue with driver. Because during installation there was no error.
Also, when I command "adb devices" it shows me a device as number.
So it is able to connect to the device then right?
You must install adb drivers AND fastboot drivers separately. I always had to install them manually via device manager. If your phone reboots from fastboot mode automatically, I'm 99% sure that you do not have drivers installed correctly.
_mysiak_ said:
You must install adb drivers AND fastboot drivers separately. I always had to install them manually via device manager. If your phone reboots from fastboot mode automatically, I'm 99% sure that you do not have drivers installed correctly.
Click to expand...
Click to collapse
Hmmmmm. Ok, I'll do that then. Thanks buddy. I'll try again and reply back asap.!!
Hello!
I have a OnePlus 5 running OxygenOS 5.1.5 (Android 8.1.0).
It's also running Magisk 26.1, and until today, TWRP 3.2.1-x.
I enabled Zygisk, which caused a boot loop, so now I can't boot normally (though I can fix this if I can get a root shell).
But now the problem is that I also (foolishly) flashed a very recent (and apparently incompatible) TWRP 3.7.0_12-1, which hangs on boot with a white status LED, so I can no longer access a terminal to fix the Magisk issue.
I can boot into Safe Mode, but it seems very limited. No apps, no ADB (neither TCP nor USB).
Is there a way I can re-flash the recovery image to a working TWRP?
Or factory reset to the factory bootloader / recovery image while retaining user data?
I can't seem to get adb / fastboot / shell access in any of the available states:
Bootlooping standard boot
Failed TWRP boot
Safe Mode
Is there any conceivable way forward?
Thanks!
Update your device
Go into bootloader mode and then BOOT the right twrp version instead of flashing.
immortalwon said:
Go into bootloader mode and then BOOT the right twrp version instead of flashing.
Click to expand...
Click to collapse
Are you referring to Fast Boot mode? And using the fastboot tool over USB from a computer with ADB tools installed?
If so, then that has failed by the phone not showing up as a device (via "fastboot devices").
At this point, I suspect that it may be an issue with the phone's USB port (which has always been flakey).
immortalwon said:
Go into bootloader mode and then BOOT the right twrp version instead of flashing.
Click to expand...
Click to collapse
A replacement USB/headphone port assembly arrived today, and I installed it successfully.
The USB connection is now solid, but the phone still does not show up when listing "fastboot devices" while on the bootloader screen.
Pseudorando said:
A replacement USB/headphone port assembly arrived today, and I installed it successfully.
The USB connection is now solid, but the phone still does not show up when listing "fastboot devices" while on the bootloader screen.
Click to expand...
Click to collapse
that's because you prob have the wrong drivers installed. IN 90% of cases, its faulty driver installation. Disable windows driver signature enforcement and re-install one plus drivers. Then download platform tools and try again.
immortalwon said:
that's because you prob have the wrong drivers installed. IN 90% of cases, its faulty driver installation. Disable windows driver signature enforcement and re-install one plus drivers. Then download platform tools and try again.
Click to expand...
Click to collapse
I dug out an old Windows laptop with USB 2.0 ports, which definitely didn't have any residual OnePlus drivers on it.
I put these in Powershell:
Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Installed the drivers from here:
https://oneplususbdrivers.com/oneplus-5-usb-driver-download/
Powered up the OnePlus 5 into Fast Boot...
And still no devices listed with "fastboot devices".
(Except when I plug in another phone in bootloader mode... other Android devices show up fine).
Pseudorando said:
I dug out an old Windows laptop with USB 2.0 ports, which definitely didn't have any residual OnePlus drivers on it.
I put these in Powershell:
Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Installed the drivers from here:
https://oneplususbdrivers.com/oneplus-5-usb-driver-download/
Powered up the OnePlus 5 into Fast Boot...
And still no devices listed with "fastboot devices".
(Except when I plug in another phone in bootloader mode... other Android devices show up fine).
Click to expand...
Click to collapse
I can't help if the device isn't being detected in bootloader / fastboot mode. It should have worked if its OEM unlocked and usb debugging was enabled.