I use
adb reboot bootloader
to get into fastboot mode.
the display shows
"Fasboot & rescue mode
please connect and open Hisuite
LINK
phone locked"
I even installed the Hisuite, but nothing happens and
fastboot devices
returns an empty list.
when the devices is booted up, USB works like a charme - but in fastboot mode windows does not even detect a device?!
any ideas?
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.
I'm trying to install TWRP on my S5 (SM-GM900W8) via Windows 7
I've been using 15 Sec ADB/Fastboot (https://forum.xda-developers.com/showthread.php?t=2588979), installed in administrator mode and in both Single User and All User modes
The phone has USB debugging enabled and it is in PTP transfer mode
I installed the ADB driver in Device Manager as per the instructions, and CMD 'C:\[...] adb devices' recognizes the phone
However, after I put the phone in fastboot, via CMD 'C:\[...] adb reboot bootloader', the phone isn't recognized
I have installed the 'Android Bootloader Interface' driver in Device Manager mode (after putting the phone in bootloader mode)
The computer still does not recognize the attached phone (stuck in WAITING FOR DEVICE)
I have tried swapping out the cables three different times
Please...help.
I can upload pictures if requested
ghostHardware said:
I'm trying to install TWRP on my S5 (SM-GM900W8) via Windows 7. I've been using 15 Sec ADB/Fastboot (https://forum.xda-developers.com/showthread.php?t=2588979), installed in administrator mode and in both Single User and All User modes. The phone has USB debugging enabled and it is in PTP transfer mode. I installed the ADB driver in Device Manager as per the instructions, and CMD 'C:\[...] adb devices' recognizes the phone. However, after I put the phone in fastboot, via CMD 'C:\[...] adb reboot bootloader', the phone isn't recognized. I have installed the 'Android Bootloader Interface' driver in Device Manager mode (after putting the phone in bootloader mode). The computer still does not recognize the attached phone (stuck in WAITING FOR DEVICE). I have tried swapping out the cables three different times. Please...help. I can upload pictures if requested
Click to expand...
Click to collapse
Your best bet is to post this question within the following thread.
http://forum.xda-developers.com/showthread.php?t=2700073
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Device LG G6
Model : G600LR30c
I was thinking of installing a custom os which requires TWRP recovery installed in the device which recuires the device to be bootloader unlocked. But when I use the command "adb reboot bootloader" in minimal adb the device never goes to boot menu, instead it simply restarts and then if I put the command "fastboot oem device-id", it never shows the id and keeps showing "waiting for a device" instead. Please help me resolve this.
P.S: I also tried to access boot menu using key combo. but in vain
If you can put the phone in Fastboot mode during powerup or restart, it's a Windows issue if it don't work. Windows must recognize the device via PnP and install a different set of drivers each time the usb mode changes. If it don't work when the phone is already in Fastboot mode, try different drivers.
I once had two sets installed, that from the device manufacturer and that ripped from the Google SDK(on XDA). This way all usb modes worked, but Windows couldn't perform the Reboot Fastboot/Recovery commands fom ADB like is the case here and the Windows software had, suitable drivers installed, to be able to access the phone if it was already set to Fastboot/Download etc mode.
That was a TI OMAP based LG L9 under Win7. Starting with Windows 8.1, Fastboot was no longer working at all, you could only perform disaster recovery via D/L mode with a stock image and then root the thing with a one-click rooter to be able to install a recovery from Android etc etc, but that was due to the no longer supported TI SoC. But Qualcomm also tends to completely abandon older SoCs.
I'm dumbfounded. I have unlocked bootloaders and rooted for years. Just got my OP8P.
I also have a new Microsoft Surface Pro with Windows 10.
I installed ADB, installed Fastboot.
Unlocked developer options and turned on USB Debugging and Developer Unlock.
Windows device manager shows ADB INTERFACE for the my device in device manager.
I can open can open Power Shell and/or the CMD prompt. I've done both.
I can type adb devices in the command prompt and I CAN see my device.
I can reboot it fastboot from the CMD prompt so I KNOW Wndows sees my phone.
BUT ONCE I'M IN FASTBOOT, the problem starts.
Fastboot does NOT see my device. Commands return the words "Waiting for Device..."
I BELIEVE the issue is with the drivers. When I boot into Fastboot, my device location changes in Device Manager from USB>ADB Interface to Portable Devices>Android.
The Android Device icon has a yellow triangle with an exclamation mark. It's says the driver for this device is not installed. But everything was working fine and the drivers were fine while the device was powered up normally.
If I try to manually install the driver it fails and says "cannot update drivers for your Android".
What heck is going on? What did I do wrong?
I've uninstall and reinstalled the drivers direct from Oneplus. I've uninstall and reinstalled the drivers direct from Google. 'I ve uninstall and reinstalled the drivers direct from Windows.
Why can't device and drivers be recognized in Fastboot. And why can't I update the drivers for the "Android" device?