Database Info

Really messed up G2X

Well I ordered a G2X the other day and finally I received it. It came with Gingerbread 2.3.3 from the factory. (worked flawlessly) Keep reading.
After a couple days I wanted to try out CM7 on it. So, I rooted the phone by using NVflash and doing all that good stuff, then I flashed the phone with (Gingerbread OTA 2.3.3 Rooted flashable zip v1.0.0) I couldn't get root with SuperOneClick so that was my only option. Well I got root and that's when the fun started.
I installed CM7 on it, seemed to run fine, looked fine. But simple me, I wanted to go back to Plane jane 2.3.3 So, I did all the usual stuff (backing up, wiping data, formatting caches), then I ran OneClickRecoveryFlasher...and restored the phone with LG-P999-V10f.zip (supposedly a stock flash for 2.2.2)
well it all seemed to work fine apon finishing. It booted fine, ran ok. However now I have some really bad problems. The major one is that my wifi doesn't work worth a damn now, the connection is highly intermittent. I can't use the market to download apps because it dies out often, along with anything else network related. (browsing works 5% of the time) You catch my drift. My other android phones have no trouble with anything. Now here where it gets weird, I supposedly restored my phone back to stock. However, the phone reports a proper android version 2.2.2 which is what I flashed it to. However it shows kernel 2.6.32.9 Baseband is July 15th 2011. When I use LG's phone update tool it says I am running V21E which is Gingerbread 2.3.3 ...but that's not true because it is actually 2.2.2
I have no clue what to do, I am stuck. I just want to either have a stock G2X running either 2.2.2 or 2.3.3

beast6228 said:
Well I ordered a G2X the other day and finally I received it. It came with Gingerbread 2.3.3 from the factory. (worked flawlessly) Keep reading.
After a couple days I wanted to try out CM7 on it. So, I rooted the phone by using NVflash and doing all that good stuff, then I flashed the phone with (Gingerbread OTA 2.3.3 Rooted flashable zip v1.0.0) I couldn't get root with SuperOneClick so that was my only option. Well I got root and that's when the fun started.
I installed CM7 on it, seemed to run fine, looked fine. But simple me, I wanted to go back to Plane jane 2.3.3 So, I did all the usual stuff (backing up, wiping data, formatting caches), then I ran OneClickRecoveryFlasher...and restored the phone with LG-P999-V10f.zip (supposedly a stock flash for 2.2.2)
well it all seemed to work fine apon finishing. It booted fine, ran ok. However now I have some really bad problems. The major one is that my wifi doesn't work worth a damn now, the connection is highly intermittent. I can't use the market to download apps because it dies out often, along with anything else network related. (browsing works 5% of the time) You catch my drift. My other android phones have no trouble with anything. Now here where it gets weird, I supposedly restored my phone back to stock. However, the phone reports a proper android version 2.2.2 which is what I flashed it to. However it shows kernel 2.6.32.9 Baseband is July 15th 2011. When I use LG's phone update tool it says I am running V21E which is Gingerbread 2.3.3 ...but that's not true because it is actually 2.2.2
I have no clue what to do, I am stuck. I just want to either have a stock G2X running either 2.2.2 or 2.3.3
Click to expand...
Click to collapse
You are probably going to have use Xboarders ROM then flash the unroot.zip he has in this thread http://forum.xda-developers.com/showthread.php?t=1158513.
See if that works to get you back to 2.3.3 completely stock.

It says that because it checks the baseband to see how recent it was, that's why it thinks you're on v21e.
As of now, there's no way to flash back to the old baseband, since people don't include the baseband in their ROMs, as that can cause a whole host of problems. The solution is to do exactly what tidewaterns said, that just gives you a little extra background info.

I am going to give this a try and see what happens, I will post results.

Well I tried the slimmed down version of Xboarders's rom and it seems to be working well so far. I originally installed his Stock OTA rom and that's when I started having problems. Oh well. thanks guys for all the help.

Crash course about root and roms: Superoneclick roots the rom you have in place. Flashing xboarders rom didn't "give you root" for the other roms you flashed, it is simply one rom out of many that is pre-rooted by the dev who packaged it up. When you flash it you have a rom that is rooted. If you had flashed CM7 (another rom that provides root access to its system files) then you'd have had a different rom that was pre-rooted by its dev.
Are you catching what I'm saying? Flashing xboarders rom didn't "give you root" any more than CM7 "gave you root." Root is built in to those roms.
If you want to restore to an unrooted stock rom browse the threads in the development section. There are a couple of stock nandroid backups posted that you can restore via clockworkmod recovery and then you'll have a stock unrooted rom. You can even do that and still have clockworkmod recovery in case you want to flash a different rom to your phone again.
And PLEASE remember when flashing from one rom to a different rom, WIPE WIPE WIPE data, cache, dalvik cache, then flash rom, then fix permissions, then reboot. This will save you SO MANY headaches.
G2X CM7

I learned something new Thanks for the info. And yes, this last time when I installed, I wiped and formatted just about everything I could possibly do, including fix permissions..seemed to do the trick.

beast6228 said:
I learned something new Thanks for the info. And yes, this last time when I installed, I wiped and formatted just about everything I could possibly do, including fix permissions..seemed to do the trick.
Click to expand...
Click to collapse
Sweet! If you're simply updating to a newer version of the same rom you can probably get away with just wiping cache and dalvik cache and then flashing. Its just when you switch to a totally different rom that you need to do a full wipe. Gives you a clean slate to start with.
G2X CM7

I'm curious about one thing though. What would I accomplish by using Nandroid and flashing a bin? I see there is a BIN_LGP999AT-01-V10f-310-260-MAR-27-2011+0.zip file that is available for this phone, although I have no clue on how to install Nandroid. Anyways, wouldn't flashing a BIN be the ultimate way to restore the G2X?

[Q] Here's a head scratcher! CM10 CWM problem?

I was happily running along with my GT2 10.1 5113 using CM10, updating nightlies, all is well. Then I put the CM 10.1 unofficial, that went well, was using it and put the 12/09 version on, that went well also. However I decided I didn't like it and wanted to go back to CM10. I had a back up that I made in CWM with the 12/08 nightly and had begun restoring it when an error came up stopping the restore, only said file error restore can't continue. OK, that kinda blows chunks cause I know my rom just got hammered. Tried to restart, boot loop. Got back into recovery re flashed the CM 10.1, trying to save my data, bootloop. Got back in recovery and wiped data re flashed, bootloop. On an act of desparation I flashed the 12/08 nightly and, viola she lit up and booted to the setup screen.
Set it all back up and updated to the next nightly, 12/10 and I'll be danged, bootloop. Went back to recovery re-flashed the 12/08 nightly and all went well. No data loss just worked fine.
Bottom line I can't get anything but the 12/08 nightly to boot up. I even flashed stock with Odin, that bootlooped too! So I'm stumped.
It boots into the 12/08 nightly just fine and that's it.
I know this is wordy, but I wanted to make a thorough explanation. I feel this is related to the CWM error, but I have no idea where to go from here.
Anybody got a suggestion? All help is greatly appreciated.

I think cm10 installs jelly bean on your system. and switching back to an older version will cause the bootloop. that's what i believed happened to me when I installed cm10 by mistake instead of cm9 which is what i wanted. it took me several tries with odin and the stock rom to be able to go back.
I think the key is when you have cm10 installed then you need to enable the "usb debugging" in the developers section. that is probably what is stopping you from switching back to an earlier version or a new version or the stock rom using odin.
anyway that's how I was able to switch back to stock.

I think the reason you can´t restore CM10 is the fact that Android 4.2 introduces muti-users management. Thus, the system do not store in /sdcard/ any longer, but in /sdcard/0/ (for the first user). Since you still have a 4.1 recovery version, it doesn´t find the backups files any more. A solution is to move your sdcard data from /sdcard/0/ to /sdcard/ before restoring your backup.
As for CM10, the 12/09 and 12/10 nightlies don´t boot, due to kernel changes. These changes were reverted in 12/11, so this one should boot.

Einril said:
As for CM10, the 12/09 and 12/10 nightlies don´t boot, due to kernel changes. These changes were reverted in 12/11, so this one should boot.
Click to expand...
Click to collapse
Bingo! That worked, 12/11 worked. I had no idea that was happening. I made all the file changes actually because I wound up with sdcard/0/0/0 from all the flashing back and forth, that was funny. All is normal now thanks!
Sent from my GT-P5110 using xda premium

[Q] restoring from backup works but system apps crash after

Greetings to All the wonderful hardworking people here!
Grab a coffee I'm going to try to be as thourogh as possible.
To start with I own and am writing this post on a SCH-I535 that is rooted, unlocked and running cm10.0.
Two weeks ago I flashed cm10 to my phone. The first time I flashed from ROM manager and it didn't take; went to rolling boot. So I restored my backup and the phone worked perfectly as it should. <-- key point there. So I waited a few days and decided to try again after doing more research and successfully flashed cm10 to my phone. I have been very happy with it as a daily driver for the last two weeks. MMS doesn't work but I can live without it. After initial flashing Skype worked flawlessly. As of yesterday 2-11-13 I can hear people but all they can hear from me is the sound of a wind tunnel. I have tried re installing Skype... re flashing the ROM to no avail. I have searched for a fix and have been unsuccessful.
So now I want to return to stock and wait till cm10.1 stable is out. I restored from my backup thinking it would be smooth like last time but I was wrong. 1st attempt android KB won't load. 2nd attempt the desktop app wouldn't load and third attempt it just kept failing on everything it seemed like. Finally I re flashed my cm backup I had and am rolling for now. What do I need to do to get my stock backup working?
If u need any additional info I'll be more than happy to get it for u.

Figured it out,,,
I solved it myself. when directly searching for a similar problem to mine i found nothing. I was watching some flashing videos and seen that some users would format /data /cache /system. I did this, restored my stock backup and everything is working fine now.

[Q] Stops Booting at Splash Screen in AOSP ROMs

I've been using CM10.1 on this phone pretty much since it's been available and updating nightlies about once a week usually. Typically I use Ktoonsez kernel and also update this regularly. Also I am on the MF1 firmware. So, I'm pretty comfortable with the update process and have done it many times.
The other day I attempted to update to CM10.1 7/8 nightly while also installing a kernel I've never tried before called 'Sultan-kernel-Venturi-r5-USA'. Also completing the update process I rebooted and the phone would not move past the CM loading animation splash screen. After about 10 minutes of this I pulled the battery and rebooted, hoping it was just a hiccup but the same thing happened. After dirty installing various CM10.1 nightly and release versions with various combos of no custom kernel and the KT kernel but nothing would fix the boot issue.
I then attempted to wipe and ended up eventually wiping everything on the phone except the external SD card. Still, I could not get the phone to move past the CM splash screen. I then tried a few other AOSP ROMs with the same issue presenting.
Eventually I installed a TW based ROM and was able to get the phone to boot and and able to at least use my phone now. I've tried a couple time since to do a nandroid backup then try installing CM10.1 again and still nothing changes. I can restore the backup and the TW ROM works fine again.
Any ideas on what could have happened to cause this or anything else I can try to get AOSP ROMs working on my phone again?

I would say Odin back to 4.0.4 stock, do the OTA's, reroot with the one click root in the developer section, and it should work.
Sent from my SCH-I535 using xda app-developers app

I did get this figured out. Somehow my EFS partition was wiped. TW based ROMs would actually boot but displayed a 'Factory Mode' warning on startup. AOSP ROMs would not finish booting at all. After restoring EFS from backup everything started working again.

[CM14] Cell Signal can't connect, turns off immediatly after trying to reconnect

This is consistent across every CM14 ROM I've flashed. I am upgrading from CM13.
The signal bar at the top is blank as in "no service", it attempts to reconnect and show a signal for a split second but then goes back to "no service" again. When I remove my SIM card and reboot the problem simply vanishes, but of course I can't get LTE
Firmware: PCA
Recovery: TWRP 3.0.1.0
I have tried running the ROM stock with no data restore and I have tried flashing APN settings from this post.
I at first thought it was a CM14 bug but then I read that others had no problems with CM14 ROMs.

Assuming you actually have a SM-G900P (since a lot of people ignore that little detail) it's probably a matter of Cm14/14.1 doesn't appear to be wholly happy with anything other than the latest baseband, which is now PK1. To get it, just reflash to stock with Odin and then poke at the thing until it gets the two OTA updates that will bring you up to PK1. At that point if you like you can poke at the controls to update the PRL and Profile (just to be sure everything's good) and then let me suggest you make a call or two and/or send some SMSes to be sure you didn't mess something up when you tried to change the APN settings one almost never needs to touch, and then flash TWRP (or whatever recovery you use) right back in and sideload the Cm14.1 nightly and open-gapps for 7.1. Also, you will need to do a factory reset after upgrading to 14.1 or you'll get a wholly different set of misbehaviours out of the phone (trust me... I deliberately cut corners through multiple rounds of reflashing to find out what symptoms to look for). One of the more endearing failures can be no soft keyboard, nobody wants that.
I had a bunch of weirdness happening (including completely non-functional GPS) with CM14 a few days ago, and since the changelog doesn't seem to show anything addressing the screwy problems I had, it hints very strongly that people will need to update to PK1 before they can expect the device be reliable.
OH... and don't try and enable Adoptive Storage if it asks. The performance is abysmal for some reason (around 2Mb/s on a Class-10 card that otherwise hums along at 14Mb/s) and it will make any apps that are trying to use storage run like crap.

So people have it working on PK1? Has anyone had it working on PCA?
Edit: Odin restored PK1, it didnt want to boot after the reflash. I installed TWRP and restored a PCA Backup, updated PRL and profile. I flashed a cm14.1 ROM and still had the same issues.
It also didn't wipe my internal storage when I ran odin, which I remember it doing in the past.

Worked great on my S5 900P

Gracefully I got it to work on Resurrection Remix. Idk if it was the APNs or just more stable ROMs.
I booted RR stock w/o gapps, I went to enter in the APN settings using this site and it just magically worked after I entered in only the first line. It's hard to tell if it was because the ROM found out how to connect or if the first line of the APN settings triggered something.