[AT&T Samsung Galaxy Note5] Delgoth:
If you, or anyone else reading for that matter, who has updated their device to the Revision 4 Bootloader could try and do these tests below and report back I'd soooo appreciate it. I'm going to spell out what and how to perform the test. If you could please follow the directions exactly as I have them written and report back exactly what you did and the results. Being as Specific as possible please. Posting results of a test without explaining your method from start to finish and giving no insights as to why does not help us further development for this device. If you have a device on Binary 1,2,or 3, I still recommend NOT updating to revision 4 if you want a more unlocked device. I have a ton of info concerning the older builds if you want an in depth review PM Me.

EDIT: Although it seems using the FlashFire method from Test #2 (Post 57), almost anything can be flashed, except the bootloader. But it's not fully tested what WON'T work.

If the testing method results in a failure, that is okay. And if, after you have tried my steps, you have an idea to try then go ahead. But I'm only asking you to follow the steps I have laid out, because that is how I would personally perform the test myself. This way I can rule out the ideas I personally have. I just no longer have this device to test on. I'm totally willing to support the development as much as I can still.

The list of steps might seem really involved at times, but bear with me since I can't sit next to you while you do this.

Test #1 (step #16 is important to get right if #15 doesn't work.)

Testing: COMBINATION_FA51_N920AUCU4APL1

Step 1.) Start Your Device Normally. Turn on "OEM Unlock" & "USB Debugging" from the Developer Settings Menu. If you can, also disable "Verify Apps via USB" from the Developer Settings.

Step 2.) Connect the Device to your PC and make sure to check "always remember" when the device asks you to accept the RSA Key for USB Debugging.

Step 3.) Remove SIM Card (if applicable), and Power Device Off.

Step 4.) Start the device in Download Mode from the Powered Off state by holding down [POWER+VOL DOWN+HOME KEY]

Step 5.) Connect Device to your PC, then open up ODIN 3.12.5 (Making sure to right click ODIN and run as Adminstrator)

Step 6.) Load the Revision 4 Factory Binary (COMBINATION_FA51_N920AUCU4APL1) into the AP Slot of ODIN.

Step 7.) On the Options Tab of ODIN 3.12.5 check the options:

"Auto Reboot" + "Nand Erase" + "Re-Partiton" + "F. Reset Time"

. Make sure the top four check boxes are checked in ODIN.

Step 8.) Press START in ODIN and begin flashing the firmware to the device.

Step 9.) Allow the device to boot up fully once ODIN has finished flashing the firmware. The factory Binary tends to take longer than a normal stock rom to boot initially.

** I have a sneaking suspicion the ENG Boot I have for binary 4, has simply been plucked from the combination firmware and labeled as an ENG Boot.img. If this is true, the device will still boot using the full Factory Binary after flashing this kernel. Although the default.prop from the UCS4 ENG Boot, states "ro.debuggable=1" & "persist.sys.usb.config=mtp,adb". Meaning the device can access ADB even while powered off charging. The thought here was correct here. Not to mention, when I unpacked the boot.img from 4APL1 factory binary the RAMDISK is indentical to the ramsdisk inside the UCS4_Eng Boot. Two dollars wasted I suppose. Why would people give out the Factory Binary for free, but then charge you for the boot.img they just handed you for free? This is why all these files are leaking slowly but surely.

END OF TEST #1 INSTRUCTIONS

===========================

===========================

EDIT: I've been told by a user here that this particular 4CQB2 build contains what seems to be an ENG Recovery Image that can bypass DM-Verity Issues on Binary 4 Devices. It has been reported to really work and fix DM-Verity issues by allowing the device to boot anyways. The Link to it: https://firmware.gem-flash.com/index.php?a=browse&b=file-info&id=22736

When [MENTION=3962799]lownslow200sx[/MENTION] reported when he messed up his Device Root Key (DRK) & DM-Verity Hashes, by flashing a modem from the N920T to his N920A via FlashFire; He couldn't get the device to boot in a stable manner. What fixed the issue and allowed the device to boot normally again was flashing the recovery.img in the above 4CQB2 firmware.