Develop Bugs

lg g3 bricked shows qdloaderboard diag says ap check failed device not in dwnld mode

i rooted my lg g3 d 855 lollipop and tried to install TWRP
but it was not a success i lost recovery + download mode but it boots perfectly into android system and can use it normally
to install twrp again i tried to flash it again and again but no success
then i flash aboot.img and it all went blank not booting not rrecovery etc
i tried board diag method to unbrick it shows up in my system as qcomm hs usb 9008
but when using board diag it says DEVICE NOT FOUND IN DLOAD MODE
plz help this is my first android phone after months of hardwork
i dont think i have enough money to replace the mobo or buy a new one:crying:

Hello,
it's recoverable, but you need to read and some knowledge...
Refer to this thread. Proceed point by point and use willcracker boarddiag.

halekhonza said:
Hello,
it's recoverable, but you need to read and some knowledge...
Refer to this thread. Proceed point by point and use willcracker boarddiag.
Click to expand...
Click to collapse
brother i used board diag method it is succesfully able to show my device as qcomm hs usb 9008
and im able extract the files with program
but when i click start after some time it says ap check failed ,device not found in dload mode
i desperately need ur help IM NEW TO XDA FORUMS I HOPE ANYONE WOULD BE ABLE TO SOLVE PROBLEM
tnx in advanc

adilismail62 said:
brother i used board diag method it is succesfully able to show my device as qcomm hs usb 9008
and im able extract the files with program
but when i click start after some time it says ap check failed ,device not found in dload mode
i desperately need ur help IM NEW TO XDA FORUMS I HOPE ANYONE WOULD BE ABLE TO SOLVE PROBLEM
tnx in advanc
Click to expand...
Click to collapse
I understand. I'm just asking if you really using right boarddiag (thread that I mentioned - willcracker.rar)
Also be sure that you have a phone connected to right port (check it in device manager)

halekhonza said:
I understand. I'm just asking if you really using right boarddiag (thread that I mentioned - willcracker.rar)
Also be sure that you have a phone connected to right port (check it in device manager)
Click to expand...
Click to collapse
halekhonza said:
I understand. I'm just asking if you really using right boarddiag (thread that I mentioned - willcracker.rar)
Also be sure that you have a phone connected to right port (check it in device manager)
Click to expand...
Click to collapse
yes im using the r8 port it shows in device manager and in board daig also i gave port 14
before my phone was going to get bricked its battery was low
is it affecting the procedure i think my battery is not charging
when i remove battery and connect to pc phone shows battery not inserted sign when i insert the batery it disappear and no sign of charging
i thought this might help:good:

You have to use the original LG usb cable. Dont try with fake china cables because its a lot possible to have troubles with them.

Lumia 820 bricked NEED HELP please

my lumia 820 bricked ,connect to pc is showed below ; how to fix it

you tried Windows Device Recovery Tool?
http://go.microsoft.com/fwlink/p/?LinkId=522381

dxdy said:
you tried Windows Device Recovery Tool?
http://go.microsoft.com/fwlink/p/?LinkId=522381
Click to expand...
Click to collapse
i'm tried WDRT,cmd prompt methods and wpinternals but didn't show my lumia ,any other idea to recover my lumia

plz help.... any idea about this

Gokul Rajan said:
plz help.... any idea about this
Click to expand...
Click to collapse
USE THIS AS STARTING POINT!!!
I once bricked a LG Leon and the solution to pc not recognizing the device was pinning the motherboard so the pc recognizes the qualcomm and you would be able to flash it, something like this:
Pinning

xxJMarian said:
USE THIS AS STARTING POINT!!!
I once bricked a LG Leon and the solution to pc not recognizing the device was pinning the motherboard so the pc recognizes the qualcomm and you would be able to flash it, something like this:
Pinning
Click to expand...
Click to collapse
how to reinstall qualcumm bootloader?

Gokul Rajan said:
how to reinstall qualcumm bootloader?
Click to expand...
Click to collapse
You need something like boardiag as shown in the video and some files to flash it, once you do the pinning and the pc recognizes the device, you will be able to flash it, you need some specific files. As far as i remember i had some folders with files with some LG models, G2, G3, etc... you need to find all the files compatibles with your device, i would suggest you first try everything to make it work without the pinning step, if you don't succeed then start thinking about this step, you can also try to do it without flashing the qualcomm, once your pc recognizes the device you might be able to recover it with WDRT without having to flash the qualcomm. Sadly, i cannot provide you with a full tutorial (including must dos if something goes wrong) because i don't have the required experience to do so.

Scatter file for E5603, E5663, ... Mediatek MT6795 Xperia M5

I played a bit around and extracted the E5603 Scatter file from my phone and converted it with MTK Studio. I hope this will help some of you

freeskyler said:
I played a bit around and extracted the E5603 Scatter file from my phone and converted it with MTK Studio. I hope this will help some of you
Click to expand...
Click to collapse
How did you do this??
Let me know
Tell me step by step method in order to get E5663 SCATTER

altmash mirza said:
How did you do this??
Let me know
Tell me step by step method in order to get E5663 SCATTER
Click to expand...
Click to collapse
I could not send the firmware.info through message
I zipped it and attached there please use it
Thnks for your efforts:angel:

Alright, the output is the same like on the E5603. So the Scatter file is based only on the Mediatek MT6795 Chipset. I will change the Thread topic that all that need the scatter file can find it here.
I really would like to test a briked phone, to unbrick it. May someone would send me for this a bricked Xperia M5?

freeskyler said:
Alright, the output is the same like on the E5603. So the Scatter file is based only on the Mediatek MT6795 Chipset. I will change the Thread topic that all that need the scatter file can find it here.
I really would like to test a briked phone, to unbrick it. May someone would send me for this a bricked Xperia M5?
Click to expand...
Click to collapse
Your work is good for many peoples who bricked there phones
Peoples who are going to try this
I have an advice for them
Sp flash tool also has an option for battery
As with battery, without battery
You can try with chek and unchek them
Cause m5 has non removable battery

Scatter does not download to phone...
[/COLOR]
freeskyler said:
I played a bit around and extracted the E5603 Scatter file from my phone and converted it with MTK Studio. I hope this will help some of you
Click to expand...
Click to collapse
That's a great starting point !!! Thanks indeed for that scatter file!
Anyway, SP Flashtool does not download the scatter to the bricked M5.
It keeps trying but never gets to the progress bar that should appear.
I followed this guide:
https://forum.hovatek.com/thread-159.html
The phone appear as "USB Serial Device (COM42)" in the device manager. And meanwhile, the "Mediatek PreLoader USB VCOM Port (COM26)" remains unchainched.
After a while, the "USB Serial Device" disappears again from the Device manager - but nothing at all happens in SP Flashtool.
Any useful hint???

There are a lot other MTK Tools that you can try to use like S-Droid toolkit 2.5. Its really not easy to manage all this. there are much .ini files like in SP Flashtool that could be tweaked to recognize our phone probebly. I just made a manualle partition backup of my phone and play now a bit around

freeskyler said:
There are a lot other MTK Tools that you can try to use like S-Droid toolkit 2.5. Its really not easy to manage all this. there are much .ini files like in SP Flashtool that could be tweaked to recognize our phone probebly. I just made a manualle partition backup of my phone and play now a bit around
Click to expand...
Click to collapse
I believe that the problem is, that my bricked M5 is only identified as "USB Serial Device", and Windows connects it to its native driver. However, it should appear as "mediatek Preloader Usb Vcom", according to http://www.yomitech.com/2015/04/how-...preloader.html
So MTK-Tools do not recognize that this the device that they are supposed to flash to... or maybe they are unable to use this windows interface and are looking for a device connected over the MTK VCOM interface driver. However, this does not happen...
I have not found any way to disable or uninstall that Windows naitive driver or any other way to make Windows connect the M5 through the VCOM Driver.
Any hint?

Updated the scatter file, seems there were some errors on it. now it should be correct.

I watched a bit around the logfiles from MTK Droid Sp Flashtool etc. It seems, that wen need yaffs2 support in the kernel, for that the tools can read correct our device.
Im a beginner of compiling a kernel. There are still some erors in my build environment.
Maybe here is someone who could compile the kernel with yaffs2 support?

Some update progress.... MTK Droid Tools
- Use SeLinuxModeChanger to set SeLinux mode to permissive.
- Use adbd insecure app
Now connects the phone correctly and the field gets green
Sadly the DTK Droid crashes when I start the backup and I get the error message that the sd card couldnt be find.

Scatter file for E5633
freeskyler said:
Updated the scatter file, seems there were some errors on it. now it should be correct.
Click to expand...
Click to collapse
Hello,
My device is E5633 and i need a scatter file for that also,,,, anyone help me please :crying::crying::crying:

nasarino4978 said:
Hello,
My device is E5633 and i need a scatter file for that also,,,, anyone help me please :crying::crying::crying:
Click to expand...
Click to collapse
Apparently, the Scatter-file is the same. If you device is bricked, just try that one out... anyway the device can't be more bricked.
I tried - but I did not succeed. SP Flash tool did just not download the information to the phone, even though the drivers were installed correctly and the phone was recognized as Mediatek USB port on the computer.
If you succeed, please let us know how you did!

diegopanther said:
Apparently, the Scatter-file is the same. If you device is bricked, just try that one out... anyway the device can't be more bricked.
I tried - but I did not succeed. SP Flash tool did just not download the information to the phone, even though the drivers were installed correctly and the phone was recognized as Mediatek USB port on the computer.
If you succeed, please let us know how you did!
Click to expand...
Click to collapse
It didn't work for me, i tried the scatter file with the SP Flash Tool and nothing happened when i pressed on Download i had chosen the android file and nothing changed.
Any suggestions .....

Test point in Xperia M5
nasarino4978 said:
It didn't work for me, i tried the scatter file with the SP Flash Tool and nothing happened when i pressed on Download i had chosen the android file and nothing changed.
Any suggestions .....
Click to expand...
Click to collapse
Please can anyone help me about the test point in Xperia M5 and how to use s1tool and if there are any files to be added in this application.
I had the set of tools attached here in other topic but i tried to figure out about the test point and i couldn't know what to do ?
hope to have some assistance about that ????? :crying::crying::crying:

nasarino4978 said:
It didn't work for me, i tried the scatter file with the SP Flash Tool and nothing happened when i pressed on Download i had chosen the android file and nothing changed.
Any suggestions .....
Click to expand...
Click to collapse
that it's because you don't have linked the files that are described in the scatter file.
i flashed a zte smarthphone in the past and the scatter file is only a map for the memory adress of the files that you could have , but i don't see any similar in the firmwares that i have downloaded , and yes i have a bricked M5 too .
i hope that the efforts of the comunity works, and one day all the red lights dissapear xD
sorry for my english , i hope that you understand

LG-K430T and Sp Flash Tool

Hey!
I have a K10 2016 phone (K10 LTE, reported as K430T, motherboard k430ds), which I bricked, but I "resurrected" it doing circuit-bridge.
Now my phone get recognized by PC, but as "0E8D:0003" under Device Manager. But LGUP, or even Uppercut doesn't seem to recognize it for proper flashing.
I installed all the known drivers: VCOM drivers, Mediatek USB drivers, for Windows 10 x64 with driver signature off.
I downloaded latest SP Flash Tools 5.1728 from here and a scatter file for chipset MT6753 here.
I have LG stock rom for the model 2016 (named K430T10b_01_0805.kdz) and extracted it using KDZ Extract.
I got all the necessary files (preloader, lk, boot, recovery, logo, secro, tee1, tee2 and system) from the KDZ rom.
I loaded scatter file into SP Flash Tools.
Then, clicked "recovery" and browse to the extracted recovery_190464.bin file, loaded OK, then preloader was autoloaded also. Ticked both and set SP to "Firmware upgrade".
But when I click "Download", an error appears, saying S_AUTH_IS_NOT_READY (5000), refering to a secure base-band chip, and needs an "authentication file first".
This is where I get lost. I don't really know what a secure base-band chip means, I know latest Mediatek chipsets are 64bits architecture, and latest SP Flash Tool can handle 64bits well, and, that they're already encrypted or have some kind of encryption.
So I downloaded an (I think) generic auth file from here, loaded it and then pressed "Download" again, with scatter, preloader, recovery and "Firmware upgrade" settings.
But then, inmediately, this message appears: "ERROR : S_SECURITY_SEND_AUTH_FAIL (6029) , MSP ERROE CODE: 0x00 [HINT]:" and then pressed OK, and don't know what else to do.
I tried FWUL but is too dificult, Linux doesn't even recognize any other usb plugged into it.
Help please! Thank you

HELP
I am with the same problem I would like to find a solution because I am without cell phone now.

I had fallen into same situation. It's due to signature verification fail as we can understand from the error text. Thanks to LG, they didn't share any authentication file which could help us to flash something through SP Flash tool (though they didn't enable it). In fact, if they wanted us to be able to flash something unofficial, they would let dm-verity go when we unlock the bootloader...
You have to either disassembly the emmc of your mother board and re-write whole stock partitions or directly replace the mother board.
I tried something similar to first option. I soldered emmc pin-outs to card reader in order to be able to see the partitions of the emmc on my pc. It didn't work actually. When I plug in the usb, the phone is recognized as MTK Serial Com while it was recognized as LGE Serial Com right before I soldered the card reader. When pc recognizes the device as MTK Serial Com, SP Flash tool is able to write/flash something but as I said above, security measures doesn't let it to do.
If you happen to ask that how I fixed it, I sent my phone to official LG Service saying that it had suddenly turned off while installing stock firmware via LG Bridge.
Update 7th March 2018: They replaced my K10 with LG G4 in 1st March.
Good luck whoever faces this damn...

You may have to deal with seccfg and NVRAM as well, or at least that was what I can attest with secure MTK SoCs like the MT8127. For the heck of it, have you tried flashing using SP Flash Tool 5.1532? The phone may not even work after flashing but let me know if it makes any difference. What I know is that there is a quirk with said version where unsigned images can be fed on a secure device.
There is also a tool by MTK for signing images through Linux but I dunno if it supports MT67xx-series chips.

panchowatkins said:
Hey!
I have a K10 2016 phone (K10 LTE, reported as K430T, motherboard k430ds), which I bricked, but I "resurrected" it doing circuit-bridge.
Now my phone get recognized by PC, but as "0E8D:0003" under Device Manager. But LGUP, or even Uppercut doesn't seem to recognize it for proper flashing.
I installed all the known drivers: VCOM drivers, Mediatek USB drivers, for Windows 10 x64 with driver signature off.
I downloaded latest SP Flash Tools 5.1728 from here and a scatter file for chipset MT6753 here.
I have LG stock rom for the model 2016 (named K430T10b_01_0805.kdz) and extracted it using KDZ Extract.
I got all the necessary files (preloader, lk, boot, recovery, logo, secro, tee1, tee2 and system) from the KDZ rom.
I loaded scatter file into SP Flash Tools.
Then, clicked "recovery" and browse to the extracted recovery_190464.bin file, loaded OK, then preloader was autoloaded also. Ticked both and set SP to "Firmware upgrade".
But when I click "Download", an error appears, saying S_AUTH_IS_NOT_READY (5000), refering to a secure base-band chip, and needs an "authentication file first".
This is where I get lost. I don't really know what a secure base-band chip means, I know latest Mediatek chipsets are 64bits architecture, and latest SP Flash Tool can handle 64bits well, and, that they're already encrypted or have some kind of encryption.
So I downloaded an (I think) generic auth file from here, loaded it and then pressed "Download" again, with scatter, preloader, recovery and "Firmware upgrade" settings.
But then, inmediately, this message appears: "ERROR : S_SECURITY_SEND_AUTH_FAIL (6029) , MSP ERROE CODE: 0x00 [HINT]:" and then pressed OK, and don't know what else to do.
I tried FWUL but is too dificult, Linux doesn't even recognize any other usb plugged into it.
Help please! Thank you
Click to expand...
Click to collapse
Could you tell me how you did the circuit-bridge? in which pin of the motherboard?
Sorry for my english

Dear members of the forum. Who knows how to restore TA? was flashed with firmware k430ds11i lowered by k430ds11k TA died (Brick) It is not determined by anything! Who can tell me what? And if there is a possibility? share loader k430ds11i.img

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..