[ROM][unlocked][karnak] Lineage-20.0 [3 January 2023]

Search This thread
By:
Advanced…
M

Magnoacd

Member
Jan 14, 2020
14
0
hello. The rom is working very well for me, but it doesn't work with hbo max, it stays in black screen and background sound. I don't know if I'm the only one that happens. Thanks
 
M

masterpost2004

Member
May 30, 2019
23
1
Is there any solution for "failed critical init step 4" error when rooting with mtk-su?

or a way to downgrade maybe?

I am trying to root fire HD8 2018 FireOS 6.3.1.4 in order to install LineageOS 20
 
M

musicmanjp6

Member
Feb 3, 2011
26
8
masterpost2004 said:
Is there any solution for "failed critical init step 4" error when rooting with mtk-su?

or a way to downgrade maybe?

I am trying to root fire HD8 2018 FireOS 6.3.1.4 in order to install LineageOS 20
Click to expand...
Click to collapse
You are going to need to follow this guide (which includes downgrading to 6.3.0.0) to prep for installing a ROM:

forum.xda-developers.com

Fire HD 8 (2018 ONLY) unbrick, downgrade, unlock & root

Changelog: v2 - Fixed the issue with the screen Make sure to read this guide completely before starting. It requires you to open the tablet, however you don't need to solder or use any advanced tools. This is only for Fire HD 8, 8th generation...
forum.xda-developers.com forum.xda-developers.com
 
M

masterpost2004

Member
May 30, 2019
23
1
musicmanjp6 said:
You are going to need to follow this guide (which includes downgrading to 6.3.0.0) to prep for installing a ROM:

forum.xda-developers.com

Fire HD 8 (2018 ONLY) unbrick, downgrade, unlock & root

Changelog: v2 - Fixed the issue with the screen Make sure to read this guide completely before starting. It requires you to open the tablet, however you don't need to solder or use any advanced tools. This is only for Fire HD 8, 8th generation...
forum.xda-developers.com forum.xda-developers.com
Click to expand...
Click to collapse

Thanks for your reply. I already tried it but I was unable to get into the recovery after running "./fastboot-step.sh

The tablet gets stuck at Amazon logo and indicating "Recovery" in the lower left corner and nothing happens after that.

Anything else I can do?
 
jumstec

jumstec

Senior Member
Dec 10, 2022
62
16
Amazon Fire HD 8 and HD 10
Xiaomi Pad 5 Pro
masterpost2004 said:
Thanks for your reply. I already tried it but I was unable to get into the recovery after running "./fastboot-step.sh

The tablet gets stuck at Amazon logo and indicating "Recovery" in the lower left corner and nothing happens after that.

Anything else I can do?
Click to expand...
Click to collapse
You may have already done this, but did you turn the screen off and on once?

Have you tried amonet-3?
forum.xda-developers.com

[UNLOCK][ROOT][TWRP][UNBRICK] Fire HD 8 2018 (karnak) amonet-3

Read this whole guide before starting. This is for the 8th gen Fire HD8 (karnak). Current version: amonet-karnak-v3.0.1.zip This is based on xyz`s original work, but adds some features such as reboot to hacked BL. It also intends to simplify...
forum.xda-developers.com forum.xda-developers.com

Also, did you send the data correctly?
It should not fail 99% of the time, but I'm not surprised that it still may not start!

Finally, the text on amonet-3 says
k4y0z said:
NOTE: If you are on a firmware newer than 6.3.0.1, a downgrade is necessary, this requires bricking the device temporarily. (The screen won't come on at all)


WARNING: There have been numerous reports that would indicate a hardware-change that doesn't allow access to the bootrom.
When bricking these devices there is currently no known way to unbrick.
This makes the hardware-method currently the safest option.
Click to expand...
Click to collapse
I know this is old,
k4y0z said:
Unbricking / Unlocking with Firmware 6.3.1.2+

If Recovery OR FireOS are still accessible (or your firmware is below 6.3.1.2) there are other means of recovery, don't continue.

If your device shows one of the following symptoms:
  1. It doesn't show any life (screen stays dark)
  2. You see the white amazon logo, but cannot access Recovery or FireOS.

If you have a Type 1 brick, you may not have to open the device, if your device comes up in bootrom-mode (See Checking USB connection below).
  1. Make sure the device is powered off, by holding the power-button for 20+ seconds
  2. Start bootrom-step.sh
  3. Plug in USB

In all other cases you will have to open the device.

Make sure ModemManager is disabled or uninstalled:
Code: 
sudo systemctl stop ModemManager
sudo systemctl disable ModemManager


NOTE: If you have issues running the scripts, you might have to run them using sudo.
Also try using different USB-ports (preferably USB-2.0-ports)

Open the device and short the pin marked in the attached photo to ground while plugging in.
1. Extract the attached zip-file "amonet-karnak-v3.0.zip" and open a terminal in that directory.

2. start the script:
Code: 
sudo ./bootrom-step.sh

It should now say Waiting for bootrom.

3. Short the device according to the attached photo and plug it in.

4. When the script asks you to remove the short, remove the short and press enter.

5. Wait for the script to finish.
If it stalls at some point, stop it and restart the process from step 2.

6. Your device should now reboot into unlocked fastboot state.

7. Run
Code: 
sudo ./fastboot-step.sh

8. Wait for the device to reboot into TWRP.

9. Use TWRP to flash custom ROM, Magisk or SuperSU

Checking USB connection
In lsusb the boot-rom shows up as:
Code: 
Bus 002 Device 013: ID [b]0e8d:0003[/b] MediaTek Inc. MT6227 phone

If it shows up as:
Code: 
Bus 002 Device 014: ID [b]0e8d:2000[/b] MediaTek Inc. MT65xx Preloader
instead, you are in preloader-mode, try again.

dmesg lists the correct device as:
Code: 
[ 6383.962057] usb 2-2: New USB device found, idVendor=[b]0e8d[/b], idProduct=[b]0003[/b], bcdDevice= 1.00
Click to expand...
Click to collapse
I wish you well.
 
M

masterpost2004

Member
May 30, 2019
23
1
Guys so sorry to bother you again.

I've notices that the fireOS version is vNext !!! is it possible to unlock it and install twrp?
 
@Bill_Dollar

@Bill_Dollar

Senior Member
Dec 19, 2011
101
46
Indianapolis, IN
@Kaijones23 or anyone @here...I tried to build a micro G version via Docker and I need a hand holding as I am on a windows machine and am almost immediately lost. Could anyone help me figure out how to build a Lineage for micog version of this ROM? TIA for any help/advice.
 
jumstec

jumstec

Senior Member
Dec 10, 2022
62
16
Amazon Fire HD 8 and HD 10
Xiaomi Pad 5 Pro
Kovaelin said:
How's the memory usage for everyone? I just noticed I'm using 1.3/1.4 GB on 20.0. Does anyone recall how this compares to the previous ROMs? Thanks.
Click to expand...
Click to collapse
Compared to lineage 16 (when rm was first started) there is an increase of about 100 MB.
When launching an app that uses a lot of memory, try going to developer mode -> running services and stop the app.
 
  • Like
Reactions: Kovaelin
@Bill_Dollar

@Bill_Dollar

Senior Member
Dec 19, 2011
101
46
Indianapolis, IN
jumstec said:
Compared to lineage 16 (when rm was first started) there is an increase of about 100 MB.
When launching an app that uses a lot of memory, try going to developer mode -> running services and stop the app.
Click to expand...
Click to collapse
If we added a high speed SD card and a kernel with Swap, we could increase the RAM tremendously. Im working on it...but am new to full builds
 
  • Like
Reactions: Kovaelin
You must log in or register to reply here.

Similar threads

Kaijones23
  • Poll
[ROM][unlocked][karnak] Lineage-14.1 [25 MAR 2020]
Replies
1K
Views
220K
C
chimpsRcool
Kaijones23
[ROM][unlocked][karnak] Lineage-16.0[04 JUNE 2020]
Replies
582
Views
161K
A
arthurbolotov
K
[UNLOCK][ROOT][TWRP][UNBRICK] Fire HD 8 2018 (karnak) amonet-3
Replies
985
Views
218K
N
nospamboz
ggow
  • Locked
[discontinued][ROM][unlocked][suez] Lineage-14.1 [26 SEP 2019]
Replies
801
Views
202K
engloa
engloa
K
[UNLOCK][ROOT][TWRP][UNBRICK] Fire HD 10 2017 (suez)
Replies
2K
Views
399K
D
dogigniter

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 1
    S
    SergeantFury
    Quick question @Kaijones23: what toolchain and personal settings have you been using to compile kernels for this ROM? I'm getting some very weird "cannot find header" issues that I suspect are configuration differences between what I have and what you used.
    for example:
    Code: 
    In file included from drivers/misc/mediatek/video/mt8163/dispsys/ddp_drv.h:17:0,
                 from drivers/misc/mediatek/video/mt8163/dispsys/ddp_gamma.c:21:
drivers/misc/mediatek/video/mt8163/dispsys/../videox/disp_drv_platform.h:29:21: fatal error: ddp_drv.h: No such file or directory
 #include "ddp_drv.h"
                     ^
compilation terminated.
    My current toolchain, obtained from Google here:

    Code: 
    $ aarch64-linux-android-gcc --version
real-aarch64-linux-android-gcc (GCC) 4.9.x 20150123 (prerelease)
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
    --
    I switched to LineageOS's gcc 4.9 from here; the errors and --version outputs are just about the same. (Actually, if it's possible, it might be easier if you built the kernel and sent it to me to test. The only really important change is setting CONFIG_CFG80211_INTERNAL_REGDB=y in whatever defconfig you're using to configure the kernel.)
    View
    1
    S
    SergeantFury
    Never mind, it worked. I switched to gcc 6.3.1 from here, manually edited a couple of Makefiles, et voilà, it builds. Works and all too. Bit slow on the boot, but I think that's a worthy price to pay for functional 5GHz WiFi.
    Code: 
    [eternitydragon ~] $ adb shell iw reg get
global
country US: DFS-FCC
    (902 - 904 @ 2), (N/A, 30), (N/A)
    (904 - 920 @ 16), (N/A, 30), (N/A)
    (920 - 928 @ 8), (N/A, 30), (N/A)
    (2400 - 2472 @ 40), (N/A, 30), (N/A)
    (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
    (5250 - 5350 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
    (5470 - 5730 @ 160), (N/A, 24), (0 ms), DFS
    (5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW
    (5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN
    (5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN
    (57240 - 71000 @ 2160), (N/A, 40), (N/A)
    Find attached proof that it works (please do not mind the German) and a TWRP-flashable, rooted, and already-Amoneted boot image containing my slightly modified kernel. (The kernel image itself is also here, in case you don't like root. I installed it via Android Image Kitchen, but there are other ways too.)
    @JerseyChewi Thank you for the help in sleuthing out the problem, and I hope this can help you too.
    --
    This exact same kernel is confirmed to boot the updated-to-December-of-'22 Lineage 18.1 as well, if that happens to be your jam.
    Speaking of confirmation, if there are any testers willing to help make sure that this works, please flash the attached boot image, confirm that you can connect to 5GHz networks, and let me know the output of iw reg get below. (Note that this will reveal your country of residence; feel free to skip this if you'd like.)
    View
    1
    JerseyChewi
    JerseyChewi
    Well done and thanks very much! I'll try this out soon.
    View
  • 9
    Kaijones23
    Kaijones23
    7652ffeccaa6bbdcda57289d991b093d.gif
    Disclaimer
    Code: 
    /*
* This ROM will eat your cat
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.

    - This ROM only works with unlocked Fires!

    Rules
    - Please search the thread before asking questions
    - Please report bugs here
    - Report only one issue per bug report
    - When reporting bugs please post a logcat and/or dmesg if possible

    Prerequisites for Installation
    - Unlocked Bootloader
    - TWRP Installed

    Install/Upgrade the ROM
    - Boot to TWRP
    - Go to wipe and wipe: system, data, cache
    - Go to install and flash ROM.zip
    - Flash G-APPS (Optional)
    - Reboot

    Downloads
    LineageOS-20.0 For Karnak
    G-APPS (ARM)

    Source Code
    - Kernel Source: https://github.com/mt8163/android_kernel_amazon_karnak
    - Device Tree: https://github.com/mt8163/android_device_amazon_karnak

    XDA:DevDB Information
    Lineage-20.0 for Fire HD8 (karnak), ROM for the Amazon Fire HD 8 and HD 10

    Contributors
    Kaijones23, Rortiz2, t0x1cSH, k4y0z
    ROM OS Version: Android 13
    ROM Kernel: Linux 4.x

    Version Information
    Status:     Testing
    Current Beta Version: 1.2
    Beta Release Date: 2022-12-25

    Created 2022-12-25
    Last Updated 2023-1-1
    View
    6
    Kaijones23
    Kaijones23
    TODO:
    - Fix Live-display Flicker
    - [DONE] Fix Sluggish boot animation.
    - [Almost Done] Fix Interface being sluggish
    - [DONE] Fix Bluetooth
    - [DONE] Fix Camera Disconnected when camera is recording
    - [DONE] Fix Video Playback


    Please post issues here or on GitHub with the logcat snippet too so we can further troubleshoot and replicate the issue .
    View
    5
    Kaijones23
    Kaijones23
    Changelog:
    [1/03/22]
    • Fixed BT Mac Address , BTMAC was disabled, I was able to remove the disabled flag and the bluetooth hal was able to pickup the [persist.service.bdroid.bdaddr]
    • Fixes the issue with the storage.xml , Twrp would get stuck.

    [1/02/22]
    • Fixed Codecs Thanks To @bengris32 and @R0rt1z2 .
    • Fixed Headphones ( Still Work in Progress)

    [12/29/22]
    • Fixed Bluetooth Issues​
    • Enabled LMK and UKSM In the Kernel​
    • Inherit several Android Go configurations​
    • Set default the Bluetooth class of device​
    • Added new vendors for Bluetooth config migration​
    • Align ASHA prop with Bluetooth Properties​
    • Enable Bluetooth profiles with system_ext.prop​
    • Update LE Audio profile properties to match spec and implementation​
    • Disable LE audio related profiles​
    • Enable Audio Support for Hearing Aids central support​
    • Use the ?= operator so BT properties can be overridden​
    • Move BT profiles props to vendor​
    • Don't write binary XML files​
    • props: Bump fingerprint to latest cheetah build​
    • Refactor and organize {system,vendor} properties​
    • Get rid of vndk-sp​
    • Disable SF configstore * ship disable_configstore because we have API level 29​
    • props: Checkout SurfaceFlinger properties from Fire OS 8​
    • props: Use phase offsets as duration​
    • dynamically allocate zram​
    • props: Configure ZRAM-writeback job​
    • Adjust zram write back policy​
    • Switch to SkiaGL as HWUI renderer​
    View
    4
    P
    phigan
    Like someone else pointed out, the tablet is definitely quieter with this ROM. Not horribly, though.

    While video streaming does work, after about 20-25 minutes of it, it stops for some reason. I thought someone else had reported the same problem, but I've been going through a lot of threads recently and it may have been a different one.

    At first I tried playing an hour-long video with NewPipe, but was watching it with the audio turned all the way down. The image froze maybe ~24 minutes into the video.
    I tried again with NewPipe and a different 1hr+ vid, this time with the audio up, and the image froze again around the 24 minute mark, but the audio kept going. I tried to move back or forward to see if it would fix it, but then it would no longer load at all.
    Then I tried playing the same video in a browser (Privacy Browser, as earlier suggested). I was able to skip ahead to where it had left off in NewPipe, but then another 25 or so minutes later the video stopped and there was a circle spinning infinitely.
    Saving the videos locally with NewPipe and then playing then with VLC worked fine.

    These issues definitely won't make me give up on this ROM or anything, but I thought I'd report my experience thus far. I'll keep trying things.

    Thanks for the love on the Karnak.
    View
    3
    Kaijones23
    Kaijones23
    Also still searching for the jobs, I’m into IT field like I have Helpdesk experience but transitioning to systems administrator and since I’ve been applying a lot daily, I haven’t heard from the employers and it makes me almost give up hope on it.
    View

New posts