First of all this is my first attempt at rooting/reviving a Google phone. Although I have 10 +years of building computers etc. under my belt and I have owned multiple android devices since G1 launch so this should not be to hard to understand.
With that said. Here is my situation and as much knowledge as I have on how it arrived at the current state.
A friend of mine bought this Nexus on craigslist. It worked for a week or so, then would not boot up past boot screen icon (no lock on boot screen). I took it off his hands for $50.
Now I am able to get the phone in to the fastboot screen (when plugged in it reads 'fastboot usb'). I was also able to get into the the factory data reset screen. No matter the option I selected or cleared out it always returns me to the same frozen boot up image.
I downloaded SDK, superboot, drivers are installed (and updated ) and I have followed to the T all forum post on how to unlock the bootloader.
Everything goes great until... I get to this hiccup!! I am able to connect the device to and get a response with device pin number in command screen.
Then I type in 'fastboot oem unlock' and it gives me this terrific message:
... INFO[ERR] partition_read: :Failed to read page 261120 or it is em
INFOpty
INFO[DISPLAY_ERR] sp_custom partition: sp_custom_img_hd read err
INFOor!
INFO[DISPLAY_ERR] Can not load custom splash!
INFOLoading custom splash failed!
OKAY
What next????
I have also noticed that i get an interesting message when I first select bootloader on device, just for a second then returns to normal (pictures attached of this!)
One step I am unable to do that I believe may be the problem, since I have never been able to get past bootscreen on the device I have not been able to select the USB DEBUGGING option. Is there anyway around this?
If anyone is able to walk me through getting past this point and running vanilla 2.1 (I can take it from there ) I will donate $25 to this site as well as paypal you personally $25.. or you can have the entire $50 donated to the site
Thanks in advance for reading this post and helping a fellow Android lover!
Fix your Phone
I do not know if you will be able to fix it yourself but if you want you can contact google, send it in to them, and they will probably replace the phone for you. Assuming it has the standard 1 year warranty, you would be elligible for repairs and possibly google completely replacing your phone, giving you a new one. My G1 had problems and i tried fixing it myself with all kinds of stuff but eventually i contacted google and after i mailed it in they send me a new unit.
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
Hey, I unwittingly bought a device owned by Google on eBay. The IMEI is clean everywhere I can check it but when trying to complete phone setup, a message pops up stating that the device is fully managed by Google LLC. Seller stated that it needed "flashed" to a non-work rom. Since I have done a fair amount of flashing I figured I could work it out. No go, after factory reset and signing into wifi, it connects to the space ship and says it will automatically reset in 1 hour.
I have contacted google tech support (they always wonder where I got their internal number, it is listed on the setup screen) and Pixel support. Pixel support was about to warranty the device but then saw that the IMEI is reported "lost" in one of their systems. Of course VZW and swappa show it clean. Google techstop support recognizes the device as theirs and generated a ticket but I have not heard anything back.
1) any suggestions on how to move forward with this very obviously stolen device (clean IMEI)
2) suggestions on how to avoid this in the future - I thought clean IMEI is all I had to worry about apparently fully managed devices are now a new element.
isaacws said:
Hey, I unwittingly bought a device owned by Google on eBay. The IMEI is clean everywhere I can check it but when trying to complete phone setup, a message pops up stating that the device is fully managed by Google LLC. Seller stated that it needed "flashed" to a non-work rom. Since I have done a fair amount of flashing I figured I could work it out. No go, after factory reset and signing into wifi, it connects to the space ship and says it will automatically reset in 1 hour.
I have contacted google tech support (they always wonder where I got their internal number, it is listed on the setup screen) and Pixel support. Pixel support was about to warranty the device but then saw that the IMEI is reported "lost" in one of their systems. Of course VZW and swappa show it clean. Google techstop support recognizes the device as theirs and generated a ticket but I have not heard anything back.
1) any suggestions on how to move forward with this very obviously stolen device (clean IMEI)
2) suggestions on how to avoid this in the future - I thought clean IMEI is all I had to worry about apparently fully managed devices are now a new element.
Click to expand...
Click to collapse
Interesting problem! Can you bypass wifi setup and get into settings? If so can you enable developer options and enable oem unlock. And flash a factory image. Or can you get into recovery and sideload the ota? I'm guessing not but worth a try.
jd1639 said:
Interesting problem! Can you bypass wifi setup and get into settings? If so can you enable developer options and enable oem unlock. And flash a factory image. Or can you get into recovery and sideload the ota? I'm guessing not but worth a try.
Click to expand...
Click to collapse
I can bypass wifi setup and get into settings. I have actually been able to get in, bypass settings and then add my gmail account. Once I connect to wifi, within seconds, it pops up with the google fully managed device so the adding account was a trick. I doubt it is a custom Rom. I think it is part of the new provisioning api that google has for Corporate control on devices, probably tied to IMEI.
I am guessing a custom rom might not get the managed alert but I really have enjoyed the last several years of not constantly tweaking my phone.
jd1639 said:
Interesting problem! Can you bypass wifi setup and get into settings? If so can you enable developer options and enable oem unlock. And flash a factory image. Or can you get into recovery and sideload the ota? I'm guessing not but worth a try.
Click to expand...
Click to collapse
OEM Unlocking is grayed out. I think it is a vzw pixel from what the IMEI shows.
isaacws said:
OEM Unlocking is grayed out. I think it is a vzw pixel from what the IMEI shows.
Click to expand...
Click to collapse
It also is on the latest build already PQ2A.190205.001, Feb 2019. I think this is an ET phone home "feature"
isaacws said:
I can bypass wifi setup and get into settings. I have actually been able to get in, bypass settings and then add my gmail account. Once I connect to wifi, within seconds, it pops up with the google fully managed device so the adding account was a trick. I doubt it is a custom Rom. I think it is part of the new provisioning api that google has for Corporate control on devices, probably tied to IMEI.
I am guessing a custom rom might not get the managed alert but I really have enjoyed the last several years of not constantly tweaking my phone.
Click to expand...
Click to collapse
I'm still not seeing an answer to JD's question. Can you unlock your BL, and if so load the factory image? You should be able to do this all without ever adding your G acct or connecting. Then, when you add it (after running with the -w in place for a full factory reset), maybe it will not pop up the managed notification.
---------- Post added at 03:40 PM ---------- Previous post was at 03:39 PM ----------
sliding_billy said:
I'm still not seeing an answer to JD's question. Can you unlock your BL, and if so load the factory image? You should be able to do this all without ever adding your G acct or connecting. Then, when you add it (after running with the -w in place for a full factory reset), maybe it will not pop up the managed notification.
Click to expand...
Click to collapse
Just saw your replies as I sent this...
---------- Post added at 03:41 PM ---------- Previous post was at 03:40 PM ----------
isaacws said:
It also is on the latest build already PQ2A.190205.001, Feb 2019. I think this is an ET phone home "feature"
Click to expand...
Click to collapse
Perhaps sideloading the OTA from stock recovery.
sliding_billy said:
I'm still not seeing an answer to JD's question. Can you unlock your BL, and if so load the factory image? You should be able to do this all without ever adding your G acct or connecting. Then, when you add it (after running with the -w in place for a full factory reset), maybe it will not pop up the managed notification.
---------- Post added at 03:40 PM ---------- Previous post was at 03:39 PM ----------
Just saw your replies as I sent this...
---------- Post added at 03:41 PM ---------- Previous post was at 03:40 PM ----------
Perhaps sideloading the OTA from stock recovery.
Click to expand...
Click to collapse
Hey thanks for the reply. I have been reading a bit more and it appears to have a zero touch enrollment for device policy which appears to provision the device with the restrictions (can't add google account, auto factory resets after 1 hr). This process uses the SN or IMEI so I am thinking other than root and a lot of system mods, no way around this.
I'd like to get the device back to google but not sure who will cover my $450 out of pocket.
https://support.google.com/work/android/answer/7514005?hl=en
isaacws said:
Hey thanks for the reply. I have been reading a bit more and it appears to have a zero touch enrollment for device policy which appears to provision the device with the restrictions (can't add google account, auto factory resets after 1 hr). This process uses the SN or IMEI so I am thinking other than root and a lot of system mods, no way around this.
I'd like to get the device back to google but not sure who will cover my $450 out of pocket.
https://support.google.com/work/android/answer/7514005?hl=en
Click to expand...
Click to collapse
Have you filed an eBay/PayPal claim?
Exactly Same Issue - Managed By Google LLC
Ive got the same issue..Wondering if youve found a way out of this..
I have the same issue. I called several times Basically,t he number that comes up and tells you to call is actually a number for internal employees of Google to call ,not. For us commoners. I was able to sign in on the device and basically she couldn't see it on their end that it had never happened. nor she could she put together the fact that this device is an asset of theirs and was stolen from an executive employee then sold to me on OfferUp.I had just gotten my Motorola z play stolen a few days before and I was in desperate needs to get a new phone because that's how I make my income.now I assumed that there was no factory reset protection on the phone so I thought it was free and clear.but you're right this brings a whole new issue into light and that is this remote Management function that they've always had and always use but I just never said it and now they're bringing it into the light I guess
I wonder if they ever think of these situations and how they're intercommunications certainly tell us that they don't have their s*** together yet and they ought to start thinking about these situations that their decisions can affect other people. Now I'm out a whole bunch of money and I'm not a wealthy person I need to deal with this blind side
Personally I think that they should let it go somehow because people pay money for things and gets built gets bills of sale and it makes me wonder are these phones even hours if I buy the phone does it mine or do if I buy the phone does it still belong to Google? If the phone belongs to me then I should be able to do whatever the hell with it that I want.well I'm still going to be looking for a work around I think eventually we might figure something out but I'm running into the same as you guys are having also and it's quite maddening because I really underestimated the pixel 3 phone cuz I really like it and I want to continue getting I want to continue using it but their policies and bureaucratic procedures and red tape and yada yada yada are going to get in the way and I know it.
No, purchase of stolen property does not make it yours. Somebody stole both a phone from Google and your money. Google may not come after you for their phone, but don't expect them to give you something for free because somebody else stole something from them; more likely they would just remotely brick the phone and write it off.
Enable debug mode.
Do a fresh start cleaning all.
Restart phone but remove sim card.
Before connect on wifi, plug the phone on USB and type this lines of code via fastboot mode:
adb devices
adb shell
pm list packages | grep ‘google’
pm list packages | grep ‘work’
pm uninstall -k --user 0 com.google.android.apps.work.oobconfig
Give me a reply if it works for you!
Hola soy de Lima Perú tengo el mismo problema compre un Google pixel 3xl y me sale el aviso que se formatea en 1 hora necesito que alguien me ayude gracias +51934644739 por favor ayuda si alguien tiene la solucion
C:\ADB>adb shell
coral:/ $ pm list packages
-------------------------------------
coral:/ $ pm list packages
-------------------------------------
coral:/ $ pm uninstall -k --user 0 com.google.android.apps.work.oobconfig
Success
coral:/ $
rodrigo82 said:
Enable debug mode.
Do a fresh start cleaning all.
Restart phone but remove sim card.
Before connect on wifi, plug the phone on USB and type this lines of code via fastboot mode:
adb devices
adb shell
pm list packages | grep ‘google’
pm list packages | grep ‘work’
pm uninstall -k --user 0 com.google.android.apps.work.oobconfig
Give me a reply if it works for you!
Click to expand...
Click to collapse
Thanks !
rodrigo82 said:
Enable debug mode.
Do a fresh start cleaning all.
Restart phone but remove sim card.
Before connect on wifi, plug the phone on USB and type this lines of code via fastboot mode:
adb devices
adb shell
pm list packages | grep ‘google’
pm list packages | grep ‘work’
pm uninstall -k --user 0 com.google.android.apps.work.oobconfig
Give me a reply if it works for you!
Click to expand...
Click to collapse
I was so pissed to find out the phone I bought was a work phone from Google themselves. I downloaded platform tools for android, shift + right click to open powershell within folder, entered the commands.. and voila !
I literally searched for hours on end, and this was the only thing that worked ! Thank you so much, I really appreciate it Rodrigo !!!!!
Victory954 said:
I was so pissed to find out the phone I bought was a work phone from Google themselves. I downloaded platform tools for android, shift + right click to open powershell within folder, entered the commands.. and voila !
I literally searched for hours on end, and this was the only thing that worked ! Thank you so much, I really appreciate it Rodrigo !!!!!
Click to expand...
Click to collapse
Happy to help!
Sorry for revising this thread. The adb way worked perfectly on my pixel 4a until recently, when I stupidly upgraded to Android 12. I did the adb part again but now the phone shows one notification that says "The phone is managed by admin and will reset automatically very soon". Any suggestions?
cohomology said:
Sorry for revising this thread. The adb way worked perfectly on my pixel 4a until recently, when I stupidly upgraded to Android 12. I did the adb part again but now the phone shows one notification that says "The phone is managed by admin and will reset automatically very soon". Any suggestions?
Click to expand...
Click to collapse
I guess I got lucky, as I upgraded to android 12, crossing my fingers that it wouldn't revert back to that admin lock.
Would a factory reset downgrade to the previous version ? And then maybe doing the ADB again ? I'm sorry, wish I had more to help you.
Please post back if you get a fix, because I'm sure there are many others with the same issue.
Unfortunately I am completely screwed now. I've tried everything I could with no luck. I guess unless a way to unlock the bootloader is found this phone is just a paper weight.
cohomology said:
Unfortunately I am completely screwed now. I've tried everything I could with no luck. I guess unless a way to unlock the bootloader is found this phone is just a paper weight.
Click to expand...
Click to collapse
I'm sorry to hear that. I hope you can find a solution..
So I just ordered a Pixel 3a today and it's the T-mobile locked version. Now I think I might have messed up because I just read that the T-mobile version cannot be bootloader unlocked or even flash factory images (or beta?). This honestly didn't even cross my mind because I thought Pixel devices were always fully open and is a main reason why I wanted it.
My question is if there is anyway to bypass this restriction and run the Google factory image? When I got a T-mobile OnePlus 6T there was a tool that allowed me to flash the factory image and then enable bootloader unlocking. I've been searching online but finding conflicting information that is outdated from a year ago.
Edit: What happens if you adb sideload an image with the bootloader locked as described here? https://developers.google.com/android/ota
My pixel 3a is the T-Mobile version. I was able to unlock the bootloader with zero issues. What seems to be the hangup on your end? I've talked to a few people who have had similar issues, and they stated that OEM unlocking was unavailable in the developer options menu. Is this where youre getting stuck? Or does the problem occur in fastboot when you actually attempt the unlock?
If the issue lies in the developer options menu, there's a workaround that I'll have to find for you. But i *think* what is happening is when you do a factory reset, it installs the generic image -- but as soon as it boots up, the Tmobile Sim causes carrier specific settings/software to be overlayed and effectively blocking the "OEM unlock" setting from being toggled. Without researching it, I believe the solution to your problem is to remove the sim card, then do a factory reset. Boot it up, go through the setup without the SIM physically installed. This should theoretically keep the the option to enable OEM locking available to be turned on.
I bought mine through T-Mobile, used it for 3 months and then asked to have it sim unlocked, which they did. At that point, I installed the verizon Sim card, did a factory reset, and the option to unlock the bootloader became available. So the method I laid out above, should work for you. If not, I'll actually dig around and get ya set up.
Let me know how it turns out, k?
Hi everyone,
First of all, sorry for my english, it's not my native language.
My brother gave me his Samsung Galaxys A50 stating that he couldn't remember his lock screen password and wanted me to fix it. Maybe that's where I ****ed up, but I went straight into recovery mode and wiped to factory reset. Note: there was no USB Debugging or OEM Unlock options active. The phone booted back up and, as usual, I had to enter my Google credentials so that it can verify my identity and let me continue with the setup process. It prompted me to 2FA and I first inserted the code I received on the phone number associated to the Goggle account. Then, it send another code on my brother secondary address mail linked to the first's one. But the email never arrived. It didn't matter how many times I tried refreshing the page or searching into every Gmail folder, the email was nowhere to been seen. And as if it wasn't enough, the primary mail address was locked because of too many tries. I tried everything, using ADB from the recovery is obviously working only for adb sideload and not for adb shell. Neither does fastboot work, as it can't even recognize the phone in Download mode because it is still locked. I even tried flashing directly TWRP with Odin but it still wouldn't work, again because of the bootloader being locked. Odin gets stuck on the NAND write part. I searched for a way to unlock the bootloader/root/enable USB debugging from adb but can't seem to find anything. I found 2 ways to bypass Google FRP but it needs adb shell or the Google keyboard. But Samsung phones have their OEM keyboard and can't, apparently, change it to Google.
Tried to get assistance from Google but, at least in my country, you need to pay to have it.
I think my only option, if doable, is to try to find a way to flash a stock rom and pray that it won't lock the phone with FRP.
Does anyone of you know of any solutions or advice I could use?
Have I to admit defeat and pay Google, hoping that the assistance is good enough to resolve the issue?
Should I just throw it into the bin and forget about it?
Thanks to everyone who helps.
Google it.
Almost everyday we get a new member asking this. While some of the inquiries might be legitimate others are not. My dead dad, brother, aunt's phone, whatever. It's a poor start entering the forum like this, in my opinion.
All the last owner needed to do was to delete their Google account from the phone and none of this would happen. Consequences.
blackhawk said:
Google it.
Almost everyday we get a new member asking this. While some of the inquiries might be legitimate others are not. My dead dad, brother, aunt's phone, whatever. It's a poor start entering the forum like this, in my opinion.
All the last owner needed to do was to delete their Google account from the phone and none of this would happen. Consequences.
Click to expand...
Click to collapse
As I said in the post, I know all the credentials used to log in the phone, I have the phone number which was linked to the Google account and the secondary mail address linked to the primary one. So, this should be enough to prove that my inquiry is legitimate.
Also, "Google it" makes me think you haven't really read what I wrote. As I said, there seems to be not a single answer.
Third and last point, how tf was I supposed to remove the Google account if the phone was locked by the forgotten pin?
Yes, this type of inquiry is surely blasonated, but insinuating that I stoled the phone without even reading the rest of what I wrote surely isn't going to help anyone, don't you think?
Having said so, if you don't have no way to help just shush.
As @blackhawk recommended it: GOOGLE FOR A SUITABLE FRP-UNLOCK TOOL. It exists for Samsung devices, too.