I received a new (to me) 2017 Shield via RMA from nVidia. I plug it in and go to set it up but when I get to entering your google account info, it consistently fails. The option to use androidtv dot com/setup and enter the provided PIN fails with "Something went wrong" (yes I'm on the same wifi, also fails when wired). The option to type in your account credentials also consistently fails saying my user name and password don't match. Now before you say "learn 2 type", immediately after not logging in, I get a security notification saying a new device has logged in to my account. This same result happens with any gmail account I try. I have factory reset the Shield (as instructed by nVidia support) to no avail. I have contacted Google support but they say it's nVidia's problem. I'm not sure what to do next. Any suggestions would be greatly appreciated.
Jesterium said:
I received a new (to me) 2017 Shield via RMA from nVidia. I plug it in and go to set it up but when I get to entering your google account info, it consistently fails. The option to use androidtv dot com/setup and enter the provided PIN fails with "Something went wrong" (yes I'm on the same wifi, also fails when wired). The option to type in your account credentials also consistently fails saying my user name and password don't match. Now before you say "learn 2 type", immediately after not logging in, I get a security notification saying a new device has logged in to my account. This same result happens with any gmail account I try. I have factory reset the Shield (as instructed by nVidia support) to no avail. I have contacted Google support but they say it's nVidia's problem. I'm not sure what to do next. Any suggestions would be greatly appreciated.
Click to expand...
Click to collapse
I have the same problem. Did you manage to get this fixed by chance?
Yes. I fixed it by flashing a recovery image. 8.0.1 just caused a boot loop but flashing 8.0 worked.
https://developer.nvidia.com/gameworksdownload
Jesterium said:
Yes. I fixed it by flashing a recovery image. 8.0.1 just caused a boot loop but flashing 8.0 worked.
https://developer.nvidia.com/gameworksdownload
Click to expand...
Click to collapse
Thanks for getting back to me. I assume that to flash a recovery image, I'll need to unlock the bootloader? I was trying to avoid flashing, but it doesn't look like another solution will work...
Aripex said:
Thanks for getting back to me. I assume that to flash a recovery image, I'll need to unlock the bootloader? I was trying to avoid flashing, but it doesn't look like another solution will work...
Click to expand...
Click to collapse
I tried quite literally everything I could think of - multiple google accounts, different networks including hot-spotting my cell service, multiple factory resets. It seems my problem may have been a very outdated OS as after I was able to flash, the setup process was in a newer android style. It didn't occur to me that what I was seeing previously was "old" and may explain why it wouldn't connect to google.
Keep in mind, you can lock the bootloader again when you're finished.
Jesterium said:
I tried quite literally everything I could think of - multiple google accounts, different networks including hot-spotting my cell service, multiple factory resets. It seems my problem may have been a very outdated OS as after I was able to flash, the setup process was in a newer android style. It didn't occur to me that what I was seeing previously was "old" and may explain why it wouldn't connect to google.
Keep in mind, you can lock the bootloader again when you're finished.
Click to expand...
Click to collapse
Cool - thanks for the advice. Like you, I tried everything too. I tried 2FA on/off, turned on the "Less secure apps" option in my Google Account > Security. I also tried to factory reset without any success, as well as using a different Wi-Fi network and opened a new dummy Google Account just to make sure my original account wasn't the problem! None of it worked and had me tearing my hair out.
I have a 2015 Shield TV that was sealed and unused until the last week. I have never seen an issue before where even an older Android device cannot be signed into Google. At least it is a lesson learned for the future....!
Anyway, I've successfully flashed a newer version of Android now and it works. Hallelujah!
Right guys I have just got a replacement NVidia pro 500gb from them for a bricked unit and I am having the same problem. As I am a novice I have no clue about flashing an updated image to it. Is there anyone who is will to spell it out for me in easy to follow instructions??
Related
So I fell victim to googles new FRP Security feature that requires you to log in using the same gmail account associated with the phone before it was reset. Short of it was I decided to flash a 6.0 ROM after using the 5.1.1 ROM to get my Project Fi account activated correctly.
After flashing 6.0 and I began going through the setup wizard where I was eventually prompted to enter the credentials for the account that I had used previously. I entered my credentials and was then sent to another screen asking me to reset my Gmail password (Turns out google decided my login attempt was suspicious...). So i reluctantly reset the password not knowing I had just screwed myself(for 72 hours at least). There is a 72 hour reset time from the time you changed your account password until you're able to use it to authenticate during the setup process and until you authenticate you cant use the phone.
Not having a backup phone I took to google and found that the only way around this problem involved a USB OTG storage device loaded with an apk that causes the settings app to launch allowing you to do a real factory reset(complete wipe of all credentials and data). Resetting the phone this way removes any account associations allowing you to setup the phone as if it were new once you've re-flashed it.
Not having the tools needed to do it that way I thought about it and decided to try a few things out and eventually found my solution.
Disclaimer: I am not responsible for any damage or loss of data that may result from the following procedure.
Solution
Requirements
A computer with adb installed
USB cable
Rom with Persistent ADB Enabled (I used the 5.1.1 Stock, Rooted Project Fi ROM)
Phone booted and at the Setup Wizard
Procedure
Have the phone turned on and sitting at the startup wizard
Connect the USB to you computer and then plugin your phone ( I assume you've already setup ADB)
The phone may then prompt you and ask to verify the device fingerprint which you will say yes to
open a terminal and type:
Code:
adb shell
Code:
am start -S com.android.settings -c android.intent.category.LAUNCHER 1
This will launch the Settings.apk
***NOTE: This will completely wipe your phone!*** (Edit: The Reset program claims to wipe all internal storage but for whatever reason my SDcard data was not touched. Would still recommend pulling any wanted data from the device prior to resetting)
Go to the Backup & Reset menu and perform a factory reset
After the phone finishes resetting, proceed to boot back into Recovery mode and re-flash your ROM
The Setup Wizard will now go through the steps without the FRP authentication steps.
Again, I have only tested this on my T-Mobile Nexus 6 (using Project Fi) running 5.1.1 so your mileage may vary depending on your setup. If you find this worked or didn't work for your particular setup/situation then post your results here.
Hope this helps!
EDIT: The original solution using the USB OTG storage can be found here.
Just to clarify a bit. The problem that these two methods try and fix stems from a new feature introduced in Lollipop called FRP(Factory Reset Protection). It is meant to keep someone that has stolen a phone from being able to use it by simply doing a factory reset and reinstalling the OS. To counter this, google requires the user to verify they're the owner of the device that was reset by giving the credentials of the google account associated with the phone before it was reset. The issue arises when the password to this account is changed after the device was reset but before verifying ownership of the device during the setup process. When this happens, you have to wait 72 hours before you will be able to verify ownership using the new password.
Edit 2: Specified having a ROM with Persistent ADB Enabled as a requirement for this to work.
I don't really follow your problem. It sounds like you may be using 2 factor authentication? If not You Should!
Also once you set up 2 factor make sure to print out the one time codes.
Maybe that wouldn't fix this, but I thought this was one of the things the one time codes get around.
Sorry if you're really saying that you can't reset your phone for 3 days after you change your password. If it is really that simple it seems pretty broken. I'd call Google on the phone. They are the only major corporation I've ever seen that has a phone answered by people that know what they're doing and can actually help you.
Sent from my Nexus 6 using Tapatalk
joyrida12 said:
...snip...
Click to expand...
Click to collapse
Ah, a workaround, nice!!! Tahnks for sharing!
Keep "OEM unlocking" enabled in the future. It will disable "Device protection"
---------- Post added at 02:27 PM ---------- Previous post was at 02:27 PM ----------
ethutch said:
I don't really follow your problem. It sounds like you may be using 2 factor authentication? If not You Should!
Also once you set up 2 factor make sure to print out the one time codes.
Maybe that wouldn't fix this, but I thought this was one of the things the one time codes get around.
Sorry if you're really saying that you can't reset your phone for 3 days after you change your password. If it is really that simple it seems pretty broken. I'd call Google on the phone. They are the only major corporation I've ever seen that has a phone answered by people that know what they're doing and can actually help you.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
This is not about 2 way auth i'm affraid
ethutch said:
I don't really follow your problem. It sounds like you may be using 2 factor authentication? If not You Should!
Also once you set up 2 factor make sure to print out the one time codes.
Maybe that wouldn't fix this, but I thought this was one of the things the one time codes get around.
Sorry if you're really saying that you can't reset your phone for 3 days after you change your password. If it is really that simple it seems pretty broken. I'd call Google on the phone. They are the only major corporation I've ever seen that has a phone answered by people that know what they're doing and can actually help you.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
No, this isn't an issue with 2FA. From Google's standpoint this isn't an issue at all actually. This verification is, to my understanding, only required when the device is factory reset in recovery mode.
The purpose of 72 hour lock period seems to be there to protect user in the event someone is trying to gain access to their phone/account.
This normally isn't an issue since most people won't change their password in that small timeframe. In order to not require the verification, you have to disassociate the account from the phone before resetting it. This is done for you when you do a reset from the settings app on the phone. That's the reason for using these methods, it does a full reset including account removal.
Sent from my Nexus 6 using Tapatalk
@joyrida12
Would you mind sharing the other solution you found? The one *with* USB OTG.
Thanks in advance!
Droidphilev said:
@joyrida12
Would you mind sharing the other solution you found? The one *with* USB OTG.
Thanks in advance!
Click to expand...
Click to collapse
Edited the post and added a link to it
Sent from my Nexus 6 using Tapatalk
joyrida12 said:
Edited the post and added a link to it
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
perfect, thanks!
Great work around.
I love that Google is putting in theft detection. A good fix to this chaos would be to require you to auth to do a reset from settings. That would close the hole. They also need to allow you to skip the 72 hour reset time with more security questions/answers. You know Google caches your PC settings. Simply logging into your google account from a known PC would be a great way to allow account authentication.
I am about to return my phone to amazon so just factory resetting through the settings menu will be fine for returning the phone so the next person doesn't have problems?
Sent from my Nexus 6 using Tapatalk
So to recap. It will NOT work on a device that was reset. Since USB debugging is off after a reset.
player911 said:
Great work around.
I love that Google is putting in theft detection. A good fix to this chaos would be to require you to auth to do a reset from settings. That would close the hole. They also need to allow you to skip the 72 hour reset time with more security questions/answers. You know Google caches your PC settings. Simply logging into your google account from a known PC would be a great way to allow account authentication.
Click to expand...
Click to collapse
That was my thoughts exactly as it was happening to me, I initially was trying to figure out if there was an alternate authentication method and was a little surprised not to find one.
I really like the direction they're moving with thus security feature but I think it was thrown out a bit early. Nexus users are more likely to be doing factory resets and locking them with no way of fixing it (aside from waiting 3 days) out because they did so on a custom recovery isn't very cool on their part lol.
Sent from my Nexus 6 using Tapatalk
sthpaw01 said:
I am about to return my phone to amazon so just factory resetting through the settings menu will be fine for returning the phone so the next person doesn't have problems?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yes, that will work just fine.
yossijoe said:
So to recap. It will NOT work on a device that was reset. Since USB debugging is off after a reset.
Click to expand...
Click to collapse
It worked for me. Before I figured this method out I had reset and flashed 2 6.0 ROMs and then the 5.1.1 ROM. Once I got to the setup wizard my device was listed under adb devices and I was able to get a shell.
Edit: It could be that the project fi ROM has USB debugging enabled by default(just a guess, haven't looked at the source to verify).
Edit 2: Confirmed that the Stock, Rooted, decrypted 5.1.1 ROM for Project Fi has persistent ADB enabled. Adding this as a requirement to the original post.
Sent from my Nexus 6 using Tapatalk
sthpaw01 said:
I am about to return my phone to amazon so just factory resetting through the settings menu will be fine for returning the phone so the next person doesn't have problems?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
He's wrong, that absolutely will not be fine.
You need to make sure to remove any screen locking you've setup, sync your Google account, and then remove your Google account before resetting.
http://forum.xda-developers.com/nexus-6/general/guide-properly-prepare-nexus-6-resale-t3104504
My nexus 6 doesn't have custom recovery installed,It has only stock one,the phone is on stock rom,and it is stuck in setup screen asking for 1st used gmail !
I have OTG usb cable but it is useless ,not working, seems motorola improved security in nexus 6,to be specific the phone has OEM lock ,so i can't install cust.recovery
is there any trick to apply those adb commands ?
any help friends ? im still stuck ,any way to disable OEM lock or to flash custom rom on frp locked nexus6 ?
joyrida12 said:
Before I figured this method out I had reset and flashed 2 6.0 ROMs and then the 5.1.1 ROM. Once I got to the setup wizard my device was listed under adb devices and I was able to get a shell.
...
.... the project fi ROM has USB debugging enabled by default
Click to expand...
Click to collapse
It seems you can enable persistent ADB and USB debugging on any ROM, as long as you can connect to the phone through ADB in recovery mode.
You just have to add a few lines to a file or two, then reboot the phone. See this post http://forum.xda-developers.com/showpost.php?p=47423916&postcount=5
W60 said:
It seems you can enable persistent ADB and USB debugging on any ROM, as long as you can connect to the phone through ADB in recovery mode.
You just have to add a few lines to a file or two, then reboot the phone. See this post http://forum.xda-developers.com/showpost.php?p=47423916&postcount=5
Click to expand...
Click to collapse
Hey, first time poster, long time lurker. This is the first thing I have not been able to find a solution for.
In order to connect to ADB in recovery, does one need a custom recovery? My Nexus 6 bootloader is locked, running 5.1.0 LMY47D. I have fastboot access but can't pull up an ADB shell.:crying::crying:
I bought a Nexus 6 on eBay that was reset and I do not have the original users info. (I thought I was getting a pretty sweet deal because I'm so good at phones and blah blah)
Thanks in advance for any assistance!
- Beej
Beej4real said:
In order to connect to ADB in recovery, does one need a custom recovery?
Click to expand...
Click to collapse
As far as I know, yes, you need a newer version of a custom recovery. Anyway, if ADB doesn't connect, you certainly need another recovery, and you can't install that if you have a locked bootloader.
....
In the Welcome screen, have you tried the OTG trick, or any of the other methods that seem to allow you to get in Settings, from where you can do a proper reset?
W60 said:
In the Welcome screen, have you tried the OTG trick, or any of the other methods that seem to allow you to get in Settings, from where you can do a proper reset?
Click to expand...
Click to collapse
I did give it a shot. No dice. I also tried entering lots of numbers in as the emergency number. No response from the phone.
Hi guys can you help to frp bypass on Samsung SM-G530H Galaxy Grand Prime without otg function, can i use this tut or need another rom for sm-g530h? where i can find Rom with Persistent ADB Enabled? Thanks
So I wanted to do a factory reset, to try and fix my adaptive storage issue.
It just did not work, no matter what I tried.
So, I went into the Recovery, and did a Data erase.
Now it prompts me to enter into my Samsung account - which is all fine - it worked several times before.
But now I get a "Processing Error".
The username + password is 100% correct, I can log in to my account on my laptop.
If I modify the login to some wrong one, it says "Invalid..." so I am sure it's something else.
How do I fix this?
Do I have to downgrade to LL to log in, disable lock, then upgrade, blah blah blah... tell me that's not the solution...
Oh yeah, before you guys ask: "But why didn't you just use the Reset in Settings"?
Well, I tried.
It just did not let me through the login screen. I mean, it did. Then it closed and popped up again.
Again, and again, and again.
And so I did the recovery reset. And now I am clueless. :-/
Back to basics.
Reseted my phone again. Somehow I managed to bypass login in the past - now I just cannot.
Flashed 5.1.1, but no change.
- Remade my account around 10 times.
- Tried all my passwords since I ever had the phone, with all my email combinations that I ever used for Samsung Account.
- Tried to "escape" with these bugs, but no Accessibility and similar stuff, so I can't get around the protection.
So, I will just blog about my suffering.
1 ) You can bypass the latest lock by...
2) Downgrade to 5.1.1 - but maybe this works on 6.0, don't know.
3) Install SideSync on PC, plug cable in
4) Open Chrome, install a Home Screen, and open it
5) There you bypassed. And you still can't add your Samsung account.
By the way even the website shows a quick "Wrong login" when I try to login.
So maybe the entire Samsung Account is messed up beyond repair.
I will try to upgrade to 6.0 now and pull this off again.
If that does not work, back to Youtube I go.
I recently Hard Reset my Samsung Galaxy Tab A6, SM-T285 through recovery. After booting i cannot sign in to my primary google account because it says "Sign in with a google account that was previously synced on this device". I tried all of my google account
nothing works.
1. Tried Odin Twice with two different version of Firmware
After enabling FRP Lock on Odin, Flashing stuck at "Sending Lock information" and fails
2.Tried Kies3 recovery process
3.Tried to install TWRP using Odin
FRP Lock is still there and i cannot use my phone
Please help me
If the firmware isn't installing it's the wrong one.
You need to go into developer settings and enable OEM UNLOCK.
ashyx said:
If the firmware isn't installing it's the wrong one.
You need to go into developer settings and enable OEM UNLOCK.
Click to expand...
Click to collapse
I cannot enter developer settings because phone requests "Sign in with a google account that was previously synced on this device". Next button is disabled without it.
pradeep.sl said:
I cannot enter developer settings because phone requests "Sign in with a google account that was previously synced on this device". Next button is disabled without it.
Click to expand...
Click to collapse
I would ensure you are using the correct account. My guess is its not.
The Google account will be associated with your device. If it's the correct account then you should be fine.
If you've installed the wrong firmware then Google may see your device as different.
I would sign into your account you think was used on the device via the web then go to Device activity & notifications and ensure your device is listed.
https://accounts.google.com/login
I can see two Devices
1.Samsung Galaxy Tab A6
2.Samsung Galaxy Tab A 7.0 LTE
Mine is Galaxy Tab A6, SM-T285, Recovery email address is correct.
But when i try to login that account on my phone, google says "Sign in with a google account that was previously synced on this device"
Are you not able to wipe data?
ashyx said:
Are you not able to wipe data?
Click to expand...
Click to collapse
I can flash using ODIN but FRP Lock is there
me also faces to this problem too..
already wipe data/factory reset.. account still there .. :crying:
pradeep.sl said:
I can flash using ODIN but FRP Lock is there
Click to expand...
Click to collapse
Try this :
http://www.rootjunky.com/factory-reset-protection/
hi ya
Im sorry I bet this come up a lot..I kind of need to be walked through this, I have some knowledge and disabilities, im good when its broken down and explained or simple logic way,
i have been given 2 tablets from a friend and been told I can keep one if I can fix. I have tried everything,,,
I have little programming knowledge but understand the for if else way of thinking from around 10yrs ago when I studyied at college.
I have tried Hard Reset and blimey its blocked everyway possible.
I can not get into recovery mode nor can I get in safe mode. I tried pluging in usb, sd card and all hard ware buttons are disabled. ive tried pin hole as well as disconnecting the battery and putting it back in..is their away like with pcs motherboard and processer? Although risky?
It has an app appearing to be on the main partition called Fundroid.
I wouldnt mind putting linux on both tbh.
I have photos but can not link them..
HTML:
<img src="https://i.ibb.co/ygsHSth/WP-20190302-07-13-03-Pro.jpg" alt="WP-20190302-07-13-03-Pro" border="0">
<img src="https://i.ibb.co/crDxtBh/WP-20190302-07-13-12-Pro.jpg" alt="WP-20190302-07-13-12-Pro" border="0">
<img src="https://i.ibb.co/KW5bZPW/WP-20190302-07-13-52-Pro.jpg" alt="WP-20190302-07-13-52-Pro" border="0">
<img src="https://i.ibb.co/4Jqg7QC/WP-20190302-07-14-00-Pro.jpg" alt="WP-20190302-07-14-00-Pro" border="0">
<img src="https://i.ibb.co/yPbDHx3/Screenshot-2019-03-02-at-06-04-58.png" alt="Screenshot-2019-03-02-at-06-04-58" border="0">
suzbackwardsbikes said:
Im sorry I bet this come up a lot..I kind of need to be walked through this, I have some knowledge and disabilities, im good when its broken down and explained or simple logic way,
i have been given 2 tablets from a friend and been told I can keep one if I can fix. I have tried everything,,,
I have little programming knowledge but understand the for if else way of thinking from around 10yrs ago when I studyied at college.
I have tried Hard Reset and blimey its blocked everyway possible.
I can not get into recovery mode nor can I get in safe mode. I tried pluging in usb, sd card and all hard ware buttons are disabled. ive tried pin hole as well as disconnecting the battery and putting it back in..is their away like with pcs motherboard and processer? Although risky?
It has an app appearing to be on the main partition called Fundroid.
I wouldnt mind putting linux on both tbh.
I have photos but can not link them..
<img src="https://i.ibb.co/ygsHSth/WP-20190302-07-13-03-Pro.jpg" alt="WP-20190302-07-13-03-Pro" border="0"><img src="https://i.ibb.co/crDxtBh/WP-20190302-07-13-12-Pro.jpg" alt="WP-20190302-07-13-12-Pro" border="0"><img src="https://i.ibb.co/KW5bZPW/WP-20190302-07-13-52-Pro.jpg" alt="WP-20190302-07-13-52-Pro" border="0"><img src="https://i.ibb.co/4Jqg7QC/WP-20190302-07-14-00-Pro.jpg" alt="WP-20190302-07-14-00-Pro" border="0"><img src="https://i.ibb.co/yPbDHx3/Screenshot-2019-03-02-at-06-04-58.png" alt="Screenshot-2019-03-02-at-06-04-58" border="0">
Click to expand...
Click to collapse
Can you reformat those links as they're just html nonsense.
Just post the links.
Also you haven't stated what your issue is?
I have been trying to reboot a used phone I have bought. The Samsung Galaxy J3 (6). Yes, there is a 6 after the J3 inside of a little circle. Apparently this is the closest thing that xda has to it on the forums. I have tried everything I could find on the internet to get around this google verify problem from the previous user. I have used the emergency caller to basically access everything on the phone. I have attempted to change the google account through settings, I have installed new apps to access other areas, I have have tried to downgrade Google Account Manager to disable the "error" problem in the quick shortcut app. This last method didn't work due to the phone not letting me be able to downgrade. I have installed the rootjunkie's samsung unlocker apk and got to settings. I have factory reset from here twice, with and without a password. Both did not do a thing for me. I am out of ideas. can anybody help me out here?
bobhihih said:
I have been trying to reboot a used phone I have bought. The Samsung Galaxy J3 (6). Yes, there is a 6 after the J3 inside of a little circle. Apparently this is the closest thing that xda has to it on the forums. I have tried everything I could find on the internet to get around this google verify problem from the previous user. I have used the emergency caller to basically access everything on the phone. I have attempted to change the google account through settings, I have installed new apps to access other areas, I have have tried to downgrade Google Account Manager to disable the "error" problem in the quick shortcut app. This last method didn't work due to the phone not letting me be able to downgrade. I have installed the rootjunkie's samsung unlocker apk and got to settings. I have factory reset from here twice, with and without a password. Both did not do a thing for me. I am out of ideas. can anybody help me out here?
Click to expand...
Click to collapse
The issue is FRP. Someone has factory reset from recovery instead of settings.
If you can get into settings as you say then set up another Google account then switch to that account.
Restart and log into that account.
Which firmware build is the device running?
ashyx said:
The issue is FRP. Someone has factory reset from recovery instead of settings.
If you can get into settings as you say then set up another Google account then switch to that account.
Restart and log into that account.
Click to expand...
Click to collapse
I have tried to add a Google account through several methods as well. Through settings, through Gmail app, through play store. All of which keep taking me to the same verification check screen, but it allows me to back out to the settings again.
ashyx said:
Which firmware build is the device running?
Click to expand...
Click to collapse
My version is 6.01 I believe. But I cannot downgrade to the 6.01 Google account manager with new security stuff.
Your device is nearly identical to J320A & J320AZ.
I am unsure if you need to enable "oem unlock" from Dev options to flash the kernel.
But if Odin let's you this method should get you going.
I have a Pixel 4 with Android 10 on it. It also has Android for Work (Enterprise), i.e., it is managed by work admin who can remote reset the device and also control what gets installed or not. It has MobileIron MDM agent installed on it.
How can I wipe all of this Android for Work and remove the MobileIron completely? I have no personal data on it and can do factory reset and the phone is carrier unlocked as well. The OEM unlock in Developer Options is greyed out.
Most likely, the phone was bought from Android Enterprise, which may also mean the app is built into the firmware - loaded as specified by whatever organization ordered the device from Google. But there's a couple things we can check:
Go to Accounts under Settings, make sure there is no work profile there.
Go to Security > Device Admin apps, see if you can remove the app there.
Failing those, try a factory reset. If the MobileIron app survives factory reset, it's built into the firmware.
Unfortunately there isn't much that can be done to get rid of it with a locked bootloader. You could try sideloading an OTA update but that may fail because the firmware won't match. You can also try the Pixel Repair Tool although I suspect that may not work for the same reason.
Let us know how it goes!
The phone is definitely Android Enterprise as I wrote above. There is work profile and MobileIron installed. Factory reset doesn't help. It always tries to want to setup as Android for Work.
I can't sideload anything I guess as it doesn't go to bootloader mode at all. I will try Pixel Repair Tool. Thanks for your suggestions.
agaurav said:
The phone is definitely Android Enterprise as I wrote above. There is work profile and MobileIron installed. Factory reset doesn't help. It always tries to want to setup as Android for Work.
I can't sideload anything I guess as it doesn't go to bootloader mode at all. I will try Pixel Repair Tool. Thanks for your suggestions.
Click to expand...
Click to collapse
What do you mean it doesn't go to bootloader mode?
Are you able to enable Developer Options and USB Debugging?
My bad. I tried Pixel Repair tool. It went thru successfully but did not remove the Android for Work so I guess I am stuck with a paper weight. Nothing can be done effectively. That's fine. I will wait for black friday deals and buy a new phone. Thanks.
agaurav said:
The phone is definitely Android Enterprise as I wrote above. There is work profile and MobileIron installed. Factory reset doesn't help. It always tries to want to setup as Android for Work.
I can't sideload anything I guess as it doesn't go to bootloader mode at all. I will try Pixel Repair Tool. Thanks for your suggestions.
Click to expand...
Click to collapse
If the device is enrolled in Android Zero Touch, there is nothing you can do unless the IMEI is removed from Zero-Touch.