yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] ShapeShifter499:
Aww this is too bad, there are loads of old Giza tablets out there. How hard would it be to back port to this tablet? I thought the underlying hardware was nearly the same (same CPU/GPU, RAM)

---------- Post added at 08:59 PM ---------- Previous post was at 08:57 PM ----------

I'm stuck with two of these giza tablets and I was hoping someone would figure out how to get TWRP and a standard build of Android working.
[Fire HD 8 and HD 10 Original Android Development] ///Manuel:
Thank you! For Windows 10 Linux Shell install, install Ubuntu from App Store, and start adb server on the windows with same adb version as used here (39). Google very useful to access windows folders from linux shell.

See also this: https://askubuntu.com/questions/826...indows-10-to-recognize-a-connected-android-de
[Fire HD 8 and HD 10 Original Android Development] RagManX:
I feel that I'm getting close on my 7th generation Fire HD 8, but I'm not quite unlocked and TWRPed. I was on the undesireable 9920 version and self-bricked then tried to unlock and flash TWRP according to the initial post instructions. Ran into some problems that I can't re-create at the moment, but did make some progress along an alternative route to rooting and unlocking.

After failing to perform the self-brick and unlock properly I downloaded the current FireOS for the Kindle Fire HD 8 (7th generation) from Amazon (https://www.amazon.com/gp/help/customer/display.html?nodeId=G2JXLC4L34GX73TE) and installed via adb sideload through the Amazon recovery mode then wiped cache and data partitions. After rebooting then, this put me to FireOS 5.6.4.0 (636558520), which I was then able to use to temp-root and perma-root through other threads in this forum (I can help others find those later, if needed). Now, however, I'm trying to run step-1.sh and getting an error. Retrieving the GPT works fine, but the call to modules/gpt.py is failing and I can't figure out why. When run, gpt.py appears to rewrite the partition table in my gpt.bin file, but then fails after 18 partition updates with the following error:

Can anyone make sense of this and tell me what I need to do to proceed? I'm considering just going ahead and flashing the regenerated gpt.bin back to the Fire and rebooting to see if I can continue. I figure I can sideload the firmware I have downloaded again if things go awry, but I want to check in for assistance first in case there's something easy I can do to fix my problem.

Thanks!
[Fire HD 8 and HD 10 Original Android Development] diplomatic:
Wait, back up a second... You were able to downgrade from the *9920 OS to *8520 by simply flashing from stock recovery? Can you confirm that you were on 9920 when you did the adb sideload? Or did the unlock script actually run and reset the anti-rollback data? (What do you mean by "some problems"?)

I ask because it's been reported that downgrading to 8520 bricks the tablet, like this post for example:
[Fire HD 8 and HD 10 Original Android Development] RagManX:
I was definitely on 9920 (exactly:FireOS 5.6.4.0 (636559920)). Was thinking I was stuck without an unlock method. I did the brick.sh script, then (and here's where my "some problems" comes in - my own error) without paying attention ran the wrong script as the next step after intentionally bricking my tablet. I don't know what state my table was in after doing that, but it wasn't booting into FireOS and I didn't have TWRP. So, not knowing what else to do, I tried flashing the latest official FireOS from the site I linked above. When I rebooted after doing that, I had a working FireOS and going into settings showed me on FireOS 5.6.4.0 (636558520).

At this point, since I was on a TWRP-able OS, I just started over with step-1.sh and step-2.sh and was able to get where I ultimately wanted to be. I'm running SlimLP. Thanks to everyone who has worked through how to make this happen.
[Fire HD 8 and HD 10 Original Android Development] diplomatic:
Oh, but you did run a bootrom-step script, right? If so, that would explain why it didn't hang after the downgrade (anti-rollback data was already downgraded).
[Fire HD 8 and HD 10 Original Android Development] Antieco:
So ? Shall I do it being on 9920

Enviado desde mi ONEPLUS A6003 mediante Tapatalk
[Fire HD 8 and HD 10 Original Android Development] dl360:
Thank you sir! I thought 9920 was beyond saving so I did not bother. But after reading your post I decided to give it a try and the process was actually easier than I thought!

Here's exactly what I did

adb reboot bootloader

to put into fastboot

Run

brick-9820.sh

(yes, 9820. I tried brick.sh and it didn't work). In this step I actually got an error message on my computer, but it's OK as long as the DEVICE itself tells you to power off on the tablet screen. Power off and unplug the cable.

Run

bootrom-step.sh

, NOT the minimal one. Plug in the cable again. It'll reboot at the end but your screen would stay blank.

Run

fastboot-step.sh

, that's it I'm in TWRP !

As a side note other than the brick step I actually ran the rest (1, 3 and 4) on a Mac (since I already got adb on it and did not want to setup the whole Android SDK on my Linux box again). The brick step I guess you have to be on Linux since the hacked fastboot only came as ELF in the zip. To run bootrom-step on Mac, simply comment out the modemanager check in main.py.
[Fire HD 8 and HD 10 Original Android Development] Antieco:
Hi great news I will try this today .

Where do I get all that files ??

Enviado desde mi ONEPLUS A6003 mediante Tapatalk
[Fire HD 8 and HD 10 Original Android Development] Antieco:
I sucessfully flashed twrp and slimlp on 9920 !! many thanks
[Fire HD 8 and HD 10 Original Android Development] snoopfan007:
Flashes successfully the new version. GApps pico doesn't work "there was a problem communicating with google servers"
[Fire HD 8 and HD 10 Original Android Development] comegalletas:
I can confirm that I was on FireOS 5.6.4.0 636559920 on my daughters Fire HD 8 7th Gen (2017) and after adb sideloading using amazon Recovery is now on FireOS 5.3.7.0 650601220.

Please if you can point to how to permanently root and disable updates I will appreciate it (Ill do a search in the forums thou)
[Fire HD 8 and HD 10 Original Android Development] slicer2k:
Guys sorry for the noob question, but i disable ota and a lot of bloatware with diplomatic temp root usind ADB, and when i try to enter in the option System updates it goes back to the main screen. How can i check my OS version? All i know is my FireHD8 is 2017 Douglas and the os is older as the diplomatic topic, because that's when i blocked OTAs.

Thanks.
[Fire HD 8 and HD 10 Original Android Development] slicer2k:
nvm just installed the exploit, my version was 5.3.6.4, good thing i disabled OTA!
[Fire HD 8 and HD 10 Original Android Development] LivinOne:
[MENTION=7104332]k4y0z[/MENTION]

I cant root my tablet because its on 9920... so looks like I need to Brick if first, yes?

Cant get it to Brick. Could use some help please...

-- run "adb reboot bootloader" and screen goes black and at the bottom I see "=> Fastboot mode..."

-- then I run 'brick-9820.sh' and then the script waits at "< waiting for any device > " and nothing ever happens until I break out of it (CTRL-C).

-- rebooting the tablet boots into the OS just fine.

I have tried different USB ports, I'm running Ubuntu and can ADB into the tablet fine. I can run STEP-1.SH but I just get "Platform Not Supported" over and over until I break out of it (I think this is to be expected since I dont have root)

Should the tablet show as a USB device once in Fastboot mode? Its not showing with trying 'lsusb'? I have tried killing and restarting ADB also.

thx for the help!
[Fire HD 8 and HD 10 Original Android Development] glassop:
I have the same problem - waiting for device and nothing happens....

so it's not being recognised as a fastboot device even though the fire hd 8 says "=> FASTBOOT mode..." on the screen

(and I can use fastboot from windows adb - just not in Ubuntu app on windows where I need to run the brick sh)
[Fire HD 8 and HD 10 Original Android Development] LivinOne:
I have tried both native Windows (Android SDK installed) and Ubuntu (Windows Linux Subsystem)

Cant get it to work with either HD8 2017 (stock) or HD10 2018 (Lineage 12.1) ... both work perfectly with ADB (devices, reboot to Fastboot, etc.) but FASTBOOT DEVICES never shows anything. Fastboot is just waiting.

Using the same PC with Ubuntu on WLS I ran the exploit and installed everything on the HD10, no issues.
[Fire HD 8 and HD 10 Original Android Development] sethjvm:
I was able to unlock and install lineageos 12.1 on 4 hd8 running 9920 today using the brick-9820.sh. I just wanted to provide the data point that 9920 can be unlocked with minimal effort.
[Fire HD 8 and HD 10 Original Android Development] glassop:
following these steps this worked for me on a 9920 amazon build

I could not get fastboot to work through the ubuntu app on windows (adb worked fine).

this was very annoying and wasted a lot of time as no error was reported.

so I had to run ubuntu live off a usb key, made using the rufus windows app. that was also annoying as adb tools did not come with the ubuntu usb build so I had to install through the universe update.

I had to put the required sh files and bin on another sd card to get it to be accessed also and chmod the permissions.

eventually it worked as detailed above (except for the fact that the tablet did not reboot after the second bootrom-step.sh script. I just went ahead and ran the final script (fastboot-step.sh) anyways.

this worked and brought the tablet into twrp

so nice to have a clean lineage set-up over the ****ty Amazon OS.
[Fire HD 8 and HD 10 Original Android Development] mazzystr:
I thought I may have had it. The final reboot gives me the Amazon logo then a msg at the bottom left corner that says HACKED FASTBOOT.

Got any suggestions?

Update 1: Interestingly I followed the following sequence (this may/may not be accurate)...

1) boot vol up + power and got HACKED FASTBOOT msg

2) powered off

3) powered on vol down + power and got HACKED FASTBOOT msg

4) powered off

3) powered on vol up + power and got a strange Amazon pin screen. I entered 1234. Menue said data was corrupted and I got a factory reset button. I hit the button and Wahlah I'm back to a normal bootloader & os (636559820)

Update 2: I'm on CentOS 7 using rpm android-tools-20130123git98d0789-5.el7.x86_64. Fastboot is either too old or I am missing a udev rules file. It doesn't recognize the device in fastboot mode. the included fastboot binary does. That had me on a wild goose chase for hours.

Update 3: I'm also in TWRP. I think the key here is using the correct cable and the correct USB 3.0 port.

Update 4: My 2nd HD8 is rooted. Second time around I updated to 5.6.0 then followed the brick procedure. It went silk smooth!

[MENTION=7104332]k4y0z[/MENTION] Thank you for your work on this!
[Fire HD 8 and HD 10 Original Android Development] cazzzb:
using the wire method run bootroom.sh is fine, but run fastboot-step seem not reboot correct, using lsusb can see it display as Lab126 devices, the device screen is totally dark even the backlight, plug the screen cable already. is the tablet totaly brick? Thanks!
[Fire HD 8 and HD 10 Original Android Development] xunair:
Need a little help

I'm on 50.6.2.6

626533320

Rooted

Do I still need to brick my device Or can I simply run these?

Enable ADB in Developer Settings

3.*Start the script:

Code:

sudo ./step-1.sh

Your device will now reboot into recovery and perform a factory reset.

4.*Start the script:

Code:

sudo ./step-2.sh

The exploit will now be flashed and your device will reboot into TWRP.

You can now install Magisk from there.
[Fire HD 8 and HD 10 Original Android Development] dontpanic-xda:
If you can reboot in recovery mode to TWRP, then you're done. No need to brick it.
[Fire HD 8 and HD 10 Original Android Development] Airton araujo:
Hi I'm using g translator.. hope you get it...

So I would like to know if before I try to use this method what can I do? I mean what's the first step? Do I have to downgrade my Fire version (which current is 5.3.7.0 650601220 installed 10/jan/20--- and this give me a little bit of confusion bcause it looks like a downgrade, reading by, someone tells it's a mistake from Amazon... Anyway if we need to "downgrade" to 5.6.4.0 where can i get it? In amazon site only 5.3.6.8 version show up to me)

Edit: i open the 5.3.6.8 link and then starts to download 50.6.5.0 650601220

So looks like it's solved: 5.3.6.8=5.6.5.0

Well I'm still looking for 5.6.4.0
[Fire HD 8 and HD 10 Original Android Development] iakovl:
Quick question, rooted my stock OS the "old" way... Do I need to do the whole new process to unlock boot and flash twrp or do I need to do something else?
[Fire HD 8 and HD 10 Original Android Development] Kingwalk1987:
5.3.7.0 newer than 5.6.4.0??

Just a little confused by the version numbers. My Douglas says that I am on the latest software but the numbers seem to suggest that I'm on an older version.

Edit: Is it even possible to perform this on this version. I've confirmed it is the newest. 650601220. Any help is appreciated.
[Fire HD 8 and HD 10 Original Android Development] photogravi:
Thoroughly Stuck At Step 1....

Running Fire HD 8 7th Gen Fire OS 5.3.7.0 Build 650601220 factory reset before starting this process

Unknown apps allowed, developer mode enabled.

Ubuntu 18.04.3 LTS to attempt root via usb

I download amonet-douglas 1.2 from here, extract to downloads. move arm mtk-su file to bin folder. Open amonet folder in terminal. Paste command sudo ./step1-sh type in my password and then I get this. I verified this is the right mtk file to use so I am not just pasting the arm64 by accident. Even tried that one once to eliminate the possibility.

Honestly have no idea where to go from here and the tablet wants to perform 19 updates whenever I don't use it so time seems like it could be of the essence here. I am pretty handy with this kind of thing but it has been so unrelentingly frustrating so far.

Trying to use mtk-su to get temp root...
Pushing root files
bin/mtk-su: 1 file pushed. 7.3 MB/s (64780 bytes in 0.008s)
bin/minisu.img: 1 file pushed. 7.8 MB/s (1048576 bytes in 0.128s)
bin/busybox: 1 file pushed. 7.0 MB/s (587368 bytes in 0.080s)
Failed critical init step 4
This platform cannot be supported
Failed critical init step 4
This platform cannot be supported
Failed critical init step 4
This platform cannot be supported
Failed critical init step 4
This platform cannot be supported
Failed critical init step 4
This platform cannot be supported

these two lines repeat infinitely
[Fire HD 8 and HD 10 Original Android Development] mazzystr:
I had the same exact problem with my second HD8.

Ensure you are using the cord that came with it. Some functions will work and others will not with 3rd party cords. Reset it to factory default. Then update to latest firmware and follow the brick procedure.

Just do it...don't be afraid.
[Fire HD 8 and HD 10 Original Android Development] photogravi:
Thanks for the reply!

Not sure if I have the factory wire but I will check when I get out of work. It does tell me that its a low power charger but it seems the only way to avoid that is with 9w power bricks which won't be possible from most computer buses to begin with so I think this one is ok.

I am resetting it again, about to update the firmware. I was extremely confused by the brick procedure. I downloaded the amonet brick file but there were no instructions anywhere that I could find and bricking it without a clear path to follow seemed risky. The instructions on this thread seem to breeze right by the bricking process but I never got that far for it to matter anyway. Any clarity you could offer on the bricking or a more detailed link by chance?

---------- Post added at 01:36 AM ---------- Previous post was at 01:07 AM ----------

I have followed these steps to the letter as far as I can tell and it is not working. Started with a clean factory reset of my Fire HD 8 7th Gen running FireOS 5.3.7.0 650601220. According to the instructions, a brick should not be required since this is under 5.6.4.0. A poster replied to my first comment on here stating I should reset again, download latest updates, enable debug and unknown app, and try again. I just did that and got the same results. Tried the brick to downgrade and it said to follow instructions on screen but nothing appeared. Am I missing something really obvious and stupid or do I just have bad luck? Any help would be greatly appreciated.
[Fire HD 8 and HD 10 Original Android Development] mazzystr:
Follow dl360's post back on page 35...

* Charge up to 100%. Low battery can screw up or delay the process.

* Reset to factory default

* Update to latest firmware

* adb reboot bootloader to boot into fastboot

* run brick-9820.sh... you should see a msg on the screen to power off

* Power off and unplug cable

* Run bootrom-step.sh

* Plug in cable and power up.

3rd party cables will fail at this point so make sure you're using the real thing. Script will output a bunch of stuff. Page 35 has posts what that output will look like. Device will reboot but the screen will be blank.

* Run fastboot-step.sh

Device will reboot into TWRP. That's it. You're rooted. I went ahead and installed Lineage 12.1 from here. It's an old release. We're all now waiting for a modern rom. Your xda search string is gonna be "[rom][unlocked][douglas]".
[Fire HD 8 and HD 10 Original Android Development] photogravi:
EDIT: Ok I'm dumb. Realized it was just ./ But nothing ever appeared on my fire screen once I typed in YES and it started bricking the PL Header. Just says waiting for any device..

How on earth do I "run" brick-9820.sh?! I got it into fastboot. Afraid to screw it up from here but I cannot for the life of me open that file. Every command I try gives me a usage unknown command error.

Thank you for trying to help with my incompetence.
[Fire HD 8 and HD 10 Original Android Development] mazzystr:
Glad you figured it out.... your license to Linux was about to be suspended. ;)

If any of the scripts hang at "waiting for any device." it means the device is powered down or the cable is wrong.

Don't proceed to the next script until you have confirmation that prior one succeeded.
[Fire HD 8 and HD 10 Original Android Development] photogravi:
This has been such a humbling experience. I was running Ubuntu like 15+ years ago when I was 10 with no issues apt getting my sudo on all day every day and I have completely forgotten everything. OSx has spoiled me rotten.

Full disclosure, I was not able to find the official Kindle cable in my rats nest of micro usb wires when I tried it last night so I went ahead and ordered another Fire tab off amazon to guarantee I have the right wire. It should arrive in a few hours and I will give it another go. The one I ordered is an 8 8th gen, do you think I might have an easier time rooting that one?
[Fire HD 8 and HD 10 Original Android Development] mazzystr:
The cables will be the same.

HD8/HD10 (2018) codename karnak's have a similar procedure. See this link ... https://xdaforums.com/hd8-hd10/orig-development/unlock-fire-hd-8-2018-karnak-amonet-3-t3963496

I don't have any newer devices so don't have direct exp with the tooling.
[Fire HD 8 and HD 10 Original Android Development] mazzystr:
Relax. Boot into recovery. Recovery should be TWRP.
[Fire HD 8 and HD 10 Original Android Development] photogravi:
adb reboot bootloader sent me to fastboot mode, not hacked fastboot. Guessing when I wiped through TWRP it set it back to factory
[Fire HD 8 and HD 10 Original Android Development] photogravi:
I did it!!!!

Woohoooooooo

I kept trying to rebrick it and it was already done so I guess it can't be done twice. Finally did some googling and realized I could just do adb reboot recovery to get to twrp. Loaded LineageOS 12.1 with no hiccups.

For the life of me, I cannot find the G-Apps download anywhere for this version of Lineage. Any ideas on where I can find it?
[Fire HD 8 and HD 10 Original Android Development] mazzystr:
Nice work. The first time is always the hardest. Under normal conditions power off, vol down + power on for 5 secs will get you right into recovery mode / TWRP.

I'm using open_gapps-arm64-5.1-stock-20200103.

And now you're in the waiting place to quote Dr. Suess waiting for a new Lineage rom like the rest of us.
[Fire HD 8 and HD 10 Original Android Development] photogravi:
No such luck unfortunately.

Didn't realize I needed to install gapps before booting into Lineage so when I went back to install it, it bugged the tablet into oblivion. Went back into recovery and reset did format, wipe data, cache, system, and dalvik before going to install that exact gapps file but it says it cannot be installed on this device. was I supposed to unzip the file and leave it on the sd card? I installed lineage zipped on the sd and it seemed to be fine. Really thought I was past the hard part but the hits just keep on coming lol.

Thank you for your continued help.
[Fire HD 8 and HD 10 Original Android Development] supersonic11800:
mtk-su not working

The mtk-su exploit does not work any more I am running Fire OS 5.3.7.0. What should I do?
[Fire HD 8 and HD 10 Original Android Development] paulsdv:
hey mate, i have the exact same problem, run the step1.sh and get the error repeating "platform cannot be supported" " failed critical init step 4"

not clear exactly what you did to fix it? any insight would be greatly appreciated. Also i am very unfamiliar with all of this so laymans terms appreciated:)
[Fire HD 8 and HD 10 Original Android Development] Kingwalk1987:
Hi guys. Same here as previously stated by others. I'm on 5.3.7.0. Is there anyway to get twrp on my device at this time?
[Fire HD 8 and HD 10 Original Android Development] lovaduck:
Is there an unlock / TWRP solution for the 6th Generation HD-8 ? I looked, I found root but no TWRP. Tks!
[Fire HD 8 and HD 10 Original Android Development] WarAxe:
Yeah, I'm on 5.3.7.0 and the process gives me "platform cannot be supported" " failed critical init step 4" over and over.
[Fire HD 8 and HD 10 Original Android Development] bunnahabhain:
Yeah i am failing at this step as well - interestingly the version number is lower than the ones mentioned in this thread.

Any idea how we can get root, TWRP and LineageOS on this device? Amazons OS is an abomination!
[Fire HD 8 and HD 10 Original Android Development] jarrah31:
I have a Fire HD 8 2017 with 5.3.7.0 (650601220) that has a build date of 18th Dec 2019. I too have the same issues mentioned above so I wonder if they've patched the vulnerability...

I've rebooted to fastboot mode and tried 'brick.sh' and 'brick-9820.sh', but neither appear to work after typing YES.
[Fire HD 8 and HD 10 Original Android Development] Colossus96:
Okay.. how do i return to fire os as current rom is not working well for me (too much lag). How do i return to fire os while keeping twrp?
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
Rename the update.bin to update.zip and flash it with TWRP.

TWRP itself will block the flashing of bootloader/tz/preloader so there's no need of worry about that.

Regards.