Hey guys,
Like many T-Mobile G2x users i got seriously fed up with the poor gps K on the phone. When i first got my phone, after i rooted it I tried many of the roms here on the development forum but none of them could fix the gps locking issue. IN the past few days, the phone could not even "view" satellites at all. I was running the JUL 2011 baseband at the time. However after digging around, I went ahead and updated from the LG website with their update software. now my current baseband is M6600A-SCAUTNZ-2.0.9720T 1 [MAR 11 2012 10:00:00] MP:TRULGE_08.09.02R-MDM and gps functionality comletely came back. I have a lock under 1 min, the phone still works for calls/text, and data still works.
I ran this process on a computer with Windows 7 Ultimate 64-bit. After the LG update completes it will revert the phone to stock recovery.
Here is a step by step of what I did. Please read everything first before doing the steps.
1. Use TGA_Gunman's guide to restoring a stock Nandroid OS that is unrooted. http://forum.xda-developers.com/showthread.php?t=1048274
A Stock ROM (v21e, v10f, or possibly others) is required for the "LG MOBILE SUPPORT TOOL" to work. Either from a personal backup or downloaded. Recovery version doesn't matter, but suggested to have latest CWM to make Nandroid backups & restores easier.
2. (optional) After you boot into the system link your google accounts, just as you would when opening a phone for the first time.
3.Visit LG's Website and download the T-Mobile LG G2x software update tool.
http://www.lg.com/us/support-mobile/lg-P999 (click on the software update tab and follow the 4 steps)
4.After installing LG Update software on your computer, run it, and follow the steps it tells you exactly.
5.Have PATIENCE! This will take around 15 min. and patience is the key. Let it sit there and do it's thing. Make sure your computer doesn't turn off or go into standby during the process and don't disconnect your USB cable until the installer is at its last step and its tells you it's done with the update.
6. Enjoy your functional gps!
P.S.: Thanks to everyone for the helpful feedback and tips to making this guide better!
If you are looking to downgrade your baseband or have unknown baseband error check out xBkKx's guide http://forum.xda-developers.com/showthread.php?t=1680292
EDIT 06/2/2012:
The CM7 RC3 update has been verified that it will work with the new March 2012 baseband. If you wish to update to the rc3, apply a "dirty flash" of the 27th nightly update after it (this resolves the gps locking time back to a couple of seconds again).
CM7 RC3 Update link : http://download.cyanogenmod.com/get...t/archive/update-cm-7.2.0-RC3-p999-signed.zip
CM7 27th Nightly Build: http://download.cyanogenmod.com/get/jenkins/1991/update-cm-7-20120527-NIGHTLY-p999-signed.zip
Why wouldn't you have calling/data after updating only calling issue is people not wanting to stay stock with this baseband.
You don't have to be on that nandroid or link your Google account prior to the update.. I restored my rooted stock nandroid downloaded drivers, installed lg tool and it updated fine as I just walked away and came back to it sitting in home screen with new baseband
Sent from my LG-P999
xBkKx said:
Why wouldn't you have calling/data after updating only calling issue is people not wanting to stay stock with this baseband.
Isn't there already guides to update the phone?
You don't need to be on that nandroid or link your account.. I restored my rooted stock nandroid downloaded drivers, installed lg tool and it updated fine as I just walked away and came back to it sitting in home screen with new baseband
Sent from my LG-P999
Click to expand...
Click to collapse
When i said calling/data still works i was referring to what some other people in the forums had said that they couldn't get a signal after updating baseband. I, however, did not find anything about using LGs update tool on windows 7. All the topics that came up were about procedures on doing it with windows xp only.
If this way works with the other nandroid versions that thats great news . However, when i was on the July 2011 baseband and I loaded one of the other stock nandroid versions the earpiece and microphone were not working at all. I could place/receive calls but the other person could not hear me nor could i hear them. when I loaded the v10f stock this problem did not come up, so just to be safe I recommend using that one.
Also you said there's calling issues for people that want to use other roms with this baseband? Does that mean I can't load up one of the recent EB ICs roms, etc with this baseband version?
call audio doesnt work with newest baseband and modded roms (tother than kwes's and buru's, both of which are based on V21Y). it just clicks and pops unless you are on wifi calling. basically devs need to start basing their ENTIRE rom on this baseband if they want call audio to work.
BuddhaTeh1337 said:
call audio doesnt work with newest baseband and modded roms (tother than kwes's and buru's, both of which are based on V21Y). it just clicks and pops unless you are on wifi calling. basically devs need to start basing their ENTIRE rom on this baseband if they want call audio to work.
Click to expand...
Click to collapse
actually now the 27th CM nightly update and the CM7 rc3 update have fixed the in call audio problem. im running this update with the new baseband on my phone and everything is working fine. the only thing that doesnt work yet are the old ROMs .hopefully devs do something about that
I also updated from rooted stock (xboarders 2.3.3). I didn't go back to stock recovery. I just ran the LG updater (already had drivers installed), plugged in the phone, hit the update button, and let it do it's thing. It took about 20 minutes
I'm confused about all of the confusion.
XDA Mobile
Hi all,
I did the above procedure, and did the restore from the "LG-P999-V10f" image.
On reboot, the phone comes up and shows the stock "LG" boot up screen.
The scrolly thing goes across for a bit, and then *stops*!
At this point, it is locked up, it won't boot any further up, and when I attempt to use the LG Updater tool, it does see the phone, and says "Phone connected", but the 2nd part of it when checking the phone communication, it fails with "Problem with communication between the cell phone and PC".
So I am stuck...
(Hopefully not bricked?)
Any thoughts? Suggestions?
Thanks!
Scott
I figured it out, after some minor panic!
The problem was, my ClockWork Mod Recovery bootloader version on the phone was too old!
I used a factory ROM image that was taken from a newer version, and it included some (.tar's I think) file types that weren't supported on the old version of the Recovery.
Thus, I burned an incomplete version of the stock firmware to the phone!!!
(Which is why it was stuck at boot!)
I was able to "One Touch Recovery" with a newer version of Clockwork Mod, slap my Backup of my CM in place, and get back to where I started.
And as part of the "One Touch Recovery", it updated my boot loader to a newer version, and so now the loading of the factory ROM image worked.
I then just ran the LG Updater software after going back to the factory ROM Image, and indeed, it finally works as expected!
Scott
Glad to hear that it worked Scott! And thanks for the feedback, i have updated step 1 to say you need latest version of clockwork recovery
It looks like LG may have taken the update file down, or for whatever other reason, the software update tab is blank. Could someone put up a link to the update file?
@sigmabeta: I noticed during a particularly slow page refresh that the links for the usb driver showed up briefly as the page loaded, then disappeared. I managed to stop the page from loading completely and got the 4 steps listed (under manuals, of all places) one of the links was the update tool, here is the link:
h-t-t-p://csmg[dot]lgmobile[dot]com:9002/clientapp/B2CAppSetup.exe
I downloaded it successfully from there. Enjoy!
(sorry I'm new and it won't let me post links yet)
LG update tool won't update
I managed to download it from LGs site, but despite flashing the v10f rom onto my phone, the update tool says software version is 11f (even tho the phone info shows 10f) and that it is up to date, and won't let me perform the update. Baseband is still Jun 2011. Any ideas, or a link to the version of the setup tool you used?
aft3rgl0w said:
I managed to download it from LGs site, but despite flashing the v10f rom onto my phone, the update tool says software version is 11f (even tho the phone info shows 10f) and that it is up to date, and won't let me perform the update. Baseband is still Jun 2011. Any ideas, or a link to the version of the setup tool you used?
Click to expand...
Click to collapse
hmm. im not sure about this one. try this: reboot into clockwork recovery mod and do factory reset . after clear your cache, then clear your dalvik cache. then install the v10f from the restore menu in clockwork mod . after restart, set up your phone as you would do for first time (link google account to it) and then plug it in to your computer and run the LG update tool. thats what i did and it worked for me
also you said version v11f? you must have not flashed the restore correctly. do the above.
The first time I flashed it, I followed the instructions, which said to factory reset AFTER the flash, but I did think of what you suggested and tried it again, factory resetting, clearing cache and dalvik twice before restoring, but the tool is still saying the SW version is 11f. If I go to Customer Support -> Update history, it shows SW v21e (even after reading phone info). Phone info SW ver says LG-P999-V10f. Weird. Should I factory reset/cache/dalvik _after_ flashing the v10f rom as well? i'll re-download it again and try in the morning. what version of the LG updater tool do you have? mine is v1.5.7.0. many thanks for your help.
aft3rgl0w said:
The first time I flashed it, I followed the instructions, which said to factory reset AFTER the flash, but I did think of what you suggested and tried it again, factory resetting, clearing cache and dalvik twice before restoring, but the tool is still saying the SW version is 11f. If I go to Customer Support -> Update history, it shows SW v21e (even after reading phone info). Weird. Should I factory reset/cache/dalvik _after_ flashing the v10f rom as well? i'll redownload it again and try in the morning. what version of te LG updater tool do you have? mine is v1.5.7.0. many thanks for your help.
Click to expand...
Click to collapse
yes. you should do a complete factory reset even after installing the v10f rom. this is detailed on the original post on how to flash back to stock rom in TGA_Gunmans post.
I just noticed too that it reverted back to froyo (v2.2.2) and not GB, could this be part of the problem? should the stock be 2.3?
just to clarify your last reply re factory reset after v10f flash - should i clear dalvik as well?
yes it should revert back to froyo. and yes reset the dalvik cache too
Have you tried the V21E? I just flashed back to my Jul baseband and restored my 2.3.3/V21E nandroid and the updater found the 2.3.4 release instantly for my phone
Sent from my LG-P999
xBkKx said:
Have you tried the V21E? I just flashed back to my Jul baseband and restored my 2.3.3/V21E nandroid and the updater found the 2.3.4 release instantly for my
Sent from my LG-P999
Click to expand...
Click to collapse
yes you could try the 21e. however for me, that version always failed to download from the website gunman uses to host those files so i used the v10f inatead. much faster download.
btw how do you revert back to a previous baseband?
I just Googled how to do it using like 6 different guides :/ I edited my thread on iso help on it with what worked for me if you want to try it: http://forum.xda-developers.com/showthread.php?t=1680292
V21E/2.3.3 Mirrors, just restore it, connect phone to computer, run updater, should go smoothly :
Dropbox
MediaFire
RapidShare
I've been checking for updates manually through the settings option but it keeps telling me the phone is up to date. Does anybody else have this problem. On Android 2.3.6. The system version I have is 55.13.22.MB865.ATT.en.US. I am currently overseas but anytime an OTA update has been released I've received it before while being out here. Tried searching around a few days on google and on this site but can't find a solution. Any help please??
Mine updated yesterday. Try again.
Sent from my MB865 using xda app-developers app
tpatur1 said:
I've been checking for updates manually through the settings option but it keeps telling me the phone is up to date. Does anybody else have this problem. On Android 2.3.6. The system version I have is 55.13.22.MB865.ATT.en.US. I am currently overseas but anytime an OTA update has been released I've received it before while being out here. Tried searching around a few days on google and on this site but can't find a solution. Any help please??
Click to expand...
Click to collapse
Reboot your phone, then go to settings, about phone, then check for updates again. If that does not work, try and clear cache and check again. Also make sure you try to check while on wifi as well, because it most likely will not let you download the update while on cell data.
Tried restart, clearing cache and while on wifi -- still no update. Guess I'll just wait it out and hopefully it updates soon.
Try idigitaltimes.com/articles/11784/20121013/motorola-atrix-2-ics-update-download-install.htm
Good Luck.
Sent from my MB865 using xda app-developers app
I am overseas and updated my phone, but I did have an issue with the update servers not being able to see my device. It is sometimes the case where an FDR (factory data reset) is needed for the update servers to be able to see your phone again (generates a new underlying Moto sync account). I had to do an FDR to get the update servers to see my device.
First try the following to force a login to the Moto update servers.
Dial #ELIOT# in the stock dialer and then wait for it to have a pop up. Then power the phone off, back on and then check for updates again.
If that does not work then do an FDR and then check for updates again after your phone has been reset.
Good luck.
jboxer said:
I am overseas and updated my phone, but I did have an issue with the update servers not being able to see my device. It is sometimes the case where an FDR (factory data reset) is needed for the update servers to be able to see your phone again (generates a new underlying Moto sync account). I had to do an FDR to get the update servers to see my device.
First try the following to force a login to the Moto update servers.
Dial #ELIOT# in the stock dialer and then wait for it to have a pop up. Then power the phone off, back on and then check for updates again.
If that does not work then do an FDR and then check for updates again after your phone has been reset.
Good luck.
Click to expand...
Click to collapse
--
Still no update!! So after just giving up and waiting I thought I'd try this again and see if anyone else could help. Tried everything mentioned already and still getting the message that my phone is up to date.
System Version: 55.13.22.MB865.ATT.en.US
Android Version: 2.36
Baseband Version: 2011-11-16 23:52 Off.Bld LUD_EDISON_R1D7_PATCH_36_111116_2336
Webtop Version: WT-1.3.0-176
Kernel Version: 2.6.35.7-g98a0a06 [email protected] #1
Build Number: 5.5.1-175_EDMR1.22
SOMEONE PLEEEASE HELP ME UPDATE THIS PHONE!
"55.13.22"
Sounds like you've gotten yourself one of the early leaked update builds. I'd recommend FXZ-ing directly to ICS, or fxz to the 55.13.25 build and updating from there.
At one point more than a year ago, there was an update pushed down from the update server to update from 55.13.22 to 55.13.25, but you'd have to find someone that has stashed that away. (I don't think I have it saved anymore)
tpatur1 said:
--
Still no update!! So after just giving up and waiting I thought I'd try this again and see if anyone else could help. Tried everything mentioned already and still getting the message that my phone is up to date.
System Version: 55.13.22.MB865.ATT.en.US
Android Version: 2.36
Baseband Version: 2011-11-16 23:52 Off.Bld LUD_EDISON_R1D7_PATCH_36_111116_2336
Webtop Version: WT-1.3.0-176
Kernel Version: 2.6.35.7-g98a0a06 [email protected] #1
Build Number: 5.5.1-175_EDMR1.22
SOMEONE PLEEEASE HELP ME UPDATE THIS PHONE!
Click to expand...
Click to collapse
1-download fxz from here http://sbf.droid-developers.org/edison/list.php
md5=2BF9CCD528C05D26523ACC5B38AC76C6
2-Follow "how to fxz" In noob guide here http://forum.xda-developers.com/showthread.php?t=1396650
Hi,
I have a 1+ yr old Galaxy S3 (so out of the warranty period). I'm getting camera fail messages. When it's not working, here's what happens:
When I try to use the stock camera app, it goes into the camera interface, hangs for a bit, and then I get a message saying "Camera Failed"
If I try to use another app that uses the camera, I get a message that the camera is in use.
So it seems to me like there is some app that is hijacking my camera, rendering it unavailable. I got in touch with Samsung tech support, and they had me reboot into safe mode, test the camera, and then reboot normally. That works to reset the camera, and I can then access it, until it happens again.
Does anyone know what the problem might be, or which app might be interfering? Is there a way to get a list of all apps that use the camera, so I could do some trouble shooting?
Thanks in advance for any help you can give.
Could you post your about phone details? Are you sure you have a Verizon Galaxy SIII (sch-i535)? Because we do not have a stock, non-rooted 4.2.2 rom.
Oops, 4.1.2, not 4.2.2
SlimSnoopOS said:
Could you post your about phone details? Are you sure you have a Verizon Galaxy SIII (sch-i535)? Because we do not have a stock, non-rooted 4.2.2 rom.
Click to expand...
Click to collapse
Yes, and I made a mistake in the title, it's 4.1.2, not 4.2.2.
Model SCH-I535
Android 4.1.2
Baseband version 535VRBMF1
Kernel Version 3.0.31-1152558 [email protected] #1 SMP PREEMPT Sat Jun 8 17:20:08 KST 2013
Build Number JZO54K.I535VRBMF1
Hardware Version I535.10
seattlecubsfan said:
Yes, and I made a mistake in the title, it's 4.1.2, not 4.2.2.
Model SCH-I535
Android 4.1.2
Baseband version 535VRBMF1
Kernel Version 3.0.31-1152558 [email protected] #1 SMP PREEMPT Sat Jun 8 17:20:08 KST 2013
Build Number JZO54K.I535VRBMF1
Hardware Version I535.10
Click to expand...
Click to collapse
Ahh, ok haha kinda got my hopes up for a second lol hmm, as a stock user, your options are kinda limited. What I can suggest is that you use Odin (a Windows program) to flash VRBMB1 firmware and see if this will resolve your camera issues. This is the quick and simple method. Essentially doing this will downgrade your modem to VRBMB1 and several files to VRBMB1 4.1.2. Doing this is compatible with all ota's even older ones. You can download the tar file here and Odin from here. You can follow step one in that guide but all you're flashing is the VRBMB1 firmware that I linked. Alternatively, the more complete suggestion is to Odin flash a full 1 GB stock tar which will erase all of your data on the phone and it will be reset to out of the box stock. If your camera does not work still then it would very likely be a hardware issue.
Does anyone know what the problem might be, or which app might be interfering? Is there a way to get a list of all apps that use the camera, so I could do some trouble shooting?
Click to expand...
Click to collapse
I'm not too sure about this question btw. Maybe someone else can provide input on an app or utility that does this? For now, the best I could suggest is uninstalling any apps you know access the camera then trying to add them one by one until you can see the issue.
Hey Guys,
this morning I got offered a new OTA update for my Note 10.1.
Since I've never fiddled around with the device (no root, no custom rom and so on) this never was a big deal for me, so I just installed it as usual.
After the update my device is stuck in a bootloop.
What I tried so far:
Connecting to KIES - failed
Recovery Mode -> Cache Wipe - failed
Recovery Mode -> Factory Reset - partly failed
Recovery Mode -> Factory Reset + Cache Wipe - partly failed
What I mean by partly failed is the following:
The device boots as normal (with factory settings) but as soon as I plug it in to KIES to sync my contacts it crashes and goes to bootloop again.
Now to the weird thing:
When I'm in recovery mode I get an error which (I suppose, at least) shouldn't be there:
Apllied the CSC-code : DBT
did not match sized '/system/csc/common/system/wallpaper/lockscreen_default_wallpaper.jpg' (No data available)
This error points to the lockscreen wallpaper?! And the REAL weird thing: While in bootloop sometimes the device gets through to my wallpaper, which then is the "old" wallpaper I had BEFORE the reset. How can that wallpaper still be there after I did a factory reset? There is no SD card in my device.
Is there any way to get back to a working version? I guess it botched up the OTA-update and now has a broken firmware or something like that...
I have no experience in Android modding/flashing whatsoever, but I'm pursuing my masters degree in Information Systems right now, so I'm not a total noob for what it's worth!
P.S.: I don't care about rescuing any data, there was nothing important which is not already backup'd on the tab... I just don't want to have a 500$ paperweight laying around ^^
Thanks in advance for any help!
You can go to sammobile.com and download manually a firmware that fits your device and flash it through odin. That will wipe the tab and flash a fresh stock firmware.
What is your version of the Note 10.1? So I can help you choose the correct firmware if you need.
Also check this video by zedomax and learn all the steps to flash correctly.
https://www.youtube.com/watch?v=NsDOSvBdALg
Sent from my GT-N8013 using XDA Premium 4 mobile app
kalashenicof said:
What is your version of the Note 10.1? So I can help you choose the correct firmware if you need.
Click to expand...
Click to collapse
Thanks for the fast reply and the information.
Not sure what you need as a "version", this is all I could get before it crashes and goes back to the bootloop:
Model #:
GT-N8000 (it's the one with Wi-Fi + 3G)
Android Version:
4.1.2
Baseband Version:
N8000XXCLL1
Kernel Version:
3.0.31 - 1388206
[email protected] #1
SMP PREEMPT Wed Sep 11 13:39:10 KST 2013
Build#:
JZO54K.N8000XXCMI2
Oh, and I'm from Germany, if that information is relevant!
Thanks in advance!
Your right it's model and not version
Check this out http://www.sammobile.com/firmwares/3/?download=19291
Check if the information matches, then download and flash it via odin.
Make sure you login to samfirmware first.
Hope it helps, if you need something else just ask.
Sent from my GT-N8013 using XDA Premium 4 mobile app
Thanks man! I downloaded the firmware and flashed it according to the video.
My tab boots fine now and the error is gone aswell... It crashed one more time though, but runs stable since. I have to keep an eye on it!
Glad it works now =)
Sent from my GT-N8013 using XDA Premium 4 mobile app