Database Develop

Downgrade android 9

So ive upgraded to 9 but I dont like it... volume menus changed, wifi keeps dropping out (even after disabling auto turn on) etc. and I was very happy with 8.
I've been following the instructions from the Razor site to downgrade but whenever i run a fastboot command from the bootloader it just changes to the "powered by android" screen with a tiny "Press any key to shutdown" at the top.
Has anyone been able to do this successfully?
I've used fastboot and ADB a lot in the past so no idea why its doing this.

Take the Oreo .zip, unzip it, boot into bootloader, open up a Command Line/Terminal (depending on your OS), cd to the unzipped Oreo folder, type in fastboot flash-all, wait for that to end, then reboot into bootloader again and fastboot flash both boot and system (it should automatically flash it into the assigned partition)
I did this in order to update to MR1

downgrade issues
not what was being asked.
you need to use a 3rd party usbA to usbC cable (stock cable doesnt play well)
once thats done, test its connected using 'fastboot devices' you should see the serial number of your phone.
then run the flash_all command (remember to unlock bootloader and critical partition beforehand)
minimal adb and fastboot installer PLUS android bootloader interface driver is required if not installed already.
good luck

I just bought 4 micro USB to type c usb adapters from Walmart's website for 7 dollars. I can use all of my previous cables from my old phones. I haven't had one issue with them and my old fast charger from my Nexus 6 works and charges the phone rapidly. It's kinda clunky but beats spending 30 bucks on 1 cable.

It was a long night and I was on my 5th beer when I typed all that up!
My USB-C cable from OnePlus works fine with this phone on my laptop

I'll give it a go, but I'm already using a 3rd party usb3 to typeC... I could try with the stock USBC cable as my desktop has one?
The phone is receiving the command from the PC because no matter what fastboot comment I type the second I hit enter it goes to this same screen.
ABD commands work perfectly though, just fastboot has this issue.
Can't wait for TWRP.
Sent from my Phone 2 using Tapatalk

Spunkybob said:
I'll give it a go, but I'm already using a 3rd party usb3 to typeC... I could try with the stock USBC cable as my desktop has one?
The phone is receiving the command from the PC because no matter what fastboot comment I type the second I hit enter it goes to this same screen.
ABD commands work perfectly though, just fastboot has this issue.
Can't wait for TWRP.
Click to expand...
Click to collapse
I believe TWRP has already been released. Check the new kernel thread in the Development section. He states that by flashing his kernel, TWRP is also installed along side it. I haven't tested myself yet though.

jal3223 said:
I believe TWRP has already been released. Check the new kernel thread in the Development section. He states that by flashing his kernel, TWRP is also installed along side it. I haven't tested myself yet though.
Click to expand...
Click to collapse
Don't I need to use fastboot to flash the kernel :-/
Sent from my Phone 2 using Tapatalk

have you solved this problem?
Spunkybob said:
So ive upgraded to 9 but I dont like it... volume menus changed, wifi keeps dropping out (even after disabling auto turn on) etc. and I was very happy with 8.
I've been following the instructions from the Razor site to downgrade but whenever i run a fastboot command from the bootloader it just changes to the "powered by android" screen with a tiny "Press any key to shutdown" at the top.
Has anyone been able to do this successfully?
I've used fastboot and ADB a lot in the past so no idea why its doing this.
Click to expand...
Click to collapse
I am in the same ****.I think we not only need to unlock the bootloader but also need to unlock the critical.But none knows how to unlock the critical.I am stuck in here too.Hate this stupid phone.

capxcom said:
I am in the same ****.I think we not only need to unlock the bootloader but also need to unlock the critical.But none knows how to unlock the critical.I am stuck in here too.Hate this stupid phone.
Click to expand...
Click to collapse
fastboot flashing unlock_critical doesn't work for you?

Ventigo said:
fastboot flashing unlock_critical doesn't work for you?
Click to expand...
Click to collapse
Finally it works!I tried handurds of times,every time I enter flash unlock critical the phone will show up that tiny message on the top left press any key to shut down.I was thinking about selling this phone,then I changed the USB a-c cable and tried with a different USB port,and suddenly it worked!
I flashed the latest stock firmware and the new customised kernel,now it works great! The battery draining is normal I only need to charge it once a day

capxcom said:
Finally it works!I tried handurds of times,every time I enter flash unlock critical the phone will show up that tiny message on the top left press any key to shut down.I was thinking about selling this phone,then I changed the USB a-c cable and tried with a different USB port,and suddenly it worked!
I flashed the latest stock firmware and the new customised kernel,now it works great! The battery draining is normal I only need to charge it once a day
Click to expand...
Click to collapse
What did you do differently? I still get the same little text at the top which says press any key to shutdown after any fastboot command. Please help me because I'm so frustrated with this issue.

Lucifer6 said:
What did you do differently? I still get the same little text at the top which says press any key to shutdown after any fastboot command. Please help me because I'm so frustrated with this issue.
Click to expand...
Click to collapse
Change the USB cable and try a different USB port,I think that may work for you.good luck!

capxcom said:
Change the USB cable and try a different USB port,I think that may work for you.good luck!
Click to expand...
Click to collapse
I've tried that with 3 different cables across 6 different usb ports on 2 diff computers and nothing seems to work.. which way worked for you? or what fastboot command did you do that was successful?

Lucifer6 said:
I've tried that with 3 different cables across 6 different usb ports on 2 diff computers and nothing seems to work.. which way worked for you? or what fastboot command did you do that was successful?
Click to expand...
Click to collapse
I just use a different cable and a different USB port , which I did all this before and it didn't work,but I don't know why it worked this time.
I just use the command" xxx\fastboot flash unlock_critical"(hope I memories this right,better find it on the Razer website),the same command with the Razer phone 1 which is posted on Razer official website .You have to unlock the bootloader first just like the Razer phone 1, the only difference is you don't need to unlock the bootloader by typing unlock bootloader on the pc ,you can just operate on the phone to unlock bootloader by pressing the "unlock the bootloader "in the bootloader interface.
When you use the command to unlock the critical ,it might let you to select yes on the phone's bootloader interface ,you can also see it on the CMD of you pc,it say something like xxx success,and if you run the command again it will say something like " unlock failed (already unlocked)"
Then you can try with flashing the stock firmware to see if you unlock the critical successfully,if you can flash the stock firmware then you can use any fast boot command on this phone .I installed the costume kernel right after I flashed the stock firmware.it works like charm.:fingers-crossed:
now the phone never get over heating again and the battery can last a whole day under my havey use.
---------- Post added at 07:47 AM ---------- Previous post was at 07:35 AM ----------
Lucifer6 said:
I've tried that with 3 different cables across 6 different usb ports on 2 diff computers and nothing seems to work.. which way worked for you? or what fastboot command did you do that was successful?
Click to expand...
Click to collapse
Maybe you can also try to install the right bootloader driver which can be found on Razer website ,just check the official tutorial about flashing the stock firmware for Razer phone 1.
The bootloader driver is different from the adb diver.Better do everything exactly the same as it says in that tutorial step by step.

capxcom said:
I am in the same ****.I think we not only need to unlock the bootloader but also need to unlock the critical.But none knows how to unlock the critical.I am stuck in here too.Hate this stupid phone.
Click to expand...
Click to collapse
Edit: my phone didn't load newer posts
For everyone else, I was able to do this at work yesterday and I'm back on 8 and loving it.
Edit 2: it was either the different cable (same one as at home just lives at work) or the laptop did something different.
Sent from my Phone 2 using Tapatalk

Lucifer6 said:
I've tried that with 3 different cables across 6 different usb ports on 2 diff computers and nothing seems to work.. which way worked for you? or what fastboot command did you do that was successful?
Click to expand...
Click to collapse
Hey mate, for me I think the issue was that first I installed the fastboot drivers on my desktop then when I changed her it to the bootloader driver it didn't take correctly.
I'll clear out my driver cache on the PC and try the correct driver and see if it fixs the issue there.
Sent from my Phone 2 using Tapatalk

Spunkybob said:
Hey mate, for me I think the issue was that first I installed the fastboot drivers on my desktop then when I changed her it to the bootloader driver it didn't take correctly.
I'll clear out my driver cache on the PC and try the correct driver and see if it fixs the issue there.
Click to expand...
Click to collapse
Just follow this instruction to install the driver .
https://s3.amazonaws.com/cheryl-fac...stall_Android_Fastboot_Drivers_on_Windows.pdf
If you can install the stock firmware you should be able in use any fast boot command

capxcom said:
Just follow this instruction to install the driver .
https://s3.amazonaws.com/cheryl-fac...stall_Android_Fastboot_Drivers_on_Windows.pdf
Click to expand...
Click to collapse
I've already done it just saying what my issue was.
Sent from my Phone 2 using Tapatalk

Spunkybob said:
I've already done it just saying what my issue was.
Click to expand...
Click to collapse
Good for you!
I'm suggesting everyone to unlock the bootloader and the critical first before start to use it.My last RP2 can't start up ,it will freeze on the starting screen as I didn't do anything before using it,I can't do anything with it as the locked bootloader.Lucky for me,I returned it and then I bought a new one .I love this hardware but Razer's software team should be fired !Just hire someone from xda should work perfectly:laugh:

Bought a used Mi A2, how do I proceed?

Just bought a used Mi A2 from a guy. He dosent know what Android version it is and its probably locked. Ive been out of the Android game for many years now, but managed to install ADB and Fastboot on my Mac.
The problem is that the device is boot looping on the Android One logo. Managed to get into Fastboot, and the device shows up in ./fastboot devices. Tried to run this quickie, but only get a "Device is already locked!" message.
So please, point me in the right direction as both the Internet and forums here are loaded with information.
In the end I would like to have a custom ROM, LinageOS or something maybe.
Thanks in advance.

joachimvadseth said:
Just bought a used Mi A2 from a guy. He dosent know what Android version it is and its probably locked. Ive been out of the Android game for many years now, but managed to install ADB and Fastboot on my Mac.
The problem is that the device is boot looping on the Android One logo. Managed to get into Fastboot, and the device shows up in ./fastboot devices. Tried to run this quickie, but only get a "Device is already locked!" message.
So please, point me in the right direction as both the Internet and forums here are loaded with information.
In the end I would like to have a custom ROM, LinageOS or something maybe.
Thanks in advance.
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375

1st try to reboot numerously with external power On (if there is a valid Android One ROM in one of two slots, sooner or later bootloader is to boot into this valid ROM).
In case phone does not have a valid Android One ROM, then next step would be MiFlash'ing via EDL (search for TestPoint Guide in "Guides, ....")

Aerobatic said:
1st try to reboot numerously with external power On (if there is a valid Android One ROM in one of two slots, sooner or later bootloader is to boot into this valid ROM).
In case phone does not have a valid Android One ROM, then next step would be MiFlash'ing via EDL (search for TestPoint Guide in "Guides, ....")
Click to expand...
Click to collapse
Like just boot loop it or hold the power to reboot?
I think the EDL pinout opiton is the way to go after some searching, but Im in a desperate need of a torx driver..

joachimvadseth said:
Like just boot loop it or hold the power to reboot?
Click to expand...
Click to collapse
Some people reported that phone rebooted just itself while bootlooping with external power, others recommended to enter fastboot mode and reboot, others recommended to enter stock recovery mode (note that there is a gotcha of "no command" -> press "Power" and then "Vol-") and then "try again: ....

Aerobatic said:
Some people reported that phone rebooted just itself while bootlooping with external power, others recommended to enter fastboot mode and reboot, others recommended to enter stock recovery mode (note that there is a gotcha of "no command" -> press "Power" and then "Vol-") and then "try again: ....
Click to expand...
Click to collapse
In Fastboot the device only displays "fastboot", no options what so ever. Tried powering on the device without power cable 20 times and no go, boot looped on external power for about 10 minutes, no go.

joachimvadseth said:
In Fastboot the device only displays "fastboot", no options what so ever. Tried powering on the device without power cable 20 times and no go, boot looped on external power for about 10 minutes, no go.
Click to expand...
Click to collapse
Sure there is no options in fastboot mode, "enter fastboot mode and reboot" means just that -> enter fastboot mode and then reboot (either long-pressing power on phone or with "fastboot reboot" command from PC.
I gave you clues, please don't tease me to dictate step-by-step, I do not own your phone.

Aerobatic said:
Sure there is no options in fastboot mode, "enter fastboot mode and reboot" means just that -> enter fastboot mode and then reboot (either long-pressing power on phone or with "fastboot reboot" command from PC.
I gave you clues, please don't tease me to dictate step-by-step, I do not own your phone.
Click to expand...
Click to collapse
Ye sure, thats fine mate
did 'fastboot reboot' about 10 times now and still no go.
Found a Xiaomitool for macOS that has an option for "unbrick my device", but need the previous owners Mi account probably, so Ive asked if he did have a Mi account.

joachimvadseth said:
Found a Xiaomitool for macOS that has an option for "unbrick my device", but need the previous owners Mi account probably, so Ive asked if he did have a Mi account.
Click to expand...
Click to collapse
Most probably that's a false path, as MiFlash, Mi Account, Mi Unlock and other such stuff are for owners of "native" Xiaomi MIUI phones, while Mi A2 boarding Android One is regarded as stepchild. Better search for Android One solutions (in these forums of in developer.android.com)

Aerobatic said:
Most probably that's a false path, as MiFlash, Mi Account, Mi Unlock and other such stuff are for owners of "native" Xiaomi MIUI phones, while Mi A2 boarding Android One is regarded as stepchild. Better search for Android One solutions (in these forums of in developer.android.com)
Click to expand...
Click to collapse
Maybe. I think the phone is stock, just bricked after some update.
Just need to get the bloody torx driver!
EDIT: when I do manage to find a tiny tiny torx driver and open up the phone, disconnect the battery a bit, connect it back up, and its time to connect the two EDL pins, how long do I hold? USB cable plugged in?

Yes I have same issue, I dont understand, why Xiaomi dont do anything with this ridiculous problem, I dont login with mi account because no paid attention to that, and when I install this update the phone get in bootloop

joachimvadseth said:
..., and its time to connect the two EDL pins, how long do I hold? USB cable plugged in?
Click to expand...
Click to collapse
Disclamer: Have not done it myself, but according to numerous sources the needed Steps (here with Windows PC) are:
1. Open (partially disassemble) Phone to reach 2 contact Test Point spots
2. Connect stock USB cable to USB2.x port on MB of PC, but not to phone, start Device Manager (to see that no USB-phone-related devices are connected and later to see that phone will be connected in EDL)
3. Download desired stock fastboot ROM https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849 and MiFlash, start MiFlash selecting ROM
4. Span the two contacts with something metal and in this state connect USB cable to phone; Device Manager must show newly connected device detected, then contacts may be open
5. Press "Refresh" in MiFlash, same new device must be displayed
6. MiFlash -> clean all, MiFlash -> flash
7. Assemble phone back and reboot
MHO Notes:
a. when EDL/TestPoint method was forced due to soft-bricking, after unbricking it is better to: (1) fully unlock phone and (2) clean-reflash stock ROM via fasboot
(Reason: this particular specimen is subject to OTA soft -bricking)
b. if EDL/TestPoint method fails with Pie (10.0.17.0 or 10.0.2.0), retry using Oreo 9.6.17.0 or 9.6.9.0.
---------- Post added at 01:01 PM ---------- Previous post was at 12:52 PM ----------
Onilink90 said:
..., and when I install this update the phone get in bootloop
Click to expand...
Click to collapse
Xiaomi is just repacking Google's Android One updates, and, obviously, does not spend much money for testing OTAs (as AndroidOne phones are not their main market items). From the other hand, Google's Android One A/B Slots feature was developed for so called friction-less ( muhaha ) reverting to previously working ROM when updated ROM fails to boot. So, an Android One phone bootlooping after OTA MUST reboot to previous version of ROM sooner or later (supposed to be 7 retries), sure if phone is not compromised / tampered by previous user actions.

Aerobatic said:
Disclamer: Have not done it myself, but according to numerous sources the needed Steps (here with Windows PC) are:
1. Open (partially disassemble) Phone to reach 2 contact Test Point spots
2. Connect stock USB cable to USB2.x port on MB of PC, but not to phone, start Device Manager (to see that no USB-phone-related devices are connected and later to see that phone will be connected in EDL)
3. Download desired stock fastboot ROM https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849 and MiFlash, start MiFlash selecting ROM
4. Span the two contacts with something metal and in this state connect USB cable to phone; Device Manager must show newly connected device detected, then contacts may be open
5. Press "Refresh" in MiFlash, same new device must be displayed
6. MiFlash -> clean all, MiFlash -> flash
7. Assemble phone back and reboot
MHO Notes:
a. when EDL/TestPoint method was forced due to soft-bricking, after unbricking it is better to: (1) fully unlock phone and (2) clean-reflash stock ROM via fasboot
(Reason: this particular specimen is subject to OTA soft -bricking)
b. if EDL/TestPoint method fails with Pie (10.0.17.0 or 10.0.2.0), retry using Oreo 9.6.17.0 or 9.6.9.0.
---------- Post added at 01:01 PM ---------- Previous post was at 12:52 PM ----------
Xiaomi is just repacking Google's Android One updates, and, obviously, does not spend much money for testing OTAs (as AndroidOne phones are not their main market items). From the other hand, Google's Android One A/B Slots feature was developed for so called friction-less ( muhaha ) reverting to previously working ROM when updated ROM fails to boot. So, an Android One phone bootlooping after OTA MUST reboot to previous version of ROM sooner or later (supposed to be 7 retries), sure if phone is not compromised / tampered by previous user actions.
Click to expand...
Click to collapse
Managed to get hold of a torx set - phone is now open, battery disconncted. USB-C cable ready (dont have USB-A-C, only USB-C-C). Installed MiFlashTool on my PC and tried to get hold of the drivers. MIFlash is giving me a hard time whineing about drivers. Giving me a erorr message, something about JIT-debugging. Only got it in norwegian.
Edit: managed to flash the stock ROM I think. Fuzzed around a bit with the qualcom driver. Now I have a white screen with a rainbow passing over it..
Edit 2: and we're there! MIUI is in - now time to get rid of it!
Edit 3: think I managed to flash TWRP now - do I need root? Can I just flash a Pixelexperience ROM now or do I need to do something else? Used the Android 9 fastboot image earlier, if that has anyting to do with anything.

[HELP] Mi6x HARD bricked?

Good day everybody
Straight to the point. I tried to flash a different rom, EU version of MI6X MIUI on my device and suddenly, at the reboot after the flash, the screen remained black.
Strange thing is that the device is still detected through usb on my pc, even on MiFlash its detected. But i cannot do anything, tried flashing a rom with Miflash but i get Catastrophic Error!
Please someone help me i dont want to change this phone!
Thank you so much!
Edit: after researching, i seem to be stuck in a useless EDL mode. My pc can detect the phone (Qualcomm 9008), but MiFlash cannot flash anything. The flash starts and based on the version of MiFlash im using gets stuck after a couple of seconds. for a different reason (Authentication on 2018 version, Send configure command on 2015 version) I dont understand. Please help

Marduk666 said:
Good day everybody
Straight to the point. I tried to flash a different rom, EU version of MI6X MIUI on my device and suddenly, at the reboot after the flash, the screen remained black.
Strange thing is that the device is still detected through usb on my pc, even on MiFlash its detected. But i cannot do anything, tried flashing a rom with Miflash but i get Catastrophic Error!
Please someone help me i dont want to change this phone!
Thank you so much!
Edit: after researching, i seem to be stuck in a useless EDL mode. My pc can detect the phone (Qualcomm 9008), but MiFlash cannot flash anything. The flash starts and based on the version of MiFlash im using gets stuck after a couple of seconds. for a different reason (Authentication on 2018 version, Send configure command on 2015 version) I dont understand. Please help
Click to expand...
Click to collapse
if it is in EDL you are in luck .
follow this guide :
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-unbrick-arb-edl-t3846426

KevMetal said:
if it is in EDL you are in luck .
follow this guide :
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-unbrick-arb-edl-t3846426
Click to expand...
Click to collapse
Hey thanks!
But i already tried this, with no luck. Miflash doesnt allow me to flash anything. Can you maybe suggest why?

Marduk666 said:
Hey thanks!
But i already tried this, with no luck. Miflash doesnt allow me to flash anything. Can you maybe suggest why?
Click to expand...
Click to collapse
i can only tell if you can tell me exactly your error

KevMetal said:
i can only tell if you can tell me exactly your error
Click to expand...
Click to collapse
On MiFlash 2018 for example, i get the Not Authorized to Download error.
Maybe the fact that i tried to flash a global rom is the problem?

Try to install twrp , and flash hex kernel , and them flash EU rom, if is not possible , try to flash vía TEST POINT

Enriquecalong said:
Try to install twrp , and flash hex kernel , and them flash EU rom, if is not possible , try to flash vía TEST POINT
Click to expand...
Click to collapse
That is the point. Its already in EDL mode, and my pc sees the phone. But Miflash doesnt allow me to flash because of authorization.

Marduk666 said:
On MiFlash 2018 for example, i get the Not Authorized to Download error.
Maybe the fact that i tried to flash a global rom is the problem?
Click to expand...
Click to collapse
that error is because of your ARB .. DOwnload the latest rom with highest ARB level ...like explained in the guide
if you have latest rom with highest ARB level but still get errors start trying all different versions of Miflash ..I tried three or four before I found one which worked ..

KevMetal said:
that error is because of your ARB .. DOwnload the latest rom with highest ARB level ...like explained in the guide
if you have latest rom with highest ARB level but still get errors start trying all different versions of Miflash ..I tried three or four before I found one which worked ..
Click to expand...
Click to collapse
So i tried again with this release V10.3.6.0.PDCCNXM_20190816.0000.00_9.0_cn, with multiple different miflash builds, same error. Tried patching the rom and not. Nothing worked, same edl authentication problem.
I believe, pretty sure, this is the build that bricked the phone: xiaomi.eu_multi_MI6X_8.6.28_v10-8.1
Maybe it can help you understand better? Also, how do i determine which is the highest ARB build available?
Thank you so much for the help!

KevMetal said:
that error is because of your ARB .. DOwnload the latest rom with highest ARB level ...like explained in the guide
if you have latest rom with highest ARB level but still get errors start trying all different versions of Miflash ..I tried three or four before I found one which worked ..
Click to expand...
Click to collapse
Found out how to get the ARB level, but still, i think i stuck on ARB4 and even if i flash an ARB4 rom, which i tried, i just get the same error. Really dont now what to do.

Marduk666 said:
Found out how to get the ARB level, but still, i think i stuck on ARB4 and even if i flash an ARB4 rom, which i tried, i just get the same error. Really dont now what to do.
Click to expand...
Click to collapse
you need to download and try many different versions of Miflash
---------- Post added at 02:41 PM ---------- Previous post was at 02:37 PM ----------
Marduk666 said:
So i tried again with this release V10.3.6.0.PDCCNXM_20190816.0000.00_9.0_cn, with multiple different miflash builds, same error. Tried patching the rom and not. Nothing worked, same edl authentication problem.
I believe, pretty sure, this is the build that bricked the phone: xiaomi.eu_multi_MI6X_8.6.28_v10-8.1
Maybe it can help you understand better? Also, how do i determine which is the highest ARB build available?
Thank you so much for the help!
Click to expand...
Click to collapse
did this brick happen when you wanted to change from jasmine to wayne ?
the error you are getting is your phone was stuck in EDL too long ...if you wait for more than 10 seconds you get error ..
open your phone manually amd enter edl again with test point
change to Miflash amd flash but dont wait longer than few seconds
also try with QFIL ...sometimes it will work when Miflash has timeout error
and every error is different ..if you dont tell me the error i can not say ..if you bricked with the 8.1 rom you dont have bad situation .. low ARB ..or if you used conversion zip you wont have ARB and your problem is you are too long in Edl mode
try to enter fastboot by holding power and volume down for very long time ..
if it doesnt work your only way is test point ..im sure you dont want that problem but it is all
explain your errors better if you want success ...if you go to fastboot see if computer will listen to command
fastboot oem edl
try the flashing again .....

look below

KevMetal said:
you need to download and try many different versions of Miflash
---------- Post added at 02:41 PM ---------- Previous post was at 02:37 PM ----------
did this brick happen when you wanted to change from jasmine to wayne ?
the error you are getting is your phone was stuck in EDL too long ...if you wait for more than 10 seconds you get error ..
open your phone manually amd enter edl again with test point
change to Miflash amd flash but dont wait longer than few seconds
also try with QFIL ...sometimes it will work when Miflash has timeout error
and every error is different ..if you dont tell me the error i can not say ..if you bricked with the 8.1 rom you dont have bad situation .. low ARB ..or if you used conversion zip you wont have ARB and your problem is you are too long in Edl mode
try to enter fastboot by holding power and volume down for very long time ..
if it doesnt work your only way is test point ..im sure you dont want that problem but it is all
explain your errors better if you want success ...if you go to fastboot see if computer will listen to command
fastboot oem edl
try the flashing again .....
Click to expand...
Click to collapse
Ok so, ill retry explaining
I was on a CHINA Wayne MI6X originally, unlocked bootloader and TWRP. It was only updated through OTA and never flashed any custom rom before.
Then, i tried through TWRP to flash this build xiaomi.eu_multi_MI6X_8.6.28_v10-8.1, which is a EU rom, think it is A2 rom and the devices reboot to a black screen, EDL mode.
After, i tried flashing many different versions of WAYNE CHINA roms through different builds on MiFlash but none worked. MIUI 10, 11, even 9 but always get EDL AUTHENTICATION error.
So, CHINA to EU to EDL bricked phone.
Now, i tried rebooting to fastboot holding for a long time VOL- POWER button but adb doesnt see the phone, i think im still in EDL mode, because device managaer sees it as QUALCOMM 9008.
Also, now on MiFlash 2014 i get Error loading type library/DDL. (0x80029c4a: wait port ready to use 9)
Same on MiFlash 2015 and 2016.
On MiFlash 2018 i get EDL AUTHETICATION error.
Same o Miflash 2017.
Let me know if you understanded better, still, thank you again!

Marduk666 said:
Ok so, ill retry explaining
I was on a CHINA Wayne MI6X originally, unlocked bootloader and TWRP. It was only updated through OTA and never flashed any custom rom before.
Then, i tried through TWRP to flash this build xiaomi.eu_multi_MI6X_8.6.28_v10-8.1, which is a EU rom, think it is A2 rom and the devices reboot to a black screen, EDL mode.
After, i tried flashing many different versions of WAYNE CHINA roms through different builds on MiFlash but none worked. MIUI 10, 11, even 9 but always get EDL AUTHENTICATION error.
So, CHINA to EU to EDL bricked phone.
Now, i tried rebooting to fastboot holding for a long time VOL- POWER button but adb doesnt see the phone, i think im still in EDL mode, because device managaer sees it as QUALCOMM 9008.
Also, now on MiFlash 2014 i get Error loading type library/DDL. (0x80029c4a: wait port ready to use 9)
Same on MiFlash 2015 and 2016.
On MiFlash 2018 i get EDL AUTHETICATION error.
Same o Miflash 2017.
Let me know if you understanded better, still, thank you again!
Click to expand...
Click to collapse
ok man i think you made a big mistake flashing that package because it locked your bootloader ( i think ) ....
if the computer can see your phone as qualcomm9008 it is in EDL mode
you can save your phone but the authentication error ..could be ARB or locked bootloader ..
but anyway your best and ONLY option now is to get android 10 .zip for Wayne ...latest update for MIUI .. then
follow the instructions in the unbricking thread i sent you ..unzip ..search for folder in MIFLASH ..
-download QFIL flasher ..install and run AT SAME TIME
- select the choose port manually option and leave window open
( so three windows open .. miflash ( ready ) ... QFIL with sekect port open )
- then connect your usb cable to computer ( not phlone )
- get a paperclip and open it and fold it in half to look lkke tweezers
- then on another phone or computer follow video on how to open phone and do test point ( you will hold the twi points of the paperclip on two points in the phone )
- while holding the pin on the points insert usb to phone with free hand
- look at the select port manually window of QFIL ...when you see a device appears here let go of pin ..
now say okay to close sekect port window so it closes ..
- on Miflash press " refresh " then "flash" QUICKLY ..dont wait longer than 10 sec
- it will start to flash
*to opem your phone you need a guitar pick to push between the screen and body ...also special screw driver ( buy on Amazon ) to remove screws you see in video ..
# the reason is your phone has been too long in EDL to flash anymore ..so if you cant exit and enter EDL withbuttons or fastboot you ONLY have one option and that is testpoint
#that is why i said it must in 10 sec after you enter EDL that you flash or you will just have more errors everytime
***then you must just continue to enter and exit tesrpoint using my technique until one copy of Miflash will finish without error .BUT KEEP IN MIND ..everytime you fail you need to start over bevause too much time passed since you were in EDL
******dont lose hope beause miflash will accept and flash the officiak rom ARB4 ... if you find the right miflash version amd start flashing before EDL timeout
good luck bro go watch testpoint video and search for a guitar pick and screwdriver

KevMetal said:
ok man i think you made a big mistake flashing that package because it locked your bootloader ( i think ) ....
if the computer can see your phone as qualcomm9008 it is in EDL mode
you can save your phone but the authentication error ..could be ARB or locked bootloader ..
but anyway your best and ONLY option now is to get android 10 .zip for Wayne ...latest update for MIUI .. then
follow the instructions in the unbricking thread i sent you ..unzip ..search for folder in MIFLASH ..
-download QFIL flasher ..install and run AT SAME TIME
- select the choose port manually option and leave window open
( so three windows open .. miflash ( ready ) ... QFIL with sekect port open )
- then connect your usb cable to computer ( not phlone )
- get a paperclip and open it and fold it in half to look lkke tweezers
- then on another phone or computer follow video on how to open phone and do test point ( you will hold the twi points of the paperclip on two points in the phone )
- while holding the pin on the points insert usb to phone with free hand
- look at the select port manually window of QFIL ...when you see a device appears here let go of pin ..
now say okay to close sekect port window so it closes ..
- on Miflash press " refresh " then "flash" QUICKLY ..dont wait longer than 10 sec
- it will start to flash
*to opem your phone you need a guitar pick to push between the screen and body ...also special screw driver ( buy on Amazon ) to remove screws you see in video ..
# the reason is your phone has been too long in EDL to flash anymore ..so if you cant exit and enter EDL withbuttons or fastboot you ONLY have one option and that is testpoint
#that is why i said it must in 10 sec after you enter EDL that you flash or you will just have more errors everytime
***then you must just continue to enter and exit tesrpoint using my technique until one copy of Miflash will finish without error .BUT KEEP IN MIND ..everytime you fail you need to start over bevause too much time passed since you were in EDL
******dont lose hope beause miflash will accept and flash the officiak rom ARB4 ... if you find the right miflash version amd start flashing before EDL timeout
good luck bro go watch testpoint video and search for a guitar pick and screwdriver
Click to expand...
Click to collapse
Thank a lot man, really! But i DID IT! Following this guide! https://miui.blog/mi-6x/unbrick-mi-6x-wayne/
Now my phone works again, thank you a lot still, for you patience!

Marduk666 said:
Thank a lot man, really! But i DID IT! Following this guide! https://miui.blog/mi-6x/unbrick-mi-6x-wayne/
Now my phone works again, thank you a lot still, for you patience!
Click to expand...
Click to collapse
ok good work it is a good guide and it will help other people if they have trouble finding modified programmer files or connecting the phone and flashing quickly enough
here the difference was that i assumed but forgot to remind you to use the patched programmer files not to be rejecting but it was also included in the post of other XDA guy :good:

ADB Works, Fastboot still "waiting for any device"

I have been blundering my way though the internet to get my ROG Phone 2 rooted. I have unlocked the bootloader, I have a modified boot image from magisk, I have the ADB connection set up through USB and it works fantastically. I honestly don't know how I got it work, it involved many different driver update attempts and then figuring out I hadn't put the phone into USB debugging, but now fastboot doesn't work.
ADB will list the device, but fastboot cannot see it. I have tried rebooting the phone into the bootloader, but there is no connection on either. Not sure why I thought that would work, but I tried. I really don't understand enough about fastboot to get any farther on my own.
I have the tencent version and I was pretty certain I have the CN android 9.0 on it, but I am no longer certain of that. I am running windows 10.
This is my build number: PKQ1.190414.001.WW_Phone-16.0622.1906.19-0
I honestly don't know, but does that WW mean my tencent phone is running the WW firmware?

RichDoe252 said:
I have been blundering my way though the internet to get my ROG Phone 2 rooted. I have unlocked the bootloader, I have a modified boot image from magisk, I have the ADB connection set up through USB and it works fantastically. I honestly don't know how I got it work, it involved many different driver update attempts and then figuring out I hadn't put the phone into USB debugging, but now fastboot doesn't work.
ADB will list the device, but fastboot cannot see it. I have tried rebooting the phone into the bootloader, but there is no connection on either. Not sure why I thought that would work, but I tried. I really don't understand enough about fastboot to get any farther on my own.
I have the tencent version and I was pretty certain I have the CN android 9.0 on it, but I am no longer certain of that. I am running windows 10.
This is my build number: PKQ1.190414.001.WW_Phone-16.0622.1906.19-0
I honestly don't know, but does that WW mean my tencent phone is running the WW firmware?
Click to expand...
Click to collapse
Fun fact, I just got Fastboot access from my computer by using the side USB port and rebooting into the bootloader from ADB. Still not to sure about the version bit. I think I'm just going to give it whirl and brick my device, maybe.

RichDoe252 said:
I have been blundering my way though the internet to get my ROG Phone 2 rooted. I have unlocked the bootloader, I have a modified boot image from magisk, I have the ADB connection set up through USB and it works fantastically. I honestly don't know how I got it work, it involved many different driver update attempts and then figuring out I hadn't put the phone into USB debugging, but now fastboot doesn't work.
ADB will list the device, but fastboot cannot see it. I have tried rebooting the phone into the bootloader, but there is no connection on either. Not sure why I thought that would work, but I tried. I really don't understand enough about fastboot to get any farther on my own.
I have the tencent version and I was pretty certain I have the CN android 9.0 on it, but I am no longer certain of that. I am running windows 10.
This is my build number: PKQ1.190414.001.WW_Phone-16.0622.1906.19-0
I honestly don't know, but does that WW mean my tencent phone is running the WW firmware?
Click to expand...
Click to collapse
1. You are running a WW rom, but that doesn't necessarily mean your fingerprint is matched. To update you need to have both WW rom and WW fingerprint. You can check if your fingerprint is CN or WW using device info hw from playstore under 'system'
2. In order to root you need to have a matching root boot img for your current rom ie root img for 1906.19, just checking that your know this?
3. Have you managed to get the phone recognised using the cmd 'fastboot devices'? Also are you using the side port?
4.when you say bootloader, have you definitely got the phone in fastboot mode - hold vol up and power button until you see the screen with some options. That screen is fastboot mode, you don't need to select any further options. Once in that mode, connect to pc, open adb and run the fastboot devices cmd. Once your device is recognised, report back here for further steps

superbrick.
reg66 said:
1. You are running a WW rom, but that doesn't necessarily mean your fingerprint is matched. To update you need to have both WW rom and WW fingerprint. You can check if your fingerprint is CN or WW using device info hw from playstore under 'system'
2. In order to root you need to have a matching root boot img for your current rom ie root img for 1906.19, just checking that your know this?
3. Have you managed to get the phone recognised using the cmd 'fastboot devices'? Also are you using the side port?
4.when you say bootloader, have you definitely got the phone in fastboot mode - hold vol up and power button until you see the screen with some options. That screen is fastboot mode, you don't need to select any further options. Once in that mode, connect to pc, open adb and run the fastboot devices cmd. Once your device is recognised, report back here for further steps
Click to expand...
Click to collapse
Thanks for the reply! I did indeed get fastboot to work over USB. Fastboot devices reported back the serial number and everything. I did not know that the build need to match on both the boot and the rom, but that does make sense and I probably should have realized that before I went ahead and copied the rooted boot.img I had over. Then my phone couldn't boot up proper, and got stuck in fastboot. Then I went ahead and copied all of the contents of the same rom over and now it is literally just a black screen. Won't turn on any more. I think I super bricked it.
Sorry I didn't see your post earlier and I know I am not father into the deep end, but is there a way out from where I am.

RichDoe252 said:
Thanks for the reply! I did indeed get fastboot to work over USB. Fastboot devices reported back the serial number and everything. I did not know that the build need to match on both the boot and the rom, but that does make sense and I probably should have realized that before I went ahead and copied the rooted boot.img I had over. Then my phone couldn't boot up proper, and got stuck in fastboot. Then I went ahead and copied all of the contents of the same rom over and now it is literally just a black screen. Won't turn on any more. I think I super bricked it.
Sorry I didn't see your post earlier and I know I am not father into the deep end, but is there a way out from where I am.
Click to expand...
Click to collapse
Oh jeepers dude. So just a black screen... Can you at least boot into fastboot?

reg66 said:
Oh jeepers dude. So just a black screen... Can you at least boot into fastboot?
Click to expand...
Click to collapse
Nope. The only response I can get out of it now is when I plug it into the fastboot port, the computer recognizes that something was plugged in. I don't even get a device on a device manager.

RichDoe252 said:
Nope. The only response I can get out of it now is when I plug it into the fastboot port, the computer recognizes that something was plugged in. I don't even get a device on a device manager.
Click to expand...
Click to collapse
Try holding the power button for around 20 secs until it shuts down. Then try vol up and power together and see if you get back to fastboot. If that doesn't work try vol up vol down and power buttons all together. Then try again to put it in fastboot mode using vol up and power. Let us know what happens /if you can reach fastboot mode

reg66 said:
Try holding the power button for around 20 secs until it shuts down. Then try vol up and power together and see if you get back to fastboot. If that doesn't work try vol up vol down and power buttons all together. Then try again to put it in fastboot mode using vol up and power. Let us know what happens /if you can reach fastboot mode
Click to expand...
Click to collapse
Unfortunately, nothing. Holding power for 20 seconds showed nothing, and like wise for volume up and power. Battery was fully charged too. Had it plugged in for most of today while I was trying to get fastboot to work.

RichDoe252 said:
Unfortunately, nothing. Holding power for 20 seconds showed nothing, and like wise for volume up and power. Battery was fully charged too. Had it plugged in for most of today while I was trying to get fastboot to work.
Click to expand...
Click to collapse
Is there any sort of illumination to the black screen ie do you think the phone is on but the screen is black or do think the phone is completely off?
Holding power button for a while should switch it off after a while. Try holding for longer than 20 secs, then try booting into fastboot mode
---------- Post added at 04:00 AM ---------- Previous post was at 03:44 AM ----------
Well dude, it's 4 am here. Gotta get some sleep dude. Will check here when I wake. Good luck in the mean time

Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results

reg66 said:
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
Click to expand...
Click to collapse
Bro get to sleep! Such a good Samaritan

TikiThePug said:
Bro get to sleep! Such a good Samaritan
Click to expand...
Click to collapse
LOL! I would if I could, just can't sleep yet. Hopefully soon tho!

RichDoe252 said:
Unfortunately, nothing. Holding power for 20 seconds showed nothing, and like wise for volume up and power. Battery was fully charged too. Had it plugged in for most of today while I was trying to get fastboot to work.
Click to expand...
Click to collapse
Try a USB 2.0 port? Surprisingly this works for some phones even though it's compatible with 3.0.

reg66 said:
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
Click to expand...
Click to collapse
Well, It's been untouched for a day now, and it still will not react to input. No response from long hold on the power button. I will try again in the morning. Is it possible that I somehow wrote into the BIOS of the phone? Android does use a BIOS, right?

RichDoe252 said:
Well, It's been untouched for a day now, and it still will not react to input. No response from long hold on the power button. I will try again in the morning. Is it possible that I somehow wrote into the BIOS of the phone? Android does use a BIOS, right?
Click to expand...
Click to collapse
Android itself does not have a BIOS, since Android is an OS and BIOS is more similar to firmware. But yes, the phone does have firmware, and it could be that the mismatch in firmware versions (from which you tried to flash), has caused the bootloader to "not know what to do now" when trying to start the phone up.
One thing which comes with all phones with a Qualcomm chipset is something called Qualcomm Crashdump Mode. You can try to see if you can get your phone in EDL (emergency download) mode and restore the correct firmware in that way:
https://www.the***********.com/rog-phone-2-unbrick-guide (URL gets censored for some reason; it should be "the custom droid" with no spaces)
Also, if you continue to have driver issues with connecting the phone to your PC, are you able to test another PC or even a Mac if you have access to one? I find Windows can be a giant pain for getting ADB and fastboot to work properly at times.
Good luck and let us know how it goes.

reg66 said:
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
Click to expand...
Click to collapse
Ok, so here's where I am: I have left the phone unplugged for a long time now. Really had no effect. I just downloaded QPST and I can actually get my computer to see the phone. However, I am still not quite sure how to USE QPST and not make things worse. So this is my plan: I am going to look through the forums here for info on how to use QPST to get my phone working again. Not really sure what that will look like, but fastboot would be a good start. From there, it sounds like I have to get the original firmware back on it, and then go about the process of rooting once again.
Still leaves me with the issue that started me down the path of rooting this phone, but at least it will not longer be bricked.

RichDoe252 said:
Ok, so here's where I am: I have left the phone unplugged for a long time now. Really had no effect. I just downloaded QPST and I can actually get my computer to see the phone. However, I am still not quite sure how to USE QPST and not make things worse. So this is my plan: I am going to look through the forums here for info on how to use QPST to get my phone working again. Not really sure what that will look like, but fastboot would be a good start. From there, it sounds like I have to get the original firmware back on it, and then go about the process of rooting once again.
Still leaves me with the issue that started me down the path of rooting this phone, but at least it will not longer be bricked.
Click to expand...
Click to collapse
You may not HAVE to flash complete firmware, it is quite likely that the boot.img is causing the problem as you flashed an incompatible version. Below you'll flash the correct version which HOPEFULLY will fix your phone, provided you can get into fastboot mode now.
Haven't read back through all the thread so i can't recall all the details of where you're at. As far as i can tell you're still running WW 16.0622.1906.19-0, correct? Can you get the device to now boot into fastboot mode? (from a powered off state, press and hold vol up and power at the same time. You should then be presented with some options, DON'T select any option. With that menu screen open is fastboot mode.
1. Download and install ADB Fastboot from here to C: drive of your pc/laptop.
2. With your phone in fastboot mode (as detailed above) connect it to pc/laptop using the side port of the phone.
3. Navigate to C:\Program Files (x86)\Minimal ADB and Fastboot folder and double click the cmd-here.exe, this will open a cmd window.
4. Type 'fastboot devices' to check that it's recognised, there should be a serial/key shown after entering that cmd.
5. Provided the serial/key is shown in fastboot mode, download the following boot.img (which is for WW 1906.19) from here.
6. Copy that boot img to the same folder you have open for ADB (C:\Program Files (x86)\Minimal ADB and Fastboot)
7. In the cmd window type 'fastboot flash boot boot.img'.
Now, that boot img is the STOCK boot img for your rom version. Don't worry about rooting for now (if i recall correctly, your phone won't boot to system), let's just try to get the phone booting first. Providing there are no errors when flashing the boot img, on the phone fastboot menu, scroll through and choose 'restart'.
Let me know if the device boots to system now... Good luck
I'll pm you my email address so you'll be able to get hold of me if you get stuck at any stage...
EDIT: was forgetting you tried so many times to get into fastboot mode, without success.
---------- Post added at 08:59 PM ---------- Previous post was at 08:17 PM ----------
Dude, is your phone screen still black but switched on? When you tap the screen does it vibrate. I'm thinking you might already be in edl mode (which could be a good thing). Let us know
Check your pm's dude for further info. I can't post links to the site required so have sent via pm

TikiThePug said:
Android itself does not have a BIOS, since Android is an OS and BIOS is more similar to firmware. But yes, the phone does have firmware, and it could be that the mismatch in firmware versions (from which you tried to flash), has caused the bootloader to "not know what to do now" when trying to start the phone up.
One thing which comes with all phones with a Qualcomm chipset is something called Qualcomm Crashdump Mode. You can try to see if you can get your phone in EDL (emergency download) mode and restore the correct firmware in that way:
https://www.the***********.com/rog-phone-2-unbrick-guide (URL gets censored for some reason; it should be "the custom droid" with no spaces)
Also, if you continue to have driver issues with connecting the phone to your PC, are you able to test another PC or even a Mac if you have access to one? I find Windows can be a giant pain for getting ADB and fastboot to work properly at times.
Good luck and let us know how it goes.
Click to expand...
Click to collapse
Just dropping you a quick note to say thanks for thanks! LOL. Yeah, your post earlier seems like the best place to go. Have used Miflash Tool a few times on Xiaomi devices, it's pretty good and straight forward. Should be a LOT easier than using QPST and having to change EMMC to UFS.
Can't remember where i saw it now, but i'm sure i read that if the phone screen is black (but switched on) and vibrates, then it's likely to be in EDL mode already. Which will hopefully be good news for @RichDoe252. Before that (having never been in that situation), i wasn't aware that an all black screen could mean EDL mode is active. Fingers crossed for Rich it'll all work out just fine.
@RichDoe252 If all goes successfully using the QPST file download (and using the Miflash Tool the guide mentions in the pm i sent you) and flashing, DON'T ROOT JUST YET!!!! LOL. Let us know how it goes and then we can look into, and point you in the right direction, for getting you rooted and up to date on latest A9 or A10 whichever you'd prefer

Well I must say Rich, I'm surprised you haven't been back here yet to give any updates on progress!! Sent you a couple of emails through pm... Man, if it was my fairly expensive phone that was in the poo pan, I'd be all over trying to fix it lol

reg66 said:
Well I must say Rich, I'm surprised you haven't been back here yet to give any updates on progress!! Sent you a couple of emails through pm... Man, if it was my fairly expensive phone that was in the poo pan, I'd be all over trying to fix it lol
Click to expand...
Click to collapse
First off, you are a freaking saint. I really do appreciate all the help you have been offering up, and I am sorry I have not been very quick with a response. As my phone currently stands, I get 0% response from anything I do to it. No vibrate, nothing. No indication it even is plugged in. I had it connected to my PC with QPST installed, and it was able to pick up that the phone was there, and then immediately tried to download something to it. Not sure what, not sure why, but that kinda typifiies my interaction with this whole process so far. If you haven't guessed, I'm kinda in over my head.
Back to the problem: QPST started some opperation to download something to it. Wouldn't let me do anything else, said the phone was in "download mode". Either way it stopped at 30% and didn't progress for 30 minutes, so I tried to unplug it and plug it back in. Same interaction. Unable to do anything to the phone, no reaction from the phone what so ever. This was, by the way, plugged into the fastboot side port.
I saw that you PM'ed me, and now I can't find the email notification or the PMs on the site. Forgive me for being unfortunately new at this. I will get back to you bud, and thank you again.

Question Black screen and hard brick

Hello everyone today i flash an incompatible rom with twrp and my screen turn completely black After reboot twrp in recovery .
Do you have solution ?
Sorry for my bad English

Hi if you can open bootloader, flash stock rom

The easy solution is press power+volume down. Phone should boot into fastboot mode. Then flash fastboot ROM without relocking the bootloader.
The other way is taking phone to service center. They'll flash stock in edl mode.

I can't seem to put it in fastboot mode. but by pressing the 3 buttons or by changing the buttons I managed to put it in something else I think that at times I manage to put it on a fastboot but the screen always remains black impossible to know i have this message in device manager (Unknown usb devices request for descriptor) do you think it causes me to reinstall drivers what could be the cause? how to adjust as soon as i can connect it so l is not a Qualcomm USB hs 2008.

Miui 13 said:
I can't seem to put it in fastboot mode. but by pressing the 3 buttons or by changing the buttons I managed to put it in something else I think that at times I manage to put it on a fastboot but the screen always remains black impossible to know i have this message in device manager (Unknown usb devices request for descriptor) do you think it causes me to reinstall drivers what could be the cause? how to adjust as soon as i can connect it so l is not a Qualcomm USB hs 2008.
Click to expand...
Click to collapse
Doesn't EDL need authorized mi account these days? It'd better to visit service center because installing EDL driver & all the fuss will be useless

May be you can find some drivers which can recognise your phone to work with ADB in fastboot and flash a new ROM. If that doesn't work, then a service center is the next best option.

Miui 13 said:
I can't seem to put it in fastboot mode. but by pressing the 3 buttons or by changing the buttons I managed to put it in something else I think that at times I manage to put it on a fastboot but the screen always remains black impossible to know i have this message in device manager (Unknown usb devices request for descriptor) do you think it causes me to reinstall drivers what could be the cause? how to adjust as soon as i can connect it so l is not a Qualcomm USB hs 2008.
Click to expand...
Click to collapse
Sounds like your device boots into EDL mode, likely due to a corrupted bootloader from the incompatible firmware you've flashed. If you have the EDL firehose files for your device, you can use QFIL to flash a compatible ROM, alternatively try to EDL flash the boot partition with a working boot (that may get you from EDL to a soft brick with a working bootloader and Fastboot - from there you can try try and flash a working firmware).

RAMBO29 said:
May be you can find some drivers which can recognise your phone to work with ADB in fastboot and flash a new ROM. If that doesn't work, then a service center is the next best option.
Click to expand...
Click to collapse
I unfortunately tried to install all the drivers but nothing has worked difficult to know if a fastboot is started it's a hassle when the screen is completely black even with the task manager open I don't I did not succeed finally I ended up paying someone who had me unlock my phone it cost me 29 € my phone is now unlocked which I can advise on the other hand for those who would like to install roms or root their phone is good it is to wait until no auth file is leaked

Andrologic said:
Sounds like your device boots into EDL mode, likely due to a corrupted bootloader from the incompatible firmware you've flashed. If you have the EDL firehose files for your device, you can use QFIL to flash a compatible ROM, alternatively try to EDL flash the boot partition with a working boot (that may get you from EDL to a soft brick with a working bootloader and Fastboot - from there you can try try and flash a working firmware).
Click to expand...
Click to collapse
I see it's super interesting as information I did not know that we could flash only a partition with QFIL.
Unfortunately I could not find the firehose files for the phone as the phone is probably very recent.
I had to pay someone to unlock my phone with an edl account of course .
My work now

Was the unlocking done in person or online? Anyways glad to see it's sorted out.
Miui 13 said:
I unfortunately tried to install all the drivers but nothing has worked difficult to know if a fastboot is started it's a hassle when the screen is completely black even with the task manager open I don't I did not succeed finally I ended up paying someone who had me unlock my phone it cost me 29 € my phone is now unlocked which I can advise on the other hand for those who would like to install roms or root their phone is good it is to wait until no auth file is leaked
Click to expand...
Click to collapse

RAMBO29 said:
Was the unlocking done in person or online? Anyways glad to see it's sorted out.
Click to expand...
Click to collapse
yes it was done online I unlocked it with TeamViewer thanks to an edl account