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
Related
This is my first post at XDA. I don't know if I am in the right section. Kindly move the post if required.
Problem
1) I had my Optimus One running CM9.
2) It made my phone slow. So, I flashed it back to CM7.
3) It had some problems, so i was foolish enough to move it back to Gingerbread instead of restoring to CM9.
4) This is where my phone started acting strange. It was getting into a boot loop.
5) I then tried to fix it using some tools I don't remember, but since then it has been dead.
The phone is dead. The phone won't turn on. Not even in emergency mode. No response when charger or USB is connected. It just wont turn on.
It was about 4 months ago when I bricked my phone and had lost hope. I have now known it's hard living without an android.
Please let me know how i can fix this and revive my bricked phone.
Some of you may have a good laugh reading this. But I already have tears in my eyes.:crying:
I dont remember what all i did to my phone in order to brick it. So, please help in whatever way you can.
Thanks to everyone in advance.
rocketonp500 said:
This is my first post at XDA. I don't know if I am in the right section. Kindly move the post if required.
Problem
1) I had my Optimus One running CM9.
2) It made my phone slow. So, I flashed it back to CM7.
3) It had some problems, so i was foolish enough to move it back to Gingerbread instead of restoring to CM9.
4) This is where my phone started acting strange. It was getting into a boot loop.
5) I then tried to fix it using some tools I don't remember, but since then it has been dead.
The phone is dead. The phone won't turn on. Not even in emergency mode. No response when charger or USB is connected. It just wont turn on.
It was about 4 months ago when I bricked my phone and had lost hope. I have now known it's hard living without an android.
Please let me know how i can fix this and revive my bricked phone.
Some of you may have a good laugh reading this. But I already have tears in my eyes.:crying:
I dont remember what all i did to my phone in order to brick it. So, please help in whatever way you can.
Thanks to everyone in advance.
Click to expand...
Click to collapse
Repair
Sent from a powerful Ice Creamy Device
Reviving my bricked p500
Thanks!!! I kinda guessed nothing could be done. But would have loved a fix. Would have saved bucks!!!
rocketonp500 said:
Thanks!!! I kinda guessed nothing could be done. But would have loved a fix. Would have saved bucks!!!
Click to expand...
Click to collapse
The thing is, if it doesn't respond then how are you going to fix it...that's the huge problem.
Moved to General Q&A.
Have you tried another charger? With and without battery.
-- Sent from my TouchPad using Communities
rocketonp500 said:
This is my first post at XDA. I don't know if I am in the right section. Kindly move the post if required.
Problem
1) I had my Optimus One running CM9.
2) It made my phone slow. So, I flashed it back to CM7.
3) It had some problems, so i was foolish enough to move it back to Gingerbread instead of restoring to CM9.
4) This is where my phone started acting strange. It was getting into a boot loop.
5) I then tried to fix it using some tools I don't remember, but since then it has been dead.
The phone is dead. The phone won't turn on. Not even in emergency mode. No response when charger or USB is connected. It just wont turn on.
It was about 4 months ago when I bricked my phone and had lost hope. I have now known it's hard living without an android.
Please let me know how i can fix this and revive my bricked phone.
Some of you may have a good laugh reading this. But I already have tears in my eyes.:crying:
I dont remember what all i did to my phone in order to brick it. So, please help in whatever way you can.
Thanks to everyone in advance.
Click to expand...
Click to collapse
It's an LG phone right?.. I also agree to Repair at the service center of your phone.. I recommend that because it's hard bricked.. When I was a newbie and accidentally soft bricked my galaxy pocket (bootloop) I bring it to the samsung service center I thought it will coast some bucks but it's free, they just reformat my phone for One hour and it's now fixed.. but now I use Odin for reformatting my phone using stock firmwares..
dumeds away,
I assume you searched the forum already, but maybe you didn't try this yet:
http://forum.xda-developers.com/showthread.php?t=883314
Hope it helps.
try putting it into download mode and connecting to the computer and checking with odin.i
Reviving P500
krishneelg3 said:
The thing is, if it doesn't respond then how are you going to fix it...that's the huge problem.
Click to expand...
Click to collapse
Yes!! There is no way I guess.
post-mortem said:
Have you tried another charger? With and without battery.
-- Sent from my TouchPad using Communities
Click to expand...
Click to collapse
Yes. I tried another chager, USB and stuff. My phone wont come up.
fozzyag said:
I assume you searched the forum already, but maybe you didn't try this yet:
http://forum.xda-developers.com/showthread.php?t=883314
Hope it helps.
Click to expand...
Click to collapse
I came across this thread. But, i cannot go into emergency mode. So, I am stuck.
aagampshah97 said:
try putting it into download mode and connecting to the computer and checking with odin.i
Click to expand...
Click to collapse
How to get into download mode? I dont really know if it would go into download mode.
Hmm , hopes are less but lets go on with the basics .
Did you try changing the battery ?
I don't think the download mode would work either but try doing the following :
Plug in the USB cable and wait for the charging screen to come on.
Now Press and HOLD the following Keys in the same order: Return Button, Volume Down Button, and the Power Button.
Let go off all the buttons when you first see the LG logo.
Then install cm9 again with odin .
If none works then you either have to go with a new phone or maybe a simple part of the phone has become dead . If it's under warranty get it replaced / repaired .
Alright i got 6 hours before tmbobile store opens and i can HOPEFULLY get an exchange, but not banking on it. btw im new to rooting so i wasnt familiar with the process, but regardless i have hard bricked my NEXUS 5. Title says the problem. I followed wwjoshdew's guide to rooting on youtube, and rooted successfully. But i could'nt for the life of me figure out how to create nandroid. I ended up realizing i didnt download cmw recovery mode and downloaded it from the play store. the app took me to a button that said flash recovery and i hit it and my phone asked for permission from unknown source, i hit ok and it shut down, on 70% battery life. Not turning on please help
Try to boot the phone into bootloader mode. Just hold volume down and the power button. From there try to cycle to recovery. You use your volume down to cycle through the options and power but as select. If you can boot into recovery and have that successfully installed then you can erase your phone and try to power it on from there. If you didn't successful install the custom recovery then you'll have the standard Android recovery. You can erase everything from that too.
These phones are hard to brick and not be able to fix it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
ruben8448 said:
Try to boot the phone into bootloader mode. Just hold volume down and the power button. From there try to cycle to recovery. You use your volume down to cycle through the options and power but as select. If you can boot into recovery and have that successfully installed then you can erase your phone and try to power it on from there. If you didn't successful install the custom recovery then you'll have the standard Android recovery. You can erase everything from that too.
These phones are hard to brick and not be able to fix it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Doesn't turn on dude. No matter what. I am new to roms but i know what a hard brick is.
You should really read the guides and stickied threads at the top of these forums. The guides are very noob friendly and you wouldn't have bricked your phone. There's one to reset your device to stock as well. There's really no need for this thread and on top of that there is a sticky that says no questions in the General forums.
Sent from my Nexus 5 using Tapatalk
Determine your phone is actually off. Plug your phone into charge, if a battery sign appears in the middle of the screen then your phone is off.
If your phone is off, hold down the volume down button with the power button to start the bootloader, press volume down twice and press the power button to enter recovery.
If your screen remains black and doesn't show a battery logo, hold the volume up, volume down and power buttons at the same time for a minute, then let go and hold down the power button. Which should hopefully start your phone.
FuMMoD said:
You should really read the guides and stickied threads at the top of these forums. The guides are very noob friendly and you wouldn't have bricked your phone. There's one to reset your device to stock as well. There's really no need for this thread and on top of that there is a sticky that says no questions in the General forums.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You should have been around long enough to know that when newbies break their new toys they go nuclear and dismiss all the information around them.
BNNEBULA said:
Alright i got 6 hours before tmbobile store opens and i can HOPEFULLY get an exchange, but not banking on it. btw im new to rooting so i wasnt familiar with the process, but regardless i have hard bricked my NEXUS 5. Title says the problem. I followed wwjoshdew's guide to rooting on youtube, and rooted successfully. But i could'nt for the life of me figure out how to create nandroid. I ended up realizing i didnt download cmw recovery mode and downloaded it from the play store. the app took me to a button that said flash recovery and i hit it and my phone asked for permission from unknown source, i hit ok and it shut down, on 70% battery life. Not turning on please help
Click to expand...
Click to collapse
You bricked a Nexus?
Hold down Volume Down, Up, and Power to get into fastboot mode. Restore from Factory Image.
Normally, to root a nexus, I fastboot Team Win Recovery Project.
Anyways what you did simply could not HARD BRICK the phone.
zeekiz said:
You should have been around long enough to know that when newbies break their new toys they go nuclear and dismiss all the information around them.
Click to expand...
Click to collapse
Seriously lol. Even though the guides are right there in their faces.
Sent from my Nexus 5 using Tapatalk
HELP SOS
FuMMoD said:
You should really read the guides and stickied threads at the top of these forums. The guides are very noob friendly and you wouldn't have bricked your phone. There's one to reset your device to stock as well. There's really no need for this thread and on top of that there is a sticky that says no questions in the General forums.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
My Nexus5 doesn't flash the Led light or enter bootloader and software . I was flashing the based CM kernel and i followed the instructions nicely, while using TWRP Recovery i pressed reboot system after the flash and the phone suddenly died. I connected it to the PC and the installing drivers popup appeared and it didn't install them, problem(QHSUSB_BULK) it only appeared once. And since that, phone is dead. PLEASE HELP!!!!
Yazan Abzakh171 said:
My Nexus5 doesn't flash the Led light or enter bootloader and software . I was flashing the based CM kernel and i followed the instructions nicely, while using TWRP Recovery i pressed reboot system after the flash and the phone suddenly died. I connected it to the PC and the installing drivers popup appeared and it didn't install them, problem(QHSUSB_BULK) it only appeared once. And since that, phone is dead. PLEASE HELP!!!!
Click to expand...
Click to collapse
Do you have a link to the kernel you flashed? I think you done bricked it good.
Were you using this method?
http://www.youtube.com/watch?v=w3beFx-3Ic4
If yes,I think then all Nexus 5 users should be warned about CF's autoroot issues,because I see more and more topics related to this issue.
Simonna said:
Were you using this method?
http://www.youtube.com/watch?v=w3beFx-3Ic4
If yes,I think then all Nexus 5 users should be warned about CF's autoroot issues,because I see more and more topics related to this issue.
Click to expand...
Click to collapse
I don't believe the issues you're seeing, appears to be failed emmc, is related to chain fire's auto root. Cf is probably the most popular method to root and it's a coincidence. I've seen these failures with other root methods too.
I think the op flashed a kernel not for his device.
jd1639 said:
I don't believe the issues you're seeing, appears to be failed emmc, is related to chain fire's auto root. Cf is probably the most popular method to root and it's a coincidence. I've seen these failures with other root methods too.
I think the op flashed a kernel not for his device.
Click to expand...
Click to collapse
I am not a developer so bear with me. I'm just a guy in mpls with a completely stock N5 from Google Play that encountered similar issue as the original post. There was no damage or water issue, or other problem prior to going dead. It had about 50% battery and maybe 15 minutes after reading an email it was dead when I looked at it again. It just simply turned off while in my pocket. I could not get it to power on or enter bootloader or a recovery screen. After a week of trying to charge via USB and the original wall charger and countless attempts to hold power and volume buttons without success, I decided to pop the back off and disconnected the battery. I put it back together, but that made no difference either. Google play will send me a new phone, but I'd like to get it fired up and extract the last week or so of pics. Any ideas? Again, I am a complete noob and this 3 month old phone has not been modified in any way, other than auto updates from Google play. Thanks for any assistance or guidance.
elf1967 said:
I am not a developer so bear with me. I'm just a guy in mpls with a completely stock N5 from Google Play that encountered similar issue as the original post. There was no damage or water issue, or other problem prior to going dead. It had about 50% battery and maybe 15 minutes after reading an email it was dead when I looked at it again. It just simply turned off while in my pocket. I could not get it to power on or enter bootloader or a recovery screen. After a week of trying to charge via USB and the original wall charger and countless attempts to hold power and volume buttons without success, I decided to pop the back off and disconnected the battery. I put it back together, but that made no difference either. Google play will send me a new phone, but I'd like to get it fired up and extract the last week or so of pics. Any ideas? Again, I am a complete noob and this 3 month old phone has not been modified in any way, other than auto updates from Google play. Thanks for any assistance or guidance.
Click to expand...
Click to collapse
So, your phone doesn't turn on at all?
jd1639 said:
I don't believe the issues you're seeing, appears to be failed emmc, is related to chain fire's auto root. Cf is probably the most popular method to root and it's a coincidence. I've seen these failures with other root methods too.
I think the op flashed a kernel not for his device.
Click to expand...
Click to collapse
Correct. No symbols, no battery icon, no vibrate, etc.
elf1967 said:
Correct. No symbols, no battery icon, no vibrate, etc.
Click to expand...
Click to collapse
I'm afraid there's nothing you can do. It would have to at least get into recovery or bootloader to have a prayer.
jd1639 said:
I'm afraid there's nothing you can do. It would have to at least get into recovery or bootloader to have a prayer.
Click to expand...
Click to collapse
Thanks - was just hoping it was not a hardware failure given the posts about difficulty bricking N5. Any chance if I bought a new battery that came charged it would fire up or replacing the motherboard an option?
p.s. I am not the original poster so not sure if I ticked someone off or not, sorry if I did. Just looking for assistance
elf1967 said:
Thanks - was just hoping it was not a hardware failure given the posts about difficulty bricking N5. Any chance if I bought a new battery that came charged it would fire up or replacing the motherboard an option?
p.s. I am not the original poster so not sure if I ticked someone off or not, sorry if I did. Just looking for assistance
Click to expand...
Click to collapse
It sure sounds like a hardware failure. Doubt a different battery would help. And don't worry about being the original op. This thread is old
jd1639 said:
It sure sounds like a hardware failure. Doubt a different battery would help. And don't worry about being the original op. This thread is old
Click to expand...
Click to collapse
I get the unknown device driver when hooked up USB to computer (QHSUSB_BULK). Think it is worth waiting a few weeks prior to returning it to see if there is a way to access the flash memory via a driver download? Searches for help showed similar unknown driver problem workable on samsung and HTC last year (QHSUSB_DLOAD)
elf1967 said:
I get the unknown device driver when hooked up USB to computer (QHSUSB_BULK). Think it is worth waiting a few weeks prior to returning it to see if there is a way to access the flash memory via a driver download? Searches for help showed similar unknown driver problem workable on samsung and HTC last year (QHSUSB_DLOAD)
Click to expand...
Click to collapse
No, you won't be able to. The memory doesn't mount like a sd card would. For the future use something like drop box or Google drive too backup your photos as you take them.
So I was posting about this in the Purity thread already, but this has become a major unresolvable issue so far..
I just updated clean install/flash of Purity ROM to the newest version, with the included stock kernel.
I tried out xposed framework, and only 1 mod (Serajr Blurred System UI)
on dalvik of course.. working fine for over a day.
Suddenly today, phone turned off in the gym randomly and wouldn't boot, then after 30 minutes in the gym after repeatedly trying it eventually boot, then right when I got home, I decided to un-install the mod on xposed framework, and reboot and then boom, off again not turning on for several hours... phone is not detectable by adb or fastboot. when connected to a PC, absolutely nothing, completely dead..
when connected to pc... the only thing that happens when I do vol up + vol down + power is that it cycles through usb device connecting on the PC but (device cannot start).
I've tried charging it, leaving it, I've went through every trouble shooting option that I know of.
There's not even a way I can communicate with the phone from the PC.
any suggestions, any ideas??
I can't believe that a device would be bricked from xposed module??
I could do an RMA, as the device is relatively new,
but If I return this device I'm worried about warranty void due to unlocked bootloader and custom ROM etc??
I'm leaning towards this being a hardware issue. If you got the phone straight from Google, the unlocked bootloader and custom whatever shouldn't be an issue.
THE_KINGDOM said:
So I was posting about this in the Purity thread already, but this has become a major unresolvable issue so far..
I just updated clean install/flash of Purity ROM to the newest version, with the included stock kernel.
I tried out xposed framework, and only 1 mod (Serajr Blurred System UI)
on dalvik of course.. working fine for over a day.
Suddenly today, phone turned off in the gym randomly and wouldn't boot, then after 30 minutes in the gym after repeatedly trying it eventually boot, then right when I got home, I decided to un-install the mod on xposed framework, and reboot and then boom, off again not turning on for several hours... phone is not detectable by adb or fastboot. when connected to a PC, absolutely nothing, completely dead..
when connected to pc... the only thing that happens when I do vol up + vol down + power is that it cycles through usb device connecting on the PC but (device cannot start).
I've tried charging it, leaving it, I've went through every trouble shooting option that I know of.
There's not even a way I can communicate with the phone from the PC.
any suggestions, any ideas??
I can't believe that a device would be bricked from xposed module??
I could do an RMA, as the device is relatively new,
but If I return this device I'm worried about warranty void due to unlocked bootloader and custom ROM etc??
Click to expand...
Click to collapse
you could try nexus root toolkit, also you could try with power off hold vol-up insert USB it should install lg flash tool driver's.some time's it take's it time installing driver's so just give it a min or two regard's joe
Wakamatsu said:
I'm leaning towards this being a hardware issue. If you got the phone straight from Google, the unlocked bootloader and custom whatever shouldn't be an issue.
Click to expand...
Click to collapse
ok as long as it shouldn't be a problem I'm prob going to do an RMA.
joecool666 said:
you could try nexus root toolkit, also you could try with power off hold vol-up insert USB it should install lg flash tool driver's.some time's it take's it time installing driver's so just give it a min or two regard's joe
Click to expand...
Click to collapse
Ok I'm going to try holding vol-up and insert USB, but i assume for nexus root toolkit to work it phone would need to be visible as a "fastboot" device bare minimum, which I'm having problems even getting that right now.
THE_KINGDOM said:
ok as long as it shouldn't be a problem I'm prob going to do an RMA.
Ok I'm going to try holding vol-up and insert USB, but i assume for nexus root toolkit to work it phone would need to be visible as a "fastboot" device bare minimum, which I'm having problems even getting that right now.
Click to expand...
Click to collapse
hi, nexus toolkit has an op for soft-bricked/bootloop. it might detect your device.
---------- Post added at 01:38 AM ---------- Previous post was at 01:22 AM ----------
THE_KINGDOM said:
ok as long as it shouldn't be a problem I'm prob going to do an RMA.
Ok I'm going to try holding vol-up and insert USB, but i assume for nexus root toolkit to work it phone would need to be visible as a "fastboot" device bare minimum, which I'm having problems even getting that right now.
Click to expand...
Click to collapse
how's it going any news?
joecool666 said:
hi, nexus toolkit has an op for soft-bricked/bootloop. it might detect your device.
---------- Post added at 01:38 AM ---------- Previous post was at 01:22 AM ----------
how's it going any news?
Click to expand...
Click to collapse
vol-up and power while connecting usb didn't do anything so far. I'm going to try nexus toolkit just for the hell of it, but I think this device is literally bricked beyond repair.
THE_KINGDOM said:
vol-up and power while connecting usb didn't do anything so far. I'm going to try nexus toolkit just for the hell of it, but I think this device is literally bricked beyond repair.
Click to expand...
Click to collapse
yeah sound's like it could be hard bricked, hope toolkit work's for you tho.
just doesn't make any sense of why it would be hard-bricked.. randomly just turns off.. so weird
THE_KINGDOM said:
just doesn't make any sense of why it would be hard-bricked.. randomly just turns off.. so weird
Click to expand...
Click to collapse
strange that, not getting detected by p.c, yeah look's like a trip to the service station.sorry i coulden't be of more help. hope you get it back to life.kind regard's joe
THE_KINGDOM said:
just doesn't make any sense of why it would be hard-bricked.. randomly just turns off.. so weird
Click to expand...
Click to collapse
All bricks are hard bricks. As much as people use the term "soft bricked", believe me - it isn't a thing. A brick is irreparable. If it was repairable, it isn't a brick.
If it is irreparable, its because its been affected beyond the software layer. Messing up the NAND partitions or NAND death are the most common. This can happen during a flash or even seemingly random - its not unusual for bricks to be random. Flash memory in my opinion, is still pretty unstable. Send it for repair /RMA.
Sent from my Nexus 5 using Tapatalk
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
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