please help me! i've FONEPAD ME175CG, blocked. i cant entry in recovery mode.... my pc dosnt see .... i've install the driver intel, but fastboot command doesnt work... PLEASE HELP!!!
donaldduck75 said:
please help me! i've FONEPAD ME175CG, blocked. i cant entry in recovery mode.... my pc dosnt see .... i've install the driver intel, but fastboot command doesnt work... PLEASE HELP!!!
Click to expand...
Click to collapse
Hi
Looks like your computer isn't recognizing the attached FonePad.
Assuming you've checked the USB cable and the connecting ports are working fine, if you are using a Windows pc, it is likely the bootloader interface drivers havent been installed properly specially if you are on Windows 10 anniversary update or beyond. This is because latest Windows builds won't allow unsigned drivers. So you can either try to download the device drivers from Asus official site and install them afresh, maybe the last time they didn't get installed properly. If you still can't, you can try using a pc with an older Windows version. You can Google for "Windows enable unsigned drivers" without quotes.
I have a FonePad ME372CG model and I've faced this issue once, rectified with ensuring that the bootloader interface driver shows up in device manager > android device name > ADB Bootloader Interface
Once you've ensured the drivers are installed okay, you can check for device connectivity by the flashboot devices command, should bring back a string of numbers.
If above fails and you're sure you've installed everything fine, you may want to check out about flashing raw firmware. I've never tried it but have seen users on asus forums mention it as a means to revive bricked devices. Here's a link to the raw firmwares
http://asusraw.blogfa.com
Please be absolutely sure of what you do and take responsibility for it
Sent from my Moto G4 Plus using XDA Labs
Related
winxp sp3 sony tablet s when put in recovery mode for flashing the mtp driver
shows yellow (!).when i try to install driver manually it trys to start but comes
back with code 10.with tablet in normal mode winxp sees mtp & adb drivers.
the problem is only with recovery mode.tryed all i can think of and read all
solutions but driver still fails to start.so i can,t flash fw!. i really need help with
this one. please someone help i`ll give you a big thanks. i know i am not the
only one with this problem.i hope this is clear enough.
Same problem here:
Everything's fine in normal boot, but in recovery mode, I can't install the MPT driver. Win7pro. It tries to install, but ends up with a Code28 (something in the INF file is invalid, can't tell the english error message, because I have German Win7).
This seems to cause my problem flashing to R5a by AiO or the auto flasher by condi.
I get the exact error message on the tablet, as shown in post #72 in this thread:
[FW R5A WIFI/3G] NEW! custom preROOTed newest stock nbx03 R5A with R1A's recovery
Trying since four nights...
At least I managed to flash and root to 4.0.3 R2a from the "unrootable" 3.2 R10 by flashing via recovery mode to Sony original ICS R2a (downloadable from sony) and then using the AIO 5.3 to root. Don't know why this way is not published here... Tried updating to 3.2.1 etc, nothing worked... the found the links to sony's fw and thought "WTF! Let's try ICS R2a, worst case is an also unrootable Tablet but with ICS". Worked, and was rootable then.
Just ignore the problem. I believe seeing the alerted MTP USB Device in Windows Device Manager when your tablet is in Recovery Mode is being cause by your tablet's borked Android System Recovery Revision 36 (i.e., Rev.36). This problem did not occur with earlier revisions of Android System Recovery. Normally, no MTP USB Device (or Sony Tablet S) should be displayed or even installed for Recovery Mode because a tablet in Recovery Mode cannot provide MTP functionality. Recovery Mode only requires Android Composite ADB Device be installed. Normal Mode, however, requires both Android Composite ADB Device (but only when the tablet's USB Debugging is turned on) and MTP USB Device, which Windows Device Manager renames and displays as Sony Tablet S.
You are basically right... it was ADB drivers, not MTP.
I tried all possible drivers from the list, also some "phone" devices. And YES!! Windows accepted one of them...
After that, I had no problem flashing my tablet to ICS R5a!!
please, could somebody who has writing permission in the dev forums, tell Condi, that the AiO 5.3 tools tells you to check this driver ONLY AFTER you are NOT stuck in "status7" error!!!!!
You do NOT get the message in the terminal box, IF you are stuck.
That would have saved me one or two nights trial and error...
But, after all, I have a nice working ICS R5a on my tablet S
I will post a how-to for other 3.2 kernel10
that explains a lot. so i need to find another adb driver that works in recovery mode and
not worry about mtp driver?.
phc1234 said:
that explains a lot. so i need to find another adb driver that works in recovery mode and
not worry about mtp driver?.
Click to expand...
Click to collapse
Right.
In device manager, it's "android phone" (?), when you select driver manually, then I think it was the same as on the first install, so the third ADB device in the drivers list.
Windows fools you, it installs an MTP driver, and thus keeps you from using your brain
Install ADB drivers, check whether your tablet will be correctly recognized in both modes... then at least the all in one tool with custom zip will work (hopefully).
Why the flasher did not work? Don't know. looking again at my error messages, I would guess, that the busybox was not working correctly. I don't know if you have to install busybox before, manually. I thought everything was integrated into the flasher...
android phone dosent show in device manager
ThreeEyes said:
Right.
In device manager, it's "android phone" (?), when you select driver manually, then I think it was the same as on the first install, so the third ADB device in the drivers list.
Windows fools you, it installs an MTP driver, and thus keeps you from using your brain
Install ADB drivers, check whether your tablet will be correctly recognized in both modes... then at least the all in one tool with custom zip will work (hopefully).
Why the flasher did not work? Don't know. looking again at my error messages, I would guess, that the busybox was not working correctly. I don't know if you have to install busybox before, manually. I thought everything was integrated into the flasher...
Click to expand...
Click to collapse
[edit]
thats the problem android phone dosent show up in device manager. tryed on 3 wixp computers and nothing no way
ti install adb drivers.
phc1234 said:
[edit]
thats the problem android phone dosent show up in device manager. tryed on 3 wixp computers and nothing no way
ti install adb drivers.
Click to expand...
Click to collapse
But by manually updating the driver and choosing manually, you can assign ANY driver to any device - it may not work or even do some damage to the system, but basically, it's your choice!
Take the device with the "!" and give it the right driver...
"CAT" above is right with rel5 and 5a that they changed the recovery rev to 36 and this rendered the
tablet s from loading any mtp driver or seeing the android phone entry in device manager so no way
to install adb driver.this has killed conis AIO tool flashing firmware and roms until someone breaks
the lockdown sony put in.
today i reflashed my phone with stock 4.0.4 french ftf and it is working fine with usb debugging off but with debugging on, my computer doesnt see the phone! what should i do?
i have reflashed it but still usb debugging mode is not working! help! please what can the problem be?
plz help !
im stuck on stock! no root! nothing good!
First: Don't Panic.
Second: Check your drivers. If not properly installed, try one from sony (just google your device together with "adb driver").
Third: after a complete flash it's like you've never touched your device, means you have to re-root your device normally.
i hope this helps.
murderered said:
First: Don't Panic.
Second: Check your drivers. If not properly installed, try one from sony (just google your device together with "adb driver").
Third: after a complete flash it's like you've never touched your device, means you have to re-root your device normally.
i hope this helps.
Click to expand...
Click to collapse
no its not working!
ive installed a new windows on virtualbox but there also no usb debugging is working!
and how do you install the adb drivers in the zip?
even though it is in debugging mode..when i try to root, it says please connect your phone in debugging mode
Can't say if it generally works with virtualbox. try to get drivers for your native system.
So the question is now: What's your host system?
If it's Windows, get Flashtool and install included driver (found in <FlashtoolInstallDir>\driver) just for rooting the device.
If you're using linux you can look if your device was recognized properly with lsusb it should be listed there.
You can try it too in virtualbox, but i don't trust the USB-driver (i would not flash or so through it) and do not recommend it.
murderered said:
Can't say if it generally works with virtualbox. try to get drivers for your native system.
So the question is now: What's your host system?
If it's Windows, get Flashtool and install included driver (found in <FlashtoolInstallDir>\driver) just for rooting the device.
If you're using linux you can look if your device was recognized properly with lsusb it should be listed there.
You can try it too in virtualbox, but i don't trust the USB-driver (i would not flash or so through it) and do not recommend it.
Click to expand...
Click to collapse
i am using windows 7 32 bit
ive already have flashtool and have tried to install the drivers but nothing works!
Ok, you've installed (i assume) the right adb drivers for your device through the installer located in <FlashtoolsInstallDir>\driver.
So is there any Android/Sony (Ericsson) named device in your device manager? What does Flashtools write if you connect? If your device is listed in device manager, does it show an error, if yes which error?
murderered said:
Ok, you've installed (i assume) the right adb drivers for your device through the installer located in <FlashtoolsInstallDir>\driver.
So is there any Android/Sony (Ericsson) named device in your device manager? What does Flashtools write if you connect? If your device is listed in device manager, does it show an error, if yes which error?
Click to expand...
Click to collapse
in flashtool it shows the same thing in on and off
the 2nd one is debugging on and 3rd with off
Please post output of "adb devices" (if not recognizing, try again after "adb usb"). If no serial number/device is shown then do following:
There is a newer version of Flashtool available, update to 0.9.11, http://androxyde.github.io/
check after reinstallation (of drivers, too)
Maybe you have to try sonys driver from the zip. So extract them (all files).
right click at your device in the device manager
click to "update driversoftware" (or something like that, i don't have english windows)
click "search on my computer for new drivers"
choose from list
display all devices
click the button below the list (i have no idea what there could be written, it's not "windows update")
search for the inf-file extracted and choose the "sa<somenumbers>adb.inf"
if not already installing, choose "Sony Ericsson saXXXX ADB Interface Driver"
reboot (pc)
check again
Basically my phone stops being recognized by the computer once I reboot into the bootloader. To be clear, the phone is recognized just fine and shows up when I type 'adb devices' when the phone is operating in the android os. Seeing that all is well there, I proceed to 'adb reboot bootloader' and it appropriately reboots to the white screen with the android on it. But there the problems begin: It reads on the screen:
FASTBOOT&RESCUE MODE
Please Connect Usb Cable to
Your Computer and Open Hisuite
More information:
the huawei website
Then it displays the droid
Then it says:
Phone Locked
FRP Unlock
I tried going ahead and running 'fastboot oem unlock ###...' but it just sits there waiting for a device to be connected. I have tried multiple USB drivers on my 2 windows 10 computers. I have removed all drivers using USBdeview and tried different drivers. Windows will not allow me to point to manualy choose my driver, instead saying, 'The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems.' So I tried it on an old 32-bit windows 7 system. No joy. I've tried multiple USB cords and ports. In windows device manager it has the device labeled as 'Kedacom USB Device' -> 'Android Bootloader Interface'. I can't figure out what's going wrong other than to say it seems that Windows is not using the correct driver once it enters the bootloader. PLEASE HELP!!!
Surely you have a drivers problem.
Are you using Huawei or Google adb drivers?
I couldn't find any Huawei drivers. So I used the drivers from Android developer site and several others I found here on XDA. If you have a link for specific Huawei drivers that would be AWESOME!
Try HiSuite.
Sent from my Galaxy Tab 3 using XDA Labs
ajalogan said:
I couldn't find any Huawei drivers. So I used the drivers from Android developer site and several others I found here on XDA. If you have a link for specific Huawei drivers that would be AWESOME!
Click to expand...
Click to collapse
Have you tried this?
http://semantic.gs/huawei_handset_adb_interface_driver_download
Google ADB should be fine.
i just unlocked bootloader few hours ago... i using adb driver from this thread , and it worked for me http://forum.xda-developers.com/showthread.php?t=2588979
and i also installed HIsuite before that...
seii3 said:
i just unlocked bootloader few hours ago... i using adb driver from this thread , and it worked for me http://forum.xda-developers.com/showthread.php?t=2588979
and i also installed HIsuite before that...
Click to expand...
Click to collapse
Did you used Huawei oficial site to get unlock code or did you used a 3rd party method?
zinko_pt said:
Did you used Huawei oficial site to get unlock code or did you used a 3rd party method?
Click to expand...
Click to collapse
Huawei official website
same issue, different flavor....
I'm having this issue as well, on a debian system. I have good ADB connectivity, all ADB commands seem to work fine. With fastboot, I get a device listed form them fastboot devices command. After that all fastboot commands are "waiting for device". If this is a driver issue, any hints on how to install those drivers in Linux/Debian? I tried a number of google searches, and have found all sorts of information, but nothing telling me where to put which files where to get the working drivers. Any hints?
Are you on Windows? Check if the device manager shows the device as Android with an exclamation mark inside a yellow triangle.
The problem could be with Windows 8.1/10.
Try with Windows 7
Here are the official drivers for Windows x64, ripped from Hisuite:
Mediafire | MEGA
Windows 10 is fine, it's what I use and have zero problems. Most of the time is other software that conflicts.
I'm facing the exact same issue (using Windows 10). I did the oem unlock using the code from Huawei. However after connecting the phone via cable to the PC, it does not allow me to browse the storage (internal or SD card) of the phone. All I see is a device named KIW-L24 which appears as an empty folder, and a virtual CD drive HiSuite. I installed HiSuite and the software shows me the photos/apps/etc. however there is no way to move files from the PC to the phone storage. Any pointers to the process to install the right drivers?
can you give me the link for huawei official win X32 drivers pls?!
Install hisuite , it will install all huawei drivers that u needed
my mi a3 is not recognized when in fastboot mode by the computer
I had this problem just some couple of hours ago and what you have to do (or at least it solved this in my end) is go to Manage Devices, scroll to TP-Link Android Phone, expand it and right click Android Bootloader Interface and uninstall without deleting the driver, then refresh for hardware changes and it will install the driver again and fastboot will work this time.
Jhon_Locke said:
I had this problem just some couple of hours ago and what you have to do (or at least it solved this in my end) is go to Manage Devices, scroll to TP-Link Android Phone, expand it and right click Android Bootloader Interface and uninstall without deleting the driver, then refresh for hardware changes and it will install the driver again and fastboot will work this time.
Click to expand...
Click to collapse
I'm facing this same issue. Please can you tell me where I can see Manage Devices on my computer? I'm using Windows 10.
I had the same issue. I tried all the methods that i researched. Even tried virtual machines running Windows 7 and Linux but same thing happens. I thought it was a Windows 10 issue. Til 1 day i tried to use a different cable, and DAMN! that fixed it.
same here, recognized as adb device but not recognized by fastboot.
I'm using Linux and fastboot work well.
The problem is that with lsusb no device is displayed, so I think it's a bootloader issue, is the bootloader environment corrupted? is there other setting to enable other then enable usb debug and enable OEM unlock?
Go to device manager right klik on android device and update the driver automatic.thats all.
U had the same problem and i solved with this.
Probably you don't have installed correctly fastboot drivers
Barbiox Dogg said:
I'm facing this same issue. Please can you tell me where I can see Manage Devices on my computer? I'm using Windows 10
Click to expand...
Click to collapse
im late but if u still need to know then hold down windows and x, a list should come up and then click device manager from there
deniloo said:
my mi a3 is not recognized when in fastboot mode by the computer
Click to expand...
Click to collapse
Just Update the device driver probably be showing under others in Device manager.
Visit this site to get the driver for your device. https://www.getdroidtips.com/download-latest-xiaomi-usb-drivers/
Dears,
How has this issue just "disable driver signature enforcement"
Search youtube on this and follow instruction
Say thanks if it help please,
So, I have searched Reddit and other sites for clues and help and I have had no luck. I have even contacted an android developer and had him try on his computer and had no luck.
I am trying to install Lineage OS for 17.1 and am currently trying to root my device. I have downloaded Google USB Drivers directly and tried from Android Studio. It detects my device fine. I go into command and run adb device, it detects my device. I reboot the device into fastboot, windows detects the driver but has no driver to install. I manually install the driver and it says it "Windows could not find the drivers for your device" despite me pointing it to "...AppData\Local\Android\Sdk\extras\google\usb_driver" which is where the driver is located. I click let me pick, install it under Andoid Devic -> Android Bootloader Interface. It says "Successfully Updated Driver" but put the device in "Other Devices" with a "?" on the icon and "Unknown Device". Even tried to see if it still worked but no device was detected (fastboot device). The Google Pixel C is "Waiting for fastboot command . . . . " but that's it.
Tried both drivers downloaded. Windows updated and no driver download. Restart windows countless times. New usb cable. Different usb port including usb 2 and 3. Nothing.
Developer reported same. Any ideas appreciated!
Thanks!
@slitterell
Never had troubles with ADB and/or Fastboot drivers.: I'm on Windows 10, too.
Use the ones as attached
jwoegerbauer said:
@slitterell
Never had troubles with ADB and/or Fastboot drivers.: I'm on Windows 10, too.
Use the ones as attached
Click to expand...
Click to collapse
Sorry for the slow response.
Same issue. I wouldn't expect otherwise though because the ones straight from Android Studio and Googles website doesn't work. Still shows "Unknown Device" and won't let me install the driver after showing "Waiting for fastboot command. . . ."
Drivers work fine until in fastboot mode.
Waiting for fastboot command. . . .
@slitterell
I'm pretty sure the USB driver ( does NOT mean ADB and/or Fastboot drivers ) you've installed is the culprit: Uninstall it and install the one suitable at 100% to your phone, will say the Google USB driver.
I don't disagree with you except I literally downloaded the the drivers and they won't install on either computer saying they are incompatible and they are the ones literally off the google website.
@slitterell
The mentioned Google USB Driver is required for Windows if you want to perform adb debugging with Google devices.
So it should be the correct USB-driver in your case.
The latest is attached.
slitterell said:
I don't disagree with you except I literally downloaded the the drivers and they won't install on either computer saying they are incompatible and they are the ones literally off the google website.
Click to expand...
Click to collapse
Google's driver package doesn't have Product ID of the Pixel C mentioned in its inf file, so it doesn't work for you. Interesting that you got adb connection anyway. So, maybe Windows has installed automatically some driver but it didn't had entry for the bootloader/fastboot.
Here is how people have added those adb entries. Bootloader entry can be found from device manager and added the same way...
https://stackoverflow.com/questions/34775508/where-is-the-windows-adb-driver-for-the-pixel-c
Or you could just use my Yet Another Universal ADB Driver Package
https://forum.xda-developers.com/an...staller-universal-adb-driver-package-t3595277
http://yet-another-universal-adbdriver.blogspot.com/
and hope for the best...