I mean, I'm not complaining. But I was incredibly surprised! I bought the phone BRAND NEW AND SEALED, from the current sale on woot ($170), and yet was still intending on returning it after I realized I had bought a Verizon variant, albeit carrier unlocked. Yeah, it's only the 64gb version, but I literally just bought this for testing, and as a backup. Actually bought a P3 from a friend that was in decent condition. A really close, trusted friend too, but unfortunately it just happened that about a month later the battery started exhibiting the dreaded behavior indicating it was starting to fail, so I decided to pull the trigger on the sale, not realizing it was a Verizon model. I went into much more detail about it in my post on Slickdeals: https://slickdeals.net/forums/showpost.php?p=146850461&postcount=127
It's also pink, but I'm putting on the Mint colored Spigen Neo Hybrid case on it anyway
So anyway, from all my collective knowledge about Pixels, and plenty of knowledge about (and hate towards) certain US carriers locking down devices, I wasn't expecting to be able to bootloader unlock this phone. Luckily I decided to open the box anyway and see if the OEM unlocking toggle was greyed out (which is what I fully expected!)... And it wasn't!? I still expected something, anything, to go wrong, but no, it actually successfully unlocked the bootloader (proceeded to factory reset as usual, etc)!! Unfortunately, it seems that the eSIM is still locked up and disabled, but like I said, for my usages as a simple dev'ing, testing, and/or backup phone, the eSIM isn't really important to me.
Don't think it matters, but I did this immediately upon opening the brand new phone, and it was on firmware PQ3A.190505.002 (May 2019, Pie). I mentioned it in my SD post, but the IMEI does start with 35, and checking it through Verizon's prepaid check system also indicated it as Verizon branded. I know that historically (on older Pixels, not even the 3, iirc), there was a [anecdotal] workaround where some owners would pop out the VZW SIM card before ever turning on the phone and they could then unlock the bootloader. Crazier for me is that I didn't even bother pulling out the VZW SIM card the phone came with before turning it on.
The only thing I can think, is that (and my memory here is foggy about the anecdotal posts) maybe when people were buying the phones from Verizon, those phones were actually turned on with then-active SIM cards, thus allowing them to "phone home" and permanently lock up the bootloader, at some point before ultimately shipping to the buyers. However, as these brand new Pixel 3's being sold are just leftover old, albeit brand new and factory sealed, stock, they were never turned on, whether at all or with active VZW SIM cards, at any point. When I initially turned on this new phone earlier today, since I left in the VZW SIM card included with the phone, I got a message pop up saying something along the lines of "we couldn't activate the device" or whatever.
So anyway, I wanted to say all of this because I'm always fascinated by flukes like this, where someone (me in this case!) is able to bootloader unlock a phone that should otherwise be completely unable to do so... Also attaching screenshots to show that it is indeed a Verizon branded Pixel 3 with the bootloader now unlocked. Note that it now shows current April 2021 firmware installed, but like I mentioned before it shipped with May 2019 installed from the factory, and I updated the firmware after unlocking the bootloader immediately after opening. Is there any explanation to this? Did I just get incredibly lucky? Does my theory in the previous paragraph possibly make sense? Or is there already a known explanation somehow and I just was completely unaware (and if so please let me know)?
final note: pics look like phone's screen is fuzzy because I haven't even removed the factory plastic wrap yet, lol. amazon glass screen protectors come tomorrow!
EDIT: LMAO! The listing on Woot now says in big bold letters, "The bootloader is LOCKED on these phones". Pretty sure it didn't say that when I bought it, so must be a lot of people complaining about it and trying to return! Not sure how I was able to do it though still... even if I couldn't, I would have just cited the lack of eSIM as my reason for return. Fully Unlocked != eSIM Neutered, lol.
Should I buy one to try to get an OEM unlock version?
Hey, i5lee8bit
I was poking around and saw this. I ordered one of these from the woot sale. SHould be arriving in the next day or so. Mine is the 128 GB version.
I'm down to try your process and see if I am able to have success too.
What method did you use to unlock the bootloader?
aNewHoax said:
Hey, i5lee8bit
I was poking around and saw this. I ordered one of these from the woot sale. SHould be arriving in the next day or so. Mine is the 128 GB version.
I'm down to try your process and see if I am able to have success too.
What method did you use to unlock the bootloader?
Click to expand...
Click to collapse
First of all, I would remove the SIM card before you ever turn it on, just in case. I didn't bother and it still worked, but just in case that somehow allows it to "phone home" and lock itself up.
I just did "fastboot flashing unlock" from bootloader.
Just skip through setup, connect to wifi, enable developer options, and check (hopefully) OEM unlocking toggle is not greyed out. Enable the OEM unlock toggle, reboot to bootloader. While phone is booted to bootloader, connect to PC (or another Magisk rooted Android device with adb / fastboot module installed), and use command "fastboot flashing unlock" without quotes. Should hopefully prompt you to confirm unlock bootloader / wipe data.
To reboot to bootloader, either shut off and then power on while holding volume down, or enable adb debugging and send command "adb reboot bootloader" without quotes from command line / terminal.
I saw that deal you mentioned, haha. Are you a SD user / browser? I think the deal popped up this morning or something. If it's indeed brand new and sealed, hopefully it works! Best of luck, I hope you manage to get the bl unlocked!
Thanks for the direction. Haven't done a root on a phone in a long time.
Indeed, I am a Slicker ha. Over there I am @Skullk. The name was taken here so I used an alternate. Been a long time lurker on these forums.
This was the Slickdeal https://slickdeals.net/f/14972183-google-pixel-3-128gb-not-pink-199-99-with-free-shipping-on-woot
I received the phone yesterday. Made sure no SIM installed. Battery was completely dead, that makes sense though as these are some older stock.
Hope to have some time this weekend to give it a try. I'll report back with my findings.
Cheers!
Dude! It totally worked!!
I feel like we got something here. Maybe since the phones batteries were completely dead for a while in stock? Or just starting with a fresh phone on whatever exact version these are out of stock.
Are you sure theyre not Google phones
that were jus set up with Verizon in their former lives?
aNewHoax said:
Dude! It totally worked!!
I feel like we got something here. Maybe since the phones batteries were completely dead for a while in stock? Or just starting with a fresh phone on whatever exact version these are out of stock.
Click to expand...
Click to collapse
Woohoo! Back a while ago, when I was still on AT&T, I was researching Pixel 4 series and saw that bootloader was indeed unlockable once SIM is unlocked (like Apple, SIM unlock is controlled on Google's side servers, but once whitelisted, not only unlocks the SIM but also "flags" the OEM unlock toggle to be allowed as well - unfortunately not the case for Verizon Pixels). Unfortunately I had problems with AT&T and eventually bought a factory (Google store) Pixel 4 XL and switched to Xfinity Mobile. Anyway, during all that research, I also saw that some Verizon Pixel 4 / 4 XL phones (iirc) were able to be bootloader unlocked as well. There were a few theories, one of which (again, iirc) applied to older gen Pixels - this particular one being that as long as the phones were never turned on with a Verizon SIM inserted, they could be bootloader unlocked (some theories suggesting doing factory reset gymnastics and stuff). But this didn't work for everyone (actually, it didn't work for the overwhelming majority of people - a lot of people suspecting lies / hoax / misunderstanding). But now I'm starting to think this theory may hold some water, though. Perhaps when you buy phones from Verizon, they're doing something on their end that essentially processes your account info to the IMEI of the phone you bought, somewhere in the backends of their systems. That, or maybe they're doing something with the SIM cards to set up for your account and turning on the phone once before shipping to you (I have no idea, I've never been a VZW customer). Either way, the phone's IMEI gets to "phone home" to Verizon thus locking the bootloader.
But since we're buying these old stock, never touched, never processed / activated into their system, completely factory sealed Pixel 3 / 3 XL phones that are total virgins to Verizon's systems (other than being preinstalled with a VZW SIM card), maybe that's why we can unlock the bootloaders. I don't think it has anything to do with the exact firmware versions they shipped with. I believe I remember seeing people on SD having bootloader unlocked on various firmware levels. Hard to say which thread(s), because the deal popped up so many times in the last few months, but I definitely remember seeing scattered preloaded firmware versions being bootloader unlocked.
Another theory had to do with a mistake on Google's end. Some people got lucky, some people got EXTREMELY unlucky. Some phones were manufactured and branded for the wrong carrier. For example, a phone manufactured for Tracfone ended up being locked to Verizon (not sure of the specific carriers and whether vice versa but you get the idea). But some people would get a phone that should have been bootloader locked down (OEM unlock toggle disabled) but still be able to do so. Not sure if the latter is related at all to how we're able to unlock these, but I doubt it. These were very small batches that got mixed up in manufacturing. Right now, we're seeing definitely Verizon locked phones, old stock, that all seem to be able to be bootloader unlocked. I really do suspect that there is a "phone home" process when initially setting up the phone that seals the deal with ending up with a permanently unlockable bootloader.
Now, an interesting experiment (that I wouldn't wish for anyone to try to be honest, lol) would be to have someone buy one of these old stock, brand new Pixel 3 Verizon phones, and initially turn it on WITH AN ACTIVE VZW SIM CARD INSTALLED. See if that permanently locks the bootloader. If not, maybe Verizon's side only perma-locks these phones up to a certain date (like their activation server sends some sort of command to permanently lock the bootloader, but that behavior of their activation server is only active during a certain lifespan of the device)? Either way, it would be interesting if smarter people could somehow use this information to come up with an exploit to bypass the initial bootloader locking mechanism, whatever it may be, and allow bootloader locking on future Verizon Pixel variants (though you'd likely be screwed once it's perma-locked).
On an alternate note, I absolutely hate that these carriers are screwing us, the end consumers and ultimate OWNERS of the device, for no damn legit reason. Ok, I can somewhat understand that they want to prevent modifications to the device to use their network (and by understand, I mean BARELY understand). But once the phone reaches end of life, ALLOW US TO UNLOCK THE DAMN BOOTLOADERS!! Otherwise, they should automatically chop off the sale price in half to whatever is the best current price from another vendor. F|_|CK Verizon and AT&T!
rocketrazr1999 said:
Are you sure theyre not Google phones
that were jus set up with Verizon in their former lives?
Click to expand...
Click to collapse
100% definitely Verizon branded. They're factory sealed, and come with a preinstalled Verizon SIM card. Also the IMEI starts with 35, and (unfortunately) the eSIM is locked and unusable. Like I posted in the OP, the box shows it's a Verizon locked variant.
Worked for me!
Hi, I too bought pixel 3 64gb from woot last week, I started the setup as well without taking the included sim card out. After completing setup, I can verify that OEM unlocking is not grayed out.
I am very noob to custom roms, but definitely interested in trying out the custom rom when the official support ends, Is there anything else I should do before popping in my Visible sim card in it, so that the bootloader stays unlock.
Thanks, long story short this worked for me too.
I ordered my pixel 3 from woot on june 7th when it clearly said "The bootloader is LOCKED on these phones." and got it today. I removed the sim card before turning it on, skipped most of the setup including WIFI, enabled developer options, and the "OEM unlocking" option was greyed out . Then I found a post about it needing to have internet access to enable that option - sure enough I connected to wifi and the option was live! I guess I should have mimicked your procedure exactly.
I then followed the instructions from here: https://android.gadgethacks.com/how-to/unlock-bootloader-your-pixel-3-3-xl-beginners-guide-0189128/
and the rest of the process completed successfully.
So, you did not do any special thing but just enabled Developer Options and the bootloader unlock was not grey? But mine was grey when I enabled Developer Options.
aNewHoax said:
Dude! It totally worked!!
I feel like we got something here. Maybe since the phones batteries were completely dead for a while in stock? Or just starting with a fresh phone on whatever exact version these are out of stock.
Click to expand...
Click to collapse
You also did nothing special, but just enabled Developer Options and found that the bootloader unlock was not greyed out?
yourrealking said:
So, you did not do any special thing but just enabled Developer Options and the bootloader unlock was not grey? But mine was grey when I enabled Developer Options.
Click to expand...
Click to collapse
I didn't do anything else. It was greyed out right after I enabled developer options but after I connected to WIFI for the first time and went back into that menu it was active.
yourrealking said:
You also did nothing special, but just enabled Developer Options and found that the bootloader unlock was not greyed out?
Click to expand...
Click to collapse
It's a little confusing, your question. Did you read the posts from the beginning? I mean the OP **specifies** exactly what he did... so when you say 'you did nothing special'... He says exactly what he did, would u call it 'special'?
it's impossible to answer your question, he did exactly what he said he did, what more do you want to know?
AsItLies said:
It's a little confusing, your question. Did you read the posts from the beginning? I mean the OP **specifies** exactly what he did... so when you say 'you did nothing special'... He says exactly what he did, would u call it 'special'?
it's impossible to answer your question, he did exactly what he said he did, what more do you want to know?
Click to expand...
Click to collapse
His posts are long, so I am not sure I got it correctly or not, but it seems that all he did was just enabling developer mode and ran "fastboot flashing unlock" in the bootloader mode. But that is a regular method that Google should have disallowed to work on a bootloader-locked device, so I wondered if there were some other "special" hacking-ish thing he did.
I thought I had tried that, but it was a long time ago, so just to be sure, I did that again now, and all I got was
"FAILED (remote: 'flashing unlock is not allowed')
fastboot: error: Command failed
Thanks to the OP, think I got the last one from woot. Did exactly as this post described and sure enough, oem unlock not grayed out.
It seems, as others have said, that when vzw disables oem unlock is when they 'set the phone up' for you at the store, or maybe simply when it connects to the vzw network with their sim.
I've unlocked and fb flashed to latest A11 non - verizon firmware, relocked bootloader, and am still able to unlock if I want.
Google sure does make it a lot easier to flash new firmware using fastboot. Especially compared to LG and lgup (only on windows), and patched dll's so u can crossflash, and one dll version for this, and another for that... meh.
Google even gives you an shell script that works with Linux Awesome!
i5lee8bit said:
I mean, I'm not complaining. But I was incredibly surprised! I bought the phone BRAND NEW AND SEALED...
Click to expand...
Click to collapse
Registered just to thank you for this. Bought a Pixel 3 from a B+H sale for my wife (who was really looking forward to her new phone) - we're in Canada, so thought I was screwed. Took awhile to get the USB drivers set up properly, but she's now got her new phone.
Thank you! It worked for me too for two Pixel 3 phones, one from B&H (software version PD1A.180720.031) and one from Woot (software version PQ1A.181105.017.A1). Here are the steps I followed (with android platform tools including adb and fastboot already installed):
1. Removed verizon sim card (just in case) before powering on
2. Powered on and skipped through Google setup
3. Connected to my T-Mobile tethered wifi instead of Verizon Fios home wifi (just in case)
4. Enable developer options, wait for "OEM Unlocking" to become not-greyed-out (requires wifi)
5. Enable USB debugging in developer options
6. Issue `adb reboot bootloader` from PC (or shutdown and use hardware keys)
7. Issue `fastboot flashing unlock` from PC
8. execute `flash-all.sh` from the official stock pixel 3 factory image zip from here: <https://developers.google.com/android/images#blueline>
a. This gets rid of Verizon's firmware completely
9. Wait for it to complete, reboot into bootloader
10. Issue `fastboot flashing lock` (erases user data) to re-lock bootloader
11. Booted normally and setup. OEM Unlocking is still available in developer options if I want it in the future.
johannish said:
Thank you! It worked for me too for two Pixel 3 phones, one from B&H (software version PD1A.180720.031) and one from Woot (software version PQ1A.181105.017.A1). Here are the steps I followed (with android platform tools including adb and fastboot already installed):
1. Removed verizon sim card (just in case) before powering on
2. Powered on and skipped through Google setup
3. Connected to my T-Mobile tethered wifi instead of Verizon Fios home wifi (just in case)
4. Enable developer options, wait for "OEM Unlocking" to become not-greyed-out (requires wifi)
5. Enable USB debugging in developer options
6. Issue `adb reboot bootloader` from PC (or shutdown and use hardware keys)
7. Issue `fastboot flashing unlock` from PC
8. execute `flash-all.sh` from the official stock pixel 3 factory image zip from here: <https://developers.google.com/android/images#blueline>
a. This gets rid of Verizon's firmware completely
9. Wait for it to complete, reboot into bootloader
10. Issue `fastboot flashing lock` (erases user data) to re-lock bootloader
11. Booted normally and setup. OEM Unlocking is still available in developer options if I want it in the future.
Click to expand...
Click to collapse
So we don't need to download the blueline images that say Verizon and can just use the latest 11.0.0 (RQ3A.210705.001, Jul 2021) image instead?
I haven't done this forever, is there still a need for TWRP if we are sticking with the stock rom, unlocking the bootloader and installing Magisk?
Related
Hey everyone,
I wanted to share a bit of a test that I just did on three Verizon Pixels. Specifically, when I got them from Verizon I did so via direct fulfillment (not a retail store). Doing this method I was able to boot loader unlock all three Verizon Pixels out of the box. The last one was about five minutes ago.
Here's what you'll need:
A new, in box Verizon Pixel - Important: Must be new in box!
A non-Verizon SIM card.
A Laptop
So, here's the rub. With these tests I was able to confirm that the Pixel does in fact use the SIM inserted into the phone at initial boot to determine boot loader lock ability. Long story short, if the Pixel is booted the first time with a Verizon SIM then the phone will be boot loader locked, and the OEM Unlock Toggle grayed out.
To unlock each of them I did the following:
Take the phone out of the box and inserted a co-workers AT&T SIM.
Booted the phone for the first time, and skipped all of the setup steps.
Enabled Developer Options, USB Debugging, and OEM Unlocking.
Accepted the RSA key and issues the command "adb reboot bootloader".
In bootloader mode issued the command "fastboot oem unlocking".
Flashed TWRP, and root.
Profit
The key to success here is ensuring the phone never gets booted initially with a VZW SIM inserted. This isn't so much phone hack as really a life/policy/process hack. Hope this helps!
Update: I've talked to a few knowledgeable folks on the topic who think the phones I got may have been part of a batch that wasn't loaded correctly. Having said that, Im sharing my experiences and would be curious to see what everyone else's experiences are. I'd also be curious to see the following, if anyone wants to try:
Place a non VZW SIM in the phone, factory default it, and see if its enabled again.
Take a brand new out of box VZW phone and ensure it doesn't connect to ANY network, rather it be wifi or Cell. See if OEM unlock is enabled.
Also, another added benefit is that the phones don't auto-download the few Verizon turdware apps.
Interesting...
Can confirm this works, my Google Pixel Verizon arrived yesterday as an RMA and I followed similar steps to unlock my Bootloader, although you can simply boot the phone without a SIM Card and these instructions will work the same.
deadlydecision said:
Can confirm this works, my Google Pixel Verizon arrived yesterday as an RMA and I followed similar steps to unlock my Bootloader, although you can simply boot the phone without a SIM Card and these instructions will work the same.
Click to expand...
Click to collapse
I have questions, the devil is in the details. Just trying to nail it down.
What version was it on when you got it?
Did you hook it to wifi for a few minutes and try the slider before it updated?
deadlydecision said:
Can confirm this works, my Google Pixel Verizon arrived yesterday as an RMA and I followed similar steps to unlock my Bootloader, although you can simply boot the phone without a SIM Card and these instructions will work the same.
Click to expand...
Click to collapse
Definitely did NOT work for my RMA from verizon, so this isn't a certain method.
TonikJDK said:
I have questions, the devil is in the details. Just trying to nail it down.
What version was it on when you got it?
Did you hook it to wifi for a few minutes and try the slider before it updated?
Click to expand...
Click to collapse
7.1. October version. Had to hook it up to Wi-fi to enable the OEM Unlock option, but I didn't allow the phone to update at all.
JAYNO20 said:
Definitely did NOT work for my RMA from verizon, so this isn't a certain method.
Click to expand...
Click to collapse
It was an RMA directly through Google, they just provided me with a NEW Verizon edition Pixel.
deadlydecision said:
7.1. October version. Had to hook it up to Wi-fi to enable the OEM Unlock option, but I didn't allow the phone to update at all.
It was an RMA directly through Google, they just provided me with a NEW Verizon edition Pixel.
Click to expand...
Click to collapse
I did the same thing with an RMA through Google after the Verizon one was a bust and got a BRAND NEW GOOGLE version of the Pixel so it was definitely unlockable. Are you sure your's was a Verizon version? Check your my verizon account and see if it shows it as a "NON-VZW Device." That's what mine shows as because it is actually a Google version.
deadlydecision said:
7.1. October version. Had to hook it up to Wi-fi to enable the OEM Unlock option, but I didn't allow the phone to update at all.
It was an RMA directly through Google, they just provided me with a NEW Verizon edition Pixel.
Click to expand...
Click to collapse
So it didnt get entered in the database properly as a locked phone. Or Google is so far behind they are just shipping what they can.This happens rather often and is not part of what the OP is saying.
Congrats, I am happy for you and TYVM for clearing it up.
TonikJDK said:
So it didnt get entered in the database properly as a locked phone. Or Google is so far behind they are just shipping what they can.This happens rather often and is not part of what the OP is saying.
Congrats, I am happy for you and TYVM for clearing it up.
Click to expand...
Click to collapse
What if you take a Google version, put in a VZW sim, connect, update. With it be grayed out? I doubt it.
Sent from my Pixel using XDA-Developers Legacy app
JAYNO20 said:
I did the same thing with an RMA through Google after the Verizon one was a bust and got a BRAND NEW GOOGLE version of the Pixel so it was definitely unlockable. Are you sure your's was a Verizon version? Check your my verizon account and see if it shows it as a "NON-VZW Device." That's what mine shows as because it is actually a Google version.
Click to expand...
Click to collapse
Definitely a Verizon version as it came with a pre-installed Verizon sim, which I removed before booting. Phone box also says the model is "g-2pw4100-021-b" which AFAIK is a Verizon one.
TonikJDK said:
I have questions, the devil is in the details. Just trying to nail it down.
What version was it on when you got it?
Did you hook it to wifi for a few minutes and try the slider before it updated?
Click to expand...
Click to collapse
It seems like the trick is to catch it BEFORE it ever gets Internet. When it comes online the first time it "phones home" and checks the IMEI blacklist. I think for this to work, most often, it needs to have never been connected to the Internet.
JAYNO20 said:
Definitely did NOT work for my RMA from verizon, so this isn't a certain method.
Click to expand...
Click to collapse
Had your phone by chance ever gotten connected to the Internet? As in, did you boot it with the VZW SIM?
TCPDump said:
It seems like the trick is to catch it BEFORE it ever gets Internet. When it comes online the first time it "phones home" and checks the IMEI blacklist. I think for this to work, most often, it needs to have never been connected to the Internet.
Click to expand...
Click to collapse
Its the other way around. It is grayed out until you connect and it finds out it is authorized to unlock. It isn't a blacklist, its a whitelist of sorts.
Thats why the ones you updates unlocked. It wasn't the update, it was the connection while it pulled the update. I am very sure of this. Seen a ton of VZ phones that can be unlocked the last couple of months. Their system is falling apart.
Early on we went through a ton of scenerios paying attention to when and how it became slidable.
This is the only explanation for what we have seen.
TonikJDK said:
Its the other way around. It is grayed out until you connect and it finds out it is authorized to unlock. It isn't a blacklist, its a whitelist of sorts.
Thats why the ones you updates unlocked. It wasn't the update, it was the connection while it pulled the update. I am very sure of this. Seen a ton of VZ phones that can be unlocked the last couple of months. Their system is falling apart.
Early on we went through a ton of scenerios paying attention to when and how it became slidable.
This is the only explanation for what we have seen.
Click to expand...
Click to collapse
I actually wondered if it was the fact that Google is EOLing them, and trying to eradicate their stockpile of VZW Pixels.
TCPDump said:
I actually wondered if it was the fact that Google is EOLing them, and trying to eradicate their stockpile of VZW Pixels.
Click to expand...
Click to collapse
Either way, long story short - Always check your pixel.
TCPDump said:
I actually wondered if it was the fact that Google is EOLing them, and trying to eradicate their stockpile of VZW Pixels.
Click to expand...
Click to collapse
Excellent thought. Maybe they are tired of VZ's too and are faking all these mistakes. That would be cool.
But yea, with the 2 comming this fall maybe they night be getting​ nervous.
TCPDump said:
Had your phone by chance ever gotten connected to the Internet? As in, did you boot it with the VZW SIM?
Click to expand...
Click to collapse
Nope. Pulled the Sim before boot.
I had the exact same luck.
I had to sadly RMA my perfect rooted Pixel due to charger no longer functioning fully expecting a locked bootloader and 7.1.2. Verizon sent me one overnight. It had 7.1.2 but in developer options it had the same Allow OEM Unlocking slider NOT greyed out. I was then able to adb restart bootloader and adb bootloader unlocking and the phone prompted me and that was that. Adb booted to TWRP, installed RR Rom, vendor image, magick, TWRP, root. Can not believe the incredible luck.
Also wanted to say that I used my Verizon SIM card to do this and connected to WiFi on initial setup and I STILL managed to unlock it in time before anything locked itself.
deadlydecision said:
Definitely a Verizon version as it came with a pre-installed Verizon sim, which I removed before booting. Phone box also says the model is "g-2pw4100-021-b" which AFAIK is a Verizon one.
Click to expand...
Click to collapse
What does it say on your my Verizon account?
Hi!
I originally bought an unlocked phone from Google and I had zero issues unlocking the bootloader, rooting, etc. I was issued a warranty replacement for an unrelated issue.
I inserted my VZW sim and booted up this new phone. I was able to check the OEM unlocking slider and enter my pin. When I rebooted to fastboot and tried to unlock, I was unsuccessful. Booting back into android showed the OEM unlocking option grayed out.
What gives? What can I try?
Thanks!
*Edit: Also worth noting - If I do a factory reset, the OEM unlocking option will be enabled already. If you try to unlock it in fastboot, it will fail. Rebooting again results in it being grayed out again.
What build number are you on?
DuckRuckus said:
What build number are you on?
Click to expand...
Click to collapse
I'm on OPM2.171019.029
mtpease said:
I'm on OPM2.171019.029
Click to expand...
Click to collapse
So, it came with the latest build then, or did you update via OTA?
Something to try: factory reset, turn it off, remove the SIM card, and give it another shot without connecting to wifi and skipping all the setup stuff. It's a long shot, but worth a try.
DuckRuckus said:
So, it came with the latest build then, or did you update via OTA?
Something to try: factory reset, turn it off, remove the SIM card, and give it another shot without connecting to wifi and skipping all the setup stuff. It's a long shot, but worth a try.
Click to expand...
Click to collapse
It came with something older, but it wasn't working with that either.
I tried the factory reset thing with no sim, but still on WiFi. The settings app kept crashung.
It seems like the VZW sim somehow permenantly locked my phone. I've done like 5 resets, and sometimes the OEM unlock slider is already off, sometimes it lets me toggle it back and forth. No matter what happens, after running the fastboot command (and failing), it will be grayed out. Rinse and repeat.
Have you called google with your IMEI number to confirm that it isn't a Verizon phone?
I just returned an Amazon refurbished Pixel 2 for this reason. They claimed it was factory unlocked, but I contacted Google who informed me that it was actually a Verizon phone that had probably had been unlocked for different carriers during the refurbishing process. I am exchanging it for another. They are not able to check the phone before it is delivered to me, so I am just going to hope I get a non-Verizon one this time or try the exploit mentioned on the forums immediately before connecting to WiFi or Cellular data.
mtpease said:
It came with something older, but it wasn't working with that either.
I tried the factory reset thing with no sim, but still on WiFi. The settings app kept crashung.
It seems like the VZW sim somehow permenantly locked my phone. I've done like 5 resets, and sometimes the OEM unlock slider is already off, sometimes it lets me toggle it back and forth. No matter what happens, after running the fastboot command (and failing), it will be grayed out. Rinse and repeat.
Click to expand...
Click to collapse
The only other thing I can suggest is to sideload that same build's OTA without the SIM in. That might get rid of any changes that the Verizon SIM may have made, as it will format everything before it installs. If that works, do everything you want to (root, recovery, kernel) before putting the SIM back in. That's all I can think of doing.
---------- Post added at 10:56 PM ---------- Previous post was at 10:19 PM ----------
joelphilippage said:
Have you called google with your IMEI number to confirm that it isn't a Verizon phone?
I just returned an Amazon refurbished Pixel 2 for this reason. They claimed it was factory unlocked, but I contacted Google who informed me that it was actually a Verizon phone that had probably had been unlocked for different carriers during the refurbishing process. I am exchanging it for another. They are not able to check the phone before it is delivered to me, so I am just going to hope I get a non-Verizon one this time or try the exploit mentioned on the forums immediately before connecting to WiFi or Cellular data.
Click to expand...
Click to collapse
All of Verizon's phones are carrier unlocked from the factory, and have been for quite some time. But, as far as being bl unlockable, that's a whole nother animal. Definitely good advice to check the IMEI with Google. Verizon can also do that for you, and it might be faster. I thought of that too, but it was my understanding that warranty claims we're filled with brand new units, but repairs potentially got you a refurbished one, so I ruled that out. I've been wrong before :silly:
DuckRuckus said:
The only other thing I can suggest is to sideload that same build's OTA without the SIM in. That might get rid of any changes that the Verizon SIM may have made, as it will format everything before it installs. If that works, do everything you want to (root, recovery, kernel) before putting the SIM back in. That's all I can think of doing.
---------- Post added at 10:56 PM ---------- Previous post was at 10:19 PM ----------
All of Verizon's phones are carrier unlocked from the factory, and have been for quite some time. But, as far as being bl unlockable, that's a whole nother animal. Definitely good advice to check the IMEI with Google. Verizon can also do that for you, and it might be faster. I thought of that too, but it was my understanding that warranty claims we're filled with brand new units, but repairs potentially got you a refurbished one, so I ruled that out. I've been wrong before :silly:
Click to expand...
Click to collapse
I opened a chat window with Google, and they confirmed that it is in fact an unlocked device. He also had me "screen share" so he could see the problem. So far, no resolution. I sideloaded the current OTA twice, to make sure it was in the a and b slots. Then I tried setting up the phone without a sim or wifi, which didn't work. I also tried wifi with no sim, that didn't work either.
If I try the fastboot flashing unlock command, when I boot up, the OEM unlocking option will be grayed out. Any time I boot up from a factory reset, the OEM unlocking option is already selected on.
mtpease said:
I opened a chat window with Google, and they confirmed that it is in fact an unlocked device. He also had me "screen share" so he could see the problem. So far, no resolution. I sideloaded the current OTA twice, to make sure it was in the a and b slots. Then I tried setting up the phone without a sim or wifi, which didn't work. I also tried wifi with no sim, that didn't work either.
If I try the fastboot flashing unlock command, when I boot up, the OEM unlocking option will be grayed out. Any time I boot up from a factory reset, the OEM unlocking option is already selected on.
Click to expand...
Click to collapse
First of all, could Google confirm whether your device was new, or refurbished? The second thing I would ask of Verizon is, whether the IMEI of your device has been registered to their network before you received it. I know it's a Google phone, but the previous owner, if refurbished, might have applied a VZW update from Google, rather than a global stock image or OTA, thinking that it would be a good thing. Then, realizing that they screwed up, relocked it and tried their best to return it to stock and send it back for replacement under whatever guise they chose. That's my best guess as of now.
My P2 came from VZW with the Dec patch, and the bl unlock wasn't greyed out. Didn't really matter because I could use the exploit out of the box without toggling it. But, once I unlocked it, the toggle went grey, and the phone still remains unlocked, even after the April factory image update (skipped Feb and Mar).
In summary, if your device is truly stock Google, you shouldn't be having these issues, which is a valid reason for a replacement. If it isn't, you have a valid reason for yet another replacement, refurbished or not, that IS stock Google. Press the issue...you paid a lot of money for it!
DuckRuckus said:
First of all, could Google confirm whether your device was new, or refurbished? The second thing I would ask of Verizon is, whether the IMEI of your device has been registered to their network before you received it. I know it's a Google phone, but the previous owner, if refurbished, might have applied a VZW update from Google, rather than a global stock image or OTA, thinking that it would be a good thing. Then, realizing that they screwed up, relocked it and tried their best to return it to stock and send it back for replacement under whatever guise they chose. That's my best guess as of now.
My P2 came from VZW with the Dec patch, and the bl unlock wasn't greyed out. Didn't really matter because I could use the exploit out of the box without toggling it. But, once I unlocked it, the toggle went grey, and the phone still remains unlocked, even after the April factory image update (skipped Feb and Mar).
In summary, if your device is truly stock Google, you shouldn't be having these issues, which is a valid reason for a replacement. If it isn't, you have a valid reason for yet another replacement, refurbished or not, that IS stock Google. Press the issue...you paid a lot of money for it!
Click to expand...
Click to collapse
I spoke with Verizon. The only time this phone has been used on their network is when it was activated on my account a few days ago. Google says it's unlocked. I'm still waiting for their response. My current theory is that it some how got locked when it recognized the verizon sim, but I really can be sure.
mtpease said:
I spoke with Verizon. The only time this phone has been used on their network is when it was activated on my account a few days ago. Google says it's unlocked. I'm still waiting for their response. My current theory is that it some how got locked when it recognized the verizon sim, but I really can be sure.
Click to expand...
Click to collapse
Seems like I heard in the past that even play store pixel devices had to be bootloader unlocked prior to jumping on Verizon's network as it was making devices non bootloader unlockable.
So in other words, if your phone was on the vzw network prior unlocking the bootloader regardless if it is a play store pixel, you might be hosed... rma
Having the same issue, I bought this phone and it works on ATT's network but i cannot unlock the bootloader. Kind of strange. oem unlock is greyed out. Ive reset it 10 times. trying after every update connecting to the internet and not from sept 2017 all the way to latest update. nothing changed the adb unlock command just says unable to unlock
owner232 said:
Having the same issue, I bought this phone and it works on ATT's network but i cannot unlock the bootloader. Kind of strange. oem unlock is greyed out. Ive reset it 10 times. trying after every update connecting to the internet and not from sept 2017 all the way to latest update. nothing changed the adb unlock command just says unable to unlock
Click to expand...
Click to collapse
if you are on Sep 2017 update, dont worry about OEM unlock.
Side load the jan update, and unlock the bootloader.
details here - https://forum.xda-developers.com/pixel-2/how-to/unlock-bootloader-verizon-pixel-2-t3730076
read carefully.
munchy_cool said:
if you are on Sep 2017 update, dont worry about OEM unlock.
Side load the jan update, and unlock the bootloader.
details here - https://forum.xda-developers.com/pixel-2/how-to/unlock-bootloader-verizon-pixel-2-t3730076
read carefully.
Click to expand...
Click to collapse
Unfortunately I already updated to the latest Version, I contacted the seller i got the phone from they said its a refurbished Verizon phone unlocked for any carrier and it has nothing verizon on the os.
Crap.... Can i at least get root on this thing?
giant22000 said:
Seems like I heard in the past that even play store pixel devices had to be bootloader unlocked prior to jumping on Verizon's network as it was making devices non bootloader unlockable.
So in other words, if your phone was on the vzw network prior unlocking the bootloader regardless if it is a play store pixel, you might be hosed... rma
Click to expand...
Click to collapse
That's not true.
Sent from my Pixel 2 using Tapatalk
owner232 said:
Unfortunately I already updated to the latest Version, I contacted the seller i got the phone from they said its a refurbished Verizon phone unlocked for any carrier and it has nothing verizon on the os.
Crap.... Can i at least get root on this thing?
Click to expand...
Click to collapse
nopes...nothing.
mtpease said:
I spoke with Verizon. The only time this phone has been used on their network is when it was activated on my account a few days ago. Google says it's unlocked. I'm still waiting for their response. My current theory is that it some how got locked when it recognized the verizon sim, but I really can be sure.
Click to expand...
Click to collapse
If it's a truly a Google phone, you can put any SIM in it you want to and the unlock slider will be available. Putting a Verizon SIM in it won't lock it down. I've unlocked mine and a couple others for other people. All of them had a Verizon SIM in them at the time and the unlock slider was still available. If it's a Google phone (or supposed to be) and you've already tried factory resetting it, your best bet is to RMA it. Something isn't right with it.
I have the same problem - phone unlocked but needed warranty replacement, can't unlock the warranty replacement due to exactly the same behavior where the option is greyed out, and even if I flash an image and turn the option on, I still can't do a fastboot flashing unlock and trying to do so greys out the option again.
However, I am not even on Verizon. I've tried with a T-Mobile SIM and with no SIM. So the Verizon SIM is probably not even the issue.
Google couldn't figure it out and sent me a second warranty replacement phone... which has the same issue.
Hello there. Experiencing the same issue. It's clearly a software problem. I have a Google Store, non Verizon, and I have RMA'ed it twice and both units CAN't be OEM unlocked. It's clearly a software problem because:
On factory reset OEM unlock options shows up and can be toggled
But when you go to fastboot, issuing 'fastboot flashing unlock' will return an error saying it's not allowed to be unlocked
On the next reboot OEM unlock toggle is now disabled. Only way to get it back is through factory reset with wifi connection, but that brings us back to 1 and the cycle repeats.
I guess it's pointless to RMA the device again. Reading here other people are experiencing the same problem. None of the devices have ever been on Verizon and are straight out from Google Store.
Despite it clearly being a software problem, Google is sending me a 4th phone now. It's obvious they don't know what's going on.
I know people are tired of the "Verizon users not being able to root because bootloader" threads. I myself have given up hope that I'll be able to do so with Verizon. However, I'm planning to switch to AT&T(Not specifically for rooting purposes, mostly because it's cheaper for more data and has comparable coverage to Verizon in my area) and I realized that if I switch to an AT&T SIM card, there could be a chance the bootloader is unlocked. Has anyone had any success in that area or are Verizon phones simply hard-wired with a locked bootloader even if a factory reset and different carrier SIM is installed because it's a Verizon model? I'm honestly just curious at this point, I'm not expecting success.
I'm using a unlocked Verizon pixel. Just use search terms in this device threads. Follow instructions and it worked for me. You can never go back to Verizon though a system process called Verizon services runs. Can be stopped and appears (I don't use Verizon) to effect anything. System process can be stopped, when I remember I do, runs as a background process. And never relock bootloader.
kkjb said:
I'm using a unlocked Verizon pixel. Just use search terms in this device threads. Follow instructions and it worked for me. You can never go back to Verizon though a system process called Verizon services runs. Can be stopped and appears (I don't use Verizon) to effect anything. System process can be stopped, when I remember I do, runs as a background process. And never relock bootloader.
Click to expand...
Click to collapse
Gotcha, thank you very much! I don't have very much love for Verizon so I doubt I'll want to return(And I'd probably just get a new phone if I did go back) so that's good news.
Yeah. Back on Android 7.12 (I think), Verizon rolled out an update to VZW customers that would make it impossible to unlock the bootloader, therefore impossible to root.
But if your bootloader is already unlocked, you're good to go.
I have a brand-new rooted and LineageOS modded Motorola One 5G Ace. Ever since the 3G shutoff, most of my family has been having problems with their phones - except for my son and his old Moto G4+ - his phone works perfectly. I expected the purchase of this phone, which was on the AT&T whitelist would solve the issues that I was having but that was not the case - this phone is still having the same problems. I even tried switching carriers (it would probably work if I went with AT&T directly but they're WAY too expensive) but it seems that no matter what I do, I can't call.
Now here is the interesting bit.
My carrier's access point gives me data but no phone.
Switching to any AT&T access point with the MMSC set to http://mmsc.mobile.att.net gives me phone, but no data. SMS is still available.
My carrier's tech support and I tried a lot of different things without success
Has anyone overcome this issue?
Sidenote - switching the MMSC to https://mmsc.mobile.att.net and the MMS port to 8080 works but data seems slower.
Shadeclan said:
I have a brand-new rooted and LineageOS modded Motorola One 5G Ace. Ever since the 3G shutoff, most of my family has been having problems with their phones - except for my son and his old Moto G4+ - his phone works perfectly. I expected the purchase of this phone, which was on the AT&T whitelist would solve the issues that I was having but that was not the case - this phone is still having the same problems. I even tried switching carriers (it would probably work if I went with AT&T directly but they're WAY too expensive) but it seems that no matter what I do, I can't call.
Now here is the interesting bit.
My carrier's access point gives me data but no phone.
Switching to any AT&T access point with the MMSC set to http://mmsc.mobile.att.net gives me phone, but no data. SMS is still available.
My carrier's tech support and I tried a lot of different things without success
Has anyone overcome this issue?
Sidenote - switching the MMSC to https://mmsc.mobile.att.net and the MMS port to 8080 works but data seems slower.
Click to expand...
Click to collapse
OK, so the answer seems to be the auto (PRL) selection in the "Set Preferred Network Type" list - except, on my phone, auto (PRL) doesn't show up for any entries other than GSM/WCDMA (dial *#*#4636#*#* and go to Phone Info). My son has LTE in his list. There must be a file somewhere on the phone with the preferred network types ...
you never mentioned where you got the phone (direct from att or 3rd party) or the precise model number.
was pondering getting this phone to help parents having to turn off LTE after the att 3g fiasco started, because att is their only coverage option
(stupid att refuses to enable VoLTE for many devices including their moto x4 devices, which would work fine on tmo if they had coverage, and running current LOS)
jmichael2497 said:
you never mentioned where you got the phone (direct from att or 3rd party) or the precise model number.
was pondering getting this phone to help parents having to turn off LTE after the att 3g fiasco started, because att is their only coverage option
(stupid att refuses to enable VoLTE for many devices including their moto x4 devices, which would work fine on tmo if they had coverage, and running current LOS)
Click to expand...
Click to collapse
Sorry. Phone is an XT2113-2 purchased directly from Motorola. Also, I was mistaken - the preferred network type needs to be set to "GSM/WCDMA preferred". I set the phone to what I listed above but the phone reset itself to that setting and it works. I suspect that once AT&T straightens everything out, you'll need to switch it to something else if it's not done automatically.
I found this phone at the top of the AT&T Whitelist for Motorola phones, which is one of the reasons I bought it. I refuse to get a Samsung or any other phone where the company goes out of its way to prevent people from unlocking the bootloader.
Well, I came across this little tidbit on the AT&T Community Forums.
The pertinent post is this one by Centarus3200:
Type this code into your keypad.
*#*#4636#*#*
If under "phone information", VOLTE is grayed out and you can't turn it on, ATT has blocked your phone's IMEI from being provisioned for 4G voice calls.
You can try to convince advanced tech support to provision your phone for VOLTE, but they'll either stall you out on an endless circle (Edited per community guidelines) or basically tell you to go (Edited per community guidelines) an egg (meaning buy a new phone from them).
Unnoficially, ATT will NOT provision any unlocked phone for VOLTE. Period.
Yes, even if it's on their whitelist. They just wanted to screw you into a corner first with that lie.
There are several vendors selling unlocked phones for use with their networks. If these phones are able to achieve LTE / 5G coverage, it must be due to one of the following reasons:
Best case (and unlikeliest scenario) - the IMEI of all phones sold by the carrier has been registered with AT&T and will be allowed on their network - that would allow modding of the phone since the IMEI is not changed during modding.
The "unlocked" phone has been modified somehow to AT&T specs so that it will be allowed on the network. This would mean modding the phone would get rid of the modification so a modded phone would lose coverage.
Worst case - AT&T can detect the OS fingerprint of the phone. If this changes when the bootloader is unlocked, that would mean that AT&T can detect phones with unlocked bootloaders.
Sadly, I am returning my brand new phone to Motorola - I don't have the technical savvy to deal with this. It would require some wizard over at LineageOS to overcome this hurdle.
Shadeclan said:
Phone is an XT2113-2 purchased directly from Motorola. Also, I was mistaken - the preferred network type needs to be set to "GSM/WCDMA preferred".
Click to expand...
Click to collapse
thanks for confirming.
i suspected that ATT would continue being excessively fascist, capitalist pigs, with their whitelist extortion racket of VoLTE certification fees from manufacturers...
no point in getting this 2021 bootloader unlockable device to use with LOS (since moto hasn't upgraded os from 10 for most variants) if my parents are stuck on 3.5G H+ mode anyway.
please file both an FCC and FTC complaint against ATT for their anti-consumer, anti-competitive, and anti-environment VoLTE whitelist policy hidden under the claims of "3g shutdown".
jmichael2497 said:
thanks for confirming.
i suspected that ATT would continue being excessively fascist, capitalist pigs, with their whitelist extortion racket of VoLTE certification fees from manufacturers...
no point in getting this 2021 bootloader unlockable device to use with LOS (since moto hasn't upgraded os from 10 for most variants) if my parents are stuck on 3.5G H+ mode anyway.
please file both an FCC and FTC complaint against ATT for their anti-consumer, anti-competitive, and anti-environment VoLTE whitelist policy hidden under the claims of "3g shutdown".
Click to expand...
Click to collapse
Well, I wouldn't say capitalist. Capitalists would be interested in maximizing their profits and would avoid restrictions. Monopolists and mercantilists, certainly but capitalists get a bad rap.
I won't be filing a complaint. AT&T is a merchantilist concern in cahoots with the government agencies mentioned. Anything I do will be flatly ignored. The best approach is the market approach - circumvent their restrictions and make them look foolish.
ATT is apparently doing just fine on the capitalist front, my parents are pretty ready to just give up on android and keep saying let's just buy an iphone because never had calling problems with them, so... i'm sure plenty other folks stuck with ATT are just buying off their whitelist from ATT, more profit from lack of choices.
Here is the story so far ...
3G Shutdown - Consumer Cellular is bought out by AT&T so all their phones are locked now.
Purchased a Motorola One 5G Ace from Motorola, unlocked the bootloader and installed LineageOS.
Moved my service to Pure Talk - no 4G.
Tried to go to Mint Mobile but there is no real T-Mobile coverage in my town.
Gave up and sent back the Ace to Motorola. Decided to purchase a phone directly from the provider.
Did some research and found that the only company offering Motorola phones on the AT&T network is Patriot Mobile - Purchased a Moto G Play from them. Decided not to unlock the bootloader quite yet but got the unlock key from Motorola.
There was some issues with activating the phone so I put my Pure Talk SIM in the phone and was able to access the 4G network.
Made myself a developer on the phone and tried to turn on OEM Unlocking - not able to do it.
Today, I ironed out the issues with Patriot Mobile activated the service and put my Patriot Mobile SIM card in. Now I can turn on OEM Unlocking.
Observations: It appears that the provider SIM card is able to control whether or not OEM Unlocking can be turned on. It also appears that the provider SIM card can detect if OEM Unlocking is on or off and either send that info to the provider, limit band access or, possibly, penalize the user in other ways.
What to Do: I plan on leaving the OEM Unlocking switch in the ON position for a week and monitor for 4G coverage. If everything looks good, I will then unlock the bootloader and wait for another week. If that goes well, I will purchase another 5G Ace and see how that goes.
Shadeclan said:
Here is the story so far ...
3G Shutdown - Consumer Cellular is bought out by AT&T so all their phones are locked now.
Purchased a Motorola One 5G Ace from Motorola, unlocked the bootloader and installed LineageOS.
Moved my service to Pure Talk - no 4G.
Tried to go to Mint Mobile but there is no real T-Mobile coverage in my town.
Gave up and sent back the Ace to Motorola. Decided to purchase a phone directly from the provider.
Did some research and found that the only company offering Motorola phones on the AT&T network is Patriot Mobile - Purchased a Moto G Play from them. Decided not to unlock the bootloader quite yet but got the unlock key from Motorola.
There was some issues with activating the phone so I put my Pure Talk SIM in the phone and was able to access the 4G network.
Made myself a developer on the phone and tried to turn on OEM Unlocking - not able to do it.
Today, I ironed out the issues with Patriot Mobile activated the service and put my Patriot Mobile SIM card in. Now I can turn on OEM Unlocking.
Observations: It appears that the provider SIM card is able to control whether or not OEM Unlocking can be turned on. It also appears that the provider SIM card can detect if OEM Unlocking is on or off and either send that info to the provider, limit band access or, possibly, penalize the user in other ways.
What to Do: I plan on leaving the OEM Unlocking switch in the ON position for a week and monitor for 4G coverage. If everything looks good, I will then unlock the bootloader and wait for another week. If that goes well, I will purchase another 5G Ace and see how that goes.
Click to expand...
Click to collapse
I unlocked the bootloader without loss of service today. I'll be reordering my Moto One 5G Ace today along with a phone for my daughter. Looks like Patriot Mobile is going to let people on the AT&T network with unlocked phones. I sent an email to the company CEO and thanked him.
Shadeclan said:
I unlocked the bootloader without loss of service today. I'll be reordering my Moto One 5G Ace today along with a phone for my daughter. Looks like Patriot Mobile is going to let people on the AT&T network with unlocked phones. I sent an email to the company CEO and thanked him.
Click to expand...
Click to collapse
Downloaded the recovery files today with the Motorola recovery tool and tried using Magisk to modify the boot image - it failed. I may try to load Magisk from recovery. There is no "official" TWRP recovery but both /e/ foundation and LineageOS have their own recoveries that can be flashed or run from fastboot.
Update 20220614 15:01 EST: I successfully rooted the phone through /e/ foundation recovery using Magisk 25.0. TopJohnWu has rewritten the whole thing V25 is currently in beta but I read through the notes and I felt more confident with this version. After root, I was able to get 5G data and send and receive phone calls just fine. Next step is to load /e/ ROM onto the phone. I am confident that I can recover using the Motorola recovery tool if things go south.
The TWRP on the Telegram channel works. I am using it.
RETIEF said:
The TWRP on the Telegram channel works. I am using it.
Click to expand...
Click to collapse
Were you able to load it under a custom ROM? That was my issue - couldn't get TWRP to load regardless of whether I had flashed it to recovery or booted into it via fastboot.
Shadeclan said:
Were you able to load it under a custom ROM? That was my issue - couldn't get TWRP to load regardless of whether I had flashed it to recovery or booted into it via fastboot.
Click to expand...
Click to collapse
I flashed it with fastboot to recovery_a and recovery_b. I then rebooted to system, then turned the phone off, rebooted to fastboot, selected recovery and it booted.
RETIEF said:
I flashed it with fastboot to recovery_a and recovery_b. I then rebooted to system, then turned the phone off, rebooted to fastboot, selected recovery and it booted.
Click to expand...
Click to collapse
Is this the syntax? fastboot flash recovery_a twrp.img ?
Shadeclan said:
Is this the syntax? fastboot flash recovery_a twrp.img ?
Click to expand...
Click to collapse
Yes. Assuming you have renamed the downloaded file "twrp.img".
RETIEF said:
Yes. Assuming you have renamed the downloaded file "twrp.img".
Click to expand...
Click to collapse
A link to the TWRP you are using? I do believe there's a beta version somewhere here on the forum ... Aaah. It's for the kiev -3. I have a XT2113-2 - probably explains why it won't work on my phone.
Shadeclan said:
A link to the TWRP you are using? I do believe there's a beta version somewhere here on the forum ... Aaah. It's for the kiev -3. I have a XT2113-2 - probably explains why it won't work on my phone.
Click to expand...
Click to collapse
kiev-twrp-3.6.0_11.0_RC-1.4.img | by SyberHexen for Moto One 5g Ace
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I have the Xt2113-2.
I have successfully installed /e/ foundation ROM on my Moto
RETIEF said:
I have the Xt2113-2.
Click to expand...
Click to collapse
I will grab it right away - many thanks.
So, I purchased the A32 5g version a little over a year ago and when I came to xda to find the method to root, I found out the bad news. But read in one of the threads that if your sitting on build 1,2 or 3 to not update because there was a possible method to unlock the bootloader coming soon and taking the updates would make it harder/impossible to unlock the bootloader. So I have been sitting on the build that came with my phone when they handed it to me which is RP1A.200720.012.A326U1UEU3AUH1.
I have been ignoring the update notifications for a year in hopes of a *free* method to be released to no avail.... I think... Right?
Also The old update notifications I would get were easy to ignore and swipe away from the notification swipe down menu and I wouldn't see them again for another week or two. But now just in the past few days for some strange reason the update notifications are different and more annoying. Whenever I restart my phone and unlock it for the first time after restart I always get a whole window notification that takes up my whole screen asking me to update so I always click "later". And it's also permanently in my notification swipe down menu now, I can't swipe it away or turn the notis off. And they've also pinned a huge banner at the top of my main settings menu that says "A software update is available" with an accept button right below it.
So, a couple questions:
If I haven't taken any updates how did my carrier change all of these update notifications and pin one to the top of my settings menu that was never there before? Are they able to do that without me taking an update? It's almost like they're trying to put it everywhere on my phone in hopes that there's more of a chance of me accidentally accepting it. Also, I believe that eventually I will accidentally hit accept on one of these constant notifications and I've waited so long for a *free* method to unlock the bootloader that hasn't come yet, should I just update and get it over with? Or is there a *free* method somewhere or word of one coming?
I also have a couple off topic questions about my carrier. So I believe my build # is the Verizon version of the A32 but my actual cell company is cellcom (American cellcom) and cellcom uses Verizon's network. So why does my carrier use Verizon software and the Verizon network? Why doesn't Verizon just open up shop where I live?
All the previous phones I've gotten from cellcom have always been pretty easy to root and they've always been carrier unlocked. Not sure why but they have been. That is until I made the mistake of getting this phone without doing any research on whether or not it was rootable.
Sorry for the long, all over the place post but If anyone could answer my few questions, it'd be greatly appreciated! Because at this point I'm thinking of just pulling the trigger on the updates if there's no way to unlock the bootloader without paying for a token.
Mine is bootloader version 8 so it can't be rooted; but yours is below 6 so this thread says it can be rooted. Please check it out & let the rest of us know how it works out for you if you try those rooting methods.
How to ROOT A32 5G