I got the Unlock Code from Moto with no problem, but can't get the phone to take it. FAIL, over and over again. I've tried several times, rebooted the phone, powered off, even tried an FDR. I keep getting a 'FAIL" message trying to push the code to the phone.
Just got the phone (used) today and I do have Unlock enabled in Dev Options. CID is 0x0032, obviously unlockabled since I did get the code from Moto. Twice. I redidthe Unlock request with a new string and got the same code again. Nothing is working. I've unlocked 15 or more Moto phones and never had anything like this happen before.
Using "fastboot oem unlock UNIQUE_KEY [20-character unlock code string]". Copied it, typed it manually, etc etc. FAIL FAIL FAIL.
Frustrating. Any clues/suggestions?
- - - - -
Edit to add: This phone has (I presume) the newest firmware on it, QZKS30.Q4-40-95-9 (RETUS), which has not been uploaded to lolinet yet.
Could this newest update be the problem? If so, can I safely roll back to 95-6 or even something older?
= = = = = = = = =
SOLVED. There was apparently an issue with the first phone I tried. Bought a second XT2113-2 relatively cheap (64GB) which came with the same 40-95-9 firmware, and it took the unlock code without a hitch.
I recall that I experienced something similar to this as well. A little bit of searching lead me to believe my issue was an older stock firmware bug. My stock firmware was initially from Jan 2021 and I did ota updates until it got to about Aug 2021 and then the phone unlocked. Can't say for sure that the deviced just needed time to "phone home" before allowing unlocking tho (I've read rumors).
If there is a ota update available, try that. I do know that I am able to relock/unlock on the 40-95-6 (Feb 2022) RETUS stock firmware.
notmyrealhandle said:
I recall that I experienced something similar to this as well. A little bit of searching lead me to believe my issue was an older stock firmware bug. My stock firmware was initially from Jan 2021 and I did ota updates until it got to about Aug 2021 and then the phone unlocked. Can't say for sure that the deviced just needed time to "phone home" before allowing unlocking tho (I've read rumors).
If there is a ota update available, try that. I do know that I am able to relock/unlock on the 40-95-6 (Feb 2022) RETUS stock firmware.
Click to expand...
Click to collapse
Thanks for replying. This phone has 40-95-9 firmware (March 1, 2022) which looks to be the latest OTA.
I have wondered if I'm stuck in another one of the newer Moto's (or Android's) mysterious holding patterns. Maybe it'll work in a few days. I will certainly post here if that's the case. . . . But why give me the Unlock button plus the Unlock Code, but then hold me back from actually pushing it to the phone? That wouldn't make a lot of sense.
This is the exact message returned by the bootloader every time:
(bootloader) usage: fastboot oem unlock < unlock code >
FAILED (remote failure)
I believe I'll try reflashing the 40-95-9 firmware, downloaded this morning via Rescue and Smart Assistant.
Reflashing firmware didn't help.
Edit to add:
I should probably stress, I flashed the entire firmware with no problems at all.
Should that suggest that this bootloader unlocking failure is not a hardware problem? . . . because if broke hardware is a possibility, I would definitely want to return this phone to the seller.
Moondroid said:
Reflashing firmware didn't help.
Edit to add:
I should probably stress, I flashed the entire firmware with no problems at all.
Should that suggest that this bootloader unlocking failure is not a hardware problem? . . . because if broke hardware is a possibility, I would definitely want to return this phone to the seller.
Click to expand...
Click to collapse
Two other things you can try:
1. make sure you are using an up to date fastboot exe (I'm using fastboot version 33.0.1-8253317 on ubuntu linux).
2. Try from both the bootloader mode and fastbootd mode on the device - I forget how to get to fastbootd from stock `adb reboot fastboot` might do it.
EDIT I'm pretty sure you want to be in the bootloader mode. Just thought I'd mention it as fastbootd was new to me and some fastboot commands seem to like the device to be in one mode or the other.
HTH
notmyrealhandle said:
Two other things you can try . . .
Click to expand...
Click to collapse
Still nothing.
I found some newer adb & fastboot utils (2021 vs 2018) and tried those. That just changed the error message a teensy bit (replaced "remote failure" with a couple of bare quote marks).
I also uninstalled & reinstalled my Motorola drivers before trying the newer adb & fastboot. That didn't help either.
Trying to boot twrp gives me a "permission denied" error.
So all I can think to try now is to run another firmware reinstall via LMSA (Rescue and Smart Assistant), just to see if that hiccups anywhere as much as anything. (I manually flashed all the files the first time.)
I think it's past time for me to say something like "this doesn't just suck, it SUPER-sucks." Moto gave me the phreaking Unlock code, but the phone won't let me use it.
Moondroid said:
Moto gave me the phreaking Unlock code, but the phone won't let me use it.
Click to expand...
Click to collapse
It will only work 48 hours after the unlock email is sent, as per this thread <https://forum.xda-developers.com/t/oem-unlocking-grayed-out-on-moto-g-play-2021.4259833/page-2>
I recently went through this myself. It was really baffling because the customer service / tech support would not tell me anything about it. Maybe it's some kind of hyper secret security measure?
Just keep the phone online and wait it out.
slipchicken said:
It will only work 48 hours after the unlock email is sent, as per this thread <https://forum.xda-developers.com/t/oem-unlocking-grayed-out-on-moto-g-play-2021.4259833/page-2>
I recently went through this myself. It was really baffling because the customer service / tech support would not tell me anything about it. Maybe it's some kind of hyper secret security measure?
Just keep the phone online and wait it out.
Click to expand...
Click to collapse
I tried the unlock code 5 minutes after I got it. Why would I wait 48 hours? Lol . . .
If this is another "time-delay" thing it doesn't make any sense at all. OEM Unlock was already enabled, the phone gave me an unlock string to send Moto, and I got the unlock key from Moto with no delays at all. Within an hour after unboxing the phone I was trying to push an unlock code to the phone.
I also tried getting another code from Moto, generated a new string and all, but the second code Moto sent me was exactly the same as the first. I did try it (again) on the phone but got the same "FAILED" message as before.
This is just nuts. Unless the latest OTA 95-9 is in fact the culprit. Moto's unlock-code process might still send unlock codes that possibly will no longer work after a certain point? Hopefully I'll get a definitive answer on this aspect soon.
Moondroid said:
Moto's unlock-code process might still send unlock codes that possibly will no longer work after a certain point? Hopefully I'll get a definitive answer on this aspect soon.
Click to expand...
Click to collapse
I meant that it will only start working once 48 hours have passed. Leaving internet active may be a requirement, and a restart may be a requirement too.
For instance if you get the first code email at 8:00am on June 7th, the code will only work after 8:00am on June 9th.
EDIT: Also I have tried manually changing the time in the phone's settings and it didn't work. I had to wait the full 48 hours for it to start working.
I do agree however that it is absolutely nuts of Motorola to do this without any sort of explanation. That's why I assume it's some kind of secretive or misguided anti-theft measure.
slipchicken said:
I meant that it will only start working once 48 hours have passed. Leaving internet active may be a requirement, and a restart may be a requirement too.
For instance if you get the first code email at 8:00am on June 7th, the code will only work after 8:00am on June 9th.
EDIT: Also I have tried manually changing the time in the phone's settings and it didn't work. I had to wait the full 48 hours for it to start working.
I do agree however that it is absolutely nuts of Motorola to do this without any sort of explanation. That's why I assume it's some kind of secretive or misguided anti-theft measure.
Click to expand...
Click to collapse
I was in that thread you quoted and I don't remember anything about having to wait AFTER getting the unlock code. Wait for OEM Unlock to show as enabled in Dev Options, yes, I'm thoroughly familiar with that. But I have never-never-never had to wait for an unlock code to work after receiving it from Moto. If that's in there somewhere please point more specifically? because I've unlocked a whole bunch of Moto phones and as I said, I've never heard of being able to enable OEM Unlock, getting the unlock code from Moto and then having to wait to use it.
See bottom of top post. The phone had some kind of problem that wouldn't allow it to accept the unlock key.
Related
So back in the day with MM i unlocked the Bootloader with the DCunlocker since i had already registered my HuaweiID on their "wrong site" and it would ve been a pain to get through their horrible system.
( Which it is, just took me 2 hours deleting amd re registering accounts! Seriously, Huawei already sits on the short straw but this is seriously the worst experience i ever had with simply logging into a website )
Long story short i somehow lost the Bootloader code and upgrading to Nougat seems to have relocked the Bootloader.
So i went to Huawei s website and got the code from there.
Booted into fastboot put it in and it got rejected ( wrong code apparently)
OEM unlock is checked and not greyed out and I'm on stock L09C432B380.
Anyone got any advice? I'm out of options at this point.
Edit: And yes, i double checked all the numbers and IDs everything is correct. Though it's been a while since I've done the procedure so maybe I've missed a tiny detail
Bump ;
tldr: Bootloader code apparently "wrong" despite being obtained from Huaweis website.
Any ideas?
Sent from my FRD-L09 using XDA Labs
Don't know how to help, but I'm having same problems with how I registered too
denism81 said:
Don't know how to help, but I'm having same problems with how I registered too
Click to expand...
Click to collapse
Unfortunately i cant quite remember how i eventually got it to work but i think i logged into my original account by going on a different login server, "vmall7" instead of "vmall5"
or something similar, deleted the account and reregistered on the other one. Maybe even the chinese one.
There are a number of topics about that around here so the solution should be somewhere.
Doesnt help much though when your code just gets rejected
Edit: is there a possible connection between the way the Beta Nougat update "locked" instead of "relocked" the bootloader?
Because i did unlock the bootloader on EMUI 4 and just updated through the Hicare beta to Nougat without manually relocking first.
So ,after i surrendered to Huaweis Websites ( again ) i paid for the DC unlocker again and it did get me a different bootloader code...
And here i thought that code never changes... well apparently it does
I hope you like stories because I like telling them.
So, I've been trying to get this phone to work for several weeks now and I'm hoping someone here can help. The backstory is going to make me sound really stupid, but here you go. I bought this phone initially to replace my old Nokia Lumia 710 which is still *functioning*, but lets be honest it needs to be replaced. It cost me $150 if I remember correctly. Well, it worked fine for about a week and then I dropped it and shattered the screen through the LCD layer. I backed up the contents while there was still enough LCD fluid for me to see what I was doing before the whole screen went black.
I then proceeded to take the phone to a repair place where they charged me $200 dollars to replace the screen. Yes, I know I could have just as easily bought one brand new, but the half-off sale was over and I've always been one to fix things instead of replacing them. Of course maybe that will change with this experience. Anyway, when they finally got it back to me and when I turned it on it said there was a software update available. So, I followed the standard procedure and allowed it to download and restart. . . but it got stuck in a loop on the restart. At this point I knew very little about the phone, so I left it at home to die and switched the SIM card back to my Nokia.
Later that day I researched how to 'reset' it, which gave me the instructions for how to put it into bootloader/download mode, and I thought "Well, it still works, I bet they can fix this at the phone repair place". So I charged it, brought it there and showed them that it still worked -sort of- and they told me they would fix it in a day for $30.
A week later they called and said "We can't fix this thing, take it back free of charge". It didn't make any sense to me because the internet made it sound like a 'soft brick' was easy to fix. So I took it back and decided to try fixing it on my own. I downloaded the HTC drivers and got to work. The first thing I found was the HTC official RUU.exe and I tried using it to fix the phone. However, it returned with a 'signature error', which I researched and as far as I can tell it's because the official RUU is nougat and my firmware has the key for marshmallow.
I looked for a RUU.exe that was a marshmallow version, but HTC took down all the downloads that I found links to and no ones seems to have saved it anywhere. Instead I found directions to update manually using a combination of ADB/fastboot/htc_fastboot. I set them up to work on the command line and they all recognize that the phone is connected. I downloaded a marshmallow RUU.zip and tried to flash it, but it failed with the message "main version NOT ALLOWED". I searched around and supposedly it's because the only zips I could find are lower versions than the broken version installed on mine. (something about s-on?)
I then thought that maybe I could update the firmware and then use the official RUU to get it working again. From what I could tell getting a TWRP recovery on there would give me enough access to the phone to allow firmware to be updated. I searched all over for ways to install TWRP, but it failed to flash also. Supposedly I need the bootloader unlocked.
I got an account on HTCDev and started following the directions but the command:
fastboot oem get_identifier_token
Returns an error "last byte is 0x00, disable unlock"
So I guess I can't unlock the bootloader either. . .
The current state of the phone is:
Software Status: Official
Locked
S-ON
Which seems to be the worst case scenario for trying to fix it. Also, just some other info, the OS version is 1.55.617.4
and it's a USA Unlocked version, if that wasn't already described by the OS version. . .
Oh and it's encrypted.
So yeah, I'm giving up today. I already ordered a new phone, however I still think it would be really satisfying to get it working again. You guys are the pros and I am in posession of the most defiant piece of non-functional silicon to ever exist, so if you can tell me how to beat it into submission I will be very happy. Thanks!
-Corneilius
Corneilius said:
I hope you like stories because I like telling them.
So, I've been trying to get this phone to work for several weeks now and I'm hoping someone here can help. The backstory is going to make me sound really stupid, but here you go. I bought this phone initially to replace my old Nokia Lumia 710 which is still *functioning*, but lets be honest it needs to be replaced. It cost me $150 if I remember correctly. Well, it worked fine for about a week and then I dropped it and shattered the screen through the LCD layer. I backed up the contents while there was still enough LCD fluid for me to see what I was doing before the whole screen went black.
I then proceeded to take the phone to a repair place where they charged me $200 dollars to replace the screen. Yes, I know I could have just as easily bought one brand new, but the half-off sale was over and I've always been one to fix things instead of replacing them. Of course maybe that will change with this experience. Anyway, when they finally got it back to me and when I turned it on it said there was a software update available. So, I followed the standard procedure and allowed it to download and restart. . . but it got stuck in a loop on the restart. At this point I knew very little about the phone, so I left it at home to die and switched the SIM card back to my Nokia.
Later that day I researched how to 'reset' it, which gave me the instructions for how to put it into bootloader/download mode, and I thought "Well, it still works, I bet they can fix this at the phone repair place". So I charged it, brought it there and showed them that it still worked -sort of- and they told me they would fix it in a day for $30.
A week later they called and said "We can't fix this thing, take it back free of charge". It didn't make any sense to me because the internet made it sound like a 'soft brick' was easy to fix. So I took it back and decided to try fixing it on my own. I downloaded the HTC drivers and got to work. The first thing I found was the HTC official RUU.exe and I tried using it to fix the phone. However, it returned with a 'signature error', which I researched and as far as I can tell it's because the official RUU is nougat and my firmware has the key for marshmallow.
I looked for a RUU.exe that was a marshmallow version, but HTC took down all the downloads that I found links to and no ones seems to have saved it anywhere. Instead I found directions to update manually using a combination of ADB/fastboot/htc_fastboot. I set them up to work on the command line and they all recognize that the phone is connected. I downloaded a marshmallow RUU.zip and tried to flash it, but it failed with the message "main version NOT ALLOWED". I searched around and supposedly it's because the only zips I could find are lower versions than the broken version installed on mine. (something about s-on?)
I then thought that maybe I could update the firmware and then use the official RUU to get it working again. From what I could tell getting a TWRP recovery on there would give me enough access to the phone to allow firmware to be updated. I searched all over for ways to install TWRP, but it failed to flash also. Supposedly I need the bootloader unlocked.
I got an account on HTCDev and started following the directions but the command:
fastboot oem get_identifier_token
Returns an error "last byte is 0x00, disable unlock"
So I guess I can't unlock the bootloader either. . .
The current state of the phone is:
Software Status: Official
Locked
S-ON
Which seems to be the worst case scenario for trying to fix it. Also, just some other info, the OS version is 1.55.617.4
and it's a USA Unlocked version, if that wasn't already described by the OS version. . .
Oh and it's encrypted.
So yeah, I'm giving up today. I already ordered a new phone, however I still think it would be really satisfying to get it working again. You guys are the pros and I am in posession of the most defiant piece of non-functional silicon to ever exist, so if you can tell me how to beat it into submission I will be very happy. Thanks!
-Corneilius
Click to expand...
Click to collapse
There are still several option to fix this phone.
might want to try flashing a newer ruu that is still Marshmallow version like this one https://androidfilehost.com/?fid=24459283995314374 or his one https://androidfilehost.com/?fid=24399994186368579
htc_fastoot oem rebootRUU
htc_fastboot flash zip 2PQ9IMG_HIA_AERO_UL_M601_SENSE7GP_1.56.617.1_signed.zip
htc_fastboot reboot
and there is still the possibility to update your firmware to 2.xx.617.x using a singed firmware.zip file making your phone accept the new ruu signature implemented in Nougat ruu.
Btw you can't unlock your BL because the "allow oem unlock" option was not previously turned on from the "developer option" (this requires a booting OS).
Sweet, you found a Marshmallow ruu!
I'll try it, thanks!
-Corneilius
OG Pixel from Verizon, had it for years, battery has been really ****ty lately. So I had to send my phone in to get a new battery, and the cost was similar to go thru google store, so I did. Wiped the phone, restored to stock android, but left bootloader unlocked. Got the phone back today and version of android was downgraded and bootloader was locked.
How ****ed am I and what are my recourses? Tried google support, they're nearly useless.
If you never booted the device yet you can try "fastboot flashing unlock" and it will just re-unlock. Other than that I don't think you will ever see a unlock status on that phone. This is why I do my repairs myself.
Fastboot flashing unlock was unsuccessful, but I suspect that was because the phone was booted up for "troubleshooting" with Google "support."
I assume then there's no way to return it to the post-flash pre-boot state without some closely guarded hardware and software?
Before updating in any way... Search Verizon unlock Pixel and see if that process will unlock. If you allow update past a certain level stuck with no options then if Verizon locked.
Oh, would never allow an update. I'm not crazy. Tried the unlock method with uninstalling the phone app before you get internet access the day I got it, still no dice. Thanks tho.
I just did a credit card chargeback as they sent me back my device in an unusable condition and refused to compensate for it. We'll see how it shakes out in a few weeks probably. Bought a refurb Pixel 3 in the meantime and it was already unlocked, so all is well.
Thanks for the replies though.
-N
n8lee said:
Fastboot flashing unlock was unsuccessful, but I suspect that was because the phone was booted up for "troubleshooting" with Google "support."
I assume then there's no way to return it to the post-flash pre-boot state without some closely guarded hardware and software?
Click to expand...
Click to collapse
Can you tell me what security patch you are on? If you are somewhere around Android 9 patch (potentially Android 10 early patches) you can re-unlock. If you try ticking the OEM unlock option in Dev options or if i heard correctly the phone wont boot? If you know your exact version you can try flashing it through recovery, or trying "fastboot unlock" after ticking the oem unlock. Also remember those old workarounds of removing android.phone and such? Yeah try those. Good luck. We'll try and get you unlocked again.
Greetings, so I recently upgraded my phone to oxygenos12 and it came with a lot of glitches and I hate it. Try to flash back oxygen11 and realised the bootloader is locked. So I tried downloading back the unlock token for the phone from my email and the oneplus token page keeps coming up blank with no token download. I saw you have to be logged in to download it and I did the same and I get the same blank page. what's really going on here? I really need oxygen11 back since this 12 here isn't supporting my two sim cards and my cellular data isn't working!!!!
OnePlus page must be down. I’ve been trying to get on there for the last 12 hours.
I have been trying this too,, it's coming blank.. like what's happening here I just get my new phone which is t mobile varient
Website is still down for me. I contacted OnePlus and they went on the routine of trying to make me fill out for another unlocking token and telling me it’s 7 days blah blah blah. They weren’t getting the fact that their website is broken. Finally after 30 different screen shots and copied links they finally understood. Hopefully the IT team can get the page back up asap
Still blank for me. Just my luck... I've been putting off rooting my oneplus 6t for so many years and finally decided to do it...
Shanebacchus said:
Greetings, so I recently upgraded my phone to oxygenos12 and it came with a lot of glitches and I hate it. Try to flash back oxygen11 and realised the bootloader is locked. So I tried downloading back the unlock token for the phone from my email and the oneplus token page keeps coming up blank with no token download. I saw you have to be logged in to download it and I did the same and I get the same blank page. what's really going on here? I really need oxygen11 back since this 12 here isn't supporting my two sim cards and my cellular data isn't working!!!!
Click to expand...
Click to collapse
Hi you shouldn't need a token to unlock bootloader for OnePlus devices.
You should also have OEM unlock enabled in developer options.
Fastboot OEM unlock
I have also been trying to reach the site and is coming out blank ,I have to tryng to get my token since yesterday.Just tried and still not working.Does anybody know a work around to this like another address thats working?Or is it just i wait game till its up again.
st3wart said:
Website is still down for me. I contacted OnePlus and they went on the routine of trying to make me fill out for another unlocking token and telling me it’s 7 days blah blah blah. They weren’t getting the fact that their website is broken. Finally after 30 different screen shots and copied links they finally understood. Hopefully the IT team can get the page back up asap
Click to expand...
Click to collapse
Good morning sir have you been able yet to get on the unlocking token site?Cauese i just tried and still coming up blank.I dont know what to do now t o get my token to unlock the boatloader.
Same problem here.i talked to Oneplus using their chat service and they are saying they are working on it.
Not sure how long it will take to restore service?
also blank here (NE USA). since 08/11/2022
i tried with a foreign vpn and instead of a blank page i received a oneplus custom 404 error
if you inspect the code of the unlock_token page. all the code looks like it's there
my OP tech support says the link doesn't work because i won't send me phones imei # over email... BIG DERP tech support at our service
Vmo x said:
Hi you shouldn't need a token to unlock bootloader for OnePlus devices.
You should also have OEM unlock enabled in developer options.
Fastboot OEM unlock
Click to expand...
Click to collapse
this is inncorrect for the TMOBILE variant. FOR TMOBILE ONLY.... the oem unlock option is only so you can retrieve the unlock code. once you receive the token you will be able to flash it and fully unlock the phone.
celo0735 said:
Good morning sir have you been able yet to get on the unlocking token site?Cauese i just tried and still coming up blank.I dont know what to do now t o get my token to unlock the boatloader.
Click to expand...
Click to collapse
I still haven't been able to get on the site. It's still broken here for me. I talked to chat support multiple times and it takes some convincing that the site is actually broken. Then I send them links and screenshots and they say they will send it over to IT.. but is been almost a week and nothing has been fixed... I asked them it they could send me my unlock token file in a email and no response lol
This is my first experience with one plus and it's not so good the phone is good but the tech support sucks nobody seems to know anything about why the page is broken or when it will be fixed or for that matter any way to deal with this token crap.
Looks like OnePlus doesn’t give a ****.this is ridiculous
I just got done with chat support was able to drag some info out apparently the support department has only received a communication from the team handling the token page issue with please give more time. I have a feeling that they have no idea what's going on and have a complete communication breakdown so who knows how long this is gonna take. I only received the generic answer of please give another 24hrs for a response "I won't hold my breath" in the meantime dose anyone know a bypass for getting around this token nonsense?
Vmo x said:
Hi you shouldn't need a token to unlock bootloader for OnePlus devices.
You should also have OEM unlock enabled in developer options.
Fastboot OEM unlock
Click to expand...
Click to collapse
Wrong!!! The T-Mobile variant requires a unlock token. Only the factory unlocked version does not.
clustercluck said:
I just got done with chat support was able to drag some info out apparently the support department has only received a communication from the team handling the token page issue with please give more time. I have a feeling that they have no idea what's going on and have a complete communication breakdown so who knows how long this is gonna take. I only received the generic answer of please give another 24hrs for a response "I won't hold my breath" in the meantime dose anyone know a bypass for getting around this token nonsense?
Click to expand...
Click to collapse
There is no way. I've been looking everywhere and there is nothing that says how to bypass it. If this doesn't get fixed tomorrow, I'm sending phone back and not getting a t-mobile variant ever.
TheSayaMan said:
Wrong!!! The T-Mobile variant requires a unlock token. Only the factory unlocked version does not.
Click to expand...
Click to collapse
Technically it is the T-Mobile software that's triggering that. If you convert it to global or EU, you don't need it, but you get stuck having to have root to get data working (software thinks the phone is dual SIM and it breaks it). Also, if your device is SIM locked, it's stuck that way unless you flash back to T-Mobile firmware to unlock it.
EtherealRemnant said:
Technically it is the T-Mobile software that's triggering that. If you convert it to global or EU, you don't need it, but you get stuck having to have root to get data working (software thinks the phone is dual SIM and it breaks it). Also, if your device is SIM locked, it's stuck that way unless you flash back to T-Mobile firmware to unlock it.
Click to expand...
Click to collapse
Well what your saying is not possible because in order to flash firmware, you need to have the bootloader unlocked so NO!!!
TheSayaMan said:
Well what your saying is not possible because in order to flash firmware, you need to have the bootloader unlocked so NO!!!
Click to expand...
Click to collapse
Nope, just an MSM Tool that can flash a T-Mobile variant. I don't know if one exists for the 9 but there is one for the 9 Pro that you can use to get to EU software and then use the global 9 downgrade package to get back to proper 9 firmware.
Convert your T-Mobile (LE2127) to EU via MSM, No unlock.bin needed!
*** Use this at your very own risk. *** You will lose all data *** Backup your working modemst1/2 and persist. If you lose these for any reason, it's unique to your device and not recoverable if you didn't back up (via MSM or other people). ***...
forum.xda-developers.com
Got an unlocked Pixel 6a delivered yesterday from the Google Store. Was planning to root it immediately upon setup but the "OEM Unlock" option in Dev settings is greyed out, saying "Connect to the internet or contact your carrier". I am connected to the internet, have a Visible SIM installed, and am on the most recent Android 13 update available for the 6a. I have tried all of the options, including factory resetting, going through setup without SIM or internet, etc. Google support has been of little to no help.
Pulled the build.prop using adb shell getprop and the value ro.oem_unlocking_supported does not exist.
Same here - same issue
this is super annoying, i wanted to root also! they need to fix this ASAP
Perhaps you can close this redundant thread since you cross posted to this one and it already has over 200 posts.
6a from Google: Can't unlock bootloader
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...
forum.xda-developers.com
Odd, when I got June update it became available. But I haven't received any update since, just waiting for ota. I think I'll wait rather than sideload, maybe it will stick.
tcat007 said:
Odd, when I got June update it became available. But I haven't received any update since, just waiting for ota. I think I'll wait rather than sideload, maybe it will stick.
Click to expand...
Click to collapse
Not for me. Just loaded stable 13 via beta; checked the unlock switch; still gray. So, I did the reset (but not the sim-removal-turn off wifi, etc) and still no bootloader unlock. What I haven't done is try the fastboot unlock anyway. It seems it would simply not work. However, trying to sideload the June OTA put my phone into a bootloop (which would have been so easy to fix with an unlocker BL) so not really going to mess around much.
Have you tried factory resetting after updating? That's what worked for me.
Yeah, I have, several times, but unfortunately to no avail.
I did the factory reset from the setting app and that did the trick. I had 13 plus the update before I did this.
mmead1143 said:
I did the factory reset from the setting app and that did the trick. I had 13 plus the update before I did this.
Click to expand...
Click to collapse
Yeah, for whatever reason that hasn't been working for me.
Just a guess, maybe go to settings/about phone/regulatory labels, and check your model number. Make sure they didn't mistakenly send you a locked to carrier phone.
Do you know of a list like that? That would be so helpful to so many.
I did the sign up for beta, get ota 13, sign out of beta, thing. Got 13 instantly (although takes 45 minutes to install), and unlock bootloader is still available.
bobby janow said:
Do you know of a list like that? That would be so helpful to so many.
Click to expand...
Click to collapse
What list are you talking about?
roirraW edor ehT said:
What list are you talking about?
Click to expand...
Click to collapse
A list of model numbers and which is Verizon, unlocked, ATT, Google unlocked etc. Things like that so if someone can't unlock the bl they can check their version/model. For instance I bought a BB unlocked and the model is:
GA03715-US
and in Regulatory Labels is shows GX7AS So I'm pretty much at a loss as to which devices are which if it even matters. I just see so many people that still can't unlock the bl even after updates and factory reset that maybe there is a pattern or versions that will not allow it.
@bobby janow You forgot to type a response when you quoted me. It just seemed like when you said something about a list that maybe you had posted that in the wrong thread, since I didn't notice anything else in the thread that made sense for that response.
Edit: Oh, you edited it now. Nevermind. I understand now.
list of pixel 6a models - Google Search
Although the first search result only lists:
Google Pixel 6a model numbersThe four model numbers are as follows:
A4RGB62Z
A4RG1AZG
A4RGX7AS
A4RGB17L
Click to expand...
Click to collapse
GSMArena only lists three:
ModelsGX7AS, GB62Z, G1AZG
Click to expand...
Click to collapse
tcat007 said:
I did the sign up for beta, get ota 13, sign out of beta, thing. Got 13 instantly (although takes 45 minutes to install), and unlock bootloader is still available.
Click to expand...
Click to collapse
Just received 6a today, straight outta the box set it up no sim installed checked version, it was 12 , OEM unlock greyed out, did a factory reset , no help, still greyed out, took the ota update , it's was just a newer version of 12, oem still greyed out, factory reset this version and it worked, oem unlock granted
HEY THIS MIGHT WORK FOR U!
Was having the same issue, nothing seemed to be working.
I had success finally, though!
Be sure you realize your phone will be wiped, etc.
Airplane Mode & No SIM inserted.
Remove All Accounts From Phone (to prevent issues with locks, etc)
Make sure you can put the phone in fastboot & adb modes
I put the phone in various modes to test, and ended up doing this:
[ REBOOT PHONE INTO SIDELOAD MODE VIA: ]
Code:
$ adb reboot sideload
Once the phone is ready to accept the side load OTA package, push that happy bullsh1t right on down the USB cable to the phone via:
Code:
adb sideload ~/MagicalGarbageDump/bluejay-ota-sd2a.220601.003-ddfde1f7.zip
From the OTA file downloaded directly from Google at THIS SITE. It's this one:
12.1.0 (SD2A.220601.003, Jun 2022)Linkddfde1f7edcdbb2b3de41d24f6c3f31587f836f387cab4cc6d16adee32bcab8a
After downloading and flashing that OTA, I had to "reset to factory settings" about two more times, seemingly randomly, and then it worked!
I made sure to have:
- NO SIM CARD IN THE PHONE.
- NO WIRELESS NETWORKS CONNECTED.
I am kind of annoyed it seemingly randomly decided to work, but also grateful that it finally unfzcked itself.
Also no luck over here. I bought my Pixel 6a directly from Google store as a "non locked device". It was sent from France Google store to Spain.
I'm in the 5th September security update under Android 13.
Tried all the tricks posted before: factory reset from settings and from recovery, sideload OTA, tried with sim and without it... No luck, OEM unlock still greyed out.
I wrote to Google about it. They asked me for the imei. After all, no help received from them to solve it.
Still waiting for "magically" disappear the greyed option...
l would send it back and get the p6 pro. For a few dollars more you get a better phone and no unlock issues.