Database Info

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] can not go in download mode

Hi,
folow problem:
i made the upgrade from 2.2 to 2.3 and found out that there are some apps, language (German), try to downgrade to 2.2 since this was done (for 3Weeks) i can not use the phone because it shows AT&T when i push the power button, when i plug in the usb it shows just the charging symbol. Itry the 3 button reset nothing changed.
Yesterday i spend the hall day to find out is this a waranty case or not ?
Futureshop where i boughtthe phone said as long the phone is not running or show the ROGERS screen they can do nothing ???!!! Costumersupport - no comment.
At Rogers plus they said they have to send it in because its on a Rogers contract.
I tried the reset method with the Roger customer service the same result nothing changed. Just the AT&T screen.
My question is what else can i do to get the phone back so that it works befor i did this update.
I don`t no what downgrate it was, the only thing i know it was the update from samsung kies.
Have u any solutions ?
THX n Regards
Cooper21

Sounds like you have a soft-brick. You have to either buy a jig ( Which you can find here: http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-download-mode-jig/ ) Or follow this guide: http://forum.xda-developers.com/showthread.php?t=889128 Use either one of these to get into download mode, and flash back to stock with odin.

try using JIG to get it into download mode and do a reset with ODIN

Cooper21 said:
Hi,
folow problem:
i made the upgrade from 2.2 to 2.3 and found out that there are some apps, language (German), try to downgrade to 2.2 since this was done (for 3Weeks) i can not use the phone because it shows AT&T when i push the power button, when i plug in the usb it shows just the charging symbol. Itry the 3 button reset nothing changed.
Yesterday i spend the hall day to find out is this a waranty case or not ?
Futureshop where i boughtthe phone said as long the phone is not running or show the ROGERS screen they can do nothing ???!!! Costumersupport - no comment.
At Rogers plus they said they have to send it in because its on a Rogers contract.
I tried the reset method with the Roger customer service the same result nothing changed. Just the AT&T screen.
My question is what else can i do to get the phone back so that it works befor i did this update.
I don`t no what downgrate it was, the only thing i know it was the update from samsung kies.
Have u any solutions ?
THX n Regards
Cooper21
Click to expand...
Click to collapse
This is not a soft brick............don't panic. This is a kernel mismatch or bootloader problem. DON"T USE KIES FOR ANYTHING...except if you really want to brick you phone. I hate that program (my personal opinnion!!).
Have you tried the button combos to go to download?
see this link for some http://samsungcaptivate.wikia.com/wiki/Putting_the_Phone_into_Download_Mode
or google "Captivate Download Mode".
CHECK YOUR USB DRIVER VERSION. http://www.capfaq.com/w/USB_drivers Use the link to Samsung (click on "Software" blue link on top).....works best with Win XP, WIn Vista. You can also use 32-bit or 64-bit driver but see next comment IF YOU ARE ON WIN 7.
ALSO, DONT USE WINDOWS 7 64-bit, unless you have to. My opinion again............but a lot of experience behind it. The USB drivers are for 32-bit and is in my opinion flaky. If you can use Win XP then great, otherwise go with Win 7 32-bit. Even Win Vista is good.
THEN USE ODIN.
YOU HAVE TO FLASH THE STOCK 2.1 I897UCJF6 from here http://forum.xda-developers.com/showthread.php?t=1300843. The work upwards to 2.3. It is better to flash JF6 since I do not know what bootloaders are there on you phone.
.........if you can get download, then post back if you do not know how to get stock. There is always a chance of bricking your phone during flashing, but it is slim.

chappatti said:
This is not a soft brick............don't panic. This is a kernel mismatch or bootloader problem. DON"T USE KIES FOR ANYTHING...except if you really want to brick you phone. I hate that program (my personal opinnion!!).
Have you tried the button combos to go to download?
see this link for some http://samsungcaptivate.wikia.com/wiki/Putting_the_Phone_into_Download_Mode
or google "Captivate Download Mode".
CHECK YOUR USB DRIVER VERSION. http://www.capfaq.com/w/USB_drivers Use the link to Samsung (click on "Software" blue link on top).....works best with Win XP, WIn Vista. You can also use 32-bit or 64-bit driver but see next comment IF YOU ARE ON WIN 7.
ALSO, DONT USE WINDOWS 7 64-bit, unless you have to. My opinion again............but a lot of experience behind it. The USB drivers are for 32-bit and is in my opinion flaky. If you can use Win XP then great, otherwise go with Win 7 32-bit. Even Win Vista is good.
THEN USE ODIN.
YOU HAVE TO FLASH THE STOCK 2.1 I897UCJF6 from here http://forum.xda-developers.com/showthread.php?t=1300843. The work upwards to 2.3. It is better to flash JF6 since I do not know what bootloaders are there on you phone.
.........if you can get download, then post back if you do not know how to get stock. There is always a chance of bricking your phone during flashing, but it is slim.
Click to expand...
Click to collapse
I must disagree with your recommendation for jf6. I would recommend KB1 or KB2. They are both available in the development section.

mrhaley30705 said:
I must disagree with your recommendation for jf6. I would recommend KB1 or KB2. They are both available in the development section.
Click to expand...
Click to collapse
Agreed. But his 'case hsitory' is murky. In fact, I actually first posted KB1 then changed to JF6, since though he says 2.2 who knows what state his phone's in. He may also be stuck somehwere in between on 2.3, where GB bootloaders may or may not be on. JF6 without bootloaders would be safest.

At this point, it looks as if he should start over. Completely start over. With bootloaders. Yes I know the danger involved in flashing bootloaders, but in this state it may be the only choice. Attempting to use jf6 w/out bootloaders could result in another boot loop. Their is the option of using Heimdall to flash kb1, taking out the bootloaders before flashing.

mrhaley30705 said:
At this point, it looks as if he should start over. Completely start over. With bootloaders. Yes I know the danger involved in flashing bootloaders, but in this state it may be the only choice. Attempting to use jf6 w/out bootloaders could result in another boot loop. Their is the option of using Heimdall to flash kb1, taking out the bootloaders before flashing.
Click to expand...
Click to collapse
Yes fully agree.

hi,
1 thx for the help n support but i have no experience how this all work.
2 i send it in after phone caal with rogers tech support, they try to fix it, when its not fixable i geet a new phone.
3 when i get a new one maybee i have to downgrade it.
King regards
Cooper21

Firmware 5699 Released OTA

Viewsonic has finally released a update OTA for the GTablet:
http://www.viewsonic.com/gtablet/support.htm

Guess what this one bricks
Just like the one we had last April, this new one bricks as well. Mine doesn't even want to read the external sd card. I tried nvflash and it doesn't recognize it. Save this one and try it later.

Installed the Firmware 5699 OTA this morning. Upgraded with no problem.
After 10 months of no support from VS, I wonder why now? I wish there was a changelog for this...

No changelog. Wow. Never update firmware without at least reading the changelog....esp if system is stable

Great. Now give us official ICS or source code

Pawnty said:
Great. Now give us official ICS or source code
Click to expand...
Click to collapse
That would be very interesting.
EDIT: not going to happen though.

Your cool Viewsonic, STILLLLLLLLL android 2.2...

I feel like this is a more of a low blow than anything. Us as users ***** for literally an entire year and Viewsonic labels the gTablet as an archived product on their website basically fully dropping support for it. Now 2012 rolls around and ICS is finally making its way onto a slew of devices and Viewsonic drops another update to a Froyo rom? Really? That was 2 generations ago... Like the hardware is still there to do something with this device. Team Drh has been proving this as we continue development with ICS. Now if Viewsonic wants to help us push ahead with this mission, by all means please help us out. But dropping updates to Froyo is BS if you ask me. But hey, what do I know...I'm just a user with an "outdated" tablet.

fosser2 said:
But hey, what do I know...I'm just a user with an "outdated" tablet.
Click to expand...
Click to collapse
LOL! That's funny!

Changelog is up. Looks like everyone is being pushed to BL 1.2 now.
http://www.viewsonic.com/gtablet/support.htm

Ok I NVflashed my Gtab just for shticks and smiggles to see what this 5699 update was really all about...
Conclusion...GARBAGE! Plus it tells you to restart your Gtab and ends up having a broken android icon with an exclamation mark on the screen!!
Oh well...now Imma flash my PreAlpha ICS rom again! YEY!

ml_boston said:
Changelog is up. Looks like everyone is being pushed to BL 1.2 now.
http://www.viewsonic.com/gtablet/support.htm
Click to expand...
Click to collapse
Not much of a change log. They state over 40 enhancements, but then only list four.

arveeee said:
Ok I NVflashed my Gtab just for shticks and smiggles to see what this 5699 update was really all about...
Conclusion...GARBAGE! Plus it tells you to restart your Gtab and ends up having a broken android icon with an exclamation mark on the screen!!
Oh well...now Imma flash my PreAlpha ICS rom again! YEY!
Click to expand...
Click to collapse
Sounds like your GTab didn't take the update. It sounds a lot like the OTA update failures on Xoom's and TF's when its been rooted or modded.
Honestly though I do not see any visible changes. All code enhancements is my guess.

I am new and have only had the gtab for two months. I thought this is an update and I should download. Now my gtab doesn't work. I am not a techy by and stretch of the imagination.
I have done the power and +volume and it said recovery and had a wrench/screwdriver on it. Then it was coming on but stuck in the tap n tap screen and then turning off.
I only use to read and play games and will be nice to have on vacations or when away from home/work but now it doesn't work. I could use help.
Any help is appreciated. Wish I could take a class. Looked at viewsonic for dummies but even that is over my head.
Thanks for any help.

dleem said:
I am new and have only had the gtab for two months. I thought this is an update and I should download. Now my gtab doesn't work. I am not a techy by and stretch of the imagination.
I have done the power and +volume and it said recovery and had a wrench/screwdriver on it. Then it was coming on but stuck in the tap n tap screen and then turning off.
I only use to read and play games and will be nice to have on vacations or when away from home/work but now it doesn't work. I could use help.
Any help is appreciated. Wish I could take a class. Looked at viewsonic for dummies but even that is over my head.
Thanks for any help.
Click to expand...
Click to collapse
Do you know if your tablet was modified (custom rom, rooted, etc.) when you took the update? People with modified stock roms and recovery seem to be having this issue on another forum.
I would say the easiest fix to try would be to drain the battery completely (might take a while) if you can boot into recovery (power) + (volume+) or apx (power) + (volume-) and leave it on till it dies (edit - if you can boot into recovery try the wipe data/factory reset option if there is one, then try to reboot. That might fix it also). Keep doing that till the tablet won't turn on anymore. Then charge it and try turning it on again. If you are lucky it will reset your tablet to stock without any complicated fixing or flashing.
Remove your SD card if you have one before you do this. You will also loose any data not stored on your SD if you do reset it but hopefully it will work again.

Same Problem
I had this same problem yesterday after downloading the OTA update. I was able to restore the bricked device by holding the power for 5 seconds (figured it was shutting down in that amount of time) restarting in APX mode (power button and volume - simultaneously) and I did not see a screen response, I plugged in the USB cord and checked the safely remove hardware widget on the bottom right of windows system tray and could see NIVIDIA device. Therefore, I knew the GTAB was on and in APX mode. I then went to the rom of choice (stock tapntap) and double clicked the batch file for the ROM and watched as it went to the CMD prompt screen and transferred the file. I did have to run the batch file several times to get it to work...but it did. I downloaded the OTA again, and discovered the same results with the same fix. I will not download the OTA update a third time. Good Luck.

I had just put my VS GTab back to complete stock 1.2 4349 in anticipation of the ICS Rom release coming soon. My GTab showed a OTA update was available and I accepted the update. It downloaded and ran through the process with no issues at all. Some of the people having issues must have modified or rooted devices.
---------- Post added at 08:36 AM ---------- Previous post was at 08:34 AM ----------
dleem said:
I am new and have only had the gtab for two months. I thought this is an update and I should download. Now my gtab doesn't work. I am not a techy by and stretch of the imagination.
I have done the power and +volume and it said recovery and had a wrench/screwdriver on it. Then it was coming on but stuck in the tap n tap screen and then turning off.
I only use to read and play games and will be nice to have on vacations or when away from home/work but now it doesn't work. I could use help.
Any help is appreciated. Wish I could take a class. Looked at viewsonic for dummies but even that is over my head.
Thanks for any help.
Click to expand...
Click to collapse
http://viewsonic-gtablet-for-dummies.webs.com/
dleem this is not difficult. Sit down, focus and read. It has step-by-step instructions. Go to Code Red.

ml_boston said:
Changelog is up. Looks like everyone is being pushed to BL 1.2 now.
http://www.viewsonic.com/gtablet/support.htm
Click to expand...
Click to collapse
Yes. I can confirm this on my old device ( was running 1.1.3588 ). I went ahead and updated the tablet, and found out the exact upgrade path.
I'm for devices using firmwares older than mine, the first update will probably be to version 1.1.3588, and then from there, the rest of the updates.
The first update after 1.1.3588 is 1.1.3588+. After installing this update, the tablet will have be able to update to 1.2.5699 using the update program, or waiting for the notification.

yup.. downloaded find and dies on the install....I wonder if I take CWM off and do a factory restore if it would work.

Clear data/cache
To upgrade, you have to use stock recovery with 1.2 bootloader. Not rooted. No CWM.
In stock recovery clear data/factory reset, clear cache; otherwise, you'll get stuck. You will lose everything so backup with Titanium Backup.
I keep a copy of Titanium Backup and Amazon Appstore Apps on my SDCARD and SDCARD2 to install after installation and restore apps.
Plants vs Zombies crashes on this.
Pixel Rider on Slatedroid will eventually mod this with market and root to be named Detonator.
If you like stock, stability and camera, this ROM has a niche.

[Q] Motorola Defy default restore

Hello, I have a Motorola Defy which i have rooted and installed clockworkmod on it. I tried to install Cyanogen mod 7.1 from the website. The phone got to the boot screen where it continued to cycle through it thing and nothing more. I restarted the phone and now it gets stuck at the first screen where its says "google". I tried to enter recovery again (power + volume down) and clockworkmod is completely gone. I want to go back to the stock OS so it atleast works again. Ive tried using the update.zip option in the stock recovery mode but I keep getting an error "failed to verify whole-file signature" when using a signed copy of cyanogen mod. I also tried putting my backup in a zip with the same error. Ive even tried formatting my sd card. What do i do?

I was more or less where you are around June or so. I'm no expert by any means, but perhaps I can help. If memory serves I used a program called RSD Lite to flash it back to the stock unlocked rom I got from the "bl7 finally rooted" thread - if you unlocked a different way, I'd try to find your original rom.
Once you get to where you understand how to get back to stock it makes the whole thing a lot less scary, or it did for me. Once you get back up and running, try flashing Whiterabbit. I didn't have luck getting anything else to run, but that one worked the first time I tried it, and I'm very happy I persevered. Miles better than the stock OS.

Marvelicious75 said:
I was more or less where you are around June or so. I'm no expert by any means, but perhaps I can help. If memory serves I used a program called RSD Lite to flash it back to the stock unlocked rom I got from the "bl7 finally rooted" thread - if you unlocked a dirrerent way, I'd try to find your original rom.
Once you get to where you understand how to get back to stock it makes the whole thing a lot less scary, or it did for me. Once you get back up and running, try flashing Whiterabbit. I didn't have luck getting anything else to run, but that one worked the first time I tried it, and I'm very happy I persevered. Miles better than the stock OS.
Click to expand...
Click to collapse
I cant use the program as my phone doesnt get detected when connected to my pc.

OK, lets start with the basics, if I can remember it right... Have you used RSD Lite successfully before this? Drivers installed? Using bootloader mode? If any of this is unfamiliar go hit the beginner's thread - if you have done all this you may be beyond my help and in need of someone a bit more experienced.

Marvelicious75 said:
OK, lets start with the basics, if I can remember it right... Have you used RSD Lite successfully before this? Drivers installed? Using bootloader mode? If any of this is unfamiliar go hit the beginner's thread - if you have done all this you may be beyond my help and in need of someone a bit more experienced.
Click to expand...
Click to collapse
I fixed it, there were a different set of buttons to hold to get into boot loader. The default recovery was not over written as i thought (happened to all my other phones). Thank you very much for you help. It has been very much appreciated.

Glad to hear it.

lg optimus zone 3 lgvs425pp stock firmware dump

hopefully this will help out some people and the developers to make,fix,restore a not so popular phone. I did a total firmware dump and have uploaded to my 4shared folder. If anyone is interested or can tell me how to upload it here for developing i will be more than happy to share with those in need. I also have a spare phone that i would be willing to test anything made from the firmware dump i created.

PLEASE link?
Some time after rooting my Optimus Zone 3 VS425PP, I got locked into a boot loop. There are no custom ROM's, neither recovery nor OS. It's not bricked. Yet, anyway. The loading screen functions, then a little window that says "OPTIMIZING APPS 1 OF 5, PLEASE DO NOT REMOVE THE BATTERY..." appears. I've seen this before, but now, upon reaching "APP 5 OF 5," it reboots and repeats. I've tried several factory resets via the LG RECOVERY (MODIFIED,) as well as safe mode to no avail. Anyone? Anything? Help? The only recourse I can think of would be to re-flash the stock ROM, which I cannot find. Anywhere. Thanks, guys.

i tried contacting judthro for the same file; no luck
Cruise Elroy said:
Some time after rooting my Optimus Zone 3 VS425PP, I got locked into a boot loop. There are no custom ROM's, neither recovery nor OS. It's not bricked. Yet, anyway. The loading screen functions, then a little window that says "OPTIMIZING APPS 1 OF 5, PLEASE DO NOT REMOVE THE BATTERY..." appears. I've seen this before, but now, upon reaching "APP 5 OF 5," it reboots and repeats. I've tried several factory resets via the LG RECOVERY (MODIFIED,) as well as safe mode to no avail. Anyone? Anything? Help? The only recourse I can think of would be to re-flash the stock ROM, which I cannot find. Anywhere. Thanks, guys.
Click to expand...
Click to collapse
Unfortunately, I don't think this file is actually out there. I have REALLY been looking, even contacted the LG Development team. The LG Support Tool, etc. are not going to help you yet as they do not have the firmware on their servers yet. That's why the LG Support Tool will freeze when trying to do an Update Recovery on this phone. -- And I've tried them all: LG Mobile Support Tool, LG PC Suite, Verizon VS425PP Update Tool (from the mounted drive on the phone), LG Flash Tool 2014 to force different KDZ files. All provide nothing. All dead ends. The Optimus won't grab a COM unless it is the right signed firmware for the phone. You'll just sit there in Download Mode or in Debug mode forever with no result. We have to wait for the first update from LG from version VS425PP1 to whatever comes next so they have something to stick on their server. But...if you find something before then, please let me know! The update will eventually be released to the public. It'll probably just take a year or so.
Good thing is Wal-Mart sells these for under $12 (yes, that's right). I picked up seven of these quad-core bad boys at that deal. Just bugs the hell out of me I can't fix the one I over rooted.

this *might* be promising...
Cruise Elroy said:
Some time after rooting my Optimus Zone 3 VS425PP, I got locked into a boot loop. There are no custom ROM's, neither recovery nor OS. It's not bricked. Yet, anyway. The loading screen functions, then a little window that says "OPTIMIZING APPS 1 OF 5, PLEASE DO NOT REMOVE THE BATTERY..." appears. I've seen this before, but now, upon reaching "APP 5 OF 5," it reboots and repeats. I've tried several factory resets via the LG RECOVERY (MODIFIED,) as well as safe mode to no avail. Anyone? Anything? Help? The only recourse I can think of would be to re-flash the stock ROM, which I cannot find. Anywhere. Thanks, guys.
Click to expand...
Click to collapse
well i'll be. this may be a promising link:
google "4share lgvs425pp" and scroll down to the 4shared link. There is a 999MB RAR file claiming to be the VS425PP ROM dump. I'm downloading it now...checking it out.

It works???!!! i have to root this cellphone because i need use with other company...

its not super useful yet
johhnyapplefake said:
well i'll be. this may be a promising link:
google "4share lgvs425pp" and scroll down to the 4shared link. There is a 999MB RAR file claiming to be the VS425PP ROM dump. I'm downloading it now...checking it out.
Click to expand...
Click to collapse
hopefully the op will chime in for insight. The 999MB isn't much good. It appears to be a RAR dump of all the partitions, perhaps made from a lglaf.py script while in download. Nevertheless, i havent found any way yet to push the firmware dump onto the phone.

I've had no luck, either.
johhnyapplefake said:
hopefully the op will chime in for insight. The 999MB isn't much good. It appears to be a RAR dump of all the partitions, perhaps made from a lglaf.py script while in download. Nevertheless, i havent found any way yet to push the firmware dump onto the phone.
Click to expand...
Click to collapse
Meanwhile, as my LG cycles endlessly through my really cool "Jolly Roger" boot animation, I stumbled across a Kyocera Hydro Wave at Walmart for $20. I snapped it up to replace the LG Optimus Zone 3. I had big plans to root it, too., but I should've researched it first. The specs are great... but one check on Cyanogen's website probably would've saved me some trouble. Not one Kyocera device is listed there. XDA thread also throws red flags-no one can get root to stick. Well, I at least learned a lesson. Next time, I plan to purposefully buy a phone that can be rooted, has been rooted, has instructions online to do so, AND has at least one custom ROM available! No wonder this thing was $20! Keep us all posted if you stumble across a bootloop fix of some kind, and I'll do the same.

here is stock recovery for this device https://www.dropbox.com/home/Apps/Flashify/VS425PP/recovery

matt4787!
Either I am unable to open that link from an Android device OR the link given is to an unshared folder? It just asks me to log in and then says 'that folder does not exist in your DropBox...' PLEASE check out the SHARE link from within your DropBox and maybe share a new folder (and drop the stock ROM in there, along with what you might've used to flash it maybe?) We'd be very grateful!

Recovery
https://drive.google.com/file/d/0B1Nk8cx3_QgAeGNxZ1JrUmtFS0E/view?usp=drivesdk
Try now

hope my post helped some ppl. now to get twrp recovery ported here.

Thank you matt4787!!
Sent from my C6740 using XDA-Developers mobile app

To all who have a bricked,phone this phone has an update. Download the LG software assistant and put assistant in repair mode then boot phone normally and wait a bit. Run the repair assistant and let it run. Hopefully if everything runs well as it did me. Mine is restored and running.

Just ordered one. Is there root for this phone? Unlocked bootloader or forgetaboutit?

I rooted this phone and then tried to de-bloat, but I must have deleted too much. Now when I boot all I get is "Security Error - Authentication Fail #9"
I can get to Download mode, but none of the recovery programs recognize the phone. I installed the drivers, but still nothing. Is there anything I can do?

matt4787 said:
To all who have a bricked,phone this phone has an update. Download the LG software assistant and put assistant in repair mode then boot phone normally and wait a bit. Run the repair assistant and let it run. Hopefully if everything runs well as it did me. Mine is restored and running.
Click to expand...
Click to collapse
was your phone in a "security error" loop? for some reason the software assistant won't recognize my phone. it'll identify a plugged in phone when I connect it in download mode, but the device model never shows up

nikicollazo said:
was your phone in a "security error" loop? for some reason the software assistant won't recognize my phone. it'll identify a plugged in phone when I connect it in download mode, but the device model never shows up
Click to expand...
Click to collapse
i forgot to mention that you have to be in download mode to make the assistant recognize the phone. plus make sure the drivers for the phone are installed on your pc

matt4787 said:
i forgot to mention that you have to be in download mode to make the assistant recognize the phone. plus make sure the drivers for the phone are installed on your pc
Click to expand...
Click to collapse
hello as you did to install the drivers , I find no way to reconnoitre the mtp device ! Thank you

angelgabg said:
hello as you did to install the drivers , I find no way to reconnoitre the mtp device ! Thank you
Click to expand...
Click to collapse
this one is troubling. hmm you got the stock rom from lg? if so then try downloading the drivers from verizon.

Any updates on recoveries? I hate being scared of tweaking due to not having a backup .-. Anyone find something? Plz lemme know, thx! Btw kingo root 4.5 seems to have root for this phone but super sume seems to brick it. Just a heads up eace: