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
Related
So I just got some type of OTA update from Verizon, I have an unlocked bootloader as well as rooted. Can I install this update or will it brick? The file is under /cache/fota/update.zip 30.92mb. I thought if you was rooted you couldn't even get OTA's. Any ideas? I renamed the file so it wouldn't update even though it asked me when to install and I entered 10pm tonight to retry.
Sent from my SCH-I535 using xda app-developers app
It's a pretty major security patch so hopefully someone here puts it in a package for flashing. Someone else said they just unlocked again immediately after but I'm not sure how to best approach it for you.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 05:31 AM ---------- Previous post was at 05:29 AM ----------
Rooting doesn't do anything about receiving updates, it's a particular file that is phoning home.
Sent from my SCH-I535 using Tapatalk 2
bskarpa said:
So I just got some type of OTA update from Verizon, I have an unlocked bootloader as well as rooted. Can I install this update or will it brick? The file is under /cache/fota/update.zip 30.92mb. I thought if you was rooted you couldn't even get OTA's. Any ideas? I renamed the file so it wouldn't update even though it asked me when to install and I entered 10pm tonight to retry.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Do you have a rom? If not people are saying they installed update and rooted device again.
I just got it this morning as well.... I'm stock rooted and I don't want the update. Do I have to accept it? Do I need to un-root? What will happen to my Google Wallet & Google Now?
I'd like to know also, I am stock rooted, unlocked and don't know if I should accept the update or not??
I got the same update but it flashed itself into recovery and then failed to install the update. Says "install aborted"
pmdied said:
I got the same update but it flashed itself into recovery and then failed to install the update. Says "install aborted"
Click to expand...
Click to collapse
You are right, I clicked "OK", it rebooted and went into CWM. I clicked "reboot now", when the phone finished booting I got an error message. Hopefully it won't continue doing this.
No I'm on a stock rooted ROM, it tried to install just now and failed as well.
Sent from my SCH-I535 using xda app-developers app
This is because you all most likely have a custom recovery like TWRP or CWM and it can only install on stock recovery. If you freeze sdm1.0 it wont keep asking you to update
Tap'n
bskarpa said:
So I just got some type of OTA update from Verizon, I have an unlocked bootloader as well as rooted. Can I install this update or will it brick? The file is under /cache/fota/update.zip 30.92mb. I thought if you was rooted you couldn't even get OTA's. Any ideas? I renamed the file so it wouldn't update even though it asked me when to install and I entered 10pm tonight to retry.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I've heard that to be safe, you need to re-lock the boot loader, un-root, and go back to stock in order to accept the updates.
There is a guide to do that here: http://forum.xda-developers.com/showthread.php?t=1867253
mooremh said:
I've heard that to be safe, you need to re-lock the boot loader, un-root, and go back to stock in order to accept the updates.
There is a guide to do that here: http://forum.xda-developers.com/showthread.php?t=1867253
Click to expand...
Click to collapse
Thanks yall!
I updated to newest ota g7 and rooted now. But can I push the aboot in terminal like I originally did? I only ask cause of all the issues I see with ez unlock. I like the manual way anyhow
Sent from my SCH-I535 using Tapatalk 2
I just flashed Scott's Rom latest vlrag7 and now my device says up to date:thumbup:
Sent from my SCH-I535 using xda app-developers app
mooremh said:
I've heard that to be safe, you need to re-lock the boot loader, un-root, and go back to stock in order to accept the updates.
There is a guide to do that here: http://forum.xda-developers.com/showthread.php?t=1867253
Click to expand...
Click to collapse
You are okay to be rooted and do a update. I do it all the time, it just unroots you and you have to rerun ur rooting. As for the bootloader i lock it before a update
Sent from my SCH-I535 using Tapatalk 2
hopesrequiem said:
I updated to newest ota g7 and rooted now. But can I push the aboot in terminal like I originally did? I only ask cause of all the issues I see with ez unlock. I like the manual way anyhow
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
If you use version 1.2 there isn't any issues. The 1.4 in the market of the one with issues. There's a thread somewhere in here that you can download the older versions that work correctly still
Tap'n
Just find ez-unlock in the play store and click on the link in the description. It will take you to the app's website,which has links for all versions.
Sent from my SCH-I535 using xda app-developers app
Wondering what version of twrp to use to flash recovery for root or am I not able with new version 4.4.4
Droid Maxx
Sent from my XT1080 using XDA Free mobile app
boffster99 said:
Wondering what version of twrp to use to flash recovery for root or am I not able with new version 4.4.4
Droid Maxx
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
Well, you can downgrade to 4.4, take the 4.4.4 OTA, and then flash the latest TWRP and install the apropiate root for the phone.
I was already at 4.4 then took the ota to 4.4.4 seems to be several versions of twrp. Just wondering what works for the maxx and does root change with the new ota?
Sent from my XT1080 using XDA Free mobile app
boffster99 said:
I was already at 4.4 then took the ota to 4.4.4 seems to be several versions of twrp. Just wondering what works for the maxx and does root change with the new ota?
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
Use whatever version you want, 2.7 works though. The update didn't require stock recovery or removing of root though. Not sure what you mean by does root change but same process as it has always been.
akellar said:
Use whatever version you want, 2.7 works though. The update didn't require stock recovery or removing of root though. Not sure what you mean by does root change but same process as it has always been.
Click to expand...
Click to collapse
So your saying you took the OTA with twrp? Or you manually flashed the update in twrp?
an21281 said:
So your saying you took the OTA with twrp? Or you manually flashed the update in twrp?
Click to expand...
Click to collapse
Flashed in TWRP. Same end result with half the headache.
I thought I had to go back to stock to take the update so I did. Sorry I didn't keep twrp and do it that way. Oh well. Thanks for the replies I really appreciate it.
Sent from my XT1080 using XDA Free mobile app
joel_sinbad said:
Well, you can downgrade to 4.4, take the 4.4.4 OTA, and then flash the latest TWRP and install the apropiate root for the phone.
Click to expand...
Click to collapse
Once on 4.4.4 - you cant downgrade, the bootloader wont allow you.
CrazyRussianXDA said:
Once on 4.4.4 - you cant downgrade, the bootloader wont allow you.
Click to expand...
Click to collapse
Don't flash the motoboot.img, that's the bootloader, skip this line...
Im on the same boat.
Currently im on 4.4, unlocked bootloader and thats all.
In order to get root, should i flash first twrp, root and then take the ota?
And other question.. ¿Its possible to lock again the bootloader? Im afraid to unlock it again, i spend $25
conquesoextra said:
Im on the same boat.
Currently im on 4.4, unlocked bootloader and thats all.
In order to get root, should i flash first twrp, root and then take the ota?
And other question.. ¿Its possible to lock again the bootloader? Im afraid to unlock it again, i spend $25
Click to expand...
Click to collapse
If your unlocked there is no way to lock the phone, flash twrp and boot into it, it will ask you to root on exiting.
Thank you ¿even if i try whit fastboot oem lock?
Whenever superSu asks for permission to run a root app my screen becomes unresponsive. Timer runs out and i am not able to apply grant permission. Help. This didnt use to happen when i was earlier rooted with towelroot. Right now also i ised towelroot
Have you tried re-flashing the supersu zip?
jameson21 said:
Have you tried re-flashing the supersu zip?
Click to expand...
Click to collapse
Yes. Didnt work.
Btw by reflash the zip file you mean reinstall it from pkay store, right?
Pardon the ignorance. Just found out that flashing a zip file and installing apps from play store are 2 different things.
Well my bootloader is locked and neither do i have a custom recovery installed. So flashing doesnt seem to be an option right now.. If i am not missing anything.
Are you running 5.0? If so how the heck did you root with towelroot? AFAIK you can not root 5.0 that way. Maybe that is a problem.
Sent from my Nexus 5 using Tapatalk
frenziedfemale said:
Are you running 5.0? If so how the heck did you root with towelroot? AFAIK you can not root 5.0 that way. Maybe that is a problem.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
No no. I am on kitkat only
Tried reinstalling it. This is what came up. I am on android 4.4.4 btw
You need to flash the supersu zip using fastboot:
teamandroid. com/2014/06/19/root-nexus-5-android-444-ktu84p-kitkat/2/ (you're going to have to fix that link because I have under 10 posts so the forum won't let me post..)
Additionally you need to have an unlocked bootloader
jameson21 said:
You need to flash the supersu zip using fastboot:
teamandroid. com/2014/06/19/root-nexus-5-android-444-ktu84p-kitkat/2/ (you're going to have to fix that link because I have under 10 posts so the forum won't let me post..)
Additionally you need to have an unlocked bootloader
Click to expand...
Click to collapse
Why is it happening now? Didnt use to happen earlier..
You say you were rooted ...why did you re-root? It looks like you are no longer rooted. Did you do an update or anything?
Sent from my Nexus 5 using Tapatalk
frenziedfemale said:
You say you were rooted ...why did you re-root? It looks like you are no longer rooted. Did you do an update or anything?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I was rooted. I unrooted because i thought it was required to update to lollipop. But i dont have any intention to update to L for now.
rahul9five said:
I was rooted. I unrooted because i thought it was required to update to lollipop. But i dont have any intention to update to L for now.
Click to expand...
Click to collapse
To get root again either flash the latest CF Auto Root in fastboot or flash the latest superSU.zip in recovery or flash a pre-rooted custom rom in a custom recovery.
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
Hey guys, bought a pixel 3 from swappa. Got a good deal because it was bootloader unlocked and the guy didn't know how easy it was to fix. Received it today. I had downloaded the June images a few days ago when I bought it. I fastboot -w it first. I then flashed factory images. Let it reboot. Back to fastboot, set to other slot and repeated factory images and-w. All went well. Back to fastboot and locked bootloader. Everything works including Google pay but when I try to update to July via ota or q beta it fails. Every time. What's up?
Sent from my Pixel 3 using Tapatalk
jmtjr278 said:
Hey guys, bought a pixel 3 from swappa. Got a good deal because it was bootloader unlocked and the guy didn't know how easy it was to fix. Received it today. I had downloaded the June images a few days ago when I bought it. I fastboot -w it first. I then flashed factory images. Let it reboot. Back to fastboot, set to other slot and repeated factory images and-w. All went well. Back to fastboot and locked bootloader. Everything works including Google pay but when I try to update to July via ota or q beta it fails. Every time. What's up?
Sent from my Pixel 3 using Tapatalk
Click to expand...
Click to collapse
Seems to be sorted after unlocking and re flashing June factory. Downloaded and installed q no problem!
Sent from my Pixel 3 using Tapatalk
jmtjr278 said:
Seems to be sorted after unlocking and re flashing June factory. Downloaded and installed q no problem!
Sent from my Pixel 3 using Tapatalk
Click to expand...
Click to collapse
i have the same issue my phone would not update to july nor Q it gives me no valid operating system
could you please write me the followed steps to recover stock
thnaks
eldode said:
i have the same issue my phone would not update to july nor Q it gives me no valid operating system
could you please write me the followed steps to recover stock
thnaks
Click to expand...
Click to collapse
Is your bootloader unlocked? If not you need to try and adb an ota.
Sent from my Pixel 3 using Tapatalk
jmtjr278 said:
Is your bootloader unlocked? If not you need to try and adb an ota.
Sent from my Pixel 3 using Tapatalk
Click to expand...
Click to collapse
bootloader is locked
i need it to install ota automatically from system update
i gives me installation error
could you please help me
jmtjr278 said:
Seems to be sorted after unlocking and re flashing June factory. Downloaded and installed q no problem!
Sent from my Pixel 3 using Tapatalk
Click to expand...
Click to collapse
Did you relock bootloader after updating, cause I need Google pay
eldode said:
bootloader is locked
i need it to install ota automatically from system update
i gives me installation error
could you please help me
Click to expand...
Click to collapse
If bootloader is locked you need to download adb and latest ota images. Boot phone into bootloader, go to recovery, hold volume up and press power until menu appears, apply update from adb, open terminal, give the command to sideload ota, adb sideload file_name.zip. Let it do it's thing. Reboot
Sent from my Pixel 3 using Tapatalk
phuzzeeoyster said:
Did you relock bootloader after updating, cause I need Google pay
Click to expand...
Click to collapse
Yes, I relocked bootloader for the same reason
Sent from my Pixel 3 using Tapatalk