[Android Q&A, Help & Troubleshooting] bobdamnit:
Give me a minute and I will update this post with instructions for ya.

And I will also update this post with instructions for bkman on the D631 for restoring download mode.

Edit:

[MENTION=6859580]straitjacket525[/MENTION] Get into any form of the latest version of Ubuntu other than a virtual machine. Once inside the virtual machine, turn your phone on and let it boot to a blank screen. Afterwords, plug your phone into Ubuntu. Fire up a terminal and type the following:

ls /dev/sd*

It will output something similar to this:

/dev/sda /dev/sda1 /dev/sda2 /dev/sda5
/dev/sdb1 /dev/sdb2 /dev/sdb3 /dev/sdb4
/dev/sdb5 .......... /dev/sdb18

Usually, USB devices mount on sdb, and as the device is so screwed, I'd assume its going to be the oddball number: sdb18. Sometimes however, you'll see it on sdc. I'm going to assume its sdb, but you can use the command I give next to be sure. Just change sdb to sdc.

Lets check the partition table on sdb:

sudo gdisk -l /dev/sdb

Which will output something similar to this:

Number Start (sector) End (sector) Size Code Name
1 4194kB 71.3MB 67.1MiB 0700 modem
2 71.3MB 72.4MB 1049kiB FFFF sbl1
3 72.4MB 72.9MB 524kiB FFFF rpm
4 72.9MB 73.4MB 524kiB FFFF tz
5 73.4MB 73.9MB 524kiB FFFF sdi
6 73.9MB 76.0MB 2097kiB FFFF aboot
7 76.0MB 76.5MB 524kiB FFFF rpmb
8 76.5MB 77.1MB 524kiB FFFF tzb
9 77.1MB 79.2MB 2097kiB FFFF abootb
10 79.2MB 81.3MB 2097kiB 0700 pad
11 81.3MB 84.4MB 3146kiB FFFF modemst1
12 84.4MB 87.6MB 3146kiB FFFF modemst2
13 87.6MB 104MB 16.8MiB FFFF misc
14 105MB 138MB 33.6MiB 0700 persist
15 138MB 161MB 23.1MiB FFFF laf
16 164MB 187MB 23.1MiB FFFF boot
17 187MB 210MB 23.1MiB FFFF recovery
18 210MB 213MB 3146kiB FFFF fsg
19 214MB 214MB 524kiB FFFF fsc
20 214MB 215MB 524kiB FFFF ssd
21 218MB 219MB 524kiB FFFF DDR
22 222MB 223MB 524kiB FFFF encrypt
23 223MB 223MB 524kiB FFFF rct
24 226MB 235MB 8389kiB 0700 drm
25 235MB 243MB 8389kiB 0700 sns
26 243MB 264MB 21.0MiB FFFF factory
27 264MB 298MB 33.6MiB FFFF fota
28 298MB 299MB 1049kiB FFFF sbl1b
29 299MB 332MB 33.6MiB 0700 mpt
30 332MB 333MB 524kiB FFFF eksst
31 336MB 1961MB 1625MiB 0700 system
32 1961MB 2275MB 315MiB 0700 cache
33 2275MB 3888MB 1612MiB 0700 userdata
34 3888MB 3909MB 21.0MiB 0700 grow

If that's not what you get, try the command again with sdc. If you can, take screenshots after each one if you don't know what it means and post it here. Maybe I do. But ideally, we want to see that partition listing. If we don't, then I'm unsure how to fix it and it may not be fixable. :(

[MENTION=5343021]bkman08[/MENTION]

First, here is the D631 laf partition. Its from the TOT file, however anyone that might need it is most likely already stuck on 4.4.2 anyway.

Mega: https://mega.nz/#!XI9C0LDL!LDnPY88WNPwSldwMNa3nmqWqhH3NLf6yZkbKQNkITx0

Now, this should be done BEFORE attempting to use the TOT file. You must be rooted and and running PhilZ Touch recovery WITHOUT download mode. In other words, you blew away the laf partition for fastboot so you could unlock and install a custom recovery. This can be done in Windows, assuming you have ADB/Fastboot installed and paths setup correctly.

Place the laf.img file on your desktop. Hold shift and right click any blank spot on your desktop and select "Open command prompt window here" from the contextual menu. Once the command prompt window opens, type the following to push the laf.img file to the internal sd card:

adb push laf.img /sdcard/

Open an ADB shell:

adb shell

Obtain root in ADB shell:

su

Overwrite the laf partition with the laf.img file:

dd if=/sdcard/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf

Reboot your device into download mode:

adb reboot download

At this point, you are ready to use the TOT file.