Hello,
because my recovery is broken I have to re-flash recovery to the phone. I set phone to fastboot mode and installed Lenovo drivers for adb and composite.
But in device manager in windows I only see exclamation marks and I cannot see devie with "c:> fastboot devices".
I also set up a seperate VirtualBox machine Win7 .. same situation .. only exclamation marks under categor "Android" and "Android Device".
Any idea how to solve it and how to get back twrp ?
Related
I recently had my phone unlocked by Alejandrissimo so I can now get into fastboot. The only problem is that when in cmd after putting in a command a message pops up saying "waiting for device" even when my phone is in fastboot mode.
My bootloader is unlocked by the way.
Are your usb drivers set up ok? check installed devices in "device manager" if it shows an exclamation mark you need to install the relevant driver http://www.multiupload.com/BMJ24IL6XY
Hope that helps
Thank you for that. I've got it working now.
please upload driver again¿¿
garner said:
Are your usb drivers set up ok? check installed devices in "device manager" if it shows an exclamation mark you need to install the relevant driver http://www.multiupload.com/BMJ24IL6XY
Hope that helps
Click to expand...
Click to collapse
I checked on device manager like you said and there is no exclamation mark but it is still waiting for device. Also can you upload the link on another website because multiupload doesn't work.
Thanks
Hi, using TWRP I formatted everything by using the format tool and ticking everything (wanted a clean slate for installing a new rom).
I can now only get into TWRP (vol- doesn't seem to do anything, vol+ gets me into TWRP). This means I can't flash using flashtool, so I will have to use TWRP's ADB sideload feature. However, my phone is not showing up on my PC when it is plugged in and on TWRP sideload. It is not showing in device manager, and obviously is not working from the ADB command line.
HELP!
Ok, in device manager when not in TWRP I've managed to get it to show up in device manager, listed under "Android Phone" as "Android ADB Interface". This is a start - however, this only works when the xperia s is showing the "sony" logo - i.e. when I reboot and don't press vol+, it stays on the "sony" loading screen forever. When I reboot into TWRP, the phone disappears from device manager, even when I'm running TWRP's ADB sideloader.
Clicking "mount" in TWRP does nothing either, so I can't transfer a ROM over by drag'n'drop.
So it shows up in ADB as offline when on the sony screen, and is completely noncommunicative when in TWRP. FFFFUUUUUU how will I ever get this working?
Basically, my only hope is probably ADB. The phone is either recognised but offline, or doesn't even show up in device manager let alone ADB.
HELP!
IceQubed said:
Ok, in device manager when not in TWRP I've managed to get it to show up in device manager, listed under "Android Phone" as "Android ADB Interface". This is a start - however, this only works when the xperia s is showing the "sony" logo - i.e. when I reboot and don't press vol+, it stays on the "sony" loading screen forever. When I reboot into TWRP, the phone disappears from device manager, even when I'm running TWRP's ADB sideloader.
Clicking "mount" in TWRP does nothing either, so I can't transfer a ROM over by drag'n'drop.
So it shows up in ADB as offline when on the sony screen, and is completely noncommunicative when in TWRP. FFFFUUUUUU how will I ever get this working?
Basically, my only hope is probably ADB. The phone is either recognised but offline, or doesn't even show up in device manager let alone ADB.
HELP!
Click to expand...
Click to collapse
Did You try flashing a stock firmware via fastboot? Or do You have an unlocked bootloader? While being in twrp, check all the devices in device manager, see if it is unrecognized or something.
Mirhawk said:
Did You try flashing a stock firmware via fastboot? Or do You have an unlocked bootloader? While being in twrp, check all the devices in device manager, see if it is unrecognized or something.
Click to expand...
Click to collapse
After about 4-5 hours of searching, flashing and mucking around with 100 different drivers, last night at 2AM I finally fixed it. I installed the google usb drivers manually, and found a device that was unrecognised hidden amongst the other usb devices. I was expecting the unknown device to be highlighted or have a big yellow question mark, it didn't- it had a very small one in the corner of the icon. I clicked update driver software, selected the google ADB driver and from then on the ADB sideload in TWRP worked. :laugh:
IceQubed said:
After about 4-5 hours of searching, flashing and mucking around with 100 different drivers, last night at 2AM I finally fixed it. I installed the google usb drivers manually, and found a device that was unrecognised hidden amongst the other usb devices. I was expecting the unknown device to be highlighted or have a big yellow question mark, it didn't- it had a very small one in the corner of the icon. I clicked update driver software, selected the google ADB driver and from then on the ADB sideload in TWRP worked. :laugh:
Click to expand...
Click to collapse
Glad You got it solved, it is always the drivers issue!
I just want to install twrp to my phone.
Installed drivers adb to my computer and open usb debug mode on my phone.
Command window i run ''adb reboot bootloader'' then my phone closed and started with the CSC Mode
After that commands doesnt work. And its make a new unknown device to my device manager; http://i.imgur.com/0xg4rkU.png
I stuck at there cant install the unknown driver.
How can i fix this, pls help..
Device; Asus zenfone max (ZC550KL) Z010D
right click on that android with yellow triangle then click (update driver software) then click >>(browse my computer for driver software) then click >>(let me pick from a list of device driver on my computer) then it will show some drivers with ASUS name on it install the adb interface, bootloader interface & composite adb interface one by one. I encounterd this problem these last days with the same phone This way ADB detected my phone by command "fastboot devices" while connected on CSC mode then u can proceed on flashing TWRP
Tried on windows 10 and 7:
Phone is detected by ADB and commands work no problem. Boot in to fastboot (download mode) and the device isn't found when using "fastboot devices". The phone appeared in device manager with the yellow triangle but I manually updated the driver to "Android Bootloader Interface" however, I still get nothing. Am I missing something?
Thank you.
Mine never has shown in fastboot, if it shows up in device manager it should work fine. To test just try fastboot reboot.
If you corrected the issue with the driver,the problem may be with the versions of Fastboot you are using. You can download the latest Fastboot and ADB files from Google directly if you search for them it should be the first or second link.
You need google usb drivers
I have the latest google usb and platform tools on a windows 7 &10 systems using different usb ports along with multiple cables and I can not detect the phone, but I can flash.
Hi.
Got a problem here I can't solve on my own.
QFIL-flashed a stock rom (tried to fix the blue screen on boot-thing) and was thinking it should be a breeze to unlock the bootloader and so on. But nope.
I have:
* Adb and fastboot installed
* The ZUK USB-drivers (yes, have turned off the option for windows to require signed drivers)
* Tried different USB-ports. Even another computer
* Other drivers, such as the "mi flash" drivers, universal ADB-drivers, naked ADB-drivers...
I have enabled USB-debugging, and when I write adb devices (when the phone is in android), the device is shown.
Then I use the "adb reboot bootloader" fo get into fastboot. The phone says fastboot_mode, but when I try to find the device via "fastboot devices", it's not shown.
In windows device manager the driver is OK, and shown as "ShenQI Composite ADB Interface".
Any clue what's wrong?
Well, I used the "tool all in one", and now it works....from that program. But still no devices in fastboot devices when I check manually....