Hi there! First of all I don't speak english very well.
My Galaxy Nexus hard bricked yesterday.
tl;dr no boot animation, no recovery mode, no download mode, no response from computer.
I thought it had just a low battery level, I found it turned off. So I tried to recharge it but it gave no signals, no battery icon, nothing.
After an all night long recharge I tried to turn it on, to enter in download mode or in recovery mode but nothing works. I also tried to connect it with my computer with and without battery, no response, no "OMAP" device found, no sound from Windows for plugging it in, nothing.
I found this thread here in xda, many people has been redirected to it and found their solution to the brick problem.
I tried to follow all the steps but when I plug in the phone and start the .bat file nothing happens, just stuck on "Waiting for device".
The phone is unlocked and rooted. I'm running AOKP JB-MR1 Build 2 and Franco Kernel for a month, never had problems with them, never installed other ROMs after that.
What should I do now? Should I try to do something or just bring it to a support center? The phone is still in warranty, there would be any problem because it has a non-stock ROM?
I've red about a jig to force the Odin mode, should I buy it? (I found this one)
Thanks for the help.
Have you tried booting into Odin mode
ntb81 said:
Have you tried booting into Odin mode
Click to expand...
Click to collapse
Yes, it doesn't work.
have you your warranty on it?
return it and get a new one
It's hard bricked and a JTAG unit may force it into download mode, if you send it in for warranty, chances are it won't be accepted as it was obviously tampered with and they would find out that your bootloader is unlocked and charge you more money than the device is actually worth to fix it.
I don't understand how it could of bricked if nothing has changed on the phone for a month or longer. Nothing was flashed recently so how can you hard brick the phone?
Beauenheim said:
It's hard bricked and a JTAG unit may force it into download mode, if you send it in for warranty, chances are it won't be accepted as it was obviously tampered with and they would find out that your bootloader is unlocked and charge you more money than the device is actually worth to fix it.
Click to expand...
Click to collapse
Yeah, that's why I'm not sure to send it in for warranty. So have I to try with a JTAG first?
[bman123] said:
I don't understand how it could of bricked if nothing has changed on the phone for a month or longer. Nothing was flashed recently so how can you hard brick the phone?
Click to expand...
Click to collapse
I'm not understanding that too, I don't know what happened. Suddendly it stopped working. Maybe is just a battery problem, I'll try to use another one before bringing it to the shop where I bought it.
same happened to me, but I have an untouched phone with stock android. it worked well for over an year until today.
I see a lot of people having same issue, but they say that when connected to PC over USB the phone is recognized as OMAP.
for me the PC doesn't do anything...
any help? thanks
---------- Post added at 06:12 AM ---------- Previous post was at 06:02 AM ----------
galiganu said:
same happened to me, but I have an untouched phone with stock android. it worked well for over an year until today.
I see a lot of people having same issue, but they say that when connected to PC over USB the phone is recognized as OMAP.
for me the PC doesn't do anything...
any help? thanks
Click to expand...
Click to collapse
so right after I wrote that I plugged my phone into USB of my PC without battery. when I inserted the battery it started showing me the battery sign and I could started the phone. 3 minutes later it went black again, but the trick didnt work again.
any ideas? thanks
Try This !!
Arrange a 4 ohm resistor and try to attach it in ur usb plug port of phone ..it 'll force the phon eto go in download mode or say Fastboot mode.
then follow a tutorial to flash any rom..
its quite easy else ping me !!
Tech.Nik said:
Arrange a 4 ohm resistor and try to attach it in ur usb plug port of phone ..it 'll force the phon eto go in download mode or say Fastboot mode.
then follow a tutorial to flash any rom..
its quite easy else ping me !!
Click to expand...
Click to collapse
Please could you explain a bit more how to go about this? I have a Verizon Galaxy Nexus in a somewhat similar condition. This one is recognised as an OMAP 4430 device. I downloaded OMAP Flasher, installed drivers and tried to bring it back to life but after running the batch file I get this error: Operation FAILED (Remote: : Driver init error 0x00FF8080 - MMC CONFIG FAILURE). Can the resistor trick work on this and if yes, how can I go about it? I am not faint-hearted; I think I can handle it if given the right instructions.
After I tried everything i could from the internet, I went to a shop and tested to see if the USB is broken - and indeed it was. I replaced the USB component of the phone and after that it started.
Thanks guys
galiganu said:
After I tried everything i could from the internet, I went to a shop and tested to see if the USB is broken - and indeed it was. I replaced the USB component of the phone and after that it started.
Thanks guys
Click to expand...
Click to collapse
Yeah, the faulty USB port is a very common issue.
Related
Hi XDA,
I've searched in many threads but i can't find an anwser.
I've bricked my Galaxy Gio when i flashed a custom kernel. It was the kernel in this thread http://forum.xda-developers.com/showthread.php?t=1319816
Now it does nothing, I can't boot in any mode, not in download mode, not in recovery mode...
I have android 2.3.3 Gingerbread.
Is there any way to unbrick or is my phone just an expensive decoration now.
Thanks in Advance.
Hi !!!
same new here
This ll work in some cases
Hope this will work in your device as well
Pull the battery to kill the boot loop (or whatever is hosed up), put the phone into downloading mode and re-flash the stock ROM.
Free to try...
Thanks for quick reply but i can't go into download mode as i said. Also my phone is just totally off and won't boot at all. My pc also doesn't detect it when it is plugged in.
SuperUub said:
Thanks for quick reply but i can't go into download mode as i said. Also my phone is just totally off and won't boot at all. My pc also doesn't detect it when it is plugged in.
Click to expand...
Click to collapse
If not even adb detects it, i'm pretty sure you're buggered, mate.
did you try and leave the battery out for some 10 min or more?
If adb does not detect the phone after that, then it seems to be a brick for real.
Is your phone stop at the "samsung" when you turn on your phone?
If is this,it's very easy to unbrick
One easy procedure which you might want to try with no guarantee it'll work:
-Remove the battery, microSD and SIM from the phone.
-Prepare the Odin software and your ROM on a known working system
-Connect the phone to the computer with the USB cable.
-With one hand, simultaneously hold Volume down, home and power.
-With your other hand, put the battery in the phone.
I was able to get Odin to detect an otherwise bricked phone this way. I was however unable to get further than the "setup connection" step. Maybe your outcome will be better.
Regards,
Darkshado
+
Yes this way usually works. I've tested this way.
that worked for me to on a brick when it didnt even went on, no recovery, download mode etc, after waiting 2 weeks and trying to repair it myself I nearly throw it away, and then suddenly it went into download mode for about 1 or 2 seconds, wich told me the battery whasn't working.. so I started to charge the battery, and hoped it would boot, but it didn't.. using that method given above, I could get into download mode again, and flashes a new stock ROM. now I still have my phone, working.
Odin to detect
Darkshado said:
One easy procedure which you might want to try with no guarantee it'll work:
-Remove the battery, microSD and SIM from the phone.
-Prepare the Odin software and your ROM on a known working system
-Connect the phone to the computer with the USB cable.
-With one hand, simultaneously hold Volume down, home and power.
-With your other hand, put the battery in the phone.
I was able to get Odin to detect an otherwise bricked phone this way. I was however unable to get further than the "setup connection" step. Maybe your outcome will be better.
Regards,
Darkshado
Click to expand...
Click to collapse
i i need help, odin detects my phone but dont pass from -"setup connection", did you have news?
I had my mainboard replaced at a service center... Probably not the news you would have liked, but I'm afraid that's your next step as well.
Darkshado said:
One easy procedure which you might want to try with no guarantee it'll work:
-Remove the battery, microSD and SIM from the phone.
-Prepare the Odin software and your ROM on a known working system
-Connect the phone to the computer with the USB cable.
-With one hand, simultaneously hold Volume down, home and power.
-With your other hand, put the battery in the phone.
I was able to get Odin to detect an otherwise bricked phone this way. I was however unable to get further than the "setup connection" step. Maybe your outcome will be better.
Regards,
Darkshado
Click to expand...
Click to collapse
This worked for me too, try to charge your battery in another phone if possible
bobcota said:
i i need help, odin detects my phone but dont pass from -"setup connection", did you have news?
Click to expand...
Click to collapse
same problem
same problem here
voetbalremco said:
that worked for me to on a brick when it didnt even went on, no recovery, download mode etc, after waiting 2 weeks and trying to repair it myself I nearly throw it away, and then suddenly it went into download mode for about 1 or 2 seconds, wich told me the battery whasn't working.. so I started to charge the battery, and hoped it would boot, but it didn't.. using that method given above, I could get into download mode again, and flashes a new stock ROM. now I still have my phone, working.
Click to expand...
Click to collapse
i also have the same prblem here just now , i tried to flash this ROM but i forgot to wipe data/factory reset the phne and i unintentionally flashed the rom without wiping it :'( and now, dont boot at all but can still turned on and ended up just "samsung" appearing on the screen . please help :crying::crying:
I've bricked my Galaxy Gio when i flashed a custom kernel.
Hi There I also have the same problem. I installed Galaxy Ace's Kernel onto my Galaxi Gio, Now it does nothing, I can't boot in any mode, not in download mode, not in recovery mode...
S[B said:
[/B]uperUub;20668671]Hi XDA!
I've searched in many threads but i can't find an anwser.
I've bricked my Galaxy Gio when i flashed a custom kernel. It was the kernel in this thread http://forum.xda-developers.com/showthread.php?t=1319816
Now it does nothing, I can't boot in any mode, not in download mode, not in recovery mode...
I have android 2.3.3 Gingerbread.
Is there any way to unbrick or is my phone just an expensive decoration now.
Thanks in Advance.
Click to expand...
Click to collapse
Not either going to Download Mode
trackIDtracker said:
Hi !!!
same new here
This ll work in some cases
Hope this will work in your device as well
Pull the battery to kill the boot loop (or whatever is hosed up), put the phone into downloading mode and re-flash the stock ROM.
Free to try...
Click to expand...
Click to collapse
Okay, so recently installed the 4.4.2 OTA on my completely stock nexus 7 (unrooted, bootloader still locked).
Tried connecting to my PC via bluetooth (for headset) and noticed that it wasnt working (was working on 4.4), so decided that maybe a reboot would fix the problem.
And now the tablet doesn't boot. Completely unresponsive, no charging icon etc. either. Tried holding down the power button, power and +/- vol for 20+ secs to no avail. Connecting the tablet to my laptop makes windows update search for the QHSUSB_DLOAD driver. From what I've read this is supposed to be some sort of hardbrick?
I left the tablet completely stock and haven't done any tinkering except use the Wugfresh toolkit to do a backup (which only needed USB debugging on). Also the battery was definitely 60%+ before I attempted rebooting.
Help please? This is completely out of the blue seeing as I never even unlocked the bootloader or anything?
Please help!
See if something in this thread helps: http://forum.xda-developers.com/showthread.php?t=2393604
...and http://forum.xda-developers.com/showthread.php?t=2381582
mdamaged said:
See if something in this thread helps: http://forum.xda-developers.com/showthread.php?t=2393604
...and http://forum.xda-developers.com/showthread.php?t=2381582
Click to expand...
Click to collapse
Gone through both of them, tried the steps in the first one but I cant get to fastboot, still a blank screen and QHSUSB_DLOAD in device manager. The second one mentions in it's FAQ that the bootloader must be unlocked before using it? Mine was locked so I guess I cant use that method?
crash91 said:
Gone through both of them, tried the steps in the first one but I cant get to fastboot, still a blank screen and QHSUSB_DLOAD in device manager. The second one mentions in it's FAQ that the bootloader must be unlocked before using it? Mine was locked so I guess I cant use that method?
Click to expand...
Click to collapse
Hmm, well, last ditch would be to charge it overnight, and hold the power button down for several minutes, if that doesn't do it, you may have to just use the warranty.
mdamaged said:
Hmm, well, last ditch would be to charge it overnight, and hold the power button down for several minutes, if that doesn't do it, you may have to just use the warranty.
Click to expand...
Click to collapse
I'll update this tomorrow morning, thanks for your help!
crash91 said:
I'll update this tomorrow morning, thanks for your help!
Click to expand...
Click to collapse
No problem, keep us updated, too bad there isn't a 100% sure-fix answer though.
mdamaged said:
No problem, keep us updated, too bad there isn't a 100% sure-fix answer though.
Click to expand...
Click to collapse
Alright so still no dice. Warranty is out of the question because I bought an imported version off eBay before it was officially available on Google play here in India.
From what I've understood this may be recoverable. People have made fixes for some HTC devices etc. Basically if someone could makes a "QCN" backup from a working device I may be able to restore the bootloader using the Qualcomm drivers. Or would this tool be of any use?
http://forum.xda-developers.com/showthread.php?t=1308546
Not too familiar with all this low level flashing stuff - so need a second opinion. Will try again today evening, leaving it unplugged this time.
crash91 said:
(...)
From what I've understood this may be recoverable. People have made fixes for some HTC devices etc. Basically if someone could makes a "QCN" backup from a working device I may be able to restore the bootloader using the Qualcomm drivers. Or would this tool be of any use?
http://forum.xda-developers.com/showthread.php?t=1308546
Not too familiar with all this low level flashing stuff - so need a second opinion. Will try again today evening, leaving it unplugged this time.
Click to expand...
Click to collapse
Yeah, I don't know much about that either, sorry, I'm not going to be much help there.
Ok, am I the first person with this problem? When the device is plugged in to the PC and I try holding down the buttons (tried almost every combo I could think of) the disconnect/connect sound plays and the tablet is re-detected by device manager as QHSUSB_DLOAD. Im extremely disappointed that this can happen even without screwing around with the system.
The warranty card with the tablet seems to imply international warranty although not specifically stated, it's from the US, so would taking it to an Asus center in India be of any use?
crash91 said:
Ok, am I the first person with this problem? When the device is plugged in to the PC and I try holding down the buttons (tried almost every combo I could think of) the disconnect/connect sound plays and the tablet is re-detected by device manager as QHSUSB_DLOAD. Im extremely disappointed that this can happen even without screwing around with the system.
The warranty card with the tablet seems to imply international warranty although not specifically stated, it's from the US, so would taking it to an Asus center in India be of any use?
Click to expand...
Click to collapse
check this: http://forum.xda-developers.com/showthread.php?t=2415471
and try holding your power button for 30-35secs
malikmoreni said:
check this: http://forum.xda-developers.com/showthread.php?t=2415471
and try holding your power button for 30-35secs
Click to expand...
Click to collapse
Only works for a couple of HTC devices, tried asking in the IRC channel and was told that it wont help at all. Held the power button for over a minute nothing happens, still the same in device manager although I can tell it restarts back into the same mode from the connect/disconnect sound.
crash91 said:
Only works for a couple of HTC devices, tried asking in the IRC channel and was told that it wont help at all. Held the power button for over a minute nothing happens, still the same in device manager although I can tell it restarts back into the same mode from the connect/disconnect sound.
Click to expand...
Click to collapse
Try using the Qualcomm product support Tool google "QPST" for download links
malikmoreni said:
Try using the Qualcomm product support Tool google "QPST" for download links
Click to expand...
Click to collapse
Downloaded them, I think a USB driver is needed for the tablet to show up as a COM port, I've tried a few drivers but QPST Configuration was unable to connect. Even if it were able to connect I dont know what to do after that, it seems that some device-specific hex/qcn/xml files are needed and this is the mode the manufacturer uses when flashing the bootloader. Does this mean that my bootloader somehow magically corrupted itself?!
crash91 said:
Downloaded them, I think a USB driver is needed for the tablet to show up as a COM port, I've tried a few drivers but QPST Configuration was unable to connect. Even if it were able to connect I dont know what to do after that, it seems that some device-specific hex/qcn/xml files are needed and this is the mode the manufacturer uses when flashing the bootloader. Does this mean that my bootloader somehow magically corrupted itself?!
Click to expand...
Click to collapse
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
---------- Post added at 08:44 PM ---------- Previous post was at 08:36 PM ----------
malikmoreni said:
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
Click to expand...
Click to collapse
okay, i think i found a solution. search the factory image for the bootloader and flash with fastboot
try following the instructions here
http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
use "fastboot flash bootloader ****************#####***###*#.img" when you find the bootloader
GOODLUCK:good:
Or you can't get it to fastboot mode also?
malikmoreni said:
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
---------- Post added at 08:44 PM ---------- Previous post was at 08:36 PM ----------
okay, i think i found a solution. search the factory image for the bootloader and flash with fastboot
try following the instructions here
http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
use "fastboot flash bootloader ****************#####***###*#.img" when you find the bootloader
GOODLUCK:good:
Or you can't get it to fastboot mode also?
Click to expand...
Click to collapse
That's exactly the thing, it doesnt get into fastboot mode or anything, I assume you need a working bootloader to be able to boot fastboot? If it was in fastboot I would have attempted this already.
Anyway the seller says that the item is covered under a 1 year international warranty, thats my only chance now I guess....
The thing that concerns me is that I was completely stock, locked bootloader and unrooted. Only installed the official OTA updates (no sideloading either).
For those who are interested - I finally had time to drop by the service centre. They replaced the battery and motherboard (it was under warranty). I was expecting them to do some magic with QPST or something though.
The same has just happened to me, but I'm out of luck, the warranty has expired.
Did anyone have managed to fix it with the QPST drivers?
thanks.
Fyi, http://www.androidpolice.com/2015/0...rate-not-likely-a-result-of-firmware-updates/
I received an SGH-T989 that wouldn't boot. It had TWRP on it, so I was able to flash latest stable CWM. Upon reboot, it apparently became hard-bricked.
Currently, I'm unable to enter download or recovery modes. USB Jig does not work. There is no output on the screen, even when charging the battery. When connected in Windows (32 or 64), I get a usb error message: "This device is disabled because the firmware of the device did not give it the required resources. (Code 29)"
My question: Is the motherboard dead, or could a jtag repair fix it?
What I've tried:
multiple micro usb cables
usb jig
odin
keis
heimdall
Thanks xda!
Dostoevsky said:
I received an SGH-T989 that wouldn't boot. It had TWRP on it, so I was able to flash latest stable CWM. Upon reboot, it apparently became hard-bricked.
Currently, I'm unable to enter download or recovery modes. USB Jig does not work. There is no output on the screen, even when charging the battery. When connected in Windows (32 or 64), I get a usb error message: "This device is disabled because the firmware of the device did not give it the required resources. (Code 29)"
My question: Is the motherboard dead, or could a jtag repair fix it?
What I've tried:
multiple micro usb cables
usb jig
odin
keis
heimdall
Thanks xda!
Click to expand...
Click to collapse
so the qhsusb_dload does not apear when your device is plugged into the computer? if so please hold on a little longer, somebody found a method of unhard bricking S3's and eventually Note 3's and the galaxy megas and im getting closer to being able to do this aswell im going to try to fix mine when i get home so hold on
Trozzul said:
so the qhsusb_dload does not apear when your device is plugged into the computer? if so please hold on a little longer, somebody found a method of unhard bricking S3's and eventually Note 3's and the galaxy megas and im getting closer to being able to do this aswell im going to try to fix mine when i get home so hold on
Click to expand...
Click to collapse
That would be great! I did see the S3 fix that loads a debrick.img from sdcard - would that work with hardbricked? Windows wouldn't load the usb drive for my phone, complaining that the firmware didn't give the "required resources". So if the firmware is borked, I'm not sure it would be able to load an external img.
I couldn't wait, though. Sent it out for jtag repair :fingers-crossed:
Dostoevsky said:
That would be great! I did see the S3 fix that loads a debrick.img from sdcard - would that work with hardbricked? Windows wouldn't load the usb drive for my phone, complaining that the firmware didn't give the "required resources". So if the firmware is borked, I'm not sure it would be able to load an external img.
I couldn't wait, though. Sent it out for jtag repair :fingers-crossed:
Click to expand...
Click to collapse
Hello I was wondering if the Jtag did its job?
sirsmokey said:
Hello I was wondering if the Jtag did its job?
Click to expand...
Click to collapse
Jtag should always do the job, unless there was physical damage done to the motherboard.
Dostoevsky said:
That would be great! I did see the S3 fix that loads a debrick.img from sdcard - would that work with hardbricked? Windows wouldn't load the usb drive for my phone, complaining that the firmware didn't give the "required resources". So if the firmware is borked, I'm not sure it would be able to load an external img.
I couldn't wait, though. Sent it out for jtag repair :fingers-crossed:
Click to expand...
Click to collapse
Trozzul said:
Jtag should always do the job, unless there was physical damage done to the motherboard.
Click to expand...
Click to collapse
Thanks for the quick reply , i guess the next question i should ask , is it really worth the 100 bux for the j tag service or to put the money towards a newer phone ?,hmmm rhetorical i guess
sirsmokey said:
Thanks for the quick reply , i guess the next question i should ask , is it really worth the 100 bux for the j tag service or to put the money towards a newer phone ?,hmmm rhetorical i guess
Click to expand...
Click to collapse
The t989 has great specs, only downside is its PPI (really low) if you still love it, I would wait if you want to send it into JTAG repairs, we are on the verge of unbricking our t989 without JTAG! Looks like we need someone with a working t989D though
I have been studying the other 'unbrick' methods, its definatly mind expanding, the amount of knowledge absorbed can seriously make you forget time n space.
If there is anything I can do / contribute holler at me.
Now ill tell you something weird so I flashed a rom not meant for T989D plus I did it all without being rooted. (if it matters) since Since the flash the phone doesn't boot into recovery or show a bootanimation, just darkness.Yet it felt operational in hand.
Once I plugged it back into the PC all I got was a constant notification of drivers that cannot be identified Also it keeps connecting and disconnecting the device.
None of this is weird until I installed OMAP flash and the T.I. drivers for which was used to fix my friends nexus. After he left I plugged my s2 to the PC still nothing. I looked away for a brief moment . Then i noticed MobileGo for Android popped on screen. Visually showing my s2 as an Alcatel rom.
just bizzare.....
The unbrick method on the S2 is a little different, but in General, at http://forum.xda-developers.com/showthread.php?t=2646310 after a little work, I resurrected a QHSUSB_DLOAD 9025 T989D to the point of ODIN and fully working Android OS working, just missing recovery.. Soon to follow in a day or so.
Lord Zog said:
The unbrick method on the S2 is a little different, but in General, at http://forum.xda-developers.com/showthread.php?t=2646310 after a little work, I resurrected a QHSUSB_DLOAD 9025 T989D to the point of ODIN and fully working Android OS working, just missing recovery.. Soon to follow in a day or so.
Click to expand...
Click to collapse
:goodude I could kiss you, thank you so much!!!! that is exactly where my phone was (QHSUSB_DLOAD):good:
Thanks to the devs behind the unbrick , all of your hard work is deeply appreciated, One Luv :laugh:
Now my 989 is working again, ive had it stuck for the past half year. Life saver you are sir
sirsmokey said:
:goodude I could kiss you, thank you so much!!!! that is exactly where my phone was (QHSUSB_DLOAD):good:
Thanks to the devs behind the unbrick , all of your hard work is deeply appreciated, One Luv :laugh:
Now my 989 is working again, ive had it stuck for the past half year. Life saver you are sir
Click to expand...
Click to collapse
glad to hear its working again! might i ask how you went about this?
sirsmokey said:
:goodude I could kiss you, thank you so much!!!! that is exactly where my phone was (QHSUSB_DLOAD):good:
Thanks to the devs behind the unbrick , all of your hard work is deeply appreciated, One Luv :laugh:
Now my 989 is working again, ive had it stuck for the past half year. Life saver you are sir
Click to expand...
Click to collapse
Lord Zog said:
The unbrick method on the S2 is a little different, but in General, at http://forum.xda-developers.com/showthread.php?t=2646310 after a little work, I resurrected a QHSUSB_DLOAD 9025 T989D to the point of ODIN and fully working Android OS working, just missing recovery.. Soon to follow in a day or so.
Click to expand...
Click to collapse
Hi, so I also have a hard bricked t989 galaxy s2 (tmobile variant) and I'm attempting to understand the instructions. However my phone has another issue...usb connection to the computer does not work, it hasn't worked since the micro usb port on the phone was replaced because the old one broke. So really the phone could charge but never connect to my pc as it cant be detected...so what are my options? If i create the sd card with the image, will i still need to connect it to a pc in order to force the phone into download mode? Please help...
sooo, I gues something went wrong... since the new marshmallow images was posted today, there was a thread on reddit on how I can just download the image and rename it and flash it as OTA. The phone reconginzed the image and went half way through the install and then went black. now it wont even buzz or register the charger. Does nothing when connected to the computer either so I assume there is nothing that could be done. Quite a shame, the phone worked quite nicely until is killed it . Anything I can do?
Did you install it thru TWRP?
thekingestkong said:
sooo, I gues something went wrong... since the new marshmallow images was posted today, there was a thread on reddit on how I can just download the image and rename it and flash it as OTA. The phone reconginzed the image and went half way through the install and then went black. now it wont even buzz or register the charger. Does nothing when connected to the computer either so I assume there is nothing that could be done. Quite a shame, the phone worked quite nicely until is killed it . Anything I can do?
Click to expand...
Click to collapse
There is one thing I recommend trying as there is a bug in official firmware where the phone when connected to a computer can turn off randomly and not charge or boot. What you need to do is disassemble the phone and unplug the connector at the top of the phone to disconnect the battery and then plug it in.
krazy23 said:
Did you install it thru TWRP?
Click to expand...
Click to collapse
no, the phone picked up the update from the internal storage
dc959 said:
There is one thing I recommend trying as there is a bug in official firmware where the phone when connected to a computer can turn off randomly and not charge or boot. What you need to do is disassemble the phone and unplug the connector at the top of the phone to disconnect the battery and then plug it in.
Click to expand...
Click to collapse
thanks, I'm aware of that. Some folks experiencing the same issue tried that with no success. My phone is still under warranty and the screw securing the backplate has a seal on it that I dont want to tamper with.
I guess I'll be sending the phone for to Asus for repair...
Don't lose hope.
My phone was in a similar predicament.
No response to any buttons, nothing on screen, no buzzing or LED's at all.
I was able to get it recognized in the xFSTK Downloader and showing up in windows device manager as a Moorefield device.
I tried many times to get it to put the images on the phone through the xFSTK tool and it failed many times.
I was about to give up and tried again this morning and miraculously the writing succeeded and now my phone is in a bootloop (I think the battery may have been completely drained with my attempts to save it's life.)
I have it on charge currently so hopefully when there is enough juice I should be able to flash the raw file and be back up and running.
I see, you can follow the unbricking tutorial in the general section. Works fine for me and saved me from sending it to the service center.
krazy23 said:
Did you install it thru TWRP?
Click to expand...
Click to collapse
I did! And now my phone is dead! But it buzzes when I press the power button for some seconds.. But it's always black
galagala2 said:
I did! And now my phone is dead! But it buzzes when I press the power button for some seconds.. But it's always black
Click to expand...
Click to collapse
That's what happened to my phone, you can follow this thread this worked for me. Unbricking Method
krazy23 said:
That's what happened to my phone, you can follow this thread this worked for me. Unbricking Method
Click to expand...
Click to collapse
do you lose the data this way?
thekingestkong said:
do you lose the data this way?
Click to expand...
Click to collapse
Unfortunately, yes. Because I ticked the "wipe data" checkbox in the ASUS Flash Tool. Not sure what will happen if I don't. :fingers-crossed:
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfon
I also bricked my phone and used the method to fix my phone. Make sure you have all the required drivers installed in your pc/laptop before doing this. I took help of DriverMax to solve the drivers related issues. Make sure before installing and running the XFTSK tool all the drivers and everything is installed otherwise you will see blank forms in the Tool.
I was doing some experiment with DriveDroid and now I am in big mess.
I think I messed up with drivedroid settings and I was not able to see my phone (oneplus 3 rooted LOS 15.1 ) on my computers.
I have tried different computers but all cant detect my phone.
I have tried drivedroid wizard, different usb systems, different usb settings and no luck.
I have tried uninstalling the drivedroid and still no luck.
The phone was going in charging mode only. Its was not going to MTP mode so I can see the phone internal storage in computer
I have tried to do factory reset also but no luck.
Now I mistakenly wiped data partition also and now the phone is with
No OS
No USB detection on phone while in TWRP
No OTG detection
No any ROM.zip file in phone memory.
When I am on TWRP and connect my phone in computer I am seeing same error message and cant see my phone interenal storage.
Now what to do? Any way to flash ROM ?
I am in big mess, and I dont want to spend money on new phone as of now
I hope someone will be my angle and suggest me something to recover and save me from this mess...
Crying out loud now...
Hi, i think you can use adb sideload with twrp
Uruloki64 said:
Hi, i think you can use adb sideload with twrp
Click to expand...
Click to collapse
Phone is not recognized in computer while in twrp mode so it is not able to connct to adb via USB.
Just get os flashed at OnePlus service center.
I did something same in my previous Samsung phone. I took it to service center and told em that it's not booting up and I don't know the reason. They flashed the firmware from scratch, charged me 250 INR and my phone was back to being normal.
aj141 said:
Just get os flashed at OnePlus service center.
I did something same in my previous Samsung phone. I took it to service center and told em that it's not booting up and I don't know the reason. They flashed the firmware from scratch, charged me 250 INR and my phone was back to being normal.
Click to expand...
Click to collapse
Ya.. going there tomorrow. Lets see what they say about it.
amit3880 said:
Ya.. going there tomorrow. Lets see what they say about it.
Click to expand...
Click to collapse
have u tried hard bricked tool for OP3? if not then try it
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Hayatzada said:
have u tried hard bricked tool for OP3? if not then try it
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Click to expand...
Click to collapse
I am not able to follow this as phone is not even coming in USB mode. So its actually soft bricked because can go to twrp and fastboot mode and booting up without OS but USB is not able to detect on my computer.
now the service center guys saying I need to change the motherboard which I dont think is the issue, mother board is not going gone for sure as I can boot up in twrp and fastboot mode. its just may be the usb host controller gone.
Cant decide if I should go ahead with mother board replacement at cost of 10k INR ( phone cost was 28K INR) .
amit3880 said:
I am not able to follow this as phone is not even coming in USB mode. So its actually soft bricked because can go to twrp and fastboot mode and booting up without OS but USB is not able to detect on my computer.
now the service center guys saying I need to change the motherboard which I dont think is the issue, mother board is not going gone for sure as I can boot up in twrp and fastboot mode. its just may be the usb host controller gone.
Cant decide if I should go ahead with mother board replacement at cost of 10k INR ( phone cost was 28K INR) .
Click to expand...
Click to collapse
If you use the Method 2 of the Unbrick Guide, you don't need normal adb/usb mode recognition. Follow that guide scrupulously and step by step. Don't skip any and don't rush.
tnsmani said:
If you use the Method 2 of the Unbrick Guide, you don't need normal adb/usb mode recognition. Follow that guide scrupulously and step by step. Don't skip any and don't rush.
Click to expand...
Click to collapse
We are giving an advice of 10K InR in free and he is not even interested according to his opinion,
Hayatzada said:
We are giving an advice of 10K InR in free and he is not even interested according to his opinion,
Click to expand...
Click to collapse
I even tried that but somehow it is not even recognized as QHUSB_BULK device.
believe me I have tried all things to revive the phone but its not hard brick in my opinion, it can boot into twrp but the when I connect the phone in computer it shows the error message I shown as attachment in my first post.
yes, I have tried 2 different computers and few usb cables.
amit3880 said:
I even tried that but somehow it is not even recognized as QHUSB_BULK device.
believe me I have tried all things to revive the phone but its not hard brick in my opinion, it can boot into twrp but the when I connect the phone in computer it shows the error message I shown as attachment in my first post.
yes, I have tried 2 different computers and few usb cables.
Click to expand...
Click to collapse
Your phone need not be hardbricked to use the Guide. It will work even on a normal perfectly working phone. If your phone is not recognised while following the Guide, it only means one of two things: either it is a hardware fault or you are not following the Guide properly.
amit3880 said:
I even tried that but somehow it is not even recognized as QHUSB_BULK device.
believe me I have tried all things to revive the phone but its not hard brick in my opinion, it can boot into twrp but the when I connect the phone in computer it shows the error message I shown as attachment in my first post.
yes, I have tried 2 different computers and few usb cables.
Click to expand...
Click to collapse
reviewed post
tnsmani said:
Your phone need not be hardbricked to use the Guide. It will work even on a normal perfectly working phone. If your phone is not recognised while following the Guide, it only means one of two things: either it is a hardware fault or you are not following the Guide properly.
Click to expand...
Click to collapse
tried to follow the unbrick guide on windows 10 but phone is not seen as QSBULK device in device manager.
I am going to try on windows 7 as few post said that windows 7 would be better for unbricking than windows 10.
finger crossed, right now flashing windows 7 live iso on USB.
so finally I am declaring my op3 as hardware failure as one of my other phone (yureka) easily identified as 9008 mode in my computer but my op3 is not. so all drivers are installed correctly but somehow my op3's usb hub is failed.
i guess time to move on..
thank you everyone for spending time to help me. it really is supportive and encouraging...
amit3880 said:
so finally I am declaring my op3 as hardware failure as one of my other phone (yureka) easily identified as 9008 mode in my computer but my op3 is not. so all drivers are installed correctly but somehow my op3's usb hub is failed.
i guess time to move on..
thank you everyone for spending time to help me. it really is supportive and encouraging...
Click to expand...
Click to collapse
So sorry about that .... Sad news
@Ammit3880
have you tried plugging in a usb in you phone trough the usb OTG cable? see if twrp recognizes the usb. and just put the needed files on there. maybe windows is just breing ignorant as always
BADA 187 said:
@Ammit3880
have you tried plugging in a usb in you phone trough the usb OTG cable? see if twrp recognizes the usb. and just put the needed files on there. maybe windows is just breing ignorant as always
Click to expand...
Click to collapse
ya.. tried all the ways including various OTG cabel/dongle,, various OS windows 7/8/8.1/10 all the way..
nothing working...
amit3880 said:
ya.. tried all the ways including various OTG cabel/dongle,, various OS windows 7/8/8.1/10 all the way..
nothing working...
Click to expand...
Click to collapse
damn sorry to hear man.
BADA 187 said:
damn sorry to hear man.
Click to expand...
Click to collapse
Got 6T yesterday.... .. Yay!!
Couldnt find other phone competative in the price range.
Time to change the xda signature...
Although I bought 6T now and am kind of happy with that, but I am still missing my oneplus 3 and want to experiment on getting it revived.
By any chance someone can help me answering my doubts.. I would be greatful..
1. Is it ok to replace oneplus3's motherboard with oneplus 3t motherboard ? If by any chance i get any resell op3 or op3t in dirt cheap price I want to know if its ok to use 3T's motherboard.
2. Is there any way I can turn on the wifi from within TWRP and so I can connect to phone via adb over wifi/tcpip ??
Thank you all in advance.