[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] radionerd:
Old stuff from my original post:

I am starting a thread here so I can document the bootloop problem with my Note 3 SM-N900V Developer Edition. I have screen captures, files and code that hopefully will reveal the problem, and maybe one of the Guru's can help fix.

The original problem was caused several months ago after a restore from TWRP openrecovery-twrp-2.6.3.0-hltetmo This version of TWRP had a problem with the efs restore. Endless bootloops, about 28 hours later I had my DE back working after searching XDA. The fix that I found was not correct for this model .it stopped the bootloops, but the efs folder that I created was from the wrong block. The fix I found had a script to rebuild efs folder from /dev/block/mmcblk0p12.This block is modemst1 in the Qualcomm model. The script created an EFS folder in root, but it was empty. Here is the thread, but it's not right for SM-N900V DE, and many others. If I knew then what I know, "confirm the EFS block before applying any script".

Last week I tried to do a efs backup so I could eventually fix the "Factory Mode" problem from blank efs folder. That's when efs folder went away again, "reboot nvbackup" and bootloops, I can't get it to stick since. Boot loops for a week.

Tried to rebuild missing efs folder using what I think is the correct adb script for SM-N900V DE using philz_touch_6.12.8-hltevzw The usb driver

Other Note 3's have efs in mmcblk0p12

mke2fs /dev/block/mmcblk0p11
mkdir /efs
~ # mount -t ext4 /dev/block/mmcblk0p11 /efs

adb shell

mke2fs /dev/block/mmcblk0p11

mke2fs /dev/block/mmcblk0p11
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
3584 inodes, 14336 blocks
716 blocks (4.99%) reserved for the super user
First data block=1
Maximum filesystem blocks=14680064
2 block groups
8192 blocks per group, 8192 fragments per group
1792 inodes per group
Superblock backups stored on blocks:
8193

Writing inode tables: done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 33 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
~ #

I tried several other similar scripts and it would rebuild the proper /efs folder

contents of my efs folder built from mmcblk0p11 (EFS is lost on reboot)

adb shell
mkdir /efs
~ # mount -t ext4 /dev/block/mmcblk0p11 /efs
ls /efs
FactoryApp lost+found
U0BwJo4kmkmm-BgyzUZgoEY7pn8_ prov
drm prov_data
hw_offset wifi
~ #

Copy of my efs after running script, before reboot. I think some folders and files are missing.

DRM is is intact

Some of the FactoryMode files are missing too. My EFS folder is only 1.02MB

adb shell
~ # ls -lR /efs
ls -lR /efs
/efs:
drwxrwxr-x 2 system system 1024 Jan 1 2013 FactoryApp
drwxrwxr-- 4 drm system 1024 Jan 1 2013 drm
-rw------- 1 system system 3 Jan 1 2013 hw_offset
drwx------ 2 root root 12288 Jan 2 21:10 lost+found
drwxrwx--- 2 radio system 1024 Jan 2 21:11 prov
drwx------ 4 system system 1024 Jan 1 2013 prov_data
drwxrwxr-x 2 radio system 1024 Jan 2 21:11 wifi

/efs/FactoryApp:
-rwxrwxr-x 1 media system 1 Jan 1 2013 earjack_count
-rwxr--r-- 1 system system 2 Jan 1 2013 factorymode
-rwxrwxr-x 1 system radio 4 Jan 2 21:11 fdata
-rwxrwxr-x 1 system radio 0 Jan 2 21:11 hist_nv
-rwxr--r-- 1 system system 3 Jan 1 2013 keystr
-rwxrwxr-x 1 system radio 1020 Jan 2 21:11 test_nv

/efs/drm:
drwx------ 3 system system 1024 Jan 1 2013 app_ms
drwxrwxr-- 3 drm system 1024 Jan 2 21:11 sdrm

/efs/drm/app_ms:
drwx------ 2 system system 1024 Jan 1 2013 MxNw57WpMwUrwl29zlzqzCi
rAwg_

/efs/drm/app_ms/MxNw57WpMwUrwl29zlzqzCirAwg_:
-rwx------ 1 system system 1072 Jan 1 2013 -lndchIc3h7lLcBHqLCVTRw
sBQU_
-rwx------ 1 system system 1072 Jan 1 2013 2a8EC7fiuOLWZ6xkJz2qV9B
UyqY_
-rwx------ 1 system system 1072 Jan 1 2013 39j-Wt07C-dAogUK9xbr3vf
7xFY_
-rwx------ 1 system system 1072 Jan 1 2013 8oPVwf9NrhTSk5DXKuiMfak
4SQI_
-rwx------ 1 system system 1072 Jan 1 2013 AqEmxtFosQPPH-ASRTWrTN0
zFwI_
-rwx------ 1 system system 1072 Jan 1 2013 aZ532jwWSI64IZ5usuKIzxv
4BOQ_
-rwx------ 1 system system 1072 Jan 1 2013 fil8fYE2kpyD+gNF9IULyWp
JiMs_
-rwx------ 1 system system 1072 Jan 1 2013 mxrN+7RFB9miwfZrRU1xlWi
eu4M_
-rwx------ 1 system system 1072 Jan 1 2013 oUtpSCeDR40uafRBmUR7mFY
w+ik_
-rwx------ 1 system system 1072 Jan 1 2013 wHPCuFBMd5Z7-P4jMU--oBv
QDz4_
-rwx------ 1 system system 1072 Jan 1 2013 xmCXhhIu8UwnU13OCzfWzRX
OFiI_

/efs/drm/sdrm:
drwxrwxr-- 2 drm system 1024 Jan 2 21:11 data_agent

/efs/drm/sdrm/data_agent:

/efs/lost+found:

/efs/prov:
-rw-rw---- 1 radio system 0 Jan 2 21:11 libdevkm.lock

/efs/prov_data:
drwx------ 2 system system 1024 Jan 1 2013 G+8IRqTrHDIvQWyDjPjJkVB
5u6o_
drwx------ 2 system system 1024 Jan 1 2013 bG5QQZ77nDjI2757PvvQ3rP
PrVg_

/efs/prov_data/G+8IRqTrHDIvQWyDjPjJkVB5u6o_:

/efs/prov_data/bG5QQZ77nDjI2757PvvQ3rPPrVg_:

/efs/wifi:
~ #

After reboot, efs folder is gone.

>adb shell ls -a -l /efs
ls: efs: No such file or directory
~ #

efs mmcblk0p11 14336KB

MD5 c91e8d8d61148fbc73074dc460b93894