Database Info

[Completed] Help with Bricked Blu LIFE PURE XL 16GB Snapdragon, tried everything...

Hello everyone.
I'm having problem in flashing a ROM into my Blu Life Pure XL 16GB with Snapdragon (Equivalent to Redmi Note 3).
My smartphone is in the following situation: >>>It only boot into fastboot mode.<<<
I cant get into recovery mode, or EDL or anything else. Debug mode is enable and bootloader is unlocked. Tried every "button combination" and no sucess.
My PC recognize ADB interface driver, i can see my device in "fastboot devices", but if i try to type "fastboot continue" my device just get stuck on BLU logo and i must restart it. (In cant ever turn off the device)
I tried to flash a ROM through MI Flashtool, the software recognize COM port everything seems to be ok, but if i try to flash a ROM then tooks forever. The green bar gets full, more then 3 hours waiting and nothing.
I also try to enter in EDL mode to try flashing a ROM through QFIL (Qualcomm Flash Image Loader), since i can only get fastboot mode i just downloaded "fastboot EDL" that i found here on XDA however its not worked, its just get stuck in "Waiting for device...". I can list my device normally using Minimal ADB and Fastboot version 1.4.2 but no sucess with Fastboot EDL V1 and V2.
All drivers are installed and working.
Anyone else have another method?
There is another FASTBOOT EDL that works on my device?
Thanks guys.

Hi there and welcome to assist,
Unfortunately there is nothing about your question/device on XDA forum. Try a Google search first or contact the manufacturer for stock firmware and flashing instructions.
Also you can try this [GUIDE]How to reboot to EDL from fastboot
You'll have to create an account to post in the main forums if you have any other questions.
Good luck

I need urgent help :(

Hey there... I was trying to get my OnePlus 7 -That I just bought - to a rooted Android 10, updating was the easy part but while trying to "fastboot flash boot twrp.img" I think I somehow got myself stuck making the bootloader (aka fastboot mode ) as my main thing the phone load into and now when I turn on the phone it goes straight to fastboot mode I go and try to "fastboot flash boot twrp.img" it says OKAY twice but I can't load into recovery it takws me back to the fast boot again.... Idk what to do... Help

More into:
I got to the twrp before once during the process and idk why dumb me rebooted when I couldn't access my phone files from pc I wanted to put the image of OOS on a flash drive and via OTG but once I restarted by mistake after that whatever choice I make on the fastboot screen will quickly restart and get back to the same screen, so I can do "fastboot flash boot twrp.img" successfully but I can't load to it I hit reboot to recover or Start or Reboot Bootloader nothing takes me to twrp,
Also when I try "fastboot flash recovery twrp.img"
It says sending recovery okay, writing recovery failed, (remote: (recovery_b) no such partition)
I hope to get any help and I'm sorry if it's an obvious thing I couldn't notice, I'm not the sharpest between my brothers. Momma says. ? with me. I'll appreciate it I promise.

Have you tried this Fastboot ROMS?

Use this:
https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
After that just put offical Rom zip for your region on internal memory and after that install update. voila

Unbrick tool also available for OxygenOS pie https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325 :good:

Help
same issue with me...whenever i try to recover using fastboot method,it gives an error like product name is sdm845 and required is msmnile
and when i use the msm tool , it gives an error of sahara server....
any help is highly appreciated.

sourabhone said:
same issue with me...whenever i try to recover using fastboot method,it gives an error like product name is sdm845 and required is msmnile
and when i use the msm tool , it gives an error of sahara server....
any help is highly appreciated.
Click to expand...
Click to collapse
"sahara server" problem : disable driver signature / update drivers
https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
Qualcomm dr: https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/
you must to press power button at the same time you plug in usb cable.....keep trying and your computer will start installing drivers for Port 9008
(you can use Google Search for more Info about "sahara" problem)

First of all twrp.img is a recovery image. You would normally use fastboot flash recovery twrp.img.
Secondly, you aren't supposed to flash twrp.img but use fastboot boot twrp.img and then boot to twrp and flash the twrp installer. If you can boot into fastboot, type fastboot boot twrp.img(twrp.70 for android q) and then flash twrp installer and oos. And if you can't boot into recovery you will have to use the msm tool.

daitalos said:
"sahara server" problem : disable driver signature / update drivers
Qualcomm dr:
you must to press power button at the same time you plug in usb cable.....keep trying and your computer will start installing drivers for Port 9008
(you can use Google Search for more Info about "sahara" problem)
Click to expand...
Click to collapse
Thanks daitalos for the reply..
the drivers for 9008 are installed as visible in device manager...
the msm tool shows the phone as connected, when i start the process, it waits for loading firehose binary and waits there for 10 sec.....after that throws error of sahara communication failed (FH:258)
i again tried the volume up + power button combo but to no avail...
also there is no red led light on the phone while charging

sourabhone said:
Thanks daitalos for the reply..
the drivers for 9008 are installed as visible in device manager...
the msm tool shows the phone as connected, when i start the process, it waits for loading firehose binary and waits there for 10 sec.....after that throws error of sahara communication failed (FH:258)
i again tried the volume up + power button combo but to no avail...
also there is no red led light on the phone while charging
Click to expand...
Click to collapse
In device manager you can see "Qualcomm HS -USB QDLoader 9008 (com3 for example) ?
You tried another usb port (?)
in windows 10 it is better for the computer to have the "developer mode" enabled
Close any antivirus temporarily..
Run msm tool as Administrator ofcourse..
(I don't know but If you try with msm tool from here : https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
you should see the models it supports (GM1900, GM1901, GM1903, GM1905)
_I think the problem is on the computer and the communication with the device...
sry for english

Thanks
daitalos said:
In device manager you can see "Qualcomm HS -USB QDLoader 9008 (com3 for example) ?
You tried another usb port (?)
in windows 10 it is better for the computer to have the "developer mode" enabled
Close any antivirus temporarily..
Run msm tool as Administrator ofcourse..
(I don't know but If you try with msm tool from here : h t tp s: // forum . xda-developers . com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
you should see the models it supports (GM1900, GM1901, GM1903, GM1905)
_I think the problem is on the computer and the communication with the device...
sry for english
Click to expand...
Click to collapse
Thank you so much daitalos.
At last i was able to recover my phone from being a paperweight.Used my other laptop and it worked perfectly first time.Maybe my 1st laptop was having some issues.

nubia x fastboot loop

hi community
i hope someone is still active in this nubia x section, because i hope for some help.
i flashed twrp to my nubia x with using Minimal ADB and Fastboot.
with twrp i flashed the new rom 3.21.
as i tried also to flash gaps i got in the "your device is corrupt. it can't be trusted and will not boot g.com/abh" error.
but because i still was able to flash files with Minimal ADB and Fastboot i flashed all the *.img files i found in the NX616J-update.zip to the phone.
so i was able to boot the recovery mode and flashed the original rom 3.21 with otg from usb stick.
then the nubia x booted normal to the original rom, but because the playstore wasn't working, i flashed again twrp with Minimal ADB and Fastboot.
in twrp i used all swipe and format functions because i thinked i want clean what i can to start from the beginning.
sorry i dont remeber exactly all the steps i did.
and now my problem is the phone only boot to the fastboot menu.
Minimal ADB and Fastboot seems to still work normal, i can unlock the device and flash twrp.
but after reboot i am still in the fastboot menu.
only boot do edload don't boot to fastboot, and if i boot edload i can connect the phone to my pc and with the qfil-tool i see connect:
"Qualcomm HS-USB QDLoader 9008 (COM4)
But to use qfil to flash i think i need a "MetaBuild Configuration (contents.xml)", and i can't find this file for nubia x.
i hope someone has an idea how i get my phone out of this fastboot-loop and share it here.
thanks and kind regards
hoitschau

i found the solution, thanks to rcsj.
https://forum.xda-developers.com/nubia-x/help/install-rom-stock-3-18-gapps-support-t4108715
flashing the file vbmetaDISABLED.img from the google drive with fastboot was my rescue.

oneplus 8t(tmo) hardstuck in fastboot mode

Been trying to fix my phone for two days. first time rooting and it was kind of a success besides the wifi not working so i wanted to undo the root. tried many things and apparently messed up many things. The phone will not go into recovery mode. It wont turn on. if i try to flash anything i get many different errors(even twrp). And yes ive made sure everything is for my phones version(s). Oneplus 8t tmobile. so basically the phone can turn off and go into fastboot and the only thing inbetween that is it shows the 1+ logo for a split second.
"fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable."
"unknown partition"
"FAILED (remote: 'Flashing is not allowed for Critical Partitions" btw bootloader is unlocked so dont understand how this is happening unless im misunderstanding the meaning
msm will not detect my phone also. even updated the qualcomm drivers and still nothing. however can't really find a sure fire way to determine if the phone is in edl mode besides it connecting in msm. which i haven't been able to do even at the start of yesterday when the phone could atleast flash twrp and boot edl from there. Pls help

lostneedfound said:
Been trying to fix my phone for two days. first time rooting and it was kind of a success besides the wifi not working so i wanted to undo the root. tried many things and apparently messed up many things. The phone will not go into recovery mode. It wont turn on. if i try to flash anything i get many different errors(even twrp). And yes ive made sure everything is for my phones version(s). Oneplus 8t tmobile. so basically the phone can turn off and go into fastboot and the only thing inbetween that is it shows the 1+ logo for a split second.
"fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable."
"unknown partition"
"FAILED (remote: 'Flashing is not allowed for Critical Partitions" btw bootloader is unlocked so dont understand how this is happening unless im misunderstanding the meaning
msm will not detect my phone also. even updated the qualcomm drivers and still nothing. however can't really find a sure fire way to determine if the phone is in edl mode besides it connecting in msm. which i haven't been able to do even at the start of yesterday when the phone could atleast flash twrp and boot edl from there. Pls help
Click to expand...
Click to collapse
WiFi not working because the boot.img you flash is not match your system version.
ULTRAJC said:
If you have to use online source patched boot.img, don't flash, only do "fastboot boot boot.img", if it can successfully boot into the system, then use magisk patch current system boot.img and reboot.
Click to expand...
Click to collapse
You can use command "fastboot oem edl".
EDL mode(usually a full black screen) will timeout in few seconds if not receive any command from MSM, so you can start MSM flash frist then put phone to EDL.
Two possible situations need attention:
Some_Random_Username said:
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008 ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
Click to expand...
Click to collapse
Some_Random_Username said:
Why is my device getting in Qualcomm crashdump mode in spite of a successful download?
Your unit was most likely manufactured after March 9th 2021, see https://forum.xda-developers.com/t/...ice-to-oxygenos.4180837/page-14#post-84789741 for reference. You therefore need to use HydrogenOS 11.0.7.12 MSM to recover your device linked at https://www.oneplusbbs.com/thread-5886794-1.html (mirrored at https://mega.nz/file/O8UySbgR#cXGlHkdA_7CYEhKIrek9zzAEwJ7Vx1D5BZdemnPlvGE by @pikatenor ). Getting new OxygenOS MSM tools is nowadays impossible unless you own the device it is meant for, so OP will not be updated to add new OxygenOS MSM tools allowing to workaround this issue. Feel however free to reach out to me in DM if you would like to get told how to maximise your chances to obtain one.
Click to expand...
Click to collapse
If MSM just not work or you not using Windows, you can follow:
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com

ULTRAJC said:
WiFi not working because the boot.img you flash is not match your system version.
You can use command "fastboot oem edl".
EDL mode(usually a full black screen) will timeout in few seconds if not receive any command from MSM, so you can start MSM flash frist then put phone to EDL.
Two possible situations need attention:
If MSM just not work or you not using Windows, you can follow:
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com
Click to expand...
Click to collapse
fastboot oem edl results in FAILED (remote: unknown command). tried it in minimal adb and fastboot and platformtools.

and that is the guide ive been following. however i keep getting partition issues.

lostneedfound said:
and that is the guide ive been following. however i keep getting partition issues.
Click to expand...
Click to collapse
Fastboot unbrick guide didn't work for you?
Maybe continue to try the key combination, open device manager, if you see devices name: …QDLoader 9008(driver installed) or …QHUSB_BULK(driver not install). That's EDL mode.
Some guide suggest this two command may work:
"fastboot reboot edl"
"fastboot reboot-edl"
Also can try "fastboot boot recovery that have adb.img" then use command "adb reboot edl".

okay so i none of that worked just continues to say unknown command or unknown partition. with the qual com i dont see anything otherthan android device for phone related stuff in the device manager. is there something ican do to get these partition errors to go away? last night i wasn't having any trouble with them and now they are everywhere and i really dont understand why becuase i hardly flashed anything last night. today i started flashing stuff from the guide you recommended/the one ive been using all this time and thats when the partition errors started and now im seeing them everywhere and i followed the guide down to the dime.

solved out of pure rage i restored my pc to factory and when it started back up i redownload msm and phone connected perfectly. also correctly rooted by adb pulling my own boot.img. ty for your help

lostneedfound said:
solved out of pure rage i restored my pc to factory and when it started back up i redownload msm and phone connected perfectly. also correctly rooted by adb pulling my own boot.img. ty for your help
Click to expand...
Click to collapse
That was one way to go, but for others. The problem was your adb/fastboot was old. Should no longer use the minimal adb it's outdated. Always use the latest platform tools.

nujackk said:
That was one way to go, but for others. The problem was your adb/fastboot was old. Should no longer use the minimal adb it's outdated. Always use the latest platform tools.
Click to expand...
Click to collapse
Exactly @nujackk ,
I have found the most likely reason for an "unknown command" message to a newer fastboot command is an old fastboot.exe version.

IN2017/TMO flashing Global failure, stuck with CrashDump & Fastboot, no EDL/MSM, etc.

Hi guys,
I think I've tried it all at this point so I'm in need of some help.
I've got the T-Mobile IN2017 version of the OP8. I wanted to get rid of the T-Mobile junk and get access to the "regular" updates.
I started with this guide: [Guide] Convert to Global [WIP]
I got my unlock token today and gave 11.0.0-GLOBAL-OnePlus8Oxygen_15.O.30_OTA_0300_all_2010031624_c5e68b42b3325-FASTBOOT a shot. When it booted into Rescue Mode I assumed something had gone wrong so I told it to wipe everything and I figured I'd start over. I realized this was probably a good thing because I had neglected to backup anything.
I used instantnoodlet_15_O.16_201001 to reset. I couldn't get the volume up + volume down combination to work at all so used adb to reboot in edl. All went well.
I then re-unlocked the bootloader, flash booted into twrp-3.3.1-test10-instantnoodle-unified-mauronofrio.img and made some backups.
I installed the latest Magisk (changing .apk to .zip) within TWRP, and used adb shell to make a backup of my persist.img
I went back to 11.0.0-GLOBAL-OnePlus8Oxygen_15.O.30_OTA_0300_all_2010031624_c5e68b42b3325-FASTBOOT and ran the flash-all.bat but this time it failed and I've found myself bricked: CrashDump Mode.
I've only been able to switch betwen CrashDump Mode, off, and Fastboot. When I'm in Fastboot if I try to start or boot in recovery it just ends up back at CrashDump. If I do a hard power off and try holding volume up + down to get into edl I end up at Fastboot again as soon as I plug the usb in. The commands fastboot reboot edl, fastboot oem edl, and fastboot reboot-edl all give me errors. I can no longer flash boot into TWRP. I've tried flashing the 11.0.0 Global again but I get "Flashing is not allowed for critical partitions" and "partition not found" errors before I end up back at the CrashDump screen.
When in CrashDump it shows up in my device manager as Qualcomm HS-USB Diagnostics 900E (COM13). When I'm in fastboot it appears as OnePlus Android Bootloader Interace. I have uninstalled the drivers and reinstalled the drivers (OnePlus_USB_Drivers_Setup, QDLoader HS-USB Driver_64Bit, androidwinusb). I'm using the latest Platform Tools. I am in test mode and I have turned off driver signature.
I only have two USB 3.0 ports and I don't have access to another Windows PC. I have used three different USB cables, including the OnePlus original, in both ports. I have taken off my phone case to make sure nothing is interfering with me pushing volume up + down. My thumb hurts from pressing it so much. I've done this dozens of times now. No EDL.
I'm at a loss. Someone please help me!
Edit: I've tried using the All-In-One-Tool but it says reboot to EDL doesn't work because I'm in fastboot and trying to boot into the latest twrp still just sends me back to CrashDump.

Solved!
I came across this twrp guide: [TWRP][3.6.0-11-b7][instantnoodle]TWRP for OnePlus 8/8Pro ][OFFICIAL][BETA] and unlike the other I had used, this one didn't warn against flashing and only booting. I flashed the img for twrp-op8-3.6.0_11-infected-b4 to recovery_a and recovery_b and booted into recovery. At first it just said I was in fastboot, it didn't give me all the usual twrp options, and the only buttons were to reboot and to switch between fastboot and adb (which did nothing, it stayed in fastboot). I tried to reboot to edl and ended up back at the fastboot screen. From here I tried again to boot into recovery and this time I got all the usual twrp options. I rebooted into edl and was able to successfully unbrick with the 10.5.7 MSM. Flashed the global 10.5.7 MSM and I'm set. Updated to A11 and everything is groovy!