[Miscellaneous Android Development] wd5gnr:
WARNINGS:

1) You should read this carefully a few times before you try it.

2) If you do not understand some part of it DO NOT DO THIS

3) I am not responsible in any way for anything that happens including but not limited to hair loss, bricked tablet, or halitosis

4) I didn't figure any of this out. I just reversed what social_media_concepts did in a batch file for the T2 option and found the right fastboot executable. That's it.

5) You might brick your tablet. Right now there are limited options to fix that because these are so new. Do you really need root? Turn back now, I beg you.

6) Until someone else replies that they did this, there could be typos or errors in this. Please report errors. Perhaps the first person to duplicate might chime in, too.

If you are using Linux, here's the steps I took. Of course, you need adb. However, you need fastboot from here: https://software.intel.com/en-us/forums/topic/494961 (link to file: http://www.mediafire.com/download/pbr4b2x2ig9b2m5/fastboot). Be sure to use that fastboot and not one installed through your package manager.

You will need to chmod +x it -- If you download it to /tmp, for example:

chmod +x /tmp/fastboot

I am not sure, but you may also need the following in your udev rules (I added it to /lib/udev/rules.d/70-android-tools-fastboot.rules

SUBSYSTEM=="usb", ATTRS{idVendor}=="8087",ATTRS{idProduct}=="0fff", MODE="0666"

You might try it without first. Worst case, run fastboot as root. But I did do that. If you do it, you need to restart udev or reboot after.

Get the SuperSU apk mentioned in the OP and put it on your tablet where you can find it (adb push, download, copy, whatever).

Now, get the file mentioned above and unzip with 7z. I noticed there was a newer version in the thread, but I pulled this one since we "know" it works.

Command line:

7z x IntelAndroid-FBRL-05-16-2015-PTR.7z

Get into fastboot mode. You can do this with the volume switch, but it is better to do it this way -- if you can't find your device, you don't need to go further until you fix that!

adb reboot-bootloader

By the way, it goes without saying you have to have the tablet connected to the USB port, right?

Ok once you are in the fastboot mode, BE SURE YOU ARE USING THE FASTBOOT YOU DOWNLOADED FROM MEDIAFIRE. I put mine in /tmp so... Get in the unzipped directory (IntelAndroid-FBRL-05-16-2015-PTR).

Probably need to triple check the command lines before hitting enter because if you get them wrong, I don't know what would happen.

Note: The first /tmp is YOUR /tmp directory. The second /tmp is the one on the device and you should NOT change the second one even if you move the fastboot binary

/tmp/fastboot flash /tmp/recovery.zip FB_RecoveryLauncher/recovery.zip
/tmp/fastboot flash /tmp/recovery.launcher FB_RecoveryLauncher/recovery.launcher
/tmp/fastboot flash /system/bin/cp FB_RecoveryLauncher/recovery.trigger.original
/tmp/fastboot oem backup_factory

On the flashes, if you botch the last part, you'll just get an error message. No worries. If you botch the first part... I don't know... don't botch the first part. If you get a "waiting on device" for awhile, you forgot to use the updated fastboot command and are using an old one. OR... you need to add the udev rules like I did OR you might be able to run it as root. If running as root doesn't help (or you just don't want to trust it) then add the udev rule and restart udev or reboot. If it works the first time, you are good to go for the rest.

That's it. You'll get some sign on messages about the author (social_media_concepts) and some fstab rebuilding. That means it is working. You'll eventually get to a tiny font CWM screen. Flash the SuperSU zip you loaded previously. Reboot. Do not let it "fix" root.

That's it. I was worried that /system/bin/cp needed to be saved, but it appears it gets reloaded somewhere or the trigger is innocuous if everything else isn't set up.

UPDATE: I wrote a quick and dirty shell script to do this. It assumes you have the "new" fastboot in the same directory the script is in. You should start the script from the directory it is in (and it should be in the IntelAndroid-FBRL-05-16-2015-PTR directory) although if you aren't there, it will try to go there. This works for me. It may or may not work for you. It might be slightly safer than trying to type it all in by hand. Then again, there isn't much error checking, so if things go badly.... as always, the risk is yours.