If you mean the boot-fastboot script, you can find it in the amonet zip from OP, alongside the boot-recovery script (which boots into TWRP).
Afaik there isn't a new amonet with support for fireOS 7.
It's a lot of work to port it (ditch the current amonet microloader and create a new eggsploit, based on the amonet 'suez' style).
A script to fix gpt, I should have clarified better. I have downloaded the gpt-fix.bin file for Karnak.
You can look at the OPs Github, in the amonet branch for douglas is the gpt-fix included, but for karnak it's missing. You may compare the files to see if you can add the gpt thing in the karnak amonet folder, take also a look into both main.py scripts...
Somehow it seems bricked... Can you point me at how to recover?
This is an 'old' 2018 fire 8. I tried the software method but after reboot nothing seemed to happen. I tried the hardware method and suddenly bricked... Please help!
This is an 'old' 2018 fire 8. I tried the software method but after reboot nothing seemed to happen. I tried the hardware method and suddenly bricked... Please help!
here, if you follow the directions for 'Another way to fix a brick', you'll be downgraded to 6.3.0.0
Fire HD 8 (2018 ONLY) unbrick, downgrade, unlock & root
Changelog: v2 - Fixed the issue with the screen Make sure to read this guide completely before starting. It requires you to open the tablet, however you don't need to solder or use any advanced tools. This is only for Fire HD 8, 8th generation...
forum.xda-developers.com
This liveISO for amonet works fine:
Releases · amonet-kamakiri/fireiso
ISO with patched kernel for kamakiri and amonet. Contribute to amonet-kamakiri/fireiso development by creating an account on GitHub.
github.com
Hi guys,
I have tried multiple ways but I am not able to get the bootrom-step to recognize the shorted Fire tablet.
I am using the FireIso 2.0 but no matter what cable I try, the tablet is not recognized. There is nothing coming up related to the table using lsusb neither the recovery nor the preloader (in case the short did not work). It also seems that the tablet is not turning on when the USB cable is plugged in.
Does anyone has an idea what is going wrong? I have the latest FireOS installed, could that be an issue for the hard mod?
I have tried multiple ways but I am not able to get the bootrom-step to recognize the shorted Fire tablet.
I am using the FireIso 2.0 but no matter what cable I try, the tablet is not recognized. There is nothing coming up related to the table using lsusb neither the recovery nor the preloader (in case the short did not work). It also seems that the tablet is not turning on when the USB cable is plugged in.
Does anyone has an idea what is going wrong? I have the latest FireOS installed, could that be an issue for the hard mod?
Hi boys.
i'm stuck with my fire 8 2018, i'm in bootloop with amazon logo.
I'm running the CLK method, using amonet-karnak-3.0.1 and running the bootrom-step script first and then fastboot-step from a terminal with sudo.
At the end I receive the writing Amazon and the writing "recovery mode" at the bottom left, but the TWRP never starts.
I also tried to give the fastboot format userdata and fastboot format cache commands, executed successfully, but the situation remains the same.
Any suggestions? Thank you all for any support
i'm stuck with my fire 8 2018, i'm in bootloop with amazon logo.
I'm running the CLK method, using amonet-karnak-3.0.1 and running the bootrom-step script first and then fastboot-step from a terminal with sudo.
At the end I receive the writing Amazon and the writing "recovery mode" at the bottom left, but the TWRP never starts.
I also tried to give the fastboot format userdata and fastboot format cache commands, executed successfully, but the situation remains the same.
Any suggestions? Thank you all for any support
Have you tried using the volume and power buttons? If I remember correctly I had to use them to enter TWRP for the first time.
Hi guys,
Please how did you manage to root your devices? I have fire HD8 2018 FireOS 6.3.0.1 and fire HD8 2017 FireOS 5.3.6.8 and I am unable to root them!
I tried mtk-su for Ubuntu and kingroot for windows but no luck.
For the fire HD8 2018, I tried to carry on with Unlock without rooting and now the device is stuck on Amazon logo.
Can anybody please help?
Please how did you manage to root your devices? I have fire HD8 2018 FireOS 6.3.0.1 and fire HD8 2017 FireOS 5.3.6.8 and I am unable to root them!
I tried mtk-su for Ubuntu and kingroot for windows but no luck.
For the fire HD8 2018, I tried to carry on with Unlock without rooting and now the device is stuck on Amazon logo.
Can anybody please help?
and I get this error when I try to run brick.sh in fastboot
Brick preloader to continue via bootrom-exploit? (Type "YES" to continue)
YES
Bricking PL Header
Check instructions on device
target reported max download size of 114294784 bytes
Sending 'brick' (111957 KB)...
OKAY [ 7.191s]
Writing 'brick'...
FAILED (remote: This partition doesn't exist)
Finished. Total time: 7.209s
Any Suggestion?
Brick preloader to continue via bootrom-exploit? (Type "YES" to continue)
YES
Bricking PL Header
Check instructions on device
target reported max download size of 114294784 bytes
Sending 'brick' (111957 KB)...
OKAY [ 7.191s]
Writing 'brick'...
FAILED (remote: This partition doesn't exist)
Finished. Total time: 7.209s
Any Suggestion?
Thanks for your reply Sus_i.
I already followed the method in post 2 but unfortunately after running fastboot-step.sh the tablets restarts but stucks at the amazon logo again!
I think the reason behind this problem is that my tablet isn't rooted.
Any other suggestions to get my tablet back to FireOS or root and unlock and flash a new rom?
If fireOS isn't aviable, the second post with shorting is the only option. There isn't any other unbrick method left.
Maybe try it again. Fastboot will also show a black/white logo screen (with a small txt note down in the corner) until the fastboot-step is completed.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
37Read 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.
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.15Unbricking / 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:
- It doesn't show any life (screen stays dark)
- 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).
- Make sure the device is powered off, by holding the power-button for 20+ seconds
- Start bootrom-step.sh
- 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:
instead, you are in preloader-mode, try again.Code:Bus 002 Device 014: ID [b]0e8d:2000[/b] MediaTek Inc. MT65xx Preloader
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.005Success
@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!5
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.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
