yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] lilyrtn:
I flashed this ROM just today. I already had the Lineage 14.1 version installed along with the 3.3.1-0 version of TWRP. The flash was successful but I accidentally used the wrong GApps package (64 bit instead of 32 bit).

When I attempted to boot back into recovery to wipe and reflash GApps, I was never able to boot into recovery. Here is a list of things I have tried and the outcomes:

Booting into recovery using the "Advanced Reboot" options and selecting "Recovery" in the power menu =====> boots to the OS directly

Booting into recovery using the power and volume down buttons =====> boots to the TWRP splash screen which occasionally flicker but never advances to the menu

Using ADB commands "fastboot flash recovery twrp.img" and "fastboot boot twrp.img" while in the bootloader screen =====> returned a "FAILED (remote: the command you input is restricted on locked hw)"

Has anyone encountered this same issue either after flashing this ROM or a different custom ROM? I have looked around at other forums and was told to come back to the source of the custom ROM. I am a total noob with regard to this stuff and I was not the person who originally installed TWRP or lineage on this device.
[Fire HD 8 and HD 10 Original Android Development] billyrich:
I think you need to update the twrp: https://xdaforums.com/t/rom-unstabl...ge-18-1-25-october-2021.4352241/post-85844385
[Fire HD 8 and HD 10 Original Android Development] Reynald0:
The problem happens also with the newer TWRP, and without Magisk or Gapps, I have karnak in the same state of stale at TWRP.

I personally haven't tried anything to resolve it, but I can think of redoing the hw exploit procedure again or using the OTA if it is configured? I don't know if reflashing TWRP again will solve the issue.
[Fire HD 8 and HD 10 Original Android Development] Korin67:
I tried this ROM to my karnak, and need help about TWRP. My TWRP is of version 3.3.1-0, this might be the source of the problem. With this TWRP, I clean installed the ROM, and then MindTheGapps-13.0.0-arm. The ROM was successfully installed but the latter finished with error. Then, I booted the ROM, with some time delay, it booted. Wonderful, but I could not find Google store (ofc). Next, I tried to go into TWRP. TWRP logo appears but it DOES NOT start. I waited more than two minutes only got TWRP logo. Should I update TWRP, if so where can I get?

Thank you for your help.

Edit: my problem is the same as the previous article submitted 5 mins before.

Edit2: Sorry for this post. A clue is shown in the article #24. I will try.

Edit3: So request to new help. How can I boot into TWRP. Now I am stacked as:

fastboot flash recovery new_twrp.img

Sending 'recovery' (20480 KB) OKAY [ 1.165s]

Writing 'recovery' FAILED (remote: 'the command you input is restricted on locked hw')

fastboot: error: Command failed
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
Almost done means that its getting normal, The UI is smooth as for now, i will update the statuses.
[Fire HD 8 and HD 10 Original Android Development] Korin67:
It seems we are on the same boat. If you find a way without redoing hw exploit, please report it. I do not want to re-open the TB. If I can use brick.sh, no need to open the TB though. Waiting for your or someone else's good news.
[Fire HD 8 and HD 10 Original Android Development] Reynald0:
I have no problems to redo the hw exploit, I just wait the OP to suggest a way to fix it.
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
Have you ever booted the kamriki iso and did boot-recovery.sh ?
[Fire HD 8 and HD 10 Original Android Development] Korin67:
I have never heard of kamriki.iso. May I know where I get the information? Thank you.
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
https://github.com/amonet-kamakiri/fireiso/releases/tag/v2.0.0

- Download the ISO linked above

- Open Rufus and then select the ISO and flash it to the USB https://github.com/pbatard/rufus/releases/download/v3.21/rufus-3.21.exe

- and then after that boot into the USB drive

- download the file after booting https://xdaforums.com/attachments/amonet-karnak-v3-0-1-zip.4818373/

- then extract the archive

- then try to run sudo ./boot-recovery.sh

If the script fails to work

- run sudo ./bootrom-step.sh

- press and hold the pwr button on the tablet and then plug the USB in and press the power button
[Fire HD 8 and HD 10 Original Android Development] Reynald0:
It says waiting for preloader, it means we have to do the hw short method to expose it right?
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
You can try that , I did the hardware way but if I accidentally bricked mine I use bootrom step and then bootloader step script
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
boot-recovery.sh does not require shorting. Just connect the tablet powered off.
[Fire HD 8 and HD 10 Original Android Development] Korin67:
Unfortunately, boot-recovery.sh did not bring to the recovery. So I tried amonet again. This time, because I do not want to open my TB, I used brick.sh. It worked. Then did bootrom-step.sh. The step was successful and end with bootloader (fastboot mode).

I did:

fastboot flash recovery new_twrp.img

Okay the new TWRP was successfully flashed. Then boot to the recovery.

On the screen I can see TWRP ver. 3.4.0-0, but does not proceed. The situation is exactly the same when I had TWRP 3.3.0-0.

How can I get TWRP work? Good thing is LOS20.0 is always stay and I can do

adb reboot bootloader, to enter fastboot mode.

Edit: I tried boot-recovery.sh and boot-fastboot.sh for the power-off tablet. These scripts just power it on, mean LOS20 boots normally.
[Fire HD 8 and HD 10 Original Android Development] jumstec:
This is a problem that has been there since lineage18, but the wifi access point does not work.

I don't know if this was known in 18 or not, but it is not that much of a problem if it doesn't work in the first place.
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
What is the issue with the wifi ? It works fine for me
[Fire HD 8 and HD 10 Original Android Development] jumstec:
If I turn it off and then try to turn it on again, I get an error.

When I go back to the previous page, it says error on wifi access point and I cannot turn it on.

Perhaps this is another on/off issue?
[Fire HD 8 and HD 10 Original Android Development] mousepaddle:
I have exact the same problem after updating to lineage-20.0-20221230-UNOFFICIAL-karnak.zip.

No way to boot into recovery. I also tried to unbrick the device with hw, hacked bootloader and new flash of recovery....

Is there any known fix for that?

Or do I have a chance to update to lineage-20.0-20230102-UNOFFICIAL-karnak.zip, e.g. with a adb command?

With LOS18 I had access to the recovery. The bug seemed to be come up with the update to LOS20.
[Fire HD 8 and HD 10 Original Android Development] ngool:
Any news on the microphone / audio issue? Noob question, but could I find the repo to the source code to see if there is any development or to maybe contribute? I could only find a few outdated forks. Or is this a private repo?
[Fire HD 8 and HD 10 Original Android Development] Goat24K:
Hey Guys, i am new for flashing the Amazon Fire HD. This Rom works also for HD 10 2021 Tronia?
[Fire HD 8 and HD 10 Original Android Development] DerivativeOfLog7:
No, only karnak; plus I don't think there's currently an unlock method for newer models anyway
[Fire HD 8 and HD 10 Original Android Development] Alotheone:
Hello everyone, it has been a while. My Karnak suffered a fall and unfortunately received injuries, but still working. Folks whose Karnak running LOS20, how's your experience running with/without Google apps? I want to try it again as at the time (November 2023) I did not have the luxury to switch as often. Now I picked up a Galaxy S8 Plus DUOS so I can now relinquish LOS16. One half of me loves the ROM flashing but the other half is tired of switching back and forth and is hesitant knowing that the RAM problem still present.
[Fire HD 8 and HD 10 Original Android Development] DerivativeOfLog7:
I haven't even attempted to run it with gapps knowing how demanding they are

I'm also running it with animation disabled due to the stuttering issues
[Fire HD 8 and HD 10 Original Android Development] Alotheone:
Yeah, I'm planning to run it Google-less.
[Fire HD 8 and HD 10 Original Android Development] Alotheone:
1 week later. as you said @DerivativeOfLog7 , I never knew how much I missed the 3.5mm jack until it's gone. I also encountered a system freeze when trying to press the power button. I'm going back to LOS16 or LOS18.1 for now. @Kaijones23 is LOS19.1 available anymore? I wanted to try it out if available.
[Fire HD 8 and HD 10 Original Android Development] Reynald0:
I think 19.1 was never available.
[Fire HD 8 and HD 10 Original Android Development] Alotheone:
oh ok.
[Fire HD 8 and HD 10 Original Android Development] Giovanni Carraro:
hi, I wanted to ask if Lineage OS 21 is still in development?
[Fire HD 8 and HD 10 Original Android Development] Reynald0:
I think yes, mt8163 has commitments, greetings to all the devs 🐸
[Fire HD 8 and HD 10 Original Android Development] Reynald0:
I tried also restore the stock recovery, but terminal says this is locked device.

Maybe we triggered e-fuse :eek:
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
Did you make sure to uncheck the option to update to lineage recovery in the setup?
[Fire HD 8 and HD 10 Original Android Development] SCrid2000:
Just wanted to say thanks for the rom, especially for such an old device. I was able to get TWRP installed with xyz's instructions and Lineage 20 seems to be running great. Makes for an awesome inexpensive tablet for the kids.
[Fire HD 8 and HD 10 Original Android Development] Korin67:
So far at least four people (including me) are suffering from locked? TWRP. What I did to install TWRP is to go to amonet and apply bootrom-step.sh. Some people did this with hw (shortning) and others (like me) with sw(brick.sh) method. In any case bootrom-step.sh finish (if successful) with fastboot mode. If I proceed with fastboot-step.sh, then TWRP 3.3.1-0 will be installed and activated (but stacks). Otherwise, under fastboot mode, apply; fastboot flash recover new_twrp.img, the TWRP 3.4.0-0 be installed. So, where can I uncheck the option. Or how I can install TWRP with xyz's instruction.

Brief description is okay, let me know the right way to install TWRP. At least four people would be resqued.

Thank you.
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
That's not how you do it right . You will need to install the image through recovery. The recovery will patch the recovery partition.
[Fire HD 8 and HD 10 Original Android Development] Reynald0:
Not much we can do, since we can only make some inferences about what changed, only devs really know what happened and how can fix this bug in twrp and if possible resolve, we as user can only hope they want believe in our good faith that the bug exist.
[Fire HD 8 and HD 10 Original Android Development] jumstec:
I did not have this problem with rom when bluetooth did not work.

I do not know if this came from a different version of rom.

It might be a good idea to look again and compare.
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
What kind of problems are you having?
[Fire HD 8 and HD 10 Original Android Development] jumstec:
The version without bluetooth (first version, heavy animation) started twrp fine, so I think something changed in the next version (dated 12/30) that made it not start.
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
Well from my testing, the Bluetooth works with Wifi on and if doesn't tend to drop.
[Fire HD 8 and HD 10 Original Android Development] jumstec:
I'm afraid you're giving me the wrong impression.

regarding the issue of twrp getting stuck on the logo.

The thing is that twrp worked fine in the older version on 12/28 (I believe this is the date) where bluetooth could not be activated.

However, in lineage 20, which was updated on 12/31, twrp would not start.

The same is true on 1/1.

So I'm assuming that some change was made in this update and twrp no longer started.
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
ohh did you mean that the twrp got stuck on the logo?

i forgot a commit that i need to merge in . sorry
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
for now do this

adb shell
$ cp /data/system/storage.xml /data/system/storage.xml.old

while youre in the os and then try to boot to recovery
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
I added the new release , The OP has the link updated as well . https://github.com/mt8163/android_d...k/lineage-20.0-20230104-UNOFFICIAL-karnak.zip
[Fire HD 8 and HD 10 Original Android Development] Reynald0:
karnak:/ $ cp /data/system/storage.xml /data/system/storage.xml.old

Permission denied

We need a root shell, that is only available from the recovery, anyway doing that from the recovery doesn't change anything.
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
you can do that from twrp when its still on the splash screen. I encountered this issue before. Heres what i did , I waited for the twrp to be at the splash screen, then do adb shell , and then do the command i mentioned above, then try to boot to recovery.
[Fire HD 8 and HD 10 Original Android Development] Reynald0:
openSUSE Paste

paste.opensuse.org
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
Whats this paste for?
[Fire HD 8 and HD 10 Original Android Development] Reynald0:
TWRP crash counter increasing, not decreasing. Every time the screen flicker, it's 1 crash.
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
Okay I see that, but did you do the stuff I mentioned above?
[Fire HD 8 and HD 10 Original Android Development] Reynald0:
Yes I did it from root shell in recovery, but nothing changed.

Also one another important thing, is that the rom cannot be resetted from the LineageOS options.

Not sure if can help a logcat:

openSUSE Paste

paste.opensuse.org
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
Did you reboot to recovery after that? Like using force shutdown and then after that you would need to boot to recovery. After removing the storage.xml file .
[Fire HD 8 and HD 10 Original Android Development] Reynald0:
Yeah I tried, let's hear also other users if they try fix, maybe I am doing it wrong.
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
Sorry, I miswrote the steps , Dont copy the storage file, try moving it instead

- Boot TO RECOVERY
- Do adb Shell
- type in mv /data/system/storage.xml /data/system/storage.xml.old
- then press and hold the power button for 10-15 seconds
- do the key combo to boot into recovery
- the screen will show up now
[Fire HD 8 and HD 10 Original Android Development] Reynald0:
Ok that fixed it
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
Can you try to see if the BT Address is generated? It's in Settings > About Tablet.
[Fire HD 8 and HD 10 Original Android Development] Reynald0:
It says it is not available. Wait, I had to activate Bluetooth, now yes.
[Fire HD 8 and HD 10 Original Android Development] Korin67:
Today is a very great day. This is what I am waiting for. All solved. Thank you.
[Fire HD 8 and HD 10 Original Android Development] jumstec:
It worked. (What ended up causing this...)

Is this something I need every time I start twrp?

Also do I need to do it again after flashing a new lineage?
[Fire HD 8 and HD 10 Original Android Development] Reynald0:
He fixed in last rom, only you need if you were in the rom affected by bug like me and others.
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
- Android 12 now writes XML files in binary format by default. This can cause incompatibility with TWRP which can hang when attempting to read XML files e.g. /data/system/storage.xml

- This commit sets the persist.sys.binary_xml property to false so that XML files are written in text format

karnak: property: Don't write binary XML files · mt8163/android_device_amazon_karnak@54456b3

- Android 12 now writes XML files in binary format by default. This can cause incompatibility with TWRP which can hang when attempting to read XML files e.g. /data/system/storage.xml - This commit ...

github.com
[Fire HD 8 and HD 10 Original Android Development] jumstec:
Thanks for the clarification.
[Fire HD 8 and HD 10 Original Android Development] jumstec:
Can I overwrite without wipe?
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
What do you mean by overwrite? Yes you can apply the update without wiping .
[Fire HD 8 and HD 10 Original Android Development] Korin67:
I think this report was the key to solve TWRP lock issue. New people will not install this problematic version. I want to say thanks to all who participated to solve the issue.
[Fire HD 8 and HD 10 Original Android Development] iloyski:
my twrp is also stack. can someone explain the Do adb shell. I'm noob.
[Fire HD 8 and HD 10 Original Android Development] jumstec:
1. Start twrp. There should be a boot loop happening, but that is not the problem.

2. Run "adb shell" as is. The left side should show "karnak". This is the code to start the terminal shell.

Next, type "mv /data/system/storage.xml /data/system/storage.xml.old".

You can use shift+ctrl+v to paste.(linux) However, nothing will be displayed when you run it. This is just adding storage.xml".old" to the name.

4. Just shut down.

5. Start twrp again.

It should start up normally by doing this.
[Fire HD 8 and HD 10 Original Android Development] xWolf13:
Great update! By the way, it's 2023 now, not 2022 haha. Was curious if anyone is also experiencing a little screen flickering when watching YouTube videos? That's where the device slows down the most, and it does make sense with only 1.5gb of RAM. Any possibility in overclocking it?
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
I think it's because the CABC is controlling it via system properties.

# CABC
on property:vendor.hwc.video_mode=1
write /sys/devices/platform/soc/soc:mtkfb@0/backlight_mode "mov"

on property:vendor.hwc.video_mode=0
write /sys/devices/platform/soc/soc:mtkfb@0/backlight_mode "off"
[Fire HD 8 and HD 10 Original Android Development] iloyski:
thanks . Although im not sure if i did it right or it's just luckily working again.
[Fire HD 8 and HD 10 Original Android Development] iloyski:
This rom has a very nice video playback . Can even stream twitch at 720p60fps w/o stuttering unlike all previous rom.
[Fire HD 8 and HD 10 Original Android Development] Reynald0:
Use Jelly or Privacy Browser for video playback very good, do not use Bromite or Chromium for video playback.

openSUSE Paste

paste.opensuse.org

Personally tested also Privacy Browser playing videos correctly: https://f-droid.org/packages/com.stoutner.privacybrowser.standard/
[Fire HD 8 and HD 10 Original Android Development] captainhase:
My son is using the tablet for school and needs YouTube app working. Amazon prime video, Netflix and Disney+ would be nice, too. Now it's on lineageos 16 rom and everything is working fine so far but I would rather switch to los 20 because of the newer OS and security patch. Is it stable enough and is everything working so far?
[Fire HD 8 and HD 10 Original Android Development] Korin67:
Magisk successfully installed?

I tried for the latest version (20230104), Magisk-v20.4.zip and Magisk-v24.2.zip.

For 20.4, TWRP says it is successfully installed but seems does not work. For 24.2, TWRP shows install error.

Sequence is:

ROM, BitGApps-arm, then boot to System. Go back to TWRP, tried to install Magisk.

If you are successful, let me know the Magisk version and install sequence.
[Fire HD 8 and HD 10 Original Android Development] iloyski:
i use 22.1.But i had to turn it back off and on coz it was unresponsive after i flashed.
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
My magisk was successfully installed. It's 25.2, I flashed it after I installed the Gapps.
[Fire HD 8 and HD 10 Original Android Development] Korin67:
With apk or zip? Did you install from TWRP?

When I tried 25.2.apk, I could not install magisk because "Let's go" option did not turn on.
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
Rename the apk file to zip . And then install it through twrp
[Fire HD 8 and HD 10 Original Android Development] Korin67:
I did not know that technique. Yes, successful and it works. Thank you.
[Fire HD 8 and HD 10 Original Android Development] jumstec:
I remember it saying and writing that nothing should be installed in magisk except for modules

Therefore, xposed cannot be installed with zygisk in magisk.

As an alternative, do you install with TWRP?

I also read that the actual bootloader is locked tightly, so I don't see how it could be done other than with TWRP.

I can't say for sure.
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
What are you talking about? Magisk modules can be installed securely within the application itself. The only caveat, in the case of Amazon devices, is that you should NEVER upgrade using the Magisk application since that would overwrite the exploit and would brick your device.​
[Fire HD 8 and HD 10 Original Android Development] jumstec:
Sorry for my bad English.

I was just curious because you wrote that it depends on the module.
[Fire HD 8 and HD 10 Original Android Development] Quinoa_:
Thank you so much for developing karnak Android 13.

Everything works fine in lineage-20.0-20230104 version.

The UI has some intermittent sluggish, but I think there is no problem with use.

If there is a problem while using it, I will upload logcat.
[Fire HD 8 and HD 10 Original Android Development] jumstec:
Please lend your wisdom.

When I tried to format my data in twrp, I got the following error

Updating partition details...
...done
formatting data using mke2fs...
mke2fs -t ext4-b 4096 /deb/block/mmcblk0p16 6627067
process ended with ERROR: 1
Unable to wipe data.
Unable to format to remove encryption.

I had no choice but to use WIPE to see what happened.

The reason why this happened is because when I installed the module after rooting, the app that automatically installs the module installed it with magisk (probably).

Backup is important
[Fire HD 8 and HD 10 Original Android Development] captainhase:
I'm getting this error:

This package is for arm but your device is arm64!

I used the gapps from the first post. Karnak is an arm device as far as I know. Any suggestions?
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
I nodded the package script to not to detect if it's arm64. There is the arch checking in the updater-binary. The link I have for the Gapps is in the forums
[Fire HD 8 and HD 10 Original Android Development] danny19901:
Im curious and i know it's unrelated but i have a Fire HD 8 12th gen is it possible to root at all? hope someone can help as the whole fire hd threads are all over no set gens section.
[Fire HD 8 and HD 10 Original Android Development] Kaijones23:
No it's not rootable at all since they disabled bootrom
[Fire HD 8 and HD 10 Original Android Development] captainhase:
I was able to get this working by:

- installing the newer twrp mentioned in post #24

- Following the instructions from the op, wiping first and installing the rom

- installing gapps linked in post #15

Thank you for your work!

Edit:

I have some difficulties setting up a second googleaccount. My son's privat account is administrated by me via family link. The second one is a google schoolaccount for using classroom etc.. The setup process went well but after 5-10 minutes it is deleted. The notification says (translated from german):

Account was deleted because another family link managed account is already signed in.

Perhaps there are some android go adjustments to this rom that prevent this from functioning well?

Also Disney+ would not play videos.