Related
So.... Can anyone confirm if the steps are the same like s3?
Shouldn't be in this section, you should know that...
Sent from my SPH-L900 using Tapatalk 2
Thread moved to Q&A.
can you do this without rooting?
No need for root to repair.
As long as the default samsung password works, it should be the same.
But I don't have my phone in hand yet. So I cannot confirm if default password work
So yes, I'm now on boost mobile with the note2.
For some reason this phone wouldn't do the ota activation or sprint zone activation trick.
I had to manually insert everything in qpst.
Working good now
Now need to work on mns
trim81 said:
So yes, I'm now on boost mobile with the note2.
For some reason this phone wouldn't do the ota activation or sprint zone activation trick.
I had to manually insert everything in qpst.
Working good now
Now need to work on mns
Click to expand...
Click to collapse
Trim, how were you able to get in and repair MEID? I used *#7284# to set the UART and USB to modem, but once I do that, Windows won't recognize the device. I do see a notification about "Qualcomm CDMA Technologies MSM" but no driver can be found.
If I set UART/USB back to PDA I can get Windows to recognize the device using mskip's device drivers.
trim81 said:
I had to manually insert everything in qpst.
Click to expand...
Click to collapse
by that you are referring to the data profiles, right? but how did you get your ESN allowed on boost, were you able to have customer service do it for you or did you actually spoof the ESN?
##3424# use that ibstead
After youre in everything is straifht foward
trim81 said:
##3424# use that ibstead
After youre in everything is straifht foward
Click to expand...
Click to collapse
What version of QPST are you using? I have build 378 and it's only good enough to establish the com port for QXDM. If you have a more recent version could you share it with us?
I'm not at home now... But look into the s3 forum, the repair method is the same, I used alpineman method.
But this phone is easier, in that no dfs is needed... Everything is repairable with qpst.
Like mentioned tho. I'm not sure if the towers or down or not.. But it will never take an ota activation both via profile 0 or wifi.
I ended having to input the settings manually via qpst
I won't go into spoon feeding, and step by step, it's already published - - look into the galaxy s3 forum
I used the same program versions as that thread
Edit
I used qpst 2.7 build 378
Can someone with knowledge please help create a voicemail. Apk hack for boost?
Still having problems
trim81 said:
Edit
I used qpst 2.7 build 378
Click to expand...
Click to collapse
Still cannot get into my phone.. hopefully you or someone else has more knowledge about this..
I installed the Toolkit drivers, then I put ##3424# into the phone. I pressed "Qualcomm USB Setting" and switched it to DM+MODEM+ADB and clicked OK, then switched UART to "CDMA MODEM", then plugged in the phone. At this point Windows correctly installs the drivers and I have a "SAMSUNG Mobile USB Serial Port (COM7)" under the device manager, and no abnormal status icon, so the driver installed correctly. But when I go to QPST I always see "No Phone" and the phone is never detected. I also get the same results if I put UART on "PDA" instead.. doesn't make a difference. Because QPST is in "No Phone" I can't get into to program it.
I also tried another way, *#7284*, then putting UART on MODEM and USB on MODEM, this time, Windows detects the device as a "Qualcomm CDMA Technologies MSM", not as a Samsung device. I installed the generic Qualcomm driver manually and QPST does detect the phone properly and I can get in, but I CANNOT read any of the crucial NVItems such as ds_mip_ss_user_prof (NVItem 466), QXDM always returns CFS_ERROR BAD PARAM, and I can't read these settings using DFS either. I tried writing it in DFS "blind" (since I cannot read to see
if it wrote correctly) but I still have no 3G, only 1xRTT and voice.
I have also tried many different USB cables and different Windows computers, always the same result. This is a brand new phone from Sprint, never been activated, is that the reason?
This is really frustrating, anyone out there seen this type of thing before? Spent days on this already.
Chanman said:
Still cannot get into my phone.. hopefully you or someone else has more knowledge about this..
I installed the Toolkit drivers, then I put ##3424# into the phone. I pressed "Qualcomm USB Setting" and switched it to DM+MODEM+ADB and clicked OK, then switched UART to "CDMA MODEM", then plugged in the phone. At this point Windows correctly installs the drivers and I have a "SAMSUNG Mobile USB Serial Port (COM7)" under the device manager, and no abnormal status icon, so the driver installed correctly. But when I go to QPST I always see "No Phone" and the phone is never detected. I also get the same results if I put UART on "PDA" instead.. doesn't make a difference. Because QPST is in "No Phone" I can't get into to program it.
I also tried another way, *#7284*, then putting UART on MODEM and USB on MODEM, this time, Windows detects the device as a "Qualcomm CDMA Technologies MSM", not as a Samsung device. I installed the generic Qualcomm driver manually and QPST does detect the phone properly and I can get in, but I CANNOT read any of the crucial NVItems such as ds_mip_ss_user_prof (NVItem 466), QXDM always returns CFS_ERROR BAD PARAM, and I can't read these settings using DFS either. I tried writing it in DFS "blind" (since I cannot read to see
if it wrote correctly) but I still have no 3G, only 1xRTT and voice.
I have also tried many different USB cables and different Windows computers, always the same result. This is a brand new phone from Sprint, never been activated, is that the reason?
This is really frustrating, anyone out there seen this type of thing before? Spent days on this already.
Click to expand...
Click to collapse
Yes!!! I did it. I thought I would share what worked for me in hopes that this will help others.
I ended up using *#7284* and then putting UART and USB both on MODEM. As I mentioned in my previous post, this causes the device to be detected as "Qualcomm CDMA Technologies MSM". I had to install a specific generic Qualcomm driver, which I have included in this post. After that, since I was only able to use QXDM/QPST/DFS to write the voice specific settings and HA profile (not passwords), the thing that ended up working for me was CDMA Workshop's free NVItem writer. Using this tool I was not able to read the crucial NVItems (466 and 1192), but I was able to write them. I did a byte-for-byte identical write, cloning the NVItems from the original phone (which I was able to read from). After the tool indicated the items were successfully written I rebooted the phone and everything worked!
guys I'm stuck, I'm not able to connect to my galaxy note 2 no matter what I try.I followed Chanman's post and was still unable to connect to my note 2 using the driver he provided. Are there any special steps I need to take because it's just not working for me.
I used all drivers and programs in the galaxy s3 post.
Follow that guide
iwin2000 said:
guys I'm stuck, I'm not able to connect to my galaxy note 2 no matter what I try.I followed Chanman's post and was still unable to connect to my note 2 using the driver he provided. Are there any special steps I need to take because it's just not working for me.
Click to expand...
Click to collapse
The driver I included in my post is a Win32 driver only. If you have Windows 7 64-bit it won't work. I had to use this particular driver on a 32-bit Windows XP machine. Sorry for not including that information in my post. You might be able to make a virtual machine to get the driver to load. I wasn't able to find a 64-bit Qualcomm CDMA MSM driver.
Ok I finally got this freaking phone connected and readable after messing it with with 1.5 days and I figured I would let you guys know.
What I had to do what go in to *#7284# mode, set both UART and USB as PDA (NOT MODEM), then go into Qualcomm USB Settings at the bottom and select either of the two options at the bottom (RNDIS+DM+MODEM or DM+MODEM+ADB, as long as it has DM in it it will connect).
As a result of this you will get a series of new devices connecting to your PC (visible on Device Manager), including one called SAMSUNG Mobile USB Serial Port (COM #), not Qualcomm CDMA MSM driver (if you get Qualcomm then you did it wrong, I wasn't able to connect to the phone using Qualcomm drivers posted above, although I'm not refuting Chanman's claim that it worked for him, I just couldn't get it working myself)
Now the drivers for the Galaxy Note 2 that you need installed are available here: http://org.downloadcenter.samsung.c..._L900_Note_II_Samsung_USB_Driver_v1_4_6_0.exe
I believe if you get the Galaxy Note 2 toolkit, those are the same drivers, but I prefer to get them directly from the source to avoid any issues.
Now I will continue by following the directions in the galaxy s3 thread as trim81 suggested, and I will report back (hopefully in a few hours).
Thanks for everyone's support.
iwin2000 said:
Ok I finally got this freaking phone connected and readable after messing it with with 1.5 days and I figured I would let you guys know.
What I had to do what go in to *#7284# mode, set both UART and USB as PDA (NOT MODEM), then go into Qualcomm USB Settings at the bottom and select either of the two options at the bottom (RNDIS+DM+MODEM or DM+MODEM+ADB, as long as it has DM in it it will connect).
As a result of this you will get a series of new devices connecting to your PC (visible on Device Manager), including one called SAMSUNG Mobile USB Serial Port (COM #), not Qualcomm CDMA MSM driver (if you get Qualcomm then you did it wrong, I wasn't able to connect to the phone using Qualcomm drivers posted above, although I'm not refuting Chanman's claim that it worked for him, I just couldn't get it working myself)
Now the drivers for the Galaxy Note 2 that you need installed are available here: http://org.downloadcenter.samsung.c..._L900_Note_II_Samsung_USB_Driver_v1_4_6_0.exe
I believe if you get the Galaxy Note 2 toolkit, those are the same drivers, but I prefer to get them directly from the source to avoid any issues.
Now I will continue by following the directions in the galaxy s3 thread as trim81 suggested, and I will report back (hopefully in a few hours).
Thanks for everyone's support.
Click to expand...
Click to collapse
Happy this worked for you. I believe this is the standard way to get into the phone (these instructions are all over Youtube and the S3 forum). The reason why I had to do things differently is that when I tried that approach, even though the devices show up as "Samsung" without any errors in Device Manager, QPST and DFS show "no phone" or can't connect to the port, even though it's there. Maybe I just got unlucky, or you got lucky, or both
So I'm playing with the brand new Sprint S3 with LJ7 stock rom and is stuck at the very first step. Managed to get the COM port opened in the PC for Samsung USB diag mode, however, the DFS 4.0.2 and QPST failed to connect. I can choose the right port to open in DFS, but whenever I try to read from the phone, it shows researching device forever, and I'm certain the spc code is correct (got from the app getmymsl, and I could use it to edit the data file). In QPST, there is no device listed under that COM port (normally you should see the phone listed as SURF****)
Searched and followed this instruction: http://forum.xda-developers.com/show...7&postcount=14 but still not working for me.
Just now I tried install the samsung usb driver and DFS 4.0.2 in a freshly installed windows 7 (64bit) machine, so the only COM ports installed/opened are the samsung's, but still the same symptoms.
I've heard people talking about downgrade ROM and radio for those software to work, but I also saw people directly using DFS for the newer ROM. What did I do wrong then? Please help.
BTW, I dial ##3424# to bring out the diag mode panel, and tried different combinations such as:
Modem / dm+modem+adb
PDA / dm+modem+adb
modem/ rmnet+DM+modem
pda/ rmnet+DM+modem
all gave me the same issue: having the COM port opened but the device could not be recognized.
However the phone was recognized fine as a media device.
procter said:
BTW, I dial ##3424# to bring out the diag mode panel, and tried different combinations such as:
Modem / dm+modem+adb
PDA / dm+modem+adb
modem/ rmnet+DM+modem
pda/ rmnet+DM+modem
all gave me the same issue: having the COM port opened but the device could not be recognized.
However the phone was recognized fine as a media device.
Click to expand...
Click to collapse
Try doing a factory reset. I find that after you flash the phone once using ##DIAG#, you won't be able to flash it a second time after the firmware upgraded. That's just been my experience though. You would still be able to see the port, but it won't read/write. Instead use *#PATH# instead.
I'm hoping someone can help. I have an LG G3 D855 phone and is factory unlocked and running Lollipop 5.0. When I first got the phone (second hand), I was able to connect the phone via USB to my PC and was able to transfer files back and fore no problem. Until about 3 weeks ago, I am now unable to do this. The PC won't recognise the phone at all, all the USB connection does is charge the phone and I can see no option to get the phone to change to file transfer mode.
I had a look at Storage in the settings menu and I don't have the three dots that some people have spoke about. I have factory reset the phone and this hasn't fixed it.
I have tried using a different USB cable, this was the same. The drivers are installed (phone was recognized before). I have also tried the LG Suite, again same result. I also had a look in Device Manager for ACER something or other and this wasn't there.
I am currently having to use Bluetooth to transfer files back and fore to my PC and this is a bit slow. I'm assuming that an update LG have done has somehow broke the USB settings. I am also unable to root the phone (tried this before the USB stopped working and nothing worked) and possibly go back to KitKat 4.4.2 to even try that.
My phone has software version V20u-EUR-XX, Kernel Version 3.4.0 and build number LRX21R.A1439960697. There is no update available for my phone in the Software Update center.
After quite a bit of searching, it seems that this is a common issue but I have not found a solution to this. Can anyone help? Is there any firmware or software that I can try?
Thanks.
Assuming the OS is Win8/8.1 or Win10, have you already tried this?...
[How to fix] Windows 8/8.1/10 is not detecting my LG G3 device
http://forum.xda-developers.com/lg-g3/help/answer-windows-8-8-1-detecting-lollipop-t2967574/post57373374#post57373374
... or tried the suggestions in this thread?: http://forum.xda-developers.com/lg-g3/help/lost-usb-connection-mode-t2847857
Thanks for the reply. I am using Windows 7 Home Edition 64 Bit and had had a look for the ACER Composite ADB Interface in Device Manager and it wasn't there. Post #18 in the thread you linked to, I have no idea what kdz file I would need. Does this method need the USB to working?
Thanks for the reply and help.
I have D85520T_00.kdz and D85520U_00.kdz files. Can someone tell me if these are OK for my phone (and latest) and what the differences between the two are (apart from the file names?) Thanks again.
I couldn't tell you what the differences are between software revisions, only that 20u is newer. And I believe 20w is the latest available. I would probably try reinstalling the latest drivers from LG...
http://www.lg.com/us/support/software-firmware
... then again check to see if your PC recognizes the phone. If the "Charge phone--> Tap for more USB options" notification doesn't appear after installing the latest driverset, I'm not sure what else you could try. The LG Flash Tool needs to be able to communicate w/ the device when it's in Download Mode. You might be able to find something in the [Guide] LG G3 Stock Firmware (Go Back to Stock) KDZ & TOT Method thread related to the same problem you're having.
http://forum.xda-developers.com/showthread.php?t=2785089
Just a quick update, can't even get the phone into download mode. I press volume up, insert the USB cable in to the PC and all I get is the battery charging icon. I'll have a further look this weekend - not good so far!
Thanks again for the replies and help.
Firmware W seems to be flashable only via TWRP or ClockWorkMod just now?
I have been able to get the phone into Download Mode a few times (not all of the time) and when I run LG Flash Tool, it just tells me that the phone isn't connected. I'm going to assume that the USB port is in someway defective. Can't think of anything else.
Have you tried w/ a different PC and/or OS? Have you tried connecting the phone via different USB ports (USB 2.0 compared to USB 3.0 or vice-versa)? And I assume you've already installed the latest driverset from LG?...
http://www.lg.com/us/support/software-firmware
Yes, I got into Download Mode once or twice on the laptop. I'm using LGMobileDriver_WHQL_Ver_4.0.3. I have tried USB 2 ports on both my Laptop & PC. I've tried driver 3.81 as well.
OK, got a new USB Charger port fitted just in case it was the port that was wrong and it's still exactly the same! I did a factory reset and have setup the phone for now. During the factory reset, it does pop up with Updating Android and has 169 updates. If anyone here has the LG G3 and has it working file transfer wise, can you tell me what version of the LG USB drivers you are using? Is it possible an LG update has caused this?
Thanks.
It's fixed!!! I think there was an update yesterday for Android Devices or Services, can't remember which was made available yesterday, installed that, reconnected the phone to the computer just a few minutes ago and it has finally been recognised! I can finally transfer files between the phone and the PC.
It was an LG update that has fixed this.
At last.
I'd like to say thank you for all the replies and help.
Hi Guys,
A weird one here for you, I'm already contemplating throwing my phone at a wall that's how long I've been trying to fix it.
I have a LG G3 D855 Gold 32gb model purchased via Kogan in Australia.
The unit is now on Android 5.0 (no updates available for 5.1+) - Software Version V20i-SEA-XX with Build number LRX21R.A1440645925.
This phone is non-rooted with stock ROM etc.
So the issue at hand, I upgraded my Win7 PC via the upgrade option to Win10 to retain my games/files etc.
Now when connecting the phone to the PC it only goes to charging mode and I am unable to click on it within the drop-down to change it to anything else.
I have tried LG G3 drivers, Googles generic drivers, ADB suite drivers. I am unable to adb find the phone, I do not have an Acer Composite device in Device Manager.
Win 10 keeps saying the device is not recognised/malfunctioned.
Tried different cords, double checked the connector on the phone for any dust specs etc.
My PC refuses to work with any driver I have thrown at it, however in each scenario with various drivers, warnings still persist in Device Manager.
Some of the drivers force the phone to connect/reconnect and cause the "ping" sound each time it disconnects and reconnects (with malfunction warning prompts).
This is on Win10 with 64bit Home edition.
I am at my wits end and can't think of anything I haven't tried beyond a factory reset of my phone (hoping not to at this stage as I'm thinking it's driver-related).
It won't let me tether or anything via USB also, same goes with USB debugging, no change.
Lastly which may also help narrow it down, with the phone plugged in BEFORE it gets to the OS, I can change between PTP/MTP and USB charge, however once the Win10 OS loads up, it disconnects/malfunctions and lists Charge Only.
And yes, this phone can connect on my Win7 small PC which I use for testing crap out on.
Any ideas guys?
Let me know if any log files or anything is required.
At this stage I am unable to do a root to the phone (due to adb issues etc) nor can I connect to the internal phone system unless I use in the in-built file explorer.
Edit: *SOLVED*
Ok so turns out the issue is, and this is just my case, my motherboard has various utilities, one of which is a USB 3.0 boost option.
When I did an upgrade to Windows 10, it somehow screwed up various programs on my PC including registry etc.
I reinstalled the particular utility (I was actually trying to fix my graphics clock etc so happy coincidence) which also re-installs the USB 3.0 Boost software which in turn has fixed my USB Ports.
So if you have a custom built PC (my Motherboard being a Rampage 4 Formula). Check the Mobo Utilities/Drivers for any conflicts.
I have the exact same problem, and I can't seem to find a solution for months now. It's really annoying and depressing
nicholsonr said:
Hi Guys,
A weird one here for you, I'm already contemplating throwing my phone at a wall that's how long I've been trying to fix it.
I have a LG G3 D855 Gold 32gb model purchased via Kogan in Australia.
The unit is now on Android 5.0 (no updates available for 5.1+) - Software Version V20i-SEA-XX with Build number LRX21R.A1440645925.
This phone is non-rooted with stock ROM etc.
So the issue at hand, I upgraded my Win7 PC via the upgrade option to Win10 to retain my games/files etc.
Now when connecting the phone to the PC it only goes to charging mode and I am unable to click on it within the drop-down to change it to anything else.
I have tried LG G3 drivers, Googles generic drivers, ADB suite drivers. I am unable to adb find the phone, I do not have an Acer Composite device in Device Manager.
Win 10 keeps saying the device is not recognised/malfunctioned.
Tried different cords, double checked the connector on the phone for any dust specs etc.
My PC refuses to work with any driver I have thrown at it, however in each scenario with various drivers, warnings still persist in Device Manager.
Some of the drivers force the phone to connect/reconnect and cause the "ping" sound each time it disconnects and reconnects (with malfunction warning prompts).
This is on Win10 with 64bit Home edition.
I am at my wits end and can't think of anything I haven't tried beyond a factory reset of my phone (hoping not to at this stage as I'm thinking it's driver-related).
It won't let me tether or anything via USB also, same goes with USB debugging, no change.
Lastly which may also help narrow it down, with the phone plugged in BEFORE it gets to the OS, I can change between PTP/MTP and USB charge, however once the Win10 OS loads up, it disconnects/malfunctions and lists Charge Only.
And yes, this phone can connect on my Win7 small PC which I use for testing crap out on.
Any ideas guys?
Let me know if any log files or anything is required.
At this stage I am unable to do a root to the phone (due to adb issues etc) nor can I connect to the internal phone system unless I use in the in-built file explorer.
Click to expand...
Click to collapse
Try the drivers from this site
http://forum.xda-developers.com/showthread.php?t=2785089
ludoke said:
Try the drivers from this site
http://forum.xda-developers.com/showthread.php?t=2785089
Click to expand...
Click to collapse
Using the drivers on that page you have advised gives the following.
Device Manager shows a Warning on it in USB controllers as "LGE Mobile USB Composite Device". It automatically "malfunctions" according to Windows 10 and I can't change the connection interface on the phone.
Going into the properties on that device in Device Manager lists the following;
This device cannot start. (Code 10)
A device which does not exist was specified.
http://forum.xda-developers.com/lg-g3/help/answer-windows-8-8-1-detecting-lollipop-t2967574
This also works for win 10
If u find this helpful rember the thanks button
TheMadScientist420 said:
http://forum.xda-developers.com/lg-g3/help/answer-windows-8-8-1-detecting-lollipop-t2967574
This also works for win 10
If u find this helpful rember the thanks button
Click to expand...
Click to collapse
This didn't work. Already tried
Fixed my problem
I've had the same issue with my LG G3 in being unable to connect the device to my laptop. I'm not sure if the cause was a phone software update or the upgrade from Windows 8.1 to Windows 10. Either way, I searched and fixed it tonight by installing updated drivers. Hope this helps others as well.
Hmmm, I cannot post the link! technobuzz dot net lg g3 drivers
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!
I have spent litterally all day trying to update my mrs g3 d855 and i have had no luck, how much of it because my computer i dont know. Im running a chromebook with a full linux distro gallumos installed, got virtual box running 32 bit windows 7. Android sdk, adb etc and got lg drivers installed to recognise the device in its various states, ptp, mtp, download. all that is working. got the official lg mobile support tool and the lg 2014 flash tool.
the problem im having is neither of these will update the phone, if i try to manaully flash the kdz using the flashtool or updating using the official one, it wont update recover either. if i try different region or enter the imei number it always fails at 4%. Iv tried different usb cables, different ports, the phone was at 100% battery the whole time, the laptop was on charge the whole time. I really dont know what else to do, i have no access to another windows machine here and its the mrs phone and she wouldnt want me to take it to work to try on another pc there. As i said earlier the drivers all seem installed correctly, the firmware downloads and extracts as it should but I really am at the point i dont know what else to try
Hello,
Did you try LGUP method? Link is here.
It's easy to use. All you need is there, try it and reply
Just TIP: Do you really have correct drivers for download mode? If LGUP see you device as "unknown", change your COM port to #41
Do "FULL WIPE AND INSTALL MM"
I think I might of, how ever before work I did download a version of lg up and some kind of other installer for it. I also got a kdz file to try and flash. The drivers should all be fine, it gets recognised in all the various modes. My fiance is on nights this week, the soonest il be able to try again is tomorrow so I will let you know it goes. Thank you for replying
The Gingerbread Man said:
I think I might of, how ever before work I did download a version of lg up and some kind of other installer for it. I also got a kdz file to try and flash. The drivers should all be fine, it gets recognised in all the various modes. My fiance is on nights this week, the soonest il be able to try again is tomorrow so I will let you know it goes. Thank you for replying
Click to expand...
Click to collapse
You can send me a PM, or just reply to this thread.
It's a common problem with various solutions. We will look at it.
halekhonza said:
You can send me a PM, or just reply to this thread.
It's a common problem with various solutions. We will look at it.
Click to expand...
Click to collapse
Thanks buddy il let you know after I can try it again. If it was a Nexus it would be fine, I know all about fastboot, unlocking bootloaders and rooting and stuff for the Nexus line. So much easier to work with
So I think I might know where I'm going wrong, i thought I had all the drivers set up but there's one I missed, for download mode
Under device manager I see when the phone is turned on with adb on
Android device- lge mobile adb interface-google Inc 4.0.0.0-working properly
Portable devices-g3-lg electronics 4.0.0.0-working properly
Ports (com & lot)-lg mobile USB serial port (com 4)-lg electronics 4.0.0.0-working properly
In download mode device manager
android device isn't there, no adb which is fair enough
Portable devices-g3 with yellow warning triangle-lg electronics 4.0.0.0- the device cannot start code 10
Ports (com & lot)-lg mobile USB serial port (com 4)-lg electronics 4.0.0.0-working properly
So I need to trouble shoot why the device cannot start. I have downloaded 2 packs of Lg drivers, lg united mobile driver & lg mobile driver. Both of which contain loads of drivers inside.
If I guide windows into either of the folders it won't install any new drivers giving an error saying that the driver software is already up to date.
I'm going to Google to find out what's going on with device cannot start error, if I'm missing something obvious please jump in
Can you please post complete screenshot with windows device manager (with open ports menu) and adb console with command "adb devices" ?
In your chromebook, do you have disabled all USB power saving bull****s? Also check VM software to see if there is such a possibility to enable/disable USB power plans.
At least, sorry for my bad english Still a lot of things to learn.
Your English is fine I understand perfectly, in fact I wouldn't of guessed it's not your native language so don't worry! Iv taken photos of my screen. You will see when the phone is turned on normally the host and client can both see the device and adb shows the device is detected and returns the serial number, all good there. The last photos shows when it's in download mode and that the driver isn't working properly, it can not start the device with a code 10 error. If I can fix that I know the lgup programming will run. The problem is because the PC can't communicate with the PC in download mode because of some driver issue.
I'm going to have to carry on tomorrow as I have to go to work and the Mrs needs her phone here while she sleeps
The Gingerbread Man said:
Your English is fine I understand perfectly, in fact I wouldn't of guessed it's not your native language so don't worry! Iv taken photos of my screen. You will see when the phone is turned on normally the host and client can both see the device and adb shows the device is detected and returns the serial number, all good there. The last photos shows when it's in download mode and that the driver isn't working properly, it can not start the device with a code 10 error. If I can fix that I know the lgup programming will run. The problem is because the PC can't communicate with the PC in download mode because of some driver issue.
I'm going to have to carry on tomorrow as I have to go to work and the Mrs needs her phone here while she sleeps
Click to expand...
Click to collapse
Please, enter download mode and change in Windows COM port from #3 to #41 and try LGUP method . It's up to you what method (upgrade, full wipe) you choose.
OK sounds straight forward enough. As I say il have to try tomorrow as I'm at work now and left the Mrs with her phone at home asleep, she will be working night shift so it will have to be when she is back home. I really appreciate the help and il post again to update how I get on
Where I am now is no further, iv tried changing the port to 41 through device manager. Iv set the port 0041 in virtual box for USB settings. Iv tried several sets of drivers. What keeps happening no matter which set of drivers I use when the phone goes into download mode mtp stops working and stops the phone communicating with the PC. When I restart it will work normally for a while but go wrong again. If I try lg up and starting the upgrade in download mode it gives me an error saying it can't change to download mode if I choose refurbish or upgrade. Lg PC suite just hangs at 0% and returns an error after a while. The 2014 flash tool will get as far as trying to flash but hangs at 4% and returns an error but doesn't specify what. I really don't know what else I can do. When these programs reboot the device into download mode it disconnects the device from the virtual machine and I can't get it connected again quick enough before errors are returned or mtp stops working which requires me to reboot the VM or phone. The only thing I can think to do is try on another machine. If it was my phone I would of thrown it out the window or under a bus. Lg software is unusable through virtual machines and I am not buying a new PC just for this lol Il see if I can use someone else's. I hate being defeated, iv have spent probably some 16 hours and got no where! Why can't they just release an ota? It only strengthens my belief in nexus and fastboot. Sorry for the rant but this really has got under my skin and I don't like giving in
Edit
I'm just as annoyed with windows as lg at this point. I really don't like using it. Grrrr