Related
I rooted the phone properly, then I installed a wrong kernel : hells-Core_b47-kk-CM_anykernel.zip (http://d-h.st/users/hellsgod/?fld_id=28949#files)
The phone doesn't boot up anymore, no fastboot, no adb, no hard factory reset. The only thing I can do is connect it to linux and send dd commands. I tried to push a new boot.img through that way but it didn't change anything. (I followed this guide : http://forum.xda-developers.com/showthread.php?t=2582142 with another boot.img obviously)
In Windows I get the QHSUSB_BULK USB device error.
Anyone could help me out?
Thanks!
= someone should pull boot partition for him so he can flash it.
With device off, you still have download/fastboot mode (Power & Volume + button) ?
If you have, find another PC with drivers properly installed.
Reflash all : http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
luminouche said:
With device off, you still have download/fastboot mode (Power & Volume + button) ?
If you have, find another PC with drivers properly installed.
Reflash all : http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Click to expand...
Click to collapse
How do you mean "Power & Volume + button"? When I hold power and volume button (I tried up, down and both together) it doesn't work. Screen stays black.
Power & Volume+ (Up, highest part of vol button) you should have fastboot mode.
luminouche said:
Power & Volume+ (Up, highest part of vol button) you should have fastboot mode.
Click to expand...
Click to collapse
Nope, that's not working.
Exactly which device is that kernel for and where did you find it? I think you've borked your partitions.
Transmitted via Bacon
timmaaa said:
Exactly which device is that kernel for and where did you find it? I think you've borked your partitions.
Transmitted via Bacon
Click to expand...
Click to collapse
It's for nexus4. I found it here I guess.
You guess? You didn't find it here, not in the OnePlus One section. My guess is you wandered into the N4 subforum by mistake. That's one very costly mistake. Unfortunately this is how flashing a kernel that's interned for an entirely different device usually ends. If you know it's for the Nexus, why on earth would you flash it on your OnePlus One?
Transmitted via Bacon
timmaaa said:
You guess? You didn't find it here, not in the OnePlus One section. My guess is you wandered into the N4 subforum by mistake. That's one very costly mistake. Unfortunately this is how flashing a kernel that's interned for an entirely different device usually ends. If you know it's for the Nexus, why on earth would you flash it on your OnePlus One?
Transmitted via Bacon
Click to expand...
Click to collapse
By "here" I meant in xdadevelopers forums. I know it's a mistake. And at that time I didn't know it was ONLY for nexus. Any idea how to unbork it?
I just noticed that it's showing up as QHSUSB_BULK on your PC, you're bricked. I believe the only possible solution is to have a jtag repair done on it. But, you're probably gonna have a hard time finding someone that does jtag repairs on this phone.
All in all, you've learned a really important (and expensive) lesson here. XDA is made up of device-specific sections, when you own a device you absolutely must stay within your device's subforum.
Transmitted via Bacon
timmaaa said:
I just noticed that it's showing up as QHSUSB_BULK on your PC, you're bricked. I believe the only possible solution is to have a jtag repair done on it. But, you're probably gonna have a hard time finding someone that does jtag repairs on this phone.
All in all, you've learned a really important (and expensive) lesson here. XDA is made up of device-specific sections, when you own a device you absolutely must stay within your device's subforum.
Transmitted via Bacon
Click to expand...
Click to collapse
Maybe I could try push recovery.img from http://forum.xda-developers.com/showthread.php?t=2780894 ?
All the files you may need are in this zip :
http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH25R-bacon-signed-fastboot.zip
DSwissK said:
Maybe I could try push recovery.img from http://forum.xda-developers.com/showthread.php?t=2780894 ?
Click to expand...
Click to collapse
You could try but judging from experience I wouldn't get your hopes up too much.
Transmitted via Bacon
I tried to push recovery.img file and... no change. Still black screen, still no adb, no fastboot, no factory reset...
I think your time would be better spent tying to locate someone who does jtag repairs on this device. You can't push a recovery to a partition that doesn't exist anymore.
Transmitted via Bacon
timmaaa said:
I think your time would be better spent tying to locate someone who does jtag repairs on this device. You can't push a recovery to a partition that doesn't exist anymore.
Transmitted via Bacon
Click to expand...
Click to collapse
I think oneplus would repair his phone. At a cost though.
Sent from my One using Tapatalk
Yeah they would. But jtag would be cheaper. OnePlus will charge for a new main board.
Transmitted via Bacon
Unnecessary now.
Transmitted via Bacon
timmaaa said:
I think your time would be better spent tying to locate someone who does jtag repairs on this device. You can't push a recovery to a partition that doesn't exist anymore.
Transmitted via Bacon
Click to expand...
Click to collapse
Alright, thanks. I'll try to find someone in my country (Switzerland).
Guys i hard bricked my opo i can't even enter in fastboot or recovery.. I flashed color os kitkat version over the cm11s but i didn't like that so i did a wipe nd restored my backup of cm11s but cm11s was giving me some problems thn I flashed color os 1.2 custom rom thn voila it got bricked.. please help guys..
try to hold power button for 10 seconds and then go for recovery if its opening or fastboot.
OR ELSE
Use warranty
They will charge me for it??
DivyeshMehta10 said:
try to hold power button for 10 seconds and then go for recovery if its opening or fastboot.
OR ELSE
Use warranty
Click to expand...
Click to collapse
They will charge me for it??
There is a post somewhere on here that tells you how to go from ColorOS to CM11s..
I had some problems also.. I went from CM11s to ColorOS back to CM11s and got reboots and FCs...
You need to manually reflash all the files through fastboot and not through recovery... after I did that, worked no problem...
gd6noob said:
There is a post somewhere on here that tells you how to go from ColorOS to CM11s..
I had some problems also.. I went from CM11s to ColorOS back to CM11s and got reboots and FCs...
You need to manually reflash all the files through fastboot and not through recovery... after I did that, worked no problem...
Click to expand...
Click to collapse
But i can't go in fastboot mode so how can i use adb?
tufail.budoo said:
Guys i hard bricked my opo i can't even enter in fastboot or recovery.. I flashed color os kitkat version over the cm11s but i didn't like that so i did a wipe nd restored my backup of cm11s but cm11s was giving me some problems thn I flashed color os 1.2 custom rom thn voila it got bricked.. please help guys..
Click to expand...
Click to collapse
have gone through a full hard brick where I couldnt even boot into anything (even fastboot!). this guide saved my oneplus one
follow it and your good to go
NOTE: this is for a complete full hard brick.. you wouldn't see anything at all jst on the screen when you try to boot it. jst a small vibration and jst nothing on display.
Wrong kernel : black screen, no fastboot, no adb, no factory reset
linezero said:
have gone through a full hard brick where I couldnt even boot into anything (even fastboot!). this guide saved my oneplus one
follow it and your good to go
NOTE: this is for a complete full hard brick.. you wouldn't see anything at all jst on the screen when you try to boot it. jst a small vibration and jst nothing on display.
Wrong kernel : black screen, no fastboot, no adb, no factory reset
Click to expand...
Click to collapse
yes u r right bro same here.. no fastboot nothing just black screen.. it was giving me small vibration till now but now it's not giving that too..
tufail.budoo said:
yes u r right bro same here.. no fastboot nothing just black screen.. it was giving me small vibration till now but now it's not giving that too..
Click to expand...
Click to collapse
maybe you ran out of battery...put it on charge for a while and go with the steps on that link. hopefully you will make it to the shore post your troubles here and i'll try my best to help you out
What was your remaining battery when you were flashing?
linezero said:
maybe you ran out of battery...put it on charge for a while and go with the steps on that link. hopefully you will make it to the shore post your troubles here and i'll try my best to help you out
Click to expand...
Click to collapse
maybe but when i try to plug it in charger it does nothing not a single vibration..
tufail.budoo said:
maybe but when i try to plug it in charger it does nothing not a single vibration..
Click to expand...
Click to collapse
maybe keep it for a while? and also try to boot into fastboot mode just by holding the vol up+ and power button while connected to the pc to check if it installs any Qualcomm drivers. and yeah u wont see anything on ur phone display again.
CafeKampuchia said:
What was your remaining battery when you were flashing?
Click to expand...
Click to collapse
I bricked my opo 2 days before nd while flashing i had 58%..
linezero said:
maybe keep it for a while? and also try to boot into fastboot mode just by holding the vol up+ and power button while connected to the pc to check if it installs any Qualcomm drivers. and yeah u wont see anything on ur phone display again.
Click to expand...
Click to collapse
Ok i will keep it for a while... nd btw m using win7
tufail.budoo said:
Ok i will keep it for a while... nd btw m using win7
Click to expand...
Click to collapse
that makes it easier so its good
Charge the device for a while and then try this:
http://forum.xda-developers.com/showthread.php?t=2991851
timmaaa said:
Charge the device for a while and then try this:
http://forum.xda-developers.com/showthread.php?t=2991851
Click to expand...
Click to collapse
I kept my device on charge for about 1 hour but it does'nt give vibration feed back when trying to boot it or even trying to get in fastboot mode..
tufail.budoo said:
I kept my device on charge for about 1 hour but it does'nt give vibration feed back when trying to boot it or even trying to get in fastboot mode..
Click to expand...
Click to collapse
Never mind what it's currently doing, did you follow the instructions in that thread?
Transmitted via Bacon
timmaaa said:
Charge the device for a while and then try this:
http://forum.xda-developers.com/showthread.php?t=2991851
Click to expand...
Click to collapse
I kept my device on charge for about 1 hour but it does'nt give vibration feed back when trying to boot it or even trying to get in fastboot mode.. it was giving before
timmaaa said:
Never mind what it's currently doing, did you follow the instructions in that thread?
Transmitted via Bacon
Click to expand...
Click to collapse
i cant open that download link.. its showing error
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
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
So I got the one for more than 6 months now. I have already the ghost touch, when the weather gets hot, the phone goes nuts!
But that's not the problem I'm trying to solve now. Today i was on CyanogenOS and decided to go back to cm11-38R, then flash 44R and etc. Re-do the steps I did one time that solved my screen problems for a long period of time. I downloaded the rooted 38R cm11 zip and installed/flashed and did a factory reset. All good until this.
But then the phone showed the 44S update. I downloaded it and clicked install. The recovery(clockworkmod) started, everything seemed allright. But then My phone died. No Cyanogen logo, no OnePlus logo, no nothing. Even when I connect it to the charger, no nothing, not even the charging led turn on. The only response I get that the phone is kinda of alive, is when I press the Power button for 10s, it vibrates but that's it, nothing else. Can anyone please help me? I guess my phone is bricked! LOL
You need this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Transmitted via Bacon
timmaaa said:
You need this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Transmitted via Bacon
Click to expand...
Click to collapse
Sir. Thank you very much! It worked perfectly, even using an windows 8 machine.