Anyone here run into this issue?
I have been using my phone for weeks after I did a bootloader unlock. I set the phone up like normal but now Pixel Setup wants to run again?
Related
When I set up my HTC One S to use a PIN, I noticed that whenever I get a call and press answer, it asks for my pin and when I type it in the phone is unlocked, with no call.
Anyone else experience this? Is it a bug?
I've also been experiencing random reboots every now and then.
Stock ROM. Bootloader is unlocked, phone rooted but only for Titanium Backup purposes and also SetCPU which I set to ondemand.
The rebooting is ok I figure it's just some bugs in the software, but obviously must be able to answer calls. As long as this works, there's no way I can use a pin, and I really should have one on my phone.
Anyone else noticed this?
Hi Community!
I was wondering if there was a way to skip the initial activation screen / setup wizard. Ive been looking around to see if there was something that can be done with adb but it seems in order to talk to the device (at least on my mac), the device has to have developer options turned on and MTP set in order for adb to talk to the Samsung S7.
Really what Im looking for is something in which I can plug in a phone or phones in and run and have them get past the activation screen and straight to home screen.
Anybody know of a way to do this?
-Zet
Hello,
Did you found a way to do that?
Thanks
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?
Hey guys, havent been on here for a while but I dug up my old Pixel and was trying to mess around with it again. However, my dad had factory reset it because he didnt know my old pin and now I can't get past the Pixel set up screen because it is asking for my old pin, and when I try to login with my email instead I cant because I had removed the device from my google account a year ago. Is there any way for me to bypass this? I tried using adb but because it doesnt go past the set up screen I am unable to enable ADB in the settings or enable unlocking the bootloader. I dont even know what firmware it is on but I am pretty sure it is updated to the latest version.
mod can you take this down, did an frp bypass and i got it to work
Hey peeps, I'm having a problem. I don't use my phone with a pin or any kind of locking. Now some apps are demanding having a pin on the phone in order to use them (for example my homebanking app). Does anyone know if there's any way to make the apps believe I have a pin set without me actually having it? I'm using an Oneplus 3T rooted with Android 9 in any case.
Thanks!