Hello everyone I am a new user
I have an old redmi 4A stuck on boot logo but recovery and fastboot are working I want to flash TWRP via fastboot but in my PC it is showing USB not recognised or unknown device in universal serial bus category and showing code 43 error in properties I have installed original ADB drivers for this device what to do please help me driver signature enforcement is also disabled what to do
just try a bunch of drivers, someone wil work, or reboot your pc.
Related
Hi all,
my sister-in-law handed me over a redmi 4x, it has a broken screen, and she wants to have the pics recovered (for a good reason!)
I can get it somehow "on", but makes a sound if I plug in a cable, in Windows the "REDMI 4X" appear, but won't display any content.
I can get it to adb, but ONLY sideload mode, not regular adb. Debugging seems to be disabled.
I can get it to fastboot, but it's not bound to my miui-account, so I can't unlock the bootloader. Neither using official Win tool, nor using fastboot unlock.
I can't boot into TWRP recovery.
In my linux logs I can see the following IDs, depending on which mode I start:
usb 2-2: New USB device found, idVendor=2717, idProduct=ff48
usb 2-2: New USB device found, idVendor=2717, idProduct=ff40
usb 2-2: New USB device found, idVendor=2717, idProduct=ff18
Anything I can do about this ?
Can I use sideload to flash recovery ?
Thanks.
Hello,
I was on 10.0.7 version, rooted with magisk.
I had error while installing 10.0.8 version, then I downloaded 10.0.7 full rom, and used flash_all_except_data.bat.
Then after rebooting, it runs infinitely on loading animation (colors bar).
When I enter in fastboot, fastboot logo is displayed, but pc doesn't recognize phone anymore (fastboot devices show nothing).
[UPDATE]
I managed to boot with wiping data from recovery (Xiaomi stock recovery).
Now I can use the phone, but I don't have wifi (maybe something messed with vendor).
And I can't flash it because it is not recognized in fastboot mode (tried 3 W10 PCs, and 1 W7, it doesn't show in device manager)...
Can you help me ?
This is because the phone presents different device identifiers to the computer in these modes, and different drivers are needed, so it is possible to have proper drivers installed for one mode, but not the other. The fastboot program is simple and will just show the < waiting for device > message forever if drivers are missing. However, the same message may appear if the drivers are installed correctly, but the phone is not in the proper state with fastboot device IDs.
Make sure you aren't using a USB 3.0 port. Trying changing ports. The USB cable might also be the problem.
try using a direct usb 2.0 port on the pc ....
Otherwise reboot everything , erase cache first ?
Fastboot erase cache
or
Keep the phone connected and reboot the recovery , the led should come on then.
Keep the phone connected in the bootloader and reboot the pc.
If the problem still exists the let me know
What's the exact error ? Waiting for device
When the phone is in the bootloader is it recognized as fastboot usb (in red text) and what does the device manager in windows say about a android phone ?
MIN313 said:
This is because the phone presents different device identifiers to the computer in these modes, and different drivers are needed, so it is possible to have proper drivers installed for one mode, but not the other. The fastboot program is simple and will just show the < waiting for device > message forever if drivers are missing. However, the same message may appear if the drivers are installed correctly, but the phone is not in the proper state with fastboot device IDs.
Make sure you aren't using a USB 3.0 port. Trying changing ports. The USB cable might also be the problem.
try using a direct usb 2.0 port on the pc ....
Otherwise reboot everything , erase cache first ?
Fastboot erase cache
or
Keep the phone connected and reboot the recovery , the led should come on then.
Keep the phone connected in the bootloader and reboot the pc.
If the problem still exists the let me know
What's the exact error ? Waiting for device
When the phone is in the bootloader is it recognized as fastboot usb (in red text) and what does the device manager in windows say about a android phone ?
Click to expand...
Click to collapse
In fastboot mode nothing shows in device manager, with 3 different cables, with 4 different computers (3x W10, 1xW7).
I tried connecting with a live cd of CentOS.
Same results, adb connect when phone is started, but when I go in fastboot mode nothings shows in lsusb or dmesg...
Looks like the phone doesn't connect to pc in fastboot, very very strange...
Hi,
I have a CC9 with Chinese version, and I want to flash the global ROM.
I've tried to unlock the bootloader with no success.
I have adb support on many computers (I've tried windows, Mac and Linux)
but in fastboot mode, no computer recognize the device, like the USB in disconnected in this mode.
Code:
C:\Users\User>adb devices
List of devices attached
f102f099 device
C:\Users\User>adb reboot bootloader
C:\Users\User>fastboot devices
C:\Users\User>
I've tried any usb driver for windows, with no success.
Does anyone have an idea? what could be problem?
same here , its is frustrating :\
ekrako said:
Hi,
I have a CC9 with Chinese version, and I want to flash the global ROM.
I've tried to unlock the bootloader with no success.
I have adb support on many computers (I've tried windows, Mac and Linux)
but in fastboot mode, no computer recognize the device, like the USB in disconnected in this mode.
Code:
C:\Users\User>adb devices
List of devices attached
f102f099 device
C:\Users\User>adb reboot bootloader
C:\Users\User>fastboot devices
C:\Users\User>
I've tried any usb driver for windows, with no success.
Does anyone have an idea? what could be problem?
Click to expand...
Click to collapse
I had this issue when trying to unlock my bootloader. Solved by using a USB 2.0 Hub. It has something to do with Xiaomi driver compatibility in Windows 10.
Hi,
I have a problem with my device, when I connect it to pc adb can see it easily but when i type "adb reboot-bootloader" it boots to fastboot but my pc doesnt see the device anymore and there is no device detected when I use "fastboot devices" command.
It used to work before windows update but now it does what I said.
Is it because of the drivers? if so can anyone send me a link to proper windows 10 drivers for china k20 pro.
I'm not rooted and no twrp. Just the stock firmware (10.3.16).
Quaczi said:
Hi,
I have a problem with my device, when I connect it to pc adb can see it easily but when i type "adb reboot-bootloader" it boots to fastboot but my pc doesnt see the device anymore and there is no device detected when I use "fastboot devices" command.
It used to work before windows update but now it does what I said.
Is it because of the drivers? if so can anyone send me a link to proper windows 10 drivers for china k20 pro.
I'm not rooted and no twrp. Just the stock firmware (10.3.16).
Click to expand...
Click to collapse
I had this problem in my Nokia 7 Plus, then i used and installed "minimal adb and fastboot" file which detected my phone in fastboot. It installs in program file with a folder named "minimal adb and fastboot"
Sent from my Redmi K20 Pro using Tapatalk
You need to enable "USB debugging" in the developper options
ImEraaz said:
You need to enable "USB debugging" in the developper options
Click to expand...
Click to collapse
It is enabled.
And ill try with the minimal adb option
Update:
Still not working
I have same problem, there is no way to recognize my 9t pro in fastboot mode... i cant do anything
First it should be intel pc
Try to install Xiaomi drivers and adb
Boot to recovery and fastboot while connecting to usb to install the drivers
Then check again
Did anyone solve this? I'm experiencing the same issue. ADB works fine, but no device is listed at all (device manager in win7 or syslog in linux) when connecting the phone in fastboot mode. It's like it wasn't physically connected at all.
simpn said:
Did anyone solve this? I'm experiencing the same issue. ADB works fine, but no device is listed at all (device manager in win7 or syslog in linux) when connecting the phone in fastboot mode. It's like it wasn't physically connected at all.
Click to expand...
Click to collapse
Try changing ports / connect to another pc
Install proper drivers .
Is your bl unlocked now ?
Got it to work under win7 with great help from this post.
What I did was:
Update to the latest miui version (to MIUI Global 11.0.3, as prompted in system settings, I hadn't bothered to update because I just want to throw miui out)
Disable OEM unlock
Reboot
Enable OEM unlock again
Reboot into fastboot
Then the phone showed up as an unknown device in Device Manager
Right clicked the device and updated the driver, chose to search for drivers in the miflash_unlock-en-3.5.1108.44\driver\xp-win7-win8 folder
The device now lists as an Android Bootloader Interface device
And now:
$ fastboot devices
e150445 fastboot
MiFlash unlock detects the phone, and I could proceed with unlocking. Still have to wait though. Tried the older-version-trick as suggested here, but that just told me to update to the latest version. Guess I'll have to wait a week then...
Hope this helps someone. This is the most tedious unlocking procedure I've encountered so far...
I use Mi 9 Transparent Edition (Ram version 12G Rom 256G) unlocked bootloader. I installed the EU rom, it's ok to use. After I locked the bootloader, it was been hard brick and i had to flash a china rom via EDL mode. I want to install global rom but in fastboot mode the computer doesn't recognize it anymore, tried everything, changed many computers still won't recognize Mi 9 in fastboot mode, so there's no way to reinstall the rom.
Please help: now how to get Mi 9 back in fastboot mode? Please help guys (
p/s : it's also lost fast charging...
WValley said:
I use Mi 9 Transparent Edition (Ram version 12G Rom 256G) unlocked bootloader. I installed the EU rom, it's ok to use. After I locked the bootloader, it was been hard brick and i had to flash a china rom via EDL mode. I want to install global rom but in fastboot mode the computer doesn't recognize it anymore, tried everything, changed many computers still won't recognize Mi 9 in fastboot mode, so there's no way to reinstall the rom.
Please help: now how to get Mi 9 back in fastboot mode? Please help guys (
p/s : it's also lost fast charging...
Click to expand...
Click to collapse
maybe is the usb cable, try with other
Naet said:
maybe is the usb cable, try with other
Click to expand...
Click to collapse
thank u very much for the answer
i tried an original cable, not working
i turn on usb debugging, oem and update the lastest driver but still not working
Head over to Device Manager, and check if your device is correctly recognized.
if your device is categorized under 'Other Devices' and has yellow triangle, then you have to install fastboot driver.
download generic usb driver below.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
after unzipping downloaded file, right click 'android_winusb.nif' file inside 'usb_driver' folder and install it.
back to the 'device manager', locate your device and right click it, and choose 'update driver'.
select 'Search driver from my Computer' - 'Select from available driver list' - find 'Android Device' from the list and select next - select 'Android ADB Interface' and select next - click yes to proceed
and voila! you successfully installed fastboot driver, your device should be recognized as Android Device and good to go.