yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] 8bitword:
Thank you for your excellent work @ggow!

I am currently on lineage 14.1 and I have locked bootloader and corrupt recovery. I broke recovery by using flashify to flash the new version of twrp. I can only get temporary root using KingoRoot.

Is there any way to flash recovery? I tried PartitionsBackup app that shows recovery and recovery_x partitions.

Does a locked bootloader allow me to flash a stock rom and install stock recovery or will it break it?

Cheers.
[Fire HD 8 and HD 10 Original Android Development] chairmanmiaow:
Having fixed suez #1 I've moved on to suez #2 and promptly find myself in the same situation as @8bitword - I forgot to check through the replies here first and decided to "update" twrp by flashing twrp_suez_3.6.1-9.0.img to recovery using the standard twrp app from the playstore. Whoops.

I should have done dd if=/sdcard/twrp_suez_3.6.1-9.0.img of=/dev/block/platform/soc/11230000.mmc/by-name/recovery_x and have now done so but I still don't have a working recovery unsurprisingly. Is this fixable? I'm in a slightly better position as I can still boot to a working lineageos 16 with root - the bootloader was unlocked and unless the ill-advised twrp flash broke it it presumably still is.

To go back to stock if I remember rightly you put the suez into download mode and then just adb sideload update-kindle-blah-blah.bin right? The latest suez firmware from Amazon is FireOS 5.3.7.3 though which I can't imagine is still hackable using the old amonet method though. Does anyone know what the latest version of FireOS for the suez is still usable and where it might be obtained?
[Fire HD 8 and HD 10 Original Android Development] chairmanmiaow:
And come to think of it, I still have suez #1 to hand which is a fully working hacked bootloader+twrp+lineageos+root setup. Could I dd the relevant partitions to .img files on the suez #1 and then dd those imgs to the relevant partitions on suez #2 to restore working order?
[Fire HD 8 and HD 10 Original Android Development] Shack70:
I'm not sure this would work or not. If you go the other route and restore a stock rom, I would use an older version that is rootable and then follow this threads instructions: https://xdaforums.com/t/unlock-root-twrp-unbrick-fire-hd-10-2017-suez.3913639/
[Fire HD 8 and HD 10 Original Android Development] greenbot2018:
Thanks to you folks the ol' Fires never quit, made it to another android generation. Great work guys. I passed on this image this last year but it looks like the big bugs are worked out. Working great for our needs. Thanks again!
[Fire HD 8 and HD 10 Original Android Development] _ck_:
This big beautiful 10 inch tablet is back restocked on Woot for only $25 again, happens a few times a year if you miss it.

They give free shipping if you have an Amazon Prime account.

They are refurbished but mine arrived in a nice Amazon box carefully prepped and other than light brush strokes on the screen which probably would disappear with a screen protector it's almost like new.

Even with the newest amazon rom you can still root/bootloader-unlock it, just takes several more steps and an hour of your time.

I'm not in a position financially to do it right now but anyone who is might want to consider drop shipping one to some of the developers around here to make sure we keep getting updates to this rom and maybe the next.

Not sure if ggow needs another or some of the other people who were active in similar devices.

This is the link but purposely breaking it in case that's not allowed on xda, not sure?

woot.com /offers/amazon-fire-hd-10-2017-your-choice-29

> Amazon Fire HD 10 (7th Gen, 2017) 10.1" Display

> $24.99 Condition Refurbished

> Free Standard shipping for Prime members

> 4 days left - OR - until sold out
[Fire HD 8 and HD 10 Original Android Development] 8bitword:
@chairmanmiaow, if copying the working recovery and recovery_x files to your other device fixes it I'd greatly appreciate a copy! ;⁠-⁠)

If I could flash stock recovery and get back to original firmware I might do the bootloader hack and get lineage 16 on there. But with the modified gpt on lineage 14.1 I don't know if it will break it.
[Fire HD 8 and HD 10 Original Android Development] URBANsUNITED:
Maybe I missed that point...

But How to get Netflix running on this Mod?

Thanks alot!

URBANsUNITED
[Fire HD 8 and HD 10 Original Android Development] chairmanmiaow:
There's some instructions back from reply #201, presumably they still work.

https://xdaforums.com/t/rom-testing-suez-lineage-16-0-05-july-2022.4232785/post-86433763
[Fire HD 8 and HD 10 Original Android Development] chairmanmiaow:
Ok to answer my own question this is how to recover from a bad twrp/flash. Combing through the original amonet root scripts was the key.

In my case I didn't want to brick it or cut off what access I still had as the bootloader was locked again and there was no working recovery available but it could still boot to lineageos with working root. This is what the partition map looked like via adb shell:

suez:/sdcard # fdisk -l /dev/block/mmcblk0
Found valid GPT with protective MBR; using GPT

Disk /dev/block/mmcblk0: 61071360 sectors, 1148M
Logical sector size: 512
Disk identifier (GUID): b998c40e-777a-4999-9548-19f4211da93d
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 61071326

Number Start (sector) End (sector) Size Name
1 1024 7167 3072K proinfo
2 7168 16383 4608K PMT
3 16384 18431 1024K kb
4 18432 20479 1024K dkb
5 20480 22527 1024K lk
6 22528 32767 5120K tee1
7 32768 43007 5120K tee2
8 43008 123903 39.5M metadata
9 123904 124927 512K MISC
10 124928 141311 8192K reserved
11 141312 174079 16.0M boot_x
12 174080 208895 17.0M recovery_x
13 208896 3515391 1614M system
14 3515392 4383743 424M cache
15 4383744 60619775 26.8G userdata
16 60619776 60845055 110M boot
17 60845056 61070335 110M recovery

Extract the original recovery.bin from the amonet-suez-v1.1.2.zip and adb push it to /sdcard. Then via adb shell as root:

dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p17

Then adb reboot recovery and immediately reboot the tablet back into the freshly restored Amazon recovery.

From there you can choose update from adb and adb sideload update-kindle-Fire_HD10_7th_Gen-40.6.5.9_user_659662020.zip to reflash the current Amazon firmware. After installing and rebooting my tablet started looping through the "optimising storage and apps" - if that happens to you then rebooting to recovery again and formatting data/reset to defaults fixed that and the tablet then finally made it all the way back to the "Welcome to Fire" introduction screen.

Obviously this procedure will completely wipe and default the tablet and I've only tried it once - YMMV.

@8bitword: Presuming your partition table looks exactly like mine did then the exact same procedure should apply to you. If not post it here.

Hope that helps someone else - looking backwards through the thread other people have done this several times lol. I guess next I'll find out if the whole unlock+root procedure is still valid in Feb 2023.
[Fire HD 8 and HD 10 Original Android Development] 8bitword:
Thank you for your assistance, Lineage 16.0 working fine. 🙃
[Fire HD 8 and HD 10 Original Android Development] spartasr:
Sorry if this was asked already, but as anyone figured out a way to get hands free Alexa or Google voice assistant working? I thought about trying to get pixel launcher but not sure if that would support it. I am getting the feature is currently unavailable message when trying to activate it.
[Fire HD 8 and HD 10 Original Android Development] smithbill:
As far as I am aware, to get handsfree Alexa working, you *have* to use FireOS (that's why I ended up returning to stock FireOS). But with root, you can replace the launcher & debloat it quite a lot whilst keeping Alexa alive.
[Fire HD 8 and HD 10 Original Android Development] spartasr:
Yea I figured, but I can't even get google assistant working, I tried downloading the google search and google assistant apps but still nothing. I'm wondering if it has to do with the pico gapps.
[Fire HD 8 and HD 10 Original Android Development] Infraviored:
I need some help.

I went through all the pain of opening up and unbricking it with amonet-suez-v1.1.2.zip from https://xdaforums.com/t/unlock-root-twrp-unbrick-fire-hd-10-2017-suez.3913639/.

Then I was in TWRP, I think 3.2.sth.

I tried to adb sideload the latest lineage for my device from this thread.

The installation finished with a red error message like /data partition not found.

I restarted the tablet, which is now stuck in a lineage os bootloop.

I thoughtthe problem might be not having the most recent TWRP. So I brought the tablet into hacked-fastboot, and flashed TWRP 3.6.1.2, which succeeded.

Not I can not even access my recovery anymore. When I try to with volume and pwr, the screen stays black.

A) why is the lineage in a bootloop

B) What about the /data partition missing error

C) How to get my TWRP to work again?

I am out of ideas.
[Fire HD 8 and HD 10 Original Android Development] lex66676:
Use amonet-suez-v1.1.2.zip

Short the point

sudo ./bootrom-step-minimal.sh

sudo ./fastboot-step.sh

This post https://xdaforums.com/t/unlock-root-twrp-unbrick-fire-hd-10-2017-suez.3913639/post-79169423

This tablet does not die, you will succeed. ))
[Fire HD 8 and HD 10 Original Android Development] Infraviored:
But I did exactly this. Shorted it, got TWRP working, I think version 3.2.sth.

Then I tried to adb sideload the latest lineage for my device from this thread.

The installation finished with a red error message like /data partition not found.
[Fire HD 8 and HD 10 Original Android Development] lex66676:
Lastest TWRP version

- 3.6.1-9.2

but I have lineage 14 installed and TWRP 3.6.1-9.2 , it has fewer video bugs.
[Fire HD 8 and HD 10 Original Android Development] droidjunkie:
why are you trying to "adb sideload" a OS install? you put the rom on your sd card and install it that way. do not use adb sideload.
[Fire HD 8 and HD 10 Original Android Development] Infraviored:
Normally I always sideload roms to not have to rely on an SD card at all. Maybe this indeed was the probelm, I will try.
[Fire HD 8 and HD 10 Original Android Development] gr4f1n:
Disclaimer: I've got no ideas of what I'm doing!

So I spent some time but dod manage to setup the gapps pico. The solution ended up with increasing the system partition size. Rough steps (probably some of them are excessive or not necessary, but I got no ideas what I was doing). I (almost) followed this idea.

Pre-requisites:

1. Make sure you have `gdisk`. I got it form this archive: parted_gdisk_fdisk_mkfs.ext4-AARCH64.zip as described in this thread.

Steps:

1. Reboot into TWRP recovery.

2. Push files to your device.

adb push ~/Downloads/parted_gdisk_fdisk_mkfs.ext4-AARCH64/gdisk /
adb push ~/Downloads/lineage-16.0-20220705-UNOFFICIAL-suez.zip /sdcard
adb push ~/Downloads/open_gapps-arm64-9.0-pico-20220215.zip /sdcard

3. (Not suer if this step has to be done no or later at step 10) Install lineage-16.0-20220705-UNOFFICIAL-suez.zip.

4. Get into adb shell.

5. Check the mount point via `mount`. You will need it later, so don't clean the console! Important part of the output is this:

/dev/block/mmcblk0p15 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p15 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)

6. From [B]/dev/block/mmcblk0p15[/B] you need to get the device name, which in my case was /dev/block/mmcblk0.

7. Allow gdisk executing: chmod +x gdisk.

8. Using gdisk, remove and re-create the cache (the command history is lost, so the commands are written from memory):

# gdisk dev/block/mmcblk0
> p
13 208896 10229759 1.4 GiB (this is already updated size) 8300 system
14 10229760 10387455 77.0 MiB 8300 cache
15 10387456 60619775 24.0 GiB 8300 userdata
> n (delete partition)
> 13 (partition number)
> n (delete partition)
> 14 (partition number)

9. At this point you have to re-create the system partition with slightly bigger size, and cache with the smaller one. I simply split the cache in 2, calculated the system end partition, created it, and created cache in the rest space.

10. On your tablet, go to `wipe` menu, and restore the `cache` and `system`. It will restore the file system on both.

11. (Not suer if this step has to be done no or before at step 3) Install lineage-16.0-20220705-UNOFFICIAL-suez.zip.

12. Install gapps.

13. Reboot device into system.

14. Profit.

If you did manage to repro, the details, especially about step 8 are very welcome.
[Fire HD 8 and HD 10 Original Android Development] MarvinMod:
im using 12.1 currently so my son can have his youtube and games working. unless 16 has been fixed for youtube and such but from what im reading, its still an issue.

the only issue i have with 12.1 which runs great is that it will show that it is charging but still show 1% battery life even after days on the charger. if i reboot, same issue but if i turn it off then back on its charged to 99%.

i read through the 12.1 thred and figured id post here where most are active, do i need to update anything or reflash anything to correct this issue or any insight on how to move forward? thanks in advance.
[Fire HD 8 and HD 10 Original Android Development] LearnEnglish:
Hi there. L16 rom has an error that Youtube zoom in a part of video many times. How can I fix it? thanks
[Fire HD 8 and HD 10 Original Android Development] MarvinMod:
Apparently progress has seemed to hult on this project. Move to 12.1
[Fire HD 8 and HD 10 Original Android Development] LearnEnglish:
I think I will com back to 14.1. thank you
[Fire HD 8 and HD 10 Original Android Development] smithbill:
I have two of these FireHD10 (suez) which until recently I was using as Alexa devices, but I've found Alexa on them to be rather 'hard-of-hearing' & infuriatingly slow in her responses. So I bought a couple of Amazon Echo Flex devices which were recently reduced to £10 each and they are much more responsive.

So I decided to reflash one of my FireHD's with this Lineage 16 ROM. I was still on TWRP 3.6.1-9.2, so that was fortunate. The ROM flashed without issue.

I tried flashing OpenGapps Nano & Pico, but ran into the Error 70 I think others have reported (to do with partition space I think). So I used NikGapps core (the older version P from 2020), it flashed fine and PlayStore works okay (although I think it updated itself after booting & I had to force-stop & clear data a couple of times).

I also rooted it by installing Magisk 26.1, but you do have to do the 'patch boot.img' method & flash the resulting img file to the boot partition in TWRP.

Now I've installed Google Speech Services & Home Assistant Companion app from the PlayStore & can get movement notifications from my ZigBee motion sensors!

So still some life left in my FireHD tablets 😁
[Fire HD 8 and HD 10 Original Android Development] Infraviored:
gdisk does not work for me.

I have

/dev/block/mmcblk0p15 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p15 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p14 on /cache type ext4 (rw,seclabel,relatime,data=ordered)

but then

gdisk dev/block/mmcblk0
GPT fdisk (gdisk) version 1.0.8

Problem opening dev/block/mmcblk0 for reading! Error is 2.
The specified file does not exist!
[Fire HD 8 and HD 10 Original Android Development] Infraviored:
I finally got this working.

But just realized the cameras are missing. When I try to download apps relying on the camera sensors, they tell me there are none.

Is there any way to enable them?
[Fire HD 8 and HD 10 Original Android Development] droidjunkie:
As can be seen in the first few posts, the camera is not currently working.

https://xdaforums.com/t/rom-testing-suez-lineage-16-0-05-july-2022.4232785/post-84492297

that post talks more about this issue. this rom is not intended to be used as a daily driver. If you need everything to be working I would suggest either going back stock or looking at the 2 older lineage versions if what you need is working on them.

Edit:

Here is the link to the post that lists what is working and what isnt working. fixed = works, todo = does not work

https://xdaforums.com/t/rom-testing-suez-lineage-16-0-05-july-2022.4232785/post-84478889
[Fire HD 8 and HD 10 Original Android Development] Infraviored:
Many thanks for the info!

My goal is not using the tablet daily, but as an interface for my Homeassistant. For this I need the camera detection working so the screen lights up when a user approaches.

From the list I see that camera is in fact not working in the mist recent version. But when was ist still working? It not working refers to all builds in the Google drive in post 1? So I need a lower version lineage?

Can I stick with my current TWRP?
[Fire HD 8 and HD 10 Original Android Development] droidjunkie:
As far as I am aware, yes you can keep the same recovery version.
[Fire HD 8 and HD 10 Original Android Development] bbt995:
your method is absolutely correct, I followed the instructions and it worked, thank you
[Fire HD 8 and HD 10 Original Android Development] bbt995:
Before: In recovery Wipe data, cache..

Step 1: Flash rom

Step 2: Flash nikgapps-core-arm64-9-20201231

End : not Wipe again
[Fire HD 8 and HD 10 Original Android Development] bbt995:
yes, Error in resolution 1080p, but 720p it 's ok
[Fire HD 8 and HD 10 Original Android Development] MarvinMod:
Try 12.1
[Fire HD 8 and HD 10 Original Android Development] bbt995:
thank u, but i'm on LineAge OS 14.1 , it 's ok , some bug in codec for Youtube
[Fire HD 8 and HD 10 Original Android Development] smithbill:
I also use my FireHD10 with LineageOS as a HomeAssistant screen, but rather than use the camera to wake the screen (and I don't think this tablet has a proximity sensor?) I installed HotWord Plugin Free from PlayStore and configured it to recognise me saying "Home Assistant!" and then used MacroDroid or Tasker to receive the 'intent' from the plugin & wake the screen and bring the HomeAssistant Companion app to the front. It worked okay, but I found that HotWord Plugin just woke the tablet up at lots of different noises.

In the end I just decided to enable 'DoubleTap to Wake' on the FireHD and that works much better.
[Fire HD 8 and HD 10 Original Android Development] soonsh:
After a couple of hours of reading and really very little effort, I've got my suez Fire rooted and running Lineage 16 with OpenGapps. Thanks to all who posted helpful info. Here's what I did for those of you still looking:

1. Offline root seems to be necessary with new firmware. It probably wouldn't hurt to use this method even on older firmware. Huge thanks to @smartypantsuk for the writeup.

https://xdaforums.com/t/unlock-root-twrp-unbrick-fire-hd-10-2017-suez.3913639/post-85824221

2. After successfully rooting, install TWRP. Just following the main guide worked.

https://xdaforums.com/t/unlock-root-twrp-unbrick-fire-hd-10-2017-suez.3913639/

3. Some say you need to upgrade TWRP to a newer version, I did this but it reverted after a reboot, I said screw it and used the older version to flash lineage and had no problems. OP for this thread gives you all you should need, just download lineage image and flash from TWRP. In my case Lineage booted up immediately with no problems whatsoever after this.

4. I used this great guide and script from @psi78 to install opengapps. Huge thanks.

https://xdaforums.com/t/rom-testing-suez-lineage-16-0-05-july-2022.4232785/post-87282103

Simple as that, I'm running lineage with everything I need and so far no problems.
[Fire HD 8 and HD 10 Original Android Development] MarvinMod:
Try using YouTube in full screen and take some videos and pictures... All that working good?
[Fire HD 8 and HD 10 Original Android Development] Klaus R:
@admin mistake please delete
[Fire HD 8 and HD 10 Original Android Development] smithbill:
Personally, I found Lineage-16 on both my FireHD10, to be sluggish & not very responsive. Yes, they were useable, but opening browser tabs, switching apps, receiving notifications (from my Home Assistant server) were all frustratingly slow. Presumably if all you want is to play videos, then it's fine.

Anyway, I reverted both my FireHD10 to Lineage-14 and the difference in responsiveness is vastly improved - it's actually useable! I rooted them with the latest Magisk & installed the system files to 'patch' the video performance, and as far as I can see YouTube videos play fine in Chrome (no idea if it works in the YouTube app, fullscreen or at HD resolution - I didn't try as I'm not interested in anything more than checking out the occasional tech review on YouTube). So for me, Lineage-14 is vastly better than Lineage-16.
[Fire HD 8 and HD 10 Original Android Development] _ck_:
The universal double-tap-to-wake using ftsgesturewakeup works awesome on this tablet/rom

So the last remaining problem I am encountering on almost a daily basis now is that cpu overuse/overheat problem from what I believe someone once in this thread called the "finger flicker bug" ?

Where it slowly eats the first two cpu cores and battery?

I cannot find the original reference or if there is any workaround

I've tried smartpack to change the cpu governor and greenify, neither solve the problem and sometimes make it worse.

There was also some kind of display update bug in some apps but I seemed to fix that by using developer options to force the GPU to use used for even 2D rendering
[Fire HD 8 and HD 10 Original Android Development] psi78:
You just need to enable Power Saving Mode, it reduces the probability of the cpu overheat bug, that's what worked best for me. And if you have the tablet in a good state, try to avoid rebooting/use flight mode over night.
[Fire HD 8 and HD 10 Original Android Development] _ck_:
You mean the power saving setting under the battery menu?

I remember trying to set that and it wouldn't let me, is there an optional driver or patch I am missing?

I keep the tablet in airplane mode 24/7 but I am not quite sure what that does otherwise without LTE

Sometimes but not every day, I come back to the tablet and the wifi has mysteriously turned itself off.

I used smartpack to try different governors and randomly "interactive" with a cpu limit of 1000mhz seems to keep it way cooler. It used to feel warm near the power button/usb port but now no problem.

I want to find an easy way to put the CPU and SOC temps in the statusbar.

Aha, I finally found your old post on this, "SurfaceFlinger" not "finger flinger" LOL LOL

https://xdaforums.com/t/rom-testing-suez-lineage-16-0-05-july-2022.4232785/post-87874803

But what's interesting is I do not have the power saver option, or fails to work.

Also, this might be related, maybe something I am adding is allowing it to go into a fatal sleep mode so it eventually overheats.

Somehow I fixed this with "interactive" governor and 1000mhz limit and the double-tap-to-wake. Maybe it never goes to (deep) sleep now with double-tap-to-wake.
[Fire HD 8 and HD 10 Original Android Development] cRaZy-bisCuiT:
Has anyone tried to build agains newer LineageOS Source like e.g. LineageOS 20? Does it build?
[Fire HD 8 and HD 10 Original Android Development] _ck_:
This awesome tablet is back on Woot for $25 used/refurbished

back suddenly on Monday June 5 2023

Anyone who can afford it should send one to a dev to make sure we keep getting rom updates.

woot .com/offers/amazon-fire-hd-10-2017-7th-gen

(link purposely broken, remove space before dot)

Mine came almost like new, just the vaguest of brush scratches on the display that are invisible when on and probably would disappear entirely with screen protector.

Despite their rom update I was able to root and bootloader unlock by hand which I think I posted the steps either in this thread or another.