I was trying to flash the lollipop kdz to my phone and was having problems with drivers but then one time it apparently was working but it still gave me an error popup so I unplugged it and now it always boots into firmware update mode :crying: Now I can't get the drivers to install. It shows 3 devices: Mtp device, LGE Android phone, and CDC Serial port (this is just from memory so the actual names might be slightly different). The MTP device always gives the error "Failed to start" and the other 2 say no driver found. I have tried different pcs and driver versions with the same results. I tried this but it says no drivers found. Does anyone know of a fix for this? Is there a way to manually specify the drivers to use or something?
I updated the drivers to the version from LG's website and now the drivers seem to be working except for the mtp one. Now when I try to flash it give the error "Connection to server failed, try again in a moment" and if I click retry it fails with the message "Upgrade stopped due to an error". Anyone have suggestions on how to fix?
Update: I tried the tot method as well and it fails with an error getting model name.
jonmast said:
Update: I tried the tot method as well and it fails with an error getting model name.
Click to expand...
Click to collapse
Make sure that you have the correct drivers installed. For Verizon they should be the LG_VZW_United_WHQL_v2.20.0 one. Use the lg flash tool 2014 http://forum.xda-developers.com/showthread.php?t=2797190 and a kdz file. I believe that you can update to lollipop directly with the lg flash tools. I could not install the lollipop kdz as I kept receiving the same issue "cannot connect to server" so I installed stock 4.4.2 that my device came with and updated to lollipop ota. If you install the the same stock software that your phone shipped with it will still say "cannot connect to server" but it will indeed update your software. I believe that the key is to making sure you install the same stock software your device shipped with for it to actually update to your phone in my experience.
I am using the drivers you mentioned. Do you know if the mtp driver failing is an issue? Also, I tried 3 different kdz versions with the same results.
Do you have a custom recovery like TWRP or CWM?
mach01 said:
Do you have a custom recovery like TWRP or CWM?
Click to expand...
Click to collapse
No
Related
Hello,
I was recently trying to load a stock rom on my LG540 and the process was interrupted because of a power failure. But the phone luckily booted into "download mode". I want to reflash using the procedures discussed in various posts on bricked phones, but my computer can no longer recognize the phone. The KDZ updater reports "Phone not Found". The correct drivers are installed and I am running windows 7 home edition.
Any thoughts as to how to get the computer recognize the phone?
Thanks, MN
maybe using "Run as administrator"
Try installing these drivers, they helped me when I first used KDZ. The links are from a hungarian site.
http://www.4shared.com/file/Zx52g1kl/Optimus_GT540_pc_sync.html
I think the bootloader is corrupted, it's basically "bricked", but not fully
Drivers must be the issue. Try uninstalling LG driver, reinstall it or use Windows Update to install drivers.
Bricked GT540
Maybe you can use LGDP2 ??
Hello.
I recently tried to root my phone with the S3 Mini Toolkit. I have the GT-I8190 international version.
It said that I needed to Install the device drivers first (which is the v1.5.18.0).
So I did it as instructed in the command prompt. When it finished installing the driver, and I plugged my device as instructed, suddenly came an error message "Samsung Hardware ID is missing error", and my Mini became unrecognized all of a sudden. I couldn't access my device storage.
There was an error message too popped up in my device saying that It cannot find a driver in my PC for my device.
I tried to install KIES afterward, hoping that it can solve the problem. Thing is, it didn't. My device was still not recognized, and KIES couldn't recognize it either (Connecting.....for, like forever).
I then tried to Google the problem, and came by a forum, saying that it was the 1.5 USB Drivers that caused the problem (but the case being talked in the forum is for Galaxy S3). Said that my PC need to uninstall the 1.5 drivers, uninstall KIES, deactivate the automatic device installation by Windows, and install the 1.4 version.
Well, what I can find in the internet is the 1.3 USB Drivers, so I tried the instructions, and installed the version 1.3 USB Drivers, and my PC recognized my device again, and able to access the storage.
(also, the 1.3 drivers made Odin unable to recognize my phone too in download mode).
Does anybody here have ever experienced the same problem as mine? Or did I do something wrong?
I managed to root my Mini, being not recognized by the PC (but registered at the toolkit) in the whole process, and then did the whole uninstalling and re-install the USB drivers so that I can access my storage again.
Because it's rather a painful process if in the future I want to use the toolkit again with the newest drivers.
Note:
- before rooting, I did the latest OTA update.
My current device info is
Android version 4.1.2
Baseband version I8190DXAMA2
Build vnumber JZO54K.I8190DXAMA2
Region Indonesia
Thank you very much
Bumped. Can anybody gives me some enlightenment about this issue? Thanks
So I think I may have bricked my phone unless I can get the H811 20i KDZ file but even that may not be good enough to save it. I'll start with where I am currently at. On boot I get the error:
Secure booting error!
Error code: 1003
Modified
I am able to get into download mode by pressing the up volume key or into the wipe mode by pressing the down volume key. However, no matter what I try I can't seem to get it to reboot normally.
Here is what I did to get myself into this situation:
I stepped through the guide to install MM and then I performed the fastboot OEM unlock and booted into TWRP. I then installed SuperSU and rebooted. Then for reasons unknown I decided I would relock the boot loader and so I ran the command fastboot oem lock. I fully understand the stupidity of that thought now but didn't think very clearly at the time.
Here is what I have tried:
Using the LG Support Tool I attempted an Upgrade Recovery which failed.
Using the guide on here to return to stock I attempted the method using the kdz file for h811 10n but that fails at the upgrading your phone with the error message "Upgrade stopped due to an error". I have attempted the retry button numerous times without any change in responses.
At this point in time I am game to try anything.
:fingers-crossed:
Thanks to autoprime I am now downloading the kdz for MM and when it is complete I will attempt to use LGUP to restore it.
Well I get an error message from LGUP stating that I don't have the correct DLL for H81120i installed. I attempted to replace the dll with the one inside the MM kdz but that didn't work.
bbenz3 said:
Thanks to autoprime I am now downloading the kdz for MM and when it is complete I will attempt to use LGUP to restore it.
Well I get an error message from LGUP stating that I don't have the correct DLL for H81120i installed. I attempted to replace the dll with the one inside the MM kdz but that didn't work.
Click to expand...
Click to collapse
Use LGBridge. Put it in download mode. Click on update error recovery.
Vseprz said:
Use LGBridge. Put it in download mode. Click on update error recovery.
Click to expand...
Click to collapse
Oh I wish it were that simple. I had tried it last night but attempted it again as I couldn't remember what happened. I get an error message stating "Connect your mobile device to the USB port. If it is already connected, contact LG customer service."
At this point I think I may just need the MM dll to use with LGUP. I attempted to use an MSI packaging utility to replace the dll in the 0.0.3.23 installer with the dll I extracted from the kdz file but that got me nowhere.
I attempted to use the LG FlashTool v1.8 and found out that the dll that I extracted is ver 0.0.3.21 which is older than the msi version found on here. Does anyone know how to get a newer one?
bbenz3 said:
Oh I wish it were that simple. I had tried it last night but attempted it again as I couldn't remember what happened. I get an error message stating "Connect your mobile device to the USB port. If it is already connected, contact LG customer service."
At this point I think I may just need the MM dll to use with LGUP. I attempted to use an MSI packaging utility to replace the dll in the 0.0.3.23 installer with the dll I extracted from the kdz file but that got me nowhere.
Click to expand...
Click to collapse
I had the same error and sucessfully used lgbridge. You probably need to reinstall your usb drivers.
OK I'll give that a shot.
No go...
I uninstalled anything I could find related to LG. I then reinstalled the LG Bridge software which then updated the USB drivers to 4.0.4. I then rebooted my computer and attempted it again and I got nothing but the same error.
bbenz3 said:
OK I'll give that a shot.
No go...
I uninstalled anything I could find related to LG. I then reinstalled the LG Bridge software which then updated the USB drivers to 4.0.4. I then rebooted my computer and attempted it again and I got nothing but the same error.
Click to expand...
Click to collapse
I had this exact same issue when upgrading my phone. Didn't do it correctly and it took me about 3 hours before I got my phone working again. It was about a week ago on another computer, but I'll try to recall what I did when it finally clicked in my mind.
Download H81120i_00_0201.kdz flashable zip from here (1.6GB Feb-04-16):
http://downloads.codefi.re/autoprime/LG/LG_G4/H811/H81120i/
Download LGUP and install it. I used the DropBox link in this thread:
http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Remember to install the LGUP_8994_DLL file BEFORE LGUP_Install
Download and install LG Bridge (for the USB drivers) here:
http://www.lg.com/uk/support/pc-suite
Select the LG 815 model, the drivers will work. I only used the LG Bridge to install the USB drivers. Nothing else.
OK, now here's where your phone comes in.
Step 1: Turn off your phone (pull the battery if you must, but put it back in).
Step 2: Hold the VOLUME UP button and plug the USB cable into your PC. This puts your phone into DOWNLOAD MODE.
Step 3: On your PC, open up LGUP. The program shoud recognize the phone as H811 in COM3 or COM4. Highlight it and click the SELECT button.
Step 4: Under the "Process" row, select UPGRADE
Step 5: Click the blank space under File Path, it will pop up a [...] [X] at the end. Click the [...].
Step 6: Select the H81120i_00_0201.kdz and click on Start. The program will push the STOCK H811 MM ROM to your phone. This will bring your phone out of Brick mode, but you will have to go through the entire rooting process again.
Donut42 said:
I had this exact same issue when upgrading my phone. Didn't do it correctly and it took me about 3 hours before I got my phone working again. It was about a week ago on another computer, but I'll try to recall what I did when it finally clicked in my mind.......
Click to expand...
Click to collapse
Woohoo!!!!!!!!!!!!!! I changed two things and I'm not certain which one it was that finally made it work but I followed your steps and installed the LGUP_DLL before the application (upon re-reading the original thread for the LGUP program I see that is the way you were supposed to do it the whole time, so much for reading comprehension) and the other was I ran it from a Win 7 VM instead of Win 10.
Big thanks to you and also to bender_007 for walking me through a bunch of stuff and recommending the VM approach.
I did the exact same thing, but I cannot get LGUP to recognize my device. Uninstalled and reinstalled drivers and all. Any other ideas?
I did the following:
Installed Windows 7 in a VM
Installed the LG Bridge software and ran in do it should update
Installed the LGUP DLL
Installed the LGUP software
Connected phone to VM
Then ran LGUP tool
bbenz3 said:
I did the following:
Installed Windows 7 in a VM
Installed the LG Bridge software and ran in do it should update
Installed the LGUP DLL
Installed the LGUP software
Connected phone to VM
Then ran LGUP tool
Click to expand...
Click to collapse
Just tried this, but still showing as unknown device. I thought that was going to work.
---------- Post added at 04:39 AM ---------- Previous post was at 04:20 AM ----------
What does the phone show up in Device Manager as when it is in download manager? Mine is showing as LGE Androidnet USB Serial Port. Is this the same for you?
hv same problem. but problem is pc can't recognize the phone for below step:
Step 3: On your PC, open up LGUP. The program shoud recognize the phone as H811 in COM3 or COM4. Highlight it and click the SELECT button.
can recognize another G4.
ilovelg4ever said:
hv same problem. but problem is pc can't recognize the phone for below step:
Step 3: On your PC, open up LGUP. The program shoud recognize the phone as H811 in COM3 or COM4. Highlight it and click the SELECT button.
can recognize another G4.
Click to expand...
Click to collapse
same... I think it might have to do with the from that was installed when I relocked the boorloader. I'm so stupid for that.
I was trying different drivers, but none have helped lgup to recognize my phone.
esteho said:
same... I think it might have to do with the from that was installed when I relocked the boorloader. I'm so stupid for that.
I was trying different drivers, but none have helped lgup to recognize my phone.
Click to expand...
Click to collapse
first of all, how can we make PC detect our G4?
actually, even w/o any drive installed in PC, the PC should detect G4 if it works normally.
Device Manager shows my device, but as "LGE AndroidNet USB Serial Port". From what I have read this may be it's bricked mode. Is there anyone with an idea on how to come back from this?
esteho said:
same... I think it might have to do with the from that was installed when I relocked the boorloader. I'm so stupid for that.
I was trying different drivers, but none have helped lgup to recognize my phone.
Click to expand...
Click to collapse
saaaaame......
model COM Ports
unknwon [com41, xTreme 3]
Can't use Send_command too.
MM relocked the boorloader was stupid.
I had this exact error yesterday. I used cdmatool to get some bands enabled so I could get AT&T LTE with an AT&T sim and T-Mobile phone. All went well, and on my way out I figured since I had done the fastboot oem unlock, I should probably relock it. BAD IDEA.
By the time I found this article I had figured that somehow I needed to reflash to a ROM with a unmodified bootloader. This article is great! Such a rare treasure - all of the links to the necessary software and a short-but-sweet guide all in one. This post saved me hours, maybe days, of searching and trial-and-error.
By the way, since I had already installed the LG device drivers (available here) it was not necessary to download and install the whole LG Bridge.
THANKS!
Many times tried to flash my H811 to 20i but always ended with blank screen...is it have to wait until 5 to 10 minutes to get the phone rebooted after flashing with LGUP? Because usually ended with blank screen and qd mode, have to revive using qfil, imei unknown, camera and google play store always closes.
Hi, I'm having issues with XZ2 Drivers.
I'm a noobie trying to do a wipe of my phone back to stock, using Newflasher and Xperifirm.
When I try to flash with Newflasher, I get the "Incorrect function" error, and from what I've read from previous posts on the newflasher thread, it is because I am missing drivers.
The issue is, there are no drivers that I can find that work with the phone when I try to install them, and zadig can't put in custom USB drivers in for me.
I've tried installing gordongate drivers, but they don't seem to work.
My phone model is H8216.
Any help will be appreciated
Reboot to safemode with F7. I recommend using flashtool drivers from http://www.flashtool.net
Bork Bork said:
Reboot to safemode with F7. I recommend using flashtool drivers from (WEBSITE)
Click to expand...
Click to collapse
Flashtool drivers don't seem to include XZ2 drivers. Am I missing something though?
Catonthemat99 said:
Flashtool drivers don't seem to include XZ2 drivers. Am I missing something though?
Click to expand...
Click to collapse
Re-read what I wrote above.
Bork Bork said:
Re-read what I wrote above.
Click to expand...
Click to collapse
After a couple of days of attempts, I have achieved a successful flash.
Unfortunately, another problem arose.
When I load into stock firmware, I'm only allowed to make emergency calls, and there's text on the bottom of the screen that says: "Simcard is Locked".
Does anyone know why that might be?
I was using Xiaomi USB Drive it was working fine but after a few flashing files for my Redmi note 9, my pc was not able to recognize my device. Then I have installed the latest Mi USB drive that is still working fine so if you want to download drives so you can also download from here. I hope it will help you out! also, you can download the latest Fastboot file from Mi.com
Hello,
I have a somewhat aged Idol 4 lying here.
This no longer boots or it hangs in the boot loop.
So I tried to install an update via a stock rom from the network via the recovery menu and ADB sideload and always got the error status 7. (Alcatel_Idol_4_6055K_01001_01002_OTA)
Resetting the system didn't help here either.
Then I tried to install TWRP on the device.
But unfortunately both methods that I tried failed.
Once via Sahara & firehose-test and the second was Suger QCT via the download mode.
But both of them got the error message NPRG Error 5002.
I have installed suitable USB drivers.
So my question, does anyone have a tip for me on how I could get the device revived?
And Sorry for my bad english
Hm.. said:
Hello,
I have a somewhat aged Idol 4 lying here.
This no longer boots or it hangs in the boot loop.
So I tried to install an update via a stock rom from the network via the recovery menu and ADB sideload and always got the error status 7. (Alcatel_Idol_4_6055K_01001_01002_OTA)
Resetting the system didn't help here either.
Then I tried to install TWRP on the device.
But unfortunately both methods that I tried failed.
Once via Sahara & firehose-test and the second was Suger QCT via the download mode.
But both of them got the error message NPRG Error 5002.
I have installed suitable USB drivers.
So my question, does anyone have a tip for me on how I could get the device revived?
And Sorry for my bad english
Click to expand...
Click to collapse
Hello, I deleted my system from twr without realizing what I was doing, the result is that I stay on the Alcatel logo. My steps were, the installation of sugar, when it starts not to update the application. Choose the 6055 model, since the 6055P model that is mine does not appear in the drop-down. Before starting sugar, turn off the mobile completely and connect it off to the usb of the pc, check if when connecting it the pc does not detect it, use another cable (there are many cables that only serve to charge and not to read on the pc) Now start sugar, choose the model and click on the Udgrade tab. You will surely get several messages saying that the mobile has been modified and that you lose the guarantee, go ahead accepting the message, in a few minutes you will have it ready. Greetings.
Perdigon55 said:
Hello, I deleted my system from twr without realizing what I was doing, the result is that I stay on the Alcatel logo. My steps were, the installation of sugar, when it starts not to update the application. Choose the 6055 model, since the 6055P model that is mine does not appear in the drop-down. Before starting sugar, turn off the mobile completely and connect it off to the usb of the pc, check if when connecting it the pc does not detect it, use another cable (there are many cables that only serve to charge and not to read on the pc) Now start sugar, choose the model and click on the Udgrade tab. You will surely get several messages saying that the mobile has been modified and that you lose the guarantee, go ahead accepting the message, in a few minutes you will have it ready. Greetings.
Click to expand...
Click to collapse
Hello, thanks for the answer and the download.
I've tried the same way. I still downloaded your file and tried as you described.
Unfortunately I got the same error NPRG Error 5002 again.
Unfortunately I have no idea where the problem could be.
I found out that it could be a memory error.
As if a flash process had failed and there is no longer a correct series of partitions.
So I would need a complete original rom and would have to flash it via fastboot.
I could also try it via twrp, but I don't get this flashed.
And I don't have a complete original rom either.
Hello,
So I have now been able to flash the phone with another PC with Sugar QCT after it suddenly started up after the battery was completely empty and I charged it again.
But unfortunately the boot problem persists after turning off the phone again.
Even after replacing the battery with a new one.
Then I tried to flash TWRP via the Alcatel Flasher.
The flash process was successful but there was no TWRP on it after the reboot.
So the problem could still be somewhere else than just the firmware.
Hm.. said:
Hello,
So I have now been able to flash the phone with another PC with Sugar QCT after it suddenly started up after the battery was completely empty and I charged it again.
But unfortunately the boot problem persists after turning off the phone again.
Even after replacing the battery with a new one.
Then I tried to flash TWRP via the Alcatel Flasher.
The flash process was successful but there was no TWRP on it after the reboot.
So the problem could still be somewhere else than just the firmware.
Click to expand...
Click to collapse
Hello, it may be that you are making the same mistake that I made when installing recoveri. When selecting the recovery, note that the twr is the one that weighs about 14 mb and the original one about 24 mb. I think that when you make a copy with the recovery program and then install the twr you select it wrong. In the program, do not make the copy of the recovery, skip that step and go directly to install and select the 14 mb file. You will see that this is the problem. Cheers