[Fire HD 8 and HD 10 Original Android Development] thinklost:
\\\Simple Rooting And Unlocking And TWRP for Fire HD 8 2017 (7th Gen) on Fire OS 5.3.7.0\\

From what I understand from reading these last pages:

1) Ignore almost EVERYTHING in the first post of this thread except the files youll need later. (Right?)

2) Follow Airton araujo post and use brick-9820.sh

OR

2B) Follow speedrcr and use brick.sh

???!??!??!??!??

I am so very lost.

So far I've:

1)Set up a VirtualMachine with Linux Mint (Will a VirtualMachine Work or MUST it be a USB Live or actual Installation?)

2) Transferred the necessary files listed in OP onto the desktop in the Virtualmachine

3) Ran the updates to Linux from OP

4) Enabled ADB in Dev Settings on Tablet from OP

5) Plugged in my Fire and allowed the VirtualMachine to Recognize it.

6) Began the Instructions Via Airton

***********Im Going to rewrite all the instructions very clearly if I succeed

Utter Failure.

When my Step-By-Step Guide mentioned encountering errors then switching scripts around from older versions into the new folder and the like I should have perhaps raised and eyebrow and waited patiently for some clearer instructions. I used Brick-9820.sh. I finally achieved the results we wanted. Great.

Now I was on the Step 3. Where in Airtons attempts he was met with many errors. My errors were not the same as his:

Load Payload works

Then Send Payload

Lets Rock

Wait for the payload to come online...

Traceback I get a serial exception device reports readiness to read but no data. "Device disconnected or multiple access?"

The entire time my device is plugged in I hear the USB mounted sound then the USB disconnected sound like its restarting over and over.

I cant turn it on. When I plug it in I just keep hearing it Mount then Unmount every 10 to 12 seconds.

Great. So lets try Step 1 again, to put it into Bootloader

error no devices emulators found

When it is briefly recognized by the VM its Mediatek Inc MT6220 Phone. . .

Oh Please Tell me I haven't "Bricked" this thing. Its just Screen not coming on, but keep hearing the connect and disconnect sound. Not recognized so cant run ADB commands on it.

Update: Amazingly step 3 still recognizes it and tries to send the payload but it is never able to in time before the darn thing disconnects again and reconnects seconds later so the process is being interrupted.

Update 2: So I continuously push command 3 as it is seemingly the only thing I can do that even senses a figment of the state my device is in. I begin timing with a stopwatch the amount of time the device stays connected before failing. Approximately 28 seconds. I continue to push it and force it to restart. Over and Over, while reading through threads and googling things. On try 46, with me now some 4 hours into this ordeal the payload gets through.

Summary

To anyone just joining us as I have, with a working knowledge of following steps but not understanding all of the underlying processes behind them I

highly

recommend holding off on venturing onward until a proper revision and rewrite of the guide is made in consideration to the latest update everyone is trying to do this from. Something maybe started from scratch. There are too many artifacts from prior versions and methods embedded in the latest guide. And then for those of us working out kinks here at the end of the thread there are still far too many issues for anyone to have a guaranteed time of it with safety and consistency. So many posts and even sometimes steps within a guide end up contradicting others. This is but the frantic way of the bleeding edge at the curve of the horizon but for the average user wait until the pioneers have posted their edits.