[CLOSED]Anyone knows how to re-write IMEI of LMV600AM? - LG V60 ThinQ Questions & Answers

I recently has the issue that the network(sim) is "permanently locked".
So I overwrote the factory firmware and went to SVC Menu > MID to rewrite the IMEI and S/N, but unlike the T-mobile version, AT&T did not have a red Gen button for rewrite. Perhaps there was a compatibility problem using the initial firmware for T-mobile. Does anyone have the initial firmware for AT&T's LMV600AM? Or does anyone know how to rewrite IMEI and S/N in LMV600AM?

Even you could write it in mid info
Network still locked.
For at&t version there is on way to open network it's restoring your mobile lun5 only.

rifay78 said:
Even you could write it in mid info
Network still locked.
For at&t version there is on way to open network it's restoring your mobile lun5 only.
Click to expand...
Click to collapse
OK. but my lun5 is already network-locked one. Then, no way to solve this problem?
I think I need "LMV600AM firmware dump files" and "LMV600AM IMPL 0 files".

You need your mobile original dump before flashing any rom or erasing your original rom

rifay78 said:
You need your mobile original dump before flashing any rom or erasing your original rom
Click to expand...
Click to collapse
what "your mobile original dump" means? LG V60 ATT dump files? or my phone's backups

fukko123 said:
what "your mobile original dump" means? LG V60 ATT dump files? or my phone's backups
Click to expand...
Click to collapse
Fukko,I seen your post over on Hova.I'm working on it with the V60tm files that was posted,but nothing as of yet.So far all I'm getting is blank boxes under MID.I'll keep working with it,but it's not looking to promising as of yet.I'm currently testing it on a blacklisted V60 AT&T variant.I'll post back if I find a way around it.

Thread Closed.
IMEI tampering is illegal in most countries, thus it cannot be discussed in XDA.
See rule 9:
9. Don't get us into trouble.
Don't post copyrighted materials or do other things which will obviously lead to legal trouble. If you wouldn't do it on your own homepage, you probably shouldn't do it here either. This does not mean that we agree with everything that the software piracy lobby try to impose on us. It simply means that you cannot break any laws here, since we'll end up dealing with the legal hassle caused by you. Please use common sense: respect the forum, its users and those that write great code.
Click to expand...
Click to collapse

Related

[Q] Galaxy Core Duos IMEI Lost after flash

Hi,
I've flashed a new rom in my Samsung Galaxy Core Duos (i8262b) but I forgot to do the f*cking IMEI Backup...
Result: My phone is giving that message of "not registered on network"...
What I've tried:
- New roms...
- Old roms...
How can I fix this?
fmatheus2003 said:
Hi,
I've flashed a new rom in my Samsung Galaxy Core Duos (i8262b) but I forgot to do the f*cking IMEI Backup...
Result: My phone is giving that message of "not registered on network"...
What I've tried:
- New roms...
- Old roms...
How can I fix this?
Click to expand...
Click to collapse
Reflash the modem. If that doesn't work, then reinstall the whole firmware. Is the IMEI still there? Listed as 000049 or unknown?
es0tericcha0s said:
Reflash the modem. If that doesn't work, then reinstall the whole firmware. Is the IMEI still there? Listed as 000049 or unknown?
Click to expand...
Click to collapse
Already tried this... the IMEI is still there, but now is different of the one under the battery... this is too strange. The number changed exactly after the first flash...
fmatheus2003 said:
Already tried this... the IMEI is still there, but now is different of the one under the battery... this is too strange. The number changed exactly after the first flash...
Click to expand...
Click to collapse
What's the beginning of the number? 0's? What file did you flash?
es0tericcha0s said:
What's the beginning of the number? 0's? What file did you flash?
Click to expand...
Click to collapse
The beggining of the IMEI is 35... I've flashed the full firmware, not just one or two files... the firmwares of this phone are packed in one single file... Found it in samfirmware...
And there is no modem.bin if I extract the tar.md5 file...
fmatheus2003 said:
The beggining of the IMEI is 35... I've flashed the full firmware, not just one or two files... the firmwares of this phone are packed in one single file... Found it in samfirmware...
And there is no modem.bin if I extract the tar.md5 file...
Click to expand...
Click to collapse
Hmm. That doesn't really make any sense. I've never heard / seen the IMEI changing to another actual IMEI number from the result of flashing (and I do this kind of stuff for a living and read here A LOT - untold hours a week). Only null IMEIs or when it changes to 00000049xxx kind of thing. You're certain you installed the correct firmware for your device?
es0tericcha0s said:
Hmm. That doesn't really make any sense. I've never heard / seen the IMEI changing to another actual IMEI number from the result of flashing (and I do this kind of stuff for a living and read here A LOT - untold hours a week). Only null IMEIs or when it changes to 00000049xxx kind of thing. You're certain you installed the correct firmware for your device?
Click to expand...
Click to collapse
Yes, the firmware is correct.. see: My phone is GT-I8262B... I've tried all firmwares in the list of samfirmware. One of the archives that I've flashed is I8262BVJANB1_I8262BZTOANB1_ZTO.tar.md5 that is the original firmware that comes in the phone...
And your certain that the IMEI was the same BEFORE you flashed? I just can't even fathom how that would be possible. I'm not convinced it is. lol
es0tericcha0s said:
And your certain that the IMEI was the same BEFORE you flashed? I just can't even fathom how that would be possible. I'm not convinced it is. lol
Click to expand...
Click to collapse
Man, I double checked the IMEI before the flash (because I like to have all my IMEI's in a file, just in case of a robbery I need to put it on the blacklist)... I'm sure the IMEI of the phone before the flash was the same of the one under the battery. The thing is tha I've too never ever see anything like this! It's too (TOO) strange for me too...
Well, if that did happen, then I'm pretty certain there is nothing that you could do yourself to fix. At this point, I believe you would need the help of a service center that has the equipment to actually change the IMEI. All the fixes you will find here is for if the IMEI is wiped or changed to the 0049xxxx one. The tools to fix this kind of thing probably cost as much as your phone would if not more and it's not something for the average shop has or knows how to do, at least that's how it is in most places I have seen (I'd love to have one of these for my shop, but it happens rarely, so not enough $$$ in it at the moment to make it worthwhile). Maybe it's different for your location.
es0tericcha0s said:
Well, if that did happen, then I'm pretty certain there is nothing that you could do yourself to fix. At this point, I believe you would need the help of a service center that has the equipment to actually change the IMEI. All the fixes you will find here is for if the IMEI is wiped or changed to the 0049xxxx one. The tools to fix this kind of thing probably cost as much as your phone would if not more and it's not something for the average shop has or knows how to do, at least that's how it is in most places I have seen (I'd love to have one of these for my shop, but it happens rarely, so not enough $$$ in it at the moment to make it worthwhile). Maybe it's different for your location.
Click to expand...
Click to collapse
Man... I'm in Brazil... if something is different here is worst...hehehe
Well If you think that an iPhone here starts at 2.800 Reais, wich is almost 1.300 dollars... and with this world cup the things are becoming more and more expensive here... if you are coming to the cup know this: you will be robbed... it's not a possibility: it's a fact...
So, I will send this thing to the servisse center and see how much will they drain of my wallet...
Thanks for everything, guy! You was very nice!!!
$1300? That's robbery itself right there... lol The equipment needed to do stuff like this is usually anywhere from 300-500 USD typically between the box and software or server connection access.
SRS (Samsung Remote Server)
Octopus Box
NS Pro
SPT Box
Something along those lines.
You could maybe see if this is helpful:
http://forum.xda-developers.com/showthread.php?t=1518694
But doubt it works on many(any?) newer Samsung due to other changes they have made to how this stuff works.
I am facing same problem

galaxy s3 i9300 incorrect imei

It's been a while my S3 has been dead now, virtually rendering it into a WiFi tablet. Let me give a backstory.i had originally bought the phone and it was running 4.0.4, rooted. I wanted to go onto a different software so I came across Cyanogenmod. I flashed it with the automatic tool on pc. It had been quite some time I was running it, until I decided that I wanted to go back to stock. I was a complete noob back then, and where I may now a lot more stuff about phones now, there is still alot to learn. Anyway, I decided to flash a rom called "Back to noot", using twrp. The flash had gone successfully however I booted up to find that I had the infamous circle with the line through it, where the signal should be. I did some more digging and had concluded that my efs had been corrupted. As I was a complete noob, I didn't know what the efs partition was and I hadn't made a backup of it. So I was without a phone basically. Recently though I flashed the latest stock 4.3 rom onto it. My IMEI and baseband are back. However my IMEI isn't correct, the last couple of digits are incorrect, resulting in me having to face the "not registered on network". This is where I am now. I'm without my correct IMEI. Can anyone please help me restore my original IMEI? I have seen on some forums where some people have flashed down to 4.0.4 to successfully recover their phone. However sammobile now requires a premium account to download a 4.0.4 rom for the i9300, weirdly. Can anyone help me to restore the IMEI? Thanks.
You can download firmware for the i9300 on fw.updato.com . Search for the i9300 and filter by version to find the one you want. I am not sure if it is possible to restore your imei without an efs backup though. Good luck
Are you referring to the digits after the "/"?
I've never heard that dowgrading the stock ROM would change the imei.
audit13 said:
Are you referring to the digits after the "/"?
I've never heard that dowgrading the stock ROM would change the imei.
Click to expand...
Click to collapse
The entire IMEI is correct until I reach a certain point.
After the 3rd dash on the back of the phone, the digits follow "182/9". However when dialing *#06# on the phone itself the digits "4344/15". This is what I feel is causing the "not registered on network" error. I never knew downgrading can restore the phone. Ive seen on a forum that someone had recovered their phone by rolling from a higher firmware down to 4.0.4
Sent from my S6 Edge+ using XDA Labs
Was the phone purchased brand new, used, or refurbished?
If the phone is running a stock 4.3 ROM, you can't flash an older ROM as the phone will not allow flashing an older bootloader.
audit13 said:
Was the phone purchased brand new, used, or refurbished?
If the phone is running a stock 4.3 ROM, you can't flash an older ROM as the phone will not allow flashing an older bootloader.
Click to expand...
Click to collapse
The phone was purchased used. If I cannot flash an older version of Android does this mean it's no hope?
Sent from my S6 Edge+ using XDA Labs
It's very unusual that the imei would change on its own. It would be even more unusual for the imei to change when flashing one stock ROM over another. I suppose it is possible but I have never come across a situation where such a thing has happened.
Since the imei on the label does not match the imei in the phone and it was a used purchase, I tend to believe the phone is a "frankenphone" in that it was put together with parts from different phones.
Did you check to see if the imei from dialling *#06# belongs to an s3?
audit13 said:
It's very unusual that the imei would change on its own. It would be even more unusual for the imei to change when flashing one stock ROM over another. I suppose it is possible but I have never come across a situation where such a thing has happened.
Since the imei on the label does not match the imei in the phone and it was a used purchase, I tend to believe the phone is a "frankenphone" in that it was put together with parts from different phones.
Did you check to see if the imei from dialling *#06# belongs to an s3?
Click to expand...
Click to collapse
Actually I haven't checked to see if it does. Do you know how I can?
Sent from my S6 Edge+ using XDA Labs
Type the imei #s in here: https://swappa.com/esn?ref=mobilenations&data1=UUwpUvbUpU2855846YYw
Sent from my S6 Edge+ using XDA Labs
ABADAZZPLAYER said:
Not sure if it's been done properly but that's what came up
Sent from my S6 Edge+ using XDA Labs
Click to expand...
Click to collapse
Please remove your imei from the post. Enter the first 15 numbers.
audit13 said:
It's very unusual that the imei would change on its own. It would be even more unusual for the imei to change when flashing one stock ROM over another. I suppose it is possible but I have never come across a situation where such a thing has happened.
Since the imei on the label does not match the imei in the phone and it was a used purchase, I tend to believe the phone is a "frankenphone" in that it was put together with parts from different phones.
Did you check to see if the imei from dialling *#06# belongs to an s3?
Click to expand...
Click to collapse
Not if he flashed a firmware or rom based earlier than 4.3 and the phone has been 4.3. Efs changed at 4.3 and going backwards kills the efs partition because 4.2 or earlier can't read the new encryption.
There is a possibility that flashing earlier firmwares can write the imei back in, I've read something about this before. If all else fails then why not try it.. Its borked anyway.
Kies emergency recovery is another method but won't work if the phone was rooted.
I think have an efs of a now dead phone. It was a btu i9300 https://drive.google.com/file/d/1MiFFyCCeh1PFuQVZa-M4woreaofcDmrb/view?usp=drivesdk
shivadow said:
Not if he flashed a firmware or rom based earlier than 4.3 and the phone has been 4.3. Efs changed at 4.3 and going backwards kills the efs partition because 4.2 or earlier can't read the new encryption.
There is a possibility that flashing earlier firmwares can write the imei back in, I've read something about this before. If all else fails then why not try it.. Its borked anyway.
Kies emergency recovery is another method but won't work if the phone was rooted.
I think have an efs of a now dead phone. It was a btu i9300 https://drive.google.com/file/d/1MiFFyCCeh1PFuQVZa-M4woreaofcDmrb/view?usp=drivesdk
Click to expand...
Click to collapse
Is this efs dead or working?
Sent from my S6 Edge+ using XDA Labs
How you use it, no clue. I've never had to. It's from a phone that was eventually killed in an accident.
The files are as they were extracted. I zipped them up myself. It is not in anyway suitable to be flashed as is but if you can get the os working and root it you can copy the files to the correct folder, set the permissions and see what happens..
I thought seeing as I have no use for it someone else can, if they can.
shivadow said:
How you use it, no clue. I've never had to. It's from a phone that was eventually killed in an accident.
The files are as they were extracted. I zipped them up myself. It is not in anyway suitable to be flashed as is but if you can get the os working and root it you can copy the files to the correct folder, set the permissions and see what happens..
I thought seeing as I have no use for it someone else can, if they can.
Click to expand...
Click to collapse
I'll give this a try. Who knows maybe this could work. If it does , lots of thanks to you lol
Sent from my S6 Edge+ using XDA Labs
The phone was successfully recovered by flashing the XXUGMK6 ROM, then flashing the Patched UGMK6 Kernal and Baseband that zuluman had given. However the phone only accepted one SIM card from a couple that I had tried, and the phone thought I was in a roaming state, meaning I couldn't use mobile data. Other than that the text message and phone calling functionality, which was the main focus of the repair, has been successful.
Sent from my S6 Edge+ using XDA Labs

Rooting version H933 (Canadian V30)

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.

LGUp 1.16.3 Patched Found and Works with LG Wing

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.

LG G8X sprint model sensors not working after messy crossflash

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.

Categories

Resources