Develop Bugs

TMobile US 3.6.390 Upgrade

I just wanted to split this discussion from the leaked ROM thread. From what I have gathered and understand, this newest update is the US equivalent of the Europe 2.51 update. I know many of you have already upgraded your devices to this, so users like me who are late/slow to the game, aren't there yet. In my case I still had the stock 3.6.160 up until last night. I know many have had the concern about 2.51 and not being able to go back. Has US TMobile done us a favor by releasing this OTA update? It would seem to me that this is now a sanctioned update, so anything from here on out would be officially supported and updated. It also seems that if the US and Europe version are the same, any thing that works for 2.51, would work for the US version. Like the 3.4.2 Nandroid backups. It should just be a matter of a simple restore and everything should work, correct? Sorry if I seem a little off. Prior to this device all of mine have been HTC devices which didn't have the locked bootloader. So this concept of of firmware/roms is a little off to me. I haven't had a chance to test any of this yet, I just want to know if the theory is correct. If I'm wrong please point me in the right direction. I'd like to be able to contribute to this forum constructively, especially as I am in charge of deploying DEFYs on our corporate network. The nice part of this is my Director is all for rooting our phones. He looks at in the manner that we need to do what needs to be done. If a phone gets bricked in the process, well we will just buy another. Warranty really isn't a concern.I'd like to get playing on it this weekend, especially with Froyo.

runeblade said:
It would seem to me that this is now a sanctioned update, so anything from here on out would be officially supported and updated.
Click to expand...
Click to collapse
Nope.
The only update for the US DEFY is an incremental one (still 2.1) and it has only been released to 500 or so users according to the offical Tmo forums.
They are testing that one now.
The official froyo for DEFY is probably still a couple/few months away from public release, but let us hope they get it out faster.
More info in this thread:
http://forum.xda-developers.com/showthread.php?t=931212

The Incremental has been released to the wild. Both of my Defy's received it OTA. I also know this is not an OS upgrade. Still stuck at 2.1. But my understanding was that the US update changes the boot loader to the same one as the Europe 2.51 update. If this is indeed true it would mean that we should be able to boot any of the 2.2 Roms out there without using the European update. Thats what I'm trying to confirm/Deny.

I registered for the "testing update", and received it this morning. Overall the phone is so much smoother. I'm now using Blur instead of ADW or LP. As a matter of fact all scrolling is smoother. The homescreens, app drawer, lock screen, widgets. Everything. Before the update if I was on Wi-Fi and sent a MMS I would get a delay, and have both icons in the notification bar for Wi-Fi and 3G, but now they send instantly, and I only have the Wi-Fi icon. Battery seems to be lasting longer today too which is one of the included functions. I'm impressed overall with what they did.

I was on of the very first few to get the Official 3.6.360 and while yes some things have improved. I decided to do a wipe after I had installed it. And I notice something interesting. No more root, Z4Root (using 1.3.0 which is what I used the first time I rooted this phone) no longer works, unexpected failure. So yea the have changed something... I run down the ADB route and see what that turns up.
I will have go the ADB route to get back to rootville.

darknetone said:
I was on of the very first few to get the Official 3.6.360 and while yes some things have improved. I decided to do a wipe after I had installed it. And I notice something interesting. No more root, Z4Root (using 1.3.0 which is what I used the first time I rooted this phone) no longer works, unexpected failure. So yea the have changed something... I run down the ADB route and see what that turns up.
I will have go the ADB route to get back to rootville.
Click to expand...
Click to collapse
I noticed the same thing. No more root access after the update. I tried to re-root with z4root, super 1 click to no avail. Not familiar with the ADB process. Kinda nervous to be honest. First Android phone and all. Had it 2 weeks. Hopefully a new 1 click method comes from one smarter than I soon.

That's interesting. I noticed right off the bat that Z4Root no longer worked, so I ran Super1click, and that worked fine for me. The only thing I haven't done is wipe the phone, but at this point it doesn't sound like I'm going too.

runeblade said:
That's interesting. I noticed right off the bat that Z4Root no longer worked, so I ran Super1click, and that worked fine for me. The only thing I haven't done is wipe the phone, but at this point it doesn't sound like I'm going too.
Click to expand...
Click to collapse
Did you need to do anything special with Super1click, or was it as simple as z4root? Can you just run it, and wait for it to finish? I mean I read some stuff that you may need to do the "turn debug off, turn it on, turn it off" thing with it because some phones give a "waiting for device". If you did certain steps other than just clicking root can you share? Thanks.

Nope. Just downloaded it, ran as admin and let it do its magic. Short and simple.

runeblade said:
Nope. Just downloaded it, ran as admin and let it do its magic. Short and simple.
Click to expand...
Click to collapse
How long did it take? I tried it, but it keeps hanging on "waiting for device..."

Mine as well. Just keeps saying waiting. It got further once but stuck in a loop and came back to waiting. I unmount the sd, put it in debug, not sure what usb mode to use or where this admin option is found though. Quite frustrated since the bloatware I froze with Titanium Backup is back and all my root permissions are one. Any help for a newAndroid guy would be awesome.

Make sure when you have it connected to your machine that you are in Portal mode, as well as making sure that your machine is actually picking up the MDB interface. I know with mine it took a couple of plug ins to get it to actually install correctly.

bobbyphoenix said:
How long did it take? I tried it, but it keeps hanging on "waiting for device..."
Click to expand...
Click to collapse
I think your problem might be that you're running it in USB "None" mode (as you would if running ADB). This is a common mistake. With Super1Click, you have to run it in "Portal" mode.
Plug your phone into the computer. You'll get "USB Connection" in your notification bar at the top. Then pull the notification bar down and click "USB connection". Click "Motorola Phone Portal". Then make sure "USB Debugging" is on (in Menu key > Settings > Applications > Development). Now run Super1Click as administrator. Click "Root".
It still takes a while in between steps, especially at the various "Waiting for device" stages. But if you did all the initial steps above, it should work properly. Just BE PATIENT.

cargohook said:
I think your problem might be that you're running it in USB "None" mode (as you would if running ADB). This is a common mistake. With Super1Click, you have to run it in "Portal" mode.
Plug your phone into the computer. You'll get "USB Connection" in your notification bar at the top. Then pull the notification bar down and click "USB connection". Click "Motorola Phone Portal". Then make sure "USB Debugging" is on (in Menu key > Settings > Applications > Development). Now run Super1Click as administrator. Click "Root".
It still takes a while in between steps, especially at the various "Waiting for device" stages. But if you did all the initial steps above, it should work properly. Just BE PATIENT.
Click to expand...
Click to collapse
Everyone keeps saying 'as administrator'. There is no option in S1C for that. Nor on my phone. How do I execute this as admin? Am I just being dumb?
Edit: Does this mean as computer admin? Like head honcho on the pc?

This is based on the assumption you are using windows 7 or vista. You right click on the program and in the drop down menu select Run as Administrator. It will then open up the program.

slipknotfn said:
Everyone keeps saying 'as administrator'. There is no option in S1C for that. Nor on my phone. How do I execute this as admin? Am I just being dumb?
Edit: Does this mean as computer admin? Like head honcho on the pc?
Click to expand...
Click to collapse
Exactly, "Head Honcho of the computer"! Do what runeblade said.

cargohook said:
I think your problem might be that you're running it in USB "None" mode (as you would if running ADB). This is a common mistake. With Super1Click, you have to run it in "Portal" mode.
Plug your phone into the computer. You'll get "USB Connection" in your notification bar at the top. Then pull the notification bar down and click "USB connection". Click "Motorola Phone Portal". Then make sure "USB Debugging" is on (in Menu key > Settings > Applications > Development). Now run Super1Click as administrator. Click "Root".
It still takes a while in between steps, especially at the various "Waiting for device" stages. But if you did all the initial steps above, it should work properly. Just BE PATIENT.
Click to expand...
Click to collapse
Yep. That was my problem. Didn't have it in portal mode. As soon as I did, it went fast. It went through a bunch of steps. I see it says "Running psneuter... ROOTED" It should be almost done. It's on "Reading OS Version properties..." now, and it's been there for like 10 minutes now.

cargohook said:
Exactly, "Head Honcho of the computer"! Do what runeblade said.
Click to expand...
Click to collapse
What if one were running, say, XP? Then head honcho would work? I have no computer here that has 7 or Vista. Just my old, trusty laptop. Thanks for all your help.
And which version of S1C? The one for 2.51 or the 1.63 version?

The 2.51 version.

runeblade said:
The 2.51 version.
Click to expand...
Click to collapse
where is that version? I'm using 1.6.3 and it's still stuck on "reading OS" thing.

[Q] Please help a Noob

OK. I think I've done my due diligence. I've scrubbed the forums for 2 days, I've googled it and I still can't figure out what I'm doing wrong.
Friend gives me this rooted LG OGP. Awsome! Works great! Then AT&T or LG sends an OTA update that bricks it :crying:. Read Aryan1312's sticky thread in this forum and get all pieces together. By now I have the 3.8.1 drivers AND the newest 3.10.1 drivers, LGFlashTool 1.8.1.1023, along with the newest 10P TOT file. I got the Flashtool to stop asking for PW and I think I'm ready to go.
But then . . . Plug my phone in and Device Management doesn't know what to do with phone. Reinstall drivers pack from LG website. Still no dice. Hmm. Phone is in Team Win Recovery Project v2.6.3.0 recovery screen (I guess that's what it's called) and computer doesn't know what to make of it. Hmm.
Maybe I can put it onto a microSD card and copy stuff over to phone? Maybe flash a different ROM through TWRP? Let's try that. I copy files over to the external SD card, put it into the phone, restart phone, hello TWRP, Advanced-File Manager option, WHY CAN'T YOU SEE THE EXTERNAL SDCARD??? Isn't it supposed to be there under /extSD?? It's time to ask for help.
Question: How do I get my Win7 PC to see the phone as a removable drive/external drive/whatever you call it so that I can get this info over?
I know that I have to change Port #'s after Win7 sees the phone. I just can't get there . . . yet.
- What I've tried:
Reinstalled drivers (both versions) and restarted between trying to plug phone in.
Tried installing phone drivers manually. Still doesn't mount as external HD as far as Win7 is concerned.
Called friend to ask his opinion. He doesn't remember and tries to tell me this is why Apple is "better".
Scoured the web to see what to do. Found articles about this same thing happening and all point to Stickied Post on this XDA forum
I did RTFM and am still lost.
---- Sorry for the long post, I just thought that people who wouldn't mind helping would appreciate the extra info.

Drivers
landran said:
OK. I think I've done my due diligence. I've scrubbed the forums for 2 days, I've googled it and I still can't figure out what I'm doing wrong.
Friend gives me this rooted LG OGP. Awsome! Works great! Then AT&T or LG sends an OTA update that bricks it :crying:. Read Aryan1312's sticky thread in this forum and get all pieces together. By now I have the 3.8.1 drivers AND the newest 3.10.1 drivers, LGFlashTool 1.8.1.1023, along with the newest 10P TOT file. I got the Flashtool to stop asking for PW and I think I'm ready to go.
But then . . . Plug my phone in and Device Management doesn't know what to do with phone. Reinstall drivers pack from LG website. Still no dice. Hmm. Phone is in Team Win Recovery Project v2.6.3.0 recovery screen (I guess that's what it's called) and computer doesn't know what to make of it. Hmm.
Maybe I can put it onto a microSD card and copy stuff over to phone? Maybe flash a different ROM through TWRP? Let's try that. I copy files over to the external SD card, put it into the phone, restart phone, hello TWRP, Advanced-File Manager option, WHY CAN'T YOU SEE THE EXTERNAL SDCARD??? Isn't it supposed to be there under /extSD?? It's time to ask for help.
Question: How do I get my Win7 PC to see the phone as a removable drive/external drive/whatever you call it so that I can get this info over?
I know that I have to change Port #'s after Win7 sees the phone. I just can't get there . . . yet.
- What I've tried:
Reinstalled drivers (both versions) and restarted between trying to plug phone in.
Tried installing phone drivers manually. Still doesn't mount as external HD as far as Win7 is concerned.
Called friend to ask his opinion. He doesn't remember and tries to tell me this is why Apple is "better".
Scoured the web to see what to do. Found articles about this same thing happening and all point to Stickied Post on this XDA forum
I did RTFM and am still lost.
---- Sorry for the long post, I just thought that people who wouldn't mind helping would appreciate the extra info.
Click to expand...
Click to collapse
1. Is the first pic with the phone connected to the pc?
2. If yes, have you tried to manually update drivers, while in device manager
3. I know that this is going to sound funny but have you tried a different USB port. The reason I ask is I had the same problem LG Optimus M and the phone was down for a couple of days. I tried everything and was about to call it quits but for some reason when I changed USB port the computer saw the phone and I was back in business. I am not saying that will 100% work but it is worth a try.

TheMighyLoki said:
1. Is the first pic with the phone connected to the pc?
2. If yes, have you tried to manually update drivers, while in device manager
3. I know that this is going to sound funny but have you tried a different USB port. The reason I ask is I had the same problem LG Optimus M and the phone was down for a couple of days. I tried everything and was about to call it quits but for some reason when I changed USB port the computer saw the phone and I was back in business. I am not saying that will 100% work but it is worth a try.
Click to expand...
Click to collapse
Yes I have. I think I did figure it out though. I put the device into "download mode" and my computer could see, and communicate, the phone.
To put my phone into "download mode" I did the following:
I connected the phone to the computer physically with USB cable
I turned phone off.
I pressed BOTH volume buttons and held the power button while phone was attached to computer.
With BOTH volume buttons still pressed, I released the power button.
The phone screen was black with a little dialog box in the middle saying "download mode"
I could then use LGFlash Tools to flash Stock AT&T TOT file back into phone. Took 519 seconds to complete the stock flash.
New problem arises, After flash, I do NOT have any 3G/4G signal. I can use the phone to make and receive phone calls and text messages, but I CANNOT use mobile internet unless I have it connected via wifi.
I installed the Debloated ROM and "tried" to flash 980 Baseband.zip but when I tried to install baseband, CWM gave me a permission error and said install failed. I haven't been able to use mobile internet since. Any help???
-- Again, sorry for the lengthy post. I figured that I might not be the only person who has gone through this. I see a lot of viewers to the thread so I think other people might be having same troubles as me.

landran said:
New problem arises, After flash, I do NOT have any 3G/4G signal. I can use the phone to make and receive phone calls and text messages, but I CANNOT use mobile internet unless I have it connected via wifi.
I installed the Debloated ROM and "tried" to flash 980 Baseband.zip but when I tried to install baseband, CWM gave me a permission error and said install failed. I haven't been able to use mobile internet since. Any help???
-- Again, sorry for the lengthy post. I figured that I might not be the only person who has gone through this. I see a lot of viewers to the thread so I think other people might be having same troubles as me.
Click to expand...
Click to collapse
It sound like you need to manually set the APN. Do a Search for your provider.. ie AT&T T-Mobile the setting is under Network/Tethering & Networks/ Mobile networks/ Access point name/ Hit Menu Button and New APN

You are the MAN / WOMAN!! Thanks for the help. That fixed it.
For posterity and to help another "noob" stuck in my case later (maybe months down the line)
This is what I've done up until now in plain text:
Used LGFlashtool to flash AT&T stock "10k" build
Went into Settings Icon>General>Developer Options>check off "USB Debugging"
Used "E980 Universal Root" from forums to gain Root access (verified with "Root Checker" from Playstore)
Used FreeGee to get TWRP recovery installed (rebooted into recovery with "QuickReboot" from Playstore).
Used TWRP recovery to install "E980 Baseband.zip" from forums
Factory Reset
Setup new phone and input APN settings (located in Settings Icon>Networks>Tethering & Networks>Mobile networks>Access point names>Menu button "New APN"/input carrier values/Menu button "Save")
Now that I know how to get back here, I'm going to scrap the stock ROM and try to do this whole process with a custom ROM. . . and another flash-a-holic is born. The learning journey continues.

Welcome:beer:
*KCCO*2SHAYNEZ*E980*

That is what this forum is for.
I have been helped out a lot from the group and I just thought it was time to pay it back. It is good to hear that you got it up and running. But one last word of advise BACK UP, BACK UP, BACK UP, and when that is done, back up the back up to the computer.

[Q] [x-post from LG G3] D851 unroot / restore to stock

I recently picked up a D851 (TMobile). I rooted it, but did not replace the ROM or install a custom bootloader.
Last weekend, the phone started randomly rebooting. Watching logcat via adb showed me several random apps throwing sig11s, after which the phone would give up and reboot. Cycle repeats.
This looks like a hardware issue, as the apps that crash change on each boot cycle.
I arranged with TMobile to swap the device, but they cautioned me that the phone must be returned to an unrooted state.
I've had a hell of a time with it from here. My first try was to install the LG drivers and the PC Suite under a Windows VM, as I do not run Windows at home. Enabling USB passthrough for the phone to the VM let Windows see the phone, but the LG drivers would invariably fail with 'Device cannot start. Code 10.'. Likewise, the PC Suite couldn't find the phone.
Next step was to throw together some spare hw and install Windows 7 on that (a desparate move, to be certain. ). The LG drivers can now recognize the phone, so that's a definite plus. The LG PC Suite, though, claimed that my phone could not be upgraded. Wonderful.
Next step was to try this tutorial: http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html . I was able to get further with this method, but as it begins to flash SYSTEM, it pauses, and then dies with 'We can't communicate with Phone'. End result - I now have a soft bricked phone. On the phone, I see the port - COM41 - appear, and the usb animation starts to spin ... and after a few seconds, stops. It's at this point that Flashtool throws the Can't Connect error.
I next tried following this tutorial: http://forum.xda-developers.com/showthread.php?t=2785089 to flash a KDZ. The newer LG Flash tool used here can't create a connection to my phone for flashing.
I've run into a wall here. Any ideas on where to go next? I need to reset this phone back to a working stock state so that I can send it back.

http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4

BACARDILIMON said:
http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4
Click to expand...
Click to collapse
Also - as silly as it sounds, make certain you're using the USB cable that came with the phone. This has solved problems for a lot of people when trying to revert to stock.

etawful said:
Also - as silly as it sounds, make certain you're using the USB cable that came with the phone. This has solved problems for a lot of people when trying to revert to stock.
Click to expand...
Click to collapse
I wasn't initially, but I did switch to it last night. Still no go.
I suspect it's either the phone itself (see above: re suspected hw failure), or the PC in question (nVidia chipset on this old motherboard, and I've had more than a few problems with adb talking to phones on nVidia motherboards). I'm going to try Bacardilimon's suggestion tonight, on a PC that has *nothing* nVidia-related in it, before I throw in the towel. As it is, the failing phone needs to be back to TMO by the middle of next week, so I'm all but out of time to resolve this.

Drake Maijstral said:
I recently picked up a D851 (TMobile). I rooted it, but did not replace the ROM or install a custom bootloader.
Last weekend, the phone started randomly rebooting. Watching logcat via adb showed me several random apps throwing sig11s, after which the phone would give up and reboot. Cycle repeats.
This looks like a hardware issue, as the apps that crash change on each boot cycle.
I arranged with TMobile to swap the device, but they cautioned me that the phone must be returned to an unrooted state.
I've had a hell of a time with it from here. My first try was to install the LG drivers and the PC Suite under a Windows VM, as I do not run Windows at home. Enabling USB passthrough for the phone to the VM let Windows see the phone, but the LG drivers would invariably fail with 'Device cannot start. Code 10.'. Likewise, the PC Suite couldn't find the phone.
Next step was to throw together some spare hw and install Windows 7 on that (a desparate move, to be certain. ). The LG drivers can now recognize the phone, so that's a definite plus. The LG PC Suite, though, claimed that my phone could not be upgraded. Wonderful.
Next step was to try this tutorial: http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html . I was able to get further with this method, but as it begins to flash SYSTEM, it pauses, and then dies with 'We can't communicate with Phone'. End result - I now have a soft bricked phone. On the phone, I see the port - COM41 - appear, and the usb animation starts to spin ... and after a few seconds, stops. It's at this point that Flashtool throws the Can't Connect error.
I next tried following this tutorial: http://forum.xda-developers.com/showthread.php?t=2785089 to flash a KDZ. The newer LG Flash tool used here can't create a connection to my phone for flashing.
I've run into a wall here. Any ideas on where to go next? I need to reset this phone back to a working stock state so that I can send it back.
Click to expand...
Click to collapse
There is a link in the general thread on how to return to stock including a method using twrp. It's a sticky thread at the top I've never done the twrp method myself but it can more than likely be done without a computer. Twrp can be installed via Playstore if you don't already have it

BACARDILIMON said:
httx://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4
Click to expand...
Click to collapse
Holy hell. That site's links are absolutely infuriating. Anyone who puts each and every download link for software referenced by a howto behind separate timed appearance links that you have to ALSO enter an annoying captcha to enable should be shot out of a cannon - or, at the very least, have their howto ignored by the rest of the world.
Suffice it to say, the quality of that page doesn't give me much confidence that this will work any better than what I've tried already. Since I've already wasted a crapload of time on this project, and more on following those damned links, I'll give it a try tonight, but I'm not going to hold my breath.
Is the author of that page an XDA member? If so, please let me know who he is, so I can berate him personally. Thanks.

Toneman07 said:
There is a link in the general thread on how to return to stock including a method using twrp. It's a sticky thread at the top I've never done the twrp method myself but it can more than likely be done without a computer. Twrp can be installed via Playstore if you don't already have it
Click to expand...
Click to collapse
I'd consider doing that, except as I mentioned, the G3 in question disconnected during a run of Flashtool, rendering it without a working OS to boot to. The phone now boots straight to download mode. The good news is, it's now officially unrooted. The bad news is, it's also officially bricked until I can get an OS flash to work.

Drake Maijstral said:
Holy hell. That site's links are absolutely infuriating. Anyone who puts each and every download link for software referenced by a howto behind separate timed appearance links that you have to ALSO enter an annoying captcha to enable should be shot out of a cannon - or, at the very least, have their howto ignored by the rest of the world.
Suffice it to say, the quality of that page doesn't give me much confidence that this will work any better than what I've tried already. Since I've already wasted a crapload of time on this project, and more on following those damned links, I'll give it a try tonight, but I'm not going to hold my breath.
Is the author of that page an XDA member? If so, please let me know who he is, so I can berate him personally. Thanks.
Click to expand...
Click to collapse
OK I gonna keep it real with you. You can either enter the captcha and fix the issue or throw the phone away. Yes he is a member and for every phone that is out their he has its own page doing this for us. If you can't fix your phone with his method then it not the method but you. I have used this for many bricks. It works and it works great. Sorry if he making you do a little typing but like I said u can use his method or keep trying the other methods. Good luck
NOTE 4

BACARDILIMON said:
OK I gonna keep it real with you. You can either enter the captcha and fix the issue or throw the phone away. Yes he is a member and for every phone that is out their he has its own page doing this for us. If you can't fix your phone with his method then it not the method but you. I have used this for many bricks. It works and it works great. Sorry if he making you do a little typing but like I said u can use his method or keep trying the other methods. Good luck
NOTE 4
Click to expand...
Click to collapse
After going through the painful process of clicking his links, I found that everything I downloaded is the same thing I already had, except for Flashtool - lgg3root's is actually older. Even the TMO firmware for my phone and the dll are both exactly the same, and I checked by running md5sum on them.
But hey, it must be me. There's clearly no other technology-related cause for this issue. I obviously don't know how to follow a howto, right?
Thanks for 'keeping it real'.

Drake Maijstral said:
After going through the painful process of clicking his links, I found that everything I downloaded is the same thing I already had, except for Flashtool - lgg3root's is actually older. Even the TMO firmware for my phone and the dll are both exactly the same, and I checked by running md5sum on them.
But hey, it must be me. There's clearly no other technology-related cause for this issue. I obviously don't know how to follow a howto, right?
Thanks for 'keeping it real'.
Click to expand...
Click to collapse
See we agree.
NOTE 4

BACARDILIMON said:
See we agree.
NOTE 4
Click to expand...
Click to collapse
Not likely.
In any case, it failed again. The video he did gave me the exact same steps I followed elsewhere, and unsurprisingly, it failed with 'We can't communicate with Phone', after beginning the flash process. There is something else wrong here, though I'm not certain if the failing phone is at fault or the PC in question is causing the issue. To be crystal clear, the flash process starts, and then, at a random point during the flash, it completely stops, and Flashtool eventually gives up and throws the aforementioned error.
Any other ideas? If not, I'm going to have to try another PC to rule that out as the culprit. Sigh.

Mine gave the same error as well as couldn't communicate with server but the flash process continued running and the phone rebooted took about 3 minutes u learned not to touch any of the popups on the screen during flash and sorry I missed the part about no OS I thought you were booting to recovery... Driving while reading not the best idea

Toneman07 said:
Mine gave the same error as well as couldn't communicate with server but the flash process continued running and the phone rebooted took about 3 minutes u learned not to touch any of the popups on the screen during flash and sorry I missed the part about no OS I thought you were booting to recovery... Driving while reading not the best idea
Click to expand...
Click to collapse
Nope, the phone is definitely not doing anything - the usb animation on the G3 completely stops before Flashtool throws the error.
And damnit, quit reading while driving. You can do that later.

Moved the hdd Windows is installed on to another PC with a different chipset. After it updated drivers, I tried again. Flash proceeded partway, then died. Reset phone, Flashtool reststarted flash from scratch, flash died at 15%.
15% is interesting. While I've seen the flash die at various points, 15% is the one that was most often repeated. This tells me the failure follows the phone, not the PC - which makes sense, as the phone has a suspected RAM failure.
At this point, it appears that flashing this phone is impossible due to faulty hw. Hopefully TMO (and eventually, LG) will accept the faulty phone back with no OS, because there's no way an OS is being written to this device ever again.

Thank you for answering

yanowman said:
Thank you for answering
Click to expand...
Click to collapse
No problem. There's nothing I hate more than stumbling across a thread where the OP has the same problem I have, only to find it was never updated with the solution.

Good luck man let us know what tmobile says

LG flashing Tool problem

I rooted my G3 using iRoot while having Lollipop 5.0 installed. I have just received my update from LG for Marshmallow. When I tried to do the update it told me that my phone was rooted so I can't get it. I un-rooted my phone, and tried to put everything back to the way it was, but no go. They still said my phone is rooted. The problem is that I can't do a hard factory reset. I get a message "secure booting error ...".
So after reading up on it a bit, I realized I needed to flash a stock ROM through my computer. I downloaded all that I needed, and installed LG Flashing Tool 1.8.1.1023 on my Windows 10 computer, following all the directions exactly (including replacing MegaLock.dll). The program installed, but when I wanted to run it, it told me that it couldn't find MegaLock.dll, and then asked for an ID and Password. I uninstalled it and reinstalled it many times using slightly different versions, but I had the exact same problem each time. Then I decided to try and install it on a Windows 7 machine, and it worked. So it seems that something is keeping it from working on the Windows 10 computer. Can anyone help me with this, or maybe there is another way? Maybe the dll file has to be placed somewhere else? Maybe a different MegaLock.dllis needed that is compatible with Win10? Maybe a different program? I have no idea. Any and all help would be appreciated.
Thank you.

http://forum.xda-developers.com/lg-g3/help/answer-windows-8-8-1-detecting-lollipop-t2967574
what varient do u have

TheMadScientist420 said:
http://forum.xda-developers.com/lg-g3/help/answer-windows-8-8-1-detecting-lollipop-t2967574
what varient do u have
Click to expand...
Click to collapse
My computer recognizes the phone, that's not the problem. It's purely the program, I can't run it. It doesn't open.

i see try older versions of the program try googling lg flash tool do you have the megalock.dll
---------- Post added at 03:45 PM ---------- Previous post was at 03:42 PM ----------
im sorry i just really read in full i had the issue to when i upgraded to win 10 i ended up going back to win 7 too things just wernt going well with 10 also had trouble with flash tool always failing never restoreing i was a pain i thought i messed my phone up and it ended up bein win 10 my pc has the secure boot and crap on it it even makes it a pain to dual boot ubuntu up so i just run 2 machines on my tv

A Possible Solution
alwaysdiving said:
I rooted my G3 using iRoot while having Lollipop 5.0 installed. I have just received my update from LG for Marshmallow. When I tried to do the update it told me that my phone was rooted so I can't get it. I un-rooted my phone, and tried to put everything back to the way it was, but no go. They still said my phone is rooted. The problem is that I can't do a hard factory reset. I get a message "secure booting error ...".
So after reading up on it a bit, I realized I needed to flash a stock ROM through my computer. I downloaded all that I needed, and installed LG Flashing Tool 1.8.1.1023 on my Windows 10 computer, following all the directions exactly (including replacing MegaLock.dll). The program installed, but when I wanted to run it, it told me that it couldn't find MegaLock.dll, and then asked for an ID and Password. I uninstalled it and reinstalled it many times using slightly different versions, but I had the exact same problem each time. Then I decided to try and install it on a Windows 7 machine, and it worked. So it seems that something is keeping it from working on the Windows 10 computer. Can anyone help me with this, or maybe there is another way? Maybe the dll file has to be placed somewhere else? Maybe a different MegaLock.dllis needed that is compatible with Win10? Maybe a different program? I have no idea. Any and all help would be appreciated.
Thank you.
Click to expand...
Click to collapse
I had problems with LG Flashing Tool the first time I tried to flash stock after upgrading my system OS to Windows 10. I finally got it to work by changing the compatibility mode for application file to Windows 8. I successfully flashed back to D85510L_00.KDZ after making the change I just mentioned.

Abort said:
I had problems with LG Flashing Tool the first time I tried to flash stock after upgrading my system OS to Windows 10. I finally got it to work by changing the compatibility mode for application file to Windows 8. I successfully flashed back to D85510L_00.KDZ after making the change I just mentioned.
Click to expand...
Click to collapse
Thanks, but I tried that already. Didn't work. In the end I transferred everything to my wife's Windows 7 computer and and did the flashing there. Everything ran as smooth as can be.

lg g4 connection to server failed

this is the error message i get when trying to flash the stock rom onto my lg g4. i bought a phone that had the google account locked out, so i figured i could get around that somehow. when i got to the part where the settings needed accessed in the vision menu, it was greyed out, so i did some more research. this led me to the lg flash tool i used today.
i went to this forum and downloaded all the items needed and installed the drivers, then put the phone into download mode and opened the tool as an administrator. i browsed to the file leaving it at cdma, diag, 33000. i hit cse flash to wipe it and it verified the phone connection. then it said connection to server reset. please try again later and made me exit. i tried again, then this time it it got to upgrading sw and went to 5%, then counted 6, 7, 8, and 9, and then said upgrade stopped due to an error. i have a log if that would help, it looks like it is having trouble extracting the file. i got the US99110c_03.kdz because that is my model of phone, but also tried an 815 in case it was a bad file. any suggestions are much appreciated.

looks like i have figured out what happened. finally, i got a tool started which gave me a thorough error message. it said the new rom was older than the one already there. now, the one dated 28 aug 15 is the newest one i can find anywhere. any ideas where i can find it?

sfzombie13 said:
looks like i have figured out what happened. finally, i got a tool started which gave me a thorough error message. it said the new rom was older than the one already there. now, the one dated 28 aug 15 is the newest one i can find anywhere. any ideas where i can find it?
Click to expand...
Click to collapse
Hey bud, did you ever figure out the issue? I'm having the same problem and can't get it working again. Same exact issue as you. https://forum.xda-developers.com/tm...bootlooped-t3654568/post73357821#post73357821