Develop Bugs

[Q] Getting 4.0.4 Stock ROM

I've been an Android user for a while (Nexus One, and now Galaxy Nexus), but am quite tired of Samsung's tyrannical rule over that little version number in "About Phone".
So, I've got my Samsung Galaxy Nexus (on 4.0.1, ERGH!), and I'm on Bell Canada (Alberta, specifically), and I don't believe I have LTE capability (I do have HSPA+...). As for computer, I run Windows 7 x64.
On that note, I'd like to unlock the BootLoader and flash 4.0.4 (no root, if possible), or at least be able to receive updates directly from Google.
These are the questions (and confirmations) I have, as I haven't been able to find any FAQ or thread that covers them...
1. Is this the ROM I should be downloading?
2. Is this the tool I should be using to unlock the BootLoader safely and properly?
3. Is a relocked BootLoader traceable by the carrier/manufacturer, in the event that I need to return it?
4. What is the best way to back up all of the App data on my phone? (High scores, calendar settings, user/password combinations, etc.) Or is this even possible? (I think things like contacts, phone settings, calendar events, and Apps will sync from the cloud... right?)
Any help is appreciated... I'm a bit of a tech geek but I've never even tampered with a phone before, so this is all new to me. Thanks to anyone brave enough to help me! ^^
PS: Sorry if this is in the wrong section; this was the most fitting, I thought.

I used that toolkit and that update and I can confirm that they both work

That is NOT the ROM for you, you have a GSM device. H+ is not LTE.
The GSM and CDMA devices are markedly different.

Try to read in this thread... as well as efrant posts, you will get your answer !
N.B. most important thing is read and read and read... before doing anything..
http://forum.xda-developers.com/showthread.php?t=1391881
Zackster said:
I've been an Android user for a while (Nexus One, and now Galaxy Nexus), but am quite tired of Samsung's tyrannical rule over that little version number in "About Phone".
So, I've got my Samsung Galaxy Nexus (on 4.0.1, ERGH!), and I'm on Bell Canada (Alberta, specifically), and I don't believe I have LTE capability (I do have HSPA+...). As for computer, I run Windows 7 x64.
On that note, I'd like to unlock the BootLoader and flash 4.0.4 (no root, if possible), or at least be able to receive updates directly from Google.
These are the questions (and confirmations) I have, as I haven't been able to find any FAQ or thread that covers them...
1. Is this the ROM I should be downloading?
2. Is this the tool I should be using to unlock the BootLoader safely and properly?
3. Is a relocked BootLoader traceable by the carrier/manufacturer, in the event that I need to return it?
4. What is the best way to back up all of the App data on my phone? (High scores, calendar settings, user/password combinations, etc.) Or is this even possible? (I think things like contacts, phone settings, calendar events, and Apps will sync from the cloud... right?)
Any help is appreciated... I'm a bit of a tech geek but I've never even tampered with a phone before, so this is all new to me. Thanks to anyone brave enough to help me! ^^
PS: Sorry if this is in the wrong section; this was the most fitting, I thought.
Click to expand...
Click to collapse

Argh! Didn't realize CMDA was the LTE version.
Thanks to everyone! Will read through that thread tonight and hopefully all is well.

Zackster said:
[snip]
On that note, I'd like to unlock the BootLoader and flash 4.0.4 (no root, if possible), or at least be able to receive updates directly from Google.
Click to expand...
Click to collapse
There is no official 4.0.4 ROM for the GSM version.The latest is 4.0.2.
By the way, you can still update your version (yakjuux) to 4.0.2 without flashing yakju, by following the instructions here.
Zackster said:
4. What is the best way to back up all of the App data on my phone? (High scores, calendar settings, user/password combinations, etc.) Or is this even possible? (I think things like contacts, phone settings, calendar events, and Apps will sync from the cloud... right?)
Click to expand...
Click to collapse
Best way is to root your device by following the instructions here, and then install Titanium Backup from the market. TB will do what you are asking.

efrant said:
There is no official 4.0.4 ROM for the GSM version.The latest is 4.0.2.
Click to expand...
Click to collapse
Hmm... does this mean that no 4.0.4 version will work on the GSM version? Or would it be ridden full of bugs, or what?
efrant said:
By the way, you can still update your version (yakjuux) to 4.0.2 without flashing yakju, by following the instructions here.
Click to expand...
Click to collapse
Still requires setting up the toolkit to get the drivers and bootloader unlocked, and to get fastboot working though, it seems, yes?
efrant said:
Best way is to root your device by following the instructions here, and then install Titanium Backup from the market. TB will do what you are asking.
Click to expand...
Click to collapse
Doesn't rooting require wiping the device, though? I'm interested in backing it up pre-4.0.4.

http://forum.xda-developers.com/showthread.php?t=1454314 That there is a little something-something I happened upon when I was growing entirely to impatient waiting for the 4.0.2 update.
It'll give you instructions on what you need to do for everything. Just make sure you select GSM/HSPA+ first.
My gift, from one Alberta boy to another!

Zackster said:
Hmm... does this mean that no 4.0.4 version will work on the GSM version? Or would it be ridden full of bugs, or what?
Still requires setting up the toolkit to get the drivers and bootloader unlocked, and to get fastboot working though, it seems, yes?
Doesn't rooting require wiping the device, though? I'm interested in backing it up pre-4.0.4.
Click to expand...
Click to collapse
There is no 4.0.4 source. There is a rumored leak of the 4.0.4 LTE version (no idea of the condition of the version), but the only source that is available is 4.0.3 (it's in the AOSP). The latest version on any GN is 4.0.2 (GSM or LTE/CDMA).
It's kind of disappointing to see the GN taking so long to update, but the Nexus S is apparently taking ages to get onto ICS. I doubt we get another update until the Nexus S gets 100% updated to ICS.

Zackster said:
Hmm... does this mean that no 4.0.4 version will work on the GSM version? Or would it be ridden full of bugs, or what?
Click to expand...
Click to collapse
There are custom ROMs available based on 4.0.3. There are NO 4.0.4 ROMs for GSM.
Zackster said:
Still requires setting up the toolkit to get the drivers and bootloader unlocked, and to get fastboot working though, it seems, yes?
Click to expand...
Click to collapse
I don't use tool kits, but yes, you need to install the drivers. You do not need to unlock the bootloader.
Zackster said:
Doesn't rooting require wiping the device, though? I'm interested in backing it up pre-4.0.4.
Click to expand...
Click to collapse
If you would have looked at the link I posted , you would have answered your question. No, rooting does not require wiping. Unlocking the bootloader wipes.
Sent from my Galaxy Nexus using Tapatalk

Zackster said:
[snip]
Still requires setting up the toolkit to get the drivers and bootloader unlocked, and to get fastboot working though, it seems, yes?
Click to expand...
Click to collapse
I've found that these drivers work the best.

krblake13 said:
http://forum.xda-developers.com/showthread.php?t=1454314 That there is a little something-something I happened upon when I was growing entirely to impatient waiting for the 4.0.2 update.
It'll give you instructions on what you need to do for everything. Just make sure you select GSM/HSPA+ first.
My gift, from one Alberta boy to another!
Click to expand...
Click to collapse
Great! I'll look into this! Good to know it's worked for someone else in this situation.
descendency said:
There is no 4.0.4 source. There is a rumored leak of the 4.0.4 LTE version (no idea of the condition of the version), but the only source that is available is 4.0.3 (it's in the AOSP). The latest version on any GN is 4.0.2 (GSM or LTE/CDMA).
It's kind of disappointing to see the GN taking so long to update, but the Nexus S is apparently taking ages to get onto ICS. I doubt we get another update until the Nexus S gets 100% updated to ICS.
Click to expand...
Click to collapse
Hmm... disappointing, for sure. I had found this MoDaCo ROM, which is why I asked.
efrant said:
There are custom ROMs available based on 4.0.3. There are NO 4.0.4 ROMs for GSM.
I don't use tool kits, but yes, you need to install the drivers. You do not need to unlock the bootloader.
If you would have looked at the link I posted , you would have answered your question. No, rooting does not require wiping. Unlocking the bootloader wipes.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Argh, I keep getting rooting and the bootloader confused. Sorry about that.
efrant said:
I've found that these drivers work the best.
Click to expand...
Click to collapse
Excellent, I'll give these a try.

New Galaxy Nexus owner

Hello all. Well after many many years with Sprint they finally got on my last nerve and now I am a new Verizon customer and a very happy new owner of the Galaxy Nexus. Awesome phone! Anyway my question is I have been told the bootloader of this phone is locked. I have never messed with a phone with a locked bootloader. While I was with Sprint I had the Epic 4G Touch so I am familiar with Odin, CWM, flashing roms, etc. What is the preferred method to altering the Nexus to be able to root, CWM, flash roms? Also what is currently considered by most to be the best rom that leaves the phone with all of its functions working? Thank you in advance for any information you folks can offer.

Pete720 said:
Hello all. Well after many many years with Sprint they finally got on my last nerve and now I am a new Verizon customer and a very happy new owner of the Galaxy Nexus. Awesome phone! Anyway my question is I have been told the bootloader of this phone is locked. I have never messed with a phone with a locked bootloader. While I was with Sprint I had the Epic 4G Touch so I am familiar with Odin, CWM, flashing roms, etc. What is the preferred method to altering the Nexus to be able to root, CWM, flash roms? Also what is currently considered by most to be the best rom that leaves the phone with all of its functions working? Thank you in advance for any information you folks can offer.
Click to expand...
Click to collapse
Unlock the boot loader firstly but beware it will wipe your sdcard.
Use fast boot to unlock it, type oem fastboot unlock and go from there.
Flash cwm using fastboot by typing fastboot flash recovery xxxxxxx.img (xxxxx.img is whatever the filename is)
You are probably familiar with cwm so I won't bother explaining that.
All the rooms here have everything working on them. We'll except sense 4.0 and touchwiz ports etc. But that's obvious.
Ps. All phones have locked bootloaders!

Yeah, you might mean unlocked bootloader. You do have to unlock it first, but it doesn't take an exploit to do so. See here for a starting point:
http://forum.xda-developers.com/showthread.php?t=1400871
As for the best rom, impossible to say, so many . It depends on what exactly you're looking for. aokp is probably the most features-popular, but there are many others. I use cm9 with the reloaded mod, personally.
sent from my Zerg Hatchery.

Ok I used the Toolkit 5.5 to unlock, root, CWM etc. Seemed easy and effortless. I have now installed AOKP Rom on my Nexus. What do I need or need to know in order to return my phone to box stock say incase I have to take it to Verizon for any reason?

Pete720 said:
Ok I used the Toolkit 5.5 to unlock, root, CWM etc. Seemed easy and effortless. I have now installed AOKP Rom on my Nexus. What do I need or need to know in order to return my phone to box stock say incase I have to take it to Verizon for any reason?
Click to expand...
Click to collapse
SDK, Fastboot, ADB

anton2009 said:
SDK, Fastboot, ADB
Click to expand...
Click to collapse
Forgive me, I am just an end user that can follow directions well Can you explain what this means? Is there a file I am going to have to download or does Option #8 in the Toolkit do everything?

Pete720 said:
Forgive me, I am just an end user that can follow directions well Can you explain what this means? Is there a file I am going to have to download or does Option #8 in the Toolkit do everything?
Click to expand...
Click to collapse
Options 8 (Extract and Flash Google Factory Stock ROM), 10 (Reflash Stock Recovery [just to be safe]), and 11 (Relock bootloader) will return it all to stock. I know, because I just had to do this to 3 GNex's this past week to send them back to Verizon

Looks like your question was answered, but for me, I used Wugfreshes toolkit to root then to unroot, just click unroot, let it do its thing and then click OEM lock to make it factory.

Okaay said:
Looks like your question was answered, but for me, I used Wugfreshes toolkit to root then to unroot, just click unroot, let it do its thing and then click OEM lock to make it factory.
Click to expand...
Click to collapse
Only if you are stock and rooted.
He is running a custom rom and kernel and has cwm flashed, that method will not revert them to stock.

nodstuff said:
Ps. All phones have locked bootloaders!
Click to expand...
Click to collapse
hmmm...not true, the Samsung Galaxy S II doesn't come with a locked bootloader

nicholaschum said:
hmmm...not true, the Samsung Galaxy S II doesn't come with a locked bootloader
Click to expand...
Click to collapse
My apologies, I totally forgot to update my signature. I do not have the GSII anymore.

Can anyone point me int he direction of the box stock rom file I need to work with Toolkit to restore my phone? I followed the directions and got the image from code.google.com but it wont install. ALways says something is missing.

Toolkit says the file shouls end in .tgz but the file I am downloading from Google does not say that. My phone is 4.0.2 (ICL53F) and that is the file I am downloading from Google's image site.

Pete720 said:
Toolkit says the file shouls end in .tgz but the file I am downloading from Google does not say that. My phone is 4.0.2 (ICL53F) and that is the file I am downloading from Google's image site.
Click to expand...
Click to collapse
I believe that the toolkit will auto download if you just run the option.

TF300T Bootloader Unlocked!

Taken from here:
http://forum.xda-developers.com/showpost.php?p=26422045&postcount=84
Quote from the Asus Global website, on the tab "download" choose "Android" as OS, then browse to "Utilities" and download the bootloader unlock tool, it dates from 22 may 2012:
http://support.asus.com/download.asp...mzkQ4yoz5WzBrW
Unlock Device App: Unlock boot loader.
Notice:
1. Only suitable for Andriod4.0 Ice Cream Sandwich OS version.
2. Before you download, install, and use the Unlock Device App you acknowledge and assume complete risk to the quality and performance of this App, including but not limited to the following: once you activate the App you will not be able to recover your ASUS product (“Original Product”) back to original locked conditions;the Original Product with the activated App will not be deemed the Original Product; the Revised Product will no longer be covered under the warranty of the Original Product; the software of Revised Product will no longer be deemed the software of the Original Product and can no longer receive ASUS software updates; your purchased digital content may also be affected.
You also acknowledge ASUS does not guarantee service satisfaction to any Revised Product, including events involving paid service requested by you to be performed to the Revised Product.
Furthermore, such repaired Revised Product will not be covered under the warranty of the Original Product; the software of the repaired Revised Product will not be deemed the software of the Original Product and will not receive ASUS software updates.
It is strongly advised that you avoid activating this App unless you fully understand and accept the risks that may arise.
※This tool now only works with TF300T ICS of TW,US,WW SKU. It won’t work on other devices.
http://dl.dropbox.com/u/25830232/UnLock_Device_App_V7.apk - APK

Amazing!
I'm proud to announce that I'm going to start porting CyanogenMod 9 to this little thing

XpLoDWilD said:
Amazing!
I'm proud to announce that I'm going to start porting CyanogenMod 9 to this little thing
Click to expand...
Click to collapse
Device here ready to run it

is it true you cant lock it again?
I dont wanna unlock and then it breaks and Im at a loss.

Awesome news! Hopefully someone will figure out a way to re-lock the device if something goes wrong.

Nekromantik said:
is it true you cant lock it again?
I dont wanna unlock and then it breaks and Im at a loss.
Click to expand...
Click to collapse
If Asus says it's true, then it's true, since they made it . But maybe some smart XDA dev will find a way to re-lock it.

maspro said:
If Asus says it's true, then it's true, since they made it . But maybe some smart XDA dev will find a way to re-lock it.
Click to expand...
Click to collapse
Thanks.
I may wait and see if anyone does come up with a way to relock.
That and the less bright screen are only thing holding me back as I want to use it outside and its getting to summer so will be bright out.

Nekromantik said:
is it true you cant lock it again?
I dont wanna unlock and then it breaks and Im at a loss.
Click to expand...
Click to collapse
I'm with you on this one lol
Sent from my ASUS Transformer Pad TF300T using XDA

One a recovery is adapted hopefully there will a stock recovery made.
Sent from my VS910 4G using xda premium

Giggity!!!
Sent from my Galaxy Nexus using Tapatalk

Still can't mine unlocked though, keeps saying network error

Just unlocked by bootloader! AWESOME! Cant wait for a custom recovery and new roms!

Hopefully TWRP will be ported over.

I am hoping for AOKP!

Anyone able to unlock a bricked tab? That would be top notch...
Nevermind, I see it's a .apk file

Now we can have the stock ROM rooted without any modifications so we can get root without downgrading our firmware. New kernels, too?

Im receiving this tablet in the mail this week.
Im hoping for a quick port of CWM and then CM9 or AOKP to follow.
great circumstances to walk into!

SilentStormer said:
Im receiving this tablet in the mail this week.
Im hoping for a quick port of CWM and then CM9 or AOKP to follow.
great circumstances to walk into!
Click to expand...
Click to collapse
No doubt. I just got this tab on Sunday after a month of researching and was super bummed that the bootloader was locked.

Does the release of the bootloader, mean it will be easier to root and not have to do the downgrade any longer?
I spent last night to no avail trying to downgrade (the adb access was an issue, which I might have solved today, but haven't put the time in to test it out).
If it means that I won't have to do the downgrade and it might be end up having easier steps to root, then I think (being too much a newbie in tablets) I should wait.
Just wanted to know if that is what this release means?
Thanks!
Rob

rlanza1054 said:
Does the release of the bootloader, mean it will be easier to root and not have to do the downgrade any longer?
I spent last night to no avail trying to downgrade (the adb access was an issue, which I might have solved today, but haven't put the time in to test it out).
If it means that I won't have to do the downgrade and it might be end up having easier steps to root, then I think (being too much a newbie in tablets) I should wait.
Just wanted to know if that is what this release means?
Thanks!
Rob
Click to expand...
Click to collapse
Bootloader means custom recovery and then custom ROM's. If you intend to continue running stock rom and merely want to be rooted, then you may still need to figure out the downgrade issue. If you just wanna run cm 9, then you could just continue to wait patiently. Sounds like you oughta figure out ur adb issue either way, though.
Sent from my ASUS Transformer Pad TF300T using Tapatalk

[Q] Question about warranty when unlocking bootloader and installing custom ROMS

Will I really lose my warranty if I unlock the bootloader and install custom ROMS?
And will I get back my warranty if I relock the boot loader and flash stock ROM?
Asus can't see I flashed my device in the past if I have stock ROM with locked bootloader, can they?
Can anyone tell me how this works exactly?
Everywhere I read I MAY risk to lose warranty.
Thanks in advance!

danielsinnema said:
Will I really lose my warranty if I unlock the bootloader and install custom ROMS?
And will I get back my warranty if I relock the boot loader and flash stock ROM?
Asus can't see I flashed my device in the past if I have stock ROM with locked bootloader, can they?
Can anyone tell me how this works exactly?
Everywhere I read I MAY risk to lose warranty.
Thanks in advance!
Click to expand...
Click to collapse
No (well...can go either way)
Yes (although you don't really lose it in the first place)
Once you've flashed the factory image and relocked the bootloader, no they can't (only Nexus to have a tamper flag is the N5)
That warning is standard on all unlockable devices. It's a standard disclaimer they put on there just like any other company would (to cover their butts). However, I do see where the company is coming from. I've seen noobs unlock and start flashing, and then end up messing their device up beyond recovery. They then feel they have the right to get it repaired free of charge. If you know what you are doing, chances are good you'll be fine. If something is actually defective, and as long as you still have to ability to flash stock image and relock, you're good. That being said, I've also read stories of people getting RMAs successfully even though they were unlocked/rooted/ROMed. As long as you can make a case that the defect wasn't caused by your own doing, I would imagine you'd be okay.

charesa39 said:
No (well...can go either way)
Yes (although you don't really lose it in the first place)
Once you've flashed the factory image and relocked the bootloader, no they can't (only Nexus to have a tamper flag is the N5)
That warning is standard on all unlockable devices. It's a standard disclaimer they put on there just like any other company would (to cover their butts). However, I do see where the company is coming from. I've seen noobs unlock and start flashing, and then end up messing their device up beyond recovery. They then feel they have the right to get it repaired free of charge. If you know what you are doing, chances are good you'll be fine. If something is actually defective, and as long as you still have to ability to flash stock image and relock, you're good. That being said, I've also read stories of people getting RMAs successfully even though they were unlocked/rooted/ROMed. As long as you can make a case that the defect wasn't caused by your own doing, I would imagine you'd be okay.
Click to expand...
Click to collapse
Thanks mate for your explanation, I was looking for this.
I have some experience flashing android devices so I probably won't mess up my device I have bought my nexus 7 2013 recently and I don't want to have no warranty when I discover a hardware issue.. But everything seems to be fine actually. I'll install a cm 11 nightly soon.
Sent from my Nexus 7 using xda app-developers app

danielsinnema said:
Will I really lose my warranty if I unlock the bootloader and install custom ROMS?
Click to expand...
Click to collapse
If you should ever need to bring your N7 to the service within the warranty, you will flash a stock ROM, unroot and lock the bootloader. Then you're 100% stock again with no sign of mods.
Do you have a N7 razor 2013?
tetakpatalked from my N7100

tetakpatak said:
If you should ever need to bring your N7 to the service within the warranty, you will flash a stock ROM, unroot and lock the bootloader. Then you're 100% stock again with no sign of mods.
Do you have a N7 razor 2013?
tetakpatalked from my N7100
Click to expand...
Click to collapse
Yes, I think I have that version. I have the wifi only version.
Thanks for the tips man!

danielsinnema said:
Yes, I think I have that version. I have the wifi only version.
Thanks for the tips man!
Click to expand...
Click to collapse
Good. Yes, it is probably razor flo, check to be sure. I have the same one. Just keep in mind to save all your data and settings elswhere as unlocking the bootloader for the first time will instantly wipe whole your tab and poasibly even corrupt the /data partition.
I have written this morning how to get out of it in one other N7 thread.
tetakpatalked from Nexus 7

tetakpatak said:
Good. Yes, it is probably razor flo, check to be sure. I have the same one. Just keep in mind to save all your data and settings elswhere as unlocking the bootloader for the first time will instantly wipe whole your tab and poasibly even corrupt the /data partition.
I have written this morning how to get out of it in one other N7 thread.
tetakpatalked from Nexus 7
Click to expand...
Click to collapse
Yes I see.
I backed up everything in TWRP before I unlocked the bootloader.
I'm now have installed the latest nighty of Cm 11, which is running flawlessly.
Thank you all for telling me how stuff works!
Sent from my Nexus 7 using Tapatalk

danielsinnema said:
Yes I see.
I backed up everything in TWRP before I unlocked the bootloader.
I'm now have installed the latest nighty of Cm 11, which is running flawlessly.
Thank you all for telling me how stuff works!
Click to expand...
Click to collapse
Hey, great mate!
That's why we have a community here.
Don't hesitate to ask if anything.
tetakpatalked from Nexus 7

Yes thank you for creating this thread because then it helps encourage people like me want to root and learn things I want to learn to be a developer when I grow up!
Sent from my Nexus 7 using XDA Premium 4 mobile app

Skipsoft unable to unlock my bootloader? Trying to root

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...