Database Info

URGENT HELP PLEASE XT1548 OTA to marshmallow TWRP BOOT RESTART

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

Psa- android 7.1.1 update blocks depixel8

Make sure you don't update to 7.1.1 on a locked bootloader for the Verizon model otherwise, the depixel8 exploit will no longer work. It was confirmed by the developers of it already as you can check at their site and see as well. Now me personally I enjoy stock so I don't care but I figured for people with the Verizon model like me would care to see this.
Do not attempt to downgrade or any other methods of rooting until you see a tested and working method by one of the XDA devs in the Android Development forums for the Pixel.

learned this the hard way by updating my Verizon Pixel XL 128 installing twrp, then boot-to-root then bootloop. it appears it breaks twrp & root. i could be wrong. anybody else have a similar experience?

macboss said:
learned this the hard way by updating my Verizon Pixel XL 128 installing twrp, then boot-to-root then bootloop. it appears it breaks twrp & root. i could be wrong. anybody else have a similar experience?
Click to expand...
Click to collapse
If you're unlocked it shouldn't have re-locked it?
Sent from my Pixel using Tapatalk

macboss said:
learned this the hard way by updating my Verizon Pixel XL 128 installing twrp, then boot-to-root then bootloop. it appears it breaks twrp & root. i could be wrong. anybody else have a similar experience?
Click to expand...
Click to collapse
I'm pretty sure the boot to root doesn't work with TWRP. Use a factory image if possible and try to install TWRP and use the SuperSU zip instead.

If we are unlocked BL, rooted, stock recovery with SR5, will root break if we adb sideload?

joshw0000 said:
If you're unlocked it shouldn't have re-locked it?
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
I was thinking the same thing... The update in general wouldn't have gone through if it was rooted.

so how do I update if I'm unlocked and have twrp installed? I'm assuming I shouldn't take the OTA update?

Bought my pixel from the Google store. Pixels from the Google store, are the bootloader's locked or unlocked?
Sent from my Pixel XL using Tapatalk

They are locked upon purchasing however, you can easily unlock them.
jreink01 said:
Bought my pixel from the Google store. Pixels from the Google store, are the bootloader's locked or unlocked?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse

Archangel said:
They are locked upon purchasing however, you can easily unlock them.
Click to expand...
Click to collapse
Might be interested in rooting at some point, is it my understanding to not take the 7.1.1 update then. Or wouldn't it matter since my bootloader is still locked? I guess what I'm asking if root would still be possible if i took the update?
Sent from my Pixel XL using Tapatalk

jreink01 said:
Might be interested in rooting at some point, is it my understanding to not take the 7.1.1 update then. Or wouldn't it matter since my bootloader is still locked? I guess what I'm asking if root would still be possible if i took the update?
Click to expand...
Click to collapse
If you are have a phone from Verizon it is required to have unlocked bootloader to obtain root.
So if it is a Verizon phone and you take 7.1.1 update - you won't be able to get root

km8j said:
If we are unlocked BL, rooted, stock recovery with SR5, will root break if we adb sideload?
Click to expand...
Click to collapse
Yes
Sent from my Pixel using Tapatalk
---------- Post added at 08:45 AM ---------- Previous post was at 08:44 AM ----------
mrj0087 said:
so how do I update if I'm unlocked and have twrp installed? I'm assuming I shouldn't take the OTA update?
Click to expand...
Click to collapse
I side loaded the OTA and went through the process again have twrp and root
Sent from my Pixel using Tapatalk

I bought my device from UK, i got it unlocked and rooted but without TWRP recovery, what is the best option for me to install the update ?
And does it erase my device ?
Thanks in advace ...
I'm running Build : NDE63V

guandms said:
I bought my device from UK, i got it unlocked and rooted but without TWRP recovery, what is the best option for me to install the update ?
And does it erase my device ?
Thanks in advace ...
I'm running Build : NDE63V
Click to expand...
Click to collapse
With an unlocked BL, you're pretty free to do whatever you want. I've done it multiple ways; to me, the most straightforward steps are:
Download the 7.1.1 NMF260 image from Google.
Extract the zip file into the adb folder on the PC.
Edit the flash-all.bat file to remove the -w switch so user data won't be deleted. You'll find this -w switch easily enough.
Put your Pixel into fastboot mode, using either power+volume down or via adb command.
Plug phone to PC if not already done so. Execute the flash-all batch file.
When that's done, you have 7.1.1 on your phone, along with new radio and new kernel. (actually, I'm not sure if Google even put out a new kernel.)
Then you can go back to re-root with whatever method you used previously.
Enjoy!

km8j said:
If we are unlocked BL, rooted, stock recovery with SR5, will root break if we adb sideload?
Click to expand...
Click to collapse
Yes, but just reroot. Works fine.
---------- Post added at 11:34 AM ---------- Previous post was at 11:31 AM ----------
jreink01 said:
Might be interested in rooting at some point, is it my understanding to not take the 7.1.1 update then. Or wouldn't it matter since my bootloader is still locked? I guess what I'm asking if root would still be possible if i took the update?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
On a Google Store pixel, you can always unlock your bootloader. You are posting in a vzw pixel revelent thread, depixel8 and any talk on the subject doesn't apply. Don't get confused.

Sorry, didn't know i was in a Verizon thread.
Sent from my Pixel XL using Tapatalk

epic4grooted said:
Yes
Sent from my Pixel using Tapatalk
---------- Post added at 08:45 AM ---------- Previous post was at 08:44 AM ----------
I side loaded the OTA and went through the process again have twrp and root
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Sorry I'm confused. So use adb side load in twrp? So I'm doing adb reboot recovery then adb side load OTA.zip once in twrp? Then I have to reflash twrp and root?

Download the OTA zip from Google run flash all it then go through the steps to reroot and install twrp
Sent from my Pixel using Tapatalk

I unlocked the BL using dePixel8 last Wed. when I picked up my Pixel. It updated to NDE63X via OTA after I unlocked BL. Received OTA update to NMF260, downloaded and installed it last night via normal OTA process. BL unlock is unchanged: unlocked status.
It helps if the phone is plugged in and on WiFi since it is a 260MB download.
So far 7.1.1 works great.

epic4grooted said:
Download the OTA zip from Google run flash all it then go through the steps to reroot and install twrp
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
got it

Anyone have Netflix working on 8.1?

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.

Tried to lock bootloader and now can't boot.

Brand new Pixel 2. Unlocked bootloader and rooted with Magisk with no issues. Decided to return the phone. Booted into fastboot and ran the command to lock the bootloader and got stuck in fastboot with an error that I forgot to write down. I tried to reboot and now I'm just stuck on the white screen with the Google logo and the loading bar going on the bottom. I am able to boot back into bootloader.
Any ideas?
Thanks

Flash factory image and make sure your platform tools is updated i.e. adb and fastboot.
Sent from my walleye using XDA Labs

dobbs3x said:
Flash factory image and make sure your platform tools is updated i.e. adb and fastboot.
Sent from my walleye using XDA Labs
Click to expand...
Click to collapse
I'm trying that now. Platform tools are fresh but now I'm getting an error that the bootloader version isn't correct. Trying to get that ironed out now.

Even trying to sideload the OTA I get an error that the bootloader is the wrong version.

Ok, so now tried unlocking the bootloader again but still the same error that it's the wrong bootloader version.

thenags said:
I'm trying that now. Platform tools are fresh but now I'm getting an error that the bootloader version isn't correct. Trying to get that ironed out now.[/QUOTE
You should post those errors here, they will help.
Sent from my walleye using XDA Labs
Click to expand...
Click to collapse

dobbs3x said:
thenags said:
I'm trying that now. Platform tools are fresh but now I'm getting an error that the bootloader version isn't correct. Trying to get that ironed out now.[/QUOTE
You should post those errors here, they will help.
Sent from my walleye using XDA Labs
Click to expand...
Click to collapse
This is what I'm getting no matter what I do;
Device version-bootloader is 'mw8998-002.0059.00'.
Update requires 'mw8998-002.0066.00'.
I'm currently trying this;
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse

The script from that thread actually got me booting again but with bootloader unlocked. Let's see if I can lock it without it breaking again.

Alright. Back in action.
Thanks dobbs3x for the moral support lol.
For anyone in the future with a similar issue go to this thread and follow the steps;
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

Rooted, installed Magisk and now phone won't boot

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