Develop Bugs

Fastboot mode Started - help

So this morning i thought it would be a great idea to revert back to stock.
i was following the KDZ lg flash tool however while it was flashing (got to about 2%) i stupidly knocked the phone and the usb cable came out....
so now when i turn my phone on it goes to a black screen with
Fastboot mode started
---reset---
---port charge--
i have tried going into download mode again but it still goes into this fastboot mode.
i found a lot of threads on this such as
http://forum.xda-developers.com/lg-g3/help/tutorial-fixing-fastboot-mode-started-t2995854
this got me to install adb/fastboot which i did via
http://forum.xda-developers.com/showthread.php?t=2588979
however when i try and run through fastboot it just comes up as waiting for device
i have attempted to install lg drivers for this but still nothing.
inside device manager it comes up as
other devices - android?
so clearly the computer is recongnising it, i just need a better driver.
I have the ldf ready to go, if only i could get it to recognise the fastboot command...
anyone able to help, i realise there is a lot of information on the web for this, after extensive research everyone seems to suddenly get into download mode each time. which is something i cannot go. and no recovery doesnt work either.
other things to note, just to save questions..
i am running LG D855 16gb.
when i attempt to go into recovery it comes up with the option to wipe device, but when i follow through menu comes back to fastboot mode started.
i attempted to install lg pc suite in hope that it would suddenly pick up the device and go through the fix upgrade errors (to no luck)
so to clarify, i cannot get into recovery, or download mode. my screen is sat on fastboot mode started.
i am running windows 8.1 although i have attempted to plug into a laptop with ubuntu but same story.
any suggestions? i have also seen a through about jtag...but i dont have any screwdrivers at this point so trying to avoid that.
thank you for reading, kind regards

Anyone out there that has any idea on how to fix?
im convinced i just need to turn the "other device - android" into something that can be recognised by adb, but other then the stock lg drivers i dont have anything else.
help?

FIXED - figured it out, i plugged it into ubuntu again and noticed that when it was connected it came up under fastboot with "accepting commands"
i then put my laf.img file into my home folder and
opened terminal
sudo su <enter>
fastboot boot laf.img
phone then went into download mode
as i didnt have any tools installed on ubuntu i then unplugged and plugged into my windows laptop and ran LG Flash tool 2014 and flashed my kdz.
hope this helps anyone who has the problem in future

[Brick] Zenfone 2 ZE551ML 4GB/32GB

Hello,
I've bricked my phone and now it just turns on to bootloader, all options in bootloader except turn off just loops it back to bootloader where it says "continue the fastboot process".
I've download the xFSTK_ZE551ML but it won't install the moorefield driver it detect it for only a few seconds and then change to android-phone driver, i believe moorefield doesn't work on bootloader but i can get the phone to hang on something else.
I also can't acess via ADB, when i type adb devices, no device is found.
Also tried the Asus FlashTool, but the raw files i tried (WW_ZE551ML_2.15.40.13_20150506.RAW) didn't work, i believe because it's Android L and phone was on Android L.
I've searched alot but haven't found a solution, can someone point me in the right direction?
Thanks in advance.

What happens when you type "fastboot devices"?

Nothing happens with that command.
It's working now, after i tried several raw files, it worked with "WW_ZE551ML_2.20.40.194_20160713.raw".
I know it's sounds newbie since i've just oppened the thread, but it literaly spend all day yesterday following guides and installing stuff on my pc, anyway glad it's apparently solved.
Anyone stuck on bootloader like i was that can't use xFSTK_ZE551ML, install the "WW_ZE55t1ML_2.20.40.194_20160713.raw" with flash tools, this was the only one that worked for me.

Just a warning to anyone who visits this thread --- If you have bootloader-- DO NOT use xFSTK -- xFSTK is to install a temp bootloader to bricked devices and only used if you have NO bootloader .

Locked bootloader by mistake, can't use the phone now

Hey all,
I just got a OnePlus 5T and because I needed a specific system language I decided to flash a custom ROM. I unlocked the bootloader, flashed Derpfest on it and it was all good until I made a mistake. From the Developers options I unchecked "OEM Unlocking" and then when I restarted into the bootloader I did a fastboot oem lock
Now the phone says it's corrupted and it won't boot. Since it's bootloader is locked I can't unlock it, I can't go into recovery and I can't start the phone. Is there anything else I can do to get it back? I don't care about wiping everything at this point, I'm just trying to get it back to a working state.
I want to add I did try the Unbrick tool https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012 but I am getting stuck at the drivers. Windows won't see QHUSB_BULK in device manager and I don't see anywhere else where the driver for the phone might be. I do see the device when doing fastboot devices but again, can't see what drivers is using.
Thanks!

Emo113 said:
Hey all,
Since it's bootloader is locked I can't unlock it, I can't go into recovery and I can't start the phone. Is there anything else I can do to get it back? I don't care about wiping everything at this point, I'm just trying to get it back to a working state.
I want to add I did try the Unbrick tool https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012 but I am getting stuck at the drivers. Windows won't see QHUSB_BULK in device manager and I don't see anywhere else where the driver for the phone might be. I do see the device when doing fastboot devices but again, can't see what drivers is using.
Thanks!
Click to expand...
Click to collapse
The unbrick tool is your best bet, what you need to do is follow the instructions. If its windows 10, you can go to device manager and update drivers from there. Make sure you are logged in as admin. Also some antivirus don't like the MSM tool so you may need to disable that.
Ensure the sequence is right. Connect usb wire to computer, press volume up, connect usb c to phone. Some ppl have tried pressing both volume up and down at the same time to make it work (same way as resolving Sahara error). If it boots first thing you need to do is back up efs.
Second you need to run these commands
adb shell
su
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
exit.
It will save the persist.img on your phone internal memory. Save this as well as efs somewhere safe. Also share the persist.img with me cause I need it for the OPlus 5t for my phone.
Hope it helps

sn809 said:
The unbrick tool is your best bet, what you need to do is follow the instructions. If its windows 10, you can go to device manager and update drivers from there. Make sure you are logged in as admin. Also some antivirus don't like the MSM tool so you may need to disable that.
Ensure the sequence is right. Connect usb wire to computer, press volume up, connect usb c to phone. Some ppl have tried pressing both volume up and down at the same time to make it work (same way as resolving Sahara error). If it boots first thing you need to do is back up efs.
Second you need to run these commands
adb shell
su
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
exit.
It will save the persist.img on your phone internal memory. Save this as well as efs somewhere safe. Also share the persist.img with me cause I need it for the OPlus 5t for my phone.
Hope it helps
Click to expand...
Click to collapse
Thanks for the help! I ended up finding a different Windows PC with no memory of the drivers for this phone so I was able to install them in the correct order and then run the MSM tool to get the phone back to stock Oreo. From there I unlocked the bootloader again to install TWRP and then my custom ROM.

Emo113 said:
Thanks for the help! I ended up finding a different Windows PC with no memory of the drivers for this phone so I was able to install them in the correct order and then run the MSM tool to get the phone back to stock Oreo. From there I unlocked the bootloader again to install TWRP and then my custom ROM.
Click to expand...
Click to collapse
That is superb. If you could do the other bit I would really appreciate it.
Thanks

sn809 said:
That is superb. If you could do the other bit I would really appreciate it.
Thanks
Click to expand...
Click to collapse
Hey there, sorry I totally mis-read the last part of your original post as something that I should do and I didn't see that you need that. Since I used the MDM tool I didn't bother to try your way first and since the phone wasn't mine to keep I already gave it to the owner so I don't have access to it anymore.
Again, very sorry about that.

No dramas. I also got it from some one else who was kind enough to lend it to me and let me root it and wipe it clean and then get the file and start using his phone again.
Thanks

How to UNBRICK?

Hi, everybody
I had the brilliant idea to try to re-lock the bootloader after installing a custom ROM, now my Acquaris X Pro is bricked. ?
I realized that the only way to resurrect it is to use Qualcomm Flash Image Loader (QFIL) by loading the original firmware. The software starts and reveals the Qualcomm HS-USB Diagnostics 900E (COM3) interface and asks me to load the contents.xml file of the programmer.
I then downloaded the latest firmware from the official https://www.bq.com/en/support/aquaris-x-pro/support-sheet page and unpacked the archive, where I found the contents.xml file which I then uploaded to QFIL.
The status window indicates that the prog_emmc_firehose_8953_ddr.mbn file is missing and is trying to load from the BOOT.BF.3.3 folder, which clearly is not present. So I looked for this online and found the folder to download on a Git repository (https://git.szzt.com/yixing/ticai_src). I downloaded the folder and placed it in the path where QFIL expects to find it. I then reloaded the contents.xml file and it reports me the lack of an additional file: rawprogram_unsparse.xml belonging to a certain folder MSM8953.LA.3.0.1.
Unlike the first one, I can't find this last folder online. Can someone help me? ?

Hi @fede91it,
Sorry for the late answer - I have been quite inactive on xda recently
Unfortunately I don't have a solution for you right away, but I got a working X Pro with stock rom (+twrp and magisk) and a bit of experience with the "standard" tools like adb and fastboot. Never worked on such a low level like you though.
Does the tool you mentioned (QFIL) offer the possibility to grab contents from the phone instead of downloading it to it?
Maybe we can get the missing data from my phone?
Sorry for the dump/obvious question, but: What happens in the current bricked state when you turn the phone on? You can't enter fastboot and unlock..?
Another approach: have you tried contacting BQ? Maybe via their forum https://www.mibqyyo.com/. Possibly the missing files are device specific and you would need bqs help..

Thanks for your answer.
I have contacted BQ but they no longer deal with Android phones, I have no support from them.
As for you, thanks for your availability, but the files I'm looking for are for development and don't end up on my phone, so it's impossible to try to extract them from your phone.
By now I've changed phones and kept the Bq as a paperweight brick

fede91it said:
Thanks for your answer.
I have contacted BQ but they no longer deal with Android phones, I have no support from them.
As for you, thanks for your availability, but the files I'm looking for are for development and don't end up on my phone, so it's impossible to try to extract them from your phone.
By now I've changed phones and kept the Bq as a paperweight brick
Click to expand...
Click to collapse
Hey, did you recover your paperweight? I'm in the same situation but with the BQ X PRO

I could not solve it. There are some files missing for the compilation, and I can't find them

Have you tried this method by only using the firehose? forum.hovatek.com/thread-31505.html

Hey, did you recover? I made the same mistake as you. I managed to repair ...
What I did was:
- I removed the battery cable (I did not remove the battery completely)
- I pressed on VolDown button and connected the phone via usb to the pc and immediately went into fastboot mode
- I opened the BQ app on the pc, I loaded the rom and put it to install the rom. It asked to unlock the bootloader (which is what we want) ... The ROM could not be flashed, but it is not important ... As soon as you unlocked the bootloader, the phone started up without a problem

fede91it said:
Hi, everybody
I had the brilliant idea to try to re-lock the bootloader after installing a custom ROM, now my Acquaris X Pro is bricked. ?
I realized that the only way to resurrect it is to use Qualcomm Flash Image Loader (QFIL) by loading the original firmware. The software starts and reveals the Qualcomm HS-USB Diagnostics 900E (COM3) interface and asks me to load the contents.xml file of the programmer.
I then downloaded the latest firmware from the official https://www.bq.com/en/support/aquaris-x-pro/support-sheet page and unpacked the archive, where I found the contents.xml file which I then uploaded to QFIL.
The status window indicates that the prog_emmc_firehose_8953_ddr.mbn file is missing and is trying to load from the BOOT.BF.3.3 folder, which clearly is not present. So I looked for this online and found the folder to download on a Git repository (https://git.szzt.com/yixing/ticai_src). I downloaded the folder and placed it in the path where QFIL expects to find it. I then reloaded the contents.xml file and it reports me the lack of an additional file: rawprogram_unsparse.xml belonging to a certain folder MSM8953.LA.3.0.1.
Unlike the first one, I can't find this last folder online. Can someone help me? ?
Click to expand...
Click to collapse
Hello! Maybe it's too late, but I have the same problem as you and I found this post that talks about our mobile! In it you can find a lot of information, but also the links to download the stock ROMs and the flashing tool to get back to the factory Rom and unbrick the phone! I leave you the links below! Hope it also helps others with the same problem as we! Greeting
Post:
[HOW-TO] BQ Aquaris X Pro | [Stock-ROM] Unlock,Recovery,Root,Upgrade (TWRP/Magisk)
Hi everyone. :) This Post (post #1) shows the complete process of unlocking, flashing, rooting etc. in general, it may refer to old firmware and/or tool versions but the steps remain the same for newer versions. The chapters rely on each other...
forum.xda-developers.com
Link of stock ROMs and the flashing tool:
Support - Aquaris X Pro
web.archive.org

Hi,
Have you ever successfully got it to work again?
Thanks

rufus.wilson said:
Hi,
Have you ever successfully got it to work again?
Thanks
Click to expand...
Click to collapse
Hi,
I managed to get everything working properly.
I installed the Lineage OS custom rom and it works 5 *, with a custom rom you should not block the boot loader, it was the mistake I made.
The solution I used I described 2 comments above

MigSantosPT said:
Hi,
I managed to get everything working properly.
I installed the Lineage OS custom rom and it works 5 *, with a custom rom you should not block the boot loader, it was the mistake I made.
The solution I used I described 2 comments above
Click to expand...
Click to collapse
Hi,
Ah ok.
Just opened it, disconnected the battery. While pressing down VOL- button, I connected it to USB.
Nothing happens on the phone screen. I don't even see the blinking red light now.
Device manager shows it as 9008 COM port.
BQ flash tool doesn't recognise the phone.
I previously installed BQ drivers and rebooted.
Any other suggestions, before I close it back?

rufus.wilson said:
Hi,
Ah ok.
Just opened it, disconnected the battery. While pressing down VOL- button, I connected it to USB.
Nothing happens on the phone screen. I don't even see the blinking red light now.
Device manager shows it as 9008 COM port.
BQ flash tool doesn't recognise the phone.
I previously installed BQ drivers and rebooted.
Any other suggestions, before I close it back?
Click to expand...
Click to collapse
It is strange because it usually shows something on the screen right away ... Pressing the Power button also does not appear anything?
Did you install the ADB drivers? After the ADB drivers are installed, the BQ program recognizes the smartphone
and it also opens doors to use the command line to do almost anything.

rufus.wilson said:
Hi,
Ah ok.
Just opened it, disconnected the battery. While pressing down VOL- button, I connected it to USB.
Nothing happens on the phone screen. I don't even see the blinking red light now.
Device manager shows it as 9008 COM port.
BQ flash tool doesn't recognise the phone.
I previously installed BQ drivers and rebooted.
Any other suggestions, before I close it back?
Click to expand...
Click to collapse
the number 9008 sounds like the EDL mode and NOT the wanted fastboot mode which is required by the usual way of flashing via bq tool or fastboot/adb tools.
What is EDL Mode and How to Boot your Qualcomm Android Device into it
Android phones and tablets equipped with Qualcomm chipset contain a special boot mode which could be used force-flash firmware files for the purpose of unbricking or restoring the stock ROM.
www.thecustomdroid.com
sorry, no solution, only confirming..

Question [SOLVED] Hard bricked device, blackscreen no response

Sup boys i am scared like a mf right now.
EDIT: Forgot to mention Blankflash doest work either,
FAILED: qb_flash_singleimage()->device_open()->error opening device
So to explain the situation i used the Corvus OS GSI and its been due for a update for a while. Today i updated it with OTA.
It didnt boot, no worries GSI didnt work for me without clearing userdata, so i did that and it booted.
Now for setting up magisk i saw it had an install after OTA option, and i did that thinking it was a neat little feature, pressed Reboot
And it shut down, black screen, no response from any buttons, no response from charging, no fastboot or adb devices show up on my laptop.
Its like the motherboard suddenly died.
I have backups for everything so i am not interested in getting anything from the device, but getting the money for another phone would be a pain.
Second edit and solution:
For the probably one other guy using Linux out there, blank flash wont work, use windows and install LMSA to get the correct driver.

You can try looking into restoring your phone using Blankflash. Look for guides here on XDA or on Tg.
IF you can see your device listed in the Device Manager on PC, you can probably still save it.
And for the love of of god, NEVER update a GSI with OTA, it will never work.

Kuntitled said:
You can try looking into restoring your phone using Blankflash. Look for guides here on XDA or on Tg.
IF you can see your device listed in the Device Manager on PC, you can probably still save it.
And for the love of of god, NEVER update a GSI with OTA, it will never work.
Click to expand...
Click to collapse
qboot seems to see it but refuses to flash it, and also no OTA, noted.

KAN7A said:
qboot seems to see it but refuses to flash it, and also no OTA, noted.
Click to expand...
Click to collapse
So what did you figure out? I have the same affliction. Whether it's qboot, QTSP, fastboot or adb, it just isn't wanting to make a connection in order to flash anything.

treysky54 said:
So what did you figure out? I have the same affliction. Whether it's qboot, QTSP, fastboot or adb, it just isn't wanting to make a connection in order to flash anything.
Click to expand...
Click to collapse
First use windows, install Lenovo Rescue and Smart Assistant, this installs the correct drivers.
Reboot your PC to make sure the drivers are loaded.
And Follow the blankflash instructions aka just run the BAT file in CMD.
It will say its waiting for a device.
After that press Volume Down and Power On at the same time and remove the USB cable from the phone and insert it again and again until qboot starts to flash it (dont remove the cable too fast so you dont miss it).
This is what worked for me and i did il like a few nights ago.
You want to make sure you grab the right Blankflash too and all that.
But if your phone boots aka starts you dont really need blankflash you just have not setup something correctly or the cable itself is faulty or does not support data transfer.

KAN7A said:
First use windows, install Lenovo Rescue and Smart Assistant, this installs the correct drivers.
Reboot your PC to make sure the drivers are loaded.
And Follow the blankflash instructions aka just run the BAT file in CMD.
It will say its waiting for a device.
After that press Volume Down and Power On at the same time and remove the USB cable from the phone and insert it again and again until qboot starts to flash it (dont remove the cable too fast so you dont miss it).
This is what worked for me and i did il like a few nights ago.
You want to make sure you grab the right Blankflash too and all that.
But if your phone boots aka starts you dont really need blankflash you just have not setup something correctly or the cable itself is faulty or does not support data transfer.
Click to expand...
Click to collapse
Yeah it seems getting the button pushes right was the hardest part for me. Your button/plug idea is far superior, very nice.

treysky54 said:
Yeah it seems getting the button pushes right was the hardest part for me. Your button/plug idea is far superior, very nice.
Click to expand...
Click to collapse
Its hard to time things righ with a blank screen and no other feedback lol
That felt more natural and I am glad it helped!