[HARDBRICK] D855; Boarddiag & flashtool not working - G3 Q&A, Help & Troubleshooting

I'm fixing a D855 model which I hardbricked by accident. This is what I tried so far but still unsuccessful:
1. I used the method which involved shorting the pins in order for my PC to detect it as Qualcomm USB QDloader (something). I used the BOARDDIAG v2.99c as it's the only version that could detect my phone connected. Newer versions doesn't seem to work. I flashed all the partitions, even the userdata and system (which the tutorial doesn't recommend as it takes very long; it took me more than 12 hrs+). After flashing the sli, which is supposed to be flashed last, my phone boots to kernel panic mode. From this point, my phone can be seen as LGE androidnet port (COM41) (sorry I'm just typing this from memory)
2. From the kernel panic mode, I used the LG flash tool to flash a D855 TOT and a LG8974.dll. However, it still cannot detect my phone model. IMEI and PID still comes out as null. Back to #1, the reason I also flashed userdata and system partition because flash tool still cannot detect my phone. I was hoping to boot it up using the 1st method but it keeps on throwing it to kernel panic mode.
Any suggestions how to revive my LG G3?

hey, i have the same issue, did you find any sulotion?

Related

[HELP] G3 Hardbrick Help! URGENT!

Here's my case:
I've got a LG G3 F400L (Korean LGU Variant), its on Marshmallow(6.0), and for all I know I used the Autorec program for Lollipop, and apparently got my bootloader corrupted; No led flashing, no display. But the Qualcomm 9008 serial port is shown on the device manager and I can use Boardiag to detect it. I know, irony and idiocy made this dilemma.
Diagnostics:
I've used Boardiag 2.99a by willcracker and yes I've checked "AP check" and "EMMC TEST" and both are tagged as "Pass", but when it comes to the "SDRAM TEST" it throws off an error indicating that there is a flash error on partition "boot" along with a 0x3000 and I can't progress beyond that, I've also tried to use the "Restore Device" option to revive it but still the later error still persists.
I've also tried Smart Boot Diagnostics but the problem is that my device's AP Chip doesn't exist on the current version of the tool.
What I would like to press on:
I would want to resolve this on my own and that no amount of suggesting on sending this to the service center would yield fruit. Please do understand, I would also like this to be a thread that can help me and other on resolving their corrupted bootloader units.
Please, can someone help me on my dilemma. Thank you very much. Any amount of help is appreciated.
Try using board diag with the battery unplugged.
Sent from my SM-G935T using Tapatalk
Already tried that but still nothing works.
Current situation:
Alas, I've accessed fastboot and had wiped the boot partition, but now the USB is detected as "LGE AndroidNet USB Serial Port."
FeitX said:
Already tried that but still nothing works.
Current situation:
Alas, I've accessed fastboot and had wiped the boot partition, but now the USB is detected as "LGE AndroidNet USB Serial Port."
Click to expand...
Click to collapse
You need to short with a cable internet connection I do this last night and changes for Qalcomm USB in the same time...After that, you need to open BoarDiag and do the process. If you canĀ“t enter in download mode, you need in BoarDiag pass the USERDATA
I follow this link: http://open-freax.fr/guide-unbrick-your-lg-g3/

LGE AndroidNet Port Instead Of LGE Mobile USB Port?

I was on a custom rom on my LG G3 D852, and I decided to go back to full stock by flashing the .tot file. I used the tool to flash .tot file, then without rooting and flashing twrp, I upgraded to marshmallow by flashing .kdz file. (I forgot that my twrp recovery was gone) When I was on marshmallow I realized I don't have twrp and root, so I wanted to return to 4.4.2 with the .tot file. The problem is, I couldn't, because the pc doesn't recognize my phone as LGE Mobile USB Serial Port (COM xx) except when my phone is booted up. When I boot into download mode, it changes to LGE AndroidNet USB Serial Port. I read some threads about people hard bricking their phones, and the port changes, but my phone is perfectly fine. It's impossible to do anything at this point, since I am on MM without root and custom recovery. If anyone could help, that would be greatly appreciated. Also, I attached a screenshot from the device manager program. My phone was turned on when the screenshot was taken.
I too have this same problem. Any answers would be nice

how to unbrick dead redmi 1s

I am flashing wrong ROM on my redmi 1s .my phone was not able to switch on ,not charging, no bootloader,no fastboot mode totally crashed. I pressed volup+power,voldown+power not going to any mode.When I connected to PC,it recognized Qualcomm qdloader driver. I am flash to ROM with mi flash tool it recognised COM10 PORT When I flash official stock ROM I got error not flashing.is there any way to flash ROM on my device.I am searched on google I found Qualcomm flash tool,how to flash ROM with Qualcomm flash tool pls help me
naveen3186 said:
I am flashing wrong ROM on my redmi 1s .my phone was not able to switch on ,not charging, no bootloader,no fastboot mode totally crashed. I pressed volup+power,voldown+power not going to any mode.When I connected to PC,it recognized Qualcomm qdloader driver. I am flash to ROM with mi flash tool it recognised COM10 PORT When I flash official stock ROM I got error not flashing.is there any way to flash ROM on my device.I am searched on google I found Qualcomm flash tool,how to flash ROM with Qualcomm flash tool pls help me
Click to expand...
Click to collapse
Man, you are not the only one in this situation, I accidentally erased the f*cking 'tz' partition. If you are on linux, connect the phone to USB, the preloader will find that the whole of the data is messed up and put the phone into bulk mode. In bulk mode, the partitions of the phone is exposed as such so you can copy files into it. DONT DO IT WITHOUT RESEARCH. BUT I AM NOT SURE HOW TO RESTORE IT. If I get tz.img instead of tz.mbn, I will be able to 'dd' it. I dont think I can 'dd' a mbn file.
..
generex144 said:
Man, you are not the only one in this situation, I accidentally erased the f*cking 'tz' partition. If you are on linux, connect the phone to USB, the preloader will find that the whole of the data is messed up and put the phone into bulk mode. In bulk mode, the partitions of the phone is exposed as such so you can copy files into it. DONT DO IT WITHOUT RESEARCH. BUT I AM NOT SURE HOW TO RESTORE IT. If I get tz.img instead of tz.mbn, I will be able to 'dd' it. I dont think I can 'dd' a mbn file.
Click to expand...
Click to collapse
MIflash actually works , just b on new miflash version(which capable of switch 9008-9006 mode)...
it may gives errors many times...
tips to b successfull flash..
1. charge battery with external charger (most imp. )
2.if ur using pc, connect usb to motherboard usb port.( backside ports of cabinet)
3.try changing usb cables (sounds stupid but actually worked for me, as phone wont stay in 9006/9008 mode if usb signal drop)
dd wont work until u have access to fastboot/adb..
another way is make deep flash cable..
dnt wrry its very easy

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

Help me unbrick my LG d722 (G3s)

https://drive.google.com/file/d/1mg8BDBCaoCS_LXE0TBSd5TdKV81YUsCM/view?usp=sharing[/IMG]
Hi guys,
i need some help unbricking my d722.
what went wrong?
I tried to flash twrp with flashify and i ended up in demigodmode.
from there i connected the phone to my computer and like 10 portable drives showed up asking to be formatted. I formatted all except one drive because it was protected from.
After i formatted the drives my phone was dead with only a black screen left.
Since i can't find any .tot firmware files for this model i tried to use the .tot firmware for a g3 in BoardDiag.
but when i want to use the extracted .tot firmware files on my phone it says this:
no response from device, check pmic first and if still boot problem replace ap
i think i have managed to install qualcomm driver and the phone is recognized as a qualcomm when plugged in.
But i did not shortwire the motherboard because i can't find the GND
can anyone please help me fix my phone thank you so much!

Categories

Resources