Honestly found it on XDA of all places after looking for it all night
What does 1.16 give us that 1.14 doesn't? Everything honestly. Could not get my Wing recognized to flash with 1.14. No 1.15 Patched exists either
We can downgrade with ChipErase (and restore IMEI), we can modify PDM, we can dump the entire phone (will do tomorrow), can upgrade.
See link here for link: https://forum.xda-developers.com/t/...er-w-fastboot-drivers-and-common_dll.4304181/
This was the only working LGUp_Tool that worked outside of LGUP CMD
I wanted this to try other countries firmware files to see if we get other weird results. This should also allow custom KDZ files? from my understanding
ADDED INFO Nov 8, 2021
How to use LGUp Tool From this Download
1.) Download the LGUp 1.16.03 Patched from the XDA Link above
2.) Run the EXE as admin so it can install Drivers and the software properly
3.) Go to the install directory and run the 2 Bat files that are in the folder as admin
Code:
Default: C:\Program Files(x86)\LG Electronics\LGUp
-- Running LGUP_UI-fixer.bat -- run as admin, follow instructions, run the software when it says to, then close it
-- Run LGUP_UI-Fixer-addon.bat -- run as admin, follow steps, then run LGUp.exe when patch complete
You now have a working LGUP Tool 1.16 Patched for the LG Wing
Explaining the functions of LGUP Tool
Code:
REFURBISH： You will lose all user data（KDZ or TOT）
UPGRADE: Keep data and update your phone（KDZ or TOT) - Select Upgrade to flash kdz firmware to unbrick/restore your phone back to stock.
Chip Erase: Dangerous, This will erase IMEI/efs, do not try this if you do not have a NV backup. - Chip Erase can also remove the Google FRP on many LG devices with Android 5.0, 6.0.
PARTITION DL：Flash the single Partition or selected partitions onto your phone. - This feature can solve “unknown model” issues. This feature can be used to bypass Google FRP by flashing specific tot firmware.
DUMP：Dump all partitions of your phone as backup. - Dump the stock firmware from a working phone as back up and use Partition DL to restore phones.
FOTA Upgrade: This can be used to flash OTA Update file that comes with dot up file extension.
PDM: Change imei, wifi address, bluetooth, mac address
video for how to use LGUP Tool to flash the Wing
Awesome! I just DL'ed.. don't know when I'll have time to mess around with it. Or if I have the skill set to help. But I would definitely try to help out if I can and be excited for rootable firmware.
kaluna00 said:
Awesome! I just DL'ed.. don't know when I'll have time to mess around with it. Or if I have the skill set to help. But I would definitely try to help out if I can and be excited for rootable firmware.
Click to expand...
Click to collapse
I plan on making a video I'll put on the post explaining the tool
KaptinBoxxi said:
I plan on making a video I'll put on the post explaining the tool
Click to expand...
Click to collapse
Holy cow I can’t believe it. You actually found the exact tool that we needed! I went ahead and did a chip erase on my demo model, which had previously been flashed with the Korean firmware from the previous tutorial, and flashed the T-Mobile Firmware. IT WORKED! To get rid of the error at that shows up every time you reboot it, I accessed the hidden menu and changed the TN number to the one associated with TMO_US, as shown in this post.
Thank you!
twocans said:
Holy cow I can’t believe it. You actually found the exact tool that we needed! I went ahead and did a chip erase on my demo model, which had previously been flashed with the Korean firmware from the previous tutorial, and flashed the T-Mobile Firmware. IT WORKED! To get rid of the error at that shows up every time you reboot it, I accessed the hidden menu and changed the TN number to the one associated with TMO_US, as shown in this post.
Thank you!
Click to expand...
Click to collapse
I still can't get mine to accept a sim card and get data but I can make calls/text and use wifi, which is nice.
I wish Partition DL worked, we'd have the boot.img
I flashed Verizon Firmware and put the Verizon NT Code using PDM Mode, still didn't work. Going to try others later
KaptinBoxxi said:
I still can't get mine to accept a sim card and get data but I can make calls/text and use wifi, which is nice.
I wish Partition DL worked, we'd have the boot.img
I flashed Verizon Firmware and put the Verizon NT Code using PDM Mode, still didn't work. Going to try others later
Click to expand...
Click to collapse
Where did you get the Verizon firmware?
kaluna00 said:
Where did you get the Verizon firmware?
Click to expand...
Click to collapse
I found a site that had a "KDZ Downloader" and used that to download it. I can upload it here for those who need it once i redownload it here at work
or you can yourself from this post. Just need the LG URL to the firmware
[LG TOOLS] LG-KDZ-dll-Tool/LGUP_UI-fixer/LG-Kdz-downloader
Please, do not share elsewhere as I want to be able to update if necessary ! LG-KDZ-dll-Tool/KDZ dll extractor (=old version) : this message actually, scroll down a bit... LGUP_UI-fixer LG-Kdz-downloader Share this thread or my blog instead...
forum.xda-developers.com
KaptinBoxxi said:
I still can't get mine to accept a sim card and get data but I can make calls/text and use wifi, which is nice.
I wish Partition DL worked, we'd have the boot.img
I flashed Verizon Firmware and put the Verizon NT Code using PDM Mode, still didn't work. Going to try others later
Click to expand...
Click to collapse
I bought a mint mobile trial sim from amazon and I’m getting calls, text, and 5G data.
twocans said:
I bought a mint mobile trial sim from amazon and I’m getting calls, text, and 5G data.
Click to expand...
Click to collapse
I get calls and text, no cell service at all. I had to manually program in an IMEI. My IMEI comes back as 0 if I just flash it without PDM. IMEI doesn't apply via the service menu either
KaptinBoxxi said:
I get calls and text, no cell service at all. I had to manually program in an IMEI. My IMEI comes back as 0 if I just flash it without PDM. IMEI doesn't apply via the service menu either
Click to expand...
Click to collapse
Interesting. I was able to generate an IMEI in the hidden menu after the chip erase and it worked fine. I did also have to re-add my CSN, because that was also removed, and then my phone did an unprompted factory reset and rebooted.
By the way, when you flashed it, did you use Refurbish? Because with my demo unit, it refused to let me do that and would only allow chip erase. I was reluctant, but it turned out fine. And, the only important thing I was unable to reprogram afterwords was the S/N, but it doesn’t really matter to me. (Too bad the fingerprint scanner still doesn’t work though. That’s the only thing left that still isn’t working after all of this.)
twocans said:
Interesting. I was able to generate an IMEI in the hidden menu after the chip erase and it worked fine. I did also have to re-add my CSN, because that was also removed, and then my phone did an unprompted factory reset and rebooted.
By the way, when you flashed it, did you use Refurbish? Because with my demo unit, it refused to let me do that and would only allow chip erase. I was reluctant, but it turned out fine. And, the only important thing I was unable to reprogram afterwords was the S/N, but it doesn’t really matter to me. (Too bad the fingerprint scanner still doesn’t work though. That’s the only thing left that still isn’t working after all of this.)
Click to expand...
Click to collapse
I plan on testing every function to document what happens, so far I've done Refurbish, Partition DL, Dump, PDM and ChipErase. only Dump didn't work
Nice work fellas!!! Exciting to see some movement towards being able to root/development.
kaluna00 said:
Nice work fellas!!! Exciting to see some movement towards being able to root/development.
Click to expand...
Click to collapse
@KaptinBoxxi
BTW... How do you get to the hidden menu on the Verizon Varient?
kaluna00 said:
@KaptinBoxxi
BTW... How do you get to the hidden menu on the Verizon Varient?
Click to expand...
Click to collapse
I think its the same dial code. I don't have the device in front of me at the moment to say
I tried this earlier...
Post in thread 'LG Wing 5G Network option activation' https://forum.xda-developers.com/t/lg-wing-5g-network-option-activation.4285275/post-85116977
Am I using the wrong dial code for Verizon?
kaluna00 said:
I tried this earlier...
Post in thread 'LG Wing 5G Network option activation' https://forum.xda-developers.com/t/lg-wing-5g-network-option-activation.4285275/post-85116977
Am I using the wrong dial code for Verizon?
Click to expand...
Click to collapse
I have yet to have network work on my demo device regardless of what firmware is on it because my Serial Number and IMEI always come back at 0 and even if I manually enter new ones, it doesn't acivate, although i was able to get to the menu just fine with the standard code in that post.
Interesting, I wonder if there's something different in your firmware or kdz...
looking at the software version. mine is on
F100VM10i
maybe they (Verizon) patched out the hidden menu. your KDZ is labeled
F100VM10d
???
kaluna00 said:
looking at the software version. mine is on
F100VM10i
maybe they (Verizon) patched out the hidden menu. your KDZ is labeled
F100VM10d
???
Click to expand...
Click to collapse
I'm not sure what the final letter signifies, but F100V is verizon, yeah
KaptinBoxxi said:
I'm not sure what the final letter signifies, but F100V is verizon, yeah
Click to expand...
Click to collapse
think that represents the SW iteration identifier between updates... bit of a guess, but i believe that character has changed with updates.
Related
So, its been a rough time with this phone. I received it rooted and im really a noob to any of this, its a verizon phone, its labeled outside, and when you remove the battery it says model VS985. But in the settings it says otherwise. I placed an att sim card in it, and it worked fine, i just had some errors on the rom that i have no idea how to fix, it all just seems like a hassle to me, so i decided to unroot it to the best of my ability. I managed to download everything and when i ran the lg flash tool, i selected the firmware i downloaded, the verizon one, but when i tried to run it, it would say "Device Model is different" "factory model check error" or something like that, it would identify the phone has D850, which is at&t version.
So i went ahead and said **** it, i downloaded that version and went with that, something messed up and it ended with factory reset status 2 instead of 3.
So i had to select BOARD instead of UPGRADE in the flash tool. and it reset everything, booted with att logo and everything, now the only problem is i don't get any signal, at all. Any help?
cedric182 said:
So, its been a rough time with this phone. I received it rooted and im really a noob to any of this, its a verizon phone, its labeled outside, and when you remove the battery it says model VS985. But in the settings it says otherwise. I placed an att sim card in it, and it worked fine, i just had some errors on the rom that i have no idea how to fix, it all just seems like a hassle to me, so i decided to unroot it to the best of my ability. I managed to download everything and when i ran the lg flash tool, i selected the firmware i downloaded, the verizon one, but when i tried to run it, it would say "Device Model is different" "factory model check error" or something like that, it would identify the phone has D850, which is at&t version.
So i went ahead and said **** it, i downloaded that version and went with that, something messed up and it ended with factory reset status 2 instead of 3.
So i had to select BOARD instead of UPGRADE in the flash tool. and it reset everything, booted with att logo and everything, now the only problem is i don't get any signal, at all. Any help?
Click to expand...
Click to collapse
Somewhere in the g3 forums is an unbranded DLL file. It is my understanding from reading about it previously, you need to use that to allow you to flash the proper firmware. The DLL file was made to fix this exact issue from what I read before.
bweN diorD said:
Somewhere in the g3 forums is an unbranded DLL file. It is my understanding from reading about it previously, you need to use that to allow you to flash the proper firmware. The DLL file was made to fix this exact issue from what I read before.
Click to expand...
Click to collapse
Really? any more info on how to find it?
cedric182 said:
Really? any more info on how to find it?
Click to expand...
Click to collapse
I wish I could point you right to it, unfortunately you may have to browse similar help threads to yours until you find it.
I have the exact same problem but mine is seen as a d855 when it is a vs985 if you can find that .dll file please tell me as well! I am going to search for it now
cedric182 said:
So, its been a rough time with this phone. I received it rooted and im really a noob to any of this, its a verizon phone, its labeled outside, and when you remove the battery it says model VS985. But in the settings it says otherwise. I placed an att sim card in it, and it worked fine, i just had some errors on the rom that i have no idea how to fix, it all just seems like a hassle to me, so i decided to unroot it to the best of my ability. I managed to download everything and when i ran the lg flash tool, i selected the firmware i downloaded, the verizon one, but when i tried to run it, it would say "Device Model is different" "factory model check error" or something like that, it would identify the phone has D850, which is at&t version.
So i went ahead and said **** it, i downloaded that version and went with that, something messed up and it ended with factory reset status 2 instead of 3.
So i had to select BOARD instead of UPGRADE in the flash tool. and it reset everything, booted with att logo and everything, now the only problem is i don't get any signal, at all. Any help?
Click to expand...
Click to collapse
If you are 100% sure you do in fact have the Verizon LG G3 (VS985), replace the Verizon DLL file with the Generic LG G3 DLL below. This error is most common if you have changed the Product Name, Product Model, Display ID, and/or Build ID entries in the build.prop
The generic dll file is on autoprime's site. It's named LGUP_8974.dll and can be found here- http://downloads.codefi.re/autoprime/LG/LG_G3 Use that along with the Verizon firmware Instead of the Verizon dll
Hawkswind thank you so much!! that worked for me now i am going to flash back the verizon .dll file
Thank you.
Hi everyone, I've followed the WTF thread to unlock the bootloader on a V30 H933 (the Canadian version), but even after unlocking there's no fastboot support on the phone, only the US998 version seems to have it. Trouble is that Rogers, my local operator, only supports VoLTE and VoWiFi on their recognized devices - I tried having US998 running on my phone, calling their support and possibly getting some actual configuration I could put on the phone, but their response was "your phone is defective and needs to be replaced".
All that said, my goal here is to somehow install TWRP on this phone and root under the original ROM, so I can have the features I need from the network. So far, I've been pretty unsuccessful in this, so my plead would be: could anyone chime in to help me either
flash the minimal necessary over US998 to get H933 functionality/network information back as to reenable VoLTE and VoWiFi on my operator
come up with an update.zip or some other file I could use to flash a Magisk-patched boot.img
pack a full flashable ZIP image of the Canadian ROM (my last attempt at this left the phone in bootloop)
an alternative idea I haven't thought about that could help?
Ideally, at the end of the process, I'd like to have TWRP and Magisk installed on the phone, but I could settle for simply Magisk.
Once again, any help or pointers are more than welcome and appreciated.
I think you can extract a h933 kdz and flash individual partitions that do not have to do with recovery or the bootloader. You can probably use the dd command for it. I think the partitions you dont flash are anything with boot in it, abl and recovery. There may be a few more however.
The Elite said:
I think you can extract a h933 kdz and flash individual partitions that do not have to do with recovery or the bootloader. You can probably use the dd command for it. I think the partitions you dont flash are anything with boot in it, abl and recovery. There may be a few more however.
Click to expand...
Click to collapse
I tried something similar, extracted a KDZ and put the necessary BIN files on a flashable ZIP I found around. All I achieved was bootlooping the device...
I have an H933 on Freedom Mobile, and running the stock FM firmware. The loss of VOWIFI (and VoLTE) are exactly what i thought would happen if I proceed with flashing to US998.
I think #1 is right; that you may be able to restore access to network specific functionality but it would depend on being able to isolate the specific required "patch".
With this in mind, take a look at this post from the WTF! Thread:
https://forum.xda-developers.com/showthread.php?p=76613814
That user flashed some files (modem binaries from the original device firmware I think) and was able to restore VOWIFI and VoLTE functionality on the Verizon network.
Sent from my LG-H933 using Tapatalk
My h933 converted to us998 says that my volte is enabled
cre4per said:
My h933 converted to us998 says that my volte is enabled
Click to expand...
Click to collapse
What menu is that from @cre4per? Have you had the opportunity to confirm staying on LTE while receiving a call?
That would be good news to hear VoLTE working on a Canadian network using a generic phone model (instead of proprietary stuff).
Sent from my LG-US998 using Tapatalk
Mad Medik said:
What menu is that from @cre4per? Have you had the opportunity to confirm staying on LTE while receiving a call?
That would be good news to hear VoLTE working on a Canadian network using a generic phone model (instead of proprietary stuff).
Sent from my LG-US998 using Tapatalk
Click to expand...
Click to collapse
*#*#4636#*#*,
and to be honest i never really noticed, will do some checks today to see if i stay on lte, will let you know
cre4per said:
*#*#4636#*#*,
and to be honest i never really noticed, will do some checks today to see if i stay on lte, will let you know
Click to expand...
Click to collapse
Looking at this this morning. I don't think that is an indication that you are connected to a VoLTE service; just that your device is ready to accept it if the right service becomes available. I have that switch turned on and the service menu even says the voice network is LTE too (see image below) but Freedom Mobile doesn't even offer VoLTE service so it isn't possible that I actually have VoLTE operational.
I would interpret the LTE provision switch as turning on or off the functionality in your device, not a connection authorization from the network. Sort of like turning on the HD calling option on your device; it allows the possibility but won't do anything unless the service provider has the capability and authorizes it on your connection.
If someone has VoLTE working, could you check the menu cited by @cre4per, then hit the options (3 dots) and in there, select IMS service status? It lools like this is where you *should* see if the network has connected you to their VoLTE service (see image below).
I don't know how to interpret the, "Voice Network: LTE" on the main menu screen.
Just check and switches to 3g on calls also when going into that ims menu says unavailable
GryphonBR said:
I tried something similar, extracted a KDZ and put the necessary BIN files on a flashable ZIP I found around. All I achieved was bootlooping the device...
Click to expand...
Click to collapse
Out of all the partitions which ones did you flash and which ones did you not flash? Also was the h933 kdz also for oreo?
-deleted-
cre4per said:
My h933 converted to us998 says that my volte is enabled
Click to expand...
Click to collapse
As @Mad Medik mentioned, so far I don't know of any Canadian operators enabling VoLTE (or VoWiFi for that matter) to generic phones. I have a Rogers P10 Plus that's registered under my account as my main phone and which I reflashed to have these features available, but it just won't work. I've had extended arguments with Rogers representatives about it, and the 1+3T I'm presently using even have the same config your phone is showing: VoLTE Provisioned, but IMS shows as Not Registered so nothing else works. I'm waiting on an LS998 I bought to arrive, I'll try flashing H933 on it to see if it actually allows me to register on IMS.
The Elite said:
Out of all the partitions which ones did you flash and which ones did you not flash? Also was the h933 kdz also for oreo?
Click to expand...
Click to collapse
KDZ was for Oreo, indeed. It was the one I used to bring the phone to the latest (at the moment) update available.
As for which partitions I flashed, I was gonna give you a list, but to make it short the only partition not flashed was recovery.
GryphonBR said:
As @Mad Medik
KDZ was for Oreo, indeed. It was the one I used to bring the phone to the latest (at the moment) update available.
As for which partitions I flashed, I was gonna give you a list, but to make it short the only partition not flashed was recovery.
Click to expand...
Click to collapse
As far as I know there are some boot partitions that should not be flashed, which may have caused the soft brick. I know autoprime used to make these zips for the G3 and runningnak3d made one for the V10, you might want to cross reference the partitions they used and what they didnt. Probably the V10 first because the G3 is relatively ancient. I think in essence you should just be able to flash boot, system and modem and rpm though, but you would need 2 combine the split up system images after the extract.
The Elite said:
As far as I know there are some boot partitions that should not be flashed, which may have caused the soft brick. I know autoprime used to make these zips for the G3 and runningnak3d made one for the V10, you might want to cross reference the partitions they used and what they didnt. Probably the V10 first because the G3 is relatively ancient. I think in essence you should just be able to flash boot, system and modem and rpm though, but you would need 2 combine the split up system images after the extract.
Click to expand...
Click to collapse
The reason why I was flashing everything is because I used this thread to recover from a previous soft brick I stumbled upon. Upon speaking to the thread creator, he mentioned I should be able to follow a similar process to achieve an H933 flashable file. Did that and, well, managed to soft brick the phone... I might try your idea, though.
So, from my knowledge of attempting to get VoLTE working on an HTC 10, I suspect you won't get VoLTE working on anything other than Rogers H933 firmware. For whatever reason, the programming required for VoLTE isn't on the USIM card in your phone, but rather programmed into the phone by the provider. This means, unless your phone model is sold and supported for VoLTE on the provider you wish to use it on, you're screwed like I was, trying to get VoLTE working on my HTC 10 on Rogers.
This being said, the good news is we are back to CDMA tech here, where the only thing preventing you from using your third party phone with your provider is knowing what code to enter, and what parameters to program in. Since my H933 is on Telus, my programming won't do you much good.
What you're looking for is the IMS settings or IP Multimedia Subsystem settings, as this is what carries the VoIP packets that consist of VoLTE. If someone were to post the settings from their Rogers H933, you may be able to get VoLTE working on US998 firmware.
Why not just flash system and boot? After unlocked and rooted of course.. Lg up partition DL will let you flash individual partitions. I would have done it that way for my carrier but there is no kdz available..
JWnSC said:
Why not just flash system and boot? After unlocked and rooted of course.. Lg up partition DL will let you flash individual partitions. I would have done it that way for my carrier but there is no kdz available..
Click to expand...
Click to collapse
I tried that last night just bootloops
cre4per said:
I tried that last night just bootloops
Click to expand...
Click to collapse
Did you wipe data?
JWnSC said:
Did you wipe data?
Click to expand...
Click to collapse
Yea. Then went to restore and the restore wouldn't even work anymore. Was saying there was no partitions backed up but I had use that restore numerous of times trying to get los to boot very strange had to start back from scratch
Anyone with H933 from freedom mobile convert to US988? I'm just wondering how the service is after the change. I'm reading mixed reports but once modems extracted and compared there was a difference.
So to use this, you will need to be bootloader unlocked, magisk rooted, and twrp installed, DM Verity Disabled this is a must!!(its always good to make a nandroid before making any changes on your phone). What this will do is more or less provision your Lg G8x to your Desired Carrier, it will also let you change your apns, so you have volte working and also the data indicator will change to match the carrier. WIfi calling is working on tmobile, will need someone to test other carriers.
There seems to be confusion , this is only for the Stock rom. this will do nothing for GSI roms.
Instructions:
1.Extract to Content of zip to Sdcard
2.Make a copy/backup of your own files: Go to twrp and backup your product partition and your op configs in case you need to restore them
3.Copy and paste the files from my zip to:
/product/op/config
and this single file cust.prop to /product/op
make sure permissions are 644.
4.Reboot your device it should now be provisioned to your Desired Carrier.
Click to expand...
Click to collapse
Download
Sprint Untested
SPR-VOLTE-FIX
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
T-Mobile
Tmo-VOLTE-VOWIFI-FIx-G8x
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
VZW Untested
VZW-VOLTE-FIX
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Credits:
vl48 this guy is awesome, and also very patient an expert in lg devices.
Can you write a guide for ATT LG G8X (LMG850UM) on
How to bootloader unlocked, magisk rooted, and twrp installed, DM Verity Disabled? It's confusing which method is valid and which files to use.
e20140 said:
Can you write a guide for ATT LG G8X (LMG850UM) on
How to bootloader unlocked, magisk rooted, and twrp installed, DM Verity Disabled? It's confusing which method is valid and which files to use.
Click to expand...
Click to collapse
There is one already made, you just need the correct twrp from telegram
siulmagic said:
There is one already made, you just need the correct twrp from telegram
Click to expand...
Click to collapse
Why not post on xda? Is everyone switching to telegram? I've read everything on xda and don't see a specific method to unlock bootloader+twrp+DM but a few failed attempts on ATT version of the G8X. I only see working solution for India, Europe, and Sprint Models. You are the only one that has successfully unlock it. I am sure more people will need help as 3G is going away and we need Volte working on this phone.
well the basic gist of it is:
This will WIpe Your Phone, make sure to backup first.
Cant post the recovery zip, but pm il send it to you. i will move this to a proper thread later today. and better formatted
1.install qpst/qualcom driver or use windows update ones
2. download firehose uncompress it somewere on your pc
3.download g8x twrp and magisk 20.4 zip also the dm verity zip
also make sure to grab the eng abl for the g8x(eng bootloader that will allow us to unlock).
4. enable oem unlock in developer settings
5. boot phone into edl mode
6.start qpst set storage type to ufs, slect built type, make sure it is flat build
7.Look for select programer then click browse, here you will chose the firehose file
8. click select port on qfil then double click 9008 com port were the phone is detected in edl mode
9.now in qfil select tools then partition manager
10. when the list of partitions show up look for abl_a,abl_b,modem a/b, and modemst1 and 2, you will right click each of them and click manage partition data then read data, this will back them up to your computer(be very careful you can wipe your whole phone if you click in the wrong place)
11.after you back up everything select load img and flash abl_a to Abl_a and abl_b. after this unplug phone and boot into bootloader mode.
To boot into bootloader mode turn off your phone and hold volm down and plug in your usb cable, this should boot it into bootloader mode .
12. if you see text that says you active boot slot, you now have successfully flashed the eng bootloader witch will allow you to unlock the bootloader.
13. now while the phone is pluged into your computer you will open a adb window and type fastboot oem unlock , the phone will ask you to agree to unlock the bootloader, select yes.
14.after this reboot your phone into edl mode, reflash your backup abl_a to abl_a and abl_b, this will restore stock bootloader you wont have fastboot anymore but no worries, also you can flash your stock rooted boot.img to boot_a and boot_b.
15. After you reboot into android, install magisk manager, flash the g8x twrp zip and without reboot, also flash magisk 20.04 zip, if you do not do it this way you will break your boot.img and have issues, like freezing system.
16 now reboot to recovery wipe data then reboot and flash the dm verity disabler to disable encryption. after this create a nandroid backup, then just reboot back to system and enjoy.
17. profit
Nice
I need to return my G8X since it has the latest 20g firmware. If anyone wants me to try or test something, please let me know before it's going back.
e20140 said:
Nice
I need to return my G8X since it has the latest 20g firmware. If anyone wants me to try or test something, please let me know before it's going back.
Click to expand...
Click to collapse
why 0o with gpst and firehose you can root bl unlock any att g8x, unless there something im not aware of?
I post the short error log here. The firehose we got can't read the partitions correctly. Maybe the mappings are different, IDK? If you want to read the full log, let me know.
e20140 said:
I post the short error log here. The firehose we got can't read the partitions correctly. Maybe the mappings are different, IDK? If you want to read the full log, let me know.
Click to expand...
Click to collapse
thats a driver error, you need to let windows install the driver from windows update or like i did use qpst on windows 7. i never got that erro fixed, so i just used windows 7 on a old laptop i have, and it works mint.
I don't have Window 7 to try but tried on other Win 10 PCs and Laptops, just no luck. I can use QPST to flash flat built on my G6 fine, really don't think it's driver issue.
e20140 said:
I don't have Window 7 to try but tried on other Win 10 PCs and Laptops, just no luck. I can use QPST to flash flat built on my G6 fine, really don't think it's driver issue.
Click to expand...
Click to collapse
well thats the error i got, with my g8 and g8x on windows 10.
wangsu10 suggested the error could be installation selection option for the QCOMM driver. Need to be install as 2nd option " ETHERNET-DHCP". I already returned mine
Maybe you can try it on your Win10 and report back. If it works, we need to have it added to the OP for all others to see.
Thank you for sharing this. I have a sprint model that ended up with T-mobile provisioning after I boot loader unlocked it. The only issue I think I have at least the obvious is google messages will never verify and setup rcs. I suspect this will be permanent eventually as they begin to roll out their other layer of security for verifying that which would basically black list bootloader unlocked or rooted devices...will your files/instructions aid in any issues with RCS currently before before Google makes the final rollout?
nate0 said:
Thank you for sharing this. I have a sprint model that ended up with T-mobile provisioning after I boot loader unlocked it. The only issue I think I have at least the obvious is google messages will never verify and setup rcs. I suspect this will be permanent eventually as they begin to roll out their other layer of security for verifying that which would basically black list bootloader unlocked or rooted devices...will your files/instructions aid in any issues with RCS currently before before Google makes the final rollout?
Click to expand...
Click to collapse
Thats an easy fix search for carrier services on play store , update it and see if chat features get enabled, I got rcs working just fine on att g8x bl unlocked and rooted ofc.
siulmagic said:
Thats an easy fix search for carrier services on play store , update it and see if chat features get enabled, I got rcs working just fine on att g8x bl unlocked and rooted ofc.
Click to expand...
Click to collapse
Yeah I did this, and by default it was already installed. Still no luck. I tried clearing data while on airplane mode everything. Nothing works yet.
@siulmagic where is the twrp image for the g8x? Did they pull it down?
nate0 said:
@siulmagic where is the twrp image for the g8x? Did they pull it down?
Click to expand...
Click to collapse
the one here never worked properlly, if you want a working one join telegram and i can send it to you,.
nate0 said:
Yeah I did this, and by default it was already installed. Still no luck. I tried clearing data while on airplane mode everything. Nothing works yet.
Click to expand...
Click to collapse
there is another app that needs updated i forgot witch one it was.
siulmagic said:
the one here never worked properlly, if you want a working one join telegram and i can send it to you,.
Click to expand...
Click to collapse
Newbie to Telegram, how does one find the group please?
mangojain said:
Newbie to Telegram, how does one find the group please?
Click to expand...
Click to collapse
LG Mobiles India 🇮🇳
Political Discussion, Obscene material/words, Selling, Fraudulent link posting will lead to Ban SHARING COPYRIGHT CONTENT & PIRACY NOT ALLOWED, it leads to REPORT & BLOCK Photography Group: @lgg8xphotography OT Group: @LG_G8X_OffTopic
t.me
Check your OnePlus updater.
mingkee said:
Check your OnePlus updater.
Click to expand...
Click to collapse
Yes, A-12 has been released for the N200, but it may screw up your phone. I bought three of the unlocked US market 5g N200s due to the 3g phase out. Yesterday two of them updated to A-12 and now neither of them will work for voice /mms/sms. The phones detect a SIM installed but will not access the mobile network at all. I'm using Consumer Cellular which in turn uses At&T towers. Nothing I've tried makes any difference, can't even place a call on my brand new phones. OnePlus tech support is useless, their solution is send the devices to them for "repair" after their update broke my phones. After chatting with their rep I have 0% confidence they will actually do anything except keep my phone for a month or so and send it back in the same condition. According to their tech, no roll back tool exists for the unlocked variant.
Scragge said:
Yes, A-12 has been released for the N200, but it may screw up your phone. I bought three of the unlocked US market 5g N200s due to the 3g phase out. Yesterday two of them updated to A-12 and now neither of them will work for voice /mms/sms. The phones detect a SIM installed but will not access the mobile network at all. I'm using Consumer Cellular which in turn uses At&T towers. Nothing I've tried makes any difference, can't even place a call on my brand new phones. OnePlus tech support is useless, their solution is send the devices to them for "repair" after their update broke my phones. After chatting with their rep I have 0% confidence they will actually do anything except keep my phone for a month or so and send it back in the same condition. According to their tech, no roll back tool exists for the unlocked variant.
Click to expand...
Click to collapse
S build based on Color OS and even the font changed.
I think I can deal with mine, but the most important of all, there's no player error on rooted N200 with S
Scragge said:
Yes, A-12 has been released for the N200, but it may screw up your phone. I bought three of the unlocked US market 5g N200s due to the 3g phase out. Yesterday two of them updated to A-12 and now neither of them will work for voice /mms/sms. The phones detect a SIM installed but will not access the mobile network at all. I'm using Consumer Cellular which in turn uses At&T towers. Nothing I've tried makes any difference, can't even place a call on my brand new phones. OnePlus tech support is useless, their solution is send the devices to them for "repair" after their update broke my phones. After chatting with their rep I have 0% confidence they will actually do anything except keep my phone for a month or so and send it back in the same condition. According to their tech, no roll back tool exists for the unlocked variant.
Click to expand...
Click to collapse
THANK YOU for posting this!! My mom purchased an N200 for the exact same reason and after the A-12 update she's having the same issues with her device. All her voice, sms, and mms transmissions go through Cricket wireless (which also uses AT&T network) She contacted OnePlus customer service and they said they'd get back to her within 48 hours. It's now been 48 hours but with it being a weekend, she's hoping to hear back from them by Monday. She went to the Cricket store yesterday and they cleaned and tried a new SIM card to see if that might fix the issue but it didn't.
While it doesn't sound like there's any fix available yet, it's helpful knowing that this issue is affecting someone else using the AT&T carrier network. Hopefully between OnePlus and the AT&T wireless carriers they'll figure out a solution sooner rather than later.
Best of luck with your devices.
The12thJuror said:
THANK YOU for posting this!! My mom purchased an N200 for the exact same reason and after the A-12 update she's having the same issues with her device. All her voice, sms, and mms transmissions go through Cricket wireless (which also uses AT&T network) She contacted OnePlus customer service and they said they'd get back to her within 48 hours. It's now been 48 hours but with it being a weekend, she's hoping to hear back from them by Monday. She went to the Cricket store yesterday and they cleaned and tried a new SIM card to see if that might fix the issue but it didn't.
While it doesn't sound like there's any fix available yet, it's helpful knowing that this issue is affecting someone else using the AT&T carrier network. Hopefully between OnePlus and the AT&T wireless carriers they'll figure out a solution sooner rather than later.
Best of luck with your devices.
Click to expand...
Click to collapse
Yeah, I called OP three times got the same promise from OPs customer service and they never got back with me. I've never dealt with a less enthusiastic company when dealing with a serious product defect. The tech support people at first acted like the didn't believe me when I described the problem. Then once I had (I think) convinced them the problem was real, their response was like "oh well, too bad, so sad". OP offered no solutions or even ideas of what to try to do to fix the problem.
Do they test anything before pushing out an update?
I had a two day window left for returning the devices for a refund so now they're gone, and I'm gone as an OP customer, I can't just do without a phone while they fumble around trying to figure out the details for some (maybe) upcoming patch.
Good devices, terrible customer service. Never settle, nope, never again.
Scragge said:
According to their tech, no roll back tool exists for the unlocked variant.
Click to expand...
Click to collapse
Try this
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
For those of you who want to downgrade from 12 to 11, use fastboot enhanced/payload dumper, boot fastbootd, delete all of the "my_" partitions, flash android 11 ROM zip (payload.bin button). Reboot bootloader, use the command fastboot -w to initiate a factory reset, reboot recovery and wipe data (this fixes mismatching metadata/userdata partitions) reboot device and voila you're on Android 11 again. Confirmed on my converted TMobile variant.
Also T-Mobile variant got official A12 OTA with the same C.15 build number.
And AT&T doesn't play nice with OnePlus, their new sim cards will not let you use a OnePlus device at all because they are unsupported.
Travisholt92 said:
For those of you who want to downgrade from 12 to 11, use fastboot enhanced/payload dumper, boot fastbootd, delete all of the "my_" partitions, flash android 11 ROM zip (payload.bin button). Reboot bootloader, use the command fastboot -w to initiate a factory reset, reboot recovery and wipe data (this fixes mismatching metadata/userdata partitions) reboot device and voila you're on Android 11 again. Confirmed on my converted TMobile variant.
Also T-Mobile variant got official A12 OTA with the same C.15 build number.
And AT&T doesn't play nice with OnePlus, their new sim cards will not let you use a OnePlus device at all because they are unsupported.
Click to expand...
Click to collapse
Do you know where to download the A12(or at least the latest A11 update so I can update to A12 via OTA) stock firmware/update or could you upload it for the T-MO(metro) variant or show how to update OTA even when I unroot both slots the OTA still fails
Tyreethetruth said:
Do you know where to download the A12 stock firmware/update or could you upload it for the T-MO(metro) variant or show how to update OTA even when I unroot both slots the OTA still fails
Click to expand...
Click to collapse
I'll get the link scraped today. To fix OTA you have to reflash the stock build to restore avb (android verified boot / vbmeta verification). Without this being restored you can't flash OTA's using the normal methods. But once I get a link to the T-Mobile/metro update, you can use fastboot enhanced to manually upgrade like I did. I'll make a tutorial for the manual upgrade/downgrade process. I first have to downgrade from OxygenOS 12 to 11, then use the MSMtool to restore stock T-Mobile software. Easy stuff
Travisholt92 said:
I'll get the link scraped today. To fix OTA you have to reflash the stock build to restore avb (android verified boot / vbmeta verification). Without this being restored you can't flash OTA's using the normal methods. But once I get a link to the T-Mobile/metro update, you can use fastboot enhanced to manually upgrade like I did. I'll make a tutorial for the manual upgrade/downgrade process. I first have to downgrade from OxygenOS 12 to 11, then use the MSMtool to restore stock T-Mobile software. Easy stuff
Click to expand...
Click to collapse
Thank you! I been stuck on the same update like 4-5 updates ago
On this build (metro/TMobile version converted. I can't keep android auto connected. I went into developer options and selected the default to transfer files/ android auto and all the other options but it just connects for a few and then disconnected and says device unsupported.
Rooted device and using a alpine iLX-w650
Tyreethetruth said:
Thank you! I been stuck on the same update like 4-5 updates ago
Click to expand...
Click to collapse
The link to the download is literally a https link in the logcat when downloading the OTA. In case you're wondering how to manually download the zip onto a computer, that is how to get the link. If anyone else beats me to sharing the link it would save me from having to downgrade to get the link for the T-Mobile variant myself
"adb logcat > logcat.txt"
Travisholt92 said:
The link to the download is literally a https link in the logcat when downloading the OTA. In case you're wondering how to manually download the zip onto a computer, that is how to get the link. If anyone else beats me to sharing the link it would save me from having to downgrade to get the link for the T-Mobile variant myself
"adb logcat > logcat.txt"
Click to expand...
Click to collapse
So I get on computer and go on bootloader and type "adb logcat"?
Negative, while booted and after you start to download the android 12 OTA you can run the adb command to get the link while the OS is running.
https://android.googleapis.com/packages/ota-api/package/7cd89efc84e6db817ed16b59b0af3120521ab323.zip
(Shout out to @lzgmc )
I dirty flashed this (DE2118 T-Mobile/Metro) build over the leaked unlocked variant (DE2117) OxygenOS 12 build most are running and did not have to factory reset after flashing with Fastboot Enhanced.
My TMobile variant is now running the T-Mobile firmware. No downgrade required for that.
Downgrade process is download the android 11 build from OnePlus, boot fastbootd, use fastboot enhanced to delete all of the "my_" partitions, flash "payload bin" (full android 11 ota zip from OnePlus), make sure to tick ignore unknown partitions. After that is done shut the phone down and boot to fastboot/bootloader using the key combo, and flash the same payload again with ignore unknown partitions ticked. This will update the partitions that were inaccessible in fastbootd (such as modem). After this you will have to use a terminal with adb/fastboot to run "fastboot -w" this will wipe metadata(encryption key for userdata) and userdata. Reboot to recovery and perform factory reset there as well. After that you should be good to reboot to OxygenOS 11. To return to stock T-Mobile after that just use msmtool
Travisholt92 said:
Negative, while booted and after you start to download the android 12 OTA you can run the adb command to get the link while the OS is running.
https://android.googleapis.com/packages/ota-api/package/7cd89efc84e6db817ed16b59b0af3120521ab323.zip
(Shout out to @lzgmc )
I dirty flashed this (DE2118 T-Mobile/Metro) build over the leaked unlocked variant (DE2117) OxygenOS 12 build most are running and did not have to factory reset after flashing with Fastboot Enhanced.
My TMobile variant is now running the T-Mobile firmware. No downgrade required for that.
Downgrade process is download the android 11 build from OnePlus, boot fastbootd, use fastboot enhanced to delete all of the "my_" partitions, flash "payload bin" (full android 11 ota zip from OnePlus), make sure to tick ignore unknown partitions. After that is done shut the phone down and boot to fastboot/bootloader using the key combo, and flash the same payload again with ignore unknown partitions ticked. This will update the partitions that were inaccessible in fastbootd (such as modem). After this you will have to use a terminal with adb/fastboot to run "fastboot -w" this will wipe metadata(encryption key for userdata) and userdata. Reboot to recovery and perform factory reset there as well. After that you should be good to reboot to OxygenOS 11. To return to stock T-Mobile after that just use msmtool
Click to expand...
Click to collapse
Alright cool thanks for the download so just go to twrp/orangefox and install it or do I get on pc and flash it via adb? Does it have to only be fastboot enhanced?
Tyreethetruth said:
Alright cool thanks for the download so just go to twrp/orangefox and install it or do I get on pc and flash it via adb? Does it have to only be fastboot enhanced?
Click to expand...
Click to collapse
PC and flash via fastbootd then again in fastboot after fastbootd. Fastboot enhanced is the easiest way to do it, otherwise you will need to fix custom recovery to support android 12 or use command line tools to unpack the oneplus ota file to manually flash each partition.
Travisholt92 said:
PC and flash via fastbootd then again in fastboot after fastbootd. Fastboot enhanced is the easiest way to do it, otherwise you will need to fix custom recovery to support android 12 or use command line tools to unpack the oneplus ota file to manually flash each partition.
Click to expand...
Click to collapse
Gotcha, how do I go to fastbootd and fastboot? Its confusing me which one is which
Tyreethetruth said:
Gotcha, how do I go to fastbootd and fastboot? Its confusing me which one is which
Click to expand...
Click to collapse
fastboot = bootloader
Fastbootd has access to more critical partitions and can be accessed by the command "fastboot reboot fastboot" at the bootloader or by hitting the "reboot to fastbootd" button in fastboot enhanced. Make sure to flash it in fastbootd BEFORE flashing it again in fastboot
Travisholt92 said:
fastboot = bootloader
Fastbootd has access to more critical partitions and can be accessed by the command "fastboot reboot fastboot" at the bootloader or by hitting the "reboot to fastbootd" button in fastboot enhanced. Make sure to flash it in fastbootd BEFORE flashing it again in fastboot
Click to expand...
Click to collapse
Gotcha, one last thing how do I flash using fastboot enhance? Idk what to pick to flash the A12 OTA
EDIT: Nvm I extracted the update and found the payload
Magisk patched boot.img for this release: https://drive.google.com/file/d/1A2x8YbnnO6SJq-R-1rdZZ18CU673Z2-Y/view?usp=sharing
I tried to crossflash my G8X to the US Open A11 software and screwed up quite badly during the process. I've had to restore my phone from having no partitions and do not have the original LUN5 files, only the 7 required for the crossflash. I've also rooted and installed twrp on this device so if anything that could help needs that I'm able to use it.
I expected the fingerprint sensor not to work, however now the light sensor, accelerometer, gyroscope, magnetometer, etc. don't work either.
Is there something I can do to get this functionality back? I've mostly given up on fixing the imei and network issues but I would like to at least have the phone in a usable state on Wifi.
If more details are needed please do tell and I will do my best to provide them.
Guille05 said:
I tried to crossflash my G8X to the US Open A11 software and screwed up quite badly during the process. I've had to restore my phone from having no partitions and do not have the original LUN5 files, only the 7 required for the crossflash. I've also rooted and installed twrp on this device so if anything that could help needs that I'm able to use it.
I expected the fingerprint sensor not to work, however now the light sensor, accelerometer, gyroscope, magnetometer, etc. don't work either.
Is there something I can do to get this functionality back? I've mostly given up on fixing the imei and network issues but I would like to at least have the phone in a usable state on Wifi.
If more details are needed please do tell and I will do my best to provide them.
Click to expand...
Click to collapse
What original firmware was on it?Most definitely,always make a full back up first thing.
Surgemanxx said:
What original firmware was on it?Most definitely,always make a full back up first thing.
Click to expand...
Click to collapse
It was originally on version 20p of the sprint software. And yeah, I definitely hadn't quite read up on all of the important things I needed to backup beforehand.
Guille05 said:
I tried to crossflash my G8X to the US Open A11 software and screwed up quite badly during the process. I've had to restore my phone from having no partitions and do not have the original LUN5 files, only the 7 required for the crossflash. I've also rooted and installed twrp on this device so if anything that could help needs that I'm able to use it.
I expected the fingerprint sensor not to work, however now the light sensor, accelerometer, gyroscope, magnetometer, etc. don't work either.
Is there something I can do to get this functionality back? I've mostly given up on fixing the imei and network issues but I would like to at least have the phone in a usable state on Wifi.
If more details are needed please do tell and I will do my best to provide them.
Click to expand...
Click to collapse
The same thing happened to me, I came from a10 sprint and installed a11 from Canada, I was left without a network and without a fingerprint sensor, but the other sensors work without problem, to fix network and ntcode I think it is only possible by box, I don't know if of the fingerprint sensor is caused by the lack of serial and imei.
if you come up with a solution let me know bro
mclarenf195 said:
The same thing happened to me, I came from a10 sprint and installed a11 from Canada, I was left without a network and without a fingerprint sensor, but the other sensors work without problem, to fix network and ntcode I think it is only possible by box, I don't know if of the fingerprint sensor is caused by the lack of serial and imei.
if you come up with a solution let me know bro
Click to expand...
Click to collapse
Did you restore your 7 bin files after flashing the A11 software?
Guille05 said:
Did you restore your 7 bin files after flashing the A11 software?
Click to expand...
Click to collapse
They don't have a backup,that's the reason I ask what version software it was.
Guille05 said:
It was originally on version 20p of the sprint software. And yeah, I definitely hadn't quite read up on all of the important things I needed to backup beforehand.
Click to expand...
Click to collapse
Use this firmware.It will correct your issues.
Download LG Firmware for LG G8X ThinQ LMG850QM _Unknown kdz stock USA Rom
Download _Unknown KDZ stock firmware for download with direct link
lg-roms.com
Guille05 said:
Did you restore your 7 bin files after flashing the A11 software?
Click to expand...
Click to collapse
I have the backup of the 7 partitions but they are useless if all the original partitions have been deleted, that is what I understand, I restored the partitions of a KDZ a10 and then flashed it to a11
Surgemanxx said:
Use this firmware.It will correct your issues.
Download LG Firmware for LG G8X ThinQ LMG850QM _Unknown kdz stock USA Rom
Download _Unknown KDZ stock firmware for download with direct link
lg-roms.com
Click to expand...
Click to collapse
I've got version 30c of that firmware installed, you think going back one update would fix it?
mclarenf195 said:
I have the backup of the 7 partitions but they are useless if all the original partitions have been deleted, that is what I understand, I restored the partitions of a KDZ a10 and then flashed it to a11
Click to expand...
Click to collapse
When you flashed the A10 kdz, you followed netmsm's guide right? Did you get any errors when flashing the partitions with fhloader? When I extracted the kdz a few files were missing from the ones used by that code but every kdz I've extracted doesn't have them either.
Guille05 said:
I've got version 30c of that firmware installed, you think going back one update would fix it?
Click to expand...
Click to collapse
Yes,go to 30b it will all work.I tried 30c on my sprint model,and had issues with network connectivity as well.
Surgemanxx said:
Yes,go to 30b it will all work.I tried 30c on my sprint model,and had issues with network connectivity as well.
Click to expand...
Click to collapse
I have the 30a, it would be to try
Guille05 said:
When you flashed the A10 kdz, you followed netmsm's guide right? Did you get any errors when flashing the partitions with fhloader? When I extracted the kdz a few files were missing from the ones used by that code but every kdz I've extracted doesn't have them either.
Click to expand...
Click to collapse
yes, the netmsm's guide, fhloader only use it to restore the luns, restore the kdz partitions one by one with qfil, just try what Surgemanxx suggested first and tell me how it goes.
mclarenf195 said:
yes, the netmsm's guide, fhloader only use it to restore the luns, restore the kdz partitions one by one with qfil, just try what Surgemanxx suggested first and tell me how it goes.
Click to expand...
Click to collapse
It works very well.I tried 30c,and noticed it was slow and laggy and rolled back to 30b and it worked flawless.Fingerprint scanning and all worked with a T-Mobile sim with no issues.They should be good with 30b,all but the IMEI issue they have.
All right I completely erased the flash again and reinstalled following the steps very carefully. I'm now on 30b and can confirm that the sensors work once again. Although the major issues I think were deeper than just the update, because I updated before doing a full erase and it still wasn't working. Now I just have to keep trying to fix the IMEI and FP sensor.
Also I think I may have found my IMEI number thanks to having the ftm partition backed up and therefore still having the serial number. The first 8 digits are always 35886110 for the LG G8x sprint model (and maybe others in the US), the next 6 are the last 6 digits of the serial and the last one is a check digit that you can look up online. I've checked the number on multiple sites and it seems legit so I hope it's actually my number. Now I'll try to write it to the phone somehow, but at least having the IMEI back is a very big step forward.
IMEI is fixed, or at least it appears as such in the phone. I went through with the tutty method of installing the IMEI, and after much trouble (and tutty saying error to my command to write the IMEI) I was able to restore the IMEI to the phone. I confirmed this first using EFS Pro and going into qualcomm NV tools. The IMEI was still as 0 in my phone but after putting in a sim it appeared in the OS and has stayed there. However it still appears as permanently locked when a sim is inserted and the nt-code error does still happen, so the network doesn't work yet.
Guille05 said:
IMEI is fixed, or at least it appears as such in the phone. I went through with the tutty method of installing the IMEI, and after much trouble (and tutty saying error to my command to write the IMEI) I was able to restore the IMEI to the phone. I confirmed this first using EFS Pro and going into qualcomm NV tools. The IMEI was still as 0 in my phone but after putting in a sim it appeared in the OS and has stayed there. However it still appears as permanently locked when a sim is inserted and the nt-code error does still happen, so the network doesn't work yet.
Click to expand...
Click to collapse
That LUNS backup is for the Sprint U.S. model G850UM9.The IMEI is stored in modemst1 and 2 which is LUNS5 that I didn't include for that reason.The NT Code error shouldn't be there if it's the same model/region.Keep me posted.
Surgemanxx said:
That LUNS backup is for the Sprint U.S. model G850UM9.The IMEI is stored in modemst1 and 2 which is LUNS5 that I didn't include for that reason.The NT Code error shouldn't be there if it's the same model/region.Keep me posted.
Click to expand...
Click to collapse
I've flashed your backups and the NT Code error indeed disappeared. However I've still got the perm locked error (so my doesn't work), and the fp sensor still refuses record fingerprints. Was your phone network unlocked when you made that backup? Idk if that maybe interferes with the sim or something
Guille05 said:
I've flashed your backups and the NT Code error indeed disappeared. However I've still got the perm locked error (so my doesn't work), and the fp sensor still refuses record fingerprints. Was your phone network unlocked when you made that backup? Idk if that maybe interferes with the sim or something
Click to expand...
Click to collapse
Yes,it was network unlocked for sure.You're not the only one that has faced this after trying to repair the IMEI.It's perma blocked because it's embedded in the chipset itself,and so far I haven't seen any fix for it as of yet.