Develop Bugs

i have bootloader unlock allowed: no!!! i want into FASTBOOT mode!!!

i can not into FASTBOOT mode
why i press the search button connect the USB
i cant see the blue led and into the charging mode, blue light for two seconds, into orange LED
not find new hardware
just SEMC Mass Storage USB Drive
oh come im f**king dead
has been installed adb package
===============================
OKAY finally, I find the problem
bootloader unlock allowed: no
SIMLOCK
How do I into FASTBOOT mode
use testpoint? s1tool? for free? help me PLZ~

Are you sure you have all the correct drivers installed?

yes, but connect the USB did not prompt new hardware

No Worries...
You have me here,
first you should have ADB installed (adb package including fastboot)
second you should have SEUS (sony Ericsson Update service) and in some cases instead of SEUS you may have SE pc suite.
Turn off your phone,after 10 seconds turn it on again and connect the USB cable while holding back key.
simply extract adb package somewhere,navigate to that folder via CMD
Type:
fastboot devices
now there should be a connected device...:good:
Feel Free To Press My THX Button

peter_dizai said:
You have me here,
first you should have ADB installed (adb package including fastboot)
second you should have SEUS (sony Ericsson Update service) and in some cases instead of SEUS you may have SE pc suite.
Turn off your phone,after 10 seconds turn it on again and connect the USB cable while holding back key.
simply extract adb package somewhere,navigate to that folder via CMD
Type:
fastboot devices
now there should be a connected device...:good:
Feel Free To Press My THX Button
Click to expand...
Click to collapse
thanks man
i try it.

peter_dizai said:
You have me here,
first you should have ADB installed (adb package including fastboot)
second you should have SEUS (sony Ericsson Update service) and in some cases instead of SEUS you may have SE pc suite.
Turn off your phone,after 10 seconds turn it on again and connect the USB cable while holding back key.
simply extract adb package somewhere,navigate to that folder via CMD
Type:
fastboot devices
now there should be a connected device...:good:
Feel Free To Press My THX Button
Click to expand...
Click to collapse
i need adb package i cant find it

There you go!
metalbug said:
i need adb package i cant find it
Click to expand...
Click to collapse
http://developer.android.com/sdk/index.html

orion4000 said:
http://developer.android.com/sdk/index.html
Click to expand...
Click to collapse
not find new hardware
just SEMC Mass Storage USB Drive
oh come im f**king dead
has been installed adb package

You can't get into fastboot mode if your bootloader is locked.
Try doing a little searching in these forums. These questions have been asked and answered many times before.
Sent from my R800x using xda premium

He speaks the truth! Also, if youre simlocked too than theres no way to unlock for free. If youre not simlocked and youre not CDMA then you can just go on sonys site to unlock your bootloader. Otherwise you need to get your bootloader unlocked, which will run you ~$24, just use the goog.

metalbug said:
not find new hardware
just SEMC Mass Storage USB Drive
oh come im f**king dead
has been installed adb package
Click to expand...
Click to collapse
You Need to Unlock your Bootloader First then try to download and install the drivers for your device.. the main driver called (S1boot fastboot) here hopefully it would help you.. http://forum.xda-developers.com/showthread.php?t=1317531

orion4000 said:
You Need to Unlock your Bootloader First then try to download and install the drivers for your device.. the main driver called (S1boot fastboot) here hopefully it would help you.. http://forum.xda-developers.com/showthread.php?t=1317531
Click to expand...
Click to collapse
no man, you dont have my idea, my device dont have blue led, and dont find new hardware "S1 boot" just only "SEMC Mass Storage USB Drive"

Oh sorry!
metalbug said:
no man, you dont have my idea, my device dont have blue led, and dont find new hardware "S1 boot" just only "SEMC Mass Storage USB Drive"
Click to expand...
Click to collapse
Sorry brother i'm trying to help! i will look for more solutions for you!

orion4000 said:
Sorry brother i'm trying to help! i will look for more solutions for you!
Click to expand...
Click to collapse
thanks man, find only way it pay for unlock

True the only way to unlock you bootloader is to pay there is no "free" way. If you need your bootloader unlocked I recommend Alejandrissmo.

BL unlocked allowed no but Iam unlock it
netizenmt said:
You can't get into fastboot mode if your bootloader is locked.
Try doing a little searching in these forums. These questions have been asked and answered many times before.
Sent from my R800x using xda premium
Click to expand...
Click to collapse
Hey man ! Ive got an xperia play R800i and Iam unlock with the S1Tool and this is worked for me and my phone said BL unlocked allowed : NO , but i cant get into fastboot mod , but the flashtool said my bootloader status : ROOT and the S1Tool the same thing . Well i guess if the bootloader status isnt rootable , but if you unlock it , the FASTBOOT NOT GONNA WORK ......

netizenmt said:
You can't get into fastboot mode if your bootloader is locked.
Try doing a little searching in these forums. These questions have been asked and answered many times before.
Sent from my R800x using xda premium
Click to expand...
Click to collapse
well today i RElock my bootloader with Xperia_relock.ftf file with flash tool. i have the same probelm with the drivers. i cant enter fastboot. And now i want to unlock it again but how to do that if when we enter to fastboot, the device connect to flash mode can i unlock it?

Geodoomer said:
well today i RElock my bootloader with Xperia_relock.ftf file with flash tool. i have the same probelm with the drivers. i cant enter fastboot. And now i want to unlock it again but how to do that if when we enter to fastboot, the device connect to flash mode can i unlock it?
Click to expand...
Click to collapse
same here..any solution anyone?

[Q] Can Not get ADB and Fastboot drivers to install

Windows 7 x64
Galaxy Nexus i515, BROKEN SCREEN, USB DEBUGGING WAS NOT TURNED ON. The phone is completely stock I just turned it on and used it until I broke my screen. Screen lock is on.
I have been trying to access my phone, using Fastboot, to wipe it before I send it in for warranty. I can not seem to do this at all. It seems that I can not install the drivers because I have not enabled USB debugging. Is this true? I have been following this guide : http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/2/ When i go to manually install the drivers, from SDK, I get, "The folder you specified does not contain a compatible software driver for your device. If the folder contains a driver, make sure that it is designed to work with Windows for x6-based systems." I then tried the driver from Samsung and got the same response.
So then I hold VOL+ _ VOL- and Power and tried to install the drivers for Fastboot with the same outcome as above. Also when I boot in Fastboot mode the drivers that are installed make my phone a modem. The driver is called, "SAMSUNG Mobile USB Modem." I can not get this to change.
So to summarize I can not get the ADB Drivers to install, because I do not have USB Debugging enabled, that in return will not allow me to install Fastboot Drivers because when I plug the phone in the computer sees it as a Modem.
Any suggestions? I am just trying to erase the info on my phone I have given up all hope of recovering any data.
Thanks,
qualm

USB debugging drivers/interface have nothing to do with fastboot drivers/interface. What's a screen lock?
a manta wrote this.

beekay201 said:
USB debugging drivers/interface have nothing to do with fastboot drivers/interface. What's a screen lock?
a manta wrote this.
Click to expand...
Click to collapse
I meant a screen pattern lock. When you wake up the screen you have to connect the dots in a certain pattern before your screen unlocks and you can use the phone.
As far as, USB debugging drivers/interface having nothing to do with fastboot drivers/interface, then what am I doing wrong? I can not get my computer to see my phone as an android device.

_qualm_ said:
I meant a screen pattern lock. When you wake up the screen you have to connect the dots in a certain pattern before your screen unlocks and you can use the phone.
As far as, USB debugging drivers/interface having nothing to do with fastboot drivers/interface, then what am I doing wrong? I can not get my computer to see my phone as an android device.
Click to expand...
Click to collapse
I know what a screen pattern lock is.
Uninstall all drivers, reboot pc.
Assuming device is off: press power+vol up+vol down, until you feel the vibration. Wait 2 secs or so. Device will be in fastboot mode.
Read this thread, i say again, READ this thread, obviously start with the first post! - http://forum.xda-developers.com/showthread.php?t=1812959

Thanks for the link. I read it and followed instructions for installing the drivers. Here is what I did:
1.Uninstalled all drivers
2.Rebooted my PC
3.Downloaded these Drivers, as suggested: http://forum.xda-developers.com/showthread.php?t=1379875
4.Followed these instructions, on how to install the driver without windows trying to find one automatically: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
Everything seemed to go well under the Device Manager, when I plug my phone in in fastboot mode, it shows Android Phone -> Samsung Android Interface. This is way better than what I had before, when it was showing up as a Modem. Now when I try to use fastboot.exe and I type "fastboot devices" nothing shows up. I reset the computer and replugged in my device, in fastboot, and the same thing nothing shows up in fastboot.
Thanks for you help.

Did you miss the part about having to feed windows the same driver again, when connecting the device for the first time, in FASTBOOT MODE?
a maguro wrote this.

beekay201 said:
Did you miss the part about having to feed windows the same driver again, when connecting the device for the first time, in FASTBOOT MODE?
a maguro wrote this.
Click to expand...
Click to collapse
Not sure if I understand what your asking.
I followed all of the steps here: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 I connected the phone booted normally and let windows find a driver so that the driver reads Portable Devices -> Galaxy Nexus. Then I unplugged the Nexus and booted it in fastboot mode and plugged it in. Next I followed the directions to install the Universal_Naked_Driver, in fastboot mode. I can not install the driver for ADB because I can not enable USB Debugging with my broken screen.
Thanks Again.

Why is it so difficult for people to understand that USB debugging has nothing to do with anything outside the booted OS?
Sent from my Galaxy Nexus

W8 a sec, do you even have your bootloader unlocked???
You said you're running stock, so that should have been my first question, because to unlock your bootloader through the usual way, you need to confirm a dialog on the device... which in your case, doesn't have a working screen.
_qualm_ said:
Not sure if I understand what your asking.
I followed all of the steps here: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 I connected the phone booted normally and let windows find a driver so that the driver reads Portable Devices -> Galaxy Nexus. Then I unplugged the Nexus and booted it in fastboot mode and plugged it in. Next I followed the directions to install the Universal_Naked_Driver, in fastboot mode. I can not install the driver for ADB because I can not enable USB Debugging with my broken screen.
Thanks Again.
Click to expand...
Click to collapse
....
Lets see:
That post shows how it's done, correctly. (I think, from what i've read)
pay attention to part 3)
3)
NOTE:
- The method described here can be used to install the "Samsung Galaxy Nexus ADB Interface" driver as well as the "Samsung Galaxy Nexus Bootloader Interface" driver.
- Differences between the two procedures. One is done with the phone booted up normally and "USB Debugging" is enabled, and the other is done when the phone is in fastboot. I will cover the "USB Debugging" part here.
Click to expand...
Click to collapse
then...
We will now install the two drivers that efrant talked about in his post.
A) (FOR ADB - WHEN RUNNING ANDROID OS):
Enable USB debugging on your device
- Goto Settings > Developer Options > Check "USB Debugging"
- Connect device, manually update driver to Naked driver by 1wayjohny, done. On 4.2 and above, you'll need to confirm that you accept the host's (your pc) RSA key.
B) (FOR FASTBOOT - WHEN RUNNING FASTBOOT MODE)
boot into fastboot mode - power off phone and hold vol up + vol down + power
Click to expand...
Click to collapse
Both for A) and B), you need to do the "Update drivers manually" part!
Right now, your only option is B), that is to use fastboot to either:
- Flash stock images.
- To get your data back, boot a custom recovery (which won't require the RSA key confirmation for ADB) from fastboot, then use ADB to pull your /sdcard/ or whatever.

Pirateghost said:
Why is it so difficult for people to understand that USB debugging has nothing to do with anything outside the booted OS?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I am learning this ^. I am having trouble getting my computer to see my phone, in fastboot mode. All of the instructions that I have read start with installing drivers for ADB, which requires the phone to be USB debugging mode, and then the drivers for fastboot. So I thought my trouble was, since I can not install the drivers for ADB, and that I was having trouble with all of my drivers, that it was probably the fact that my phone can not be put into USB debugging mode. I now realize that USB debugging has nothing to do with fastboot, as fastboot is before the OS is booted. I am still just having trouble with my fastboot driver and seeing my phone with fastboot.exe.

beekay201 said:
W8 a sec, do you even have your bootloader unlocked???
Both for A) and B), you need to do the "Update drivers manually" part!
Right now, your only option is B), that is to use fastboot to either:
- Flash stock images.
- To get your data back, boot a custom recovery (which won't require the RSA key confirmation for ADB) from fastboot, then use ADB to pull your /sdcard/ or whatever.
Click to expand...
Click to collapse
No my bootloader is not unlocked. Is this the reason that my phone is not detected by fastboot.exe? Do I need to unlock my bootloader?
I have been trying option B, as I know this is my only option. I have been doing the "Update drivers manually" part I even tried on another PC with windows 7, to no avail. What ever I seem to do I can not see my device in fastboot.exe.

_qualm_ said:
No my bootloader is not unlocked. Is this the reason that my phone is not detected by fastboot.exe? Do I need to unlock my bootloader?
I have been trying option B, as I know this is my only option. I have been doing the "Update drivers manually" part I even tried on another PC with windows 7, to no avail. What ever I seem to do I can not see my device in fastboot.exe.
Click to expand...
Click to collapse
No. Fastboot should be able to see your device if the proper drivers are installed. Fastboot is REQUIRED to unlock the bootloader
Sent from my Galaxy Nexus

Pirateghost said:
No. Fastboot should be able to see your device if the proper drivers are installed. Fastboot is REQUIRED to unlock the bootloader
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
If you used odin to flash something, that will unlock the bootloader. Flashing a section of edited param using OMAP flash will also unlock the bootloader.
Beamed from my Maguro.

I also have the same problem with my galaxy C5.
_qualm_ said:
No my bootloader is not unlocked. Is this the reason that my phone is not detected by fastboot.exe? Do I need to unlock my bootloader?
I have been trying option B, as I know this is my only option. I have been doing the "Update drivers manually" part I even tried on another PC with windows 7, to no avail. What ever I seem to do I can not see my device in fastboot.exe.
Click to expand...
Click to collapse
My galaxy C5 is also not recognized as a bootloader interface while in fastboot mode, after installing all the drivers correctly. Samsung usb driver v1.5.63.0 makes the changes i think, and it makes it as a modem instead of bootloader. maybe the solution is i have to manually update the driver of that modem into bootloader, right click on the modem in device manager and change it's driver into bootloader of your phone, maybe it works. I will try it this way.
Let me know if this solution has worked for someone.
Thanks

HTC desire in boot loop. PLEASE PLEASE HELP!

My HTC desire 820 keeps restarting itself as it is stuck in an endless boot loop. I have come across threads speaking of the same issue but the solutions don't seem to work on my phone.
My boot loader is locked. When i try to unlock it in fastboot mode, the device doesn't show up on the PC.
I need the boot loader unlocked so that i could push in a custom recovery mode as i cant get into the stock recovery too.
Does anybody have a solution for my kind of problem?
Also, when the phone is in fastboot usb mode, the computer makes a notification sound which indicates it recognizes the phone.
The only thing i can get into is my boot loader and which looks like this now:
***LOCKED***
A51_DTUL PVT SHIP S-ON
HBOOT-3.19.0.0000
OS-3.17.708.3
eMMC-boot 2048 mb
Apr 12 2016, 11:49:54.0
NOTE: I never tried to install a custom ROM. This problem arose on its own for reasons unknown to me. Moreover, my phone is UNROOTED.
PLEASE SOMEBODY HELP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! PLEASE!
I'm clueless!

themember1993 said:
PLEASE SOMEBODY HELP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! PLEASE!
I'm clueless!
Click to expand...
Click to collapse
Have you installed the adb/fastboot drivers on your PC?
Sounds like a drivers issue to me.
Try this thread to install the drivers then try communicating with the bootloader again.
https://forum.xda-developers.com/showthread.php?t=2588979

Gibz97 said:
Have you installed the adb/fastboot drivers on your PC?
Sounds like a drivers issue to me.
Try this thread to install the drivers then try communicating with the bootloader again.
https://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Thank you for replying, friend.
I did what you asked me to do i.e. installed adb/fastboot drivers and then ran the command to identify.
But all i get is this. I have attached a screenshot of the message i'm getting in the command prompt.
What do i do?

themember1993 said:
Thank you for replying, friend.
I did what you asked me to do i.e. installed adb/fastboot drivers and then ran the command to identify.
But all i get is this. I have attached a screenshot of the message i'm getting in the command prompt.
What do i do?
Click to expand...
Click to collapse
Still a drivers issue
Try installing HTC Sync Manager from here and try again.
http://www.htc.com/us/support/software/htc-sync-manager.aspx

Gibz97 said:
Still a drivers issue
Try installing HTC Sync Manager from here and try again.
http://www.htc.com/us/support/software/htc-sync-manager.aspx
Click to expand...
Click to collapse
I had installed the htc manager again as per your instructions even though i had it on my pc earlier.
HTC sync manager doesn't detect the phone.
Nor does fastboot command in the command prompt.
i have the adb drivers installed as you asked me to install them earlier.
I get the same message "waiting for phone" in cmd. I rebooted fastboot but even that doesn't change anything.
What do i do now? Is it a hardware issue? I do not think it could be a hardware issue because the phone has never undergone physical damage. it just decided to turn itself off one unfortunate day by itself.
Is there another way? another software?

themember1993 said:
I had installed the htc manager again as per your instructions even though i had it on my pc earlier.
HTC sync manager doesn't detect the phone.
Nor does fastboot command in the command prompt.
i have the adb drivers installed as you asked me to install them earlier.
I get the same message "waiting for phone" in cmd. I rebooted fastboot but even that doesn't change anything.
What do i do now? Is it a hardware issue? I do not think it could be a hardware issue because the phone has never undergone physical damage. it just decided to turn itself off one unfortunate day by itself.
Is there another way? another software?
Click to expand...
Click to collapse
Open device manager.
Connect phone to PC. Does the device manager show a new device added?
And BTW why can't you get into the stock recovery?

Gibz97 said:
Open device manager.
Connect phone to PC. Does the device manager show a new device added?
And BTW why can't you get into the stock recovery?
Click to expand...
Click to collapse
When i select "fastboot mode" in the bootloader screen, the PC makes a connection notification sound.
And the device shows up as "Android 1.0" in Device manager.
I have attached a screenshot which shows the same.
Also, when i try any of the options in the bootloader i.e., factory reset, recovery mode, reboot or power down, the device goes back to the endless bootloop and never really lets me do anything.

themember1993 said:
When i select "fastboot mode" in the bootloader screen, the PC makes a connection notification sound.
And the device shows up as "Android 1.0" in Device manager.
I have attached a screenshot which shows the same.
Also, when i try any of the options in the bootloader i.e., factory reset, recovery mode, reboot or power down, the device goes back to the endless bootloop and never really lets me do anything.
Click to expand...
Click to collapse
Try downloading usb deview from here. Uninstall all the USB drivers, reinstall them then try again
http://downloads.tomsguide.com/USBDeview,0301-13254.html

I tried to unlock my bootloader and my phone is stuck on bootloop

I have tried to re-flash the original ftf file, but I think that I had forgot my "USB debugging" option disabled before unlocking my bootloader... I do not really know wtf is really going on... Any help?

DrunkProgrammer said:
I have tried to re-flash the original ftf file, but I think that I had forgot my "USB debugging" option disabled before unlocking my bootloader... I do not really know wtf is really going on... Any help?
Click to expand...
Click to collapse
I don't think usb debugging is necessary if you select flash mode. Just check that drivers are installed in pc properly or not.

hhjadeja007 said:
I don't think usb debugging is necessary if you select flash mode. Just check that drivers are installed in pc properly or not.
Click to expand...
Click to collapse
They are installed properly! I have fixed again my phone from bootloop when I was trying to install CWM with the same ftf that I am trying right now but it does not work this time

It surely is a problem with pc. Try using your friend's pc.
One another thing, can you enter fastboot mode?
Type fastboot devices in cmd while connecting your phone with vol- button.

PC cant detect my phone

i flash pixel experience plus and latest firmware and now my phone stuck in fastboot mode and wont detect on my pc.. i cant see it on device manager either.. whenever i try to restart it goes to stucked twrp logo.. can someone help me here?

aidenskcyu said:
i flash pixel experience plus and latest firmware and now my phone stuck in fastboot mode and wont detect on my pc.. i cant see it on device manager either.. whenever i try to restart it goes to stucked twrp logo.. can someone help me here?
Click to expand...
Click to collapse
You just have to update drivers from device manager.
Follow this, you can use the fastboot drivers either from Xiaomi or Google (if you already have them installed)
If you don't have the Android with exclamation mark, you can do it the same as shows the latest image.

SubwayChamp said:
You just have to update drivers from device manager.
Follow this, you can use the fastboot drivers either from Xiaomi or Google (if you already have them installed)
If you don't have the Android with exclamation mark, you can do it the same as shows the latest image.
Click to expand...
Click to collapse
Before i got stuck in fastboot my phone doesn't really detected in my pc even on other computers with fastboot drivers. USB File Transfer not working too, it's only charging. I'm using Havoc OS 4.8 rom and this firmware.

aidenskcyu said:
Before i got stuck in fastboot my phone doesn't really detected in my pc even on other computers with fastboot drivers. USB File Transfer not working too, it's only charging. I'm using Havoc OS 4.8 rom and this firmware.
Click to expand...
Click to collapse
And did you try what I posted? Probably you need to check which drivers you have actually installed, some of them are sometimes redundant and not necessary, what you need is the Google ADB/fastboot that it is in the Google site, and regards Xiaomi all is in the Mi flash tool and Mi Unlock tool, see to the option to install the drivers hoping that you don't need the Qualcomm 9008-USB drivers.
Of course, this is assuming that you have a data cable not only a charger cable and the issue is not with the ROM itself.

Use known good data cable!!!
Does the phone see the connection?
Is it configured properly?!!!
Try another port.
Reboot, reboot, reboot...
Event manager, check for error messages.
Disk management>scan for new disks, open from here!
Device management, update driver, rollback driver... reboot.
Meh, play with it...

SubwayChamp said:
And did you try what I posted? Probably you need to check which drivers you have actually installed, some of them are sometimes redundant and not necessary, what you need is the Google ADB/fastboot that it is in the Google site, and regards Xiaomi all is in the Mi flash tool and Mi Unlock tool, see to the option to install the drivers hoping that you don't need the Qualcomm 9008-USB drivers.
Of course, this is assuming that you have a data cable not only a charger cable and the issue is not with the ROM itself.
Click to expand...
Click to collapse
can you give me the file for fastboot? now its showing “Unknown USB Device (Device Descriptor Request Failed)”

aidenskcyu said:
can you give me the file for fastboot? now its showing “Unknown USB Device (Device Descriptor Request Failed)”
Click to expand...
Click to collapse
Are you sure your device is actually in fastboot mode with that issue "Device Descriptor Request Failed"?
The drivers are in the Mi Flash tool, when you install the tools you can see the option to install the drivers that are already included in the Mi unlock tool.
From there, just follow the steps indicated in the pictures to update them.

SubwayChamp said:
Are you sure your device is actually in fastboot mode with that issue "Device Descriptor Request Failed"?
The drivers are in the Mi Flash tool, when you install the tools you can see the option to install the drivers that are already included in the Mi unlock tool.
From there, just follow the steps indicated in the pictures to update them.
Click to expand...
Click to collapse
i tried it but it has exclamation mark in android bootloader interface.

aidenskcyu said:
i tried it but it has exclamation mark in android bootloader interface.
Click to expand...
Click to collapse
It's not showing here an exclamation mark,
Can you upload the right SS?,
Also Did you install the fastboot drivers either from Mi Unlock tool or Mi Flash tool?

Try to install ADB and FastBoot drivers for redmi note 8

If Dosent work text here

SubwayChamp said:
It's not showing here an exclamation mark,
Can you upload the right SS?,
Also Did you install the fastboot drivers either from Mi Unlock tool or Mi Flash tool?
Click to expand...
Click to collapse
yes i did install it

aidenskcyu said:
yes i did install it
Click to expand...
Click to collapse
All is here in this same sequence.

i dont know why i get this error code 10.

aidenskcyu said:
i dont know why i get this error code 10.
Click to expand...
Click to collapse
Upload the same as my pictures 2 and 3 from your device manager, from the picture 2 you can use either from Xiaomi or Google.
Delete that Kedacom USB driver and replace for the proper ones, here you have the right guide https://xiaomifirmware.com/guides-and-tips/delete-kedacom-usb-device-driver-pc/

SubwayChamp said:
Upload the same as my pictures 2 and 3 from your device manager, from the picture 2 you can use either from Xiaomi or Google.
Delete that Kedacom USB driver and replace for the proper ones, here you have the right guide https://xiaomifirmware.com/guides-and-tips/delete-kedacom-usb-device-driver-pc/
Click to expand...
Click to collapse
somehow it got detected as android bootloader interface. it got detected too in miflash and tried to flash but i got stucked in flashint system.img. after a while it shows timeout error and after that i flash twrp recovery but i got a message that my battery is very low to flash it. will my phone charge in fastboot? because it keeps bootlooping now if ii dont go on fastboot mode

aidenskcyu said:
somehow it got detected as android bootloader interface. it got detected too in miflash and tried to flash but i got stucked in flashint system.img. after a while it shows timeout error and after that i flash twrp recovery but i got a message that my battery is very low to flash it. will my phone charge in fastboot? because it keeps bootlooping now if ii dont go on fastboot mode
Click to expand...
Click to collapse
Well, at least you got your device showed, no?
To power off the device you can put it in fastboot mode, after of approximately 10 minutes if the device is not attached to your PC, it'll power off, then you can charge it.
But if your device reacts to the power charger trying to boot to nowhere, then fastboot will charge the battery but very, very slowly.
Do you have bootloader unlocked? Why not flashing it through EDL mode?, you don't need battery power to do that.