[Android Q&A, Help & Troubleshooting] droidvoider:
**** Warning **** This is the most dangerous developer tool I've seen in a very long time. You can easily smoke your device with this without even trying.

====>] farm-root updated for Note 5 [<====

Ok guys it works for recovery or boot. It will pull an image or push an image.

https://github.com/droidvoider/Note5-Root-Farmer

toolbox directory compressed for recovery and boot, matches above code

boot push / pull --- aosp toolbox directory

recovery push / pull --- aosp toolbox directory

-DFARM_BOOT changes from recovery to boot in the shared.c

-DFARM_PULL is for pulling in toolbox,c / bridge.c, no define means compile to push.

-DDEBUG is for logcat messages, recompile minus this option to reduce binary size a lot

===>] What was wrong? [<===

When I got this working at first a couple weeks ago I thought I checked the path but I didn't. That and the updates to dirtycow are the only differences between mine and freddies version. (except that I also added push boot.img)

partitions:

/dev/block/platform/15570000.ufs/by-name/RECOVERY

/dev/block/platform/15570000.ufs/by-name/BOOT

directory containing sym links: (shell is allowed to ls -la inside this directory and view partition links!)

/dev/block/platform/15570000.ufs/by-name/

===>] So why can't we do this to the bootloader? [<===

I am now focusing just on this idea!!

Notes: I have a suspicion that if we used the bootloader from another device the numbers won't match, such as mac, and that will be permanent hard brick. I need someone to copy their bootloader partition both locked and unlocked using a tool I create for that purpose. (anyone got a friend who will help out?) Obviously this will not be an AT&T version.

===>] Basic instructions [<===

Download and unzip to a Ubuntu directory (android sdk + ndk needed)

Plug in your device and make sure you can adb shell

Add a screen lock pin to your device first

In terminal change to the directory first then make log

Open another terminal then you compile the sources for pushing or pulling as follows

make pull_boot, make pull_recovery, make_push_boot, make_push_recovery

You will be hung on "waiting for process to complete"

On your phone enter your pin, then go to settings, remove the screen lock pin..

close settings

On your phone again now go add back a lock screen pin.. close settings.

repeat the lockscreen thing it will go...

===<> Breaking my rule and playing with it now <>===

I tried boot.img altered with Assayed kitchen modified heavily but no changes, I think it was written back on reboot I bet recovery-from-boot.p really replaces this.

So I tried with recovery.img from Assayed kitchen modified heavily, I got a big blue error telling me to take my phone to AT&T

(if you get an error use heimdall to flash the specific file(s) or use odin to flash your AP file from the firmware.)

Continue Notes: I have confirmed I am replacing the boot.img and recovery.img completely freddie knocked it out of the park fellas. I have only tried heavily modified versions, I have not tried modifying the pulled version yet. If I flash anything not factory the phone has an error screen telling me to take it to at&t. pwr+vol. down I have to release and retry but eventually I get it to reboot, then download mode. Then simply flashing back what I replaced with farm-root gets me back up again.

If I flash recovery.img from t-mobile note 5 twrp it won't give me the error message until I attempt to enter recovery! After that it will always give the error. I tried putting twrp as the boot.img but that fails too, it does look like it almost loads something then I get the chain of trust error.

continuation of notes: I've still only tried heavily modified versions but I have unpacked the boot.img and recovery.img I've pulled, they are complete. If I flash recovery.img first then reboot without entering recovery it doesn't error. (until you enter recovery then it won't allow boot)... So instead I flashed boot.img also. Now boot.img isn't replaced on startup, I get the blue error message and this time I have to flash both recovery.img and boot.img to get the phone working again. (what does that mean?, mostly it confirms we wrote to both partitions which I have also confirmed through pulling / testing after writes) one thing is for sure this is a lot more fun then having nothing.