[Q] LGMobile Support Tool says already the latest version - T-Mobile LG G2x

The LGMobile support Tool reports that I have model LGP999DW and version V10F, but also says that "The Cell phone is the latest version already." Occasionally it will report my model as simply LGP999, in which case I can start updating, but it stops at around 40% with the message "model not supporting S/W update."
If I look under Customer Support > Supporting Model I do not see the LGP999DW listed but I do see LGP999WA. A google search for LGP999WA turns up only one link to a LG site that has a global list of phones that can be updated.
So, do I have a bad version of the update program? Has the update for this phone been pulled even from LG's site? And if I cannot update through LG's program, how do I get the new baseband?
Thanks for your help, because this is getting really frustrating.

Try this method. http://forum.xda-developers.com/showthread.php?p=17258229
Sent from my LG-P999 using xda premium

That did update me to 2.3.3, but it did not upgrade the baseband, which is the whole point of going through the LG updater. The updater still says that I am on version V10F even though the phone says V21e, and it still says that I am up to date.
It also appears that I am now on stock recovery, when I had CWM before. However, I cannot get into stock recovery. Holding down the "down volume" button and power launches an icon of a box with an arrow coming out of it and andy, and appears to do a factory reset of my phone. Is this how stock recovery works, or is it an indication that something is wrong?
Finally, the LG updater program always stops on "checking phone #", is this indicative of something?

If the method I suggested completed. And the phone shows the new baseband. I would tend to believe the phone. It should have flashed everything to stock including the recovery. Just nvflash the latest cwr. And the stock recovery will "factory reset" the phone when using vol down + power.
Sent from my LG-P999 using xda premium

The phone says that the baseband has not been updated. It still has a date of March 27 2011. The lg updater only gives me information about the software version.

Did you try the kdz method? I can't find the thread right now from my phone facepalm but it was posted in the general section, I believe.
Edit.. I found it Here's the link.
http://forum.xda-developers.com/showthread.php?p=15936150
Sent from LG-P999 using xda premium

The updater appears to be messed up. Only shows it supports that model you mention which, as far as I know, is not a valid US model number. Hopefully LG fixes it.

I mean no offense by this, but to me I find this funny. Reason for this is that I have the LGP999WA, it is the model T-Mobile was giving out at the Gadget Chicago event and on Twitter Friday last week (Sept. 16th or 15th I think the date was).
Now as for the updater program, the updates through it have been disabled till LG can fix some sort of driver issue for the program/phone (was stated clearly for which), and I got that straight from the tech rep Sat. afternoon when I was trying to make sure my phone was fully updated.

kaeruil said:
I mean no offense by this, but to me I find this funny. Reason for this is that I have the LGP999WA, it is the model T-Mobile was giving out at the Gadget Chicago event and on Twitter Friday last week (Sept. 16th or 15th I think the date was).
Now as for the updater program, the updates through it have been disabled till LG can fix some sort of driver issue for the program/phone (was stated clearly for which), and I got that straight from the tech rep Sat. afternoon when I was trying to make sure my phone was fully updated.
Click to expand...
Click to collapse
Probably for the issue that during the update the updater resets the device's USB connection three times. It is during these resets that the connection error can occur. This is what has been soft-bricking people G2X's. I had it at my first reset but simply removed the USB cable and reinserted it, waited for the computer to beep and pressed restart and it finished in about 15 minutes. I ignored the moronic instructions about doing a battery pull on the device itself first. They need to do the update without resetting the USB or have a driver that connects faster; or have a longer timeout in the updater program to allow enough time for the phone to reconnect to the computer. It is flashing four files, so I think it is resetting the USB between each file flash. Don't know why and it is not a good way to do things; but certainly an easy way to brick phones.

Alright, thanks for the information, its really helpful to know that its not just me. For now, I have flashed to cyanogen, and will attempt to update the baseband at a later time.

Just so people know I checked the updater and all the models have been restored. They are still on V21e rom (Our 2.3.3 GB rom). The models listed are LG-P999DW, LG-P999DWP, LG-P999DWDU and the new and mysterious LG-P999WA.

Related

Prototypes and Developer versions

I found 2 firmware versions on the forum that are dated before the official launch of the phone, an April one, LGP920-V08i-APR25-2011 (which I also have), and a May one, P920-V08j-MAY-03-2011. Some people reported being able to update to other ROMs by installing CWM, but all of them (if I read correctly) had the May ROM initially. Was anyone with the April version able to get a new firmware without the bricking or non-charging battery issues, or are we all who have these prototype phones doomed? I've read the O3D section for a full day, and I'm too terrified to try flashing or installing CWM, even though as an LG GT540 user I've swapped ROMs and unbricked my phone too many times to count.
sandulea said:
I found 2 firmware versions on the forum that are dated before the official launch of the phone, an April one, LGP920-V08i-APR25-2011 (which I also have), and a May one, P920-V08j-MAY-03-2011. Some people reported being able to update to other ROMs by installing CWM, but all of them (if I read correctly) had the May ROM initially. Was anyone with the April version able to get a new firmware without the bricking or non-charging battery issues, or are we all who have these prototype phones doomed? I've read the O3D section for a full day, and I'm too terrified to try flashing or installing CWM, even though as an LG GT540 user I've swapped ROMs and unbricked my phone too many times to count.
Click to expand...
Click to collapse
CWM is your friend.... try and install something after you have made a backup and if all goes wrong just restore your backup...
http://forum.xda-developers.com/showthread.php?t=1202022
Clockwork was my first idea as well, but its installation also causes problems, mainly with the April ROMs.
sandulea said:
http://forum.xda-developers.com/showthread.php?t=1202022
Clockwork was my first idea as well, but its installation also causes problems, mainly with the April ROMs.
Click to expand...
Click to collapse
you dload lg flash tool. shut the phone down. remove battery. connect it pressing vol-up then chose emergency update from menu.it will ask you your IMEI s/n and phone model. insert IMEI without - in between numbers. at 50% it will get stuck saying connection with phone was lost. dsiconect it without pressing anything insett battery and reconnect by pressing vol-up. press retry and wait. it should get you latest lg firmware. and if anything goes wrong you take it back to lg *****ing about how their software messed up your phone.
ps I only said remove battery before starting the process is cause mine had problems if the battery was on when i inserted the IMEI. it was not recognised.
I think I'll have a few more gray hairs after tonight... I went ahead and installed Rom Manager, flashed CWM, and, as I expected, after reboot it would only boot in Clockwork Recovery mode. I started to get really nervous. I then made a backup of the original April v08i ROM (not entirely clean, unfortunately), then I flashed v10B as written here: http://forum.xda-developers.com/showthread.php?t=1186460 . I wiped data, cache and nv dynamic partition, rebooted and it booted into Android! Now I expected it to not charge, but after 5-10 minutes the battery went from 63 to 73 percent (!!!).
I really hope it works out eventually. I'll take the phone off the charger once it's full, then reboot, play some 3d games to bring down the battery and charge it again. If no problems appear, I think I'll wait patiently for the official Gingerbread and Ice Cream Sandwich and stay out of custom ROM trouble.
EDIT: v10b, SIM and SD card in, 2 reboots later, and it's still able to charge, so I guess it's all fine. The battery appears to last longer (v08i drained out fully in a day in moderate use), 3D videos look better, 3d filming isn't as dark, but still a little dark, and surprisingly it feels a little slower, mostly around the launcher. However, I feel like I really dodged the bullet, because I installed CWM thinking I'll be taking my phone to an LG service center on Monday. OTA updating still doesn't work (same auth error as on v08i), so I'll have to update to 2.3 (and 4 if we'll ever have) some other way. But I'll cross that bridge when I get to it, and as far as I know I won't be the only one in this situation.

[Q] g2x Major Problems after Rooting / unRooting

Alrighty.. This phone has caused me so much time and trouble, I finally decided to start a thread. I really cannot find an answer for my problems by surfing...
In the beginning, all was great. Then I wanted to root my phone...
I went here and followed these instructions to root initially.
http://forum.xda-developers.com/showthread.php?t=1179748
(Stock Gingerbread OTA 2.3.3 Rooted)
I started to have problems:
-WIFI kept shutting off upon sleep. I depend on WIFI because I only have a 200MB plan..
Also, I have low signal in my apartment, so I use wifi calling very frequently. After about 10 minutes, wifi calling disables itself.
SO, I wanted to UNROOT. The link that said 'UNROOT' did not work..
Next, I used this link to unroot..
http://theunlockr.com/2011/05/23/how-to-unroot-the-t-mobile-g2x/
I returned to stock froyo OS. BUT i still wanted gingerbread!! I tried to use the LG update desktop tool, but it kept on saying that 'the phone was already up to date.'
SO, I ended up 'installing from zip' the backup that was made before I downgraded to froyo.. Unfortunately, this left me back at square one: A rooted gingerbread.. Exactly where I was before.
I went to this link next.
http://forum.xda-developers.com/showthread.php?t=1255214
I used the 'UNROOT ZIP', and it unrooted it!!
Seems perfect right??
BUT, ever since I did that, my GPS doesn't work. It is unable to pick up my location.
I tried to 'restore to stock' using BOTH the option while the phone is on, and using the 'clockwerk mod' (Where you hold power and the down button).
I just want things to go back to the way they were.
I'm hoping that I can just have a NORMAL 2.3.3, with GPS working, and everything back to the way it was before I started this whole 'root' journey..
Thank you so much ahead of time for taking the time to help me. Your 5 minutes could save me hours..
try restoring to stock, 2.2.2, then get the LG Updater tool to "Recovery Phone" which is at "Customer Support" and the last one, enter your phone model, and serial number, and it should recover it to stock with no problems for you. Good Luck.
Wifi is suppose to shut off on sleep mode unless you configure it not to.
Sent from my LG-P999 using xda premium
ed116 said:
try restoring to stock, 2.2.2, then get the LG Updater tool to "Recovery Phone" which is at "Customer Support" and the last one, enter your phone model, and serial number, and it should recover it to stock with no problems for you. Good Luck.
Click to expand...
Click to collapse
I will try this now.
Thanks. Hopefully it works.
It still says 'Update not required' after I use the recovery version.
It is saying that because just flashing 2.2 you are still on the July baseband which is telling the software you are on the latest. You should be able to find a stock nandriod in the forum somewhere to flash Gingerbread stock.
Go to Wireless and networks > Wifi > hit menu > Wifi sleep policy > never.
Sent from my MIUI G2x using XDA Premium App
GTWalling said:
It is saying that because just flashing 2.2 you are still on the July baseband which is telling the software you are on the latest. You should be able to find a stock nandriod in the forum somewhere to flash Gingerbread stock.
Click to expand...
Click to collapse
I was unable to find such a thread. I decided just to root it and go with the 'eagle' and deal with random problems..
However, the front facing camera keeps on stretching the picture..
Any thoughts?
FFC issues are common on non-stock roms trying to use LG camera instead of Android stock camera. Rooting your phone cannot cause wifi issues, etc. unless you made some errant changes to system files. Rooting does nothing but allow you or programs to get what is called in the Linux world SuperUser permissions. It allows you or the program to change or do anything it wants and removes the restrictions placed on the handset by the manufacturer and/or Google. All the rooting process does is add two files to your system and set the proper permission for su to be able to become root. The SuperUser.apk is the gateway to root. It is there to protect you from malicious programs getting root, as you have to approve all root access requests. It is actually very safe unless you do something stupid.
yoo992 said:
I was unable to find such a thread. I decided just to root it and go with the 'eagle' and deal with random problems..
However, the front facing camera keeps on stretching the picture..
Any thoughts?
Click to expand...
Click to collapse
Here is a link to both Froyo and Gingerbread.
http://forum.xda-developers.com/showthread.php?t=1037120

Trying to update from Froyo Stuck at 4% don't know how to stop

Title says it all. I am trying to update (from Froyo) with LG update tool. Everything seemed to go well but now its stuck at 4%. How do I go about disconnecting and trying again? We're talking right now....been stuck there according to elapsed time 1 hr 27 minutes. If I just disconnect the phone will I brick it?
http://forum.xda-developers.com/showthread.php?p=24910877#post24910877
Go to that post. It has what to do. I was stuck on it also. I did that.
Thanks for the reply. I ended up disconnecting it and removing the battery. When I turned it back on, it was still on the upgrade screen. Plugged it back in and it restatrted the download and completed it. I guess I'm on the new firmware now.
V21e?
Thats old. New baseband is v21y.
P.S: Sorry, didn't see you were on froyo before. Yeah then it did update it for you. Its just that a new firmware was made available from LG a while back.
So I should do it again?
No. You won't be able to. Its been pulled. Wait for a few weeks. If you are on stock rom, You will get OTA update to v21y from tmobile or LG.
I thought they reposted it yesterday, available for manual download? That's why I tried it today.....
Edit....OK I reread it on Tmobiles site.
http://support.t-mobile.com/docs/DOC-2362
OTA Update
The G2x will receive a notification that the update is available.
Select Update.
The update will install.
Once complete the phone will restart.
It says it will come to you. Go to your software update and see if it lets you update. I think its on their timing. Not yours. Then again, I am not with any US Carrier so i don't know how the update might work. Sorry.

[GUIDE] UPDATING TO MARCH 2012 Baseband[LG Update] [Win7]

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

FreedomPop Motorola Photon Q 4G LTE xt897c, want help with Cyanogenmod

Hi xdadevelopers,
I ordered a Motorola Photon Q 4G LTE (xt897c) phone from FreedomPop for $25 and 28 days later it has arrived. My experience with FreedomPop has been decidedly mixed. Lots of hassle from customer service combined with a product that is sometimes very useful and always cheap. (Unless you use over 2GB of data per month) The phone itself seems very adequate for an excellent price. I would like your assistance in putting Cyanogenmod or another appropriate ROM on it.
Here's where I am,
The phone appears to have been rooted out of the box according to "Root Checker Basic" from Google Play
I installed "Superuser" from Google Play and that seems to work correctly
Busybox seems to be present already according to "Online Nandroid" from Google Play
I have created a TWRP Backup using Online Nandroid without modifying the recovery
The phone currently has Android 4.1.2
Where I want to be
I want to install a custom recovery, preferably one I can make backups from
I want to update to a more recent version of Android such as the stable one found here DUCK RULES cyanogenmod bot org /?device=xt897c or another version where everything just works
Notes. I have ADB and Fastboot installed from "Android Studio". I have an appropriate USB cable. I do not have a microsdhc card right now. It appears "Sandisk 64GB Extreme Micro SD (SDXC) Card + Adapter 60MB/s Class 10 U3 UHS-1" at DUCK RULES amazon bot com /gp/product/B00N98QLRQ is a good choice for a good price. I have this on order and should have it within the week.
I understand this phone has a locked bootloader. The "Messaging" app from FreedomPop available in Google Play seems to control messaging and the phone dialer. I went to the official Motorola Bootloader unlock page DUCK RULES motorola-global-portal bot custhelp bot com /cc/cas/sso/redirect/standalone%2Fbootloader%2Funlock-your-device-b I booted into recover with Power and volume up and volume down held, selected fastboot, connected to the computer , ran fastboot, as described, got the code, put the code in the webpage as described, and got a blank page. This happened 2x, with no emails form Motorola. I tried a third time 6 hours later, and it loaded a page with more instructions and I had the bootloader unlock code in my email instantly (There were no preceding messages, they didn't go to spam or somewhere else). I have installed TWRP Manager by Jmz software from Google Play. The standard reboot method doesn't work I changed the settings to "Reboot using an alternate method". I attempted to the TWRP recovery with the "Install TWRP". One must select their device and the closest thing to mine was "Motorola Photon 4G" codename "sunfire". This didn't appear to be it exactly but there wasn't a better choice. The next line down says "custom recovery not installed or detected". Then I selected the recovery version to install "2.6.3.0" "openrecovery-twrp-2.6.3.0-sunfire.img appeared the most recent, then I attempted to "Install Recovery" The phone downloaded the image, and said "Ensure the partition listed below is the correct one for your device..." "/dev/block/mmcblk0p10" how do I know if that's correct or not? I said yes to the question and went ahead, the phone rebooted to an Android on it's side with a yellow triangular sign with an exclamation point above it. Thirty seconds later the phone rebooted normally and everything worked no custom recovery was flashed.
Also thanks to the xdadevelopers community for your past and future efforts. I threw in my lot with Android when the neXus One launched after watching the keynote, buying it full price and paying extra for next day air shipping. I stayed stock despite the cool stuff being done by the development community until Google fell behind in updates. Then I started with CM6 and later went to CM7. That was wonderful software, thanks everyone who was involved in that. Unfortunately way late in the life of my phone I was homeless and got robbed for it. I got a used HTC HD7 Windows Phone for free from a friend. It was great for movies and music with a great screen and touch sensor but it was very early in the life of the new Windows Phone and there wasn't a lot of quality software being developed. That, and it just wasn't Android, and I longed for freedom. The integrated Web browser IE 9 variant sucked, and T-mobile denied me the final Windows Phone 7 update. The phone has gotten less and less useful as time went by though it always sucked for web browsing. This fall I got a One Plus One, it made a wonderful Wifi phablet, but when I tried to use it as a phone I found the radio was severely deficient in range, possibly due to defective manufacture as it got better range in colder weather. I had to initiate a chargeback with my credit card company to get support to talk to me and then ultimately get a refund. That's how I got where I am now and this is the first time I've needed to register for an account here. Thanks again xdadevelopers.
What is the best way to proceed? Semi detailed logical instructions please, as while I am intelligent and not a noob, I have been out of the game since CM7
Code:
.. ("`-''-/").___..--''"`-._
.. `6_ 6 ) `-. ( ).`-.__.`)
.. (_Y_.)' ._ ) `._ `. ``-..-'
.. _..`--'_..-_/ /--'_.' ,'
.. (il),-'' (li),' ((!.-'
Holy wall of text. This seems to be the crux:
Aslan_ said:
I have installed TWRP Manager by Jmz software from Google Play. The standard reboot method doesn't work I changed the settings to "Reboot using an alternate method". I attempted to the TWRP recovery with the "Install TWRP". One must select their device and the closest thing to mine was "Motorola Photon 4G" codename "sunfire". This didn't appear to be it exactly but there wasn't a better choice. The next line down says "custom recovery not installed or detected". Then I selected the recovery version to install "2.6.3.0" "openrecovery-twrp-2.6.3.0-sunfire.img appeared the most recent, then I attempted to "Install Recovery" The phone downloaded the image, and said "Ensure the partition listed below is the correct one for your device..." "/dev/block/mmcblk0p10" how do I know if that's correct or not? I said yes to the question and went ahead, the phone rebooted to an Android on it's side with a yellow triangular sign with an exclamation point above it. Thirty seconds later the phone rebooted normally and everything worked no custom recovery was flashed.
Click to expand...
Click to collapse
Why would you flash something that is OBVIOUSLY not for your device!? I sincerely hope it did nothing because you could do some permanent damage to your device by flashing stuff that's not made for it.
Did you bother looking for any recovery threads? Say my TWRP thread?
I recommend 2.7.1.2 in that thread, which is fine for CM11. If you want CM12, grab 2.8.5.0 in that thread.
Flash it per my directions using fastboot in my TWRP thread.
Got it thanks, now which rom?
Thank you very much arrrghhh. First off I sucessfully flashed TWRP 2.7.1.2. I did see the "[recovery] TWRP 2.7.1.2" thread, but it was from 2012 and it's 2015 now, plus it was 25 pages. Now I do see that the initial post was last edited 23rd July 2014, so that's better, but that's still over six months ago, so I'd have asked the question anyway having seen that. Several things to note, GooManager has been retired since the new cdn for goo.im was implemented, so that should be removed from the post. I like apps, they make me feel like there's less risk in my actions, though after some poking around I see it's probably the opposite. People are doing so much more low level stuff in apps compared to CM7 it's amazing.
arrrghhh said:
I recommend 2.7.1.2 in that thread, which is fine for CM11. If you want CM12, grab 2.8.5.0 in that thread.
Click to expand...
Click to collapse
It would be nice to see that info in the 2.7.1.2 thread. that the newer version is recommended for CM12 and where to get it, that would show you're on top of the latest changes not to mention make the thread even more useful. Perhaps include the reason for stopping at 2.7.1.2, the SELinux split. Seeing a new version that works always makes me want to get the newer version, but in this case there's a good reason not too.
I'm always hated vague it's broken posts that don't adequately describe the problem, the hardware used and the environment, so I head in the opposite direction with mine.
Next question is which rom should I choose? I want something stable and secure with everything or just about everything working. I like Cyanogen Mod, but I'm open to other things. As new as I can get, but stable. I thought I needed something from download bod cyanogenmod bot org /?device=xt897c , but now looking around it looks like I might be able to use other sources like download bot cyanogenmod bot org /?device=xt897 I'm not sure though. Again I have the Motorola Photon Q 4G LTE which is CDMA, from FreedomPop running on the Sprint Network.
Code:
.. ("`-''-/").___..--''"`-._
.. `6_ 6 ) `-. ( ).`-.__.`)
.. (_Y_.)' ._ ) `._ `. ``-..-'
.. _..`--'_..-_/ /--'_.' ,'
.. (il),-'' (li),' ((!.-'
Aslan_ said:
Thank you very much arrrghhh. First off I sucessfully flashed TWRP 2.7.1.2. I did see the "[recovery] TWRP 2.7.1.2" thread, but it was from 2012 and it's 2015 now, plus it was 25 pages. Now I do see that the initial post was last edited 23rd July 2014, so that's better, but that's still over six months ago, so I'd have asked the question anyway having seen that. Several things to note, GooManager has been retired since the new cdn for goo.im was implemented, so that should be removed from the post.
Click to expand...
Click to collapse
I no longer use this as my primary device, so my threads are basically stagnant. fastboot always works, where apps come and go... I'll try to find some time to adjust the post.
Aslan_ said:
It would be nice to see that info in the 2.7.1.2 thread. that the newer version is recommended for CM12 and where to get it, that would show you're on top of the latest changes not to mention make the thread even more useful. Perhaps include the reason for stopping at 2.7.1.2, the SELinux split. Seeing a new version that works always makes me want to get the newer version, but in this case there's a good reason not too.
Click to expand...
Click to collapse
Reason for stopping at 2.7.1.2 was they implemented MTP in 2.8.x, and I could never get it working right for both Win & Lin. I spose my bar was too high and I should've just released it, but I hate releasing half working stuff. It was a new feature that didn't work right.
Again, this is no longer my primary device so I'm not working on it very much at all. I have to pry the thing from my roommate's hands to even play with it, I haven't flashed CM12 yet (because it's no longer my device really).
I'd like to update the official TWRP, but in the meantime the CM maintainer has taken care of updating it so F2FS can be utilized.
Aslan_ said:
Next question is which rom should I choose? I want something stable and secure with everything or just about everything working. I like Cyanogen Mod, but I'm open to other things. As new as I can get, but stable. I thought I needed something from download bod cyanogenmod bot org /?device=xt897c , but now looking around it looks like I might be able to use other sources like download bot cyanogenmod bot org /?device=xt897 I'm not sure though. Again I have the Motorola Photon Q 4G LTE which is CDMA, from FreedomPop running on the Sprint Network.
Click to expand...
Click to collapse
Well obviously some of that does go down to choice - if you want CM, it is a little confusing. The device started out in CM10 as its own device, xt897 for GSM xt897c for CDMA. Then in CM11 they merged the devices into moto_msm8960. Of course they had to split again when the new bootloaders were released for the other moto_msm8960's (Razr HD, Atrix HD, etc) and moto_msm8960_jbbl was kind of a stopgap device at the end of CM11. Again, reading is your friend here although I realize all of that history is hard to glean. At least read the OP of the CM thread:
kabaldan said:
Please note:
In CM12, the Motorola 2012 msm8960 device line has been de-unified again, so moto_msm8960/moto_msm8960_jbbl builds are dead from now on.
Please check the xt897 device link for new Photon Q builds.
Click to expand...
Click to collapse
Good luck. The device is now semi-unified (GSM & CDMA), as xt897.
Aslan_ said:
[*]I have created a TWRP Backup using Online Nandroid without modifying the recovery
Click to expand...
Click to collapse
Would you mind terribly to share this? My device shipped with a Sprint branded ROM and I'd like a proper backup.
I flashed CM 12.1 and lost data (3g/LTE) connection
I tried to flash FreedomPOP APN fix but it did not help
Anyone knows how to fix this?
How do I update PRL/Profile on CM 12.1?
turbozapekanka said:
I flashed CM 12.1 and lost data (3g/LTE) connection
I tried to flash FreedomPOP APN fix but it did not help
Anyone knows how to fix this?
How do I update PRL/Profile on CM 12.1?
Click to expand...
Click to collapse
You don't update PRL/Profile in CM, you do that on the stock ROM. Make sure EVERYTHING works on stock before flashing CM.
I found another APN fix and it worked.
So the result of the update PRL/Profile is stored somewhere in the phone and does not get lost when I flash a new ROM, is that correct?
The only way to update PRL/Profile is to flash back to stock, do update, reflash back to custom, right?
turbozapekanka said:
I found another APN fix and it worked.
So the result of the update PRL/Profile is stored somewhere in the phone and does not get lost when I flash a new ROM, is that correct?
The only way to update PRL/Profile is to flash back to stock, do update, reflash back to custom, right?
Click to expand...
Click to collapse
Correct.
turbozapekanka said:
I found another APN fix and it worked.
So the result of the update PRL/Profile is stored somewhere in the phone and does not get lost when I flash a new ROM, is that correct?
The only way to update PRL/Profile is to flash back to stock, do update, reflash back to custom, right?
Click to expand...
Click to collapse
Can you share this "another APN fix"?
already shared here http://forum.xda-developers.com/showpost.php?p=60153295&postcount=18
Anyone still have issues? I was running a June Nightly and it was working somewhat. It would randomly lose connection and I would have to flash the APN.zip. It happened again a few days ago and I decided to go up to 722 Nightly and now I haven't been able to connect. When I go to APNs the list is empty and even if I manually add one it does not seem to stick. The APN zip doesn't help either. The phone is connected but shows an exclamation mark next to the signal and I have no data.
Sort of solved my own problem
Flashed back to stock Spring using RSD lite and a modified XML that didn't flash the system.img since it kept giving me errors. Found a stock TWRP dump on the forums and flashed that. Updated PRL and Profile, reflahsed back to CM11 Snapshot and flashed the 2015 FreedomPOP APN fix. Working for 1 day now.

Categories

Resources