Thanks! Got everything working and now I am running LOS 18.@vanish0104 Yes, flash latest build with MSMtools, unlock bootloader and then follow the instructions.
Thanks! Got everything working and now I am running LOS 18.@vanish0104 Yes, flash latest build with MSMtools, unlock bootloader and then follow the instructions.
I don't know if Verizon blocks the ability to flash images (but that wouldn't be surprising tbh), but if you are willing to flash, you most likely have nothing to lose trying. Worst case scenario you'll just have to flash stock via msmtools.Thinking about coming back to LOS, it and CM before it has always been a fav. I have one question before I do.
I keep seeing posts about Verizon, modem, A11, and not being able to flash LOS 18 (A11) yet.
I'm a Big Red Customer but aquired my device directly from 1+, am running A11 OB4, and am BL unlocked, have the latest Magisk canary, etc.
Since my device came from 1+, not VZW, I should be able to flash this. Correct?
Sent from my IN2025 using Tapatalk
---------- Post added at 10:21 PM ---------- Previous post was at 10:12 PM ----------
Oh, stupid question, too. [emoji16][emoji16]
Gapps included or do I need? If need, which? I'm a minimal Gapps person....
I've downloaded lineage-18.0-20201128_014340-UNOFFICIAL-instantnoodlep-gms.zip
Sent from my IN2025 using Tapatalk
I cannot reproduce this issue. The fingerprint setup doesn't mention the "fingerprint reader on the back", and works fine. Are you on latest build ?@LuK1337 I found another bug / problem. Adding a fingerprint during first install works fine but now adding a second one from security menu doesn't trigger the FP sensor. It asks to touch the FP on the back of the phone and doesn't trigger the front reader at all.
Not sure how Big Red can block me, it's not a Big Red device, just curious. My last device was their branded P3XL so I've been out of the custom scene for a bit. This one has been on a few of the custom kernels already. Guess I'll be taking it for a spin......I don't know if Verizon blocks the ability to flash images (but that wouldn't be surprising tbh), but if you are willing to flash, you most likely have nothing to lose trying. Worst case scenario you'll just have to flash stock via msmtools.
GMS builds contain GAPPS. Not minimal (quite a lot of apps for my taste), but you could disable them. Otherwise you might be able to flash your own GAPPS on the non-gms build with adb. I don't use GAPPS so I am not sure about the second one.
Google Pay works fine with MagiskHide enabled, have not tested it on LOS18. But i guess regardless of which OS you use, it should work as it works for me.Has anyone got Google pay to work? If not does root with Magisk hide allow it to work?
Thanks. Does not seem to work with Magisk hide enabled on all roms but I might give it a try.Google Pay works fine with MagiskHide enabled, have not tested it on LOS18. But i guess regardless of which OS you use, it should work as it works for me.
Have you tried changing your SIM card slot ? If you have no important data setup yet, you should also redownload and reflash the OSS11 build and check if everything works properly.Hello! This ROM seems to run really well. My only problem is unfortunately a big one. I started by flashing A11 with MSMtool and unlocked the bootloader. Then I copied and pasted the commands one at a time. Everything looked like it worked, except I have no mobile data, like my sim card isn't there. In fact it tells me to insert my sim card when I never took it out to begin with. This is on the latest Nov. 29th GSM build.
Any help is greatly appreciated.
Wrong thread. Thought this was lineage 17Hi All,
so when I am going through this, I am getting stuck. First thing I notice is that 'fastboot reboot fastboot' sends me into fastbootd, and when getting back to fastboot, it fails to boot into userspace? I'm thinking this is messing up the rest of the install process, as when I attempt to do 'fastboot flash system system.img' it fails in writing 'system' as partition not found.
Any help on where i go from here? I've tried this with LOs 17 and 18. OnePlus 8 Pro. Thanks!!
Yes, the stock AOSP fingerprint overlay doesn't align with instantnoodlep on LOS18 as well. It would most likely require a lot of work to replace it with a custom one (afaik).Hello. Hope this wasn't asked before. For LOS17 the fingerprint animation looks strange when it's used in other apps. Then you have two animation visibly oberlayed. Is that the same in LOS18?
I got it working bud, in Magisk manager just hide it and then follow these steps, if it works for you let us know.Thanks. Does not seem to work with Magisk hide enabled on all roms but I might give it a try.
I got it working bud, in Magisk manager just hide it and then follow these steps, if it works for you let us know.
Here are the steps –
First, go to the Google Play Store & download “Termux” which is an Android terminal emulator and Linux environment app.
Next, open Magisk Manager & swipe from the left side. From there, select the “Downloads” option.
There, you need to Install two Magisk Modules – Busybox for Android NDK & MagiskHide Props Config
You can either Install one Module & then reboot and then Install the other, or Install One, go back, install the second, and then reboot. Both will work.
Once the phone reboots, now we need to do one final thing which is the most important step. Before moving to the next step, just check if both the modules are shown as installed or not in Magisk Manager.
Open the Termux app & then type “su” and press Enter. This will grant Superuser Rights to the app.
Next, type “props” & press Enter. You will see a lot of options & numbers in front of them to choose from.
You need to choose the option that says “Edit Device Fingerprint”. It should be the Number “1” but just double check it on your device.
Enter that Number & press Enter.
Again, you’ll see some options & from there, choose the one that says “Pick a certified fingerprint”. This time, instead of numbers, you will see letters in front of each option like “f”, “v”, “s”, “b” etc. Enter the letter in front of the option (Pick a Certified Fingerprint) & press Enter.
Now, you’ll see a long list of various Smartphone companies so from here, you need to choose your phone’s company. For Example, if your phone is the Asus Zenfone Max Pro M1, choose “Asus”. Here also, you need to type the number in front of the company name & then press Enter.
Now, it’ll show you various devices from that company. If your device is there in the list, you’re good to go. Otherwise, you’re not lucky so you will have to wait for some other method.
Select the number in front of your Phone’s name & then press Enter.
Finally, it will ask if you want to continue. If you have followed everything above & selected the right options, write “y” & press Enter.
Finally, press “y” to reboot your device & press Enter. Now, your phone will reboot.
After all these steps, now you will see that in the Magisk Manager, it no longer says “false” in front of ctsProfile option. Also, in the play store, it’ll say “Device in Certified”. Hopefully, now you will also be able to use Payment apps like Google Pay on your device.
Good luck.