Hello everyone. I was trying to downgrade from emui 8.1 to emui 8 using the dload method. Everything was fine until the phone rebooted and nothing was showing on the display. I let it sit for about an hour and still nothing. The phone was completely unresponsive. Plugging it into a computer, windows recognized it as a kedacom usb device named Android bootloader interface. At this point, I tried to flash the board software using the image downloader software for Hisilicon devices. Unfortunately, it did not work and gave me error 29. I realized at this point I needed to put my phone into com1 mode, so I opened it up and found the probe point near the lcd connector. I disconnected the battery and lcd connector and plugged the phone into my laptop. I shorted that test point with ground and windows still recognized it as kedacom usb device named Android bootloader interface. I tried reinstalling the huawei drivers provided by the software, but I just can't get windows to recognize it as huawei com1 interface. Am I doing something wrong here? Is it the wrong probe point I am shorting? Any help would be appreciated! Btw the bootloader is locked and phone is not rooted.
Phone's actual configuration - for whatever reson - is to boot into it's bootloader.
Try
Code:
fastboot devices
fastboot reboot
to get phone booted in default mode.
jwoegerbauer said:
Phone's actual configuration - for whatever reson - is to boot into it's bootloader.
Try
Code:
fastboot devices
fastboot reboot
to get phone booted in default mode.
Click to expand...
Click to collapse
Yes I have tried that and still nothing shows up on the screen. Device manager still shows it as a kedacom device called android bootloader interface.
WayneSeng said:
Yes I have tried that and still nothing shows up on the screen. Device manager still shows it as a kedacom device called android bootloader interface.
Click to expand...
Click to collapse
Get rid of KEDACOM USB DEVICE DRIVER, what is for Xiaomi devices, AFAIK.
Install the HUAWEI ANDROID USB DRIVER: this driver resolves all USB connection issues between Huawei Android Smartphone / Tablet and Windows 10/8.1/7 PC. It addresses all connection issues, be it transferring files between Huawei device and PC, or debugging over ADB and Fastboot.
jwoegerbauer said:
Get rid of KEDACOM USB DEVICE DRIVER, what is for Xiaomi devices, AFAIK.
Install the HUAWEI ANDROID USB DRIVER: this driver resolves all USB connection issues between Huawei Android Smartphone / Tablet and Windows 10/8.1/7 PC. It addresses all connection issues, be it transferring files between Huawei device and PC, or debugging over ADB and Fastboot.
Click to expand...
Click to collapse
Ok, so I uninstalled the kedacom usb driver and installed the huawei usb drivers. After restarting my laptop and plugging in my phone, device manager shows it as Android phone called Android sooner single adb device. Flashing the board software using Hisilicon image tool gave me error 39.
WayneSeng said:
Flashing the board software using Hisilicon image tool gave me error 39.
Click to expand...
Click to collapse
Can't help you further: don't have a device based on Hisilicon Kirin chipset.
jwoegerbauer said:
Can't help you further: don't have a device based on Hisilicon Kirin chipset.
Click to expand...
Click to collapse
What do you mean? I have a mate 10 pro bla-al00 with a kirin 970 chipset. My issue is not with connection, but with getting the phone into com1 mode and flashing the board firmware in order to unbrick the phone. Here is a tutorial I am following to do this: https://www.youtube.com/watch?v=SJxKH_unwAI&ab_channel=GSMTechZambia
I just can't get the phone into com1 mode. I short the testpoint shown in the video to ground with a piece of wire and all it does is reset the connection and device manager shows an adb device not the com port. Is it the wrong test point I am shorting to ground or am I doing something else wrong? Thanks
WayneSeng said:
What do you mean? I have a mate 10 pro bla-al00 with a kirin 970 chipset. My issue is not with connection, but with getting the phone into com1 mode and flashing the board firmware in order to unbrick the phone. Here is a tutorial I am following to do this:
I just can't get the phone into com1 mode. I short the testpoint shown in the video to ground with a piece of wire and all it does is reset the connection and device manager shows an adb device not the com port. Is it the wrong test point I am shorting to ground or am I doing something else wrong? Thanks
Click to expand...
Click to collapse
If You didnt solve, take a look at this:
HUAWEI MATE 10 HARD BRICK
Hello, i have a hard bricked Huawei mate 10 ALP-l29 with all partitions deleted. Bootloader is locked and no chance to unlock. Tried all services - nothing! Is it any hope? I like this phone damn.
forum.xda-developers.com
Related
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
I have just got my phone today and have spent 5 hours trying to get to the point where the mi unlock software tells me to wait 72 hours.
I put my phone in fastboot mode and as soon as I connect it to the computer it disappears. Tried 5000 different ways to do this and even
wiped my pc with a clean install of windows but no matter what my phone is not recognized in the unlock tool. Please steer me in the right direction.
I'm sure I'm not the first person with this issue.
If I remember correctly, the unlock tool has an installable driver in the settings option. That should make the phone detectable in fastboot
satan89 said:
If I remember correctly, the unlock tool has an installable driver in the settings option. That should make the phone detectable in fastboot
Click to expand...
Click to collapse
yeah I did that
Apgibby said:
yeah I did that
Click to expand...
Click to collapse
You see the problem is within windows 10. I boot phone in fastboot mode
and my phone goes to a black screen and phone becomes unrecognized in windows.
Try using another computer, windows 7 if possible. Otherwise try using another usb cable
thunderskain said:
Try using another computer, windows 7 if possible. Otherwise try using another usb cable
Click to expand...
Click to collapse
no extra usb c cable I will install windows 7 on spare hard drive and try it again will post findings when done. thanks
I was facing the same issue, go to Device manager in Windows 10. In the View tab enable show hidden devices, then you should see Android Phone on the top. Click the right arrow and uninstall drivers under Android phone, connect your phone again and the drivers should be installed.
Windows 10 should detect your device in Fastboot mode now onwards.
Unkn0wNx said:
I was facing the same issue, go to Device manager in Windows 10. In the View tab enable show hidden devices, then you should see Android Phone on the top. Click the right arrow and uninstall drivers under Android phone, connect your phone again and the drivers should be installed.
Windows 10 should detect your device in Fastboot mode now onwards.
Click to expand...
Click to collapse
I did that and the minute I launched the unlocker the green fastboot went away and it says press any key to shut down.
Apgibby said:
I did that and the minute I launched the unlocker the green fastboot went away and it says press any key to shut down.
Click to expand...
Click to collapse
unlocker said proper driver installed but install screen stays greyed out. What a pain the butt this is.
If I recall it right you just have to go to the mi unlock site and apply, the unlock is bouund to the mi account.
Have you tried a different usb port? Heard pocophone is finicky on usb 3.0, maybe use a usb 2.0 port.
Try another USB port. It solved for me.
Apgibby said:
unlocker said proper driver installed but install screen stays greyed out. What a pain the butt this is.
Click to expand...
Click to collapse
If you are using AMD RYZEN, it won't recognise the phone. Use Intel or other AMD machines.
tnsmani said:
If you are using AMD RYZEN, it won't recognise the phone. Use Intel or other AMD machines.
Click to expand...
Click to collapse
no amd here running intel 8 series chipset tried all 6 available usb ports.
Apgibby said:
no amd here running intel 8 series chipset tried all 6 available usb ports.
Click to expand...
Click to collapse
Then try another PC/Laptop.
Apgibby said:
You see the problem is within windows 10. I boot phone in fastboot mode
and my phone goes to a black screen and phone becomes unrecognized in windows.
Click to expand...
Click to collapse
All my Xiaomi phones, including Poco F1, are recognized in Windows 10, and I've unlocked them all in Windows 10. So it shouldn't be Windows.
Why is your phone going to a black screen when you boot in fastboot mode ?
I don't know how to solve your problem though. I reboot my phone into fastboot while not connected to the PC, and it surely will show the fastboot animation screen. Then I plug in the cable to the PC, and the unlock tool will start its work.
Maybe redownload the MI unlocker tool ... or create a new MI account and re-bind that account under developer options ...
unlocking boot loader will wipe all the data right?
That is correct. You need to wait 3 days when unlocking the bootloader. That is Xiaomi's waiting period for the Pocophone.
Better than Samsung's 7 day wait, and better than LG's way of having to request an unlock key.
Sent from my POCOPHONE F1 using Tapatalk
@Apgibby
Are you putting the phone in bootloader mode, connect it to the PC and then opening the Mi Unlocker? The correct sequence is open the Unlocker, put your phone in bootloader mode and then connect it to the PC. Try it.
If still not working, open the adb command window on your PC, put your phone in bootloader mode and connect it to the PC. Now type "fastboot devices" (without the quotation marks). You should get a serial number with alphabets and numerals. If you get it, it is confirmation that your drivers for bootloader are working. Try this and let us know the result.
Lastly, try another PC.
Solved used windows 7 with usb 2.0 ports.
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,
I own the TV BOX TRANSPEED_H616 (Allwinner H616, Arm Mali-G31 MP2, Android 10, 4/64 GB).
I would like to root but can't. I can't even connect the device to the PC.
When I connect it with the USB-OTG cable, in the device manager it shows "USB device unknown (device descriptor request failed)" and I cannot find the drivers. Can someone help me?
Thank you
i have same problem.
After several attempts I managed to enter recovery mode.
I would like to root the device now but I don't know how to do it.
Can anyone help me?
Thank you
Since no one can help me, I want to try to summarize everything I understand using this device. The first thing to do is to enable the developer option and then check USB DEBUG and USB0. At this point, by connecting the USB cable to the OTG input, the device is recognized by the PC as MPT. By opening the Phoenixsuite or Powershell application from the SDK folder you can send commands to the device, you can access the custom recovery and nothing more. Unfortunately, the bootloader cannot be unlocked, and the firmware cannot be changed either through the PC or even with SD. When entering Bootloader mode the PC loses connection with the device because it changes to an unknown device without drivers. Also with Powershell if you want to unlock the bootloader this is not possible because when you send the command "./fastboot flashing unlock" it returns the message "Failed". By inserting the SD card with the firmware and starting the device with a stick inserted in the AV input and the electrical AC connector, a red indicator lights up on the display and the flashing does not start. Clearly in these conditions it is impossible to think about rooting the device. I hope that in the light of what has been said, someone can give me some research ideas or useful advice. Finally I apologize for my English (from Google)
Hello, recently I bought a transpeed X88 pro s (from transpeed official) , h616, 4gb+128gb with android 10.
But it is a fake, it's a board with hacked firmware (dispute is open) , it only have 64gb ( chip Samsung Klmcg2ketm), it warm so much (more than 90°C) with faults on gpu (changing colors, slowly,...), only way to work is with open box or fan.
Anyway, I'm in the way to root and change firmware too.
It's rooted by default, with supersu 1.82 work well and permit restart to bootloader (with reset button was impossible).
I will inform about progress.
2 days ago my cousin left his phone in charge and at morning his phone was stuck at huawei logo.
1) I can only access fastboot&rescue mode and when i access it shows the phone state as "Phone Locked FRP Lock"
2) oem and usb debug is not active (i cannot boot phone so i am not able to open them)
3) bootloader is locked so i can't flash any recovery.img boot.img etc.
4) I tried test point method but test point is not working (not showing huawei usb at device manager)
I am currently living in Turkey, warranty is over and technical service said that it has a motherboard issue and asks for like 100$ (1500 Turkish Liras) for to change / fix motherboard.
How can i fix this phone?
Krali said:
not showing huawei usb at device manager)
Click to expand...
Click to collapse
Do you have this driver installed on your PC?
Huawei USB COM 1.0
-Alf- said:
Do you have this driver installed on your PC?
Huawei USB COM 1.0
Click to expand...
Click to collapse
I am not sure i have this driver (when i try to install it without usb port it throws an error) but when i ground the test point it shows as Android ADB Interface not Huawei USB COM 1.0
I am trying to test point while i am at fastboot screen because at huawei logo nothing is showing up and i can only access fastboot. (There is a fix on the internet, when they modify their connection cable to short circuit red and green cables with 10k resistor it allowed test point, i did that also but didn't work for me. )