Related
LG OPTIMUS ZONE 3 - UNBRICKING GUIDE AND 5.1.1 FACTORY FIRMWARE
This guide has two main objectives: (1) for those with a bricked device who want to restore to the latest factory firmware image; and (2) those who need .kdz Stock 5.1.1 Factory Firmware files.
1. UNBRICKING THE LGVS425PP:
The Verizon LGVS425PP comes, pre-installed on the device, a Windows compatible LG Software Upgrade and Repair utility. When connected via micro USB cable, your device will connect to your PC as an installer and, if you look in your PC directory, you will see an installation directory for the Verizon LG utility. Inside that directory is an .exe file that will install the upgrade/repair utility on your PC. When launched, the utility will auto detect your device, determine if a firmware update is available, and give you an option to repair your device. The repair option will backup your existing userdata (depending on the level of damage to the firmware), download the most recent firmware build for your device, and flash your device to complete stock condition.
Of course, there are those who bricked their devices before being able to install the Verizon LG Upgrade/Repair utility on their PCs. And this utility appears difficult to locate for download on the internet. So, below is a download link for the utility:
DOWNLOAD LINK
https://drive.google.com/drive/folders/0B1Sfod4HWfk2elpGQ3JEbzF4Q0E?usp=sharing
The Verizon LG utility should install the correct USB mobile drivers on your PC. But just in case any driver issues arise, download and install the following LG United Mobile Driver package:
DOWNLOAD LINK
https://drive.google.com/file/d/0B1Sfod4HWfk2RHY2c29mTWg1Rkk/view?usp=sharing
Once the utility is launched, make sure your PC is connected to the internet, put your device in download mode by holding +Volume while connecting your micro USB cable for your PC connection. The utility will then detect your device. Select the REPAIR option and follow the on-screen instructions.
2. STOCK 5.1.1 FACTORY FIRMWARE
The following link is for four software versions of stock 5.1.1 Factory Firmware .kdz files for the Optimus Zone 3: VS425PP2, VS425PP4, VS425PP7 & VS425PP8. Also in the link is the LG United Mobile Driver, the LG-UP flashing tool, and the LG-UP .DLL for the VS425PP. Use these tools at your own risk. I am not responsible for bricked or inoperable devices. I want to thank each and every member in this thread who has tested and reported their findings and issues. That narrows it down greatly. And thanks guys for your patience.
As to rooting the Zone 3, several recent advancements have been achieved and full root access is now possible. Thanks to @Astr4y4L, a comprehensive root package is available for download. http://astrayalslanding.dynu.net:88/Android_Development/ Click on this link and scroll down the the bottom and click the projects link. His package includes precise instructions and alI the files you will need to root this phone. I am currently drafting a concise tutorial for downgrading this phone. Instructions for downgrading can be found within this thread, albeit somewhat scattered. I will update the OP accordingly as further progress is made. Guys, please be sure to thank @Astr4y4L for his unceasing hard work and development on this device. If you like his work and benefit from it, donations are always nice, even if just a couple bucks.
DOWNLOAD LINK
https://drive.google.com/drive/folders/0B1Sfod4HWfk2MUwxNk1oeXJCZEE?usp=sharing
I was attempting to test this on a phone i purchased just yesterday. The about phone section identifies this phone as a vs425pp but under the battery it's identified as a VS425LPP.
The drivers install successfully. The LGUP and LGUP .dll install fine. But when i start LGUP i get an error saying that it can't load the model. looks like i can't attach a picture probably because i'm new but i do have screencaps. I've tried it on my laptop where i do most of my android stuff and on my desktop, same problem on both. According to the LG Mobile Support Tool this one has VS245PP5 installed.
LGUP will start without the phone connected telling me there is no compatible handset attached and then show me a com window. But when i connect the phone it throws the same error and exits.
I must be the biggest idiot, because I cannot figure out how to get into download mode - I power off the device, then while holding the power and volume up key I plug in the usb cord from the Computer. I get the buzzing on the phone, the Verizon logo comes up, and i'm on the home screen. What am I doing wrong?
---------- Post added at 12:55 AM ---------- Previous post was at 12:51 AM ----------
never mind, I got it - it's the volume down and power, not volume up -
---------- Post added at 01:00 AM ---------- Previous post was at 12:55 AM ----------
ok, apparently, that's the restore function, not the download mode - I can't seem to figure out the combo of buttons for the download mode - as above, I go volume up and power then when it vibrates I plug it in?? any suggestions??
wperdigon said:
I must be the biggest idiot, because I cannot figure out how to get into download mode - I power off the device, then while holding the power and volume up key I plug in the usb cord from the Computer. I get the buzzing on the phone, the Verizon logo comes up, and i'm on the home screen. What am I doing wrong?
---------- Post added at 12:55 AM ---------- Previous post was at 12:51 AM ----------
never mind, I got it - it's the volume down and power, not volume up -
---------- Post added at 01:00 AM ---------- Previous post was at 12:55 AM ----------
ok, apparently, that's the restore function, not the download mode - I can't seem to figure out the combo of buttons for the download mode - as above, I go volume up and power then when it vibrates I plug it in?? any suggestions??
Click to expand...
Click to collapse
I just hold volume up and keep it help while connecting the micro USB
Metalchic said:
I was attempting to test this on a phone i purchased just yesterday. The about phone section identifies this phone as a vs425pp but under the battery it's identified as a VS425LPP.
The drivers install successfully. The LGUP and LGUP .dll install fine. But when i start LGUP i get an error saying that it can't load the model. looks like i can't attach a picture probably because i'm new but i do have screencaps. I've tried it on my laptop where i do most of my android stuff and on my desktop, same problem on both. According to the LG Mobile Support Tool this one has VS245PP5 installed.
LGUP will start without the phone connected telling me there is no compatible handset attached and then show me a com window. But when i connect the phone it throws the same error and exits.
Click to expand...
Click to collapse
With your device connected go to Device Manager. Look under Portable Devices, Ports and Com's, etc and look for LGE notations of your device. If you see a yellow question mark by any of the LGE notations, your issue is drivers.
MotoJunkie01 said:
With your device connected go to Device Manager. Look under Portable Devices, Ports and Com's, etc and look for LGE notations of your device. If you see a yellow question mark by any of the LGE notations, your issue is drivers.
Click to expand...
Click to collapse
i have a
Modems > LGE Mobile for VZW USB Modem - Operational
Ports (COM & LPT )> LGE Mobile for VZW USB Serial Port (COM4) - Operational
Portable Devices > LGE Android MTP Device - Code 10 device cannot start
I initially had the 4.1.1 drivers installed from the LG Mobile Support Tool. After uninstalling those and installing the 4.0.4 version from this thread i still have Code 10 error on LGE Android MTP Device.
Metalchic said:
i have a
Modems > LGE Mobile for VZW USB Modem - Operational
Ports (COM & LPT )> LGE Mobile for VZW USB Serial Port (COM4) - Operational
Portable Devices > LGE Android MTP Device - Code 10 device cannot start
I initially had the 4.1.1 drivers installed from the LG Mobile Support Tool. After uninstalling those and installing the 4.0.4 version from this thread i still have Code 10 error on LGE Android MTP Device.
Click to expand...
Click to collapse
Ok I have seen that MTP Device error before. It is not uncommon. Search the forums for a driver resolution. Off top of my head I cannot recall, but I do know there are threads on it.
MotoJunkie01 said:
Ok I have seen that MTP Device error before. It is not uncommon. Search the forums for a driver resolution. Off top of my head I cannot recall, but I do know there are threads on it.
Click to expand...
Click to collapse
The initial solution was to reinstall the drivers, did not work.
Second solution discovered in reference to samsung devices was to delete a registry key called UpperFilters from the WPD section. Did not work.
The third solution i've found involves downloading the Android SDK and installing it.
This last one seems sort of like a nuclear option. But i'm running out of ideas. the MTP and PTP transfer modes install and start correctly when the device is booted normally but when booted into download mode it just goes code 10. I'm working on the third option now but it will take a while to download.
Metalchic said:
The initial solution was to reinstall the drivers, did not work.
Second solution discovered in reference to samsung devices was to delete a registry key called UpperFilters from the WPD section. Did not work.
The third solution i've found involves downloading the Android SDK and installing it.
This last one seems sort of like a nuclear option. But i'm running out of ideas. the MTP and PTP transfer modes install and start correctly when the device is booted normally but when booted into download mode it just goes code 10. I'm working on the third option now but it will take a while to download.
Click to expand...
Click to collapse
Yes that SDK is a bulk of a download and installation. But may be your fix. Very odd I agree
MotoJunkie01 said:
Yes that SDK is a bulk of a download and installation. But may be your fix. Very odd I agree
Click to expand...
Click to collapse
It didn't work. Still code 10. I tried on a third computer, an old Dell laptop running Windows XP. It gave a strange error Code 28 saying something about an invalid service section of the INF. But i think this may be a red herring and actually be caused by Windows Media Player 11 not being installed. I'll have to setup an installation of Windows 7 to try that.
Edit: looks like i'm going to have to give up trying to fix the code 10 error because NONE of the information from google is relevant to this. All the information is for the phone being started normally and being unable to access the MTP file transfer through normal working operation. None of it relates to this "download mode" that LG has implemented. I wish this were easy like my Galaxy Nexus was back in the day.
Metalchic said:
It didn't work. Still code 10. I tried on a third computer, an old Dell laptop running Windows XP. It gave a strange error Code 28 saying something about an invalid service section of the INF. But i think this may be a red herring and actually be caused by Windows Media Player 11 not being installed. I'll have to setup an installation of Windows 7 to try that.
Click to expand...
Click to collapse
OK. Let me know..
Metalchic said:
It didn't work. Still code 10. I tried on a third computer, an old Dell laptop running Windows XP. It gave a strange error Code 28 saying something about an invalid service section of the INF. But i think this may be a red herring and actually be caused by Windows Media Player 11 not being installed. I'll have to setup an installation of Windows 7 to try that.
Edit: looks like i'm going to have to give up trying to fix the code 10 error because NONE of the information from google is relevant to this. All the information is for the phone being started normally and being unable to access the MTP file transfer through normal working operation. None of it relates to this "download mode" that LG has implemented. I wish this were easy like my Galaxy Nexus was back in the day.
Click to expand...
Click to collapse
Yeah tell me about it. The good ol' Nexus days were much simpler. I'm like you....I think its a Red Herring of some sort you are dealing with. Something so obvious and so simple that it is hiding behind a thin wall.
I'm searching right now trying to help too.
Hi MotoJunkie01,
I appreciate you putting together this guide but I have to say that I no further along than everyone else here. Similar to Metalchic I received the "can't load model" error from LGUP. Googling around i found that I was missing the LGUP_common.dll file. Found that and LGUP opened fine and found my device. Tried to flash VS425PP2 kdz got to about 9% and received "Secure device, But Unsecure image" error. And that's as far as i got.
As far as the LG Android MTP driver goes i also receive the code 10 cannot start error but only when the phone is in download mode. Otherwise the driver loads fine when the phone is "booted". I dont know jack about rooting phones and have never done it before. I had this one lying around and thought I'd try it. Hopefully all this helps to narrow down the issue.
roscoemctavish said:
Hi MotoJunkie01,
I appreciate you putting together this guide but I have to say that I no further along than everyone else here. Similar to Metalchic I received the "can't load model" error from LGUP. Googling around i found that I was missing the LGUP_common.dll file. Found that and LGUP opened fine and found my device. Tried to flash VS425PP2 kdz got to about 9% and received "Secure device, But Unsecure image" error. And that's as far as i got.
As far as the LG Android MTP driver goes i also receive the code 10 cannot start error but only when the phone is in download mode. Otherwise the driver loads fine when the phone is "booted". I dont know jack about rooting phones and have never done it before. I had this one lying around and thought I'd try it. Hopefully all this helps to narrow down the issue.
Click to expand...
Click to collapse
Thanks for pointing out the common .dll file. I will edit that in my thread for download. I am not sure on the MTP error. I have two of these Zone 3s lying around and neither gives any type of error on MTP. Almost certainly sounds like a driver related issue though. Im going to uninstall drivers and everything on my end, do factory resets, and reinstall everything and walk back through the process from scratch. See if I can pinpoint the issue.
MotoJunkie01 said:
Thanks for pointing out the common .dll file. I will edit that in my thread for download. I am not sure on the MTP error. I have two of these Zone 3s lying around and neither gives any type of error on MTP. Almost certainly sounds like a driver related issue though. Im going to uninstall drivers and everything on my end, do factory resets, and reinstall everything and walk back through the process from scratch. See if I can pinpoint the issue.
Click to expand...
Click to collapse
like roscoemctavish i was able to grab the LGUP_common.dll file and put it into ..\LG Electronics\LGUP\model\common and then LGUP started detecting my phone. It only takes the kdz file type under the Upgrade selection. But like roscoemctavish i ran into the 'unsecured image secured device' error. Still code 10 on the MTP driver but i don't think it's related to this. Maybe though.
Metalchic said:
like roscoemctavish i was able to grab the LGUP_common.dll file and put it into ..\LG Electronics\LGUP\model\common and then LGUP started detecting my phone. It only takes the kdz file type under the Upgrade selection. But like roscoemctavish i ran into the 'unsecured image secured device' error. Still code 10 on the MTP driver but i don't think it's related to this. Maybe though.
Click to expand...
Click to collapse
So in your instance, did the .kdz file flash for you with no issue or did it stop at some point?
MotoJunkie01 said:
So in your instance, did the .kdz file flash for you with no issue or did it stop at some point?
Click to expand...
Click to collapse
stopped at 9% with the "Secure device, But Unsecure image" error the other guy was having.
Metalchic said:
stopped at 9% with the "Secure device, But Unsecure image" error the other guy was having.
Click to expand...
Click to collapse
OK. So both you guys having the stop at 9% please try this. Rename the VS425PP2 file to the filename VS425PP6. Then flash the .kdz.
For now I'm editing the thread down to unbricking via the Verizon LG utility and I'll give links to the .kdz files. It's back to the drawing board guys. I'm very sorry. Please know that I am working hard on it.
MotoJunkie01 said:
For now I'm editing the thread down to unbricking via the Verizon LG utility and I'll give links to the .kdz files. It's back to the drawing board guys. I'm very sorry. Please know that I am working hard on it.
Click to expand...
Click to collapse
No worries man and I appreciate just having this as a potential option. If it matters I have tried to root my phone with Kingoroot. Of course it fails but the software status has changed to "modified". Current software version is VS425PP5.
I did try changing the filename "VS425PP2_02_ARB00.kdz" to "VS425PP6.kdz" and flashing with the same result (Stops at 9% with unsecure image error). There is a log file in the "\LGUP\model\common\LOG" folder which when opened in notepad produces unreadable text. Let me know if I can provide anything else.
Thanks!
Hi Guys,
Im new to the forums so i hope this is the right place for this post
I have a hardbricked oneplus one 64GB.
I have read and followed mutiple guides here and on youtube on how ot unbrick it.
But in every guide i followed mine "failed" at the same step.
When i start the "oneplus one recovery tool" or Msm8974DownloadTool this happens; (cant seem to use a link so ill try to explain it).
It starts with one green bar, when that is finished it stops an i hear the disconnected device sound.
I am currently on Win 10 but i also tried it on WinXP since mutiple posts suggested hat it would work better, but that also didnt help.
I also tried diffrent drivers (oneplus driver from the color zip), google multi driver, qualcomm driver etc.
Hope someone can help
Tiic said:
Hi Guys,
Im new to the forums so i hope this is the right place for this post
I have a hardbricked oneplus one 64GB.
I have read and followed mutiple guides here and on youtube on how ot unbrick it.
But in every guide i followed mine "failed" at the same step.
When i start the "oneplus one recovery tool" or Msm8974DownloadTool this happens; (cant seem to use a link so ill try to explain it).
It starts with one green bar, when that is finished it stops an i hear the disconnected device sound.
I am currently on Win 10 but i also tried it on WinXP since mutiple posts suggested hat it would work better, but that also didnt help.
I also tried diffrent drivers (oneplus driver from the color zip), google multi driver, qualcomm driver etc.
Hope someone can help
Click to expand...
Click to collapse
How your device got bricked?
Which recovery tool you tried?
Mr.Ak said:
How your device got bricked?
Which recovery tool you tried?
Click to expand...
Click to collapse
I don't have all the info since i got the phone from a "friend" who was about to throw it out, but ill do my best to provide accurate info
According to the privious owner the flashing of a custom rom or recovery went wrong and it ended up in it's current state.
The recovery tools i tried are;
- Oneplus one recovery tool by; Zyxxeil
- Oneplus one toolkit 1.5 by Manudroid19
- Msm8974DownloadTool
Tiic said:
I don't have all the info since i got the phone from a "friend" who was about to throw it out, but ill do my best to provide accurate info
According to the privious owner the flashing of a custom rom or recovery went wrong and it ended up in it's current state.
The recovery tools i tried are;
- Oneplus one recovery tool by; Zyxxeil
- Oneplus one toolkit 1.5 by Manudroid19
- Msm8974DownloadTool
Click to expand...
Click to collapse
Use the one with cm11s by Zyxxeil.Use Xp and use Qualcomm drivers,as this tool doesn't use fast boot/adb drivers and instead uses USB debugging port.
It need a few tries before device getting detected.
Make sure the device is getting recognized as "Qhs_bulk" or "Qualcomm diagnostics 9006" or some thing like that then install drivers manually.Also try different ports and refresh the toolkit. Open the toolkit with administrator rights.
Hope this helps
Mr.Ak said:
Use the one with cm11s by Zyxxeil.Use Xp and use Qualcomm drivers,as this tool doesn't use fast boot/adb drivers and instead uses USB debugging port.
It need a few tries before device getting detected.
Make sure the device is getting recognized as "Qhs_bulk" or "Qualcomm diagnostics 9006" or some thing like that then install drivers manually.Also try different ports and refresh the toolkit. Open the toolkit with administrator rights.
Hope this helps
Click to expand...
Click to collapse
I'm on windows xp now.
Made a clean install to be sure.
Phone is connected as Qualcomm HS-USB QDLoader 9008
The Zyxxeil tool recognizes it as a com port.
When i press start, it starts flashing 8974_msimage.mbn
When it finishes it just does the same. It looks like it's stuck on a loop at flashing 8974_msimage.mbn
I would post some pictures but i can't since im a new user
Edit; It is the same as this guy; youtube (dot) com/watch?v=TOw3-yX57jM
Flashing 8974_msimage.mbn nin a loop.... you're not the only one with this problem. I couldn't find a solution to this problem so far. Have tried fresh installs of Windows XP and Windows 7 and drivers installed in Test Mode without success. Please report back once you could figure out what's wrong.
Tiic said:
I'm on windows xp now.
Made a clean install to be sure.
Phone is connected as Qualcomm HS-USB QDLoader 9008
The Zyxxeil tool recognizes it as a com port.
When i press start, it starts flashing 8974_msimage.mbn
When it finishes it just does the same. It looks like it's stuck on a loop at flashing 8974_msimage.mbn
I would post some pictures but i can't since im a new user
Edit; It is the same as this guy; youtube (dot) com/watch?v=TOw3-yX57jM
Click to expand...
Click to collapse
Got it,it's because of a bad download or corrupt zip perhaps.Redownload the toolkit and also try with Color Os toolkit too.
If your device is recognized then there's no way you can't bring it back to life.
Mr.Ak said:
Got it,it's because of a bad download or corrupt zip perhaps.Redownload the toolkit and also try with Color Os toolkit too.
If your device is recognized then there's no way you can't bring it back to life.
Click to expand...
Click to collapse
Just redownloaded the tools and tried again.
Still the same issue, i also tried the color os toolkit like you suggested.
I have the same issue too, keep installing 8974_msimage.mbn again and again.
I'm still open for sugestions since the issue is still there
Right click msm tool, and RUN AS ADMINISTRATOR.
Problem solved.
kthejoker20 said:
Right click msm tool, and RUN AS ADMINISTRATOR.
Problem solved.
Click to expand...
Click to collapse
Although it is correct that you must run it as admin, this isn't the issue at all. There are phones that appear to be broken beyond the point where you can fix it with software.
MrBrainstorm said:
Although it is correct that you must run it as admin, this isn't the issue at all..
Click to expand...
Click to collapse
Yep, i always run tools like this as admin, the issue is something else in this case, but i wouldn't know what exactly
I may have found a solution/work-around to the problem described (in case anyone's still trying to unbrick a OPO after all this time). I must warn, however, that I really have no idea what I'm doing as I'm new to all of this, and have blundered through with no real understanding of what's going on, so pay heed at your own risk. It uses Qualcomm's QFIL program and Zyxxeil's OPO unbricking tool. I want give detail in describing the steps involved, so this will be fairly long.
***background***
My 64GB OPO has for the past couple of months almost always failed to get past the first 6-7 seconds of booting, and powered off before reaching the Cyanogen animation. It did the same when booting into fastboot and recovery, and at some point it stopped being able to access recovery at all. Very rarely it would boot, but pressing the power button while it was on would cause it to crash a few seconds later. I discovered that it would consistently boot properly if volume up were tapped while holding down the power button before it vibrates and the OnePlus logo appears, but this fix simply stopped working recently, and so it became impossible to turn the OPO on. Before giving up on it, I decided it would be worth trying the hard unbricking tool based on the ColorOS installer by Zyxxeil. However, I had the problem where the tool continually repeats the step of flashing 8974_msimage.mbn without progressing any further, to which nobody ever seemed to find a solution. I may have found a way to get around the problem, however.
Even though the procedure seems to have worked, the phone still shuts down after a few seconds as it did before (so I suspect my device has a hardware problem, possibly with the power button, and there's nothing that can be done for it). This means that I can't confirm that the fix actually works, but only that it appears to have worked. What it did was:
1) unbricked the phone - it probably wasn't even bricked before, but it definitely was after the installer hung on 8974_msimage.mbn ; it wouldn't respond to the power button at all afterwards. Applying the workaround allowed it to show signs of life again.
2) installed the COS11 fastboot. I'm not sure and can't tell whether the rest of the OS is there or intact, but the fastboot logo has changed from the newer small one to the bigger one from older versions.
***the problem***
The standard method for dealing with a hard-bricked OPO is to use the ColorOS tool as described in the "[GUIDE] [UNBRICK] Unbrick Oneplus One" thread and then flash Cyanogen, or to use Zyxxeil's tool which goes straight there. A common issue in both is that after pressing start, the tools repeat the step of flashing 8974_msimage.mbn , seemingly disconnecting the phone each time, and never progressing beyond that. This happened to me as well. This will happen if the tool is not run as an administrator, but for some people the same problem is seen even if it's run as an administrator. To the best of my knowledge, nobody has posted a solution to this problem, but some have suggested using alternative methods such as using QFIL (which I have gotten to work) or MiFlash.
***potential solution***
From what I understand, QFIL does the same thing as the unbricking tool, only not automatically. I directed it to use the files provided by Zyxxeil's tool, and it was then able to do something that unbricked the device as described above. This is what I did: (all on Windows 10, *not* using the original cable)
Required files:
1) Obtain the Qualcomm QDLoader driver. I used the the Qualcomm HS-USB QDLoader 9008 2.1.0.5 x64 driver from Zyxxeil's tool's thread (page 5, #48).
2) Download Zyxxeil's tool. I used the 64GB version. Extract DRIVER.iso and run setup.exe as described. I'm not sure whether this actually did anything and presume manually installing the driver in 1) overrides this, but I'm including this for completeness.
3) Download QFIL version 1.0.0.2 . I originally used 2.0.0.5 , but this did not work (it produced the error "unable to read packet header. only read 0 bytes", to which the recommended solution was to use an older version). This can be run from the extracted folder. Open it once, and then close it again - it seems not to behave properly the first time it is run.
Preparation:
4) Create a new folder, for instance on the desktop, and give it a short name. Copy and paste (or just move) the contents of the "OnePlusRestoreTool" folder from Zyxxeil's tool into here. This step is because QFIL supposedly doesn't like long folder names or locations (I'm not sure whether this is true or not but there's no harm in making sure).
5) Install the QDloader driver: (the PC may need to be disconnected from the internet for this stage, I think Windows may try to automatically download and install incorrect drivers)
>Open device manager, then plug the OPO into the computer. It should come up after a few seconds under "Ports (COM & LPT)" as something like QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008. Mine originally showed up as "Quectel QDLoader 9008". If it comes up as a malfunctioned device ("Unknown USB Device") under "Universal Serial Bus controllers", try holding the power button on the OPO down for a few seconds, or holding it down for a few seconds at the same time as volume up. If it's still not recognised, try rebooting the PC and repeating this step.
>Right click on the device as it appears in device manager, select "Uninstall device", tick the box saying "Delete the driver software for this device", and click on "Uninstall".
>The OPO will disappear from device manager. Unplug and then replug it into the PC, and after a few seconds it should be recognised again, perhaps as "Unknown USB Device" again, requiring the same procedure as above. It should now show up as QHSUSB_BULK under "Ports (COM & LPT)"
>Right click on the device and select "Update driver", then "Browse my computer for driver software". Paste in the file path for the folder containing the driver as downloaded above, which will be called "20561190_ed08f7139a2028da454a6668162f44ac311facc0" if using the driver specified above. Ensure "Include subfolders" is ticked, and click on Next. This should install the driver, and because it's signed, it shouldn't present problems often encountered in this stage. Your device should now be called "Qualcomm HS-USB QDLoader 9008", with (COM#) after it.
Fix:
6) Restart the PC, leaving the phone plugged in. Open device manager again. At this point, if it is detected as a malfunctioned "Unknown USB Device", do not try to remedy it as described above - leave it as it is. This is exactly what happened in my case.
7) Run QFIL.exe as an administrator. I don't know whether this is actually necessary to run as an administrator, but seeing as problems arise in the normal methods from not doing so, it seems sensible. If the device is listed as "Unknown USB Device", then QFIL should say "No Port Available".
8) In QFIL, click on "Browse" in the "select programmer" section. Navigate to the folder where the contents of Zyxxeil's tool were copied/moved to, and open "prog_emmc_firehose_8979.mbn". Lower down, click on "Load XML", which should give you three files to choose from. As I couldn't fully boot my OPO afterwards I don't know which one is most appropriate, but I have tried the procedure with each and it worked for all of them. Perhaps start with rawprogram_unsparse.xml and if that doesn't work try the other two. Click Open, then select patch0.xml , then click Open again.
9) Paying attention to the QFIL window, hold down power+volume up until the text changes from "No Port Available" to "Qualcomm HS-USB QDLoader 9008 (COM#). Incidentally, this will also cause the device to change from "Unrecognised USB Device" to "Qualcomm HS-USB QDLoader 9008 (COM#)" in device manager. I believe that this step starts "Qualcomm's debugging mode" as explained in Zyxxeil's thread, and this is necessary for the process to work.
10) Click on "Download" (below "Load XML"). QFIL should do its thing, and if nothing has gone wrong the phone might be unbricked at the end of the process. Disconnect from the PC and see if it works.
In my experience, where this step did not work it gave one of two errors:
"unable to read packet header. only read 0 bytes" - this happens on the newer version of QFIL, which is why I used the older one.
"unable to download flash programmer using sahara protocol" - this was the troublesome one. I believe it means that the phone is not in Qualcomm's debugging mode. This would probably be the case if, for whatever reason, the PC recognised the phone immediately as Qualcomm HS-USB QDLoader 9008, and so it wasn't necessary to hold power+volume up for the PC to recognise it properly. In my case the program ran properly the first time but was interrupted because I hadn't transferred all of the right files to the target folder. After I had done this and tried again, it gave this error. I fixed this by holding down power+volume up, while the device was recognised, until the PC made a sound indicating something had been plugged in. The next attempt to download was successful.
If the procedure doesn't work properly, it might also be worth using one of the other two XML files mentioned in step 9.
*** ***
Anyway, after hours of searching and trial and error, this unbricked the phone, with it becoming responsive once more to button presses, despite still having the original problem of powering down during boot. It seems to have the CM11 fastboot as expected, and I was able to have my PC recognise it in the short time it stays on using fastboot devices. Other than that, I'm afraid I don't know how successful this was, or how successful it would be for other people. I hope this is useful nonetheless!
hi follow this guide https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
lg optimus 3d won't turn on after baseband v20c flash and reboot, using the power button or power button, volume down and 3d key.
If I keep power and volume down while it's connected to the pc, then click power/volume down not sure the exact sequence, it starts making 3 short usb sounds, pause, 1 usb sound, then repeats forever
If I keep device manager open, in other devices with exclamation mark "OMAP4430" appears and device manager refreshes each time the sounds repeat, but it won't do anything else. If I pull the USB cable "OMAP4430" dissapears and sound loop stops
How can I fix this?
service sais I overwritten the bootloader. Baseband zip that I picked around here didn't say anything about bootloader... so far it made my phone inoperable. I'm trying to get this to work: https://forum.xda-developers.com/showpost.php?p=33650068&postcount=46
I unbricked it following this tutorial: https://forum.xda-developers.com/showthread.php?t=2246001
I'm pasting my post while I had some trouble with it:
Got P920 and I think I deleted my bootloader with a baseband zip: https://forum.xda-developers.com/op...ont-baseband-v20c-flash-t3654606#post73445561
I get stuck at step 7, can't find "LG port", basically what I get is fastloader mode, not downloader mode and LG port
then I get stuck at step 11, can't see "LG Cosmo"
If I pick step 13 and try to load gb bootloader it sais "waiting on device" forever, same as on fastloader trying to replace boots
What am I doing wrong?
EDIT1: Decided to do this on laptop (xp) not pc (windows 7). Now I see in ports section (which in windows 7 I don't at all) "LGE Bluetooth TransPort (COM15), not as in the tutorial but at least it's something... I set that to COM41 as instructed. Will edit here if I get any further
EDIT2: if I keep vol+ pressed it won't enter fastboot with os hacking tool. After it did, it found another hardware which I pointed to the only driver it finds in os hacking tool package, that is omap4430 which I already have installed, but this new one gives a code 10 this device will not work message, so I believe I'm stuck at step 11 again because I see no LG Cosmo in device manager.
EDIT3: I looked inside Device Manager > Android Device > OMAP4430 FastBoot USB Device, and is described in "Location:" as Location 0 (LG COSMO) ... which dissapears in a minute like while typing this Have no idea if this is what I'm suppose to get at step 11
EDIT4: seems that's LG COSMO after all because at step 13 after rebooting OS HACKING it did flash the GB BootLoaders (wrote a few lines of text)
...aaand ... drumroll ... it rebooted in my last rom (king's)
WOOOT! THANK YOU! THANK YOU! THANK YOU!
phone unbricked!
Now back to the problem of getting a proper rom that doesn't consume my battery idly in a day like 4.x unlike froyo (2.2.2) which can keep idle for a week, and that also gets a signal... tried them all except back to froyo (2.2.2) :-/
Click to expand...
Click to collapse
Hello! First post here, bit of a doozy. I have a OnePlus 6 and this weekend I decided I'd try out LineageOS 18. I installed it fine and it works (phone isn't bricked) but I've decided I want to go back to Oxygen OS now. However, I'm having a lot of trouble making this happen.
I've been following all the various guides, which involve using MSM Tool to flash the stock ROM back to the phone, but it always hangs up when I hit "Start" on MSM Tool. It'll get stuck on "Waiting for Device," or sometimes I get "Open Serial Device Failed" and I've also gotten "Sahara Communication Failed."
It seems like I can get everything else right though, so I'm not sure why it hangs here. The phone, when plugged in, shows up in Device Manager as "Qualcomm HS-USB QDLoader 9008 (COM3)" like it should, and it also shows up in MSM Tool under COM 3, so it should be good, but it just never works when I hit "Start."
Does anyone have any ideas on what to do? It's not the end of the world but I'm having issues with Lineage and it would be real nice to be back on stock Oxygen OS. Thanks.
I wonder if you're on a USB 3.0 port. If so, try a USB 2.0 port. Cheers.
Kidneybot said:
Sahara Communication Failed
Click to expand...
Click to collapse
This might happen when you are using a USB 3.0 port. Try changing to a USB 2.0 port one.
Kidneybot said:
Open Serial Device Failed
Click to expand...
Click to collapse
This happens when 2 devices like printers or something uses the same COM port, make sure there is no weird serial devices are plugged in at the same time, also make sure your drivers are installed correctly and functioning.
When you get the Sahara message, leave the message on the screen and hold the power and volume up buttons on your phone. It will briefly re-establish connection then start the download. This worked for me when I had the problem. Good luck.
Greetings everyone. I didn’t find a thread for this specific phone model. So I am putting it up here. Few days back I decided to unlock the bootloader of my LG W41 (LM-K610IM) and upgrade to a custom ROM. So, I used fastboot mode to unlock the bootloader and up until now everything went like a dream. Problems started when I couldn't get a TWRP recovery for my specific model. I downloaded a generic one and first tried to push it to my recovery partition. That's when I learned my phone doesn't have a recovery partition. I don't know what came to me then I used fastboot flash command to flash the TWRP image to my boot partition. It was successful but my phone won't start after that. It was a softbrick. Only the LG logo started bootlooping. But the worse was still not over. In an attempt to restore my device I searched everywhere for the stock ROM as the official website is down, but couldn't find any. At last, I zeroed in on a similar device by the same manufacturer LG K52. It had the ditto hardware like LG W41. Even the model number was similar. So, I downloaded the KDZ file. Extracted the dz from the kdz and the boot.img from the dz using LG KDZ extractor . Made a scatter file using a Hovatek instruction and using WWR MTK tool and formatted my device using SP flash tool and flashed everything. Till now my device was detected by the Windows 11 PC as a LGE device. Anyways the SP tool successfully flashed everything but after that my won't turn on any more. It's total dead. It won't power on, pc won't recognize it. I have tried connecting using USB and all possible hardware key combinations. It is dead bricked I think. All because of my stupidity. Now my question is, does it have any hope left or should I throw it away and buy a new device? I am keeping my fingers crossed and hope to find a superhero
Edit 1: SP Flash tool doesn't see my device any more. I have all the specific drivers installed. From LG and from Mediatek.
Try LG Bridge or check lg-firmwares.com
or
buy/borrow second device and 1:1 clone with mtkclient
Thanks for the quick response, but I have already tried LG Bridge, LGUP . After soft brick LGUP was seeing device as "unknown at COM Port 9". After hard brick it doesn't see it any more. Actually my PC won't see the device anymore
The firmware is not available at LG-firmwares.com but I have requested for it there. Keeping fingers
you should be able to repair preloader from bootrom mode (BROM)
How to enter bootrom mode. I am sorry if it is a noob question
Soumyadip999 said:
How to enter bootrom mode. I am sorry if it is a noob question
Click to expand...
Click to collapse
XRed_CubeX said:
To put your device in BRom mode you may need a different key combination or a test point, find out on the internet how to put the device in BRom mode or ask various devs of that device
Click to expand...
Click to collapse
find KCOL0 test point and short to GND
https://forum.hovatek.com/thread-11802.html
Okay let me ask and I will follow up. Thank you for the amazing guidance. Let's see if the poor device could be saved
you should poll lsusb in linux while trying to connect usb with both vol keys pressed. disconnect battery from pcb if possible to ensure phone is off.