Question Haven't factory reset, should I update? - Google Pixel 6a

I haven't done the factory reset after the update to Android 13. Apparently, this factory reset fixes the developer toggle for oem unlock being greyed out. Now the Oct 13 update is available. Should I complete the factory reset first to get the oem toggle? Could this be update affect my ability to access it later?

motolio said:
I haven't done the factory reset after the update to Android 13. Apparently, this factory reset fixes the developer toggle for oem unlock being greyed out. Now the Oct 13 update is available. Should I complete the factory reset first to get the oem toggle? Could this be update affect my ability to access it later?
Click to expand...
Click to collapse
There's no definitive answer to this. Updating may or may not correct the OEM Unlocking unavailable toggle issue. If you intend to factory reset, might as well do it after updating if the toggle is still unavailable.

Alright. I volunteer as tribute! Downloading now.

Nope. Still greyed out. Looks like factory reset for me.

Related

Factory Reset after bootloader unlock

I was wonder why all manufacturers make the device do a factory reset after unlocking bootloader. Is there something internal to bootloader unlock that works only when a factory reset is performed?
I also performed an oem unlock on my android one device (micromax canvas A1+) and I chose not to do a factory reset. Now the device is stuck in a bootloop. Why would this behaviour be?
brainwave92 said:
I was wonder why all manufacturers make the device do a factory reset after unlocking bootloader. Is there something internal to bootloader unlock that works only when a factory reset is performed?
I also performed an oem unlock on my android one device (micromax canvas A1+) and I chose not to do a factory reset. Now the device is stuck in a bootloop. Why would this behaviour be?
Click to expand...
Click to collapse
I guess as far as it is for my knowledge. The bootloader is related to hardware not software that is why if once it is unlocked the factory reset has to be done because after that system acts different after it is unlocked. Like in my moto g after is has been unlocked instead of bootlogo it show the warning bootloader has been unlocked logo that is why it has to be reset.
And another thing doesnt matters if you reflash your whole stock firmware but once bootloader is unlocked, it is unlocked. So it is on hardware and that is why factory reset has to be done as it changes the way system rom acts.
Sent from my XT1033 using XDA Free mobile app
I think it is also a security measure, as unlocking the bootloader allows you to do practically everything with the phone. So you could be accessing other peoples stuff or something. But @Malyaj 's guess might be correct.
About the bootloop... You can try solving it by flashing the stock firmware again. You can also try doing the factory reset, of course. Didn't know people could choose to factory reset One Plus Ones or not... in my Moto G it just rebooted all clean.
gabriel.s said:
I think it is also a security measure, as unlocking the bootloader allows you to do practically everything with the phone. So you could be accessing other peoples stuff or something. But @Malyaj 's guess might be correct.
About the bootloop... You can try solving it by flashing the stock firmware again. You can also try doing the factory reset, of course. Didn't know people could choose to factory reset One Plus Ones or not... in my Moto G it just rebooted all clean.
Click to expand...
Click to collapse
Yeah man same with me. I also didn't knew people even had choice to do factory reset or not. Mine moto g also rebooted clean after the bootloader unlock.
Sent from my XT1033 using XDA Free mobile app

On a phone that cannot be rooted, can anything survive a factory reset?

Hey all,
On a phone that supposedly cannot be rooted, such as the Canadian LG G5 H831 model, is there any other way to access the system partition / settings on the phone, or otherwise make changes that can survive a factory reset?
I ask because I would like to perform a factory reset and would like to be certain that everything is returned to normal for security purposes.
Do you know of anything that can survive a factory reset on a phone that has a bootloader that CANNOT be unlocked/ rooted that might compromise a device even after a factory reset?
Any knowledge or advice on the topic is appreciated.
Bonus: Are there different methods to perform a factory reset that differ from each other in effect?
Thanks!!

Factory reset: Unrooting?

Just curious, since my S8+ was rooted, I decided to factory reset it since I thought it would be unrooted if I did.
Will it be unrooted?
Also please help me, I factory reset it and now it always displays Custom binary blocked by OEM Lock when booted. Full details here: https://forum.xda-developers.com/galaxy-s8+/help/factory-data-reset-custom-binary-t3813547

Oem unlock greyed out android 11 us retail

Help! I got the unlocked version and i updated it to android 11 and now oem unlock is greyed out. It says connect to internet or contact carrier and even though the internet is connected it is still greyed out someone please help me
smartasiankid said:
Help! I got the unlocked version and i updated it to android 11 and now oem unlock is greyed out. It says connect to internet or contact carrier and even though the internet is connected it is still greyed out someone please help me
Click to expand...
Click to collapse
Why is OEM Unlocking greyed out?
In theory, because you are already unlocked.
This happened to me flashing the stock 11 image over a DIY lineageos build (with the bootloader unlocked). The OEM unlock was in the "allow" position before flashing the stock image but, while running stock 11, I oberved it in the greyout "deny" position with text below it saying the the bootloader was unlocked.
After flashing lineageos, relocking my bootloader (this is a custom lineageos build that allows relocking), I could then toggle the allow OEM unlock back to the "allow" position.
Given that experience, you might be able to reboot into the bootloader, do `fastboot flashing lock` (which will wipe your data - be sure to back up before doing this), reboot and then toggle the OEM unlock to the "allow" position, and then unlock the device with `fastboot flashing unlock` (which will wipe data again). I doubt you will need any unlock code (if you have previously unlocked your device).
Note that I have NOT done this lock/OEM toggle/unlcok process with stock so proceed at your own risk.
Or you could just wait and see if moto does an update that "fixes" this behavior.
Edit: you don't say if your device was already unlocked before you updated to 11. If you never unlocked it, then just wait for a few days with your device connected to the carrier.
notmyrealhandle said:
This happened to me flashing the stock 11 image over a DIY lineageos build (with the bootloader unlocked). The OEM unlock was in the "allow" position before flashing the stock image but, while running stock 11, I oberved it in the greyout "deny" position with text below it saying the the bootloader was unlocked.
After flashing lineageos, relocking my bootloader (this is a custom lineageos build that allows relocking), I could then toggle the allow OEM unlock back to the "allow" position.
Given that experience, you might be able to reboot into the bootloader, do `fastboot flashing lock` (which will wipe your data - be sure to back up before doing this), reboot and then toggle the OEM unlock to the "allow" position, and then unlock the device with `fastboot flashing unlock` (which will wipe data again). I doubt you will need any unlock code (if you have previously unlocked your device).
Note that I have NOT done this lock/OEM toggle/unlcok process with stock so proceed at your own risk.
Or you could just wait and see if moto does an update that "fixes" this behavior.
Edit: you don't say if your device was already unlocked before you updated to 11. If you never unlocked it, then just wait for a few days with your device connected to the carrier.
Click to expand...
Click to collapse
i unlocked it on 10, got the retus 11 update, then locked it on 11. and now its greyed out
smartasiankid said:
i unlocked it on 10, got the retus 11 update, then locked it on 11. and now its greyed out
Click to expand...
Click to collapse
I'm not sure then.
If I was in your situation and I didn't mind wiping my data, I'd probably try booting into the bootloader and trying `fastboot flashing unlock` just to see what happens. If this command works, it will wipe your data so be sure about your backups. If it does unlock, you could try rebooting, check the OEM lock (I expect it will still be greyed out with an unlocked bootloader), and then relock and check again. Regardless if you can unlock inspite of the OEM toggle you shouldn't have much to worry about (at least until the next update).
If this doesn't work then I'd just wait a week or so. Alternatively, you could try the moto site, request your unlock key (again) and then wait a few days. It would be silly if this works, but maybe moto just needs to send a reminder to your device to enable the OEM unlocking toggle.
If none of this works, then I'd try posting to the moto official forums.
HTH
Never mind guys!! Just wait three maybe four days and it will automatically be toggle able again!! Thanks to all of those who tried to help me out!
Also a side note: to those of you who are looking to update to android 11, dont because you will not be able to change your preferred network type unlike on android 10 where you could.
smartasiankid said:
Also a side note: to those of you who are looking to update to android 11, dont because you will not be able to change your preferred network type unlike on android 10 where you could.
Click to expand...
Click to collapse
Click phone dialer
Dial. *#*#4636#*#*
A diagnostics menu will show
Choose phone information
Preferred network is in there
Default is the global setting
If your not sure what your doing, then don't change anything.
MrCamby said:
Click phone dialer
Dial. *#*#4636#*#*
A diagnostics menu will show
Choose phone information
Preferred network is in there
Default is the global setting
If your not sure what your doing, then don't change anything.
Click to expand...
Click to collapse
it is greyed out for me. i am on at&t network. it has been greyed out ever since android 11. not sure why that is happening.

General Pixel 6a OEM Unlocking Greyed Out STILL in August Update

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 numbers​The 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.

Categories

Resources