LGv20 - cannot boot into bootloader, having carrier swap issues, please review - LG V20 Questions & Answers

SO, this is a unique problem, The internet has been able to
assist me in fidning an answer, I see nobody else with this issue.
primary problem: Phone needs to move from sprint to cricket
obstacles: Phone is a lease device.
*at this point I decided what I need to do is root the phone so
I can edit the build prop.
Current problem: seems as though the commands through usb are halfway ignored.
adb reboot bootloader - just reboots phone
adb reboot fastboot - same as above
adb reboot recovery - reboots phone into recovery.
Why is my reboot into bootloader not working?
OEM unlock is [on]
USB debugging is [on]

Stock sprint does not have access to bootloader/fastboot.

williamschromebook said:
SO, this is a unique problem, The internet has been able to
assist me in fidning an answer, I see nobody else with this issue.
primary problem: Phone needs to move from sprint to cricket
obstacles: Phone is a lease device.
*at this point I decided what I need to do is root the phone so
I can edit the build prop.
Current problem: seems as though the commands through usb are halfway ignored.
adb reboot bootloader - just reboots phone
adb reboot fastboot - same as above
adb reboot recovery - reboots phone into recovery.
Why is my reboot into bootloader not working?
OEM unlock is [on]
USB debugging is [on]
Click to expand...
Click to collapse
So what version of software are you on? ZV6?
---------- Post added at 10:29 AM ---------- Previous post was at 10:26 AM ----------
and to be honest, the phone being leased will restrict cricket from being able to add the device to their system, the ESN aka serial number will be black listed until the device is in paid off status and released by sprint. There will be 0 discussion on how to circumvent this as its illegal. Rooting the sprint variant LS997 has been covered in extent in the forums. Look for DIRTY SANTA ROOT AND UNLOCK. If you have updated to latest software release and are not already rooted ur screwed as ZV6 will block dirty santa from being able to root ur device.

Related

Update : Possible to enable OEM Lock via ODIN or ADB ?

# Update ##
USB Debug works great
Possible to enable OEM Lock via ODIN or ADB ?
Everything is blocked by FRP Lock
######
Hi all,
Regarding s6 edge plus, I have a SM-G928I, is it possible to enable usb debugging without going into developer options ? A friend bought a second hand phone and its locked to an account unfortunately, and ODIN wont connect so ican root/reflash due to im assuming the usb debugging not being enabled.
I'm trying to save him some money by paying a repair shop >.< any tips?
Thanks
Anyone?
They sure are nice phones, the screen real estate vs my HTC one m9 is certainly noticeable
Did you install Samsung USB drivers and plugged phone in download mode? Can try also going to recovery and performing factory reset
Have installed samsung drivers, i can see the phone on the PC as a drive to load data to, but odin doesn't see it.
Factory reset seems to still have the account linked, a security feature of 5.1 i'm sure.
I'm getting a copy of the stock rom from sammobile
http://www.sammobile.com/firmwares/database/SM-G928I/
fingers crossed i can use this and it recognises it if i just replace the stock file
can it be forced via adb?
Okay so turns out i'm thinking of the wrong thing. USB Debug works., great can interface via ODIN and ADB.
Is it possible to enable "OEM Unlock' via command line interface of adb, or ODIN ? without access to the OS this is making life hard
Flash stock firmware. You need to flash stock firmware to access the OS and then enable OEM Unlock. There is no other way. You cannot charge it even without enabling it.
AFTER ROOTING MAKE SURE NOT TO DISABLE OEM UNLOCK.
I tried that, flashed stock firmware from sammob but it still wants the sellers Gmail account has he bought a brick?
Do a factory reset after ODIN flash. Flash TWRP, access recovery, format system, cache and data (including internal) and then check.
thanks, will update soon
Stock firmware flash works
Factory reset / cache clear works
Flashing TWRP fails due to FRP lock , due to the OEM Unlock not being enabled im assuming
"Custom Binary(RECOVERY) Blocked by FRP Lock"
I'm sorry but I think you are locked out of the phone.
It certainly seems that way. its always frustrating as a geek to be defeated
AK1149 said:
Do a factory reset after ODIN flash. Flash TWRP, access recovery, format system, cache and data (including internal) and then check.
Click to expand...
Click to collapse
The stupid practice
---------- Post added at 06:18 AM ---------- Previous post was at 06:11 AM ----------
ReaperZ said:
It certainly seems that way. its always frustrating as a geek to be defeated
Click to expand...
Click to collapse
If your mobile phone flash after the official firmware Able to enter the activation page
So you can contact me, I can help you remove OEM-FRP LOCK
china chenli said:
If your mobile phone flash after the official firmware Able to enter the activation page
So you can contact me, I can help you remove OEM-FRP LOCK
Click to expand...
Click to collapse
PM'd
so china chenli wants remote access to my PC ... no thanks !
any other clever ideas ?
ReaperZ said:
so china chenli wants remote access to my PC ... no thanks !
any other clever ideas ?
Click to expand...
Click to collapse
Hi, I've bought a phone with same condition.
Have you solved the problem?
Sure have, I obtained a file which allows you into the settings from the Google lock screen which allows you to enable OEM unlock. Due to the legalities though I'm not sure it's allowed to share this here though
can you please post/send me this file ? and instructions, i assume you flash it via Odin/adb
ReaperZ said:
Sure have, I obtained a file which allows you into the settings from the Google lock screen which allows you to enable OEM unlock. Due to the legalities though I'm not sure it's allowed to share this here though
Click to expand...
Click to collapse
Hi, I'm facing the same situation, can you send me the procedure and file you followed to enable the oem unlock?
regards
Giuseppe

Samsung Galaxy SM-J120W Google Account FRP Bypass Removal HELP!!

Hello
Having a real tough time with this one.
Issue: Samsung Galaxy SM-J120W - Stuck in FRP. Can not sign into a google account. Phone is not rooted.
Does anyone have a walk-through solution for this specific device?
Any assistance is much appreciated
Thank You
Samsung J120W FRP fix
I had the same issue. I fixed with odin and a download of the phones stock firm ware. I put the firmware .tar in the CSC section in Odin
i'm having issues with bypassing... does the odin method still work? could swear i tried it... what version rom should i download?
vibespredah said:
i'm having issues with bypassing... does the odin method still work? could swear i tried it... what version rom should i download?
Click to expand...
Click to collapse
Any luck?
I'm dealing with the same scenario. I've researched a bit and found many instructions impossible to execute.
Plenty of the methods that are supposed to work seem contorted and overly complicated.
I'm scratching my head, wondering why it isn't a straightforward process involving flashing from download mode.
It's just gotta be that simple. As it is the unit I'm dealing with won't recognize from adb, so I'm limited.
IMO the info pointing to a solution is somewhere in a sea of malware and ad-laden apps and sites, now that having a custom ROM is more commonplace with the non-programmer end-user.
You can use Miracle Box. It can bypass FRP but if you want use this program, you must have a Miracle Box dongle.
yes odin method does still work but dont forget you need to do each step in the correct order and if it doesn't work and you try again you must CLOSE odin, unplug the phone then re-start odin and do the steps again
---------- Post added at 11:50 PM ---------- Previous post was at 11:35 PM ----------
vibespredah said:
i'm having issues with bypassing... does the odin method still work? could swear i tried it... what version rom should i download?
Click to expand...
Click to collapse
it does still work but dont forget if you try and fail and want to try again you must close odin, unplug your phone and then re-start odin and follow the steps.
as for what version you need to download that would depend on your carrier - that said - i downloaded and flashed the one for rogers canada and it worked even though im with chatr so the carrier may not matter so much? here are a couple of the canadian versions you can look for
Canada rogers - J120WVLU1APC8 - RWC
Canada Sasktel - J120WVLU1APC8 - BWA
Canada Telus - J120WVLU1APC8 - TLS
help
i have this same problem if anyone can help me i would really appreciate it i have a samsung j120w with chatr so i believe its the telus firmware i need
found a couple threads and thanks to this site i am confident i will be able to unlock this device using odin or twrp or a combination of the two im not sure i will follow the instructions and repost here i see the key to skipping the frp is On your phone, Open Settings > Developer options > Enable OEM unlock and Enable USB debugging.
hopefully this will go smooth thanks to all of you
i cannot access the phones menus as it is stuck at the 'enter your previous email screen'
cannot access the phones internal memory so i cannot put twrp on there. in recovery mode it wont access the sd card i tried placing it there as well. sending it with adb gets a blocked custom binary by frp lock error.
any help would be appreciated i spent 7 hours on this last night and got nowhere
I think the easiest way is to enable Settings >Developer Options > Enable the option OEM Unlock. This will allow the device to be OEM unlocked.
How to enable Developer Options:
Got to Settings > About Device > Software Info > and tap on Build Number 5 times, it unlocks the Developers options..
arvinderss said:
I think the easiest way is to enable Settings >Developer Options > Enable the option OEM Unlock. This will allow the device to be OEM unlocked.
How to enable Developer Options:
Got to Settings > About Device > Software Info > and tap on Build Number 5 times, it unlocks the Developers options..
Click to expand...
Click to collapse
i am stuck at the google frp lock i cannot get into the phone any other suggestions?
Can we resurrect this coffin or should I start another thread?
I need to bypass FRP. Not familiar with android whatsoever but was able to fumble through ODIN flashes unsuccessfully. (Got PASS but FRP is still there).

Trying to enable WiFi Calling on my Note 4 N910V

I have a Galaxy Note 4 SM-N910V that I successfully rooted a couple of years ago. I played it safe and installed the stock ROM per the instructions, N910VVRU2BPA1_N910VVZW2BPA1_VZW [5.1.1 Stock FW]. I also have TWRP installed. The issue I'm having now is I'm working in a building that I get no service whatsoever, except at the front door. It's terrible, but someone told me I should use WiFi calling, since we have WiFi throughout the building. He had me all pumped up until I realized I didn't have the option for WiFi calling on my Note 4. After researching it, I believe you must have at least Android 6.0.1 (Marshmallow).
Can someone confirm this or tell me what I need to do so I can enable this wonderful feature called WiFi calling on my phone? This would be a godsend for me. I've been told that since I have TWRP installed I can pretty much install and test any roms, but I've been afraid to because I figured there has to be more to it than that.
Thank you!
Modify_inc said:
I have a Galaxy Note 4 SM-N910V that I successfully rooted a couple of years ago. I played it safe and installed the stock ROM per the instructions, N910VVRU2BPA1_N910VVZW2BPA1_VZW [5.1.1 Stock FW]. I also have TWRP installed. The issue I'm having now is I'm working in a building that I get no service whatsoever, except at the front door. It's terrible, but someone told me I should use WiFi calling, since we have WiFi throughout the building. He had me all pumped up until I realized I didn't have the option for WiFi calling on my Note 4. After researching it, I believe you must have at least Android 6.0.1 (Marshmallow).
Can someone confirm this or tell me what I need to do so I can enable this wonderful feature called WiFi calling on my phone? This would be a godsend for me. I've been told that since I have TWRP installed I can pretty much install and test any roms, but I've been afraid to because I figured there has to be more to it than that.
Thank you!
Click to expand...
Click to collapse
I'm almost certain that is a marshmallow feature. If you can see the option but it's grayed out and you can't turn it on then there's a fix for that. Otherwise you would need to upgrade to 6.0.1 and you'll have to go through the bootloader unlock method with a 6.0.1 bootloader is the only obstacle. If you don't update the bootloader your wifi won't work with the 6.0.1 roms.
Use this link for a guide to unlock your bootloader.
If you see the option but it's grayed out then follow this guide.
kevintm78 said:
I'm almost certain that is a marshmallow feature. If you can see the option but it's grayed out and you can't turn it on then there's a fix for that. Otherwise you would need to upgrade to 6.0.1 and you'll have to go through the bootloader unlock method with a 6.0.1 bootloader is the only obstacle. If you don't update the bootloader your wifi won't work with the 6.0.1 roms.
Use this link for a guide to unlock your bootloader.
If you see the option but it's grayed out then follow this guide.
Click to expand...
Click to collapse
Thank you for the reply and the link! I wish it were only greyed, but no, I do not have the option at all.
Regarding the bootloader, the link you provided shows in the title that it is for N910VVRU2CQI2, but I have N910VVRU2BPA1. I did originally have N910VVRU2CQI2, but to root my phone, I was told to flash the N910VVRU2BPA1_N910VVZW2BPA1_VZW [5.1.1 Stock FW] ROM to my phone.
Will I need to revert back to N910VVRU2CQI2 or can I still follow the instructions to unlock the bootloader with my current N910VVRU2BPA1 baseband version?
Thank you, again!
Modify_inc said:
Thank you for the reply and the link! I wish it were only greyed, but no, I do not have the option at all.
Regarding the bootloader, the link you provided shows in the title that it is for N910VVRU2CQI2, but I have N910VVRU2BPA1. I did originally have N910VVRU2CQI2, but to root my phone, I was told to flash the N910VVRU2BPA1_N910VVZW2BPA1_VZW [5.1.1 Stock FW] ROM to my phone.
Will I need to revert back to N910VVRU2CQI2 or can I still follow the instructions to unlock the bootloader with my current N910VVRU2BPA1 baseband version?
Thank you, again!
Click to expand...
Click to collapse
No you're already at the right starting point. Just start at the step where you flash the combination firmware of BPA1_CPD1. After that the process is the same as @ryanbg posted in the original unlock method.
If you want, these are the steps I did:
1. Power down, pull the battery for 3 seconds, then boot into Download Mode
2. Using Odin, flash the BPA1\CPD1 hybrid firmware
3. Once that's done flashing reboot to recovery and factory reset. Then reboot and let that firmware install
4. Once you've gotten past all the setup part you'll want to power off again and boot to download mode again
5. Using Odin, flash the CQI2 aboot and then reboot. From this point on the process is the same as before.
6. Enable developer options, turn on USB debugging and turn on "allow unknown sources" in the security settings.
7. At this point, you'll want to have your spare SD card in and go ahead and open a command window from the same location that you have the samsung_unlock_n4-fix file in. In my case it was in my download folder and the easiest way to do that is to open that window, hold down the shift button, then right click. You should see an option that says "open command window here" then click that to open.
8. Once you open the terminal enter this command: adb devices
9. Then this command: adb push samsung_unlock_n4-fix /data/local/tmp/
10. Then install kingroot and let it start rooting. Be sure to keep the terminal open and your phone connected.
11. Once kingroot starts the rooting process do not let the phone go to sleep. Just keep a finger on the screen.
12. When kingroot gets past 50 -60 percent, enter this command in the terminal: adb shell
13. If you enter adb shell and it gives an error or says your offline, just unplug the Usb from your phone and plug it right back in. Then enter the adb shell command
14. As soon as kingroot says you're rooted, enter this command in the terminal: su (You have to grant root permission on the phone and continue)
15. Then this command: cd /data/local/tmp/
16. Then this command: chmod 777 samsung_unlock_n4-fix
17. Then this command: ./samsung_unlock_n4-fix
18. Once the scripts starts it will ask you if you want to continue, just type out: yes
Then it will do it's thing, back up your bootloader, and then power your phone down when it's done.
19. Once powered down, PULL OUT YOUR SD CARD, and boot back into Download Mode
20. Using Odin, flash Twrp and immediately boot into recovery when Odin reboots your phone.
kevintm78 said:
No you're already at the right starting point. Just start at the step where you flash the combination firmware of BPA1_CPD1. After that the process is the same as @ryanbg posted in the original unlock method.
If you want, these are the steps I did:
Click to expand...
Click to collapse
Thanks for all your help, I finally got around to upgrading it. Everything went smooth and I am finally running MM 6.0.1 but unfortunately, I still can't find the feature for Wi-Fi Calling. I do now have a Advanced Calling option under Settings, which I believe you must have to use WiFi Calling, but I can't find the WiFi Calling anywhere to enable it. I must say, I'm really disappointed, yet still proud of myself that I didn't brick my phone in the upgrade process.
So, any suggestions as to why I can't find WiFi Calling on MM 6.0.1?
So no one has any ideas why I would still not have the wifi calling after installing the 6.0.1 MM? Is there a security or other update that I now need to install to get this feature? I installed the Jasmine v6 rom, if that makes any difference. Is there a way I can install 7.0 Nougat on this device, and would it likely provide the wifi calling feature or likely be a waste of time and effort?
I'm using Safelink with my Verizon phone, but they are no help, though they do say they support wifi calling as long as I can enable it on the phone. Is it possible Verizon could tell me what I need even though I don't have service with them but do use their towers?
Sorry for so many questions, I just really need wifi calling and can't understand why I don't have the option for it using 6.0.1.
I found an app named WiFi Calling while browsing through my phone directory. It looks like a system file, so shouldn't that mean the phone should have it? Is my Jasmine ROM keeping it from working or is it likely something else?
I'm now using Jasmine v7, if that makes any difference.
Help! Now my wife has no phone
kevintm78 said:
No you're already at the right starting point. Just start at the step where you flash the combination firmware of BPA1_CPD1. After that the process is the same as @ryanbg posted in the original unlock method.
Click to expand...
Click to collapse
I tried to do the same for my wife since she has the same exact phone running 5.1.1 with root. Everything appeared to be going fine, but after performing the last step (flashing the N910VVRU2CQL1_PartialFirmware_DevEd.tar.md5.7z via Odin) and rebooting the phone, it now goes into a boot loop. It will load the Samsung logo for about 20-30 seconds, then reboot every time. I can still access TWRP from recovery and I have cleared Dalvik and Cache, but it still does the same thing. I also reflashed JasmineROM_v7.0_N910VVRU2CPF3, cleared Dalvik and Cache again, but still the same boot loop. It does still show the word Custom under the Samsung logo at boot, so I assume that is good news. Doesn't that mean the bootloader is still unlocked or something?
If it helps, the part of the process that had me concerned was after unlocking the bootloader. I powered off the phone, and then tried to load the recovery menu so I could factory reset the phone and clear the cache, but the recovery menu never appeared. It did show the Android fix-it guy for the recovery for about 10 seconds then a short progress bar under it for about 5 seconds, then it went straight to the Samsung logo. It never did give me the actual recovery menu, just the Android fix-it guy animation, which I thought was odd because I've always had the recovery menu pop up after that.
I made a complete backup using TWRP before attempting this upgrade. So, can I just restore it or are there other steps I need to perform before I attempt to revert back?
Did you ever get this resolved? I have been having an issue since mid-July where my phone does not send or receive texts or calls within half a mile radius of my office but otherwise works great everywhere else. I don't have to be in the building...I can be standing in the parking lot, parked at a nearby building/area, or driving down the street in vicinity of the area and nothing. When I try to send a text, I get a message stating there's no service. When I try to call, the phone goes from 4G with four bars to 4G with zero bars and is stuck on "dialing". When I end the call, it goes back up to four bars.
I have tried contacting Verizon many times and they tell me I need to enable WiFi calling but I don't have the Advanced Calling option in my settings. I am also running 5.1.1 on a rooted SM-N910V. Today when I spoke to them, they told me that even though my phone shows 4G, I really only had 1G service. I find this explanation ridiculous because if this was the case, I would have problems in other areas too and not just in the middle of the 8th largest urbanized area in Louisiana (while elsewhere in the same urbanized area, the phone works great). They told me I needed to do a system update which will cause me to lose root.

A bunch of questions about rooting SM-G975F/DS

I just got an SM-G975F/DS ~ seems like the Taiwan version.
My current issues:
Can't disable emergency alerts!!!
Can't clear voicemail notification from tray. Infuriating.
No hosts file override (need this for app development & Adaway)
Samsung bloatware
I don't give a f*ck about Knox or Samsung Pay but I like the stock camera so I have a few questions about the root process.
First it seems like this is the process just to have root in with Stock ROM. Please correct me if I'm wrong.
For randoms reading this: THIS WILL NOT WORK ON USA Snapdragon VERSION
Enable OEM Unlock from developer menu.
Boot into download mode (Plug in PC connected USB cable while holding Bixsby Button + Vol Down)
Unlock bootloader by pressing volume up and confirming (not actually unlocked yet due to Samsung trickery)
Quick setup OS with Internet connectivity knowing it's gonna be wiped again.
At this point Samsung's Vaultkeeper service should detect OEM unlock and finally actually unlock the bootloader.
Install Magisk with this guide.
So it seems like this process would patch just the AP partition with Odin while keeping the ROM and Recovery stock.
So here's the questions.
If I continue to run stock ROM with Magisk with this method any official OTA updates must be done manually or I risk bricking the device?
If I install TWRP and try out some roms and don't like them can I go back to stock?
Is it possible to flash stock rom WITHOUT Magisk after doing all this?
I plan on writing some simple guides on this when I'm done since the current ones are a bit confusing so I would appreciate some clear and concise answers the the above questions.
Thanks all!

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