When will we get Lineage OS 15, since the nexus 4 already got it, which has very similar specs, but not the same.
Can you get lineage is 14 for android nougat with gapps?
Sent from my E5823 using Tapatalk
mgdorbit said:
Can you get lineage is 14 for android nougat with gapps?
Sent from my E5823 using Tapatalk
Click to expand...
Click to collapse
Not sure exactly what you're asking. But Lineage 14.1 is available for the N7 and you flash gapps separately.
the_gunner said:
Not sure exactly what you're asking. But Lineage 14.1 is available for the N7 and you flash gapps separately.
Click to expand...
Click to collapse
Sorry, I was being lazy, I meant nougat. I see you can get it as a nightly build, however I'm reading Netflix doesn't work, so that's a no go for installing it for me
Sent from my E5823 using Tapatalk
I believe there are older versions of Netflix that will work with some builds of Lineage. I had it working at one time, but after updating to a recent nightly, it is broken.
About Netflix, you can use Magisk which can hide itself and you will be able to install Netflix (and al other protected apps)
About Oreo, I hope we get it soon, I have Oreo on my Nexus 5X and it's great
Ja_som said:
About Netflix, you can use Magisk which can hide itself and you will be able to install Netflix (and al other protected apps)
About Oreo, I hope we get it soon, I have Oreo on my Nexus 5X and it's great
Click to expand...
Click to collapse
Been a while since I've flashed anything, last time was with HD2. So I need to unlock bootloader on my N7 and then install Magisk, then install lineage OS? So then Netflix app will still work with latest version from the play store?
Sent from my E5823 using Tapatalk
mgdorbit said:
Been a while since I've flashed anything, last time was with HD2. So I need to unlock bootloader on my N7 and then install Magisk, then install lineage OS? So then Netflix app will still work with latest version from the play store?
Sent from my E5823 using Tapatalk
Click to expand...
Click to collapse
First LOS, then Magisk.
Personally, I don't use Netflix, it is not fully available in my country. AFAIK, it was not possible to install it from the Play Store when device was rooted, or BL was unlocked (not sure which one), but with Magisk I can install it, I can also open it, but as I said, I don't pay it, so I can't do nothing more, and AFAIK t should work.
It's WIP, just wait.
Related
Is there a good updated guide to root the robin?
Sent from my Moto G4 Plus using Tapatalk
I recently did, its still the same as it was before. Nothing has changed.
Only difference is it more or less depends on which tool you want to use to root. I personally used Magisk v14.0
This video does a good job. As I said I would replace SuperSU with Magisk
https://www.youtube.com/watch?v=DKyEhn9clNw
Good luck!
/root said:
I recently did, its still the same as it was before. Nothing has changed.
Only difference is it more or less depends on which tool you want to use to root. I personally used Magisk v14.0
This video does a good job. As I said I would replace SuperSU with Magisk
https://www.youtube.com/watch?v=DKyEhn9clNw
Good luck!
Click to expand...
Click to collapse
Thank you! A question, Does Android pay and the cloud storage works after root?
Sent from my Moto G4 Plus using Tapatalk
maurogg84 said:
Thank you! A question, Does Android pay and the cloud storage works after root?
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
I stopped using nextbit cloud storage after they announced the end of life for device. I am not sure they will keep the cloud storage running anyway.
Android Pay not available in my region but Magisk lets you hide it from detection and it does pass the SafetyNet so Android Pay should work.
Banking apps which detected root can't detect it with Magisk Hide. So I am able to use those apps despite having the root.
maurogg84 said:
Thank you! A question, Does Android pay and the cloud storage works after root?
Click to expand...
Click to collapse
Android Pay works fine with Magisk. Both with rooted stock and custom ROMs. At least in my experience.
Sent from my Robin using XDA Labs
Good day, I have a little problem with my 5x, when I long click on the power button, the power menu doesn't appear. Instead, I go to the boot animation and it just restarts, without showing the Google's logo.
Note that I use LineageOS 14.1, ElementalX 4.14, Magisk v14.0 and substratum with Flux (white) theme. I uninstalled XPosed but there are no significant differences, it's just about the same.
Anyone could give me a feedback? Thank you!
Skailog said:
Good day, I have a little problem with my 5x, when I long click on the power button, the power menu doesn't appear. Instead, I go to the boot animation and it just restarts, without showing the Google's logo.
Note that I use LineageOS 14.1, ElementalX 4.14, Magisk v14.0 and substratum with Flux (white) theme. I uninstalled XPosed but there are no significant differences, it's just about the same.
Anyone could give me a feedback? Thank you!
Click to expand...
Click to collapse
Uninstall the theme and see if it still reboots randomly.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Uninstall the theme and see if it still reboots randomly.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
No, the device reboots still. But it is not random, actually it only happen when I press and hold the power button.
I will try to deactivate Magisk
Skailog said:
No, the device reboots still. But it is not random, actually it only happen when I press and hold the power button.
I will try to deactivate Magisk
Click to expand...
Click to collapse
Hmm. Reinstall the vendor image that matches the monthly security date that your rom is based on. If that doesn't help, you'll probably have to clean flash the rom.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Hmm. Reinstall the vendor image that matches the monthly security date that your rom is based on. If that doesn't help, you'll probably have to clean flash the rom.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Okay, so I did a new clean install, but the problem is still here. Is it possible that this occurs after installing a new application? I have installed a few and the problem showed after that
Skailog said:
Okay, so I did a new clean install, but the problem is still here. Is it possible that this occurs after installing a new application? I have installed a few and the problem showed after that
Click to expand...
Click to collapse
Yes. You can install your apps one at a time until you see a culprit.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Yes. You can install your apps one at a time until you see a culprit.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Roger Roger, thanks for your help!
Magisk v14.0 cause a lot of bug try 13.3 is better
Sofiane omega said:
Magisk v14.0 cause a lot of bug try 13.3 is better
Click to expand...
Click to collapse
Yeah. I have tried with Magisk v13.3 (and so I uninstalled v14) but the same problem occurs.
I will try with a new nightly of LineageOS asap and report here if ever I find a solution.
Skailog said:
Yeah. I have tried with Magisk v13.3 (and so I uninstalled v14) but the same problem occurs.
I will try with a new nightly of LineageOS asap and report here if ever I find a solution.
Click to expand...
Click to collapse
try paranoid android 7.3.0 are more better than LOS 14.1
substratum OMS support,Magisk 13.3 and BlueBorne Patch
Anyone have Netflix working on 8.1 beta? I had it before the beta and now it's telling me I have an incompatible device.
dchurch85 said:
Anyone have Netflix working on 8.1 beta? I had it before the beta and now it's telling me I have an incompatible device.
Click to expand...
Click to collapse
Of course. The only way now is to lock the bootloader or download from apk mirror. In the future, passing safetynet with a custom kernel or Magisk/autohide will work
Golf c said:
Of course. The only way now is to lock the bootloader or download from apk mirror. In the future, passing safetynet with a custom kernel or Magisk/autohide will work
Click to expand...
Click to collapse
Interesting. Didn't think the bootloader would affect it. Once we can get safetynet, I'll unlock again.
dchurch85 said:
Interesting. Didn't think the bootloader would affect it. Once we can get safetynet, I'll unlock again.
Click to expand...
Click to collapse
I'm running a custom kernel that passes safetynet on 8.0. The easiest way is to download Netflix from Apk mirror. That way you can stay unlocked
dchurch85 said:
Anyone have Netflix working on 8.1 beta? I had it before the beta and now it's telling me I have an incompatible device.
Click to expand...
Click to collapse
Mine is working but I installed​ Netflix after I updated too 8.1.
dchurch85 said:
Anyone have Netflix working on 8.1 beta? I had it before the beta and now it's telling me I have an incompatible device.
Click to expand...
Click to collapse
Yep works fine for me. I just finished all of Manhunt Unibomber on Netflix on 8.1.
Sent from my Pixel 2 XL using Tapatalk
Golf c said:
Of course. The only way now is to lock the bootloader or download from apk mirror. In the future, passing safetynet with a custom kernel or Magisk/autohide will work
Click to expand...
Click to collapse
You can download the APK directly from Netflix website in the help section.
toknitup420 said:
You can download the APK directly from Netflix website in the help section.
Click to expand...
Click to collapse
Thats funny. They won't let you do it from the play store, but they give you the workaround right from their website. Lol
I haven't had any issues with Netflix.
I'm on stock Oreo with Magisk, custom Kernel, Android Pay working, v4a working, custom recovery, CF+lumen, and a few others.
Can I accomplish that on Pie right now?
I was updating a bunch of magisk stuff and messed up the system today, so I need a clean install.
Working Bluetooth reliably is a must.
Thanks!
Sent from my Pixel XL using Tapatalk
MeetFace said:
I'm on stock Oreo with Magisk, custom Kernel, Android Pay working, v4a working, custom recovery, CF+lumen, and a few others.
Can I accomplish that on Pie right now?
I was updating a bunch of magisk stuff and messed up the system today, so I need a clean install.
Working Bluetooth reliably is a must.
Thanks!
Click to expand...
Click to collapse
Yup. Pie works beautifully my friend. I've had v4a, Android pay working , of course a custom kernel and it's great.
Phalanx7621 said:
Yup. Pie works beautifully my friend. I've had v4a, Android pay working , of course a custom kernel and it's great.
Click to expand...
Click to collapse
Have you followed any tutorials that would be helpful? I know magisk and v4a and kernels can be finnicky if you go in the wrong order.
NM, here it is =]
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3825866
Sent from my Pixel XL using Tapatalk
@Phalanx7621 I'm having trouble installing v4a. I've got benzo with Magisk and Elemental atm. When in TWRP it says "Error 2" when installing the v4a zip I got from the Zackptg5 website. Any ideas?
MeetFace said:
@Phalanx7621 I'm having trouble installing v4a. I've got benzo with Magisk and Elemental atm. When in TWRP it says "Error 2" when installing the v4a zip I got from the Zackptg5 website. Any ideas?
Click to expand...
Click to collapse
Yeah you don't install it via a zip in recovery, it's a Magisk Module you install through Magisk.
Interesting. I guess that's a Pie thing. There's a zip created specifically for Magisk that has been troubleshot with Pixel in mind. Worked great on Oreo.
I'll try that, thanks!
Phalanx7621 said:
Yeah you don't install it via a zip in recovery, it's a Magisk Module you install through Magisk.
Click to expand...
Click to collapse
Sent from my Pixel XL using Tapatalk
MeetFace said:
Interesting. I guess that's a Pie thing. There's a zip created specifically for Magisk that has been troubleshot with Pixel in mind. Worked great on Oreo.
I'll try that, thanks!
Click to expand...
Click to collapse
Yup. Make sure you install the viper called FX not the other one.
Did you have to install. Any other mods? AML, Notification Helper Remover, etc?
Sent from my Pixel XL using Tapatalk
MeetFace said:
Did you have to install. Any other mods? AML, Notification Helper Remover, etc?
Click to expand...
Click to collapse
Not sure haven't used those.
I'll be that guy and say that battery life on pie sucks major
Yeah, my battery life has been miserable thus far. 3 hrs SOT, pretty bad.
Sent from my Pixel XL using Tapatalk
Anyone try it on there pixel 2 xl yet?
Was just asking if anyone seen if it's worth the time to flash it
WoZzYDoesitbest said:
Anyone try it on there pixel 2 xl yet?
Was just asking if anyone seen if it's worth the time to flash it
Click to expand...
Click to collapse
Works just fine on the P2XL. Been on it over a day now, no problems that I've noticed since then :good:
WoZzYDoesitbest said:
Anyone try it on there pixel 2 xl yet?
Was just asking if anyone seen if it's worth the time to flash it
Click to expand...
Click to collapse
Google pay is working fine with Magisk hide after the update...
Badger50 said:
Works just fine on the P2XL. Been on it over a day now, no problems that I've noticed since then :good:
Click to expand...
Click to collapse
sidhg said:
Google pay is working fine with Magisk hide after the update...
Click to expand...
Click to collapse
Awesome how are the modules working?
Thanka for the feedback guys
WoZzYDoesitbest said:
Awesome how are the modules working?
Thanka for the feedback guys
Click to expand...
Click to collapse
The modules I use are working fine, and they've all been updated by their specific developers. However, YMMV depending on what modules you have questions about :good:
sidhg said:
Google pay is working fine with Magisk hide after the update...
Click to expand...
Click to collapse
I don't really understand what's happening on my end then, I have the latest Canary Magisk version and I'm hiding Google Pay and Google Play Services, but I still get a message about the phone being rooted.
Problem here is that if I hide Google Pay in Magisk 19.0 it doesn't work- sticks at the Google logo. If I don't hide it, it doesn't work because of root/unlocked bootloader, so I'm a bit stuck in the middle.
Tried on rooted stock- same problem. Tried with elementalx kernel- just the same. Any ideas (pixel 2 btw)?
1959best said:
Problem here is that if I hide Google Pay in Magisk 19.0 it doesn't work- sticks at the Google logo. If I don't hide it, it doesn't work because of root/unlocked bootloader, so I'm a bit stuck in the middle.
Tried on rooted stock- same problem. Tried with elementalx kernel- just the same. Any ideas (pixel 2 btw)?
Click to expand...
Click to collapse
I feel your pain and that's exactly why i went straight back to pure stock at least until magisk is fully functional again WITHOUT any hiccups.
mbrian27 said:
I don't really understand what's happening on my end then, I have the latest Canary Magisk version and I'm hiding Google Pay and Google Play Services, but I still get a message about the phone being rooted.
Click to expand...
Click to collapse
I'm using the beta version.. it's different from the canary.
Try installing beta.
sidhg said:
Google pay is working fine with Magisk hide after the update...
Click to expand...
Click to collapse
I don't believe you, I'm on March update with pixel 2xl magisk and unlocked bootloader with TWRP installed. Safety net passes but Google pay doesn't work. I tried magisk beta too, magisk hid Google pay, Google Play services tried a bunch of things but it ain't working Hmm
zee24 said:
I don't believe you, I'm on March update with pixel 2xl magisk and unlocked bootloader with TWRP installed. Safety net passes but Google pay doesn't work. I tried magisk beta too, magisk hid Google pay, Google Play services tried a bunch of things but it ain't working Hmm
Click to expand...
Click to collapse
Google Pay never stopped working for me. It worked fine on version 18 and works fine on version 19. I'm running stock March security patch with Kirisakura kernel.
murphyjasonc said:
Google Pay never stopped working for me. It worked fine on version 18 and works fine on version 19. I'm running stock March security patch with Kirisakura kernel.
Click to expand...
Click to collapse
Wow , That is strange. I can't get it working for the life of me. Have been the other magisk thread extensively. Was hoping 19.0 would have fixed my issues but it didn't
Cowbell_Guy said:
Wow , That is strange. I can't get it working for the life of me. Have been the other magisk thread extensively. Was hoping 19.0 would have fixed my issues but it didn't
Click to expand...
Click to collapse
I've looked at the threads also. I'm not sure why it stopped working for some people and not for others. I was one of the lucky ones I guess. Have you tried clearing the data for Google pay and Google play services? Some people have said that fixed it for them with version 19.
Cowbell_Guy said:
Wow , That is strange. I can't get it working for the life of me. Have been the other magisk thread extensively. Was hoping 19.0 would have fixed my issues but it didn't
Click to expand...
Click to collapse
This is the fix
Magisk stable build, all latest official builds of everything else, nothing special. and Magisk hide on google play store, google play services and google pay then - Renaming com.google.android.gms to com.google.android.gms.bak (found in Data/Data) in root browser and then rebooting is the answer .
prot- said:
This is the fix
Magisk stable build, all latest official builds of everything else, nothing special. and Magisk hide on google play store, google play services and google pay then - Renaming com.google.android.gms to com.google.android.gms.bak (found in Data/Data) in root browser and then rebooting is the answer .
Click to expand...
Click to collapse
I'm on the latest Canary build working fine to pay in stores using the method listed here. The rename was key...
prot- said:
This is the fix
Magisk stable build, all latest official builds of everything else, nothing special. and Magisk hide on google play store, google play services and google pay then - Renaming com.google.android.gms to com.google.android.gms.bak (found in Data/Data) in root browser and then rebooting is the answer .
Click to expand...
Click to collapse
Thanks, this worked!!
docluv01 said:
Thanks, this worked!!
Click to expand...
Click to collapse
Worked for me big thanks.
Sent from my Pixel 2 XL using Tapatalk
---------- Post added at 02:28 AM ---------- Previous post was at 02:27 AM ----------
prot- said:
This is the fix
Magisk stable build, all latest official builds of everything else, nothing special. and Magisk hide on google play store, google play services and google pay then - Renaming com.google.android.gms to com.google.android.gms.bak (found in Data/Data) in root browser and then rebooting is the answer .
Click to expand...
Click to collapse
Sorry wrong quote on last post. This worked for me big thanks
Sent from my Pixel 2 XL using Tapatalk