Database Info

G2X (P999) Baseband Discussion

This was split off from another thread that was getting off track a bit.
http://forum.xda-developers.com/showthread.php?t=1305077
slycog said:
It's not on a partition that is accessible through nvflash, the radio module itself has it's own internal flash (1GB) and it can only be accessed via the baseband itself... in fastboot there is a serial interface that becomes available that allows you to talk directly to the baseband.
The code that i've written is a basic framework to allow communicating directly with the baseband... right now the only thing it does is issue the basic AT and SWV commands. You would need to implement a FBOOT handler to facilitate a baseband flash.
There isn't really a compelling reason to get it working, those people having issues with the KDZ tool will have the same issues with the tool I've written... the KDZ tool barfs on itself because it's not able to find/mount the serial interface. (in the examples that I've seen the LG drivers simply don't function properly preventing the pc from ever making the interface available)
Aside from all of that, usb serial adapters are buggy in general... you get all kinds of weird timing issues... you can attribute most of the failed updates to this. I myself had a bad flash my first go-round with the LG Updater.
As for the firmware with imei, if it's not available via B2C (which i'm pretty sure it is) then it can be obtained through B2B (this is the commercial tool used internally by the carriers). B2B is how the service manuals leak for LG... it's not uncommon for people to sell access to B2B... example here: http://b2b-lg.blogspot.com/
Click to expand...
Click to collapse
If you are talking to the baseband directly then why was Paul's Smartflash able to flash an O2X baseband to a G2X? They are different chips, and so it would seem, that they have different protocols for flashing. Maybe these people haven't actually flashed the baseband but screwed up the RIL layer that talks to the baseband? I don't see how a program that is targeting an Infineon baseband chips was able to flash and screw up a Qualcomm baseband chip. That just doesn't make sense to me. Maybe you can illuminate us on how this happened?

jboxer said:
This was split off from another thread that was getting off track a bit.
http://forum.xda-developers.com/showthread.php?t=1305077
If you are talking to the baseband directly then why was Paul's Smartflash able to flash an O2X baseband to a G2X? They are different chips, and so it would seem, that they have different protocols for flashing. Maybe these people haven't actually flashed the baseband but screwed up the RIL layer that talks to the baseband? I don't see how a program that is targeting an Infineon baseband chips was able to flash and screw up a Qualcomm baseband chip. That just doesn't make sense to me. Maybe you can illuminate us on how this happened?
Click to expand...
Click to collapse
It's highly unlikely that this scenario happened at all, it's more likely someone tried to flash the o2x rom and jacked up their partitions causing a soft brick.
If you look at the P990.dll or what has been renamed model.dll for the smartflash release, check the function at 100048D0... you can trace through and look at the commands it's sending to the baseband, 90% of them simply don't exist in the qualcomm based g2x baseband.
Even if you've never used a disassembler before there is a free copy of IDA or even Ollydbg that you can use to look at the model.dll to confirm.
For clarity, when the program gets unexpected results from commands it's issuing it will fail through and return without doing anything... in this specific example the command "AT%CHIPSET" is issued first to which the g2x simply returns "ERROR"... at this point it doesn't go any further.
Let's say for example that it somehow gets beyond the first command, the commands that are shared between devices that get issued in the o2x update process are very generic... such as "AT%IMEI" which does nothing more then return the device IMEI.

I have a few questions in regard to Baseband updates and if we can take advantage of this.
My Question has been covered throughout this forum, with short answers, here and there. However, I have yet to find a sufficient answer to Baseband, Modems, and Radios.
The reason for these questions, are because my signals are horrible and I know it has nothing to do with the roms, I have used all roms offered by our devs. My fiancées mytouch 4g smokes my lg g2x ( sad sad day)
I have ran “GetRil” on every rom and it shows V21e Matching. I have also tried the recommended kernels for each rom.
I have found, depending on the Phone and the thread the terminology changes. For example, HTC threads speak of Radios and Samsung threads talk about Modems. In this thread I have seen Baseband used quite often. Regardless of the terminology, this is the item that effects the signal connection (and much more).
Currently I am running:
Baseband version
M6600A-SCAUTNZ-2.0.9720T [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
Kernel version
2.6.32.9
BUILD
Custom
Software Version
LG-P999-V21e
Can we extract the baseband from leaks (if leaks exist)?
Is a different baseband a potential benefit for signal issues?
Any information or advise is greatly appreciated

j3.cole said:
I have a few questions in regard to Baseband updates and if we can take advantage of this.
My Question has been covered throughout this forum, with short answers, here and there. However, I have yet to find a sufficient answer to Baseband, Modems, and Radios.
The reason for these questions, are because my signals are horrible and I know it has nothing to do with the roms, I have used all roms offered by our devs. My fiancées mytouch 4g smokes my lg g2x ( sad sad day)
I have ran “GetRil” on every rom and it shows V21e Matching. I have also tried the recommended kernels for each rom.
I have found, depending on the Phone and the thread the terminology changes. For example, HTC threads speak of Radios and Samsung threads talk about Modems. In this thread I have seen Baseband used quite often. Regardless of the terminology, this is the item that effects the signal connection (and much more).
Currently I am running:
Baseband version
M6600A-SCAUTNZ-2.0.9720T [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
Kernel version
2.6.32.9
BUILD
Custom
Software Version
LG-P999-V21e
Can we extract the baseband from leaks (if leaks exist)?
Is a different baseband a potential benefit for signal issues?
Any information or advise is greatly appreciated
Click to expand...
Click to collapse
P999 - No. There are only three known basebands (2 TMO and 1 Wind) and nobody has come up with a way to flash them. We have the .bin file for the baseband that came with the GB update, but no way to flash it. P990 has many basebands because many world versions and due to the baseband chip being different hardware they have a way to flash them.

guys i have a question. its the basebands sames as Radios?
i was just wondering because there are roms for the sensation ported to the sensation 4g and they have a thread were you see all the radios and you just pick the one u need as example we picked the one for tmous and works fine with others roms

gypsy214 said:
guys i have a question. its the basebands sames as Radios?
Click to expand...
Click to collapse
Yes, conceptually anyway. What works on one phone may not work on another.

I have the same July 15 baseband. I updated from the June 15 (Windmobile baseband)
LIke the new one better because my GPS now locks on GB ROM.
With the June 15 baseband, it does not lock on the GPS when using GB ROM.

SL said:
I have the same July 15 baseband. I updated from the June 15 (Windmobile baseband)
LIke the new one better because my GPS now locks on GB ROM.
With the June 15 baseband, it does not lock on the GPS when using GB ROM.
Click to expand...
Click to collapse
That's one of the improvements of the July 15th baseband. It fixed GPS locking problems and it improves WiFi connectivity also. The new baseband chips to everything; radio, wifi, gps, bluetooth, etc. so the baseband code being solid is very important.

SL said:
I have the same July 15 baseband. I updated from the June 15 (Windmobile baseband)
LIke the new one better because my GPS now locks on GB ROM.
With the June 15 baseband, it does not lock on the GPS when using GB ROM.
Click to expand...
Click to collapse
How did you update your WIND baseband? Would you please post your method.

Core Memory said:
How did you update your WIND baseband? Would you please post your method.
Click to expand...
Click to collapse
Most likely he used the KDZ method to force the installation of the Gingerbread udpate. That would also flash the new baseband. You also get the TMO splash screens and bloatware as bonuses.

jboxer said:
Most likely he used the KDZ method to force the installation of the Gingerbread udpate. That would also flash the new baseband.
Click to expand...
Click to collapse
I tried the KDZ method but, although the update started, it got stuck and wouldn't continue. The USB connection was ok and the kdz installer worked. I explained what I did in another thread http://forum.xda-developers.com/showthread.php?p=18844956&posted=1#post18844956
Should I retry with all the steps implemented or is there another method as I ask about.

Core Memory said:
I tried the KDZ method but, although the update started, it got stuck and wouldn't continue. The USB connection was ok and the kdz installer worked. I explained what I did in another thread http://forum.xda-developers.com/showthread.php?p=18844956&posted=1#post18844956
Should I retry with all the steps implemented or is there another method as I ask about.
Click to expand...
Click to collapse
It's been stated numerous times that using virtual PC is extremely buggy... more importantly the tool is inherently buggy anyways for a number of reasons.
The baseband itself gives you a software based vector for updating (you talk to an initialized baseband)... in addition there is an emergency based diagnostic interface for when you fubar a flash... very similar to nvflash for our system nand.
Your concerns in regards to the recovery are also silly as nvflash provides unrestricted low level access to the system nand memory.
Find a Windows XP PC and report back.

same hardware lastest baseband lg-l95g
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I seen this other thread
Where can find lg l95g 's baseband
How to update only baseband
Its really compatible g2x, some tryed flash this baseband to g2x?

sukhochir said:
I seen this other thread
Where can find lg l95g 's baseband
How to update only baseband
Click to expand...
Click to collapse
You've asked and you've been given an answer already. You CANNOT update only the baseband on this phone at this time. Nobody has come up with a way to do it.

More specifically, before you can even think about updating to the prototype baseband you must dump it from the device itself.
Now, because we have extracted the g2x baseband updates from the official kdz files, it is absolutely possible for this guy to force an update to our baseband... which would in theory allow him to use his device on tmobile.

slycog said:
More specifically, before you can even think about updating to the prototype baseband you must dump it from the device itself.
Now, because we have extracted the g2x baseband updates from the official kdz files, it is absolutely possible for this guy to force an update to our baseband... which would in theory allow him to use his device on tmobile.
Click to expand...
Click to collapse
Not sure about that. There is a hidden partition that controls sim lock, etc. That would have to be flashed also to remove the lock. You need special tools to do that.

Deleted - posted in wrong thread.

,When i updated baseband need unlock? , my phone is factory unlocked

sukhochir said:
,When i updated baseband need unlock? , my phone is factory unlocked
Click to expand...
Click to collapse
There are no factory unlocked P999s sold. Only the P990 can be bought factory unlocked. If you bought it unlocked someone unlocked it with a code or special software. The unlock state is kept in a secret hidden partition that you cannot access. Flashing the baseband, which we cannot do, should not change your locked/unlocked state.

A little offtopic but one of the best reasons i loved my old mt4g was how easy it was to flash the radios/baseband thru the bootloader, LG and their godawful drivers/support for this phone just makes me sick. Wish HTC would have made the G2x but kept the tegra chip intact, it's still a nice chip despite having no support from nvidia, played some very nice games with it that put other qualcom/powervr games look ****ty next to it lol

Videotron 2.2 security update rom - NOT Gingerbread

Edit: It turns out this is a 2.2 security patch update. The rom version number doesn't make sense for a Froyo rom. Sorry guys.
Here is a link for the KDZ file for the new Videotron GB rom. Since it was just released I am assuming it is 2.3.4 but I don't know for sure. Once people install it they can do a Nandroid backup and post the system image for the rest of us to download. I suspect it includes an updated baseband also. Once we get confirmation people can use the KDZ method to update their baseband and then flash back to the rom of their choice. If someone does flash it during the flashing process please copy and save all the extracted rom files in the C:\ProgramData\LGMOBILEAX\Phone directory. The phone subdirectory is created by the KDZ Updater and creates a dll and a wpb file. Then the LG Updater will further extract the wpd file into the files it will flash.
http://www.multiupload.com/70DYL7FMHF

Now that's what i am talking about!! Thank you so much jboxer!! Now, step by step what do I do?
Thanks!

rapcenter said:
Now that's what i am talking about!! Thank you so much jboxer!! Now, step by step what do I do?
Thanks!
Click to expand...
Click to collapse
Search for the KDZ method to unbrick a device. Use the same method. I am not going to give you a step by step as that is already in that thread. You can search yourself and find it in the development section.

This is a link to the KDZ method thread:
http://forum.xda-developers.com/showthread.php?t=1180331
However, I am confused about this so-called update, as its number is exactly the same version as the stock 2.2.2 Videotron ROM ("LG-P999-AVC-V21d"). Is it really a 2.3.3 or 2.3.4 ROM? I'll try it out but I am skeptical...

GenghisKhan67 said:
This is a link to the KDZ method thread:
http://forum.xda-developers.com/showthread.php?t=1180331
However, I am confused about this so-called update, as its number is exactly the same version as the stock 2.2.2 Videotron ROM ("LG-P999-AVC-V21d"). Is it really a 2.3.3 or 2.3.4 ROM? I'll try it out but I am skeptical...
Click to expand...
Click to collapse
The rom designations are done on a carrier by carrier basis based on how many builds LG does before they have a final release. It has nothing to do with any other roms. The previous rom for Videotron was a v11 rom. When LG jumps the number by 10, it is always a newer version of the OS. It should be a GB rom. We just don't know if 2.3.3 or 2.3.4 until someone flashes it.

Ok, tried the update using my trusty XP Mode virtual machine and got a "failed to decode the file you specify" in the KDZ Updater.

GenghisKhan67 said:
Ok, tried the update using my trusty XP Mode virtual machine and got a "failed to decode the file you specify" in the KDZ Updater.
Click to expand...
Click to collapse
Make sure you got a complete download. The file is 181Mb in size. I was able to get the KDZ program to extract the .dll and the .wdb file but after that if a phone is not attached it won't launch the LG Updater.

GenghisKhan67 said:
Ok, tried the update using my trusty XP Mode virtual machine and got a "failed to decode the file you specify" in the KDZ Updater.
Click to expand...
Click to collapse
As stated in big bold letters in the link jboxer posted.
Note: You MUST do this via a PC running Windows XP. Running Vista/7 in compatibility mode is not going to work, period.

jboxer said:
Here is a link for the KDZ file for the new Videotron GB rom. Since it was just released I am assuming it is 2.3.4 but I don't know for sure. Once people install it they can do a Nandroid backup and post the system image for the rest of us to download. I suspect it includes an updated baseband also. Once we get confirmation people can use the KDZ method to update their baseband and then flash back to the rom of their choice. If someone does flash it during the flashing process please copy and save all the extracted rom files in the C:\ProgramData\LGMOBILEAX\Phone directory. The phone subdirectory is created by the KDZ Updater and creates a dll and a wpb file. Then the LG Updater will further extract the wpd file into the files it will flash.
http://www.multiupload.com/70DYL7FMHF
Click to expand...
Click to collapse
Where's the original source for the Videotron LG P999 update? I looked around Videotron's website and couldn't find it.
Update
I found it on LG Canada's website: http://www.lg.com/ca_en/support/mc-support/mobile-phone-support.jsp
I phoned LG Canada. The CSR told me that it is not an Android update, it is just a patch for Videotron's LG-P999 phones which have a problem receiving text messages.

I am updating right now.
I am at 4% after 4 .30 minutes. (Will update this post as I go)
Still stuck at 4% after 6.51 minutes
After 10.18 minutes still at 4% (now wondering if there is a problem. I have used KDZ numerous times - over 10 phones and have never been this long stuck on the 4% (the Update on the LG SW still flashing. The Phone hows SW upgrade..please wait
At 14.13 minutes..still at 4%
REad Core Memory post.
Did exactly what he did.
Rebbot phone. Install CWM 5.02
Install weapon.Phone still shows as SW upgrade. (even though weapon install was successfil)
I will play with it a bit later. Need to get back to work
jboxer said:
Here is a link for the KDZ file for the new Videotron GB rom. Since it was just released I am assuming it is 2.3.4 but I don't know for sure. Once people install it they can do a Nandroid backup and post the system image for the rest of us to download. I suspect it includes an updated baseband also. Once we get confirmation people can use the KDZ method to update their baseband and then flash back to the rom of their choice. If someone does flash it during the flashing process please copy and save all the extracted rom files in the C:\ProgramData\LGMOBILEAX\Phone directory. The phone subdirectory is created by the KDZ Updater and creates a dll and a wpb file. Then the LG Updater will further extract the wpd file into the files it will flash.
http://www.multiupload.com/70DYL7FMHF
Click to expand...
Click to collapse

SL said:
I am updating right now.
I am at 4% after 4 .30 minutes. (Will update this post as I go)
Still stuck at 4% after 6.51 minutes
After 10.18 minutes still at 4% (now wondering if there is a problem. I have used KDZ numerous times - over 10 phones and have never been this long stuck on the 4%
Click to expand...
Click to collapse
I had that happen to me too when I tried to install the T-Mobile update. After the same problem occurred a few times, I left it at 4% for a while then installed Weapon 3 and it booted with the updated baseband. Apparently, the baseband is the first thing that gets flashed and it may already be installed even though the update is stuck at 4%.

GTWalling said:
As stated in big bold letters in the link jboxer posted.
Note: You MUST do this via a PC running Windows XP. Running Vista/7 in compatibility mode is not going to work, period.
Click to expand...
Click to collapse
I'm running a virtual machine, same as a native XP install. "XP Mode" is NOT the same as "compatibility mode".
jboxer said:
Make sure you got a complete download. The file is 181Mb in size. I was able to get the KDZ program to extract the .dll and the .wdb file but after that if a phone is not attached it won't launch the LG Updater.
Click to expand...
Click to collapse
The download was completed with no error and is the correct size. As I stated above, the process starts but finishes with the error message I posted previously.
That said, I updated the phone using the default Videotron stock ROM referenced in the LG Updater and that worked fine, but that's only on version 2.2.2.

GenghisKhan67 said:
XP Mode is not the same as compatibility mode. I'm running a virtual machine, which is exactly the same as running XP natively. The update craps out because the KDZ file is no good.
Click to expand...
Click to collapse
You're half right. But that also makes you half wrong. I'm a computer tech, so I'm familiar with the fact that running something in an emulated environment isn't the exact same thing as running in a real environment. You're running a virtual machine, it's an emulation, not the real thing, programs don't always work the same under emulation versus the real world (for lack of a better term). If this is that big of a deal to you, go find a place, such as a copy shop, where you can run the necessary software from inside XP, either that or set yourself up with a dual boot.

Волк said:
You're half right. But that also makes you half wrong. I'm a computer tech, so I'm familiar with the fact that running something in an emulated environment isn't the exact same thing as running in a real environment. You're running a virtual machine, it's an emulation, not the real thing, programs don't always work the same under emulation versus the real world (for lack of a better term). If this is that big of a deal to you, go find a place, such as a copy shop, where you can run the necessary software from inside XP, either that or set yourself up with a dual boot.
Click to expand...
Click to collapse
Everything other than flashing the KDZ works under the virtual machine without a hitch, including flashing CWM with the nVidia updater. The problem is with the KDZ file. My phone is detected, no problem, APX drivers installed, the works. I'm not going to type out all the messages that flew by, the process starts but eventually stops. Not a good sign.
Oh, and BTW, I've been working in the IT industry for over 25 years, so I think I have a pretty good understanding what will work or not in a virtualized environment VS native OS, so spare me the condescension.

GenghisKhan67 said:
Everything other than flashing the KDZ works under the virtual machine without a hitch, including flashing CWM with the nVidia updater. The problem is with the KDZ file.
Oh, and BTW, I've been working in the IT industry for over 25 years, so I think I have a pretty good understanding what will work or not in a virutalized environment VS native OS, so spare me the condescending tone.
Click to expand...
Click to collapse
But I spare so few the condescending tone. Especially know-it-alls. So, please, spare the rest of us yours and we'll call it even on that.
I really don't care how long you've been in the industry and the IT industry covers a lot so for all we know you could be a networking guru who knows crap about fixing computers but knows networking inside and out.
And if a program absolutely has to be run in XP it sounds more like a failing in the program since most programs have worked better on Windows 7 than they did on XP. But this thread isn't about that.

Волк said:
I really don't care how long you've been in the industry and the IT industry covers a lot so for all we know you could be a networking guru who knows crap about fixing computers but knows networking inside and out. /QUOTE]
So why did you bring it up in the first place? If you know so much about this, how about helping us test this out instead of whining? You're not being helpful at all.
Click to expand...
Click to collapse

Isn't it ironic that the LG drivers and KDZ update work well in Windows running virtually on a Mac?

Core Memory said:
Isn't it ironic that the LG drivers and KDZ update work well in Windows running virtually on a Mac?
Click to expand...
Click to collapse
If it does, that's great. I guess this means we should expect a download link from you shortly?

Since that thread on how to unbrick many moons ago -- People reported that they did in fact get things working in Win7/Vista; It just had a lot lower success rate. People also got it going in XP mode / Virtual environments. So an actual XP machine isn't 100% necessary, it was just the most successful method.

speedsk8x said:
Since that thread on how to unbrick many moons ago -- People reported that they did in fact get things working in Win7/Vista; It just had a lot lower success rate. People also got it going in XP mode / Virtual environments. So an actual XP machine isn't 100% necessary, it was just the most successful method.
Click to expand...
Click to collapse
I was just gonna say, I updated my phone to the July 15 baseband using 64-bit Win 7 using this guide:
http://forum.xda-developers.com/showthread.php?t=1332350
I don't think XP is required at all, it's just a false myth, most people's issues stem from the fact that you need to have a stock ROM for a KDZ file to flash properly (IE you can't update your baseband/flash a .kdz with CM7 installed).
You'd need to follow a guide this like:
http://forum.xda-developers.com/showthread.php?t=1048274
to flash back to a stock Froyo or Gingerbread ROM, and probably use NVFlash to put stock recovery back on too.
... Perhaps in the future instead of bragging to each other about how much IT experience you have just find a solution to the problem and post that instead...

From Hellfire to Stock ROM

Hello all,
I have the "call sound" problem with Hellifire ROM as I didn't upgrade my baseband. In order to do to it I read that I have to return to stock ROM, update the baseband and then put Hellfire or whatever other ROM back again.
My question is how to go back to the stock rom. I did try the CWM way several times but no result. Is there any step by step guide I should follow elsewhere?
Thank you very much!

Here you go
http://forum.xda-developers.com/showthread.php?t=1674901
Just use the search function next time, you can expect a lot of people to comment the same thing.
Sent From My Handheld Portal Device

I don't think he made any effort to find the answer himself. A search wasn't even necessary considering the link you posted is located on the second page of general. Had he just went to the second page and scrolled down, he would have found it.
Anyway, I'm also contributing to this thread: http://forum.xda-developers.com/showthread.php?t=1696266
That's the method I used in order to update my baseband OTA. It was simple. All you need to do is dowload a stock nandroid that you can easily find on the development section if you don't have one of your own.

The way I did mines was download xboarders LG ota 2.3.3 rom from rom manager, use nvflash to flash stock recovery, use superoneclick to unroot, then ran LG tool. But I heard people say as long as your on stock 2.3.3 rom you don't need to unroot. But I wanted it stock less chance of something going wrong
Sent from my LG-P999 using xda app-developers app

Instead of attacking you should read what I'm writing... I said that I did the CWM method several times but no result. I did also what your links suggested but nothing again.
Any other suggestion. While back in "stock" version, v10f or v21e I'm trying to update to the new baseband but my process stops at 4%.
I have tried removing the battery and turning it on again -> NOTHING
I have tried reboot and hold VOL DOWN and POWER -> NOTHING (CWM is still installed)
Any other input will be highly appreciated.

There are several suggestions in that thread to get the baseband to update, you tried all of them?
Reinstall the LG drivers
Attempt to update with V21E Stock ROM AND Stock Recovery
use the kdz method with the V21Y file (being on the 2.3.4 Stock ROM makes this go quicker according to posts in thread)
What operating system do you use also? Do you have admin rights?
If anything this should get the call audio to work even on the old baseband if you flash it on top of the ROM as the new baseband has shown no improvement for anything in my personal experience: http://www.mediafire.com/?ducdiqhcuaje5y2

AT&T H810 Back to Stock Guide (TOT Method)

Use this at your OWN RISK! No responsible for anything you do to your phone.
2015 (updated with pictures) TOT Method!
RETURN TO STOCK TOT METHOD for AT&T H810 !!
How to Flash YouTube Video:
1. Download Everything!
1.1) Download Both Stock Image & DLL File – Download HERE & DLL File HERE
1.2) Download LG FlashTools V1.8 - Setup_LGFlashTool_1.8.1.1023.exe - 9.3 Mb
1.3) Download Drivers (Any LG Phone) - Here (Verizon Only) – Here
1.4) Megalock DLL File - Megalock.dll Download
Install:
2. Install LG Drviers
3. Install Flashtool (Don’t run it yet)
4. Extract the TOT file from the Zip
5. Copy MegaLock.dll file to C:\LG\LGFlashtool (This might be a hidden folder so enable "hidden folders". Replace the old MegaLock.dll file)
6. Power off your Device & or pull battery (G3),(G Pro),(G Flex)
7. Press and hold the Vol UP Key and plug in the USB cable to your phone you should now see “Firmware Update/Download Mode” and be in Download mode.
8. Open up Device Manger on your PC
8.1) Click on ports and double click LGEModem
8.2) Go to Port Settings Tab and click Advanced
8.3) Change COM Port to COM41 and click Okay.
8.4) After this you may need to rereboot your phone back into download mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
9. Run LG Flashtool as Administrator
10. Select Manual Mode at the top
11. Click The DLL Box and choose the DLL file from Above meant for your device
12. Click the S/W box and select the firmware file with the .tot extension, Then Click OK when done.
13. Now Click the Yellow Arrow Button at the top left, The Firmware install will be triggered
14. You may need to unplug/replug phone before Firmware install will start (If it does nothing after clicking the yellow button
15. Should take anywhere between 4-8 Minutes, When its done your phone should reboot
16. LG G3 Only, After reboot you will be presented with a Factory reset screen, Just pull battery and put it back in and it should boot right up!
Do NOT Close the FlashTool Window during firmware update.
99% of the time FlashTool will FAIL after 85% anything after 85% is just your phone rebooting so your safe
​File provided in thanks to an anonymous donate .
Feel Free to support me by helping with Server Costs and Coffee if you feel my work has helped you Thank you!

Just a little info on the upgrade/downgrade ordeal: Thanks to @autoprime
autoprime said:
Ok... alrighty... so.. AT&T H810 10O is "V2"
H810 10A was V0. then there was 10E and 10G which were V1.
I saw mention of a 10l but I have no idea about that at all. could be V1.. or could be V2. haven't seen the files for that. anyway.. doesn't matter. forget about 10l
H810PR KDZ's were all V1.
basically unless you are on 10A and holding out for a bootloader exploit on V0... this TOT is completely safe to use regardless of what current version you are on. For example, you could be on 10g (V1) and still flash this TOT safely.. it would just increase the qfuse from V1 to V2.
V2 is no more locked down than V1... so there's no worry about losing your current v1 and no need to stay on 10E or 10G. 10A V0 is the only version worth holding onto.
Of course "V3" may come with android M... but too early to say one way or another on that. if M is indeed V3.. then anyone that upgraded to M could no longer flash this TOT. Hopefully the USA carriers knock it off with increasing the qfuse versions tho and it stops at v2. I will edit the previous sentence after Android 6.0 M comes out for H810 to confirm.
H810PR info: If there is an AT&T user who previously flashed H810PR KDZ to unbrick.. they should be safe flashing this 10o TOT if they want to get back into AT&T land.. hopefully fixing their green camera issue. H810PR users who have an original H810PR (not a converted att h810) should NOT use this TOT as it will increase your qfuse from V1 to V2 and you'll be stuck with AT&T software... plus there's just no point in using it since H810PR has official KDZs.
so.. summary. 10o is v2. everyone on an AT&T H810 can flash this safely without fear of bricking.. as there is no higher qfuse version yet. AT&T H810 users who "converted" to H810PR can safely flash the TOT. Original H810PR users should avoid flashing this TOT as they'll get stuck on V2 AT&T software. The only other users who should maybe try not using it are those on 10A V0 who are holding out for bootloader unlock.
:good:
Click to expand...
Click to collapse

Have you Tested this on an H810, or did someone just donate the .tot file? Would this also restore the /persist partition removing the RCTD flags?
[edit] updated Question to something that makes sense.

Waiting on DLL file. Thank you so much
Sent from my A0001 using Tapatalk

The download is posted in the general g4 thread.

Will this upgrade from an earlier version say 10g or 10i?

TheJokah said:
Will this upgrade from an earlier version say 10g or 10i?
Click to expand...
Click to collapse
Yes, you can use this on any Previous version. If you are on 10A you might want to hold off since this is the only version with qfuse V0, otherwise you are safe to use.

Am I missing where the DLL file is linked? I can't seem to find it in the links provided.

jpwarne said:
Am I missing where the DLL file is linked? I can't seem to find it in the links provided.
Click to expand...
Click to collapse
Check out @utoprime's Tweet: https://twitter.com/utoprime/status/665415181154037762?s=09
Link is in the thread from his tweet

warri said:
Check out @utoprime's Tweet: https://twitter.com/utoprime/status/665415181154037762?s=09
Link is in the thread from his tweet
Click to expand...
Click to collapse
only the .tot file not the DLL

So unless someone has the DLL file, it will need to be bought. I found it but sadly the site charges $20 for it. If I had the extra I'd buy it and rehost it. (if its legit anyway)
EDIT: Try this! http://oceanhost.eu/jvoa0qy97tkf/LGUP_8974.dll.htm let me know if it works, if so I'll add it to the OP Thanks.

hyelton said:
So unless someone has the DLL file, it will need to be bought. I found it but sadly the site charges $20 for it. If I had the extra I'd buy it and rehost it. (if its legit anyway)
EDIT: Try this! http://oceanhost.eu/jvoa0qy97tkf/LGUP_8974.dll.htm let me know if it works, if so I'll add it to the OP Thanks.
Click to expand...
Click to collapse
Link me the site, i'll buy it. I got $20 to waste

kazak1911 said:
Link me the site, i'll buy it. I got $20 to waste
Click to expand...
Click to collapse
Try the above DLL first, might not need it

hyelton said:
Try the above DLL first, might not need it
Click to expand...
Click to collapse
The DLL above worked perfectly!! my AT&T LG G4 (H810PR) got back to stock (H810 10o). Thanks for all your work !! it's been 3 months of waiting patiently for this. Now, all we need is a rooted .img of this H810 10o. Do you know anyone has done it yet?
P/S: Green dot camera issue is gone!!

kazak1911 said:
The DLL above worked perfectly!! my AT&T LG G4 (H810PR) got back to stock (H810 10o). Thanks for all your work !! it's been 3 months of waiting patiently for this. Now, all we need is a rooted .img of this H810 10o. Do you know anyone has done it yet?
P/S: Green dot camera issue is gone!!
Click to expand...
Click to collapse
YES YES & YES! Awesome! Well I think you are the first at it then unless others already figured out the dll file. I'm glad its fixed for you. Not sure on anything about root

i've never done a root img before. So i'm not sure if I am gonna do it right. But the tot and dll absolutely work. im running stock with full of bloatware now. But I love the way it really fix the green dot issue.

kazak1911 said:
i've never done a root img before. So i'm not sure if I am gonna do it right. But the tot and dll absolutely work. im running stock with full of bloatware now. But I love the way it really fix the green dot issue.
Click to expand...
Click to collapse
So..the green issue was a software bug after all...:good:
you can find here both stock and rooted 10o

So I've got my phone in a boot loop. No idea why. It just happened out of the blue.
Tried following instructions here, the flash tool stops working midway when the phone tries to reboot, and is unable to reconnect. Flashtool shows the error "We can't communicate with your phone"
First time, the progress percentage was at 44%. The next time, it was 25% before the phone reboot, and got stuck. Next time it was 49%.
Any help would be appreciated. :3

taurius1 said:
So I've got my phone in a boot loop. No idea why. It just happened out of the blue.
Tried following instructions here, the flash tool stops working midway when the phone tries to reboot, and is unable to reconnect. Flashtool shows the error "We can't communicate with your phone"
First time, the progress percentage was at 44%. The next time, it was 25% before the phone reboot, and got stuck. Next time it was 49%.
Any help would be appreciated. :3
Click to expand...
Click to collapse
try different cable and/or usb slot

After getting back to stock o, phone isn't seeing any update available for 2 days. Has anyone else been able to take the ota update?

(XT1575) Moto X Pure February 24.201.3. update flashable modem

Here's a flashable zip of the newest modem for Moto x pure xt1575. I recommend to backup efs before flashing...figured id share for those interested
Flash at your own risk:
...remember to make a efs backup first...
https://www.androidfilehost.com/?fid=24438995911969212
Thanks to @Spasticdroid for images
And whoever made the flashable zip for the intial MM update

Google~Android said:
Here's a flashable zip of the newest modem for Moto x pure xt1575. I recommend to backup efs before flashing...figured id share for those interested
Flash at your own risk:
https://www.androidfilehost.com/?fid=24438995911969212
Thanks to @Spasticdroid for images
And whoever made the flashable zip for the intial MM update
Click to expand...
Click to collapse
Flashed with TWRP 3.0.0 and got no service/signal of any kind. Only wifi. Flashed an old modem zip I had and still did not fix the problem. Restoring the EFS backup I made prior to the initial flash returned everything to normal. Anything I did wrong or didn't understand?
Running 2-26 AOKP build

crowmallet said:
Flashed with TWRP 3.0.0 and got no service/signal of any kind. Only wifi. Flashed an old modem zip I had and still did not fix the problem. Restoring the EFS backup I made prior to the initial flash returned everything to normal. Anything I did wrong or didn't understand?
Running 2-26 AOKP build
Click to expand...
Click to collapse
Same issue here.

crowmallet said:
Flashed with TWRP 3.0.0 and got no service/signal of any kind. Only wifi. Flashed an old modem zip I had and still did not fix the problem. Restoring the EFS backup I made prior to the initial flash returned everything to normal. Anything I did wrong or didn't understand?
Running 2-26 AOKP build
Click to expand...
Click to collapse
defvayne said:
Same issue here.
Click to expand...
Click to collapse
Idk... Maybethe rpm images r needed... I flashed it right before i uploaded it... It took about 20 seconds to find my imei and network and then since then all go.... I even proir had an issue wit my fone randomly showong i had. No sim inserted and since i flashed the new update and then flashed aosp roms i habe on the problem twice... So idk what it is.. Oh well that why the first thing a fone should do after twrp is a safely Kept efs backup
Edit... Just flashed another rom along wit the modem just to test and everything worked great...

Google~Android said:
Here's a flashable zip of the newest modem for Moto x pure xt1575. I recommend to backup efs before flashing...figured id share for those interested
Flash at your own risk:
...remember to make a efs backup first...
https://www.androidfilehost.com/?fid=24438995911969212
Thanks to @Spasticdroid for images
And whoever made the flashable zip for the intial MM update
Click to expand...
Click to collapse
Something is not right here.
File sizes are completely different compared to the recovery images from motorola. See pics below:
OP's file contents:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Contents from the motorola update:
Difference in unpacked image size. My guess is the OP's images are of the entire partition while the motorola ones are of just the file contents. Still, some folks having identical issues warrants further research.

gpz1100 said:
Something is not right here.
File sizes are completely different compared to the recovery images from motorola. See pics below:
OP's file contents:
Contents from the motorola update:
Difference in unpacked image size. My guess is the OP's images are of the entire partition while the motorola ones are of just the file contents. Still, some folks having identical issues warrants further research.
Click to expand...
Click to collapse
I can promise u there were pulled from the zip in the general section of the February update....extracted the previous modem band 12 fix zip and replace the 2 files... That all i did

gpz1100 said:
Something is not right here.
File sizes are completely different compared to the recovery images from motorola. See pics below:
OP's file contents:
Contents from the motorola update:
Difference in unpacked image size. My guess is the OP's images are of the entire partition while the motorola ones are of just the file contents. Still, some folks having identical issues warrants further research.
Click to expand...
Click to collapse
Could you share link to where you got the stock February firmware

Guys, PLEASE STOP THE UNNECESSARY QUOTING!!! Surely it's possible to reply without automatically quoting or edit the quote out.
I got the firmware by requesting it through motorola. I believe there's a thread on here that's mirroring it but don't have the link. Look in the general or Q&A subsections. Should be on the first or second page.

Following
Sent from my XT1575 using Tapatalk

gpz1100 said:
I got the firmware by requesting it through motorola. I believe there's a thread on here that's mirroring it but don't have the link. Look in the general or Q&A subsections. Should be on the first or second page.
Click to expand...
Click to collapse
That is odd, because i requested the link from Motorola as well and my folder sent from them does not Say Feb 2016 in the title anywhere.
The contents are also diff file sizes as well.
I looked at all the linked mirrors and they all point to the one i have.
look at this pic, yours is on the left, mine on the right.

^^I added the feb 2016 to the name to better distinguish between all the firmware files. After a while it gets hard to figure out which one is what.
Yours looks nearly identical. The difference is you're looking at explorer which shows file size in terms of KB, mine shows actual byte size. Do a properties on each file and you'll see the actual size too. Windows 101.

gpz1100 said:
^^I added the feb 2016 to the name to better distinguish between all the firmware files. After a while it gets hard to figure out which one is what.
Yours looks nearly identical. The difference is you're looking at explorer which shows file size in terms of KB, mine shows actual byte size. Do a properties on each file and you'll see the actual size too. Windows 101.
Click to expand...
Click to collapse
Thanks for the window's 101, did not know that..
But it looks like that's your answer too.. The build that you have is identical to mine. Meaning that we are on the November 1 2015 security patch. OP uploaded the differences from the new February 1 2016 update.

cangri87 said:
Thanks for the window's 101, did not know that..
But it looks like that's your answer too.. The build that you have is identical to mine. Meaning that we are on the November 1 2015 security patch. OP uploaded the differences from the new February 1 2016 update.
Click to expand...
Click to collapse
That's the weird part, files within the archive are dated 2/1/2016. Even so, baseband files do not grow that much in size, especially when they still return the same version number.
Stranger yet (I mentioned it in the feb update thread) is if you flash the current motorola firmware (MPH24.49-18_18), the phone refuses to take the ota to the newest firmware. OTOH, if you flash the original nov firmware 24.49-18, then the phone updates to the feb build without any issues. I've tested all these different firmwares to arrive at the conclusions above.
A binary compare between the original MM baseband (from the november firmware) and the current one (firmware on the motorola site) reveals many differences. There must be some undocumented changes.
My suggested upgrade path is real simple;
1) Flash the original 24.49-18 firmware (not the one that's on motorola now). This is available in the general or developer's thread. filename: CLARK_RETUS_6.0_MPH24.49-18_cid9_subsidy-DEFAULT_CFC.xml.zip
2) Let it boot then perform the system update - this will bring you to the feb build of everything including the baseband
3) Flash whatever rom you want. Don't touch the baseband
Unless there are worthwhile changes, I generally don't touch the baseband. Usually don't touch the firmware either.

non developer build
Hi, if I bought the xt1575 from best buy and flashed the latest marshmallow would it brick my radios and wifi? And if not, where can I find the latest firmware, I tried one from motorola, and lost my radio, comming from 5.1
gpz1100 said:
That's the weird part, files within the archive are dated 2/1/2016. Even so, baseband files do not grow that much in size, especially when they still return the same version number.
Stranger yet (I mentioned it in the feb update thread) is if you flash the current motorola firmware (MPH24.49-18_18), the phone refuses to take the ota to the newest firmware. OTOH, if you flash the original nov firmware 24.49-18, then the phone updates to the feb build without any issues. I've tested all these different firmwares to arrive at the conclusions above.
A binary compare between the original MM baseband (from the november firmware) and the current one (firmware on the motorola site) reveals many differences. There must be some undocumented changes.
My suggested upgrade path is real simple;
1) Flash the original 24.49-18 firmware (not the one that's on motorola now). This is available in the general or developer's thread. filename: CLARK_RETUS_6.0_MPH24.49-18_cid9_subsidy-DEFAULT_CFC.xml.zip
2) Let it boot then perform the system update - this will bring you to the feb build of everything including the baseband
3) Flash whatever rom you want. Don't touch the baseband
Unless there are worthwhile changes, I generally don't touch the baseband. Usually don't touch the firmware either.
Click to expand...
Click to collapse

gigawatt said:
Hi, if I bought the xt1575 from best buy and flashed the latest marshmallow would it brick my radios and wifi? And if not, where can I find the latest firmware, I tried one from motorola, and lost my radio, comming from 5.1
Click to expand...
Click to collapse
If you read everything (including filenames) carefully and were using the correct firmware, (in this case, NOT 1572 which is the Style and not Pure), you wouldn't be losing any radio, unless you were downgrading, in which you'd just have to manually flash the radios again via fastboot after downgrading. Use search for that info.
Anything else you did besides flashing the correct firmware, and not explaining in your posts more on what you did (such as rooting) is on you. Put more details into your post.
There's a sticky thread under Android Development with a collection of firmware for both Pure and Style.
BTW, I saw your other thread. I'm not sure what you were reading, but there is no "developer edition" of this phone, nor firmware.

Has anyone measured any improvement with the newer modem file? I like to use the latest modem when possible.

gigawatt said:
Hi, if I bought the xt1575 from best buy and flashed the latest marshmallow would it brick my radios and wifi? And if not, where can I find the latest firmware, I tried one from motorola, and lost my radio, comming from 5.1
Click to expand...
Click to collapse
You can't "brick" your radios by flashing anything posted here. You can disable them however which is easily fixed by flashing modem or kernel or su depending on the situation.

Anyone been able to solve the problem on this flashable modem file? When I try to flash it, it fails. Currently I was stuck on "roaming indicator on" while on MM and upgraded my custom rom to Nougat (Dirty Unicorn) thinking it would fix it, but it didn't. I tried flashing the MM modem zip, roaming indicator is gone, but I seem to have lost my radio.

modem
Holymsophy said:
Anyone been able to solve the problem on this flashable modem file? When I try to flash it, it fails. Currently I was stuck on "roaming indicator on" while on MM and upgraded my custom rom to Nougat (Dirty Unicorn) thinking it would fix it, but it didn't. I tried flashing the MM modem zip, roaming indicator is gone, but I seem to have lost my radio.
Click to expand...
Click to collapse
how do i tell if my modem is still nougat modem if im back to marshmallow what is nougat radio number or version?

Sherrillface said:
how do i tell if my modem is still nougat modem if im back to marshmallow what is nougat radio number or version?
Click to expand...
Click to collapse
Here is a screenshot from my phone that is running stock Nougat. It shows the Baseband version which is the radio number.