yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] MontysEvilTwin:
Having the same problem. The tablet boots into hacked fastboot mode but gets stuck on 'waiting for device'. I downloaded and unzipped the latest Android SDK tools and placed the 'platform-tools' folder in the 'amonet' folder and tried the first command but I just get error messages with odd text encoding (it looks a bit different within the Ubuntu terminal window):
[Fire HD 8 and HD 10 Original Android Development] MontysEvilTwin:
I have sorted this problem out now. The version of fastboot in the repository for Ubuntu 16.04 is too old and does not work with hacked fastboot on the Suez tablet. I downloaded the latest Android platform tools and tried to run the fastboot steps manually, but it would not run on my 32-bit installation. I eventually installed Ubuntu 18.04 (64 bit) on a different laptop and the 'fastboot-step.sh' script ran correctly first time with the repository version of fastboot installed on this version of Ubuntu.
[Fire HD 8 and HD 10 Original Android Development] davekaz:
Doesn't win 10 support Linux now WSL You can install Ubuntu from Microsoft store and run terminal. Shouldn't that work? Maybe you need insiders preview build which I have.WSL2 with Linux kernel
[Fire HD 8 and HD 10 Original Android Development] DB126:
WSL has difficulty communicating via USB interface. Hopefully WSL2 will address that.
[Fire HD 8 and HD 10 Original Android Development] davekaz:
I was able to update ubuntu in wsl 2 but command not found when sudo ./step-1.sh. I think I have to downgrade but blocked updates and cant see ver. But that wouldn't stop .step command. Just want to make sure before I downgrade
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Don't downgrade, you will likely brick your device and will have to disassemble it to unbrick.

Either step-1.sh isn't where it should be, or it is not marked executable (probably because it was extracted onto a filesystem that doesn't support linux attributes).

That said, I have no experience with WSL.
[Fire HD 8 and HD 10 Original Android Development] davekaz:
Can you tell me exactly how you did it. Adb device list nothing
[Fire HD 8 and HD 10 Original Android Development] davekaz:
can not get it to see device in ubuntu wsl2.. I see it in cli and continuously swap back and forth. i go into puppy and it doesn't mount amazon correctly and fails Im rooted on ver 564 fire hd 10. I put adb in its own dir with amonet and mounted it adb works but no device listed
[Fire HD 8 and HD 10 Original Android Development] chemengire:
"If you are on firmware 5.6.4.0 or newer, a downgrade is necessary" - what does this mean, in practice?

My current version is v5.6.4.0 - do I have to install a lower version? If so, when?

I'm sorry if this is a dumb question. For me, the instructions are not succinct enough.
[Fire HD 8 and HD 10 Original Android Development] DB126:
You'll need to obtain an older build of FireOS for this device (suggest 5.0.1) and install it via Amazon's stock recovery menu. Be aware this action will appear to 'brick' your device; it will become lifeless, dark and unresponsive to any user input. At that point you are comitted to following the rest of the unlock procedure.
[Fire HD 8 and HD 10 Original Android Development] MontysEvilTwin:
Just follow the instructions in the first post. You will be asked to confirm that you want to brick the device and everything will be done by the script. Bear in mind that if you brick during step 1, you don't run the step 2 script: the procedure is described in post #1, but you have to show the full post to see them.

The only problem I had is that the last step, when bricking, requires hacked fastboot mode and the latest version of fastboot available in the repository for Ubuntu 16.04 is too old and does not work with the device in this mode. I had to run the last step on Ubuntu 18.04: the fastboot version is more up to date and works with hacked fastboot.

---------- Post added at 12:38 PM ---------- Previous post was at 12:31 PM ----------

That is the procedure for the Amazon Fire 7 (2015) where loading version 5.3.2 (or older) allows you enter bootrom mode by holding down one of the volume buttons when you plug in the USB cable. The method described in this thread for the suez will brick the device for you if necessary.
[Fire HD 8 and HD 10 Original Android Development] DB126:
Ahh...thank you! I wasn't paying attention to the specific thread and dished up a valid but unnecessarily complex solution. Consequence of posting before coffee kicks in. ?
[Fire HD 8 and HD 10 Original Android Development] :
Ok, I've looked through some build and source files of amonet-karnak and amonet-suez. What I've discovered is that the preloader, LK, and TZ are replaced with patched versions on both tools. However, amonet-karnak appears to use stock GPT and choses to install the exploits to the beginning of boot/recovery, while amonet-suez modifies GPT and installs the exploits to new boot/recovery partitions, created after userdata, while keeping the stock boot/recovery partitions, which are now renamed to boot_x/recovery_x stock without modification, with the exception of flashing TWRP to recovery_x.

It seems that amonet-karnak's method is actually cleaner since it doesn't appear to require modifying the GPT/partitions. The downside is that TWRP must uninstall and reinstall the exploits when flashing files. This certainly seems a little dangerous but should work fine unless a power failure or something of that nature is experienced between the uninstallation and reinstallation.

My question to [MENTION=7104332]k4y0z[/MENTION] is this, why isn't this method used, or at least available as an option? Personally I would prefer to use this method and keep the stock GPT/partitions. Thanks for your time. Please correct me if my assumptions are incorrect.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Neither amonet-karnak nor amonet-suez use patched versions of PL, LK or TZ.

That wouldn't work, since their signatures are checked on boot.

It just makes sure that the correct version of LK (together with PL and TZ) are installed, since the exploit is targeting a specific version of LK.

That is mostly correct.

That's also mostly correct, both methods have their pros and cons.

The reason is, that the LK on suez (and douglas) forces the kernel loading-address to 0x45000000 and therefore it cannot be exploited like it is on karnak.
[Fire HD 8 and HD 10 Original Android Development] :
Thank you for the in-depth reply. I like to learn a lot about the tools I'm using and I appreciate the time you took to explain the way this works. If I understand correctly, there isn't a particularly better to exploit this device. As ridiculous as this sounds, the partition modification still bothers me for little to no reason. It's quite annoying that it has to be done this way. But I guess it's good that it works. Out of interest, are the _x suffixes hardcoded in the exploit files, such as boot.hdr or could they be changed to something else, provided they are different from the stock "boot" and "recovery" names?
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Yes they are hardcoded in lk-payload, otherwise how would it know were to load boot/recovery from?
[Fire HD 8 and HD 10 Original Android Development] :
Alright. Thanks for your help! Apologies for bugging you over a minor annoyance. It's quite interesting to know how and why that's needed though!
[Fire HD 8 and HD 10 Original Android Development] chemengire:
Thank you for your reply.

So, I don't have to install any other Fire OS ROM? I follow the script. Once the bootloader is unlocked & TWRP installed I can go ahead and install the new Lineage OS v12.1 ROM? Is this accurate?

Thank you so much for helping me!
[Fire HD 8 and HD 10 Original Android Development] MontysEvilTwin:
Yes. Wipe system, data and cache then flash the Lineage ROM from TWRP. You can wipe data without wiping 'internal storage' so you can either flash the rom from the internal storage or an sdcard.
[Fire HD 8 and HD 10 Original Android Development] chemengire:
Thank you so much for your information. The instructions for the unlock were a little bit ambiguous (for me), but I feel happy to go ahead and attempt it now.

Would be great to free the tablet from the Amazon garbage, finally.
[Fire HD 8 and HD 10 Original Android Development] davekaz:
Got it to work. I'm such a stupid ass. I was typing an -l instead of 1 lol. I had temp brick it which was a trip but got it to work with your fastboot hack. Magical. Its truly a beautiful experience now with twrp and. Lineage. Thanks man so glad for your input. How do I donate?
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Good to hear you got it working.

There is a donation-button on my profile. :)
[Fire HD 8 and HD 10 Original Android Development] shakeandscream:
Little late to the party, but having an issue. I noticed while reading through the thread that the old fastboot is out of date. I downloaded platform tools, and put them in the amonet directory. I was able to do step-1 with no issue after getting mtk-su, and I chose to brick the device. I'm assuming it's bricked because it obviously won't turn on or do anything. The problem I'm having is when I'm trying to run the fastboot commands manually, it says "waiting for any devices" and it doesn't seem to be detecting my Fire HD 10 as being in hacked fastboot, or recognizing it at all. Any help would be appreciated!
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Sounds like you're missing a step.

If it is currently bricked as you say, then obviously fastboot won't work.

Did you run bootrom-step-minimal.sh?
[Fire HD 8 and HD 10 Original Android Development] SaulG:
Hi, how did u overcome the Ubuntu terminal in WSL issues? I am facing your same previous problem where adb in Ubuntu terminal lists no devices.
[Fire HD 8 and HD 10 Original Android Development] kcasante:
Can you provide the link to Lineage ROM link? I followed the post. Everything worked fine except for one thing: I can get TWRP loading easily but I can't get back into FireOS. Boot it regularly and it gets stuck at the Amazon logo.

Boot it with volume button held and it boots into TWRP.

I'm new to all this so I'm having a bit of a hard time getting back to FireOS.

Many replies say there are no official ROMS for the Fire HD 10 (7th Gen) yet so you have to install toolbox but since I can't get back into the fireOS I'm a bit lost...

Any recommendations out there?

Thanks
[Fire HD 8 and HD 10 Original Android Development] MontysEvilTwin:
If you have wiped System but not flashed the ROM the device will have no OS installed. The Lineage ROM for the HD 10 (2017) is linked in the first post in this thread: https://xdaforums.com/hd8-hd10/orig-development/rom-lineage-12-1-t3953677
[Fire HD 8 and HD 10 Original Android Development] cratediggah:
Error when trying to achieve root

Hi all -- I've successfully rooted/installed Lineage on a couple of HD 8s. I purchased a 2018 Fire HD 10 [7th generation, Suez] w/ FireOS version 5.6.4.0 installed.

When I try to run the steps here, I receive the following error, couple of notes:

1) I copied over arm64 version of mtk-su

2) I permissioned chmod 755 on mtk-su

.. error:

Trying to use mtk-su to get temp root...

Pushing root files

[100%] /data/local/tmp/mtk-su

[100%] /data/local/tmp/minisu.img

[100%] /data/local/tmp/busybox

Failed critical init step 4

mount: permission denied (are you root?)

when I try adb shell, cd /data/local/tmp .. ./mtk-su I get the following error as well:

127|shell@suez:/data/local/tmp $ ./mtk-su

Failed critical init step 4

UID: 2000 cap: 0000000000 selinux: enforcing

shell@suez:/data/local/tmp $

Any help greatly appreciated.
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
Uh oh... Sounds like amazon may patched mtk-su in latest update.. [MENTION=8132642]diplomatic[/MENTION] can you confirm this?
[Fire HD 8 and HD 10 Original Android Development] mi7chy:
Fire HD 10 7th gen runs stock 32-bit Android so try 32-bit mtk-su. Did mine running 5.6.4.0 the other day and it worked fine.
[Fire HD 8 and HD 10 Original Android Development] diplomatic:
When did this firmware come out? Is there a date? It certainly does look like the end of the line for mtk-su. There isn't a new firmware or kernel source out on the web for me to check.
[Fire HD 8 and HD 10 Original Android Development] cratediggah:
Fire was delivered on Thursday, plugged it in today... I pushed arm [32 bit] using adb, chmod 755, ran and got following

127|shell@suez:/data/local/tmp $ ./mtk-su -v

armv8l machine

Failed critical init step 4

setns failed: Permission denied

starting /system/bin/sh

UID: 2000 cap: 0000000000 selinux: enforcing

---------- Post added at 10:33 PM ---------- Previous post was at 10:32 PM ----------
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
5.6.4.0 has been out for a while, unless they released a fix with the same version-number.

[MENTION=8132642]diplomatic[/MENTION], could it be that something is broken for HD10 in current mtk-su release?
[Fire HD 8 and HD 10 Original Android Development] diplomatic:
[MENTION=4106600]cratediggah[/MENTION], can you check in Settings for the build number, build date, install date or something. It could have installed an update that you were not aware of.

Yeah, it could have been an update with the same version number, like they did with the Fire 7 9th. Same version, but a higher build number. I'd think that if it was a problem mtk-su, there would be a lot more reports...
[Fire HD 8 and HD 10 Original Android Development] Kctucka:
Had a friend running stock check. They received an update on September 13th :(

Still 5.6.4.0.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
I didn't know they did that on mustang.

Didn't think they would do that.

Doesn't the fix require a kernel-update?
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Can you ask them to check the build-number as [MENTION=8132642]diplomatic[/MENTION] suggested?
[Fire HD 8 and HD 10 Original Android Development] cratediggah:
Okay, so I still have updates pending -- didn't accept, but looks like an update was installed today.

5.6.4.0 (636559820)
[Fire HD 8 and HD 10 Original Android Development] Kctucka:
It's 636559820.
[Fire HD 8 and HD 10 Original Android Development] diplomatic:
Yeah, so that pretty much settles the question. No more mtk-su for Fire HD10, guys. Can't say it's a big surprise. The update presumably installs a new boot image, [MENTION=7104332]k4y0z[/MENTION]. It looks like you will have to port your fastboot hack to this device too.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Yeah looks like it, I quickly made a version based on the LK used in amonet-suez.

Not sure if LK has changed since then, otherwise I'll have to port it to the newer one.

[MENTION=4106600]cratediggah[/MENTION]

Can you test the attached zip?

Go into fastboot-mode and run the brick.sh

If it works it should brick the preloader and then let you use bootrom-step.sh to unlock.
[Fire HD 8 and HD 10 Original Android Development] cratediggah:
Hi, thanks. I’m happy to give it a shot, but was going to return this (literally just bought) if unable to root/install Lineage. Would doing this permanently brick or make my device unable to return? Not in a position for it to be a total loss. Please let me know thanks
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
So I checked and the zip-file I uploaded earlier will not work on 5.6.4.0.

I was however able to create a version that should work on both versions.

I have attached it here again.

It will temporarily brick your device and you can then subsequently follow the instructions for unbricking in Post #2.

However unlike described in that post, you don't have to open the device and short anything ;)
[Fire HD 8 and HD 10 Original Android Development] cratediggah:
Ok great thanks, just so I have it straight. I’ll brick w this and try to root w mtk and/or step 1 from this thread?
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
That is not what I said :rolleyes:.

As you already noticed mtk-su doesn't work on your firmware.

You will brick and then follow the instructions in Post #2 using bootrom-step.sh and fastboot-step.sh.
[Fire HD 8 and HD 10 Original Android Development] davekaz:
I never did it with wsl . I installed ubuntu along side win 10. Ran it in there. It was scary at one point. I was on 564 so had to temp brick it. Screen was black. Couldn't tell if was on or not. Finally ran that fastboot hack and it installed twrp and rebooted . Working great with lineage rom
[Fire HD 8 and HD 10 Original Android Development] thestudentOO:
Hi,

i've a Fire HD 10 with the newest Version of FireOS 5.6.4.0 (636559820).

I will try the brick Method. I'm not sure the right Steps so is this the right steps for brick/downgrade/root etc.

a) linux is availible with adb/fastboot etc.

b) i downloaded the amonet-suez-v1.1.2.zip and brick-suez.zip and extracted.

Now the Steps i think i should do with the Questions i have in red:

1) boot in fastboot mode

2) run brick.sh (from Post #830) and confirm with yes -> will brick my Fire HD 10

Question: After brick will the device try to boot and Screen stays black or how i know that i bricked successfully?

3) disconnect device from pc

4) Run "sudo ./bootrom-step-minimal.sh"

5) Then plug the device back in.

6) It will then boot into "hacked fastboot" mode.

7) Run "sudo ./fastboot-step.sh"

This will flash TWRP and reset my device to factory defaults, then reboot into TWRP.

Am i right with this steps?

After it boot to TWRP i can install Magisk from there.

And after reboot have a unlocked/rooted Fire HD 10?

I will install the Lineage-12.1 Rom from the other Thread.

Hope you can confirm my steps.

Greetz

ThestudentOO
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
That's mostly correct, you will need to use bootrom-step.sh instead of bootrom-step-minimal.sh.

Regarding your question how to know it is bricked, it will display instructions on the display of the device.

At that point you disconnect it and power it off yourself.
[Fire HD 8 and HD 10 Original Android Development] thestudentOO:
Thx. Will give it a try when home again.

Gesendet von iPhone mit Tapatalk
[Fire HD 8 and HD 10 Original Android Development] sga999:
I think he thought it was the minimal step because this is near the end of brick.sh.

echo "Then continue with bootrom-step-minimal.sh

Is there a reason for brick-suez.zip being included in itself? I mean, brick-suez.zip includes the amonet folder and brick-suez.zip.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
It should be saying "Then continue with bootrom-step.sh" in the last version I uploaded.

That's not on puprpose, that the zip is included again.

I may be able to adapt it to work with bootrom-step-minimal, since not much has changed in LK, but for now you should use bootrom-step.sh if you weren't unlocked before.
[Fire HD 8 and HD 10 Original Android Development] sga999:
I'm looking at the zip from post #830. It shows the minimal version in the echo command. No problem, just wanted to be sure I know what's right.
[Fire HD 8 and HD 10 Original Android Development] thestudentOO:
i booted to fastboot and than

run sudo ./brick.sh

thats my output. Fire HD came up after that normaly without a brick.

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' (111616 KB)...
OKAY [ 5.311s]
Writing 'brick'...
FAILED (status read failed (No such device))
Finished. Total time: 37.535s

what did i wrong?

Also can i booting to fasboot without booting to recovery before?

Edit: i've tried it with an Ubuntu live System. Does it make a difference when its a live System?
[Fire HD 8 and HD 10 Original Android Development] thestudentOO:
Does someone have an idea what i can do to unlock/root with brick trick?

Should i try another pc oder another cable?

I used the factory cable that came with the fire hd 10.
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
Well I recommend you try differents computers, ports and cables.

Also try redownloading the zip.

Also if you still had no luck after a lot of times, I would try to root with KingoRoot and then run the normal process (step-1.sh & step-2.sh).

Regards.

Enviado desde mi WAS-LX1A mediante Tapatalk
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
I am pretty sure you can just downgrade from the new 5.6.4.0 to the old 5.6.4.0 using stock recovery and then use mtk-su.
[Fire HD 8 and HD 10 Original Android Development] thestudentOO:
Ok. I will try it end of week. Dont have much time next days.

Thx for the help.
[Fire HD 8 and HD 10 Original Android Development] ksh0127:
I'm running Ubuntu on VirtualBox on Windows. That shouldn't be a problem right?
[Fire HD 8 and HD 10 Original Android Development] ksh0127:
Walkthrough

Please forgive my amateurishness, but I have some really basic questions to ask. I am not very experienced with linux and am using Ubuntu through a VirtualBox on my windows laptop. I just wanted Lineage on my tablet and thought i'd give this a go. I'm kinda confused here so can someone please walk me through this process? Here's what I understood:

1. I have ubuntu with python3, PySerial, adb, fastboot dos2unix - all installed.

2. I download amonet-suez-v1.1.2.zip and brick-suez.zip. And I extract them - but where?

3. My tablet is connected, I power it off, hold volume down + power (for fastboot mode)

4. Then i go to the folder where brick.sh is present, open terminal and type sudo ./brick.sh, then YES

5. Unplug device

6. Go to the folder where bootrom-step.sh is present, open terminal, type sudo ./bootrom-step.sh

7. Go to the folder where fastboot-step.sh is present, open terminal, type sudo ./fastboot-step.sh

8. This should flash TWRP then follow instructions on the Lineage thread.

Have I understood this correctly? Is there an easier more fool-proof way to do this? If not, can someone walk me through the right steps? Thank you very much, appreciate any help.
[Fire HD 8 and HD 10 Original Android Development] shadowcliffs:
I'm not the person you replied to but after I saw your post, I tried downgrading from the new 5.6.4.0 to the old one using stock recovery and stock recovery. Now the device wont boot up. Is it bricked? What should I do next to unbrick it? TIA!
[Fire HD 8 and HD 10 Original Android Development] thestudentOO:
Did you took the right Firmware for fire hd 10 7th gen?

If the Device doesn't came up its maybe bricked. Better you wait for k4y0z answer but i think you can try the steps i wanted to do after brick. But with the brick.sh it doesn't bricked my fire hd 10.

Some posts above or in second post there are steps for unbrick.

Good luck.

---------- Post added at 08:10 AM ---------- Previous post was at 08:04 AM ----------

After brick...

After step 6 you have to plugin Device. And wait.

Thats how k4y0z described it
[Fire HD 8 and HD 10 Original Android Development] ksh0127:
Thanks. Where do I extract the zip files in step 2 though?
[Fire HD 8 and HD 10 Original Android Development] thestudentOO:
I extracted them where i wanted. You can navigate in every directory in Linux. So no matter where you extract them. But on the PC and NOT the fire hd.

I still didn't root my fire hd so i can not give you a warranty that it will go with this steps. My fire Just booted normally after the fail in brick.sh as i wrote above
[Fire HD 8 and HD 10 Original Android Development] ksh0127:
Oh okay, I did the same. But when I run brick.sh and say YES, I get an error saying there's no such file or something.

And I can extract the amonet and brick in different folders right?