How do I restore the original firmware LG G2X? - T-Mobile LG G2x

I flashed the firmware LG G2X 2x-v10b-1300166062-NVFLASH!
Now I do not know how to restore the original firmware!
Who can help me or give ROM under NVFLASH?

ILUHA_89 said:
I have sewed LG G2X an firmware 2x-v10b-1300166062-nvflash!
Now I don't know how to recover an initial firmware!
Who can help me, or will give ROM under NVFlash
Click to expand...
Click to collapse
Its a little hard to understand what you're asking but if I'm understanding correctly then you're saying you flashed the 2x-v10b-13...... firmware to your phone. Am I correct? If so then you've definitely screwed up your G2X because that firmware appears to be for the O2X(P990) and not the G2X (P999) which would mean you have altered your partitions and flashed a baseband that's incompatible with your phone. Even if you recreate your partitions correctly, I'm not aware of any straightforward way of replacing the baseband with the proper one. I haven't seen any flashable basebands for the G2X.
Someone else wanna chime in here?

Does your phone even boot?

Yes, you understood correctly!
Phone is loaded but not running a network and not see the battery!
I even made a CWM and put CM7
But exactly the same result no network and not see the battery

Did you wipe correctly? Boot into ClockworkMod, and select Mounts and Storage.
Here's what I do.
-Format System
-Format Cache
-Format Data
Then wipe Dalvik Cache...
After that, flash any ROM you'd like... Boot into the ROM, and perform a Factory Reset.

And another question why he does not want sewn through SmartFlash!
Throws:
00:00.0 Sec ownload Start...
00:02.0 Sec :RomBinary Download start
00:02.1 Sec SI RAM writing start
00:02.1 Sec :Trying to communicate with IFX modem
00:22.1 Sec :Timeout error is occured
00:22.1 Sec :error!

I install [ROM] Stock NANDROID Restore Froyo 2.22 Rooted LG-P999-V10f 4-23-2011
Phone does not boot (boot animation and restart)

I think I have a way you can fix it. Check out the thread about fixing a soft-bricked phone. Use the KDZ program to flash the new GB rom for the G2X. When the KDZ program starts DO NOT click detect device. Instead just click to immediately start the update. This should flash your phone with the current firmware and the new baseband. Make sure you have the latest LG T-Mobile USB drivers installed on your computer.
http://forum.xda-developers.com/showthread.php?t=1180331

Thank you!
I will try restoring!

ILUHA_89 said:
Yes, you understood correctly!
Phone is loaded but not running a network and not see the battery!
I even made a CWM and put CM7
But exactly the same result no network and not see the battery
Click to expand...
Click to collapse
Sorry I missed the replies here. So the phone was booting up but with no network or battery detected. And looks like you tried flashing cm7 and performing a nandroid restore of the stock 2.2.2 firmware and now won't boot but gets stuck in a boot loop. Is that all correct?
I'm almost certain that your original issue is that you flashed a rom designed for the Optimus O2X (P990) and not the G2X (P999). If that's the case then a simple nandroid restore or flashing any rom won't work to fix your phone as far as I know. You might have some luck with the kdz flasher but I don't know.
If you CAN boot into your phone then go to Settings > About phone and tell us what it says there in regards to Model number and Baseband.

The KDZ method is a full flash like an OTA. If it works, and I think it will, the correct baseband will be flashed.
Sent from my LG-P999 using Tapatalk

jboxer said:
I think I have a way you can fix it. Check out the thread about fixing a soft-bricked phone. Use the KDZ program to flash the new GB rom for the G2X. When the KDZ program starts DO NOT click detect device. Instead just click to immediately start the update. This should flash your phone with the current firmware and the new baseband. Make sure you have the latest LG T-Mobile USB drivers installed on your computer.
http://forum.xda-developers.com/showthread.php?t=1180331
Click to expand...
Click to collapse
Not it is got!
KDZ log:
[R&D Test Tools Log File]
14:48:44 : Launching SW update
14:48:44 : Unpacking KDZ
14:48:53 : KDZ file extraced
14:48:58 : Files were extracted.
14:48:58 : LGMobileDL Load.
14:49:09 : Port = 0
14:49:20 : Connecting to phone
14:49:31 : Check Phone mode = 2
14:50:09 : Phone type check.......
14:50:11 : _DetachDLL Call
14:50:11 : _DetachDLL Call End
14:50:11 : Param : Path = C:\Documents and Settings\All Users\Application Data\LGMOBILEAX\Phone\V21E.wdb
14:50:11 : Param : moduleDir =
14:50:11 : Param : waitTime = 0
14:50:11 : Param : UsbHighSpeed = 1
14:50:11 : Param : PhoneMode = 2
14:50:11 : Param : BinVersion = V21E_00
14:50:11 : Param : AuthMark = 0
14:50:11 : Call fn_StartUpgrade
14:50:33 : CDMA: wParam = 2007, lParam = 0
14:50:33 : Model Dll Msg Not Found(2007, 0)
14:50:33 : CDMA: wParam = 2008, lParam = 8
14:50:33 : Model Dll Msg Not Found(2008, 8)
14:50:33 : CDMA: wParam = 2005, lParam = 0
14:50:33 : Model Dll Msg Not Found(2005, 0)
14:50:33 : CDMA: wParam = 2003, lParam = 16
14:50:33 : Model Dll Msg Not Found(2003, 16)
14:50:33 : CDMA: wParam = 2005, lParam = 1
14:50:33 : Model Dll Msg Not Found(2005, 1)
14:50:33 : CDMA: wParam = 2009, lParam = 1
14:50:33 : Model Dll Msg Not Found(2009, 1)
14:50:33 : CDMA: wParam = 2005, lParam = 5
14:50:33 : Model Dll Msg Not Found(2005, 5)
14:51:06 : CDMA: wParam = 2010, lParam = 3015
14:51:06 : Model Dll Msg Not Found(2010, 3015)
14:51:06 : CDMA: wParam = 2010, lParam = 3015
14:51:06 : Model Dll Msg Not Found(2010, 3015)

FatalityBoyZahy said:
Did you wipe correctly? Boot into ClockworkMod, and select Mounts and Storage.
Here's what I do.
-Format System
-Format Cache
-Format Data
Then wipe Dalvik Cache...
After that, flash any ROM you'd like... Boot into the ROM, and perform a Factory Reset.
Click to expand...
Click to collapse
All have done as You have said!
But smartphone does not want be loaded!

phburks said:
Sorry I missed the replies here. So the phone was booting up but with no network or battery detected. And looks like you tried flashing cm7 and performing a nandroid restore of the stock 2.2.2 firmware and now won't boot but gets stuck in a boot loop. Is that all correct?
I'm almost certain that your original issue is that you flashed a rom designed for the Optimus O2X (P990) and not the G2X (P999). If that's the case then a simple nandroid restore or flashing any rom won't work to fix your phone as far as I know. You might have some luck with the kdz flasher but I don't know.
If you CAN boot into your phone then go to Settings > About phone and tell us what it says there in regards to Model number and Baseband.
Click to expand...
Click to collapse
There "unknown radio module" is written

jboxer said:
The KDZ method is a full flash like an OTA. If it works, and I think it will, the correct baseband will be flashed.
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
OneClickRecoveryFlasher gives such picture!

Then you killed it by flashing wrong firmware. No other way to flash the correct baseband.
Sent from my LG-P999 using Tapatalk

I solved my problem myself!
I made a firmware for NVFlasher and sent it directly to your phone!
ROM G2X to lay out and who may later come in handy!

ILUHA_89 said:
I solved my problem myself!
I made a firmware for NVFlasher and sent it directly to your phone!
ROM G2X to lay out and who may later come in handy!
Click to expand...
Click to collapse
I and many others would like to know how you set up firmware for NVFlasher for the 999 and the commands to use it.
My phone was bricked by LGupdater, and could not update/restore it with KDZ -(repeatedly indicated fatal error). Out of desperation, I used a script tool from modeco.com that flashed 990 firmware. I then had a 990 device - lol.
I then tried Smartflash to restore the stock 999 firmware (CP.bin and AP.bin), but it would not do the CP.bin file It did flash the AP.bin file, which is the ROM, but did not restore the partitions and baseband with the CP.bin file. So I put stock recovery back on it and got a replacement. It looked like stock in settings, but baseband was "unknown".
I spent days on this and looked and inquired everywhere - but there was NOTHING in XDA nor modeco.com about how to restore a 999.
So please respond and detail your procedure.

Lay out in the evening a description and a link to the firmware!

ILUHA_89 said:
Lay out in the evening a description and a link to the firmware!
Click to expand...
Click to collapse
Looking forward to it.

Related

[Q]Error while searching for networks with "baseband V21E" [SOLVED]

HI there,
Was wondering If there is a fix to my little problem here.
I had been really keen to try out xbsall's XBSA V21E P920 ROM, so once it was uploaded I was right onto it, installed the zip from CWM and I'm very impressed. Baseband now v21e from v21a. However I have no mobile network and when I try to search it flashes with a quick Error message: "Error while searching for networks."
So I tried to flash v21e basband using smart tools and the v21e bin / fls.
So this time without the ROM and just having a stock baseband of v21e I have no mobile network and the same problem occurs.
Baseband Version:
L6260_MODEM_SIC_01.1042.00
Kernal Version
2.6.35.7+
Build Number:
GRJ90
Software Version:
LGP920-V21e-Apr-19-2012
Phone info:
IMEI: Unknown
Phone number: Unknown
Current network:
Ping IpAddr:
Ping Hostname(www.google.com): Pass
HTTP Clint test: Pass
Signal strength: 0 dBm 0 asu
Location LAC = unknown CID = unknown
Neighbouring CID: unknown
Roaming: Not roaming
GSM service: Emergency calls only
GPRS service: Disconnected
Network type: Unknown
Message waiting: false
Call redirect: false
Call status: Idle
Radio resets: 0
Data attempts: 0
GSM dissconnects: ========DATA========
Went into phone info via *#*#4636#*#* to see if I could change "Set Preferred network type: from Unknown to WCDMA" continues to stay unknown upon clicking WCDMA.
Any ideas? or should I go back to an earlier baseband and a different ROM for the time being?
Kind Regards
EDIT: Solved by installing TitanKernel V0.4.2 V21D 09-04-2012
Now the kernel version is 2.6.35.7 instead of 2.6.35.7+
and I am running XBSA V21E Gingerbread with ICS Theme Perfectly now, Love it so far!
Software version LGP920-V21e-Apr-10-2012
Loopy Frog said:
HI there,
Was wondering If there is a fix to my little problem here.
I had been really keen to try out xbsall's XBSA V21E P920 ROM, so once it was uploaded I was right onto it, installed the zip from CWM and I'm very impressed. Baseband now v21e from v21a. However I have no mobile network and when I try to search it flashes with a quick Error message: "Error while searching for networks."
So I tried to flash v21e basband using smart tools and the v21e bin / fls.
So this time without the ROM and just having a stock baseband of v21e I have no mobile network and the same problem occurs.
Baseband Version:
L6260_MODEM_SIC_01.1042.00
Kernal Version
2.6.35.7+
Build Number:
GRJ90
Software Version:
LGP920-V21e-Apr-19-2012
Phone info:
IMEI: Unknown
Phone number: Unknown
Current network:
Ping IpAddr:
Ping Hostname(www.google.com): Pass
HTTP Clint test: Pass
Signal strength: 0 dBm 0 asu
Location LAC = unknown CID = unknown
Neighbouring CID: unknown
Roaming: Not roaming
GSM service: Emergency calls only
GPRS service: Disconnected
Network type: Unknown
Message waiting: false
Call redirect: false
Call status: Idle
Radio resets: 0
Data attempts: 0
GSM dissconnects: ========DATA========
Went into phone info via *#*#4636#*#* to see if I could change "Set Preferred network type: from Unknown to WCDMA" continues to stay unknown upon clicking WCDMA.
Any ideas? or should I go back to an earlier baseband and a different ROM for the time being?
Kind Regards
EDIT: Solved by installing TitanKernel V0.4.2 V21D 09-04-2012
Now the kernel version is 2.6.35.7 instead of 2.6.35.7+
and I am running XBSA V21E Gingerbread with ICS Theme Perfectly now, Love it so far!
Software version LGP920-V21e-Apr-10-2012
Click to expand...
Click to collapse
You can flash the Prometheus project kernel v1.3 might be plus can't remember but samno used the kernel source from 21e when he wrote it I have it working on my thrill
sent from my acidhazard thrill
nice to hear it works for you mate
did you follow the PREinstallation guide step by step and it didnt work?
cause you should use v21e kernel
how to change kernel?
i am having the same problem
I flash v21e, and my kernel changed from version 2.6.35.7 to 2.6.35.7+
I think that because of that i have no network connection (sometimes i have it, sometimes no)
I tried different kernels, like promethius rom 1.5, promethius kernel v1.4.5.1+, xbsa_V21e_gb_ics, NovAndroid2.1
All of them show kernel 2.6.35.7+
I found titankernel_v0.4.2_v21d_09-04-2012 in a german site, tried to flash but it locked my phone
Now i am back to promethius, and i have network connection only at the street, never in buildings.
What should i do?
Flash 21e baaseband.
Sent from my LG-P920 using xda app-developers app
iodak said:
Flash 21e baaseband.
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
i flashed V21E_00.kdz using
Code:
http://forum.xda-developers.com/showpost.php?p=23474089&postcount=1
Is the baseband included in the kdz? if not, can you point me how to do that?
Thanks
Yes it is included in kdz. You can now flash any custom rom that is 21e based.
Sent from my LG-P920 using xda app-developers app
V21E does not work in canada
iodak said:
Yes it is included in kdz. You can now flash any custom rom that is 21e based.
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
It looks like V21e does not work in Canada
I stick with V20C, flashed bluekernel, and no GC for 2 days

[Q] Accidentally set radio to USA band

Hey Folks,
normally I'm a silent reader. Till now I could solve any problems but right now I'm facing a problem which I can't get rid of.
I did the Sim Mod on my Photon q and while trying to get the mobile data working I accidentally set the radio band to "USA band". So now I can't get any connection to a german provider.
I tried to fix this problem with QPST. But failed in the beginning. I downloaded QPST 2.7 Build 378 and tried to get a connection between the phone and QPST with no sucess.
Could anybody help me with aome detailed instructions? Would appreciate it!
Thanks!
You made the same mistake I made.
I solved it by modifying my Photon Q with QPST, I changed the "UMTS System" and selected every Band by "Prefered Band".
Now I would only select those bands which are used in germany.
PS: If you need help in german, ask here for help -> http://www.android-hilfe.de/motorola-photon-q-forum/
HeliPilotMech said:
Hey Folks,
normally I'm a silent reader. Till now I could solve any problems but right now I'm facing a problem which I can't get rid of.
I did the Sim Mod on my Photon q and while trying to get the mobile data working I accidentally set the radio band to "USA band". So now I can't get any connection to a german provider.
I tried to fix this problem with QPST. But failed in the beginning. I downloaded QPST 2.7 Build 378 and tried to get a connection between the phone and QPST with no sucess.
Could anybody help me with aome detailed instructions? Would appreciate it!
Thanks!
Click to expand...
Click to collapse
Download the newest QPST. This is important. Follow this guide to set up QPST http://www.cricketusers.com/sprint-...-q-4g-lte-cricket-talk-text-mms-internet.html. From there, just select all the bands under UMTS (i am not sure on this one, but look through the menus). Selct all the bands and flash. Your phone should be good as new.
amrewsl Systeme
zodiac12345 said:
Download the newest QPST. This is important. Follow this guide to set up QPST http://www.cricketusers.com/sprint-...-q-4g-lte-cricket-talk-text-mms-internet.html. From there, just select all the bands under UMTS (i am not sure on this one, but look through the menus). Selct all the bands and flash. Your phone should be good as new.
Click to expand...
Click to collapse
Thanks zodiac, that helped a lot!
But I'm having trouble with getting my MSL/SPC. I tried to get it with this method: http://forum.xda-developers.com/showthread.php?t=1894038
But the only thing I get is: ~1,1~3,1~5,1~7,1~9,1~11,1
And I also tried this method: http://forum.xda-developers.com/showthread.php?t=1365058
But there I get this message:
Sending 'RDELEM' command with data '278600010000000E' to the radio...
Sent to radio:
TC Send Header: 000800200000000000000008
TC Send Data: 278600010000000E
Returned from radio:
TC Receive Header: 860800200087000000000070
TC Receive Data: 46544D20636F6D6D616E64206661696C65642C2064726976657220657272203D20302C20737461747573203D20313B206661696C656420746F206F70656E2046544D206465766963652C206572726F72203D2032284E6F20737563682066696C65206F72206469726563746F72792900
TC ASCII Error: FTM command failed, driver err = 0, status = 1; failed to open FTM device, error = 2(No such file or directory)
RDELEM ==>FAILED
Driver answer ==> -4
Error Description ==> Unknown Error
Time to execute command: 0 seconds.
Command timeout set to : 15 seconds.
Any ideas how to get my MSL/SPC?
Sent from my Nexus 7 using xda app-developers app
A User in the german Android-Hilfe.de forum have pointed at this two posts:
parin11 said:
ON Jellybean it not working
On ICS Its reading SPC perfectly
Click to expand...
Click to collapse
x86Daddy said:
I was receiving the same wrong number many have posted (~1,1~3,1~5,1~7,1~9,1~11,1)... because my used Photon Q arrived with 4.1.2 already installed. Here's the high level steps I took to get my MSL:
I unlocked the bootloader through Motorola
I installed the latest TWRP recovery for the Photon Q (2.6.0.0 in my case), using the fastboot method described here
I installed the ICS stock rom from this XDA thread
I tried the MSL retrieval batch file tool again. I had to click the OK after verifying the empty code for the batch tool to work.
I have a working MSL code now.
I then wiped the OS again and installed the latest Cyanogenmod nightly.
Thanks to this community and to the author of this batch from the CricketUsers site!!!
Click to expand...
Click to collapse
Maybe it will be helpful.

Can i manually update my D801 touch firmware?

The following is my Touch Firmware Version:
ic_fw_identifier = PLG208 - 1
ic_fw_version = E067
img_fw_product_id = PLG208
img_fw_version = E067
ic_chip_rev = 2
bootloader_fw_ver = 0
lcd_panel_type(boot) = 0
lcd_panel type(current) = 0
Those of you with a black, tmobile G2, can you tell me if you're on the same touch firmware (via the hidden menu). -> 3845#*801#
My touchscreen is completely non functional after the latest knock-code update from Tmobile. I suspect that its my touch firmware (perhaps being old, and not upgrading?). I have rooted, reflashed multiple versions images, and returned it to completely stock via the flash tool using a few KDZ files. Nothing is working.
Would like to compare what other's touch firmware version is, and if possible, do a manual upgrade of my touch firmware.

Sony Xperia Z3 SO-01G Cant flash??

At least, I think that's the problem. After trying to flash a newer SO-01G_NTT DoCoMo JP_1290-5930_23.1.B.1.160 on my phone with Flashtool (v0.9.19.1) Windows 8.1, all it does is boot to the SONY logo, then proceeds to say "The software update failed. Make sure that your phone is connected to the computer and try again." This only happens again and again afterwards..
During the flashing process, it seems all fine and dandy until it comes to the system.sin part, finishes and results in an error. It seems to me that according to the log from Flashtool, the program is loading it into the phone but the phone is rejecting it or something? Could it be that there is not enough space left on the phone to flash another rom?
Writing packet to phone
10/002/2015 00:02:56 - DEBUG - (USBFlashWin32.java:47) - OUT : CommandID : 6 / Flags : false,true,true / Data length : 524288 / Data CRC32 : [21, C7, 4A, E0]
10/002/2015 00:02:56 - DEBUG - (USBFlashWin32.java:58) - Reading packet from phone
10/002/2015 00:02:56 - DEBUG - (USBFlashWin32.java:64) - IN : CommandID : 6 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
Ive tried alternatives to this Flashtool, including Emma and PC Companion. But because the phone naturally has a locked bootloader that cant be unlocked due to the previous carriers restrictions (NTT DoCoMo).
Thanks in advance?! :fingers-crossed:
Got the same problem. I think the problem is flashtool, because after an update i can't Flash newer firmwares than "***.93".
I tried it with Windows 10/8.1/7.
And fileset decrypt doesn't work anymore too.
Fingers crossed
Flockrock said:
Got the same problem. I think the problem is flashtool, because after an update i can't Flash newer firmwares than "***.93".
I tried it with Windows 10/8.1/7.
And fileset decrypt doesn't work anymore too.
Click to expand...
Click to collapse
Hopefully there might be a solution soon.. I mean, I've searched high and low for a fix and alas, nothing.
Well, delete completly your flashtool then reinstall it. Reinstall the driver as well. The prolem fixed. Mine's work .
Hello I'm very interested in changing the firmware on my Xperia SO-01G to I guess global or Nordic just so I can pick up 4g or lte I dnt care for NFC. My network is like Tmobile and.AT&T. please advise on what I can do and links for downloads if possible. Thanks in advance.
Sent from my SO-01G using XDA Free mobile app

Question IMEI Recovery

Hello everyone, I have unsuccessfully flashed 5 or so GSI roms and eventually even flashing back to Android 9 would still result in bootloop. I formatted and downloaded Android 9 and now the phone boots but the IMEI's are blank.
I can connect with Modem META but am unable to readback with SP flash tool to get my nvram file.
Could someone provide me with the nvram file to add my IMEI numbers again with Modem META?
I am on the stock Android 9 (TA-1188)
djinc91 said:
Hello everyone, I have unsuccessfully flashed 5 or so GSI roms and eventually even flashing back to Android 9 would still result in bootloop. I formatted and downloaded Android 9 and now the phone boots but the IMEI's are blank.
I can connect with Modem META but am unable to readback with SP flash tool to get my nvram file.
Could someone provide me with the nvram file to add my IMEI numbers again with Modem META?
I am on the stock Android 9 (TA-1188)
Click to expand...
Click to collapse
You can get your nvram using a different tool, https://github.com/bkerler/mtkclient. Flashing again the latest firmware may fix the nvram issue.
SubwayChamp said:
You can get your nvram using a different tool, https://github.com/bkerler/mtkclient. Flashing again the latest firmware may fix the nvram issue.
Click to expand...
Click to collapse
Thank you, I will try that tomorrow after work and post my results.
SubwayChamp said:
You can get your nvram using a different tool, https://github.com/bkerler/mtkclient. Flashing again the latest firmware may fix the nvram issue.
Click to expand...
Click to collapse
Well I am getting closer. I pulled my nvram from the phone using mtkclient. However when I went to use Modem Meta it is looking for a firmware db file. They have one on their website but it is version 88 and my phone is version 50. If I load the db from the phone itself I can attempt to enter my IMEI numbers but it states they should be 14 digits or less. Mine are 15 digits.
I am going to update to stock android 11 and hope that is version 88 so I can try again.
djinc91 said:
Well I am getting closer. I pulled my nvram from the phone using mtkclient. However when I went to use Modem Meta it is looking for a firmware db file. They have one on their website but it is version 88 and my phone is version 50. If I load the db from the phone itself I can attempt to enter my IMEI numbers but it states they should be 14 digits or less. Mine are 15 digits.
I am going to update to stock android 11 and hope that is version 88 so I can try again.
Click to expand...
Click to collapse
I never had this issue, with this version https://mtktool.com/modemmeta-v10-2044-0-02, you have to write the first 14 digits and the tool automatically writes the last one.
SubwayChamp said:
I never had this issue, with this version https://mtktool.com/modemmeta-v10-2044-0-02, you have to write the first 14 digits and the tool automatically writes the last one.
Click to expand...
Click to collapse
Yeah, I'm just an idiot. I did some research on IMEI numbers and realized I only needed the first 14 digits.
Thank you for all of your help!

Categories

Resources