Hi guys
I have recently been helping out a local pawn shop with some of their pawned devices and bypassing Google's FRP system. This has been fairly successful on the more popular devices by both LG and Samsung.
Over the weekend they asked me to take a look at an LG K8 M200n that had been pawned and the reset had triggered the FRP.
I spent a good 2 hours trying the various guides I had found online and hit issues with each one.
Some of the guides flat out didn't work as the early steps I was advised to do (add a wifi network, type in random letters, select them and then choose assist) were unavailable
Some of them had partial success but I was unable to get the last step to complete.
The closest I have come to this is getting in to the SVC Menu and selecting LDB but unable to turn on ADB Debugging. I was also able to get into the actual settings menu for the phone and disable setup apps and google services but unable to turn on Unknown Sources to allow the installation of Quick Shortcut Maker.
This is the first phone I have helped them with that has actually caused me some major problems.
The phone details are as follows:
LG K8 M200n (2017)
Android Version - 7.0
Security Patch - 1 Mar 2018
Kernel - 3.18.31
Software Version - V10l-EUR-XX
Build Number - NRD90U
Anyone got any ideas or suggestions?
Common methods
Have you tried the LG bypass tool? https://www.file-up.org/7e6838bszflr
There is a way to do that but I cuurently forget how, I'll look through my notes and get back to you later if I can find the method.
Related
Hi everyone,
I have a LG G6 (H870DS/SEA) and it's a great device. Even better with Oreo, now the device doesn't have the problems we've had on Nougat.
Let me tell a quick story about security and this device. I've upgraded officially (using LG Bridge) to Oreo one month ago, I think. Everything worked at the time: my bank account, Pokémon GO (which uses SafetyNet) and every single application that depends on device certifications.
Recently, after seeing so many posts about the new ThinQ features, the bright camera mode and the rename, I decided to flash the CIS firmware using LGUP and UPPERCUT to make the G6 detectable by LGUP. No problems, SafetyNet was indeed working at the time (attested using Pokémon GO).
After some time w/out using the device, I decided to go back and use it. Yesterday, I tried to open my bank application and it failed several times with the same error code. I thought that it was some kinda of problem with my account, but then I realized that SafetyNet problems actually does the same things when the CTS profile mismatchs or something else prevents SafetyNet to be attested.
With that in mind, I decided to install a "SafetyNet checker" and see what was actually going on. Boom. SafetyNet failing multiple times. It says my device doesn't support SafetyNet (which is a lie, IMO). Initially, my thoughts were that, upon flashing the CIS firmware, something broke and SafetyNet end up broke. Tried to flash the last SEA firmware, no luck. Tried to revert back to the original SEA Oreo firmware (which I flashed the CIS firmware on top), no luck at all.
Apart from my bank application, Pokémon GO and any application that eventually uses SafetyNet for security checking, everything else works. I just don't know what happened with this, as I don't know if my device is still "official" or a red bright light was powered during the flash process (which, IMHO, I doubt, otherwise I'd have seen this on the start).
At this point, I think I'm stuck into this unless a bootloader unlock comes along sometime (this is not impossible, but let's keep hoping for now) and Magisk + its modules are activated in order to hide SafetyNet approval.
TL;DR:
- My phone is failing on every SafetyNet test and I just don't know why;
- It runs official firmware. However, it went through LGUP flashes 2-3 times now;
- There are no root or bootloader unlock methods to this specific model, so there were no unofficial modifications whatsoever;
- The problem started recently, as the SafetyNet depended applications seemed to work after the first flash;
- The first flash actually changed the region (SEA>CIS), so I just don't know if this is the real problem or this is just an unfortunate coincidence;
- I just reverted the phone to its normal region (SEA), and it keeps failing;
- According to multiple SafetyNet checkers, it just says it's uncompatible and tells something about an empty payload. Neither the CTS profile is available;
- Just in case, if someone wonders about the versions I've used until now, the order of the flashing process is:
SEA Nougat -> SEA Oreo (LG Bridge) -> CIS Oreo (LGUP+UPPERCUT) -> SEA Oreo (20C/LGUP+UPPERCUT) -> SEA Oreo (20A/LGUP+UPPERCUT)
If this problem is also happening with someone, or happened to someone else and eventually had a fix, please show the way. If you had the problem, please answer the questions below:
- Have you ever used LGUP with this device? If yes, which firmware did you flash?
- There was a region/carrier change? (eg.: SEA -> CIS, CIS -> EUR, TIM BRAZIL -> BRA and so on)
- SafetyNet dependents were working after the flash?
- Did you wipe your device after the flash? (if you've answered "yes" to the first question).
Thanks in advance.
Mr. I.
(PS: this is NOT a thread to ask for a bootloader unlock. Please don't answer this just to ask for a solution to this. Thanks!)
Coming from GNote 3, totally new to LG devices.
Locked Verizon G6 V988T has Google FRP lock, trying to remove it.
After going through frp unlock process and getting to file manager, bringing up settings I am getting a reduced version of settings. Options are wifi and data only; and if you click more there's only bluetooth and hotspot. And that's it. So I have no way of enabling install from unknown sources, so that I can install slide.
When I use the other method where in chrome you search for a business number, hit call and it brings up the dial pad so that you can dial service menu, there's no response. Even dialing imei does not bring the imei ID number. Seems this is disabled too.
I have no idea what software version is installed currently but it seems those two options/routes have been disabled/blocked. So my thinking is to downgrade to 7.0, follow the FRP unlocking procedure. Then install TWRP, root it.
I cannot properly ID the correct older kdz file for this phone.
1-Can you guys confirm if my steps are the way to go in order to be able to unlock frp, and,
2-a link to the correct kdz version for this phone?
Took a while/couple of tries but mission accomplished.
Good day,
I know this question has been asked a million times already. FW version of the device is m10 and when I try the usual bypass tricks, access to chrome/youtube is denied meaning that either it waits and spins on the youtube URL or does not allow me to get to settings to perform the next step. The phone is mine, one day I got stupid and wanted to install lineage by directly resetting it. Now I am stuck at FRP gate.
Any ideas?
V20 h910 AT&T
Thanks,
-a
The toggle to enable OEM unlocking under developer options is completely missing, and nothing seems to make a difference.
The widely-shared workaround involving changing the date didn't work.
Waiting seven whole days didn't work.
Is 168 hours uptime with no reboots necessary?
Is a Google account necessary?
Is a Samsung account necessary?
Could someone please just explain the exact set of conditions necessary to enable this option?
try connecting to wifi
SiliconValleyPondScum said:
The toggle to enable OEM unlocking under developer options is completely missing, and nothing seems to make a difference.
The widely-shared workaround involving changing the date didn't work.
Waiting seven whole days didn't work.
Is 168 hours uptime with no reboots necessary?
Is a Google account necessary?
Is a Samsung account necessary?
Could someone please just explain the exact set of conditions necessary to enable this option?
Click to expand...
Click to collapse
I would like to find the answer, I am with this problem in a galaxy xcover pro that I need to root to use development apps, no method worked for me and even worse it was automatically updated to Android 11, I have even less hope that it will work
Is this an LTE variant?
-SpaceCowboy- said:
I would like to find the answer, I am with this problem in a galaxy xcover pro that I need to root to use development apps, no method worked for me and even worse it was automatically updated to Android 11, I have even less hope that it will work
Click to expand...
Click to collapse
I also have Samsung Galaxy Xcover Pro (SM-G715FN) with Android 11. On my phone the `OEM Unlocking` option appeared after using phone for 7 days and I successfully rooted the phone. I had Google account, Samsung account and automatic software updates enabled, but I don't know if it was neccesary.
d5sword said:
I also have Samsung Galaxy Xcover Pro (SM-G715FN) with Android 11. On my phone the `OEM Unlocking` option appeared after using phone for 7 days and I successfully rooted the phone. I had Google account, Samsung account and automatic software updates enabled, but I don't know if it was neccesary.
Click to expand...
Click to collapse
thank you, i trie and coment you
The following worked for me:
1. Factory reset
2. During tablet setup:
a. connect to wifi
b. Sign in to Google and Samsung accounts
3. turn on developer mode
4. the OEM Unlock option appears!
I did not have to reset the tablet date/time.
Can I get someone with a Tab S6 to confirm the above?
---
Edit:
Here's the relevant software info:
One UI Version: 3.1
Android Version: 11
Kernel Version: 4.14.190-21627332-abT860XXS3CUG1
Build Number: RP1A.200720.012.T860XXS3CUG1
-SpaceCowboy- said:
I would like to find the answer, I am with this problem in a galaxy xcover pro that I need to root to use development apps, no method worked for me and even worse it was automatically updated to Android 11, I have even less hope that it will work
Click to expand...
Click to collapse
TLDR: Just enable Wifi.
I bring you the answer today
I'm with a XCover Pro running Android 12 already (G715FNXXUADVG4). Before connecting the device to the internet, I absolutely wanted to prevent any further updates, as I'm going to use some variant of the xposed framework and higher Android versions make things more complicated.
So I disabled automatic Updates in the developer options (and everywhere else I could find anything update-related).
I even removed almost every app, including update apps, using this debloat script: https://github.com/khlam/debloat-samsung-android .
I have no Samsung account nor Google account.
The option to unlock the bootloader was still missing.
I changed the date from 2022 to 2023 (for some reason it was a couple of months off). I restartet the phone.
Still no option to unlock OEM.
The device told me there were updates available now (for whatever reason). There is not even a sim card inserted, yet.
Then I enabled wifi. Couldn't tell if any updates happened, didn't notice anything going on.
And then the magic happened ...
"Unlock OEM" appeared INSTANTLY in the developers menu, just after the device connected to wifi / internet.
That's it.
Hello everyone. I recently purchased a used Pixel 4. Past owner said WiFi+Data stopped working after updating Android and that the phone is unlocked and carrier-free. I need to unlock bootloader in order to install GrapheneOS but it is greyed out. As you can see in the screenshots, it seems like the phone is not recognizing WiFi and IMEI hardware while booted. IMEI does show up in the barcode menu option in fastboot. System UI crashes if I try to open WiFi config. The only thing I could try was tethering via Bluetooth from my other phone and updating Android OS and apps. Already tried wiping everything and forcing phone to connect to Google while on Bluetooth tethering by pressing (*#*#2432546#*#*) in the dialer as sugested here: https://source.android.com/setup/contribute/flash#preparing-your-device
This doesn't show any success or error message.
One thing that may have happened is this: https://www.phonearena.com/news/google-pixel-android-12-verizon-update-issue_id136367
Apparently Google sent OTA Verizon update to unlocked Pixel 4's by mistake. Maybe the wrong software is what is making it not recognize WiFi+Data?
Current installed build is 12.1.0 (SQ3A.220605.009.A1, Jun 2022). Maybe I should wait for a new SP* instead of SQ* build to come out and try installing it? This is because P is for the main platform branch as explained here: https://source.android.com/setup/start/build-numbers#build-ids-defined
Hopefully it comes out before October since that is the end-of-support date.
OTA builds: https://developers.google.com/android/ota#flame
Other option would be to try out this but it seems the riskiest and last resort option:
Unlock carrier locked bootloader Pixel [BETA]
UPDATE AS OF 16 OF MAY 2023 This project isn't working right now, but I am still working on it. However due the complicated nature of the projects and the fact that I have little free time means this project will probably still take time to get...
forum.xda-developers.com
And yet another option would be to purchase a new board and replace it.
What do you think? I tried submiting the IMEI to T-Mobile's site and it says it is OK to be ported. Verizon's site didn't let me submit the IMEI I don't know why. And for AT&T I didn't find any site for that. IMEI checks say it is not blacklisted.
Did u solve this?