Hello everyone I hope I'm doing this right.
I have a bricked lenovo, first I was trying to recover the modem path (flashed by mistake and lose the efs and imei data). I used first lenovo smart assistance, it recover well the phone but none modem fix, then I tried to recover using qfil tool and now I got my device bricked, it just turn on the led into a red light when I plugged in. My pc just recognised as a Qualcomm HS USB QDLOADER 9008.
I hope anyone can help me, I'll be very grateful.
Greetings and have a nice day!
Enviado desde mi hi6210sft mediante Tapatalk
Turbonanox said:
Hello everyone I hope I'm doing this right.
I have a bricked lenovo, first I was trying to recover the modem path (flashed by mistake and lose the efs and imei data). I used first lenovo smart assistance, it recover well the phone but none modem fix, then I tried to recover using qfil tool and now I got my device bricked, it just turn on the led into a red light when I plugged in. My pc just recognised as a Qualcomm HS USB QDLOADER 9008.
I hope anyone can help me, I'll be very grateful.
Greetings and have a nice day!
Enviado desde mi hi6210sft mediante Tapatalk
Click to expand...
Click to collapse
I got the same problem, i flashed my phone with QFIL, after, got a hard brick My lenovo vibe k5 a6020l37, any solution?
Log QFIL when try flashing a rom:
Sahara Version: 0.
Start Sending Programmer
Download Fail Unable to download Flash Programmer using Sahara protocol
Download Fail: Sahara FailSahara Fail
Finish Download.
My phone is reconize in the PC like "qualcomm hs-usb qdloader 9008 " in the devices
just turn on the led into a red light when I plugged in. My pc just recognised as a Qualcomm HS USB QDLOADER 9008. same here bro, just the red light
TrapitoZkaa said:
I got the same problem, i flashed my phone with QFIL, after, got a hard brick My lenovo vibe k5 a6020l37, any solution?
Log QFIL when try flashing a rom:
Sahara Version: 0.
Start Sending Programmer
Download Fail Unable to download Flash Programmer using Sahara protocol
Download Fail: Sahara FailSahara Fail
Finish Download.
My phone is reconize in the PC like "qualcomm hs-usb qdloader 9008 " in the devices
just turn on the led into a red light when I plugged in. My pc just recognised as a Qualcomm HS USB QDLOADER 9008. same here bro, just the red light
Click to expand...
Click to collapse
I hope some kind soul can help us with this problem [emoji20]
Enviado desde mi hi6210sft mediante Tapatalk
I got the same problem
Kimerian666 said:
I got the same problem
Click to expand...
Click to collapse
Did you solve this?
Enviado desde mi C6906 mediante Tapatalk
Please, help us.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Enviado desde mi C6906 mediante Tapatalk
Anyone solved this problem?
I have not bricked mine, but I do have problems unlocking my stock Lenovo Vibe K5. Perhaps someone can give a suggestion.
1. I installed ADB on my mac
2. Enabled USB Debugging and OEM Unlock in Developer options
3. Executed adb devices => works and shows device as "device"
4. Executed adb reboot bootloader => the phone reboots but shows only a white screen with the Lenovo logo and a text Powerkey long press can reboot phone
5. Executed fastboot flash recovery twrp-k5-3.0.3-n3_shreps.img => Shows sending 'Recovery' OKAY and finished
6. Executed adb reboot bootloader => still the white logo screen
I would expect to see a bootloader options screen (after 4 already actually)
Ah seems to be possible now to type adb reboot recovery and get into the recovery menu!
mschipperheyn said:
I have not bricked mine, but I do have problems unlocking my stock Lenovo Vibe K5. Perhaps someone can give a suggestion.
1. I installed ADB on my mac
2. Enabled USB Debugging and OEM Unlock in Developer options
3. Executed adb devices => works and shows device as "device"
4. Executed adb reboot bootloader => the phone reboots but shows only a white screen with the Lenovo logo and a text Powerkey long press can reboot phone
5. Executed fastboot flash recovery twrp-k5-3.0.3-n3_shreps.img => Shows sending 'Recovery' OKAY and finished
6. Executed adb reboot bootloader => still the white logo screen
I would expect to see a bootloader options screen (after 4 already actually)
Ah seems to be possible now to type adb reboot recovery and get into the recovery menu!
Click to expand...
Click to collapse
This does not work because we can't access the phone in order to enabled USB Debugging and OEM Unlock
Related
Hello,
I bought this product : .aliexpress.com/item/Original-Xiaomi-Redmi-Note-2-TD-TDD-Mobile-Phone-MTK6795-Octa-Core-5-5-1920X1080P-2GB/32463256279.html?spm=2114.01020208.3.1.OUID3w&ws_ab_test=searchweb201556_1_79_78_77_80,searchweb201644_5,searchweb201560_6[/url]
After few days I put developer room via mi PC manager( C: xiaomi/downloads/gucci/rom/5.11 ......) but my sound was not good.
I found on youtube video to root phone cwm or twrp some like that, I bricked my phone soft. After I try via minimal fastboot and put my phone in fastboot mode and put on MI pc manager to flash room but in middle of transfer computer show blue screen and transfer interrupted.
Now my phone turn on show Mi logo and restart, I can not enter in fastboot mode (vol down plus power btn)
I instal vcom driver preloader try 2 computer, every usb port- Sp flash tool not show red line- and after I put out cable show broom error 1013 or 2005 (i have original usb Mi cable and also try other usb cable.
I try to found test points but not have.
Please help me.
Thank in advance.
blagotan said:
Hello,
I bought this product : .aliexpress.com/item/Original-Xiaomi-Redmi-Note-2-TD-TDD-Mobile-Phone-MTK6795-Octa-Core-5-5-1920X1080P-2GB/32463256279.html?spm=2114.01020208.3.1.OUID3w&ws_ab_test=searchweb201556_1_79_78_77_80,searchweb201644_5,searchweb201560_6[/url]
After few days I put developer room via mi PC manager( C: xiaomi/downloads/gucci/rom/5.11 ......) but my sound was not good.
I found on youtube video to root phone cwm or twrp some like that, I bricked my phone soft. After I try via minimal fastboot and put my phone in fastboot mode and put on MI pc manager to flash room but in middle of transfer computer show blue screen and transfer interrupted.
Now my phone turn on show Mi logo and restart, I can not enter in fastboot mode (vol down plus power btn)
I instal vcom driver preloader try 2 computer, every usb port- Sp flash tool not show red line- and after I put out cable show broom error 1013 or 2005 (i have original usb Mi cable and also try other usb cable.
I try to found test points but not have.
Please help me.
Thank in advance.
Click to expand...
Click to collapse
Wrong preloader drivers, I guess.
Have a look at the alcatel drivers posted somewhere, those work for me.
blagotan said:
Hello,
I bought this product : .aliexpress.com/item/Original-Xiaomi-Redmi-Note-2-TD-TDD-Mobile-Phone-MTK6795-Octa-Core-5-5-1920X1080P-2GB/32463256279.html?spm=2114.01020208.3.1.OUID3w&ws_ab_test=searchweb201556_1_79_78_77_80,searchweb201644_5,searchweb201560_6[/url]
After few days I put developer room via mi PC manager( C: xiaomi/downloads/gucci/rom/5.11 ......) but my sound was not good.
I found on youtube video to root phone cwm or twrp some like that, I bricked my phone soft. After I try via minimal fastboot and put my phone in fastboot mode and put on MI pc manager to flash room but in middle of transfer computer show blue screen and transfer interrupted.
Now my phone turn on show Mi logo and restart, I can not enter in fastboot mode (vol down plus power btn)
I instal vcom driver preloader try 2 computer, every usb port- Sp flash tool not show red line- and after I put out cable show broom error 1013 or 2005 (i have original usb Mi cable and also try other usb cable.
I try to found test points but not have.
Please help me.
Thank in advance.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Redmi note 2 rom was hermes not gucci. Miflash can detected your phone? If can, then quit miflash and run windroid and selected redmi note 2. Read post #11 on this thread: http://forum.xda-developers.com/redmi-note-2/help/redmi-note-2-downgrade-upgrade-problem-t3243079. Hope it help.
Sent from my 2014817 using Tapatalk
Hello,
So I am going to unlock the bootloader on my device. However...
Adb will recognize my device but in fastboot mode it won't. Fastboot devices show nothing.
I have already installed every necessary driver (universal adb driver, miflash drivers, official xiaomi usb driver, qualcomm driver, android sdk, etc...)
But still, fastboot unable to recognize my device...
But when I plug in other device (in my case, Mi A2) in fastboot mode, it recognizes successfully. So I don't know what to do next...
My device is currently in global version 10.3.9.0.PFQMIXM (Nov security)
Any help is appreciated! Thank you.
Connect A3 to the PC and open device manager. Is the driver installed correctly (no exclamation mark)? What is the device name in device manager?
_mysiak_ said:
Connect A3 to the PC and open device manager. Is the driver installed correctly (no exclamation mark)? What is the device name in device manager?
Click to expand...
Click to collapse
It did show as Android Composite ADB interface, I tried updating those drivers as well, but won't help...
Edit: Problem solved after uninstalling and reinstalling all the related drivers, now fastboot would recognize my phone. Thanks for your help anyways.
MarcusMario0605 said:
It did show as Android Composite ADB interface, I tried updating those drivers as well, but won't help...
Click to expand...
Click to collapse
Manually reinstall drivers and choose correct device type (android bootloader if I remember correctly). Automatic installation most probably won't work on recent Windows versions.
Edit: nevermind if you already fixed it [emoji846]
Fastboot not recognized
MarcusMario0605 said:
Edit: Problem solved after uninstalling and reinstalling all the related drivers, now fastboot would recognize my phone. Thanks for your help anyways.
Click to expand...
Click to collapse
I have the same problem with a recently acquired Mi A3 running android 10 with the security update Oct 5, 2020 connecting to Win10. I have used MiUsbDriver.exe from miflash_unlock to install drivers. It is recognized by adb devices and shows up in Win10 Device Manager as shown below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
However, after adb reboot bootloader, I see the Fastboot image on the A3, but fastboot devices finds nothing and nothing shows in Device Manager. If I rerun MiUsbDriver.exe while the phone is showing the fastboot screen I get
but nothing happens when I connect and reconnect the USB cable.
I have tried multiple usb cables on 2 different Win10 machines and one linux machine with both USB 2 and USB 3 ports and have never been able to make a connection when in fastboot mode on the phone.
using the same machines and cables fastboot works fine with connections to a Pixel 2XL and a LG V20.
You mention uninstalling and reinstalling the related drivers. Which drivers are "related"?
Any other suggestions to get the PC to recognize the phone in fastboot mode?
update: the next morning, tried yet another USB cable and fastboot now recognized. No explanation.
holistone said:
I have the same problem with a recently acquired Mi A3 running android 10 with the security update Oct 5, 2020 connecting to Win10. I have used MiUsbDriver.exe from miflash_unlock to install drivers. It is recognized by adb devices and shows up in Win10 Device Manager as shown below:
However, after adb reboot bootloader, I see the Fastboot image on the A3, but fastboot devices finds nothing and nothing shows in Device Manager. If I rerun MiUsbDriver.exe while the phone is showing the fastboot screen I get
but nothing happens when I connect and reconnect the USB cable.
I have tried multiple usb cables on 2 different Win10 machines and one linux machine with both USB 2 and USB 3 ports and have never been able to make a connection when in fastboot mode on the phone.
using the same machines and cables fastboot works fine with connections to a Pixel 2XL and a LG V20.
You mention uninstalling and reinstalling the related drivers. Which drivers are "related"?
Any other suggestions to get the PC to recognize the phone in fastboot mode?
update: the next morning, tried yet another USB cable and fastboot now recognized. No explanation.
Click to expand...
Click to collapse
link??
Sami Devo said:
link??
Click to expand...
Click to collapse
"link??" to what?
holistone said:
"link??" to what?
Click to expand...
Click to collapse
software that fixed u
Sami Devo said:
software that fixed u
Click to expand...
Click to collapse
reread the update at the bottom of the post: fixed with a different USB cable, no change of software. It seems not all USB cables are created equal. I don't know how to tell in advance the difference between them. My other USB cables worked for fastboot on different phones, but only one of the cables worked with the Mi A3 fastboot.
Hi everyone! I'll explain my problem with this phone, sorry for any error because i'm italian and a complete android noob!
My girlfriend gave me her P20 lite which looks like it's bricked. She said that the phone was charging and she was speaking on the phone and suddenly the phone shut down.
Trying to reboot the phone was useless: it showed the huawei logo and then it just rebooted again. The phone only did this while under charge. If I unplug the usb cable it just tried to boot up, showed the huawei logo, shut down and then a green screen with red and blue boxes showed up for 1 second.
I tried to boot the phone with Volume up + power to enter recovery and this screen showed up: https://imgbb.com/zQ76Ywx
I tried to do option 1 and 2 but in both cases the phone just rebooted with the huawei logo and continued to reboot.
Booting the phone while pressing Volume down + power brought me in fastboot mode: https://imgbb.com/dmHQxB0
I understood that PHONE Locked and FPR Lock means that the bootloader is locked. I assume this is normale because my girllfriend is not into modding. The phone was 100% stock.
In fastboot mode i was unable to do anything. So I rebooted, unplugged the cable and just like before the green screen came up: https://ibb.co/sFWmgZv
Next step was connecting the phone to HiSuite: nothing to do, the phone was not recognised.
I tried to download a modified HiSuiteConfig.xml with support for P20 Lite, put the phone into fastboot and perform a system reset: nothing to do, it said that the phone was not supported. After trying this, The phone changed behaviour. It doesn't show anymore the huawei logo while booting, I can only see a black screen with a red led flashing followed by the green screen with red and blue boxes and continues with this loop. I am not able anymore to boot with volume up + power but only in fastboot mode.
Last thing I tried was the testpoint mode:
I downloaded this IDT Tool with firmware: https://mega.nz/file/jEoWRSAZ#sltXiQMt3kNNIEbq30WYuJTme0AoZMKRpbEtMu3-Mx4
I downloaded this driver for testpoint mode: https://androidfilehost.com/?fid=17248734326145712518
I recoreded a small video to show all the step i did:
Please note this: at the beginning the phone is connected in fastboot mode and is recognised by windows as "Android Composite ADB Interface"
Then, I reboot the phone and shortcircuiting the testpoint: the phone is recognised as "HUAWEI USB COM 1.0(COM5)"
When I start the procedure with IDT Tool after the first completed the step the phone disconnect and reconnect itself and is once again recognised as "Android Composite ADB Interface". Is it the correct behaviour?
However, the procedure fails and I couldn't find anything about error 39 of IDT Tool.
Sorry for the long message, but I wanted to explain carefully what happened.
Do you have any suggestion?
EXTRA INFO: I installed fastboot on my pc with this tool: https://forum.xda-developers.com/t/...s-adb-installer-v1-4-3.2588979/#post-48915118
I run the following commands:
fastboot oem get-product-model
...
(bootloader) ANE-LX1
OKAY [ 0.000s]
finished. total time: 0.000s
fastboot oem get-build-number
...
(bootloader) :ANE-LX1 9.1.0.381(C432E7R1P7)
OKAY [ -0.000s]
finished. total time: -0.000s
pspmaster said:
green screen with red and blue boxes
Click to expand...
Click to collapse
pspmaster said:
black screen with a red led flashing
Click to expand...
Click to collapse
Probably HW issue (emmc memory dead, out of order, or in r /o mode).
If in the process of installing the board firmware you get an error like on the screen, this confirms a memory error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I was watching the video I posted above at 0.25x speed and yes, just before failing with error 39 e can see this message. So it is an hardware issue memory related and is not fixable. The only solution would be to change the entire motherboard correct?
pspmaster said:
The only solution would be to change the entire motherboard correct?
Click to expand...
Click to collapse
I'm not sure bro, I don't work in a service center, it's just my hobby... Complete motherboard replacement is too expensive if you don't have a phone warranty. But it is possible to replace only the emmc memory, ask the service center, or google it. Good luck!
of course mate, thank you for your support!
I think I will pass, changing the whole board is too expensive and changing the memory chip is far beyond my capabilities. The official service center would be too expensive considering the value of the phone.
Hi, I've recently hardbricked my redmi k40 pro when trying to flash some custom roms and custom recoveries. I managed to get it into EDL mode hoping to flash a working recovery from there. However when I try to use the miflash tool it gets stuck on "ping target via firehose", or goes to "write time out, maybe device was disconnected" and I cannot get anything to work. I realized that even if i get past that part that I still require an authorized xiaomi account to flash in EDL mode. So I thought i'd try it using QFiL, however that requires the programmer file for the phone, and from my understanding that's a proprietary file that only xiaomi has and you can only get from leaks and such.
I was wondering if anyone knew where to get the programmer file or if you knew how I could get an EDL authorized xiaomi account so i could use the miflash tool to fix my phone.
Also does anyone know how to fix the "write timeout, maybe device was disconnected"? I have tried different usb ports and different usb cables and I can' get anything to work.
Also is any snapdragon 888 programmer file usable? Or do I have to have one specific to my phone?
Any help would be greatly appreciated as I am very new to EDL mode.
froggydood said:
Hi, I've recently hardbricked my redmi k40 pro when trying to flash some custom roms and custom recoveries. I managed to get it into EDL mode hoping to flash a working recovery from there. However when I try to use the miflash tool it gets stuck on "ping target via firehose", or goes to "write time out, maybe device was disconnected" and I cannot get anything to work. I realized that even if i get past that part that I still require an authorized xiaomi account to flash in EDL mode. So I thought i'd try it using QFiL, however that requires the programmer file for the phone, and from my understanding that's a proprietary file that only xiaomi has and you can only get from leaks and such.
I was wondering if anyone knew where to get the programmer file or if you knew how I could get an EDL authorized xiaomi account so i could use the miflash tool to fix my phone.
Also does anyone know how to fix the "write timeout, maybe device was disconnected"? I have tried different usb ports and different usb cables and I can' get anything to work.
Also is any snapdragon 888 programmer file usable? Or do I have to have one specific to my phone?
Any help would be greatly appreciated as I am very new to EDL mode.
Click to expand...
Click to collapse
UNBRICK XIAOMI PHONES WITH EDL
DOWNLOAD MODIFIED MIFLASHAND Qualcomm HS-USB QDLoader 9008 DRIVER
The following actions :
1) Connect phone to pc in EDL mode
2) Open Miflash and specify the path to the firmware
3) Click on flash
4) A window will appear where you will need to register the keys
5) On the second line you will need to write the password -
Code:
055F4BBD62228C3E55433D11D59BB445
6) On line 3, write "answer" -
Code:
jL6N48NekgtUZ/3ubbjqXi5RPllB+MoM6Rwqvrvz62jIPQLAVtekYtBxTumF0G95xEAJn2GDsT4G
iMByr/jp5HgtMMsF01DckdGctz7TfddXJ5XDT1Ki/IqQYFZf79M7z+3vFPuVsAL8muq4HBsMYFnm
A5jWj1zaFBtZ+N9VX/0QfRBUcZamyVsWv7X7hd8zVX6MY86eyb6H6EbLaQRueI8j71TcyUaVkUS5
FOyTJ4J1g+XQVeTTNd7Ht9qkfsOkbMha1SPVdLSCHwpI0kc2GXVz/noIv7PatXNQ7II1Sddmo2pn
qNYMfKqpEttJxfVg0No9KBuyzWBNf/sE/W3EBw==
actually don’t know if this still works, but it was a major loophole found.
Kenora_I said:
UNBRICK XIAOMI PHONES WITH EDL
DOWNLOAD MODIFIED MIFLASHAND Qualcomm HS-USB QDLoader 9008 DRIVER
The following actions :
1) Connect phone to pc in EDL mode
2) Open Miflash and specify the path to the firmware
3) Click on flash
4) A window will appear where you will need to register the keys
5) On the second line you will need to write the password -
Code:
055F4BBD62228C3E55433D11D59BB445
6) On line 3, write "answer" -
Code:
jL6N48NekgtUZ/3ubbjqXi5RPllB+MoM6Rwqvrvz62jIPQLAVtekYtBxTumF0G95xEAJn2GDsT4G
iMByr/jp5HgtMMsF01DckdGctz7TfddXJ5XDT1Ki/IqQYFZf79M7z+3vFPuVsAL8muq4HBsMYFnm
A5jWj1zaFBtZ+N9VX/0QfRBUcZamyVsWv7X7hd8zVX6MY86eyb6H6EbLaQRueI8j71TcyUaVkUS5
FOyTJ4J1g+XQVeTTNd7Ht9qkfsOkbMha1SPVdLSCHwpI0kc2GXVz/noIv7PatXNQ7II1Sddmo2pn
qNYMfKqpEttJxfVg0No9KBuyzWBNf/sE/W3EBw==
Click to expand...
Click to collapse
I still get the write time out, maybe device was disconnected error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does that work with redmi k40 ???
+1
I am facing the same issue with the bricked device. Mi Flash won't let me install anything using EDL mode without authorization. Anyone can help?
Kenora_I said:
actually don’t know if this still works, but it was a major loophole found.
Click to expand...
Click to collapse
It doesn't work anymore.
Hi,
I am experiencing issues with my Poco M4 Pro 4G and trying to unlock the bootloader. What I am currently doing is the following;
I enabled developer options, enabled usb debugging and OEM unlocking. I went to unlock status hit agree and hit pair and have waited 7 days for the timer to run out
I shut down the phone and then enter fastboot by holding the volume down button and the power button at the same time.
I downloaded the mi flash unlock tool from here and I logged in using the same account as on the phone, and got up to this screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I then connect the phone which currently has the fastboot logo on to the computer but the button stays grey.
The following is what I have done;
I have installed adb tools. When the phone is booted and is connected to my computer I can see it via "adb devices" in CMD as admin. I can even send it to fastboot mode by "adb reboot fastboot"
I have installed the qualcomm drivers but I am unsure if they are the correct ones.
I have tried with different cables.
I have tried with different PCs.
The computer that I am using mainly to try and unlock the bootloader is a laptop and the specs are as follows;
Model: GP72 2QE Leopard Pro
Intel Core i7 5700HQ
16GB RAM
The other systems that I have tried are almost identifically specced both are AMD based on X570 Mobo and a Ryzen 7 3700X
There does seem to be a known problem with the Mi Unlock tool not being able to communicate properly with the system drivers. There are some tips for getting it working on this thread:
https://forum.xda-developers.com/t/...ol-cannot-detect-phone.3663139/#post-73566526
If that post doesn't solve the problem then try reading through the later posts in that thread.
Sorry for the late reply, I did the suggestion and it worked! Thank you for the help.
My goal was to flash the indonsian rom of the device onto and I had a bit of a problem last night I ended up sending it into a bootloop because the connection wasn't stable from the computer to the phone, I just woke up today and tried it again on a different computer and a brand new cable and the connection wasn't cutting out at all. I put it in fastboot and succesfulyl flashed it. I can't thank you enough for the help.
I just need to know if I need to close this thread or something now that my issue is complete. I'm new around here so I don't know if I shoudl do that.
The Spike Man said:
I just need to know if I need to close this thread or something now that my issue is complete. I'm new around here so I don't know if I shoudl do that.
Click to expand...
Click to collapse
No need, your experience may be shared by others in which case it will be useful to have somewhere to talk about it
The Spike Man said:
Hi,
I am experiencing issues with my Poco M4 Pro 4G and trying to unlock the bootloader. What I am currently doing is the following;
I enabled developer options, enabled usb debugging and OEM unlocking. I went to unlock status hit agree and hit pair and have waited 7 days for the timer to run out
I shut down the phone and then enter fastboot by holding the volume down button and the power button at the same time.
I downloaded the mi flash unlock tool from here and I logged in using the same account as on the phone, and got up to this screen.
View attachment 5681651
I then connect the phone which currently has the fastboot logo on to the computer but the button stays grey.
The following is what I have done;
I have installed adb tools. When the phone is booted and is connected to my computer I can see it via "adb devices" in CMD as admin. I can even send it to fastboot mode by "adb reboot fastboot"
I have installed the qualcomm drivers but I am unsure if they are the correct ones.
I have tried with different cables.
I have tried with different PCs.
The computer that I am using mainly to try and unlock the bootloader is a laptop and the specs are as follows;
Model: GP72 2QE Leopard Pro
Intel Core i7 5700HQ
16GB RAM
The other systems that I have tried are almost identifically specced both are AMD based on X570 Mobo and a Ryzen 7 3700X
Click to expand...
Click to collapse
Are u sure m4 pro 4g is qualcom ?
Thought is mediatek
aariss said:
Are u sure m4 pro 4g is qualcom ?
Thought is mediatek
Click to expand...
Click to collapse
It is mediatek.