Develop Bugs

Bricked Lenovo Vibe shot z90-7, no edl, fastboot twrp and locked bootloader.

I got a lenovo vibe shot z90-7 which was using Android 5.1. I found an upgrade rom on needrom to 6.0. I flashed it using qfil (qualcomm flashing tool) and it went all right, all functional. But I also wanted to unlock the bootloader and install a twrp (I found a procedure and twrp image on a russian forum). I followed the steps but it didn't work, I still wasn't able to unlock the bootloader. Thus, I was not able to enter fastboot anymore: from adb I was typing "adb reboot bootloader" and the device would reboot normally, not in fastboot mode. I decided to change to another rom (from needrom) which was claiming would allow you to unlock the bootloader. So, without hesitation I flashed it in qfil (edl mode) and it went all right, but I got stuck in boot loop. After the splash screen, the device shuts the screen off and does a long vibration and stays like that. If I connect it via usb to my pc I get a some "need to format drive" alerts, and in qfil I see "Qualcomm HS-USB Diagnostic 9006 (COM5)". If then I try to flash the rom I get this log:
Code:
Start Download
COM Port number:5
Switch To EDL
Download Fail:System.Exception: Failed to Switch to Emergency Download mode
at QC.QMSLPhone.Phone.QPHONEMS_SwitchToEDL()
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
Download Fail:Switch To EDL FailSystem.Exception: FireHose Fail
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
at QFIL.Tech.DownloadTech.SwitchToEDL()
Finish Download
It's seems like I need to get in Edl mode first, but I cannot use adb and pushing vol+ and plug the usb at the same time (or a little bit first one or the other, I tried all) does't do anything but booting the device normally.
I also tried getting in fastboot mode (keep vol- and power button) but it doesn't work.
I read of an "engineering mode" by keeping vol- on boot. It does something, the screen becomes black, but it's on. On my pc the adb driver comes in in the popup, like if I'm in fastboot or adb, but on "fastboot devices" I can't see anything, while on "adb devices" I see a device, which is "? unauthorized". Strange to me, I can't do much with it since it's unauthorized and the screen on the device remains black. And after a few seconds (about 30) it gets back to long vibration and screen off state.
I can get into the stock recovery by holding vol+, vol- and power, but it's a very poor recovery. All I can do is reboot, shut down, wipe data and update. I tried to use "update" and put a zip file of an official rom downloaded into the sd card and named "update.zip" as suggested by the recovery, but I get an error (with no technical information about what kind of error), so no luck with that either.
I tried to force the qualcomm driver from "Qualcomm HS-USB Diagnostic 9006 (COM5)" to "Qualcomm HS-USB QDLoader 9008 (COM5)", then tried to flash using qfil, but I still get an error, even if this time is different:
Code:
COM Port number:5
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
I finally tried to download the rom in .qsb format and get in engineering mode again, but the screen remains black and no sign of flashing possibilities.
Please help, I tried everything it came to my mind.
I also tried with miflash, but still got errors...
Thank you

Hello, did you solve the problem? i have the same as you....
regards

Hi guys.
I had the similar problem few moths ago. I tried to remember what i've done to fix it, but I don't remember all things, I hope this steps helps to find the solution.
Check this:
-Use Windows 7 (I tried with Windows 10 and always appears some errors)
-Use original miniUSB cable or good quality cables
-Install Lenovo Usb drivers
Turn ON phone and press Vol+ and Vol-, hold 3 seconds
If you cant enter Recovery mode (because is corrupt or bricked), phone will vibrate for 1-2 seconds and screen keep black. Now connect USB cable (check drivers, also if Qualcomm HS-USB QDLoader 9008 was installed)
Once you done, use QSFL or MiFlash (but not 2016 version!, never works to flash)
NOTE: I had some problems with my desktop computer with Windows 7 but no problem in laptop. So check it in more than one...
Good luck.

How I fixed this
I fixed it installing a update.zip via recovery (vol + plus vol - plus power) I found here
http://forum.xda-developers.com/android/development/vibe-shot-6-0-update-root-xposed-t3409989
This not fixed the phone , but allowed me to unlock bootloader entering in fastboot mode (vol + plus vol - plus plug usb) using this
http://lenovo-forums.ru/topic/18149-lenovo-vibe-shot-разблокировка-bootloader/
Then I was allowed to install TWRP as explained here
http://lenovo-forums.ru/topic/18150-lenovo-vibe-shot-расширенное-рекавери-twrp-by-sevenmaxs/
Then I was able to go to TWRP terminal and type
reboot edl
Phone went into downloader mode and I was able to install this rom with QFIL
http://www.needrom.com/download/lenovo-vibe-shot-android-6-0-1-1625-encn-unlocked/
and I restored NVRAM with a qcn file I found in Ebay after putting the phone in diagnostics mode. Then I changed imeid, meid and esn to the original ones I found in the box. Phone fixed.
Just note that this file was for a Z90-7 rom and it will not work with a Z40a20 rom.
Hope this helps someone.

francesco9696 said:
I got a lenovo vibe shot z90-7 which was using Android 5.1. I found an upgrade rom on needrom to 6.0. I flashed it using qfil (qualcomm flashing tool) and it went all right, all functional. But I also wanted to unlock the bootloader and install a twrp (I found a procedure and twrp image on a russian forum). I followed the steps but it didn't work, I still wasn't able to unlock the bootloader. Thus, I was not able to enter fastboot anymore: from adb I was typing "adb reboot bootloader" and the device would reboot normally, not in fastboot mode. I decided to change to another rom (from needrom) which was claiming would allow you to unlock the bootloader. So, without hesitation I flashed it in qfil (edl mode) and it went all right, but I got stuck in boot loop. After the splash screen, the device shuts the screen off and does a long vibration and stays like that. If I connect it via usb to my pc I get a some "need to format drive" alerts, and in qfil I see "Qualcomm HS-USB Diagnostic 9006 (COM5)". If then I try to flash the rom I get this log:
Code:
Start Download
COM Port number:5
Switch To EDL
Download Fail:System.Exception: Failed to Switch to Emergency Download mode
at QC.QMSLPhone.Phone.QPHONEMS_SwitchToEDL()
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
Download Fail:Switch To EDL FailSystem.Exception: FireHose Fail
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
at QFIL.Tech.DownloadTech.SwitchToEDL()
Finish Download
It's seems like I need to get in Edl mode first, but I cannot use adb and pushing vol+ and plug the usb at the same time (or a little bit first one or the other, I tried all) does't do anything but booting the device normally.
I also tried getting in fastboot mode (keep vol- and power button) but it doesn't work.
I read of an "engineering mode" by keeping vol- on boot. It does something, the screen becomes black, but it's on. On my pc the adb driver comes in in the popup, like if I'm in fastboot or adb, but on "fastboot devices" I can't see anything, while on "adb devices" I see a device, which is "? unauthorized". Strange to me, I can't do much with it since it's unauthorized and the screen on the device remains black. And after a few seconds (about 30) it gets back to long vibration and screen off state.
I can get into the stock recovery by holding vol+, vol- and power, but it's a very poor recovery. All I can do is reboot, shut down, wipe data and update. I tried to use "update" and put a zip file of an official rom downloaded into the sd card and named "update.zip" as suggested by the recovery, but I get an error (with no technical information about what kind of error), so no luck with that either.
I tried to force the qualcomm driver from "Qualcomm HS-USB Diagnostic 9006 (COM5)" to "Qualcomm HS-USB QDLoader 9008 (COM5)", then tried to flash using qfil, but I still get an error, even if this time is different:
Code:
COM Port number:5
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
I finally tried to download the rom in .qsb format and get in engineering mode again, but the screen remains black and no sign of flashing possibilities.
Please help, I tried everything it came to my mind.
I also tried with miflash, but still got errors...
Thank you
Click to expand...
Click to collapse
Hi, did you slove the problem? Same situation with me. But I managed to install twrp ( Chinese) but I can't install any rom .. After successful flashing it reboot with lenovo logo, then long vibrates.. When I connect it to PC. It show number of partition and need to format popup.. I tried different ROMs.. All via twrp. I don't use miflash or qfil.. If you have solved it please share how. Thanks.

i know how to enter in edl mode in z90-7 or z90a40
Hello
This is nisar I successfully entered in edl mode and flashed rom to know the procedure pm me on +919743392420 WhatsApp

Bricked Vibe Shot - multiple partitions in device manager - no edl
having read all the above I'd like to share small info once again, it is all about correct qualcomm drivers, you can get them from androidurdu.net, do not search on the site but click on mobile drivers then scroll down and download qualcomm usb drivers.zip . unpack and use "checked" folder within the zip, they are signed and work on any windows including 10th. You see, your brick might be having an edl times, but PC doesn't know without proper drivers installed. You might want to remove all earlier/bad driver versions, for example try sigverif command or just install below qualcomm drivers and try away.
1. connect phone with good usb cable, 2. press power button till it shuts, then release power button and press volume up and down same time and phone will enter edl mode itself almost instantly, if you had twrp installed then it'll enter there, if so run from terminal "reboot edl"; keep device manager open and comm tree will appear along.
other way is via adb reboot edl command, if fastboot doesn't work, or fastboot reboot-edl
on miflash when refreshed you see the short port name and the number like com4 or 3. now it's time to flash, but the last proven flash I did with QiFL, Miflash works as fine.
i used latest international marshmallow version. after first boot, within dev mode unlocked oem + enabled adb and connected to PC with phone turned on in order to accept handshake prompt.
unlocking bootloader is easy via adb command: adb reboot bootloader, then: adb bootloader unlock-go .
all files are available online via some russian speaking forum, you just need to install twrp, then place su.zip onto phone (I copied on internal memory), boot into twrp and flash; if clean - no errors flash then you got neatly rooted marshmallow phone.
my struggle with bricked vibe shot was worth it. earlier I noticed cpu was running high, all cores all the time. also many google apps which I wanted to eliminate for draining the battery and uploading stuff all the time.
right after flashing su.zip boot into phone and install kernel adiutor from play store, then take control of how your 8 cores behave. I discovered the minimums were set at 800+Mhz so I dropped them to 200, then below within cpu section enabled all "disabled" options for boost + enabled "ondemand" + plus few more. You got to understand the process and enjoy tuning your phone your way.
I've charged my vibe shot 3 hours ago and was randomly chatting on whatsap until now and I have 73% battery. Day before yesterday before the bricking, full charge would not last more than 3 hours, incredible battery performance thanks to "adiutor" .
One more important thing, use correct rom version for your phone because of advanced camera and specific drivers camera won't work well.
Names of files used to make my phone a super hero:
1. adb-setup-1.4.2.exe
2. Miflash_140509.exe
3. Qualcomm_USB_Drivers.7z via androidurdu.net
4. TWRP-3.0.2.0_Z90a40_by_SevenMaxs.rar - has .bat files inside; enter bootloader mode and shoot
5. UPDATE-SuperSU-v2.76-SYSTEMMODE-PRO.zip (I pay for my apps including supersu pro)
6. Z90a40_Android-L_unlock_7M.7z , or use command line via adb shell.
7. Z90a40_S363_160625_ROW_QPST.7z - latest intl Mashmallow Os , to make it more perfect download marshmallow google dialer - patched.apk.
8. QPST / QIFL , used to flash the above rom
I'm not a pro so small mistakes are acceptable, I hope.
ciao.

francesco9696 said:
I got a lenovo vibe shot z90-7 which was using Android 5.1. I found an upgrade rom on needrom to 6.0. I flashed it using qfil (qualcomm flashing tool) and it went all right, all functional. But I also wanted to unlock the bootloader and install a twrp (I found a procedure and twrp image on a russian forum). I followed the steps but it didn't work, I still wasn't able to unlock the bootloader. Thus, I was not able to enter fastboot anymore: from adb I was typing "adb reboot bootloader" and the device would reboot normally, not in fastboot mode. I decided to change to another rom (from needrom) which was claiming would allow you to unlock the bootloader. So, without hesitation I flashed it in qfil (edl mode) and it went all right, but I got stuck in boot loop. After the splash screen, the device shuts the screen off and does a long vibration and stays like that. If I connect it via usb to my pc I get a some "need to format drive" alerts, and in qfil I see "Qualcomm HS-USB Diagnostic 9006 (COM5)". If then I try to flash the rom I get this log:
Code:
Start Download
COM Port number:5
Switch To EDL
Download Fail:System.Exception: Failed to Switch to Emergency Download mode
at QC.QMSLPhone.Phone.QPHONEMS_SwitchToEDL()
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
Download Fail:Switch To EDL FailSystem.Exception: FireHose Fail
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
at QFIL.Tech.DownloadTech.SwitchToEDL()
Finish Download
It's seems like I need to get in Edl mode first, but I cannot use adb and pushing vol+ and plug the usb at the same time (or a little bit first one or the other, I tried all) does't do anything but booting the device normally.
I also tried getting in fastboot mode (keep vol- and power button) but it doesn't work.
I read of an "engineering mode" by keeping vol- on boot. It does something, the screen becomes black, but it's on. On my pc the adb driver comes in in the popup, like if I'm in fastboot or adb, but on "fastboot devices" I can't see anything, while on "adb devices" I see a device, which is "? unauthorized". Strange to me, I can't do much with it since it's unauthorized and the screen on the device remains black. And after a few seconds (about 30) it gets back to long vibration and screen off state.
I can get into the stock recovery by holding vol+, vol- and power, but it's a very poor recovery. All I can do is reboot, shut down, wipe data and update. I tried to use "update" and put a zip file of an official rom downloaded into the sd card and named "update.zip" as suggested by the recovery, but I get an error (with no technical information about what kind of error), so no luck with that either.
I tried to force the qualcomm driver from "Qualcomm HS-USB Diagnostic 9006 (COM5)" to "Qualcomm HS-USB QDLoader 9008 (COM5)", then tried to flash using qfil, but I still get an error, even if this time is different:
Code:
COM Port number:5
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
I finally tried to download the rom in .qsb format and get in engineering mode again, but the screen remains black and no sign of flashing possibilities.
Please help, I tried everything it came to my mind.
I also tried with miflash, but still got errors...
Thank you
Click to expand...
Click to collapse
have you try
adb reboot edl

Hey, I have the same problem as you, trying to do the step you did, but I get stucked at the first step,
I cannot find the file UPDATE.ZIP in the page from your link....
Could you help?
Thanks
josepgb said:
I fixed it installing a update.zip via recovery (vol + plus vol - plus power) I found here
http://forum.xda-developers.com/android/development/vibe-shot-6-0-update-root-xposed-t3409989
This not fixed the phone , but allowed me to unlock bootloader entering in fastboot mode (vol + plus vol - plus plug usb) using this
http://lenovo-forums.ru/topic/18149-lenovo-vibe-shot-разблокировка-bootloader/
Then I was allowed to install TWRP as explained here
http://lenovo-forums.ru/topic/18150-lenovo-vibe-shot-расширенное-рекавери-twrp-by-sevenmaxs/
Then I was able to go to TWRP terminal and type
reboot edl
Phone went into downloader mode and I was able to install this rom with QFIL
http://www.needrom.com/download/lenovo-vibe-shot-android-6-0-1-1625-encn-unlocked/
and I restored NVRAM with a qcn file I found in Ebay after putting the phone in diagnostics mode. Then I changed imeid, meid and esn to the original ones I found in the box. Phone fixed.
Just note that this file was for a Z90-7 rom and it will not work with a Z40a20 rom.
Hope this helps someone.
Click to expand...
Click to collapse

Sorry if it's reviving the thread but i found a way to unbrick the device from this state. Not sure if will work for all models because this one was a really weird one (almost all button combinations were different than any described on the internet). So my phone was from China (Z90-7 - later it showed that it's a Z90A40 and I had to flash that firmware) with a international chinese ROM and it god badly bricked (no edl, no lenovo recovery, locked bootloader etc. etc.). Now, when holding [vol+]+[vol-]+[pwr] (usually recovery mode according to the internet) it went into the Qualcomm 9006 diagnostics mode that shows a million partitions. There was no way i could get it into edl mode but there was the so called factory mode that is accessed by holding [vol-] and plugging in the usb before it vibrates. Through this I managed to flash firmware in .qsb format from a SD card and successfully unbricked the phone that I almost threw into the bin.
1. Check if your phone has "factory mode" [vol-]+[pwr] then release [pwr] or hold [vol-] while inserting usb cable.
- make sure to try different combinations, the button combinations on my phone were much different than what I mostly found on the internet
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Download Vibe Shot firmware in .qsb format (Google it, the phone will warn you if it's not the right one (A40 or -7))
3. Copy the .qsb file into SD:/sdfuse
4. Insert the SD card into the phone (maybe a restart will be needed for it to be detected, you should see a message saying "DEV: External storage" when you select sd flash)
5. Select "SD update" and follow the instructions.
I hope this helps someone who can access the factory mode. This is so easy and I couldn't believe that there is so little information on flashing it this way.
Good luck.

i wonder how do you change HS-USB Qualcomm 9006 become HS-USB Qualcomm 9008?

Cant Unrbick Lenovo Vibe Shot Z90A40

Hi
I have tried a lot to unbrick my Lenovo Vibe Shot. Now I am helpless and looking for some workable solution:
I used Lenovo Smart Assistant to download a proper firmware so it turned out it is:
z90a40_USR_S363_1606250500_Q202533.1_ROW.zip
I tried to use Lenovo Smart drive assistant to update ROM or Device Rescue, but both wont detect phone
The phone default Lenovo recovery can be loaded by pressing VOL+, VOL- and power button, and then releasing power button
when logo appears. I used an Update.zip in 8GB mem card and used the option: ‘install update package’ then it complete the process 100% I was happy that I was going to get my phone unbrick
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
but when it asked for reboot and I rebooted it, it vibrated
2 times, first it vibrated, and showed logo of Lenovo for 1 second then it vibrated long like 2/3 seconds and turned off. I repeated many times these steps but still it behaves same.
Another thing is after brick, it showed this in My Computer:
And with each new drive letter it shows following. I tried to format but it then says Write protected error.
Then tried 3 or 4 methods from following
https://boycracked.com/2016/02/07/stock-rom-frimware-lenovo-vibe-shot-z90/
I was just simply not able to use Qualcomm Lenovo HS-USB QDLoader 9008
as on all my PCs it is detecting as some Diagnostic 9006 version instead of above.
Tried on different PCs and ROMs/Firmwares titling Lenovo Vibe Shot, Either the following error or Delete drive layout comes.
Then I followed next method for QFIL but still it cannot download it.
Please help me how can get things right, I have tried on 3 PCs (2 of them were 32 bit windows, and a Win 10 laptop)
Still no luck

I have the same problem. tried everything, QFIL MiFlash Recovery. no luck. Partition tool does not delete the partition. tried deleting all of them and creating a new 1. nothing happened. the pc no longer detected the multiple write protected drives but the partition tool still does and when I plugged it in a different PC, the multiple write protected drives appeared again. Hope we find a solution for this. I haven't been sleeping that much for the past week because of this.

babui21 said:
I have the same problem. tried everything, QFIL MiFlash Recovery. no luck. Partition tool does not delete the partition. tried deleting all of them and creating a new 1. nothing happened. the pc no longer detected the multiple write protected drives but the partition tool still does and when I plugged it in a different PC, the multiple write protected drives appeared again. Hope we find a solution for this. I haven't been sleeping that much for the past week because of this.
Click to expand...
Click to collapse
I figured it out from my semi-sleepless nights. But b4 the solution that worked for me, I had to
learn a lot out of my desperation to finally get it worked on the day I decided to hand over to
some technical guy from local market
The full comment form Francisco Kadzi helped me finally do it from following youtube link:
https://www.youtube.com/watch?v=SmMg00Wqabc&t=1s
Besides I had to take care of many things. First here are the things I was doing wrong:
- Not taking care of a heavily charged phone, I would try to unbrick after just 1 hour
or less charging from a total uncharged device.
- I was going to a backward step whenever I failed on something (Reboot in
fastboot mode, trying with QFIL etc.). Whereas many different forums (mainly XDA),
people were saying to try again and again.
- I was using improper ROMS or flash files my device was: Z90a40_USR_S363_1606250500_Q202533.1_ROW
- When I would see 9006 mode again I would be disappointed and would try different solution.
The correct thing to try was uninstall this driver and then connect the device again with
PC in fastboot mode .
Then I used Lenovo Smart Assistant and got this proper file:
Z90a40_USR_S363_1606250500_Q202533.1_ROW
OK read my first post to know what problems I faced, but at the end the multiple
partitions were not really the problem. The actual problem was getting 9008 mode
in Device Manager of my Windows 7. I always got it as Diagnostics 9006 mode. One
I started getting 9008, things went in my way gradually. So the person posting on
above comment from youtube link helped me
Am a happy fellow at the moment and will help anyone with same problem if needed
My email id is: usman400 on G Mail

usman400 said:
I figured it out from my semi-sleepless nights. But b4 the solution that worked for me, I had to
learn a lot out of my desperation to finally get it worked on the day I decided to hand over to
some technical guy from local market
The full comment form Francisco Kadzi helped me finally do it from following youtube link:
https://www.youtube.com/watch?v=SmMg00Wqabc&t=1s
Besides I had to take care of many things. First here are the things I was doing wrong:
- Not taking care of a heavily charged phone, I would try to unbrick after just 1 hour
or less charging from a total uncharged device.
- I was going to a backward step whenever I failed on something (Reboot in
fastboot mode, trying with QFIL etc.). Whereas many different forums (mainly XDA),
people were saying to try again and again.
- I was using improper ROMS or flash files my device was: Z90a40_USR_S363_1606250500_Q202533.1_ROW
- When I would see 9006 mode again I would be disappointed and would try different solution.
The correct thing to try was uninstall this driver and then connect the device again with
PC in fastboot mode .
Then I used Lenovo Smart Assistant and got this proper file:
Z90a40_USR_S363_1606250500_Q202533.1_ROW
OK read my first post to know what problems I faced, but at the end the multiple
partitions were not really the problem. The actual problem was getting 9008 mode
in Device Manager of my Windows 7. I always got it as Diagnostics 9006 mode. One
I started getting 9008, things went in my way gradually. So the person posting on
above comment from youtube link helped me
Am a happy fellow at the moment and will help anyone with same problem if needed
My email id is: usman400 on G Mail
Click to expand...
Click to collapse
I had problem like you, and i couldnt solve it so i sent it to repair shop and waiting now to hear from them.
I managed to get 9008 port, tryed to downgrade, upgrade, flash would complete, i tried literaly all row and china rom, no way to boot up sucessfully.
I even flashed twrp and tryed cm rom and mokee, i could boot after lenovo sign.
But i have same situation like you, many partitions and thats all. I think problem is read only partitions...
Can you tell me what drivers did you use?

I was able to fix exactly same problem this morning an hour before important meeting. All contacts and location puns were on gdrive and hadn't slept full night. You need to download correct qualcom drivers. Enter in Google: android qualcom urdu checked. Inside the zip unpack "checked" folder, right click and select install all infs. Run adb reboot bootloader while phone attempts to boot, when command succeeds run adb reboot edl, or fastboot reboot-edl whichever works. Keep miflash open and refresh. Then you see a short Comm port name. Now shoot flash with any rom that you have. If you do Chinese version then SNAPit lags badly, install correct version.
To sum up, focus on implementing correct qualcom drivers. In windows 10 run command testsign off and reboot in advance.

Actually I bricked my phone a whole lot of times even after my post thats because once I knew that it is just soft bricked and I can get it back somehow, I got the confidence and tried advanced things that bricked my phone again and again
And it was only the recent time (around 3 weeks ago), that I figured the 100% working 9008 method for my phone
actually u have to drain the battery completely out then it will get 9008 mode to do it u shall try turning your phone on again and again so that battery goes off
For example: Press Power button for a few seconds to turn it on.
Or press 3 buttons at same time (VOL+, VOL- and Power), then release only Power button when you get vibration. Then after 2 seconds release both VOL buttons as well (this is for going to recovery mode)
This way you can drain all battery of phone, and you will know when the battery is all gone when you will press the Power button and phone will not show any LED light or screen light, it will just vibrate and will be off
Now you connect ur phone to PC in following way:
If at bricking you you were on Lollipop (Android 5): Pressing VOL+ key and plug the USB cable in WITHOUT PRESSING POWER BUTTON ! 9008 will open use Qfil to flash the ROM u want
OR If at bricking you were on Marshmallow (Android 6): Plug the USB cable in phone, then connect cable to PC and exactly at the same time press power button (some times u dont need to press power button so try with both options). Then if you see 9008 mode in Qfil, then immediately press the Download button in Qfil
If you see Qfil error then repeat the above process to get 9008 mode and use miflash instead of Qfil miflash worked for me better than Qfil from such situation as Qfil often gives error in between
And when you get the flashing 100% then phone will either auto restart or you have to restart it manually Using Qfil it shows u message when it is restarting the phone, and I think using miflash it just says process 100% complete then u have to restart phone yourself
Remember at this point (after restart) connect your phone charger properly in a electricity power socket instead of PC as the battery was already drained so you need to charge the device while it shows the long booting process due to new ROM flashed.
Good luck,

I had the same problem from two days my phone is bricked and when i connect it to my pc too many partitions appears and when flashing by miflash it says (incorrect function) and i tried too many methods without any good result
But I finally unbricked my vibe shot successfully
At first i downloaded Qualcomm Lenovo HS-USB QDLoader 9008 driver definition, i searched for it by google until i get a zip file with the driver definition. i installed it manually from device manager on computer when my phone was connected to pc.
After that i downloaded an official z90a40_s240 for flashing via Qfil.
Steps:
1- disconnect your phone
2- go to recovery mode by ( holding power button with volume+ and volume- at the same time) until booting to recovery mode.
3-In recovery mode chose English then power off
4- open Qfil and get it ready to flash the official firmware
5-connect the USB to your pc then keep holding volume up and connect your phone to USB.
6- your phone screen should be turned off, also the LED light and you should see 9008 mode
7- click to download button and the flashing will start.
And congratulations your phone unbricked successfully ?

I have facing same problem on my phone. Could you help to show me hơ to unbricked it . Thanks you so much.

How to enter EDL mode on Mi5s Plus when cannot switch it off

Hi guys,
Looks like I have a big problem now on my Mi5s Plus. After flashing a chineese developer ROM 6.12.29 in EDL mode I got permanent MI.COM icon on the screen, so device is bricked, power button only restarts the icon. The worst thing is I cannot enter EDL mode anymore since I cannot switch off the device. I have deep flash cable, but it doesn't help, because the phone has to be turned off before release a button. The bootloader is locked, I have permission to unlock, but it doesn't work, saying account on the device is different to account I logged in.
Does anybody know how can I enter again EDL mode in this situation? How can I proceed to get the device unbricked? Please suggest.
I have tried chinees MiFlash to flash the ROM, but also without result (stops in the beginning).
Many thanks in advance.

USB cable mod, search for "USB cable EDL mode"

zebster said:
USB cable mod, search for "USB cable EDL mode"
Click to expand...
Click to collapse
I could find only the topic with modified fastboot, tried, no effect, restart to the same logo.
Could you please give me a link of the post which you think will help me.
Many thanks!

http://en.miui.com/thread-324300-1-1.html
As simple as that.
You have to join the two wires and then connect it to the usb port on PC.
To flash you have to separate them as a normal cable.

zebster said:
http://en.miui.com/thread-324300-1-1.html
As simple as that.
You have to join the two wires and then connect it to the usb port on PC.
To flash you have to separate them as a normal cable.
Click to expand...
Click to collapse
It doesn't work in my situation, I've been trying already since 4 days, because to use this method and cable the phone has to be switched off, and this is not possible, because it always restarts when I press power button. I tried to switch it off in fastboot mode, leaving it in fastboot mode not connected to anything, then after approx. one minute the screen is fully off, but when I connect deep flash cable with joined wires and release the wires, it is just switching on to the same MI.COM logo and then the battery charging screen...((( The cable was working when device was alive, so contacts are correct (black and green)...
I need either the way how to bypass bootloader locking in fastboot, or another way how to reach EDL mode.
I really thought it is always possible to go into EDL with deep flash cable, but looks like it is not... Maybe I use the wrong moment to release the button. I insert cable into PC and wait 3 seconds, then release the button... Tried many times and different moments. But when device was alive it was working immediately and always...(((
Are there other ideas, guys?
Please help!!!

DR2010 said:
It doesn't work in my situation, I've been trying already since 4 days, because to use this method and cable the phone has to be switched off, and this is not possible, because it always restarts when I press power button. I tried to switch it off in fastboot mode, leaving it in fastboot mode not connected to anything, then after approx. one minute the screen is fully off, but when I connect deep flash cable with joined wires and release the wires, it is just switching on to the same MI.COM logo and then the battery charging screen...((( The cable was working when device was alive, so contacts are correct (black and green)...
I need either the way how to bypass bootloader locking in fastboot, or another way how to reach EDL mode.
I really thought it is always possible to go into EDL with deep flash cable, but looks like it is not... Maybe I use the wrong moment to release the button. I insert cable into PC and wait 3 seconds, then release the button... Tried many times and different moments. But when device was alive it was working immediately and always...(((
Are there other ideas, guys?
Please help!!!
Click to expand...
Click to collapse
No, you don't have to have the phone swithed off.
Connect the cable with the mod and then press the power button until it shutsdown.
When it restarts it will be already on EDL mode.
I had exactly the same problem as you.
---------- Post added at 03:52 PM ---------- Previous post was at 03:48 PM ----------
With the phone as you have do this:
- use the modded usb cable and connect the phone to PC
- press power button until the phone restarts
- disconnect usb from PC
- use normal USB cable to connect phone to PC
Now you should see the "Qualcomm HS -USB QDLoader 9008" device on you PC device manager, EDL mode on the phone with a black screen

zebster said:
No, you don't have to have the phone swithed off.
Connect the cable with the mod and then press the power button until it shutsdown.
When it restarts it will be already on EDL mode.
I had exactly the same problem as you.
---------- Post added at 03:52 PM ---------- Previous post was at 03:48 PM ----------
With the phone as you have do this:
- use the modded usb cable and connect the phone to PC
- press power button until the phone restarts
- disconnect usb from PC
- use normal USB cable to connect phone to PC
Now you should see the "Qualcomm HS -USB QDLoader 9008" device on you PC device manager, EDL mode on the phone with a black screen
Click to expand...
Click to collapse
Unfortunately it doesn't work, as I told above(((
When I press the power button and do not release it, the phone cyclically restarts independently if it is connected to something or not and with mod cable or not...
When did you release a power button?

1. Have you tried to press both power and volume up to enter recovery? If you can, select download to flash with MIflash.
2. Can you enter fastboot mode? I so:
https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718

zebster said:
1. Have you tried to press both power and volume up to enter recovery? If you can, select download to flash with MIflash.
2. Can you enter fastboot mode? I so:
https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
Click to expand...
Click to collapse
Dear zebster, many thanks for your kind efforts to help me.
Yes, I can enter both - standard recovery and fastboot. In standard recovery there is no any selection possible. MiFlash doesn't see anything in this mode as expected.
There is only animated (connected/disconnected) cable and adb interface available on the phone when I connect in this mode to PC, but chineese Mi PC Suite can see the phone, starts flashing even, but hangs on 5% approximately, saying there was an error, please try again (of course doesn't help).
Also I have tried before modified fastboot utility from the link to enter EDL, only restarts the phone, like I pressed the power button, and I get again lovely MI.COM logo...(((

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if you can see this option you should be able to flash thru miflash

zebster said:
if you can see this option you should be able to flash thru miflash
Click to expand...
Click to collapse
no, I have just standard recovery from official ROM (but God knows from which one now...): on the black background screen the white edges of smartphone are pictured and the USB cable below. When I connect device to PC cable becomes connected, when disconnect - disconnected. That's all. You have different recovery...

You have this:
My advice is to download the original rom and flash it thru fastboot:
http://en.miui.com/download-314.html

zebster said:
You have this:
My advice is to download the original rom and flash it thru fastboot:
http://en.miui.com/download-314.html
Click to expand...
Click to collapse
As far as I know it would work if the bootloader would be unlocked, but it is locked!
And the unlocking software says that account is different (I even have official permission to unlock the bootloader). So, I got stucked in a circle((((
I even tried it yesterday, but MiFlash itself in this case crashes...

DR2010 said:
As far as I know it would work if the bootloader would be unlocked, but it is locked!
And the unlocking software says that account is different (I even have official permission to unlock the bootloader). So, I got stucked in a circle((((
I even tried it yesterday, but MiFlash itself in this case crashes...
Click to expand...
Click to collapse
I've flashed mine with bootloader locked in EDL mode.
If you can use Miflash with bootloader you can flash it even with bootloader locked.
Download the oficial ROM and flash thru MIflash.
To unlock you may need to flash the China Developer ROM.

zebster said:
I've flashed mine with bootloader locked in EDL mode.
If you can use Miflash with bootloader you can flash it even with bootloader locked.
Download the oficial ROM and flash thru MIflash.
To unlock you may need to flash the China Developer ROM.
Click to expand...
Click to collapse
Thanks, but again doesn't work on my device...
As I expected, MiFlash 2016.12.14.1(Release) in fastboot mode says that "Partion flashing is not allowed" and finishes with error...
The same as I do it manually via fastboot command interface...(((
Which version of MiFlash did you use? Where can I download it?

Use miflash 2015.10.28.0
Was the version that worked for me.
You can also try to enter EDL on fastboot using:
fastboot oem edl

zebster said:
Use miflash 2015.10.28.0
Was the version that worked for me.
You can also try to enter EDL on fastboot using:
fastboot oem edl
Click to expand...
Click to collapse
fastboot oem edl needs the bootloader to be unlocked.
do you have a link to download miflash 2015.10.28.0?
thanks!

I had the same problem with my Mi 5s.
This is what I eventually did to solve it (from memory - Google a bit for detailed instructions):
Download the Chinese version of Mi PC Suite (It has more options than the english version)
You can then recover from bootloop, by using it's recovery;
- Start MiPCSuite
- Boot phone to recovery (volume up + power)
- Select "Connect with MiAssistant" (bottom option)
- Phone should be detected, and a popup will show on PC with recovery options.
I believe it could download the latest version for you, or you can select a downloaded .zip file to flash.
It will have to be the same type that was previously installed (during the failed flash). So you can not go from Dev to Stable, or from CN to Global.
Go here for (Mi 5s) roms: http://en.miui.com/download-314.html#456
On the PC it immediately said flash failed, but the phone re-flashed the ROM anyway.
Hope this helps some...
P.S. Used my old phone with Google Translate App to read Chinese (Instant translation with the camera)
P.P.S. Other options won't work, because Xiaomi locked out the EDL in Chinese Developer versions. Even with the Deep Flash cable.
I'm now running Chinese Dev. version, and can not enter EDL anymore. I'll have to wait for bootloader unlock before I can flash again...
P.P.P.S. It seems I was wrong about not being able to switch: just flashed Global ROM 8.0.3.0 (From Chinese Dev. ROM 7.1.20) using the same method.
Again on the PC it said flashing failed (immediately) and stays at 0%, but the phone shows it's updating...
After flashing had to clear/reset data (again from MiPCSuite - Middle option in popup - Red button in 2nd popup), otherwise all apps keep crashing.
Because I'm back to Global ROM now, I can also use my Deep Flash cable again.

Dear Zappo, many thanks for your reply! I still fighting with the problem... already tried to disconnect the battery, not going to EDL as well.
I think only JTAG-flasher will help in my case (cannot get it, because I'm out of "civilisation" for a long time), but you have given to me the last hope))
Could you please make a screenshot where you did see the option "Connect with MiAssistant". Which version of chinese MiPCSuite did you use?
I used version 2.3.0.9091, it hangs on approximately 5% (on the phone) and does not proceed... was waiting for 30 minutes, no progress... I used it in a way to download the latest ROM and then install it.

My dear friend Zappo, I still do not believe, but I had success recovering this brick with chinese MiPCSuite v2.3.0.9091. It just downloaded the latest ROM for the device from internet and was flashing it during 1 hour 10 minutes!!! Before I had no success because I was waiting only half an hour, not more!)) But exactly after half an hour it continues and finalizes successfully!!! Another reason of my success I think could be (but less probable) that I have opened a device some days ago and disconnected the battery in order to try to get in EDL mode without the power (but was also not successful). Also today before I started MiPCSuite I have switched on the device from completely OFF state with Volume+ and Power button... So, I really do not know how the success come, but now I'm really happy!!! Many, many, many thanks for your help and for second breath )))

The current image(boot/recovery) have been destroyed and can not boot.

Hello.
I tried to lock back the bootloader, and after executing
PHP:
fastboot flashing lock
got an error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then I faced a similar problem described in this topic https://forum.xda-developers.com/re...-3-pro-boot-recovery-destroyed-t3938481/page3
When you turn on the phone an error pops up for 20 seconds and then phone reboots and everything goes in a circle.
If you press the power button once, the reboot process stops and the phone turns off.
I tried to enter fastboot mode by pressing the power + volume button -
But I didn't succeed.
Can you tell me what I'm doing wrong ?

You should have return the stock fully before locking.
Try to unlock again and then flash original firmware fully

kkffiirr said:
You should have return the stock fully before locking.
Try to unlock again and then flash original firmware fully
Click to expand...
Click to collapse
Thanks for the answer, but unfortunately due to this error fastboot does not load.
If you can tell me how I can flash the phone I will be very grateful.
I would not like to contact an unofficial service...

I guess you don't have recovery as well...
Well, we need to dig in Chinese forums to find edl option, since I don't see any other way.

kkffiirr said:
I guess you don't have recovery as well...
Well, we need to dig in Chinese forums to find edl option, since I don't see any other way.
Click to expand...
Click to collapse
Before lock, I installed TWRP, but idk if it's still there.
UMF cable will help me ?

Me i too i got same your problem i bricked my realme x2 i still didnt find the solution to flash it again

Maybe contact service center

Try booting with both VolUp and VolDown pressed. The screen should be black, but computer should see 9008 device (Qualcomm Download mode). If it works, search through Internet for Snapdragon 730G programmer and proper boot files.
Another option is devices alike Medusa Box; they seem to have underground connections with manufactors, they may provide a solution too.
EDIT. Thanks to the clarification from @T1MOXA, you can enter EDL mode by holding VolUp and VolDown and plugging the switched off phone to a computer.

first confirm that your device is fully turn off and connect a usb cable to the PC by pressing Vol (-) at the same time and you will be in fastboot mood.

yakovpol said:
Try booting with both VolUp and VolDown pressed. The screen should be black, but computer should see 9008 device (Qualcomm Download mode). If it works, search through Internet for Snapdragon 730G programmer and proper boot files.
Another option is devices alike Medisa Box; they seem to have underground connections with manufactors, they may provide a solution too.
Click to expand...
Click to collapse
I've tried this option before, but it led me to the same error screen.
I turned off the phone with a single press of the power button, then pressed all the buttons at the same time.

razu031 said:
first confirm that your device is fully turn off and connect a usb cable to the PC by pressing Vol (-) at the same time and you will be in fastboot mood.
Click to expand...
Click to collapse
I just got the same error.
When you connect the cable, the phone boots with the same error.

narshi shukla said:
Maybe contact service center
Click to expand...
Click to collapse
Unofficial ?
They too bad in my country.
They can easily make it worse.

I can buy a UMF cable, but whether it will help me I do not know.
What do you think ?

Good news...
My phone is defined on the PC as "Qualcomm HS-USB QDLoader 9008 (COM 5)" by connecting and pressing all the volume keys.
Only I don't know if it gives me anything and what to do next...

T1MOXA said:
Good news...
My phone is defined on the PC as "Qualcomm HS-USB QDLoader 9008 (COM 5)" by connecting and pressing all the volume keys.
Only I don't know if it gives me anything and what to do next...
Click to expand...
Click to collapse
Most phones will be able to flash in this mode using qfil tool,
But first you need to find necessary firmware, idk if stock rom downloaded from official site will work or not, maybe fastboot one will work.
This mode is called emergency download mode (edl).
But pls do a lil research as its a newly launched device and you can easily mess it up.
BTW exact same error(boot recovery destroyed) is common error on realme Phones and it can be fixed by flashing vbmeta.img using fastboot.

See attached image for reference only
The 1kb vbmeta is modified to bypass boot verification.
Idk if such vbmeta is available for x2.
If not then flashing stock vbmeta might work.

T1MOXA said:
Hello.
I tried to lock back the bootloader, and after executing
PHP:
fastboot flashing lock
got an error
Click to expand...
Click to collapse
I have the same problem. On 4pda there is a firmware for MsmDownload Tool and the tool itself, but it requires a username and password. Are there alternative options to restore your phone?

Problem: The current image have been destroyed and can not boot
Dear friends, I'm using Realme X2.
Last day, I try bootloader unlock my device. Bootloader unlocked successfully and twrp also successfully installed.. but after I'll try boot, but the is not boot.
The pop-up message shows "THE CURRENT IMAGE HAVE BEEN DESTROYED AND CAN NOT BOOT".. so please me how to solve this problem .
My mobile model number : RMX1992
please help me

Iamsanthoshravi said:
Dear friends, I'm using Realme X2.
Last day, I try bootloader unlock my device. Bootloader unlocked successfully and twrp also successfully installed.. but after I'll try boot, but the is not boot.
The pop-up message shows "THE CURRENT IMAGE HAVE BEEN DESTROYED AND CAN NOT BOOT".. so please me how to solve this problem .
My mobile model number : RMX1992
please help me
Click to expand...
Click to collapse
Look friend i had the same problem and i fix it u have to download the firmware RMX1991 not ozp file then u have to buy the password of the firmware there are sone website they ask you to install teamviewer because thet gonna flash your phone online ok friend i did as i mentioned and i fixed so there is no other way to fix it i cant put the link of firmwares because last time xda warned me

I got same
Hey bro can you fix your phone?
Today I experience same.
What can I do now?

Question [HELP] Unbrick an almost completely bricked phone.

Hey.
This post is my last faith in this device.
So basically I was about to flash partitions, but when I tried to go into fastbootd to flash the critical stuff, after the "fastboot reboot fastboot" command my phone was completely got bricked. I already tried every type of key combinations, the screen was black the entire time, and the phone won't even vibrates.
The only signal of it's being alive, when I plug it and press pwr + vol up, windows gives the sound of a connected/disconnected device, and the MsM tool shows that too. At this point, i was sure about the MsM tool and didn't panicked, I knew that I can almost always unbrick the phone with that... Hmm... This time it was different, because every time I get an error: "Sahara communication failed", or "Param preload", and I cant even do anything. Currently the phone was completely dead.
If you have any idea how to fix that Please let me know! Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

pmppm said:
Hey.
This post is my last faith in this device.
So basically I was about to flash partitions, but when I tried to go into fastbootd to flash the critical stuff, after the "fastboot reboot fastboot" command my phone was completely got bricked. I already tried every type of key combinations, the screen was black the entire time, and the phone won't even vibrates.
The only signal of it's being alive, when I plug it and press pwr + vol up, windows gives the sound of a connected/disconnected device, and the MsM tool shows that too. At this point, i was sure about the MsM tool and didn't panicked, I knew that I can almost always unbrick the phone with that... Hmm... This time it was different, because every time I get an error: "Sahara communication failed", or "Param preload", and I cant even do anything. Currently the phone was completely dead.
If you have any idea how to fix that Please let me know! Thanks.
View attachment 5788047
Click to expand...
Click to collapse
From the image you posted, it looks like you are using the wrong MSM version. "Device not match image".......

TheGhost1951 said:
From the image you posted, it looks like you are using the wrong MSM version. "Device not match image".......
Click to expand...
Click to collapse
I used this exact version on this phone like 2 days ago, I dont think it is a version problem, but thanks for the help!

And it is pretty interesting.. As far as i know EDL connection only alive for 5-10 sec, but currently MsM tool shows Connected until my phone was plugged in (even after refreshing it)

pmppm said:
I used this exact version on this phone like 2 days ago, I dont think it is a version problem, but thanks for the help!
Click to expand...
Click to collapse
Just like the other posted said. If it says that error, it means that your device ID is different. Did you possibly use the India MSM which would change your device ID and not allow you to use the one you were using before? You can also try unchecking sha265check and check use lite firehose and see if it works that way.

TheSayaMan said:
Just like the other posted said. If it says that error, it means that your device ID is different. Did you possibly use the India MSM which would change your device ID and not allow you to use the one you were using before? You can also try unchecking sha265check and check use lite firehose and see if it works that way.
Click to expand...
Click to collapse
Okay so basically, you're both right. I got the Global version, but with the correct MsM version for that did not worked. The solution was to use the Indian version to unbrick it, then ofc switch back to the global. I took this idea from this post, It's seemed so idiot to do it that way, but I had nothing to lose. Thanks again!

pmppm said:
Okay so basically, you're both right. I got the Global version, but with the correct MsM version for that did not worked. The solution was to use the Indian version to unbrick it, then ofc switch back to the global. I took this idea from this post, It's seemed so idiot to do it that way, but I had nothing to lose. Thanks again!
Click to expand...
Click to collapse
Once you used the Indian MSM, then to go global you have to install the updater tool from Google Play store to choose the version you want and install it that way. I believe.....

TheGhost1951 said:
Once you used the Indian MSM, then to go global you have to install the updater tool from Google Play store to choose the version you want and install it that way. I believe.....
Click to expand...
Click to collapse
I don't believe it's available in play store, have to Google search for it but otherwise your right, once you use the India MSM, your device ID is permanently changed and can no longer use the reg MSM for the device.

TheSayaMan said:
I don't believe it's available in play store, have to Google search for it but otherwise your right, once you use the India MSM, your device ID is permanently changed and can no longer use the reg MSM for the device.
Click to expand...
Click to collapse
Would this not work?

I am not sure how OnePlus implements it, but many devices have a Qualcomm USB mode or "Emergency Download Mode" for performing a low level reflash of basic firmware such as the bootloader. Most often, when a device screen doesn't come on, but it vibrates and a PC shows a connected device, this is the case - the PC has detected the QUSB mode.
Unfortunately, Qualcomm does not make their Qualcomm Product Support Tool available to the public, and most OEMs do not provide the necessary binaries to restore the bootloader. The device cannot be repaired or restored without these tools, unless the mainboard is replaced. Unfortunately in this case, I believe that is your only option.

V0latyle said:
I am not sure how OnePlus implements it, but many devices have a Qualcomm USB mode or "Emergency Download Mode" for performing a low level reflash of basic firmware such as the bootloader. Most often, when a device screen doesn't come on, but it vibrates and a PC shows a connected device, this is the case - the PC has detected the QUSB mode.
Unfortunately, Qualcomm does not make their Qualcomm Product Support Tool available to the public, and most OEMs do not provide the necessary binaries to restore the bootloader. The device cannot be repaired or restored without these tools, unless the mainboard is replaced. Unfortunately in this case, I believe that is your only option.
Click to expand...
Click to collapse
It is called the MSM Download Tool. And it is device specific and ready available.

TheGhost1951 said:
It is called the MSM Download Tool. And it is device specific and ready available.
Click to expand...
Click to collapse
Oh, specifically for the OnePlus. Good to know. I suppose I'm of absolutely no help here

Odin is for flashing Samsung devices. Samsung and now OnePlus are the only two devices I have worked with.

pmppm said:
Hey.
This post is my last faith in this device.
So basically I was about to flash partitions, but when I tried to go into fastbootd to flash the critical stuff, after the "fastboot reboot fastboot" command my phone was completely got bricked. I already tried every type of key combinations, the screen was black the entire time, and the phone won't even vibrates.
The only signal of it's being alive, when I plug it and press pwr + vol up, windows gives the sound of a connected/disconnected device, and the MsM tool shows that too. At this point, i was sure about the MsM tool and didn't panicked, I knew that I can almost always unbrick the phone with that... Hmm... This time it was different, because every time I get an error: "Sahara communication failed", or "Param preload", and I cant even do anything. Currently the phone was completely dead.
If you have any idea how to fix that Please let me know! Thanks.
View attachment 5788047
Click to expand...
Click to collapse
India device or global devices
And tip
Reboot to edl
Power off the phone
And press and hold pressed the voll up and voll down
And putt in the usb cable and hold pressed the voll up and voll down
And try msm tool

V0latyle said:
Oh, specifically for the OnePlus. Good to know. I suppose I'm of absolutely no help here
Click to expand...
Click to collapse
Not only specific to OnePlus but also specific to OOS versions.

Might try to uninstall Qualcomm drivers, make sure PC driver signing is disabled. Reboot PC, then re-install latest Qualcomm drivers, re-boot PC and try again with MSM tool. The windows sound when plugging in before is the sound of a device plugged in but couldn't recognize it and threw it out of device manager. That was the reason for the TWO sounds you heard. Also try holding down on vol + - and pressing power and holding it down to try to boot into fastboot mode. If it does, flash boot boot TWRP.img and then boot into edl from there with phone connected to PC and MSM tool in start mode ready to flash as soon as device is connected.