Problem
Hello,
After being frustrated by bugs in lollipop roms I decided to go completely stock with my OPO, so following instructions from this thread, I entered the phone in fastboot mode and clicked the flash-all.bat, and with utter carelessness I forgot to unzip the image file inside the zip file(cm-11.0-XNPH05Q-bacon-signed-fastboot.zip containing all the .img files) the command prompt showed "remote: flash write failure" then rebooting into fastboot, the the cm logo in fastboot in my OPO is gone the phone doesnt start anymore, no combination of volume keys+power key works.
I then followed this thread to unbrick my OPO and procured one XP laptop containing no previous android drivers, but after installing color os USB driver extracted from color.zip and connecting my OPO and pressing Vol UP + Power key does noting no vibration no pop up in laptop for driver installation, no nothing.
No new device is shown in Device Manager.
Can anyone help me with this?
Thank You.
Solution.
As my OPO had no signs of life and it was not detected by any computer, I took a different route. One thing I noticed was OPO was getting warm, so the phone was indeed ON. I decided to drain all the battery life out of OPO, How did I knew the all the battery is drained? Simple, the top portion as no longer getting warm. The to boot into fastboot I pressed Vol+ and Power key for few seconds and connected it the computer. The device manager showed QHSUSB_BULK but it didn't showed in OnePlusRestoreTool(64GB).exe list because the driver was not available to which I updated the QHUSB_BULK driver using Qualcomm 2012 driver and bamm there was my OPO in the list then I clicked Start button and after few mins I was looking at a fresh CM11S OPO with XNPH05Q OTA update ready for download.
The machine you originally used to flash this device doesn't recognize it anymore? Even just plugging the device in and pushing just the power button?
No, It simply doesn't show up in either system(the one with Win7 and other with XP)
S1611 said:
No, It simply doesn't show up in either system(the one with Win7 and other with XP)
Click to expand...
Click to collapse
Any vibrations from the phone? Any signs of life from your device?
TheROMGuy said:
Any vibrations from the phone? Any signs of life from your device?
Click to expand...
Click to collapse
Absolutely no sign of any life.
S1611 said:
Absolutely no sign of any life.
Click to expand...
Click to collapse
Tried holding down power for 20 seconds?
TheROMGuy said:
Tried holding down power for 20 seconds?
Click to expand...
Click to collapse
Yes, ive tried that too, holding vol up + power for more than 2 min does nothing Ive plug it to charger, seem to be getting warm, so its a relief that atleast there is nothing wrong about hardware
S1611 said:
Yes, ive tried that too, holding vol up + power for more than 2 min does nothing Ive plug it to charger, seem to be getting warm, so its a relief that atleast there is nothing wrong about hardware
Click to expand...
Click to collapse
That's excessively odd. With installing the drivers for the first time on the windows xp machine, did you plug in the device and install the drivers through the device manager?
TheROMGuy said:
That's excessively odd. With installing the drivers for the first time on the windows xp machine, did you plug in the device and install the drivers through the device manager?
Click to expand...
Click to collapse
No i let the driver from color os install completely without plugging the OPO, and then connected it and pressed Vol Up + Power for more than 20-30 secs nothing happened. The installer though sort of hanged at 95% mark for about 2 min on both the system.
S1611 said:
No i let the driver from color os install completely without plugging the OPO, and then connected it and pressed Vol Up + Power for more than 20-30 secs nothing happened. The installer though sort of hanged at 95% mark for about 2 min on both the system.
Click to expand...
Click to collapse
Have you tried to see if fastboot will recognize the device as is on either system? After plugging in and attempting to "power" the device on?
Nope, command 'fastboot devices' shows no device
S1611 said:
Nope, command 'fastboot devices' shows no device
Click to expand...
Click to collapse
Try uninstalling the drivers and plugging your device in and see if device manager shows anything at that point. Make sure to follow it like this. Don't install the drivers before hand just extract them to your desktop.
Once you have the drivers straightened out, connect your bricked phone to the computer and start it up by holding VolUp + Power to about 10 seconds, and let the computer do its thing. Don't install drivers if they are not installed by itself. Instead launch Msm8974DownloadTool.exe as Administrator (right click on Msm8974DownloadTool.exe and select "Run as administrator") from the extracted Color.zip archive. It will scan all the COM ports and find the phone. That's the one line that looks different in the list. The list is just a list of your com ports and devices. If you unplug the phone and move it to another port, it will show your bricked phone on a different line.
Clicking on "Enum" just rescans the busses. Clicking the big square button in upper right corner scans the phone and reports what's good and what's not. It takes a minute for the scan to finish.
If you don't see your phone in the list of com devices, try unplugging/plugging in your phone a couple times, and rebooting it with VolUP + Power (hold 10 seconds). You will see it in Device Manager as well.
Once you see the phone in the list, click Start. You should see the programs start writing different files to the phone. Each time it writes a file you'll see a progress bar. Once you see this process happening, smile, you know you will be good to go... After all files are written, the com line with your device will turn green. You're good, unplug and reboot your phone. It will boot to ColorOS, the Chinese OS that comes on OPO.
source: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
---------- Post added at 03:32 AM ---------- Previous post was at 03:13 AM ----------
This is all I can think of to do. If you're going to use the XP Machine. install the drivers using this.
Go to the extracted Color.zip folder and find Driver.iso. Extract Driver.iso. Inside the extracted folder find Setup.exe. Run Setup.exe to install the drivers. The installer is Chinese, but all you need to do is click through the prompts.
Then follow this word for word.
Once you have the drivers straightened out, connect your bricked phone to the computer and start it up by holding VolUp + Power to about 10 seconds, and let the computer do its thing. Don't install drivers if they are not installed by itself. Instead launch Msm8974DownloadTool.exe as Administrator (right click on Msm8974DownloadTool.exe and select "Run as administrator") from the extracted Color.zip archive. It will scan all the COM ports and find the phone. That's the one line that looks different in the list. The list is just a list of your com ports and devices. If you unplug the phone and move it to another port, it will show your bricked phone on a different line.
Clicking on "Enum" just rescans the busses. Clicking the big square button in upper right corner scans the phone and reports what's good and what's not. It takes a minute for the scan to finish.
If you don't see your phone in the list of com devices, try unplugging/plugging in your phone a couple times, and rebooting it with VolUP + Power (hold 10 seconds). You will see it in Device Manager as well.
Once you see the phone in the list, click Start. You should see the programs start writing different files to the phone. Each time it writes a file you'll see a progress bar. Once you see this process happening, smile, you know you will be good to go... After all files are written, the com line with your device will turn green. You're good, unplug and reboot your phone. It will boot to ColorOS, the Chinese OS that comes on OPO.
source: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
nope uninstalling driver does nothing. Downloader tool shows following log:
8974_msimage.mbn: OK
dynamic_nvbk.bin: OK
emmc_appsboot.mbn: OK
gpt_backup0.bin: OK
gpt_backup0_64G.bin: OK
gpt_main0.bin: OK
gpt_main0_64G.bin: OK
userdata.img: FAILED
userdata_64G.img: FAILED
rawprogram0.xml: OK
rawprogram0_64G.xml: OK
NON-HLOS.bin: OK
MPRG8974.mbn: OK
rpm.mbn: OK
sbl1.mbn: OK
sdi.mbn: OK
static_nvbk.bin: OK
tz.mbn: OK
boot.img: FAILED
cache.img: OK
persist.img: FAILED
recovery.img: FAILED
system.img: FAILED
S1611 said:
nope uninstalling driver does nothing.
Click to expand...
Click to collapse
Try this.
This is all I can think of to do. If you're going to use the XP Machine. install the drivers using this.
Go to the extracted Color.zip folder and find Driver.iso. Extract Driver.iso. Inside the extracted folder find Setup.exe. Run Setup.exe to install the drivers. The installer is Chinese, but all you need to do is click through the prompts.
Then follow this word for word.
Once you have the drivers straightened out, connect your bricked phone to the computer and start it up by holding VolUp + Power to about 10 seconds, and let the computer do its thing. Don't install drivers if they are not installed by itself. Instead launch Msm8974DownloadTool.exe as Administrator (right click on Msm8974DownloadTool.exe and select "Run as administrator") from the extracted Color.zip archive. It will scan all the COM ports and find the phone. That's the one line that looks different in the list. The list is just a list of your com ports and devices. If you unplug the phone and move it to another port, it will show your bricked phone on a different line.
Clicking on "Enum" just rescans the busses. Clicking the big square button in upper right corner scans the phone and reports what's good and what's not. It takes a minute for the scan to finish.
If you don't see your phone in the list of com devices, try unplugging/plugging in your phone a couple times, and rebooting it with VolUP + Power (hold 10 seconds). You will see it in Device Manager as well.
Once you see the phone in the list, click Start. You should see the programs start writing different files to the phone. Each time it writes a file you'll see a progress bar. Once you see this process happening, smile, you know you will be good to go... After all files are written, the com line with your device will turn green. You're good, unplug and reboot your phone. It will boot to ColorOS, the Chinese OS that comes on OPO.
source: http://forum.xda-developers.com/onep...s-one-t3013732
Downloader tool shows following log:
8974_msimage.mbn: OK
dynamic_nvbk.bin: OK
emmc_appsboot.mbn: OK
gpt_backup0.bin: OK
gpt_backup0_64G.bin: OK
gpt_main0.bin: OK
gpt_main0_64G.bin: OK
userdata.img: FAILED
userdata_64G.img: FAILED
rawprogram0.xml: OK
rawprogram0_64G.xml: OK
NON-HLOS.bin: OK
MPRG8974.mbn: OK
rpm.mbn: OK
sbl1.mbn: OK
sdi.mbn: OK
static_nvbk.bin: OK
tz.mbn: OK
boot.img: FAILED
cache.img: OK
persist.img: FAILED
recovery.img: FAILED
system.img: FAILED
S1611 said:
Downloader tool shows following log:
8974_msimage.mbn: OK
dynamic_nvbk.bin: OK
emmc_appsboot.mbn: OK
gpt_backup0.bin: OK
gpt_backup0_64G.bin: OK
gpt_main0.bin: OK
gpt_main0_64G.bin: OK
userdata.img: FAILED
userdata_64G.img: FAILED
rawprogram0.xml: OK
rawprogram0_64G.xml: OK
NON-HLOS.bin: OK
MPRG8974.mbn: OK
rpm.mbn: OK
sbl1.mbn: OK
sdi.mbn: OK
static_nvbk.bin: OK
tz.mbn: OK
boot.img: FAILED
cache.img: OK
persist.img: FAILED
recovery.img: FAILED
system.img: FAILED
Click to expand...
Click to collapse
so after doing this (connect your bricked phone to the computer and start it up by holding VolUp + Power to about 10 seconds) it did install the drivers?
doesnt seem to, coz it the same log that it gives by disconnecting the OPO, i think its the default log
S1611 said:
doesnt seem to, coz it the same log that it gives by disconnecting the OPO, i think its the default log
Click to expand...
Click to collapse
try this.
connect your bricked phone to the computer and start it up by holding VolUp + Power to about 10 seconds then
launch Msm8974DownloadTool.exe as Administrator (right click on Msm8974DownloadTool.exe and select "Run as administrator") from the extracted Color.zip archive then
Click the big square button in upper right corner scans the phone and reports what's good and what's not. It takes a minute for the scan to finish.
if it gives you a log, post that.
8974_msimage.mbn: OK
dynamic_nvbk.bin: OK
emmc_appsboot.mbn: OK
gpt_backup0.bin: OK
gpt_backup0_64G.bin: OK
gpt_main0.bin: OK
gpt_main0_64G.bin: OK
userdata.img: FAILED
userdata_64G.img: FAILED
rawprogram0.xml: OK
rawprogram0_64G.xml: OK
NON-HLOS.bin: OK
MPRG8974.mbn: OK
rpm.mbn: OK
sbl1.mbn: OK
sdi.mbn: OK
static_nvbk.bin: OK
tz.mbn: OK
boot.img: FAILED
cache.img: OK
persist.img: FAILED
recovery.img: FAILED
system.img: FAILED
S1611 said:
8974_msimage.mbn: OK
dynamic_nvbk.bin: OK
emmc_appsboot.mbn: OK
gpt_backup0.bin: OK
gpt_backup0_64G.bin: OK
gpt_main0.bin: OK
gpt_main0_64G.bin: OK
userdata.img: FAILED
userdata_64G.img: FAILED
rawprogram0.xml: OK
rawprogram0_64G.xml: OK
NON-HLOS.bin: OK
MPRG8974.mbn: OK
rpm.mbn: OK
sbl1.mbn: OK
sdi.mbn: OK
static_nvbk.bin: OK
tz.mbn: OK
boot.img: FAILED
cache.img: OK
persist.img: FAILED
recovery.img: FAILED
system.img: FAILED
Click to expand...
Click to collapse
Is your device on the list?
Related
Well, it was only a matter of time but while trying to fix my phone, it decided to brick itself. I was installing a RUU, and then it rebooted to bootloader but instead of loading that up, it just died. Completely. Doesn't charge, doesn't power on, no LED whatsoever. This was last night. However, this afternoon it randomly entered QHSUSB_DLOAD mode when I plugged it into USB, or I assume so anyway - as my PC installed drivers for "Qualcomm HS-USB QDLoader 9008 (COM3)".
I downloaded an Ubuntu live DVD to try some unbrick methods, but while doing so I pressed the power button on my phone, now it's become undetectable again. Plugging into USB doesn't detect anything on my PC.
My question is, does anyone know how to get the phone back in QHSUSB_DLOAD mode?
Assume you ate referring to this method:
http://forum.xda-developers.com/showthread.php?p=34076562
Dumb question but I assume you tried repressing the button again?
This method worked for me and I think we've had the same brick experience
Sent from my back from the dead One S
ATSPerson said:
Assume you ate referring to this method:
http://forum.xda-developers.com/showthread.php?p=34076562
Dumb question but I assume you tried repressing the button again?
This method worked for me and I think we've had the same brick experience
Sent from my back from the dead One S
Click to expand...
Click to collapse
I'm trying that method as we speak. I figured out how to get it back on QDL mode by pressing all three buttons a few times for a few seconds and it pops up. However, when I type the "ls /dev/sd*" command, I get this:
Code:
[email protected]:/dev$ ls /dev/sd*
ls: cannot access /dev/sd*: No such file or directory
Even though my device comes up as expected for that procedure:
Code:
Bus 002 Device 007: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Just wondering - in this step:
Now, hold power down on your phone for about 10 seconds*,OR until you see (QDL mode) disappear and let go, Then go to your second window and repeatedly run the following command
Click to expand...
Click to collapse
Should only the "QLD mode" part disappear or should the entire device disappear? Because when I press power for ~10 seconds, the entire device vanishes.
Yes it all sounds OK, but you start off with the QUSB message hold power down till it disappears (about 10 secs for me) then do the list command.
Should work
Sent from my back from the dead One S
ATSPerson said:
Yes it all sounds OK, but you start off with the QUSB message hold power down till it disappears (about 10 secs for me) then do the list command.
Should work
Sent from my back from the dead One S
Click to expand...
Click to collapse
Basically when I press power, the entire device disappears. And when I do ls /dev/sd* I still get the same error, there's nothing found.
djsubtronic said:
Basically when I press power, the entire device disappears. And when I do ls /dev/sd* I still get the same error, there's nothing found.
Click to expand...
Click to collapse
How long do you need to press the power button before it disappears? Disappearing when it is pressed for about 10 secs is normal... less idk..
btw check your dm
NOTE: Before we start, I have now googled it and in hindsight I probably should of left RM alone!
Anyway as the title states my O3D seems totally goosed! I selected the recovery flash in ROM Manager for P920, it rebooted and all it does now is show the logo for a second, vibrate then off. I tried the usual tutorial stuff...
Power button, Vol up battery in - it comes up 'USB Device Unrecognised' and then It also keeps popping up 'Unknown Device' however when I click on properties every entry is 'Unavailable'
Power button, Vol Down, battery in does nothing (tried it a million times)
If I do...
Power button, Vol up then apply the battery - Device Manager finds... 'LG Mobile USB Modem', 'MAP SMS' (Other Devices) and 'LGE Mobile Composite USB Device'
No sign of OMAP44xx so the flash tools don't see it... strangely LG Mobile Support Tool sees the phone and tries to update it however it says it has the latest firmware, when I use the update recover option it gets to 15% but then complains that it can't communicate with the phone.
Is it dead? :crying:
Any help would be much appreciated.
dont worry. its not dead. has happened to my phone a trillion times ..
all you need to is try as below:
1. without connecting phone to usb first hold down 3d button then volume down and keep pressing power untill it starts up and then off again , then release all 3 together as it is off and repeat (remember first 3d then volume down and then power). this time just let the power button go on lg logo but keep pressing the other 2.
2. if this doesnt work, then easiest method - download omap4boot for optimus v1.21 or all in one p920 v1.3 by XDA, remove battery, only press down the volume up button and while pressing connect usb. make sure you hear 1 ding of connect , 1 dong of disconnect then 2 dings of connect. after this the ding dong should end .. if you have all drivers installed , then it will install omap drivers. a window will pop up and everything will have a green check. once it does that you can install a custom recovery twrp or cwm using fastboot . boot into recovery and flash a rom.
still if doesnt work, have patience, post a reply and will tell other steps to proceed with .....
Thanks for your time RVBSD, unfortunately (although I will keep trying!)
In No. 1 - I get the first logo, but when I re-apply the 3D/V and power, I don't get the second logo.
In No.2 - I get the first ding/dong then just 1 ding, no sign of Mr OMAP! - I'll keep trying though.
Once u get the second ding and then this music stops, Open device manager. Look for lg usb modem and disable it. Then look for omap44 something. The device manager may be refreshing quickly. Somehow i had a chance to right click on omap device and chose update driver. Select manual and choose omap.inf from the folder that u have to download as per my previous reply. Restart computer and check again.
Alternatively you can install all inf manually, right click and install, before connecting the device.
Let me know
Sent from my LG-P920 using xda app-developers app
Again, thanks again for your input but I am still no further. I manually clicked the inf and it said it installed fine... but nothing changed in Device Manager. I then attempted to 'force' the driver on the unknown device, however after it installed it returned a 'Code 10' error... unable to start.
Even tried the service software 'LGNPST' but it couldn't even connect to the port! ho-hum...
i tried it again. even on my computer it didnt take the omap drivers this time.... strange .....
but i could install fastboot, then installed cwm recovery . then flashed a rooted rom and its working ...
1. Turn off your Phone, pull out battery.
2. download omap4boot-for_optimus-v1.21 (run "start_fastboot.bat" (it will wait until phone connected)
3. connect phone with USB cable without battery, the usbboot will start
4. insert battery while the usbboot is waiting, it gives 5 secs only
5. unplug USB cable the LG logo will appear with fastboot on top
6. download the attached files to your desktop and extract
7. open cmd and in cmd navigate to fastboot.exe location, where ever downloaded
8. run fastboot.exe from cmd and choose the cwm file to be pushed to your phone
command : fastboot -s flash recovery recovery-clockwork-6.0.1.9-p920.img
9. reboot device into recovery , try to wipe cache and factory reset and try to reboot
if this works it will take you to existing installed rom, then you can reboot to recovery and flash Su_Bbox_1.20.2_gazhead_signed.zip to root it
10. else copy a custom rom to sd card , insert in the mobile , reboot into recovery and flash the cutom rom
PLease help
CAn you tell me how can mount recovery partition
I was trying to flash BlissPop. It didn't flash. So, I decided to flash fastboot image of CM11s 44.
I issued this command :
Code:
fastboot flash modem NON-HLOS.bin
fastboot reboot-bootloader
fastboot flash sbl1 sbl1.mbn
fastboot reboot-bootloader
The flash sbl1 command gave an error.
I rebooted bootloader. The phone turned off, but it never turned on.
I don't know how could it brick my phone, because I've done it a few times without any error.
My battery was on 65% when I was doing all this. So, I don't suspect battery has died.
But, I'm charging the phone anyway. There is no lead, but the power bank shows that battery is taking charge.
When I connect the phone to PC, it shows no signs of any device connected. Device manager doesn't show any thing/any refresh.
I've tried to push the power button for about a minute for 5 times, as 1+1 site says.
I've tried vol up + power and vol down + power buttons. It doesn't boot it.
I've no access to fastboot, recovery, OS, anything.
Please, suggest me solutions.
Did you flash the firmware updates before you flashed bliss? There is a toolkit out there, linked in bliss thread, on how to unbrick. I'll see if I can't find it.
Sent from my A0001 using Tapatalk
---------- Post added at 11:49 PM ---------- Previous post was at 11:45 PM ----------
http://forum.xda-developers.com/showthread.php?p=58230647
First look at this perhaps. If not there is a toolkit out there to flash back to stock. Should be able to communicate w the phone if it can turn on at all.
Sent from my A0001 using Tapatalk
http://forum.xda-developers.com/showthread.php?p=58230647
First look at this perhaps. If not there is a toolkit out there to flash back to stock. Should be able to communicate w the phone if it can turn on at all.
Click to expand...
Click to collapse
Thanks. I looked at it.
But, as you said I can't do anything till the phone turns on even once.
BTW, I highly suspect battery drain, because I was in TWRP for long to take backup, flashing MultiROM, etc. TWRP is known to not allow charging, as reported by some people.
Can you tell me whether flashing sbl1 could have bricked it or not? It didn't fail to flash in past and it never caused problem.
I had flashed CM12 firmware update before flashing BlissPop. Could reflashing CM11s fastboot image over it cause problem. I think it should not, because fastboot image replace all things. What's your opinion?
Had the same problem. Try first leave it charging for 12 hours after that plug it in. Then get into fastboot this is not easy. Just hold vol up and power together for atv least 5 Sec.
Sent from my A0001 using XDA Free mobile app
I guess its possible. But I would do what falastine said. Charge it for some time. With a soft brick it may not show anything on the screen but could actually be on. So be patient trying to get the toolkit to find the phone. I've heard in another thread someone's phone did in fact connect but nothing was on the screen
Sent from my A0001 using Tapatalk
any progress on this? i think the exact same thing happened to me. was trying to flash back to CM11s using fastboot, but it died. now i dont get anything at all. no response to the chrager, or the computer or anything.
ive tried holding the power button, holding the vol keys with the pwr button, but no avail.
let me know if you figured it out!
Falastine said:
Had the same problem. Try first leave it charging for 12 hours after that plug it in. Then get into fastboot this is not easy. Just hold vol up and power together for atv least 5 Sec.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I left the phone in charge for 24 hours using original charger and wire.
Tried long presses for multiple times - nothing happens.
Tried vol up/ vol down combinations with power button for long nothing happens.
I am now waiting for 12 hours and then will plug it again, as some thread said.
In between I'm trying to download a tool from here : http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
I hope it detects my phone.
hassan3216 said:
any progress on this? i think the exact same thing happened to me. was trying to flash back to CM11s using fastboot, but it died. now i dont get anything at all. no response to the chrager, or the computer or anything.
ive tried holding the power button, holding the vol keys with the pwr button, but no avail.
let me know if you figured it out!
Click to expand...
Click to collapse
There is no progress.
It appears that we are in same situation.
I highly suspect dead battery, instead of dead phone. Anyway, I'll post updates.
Please, share if anything works for you.
I had the same problem and had to restore the phone with this tool:
https://forums.oneplus.net/threads/...ol-restore-stock-cm11s-fix-bricks-etc.237827/
I had many problems with the drivers and i had tot install the qualcom drivers http://sciencespaces.com/search/Qualcomm+HS-USB+Android+DIAG+9018/
The topic said that there is an issue with the modem and you have tot flash it manually but i don't have problems so far.
michaeldepotter said:
I had the same problem and had to restore the phone with this tool:
https://forums.oneplus.net/threads/...ol-restore-stock-cm11s-fix-bricks-etc.237827/
I had many problems with the drivers and i had tot install the qualcom drivers http://sciencespaces.com/search/Qualcomm+HS-USB+Android+DIAG+9018/
The topic said that there is an issue with the modem and you have tot flash it manually but i don't have problems so far.
Click to expand...
Click to collapse
@michaeldepotter
Thanks for writing here.
I'm following the thread mentioned by you.
But, the problem is that I don't know how to get the phone in Qualacom mode.
I don't whether my phone is on or off. So, I've tried to connect it with PC and pressing key mentioned in the thread. It didn't work.
If you could share your experience with me, it will be kind of you.
I've windows 8.1 64 bit.
I'm at work now but in a couple of hours i can give you more info how i did it
Sent from my A0001 using XDA Free mobile app
michaeldepotter said:
I'm at work now but in a couple of hours i can give you more info how i did it
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
@michaeldepotter,
Sure, no problem.
I'll be eagerly waiting.
mahastat said:
@michaeldepotter
Thanks for writing here.
I'm following the thread mentioned by you.
But, the problem is that I don't know how to get the phone in Qualacom mode.
I don't whether my phone is on or off. So, I've tried to connect it with PC and pressing key mentioned in the thread. It didn't work.
If you could share your experience with me, it will be kind of you.
I've windows 8.1 64 bit.
Click to expand...
Click to collapse
open your device manager in your pc and use volume up and power button while connected to pc to get into qualcom mode.most probably it would be detected as android fastboot interface just click on it and update the driver to qualcom usb serial interface then use http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851 this tool to recover
wilbur2brooks said:
open your device manager in your pc and use volume up and power button while connected to pc to get into qualcom mode.most probably it would be detected as android fastboot interface just click on it and update the driver to qualcom usb serial interface then use http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851 this tool to recover
Click to expand...
Click to collapse
@wilbur2brooks
Thanks for writing.
I could understand that once my phone is detected as even unknown device, I can install drivers and try to recover through the tool you mentioned.
But, the problem is that my phone is not recognized as anything. The Device Manager shows no reaction when I connect the phone to computer.
I have disabled driver signature on my Windows 8.1 64 bit. I've Qualacom drivers installed. Rebooted computer in disabled signature mode.
I've connected my device through official cable and I've tried the key combination mentioned.
My other devices show up when connected to PC, but 1+1 doesn't.
Any other thing which I could try.
I had left my phone in charging for 24 hours, but it doesn't wake it up.
Any suggestion is appreciated.
mahastat said:
@michaeldepotter
Thanks for writing here.
I'm following the thread mentioned by you.
But, the problem is that I don't know how to get the phone in Qualacom mode.
I don't whether my phone is on or off. So, I've tried to connect it with PC and pressing key mentioned in the thread. It didn't work.
If you could share your experience with me, it will be kind of you.
I have windows 8.1 64 bit.
Click to expand...
Click to collapse
So this is how i did it.
1. install the drivers from OPO (located in the .zip file from this tool https://forums.oneplus.net/threads/t...ks-etc.237827/ )
2. Open your device manager (Start - right click on computer - properties - devices manager)
3. Press on power + vol up for like 10 sec until you see a device showing up (called QHSUSB_BULK)
4. Download the qualcomdriver ( https://www.dropbox.com/s/vgujdut93m341qm/Qualcomm 2012.rar?dl=0 ). Right click on this devices and click on "Update Driver Software" -> "Browse my computer for driver software" -> locate the Qualcomm 2012\fre\Windows7 8 or vista folder depending on your setup. Update the driver.
5. Now the OPO tool should recognize your device. I turn off all my network connections so the usb device can't find other drivers. (in case windows overwrite the driver).
---------- Post added at 07:29 PM ---------- Previous post was at 07:07 PM ----------
Have you tried another PC?
Sent from my A0001 using XDA Free mobile app
michaeldepotter said:
So this is how i did it.
1. install the drivers from OPO (located in the .zip file from this tool https://forums.oneplus.net/threads/t...ks-etc.237827/ )
2. Open your device manager (Start - right click on computer - properties - devices manager)
3. Press on power + vol up for like 10 sec until you see a device showing up (called QHSUSB_BULK)
4. Download the qualcomdriver ( https://www.dropbox.com/s/vgujdut93m341qm/Qualcomm 2012.rar?dl=0 ). Right click on this devices and click on "Update Driver Software" -> "Browse my computer for driver software" -> locate the Qualcomm 2012\fre\Windows7 8 or vista folder depending on your setup. Update the driver.
5. Now the OPO tool should recognize your device. I turn off all my network connections so the usb device can't find other drivers. (in case windows overwrite the driver).
---------- Post added at 07:29 PM ---------- Previous post was at 07:07 PM ----------
Have you tried another PC?Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
The hard part is that I could not get the phone detected by PC as anything.
I followed the same key combination which you mentioned. It doesn't help.
Can you tell me if battery is totally depleted, will it be possible for phone to be detected?
I've tried to charge my phone with various chargers and power banks. The battery stays cold, the charger stays cold, power bank blinks and get depleted, but phone is not vibrating even on long press.
I've tried on virtual PC, a XP machine. And on other real XP PC.
Thanks for your help.
If you have some more suggestions based on information given by me, kindly post it again.
mahastat said:
@wilbur2brooks
Thanks for writing.
I could understand that once my phone is detected as even unknown device, I can install drivers and try to recover through the tool you mentioned.
But, the problem is that my phone is not recognized as anything. The Device Manager shows no reaction when I connect the phone to computer.
I have disabled driver signature on my Windows 8.1 64 bit. I've Qualacom drivers installed. Rebooted computer in disabled signature mode.
I've connected my device through official cable and I've tried the key combination mentioned.
My other devices show up when connected to PC, but 1+1 doesn't.
Any other thing which I could try.
I had left my phone in charging for 24 hours, but it doesn't wake it up.
Any suggestion is appreciated.
Click to expand...
Click to collapse
Even if your battery is depleted it should get detected in your machine when u press volume up and power while its connected to your pc.hold it for a minute this combination should show something also keep your pc volume up to hear any port connect discconect sounds.If this doesnt happen then your hardware is dead no other option but try to give it to opo for service.
So, nothing ever comes on the screen? Does the phone vibrate if you hold the power button for 20 seconds? If so, this might be of help, if it sounds like it's bricked: http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
wilbur2brooks said:
Even if your battery is depleted it should get detected in your machine when u press volume up and power while its connected to your pc.hold it for a minute this combination should show something also keep your pc volume up to hear any port connect discconect sounds.If this doesnt happen then your hardware is dead no other option but try to give it to opo for service.
Click to expand...
Click to collapse
I've PC volume UP, device manager in front and phone connect. Key combination brings nothing.
So, I think I'll take it to OPO Service Center now.
Thanks for helping me.
netbuzz said:
So, nothing ever comes on the screen? Does the phone vibrate if you hold the power button for 20 seconds? If so, this might be of help, if it sounds like it's bricked: http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
Nothing comes on screen, no vibrations. It's bricked.
Going to OPO Service Center.
Thanks for looking after my problem.
I appreciate all who took part in this thread to help me. Thanks.
Moderators may close this thread now.
i tried to update my lg ku5400, with the official lg pc companion, after the update completed, the phone failed to switched on, it ends up blinking word of prada. please help me to solve the problem
need help please T_T
Renz Kell said:
need help please T_T
Click to expand...
Click to collapse
If under warranty then claim it. Or try doing update again
Hard Reset or Flashing LG KU5400
Renz Kell said:
i tried to update my lg ku5400, with the official lg pc companion, after the update completed, the phone failed to switched on, it ends up blinking word of prada. please help me to solve the problem
Click to expand...
Click to collapse
Try updating it again.
Or try Hard Reset.
Turn off the phone, Press Power button, Vol (+)up button, and Vol (-)down button simultaneously.
If it didn't work (happened to me ), you may just flash it, the easiest way.
Download:
LGUnitedMobileDrive - (no need if you're using the same PC with lg pc companion)
KDZFlashUtility.rar
V20I_00.kdz or V20D_00.kdz (I'd go for V20I_00.kdz)
1. Put your phone in S/W download mode: Turn it off, connect USB to PC, then plug in your phone.
Quickly, press both power button and Vol (+)up button. Screen should show S/W. See attached SS.
Wait for PC to recognize your phone.
2. Extract KDZFlashUtility.rar in a folder on your desktop. (on SS, I named the folder "KDZ")
3. Double click UpTestEX.exe
4. On "Select model.dll", click browse and choose "LGMUpgradeDL.dll". (it's in the "KDZ" folder)
5. On "PhoneMode", it's "DIAG" by default.
6. On "Select S/W file", click browse and select .kdz file you've downloaded. (V20I_00.kdz or V20D_00.kdz)
7. Now, click "Phone Type check and call Startupgrade".
The program will stop responding, a little patience would be nice, it's just extracting KDZ, so, don't worry.
*See attached SS for ref.
8. When it reaches IParam 95, your phone will automatically restart.
Wait for your phone to completely reboot and you're done!!!
P.S.
If it didn't work, choose "EMERGENCY" on "PhoneMode".
Hope this helps!!!
1) stuck in bootloader
2) changed to B slot thru terminal . following a thread I guess
3) got into recovery (.IMG) but couldn't flash zip
4) seen "edl" and thought, what's that? So I clicked it
5) screen now blank
6) buttons have no response
7) I've owned the phone for 2 days (new)
Am I out a lot of $ or is there a hope for me
does your computer detect the phone at all when you plug it in? I know it isn't responsive, but try powering it on when you plug it in via USB and see if your PC detects anything.
Seems like you stuck at edl mode. Try holding vol down (or up) + power buttons for at least 30 seconds. Than you can try flashing stock rom from fastboot mode.
alexkalicharan said:
does your computer detect the phone at all when you plug it in? I know it isn't responsive, but try powering it on when you plug it in via USB and see if your PC detects anything.
Click to expand...
Click to collapse
Everytine I plug it in (windows8: test mode) the PC makes a sound but can't seem t find the device in the device manager.
Msmdownload tool finds nothing
Hold volume up + power button together for 10 to 30 seconds. Then release. Wait a few seconds. Now press and hold power button until it vibrates to see if it boots
alexkalicharan said:
does your computer detect the phone at all when you plug it in? I know it isn't responsive, but try powering it on when you plug it in via USB and see if your PC detects anything.
Click to expand...
Click to collapse
elmarian756 said:
Hold volume up + power button together for 10 to 30 seconds. Then release. Wait a few seconds. Now press and hold power button until it vibrates to see if it boots
Click to expand...
Click to collapse
Used a newer PC, w/win 10
Held volume up+down + power , plugged in USB to PC
Held those 3 buttons until of made a second sound
(almost 30 secs)
I can now see battery charging, woohoo
I seriously can't wait to installed mclroG
And rid myself from G00g1e
Still reading hard brick guide
I apologize to everyone reading this but sometimes you have to interact w/ someone to get the solve
elmarian756 said:
Hold volume up + power button together for 10 to 30 seconds. Then release. Wait a few seconds. Now press and hold power button until it vibrates to see if it boots
Click to expand...
Click to collapse
OnePlus 7pro bought directly from OnePlus
( i think its GM1915)
windows 10 pc
device manager lists phone as Kedacom USB Device ---> Android Bootloader Interface
i downloaded "10.0.3-GLOBAL-OnePlus7ProOxygen_21.O.23_OTA_023_all_1912032357_76b445-FASTBOOT"
ran the "flash-all" batch file
when it's done, phone reboots into "Qualcomm: CrashDump"
I can press the up+down volume buttons w/ the power button and get back to Fastboot mode
I can also get into the Chinese mode.. with that, i click ENGLISH then WIPE EVERYTHING
still no luck.... truly is an interesting BRICK
Well, you can try flashing using "TOOL ALL IN ONE".
Did you try the MSMtool?
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691/amp/
I also bricked mine a couple days ago , restored it by using MNSTOOL , you can find threads or youtube videos how to use it , it will finish it in around 5 minutes and also it will lock the bootloader.
Zed Kay said:
Did you try the MSMtool?
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691/amp/
Click to expand...
Click to collapse
so many times i've tried the msmdownload tool
my device is not recognized... so i figure it's the driver
i followed the instructions.. it says with phone off ,hold the vol up+down for 5 secs then plug in to usb on pc
the drivers should auto download into the pc
it did.. i see in Device Manager under PORTS the qualcomm driver appear when phone is plugged in
but phone is in Qualcomm CrashDump mode
when i reboot to FASTBOOT MODE (by holding volume up+down and power button) the Device Manager
recognizes the phone as Kedacom USB Device/Android Bootloader Interface
(not Qualcomm)
and of course MSMDownload tool does not recognize phone... i'll keep trying
csmooth2001 said:
so many times i've tried the msmdownload tool
my device is not recognized... so i figure it's the driver
i followed the instructions.. it says with phone off ,hold the vol up+down for 5 secs then plug in to usb on pc
the drivers should auto download into the pc
it did.. i see in Device Manager under PORTS the qualcomm driver appear when phone is plugged in
but phone is in Qualcomm CrashDump mode
when i reboot to FASTBOOT MODE (by holding volume up+down and power button) the Device Manager
recognizes the phone as Kedacom USB Device/Android Bootloader Interface
(not Qualcomm)
and of course MSMDownload tool does not recognize phone... i'll keep trying
Click to expand...
Click to collapse
I will tell you the full guide.
1. Extract msm(whatever).zip
2. Turn off your phone
3. Open msm.exe (green icon) as admin
5. Hold vol+ and vol- for 30 (no less)
5. Connect usb while holding both volume buttons and release after connecting the usb
6. As soon as you connect the usb hit start.
msmtool does not recognize
Zed Kay said:
Did you try the MSMtool?
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691/amp/
Click to expand...
Click to collapse
i figure it's the driver.. windows keeps installing a specific driver for the phone.
but i think it's the wrong driver
(doesnt say QUALCOMM in the device manager)
so now i have to force install the driver
by right clicking on the phone in the device manager and working thru the menu to get to 'HAVE DISK'
so i have to be in windows as an admin
https://www.technipages.com/windows-administrator-account-login-screen
then after downloading the Qualcomm driver in a .cab file as admin i can right click and choose install .cab file
***AAAAAND nope can't right click to have "install" appear in the menu
FUDGE FUDGE FUDGE
all because windows says the driver is already installed... and has a kaed???? driver instead of the Qualcomm
can my life with this phone be any more difficult??
csmooth2001 said:
i figure it's the driver.. windows keeps installing a specific driver for the phone.
but i think it's the wrong driver
(doesnt say QUALCOMM in the device manager)
so now i have to force install the driver
by right clicking on the phone in the device manager and working thru the menu to get to 'HAVE DISK'
so i have to be in windows as an admin
https://www.technipages.com/windows-administrator-account-login-screen
then after downloading the Qualcomm driver in a .cab file as admin i can right click and choose install .cab file
***AAAAAND nope can't right click to have "install" appear in the menu
FUDGE FUDGE FUDGE
Click to expand...
Click to collapse
You can just use the drivers which are provided in the msm archive.
tried manually install a .cab with a terminal command as admin
but i get error "An error occurred trying to open - c:\usb.cab Error: 0x80070003
maybe i have to rename it KB(+number).cab in order for it to work (instead of usb.cab)
NOPE THAT DIDNT WORK
Zed Kay said:
Did you try the MSMtool?
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691/amp/
Click to expand...
Click to collapse
Zed Kay said:
You can just use the drivers which are provided in the msm archive.
Click to expand...
Click to collapse
I'll try that
NOPE!!!
pop window states
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
csmooth2001 said:
I'll try that
NOPE!!!
pop window states
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
Click to expand...
Click to collapse
What do you see in device manager while the phone is connected?
---------- Post added at 02:16 PM ---------- Previous post was at 02:13 PM ----------
csmooth2001 said:
I'll try that
NOPE!!!
pop window states
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
Click to expand...
Click to collapse
L2 drivers>qcser64>view signature>view certificate>install certificate>next>next>finish then reboot
my phone is GM1915
which is tmobile (even though i bought it directly from OnePlus)
so i will search for downloads for that
**on a mission**
Msmtool is what you need to use. You will recover it for sure
csmooth2001 said:
my phone is GM1915
which is tmobile (even though i bought it directly from OnePlus)
so i will search for downloads for that
**on a mission**
Click to expand...
Click to collapse
currently trying --> https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947