yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] Michajin:
Have you tried the offline rotting method or kingoroot? Last I knew they still worked...

HD 10 (2017): Offline rooting

Update: While this still works, there's an easier method here. Please try that first. Disclaimer #1: KingoRoot, dr.fone, and most other one-click rooting tools are characterized as malware. Should you use these tools? That decision is yours and...

xdaforums.com
[Fire HD 8 and HD 10 Original Android Development] poulopoulosa:
No Kingoroot is not ideal as I want to unlock the bootloader.

For those who have the latest fireOS like OP says you have to downgrade so you would have to "brick" your device. In order to brick your device you would have to push it into bootrom mode (idk if that is the right terminology). I shorted the PCB from a picture I saw by @retyre in this post.

I have managed to unlock and install lineage OS 16.0 (under development still). Please understand if you have the latest firmware the only way is to "brick" the device.
[Fire HD 8 and HD 10 Original Android Development] Michajin:
Yes it is, but if you don't want to open the device, you need root. Unlocking the bootloader will wipe everything, shorting out will get you into the bootrom, but it's easier to root and boot into it. I have 3 of these, never opened one...
[Fire HD 8 and HD 10 Original Android Development] jayp900:
I have a huge problem since a few hours. I rooted my Fire HD 10 2017 yesterday and everything worked fine. ..until I accidentally flashed TWRP to bootloader instead of recovery. I don't know what I did there.. Obviously the device is now stucked in boot loop. I can't get into recovery mode via button combination and I can't send any commands via adb since the device disconnects every few seconds because it is stucked in bootloop. Fastboot is also not working. Any idea?
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
In case you tried the boot-fastboot.sh script and it doesn't work for you... I guess you need to open it up for shorting...
[Fire HD 8 and HD 10 Original Android Development] kwanbis:
Hey k4y0z. Brilliant work here!

However, there are a couple of things that were not clear/confusing for me:

I was running a 2020 update (6.3.7.0 I believe), so I was getting an error on line 4, something about the firmware could not be modified or something like that.

I fixed it by first rooting the HD10 with Kingroot in my Windows machine, and then connecting the HD10 back to my Linux machine and starting the process again (run sudo ./step-1.sh etc).

As stated, I need to do the downgrade, so I followed these instructions.

I don't remember the exact moment, but the script asks you to "remove the short" or something like that. So I was confused, do I need to re-remove the cable and do it again?

I did and ended up on TWRP. But then it says:

I was wondering if at this point I can just flash LineageOS or do I really need to at least boot FireOS once?

THANKS!
[Fire HD 8 and HD 10 Original Android Development] Michajin:
You can just flash Los at this point. Still need to wipe though. This was written before that was los was a option.
[Fire HD 8 and HD 10 Original Android Development] kwanbis:
I had the exact problem. mkt-su would not work (first step of the guide), so I used kingroot from my windows machine to get root first, and then I followed the guide and worked perfectly.
[Fire HD 8 and HD 10 Original Android Development] arooni:
got the root on my 2017 fire 10 tablet via the offline method

~/D/amonet  sudo ./step-1.sh

Testing root access...

uid=0(root) gid=0(root) context=u:r:init:s0

PL version: 5 (5)

LK version: 4 (2)

TZ version: 267 (263)

TZ, Preloader or LK are too new, RPMB downgrade necessary (or brick option used)

Brick preloader to continue via bootrom-exploit? (Type "YES" to continue)

YES

Bricking preloader

8+0 records in

8+0 records out

4096 bytes transferred in 0.002 secs (2048000 bytes/sec)

Flashing LK

bin/lk.bin: 1 file pushed. 5.2 MB/s (407012 bytes in 0.075s)

794+1 records in

794+1 records out

407012 bytes transferred in 0.031 secs (13129419 bytes/sec)

Flashing TZ

bin/tz.img: 1 file pushed. 5.7 MB/s (3559424 bytes in 0.592s)

6952+0 records in

6952+0 records out

3559424 bytes transferred in 0.197 secs (18068142 bytes/sec)

6952+0 records in

6952+0 records out

3559424 bytes transferred in 0.283 secs (12577469 bytes/sec)

Rebooting..., continue with bootrom-step-minimal.sh

~/D/amonet  sduo ./^C

~/D/amonet  sudo ./bootrom-step-minimal.sh

[2021-05-18 21:06:49.956789] Waiting for bootrom

what to do now ?
[Fire HD 8 and HD 10 Original Android Development] arooni:
nevermind. got it!

i had to turn the device on i think to get it to boot by holding down the power button; didn't see that in the instructions.
[Fire HD 8 and HD 10 Original Android Development] furomin:
I have a question regarding this. Seems like I have a brick right now, because I tried to update magisk through the manager app... I can boot into TWRP but trying to do a default restart I'm stuck in a boot loop.... What can I do about it? Sorry if my question sounds stupid, but I'm a total noob...

Any help much appreciated!

Kind regards,

Florian
[Fire HD 8 and HD 10 Original Android Development] furomin:
Oops, sorry for double posting! I had some serious technical issues....
[Fire HD 8 and HD 10 Original Android Development] Michajin:
Reinstall your system, then flash magisk. Did you make a backup? Oh and never flash magisk from the manager.. lol
[Fire HD 8 and HD 10 Original Android Development] furomin:
First of all thank you for your answer, michajin! But, what do you mean by reinstallling the system? What exactly do I have to do? Thank you, and sorry for my stupidity! And also I should have known to not install Magisk through Manager app, sorry!
[Fire HD 8 and HD 10 Original Android Development] Michajin:
Flash your rom. Fireos or lineage...
[Fire HD 8 and HD 10 Original Android Development] flash713:
Talk about a helpful thread!!! Everything and more I was able to figure out reading the last two pages. 😁 I've had my suez since a few months after it came out. I guess I'll root it now and get all these apps off it that I don't use. Reminds me of an old Motorola phone I had some years ago. After unlocking bootloader and rooting it and then deleting all the bloat my ram almost doubled!! 😂 I'm sure this thing will be about the same. Tks everyone for making all these very helpful posts here!!
[Fire HD 8 and HD 10 Original Android Development] flash713:
Double post. 🙄
[Fire HD 8 and HD 10 Original Android Development] Michajin:
Lineage works pretty well on it....
[Fire HD 8 and HD 10 Original Android Development] furomin:
Just one more question... Where can I find the latest magisk canary zip file version 23001? Can someone link me up, please? Thank you!!
[Fire HD 8 and HD 10 Original Android Development] Michajin:
the apk is flashable, just rename it to a zip....

GitHub - topjohnwu/Magisk: The Magic Mask for Android

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com
[Fire HD 8 and HD 10 Original Android Development] furomin:
Thank you, Michajin!!!!!!!!
[Fire HD 8 and HD 10 Original Android Development] koad1226:
1. I tried rooting my hd 10 2017 7th generation and soft bricked the device.

2. I attempted to adb sideload FireOS 5.6.8.0 and ended up permanently bricking the device.

3. I used shorting to bring back the device. (at this point I did not know the os version the device was running)

4. But the problem is device boots normally to the first setup page BUT THE TOUCH IS NOT WORKING.

5. I have sideloaded the FireOS 5.6.8.0 again the screen is not responsive to touch still.

6. Physically, I don't see any damage to the digitizer.

7. I can boot into Amazon Recovery; volume keys, sound and screen rotation work perfectly.

8. Is my problem due to a corrupt os (don't know if that is possible) or a hardware issue?

KINDLY HELP ME FIX THE ISSUE.
[Fire HD 8 and HD 10 Original Android Development] koad1226:
Help me oo.

I can boot into Amazon Recovery and the first set up screen as shown above but the screen is not responsive to touch. It is on 5.6.8.0.

Can I sideload 5.6.3.0 without bricking the device? (just to verify if is the os causing the touch problem)
[Fire HD 8 and HD 10 Original Android Development] Phantasy0742:
./step-2.sh command also an error still occurs.

My fire hd 10 was anti-rollback hardbrick. so I did unbrick my device, and have factory reset.

Then, setting adb in dev option, excuted ./step-1.sh but error occurs and device did not operate to factory reset.
[Fire HD 8 and HD 10 Original Android Development] ffstudios:
Huh, I dunno. I had the same exact error you did when I ran step-1.sh but I was able to get back into developer options and run step-2.sh (well, after the extra factory reset due to the Serial Number being greyed out I guess)
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
The error you are getting in step-1.sh means, that it already modified the first stage.

If it didn't factory-reset just boot into recovery and do it manually.

Then run step-2.sh
[Fire HD 8 and HD 10 Original Android Development] bibikalka:
[MENTION=7104332]k4y0z[/MENTION] - Why are those 2 new partitions at the end are so giant? Those could be pretty beefy /boot and /recovery, at 110 MiB each :D Can really fit in a small-ish ROM!

I also keep wondering why the stock /cache is that specific large number (424Mb), I've never seen it filled up by FireOS. Unless it's used during sideloading operations ...

Finally, an interesting partition is /metadata . It's 40Mb sitting out there, never seems to be used to any substantial extent. I wonder if that's the reference partitioning from MTK that Amazon just borrowed.
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
The metadata partition is used when device is encrypted and is 16MB or larger.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
I just uploaded version 1.1.1.

It fixes the unbricking procedure, no other differences to version 1.1.

This is due to the way the exploit works. The actual boot/recovery images go to the boot_x/recovery_x partitions which are 16/17MiB.

/cache is also used to hold the update-bin during an OTA update.

/metadata is used for encryption.
[Fire HD 8 and HD 10 Original Android Development] Phantasy0742:
thanks for reply.

but still error occurs and happen nothing.

Traceback (most recent call last):

File "modules/gpt.py", line 314, in <module>

main()

File "modules/gpt.py", line 297, in main

part_list_unpatched = unpatch(gpt_header, part_list)

File "modules/gpt.py", line 226, in unpatch

partition = get_part_by_name(part_list_n, "boot_x")

File "modules/gpt.py", line 116, in get_part_by_name

if part['name'].decode("utf-16le").rstrip("\x00") == name:

File "/usr/lib/python3.6/encodings/utf_16_le.py", line 16, in decode

return codecs.utf_16_le_decode(input, errors, True)

UnicodeDecodeError: 'utf-16-le' codec can't decode byte 0x00 in position 0: truncated data
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Please say the exact steps you did and give the full output of the scripts.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
No more serial port errors. Progress. Now this:

[2019-03-26 14:06:57.619058] Waiting for bootrom
[2019-03-26 14:07:18.236851] Found port = /dev/ttyACM0
[2019-03-26 14:07:18.241677] Handshake
[2019-03-26 14:07:18.242359] Disable watchdog

* * * Remove the short and press Enter * * *

[2019-03-26 14:07:22.028496] Init crypto engine
[2019-03-26 14:07:22.047291] Disable caches
[2019-03-26 14:07:22.047825] Disable bootrom range checks
[2019-03-26 14:07:22.061366] Load payload from ../brom-payload/build/payload.bin = 0x4820 bytes
[2019-03-26 14:07:22.065072] Send payload
[2019-03-26 14:07:22.616363] Let's rock
[2019-03-26 14:07:22.617021] Wait for the payload to come online...
[2019-03-26 14:07:22.621116] all good
[2019-03-26 14:07:22.621430] Check GPT
Traceback (most recent call last):
File "main.py", line 192, in <module>
main()
File "main.py", line 95, in main
switch_user(dev)
File "main.py", line 56, in switch_user
block = dev.emmc_read(0)
File "/home/dragon/amonet-suez/amonet/modules/common.py", line 196, in emmc_read
raise RuntimeError("read fail")
RuntimeError: read fail
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Can you please send me the files from the gpt-regen folder?
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
That looks like a hardware issue. Are you sure you have removed the short?

Check that there aren't any scratches/missing components etc.
[Fire HD 8 and HD 10 Original Android Development] Phantasy0742:
Attached zip file.
[Fire HD 8 and HD 10 Original Android Development] OldFeller:
Stuck at "Testing Root Access..." in script 1

I soft bricked my SuperSU rooted HD 10 (7th) Fire OS 5.3.6.4 while removing the Amazon crap and couldn't find any way to get it out of the fastboot it was stuck in, so I just reset back to factory. Enabled ADB and used a Windows command window to make sure it was all working. I was able to get the HD 10 back into temporary root with ARM64 mkt-su.

I thought I was at a point where I could use this new root & unlocking method, so I set up a virtual machine using VMware with Ubuntu 18.04 on my Windows 7 PC x64. I've spent a day getting it all ready with the necessary updates, packages and tools. I have a passing familiarity with Linux having used it to hack several previous devices like my old DirecTivo and Motorola Razor flip phone. I just got it all done and started the first script. It makes it to "Testing Root Access..." with a blinking cursor for just a few seconds, then the cursor stops blinking and the session just stops. I waited for several minutes with no apparent movement, then used Crtl-C to break out. I've placed a copy of ARM64 mkt-su in the amonet/bin directory that I know works as I've used it manually. Now after 3 trys and fails, it's time to ask for help. Where do I go from here ?
[Fire HD 8 and HD 10 Original Android Development] chivoyage:
Thank you, O lord of the Fire world! Now I can finally mod the Fire HD 10 my heart's content.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
I have just uploaded amonet-suez-v1.1.2.zip

That should fix your issue, please try.

Please share the exact output of the scripts.

Is adb enabled?
[Fire HD 8 and HD 10 Original Android Development] OldFeller:
Thank you for such a quick reply ! Yes, ADB was enabled on the HD 10. I'll give this script a try and post the output.
[Fire HD 8 and HD 10 Original Android Development] SingleMalt69:
I had the same issue, v1.12, stuck on "Testing Root Access". I killed the script, unplugged the Fire, plugged it back in and restarted the step2 script. This time I had no problems at all.

Sitting right now in TWRP, and waiting for someone smarter than me to develop a custom ROM for this.

Great work!

P.S. Running FireOS v5.6.0.1, and used the 1.12 scripts.
[Fire HD 8 and HD 10 Original Android Development] OldFeller:
1st Script Output

Ran first script and this time it appears to have worked. Got this output => https://xdaforums.com/attachment.php?attachmentid=4731561&stc=1&d=1553633279

HD10 went through Recovery and booted up. I enabled Developer Options and ADB. Reconnected portable device to Ubuntu and verified with ADB that HD 10 was connected through ADB. Here's output from this => https://xdaforums.com/attachment.php?attachmentid=4731564&stc=1&d=1553633726

Hope I did the output so you can see it. Second script hung up on Testing Root Access.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
That's weird, the first thing that "Testing root access" does is:

adb shell su -c id | grep uid=0\(root\)

I don't know why it doesn't work, but I suppose if the first script succeeded, just try the second one until it succeeds.
[Fire HD 8 and HD 10 Original Android Development] flash713:
I always rename canary apk to canary.zip and flash or I patch my boot.img on my phone, pixel 4xl, but I saw the other day a few people posted that they flashed the APK in twrp. I was like "WTF!!" 😂🤣😁 Android has come a LOOOONG way!!! I'm grateful we still have the creater and maintainer of magisk, topjohnwu, still around and doing all he does, especially after he was recently hired on to Google on the development team. I always laugh a lil because he is an Apple developer as well. I remember all the fuss back in the day about people hating Apple.. topjohnwu is definitely a top notch dev and we are blessed to have him as we are blessed to have everyone who participates in development. 🙏✌️❤️
[Fire HD 8 and HD 10 Original Android Development] jaagoodall:
Hi, I am completely new to this and I ran into a problem immediately. After I downloaded the zip files and extracted them, copied the binary to the required folder and then opened the command line I ran the command

sudo ./step-1.sh

but got the error:

sudo: ./step-1.sh: command not found

I enabled ADB, have everything installed, connected my tablet via usb, etc. Can anyone let me knw what I'm missing?

Edit: Just moved to amonet folder and it started working... must be tired

Thanks
[Fire HD 8 and HD 10 Original Android Development] koad1226:
I

I can't enable ADB since I can't go beyond the first set up screen. Is there any hope for me?
[Fire HD 8 and HD 10 Original Android Development] jaagoodall:
Why cant you go past the first set up screen? If you are trying to prevent amazon automatically upgrading then I think it's been mentioned that you can skip setting up wifi by doing something along the lines of "set up WiFi" then selecting the "skip" option.
[Fire HD 8 and HD 10 Original Android Development] koad1226:
Touch screen not working. I strongly believe the digitizer is intact.
[Fire HD 8 and HD 10 Original Android Development] gRooster:
You previously stated that you opened it up to do the short, so my first guess would be that you damaged the ribbon cable for the screen, or did not seat it in properly. I would open it back up and try reseating the cable, making sure that it is inserted all the way, etc. Beyond that IDK, maybe whatever version of FireOS you installed does not have the correct drivers, I would try reinstalling whatever version (specifically for this tablet) was previously working. You could also try a USB keyboard to see if it will allow you to interact with the setup screens, but I do not think that is gonna fix anything related to the touch screen.
[Fire HD 8 and HD 10 Original Android Development] koad1226:
Thank you. I will try both suggestions
[Fire HD 8 and HD 10 Original Android Development] gRooster:
Good luck, I hope it works out for you. Regarding the ribbon cable, it has been a little while since i did mine, but I seem to recall that it is fairly short, making it a little tough to line up with the socket. Just make sure it is in all the way and straight (IIRC there are tiny little tab stops on the side of the cable that should be right up against the socket). And make sure push the little black lever on the socket (that you lift to remove the cable,) back down to lock it in place.

Assuming that the FireOS version that you tried to install was for this tablet (HD 10 2017) and you got it from official sources, then I see no reason the touch screen should not be working, beyond the hardware (cable, etc)
[Fire HD 8 and HD 10 Original Android Development] koad1226:
☹☹ Sadly, I would have to resign myself to an unusable tablet. It is left with the external keyboard thing which I will try. But for now, it is sadness. My first ever tablet. Was going to treasure it like Jolly's Coat of many colours. And it was a gift. Hmmmmmm
[Fire HD 8 and HD 10 Original Android Development] RodMcKay:
Good evening everyone. I have a question regarding the available ROMs which can be flashed after I conducted this guide.

Are these the available ROMs for suez or am I missing something?

[discontinued][ROM][unlocked][suez] Lineage-12.1 [05 MAY 2020]

[discontinued][ROM][unlocked][suez] Lineage-14.1 [26 SEP 2019]

[ROM][testing][suez] Lineage-16.0 [12 FEB 2021]

I ask because I need at least Android 6 on my suez device. I am looking for the most stable >= Android 6 ROM I can find.

Thank you!
[Fire HD 8 and HD 10 Original Android Development] gRooster:
Those are the only ROMs that I know of. Lineage 14.1 is Android 7.1.2, and I have not had any stability issues with it, however, you would have to look to see if anything that you absolutely need is working. e.g. cameras do not work, so if you need the cameras, then it is not an option, etc.
[Fire HD 8 and HD 10 Original Android Development] bluedesire:
Hi i would like to know if i decied to get this way, how can i go back on Stock?

Is a Linux system realy needed or can i get in a VM ?

Otherwise why it doesn´t work on Windows? is there a way to do it on Windows?
[Fire HD 8 and HD 10 Original Android Development] smithbill:
My post here and the help I was given by @chairmanmiaow may be useful to you. Once rooted with Lineage-12.1 installed on my FireHD10, it was just a matter of clean flashing Lineage-14.1.

However, although it was certainly cleaner & faster on Lineage than when on stock FireOS, I soon found that my FireHD10 was just another Android device that sat in a drawer unused. So, as you'll see from my subsequent postings in the linked thread, I decided to go back to stock FireOS so I could at least use the tablet as an Alexa device with working hot-word detection. And with Magisk installed, my device remained rooted allowing me to install Google PlayStore and to debloat it (I use AppFreezer 1.0.6) & use a custom Launcher (Nova 6).

Be aware: newer versions of Magisk don't seem to work with FireOS 5.6.8.0 - the last known good version for me was Magisk 20.4 (if you read the linked thread in full you'll see some details).

So I have two FireHD10 (suez) both on stock FireOS 5.6.8.0 and rooted with Magisk 20.4, Google PlayStore installed, FireOS debloated using AppFreezer 1 0.6, default Launcher set to Nova 6 (latest Nova 7 doesn't work) and with Alexa hot-word detection working normally.
[Fire HD 8 and HD 10 Original Android Development] bluedesire:
I have tried to flash but i dont know iam on Version 5.6.8.0 how can i flash TWRP and how can i root it?

How can i downgrade it?

Because it doesn´t work , Kingroot is not effectly because is temporary so how can i root and flash my Fire HD 10 2017.
[Fire HD 8 and HD 10 Original Android Development] smithbill:
I'm not sure if you can root FireOS 5.6.8.0. You'll have to try it (if you dare).

You won't get a 'guaranteed to work' step-by-step instruction. There are too many variations & adaptions have happened over the years for a clear process to exist, so you'll have to gather the information yourself by reading threads & try it.

I can be fairly confident in saying Kingroot is a waste of time - it won't give you root with FireOS 5.6.8.0. So ditch Kingroot.

If I recall correctly, part of the rooting process involves 'downgrading' to a previous version, but I may be wrong.

Have you actually read all of the thread I linked you too?

As I recall, the key part involves obtaining a *temporary* root and then NOT rebooting the system until you had flashed the relevant files using ADB - I don't remember the details, but once the relevant files were flashed & Magisk also flashed, then root became permanent and the system could be rebooted.

So the key part is to obtain the temporary root & with all of the required Recovery, ROM & Magisk files prepared (I think on your PC for use with ADB & fastboot?) you can flash the files & restart the system with root now permanent.
[Fire HD 8 and HD 10 Original Android Development] bluedesire:
i have done with it root over this:

HD 10 (2017): Offline rooting

Update: While this still works, there's an easier method here. Please try that first. Disclaimer #1: KingoRoot, dr.fone, and most other one-click rooting tools are characterized as malware. Should you use these tools? That decision is yours and...

xdaforums.com

Now the Lineage OS 12.1 is running :) but how can i flash Gapps arm and arm64 not working, please help