Motorola g7 play xt1952-1 BLANKFLASH PROBLEM - Moto G7 Play Questions & Answers

Hi, I have a problem with my phone motorla g7 play (xt1952-1). The phone is hardbrick and I can't find the right blankflash for it. When I run blankflash from other topics sahara error pops up, if when I run blankflash I reset the phone (power + volume up) then very long time the message "Waiting for firehose to get ready" persists until finally error pops up and I can only shut down the program. I need the correct file most likely, qualcoom I have installed and it appears as com** in device manager. Sorry for my poor language.

Hi. Check my post on Blank Flash, i have a Firehose prepped. All you have to do is drag the firehose into your BlankFlash folder and watch it do magic.

Thanks a lot of for your answer. Main problem is, when i run cmd and put your command "fastboot oem blankflash" i've got information about "waiting for any device". Any ideas how to resolve it? Phone is full bricked, cant do nothing except turn off/on (sound at pc and appear in device manager as a qualcomm hs-usb qdloader).

Related

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?

Bootloader/Recovery problems...

Hi!
I recently bought an LG G4 from an online seller. The cell phone itself is working fine, but it has some problems. It is a refurbished model.
I will very much appreciate any help.
The cell phone is actually a F500L model (I checked it by looking at the motherboard), but in the software information it shows to be a model H81510h.
The phone is not rooted. But I believe that someone did it, changed the device's descriptions and then uninstalled it.
It is an android 5.1, but I cannot update using the update center. There it shows that it is already in the latest version.
In the developer settings, I try to enable OEM unlock, it activates for 1 second and deactivates automatically.
I try to do the hard reset, but when restarting to start the process, it presents an error "Secure booting error 1002".
I can activate USB debugging, it is recognized in ADB tools and I can send commands to it. But it does not start the bootloader with the command "adb reboot bootloader", and it presents the same error "Secure booting error 1002" if I try to send the command "adb reboot recovery".
I can activate the Download mode (by pressing the VOL UP button and inserting the USB cable), but it is not recognized by LGup (UNKNOW / COM5 H81510h), LGup does not let me work with it.
In the LG Flash Tool, it does not start the flash process, when it reaches "BIN CRC Check" it presents the error "Failed PreviousLoad0". (I already changed the port to COM41)
In LG Bridge, it is recognized as F500L and shows that there is an update. But when trying to update, it does the first steps, but after the download, when installing it gives an error and asks to start over.
I have tried to use UPPERCUT_1.0.0.0, without success.
I do not know what else to do...
Any help will be appreciated.

Nokia 7.1 Bricked (QUSB_BULK). Please help

Hey everybody.
I woke up the other day to my phone being off (happens sometimes but turns on normally when pressing the power button). This time however, it didn't turn on. I tried all kinds of combinations to turn it on, but nothing worked. I plugged it into the laptop, and it showed first QUSB_BULK. Downloaded qualcomm drivers, now it shows HS-USB Diagnositcs 9008.
I tried QFIL, but I dont know what file to load. I tried to load the STOCK ROM files, but I only get an error saying "Failed to switch to Emergency Download Mode".
QPST needs a .hex image?
OST for Nokia isn't working.
and SP Flash tool needs a Scatter file?
I dont know what to do. Please help!
Damn.. I was hoping someone would have posted a reply to this. I just experienced the same exact thing with my Nokia 7.1..
Anyone have any solutions? I ran through the same steps as OP above. Was showing as "QUSB_BULK" in Device Manager. Installed the Qualcomm Drivers, now it shows as "HS-USB Diagnostics 9008".
Doesn't show up in "fastboot devices", doesn't show up in "adb devices".. doesn't respond to any PWR+VOLUP/DWN combinations.. nothing. Practically dead.

Question I am stuck in fastboot and can only boot into fastboot please help??

I can only accsess fastboot and cannot reboot into anything except fastboot.... I tried extracting the payload bin but can only flash a few lines then I am told to reboot into fastbootd but cannot access that either... I cannot access recoveries either and I have tried to flash them but still wont budge... any ideas??
Use MSM tool
I also have this problem and I can't get it to EDL mode nothing happens stuck in fastboot.
I just typed a whole guide on how I managed to solve this in detail and the tab got closed out... in short then, download Qualcomm drivers and not oneplus's. There are many drivers in the file, just extract the whole thing and point to the file on device manager and include subfolders. It should find which I think was the HS-USB QDloader 9008 driver then install. Make sure you download the correct MSM for your version. The latest for global (or O2) is only hosted on one server and was going to take 12 hours to download on highspeed internet so I used lemonadep_22_O.05_210324 being 11.2.2.2. Use the Win7 version. Even though you cannot use EDL, you can reference these key combinations to get it recognized. If you're having a completely black screen, use the all button press hold until it vibrates. Make sure you are shutdown all the way and if needed use fastboot to. With MSM opened, drivers installed, and phone off, hold both vol keys and connect to PC. Hit Enum to refresh connections and hopefully it shows up and you can get a successful download complete. I found that the black screen was actually the device being in recovery mode. It was possible to successfully enter recovery using boot with power and volume down at times, although all sideload OTA's (along with prior fastboot flash boot *.img, fastboot -w, fastboot update, fastboot reboot-edl, ect.) failed. There was a lot of trial and error where just repeating some things after they had failed almost magically started working or stopped however this process is what worked in my case.
xifo.0001 said:
I just typed a whole guide on how I managed to solve this in detail and the tab got closed out... in short then, download Qualcomm drivers and not oneplus's. There are many drivers in the file, just extract the whole thing and point to the file on device manager and include subfolders. It should find which I think was the HS-USB QDloader 9008 driver then install. Make sure you download the correct MSM for your version. The latest for global (or O2) is only hosted on one server and was going to take 12 hours to download on highspeed internet so I used lemonadep_22_O.05_210324 being 11.2.2.2. Use the Win7 version. Even though you cannot use EDL, you can reference these key combinations to get it recognized. If you're having a completely black screen, use the all button press hold until it vibrates. Make sure you are shutdown all the way and if needed use fastboot to. With MSM opened, drivers installed, and phone off, hold both vol keys and connect to PC. Hit Enum to refresh connections and hopefully it shows up and you can get a successful download complete. I found that the black screen was actually the device being in recovery mode. It was possible to successfully enter recovery using boot with power and volume down at times, although all sideload OTA's (along with prior fastboot flash boot *.img, fastboot -w, fastboot update, fastboot reboot-edl, ect.) failed. There was a lot of trial and error where just repeating some things after they had failed almost magically started working or stopped however this process is what worked in my case.
Click to expand...
Click to collapse
After hundreds of trys I finally got it scared ****less that I lost my phone.
holydemon said:
After hundreds of trys I finally got it scared ****less that I lost my phone.
Click to expand...
Click to collapse
lol same here, you say it's working now though?
xifo.0001 said:
lol same here, you say it's working now though?
Click to expand...
Click to collapse
Yeah but that was a hassle should've been easier to reach that interface. I was almost sending it to service for nothing but a stupid unreachable interface nonsense.
Also to note when I tried with original cable from the box was successful the other usb cable gave me problems.

Oneplus 7T bricked in EDL mode (Firehose GetUsInfo Failed)

I was using my oneplus 7T normally without root and with bootloader locked when it decided, out of nowhere, to fall into "Qualcomm Crashdump Mode". When I tried to reboot it, it just went into "Qualcomm Crashdump Mode" again. So I went into fastboot mode, unlocked it, and flashed an european ROM from here: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7T/ . However when the device tried to boot up it just went to "Qualcomm Crashdump Mode" again, so I tried using "MsmDownloadTool" (hotdogb_14_E.21_201105) ( https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.3994835/ ) and it worked, but this time when the device attempted to boot up it went into EDL mode and the bootloader was locked and when I tried to unlock it, it gave me an error related to "OEM unlock" not being enabled in developer options. So I tried using "MsmDownloadTool" (hotdogb_14_E.21_201105) again, and somehow this time it actually booted up. Still, after 10 seconds it went into EDL mode AGAIN (note: at this point, I couldn´t get out of EDL mode, I could only boot into anything else after the battery died, in the first boot). So I downloaded another ROM for msm but this time it gave me the error: Firehose GetUsInfo Failed, and the phone seems to disconnect and reconnect. From here I tried multiple ROMs for msm and always received the same error, even using the one I used originally. (Note: I have been waiting for my battery to die for 5 days, and it still has power; also tried removing the battery )
Output when trying to use EDL-master:
edl.py printgpt
Qualcomm Sahara / Firehose Client (c) B.Kerler 2018-2019.
__main__ - Trying with no loader given ...
__main__ - Waiting for the device
__main__ - Device detected
__main__ - Mode detected: sahara
Device is in EDL mode .. continuing.
Library.sahara -
------------------------
HWID: 0x000a50e100514985 (MSM_ID:0x000a50e1,OEM_ID:0x0051,MODEL_ID:0x4985)
PK_HASH: 0x2acf3a85fde334e2e28d64cbc416b2474e0e95cad4698f143e27479d67e92d99
Serial: 0xb0180648
SBL Version: 0x00000000
Library.sahara - Couldn't find a loader for given hwid and pkhash
Commands I tried to unlock bootloader:
fastboot oem unlock; fastboot oem unlock-go; fastboot flashing unlock; fastboot flashing unlock_critical
Can someone help me with this issue?
Sorry if the description was too confusing, long, or had any mistakes in terms of English. I am just trying to be as complete as possible.
The same arround here.....
Any solution?
Sounds like hardware failure (memory ram chips). Buy a cracked 7T and swap motherboard
First of all thank you for replying! I really appreciate it. Second of all, I did some research considering your reply and I stumbled upon this post: https://forum.xda-developers.com/t/oneplus-6-possibly-soft-bricked.4297489/ . What I did after seeing it was, I vacuum sealed my phone in a bag (to minimize condensation) and place it in the freezer for about 20 minutes I tried booting up the phone but it just went into edl mode again. However this time when I used MSM download to it actually was able to complete the whole process. The phone still didn't boot, but now I can enter fastboot and recovery. All this leads me to conclude that you are right.

Categories

Resources