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 .
Hey there,
So I just got my GSM Galaxy Nexus in the mail today and found a couple things to be a bit odd. You see, my package came with 2 Galaxy Nexuses (or nexi?) and my brother's phone seemed completely normal. It had Android 4.0.4 which he instantly got an update for Jellybean. My phone on the other hand was a bit off, as stated previously. My Galaxy Nexus shipped with Android 4.0.1, when i went to the "about phone" tab, there was no option to even check for a system update, my lock screen doesn't work (security settings are on slide yet the power button just wakes my screen and no sliding to unlock required), I have no market or google play store, I can't add a Gmail account under the "accounts and sync" tab, and my home button wasn't working (factory resetting fixed this).
I'm honestly just stuck on what to do about this device. I've factory reset this device 5 times already and nothing else has worked except for fixing the home button which wasn't working on my initial boot up.
Is there any solution to this Nexus or do I just have a defective one?
U can get rif of lock screen in the setting>security>screen lock<none
Sent from my Galaxy Nexus using xda premium
In Settings - About Phone, what is your Build Number? Also your brother's?
Any why couldn't you have picked your brother's phone out of the box?
netbuzz said:
In Settings - About Phone, what is your Build Number? Also your brother's?
Any why couldn't you have picked your brother's phone out of the box?
Click to expand...
Click to collapse
Build Number: full_maguro-eng 4.0.1 ICL23D 347 test-keys
And why couldn't I have picked my brother's? Haha I don't know!
They sent you a phone with an early engineering build. This can be easily fixed by flashing the stock Google image.
Here's a guide with all the info you need. http://forum.xda-developers.com/showthread.php?t=1626895
If you are in the US flash the takju build. Elsewhere the yakju build.
I'll hang out here for a while. If you have any questions reply here and I'll help!
Sent from my Nexus 7 using xda premium
airkenada said:
U can get rif of lock screen in the setting>security>screen lock<none
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The problem is that my settings are set to slide yet my phone is acting as if it's set to none
El Daddy said:
They sent you a phone with an early engineering build. This can be easily fixed by flashing the stock Google image.
Here's a guide with all the info you need. http://forum.xda-developers.com/showthread.php?t=1626895
If you are in the US flash the takju build. Elsewhere the yakju build.
I'll hang out here for a while. If you have any questions reply here and I'll help!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Does this void any warranty?
BrokeEven said:
Does this void any warranty?
Click to expand...
Click to collapse
You won't have a problem with warranty if you are running a stock build.
http://www.blogcdn.com/www.engadget.com/media/2011/11/nexnex20111117103746mat400mat400.jpg
Can you compare whether your phone and your brother's have some of these apps? I'm betting its your phone.....
maschiosoosai said:
Can you compare whether your phone and your brother's have some of these apps? I'm betting its your phone.....
Click to expand...
Click to collapse
Ha yeah! The not-so-normal apps that I have on my phone include "Angry GPS", "Dev Tools", and "SUB PBA Test". I checked with my Brother's Nexus running JB and he's got none of those. I called into Google's hotline for Nexus support and was able to get in touch with one of the supervisors. I was told that the device I received was a Developer's Model and that it was the "strangest thing ever".
El Daddy said:
You won't have a problem with warranty if you are running a stock build.
Click to expand...
Click to collapse
So, the instructions involve unlocking my bootloader (a task I know very little about!). To be honest, I don't have much experience with the mobile development. The only thing I've done in terms of tweaking with phones is following the instruction with the ace hack kit to root my phone (which seemed a lot more simplier than these instruction) and flashing custom ROMs.
To further my previous question, since the instructions say unlock the bootloader, does that invalidate my phone's warranty if I were to return anytime within its warranty period with an unlocked bootloader running stock android? (Would they even check/realize?)
And lastly, how safe is this procedure (returning the stock?) Is there a chance to brick my device?
BrokeEven said:
So, the instructions involve unlocking my bootloader (a task I know very little about!). To be honest, I don't have much experience with the mobile development. The only thing I've done in terms of tweaking with phones is following the instruction with the ace hack kit to root my phone (which seemed a lot more simplier than these instruction) and flashing custom ROMs.
To further my previous question, since the instructions say unlock the bootloader, does that invalidate my phone's warranty if I were to return anytime within its warranty period with an unlocked bootloader running stock android? (Would they even check/realize?)
And lastly, how safe is this procedure (returning the stock?) Is there a chance to brick my device?
Click to expand...
Click to collapse
You need to unlock your bootloader to flash the images. You can always relock your bootloader if you wish. You won't have an issue with the warranty.
Flashing the images the way I provided is a good way to learn the basics and will be beneficial in the future. It's very easy to learn. Just follow the link step by step. Flashing with fastboot is the safest way to do things and there is a very small chance of you bricking your phone.
Also what did google tell you to do when you called them?
Development Tools
maschiosoosai said:
Can you compare whether your phone and your brother's have some of these apps? I'm betting its your phone.....
Click to expand...
Click to collapse
I just got another Nexus from Play Store.
It's in developer mode, without Google apps and filled with a bunch of testing tools, like AngryGPS and Screen Test, the same menu in this image from maschiosoosa.
I tried to call Google Support and they give me two options.. One is doing exactly what everybody does.. Flash a stock Google image (but they said: "it's a very difficult way" lol) or the second, they will call Samsung for a replacement.
It's not a defective device, but it's kind of getting a Windows 8 Consumer Preview. A thing that it's not finished yet. Shame on Goole. lol
I'll flash of course.. It seems the bootloader is unlocked and its probably easy to do the flash thing.
Hey BrokeEven, if you got your device from Play Store you can ask for a replacement (if you are not sure of the flash image).
And probably your bootloader is already unlocked (at least if you received this same dev tool device).
El Daddy said:
You need to unlock your bootloader to flash the images. You can always relock your bootloader if you wish. You won't have an issue with the warranty.
Flashing the images the way I provided is a good way to learn the basics and will be beneficial in the future. It's very easy to learn. Just follow the link step by step.
Also what did google tell you to do when you called them?
Click to expand...
Click to collapse
Thank you, I'm gonna give it a shot!
When I called Google and talked to one of the supervisors, he was almost excited to hear about such an "interesting" story and said, "It looked like you may have gotten a rooted or developers model" and "If i got a dev model, I'd just keep it haha - but that's just me" I proceeded to ask him about whether or not it'd be a safe idea to keep the phone and do my own tweaking and such. He responded by telling me that even if i was to safely flash back to stock, it'd be "hard to prove" to Google or Samsung that I hadn't tampered with it. He was a cool guy
So let's say I did in fact get a rooted model by mistake, is there any way I'd be able to figure out if the bootloader is locked or not (even though rooted doesn't necessarily mean it has an unlocked bootloader)?
BrokeEven said:
Thank you, I'm gonna give it a shot!
When I called Google and talked to one of the supervisors, he was almost excited to hear about such an "interesting" story and said, "It looked like you may have gotten a rooted or developers model" and "If i got a dev model, I'd just keep it haha - but that's just me" I proceeded to ask him about whether or not it'd be a safe idea to keep the phone and do my own tweaking and such. He responded by telling me that even if i was to safely flash back to stock, it'd be "hard to prove" to Google or Samsung that I hadn't tampered with it. He was a cool guy
So let's say I did in fact get a rooted model by mistake, is there any way I'd be able to figure out if the bootloader is locked or not (even though rooted doesn't necessarily mean it has an unlocked bootloader)?
Click to expand...
Click to collapse
Yep... The same case... The guys on Google are very funny. lol
Reboot your device and check if theres a unlocked locker at the bottom of the Google logo screen.
BrokeEven said:
Thank you, I'm gonna give it a shot!
When I called Google and talked to one of the supervisors, he was almost excited to hear about such an "interesting" story and said, "It looked like you may have gotten a rooted or developers model" and "If i got a dev model, I'd just keep it haha - but that's just me" I proceeded to ask him about whether or not it'd be a safe idea to keep the phone and do my own tweaking and such. He responded by telling me that even if i was to safely flash back to stock, it'd be "hard to prove" to Google or Samsung that I hadn't tampered with it. He was a cool guy
So let's say I did in fact get a rooted model by mistake, is there any way I'd be able to figure out if the bootloader is locked or not (even though rooted doesn't necessarily mean it has an unlocked bootloader)?
Click to expand...
Click to collapse
Reboot the phone, when it's rebooting (showing google logo) if there's unlocked sign (lock that is unlocked) under the google logo, then it's unlocked Nexus. If you only see Google logo, then it's just locked Nexus
I don't know whether this is a curse or a blessing... I remembered when i ordered this phone I said "meh, I'm not gonna bother with rooting and flashing ROMs. I'll just stick to stock. And so Google sends me a Nexus with an unlocked bootloader and now force me to flash back to stock (or root) in order to get my phone fully functional
One pic is my unlocked bootloader, the other is a picture of my ALL the apps on my phone
Cool so you are already unlocked. Just download the images and flash away!
Sent from my Nexus 7 using xda premium
El Daddy said:
Cool so you are already unlocked. Just download the images and flash away!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Just one question and this may be a simple one...
It's step 8 under subsection C. What does it mean to open the command prompt in the same directory? And sorry in advance! I need you to be very simple in explaining this to me. To my knowledge, I thought you just open the command prompt. How do you open the command prompt in the same directory?
BrokeEven said:
Just one question and this may be a simple one...
It's step 8 under subsection C. What does it mean to open the command prompt in the same directory? And sorry in advance! I need you to be very simple in explaining this to me. To my knowledge, I thought you just open the command prompt. How do you open the command prompt in the same directory?
Click to expand...
Click to collapse
On windows just hold down shift while you right click in the folder. You will see open command prompt here or similar.
Sent from my Nexus 7 using Tapatalk 2
I bought my buddy a phone to use while he was working with me. 4 days later he quits and didn't want to give the phone up so he wiped it while logging in locking the phone. I bought the phone used off Facebook perfectly unlocked so no receipts or anything. I know that pretty much stops me from proving this is my phone but my question is if it's possible to just flash the stock firmware over the already stock firmware, wiping the phone? I've done all the little tricks and have gotten in the settings, installed test dpc etc but it has the newest security patch and I can't get it unlocked that way. Any help would be really really appreciated. I don't really like moto phones and id like to recoup some cash from it.
Anyone? I would even take the paid service route if anyone could tell me it's possible. I've gotten into the settings but none of the usual apps or tricks work to bypass the lock. I know this is a grey area because of security issues but man im having a hard time accepting this thing as paper weight
brd912 said:
Anyone? I would even take the paid service route if anyone could tell me it's possible. I've gotten into the settings but none of the usual apps or tricks work to bypass the lock. I know this is a grey area because of security issues but man im having a hard time accepting this thing as paper weight
Click to expand...
Click to collapse
Acces the phone into fastboot
Then from ADB (computer)
fastboot erase user data
nosiobadx said:
Acces the phone into fastboot
Then from ADB (computer)
fastboot erase user data
Click to expand...
Click to collapse
Already done that. Doesn't format the encrypted memory where the Google info is stored, I'm assuming.
brd912 said:
Already done that. Doesn't format the encrypted memory where the Google info is stored, I'm assuming.
Click to expand...
Click to collapse
Flash stock ROM using fastboot commands
There are several threads around about,so maybe that helps
nosiobadx said:
Flash stock ROM using fastboot commands
There are several threads around about,so maybe that helps
Click to expand...
Click to collapse
Tried that with no luck also. It seems as though Motorola has this phone locked tight
nosiobadx said:
Flash stock ROM using fastboot commands
There are several threads around about,so maybe that helps
Click to expand...
Click to collapse
I've tried all the guides I can find and I get nothing but errors trying to flash any firmware file through adb, fastboot, rsd etc
So I figured this out. Thanks thread can be closed
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...
Verizon phone, hate my life.
Haven't upgraded yet but worried my stuff will stop working, and I'll be stuck. Sorry if this is covered elsewhere, I searched.
Alternative solution anyone want to trade for your unlocked phone? :crying:
Google has implemented a rollback prevention system on their devices. You cannot install an earlier version of Android over a later one. Attempting to do so generates an error message and the device will not boot. I believe this applies regardless of the lock status of the bootloader, but I'm sure someone more knowledgeable will chime in.
Sell your device on Swappa. Then purchase an unlocked model off Swappa, if available. No sane person is going to trade their unlockable device for your Verizon model.
if you unlock the bootloader, and wipe the device, you can downgrade to any version that google has published for the device.
If you do NOT unlock the bootloader, it is not possible.
@uicrnen: He has a Verizon device, so he can't unlock it.
Strephon Alkhalikoi said:
@uicrnen: He has a Verizon device, so he can't unlock it.
Click to expand...
Click to collapse
correct, therefore they cannot downgrade.
If they had an unlockable version of the phone, they could downgrade, should they desire to.
uicnren said:
correct, therefore they cannot downgrade.
If they had an unlockable version of the phone, they could downgrade, should they desire to.
Click to expand...
Click to collapse
Which is why I gave your post a thumbs up. Rollback protection then is similar to Factory Reset Protection in this regard. So long as OEM Unlocking is enabled in developer options and the bootloader unlocked, neither will kick in.
uicnren said:
if you unlock the bootloader
Click to expand...
Click to collapse
Please can you recommend the safest/most reliable way to accomplish this.
uicnren said:
...and wipe the device, you can downgrade to any version that google has published for the device.
Click to expand...
Click to collapse
Once I do this, I presume I can then relock the bootloader...?
I am finding that I prefer Oreo over Pie and my Pixel 2 XL has to be restarted more regularly than when I was on Oreo. Sigh....
I'm happy having a non-rooted device as my biggest peeve is the ads, so use DNS66 to block ads successfully.
Plus, I want to be able to use Google Pay and (Barclays) banking apps. Barclays mobile app doesn't show up in USA Google Play Store but does once you install it from APK. (Had a UK friend send me the APK. Seriously banks, do you think only folks from your country have accounts? ?).
Over the years I have frequently rooted from the get-go but am enjoying being able to update OTA and have Google Pay work seamlessly.
Most apps I use that are beneficial use the ADB Write Settings commands now which accomplish what rooted device did. Wish Titanium Backup could do this with ADB Write command.
Thanks for any help.
IconBoy said:
Please can you recommend the safest/most reliable way to accomplish this.
Once I do this, I presume I can then relock the bootloader...?
I am finding that I prefer Oreo over Pie and my Pixel 2 XL has to be restarted more regularly than when I was on Oreo. Sigh....
I'm happy having a non-rooted device as my biggest peeve is the ads, so use DNS66 to block ads successfully.
Plus, I want to be able to use Google Pay and (Barclays) banking apps. Barclays mobile app doesn't show up in USA Google Play Store but does once you install it from APK. (Had a UK friend send me the APK. Seriously banks, do you think only folks from your country have accounts? ?).
Over the years I have frequently rooted from the get-go but am enjoying being able to update OTA and have Google Pay work seamlessly.
Most apps I use that are beneficial use the ADB Write Settings commands now which accomplish what rooted device did. Wish Titanium Backup could do this with ADB Write command.
Thanks for any help.
Click to expand...
Click to collapse
Assuming you have a Pixel 2 XL, which the bootloader is unlockable:
1. BACKUP. Save anything you deem important, as your device will be erased.
1a. Be sure you have the latest adb/fastboot installed/working, available from: https://developer.android.com/studio/releases/platform-tools
2. Enable developer options. Settings > System > About then tap on build number 7 times, follow prompts.
3. Settings > System > Advanced > either enable or make sure that 'OEM unlocking' is enabled.
4. Download (the version you wish to install) and follow ALL instructions from: https://developers.google.com/android/images ***this includes performing BOTH fastboot flasshing unlock AND fastboot flashing unlock_critical***
Thats all there is to it.
After doing above, re-enable developer options and again make sure to re-enable OEM unlocking. Be sure to do this BEFORE re-locking the bootloader.
If you wish to re-lock the bootloader, be 100% certain that you are completely stock ROM. There have been issues (sometimes catastrophic) when re-locking the bootloader when the device is not 100% stock.
Worth mentioning to him if he's on Verizon, it isn't gonna work.
Upgraded anyway. Handful of issues but not enough to regret it. I do regret buying through Verizon though...
forwardthinking said:
Verizon phone, hate my life.
Haven't upgraded yet but worried my stuff will stop working, and I'll be stuck. Sorry if this is covered elsewhere, I searched.
Alternative solution anyone want to trade for your unlocked phone? :crying:
Click to expand...
Click to collapse
Sell it on swappa ms buy what you want.
uicnren said:
Assuming you have a Pixel 2 XL, which the bootloader is unlockable:
Click to expand...
Click to collapse
Unlocked Pixel 2 XL bought from Google Store.
uicnren said:
Be sure you have the latest adb/fastboot installed/working, available from: https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Will 15 Second ADB be sufficient, as I've always had success with that...?
Hopefully the ADB Fastboot file from Android Developer I can unzip and copy the updated contents to 15 Second ADB as their batch file installs system wide which is so helpful.
uicnren said:
2. Enable developer options. Settings > System > About then tap on build number 7 times, follow prompts
Click to expand...
Click to collapse
Done that already. :good:
uicnren said:
3. Settings > System > Advanced > either enable or make sure that 'OEM unlocking' is enabled.
4. Download (the version you wish to install) and follow ALL instructions from: https://developers.google.com/android/images
Click to expand...
Click to collapse
As my device is unlocked and not specific to any carrier, am I correct in choosing the sixth from bottom from the list:
Taimen 8.1.0 (OPM2.171026.006.H1, Jul 2018)?
uicnren said:
***this includes performing BOTH fastboot flasshing unlock AND fastboot flashing unlock_critical***
Thats all there is to it.
Click to expand...
Click to collapse
Duly noted!
uicnren said:
After doing above, re-enable developer options and again make sure to re-enable OEM unlocking. Be sure to do this BEFORE re-locking the bootloader.
Click to expand...
Click to collapse
Once the device first boots from doing all this, is it okay if I skip all the Google account setup and just enable Developer Options and enable OEM unlock?
uicnren said:
If you wish to re-lock the bootloader, be 100% certain that you are completely stock ROM. There have been issues (sometimes catastrophic) when re-locking the bootloader when the device is not 100% stock.
Click to expand...
Click to collapse
So the file I chose from the Android Developers Images page above, would be 100% stock?...and I can just go ahead and relock bootloader?
Should I factory reset after bootloader is relocked?
Thank you for clarifying the steps.