Related
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.
Hi guys,
I have been searching for hours but I can't seem to find how to fix my problem.
I have a new Z5 Compact that I was trying to flash with the stock firmware but I somehow managed to brick it. I don't think I had the drivers installed properly when I tried to flash with flashtool but since flashtool didn't even detect my phone or appear to begin flashing it I don't know how I bricked it. Anyway after trying for hours to fix it on my own I can't seem to find the information that I need. I have installed the drivers properly as far as I can tell by allowing unsigned drivers on windows 10 but whenever I boot to flash mode the phone isn't detected. Nothing even comes up in Device Manager so there are no options to update drivers or anything. I just hold the volume down button, plug in the usb, the LED briefly flashes red before holding on green and then nothing happens. Neither Flashtool or PC Companion detect the phone and I have tried this on 2 different laptops running Windows 7 and Windows 10. If anyone has any instructions on how to get this to work on Ubuntu I'm willing to try that too as I also have Ubuntu installed but I am really at a loss for what else I can try.
Any help would be greatly appreciated.
Thank you
tokococo said:
Hi guys,
I have been searching for hours but I can't seem to find how to fix my problem.
I have a new Z5 Compact that I was trying to flash with the stock firmware but I somehow managed to brick it. I don't think I had the drivers installed properly when I tried to flash with flashtool but since flashtool didn't even detect my phone or appear to begin flashing it I don't know how I bricked it. Anyway after trying for hours to fix it on my own I can't seem to find the information that I need. I have installed the drivers properly as far as I can tell by allowing unsigned drivers on windows 10 but whenever I boot to flash mode the phone isn't detected. Nothing even comes up in Device Manager so there are no options to update drivers or anything. I just hold the volume down button, plug in the usb, the LED briefly flashes red before holding on green and then nothing happens. Neither Flashtool or PC Companion detect the phone and I have tried this on 2 different laptops running Windows 7 and Windows 10. If anyone has any instructions on how to get this to work on Ubuntu I'm willing to try that too as I also have Ubuntu installed but I am really at a loss for what else I can try.
Any help would be greatly appreciated.
Thank you
Click to expand...
Click to collapse
sounds dumb but have you tried a different port and different cable? i ran into the same problem and found out one of the ports on my laptop doesnt work for data. flashtool is a major pain, it took me three pcs to find one that it worked with and then it took a good 5 tries and reboots to have a successful flash. flashing twrp and then xpower would be easier imo.
civicsr2cool said:
sounds dumb but have you tried a different port and different cable? i ran into the same problem and found out one of the ports on my laptop doesnt work for data. flashtool is a major pain, it took me three pcs to find one that it worked with and then it took a good 5 tries and reboots to have a successful flash. flashing twrp and then xpower would be easier imo.
Click to expand...
Click to collapse
Yeah, I have tried 7 ports and 3 cables across two different pcs. There's a desktop I can try on but I'll wait until tomorrow. It's really frustrating. I just wanted to root so that I could batch install my apps from Titanium but now I have got a brick. In the time that I have spent trying to fix it I could have selected and installed all the apps individually.
tokococo said:
Yeah, I have tried 7 ports and 3 cables across two different pcs. There's a desktop I can try on but I'll wait until tomorrow. It's really frustrating. I just wanted to root so that I could batch install my apps from Titanium but now I have got a brick. In the time that I have spent trying to fix it I could have selected and installed all the apps individually.
Click to expand...
Click to collapse
keep trying, it'll work after you figure out whats wrong with your install, flashtool is real finnicky. If your already soft bricked and only want root id suggest fastboot twrp 3.0.2 then flash xpower 3.0 and be done with it. the only real reason to use flashtool is to flash a new image onto the phone because you cant take an ota.
civicsr2cool said:
keep trying, it'll work after you figure out whats wrong with your install, flashtool is real finnicky. If your already soft bricked and only want root id suggest fastboot twrp 3.0.2 then flash xpower 3.0 and be done with it. the only real reason to use flashtool is to flash a new image onto the phone because you cant take an ota.
Click to expand...
Click to collapse
Thanks for your help. So I can do that without unlocking the boot loader?
tokococo said:
Thanks for your help. So I can do that without unlocking the boot loader?
Click to expand...
Click to collapse
bootloader has to be unlocked before doing any of this.
civicsr2cool said:
bootloader has to be unlocked before doing any of this.
Click to expand...
Click to collapse
Oh, you mean to do that once I have fixed my current issue.
Hmm, I seem to be having a smiliar issue, except instead of flashmode, mine isn't detected in fastboot mode, tried a crap load of drivers and usb ports etc..
EDIT: Got it fixed after following this guide
http://forum.xda-developers.com/z5-compact/general/unlock-bootloader-z5-compact-t3236237
RaunoT said:
Hmm, I seem to be having a smiliar issue, except instead of flashmode, mine isn't detected in fastboot mode, tried a crap load of drivers and usb ports etc..
EDIT: Got it fixed after following this guide
http://forum.xda-developers.com/z5-compact/general/unlock-bootloader-z5-compact-t3236237
Click to expand...
Click to collapse
I tried following that guide but when I try to install the driver it just says "The INF file you selected does not support this method if installation". You didn't happen to have that problem and find a workaround did you?
Just an update on what I have tried if anyone has any suggestions...
I tried inserting a SIM in case that would make any difference. I have also tried it on a desktop pc as well as the two laptops now which is windows 7, 8.1 and 10. The Windows 8.1 attempt was a clean install and I used the advanced boot method to enable the installation of unsigned drivers. I had high hopes for that but it didn't work. What I find curious is there is no activity when I plug the phone in, in flash mode. If I plug it in, in fastboot mode it searches for drivers and the device appears in device manager but with flash mode I get nothing. I'm beginning to think that perhaps the device itself has a faulty flash mode.
tokococo said:
I tried following that guide but when I try to install the driver it just says "The INF file you selected does not support this method if installation". You didn't happen to have that problem and find a workaround did you?
Click to expand...
Click to collapse
Sadly no :/
I managed to flash a Z5 Compact with the same model number without any issues on the same computer that won't detect my handset so I'm pretty sure that it's an issue specific to this handset. Thanks everyone for their suggestions.
March 22 2019 - Solved because I'm an idiot. Story on page 2
Trying to Flash TWRP, but the adb packages and driver's I been using that I can find all over the internet just aren't freaking working.
Specifically it's just Fastboot giving me problems, It doesn't even detect devices.
What I need help with:
Adb communicating with Fastboot
How far I got:
Unlocked bootloader (unlock symbol when booting)
Installed plethora of Adb Driver's via Google, Xiaomi, Qualcomm
Used USBDeview to uninstall all drivers even from my past devices and try reinstalling just drivers involving Xiaomi, Poco ect...
What does work:
Adb commands recognized in Miui
Adb commands recognized in Miui Recovery as sideload (after selecting pc suite option)
Miui unlocking tool (was able to unlock and can still detect the device unlocked in Fastboot)
In Miui File Transfer & PTP mode
What I tried:
Different USB ports 2.0 & 3.0 directly in the back of the PC and the front hub
Different USB C cords with and without extension cord (even though that shouldn't matter)
Different drivers old and new
Powershell & CMD as administrator.
What's already been done before you suggest it:
2nd computer, different ports, satanic ritual, different cords, turning PC on and off again after driver installs.
Trying methods from First 5 results when you Google anything along the lines of "Poco f1 adb Fastboot not recongnized"
Uninstalling drivers and retrying
USB Debugging on, duh.
Oem unlock on, duh.
Basically it's this, clearly the device is being recongnized and being talked to, just able to unlock the device via Xiaomi unlock tool is proof enough of that it's detected in and out of Fastboot, but in a adb window via powershell or cmd-here, it's just not recongnized my device in Fastboot. In Miui or recovery theres no issue, they communicate fine.
Or if there's an alternative way to install TWRP that doesn't involve Fastboot I'm all ears on that.
If you can temporarily root it (which I wouldn't how to without fastboot) you could write the recovery directly onto its partition.
(https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/)
But I suppose you want to flash the recovery to get root. So did you try different stable roms with the Mi Flash tool? Maybe your fastboot got corrupted and it could be solved with an oreo rom. Not sure about rollback protection though.
Ah and to eliminate driver issues: you could always use a live distro like manjaro on a usb stick, install the adb package and check whether fastboot is working in the terminal.
I always go back to linux when windows has its funny moments ._.
lolmensch said:
If you can temporarily root it (which I wouldn't how to without fastboot) you could write the recovery directly onto its partition.
(https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/)
But I suppose you want to flash the recovery to get root. So did you try different stable roms with the Mi Flash tool? Maybe your fastboot got corrupted and it could be solved with an oreo rom. Not sure about rollback protection though.
Ah and to eliminate driver issues: you could always use a live distro like manjaro on a usb stick, install the adb package and check whether fastboot is working in the terminal.
I always go back to linux when windows has its funny moments ._.
Click to expand...
Click to collapse
I want the recovery so I have an option that isn't miui.
My phone isn't slow, but it's running more than a fair share of mi bloat.
lolmensch said:
If you can temporarily root it (which I wouldn't how to without fastboot) you could write the recovery directly onto its partition.
(https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/)
But I suppose you want to flash the recovery to get root. So did you try different stable roms with the Mi Flash tool? Maybe your fastboot got corrupted and it could be solved with an oreo rom. Not sure about rollback protection though.
Ah and to eliminate driver issues: you could always use a live distro like manjaro on a usb stick, install the adb package and check whether fastboot is working in the terminal.
I always go back to linux when windows has its funny moments ._.
Click to expand...
Click to collapse
Also can you roll back to 8.1 without twrp, root, or adb?
I tried rolling back via the update screen and selecting the package/downgrade, but Miui won't allow installing/flashing older software, which is something I tried before.
No one else has this problem?
Chocolina said:
No one else has this problem?
Click to expand...
Click to collapse
Why not try Flashify? It comes in the form of an apk and it only requires root, no fastboot. Through it, you can flash TWRP.
Are you connecting the phone to an Intel computer or an AMD? AMD Ryzen has an issue.
tnsmani said:
Why not try Flashify? It comes in the form of an apk and it only requires root, no fastboot. Through it, you can flash TWRP.
Are you connecting the phone to an Intel computer or an AMD? AMD Ryzen has an issue.
Click to expand...
Click to collapse
Don't you need TWRP to install root?
I haven't rooted 1st and then did recovery since the Nexus 5 days, every device I've had since has had root guides that wanted me to fastboot flash the recovery first and install root that way.
And i dont know if my pc is Ryzen, not a pc gamer so all I have is on board, but it is old amd machine running windows 10. I also don't have a monitor these days, I have my pc setup to accept remote desktop so I interact with it that way because it's rare I need a pc these days
All I know is adb works with miui and recovery (sideload) fine, it's fastboot giving me problems, and all the root guides require fastboot
Also same exact issue regarding my mi pad I just got too
https://forum.xda-developers.com/mi-pad-4/help/please-help-troubleshoot-xiaomi-t3910249
lolmensch said:
If you can temporarily root it (which I wouldn't how to without fastboot) you could write the recovery directly onto its partition.
(https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/)
But I suppose you want to flash the recovery to get root. So did you try different stable roms with the Mi Flash tool? Maybe your fastboot got corrupted and it could be solved with an oreo rom. Not sure about rollback protection though.
Ah and to eliminate driver issues: you could always use a live distro like manjaro on a usb stick, install the adb package and check whether fastboot is working in the terminal.
I always go back to linux when windows has its funny moments ._.
Click to expand...
Click to collapse
Tell me more about this Linux/your method
I never used Linux, so I don't know what I'd do to get it or if I could boot it temporarily off of another form of storage or something.
Chocolina said:
Trying to Flash TWRP, but the adb packages and driver's I been using that I can find all over the internet just aren't freaking working.
Specifically it's just Fastboot giving me problems, It doesn't even detect devices.
Click to expand...
Click to collapse
Are you running a Ryzen PC ? Xiaomi drivers have been reported to have problems with Ryzen builds.
Dose the roms solve touch issue???????
MasterFURQAN said:
Are you running a Ryzen PC ? Xiaomi drivers have been reported to have problems with Ryzen builds.
Click to expand...
Click to collapse
How would I know if it's ryzen?
It's a prebuilt from 5 or more years ago
Chocolina said:
How would I know if it's ryzen?
It's a prebuilt from 5 or more years ago
Click to expand...
Click to collapse
If it's more than 5 years old, then it's not ryzen. Fyi Ryzen is the newest range of CPUs from AMD.
I went out and bought an Intel laptop and it still won't work!!
Found and addressed my issue, and it was because of my Stupidity and old habits keeping me from following directions. But I'm also a little angry at the directions themselves for omitting information that would have been useful to me.
So an old habit of mine is before flashing anything in fastboot, I alway run adb commands to see if my phone, fastboot, and windows are all taking to each other and playing nice. Every phone and device I've had until now hasn't had an issue.
If adb or other apps was showing me my connected devices in System and in Recovery, then why the hell wouldn't it do so in fastboot. So old habits with all my devices since 2012 have been reinforcing my behavior for years until I got this Xiaomi Pocophone and Xiaomi Mi Pad. So as a requisite I've always had and continued to check my devices in adb and performing a reboot test before performing a flash just to make sure the device was listening and taking commands.
The problem with the dozens of guides and videos I watched, none of them said that checking for device first didn't always work, so before flashing recovery I kept trying everything I could to get devices to read back in fastboot or accept a reboot command.
Then In one of the half of dozen xiaomi mi pad adb packages I downloaded, someone wrote a simple script that did the flash anyway even though checking to see the device was recognized came up empty.
Apparently I could have been sending flash commands all this time despite devices showing a blank.
So I did so on pocophone to find out devices and reboot commands didn't work but apparently flashing commands do.
I went out and bought (with the intent to return) a ****ty Intel laptop (made by RCA lmao) just to come to the conclusion that I should have just followed the guides in the first place and save myself trouble instead of relying on my past knowledge and habits.
Chocolina said:
Found and addressed my issue, and it was because of my Stupidity and old habits keeping me from following directions. But I'm also a little angry at the directions themselves for omitting information that would have been useful to me.
So an old habit of mine is before flashing anything in fastboot, I alway run adb commands to see if my phone, fastboot, and windows are all taking to each other and playing nice. Every phone and device I've had until now hasn't had an issue.
If adb or other apps was showing me my connected devices in System and in Recovery, then why the hell wouldn't it do so in fastboot. So old habits with all my devices since 2012 have been reinforcing my behavior for years until I got this Xiaomi Pocophone and Xiaomi Mi Pad. So as a requisite I've always had and continued to check my devices in adb and performing a reboot test before performing a flash just to make sure the device was listening and taking commands.
The problem with the dozens of guides and videos I watched, none of them said that checking for device first didn't always work, so before flashing recovery I kept trying everything I could to get devices to read back in fastboot or accept a reboot command.
Then In one of the half of dozen xiaomi mi pad adb packages I downloaded, someone wrote a simple script that did the flash anyway even though checking to see the device was recognized came up empty.
Apparently I could have been sending flash commands all this time despite devices showing a blank.
So I did so on pocophone to find out devices and reboot commands didn't work but apparently flashing commands do.
I went out and bought (with the intent to return) a ****ty Intel laptop (made by RCA lmao) just to come to the conclusion that I should have just followed the guides in the first place and save myself trouble instead of relying on my past knowledge and habits.
Click to expand...
Click to collapse
Thank you for the info. I learnt something new today.
I also have the same habit of checking whether the adb devices and fastboot devices commands work before starting any flashing. However I don't check the reboot command. It still is a good habit notwithstanding what you have discovered. What happened to you has not happened to me so far, so I am filing this knowledge for future use if the occasion arises.
tnsmani said:
Thank you for the info. I learnt something new today.
I also have the same habit of checking whether the adb devices and fastboot devices commands work before starting any flashing. However I don't check the reboot command. It still is a good habit notwithstanding what you have discovered. What happened to you has not happened to me so far, so I am filing this knowledge for future use if the occasion arises.
Click to expand...
Click to collapse
It was a headache because my precautions weren't working. Next time I'm just going to check if it'll take flash commands anyway before asking for help.
On the plus side, I got to learn what a laptop made by RCA is like. It's **** sure, I'd expected as much, but it was as bad, if not worse than those $99 "windows 8" tablets from 2014-2015 running those archaic Intel Z3735 Atom series processors. Stay away
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.
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.