yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] psi78:
Cool you tested it. Did you try the other app alternatives too? I'm on LOS12.1 atm and can't test it.

@ggow you used some of those ibilux patches for the mediatek chipset and omx. There is one patch which fixes the zoomed in videos too apparently, maybe that's the fitting fix for the zoomed in videos on yt app on this rom?

See https://github.com/ibilux/android_d...x-video-autoscaling-on-old-OMX-decoders.patch
[Fire HD 8 and HD 10 Original Android Development] smithbill:
This isn't quite the right thread, but as @lipsand had enquired here & I had posted some guidance to his question, I thought it useful to include some details here to answer his question & also in case it's helpful to others.

I decided to return my Fire HD 10 (Suez) to running Fire OS as I was finding lineage rather lagging & without Alexa, my Fire HD was just another unused Android device.

I downloaded the latest Fire OS (v 5.3.7.3) from Amazon here and copied it to my tablet, renamed it to a zip & flashed it in TWRP and it booted up fine.

I then ran into some problems: I couldn't get my Win11 laptop to recognise the tablet as a USB device even after trying all kinds of device drivers. I even tried re-imaging my laptop. Eventually, after installing legacy MTP device drivers & rebooting my Fire HD after clearing cache/dalvik in TWRP multiple times, I managed to get a working connection & could then use ADB with the tablet. I'm not sure what was going on, but the issue was obviously the FireHD as my other FireHD running an older FireOS had no such problems on the same laptop.

Anyway, with a working ADB connection, I was then able to use Fire Toolbox to install Google Services & debloat etc.

Then I realised that I had lost 'root' as I guess Amazon had patched the root exploit with the latest version of Fire OS v 5.3.7.3 (I think others have posted about this, but I hadn't realised until after I re-flashed my tablet).

So I downloaded the *latest* Magisk manager (v 25.2) & installed the Magisk app. I then used the Magisk app to install Magisk itself & selected the "Patch vbmeta in boot image" (not sure if I needed to do that?) & then I chose the method as "Select and patch a file" (which was the only option available).

I then did the Magisk patch on the boot.img which I extracted from the FireOS .bin file I had previously downloaded (v 5.3.7.3). This then generated a "magisk_patched-25200_oFAdX.img" file

Then I rebooted the tablet into TWRP & flashed the patched .img file to the "boot" partition. Cleared cache/dalvik & rebooted.

And I now had the latest FireOS (v 5.3.7.3) with latest Magisk root (v 25.2) and I could install Nova Launcher etc from PlayStore.

I also use an app call "App Freezer" from Wakasoftware to do some debloating & importantly to disable the FireOS launcher (Paladin & Home Pages) although you have to use their older version 1.0.6 as the updated it after that to remove the System apps tab (it's a good app because it's easy to disable or reenable apps as required).

So I now have a clean & spritely FireOS rooted with Magisk.
[Fire HD 8 and HD 10 Original Android Development] likwidchz:
This is pretty cool, what do you think about somehow cloning your custom pre rooted build and upload it somewhere? I wouldn't mind trying it out. I'm sure a handful of others would use it.

Infact in another thread someone explained I could download the latest fireHD 10 2017 from amazon and rename the bin to zip and flash. I sort of joked "it's that easy!@?" I guess it is. I had assumed that when the OS went out and updated it would overwrite TWRP, which I'm glad I was corrected and it does not do that.

I tried this build similar? to your customization and realize it does not connect to wireless.

5620_Fire_HD_10_pre_rooted_optimized_stock_rom-signed.zip
[Fire HD 8 and HD 10 Original Android Development] smithbill:
I don't understand the Android build structure enough to know whether my rooted boot.img file contains any personal data, so I'm not going to upload it anywhere I'm afraid (I suspect the boot partition is just a pure bootstrap & personal data is all in Data, but I don't know so will err on the side of caution).

That said, it seems quite easy to generate your own rooted boot.img from the latest FireOS v 5.3.7.3:

1. download FireOS v 5.3.7.3 from Amazon & rename it to a .zip

2. flash it to your Fire HD 10 (Suez) in TWRP (it won't overwrite TWRP but you will lose root)

3. boot the tablet & use Safari to download Magisk v 25.2 .apk from GitHub and install it

4. Use the installed Magisk app to 'install' Magisk itself - this doesn't actually install anything, it just allows you to 'patch/root' a chosen boot.img which you have to install yourself using TWRP. I chose to "Patch vbmeta in boot image" but I'm not sure if I needed to do that.

5. The .img file you want to 'patch/root' using Magisk is contained *inside* the .bin file you downloaded from Amazon. So you need to extract it from the .bin archive (this is the slightly hard bit because a fresh FireOS doesn't have any tools to allow you to do that - so you'll either have to do it on a PC with WinZip or else use Fire Toolbox to install Google PlayStore to your tablet & then use a decent file explorer app to extract the .img from inside the .bin on the Fire HD 10).

6. Once you've generated a new 'patched/rooted' .img file using Magisk you then need to reboot back into TWRP.

7. Once in TWRP install the new boot.img file to the BOOT partition (make sure it's to the boot partition or you may well screw up your Fire HD 10!)

8. Wipe cache/dalvik & I suggest you reboot to Recovery (not the system!) just to make sure your new boot.img doesn't somehow get replaced by something Amazon have done.

9. Wipe cache/dalvik again & reboot to system & check in Magisk if it's installed & your Fire HD 10 is rooted.

Then you can use Fire Toolbox to debloat & replace Amazon launchers etc etc
[Fire HD 8 and HD 10 Original Android Development] smithbill:
Well, your write up is more informative & certainly more entertaining (I'll hazard a guess from your use of the term "hosed" that you're a good 20+ years younger than me! 😆)

I should apologise to Op for the last few posts being off topic, but on the basis that lineage development on Suez is 'paused' whilst @ggow learns about fatherhood, it seemed helpful to post about how to reinstall the latest Amazon image & get root working (for the time being).

@likwidchz I am assuming from your detailed write up, that this worked fine for you with no real problems?

One minor correction I should make, is that you won't normally lose root when flashing a new ROM in TWRP. I believe the only reason you lose root in this case is because Amazon patched something in their later releases which over-wrote root.

Also, I've no idea what vbmeta is/does, so I've no idea if it was necessary to tick that box in Magisk.
[Fire HD 8 and HD 10 Original Android Development] likwidchz:
Yeah! it worked for me. We will leave age as a mystery.

No real problems, everything was honestly pretty straight forward, everything worked without really any WTF moments..

I don't really get steps 10-11 portion. You patch the boot image/partition and wipe cache/dalvik then reboot to recovery and wipe cache and dalvik a 2nd time? Then reboot. seems kind of circular, but not sure. Does the boot image also populate the Cache and Dalvik? To be clear, I have no idea what in the world those partitions do. I could see somehow re'writing that portion if something is redundant in the steps.

And after spending all this time messing around with getting the OEM fire OS working at the latest release with root, its kind of garbage lol. Lot's of stuff to have to do, their "REGISTER THIS TABLET BS" logo on the front page, needing to replace the launcher with some other rando launcher. It's kind of fiddly.

I was having issues with one of the releases with lineage not working too well with an app I have that I coded with processing.org, I would get mixed framerates in it with Linage 12, 14, fire os and literally all of the different flavors. I also noticed battery life issues. One of them being one of the cpu's didn't ever slow down/sleep state and I saw bad battery life issues. To be clear, these tablets are old, used, I have 5 I bought off ebay to mess around with. I do not know if I am chasing the wind here with that one.

I would based on the off'topic'ness of this post, feel free to start a new one and we can discuss it there? Feel free to take your guide I re wrote and modify it again and make a new thread

One thing I can see helpful at least for me, is a listing of essential software apps to install for more customization of things. Maybe add some fluff to the write up about essential hacks/adjustments to the OEM OS to make it better.

Additionally it seems kind of silly. Spend all this time rooting the Fire OS, to install TWRP, to then put it back on and have to spend heaps of time messing with it to get the thing working the way you want vs just putting Lineage on it? Oh well. No one doesn't like a good comprehensive guide to do things.

Thanks again! This is really great.
[Fire HD 8 and HD 10 Original Android Development] smithbill:
You can save yourself a lot of time & effort debloating etc by using the Fire Toolbox - it's quite helpful.
[Fire HD 8 and HD 10 Original Android Development] likwidchz:
Oh yeah I used that in this example. Its pretty helpful.
[Fire HD 8 and HD 10 Original Android Development] computerworm:
Hi Kate6,

I was having trouble with installing GApps, so i tried to do what you described here, and at one point parted told me i had to reboot to get the kernel to register the partition changes. So I did, and now my device is in a bootloop. I don't understand, I was very careful of which partitions I nuked. I'm sure I didn't overwrite recovery. But it shows the Amazon logo screen and that's it. I can't even boot to TWRP. I tried to follow these instructions here, and it didn't work. Any idea how to fix it?
[Fire HD 8 and HD 10 Original Android Development] Kate6:
https://xdaforums.com/t/unlock-root-twrp-unbrick-fire-hd-10-2017-suez.3913639/
[Fire HD 8 and HD 10 Original Android Development] Shack70:
Power off completely, hold the volume down and power at the same time. When the Amazon logo appears it should say recovery at the bottom in small print. At that point let go of the two buttons. and it should enter TWRP.
[Fire HD 8 and HD 10 Original Android Development] psi78:
In other words (because the Volume down is not marked) hold down power and the Volume key next to the headphone jack.

In case the repartitioning damaged the recovery partition i guess it'll get more complicated. I guess i'd try to reflash recovery then with TWRP from a pc and suez in fastboot mode.

See also here how to flash recovery in fastboot mode.

How to Flash TWRP Recovery via Fastboot on Android

After completing all the steps mentioned above, let's understand a simple and fairly easy process to flash or install TWRP Recovery on Your Android Device

techrrival.com

I think the key combination for suez to get it into fastboot mode was to hold power and volume up at device startup, so the other volume button near the edge of the longer side of the display/not near the headphone jack.

Edit: Hmm no, doesnt't work on my device

In case the device doesn't react anymore you could also force a reset by holding down power button 20 seconds.
[Fire HD 8 and HD 10 Original Android Development] Mlinko6:
Dear All,

Does someone has the same Issue? Main Storage - not available? Can I somehow change that?

Thx!

Rok
[Fire HD 8 and HD 10 Original Android Development] Mlinko6:
I think I found the solution... Will keep you posted. Found it! Sorry to bother you!
[Fire HD 8 and HD 10 Original Android Development] Kate6:
It's got a whole host of complexities and kinks because of how the bootloader hack works, where it modified the partition table to add the recovery_x and boot_x partitions... But one (in my opinion) very nice thing about this device is that regardless of how screwed up it gets, the unbricking procedure described in the first comment of https://xdaforums.com/t/unlock-root-twrp-unbrick-fire-hd-10-2017-suez.3913639/ where you open the thing up and short a particular contact to ground should literally always work.

I feel like that might be a simpler path to take than trying to help someone relatively inexperienced who tried to do something a bit too outside their skill set figure out precisely what they did and what ended up getting screwed up as a result.

This device's actual fastboot mode is pretty heavily locked down. The bootloader hack enables a "hacked fastboot" mode that lets you flash any of the partitions. But there's all sorts of ways the bootloader hack can malfunction if you've left the partition table in an uncertain or inconsistent state and restarted the hardware.
[Fire HD 8 and HD 10 Original Android Development] Sherooo3:
hallo everyone,

i dont understand why I keep getting err 7 while installing lineage-16.0-20220705-UNOFFICIAL-suez.zip

i am using twrp_suez_3.6.1-9.0 but also used twrp_suez_3.6.1-9.2 and it didn't work.

i wiped everything but the sd-card before installing the Rom. and also tried to reboot in recovery after wiping.

lineage-16.0-20220506-UNOFFICIAL-suez.zip works. it's just the lineage-16.0-20220705-UNOFFICIAL-suez.zip not wanting to be installed :(

any more Ideas?

System =15998 MB/used 43MB

Data= 9275MB /used 0MB

cash=3440MB/used 6MB
[Fire HD 8 and HD 10 Original Android Development] psi78:
Hmm did you repartition your System partition?

Looks quite big.

Doesn't make much sense to make it that big though, as in Android the System partition is readonly normally. So only ROM and gapps normally go on it. The rest will be unused space, because all further apps and app updates go to Data partition. It's not like in Windows or Linux where you install more programs and apps to your System partition.

On my Xperia Z5 the System partition is 5GB, and only 1,8 GB used by Android 11 and gapps.

Also in TWRP i'd try to repair/ reformat the partitions (Cache, System, Data), then power off first (before you flash the ROM), and restart to recovery, and only then flash the ROM and gapps.
[Fire HD 8 and HD 10 Original Android Development] luk2009:
the tablet keeps trying to go up.

the Fire logo appears and then

optimizing system storage and applications....

then the fire logo again and then

optimizing system storage and applications....

and that process repeats itself indefinitely.

what can I do?
[Fire HD 8 and HD 10 Original Android Development] likwidchz:
Not sure what you did to cause it to get into this condition.

If you have TWRP on it, wipe the device within TRWP and give it another go.

If you don't have TWRP on it, Try flashing the OEM binary again with fastboot. Then once its flashed and boots up, root it and try again with the lineage rom.

If someone can correct me on this, I think that is soft bricked. You might want to search around for what that is and how to solve it unless my attempt at help is indeed help and not a rabbit hole.

Good luck.

Take care,
[Fire HD 8 and HD 10 Original Android Development] luk2009:
I have TWRP and I have wiped everything except internal storage and flash the bin file changed to .zip

and have the same problem
[Fire HD 8 and HD 10 Original Android Development] luk2009:
I did the process several times and the fifth time, the system came up.

fire os 5.7.0.0
[Fire HD 8 and HD 10 Original Android Development] likwidchz:
Well that is weird then. Perhaps someone else can chime in and provide a reason. I'm just guessing at this time.

Glad you got it all taken care of.
[Fire HD 8 and HD 10 Original Android Development] psi78:
I'm no expert on this, but i think ART (Android Runtime) is precompiling apps with dex2oat tool (for quick startup and preloading by the Zygote Process) at the first boot after installation.

On former Android versions (before Android 5) this is done by Dalvik, but just in time compiled then at app start i think in Android 5/LOS 12 it's still Dalvik.

I read that some ROMs have a timeout regarding the boot process, and reboot after a time.

So i guess if the boot time is too long, rebooting Android several times leads to precompiling a part of the apps/apks, then the next boot some more of the apps are precompiled and apparently after some boots all of the apps.

Wiping Dalvik/ART cache on Android 5/LOS12 leads to this whole precompiling process done again (i just tested it on LOS12/Android 5.1 for suez)

So try to avoid it if not necessary i guess.

Maybe also something wasn't wiped yet, wiping internal storage, or also formatting Data besides formatting System and Cache partitions, is possible before you do a reinstallation of a ROM, i've done it several times.

Edit: hmm apparently from Android 5.0 and later ART is used, but it can be configured in the system.prop of a device before ROM building (i've done it when i compiled LineageOS for my Xperia Z5) or in /system/build.prop with a built ROM.
[Fire HD 8 and HD 10 Original Android Development] likwidchz:
I think they need to patch these tablets... all of them, so you can see the boot process happening and not stamp an image at boot. That way when something bombs out, there is some breadcrumbs as to what tanked.

Glad you know about this! I had no idea how this stuff works behind the scenes.
[Fire HD 8 and HD 10 Original Android Development] psi78:
Yeah, i agree. It sucks when you can't see what 's happening during the boot process.

if you wanna read something more, these articles may shed some.light:

What the Zygote!?

Android OS boot process explained with focus on Zygote

medium.com

Difference between dexopt and dex2oat?

Google is moving from Dalvik to ART(Android Runtime). I was trying to understand, how it is going to improve the performance. The best explanation I found is the below image: One of the main com...

stackoverflow.com

Android Runtime - Wikipedia

en.wikipedia.org
[Fire HD 8 and HD 10 Original Android Development] shaunblyde:
I have this problem when flashing a stock image (.bin renamed to .zip) - except I don't get the "optimizing" message, only that I am stuck on the fire logo screen for hours on end. I have TWRP installed and have tried wiping system (and other partitions), many different stock roms from the Amazon website and XDA. Unfortunately no luck with any of this.

Anyone have suggestions on what to flash or what I'm doing wrong to get back to stock FireOS with TWRP installed?
[Fire HD 8 and HD 10 Original Android Development] psi78:
Did you format Data partition too (not only wipe it)? Then power off/reboot to recovery before you flash.
[Fire HD 8 and HD 10 Original Android Development] shaunblyde:
Just tried this - explicitly formatted Data (then typed "yes"). Shut down, then booted into recovery again to flash stock zip, with no luck unfortunately. Still sitting on Fire screen 10 minutes later.
[Fire HD 8 and HD 10 Original Android Development] psi78:
Hmm, just tried it, worked perfectly in one go for me.

Did you use the correct file for your device?

I wiped everything besides Micro SD card, i.e. Dalvik / ART cache, System, Data, Internal Storage, Cache.

Then i formatted Data partition.

Then power off and boot to TWRP again.

Then installed the renamed .zip file, didn't wipe Dalvik/ ART cache or cache at this point.

Then rebooted, FireOS taking like 2 mins to optimize the apps (there was visible progress at the progress bar), then i was in.
[Fire HD 8 and HD 10 Original Android Development] shaunblyde:
Thanks for testing it out. To confirm, I have the 7 Generation Fire HD 10 (Suez) and am following the method you advise, and am using the file from this link (renamed as .zip) for the stock image: https://www.amazon.com/gp/help/customer/display.html?nodeId=G2JXLC4L34GX73TE

Fire HD 10 (7th Generation)​

FireOS 5 | FireOS 5.3.7.3

Download Software Update

Is this the same stock image you are using? I am only installing the single zip/image, nothing additional (root, Magisk, Gapps etc), I assume this is the same under your testing?

I am wondering if perhaps my partition table or boot image needs manual intervention after the custom rom installations?
[Fire HD 8 and HD 10 Original Android Development] psi78:
Yeah, that one. There's a boot.img inside the zip, so it will flash boot image just like other ROMs. If it doesn't boot probably you haven't wiped/formatted everything. You could also use the repair partition function of TWRP on Cache, System, Data partitions or reformat these with ext4 filesystem. Unless you didn't repartition the device or messed up something with adb there shouldn't be any more interventions needed than that. Edit: Maybe it's the TWRP version, i'm using not the latest one, but 3.6.1-9.0
[Fire HD 8 and HD 10 Original Android Development] shaunblyde:
Thanks, still no luck unfortunately. Seems I am following the same process as you. I just updated to 3.6.1-9.2 yesterday, but before that was using 3.6.1-9.0, and still no result, so I think that is unlikely to be the problem, but can roll back TWRP and try.
[Fire HD 8 and HD 10 Original Android Development] psi78:
I'd try to wipe everything possible (just not Micro SD card if you have an external sd card inserted) + format data, then also use the repair partition function (in the wipe section of TWRP) on every possible partition.

I had it once or twice when i did stuff with adb that for example the cache partition was broken.
[Fire HD 8 and HD 10 Original Android Development] shaunblyde:
Still no success :( I've tried all you've mentioned, so really not sure what to try next.

Just to confirm, your partitions are all ext4 and match the sizes below? I have tried to repair, "change file system" to ext4 (which they already were, I was just hoping to refresh the partitions) and wipe them all - besides for the system partition, which I could only wipe, not repair or "change file system".

/system ext4 1557MB (No repair option, only Change File System)

/data ext4 26899MB

/cache ext4 394MB
[Fire HD 8 and HD 10 Original Android Development] psi78:
@ggow As it turns out the contents of this patch are already in the LOS16 source code of

frameworks/av/media/libstagefright/ACodec.cpp

Just the define is missing, so this entry in the same file is needed to enable the legacy rescaling:

#define USE_LEGACY_RESCALING
[Fire HD 8 and HD 10 Original Android Development] psi78:
Hmm, something seems wrong with your system partition then, you should be able to wipe it, which means it would be reformatted.

Can you use repair partition on it and format it as ext4?

Edit: Oh you said, you can't, well i guess try to remember what you did with it, or switch the deivce off, then go to recovery and format it, maybe unmount it first?

Or maybe you have to reconstruct the system partition.

You could also try to do this what @Kate6 suggested:

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

Yeah all partitions are ext4, and i think they have the same size as yours
[Fire HD 8 and HD 10 Original Android Development] shaunblyde:
Managed to wipe and repair system partition, it was not mounted by default. Once I mounted it, it was treated the same as the others. But still nothing sadly. Thanks for your help though.
[Fire HD 8 and HD 10 Original Android Development] psi78:
Tried to rebuild the ROM with ggow's sources, this fix and booting with only the little cpus 0-1. At one point i was able to build the kernel/boot.img, but for the rest of the ROM the build seems to be missing/dependent on libnvram sources. Don't really have a clue where to get that or what i'm missing there. Anyone got an idea?
[Fire HD 8 and HD 10 Original Android Development] Syco54645:
So I am a bit confused, is the camera working at all in this rom? It seems like the camera may be fine but cannot do video.
[Fire HD 8 and HD 10 Original Android Development] _ck_:
Install LiveBoot app by Chainfire

Way, way too much info on default settings but can be tuned very well

You'll be amazed how many typical errors occur on every rom boot
[Fire HD 8 and HD 10 Original Android Development] likwidchz:
I'll check that out! thank you. I had no idea there was a method to do this.