Hi just got the pixel 2 xl. Came with 8.1 updated to 9 now I'm getting each security update. Can I just sideload the latest ota and save a whole lot of time?
No. You'll have to go through them all unless you unlock your bootloader and flash the June factory image.
Sent from my Pixel 2 XL using XDA Labs
MrMeeseeks said:
No. You'll have to go through them all unless you unlock your bootloader and flash the June factory image.
Click to expand...
Click to collapse
Ah unlocking the bootloader is no big deal. Better than sitting through 6 more security updates. Thanks for the info.
mojorisin7178 said:
Ah unlocking the bootloader is no big deal. Better than sitting through 6 more security updates. Thanks for the info.
Click to expand...
Click to collapse
Just remember not to relock the bootloader unless you are 100% positive the phone is 100% stock. Personally, if I had a need to relock (which I can't think of a single reason why I would) I would flash a full factory image using the flash-all.bat file with the -w still in there to allow it to do a complete wipe off the phone. Just my personal paranoia but these threads are littered with the wreckage of uninformed locking of bootloaders...
Sent from my Pixel 2 XL using XDA Labs
CyberpodS2 said:
Just remember not to relock the bootloader unless you are 100% positive the phone is 100% stock. Personally, if I had a need to relock (which I can't think of a single reason why I would) I would flash a full factory image using the flash-all.bat file with the -w still in there to allow it to do a complete wipe off the phone. Just my personal paranoia but these threads are littered with the wreckage of uninformed locking of bootloaders...
Click to expand...
Click to collapse
That's good advice. Thank you
mojorisin7178 said:
That's good advice. Thank you
Click to expand...
Click to collapse
I'd add to that to flash both slots with a full factory wipe before relocking.
Related
Hi, just flashed the Google Factory Reset Image for GN (Android 4.0.2).
Should i lock the bootloader again (seems to be recommended from Google's side)..?
Im not gonna run custom software at this time.
no_johnr said:
Hi, just flashed the Google Factory Reset Image for GN (Android 4.0.2).
Should i lock the bootloader again (seems to be recommended from Google's side)..?
Im not gonna run custom software at this time.
Click to expand...
Click to collapse
No you should not. There is no reason to.
Sent from my Galaxy Nexus using Tapatalk
efrant said:
No you should not. There is no reason to.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
What he said. Just leave the bootloader unlocked and don't flash anything. You'll still receive ota.
Sent from my Galaxy Nexus using xda premium
The only danger of an unlocked boot loader comes from what you do with the phone from when it's unlocked .
If you feel confident with flashing etc then keep it open , if as you have stated you don't want to flash then you may as well just lock it . It's so simple to unlock in any case . Personal preference really
Merry Christmas
wardy said:
The only danger of an unlocked boot loader comes from what you do with the phone from when it's unlocked .
If you feel confident with flashing etc then keep it open , if as you have stated you don't want to flash then you may as well just lock it . It's so simple to unlock in any case . Personal preference really
Merry Christmas
Click to expand...
Click to collapse
Yes, but every time you unlock it wipes all your data...
Sent from my Galaxy Nexus using Tapatalk
Yep it sure does . Best to clear all data if you flash anything anyway . Either way it's up to you , no advice here is wrong . Your decision )
efrant said:
Yes, but every time you unlock it wipes all your data...
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
+1... leaving it unlocked does no harm as long as you dont do any mods afterwards. Leaving it unlocked allows you to back up game saves / app data if you decide to root/modify again.
Just if you send it back for manufacturer purposes.. relock the phone.
wardy said:
Yep it sure does . Best to clear all data if you flash anything anyway . Either way it's up to you , no advice here is wrong . Your decision )
Click to expand...
Click to collapse
I agree with you, that you should wipe everything when flashing a new ROM. However, I don't think I expressed my point properly: if your bootloader is locked, and say you want to flash a new radio, or a new recovery image (which do NOT require wiping your data at all), you CANNOT easily without wiping everything.
I have unlocked my gnex and rooted it.And then should I relock it?is there any difference whether relock it or not?thanks in advance
No difference just keep it open because if you ever have to reflash recovery or something you'll have to re unlock and that will wipe all data.
Sent From My Toro+ via White Tapatalk
I would read this...
http://forum.xda-developers.com/showthread.php?t=1898664
danger-rat said:
I would read this...
http://forum.xda-developers.com/showthread.php?t=1898664
Click to expand...
Click to collapse
so detail.thank you
The Play Store bought Galaxy Nexus doesn't even wipe when unlocking the bootloader, so there is no reason to bother relocking if that's what you have.
Sent from my Galaxy Nexus
andrewNY said:
The Play Store bought Galaxy Nexus doesn't even wipe when unlocking the bootloader, so there is no reason to bother relocking if that's what you have.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Seems like this shouldn't be true...
cwoggon said:
Seems like this shouldn't be true...
Click to expand...
Click to collapse
Agreed, but multiple users have reported this. I'm rather curious what's going on with those play store devices. It's hard to believe Google deliberately removed a crucial security feature. If unlocking the bootloader does not wipe userdata, everybody who's not using encryption is basically facing a security risk.
cwoggon said:
Seems like this shouldn't be true...
Click to expand...
Click to collapse
It's widespread enough to be true.
http://forum.xda-developers.com/showthread.php?t=1650830&page=22
Mach3.2 said:
It's widespread enough to be true.
http://forum.xda-developers.com/showthread.php?t=1650830&page=22
Click to expand...
Click to collapse
I was unaware, haven't been following the GNex forums for awhile. Seems like this could be a security issue...
My purpose to root is limited to supersu on the stock rom and xposed framework if possible. I do not want to flash any custom rom.
Is it possible to keep all DRM related functionalities with stock rom + root, with this method?
Is there some way to get root without unlocking the bootloader/wiping?
AFAIK root requires a custom recovery, to flash a custom recovery requires unlocked bootloader, so simple answer is no.
ghostofcain said:
AFAIK root requires a custom recovery, to flash a custom recovery requires unlocked bootloader, so simple answer is no.
Click to expand...
Click to collapse
What functionality do I loose with unlocking? Wiping data of course, but otherwise?
kokesh said:
What functionality do I loose with unlocking? Wiping data of course, but otherwise?
Click to expand...
Click to collapse
Nothing, the only downside is the need to wipe data.
ghostofcain said:
Nothing, the only downside is the need to wipe data.
Click to expand...
Click to collapse
I want sure about the fingerprint, etc. Thanks!
Damn, read a bit about what a bootloader is, its role is described in its name. Those fears are pointless.
Striatum_bdr said:
Damn, read a bit about what a bootloader is, its role is described in its name. Those fears are pointless.
Click to expand...
Click to collapse
Not necessary, coming from other devices. I am no noob, I know what BL is, but some manufacturers tie certain features to locked BL. Sony for example cripples camera when you unlock.
kokesh said:
Not necessary, coming from other devices. I am no noob, I know what BL is, but some manufacturers tie certain features to locked BL. Sony for example cripples camera when you unlock.
Click to expand...
Click to collapse
oneplus works same whether the bootlader is locked or unlocked. the only downside is as soon as you lock or unlock your bootloader your phone is wiped completely.
bonham1988 said:
oneplus works same whether the bootlader is locked or unlocked. the only downside is as soon as you lock or unlock your bootloader your phone is wiped completely.
Click to expand...
Click to collapse
How does it work with OTA updates? Do those work with TWRP?
kokesh said:
How does it work with OTA updates? Do those work with TWRP?
Click to expand...
Click to collapse
Otas dont work with twrp, oneplus releases a singed ota update on their forums usually within a week or two after the official ota. These singned updates can be flashed via twrp.
Sent from my OnePlus3 using XDA Labs
The only downside to unlocking the BL on the OP3 is that you get a warning message (http://i.imgur.com/88NcI2K.jpg) when booting the phone. Lots of people hate it, i like it personally. It makes pressing button combos to get into fastboot/recovery obsolete.
bonham1988 said:
Otas dont work with twrp, oneplus releases a singed ota update on their forums usually within a week or two after the official ota. These singned updates can be flashed via twrp.
Click to expand...
Click to collapse
And xda often have a TWRP flash able update before the OTA has reached everyone.
ghostofcain said:
AFAIK root requires a custom recovery ...
Click to expand...
Click to collapse
If flashing is the only way to root the device, then yes.
And unfortunately flashing seems to be the only way.
kokesh said:
What functionality do I loose with unlocking? Wiping data of course, but otherwise?
Click to expand...
Click to collapse
Security. Your data are no more safe if your phone get stolen.
kokesh said:
What functionality do I loose with unlocking? Wiping data of course, but otherwise?
Click to expand...
Click to collapse
All SafetyNet apps stop working (Android Pay, PokeGO etc.)
kokesh said:
What functionality do I loose with unlocking? Wiping data of course, but otherwise?
Click to expand...
Click to collapse
I loose Android Pay. That's what i miss
Sent from my OnePlus 3 using XDA Labs
fp1707 said:
I loose Android Pay. That's what i miss
Click to expand...
Click to collapse
Use Magisk and its all fine.
Puddi_Puddin said:
Use Magisk and its all fine.
Click to expand...
Click to collapse
I tried setting that up but i keep failing. Not sure what i'm doing wrong
NVM i see what i got wrong, now it works just fine
bonham1988 said:
oneplus works same whether the bootlader is locked or unlocked. the only downside is as soon as you lock or unlock your bootloader your phone is wiped completely.
Click to expand...
Click to collapse
This is not correct on OxygenOS 4.0.2, it's possible to root without wipe:
https://www.youtube.com/watch?v=tDRPWvYJYfU
I'm not rooted and my bootloader is still locked.
knitler said:
I'm not rooted and my bootloader is still locked.
Click to expand...
Click to collapse
I am assuming a Google phone.
You can drop out of the beta and you should get an OTA to take you back. However last I heard from others they are still waiting on their OTA. So that might require waiting a bit.
Anything else will wipe the phone. Unlocking it will trigger a wipe. If you are already unlocked you could do it....But you are not.
Everything you mentioned will wipe the device. The is no way to go back manually. The only way not to force wipe the phone is to wait for the release version of. 2 in a few months.
Sent from my Pixel using XDA-Developers Legacy app
Is 7.1.2 as awful as 7.1.1 was?
You'll need to wait for the mysterious OTA after you unenroll. That's your only option being that your bootloader is locked.
Sent from my Pixel XL
knitler said:
I'm not rooted and my bootloader is still locked.
Click to expand...
Click to collapse
No. End of discussion.
Sent from my Pixel using XDA-Developers Legacy app
So I bought my Google Pixel XL few days ago from eBay. The phone was used by the seller only for few days. Everything works fine except for the system update.
I'm actually able to download the 2017-03 security patch, but once the installation starts it fails in step 1 and I get the error message in the screenshot.
Did anybody experience a similar problem? Do you think I must return the phone?
Only reason I can think of that will bork an update is if one or more of the core apps are deleted or frozen. You verified you're all stock correct?
Sent from my Pixel XL using Tapatalk
tatootie67 said:
Only reason I can think of that will bork an update is if one or more of the core apps are deleted or frozen. You verified you're all stock correct?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
How can I do that ?
I checked that the phone is not rooted and I did a hard reset.
Elixir_ said:
How can I do that ?
I checked that the phone is not rooted and I did a hard reset.
Click to expand...
Click to collapse
The seller may have had it rooted. And he didn't install factory firmware, before he sold it to u. Maybe he did an unroot root in SuperSU and that is not a sure thing. Just a guess. I would go to Google site and fastboot newest factory image.
Edit. Is the bootloader unlocked?
Check in your about phone section and see what version, kernel, and baseband your on. Or screenshot it and post it here
Sent from my Pixel XL using Tapatalk
mac796 said:
The seller may have had it rooted. And he didn't install factory firmware, before he sold it to u. Maybe he did an unroot root in SuperSU and that is not a sure thing. Just a guess. I would go to Google site and fastboot newest factory image.
Edit. Is the bootloader unlocked?
Click to expand...
Click to collapse
This is what I get when I boot into bootloader
tatootie67 said:
Check in your about phone section and see what version, kernel, and baseband your on. Or screenshot it and post it here
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Here is a screenshot
Elixir_ said:
This is what I get when I boot into bootloader
Click to expand...
Click to collapse
Is it a Google version if it is I would unlock it and flash the new factory image. If it's not I would prob try to get money back. I'm not sure if you can flash factory image with locked bootloader. I think you can go ahead but not backwards. You will have to make sure.
You can use adb to sideload the signed ota zip in stock recovery with a locked bl.
You shouldn't have to do any of that if it's stock unrooted. But unfortunately, you don't know what the previous owner may have done.
Adb sideload might be your only choice to truly get back to stock.
Sent from my Pixel XL using Tapatalk
toknitup420 said:
You can use adb to sideload the signed ota zip in stock recovery with a locked bl.
Click to expand...
Click to collapse
I think this is the best place to start. Here are some directions for the OP.
Get the fastboot adb tools from google. Unzip them onto your computer's desktop.
https://developer.android.com/studio/releases/platform-tools.html
Then get the full ota zip and follow the directions on this page.
https://developers.google.com/android/ota
Keep us posted, we will help you.
TonikJDK said:
I think this is the best place to start. Here are some directions for the OP.
Get the fastboot adb tools from google. Unzip them onto your computer's desktop.
https://developer.android.com/studio/releases/platform-tools.html
Then get the full ota zip and follow the directions on this page.
https://developers.google.com/android/ota
Keep us posted, we will help you.
Click to expand...
Click to collapse
Which OTA should I download ? Sorry for my ignorance, it's my first Google/stock android phone...
Elixir_ said:
Which OTA should I download ? Sorry for my ignorance, it's my first Google/stock android phone...
Click to expand...
Click to collapse
XL right? Under the Marlin for XLsection the last one if your carrier is Rogers. Second to the last for anything else.
Elixir_ said:
Which OTA should I download ? Sorry for my ignorance, it's my first Google/stock android phone...
Click to expand...
Click to collapse
You should use the full flashable image and not the OTA to return to stock from this page:
https://developers.google.com/android/images
Using the specific image 7.1.1, second from bottom of Pixel XL seection.
Ok thanks a lot guys, I'll flash it once I get home.
Just to be sure, this won't void the warranty right ? because I checked with Google and the phone is still under warranty.
Elixir_ said:
Ok thanks a lot guys, I'll flash it once I get home.
Just to be sure, this won't void the warranty right ? because I checked with Google and the phone is still under warranty.
Click to expand...
Click to collapse
No it won't void the warranty.
IIIIkoolaidIIII said:
You should use the full flashable image and not the OTA to return to stock from this page:
https://developers.google.com/android/images
Using the specific image 7.1.1, second from bottom of Pixel XL seection.
Click to expand...
Click to collapse
He can't his bootloader is locked. No flashing images
toknitup420 said:
He can't his bootloader is locked. No flashing images
Click to expand...
Click to collapse
you can flash official signed images with locked bootloader, you just can't flash anything non official.
I did ti on my own only 2 weeks ago when messed up sometyhing with beta builds.
IIIIkoolaidIIII said:
you can flash official signed images with locked bootloader, you just can't flash anything non official.
I did ti on my own only 2 weeks ago when messed up sometyhing with beta builds.
Click to expand...
Click to collapse
So you ran the flash all on a locked bootloader?
toknitup420 said:
So you ran the flash all on a locked bootloader?
Click to expand...
Click to collapse
yes as i have many times before
Sent from my Pixel XL using XDA Labs