Database Users

2017g DFU mode investigation

This thread is for users who have a 2017g model that is stuck in DFU mode.
If you would like to assist in the investigation, please reply here. I'll be sending links to test programs to try to diagnose and repair devices.
With any luck, we can get the devices back to normal within a few days.

Reserved

I had this problem, but luckily I could send it back and get a new one on warranty. I was very careful when unlocking the new one ?
Skickat från min ZTE A2017G via Tapatalk

Can more people who are stuck in DFU mode PLEASE contact tennear? I worked with him before and he really knows what he is doing. He's the only one who I think could be able to help you restore your device to working state.
Please help him, so A2017g users like me know they have a trick up their sleeve in the case the BL unlock goes awfully wrong
Thank you.

@tennear keep us updated. I'm planning to give up root in order to get this week's B08 update and i'm not sure if flashing the system with twrp will go smoothly.
Thank you for you work and dedication to help other people.

I have two people that are able to help now. But more is always better. If you have a G model and you can access DFU (regardless if you are bricked or not), you can help test. Linux is my preferred OS, but I can also build for Win64 if needed.

razorsbk said:
@tennear keep us updated. I'm planning to give up root in order to get this week's B08 update and i'm not sure if flashing the system with twrp will go smoothly.
Thank you for you work and dedication to help other people.
Click to expand...
Click to collapse
If you are Lock bootloader and have TWRP you CAN flash B08 , just need to mod. The updater_script in other for the B08 to be install, but YOU WON'T BE ABLE TO ROOT unless you unlock bootloader and I'll be posting something about that later today or coming days.

DrakenFX said:
If you are Lock bootloader and have TWRP you CAN flash B08 , just need to mod. The updater_script in other for the B08 to be install, but YOU WON'T BE ABLE TO ROOT unless you unlock bootloader and I'll be posting something about that later today or coming days.
Click to expand...
Click to collapse
I'm rooted without unlocking bootloader (tenfar's method).
So you are saying I can flash the upcoming update safely from TWRP by editing updater script and removing getprop & assertprop lines from it?
I also have system modifications.
Sent from my ZTE A2017G using Tapatalk

razorsbk said:
I'm rooted without unlocking bootloader (tenfar's method).
So you are saying I can flash the upcoming update safely from TWRP by editing updater script and removing getprop & assertprop lines from it?
I also have system modifications.
Sent from my ZTE A2017G using Tapatalk
Click to expand...
Click to collapse
Ok, I don't want to go off topic here, but YES you'll need to edit updater_script and look and bookmark if possible my thread about Updates ,I'll be posting B08 as soon the full update hits ZTE site. If you want to talk about Updates post there , so we can keep this thread on topic.

I agree. See you there.
Sent from my ZTE A2017G using Tapatalk

tennear said:
I have two people that are able to help now. But more is always better. If you have a G model and you can access DFU (regardless if you are bricked or not), you can help test. Linux is my preferred OS, but I can also build for Win64 if needed.
Click to expand...
Click to collapse
I have a G model and I am using Linux (based on ArchLinux). I can use Windows 10 if needed, so OS should not be a problem.
So if you need some testing, I can help

Hi, I would love to help,
I have a G model and I have TWRP and unlocked bootloader but u can access DFU mode
I am using windows

I'm afraid that I have not been successful getting out of DFU mode. I have tried several things, but the device refuses to switch into EDL mode.
According to the user who has a bricked device, he got bricked by running "axon7backup -d" without any image files present. The tool wrote something to both boot and recovery partitions. I don't know what that something is -- zeros, random data, ... who knows.
So it seems that if you are careful and only flash recovery properly, the device should not brick. But I cannot test -- someone else will need to confirm.
Now that this investigation is concluded, I will be posting my own tool shortly.
Always remember: to avoid bricking your device, never flash both boot and recovery at the same time.

^^Is there even a reason to flash the boot/kernel? The main reason why most of us would use the axonbackup tool is to flash twrp.

gpz1100 said:
^^Is there even a reason to flash the boot/kernel? The main reason why most of us would use the axonbackup tool is to flash twrp.
Click to expand...
Click to collapse
The only reason why tenfar had the tool to Flash boot is because he had the boot sign and pre-rooted for Lock bootloader units.

^^Got it. I thought about keeping the BL locked, but decided unlocking it would cause fewer headaches and be less restrictive.

That is correct, there is no real reason to flash your boot partition now that the images provided by tenfar are not compatible with the latest updates from ZTE.
However, the real danger remains: if you run "axon7backup -d" with no files to write, it is reported to write bad data over both boot and recovery and brick your device.
I highly recommend using my tool instead. I can guarantee that it will never write both boot and recovery in the same session.

tennear said:
That is correct, there is no real reason to flash your boot partition now that the images provided by tenfar are not compatible with the latest updates from ZTE.
However, the real danger remains: if you run "axon7backup -d" with no files to write, it is reported to write bad data over both boot and recovery and brick your device.
I highly recommend using my tool instead. I can guarantee that it will never write both boot and recovery in the same session.
Click to expand...
Click to collapse
The command help indicates -d is to dump only. My understanding is nothing is written to the phone when reading from it? Are you saying that's not the case?

gpz1100 said:
The command help indicates -d is to dump only. My understanding is nothing is written to the phone when reading from it? Are you saying that's not the case?
Click to expand...
Click to collapse
Yes, that is what I am saying. According to a PM that I received, the user ran "axon7backup -d" without any other files in the directory. The tool flashed something to both boot and recovery partitions. No idea what it flashed. But then the device was bricked. And because 2017g cannot enter EDL mode directly, there is no way to unbrick.

hi i have china version of axon 7 A2017 and have the same problem with my device (stuck in dfu mode after Flashing SuperSU).Will there ever be a way to fix this problem? I am depered :crying:.

How to unlock the bootloader of the SM-N910F (Samsung Galaxy Note 4)?

Hey guys!
At first, this is my first post here so please be lenient if I posted this in the wrong section or whatever. I still need to get used to this forum.
Second, English is not my native language so it could become some gibberish from time to time. I also have to mention that my Android skills are somewhere between newbie and advanced, so please keep that in mind.
But let's get ahead to my problem:
Some days ago, I decided to install Linage OS 14 on my SM-N910F because I don't like the Stock Android 6.0.1 of it.
As you know, a custom ROM requires an unlocked bootloader an that's where my struggle starts.
I simply can't find any tutorial or similar for my phone. The only one I found didn't work (It was with adb fastboot, the process got stuck at "<wating for device>" after the command "fastboot unlock oem" which was described in the tutorial).
I retried it about three or four times before I gave up. It feels like I searched the entire internet, including this forum, but I couldn't find anything useful.
Maybe it's my fault because I didn't look properly, but yeah, know I'm here to ask directly:
Do you guys have any tricks, tipps, ideas or tutorials for me to try?
If it helps you, my phone is already rooted. (chainfire's CF Autoroot)
It'd make me really, really happy and already thank you for your (hopefully) incoming answers.

Vygravlil said:
Hey guys!
At first, this is my first post here so please be lenient if I posted this in the wrong section or whatever. I still need to get used to this forum.
Second, English is not my native language so it could become some gibberish from time to time. I also have to mention that my Android skills are somewhere between newbie and advanced, so please keep that in mind.
But let's get ahead to my problem:
Some days ago, I decided to install Linage OS 14 on my SM-N910F because I don't like the Stock Android 6.0.1 of it.
As you know, a custom ROM requires an unlocked bootloader an that's where my struggle starts.
I simply can't find any tutorial or similar for my phone. The only one I found didn't work (It was with adb fastboot, the process got stuck at "<wating for device>" after the command "fastboot unlock oem" which was described in the tutorial).
I retried it about three or four times before I gave up. It feels like I searched the entire internet, including this forum, but I couldn't find anything useful.
Maybe it's my fault because I didn't look properly, but yeah, know I'm here to ask directly:
Do you guys have any tricks, tipps, ideas or tutorials for me to try?
If it helps you, my phone is already rooted. (chainfire's CF Autoroot)
It'd make me really, really happy and already thank you for your (hopefully) incoming answers.
Click to expand...
Click to collapse
Pretty certain your bootloader isn't locked, you just need to install twrp with odin and then you are good to flash lineage

sawdoctor said:
Pretty certain your bootloader isn't locked, you just need to install twrp with odin and then you are good to flash lineage
Click to expand...
Click to collapse
Thank you for your fast reply. I'll try it once again, moreover I'll let you know if it worked.

It's me again. Flashing the ROM worked, my phone now runs under Linage OS 14.1. But now I've got another problem: Gapps. Somehow I can't flash the Gapps package, TWRP always tells me that the file is corrupted. I downloaded both the Pico and the Nano package for ARM Android 7.1* devices. Both don't work. I also tried the Android 7.0.* version, but that didn't work ofcourse. (Error 20: Wrong Android version installed on the device.) Is it my fault because I downloaded the wrong packages or what's the issue?
It'd be awesome if you could help me again.
Vygravlil
EDIT:
Okay, now it works. TWRP was right, the file was corrupted. I figured out that my PC kinda messed up the download of the package. I downloaded it with another computer and now everything works fine.

Checking on unlock possibility

Hey guys, I'm looking into getting an axon7mini. Before I do, I want to verify that I can get into EDL mode and talk to the device. Is anyone willing to take one of the axon7 tools and see if it will talk to the axon7mini in EDL mode? You don't need to write anything, just read. For example, do a backup of the recovery image using one of the tools.
If that works, I'll snag one off ebay and get Lineage up and running in short order.

If you can provide some instructions, I'm happy to test this for you. Running the latest lollipop rom atm. Can update to nougat if required.
Thanks

Just grab one of the axon7 EDL programs, such as:
https://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Or:
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
Follow the instructions there to backup your recovery or boot partition.
If it can communicate with the axon7mini, then odds are very high that we can get the boot loader unlocked and start building custom ROMs.
If it cannot communicate with the axon7mini, I'll need to pursue other channels for an unlock, which may not be successful.
dpgc213 said:
If you can provide some instructions, I'm happy to test this for you. Running the latest lollipop rom atm. Can update to nougat if required.
Thanks
Click to expand...
Click to collapse

tdm said:
Just grab one of the axon7 EDL programs, such as:
https://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Or:
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
Follow the instructions there to backup your recovery or boot partition.
If it can communicate with the axon7mini, then odds are very high that we can get the boot loader unlocked and start building custom ROMs.
If it cannot communicate with the axon7mini, I'll need to pursue other channels for an unlock, which may not be successful.
Click to expand...
Click to collapse
Cool, will give it a go tomorrow.

tdm said:
Just grab one of the axon7 EDL programs, such as:
https://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Or:
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
Follow the instructions there to backup your recovery or boot partition.
If it can communicate with the axon7mini, then odds are very high that we can get the boot loader unlocked and start building custom ROMs.
If it cannot communicate with the axon7mini, I'll need to pursue other channels for an unlock, which may not be successful.
Click to expand...
Click to collapse
Hi,
I can get it to communicate however when attempting "axon7tool -r gpt boot recovery" I'm getting an error which cause the tool to crash. it reads failed to read command.
Thanks

dpgc213 said:
Hi,
I can get it to communicate however when attempting "axon7tool -r gpt boot recovery" I'm getting an error which cause the tool to crash. it reads failed to read command.
Thanks
Click to expand...
Click to collapse
Thanks. That probably means it's incompatible. :/

tdm said:
Thanks. That probably means it's incompatible. :/
Click to expand...
Click to collapse
Yeah, this means incompatible, we need the programmer, firehose file 8952. But is only in a old firmware (NOT SD card upgrade). Anyone have this?

tdm said:
Just grab one of the axon7 EDL programs, such as:
https://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Or:
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
Follow the instructions there to backup your recovery or boot partition.
If it can communicate with the axon7mini, then odds are very high that we can get the boot loader unlocked and start building custom ROMs.
If it cannot communicate with the axon7mini, I'll need to pursue other channels for an unlock, which may not be successful.
Click to expand...
Click to collapse
tdm, you don't live far from me.
i'll try these out as well, but you have a local beta tester
Edit:
Same error even running in compatibility mode Windows 8
Code:
E:\Axon>axon7tool -r recovery
Connecting to device...
Sending programmer...
S: target error 0x00000014
terminate called after throwing an instance of 'std::runtime_error'
what(): error: No error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Code:
E:\Axon\axon7root>axon7root -d
Copyright @tenfar [email protected]
Version 1.10
Failed to say hello to device
device no response
!!!!!!!! Horse is dead!!!!!!!!!

rombdeta said:
Yeah, this means incompatible, we need the programmer, firehose file 8952. But is only in a old firmware (NOT SD card upgrade). Anyone have this?
Click to expand...
Click to collapse
I can probably find a 8952 firehose, but it will be from another manufacturer. So it won't be signed with the proper key. Which means it almost surely won't work.
Sent from my Find 5 using Tapatalk

Been trying to snag an axon7mini on ebay for about $120 but they keep going for $140-$150. @fallen00sniper if you want to trade me for another phone for a week, I can try my hand at unlock.

Well i have the programmer finally!

rombdeta said:
Well i have the programmer finally!
Click to expand...
Click to collapse
Which programmer? The official axon7mini one? Or for another device?

tdm said:
Which programmer? The official axon7mini one? Or for another device?
Click to expand...
Click to collapse
Axon 7 mini, 8952, but i will work with my device, i need info how to edit the bootloader bit

Currently, I added a file to remove patron / code, since some recovery does not bring the option of "wipe data", but I repeat is only a test, I do not take responsibility for damages, this is the door to unlock the boot and customs roms , recoverys and so on.
https://mega.nz/#!k1M2gKya!tjtjCD4Jp...xvYzx-wjeTrYvE

tdm said:
Been trying to snag an axon7mini on ebay for about $120 but they keep going for $140-$150. @fallen00sniper if you want to trade me for another phone for a week, I can try my hand at unlock.
Click to expand...
Click to collapse
We would have to speak about this further.
I'm on MetroPCS and they charge $15 Everytime I move the Sim to a different device, maybe on the website I can do it for free, not sure.

How do they do that? You should just be able to swap your sim over shouldn't you?

Hdale85 said:
How do they do that? You should just be able to swap your sim over shouldn't you?
Click to expand...
Click to collapse
I can swap the Sim over, but the IMEI change is where they get me, but it looks like I can do it free on the website, since I cannot go any further without a different IMEI I don't know if they charge and I am currently out of work :/
However if @tdm pm me we can talk about this trading for a week and try to get this ball rolling.

rombdeta said:
Axon 7 mini, 8952, but i will work with my device, i need info how to edit the bootloader bit
Click to expand...
Click to collapse
Nice! I'd love a copy of that. I can most likely make unlock tools with it.
Next question... does this device have a fbop partition?

tdm said:
Nice! I'd love a copy of that. I can most likely make unlock tools with it.
Next question... does this device have a fbop partition?
Click to expand...
Click to collapse
I think so, the link is in another post.

rombdeta said:
I think so, the link is in another post.
Click to expand...
Click to collapse
The link is bad, it says the provided key is invalid.

Sooo... I screwed up BIG TIME...

First of all, hello there community, all of you have already helped me so much and I really appreciate the effort that you put into this site to help guys like me out
Now onwards to my Problem:
I've had the P Smart for a couple of month when I considered using a Treble custom Rom (just to try it out and have some fun with it).
Since I didn't know how to flash GSI's I googled it and took the first step by step tutorial and followed it.
The Rom I flashed was the PixelExperience_arm64_a-8.1.0-20181015-0009-OFFICIAL.img.
Basically I flashed the rom via fastboot.
When I then realized that it wasn't quite what I expected I wanted to try out other roms.
So I went do dev-options and turned on ADB and OEM-Unlock but then... The OEM-Unlock option was greyed out.
f.
Since I came from stock I have had not yet installed TWRP.
I have searched the internet for hours and hours, day after day but I could not find a single option that could help me with my particular problem.
My current state:
- I have a rom that I do not longer want installed
- I do not have TWRP or any other custom-recovery installed
- In fastboot it says
"bootloader unlocked"
"FRP locked"
(My model is FIG-LX1 btw)
So, here I am and asking you guys for help.
Is there ANY possibility (aside from replacing the mainboard) to fix my phones current state?
Your help is really appeciated,
love y'all
kthxbye

the_darkest_knight said:
First of all, hello there community, all of you have already helped me so much and I really appreciate the effort that you put into this site to help guys like me out
Now onwards to my Problem:
I've had the P Smart for a couple of month when I considered using a Treble custom Rom (just to try it out and have some fun with it).
Since I didn't know how to flash GSI's I googled it and took the first step by step tutorial and followed it.
The Rom I flashed was the PixelExperience_arm64_a-8.1.0-20181015-0009-OFFICIAL.img.
Basically I flashed the rom via fastboot.
When I then realized that it wasn't quite what I expected I wanted to try out other roms.
So I went do dev-options and turned on ADB and OEM-Unlock but then... The OEM-Unlock option was greyed out.
f.
Since I came from stock I have had not yet installed TWRP.
I have searched the internet for hours and hours, day after day but I could not find a single option that could help me with my particular problem.
My current state:
- I have a rom that I do not longer want installed
- I do not have TWRP or any other custom-recovery installed
- In fastboot it says
"bootloader unlocked"
"FRP locked"
(My model is FIG-LX1 btw)
So, here I am and asking you guys for help.
Is there ANY possibility (aside from replacing the mainboard) to fix my phones current state?
Your help is really appeciated,
love y'all
kthxbye
Click to expand...
Click to collapse
You must sign in google account

leap_ahead said:
You must sign in google account
Click to expand...
Click to collapse
Did that already...

Erecovery, connects to wifi, reads the lastest rom from a server, installs it, wipes it all to stock
Hopefully that works
https://www.hardreset.info/devices/huawei/huawei-p-smart/recovery-mode/

redultra82 said:
Erecovery, connects to wifi, reads the lastest rom from a server, installs it, wipes it all to stock
Hopefully that works
https://www.hardreset.info/devices/huawei/huawei-p-smart/recovery-mode/
Click to expand...
Click to collapse
Tried that already, it can't connect to the update server. ("Getting package info failed").
Also I tried the dload method, but none of the update files that I tried seemed to work, it either goes to 5% or says "software install failed" (or both).

..

the_darkest_knight said:
Tried that already, it can't connect to the update server. ("Getting package info failed").
Also I tried the dload method, but none of the update files that I tried seemed to work, it either goes to 5% or says "software install failed" (or both).
Click to expand...
Click to collapse
I thought that was the be all of recovery, its never let me now

Hey dude i had ur same problem . All u need to do is use eRecovery and firmware finder through d's its easy
U this will guide you
https://www.google.tn/amp/s/forum.x...y-huawei-erecovery-solution-100-t3620165/amp/
let me know if you need further help

redultra82 said:
I thought that was the be all of recovery, its never let me now
Click to expand...
Click to collapse
I don't know why it doesn't work...
ilyes9999 said:
Hey dude i had ur same problem . All u need to do is use eRecovery and firmware finder through d's its easy
U this will guide you
https://www.google.tn/amp/s/forum.x...y-huawei-erecovery-solution-100-t3620165/amp/
let me know if you need further help
Click to expand...
Click to collapse
So I tried that out, but firstly I couldn't find a proper OEMINFO, and secondly I don't think I could flash it, since my OEM bootloader is still locked...
As I understood HWOTA doesn't support the P Smart (yet?), and it also needs the OEM to be unlocked
And without the OEMINFO it does not seem to work

the_darkest_knight said:
I don't know why it doesn't work...
So I tried that out, but firstly I couldn't find a proper OEMINFO, and secondly I don't think I could flash it, since my OEM bootloader is still locked...
As I understood HWOTA doesn't support the P Smart (yet?), and it also needs the OEM to be unlocked
And without the OEMINFO it does not seem to work
Click to expand...
Click to collapse
I don't know what you mean . All i know by my experience if you can access the eRecovery you can fix it even with locked bootloader
---------- Post added at 03:27 PM ---------- Previous post was at 03:25 PM ----------
And by the way when looking for a firmware for your device . You should use older versions and it should be the full ota update

Please, I need prog_emmc_firehose_8996.mbn (.elf) for QFIL [I offer donation]

Hello, thank you very much for reading, I hope you can help me. I need one or more files to be able to recover my phone: Samsung Galaxy S7 Active.
These are the files that I need:
prog_emmc_firehose_8996.mbn (.elf)
rawprogram0.xml
patch0.xml
I do not know if I would also need these:
MPRG8996.hex
rawprogram_unsparse.xml
I think these files are the same as prog_emmc_firehose_8996.mbn (.elf):
8996_msimage.mbn
MSM8996.mbn
How did I make a brick my phone? Installing the first official version:
SM-G891A_G891AUCU1APG7_ATT_Full_Repair_Frimware
Previously I used this version without any problem:
G891AUCS2API2_CL8737252_QB10881022_REV02_user_low_ship_MULTI_CERT

I wish someone could help me, I have read more than 50 pages, but I have not been able to solve the problem.

Please.

Can anybody help me?

hey.... i'm on the same situation..
i need zuk Z2 pro/ prog_ufs_firehose_8996_ddr_zuk.mbn but i only have elf....
it's to remove this stupid frp lock from someone who forgot his first mail... :/
keep going we are going to find out the solution

yakine13 said:
hey.... i'm on the same situation..
i need zuk Z2 pro/ prog_ufs_firehose_8996_ddr_zuk.mbn but i only have elf....
it's to remove this stupid frp lock from someone who forgot his first mail... :/
keep going we are going to find out the solution
Click to expand...
Click to collapse
I hope someone helps us.

HEY!
I found a way!!!
...for me:/
why you want this emmc_firehose_8996.mbn?
actually, i think that you don't need that file especially, it doesn't exist from where i've searched.
if it's to flash your phone all you need is odin and a flashable file of your phone firmware
i had a zuk z2 pro and was locked with frp when i wanted to setup custom rom AOSP 9.0.0 for example.
but i managed to unlock it by flashing a custom rom without gapps in the first place to no get locked out.
tell me how your phone is reacting, what do you have access to, and your initial step before brick

yakine13 said:
hey.... i'm on the same situation..
i need zuk Z2 pro/ prog_ufs_firehose_8996_ddr_zuk.mbn but i only have elf....
it's to remove this stupid frp lock from someone who forgot his first mail... :/
keep going we are going to find out the solution
Click to expand...
Click to collapse
yakine13 said:
HEY!
I found a way!!!
...for me:/
why you want this emmc_firehose_8996.mbn?
actually, i think that you don't need that file especially, it doesn't exist from where i've searched.
if it's to flash your phone all you need is odin and a flashable file of your phone firmware
i had a zuk z2 pro and was locked with frp when i wanted to setup custom rom AOSP 9.0.0 for example.
but i managed to unlock it by flashing a custom rom without gapps in the first place to no get locked out.
tell me how your phone is reacting, what do you have access to, and your initial step before brick
Click to expand...
Click to collapse
Hello, sorry for my bad English. My phone is a Samsung Galaxy S7 Active (SM-G891A). I will try to explain what happened.
I had this version of Android 6 installed (via Odin) on the phone:
G891AUCS2API2_CL8737252_QB10881022_REV02_user_low_ship_MULTI_CERT
With that version my phone was fine, but then I tried to install the first version of Android 6 (official) via Odin:
SM-G891A_G891AUCU1APG7_ATT_Full_Repair_Frimware
When the installation was completed (Odin said the installation was successful), the phone never restarted. There is no way to turn it on with any combination of buttons, nor with a microSD with a debrick.img. A USB JIG has not worked for me either.
Windows detects my phone in Qualcomm 9008 mode. Odin does not detect it.

did you find a solution?
actually it look like to be a hard brick but as it's snapdragon 820 you can recover from it

I'm waiting for the day when noobs and half-noobs (no offense, all of us have been there) will start reading before writing and stop assuming that their 1st aid kit will revive a kitten ran over by a train.
It's okay not to know, but before writing a spam reply, just consider for a second that the user already tried your solution and is already a step ahead.
Listen guy, go to Halab Tech. They have certain firmwares for what you need, but they ask money.
Those type of firmwares have a prefix "DEBUG_EMERGENCY_DOWNLOAD_FA....'
In my case it's "DEBUG_EMERGENCY_DOWNLOAD_FA70_G955U1SQU6ASG1_CL12542406_QB24669289_REV00_user_mid_noship_MULTI_CERT.tgz"
As I consider that a bastard move (since they are selling Samsung's intellectual property as their own, stuff that should be public in the first place), I encourage you to share the files if you buy them, so that we can all use them and screw over these monopoly playing-intellectual property stealing bastards.
I'm now working on a recovery of my G955U1 (S8+ Qualcomm USA). I paid $25 for a god damn firmware and I'm gonna post it in next couple of days.
I'm personally having trouble of flashing the firmware (because not many flash tools support flashing .elf flash loaders), but I used one FRP tool (Octoplus FRP tool) to check the loader and it managed to send it, receive the "hello" packet, read partitions and erase the FRP partition (I assume it worked by the log), but I don't have a way to flash other partitions yet.
You people should have in mind one thing: even though certain devices have the same chipset, doesn't mean that you can use the same firehose flash loader, since manufacturers create different loaders for them and write their digital signatures into the chip (don't know is it hardwired or flashed), meaning that you cannot use Xiaomi's prog_ufs_firehose_8998_ddr.elf (just an example) to flash a Samsung device with MSM8992 chipset.
In fact, I think that each phone model and possibly even it's different firmware revisions have unique loaders, since I didn't manage to get a successful response from my G955U1 by sending G955U2 loader, and the loader which I managed to send is actually stated to be for G955U1U6 (U6 is the bootloader revision number, while U1 is the part of the model number).
Best of luck, contact me if you need help.