Got my 5X earlier last week, but I haven't been able to get the MDB08I OTA update. Anyone else not getting it? Is there anyway to force it?
Thanks!
You can sideload it if you can download the ota file. Google rolls it out based on some algorithm based on IMEI. You'll get it eventually.
Still waiting for my USB-C to A cable to come in. Just wasn't sure if something else was up with my phone. Didn't know the rollout was based on IMEI; the more you know =)
Thanks!
i havent gotten it yet either :/
i cant even sideload it.. whenever i do "adb devices" when the phone is in recovery mode.. i do not see the device..
on linux & windows. :/
so lame.
Mine was telling me there was an update as soon as I unboxed it and turned the WiFi on. Weird that you aren't getting the update.
On another side note. I've had no problem with getting adb to work.
I've had my 5x since last Monday (19th October) and I don't have it yet either. I'm in the UK.
I'm on MDA89E after getting from cpw yestaday and unboxing didn't get any update yet but loving the 5x so far
Sent from my Nexus 5X using Tapatalk
I think updates are delivered depending on which carrier you are with (as determined by which company's SIM is inserted in the device). It's possible that there isn't one associated with the carrier you are with.
myphone12345 said:
I think updates are delivered depending on which carrier you are with (as determined by which company's SIM is inserted in the device). It's possible that there isn't one associated with the carrier you are with.
Click to expand...
Click to collapse
I thought the point of Nexus range was there was no delay due to carriers?
myphone12345 said:
I think updates are delivered depending on which carrier you are with (as determined by which company's SIM is inserted in the device). It's possible that there isn't one associated with the carrier you are with.
Click to expand...
Click to collapse
Nope. I had no SIM installed when I was alerted to the update. Has nothing to do with SIM or carrier.
Does the bootloader have to be locked to get otas?
nyjumpman said:
Does the bootloader have to be locked to get otas?
Click to expand...
Click to collapse
Probably it's OK to be unlocked, but probably it's not OK to have a custom recovery if you want OTA's. (and want them installed). Best bet is to download B08I and install it via the batch file.
To some other poster in this thread asking about being unable to see phone from adb when recovery is booted up: If it's stock recovery, that makes sense, but if it's custom recovery, you should see adb devices having output.
oxfordmark said:
I thought the point of Nexus range was there was no delay due to carriers?
Click to expand...
Click to collapse
From what I understand, Google has now also started sending out mini updates which are contingent on what company's SIM is in the phone.
myphone12345 said:
From what I understand, Google has now also started sending out mini updates which are contingent on what company's SIM is in the phone.
Click to expand...
Click to collapse
Like I posted earlier. I was alerted to the update and had no SIM installed.
myphone12345 said:
From what I understand, Google has now also started sending out mini updates which are contingent on what company's SIM is in the phone.
Click to expand...
Click to collapse
Oh right, must be for things like wifi calling.
manilaboy1vic said:
i havent gotten it yet either :/
i cant even sideload it.. whenever i do "adb devices" when the phone is in recovery mode.. i do not see the device..
on linux & windows. :/
so lame.
Click to expand...
Click to collapse
Its early and I haven't had my coffee yet so maybe I'm mistaken, but if you are in recovery mode I believe you should be using the command "fastboot devices" to check if your computer can see your phone.
http://www.droid-life.com/2015/10/21/nexus-5x-receiving-update-today-to-build-mdb08i/
Just followed these instructions and the associated links and 30 minutes later ... updated FTW.
Was having problems, at first, with my phone to being recognized. Either the initial usb 2.0 port was jacked or not, I switched to another port and made sure the cable was seated properly and it was picked up right away.
My N5X on AT&T got this update last Tuesday when I got the phone. My girlfriends N5X on Verizon did not yet get the update OTA. Might have to do with carrier?
I always set my phone up without a SIM. Got the update right away during the set up process.
Jexx11 said:
Its early and I haven't had my coffee yet so maybe I'm mistaken, but if you are in recovery mode I believe you should be using the command "fastboot devices" to check if your computer can see your phone.
Click to expand...
Click to collapse
thanks.. that cmd worked..
Android is upgrading... (w00t)
was easier for me to get it going on linux ubuntu.. now onto the hotspot tutorial
Related
Has anyone grabbed the 4.0.2 update file yet and examined it? I'm curious as to the real reason this launch was "delayed" (why stock was held at stores with repeated notices not to sell until further notice)...
The worst in me fears it affects the NFC stack, either to disable Google Wallet, or pave the way for ISIS' api's, or both...
No one? Can we reason out the url?
I believe that the factory images uploaded by JBQ for the VZW Nexus today contain the changes you seek. If not then I'm sure someone will post the update for ya
I don't really understand why you want/need them though, from what I've heard they are just bugfixes for the VZW Nexus.. Might be wrong on that point though!
EDIT--------->
Oh, just saw that you are looking for a couple of specific changes.... Sorry, long day at work has made me a bit zombie-ish.
Here's VZW description of the update. It helps 3G/4G, and kills DivX playback.
http://www.droid-life.com/2011/12/1...-will-receive-an-update-here-are-the-details/
http://groups.google.com/group/android-building/msg/2cd2b16ed56a7e84?pli=1
GSM: http://www.google.com/url?sa=D&q=https://dl.google.com/dl/android/aosp/yakju-icl53f-factory-89fccaac.tgz&usg=AFQjCNFacF_Wig9P8BajyVePTzKUcREmtA
Verizon: http://www.google.com/url?sa=D&q=https://dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz&usg=AFQjCNFgH762OhQZddkNiI9yTxKdUyW1tA
Simba90 said:
I believe that the factory images uploaded by JBQ for the VZW Nexus today contain the changes you seek. If not then I'm sure someone will post the update for ya
Click to expand...
Click to collapse
Thanks, I'll check them out later
Simba90 said:
I don't really understand why you want/need them though, from what I've heard they are just bugfixes for the VZW Nexus.. Might be wrong on that point though!
Click to expand...
Click to collapse
well the phones were sitting around waiting for something, then VZW trained employees about the update soon after customers activate their devices, and release the phone shortly afterwards.
It could just be bug fixes (and I could be out in left field here), but I am thinking something almost made it out the door on the phones that Verizon wanted changed or deleted.
dnlsmy said:
Here's VZW description of the update. It helps 3G/4G, and kills DivX playback.
Click to expand...
Click to collapse
Yeah the DivX might be it, but as buggy as other devices as Verizon has launched, I don't think this was a quality control issue. It was most likely something that would have cost them money. I'm thinking either something in the mobile hotspot functionality or NFC payments (Google Wallet's embedded "Secure Element"), both of which Verizon would stand to make money on, if the free versions were disabled and users were locked into their options.
This is not something that would be in a press release, it will only be visible in the code.
Has anyone tried it out? This would be awesome..just don't have a USB OTG Cable here :/
"I believe that USB OTG is in ICL53F, yes."
https://twitter.com/#!/jbqueru/status/147431593005416448
MysteriousDiary said:
Has anyone tried it out? This would be awesome..just don't have a USB OTG Cable here :/
"I believe that USB OTG is in ICL53F, yes."
https://twitter.com/#!/jbqueru/status/147431593005416448
Click to expand...
Click to collapse
Yes I just updated my GSM version to ICL53F. Works just fine.
Used images from: http://bit.ly/rEhnbD
Attaching screenshot with system info after the update.
Is it possible to upgrade without having root??
TheChiller said:
Is it possible to upgrade without having root??
Click to expand...
Click to collapse
Yes if you unlocked the bootloader. Root is not needed at all to do update with Google's official images.
okay, when do you think the OTA is coming??
I got the OTA update today. Just pulled my battery out a few times and it popped up.
What are the improvements?
Is there a changelog?
Still no support for usb stick.
Are you GSM or VZW version? I just checked no update yet
dr.duct_mossburg said:
I got the OTA update today. Just pulled my battery out a few times and it popped up.
Click to expand...
Click to collapse
Sent from my Galaxy Nexus using XDA App
macfre said:
Yes if you unlocked the bootloader. Root is not needed at all to do update with Google's official images.
Click to expand...
Click to collapse
How do I flash using fast boot step by step I have done tons of Google searches and have not found much of anything that shows me step by step on how to flash.
I have the boot loader unlocked but cant fugure how to use flash-all.sh like it says @
this site
http://groups.google.com/group/andr...a058a737b9/43c3a418144fc6c5?#43c3a418144fc6c5
THANK YOU!
if you want to force the device to check for updates immediately enter *#*#checkin#*#* on the dialer keypad ( *#*#2432546#*#*)
alpha2beta said:
How do I flash using fast boot step by step I have done tons of Google searches and have not found much of anything that shows me step by step on how to flash.
I have the boot loader unlocked but cant fugure how to use flash-all.sh like it says @
this site
http://groups.google.com/group/andr...a058a737b9/43c3a418144fc6c5?#43c3a418144fc6c5
THANK YOU!
Click to expand...
Click to collapse
That script is a bash script, won't run in windows as you don't have a bash shell
Assuming the packages found here: https://groups.google.com/forum/#!msg/android-building/pJDz7jxCNkk/hH5q1W6x0iwJ
If you have the bootloader unlocked (GSM instructions) :
Code:
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
fastboot update image-yakju-icl53f.zip
CDMA instructions
Code:
fastboot flash bootloader bootloader-toro-primekj10.img
fastboot flash radio-cdma radio-cdma-toro-i515.ek01.img
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot update image-mysid-itl41d.zip
Note: Adding -w to the update will wipe before updating.
Note: Rebooting pre update is necessary as it asserts that boot loader version and requires the updated version out of the box.
Thanks! krohnjw that helped alot!
Have U unlocked the Bootloader or Rooted your device before U got an OTA?
Thanks, I really don't know what cause the OTA delayed problem .
So, I was installing ADB and such with android toolkit, It rebooted my phone into FASTBOOT in order to check the status of bootloader. Got the info I needed, then the phone rebooted, I went to download depixel8 and get ready to unlock and start the root shenanigans...and boom. The phone installs the NMF26U update without me even telling it to/letting it. Am I completely screwed on here as far as now being able to root and unlock my phone?
SomeFknGuy said:
So, I was installing ADB and such with android toolkit, It rebooted my phone into FASTBOOT in order to check the status of bootloader. Got the info I needed, then the phone rebooted, I went to download depixel8 and get ready to unlock and start the root shenanigans...and boom. The phone installs the NMF26U update without me even telling it to/letting it. Am I completely screwed on here as far as now being able to root and unlock my phone?
Click to expand...
Click to collapse
The toolkit updated your phone, or your phone took an ota? The toolkit should not have been able to update if you weren't already unlocked. Unless there's something I'm missing here..
k.s.deviate said:
The toolkit updated your phone, or your phone took an ota? The toolkit should not have been able to update if you weren't already unlocked. Unless there's something I'm missing here..
Click to expand...
Click to collapse
The OTA update notification was there, but I've been avoiding and ignoring it. When ADB/Toolkit rebooted my phone to check the status of the bootloader all was good, the second my phone rebooted from all that the notification bar showed that it was finishing the update. Went into the settings window to check the build version and it is now showing 7.1.1 and NMF26U. I'm without a solid hotspot work around now since foxfi is dead and I'm too lazy to pull my phone case constantly to remove and replace the sim heh. Just wondering what toolkit triggered to allow and instigate the update install
SomeFknGuy said:
The OTA update notification was there, but I've been avoiding and ignoring it. When ADB/Toolkit rebooted my phone to check the status of the bootloader all was good, the second my phone rebooted from all that the notification bar showed that it was finishing the update. Went into the settings window to check the build version and it is now showing 7.1.1 and NMF26U. I'm without a solid hotspot work around now since foxfi is dead and I'm too lazy to pull my phone case constantly to remove and replace the sim heh. Just wondering what toolkit triggered to allow and instigate the update install
Click to expand...
Click to collapse
I'm pretty sure the ota automatically downloads, when the toolkit rebooted the device it finished the install. If your device is Verizon then yes I think you're boned.
k.s.deviate said:
I'm pretty sure the ota automatically downloads, when the toolkit rebooted the device it finished the install. If your device is Verizon then yes I think you're boned.
Click to expand...
Click to collapse
oy... i was afraid of that... maybe someone can find a work around to at least get my hot spot working...
Is there no way to change the boot slot? Old system is still on the now not active bootslot.
So my question is there a way to change the bootslot without twrp.
mikaole said:
Is there no way to change the boot slot? Old system is still on the now not active bootslot.
So my question is there a way to change the bootslot without twrp.
Click to expand...
Click to collapse
There is. "fastboot --set-active=_a" (or _b). Here is a list of all known fastboot commands. https://forum.xda-developers.com/pixel-xl/how-to/pixel-xl-fastboot-commands-t3490080
mikaole said:
Is there no way to change the boot slot? Old system is still on the now not active bootslot.
So my question is there a way to change the bootslot without twrp.
Click to expand...
Click to collapse
Isn't the old system partition updated in the background then after the update is complete? Even if it isn't, the radio and bootloader are still updated.
Sent from my Pixel XL
imnuts said:
Isn't the old system partition updated in the background then after the update is complete? Even if it isn't, the radio and bootloader are still updated.
Sent from my Pixel XL
Click to expand...
Click to collapse
Nope, they aren't updated until a new update comes. Also there are two slots for radio and bootloader just like everything else so in theory if he could use fastboot he could switch boot slots.
Sent from my Pixel XL using Tapatalk
superchilpil said:
Nope, they aren't updated until a new update comes. Also there are two slots for radio and bootloader just like everything else so in theory if he could use fastboot he could switch boot slots.
Click to expand...
Click to collapse
Unfortunately this won't help. If he installed the update his bootloader is now locked and there is no way to unlock it.
aholeinthewor1d said:
Unfortunately this won't help. If he installed the update his bootloader is now locked and there is no way to unlock it.
Click to expand...
Click to collapse
I sry to say..but I completely agree. If your on 7.1.1 and still locked your stuck locked.
SomeFknGuy said:
oy... i was afraid of that... maybe someone can find a work around to at least get my hot spot working...
Click to expand...
Click to collapse
Pop the sim card, push it back in, wait 4 seconds, turn on hotspot.
No there is a way past this it happened to me, @jcase knows the command you need to get by this.
mwalt201 said:
Pop the sim card, push it back in, wait 4 seconds, turn on hotspot.
Click to expand...
Click to collapse
actually been doing just this. just a little bit of a pain to do with the cover that I'm running. worth it though, until verizon figures out a fix for that :|
Took an OTA and now whenever I turn the device on it says in red letters: "Your device is corrupt. It can't be trusted and may not work properly". I can still boot into the OS normally. I can still access fastboot. I can still access recovery. I have done many searches and people keep saying to relock the bootloader or unlock the bootloader and flash stock firmware. There's no way to do either because this Verizon variant is locked down like Fort Knox. I don't understand why the bootloader has to be unlocked to flash STOCK firmware straight from Verizon. Smh. Anyways, does anyone have any ideas. about how to get rid of this message?
ClassickWORLD said:
Took an OTA and now whenever I turn the device on it says in red letters: "Your device is corrupt. It can't be trusted and may not work properly". I can still boot into the OS normally. I can still access fastboot. I can still access recovery. I have done many searches and people keep saying to relock the bootloader or unlock the bootloader and flash stock firmware. There's no way to do either because this Verizon variant is locked down like Fort Knox. I don't understand why the bootloader has to be unlocked to flash STOCK firmware straight from Verizon. Smh. Anyways, does anyone have any ideas. about how to get rid of this message?
Click to expand...
Click to collapse
You could side load the Google OTA image and see if that fixes it. Or just wait until next week and see if the March OTA fixes it. If your device is working properly, I wouldn't worry too much about it.
Badger50 said:
You could side load the Google OTA image and see if that fixes it. Or just wait until next week and see if the March OTA fixes it. If your device is working properly, I wouldn't worry too much about it.
Click to expand...
Click to collapse
I have moved on to the iPhone 8 Plus. I sold the device and had it returned because of that message... and now I want to sell it again. I just need to get rid of it. So you are saying that I can sideload via adb even on a Verizon device with a locked bootloader?
ClassickWORLD said:
I have moved on to the iPhone 8 Plus. I sold the device and had it returned because of that message... and now I want to sell it again. I just need to get rid of it. So you are saying that I can sideload via adb even on a Verizon device with a locked bootloader?
Click to expand...
Click to collapse
While I haven't done it personally, I've seen several people do just that from stock recovery. At worst, the install will fail and nothing will be changed. Unlocking the bootloader is mainly for flashing factory images and rooting, not OTA's. Just follow the instructions from Google and see what happens. In your current situation, you really have nothing to lose.
https://developers.google.com/android/ota
ClassickWORLD said:
I have moved on to the iPhone 8 Plus. I sold the device and had it returned because of that message... and now I want to sell it again. I just need to get rid of it. So you are saying that I can sideload via adb even on a Verizon device with a locked bootloader?
Click to expand...
Click to collapse
Yes, I have a Verizon version of the Pix2-XL, and I have run 4 or 5 times on it.
https://developers.google.com/android/ota
Use these instructions exactly, and be sure you have the newest Android Tools.
This should take care of your error message.
michaelbsheldon said:
Yes, I have a Verizon version of the Pix2-XL, and I have run 4 or 5 times on it.
https://developers.google.com/android/ota
Use these instructions exactly, and be sure you have the newest Android Tools.
This should take care of your error message.
Click to expand...
Click to collapse
Thanks for the conformation my friend. I kinda feel sorry for that poor guy, he went to an iphone!!.....oh the horror! ??????
michaelbsheldon said:
Yes, I have a Verizon version of the Pix2-XL, and I have run 4 or 5 times on it.
https://developers.google.com/android/ota
Use these instructions exactly, and be sure you have the newest Android Tools.
This should take care of your error message.
Click to expand...
Click to collapse
Hey thanks for that. The latest image I see for the Verizon Pixel XL 2 is for 8.0.0 from Nov 2017. I am on 8.1. So I have to downgrade? Is that even possible?
ClassickWORLD said:
Hey thanks for that. The latest image I see for the Verizon Pixel XL 2 is for 8.0.0 from Nov 2017. I am on 8.1. So I have to downgrade? Is that even possible?
Click to expand...
Click to collapse
Huh?? You have a P2XL right?? It's right there at the bottom of the P2XL section.
What build month are you currently on?
ClassickWORLD said:
Hey thanks for that. The latest image I see for the Verizon Pixel XL 2 is for 8.0.0 from Nov 2017. I am on 8.1. So I have to downgrade? Is that even possible?
Click to expand...
Click to collapse
You do want the February one. It's for all phones including Verizon.
Badger50 said:
Huh?? You have a P2XL right?? It's right there at the bottom of the P2XL section.
What build month are you currently on?
Click to expand...
Click to collapse
So I can flash that with no radio issues? I thought OPM1 is google, OPM2 is Telus only, and OPD3 is Verizon only? I have a Verizon P2XL
Edit: I think I've found my issue. The person who had the device before me must have sideloaded 8.1.0 (OPM1.171019.018, Feb 2018)" to this device and that may be the reason for the error. I am thinking because that's not the Verizon P2XL firmware but the Google P2XL device firmware.
michaelbsheldon said:
You do want the February one. It's for all phones including Verizon.
Click to expand...
Click to collapse
Ok gotcha. Downloading now as we speak.
Badger50 said:
Thanks for the conformation my friend. I kinda feel sorry for that poor guy, he went to an iphone!!.....oh the horror! ??
Click to expand...
Click to collapse
Lol I still have my trusty ol' Nexus 6P as my secondary device.
WoW this download link is really slow. Downloading at 50 KB/s. Says 9 hours left. I have fiber speeds for my internet. Anyone know of any alternative download locations for this OTA?
Edit: Rebooted my router and that fixed it. It downloaded in 2 minutes.
ClassickWORLD said:
WoW this download link is really slow. Downloading at 50 KB/s. Says 9 hours left. I have fiber speeds for my internet. Anyone know of any alternative download locations for this OTA?
Edit: Rebooted my router and that fixed it. It downloaded in 2 minutes.
Click to expand...
Click to collapse
Fixed and you're a happy camper, right?
P.S. try a factory reset to complete this
You guys are great. The sideload fixed the problem! I truly appreciate you guys. Thanks a lot.
ClassickWORLD said:
Lol I still have my trusty ol' Nexus 6P as my secondary device.
Click to expand...
Click to collapse
Ok bruh, your forgiven :laugh: Did you get your problem fixed?
Oooops....never mind. I see that you did :good:
Is this the method for unlocking a Verizon Pixel 2 XL? Or just to fix the message this person was receiving. I want to buy a verizon Pixel 2 XL today in the store and do this vs waiting on google to deliver it.
tradermatt said:
Is this the method for unlocking a Verizon Pixel 2 XL? Or just to fix the message this person was receiving. I want to buy a verizon Pixel 2 XL today in the store and do this vs waiting on google to deliver it.
Click to expand...
Click to collapse
There is no method to unlock the Verizon P2XL!!
Hey, trying to use skipsoft to unlock my bootloader, install twrp, etc. I select the unlock bootloader option, it reboots to fastboot, notes that the bootloader is locked, but then says bootloader already unlocked no data will be wiped rebooting to android. What can I try to get around this? Thanks
GunnermanBill said:
Hey, trying to use skipsoft to unlock my bootloader, install twrp, etc. I select the unlock bootloader option, it reboots to fastboot, notes that the bootloader is locked, but then says bootloader already unlocked no data will be wiped rebooting to android. What can I try to get around this? Thanks
Click to expand...
Click to collapse
Which phone variant do you have? What is the status of the "Allow OEM Unlocking toggle" under Developer Settings? That has to be toggled on first. It should be clearly "on" and not greyed out. If you have the 2XL, you can run the IMEI through this link to verify the variant you have. Under Buyer Name It should say "Google_Open_64GB" or similar.
v12xke said:
Which phone variant do you have? What is the status of the "Allow OEM Unlocking toggle" under Developer Settings? That has to be toggled on first. It should be clearly "on" and not greyed out. If you have the 2XL, you can run the IMEI through this link to verify the variant you have. Under Buyer Name It should say "Google_Open_64GB" or similar.
Click to expand...
Click to collapse
variant is GOOGLE_VRZ_128G
Allow Oem Unlocking Toggle is greyed out for some reason.
GunnermanBill said:
variant is GOOGLE_VRZ_128G
Allow Oem Unlocking Toggle is greyed out for some reason.
Click to expand...
Click to collapse
Well unfortunately there is your reason. Your bootloader cannot be unlocked because your variant is Verizon. Verizon's are bootloader locked and this cannot be overcome. As such you will not be able to flash a custom recovery, flash full Google factory images, or root the phone.
v12xke said:
Well unfortunately there is your reason. Your bootloader cannot be unlocked because your variant is Verizon. Verizon's are bootloader locked and this cannot be overcome. As such you will not be able to flash a custom recovery, flash full Google factory images, or root the phone.
Click to expand...
Click to collapse
Well that's new as far as google phones go
GunnermanBill said:
Well that's new as far as google phones go
Click to expand...
Click to collapse
Sorry to say but it's not new for Verizon variants of Pixel or Nexus (or almost any other phone Verizon sells with very few exceptions). Verizon refuses to allow their users to unlock their own bootloader- including Google phones. Your Verizon phone is bootloader-locked and there is nothing you can do about it. Verizon phones are sometimes sold at deep discounts with the hook of a multi-year service agreement. Have you ever heard the term "The Red Devil" used for Verizon? It's not new either. Sorry to bring you the bad news, but it is true. There are many threads here on XDA which will confirm this. Best of luck.
v12xke said:
Sorry to say but it's not new for Verizon variants of Pixel or Nexus (or almost any other phone Verizon sells with very few exceptions). Verizon refuses to allow their users to unlock their own bootloader- including Google phones. Your Verizon phone is bootloader-locked and there is nothing you can do about it. Verizon phones are sometimes sold at deep discounts with the hook of a multi-year service agreement. Have you ever heard the term "The Red Devil" used for Verizon? It's not new either. Sorry to bring you the bad news, but it is true. There are many threads here on XDA which will confirm this. Best of luck.
Click to expand...
Click to collapse
It's no big deal, my gf took the upgrade to Pie and hates it and I was just gonna root mine before it started prompting me. Someone will get it unlocked in a year or something like always. As far as I can tell the pixel line is the first that Verizon did this with, we had Galaxy Nexus' a long time ago and those weren't locked.
GunnermanBill said:
It's no big deal, my gf took the upgrade to Pie and hates it and I was just gonna root mine before it started prompting me. Someone will get it unlocked in a year or something like always. As far as I can tell the pixel line is the first that Verizon did this with, we had Galaxy Nexus' a long time ago and those weren't locked.
Click to expand...
Click to collapse
Verizon users have been hoping for an unlock method since the 2XL's release.
Look at this thread for more information on that.
xunholyx said:
Verizon users have been hoping for an unlock method since the 2XL's release.
Look at this thread for more information on that.
Click to expand...
Click to collapse
i mean it only happened for the regular pixels in 2016. I'm in no rush, like i said NBD
I'm also trying to relock, just used your link. I'm on the google version running android p. I unlocked a long time ago, but never ended up doing anything with it. I have an RMA coming and the option is grayed out and wugs is failing ... .. Thought about trying to downgrade to O and trying my luck on "android o"
kickenwing13 said:
I'm also trying to relock, just used your link. I'm on the google version running android p. I unlocked a long time ago, but never ended up doing anything with it. I have an RMA coming and the option is grayed out and wugs is failing ... .. Thought about trying to downgrade to O and trying my luck on "android o"
Click to expand...
Click to collapse
You may not have unlocked critical. There are two separate commands. Anyway, since your RMA is on the way just wait until it arrives, update it to Pie and then do a data transfer for all your settings/data. Once your new phone is set up, just do a FDR before sending it back. You do NOT need to relock the phone. They do not care. Just FDR to wipe your personal data off the phone. Lastly, you want to de-register or remove that old phone from your Google account before sending it back. Best of luck.
v12xke said:
You may not have unlocked critical. There are two separate commands. Anyway, since your RMA is on the way just wait until it arrives, update it to Pie and then do a data transfer for all your settings/data. Once your new phone is set up, just do a FDR before sending it back. You do NOT need to relock the phone. They do not care. Just FDR to wipe your personal data off the phone. Lastly, you want to de-register or remove that old phone from your Google account before sending it back. Best of luck.
Click to expand...
Click to collapse
Thank you so much dude. I know you're right . I used the toolkit and nothing after unlocking ever worked and I'm assuming it's because of that .... I've been telling myself I need to learn it the old fashioned way but have never been able to properly install adb and all that stuff..
kickenwing13 said:
Thank you so much dude. I know you're right . I used the toolkit and nothing after unlocking ever worked and I'm assuming it's because of that .... I've been telling myself I need to learn it the old fashioned way but have never been able to properly install adb and all that stuff..
Click to expand...
Click to collapse
I would encourage you to just "install" adb/fastboot. It is literally opening a zip file and extracting everything into a new folder. Then adding that folder to your path statement (Windows) means you can use the command from anywhere. For example I created a folder c:\adb and just dumped the files in there. I see you already have opened the flash-all.bat script and are poking around ... so in the beginning you can just cut and paste those commands if you want to do things manually -or- just run the script. You can always get the latest standalone binaries direct from Google. Ditch the toolkits and you will be glad you did. It is just not that hard, and you will know how to get yourself out of a jam later. :good:
I DID IT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! It was cake. Thanks for the awesome directions. I just opened up through cmd insead of your second step, but dude! clutch . I relocked it.. took 2 seconds once my buddy helped me tpye my first command. But thank you again! Now debating getting more into it. This is the first phone i haven't installed a custom ROM on because the unlock and root stuff absolutely failed...
I'm using a sim-unlocked Verizon pixel 3 on Fi and (though I've hit the 'check for update' button, which should now get the update whether it was automatically available via OTA or not) I still haven't received the December security patch. I would just flash it, but the Verizon model has a locked bootloader so unfortunately that isn't an option. Is anyone else having this same issue? I know some over on Reddit were.
jacobsface said:
I'm using a sim-unlocked Verizon pixel 3 on Fi and (though I've hit the 'check for update' button, which should now get the update whether it was automatically available via OTA or not) I still haven't received the December security patch. I would just flash it, but the Verizon model has a locked bootloader so unfortunately that isn't an option. Is anyone else having this same issue? I know some over on Reddit were.
Click to expand...
Click to collapse
Nothing wrong with your phone. Since you are BL locked you are just somewhere in the queue of the phased roll-outs and they complete 2-3 weeks after the first Monday every month. It's unfortunate because with some other GSM carriers, when you pay the phone off you can unlock the BL. The Red Devil does not work like that and there is no workaround.
v12xke said:
Nothing wrong with your phone. Since you are BL locked you are just somewhere in the queue of the phased roll-outs and they complete 2-3 weeks after the first Monday every month. It's unfortunate because with some other GSM carriers, when you pay the phone off you can unlock the BL. The Red Devil does not work like that and there is no workaround.
Click to expand...
Click to collapse
Dang it sucks that the rollout can take that long. Someone on Reddit had said it should be out to all by yesterday because the patch is dated the 5th, but that obviously didn't happen. The thing is I didn't even buy it from Verizon, I got it from someone on Ebay who just said it was the unlocked version. At the time I didn't realize Verizon variants were bootloader locked and didn't think to ask for clarification on the bootloader. There's a whole other thread here for trying to unlock it that I've been following but there hasn't been much luck besides luck rma's. It'd be a lot easier if I didn't live in rural West Virginia with service only from a few locked down carriers who barely support any phones besides Galaxies and iPhones. Oh well!
Yeah, I haven't received Dec OTA either. I have a BL unlocked 3XL from Google Fi and normally flash the FULL factory image but I took the OTA last month and like that process better so I'll keep waiting...
jacobsface said:
Dang it sucks that the rollout can take that long. Someone on Reddit had said it should be out to all by yesterday because the patch is dated the 5th, but that obviously didn't happen. The thing is I didn't even buy it from Verizon, I got it from someone on Ebay who just said it was the unlocked version. At the time I didn't realize Verizon variants were bootloader locked and didn't think to ask for clarification on the bootloader. There's a whole other thread here for trying to unlock it that I've been following but there hasn't been much luck besides luck rma's. It'd be a lot easier if I didn't live in rural West Virginia with service only from a few locked down carriers who barely support any phones besides Galaxies and iPhones. Oh well!
Click to expand...
Click to collapse
Hear ya. True statement, the images really *are** out to all who can flash it the first Monday of each month, and YES you can manually flash the OTA image with a locked bootloader. You should read up on getting ADB/Fastboot running on your PC. Instructions on how to flash OTA's are on Google's developer page. Get the latest toolkit you need HERE.* Getting ADB/Fastboot up and running on your PC is a necessary lifesaving skill and really just takes reading and paying attention. Off you go.
Just giving my 2 cents. Stock 3XL. No update here yet either.
v12xke said:
Hear ya. True statement, the images really *are** out to all who can flash it the first Monday of each month, and YES you can manually flash the OTA image with a locked bootloader. You should read up on getting ADB/Fastboot running on your PC. Instructions on how to flash OTA's are on Google's developer page. Get the latest toolkit you need HERE.* Getting ADB/Fastboot up and running on your PC is a necessary lifesaving skill and really just takes reading and paying attention. Off you go.
Click to expand...
Click to collapse
It worked finally! See, Verizon hid their recovery mode behind a button combination on the bootloader. That, and forcing anything to happen from the bootloader screen itself via adb was a no go. But, you have to do a button combination on it to be able to select to apply update from ADB
jacobsface said:
It worked finally! See, Verizon hid their recovery mode behind a button combination on the bootloader. That, and forcing anything to happen from the bootloader screen itself via adb was a no go. But, you have to do a button combination on it to be able to select to apply update from ADB
Click to expand...
Click to collapse
Happy to see you were able to get it done. After a couple of times it just becomes routine. As for recovery button press, we can't blame that one on Verizon. That is the how the stock recovery works even on unlocked phones directly from Google. Don't feel bad, lots of people get tripped up on that too. Cheers :good: