Develop Bugs

Scrolling horizontal bar problem

Hello everyone.
Im having this problme that only occurs in custom roms and custom recovery. I started having this problem after i updated my phone to official ColorOS 2.0.
So because i couldn't flash that firmware with TWRP I had to go back to Oppo Recovery. I did that and installed new ColorOS.
I then decided to install DU ROM back on my phone (gotta love stock android feel). I went about by flashing latest TWRP 2.8.0.1 to my phone. Restarded phone back into recovery.
This is when i noticed a horizontal line scrolling from top to bottom. I went back to the OS and it was fine. Rebooted back to recovery and the line was still there. I went ahead and flashed DU to my phone. Once it got done i rebooted and now the problem still occurred in the ROM itself. A restart didn't help it either. Went back to recovery and flashed ColorOS lite and problem wasn't there. But when i go back to recovery the problem still persists.
Anyone have this issue?
Everything was working fine before the Color update.

Try flash color is 1.2.6 and then go to flash twrp & DU

tork987 said:
Try flash color is 1.2.6 and then go to flash twrp & DU
Click to expand...
Click to collapse
Should I flash official or kayula rom?
Should i flash it with official recovery or twrp?

I would flash the official with twrp

I need to do some more investigation, but it seems like KitKat ColorOS 2.x contains a new bootloader that causes graphics issues when running custom firmwares (or probably older ColorOS if you didn't downgrade bootloader in the process, for example if you restored a recovery backup instead of flashing COS 1.2.6)
I'll look into methods for bootloader downgrade that don't involve flashing a complete ColorOS package this weekend. I'm not sure, but IIRC, I think some of the existing baseband packages might be sufficient for the bootloader downgrade.

Entropy512 said:
I need to do some more investigation, but it seems like KitKat ColorOS 2.x contains a new bootloader that causes graphics issues when running custom firmwares (or probably older ColorOS if you didn't downgrade bootloader in the process, for example if you restored a recovery backup instead of flashing COS 1.2.6)
I'll look into methods for bootloader downgrade that don't involve flashing a complete ColorOS package this weekend. I'm not sure, but IIRC, I think some of the existing baseband packages might be sufficient for the bootloader downgrade.
Click to expand...
Click to collapse
I think your right. New color os does have a new bootloader because before the update the boot logo didnt contain the words "powered by android" . With this new one the logo looks different and it states those words at the bottom for a few seconds.

tork987 said:
Try flash color is 1.2.6 and then go to flash twrp & DU
Click to expand...
Click to collapse
thanks. this did the trick!

djabi90 said:
I think your right. New color os does have a new bootloader because before the update the boot logo didnt contain the words "powered by android" . With this new one the logo looks different and it states those words at the bottom for a few seconds.
Click to expand...
Click to collapse
The boot logo and the actual bootloader are separate components.

custom roms do not boot up

hi there,
i used crDroidAndroid-8.1-20180606-riva-v4.3 but there were color problems i didnt know 2 fix so i decided 2 flash a new rom resp. a newer version but no custom rom boots up.
when it tries 2 boot is freezes at the boot screen, then screen switches off and nothing happens. i can go 2 fastboot and recovery.
sometimes it boots up but after a few seconds it freezes 2.
i tried different roms and recoveries but nothing works.
i foolishly wiped internal storage once but then i flashed the stock rom again which boots up. then i unlocked the bootloader and flashed a custom recovery and a rom again but the same error is there (no booting up)
anyone got a solution for this problem? no unbricking suggestions plz
edit: im in the wrong thread i think. i wanted 2 post it in "Guides, News, & Discussion". cant delete it. sry for that

logs
so i managed 2 create logs while booting up.
1) https://pastebin.com/cgrX2DA1
2) https://pastebin.com/r7DmcN46
3) https://pastebin.com/0pwXyuys
4) https://pastebin.com/S41FG2SQ
1) is 1st part of the log while booting with no success to boot into the os.
2) is 2nd part of the log while booting with no success to boot into the os.
3) is 1st part of the log while booting with successful boot into the os.
4) is 2nd part of the log while booting with successful boot into the os.
i also tried 2 log "cat /proc/last_kmsg > /sdcard/last_kernel_message_log.txt"
and "dmesg > /sdcard/kernel_boot_log.txt" via terminal in linux but it only sais file or directory not found.
i hope sum1 can give me sum help now.

so i did this https://en.miui.com/thread-3921604-1-1.html but it doesnt help. as i expected.
any1? i can post more information if necessary. just say which and perhaps how ;D

cmon guys. i can impossibly b the only 1 who faces this problem.
i dont think its a hardware thing cause stock rom and android 7.1.2 (viper os) work. maybe a vendor problem? could flash another vendor img solve this problem? can sum1 send me his?
i got sum more logs after flashing rr 7.0:
logcat 1st part: https://pastebin.com/EBZAgbhF
logcat 2nd part: https://pastebin.com/qaMFrvxi
dmesg: https://pastebin.com/Gg8bYkJy
cheers

Fastboot flash latest miui 10 stable using mi flash tool and use the rom after setting up. Then flash custom recovery and do a full wipe.
This works for most cases.

NaAnBcEhEuL9A8K7 said:
Fastboot flash latest miui 10 stable using mi flash tool and use the rom after setting up. Then flash custom recovery and do a full wipe.
This works for most cases.
Click to expand...
Click to collapse
thx for ur answer but i tried this already. does not work on android 8 and 9 roms

daemonicvs said:
thx for ur answer but i tried this already. does not work on android 8 and 9 roms
Click to expand...
Click to collapse
Well it worked for me.
Which custom rom you want to use?

well, it doesnt matter 2 me. the main thing is that it works =D rr, aex, crdroid..

daemonicvs said:
well, it doesnt matter 2 me. the main thing is that it works =D rr, aex, crdroid..
Click to expand...
Click to collapse
Crdroid is my choice because aex and rr are very early builds. I like pixel experience but the devs not updating it so crdroid or havoc os.
Like i said use Xiaomi flash tool and flash miui 10 stable via fastboot method(there are 3 options in the bottom select flash all instead of flash and lock to avoid unlocking the bootloader again), don't flash anything else, setup and use the phone, flash recovery wipe all and format, install rom, don't flash gapps yet, boot into rom and see if its fixed.
Use vendor based recovery, if using batik recovery you have to flash batik recovery again after format.
This is my solution.

NaAnBcEhEuL9A8K7 said:
Crdroid is my choice because aex and rr are very early builds. I like pixel experience but the devs not updating it so crdroid or havoc os.
Like i said use Xiaomi flash tool and flash miui 10 stable via fastboot method(there are 3 options in the bottom select flash all instead of flash and lock to avoid unlocking the bootloader again), don't flash anything else, setup and use the phone, flash recovery wipe all and format, install rom, don't flash gapps yet, boot into rom and see if its fixed.
Use vendor based recovery, if using batik recovery you have to flash batik recovery again after format.
This is my solution.
Click to expand...
Click to collapse
i did it several times before but 2 b safe i did it again like that:
i flashed riva_global_images_V10.1.1.0.NCKMIFI_20181029.0000.00_7.1_global_f444c158ed.tgz using XIAOMI-TOOL-MiFlash-for-Linux-by-IceMan-master. im on linux mint 18.3. i have 4 options:
flash_all_lock.sh
flash_all_lock_crc.sh
flash_all_except_data_storage.sh
flash_all.sh
i chose flash_all.sh
i booted into the stock rom and set it up, enabled dev options and adb.
then i switched it off, went into bootloader, flashed twrp-3.2.3-0-riva.img via fastboot.
after that i entered twrp, flashed OrangeFox-R8.3-riva.zip and rebooted into recovery
i wiped everything except external sd and usb otg (i dont have these)
after a reboot intorecovery i formatted data then rebooted in recovery
i flahed crDroidAndroid-9.0-20181002-riva-v5.0.zip
then reboot into system
no success as i expected! wtf is wrong wtf. this cant b true!
but thank u very much for ur efforts! perhaps i would try 2 restore a vendor img from sum1 which rom does work. i know its a great demand but could u send me urs? ;D i dont know if there r sum personal info..
best regards

Don't give up there might be a solution.
Pray to God for some help.
:good:
---------- Post added at 01:23 PM ---------- Previous post was at 12:59 PM ----------
Currently I am using Xiaomi.eu beta rom. You can check their website for all the features. Its smooth, stable and can update without needing to got the recovery:victory:
This should work for you because unlike other roms this is based on miui for riva. That means you will get updates till Xiaomi ditches support for riva.
I recommend you use this rom over the global rom until you fix the problem with your phone.
Some things missing:
Choice of region is limited( India is not available)
There is no custom kernel available for miui oreo as of now.
Magisk safetynet not passed
If you're going flash this rom you need to be on latest global beta fastboot rom and need a recovery that supports oreo base.
I use batik recovery base oreo.

yes. i cant b the only 1 facing this problem...!? really. i cant!
thx anyway

daemonicvs said:
yes. i cant b the only 1 facing this problem...!? really. i cant!
thx anyway
Click to expand...
Click to collapse
Maybe you can be the only one facing this problem.
Try joing telegram community maybe your problem will get fixed from there.

NaAnBcEhEuL9A8K7 said:
Maybe you can be the only one facing this problem.
Try joing telegram community maybe your problem will get fixed from there.
Click to expand...
Click to collapse
theres no difference between my device and yours... everybody must have this problem ;/

daemonicvs said:
theres no difference between my device and yours... everybody must have this problem ;/
Click to expand...
Click to collapse
Did you try edl method?

NaAnBcEhEuL9A8K7 said:
Did you try edl method?
Click to expand...
Click to collapse
yes. i could flash the stock rom this way but the problem is not solved this way

daemonicvs said:
yes. i could flash the stock rom this way but the problem is not solved this way
Click to expand...
Click to collapse
At least you have to try.

I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.

Eddyb299 said:
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Click to expand...
Click to collapse
Did you flash lazy flasher?

Eddyb299 said:
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Click to expand...
Click to collapse
dont u have 2 wait 2 weeks or so till bootloader is unlocked?
what exactly do u mean with won't boot up? bootloop? or stuck at boot logo?
after flashing a custom recovery, did u boot directly into the system or did u try 2 boot into recovery? sometimes the stock recovery overwrites the custom 1 when stock rom boots up
my problem is solved. i remembered that i made a full nandroid backup with twrp before i flashed a new rom and the problem appeared. so i restored everything i backed up with twrp (incl cust) and voila, rom booted up. and i can wipe system and data and flash every rom i wanna and it still boots up \o/
i really could have tried it earlier but i didnt think of this untill yesterday ;D
well, thx for ur efforts anyway buddy @NaAnBcEhEuL9A8K7
cheers

Bootloop after installing magisk

hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?

mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
try to flash stock boot.img and recovery.img

sonn3 said:
try to flash stock boot.img and recovery.img
Click to expand...
Click to collapse
Same issue. So how would we go about flashing properly?

Search for recovery.img and boot.img in stock rom and flash in fastboot mode.

mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
Did you select close avb 2.0 in twrp and factory reset?

mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
We would need further details on which device (region) which MIUI version (number, android, region) you were on when you attempted to install Magisk. Of course we assume here you had unlocked your bootloader first, otherwise any attempt to flash anything will result in bootloop.
Many have successfully rooted on Android 9 regardless of MIUI version.
Complication often comes with Chineses devices from what I read, Global not so much so if you are on Global device consider yourself lucky
Easiest root is probably to flash LR team TWRP If you can still access fastboot mode (voloume - + power) version 09.24 or 11.04 if you are on Android 9 or version 12.10 if you are on Android 10. Note that you probably have more chances of success being on Android 9.
And use the root feature from WITHIN that TWRP to install root on your device.
You have a complete guide of the steps to reproduce here:
Guide
I have tested on Android 9, EEA device, EEA rom MIUI 11.0.2.0 and it works without an issue if you follow the guide provided above.
If you still want to manually flash Magisk from any other recovery, make sure to use version 19.04 which seems to have the higher odds of success (update afterward from Manager).
Also as mentioned by @wang1chung do not forget to close avb 2.0.
Myself I also had RM Force encrypt option used (just in case) even if not mentionned in the thread.
But unlike what was suggested in those threads I did not wipe data.
That said since I do not want to have TWRP to stick for now, I actually want it to automatically be replaced by stock recovery all went fine for me, and Magisk is there.
And when I need TWRP for something I just flash it again and do my stuff.
Hope this helps.
Good luck!

Same problem here. Luckly fastboot was still working (vol down + power after Redmi logo gets off). Then, I've downloaded stock ROM, and tryied manually execute fastboot commands, without success. Then, I've found a .bat file inside the root folder of the stock ROM .tar.gz archive, then executed the .bat file. Phone is working back. So, whats the catch about install Magisk? Any tips?

allxdadev said:
Same problem here. Luckly fastboot was still working (vol down + power after Redmi logo gets off). Then, I've downloaded stock ROM, and tryied manually execute fastboot commands, without success. Then, I've found a .bat file inside the root folder of the stock ROM .tar.gz archive, then executed the .bat file. Phone is working back. So, whats the catch about install Magisk? Any tips?
Click to expand...
Click to collapse
Personally I used the hassle-free method pressing the button to root directly from within the LR-TWRP (09.24, or 11.04 on Android 9 MIUI), swiped, then pressed that other provided button to close AVB 2.0, swiped and it worked on first attempt.
Of course TWRP got replaced on first reboot by system recovery, but I dont care as I do not want it to stick on my device. I just flash it again when I need it.
Magisk stayed, updated it from Manager (well manager updated first to that new ugly theme.... yurk!), then Magisk updated, no problem.
Note that I am on EU Phone running EEA MIUI 11.0.2.0. You might get a different outcome with other devices/roms.
Side note, LR-TWRP 09.24 installs Magisk 19.04 which has been reported numerous time to work on most Android 9 MIUI regional versions. LR-TWRP 11.04 howevers installs Magisk 20.0 fyi.
Hope this helps,
Regards,

regarding the thread title, i had the same problem. right when i was about to retart everything all over from 0, i was glad i was able to just go into twrp and just unroot. rebooted and it started as if nothing hsppended. now i jjust gotta find which module made me bootloop.

try this n give us the result

Question Standard oxygen OS or magisk and lineage ROM?

What you guys recommend better option I'm torn between oxy or lineage ROM with magisk for one plus 9 pro. Lmk thoughts Ty.

I used lineage for awhile and can say that battery life will be better, device will perform well, and background apps are more reliable, but I just prefer other ROMs over lineage, it's too basic in terms of customization and OOS is better in some ways. You'll give up the OnePlus camera app and it's optimizations and post-processing. If you're okay using gcam instead of OnePlus cam, then lineage is ok, but I'd recommend crDroid over it most definitely. Its equally stable but felt snappier and more complete feature set in my use. Plus the maintainer updates frequently and does a good job.

Yeah? Alright ... Thank you for your response I appreciate that, so you definitely reccommend using a custom ROM oppose to oxygen? And what is best for one plus 9 pro , CR? And do I use TWRP recovery ?! Thank you appreciate it .

Anonymous-Ciphers said:
Yeah? Alright ... Thank you for your response I appreciate that, so you definitely reccommend using a custom ROM oppose to oxygen? And what is best for one plus 9 pro , CR? And do I use TWRP recovery ?! Thank you appreciate it .
Click to expand...
Click to collapse
crDroid is the best I've used in terms of reliability, though I've been hearing EvolutionX is just as stable and on similar update schedule, and has even better customization, but I can't give full recommendation as I've only used on an older phone. But definitely had better experience with custom ROMs than OOS, so if you can unlock the bootloader, I'd go for it. You'll want TWRP recovery, but don't technically need it. You'll also want to have the newest OOS installed to avoid vendor driver issues (I haven't heard of a real problem except for T-Mobile model needing the vendor modem reflashed every time you update a custom ROM, better safe than sorry though)
Best way to flash would be to download TWRP (found in the development tab here on XDA) and get phone booted into bootloader. Then run
fastboot boot /location/of/twrp.img
Factory reset inside twrp
Then enter adb sideload mode and run
adb sideload /location/of/rom.zip
It WILL get stuck at 47% but will complete successfully if you wait 2-3 min. once finished, I'd repeat the exact same process once more as that will write your other boot slot to assure they're the same and prevent issues (lineage has a script for it, but doing the install process twice works just fine for me). From there, if you want TWRP installed permanently, in the advanced tab, you'll find "install current TWRP" and do that, reboot back into recovery to flash the magisk.apk as a zip file, and it will modify the boot to be running magisk.
You will find other ways of installing if you look at guides and such but what I've outlined works for every ROM and TWRP version I've used on my OP9p. You might see to flash the zip directly in TWRP instead of adb sideload, but some ROMs don't install that way, while adb sideload pretty much always works
Edited: forgot to add info that it's best to flash both A/B slots, added steps

thats_the_guy said:
crDroid is the best I've used in terms of reliability, though I've been hearing EvolutionX is just as stable and on similar update schedule, and has even better customization, but I can't give full recommendation as I've only used on an older phone. But definitely had better experience with custom ROMs than OOS, so if you can unlock the bootloader, I'd go for it. You'll want TWRP recovery, but don't technically need it. You'll also want to have the newest OOS installed to avoid vendor driver issues (I haven't heard of a real problem except for T-Mobile model needing the vendor modem reflashed every time you update a custom ROM, better safe than sorry though)
Best way to flash would be to download TWRP (found in the development tab here on XDA) and get phone booted into bootloader. Then run
fastboot boot /location/of/twrp.img
Factory reset inside twrp
Then enter adb sideload mode and run
adb sideload /location/of/rom.zip
It WILL get stuck at 47% but will complete successfully if you wait 2-3 min. once finished, I'd repeat the exact same process once more as that will write your other boot slot to assure they're the same and prevent issues (lineage has a script for it, but doing the install process twice works just fine for me). From there, if you want TWRP installed permanently, in the advanced tab, you'll find "install current TWRP" and do that, reboot back into recovery to flash the magisk.apk as a zip file, and it will modify the boot to be running magisk.
You will find other ways of installing if you look at guides and such but what I've outlined works for every ROM and TWRP version I've used on my OP9p. You might see to flash the zip directly in TWRP instead of adb sideload, but some ROMs don't install that way, while adb sideload pretty much always works
Edited: forgot to add info that it's best to flash both A/B slots, added steps
Click to expand...
Click to collapse

Thank you kindly I still can't get it. I tried doing cr android but it said I cant downgrade not allowed and twrp won't work, then when sideload cr android and it boots but my screen touch doesn't work and really liked the ROM would appreciate someone help

I return to OOS from Lineage OS last month, after using Lineage for a long time. Just because camera on Lineage just can't fit my needs. I tried Google Camera, but there are some bugs and still OOS camera is the best.

Anonymous-Ciphers said:
Thank you kindly I still can't get it. I tried doing cr android but it said I cant downgrade not allowed and twrp won't work, then when sideload cr android and it boots but my screen touch doesn't work and really liked the ROM would appreciate someone help
Click to expand...
Click to collapse
Haven't seen a no touch issue before. Well I'd try another factory reset inside TWRP and flash again, I believe 9 and 9 pro are unified for cr but also make sure you got the right zip. If that doesn't work, OOS 11.2.7 is the newest full zip file you can download from OnePlus, maybe try flashing that, and try installing crDroid without updating to 11.2.8 or 11.2.9. If that doesn't work, might be at a loss.

How come twrp I can't get going

[LineageOS 19.1] Reboots to fastboot despite successful install

Hey
couldn't find anything related to my situation so I decided to ask. Here it goes:
After having to wait an entire week to unlock the bootloader (really??) its finally unlocked and I decided to install LineageOS.
Got a Mi10T Lite, gauguin, M2007J17G. It managed to snuck in an update to something like August 2020 security level at some point but after unlocking it got reset, so I suppose it had Android 10 and MIUI 12(?).
Simple enough, have done that countless times before.
- Flashed recovery, format data/factory reset as explained in wiki
- adb sideloaded ROM (nightly builds 20220822 and 20220815) - both succeeded
After rebooting the devices enters the bootloader again.
The wiki never mentions behaviour like this and I couldn't find anything online.
Do I need to flash latest MIUI ROM again?
Any ideas what went wrong and how to solve this issue?
I unzipped the ROM and fastboot boot boot.img which just resulted in a reboot to fastboot again.
Any idea or, preferrably, a solution would be most welcome
Thanks in advance.

woelkchen said:
Hey
couldn't find anything related to my situation so I decided to ask. Here it goes:
After having to wait an entire week to unlock the bootloader (really??) its finally unlocked and I decided to install LineageOS.
Got a Mi10T Lite, gauguin, M2007J17G. It managed to snuck in an update to something like August 2020 security level at some point but after unlocking it got reset, so I suppose it had Android 10 and MIUI 12(?).
Simple enough, have done that countless times before.
- Flashed recovery, format data/factory reset as explained in wiki
- adb sideloaded ROM (nightly builds 20220822 and 20220815) - both succeeded
After rebooting the devices enters the bootloader again.
The wiki never mentions behaviour like this and I couldn't find anything online.
Do I need to flash latest MIUI ROM again?
Any ideas what went wrong and how to solve this issue?
I unzipped the ROM and fastboot boot boot.img which just resulted in a reboot to fastboot again.
Any idea or, preferrably, a solution would be most welcome
Thanks in advance.
Click to expand...
Click to collapse
Try to flash the last firmware or rom
V13.0.4.0.SJSMIXM
https://xiaomifirmwareupdater.com/firmware/gauguin/
https://xiaomirom.com/en/rom/mi-10t-lite-gauguin-global-fastboot-recovery-rom/
TWRP
https://androidfilehost.com/?w=files&flid=318225

Thx. Went ahead and did that which ofc solved the issue. Thx a lot

Hi, I have same issue. I installed lineage 19.1 2022-09-26 on Mi 10T lite, actually last nightly, and after succesfull installation, after reboot lineage doesnt start and i have just fastboot mode. I have lineage recovery installed, and if i try to install recovery-rom, i dont feel comfortable on installing fastboot-rom, i get error, just after 47% i get unknown signature and it ask if i want continue, if i choose yes continue, on device it says it cant downgrade so its stopped. I also deleted cache but it didnt help, im not very happy to format system partition, im worried to brick it. Should i format system partition? And how deal with missing signature when i try to push stock rom? should i allow it?

BolognaTown said:
Hi, I have same issue. I installed lineage 19.1 2022-09-26 on Mi 10T lite, actually last nightly, and after succesfull installation, after reboot lineage doesnt start and i have just fastboot mode. I have lineage recovery installed, and if i try to install recovery-rom, i dont feel comfortable on installing fastboot-rom, i get error, just after 47% i get unknown signature and it ask if i want continue, if i choose yes continue, on device it says it cant downgrade so its stopped. I also deleted cache but it didnt help, im not very happy to format system partition, im worried to brick it. Should i format system partition? And how deal with missing signature when i try to push stock rom? should i allow it?
Click to expand...
Click to collapse
Cant use LOS recovery for stock rom.
go back to Miui
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/

NOSS8 said:
Cant use LOS recovery for stock rom.
go back to Miui
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Click to expand...
Click to collapse
i didnt understand completely, should i find stock recovery and 'fastboot flash recovery stock-recovery.img'
or just using miflashtool without adding any stock recovery?

BolognaTown said:
i didnt understand completely, should i find stock recovery and 'fastboot flash recovery stock-recovery.img'
or just using miflashtool without adding any stock recovery?
Click to expand...
Click to collapse
Use Miflash and read the tutorial carefully.
Miflash=Fastboot rom

Thank you, i unbricked it, and i installed lineage. Great Job