Database Info

At&t lg g3 (d850)

I hope someone can help? I have an AT&T LG G3 (D850) that boots up with an error message at the logo screen. It does not go any further than that. I can get the phone in recovery mode only. I have reset to factory several times. No luck. Additionally, my computer does not recognize that the G3 is connected, so can't use Odin to flash recovery.
Is there any way to get the phone to work again? Or, am I looking at a very expensive paper weight. I thank you in advance is you can help me out.

MuthaTrucker said:
I hope someone can help? I have an AT&T LG G3 (D850) that boots up with an error message at the logo screen. It does not go any further than that. I can get the phone in recovery mode only. I have reset to factory several times. No luck. Additionally, my computer does not recognize that the G3 is connected, so can't use Odin to flash recovery.
Is there any way to get the phone to work again? Or, am I looking at a very expensive paper weight. I thank you in advance is you can help me out.
Click to expand...
Click to collapse
can you get to download mode hold the volume up button while you plug the usb cable in to the phone

jerrycoffman45 said:
can you get to download mode hold the volume up button while you plug the usb cable in to the phone
Click to expand...
Click to collapse
No, I am not able to do so. The computer shows an error message about the device not being recognized. Thanks.

MuthaTrucker said:
No, I am not able to do so. The computer shows an error message about the device not being recognized. Thanks.
Click to expand...
Click to collapse
if you cant get to download mode then it is probably a brick call att for warrenty

jerrycoffman45 said:
if you cant get to download mode then it is probably a brick call att for warrenty
Click to expand...
Click to collapse
Thanks for your help. The phone was rooted, so I am sure that AT&T will say that I voided the warranty. But, it does not hurt to try.

If it won't boot they can't tell doubt they will check anyway

MuthaTrucker said:
I hope someone can help? I have an AT&T LG G3 (D850) that boots up with an error message at the logo screen. It does not go any further than that. I can get the phone in recovery mode only. I have reset to factory several times. No luck. Additionally, my computer does not recognize that the G3 is connected, so can't use Odin to flash recovery.
Is there any way to get the phone to work again? Or, am I looking at a very expensive paper weight. I thank you in advance is you can help me out.
Click to expand...
Click to collapse
Are you using Odin or the lg flash tool?
Sent from my LG-D850 using XDA Premium HD app

Intub8 said:
Are you using Odin or the lg flash tool?
Sent from my LG-D850 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for your response. Odin does not highlight a port, when the phone is connected. ADB says no device found. I think I will go to Best Buy and ask their Samsung Expert to update ROM, which might get it out of loop.

While in recovery you should be able to mtp xfer a stock rom to your downloads directory (SD card), and flash it, would be my hope. I believe you did say you can get to recovery.
What happened/changed that left it error booting?

JeffDC said:
While in recovery you should be able to mtp xfer a stock rom to your downloads directory (SD card), and flash it, would be my hope. I believe you did say you can get to recovery.
What happened/changed that left it error booting?
Click to expand...
Click to collapse
Maybe I am using the wrong term...I can hold the volume button down and power button to get it to a screen where I can wipe the data to factory. Besides that I cannot get to any other screen. I was trying to flash Philz recovery on the device. Thanks for taking the time to respond.

MuthaTrucker said:
Maybe I am using the wrong term...I can hold the volume button down and power button to get it to a screen where I can wipe the data to factory. Besides that I cannot get to any other screen. I was trying to flash Philz recovery on the device. Thanks for taking the time to respond.
Click to expand...
Click to collapse
you didnt answer the earler question are you using lg flash tool oden is for samsung

jerrycoffman45 said:
you didnt answer the earler question are you using lg flash tool oden is for samsung
Click to expand...
Click to collapse
I have downloaded the tool per your suggestion. However, I cannot get the phone into download mode, so I am back to square one. Thanks.

MuthaTrucker said:
I have downloaded the tool per your suggestion. However, I cannot get the phone into download mode, so I am back to square one. Thanks.
Click to expand...
Click to collapse
try this http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827

MuthaTrucker said:
Maybe I am using the wrong term...I can hold the volume button down and power button to get it to a screen where I can wipe the data to factory. Besides that I cannot get to any other screen. I was trying to flash Philz recovery on the device. Thanks for taking the time to respond.
Click to expand...
Click to collapse
Are you on OEM recovery? If on TWRP recovery you can MTP a file to the SD and flash via that. I'm not familiar with OEM recovery other than seeing it once.

JeffDC said:
Are you on OEM recovery? If on TWRP recovery you can MTP a file to the SD and flash via that. I'm not familiar with OEM recovery other than seeing it once.
Click to expand...
Click to collapse
First of all, thank you for all your responses. I really appreciate that. I ended up sending the phone to LG to be fixed. I just want the phone fixed and server as my backup now, since I bought the Samsung Note 4 and Gear S. Will update, when I hear back from LG. Thanks again.

Sounds to me that the drivers are not loaded correctly on the PC. If you can get to recovery you should be able to get to DL, I would think.

[Q] Bricked my One XL by flashing the wrong boot.img file

I was following Timmaaas 'How To' guide to a tee when I got to step #5 and and did the Reboot to find that my phone is now bricked. I was racking my brain trying to understand what I did wrong and I realize that I used the wrong Boot.img file when I flashed it!
I was having issues during the entire process and realized it was because I was using the CyanogenMod One X ROM instead of the XL. This was causing me to get an 'Error 7' until I switched to the XL and everything downloaded fine. However, I completely forgot to replace the Boot.img and ended up flashing my phone with the One X boot.img instead of the XL!
The phone is not responding at all. I did have it plugged into the computer and after it became bricked my computer downloaded the Qualcomm USB drivers for 9006 but its still not responding at all.
Is there anything I can do? It seems like all I need to do is change that one boot file and I would be golden. Please keep in mind this is my first Root so if you know of a way to fix I would really appreciate it if you can teach me in simple terms if possible.
Thanks so much! I really appreciate all you guys do at XDA you help an enormous amount of people. A donation from me is on the way! :good:
EDIT: I kept messing with the power button trying to boot it over and over and finally it launched to HTC one entry screen with the red text for a little less then 1 second but then shut back off. Maybe this gives some hope?

You're gonna need to get a jtag repair done. There's just no way for you to get the device to the bootloader in order to flash the right boot.img because it won't boot due to you borking the boot partition.
Transmitted via Bacon

BrickedAmbitions said:
EDIT: I kept messing with the power button trying to boot it over and over and finally it launched to HTC one entry screen with the red text for a little less then 1 second but then shut back off. Maybe this gives some hope?
Click to expand...
Click to collapse
Are you able to issue adb commands? If you're seeing the splash screen then you may not be completely bricked. If the device is still showing as qualcommUSB then you're likely out of luck though.

nem1yan said:
Are you able to issue adb commands? If you're seeing the splash screen then you may not be completely bricked. If the device is still showing as qualcommUSB then you're likely out of luck though.
Click to expand...
Click to collapse
No I can't issue any commands. I guess its toast, oh well. How do I get the jtag repairs done?

nem1yan said:
Are you able to issue adb commands? If you're seeing the splash screen then you may not be completely bricked. If the device is still showing as qualcommUSB then you're likely out of luck though.
Click to expand...
Click to collapse
There's no way the phone can get to the bootloader, it ain't gonna happen with a broken boot partition.
BrickedAmbitions said:
No I can't issue any commands. I guess its toast, oh well. How do I get the jtag repairs done?
Click to expand...
Click to collapse
You need to find a jtag repairer in your area.
Transmitted via Bacon

[Q] Dead after flashing stock rom - really dead

Hi there,
Today I tried to get back from cm12 to stock rom. I flashed, then tried to reboot ... nothing.
The phone is absolutely dead. No light when connected to power, no vibration when pressing the power button, no fast boot, no recovery mode. I tried to press power button over one minute, I tried to press for 20 seconds five times... nothing.
The device is absolutely dead. "adb devices" / "fastboot devices" show nothing, my Mac does not even see anything on the usb-port.
I cannot imagine how this is even possible. Is it really possible to destroy a device with flashing?
Has anybody have a hint for me?
S.

It's entirely possible to brick a device with flashing, in fact it's the most likely way to brick a device. Exactly what did you flash? And using what method?
Transmitted via Bacon

I used the method described here (xda-dev forum) with the stock rom from cygn.com : cm-11.0-XNPH44S-bacon-signed-fastboot.zip
all the flashes went fine, then I gave : "fastboot reboot" and got back " rebooting... finished. total time 0.005s". (And a black screen)...
What a pitty

McSvenster said:
I used the method described here (xda-dev forum) with the stock rom from cygn.com : cm-11.0-XNPH44S-bacon-signed-fastboot.zip
all the flashes went fine, then I gave : "fastboot reboot" and got back " rebooting... finished. total time 0.005s". (And a black screen)...
What a pitty
Click to expand...
Click to collapse
Did you use a toolkit or did you do it manually?

//edit
Wow somehow I got threads mixed up while switching back and forth from Tapatalk and chrome. Sorry ignore what I wrote lol.
From what I've read, the colorOS stuff is the way to recover from a bricked phone. I don't have any experience in it though so I can't help much there. I would seek advice from that colorOS thread and hopefully you're able to recover
Sent From Lollipopified Bacon Goodness!

ek69 said:
If going back from cm12 to cm11s then the cm11s firmware files need to be flashed also.
Are you able to get back into fast boot mode still?
Sent From Lollipopified Bacon Goodness!
Click to expand...
Click to collapse
The stock images contain the firmware so that isn't the issue.

The phone is practically dead, so colorOS seems to be no solution as I don't know how to flash it without usb connection. But thanks for the hint.
What I do not understand: What could have gone so wrong that the whole power circuit is damaged? I thought, that flashing only affects the internal "hard disk".
Does anyone know what exactly happens on powering on a working phone?

McSvenster said:
The phone is practically dead, so colorOS seems to be no solution as I don't know how to flash it without usb connection. But thanks for the hint.
What I do not understand: What could have gone so wrong that the whole power circuit is damaged? I thought, that flashing only affects the internal "hard disk".
Does anyone know what exactly happens on powering on a working phone?
Click to expand...
Click to collapse
Nobody said anything about the power circuit being damaged, and it almost definitely isn't. That isn't the cause of a brick, what's most likely wrong is the partitions are corrupted, so it has no information telling it how to boot, what to boot into, or even to boot at all.
You didn't answer my question earlier though, diff you flash manually or via a toolkit?
I'd suggest you try this out:
http://forum.xda-developers.com/showthread.php?t=2991851
Transmitted via Bacon

McSvenster said:
The phone is practically dead, so colorOS seems to be no solution as I don't know how to flash it without usb connection. But thanks for the hint.
What I do not understand: What could have gone so wrong that the whole power circuit is damaged? I thought, that flashing only affects the internal "hard disk".
Does anyone know what exactly happens on powering on a working phone?
Click to expand...
Click to collapse
Well, I'm not entirely sure but I think that when you press the power button, you connect two ends, one end has a signal and the other end doesnt, when those two connect, the one without the signal gets a signal which will result in a battery going on maybe? Of this last battery part I'm not sure but that's how I guess it works...

I did the same as you - This fixed it for me.
http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136
Basically you have to use a Windows computer and the original ColorOS firmware to fix your partitions. Follow this guide and it will flash your One with ColorOS, then you can flash TWRP and go on to flash CM11S.
It worked for me but it was a bit of a pain.

timmaaa said:
Nobody said anything about the power circuit being damaged, and it almost definitely isn't. That isn't the cause of a brick, what's most likely wrong is the partitions are corrupted, so it has no information telling it how to boot, what to boot into, or even to boot at all.
You didn't answer my question earlier though, diff you flash manually or via a toolkit?
I'd suggest you try this out:
http://forum.xda-developers.com/showthread.php?t=2991851
Transmitted via Bacon
Click to expand...
Click to collapse
Sorry, I mixed up two answers... I did it all with the fastboot commands (e.g. fastboot flash userdata cm11s\userdata_64G.img)
Thank you all a lot for your hints - I will try to fix it with a windows computer and keep you informed.

I'd suggest you try this out:
http://forum.xda-developers.com/show....php?t=2991851
Click to expand...
Click to collapse
Well, that did the trick, thank you very much! Using Windows the phone was detected as a Qualcom mass storage. I could then use the tool that directly flashed the stock cm11.
Again, thanks a lot!
All the best,
Sven

McSvenster said:
Well, that did the trick, thank you very much! Using Windows the phone was detected as a Qualcom mass storage. I could then use the tool that directly flashed the stock cm11.
Again, thanks a lot!
All the best,
Sven
Click to expand...
Click to collapse
Awesome news.
Transmitted via Bacon

Super hard bricked Oneplus One.

Okay, so I was flashing full stock + unroot using WugFresh Bacon Root Toolkit.
It got up to flashing the RPM, completed that and then rebooted into bootloader.. It never rebooted it just shut down and didn't come back on.
Dead screen, can't reboot into bootloader, fastboot, normal reboot, nothing on screen at all ever, the charging LED doesn't even come on.
Device is not recognised on my computer at all, under any device name.
Took the back casing off, unhooked the battery and rehooked it back on again.. Nothing.
Thinking the phone is well and truly f*cked.
What are my options guys? Contact Oneplus customer service and play roulette to see if I actually get a response from them within a 3 month period and then have to face the gigantic cost of posting the phone back to them from Australia on the hopes of getting a new one? Or just buy a new phone, the S6 just came out so that's an option.

Lesson: don't use toolkits.
Anyway, give this a try:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
If that doesn't revive your phone nothing will. There's no point in contacting OnePlus about this unless you're happy to pay for whatever repairs are needed, this doesn't fall under warranty.
Transmitted via Bacon

timmaaa said:
Lesson: don't use toolkits.
Anyway, give this a try:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
If that doesn't revive your phone nothing will. There's no point in contacting OnePlus about this unless you're happy to pay for whatever repairs are needed, this doesn't fall under warranty.
Transmitted via Bacon
Click to expand...
Click to collapse
Yeah like I said earlier.. It isn't recognised via USB at all. Thanks anyway.
It wasn't a fault of the toolkit, it was the fault of the phone itself. I use it because it saves me time, who can be arsed typing that manually when you have a .bat to do it for you?

Stevles said:
Yeah like I said earlier.. It isn't recognised via USB at all. Thanks anyway.
Click to expand...
Click to collapse
Yeah, and many of the people who have successfully revived their phones using that method weren't able to recognise their phone via usb to start with either. But hey, I guess it isn't worth trying.
Transmitted via Bacon

timmaaa said:
Yeah, and many of the people who have successfully revived their phones using that method weren't able to recognise their phone via usb to start with either. But hey, I guess it isn't worth trying.
Transmitted via Bacon
Click to expand...
Click to collapse
"A hardware bricked OPO has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition. The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OPO should be detected as QHSUSB_BULK USB"
AS I SAID the device is not showing up on the computer, AT ALL. Under any device name.
It does not vibrate when I hold the power button for 20 seconds, it has no ADB, no fastboot, no nothing.
But hey, thanks for being an arsehole about it. Really appreciate it.

Stevles said:
"A hardware bricked OPO has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition. The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OPO should be detected as QHSUSB_BULK USB"
AS I SAID the device is not showing up on the computer, AT ALL. Under any device name.
It does not vibrate when I hold the power button for 20 seconds, it has no ADB, no fastboot, no nothing.
But hey, thanks for being an arsehole about it. Really appreciate it.
Click to expand...
Click to collapse
I know what a hard brick is. And as I said, many people who thought they were hard-bricked have revived their phones with that method. It isn't your usual detect-by-fastboot fix. Isn't it worth a try? Others in your situation have had success with it.
Plus, if your phone is actually 100% hard-bricked, why are you posting here? If that's the case there's absolutely nothing that can be done. You came here looking for help, I'm giving you the link to the one thing that has a chance of saving your phone.
Transmitted via Bacon
---------- Post added at 12:40 ---------- Previous post was at 12:39 ----------
Jessooca said:
Wugfresh is the one of the most reputable and is the most downloaded developer on all of XDA look it up. So suggesting not to use toolkits is ridiculous.
Send me a PM of your issues and I'll see if I can't get you back up and running... Provide me all the details of what all your phone does and does not do, etc... I've read all that you've said above, so I suppose just tell me what it DOES so if anything, Thanks
- Jessooca
---------- Post added at 06:32 PM ---------- Previous post was at 06:31 PM ----------
+1
Click to expand...
Click to collapse
It doesn't matter how reputable a toolkit is, they cause problems, this thread is a testament to that. You can find many threads just like this one in this very q&a section that describe very similar issues after using a toolkit.
Transmitted via Bacon

timmaaa said:
I know what a hard brick is. And as I said, many people who thought they were hard-bricked have revived their phones with that method. It isn't your usual detect-by-fastboot fix. Isn't it worth a try? Others in your situation have had success with it.
Plus, if your phone is actually 100% hard-bricked, why are you posting here? If that's the case there's absolutely nothing that can be done. You came here looking for help, I'm giving you the link to the one thing that has a chance of saving your phone.
Transmitted via Bacon
---------- Post added at 12:40 ---------- Previous post was at 12:39 ----------
It doesn't matter how reputable a toolkit is, they cause problems, this thread is a testament to that. You can find many threads just like this one in this very q&a section that describe very similar issues after using a toolkit.
Transmitted via Bacon
Click to expand...
Click to collapse
Actually in this case I'm almost 100% sure it was due to the fact I had just installed Oxygen OS and was reverting back to stock from it. Had nothing to do with the toolkit. Not to mention, I have never had any problems with this toolkit in the past and I would still recommend it to people who want to save them self from hassle and wasting time. Thanks anyway.
By the way, anyone reading this: Stay the hell away from OxygenOS. Nothing but dramas from it, it seems. Not forgetting to mention the fact it is literally just a stock version of Lollipop anyway! Better off with CM12S or BlissPop or any of the CFW's out there.

Stevles said:
Actually in this case I'm almost 100% sure it was due to the fact I had just installed Oxygen OS and was reverting back to stock from it. Had nothing to do with the toolkit. Not to mention, I have never had any problems with this toolkit in the past and I would still recommend it to people who want to save them self from hassle and wasting time. Thanks anyway.
By the way, anyone reading this: Stay the hell away from OxygenOS. Nothing but dramas from it, it seems. Not forgetting to mention the fact it is literally just a stock version of Lollipop anyway! Better off with CM12S or BlissPop or any of the CFW's out there.
Click to expand...
Click to collapse
I agree that there are better ROMs available for this phone, but that's just our opinion, heaps of people have been looking for a stock aosp experience on this phone and I think Oxygen is as close as you could get. As for the ROM itself causing problems, I don't think that's it. I flashed it to test it out and went back to my previous ROM without a single issue (as have many others). I think it's a matter of taking the care to flash the right firmware/modem before reverting back to whatever ROM was running previously, otherwise it's kinda asking for trouble.
So have you tried the unbrick method I linked you to? I'm not saying it's definitely going to fix your problem. What I'm saying is there have been several cases of this phone showing all the signs of being hard bricked, without it actually being hard bricked, and that's the fix that saved those phones. You might be hard bricked, or your phone might fall into the category that I just mentioned, but at this point anything has to be worth a try.
Transmitted via Bacon

timmaaa said:
I agree that there are better ROMs available for this phone, but that's just our opinion, heaps of people have been looking for a stock aosp experience on this phone and I think Oxygen is as close as you could get. As for the ROM itself causing problems, I don't think that's it. I flashed it to test it out and went back to my previous ROM without a single issue (as have many others). I think it's a matter of taking the care to flash the right firmware/modem before reverting back to whatever ROM was running previously, otherwise it's kinda asking for trouble.
So have you tried the unbrick method I linked you to? I'm not saying it's definitely going to fix your problem. What I'm saying is there have been several cases of this phone showing all the signs of being hard bricked, without it actually being hard bricked, and that's the fix that saved those phones. You might be hard bricked, or your phone might fall into the category that I just mentioned, but at this point anything has to be worth a try.
Transmitted via Bacon
Click to expand...
Click to collapse
Read through it and the sole problem of why it won't work is that there is no communication with my phone via my computer at all. The point of that tutorial is to unbrick your device by manipulating what your computer see's as the device (Qualcomm generic hardware ID being reported) unfortunately I can't even see that. I think it's just a lost cause unfortunately. But thank you for taking an interest.
UPDATE: Wow what do you know? After trying for an hour of powering on/off and trying to fastboot and flashmode and all that jazz and no luck, tried it on my laptop and sure enough it popped up with the Qualcomm generic driver ID. Whole bunch of screwing around and now it is booting into ColosOS. Thanks guys for the links and offers of help!

Stevles said:
Read through it and the sole problem of why it won't work is that there is no communication with my phone via my computer at all. The point of that tutorial is to unbrick your device by manipulating what your computer see's as the device (Qualcomm generic hardware ID being reported) unfortunately I can't even see that. I think it's just a lost cause unfortunately. But thank you for taking an interest.
UPDATE: Wow what do you know? After trying for an hour of powering on/off and trying to fastboot and flashmode and all that jazz and no luck, tried it on my laptop and sure enough it popped up with the Qualcomm generic driver ID. Whole bunch of screwing around and now it is booting into ColosOS. Thanks guys for the links and offers of help!
Click to expand...
Click to collapse
Lol, I knew that was going to get your phone up and running again [emoji14]
Very glad to see that your phone has been revived from the dead
Transmitted via Bacon

timmaaa said:
Lol, I knew that was going to get your phone up and running again [emoji14]
Very glad to see that your phone has been revived from the dead
Transmitted via Bacon
Click to expand...
Click to collapse
You earn a medal!
You can even help people who don't want to get helped
Way to go, Tim

Same thing happen to me whike swithing back to stoc. After using oxygen but i m flashing the factory images flashall.bat but after this hard brick my device after changing or trying able to connect my like bulkusb kind of in device manager and use one plus one recovery toolkit 1.0 it will brink my complete dead one plus one to life try buddy

rakesh595160 said:
Same thing happen to me whike swithing back to stoc. After using oxygen but i m flashing the factory images flashall.bat but after this hard brick my device after changing or trying able to connect my like bulkusb kind of in device manager and use one plus one recovery toolkit 1.0 it will brink my complete dead one plus one to life try buddy
Click to expand...
Click to collapse
Yeah, I'm just gonna wait for the CM12S OTA. Tried most every other ROM and was not impressed. This being said, I'm still buying an S6 in two days. Will be keeping my OPO to satisfy my ROM flashing/android manipulating needs and using the S6 for everything else a smart phone offers

Stevles said:
UPDATE: Wow what do you know? After trying for an hour of powering on/off and trying to fastboot and flashmode and all that jazz and no luck, tried it on my laptop and sure enough it popped up with the Qualcomm generic driver ID. Whole bunch of screwing around and now it is booting into ColosOS. Thanks guys for the links and offers of help!
Click to expand...
Click to collapse
How did u get it unbricked / ur PC to recognize ur OPO? Im having the same hard brick issue... my OPO is completely dead, doesnt even charge at all too. :crying:

MatLiamSousa said:
How did u get it unbricked / ur PC to recognize ur OPO? Im having the same hard brick issue... my OPO is completely dead, doesnt even charge at all too. :crying:
Click to expand...
Click to collapse
Try plugging it into a different computer.. That was what worked for me.
Don't know if it was necessary (in fact I am almost certain it isn't) but In my haste I took off the back cover and unscrewed a thousand small screws with my jewellers kit and unplugged the battery and plugged it back in. Like I said, not necessary.
Even if it doesn't look like it's charging.. If you can't see it on a computer at all then keep it on charge for a few hours anyway.. It can't hurt.
Best of luck!

Stevles said:
Okay, so I was flashing full stock + unroot using WugFresh Bacon Root Toolkit.
It got up to flashing the RPM, completed that and then rebooted into bootloader.. It never rebooted it just shut down and didn't come back on.
Dead screen, can't reboot into bootloader, fastboot, normal reboot, nothing on screen at all ever, the charging LED doesn't even come on.
Device is not recognised on my computer at all, under any device name.
Took the back casing off, unhooked the battery and rehooked it back on again.. Nothing.
Thinking the phone is well and truly f*cked.
What are my options guys? Contact Oneplus customer service and play roulette to see if I actually get a response from them within a 3 month period and then have to face the gigantic cost of posting the phone back to them from Australia on the hopes of getting a new one? Or just buy a new phone, the S6 just came out so that's an option.
Click to expand...
Click to collapse
hello buddy,
i got same situation like yours. but the only different thing is when i connect my opo to my laptop and press the power button with vol up key it connects to my laptop showing QHUSB_BULK. I update it with ANDROID ADB INTERFACE and it does but thats it nothing else. i cant go fastboot or adb.
CAN YOU PLEASE tell me how you fixed your super hard bricked opo like mine...
thank you.

dewan555 said:
hello buddy,
i got same situation like yours. but the only different thing is when i connect my opo to my laptop and press the power button with vol up key it connects to my laptop showing QHUSB_BULK. I update it with ANDROID ADB INTERFACE and it does but thats it nothing else. i cant go fastboot or adb.
CAN YOU PLEASE tell me how you fixed your super hard bricked opo like mine...
thank you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
From previous comment on thread.

dewan555 said:
hello buddy,
i got same situation like yours. but the only different thing is when i connect my opo to my laptop and press the power button with vol up key it connects to my laptop showing QHUSB_BULK. I update it with ANDROID ADB INTERFACE and it does but thats it nothing else. i cant go fastboot or adb.
CAN YOU PLEASE tell me how you fixed your super hard bricked opo like mine...
thank you.
Click to expand...
Click to collapse
No that is exactly like what happened to mine. Follow the guide to the letter and it'll fix it up if you did it right, it fixed mine.
Best of luck!

help plz
The step to install color fails every time. Suggestion plz....
Here is the log(both in windows 8.1 & xp) plz help...
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

mobasser said:
The step to install color fails every time. Suggestion plz....
Here is the log(both in windows 8.1 & xp) plz help...
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
Click to expand...
Click to collapse
Instead of posting this multiple times in various threads (double posting is against the rules) you should ask this question in the unbrick thread.
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732

My One is completely dead .. Please Help

I installed Oxygen OS and evrything was going fine until my rootchecker told me the root was incomplete and i somehow managed to remove my Entire operating system and format my entire sdcard trying to root . and was stuck in boot loop but after around 2 hours searching on forums i managed to reinstall Oxygen OS again ....thats where my real problem started, After flashing Oxygen .....70% of the phone functions were not functioning ....screen brightness adjustment ,,,on screen navigation, downloading apps , making calls , etc .... So , the genius me decided to revert back to stock using a guide which i cannot post the link to because i m a new user . and this is where things got beyond my control .. During this process my phone was on fast boot mode ..after which it went blank and the linux penguin appeard for a brief moment after which my phone completely died ....i have tried doing the 20 secs power button hold x 5 times ....no result .....after that i pluged it in to my charger ...have been charging for the past 30 mins now ...still no sign of life ....PLease help me :crying:

http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Transmitted via Bacon

timmaaa said:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Transmitted via Bacon
Click to expand...
Click to collapse
thnx but my one is showing no signs of life..not even a tiny blink...any suggestions ???

rikujamo said:
thnx but my one is showing no signs of life..not even a tiny blink...any suggestions ???
Click to expand...
Click to collapse
My suggestion is to try the method I linked you to. Plenty of people in your exact situation have saved their phone using that.
Transmitted via Bacon

Yeah, I was in the exact same situation. I thought the phone was completely hard bricked.
Just try to get into Qualcomm USB Mode many many times as described in the link posted by timmaaa. For me it worked after about 100 attempts.

Timma's method works for me try with patience

timmaaa said:
My suggestion is to try the method I linked you to. Plenty of people in your exact situation have saved their phone using that.
Transmitted via Bacon
Click to expand...
Click to collapse
Nothing happens when i connect my One to my laptop ....nothing appears on the device manager ...what do i do ???:crying:

rikujamo said:
Nothing happens when i connect my One to my laptop ....nothing appears on the device manager ...what do i do ???:crying:
Click to expand...
Click to collapse
Are you reading the other comments here and in the thread I linked you to?
Transmitted via Bacon

timmaaa said:
Are you reading the other comments here and in the thread I linked you to?
Transmitted via Bacon
Click to expand...
Click to collapse
HEYYY mannn.....it worked !!! ....I just had to press power +volume up button ...for windows to detect ....ColorOS installed successfully...THank you very much

rikujamo said:
HEYYY mannn.....it worked !!! ....I just had to press power +volume up button ...for windows to detect ....ColorOS installed successfully...THank you very much
Click to expand...
Click to collapse
You're welcome, glad to help.
Transmitted via Bacon