Database Info

[Q] Bricked Transformer

I had a working Transformer until earlier today when the OTA update came along. Having accepted installation, my device now gets to the Eee Pad / ASUS logo and hangs there (waited for about 45 minutes after the update). Trying to reboot into recovery gives:
Android WW_epad-user bootloader < e> released by "WW_epad-8.2.3.6-20110414".
Checking for android ota recovery
Booting recovery kernel image
It does not give me the Up to recovery, Down to wipe option.
Any thoughts on how I might recover the device?
Many thanks in advance for your help.

Ohh **** that dont sound good
Sorry i cant help with any advice on fixing it, apart from trying a factory reset ?
Did you apply the update with under 50% of the battery available ?

No, full. And connected to the mains.
I cant get any option to do a full wipe, it never asks me.

morak said:
No, full. And connected to the mains.
I cant get any option to do a full wipe, it never asks me.
Click to expand...
Click to collapse
There are some things you can try in this thread - http://forum.xda-developers.com/showthread.php?t=1032374
Here a few key combinations for anyone interested:
VOL_DOWN + POWER (continue holding VOL_DOWN when it starts booting until you get a prompt) = Bootloader which offers two prompted options: (1) Recovery if you press VOL_UP within 5 seconds or (2) Data wipe if you press VOL_UP later. None of these seem to offer any USB devices like fastboot etc.
VOL_UP + POWER or VOL_DOWN + VOL_UP + PLUG IN USB = NVFlash mode. It clearly is the NVFlash APX device that we see appearing, but it barfs as soon as we run any sort of nvflash on it (Many Windows and Linux versions have been tried). Please note that in this mode the screen stays completely blank and the only way to get out of it is the following option:
Hold POWER for ~10s = Forced power off. This always helps if you are stuck in some weird mode and nothing on the screen
Dont know if any of these key presses will work on yours, worth a try to get it to recover ?

Yeah I had seen that thread. Unfortunately no joy from either option. I dont get the prompt when I do VOL DOWN+POWER, just seems to go straight into recovery. And as the post says, NVflash doesn't help at the moment.
Can't even seem to get the ADB USB devices to show up, I can only get the APX device which seems to be fairly useless ATM. Looks like I may have to RMA the thing.

What is that small hole next to HDMI port? Did you try that, it may just be button (use paper pin) to reset it to factory default?

Or maybe microphone ? lol i personnaly don't think those tablets would actually have a reset button, would check the manual first before sticking a paper pin into every holes...

My Transformer just came in, I accepted the OTA update and while installing it saw this thread and had a dreadful feeling. Thankfully, it rebooted fine and is working... sounds like something's wrong with yours unfortunately OP .

If you haven't tried the 10 second power button method as mentioned in an earlier post it's definitely worth a try.

stuntdouble:
I thought the 10 sec power button thing just turned the device off. Is there something else I can do that I am missing?

I think it clears cache and/or ram too. I'm not saying it will definitely fix your problem, it may not, but if it was me I'd try everything. It won't damage anything so don't worry.

Have you tried getting into the Clockwork mod recovery? You need to place it on an external microsd and when you do the holding down when switching on thing, it goes into the recovery on the card instead of the stock one. It might allow you to flash a rom to get it running again.
You can find the Clockwork recovery with instructions here
http://android.modaco.com/content/a...od-recovery-for-the-asus-eee-pad-transformer/

Good idea, unfortunately it didnt work. It doesnt appear to be allowing me to get to the point where it will read EP101_SDUPDATE.zip from the SD.

You sure filename is EP101? Shouldnt it be TF?

All the instructions call for EP101, but I tried TF too just in case!

dotpro said:
What is that small hole next to HDMI port? Did you try that, it may just be button (use paper pin) to reset it to factory default?
Click to expand...
Click to collapse
It's a microphone. If you go poking a paperclip in there, good luck claiming under warranty.

Same thing just happened to me... reboot for update, stuck at boot screen.
Not sure if we can find a EP101_SDUPDATE.zip for higher than 20110414 if that'd be a fix or what... or even a PC restore process.

hecatomb said:
Same thing just happened to me... reboot for update, stuck at boot screen.
Not sure if we can find a EP101_SDUPDATE.zip for higher than 20110414 if that'd be a fix or what... or even a PC restore process.
Click to expand...
Click to collapse
sonofab*tch same here. You would think they would warn people that this could happen. This is ridiculous. Their worthless phone tech kept traying to get me to hold f9. I wanted to reach through the phone and punch him.

So you are getting bricked units with stock? No modications or rooted devices?

stuntdouble said:
So you are getting bricked units with stock? No modications or rooted devices?
Click to expand...
Click to collapse
Root doesnt work on the US devices, also, OP hadnt rooted.

Nexus S boot problem

Here's the problem..my Nexus S power button isn't working, so I was using other hardware keys to shut down, turn on and such. Now I got into a problem. I installed chainfire3d drivers and now the phone won't boot and since my power button is broken, I can't access recovery. I can get into fastboot but the volume up/volume down buttons won't work so I can't select the option "RECOVERY" plus my PC doesn't recognize that my phone is in fastboot (I'm using Windows 8, 64bit.)
Can someone help me with this, if it's possible? How do I get into recovery?
Thank you in advance.

SlashSpeed said:
Here's the problem..my Nexus S power button isn't working, so I was using other hardware keys to shut down, turn on and such. Now I got into a problem. I installed chainfire3d drivers and now the phone won't boot and since my power button is broken, I can't access recovery. I can get into fastboot but the volume up/volume down buttons won't work so I can't select the option "RECOVERY" plus my PC doesn't recognize that my phone is in fastboot (I'm using Windows 8, 64bit.)
Can someone help me with this, if it's possible? How do I get into recovery?
Thank you in advance.
Click to expand...
Click to collapse
There might be several solutions to your problem. According to what youve written it seems that the powerbutton is stuck in the "ON" position, right? Meaning that the phone turns on when you insert the battery. It would also mean that in bootloader you cant select anything because the powerbutton is "pressed". Sadly if this is the case, having properly working drivers wouldnt help since phone wont be detected until the powerbutton is in the "OFF" position.
Case 1: powerbutton in "ON" position
Solution 1: Send your phone to repair. Sadly you will have to pay for that since your warranty is void (unlocking the bootloader voids the warranty as far as i know". Having the button unstuck would allow you to choose recovery with volume buttons and accept with power.
Solution 2: Since your warranty is void, do it yourself. NS disassembly is quite easy and theres nothing to be afraid of. In this case theres just some dust so once you také it appart and clean the powerbutton it should work again. Having the button unstuck would allow you to choose recovery with volume buttons and accept with power.
Case 2: powerbutton in "OFF" position
There are plenty of tutorials around here on getting drivers to work. General advice would be reinstall the drivers, try different ports, try to do it from other computer.
Hope this helps, good luck

cahir_cz said:
There might be several solutions to your problem. According to what youve written it seems that the powerbutton is stuck in the "ON" position, right? Meaning that the phone turns on when you insert the battery. It would also mean that in bootloader you cant select anything because the powerbutton is "pressed". Sadly if this is the case, having properly working drivers wouldnt help since phone wont be detected until the powerbutton is in the "OFF" position.
Case 1: powerbutton in "ON" position
Solution 1: Send your phone to repair. Sadly you will have to pay for that since your warranty is void (unlocking the bootloader voids the warranty as far as i know". Having the button unstuck would allow you to choose recovery with volume buttons and accept with power.
Solution 2: Since your warranty is void, do it yourself. NS disassembly is quite easy and theres nothing to be afraid of. In this case theres just some dust so once you také it appart and clean the powerbutton it should work again. Having the button unstuck would allow you to choose recovery with volume buttons and accept with power.
Case 2: powerbutton in "OFF" position
There are plenty of tutorials around here on getting drivers to work. General advice would be reinstall the drivers, try different ports, try to do it from other computer.
Hope this helps, good luck
Click to expand...
Click to collapse
Hey, thanks for the help, much appreciated. I'll try to open the case and clean the power button if possible and see if it's gonna work then.
On the other note, after 3 hours of searching I finally found the right solution. When on the Google screen, Windows recognized the phone as "Nexus". I clicked on it in device manager and installed Android ADB interface driver (which I downloaded via SDK manager). Windows then recognized the device in cmd via adb and I could reboot into recovery with the command "adb reboot recovery".
What a relief! :victory:

SlashSpeed said:
Hey, thanks for the help, much appreciated. I'll try to open the case and clean the power button if possible and see if it's gonna work then.
On the other note, after 3 hours of searching I finally found the right solution. When on the Google screen, Windows recognized the phone as "Nexus". I clicked on it in device manager and installed Android ADB interface driver (which I downloaded via SDK manager). Windows then recognized the device in cmd via adb and I could reboot into recovery with the command "adb reboot recovery".
What a relief! :victory:
Click to expand...
Click to collapse
Congratulations Never knew you can use adb while booting Good luck with the cleaning

Well I'm just..brilliant to say the least. After I fixed everything I tried to install the Chainfire3D driver again, this time with no EGL and well, same thing happened, no boot. Stuck on Google screen, just that this time, Windows recognizes the device as "google file-cd gadget usb device" not as "Nexus" or "ADB interface". Damn it...
Edit: Well, I'm clueless now...any help would be appreciated..

SlashSpeed said:
Well I'm just..brilliant to say the least. After I fixed everything I tried to install the Chainfire3D driver again, this time with no EGL and well, same thing happened, no boot. Stuck on Google screen, just that this time, Windows recognizes the device as "google file-cd gadget usb device" not as "Nexus" or "ADB interface". Damn it...
Edit: Well, I'm clueless now...any help would be appreciated..
Click to expand...
Click to collapse
well get in to fastboot menu and original flash firmware
should i take u step by step? or u have some idea of fastboot?

uxmanz said:
well get in to fastboot menu and original flash firmware
should i take u step by step? or u have some idea of fastboot?
Click to expand...
Click to collapse
I can get into the fastboot menu, but I can't use the volume up/down buttons and I don't think that my computer recognizes the device in fastboot at all, because of the broken power button. If you could help me somehow, then I would really be in your debt.

SlashSpeed said:
Well I'm just..brilliant to say the least. After I fixed everything I tried to install the Chainfire3D driver again, this time with no EGL and well, same thing happened, no boot. Stuck on Google screen, just that this time, Windows recognizes the device as "google file-cd gadget usb device" not as "Nexus" or "ADB interface". Damn it...
Edit: Well, I'm clueless now...any help would be appreciated..
Click to expand...
Click to collapse
Asking for it aren't you?
Chainfire isn't compatible with Jellybean. Seriously.
Google-file CD Gadget USB Device is what becomes detected as "Nexus" later in the boot process. Have you tired detecting devices with adb devices?

polobunny said:
Asking for it aren't you?
Chainfire isn't compatible with Jellybean. Seriously.
Google-file CD Gadget USB Device is what becomes detected as "Nexus" later in the boot process. Have you tired detecting devices with adb devices?
Click to expand...
Click to collapse
Yeah...learned it the hard way..I'm too stubborn sometimes. Chainfire3D actually worked on CM10 on the Optimus Black, seems like here it wasn't the case..
Anyway, about that, yeah, I did and it doesn't detect it. Can I somehow turn the CD gadget USB device back into Nexus, like it was before or?

SlashSpeed said:
Yeah...learned it the hard way..I'm too stubborn sometimes. Chainfire3D actually worked on CM10 on the Optimus Black, seems like here it wasn't the case..
Anyway, about that, yeah, I did and it doesn't detect it. Can I somehow turn the CD gadget USB device back into Nexus, like it was before or?
Click to expand...
Click to collapse
I believe you could always enter download mode and ODIN back to stock in the worst case scenario.

polobunny said:
I believe you could always enter download mode and ODIN back to stock in the worst case scenario.
Click to expand...
Click to collapse
I tried that, but nothing happened, I couldn't enter download mod, probably because the power button is broken and it's probably on "ON".

SlashSpeed said:
I tried that, but nothing happened, I couldn't enter download mod, probably because the power button is broken and it's probably on "ON".
Click to expand...
Click to collapse
If you can enter bootloader mode you can enter download mode.

polobunny said:
If you can enter bootloader mode you can enter download mode.
Click to expand...
Click to collapse
I can enter download mode by holding down Volume Up and Volume Down together right? It doesn't work sadly..

SlashSpeed said:
I can enter download mode by holding down Volume Up and Volume Down together right? It doesn't work sadly..
Click to expand...
Click to collapse
Make sure your phone is connected to your PC. Then hold VOL down and press power if I recall correctly. It might be both volume keys together that you hold, but either way you need to make sure you phone is connected to your computer.

polobunny said:
Make sure your phone is connected to your PC. Then hold VOL down and press power if I recall correctly. It might be both volume keys together that you hold, but either way you need to make sure you phone is connected to your computer.
Click to expand...
Click to collapse
Tried both, with just volume down and volume down + up and nothing. My phone was connected to the PC. I can only enter the bootloader..

SlashSpeed said:
Tried both, with just volume down and volume down + up and nothing. My phone was connected to the PC. I can only enter the bootloader..
Click to expand...
Click to collapse
If you hold the middle of the volume key while connecting the USB cable (not pressing power) do you see anything?

polobunny said:
If you hold the middle of the volume key while connecting the USB cable (not pressing power) do you see anything?
Click to expand...
Click to collapse
I can't do that, because as soon as I plug in the battery the phone turns on..but yeah, I tried what you said and nothing.

SlashSpeed said:
I can't do that, because as soon as I plug in the battery the phone turns on..but yeah, I tried what you said and nothing.
Click to expand...
Click to collapse
Ah obviously. I'm out of idea here, someone else might chime in. Other than making the power button work, you might have thrown yourself into a real problem this time.

polobunny said:
Ah obviously. I'm out of idea here, someone else might chime in. Other than making the power button work, you might have thrown yourself into a real problem this time.
Click to expand...
Click to collapse
If nothing else helps, I guess I'll just send it to a repair center for the power button. I wanted to do that anyway and I sadly I have a real reason.. :/
Polobunny, I appreciate your efforts though.
Edit: Took my phone to a repair center, screw it.

[Q] Stuck with bootloop no bootloader access :/

Hello, just to start I have read through probably 100 post regarding similar issues but none are working. I have the ATT Htc one x EVITA 3.18 version. I did the super CID unlocked my bootloader through htc dev, flashed twrp recovery, and got a custom rom, gapps etc.. in twrp I wiped all data,system,cache, factory reset. Then flashed my rom and gapps (being kinda new to HTC devices I didn't flash the boot.img from the rom) now my phone after restarting just continues a bootloop (HTC Quietly Brilliant) screen, then powers off repeating this over and over.. I tried holding the volume down with the power button it just loops again, the I tried some other suggestions like holding power and vol down until the flashes stop and releasing power while continuing to hold volume down, again loops, then tried using volume up as well...none of these are working I don't understand what happened and why I can't get into any of these? I did not run any RUU. I tried using adb but of course i cant get into fastboot or anything so the phone is not recognized. If anyone could please help I really do appreciate it. I know this has been all over the threads but I read for the past 3 hours and could not get anything to work.. Thanks in advanced for any help it is much appreciated. :crying:

First of all, don't hold volume up and power, that's bad news. Trying random button combinations is a really bad idea. While it's looping just hold volume and the next time it starts again it should reach the bootloader.
Sent from my Evita

timmaaa said:
First of all, don't hold volume up and power, that's bad news. Trying random button combinations is a really bad idea. While it's looping just hold volume and the next time it starts again it should reach the bootloader.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply timmaaa... I usually would not try the other button presses just someone else had said that worked for them, but thanks for the advice. I did try what you said and just holding the volume down button, let it bootloop, and keep holding and it just continues to bootloop :/ it stay off for about 20 seconds the same then bootloops, with the htc screen for about 5 seconds the rinse and repeats D**n this thing is annoying. Any other Ideas? Thanks again man appreciate it.

if you are SOFF u can go for RUU?

Sonone said:
if you are SOFF u can go for RUU?
Click to expand...
Click to collapse
No I'm still s-on I didn't try to RUU cus I read it would brick..but seems I'm somewhat bricked anyway:silly:

sensei_777 said:
No I'm still s-on I didn't try to RUU cus I read it would brick..but seems I'm somewhat bricked anyway:silly:
Click to expand...
Click to collapse
are you sure you did get the SUPER CID cause if its not then you can RUU your device!
cause if you are not SUPERCID get a matching RUU or a latest version meant for your device!
only if you could somehow manage your phone to get recognized by a PC etc then you could flash boot.img with some toolkit etc and everything would have been fine!
but unless some expert actually figures out your problem dont RUU!
i really wonder whats obstructing the boot loader access!??
please let me know if u can get your device back to normal!

Sonone said:
are you sure you did get the SUPER CID cause if its not then you can RUU your device!
cause if you are not SUPERCID get a matching RUU or a latest version meant for your device!
only if you could somehow manage your phone to get recognized by a PC etc then you could flash boot.img with some toolkit etc and everything would have been fine!
but unless some expert actually figures out your problem dont RUU!
i really wonder whats obstructing the boot loader access!??
please let me know if u can get your device back to normal!
Click to expand...
Click to collapse
I had to change the CID to unlock the bootloader on htc dev, its like 11111 so that is super CID right?
Yea I've tried everything to get to adb since I am familiar with adb but its a no go none of the tool kits or even manual cmd is recognizing the device.. I had a one x just like this before and never had the problem getting into bootloader so I don't really get what is blocking it. Only thing I had done was flash twrp recovery, wiped data/factory reset, system and cache, then flashed the rom as one usually would and gapps, just I had forgot about these phones needing you to flash the boot.img. that is all I did to it. Kinda sucks I just got this thing yesterday from a friend too.

Yes, 11111111 is SuperCID. In any case I probably wouldn't attempt an RUU while the phone is this unstable, could be quite dangerous. It's possible the "adb reboot bootloader" command might work if you catch it at the right time in the boot cycle.
Sent from my Evita

timmaaa said:
Yes, 11111111 is SuperCID. In any case I probably wouldn't attempt an RUU while the phone is this unstable, could be quite dangerous. It's possible the "adb reboot bootloader" command might work if you catch it at the right time in the boot cycle.
Sent from my Evita
Click to expand...
Click to collapse
Thanks bud, well I can't get it to catch even using super finger speed cmd'ing lol.. oh well.. I'm not gonna try anything else other than the usual ways to get into bootloader until someone else has some idea what might be blocking it from entering. Is there anyway to turn it off? its just restarting over and over with the bootloop. Or does one just let it go dead? I suppose worse case senario sending it for Jtag would fix it right? thanks again to the both of you.

I believe in the command window your can press the down key to give the previous command again, so if you hit down and enter one after the other (spamming it) you might have a chance. I'm really surprised that continually holding volume down during the loop process isn't getting you to bootloader, that's very strange. There's no way to turn it off. But, it usually burns through a fair bit of battery during a boot loop so you could wait for it to die completely, charge it for a couple of hours, and then try the volume down + power combination to get to the bootloader. I hope it works, let us know how you go.
Sent from my Evita

timmaaa said:
I believe in the command window your can press the down key to give the previous command again, so if you hit down and enter one after the other (spamming it) you might have a chance. I'm really surprised that continually holding volume down during the loop process isn't getting you to bootloader, that's very strange. There's no way to turn it off. But, it usually burns through a fair bit of battery during a boot loop so you could wait for it to die completely, charge it for a couple of hours, and then try the volume down + power combination to get to the bootloader. I hope it works, let us know how you go.
Sent from my Evita
Click to expand...
Click to collapse
Yes well on my laptop its the up key that's what I was doing was spamming, you can hear the connected device sound on then off, but it just doesn't see it. I will let you all know once its working again and what I did or had to do to get it back so that it may possibly help others that run into the same issue. If not I suppose I'll try to get it Jtagged, too nice of a phone to use as a paperweight really

Yeah sorry, I knew it was one of the arrow keys, kinda took a stab in the dark at that one :sly:
Sent from my Evita

Hold down the power button until the phone turns off. You'll see the buttons flash. This simulates a battery pull. Then wait a few secs then hold vol down and press power button for 2 secs while still holding vol down. Wait for bootloader
Sent from my VENOMized HoxL

You should hold volume down while holding power. Holding power alone just initiates a reboot, not a power down, so if you're not holding volume down at the same time when the reboot kicks in it'll just reboot as normal.
Sent from my Evita

timmaaa said:
You should hold volume down while holding power. Holding power alone just initiates a reboot, not a power down, so if you're not holding volume down at the same time when the reboot kicks in it'll just reboot as normal.
Sent from my Evita
Click to expand...
Click to collapse
Nothing is working guys :/ full Battery drain and everything it just keeps looping no matter what I do it will not go in bootloader :crying: thanks for trying to help

If you are trying while the phone is plugged into power it will not work.
The method I use is to hold power until the screen shuts off then I let go of power and hold volume down until the bootloader comes up.
Sent from my One Xl using xda app-developers app

exad said:
If you are trying while the phone is plugged into power it will not work.
The method I use is to hold power until the screen shuts off then I let go of power and hold volume down until the bootloader comes up.
Sent from my One Xl using xda app-developer app
Click to expand...
Click to collapse
Yes I don't have power plugged in, I've never had a problem like this. . I also don't even have to turn off the screen everytime it loops it goes off for a good 20 seconds or more. But I did try what you all said too and it seems there is not even an effect at all it just loops
YAY!! I was messing around and held volume up and volume down with power, and it put the phone into some kind of off/sleep mode, then it recognized the device in windows device manager and said device cannot start, so I tried uninstalling the driver and then refreshed to let it reinstall them and during the reinstall i tried running the adb command and it let me back into bootloader! woo! that was lucky.. hopefully this can be helpful to others that get stuck like that. I'm worried now though i have bootloader sitting pretty what should I do first? I'm scared to loop again thanks all.

sensei_777 said:
Yes I don't have power plugged in, I've never had a problem like this. . I also don't even have to turn off the screen everytime it loops it goes off for a good 20 seconds or more. But I did try what you all said too and it seems there is not even an effect at all it just loops
YAY!! I was messing around and held volume up and volume down with power, and it put the phone into some kind of off/sleep mode, then it recognized the device in windows device manager and said device cannot start, so I tried uninstalling the driver and then refreshed to let it reinstall them and during the reinstall i tried running the adb command and it let me back into bootloader! woo! that was lucky.. hopefully this can be helpful to others that get stuck like that. I'm worried now though i have bootloader sitting pretty what should I do first? I'm scared to loop again thanks all.
Click to expand...
Click to collapse
Just flashed the boot.img good to go now thanks for the advice everyone

[Q] Hard brick?

Hey Guys,
so ive been messing around with this little phone and think i might have managed a hard brick. Any thoughts or advice would be appreciated.
was attempting to relock the bootloader and flashing my local 4.4.2 rom and on the command prompt when i reached flash system.img parsechunk lines, they failed. as it said permission denied.
Tried to continue with no luck. Restarted my phone and now cant get into recovery and no boot, the only screen i see is the white warning bootloader locked screen, get a vibrate and then it turns off again. Any ways to flash without Recovery or Fastboot or am i completely out of luck?
Sorry im new to motorolas, had no problems messing around with my old SGS2
Thanks in advance everybody.

did you try this ?
http://forum.xda-developers.com/showthread.php?t=2542219

the only problem is cant get the phone into fastboot mode. Thanks for the input though!

mackb44 said:
the only problem is cant get the phone into fastboot mode. Thanks for the input though!
Click to expand...
Click to collapse
I've been in a few situations where I thought I had 'bricked' my phone. One way that worked (sometimes) was to long press the POWER button for a very long time(minutes), then release and (sometimes) it would reboot.
The usual way to the fastboot menu is - power off (which yours probably is), then hold vol. down and press power button for 5/10 seconds and release both.
Good luck!

jamsh said:
I've been in a few situations where I thought I had 'bricked' my phone. One way that worked (sometimes) was to long press the POWER button for a very long time(minutes), then release and (sometimes) it would reboot.
The usual way to the fastboot menu is - power off (which yours probably is), then hold vol. down and press power button for 5/10 seconds and release both.
Good luck!
Click to expand...
Click to collapse
Yea tried both options, no luck!
The only screen i can get now is the bootloader unlocked screen or the white charging screen when plugged in. After that the screen will stay on but is completely black.

Success I can get into fastboot now!!!! not sure why i could not before

mackb44 said:
Success I can get into fastboot now!!!! not sure why i could not before
Click to expand...
Click to collapse
yes i had something similar,bootlocker warning and then the screen going dark. i just ended up using fastboot and flashing a stock rom and went from there.
glad your panic is over .

quizmaniac said:
yes i had something similar,bootlocker warning and then the screen going dark. i just ended up using fastboot and flashing a stock rom and went from there.
glad your panic is over .
Click to expand...
Click to collapse
Yea thanks buddy!
just have to wait for it to charge up before it will let me flash using adb, oddly its only showing that it is charging while plugged into usb and not the wall socket

NEVER SEEN HARD BRICK on Oneplus One

Good Morning,
yesterday when i flashed a rom, something goes wrong.
My opo don't go in boot animation and work only the recovery and fastboot.
I don't know why but afther another reboot the phone is dead, i think that is a normal hard brick so i try to restore with the tool "msm8974 download tool" but it don't work, when i start the restore come out a red word.
I never seen a hard brick like this, the phone is 100% dead , when i press the power button don't vibrates and nothing come out, diplay is black.
What can i do to restore my opo? :crying:

Try Wiping everything from TWRP and try a different ROM.
Another thing to try is connecting ADB to get the logcat.
Can you give more details on what you've tried so far?
Additionally, I remember reading that the OPO can stop booting correctly when the battery starts failing.

umer936 said:
Try Wiping everything from TWRP and try a different ROM.
Another thing to try is connecting ADB to get the logcat.
Can you give more details on what you've tried so far?
Additionally, I remember reading that the OPO can stop booting correctly when the battery starts failing.
Click to expand...
Click to collapse
Now the phone is dead, if I press the power button nothing come out (no vibration, no screen) the phone look like without battery! (But it is over 50%)
I followed the tutorial to restore HARD BRICK with the tool but it don't success!

ghibli2 said:
Now the phone is dead, if I press the power button nothing come out (no vibration, no screen) the phone look like without battery! (But it is over 50%)
I followed the tutorial to restore HARD BRICK with the tool but it don't success!
Click to expand...
Click to collapse
Me to.. this morning my phone dead.. i dont know what can i do again..
Trying pressing all combination button not showing anything even in pc device manager usb not recognize or qhsusb_bulk not appear
Anyone can help me please.. @netbuzz

I have bricked this phone in and out, believe me lol all you gotta do is open the phone, unscrew all (TOP HALF) screws and UN plugg battery......wait about 30 sec RE plugg/connect battery and re run the unbricking tool