Database Info

[Q] Error Code: 80072EFD

I have HTC MOZART, NODO Build, unbranded in indonesia.
Now my question is, once every 2-3 weeks, I got his kind of error. Basically The internet connection is gone when this happens, and I cannot update anything, unless of course I connect to zune in my laptop and use usb for internet connection shared from the laptop.
The only way to fix this AFAIK is by restarting the device (or remove the battery, and put back in)... hold the on button until off and turn on again is suffice though....
I dont mind restarting the phone within that interval, it is just weird and I tried to google and looked it up everywhere, I have not got the right explanation. Restarting the phone WORKS every time btw.
Anybody knows what this error is?
UPDATE:
I see that many others experience this and still no answer
http://answers.microsoft.com/en-us/...83cf0108/95bb01b5-9357-e011-8dfc-68b599b31bf5
Thanx

[Q] Problem with communication during GB update

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.

Bootloop, can't get it recognized in what I believe is fastboot mode

So my G8141 recently started rebooting whenever it would get disconnected from an audio out source via the headphone jack. That's been happening for about two days. Today, I had it plugged into my car, shut my car off, and my phone rebooted. And continued rebooting. Endlessly. Only way I managed to get it to shut off was Volume Up + Power + Camera (not sure what about that specific sequence did it, but I got one vibration followed by three vibrations, let go, and it was off). I got home, held Volume Down, plugged it into my Windows computer. The LED came on green, Windows found a new device...and nothing. Granted, I just wiped my desktop, so I don't have any of my android debug stuff installed, and I never got around to installing the drivers for this phone before now. So I downloaded the drivers from Sony, tried to install them, and...nothing. Windows says it can't find a driver for the device in the directory. Am I missing something, or is the phone FUBAR?
The phone already needs to go back to Sony for repair (the back cracked about a week after I got it)...do I have any shot of salvaging what's on it before sending it in? I don't think there's much if anything that's important, but I'd like to see what I can do before sending it in...because I bought the UK model from the UK and live in the US...so I have to ship it to the UK repair facility, per Sony help. Also, if I can get it working again, I'm not terribly worried about the back now that I have a case on the way, so I may just live with the cracked back, as long as the phone is stable.

Update: Plugged it into my work MacBook Pro, fastboot devices is giving me
Code:
???????????? fastboot
Same result whether sudo-ed or not.
---
Update 2: fastboot reboot-bootloader followed by fastboot devices lists an actual device. LED is blue. Progress?
Never unlocked the bootloader on this phone, so not sure what I can do from here...thoughts? I can't tell if it's a hardware issue or a software issue...device has updated a couple of times, so it's possible one of those updates introduced a bug. That said, the spontaneous reboot feels more hardware-y to me...reminds me of a PC with bad memory or something. If I could somehow get logs out of it, I suspect I'd find a kernel panic in there.
---
Update 3: Contacted Sony Support, they suggested using Xperia Companion to "repair" the phone. Currently doing what I believe is a stock reimage of the device using Companion. Next step is probably sending it to Sony UK :-/
Just a note for others that might be interested, green is download mode, blue is fastboot.

Well if you haven't unlocked bootloader just repair it? I don't really understand what the issue is about in your post.

Samsung Galaxy J3 Pro keeps on rebooting & has turned unusable!

Hi All,
The phone was problematic even after Reset(s) to factory condition. It used to reboot randomly launching apps, etc. I made all the Google Play updates successfully but the Samsung updates ( phone settings ) always failed.
Then I decided to use 'Samsung Smart Switch' ( Windows + Android Utility ) ( Official Downloads ). When I used the utility, it found some 2GB firmware update for the phone which was never listed from within the phone settings. I was quite hopeful but while making updates, it got hung at 'Preparing software environment for updates' for 2:30 hours. My computer's fans were running like anything so i got afraid & disconnected the phone. Probably, I halted the firmware updation in the middle & now I understand that. Since then the phone is almost unusable, rebooting every few seconds.
Undoubtedly, I am ready for the hard work & want to get my phone back to the usable state but am totally unaware as what are my options.
I also want to know the possibilities of getting it back to the usable state anyway.
Thanks for all the help & information!

A Firmware flash from Download Mode & ODIN did the trick. Thanks to the forum!

S7 930U (Snapdragon) ADB connection issues

So I had a broken USB port for a while, but since I want to pull data off my phone (including, if possible, the apps that I needed 2FA to enable like WhatsApp and so on, since I'm currently in Europe for the next 6-12 months and AT&T prepaid doesn't allow me to receive text messages or phone calls).
I bought a replacement daughterboard for the USB connector, and pulled the back of the phone off, removed the old USB connection board, and replaced it with this one. However, I've got some weird problems and I'm not sure if its hardware or software related.
When plugging the phone into USB, there's no indication on the telephone that the phone is charging, there's no indication that the phone has some connection to the computer, the computer doesn't display anything about the phone or allow me to access storage, and ADB can't find the device despite trying about 7 different methods and combinations of drivers, ADB programs, etc.
So I'd believe that my new daughterboard is either broken internally or some other issue ... except ODIN works flawlessly, as I got the inital step of loading the combo firmware to work without issue. (linked here: https://forum.xda-developers.com/t/root_method_rev_b-11_bootloader_using_combo_firmware.4374741/). But I can't get safestrap to work, because it relies on ADB, and ADB still doesn't have any way to connect to the device.
When I start the phone in download mode, I'm able to pull up a device with the Hardware ID USB\VID_04E8&PID_685D&REV_0100, but ADB doesn't recognize it. When I start the phone in any other method, the device doesn't register in device manager. It's a similar story when I tried reaching the phone with ADB from my linux desktop, as "something" exists in download mode, but adb has no ability to actually see the device or make a connection.
As far as avoiding obvious pitfalls, I enabled development mode / USB debugging / OEM unlock in the stock firmware I was running before, and also enabled dev mod/usb debug in the flashed firmware from that page.
It's quite possible that flashing the Combination firmware already wiped my data, as I'm not sure if it does it or not (after scouring the internet, it's pretty much the only option to get root with the B/11 bootloader so it was worth a shot), but ultimately I'd like to try and resolve this ADB issue so that I can actually finish the steps and see if it will work or not.
I just don't know what to troubleshoot next to try and get ADB to work.

To add on to this, I tried reaching out to AT&T to see if I can use my S8+ (VoLTE and all that jazz capable) to receive text messages while abroad here, but they won't let me use the phone even though I'm already abroad, since if it's not compatible with their network in the US it won't be compatible with their roaming network abroad. So I really do have to do the ole root trick.