[Q] H870DS failing SafetyNet API checks - LG G6 Questions and Answers

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!)

Related

LG G5 RS988 Removing RAC (rent a center) remote locking software

Hello,
I hope this post is not against the rules, but I believe I found out how to remove the Rent a Center tracking and locking software that I believe if from computrace that is installed on our devices. It acts like a root kit that automatically reinstalls itself and has a device administrator profile that you can not remove.
I think I figured out how to get rid of the RAC (rent a center) lock for good. The rac lock uses a system administrator profile along with a program called sec.abt that can not be removed or frozen. If you manage to uninstall it is just reinstalls itself. I was not able to find any information on how to remove this without using special hardware like an octopus box that costs hundreds of dollars.
I used LGUP with the uppercut modification (can be found here on XDA) along with the KDZ files from here https://lg-firmwares.com/lg-rs988-firmwares/
I was only able to find the USA RSS 11C firmware until I found the page linked above with the BPT 10D firmware. Whenever you flash the stock 11C USA firmware the RAC program comes back and once connected to the net will lock your device, however if you use LGUP and uppercut to flash the BPT 10D firmware using the upgrade option (refurbish will error out) I found that my device booted correctly and seemed to work, however I did not have any fastboot options and it said there were no updates available (you need fastboot to unlock the bootloader and the latest update grants that ability). I then reinstalled the USA 11C firmware and to my delight found that the RAC software and device administrator profile were gone.
I then checked for updates and it started download the latest update. I believe I will not have a problem unlocking the bootloader and rooting from this point on. I'll let you guys know if anything changes.
I'm only posting this because I have been sitting on a RAC locked phone for months that got locked over six months after I bought it used and really hope this can help someone else that got screwed over.
Bought my phone almost a year ago off ebay woke up yesterday to this RAC device lock. This worked for me thanks.
Well done..
This happened to me after buying a device off of ebay.. thankfully RAC lock happened within a couple of days and I was able to use the ebay return policy.. I'm gonna pass this on to the dude who sold it to me as he got conned as well.. I verified the original RAC owner with RAC.. the device was purchased in Puerto Rico..
Cheers!
I'm trying to do same with V20 (us996) , but there is only one firmware avaliable :| no older or newer firmwares
Nothing seemed to happened after I tried to flash back to stock using either file. Do you know what I might have done wrong?
EDIT: It works now. Not sure what happened buy after my 7th attempt, the flash went smoothly and I was able to follows inaudible101 instruction to remove RAC lock. Thanks for the help!
inaudible101 said:
Hello,
I hope this post is not against the rules, but I believe I found out how to remove the Rent a Center tracking and locking software that I believe if from computrace that is installed on our devices. It acts like a root kit that automatically reinstalls itself and has a device administrator profile that you can not remove.
I think I figured out how to get rid of the RAC (rent a center) lock for good. The rac lock uses a system administrator profile along with a program called sec.abt that can not be removed or frozen. If you manage to uninstall it is just reinstalls itself. I was not able to find any information on how to remove this without using special hardware like an octopus box that costs hundreds of dollars.
I used LGUP with the uppercut modification (can be found here on XDA) along with the KDZ files from here https://lg-firmwares.com/lg-rs988-firmwares/
I was only able to find the USA RSS 11C firmware until I found the page linked above with the BPT 10D firmware. Whenever you flash the stock 11C USA firmware the RAC program comes back and once connected to the net will lock your device, however if you use LGUP and uppercut to flash the BPT 10D firmware using the upgrade option (refurbish will error out) I found that my device booted correctly and seemed to work, however I did not have any fastboot options and it said there were no updates available (you need fastboot to unlock the bootloader and the latest update grants that ability). I then reinstalled the USA 11C firmware and to my delight found that the RAC software and device administrator profile were gone.
I then checked for updates and it started download the latest update. I believe I will not have a problem unlocking the bootloader and rooting from this point on. I'll let you guys know if anything changes.
I'm only posting this because I have been sitting on a RAC locked phone for months that got locked over six months after I bought it used and really hope this can help someone else that got screwed over.
Click to expand...
Click to collapse
Hey bro, thanks for the input.
I know you're talking about LG G5 but Im exactly in the same situtation for an LG V20 us996(Unlocked version), I have kinda tried this but didnt work. Do you have any advice or any other thing to consider you could tell me so I try on my phne? I cant access the phone to activate usb debugging nor oem unlock
Thanks man!
I got USB debugging to turn on, but the settings close everytime I try to turn on the oem unlocking.
Sent from my LG-US996 using Tapatalk
ThaHaloMilitia said:
I got USB debugging to turn on, but the settings close everytime I try to turn on the oem unlocking.
Click to expand...
Click to collapse
If you go into safe mode you can turn on USB debug as well as enable OEM unlock. You can normally get into safe mode by holding power button like your going to shut it off only hold the power off till a screen pops up. Select turn on and phone will reboot into safe mode.

KG Prenormal

I have an s8 that I have always used with android 8, magisk and rmm state.
When version 9 came out I tried the same procedure and it worked very well, I installed twrp, etc, after updating all Google app and reboot it presents the message "only official realease binaries are allowed to be flashed" and in download mode it accuses KG Prenormal.
In summary is there a way to have root on the S8 with Android 9?
Well I read almost every post back and I could not reach a consensus.
Someone?
up.
costafabiof said:
I have an s8 that I have always used with android 8, magisk and rmm state.
When version 9 came out I tried the same procedure and it worked very well, I installed twrp, etc, after updating all Google app and reboot it presents the message "only official realease binaries are allowed to be flashed" and in download mode it accuses KG Prenormal.
In summary is there a way to have root on the S8 with Android 9?
Well I read almost every post back and I could not reach a consensus.
Click to expand...
Click to collapse
Yes you still can. I had RMM state prenormal and kg state prenotmal when ii flashed pie on my S8.
For me to be able to install twrp,root and xposed I had to get the
Kgstate = checking
Rmm state = normal ( in my case disappeared from download mode )
While I didn't use the method provided in the link below but due to work commitments over the last few weeks I haven't had time to re-try the method I used as I like to test a few times first as it may have been a fluke. I have an S9 with the same.issue to try on. The process took me about 15 - 20 minutes to do after a lot of trail and error.
Currently for my region the latest security patch is feb. which is the version I used to root the phone.
The issue with the new kgstate is still being looked at. The link below has more info and a another possible short term work around.
https://forum.xda-developers.com/sa...ot-install-twrp-samsung-t3747535/post78966561
spawnlives said:
Yes you still can. I had RMM state prenormal and kg state prenotmal when ii flashed pie on my S8.
For me to be able to install twrp,root and xposed I had to get the
Kgstate = checking
Rmm state = normal ( in my case disappeared from download mode )
While I didn't use the method provided in the link below but due to work commitments over the last few weeks I haven't had time to re-try the method I used as I like to test a few times first as it may have been a fluke. I have an S9 with the same.issue to try on. The process took me about 15 - 20 minutes to do after a lot of trail and error.
Currently for my region the latest security patch is feb. which is the version I used to root the phone.
The issue with the new kgstate is still being looked at. The link below has more info and a another possible short term work around.
https://forum.xda-developers.com/sa...ot-install-twrp-samsung-t3747535/post78966561
Click to expand...
Click to collapse
I just got it to work. I'm just testing the procedure again to make sure and put it here.
I arranged this item like this.
In Android 9, installing TWRP soon after installing Android no longer works, after installing TWRP, it appears in red "only official realease binaries are allowed to be flashed" and restarting in the download mode appears KG STATE PRENORMAL.
To fix I installed Android 9 again without the TWRP, Magisk, etc, that is, pure. I entered the system and started the updates by Google, when I came back to check in download mode KG STATE was with CHECKING which is normal.
With this I returned everything to normal, I installed TWRP, Magisk, etc. and I continued.
spawnlives said:
Yes you still can. I had RMM state prenormal and kg state prenotmal when ii flashed pie on my S8.
For me to be able to install twrp,root and xposed I had to get the
Kgstate = checking
Rmm state = normal ( in my case disappeared from download mode )
While I didn't use the method provided in the link below but due to work commitments over the last few weeks I haven't had time to re-try the method I used as I like to test a few times first as it may have been a fluke. I have an S9 with the same.issue to try on. The process took me about 15 - 20 minutes to do after a lot of trail and error.
Currently for my region the latest security patch is feb. which is the version I used to root the phone.
The issue with the new kgstate is still being looked at. The link below has more info and a another possible short term work around.
https://forum.xda-developers.com/sa...ot-install-twrp-samsung-t3747535/post78966561
Click to expand...
Click to collapse
Do you mind sharing how you did it?
I had my bootloader unlocked and flashed TWRP successfully while on Android 9.0. My phone had a fit so I flashed stock firmware. Turns out my it was actually my mobile provider who had issues, not my phone. Also had to do a factory reset to get back my full 64 GB storage. Somewhere along the line my RMM_State tripped to prenormal. I think KG_State did too. I was fine to wait 7 days, which I did (over 8 days uptime). RMM_state is still prenormal. KG_State does not appear.
I'm wondering if it has anything to do with the fact that my original firmware was region XSA, and I've ended up on VAU (because I'm with Vodafone, though I bought the phone outright from the shops). So my firmware region is XSA, while my Carrier_ID (in download mode) shows up as XSA. Do these regions have to match?
I'd appreciate any advice on removing the prenormal state, even if it involves waiting. Maybe involving flashing an older bootloader? I've done a tonne of searching, and I'm finding it hard to find information that is relevant or likely to work on Pie. Cheers.
DSMB said:
Do you mind sharing how you did it?
I had my bootloader unlocked and flashed TWRP successfully while on Android 9.0. My phone had a fit so I flashed stock firmware. Turns out my it was actually my mobile provider who had issues, not my phone. Also had to do a factory reset to get back my full 64 GB storage. Somewhere along the line my RMM_State tripped to prenormal. I think KG_State did too. I was fine to wait 7 days, which I did (over 8 days uptime). RMM_state is still prenormal. KG_State does not appear.
I'm wondering if it has anything to do with the fact that my original firmware was region XSA, and I've ended up on VAU (because I'm with Vodafone, though I bought the phone outright from the shops). So my firmware region is XSA, while my Carrier_ID (in download mode) shows up as XSA. Do these regions have to match?
I'd appreciate any advice on removing the prenormal state, even if it involves waiting. Maybe involving flashing an older bootloader? I've done a tonne of searching, and I'm finding it hard to find information that is relevant or likely to work on Pie. Cheers.
Click to expand...
Click to collapse
Have a look here
https://forum.xda-developers.com/sa...ot-install-twrp-samsung-t3747535/post79745844

Need help downgrading stock Oreo to MM or Nougat (with locked bootloader)

Edit: I worked out my issues, I'll leave this here in case others have similar trouble:
I needed to manually add in the RAW F53XX files from the github (https://github.com/Androxyde/devices/tree/master/F53XX), this allowed Flashtool to correctly detect the type of phone and apply the fsc. I was then able to flash my desired firmware, I chose the 6.0.1 release for Journalists to begin with as a test. This confirmed my suspicion that it was a software update issue causing the proximity sensor to malfunction (stuck on) and also fixed up the FACTORY STARTUP SERVICE-POWER OFF bug and the Warrantytimeservice permanent notification. I can now look at updating to later versions of Android and find the latest version before I have issues again.
---
tl;dr - I need a guide that actually works on downgrading the F5321 to a specific stock Android version with a locked bootloader.
I recently received a new, old stock version of the X Compact (F5321) that appears to be a HK variant as it started up with the Chinese language selected.
It was initially stock Android 6.0.1 with no apparent problems. After OTA updating all the way through to 7.1.x and onward to the latest 8.0, I now receive the "FACTORY STARTUP SERVICE" problem. Even if I'm quick enough to disable the service for the service flag, the proximity sensor does not work as well after updating, making phone calls impossible. I believe the issue is all related to software, not hardware. I want to downgrade to 6.x and go from there before I have to send it back for another replacement.
I'm having trouble with getting Flashtool to correctly detect and identify the firmware files that I want to flash. I want a completely stock version of Android, so keeping the bootloader locked is fine for me.
After downloading the firmware that I want to try, XperiFirm will close and Flashtool will successfully build the FTF. After clicking the lightning bolt > flashmode > the firmware list is blank.
I'm using Flashtool 0.9.26 (I have tried older versions as well with the same problems) with driver signature enforcement disabled and correct drivers installed to detect the phone.
The last time I used Flashtool was to flash my older Z5 Compact, I didn't have any issues then and it was all done within 10 minutes. I've already spent more than 5 hours on this phone and would appreciate any help.
I seem to have the exact same problem with a Hong Kong-sourced X Compact. I am familiar with Flashtool, and have used it for basic flashing of firmware. This time, however, I am experiencing the dreaded "FACTORY STARTUP SERVICE" problem. Was wondering if Flashtool could be used to circumvent the problem. I simply want the USA Android 8.0 firmware on the phone. I am not familiar with the various options that Flashtool offers. I note that you mention a specific script(?) that can be installed. Do you have any advice? Thanks
pseudonym58 said:
I seem to have the exact same problem with a Hong Kong-sourced X Compact. I am familiar with Flashtool, and have used it for basic flashing of firmware. This time, however, I am experiencing the dreaded "FACTORY STARTUP SERVICE" problem. Was wondering if Flashtool could be used to circumvent the problem. I simply want the USA Android 8.0 firmware on the phone. I am not familiar with the various options that Flashtool offers. I note that you mention a specific script(?) that can be installed. Do you have any advice? Thanks
Click to expand...
Click to collapse
The "FACTORY STARTUP SERVICE" and to a lesser extent, "Warrantytimeservice" problems surface only in the later version of Android. The only way I could remove them was by staying on 6.0.x only. Anything higher, and the problems show up again. It seems to be a byproduct of upgrading the HK variant that wasn't designed to actually be software upgraded - you won't be able to have the US 8.x firmware on the phone.
Sorry to say, but you'll be stuck on 6.0.x if you want a usable phone. I should mention that I was never able to maintain a newer firmware on that particular phone.
I've since sent the Compact X back (it was meant to be a gift) and replaced it with a Samsung A20.
h
I'm using SO-O2J and a sim card not docomo. Use the "Repair" in Xperia Companion and it auto flash Android 7.0
..
PioneerSeeker said:
Try different region's roms on www.xperiablog.net and I hope you'll be successful to find nougat or oreo at last for your phone.
Remember xperia devices do not need to unlock bootloader for downgrade...
Click to expand...
Click to collapse
Thanks; I was able to obtain an X Compact originally for the UK market, and was able to successfully flash the US Oreo firmware. All seems to be in order.

Help: My LG H990 DS only enters Fastboot and now the device changes to US996

Hi, I get a notification to update magisk. then I update it and use the recommended action to update it. After that it asks me to reboot the device. After rebooting the device it goes to fastboot only. And I see the device now changes to US996 while what I have is H990DS.
Can someone explain to me what's wrong and how to fix it without losing all my data?
thanks...
Hi there,
all I can say is that is happened exactly the same to me just some minutes ago, I installed latest magisk update like I've been doing with no problems, just that today, after reset, its always booting stuck into fastboot mode.
I have a H910 and I also see the message about US996, maybe this is related to the method used to root the phone, If I recall correctly it had something to do with installing a US996 modified bootloader.
I still haven't found a way to get my phone back to life. All I can say is that I do manage to boot into recovery (TWRP, via the appropriate key combination at power on), so I guess I'll manage to flash something to fix this and return it back to life I hope
aliks00 said:
Hi there,
all I can say is that is happened exactly the same to me just some minutes ago, I installed latest magisk update like I've been doing with no problems, just that today, after reset, its always booting stuck into fastboot mode.
I have a H910 and I also see the message about US996, maybe this is related to the method used to root the phone, If I recall correctly it had something to do with installing a US996 modified bootloader.
I still haven't found a way to get my phone back to life. All I can say is that I do manage to boot into recovery (TWRP, via the appropriate key combination at power on), so I guess I'll manage to flash something to fix this and return it back to life I hope
Click to expand...
Click to collapse
It's common knowledge that if you root your phone you never apply an OTA
Sent from my LG-H910 using XDA Labs
cnjax said:
It's common knowledge that if you root your phone you never apply an OTA
Click to expand...
Click to collapse
Thanks, but who said I ever applied an OTA? It was magisk that wanted to update itself, I've been performing magisk updates regularly for quite some time and never had a problem, in fact I can't even perform an OTA phone update as I have AT&T variant but with a different sim...
Other times, when updating magisk, I lost root but never lost the ability to boot...
I was running alpha-omega oreo with mk2000 kernel and updating rom, kernel and magisk regularly through TWRP (or direct install in case of magisk though magisk app) and never had this problem before... at least I can manage to boot from recovery/TWRP so hopefully I will soon manage to get things working again... that is, if I can copy some images to my SD card that windows insists that is corrupted but that's another story...
I ended up flashing whole rom again and everything is back to normal

US997 US Cellular/BRIGHTPOINT Bootloader Unlock Solution??

OK so I need some help...
When I originally purchased my LG G6 in June of 2019, I made sure it was a US997 model, but I ended up getting a BRIGHTPOINT version during my purchase. I went through the website to check the imei and the device ID and it gave me the not unlockable status.
After that, I went and decided to update the software manually to US99721e since it wouldn't OTA it and have been on that ever since. Now, I just recently tried while on the 21e software and I was given an unlock.bin code!
So if someone could help me out:
IF you're on a US997 BRIGHTPOINT G6:
-Download LG UP and UpperCut
-Download US997_21e_01_0211-UCL.kdz at lg-firmwares.com (this is the one I'm on, try this one first!)
-Once it's done, enable developer mode, adb debugging, and OEM unlock
-Go through the unlocking process
Please let me know what you find out!!
Is that only for us cellular?
Sent from my V60 ThinQ using XDA Labs
I have a brightpoint LG G6, which I bought as the seller claimed it was an unlocked US997, failing to share it was a OEM phone. I don't understand how this works please can you clarify? I tried the unlocking process and I have to supply my phone information to LG. Their database says it is a brightwell phone and so they won't release the unlock. Are you saying that after installing this ROM I don't need the key from LG to unlock the bootloader?
I have installed Uppercut and LGUP (1.14 as newer versions don't seem to work). I downloaded the ROM and I have the LGUP loaded. It shows the phone using US99721a. I have 4 process options, Refurbish, Upgrade, FOTA upgrade or Phonesettings which is the one to use?
It works! At least I obtained an unlock.bin file from LG. I need to work out which is the best LG G6 US997 ROM and how to load it when my SD card doesn't work. Any help or pointers to useful information much appreciated. For anyone else trying this here is what I found. I downloaded the LG windows drivers and LGUP 1.14 (There are newer versions but these don't work with uppercut. I downloaded Uppercut from XDA website and then you run Uppercut not LGUP. This immediately caused my virus checked to block it as it contains a trojan. I didn't like that but googled to find others had the same issue. There seems to be a way to load the correct file to get LGUP to work directly and I would recommend researching that but I disabled the virus software and proceeded. I used the UPGRADE option in LGUP - you need to reboot your phone into download mode. To do so, disconnect USB cable then Power off the phone completely. Now hold Volume Up then plug in USB cable at the same time. Make sure that LGUP is NOT running when you connect the USB cable and start it once you are in download mode. It loads the ROM very quickly and takes a bit longer to reboot and then it needs time to upgrade android as you have a 6 months newer version of Android 8. Then follow direction on the LG unlock site https://developer.lge.com/resource/mobile/RetrieveBootloader.dev. You will need to install ADK https://developer.android.com/studio/releases/platform-tools unzip after you download. LG emailed my unlock code immediately.
Yes, I can confirm that it works with the US997 model now. I already was at version US99721e so I didn't have to jump through the hoops to load this version. I went through the steps to unlock the bootloader via the LG developer website and voila, got sent the unlock.bin file, too.
Now I am pretty sure that I tried that in past perhaps 1-2 years ago and it didn't work, so perhaps LG has secretly flipped a few bits in their database to allow unlocking for these not quite brand new devices.
I just applied the unlock.bin and got the "cannot check for corruption" warning on the boot screen. So this is working - fantastic!
Now have to restore my device from the LG Backup I made before and put on the SD card.
I had tried the unlock last year but I didn't retry before I updated so it may have worked anyway and the update of the ROM wasn't needed. I unlocked the phone and installed Sky Hawk recovery but when that starts it asks for a deception password and nothing I have tried works. I'm not sure if that is a real issue or I can continue safely with flashing a new ROM. Has anyone worked through this issue?
challenger07 said:
I had tried the unlock last year but I didn't retry before I updated so it may have worked anyway and the update of the ROM wasn't needed. I unlocked the phone and installed Sky Hawk recovery but when that starts it asks for a deception password and nothing I have tried works. I'm not sure if that is a real issue or I can continue safely with flashing a new ROM. Has anyone worked through this issue?
Click to expand...
Click to collapse
First, when you're in Adroid remove all screen lock mechanisms, you can re-enable it later.
Enable USB debugging, do adb reboot bootloader and fastboot flash recovery with this recovery instead (rel_o2):
https://forum.xda-developers.com/lg-g6/development/recovery-twrp-3-2-1-unofficial-fixes-t3722199
Do the button combo to launch recovery. If you're in recovery, first reformat /data (you have to enter "yes") to get rid of encrption and after that flash the anti-root removal tool mentioned in the post. Then reboot into recovery and then flash Magisk and/or your ROM of choice. Note that I have only used this with stock ROM and Magisk and not tried any custom ROMs, but the thread has plenty of people having also tried other ROMs.
How do you even know if you have a Brightpoint device?
I found out when I tried to unlock. http://mobile.developer.lge.com/
Thanks for the info. I'll dig into this once I know for sure that a version of Android 10 is available to load into the phone.
What I've been dealing with so far keeps asking for a 15 digit IMEI number. My phone only has a 14 digit value.
I pulled box (yes I kept it) and discovered that the IMEI is 15 digits. No idea why the value is the phone truncates the last digit. The site that checks IMEI numbers says that it is the platinum edition: US997PL. Gee, the box says that.

Categories

Resources