I bought an 8T directly from OnePlus so it's not locked to any carrier. I intend to install a custom ROM on first use. I'd like to know the following before I unbox it:
Are there any steps required before the OEM Unlocking toggle is not greyed-out and before the phone will respond to the unlock command via fastboot?
I'm pretty sure I read a post a while back where the user stated the unlock command wouldn't function until he put a SIM card in the phone, or connected the phone to the internet, or logged into his Google account, or some such thing.
Does anyone with experience unlocking a brand new phone have anything to add? I've been following the 8T forums since before Mauronofrio's TWRP to learn all the procedures, but I don't recall anyone else mentioning issues specific to never-used phones.
The unlock toggle was indeed greyed-out when I unboxed the phone. Connecting to the Internet and completing the Android Setup wizard did not alter the state of the unlock toggle.
Actually, to be clear, I set up the phone first without Internet, then a few days later connected to the internet, but doing so did not make the greyed-out OEM Unlocking toggle suddenly accessible.
So at this point I'm not sure what's the issue... Does the phone need to see a SIM before it will let me access OEM Unlocking? Or does is require a Google account login? Or something else?
I found a comment on a non-XDA forum about a different type of android phone where the user reported that he had solved the problem by connecting to the internet and going through a minimal Google setup.
I gave it a try, only in my case I connected by ethernet cable (USB-C to Ethernet adapter), so it doesn't have anything to do with installing a SIM or turning on WiFi.
Then while connected I did a factory reset to re-start the android setup wizard. This time it took a lot longer to initiate the setup program and there were a lot more steps and conditions to accept along the way. Plus, there were Google terms and conditions to accept that weren't there the first time, and files I had to agree to download. :-( I disconnected before much else and rebooted. This time the OEM Unlocking toggle was enabled.
Related
Hi,
I went abroad on vacation and turned off the data connection on my Nexus S (GT-i9023). While on vacation a friend figured out my pattern to unlock my phone. Because of that I changed the pattern and of course couldn't remember the new pattern which led to my phone getting locked. To unlock it I have to sign in to my Google account but like I wrote I turned of data connection before I went abroad so I can't log in to my Google acoount. =(
Is there a way to force activate data connection or WiFi without USB debugging enabled? If not, is there a way to force activate USB debugging and then force activate data connection or WiFi? If I can get either one of them working I guess I would be able to unlock the phone by entering my Google account information.
Is there another way of recovering my pictures and videos from the phone maybe? I really really would like to be able to save all pictures and videos that I took on my vacation up until I looked it out.
Please please help and thank you very much in advance!!
Is your phone rooted?
sent from my so icey ns4G
No it's not rooted.
Have you tried entering "null" without the quotes for your password?
Yes I have tried with null as password and with and without @gmail.com with my username.
I have tried to connect it with ADB but the device is not found. I don't think the USB-debugging is activated so I guess that's why I can't see it. Isn't there any tool to force activate USB-debugging or get around that somehow? Atleast then I would have a chance.
Please, any tips?
I also contacted Samsung support but the only answer i get from them is that i have to reset my phone or send it to them so they can reset it and I don't want to do that.
There must be a way? If I connect the usb-cable while in the boot menu I can see it in the device manager as "Android phone - Android ADB Interface". But if I type adb devices the "List of devices" ends up empty.
Is there really no way? I'm totally new to this but it doesn't make sense that there is no way what so ever to get a connection to the phone. Please help, I'll try anything.
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?
Hello, I recently found an LG Stylo 3 in one of my drawers that has a knock code on it. I don't remember the code and I already tried 66 times to unlock it (it now takes 240 seconds between each attempt). No "Forgot Password" or backup pin option shows up, USB Debugging is on but it's unauthorized, and the mode that it's on when I connect the phone to my PC is Charging Only. I just want to know what pictures I have saved on it, or if I can pull out my photos or something. I can't reboot into bootloader from the recovery options, it just reboots my phone. I'm able to go into recovery, and safemode, update from adb puts it into sideload mode, and it's connected to my wifi but because I changed my passwords on my google accounts already, the phone doesn't show up in any of my google device manager accounts.
Everything is stock, no custom recovery or firmware and it's not rooted.
What can I do now? Is there a way to reset my password or bypass it entirely? I don't care how technical it is, if given a good guide I can do it. I can't find anything to help me, hopefully someone can help my problem here.
Before anything, I didn't steal the phone, it's my old phone I had when on Virgin Mobile, I can give as much proof as I can to show that it is my phone if needed. I just don't remember the knock code
Thanks!
So I had a broken USB port for a while, but since I want to pull data off my phone (including, if possible, the apps that I needed 2FA to enable like WhatsApp and so on, since I'm currently in Europe for the next 6-12 months and AT&T prepaid doesn't allow me to receive text messages or phone calls).
I bought a replacement daughterboard for the USB connector, and pulled the back of the phone off, removed the old USB connection board, and replaced it with this one. However, I've got some weird problems and I'm not sure if its hardware or software related.
When plugging the phone into USB, there's no indication on the telephone that the phone is charging, there's no indication that the phone has some connection to the computer, the computer doesn't display anything about the phone or allow me to access storage, and ADB can't find the device despite trying about 7 different methods and combinations of drivers, ADB programs, etc.
So I'd believe that my new daughterboard is either broken internally or some other issue ... except ODIN works flawlessly, as I got the inital step of loading the combo firmware to work without issue. (linked here: https://forum.xda-developers.com/t/root_method_rev_b-11_bootloader_using_combo_firmware.4374741/). But I can't get safestrap to work, because it relies on ADB, and ADB still doesn't have any way to connect to the device.
When I start the phone in download mode, I'm able to pull up a device with the Hardware ID USB\VID_04E8&PID_685D&REV_0100, but ADB doesn't recognize it. When I start the phone in any other method, the device doesn't register in device manager. It's a similar story when I tried reaching the phone with ADB from my linux desktop, as "something" exists in download mode, but adb has no ability to actually see the device or make a connection.
As far as avoiding obvious pitfalls, I enabled development mode / USB debugging / OEM unlock in the stock firmware I was running before, and also enabled dev mod/usb debug in the flashed firmware from that page.
It's quite possible that flashing the Combination firmware already wiped my data, as I'm not sure if it does it or not (after scouring the internet, it's pretty much the only option to get root with the B/11 bootloader so it was worth a shot), but ultimately I'd like to try and resolve this ADB issue so that I can actually finish the steps and see if it will work or not.
I just don't know what to troubleshoot next to try and get ADB to work.
To add on to this, I tried reaching out to AT&T to see if I can use my S8+ (VoLTE and all that jazz capable) to receive text messages while abroad here, but they won't let me use the phone even though I'm already abroad, since if it's not compatible with their network in the US it won't be compatible with their roaming network abroad. So I really do have to do the ole root trick.
So basically I have a Stock Sony Xperia Z3 Docomo variant (if I recall correctly it was D6653) that I used all the way from 2017, until I had to let it rest in 2020 because the screen was broken (although at that time before the screen went completely messed up, I managed to enable USB debugging in order to mirror the screen on my laptop with scrcpy so I can use it). It's just laying down on my desk cabinet for two years. Until finally I got a chance to replace the screen, the battery and the back cover earlier this weekend. Problem is, I already forgot the pattern to unlock it. Not even my brother (who used it sometimes to game back then) remember the pattern. Worse part is some of the SIM card, even when it does have data plan (I just simply put the SIM from my other phone), the phone is just going to show as full bar Roaming (R) and no internet at all so this phone completely have no network (although I do also have suspicion that data connection is probably disabled), and obviously that means I can't use google account to unlock it
Wanted to use TWRP or Aroma File Manager to delete the pattern lock file, but then I realized I have to flash this thing, and even if I do now understand how to install TWRP on my Z3 model because I already read various tutorial on this forum since Saturday, the problem is that OEM unlock isn't even enabled simply because at the time it was still a bit functional, I don't see it as something I need as I don't root any phone that I use. And as additional note, as time goes on obviously all of the laptop at home had gone many clean reinstall, which means no ADB key backup, and I can't authorize because pattern lock
Is there hope left, or this phone is completely locked?
(TLDR: Phone locked because I forgot lock pattern, no Internet, data stuck at R, no connection so I can't recover with google account, USB Debugging on but not OEM unlock)