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

[Q] lock symbol

hey guys....well i downgraded my nexus s 9020T for 4.0.3 to 2.3.6...however but while switching it on the 2.3.6..im getting a lock symbol while switching it on..and when i insert my sim onto the phone ..it is recognising the network but not catching the signal
kindly help me out

The lock symbol at the bottom means your bootloader is unlocked. This means you can replace your recovery partition to CWM or the likes, as well as flash superuser to the OS and flash custom ROMs. You would have achieved this through the "fastboot oem unlock" command.
The signal issue may be related to a bad flash. I would be going into recovery, doing a factory/data reset, formatting /system and /boot, and then flash the 2.3.6 file you have again. Remembering of course to backup anything currently on the phone, and doing a NANDROID backup if you don't have a working one already.

thank so much for the information...after doing this..can my phone still OTA official updates from google once they are released??

roshan567 said:
thank so much for the information...after doing this..can my phone still OTA official updates from google once they are released??
Click to expand...
Click to collapse
As long as you flash a official update
Sent from my ice cream powered Nexus S

a friend of mine is doing the flashing...any idea as to how can i know whether he has flashed an official update or not?

also what is the different between flashable roms n the increamental updates given in this link??
http://forum.xda-developers.com/showthread.php?t=1063664
are both official versions given out by google?

Yes, all of the links in that thread are official Google builds. The full/flashable ROMs are the full operating system in one file. You can install this over any Android version/ROM since the zip will contain all of the files necessary to get the system working.
The incremental updates should only be used if you have a specific (official) Android version and wish to only install the updated files. For example, if you have the official Google release of 2.3.6 and wish to upgrade to 4.0.3, you can use the 2.3.6 -> 4.0.3 incremental update. Otherwise, if don't have one of the supported incremental update versions or if you're using a non-stock ROM then you'll need to download the full ROM.

thank you so much for the information....
i am downgrading my OS to 2.3.6 from 4.0.3..how can i find out whether the 2.3.6 OS ive installed is the original OS???

You can find out BEFORE flashing the rom by comparing checksums, the zip file should have the exact same checksum as indicated in the filename of the files in that thread. Also, that thread just links to files from googles servers used for official updates.
Once it's installed there is no point trying to finding out if it is 100% stock.

Harbb said:
You can find out BEFORE flashing the rom by comparing checksums, the zip file should have the exact same checksum as indicated in the filename of the files in that thread. Also, that thread just links to files from googles servers used for official updates.
Once it's installed there is no point trying to finding out if it is 100% stock.
Click to expand...
Click to collapse
thanks for the information...i didn understand properly how do u do checksums..can you pls explain it??im a noob..

Checksum (or hash) is a way to verify a file. It will create a word/number/pattern/etc according to an algorithm based on all the data in the file. With MD5, SHA1, etc we have a practically guaranteed chance of comparing the two files. Those files there are straight from google and google has provided the checksums in the filename (part of the checksum, at least). If you have any file at all and it has the same code as that, we can be happy that it's the exact same file - thus 100% stock
You can use software such as Checksum or my personal favourite HashTab to find the various comparing techniques.

hey thanks a lot for your information..it really helps....
when i upgraded to ICS my phone stopped receiving reception after 2 days..when i downgraded it after unlocking the bootloader it still wasnt receiving recepetion...why does this happen?

New firmware, V21Y for G2X showing in LGMobile Support Tool

Original Post
I started up the LGMobile Support Tool and selected supported model. When I scrolled down, it shows new firmware, V21y, for the LGP999DW, LGP999DWDU, LGP999DWP but still shows V21e for the LGP999WA.
Update 4/20/2012
The V21Y_00 update (LG T-Mobile branded Android 2.3.4) is not available anymore through the LGMobile Support Tool and LG has removed the direct download link to the V21Y_00.kdz file. Instead, thanks to another member, overground, it is now available from http://www.mediafire.com/?obr7717n1ebj2qa
Get it while you can in case LG files a DMCA complaint against Mediafire.
overground
Today, 12:48 PM
# 315
Yeah, seems LG has removed the update from their servers.
I've uploaded V21y here = http://www.mediafire.com/?obr7717n1ebj2qa
@CoreMemory: Feel free to put the link in the OP.
IMPORTANT!
A lot of peeps have had trouble installing the V21Y_00.kdz file. There are many variables which can cause installation failure which are due to "operator error" and/or computer idiosyncracies. This thread and others have information about various methods used to overcome update problems so, if at first you don't succeed, read the thread(s) and keep trying.
As well, this update will install a new baseband and an LG and T-Mobile branded Android 2.3.4 ROM. LG has made some serious changes to the baseband which prevents other ROMs, except for a modded version of the same Android 2.3.4 ROM or the newest versions of CM7 and some other ROMs (which you can find by searching for compatibility with V21Y/March baseband), from working with in-call audio which is the audio for using the phone as a phone - to make and receive phone calls and for the people on each side of the connection to hear each other. So, if you want to install modded ROMs, other than the a modded version of the V21Y Android 2.3.4 ROM installed by this update or one such as CM7 which is compatible (Weapon isn't), don't update. If you do install it you can revert back to V21e by downloading it and using whatever method you used to successfully install the V21y update.
Before you update to V21Y, save a CWM backup of your existing ROM which you can use to revert back to the installation you now have after you reinstall V21E (including the V21E baseband). You can't use CWM to reinstall V21E, you must use the KDZ updater with the V21E kdz file then use CWM to restore your previously installed V21E modded ROM and Kernel. Good Luck!
If you want to revert to V21E Android 2.3.3 and the compatible baseband, get the V21E kdz update file here: http://www.2shared.com/file/WVH0y09f/V21E_00.html
INSTRUCTIONS
There's usually no need to revert your phone back to a stock ROM. If you use the following method, you can install any G2X/P999 .kdz update file (V10f, V21e, V21y, etc.) over almost any ROM, including modded ones. If you want to eliminate a potential update problem, revert to a stock ROM first. If the update didn't work, and you bricked your phone, you need to revert back to a stock ROM which you can do by following the instructions here: http://forum.xda-developers.com/showthread.php?t=1248644&highlight=unbrick+phone
I successfully used Windows Virtual PC in XP Mode to install the .kdz file but you may be able to install it in Windows XP and Windows 7 (32 and 64 bit), as others have successfully done, by using LG_KDZ_FW-Update_OfflineFix as follows:
First,
From the OP by adixtra at http://forum.xda-developers.com/showthread.php?t=1287236
1. download: LG_KDZ_FW-Update_OfflineFix (OFFLINE INSTALLER DOWNLOAD)
2. download: KDZ_FW_UPD_EN (DOWNLOAD FLASHING PROGRAMS)
3. download: ROOT USING SuperOneClick
DO NOT DOWNLOAD ANY OF THE OTHER FILES THERE!
Alternative to downloading the #1 and #2 files listed above,
here's a link to instructions and files, by spyrosk, which includes almost everything (except for SuperOneClick and the .kdz update file) which installs and runs by using an included VB Script: http://forum.xda-developers.com/showpost.php?p=22189294&postcount=30
You will still need the .kdz file of your choice to use with it.
Second,
Download the V21Y_00.kdz upgrade/update file which, although LG has removed the V21Y_00.kdz file from their server, thanks to another member, overground, it is now available from http://www.mediafire.com/?obr7717n1ebj2qa
Third,
From the OP by Kairi_zeroblade at http://forum.xda-developers.com/showthread.php?t=1566681
download CWM-Based Recovery 5.0.2.8
Fourth,
Carry out the steps in adixtra's OP at http://forum.xda-developers.com/showthread.php?t=1287236 with the V21y_00.kdz file you downloaded by selecting it from wherever you downloaded it to.
It takes about 10 minutes to complete.
Fifth,
Afterwards, you will have to root it with SuperOneClick and install CWM if you want to use it for backing up, restoring, etc. (saving your butt) otherwise if you restore it will be the stock v21y installation.
XP MODE Instructions
If you don't succeed with Windows 7 or Windows XP (which it should have), it may work with XP Mode in Virtual PC. The LG Modem drivers have to be installed in Windows 7 first then, after you get XP Mode operating, carry out the steps again. After you connect the phone to the computer, you will have to attach the phone's USB port in XP Mode from the XP Mode USB menu. During the update process, the phone's USB port will detach, you'll hear an alert sound, and you must reattach the USB port again from the XP Mode USB menu. That will happen a few times until the process completes. Here's instructions from Microsoft about how to install and use Windows XP mode in Windows 7 http://windows.microsoft.com/en-US/windows7/install-and-use-windows-xp-mode-in-windows-7.
Also,
Have a look at Enyah's thread for information about how others have successfully updated to V21Y_00.kdz http://forum.xda-developers.com/showthread.php?t=1610597
Have a look at Rafase282's post too, it repeats some content from my thread and others' but has some additional content http://forum.xda-developers.com/showpost.php?p=26935107&postcount=3

We're on 21E, right? Weird. Wonder what it is.
Sent from my LG-P999 using xda premium

SefEXE said:
We're on 21E, right? Weird. Wonder what it is.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Yes, weird but I have confirmed that it is available. I added a direct link to it in the first post of this thread.

we need a new baseband that sucks less power, and one that does not lose APN when going in to airplane mode... D:

ICS!!!!
.
.
.
.
.
.
SIKEEE x) idk, but I'm restoring back to stock to find out...

missaellpzchvz said:
ICS!!!!
.
.
.
.
.
.
SIKEEE x) idk, but I'm restoring back to stock to find out...
Click to expand...
Click to collapse
I wish
Sent from my Handheld Portal Device

update
just completed the update
gingerbread version 2.3.4 now
and new baseband March 11, 2012
that's what i notice in the first minute
it DID unroot my phone after updating.....sorry i made a mistake before
No LG Camera

illipower said:
just completed the update
gingerbread version 2.3.4 now
and new baseband March 11, 2012
that's what i notice in the first minute
it didn't unroot my phone after updating
Click to expand...
Click to collapse
Ohooooo
Sent from my LG-P999 using xda premium

illipower said:
just completed the update
gingerbread version 2.3.4 now
and new baseband March 11, 2012
that's what i notice in the first minute
it didn't unroot my phone after updating
Click to expand...
Click to collapse
Can you check if it has the LG Camera?
Sent from my LG-P999 using XDA

illipower said:
just completed the update
gingerbread version 2.3.4 now
and new baseband March 11, 2012
that's what i notice in the first minute
it DID unroot my phone after updating.....sorry i made a mistake before
No LG Camera
Click to expand...
Click to collapse
Is it rootable?
It is probably to placate us for a bit about not getting an update to ICS - yet?

Man, even though not ics, it's something. At least we get a new baseband. I'm gonna go fire up the updater and give it a chance, hopefully the baseband is better and that will be used with whatever we flash.
Sent from my LG-P999 using xda premium

mustangtim49 said:
Man, even though not ics, it's something. At least we get a new baseband. I'm gonna go fire up the updater and give it a chance, hopefully the baseband is better and that will be used with whatever we flash.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Same here, haha. I'm in the process of restoring my G2x to stock firmware so I can update it. Takes so long -__-

FatalityBoyZahy said:
Same here, haha. I'm in the process of restoring my G2x to stock firmware so I can update it. Takes so long -__-
Click to expand...
Click to collapse
All I did was restore the stock recovery and I was able to update...then NVFlash CWM back...and restore my ROM I backed up before I updated...
Sent from my LG-P999 using Tapatalk 2

Could somebody please post the OneClickRecovery Flasher? I've gone past my download limit for DepositFiles

lol, I we got 2.3.4 after a almost a year...i guess we are gonna wait for ICS another year ;o

I just updated. Here's some info:
Version: 2.3.4
Baseband: MAR 11 2012
Kernel: 2.6.32.9
Version: GRJ22
Software Version: LG-P999-V21y
So I believe it's running the same kernel as the 2.3.3 update. I'm not sure what differences the new baseband brings.

Why in the f**k would they release another gb version yeah new baseband could be useful however all that manpower and developing could have gone towards some slightly more worthwhile like oh I dunno... ics?
Or maybe LG is soooooo bass ackwards they think 2.3.4 is ics? lmao
Pin it to Win it.

Definitely more stable than 2.3.3, new kernel boot animation seen on leaked build from a few months ago & more options for video encoding (recording). I'm probably going to run it for a while since I do miss the great battery life that LG stock has.
{
"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"
}
Sent from my LG-P999 using Tapatalk 2

I confirm I have the updated baseband. I went through the process to go back to stock and it updated. Then I just restored my backup.

whats the difference btw the two GBs? I know it changes the basebands but anything else that people are noticing?

New Update - QC2

According to the Verizon Galaxy S5 Update Page:
This software update provides the latest Android™ security patches, fixes an email issue and updates the Amazon Shopping app.
Email update:
Fixes an issue that prevented Outlook® 2007 and 2003 users from accessing and downloading email attachments.
Click to expand...
Click to collapse
Please note that if you happen to play Pokemon GO or any game which "GPS Spoofers" take advantage of, the March Security Patch, and this update will prevent GPS Spoofing.
Also, I'm not entirely sure yet as to whether the Samsung Patch for Qualcomm Galaxy S5 bootloaders included in the March Security Patch will affect the ability to have a Developer bootloader anymore:
SVE-2016-7930: Multiple Buffer Overflow in Qualcomm Bootloader
Severity: Critical
Affected versions: Galaxy S5 with Qualcomm AP chipset
Reported on: December 20, 2016
Disclosure status: Privately disclosed.
A buffer overflow vulnerability exist in Qualcomm bootloader.
The patch prevents buffer overflow by removing the problematic source code.
Click to expand...
Click to collapse
I, personally, am not willing to test this, but if anyone does, please post your results. I'll upload an aboot free (Dev Friendly) firmware as soon as possible in case anyone wants to test it.
I'm currently in the process of downloading/uploading the Odin firmwares right now. I'll update this post when they are uploaded.
EDIT:
Stock No-Wipe FW. Will remove Developer Status Bootloader: G900VVRU2DQC2_G900VVZW2DQC2_G900VVRU2DQC2_HOME.tar.md5.zip
Developer Bootloader Friendly:
G900VVRU2DQC2_G900VVZW2DQC2_G900VVRU2DQC2_HOME_No_Aboot.tar.md5.zip

If it breaks something that I warned about, please reply.
If it breaks something that I didn't warn or know about, please share with everyone else.

I'm guessing no replies and no ROMs based on QC2 means noone has tested it yet.
I'm going to flash the aboot free version to one of my CID 15 S5's later tonight so I'll reply with results.

I'm gonna try it out when I get a chance this week. Thanks!

Has anybody tried this?

robbyoconnor said:
Has anybody tried this?
Click to expand...
Click to collapse
Not yet I'm gonna download this once I get to a pc definitely
Sent from my SM-G900V using Tapatalk

Kastro1784 said:
Not yet I'm gonna download this once I get to a pc definitely
Click to expand...
Click to collapse
You can use Flaahfire by the way.

Download /installed last night.Havent had time to dig around. Precursor look has only shown latest Android security updates.

Dudash said:
I'm going to flash the aboot free version to one of my CID 15 S5's later tonight so I'll reply with results.
Click to expand...
Click to collapse
How we looking, captain?

I recently was pushed the QC2 update with the March 2017 security package. I have noticed a significant decline in performance and battery life. Anyone in the same boat?
It seems like they have pushed a security updated every other month or so for the last 6 months. It is very irritating. I want to go back to root but it is too much of a hassle to figure it out at this point. I feel like they are deliberately doing these updates to make the S5 run worse and feel more outdated so you are more inclined to go buy a new one. Really sick of the whole game that is the telecom industry.
I am going to try doing a factory reset (very annoying) and see if that helps. Hopefully I can hold out long enough for the Pixel 2.

@Dudash QD1 is up, can you upload it to AFH. thanks in advance.

Noooooo! I flashed the Dev friendly QC2 modem and it seems to have killed my dev bootloader and wiped my phone!
I'll keep messing around and see if it can't be remedied. I could just punch myself for being so ambitious, though.
Edit 1: It was taking forever on the Verizon logo, so I pulled the battery and rebooted to recovery. It wiped TWRP and put in stock. I booted to Download Mode, and it still reads MODE: Developer (which I hope to God means my Dev bootloader is retained).
Edit 2: TWRP sucessfully re-flashed. The "Custom" with unlocked lock icon has reappeared on the boot screen, along with the yellow text at the top (so clearly, I was wrong about losing Dev status. Whew! I just freaked out when I saw a plain boot screen and the dreaded Verizon logo :silly. My installation of Lineage OS is clearly gone, but, peeking through TWRP's file manager appears to indicate my media data (photos, downloads, etc.) may yet have survived. I'll flash Lineage and GApps and see what happens.
Edit 3: Lineage OS booted successfully (made easier with the help of an SD card-- hooray for those things, amirite?), with QC2 baseband intact! Hooray! And my downloads and pictures and everything survived too.
Lesson: Always make a nandroid backup when doing this sort of thing! It takes a while, and it's morbidly annoying, but had I done it, I probably wouldn't've had to start from scratch. But hey, got the new baseband, and still running Lineage, so I call this a win. Cheers, everyone! And thanks to OP for posting updates!
Follow-up: Since it doesn't seem like we can flash only the new basebands by themselves, I've found a tactic that does the trick for those of us on not-stock ROMs. Boot into TWRP and make a backup of Boot, System, and Data (notice there's a Modem option-- leave it unchecked). I imagine it's best to put the backup image on an SD card. Then Odin the dev-friendly firmware update (I used the no-wipe option). Let the phone restart, then Odin the most recent TWRP back on there. Boot into TWRP, do a Factory Reset Wipe, and restore the backup you made. Takes a little while, but it does leave you with your phone as it was, but with the new baseband. :victory:
{
"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"
}

mohammad.afaneh said:
@Dudash QD1 is up, can you upload it to AFH. thanks in advance.
Click to expand...
Click to collapse
In the process of uploading right now.

Dudash said:
In the process of uploading right now.
Click to expand...
Click to collapse
??? thanks

J-Lindo said:
How we looking, captain?
Click to expand...
Click to collapse
I totally missed this reply. I flashed QC2 onto one of my S5's and it remained a Dev Edition. Then earlier today I flashed QD1 onto my other S5 and it remained a Dev Edition as well. Faking GPS doesnt work on either anymore but they keep Dev status.

Dudash said:
I totally missed this reply. I flashed QC2 onto one of my S5's and it remained a Dev Edition. Then earlier today I flashed QD1 onto my other S5 and it remained a Dev Edition as well. Faking GPS doesnt work on either anymore but they keep Dev status.
Click to expand...
Click to collapse
No problem! I'm sure you've already seen the results of my first (embarrassingly n00bish) independent baseband flash :laugh:
I appreciate the response, though. Fortunately, I'm not into GPS spoofing, so this isn't an issue for me. When you say you flashed QC2 and QD1, do you mean strictly the basebands without the bootloaders, or did you flash the entire updates and still retain Dev status?

J-Lindo said:
No problem! I'm sure you've already seen the results of my first (embarrassingly n00bish) independent baseband flash :laugh:
I appreciate the response, though. Fortunately, I'm not into GPS spoofing, so this isn't an issue for me. When you say you flashed QC2 and QD1, do you mean strictly the basebands without the bootloaders, or did you flash the entire updates and still retain Dev status?
Click to expand...
Click to collapse
I flashed the entire firmware minus the aboot.

US Version flashing Internation version and mobile signal.

So in the world of Sony, I'm very unfamiliar with the flashing process but through trial and errors i would like correction if there needs to be one and if my method is valid i would recommend it for US version buyers. So when i originally flashed the International version i had bad signal problems, so naturally i figured it was the modem. Spent near a day flashing different versions and the signal was still horrible compared to the us version which had me ready to return the phone and just buy the international version. After a trying a last method (since moving the US version modem to the European rom folder didn't work) I tried only flashing these files and viola, mobile signal back up to were it should be. I flashed back the US version and only flashed these files, so far no problems at all since yesterday, maybe there is an easier method that can be discussed, but for me, flashing the US modem didn't help my signal and call issues. attached is the files i flashed.
{
"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"
}

mykenyc said:
So in the world of Sony, I'm very unfamiliar with the flashing process but through trial and errors i would like correction if there needs to be one and if my method is valid i would recommend it for US version buyers. So when i originally flashed the International version i had bad signal problems, so naturally i figured it was the modem. Spent near a day flashing different versions and the signal was still horrible compared to the us version which had me ready to return the phone and just buy the international version. After a trying a last method (since moving the US version modem to the European rom folder didn't work) I tried only flashing these files and viola, mobile signal back up to were it should be. I flashed back the US version and only flashed these files, so far no problems at all since yesterday, maybe there is an easier method that can be discussed, but for me, flashing the US modem didn't help my signal and call issues. attached is the files i flashed.
Click to expand...
Click to collapse
Did you still keep fingerprint functionality? I flashed the CE1 ROM last night and my signal strength is horrible compared to the US ROM.
Sent from my G8142 using Tapatalk

GiancarloMorr24 said:
Did you still keep fingerprint functionality? I flashed the CE1 ROM last night and my signal strength is horrible compared to the US ROM.
Click to expand...
Click to collapse
Yes flash back US then flash only these from Euro.

mykenyc said:
Yes flash back US then flash only these from Euro.
Click to expand...
Click to collapse
Got it. Thank you.
Sent from my G8142 using Tapatalk

Did you unzip the partition zip file and create a partition folder before you flashed?

Thanks for this my signal has been horrible as well after flashing the CE1 firmware on the US model. Just to summarize.
1. Download the US firmware.
2. Flash everything from it.
3. After this, from the CE1 firmware only flash the files shown from your screen shot.
Doing this will give the working fingerprint scanner as well as intended signal strength/quality from the original US firmware. Is my understand correct?
Edit:
Just tried and worked fine, not measured the signal strength yet but definitely looks to have more bars than I had before. I'll test at office on Monday where signal was not holding well compared to other phones [emoji106]
Any idea if this is going to affect the updates since we have files flashed from 2 different firmwares?

mykenyc said:
So in the world of Sony, I'm very unfamiliar with the flashing process but through trial and errors i would like correction if there needs to be one and if my method is valid i would recommend it for US version buyers. So when i originally flashed the International version i had bad signal problems, so naturally i figured it was the modem. Spent near a day flashing different versions and the signal was still horrible compared to the us version which had me ready to return the phone and just buy the international version. After a trying a last method (since moving the US version modem to the European rom folder didn't work) I tried only flashing these files and viola, mobile signal back up to were it should be. I flashed back the US version and only flashed these files, so far no problems at all since yesterday, maybe there is an easier method that can be discussed, but for me, flashing the US modem didn't help my signal and call issues. attached is the files i flashed.
Click to expand...
Click to collapse
Did you compare the actual dBm values before and after flashing, or were you just looking at the number of bars shown?
I don't know if Sony does this, but on some of my other phones like my S7 Edge the US Rom will show more bars than international roms on the same phone, however the actual signal strength (in dBm) is exactly the same.

walrusmonarch said:
Did you compare the actual dBm values before and after flashing, or were you just looking at the number of bars shown?
I don't know if Sony does this, but on some of my other phones like my S7 Edge the US Rom will show more bars than international roms on the same phone, however the actual signal strength (in dBm) is exactly the same.
Click to expand...
Click to collapse
No, but for myself when I flashed the Euro ROM in my apartment the signal would die or go to 1 bar I also had horrible call problems outside. Now I have full bars and have yet to have call issues so I'm sure it isn't a placebo.

mykenyc said:
No, but for myself when I flashed the Euro ROM in my apartment the signal would die or go to 1 bar I also had horrible call problems outside. Now I have full bars and have yet to have call issues so I'm sure it isn't a placebo.
Click to expand...
Click to collapse
Interesting, maybe the USA firmware's baseband is tuned to favor certain bands or something than the European firmware.
I haven't noticed any major difference between the Singapore and CE1 firmware on my XZP or my T-Mobile S7E. I haven't tried the USA firmware though.
In any case, I will keep this in mind if I do come across something down the line.
Do you know how this would affect future OTAs?

Interesting discussion. I purchased mine from the UK so I would NOT have to flash anything and still have the fingerprint sensor working. However, is it the consensus here that the US firmware will provide for a better signal? I am on AT&T pre-paid.
If I were to flash the US firmware over my phone from the UK will it kill the fingerprint sensor also???
Thanks in advance for any information!

I tried your method with the files exactly as you have shown but got stuck on the boot screen after flashing. Do you know what I did wrong?

Did you extract the files from the partition.zip and then create a folder called partition with those files in it. According to the developer of newflasher, that's what needs to be done

No I did not, I will do that now. Thanks for the reply.
---------- Post added at 02:01 AM ---------- Previous post was at 01:17 AM ----------
Same result, its stuck on the boot screen.

madmc320 said:
No I did not, I will do that now. Thanks for the reply.
---------- Post added at 02:01 AM ---------- Previous post was at 01:17 AM ----------
Same result, its stuck on the boot screen.
Click to expand...
Click to collapse
I would download and run xperia companion and do a emergency repair on your phone
http://support.sonymobile.com/us/xperia-companion/

Would you mind to create a step by step manual, please
mykenyc said:
So in the world of Sony, I'm very unfamiliar with the flashing process but through trial and errors i would like correction if there needs to be one and if my method is valid i would recommend it for US version buyers. So when i originally flashed the International version i had bad signal problems, so naturally i figured it was the modem. Spent near a day flashing different versions and the signal was still horrible compared to the us version which had me ready to return the phone and just buy the international version. After a trying a last method (since moving the US version modem to the European rom folder didn't work) I tried only flashing these files and viola, mobile signal back up to were it should be. I flashed back the US version and only flashed these files, so far no problems at all since yesterday, maybe there is an easier method that can be discussed, but for me, flashing the US modem didn't help my signal and call issues. attached is the files i flashed.
Click to expand...
Click to collapse
HI, would you mind to create a step by step manual of what you did, so we all can enjoy the finger print unlock feature and the good signal, please?
Cheers

As no one has done a step by step manual for dummies like me...
hittori said:
HI, would you mind to create a step by step manual of what you did, so we all can enjoy the finger print unlock feature and the good signal, please?
Cheers
Click to expand...
Click to collapse
Hi,
a few days ago i asked if someone can create a step by step manual for dummies like me, and no one has done it. Therefore i put some effort, and risk, and i tried myself. Open hundreds of XDA developers pages, and at the end this is what i found outÑ
1.- Download XperiFir from here version 5 in my case.
2.- Click on Xperia XZ Premium Maple, then in G8142 dual, then in Central Europe, finally on the right side click on the 45.0.a.5.1; this will start the process and download 3 files which it will unzip for a total of 2.75GB
3.- Download New Flashear from here [Updated for Oreo]
4.- Copy to the folder where you unzip Newflashear the following files:
as you can see in the right side i have all the files from the European Version, and i copied to the left side (where the newflasher.exe is) the needed files
5.- in this folder, create a folder call partition and unzip all the partition.zip files in there.
6.- Check that you have the boot, flash_session and Partition folder. in the Boot folder you should see this:
and in the Partition folder this:
7.- Turn off your Sony Xperia XZ Premium, press the volume down button and plug the Usb C cable to the phone and the other part to the Computer
8.- Run newflasher.exe (I did as Admin to be sure it will run with no restriction).
8a.- Newflasher will be asking you two questions, type n and then press enter on both questions [Update for OREO]
9.- Wait and enjoy it will tell you when to unplug it and turn on your device.
Extra, in my case it took me a few tries to turn it on. What i think i found out is that if I press Volume Up and Power ON, it does power on.
Enjoy your previous disabled feature, now finally enabled.

Thanks for the guide, I am getting am disk space error. Error code 112 during the system_X inflation process. The device has nothing on it , why am I getting this error.

I can not find the folder flash_session, What is it? And where do I find it?
Cheers

san.13 said:
I can not find the folder flash_session, What is it? And where do I find it?
Cheers
Click to expand...
Click to collapse
it was empty, so no need to have it. If you please, create it yourself, but i believe it was created first time i run it without the right files
---------- Post added at 11:37 PM ---------- Previous post was at 11:35 PM ----------
madmc320 said:
Thanks for the guide, I am getting am disk space error. Error code 112 during the system_X inflation process. The device has nothing on it , why am I getting this error.
Click to expand...
Click to collapse
Sorry, i have no clue why is that.... Do you have the US version and installing the European version, are you? maybe someone with more experience can help you here.

hittori said:
it was empty, so no need to have it. If you please, create it yourself, but i believe it was created first time i run it without the right files
---------- Post added at 11:37 PM ---------- Previous post was at 11:35 PM ----------
Sorry, i have no clue why is that.... Do you have the US version and installing the European version, are you? maybe someone with more experience can help you here.
Click to expand...
Click to collapse
Fixed the issue by moving the file to another location. Not sure why it the difference was because there was plenty of space.