[Paid Software Announcement and Discussion] Chainfire:
Sorry for the delays in response, I was on vacation :)

It seems from your lastlog that the actions were actually performed, your screen was just black. Could you perhaps look really closely, possibly aided with a flashlight, and see if the backlight isn't just off ? This seems to be happening for more users.

It is common for the first boot after FlashFire backup/restore/etc to fail. The reason is of yet unknown. Be sure to try booting multiple times. Perhaps you need to flash the correct modem via Odin for Android to boot, though?

If you can replicate this issue I would be happy to have the file, to see why it crashes things.

This is only a partial log. I need a full log to be of assistance.

Sorry, I'm not sure yet why this sometimes happens.

tw's author didn't actually find the exploit, he just ported it to Android, in a few hours. tw would exist even if this guy didn't - he got advice and help from several other exploiters, each of which could have probably released it themselves (you don't know their names, just how they like it). He even managed to mis-package SuperSU even after ample advice from yours truly, and I had to release an update to SuperSU itself to fix all those broken users... This guy is really good at riding credit and making fame, I'll give him that, though. Non OEM specific exploits have become significantly rarer due to SELinux anyways - most of the roots you see today for locked devices are exploits in OEM-specific components (bootloaders, radios, apps), rather than security issues with Android's core or the Linux kernel as was regularly the case before.

Might sound like I'm bashing the guy here, or lecturing you, neither is the intent. I'm just trying to point out that the perception of tw is very different from the reality of tw.

I am aware of the issue, I'm not sure yet why it actually happens, though.

There hasn't been any progress made. Neither myself nor [MENTION=402300]amarullz[/MENTION] has put any work in. It does appear he has a newer version of his graphics driver for his recovery file explorer than is currently used in the publicly available installer sources. I expect this will be ported to the installer at some point. Additions to make it work with FlashFire across all devices should be made at that stage - it seems like a waste to try to port my graphics core to the outdated graphics code currently in the installer. I should probably talk to the guy at some point to see what his plans are for this. I expect it'll be a while for devices where it doesn't already work out of the box.

Did you skip /cache for this backup, because it reported an issue in your previous post?

Can you paste the output of "mount" from adb shell or terminal emulator, assuming the issue still exists for you?

You are not the only one with this problem. Looking into it.

Update to latest version.

Did you rename the file, by any chance? This breaks the hash check in Odin.

This post needs an actual description of the problem, and the logs requested in post #1.

Not sure, could be related to MultiSystem. Or TWRP, if you used that in between. On some Android versions, internal storage is based on /data/media/, on others it is /data/media/x/ (where x is 0 for the default user). This can get messed up when transitioning between versions. You can indeed just move the files to the correct location using any (root) file explorer.

Please post the logs. See the first post of this thread.

That depends on exactly what you want to flash. VZW S6s have a locked bootloader, so it won't boot custom kernels. Not sure about modified system. Consult VZW S6 experts in the relevant forums.

In FlashFire, tap the card that mentions Samsung protections, and read the popup.

There's a button to make a new .tar.md5 if you open an existing one for flashing (next to the OK button). This is generally used to create a package with bootloaders and modems to flash via ODIN. You cannot backup to a .tar.md5 file, that option does not exist in FlashFire. Emergency restore of a backup can be done via TWRP - an installable ZIP is placed in each backup folder. If that is not available for your device, you have to do a normal ODIN flash and root it somehow. On locked devices this will usually mean going back to 4.x, rooting it with towelroot or some such, then using FlashFire to flash Lollipop and keep root.

RAW backups are used specifically for block-level OTAs such as employed by some of the newer Nexus devices. You don't ever need to use this option on your device.