Hello,
I am currently in a dead end with my Poco F1, and would like to check with you before throwing it away.
I was using my Poco in version 12.0.3.0 with TWRP installed and root with Magisk. Due to the last days errors of apps that shut down when opened, I decided to reinstall the system using TWRP, but I made a mistake and installed version 12.0.2.0.
I don't know what installing this version did, but now the mobile isn't starting MIUI anymore, it's starting by default TWRP. Furthermore, something has been changed in the TWRP version installed that touchsreen it's not responding, so I can´t use.
The problem is worse since, for a long time the transfer of files to a PC via USB cable isn't working on my Poco, so Windows is not able to detect the mobile in fastboot mode either. I tryied reinstalling drivres in many ways, and still not working. The poco charges perfectly, so I don't think the problem is the USB conector, maybe is a motherboard related issue, so changing the connector I don't belive will solve the problem
Recap:
- I can't start MIUI (the version has been corrupted).
- I can't use TWRP (it has been corrupted and the touch screen does not work).
- I can't install from fastboot (Windows isn`t detecting the Poco with the cable connected).
- I don't think changing USB connector solve de USB data transfer problem.
Any ideas or should I throw away the smartphone?
For me it's a real pitty, because I don't like the new Poco F3 or others phones on the market, most of them don't have 3.5mm jack or microsd card slot, and are bigger, heavier and more expensive than the Poco F1.
Thanks to everyone.
slumpp said:
Hello,
I am currently in a dead end with my Poco F1, and would like to check with you before throwing it away.
I was using my Poco in version 12.0.3.0 with TWRP installed and root with Magisk. Due to the last days errors of apps that shut down when opened, I decided to reinstall the system using TWRP, but I made a mistake and installed version 12.0.2.0.
I don't know what installing this version did, but now the mobile isn't starting MIUI anymore, it's starting by default TWRP. Furthermore, something has been changed in the TWRP version installed that touchsreen it's not responding, so I can´t use.
The problem is worse since, for a long time the transfer of files to a PC via USB cable isn't working on my Poco, so Windows is not able to detect the mobile in fastboot mode either. I tryied reinstalling drivres in many ways, and still not working. The poco charges perfectly, so I don't think the problem is the USB conector, maybe is a motherboard related issue, so changing the connector I don't belive will solve the problem
Recap:
- I can't start MIUI (the version has been corrupted).
- I can't use TWRP (it has been corrupted and the touch screen does not work).
- I can't install from fastboot (Windows isn`t detecting the Poco with the cable connected).
- I don't think changing USB connector solve de USB data transfer problem.
Any ideas or should I throw away the smartphone?
For me it's a real pitty, because I don't like the new Poco F3 or others phones on the market, most of them don't have 3.5mm jack or microsd card slot, and are bigger, heavier and more expensive than the Poco F1.
Thanks to everyone.
Click to expand...
Click to collapse
Hello,
The issue with error of apps was probably due Webview which Google pushed an update and fixed it. For more infos read here.
Now, to the current problem...how did u flashed previous version? Clean installed or Dirty installed?
What Desktop system do you use? AMD or Intel? Your PC can detect the device while you are on TWRP? Do you have twrp.img on ur device so you can reflash it via TWRP?
Check my POCO F1 Ultimate Collection & Guides
Retrial said:
Hello,
The issue with error of apps was probably due Webview which Google pushed an update and fixed it. For more infos read here.
Now, to the current problem...how did u flashed previous version? Clean installed or Dirty installed?
What Desktop system do you use? AMD or Intel? Your PC can detect the device while you are on TWRP? Do you have twrp.img on ur device so you can reflash it via TWRP?
Check my POCO F1 Ultimate Collection & Guides
Click to expand...
Click to collapse
Thanks for your answer.
I noticed that the issue with the apps is due to webview after breaking my phone, next time I'll think things twice before flashing anything.
I did a dirty installation, I thought I was installing same version (12.0.3.0), but I was flashing 12.0.2.0 on top of 12.0.3.0 without cleaning.
I tried both desktop systems: my laptop with an Intel CPU, and a PC with AMD Ryzen 9 3900X. I also tried 5 diferent USB-C cables that are working perfectly with others Android devices. When I look for new devices in the device manager of windows I can't tell any diference on listed devices with or without connecting the Poco. As I said, maybe I have some hardware issue in the phone, because file transfer was not working for many months.
I can't install anything via TWRP because touchscreen don`t respond to mi fingers... I remerber that this happend to me years ago when I installed a wrong TWRP version, but don't know if that is the problem.
slumpp said:
Thanks for your answer.
I noticed that the issue with the apps is due to webview after breaking my phone, next time I'll think things twice before flashing anything.
I did a dirty installation, I thought I was installing same version (12.0.3.0), but I was flashing 12.0.2.0 on top of 12.0.3.0 without cleaning.
I tried both desktop systems: my laptop with an Intel CPU, and a PC with AMD Ryzen 9 3900X. I also tried 5 diferent USB-C cables that are working perfectly with others Android devices. When I look for new devices in the device manager of windows I can't tell any diference on listed devices with or without connecting the Poco. As I said, maybe I have some hardware issue in the phone, because file transfer was not working for many months.
I can't install anything via TWRP because touchscreen don`t respond to mi fingers... I remerber that this happend to me years ago when I installed a wrong TWRP version, but don't know if that is the problem.
Click to expand...
Click to collapse
Are you able to to connect your device while u are on TWRP? Your PC recognize it?
Retrial said:
Are you able to to connect your device while u are on TWRP? Your PC recognize it?
Click to expand...
Click to collapse
I tried to connect the device with TWRP opened, and in fastboot mode, PC don't recognize in any case.
slumpp said:
I tried to connect the device with TWRP opened, and in fastboot mode, PC don't recognize in any case.
Click to expand...
Click to collapse
Well, somehow you need to manage to flash MIUI again via TWRP or Mi Flash Tool.
Perhaps if you redownload latest twrp.img and latest official miui 12.0.3.0 and transfer them to USB OTG or external SD Card and then put ur OTG or external SD Card to your phone and flash it from TWRP. Since you was able to wipe system as u said before you will be able to flash twrp.img into "Recovery" make Clean Install (according my guide) and flash MIUI.
I'll try if connecting something via OTG make the phone responds, but the main problem with TWRP is that appears to be corrupted or something. I cann't use it because touchscreen don't responds to me, and nothing happens either if I try to use it with volume+ and volume- buttons, I see TWRP but I can`t interact with it.
Thanks again for your patience.
Retrial said:
Well, somehow you need to manage to flash MIUI again via TWRP or Mi Flash Tool.
Perhaps if you redownload latest twrp.img and latest official miui 12.0.3.0 and transfer them to USB OTG or external SD Card and then put ur OTG or external SD Card to your phone and flash it from TWRP. Since you was able to wipe system as u said before you will be able to flash twrp.img into "Recovery" make Clean Install (according my guide) and flash MIUI.
Click to expand...
Click to collapse
I tried using OTG cable in TWRP and nothing hapens, TWRP don't respond.
Seems that I'm in a dead end, I ordered an USB PCB spare part to try if is posible to repair the USB data transfer connection replacing it, becuase looks like is the only way I have of flashing a new clean rom.
slumpp said:
I tried using OTG cable in TWRP and nothing hapens, TWRP don't respond.
Seems that I'm in a dead end, I ordered an USB PCB spare part to try if is posible to repair the USB data transfer connection replacing it, becuase looks like is the only way I have of flashing a new clean rom.
Click to expand...
Click to collapse
If you have AMD system try the AMD Fix in my guide. Also try this guide to install drivers.
Finally I could solve the problem.
I bought a new part of the USB port PCB from aliexpress, I ordered one that claims to be original for around 15€, not the 2€ ones.
I replaced it and the data transfer is working again, so I could install the ROM via fastboot from my PC.
I don't beleive that the PCB I replaced is original, but works like it is, phone charges properly and seems that didn't loose signal.
Thanks to everyone.
Related
Hey,
I have been using CM12.1 Nightlies since January, and I've been experiencing bugs related to USB recognition. Yesterday I've updated to CM13 thinking that it would solve this issue, but it haven't.
What happens is that I can't use USB storage/MTP/Odin/direct plug adb because my phone doesn't get recognized by the OS. I think that the USB port is not damaged because I can charge it when connected to my PC . I used to have CM11 and it worked fine, I think that maybe it is something related to the build itself..?
I have already tried a lot of methods, USB debug on/off, different cords, OSes (Tried on Windows, Mac, Linux), multiple adb/samsung drivers, apps.. nothing has worked so far.
I can only access the internal data using an external SD card or through network adb.
I think that the USB module was overwritten, because it looks undentified in every device that I've tested.
Has anyone experienced something like that? any tips, tests, or patches that I've missed?
Thanks.
Did you install Google USB Driver? I had to install this one to get my device on CM 13 recognized. It should work "out-of-the-box" on Linux distros though if you've got libmtp installed (for MTP browsing).
matee89 said:
Did you install Google USB Driver? I had to install this one to get my device on CM 13 recognized. It should work "out-of-the-box" on Linux distros though if you've got libmtp installed (for MTP browsing).
Click to expand...
Click to collapse
The device doesn't get recognized by Windows, it doesn't even show up on the connected devices list. The funny thing is that the phone actually charges, so it is not a dead usb connection...
I think that I'll have to replace the USB PCB...
Hello,
i tried to flash twrp to my i9100.
I had cm12.1 with cyanogen recovery and tried to apply update for :
"recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab)"
and
"kernel-Lanchon-TRIM-IsoRec-20160207-cm-13.0-i9100"
but know my phone is not starting anymore.
I already know that i used 13 kernel for 12.1 system and that was wrong.
I can access ODIN Mode but my pc (win10) and Odin v.3.10 don´t recognize my S2.
Can you tell me how to solve my problem?
i9100cm said:
Hello,
I can access ODIN Mode but my pc (win10) and Odin v.3.10 don´t recognize my S2.
Can you tell me how to solve my problem?
Click to expand...
Click to collapse
Try reinstalling Samsung USB drivers. If that didn't work then try it on another computer.
Now my S2 is getting recognized again.
But i geht the error code 43.
The device description is failured.
Kevin3014 said:
Try reinstalling Samsung USB drivers. If that didn't work then try it on another computer.
Click to expand...
Click to collapse
Kevin, how to flash lanchon kernel without recovery?
because my recovery is cyanogenmod recovery cm13 it cannot update from sdcard..
Abdullah Yusoff said:
Kevin, how to flash lanchon kernel without recovery?
because my recovery is cyanogenmod recovery cm13 it cannot update from sdcard..
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...es/guide-want-to-update-to-cm13-read-t3313978
Read this thread, it has the answer to your question.
Hey, OP here.
So just updating my status, I bought and replaced the Micro-USB connector and everything is working now, the device is recognized by the OS and I'm able to use use Odin/ADB normally.
If anyone out there is having the same issue, I recommend buying a new Micro-USB PCB. This phone is from 2011, batteries and connectors might stop working...
Thanks everyone for helping me out!
Thyrr said:
Hey,
I have been using CM12.1 Nightlies since January, and I've been experiencing bugs related to USB recognition. Yesterday I've updated to CM13 thinking that it would solve this issue, but it haven't.
What happens is that I can't use USB storage/MTP/Odin/direct plug adb because my phone doesn't get recognized by the OS. I think that the USB port is not damaged because I can charge it when connected to my PC . I used to have CM11 and it worked fine, I think that maybe it is something related to the build itself..?
I have already tried a lot of methods, USB debug on/off, different cords, OSes (Tried on Windows, Mac, Linux), multiple adb/samsung drivers, apps.. nothing has worked so far.
I can only access the internal data using an external SD card or through network adb.
I think that the USB module was overwritten, because it looks undentified in every device that I've tested.
Has anyone experienced something like that? any tips, tests, or patches that I've missed?
Thanks.
Click to expand...
Click to collapse
hey..if no method works for you i have simple way..to turn on usb debugging and for odin (means from this way odin will recognose your mobile)...just flash the new simple custom rom with lower android versions and then turn on usb debuging mode....thats all ...i also strucked in this problem but i did this and all works fine...sry for my bad english and typing
Hello guys, I got a Z2 which the USB port is not working, neither to charge or to transfer data, I have to charge it with a magnetic charger. I had successfully rooted and installed TWRP through WiFi ADB and then flashed latest sony stock BETA. A week after that I notice that the recovery was gone! No led flashes on boot and I couldn't enter in TWRP, so I thought that I need to get it back, because I can't use USB on it so TWRP is the only way the have backups and so. I tried to reinstall TWRP through WiFi ADB but then the nightmare began... After the Z2 rebooted, BOOTLOOP!
I know, I should fix the USB port, but I can't do it right now, it's kind of expensive here in Brazil...
So, is there anyway to get it working again without the USB?
Unfortunately no.
Sorry dude.
You need working usb port for that.
You could try ordering the component from China (like aliexpress etc), it should be cheaper there.
Sent from Note 3, Xiaomi Redmi Note 3.
Hello,
I have a small problem concerning the USB-C port.
After connecting my bluetooth earphones, the terminal was stuck in headset mode. I tried to format data, to install again the rom, I made a factory reset, I tried different rom AOSP ... nothing
When I connect wired headphones, the sound works but when I disconnect them no sound works (phone calls and media for speakers or earpiece). I know the earpiece and loudspeaker are working because I tried SoundAbout under android 7.1.0, but this application does not work with android 8.1.0 or 9.0-Alpha
File transfer does not work either, but when I connect my device fastboot, adb recognizes it, when I connect it via android, only charge works.
I think the problem is related to the USB-C port, I cleaned it but it does not change anything ...
Maybe there is another solution that I have not explored yet ...
Thank you for your help.
Best regards
(sorry for my english)
Max.
The Max 2 X829 (treblized)
Android 9.0 alpha (AospExtended-v6.0-x2-20180908-1833-ALPHA)
Hi,
I downgraded to Android 8.1.0 [AOSPExtended [treble] V5.7-official] then I rebooted the system with the charging cable plugged and the sound came back ... weird :cyclops:
But If I reboot without the charging cable, the terminal stays into headset mode...
Data still not working
I don't know why ?
Someone get an idea ? What is the problem ? Any solution ?
thanks
Hello
sorry for a bit of necro
I also have the problem.
I use Audio Router from playstore which works like Sound About but is compatible with 8+ Android.
I also have problems that appeared all of a sudden at the same time:
- same faulty sound behaviour
- usb mtp/adb not available (under recovery and under Android)
- It also seems that my battery will not charge as fast as before though Quick charge is enabled.
pluging/unpluging will not bring the notification to modify the usb link behaviour.
I also tried enabling/disabling usb debugging options...
This happened after trying/flashing many roms so I don't really know which one would have caused evil :/
Do any treble rom could harm the device like this by altering the vendor partition or has it nothing to do with it ?
about usb under pie roms :
The options are greyed under Usb Preferences.
In developer mode, changing the default usb behaviour does nothing.
I have tried 2 USB C cables.
Both are working with my X820 only in bootloader mode.
And both are working fully with my second LeEco (x525).
So i don't think the cables are faulty.
And as it is working also in bootloader mode I suspect there is some lockdown somewhere hidden in my partitions.
But I can't find anything.
I also fully restored the X820 to stock and the problem remains.
under eui roms :
Same problem
No usb configuration available
If anybody could help that would be awesome.
thanks in advance
I would recommend you to reflesh phone with qfil.
kihope12 said:
I would recommend you to reflesh phone with qfil.
Click to expand...
Click to collapse
Thanks for replying.
I have already done that (full qualcomm reflash with FlashOne & QFil image).
The problem still occurs.
This is very strange behaviour...
The phone is pretty new and I did not make it fall or whatever missuse.
The usb-c is still working in FastBoot Mode (but not mtp/usb file transfer nor usb debugging/Adb) and I can still charge the phone when not using it.
And about the audio problem it can be fixed with an app (audio router/sound about/...) so I am pretty sure it is pure software issue but I can't find any more information about this.
Is there any other system internal partition or else that is not flashed with every rom (other than vendor) and that could be different amongst the x82x devices ?
I have also tried flashing some modem files (not all) maybe this can be linked to this problem ?
Thanks
sirnonox said:
Thanks for replying.
I have already done that (full qualcomm reflash with FlashOne & QFil image).
The problem still occurs.
This is very strange behaviour...
The phone is pretty new and I did not make it fall or whatever missuse.
The usb-c is still working in FastBoot Mode (but not mtp/usb file transfer nor usb debugging/Adb) and I can still charge the phone when not using it.
And about the audio problem it can be fixed with an app (audio router/sound about/...) so I am pretty sure it is pure software issue but I can't find any more information about this.
Is there any other system internal partition or else that is not flashed with every rom (other than vendor) and that could be different amongst the x82x devices ?
I have also tried flashing some modem files (not all) maybe this can be linked to this problem ?
Thanks
Click to expand...
Click to collapse
It looks like software, when does it stoped
working?
kihope12 said:
It looks like software, when does it stoped
working?
Click to expand...
Click to collapse
I am not really sure because I installed many roms for geekly testing purpose
And I can't remember exactly since when It happened...
I ordered my phone from China so I got a chinese eui and modem version but I don't remember which modem version it was...
though I am not sure it can be important or not here...
Currently I went back to SmallEui by Aurel.
This sound exactly like the problem I have.
I am sure it is not hardware related. I even replaced the usb port/flex cable.i don't know which ROM brought me to this stage. Maybe it was linage 15.1, build 20181201, but I don't think it's linage's fault. Because flashing an other ROM doesn't help.
Is there any partition that is not touched by flashing qfil zip file?
Maybe someone can provide twrp backup of all partitions that are reachable by twrp. Hopefully we can find the wrong part this way.
Regards
Jo
So yesterday I flashed again with qualcomm qfil (2 or 3 times) and I finally got back the audio, usb (debugging, mtp and charge).
I do not understand why but the at 1st attempt the audio problem was still here
at the second attempt the audio problem disappeared but my internal storage went partitioned down from 64 Gb to 16 GB
and finally at the third attempt It worked though I had to perform a final factory Reset from Android Settings because the internal storage was filled up to 50 Gb with leeco default garbage....
Everything looked good then and I was happy at last!
But then today suddenly it stopped working again...
I don't know what exactly is in cause...
since yesterday
- I played around with the usb-c / jack audio adapter
- I restored my apps
- I plugged the phone in another usb-c power cable (with magnet pin)
I will try again to fully restore and see what exactly is in cause of the problem...
The other Usb-C seems to be problematic though I am not sure it is the only one to possibly cause the issue....
So, this is after searching for around 7-8 hours for a solution. My poco f1's usb port is somehow broken. By broken, I mean it charges perfectly fine, but will not get recognized by any other device (tried 3 different pcs, both ryzen and intel).
About 4 months ago i bought my poco f1, and installed lineageOS as soon as i could. Had some hiccups, but in the end everything was fine.
About 3 days ago I ended up trying to switch to pixel experience rom, since people were enjoying that more than lineag. I ended up getting an error saying i needed firmware from MIUI 9.2.15 or something. Alright, I'll just flash miui and then flash pixel experience... right? Well, apparently this also overrides twrp recovery and makes it boot into xiaomi's useless miui recovery. This makes it so that you cant get back into twrp without a computer. Great, now I guess ill just connect it to my pc... annnd... nothing.
Enabling every usb debugging setting, changing the usb networking to file transfer, rebooting, factory resetting and repeating everything leads to a dead end. Tried 4 different usb cables with absolutely no results. Tried 3 different pcs, nothing. And after all this, the phone charges completely fine as if nothing is wrong. The device isnt rooted either, meaning i cant manually boot into twrp using their app.
My device's bootloader IS unlocked, leading to my only possible solution i can think of: achieving root somehow since the bootloader is unlocked and downloading the TWRP app and rebooting into twrp. Or i should just yeet this on ebay and get a new poco.
Help?
Crimson123 said:
So, this is after searching for around 7-8 hours for a solution. My poco f1's usb port is somehow broken. By broken, I mean it charges perfectly fine, but will not get recognized by any other device (tried 3 different pcs, both ryzen and intel).
About 4 months ago i bought my poco f1, and installed lineageOS as soon as i could. Had some hiccups, but in the end everything was fine.
About 3 days ago I ended up trying to switch to pixel experience rom, since people were enjoying that more than lineag. I ended up getting an error saying i needed firmware from MIUI 9.2.15 or something. Alright, I'll just flash miui and then flash pixel experience... right? Well, apparently this also overrides twrp recovery and makes it boot into xiaomi's useless miui recovery. This makes it so that you cant get back into twrp without a computer. Great, now I guess ill just connect it to my pc... annnd... nothing.
Enabling every usb debugging setting, changing the usb networking to file transfer, rebooting, factory resetting and repeating everything leads to a dead end. Tried 4 different usb cables with absolutely no results. Tried 3 different pcs, nothing. And after all this, the phone charges completely fine as if nothing is wrong. The device isnt rooted either, meaning i cant manually boot into twrp using their app.
My device's bootloader IS unlocked, leading to my only possible solution i can think of: achieving root somehow since the bootloader is unlocked and downloading the TWRP app and rebooting into twrp. Or i should just yeet this on ebay and get a new poco.
Help?
Click to expand...
Click to collapse
Maybe your usb port is broken, but if you have root you can flash twrp using apps such as flashify. Won't be much use since usb might be broken. Try going to a service center nearby to get it fixed.
Crimson123 said:
So, this is after searching for around 7-8 hours for a solution. My poco f1's usb port is somehow broken. By broken, I mean it charges perfectly fine, but will not get recognized by any other device (tried 3 different pcs, both ryzen and intel).
About 4 months ago i bought my poco f1, and installed lineageOS as soon as i could. Had some hiccups, but in the end everything was fine.
About 3 days ago I ended up trying to switch to pixel experience rom, since people were enjoying that more than lineag. I ended up getting an error saying i needed firmware from MIUI 9.2.15 or something. Alright, I'll just flash miui and then flash pixel experience... right? Well, apparently this also overrides twrp recovery and makes it boot into xiaomi's useless miui recovery. This makes it so that you cant get back into twrp without a computer. Great, now I guess ill just connect it to my pc... annnd... nothing.
Enabling every usb debugging setting, changing the usb networking to file transfer, rebooting, factory resetting and repeating everything leads to a dead end. Tried 4 different usb cables with absolutely no results. Tried 3 different pcs, nothing. And after all this, the phone charges completely fine as if nothing is wrong. The device isnt rooted either, meaning i cant manually boot into twrp using their app.
My device's bootloader IS unlocked, leading to my only possible solution i can think of: achieving root somehow since the bootloader is unlocked and downloading the TWRP app and rebooting into twrp. Or i should just yeet this on ebay and get a new poco.
Help?
Click to expand...
Click to collapse
Found any solution for this. I am facing the same issue
kiranbala003 said:
Found any solution for this. I am facing the same issue
Click to expand...
Click to collapse
Try change ur port usb. Use port 2.0, not 3.0. Intel pc, not other.
tiennhu89 said:
Try change ur port usb. Use port 2.0, not 3.0. Intel pc, not other.
Click to expand...
Click to collapse
Yup. Tried everything. Still not detecting
Are you using the cable that comes out of the box ?
Some third party cables don't transfer data.
(Can be the case for deteriorated cables too)
If You trying with Windows make batch file for example:
c:\usb-fix.bat
@Echo off
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "osvc" /t REG_BINARY /d "0000" /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipContainerIdQuery" /t REG_BINARY /d "01000000" /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipBOSDescriptorQuery" /t REG_BINARY /d "01000000" /f
Start cmd as Administrator and restart PC, then will work on Windows.
Everything was working fine until I auto-updated xiaomi.eu to 11.0.10. Now it's on 11.0.11 and I still have the same problem.
Tried downgrading but just got bootloops, no big deal because I didn't want to clean flash.
BUT. I'm pretty sure this update somehow broke my USB port. Can anybody else confirm/deny/offer assistance?
Thank you.
ext23 said:
Everything was working fine until I auto-updated xiaomi.eu to 11.0.10. Now it's on 11.0.11 and I still have the same problem.
Tried downgrading but just got bootloops, no big deal because I didn't want to clean flash.
BUT. I'm pretty sure this update somehow broke my USB port. Can anybody else confirm/deny/offer assistance?
Thank you.
Click to expand...
Click to collapse
I'd suggest downloading the stock ROM (fastboot version) for your variant and flashing it with MiFlash. Take care as to not lock the bootloader by unticking 'lock' option in MiFlash else you'll get a hardbrick
I had a similar problem with mi note 10 pro, it was working fine with an .eu rom, by mistake I installed a chinesse rom, it was deleted the TWRP and the mode fastboot doesn't work since that. I could returned to the global rom using edl. and still now with the global rom only adb is working it is possible to put the mobile into fastboot mode but it isn't recognized by the PC, I have tried a lot of PC and drivers and still doesn't work, I and ending up thinking that perphas there is some king of physical damage in the USB port.
charlie11 said:
I had a similar problem with mi note 10 pro, it was working fine with an .eu rom, by mistake I installed a chinesse rom, it was deleted the TWRP and the mode fastboot doesn't work since that. I could returned to the global rom using edl. and still now with the global rom only adb is working it is possible to put the mobile into fastboot mode but it isn't recognized by the PC, I have tried a lot of PC and drivers and still doesn't work, I and ending up thinking that perphas there is some king of physical damage in the USB port.
Click to expand...
Click to collapse
I can help you with this. If adb is working then fastboot should work too.