yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Kaijones23:
fire hd 8 2018 boots into fast-boot after installing custom ROM.

[MENTION=7104332]k4y0z[/MENTION], well I see some progress in this code after I remove this line,

/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/system /system ext4 ro wait,verify

to

/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/system /system ext4 ro wait

it boots into fastboot after installing custom ROM.

the files I have attached is:

ramdisk.zip rootdir from my device tree

boot.zip boot.img from lineage os before it was compiled.

there is something is preventing the ROM from booting up because I won't be able to get the logs.

if you want to see the fire HD 8's extracted boot image, it is posted on my GitHub here.

the problem I think it is an issue with init files.

thank you for your help. I know you dont have a fire hd 8 and i want this thing to boot into lineage.
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] k4y0z:
Yes, you definitely want to disable dm-verity.

If it (re)boots into fastboot, you are probably missing some kernel-patches/features
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Kaijones23:
Ok so I have been using prebuilt kernel and then well if I use the original kernel amazon uses, I can’t boot it up. It just bootloops. What patches do I need to add from the kernel tree l, I can’t build a rom Amazon’s script because it has issues. I’ll try once more with Amazon’s build script. How can I use it properly so it can successfully compile
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Kaijones23:
Hello I was able to compile the Amazon’s fire hd kernel with the script that’s included with the source. I don’t know what modifications to make it support android pie
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Legitsu:
you could start with cherry-picking commits to get it booting and then go from there

mostly you are gonna be building up from scratch and cherry picking commits from other mtk devices

its not impossible I know [MENTION=7104332]k4y0z[/MENTION]

has los16 booting on suez but I am pretty sure it doesn't do much else yet
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Kaijones23:
[MENTION=7104332]k4y0z[/MENTION] well since I set to SELinux to permissive, it has logcat and I proveded it in this attachment. when I build the kernel with amazons script and added some patches to my kernel from your tree, it doesn't boot up like it shows at Amazon logo and shuts down.

how would you be able to get the built kernel to boot up?
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] k4y0z:
That's not entirely accurate, I have WiFi working and audio partially :p

But yes, getting it to boot is something entirely different from getting it to actually be usable.

I don't know why your kernel doesn't boot, but the log shows you are missing some stuff as I have said before.

You probably need ambient capabilities and hwbinder patches.
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Legitsu:
ahh I was just going by why I saw in your git

nice nice
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Kaijones23:
Since I added ambient capabilities patches, and made it into image.gz-dtb, it doesn’t boot. What it does it shuts down because it doesn’t extract the image.gz-dtb. How I got it working is that i pulled an zimage from fire os boot img but all it has adb and errors same as up there. . and I’m looking for ways to convert Image file into zimage. Thanks!
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Kaijones23:
[MENTION=7104332]k4y0z[/MENTION] I have to take a break from pie for a little and I'm working on CM 14.1 what's happening in logcat is that the keystore is not working.

2019-04-29 12:28:07.536 553-553/? I/keystore: Found keymaster1 module Keymaster MTEE based HAL, version 100
2019-04-29 12:28:07.536 553-553/? I/SoftKeymaster: system/keymaster/soft_keymaster_device.cpp, Line 131: Creating device
2019-04-29 12:28:07.536 553-553/? D/SoftKeymaster: system/keymaster/soft_keymaster_device.cpp, Line 132: Device address: 0xf6a8d000
2019-04-29 12:28:07.536 553-553/? I/KM_UREE: open keymaster device
2019-04-29 12:28:07.536 553-553/? I/KM_UREE: open keymaster device.. done
2019-04-29 12:28:07.536 553-553/? D/keystore: Wrapping keymaster1 module Keymaster MTEE based HAL with SofKeymasterDevice
2019-04-29 12:28:07.536 553-553/? D/SoftKeymaster: system/keymaster/soft_keymaster_device.cpp, Line 178: Reinitializing SoftKeymasterDevice to use HW keymaster1
2019-04-29 12:28:07.536 553-553/? E/uree.so: UREE_OpenFd open fd fail, err = Permission denied
2019-04-29 12:28:07.537 553-553/? E/uree.so: uid=1017, gid=1017
2019-04-29 12:28:07.537 553-553/? E/uree.so: groups={1026 3009}
2019-04-29 12:28:07.537 553-553/? E/uree.so: cmdline=/system/bin/keystore
2019-04-29 12:28:07.537 553-553/? E/uree.so: permission granted for UID 1000(SYSTEM), GID 1026(DRMRPC)
2019-04-29 12:28:07.537 553-553/? E/KM_UREE: Failed to create keymaster session, ret=-65536
2019-04-29 12:28:07.537 553-553/? E/KM_UREE: get_supported_digests failed with -49
2019-04-29 12:28:07.537 553-553/? E/SoftKeymaster: system/keymaster/soft_keymaster_device.cpp, Line 93: Error -49 getting supported digests from keymaster1 device
2019-04-29 12:28:07.537 553-553/? E/keystore: Got error -49 from SetHardwareDevice
2019-04-29 12:28:07.537 553-553/? E/keystore: keystore keymaster could not be initialized; exiting
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Kaijones23:
also, I'm having issues with this too

issive=1

04-29 20:02:24.456 1978 1978 D NvramDrv: NvramDrv check nvram demon

04-29 20:02:24.456 1978 1978 E NvramDrv: NvramDrvMError: 623: error demomn 10014 ms, timeout

04-29 20:02:24.456 1978 1978 D NVRAM : length of g_NVRAM_BACKUP_DEVICE=59

04-29 20:02:24.456 1978 1978 D NVRAM : failed to get entry for /nvdata

04-29 20:02:24.456 1978 1978 D NVRAM : failed to get nvdata path /nvdata

04-29 20:02:24.456 1978 1978 D NVRAM : nvram_layout_callback will run!!!

04-29 20:02:24.456 1978 1978 D NVRAM : nvram_platform_log_block: 2

04-29 20:02:24.456 1978 1978 D NVRAM : nvram_platform_resv_block: 2

04-29 20:02:24.456 1978 1978 D NVRAM : nvram_platform_DM_block: 1

04-29 20:02:24.456 1978 1978 D NVRAM : nvram_platform_layout_version: 0

04-29 20:02:24.456 1978 1978 D NVRAM : nvram_platform_header_offset: 0

04-29 20:02:24.456 1978 1978 D NVRAM : g_i4CFG_File_Count: 49

04-29 20:02:24.456 1978 1978 D NVRAM : NVM_Init Max Lid: 71

04-29 20:02:24.456 1978 1978 D NVRAM : [NVRAM]: info nvram_gpt_flag =1

04-29 20:02:24.456 1978 1978 D NVRAM : [NVRAM]: info NVRAM Init Completed!

04-29 20:02:24.456 1978 1978 D NVRAM : NVM_GetFileDesc: Open /data/nvram/media/CAMERA_VERSION,LID:22

04-29 20:02:24.457 1978 1978 D NVRAM : NVM_CmpFileVerNo 22

04-29 20:02:24.457 1978 1978 D NVRAM : NVM_GenerateFileVer: CPY_File_To_NVM=1 ++

04-29 20:02:24.457 1978 1978 D NVRAM : iCustomBeginLID = 49

04-29 20:02:24.457 1978 1978 D NVRAM : Create/Open the file of /data/nvram/APCFG/APRDCL/FILE_VER

04-29 20:02:24.457 1978 1978 D NVRAM : Create the dir path of /data/nvram/APCFG/APRDCL/FILE_VER

04-29 20:02:24.457 1978 1978 D NVRAM : mkdir error! Permission denied

04-29 20:02:24.457 1978 1978 D NVRAM : Fail to open /data/nvram/APCFG/APRDCL/FILE_VER

04-29 20:02:24.457 1978 1978 D NVRAM : GenerateFileVer Fail!

04-29 20:02:24.457 1978 1978 D NVRAM : NVM_ReadFileVerInfo NVM_CheckFileInfo Fail: Reset!!!

04-29 20:02:24.457 1978 1978 D NVRAM : NVM_ResetFileToDefault : 22 ++

04-29 20:02:24.457 1978 1978 D NVRAM : iCustomBeginLID = 49

04-29 20:02:24.457 1978 1978 D NVRAM : NVM_GenerateFileVer: CPY_File_To_NVM=1 ++

04-29 20:02:24.457 1978 1978 D NVRAM : iCustomBeginLID = 49

04-29 20:02:24.457 1978 1978 D NVRAM : Create/Open the file of /data/nvram/APCFG/APRDCL/FILE_VER

04-29 20:02:24.457 1978 1978 D NVRAM : Create the dir path of /data/nvram/APCFG/APRDCL/FILE_VER

04-29 20:02:24.457 1978 1978 D NVRAM : mkdir error! Permission denied

04-29 20:02:24.457 1978 1978 D NVRAM : Fail to open /data/nvram/APCFG/APRDCL/FILE_VER

04-29 20:02:24.457 1978 1978 D NVRAM : GenerateFileVer Fail!

04-29 20:02:24.457 1978 1978 E NvramDrv: NvramDrvMError: 633: readNvramData(): create NVRAM file fail

04-29 20:02:24.457 1978 1978 E NvramDrv: NvramDrvMError: 229: readNvramData() error: ==> readDefaultData()

04-29 20:02:24.457 1978 1978 D nvbuf_util.cpp: nvbuf_util.cpp readVerNvramNoLock error ln=182

04-29 20:02:24.457 1978 1978 D nvbuf_util.cpp: nvbuf_util.cpp readRamVersion ln=600 ver=0 err=-2147483645
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Rortiz2:
[MENTION=7104332]k4y0z[/MENTION]

[MENTION=9605864]Kaijones23[/MENTION] got it!
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] k4y0z:
Good Job! :good:
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Kaijones23:
What’s not working is wifi and audio and camera
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] DB126:
Yep - those would be the big three along with BT and panel rotation (although the latter seems confined to older platforms). Great start though!
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Kaijones23:
Also Bluetooth too. What libraries do I need for that?
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] DB126:
Suggest reaching out to [MENTION=5749760]ggow[/MENTION] who has extensive experience spinning up custom ROMs for Amazon devices spanning multiple generations. Likely some platform commonality.
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Legitsu:
[MENTION=7104332]k4y0z[/MENTION] said he had wif working on suez I am not sure if its the same driver for karnak
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Rortiz2:
Wifi doesn't work, audio too and camera too.

Any ideas.
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] DB126:
Hardware interfaces that must be reconciled via kernel. Typically the most challenging aspect of getting custom ROMs to work on Amazon devices due to non-standard (and largely undocumented) binaries. Getting it to boot is the easy part.
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Kaijones23:
[MENTION=7104332]k4y0z[/MENTION] [MENTION=8165603]DragonFire1024[/MENTION] [MENTION=5749760]ggow[/MENTION] [MENTION=5488402]Davey126[/MENTION]

when i was trying to fix the audio, the adio library has issues like

HAL : load: module=/vendor/lib/hw/audio.primary.mt8163.so
05-02 21:07:53.869 311 311 E HAL : dlopen failed: cannot locate symbol "__metrics_log_print" referenced by "/system/lib/libasp.so"...
05-02 21:07:53.869 311 311 E AudioFlinger: int android::load_audio_interface(const char *, audio_hw_device_t **) couldn't load audio hw module audio.primary (Invalid argument)
05-02 21:07:53.869 311 311 E AudioFlinger: loadHwModule() error -22 loading module primary

for a full log here you go.

and whats the issie is that camera doesnt stil work after i addded librairies to it.

davey, the problem is that i cant get the custom kernel to boot up.

heres my tree.

https://github.com/488315/android_device_amazon_karnak/tree/cm-14.1
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] DB126:
Seek out this resource. No one know more about the idiosyncrasies of Amazon devices when it comes to custom kernels/roms.
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] k4y0z:
You will either need to find the library that defines the missing symbol (__metrics_log_print) or you will have to write a shim for it.
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] obvious:
Sorry for the OT but would it be possible for you to help with the bootloader unlock for HD 8 2017? I'm not sure it's within your area of expertise. We're pretty much stuck without a way to unlock. Sure we've got root but as it stands no chance of custom ROMs.
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] ggow:
I haven't got an HD 8 2017. When I have got through the current round of amazon things then I'll see if I can borrow one.
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] obvious:
Wow, thanks
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Kaijones23:
Do you want me to send you the link of my rom or you’re going to build it?
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Kaijones23:
Heres the ROM zip file for if anyone wants tot try it

[MENTION=7104332]k4y0z[/MENTION] [MENTION=8165603]DragonFire1024[/MENTION] [MENTION=5749760]ggow[/MENTION]

https://github.com/488315/android_device_amazon_karnak/releases/tag/1.0

Direct Download

https://github.com/488315/android_d...oad/1.0/lineage-14.1-20190429-UNOFFICIAL-.zip
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] ggow:
Just saw you message, thanks for the link :good:
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] DragonFire1024:
Funny you should just mention the audio. I made a kernel bill before I left the house for work. I'm all the build that I've tried so far it was the only one that I had problems with that booted. And the issues were with the audio. so I am going to assume that it doesn't have to do with the libraries but probably the drivers and other files. I'll have to look at my previous build and see what I missed this time.

On another note I removed the RSA certificates from vendor data, while in recovery, then wiped cache and dalvik and rebooted to a bootloop at the boot animation. So I reboot into recovery and re-added the files. Then reboot and everything is fine. I just found it strange. So if those certificates weren't of any importance it would not have caused the bootloop. So I again wonder what they are used for. So it's not a dead end it could explain some of the difficulties.
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] DragonFire1024:
Do in a shell, you need to be root for some of it, and run netcfg. Those are your nodes, p2p, wlan0 (if there is one) also check system/etc/wifi and data/wifi make sure wpa and p2p confs are there. If in netcfg there is no wlan0, specify one of the open nodes and build prop it. On the HD 10 we have a deodex issue where there's no DHCP. Though if you ask me I think it has to do with the settings app and something Amazon has set in an app somewhere.
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] DragonFire1024:
Wpa supplicant isn't a lib, it's a conf. There's a few in etc and in data. There are also settings in the framework.
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Rortiz2:
When he said that wpa_supplicant its a lib? :/
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] DragonFire1024:
Wpa_supplicant.conf in /system/etc/wifi, /data/misc and it's also a bin... /System/bin/wpa_supplicant. You can also set the scan interval in the build prop.
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Rortiz2:
I mean that Kaijones not said that it is a lib. I know it's also a bin.
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] k4y0z:
wpa_supplicant is a program, and it usually also includes a private lib.

You will likely need the files in /system/etc/firmware and a few services (wmt_loader, wmt_launcher/6620_launcher).

And also the private lib for wpa_supplicant https://github.com/chaosmaster/android_device_amazon_suez/tree/lineage-16.0/wpa_supplicant_8_lib.

Alternatively you can try and use the prebuilt wpa_supplicant.
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Rortiz2:
Hey!

Thanks for the reply :)

We are already using your private lib and even then the wifi does not work.

In the ROM are all the files in system/bin but there is no way to turn on the wifi.

Always we get:

05-06 10:28:06.938 858 946 E WifiMonitor: killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
05-06 10:28:06.938 858 946 E WifiHW : Failed to open driver state control param (Permission denied)
05-06 10:28:06.938 858 946 E WifiStateMachine: Failed to load driver
05-06 10:28:06.941 858 858 E WifiController: WifiControllerWifi turn on failed

If we use stock libhardwarelegacy.so and libwifi-service the ROM bootlops but look at WIFI logcat:

[B]WifiService: WifiService starting up with Wi-Fi enabled
05-06 10:51:10.399 869 869 D WifiService: setWifiEnabled: true pid=869, uid=1000
05-06 10:51:10.400 869 869 I WifiScanningService: Starting wifiscanner
05-06 10:51:10.400 869 1264 D WifiController: WifiController msg { when=0 what=155656 target=com.android.internal.util.StateMachine$SmHandler } deferred for 499ms[/B]
05-06 10:51:10.915 869 1264 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: WifiService
05-06 10:51:10.915 869 1264 E AndroidRuntime: java.lang.UnsatisfiedLinkError: No implementation found for boolean com.android.server.wifi.WifiNative.setApMode(boolean) (tried Java_com_android_server_wifi_WifiNative_setApMode and Java_com_android_server_wifi_WifiNative_setApMode__Z)
05-06 10:51:10.915 869 1264 E AndroidRuntime: at com.android.server.wifi.WifiNative.setApMode(Native Method)
05-06 10:51:10.915 869 1264 E AndroidRuntime: at com.android.server.wifi.WifiStateMachine.setSupplicantRunning(WifiStateMachine.java:1846)
05-06 10:51:10.915 869 1264 E AndroidRuntime: at com.android.server.wifi.WifiController$StaEnabledState.enter(WifiController.java:632)
05-06 10:51:10.915 869 1264 E AndroidRuntime: at com.android.internal.util.StateMachine$SmHandler.invokeEnterMethods(StateMachine.java:1021)
05-06 10:51:10.915 869 1264 E AndroidRuntime: at com.android.internal.util.StateMachine$SmHandler.performTransitions(StateMachine.java:867)
05-06 10:51:10.915 869 1264 E AndroidRuntime: at com.android.internal.util.StateMachine$SmHandler.handleMessage(StateMachine.java:809)
05-06 10:51:10.915 869 1264 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
05-06 10:51:10.915 869 1264 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
05-06 10:51:10.915 869 1264 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:61)

We can try with the prebuilt wpa_supplicant but do you have any more ideas?

Regards!
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Rortiz2:
[MENTION=7104332]k4y0z[/MENTION] Since its a permission denied error:

E WifiHW : Failed to open driver state control param (Permission denied)

we need to edit any .rc file? Maybe init.connectivity.rc? The Selinux its in permissive so thats not the problem...

BOARD_KERNEL_CMDLINE += androidboot.selinux=permissive

We tried all the possible and still not working. We need your help :(
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] k4y0z:
This has nothing to do with selinux.

You probably have to change this to wifi wifi:

https://github.com/488315/android_device_amazon_karnak/blob/master/rootdir/etc/ueventd.mt8163.rc#L28
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Rortiz2:
Well, I know it had something to do with some .rc.

Thanks, now the error has been solved :fingers-crossed: but now it gives us the following:

05-08 10:07:21.029 861 947 E wifi : Could not read interface wlan0 flags: 19
05-08 10:07:21.029 861 947 E WifiNative-HAL: Could not start hal
05-08 10:07:21.029 861 947 E WifiStateMachine: Failed to start HAL
05-08 10:07:21.047 861 947 D WifiMonitor: startMonitoring(wlan0) with mConnected = false
05-08 10:07:21.051 861 947 E WifiHW : Unable to open connection to supplicant on "@android:wpa_wlan0": No such file or directory

Maybe now its a wpa_supplicant.conf error?

PS: Sorry for bother you...
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Rortiz2:
Well, found the causant:

05-09 08:42:26.240 817 817 I Binder:400_2: type=1400 audit(0.0:134): avc: denied { write } for name="wmtWifi" dev="tmpfs" ino=16078 scontext=u:r:netd:s0 tcontext=u:object_r:device:s0 tclass=file permissive=1
05-09 08:42:26.240 817 817 I Binder:400_2: type=1400 audit(0.0:135): avc: denied { open } for path="/dev/wmtWifi" dev="tmpfs" ino=16078 scontext=u:r:netd:s0 tcontext=u:object_r:device:s0 tclass=file permissive=1

We need to add a sepolicy rule to solve it no?

Regards!
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] k4y0z:
Forget selinux for now, it is set to permissive, these are just audit-messages that tell you what WOULD happen if selinux was enforcing.
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] DB126:
Thank you; more than obvious.
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Kaijones23:
Hey guys, Sorry to bother you, well I need help figuring out to get a Custom kernel to boot. I don't know why but it is not extracting the image-gz-dtb instead of zimage. I have added hwbinder patches, ambient capabilities and Kernel assisted Super User. [MENTION=7104332]k4y0z[/MENTION], Have you got yourself a fire HD 8 yet? if not it's ok, I'm going to try hard to figure it out on my own. I have tried other cmd lines and other things like that. What I think something is not letting the kernel extract. I would appreciate you guys help! I think that the amazons kernel source is missing something or it needs fixes.
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] crash4fun:
I'll gladly send you mine on loan to help further things. There are so many of these tablets just sitting in people's drawers because of how limited the stock firmware is. Just PM me when you are ready to investigate.
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] obvious:
Just a quick note to ask if this is still on your radar? Thanks :)
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] AmznUser444 Dev:
You must be need to wipe the data or factory reset first
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Kaijones23:
[MENTION=4062149]mattgyver[/MENTION] can you please close this thread because this is already solved?
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] mattgyver:
Thread closed per OP request.
[Honor 5X ROMs, Kernels, Recoveries, & Other Develo] Ehsan-Sa:
This is ViperOS

Disclaimer:

We are not responsible for anything that may happen to your phone as a result of installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.

"This is a user friendly thread. All feature requests will be heard and considered. I am not against anything that doesn't stray too far away from the original idea of the ROM! Helping one another is also encouraged! Please be respectful and you will always be treated the same way, we are all here for a good experience."

About:

We are a Brazilian team, ViperOS aims to bring stability and useful features. If you are looking for a stable ROM with true tested features, minimal bugs and no Lineage bloatwares, then this is the place to be.

Features:

Statusbar

QS settings

Clock statusbar settings

Battery style

Carrier label

Network traffic

4G/LTE icon toggle

Rounded corner settings

QS for Reboot/Recovery

Recents

Style recents AOSP and QuickStep

Button clear and Membar for recents AOSP

Lockscreen

Face auto unlock

WheaterClient

Battery info Charging

System

Color engine

theme QS style

Buttons and navbar settings

LED battery Charging

LED notifications colors

Power Menu advanced

Fonts packages

Many other customizations, install and take a look

Download:

MEGA

OpenGApps

Credits & Thanks:

All ViperOS Team

LineageOS team

ResurrectionRemix team

crDroid team

And all other open source Devs/Teams I may have missed!

Other links

Telegram channel

Telegram chat discussion

XDA:DevDB Information

ViperOS Project, ROM for the Honor5x (kiwi)

Contributors

Ehsan-sa

ROM OS Version: 9.x Pie

ROM Kernel: Linux 3.x

Based On: LineageOS

Version Information

Status: Stable

Current Stable Version: 6.3

Created 2019-04-17

Last Updated 2019-04-17