Database Info

Having issue after gaining root...

Hello all,
Just stumbled into the world of rooted G1 and its glory today on my sick day. Just performed the update and everything went smoothly (thanks for the detailed instructions everyone). Now I am attempting to add some themes and the 1.41 but, when I attempt to apply the update from my card (via alt s) it comes up with "Can't open /sdcard/update.zip (no such file or directory), then the install is aborted. Any help would be much appreciated.
Thanks,
Jim

One thing I can come up with is having your phone connected to the PC. Make sure you unplug all the cables first.
If that's not the case, I'll let people smarter than me have their say

impactsto said:
Hello all,
Just stumbled into the world of rooted G1 and its glory today on my sick day. Just performed the update and everything went smoothly (thanks for the detailed instructions everyone). Now I am attempting to add some themes and the 1.41 but, when I attempt to apply the update from my card (via alt s) it comes up with "Can't open /sdcard/update.zip (no such file or directory), then the install is aborted. Any help would be much appreciated.
Thanks,
Jim
Click to expand...
Click to collapse
Make sure you name it to update (if you are hiding file extensions in windows). Don't rename it to update.zip or else it'll show up as update.zip.zip to the phone when you are trying to flash it.

Thanks for the assist guys! I tried the above but the results are the same. Its odd because the rooting process went without a hitch. Now I can't get themes or 1.41. Very odd. Any other suggestions?

Can you access your card via phone though? It might be that when you had your phone hooked to the PC, you did not unmount ("eject" in Windows) it properly and therefore linux (Android) can't mount it.

You got it! After I tried plugging it back in to check it, Windows went through the whole "install" process. After that I ejected it and the update on the card went through no problem. Thank you much for the help!

Glad to help! I constantly have similar problem on my PC when my wife just unplugs USB flash from her Windows machine. I then have to go through the process of manual mount every time.

So after enjoying my rotted phone for a bit I decided I would switch the theme. Applied on the sd and all went seemingly well. Until the "Tmobile G1" screen came...and never went away. I tried to reinstall the theme, did a wipe, removed the battery multiple times but it doesn't go away. Now I do believe I bricked my phone. Where do I go from here?

Also, I meant rooted not "rotted". Although that might be what I have now lol.

impactsto said:
Also, I meant rooted not "rotted". Although that might be what I have now lol.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=442480
Follow the very first instructions, the part that involves DREAMIMG.nbh. This will reset your phone back to RC29, so you can update to JF 1.41 again after. Be VERY careful, and make sure you copy the DREAMIMG.nbh file over properly, and make sure it's named correctly, etc. Flashing NBH's is pretty risky.
Also, I VERY strongly suggest you stay away from themes until you know more about the phone. If you use a theme that doesn't support 1.41, stuff like this happens and you'll brick. Stick to default until you're more comfortable.

once you have JF 1.41 installed and working, I would suggest making a backup, you can do this from the same screen you select Alt S for updates.
Then install your theme of choice, if it fails you don't have to start completely over.
Buuf theme is working great with 1.41

Thanks again for the assist! I shall try it when I get home from work. So to be perfectly clear I re-flash DREAMIMG.nbh. Then once completed I do the normal update.zip procedure with 1.41. I want to make sure, I don't think I can maneuver a new AV system AND phone with the wifey.

impactsto said:
Thanks again for the assist! I shall try it when I get home from work. So to be perfectly clear I re-flash DREAMIMG.nbh. Then once completed I do the normal update.zip procedure with 1.41. I want to make sure, I don't think I can maneuver a new AV system AND phone with the wifey.
Click to expand...
Click to collapse
correct me if i'm wrong .. but flashing the DREAMIMG.nbh you will have to go thru the root process again .. yes?

LucidREM said:
correct me if i'm wrong .. but flashing the DREAMIMG.nbh you will have to go thru the root process again .. yes?
Click to expand...
Click to collapse
You might have to, I've never flashed an NBH myself so I can't say for sure.

Yup turns out I had to. Once the NBH was flashed the phone booted up. After the wait to the "Android" screen I breathed a sigh of relief. All in I'm back to where I was when I first rooted and so far so good! Thanks again to all for the help.
Jim

[Q] T-Mobile G2X - Recovery From Attempting Flash/ROM install via CWM

Hello:
I'm having a frustrating experience attempting my first root of my G2X.
I've had a previous thread from yesterday, attempting to do things from the Mac side:
http://forum.xda-developers.com/showthread.php?t=1172487&highlight=velanche
As of now, I've decided to revert to Windows 7 on my Mac to try and rectify things. I'm able to use One-Click Recovery Flasher, following the instructions, to flash the phone. I then downloaded an earlier nightly version of CM7, installed it on my flash drive, and did the install via ClockworkMod.
I had no errors from CWM, from the wipe to the install. I then choose the reboot open, and it powers off my phone.
Upon attempting to turn on my phone, I would get the LG screen, followed by a quick flash, followed by another LG screen with some horizontal blue background behind it. I'm taking it that it means that it's stuck, because I've waited 10 minutes before having to do a battery pull.
I did at one time attempted to flash back to the stock T-Mobile, but when the LG screen came it, it would just remain there without any progress.
At this stage, I don't know where else to go. I'm not sure if there's something amiss, because my phone, as far as I know, as been erased. If there's a way to progress to CM7, I'm game. But one thing I really need to do is to get my phone back.
I didn't backup my phone's contents initially because I was going to recreate everything anyway. Now I'm in a not-so-good place, save having to get a phone exchange.
Any assistance would be appreciated; thanks so much.
V.

Download one of the "Stock Rooted Nandroid Backups" from the development section, stick it on your SD card and do a Nandroid restore from CWM. That should get your phone working again...
On the CM7 installation problem, I have no idea what that could be. I've been flashing ROMs on Android devices since the G1 first came out a few years ago and the only reasons I had bootloops were from me trying to flash without wiping or flashing an unstable build.
Sorry to digress for a second here, but you DO have the T-Mobile branded G2x and NOT the Optimus2x, right?

Working on It
Hey thanks for the help.
I have a T-Mobile G2X, so I should have done everything the way I expected. Then again, things should have worked if I did.
So I installed the Nandroid recovery for my phone, and attempted recovery via CWM, but ended up with a MD5 mismatch error (whatever that means).
I even went so far as move select files from my SD card. I formatted it, then put in those select files i wanted to keep.
I tried again, and no change.
Any suggestions on how I should proceed? Thanks!
V.

I get the same kind of "just not going to happen" errors when I try to install EaglesBlood. I've found no solution, though CM7 works just fine. I don't know what to tell you, really...
Sent from my Nexus 5g using XDA Ultimate App

velanche said:
Hey thanks for the help.
I have a T-Mobile G2X, so I should have done everything the way I expected. Then again, things should have worked if I did.
So I installed the Nandroid recovery for my phone, and attempted recovery via CWM, but ended up with a MD5 mismatch error (whatever that means).
I even went so far as move select files from my SD card. I formatted it, then put in those select files i wanted to keep.
I tried again, and no change.
Any suggestions on how I should proceed? Thanks!
V.
Click to expand...
Click to collapse
The md5 mismatch will happen if you try to copy and past the files. Try it again but this time unzip it directly to the fold where it should be. Do not copy and past the unzipped folder. This is also someones backup so you must go through the restore option in cm
Sent from my LG-P999 using XDA Premium App

LordButtersI said:
I get the same kind of "just not going to happen" errors when I try to install EaglesBlood. I've found no solution, though CM7 works just fine. I don't know what to tell you, really...
I don't know if this might have anything to do with why I've had problems getting CM7 to work, but I've noticed that when I plug the phone either into Windows or OS X, I've somehow lost the internal drive. I know that it's there because I've found a whole bunch of files on it while in CWN, but I'm suspecting that there's some link between neither computer seeing the internal drive and the issue with getting the phone to boot.
Yes, I can mount the external drive, either from CWM's mount on both platforms or when I press both volumes on my phone and plug in to Windows 7 via USB.
Do you have any insight on this? I was watching a few of The Unlockr vids, and I noticed that even though the guy's phone was rooted and flashed, he still could boot into his phone until he was ready to put on the new ROM (CM7, in this case).
Thanks!
Click to expand...
Click to collapse

scooter247 said:
The md5 mismatch will happen if you try to copy and past the files. Try it again but this time unzip it directly to the fold where it should be. Do not copy and past the unzipped folder. This is also someones backup so you must go through the restore option in cm
I tried on the OS X side to do this, having to download an RAR app. I found the LG file, and told the app to extract it to the backup directory on my phone. I tried the restore again in CWM, but still a mismatch.
I will try it in Windows 7 tomorrow, and will let you know the outcome.
I'm beat; spent the whole weekend on this phone modding biz. I suspect I'll be really good by the time I finally am able to get things working.
V.
Click to expand...
Click to collapse

Is this an old SD card? Perhaps some bad sectors on it? Without holding the phone in my hands I can't think of anything else. Other than double check your steps, re-copy the files and try, try again.

The SD card is not old; about 2 months old. I tried formatting the card via Windows 7, but did it in FAT32. I take it that it's supposed to be formatted differently? The card is 16GB, but when I looked into CWM it's limit is 4GB.
I tried the steps again, and still get the same md5 mismatch. Is my guess correct that the card is supposed to be formatted a certain way? Unfortunately, I can access the previous OS via my phone, nor will the internal memory appear when the phone is plugged into the computer. However, I am able to mount the SD card within the computer's OS.
I almost feel like walking away from it for a week, but that means I'll be stuck without phone access for awhile. Tips or suggestions are most welcome.
BTW, there's apparently alternate instructions to deal with the md5 mismatch error. Though in Windows the NDIVIA driver is loaded for the phone, I tried the adb shell command but my device isn't detected by the software.
Thanks again,
V.

T-Mobile still sending out the GB OTA?

I could've swore I read they stopped it? If so then is there anyway to flash the phone and be able to get the baseband? My co-worker's phone keeps rebooting, etc. I don't want to use the LG Update Tool. I bricked my phone and finally got it unbricked after 5 hours.

you are right T-Mobile already stopped rolling out the OTA.
Your only opportunity to get the new baseband is the LG tool
flexnix said:
I could've swore I read they stopped it? If so then is there anyway to flash the phone and be able to get the baseband? My co-worker's phone keeps rebooting, etc. I don't want to use the LG Update Tool. I bricked my phone and finally got it unbricked after 5 hours.
Click to expand...
Click to collapse
Sent From My WeaponG2x

I used the LG tool about an hour after the update was relesed and it went perfectly smooth. What I did was a factory reset before I did it and I dont know if that mattered but I had no problems. I would do it you really have no choice. I thought I read somewhere that someone is working on a version that you can install from SD but I might be wrong and I dont think you will get the new baseband which in my opinion is one of the best things about the update. It is the only part you cant just flash. If you root you can install any ROM like the leaked one or whatever. So I would use the LG updater. The other thing is I have the LG updater on my computer and it starts automatically and it says that their servers are undergoing maintenance so you cant use that either. I hope this helps you
Charlie

flexnix said:
I could've swore I read they stopped it? If so then is there anyway to flash the phone and be able to get the baseband? My co-worker's phone keeps rebooting, etc. I don't want to use the LG Update Tool. I bricked my phone and finally got it unbricked after 5 hours.
Click to expand...
Click to collapse
There are precautions you can take to prevent a bad experience. Most of them are listed on the Forum somewhere. But to recap,
Stock ROM: Install a stock rom. Root does not impact the update, so being rooted is not an issue. Find the Stock Rom and load it.
Standard recovery: Flash the standard recovery. If you are happy with your current rom, do a nand backup first. Then flash the stock ROM.
Factory reset: Throw this in because it can't hurt.
Many of the people that had problems with the LG updater simply did not meet the above steps.
While doing the update, remember, turn off AV, turn off pop up blockers. Turn off FAX programs or any other monitoring program, even screen savers. Do NOT make assumptions. There are several places in the update where the progress appears to stop. Do NOT disconnect. If you have been stopped for a hour, something is wrong. But a few minutes is not out of line. Personally I stopped at 4% for about 5 minutes...then it continued.
Here's the thread to return your device to stock....its pretty good. I can walk through these steps in less than 5 minutes....its really simple. Set your friend up with this.....
http://forum.xda-developers.com/showthread.php?t=1088728
In case you're wondering, the thread above will NOT restore to pure factory like condition. It will NOT restore the original baseband. But all the rest works....its easy to use, simple to follow.....and more than anything else, does not require you to think....only follow. The worst problem people have when doing this is thinking, and assuming. Just follow the steps as is, no ad lib.
Good luck.

I've used the LG Updater on 3 phones, and I haven't had any problems.

I followed this page of instructions from the LG website and had no issues. http://wwwstg.lg.com/us/mobile-phones/G2X-Driver/index.jsp
I used my netbook running Windows 7 Starter Edition.

I just tried updating on the lg website and it says servers down for maintence
Sent from my G2X

kwiggington said:
I just tried updating on the lg website and it says servers down for maintence
Sent from my G2X
Click to expand...
Click to collapse
That is only the first time it runs after you install it. Click start and go to "LGMobile Support Tool" and run the "LGMobile Update" program. It should run this time without the bogus server down message. If you look at the dates in that notice, the maintenance was back in July. Be sure to right click the program and run as administrator if you are running Windows 7. Make sure you install the drivers from within the updater also, as the other driver pack on their website doesn't seem to install all the drivers you need to complete the update. Good luck.

jboxer said:
That is only the first time it runs after you install it. Click start and go to "LGMobile Support Tool" and run the "LGMobile Update" program. It should run this time without the bogus server down message. If you look at the dates in that notice, the maintenance was back in July. Be sure to right click the program and run as administrator if you are running Windows 7. Make sure you install the drivers from within the updater also, as the other driver pack on their website doesn't seem to install all the drivers you need to complete the update. Good luck.
Click to expand...
Click to collapse
I didn't have to run as administrator and I used Windows 7. Following the instructions in the link I posted above I had no issues at all. Drivers were installed separately from the updater, again just following the instructions from that link.
Follow LG's instructions word for word, in order, from start to finish, without skipping any steps, and you shouldn't have any issues.

phburks said:
I didn't have to run as administrator and I used Windows 7. Following the instructions in the link I posted above I had no issues at all. Drivers were installed separately from the updater, again just following the instructions from that link.
Follow LG's instructions word for word, in order, from start to finish, without skipping any steps, and you shouldn't have any issues.
Click to expand...
Click to collapse
Thanks ill try it when i get home
Sent from my G2X

Is anybody working on getting the baseband as a zip that can be flashed, that would be great instead of going through the whole updater tool thing.
Sent from my LG-P999 using XDA App

Updated works awsome now
Sent from my G2X

phburks said:
I didn't have to run as administrator and I used Windows 7.
Click to expand...
Click to collapse
When you ran the program did Windows have a warning box that said this program wants to make changes to your computer, and you had to say yes or no to allow it to continue. That means the program installer set it to admin mode already and Windows confirms you want to run the app as an admin. Without admin mode in Windows 7, programs that flash roms and such simply don't work properly. Looks like LG mitigated a problem by setting the flag during the program install.

jboxer said:
When you ran the program did Windows have a warning box that said this program wants to make changes to your computer, and you had to say yes or no to allow it to continue. That means the program installer set it to admin mode already and Windows confirms you want to run the app as an admin. Without admin mode in Windows 7, programs that flash roms and such simply don't work properly. Looks like LG mitigated a problem by setting the flag during the program install.
Click to expand...
Click to collapse
Yea it asks for that confirmation. The one I used is version 1.5.2.2

Bricked Wind Mobile G2x - Need help understanding why

Hi, I apologize up front for the long winded post, but I want to relay as much info as possible in the hope that someone can point out my mistake(s).
This is the 2nd android phone I have managed to brick in the past couple years.. The first was an old dream and I flashed the wrong update file for a different phone by accident, but at least I knew what I did wrong that time.
Fast forward to yesterday. I picked up a brand new LG Optimus 2X (LG-P999 = G2X) From Wind Mobile in Canada running android 2.2.2. I bring it home and load up super one click and it tells me I am rooted, great! After that I loosely followed these instructions: hxxp://wiki.cyanogenmod.com/wiki/LG_Optimus_2X:_Full_Update_Guide to get ClockworkMod Recovery installed via the market (free version).
First little hiccup was that when I opened the mod manager and tried to click on 'Flash ClockworkMod Recover' it gave me an error saying, "Error while downloading from Server. Please make sure that you have a stable internet connection, and that your SD card is inserted and has free space!". That's weird.. I have a brand new 2gb sd card and my 3g connection is working great.. I was able to sort that out by connecting to my home wifi connection and then this message disappeared. When flashing clockwork it asks for my model of phone and I choose the LG G2X from the list. Success! Although when I try to click on the option to boot into recovery -- nothing happens. Since I don't want to power off my phone, I download "Quick Boot" by Sirius Applications Ltd. and try to click the reboot option, but again, nothing happens. The recovery option also does nothing, whats going on here? I finally decide to power down my phone the "normal" way from the home screen.
I boot back up normally and realize that I didn't download cyanogenmod yet, so I go do that. I download update-cm-7.1.0.1-G2x-signed.zip for the T-Mobile G2x, even though mine is not T-Mobile, I read on the internet that I definitely have a G2x even though it is marketed as an LG Optimus 2X. I also download the Google apps gapps-gb-20110828-signed.zip.
Once the files are downloaded, I attempt to copy them up to the memory card, but windows explorer (Im using Windows XP) seems to lock up for a bit and I get a weird error: Cannot copy gapps-gb-20110828-signed.zip: The path is too deep. I have never seen this copy error before. I look it up on google and don't get much help, although it tells me what I already assume, that this error appears when your filename + path combo is too long. But its not too long! gapps-gb-20110828-signed.zip is on my desktop, and I'm copying to the root of F:\ !! The other weird thing is that this gapps-gb-20110828-signed.zip is only 6MB large. I have no problem copying the update-cm-7.1.0.1-G2x-signed.zip which is 93MB! I can copy any other file I throw at it.. BUT I CANT COPY THE GAPPS FILE !? I tried so many things at this point. I renamed gapps-gb-20110828-signed.zip to gapps.zip. I redownloaded it from the mirror. I tried copying it from the root of C:\ and another drive. I tried unzipping it and rezipping it. I always got the same error.
Finally I decided to copy the gapps file to the internal memory, and it copied without a problem. I wasn't sure if I could access that drive from recovery, but I decided to try it, even without gapps since I wasn't having much luck getting it onto the card. In hindsight, I should have maybe tried copying it to another sd card and also tried copying to the same sd card plugged into my computer via sd reader to see if the same problems existed. Even rebooting the phone and my computer would have been some good troubleshooting, but I wasn't aware of what would happen next.
I booted to recovery at this point (I can't remember if I booted via the rom manager link or if I rebooted and held the power and volume down button) and it came up as expected. I first made a backup of the existing system even though I didn't think I really needed it. Then I did the Wipe data/factory reset and Wipe cache partition. Finally, I loaded the cyanogenmod update and was surprised at how it loaded in mere seconds-- my old dream always took at least 1 or 2 minutes even for a smaller file. I then noticed an option to load a zip file from my the other storage (I can't remember the exact name of the option - but it was the place where the gapps file was). I loaded gapps without error and rebooted the phone.
It is at this point that I never booted back into anything again. If I remember correctly, it loaded the first LG symbol as usual, and then I saw another 'fancier' LG logo come up, with no animation or progress bar. I waited on this screen for more than 10 minutes, expecting that it would finally change to cyanogenmod, but nothing ever happened. No problem I thought, I can just boot back into recovery and try again without the gapps perhaps. No dice. I removed and replaced the battery, and then booted up with the power and volume down arrow held. I saw a LG symbol with progress bar, I saw a android character coming out of a box with a progress bar. I let go of the buttons. The phone rebooted. I tried again and again. Nothing.
At this time I was getting quite worried, but I had my phone plugged into the computer still and I noticed that everytime I got to the 'fancier' LG logo screen, the computer would recognize the phone via usb. I decided to see what the internet offered for solutions and I read lots and lots of info.
Everything boiled down to pulling out the battery, holding the volume up and down buttons and then plugging the usb to the computer. I installed all the necessary drivers and ran nvflash in an attempt to either install CWM or even the stock recovery. Getting the computer to recognize the phone properly was a chore in itself. Often it would come up saying 'Unrecognized usb device' or it would simply show up in the device manager with an "!". Sometimes when it showed up with the "!" I would right-click and uninstall it, then unplug and replug and install the driver again and that would work for a time or two.
The problem was that when I ran any commands I found for nvflash, it seemed to take forever to do anything. I mean I would be waiting, and waiting, and waiting, and all the command prompt would say is:
"Nvflash started"
One post I read somewhere said to just try a harmless command of "nvflash --sync" to see if the proper output appeared. I tried it a few times, but all I got was the same "Nvflash started", but then one time I noticed after a while it came up with a new line after that of "rcm version 0X20001". I tried nvflash at least 1000 times, no joke. I wasn't about to let this brand new phone beat me without a fight.
On one occassion I tried using the "One Click Recovery Flasher" that I found, and I attempted to load the stock recovery. The response from nvflash seemed to flow a little quicker this time and I got further in the process then ever before. Since it was now 4am I decided to let it do its thing and I would wake up and check it in the morning. I woke up at 10am and it was exactly where I left it. After 6 hours, I would have expected it to do SOMETHING! Here is what it said:
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 4
chip sku: 0xf
chip uid: 0x037c704243a08357
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
It apparently was unable to send the fastboot file for some reason. I could try 1000 more times but I am defeated at this point. I am planning to return the phone today and see what they say. If by chance I return it successfully, and I get the same model of phone, I will be super wary of trying to root it again. But I also don't want a phone that I can't "have fun with". Any comments or suggestions are most welcome. I would like to know what I did wrong so that I can learn for "next time". Other than the weird sd card error, I really think I did everything correct. At this point I am thinking there was either something wrong with the sd card or even with the phone itself. Regardless, I thank you for reading my story and I look forward to any helpful responses.
Cheers!

I'm also on wind. The first thing I did was use nvflash to get a recovery. Never never use ROM manager to flash recovery on the g2x. It's a fake flash. Also, try running a vm or dual boot to use Linux. Nvflash worked fine on Linux didn't try on windows. no drivers needed. It recognizes it without doing anything special.
Sdcard problem is because the 2GB card is under /emmc or /sdcard/_Externalsd our something on stock.

tahahawa said:
I'm also on wind. The first thing I did was use nvflash to get a recovery. Never never use ROM manager to flash recovery on the g2x. It's a fake flash.
Click to expand...
Click to collapse
Did the same thing. I am on Linux too, and everything was extremely simple.
BTW, I think Wind's LG doesn't have screen bleeding or rebooting issues. I've never had them.

It sounds like you didn't install the drivers for the APX mode. When you get the explanation mark you need to right click and say update driver, then says I will find myself and browse to the apx directory where you extracted the One Click program for NVFlash. Then when it says the driver is unsigned click yes to continue. Once the apx driver is properly loaded you can flash CWM and reflash any rom you want. Don't worry your phone is not bricked. It is almost impossible to truly brick a G2X.

Did you resolve this issue. I just encountered it myself. Are you in Toronto by any chance. [sigh]. This sucks. I hope you can help shed some light.

Did you see my advice above? Try that. Also try re downloading everything, including all nvflash files.
Sent from my LG-P999 using XDA App

Awesome. Nvflash unbricked the SOB. I used the youtube video (lookup this one: "How To Install CyanogenMod 7 Nightly on T-Mobile G2x after Nandroid Backup") and the G2x P999 ROM from cyanogen, and got my phone back. The video worked perfectly for me and I would recommend it (but of course don't blame me if anything goes wrong... why should I be different? . The T-mobile stuff bugs me though. I wonder why the cyanogen mod has their branding in it. Ah well.
Now that my phone works again, I can figure out how to get those annoying lines to stop moving all over the frickin' place. Then back up this ROM so I have something to recover to. And maybe try the cynaogen Optimus 2x ROM; although it does say in the file name that it is 990 and not 999. And maybe give the fine xda ROM a go (since I found the answer here).
Thanks to Wind Mobile for messing around with the names and making it confusing. The Optimus 2x by Wind is a P999 and the same as what T-Mobile has, and an Optimus 2x looks to be a 990 everywhere else in the world. I guess Wind never intended to make it easy to upgrade these phones from the start (and aren't offering an official Gingerbread, never mind Ice Cream Sandwich upgrade). Now it looks like they won't even be selling them any more. I guess they would cut into the profit of the new more expensive Galaxy when it comes out.
I know I won't use that ROM manager again. At least not for this phone. Wow!
Thanks again for the quick reply and sticking my nose back into the answer.
Regards,
BillR

tahahawa said:
Never never use ROM manager to flash recovery on the g2x. It's a fake flash.
Click to expand...
Click to collapse
Is this true of ROM Manager in general, or is this something particular to the G2x?

dmj2012 said:
Is this true of ROM Manager in general, or is this something particular to the G2x?
Click to expand...
Click to collapse
Just the g2x/optimus 2x.
theshowmecanuck said:
Awesome. Nvflash unbricked the SOB. I used the youtube video (lookup this one: "How To Install CyanogenMod 7 Nightly on T-Mobile G2x after Nandroid Backup") and the G2x P999 ROM from cyanogen, and got my phone back. The video worked perfectly for me and I would recommend it (but of course don't blame me if anything goes wrong... why should I be different? . The T-mobile stuff bugs me though. I wonder why the cyanogen mod has their branding in it. Ah well.
Now that my phone works again, I can figure out how to get those annoying lines to stop moving all over the frickin' place. Then back up this ROM so I have something to recover to. And maybe try the cynaogen Optimus 2x ROM; although it does say in the file name that it is 990 and not 999. And maybe give the fine xda ROM a go (since I found the answer here).
Thanks to Wind Mobile for messing around with the names and making it confusing. The Optimus 2x by Wind is a P999 and the same as what T-Mobile has, and an Optimus 2x looks to be a 990 everywhere else in the world. I guess Wind never intended to make it easy to upgrade these phones from the start (and aren't offering an official Gingerbread, never mind Ice Cream Sandwich upgrade). Now it looks like they won't even be selling them any more. I guess they would cut into the profit of the new more expensive Galaxy when it comes out.
I know I won't use that ROM manager again. At least not for this phone. Wow!
Thanks again for the quick reply and sticking my nose back into the answer.
Regards,
BillR
Click to expand...
Click to collapse
Never flash anything meant for p990. Period. Unless it states it is for both. cyanogenmod had no Tmobile stuff except wifi calling.
Sent from my LG-P999 using XDA App

tahahawa said:
cyanogenmod had no Tmobile stuff except wifi calling.
Click to expand...
Click to collapse
When I first started the phone a message came up asking me if I wanted to run something, and that I could go to the T-Mobile site later if I didn't want to. Now I have been playing with it for the last hour and haven't seen any other TM related stuff, so maybe it was just that one.

The very first time it runs you get that message from the wifi calling app. You should never see it again unless you do a factory reset.

[Q] Virgin Mobile Galaxy 550 root FAIL. :c

Hi there. I got me a samsung galaxy 550 from virgin mobile canada yesterday, and well, I kinda like it despite being a slow piece of hardware with a 320x240 screen but until I can get enough money to buy something better, I'm fine with this (the phone I had before was a nokia n95, so that's a step up.)
The problem is, I want to try out the official 2.2.1 rom from samsung, and the only way I can do that is to update via odin. actually, that's not the problem, but I want to make a backup of all the apps I've downloaded already, and I just can't get it rooted. at all. z4root, universal androot, superoneclick; they just don't work. the one that was the closest to getting it rooted was superoneclick, and even then it can't finish the job, so I'm stuck with superuser on an unrooted phone, and titanium backup won't work either, so I'm kinda stuck here.
What else could I do?

anyone? please?

6 days later...

You may have noticed this is a "development and hacking" forum. Your problem reads more like a user error than a development one.
I do not mean to say this thread does not belong. It is just that "they just don't work" is something like what a Windows-using grandmother would say.
What are the exact errors you are getting? Preferably, they should be copied and pasted from the terminal itself.

Jason_25 said:
You may have noticed this is a "development and hacking" forum. Your problem reads more like a user error than a development one.
I do not mean to say this thread does not belong. It is just that "they just don't work" is something like what a Windows-using grandmother would say.
What are the exact errors you are getting? Preferably, they should be copied and pasted from the terminal itself.
Click to expand...
Click to collapse
Well, z4root doesn't do anything after it says "running exploit", superoneclick gets stuck on "waiting for device", and the only time it managed to get superuser onto it, it couldn't root the device no matter if I updated it or not; universal androot says "FAILED NO FU GOO", both odin and heimdall fails to connect to the device, and ADB doesn't even see the phone no matter what mode it is. I can't seem to find how to boot into recovery mode (I only ever get instructions to boot into download mode).

ok now in odin I get "cannot open the usb serial port. code: 2". sometimes it's code 5.

Go to madteam.co...dedicated for G5 users,you will get help there at no time
Sent from my blek krupuk

First problem is ADB not seeing the phone. ADB is pretty necessary if you want to debug something. You will need to download LG's Windows driver for your phone if you use Windows. I will include the one I use for my Optimus V here.
On many LG phones it is impossible to boot into recovery or fastboot mode without modification.
Try zergRush from here first:
https://github.com/revolutionary
If not working, try GingerBreak from here:
http://c-skills.blogspot.com/2011/04/yummy-yummy-gingerbreak.html
You may want or need to compile these first which is going to add another level of complexity. Be patient.
The general idea is:
1.setup your drivers
2.get comfortable working with ADB
3.run temporary root
4.immediately flash recovery
5.immediately Nandroid backup everything in several places for safety
6.test Nandroid backup
7.make whatever modifications you like, including permanent root

That's not a lg phone.

Ok so I managed to install cyanogemod and everything's fine. now, I just wanna know, is there any way to enable multitouch on this thing? it's got a capacitive screen, but no multitouch. can that be fixed or is it really just a hardware issue?

Multitouch is not possible,a fake dual touch is possible.
Sent from my blek krupuk

lexobys said:
Multitouch is not possible,a fake dual touch is possible.
Sent from my blek krupuk
Click to expand...
Click to collapse
fake dual-touch?