After updating to 8.1, Netflix won't work. Couldn't find it on play store, so downloaded from APK mirror. Upon opening it gives an error. Tried hiding magisk from Netflix, and also have magisk in core only mode.
Sent from my [device_name] using XDA-Developers Legacy app
Works fine.
Works fine on both phones. Stock kernel and Snoke kernel.
Sent from my Pixel 2 using Tapatalk
krelvinaz said:
Works fine.
Click to expand...
Click to collapse
Diesel_Jeremiah said:
Works fine on both phones. Stock kernel and Snoke kernel.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
So what do I need to do
Sent from my [device_name] using XDA-Developers Legacy app
gvsukids said:
So what do I need to do
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
How did you update to 8.1? What version of Magisk? Custom or stock kernel or custom (Smoke, Flash)?
Sent from my Pixel 2 using Tapatalk
Diesel_Jeremiah said:
How did you update to 8.1? What version of Magisk? Custom or stock kernel or custom (Smoke, Flash)?
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Updated via OTA, but had to use Android data reset. Using magisk manager 14, 14.5 zip. Flash walleye 2.02
Sent from my [device_name] using XDA-Developers Legacy app
I would try going back to stock kernel and remove Magisk. Check Netflix. Install Magisk. Check Netflix. Flash kernel. See if you can pin point what's actually breaking the app.
Sent from my Pixel 2 using Tapatalk
Diesel_Jeremiah said:
I would try going back to stock kernel and remove Magisk. Check Netflix. Install Magisk. Check Netflix. Flash kernel. See if you can pin point what's actually breaking the app.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Use fastboot to flash stock kernel? Would it be the one from the factory image or the OTA image?
Sent from my [device_name] using XDA-Developers Legacy app
If you can't find it in the play store, that means safetynet is not passing. Check safetnet in magisk manager.
gvsukids said:
Use fastboot to flash stock kernel? Would it be the one from the factory image or the OTA image?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
You will use fastboot to flash both boot and dtbo from the factory image.
Link added for ease of locating: Factory Images for Nexus and Pixel Devices
Diesel_Jeremiah said:
You will use fastboot to flash both boot and dtbo from the factory image.
Link added for ease of locating: Factory Images for Nexus and Pixel Devices
Click to expand...
Click to collapse
did that, and with no root, I have no netflix. cleared app data, rebooted and still not able to access netflix
should i just reflash the ota?
gvsukids said:
did that, and with no root, I have no netflix. cleared app data, rebooted and still not able to access netflix
should i just reflash the ota?
Click to expand...
Click to collapse
Is your bootloader still unlocked? You will not pass safetynet with an unlocked bootloader using the stock kernel. You need a kernel modified to pass the bootloader check, (there's stock and other variants like snoke, flash, elementalx) and then re-clear your play store/services app data.
clcdev said:
Is your bootloader still unlocked? You will not pass safetynet with an unlocked bootloader using the stock kernel. You need a kernel modified to pass the bootloader check, (there's stock and other variants like snoke, flash, elementalx) and then re-clear your play store/services app data.
Click to expand...
Click to collapse
Tried with flash 2.0.3, patched with magisk 5.4.3, passed safety net, but Netflix wouldn't load. Didn't have this much trouble on 8.0
Sent from my [device_name] using XDA-Developers Legacy app
gvsukids said:
Tried with flash 2.0.3, patched with magisk 5.4.3, passed safety net, but Netflix wouldn't load. Didn't have this much trouble on 8.0
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Hmmm... that's weird. If you go to settings in the Play Store, does it say 'Device certification certified' at the bottom of the screen?
clcdev said:
Hmmm... that's weird. If you go to settings in the Play Store, does it say 'Device certification certified' at the bottom of the screen?
Click to expand...
Click to collapse
Says uncertified
Sent from my [device_name] using XDA-Developers Legacy app
gvsukids said:
Says uncertified
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Ok. That's the crux of your problem. Netflix won't work until that says certified. As far as I know, once you have safetynet passing you should be able to clear data/cache for pay services/play store and reboot. Then it should say certified in settings.
clcdev said:
Ok. That's the crux of your problem. Netflix won't work until that says certified. As far as I know, once you have safetynet passing you should be able to clear data/cache for pay services/play store and reboot. Then it should say certified in settings.
Click to expand...
Click to collapse
I can now install Netflix from play store, but still had the error even trying to load
Sent from my [device_name] using XDA-Developers Legacy app
gvsukids said:
I can now install Netflix from play store, but still had the error even trying to load
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Ok. If you can install from the play store now, not sure what's going on. I just downloaded it myself and it loaded up just fine. I'm rooted with Magisk 14.5, Flash kernel 2.0.3 and my play store says 'certified'.
clcdev said:
Ok. If you can install from the play store now, not sure what's going on. I just downloaded it myself and it loaded up just fine. I'm rooted with Magisk 14.5, Flash kernel 2.0.3 and my play store says 'certified'.
Click to expand...
Click to collapse
What finally worked for me was connecting to WiFi. Now it works on data
Need steps are rooting
Sent from my [device_name] using XDA-Developers Legacy app
clcdev said:
Ok. That's the crux of your problem. Netflix won't work until that says certified. As far as I know, once you have safetynet passing you should be able to clear data/cache for pay services/play store and reboot. Then it should say certified in settings.
Click to expand...
Click to collapse
Thanks, this fixed things for me straight away.
Related
hi
this morning i have received the OTA, i ran it and it successfully updated to 4.4.2 however i no longer have root access.
so do i have to redo everything again (backup everything and reboot again) or is there any quick way to fix this?
Sent from my Nexus 5 using xda app-developers app
its like no one searches anymore...
just reflash a custom recovery and then flash supersu.zip again.
redjersey said:
hi
this morning i have received the OTA, i ran it and it successfully updated to 4.4.2 however i no longer have root access.
so do i have to redo everything again (backup everything and reboot again) or is there any quick way to fix this?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Of course you lost root. That's normal. Just re-root. How did you root before?
jd1639 said:
Of course you lost root. That's normal. Just re-root. How did you root before?
Click to expand...
Click to collapse
bet he used a toolkit.
Zepius said:
bet he used a toolkit.
Click to expand...
Click to collapse
I'm guessing too.
Shoulda just flashed su zip after flashing the update then reboot
Sent from my Nexus 5 using Tapatalk
I was using this method:
http://www.youtube.com/watch?v=w3beFx-3Ic4
to root my nexus 5.
redjersey said:
I was using this method:
http://www.youtube.com/watch?v=w3beFx-3Ic4
to root my nexus 5.
Click to expand...
Click to collapse
Use this method http://forum.xda-developers.com/showthread.php?p=47025283
installed supersu from google play, now it's fine
redjersey said:
installed supersu from google play, now it's fine
Click to expand...
Click to collapse
I'm a bit surprised that installing the app from the market fixed it..... maybe I am missing something... LOL
Zepius said:
bet he used a toolkit.
Click to expand...
Click to collapse
hell guys, why be snobs?
ive been around here for many years, had many, many devices, probably a hundred roms, and I use the toolkit because I find it easier...and have had no major problems.
so
After rooting with the toolkit, SuperSU was not showing up as an app. Installing it via play store worked for me too... - it asked if I wanted to update binaries, I chose normal instead of via twrp, and after doing that and a reboot, all is good...
cheers
Mark.
redjersey said:
installed supersu from google play, now it's fine
Click to expand...
Click to collapse
If you accepted an OTA you will have to re-root manually or with the tool kit you originally used.
You can't simply install SuperSU from the Play Store and regain root. Sure the app will install (anyone can do this) but the binaries will be absent (i.e. no root).
You can test this by opening SuperSU. When you open it, it will tell you if it's working correctly.
Sent from my Nexus 5 using Tapatalk
I just finally got the new 38R update and it updated fine. I did just realize I lost root. Just out of curiosity, is there way to circumvent that for the next update? Or will I have to reroot every time
Go into supersu and enable survival mode.
To re obtain root, just re flash supersu in recovery mode.
Sent from my A0001 using Tapatalk
Yeah rerooting is easy. I was just curious.
Sent from my A0001 using XDA Free mobile app
xImposter said:
Yeah rerooting is easy. I was just curious.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
It would only work if the rom came pre-rooted.
TWRP has a nice feature which auto-roots from recovery if it detects you lost root while flashing.
By auto-root I mean it moves su to your phone and adds supersu apk xD
I've applied previous OTA zips by just flashing in TWRP. However I'm getting an error this time around. I'm on the KK build ending in P, but when i try to flash Lollipop it says my build fingerprint is incorrect, that it's the KK build ending in H. Anyone have insight on why this is?
Sent from my Nexus 5 using XDA Free mobile app
As it says, you're not 100% stock so it won't flash
This would be due to my recovery and xposed i take it? Or strictly xposed?
Sent from my Nexus 5 using XDA Free mobile app
Definitely Xposed, probably recovery as well
Xposed. You'll not just need to uninstall the xposed files, but the app too as ART doesn't like to boot with that app installed.
Recovery is fine. Only issue would be that an OTA.wouldnt automatically install. You'd have to manually boot into recovery to flash.
rootSU said:
Xposed. You'll not just need to uninstall the xposed files, but the app too as ART doesn't like to boot with that app installed.
Recovery is fine. Only issue would be that an OTA.wouldnt automatically install. You'd have to manually boot into recovery to flash.
Click to expand...
Click to collapse
Many thanks. Got it working. Appreciate it!
Sent from my Nexus 5 using XDA Free mobile app
rootSU said:
Xposed. You'll not just need to uninstall the xposed files, but the app too as ART doesn't like to boot with that app installed.
Recovery is fine. Only issue would be that an OTA.wouldnt automatically install. You'd have to manually boot into recovery to flash.
Click to expand...
Click to collapse
Hmm, it didn't work. Removed xposed and unistalled, still getting same error. I'm stock, rooted, had xposed.
Sent from my Nexus 5 using XDA Free mobile app
rootSU said:
Xposed. You'll not just need to uninstall the xposed files, but the app too as ART doesn't like to boot with that app installed.
Recovery is fine. Only issue would be that an OTA.wouldnt automatically install. You'd have to manually boot into recovery to flash.
Click to expand...
Click to collapse
Do i need to sideload the ota zip in recovery or flash like normal?
Sent from my Nexus 5 using XDA Free mobile app
You may want to look at flashing a full ROM.zip instead as it will be much easier.
rootSU said:
You may want to look at flashing a full ROM.zip instead as it will be much easier.
Click to expand...
Click to collapse
I can just fastboot flash the images separately... Which ones do i omit to keep recovery and user data?
Sent from my Nexus 5 using XDA Free mobile app
Don't flash userdata.img and your storage data will be fine. If you want to keep your custom recovery, don't flash recovery.img.
Phaded said:
I can just fastboot flash the images separately... Which ones do i omit to keep recovery and user data?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Funnily enough, recovery.img and userdata.img haha
Also you'll need to delete:
/system/recovery.init.boot.p
/system/bin/install-recovery.sh
Before boot, although flashing superSU should prevent them installing stock recovery
rootSU said:
Funnily enough, recovery.img and userdata.img haha
Also you'll need to delete:
/system/recovery.init.boot.p
/system/bin/install-recovery.sh
Before boot, although flashing superSU should prevent them installing stock recovery
Click to expand...
Click to collapse
You listed two files i need to delete. Is that before or after flashing the img files?
I've never had a problem before, i don't get why it's failing now... Keeps saying I'm showing an old build fingerprint. Never seen this error before.
Short of being rooted, I've removed any modifications to my system. Really don't feel like wiping the whole device.
Sent from my Nexus 5 using XDA Free mobile app
Sent from my Nexus 5 using XDA Free mobile app
I have an update for 8.1.0. I'm rooted, custom kernel, and using magisk. Before I update, I'm wondering if I'll lose root when flashing the update, or just my kernel.
Sent from my [device_name] using XDA-Developers Legacy app
gvsukids said:
I have an update for 8.1.0. I'm rooted, custom kernel, and using magisk. Before I update, I'm wondering if I'll lose root when flashing the update, or just my kernel.
Click to expand...
Click to collapse
The OTA won't install. You have to side load the full image from Google. It shouldn't break root.
PuffDaddy_d said:
The OTA won't install. You have to side load the full image from Google. It shouldn't break root.
Click to expand...
Click to collapse
Full OTA image, or full factory image?
Sent from my [device_name] using XDA-Developers Legacy app
gvsukids said:
Full OTA image, or full factory image?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
me too waiting for answer
Daandofreak said:
me too waiting for answer
Click to expand...
Click to collapse
the OTA is easier, but you can do the factory image if you modify the flash-all script and remove the -w command, which would have wiped your phone.
I just reflash my phone's current factory image (without -w), then OTA sideload to the new one.
collinjames said:
the OTA is easier, but you can do the factory image if you modify the flash-all script and remove the -w command, which would have wiped your phone.
Click to expand...
Click to collapse
kinfam said:
I just reflash my phone's current factory image (without -w), then OTA sideload to the new one.
Click to expand...
Click to collapse
Why flashing the factory image first?
Sent from my [device_name] using XDA-Developers Legacy app
Try following this method. It's a bit of work but is proven to be effective.
https://forum.xda-developers.com/pixel-2/how-to/dec-2017-to-jan-2018-update-how-updated-t3729313
Can the Pixel 3 be rooted? I see the boot loader can be unlocked.
Sent from my [device_name] using XDA-Developers Legacy app
gvsukids said:
Can the Pixel 3 be rooted? I see the boot loader can be unlocked.
Click to expand...
Click to collapse
You'll have to wait and see. It seems that @topjohnwu, the creator of magisk, gets his P3 today. So we'll see what he comes up with :good:
Has anyone been able to flash individual partitions, such as boot? I've tried and don't remember the exact error but it was something to the effect that the partition doesn't exist.
Sent from my [device_name] using XDA-Developers Legacy app
Wait, so the bootloader CAN be unlocked?
k.s.deviate said:
Wait, so the bootloader CAN be unlocked?
Click to expand...
Click to collapse
On the google version it can.
Badger50 said:
On the google version it can.
Click to expand...
Click to collapse
Ok, until an RMA is needed.
k.s.deviate said:
Ok, until an RMA is needed.
Click to expand...
Click to collapse
Google doesn't care if the bootloader is unlocked. So no worries there. But if you can't flash partitions it makes me nervous doing anything with the phone.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Google doesn't care if the bootloader is unlocked. So no worries there. But if you can't flash partitions it makes me nervous doing anything with the phone.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
No, I know that. I meant wait until you get a device back on an RMA and find out it's refurbished. Will not be able to unlock the bootloader... Just like the pixel 2.
k.s.deviate said:
No, I know that. I meant wait until you get a device back on an RMA and find out it's refurbished. Will not be able to unlock the bootloader... Just like the pixel 2.
Click to expand...
Click to collapse
You can unlock bootloader on Pixel 2 and on Pixel 3
Sent from my [device_name] using XDA-Developers Legacy app
Curious.. is the Verizon bootloader locked again this time? Wondering if I can pick one up at Best Buy or if I'll have to order from the Google Store.
EDIT - Nm. Per other threads, Verizon is locked down again.
gvsukids said:
You can unlock bootloader on Pixel 2 and on Pixel 3
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-2/help/oem-unlocking-grayed-vzw-pixel-2-t3776763
Yes it is possible
https://twitter.com/topjohnwu/status/1053488124389720064
topjohnwu got magisk working on Pixel 3
I'm rooted! Thanks to @topjohnwu
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I'm rooted! Thanks to @topjohnwu
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
how'd you obtain root? I tried canary build this morning and still get bootloops. github looks like its still "down" https://status.github.com/messages
k.s.deviate said:
Wait, so the bootloader CAN be unlocked?
Click to expand...
Click to collapse
Yeah, the usual way for a google device. fastboot flashing unlock. You'll need the beta version of Magisk to root, I used v17.4. I did need to flash the patched boot image to both boot partitions.
jd1639 said:
Yeah, the usual way for a google device. fastboot flashing unlock. You'll need the beta version of Magisk to root, I used v17.4. I did need to flash the patched boot image to both boot partitions.
Click to expand...
Click to collapse
beta is showing as 17.2 for me, im going to try canary with the OTA boot.img
marc.ientilucci said:
beta is showing as 17.2 for me, im going to try canary with the OTA boot.img
Click to expand...
Click to collapse
Use this URL for the custom URL in Magisk, https://bit.ly/2N8UVlq That'll get you to the latest beta.
jd1639 said:
Use this URL for the custom URL in Magisk, https://bit.ly/2N8UVlq That'll get you to the latest beta.
Click to expand...
Click to collapse
using the canary build worked. i removed magisk manager, reinstalled it, used the boot.img from the factory image and all went well.
Please help.. I am stuck with no valid slot to boot and wont be able to reboot at all..
I do have patched_boot.img on my PC where I ran "fastboot flash boot patched_boot.img" and it did not show any error but I still cant reboot it due to no valid slot.
Help me would be greatly appreciated.
it is unlocked and use Sprint carrier.
Thanks,
Adrian
adhusky said:
Please help.. I am stuck with no valid slot to boot and wont be able to reboot at all..
I do have patched_boot.img on my PC where I ran "fastboot flash boot patched_boot.img" and it did not show any error but I still cant reboot it due to no valid slot.
Help me would be greatly appreciated.
it is unlocked and use Sprint carrier.
Thanks,
Adrian
Click to expand...
Click to collapse
You'll have to flash the patched image to both boot partitions. fastboot flash boot_a patched_boot.img. Do the same with boot_b