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
Related
I have the download link (the official .zip) for the update from google's servers but don't have access to adb. Can I download the update myself and then just boot into recovery or something and load it from there?
leaveone said:
I have the download link (the official .zip) for the update from google's servers but don't have access to adb. Can I download the update myself and then just boot into recovery or something and load it from there?
Click to expand...
Click to collapse
You can manually flash the factory image files with fastboot. If you don't have fastboot Google 15 second adb install xda, try not to use the dev host download site. It's bad.
Sent from my Nexus 5 using XDA Free mobile app
Doesn't flashing a factory image erase data? I'm trying to apply the OTA update without factory resetting my phone.
leaveone said:
Doesn't flashing a factory image erase data? I'm trying to apply the OTA update without factory resetting my phone.
Click to expand...
Click to collapse
Don't flash the userdata.img and it won't wipe your device. If you're going from 5.0 to 5.0.1 you should get by with just flashing the radio, boot, and system images. But as always, backup first off the device just in case.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Don't flash the userdata.img and it won't wipe your device. If you're going from 5.0 to 5.0.1 you should get by with just flashing the radio, boot, and system images. But as always, backup first off the device just in case.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I successfully used the adb sideload method last night. I was just curious if there was a way to apply the update without needing adb, like I have on other phones use CWM to apply an update from zip. Thanks for the help!
Hello i was wondering if you could help me with something. My XT1548 just got an OTA update. And i tried updating too it, but my phone keeps restarting every 2 minutes into TWRP instead of updating
i am on lollipop 5.1.1 trying too get the latest OTA.
SpitFire727 said:
Hello i was wondering if you could help me with something. My XT1548 just got an OTA update. And i tried updating too it, but my phone keeps restarting every 2 minutes into TWRP instead of updating
i am on lollipop 5.1.1 trying too get the latest OTA.
Click to expand...
Click to collapse
When twrp starts, clear caches and reboot. Should be good to go, and don't accept ota again, you must be stock to take ota.
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
When twrp starts, clear caches and reboot. Should be good to go, and don't accept ota again, you must be stock to take ota.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
So i unrooted VIA superSU
is the next step too install the stock rom?
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
SpitFire727 said:
So i unrooted VIA superSU
is the next step too install the stock rom?
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Click to expand...
Click to collapse
Maybe... If you had installed Xposed or other root app, it's best to that, or restore your pre-rooted nandroid backup. Otherwise, if you didn't modify system, just fastboot flash stock recovery and take the ota.
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Maybe... If you had installed Xposed or other root app, it's best to that, or restore your pre-rooted nandroid backup. Otherwise, if you didn't modify system, just fastboot flash stock recovery and take the ota.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
i removed a bunch of bloatware. mostly sprint junk
SpitFire727 said:
i removed a bunch of bloatware. mostly sprint junk
Click to expand...
Click to collapse
Then an OTA may fail, depending on what the update script checks for. I would flash back to pure stock to be safe.
Sent from my Motorola XT1575 using XDA Labs
i don't have a pre rooted backup :/
SpitFire727 said:
i don't have a pre rooted backup :/
Click to expand...
Click to collapse
Then I would flash back to stock...
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Then I would flash back to stock...
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
could you walk me through all the steps i need too take?
It's not complicated, get the image from this thread: http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Then use these instructions: http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Well documented and established method, just follow the instructions.
moving discussion to Q&A..
acejavelin said:
It's not complicated, get the image from this thread: http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Then use these instructions: http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Well documented and established method, just follow the instructions.
Click to expand...
Click to collapse
so i did all the steps, i updated too 6.1. but now i face a new problem, no devices are found in adb when in boot loader mode. it is detected while the phone is started up though.. in the progress of trying too fix this.
acejavelin said:
It's not complicated, get the image from this thread: http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Then use these instructions: http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Well documented and established method, just follow the instructions.
Click to expand...
Click to collapse
so followed all the steps and am now on 6.1, but now i face a new challenge. my adb is not finding any devices while in boot loader but it detects it while the phone is fully booted up.
SpitFire727 said:
so followed all the steps and am now on 6.1, but now i face a new challenge. my adb is not finding any devices while in boot loader but it detects it while the phone is fully booted up.
Click to expand...
Click to collapse
You phone will never be detected with adb in the bootloader, that isn't what adb is intended for, but that is where you use fastboot.
Your situation is completely normal.
acejavelin said:
You phone will never be detected with adb in the bootloader, that isn't what adb is intended for, but that is where you use fastboot.
Your situation is completely normal.
Click to expand...
Click to collapse
oh okay so how too i install TWRP, its in the internal storage and the command fastboot boot twrp.img just says waiting for device
SpitFire727 said:
oh okay so how too i install TWRP, its in the internal storage and the command fastboot boot twrp.img just says waiting for device
Click to expand...
Click to collapse
The TWRP img file needs to be on the computer in the fastboot directory. Start the bootloader and type 'fastboot devices' to make sure the device is recognized, then 'fastboot boot twrp.img' (remember to use the actual filename in place of twrp.img)
Sent from my Motorola XT1575 using XDA Labs
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.
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
So after I unlocked my bootloader I used the all in one tool to root and flash Magisk Seemed to go ok, but when I went to reboot I'm stuck at the G screen and then it goes back to twrp.
I flashed the patched boot image but it still isn't working.
What do i need to do?
mpetruzz said:
So after I unlocked my bootloader I used the all in one tool to root and flash Magisk Seemed to go ok, but when I went to reboot I'm stuck at the G screen and then it goes back to twrp.
I flashed the patched boot image but it still isn't working.
What do i need to do?
Click to expand...
Click to collapse
Flash the stock boot image to both slots.
Sent from my [device_name] using XDA-Developers Legacy app
I ended up going back to stock and then redoing the root/magisk process and everything worked ok. Must have been a weird issue, but it's working now.
mpetruzz said:
I ended up going back to stock and then redoing the root/magisk process and everything worked ok. Must have been a weird issue, but it's working now.
Click to expand...
Click to collapse
That works too. Glad you got it working. Did you use a tool or fastboot?
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
That works too. Glad you got it working. Did you use a tool or fastboot?
Click to expand...
Click to collapse
I flashed the factory image via the all in one tool, then rooted and flashed magisk via the tool as well.
The only difference step I took was that I decrypted twrp. Not sure if that was the issue but I'm all working now!!
mpetruzz said:
I flashed the factory image via the all in one tool, then rooted and flashed magisk via the tool as well.
The only difference step I took was that I decrypted twrp. Not sure if that was the issue but I'm all working now!!
Click to expand...
Click to collapse
If you didn't allow modifications when twrp first booted that is the issue.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
If you didn't allow modifications when twrp first booted that is the issue.
Click to expand...
Click to collapse
I allowed for modifications, but didn't enter my password so it didn't decrypt
same problem here
jd1639 said:
Flash the stock boot image to both slots.
I also have the problem, but when i try to flash magisk, It got bootloop. after that I flashed boot.img, system can boot, but there is no magisk authority.
Click to expand...
Click to collapse
Kongfihy said:
jd1639 said:
Flash the stock boot image to both slots.
I also have the problem, but I can not find an .img file in the offical firmware. I extracted it but only got these files:
META-INF
care_map.txt
compatibility.zip
payload.bin (size: 1.2G, the largest)
payload_properties.txt
I assume that payload.bin may contain something I need, but I can not open it.
Click to expand...
Click to collapse
That's not the factory image. It looks more like it might be a custom rom of some sort. Google pixel factory image. You need the full image, not the ota. Extract this. Inside is another zip file, extract that too. In there you'll find the boot image.
Edit, what you extracted is the ota. I've never extracted one before so didn't recognize it. There's never been a reason to extract it.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
mpetruzz said:
So after I unlocked my bootloader I used the all in one tool to root and flash Magisk Seemed to go ok, but when I went to reboot I'm stuck at the G screen and then it goes back to twrp.
I flashed the patched boot image but it still isn't working.
What do i need to do?
Click to expand...
Click to collapse
Need to flash factory image
Do your restore/account setup
Let it finish
Reboot bootloader
Boot TWRP
Flash magisk
Reboot
Pie not working?
mpetruzz how did u do it