I decided to try to update to GB because my G2X rebooted while on the charger, clock night mode turns off and the screen locks, and wifi is ok but resets sometimes. My phone is stock 2.2 with stock recovery but rooted.
I turned off all programs on my Windows 7 32 bit laptop, turned off anti virus and turned off Windows firewall. The updater ran ok, checked the phone environment and downloaded the update. Then at 4% when the phone is supposed to download into software update mode, it just sat there staying in Android. After the update failed and it told me to remove the cable and remove battery, etc., I just shutdown the phone, did a battery pull and turned the phone back on. I then canceled the update.
My phone booted back into Android no problem. I tried to boot into recovery using Quickboot but that just rebooted the phone back into Android. My questions are as follows:
1. Did the update change anything on the phone or did it fail before attempting to change anything?
2. Why did it fail to boot into software update mode? Do I need to try another USB port or another computer?
3. Should I use the alternate method on a Windows XP machine that people use when their phone is soft bricked?
4. Should I just install CWM recovery and use the pre-rooted zip of GB with the old baseband?
5. Or should I just forego the update for now and see if another update is released?
Try reinstalling everything, and restarting your computer. It worked just fine on Windows 7 Ultimate x86, and x64.
My update went the same way but everytime I retried it got a little further so I just retried it over and over till I hit 100 percent
Sent from my LG-P999 using XDA App
I just tried to run the LG update program on my XP machine but I got a runtime error (see attached). Anybody know what this means and how to fix it?
Does anyone know why it just sits there on 4% and never boots into the software update mode? Can I just run it and then when it fails manually boot into software update mode? Or is that risking a brick?
jboxer said:
I decided to try to update to GB because my G2X rebooted while on the charger, clock night mode turns off and the screen locks, and wifi is ok but resets sometimes. My phone is stock 2.2 with stock recovery but rooted.
I turned off all programs on my Windows 7 32 bit laptop, turned off anti virus and turned off Windows firewall. The updater ran ok, checked the phone environment and downloaded the update. Then at 4% when the phone is supposed to download into software update mode, it just sat there staying in Android. After the update failed and it told me to remove the cable and remove battery, etc., I just shutdown the phone, did a battery pull and turned the phone back on. I then canceled the update.
My phone booted back into Android no problem. I tried to boot into recovery using Quickboot but that just rebooted the phone back into Android. My questions are as follows:
1. Did the update change anything on the phone or did it fail before attempting to change anything?
2. Why did it fail to boot into software update mode? Do I need to try another USB port or another computer?
3. Should I use the alternate method on a Windows XP machine that people use when their phone is soft bricked?
4. Should I just install CWM recovery and use the pre-rooted zip of GB with the old baseband?
5. Or should I just forego the update for now and see if another update is released?
Click to expand...
Click to collapse
Follow your Item 4
Finally got it updated
Used Windows 7 32bit.
The update progressed very scarily.
I downloaded the drivers and reinstalled them directly from the update program. I then used a different USB port then my previous attempt, unplugged all other USB devices, and shutdown everything running on the computer I could including Avast andti-virus and the Windows Firewall. This time when I plugged the G2X into my computer a lot more devices installed than last time (first time only 2 devices were installed, this time about 8 to 10).
During the first download of the firmware I canceled it because I realized I left the micro sd card in the phone and the instructions on the website say to remove the card. Then I also decided to unroot the phone and remove all programs that require root access. Since the phone would be unrooted after an update I decided I didn't want superuser in the system if I couldn't use it, and after the update I would be unable to remove it since the phone would not be rooted.
Then I ran the program again and this time the phone booted into software update mode. It started pushing the update to the phone and at 5% the phone disconnects from the computer and reconnects (does this three times during the update) but the software doesn't see the phone and tells me to unplug the USB cable, remove the battery, reinsert the battery and turn the phone back on. But I heard the computer reconnect to the phone so I decided I would just remove the cable and reinsert it. This worked and the update started over again. This time it went past 5% and then reset the phone connection again at 46%. It then slowly completed the update resetting one more time at 76% and when it reconnected it went back to 75% but then progressed to 100% and rebooted the phone.
It now has an updated baseband and Gingerbread 2.3.3. I am leaving it unrooted for now and just use it stock.
jboxer said:
Does anyone know why it just sits there on 4% and never boots into the software update mode? Can I just run it and then when it fails manually boot into software update mode? Or is that risking a brick?
Click to expand...
Click to collapse
I do! It's installing one of the THREE usb drivers that it installs over the course of the upgrade. Mine got stuck at 4% for just a second (at which point I about **** my pants), but then I saw a Win7 notification pop up that it had just installed a USB driver, and then it proceeded to do the update.
So maybe the failure mode is the LG updater not being able to install a USB driver?
Maris_ said:
Follow your Item 4
Click to expand...
Click to collapse
Is there any significant reason to update to get the newest baseband and then flash CM7? Or is there no benefit from the new baseband?
brdma said:
Is there any significant reason to update to get the newest baseband and then flash CM7? Or is there no benefit from the new baseband?
Click to expand...
Click to collapse
July 15, 2011 baseband has more reliable wifi and much better GPS lock. After the scares of getting mine updated finally, my G2X has had no issues in the 30+ hours since the update. No reboots on charger, no sleep of death and everything is working as it should.
Related
I tried (risk) this tonite and it work out good. It took me like 20 min (should be shorter if I understand with the instruction means the first time). It's prretty simply and straight forward.
**It works with me but I can't guarantee it'll work with anyone else. I just think that it don't make sense requiring a window XP machine to do the update. I don't responsible to anyone brick their phone**
1) Go to LG Support web site and "Download LG Mobile Support Tool to PC"
2) After download the LG Mobile support tool (updater tool), run it. It'll show phone is discounted. Plug in your phone and it should start connecting it. If doesn't connect, click the install driver on the right hand side. After the new driver installed it will connect.
3) Once connected to your phone, click the update button on the bottom. The software will update your phone now. Your phone will show up the S/W update screen now.
4) When the installation bar run to 50%, it'll stop and ask you to do something. The instruction ask you to first unplug the phone; second remove battery and then put it back in; third turn on your phone (it'll show S/W update screen); forth click "restart" button; fifth when it show phone disconnected, plug back in your phone and click restart again.
5) Now it'll start the update all over again from 0%. Here's the tricky part. This time the installation will run pass 50% but stop at 75% asking you to do the same thing on step 4. So you just do exactly what you just did from step 4.
6) Same thing it'll start the update from 0% again. This time it'll run all the way to 100% and complete the update. Once it complete your phone will boot up again. Then you'll have updated baseband 2.3.3 v21e rom.
After that you'll do all the recovery and flashing as usual. The speed is faster than 2.2.2 (I test it with a bone stock G2x). Everything is working fine.
I just found one problem. IF you need to install new driver from the LG Mobile Support Tool in order to connect your phone, you'll need to re-install the T-Mobile USB driver v2.2 to get your phone mount to your PC again.
Enjoy and hope this help.
PS: If the Mods find it useful, please sticky this.
nice write up.
A few things i found.
works much better on 32 bit versions.
you must have a t-mobile SIM for the updater to work.
I am on Walmart Family Mobile and if fails the Cell # check.
if you fail somewhere, it may be required to uninstall everything and start over.
darknessxyz said:
I tried (risk) this tonite and it work out good. It took me like 20 min (should be shorter if I understand with the instruction means the first time). It's prretty simply and straight forward.
**It works with me but I can't guarantee it'll work with anyone else. I just think that it don't make sense requiring a window XP machine to do the update. I don't responsible to anyone brick their phone**
1) Go to LG Support web site and "Download LG Mobile Support Tool to PC"
2) After download the LG Mobile support tool (updater tool), run it. It'll show phone is discounted. Plug in your phone and it should start connecting it. If doesn't connect, click the install driver on the right hand side. After the new driver installed it will connect.
3) Once connected to your phone, click the update button on the bottom. The software will update your phone now. Your phone will show up the S/W update screen now.
4) When the installation bar run to 50%, it'll stop and ask you to do something. The instruction ask you to first unplug the phone; second remove battery and then put it back in; third turn on your phone (it'll show S/W update screen); forth click "restart" button; fifth when it show phone disconnected, plug back in your phone and click restart again.
5) Now it'll start the update all over again from 0%. Here's the tricky part. This time the installation will run pass 50% but stop at 75% asking you to do the same thing on step 4. So you just do exactly what you just did from step 4.
6) Same thing it'll start the update from 0% again. This time it'll run all the way to 100% and complete the update. Once it complete your phone will boot up again. Then you'll have updated baseband 2.3.3 v21e rom.
After that you'll do all the recovery and flashing as usual. The speed is faster than 2.2.2 (I test it with a bone stock G2x). Everything is working fine.
I just found one problem. IF you need to install new driver from the LG Mobile Support Tool in order to connect your phone, you'll need to re-install the T-Mobile USB driver v2.2 to get your phone mount to your PC again.
Enjoy and hope this help.
PS: If the Mods find it useful, please sticky this.
Click to expand...
Click to collapse
Man, this is a dangerous post. You were told to remove your battery, because a connection could not be made. If you remove the battery during an install that has no connection problem, you will brick your phone.
Be very clear here. When updating anything, first and foremost, follow instructions listed on the page. Read the instructions through BEFORE starting update. If you do not understand, do NOT update.
Do not adlib. Do not think you know better. Do NOT pull your battery unless you are told Pull your battery.
32bit/64 bit Windows 7 makes not difference. It will update equally with either. But you should protect your update by making sure pop up blockers and malware/AV are turned off. Turn off fax programs, skype, things like that. Then try your update. BTW....this is true for most updates on any other device, to include your PC.
Just be careful and follow instructions.
I dont understand I Used the LG update tool the day no wait the hour the update came out I have a windows 7 64 bit pc my phone is a p999dw and it went off without a hich. I did not have to pull the battery and I did not have to install the updated drivers. I had the LG mobile updater on my computer since I bought the phone about 2 weeks after relese and discovered that I needed to install the drivers. I dont understand why all the problems and I never heard You can only use an xp machine. I did however read that you originally needed an xp machine to fix your phone if it bricked but even that was fixed. Just like the dude said in the post above me just read the directictions and be careful
ehh all i can see now is S/W uptade srcreen, i can reboot to cwm recovery,
does it mean i need a new phone or there is still a chance? ;/
Nvm, ive just called TM and they gonna send me a replacement
I used the phone for about 2 days after I updated to mango. While I was at class the phone died because of low battery. Once I plugged it back up it's been stuck at the samsung screen for three days now. Tried format, tried download mode but can't get the software to do anything when I open it just says "cannot image file", and I tired recovering the phone with zune. It will get to Step 2 and do nothing more even after running for a good 10 hours. Any suggestions? Using Samsung Focus 1.3
bulletdog said:
I used the phone for about 2 days after I updated to mango. While I was at class the phone died because of low battery. Once I plugged it back up it's been stuck at the samsung screen for three days now. Tried format, tried download mode but can't get the software to do anything when I open it just says "cannot image file", and I tired recovering the phone with zune. It will get to Step 2 and do nothing more even after running for a good 10 hours. Any suggestions? Using Samsung Focus 1.3
Click to expand...
Click to collapse
There is a chance that the battery went below control charge and it appears dead. Before you do anything to the phone I recommend to replace the battery. There is a control circuit in the battery that tracks capacity. If the capacity falls below a critical value, it won't charge anymore and the battery appears dead.
edit: sorry, never mind, I didn't read your post carefully enough.
Do you have an expansion microsd card? if so, pull it out... might just be a cooincidence that you had one fail.
ROCOAFZ said:
Do you have an expansion microsd card? if so, pull it out... might just be a cooincidence that you had one fail.
Click to expand...
Click to collapse
Never used a SD card with phone, I went to ATT store and tried a new battery, didn't help. From reading it sounds like a firmware ordeal but like I said before the software for tye binaries won't do anything
tried running zune restore again, this time got a error message. Downloaded the windows phone support tools and and ran it. This time got a error of 80004005
This happened to me when I was trying to hack update to mango. I fixed it by doing these steps.
1) Restore it to the original ROM. I think it is 7004.
Here is a good tutorial (just read the description no need to watch the vid http://www.youtube.com/watch?v=hvw5gLY6sOc
2) Use Chevron hack to update to nodo.
3) Update to Mango
Not sure if it has changed where the device will auto update from 7004 to 7720, so you can check that right after you flash it.
Sk8rjwd said:
This happened to me when I was trying to hack update to mango. I fixed it by doing these steps.
1) Restore it to the original ROM. I think it is 7004.
Here is a good tutorial (just read the description no need to watch the vid
2) Use Chevron hack to update to nodo.
3) Update to Mango
Not sure if it has changed where the device will auto update from 7004 to 7720, so you can check that right after you flash it.
Click to expand...
Click to collapse
Followed the link and stuck at connecting my phone while it's in download mode, the computer wont recognize it so I can't start the flash. The search continues.
UPATE:
Finally got the computer to recognize the phone, I had to download the samsung usb drivers from their website. Installing mango right now. Should I try a recovery now that the phone is working that was made before the orginal mango update? Or should I just suck it up and start from scratch. THANKS Sk8rjwd!
bulletdog said:
I used the phone for about 2 days after I updated to mango. While I was at class the phone died because of low battery. Once I plugged it back up it's been stuck at the samsung screen for three days now. Tried format, tried download mode but can't get the software to do anything when I open it just says "cannot image file", and I tired recovering the phone with zune. It will get to Step 2 and do nothing more even after running for a good 10 hours. Any suggestions? Using Samsung Focus 1.3
Click to expand...
Click to collapse
i got this problem with my omnia gt 8350 , battery die, and now my phone is brick no power no nothing replace the battery still no go. no power, when i plug to usb the pc telling me to install driver called QHSUSB installed susses ,and in the device manager i can see the phone is detected, by the windows but, still cant reflash it, i dont have the rom for this device plus, i cant boot to download mode.
find another phone with a similar battery, running something other than wp7 and charge it till boot. you should be good to go from then on. happened to me once. lucky my dad has an incredible s so my mozart battery fit there and i could charge. i was on beta mango though. rtm mango fixed this issue for me where in several cases my battery died but i still managed to get it charged up normally
After checking lots of other recent posts, nothing has come close to the problems I'm having.
Nexus S (of course), i9020T, running CM7 before the trouble started. In order to load the OTA update I tried to flash back to stock 2.3.6. Flashed to 2.3.6 successfully (quickly went through setup process on 2.3.6, just to check.)
Then went back onto clockwork mod to install the ICS update. update went very quickly and I then tried rebooting the phone. Just get the ICS boot screen on an endless loop. Start the phone in fastboot mode, but now can't get to recovery (get "dead droidbug" image). Device doesn't show up when connected with USB on Mac, Windows or Linux. Ran ADB on computer and it says the device is not connected. Tried using Unbrickable, didn't detect the device. HOWEVER, when connected to Windows it shows up as "Android 1.0" in device manager, but says that there are no drivers isntalled for it, and none of the drivers from Android SDK work.
Device can still charge from USB, and I can get to fastboot on the device itself. If I can some how get the device to show up on USB I know I'd be set. Any thoughts?
filmgeekben said:
After checking lots of other recent posts, nothing has come close to the problems I'm having.
Nexus S (of course), i9020T, running CM7 before the trouble started. In order to load the OTA update I tried to flash back to stock 2.3.6. Flashed to 2.3.6 successfully (quickly went through setup process on 2.3.6, just to check.)
Then went back onto clockwork mod to install the ICS update. update went very quickly and I then tried rebooting the phone. Just get the ICS boot screen on an endless loop. Start the phone in fastboot mode, but now can't get to recovery (get "dead droidbug" image). Device doesn't show up when connected with USB on Mac, Windows or Linux. Ran ADB on computer and it says the device is not connected. Tried using Unbrickable, didn't detect the device. HOWEVER, when connected to Windows it shows up as "Android 1.0" in device manager, but says that there are no drivers isntalled for it, and none of the drivers from Android SDK work.
Device can still charge from USB, and I can get to fastboot on the device itself. If I can some how get the device to show up on USB I know I'd be set. Any thoughts?
Click to expand...
Click to collapse
i made this suggestion in another thread just a bit ago. I would try to slip a knife or something else thin under the tab in the phones usb port and push it up just a bit. My device was not being recognized or anything on my pc but would charge just fine. I did the afore mentioned and it works like a charm now.
other than that can't you push a recovery img through a terminal emulator on your phone?
I was able to connect to USB only a few minutes before this whole problem started, I even copied my backup folder from the device on to my computer. After the update, the drive disappeared.
On Windows it will appear as "Android 1.0" but says that drivers aren't installed, and the drivers installed from either Samsung or the Android SDK do not work for the device. I also tried using Odin as well as Unbrickable, which showed that it was connected, but failed when I tried pushing an image that way and said "Device not found".
I can get the device into Download mode in addition to fastboot, but neither can be recognized.
My phone did exactly the same connect very rarely and then only briefly, adb , fastboot and usb ( even sdcard on CWM) not working. I tried almost everything, even format all .....and then broke all....works only bootloader and CWM ...but what did not work anything ( adb, fastboot, usb) - I decided to go for repair because it was in warranty. Three weeks have passed since it is repaired....but they said that I will get back shortly. If you see that you can not do anything .... Think it take to repair....
When you start to have problems with usb will not take long and the phone will become unusable ! Get it repaired as quickly as you can , even if it's unlocked bootloader , if it have warranty will fix it....Good luck !
Surdu, I think you're right. I have arranged to have Samsung check it out, if they do wind up charging me for the repair hopefully it won't be too much.
filmgeekben said:
After checking lots of other recent posts, nothing has come close to the problems I'm having.
Nexus S (of course), i9020T, running CM7 before the trouble started. In order to load the OTA update I tried to flash back to stock 2.3.6. Flashed to 2.3.6 successfully (quickly went through setup process on 2.3.6, just to check.)
Then went back onto clockwork mod to install the ICS update. update went very quickly and I then tried rebooting the phone. Just get the ICS boot screen on an endless loop. Start the phone in fastboot mode, but now can't get to recovery (get "dead droidbug" image). Device doesn't show up when connected with USB on Mac, Windows or Linux. Ran ADB on computer and it says the device is not connected. Tried using Unbrickable, didn't detect the device. HOWEVER, when connected to Windows it shows up as "Android 1.0" in device manager, but says that there are no drivers isntalled for it, and none of the drivers from Android SDK work.
Device can still charge from USB, and I can get to fastboot on the device itself. If I can some how get the device to show up on USB I know I'd be set. Any thoughts?
Click to expand...
Click to collapse
that dead droidbug image is stock recovery. update your drivers(pdanet is an easy way how), fastboot a recovery, access the usb option in your newly flashed custom recovery, load a rom unto your sd storage, WIPE, then flash the rom. i think your problem was that you didnt wipe before flashing the ics rom. it was a big step between gingerbread and ics, you usually want to wipe when roms are that different.
simms22 said:
that dead droidbug image is stock recovery. update your drivers(pdanet is an easy way how), fastboot a recovery, access the usb option in your newly flashed custom recovery, load a rom unto your sd storage, WIPE, then flash the rom. i think your problem was that you didnt wipe before flashing the ics rom. it was a big step between gingerbread and ics, you usually want to wipe when roms are that different.
Click to expand...
Click to collapse
He can not update the drivers because when the phone connects to the computer nothing happens !!! And if you try to install PdaNetA300.exe or x64.exe you can not because you must have phone connected to it!
---------- Post added at 07:51 PM ---------- Previous post was at 07:46 PM ----------
If your computer detects the phone you can enter in the device manager and click rigt on the android drivers and update with : http://www.4shared.com/rar/_bgEMHqk/Nexus_S_Drivers_x86__x64.html
---------- Post added at 08:02 PM ---------- Previous post was at 07:51 PM ----------
filmgeekben said:
Surdu, I think you're right. I have arranged to have Samsung check it out, if they do wind up charging me for the repair hopefully it won't be too much.
Click to expand...
Click to collapse
Hey I'm very happy now!!!
Today I received the phone back after being in service....very curious : they left bootloader unlocked ....mention that so I sent and with CWM 5.0.2.0 installed ....
On receipt of repair writes that changed the screws and update the software ...with 2.3.6 but still it was installed before breaks!
And all that free because the phone was in warranty!
Hey ppl! I messed up my phone and I need some help. I have a G2x and I recently rooted it using the root.zip I found on one of the forum threads here. It worked fine and I flashed over to Eagleblood 2.5 and I didn't notice when I downloaded it that it didn't come with the google apps. I couldn't figure out how to get the google apps back into the phone since market wasn't installed. I tried downloading it but the phone kept telling me I don't have an SD Card being that I don't have an external one yet. Yes, I could have just downloaded it on pc and then transfered market apk via usb but I couldn't find the option to activate usb which was weird. Usually when you plug in your usb cable the driod icon pops up. So instead of flashing back using the backup I made on CWM I used nvflash and then used that LG tool to install V21E_00.kdz to install Gingerbread again. That's where everything messed up. I no longer was getting a cell signal and the battery icon had a ? in it. I assumed that the installation went bad to i did the process again with the nvflash and the V21E_00.kdz file. I got the same results again. I managed to get the wifi working again cause it wouldn't connect and downloaded cm7 7.1.0.1 to see if it would fix the problem. I flashed over and got the same results on cm7. No cell signal and battery icon screwed up. I gave up and did a full wipe and tried to install Gingerbread again. This time my pc wasn't reading my phone anymore when I connected it to the usb to use the LG tool to install V21E_00.kdz. Now my phone is in a cm7 boot cycle. If my phone is broken just tell me so I can dump it. My friend warned me about the G2x and I didnt listen cause I was in a hurry to get a nice phone. Any input and help would be greatly appreciated. If you guys need more info on anything please ask. If I can salvage this hunk o' junk I'm getting rid of it.
This phone is unbrickable damn near, have you tried the rom for recovery in development section? It will low level nvflash your phone to GB OTA 2.3.3 good luck.
http://forum.xda-developers.com/showthread.php?p=17258229
Sent from my LG-P999 using xda premium
Great! Thanks for the help. The phone is somewhat alive but I still have no cell signal and my battery icon has a question mark in it again. I was reading on that thread you linked me mentioning to do a firmware upgrade using the kdz file or LG Tool. Do I have to flash the firmware to get the cell signal working and the battery icon to work? If so, where do I get the firmware to flash?
To fix the boot loop cycle just boot back into clockworkmod recovery and do a factory reset, wipe cache, Dalvik cache, and then reboot and give it several minutes (first boot takes a little longer).
Or since you said you have a backup, just boot into clockworkmod, do a factory reset, format /system, and then restore your backup.
Again, the first boot always takes a little longer.
Thanks phburk I managed to get the phone working again with the flash.bat file from the link posted but I still dont have cell signal and battery icon has a question mark in it. I'm trying to download and use the LG Update Tool to see if that flashes the firmware to get the cell signal and battery icon working again.
The LG Update Tool fails at 30%. I can't get wifi on the phone to work and I have no cell signal and battery icon has a question mark still. This phone has to be broken. I see no fix in site for this problem. Anyone want to trade a GS2 for a G2x?
Kolcrok78 said:
The LG Update Tool fails at 30%. I can't get wifi on the phone to work and I have no cell signal and battery icon has a question mark still. This phone has to be broken. I see no fix in site for this problem. Anyone want to trade a GS2 for a G2x?
Click to expand...
Click to collapse
If you have a backup from a working configuration, try restoring that. Before you restore it, boot into clockworkmod and do a factory reset, and then format /system. THEN restore your backup.
After you restore allow the phone to reboot. If you still don't have signal then go to Settings > About Phone and see what it says for Baseband version.
Right now its going to show "unknown" for baseband. Might sound stupid but remove the battery sim card and sdcard for 5 minutes or so and then put them all back in and reboot. Try that after the factory wipes and installing a new rom. I've done that when I saw the "?" And no cell or data...
Sent from my LG-P999 using xda premium
I'll give it a shot. That's all I can do at the moment.
I no longer have a backup. The backup got corrupted that's why I've been trying other methods of restoring my phone. After running backup from CWM, the phone would reboot and stay on a black screen and flash. Screen would go dim then black like the backlight showing a black screen and dim again. That's all it kept doing and would not reboot. I tried doing a kdz flash but the pc wouldn't even recognize my phone when I plugged in the usb. (Yes, the drivers were installed and it was working. Previous to this I have kdz flashed twice. Phone has to be in S/W Update Mode by first pressing power button and as soon as the LG Logo shows up on the screen, let go of the power button and hold volume down.)
This resolved my reboot issue since I couldn't do a kdz flash.
http://forum.xda-developers.com/showthread.php?t=1248644
It got my phone working but still have unknown baseband and a question mark inside my battery icon.
**Update**
I read several threads regarding unknown baseband issue.
I've tried this method:
http://forum.xda-developers.com/archive/index.php/t-1332350.html
Since I already just did the first part by using the flash.bat file all I had to do was use the kdz flash. Unfortunately, my pc is still not recognizing my phone when I plug it in to the usb while in S/W Update Mode. I tried using this method above since the phone doesn't have to be in S/W Update Mode.
Outcome:
The LG Update Tool used in the method above kept stalling at 4%.
I read in another thread that this LG Update Tool doesn't work on Gingerbread. This LG Update Tool only works on Froyo.
So my next option was to use this method and try installing Froyo:
http://forum.xda-developers.com/showthread.php?t=1048274
This method just didn't work period. Since I don't have baseband or wifi working on the phone I can't get into market to download Rom Manager and I can't install File Expert which I have backed up on my pc. I already had the _ExternalSD directory so I made a sub directory /clockworkmod and another subdirectory /backup in the previous subdirectory. Made this on both the External and Internal sd cards and CWM tells me Couldn't open directory - No files found. So installing Froyo this way was out of the question.
I found this thread:
http://forum.xda-developers.com/archive/index.php/t-1037120.html
This is the stock Froyo version before the Gingerbread update as a zip file.
Unfortunately, when I tried to install the zip file from CWM it didn't work. I unzipped the zip file and found 2 .bin files which answers my question why CWM didn't install the zip.
I tried this method as well:
http://forum.xda-developers.com/archive/index.php/t-1332350.html
This method involves the flash.bat file to be done as a prerequisite before flashing to kdz. To my understanding, the flash.bat file fixes the partitions that most likely were screwed up on the phone and the kdz flash fixes the baseband (update/repair). I still haven't been able to get that kdz flash v1e to work simply because my pc won't recognize my phone into the usb when its in S/W Update Mode. I'm leaning towards the LG Update Tool to fix my baseband but I just need to downgrade to Froyo.
Don't know what else to do. I've been at it for 2 days and I'm seriously going to give up and just cancel T-Mobile.
If one of the methods involves installing apps, u can use adb to install them from ur computer without having to copy them to ur phone. But that's if u can get it into usb debugging mode.
Sent from my LG-P999 using XDA App
When you installed the rom, there should've been an extra package for Google apps that you should have flashed along with the rom as well, but you did so many different things, I don't know what to say.
You don't need your backup, it won't fix your baseband if it's corrupted or at all because no one has been able to get this phone to independently flash a baseband and the only way is through running the Gingerbread update either with KDZ or the LG updater.
I also went through hell more than once when I bricked my phone a few times. The first time I spent almost 2 weeks at it until I fixed it with the help of others here.
I also had the KDZ update stop at 4% over and over again which drove me crazy with anxiety. I was desperate so, after a few of those 4% hangups, I decided to reinstall a ROM and kernel just to see if the phone's baseband had installed anyway. Well, what a surprise, it did work.
You should try KDZ update again and, when it stalls at 4%, leave it for about 20 minutes then install a ROM based on Android 2.3.3, such as Weapon 3, fix permissions then reboot. That's what worked for me once. Another time, I did the same but I installed MTK drivers first then ran KDZ which stopped at 4% too but it worked too.
Read post #20 in this thread about how someone else did that successfully: http://forum.xda-developers.com/showthread.php?t=1180177
Here's where the MTK driver is: http://www.4shared.com/file/EqniU1Xt/MCCI_r_Firmware_Update_Driver_.html
Kolcrok78 said:
I'll give it a shot. That's all I can do at the moment.
I no longer have a backup. The backup got corrupted that's why I've been trying other methods of restoring my phone. After running backup from CWM, the phone would reboot and stay on a black screen and flash. Screen would go dim then black like the backlight showing a black screen and dim again. That's all it kept doing and would not reboot. I tried doing a kdz flash but the pc wouldn't even recognize my phone when I plugged in the usb. (Yes, the drivers were installed and it was working. Previous to this I have kdz flashed twice. Phone has to be in S/W Update Mode by first pressing power button and as soon as the LG Logo shows up on the screen, let go of the power button and hold volume down.)
This resolved my reboot issue since I couldn't do a kdz flash.
http://forum.xda-developers.com/showthread.php?t=1248644
It got my phone working but still have unknown baseband and a question mark inside my battery icon.
**Update**
I read several threads regarding unknown baseband issue.
I've tried this method:
http://forum.xda-developers.com/archive/index.php/t-1332350.html
Since I already just did the first part by using the flash.bat file all I had to do was use the kdz flash. Unfortunately, my pc is still not recognizing my phone when I plug it in to the usb while in S/W Update Mode. I tried using this method above since the phone doesn't have to be in S/W Update Mode.
Outcome:
The LG Update Tool used in the method above kept stalling at 4%.
I read in another thread that this LG Update Tool doesn't work on Gingerbread. This LG Update Tool only works on Froyo.
So my next option was to use this method and try installing Froyo:
http://forum.xda-developers.com/showthread.php?t=1048274
This method just didn't work period. Since I don't have baseband or wifi working on the phone I can't get into market to download Rom Manager and I can't install File Expert which I have backed up on my pc. I already had the _ExternalSD directory so I made a sub directory /clockworkmod and another subdirectory /backup in the previous subdirectory. Made this on both the External and Internal sd cards and CWM tells me Couldn't open directory - No files found. So installing Froyo this way was out of the question.
I found this thread:
http://forum.xda-developers.com/archive/index.php/t-1037120.html
This is the stock Froyo version before the Gingerbread update as a zip file.
Unfortunately, when I tried to install the zip file from CWM it didn't work. I unzipped the zip file and found 2 .bin files which answers my question why CWM didn't install the zip.
I tried this method as well:
http://forum.xda-developers.com/archive/index.php/t-1332350.html
This method involves the flash.bat file to be done as a prerequisite before flashing to kdz. To my understanding, the flash.bat file fixes the partitions that most likely were screwed up on the phone and the kdz flash fixes the baseband (update/repair). I still haven't been able to get that kdz flash v1e to work simply because my pc won't recognize my phone into the usb when its in S/W Update Mode. I'm leaning towards the LG Update Tool to fix my baseband but I just need to downgrade to Froyo.
Don't know what else to do. I've been at it for 2 days and I'm seriously going to give up and just cancel T-Mobile.
Click to expand...
Click to collapse
I was trying to root my brothers phone and i made a mistake.
I was on odin starting root the process by installing the FC17 update and having the phone in download mode.
When i clicked start on odin i thought the phone was supposed to go from download mode
to installing the fc17 update, but when the phone turned on and it acted normal i thought something was wrong.
When i looked on odin's message box it said something about the connection being void until something happened
(i cant really remember what it said) so i decided to unplug the phone.
After i unplugged the phone i decided to restart the rooting process.
This time the download mode screen was different and had a warning about installing a custom OS, but i just ignored it.
The problem is this time around odin wasn't recognizing my bro's phone and i don't know what the issue is.
I installed the phone's drivers and the usb ports are fine. I also tried this on a different computer but it didnt work on that one either
so i figured the problem is that something messed up when i unplugged the phone. Odin now doesn't recognize the phone when its in download mode and i need help.