Been searching on these forums for the last 6 hours, trying a number of different solutions, and I haven't found an answer yet. I am going to go back through step-by-step through the night in my next post unless someone else appears with a solution, first, starting with using fastboot to flash the firmware images again.
I had attempted to install CWM 12 on my LG G2 D80020u today. It didn't work, but when I attempted to recover, I hit a wall.
I found a few solutions for my problem, but they assume Windows PC, and I'm running Ubuntu Linux.
Currently:
If I reboot normally with the device unplugged, I get the LG logo with "security error"
I CAN access fastboot and erase/flash various images, but none have solved my issue yet
I CAN get to Download Mode, but my linux computer cannot see the device to transfer files.
I CANNOT use ADP. I could earlier, but now when I type "adp devices", my terminal displays no devices.
If I run ./ioroot.sh, I get "Waiting on ADB detection" and then a stand-still.
Any ideas? Thanks for all of the help.
Hi everyone,
I have received my new Idol 3 4.7 (6039Y, european version) yesterday. I was stupid enough to apply all proposed updates before reading the forums thoroughly, so I got stuck with a 01005 build, with fastboot disabled.
I followed petrov.0’s guide to restore fastboot: http://forum.xda-developers.com/idol-3/development/6039-guide-how-to-return-fastboot-t3201077 or at least I tried.
I chose the files for "6039Y (repartitioned by following the repartitioning guide)" in the hope that it would save me some further work. QFIL seemed happy, but on restart, there was a message complaining about something like "unencryption failed", then saying that it was necessary to wipe the memory and perform factory reset. Then the phone spent some time wiping the data, and reboot took me to the stock recovery with a big nasty red error message.
So I used Alcatel Mobile Upgrade to restore the stock system, which went fine, but I was still stuck with a 01005 build. Then I tried again to follow petrov.0’s instructions, now using the files for "6039Y (8GB stock partition sizes)". According to QFIL's log, all went fine (except it waited forever in the final step, after the phone rebooted).
Once rebooted, the phone works ok, "adb devices" lists the phone, but "fastboot devices" still doesn’t.
Does anyone have the same problem? Any idea on how to solve it?
P.S.: this is my first post so I can't reply to petrov.0’s thread, and I couldn't find a Q&A thread on this subject, so here it is.
Fastboot -i 0x1bbb devices should be the right syntax. You have to directly adresy the devices by add “-i 0x1bbb“. Next zimě try to use search and read a little before posting stupid questions.
?
DallasCZ said:
Fastboot -i 0x1bbb devices should be the right syntax. You have to directly adresy the devices by add “-i 0x1bbb“. Next zimě try to use search and read a little before posting stupid questions.
Click to expand...
Click to collapse
No need to be rude : of course, I also tested the "fastboot -i 0x1bbb devices" with no more success.
(AFAIK, the -i option is just a filter: am I wrong?)
Turns out I was even more stupid than DallasCZ thought: my problem was that I used the fastboot commands in recovery mode rather than fastboot mode!
In case anyone as dumb as I passes by: use "adb reboot-bootloader" before trying any fastboot command.
And I confirm that the phone is NOT listed if I omit the -i option. The man page is really not clear about that: maybe the XDA-University guide about fastboot http://forum.xda-developers.com/showthread.php?t=2277112 could mention this kind of quirk?
Sorry for the noise.
I really have failed to restore fastboot commands using @petrov.0 's guide.
The problem I had having failed at flashing a modified OTA update file...well to cut a long story short I resorted to using Alcatels Mobile Upgrade Q 4.9.2 to fix my phone. I have no windows so was running the program on Linux host using VirtualBox. After loads of trouble with the drivers with 64 bit windows XP finally got everything to work using Windows 7.
I thought it would now be simple to restore fastboot commands using QFIL and to get my awesome 16GB internal memory back but despite phone definitely being in download mode and the phone showing up as Android HS-USB QDLoader 9008 on COM6 and QFIL automatically choosing COM6 etc and following everything in the guide as it should be I got an error when I hit the download button. Something about the phone not being in Firehose mode. I tried again and this time the error was about Sahara.
Anyone have any ideas?! Is it perhaps just not possible through Virtualbox?
Please help me! I want my 16GB internal memory back!
(phone is 6039Y-2AALWE7 and Upgrade Q updated it from 1AB2AZ22 to 1AJEAZE0)
fastboot - no permisions
deleted - found a simple solution.... for fastboot command in linux you need "sudo"!
Thank you
deleted
please a moderator wipe this post
gridmuncher said:
I really have failed to restore fastboot commands using @petrov.0 's guide.
The problem I had having failed at flashing a modified OTA update file...well to cut a long story short I resorted to using Alcatels Mobile Upgrade Q 4.9.2 to fix my phone. I have no windows so was running the program on Linux host using VirtualBox. After loads of trouble with the drivers with 64 bit windows XP finally got everything to work using Windows 7.
I thought it would now be simple to restore fastboot commands using QFIL and to get my awesome 16GB internal memory back but despite phone definitely being in download mode and the phone showing up as Android HS-USB QDLoader 9008 on COM6 and QFIL automatically choosing COM6 etc and following everything in the guide as it should be I got an error when I hit the download button. Something about the phone not being in Firehose mode. I tried again and this time the error was about Sahara.
Anyone have any ideas?! Is it perhaps just not possible through Virtualbox?
Please help me! I want my 16GB internal memory back!
(phone is 6039Y-2AALWE7 and Upgrade Q updated it from 1AB2AZ22 to 1AJEAZE0)
Click to expand...
Click to collapse
Any progress with this ?!? I'm a Linux user too, but I must admit that for this process I had to start my dusty Windows installation. As for the second attempt ... if the first one fails you must restart the phone in download mode again.
petrov.0 said:
Any progress with this ?
Click to expand...
Click to collapse
Sadly no. I don't understand why Upgrade Q would work in Virtualbox but QFIL doesn't. Still get the firehose error:
NOP: Fail Code: 10
Unable to send FireHose NOP, Device is not in Firehose mode!
Download Fail: System.Exception: Failed to send Firehose NOP to the phone
As I said before the phone is definitely in download mode and shows up in device manager correctly. I tried altering the USB filter in Virtualbox to be less device specific and a few other things, plugging unplugging, different usb cable, different usb port on laptop etc but no luck.
I might try a different Windows version but I think I'll probably resort to using a friends computer at some point.
Don't want to dual-boot windows as my laptop HDD is toooooooooo full and it would involve altering a few of my partitions etc.
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
I followed the instructions from another form for rooting LG G5 H8320:
https://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-t3384526
but did it without 1) enabling debugging mode or 2) doing the OEM unlock.
Seeing as I'm a complete noob, I didn't know to do this, and found out about this after reading a few other forums.
Device only boots to "Firmware update" screen now. Should I throw the device away? Or are one of you the second coming of our lord and savior and able to resurrect this thing from the dead?
JasonFam said:
I followed the instructions from another form for rooting LG G5 H8320:
https://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-t3384526
but did it without 1) enabling debugging mode or 2) doing the OEM unlock.
Seeing as I'm a complete noob, I didn't know to do this, and found out about this after reading a few other forums.
Device only boots to "Firmware update" screen now. Should I throw the device away? Or are one of you the second coming of our lord and savior and able to resurrect this thing from the dead?
Click to expand...
Click to collapse
Just to be clear, the instructions did not include these two steps as it was assumed noobs weren't reading I imagine?
Download LG program on your computer, and put the phone to download mode to restore it.
A brick means that it does not turn on at all due to software program.
bro if your device starts up and shows software update mode (download mode) you can flash official or tut using LGUP tool connecting it to PC...
have you tried flashing it with kdz files??
Doesnt work
hotsamfisher said:
bro if your device starts up and shows software update mode (download mode) you can flash official or tut using LGUP tool connecting it to PC...
have you tried flashing it with kdz files??
Click to expand...
Click to collapse
Doesn't work.
Tried LGUP I get error:
error: Error Code = 0x2BC, Invalid command response code = 0x80000121
Tried unlocking the bootloader, using adb and that doesnt work either since I didn't enable oem unlock:crying:
Hi all,
sorry if there is plenty of these threads already floating around but wasnt able to find a relevant one to my problem. I'm hoping someone here might be able to help.
This is the primary XZ rooting guide i have been following, with other supplimentary guides 1 & 2
These have been my steps:
- Managed to successfully update fastboot driver with "android_winusb.inf-file" from 'Google USB Driver' within android studio.
- Unlocked bootloader
- Installed AndroPlus Kernel sucessfully "fastboot flash boot boot.img"
Now went to reboot device as stated by instructions (mistake) and now the device is not recognized in cmd "waiting for device". I've replugged the usb in multiple ports and the device shows up as "android" in devices and printers. I go to update the android "SOMC Flash Device" to the platform tools directory but makes no difference in cmd. Still "waiting for device". In Device Manager there is no sign of the device either.
When the phone is turned on it shows your device has been "unlocked and cant be trusted will reboot in 5 seconds" then proceeds to xperia logo and freezes. With no recoveries theres not much options.
Is there a way to continue from here or even return to a previous state? It seems like i hit a brick wall. Please help
MugenG said:
Hi all,
sorry if there is plenty of these threads already floating around but wasnt able to find a relevant one to my problem. I'm hoping someone here might be able to help.
This is the primary XZ rooting guide i have been following, with other supplimentary guides 1 & 2
These have been my steps:
- Managed to successfully update fastboot driver with "android_winusb.inf-file" from 'Google USB Driver' within android studio.
- Unlocked bootloader
- Installed AndroPlus Kernel sucessfully "fastboot flash boot boot.img"
Now went to reboot device as stated by instructions (mistake) and now the device is not recognized in cmd "waiting for device". I've replugged the usb in multiple ports and the device shows up as "android" in devices and printers. I go to update the android "SOMC Flash Device" to the platform tools directory but makes no difference in cmd. Still "waiting for device". In Device Manager there is no sign of the device either.
When the phone is turned on it shows your device has been "unlocked and cant be trusted will reboot in 5 seconds" then proceeds to xperia logo and freezes. With no recoveries theres not much options.
Is there a way to continue from here or even return to a previous state? It seems like i hit a brick wall. Please help
Click to expand...
Click to collapse
Installed adb SystemWide?
adb drivers are Installed corrcetly? , better to reinstall them.