[UNLOCK][ROOT][TWRP][UNBRICK] Fire HD 8 2018 (karnak) amonet-3

Search This thread
since u also got a Fire HD 10 2019 n i notice u mentioned in the toolbox thread u been using it for a year. if u dont mind, plz check its serial number. if u purchase it in late 2019, it should look like xxxx xx05 9xxx xxxx n it is rootable.
I checked the S/N and it is definitely the xx05 9xxx variety. Interesting, I had pretty much given up on root access for this tablet since as you say it's doing about 90% of what I want it to do already, although root would be nice for some things like Titanium Backup. In the morning when I'm fully awake (it's almost 3 AM here as I type this :) ) I'll look up the article. Thanks again!
 

topcorner

Member
Feb 26, 2011
36
0
I bricked kindle fire a while back but I can't remember exactly what I had done. Anyways I decided to look at unbricking it again. It stays on the Amazon logo screen.

I quite certain I'm on a version before 6.3.1.2. It says "If Recovery OR FireOS are still accessible (or your firmware is below 6.3.1.2) there are other means of recovery, don't continue." Can I not open up the tablet and use the bootrom-step.sh script?

I also used fastboot-step.sh and I get the following output and then back stuck on the Amazon logo screen again.
Code:
Waiting for preloader
Found port = /dev/ttyACM0
Handshake
Preloader ready, sending FACTFACT

Any help will be appreciated.
 

binarymelon

New member
Apr 15, 2015
1
0
It depends on when it was made if it was made after I think January 2020 then your tablet got the hardware fix and your stuck with FireOS
Which directions would someone follow if their device was manufactured before that? The OP and subsequent post aren't entirely clear. I purchased mine July '19, but it's updated to 7.3.1.8.
 

Falcon342

Senior Member
Aug 24, 2020
190
66
Which directions would someone follow if their device was manufactured before that? The OP and subsequent post aren't entirely clear. I purchased mine July '19, but it's updated to 7.3.1.8.
Here would 2 good places to start:
One thing i should note is that after unlocking the bootloader you cant use FireOS 7 you must use FireOS 6 or a custom Rom because FireOS 7 will get stuck in a bootloop, your device currently being on FireOS 7 should not be a issue i havent heard anybody say this method not working on FireOS 7.
 
Last edited:

DrWu

Senior Member
Feb 10, 2015
106
3
I got a brand-new, unmodded 8th Gen Fire HD 8 / Fire OS 6.3.0.0 to root. Next I ran "sudo ./fireos-step.sh", which terminated with 'Rebooting to TWRP' but it's boot-looping to the Amazon logo.

"adb devices" doesn't 'see' it and if I hold the left side of the volume button it shows "=> RECOVERY mode..." in the lower left corner.

Is it 'fastboot' time or should I crack the case?
 

Falcon342

Senior Member
Aug 24, 2020
190
66
I got a brand-new, unmodded 8th Gen Fire HD 8 / Fire OS 6.3.0.0 to root. Next I ran "sudo ./fireos-step.sh", which terminated with 'Rebooting to TWRP' but it's boot-looping to the Amazon logo.

"adb devices" doesn't 'see' it and if I hold the left side of the volume button it shows "=> RECOVERY mode..." in the lower left corner.

Is it 'fastboot' time or should I crack the case?
It might be time to open it up, but first try holding the power button until it shuts down, then hold power and volume down and see if it boots in twrp,

if that doesnt work then its time to open it up or go digging through these threads and see if somebody else has had the same problem.

(if it wont shutdown by holding the power button you either have to wait for the battery to die or open it up and unplug then plug in the battery)
 
Last edited:

DrWu

Senior Member
Feb 10, 2015
106
3
It might be time to open it up, but first try holding the power button until it shuts down, then hold power and volume down and see if it boots in twrp,

if that doesnt work then its time to open it up or go digging through these threads and see if somebody else has had the same problem.

(if it wont shutdown by holding the power button you either have to wait for the battery to die or open it up and unplug then plug in the battery)
Once I used the proper button technique, it booted to TWRP. And I'm sorry to have to ask this but I'm overwhelmed by the details on the first page about bricking and unbricking, but if TWRP loads, I should be ready to load the custom ROM, yes?

And should I flash Magisk immediately or wait until after flashing the ROM?
 

Falcon342

Senior Member
Aug 24, 2020
190
66
Once I used the proper button technique, it booted to TWRP. And I'm sorry to have to ask this but I'm overwhelmed by the details on the first page about bricking and unbricking, but if TWRP loads, I should be ready to load the custom ROM, yes?

And should I flash Magisk immediately or wait until after flashing the ROM?
Now that twrp is working you can flash the custom rom (dont forget to do the advanced wipe to get rid of FireOS) i recommend getting the Rom setup first then flash Magisk,

Magisk flashing instructions:
(Taken from: https://topjohnwu.github.io/Magisk/install.html)

1. Download the files below on your Fire Tablet

2. install the Magisk-v22.1.apk provided below (you need to enable "allow installion from unknown sources" in settings > security disable after apk is installed)

3. reboot into twrp, then in twrp choose "install" and navigate to the magisk-v22.1.zip swipe to install, wait for it to finish, now your done reboot into android and now you have root.


uninstalling Magisk/removing Root:
First uninstall the Magisk app
Now reboot into twrp and choose "install" and now navigate to uninstall.zip swipe to install and now Magisk/Root with be removed, reboot and Magisk should be gone.
 

Attachments

  • Magisk-v22.1.zip
    6.4 MB · Views: 6
  • uninstall.zip
    6.4 MB · Views: 3
  • Magisk-v22.1.apk
    6.4 MB · Views: 5
Last edited:

JayUK74

New member
Jan 18, 2021
2
0
Hi all,

Like everyone else on here I need some help.... :(

My FHD8 has been running this ROM for a while, but for some stupid reason I decided to mess about with it. I have managed to break the recovery partition. The tablet still boots fine in to LOS, but TWRP no longer works. It simply sits on the "Recovery Mode" white text for a while and then reboots.

If I try to do a fastboot flash recovery I got the error "'the command you input is restricted on locked hw'".

I can not re-run this fireos-step script as the OS is no longer FireOS. I've manually ran mtk-su but that reports "This firmware cannot be supported"

Anyone got any ideas how I can get TWRP recovery working again?

Thanks,
J.
 

Michajin

Senior Member
Oct 23, 2012
1,245
486
Hi all,

Like everyone else on here I need some help.... :(

My FHD8 has been running this ROM for a while, but for some stupid reason I decided to mess about with it. I have managed to break the recovery partition. The tablet still boots fine in to LOS, but TWRP no longer works. It simply sits on the "Recovery Mode" white text for a while and then reboots.

If I try to do a fastboot flash recovery I got the error "'the command you input is restricted on locked hw'".

I can not re-run this fireos-step script as the OS is no longer FireOS. I've manually ran mtk-su but that reports "This firmware cannot be supported"

Anyone got any ideas how I can get TWRP recovery working again?

Thanks,
J.
Run the boot-fastboot from the amonet script. To flash you have to be in the hacked unlocked fastboot. From there you can flash recovery or run the fastboot step script
 

JayUK74

New member
Jan 18, 2021
2
0
Run the boot-fastboot from the amonet script. To flash you have to be in the hacked unlocked fastboot. From there you can flash recovery or run the fastboot step script
Hi,

It was stating that the device was locked/restricted. After many hours I've finally fixed it - I resorted to opening the case and doing it that way. I've now got working recovery and LOS.

Thanks for the reply :)

J.
 

Michajin

Senior Member
Oct 23, 2012
1,245
486
Hi,

It was stating that the device was locked/restricted. After many hours I've finally fixed it - I resorted to opening the case and doing it that way. I've now got working recovery and LOS.

Thanks for the reply :)

J.
Maybe you didn't understand my post. You run the boot-fastboot to get into the "unlocked" fastboot. By running adb reboot bootloader you are in the locked fastboot.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 35
    Read this whole guide before starting.

    This is for the 8th gen Fire HD8 (karnak).

    Current version: amonet-karnak-v3.0.1.zip

    This is based on @xyz`s original work, but adds some features such as reboot to hacked BL.
    It also intends to simplify the installation process.
    If you are already unlocked you can simply update by flashing the ZIP-file in TWRP.


    NOTE: If you are on a firmware lower than 6.3.1.2 this process does not require you to open your device, but should something go horribly wrong, be prepared to do so.


    What you need:
    • A Linux installation or live-system
    • A micro-USB cable

    Install python3, PySerial, adb, fastboot dos2unix. For Debian/Ubuntu something like this should work:
    Code:
    sudo apt update
    sudo add-apt-repository universe
    sudo apt install python3 python3-serial adb fastboot dos2unix

    1. Extract the attached zip-file "amonet-karnak-v3.0.1.zip" and open a terminal in that directory.


    NOTE: If you are already rooted, continue with the next step, otherwise get mtk-su by @diplomatic from here and place (the unpacked binary) into amonet/bin folder


    2. Enable ADB in Developer Settings

    3. Start the script:
    Code:
    sudo ./fireos-step.sh


    NOTE: If you are on a firmware newer than 6.3.0.1, a downgrade is necessary, this requires bricking the device temporarily. (The screen won't come on at all)



    WARNING: There have been numerous reports that would indicate a hardware-change that doesn't allow access to the bootrom.
    When bricking these devices there is currently no known way to unbrick.
    This makes the hardware-method currently the safest option.



    To brick firmware 6.3.1.2 use the attached brick-karnak.zip, boot into fastboot
    Code:
    adb reboot bootloader

    and run
    Code:
    ./brick-6312.sh

    Make sure ModemManager is disabled or uninstalled:
    Code:
    sudo systemctl stop ModemManager
    sudo systemctl disable ModemManager

    After you have confirmed the bricking by typing "YES", you will need disconnect the device and run
    Code:
    sudo ./bootrom-step.sh
    Then plug the device back in.

    The device will reboot into TWRP.

    You can now install Magisk from there.


    Going back to stock

    Extract the attached zip-file "amonet-karnak-return-to-stock.zip" into the same folder where you extracted "amonet-karnak-v3.0.1.zip" and open a terminal in that directory.

    Then run:
    Code:
    sudo ./return-to-stock.sh

    Your device should reboot into Amazon Recovery. Use adb sideload to install stock image from there. (Make sure to use FireOS 6.3.0.0 or newer, otherwise you may brick your device)

    Important information


    Don't flash boot/recovery images from FireOS (FlashFire, MagiskManager etc.)

    TWRP will prevent updates from overwriting LK/Preloader/TZ, so generally installing an update should work without issues (only full updates, incremental updates won't work).

    For ROM developers there is still an option to overwrite these, which should only be done after thorough testing and if needed (LK should never be updated).

    It is still advised to disable OTA.

    Very special thanks to @xyz` for making all this possible and putting up with the countless questions I have asked, helping me finish this.
    Special thanks also to @diplomatic for his wonderfull mtk-su, allowing you to unlock without opening the device.
    Thanks to @Kaijones23 for testing.
    13
    Unbricking / Unlocking with Firmware 6.3.1.2+

    If Recovery OR FireOS are still accessible (or your firmware is below 6.3.1.2) there are other means of recovery, don't continue.

    If your device shows one of the following symptoms:
    1. It doesn't show any life (screen stays dark)
    2. You see the white amazon logo, but cannot access Recovery or FireOS.

    If you have a Type 1 brick, you may not have to open the device, if your device comes up in bootrom-mode (See Checking USB connection below).
    1. Make sure the device is powered off, by holding the power-button for 20+ seconds
    2. Start bootrom-step.sh
    3. Plug in USB

    In all other cases you will have to open the device.

    Make sure ModemManager is disabled or uninstalled:
    Code:
    sudo systemctl stop ModemManager
    sudo systemctl disable ModemManager


    NOTE: If you have issues running the scripts, you might have to run them using sudo.
    Also try using different USB-ports (preferably USB-2.0-ports)


    Open the device and short the pin marked in the attached photo to ground while plugging in.
    1. Extract the attached zip-file "amonet-karnak-v3.0.zip" and open a terminal in that directory.

    2. start the script:
    Code:
    sudo ./bootrom-step.sh

    It should now say Waiting for bootrom.

    3. Short the device according to the attached photo and plug it in.

    4. When the script asks you to remove the short, remove the short and press enter.

    5. Wait for the script to finish.
    If it stalls at some point, stop it and restart the process from step 2.

    6. Your device should now reboot into unlocked fastboot state.

    7. Run
    Code:
    sudo ./fastboot-step.sh

    8. Wait for the device to reboot into TWRP.

    9. Use TWRP to flash custom ROM, Magisk or SuperSU

    Checking USB connection
    In lsusb the boot-rom shows up as:
    Code:
    Bus 002 Device 013: ID [b]0e8d:0003[/b] MediaTek Inc. MT6227 phone

    If it shows up as:
    Code:
    Bus 002 Device 014: ID [b]0e8d:2000[/b] MediaTek Inc. MT65xx Preloader
    instead, you are in preloader-mode, try again.

    dmesg lists the correct device as:
    Code:
    [ 6383.962057] usb 2-2: New USB device found, idVendor=[b]0e8d[/b], idProduct=[b]0003[/b], bcdDevice= 1.00
    5
    Success

    Read this whole guide before starting.

    This is for the 8th gen Fire HD8 (karnak).

    @k4y0z thank you so much for your work on this project. About oh...15 pages back you answered a few of my questions, and I finally today got around to giving this a whirl. It was so simple, and worked perfectly. You took a insanely complicated set of instructions into 3 easy to use scripts and you should be applauded for it.

    For anyone who wants to do this (on a current 6.3.1.2 w/ the soft brick method), here are some tips.
    -Factory reset and wipe everything before you start. If you need to keep your data back it up, from a clean boot this works slick with no issues
    -Skip network setup on initial wizard, go straight to enable USB debugging, etc blah
    -Try several USB cables (I had to try 4 before I found one that would enable USB debugging. All cables not created equal)
    -Use Ubuntu 18.04 and use the apt commands provided by @k4y0z in his first post.
    -Open a terminal in Ubuntu and type 'sudo -i' which will switch to a mode where all commands are issued sudo'ed as root
    -Run the bricking script (brick-6312.sh), then in another terminal window tell ADB to reboot to bootloader. Watch his magic script do the soft brick
    -Shutdown with 30s power button hold, and then turn off the Debian/Ubuntu ModemManager service as he indicated in his instructions
    -Run the bootrom script (bootrom-step.sh), and then turn it on with a 3s power button press. Follow instructions in linux terminal
    -Afterwards the device reboots into hacked fastboot (screen will still be blank). Verify fastboot mode with 'adb devices'
    -Run the final fastboot script (fastboot-step.sh), and then watch as it reboots and loads up into TWRP

    Once your in TWRP you are golden. Install Lineage, downgrade to older FireOS, root the current FireOS w/ Magisk, or whatever you want
    *As noted by others, when working with packages (like Magisk) do the work from recovery NOT in the OS, so it properly uses the patched bootloader

    Hopefully they don't push a new update before Black Friday, so I can snag a few more and unlock them as well!

    Cheers!
    4
    @bibikalka and also for anyone who is on 6.3.1.2 and doesn't want to open the device.
    I have something new for you to try out.
    All you need to do is get into fastboot mode:
    For 6.3.1.2
    Code:
    adb reboot bootloader

    @bibikalka, yours should be in fastboot anyway.

    Then run
    Code:
    brick-6312.sh

    or
    Code:
    brick.sh

    From the attached zip-file and follow the instructions on the display.

    Good luck ;)
    4
    So I got a HD8 2018 today and it came with OS version that forced me to connect to WiFi and update itself. I was pretty pissed but I used this guide to get root easily.

    I had Arch based linux installed which gave problems while running script, so I made bootable Ubuntu usb and that worked fine. Thank you everyone involved in developing this hack.
    For future reference you can avoid the presumed forced WiFi connect by putting in a bogus password; once authentication fails a 'skip' option will appear.