Develop Bugs

Unbrick help / Need bin. files

Hy nexus friends,
I need help from someone with a 791F 32GB. I dont know if a 790 or a 16gb version is identical.
It would be great if someone with a rooted device can make a backup for me of the bootloader bin files.
aboot, sbl1, rpm, tz, sdi, sbl1b, tzb, rpmb, abootb, misc, laf, persist.
I flashed the hammerhead bootloader and stuck at 9008 mode.
It will be ver great if someone could help me.
Some partition apps could make a backup or with the dd command.
If i fet a solution, i would post it here. At the moment i had the device and the tools that i flashed for test a nexus 5 sbl. So write is possible.
Thanks for help guys

Where can I see if my phone is 791F?

i have the US Nexus 5X 32GB. Tell me what to do and I'll get you what you need.

tacofromhell said:
Where can I see if my phone is 791F?
Click to expand...
Click to collapse
Model number on the phone box and I believe in the bootloader screen: turn off phone then hold volume down and power.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Model number on the phone box and I believe in the bootloader screen: turn off phone then hold volume down and power.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Ok. Just rebooted into bootloader and under "Variant" it says LGH791 but no F, sorry

Thx for your help.
You can backup the partitions with some partition backup apps or with dd.
If you look with a file explorer in /dev/block/platform/soc.0/f9824900.sdhci/by-name/XXXXX , XXXX there are the partiton names.
If you want to copy with adb, make adb shell, su, and then:
dd if= /dev/block/platform/soc.0/f9824900.sdhci/by-name/cmnlib of=sdcard/cmnlib.img
Around 36 partitons are in the MM build. System, cache, userdata are not needed..

konsolen said:
Thx for your help.
You can backup the partitions with some partition backup apps or with dd.
If you look with a file explorer in /dev/block/platform/soc.0/f9824900.sdhci/by-name/XXXXX , XXXX there are the partiton names.
If you want to copy with adb, make adb shell, su, and then:
dd if= /dev/block/platform/soc.0/f9824900.sdhci/by-name/cmnlib of=sdcard/cmnlib.img
Around 36 partitons are in the MM build. System, cache, userdata are not needed..
Click to expand...
Click to collapse
Have you found a solution to get booting again? Been searching and tried multiple methods to repair my boot image on the H791 I own.
I have worked with another XDAer who extracted and now have the bootimage files from several stock H791 files available. They include the GPT from the stock image MDA89E and the boot image files from bootloader-bullhead-bhz10i.img bootloader-bullhead-bhz10k.img and bootloader-bullhead-bhz10m.img. Let me know if you still need these. I see 11 files in the boot image. During some testing I flashed over the sbl1 on my device and lost the ability do anything but go into QUSB DL mode 9008 as well.
As I am writing this I am now wondering if there is a separate set of SBL etc. files for the International variant? We may need to extract from the 791 tot file available the needed files if we do not have another method of obtaining them. Let me know if you have found a workable way to flash the needed boot images in place. Thanks.

nate0 said:
Have you found a solution to get booting again? Been searching and tried multiple methods to repair my boot image on the H791 I own.
I have worked with another XDAer who extracted and now have the bootimage files from several stock H791 files available. They include the GPT from the stock image MDA89E and the boot image files from bootloader-bullhead-bhz10i.img bootloader-bullhead-bhz10k.img and bootloader-bullhead-bhz10m.img. Let me know if you still need these. I see 11 files in the boot image. During some testing I flashed over the sbl1 on my device and lost the ability do anything but go into QUSB DL mode 9008 as well.
As I am writing this I am now wondering if there is a separate set of SBL etc. files for the International variant? We may need to extract from the 791 tot file available the needed files if we do not have another method of obtaining them. Let me know if you have found a workable way to flash the needed boot images in place. Thanks.
Click to expand...
Click to collapse
I'm on the same boat , hope you have something to boot it up
It's been more than 3 weeks, my 5X just brick itself . And LG doesn't support 5X in my country . I'm very very hoping you will find solution.

Apayah said:
I'm on the same boat , hope you have something to boot it up
It's been more than 3 weeks, my 5X just brick itself . And LG doesn't support 5X in my country . I'm very very hoping you will find solution.
Click to expand...
Click to collapse
I think the only way from my perspective so far is to manually flash the needed QComm/boot image/boot loader files with something that can interface with the phone. I am pretty sure I know a method to manually do this but need the flash programmer that works with this device to accomplish. Or if there is a way to add MSM8992 support to the BoardDiag tool, that would work...I have not given up, just have not had a whole lot of time to work on this the past 2 days.

nate0 said:
I think the only way from my perspective so far is to manually flash the needed QComm/boot image/boot loader files with something that can interface with the phone. I am pretty sure I know a method to manually do this but need the flash programmer that works with this device to accomplish. Or if there is a way to add MSM8992 support to the BoardDiag tool, that would work...I have not given up, just have not had a whole lot of time to work on this the past 2 days.
Click to expand...
Click to collapse
I see boardiag for n5 , please don't give up ?.
And i see blank flash file for N6

Try to connect the usb cable with the pressed vol up button. Normaly the lg download screen should pop up.
Its possible then to flash a tot file with the lg up tool.
But i found only one tot file around the i net.
It will be flashed but hang in the bootscreen.
A org. tot or kdz file were great or a solution to create such a file.

konsolen said:
Try to connect the usb cable with the pressed vol up button. Normaly the lg download screen should pop up.
Its possible then to flash a tot file with the lg up tool.
But i found only one tot file around the i net.
It will be flashed but hang in the bootscreen.
A org. tot or kdz file were great or a solution to create such a file.
Click to expand...
Click to collapse
I can go to download mode but it can't hang , the screen turns to black Immediately. I'm just waiting for another way .

Apayah said:
I can go to download mode but it can't hang , the screen turns to black Immediately. I'm just waiting for another way .
Click to expand...
Click to collapse
Yes. The FW download screen is not an option here. Seems those of us currently needing a solution or method is do to the phone being in QC emergency mode only. I can see my phone in device manager only as with the QC HUSB 9008 drivers.

nate0 said:
Yes. The FW download screen is not an option here. Seems those of us currently needing a solution or method is do to the phone being in QC emergency mode only. I can see my phone in device manager only as with the QC HUSB 9008 drivers.
Click to expand...
Click to collapse
Yes it same , i got that to.
So what is blank flash? on N6 thread .

链接：https://pan.baidu.com/s/1TmQ9jmdAym2NYt_YGyt2Cg 引脚：g5cg

Unbrick LG G4 H815 9008 Qualcomm

Hi guys,
i came up with a temporary to unbrick LG G4 H815 , you just need a 32 GB SD card ( i used Sandisk 10 class) , the dump that i will link , and Win32 disk Imager, the SD card must low level formatted.
1- download this dump
http://www.4shared.com/rar/NzSqsBziba/EMMC_ROM1_032G74_1803230737_00.html
2- put the SD card in the PC and chose the dump file and write ( run as admin ):
3- put the sd card in the phone plug the battery and power on.
Bam

unbrick H811 T-MOBILe
how i can get H811 LG G4 Dump file...?

T.E.I.M said:
how i can get H811 LG G4 Dump file...?
Click to expand...
Click to collapse
From the 1st post?
Sent from my SM-G930F using Tapatalk

bender_007 said:
From the 1st post?
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
i need H811 Model dump file...the 1st one its for h815 Euro Model!!!!!

T.E.I.M said:
i need H811 Model dump file...the 1st one its for h815 Euro Model!!!!!
Click to expand...
Click to collapse
Ah I see now. You have to ask someone from 811 thread to dump it for you. Your keyboard "!" got stuck also?

Is the SD Card must be 32 GB?

aes1151 said:
Is the SD Card must be 32 GB?
Click to expand...
Click to collapse
no, 8 gb enough

Thanks for the answer.
I tried 8GB SD card before and it working but gave me an error (security Error) when I went to get into Download mode ..or gave Boot loop at normal mode ..
Finally it stopped working .. also when I repeated the steps again not running any more
(but with another dump file.)

T.E.I.M said:
i need H811 Model dump file...the 1st one its for h815 Euro Model!!!!!
Click to expand...
Click to collapse
I posted one here for h811 v20o. It booted mine up.

culot said:
I posted one here for h811 v20o. It booted mine up.
Click to expand...
Click to collapse
thanx
size of sd-card you used....?
32 or 8 Go

T.E.I.M said:
thanx
size of sd-card you used....?
32 or 8 Go
Click to expand...
Click to collapse
32gb.

culot said:
32gb.
Click to expand...
Click to collapse
can i use the full dump "Dump_H811_1GB.img"
http://www.gsm-file.com/files/dumph8111gbzip-2702.html
or i must use dump file *.BIN that i cant find it
link me *.bin file for h811

T.E.I.M said:
can i use the full dump "Dump_H811_1GB.img"
http://www.gsm-file.com/files/dumph8111gbzip-2702.html
or i must use dump file *.BIN that i cant find it
link me *.bin file for h811
Click to expand...
Click to collapse
That specific dump did not work at all for me. The singleimage.bin I posted worked for me right away. It's inside the archive i linked in that post.
---------- Post added at 03:15 PM ---------- Previous post was at 02:58 PM ----------
T.E.I.M said:
can i use the full dump "Dump_H811_1GB.img"
http://www.gsm-file.com/files/dumph8111gbzip-2702.html
or i must use dump file *.BIN that i cant find it
link me *.bin file for h811
Click to expand...
Click to collapse
Image is is q.zip in the download link in that post.

thanx

Awesome! I'm sure you will be a lifesaver for many people. Now I don't have to worry as much if I try to port ROMs.
BTW, just curious, but does the SD card execute the dump when the phone boots up or something? (just curious as to how it works by putting a dump on an external sd card).
Thanks

leptdre said:
Hi guys,
i came up with a temporary to unbrick LG G4 H815 , you just need a 32 GB SD card ( i used Sandisk 10 class) , the dump that i will link , and Win32 disk Imager, the SD card must low level formatted.
1- download this dump
2- put the SD card in the PC and chose the dump file and write ( run as admin ):
3- put the sd card in the phone plug the battery and power on.
Bam
Click to expand...
Click to collapse
Hello!
When I put SD in phone and turn it on - it enters download mode and do nothing.
What did I do wrong?

darkommm said:
Hello!
When I put SD in phone and turn it on - it enters download mode and do nothing.
What did I do wrong?
Click to expand...
Click to collapse
you did nothing Wrong , now u need to flash KDZ with LGUP , and you are good to go

qualcomm 9008
my lg g4 h811 stuck on qualcomm 9008 mode,no display, phone does not turned on, but connect as qualcomm 9008 while connected through usb. will this method work for me??

AwaisTariq20 said:
my lg g4 h811 stuck on qualcomm 9008 mode,no display, phone does not turned on, but connect as qualcomm 9008 while connected through usb. will this method work for me??
Click to expand...
Click to collapse
yes use this mothod

Help me
I just follow ur instructions and my phone alive again but one thing after 4 or 5 min later my phone goes blank and turn into Qualcomm 9008 and when i pull battery and insert again phone booted again in normal. Plz help me in this meter i tried all kdz firmwares and also custom roms but still facing this problem. My phone model is h811.

[Unbrick] How to revive H815 - no recovery/fastboot/download mode

Today something went wrong while flashing weekly LOS build and my LG G4 (H815 with v20P firmware) went into very fast bootloop: https://www.youtube.com/watch?v=9gm0dh6bLp4
In this state i wasn't able to enter recovery, nor fastboot, nor download mode. Only IMEI screen (Vol Up + Vol Down I believe) was accessible which was no use.
Here are the steps which got me out of troubles:
A) Verify that you have LGUP installed and have proper 8994.dll version for your device.
Different versions of FW use different libraries which results in errors during flashing.
Steps:
1) Install LGUP with this guide https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
2) Get the right DLL. You can try this one:
Abandoned War Place said:
FIX REFUBRISH/DOWNGRADE ETC STUCK AT 16% DOWNLOAD MODE UNABLE TO GET BACK TO STOCK
error 0x2000 invalid command response Has Been FixeD WITH THE LASTEST DLL FILE
FILE INCLUDE (DLL+PATCH_DLL+SETUP LGUP+DRIVER) package
Please Read The *READ ME FILE FOR THE RIGHT INSTALLATION WITHOUT GETTING ANY PROBLEM :
Link Easy To Download No Ads Bulllsh*t.................. :
https://drive.google.com/file/d/0B_yWw6RLoA-gdTMtZFczMUhQOHM/view?usp=sharing
Click to expand...
Click to collapse
...or extract it directly from KDZ file with extractor https://forum.xda-developers.com/showthread.php?t=2600575.
You need to extract it from FW version that your phone is already running, not from the one you are about to flash! (when flashing from v20d to v20p you need v20d version, but when reflashing v20p FW you need the v20p DLL)
3) Navigate to LGUP install folder (default "C:\Program Files (x86)\LG Electronics\LGUP")
4) Overwrite the old DLL located in "model\8994" folder version with new one in
I don't know the exact compatibility, or how many different DLL versions are out there. Hopefully it doesn't brick the device even more when wrong version is used, it just doesn't work.
B) Write h815 image to sdcard as mentioned here:
leptdre said:
Hi guys,
i came up with a temporary to unbrick LG G4 H815 , you just need a 32 GB SD card ( i used Sandisk 10 class) , the dump that i will link , and Win32 disk Imager, the SD card must low level formatted.
1- download this dump
http://www.4shared.com/rar/NzSqsBzib...230737_00.html
2- put the SD card in the PC and chose the dump file and write ( run as admin ):
Click to expand...
Click to collapse
It worked for me with just 8GB one. Be aware that the image written to SD have like 20 partitions so windows might go crazy.
C) Follow these steps:
jam1445 said:
3. One the Write Completes. Eject Card and insert in your LG G4 H811. Press Volume Up Button while connecting the USB Cable.
4. There you go, it will open the download mode.
Click to expand...
Click to collapse
D) At this moment my G4 finally entered Download mode
I was able to reflash KDZ using the usual procedure (select UPGRADE, find a KDZ file, restart LGUP, select REFURBRISH and START). Initially I got 0x2000 error at approximately 16% (boot displayed as status) that was caused by old version of 8994.dll library.
E) Back to stock
Now you should have stock H815 again so lets flash LOS back as usual
Kudos to OPs: @bullghost , @shakeyabooti , @leptdre , @jam1445 and other posters on G4 section of XDA!
Hope this helps someone!

Good job. If your using this and you're gonna buy a SDCard on purpose, be aware that this fix might not work on your device. Ehehe

@Jirrick im getting the same error on LGUP where do i find a newer version of the dll?

inso420 said:
@Jirrick im getting the same error on LGUP where do i find a newer version of the dll?
Click to expand...
Click to collapse
are these what you looking for.?
https://forum.xda-developers.com/showpost.php?p=73586554&postcount=921

VS986 Stuck on Download Mode
Jirrick said:
Today something went wrong while flashing weekly LOS build and my LG G4 (H815 with v20P firmware) went into very fast bootloop: https://www.youtube.com/watch?v=9gm0dh6bLp4
In this state i wasn't able to enter recovery, nor fastboot, nor download mode. Only IMEI screen (Vol Up + Vol Down I believe) was accessible which was no use.
Here are the steps which got me out of troubles:
A) Verify that you have LGUP installed and have proper 8994.dll version for your device.
Different versions of FW use different libraries which results in errors during flashing.
Steps:
1) Install LGUP with this guide https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
2) Get the right DLL. You can try this one:
...or extract it directly from KDZ file with extractor https://forum.xda-developers.com/showthread.php?t=2600575.
You need to extract it from FW version that your phone is already running, not from the one you are about to flash! (when flashing from v20d to v20p you need v20d version, but when reflashing v20p FW you need the v20p DLL)
3) Navigate to LGUP install folder (default "C:\Program Files (x86)\LG Electronics\LGUP")
4) Overwrite the old DLL located in "model\8994" folder version with new one in
I don't know the exact compatibility, or how many different DLL versions are out there. Hopefully it doesn't brick the device even more when wrong version is used, it just doesn't work.
B) Write h815 image to sdcard as mentioned here:
It worked for me with just 8GB one. Be aware that the image written to SD have like 20 partitions so windows might go crazy.
C) Follow these steps:
D) At this moment my G4 finally entered Download mode
I was able to reflash KDZ using the usual procedure (select UPGRADE, find a KDZ file, restart LGUP, select REFURBRISH and START). Initially I got 0x2000 error at approximately 16% (boot displayed as status) that was caused by old version of 8994.dll library.
E) Back to stock
Now you should have stock H815 again so lets flash LOS back as usual
Kudos to OPs: @bullghost , @shakeyabooti , @leptdre , @jam1445 and other posters on G4 section of XDA!
Hope this helps someone!
Click to expand...
Click to collapse
I just did all your steps for my VS986 , and I got 2 G4 Verizon's back up and working , Thank you so much.
---------- Post added at 10:54 AM ---------- Previous post was at 10:53 AM ----------
I just did all your steps for my VS986 , and I got 2 G4 Verizon's back up and working , Thank you so much.

I'm using a 16gb microsd, but however I try to image it (exfat, fat32 filesystems, different win32imager versions) also have tried different cables, but it still doesn't show any sign of life. I bricked it exactly the same way as OP did. Does anyone have anything else I could try to fix this? Also does the battery charge when its on 9008 mode?

inteLzzz said:
I'm using a 16gb microsd, but however I try to image it (exfat, fat32 filesystems, different win32imager versions) also have tried different cables, but it still doesn't show any sign of life. I bricked it exactly the same way as OP did. Does anyone have anything else I could try to fix this? Also does the battery charge when its on 9008 mode?
Click to expand...
Click to collapse
Can you get at least to the IMEI Display mode (Vol UP and then quickly Vol DOWN, keep both pressed until it shows up)?

Jirrick said:
Can you get at least to the IMEI Display mode (Vol UP and then quickly Vol DOWN, keep both pressed until it shows up)?
Click to expand...
Click to collapse
No could it be caused by low battery? I remember it being like 30% when I bricked it, and does it charge under 9008 mode?

Sorry to hear that. I'm afraid this is beyond my knowledge if it wont even enter the IMEI screen. I suppose you can leave it bootlooping in charger over night and then try in the morning?

Jirrick said:
Sorry to hear that. I'm afraid this is beyond my knowledge if it wont even enter the IMEI screen. I suppose you can leave it bootlooping in charger over night and then try in the morning?
Click to expand...
Click to collapse
It does not bootloop, straight up dead. Just shows 9008 forever on the pc, I left it for like 2 hours like that yesterday. I'll leave it overnight today and if not I'll hack up a direct 5v 1a charger to charge the battery directly. If both don't work i'll probably flash LS991 files in QFIL and use it as a tablet afterwards.. damn i got this phone not even 2 weeks ago perfect condition and all. Will not buy any more damn LG devices.

Oh, I thought your phone was rapidly bootlooping like mine did. Sounds like the person who sold it to you was aware that the phone is on last legs (probably even baked the phone so it runs for few days more) and screwed you over. My next phone wont be LG either.

Flash failed, stuck in download mode (H815)

Hi guys,
for the last months I was using LineageOs, but since they dropped development for our device I wanted to get rid of it.
I tried to get AOSP running but failed. Next I flashed a stock kdz file in Download Mode using LGUP and it worked,
I was back to stock. I tried to install AOSP through TWRP but failed again and eventually ended up doing a hard reset.
This temporarily bricked the device because now the stock android booted and Android Device Protection (FRP) was
active and didn't let me log in. Desperate to find a solution I flashed random kdz/tot files for the device that I found on
the Internet until one finally worked (LGH815 EU Nougat 7.0 BySezerSimsek), the FRP thing was gone. Then I tried to at
least get back to stock again, but when I tried to flash the stock kdz file LGUP aborts at 25% with Error Code 0x2000.
Every time I start the phone now, it goes directly in this firmware update/download mode.
The device shows up as "LGE AndroidNet USB Serial Port" In Windows Device Manager
In Download mode it says "633A B92 Official" on the display
I already tried:
Different dll files for LGUP
Using LG Flash Tool 2014 instead
Putting dump file on SD card
Should I put it in 9008 mode and work with QFIL or what am I supposed to do now?
Thank you.

I'm still able to get into fastboot mode btw. But I'm going to wait for replies here
before I make things worse. If that's even possible at this point. :silly:

h4yabu5a said:
I'm still able to get into fastboot mode btw. But I'm going to wait for replies here
before I make things worse. If that's even possible at this point. :silly:
Click to expand...
Click to collapse
:highfive:<-

jason_l367 said:
:highfive:<-
Click to expand...
Click to collapse
My phone is alive again, thanks Jason:laugh:
Just a short recap what I've done now in case it helps someone with the same problem, the full instructions
are in Jasons link.
I used the KDZ and TOT Extractor to extract the LGUP8994.dll file out of a stock Marshmallow v20p KDZ.
I renamed the dll to LGUP_8994.dll and moved it to C:\..\LG Electronics\LGUP\model\8994, overriding the
existing file. Now LGUP was able to flash the v20p KDZ without the 0x2000 Error.

"WIP" Debrick / Unbrick T560NU-Galaxy-TAB-E / Qualcomm APQ8016 CPU

First......This is a work in progress meaning it is not a fully working solution yet.​
So that's the bad news.
The good news is that this provides an opportunity to learn something.
Everything we learn should also apply to any of the newer Samsung Qualcomm Based Devices.
Lets investigate some of the past methods used to unbrick dead samsung devices.
Also please note that these methods are for Hard Bricked Devices. ( NO Download Mode / NO Recovery Mode / Unresponsive )
Any device that can boot into download mode can easily be fixed with ODIN.
#1) Methods of possible DeBrick That I know of.
A) Use Recovery SD Card.
B) Use Firehose to flash in QDL 9008 / 9006 mode.
C) Boxes - JavaCard - Hardware type solutions.
For now lets look at option A). Hopefully this option is still viable. Although I have tested this a little and so far I am still unable to get booted into download mode.
So in researching Debrick image or Debrick rom of samsung devices you will find some things.
This is what we are interested
https://www.scribd.com/document/272...de-Qualcomm-APQ8084-Includes-SM-N910F-Rev-3-0
Looking at that we should be able to use ODIN and select T-Flash to create the Boot-Recovery-Image.
Unfortunately I tried this and it did not work. The T-Flash just hangs and eventually errors out.
This could be due to the version of Odin i used.
I tried a couple of different Odin versions without any luck.
And also YES you have to do this on a working device.
Since the ODIN method didn't work I know from past experience how to make a bootable EMMC Clone onto a SD-Card.
You can do this in windows or in linux or in the device Terminal ( TWRP Terminal)
This command will make a byte for byte copy of the device EMMC onto a SD Card.
Here are the steps.
1) Insert Blank 16GB SD card into the working device. ( The sd card must be high quality Like V30 or U1 Class. " 95 to 100 mbs speed " )
2) The bootloader version of the device you are using to make the sd card has to match the version on the bricked device. (Flash good device with odin to match factory software before making sd card) <-- <-- <-- " Probable reason my Card is not working yet to boot my bricked device "
3) After that its pretty simple.
We know that the main EMMC of the Tablet is MMCBLK0
We know that the SD Card is assigned MMCBLK1
So executing the following command will clone the emmc to the sd card.
Code:
dd if=/dev/block/mmcblk0 of=/dev/block/mmcblk1
It will take between 30 min and a hour to copy.
I have created this image and tested it but no luck yet.
The image is of the factory T560NUUEU1CQK2_T560NUXAR1CQK2 firmware.
I bricked my tab by flashing the aboot.bin alone from COMBINATION_XAR_FA51_T560NUUEU1APH1.
I flashed just the aboot without flashing the rest of the booloaders from COMBINATION_XAR_FA51_T560NUUEU1APH1.
So what i need to do next is make a card that has the complete set of bootloaders from COMBINATION_XAR_FA51_T560NUUEU1APH1.
Once we have a clone of the emmc we can flash seperate partitions on the sd card just like if we did on the device.
I know for sure the bootloader versions have to match. This is a likly cause for my card not to bring my Tab back to life.
Another possibility is that the card has the whole emmc backup. Mirror of the device. Realistically it should be just the bootloaders.
I have looked at some of the boot-recovery images for other devices. Some have only the bootloaders. Some have all the partitions but only the bootloaders flashed. And even the fact that it is a direct copy of the emmc and not its own unique GPT could all factor into it not working at the moment.
All these different combinations of things could be the difference between the card working or not working.
I will upload the image for you if you want to test it.
You can also dump each partition to an individual backup image in case you need any of them.
Do it in linux using "dd" or do it on the device using "dd" and mmcblk1 rather than mmcblk0
If you don't know what i'm talking about don't worry. I will go over things like that at some point in time.
Here is a upload of the SD Card - EMMC Clone for 16GB T560NU
http://www.mediafire.com/file/5m0b7r11nc3nn5q/16GB-T560NU-.img.zip/file
Unzip the file.
Use win32diskimager to flash the image to the sdcard.
After win32diskimage is complete a bunch of file windows will pop up. On windows 10.
It will say disk must be formatted. Do NOT format the disks.
Close them all and remove the sd card from the computer.
Put sd card in bricked device.
Plug in usb.
Try to boot.
Try to boot into download mode.
Let it sit 5 or 10 min.
See if anything happens.
If you have any luck please let us know.

Unfortunately I think were gonna end up having to do it this way.
https://forum.xda-developers.com/galaxy-s8/help/s8-g950u-hardbrick-t3668572
But we need the .elf programmer for APQ8016.
If anyone can get me the firehose programmer I can build the service rom.

BigCountry907 said:
Unfortunately I think were gonna end up having to do it this way.
https://forum.xda-developers.com/galaxy-s8/help/s8-g950u-hardbrick-t3668572
But we need the .elf programmer for APQ8016.
If anyone can get me the firehose programmer I can build the service rom.
Click to expand...
Click to collapse
Did you ever figure yours out? I did the same thing you did (downgraded aboot and hard bricked). I've been able to create a debrick img using another identical device, but the bricked one still won't respond when the sd card is inserted

iBowToAndroid said:
Did you ever figure yours out? I did the same thing you did (downgraded aboot and hard bricked). I've been able to create a debrick img using another identical device, but the bricked one still won't respond when the sd card is inserted
Click to expand...
Click to collapse
I ended up changing the mainboard.
It was like $60 on amazon. Not sure how many are available.
I tried using a good device to T-Flash a sd card in odin.
The t-Flash never worked.
I also did a direct dump to a sdcard, Literally mirroring the emmc onto the sdcard.
dd if=/dev/block/mmcblk0 of=/dev/block/mmcblk1
The device did not respond to the sd card.
I have recently un-bricked a N950U Note 8 but in order to do that i needed things.
In order to get into edl mode there is a test point somewhere on the board.
You short the test point to ground and then plug in the usb and it will boot edl.
I do not know where the test point of the t560nu is at.
Second you will need the Firehose programmer for the t560nu specifically.
It needs to match the bootloader rev as well.
I don't think its revision that causes the brick but it could be.
I flashed the engineering aboot to a normal running device and that's how i bricked.
I believe you have to flash the whole bootloader set if your going to flash bootloaders.
Someone with a octoplus box got me the test point location.
Octoplus software has photos of the test points.
The edl package was from a different source.
It's possible someone with octoplus or medusa or similar boxes may be able to get the test point and the firehose.
I asked my guy for it but i don't think he looked yet.
I still have my bricked board so if you find the firehose and the testpoint let me know.
I will ask my guy again to check.

BigCountry907 said:
I believe you have to flash the whole bootloader set if your going to flash bootloaders
Click to expand...
Click to collapse
Correct, with qualcomm devices the revision of aboot needs to match the sbl.
Sbl checks the version of aboot if it doesn't match it refuses to boot.
Been there done that.
However I have yet to attempt a hardware repair. Debrick images unsuccessful, no response.
My next step(when I can be bothered to get around to it) is to use an sd card adapter wired directly to the emmc as both use the same protocols and an sd card controller should be able to communicate with an emmc.
As long I can get the partitions to show up on the EMMC, should hopefully be a case of flashing the correct aboot to the right partition.

BigCountry907 said:
I ended up changing the mainboard.
It was like $60 on amazon. Not sure how many are available.
I tried using a good device to T-Flash a sd card in odin.
The t-Flash never worked.
I also did a direct dump to a sdcard, Literally mirroring the emmc onto the sdcard.
dd if=/dev/block/mmcblk0 of=/dev/block/mmcblk1
The device did not respond to the sd card.
I have recently un-bricked a N950U Note 8 but in order to do that i needed things.
In order to get into edl mode there is a test point somewhere on the board.
You short the test point to ground and then plug in the usb and it will boot edl.
I do not know where the test point of the t560nu is at.
Second you will need the Firehose programmer for the t560nu specifically.
It needs to match the bootloader rev as well.
I don't think its revision that causes the brick but it could be.
I flashed the engineering aboot to a normal running device and that's how i bricked.
I believe you have to flash the whole bootloader set if your going to flash bootloaders.
Someone with a octoplus box got me the test point location.
Octoplus software has photos of the test points.
The edl package was from a different source.
It's possible someone with octoplus or medusa or similar boxes may be able to get the test point and the firehose.
I asked my guy for it but i don't think he looked yet.
I still have my bricked board so if you find the firehose and the testpoint let me know.
I will ask my guy again to check.
Click to expand...
Click to collapse
It's only ever been on bootloader rev 1, so i figured i was fine going back as far as possible with aboot, like how it is for sboot on Exynos. Obviously not correct though.
Yeah, I dumped to an SD, but only did the first 200MB, instead of an entire image. I have no idea if that even works on this model - I was just hoping it would, like it used to for the S3 and other devices.. I have no idea where i'd get the firehose so this might be SOL

respected brother plz give me your whatsap no# my tablte t560nu dead after flash
respected brother plz give me your whatsap no# my tablte t560nu dead after flash
My whatsap 03103615995
---------- Post added at 12:47 PM ---------- Previous post was at 12:39 PM ----------
respected brother plz give me your whatsap no# my tablte t560nu dead after flash
My whatsap 03103615995

SM-T560NU Does not Turn On After Software Flash
Hello All,
I have been told this is the right place to find a solution to this problem. I have a Galaxy Tab E (SM-T560NU) that had an attempt made to get around FRP using Odin and Sboot firmware. Unfortunately the thing has not been able to turn on since the flash was done & I am told it has been soft bricked. Is there a proven method of brining this thing back to life?

Datsys said:
Hello All,
I have been told this is the right place to find a solution to this problem. I have a Galaxy Tab E (SM-T560NU) that had an attempt made to get around FRP using Odin and Sboot firmware. Unfortunately the thing has not been able to turn on since the flash was done & I am told it has been soft bricked. Is there a proven method of brining this thing back to life?
Click to expand...
Click to collapse
If it won't even turn on, then it's hard bricked - not soft bricked. And no, no proven method to fix it

Datsys said:
Hello All,
I have been told this is the right place to find a solution to this problem. I have a Galaxy Tab E (SM-T560NU) that had an attempt made to get around FRP using Odin and Sboot firmware. Unfortunately the thing has not been able to turn on since the flash was done & I am told it has been soft bricked. Is there a proven method of brining this thing back to life?
Click to expand...
Click to collapse
How have you managed to flash firmware for Exynos to a Snapdragon device? Sboot is the Exynos boot loader.

ashyx said:
How have you managed to flash firmware for Exynos to a Snapdragon device? Sboot is the Exynos boot loader.
Click to expand...
Click to collapse
I'm sure he meant aboot

iBowToAndroid said:
I'm sure he meant aboot
Click to expand...
Click to collapse
Well if he flashed aboot without sbl then there's not much hope.
SBL checks the integrity of aboot and if it doesnt match it refuses to proceed.
Can't even use qualcomm low level tools.
The only way that may be possible which I have never tried is to wire the emmc direct to an sdcard adapter and hope the controller is able to boot it and see the partitions.
Then flash the correct aboot or sbl.