Hi,
i have problem with my Novo 7 Paladin. One week ago i installed Google Maps update. After that my tablet was very strange. Sometimes when it go to sleep it won't wake up. I had to press power on again. Later that week there was some graphical glitch on screen (blinking colors). And now i can't boot at all. So i tried the SD card method to recover system. The problem is that i can't boot. Combination of keys like VOL+ and POWER or VOL+ and RESET doesn't work. Then i tried the original USB Boot Tool from Ainol. This tool doesn't work either.
USB Boot Tool
1) install correct USB drivers (press VOL+ and plug USB)
select drivers from tool/drivers/4770
2) unplug USB and start USBBootTool.exe
3) press VOL- and plug USB
4) it says BOOT... please waite0% (attachment boottool.JPG)
5) after some time of waiting the error apears (attachment boottool2.JPG)
Can someone help me please?
Great, so I can throw it away!
ErrorTM said:
Great, so I can throw it away!
Click to expand...
Click to collapse
First try to recharge it overnight, then push power button and see what happens. Anything shown on the screen?
lenik said:
First try to recharge it overnight, then push power button and see what happens. Anything shown on the screen?
Click to expand...
Click to collapse
Tested, same result.
when you connect your tablet to the PC, do you see any devices appear/disappear?
if you use linux, try lsmod (LSMOD lowercase) to see if your tablet shows on the list.
lenik said:
when you connect your tablet to the PC, do you see any devices appear/disappear?
if you use linux, try lsmod (LSMOD lowercase) to see if your tablet shows on the list.
Click to expand...
Click to collapse
I'm using Windows XP. Yes it appears in devices and install drivers.
ErrorTM said:
I'm using Windows XP. Yes it appears in devices and install drivers.
Click to expand...
Click to collapse
If it appears in devices, it's not completely dead. I don't have enough windows experience, but other people had occasional success installing correct drivers and reflashing the device using Ingenic USB Boot Tool or something like that. If the reflash process does not start, most probably it's because you have installed incorrect drivers.
lenik said:
If it appears in devices, it's not completely dead. I don't have enough windows experience, but other people had occasional success installing correct drivers and reflashing the device using Ingenic USB Boot Tool or something like that. If the reflash process does not start, most probably it's because you have installed incorrect drivers.
Click to expand...
Click to collapse
I am willing to install Linux if you think it could help.
I found xburst-tools, which i think is for flash my tablet. I used Ubuntu live distribution. Problem is that i cant even install prerequisities like libconfuse0. I dont know how to install it. Sorry im newbie in linux.
Related
Hi all
I have a problem with my hero not being recognized by my PC. This happened after a weekend trip and i charged the phone with iphone USB adapter as i lost my one and now after returning from my trip i connect my hero to my PC to be greeted with the "USB Device Not Recognized" message.
Also my Amon_Ra recovery i used has been wiped and i cant get into recovery or install any rom at all.
I am thinking this might be the same USB brick that affected some Desire owners but i am not sure.
So please if anyone can help me, please do.
Thanks in advance.
fizzle101 said:
Hi all
I have a problem with my hero not being recognized by my PC. This happened after a weekend trip and i charged the phone with iphone USB adapter as i lost my one and now after returning from my trip i connect my hero to my PC to be greeted with the "USB Device Not Recognized" message.
Also my Amon_Ra recovery i used has been wiped and i cant get into recovery or install any rom at all.
I am thinking this might be the same USB brick that affected some Desire owners but i am not sure.
So please if anyone can help me, please do.
Thanks in advance.
Click to expand...
Click to collapse
this happen to me. What i did was switch my phone off, plug in the usb and switched it back on. then wait for windows to say it not recognised. then go to to device and printers and uninstall the drivers for the phone. Disconnect and reconnect the usb back to the phone and it it will pick it up.
Can you try booting in fastboot and tell me if that is recognized?
it still doesnt recognize it in fastboot
fc_Kuro said:
this happen to me. What i did was switch my phone off, plug in the usb and switched it back on. then wait for windows to say it not recognised. then go to to device and printers and uninstall the drivers for the phone. Disconnect and reconnect the usb back to the phone and it it will pick it up.
Click to expand...
Click to collapse
i have tried that and it doesnt help
fizzle101 said:
i connect my hero to my PC to be greeted with the "USB Device Not Recognized" message
Click to expand...
Click to collapse
Sounds like its just a driver issue. Have you tried plugging it in, when you get that message open DEVICE MANAGER,... Find the yellow "!", right click it, uninstall, unplug phone, reboot PC.
.... Then use BTDAG's [Guide] How to Setup Correct Hero Drivers (for x86 & x64 users)
I hav the same problem. In recover mode it works but then turn on the phone, there is no popup options as before. Tried around with drivers but didnt work either. But found a solution which is very convenient. I dont know if it works on other ROM versions but I'm on 2.1 (Villain10).
- Install extended control widget (dont remember where I got it but you can google, it seems I cannot find it on the market)
- Add this widget to the home screen: Menu/Add to Home/Widget/ Extended Control bar (you can choose the size from 1x1 to 1x4) then select "Mass storage" at the bottom, apply.
Now you have a widget to turn on/off USB storage. When you connect Hero to the PC, just click on this widget then the PC will connect to the SD card, and click one more to turn it off.
ok i will give that a try
crk23 said:
I hav the same problem. In recover mode it works but then turn on the phone, there is no popup options as before. Tried around with drivers but didnt work either. But found a solution which is very convenient. I dont know if it works on other ROM versions but I'm on 2.1 (Villain10).
- Install extended control widget (dont remember where I got it but you can google, it seems I cannot find it on the market)
- Add this widget to the home screen: Menu/Add to Home/Widget/ Extended Control bar (you can choose the size from 1x1 to 1x4) then select "Mass storage" at the bottom, apply.
Now you have a widget to turn on/off USB storage. When you connect Hero to the PC, just click on this widget then the PC will connect to the SD card, and click one more to turn it off.
Click to expand...
Click to collapse
that didnt work. o well i guess i am stock with the rom i have there.
fizzle101 said:
that didnt work. o well i guess i am stock with the rom i have there.
Click to expand...
Click to collapse
i've got this problem once and it was as simple as the cable was damaged...
i changed the cable and since then, everything works try that.
robocik said:
i've got this problem once and it was as simple as the cable was damaged...
i changed the cable and since then, everything works try that.
Click to expand...
Click to collapse
i have tried everything. changed the cable, used different pc but nothing works. i think is a hardware problem, something might be broken inside or something like that
Did you ever got this solved? I have the same problem only i use stock rom 2.1 Hero.. driving me nuts ...
baklap said:
Did you ever got this solved? I have the same problem only i use stock rom 2.1 Hero.. driving me nuts ...
Click to expand...
Click to collapse
No i havent and i gave up trying because i dnt think there is a fix for it. if yours is unrooted and the warranty is still valid you should consider returning it to HTC maybe they might replace it
got the same problem. Any solution so far ??
ddotpatel said:
Sounds like its just a driver issue. Have you tried plugging it in, when you get that message open DEVICE MANAGER,... Find the yellow "!", right click it, uninstall, unplug phone, reboot PC.
.... Then use BTDAG's [Guide] How to Setup Correct Hero Drivers (for x86 & x64 users)
Click to expand...
Click to collapse
Did you try that?..... You need to do the reboot PC/Laptop after uninstalling ALL HTC drivers! Then when you reboot PC, plug phone back in, should say "not recognised" again,... then follow BTDAG's guide. T'is definitely a driver issue!
tried flashing 3 roms, modaco, radug and now kimera... none working.
can connect in fastboot, it shows up in device manager as android 1.0
ive tried 3 different usb cables and 4 differet pcs, still there is no response on my phone !!!
using villian rom 10.0 rite now.
okay it boots up into fastboot and fastboot usb shows up on the screen in red,
BUT when i use the "adb devices" command in adb it doesnt show the device,
it is showing as android 1.0 in devices and printers (windows 7)
You need to use....
fastboot devices
....when your are in fastboot.
What happens when you go into your recovery, select "Toggle MS/USB" with USB connected to PC?
okay
fastboot devices command shows some serial number.
then i tried adb remount, it gave an error....
enabling usb-ms with cable attached gives no response
ok i think it might be USB driver like ddotpatel said but i am not sure.
i reinstalled my whole windows 7 to 32bit now instead of the 64bit version i was using before and today i just connected my hero to my PC and windows 7 did its thing and installed the drivers and finally my hero can mount the SD card in my PC again although i kept getting this can perform faster in USB 2.0 port or something like that i didn’t care as long as i can mount my SD card again.
now went into fastboot and used the fastboot device command and i could see my hero serial no. but when i try to flash the amonra recovery i got the permission error (i cant really remember). i tried flashing using the adb method but still no luck.
so i went to market and downloaded rom manager and used it to flash clockwork recovery and now i could boot to clockwork recovery.
from this recovery i can now flash any rom i want and although there are still a few more problems i am glad now that i can flash custom roms again.
the problem i can see so far but i can deal with is
1. i don’t think fastboot commands work even if the phone is detected.
2. SD card mounts at USB 1.1 speed. (i have tried different ports and cable but still the same thing and this is the ports i use for my N1, Desire and my other android phones with USB 2.0 speed)
PS: adb commands for pushing and removing apps is working.
Hope this can be helpful to those experiencing the same problem.
Instead of re-installing your entire OS just use usbdeview to remove the failing drivers.
Also remove any old HTC Sync installs and install the latest version.
I really Need Help! My computer wont recognize my tablet in fastboot mode, and my tablet wont read my micro SD card, also when i turn it on normally it stays at splash screen and when its plugged in to the computer the computer starts installing the drivers and it fails to install each time. I go to troubleshooting options and it states code 10. which states device cannot start.
I Have looked for ways around this, like manually installing the drivers, and my computer wont let me. Also the tablet can go to both: bootloader, and Clockworkmod recovery.
I factory reset my tablet so I cannot install anything, untill i get it to connect to my computer.
I am running Windows 7 64-bit on my computer!
Any help is very much appreciated!
Thanks!
NewDev4IOS said:
I really Need Help! My computer wont recognize my tablet in fastboot mode, and my tablet wont read my micro SD card, also when i turn it on normally it stays at splash screen and when its plugged in to the computer the computer starts installing the drivers and it fails to install each time. I go to troubleshooting options and it states code 10. which states device cannot start.
I Have looked for ways around this, like manually installing the drivers, and my computer wont let me. Also the tablet can go to both: bootloader, and Clockworkmod recovery.
I factory reset my tablet so I cannot install anything, untill i get it to connect to my computer.
I am running Windows 7 64-bit on my computer!
Any help is very much appreciated!
Thanks!
Click to expand...
Click to collapse
Did you install the naked driver from here? http://forum.xda-developers.com/showthread.php?t=1426502 if not do that first once you get that working... then you should be able to fastboot to the pc... next thing I would concider is going to twrp recovery instead of cwm....either go for an older version or go the full gambit of nvflash then install the latest twrp... after that you should be set.....I can comment more on it if you need it....
Bricked Tablet Help
Gage_Hero said:
Did you install the naked driver from here? http://forum.xda-developers.com/showthread.php?t=1426502 if not do that first once you get that working... then you should be able to fastboot to the pc... next thing I would concider is going to twrp recovery instead of cwm....either go for an older version or go the full gambit of nvflash then install the latest twrp... after that you should be set.....I can comment more on it if you need it....
Click to expand...
Click to collapse
I tried installing those drivers but it didnt work
also i used WSG_Unbricker v.1.0.3
my system is wiped
is there any way to install the operating system on it
i need a link for an update.zip
thanks
i can now only go to fastboot mode and wipe data mode.
NewDev4IOS said:
I tried installing those drivers but it didnt work
also i used WSG_Unbricker v.1.0.3
my system is wiped
is there any way to install the operating system on it
i need a link for an update.zip
thanks
i can now only go to fastboot mode and wipe data mode.
Click to expand...
Click to collapse
What do you see in device manager with the tablet plugged into the pc and running in fastboot?
Maybe this helps
I had a similar issue but my tablet couldn't be identified by windows, at first i thought it was my drivers so i tried to install new ones but windows wouldn't let me stating the same code 10. At the end it was a defective usb cable, i bought a new one and everything worked all right the first time i plugged it in. And by the way i was stucked at the CWM loop. Hope this helps and sorry for my bad english.
Bricked tablet
sj010489 said:
I had a similar issue but my tablet couldn't be identified by windows, at first i thought it was my drivers so i tried to install new ones but windows wouldn't let me stating the same code 10. At the end it was a defective usb cable, i bought a new one and everything worked all right the first time i plugged it in. And by the way i was stucked at the CWM loop. Hope this helps and sorry for my bad english.
Click to expand...
Click to collapse
Thanks
Im not sure if it is a bad usb cable, i think it is my computer because my computer doesnt even recognize my iphone and i have itunes installed,
i think it is partially due to a funky computer for me.
BRICKED
Gage_Hero said:
What do you see in device manager with the tablet plugged into the pc and running in fastboot?
Click to expand...
Click to collapse
It says fastboot
I sent my tablet in to asus
just waiting on them to reply
Hi
New on here so sorry if I don't know to much
I have a Nexus 7 2012. Install Timurs kernel and Rom on my tablet and installed it in my car, and it worked great for months, then the other day it shut down. When I rebooted it, it gets stuck on the Google logo.
If I try boot into recovery it once again gets stuck at the Google Boot logo
I can get it into Fastboot mode but it wont connect to the PC. I am sure the Drivers are ok as I have another nexus 7 and i have today flashed a new rom using the WUGs Nexus Toolkit
Any Ideas anyone as at the moment I would class this as bricked as it wont boot, wont go into recovery and wont connect to the PC
Any advice would be hugely appreciated
Cheers
Aaron
aaronthew said:
Hi
New on here so sorry if I don't know to much
I have a Nexus 7 2012. Install Timurs kernel and Rom on my tablet and installed it in my car, and it worked great for months, then the other day it shut down. When I rebooted it, it gets stuck on the Google logo.
If I try boot into recovery it once again gets stuck at the Google Boot logo
I can get it into Fastboot mode but it wont connect to the PC. I am sure the Drivers are ok as I have another nexus 7 and i have today flashed a new rom using the WUGs Nexus Toolkit
Any Ideas anyone as at the moment I would class this as bricked as it wont boot, wont go into recovery and wont connect to the PC
Any advice would be hugely appreciated
Cheers
Aaron
Click to expand...
Click to collapse
You can't go into your recovery?
Install ADB and try to connect your Nexus to your PC and enter "adb devices". See if your tablet is recognized like that.
How to setup ADB
Do not use toolkits with Nexus devices.
cheers for the advice but nope no luck still wont connect
aaronthew said:
cheers for the advice but nope no luck still wont connect
Click to expand...
Click to collapse
When you plug your tab in, does it even attempt to load drivers and just fails or does it not even recognize that you plugged anything in? Make sure by checking the Device Manager as you plug / unplug. If it just doesn't load correctly, then attempt to load the Naked Universal Drivers manually and then you should be able to get things back on track at least with fastboot flashing the stock img files back to it. If the Device Manager doesn't change or show any differences when you plug in the tab, then that's a bad thing... If you can boot to the bootloader still, most likely it can be fixed. If it only boots to a black screen and when plugged in shows the APX driver, you're boned. That problem IS fixable, but only if you would have saved your blob.bin and wheelie blobs before it went down, which I am certain you didn't do as it is not a common procedure.
es0tericcha0s said:
When you plug your tab in, does it even attempt to load drivers and just fails or does it not even recognize that you plugged anything in? Make sure by checking the Device Manager as you plug / unplug. If it just doesn't load correctly, then attempt to load the Naked Universal Drivers manually and then you should be able to get things back on track at least with fastboot flashing the stock img files back to it. If the Device Manager doesn't change or show any differences when you plug in the tab, then that's a bad thing... If you can boot to the bootloader still, most likely it can be fixed. If it only boots to a black screen and when plugged in shows the APX driver, you're boned. That problem IS fixable, but only if you would have saved your blob.bin and wheelie blobs before it went down, which I am certain you didn't do as it is not a common procedure.
Click to expand...
Click to collapse
Hi
I can get to the bootloader screen and it says Fastboot mode on the tablet.
When i plug the tablet into the Pc, device manger does not refresh and the computer makes no acknowledgement at all when I plug the device in
aaronthew said:
Hi
I can get to the bootloader screen and it says Fastboot mode on the tablet.
When i plug the tablet into the Pc, device manger does not refresh and the computer makes no acknowledgement at all when I plug the device in
Click to expand...
Click to collapse
Hmm. Very odd. Typically if the bootloader is still there, the rest is easily solvable. What happens when you choose the recovery option from bootloader? Unfortunately you have to test some more things to eliminate the easy stuff. These include trying different cords, ports, and computers. If possible, see if you can try a Linux PC as well or at least a Live CD. If TWRP still loads at all and supports USB OTG, you might be able to load something from it as a long shot.
es0tericcha0s said:
Hmm. Very odd. Typically if the bootloader is still there, the rest is easily solvable. What happens when you choose the recovery option from bootloader? Unfortunately you have to test some more things to eliminate the easy stuff. These include trying different cords, ports, and computers. If possible, see if you can try a Linux PC as well or at least a Live CD. If TWRP still loads at all and supports USB OTG, you might be able to load something from it as a long shot.
Click to expand...
Click to collapse
if i choose recover, to gets stuck on the google screen
Tried different cables, Pc and PC ports no luck
I could try get linux on vm when i get home? never used it thou
Sucks man. Such a random thing and not typical of most Nexus issues. This is the only other option I can think of then: http://mobiletechvideos.mybigcommerce.com/asus-nexus-7-2012/ - Brick service. These guys are legit. They have a great reputation and I've personally used their services twice (different devices) and one was fixed while the other was a lost cause, but Josh was nice enough to refund some of the money since it didn't work. I'm guessing they would need to do what's called a JTAG service where they hook up (usually solder) a special cable to a specific port on the board and it kind of circumvents the other issues and reloads the OS back on.
Thanks for all you hep mate will prob give them a try
No problem. Good luck!
Hi there peeps!
My Xperia Z2 has gone into a bootloop, with no recovery, no boot logo, not registering ADB / fastboot drivers anymore.. BUT.. the buttons seems to work, so i may reboot it some different ways. The only indication of life it got, is the red light when booting.
Someone want to tag team with me to find the solution?
Donation will be gived to a working solution
Best regards!
There is no solution for this atm. The best way to fix it is to send it to the service center.
kimocoder said:
Hi there peeps!
My Xperia Z2 has gone into a bootloop, with no recovery, no boot logo, not registering ADB / fastboot drivers anymore.. BUT.. the buttons seems to work, so i may reboot it some different ways. The only indication of life it got, is the red light when booting.
Someone want to tag team with me to find the solution?
Donation will be gived to a working solution
Best regards!
Click to expand...
Click to collapse
I may have a solution. Red light usually means it cannot boot the kernel.
I have a simple fix. Follow this guide and make sure to download the firmware of your exact model and current software version number.
When you get to this step, on the right side don't check anything under 'WIPE', leave them blank. And under 'EXCLUDE', check everything except 'KERNEL'. Leave Kernel blank and the rest under exclude check them.
Proceed and press 'volume down' and connect the usb cable at the same time. Let the flash finish and boot the phone back up. Let me know how it goes.
Thanks! I'm trying your solution now, but i dont think it works... none of the drivers are either so. Give me some hours, i will walkthrough here
I can say, it is NEARLY dead i would think, but there must be a way somehow..
Yeah, this will not work.. It gets stuck on "HOLD THE VOLUME DOWN + PLUG THE CABLE" and both ADB and Fastboot are missing so.. It won't do anything there. Holding the Volume UP + Power reboots (that works for some reason). And the orange reboot button in the charging is working but nothing that will help me i think.
kimocoder said:
Yeah, this will not work.. It gets stuck on "HOLD THE VOLUME DOWN + PLUG THE CABLE" and both ADB and Fastboot are missing so.. It won't do anything there. Holding the Volume UP + Power reboots (that works for some reason). And the orange reboot button in the charging is working but nothing that will help me i think.
Click to expand...
Click to collapse
When the device is connected in flash mode (USB + Vol down), go to device manager and see if the device is there (may be called 'Xperia Z2" or "Unknown Device", right click and go to properties and update drivers to this. Update me how it goes. I had the EXACT same issue and it took me some time to resolve, by solving the drivers issue you can flash the kernel again without losing data.
If that doesn't work, install these drivers: http://forum.xda-developers.com/showthread.php?t=2588979
Hi!
When my went to Bootloop the only thing that woked was using sony's Pc recovery tool.
sony's Pc recovery tool
Hope this helps you out
Try Software repair on the new Xperria Companion
http://support.sonymobile.com/global-en/xperiaz2/tools/xperia-companion/
Both Sony Companion and Sony Emma are not registering the devices, but after fiddling around with VOLUME UP, VOLUME DOWN and lots of trying, at some point the device manager finds a unknown device. "hiredantispammer" may got the solution, but i will try all posted solutions right away! Post update soon
1. On "VOLUME DOWN + PLUG" the Device Manager refreshes, and the Z2 got the "red light" -- but Device Manager does not show any connected devices nor drivers needed.
2. The Sony Companion does not find the device either.
But.. i was reading about some Windows 10 driver problems, so i will try switch to Windows 7 x32 to ensure the drivers are working correctly.
Another thought.. Is it some way to put a "update.zip" on a sdcard for force installation of new kernel or anything?
Yeah, the solution is right. Hopefully Win 7 solves your driver issues. I had to reformat my laptop and install Win10 again because of driver issues when I have the exact same issue as you. Hope you get your phone working again!
Sent from my D6503 using XDA-Developers mobile app
And no, there's no other safe way to reflash the kernel. Even with an unlocked bootloader, you need fastboot drivers.
This worked for me.
Grab your original cable and make sure the phone is charged to st least 80%.
Start the pc companion and the repair program.
Hold the down key and connect to the computer.
In around 20 minutes the phone is repaired
Hope this helps.
It is important to use proper cable and not any old thing laying around. Mine would not connect until i got the original one.
Ah, charge your device fully. Reboot Windows 10 in safe mode and disable driver signature. Install device drivers. Use Sony PC companion or flashtool to fully reflash the right firmware for you device. You are still able to turn it off and on, so it should work if you do it right.
Best to first flash just the kernel and see if it boots, if it doesn't since you have the firmware files, flash everything and don't wipe data.
I have just got my phone today and have spent 5 hours trying to get to the point where the mi unlock software tells me to wait 72 hours.
I put my phone in fastboot mode and as soon as I connect it to the computer it disappears. Tried 5000 different ways to do this and even
wiped my pc with a clean install of windows but no matter what my phone is not recognized in the unlock tool. Please steer me in the right direction.
I'm sure I'm not the first person with this issue.
If I remember correctly, the unlock tool has an installable driver in the settings option. That should make the phone detectable in fastboot
satan89 said:
If I remember correctly, the unlock tool has an installable driver in the settings option. That should make the phone detectable in fastboot
Click to expand...
Click to collapse
yeah I did that
Apgibby said:
yeah I did that
Click to expand...
Click to collapse
You see the problem is within windows 10. I boot phone in fastboot mode
and my phone goes to a black screen and phone becomes unrecognized in windows.
Try using another computer, windows 7 if possible. Otherwise try using another usb cable
thunderskain said:
Try using another computer, windows 7 if possible. Otherwise try using another usb cable
Click to expand...
Click to collapse
no extra usb c cable I will install windows 7 on spare hard drive and try it again will post findings when done. thanks
I was facing the same issue, go to Device manager in Windows 10. In the View tab enable show hidden devices, then you should see Android Phone on the top. Click the right arrow and uninstall drivers under Android phone, connect your phone again and the drivers should be installed.
Windows 10 should detect your device in Fastboot mode now onwards.
Unkn0wNx said:
I was facing the same issue, go to Device manager in Windows 10. In the View tab enable show hidden devices, then you should see Android Phone on the top. Click the right arrow and uninstall drivers under Android phone, connect your phone again and the drivers should be installed.
Windows 10 should detect your device in Fastboot mode now onwards.
Click to expand...
Click to collapse
I did that and the minute I launched the unlocker the green fastboot went away and it says press any key to shut down.
Apgibby said:
I did that and the minute I launched the unlocker the green fastboot went away and it says press any key to shut down.
Click to expand...
Click to collapse
unlocker said proper driver installed but install screen stays greyed out. What a pain the butt this is.
If I recall it right you just have to go to the mi unlock site and apply, the unlock is bouund to the mi account.
Have you tried a different usb port? Heard pocophone is finicky on usb 3.0, maybe use a usb 2.0 port.
Try another USB port. It solved for me.
Apgibby said:
unlocker said proper driver installed but install screen stays greyed out. What a pain the butt this is.
Click to expand...
Click to collapse
If you are using AMD RYZEN, it won't recognise the phone. Use Intel or other AMD machines.
tnsmani said:
If you are using AMD RYZEN, it won't recognise the phone. Use Intel or other AMD machines.
Click to expand...
Click to collapse
no amd here running intel 8 series chipset tried all 6 available usb ports.
Apgibby said:
no amd here running intel 8 series chipset tried all 6 available usb ports.
Click to expand...
Click to collapse
Then try another PC/Laptop.
Apgibby said:
You see the problem is within windows 10. I boot phone in fastboot mode
and my phone goes to a black screen and phone becomes unrecognized in windows.
Click to expand...
Click to collapse
All my Xiaomi phones, including Poco F1, are recognized in Windows 10, and I've unlocked them all in Windows 10. So it shouldn't be Windows.
Why is your phone going to a black screen when you boot in fastboot mode ?
I don't know how to solve your problem though. I reboot my phone into fastboot while not connected to the PC, and it surely will show the fastboot animation screen. Then I plug in the cable to the PC, and the unlock tool will start its work.
Maybe redownload the MI unlocker tool ... or create a new MI account and re-bind that account under developer options ...
unlocking boot loader will wipe all the data right?
That is correct. You need to wait 3 days when unlocking the bootloader. That is Xiaomi's waiting period for the Pocophone.
Better than Samsung's 7 day wait, and better than LG's way of having to request an unlock key.
Sent from my POCOPHONE F1 using Tapatalk
@Apgibby
Are you putting the phone in bootloader mode, connect it to the PC and then opening the Mi Unlocker? The correct sequence is open the Unlocker, put your phone in bootloader mode and then connect it to the PC. Try it.
If still not working, open the adb command window on your PC, put your phone in bootloader mode and connect it to the PC. Now type "fastboot devices" (without the quotation marks). You should get a serial number with alphabets and numerals. If you get it, it is confirmation that your drivers for bootloader are working. Try this and let us know the result.
Lastly, try another PC.
Solved used windows 7 with usb 2.0 ports.