Related
Alrighty,
So I keep trying to update my g2x through LG but I continuously get an error message that says, "Problem with communication between cell phone and PC", and then it never goes past 4%. Yes, I've downloaded the proper drivers, and have followed the prompts of disconnecting the phone, removing the battery, powering back and pressing restart (countless times). None of it works though. And no, my phone isn't bricking up on the SW update, so that thread doesn't really help me.
I've been doing some research and it seems that it just doesn't work for some phones, but I'm wondering if anyone here has been able to successfully troubleshoot this.
Yeah, I'm one of the unfortunate ones that got a bad phone a while ago, so I'm hoping I can find a way to make it work...
Thanks in advance!!
I have had the same problem. I have a G2x that I got off ebay. It was un-moded, running stock Froyo 2.2.2. I went to the T-Mobile / LG update site and followed the steps. The program actually worked the first time, it went through the whole update procedure and said it was complete. The phone restarted, but when it restarted it no longer recognizes the SIM card and there is a question mark for the battery symbol. When I go into the settings, it does not show a baseband version. I have tried to re-install using the update program, but it stops after 36% saying "Problem with communication between cell phone and PC". Any ideas?
npo123 said:
Alrighty,
So I keep trying to update my g2x through LG but I continuously get an error message that says, "Problem with communication between cell phone and PC", and then it never goes past 4%. Yes, I've downloaded the proper drivers, and have followed the prompts of disconnecting the phone, removing the battery, powering back and pressing restart (countless times). None of it works though. And no, my phone isn't bricking up on the SW update, so that thread doesn't really help me.
I've been doing some research and it seems that it just doesn't work for some phones, but I'm wondering if anyone here has been able to successfully troubleshoot this.
Yeah, I'm one of the unfortunate ones that got a bad phone a while ago, so I'm hoping I can find a way to make it work...
Thanks in advance!!
Click to expand...
Click to collapse
Mine did this the first time. This is where the phone is never commanded to boot into S/W update mode so at least this is not a step where it can be bricked, as no update has actually occurred yet.
This is how I fixed it and got mine to update. Use a different USB port on your computer. Yes there are different as some are on internal hubs. The update must have a direct USB port with no hubs in between. I also reinstalled the drivers through the LG Update program and not from the LG website. When I did this and plugged in my phone about eight new devices were detected and installed as opposed to about two the first time around. Also, make sure your phone is in debug mode in Android application settings.
Then make sure you disable any anti-virus programs and turn off the Windows firewall. Then use ctrl-alt-delete and close down any programs running. Also go to the taskbar and click on the up arror (if Windows 7) and right click on each icon and see if you can close it down. Also, unplug all other USB devices (even a mouse if you don't need it) as they can interfere with communications between the updater program and your phone. The only USB device I left connected to my computer was the keyboard.
The LG Updater must be run in Admin mode. If when you run it you get a Windows warning asking you if it is ok for this program to make changes to your computer then it is launching in Admin mode. If not right click the LG Updater icon by clicking Start>All Program>LGMobile Support Tool>LGMobile update. Right click the last item and run it in admin mode. Again this is assuming you are running Windows 7. Admin mode is not necessary for Windows XP.
If all the drivers get loaded properly and you are not on a flakey USB port then at 4% the updater instructs the phone to reboot into S/W Update mode and that is where the real magic happens if you are lucky.
coreycollins3066 said:
I have had the same problem. I have a G2x that I got off ebay. It was un-moded, running stock Froyo 2.2.2. I went to the T-Mobile / LG update site and followed the steps. The program actually worked the first time, it went through the whole update procedure and said it was complete. The phone restarted, but when it restarted it no longer recognizes the SIM card and there is a question mark for the battery symbol. When I go into the settings, it does not show a baseband version. I have tried to re-install using the update program, but it stops after 36% saying "Problem with communication between cell phone and PC". Any ideas?
Click to expand...
Click to collapse
Use another USB port and try again. At various points in the update the updater resets the phones usb port and it has to reconnect. If it doesn't connect don't do a battery pull. Just try removing the USB cable and reinserting it. If you hear the computer beep wait a bit and then click restart on the updater. Hopefully it should see the device this time and continue the update.
I managed to get up to the beta version of 7712, when i proceed to the next step to upgrade to mango, it goes through the motions, i've made sure i've signed in to zune by the way, and exited when doing this.
So it goes through the motions, says phone resetting, then the DOS screen goes off for short while. Then after a short while it opens zune up and says the stuff about agreeing to restore to a previous version!
I just wanted to check to see if this is supposed to happen or if anyone else has come across this and found a way to resolve this? Was i supposed to of unplugged the phone once the DOS screen went off? Or was i right to wait for zune beta to open up? Just wondering if anyone else has come across this and maybe resolved it?
When i unplug the phone and switch it back on its still on 7712?
Thanks for your help on this
Samsung
Omnia 7
Oh and handset isn't locked to any network, its network free
Evening people, im seeking some advice as im trying to update to mango 7720 from isv 7403
**step 7 of 9 installing update is where its failing the white bar at the top is only reaching half way then i step 1 of 2 appears with restarting your phone then the error code**
i have searched on most windows 7 forums and tried some tricks as suggested as time zone reserved space take sim out update drivers virus/firewall off uninstall/reinstall zune nothing is working ..called microsoft they are not familiar with the code...any other ideas or tip i would be grateful..its been 72hours i been at it.
Anyone come across this code? thank you for any advice
i met the same problem, anh havent solved yet.
Im trying the last time, try to wait for the phone restarting step (7of9) patiently
Hi folks,
Has anyones Z3 started randomly rebooting on its own?
Its done it 4 times in the last hour. Battery life is at 30%
Thanks
Mine none have this issue. Try using pc companion or flashtool repair your phone.
Sent from my D6653 using XDA Free mobile app
KurtHoyle said:
Hi folks,
Has anyones Z3 started randomly rebooting on its own?
Its done it 4 times in the last hour. Battery life is at 30%
Thanks
Click to expand...
Click to collapse
No I haven't seen that on mine, and I have run my battery down numerous times. As suggested above, I would look at restoring your phone or factory resetting it
I have gone through 3 Z3s and on 4th now, all were replaced for cosmetic reasons, none had any stability issues. All were rock solid no crashes.
Try removing all non factory installed apps, if that does not work try resetting to factory defaults. If that also fails then maybe your firmware/NAND got corrupted... happened to me with an HTC One X before (NAND). I highly doubt the worst case scenario though.
Thanks everyone. Ill do a factory reset today and see if that helps
Cheers
Bumping this thread to see if anyone else has had this issue... I've Googled, and some users have experienced this issue. So far I have factory reset my phone, but that has yet to work.
I'm getting random crashes, sometimes using the phone and sometimes while it's just sitting there... It happens like at least 10-15 times a day and I've only had my phone for like 4 days.
Toneekay said:
Bumping this thread to see if anyone else has had this issue... I've Googled, and some users have experienced this issue. So far I have factory reset my phone, but that has yet to work.
I'm getting random crashes, sometimes using the phone and sometimes while it's just sitting there... It happens like at least 10-15 times a day and I've only had my phone for like 4 days.
Click to expand...
Click to collapse
Same. Struggling.
i had my first random reboot yesterday phone was just sitting there.
hasn't done one since.
I've had the phone for 4 days (Software 23.0.A.2.93) and it randomly reboots 2-3x a day.
I've had the same problem as well. Sent it to Sony for repair. They said it had something to do with the software. Asked for more information, they said an app was causing it (I use normal applications: FB, Line, reddit, skype, dropbox). Sony said they "repaired" my phone by erasing all my data and re-installed the firmware. Happened AGAIN TODAY. BTW it shows up as a "system restart" in the diagnostics menu. Is this the same for everyone experiencing this? Btw i used the pc companion to repair my phone as you have mentioned before sending it to Sony; that DIDN'T work either
I'm seeing this maybe once every 1-2 days, after reading the program list above I'm trying removing Skype to see if that's causing issues.
Ian
ke7in said:
I've had the phone for 4 days (Software 23.0.A.2.93) and it randomly reboots 2-3x a day.
Click to expand...
Click to collapse
Suggest you to update to .98 or even .105, do a factory reset and check how it works afterwards.
sxtester said:
Suggest you to update to .98 or even .105, do a factory reset and check how it works afterwards.
Click to expand...
Click to collapse
So you presume that its a problem with software and not hardware is that correct?
kiminoir said:
So you presume that its a problem with software and not hardware is that correct?
Click to expand...
Click to collapse
Yes, correct. I'm running on .98 since day one and never had any unintended reboots at all. As we speak, my Z3C runs since about 10 days.
Sent from my D5803 using XDA Free mobile app
sxtester said:
Yes, correct. I'm running on .98 since day one and never had any unintended reboots at all. As we speak, my Z3C runs since about 10 days.
Sent from my D5803 using XDA Free mobile app
Click to expand...
Click to collapse
How do I do that though? There are now more issues now. The necessary phone applications themselves are now crashing (ie. contacts, clock, walkman) I've included a photo for you. My current plan is to send my phone back to Sony for repair once again. The problems seem to appear out of nowhere.
Thanks in advance
kiminoir said:
How do I do that though? There are now more issues now. The necessary phone applications themselves are now crashing (ie. contacts, clock, walkman) I've included a photo for you. My current plan is to send my phone back to Sony for repair once again. The problems seem to appear out of nowhere.
Thanks in advance
Click to expand...
Click to collapse
Please use the search function, it's been explained a countless times already: http://forum.xda-developers.com/z3/general/ftf-stock-firmwares-xperia-z3-models-t2886061
I did a repair (still on .93) and it seems ok since yesterday but we'll see. Here are the instructions Sony sent me:
Thank you for contacting Sony Xperia™ Online Support.
We have an extended guide that should help you fix the issue on your phone, please follow the instructions carefully:
Visit this link:
sonymobile dot com/us/tools/pc-companion/
Click on Download PC Companion
Run the software and install it
Turn the phone off and disconnect it from the computer
1. No matter what the program says do not connect the phone until you complete step 9
2. In the welcome screen you will see the different modules available for you including the "Support Zone" option. Click on "Start" below it.
3. On the next page Click on "Start" under "Phone Software Update"
At this point if you get an error stating that "Unable to install update components" or "Server is busy" , then please proceed to step 12
4. The program will say that there is no phone connected. Click on the option below that reads: "Repair my phone" the program will issue you a warning about the content that you will lose during the update
5. Choose the option to continue.
6. The program will issue a final message warning you of possible data lost during the update. Click on the checkmark and then on "Next".
7. After that, the program will download the necessary information (5 to 6 minutes) and it will present you with a list of phones.
8. Choose your phones model from the list then click on "Next" then you will see a new section telling you how to connect the phone. (don't connect it yet)
At this point the phone must be off and disconnected from the PC.
9. Connect the cable to the PC not to the phone, then while pressing and holding the indicated button (in the steps on screen an specific button will be shown for you to press on the phone) connect the cable to the phone and keep holding the indicated button until the program says "the update of your phone has started..." (in some cases a message of "Installing drivers" will appear before the message of "the update of your phone has started..." is shown.)
10. If you failed to follow the steps correctly the phone will turn on and it will request that you "Proceed with the following steps, slide down the notification bar", If this happens disconnect the phone from the cable, turn it off and repeat from step 9).
11. If the phone is connected properly, PC Companion will proceed with the update ( It will tell you to let go of the back key) then wait for the update to finish and follow instructions on screen to disconnect the unit.
Dear Customer,
12. If "Unable to install update components"
1. Close PC Companion
2. Install Java from: java dot com
3. Start PC Companion again and try to do the software unlock process once more.
Note: If you wish only to update the unit wait for the program to open and then select the quick link on the upper left corner that says "Update Phone/Tablet" and follow the instructions to perform the update. (the PC may request for the phone to be placed in Mass Storage mode. Do this by going into Settings>Xperia>Connectivity>USB connection mode)
Click to expand...
Click to collapse
Same here.
i have the same problem but i have rooted min with Glade rom, works fine except for the random reboot.
Hi all,
2 days ago I purchased brand new Z3 and today the device started restarting every 15-20 minutes. There are no external factor that seems to be causing it – the phone restarts without being in use. What I’ve notice is that it’s doing a “Soft Reboot”.
Some additional info – after the phone was turned on for first time it asked for an Software Update to Android 5.0. After installation it rebooted and asked for another update. The heaviest app that is currently running is Facebook.
I would really appreciate any suggestions as I would like to avoid waiting for two weeks for the service centre to do something, that I can also do.
Thanks!
KurtHoyle said:
Hi folks,
Has anyones Z3 started randomly rebooting on its own?
Its done it 4 times in the last hour. Battery life is at 30%
Thanks
Click to expand...
Click to collapse
...
I'm on stock rooted ROM 20H sep 2018. Last time I checked (just now) this is still the latest verion.
However my H910 keeps bugging me about new update available from AT&T.
Does that happen to you guys?
It didn't give me any info about versions and so on.
Should I proceed?
I got it too. Came here to see if it was just me. I'm on H910 Oreo stock rooted.
Warning: DO NOT try to silence the nagging by blocking the notifications. AT&T/LG will treat "quit bothering me" like "go ahead, have your way", and simply go ahead and try to install the update without even bothering to ask you next time. If you're running RootedStock, you'll end up in a slow semi-bootloop where Android boots, you'll have about 3-5 minutes, then it will forcibly install the update, reboot, you'll end up in TWRP, and when you reboot to system (or power off, then power up later), the whole cycle will repeat.
I'm not sure how robustly my solution worked, but here's how I broke out of it. So far, about 15 minutes after rebooting, it seems to have worked. Since I'm writing this AFTER seemingly fixing the problem, I'm writing it from memory, and can't say with 100% certainty which step was actually the one that fixed the problem for me. I actually began the process of installing Titanium backup about a half-dozen FOTA-reboot cycles before tripping over another post here that advised deleting /cache/FOTA. Titanium Backup might, or might not, be an essential element of my apparent success. I honestly don't know. If you own it, use it... you have nothing to lose. If you don't already own it, try just deleting /cache/FOTA first from TWRP's file manager and see whether it works (temporarily or permanently).
Anyway... here's the approximate path to slaying the FOTA beast:
1. I installed Titanium Backup from Google Play. It actually took two reboot cycles to do this... you REALLY have to be ready to unlock the phone, launch Google Play, search for Titanium, and trigger its installation while standing a few feet from your wifi AP for it to finish the download and begin installing it before the next forced-update attempt begins. When it does, swear violently. It'll make you feel a tiny bit better.
1b. When FOTA forces the reboot into TWRP, try deleting /cache/FOTA before rebooting. It might work to temporarily slay the FOTA beast, it might not. If it does, it'll save you about 30 minutes of FOTA-reboot misery for the remaining steps. Feel free to repeat this after each of the following steps. It can't hurt.
2. On the next cycle, launch Google Play the moment your phone finishes booting, and go back to Titanium Backup. Hopefully, it'll be installing. With a little luck, installation will finish before FOTA begins. Then sigh, and let FOTA waste another 5 minutes of your time.
3. On the next cycle, launch Ti backup, give it permanent root permission, and give it permission to do everything it wants. Then, try to launch Google Play, search for Titanium, scroll down, select Ti Backup pro key, and try to initiate installation before FOTA kicks in yet again.
4. On the next cycle, launch Google Play, search for Titanium, scroll down, select the pro key, and begin installation if it isn't already downloading and/or installing. 99% likely you'll end up going through another round of FOTA misery.
4b. If FOTA is still forcing reboots up to this point, repeat step 1b before step 5.
5. On the next cycle, launch Titanium Backup, give it any additional permissions it wants, then select Backup/Restore, scroll down to "FOTA Update 8.0.0", and freeze it.
5b. If FOTA kicks in again, repeat step 1b.
If, despite deleting /cache/FOTA, then freezing FOTA Update 8.0.0 using Ti backup, then deleting /cache/FOTA again, it's still happening... well, then my solution didn't work for you (and possibly not for me. I'll start breathing again normally if my phone is still working normally tomorrow).
Anyway, hopefully this will help someone. I suspect a lot of people running RootedStock Oreo are going to get stung by this. I'd guess that more than a few v20 owners actually bought theirs long after AT&T's previous forced update, and have never actually HAD to deal with blocking forced updates with their current ROM.
It's entirely possible that purchasing Ti backup (I don't think the free version can freeze apps) will be essential for the H910 going forward if you want to keep using what was, prior to yesterday, the newest rooted-stock Oreo ROM without having AT&T's FOTA harass you every few hours (or wipe your phone and reflash once someone releases a newer build based on the current update). Trust me, you can't swat it away forever. I went through this forced-update nagging bull**** years ago with my Motorola Photon. Someday, when you least expect it, the dialog will come flying at you when you're driving and trying to select a song using Amazon Music, or in the middle of a phone call, or semi-distracted, or scrolling down a web page while the phone is bogged down because it's grinding its wheels in the background preparing to harass you about updating again, and you WILL accidentally click "ok" & have your life go down the toilet for the next few hours until you're able to dig yourself out of the mess.
Bite the bullet, and freeze FOTA Update 8.0.0 now, while you can still do it without burning an hour of your life waiting for reboot after reboot.
For those finding their way here, make sure to back up in the brief period of time before you get hamstrung if you can't freeze the process. I am/was bone stock H910 and after ATT forced the update on me, my phone now won't finish starting up and functionally boot-loops now until I pull the battery.
It will start, get to the home screen, I might get 5-15 seconds of actual usable time with the phone before it freezes, goes back to the bootscreen and will get warmer and warmer and give me less and less time until it freezes in the middle of the ATT logo. Tried pulling SD card and SIM card, just in case. The sim card removal bought me enough time to get the phone to tell me it was "finished updating" but upon attempting to power down and start re-inserting cards, the phone locked up and bootlooped.
No idea what this update is for but it seems to have killed my phone rather handily, beware.
FWIW, airplane mode does not stall the update either.
bitbang3r said:
Warning: DO NOT try to silence the nagging by blocking the notifications. AT&T/LG will treat "quit bothering me" like "go ahead, have your way", and simply go ahead and try to install the update without even bothering to ask you next time. If you're running Roote
Bite the bullet, and freeze FOTA Update 8.0.0 now, while you can still do it without burning an hour of your life waiting for reboot after reboot.
Click to expand...
Click to collapse
Hope I'm not jinxing myself, but this appears to have worked for me.
I have gotten a "update could not be installed" popup, which I'm taking to be a good sign.
Still annoying, since I have auto-updates turned off.
Ugh, it popped up again. Confirmed, FOTA is still frozen.
It initiated the update for me on its own. Luckily I noticed and plugged it in or it would have died and maybe bricked the phone.
I don't notice a difference. Same Android version (8.0) same security patch (Sept 2018). The ATT version might have gone from H to I.
Yep, it started nagging me again, too. Goddamn it, this is really starting to piss me off.
Okay, on mine I think when I delete /cache/FOTA while in TWRP, it might not actually be deleting the folder.
I deleted the folder in recovery mode, then rebooted and went straight to X-plore file manager. The FOTA folder was either still there, or it just recreated itself on boot. I deleted it again in X-plore and it's now been working since my previous post.
Fingers crossed.
I just rooted a H910 yesterday, and this morning the same "slow boot loop" with the update started. I tried different things, and what so far seems to have worked was:
1. Entered TWRP recovery (from the last "update cycle." (Not like I had a choice.)
2. Wiped everything and re-installed Oreo, and all other zip and img files back to the way I originally set it all up.
3. After phone was booted up, I DID NOT have a SIM card in it, nor did I enable WiFi.
4. Temporarily skipped all the Google sign in stuff.
5. Enabled Developer options, and turned off "automatic system updates." (Not Google Play Updates!)
6. Re-booted phone and then confirmed that the above setting still showed "off."
7. Enabled WiFi and connected.
8. Set up Google account and other misc settings.
9. Restored a backup that I had made prior to the phone doing the update reboot loop, but was careful to uncheck settings. I did not use Titanium Backup. I used the built in one.
NOTE: This is not my daily driver phone. It is meant to be used as an emergency backup phone in the event that my regular phone (Samsung Galaxy S Series) falls in a canal or gets run over by a truck. (Or City Bus)
So far so good. I will use the phone for the day and check again the following morning to see if it starts the forced update. I will check back here in a few days and let everyone know what the end result was.
My theory is that if the phone does not have a chance via cell data or WiFi to get any FOTA updates prior to me turning off the "automatic system updates" that is in the Developer Options, it will never check in with AT&T's update server.
I am not sure about this, and if someone else knows, please correct the following:
I don't think AT&T "pushes" updates out. At least the type of updates we are talking about. I believe the software in the phone periodically polls an AT&T update server, and "pulls" any update at a schedule time, or time interval. My working theory is that turning off the automatic system updates will disable this automatic check, or polling routine. If it already has an update that it downloaded prior to turning off automatic system updates, its too late.
Thanks for everyone's input on this in advance.