I installed the Nov 2022 update yesterday (TP1A.221105.002), and suddenly the developer OEM Unlock option is no longer greyed out and I am able to enable it!
Not sure if this has happened for anyone else, but thought I might share some info in case it helps anyone.
My journey:
Purchased in September.
Booted up to Android 12.
Installed OTA via system settings.
Ran stock Android 13 for two months - checked OEM Unlock option every couple days with no luck.
Installed November OTA via system settings and rebooted.
Checked developer options today and OEM Unlock is working!
Not sure what would have fixed the issue. I didn't see any mention of this being a fix in the update. ¯\_(ツ)_/¯
Is unlock working for anyone else after Nov OTA?
No, still not working
In order to activate the OEM switch all you need to do is boot into the system and then do the first OTA. Reboot and then factory reset. That's it if you bought a Google unlocked version. Getting a "new" device with A13 on it means the phone is a refurbished one since all P6a are shipped with A12. If the update to a later version of A12 doesn't enable the switch return the device. Don't call Google support, don't pass go. Just return it for your money back.
No clue on how the latest Nov A13 patch magically enabled the switch but that is not usual to say the least. It doesn't matter if you have a sim in or not. I had 2 sims in both Verizon and unlock was available after update and reset.
If you bought it from a 3rd party or a carrier all bets are off. Either you got lucky or you didn't. Return it or keep it and live with a locked bootloader. Does that help clear it up? Can we let these threads die a merciful death already?
If it was so easy for us to just return it — sure we'll did it. But if people asking and searching for solution for hours and days — maybe return isn't the easiest solution for them.
Also many people getting there OEM button active after some time for no reason or after some weird combinations of resetting and updating...
I have two p6a, one with a13 from the box with no problem and the other with a13 updated by OTA to a13 still having this problem.
ectavgen said:
If it was so easy for us to just return it — sure we'll did it. But if people asking and searching for solution for hours and days — maybe return isn't the easiest solution for them.
Also many people getting there OEM button active after some time for no reason or after some weird combinations of resetting and updating...
I have two p6a, one with a13 from the box with no problem and the other with a13 updated by OTA to a13 still having this problem.
Click to expand...
Click to collapse
You're right, sorry. This is a quality control problem and it's a shame it needs to be dealt with. I posted the way it should be and obviously that's not always the way it is. I stand corrected.
In my case, I guess patiently using stock pixel like a good little googler payed off for whatever reason. Either way, I'm just pumped I get to root this thing and really start personalizing!
I was fortunate with both mine. At first I was puzzled then mad af...(before I had seen the post saying to update then reset). Ofc by then, I had already begun installing and configuring most of my non-root 'daily' apps then my root apps with the tedious ADB perms. Next day ofc...I see the post saying to wipe then recite about every profanity I know...at max volume. Proceed with wipe, re-updated w/ota...nothin'! Waited a bit and one more re-boot and it worked. 2nd phone was the same with only 1 reboot after the ota...I just waited a lil longer. Was soo annoyed at first...waiting a month or two and I'd have blown a gasket 4 sure.
ectavgen said:
No, still not working
Click to expand...
Click to collapse
Did you try to turn off the "Use Developer Options" and see if the "OEM Unlocking" pops out? I had the "OEM Unlocking" button greyed out from when I received the phone from Amazon until I updated Android 12 June update. Out of desperation, I decided to turn off the "Use Developer Options", and then the "OEM Unlocking" popped out and then I enabled it. Give it a try.
Of course I did)
I have tried every possible way mentioned on the internet I guess.
I came to share my experience cause just yesterday the oem unlock enabled itself.
I bought a few days ago a pixel 6a in mexico on an online local store that stated that devices were unlocked.
Without knowing this issue with oem unlock, I conected to wifi and updated to a13.
Then I was curious about root and discovered that oem was grayed out. I proceed to format factory and tried again with no luck.
On wednesday I inserted my sim in order to verify carrier compatibily and I was able to have data and make calls. I use the sim for about and hour and then i inserted again on my main device.
Then, all of sudden, yesterday oem unlock was enabled. I activate it in order to verify and it´s working fine.
I´m not sure if it was the november update or having used a sim on the device, but now it´s enabled.
P.S. The pixel 6a it´s not mine, but now I´m going to buy one for myself and root it.
Related
Prior to making this thread, I'm active in this thread, talking about my update situation.
------------------------------------------
UPDATE: This is how you bypass the activation screen! Big thanks to @henser for figuring it out!
------------------------------------------
Here's my situation (which seems to fit others in the same situation so it's not just me) : My wife and have Moto Gs (hers an XT1028 wifi-only, mine an XT1031 wifi-only), and hers is "locked by Verizon and cannot be activated" (basically meaning it's never been scanned by a VZW cashier). She received the 5.1 OTA, and updated. Everything went smoothly, and she decided she wanted a fresh start, so she factory reset the device.
Bad move.
Apparently, the old bypass methods for Moto G's activation screen are now patched and no longer work in LP. This means that because VZW has "locked the device" and it "cannot be activated", she is ultimately stuck at the Setup Wizard / Activation screen with nothing to do but wait until someone figures out the new method.
Traditionally, a person might think of something else to do like unlock the bootloader and root it, but the XT1028's bootloader cannot be unlocked.
Did you try pulling down the notifications bar. Just try to get the navigation buttons back then press home or recent apps. That might be able to help!
jakeh9777 said:
Did you try pulling down the notifications bar. Just try to get the navigation buttons back then press home or recent apps. That might be able to help!
Click to expand...
Click to collapse
That method has been patched as well. To my experience, every previous bypass has been patched. I know of 5, and have extensively searched for more.
DamianHelixTV said:
That method has been patched as well. To my experience, every previous bypass has been patched. I know of 5, and have extensively searched for more.
Click to expand...
Click to collapse
Ok I would like to help out more and try but I don't want to reset my device right now. Just try all methods even older ones that are found on other devices too. Just let everyone know when you found one and I will just search the Internet for awensers too.
happened to me aswell i did factory reset, may i know if i can rollback to 4.4.4 ??
henser said:
happened to me aswell i did factory reset, may i know if i can rollback to 4.4.4 ??
Click to expand...
Click to collapse
Doesn't seem to be a way to downgrade, other than getting Motorola to give a free replacement Moto G and it just happen to not be on LP.
DamianHelixTV said:
Doesn't seem to be a way to downgrade, other than getting Motorola to give a free replacement Moto G and it just happen to not be on LP.
Click to expand...
Click to collapse
can you tell me where is the link to chat with motorola, thank you
henser said:
can you tell me where is the link to chat with motorola, thank you
Click to expand...
Click to collapse
This should be it: (link)
i have given these 2 options but unfortunately none of the options work for me
The first option is called Advance Exchange: This require for you to provide a credit card to which we place a hold for $100, now this program includes a premium fee for $24.99 (amount that will not be refundable), in regards to allow us to send you the replacement device to you first, and you have up to 5 days to return the defective one to Motorola, once received the defective device, the hold will be released. The shipping label you will receive along with the shipping instructions will expire in 5 days.
Erick: The second option is called Return and Exchange: On this scenario, you must send the defective device first, once received we process the replacement and send it to you. In this case, it takes 2 Business days for us to receive your device and as soon as we receive this unit it takes 3 - 5 Business days in order to be delivered to you. The shipping label you will receive along with the shipping instructions will expire in 3 days.
henser said:
i have given these 2 options but unfortunately none of the options work for me
The first option is called Advance Exchange: This require for you to provide a credit card to which we place a hold for $100, now this program includes a premium fee for $24.99 (amount that will not be refundable), in regards to allow us to send you the replacement device to you first, and you have up to 5 days to return the defective one to Motorola, once received the defective device, the hold will be released. The shipping label you will receive along with the shipping instructions will expire in 5 days.
Erick: The second option is called Return and Exchange: On this scenario, you must send the defective device first, once received we process the replacement and send it to you. In this case, it takes 2 Business days for us to receive your device and as soon as we receive this unit it takes 3 - 5 Business days in order to be delivered to you. The shipping label you will receive along with the shipping instructions will expire in 3 days.
Click to expand...
Click to collapse
I chose the 2nd option. Though... I didn't know the label expired. Crap. Gotta get a new label.
yes i was tryng to get to the setting, i made a wipe data reset. and a window popped up. asking me if i want to get roaming but gave me a global number i tapped into it and i could go to add as an contact. and got into the dial number is there a way to dial a number and go to the settings tab ? i could activate or deactivate airplane mode and activate the bluetooth but i couldn't turn on the wifi.
edit:
also i could enter to file explorer but i cant select home or the other buttons and my pc detect the phone but doesn't show any files
Try dialing *228 then select option 1
Can I just BLOCK the upgrade to lollipop?
My MOTXT1028NPP works just fine for what I need.
I Don't have service, WIFI only.
Every time I turn it on, it says it's gonna upgrade to lollipop. Only option have is to delay until later the same day.
I don't want ANY upgrade. It works just fine for what I need.
It appears from this thread that the upgrade will prevent me using the device without service and prevent installing a custom rom???
Maybe only if I factory reset?
What if I need a factory reset for some other purpose?
Googling suggests that some people have experienced slowdowns from the upgrade that were fixed by a factory reset.
I considered the possibility that I might be able to install a custom ROM before it updates,
but those all seem to have issues.
Is there away to just PREVENT, PERMANENTLY, any and all upgrades, including this one??
spamme0 said:
Can I just BLOCK the upgrade to lollipop?
My MOTXT1028NPP works just fine for what I need.
I Don't have service, WIFI only.
Every time I turn it on, it says it's gonna upgrade to lollipop. Only option have is to delay until later the same day.
I don't want ANY upgrade. It works just fine for what I need.
It appears from this thread that the upgrade will prevent me using the device without service and prevent installing a custom rom???
Maybe only if I factory reset?
What if I need a factory reset for some other purpose?
Googling suggests that some people have experienced slowdowns from the upgrade that were fixed by a factory reset.
I considered the possibility that I might be able to install a custom ROM before it updates,
but those all seem to have issues.
Is there away to just PREVENT, PERMANENTLY, any and all upgrades, including this one??
Click to expand...
Click to collapse
On the contrary, we've already figured out a bypass for the activation but that's only needed if you plan on factory resetting.
In any case, you said you don't want to update. I think you can disable the OTA app, that would make the update notification not happen again until you want to in the future.
Also, unless you're one of those people who have an unlocked bootloader and a custom recovery on the XT1028 (some people do who got the device early) you can't flash any ROMs.
DamianHelixTV said:
On the contrary, we've already figured out a bypass for the activation but that's only needed if you plan on factory resetting.
In any case, you said you don't want to update. I think you can disable the OTA app, that would make the update notification not happen again until you want to in the future.
Also, unless you're one of those people who have an unlocked bootloader and a custom recovery on the XT1028 (some people do who got the device early) you can't flash any ROMs.
Click to expand...
Click to collapse
Have you seen this on youtube
watch?v=fiXZwX_Wvx8&feature=youtu.be
I have found it on reddit
/r/MotoG/comments/3tbyq0/1st_gen_moto_g_on_lp_new_activation_bypass/
So I had an interesting thing happen today. My phone's audio stopped working entirely. Any app that had or used sound causes my device to lock up entirely. Went through the standard steps, all the way to flashing back to stock, with the same issue. Called Google, and they informed me that it is 100% a hardware issue, and I need to RMA. Great. So I am in need of some advice. Since I have to send this to Google, I will want to be stock. I know that locking the bootloader is problematic, and will ultimately cause me to not be able to unlock. Should I lock the bootloader? It is going back to Google, but if they see it is a Verizon device with an unlocked bootloader, they may not like it. Also, while I know the people on XDA aren't mindreaders, maybe someone else will have dealt with this. What are the odds of getting a device with an exploitable build? Has anyone gotten a replacement from Google, and if so, what build was it running? I know I shouldn't expect to be able to unlock, but I can hope.
You have to wipe the device anyways and send it in. So why not just take the extra minute to lock the bootloader as a precautionary step?
dymmeh said:
You have to wipe the device anyways and send it in. So why not just take the extra minute to lock the bootloader as a precautionary step?
Click to expand...
Click to collapse
The only thing I am worried about is if something happens before locking. I know that locking the bootloader has been heavily advised against by beaups, and I just don't want anything to happen during the locking process.
stompysan said:
So I had an interesting thing happen today. My phone's audio stopped working entirely. Any app that had or used sound causes my device to lock up entirely. Went through the standard steps, all the way to flashing back to stock, with the same issue. Called Google, and they informed me that it is 100% a hardware issue, and I need to RMA. Great. So I am in need of some advice. Since I have to send this to Google, I will want to be stock. I know that locking the bootloader is problematic, and will ultimately cause me to not be able to unlock. Should I lock the bootloader? It is going back to Google, but if they see it is a Verizon device with an unlocked bootloader, they may not like it. Also, while I know the people on XDA aren't mindreaders, maybe someone else will have dealt with this. What are the odds of getting a device with an exploitable build? Has anyone gotten a replacement from Google, and if so, what build was it running? I know I shouldn't expect to be able to unlock, but I can hope.
Click to expand...
Click to collapse
Dealing with this exact problem right now on my wife's Verizon Pixel.
It was bootloader unlocked and rooted, but still auto updated for the Feb update. Soon after, audio broke just as you described. I was able to get it back working for a little bit after a couple factory image flashes, but it broke again for good.
I contacted Google and they set me up with an RMA. I flashed an exploitable factory image, relocked the bootloader, and sent it in last Wednesday. The replacement should be delivered tomorrow. I'm really hoping it was on the shelf at Google since launch and depixel. The phone was useless otherwise, so I had no choice but to send it back. I wish they'd just send me a non-Verizon.
"Your replacement Pixel Phone Silver 32 GB (Verizon) was shipped on February 20, 2017 via FXG"
I'll try to update after the replacement comes tomorrow.
jsbeagle said:
Dealing with this exact problem right now on my wife's Verizon Pixel.
It was bootloader unlocked and rooted, but still auto updated for the Feb update. Soon after, audio broke just as you described. I was able to get it back working for a little bit after a couple factory image flashes, but it broke again for good.
I contacted Google and they set me up with an RMA. I flashed an exploitable factory image, relocked the bootloader, and sent it in last Wednesday. The replacement should be delivered tomorrow. I'm really hoping it was on the shelf at Google since launch and depixel. The phone was useless otherwise, so I had no choice but to send it back. I wish they'd just send me a non-Verizon.
"Your replacement Pixel Phone Silver 32 GB (Verizon) was shipped on February 20, 2017 via FXG"
I'll try to update after the replacement comes tomorrow.
Click to expand...
Click to collapse
I went ahead and did the same thing. Let me know what build your replacement is. I still have my fingers crossed.
They all say they're Verizon models but almost everyone on this forum who has done this got a Google Play edition (it just has a Verizon SIM).
When I went through it, they said locking the bootloader was not necessary. Also, I got a brand new device with all accessories but they told me not to send the accessories in since I'd only be getting a phone back. Great experience for me. Props to Google for great service.
stompysan said:
I went ahead and did the same thing. Let me know what build your replacement is. I still have my fingers crossed.
Click to expand...
Click to collapse
YES!!!!!
Replacement Pixel just delivered. Appears to be brand new. All accessories included (they told me to only return the phone)
Verizon SIM was installed (I removed before booting it up).
Android Version 7.1
October 5 security patch
Build NDE63P
OEM unlocking toggle was greyed out until I connected to wifi, then I was able to toggle it to allow the bootloader to be unlocked. It does appear to be a google play edition in every way except the sim card that is included.
This is awesome. I'm now jealous of my wife and her non Verizon version. (We both still have the old grandfathered unlimited data and used the best buy trick to get Pixels on subsidized upgrades)
PsiPhiDan said:
They all say they're Verizon models but almost everyone on this forum who has done this got a Google Play edition (it just has a Verizon SIM).
When I went through it, they said locking the bootloader was not necessary. Also, I got a brand new device with all accessories but they told me not to send the accessories in since I'd only be getting a phone back. Great experience for me. Props to Google for great service.
Click to expand...
Click to collapse
jsbeagle said:
YES!!!!!
Replacement Pixel just delivered. Appears to be brand new. All accessories included (they told me to only return the phone)
Verizon SIM was installed (I removed before booting it up).
Android Version 7.1
October 5 security patch
Build NDE63P
OEM unlocking toggle was greyed out until I connected to wifi, then I was able to toggle it to allow the bootloader to be unlocked. It does appear to be a google play edition in every way except the sim card that is included.
This is awesome. I'm now jealous of my wife and her non Verizon version. (We both still have the old grandfathered unlimited data and used the best buy trick to get Pixels on subsidized upgrades)
Click to expand...
Click to collapse
You have no idea how excited this makes me. I have been extremely worried, but looks like I didn't need to be. Thanks!
stompysan said:
You have no idea how excited this makes me. I have been extremely worried, but looks like I didn't need to be. Thanks!
Click to expand...
Click to collapse
For the record, the only person who got a Verizon model still was able to unlock the bootloader (it was a new device with old 7.1 software) using dePixel8 so I think you're set regardless! Google is good!
For those who had the audio-craps-out problem, can I ask when you ordered you phones?
My wife & I have Google Store devices. I ordered mine in the first week after launch, and it's been great. I ordered my wife's in early January and she has audio-craps-out disease.
So I'm wondering if there's a bad batch of Pixels?
UnusualSuspect said:
For those who had the audio-craps-out problem, can I ask when you ordered you phones?
My wife & I have Google Store devices. I ordered mine in the first week after launch, and it's been great. I ordered my wife's in early January and she has audio-craps-out disease.
So I'm wondering if there's a bad batch of Pixels?
Click to expand...
Click to collapse
I got a Verizon version in January and it had an issue I haven't seen too many have, but it was audio related and apparently a hardware defect: mine had awful sound through the headphone jack only. Sounded like hissing and scratching beneath all the music. As if you didn't have the connection tight (but I did). Got the replacement and all is well!
UnusualSuspect said:
For those who had the audio-craps-out problem, can I ask when you ordered you phones?
My wife & I have Google Store devices. I ordered mine in the first week after launch, and it's been great. I ordered my wife's in early January and she has audio-craps-out disease.
So I'm wondering if there's a bad batch of Pixels?
Click to expand...
Click to collapse
Mine was ordered through Verizon on November 12, and shipped the next day. I am going to assume that it was a launch device.
Mine was purchased from bestbuy.com in mid November. It actually shipped from a local Best Buy store.
I believe there is a bad batch of pixels. I'm currently on my second one.
A couple weeks ago my pixel crashed and shutdown and well never turned on again. Basically the phone was bricked. Idk how or why. I was running perfectly and I only had the bootloader unlocked.
Long story short. I contacted my provider (Project Fi) and they sent me a new one. Received it the next day. (Great customer service!!)
So yes I believe there is a bad batch of pixels out there.
I have an interesting problem, at least from my perspective. I'm getting a replacement Verizon Pixel tomorrow due to GPS issues and confirmed at the store. I'm assuming the refurb will be running 7.2. My current device is running dev preview 8.1. My understanding is that I can't transfer settings/programs from a higher version to a lower, i.e. my current to the new device. So what would be the best way of doing this? Initial thoughts are to boot the new device without the sim, only wifi, and have it auto update to 8.0. Then I'm not sure how I would enroll that device to get to 8.1 and then start the transfer. Do I need to wipe the new device once it updates after I log in? And you know if I call support they will be of minor help since it's 8.1.
I'm not worried about bootloader unlock since I don't unlock anyway. I also assume that it will come unable to unlock which is fine by me. Any thoughts are welcome or experiences doing something like this. TIA
Well it looks like I'm talking to myself here. So this is what happened. Got the new device yesterday, fired it up without the sim so I could transfer settings and data from the original P. Didn't use the cable and it asked me if I wanted to transfer from the other phone and I said yes. Well it couldn't or said it couldn't and immediately gave me an update notification from 7.2 to 8.0 September patch. Rebooted and tried to figure out how to get the 8.1 settings to 8.0 but alas there was no way I could see.
Ok, so I'm in for a couple of hours restoring apps and data and passwords what can ya do? Immediate update to October patch and I'm off to the races, right? Well here's the interesting part. I naturally go into developer options after enabling them. Just something I always do so I can adb stuff and transfer pics and apks. The switch for OEM unlock is live!! Not grayed out! Well I don't bootloader unlock or root but there was no way I was letting this opportunity pass and flipped the switch. And there it remains, still active after I put in the sim and rebooted.
Now I know this came from Verizon and not Google from the tracking and return label. So what do you think happened? This one just slipped by? Unenrolled the old P without the sim now and it wiped the device and rebooted. That one still has oem grayed out and says something like.. "connect to the internet or contact your provider". I set up wifi and even logged in once again just to check but it's still grayed out. Removed my account and wiped one more time and back it goes.
I hope you find this interesting reading but I really don't care if you don't. lol Just kidding naturally but I will not flip the switch back in case you are thinking of asking me to test it. But I can do some diagnostics that don't require locked bl or root if you wish. The new device is pristine and the battery seems much, much better since I had the old one since black Friday last year and it seemed to be degrading.
I was wondering if anyone else purchased the unlocked version from Samsung and it arrived with Developer options already enabled.
I have never seen that before, so it made me wonder if somehow I was receiving a device that had been returned. There don't appear to be any issues (packaging was sealed, device appeared new, etc).
The alternative would be that it restore the menu as part of the transfer from a Galaxy Note 20 Ultra backup, but this would be the first time. The Note 20 was restored from an S10 Plus, but the settings had to be enabled again on the new device.
twistedumbrella said:
I was wondering if anyone else purchased the unlocked version from Samsung and it arrived with Developer options already enabled.
I have never seen that before, so it made me wonder if somehow I was receiving a device that had been returned. There don't appear to be any major issues (packaging was sealed, device appeared new, etc) beyond the bootloader appearing to possibly be unlocked, as well.
The alternative would be that it restore the menu as part of the transfer from a Galaxy Note 20 Ultra backup, but this would be the first time. The Note 20 was restored from an S10 Plus, but the settings had to be enabled again on the new device. I don't see them whitelisting that.
Click to expand...
Click to collapse
Maybe an engineering build fell into the production line by mistake, please check if it's an engineering build
That would be a game changer, for people developing custom roms and gaming drivers for it
flairepathos.info said:
Maybe an engineering build fell into the production line by mistake, please check if it's an engineering build
That would be a game changer, for people developing custom roms and gaming drivers for it
Click to expand...
Click to collapse
Samsung claimed it was "a new change for the ease of our users" until I questioned it. It then became a software glitch. I don't know
twistedumbrella said:
Samsung claimed it was "a new change for the ease of our users" until I questioned it. It then became a software glitch. I don't know
Click to expand...
Click to collapse
Ohhh yeah remember they are getting pooped on for disabling cameras if you unlock your bootloader LOL this is just fantastic
flairepathos.info said:
Ohhh yeah remember they are getting pooped on for disabling cameras if you unlock your bootloader LOL this is just fantastic
Click to expand...
Click to collapse
That's the Fold, not the Flip.
twistedumbrella said:
That's the Fold, not the Flip.
Click to expand...
Click to collapse
Oh well XD
So Samsung support is a lot like Amazon. If it isn't in the FAQs, they attempt to make up an answer or connect you to someone else. Pretty sure I could have spent an hour getting help trying to make calls on my toaster if I sounded confident it's possible.
I was initially asked for my IMEI to answer the question. I asked how a device that just released would have an expired warranty, but was told it was to verify the device was new. After giving it, I was told about having the premium warranty...
This led to being told how the option was enabled as a new way to make things easier on the user. When asking why they enabled something that could potentially void my warranty, I was sent to someone else who claimed it was a glitch. When asking why the OEM unlock option was missing (which I later found has a time delay on newer devices), I was put on hold for 15 minutes.
I finally said I had somewhere to be and was told they were happy to have helped. I still don't know if it was part of the restore, but i'll be waiting the week to make sure OEM unlock appears before I go back to discuss a defective firmware.
I did a restore from my s21 Ultra and the developer options was not enabled. Also oem unlock was there from the first second I enabled it.
Interesting... I am torn between wiping to find out if that fixes it and trying to fix it first to end up wiping it anyway.
Has anyone had any problems with this variant? Factory Unlocked to any carrier in the WORLD and no bootloader unlock. Motorola says it's ineligible. Any thoughts?
Articul8Madness said:
Has anyone had any problems with this variant? Factory Unlocked to any carrier in the WORLD and no bootloader unlock. Motorola says it's ineligible. Any thoughts?
Click to expand...
Click to collapse
Use a different email address. You have unlocked too many devices in a period of time so it won't let you with that email. Try again with new or alt email.
sosthenisRR said:
Use a different email address. You have unlocked too many devices in a period of time so it won't let you with that email. Try again with new or alt email.
Click to expand...
Click to collapse
First I have to wait for the OEM to ungrey. Stll greyed out.
Articul8Madness said:
First I have to wait for the OEM to ungrey. Stll greyed out.
Click to expand...
Click to collapse
That should only take 72 to 96 hours if you leave it on and connected to data and/or wifi the whole time.
sosthenisRR said:
That should only take 72 to 96 hours if you leave it on and connected to data and/or wifi the whole time.
Click to expand...
Click to collapse
Can you please elaborate? I have the OEM unlock option greyed out. I followed instructions on another thread and factory reset, retried with wifi, no sim, no login, no joy.
Now will this change if I wait 72 hours? I already have a code from motorola, but I'm going on call for work again shortly and I can't leave the sim out for 72 hours. Thanks.
Edit: Just bought the model today, hoping for a LineageOS phone. Third try of the "buy a new phone" strategy, but I got a different model than was advertised, XT2131-1
nibake said:
Can you please elaborate? I have the OEM unlock option greyed out. I followed instructions on another thread and factory reset, retried with wifi, no sim, no login, no joy.
Now will this change if I wait 72 hours? I already have a code from motorola, but I'm going on call for work again shortly and I can't leave the sim out for 72 hours. Thanks.
Edit: Just bought the model today, hoping for a LineageOS phone. Third try of the "buy a new phone" strategy, but I got a different model than was advertised, XT2131-1
Click to expand...
Click to collapse
Yes you will need to wait a few days like he said. Just leave it alone, don't reset or anything. Leave the phone booted up and preferably on wifi. It will eventually become available.
wickedxjay said:
Yes you will need to wait a few days like he said. Just leave it alone, don't reset or anything. Leave the phone booted up and preferably on wifi. It will eventually become available.
Click to expand...
Click to collapse
So this is really a new thing Motorola/Lenovo is doing? My phone is factory unlocked. XT-2211-2 (I got the 2022 Stylus model factory unlocked no carrier brand). I did manage to get the unlock code from moto's site (Looks like it was just glitchy when i first tried but another poster said keep at it and i did and the 3rd time they mailed it to me) but the OEM is still greyed out. Turned on the phone Sunday. So I have to wait for it to "Trigger"?
wickedxjay said:
Yes you will need to wait a few days like he said. Just leave it alone, don't reset or anything. Leave the phone booted up and preferably on wifi. It will eventually become available.
Click to expand...
Click to collapse
Listen to my other post. Leave the sim card in. Leave it on. For 72+ hours. The option should then be ready after that.
Articul8Madness said:
So this is really a new thing Motorola/Lenovo is doing? My phone is factory unlocked. XT-2211-2 (I got the 2022 Stylus model factory unlocked no carrier brand). I did manage to get the unlock code from moto's site (Looks like it was just glitchy when i first tried but another poster said keep at it and i did and the 3rd time they mailed it to me) but the OEM is still greyed out. Turned on the phone Sunday. So I have to wait for it to "Trigger"?
Click to expand...
Click to collapse
And as for the xt2211 this is NOT the forum for said device. Please either request one be made or wait. I understand we all get itchy to root and make our devices custom but when the device was just released less than 6 months ago I wouldn't expect much. Sorry guys.
But to answer, yes young Padawan, patience is a must.
sosthenisRR said:
Listen to my other post. Leave the sim card in. Leave it on. For 72+ hours. The option should then be ready after that.
And as for the xt2211 this is NOT the forum for said device. Please either request one be made or wait. I understand we all get itchy to root and make our devices custom but when the device was just released less than 6 months ago I wouldn't expect much. Sorry guys.
But to answer, yes young Padawan, patience is a must.
Click to expand...
Click to collapse
Ok. OEM just unlocked so I'm rooting now of my own recognizance.
nibake said:
Can you please elaborate? I have the OEM unlock option greyed out. I followed instructions on another thread and factory reset, retried with wifi, no sim, no login, no joy.
Now will this change if I wait 72 hours? I already have a code from motorola, but I'm going on call for work again shortly and I can't leave the sim out for 72 hours. Thanks.
Edit: Just bought the model today, hoping for a LineageOS phone. Third try of the "buy a new phone" strategy, but I got a different model than was advertised, XT2131-1
Click to expand...
Click to collapse
Swinging by to report that this was accurate for me and after the 3 days I was able to cycle developer options and unlock OEM, already got the code from Motorola during the waiting period.
Quick update:
Finally unlocked my 2nd device with this. Letting you guys know that wifi alone will not unlock it. Left it on wifi for 8 days no OEM unlock. Dropped my sim card in it and it unlocked instantly. It also won't turn "on" so to speak, just tap it when it looks like its not active and the prompt will come up like its hidden.