Hi all,
just received my 6a directly from Google and I seem to be unable to unlock the bootloader.
The option "OEM unlocking" is greyed out and it says "Connect to the internet or contact your carrier.".
I connected it to the internet via Wifi and updated all the apps.
What can I do?
Best,
Mustkeg
Mustkeg said:
The option "OEM unlocking" is greyed out and it says "Connect to the internet or contact your carrier.".
Click to expand...
Click to collapse
You just answered your own question. While you may have purchased the device from Google, is it a "carrier" branded device for Big Red, AT&T, T-mobile..etc?
If so, then you'll have to contact the carrier to see if they will let you unlock it once it's paid off. Best bet is to return it for an "unlocked" model. Best of luck to you.
Badger50 said:
You just answered your own question. While to may have purchased the device from Google, is it a "carrier" branded device for Big Red, AT&T, T-mobile..etc?
If so, then you'll have to contact the carrier to see if they will let you unlock it once it's paid off. Best bet is to return it for an "unlocked" model. Best of luck to you.
Click to expand...
Click to collapse
That is exactly right. A warning to others, never buy a branded device even from Google.
I'm actually in the same boat here, purchased the Unlocked non-carrier branded Google Pixel 6a directly from the Google Store and "OEM Unlocking" is greyed out...contacted Google support about it and they had no idea why, transferred to a specialist and still no answers...they said they're going to look into it more and get back to me
I do not even have the choice to buy crappy "Verizon et al." locked variants in my country via the Google Store. I paid it in full up front and without any carrier bloat.
Just had a support chat with Google, they told me it's a bug and will be fixed in an update. Soon...ish.
hello from store google in france .this and write unlock
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Mustkeg said:
I do not even have the choice to buy crappy "Verizon et al." locked variants in my country via the Google Store. I paid it in full up front and without any carrier bloat.
Just had a support chat with Google, they told me it's a bug and will be fixed in an update. Soon...ish.
Click to expand...
Click to collapse
In some cases, the device just needs to be connected to the Internet for a while for OEM Unlocking to become available.
It is true that they can remedy this with a software update.
If OEM Unlocking is unavailable, this means that the ro.oem_unlock_supported property is set to 0.
If ro.oem_unlock_supported=1 then OEM Unlocking will be available in Developer Options. This toggles the get_unlock_ability property to 1, which informs the bootloader that unlocking is allowed.
I would request an RMA if this issue does not resolve itself. You paid for an unlocked device from Google; they should have sent you an unlocked device. When I ordered my Pixel 5, I unlocked it straight out of the box without even connecting to WiFi.
V0latyle said:
In some cases, the device just needs to be connected to the Internet for a while for OEM Unlocking to become available.
It is true that they can remedy this with a software update.
If OEM Unlocking is unavailable, this means that the ro.oem_unlock_supported property is set to 0.
If ro.oem_unlock_supported=1 then OEM Unlocking will be available in Developer Options. This toggles the get_unlock_ability property to 1, which informs the bootloader that unlocking is allowed.
I would request an RMA if this issue does not resolve itself. You paid for an unlocked device from Google; they should have sent you an unlocked device. When I ordered my Pixel 5, I unlocked it straight out of the box without even connecting to WiFi.
Click to expand...
Click to collapse
You're right. I definitely bought an unlocked device, but ADB getprop says [sys.oem_unlock_allowed]: [0].
I'll hold out for an eventual update for some days and if the end of the return window turns near, I'll return it.
Maybe other users will chime in soon and tell about their experiences with unlocking the 6a. There are not even factory images available at this point.
Mustkeg said:
You're right. I definitely bought an unlocked device, but ADB getprop says [sys.oem_unlock_allowed]: [0].
I'll hold out for an eventual update for some days and if the end of the return window turns near, I'll return it.
Maybe other users will chime in soon and tell about their experiences with unlocking the 6a. There are not even factory images available at this point.
Click to expand...
Click to collapse
To be honest, this has been a mystery for more than a decade. I cut my teeth on the OG Motorola Droid, back when the most common recovery was ClockWorkMod, and CyanogenMod was still in its infancy. Still, we haven't quite figured out exactly what sets the ro.oem_unlock_supported property, especially in circumstances like the Pixel series, where unlocked devices from Google are seemingly identical to carrier branded devices, and even run the exact same firmware - yet the latter remains locked. It's entirely possible that this property is set in hardware, and that Google manufactures devices specifically for carriers who don't want the devices to be unlockable.
Do you have Fastboot? If so, look up how to unlock bootloader with fastboot.
You can bypass Bootloader restrictions in some cases. What OS version are you on? What Version of Linux Kernel? You can find these answers in the "About" section.
V0latyle said:
To be honest, this has been a mystery for more than a decade. I cut my teeth on the OG Motorola Droid, back when the most common recovery was ClockWorkMod, and CyanogenMod was still in its infancy. Still, we haven't quite figured out exactly what sets the ro.oem_unlock_supported property, especially in circumstances like the Pixel series, where unlocked devices from Google are seemingly identical to carrier branded devices, and even run the exact same firmware - yet the latter remains locked. It's entirely possible that this property is set in hardware, and that Google manufactures devices specifically for carriers who don't want the devices to be unlockable.
Click to expand...
Click to collapse
If you recall this happened once before. I'm not sure which Pixel it was, perhaps the 3 or 4 but Google must have reset their IMEI database and then asked users to do a factory reset. That fixed it but it did require a wipe so beware once they fix it. It has to be the IMEI that allows or disallows the OEM switch since no one can find any other reason and how can they just globally reset the switch other than that. But I defer to the experts on this one.
Mustkeg said:
You're right. I definitely bought an unlocked device, but ADB getprop says [sys.oem_unlock_allowed]: [0].
I'll hold out for an eventual update for some days and if the end of the return window turns near, I'll return it.
Maybe other users will chime in soon and tell about their experiences with unlocking the 6a. There are not even factory images available at this point.
Click to expand...
Click to collapse
just saw this part - so there are a few options to try then. Let me read the rest of the post to see whats already been done and ill list a few other options. Also, check out my post on BruteRoot for a collection of ways you can get temp root in order to go and edit the build prop. or unlock BL.
K0mraid3 said:
Do you have Fastboot? If so, look up how to unlock bootloader with fastboot.
You can bypass Bootloader restrictions in some cases. What OS version are you on? What Version of Linux Kernel? You can find these answers in the "About" section.
Click to expand...
Click to collapse
This is a known issue with Google devices ever since the Nexus - Google branded devices purchased without a carrier plan are usually bootloader unlockable, while carrier branded devices, whether purchased from Google or from the carrier, are not. There is no known vulnerability that allows circumventing the bootloader lock.
bobby janow said:
If you recall this happened once before. I'm not sure which Pixel it was, perhaps the 3 or 4 but Google must have reset their IMEI database and then asked users to do a factory reset. That fixed it but it did require a wipe so beware once they fix it. It has to be the IMEI that allows or disallows the OEM switch since no one can find any other reason and how can they just globally reset the switch other than that. But I defer to the experts on this one.
Click to expand...
Click to collapse
Interesting, I hadn't heard of that. I have heard of some TMobile users being able to request a bootloader unlock through their carrier once the device is paid off.
The problem with the IMEI database theory is that it could be safely assumed that every device would not be unlockable until it was able to connect to the Internet. Most of us with unbranded devices have been able to unlock them right out of the box without even setting up WiFi.
Just received mine, went into developer options (after connecting to wifi) and it's greyed out for me as well. no system update available so i went to check the factory images and there are only 2 for the 6a, one for japan and another for verizon. mine is a non-verizon model, but i plan to use it on their service, none for the generic device. i have not inserted my sim card yet.
I then tried updating all apps, play services, etc. and then restarted. still grayed out. factory reset, still grayed out.
very frustrating....dying to get rid of my 4a5g which overheats constantly....
hochoch said:
Just received mine, went into developer options (after connecting to wifi) and it's greyed out for me as well. no system update available so i went to check the factory images and there are only 2 for the 6a, one for japan and another for verizon. mine is a non-verizon model, but i plan to use it on their service, none for the generic device. i have not inserted my sim card yet.
I then tried updating all apps, play services, etc. and then restarted. still grayed out. factory reset, still grayed out.
very frustrating....dying to get rid of my 4a5g which overheats constantly....
Click to expand...
Click to collapse
The first factory images are dated 220601.
My 6a runs a "220123" build.
Let's hope the international 6a factory builds are also newer and include the fix.
Mustkeg said:
The first factory images are dated 220601.
My 6a runs a "220123" build.
Let's hope the international 6a factory builds are also newer and include the fix.
Click to expand...
Click to collapse
Looks like we'll have to wait until after the weekend...finger's crossed: https://9to5google.com/2022/07/28/pixel-6a-factory-images/
"Google told us that the August security patch is coming in a matter of days (i.e., Monday) and will be the first update."
V0latyle said:
This is a known issue with Google devices ever since the Nexus - Google branded devices purchased without a carrier plan are usually bootloader unlockable, while carrier branded devices, whether purchased from Google or from the carrier, are not. There is no known vulnerability that allows circumventing the bootloader lock.
Interesting, I hadn't heard of that. I have heard of some TMobile users being able to request a bootloader unlock through their carrier once the device is paid off.
The problem with the IMEI database theory is that it could be safely assumed that every device would not be unlockable until it was able to connect to the Internet. Most of us with unbranded devices have been able to unlock them right out of the box without even setting up WiFi.
Click to expand...
Click to collapse
I won't swear to it but my P6 was not unlockable until I connected to the internet via wifi or carrier. I"d be curious to see what others have experienced to either confirm or deny what I remember. But in the other instance a year or so ago it seemed to some of us that they had to update their IMEI database, factory reset and then it was registered to allow unlock. No one was entirely sure though but they fixed all of them with one back end update. What else could it have been? As you stated the devices and images are identical. That's why I don't think the August update will do anything at this point. They will have to do something similar, whatever that was, since there was no software update for those affected just a factory reset.
bobby janow said:
I won't swear to it but my P6 was not unlockable until I connected to the internet via wifi or carrier. I"d be curious to see what others have experienced to either confirm or deny what I remember. But in the other instance a year or so ago it seemed to some of us that they had to update their IMEI database, factory reset and then it was registered to allow unlock. No one was entirely sure though but they fixed all of them with one back end update. What else could it have been? As you stated the devices and images are identical. That's why I don't think the August update will do anything at this point. They will have to do something similar, whatever that was, since there was no software update for those affected just a factory reset.
Click to expand...
Click to collapse
As a last ditch effort, I popped in my sim card (verizon) and it triggered an update to the June security patch (40mb update that took forever). I was hopeful that this would fix things, but it still greyed out.
new build # is SD2A.220601.004
Just received my "unlocked" Pixel 6a direct from Google and indeed the entry in Developer Options to unlock the bootloader is greyed out.
Just adding to the list that I also received an "unlocked," carrier agnostic, 6a from Google with the bootloader unlock grayed out.
Related
So, I just got my shiny, new Pixel, and immediately went to unlock the bootloader prior to booting it up for the first time. I was not pleased to be greeted with the following message:
FAILED (remote: oem unlock is not allowed)
What I've found online is that with newer Android phones, you *have* to boot the phone first and enable USB debugging/OEM unlocking from the developer settings. Is there no way around this? I don't want to waste all that time doing that, only to wipe data a minute later.
If I am forced to do it this way, is there a way to get into the developer settings without first adding my google account, etc.? This is really, frustratingly difficult, especially for such an obscenely expensive phone!
Edit: Okay, you can get into settings without adding a Google account, but the "OEM unlocking" option is greyed out, with the message "Connect to the internet or contact your carrier." WTF? I don't even have a SIM in this phone yet. What gives, Google?
hackel said:
So, I just got my shiny, new Pixel, and immediately went to unlock the bootloader prior to booting it up for the first time. I was not pleased to be greeted with the following message:
FAILED (remote: oem unlock is not allowed)
What I've found online is that with newer Android phones, you *have* to boot the phone first and enable USB debugging/OEM unlocking from the developer settings. Is there no way around this? I don't want to waste all that time doing that, only to wipe data a minute later.
If I am forced to do it this way, is there a way to get into the developer settings without first adding my google account, etc.? This is really, frustratingly difficult, especially for such an obscenely expensive phone!
Click to expand...
Click to collapse
I can't answer the main part of the question, but you can skip adding a google account and still enable OEM unlock ability in dev options.
EDIT: regarding your edit, hackel, that is frustrating they make you "activate" it on a carrier or via google before allowing OEM unlock. Very Apple-ish.
hackel said:
Edit: Okay, you can get into settings without adding a Google account, but the "OEM unlocking" option is greyed out, with the message "Connect to the internet or contact your carrier." WTF? I don't even have a SIM in this phone yet. What gives, Google?
Click to expand...
Click to collapse
Did you buy the phone from Verizon or Best Buy? The only ones that support bootloader unlocking are sold direct from Google. The ones from Vz and BB will have "OEM Unlocking" greyed out.
FWIW, I just set mine up this morning. I skipped through most of the settings, didn't add a google app, enabled OEM unlocking, and then unlocked with fastboot with no issues.
EDIT: hmm, I may have put my SIM in it first. Can't remember.
dmbfan36_23 said:
[snip]
Did you buy the phone from Verizon or Best Buy? The only ones that support bootloader unlocking are sold direct from Google. The ones from Vz and BB will have "OEM Unlocking" greyed out.
Click to expand...
Click to collapse
Do you have confirmation of this? We know about Verizon, but where did you see that devices sold through BestBuy or other carriers would not allow unlocking?
dmbfan36_23 said:
Did you buy the phone from Verizon or Best Buy? The only ones that support bootloader unlocking are sold direct from Google. The ones from Vz and BB will have "OEM Unlocking" greyed out.
Click to expand...
Click to collapse
Are you sure? Ars Technica, for instance, among many, are reporting that the Verizon variant can indeed have the BL unlocked. The default for all versions is greyed out until you change it.
dmbfan36_23 said:
FWIW, I just set mine up this morning. I skipped through most of the settings, didn't add a google app, enabled OEM unlocking, and then unlocked with fastboot with no issues.
Click to expand...
Click to collapse
Did you have your phone connected to the internet and/or have a SIM in it when you enabled OEM unlocking?
dmbfan36_23 said:
Did you buy the phone from Verizon or Best Buy? The only ones that support bootloader unlocking are sold direct from Google. The ones from Vz and BB will have "OEM Unlocking" greyed out.
Click to expand...
Click to collapse
No, purchased directly from Google Store. I didn't add a working wifi network the first time (intentionally). I finally just caved in and added one, and after a few seconds the OEM unlocking option became available. I really wish I didn't have to allow the device to check-in with Google simply in order to unlock it.
Oh well, thanks!
efrant said:
Do you have confirmation of this. We know about Verizon, but where did you see that devices sold through BestBuy or other carriers would not allow unlocking?
Click to expand...
Click to collapse
Best Buy is selling the Verizon version. Google has stated that only the ones sold directly from them have unlockable bootloaders.
---------- Post added at 02:07 PM ---------- Previous post was at 02:03 PM ----------
dispatch said:
Are you sure? Ars Technica, for instance, among many, are reporting that the Verizon variant can indeed have the BL unlocked. The default for all versions is greyed out until you change it.
Click to expand...
Click to collapse
Where did they say that? Everything I've seen says it's not unlockable:
http://www.androidpolice.com/2016/10/04/confirmed-verizon-pixels-bootloader-will-not-unlockable/
All of the phones ship locked, but on non-Google versions the option to enable OEM unlocking remains greyed out.
All phones, including those sold by Vz, are carrier unlocked though.
dmbfan36_23 said:
Best Buy is selling the Verizon version. Google has stated that only the ones sold directly from them have unlockable bootloaders.
Click to expand...
Click to collapse
You're absolutely right. I must've read that the Verizon variant will be carrier unlocked and interpreted that as BL.
Still garbage that you have to phone home before the google variant will allow an OEM unlock.
dmbfan36_23 said:
Best Buy is selling the Verizon version. Google has stated that only the ones sold directly from them have unlockable bootloaders.
Click to expand...
Click to collapse
Ok, I think you are talking specifically about the U.S. then. I'm pretty sure Pixel devices sold through carriers here in Canada have unlockable bootloaders. My device hasn't arrived yet, so I haven't personally verified.
Out of curiosity... Has anyone tried removing the Verizon sim card and replacing it with a T-Mobile or AT&T sim before or after first boot to see if it changes the unlock option?
efrant said:
Ok, I think you are talking specifically about the U.S. then. I'm pretty sure Pixel devices sold through carriers here in Canada have unlockable bootloaders. My device hasn't arrived yet, so I haven't personally verified.
Click to expand...
Click to collapse
Please let us know when you do especially if you're on Bell. Thanks!
dmbfan36_23 said:
Did you buy the phone from Verizon or Best Buy? The only ones that support bootloader unlocking are sold direct from Google. The ones from Vz and BB will have "OEM Unlocking" greyed out.
FWIW, I just set mine up this morning. I skipped through most of the settings, didn't add a google app, enabled OEM unlocking, and then unlocked with fastboot with no issues.
EDIT: hmm, I may have put my SIM in it first. Can't remember.
Click to expand...
Click to collapse
Does anyone know for sure that the phones from best buy are locked and have a locked bootloader? I contacted best buy and they said the phones are locked but when I contacted Google support, they said those phones along with the Google store phones are unlocked with a unlocked bootloader. Don't know who to believe? I would like to buy the phone from best buy only if it's unlocked with a unlocked bootloader because the Google stores shipping and logistics are all screwed up. Ordered placed later are getting shipped before earlier orders. Not happy with Google.
Sent from my LGLS990 using Tapatalk
hackel said:
No, purchased directly from Google Store. I didn't add a working wifi network the first time (intentionally). I finally just caved in and added one, and after a few seconds the OEM unlocking option became available. I really wish I didn't have to allow the device to check-in with Google simply in order to unlock it.
Oh well, thanks!
Click to expand...
Click to collapse
Hackel, you don't need to enter your google account info or insert your sim. Just connect to wifi and then go to developer settings to disable OEM unlock.
Source: Me cause I did it, duh
tjarvis said:
Out of curiosity... Has anyone tried removing the Verizon sim card and replacing it with a T-Mobile or AT&T sim before or after first boot to see if it changes the unlock option?
Click to expand...
Click to collapse
That's a no go, the VZW model has a different CID.
I can't speak for why we have to connect to the internet before you can OEM unlock, but toggling this setting before you can unlock the bootloader is a security measure and its a really good thing.
Think about it, if your Pixel was a corporate phone or you actually cared about security, you would want the bootloader to be locked.
Without the need to boot the phone and enter a password:
1. I could steal / borrow your phone when you aren't looking
2. unlock the bootloader with ANY PC
3. then sideload a kernel that did something bad, or fastboot boot to twrp and install some malware
4. then give it back to you
OR
I could just steal your phone and wipe / flash it and keep it or sell it.
Nothing could stop me from doing either if you got your wish. In its current setup, your pin / password / fingerprint can still protect the phone from getting unlocked. You are in control.
I know anyone who wants to unlock the bootloader here does not care about security. I've been there. But you also have to think about who these phones are really made for. They were built to be mainstream phones for everyone. These aren't strictly developer phones. Even Nexus phones had this feature. My 5x and 6p required me to OEM unlock before I could unlock the bootloader. I don't remember if the Nexus 4, 5, 6 made me do this. It may have started with device encryption. I don't remember.
dbrohrer said:
I can't speak for why we have to connect to the internet before you can OEM unlock, but toggling this setting before you can unlock the bootloader is a security measure and its a really good thing.
Think about it, if your Pixel was a corporate phone or you actually cared about security, you would want the bootloader to be locked.
Without the need to boot the phone and enter a password:
1. I could steal / borrow your phone when you aren't looking
2. unlock the bootloader with ANY PC
3. then sideload a kernel that did something bad, or fastboot boot to twrp and install some malware
4. then give it back to you
OR
I could just steal your phone and wipe / flash it and keep it or sell it.
Nothing could stop me from doing either if you got your wish. In its current setup, your pin / password / fingerprint can still protect the phone from getting unlocked. You are in control.
I know anyone who wants to unlock the bootloader here does not care about security. I've been there. But you also have to think about who these phones are really made for. They were built to be mainstream phones for everyone. These aren't strictly developer phones. Even Nexus phones had this feature. My 5x and 6p required me to OEM unlock before I could unlock the bootloader. I don't remember if the Nexus 4, 5, 6 made me do this. It may have started with device encryption. I don't remember.
Click to expand...
Click to collapse
In the past, when you purchased a Nexus device, you could pull it out of the box, boot directly into the bootloader, and unlock the bootloader without booting into Android. Starting with the Nexus 6, if (and only if) you booted into Android before unlocking the bootloader, then you needed to enable the "Allow OEM unlock" setting to unlock the bootloader. (This was done as part of Google's factory reset protection, so that if you lost your device, someone wouldn't be able to just wipe it and use it.) So, having to enable the "Allow OEM unlock" setting is nothing new. However, now, apparently, what is new, is that you cannot unlock the bootloader when you take it out of the box for the first time, without booting into Android first. I fail to see how this is a security measure, as a brand new phone has nothing on it, and anyone can boot into Android anyway when taking it out of the box.
efrant said:
In the past, when you purchased a Nexus device, you could pull it out of the box, boot directly into the bootloader, and unlock the bootloader without booting into Android. Starting with the Nexus 6, if you booted into Android before unlocking the bootloader, then you needed to enable the "Allow OEM unlock" setting. (This was done as part of Google's factory reset protection, so that if you lost your device, someone wouldn't be able to just wipe it and use it.) So, having to enable the "Allow OEM unlock" setting is nothing new. However, now, apparently, what is new, is that you cannot unlock the bootloader when you take it out of the box for the first time, without booting into Android first. I fail to see how this is a security measure, as a brand new phone has nothing on it, and anyone can boot into Android anyway when taking it out of the box.
Click to expand...
Click to collapse
Ok. That sounds correct. I nevered tried to unlock out of the box. I assumed it was the same as after the first boot.
Thanks for the clarification.
efrant said:
In the past, when you purchased a Nexus device, you could pull it out of the box, boot directly into the bootloader, and unlock the bootloader without booting into Android. Starting with the Nexus 6, if (and only if) you booted into Android before unlocking the bootloader, then you needed to enable the "Allow OEM unlock" setting to unlock the bootloader. (This was done as part of Google's factory reset protection, so that if you lost your device, someone wouldn't be able to just wipe it and use it.) So, having to enable the "Allow OEM unlock" setting is nothing new. However, now, apparently, what is new, is that you cannot unlock the bootloader when you take it out of the box for the first time, without booting into Android first. I fail to see how this is a security measure, as a brand new phone has nothing on it, and anyone can boot into Android anyway when taking it out of the box.
Click to expand...
Click to collapse
It hinders someone from loading malware before the phone is booted. It also makes you clearly aware of the "risks".
Sent from my Pixel using XDA Labs
This is the dumbest complain thread that I've read in awhile honestly. You're complaining about a 1 minute inconvenience? Just login and OEM unlock and you're done...it took you longer to type up this thread and find a way around it.
Cares said:
This is the dumbest complain thread that I've read in awhile honestly. You're complaining about a 1 minute inconvenience? Just login and OEM unlock and you're done...it took you longer to type up this thread and find a way around it.
Click to expand...
Click to collapse
Well, there are other reasons for wanting to be able to unlock the bootloader without ever having booted into Android, so I wouldn't call this a complaint thread. For example, getting a complete backup of all the partitions in a (mostly) untouched condition (e.g., partitions like frp, persist, etc.).
Calling someone's question/observation a "dumbest complain thread" isn't really contributing to the discussion.
efrant
Senior Moderator
i know some one will say search or some such but i have and right now am so tired and exhausted so please, if someone could just confirm it the bootloader is locked or if im just being tired and stupid and missing something
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The device says locked, so yes the bootloader is locked. That information at the very last line is referring to your bootloader.
mikeprius said:
The device says locked, so yes the bootloader is locked. That information at the very last line is referring to your bootloader.
Click to expand...
Click to collapse
Thank you, so that means no fast oem unlock and then rooting, correct? there is no easy bootloader unlocking is there?
mark2410 said:
so that means no fast oem unlock and then rooting, correct? there is no easy bootloader unlocking is there?
Click to expand...
Click to collapse
Correct if you have the Verizon version. Not correct if you bought your phone from Google. That screen just means that your bootloader is currently locked. But it's trivial to unlock (and then root, if desired), as long as you don't have the Verizon version.
mikeprius said:
The device says locked, so yes the bootloader is locked. That information at the very last line is referring to your bootloader.
Click to expand...
Click to collapse
jss2 said:
Correct if you have the Verizon version. Not correct if you bought your phone from Google. That screen just means that your bootloader is currently locked. But it's trivial to unlock (and then root, if desired), as long as you don't have the Verizon version.
Click to expand...
Click to collapse
well..... neither. i in the UK and i got it from CEX so, basically second hand but still a shop so it can be returned if i cant unlock it. I have tried unlocking the bootloader but have been unable and as i not done it since my nexus 5 i can tell im so tired that if ive just missed soemthing silly or i cant unlock its bootloader. "Enable OEM Unlock" is greyed out in the dev menu
mark2410 said:
Thank you, so that means no fast oem unlock and then rooting, correct? there is no easy bootloader unlocking is there?
Click to expand...
Click to collapse
No. the idea of having a locked bootloader is so your phone is protected from the get-go. If you could unlock it and root it then the bootloader would be useless.
If you have been trying to unlock it and haven't been able to 1 of 2 (or possibly both issues) are present:
1. You have Verizon and they have updated the patch so Verizon users are not able to unlock unless a new exploit comes out.
2. You do not have fastboot and/or your phone drivers are not working, so fastboot is not properly working on your computer.
3. Both 1 & 2.
mark2410 said:
well..... neither. i in the UK and i got it from CEX so, basically second hand but still a shop so it can be returned if i cant unlock it. I have tried unlocking the bootloader but have been unable and as i not done it since my nexus 5 i can tell im so tired that if ive just missed soemthing silly or i cant unlock its bootloader. "Enable OEM Unlock" is greyed out in the dev menu
Click to expand...
Click to collapse
What version is the software? If it is 7.1.1 you are done. If it is 7.1 you can use depixel8 on it.
mark2410 said:
well..... neither. i in the UK and i got it from CEX so, basically second hand but still a shop so it can be returned if i cant unlock it. I have tried unlocking the bootloader but have been unable and as i not done it since my nexus 5 i can tell im so tired that if ive just missed soemthing silly or i cant unlock its bootloader. "Enable OEM Unlock" is greyed out in the dev menu
Click to expand...
Click to collapse
I'm not sure what that means with it being greyed out. I've seen others with that issue. Here in the United States that's not a problem, so it's likely something with the UK or carrier, or something else. I don't know any information beyond that.
---------- Post added at 02:43 PM ---------- Previous post was at 02:42 PM ----------
TonikJDK said:
What version is the software? If it is 7.1.1 you are done. If it is 7.1 you can use depixel8 on it.
Click to expand...
Click to collapse
He's in the UK. Verizon depixel8 is not applicable.
mikeprius said:
He's in the UK. Verizon depixel8 is not applicable.
Click to expand...
Click to collapse
It is an EE phone, that is what CEX has been selling. So yes depixel8 is applicable.
mikeprius said:
No. the idea of having a locked bootloader is so your phone is protected from the get-go. If you could unlock it and root it then the bootloader would be useless.
If you have been trying to unlock it and haven't been able to 1 of 2 (or possibly both issues) are present:
1. You have Verizon and they have updated the patch so Verizon users are not able to unlock unless a new exploit comes out.
2. You do not have fastboot and/or your phone drivers are not working, so fastboot is not properly working on your computer.
3. Both 1 & 2.
Click to expand...
Click to collapse
2 well peretty sure it was working fine, could use adb to find the device and reboot the phone no problem so no driver issues im aware of
TonikJDK said:
What version is the software? If it is 7.1.1 you are done. If it is 7.1 you can use depixel8 on it.
Click to expand...
Click to collapse
tried it did not work, ran, then would fail after a little bit, it is on 7.1.1
tbh im pretty sure its one thats come from EE so basically the same thing as verizon but the UK version of the devil in telco form. i think im just going to ahve te suck it up and pay the ridiculous price google want for one from them directly
mark2410 said:
2 well peretty sure it was working fine, could use adb to find the device and reboot the phone no problem so no driver issues im aware of
tried it did not work, ran, then would fail after a little bit, it is on 7.1.1
tbh im pretty sure its one thats come from EE so basically the same thing as verizon but the UK version of the devil in telco form. i think im just going to ahve te suck it up and pay the ridiculous price google want for one from them directly
Click to expand...
Click to collapse
Yea, you are done as far as unlocking is concerned. Sorry man.
TonikJDK said:
Yea, you are done as far as unlocking is concerned. Sorry man.
Click to expand...
Click to collapse
np, oh well now if i can just go back in time two weeks and just order one from google because of course now they are currently out of stock. :crying:
why the FFFFFFFFFF do networks lock the f ing bootloader of a bloody device that the point of is that its not full of network shi..... poo???
mark2410 said:
np, oh well now if i can just go back in time two weeks and just order one from google because of course now they are currently out of stock. :crying:
why the FFFFFFFFFF do networks lock the f ing bootloader of a bloody device that the point of is that its not full of network shi..... poo???
Click to expand...
Click to collapse
In the United States most of the major networks would subsidize or pay for some type of incentive for users to use their networks. They have an interest in keeping the users on their network and prevent taking the device to another network esp after paying incentives for it. I have an old Nexus 6 that Sprint paid for that I got at a very low price that is network locked to Sprint despite it being a global compatible network device.
mikeprius said:
In the United States most of the major networks would subsidize or pay for some type of incentive for users to use their networks. They have an interest in keeping the users on their network and prevent taking the device to another network esp after paying incentives for it. I have an old Nexus 6 that Sprint paid for that I got at a very low price that is network locked to Sprint despite it being a global compatible network device.
Click to expand...
Click to collapse
well no, people still pay for the device they just two it over 2 years rather than upfront. but anyway my point was more that people wanting to a buy a pixel probably want to becaues they dont want the networks to have enhanced / ruined it.
im just annoyed that i now have to go return the thing and waste half a day
mark2410 said:
well no, people still pay for the device they just two it over 2 years rather than upfront. but anyway my point was more that people wanting to a buy a pixel probably want to becaues they dont want the networks to have enhanced / ruined it.
im just annoyed that i now have to go return the thing and waste half a day
Click to expand...
Click to collapse
You are referring to either a payment plan or leasing which is different. In the past carriers used to offer 2 yr contracts which immediately subsidized the phone's entire cost. The Nexus 6 I was able to get brand new under $200 because of this. Verizon is packing in credit over 24 months, but this is still money that is being used as a subsidy.
http://www.droid-life.com/2016/11/22/verizon-black-friday-deals-pixel-xl/
Anyways good luck with the phone
Apologies if I posted in the wrong Section.
Well, if you have the MetroPCS version (SM-J727T1) , let me stop some hair pulling.......for now.
If you read my earlier posts, you'll find that LG will let you openly Root their v20 from their Website. However, support for mid-range DID NOT have OEM Unlock.
I moved to the Samsung j7 Prime - a Mid-Range that rivals - if not out performs my rooted Samsung s6 Edge.
1. IF you goto Developer Options and OEM Unlock is not there, dont get the phone
2. IF you get the phone anyway, don't bother XDA
3. Open Developer Options on a Demo Phone 1st and re-check #'s 1 and 2
Why?
I called Samsung Tech just now. Told them why and what I was doing. Why hide? I know it's Voided.
The Tech confirmed the following:
High-End Phones WILL have OEM Unlock
Mid-Range phones are Built to the Carriers Specs -- in other words, Samsung says we dont care... MetroPCS says we do. Remove that Option.
Mid-Range phones are now more likely to NOT have OEM Unlock because of Removal - not just being Hidden
The newest j7 Prime, as it stands, has no Future OEM Unlock plan
Again, this is not limited to Samsung. This is my 2nd Encounter with Mid-Range Phones being Carrier Locked.
LG being the First.
Why would this happen? Business.
Void your $1000us Phone on us - free of charge from the Manufacturer's Site (LG Developer Signup is Free)
The Samsung Tech agreed that Yes, if it's High-End, your chance of Rooting is Exponential now.
More than likely, I will not be watching this thread anymore.
Verification of my statements can be done by calling Samsung. 1 (800) 726-7864
Thanks!
Khronik
Thanks Khronik. I guess one alternative is to buy an unlocked mid-range phone and then bring it to the low-cost carrier, which most of them allow to you to do. The unlocked phones are more expensive than their branded counterparts, but obviously still way cheaper than high end phones. And I've seen some unlockeds that are close in price to their locked, branded counterparts. Avoid Amazon unlockeds, as they come with their own set of problems, from what I've read.
Thanks again.
I only ask because I do not know. Is it at all possible to extract the partitions or go from a factory rom and rebuild the bootloader or other necessary partitions in order to create the GUI setting for OEM unlock or just rebuild it as unlocked? It would almost seem logically possible. Anyone?
unclevername said:
Thanks Khronik. I guess one alternative is to buy an unlocked mid-range phone and then bring it to the low-cost carrier, which most of them allow to you to do. The unlocked phones are more expensive than their branded counterparts, but obviously still way cheaper than high end phones. And I've seen some unlockeds that are close in price to their locked, branded counterparts. Avoid Amazon unlockeds, as they come with their own set of problems, from what I've read.
Thanks again.
Click to expand...
Click to collapse
Be careful with Mid-Ranges. I said I wouldn't Monitor but I have more concrete evidence to Support.
So, thank you.
If you go Mid-Range, CHECK and DOUBLE CHECK the "Actual Phone Series".
We call this a J7 Prime 32gb - when in Fact - SMJ7T21 is Samsung POP - a TOTALLY different Bootloaded Phone
This is Metro PCS, not Samsung.
So yes, you are correct. Now, its up to us to find the Truly Unlocked / Rootable Mid-Ranges worth buying moving forward with this data.
Thanks again Unclevername!
Deep Ellum Dan said:
I only ask because I do not know. Is it at all possible to extract the partitions or go from a factory rom and rebuild the bootloader or other necessary partitions in order to create the GUI setting for OEM unlock or just rebuild it as unlocked? It would almost seem logically possible. Anyone?
Click to expand...
Click to collapse
I might have found the actual Root Cause but I'm not 99.9% sure yet.
There are 3 variants of the J7 Prime:
Prime 16gb
prime 32gb
actual prime 32gb - (POP)
-Prime 16gb - can cause you to lose 16gb of Space with wrong info
-Prime 32gb doesn't exist
-Actual J7 Prime 32gb uses J7 POP Bootloader - https://ach.fcc.gov/products-and-services/mobile-devices/3407/samsung-galaxy-j7-popsm-j727t1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
However, there were International Versions of this phone made. THEY may have OEM Unlock for Rooting purposes.
You cannot use International Build, yet, from what I've seen on North America Release and even toying with different MetroPCS Builds for North America have been sketchy. Remember, this phone DID have OEM Unlock long enough to remove it, but again, some International Versions can be done.
I'ts Phone Browsing time but I will not use a Carrier. This does not mean you will be able to Root.
I would do like Unclevername. Research the Phone I want, go directly to Developer.
turn on Dev.
If OEM Unlock is not there - DO NOT BUY.
Original Equipment Manufacturer is the same as Dell and HP except we cant just burn phones anymore.
They caught on. We buy wisely to achieve better Results.
OEM is the new UEFI, except it is removed.
You cannot inject it because the Current Bootloader MUST be disabled to allow.
OEM Unlock is the disabler.
I should add - Until we find the pattern of Rooting again.
But, if the Manufacturer sells it off the Shelf Rootable - this a Moot Discussion.
It's about what Phone allows Rooting and how to Achieve.
Odin 3.12 tries to compensate - but there are no Unlocked Firmware Options I've seen that I would recommend on XDA.
Sorry - I promise this is the last one.
I forgot to say...
MetroPCS uses the TMK USA Build for J7 Prime 32gb, which is a Geo-Locked Version of POP.
Basically rebuilding the phone from different Country Codes that are compatible.
Easier on the Mind to get a Rootable phone and use Brain Cells elsewhere.
Doesn't mean Root can't eventually be achieved.
-Khronik
OEM UNLOCK on Metropxs phones
ThaKhronik said:
Apologies if I posted in the wrong Section.
Well, if you have the MetroPCS version (SM-J727T1) , let me stop some hair pulling.......for now.
If you read my earlier posts, you'll find that LG will let you openly Root their v20 from their Website. However, support for mid-range DID NOT have OEM Unlock.
I moved to the Samsung j7 Prime - a Mid-Range that rivals - if not out performs my rooted Samsung s6 Edge.
1. IF you goto Developer Options and OEM Unlock is not there, dont get the phone
2. IF you get the phone anyway, don't bother XDA
3. Open Developer Options on a Demo Phone 1st and re-check #'s 1 and 2
Why?
I called Samsung Tech just now. Told them why and what I was doing. Why hide? I know it's Voided.
The Tech confirmed the following:
High-End Phones WILL have OEM Unlock
Mid-Range phones are Built to the Carriers Specs -- in other words, Samsung says we dont care... MetroPCS says we do. Remove that Option.
Mid-Range phones are now more likely to NOT have OEM Unlock because of Removal - not just being Hidden
The newest j7 Prime, as it stands, has no Future OEM Unlock plan
Again, this is not limited to Samsung. This is my 2nd Encounter with Mid-Range Phones being Carrier Locked.
LG being the First.
Why would this happen? Business.
Void your $1000us Phone on us - free of charge from the Manufacturer's Site (LG Developer Signup is Free)
The Samsung Tech agreed that Yes, if it's High-End, your chance of Rooting is Exponential now.
More than likely, I will not be watching this thread anymore.
Verification of my statements can be done by calling Samsung. 1 (800) 726-7864
Thanks!
Khronik
Click to expand...
Click to collapse
You can OEM UNLOCK MetroPCS version (SM-J727T1) even if its not in the deveoper screen. Goto the MetroPCS folder in the apps folder and there is a app to "Unlock Device" in it. Tje first you run it, it will fail and you will need to call metro customer service and they will enable the app to work and unlock your phone. I have done this with three phones.
That is NOT ...OEM UNLOCK.
I'm using the phone now and it just had another update.
My s4? The kid updated Android - Sprint Version - SURPRISE....no more OEM UNLOCK - UNDER DEVELOPER OPTIONS. = No More Root on s4
Meanwhile on my Sprint s6 Edge - ROOTED via OEM UNLOCK still..
Using MetroPcs Unlock allows you to switch from T-Mobile to AT&T after X amount of Days. You will be very mad when you find out we've already done this. aka CARRIER UNLOCK - not OEM UNLOCK FOR ROOT
There were versions of this phone BUT as stated, buying Direct is the surefire way of OEM UNLOCK for Root now.
Peace.
Oh yea - switching Carriers is becoming a hassle depending on the phones now. Too many IMEI Burners, so, all of my "Junk Phones" I used to give to friends that needed phones is done. Bought Legally - Contracts fulfilled. Carrier Unlock works fine - Carrier shows phone unlocked.
Tried using Verizon chip - Not Compatible
AT&T - No Service
U.S. Cellular (where it was bought) - verified Unlocked, worked on Tower
Checked phone specs-
Yes the phone is GSM - "Sim Not Compatible" is Carrier Side and yes the phone is locked down and USC wanted the person to buy another phone instead.
I'm done.
Deuces
Anyone tried this option?
Would it not be possible to "enable" the OEM Unlock option in the developer settings menu if you booted into recovery mode and then mounted /system and used adb to pull the build.prop file and changed the value set for OEM Unlock from 0 to 1 or true then save the edited build.prop file and used adb to push it back onto the phone?
NewbSandwich said:
Would it not be possible to "enable" the OEM Unlock option in the developer settings menu if you booted into recovery mode and then mounted /system and used adb to pull the build.prop file and changed the value set for OEM Unlock from 0 to 1 or true then save the edited build.prop file and used adb to push it back onto the phone?
Click to expand...
Click to collapse
Ok, but then what? There arent any root methods or rooting apps that can root the sm-j727t1
hello I used firmware combination J737T1UVU4ASB1 for j737t1, flash with miracle box and I see that I think OEM Unlock to enable it, I have not yet enabled.
now that it has combination I am thinking of converting j737t1 to j737u with OEM enabled I hope it works.
here is the capture: http://www.mediafire.com/folder/msm2fczpgcxgu/J737
Look https://youtu.be/-_X2HFd7C_g
Enviado desde mi SM-J737T1 mediante Tapatalk
I attained root, here is my guide.
https://forum.xda-developers.com/galaxy-j7/how-to/root-guide-samsung-galaxy-j7-prime-t4010939
GuestK00251 said:
hello I used firmware combination J737T1UVU4ASB1 for j737t1, flash with miracle box and I see that I think OEM Unlock to enable it, I have not yet enabled.
now that it has combination I am thinking of converting j737t1 to j737u with OEM enabled I hope it works.
here is the capture: http://www.mediafire.com/folder/msm2fczpgcxgu/J737
Click to expand...
Click to collapse
they are talking about J727T1 here, not J737
Hey is this a viable option? https://shell.boxwares.com/Download.aspx?L=2676
the-her0 said:
Hey is this a viable option? https://shell.boxwares.com/Download.aspx?L=2676
Click to expand...
Click to collapse
All that firmware will do is put factory test firmware on the device.
ThaKhronik said:
Apologies if I posted in the wrong Section.
Well, if you have the MetroPCS version (SM-J727T1) , let me stop some hair pulling.......for now.
If you read my earlier posts, you'll find that LG will let you openly Root their v20 from their Website. However, support for mid-range DID NOT have OEM Unlock.
I moved to the Samsung j7 Prime - a Mid-Range that rivals - if not out performs my rooted Samsung s6 Edge.
1. IF you goto Developer Options and OEM Unlock is not there, dont get the phone
2. IF you get the phone anyway, don't bother XDA
3. Open Developer Options on a Demo Phone 1st and re-check #'s 1 and 2
Why?
I called Samsung Tech just now. Told them why and what I was doing. Why hide? I know it's Voided.
The Tech confirmed the following:
High-End Phones WILL have OEM Unlock
Mid-Range phones are Built to the Carriers Specs -- in other words, Samsung says we dont care... MetroPCS says we do. Remove that Option.
Mid-Range phones are now more likely to NOT have OEM Unlock because of Removal - not just being Hidden
The newest j7 Prime, as it stands, has no Future OEM Unlock plan
Again, this is not limited to Samsung. This is my 2nd Encounter with Mid-Range Phones being Carrier Locked.
LG being the First.
Why would this happen? Business.
Void your $1000us Phone on us - free of charge from the Manufacturer's Site (LG Developer Signup is Free)
The Samsung Tech agreed that Yes, if it's High-End, your chance of Rooting is Exponential now.
More than likely, I will not be watching this thread anymore.
Verification of my statements can be done by calling Samsung. 1 (800) 726-7864
Thanks!
Khronik
Click to expand...
Click to collapse
Guys, links are down, could u pls reupload again or somehow made them available?
ty in advance
Hi all,
I just bought an "international" (i.e. non-US) version of the S10e on ebay, model SM-G970F dual-sim, which is an Exynos variant (I think), with the understanding that Exynos variants are bootloader-unlockable.
I happily went into the settings menu, enabled developer options, and was very sad to discover that there is no OEM unlock option. Is there a trick to make it appear, or what is the procedure to unlock the bootloader on this phone? Do I need to return it and buy a Pixel 3 instead?
Thanks!
Check this out with sim card: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
Update: I was able to get the OEM unlock option!:victory:
Yes @snowqwer, I eventually found a similar article that said basically the same things as the one you linked: (cannot post links, google for "fix-missing-oem-unlock-toggle-samsung-galaxy-devices", on "the custom droid" dot com)
That one also says that, as of Jan 20, 2019, that method shouldn't work anymore ... but somehow it did for me! (I'm not complaining ...)
I can definitely confirm that, before unlocking, the bootloader showed the dreaded "KG: Prenormal" line, but I suspect this is somehow different than the 7 days theft prevention situation, cause this was (supposedly) a new, unopened, never used before phone, unless of course the ebay seller cheated me (but the package was sealed).
Is it possible that all new phones ship with "KG: Prenormal" and only after checking for an update they allow unlock? What made it appear for me was, other than bringing the date back and forth, which I did several times unsuccessfully, when I for the first time went to check for an update. The phone tried to do that during the initial setup but I turned the wifi off and didn't let it. Maybe setting the date back then forth wasn't really necessary, but as a new phone, it first needed to check with "the mothership" whether it's allowed to be OEM unlocked? Just guessing, but I don't really like the idea that Samsung can decide to lock my phone remotely without my consent.
TL;DR: basically, I set the date one month back, went to manually check for updates, then brought the date back to normal, and "OEM unlock" appeared, but I suspect the thing that really made it unlock was just checking for updates, as this is a brand new phone.
EDIT: Also to be clear, this phone has never in its short life seen a sim card yet.
I have a Cricket branded Denver varient and it has a locked bootloader... ugh
The website says it is not eligible for bootloader unlocking but here's my question
Is it possible to cross flash the RETUS firmware and be able to unlock the bootloader like that?
Also if I do cross flash, will I lose my IMEI in the process? Do I need to remove the sim card while flashing?
Also OEM UNLOCK is greyed out....
In my experience, no, you can't flash RETUS on the Cricket model. Even if you could, that wouldn't change the fact that the IMEI is forever blacklisted by Motorola for unlocking as it is a Cricket device, unless Cricket changes their policies sometime in the next 100 years. As for OEM Unlocking, it becomes toggleable after being connected to the internet for a while, but serves absolutely no purpose.
Go disable "Mobile Services" in the apps so it stops auto downloading random junk apps then debloat it as much as possible. Truly that's the best bet you have with their version. I broke down and bought an unlocked one from eBay.
Can anyone else give me further advice
xStealth said:
In my experience, no, you can't flash RETUS on the Cricket model. Even if you could, that wouldn't change the fact that the IMEI is forever blacklisted by Motorola for unlocking as it is a Cricket device, unless Cricket changes their policies sometime in the next 100 years. As for OEM Unlocking, it becomes toggleable after being connected to the internet for a while, but serves absolutely no purpose.
Go disable "Mobile Services" in the apps so it stops auto downloading random junk apps then debloat it as much as possible. Truly that's the best bet you have with their version. I broke down and bought an unlocked one from eBay.
Click to expand...
Click to collapse
Thanks so much
I need some help
If cricket won't let you unlock, there's nothing left to help. It's a stock android phone.