Blue Light flash - Lenovo Zuk Z2 Pro Questions & Answers

Blue Light flash - Lenovo Zuk Z2 Pro Questions & Answers

Hey all,
I have Zuk z2pro z2121. I wanted more than stock ROM so I downloaded zui 2.5.344. I unlocked bootloader n rooted my phone as well as installed TWRP. "Tool All in one" PC software helped me to carry out above with ease.
While playing around I clicked "Lock Bootloader" and phone got switched off with indicating continuous blue light. I tried pressing vol down + power + Home button, and several other combination but didn't help. When I pressed power button for long, I got Zuk logo onscreen with a white flash on indicator for 1 sec and then again the blue light indicator.
After a little RnD after pressing power button till I got white flash for 3 times and the blue light got completely off. I don't know what to do further. I have backup of my boot , recovery and ROM. Kindly suggest.
Shoaib

Press and hold volume - and power . Release power, after vibration you can release the volume -. You will be in that menu https://ibb.co/f3vOHm . Go to device manager and check if pc recognize your phone https://ibb.co/bHqZOR . Open CMD in adb folder and write adb devices https://ibb.co/cwCg3R . Then adb reboot edl . You are i EDL https://ibb.co/cvjiHm . Use Qfil to flash stock rom

Didn't work...
Thanks for responding. As said, tried pressing Vol + Power and never got any vibrations. Tried Up vol + power, tried Down vol + power. No vibrations.
When I press power button with any combination, this is what happens,
After Approx 15 secs - 1 white light flash in place of blue along with ZUK pic on d display (stays approx 1 sec)
Still keeping power button pressed
After approx 7-8 secs - same as above
Still keeping power button pressed
After Approx 15 secs - 1 white light flash in place of blue along with ZUK pic on d display (stays approx 1 sec)
But now after this third time of flash, blue light appears and after 4-5 secs disssappears. If I leave the button only at this time, the blue light doesn't comes back.
If I leave the power button before or after this sequence, the blue light doeanon the indicator doesn't goes off at all.

What is happening when you connect phone with pc ? Is there any reaction ?

No reaction from PC.
I tried connecting to PC, earlier Tool all in one immediately use to detect, n now there is no response from the PC or the software after making USB connection.

Sir,
As I said earlier, I clicked lock bootloader, n when the screen went off, I disconnected the phone from PC. There is a possibility of the boot partition getting damaged or so. Kindly assist.
Rgds

There aren't any ways to enter in fastboot or recovery , even in service menu . I think you should try deep flash cable to enter in EDL .

Will do as u say. Just one last thing, when I checked device manager in my PC, it showed the phone as other devicez "QUSB XXXX". Question is,
1. Any possibilities of recovery without going for a deep flash, as I got to learn it first.
2. Other part is, my phones battery seems to be drained now. So, it won't be a problem for a deep flash.

Could you give some print screen ?

The matter is that you must switch your phone to edl . Try this yet . Your phone must be turn off .
Press only volume up button for 10 sec and while keeping it pressed,connect phone to PC . Hold volume up until your PC finds a new hardware . It should be android phone - ShenQi composite adb interface . If it doesn't work I have no more ideas apart from df cable . This cable works on Zuk z2 and I think it should works on our Zuk z2 pro

Sir,
I managed to connect the phone via USB as 9008. Miflash not supporting my ROM. Will download Stock ROM n then try with QFIL and MiFlash as well. Thanks for all your support. Will keep u posted about the progres. XML file is not found in any ROMs I have. Miflash some error also but detecting the device. Is there any other tool similar to Miflash, which I can try..
Rgds

First use QPST/Qfil . Follow this guide https://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.57/
Do all steps .

Good day.
I tried QFIL as well as Mi flash tool. Both showing errors. QFIL displaying Qualcomm HS USB QLoader 9008. But when downloading content , it shows Sahara error with even initiating the installation. After browsing a bit, started eMMC software download, and found displaying COM20 No phone connected. Can u assist me to fix this. I mean the phone must be in download mode. But how ?
Miflash, on the other hand shows Hello packet error. Don't know how to fix.
Things I did to fix above errors,
1. Copied ROM to Qualcomm/ bin file
2. Copied ROM to C:/
3. Tried using different USB ports
4. Tried different USB cables
5. Uninstalled n reinstalled USB driver, adb n fastboot, qpst, n miflash many a times along with restarting my PC.
None of the above helped.
I think, if eMMC software download starts displaying COM20 Phone connected, then the issue might be sorted out.
Kindly assist.
Rgds

DrTahseen said:
Good day.
I tried QFIL as well as Mi flash tool. Both showing errors. QFIL displaying Qualcomm HS USB QLoader 9008. But when downloading content , it shows Sahara error with even initiating the installation. After browsing a bit, started eMMC software download, and found displaying COM20 No phone connected. Can u assist me to fix this. I mean the phone must be in download mode. But how ?
Miflash, on the other hand shows Hello packet error. Don't know how to fix.
Things I did to fix above errors,
1. Copied ROM to Qualcomm/ bin file
2. Copied ROM to C:/
3. Tried using different USB ports
4. Tried different USB cables
5. Uninstalled n reinstalled USB driver, adb n fastboot, qpst, n miflash many a times along with restarting my PC.
None of the above helped.
I think, if eMMC software download starts displaying COM20 Phone connected, then the issue might be sorted out.
Kindly assist.
Rgds
Click to expand...
Click to collapse
U need ufs flash not emmc. Change programmer in qfil.

I have a some experience with miflash but I use it for xiaomi . I've never flashed my zuk z2 pro by miflash . If you want to use miflash use 2016.03.30 and run it on PC with win 64 . Create a folder on c: for example "zuk" and copy to that all contents of unrar Qpst/Qfil zui rom . If you have Qualcomm hs usb 9008 that means your phone is in edl ( download mode ) . Good luck

I appreciate all ur support....
As suggested, tried Miflash 30.03.2016 also. This ones showing class not registered.
No of things i did to overcome this errors.
1. Changed my PC to developer mode. Allowed portable device connections n stuff.
2. Visual studio C++ 2010 was installed along with Qualcomm driver, i believe thats sufficient.
3. Disabled my Firewall.
4. Downloaded n copied some atl70.dll file to my syswow64 folder as well as sys32 folder.
Tried all flash tools again after these changes....Same negative results.
Any further advices !!!
Regards

It's fault of drivers . Go to device manager and chose qualcomm hs usb 9800 and update driver automaticly . The second matter concerning of flashing by qpst/qfil - why did you put rom in qpst location ? . It must be for example on desktop in one folder . The simplest path is better . Don't use spacebar . Load content you must chose from that rom . Don't use other location . It's not necessary . Could you give some screenshots with qfil errors

DrTahseen said:
I appreciate all ur support....
As suggested, tried Miflash 30.03.2016 also. This ones showing class not registered.
No of things i did to overcome this errors.
1. Changed my PC to developer mode. Allowed portable device connections n stuff.
2. Visual studio C++ 2010 was installed along with Qualcomm driver, i believe thats sufficient.
3. Disabled my Firewall.
4. Downloaded n copied some atl70.dll file to my syswow64 folder as well as sys32 folder.
Tried all flash tools again after these changes....Same negative results.
Any further advices !!!
Regards
Click to expand...
Click to collapse
Did u use ufs flash in qfil instead of emmc?

Starchm said:
Did u use ufs flash in qfil instead of emmc?
Click to expand...
Click to collapse
Yups !!! I already did with Meta Build Type selection. Didnt Help. I tried to search for mbn file also to try emmc but cudnt find so was stuck with ufs....

mar.ur said:
It's fault of drivers . Go to device manager and chose qualcomm hs usb 9800 and update driver automaticly . The second matter concerning of flashing by qpst/qfil - why did you put rom in qpst location ? . It must be for example on desktop in one folder . The simplest path is better . Don't use spacebar . Load content you must chose from that rom . Don't use other location . It's not necessary . Could you give some screenshots with qfil errors[/QUOTE
https://forum.xda-developers.com/attachment.php?attachmentid=4339940&stc=1&d=1511421690
https://forum.xda-developers.com/attachment.php?attachmentid=4339941&stc=1&d=1511421690
https://forum.xda-developers.com/attachment.php?attachmentid=4339942&stc=1&d=1511421690
Click to expand...
Click to collapse

Related

xiaomi mi3 hard brick cold dead?

Lately I was flashing mi3 trough fastboot on w7ulti64bit when something went wrong and now its cold dead.
I have been looking for solution everywhere and as usual xda is my last resort for help with phones, usually I found here what I was looking for but this time it is first time when I have to post new threat.
So basically I found that battery controller had some cold soldier on chip, whole module gives 0v while cell itself 2,8v so I think I fixed it since now whole battery module shows 3.3v and cell itself 3.8v after charging.
But im unable to wake up phone in to fastboot or any other way to reflash it.
When connected to 2000mAh charger there is solid red light, when connected to PC it lit for a second then goes off and PC recognizes mi3 as USB input device and HID compliant device.
I have tried to update drivers for those devises so miflash would recognize it and allow to flash it but without any success.
Any idea what else I could do with it, or how to force flash to flash at least boot sector?

Shamoth said:
Lately I was flashing mi3 trough fastboot on w7ulti64bit when something went wrong and now its cold dead.
I have been looking for solution everywhere and as usual xda is my last resort for help with phones, usually I found here what I was looking for but this time it is first time when I have to post new threat.
So basically I found that battery controller had some cold soldier on chip, whole module gives 0v while cell itself 2,8v so I think I fixed it since now whole battery module shows 3.3v and cell itself 3.8v after charging.
But im unable to wake up phone in to fastboot or any other way to reflash it.
When connected to 2000mAh charger there is solid red light, when connected to PC it lit for a second then goes off and PC recognizes mi3 as USB input device and HID compliant device.
I have tried to update drivers for those devises so miflash would recognize it and allow to flash it but without any success.
Any idea what else I could do with it, or how to force flash to flash at least boot sector?
Click to expand...
Click to collapse
Try mi flash tool

Main problem is that I have tried all 3 miflash I could found 2.11.6 20131108 20140509 and none of them recognizes device and I can't even initiate flashing process ;/

it sounds like a driver issue. just download all the drivers you can find for your phone.

Shamoth said:
Lately I was flashing mi3 trough fastboot on w7ulti64bit when something went wrong and now its cold dead.
I have been looking for solution everywhere and as usual xda is my last resort for help with phones, usually I found here what I was looking for but this time it is first time when I have to post new threat.
So basically I found that battery controller had some cold soldier on chip, whole module gives 0v while cell itself 2,8v so I think I fixed it since now whole battery module shows 3.3v and cell itself 3.8v after charging.
But im unable to wake up phone in to fastboot or any other way to reflash it.
When connected to 2000mAh charger there is solid red light, when connected to PC it lit for a second then goes off and PC recognizes mi3 as USB input device and HID compliant device.
I have tried to update drivers for those devises so miflash would recognize it and allow to flash it but without any success.
Any idea what else I could do with it, or how to force flash to flash at least boot sector?
Click to expand...
Click to collapse
Same problem here, waiting for someone give the solution

if the device is not getting detected in any of the mi flash tools,i feel its a clear sign of driver issues ,

ZenR2 said:
if the device is not getting detected in any of the mi flash tools,i feel its a clear sign of driver issues ,
Click to expand...
Click to collapse
r u following correct procedure for using MI flash tool ?
is ur Phone able to boot to FLash mode ( turn phone off > Press volume + Key then Press Power on - it will show flash mode )
Now Open MI Flash tool > Press Refesh > it will show phone now ( a number will b shown instead of name Xiamo Mi3)
Now Extract Fastboot rom to C Drive ( it should look like this C:\ROM (Location should not cointain space)
Now click Browse > advance > select C:\ROM\Folder\ select bat file

Its not drivers issue since its get detected as QUALCOMM HS-USB QDLoader 9008 or QUALCOMM HS-USB Diagnostic 9006 depending of its state.
In QDLoader it is recognized by miflash as COM20 device and I can upload by miflash or qpst boot image, then it switches to diagnostic that is recognized by some sort of string and I can upload/proceed with rest of rom flashing that includes creating partitions and writing data to them.
Main problem is that when its successfully flashed it is still cold dark, while PC can see it and all partitions like 28 of them...
And I think its related to the fact that qpst reports phone as in download mode.
Any idea how to exit that mode, like in Mi2 that was forced to enter "service" by shortening some pins to put it download mode to flash cold dead ones?

agdag said:
magdag from en.miui.com forum seems to be able to hekp ..or try [email protected] , jason provide paid service
Click to expand...
Click to collapse
You were already looking at it
Kinda wasted a lot of Mine and Yours time and some of my money
If You got any other ideas since that time how to resurrect it just let me know.

Any solution?
Is there any solution to this problem? My phone has been cold brick for 3 days now. Doesnt boot up or charge up. Detected on connecting to PC with a sound, but Shows as Com 10 or 20 on Miflash and thus cannot be flashed.
Cannot boot into fastboot as well.
Anyone anything?

androidy88 said:
Is there any solution to this problem? My phone has been cold brick for 3 days now. Doesnt boot up or charge up. Detected on connecting to PC with a sound, but Shows as Com 10 or 20 on Miflash and thus cannot be flashed.
Cannot boot into fastboot as well.
Anyone anything?
Click to expand...
Click to collapse
You can check the steps I took for recovering from a similar problem here: http://en.miui.com/forum.php?mod=viewthread&tid=22811
If you have any other questions, tag me on your reply and i'll try my best to help.

Device bricked - Qualcomm 9008 port up but ADB does not detect the device

Hello everyone,
It seems that my worst nightmares came up, and got my device bricked while trying to flash it to a stock ROM (had a custom multilingual ROM installed by the chinese seller), and now it's in a strange stage, as Windows detects the Qualcomm port, but adb can't see it.
The adb devices list is in blank, and QPST detects everything, but when trying to flash the device, the error message on the screenshot appears.
Also tried to do it with MiFlash, but didn't worked too.
Any idea about how to solve this?
Thank you in advance for your help.
P.D.: My device is in black screen, so no menu or anything.
P.D.2: Already downloaded the Android SDK in order to try it's ADB, but it didn't worked too.

Now after some research, I found out that the "ADB interface" is not showing in Windows device manager
I tried to install it manually, but can't find a way to get it working, and after the flash, USB debugging was set on, so can't figure out what could be happening...
Is it possible it's completely dead?
Any idea?

Just to say that I have tried multiple combinations while plugging the device to the PC, and didn't worked...
I mean, the PC seems to react, but always with the same end, only shows the Qualcomm port 9008, nothing about the adb...
Getting out of ideas, anyone more has some?

did you start the tool with admin rights?
read a Little bit here
http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-z2131-only.104/
if you have a Z2 pro take this
http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.57/

Zukunft said:
did you start the tool with admin rights?
read a Little bit here
http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-z2131-only.104/
if you have a Z2 pro take this
http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.57/
Click to expand...
Click to collapse
Yeah, I already started the cmd with admin rights, but the problem is that adb does not works, as the device is not turning on.
As you can check in my first post, in the screenshot, after running the "adb devices" command, it doesn't gives any kind of error, just returns a blank list.

Noggin said:
Yeah, I already started the cmd with admin rights, but the problem is that adb does not works, as the device is not turning on.
As you can check in my first post, in the screenshot, after running the "adb devices" command, it doesn't gives any kind of error, just returns a blank list.
Click to expand...
Click to collapse
adb will never recognized it, in 9008 mode or it's called EDL, the only program that recognized the port is QFIL / Miflash. if you get an error when flashing you must reset your phone again to repeat the process by pressing power button for a couple seconds. if your bootloader already unlocked that must be simpler to do, just press power button for a couple minutes until shor vibration then press vol up + vol down and connect to usb at the same time..

arif_kholid said:
adb will never recognized it, in 9008 mode or it's called EDL, the only program that recognized the port is QFIL / Miflash. if you get an error when flashing you must reset your phone again to repeat the process by pressing power button for a couple seconds. if your bootloader already unlocked that must be simpler to do, just press power button for a couple minutes until shor vibration then press vol up + vol down and connect to usb at the same time..
Click to expand...
Click to collapse
Thanks for the info, I've tried the vol + and vol- buttons after the short vibration, and the PC does not detect the device...
Is it there any other way to get the device detected by the PC?
Actually, the only thing the device does, is the following:
After pressing the PWR button for around 5-7 seconds, it makes a short vibration and the notifications led makes a flash in green colour, but nothing more... If you keep pressing it, around 7-8 later, it makes a litte bigger vibration and a flash on green too... And if you continue, it does on, and on, and on...
Any idea? Anyone told me about getting a Xiaomi Deep flash cable, but I'm not sure about if that will work or not...

Noggin said:
Thanks for the info, I've tried the vol + and vol- buttons after the short vibration, and the PC does not detect the device...
Is it there any other way to get the device detected by the PC?
Actually, the only thing the device does, is the following:
After pressing the PWR button for around 5-7 seconds, it makes a short vibration and the notifications led makes a flash in green colour, but nothing more... If you keep pressing it, around 7-8 later, it makes a litte bigger vibration and a flash on green too... And if you continue, it does on, and on, and on...
Any idea? Anyone told me about getting a Xiaomi Deep flash cable, but I'm not sure about if that will work or not...
Click to expand...
Click to collapse
i've already tried xiaomi deep flash cable, and its work on my z2 plus, that's how to force phone into 9008 mode.. and also, dont add space between folder names where your firmware files there or there will always sahara fail

Hey man!
I had the same Problem!
Sahara error, no reaction from device, black screen, port recognized in qfil etc.
I found out that this behaviour of the device means, that it is in EDL-mode.
what helped ma was:
1) Unplug everything.
2) Set up the QFIL Tool completely, but do not hit "Download Content".
3) Try to "reboot" the Zuk Z2 Pro by pressing the power button for several seconds. Kind of resets everything.
4) Plug in USB
5) execute: "adb reboot edl" via adb
6) unplug USB
7) plug in USB and immediately (within a second!) hit the "Download Content" buton, just after it is clickable.
8) dowload should start without sahara error
Hope it works! :good:

Well, finally, I talked with the aftersales dpt from the shop where I got the device, and returned it, and incredibly it seems it was defective.
The guy from the tech dpt said that it wasn't supposed to die that way, so they returned me a brand new device, and fortunately it's up to date with ZUK's last official ROM.
Thank you everyone for your ideas and help, now I can enjoy this great device

My Zuk Z2 plus got stuck after TWRP, I need help badly.
sirmclord said:
Hey man!
I had the same Problem!
Sahara error, no reaction from device, black screen, port recognized in qfil etc.
I found out that this behaviour of the device means, that it is in EDL-mode.
what helped ma was:
1) Unplug everything.
2) Set up the QFIL Tool completely, but do not hit "Download Content".
3) Try to "reboot" the Zuk Z2 Pro by pressing the power button for several seconds. Kind of resets everything.
4) Plug in USB
5) execute: "adb reboot edl" via adb
6) unplug USB
7) plug in USB and immediately (within a second!) hit the "Download Content" buton, just after it is clickable.
8) dowload should start without sahara error
Hope it works! :good:
Click to expand...
Click to collapse
I will tell my issue
I bought this device this July month, I was encouraged seeing you guys did a lot of flashing, I thought I could flash myself but it became a nightmare now.
I am not that much technical so please bare my usage of words below, but I need a real help.
I was doing the basic TWRP for getting the AICP ROM 12.1 but after wiping the data from TWRP my device doesnt get recognized for the Sideload and I did whatever I can but it doesnt detect my phone, so I am having a screen with Start "Green" which is showing the device status as unlocked and when I click on Recovery it goes to the Zuk logo and doesn't have any sign after that.. stuck really
I tried using QFIL but my device detects as 900H but not 9008 also adb doesn't detect my device at all after this.
I think I really did a hard brick of my device.
I dont want to loose hope, I want your help really badly.

For those of you who had the same problem don't give up! I was in that same situation and I solved by putting my phone on EDL via this method
https://www.youtube.com/watch?v=2m44xKog-dI
After plugging the phone for the second time and QFIL recognize as EDL mode I clicked on download content as fast as I could so it started to flash the ROM that I spent like 10h trying to figure a way to do it lol. Anyways, the procedure is the same as putting into EDL via adb fastboot, the only difference is that you make it through a "fake" deep flash cable as that guy in the video shows.

My Z2 Pro dead .. help me ..!!

i did something Stupid and my Z2 Pro dead
there is no fast-boot and no recovery .. only black screen and when i press power button there is a short and long vibration just that and the LED there is flash yellow for 0.1 second

aljthab said:
i did something Stupid and my Z2 Pro dead
there is no fast-boot and no recovery .. only black screen and when i press power button there is a short and long vibration just that and the LED there is flash yellow for 0.1 second[/QUOTE try connecting it to the PC, if it doesn't show anything on PC then just hand it over to the lenovo service center and blame it on the device that it stopped booting :silly:. I thought i had bricked my device but they did something and gave it to me in 3 to 4 days and that was done under the warranty no extra charge and don't confess that I had rooted ur device , If u tell them that they will try to extort money from u :crying:
Click to expand...
Click to collapse

aljthab said:
i did something Stupid and my Z2 Pro dead
e LED there is flash yellow for 0.1 second
Click to expand...
Click to collapse
I have exactly the same, what to do? I installed the dev 44, the rate of established but after 15 minutes, logo is stalled, not waiting until the end of excess freewheeling dev 300, it is not fully established and bug crawled, I rebooted the machine and an endless vibration with green LED :crying:
1 Charging can be a little warm
2. can not be detected pc
3. can not access the fastboot mode
4. when charging, the notification light dies
5. deep flash cable has not helped
sorry my bad english

kerei said:
I have exactly the same, what to do? I installed the dev 44, the rate of established but after 15 minutes, logo is stalled, not waiting until the end of excess freewheeling dev 300, it is not fully established and bug crawled, I rebooted the machine and an endless vibration with green LED :crying:
1 Charging can be a little warm
2. can not be detected pc
3. can not access the fastboot mode
4. when charging, the notification light dies
5. deep flash cable has not helped
sorry my bad english
Click to expand...
Click to collapse
Refer to this http://zukfans.eu/community/threads/how-to-unbrick-zuk-z2-from-diagnostic-port-900e.2856/ and this http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-z2131-only.104/

same issue with zuk z2
adriano1593 said:
Refer to this http://zukfans.eu/community/threads/how-to-unbrick-zuk-z2-from-diagnostic-port-900e.2856/ and this http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-z2131-only.104/
Click to expand...
Click to collapse
Hello there... Any solution you found? I am stuck with my zuk z2 in same situation ?? any help ?

I have a similar problem.
What caused the black screen? -
History:
I booted to test mode at 2.5.033 ST, the phone got stucked at this menue there was no way to get out. TWRP Restore to Nandroid bougt only black screen after 2nd vibration and ZUK logo.
I fixed the Test mode bug, by flashing the ZUI 1.9.104 ST Stock ROM via QPST.
After the phone was "repaired" I unlocked the bootloader, installed TWRP, made a nandroid backup of fully stock ROM and restored a nandroid backup from before the test mode problem.
The nandroid restore was successful, I rebooted the phone and it was "dead". Black screen, only rebooting (perioldy vibrating) there was no end, until the battery was empty.
I got no luck to reach any mode with tricky button pressing (vol+ pwr; vol- pwr; vol+ vol- pwr; usb in vol-) nor Windows detecting the phone. That's why I decided to remove the back glass cover, to got access to the battery.
Now I'm able to get the phone detected by my PC.
What I did: disconnect the battery, connect the phone to my computer, pressed the vol- button and connect the battery.
This made my PC able to detect the phone, but no I have an other problem. Windows only detects the phone as "unknown usb device (device descriptor request failed)". I don't know any way to install the driver....
Maybe anyone is able to help me or has any tip?
Thanks!
Cheers,
m_atze

eryenakgun said:
What id shown in unknown device.
Like ven_9102&dev_1234
Maybe with editing quallcom drivers for your device id, you can still install it.
and if luck qpst can recognize it as qualcomm debug mod
Sent from my ZUK Z2121 using Tapatalk
Click to expand...
Click to collapse
Hi,
Thanks for your quick response.
The Hardware ID: USB\DEVICE_DESCRIPTOR_FAILURE
"Error Message": This device has been stopped because it has reported errors. (Code 43)
An error occurred while requesting the USB device descriptor.

m_atze said:
I have a similar problem.
What caused the black screen? -
History:
I booted to test mode at 2.5.033 ST, the phone got stucked at this menue there was no way to get out. TWRP Restore to Nandroid bougt only black screen after 2nd vibration and ZUK logo.
I fixed the Test mode bug, by flashing the ZUI 1.9.104 ST Stock ROM via QPST.
After the phone was "repaired" I unlocked the bootloader, installed TWRP, made a nandroid backup of fully stock ROM and restored a nandroid backup from before the test mode problem.
The nandroid restore was successful, I rebooted the phone and it was "dead". Black screen, only rebooting (perioldy vibrating) there was no end, until the battery was empty.
I got no luck to reach any mode with tricky button pressing (vol+ pwr; vol- pwr; vol+ vol- pwr; usb in vol-) nor Windows detecting the phone. That's why I decided to remove the back glass cover, to got access to the battery.
Now I'm able to get the phone detected by my PC.
What I did: disconnect the battery, connect the phone to my computer, pressed the vol- button and connect the battery.
This made my PC able to detect the phone, but no I have an other problem. Windows only detects the phone as "unknown usb device (device descriptor request failed)". I don't know any way to install the driver....
Maybe anyone is able to help me or has any tip?
Thanks!
Cheers,
m_atze
Click to expand...
Click to collapse
Alright bro, there is one method you can try.
http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.57/
I assume your phone is a brick now. The only method you can use is the 9008 unbrick mode. (AKA QBST)
There are a few things you need to prepare before you save ur phone. U need to download the require application that the website provided above, after you set everything up,
make sure you download the latest 2.5 QBST rom,
http://bbs.lenovomobile.cn/z2pro/t554654/
Because ur phone wont be able to enter 9008 through software, thus u need to do the following.
1. Load the content XML fille,
2.Turn off your phone. After it's fully shutdown
3. press and hold the volume up button for 3 seconds
4. press power button while hold the volume up (press it for 0.5second and keep holding it)
5. after 0.5 seconds, plug in the usb right away
6. the QFIL tool should appear the Qualcomm usb QD loader
7. the download button should turn blue
8. flash it and wait for reboot

OtakuLi said:
Alright bro, there is one method you can try.
http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.57/
I assume your phone is a brick now. The only method you can use is the 9008 unbrick mode. (AKA QBST)
There are a few things you need to prepare before you save ur phone. U need to download the require application that the website provided above, after you set everything up,
make sure you download the latest 2.5 QBST rom,
http://bbs.lenovomobile.cn/z2pro/t554654/
Because ur phone wont be able to enter 9008 through software, thus u need to do the following.
1. Load the content XML fille,
2.Turn off your phone. After it's fully shutdown
3. press and hold the volume up button for 3 seconds
4. press power button while hold the volume up (press it for 0.5second and keep holding it)
5. after 0.5 seconds, plug in the usb right away
6. the QFIL tool should appear the Qualcomm usb QD loader
7. the download button should turn blue
8. flash it and wait for reboot
Click to expand...
Click to collapse
Thanks for your tip.
I followed your described procedure, but the phone will not be recocnized by the PC.
1st: I loaded QFIL XML file. (By the way this tut is made by me)
2nd: I disconnected the battery (The phone can't be turned off normally!)
3rd, 4th, 5th
6th: nothing happend!
7th: "-"
8th: "-"
The only way the phone will detected by the PC:
1st: disconnect battery
2nd: plug in USB (PC and Phone)
3rd: press VOL+ or VOL- or PWR button (doesn't matter which one)
4th: connect battery
5th: detected as "unknown usb device (device descriptor request failed)"

m_atze said:
Thanks for your tip.
I followed your described procedure, but the phone will not be recocnized by the PC.
1st: I loaded QFIL XML file. (By the way this tut is made by me)
2nd: I disconnected the battery (The phone can't be turned off normally!)
3rd, 4th, 5th
6th: nothing happend!
7th: "-"
8th: "-"
The only way the phone will detected by the PC:
1st: disconnect battery
2nd: plug in USB (PC and Phone)
3rd: press VOL+ or VOL- or PWR button (doesn't matter which one)
4th: connect battery
5th: detected as "unknown usb device (device descriptor request failed)"
Click to expand...
Click to collapse
Make sure you have to plug in the usb right away as soon as you u press power, and keep holding them

OtakuLi said:
Make sure you have to plug in the usb right away as soon as you u press power, and keep holding them
Click to expand...
Click to collapse
Yes, I did exactly you described. Sorry but this isn't working.
I don't know what I should do. Even a repair shop couldn't fix it.
Maybe I need to do this:
http://bbs.lenovomobile.cn/z2/t121791/?highlight=900e
But I don't want to destroy my PC (3000 bugs)

m_atze said:
Yes, I did exactly you described. Sorry but this isn't working.
I don't know what I should do. Even a repair shop couldn't fix it.
Maybe I need to do this:
http://bbs.lenovomobile.cn/z2/t121791/?highlight=900e
But I won't destroy my PC (3000 bugs)
Click to expand...
Click to collapse
oh well, good luck

OtakuLi said:
oh well, good luck
Click to expand...
Click to collapse
I will report the result.

OK. I made the deepflash cable.
After using it there is no difference between pressing one of the button combinations I recently mentioned (VOL+ or VOL- or PWR).
The phone will be detected as Unknown device. After intalling my modified driver to match the unknown ID, QFIL don't detect the COM Port.

Hello had the same problem, only with the difference that my battery was not completely discharged.
What has helped:
1 Start QFIL Tool
2 Press the volume +
3 Connect the original cable to the PC
4 QFIL Tool recognized the phone and I could play an original Rome.
Mfg
Ps. Is now the battery cover (glass) broken?

No, I used a hairdryer, a razorblade, plastic tool and a suction cup to lift the backcover glass.
The glass is fully intact no damages.

You have good nerves. I would not have expected that.
But in the end, it does not matter if it does not start anymore.
Thank you again for your great instructions for playing and rooting the mobile phone.
I hope you get your phone back.
Mfg

Good and bad news
The guy unbricked the phone successfully, I received it today.
Now I have an other problem:
The phone is very very slow and laggy now.
The problem occurs everywere, Recovery, boot (the bootlogo laggs), booted System, also the test mode laggs now
Furthermore the sceen flickers sometimes and at the right side the sceen is mirrored sometimes.
Did anyone has an idea?
What I did today:
reflash through qfil
1.9.104_ST
2.3.044_ST
ZUI_2.5.335_ST

Hi m_atze, I am exactly in the same situation as You. After using deep flash cable method, I got "unknown usb device (device descriptor request failed)". Could You tell me what was the solution to unbrick the phone?

Bricked Le S3 X626 after flashing TWRP, can't power on, PC won't recognize device

Hi - I'm not sure if I am having the same problem as b1gb1ng has - but I'll describe what I am experiencing as best as I can...
After using my Le S3 X626 for a week with no problems at all, I decided to install TWRP. So the first thing I did was follow the instruction on this website getdroidtips.com to unlock the bootloader via my Windows 10 64bit PC with the ADB.exe and fastboot.exe tool. I followed all the instructions carefully, my batteries were well above 80%, and I got to the part where I issued the command "fastboot reboot" on my Dos prompt. The phone rebooted and everything seemed perfectly normal. So far, so good... The next thing I did was used the same ADB.exe and fastboot.exe tool to flash a TWRP file that I downloaded from another website. I issued the command: "fastboot flash recovery twrp.img" and THAT'S when the problem began - the screen of my le S3 x626 just went pitch black this time around instead of showing the Chinese characters!
I disconnected my Le S3 x626 from my PC, tried turning the phone's power on (no response), tried holding the Vol+ and/or Vol- buttons and the power button (no response). The phone was completely unresponsive. No light came on at all. I connected my Le S3 x626 back to the PC's USB port, and the red light on the phone came on (as if it's charging) but my PC kept connecting and disconnecting to the Le S3 x626 over and over again (before this incident, the PC would recognize my Le S3 X626 right after I connect to USB port). I tried to reboot the bootloader again via Dos Prompt - but instead I get the error message "error: device '(null)' not found. Which I guess makes sense because my PC was no longer able to connect to the Le S3 x626 anymore...
<< 1st EDIT - Dec 26 2017>>
<<2nd EDIT - Jan 5 2018>>
<<3rd EDIT - Jan 11 2018>>
<<4th EDIT - Jan 27 2018>>
<<5th EDIT - Jan 30 2018>>
So after more than a month of tinkering with the phone, I was able to unbrick the phone. It seems like a lot people are able to solve in one or two days so my slow progress was likely due to a combination of 1) there being many different version of the solution on the web which confuses more than helps and 2) my inability to follow instructions properly and 3) not having a lot of time on my hand. Anyway, I have summarized my experience in solving this problem as well all the errors due to my screwing up the process - so hopefully this will be a useful guide for everyone who bricked their X626!
Which solution to use
---------------------------
The solution that worked for me was based on advice from alberto-a-l and Catani who pointed me to http://tickernel.org/how-to-unbrick-le-x626-red-light/ which apparently was taken from an article written by os_man... So I guess thanks to all three of you???
What we're all about to accomplish
--------------------------------------------
In case you're interested in the technical details of what we're about to do, here's the quick low down: according to kanewilliam, the Tickernel website solution tells us that we need to first flash the le eco x620 firmware as well as boot and recovery into our bricked x626 phone, and for that we need to download a bunch of files from various websites. Once we have all the necessary files and we have successfully flashed the x620 firmware/boot/recovery via spflash tools, the phone will successfully boot but the screen will be mirrored making it unusable. However, that's okay, because after that we can then boot the mirrored phone in fastboot mode, relock the bootloader, and then flash the phone with a new ROM via dos commands, and after that we will have the phone back up and working again (albeit all the original info would have been deleted). Big thanks to kanewilliam for clarifying the big picture for us!
Part 1 - setting up
---------------------
First you need to download and unzip four files/folders - "LeEco_x620_SP_Rom.androidbrick", "x620_flash_tool_androidbrick", "Windows+10_MTK+VCOM+USB+Preloader+Drivers" and "乐视S3_X626". You need all of them for this solution to work. The links are on http://tickernel.org/how-to-unbrick-le-x626-red-light/ page. These files are like 2.3GB combined and you need to click all sorts of ad stuff to download so this will take a while...
Since a lot of people had problems downloading the files from the tickernel website - I've included the steps on what you need to do to get the files downloaded. There are two ways of doing this:
Method A - via Tickernel links
========================
1. Firstly, you need to find the link first! You could navigate through the website by clicking on the word "steps" which will then take you to a second page where you have to scroll all the way to bottom, or you can just use these links that I copied from the page:
Download :*
Firmware for unbrick:*http://idsly.com/0dN
SP Flash Tool :*http://idsly.com/Xfppfu
Driver :*http://idsly.com/d3t5
Download without ads:
Firmware for unbrick:*https://cnhv.co/teyy
SP Flash Tool:*https://cnhv.co/tezc
Driver:*https://cnhv.co/tf1i
2. Pick either with ads or without ads. If you choose download without ads, they will make you do some mining for them first (proof of work) and once done they'll let you download. If you choose download with ads, there won't be any mining (apparently) but you have to view a few ads before they let you download
3. If you choose with ads (which was what I did), you will first be taken to the IDSLY page where you need to do some fun ad clicking activities. First, scroll down slightly and click on the green "visit link" button once, and tell your browser to allow pop up if prompted.
4. A new page will open up along with an ad pop up. The new page will say "your link is almost ready"... yeah right! You can close the pop up but DO NOT close the new page. Now scroll down the “your link is almost ready" page and click the blue "get link" button.
5. More pop-up windows show up, and some of them have the potential to be NSFW (not safe for work) so be sure to do this at home! You can close the pop-up windows but don't ever close the main page or you'll have to start all over again! However, you may be taken back to the original IDSLY page that you were directed to in (3). Don't be disheartened, this is normal... they like to mess with you!
6. Repeat the steps 3-5 again, and again, and again. By the third or fourth time it'll no longer loop you back to the IDSLY page and you'll just be stuck with "your link is almost ready" page instead. This is a good sign. Keep clicking on the blue "Get Link button" and close all the virusy pop ups as they show up.
7. After may be a few more times of clicking blue "Get Link" button and closing a dozen virusy pop up ads, you'll finally get the browser prompt (legit this time) asking you to download the file - "What do you want to do with .LeEco_x620_SP_Rom.androidbrick.7z". Click “save” to download the file and now you're done with one file!
8. Now do the same for the other two files... yeah, this process takes a while!
Method B - Gizmodo links & mediafire
==============================
Based on the responses I got in this thread, there are some people who don't like method A as you need to 1) go through a ton of clicking just to get to the final download URL for each file, and 2) along the way there are lot of those spam/adware sites that pop up on your browser. Personally I think these pop ups are pretty harmless as long as you don't download or install anything outside of the zip files you need (like flashplayerx.exe!), but understandably some people don't want to deal with the hassle. Thankfully, adaa1262 has informed us that you can get most of the files from gizmodo at https://www.gizmochina.com/2016/12/20/leeco-le-2-x620-x620-pro-x625-pro-rescue-guide-video/, although you may have to follow their instructions since their file naming convention is different from the Tickernel files that I downloaded and used.
Regardless, you would still need to get the S3_X626 file which gizmodo doesn't seem to provide a link to. If you want to bypass the tickernel link method, here's the direct mediafire link for S3_X626:
http://www.mediafire.com/file/cmkqb7...h7/S3_X626.rar
Note - apparently the author of the Tickernel website changed the URL, probably because too many people were getting the file directly instead of going through the advertising loop.... or either that mediafire has a policy of randomizing the URL labels.... So anyway it looks like the only way to get the S3_X626.rar file is via the Tickernel website for now, unless someone is generous enough to host it on an ad free server!
Note that when unzipping 乐视S3_X626.rar, I got a bunch of warnings from Windows Defender about virus/Trojans etc. - so just ignore them.
Part 2.1 Installing the MediaTek drivers
---------------------------------------------
First you need to get Windows into unsigned mode. The instruction below is fairly straightforward and taken from Dell website.
1. Click the Start menu and select Settings.
2. Click Update and Security.
3. Click on Recovery.
4. Click Restart now under Advanced Startup.
5. Click Troubleshoot.
6. Click Advanced options.
7. Click Startup Settings.
8. Click on Restart.
9. On the Startup Settings screen press 7 or F7 to disable driver signature enforcement.
Once you've disabled signed driver enforcement, you can try to restore the drivers - so here are the next steps:
10) If you haven't done so, go to device manager and connect the x626 to the PC's USB
11) Sometimes, you have to wait for a minute or two for the PC to recognize the phone. If this doesn't work, unplug, try holding the power button and Vol - for 15 seconds then let go, it 'wakes' up the phone somehow, then connect it back in. You might need to do this a few times.
12) If you get it to work, it will try to install a generic USB driver. Wait for the generic USB driver to show up under "Ports (COM & LPT)" (along with the USB connect chime sound), then click on "update driver"
13) Select "browse my computer for driver software"
14) Select "Let me pick from a list of available drivers on my computer"
15) Select "Have Disk..."
16) Select "Browse", then find the Windows+10_MTK+VCOM+USB+Preloader+Drivers inf file that you saved earlier and click on the appropriate version (x64 for me)
17) Now you will have the option to replace the generic driver with the new drivers. I personally selected "MediaTek DA USB VCOM" driver.
Note that luckyrai had success with the preloader driver instead of the DA USB VCOM driver. So you could try those drivers instead if you're stuck later on
Part 2.2 fixing USB connect and disconnect
----------------------------------------------------
This was the most difficult part for me (and I guess a lot of people) - but here's how I resolved it:
Note that both luckyrai and blueasteroid stated that steps 1-5 below is not be necessary in their experience
1) After the MTK driver installation is completed, take out the phone
2) Keeping the device manager windows opened, plug the phone back in again
3) After this, disconnect the x626 from the PC's USB port and reconnect again. The PC will most likely try to switch to another COM Port and reinstall another generic USB driver. If it does that, repeat step 5 and overwrite the new generic driver and COM port with the MediaTek DA USB VCOM driver . Keep doing this until you end up with a situation where you have the PC cycling between 2-3 COM ports in the connect/disconnect loop but at least they will be showing MediaTek DA USB VCOM every time.
4) Now reassign all these COM ports (right click, properties, Port setting, advanced) to a single designated port (like, say "3").
5) If you follow this instruction, the phone will still connect and disconnect from the USB, but each time it does so the phone will always connect to the same COM port and using the same driver - this will make it easier to flash though success is not guaranteed every time
Part 3 - SP Flash Tool
---------------------------
This part is supposed to be easy but I screwed this one royally by not following instructions and ended up wasting a lot of time.
1) The first thing you are supposed to do is open one of the downloaded folders "x620_flash_tool_androidbrick", then double click on flash_tool.exe to open the SP Flash Tool.
2) press Ctl Al S and it will expand the fields to include Authentication File .
3) fill each fields like this by navigating to each specific file in each specific folders:
Download Agent : \..\..\x620_flash_tool_androidbrick\secureboot\DA_ BL_HIGH.bin
Scatter-Loading File: \..\..\LeEco_x620_SP_Rom.androidbrick\MT6797_Andro id_scatter.txt
Authentication File: \..\..\x620_flash_tool_androidbrick\secureboot\aut h_sv5_letv.auth
Note the "Certification File" field you leave blank.
Now it is paramount that you select the EXACT file in the EXACT folder. If you did this right, then the download rows should be populated and the tick boxes all ticked, and the "location" column is filled up with the location of all the .bin files. If you did not follow the instruction properly (like I did), what ends up happening is even though the "Name" column is filled up, the Location column will be mostly empty and the tick boxes unticked except "preloader" row and this will give you errors later on when you try to download (more on that in a bit)
4) Untick recovery (second row) and boot (eleventh row).
5) Then plug in the X626. At first I held down the Vol - button but it turned out that if you did this right, you don't need to press any button at all! When the USB connect sound chimes immediately click "Download". If you did this wrong, you will get the error message “BROM ERROR : S_COM_PORT_OPEN_FAIL (0x3F5)". In that case, unplug phone, hold down power and Vol - button for 15 seconds, then try again. If you did it right, it will start to flash.
Note that blueasteriod confirmed that holding the Vol - button the entire time is absolutely necessary for him as it somehow ensures that the device stays connected despite the COM port switching issue, so basically the same opinion as alberto-a-l and Catani, so I guess you can try the Vol - button option if the flashing continues to fail
6) However, depending on whether you did step (3) right, the flashing process could die within 10 seconds and give you the error "BROM ERROR: STATUS_OPEN_FILE_ERR (0xC001000E)". If you see this error then you screwed up step 3 (like I did many times) - go back and make sure you selected the right file I the right folder and the relevant boxes are ticked.
7) If you did step 3 right, then the SP Flash Tool window would go from red (Downloading DA 100%) to purple (Download Bootloader 100%), then goes to yellow as it download each of the .bin files to the phone. The process could take about 10 mins. Again, at first I thought you need to hold down the Vol - button but turned out if you did it right you won't need to.
8) So that's the hard part. Now the easy part - press Control Alt V, go to "Window" in the menu bar of SP Flash Tool and click on "Write Memory". The write memory tab will magically appear next to memory test tab. Again, you need do exactly as the instruction says - select boot-verified.img in the downloaded folder LeEco_x620_SP_Rom.androidbrick, and type "0xf900000" on the Begin Address field. Connect the X626 to USB but this time hold the Vol - button while doing so. Click "Write Memory" and the writing should work (Green okay sign). If you didn't do this right, you will get a slightly different error (something like VFY_FAIL).
9) Repeat the process but choose recovery_stock_works _after_brick.img in the folder LeEco_x620_SP_Rom.androidbrick for the file path, and change the Begin Address field to 0x8000. Again, connect the phone and hold down Vol +, and click "Write Memory"
Now, I skipped the DA_BR.bin part although it didn't seem to cause a problem. Anyway, I tried to power on my phone - initially and the red light started flashing and the battery icon appears on the screen - which means I need to charge my phone first since the battery has been depleted after a month of trying to fix the phone. So I charged it up for 20 mins, tried again and this time the phone booted! However, the screen will like its mirrored (just like the instructions said), and you won't be able to do much but at least I was able to boot into the home screen. Yay!
Part 5 - Running .bat files in S3 X626 folders
----------------------------------------------------
1) Boot the phone in fastboot mode per instruction (Vol -, Power), and the familiar black screen with Chinese characters showed up on the phone. Plug in the phone back into USB. By now the PC fully recognizes the X626! So no more annoying connect/disconnect problem.
2) Run the file 开机oem解锁-音量下+开机键_读取Devices.bat. The Dos prompt would then show that is doing a bunch of stuff (I guess it's unlocking the bootloader?) and then a text file "Devices.txt" is generated in the folder..
3) Run the file 刷机.bat. You will get an error on the dos prompt. So what you need to do is change the folder name from "乐视S3_X626" to "S3_X626" by removing all the Chinese characters. Run the file again and the dos prompt will through some sort of flashing process which will take about 10 mins.
4) Unplugged the phone and hold down the power button for a while to reboot. You may need to do this several times as I found that I was stuck in the bootloader screen.
5) Now the phone would reboot normally and the "EUI" logo showed up. What happened to me was it froze. So I rebooted the phone again, and this time the EUI logo showed up and it started to initialize all the default apps (I think 15 of them). That took about 10 mins. So be sure that your battery is fully charged when you do this!
6) You are then taken to the setup screen, put in the Sim Card and connect to Wifi - skipped the finger print set up stuff and you will be back to the home screen.
7) You'll note that EUI is version 5.9.020S (I was on 5.8 earlier), with baseband, IMEI and everything all in place.

joebah said:
Hi - I'm not sure if I am having the same problem as b1gb1ng has - but I'll describe what I am experiencing as best as I can...
After using my Le S3 X626 for a week with no problems at all, I decided to install TWRP.
So the first thing I did was follow the instruction on this website getdroidtips.com to unlock the bootloader via my Windows 10 64bit PC with the ADB.exe and fastboot.exe tool. I followed all the instructions carefully, my batteries were well above 80%, and I got to the part where I issued the command "fastboot reboot" on my Dos prompt. The phone rebooted and everything seemed perfectly normal. So far so good...
The next thing I did was used the same ADB.exe and fastboot.exe tool to flash a TWRP file that I downloaded from another website. I issued the command: "fastboot flash recovery twrp.img" and THAT'S when the problem began - the screen of my le S3 x626 just went pitch black this time around instead of showing the Chinese characters!
I disconnected my Le S3 x626 from my PC, tried turning the phone's power on (no response), tried holding the Vol+ and/or Vol- buttons and the power button (no response). The phone was completely unresponsive. No light came on at all.
I connected my Le S3 x626 back to the PC's USB port, and the red light on the phone came on (as if it's charging) but my PC kept connecting and disconnecting to the Le S3 x626 over and over again (before this incident, the PC would recognize my Le S3 X626 right after I connect to USB port).
I tried to reboot the bootloader again via Dos Prompt - but instead I get the error message "error: device '(null)' not found. Which I guess makes sense because my PC was no longer able to connect to the Le S3 x626 anymore...
I am the end of my wits at this point, and really wish I hadn't mucked around with my phone :crying:... is there anyway I can recover my Le S3 X626 back to stock ROM? Thank you very much!
Click to expand...
Click to collapse
250/5000
Hello, the same thing happened to me. Try using the manual on the following page ]ht tp://tickernel.org/how-to-unbrick-le-x626-red-light/ but the flashtool does not detect the terminal when trying to click on download does nothing. I do not know what to do...

alberto-a-l said:
250/5000
Hello, the same thing happened to me. Try using the manual on the following page ]ht tp://tickernel.org/how-to-unbrick-le-x626-red-light/ but the flashtool does not detect the terminal when trying to click on download does nothing. I do not know what to do...
Click to expand...
Click to collapse
Okay, so I downloaded all three files "Windows+10_MTK+VCOM+USB+Preloader+Drivers.zip", "x620_flash_tool_androidbrick.7z" and "unbrick_tool_x626.zip" and extracted them. I tried the "How to fix le x626 undetected" step first given that none of this will work if the USB connection is not stable...
The problem is that because my PC keeps connecting and disconnecting from the X626, it's impossible to update my PC device driver as the instruction suggests. However, I noticed that under the Port section of device manager, each time the X626 tries to reconnect to the PC, the name of the driver changes. It cycles from "MediaTek Preloader USB VCOM (Android) (COM3)" to "MediaTek USB Port (COM4)" in an endless loop. It's almost like the phone can't make up its mind about which driver to use. I am wondering if my earlier failed attempt to flash TWRP onto the x626 had caused this issue (along with bricking my phone)?
If anyone knows how to fix this problem please let me know. I'm fairly convinced that once the PC is able to connect, the unbricking process should be fairly straightforward!

I have some problem...

joebah said:
Okay, so I downloaded all three files "Windows+10_MTK+VCOM+USB+Preloader+Drivers.zip", "x620_flash_tool_androidbrick.7z" and "unbrick_tool_x626.zip" and extracted them. I tried the "How to fix le x626 undetected" step first given that none of this will work if the USB connection is not stable...
The problem is that because my PC keeps connecting and disconnecting from the X626, it's impossible to update my PC device driver as the instruction suggests. However, I noticed that under the Port section of device manager, each time the X626 tries to reconnect to the PC, the name of the driver changes. It cycles from "MediaTek Preloader USB VCOM (Android) (COM3)" to "MediaTek USB Port (COM4)" in an endless loop. It's almost like the phone can't make up its mind about which driver to use. I am wondering if my earlier failed attempt to flash TWRP onto the x626 had caused this issue (along with bricking my phone)?
If anyone knows how to fix this problem please let me know. I'm fairly convinced that once the PC is able to connect, the unbricking process should be fairly straightforward!
Click to expand...
Click to collapse
I've been through the same thing, soft bricked my phone the first day I got it ) . Long story short...black screen , just the red light when connecting the usb cable and pc just basically didn't recognize it or kept disconnecting when it did. I've spent 2 days playing around with it and I can't remember where but there is a site and a youtube clip that explains how to unbrick. What worked for me was pressing the volume up or volume down (try both since I don't remember which worked) when connecting the cable to the phone in Flash Tool/Mtk tools .IKeep pressing the volume button until the download starts and you see the green bar loading. otherwise it will imediatly disconnect. I know I'm a little cryptic here but it's my first phone with an MTK chip so the whole flash process is new to me . I'm more used with the simple Qualcomm process. Hope this helps.
I don't know if I'm allowed to post a link but here it is.. http://tickernel.org/how-to-unbrick-le-x626-red-light/

Catani said:
I've been through the same thing, soft bricked my phone the first day I got it ) . Long story short...black screen , just the red light when connecting the usb cable and pc just basically didn't recognize it or kept disconnecting when it did. I've spent 2 days playing around with it and I can't remember where but there is a site and a youtube clip that explains how to unbrick. What worked for me was pressing the volume up or volume down (try both since I don't remember which worked) when connecting the cable to the phone in Flash Tool/Mtk tools .IKeep pressing the volume button until the download starts and you see the green bar loading. otherwise it will imediatly disconnect. I know I'm a little cryptic here but it's my first phone with an MTK chip so the whole flash process is new to me . I'm more used with the simple Qualcomm process. Hope this helps.
I don't know if I'm allowed to post a link but here it is.. http://tickernel.org/how-to-unbrick-le-x626-red-light/
Click to expand...
Click to collapse
Okay, so It seems like different solution has different outcome for everyone. Instead of clicking download button on SP Flash Tool and plugging in the phone (which did not work), I did the opposite instead by plugging in the phone first and THEN immediately click download button on SP Flash Tool. Also, instead of holding down Vol - button I pressed it repeatedly (apparently someone claims that this confuses the SP Flash tool and sometimes it works). Then all of a sudden the flashing starts working :laugh:. However, the SP Flash tool bugged out after 10 seconds and told me the Flashing process failed , and I was back to square one. The odd thing is that when I tried replicating this method the flashing process won't start anymore (SP Flash tool just get hung up) - though at least the phone now connects to the PC USB permanently. ADB still tool doesn't work either. So I'll try deleting and reinstalling the device driver and tinker with this but it looks like the only way to resolve this is to try as many different things as possible. Will post again if I can find a solution but in the meanwhile if you have any other suggestions please let me know!

joebah said:
Hi - yes that's the site I am downloading the flashtool from. I pressed the volume +/- button and plugged in the phone after clicking on "Download" in the flash tool as you have suggested. It still disconnects and the download never happened - however the Flash tool gave me this this error message :
BROM ERROR : S_COM_PORT_OPEN_FAIL (0x3F5)
[COM] Failed to open COM port.
[HINT]:
Was this the same error you got from the Flash Tool when you tried plugging the phone when downloading? So you kept plugging it out and back in again until it worked right?
Click to expand...
Click to collapse
Yes. It was the same for me but eventually I got it. I can't remember exactly but I was swapping the volume button. I remember I kept pressing either volume up or down and the download went all the way. If you don't press the volume button you will constantly get those errors. It's trial and error...keep trying , eventually you will get it. Oh, and I was forgetting, you can also try to change the driver manually, you should have 3 drivers to choose from. Try all 3, because only one of them work.

owell
i managed to get mediatek usb port in device manager but my download wont start in the flash tool. have you managed to unbrick it? if so, please provide some help

Summarizing my experience with the bricked X626 (so far)
Okay, so after a few days of messing around with the x626 - I was still unable to get it fixed :crying:. However, since I spent quite a few hours tinkering with the flashing process, I figured I might as well document my experience on XDA so other people who are having the same issues can at least get to where I am without having to waste a few days messing around with their PC, and perhaps share their experience with the rest of the community once they are able to unbrick their x626!
Resolving USB connect/disconnect issue (Windows 10)
-------------------------------------------------------------------
This was finally resolved for me - and I found the following solution to work most of the time:
1) Restarted PC in troubleshooting mode
2) press "7" at startup screen option to enable the user to install unsigned drivers.
3) After the booting is completed, open device manager
4) Connect the x626 to the PC's USB, wait for the generic USB driver to show up under "Ports (COM & LPT)" (along with the USB connect chime sound). Sometimes, you have to wait for a minute or two for this to happen. If this doesn't work try holding the power button and Vol -, it 'wakes' up the phone somehow.
5) Once you see the new COM port lights up on Device Manager, quickly select it, right click, update driver and overwrite with the "MediaTek DA USB VCOM" from the Windows+10_MTK+VCOM+USB+Preloader+Drivers inf file (you'll have to google the instructions from other website but it's pretty straight forward).
6) After this, disconnect the x626 from the PC's USB port and reconnect again. The PC will most likely try to switch to another COM Port and reinstall another generic USB driver. If it does that, repeat step 5 and overwrite the new generic driver and COM port with the MediaTek DA USB VCOM driver . Keep doing this until you end up with a situation where you have the PC cycling between 2-3 COM ports in the connect/disconnect loop but at least they will be showing MediaTek DA USB VCOM every time.
7) Now reassign all these COM ports (right click, properties, Port setting, advanced) to a single designated port (like, say "3").
8) If you follow this instruction, the phone will still connect and disconnect from the USB, but each time it does so the phone will always connect to the same COM port and using the same driver - this will make it much easier to flash.
Resolving Flashing issue
------------------------------
This may not work for everyone, but this is what worked for me:
1) Power down the phone first (by holding Power button and Vol - button for 15 seconds since I have no way of telling if the phone is on or not due to the constant black screen) ,
2) Keep holding the Vol - button and plug the USB cable in, wait for the connection sound to chime on my PC
3) When that happens immediately click on Download button on Flashtool. Timing is crucial here, you have to be pretty quick with steps 2 and 3.
By doing this I was able to get the flashing going most of the time - though I do still get the "BROM ERROR : S_COM_PORT_OPEN_FAIL (0x3F5)" every now and then in which case I would unplug the phone from the USB and try again.
Dead end?
------------
Unfortunately, I wasn't quite able to flash everything. If I try to flash all the items in the Download table (except recovery and boot) using the Android scatter file, authentication file and DA_PL_HIGH.bin file per instruction, the status bar at the bottom of SP Flash Tool window would go from red (Downloading DA 100%) to purple (Download BootLoader 100%) - but then it ends up getting stuck for about 10 seconds, before giving me the error "BROM ERROR: STATUS_OPEN_FILE_ERR (0xC001000E)".
The ONLY way I can get the flashing process to go through completion is by unticking all the options on the download table except preloader. Only then would I get the "OK" notification from SP Flash Tool. Since the instructions on the web tells me that I should be ticking all the boxes except boot and recovery, I would imagine that this is not the correct way of doing things...
Fortunately, the Write Memory part works (that's where I press Ctrl Alt V, choose the Write Memory Tab, pick the recovery_stock_works _after_brick.img and type 0x8000 in the Being Address field). I used the same procedure as when flashing. So far so good...
But then I would run into the same problem again when flashing using DA_PL.bin file (supposedly the final part of the solution), with SP Flash tool tells me "BROM ERROR: STATUS_OPEN_FILE_ERR (0xC001000E)" .
So I am at a loss on what to do next. I did see some other people reporting that they got to where I am but pretty much can't progress any further due to this STATUS_OPEN_FILE_ERR problem... so if anyone is able to get through the flashing process and get their x626 to boot up, please please please share their experience, preferably on this thread! :fingers-crossed:

Catani said:
I've been through the same thing, soft bricked my phone the first day I got it ) . Long story short...black screen , just the red light when connecting the usb cable and pc just basically didn't recognize it or kept disconnecting when it did. I've spent 2 days playing around with it and I can't remember where but there is a site and a youtube clip that explains how to unbrick. What worked for me was pressing the volume up or volume down (try both since I don't remember which worked) when connecting the cable to the phone in Flash Tool/Mtk tools .IKeep pressing the volume button until the download starts and you see the green bar loading. otherwise it will imediatly disconnect. I know I'm a little cryptic here but it's my first phone with an MTK chip so the whole flash process is new to me . I'm more used with the simple Qualcomm process. Hope this helps.
I don't know if I'm allowed to post a link but here it is.. http://tickernel.org/how-to-unbrick-le-x626-red-light/
Click to expand...
Click to collapse
You could ask for my permission at least, to copy paste my article to your blog hmm ?

os_man said:
You could ask for my permission at least, to copy paste my article to your blog hmm ?
Click to expand...
Click to collapse
I'm sorry, are you talking to me? That's not my blog. I was just helping the guy with his problem, I posted a link to a site that I found while I was researching the same problem that I had. If any of that material found on the blog is yours you should take it up with the owner, if I'm not mistaken I think he's a XDA member also.

Catani said:
I'm sorry, are you talking to me? That's not my blog. I was just helping the guy with his problem, I posted a link to a site that I found while I was researching the same problem that I had. If any of that material found on the blog is yours you should take it up with the owner, if I'm not mistaken I think he's a XDA member also.
Click to expand...
Click to collapse
Sorry i ment the owner of that blog that you gave the link, the tickernel guy

Okay, so after taking a break for a few days to clear my head and then coming back to this problem, I finally noticed what I did wrong. I used the wrong scatter files and .img file for all the steps! That's why the flashing process never completed!
So for the first part, the configuration is supposed to look like this:
Download Agent : \..\..\x620_flash_tool_androidbrick\secureboot\DA_BL_HIGH.bin
Scatter-Loading File: \..\..\LeEco_x620_SP_Rom.androidbrick\MT6797_Android_scatter.txt
Authentication File: \..\..\x620_flash_tool_androidbrick\secureboot\auth_sv5_letv.auth
Untick Boot and Recovery, and now I can flash the entire thing (Green okay sign) without even having to hold down the Vol - or + button!
Then for the memory step, I used the boot-verified.img in the downloaded folder LeEco_x620_SP_Rom.androidbrick, and write to 0xf900000, this time I pressed the Vol + button, and the writing works (Green okay sign)
For the second memory step, I used the recovery_stock_works _after_brick.img in the folder LeEco_x620_SP_Rom.androidbrick, and write to 0x8000. Once again, the writing works (Green okay sign)
I am not sure if I did the DA_BR.bin step correctly or not... but after doing this the screen came on when I tried to boot! I did have to charge it first as the battery was completely dead. However, like the tutorial said, the screen is 'mirrored' (ie, it's like holding the phone to a mirror and seeing everything backward - really weird). So I can't use the phone at this point - But hey, this is the first time in two weeks that I am no longer stuck on a black screen when I tried to power on the phone! Woo hoo!
I feel like I am getting close to fixing this phone now... will post if there is any new development. So excited! :fingers-crossed:

Finally!
Okay, so I downloaded the file S3_X626.rar per the second part of the instruction - took a while but in the end it resolved all my problem. Here's my experience (I want to document before I forget about the details as it seems with this issue you need to get everything right to unbrick the phone)
So my phone screen is mirrored right now, I can kind of navigate around but have to guess where to touch the screen to go into apps and settings. Also, the baseband, EMEI and just about everything is missing. Clearly this was sort of a temporary ROM that gets the phone back into a semi ususable state. In fact, it took me a little while to figure out how to shutdown the phone again! (necessary for the next step)
After unzipping S3_X626.rar - it created a folder called "乐视S3_X626". I also got a bunch of warnings from Windows Defender about virus/Trojans etc - I ignored them.
I booted the phone in fastboot mode per instruction (Vol -, Power), and the familiar black screen with Chinese characters showed up on the phone. I then plugged in the phone into USB. By now my PC fully recognizes the X626! So no more annoying connect/disconnect problem.
I ran the file 开机oem解锁-音量下+开机键_读取Devices.bat. The Dos prompt did a bunch of stuff (I guess it's unlocking the bootloader?) and then a text file "Devices.txt" is generated in the folder. I guess this part just figures out some sort of ID of the phone? Anyway, onto the next step..
I ran 刷机.bat, immediately I got an error on the dos prompt and had to exit. So it turned out that for this step, I need to change the folder name from 乐视S3_X626 to S3_X626 by removing all the Chinese characters - which the instruction said though it wasn't very clear when the author wrote it. The dos prompt went through some sort of flashing process which took like 10 mins. When it was done, I unplugged the phone - and had to hold down the power button for a while to reboot (at first it just got stuck on the bootloader screen)
The next part is where things got interesting. So now the phone rebooted normally and the "EUI" logo showed up. Then it froze. So I rebooted the phone again, and this time the EUI logo showed up and it started to initialize the app (I think 15 of them). That took about 10 mins - thankfully I had my device all charged up before I did all this! Finally, we got to the setup screen, put in my Sim Card and connected to Wifi - skipped the finger print set up stuff and finally I am back to the home screen. Also, the EUI is now in version 5.9.020S (I was on 5.8 earlier), with baseband, IMEI and everything! Android 6.0 of course. Everything works as it should.
So this has been one heck of an effort to unbrick. To be honest, I was about to throw away the phone had it not been for the fact that it's the holiday seasons and I had a lot of down time on my hands . Must have spent a good 15-20 hours messing around with it. Definitely the USB connection and flashing were the hardest to figure out as there are all sorts of different instructions on the web on how to do this and there doesn't seem to be one right way of doing it - though I would have to say that the tickernel blog / OS_man instruction (not sure who owns the IP to this one but thanks guys) is the most helpful. My guess is if your phone is bricked and tried to copy my instruction word for word, there's still a good chance it won't work for you! Anyway, I figured documenting my experience on XDA would be helpful because at least you get to know what will happen if you get a step right (or wrong) - I was mostly in the dark when I did this. Merry X mas!

Thanks for directing me to the website. I have unbricked my phone now and put a detailed 'journal' of how I did this on my original post under "Edit" section for all to see! Have a happy new year!
alberto-a-l said:
250/5000
Hello, the same thing happened to me. Try using the manual on the following page ]ht tp://tickernel.org/how-to-unbrick-le-x626-red-light/ but the flashtool does not detect the terminal when trying to click on download does nothing. I do not know what to do...
Click to expand...
Click to collapse

Thanks for your help
Thanks for directing me to the website. I have unbricked my phone now and put a detailed 'journal' of how I did this on my original post under "Edit" section for all to see! Have a happy new year!
Catani said:
I've been through the same thing, soft bricked my phone the first day I got it ) . Long story short...black screen , just the red light when connecting the usb cable and pc just basically didn't recognize it or kept disconnecting when it did. I've spent 2 days playing around with it and I can't remember where but there is a site and a youtube clip that explains how to unbrick. What worked for me was pressing the volume up or volume down (try both since I don't remember which worked) when connecting the cable to the phone in Flash Tool/Mtk tools .IKeep pressing the volume button until the download starts and you see the green bar loading. otherwise it will imediatly disconnect. I know I'm a little cryptic here but it's my first phone with an MTK chip so the whole flash process is new to me . I'm more used with the simple Qualcomm process. Hope this helps.
I don't know if I'm allowed to post a link but here it is.. http://tickernel.org/how-to-unbrick-le-x626-red-light/
Click to expand...
Click to collapse

batch23 said:
i managed to get mediatek usb port in device manager but my download wont start in the flash tool. have you managed to unbrick it? if so, please provide some help
Click to expand...
Click to collapse
Hi - please see the edited version of the original post where I made a detailed documentation of what I did to unbrick the phone. It's been extremely frustrating for me too and I got stuck in the flashing stage for almost three weeks - but if you try what I did I think you might be able to get the flashing work though the result is not always consistent (ie, you may have to attempt to flash several times and double/triple check everything as one minor error will immediately cause an error). It's a pain but don't give up yet! Happy new year!

Hi - if you did come up with the solution on that tickernel site then thanks for your help for making my phone work again! Have a happy new year!
os_man said:
Sorry i ment the owner of that blog that you gave the link, the tickernel guy
Click to expand...
Click to collapse

Hi please see my documented solution in the edited section of the original post Happy new year!
rapidsebuja said:
I have some problem...
Click to expand...
Click to collapse

[PLZ HELP] Redmi 9c NFC won't enter fastboot, recovery or boot up.

Hi, I have a new redmi 9c NFC, it has an Mediatek chip, so I can instant unlock bootloader, I installed a MIUI 12.5 Port for this phone "https://forum.xda-developers.com/t/...dmi-9c-nfc-angelica-angelican-stable.4383125/"
I didn't had enough space for GApps I saw a tutorial on YouTube for expand system partition "
"
I deleted partitions, (super, recovery and cache). I accidentally rebooted my phone, and now i'ts on a black screen, no recovery, not fasboot, no vibrations, the only signal of life that I have is when I connect the phone to my computer, It appears like this: "Dispositivo serie USB (COM4)" (It's on spanish because I'm spanish, and sorry for my bad English) I can't use Mi flash or something. PLZ HELP, I'M DESESPERATED

AvZPablo4 said:
Hi, I have a new redmi 9c NFC, it has an Mediatek chip, so I can instant unlock bootloader, I installed a MIUI 12.5 Port for this phone "https://forum.xda-developers.com/t/...dmi-9c-nfc-angelica-angelican-stable.4383125/"
I didn't had enough space for GApps I saw a tutorial on YouTube for expand system partition "
"
I deleted partitions, (super, recovery and cache). I accidentally rebooted my phone, and now i'ts on a black screen, no recovery, not fasboot, no vibrations, the only signal of life that I have is when I connect the phone to my computer, It appears like this: "Dispositivo serie USB (COM4)" (It's on spanish because I'm spanish, and sorry for my bad English) I can't use Mi flash or something. PLZ HELP, I'M DESESPERATED
Click to expand...
Click to collapse
You can use instead SPFT.

I used SP Flash Tool. I watched a YouTube tutorial:
I didn't had luck, It said me : PTM changed from the ROM; It must be downloader. Please select "Formato Allí + Download" scene and try again
It didn't work on Format All . It grave me this error: ERROR : STATUS_UNKNOWN_STORAGE_SECTION_TYPE (0xC003000C). [HINT]:
I tried to search solutions but nothing.

Well, it is very risky to use this function, it may format the calibration data, and your IMEI, within other things, so you shouldn't have to try this option, before to take a backup and even be sure, that this backup will, really, restore the things.
Try flashing only the preloader first, then go for the rest of partitions. You also have this tool to back up every thing that is not corrupted, https://github.com/bkerler/mtkclient

SubwayChamp said:
Well, it is very risky to use this function, it may format the calibration data, and your IMEI, within other things, so you shouldn't have to try this option, before to take a backup and even be sure, that this backup will, really, restore the things.
Try flashing only the preloader first, then go for the rest of partitions. You also have this tool to back up every thing that is not corrupted, https://github.com/bkerler/mtkclient
Click to expand...
Click to collapse
Ok, I have a problem, I think that my phone is bricked forever. I watched a tutorial
It's a bad quality tutorial
It surprisely worked!! I obviously used Redmi 9c NFC files.
When the phone were flashing, my cat passed trough the cable and he desconnected it. It only flashed bootloader, but still no fastboot or something else Now, if I connect the mobile to the computer it says: The usb device is not recognized.
In the device manager it appears as: Unknown USB device (Device descriptor request error).
It has error code 43
I'm going to press the power button or something and try it again

AvZPablo4 said:
Ok, I have a problem, I think that my phone is bricked forever. I watched a tutorial
It's a bad quality tutorial
It surprisely worked!! I obviously used Redmi 9c NFC files.
When the phone were flashing, my cat passed trough the cable and he desconnected it. It only flashed bootloader, but still no fastboot or something else Now, if I connect the mobile to the computer it says: The usb device is not recognized.
In the device manager it appears as: Unknown USB device (Device descriptor request error).
It has error code 43
I'm going to press the power button or something and try it again
Click to expand...
Click to collapse
Well, what the guy is doing, is basically, installing the LibUSB dev filters, to get device recognized, and can bypass the DA/SLAA authentication, then it is flashing a firmware using SPFT, this usually, even in a serious bricking state, is not that hard, BUT, your main issue now, is that you repartitioned some essential images onto your device, so the safe way to keep it trying will be flashing once by once, every partition to detect exactly, which of them were altered (I guess super and data), flash first the preloader, and then proceed one by one.
For sure the option format all will fix your device but unfortunately, this will erase the calibration data and your IMEI, mainly, you have the option that you can back up all your partitions, no matter super nor recovery nor userdata, but the others, using the CLI tool I provided the link, after that you should perform a format all, and then restore them.

SubwayChamp said:
Well, what the guy is doing, is basically, installing the LibUSB dev filters, to get device recognized, and can bypass the DA/SLAA authentication, then it is flashing a firmware using SPFT, this usually, even in a serious bricking state, is not that hard, BUT, your main issue now, is that you repartitioned some essential images onto your device, so the safe way to keep it trying will be flashing once by once, every partition to detect exactly, which of them were altered (I guess super and data), flash first the preloader, and then proceed one by one.
For sure the option format all will fix your device but unfortunately, this will erase the calibration data and your IMEI, mainly, you have the option that you can back up all your partitions, no matter super nor recovery nor userdata, but the others, using the CLI tool I provided the link, after that you should perform a format all, and then restore them.
Click to expand...
Click to collapse
Thanks for the reply!!
I can't backup, Flash or something, my pc down't detect my phone, it's unrecognised, by device manager or in lib usb, I changed the usb cable and port but nothing, I can't connect the phone to the pc.
If I get the possibility of connect the phone to the pc successfully, I would try that! ( I reset PC but nothing)
I sent a (tablet quality) video reporting the problem a bit.

AvZPablo4 said:
Thanks for the reply!!
I can't backup, Flash or something, my pc down't detect my phone, it's unrecognised, by device manager or in lib usb, I changed the usb cable and port but nothing, I can't connect the phone to the pc.
If I get the possibility of connect the phone to the pc successfully, I would try that! ( I reset PC but nothing)
I sent a (tablet quality) video reporting the problem a bit.
Click to expand...
Click to collapse
Windows not recognizing is normal in this state because your device is trying to boot to system, then Windows can't detect it as MTP BUT to have the device detected properly for preloader mode, you firstly have to install all the proper MediaTek drivers, then, from LibUSB entries listed choose one from all, i.e. Dispositivo Compuesto USB, it doesn't matter that it is the right entry, but this entry, if it is succesfully changed, would serve to recognize it, always that the VCom, and preloader drivers are properly installed.

I installed all LibUSB entries, install mtk drivers but nothing, it says (the same as before):
USB device not recognized
The last USB device you connected to this computer did not work properly, and Windows did not recognize it.
Remember that I flashed bootloader (I don't know what it is for you, but in case it causes a conflict with the IMEI or I don't know)

AvZPablo4 said:
I installed all LibUSB entries, install mtk drivers but nothing, it says (the same as before):
USB device not recognized
The last USB device you connected to this computer did not work properly, and Windows did not recognize it.
Remember that I flashed bootloader (I don't know what it is for you, but in case it causes a conflict with the IMEI or I don't know)
Click to expand...
Click to collapse
You have to keep pressed the buttons, even while the device is connected to the PC, your device will pass through various states, then quickly you have to release your fingers.
Well, preloader is a kind of bootloader, in MediaTek.
Use this tool, to bypass, https://androidfilehost.com/?fid=17825722713688275528 when you have success from the tool, then just run SPFT, uncheck the options LIB USB DA match storage and Storage Life Cycle, also check USB full speed.

I'm going to try it right now. Im' going to edit this for give the results
1st edit: I didn't start yet to bypass that, but, it has password
2nd edit: I pressed power button for 15 seconds and pw button + vol up for 10 seconds but nothing, with all drivers and all, still at: unknown usb device

AvZPablo4 said:
I'm going to try it right now. Im' going to edit this for give the results
1st edit: I didn't start yet to bypass that, but, it has password
2nd edit: I pressed power button for 15 seconds and pw button + vol up for 10 seconds but nothing, with all drivers and all, still at: unknown usb device
Click to expand...
Click to collapse
The tool is mirrored from other sites though https://gsmatoztool.com/mtk-auth-bypass-tool-v26-new-update-latest-tool/
Press the three buttons, but pay attention to the sound of PC and to device manager when something change.
Also download the UsbDk 64-Bit installer from the site I linked, with mtk-client tool you also can do some things.

SubwayChamp said:
Press the three buttons, but pay attention to the sound of PC and to device manager when something change.
Click to expand...
Click to collapse
I pressed the 3 buttons at the same time by 5 minutes but nothing, no sound, no changes on device manager

AvZPablo4 said:
I pressed the 3 buttons at the same time by 5 minutes but nothing, no sound, no changes on device manager
Click to expand...
Click to collapse
The way to use the tool I linked is, clicking on bypass and pressing the two volume buttons, but probably you have to get your device listed in LibUSB, and quickly, install it, otherwise you won't be able to use SPFT.
This is the guide to get the things working, read carefully every step, if it's needed, then uninstall all the drivers and reinstall them, just what you need. https://forum.xda-developers.com/t/...india-6s-using-spflash-tool-for-free.4222027/

SubwayChamp said:
The way to use the tool I linked is, clicking on bypass and pressing the two volume buttons, but probably you have to get your device listed in LibUSB, and quickly, install it, otherwise you won't be able to use SPFT.
This is the guide to get the things working, read carefully every step, if it's needed, then uninstall all the drivers and reinstall them, just what you need. https://forum.xda-developers.com/t/...india-6s-using-spflash-tool-for-free.4222027/
Click to expand...
Click to collapse
Nope, I installed all, but when I connect it (vol up + vol down) the same, usb not recognized. This is a redmi 9C NFC, that realme has the same mtk chip, but it might change on this xiaomi

AvZPablo4 said:
Nope, I installed all, but when I connect it (vol up + vol down) the same, usb not recognized. This is a redmi 9C NFC, that realme has the same mtk chip, but it might change on this xiaomi
Click to expand...
Click to collapse
This is a generic guide that applies for any MediaTek device, I had Realme and Xiaomi. Try combining other hardware buttons, pay attention to this: you should keep pressing (even blindly because of no sign of life) assuming that your device is either on or off, and interchanging the buttons.

SubwayChamp said:
This is a generic guide that applies for any MediaTek device, I had Realme and Xiaomi. Try combining other hardware buttons, pay attention to this: you should keep pressing (even blindly because of no sign of life) assuming that your device is either on or off.
Click to expand...
Click to collapse
I kept pressing vol up + vol down for like 10 min, but, nothing

AvZPablo4 said:
I kept pressing vol up + vol down for like 10 min, but, nothing
Click to expand...
Click to collapse
It's not a matter of time, if after 15 seconds or around, you don't hear something either from your PC or your device, then clearly, it's not working.
What I'm trying to say is, that you have to press all the modes available, PWR + vol. down, PWR + vol. up, both volume buttons, three buttons, all that doing it blindly because you can't see something onto your display, so no sign of life.
To better understand what I'm trying to say, suppose that your device is on, then make the combination keys, to quickly power off your device, and pressing rapidly the combination keys to enter to preloader mode, but again, you have to do it BLINDLY, just assuming that your device is on, and after, if no results, the other way around, assuming that your device is off, just do the combination keys, if your device is off, then pressing the three buttons around 10 seconds, then your device can tend to power on, in this short time you have to press, only the two volume buttons and release the PWR button, do you understand? I have bricked my Redmi Note 9 some year ago, and I have really, really bricked my Realme 7, and I recovered this way.

SubwayChamp said:
It's not a matter of time, if after 15 seconds or around, you don't hear something either from your PC or your device, then clearly, it's not working.
What I'm trying to say is, that you have to press all the modes available, PWR + vol. down, PWR + vol. up, both volume buttons, three buttons, all that doing it blindly because you can't see something onto your display, so no sign of life.
To better understand what I'm trying to say, suppose that your device is on, then make the combination keys, to quickly power off your device, and pressing rapidly the combination keys to enter to preloader mode, but again, you have to do it BLINDLY, just assuming that your device is on, and after, if no results, the other way around, assuming that your device is off, just do the combination keys, if your device is off, then pressing the three buttons around 10 seconds, then your device can tend to power on, in this short time you have to press, only the two volume buttons and release the PWR button, do you understand? I have bricked my Redmi Note 9 some year ago, and I have really, really bricked my Realme 7, and I recovered this way.
Click to expand...
Click to collapse
No, i didn't get something, I'm desesperated, you can teamviwer me or something or... I DON'T KNOW

AvZPablo4 said:
No, i didn't get something, I'm desesperated, you can teamviwer me or something or... I DON'T KNOW
Click to expand...
Click to collapse
Not much I can do. I recommended all the best to bypass this. If you have taken it in consideration, then you should sort it out.
- Uninstall all the drivers, reinstall exactly only what you need.
- Be sure that LibUSB is properly installed.
- Install the UsbDK 64 bits installer from the site I linked and try also the mtk-client tool.
- The option Format all except bootloader in SPFT may help, but consider that it may erase your calibration data and IMEI, mainly.

Database Develop

welcome