I have a OnePlus 7 Pro. I had LineageOS 17 (Android 10) with microG, magisk, and vanced on it running just fine for almost a year. I upgraded the Android version to 11 first (which LineageOS documentation says is a pre-requirement) then I upgraded to LineageOS 18, and everything seemed to work just fine. I can confirm that my recovery and wifi worked. A few days later I wanted to open Vanced YT, but it was no longer installed, then I noticed that magisk was no longer installed. So I installed it according to it's instructions which was basically using the app to patch the boot.img I got from the extracted files (from a payload-dumper) and then installed the produced magisk_patched-24200_Y0Qmv.img. Ever since then is my problem. I can no longer turn on my wifi, I no longer have recovery mode, and every time I turn on/reboot the device I am greeted with a "System UI Crashed" error message. I can hit ok and everything else seems to work as expected. With the exception to my wifi not being able to turn on What I've tried: - re-flashed the original boot.img - re-flashed the recovery image - uninstalled magisk - I tried re-flashing other images from the payload dump (modem.img, etc) the same way the LineageOS documentation said to upgrade and I get the following error

fastboot flash --slot=all modem modem.img
fastboot: error: Could not check if partition modem has slot all

I have no idea what that error means. Nothing changed. I'm still greeted with the same crash message. I still can't turn on my wifi. And I still can't boot into recovery mode. To make sure I'm clear, my question is; "Where should I go from here? What things can I tell you in order to help me get my wifi working again, and to fix this 'System UI Crashed' error message?"

According to the release notes in [Magisk v25 there was significant rewrite](https://topjohnwu.github.io/Magisk/changes.html) . The installation instructions advocated now say flashing Magisk in recovery is > This installation method is **deprecated and is maintained with minimum effort.** YOU HAVE BEEN WARNED! Instead they're pushing a new ["Patching Image"](https://topjohnwu.github.io/Magisk/install.html#patching-images) method. My device has a vbmeta and a ramdisk, but I don't understand what they mean with boot.img. What is that? I'm flashing LineageOS with Micro G, which has * lineage-18.1-20220703-microG-instantnoodlep.zip There is no boot.img there, and even in the zip there is no .img. So how do you get the patched method working with a custom ROM that isn't an .img? All the instructions say is > If your device has boot ramdisk, get a copy of the boot.img. But it doesn't say where to get the boot.img?

Version 0.2.29 of microG removed support for UnifiedNLP location provider back-ends (due to technical issues with newer Android versions), and instead built the functionality of some of these backends into microG. That includes the ability to scan for cell towers and WiFis in range and build a local database with them (formerly provided by the Déjà-Vu location providers) and the ability to query Mozilla Location Service (at least until that service was discontinued, but services with a compatible API would still work). Now I am wondering if there is a way to import an existing database into microG to be queried locally (there used to be modules for mobile and wifi networks that could do this). Format is not that important – I can convert that as needed, if needed. Unfortunately, since MicroG is a system app, I am somewhat reluctant to upgrading it just to find out, as I have never tried going back to an earlier version if something fails. The phone is my daily driver (i.e. production), not something I would want to carry out tests on. So – does microG provide a way to import cell/wifi databases?

**NOTE**: I see the following similar discussion here: https://android.stackexchange.com/questions/139248/how-to-restore-line-messages-from-titanium-backup Although that discussion offers a suggestion that might partially apply to what I want to ask here, it does not confirm the validity of that suggestion. Therefore, it does not actually answer my following question: I'm thinking of switching to microG, but a stumbling block is LINE Messenger. I know that it can run under microG, but I also know that it can't normally back up and restore LINE Messenger chat history without access to Google Drive. I have an idea of how I might be able to bypass this restriction, but I'm wondering if it actually would be feasible. Here's my idea ... (1) Under my current non-microG Android OS, take a backup of /data/data/jp.naver.line.android (2) Install microG, and then install LINE Messenger. (3) Restore the previously backed up jp.naver.line.android to /data/data under the microG OS. (4) Take periodic backups of /data/data/jp.naver.line.android as I use LINE under microG. (5) If i ever want to restore my LINE history under microG, repeat step 3 with the latest jp.naver.line.android backup. A variation might be to only back up and restore one or more appropriate sqlite databases that are resident within /data/data/jp.naver.line.android, instead of that entire directory tree. I'm willing to experiment with this approach, but before I do, I'm wondering whether anyone has tried anything like this with LINE Messenger under microG. Thank you in advance for any thoughts and suggestions. **UPDATE**: Thanks to @Andrew-T for the pointer to the other discussion that I missed, which indeed confirms that backup and restore for the database under /data/data/jp.naver.line.android can actually be done. I'm just wondering if anyone has actually gotten something like this to work specifically under microG. I'd like to switch to microG, but it would give me more confidence to take that step if anyone has already been able to do this in order to get full LINE functionality under that OS, including backup and restore. **FURTHER UPDATE**: That other discussion is more than 7 years old, and sadly, it turns out that the information is outdated. The /data/data/jp.naver.line.android/databases directory that is referred to in that article doesn't contain the database that is mentioned. Furthermore, I checked each and every other database in that directory, and none of them contain any chat history. I also checked all of the other files and directories under /data/data/jp.naver.line.android, and none of them contain any chat history, either. This is consistent with LINE's decision a while ago to stop allowing local-storage backup and to make Google Drive the only location to where chat history can be backed up and restored from. In conjunction with that decision, LINE seems to have gotten rid of all local chat history data from its device-resident databases. So, it looks like I'm out of luck regarding non-Google-based backup and restore for LINE. However, I'll keep this question open for a while longer, in case it turns out that someone knows of another way I can manage Android-based LINE backups and restores without Google being in the picture. **PS**: Hmm ... I wonder if it would be possible to create a fake "Google Drive" service which looks just like Google Drive to LINE, but which actually just manages a data store of my own. I'm going to look into this and report back if I have any luck with this idea.

I've got a Motorola Moto G4. Bootloader unlocked, TWRP installed, LineageOS installed, Open Gapps installed, non-rooted. Been using it for about a year. I want to try [LineageOS for microG](https://lineage.microg.org/) . I want to keep my current data/apps (including some end-user Google apps like their PDF viewer) as much as possible and migrate to microG, removing only the "core" Google stuff a user doesn't generally care about directly that will be replaced by microG. So, I'm following the dirty install process. --- I have none of the listed apps installed. I have tried removing Open Gapps, but it doesn't seem to work. Using the aroma installer to choose settings until the config at the end is "Include" with *no* apps listed, some Google apps are still installed (notably, the Play Store) after rebooting. The Open Gapps installer process also mentions removing existing/obsolete apps for only a short time, then moves to the next step "installing Gapps" which takes a long time. This seems to contradict the settings I gave it, namely to leave none installed, but is consistent with the fact that they don't seem to get uninstalled. I have also flashed https://github.com/CHEF-KOCH/Remove-Gapps to try to get rid of them, but some Gapps (like the Play Store) still survive. --- After any combination of attempts to follow the instructions and remove the Gapps, I flash the key migration zip followed by the lineage-microG.zip for my device (athene). I also make sure to wipe the Dalvik and cache partitions before rebooting. After all this, every time I reboot, my system is almost *exactly* like it was before I did anything: Google services installed (though the Play Store does not actually work, it's still there), the microG settings app is not installed, etc. A few things are broken (some notifications of apps crashing) but overall nothing noteworthy has happened. I've resorted to even wiping /system before a migration attempt, but even this achieves nothing. --- I got a partial success once by manually going through /system/app, /system/priv-app, and /data/app and removing anything that looked Google-y, then performing the migration. Upon rebooting, the microG settings app was present and the self-check section looked like it should look on a clean install, but the Play Store was still present. I don't know to what extent this migration was a success. I'm not familiar with the Android/Google ecosystem's insides and app politics, just the userland, so when I'm manually going around deleting files, I have little knowledge of what I'm doing, so I don't consider this attempt a success. --- Now that all the info has been laid out, could someone please help me cleanly perform the migration to lineage-microG, without excessive butchering of my system or leaving things that should not be left? Why does the dirty install procedure laid out by the lineage-microG team fail? Why do the Gapps removal tools fail? What exactly is necessary to correctly and cleanly migrate lineage to lineage-microG?

I understand the title sounds very basic. But I could not think of a way to describe my question in a short title. My question sort of comes in two parts. 1. Do I actually need to install microg and 2. Now that I have upgraded from LineageOS 17 with microg to LineageOS 18 without microg (by mistake), are there any gotchya's and clarify some instructions from microg's official instructions . Device is OnePlus 7 Pro, in case it matters. My particular case is, I recently upgraded from LOS 17 with microg to LOS 18 without microg by mistake. What I mean by that is, I'm still very green when it comes to flashing ROM's and other android development. I was more nervous about bricking my phone, I was following Lineage's upgrade instructions to the tee. **Here is my mistake**. I used Lineage's upgrade instructions link to the img to download and flash, and not microg's img download like I should have. At first, I honestly didn't notice the difference at all. Microg's settings app was still installed, most apps seemed to work. They popped up a warning or notification about not being able to work without google play services, but allowed me to hit "**Ok**" and continue to use the app. Just the other day, Lineage pushed out an OTA update, and I updated, then that changed. Now I can't use those apps at all anymore at all. They instantly close. So I went to searching for my issue, and basically it lead me to realize, I installed the LOS without microg. So I read their instructions to get an idea of what I should have done. Now I have questions. **Question 1**: The symptoms I'm describing, I do actually need to re-flash the microg img even though I have the microg settings app installed. Correct? I think the answer is "**Yes**". I just want to see if anyone can confirm this or tell me maybe another or better way, since I'm dealing with a non-typical issue. **Question 2**: If question 1 is "Yes" and I do need to re-flash with the microg lineage img. Then it's really a series of questions clarifying microg's installation instructions. Because I'm a newbie and don't understand everything as a more experienced android dev would. - Do I or should I uninstall the microg settings app first? - Since I just OTA updated, I think according to microg's install instructions, I need to wait for another release before trying to flash the microg lineage img, correct? Or would rolling back a version be a better option? - In their *"Migration from LineageOS"* section, I noticed that they mentioned *"...you can't directely flash our ROM on top of the official LineageOS while keeping your data..."*. So I can't keep my personal data, or installed apps, pictures, music, etc? Is this correct? If so, is there any way to back it up, and re-install after I re-flash the microg img? - In their install docs, they also say *"If you have installed unofficial builds of"*, and in that list, I think I have almost all of them. But I don't think they are *"unofficial"*. F-Droid should be from their github, and all the rest I think were installed from my last microg installation prior to the upgrade I just made. I honestly don't know if they technically still installed or not given my apps crashing which need google play services. As I mentioned the microg settings app is still there. I don't even know how to verify this. I will say, after having these troubles and poking around, I have noticed that they mention in the *"Post-install"* section that by default MozillaNlpBackend and NominatimNlpBackend are both plugins which are installed by default. And *"If you want to use these plugins, go to microG Settings -> UnifiedNlp Settings, configure and enable both"*. Even though I have the mocroG settings app installed. That *"UnifiedNlp Settings"* is just not there in mine. So what do you guys think? Does it sound like this is my issue? That I don't have microg installed even though the settings app is there? And are there any special things I need to do before trying to re-flash the microg lineage img?

I am referring to the topic How to decrypt Island / Work profile and Parallel Apps user in TWRP? After installing a work profile (via Shelter) I wanted to install a backup of my LineageOS 17.1 via TWRP. My backup did not work and resulted in a bootloop straight into TWRP again: failed to decrypt user 10. My problem is: I do not know the user 10 password and I cannot start Android again. I cannot put in the password in TWRP or access the settings like advised in the answer of firelord… stupid me. Does anybody have a suggestion? Is there a way to wipe the user 10? Any help would greatly appreciated.

I am trying to work out whether it would be possible to use a custom rom such as LineageOS without flashing Gapps rather than using the LineageOS+MicroG as an option. The basic requirement is to be able move away from the Big Brother. I have read that LineageOS+MicroG option is a good one but it creates security risks because of the need to do signature spoofing. I am just a newbie here and wondering whether it would be possible to install a downloaded apk directly on LineageOS? If yes, would like to find more details on this process. If no, are there any solutions to this problem or we just have to put up with the Big Brother until Linux phones make inroads into this space? Many thanks EDIT: Thanks for all those who provided valuable comments/suggestions. I decided to try out LineageOS for MicroG and found it quite a painless process. The phone works great without the Big Brother tracking me. I also run DNS66 (from F-Droid Store) which stops ads on some apps. Overall, pretty much impressed with the outcome. Thanks again.

I've recently bought a Xiaomi Redmi Note 4 with the intention of installing the LineageOS + microG distribution. When reviewing and researching which apps I need to install, I realized that at least one of the apps I need, which is a two-factor app for my credit card , requires the phone to be able to pass the (new) Safety Net check that Google added to its Android services. I'm currently waiting for Xiaomi to finish the countdown allowing me to unlock the bootloader. In the meantime, can anyone tell me whether or not I can use apps requiring Safety Net on that ROM? Infos I found when googling are unclear and contradict each other (1 , 2 , 3 , 4 , 5 ). I'm not currently planning to root the device or use XPosed or anything similar, and I'm fine with possibly having to relock the bootloader. From what I've seen, the LineageOS + microG distribution includes something called the DroidGuard helper, which emulates or implements the Safety Net features, but it seems to me to depend on the device, the LineageOS version (I'm planning to install 15.1) and patch level, and the whims of Google whether or not the checks pass. In short, the question I have is: - On a Xiaomi Redmi Note 4, running LineageOS + microG as offered on the project webpage, will I be able to use an two-factor credit card app like I linked above that requires Safety Net?

I'm facing a tricky scenario, sometime back I decided to discontinue using Google Play Services in favour of an open source alternative - microG due to constant problems and crashing of several Google applications on my device. As Google launched Google Play Protect 1 feature (on all Android devices running Google Play Services 11 or later), this seems to be missing or at least I'm not sure how to use it (i.e enable or disable it) with microG. With a device running Google Play Services, one can easily control it by navigating to: Settings ➡ Google ➡ Security ➡ Google Play Protect I wish to be able to control this feature on microG so I can control/disable constant false positive notifications about my installed applications being harmful, and also to have my applications regularly scanned. Is there way to control "Play Protect" on a device running microG, or at least to integrate via another means, perhaps an Xposed module? ---------- 1 > Google Play Protect is a feature that is, essentially, an evolution of > the company’s “Verify Apps” service that was rolled out to Android > many years ago. The feature, which will be enabled by default on all > Android devices, is meant to be a real-time malware scanner that will > scan every installed or about-to-be installed app and inform users in > case there’s something amiss.