[Fire HD 8 and HD 10 Original Android Development] cybersaga:
Is it normal for it to still try and make you register your device with an Amazon account? It also tried to look for updates. Still trying to figure out how to get out of the registration. It won't let me past.

---------- Post added at 08:23 PM ---------- Previous post was at 08:22 PM ----------

There we go! It eventually gave me a "Not now" button.

---------- Post added at 08:54 PM ---------- Previous post was at 08:23 PM ----------

Root confirmed! Thanks for your quick help tonight [MENTION=9325417]t0x1cSH[/MENTION]

This should answer your question [MENTION=1744821]x410x[/MENTION] (skip down to "Building the system image"), but I'm including more information for everyone else's benefit too.

Setup a Ubuntu VM (if you need to)

I did this in VMWare (free) with a Ubuntu image from osboxes.org (make sure you pick the VMWare one). The password for those images is "osboxes.org".

Tell VMWare to automatically connect any new USB devices to the VM:

In the top left of the window open the "Player" menu -> File -> Preferences

Under "USB" select "Connect the device to the running virtual machine"

Click OK

Open a terminal (right-click the desktop and "Open Terminal")

sudo apt-get remove modemmanager
sudo apt-get install android-tools-adb android-tools-fastboot android-tools-fstools python3-serial attr

Building the system image

I downloaded the OTA archive from here. For convenience, download it inside your VM then you don't need to worry about moving it over.

Rename that .bin file to .zip and extract it to your desktop.

Follow steps 3-5 in the OP. I'll assume the image is mounted at ~/Desktop/system

Many of these steps are taken from the hardmod thread, but more detailed.

Download SuperSU version 2.79.

I'll assume these paths:

system.img is mounted at ~/Desktop/system

SuperSU is extracted to ~/Desktop/supersu (you only need the arm64 and common folders)

Open a terminal:

sudo bash
cd ~/Desktop/system

mkdir app/SuperSU
chmod 0644 app/SuperSU
setfattr -n security.selinux -v "u:object_r:system_file:s0" app/SuperSU

cp ../supersu/common/Superuser.apk app/SuperSU/SuperSU.apk
chmod 0644 app/SuperSU/SuperSU.apk
setfattr -n security.selinux -v "u:object_r:system_file:s0" app/SuperSU/SuperSU.apk

cp ../supersu/common/install-recovery.sh etc/install-recovery.sh
chmod 755 etc/install-recovery.sh
setfattr -n security.selinux -v "u:object_r:system_file:s0" etc/install-recovery.sh

mv bin/install-recovery.sh bin/install-recovery-old.sh
ln -s /system/etc/install-recovery.sh bin/install-recovery.sh

cp ../supersu/arm64/su xbin/su
chmod 0755 xbin/su
setfattr -n security.selinux -v "u:object_r:system_file:s0" xbin/su

cp ../supersu/arm64/su xbin/daemonsu
chmod 0755 xbin/daemonsu
setfattr -n security.selinux -v "u:object_r:system_file:s0" xbin/daemonsu

cp ../supersu/arm64/supolicy xbin/supolicy
chmod 0755 xbin/supolicy
setfattr -n security.selinux -v "u:object_r:system_file:s0" xbin/supolicy

cp ../supersu/arm64/libsupol.so lib64/libsupol.so
chmod 0644 lib64/libsupol.so
setfattr -n security.selinux -v "u:object_r:system_file:s0" lib64/libsupol.so

mv bin/app_process bin/app_process_backup
ln -s /system/xbin/daemonsu bin/app_process

> etc/.installed_su_daemon
chmod 0644 etc/.installed_su_daemon
setfattr -n security.selinux -v "u:object_r:system_file:s0" etc/.installed_su_daemon

From there, continue at step 7 in the OP.