Related
I've recieved my second MotoG 3rd gen today. Both stock, untouched. When booting to fastboot mode I've noticed that it shows 'Device is ENGINEERING' and 'Software status: Modified'
We've got a similar device for my wife so I can compare the two. This one shows 'Device is LOCKED. status code 0' and ' Software status: Official.'
The device with status Engineering does not respond to adb or fastboot commands and is not recognised in windows device manager or the Motorola device manager.
Made a call to customer support where I bought the device and I expect they will just swap it.
Still, out of curiosity, tried to google the problem but not much shows up, except a few Motorola Nexus devices that show a similar status. Does anyone know the exact meaning of 'Device is ENGINEERING'?
That's the same thing as Service Mode. Every phone has it and you normally enter into it by a series of numbers on the dial pad. There are also apps that do it. I wouldn't have a clue why yours is showing that in the bootloader unless some Moto tech left it there after testing. I would think there's a fastboot entry to stop it. I also wonder if you could go in and out of service mode after booting.
Enable USB Debugging
Open your dialer
Enter *#*#2486#*#*
There's a factory setting on the bottom checked as default.
Do I need to uncheck that radio button? There is not much I can do in that service menu. Tried to change between factory and alt but that did not change the status back to normal.
gais said:
Do I need to uncheck that radio button? There is not much I can do in that service menu. Tried to change between factory and alt but that did not change the status back to normal.
Click to expand...
Click to collapse
I don't know about that. I'd wait and see if Motorola gets back to you. You could try posing a question in the Motorola Owners Forum at https://forums.motorola.com/hives/08e565d7be/summary Log in with your Google ID if you haven't been there before.
i also have a phone that says engineering in fastboot mode and was wondering what it meant. its a xt1550 asia model.
my phone has a lot of extra apps however bug2go battery tracer desense tester cdbench iplog tool just to name a few. should i leave the phone as is or is it possible to flash a US retail.? any comments are welcome
So I picked up a Virgin Moto G3, and I wanted to wipe everything, unlock, and flash a custom ROM, I've done this to other Moto G3s in the past, so I didn't think I was in for a tough feat, except I cannot get past this dumb activation screen.
However, I can get past the activation screen by hitting the Emergency Call button -> Recent Apps -> Tapping the Google Search bar -> Entering into settings -> Trying to do an Allow OEM Unlock, however it is nowhere to be found in Developer Options.
I have enabled USB Debugging, but I do not know what to do from here. Is there any such adb command that can toggle OEM unlock from inside the stock ROM? The Activation will not go away, the device has been on for an hour and it's not going anywhere, even though I have full service.
If anyone can help me on this crappy journey, it would be much appreciated, I'm stuck between a rock and a hard place right now.
Could not post an image here, but here is a similar link:
image.prntscr(dot)com/image/9eac693d4bff4e89a9d51b668f6131fa.png
bump, hopefully by the grace of god, someone can figure this crap out.
slutexpress said:
bump, hopefully by the grace of god, someone can figure this crap out.
Click to expand...
Click to collapse
What exactly is the problem with the activation screen??
You can do a factory reset using ADB and then try to start your phone again. Maybe that'll get you past the activation and wherever you're stuck.
slutexpress said:
So I picked up a Virgin Moto G3, and I wanted to wipe everything, unlock, and flash a custom ROM, I've done this to other Moto G3s in the past, so I didn't think I was in for a tough feat, except I cannot get past this dumb activation screen.
However, I can get past the activation screen by hitting the Emergency Call button -> Recent Apps -> Tapping the Google Search bar -> Entering into settings -> Trying to do an Allow OEM Unlock, however it is nowhere to be found in Developer Options.
I have enabled USB Debugging, but I do not know what to do from here. Is there any such adb command that can toggle OEM unlock from inside the stock ROM? The Activation will not go away, the device has been on for an hour and it's not going anywhere, even though I have full service.
If anyone can help me on this crappy journey, it would be much appreciated, I'm stuck between a rock and a hard place right now.
Could not post an image here, but here is a similar link:
image.prntscr(dot)com/image/9eac693d4bff4e89a9d51b668f6131fa.png
Click to expand...
Click to collapse
You'll need minimal adb & fastboot on your PC and the USB Drivers for Motorola devices (Motorola Device Manager is preferred). Boot your G3 into fastboot mode, connect to PC with micro USB sync cable. Open a command prompt in your adb/fastboot directory. Type: fastboot erase carrier
That will kill the activation screen
Hello there and thank you for your patience, I had previously considered myself smart until yesterday. You see I'm new to all this, just a bb, but I find it fascinating.
So I sold my phone pixel 3 to someone who want to have lineageOS on google Fi and wants to make sure the OEM is unlocked. Phone has sim card slot
Not knowing anything I looked it up completed the steps to get developer options, OEM greyed out, ok so I proceed to look up articles and videos, finally found what seems to be a legit solution here
https://forum.xda-developers.com/pi...izon-pixel-t3796030/post83674835#post83674835
after downloading more software than I needed and making several attempts to access the adb command prompt on my macbook pro, I decided to borrow my friends pc to try and do it
Downloaded https://developer.android.com/studio/releases/platform-tools platform tools, unzipped, shift right click in folder, no command window option
I decided to after following the instructions on the phone, just hit the up volume key and power to turn it on, it says "no command" I'm guessing because I dont have the window up and cant seem to figure out how to get it up
Now I'm. back on my macbook pro and I'd like someone to please help me, preferably on macOS but I'll take any help I can and go back to my friends broken pc if I have to (touch screen broken and keyboard doesnt work, I got a keyboard, but the broken touch screen goes crazy and it's really frustrating.
Anyway sincere gratitude to anyone who can help me as I am desperate
Update: went back to pc unzipped platform tools, shift right clicked and there was an option for powershell window, however it did not recognize any adb commands :/
Nadia927 said:
Hello there and thank you for your patience, I had previously considered myself smart until yesterday. You see I'm new to all this, just a bb, but I find it fascinating.
So I sold my phone pixel 3 to someone who want to have lineageOS on google Fi and wants to make sure the OEM is unlocked. Phone has sim card slot
Not knowing anything I looked it up completed the steps to get developer options, OEM greyed out, ok so I proceed to look up articles and videos, finally found what seems to be a legit solution here
https://forum.xda-developers.com/pi...izon-pixel-t3796030/post83674835#post83674835
after downloading more software than I needed and making several attempts to access the adb command prompt on my macbook pro, I decided to borrow my friends pc to try and do it
Downloaded https://developer.android.com/studio/releases/platform-tools platform tools, unzipped, shift right click in folder, no command window option
I decided to after following the instructions on the phone, just hit the up volume key and power to turn it on, it says "no command" I'm guessing because I dont have the window up and cant seem to figure out how to get it up
Now I'm. back on my macbook pro and I'd like someone to please help me, preferably on macOS but I'll take any help I can and go back to my friends broken pc if I have to (touch screen broken and keyboard doesnt work, I got a keyboard, but the broken touch screen goes crazy and it's really frustrating.
Anyway sincere gratitude to anyone who can help me as I am desperate
Update: went back to pc unzipped platform tools, shift right clicked and there was an option for powershell window, however it did not recognize any adb commands :/
Click to expand...
Click to collapse
I know nothing about macbooks, but according to this article you have to change some system settings to open a terminal window.
https://www.groovypost.com/howto/op...nal-window-specific-folder-windows-mac-linux/
Can you open a terminal window in any folder? If so, just do a cd command to the platform-tools directory.
Regarding your powershell window, it sounds like you are not in the platform-tools directory. Do a dir command. Do you see the adb file? If so, try ./adb. If not, do a cd to the platform-tools directory.
Do you have a Verizon branded phone? If so, you probably cannot unlock the bootloader. The link you pointed to is for a Pixel, not a Pixel 3.
If your OEM button is grayed out you are done, you can't unlock that phone.
Hi All,
Apologies, this is my first post, I cracked something trivial, but didn't find the steps or the same situation anywhere, so posting my version of events. This guide is based on the following situation
Bought a Google Pixel 3 XL - CARRIER LOCKED phone off ebay (Locked to EE)
- Running Android 10 - working fine - pre wiped
- EE SIM installed
- Wifi Connected
- Based in the UK
- I need to root this phone to perform security testing
So, for me, because the phone is locked to EE, when I did tried to enable OEM unlocking in dev options, I got the dreaded OEM unlocking unavailable on carrier locked devices.....:
Details:
Enable DEVELOPER MODE
SETTINGS > ABOUT PHONE > Hit “Build Number“ 7 times > Enter your pin/pattern
Go To Enable OEM Unlocking
SETTINGS > SYETEM > ADVANCED > DEVELOPER OPTIONS > OEM UNLOCKING option
However,
You end up with “OEM unlocking unavailable on carrier locked devices” and the option greyed out and disabled (Silent sobbing in the corner by my wallet)(See attached my mocked up screen shot of this)OEM unlocking is step 2 of every rooting tutorial I’ve seen (the 1st being DEV OPTIONS!) (Silent sobbing in the corner by me!)
Reading many forums, all hope was lost, lots about Verizon phones, and specific IMIE numbers called out for versions to watch out for, blah blah until a passing comment about getting the Carrier (EE) to unlock.
EE do this for FREE if YOU bought the phone from THEM….or they charge £8.99 for 2nd hand phone unlocks
1) So, call EE on 150 (UK)
2) Give them the IMIE number of the phone
SETTINGS > ABOUT PHONE > IMEI number
3) They fill out a form and send to their back office “unlock team”
4a) Short Story – I called back and was advised to update my phone...the end
4b) Long Story - I was told this would take 24 hrs, and they would send me an email with instructions…this never arrived, so I called back, only to be told there was a back log and it would take 1-10 days!! 5 days later, no email, no codes, no love! so I called back begging for an escalation, I was told there was a note on the account saying it was done! and the phone just needed an update….(no code, no email, no call, if I was waiting at a restaurant for you EE, I'd of left!)
5) Next update Android to the very latest version
SETTINGS > SYSTEM > ADVANCED > SYSTEM UPDATES6) Wait the age for it to install and “optimize” the apps
7) I checked for more updates, found “A security patch”, went through the process again….7 more times! (took me a couple hours!)….I repeated this process until there were no more updates to collect (back to step 5 you go!)
8) Check:
SETTINGS > SYETEM > ADVANCED > DEVELOPER OPTIONS > OEM UNLOCKING option = still locked for me at this point.
9) Perform a FACTORY RESET
SETTINGS > SYSTEM > RESET OPTIONS > DELETE ALL DATA (FACTORY RESET)10) Let it Reboot
11) Re-set up
Enable DEVELOPER MODE...againSETTINGS > ABOUT PHONE > Hit “Build Number“ 7 times > Enter your pin/patternGo To Enable OEM Unlocking...againSETTINGS > SYETEM > ADVANCED > DEVELOPER OPTIONS > OEM UNLOCKING option
BOOM! OEM unlocked! (for me at least)
Long oand short of it - get EE to unlock and confirm > update the [email protected] out of the phone > perform factory reset
I hope these saves time for someone out there
D2
Hi, I bought a refurbished Pixel 3. I tried to unlock bootloader by: starting the device, skipping all set-up, enabling developer options, trying to enable "OEM unlocking". But it is greyed out with message "Connect to the Internet or contact your operator".
Then I tried to connect to wifi, still same message. Then I inserted a SIM card, still same message. I also rebooted a couple times, still nothing. Doing "adb reboot bootloader" shows that the bootloader is locked.
So what does this mean? I looked up online that some phones are from Verizon so they will not be able to be unlocked. Is this the case? How can I check this? If the bootloader is not unlockable I'm just going to return it x) which will be a pain in the a** since I'll have to pay return shipping and everything.
Thanks for any help!!
andrepd said:
Hi, I bought a refurbished Pixel 3. I tried to unlock bootloader by: starting the device, skipping all set-up, enabling developer options, trying to enable "OEM unlocking". But it is greyed out with message "Connect to the Internet or contact your operator".
Then I tried to connect to wifi, still same message. Then I inserted a SIM card, still same message. I also rebooted a couple times, still nothing. Doing "adb reboot bootloader" shows that the bootloader is locked.
So what does this mean? I looked up online that some phones are from Verizon so they will not be able to be unlocked. Is this the case? How can I check this? If the bootloader is not unlockable I'm just going to return it x) which will be a pain in the a** since I'll have to pay return shipping and everything.
Thanks for any help!!
Click to expand...
Click to collapse
The IMEI will tell you if it is a Verizon phone. I believe Verizon IMEIs begin with 35. Google "IMEI lookup" and you'll find plenty of sites that will give you information on that phone.
dcarvil said:
The IMEI will tell you if it is a Verizon phone. I believe Verizon IMEIs begin with 35. Google "IMEI lookup" and you'll find plenty of sites that will give you information on that phone.
Click to expand...
Click to collapse
Thanks, I tried that, it is indeed a Verizon model. Do you know if there is any way around this to unlock the bootloader? I guess I'll have to google around a bit to figure out if it's hopeless or not x)
There is no way to unlock a Verizon phone.
Hmm well I'm getting quite mixed signals here:
- imei.info says "Pixel 3 128GB, US VZ, Just Black"
however:
- ro.oem_unlock_supported is 1
- and bootloader screen says "Product revision: MP1.0(ROW)", not "(VZW)"
- box says "ESIM" rather than "SIM"
and also in some threads users report being able to unlock verizon phones... So it's all very strange x)
Pretty much same here. Did you figure out something?
me too
Ok, so a brief update here, the results of my search over the last couple of days:
Most likely, your Pixel 3 cannot be unlocked, it has been locked by Verizon when activated on their network and we don't have a way to undo this OEM lock. If you bought it re-furbished or second hand, and OEM Unlocking is grayed out, the most likely is that there is nothing to do.
Relevant / connected threads:
- https://forum.xda-developers.com/t/oem-unlocking-grayed-out.3860023/page-21
- It can be unlocked before it has activated on verizon: https://forum.xda-developers.com/t/...branded-pixel-3-how-is-this-possible.4267273/
- Some (unsuccessful) attempts are discussed at https://forum.xda-developers.com/t/bounty-unlock-bootloader-vzw-pixel-3-xl.3856605/page-113 and
Use 'fastboot oem citadel' to unlock bootloader? (Verizon Pixel 3)
I unfortunately have a Pixel 3, from Verizon (when I bought it it was not described as a phone issued by Verizon had I known it I wouldn't have bought it). I'm trying to accomplish The impossible by finding some way to unlock the bootloader...
forum.xda-developers.com
- This post pretends that it can be undone, but this has not been confirmed / applies only to very speecific cases:
https://www.reddit.com/r/GooglePixel/comments/sc2w1r
- https://support.google.com/pixelpho...ixel-3-verizon-flashed-3xl-system-image?hl=en
-
https://www.reddit.com/r/GooglePixel/comments/rsrnu0
Last month, I decided that I wanted to try rooting my Samsung galaxy s21 + 5g (model name SM-g996u), and I got as far as unlocking the network before I hit a snag. In all of the tutorials I have looked at concerning how to root my device, they all keep saying that I need to OEM Unlock my phone under the developer settings. However, as the title of this post would indicate, that setting is not present in the development settings. I have just about lost my damn mind trying to find and enable this setting via online tutorials, and I keep coming across the same suggestions: configure date/time setting so that it is not automatically set, manually set the date back a couple of months, go to dev settings and disable auto-update system setting, disable 'Download updates automatically' setting in software update (this is the only step I was not able to follow because that setting appears to have been removed from more updated version), and restart the device. I even tried removing my sim card, resetting my phone, and retrying the previously outlined steps. Nothing has worked. Is there anyone out there that can help me with this? Any info would be great.
Is device leased from a carrier, e.g Verizon? AFAIK by default this phone has OEM Unlock option in Android's Developer Options.
[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com
whiggs2 said:
Last month, I decided that I wanted to try rooting my Samsung galaxy s21 + 5g (model name SM-g996u), and I got as far as unlocking the network before I hit a snag. In all of the tutorials I have looked at concerning how to root my device, they all keep saying that I need to OEM Unlock my phone under the developer settings. However, as the title of this post would indicate, that setting is not present in the development settings. I have just about lost my damn mind trying to find and enable this setting via online tutorials, and I keep coming across the same suggestions: configure date/time setting so that it is not automatically set, manually set the date back a couple of months, go to dev settings and disable auto-update system setting, disable 'Download updates automatically' setting in software update (this is the only step I was not able to follow because that setting appears to have been removed from more updated version), and restart the device. I even tried removing my sim card, resetting my phone, and retrying the previously outlined steps. Nothing has worked. Is there anyone out there that can help me with this? Any info would be great.
Click to expand...
Click to collapse
This device(all of the US models) doesn't have the OEM unlock option. As far as I know, these devices have to be unlocked via a paid service from a 3rd party.
jwoegerbauer said:
Is device leased from a carrier, e.g Verizon? AFAIK by default this phone has OEM Unlock option in Android's Developer Options.
Click to expand...
Click to collapse
Device has been paid off. It is also network unlocked as well. The device was originally leased from Tmobile. I am aware that the setting is supposed to be in developer settings. I am telling you, it is not showing up for me.
whiggs2 said:
Device has been paid off. It is also network unlocked as well. The device was originally leased from Tmobile. I am aware that the setting is supposed to be in developer settings. I am telling you, it is not showing up for me.
Click to expand...
Click to collapse
May I'm wrong but the fact that the client have covered the contract, doesn't mean that the carrier do that, if a special petition was not presented to them, then, they don't care about. If the device came with a firmware that came with that feature disabled, so it, also, ends its "normal" life with the same featured included (or not) in the firmware by default.
But you could make advantage from the network unlocked condition, switching to a different firmware it would be possible, and, the option may appear.
SubwayChamp said:
May I'm wrong but the fact that the client have covered the contract, doesn't mean that the carrier do that, if a special petition was not presented to them, then, they don't care about. If the device came with a firmware that came with that feature disabled, so it, also, ends its "normal" life with the same featured included (or not) in the firmware by default.
But you could make advantage from the network unlocked condition, switching to a different firmware it would be possible, and, the option may appear.
Click to expand...
Click to collapse
I have seen that suggestion mentioned before online, though I have not really found any good tutorials on how to go about doing that. Any suggestions?
Droidriven said:
This device(all of the US models) doesn't have the OEM unlock option. As far as I know, these devices have to be unlocked via a paid service from a 3rd party.
Click to expand...
Click to collapse
This - The 'U' devices do not have OEM unlock by default.
whiggs2 said:
I have seen that suggestion mentioned before online, though I have not really found any good tutorials on how to go about doing that. Any suggestions?
Click to expand...
Click to collapse
This may be just a kind of starting point, to have in mind, but that need more research though, I did it in my GN8 but with your device, things may be different.
There are some things you have to check, in the download screen, KG has to be completed, not prenormal or checking, also search for the CSCs that are compatible for your device, this is one of the tutorial, kind of, that I followed https://www.getdroidtips.com/guide-...ocked-firmware-galaxy-note-8-sm-n950u-n950u1/