Database Info

HD8 '18 OS 6.3.1.5 (& HD10 '17) Xposed crashloop with WiFi:

HD8 2018 6.3.1.5 (and 6.3.1.4) issues
HD8 2018 OS continues to present never ending issues (seems like a poorly supported product compared to the earlier Fires ...)
I flashed 6.3.1.5 (6.3.1.4) on top of 6.3.1.2 via TWRP (+Magisk/systemless Xposed), and, ended up with a weird WiFi crashloop that took a few tries to understand. Essentially, the moment it connects to a WiFi network, it reboots. If I set WiFi to off, it's stable (have to do it quick before it connects after a reboot!). If I disable Xposed module, it's stable. Neither Xposed 89.3 or 90beta work correctly.
On 6.3.1.2 Xposed worked more or less OK.
I tried to downgrade back to OS 6.3.1.2 or 6.3.0.1, but apparently the settings are not compatible once you load 6.3.1.4 on it. It never reaches the launcher, and keeps sitting at Fire screen. I could not even boot 6.3.1.2 or 6.3.0.1 without Magisk. Doing a factory reset was not in my plan yet. So I had to go to 6.3.1.4 again where it booted fine. I now run 6.3.1.4 with Xposed disabled.
Anybody has 6.3.1.4 with Xposed & WiFi working properly out there? I wonder if this is also a similar issue with Fire 7 2019 (mustang) - @Michajin
HD10 2017 40.6.5.0_user_650601220 issues
Well, what do you know ... I finally took the plunge to do the unlock and install TWRP on my Kingoroot rooted HD10 2017 (thanks @k4y0z !). I backed up all the apps via Titanium Backup, and then backed up the internal sdcard via Total Commander to a zip, which later nicely restores things back with the proper timestamps (yay!). It's very difficult to restore timestamps, but Total Commander with root can do it.
In my optimism, after getting TWRP, I immediately installed the latest FireOS, 40.6.5.0_user_650601220, with Magisk, and Xposed installed into system (xposed-v89-sdk22-arm64.zip). And, just like HD8 2018, the moment I activated Xposed modules, the tablet started rebooting when WiFi was on. If I managed to hit WiFi off button before it did so, it seemed stable. So both HD10 2017 and HD8 2018 appear to have the same Xposed bug in the latest FireOS versions!!! I wonder if it's related to the fix of MTK-SU issue.
I also ran into Google Play & battery drain issues. Tired of several attempts of troubleshooting, I actually ended up backtracking all the way to 40.6.2.6_user_626533320, which is the version I started with. Once Google Play went south after my 1st restore, I could not fix it over multiple tries, and I had to do a Factory reset again and restore apps via Titanium Backup a bit more carefully, starting with the latest versions of Google Play apps without data (rather than just all at once). Now everything appears to be working as before, with TWRP, and the same old FireOS version that I already had
The battery drain issue was an interesting one, apparently, Vanced Youtube helper app, microg_YouTube_Vanced_0.2.6.17455, creates a lot of battery drain via needless Wakelocks, which can be fixed by running the following commands:
Code:
adb shell
su
pm disable com.mgoogle.android.gms/org.microg.gms.people.ContactSyncService
P.S. A week ago I unlocked HD8 2017 (OS version 50.6.3.6_user_636558520), and successfully cloned HD8 2016 to this 2017 via TiBa & Total Commander. That attempt went without a glitch, and that's why I thought I could also do HD10 in no time, but HD10 gave me all kinds of issues.

bibikalka said:
HD8 2018 OS continues to present never ending issues (seems like a poorly supported product compared to the earlier Fires ...)
I flashed 6.3.1.4 on top of 6.3.1.2 via TWRP (+Magisk/systemless Xposed), and, ended up with a weird WiFi crashloop that took a few tries to understand. Essentially, the moment it connects to a WiFi network, it reboots. If I set WiFi to off, it's stable (have to do it quick before it connects after a reboot!). If I disable Xposed module, it's stable. Neither Xposed 89.3 or 90beta work correctly.
On 6.3.1.2 Xposed worked more or less OK.
I tried to downgrade back to OS 6.3.1.2 or 6.3.0.1, but apparently the settings are not compatible once you load 6.3.1.4 on it. It never reaches the launcher, and keeps sitting at Fire screen. I could not even boot 6.3.1.2 or 6.3.0.1 without Magisk. Doing a factory reset was not in my plan yet. So I had to go to 6.3.1.4 again where it booted fine. I now run 6.3.1.4 with Xposed disabled.
Anybody has 6.3.1.4 with Xposed & WiFi working properly out there? I wonder if this is also a similar issue with Fire 7 2019 (mustang) - @Michajin
Click to expand...
Click to collapse
you will have to refresh me where i had on the mustang. I am using los 16.0 on the hd8, dont really have a need for xposed. Seems like i had this on the mustang right after root when on stock? i will look into it and try and refresh myself if you cant point me into the thread...

Michajin said:
you will have to refresh me where i had on the mustang. I am using los 16.0 on the hd8, dont really have a need for xposed. Seems like i had this on the mustang right after root when on stock? i will look into it and try and refresh myself if you cant point me into the thread...
Click to expand...
Click to collapse
It was here :
https://forum.xda-developers.com/showpost.php?p=79841222&postcount=21

bibikalka said:
It was here :
https://forum.xda-developers.com/showpost.php?p=79841222&postcount=21
Click to expand...
Click to collapse
I am trying to remember but it seems i had to flash full xposed from TWRP. I think i had issues with the systemless version from magisk. I didn't know people would chose to run FIRE-OS once anything else was available (no offense) with 14.1 and 16, both being decent... lol

Michajin said:
I am trying to remember but it seems i had to flash full xposed from TWRP. I think i had issues with the systemless version from magisk. I didn't know people would chose to run FIRE-OS once anything else was available (no offense) with 14.1 and 16, both being decent... lol
Click to expand...
Click to collapse
You have a point here regarding LoS I thought I was gaining stability by sticking to FireOS, but this version has been anything but stable!
I need Skype to work - is the camera working in either LoS 14.1 or 16? The issue is that some of these ROMs seem to be in eternal beta, once the low hanging fruit is done, the polish is not applied further.

bibikalka said:
You have a point here regarding LoS I thought I was gaining stability by sticking to FireOS, but this version has been anything but stable!
I need Skype to work - is the camera working in either LoS 14.1 or 16? The issue is that some of these ROMs seem to be in eternal beta, once the low hanging fruit is done, the polish is not applied further.
Click to expand...
Click to collapse
The camera works on both 16.0 and 14.1. But 14.1 is by far more stable at this time. Bluetooth and headphones (plus more- see thread) issues on 16.0. The only issue on 14.1 is the headphone jack doesn't work (but i think someone has found a fix for it but it hasnt been updated in the rom). Backup in TWRP and install 14.1 and give it a shot, i am on 16.0. 14.1 was working really smooth. I have not tested skype on either. 14.1 seemed smoother and less buggy than fireOS right at Beta.

bibikalka said:
You have a point here regarding LoS I thought I was gaining stability by sticking to FireOS, but this version has been anything but stable!
I need Skype to work - is the camera working in either LoS 14.1 or 16? The issue is that some of these ROMs seem to be in eternal beta, once the low hanging fruit is done, the polish is not applied further.
Click to expand...
Click to collapse
Observation regarding custom ROMs is one reason I typically hang with 'stock' and tune to my liking. LOS 14.1 for this device/gen (and a few others) is an exception; worth considering. LOS 16.1 is less refined ATM with no meaningful advantage over 14.1.

bibikalka said:
You have a point here regarding LoS I thought I was gaining stability by sticking to FireOS, but this version has been anything but stable!
I need Skype to work - is the camera working in either LoS 14.1 or 16? The issue is that some of these ROMs seem to be in eternal beta, once the low hanging fruit is done, the polish is not applied further.
Click to expand...
Click to collapse
I needed to have headphones working, so I didn't try LOS 14 until recently. I'm extremely happy with it. It's so much snappier than stock for me, and videos load so much faster, like in Netflix, for example. I'm also using Magisk and Xposed with no issues.

I didn't realize the new build is up with fixes... Going back to 14.1, I think he is working on 17.0 (Kaijones23) 17.0 was updated last night....
https://github.com/mt8163/android_device_amazon_karnak/branches

Noob question - how do you flash lineage-16 or cm-14.1 onto the device? I downloaded the zip files from the link above, but they are way to small to be a complete rom. Is there a different location where I can download the roms?

xantiux said:
Noob question - how do you flash lineage-16 or cm-14.1 onto the device? I downloaded the zip files from the link above, but they are way to small to be a complete rom. Is there a different location where I can download the roms?
Click to expand...
Click to collapse
Have you unlocked the bootloader (prerequisite):
https://forum.xda-developers.com/hd...nlock-fire-hd-8-2018-karnak-amonet-3-t3963496

I have unlocked the bootloader, for which I had to open the tablet up in order to short a pin. I was able to load the FireOS 6.0.0.0 and 6.0.0.1, and was looking if there is a way to load 6.0.1.2 or 6.0.1.4, when I came upon this thread, and saw that it may be possible to load lineage or cm, but I don't know how to get my hands on the ROMs. The downloads from the links above are way too small.

xantiux said:
I have unlocked the bootloader, for which I had to open the tablet up in order to short a pin. I was able to load the FireOS 6.0.0.0 and 6.0.0.1, and was looking if there is a way to load 6.0.1.2 or 6.0.1.4, when I came upon this thread, and saw that it may be possible to load lineage or cm, but I don't know how to get my hands on the ROMs. The downloads from the links above are way too small.
Click to expand...
Click to collapse
This help?
https://forum.xda-developers.com/hd8-hd10/general/lineageos-14-1-fire-hd8-2018-t3936242
https://forum.xda-developers.com/hd8-hd10/orig-development/rom-lineage-16-0-t3981685

This is great, thank you!
Somewhat related question - is it hard to get a zip of fireOS 6.3.1.2, so it can be flashed via TWRP?

xantiux said:
This is great, thank you!
Somewhat related question - is it hard to get a zip of fireOS 6.3.1.2, so it can be flashed via TWRP?
Click to expand...
Click to collapse
Supposedly renaming .bin to .zip allows flashing from twrp. I'd be wary of other partitions such as recovery and aboot which could trigger a bad day.

Headphone fix for LOS 14 has been applied in the latest version of the ROM. If you don't feel like reflashing entire ROM, there is a flashable zip containing only the headphone fix (module). I don't have the links handy but it's all available on this forum.

Updated post #1 and described HD10 '17 Xposed WiFi crashloop as well.

Updated with the same HD8 2018 6.3.1.5 WiFi/Xposed issue.

bibikalka said:
Updated with the same HD8 2018 6.3.1.5 WiFi/Xposed issue.
Click to expand...
Click to collapse
Welcome back!

[DISCONTINUED] LineageOS 17.1

Originally, this was thread was centered on the LineageOS 17 GSI by AndyYan, however, CodeF86 has so very generously made a working GSI for the Moto G6 which you can try out now!
Unlike AndyYan's generic GSI, for this you do NOT need to flash johnaltg1's LineageOS 16 image (if you do, this GSI will NOT boot). It is recommended you use stock Pie firmware. Oreo firmware has not been tested and may result in bugs.
​Download here—Compiled Feb 22nd, w/ working LTE!
See CodyF86's thread post
Some notes:
Unlike the generic GSI, calling works.
Also unlike the GSI, the colors don't invert randomly.
Magisk DOES NOT work at the moment, neither phhuson's nor regular Magisk. Flashing it will cause a bootloop.
Bluetooth audio has been reported to not work
As with many Android 10 GSIs/ROMs, Chrome freezes or crashes because GApps packages currently are missing the new Trichrome WebView implementation which replaces Chrome as the default WebView. This being worked on (see OpenGApps wiki and issue #773 on their GitHub.) For now, use another browser (like LineageOS's default browser) if you install GApps. —As soon as Trichrome is added onto the ARM package just as it has for ARM64, Chrome should be stable.
For now, that's all I can think of. However, if you notice any other bugs or caveats, let me know so I can add it to the list.
This is a GSI based on phhuson's prereleased GSI work and also based on the prereleased LineageOS 17. This is a pre-release so please be careful and don't use this as a daily driver. Things may break randomly, whoops, so please be patient! If you see any bugs, report them here.
Extremely huge shoutout to CodyF86 for this GSI!
The developer of this ROM has moved on to another phone and the community now has a full fledged 64-bit ROM which has much better support for things.

AgentICS said:
The LineageOS 17 GSI works great on the Moto G6. There are some caveats however for anyone willing to try it:
You MUST first flash the LineageOS 16.0 ROM first or else you will bootloop.
Use this Magisk from phhuson's official GitHub
Your screen may change colors and look weird, when this happens, go to Settings > Display > LiveDisplay> Color mode and change it to the value under the value selected on the menu and then back to the original one and that should fix it
If you flash GApps before first boot, follow AndyYan's suggestions as the Setup Wizard is broken for some reason on most GApps packages.
Calling while not on WiFi is broken for now.
For now, that's all I can think of. However, if you notice any other bugs or caveats, let me know so I can add it to the list.
This is a GSI based on phhuson's prereleased GSI work and also based on the prereleased LineageOS 17. Things may break randomly, whoops, so please be patient!
Click to expand...
Click to collapse
Just to reiterate, you are stipulating that this pre-release build doesn't permit me to make an outgoing phone call (nor possibly receive any) unless connected to a WiFi network? Please pardon my not-so-subtle-sarcasm ... but, why would anyone release this with a bug (or limitation) which inhibits the core functionality of the device? I could see a million other issues being permissible but not being able to make normal phone calls (or possibly even receive them) doesn't warrant any kind of release for testing. That being said, I'd be happy to help if possible and eagerly await a usable version of Android 10 to put on my Moto G6 which I only got a month ago (happily unlocked at a great price on Amazon). However, it is (currently) my main phone for making calls.

xda4joe said:
Just to reiterate, you are stipulating that this pre-release build doesn't permit me to make an outgoing phone call (nor possibly receive any) unless connected to a WiFi network? Please pardon my not-so-subtle-sarcasm ... but, why would anyone release this with a bug (or limitation) which inhibits the core functionality of the device? I could see a million other issues being permissible but not being able to make normal phone calls (or possibly even receive them) doesn't warrant any kind of release for testing. That being said, I'd be happy to help if possible and eagerly await a usable version of Android 10 to put on my Moto G6 which I only got a month ago (happily unlocked at a great price on Amazon). However, it is (currently) my main phone for making calls.
Click to expand...
Click to collapse
everything works for me

taiyofurukawa said:
everything works for me
Click to expand...
Click to collapse
so you can make phone calls without WIFI conection?

xavcasgar said:
so you can make phone calls without WIFI conection?
Click to expand...
Click to collapse
yesssss

xda4joe said:
Just to reiterate, you are stipulating that this pre-release build doesn't permit me to make an outgoing phone call (nor possibly receive any) unless connected to a WiFi network? Please pardon my not-so-subtle-sarcasm ... but, why would anyone release this with a bug (or limitation) which inhibits the core functionality of the device? I could see a million other issues being permissible but not being able to make normal phone calls (or possibly even receive them) doesn't warrant any kind of release for testing. That being said, I'd be happy to help if possible and eagerly await a usable version of Android 10 to put on my Moto G6 which I only got a month ago (happily unlocked at a great price on Amazon). However, it is (currently) my main phone for making calls.
Click to expand...
Click to collapse
It is pre-release so not all the bugs are ironed out, I should have added that this should not be used on your daily driver. But yes, it's dumb to use a phone that can't make calls without WiFi. Just as a note, you can make and receive calls however if you're not using WiFi, the caller can't hear you. I have filed a bug upstream with phhusson as this affects every GSI built using his work (Pixel Experience, Lineage and AOSP which I've tested). I hope this gets fixed soon so stay tuned to that GitHub issue

taiyofurukawa said:
everything works for me
Click to expand...
Click to collapse
xavcasgar said:
so you can make phone calls without WIFI conection?
Click to expand...
Click to collapse
taiyofurukawa said:
yesssss
Click to expand...
Click to collapse
How? What is your modem version/phone model?

Can't Boot
AgentICS said:
The LineageOS 17 GSI works great on the Moto G6. There are some caveats however for anyone willing to try it:
You MUST first flash the LineageOS 16.0 ROM first or else you will bootloop.
Use this Magisk from phhuson's official GitHub
Your screen may change colors and look weird, when this happens, go to Settings > Display > LiveDisplay> Color mode and change it to the value under the value selected on the menu and then back to the original one and that should fix it
If you flash GApps before first boot, follow AndyYan's suggestions as the Setup Wizard is broken for some reason on most GApps packages.
Calling while not on WiFi is broken for now.
Bluetooth is horribly broken for now, it causes the app playing audio to lag and crash so please stay away from it.
Chrome is wonky at the moment. It'll work and then all of a sudden cause the whole OS to lag and crash or become unresponsive. This is possibly an upstream GApps issue.
For now, that's all I can think of. However, if you notice any other bugs or caveats, let me know so I can add it to the list.
This is a GSI based on phhuson's prereleased GSI work and also based on the prereleased LineageOS 17. This is a pre-release so please be careful and don't use this as a daily driver. Things may break randomly, whoops, so please be patient!
I am documenting everything on here. Stay tuned to that page for more info and further updates. Addiotionally, I have filed a bug report regarding calling, please add on to that GitHub issue and bump it so it can get resolved.
Click to expand...
Click to collapse
Ok, so I installed and flashed Lineage 16 first. Then I flashed Lineage 17 GSI in system img, but then when I did that I go into twrp and it said an os was not installed and wouldn't boot. But if I just flash Lineage 16 it would boot. Am I doing something wrong?

SomeAndrodGuyWithInternet said:
Ok, so I installed and flashed Lineage 16 first. Then I flashed Lineage 17 GSI in system img, but then when I did that I go into twrp and it said an os was not installed and wouldn't boot. But if I just flash Lineage 16 it would boot. Am I doing something wrong?
Click to expand...
Click to collapse
First off, are you unzipping the file? The standalone uncompressed file is unflashable. It needs to be decompressed from it's .gz (or whatever it was compressed to) form. If you have, have you tried using fastboot flash system <lineage file name> from a PC?

AgentICS said:
It is pre-release so not all the bugs are ironed out, I should have added that this should not be used on your daily driver. But yes, it's dumb to use a phone that can't make calls without WiFi. Just as a note, you can make and receive calls however if you're not using WiFi, the caller can't hear you. I have filed a bug upstream with phhusson as this affects every GSI built using his work (Pixel Experience, Lineage and AOSP which I've tested). I hope this gets fixed soon so stay tuned to that GitHub issue
Click to expand...
Click to collapse
Just wanted to jump in here and say I'm seeing same bug on xt1925-6 with callers not able to hear me on any 10 gsi's and speakerphone does not work at all. Phh aosp 10 build 209 with stock pie 55-37-7-2 boot vendor boots fine, other gsi's will only boot using the Ali lineage full ROM boot- vendor but call audio is broken as well. Thanks for submitting the bug report, hopefully it will get fixed in future builds.

Hello friends,
It's been a while since i've posted on XDA. I was the person who originally rooted the g6 play. I managed to build a GSI image of 17.1 with the latest code as of today if anyone is interested I can upload it to gdrive or something, didn't feel like making a new thread.
It boots, mobile calls work, dark mode works (which is amazing), it all seems to work.
Getting it to compile was just short of a miracle...lol.
Only bad thing is I cannot get it to boot with any version of magisk even the version specifically for phh / Android 10, but with just the stock kernel with the ,verify removed it boots fine.

CodyF86 said:
Hello friends,
It's been a while since i've posted on XDA. I was the person who originally rooted the g6 play. I managed to build a GSI image of 17.1 with the latest code as of today if anyone is interested I can upload it to gdrive or something, didn't feel like making a new thread.
It boots, mobile calls work, dark mode works (which is amazing), it all seems to work.
Getting it to compile was just short of a miracle...lol.
Only bad thing is I cannot get it to boot with any version of magisk even the version specifically for phh / Android 10, but with just the stock kernel with the ,verify removed it boots fine.
Click to expand...
Click to collapse
That's amazing! Could you upload it please so I can test it?
Thank you!

AgentICS said:
That's amazing! Could you upload it please so I can test it?
Thank you!
Click to expand...
Click to collapse
GSI-Lineage-17.1-2-16-2020-system.img
It seems it only connects at 3g although it lists a different apn server on lineage, I may be able to fix that, and I couldnt get the sd card to format as anything but adaptive storage, but everything works more or less. going to recompile in a week its still pretty early in development stage of lineage.

CodyF86 said:
GSI-Lineage-17.1-2-16-2020-system.img
It seems it only connects at 3g although it lists a different apn server on lineage, I may be able to fix that, and I couldnt get the sd card to format as anything but adaptive storage, but everything works more or less. going to recompile in a week its still pretty early in development stage of lineage.
Click to expand...
Click to collapse
Huge thanks for this GSI!!! I've been using it and it works flawlessly, I have also observed that only 3G works for now but regardless of that, everything works fine.
Again, I can't reiterate enough how thankful I am with you for this GSI!

AgentICS said:
Huge thanks for this GSI!!! I've been using it and it works flawlessly, I have also observed that only 3G works for now but regardless of that, everything works fine.
Again, I can't reiterate enough how thankful I am with you for this GSI!
Click to expand...
Click to collapse
May have a fix for LTE compiling it now, using the stock apn file with the adjusted mcc mnc numbers.
If I could get root I could get it for sure, but I can't get it to boot with a magisk flashed kernel, even the android 10 special version of magisk.

I got LTE but now mobile network stays disconnected although there is an LTE connection. It's an apn issue will work on it. if I get it working will make a thread...not sure why magisk won't work with my builds / kernel though yet.
https://github.com/codyf86

I've noticed that restarting always restarts to the bootloader. I don't know if it's just me but that's weird

Could you provide a link to the kernel source used in the rom?

Uclydde said:
Could you provide a link to the kernel source used in the rom?
Click to expand...
Click to collapse
It's on his GitHub

The kernel is actually just the stock kernel from the latest firmware with the ',verity' flag hexedited out to disable encryption. (You also need to change the fstab that is in all the guides ever made including my original one), but I'm working on building the kernel and making it work...but I got LTE to woooooork with some changes to the stock apn file lineage provides ! lol.
Only thing now is that it thinks my external sd card is corrupted and wont format right unless i set it to adaptive storage, so make a backup of your external sd card for now. Going to try using TWRP to format it with a couple different file systems.
Here she is boys.
Lineage-17.1-02.22.20-treble-arm-system
Still working on getting it to boost with magisk not sure why it won't when it was fine in Pie.
Still playing with the apn file the apn its using says sprint ehrpd but not sure what makes it pick which apns to show on the screen, but the apn is set to x.boost.ispsn which makes LTE work. I'll clean it up soon.
(All of this is assuming you're on Boost / Sprint)

rooted stock debloated , Omni ROM, or GSI? As of 082020?

And by debloated I mean Google too. I prefer zero crap on the phone but baked in"features"aren't bloat hahhaahaha. I've gotta run microg that's what I bought it for lol. Prefer toot so I can do what I want.

Well since no one knows, has tried all three, or is afraid to offend sunshine, I'll chime in myself.
The Omnirom build is very good and let's me do everything I need but not everything I want. I've read that it's better than using a GSI (generic system image - I think). Omni has been very stable to be as old as it is. I was able to remove the gapps and install microg.
Microg won't install in twrp, and won't work in magisk unless you make 100% sure Google play services are gone.
An easy way to check if things are on the right track with microg is to look in settings under system, if it shows up at the near the bottom it's going to work.
I was unable to get microg working with stock but I think I could now.
With big red ( Verizon) wifi calling is available on stock but not in omni. This is expected as I've never had to work on anything other than a stock rom in the past. So if you're at the edge of signal coverage or like I am at the edge and about the same distance between 2 towers in two states with different service in both lol, you might want to keep stock if you need that feature. If not I'd say Omni all the way.
Perhaps I'll add to this as time goes on.
If you are just starting out tahr note that fastbootd isn't the bootloader, and use the latest adb and fastboot from Google, even on Linux I downloaded the most recent to be sure but that's up to you.
The Lenovo Recover works great but fastbootd works well for fixing small blunders too.
Fastbootd says Fastboot in huge letters at the top you can't miss it. Hahaha
One thing I find peculiar is that I was able to use the Fastboot command in the bootloader mode to install twrp. This gave me a false sense of hope.
And I falsely assumed I was in Fastbootd. Fastboot has been around for years I just never used it. I think it was around in the Droidx days but I could be mistaken.
Good luck!
We are very fortunate to have vache and other devs working on these devices. As well as users who can test and stuff.

Another user asked this previously without any response ... Could you post a degoogled Omni ROM without gapps? Or give any advice how to remove it ? You were the one to put it all together so surely for you it must be easy removing it? As for me, I've been stuck.

Sorry i never saw this until now but I'm not a developer just a microg and self-hosted nextcloud user.

Working GSI ROMs on Mi Note 10 Lite / toco

As the title says, here's a list of some GSI's i have tested so far... but first for some story.
Bought the phone in summer, it's quite nice but has its own issues like no kernel source BUT since we can unlock the device and actually play around, oh boy it has been fun.
On the course of few hours and many downloads later I have a small list of GSI's that worked!
Every GSI I have mentioned REQUIRE device specific patch(es)!!!
For that you have to root.
----------------------WORKING GSI's-------------------------
BlissROM - It boots and functions quite fast
Cons: no included Gapps
Flashing any system editing patch results in "Phone is booting" homescreen.
https://sourceforge.net/projects/treblerom/files/BLESS/2020.09.21/
3.5 jack, VoLTE, Bluetooth, ComboFix patches are required, flash with Magisk manager
DO NOT USE FixLagSmooth
HavocOS 3.7 and 3.6 - Work and can be daily driven
3.6 requires FixLagSmooth patch
MUST root and apply all linked patches (don't use FixLagSmooth on 3.7, you can but no need)
https://forum.xda-developers.com/mi...rom-how-to-install-android-10-gsi-mi-t4126223
AOSP Android 10 based - Also does work and requires patching
https://forum.xda-developers.com/mi...rom-how-to-install-android-10-gsi-mi-t4126223
HydrogenOS Android 10 - Works
Has few bugs
No Google services
https://mirrors.lolinet.com/firmware/gsi/HydrogenOS/
----------------------COMMUNITY REPORTED GSI's-------------------------
Android 11 GSI - Reported to be functional by HumptyPotato47, thanks mate!
No Gapps as of now NikGapps exist for Android 11, search XDA for it!
Requires more testing...
https://github.com/phhusson/treble_experimentations/releases/tag/v300.f
----------------------MAYBE WORKING GSI's-------------------------
OxygenOS 10 GSI - Seems to work.. sorta
First boot after exiting fastboot causes the phone to reboot
Second boot will loop
https://mirrors.lolinet.com/firmware/gsi/OxygenOS/
----------------------NON FUNCTIONAL GSI's-------------------------
You tell me
...I did find a very nice list of GSI ROMs to try out more, here's the link:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
----------------------FLASHING GSI-------------------------
If you test one then don't hesitate with replying which one, about the experience, bugs and how you installed it.
My method of installing was this:
1. Make sure to have the new adb commandline that supports fastbootd mode
2. Drop the GSI .img file in /adb directory for ease
3. Make sure you're running MIUI with unlocked bootloader and USB debugging enabled
3.5 MAKE SURE you get a GSI ROM with Gapps as existing TWRP isn't fully functional
4. GSI you should have must be AB partition!!!​
Once all set then follow the next commands
>adb reboot bootloader
>fastboot -w
>fastboot reboot fastboot
>fastboot erase system
>fastboot flash system "GSI-ROM-name-without-quotes".img
>fastboot reboot bootloader
>fastboot reboot​
----------------------SETTING UP GSI-------------------------
Once all that is complete it should boot, if not then that specific GSI does not work.
Also a thing worth mentioning! Whenever I boot this phone to fastbootd Windows keeps forgetting what driver it was which requires
few extra clicks in device manager to set it up for fastbootd use. Including an image with simple to follow instructions if you have the same issue.
>fastboot boot twrp.img
Once in TWRP you should be able to access internal storage with your computer, drag Magisk.zip over and flash. Don't forget to wipe cache!
If it boots normally then root was successful, now apply the linked patch and reboot once again. Since we are playing with GSI:
Head to Settings
Find Phh Treble Settings
Misc features
Check Disable audio effect. -- DISABLE IT AFTER PATCHING!!!​
IMPORTANT!!! I only tested Havoc and Bliss for a long period, IF one of my mentioned GSI's or others require more patches then I have linked headphone jack and Bluetooth audio patches too.
Combo fix should do the trick thought so your mileage may vary.
----------------------HELP US-------------------------
IF you find more working GSI's then tell us and I will make sure to add them to the main post so it won't get clogged under other comments!

Update on 05.10.2020 GMT+3
Bliss ROM GSI
As only a day or two have passed I already encountered few issues.
> You cannot remove screenshot sounds, even when fully muted
> Data drain is something interesting I've noticed, consumption compared to MIUI is higher.
> When using the gesture navigation it is a bit buggy when using quick side swipe for multitasking.
Positive notes!
> It is stupid fast
> Battery life is good
> GCam is amazing
> 99% of the customization options work perfectly
> Fast charging modes and such work perfectly
Neutral stuff...
> No FOD, thanks for closed source
> whenever you take a picture or a screenshot and have Blutetooth audio connected, it pauses and plays out loud via speaker. No music leaks out

this phone is born dead, no developer cares about it.

alsartawi said:
this phone is born dead, no developer cares about it.
Click to expand...
Click to collapse
Sad truth but won't stop others from working on it. Eventually we might get a kernel source

Kevin Soosaar said:
Sad truth but won't stop others from working on it. Eventually we might get a kernel source
Click to expand...
Click to collapse
i would pay to see a stable custom rom for this phone, i really loved it.

alsartawi said:
i would pay to see a stable custom rom for this phone, I really loved it.
Click to expand...
Click to collapse
Havoc OS and Bliss ROM are both quite stable, albeit with Bliss you don't get Gapps which is a huge bummer to most users.
Personally I just installed MicroG services and use Aurora store with anonymous "account".
When I tried to flash Gapps with TWRP I ended up soft bricking ROM so it was required to restore stock and try again. Of course there's no need if you can still use fastbootd.

Kevin Soosaar said:
Havoc OS and Bliss ROM are both quite stable, albeit with Bliss you don't get Gapps which is a huge bummer to most users.
Personally I just installed MicroG services and use Aurora store with anonymous "account".
When I tried to flash Gapps with TWRP I ended up soft bricking ROM so it was required to restore stock and try again. Of course there's no need if you can still use fastbootd.
Click to expand...
Click to collapse
does FOD works on Havoc OS?
edit: sorry i just read that it's not working.

alsartawi said:
does FOD works on Havoc OS?
Click to expand...
Click to collapse
FOD is not working as the driver sources are not public, reverse engineering is not possible too afaik. Everything else works.

Should i send this phone back to Amazon?
Seriously, last night i bought it, thinking about to install some custom rom, but if there are no developers caring of it, i might returb the phone to the seller...

IMO MIUI EU is better then GSI roms. Everything works. Got rid of most chinese crap. You can use Magisk.
Have nice features (MIUI in general). The only thing i dont like -mine turns on WIFI byitself dotn know how it happens... but it happens when i sleep. china collecting logs?
https://www.scmp.com/abacus/tech/ar...earch-and-browsing-data-china-researcher-says

afigienas said:
IMO MIUI EU is better then GSI roms. Everything works. Got rid of most chinese crap. You can use Magisk.
Have nice features (MIUI in general). The only thing i dont like -mine turns on WIFI byitself dotn know how it happens... but it happens when i sleep. china collecting logs?
https://www.scmp.com/abacus/tech/ar...earch-and-browsing-data-china-researcher-says
Click to expand...
Click to collapse
Literally the main reason I made this post is to help others who are interested to use GSI ROM's on their devices. I do agree that MIUI has some decent features and I did use Xiaomu.eu before but it was so buggy. In the end I love customizing the device however I like it so MIUI is just not for me. Either way I might try to negotiate with Amazon to get a refund as touch and Bluetooth problems still persist. Fun fact, on Bliss the edge detection is pretty good and not as aggressive or straight out bad.

Simon_19 said:
Seriously, last night i bought it, thinking about to install some custom rom, but if there are no developers caring of it, i might returb the phone to the seller...
Click to expand...
Click to collapse
Actually there are plenty of people ready to build ROMs for Toco (Mi Note 10 Lite) and Tucana (Mi Note 10) but there just isn't any kernel source available. Making things worse is the cancelled release of Toco in India and we know that they are one of the biggest Android ROM builders next to Russians. No one there is gonna import a device like this because better phones for money exist. If you don't like it then yeah I recommend returning otherwise give GSI a try for now and see what happens.
You won't lose warranty as there is no E-fuse like on Samsung phones so locking bootloader and flashing back to stock is enough.

Is anyone try oos gsi ?

HumptyPotato47 said:
Android 11 GSI of phh is working fine. It is very smooth. But i switched back to miui because i can't find any android 11 gapps.
Click to expand...
Click to collapse
can you give the link of the rom?

HumptyPotato47 said:
Android 11 GSI of phh is working fine. It is very smooth. But i switched back to miui because i can't find any android 11 gapps.
Click to expand...
Click to collapse
Hi, there are gapps for Android 11, look for NikGapps here in XDA

Kevin Soosaar said:
Actually there are plenty of people ready to build ROMs for Toco (Mi Note 10 Lite) and Tucana (Mi Note 10) but there just isn't any kernel source available. Making things worse is the cancelled release of Toco in India and we know that they are one of the biggest Android ROM builders next to Russians. No one there is gonna import a device like this because better phones for money exist. If you don't like it then yeah I recommend returning otherwise give GSI a try for now and see what happens.
You won't lose warranty as there is no E-fuse like on Samsung phones so locking bootloader and flashing back to stock is enough.
Click to expand...
Click to collapse
who said its cancelled?

Dr. DoubtReaper said:
who said its cancelled?
Click to expand...
Click to collapse
The mentioned Mi Note 10 Lite for India was supposed to be called Mi 10i or something like that. It quickly disappeared and is not happening.
Of course I might be wrong by this date but looking for now there is no 10i, only speculation videos and threads.
Mi Note 10 Lite for India would've been code named "tocoin", same hardware and everything else so just a rebadge in old Xiaomi fashion... :laugh:

anyone tried new version of blissROM? feedback?

GaryFisher88 said:
anyone tried new version of blissROM? feedback?
Click to expand...
Click to collapse
Not sure if the one I linked is up do date, give it a try yourself as my device went in for warranty repairs.

Hello, I am currently using Xiaomi.eu based on MIUI 12 and I would like to know how to flash HAVOC OS GSI. Should I flash back to Global Rom then flash the GSI as indicated? Answer is greatly appreciated.

[Help Please] Setting up Magisk on Lineage 18.1

Hello everyone. Long time since I had an android device and I'm cutting the chains of my iPhone wanting to be de-Googled and de-Appled. I was running Lineage 17.1 from Microg and thought I had everything working on it until I started updating some software on my phone over the air. I rebooted and it went to bootloop. Since then I re-installed 17.1 and got things working again. I just upgraded to 18.1 and want to make sure it's all set up properly and won't have any errors.
Magisk says SafetyNet has an "SafetyNet API Error." "Basicintegrity, ctsProfile, evalType N/A." all in red when I check if it's working. I've done some digging, but want to make sure I do this right. I need to get the boot.img file from the original firmware. Should I get this from the oneplus website, or should I be looking for something else since I have Lineage? Can anyone provide the raw boot.img file for the OnePlus 7 Pro that I should use? I'm a little overwhelmed with all of the steps to extract it from the original firmware. Please and thanks for any help getting this phone set up the way I need it to work!

That error show when safety net API download was incomplete/corrupt, you can try to erase data from magisk manager and check safetynet again but with a better internet connection or use another magisk version like canary
And if you end in a bootloop for any magisk module just turn off your device and in your computer in a CMD/powershell/terminal window enter this command
adb wait-for-device shell magisk --remove-modules
Then connect and turn on your phone and automatically your phone will reboot with all your magisk modules disabled

Use magisk canary bro,,,

I sideloaded Canary and still get the red SafetyNet API error screen after opening it. Can someone direct me to a full tutorial on how Magisk works and what the modules do? I'm thinking I might need to do a full uninstall of Magisk and start over. If I do this will I lose all the data on the phone and have to start from scratch? Thanks for your help so far!

Well I've spent several hours researching tutorials and typing in codes via Terminal on my Mac and have gotten the phone restocked twice and working normal on stock OS, but after putting TWRP on it and then installing Lineage 18.1 it goes into a Lineage logo boot loop. What am I missing here?
It seems to me that TWRP is not compatible with Lineage. Sometimes when I rebooted the phone and was playing with the Recovery.IMG I saw the Lineage Recovery, then other times the TWRP would flash on and off in a boot loop. I have been careful about using the command " ./fastboot boot TWRP.img " and not "flash" TWRP, as would be the case for non a/b storage devices. On a couple occasions I could reboot with the Lineage Recovery.IMG and it would boot to startup, but if I rebooted to Recovery from the home screen, it would get stuck on TWRP.
I'm probably just missing something simple, but what might I be doing wrong? Is it the timing of installing TWRP and then installing Lineage in the same TWRP session?
This all stemmed from me wanting to get TWRP with Lineage 18.1 and getting Magisk and Microg working correctly for a "de-googled" phone with working apps. I'm frustrated, but will keep trying if I can get some direction. Thanks for your input.
-L

Lear31pilot said:
Well I've spent several hours researching tutorials and typing in codes via Terminal on my Mac and have gotten the phone restocked twice and working normal on stock OS, but after putting TWRP on it and then installing Lineage 18.1 it goes into a Lineage logo boot loop. What am I missing here?
It seems to me that TWRP is not compatible with Lineage. Sometimes when I rebooted the phone and was playing with the Recovery.IMG I saw the Lineage Recovery, then other times the TWRP would flash on and off in a boot loop. I have been careful about using the command " ./fastboot boot TWRP.img " and not "flash" TWRP, as would be the case for non a/b storage devices. On a couple occasions I could reboot with the Lineage Recovery.IMG and it would boot to startup, but if I rebooted to Recovery from the home screen, it would get stuck on TWRP.
I'm probably just missing something simple, but what might I be doing wrong? Is it the timing of installing TWRP and then installing Lineage in the same TWRP session?
This all stemmed from me wanting to get TWRP with Lineage 18.1 and getting Magisk and Microg working correctly for a "de-googled" phone with working apps. I'm frustrated, but will keep trying if I can get some direction. Thanks for your input.
-L
Click to expand...
Click to collapse
TWRP is not working for OOS11 or A11 ROMs using Oos11 blobs.

Lossyx said:
TWRP is not working for OOS11 or A11 ROMs using Oos11 blobs.
Click to expand...
Click to collapse
Got it! I'll go back to 17.1 Thanks!

Bump
Still trying to find a solution. I get fairly far into flashing the ROM, getting TWRP working and then end up stuck at Microg not letting me open the location menu. If only there were a guide with start to finish Lineage 17.1 or 18.1 with Microg and Magisk for my OnePlus 7 Pro. I find some guides, but there isn't one that encompasses everything that actually works. I'm going to try Lineage 18.1 with Microg built in and then flash Magisk.

Lear31pilot said:
Bump
Still trying to find a solution. I get fairly far into flashing the ROM, getting TWRP working and then end up stuck at Microg not letting me open the location menu. If only there were a guide with start to finish Lineage 17.1 or 18.1 with Microg and Magisk for my OnePlus 7 Pro. I find some guides, but there isn't one that encompasses everything that actually works. I'm going to try Lineage 18.1 with Microg built in and then flash Magisk.
Click to expand...
Click to collapse
I never installed lineage but i guess you can flash the ROM, change slots, then format data(this will erase all your stuff) and flash magisk then reboot into system
And for the safety net error yesterday was released a "fix" for that so try again

RokCruz said:
I never installed lineage but i guess you can flash the ROM, change slots, then format data(this will erase all your stuff) and flash magisk then reboot into system
And for the safety net error yesterday was released a "fix" for that so try again
Click to expand...
Click to collapse
Thank you. I'll have to address this at some point. I got the phone restocked, and flashed 18.1 Lineage on it again. Got all my apps and accounts back up on it. I'm just debating running Magisk again knowing that I'll likely have to start from scratch again. I wasn't able to get TWRP working correctly, so I left Lineage Recovery on, so it will be some time before I try going through this again. I'm going to do some research on what exactly is happening when I put recoveries and ROMs on different slots. Same goes for the Magisk. It's all quite new to me with the "slots" and what information has to go on which slot. I also need to find out how to backup my apps so if I re-flash a ROM, it's not so painful to get my data back on the phone.
At least I have a working phone without a Google login and most of the apps I want work. I'm only missing Lyft and my bank app. Again, thanks for the reply, and I'll look into this when I have some time to play with the phone again.

Lear31pilot said:
Thank you. I'll have to address this at some point. I got the phone restocked, and flashed 18.1 Lineage on it again. Got all my apps and accounts back up on it. I'm just debating running Magisk again knowing that I'll likely have to start from scratch again. I wasn't able to get TWRP working correctly, so I left Lineage Recovery on, so it will be some time before I try going through this again. I'm going to do some research on what exactly is happening when I put recoveries and ROMs on different slots. Same goes for the Magisk. It's all quite new to me with the "slots" and what information has to go on which slot. I also need to find out how to backup my apps so if I re-flash a ROM, it's not so painful to get my data back on the phone.
At least I have a working phone without a Google login and most of the apps I want work. I'm only missing Lyft and my bank app. Again, thanks for the reply, and I'll look into this when I have some time to play with the phone again.
Click to expand...
Click to collapse
TWRP can't boot in devices with OOS 11 blobs and encrypted data, for Magisk the only way I can imagine is using a patched boot.img.
Make a backup of your current boot.img(lineage) with apps like Franco kernel, then Patch it with magisk, then flash it in fastboot (fastboot flash boot boot.img)
if something woes wrong you can restore the backup from Franco kernel

RokCruz said:
TWRP can't boot in devices with OOS 11 blobs and encrypted data, for Magisk the only way I can imagine is using a patched boot.img.
Make a backup of your current boot.img(lineage) with apps like Franco kernel, then Patch it with magisk, then flash it in fastboot (fastboot flash boot boot.img)
if something woes wrong you can restore the backup from Franco kernel
Click to expand...
Click to collapse
Thanks RokCruz,
I'm going to get 18.1 back on with the LOS Recovery again. I'll try the boot patch method with the LOS boot.img from 18.1 for Magisk. I haven't tried the Franco kernel as I just now found out about it. I don't really need to do anything else fancy with the phone in terms of overclocking or underclocking. Does that kernel facilitate easier backups? I'm still learning a LOT about how Android works. It's been a steep learning curve. Fortunately, I can get myself out of any binds with a restock and fastboot!

Lear31pilot said:
Thanks RokCruz,
I'm going to get 18.1 back on with the LOS Recovery again. I'll try the boot patch method with the LOS boot.img from 18.1 for Magisk. I haven't tried the Franco kernel as I just now found out about it. I don't really need to do anything else fancy with the phone in terms of overclocking or underclocking. Does that kernel facilitate easier backups? I'm still learning a LOT about how Android works. It's been a steep learning curve. Fortunately, I can get myself out of any binds with a restock and fastboot!
Click to expand...
Click to collapse
Yes only for boot backups, I always made a backup of my boot.img of every OB just in case something goes wrong but i have never experienced that.
I personally prefer OOS, just install custom kernel and some mods like Cyberpunk 2077 theme, Riru Lsposed and a adbloker and that's all I need

RokCruz said:
Yes only for boot backups, I always made a backup of my boot.img of every OB just in case something goes wrong but i have never experienced that.
I personally prefer OOS, just install custom kernel and some mods like Cyberpunk 2077 theme, Riru Lsposed and a adbloker and that's all I need
Click to expand...
Click to collapse
I'm trying to de-google. Can I de-google on OOS? Most stock ROMs require a google login.

Lear31pilot said:
I'm trying to de-google. Can I de-google on OOS? Most stock ROMs require a google login.
Click to expand...
Click to collapse
I guess you can, just use a debloater
But it's better to install HydrogenOS just disable Chinese apps, install micro g and it's complements and you can run any Google dependant app, safety net passes without problems too.
I installed hydrogen and it runs smoothly but Cyberpunk isn't available for it so I reinstalled OOS

RokCruz said:
I guess you can, just use a debloater
But it's better to install HydrogenOS just disable Chinese apps, install micro g and it's complements and you can run any Google dependant app, safety net passes without problems too.
I installed hydrogen and it runs smoothly but Cyberpunk isn't available for it so I reinstalled OOS
Click to expand...
Click to collapse
Thanks for the tip about Hydrogen. I'll do some research on that. And thanks for getting back so quickly. The Android community really has some great people. Happy to be apart of it!

So
Lear31pilot said:
Thanks for the tip about Hydrogen. I'll do some research on that. And thanks for getting back so quickly. The Android community really has some great people. Happy to be apart of it!
Click to expand...
Click to collapse
So at the end of the day, I ended up with HydrogenOS 11 and have F-Droid and Aurora Store installed and working fine. I didn't/don't need Magisk or MicroG since HOS apparently is OK'd by google and all of my apps work.
So this worked perfectly for me. I have a fully functional OS and no Google sign-in needed. I did as you said and just deleted the Chinese bloat apps. I can't manage to get rid of the "Market" app though.
Lyft works and all of my location requiring apps like Waze work as well. Thanks for pointing me in the right direction.
Question: Will OxygenOS work the same without a google login? If so, what would be the advantage of HOS vs OOS? HOS 11 has an entire section devoted to a Google login for different services. I left it blank, but just wondering what the difference would be on OOS.

Lear31pilot said:
So
So at the end of the day, I ended up with HydrogenOS 11 and have F-Droid and Aurora Store installed and working fine. I didn't/don't need Magisk or MicroG since HOS apparently is OK'd by google and all of my apps work.
So this worked perfectly for me. I have a fully functional OS and no Google sign-in needed. I did as you said and just deleted the Chinese bloat apps. I can't manage to get rid of the "Market" app though.
Lyft works and all of my location requiring apps like Waze work as well. Thanks for pointing me in the right direction.
Question: Will OxygenOS work the same without a google login? If so, what would be the advantage of HOS vs OOS? HOS 11 has an entire section devoted to a Google login for different services. I left it blank, but just wondering what the difference would be on OOS.
Click to expand...
Click to collapse
Market can be disabled if my mind serve me right, OOS could end in a bootloop if we remove all Google apps so it's better not to do that.
I never see that section, I only installed OB1 and OB2 and never see that.

And remember you need to install magisk in order to pass safetynet.

RokCruz said:
Market can be disabled if my mind serve me right, OOS could end in a bootloop if we remove all Google apps so it's better not to do that.
I never see that section, I only installed OB1 and OB2 and never see that.
Click to expand...
Click to collapse
Looks like I'm denied the ability to disable the Market App.
Photo's attached for the Google settings I have available on HOS 11.
Also unable to make the microphone work in the keyboard for voice to text, but I have a feeling I won't be able to make that work without logging in to Google. Currently looking for some workarounds.
What will passing Safetynet allow me to do that I'm not already able to do now? Use banking apps and "tap to pay" type apps? I haven't found my bank app on the Aurora Store just yet. "US Bank" if it makes a difference.
I'll continue to play with this OS, but so far, it seems the easiest to get working right from the get-go.