Database Info

Lineage OS 14.1 Release 1 (uploaded January 17 1025pm eastern)

Release 1 is posted.
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
******************************Start of dev stuff************************************************************
kernel sources based off of LG K10 devs msm8916 caf kernel sources (since its basically the same device) here:
https://github.com/touchpro/android_kernel_lge_msm8916
all the device and vendor trees are based off of teamregular's/LG K10 devs work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos14
vendor: https://github.com/touchpro/android_vendor_lge-lineageos14.1
*********************End of dev stuff*********************************************************************
Feel free to create other custom roms based on the trees above!
I would recommend using my TWRP 3.2.0-0 here to flash it: https://androidforums.com/threads/update-twrp-3-2-0-built-from-source-12-8-17.1103219/
what works:
everything as far as I can tell
The rom zip:
https://androidfilehost.com/?fid=746010030569947653
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 7.1)
THIS DOESNT COME STOCK WITH SU!
Download it here: https://download.lineageos.org/extras
(choose the option for su (arm) and 14.1)
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!

beta 2 uploaded
dt2w works, bluetooth audio works, camcorder works.
wifi still partially broke and is a wip. after that its on to lineage os 15 for the h631

wifi works now and the end? of lineage 14.1 dev is here. everything seems to work now
release 1 is posted in the op.

Awesome work! I've finally got me a full featured daily driver

I still got my OG Stylo lying around somewhere. Guess I'll give this ROM a try...

After attempting to reboot after installing, I got a "Kernel Crash!" error. Now my Wi-Fi won't work after restoring a Nandroid backup. Good thing the OG Stylo isn't my primary phone, anymore.
EDIT: I just realized Bluetooth is busted, too.
EDIT 2: After reading from sources outside of XDA, the firmware should have definitely been on v20k before flashing this. Oh well. I might check into attempting to fix the issues, one day.
But ever since I moved on to the OnePlus 5, I only use the OG Stylo as an alarm clock. As long as that still functions, at least it won't end up in the dumpster.

Gave this ROM a go. VERY pleased! WiFi had a hiccup but now working. I can connect to Bluetooth but can not hear audio. Any others come across this? I'm on the metro version of the Stylo.
Thanks in advance.
Z
Sent from my LG-H631 using Tapatalk

I have a MS631 (MetroPCS).
S/W : MS63120p
Is it possible to install and any plan to post Official Release (14.1 or 15 later)?
Thanks..

This is cool... hoping to get a Google-less minimal fernsprecher going, but this time (compared to your other 14.1 build) I can't see any providers-- just 'error while searching for networks.' Now I'm guessing the reason is the same in both cases-- I started from wrong official ROM. Can anyone point to a 63120k kdz? All the old links I found yet are dead
ed: Tried to prove to myself that a kdz was even useful. I have a few wrong kdz sitting around still-- 10j, 20b, 20l. LG Flash Tool wouldn't actually change anything, ever, no matter what. ("Consult your system administrator". Well, he's me... baka.) And LGUP looked like it was doing great the first time, right up until it gave me back a shiny brick (QHSUSB__BULK), so ...maybe later?
:: phasepalm ::
ed-2: found https://lg-firmwares.com/lg-ms631-firmwares/ so now all I have to do is get QFIL to do anything.

I love this OS. I removed the Nexus launcher and installed the new pixel 2 launcher in its place though. Every now and again I have to disconnect and reconnect Bluetooth. But that's not really a problem for me. WiFi sometimes drops but reconnect. I can't wait for the new lineage OS.

Any update?

pnaralove said:
Any update?
Click to expand...
Click to collapse
Nope, because the OP's phone was destroyed.
On another note: I was also able to get my OG Stylo up and running again with LG Bridge yesterday, with the latest official update (Marshmallow). I might try this ROM again, one day.

Revenant Ghost said:
Nope, because the OP's phone was destroyed.
On another note: I was also able to get my OG Stylo up and running again with LG Bridge yesterday, with the latest official update (Marshmallow). I might try this ROM again, one day.
Click to expand...
Click to collapse
Thank you for the reponse
Please let me know how it is after you try this ROM.

won't boot all the way through, logcat without complete boo
whoshotjr2006 said:
Release 1 is posted.
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
******************************Start of dev stuff************************************************************
kernel sources based off of LG K10 devs msm8916 caf kernel sources (since its basically the same device) here:
https://github.com/touchpro/android_kernel_lge_msm8916
all the device and vendor trees are based off of teamregular's/LG K10 devs work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos14
vendor: https://github.com/touchpro/android_vendor_lge-lineageos14.1
*********************End of dev stuff*********************************************************************
Feel free to create other custom roms based on the trees above!
I would recommend using my TWRP 3.2.0-0 here to flash it: https://androidforums.com/threads/update-twrp-3-2-0-built-from-source-12-8-17.1103219/
what works:
everything as far as I can tell
The rom zip:
https://androidfilehost.com/?fid=746010030569947653
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 7.1)
THIS DOESNT COME STOCK WITH SU!
Download it here: https://download.lineageos.org/extras
(choose the option for su (arm) and 14.1)
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!
Click to expand...
Click to collapse
Hello, everything seems to be fine but it won't boot all the way through. Also I am still a noob and am wondering how to get a logcat without being able to get all the way into the operating system? Any help would be appreciated

whoshotjr2006 said:
Release 1 is posted.
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
******************************Start of dev stuff************************************************************
kernel sources based off of LG K10 devs msm8916 caf kernel sources (since its basically the same device) here:
https://github.com/touchpro/android_kernel_lge_msm8916
all the device and vendor trees are based off of teamregular's/LG K10 devs work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos14
vendor: https://github.com/touchpro/android_vendor_lge-lineageos14.1
*********************End of dev stuff*********************************************************************
Feel free to create other custom roms based on the trees above!
I would recommend using my TWRP 3.2.0-0 here to flash it: https://androidforums.com/threads/update-twrp-3-2-0-built-from-source-12-8-17.1103219/
what works:
everything as far as I can tell
The rom zip:
https://androidfilehost.com/?fid=746010030569947653
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 7.1)
THIS DOESNT COME STOCK WITH SU!
Download it here: https://download.lineageos.org/extras
(choose the option for su (arm) and 14.1)
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!
Click to expand...
Click to collapse
hi, me again.. I finally got my phone back to totally stock from the LG Bridge. How do I get the v20 K that you were sitting on to try and get lineage on my phone now at this point. Thanks in advance

gameplayerdo2 said:
hi, me again.. I finally got my phone back to totally stock from the LG Bridge. How do I get the v20 K that you were sitting on to try and get lineage on my phone now at this point. Thanks in advance
Click to expand...
Click to collapse
Like I said, I finally found https://lg-firmwares.com/lg-ms631-firmwares/ and v20k is on there but no promises unless you can find the known good MD5 hash somewhere. I couldn't just try it because again, this ms631 is bricked in 9008-mode.

derpendicular said:
Like I said, I finally found https://lg-firmwares.com/lg-ms631-firmwares/ and v20k is on there but no promises unless you can find the known good MD5 hash somewhere. I couldn't just try it because again, this ms631 is bricked in 9008-mode.
Click to expand...
Click to collapse
Hey there I got it. What I did was I hooked up to LG Bridge and let LG do the repair from the upgrade repair button and it got my phone back to square one which was fine. From there i unlocked the bootloader and booted from TWRP 2.8.7.1 image file and then once inside TWRP I installed version TWRP 3.2.0-0 recovery from the zip file. At that point I then was able to do an advanced wipe and wipe out the system and then do the lineage install from there. Once that worked I wiped it out and installed CyanogenMod just to see if it will go on as well and it did. So I went back and wipe that out and put the lineage OS back on there with the opengapps and it's running flawlessly! I also installed magisk to root it and everything is running fine. The only thing I miss from the LG part of the software was the knock on knock off feature. And I downloaded a tap on tap off app for that but you can't use any other locks with it. but I'm good, and thanks! Because I hated that stock operating system with all the bloatware even though MetroPCS didn't have as much garbage as the T-Mobile or other versions but still now I can control Play Store and everything else. I in fact use APK pure to get most of my apps if I can find the software there.

Hey I got my LG g Stylo and might use it again with lineage on it. I need to understand you're flashing a nougat custom rom over a mm stock room and it works? Also, I have 20o and in reading I see 20k is the requirement? Hope to hear feedback, thanks in advance. And can anybody tell me how they got twrp 3.0.2 on the stylo? I can't seem to do it with an unlocked bootloader via adb.

elwhiteboy01 said:
I need to understand you're flashing a nougat custom rom over a mm stock room and it works? Also, I have 20o and in reading I see 20k is the requirement? Hope to hear feedback, thanks in advance. And can anybody tell me how they got twrp 3.0.2 on the stylo? I can't seem to do it with an unlocked bootloader via adb.
Click to expand...
Click to collapse
Your best bet is (very likely) to back up stuff and wipe it all out. I use SMS Backup Restore, manually export contacts, copy the files to SD, etc. Then to answer your other question-- root using apk from Kingroot.net which works but it loses root every time you reboot. So before you do, you can use Flashify to flash TWRP onto recovery, also run TitaniumBackup once and put everything on SD card. Then with TWRP running you could install SuperSU zip onto the stock rom and it actually sticks, but you would (make yet another backup and) wipe the phone before starting fresh with Lineage and then restoring your stuff piecewise. That was last year, though, might have forgotten something. Like it's hard to remember but I *think* you can skip the Kingroot & Flashify routine altogether, just reboot to fastboot and on the computer 'fastboot boot twrp-x.x.x.x.img' to boot it once-- even though it won't flash it directly. Then 'adb push twrp-x.x.x.x.img /sdcard' and then inside TWRP, flash it using [Install Image] under [Install] instead of the usual zip file. HTH

derpendicular said:
Your best bet is (very likely) to back up stuff and wipe it all out. I use SMS Backup Restore, manually export contacts, copy the files to SD, etc. Then to answer your other question-- root using apk from Kingroot.net which works but it loses root every time you reboot. So before you do, you can use Flashify to flash TWRP onto recovery, also run TitaniumBackup once and put everything on SD card. Then with TWRP running you could install SuperSU zip onto the stock rom and it actually sticks, but you would (make yet another backup and) wipe the phone before starting fresh with Lineage and then restoring your stuff piecewise. That was last year, though, might have forgotten something. Like it's hard to remember but I *think* you can skip the Kingroot & Flashify routine altogether, just reboot to fastboot and on the computer 'fastboot boot twrp-x.x.x.x.img' to boot it once-- even though it won't flash it directly. Then 'adb push twrp-x.x.x.x.img /sdcard' and then inside TWRP, flash it using [Install Image] under [Install] instead of the usual zip file. HTH
Click to expand...
Click to collapse
The phone is bricked now. I did a fastboot boot twrp and installed magisk zip. Then installed flashify and flashed twrp image. Then formatted data and installed the lineage os and it didn't go through. I was in a hurry so I didn't backup the stock ROM. And so I pulled the battery and put it in download mode and flashed kdz. And when it finished the screen went black and shows no signs of life no matter what I do.

How to properly flash tulip with twrp and ota on stock?

Hello there.
I'm using tulip for few months now. One of first things that I've done, have been unlocking device, rooting it and put stock rom with root access on it. So far, so good. I did not encounter any serious glitches etc, but now I would like to finally upgrade miui to 11 (currently having 10.3).
And there's my problem. I would love to dodge making clean installation (wipe data etc) and I do not wish to risk to bootlooping my phone. I've read on some threads (older ones, but still) that you cannot simply install ota update in system, because due to changed recovery (I do have TWRP instead of fabric one) you will cause bootloop. I've tried alternative method of installing zip BY twrp, but program says, that it encounter a problem called "package expects build fingerprint (...) of tulip 0/PKQ1.180904.001/V10.3.2.0.PEKMIXM or PKQ1.180804.001/V11.0.2.0; this device has omni_tulip/tulip:8.1.0/OPM8.181105.002/1", and then sait, that in had error 7.
Is it simply wrong rom being installed and I have to choose something that is being named the same way and supports ota, or is there a way to go more swiftly through this process? If so and I should pick rom with ota - what to choose? I like deep level customisation, but compatibility with google store, being able to use store, payments and paid apps, instead of "opening them" by some lucky patchers kind of apps.
OR MAYBE I just need to change recovery from TWRP to something different - like PBRP f.e.? Just like this thread says - https://forum.xda-developers.com/re...how-to-setup-official-miui-breeaking-t3893703

Just a quick update - changing twrp to pbrp does not change anything in upgrade process - still get the same error, now just without telling me, which version do I have.
Also, what's interesting, apparently twrp said to me that I do have android 8.1, but "about phone" in system says, that its android 9 (9PKQ1.180904.001 to be exact).
That's werid, because everywhere I check, phone says "android 9" as a version of it.

Have you tried wiping system and installing?

Nitin Rai said:
Have you tried wiping system and installing?
Click to expand...
Click to collapse
Not yet. I've found method of flashing via PBRB with usage of downloaded file and one option check, but I'm not gonna try it, unless I do a backup of my apps. If that won't work, I'll perform a clean instalation and choose rom that supports ota.

well, I've tried to do this with the method, that I've described before, but this did not ended successfully. I'll look for rom with ota update possibility and then install it most likely. Apps had backup, so I lost almost nothing.

It worked. I had to download bigger patch (1.7 GB, instead of circa 700 MB, that I've tried before), I also had to use method described here -> https://c.mi.com/thread-1782169-1-1.html (pitch black recovery, instead of twrp + one tweak in options). Start after flash was very long (it took like 10 minutes or so), but it booted successfully in the end. Not sure which rom I do have after all, but as far as I remember it was so close to stock, as possible (with only few extra options and tweaks). So yea, it just works.

Auto OTA update on a rooted one plus 7 pro with magisk and TWRP?

Hello! I have had my One plus 7 pro international running for months now, rooted, following this guide https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368. I had the OTA update notification for quite some time now, but I ignored it because I was lazy. A few weeks ago my phone must have auto updated however, as I started noticing banner ads again that adaway usually blocked, and I have had a few other minor issues like GPS taking longer to connect or find where I am, wifi disconnects, and google not understanding what it usually does. Phone still works just fine, just minor issues I didn't really experience before.
I would like to completely reset the phone to clean it up, and re root and setup TWRP again, but im not sure how to safely do that since my phone was updated improperly (automatically). I have magisk still installed, but the modules dont seem to be working properly. Rebooting to recovery will reboot me to one plus recovery instead of twrp. When I restart is still says my boot loader is unlocked, and some apps (like chase mobile app) still say my phone is rooted. Oxygen updater says im up to date on OxygenOS 10.0.3.gm21aa.
What would be the best option for me to clean everything up, get my root modules working again, and have the phone fully up to date and stable? Any information would be greatly appreciated.

follow the same steps you followed first time. Boot to TWRP flash magisk, No need to factory reset. Flash twrp again if you want and reboot to system

[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.

Question Bootloop after 12.5.5.0 OTA (with OrangeFox recovery)

Unfortunately, I have a problem. My phone was on the power cord overnight and pulled the latest update (EEA 12.5.5.0 Enhanced). It was then booted into OrangeFox (OrangeFox recovery with OTA support) and waited for my OK. I didn't think anything of it and didn't make a backup either, as I assumed that everything would go smoothly like the last update.
The update then went on, but there was probably an error, because now I have a bootloop (yellow Poco lettering for about 2 seconds). I can't use an old backup because I'm abroad right now and I don't want to lose the apps I've already set up (pandemic, tracking apps, certificates, ...).
Does anyone have a quick trick or the latest full ROM that I can just iron over or any other good quick idea? Change bootloader slot or other options? OrangeRecovery and Fastboot are still accessible. Now I only have ADB/Fastboot on my work laptop, but I still can't list the device with adb devices. I guess I still need to install the Xiaomi driver for it, but that should be the minor issue.
Update: I am currently downloading the different ROM versions (fastboot, recovery and incremental update), just in case they are needed.

OTA for the rom and using ofox? hmm it's not supported unless you will flash stock rom maybe. I don't know much more. Correct me if im wrong.

OTA works very well with orangefox and AICP 16.1...