[ROM][OFFICIAL][ginkgo][11] LineageOS 18.1 for Redmi Note 8 / 8T

Search This thread

BeriCud

Senior Member
Dec 9, 2010
245
36
It sounds so easy, and - in fact - I had this rom installed pretty recently, then tried another rom - with disastrous results... bricked my RN8T but after many tries, was able to revive the phone with EDL (test points method) and QFIL. Meanwhile, I had bought a Redmi Note 11 as replacement (and placed my sim-card ex-RN8T into my new phone).
Well, I thought, now I'm going to use my old RN8T to try LineageOS 18.1 more specifically. Tried to install again, but this time the installation went wrong. All looked well until reboot: the animated LineageOS showed all right, but then the phone restarted again. And this repeated continuously.
I now have a question, because - in my opinion - thit is the only difference with the earlier installation when all went all right: does it make a difference whether a sim-card is placed or not?
With an older phone, some years ago, I was used to use TWRP to install the ROMs, having placed
the relevant zip-files on the phone beforehand. But this no longer appears to work, because - after wiping - everything on the phone seems encrypted (or has been decrypted after having been encrypted before the wiping). Therefore, I have to revert to flashing through adb sideload. And then something like "system destroyed" occurs. In other words, I'm doing something wrong. Is there somewhere a guide to install custom ROMs, writting in a somewhat more detailed way? Its sounds so easy: "flash recovery", "flash firmware", "flash ROM" etc., but in practice I ran into a bricked device. Happily, I've been able to bring back my RN8T to life so far, but it's a time-consuming process anyway. Still I would like to try a custom ROM, mostly for reasons of security. The RN8T will no longer receive updates; date of the last security patch is 1-5-2022. I woukl like to extend the life of the phone a few more years.
I think you didn´t do some steps which you should. The procedure shoul be on the first page. My procedure is a bit different but for me work for this days so it should help for you too.

  • Download the latest build and gapps
  • Reboot to recovery
  • backup data (if you are using LineageOS on same version and want use apk you have already instaled after flashing rom you are going update)
  • wipe parttitons (system, data, cache, dalvik/ART cache, vendor, internal storage (backup all data you want save before do this)
  • Format data (IMPORTANT DO THIS - cause reboots)
  • Flash the latest build, disable_Dm-Verity_ForceEnrypt (optional for not encryption storage), last firmware and gapps
  • Reboot
  • after bootup directly reboot to recovery
  • restare data (optional if you don´t wanto restore previous data you can set all data (install apk) just as new device

This way it should work for you. No SIM card needed.
 

gjongbloed

Member
Oct 23, 2016
30
2
I think you didn´t do some steps which you should. The procedure shoul be on the first page. My procedure is a bit different but for me work for this days so it should help for you too.

  • Download the latest build and gapps
  • Reboot to recovery
  • backup data (if you are using LineageOS on same version and want use apk you have already instaled after flashing rom you are going update)
  • wipe parttitons (system, data, cache, dalvik/ART cache, vendor, internal storage (backup all data you want save before do this)
  • Format data (IMPORTANT DO THIS - cause reboots)
  • Flash the latest build, disable_Dm-Verity_ForceEnrypt (optional for not encryption storage), last firmware and gapps
  • Reboot
  • after bootup directly reboot to recovery
  • restare data (optional if you don´t wanto restore previous data you can set all data (install apk) just as new device

This way it should work for you. No SIM card needed.
(1) Reboot to recovery... Are you using the recovery (associated with the ROM) on following page?
Or do you use a relevant TWRP.img as recovery?
Reboot to recovery? Presumably wirh commands 'fastboot flash recovery (recovery name.img)'
(2) All the wipes plus format data... OK
(3) Flash latest build, latest firmware and gapps... How do you 'flash'? In TWRP one would select "Install", to install a zip file, but that zip-file must be present on the phone itself. Same applies to the gapps-file. And where do I find the firmware-file?
Or is the flashing done through the (associated) recovery? No need to have the files to be flashed, present in the internal memory of the phone? Or is the flashing also done with fastboot flash commands? Is it allowed to rename/shorten the filenames of the zip files in order to avoid typing errors in the fastboot flash commands?

Help enormously appreciated!
 

Uluru25

Senior Member
Nov 27, 2016
392
152
Samsung Galaxy S7
Samsung Galaxy A6
(1) Reboot to recovery... Are you using the recovery (associated with the ROM) on following page?
Or do you use a relevant TWRP.img as recovery?
Reboot to recovery? Presumably wirh commands 'fastboot flash recovery (recovery name.img)'
(2) All the wipes plus format data... OK
(3) Flash latest build, latest firmware and gapps... How do you 'flash'? In TWRP one would select "Install", to install a zip file, but that zip-file must be present on the phone itself. Same applies to the gapps-file. And where do I find the firmware-file?
Or is the flashing done through the (associated) recovery? No need to have the files to be flashed, present in the internal memory of the phone? Or is the flashing also done with fastboot flash commands? Is it allowed to rename/shorten the filenames of the zip files in order to avoid typing errors in the fastboot flash commands?

Help enormously appreciated!
Firmware can be downloaded here: https://xiaomifirmwareupdater.com/firmware/willow/

If you have a ginkgo, jump back in the structure and select ginkgo.

edit: here is the link https://xiaomifirmwareupdater.com/firmware/ginkgo/
 
Last edited:

gjongbloed

Member
Oct 23, 2016
30
2
So (I presume)...
  • 'recovery' is the associated LineageOS recovery?
  • the wiping/flashing is all done through this recovery?
  • No need to have the lineageOS ROM, firmware and gapps (as zip files) placed in the internal memory of the phone beforehand?
    (Because, I guess that these files - if placed on the phone beforehand - will have been wiped after the wiping and 'format data')
 
Last edited:

Uluru25

Senior Member
Nov 27, 2016
392
152
Samsung Galaxy S7
Samsung Galaxy A6
So (I presume)...
  • 'recovery' is the associated LineageOS recovery?
  • the wiping/flashing is all done through this recovery?
  • No need to have the lineageOS ROM, firmware and gapps (as zip files) placed in the internal memory of the phone beforehand?
    (Because, I guess that these files - if placed on the phone beforehand - will have been wiped after the wiping and 'format data')
1) You can use the Lineage recovery but I use TWRP since these recoveries provide some more options. I run this recovery:
2) yes, wiping, formatting and flashing is done in the revovery
3) indeed formatting (!) /data will erase all files etc. you have stored there. Wiping (!) /data will erase your installed apps but not erase a specific folder inside /data where all your personal files are stored
4) since I am to lazy to use adb commands, I do all via the recovery and therefore use an sd-card inserted into the phone. And thus have all files I need: the lineage rom, firmware, magisk (manually renamed from .apk to .zip) and some basic apps (e. g. AFWall or the modules I want later to install in magisk) before on the sd-card
5) I try to live "google-free" and therefore do not install any gapps; therefore I can't recommend you here anything
 

gjongbloed

Member
Oct 23, 2016
30
2
1) You can use the Lineage recovery but I use TWRP since these recoveries provide some more options. I run this recovery:
2) yes, wiping, formatting and flashing is done in the revovery
3) indeed formatting (!) /data will erase all files etc. you have stored there. Wiping (!) /data will erase your installed apps but not erase a specific folder inside /data where all your personal files are stored
4) since I am to lazy to use adb commands, I do all via the recovery and therefore use an sd-card inserted into the phone. And thus have all files I need: the lineage rom, firmware, magisk (manually renamed from .apk to .zip) and some basic apps (e. g. AFWall or the modules I want later to install in magisk) before on the sd-card
5) I try to live "google-free" and therefore do not install any gapps; therefore I can't recommend you here anything

That is great. It clarifies all my uncertainties. You helped me tremendously; thanks a lot!
 

Uluru25

Senior Member
Nov 27, 2016
392
152
Samsung Galaxy S7
Samsung Galaxy A6
That is great. It clarifies all my uncertainties. You helped me tremendously; thanks a lot!
You're welcome - good luck! After having flashed the new rom check in the dev options that usb debugging is still enabled and that your PC or notebook is recognized ther, so that you always have this way to modify / repair your system if you are locked out via the recovery (at least I do it this way) .
 
Oct 22, 2017
35
9
Hello guys, I've been using LineageOS for almost 2 years now, the ROM is perfect, no bloatware, no lags, but there's one issue only, the phone randomly reboots on its own, sometimes. Mostly this happens when I'm walking and I grab my phone out for a second from my pocket, or it happens when i turn off Wifi option.
Anyone else having such similar issues? please let me know.
Hey, had the same issue. It seemed to start a few releases ago (mid-Sept). Earlier it seemed to be a microSD issue (replaced it and most reboots went away), but I still get it once or twice a week. Randomly I grab the phone and it's off... no rhyme or reason. But it's a small inconvenience compared to the freedom!
 
Oct 22, 2017
35
9
Just wondering though, if developments are still ongoing.

Around Nov 1, I started have weird wifi issues that it should suddenly drop my home wifi connection and take 3 - 4 tries to reconnect manually.

But I also noticed that the Nov 1 build is the last one available.

Thanks for all the hard work to make this ROM what is is though!!
 
  • Like
Reactions: realtimes

gjongbloed

Member
Oct 23, 2016
30
2
  • Alas... hard brick again...
  • Flashing TWRP (willow) went OK
  • Flashing and formatting OK
  • I had the firmware-lineage OS - Gapps - Magisk .zip files all renamed in shortened filenames in the adb-fastboot folder
  • From there with 'adb push (filename).zip /data' commands, all four files placed in the /data folder of the phone
  • Then installed (with TWRP Install) the 4 files in one move. Then reboot...
  • The animated Lineage logo appeared, even once "Hi there...", but then it broke off, repeating the bootprocess, breaking off and repeating again...
  • Was still able to reopen recovery/TWRP, so decided to repeat the flashing process, but this time one-by-one
  • Flashing the nightly file: OK
  • flashing the firmware however ended with the message "this package is for willow devices; this is a 'ginkgo' (??? it is a 'willow ')
  • Anyway, decided to download the ginkgo firmware, which took about an hour - slow server
  • Renamed the file, pushed it to the /data folder on the device, restarted the installation of the firmware-, gapps- and Magisk-files through TWRP
  • wipe cache and Dalvik at the end
  • reboot... and then... only a slow flashing screen. Booting in recovery- or fastboot-mode is no longer possible.
  • Have to revert to the EDL mode again to re-install stock-ROM (for the 3rd time)...
 
Last edited:

BeriCud

Senior Member
Dec 9, 2010
245
36
  • Alas... hard brick again...
  • Flashing TWRP (willow) went OK
  • Flashing and formatting OK
  • I had the firmware-lineage OS - Gapps - Magisk .zip files all renamed in shortened filenames in the adb-fastboot folder
  • From there with 'adb push (filename).zip /data' commands, all four files placed in the /data folder of the phone
  • Then installed (with TWRP Install) the 4 files in one move. Then reboot...
  • The animated Lineage logo appeared, even once "Hi there...", but then it broke off, repeating the bootprocess, breaking off and repeating again...
  • Was still able to reopen recovery/TWRP, so decided to repeat the flashing process, but this time one-by-one
  • Flashing the nightly file: OK
  • flashing the firmware however ended with the message "this package is for willow devices; this is a 'ginkgo' (??? it is a 'willow ')
  • Anyway, decided to download the ginkgo firmware, which took about an hour - slow server
  • Renamed the file, pushed it to the /data folder on the device, restarted the installation of the firmware-, gapps- and Magisk-files through TWRP
  • wipe cache and Dalvik at the end
  • reboot... and then... only a slow flashing screen. Booting in recovery- or fastboot-mode is no longer possible.
  • Have to revert to the EDL mode again to re-install stock-ROM (for the 3rd time)...
Sorry for late reply.

Do you have open bootloader? Did you ask/apply for unlocking miui device https://en.miui.com/unlock/index.html? I hope so becouse without that it´s impossible flash custom rom.

So if you have already unlock your device you have to for the last time (for me) use ADB for flash some recovery (for me orangefox) and then boot into recovery (if everything went well should be orangefox).

Then all necessary things for flashing custom rom you can do in recovery and if I were you I'll use recovery (more user friendly). Of course is it necessary know which device you have gingko/willow and for your device flash proper file as firmware etc.

Flash only system + firmware for the first time without any other zip, if it all went well and system boot up you can i next round flash gapps and again try to boot up, slowly flash and reboot to come all files flashed and have working system with all things you want in your system (system, gapps, magisk, etc). You do something wrong for that reason flash step by step to find out where is the problem. Now I thing you wrote that you will flash stock rom. If so you could flash only system without firmware becaouse in stock rom you should have latest firmware and flash again firmware but separately is for nothing and if you choose badly you could brick your device so may be don´t do that (in first sentence I sugested it becouse some roms needed latest firmware and I didn´t realize you are going flash latest stock rom I gues.

Download the files needed for flashing to the sd card and flash from there. internal storage you should wipe and format so you can lose your file.

Good luck.
 
Last edited:

gjongbloed

Member
Oct 23, 2016
30
2
  • Bootloader was/is unlocked
  • Only returned to stock-ROM because the phone was hard bricked (again), no fastboot, no recovery, no nothing... Only possibily left was to re-install stock-ROM through EDL, using QFIL.
  • I do not have an SDcard, so I can't place files to be flashed there. Probably handy to buy and insert an SDcard. Will do that when I've solved next problem...
  • Meanwhile, I have a first priority problem: need to restore the IMEI number. *#06# reads "0/00"... Happily, I found at least one (of two) IMEI number(s) on the inside of the phone.
  • Also, have installed TWRP and rooted with Magisk
 

mattiafontanelli

New member
Dec 5, 2022
2
0
I'am on lineage last update with recovery patch
as boot
do not know (Magisk). root as well and microG.. I' have set an alarm song
in app and
also: without media; permission, it accept it but when my alarm wake up my phone from power of state do not ring (i am using a lockscreen)
only sometime with a strange notification event i dont have set i know because is a monotobe "Dlin".
Only work when the device is not turn off using different sound not from "system" think android 11 firmwere 12.5.6 use as long (single folder permission where you have to chose one folder for every app who need media) old Storage Access Framework i do not know. But clearing all data and chose from from phone settings a single song that'll be added in system sound of the application and problem solved, i don't know if i can save multiple but is enaf thxo..
 

wora92

Senior Member
Sep 19, 2019
83
31
Hello,

I have an issue with my Note 8. Apps like whatsapp or telegram cannot access the mic. If I make a call with those apps the other party cannot hear me. Is this a known issue? Is there a fix for that issue?

Some help would be appreciated.
 

ludemon

Senior Member
I have just flashed the latest nightly LOS 18.1 on to a RN8 and most things appear to be working except that the display goes blank for 1 second every 5 seconds. Repeated the procedure including flashing the latest EU firmware several times with the same result.
Has anyone else had this issue and what is the likely cause?
Further to this issue I have tried crDroid and Pixel Experience ROMs and although the result is not the same as LOS, there is a problem in that the screen touch stops working after waking the phone from the sleep condition. The only way to get back to an active screen again is to reboot the phone.
Is this problem likely to be due to the fact that the screen has been replaced?
However there is no such problems with MIUI and PixelPlusUI ROMs
This issue is also described in more detail at https://gitlab.com/LineageOS/issues/android/-/issues/5091
 
Last edited:

firefoxos

Senior Member
Jul 9, 2012
117
6
Hello,

I have an issue with my Note 8. Apps like whatsapp or telegram cannot access the mic. If I make a call with those apps the other party cannot hear me. Is this a known issue? Is there a fix for that issue?

Some help would be appreciated.
I had the same problem in the spring of 2022. It went away around may. Redmi Note 8T EU, LOS 18.1
 

firefoxos

Senior Member
Jul 9, 2012
117
6
Interesting. Did you do anything specific? Because I am on December version of LOS 18.1 and the problem still persists. Redmi Note 8 though, no T. Maybe that's the difference then.
I didn't. Notably the problem reappeared few builds down and went away with the following update. Please note that 8T has frequent LOS updates.
 

EthanWaber21

Member
May 10, 2019
5
0
Kharkiv
Hello 0/
Started to use LineageOS from december beginning. Want to say a lot of thanks because this rom works much better than all versions of miui 11 and miui 12. As I'm not developer and just usual customer and I did notice that with every new update of miui our phone works more badly.
Have some questions about LineageOS 18.1 for redmi note 8 (ginkgo):

1. It feature of clean android or some kind of issue when you get nottification and nottification light flashes, usually I need just press unblock button for turn off nottification light, but on LineageOS nottification light will be flashes till I open app or close nottification in status bar

2. Camera cutout looks a bit different not so smooth and you can see the pixels of the circle. For example I tried PixelExperience OS plus 13 Android and there all is ok with Camera cutout. It possible to fix it?

3. Uncertified Google play market shows, but I can use PayPal app from google store and all another apps, just worries about my personal data, will be all okay? Also tried to add device ID in google for sertification, but still shows as "Unsertified". Not sure that want to do roots and use Magisk app.
 

dam74

Member
Dec 23, 2022
5
0
Charix (France)
hi,
my redmi with lineage17.1 works fine since 2 years.
i wanted to test 18.1but it not start correctly : black screen and reboots

LineageOS version: 18.1
LineageOS Download url: https://mirrorbits.lineageos.org/fu...neage-18.1-20221201-nightly-ginkgo-signed.zip
Gapps version: no gapps ( i only use apkpure )

Did you--
wipe: yes
restore with titanium backup: no
reboot after having the issue: yes, it always reboot

Are you using--
a task killer: no
a non-stock kernel: no
other modifications: new recovery https://mirrorbits.lineageos.org/recovery/ginkgo/20221201/lineage-18.1-20221201-recovery-ginkgo.img

thank you !
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Good news from the dev (see screenshots from dev's TG channel): new build for 19.1 might come soon, also going to official seems possible for the dev.
  • 24
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    What's not working :
    • You tell me
    Instructions :
    • Download the latest build and gapps
    • Reboot to recovery
    • Format data (if it is first time installation)
    • Flash the latest build and gapps
    • Reboot
    Downloads :
    Reporting Bugs
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

    Code:
    What is your--
    LineageOS version:
    LineageOS Download url:
    Gapps version:
    
    Did you--
    wipe:
    restore with titanium backup:
    reboot after having the issue:
    
    Are you using--
    a task killer:
    a non-stock kernel:
    other modifications:
    
    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:


    LineageOS, ROM for the Redmi Note 8/8T

    Contributors

    DarkJoker360
    Source Code: https://github.com/LineageOS
    Device source code: https://github.com/ginkgo-dev
    Telegram support chat: https://t.me/ginkgodev

    ROM OS Version: Android 11
    ROM Kernel: Linux 4.x
    Based On: LineageOS
    13
    Dear ginkgo/willow users LineageOS is back !
    We are working to promote our devices to 18.1, few things to do are left such as pushing all and opening ticket.
    Changes are open at: https://review.lineageos.org/q/status:open+-is:wip
    Source will be the same as Official lineage 17.1 ones so clean flash will be needed.
    Stay tuned !
    11
    Hello !
    Here is an unofficial test build of LineageOS 19.1 for our device. Everything is working out of the box and it is ready to be daily driven. Will wait a bit to have feedbacks before releasing officially

    9
    Welcome Android 12 !

    Me and danascape booted new Android release at day one.

    Builds aren't unified yet.

    IMG_20211005_225449_388.jpg