Database Info

How To Unbrick Nexus S? Need Urgent Help.

Dear Geeks,
I need your urgent help/advice. i'm three weeks far to my wedding and have a lot of troubles to handle, of course i need this phone.
let me describe the matter i have.
My nexus s is not booting, not starting, nothing.
what i did?
Last night, power button stopped working. I have experienced this 4-5 months ago. I don't know why, the problem has been solved by itself after few days later. i did nothing at those days. the power button came back. (as to my opinion, this is happening due to software problem) Anyway, i have used the market and installed ''fix power button'' application to use volume buttons for opening the screen.
I slept and when i woke up, i saw that phone needs to be charged but i waited. there was %11 something. i tried to handle the power button, pressed many times on it, thought that it may come back again same as 4-5 months ago it happened.
I removed battery and replaced again. i tried this many times. removed, replaced, used the usb cable via AC charger and phone started but there was no result. power button still was not working.
i thought that if the battery runs out, and then, when i charge the phone, maybe this matter may be solved. (ok this was stupid idea)
phone started to charge. when i plug the usb cable, phone was booting and displaying the google and animation and later it was ok to use.
meanwhile i keep on removing battery and replacing battery while the usb cable connected. but when phone starts to boot, i removed battery and replaced again. phone was ok, it was booting. few times it was booting.
but baaaam.
it is now not starting not booting, nothing.
now, when i replace the battery, phone is getting hot, especially sim-card area. i m removing the battery and connecting the usb. same again phone is getting hot, same sim-card area again.
i have waited enough not to connect the battery or usb charging cable. but no result.
what can i do now? what are your opinions?
my opinions/guess:
-i am using 3500 mah lithium polymere battery. maybe the battery died. i m using that battery more than 1 year, around 15 months. i dont turn off wi-fi so i m charging phone everyday.
- phone crashed during booting. and now the phone is totally brick.(i dont wanna believe this, this phone can be usable, believe me i feel it i think whatever happens, this phone can be usable via software installing or rooting... of course if you dont throw it towards a wall etc.)
by the way, my phone was not rooted. no time to root these days. and of course the phone was not starting.
what is your idea? what happened phone? what should i do?
if you reply, i will be appreciated.
A big advice for people reading this, dont remove the battery when your phone is booting.

I hope someone has a solution, since I have the same probelm...
I searched everything and tried every tool in this forum, but no success...

use search button, there is tens of similar threads...
http://forum.xda-developers.com/showthread.php?t=1524858&highlight=power+button

same thing has happened to me since updating from JB. Just past one year warranty too lol!

greg2826 said:
use search button, there is tens of similar threads...
http://forum.xda-developers.com/showthread.php?t=1524858&highlight=power+button
Click to expand...
Click to collapse
Actually, it was power button failure issue but now, i believe it is not.
But thanks i will try it.

captainirmak said:
Actually, it was power button failure issue but now, i believe it is not.
But thanks i will try it.
Click to expand...
Click to collapse
what is ur theory then?
u might find something here as well http://forum.xda-developers.com/showthread.php?t=1504501&highlight=power+button+conspiracy

greg2826 said:
use search button, there is tens of similar threads...
http://forum.xda-developers.com/showthread.php?t=1524858&highlight=power+button
Click to expand...
Click to collapse
dude, unfortunately those solutions not working on my device.
when i connect charger and i replace the battery, within seconds phone boots itself without power button. it should be this way. removing and replacing the battery helped me to start to boot.
i sense this case a bit different from that solutions.
i need to try with a different battery. my wife has nexus s also. she is very lucky she has no problems i have experienced so far. i will try with her battery.
i think there is a matter with mainboard.
by the way i forgot to say that i dropped my phone last evening. just after then phone was acting that i'm pressing long onto power button. and power button finally stopped working when i remove the battery.
i think this is happened because of dropping the phone from my belly high.
but the last thing i have done which removing the battery while the phone is booting, i wish, i should not have done. i could use it without the power button.

captainirmak said:
dude, unfortunately those solutions not working on my device.
when i connect charger and i replace the battery, within seconds phone boots itself without power button. it should be this way. removing and replacing the battery helped me to start to boot.
i sense this case a bit different from that solutions.
i need to try with a different battery. my wife has nexus s also. she is very lucky she has no problems i have experienced so far. i will try with her battery.
i think there is a matter with mainboard.
by the way i forgot to say that i dropped my phone last evening. just after then phone was acting that i'm pressing long onto power button. and power button finally stopped working when i remove the battery.
i think this is happened because of dropping the phone from my belly high.
but the last thing i have done which removing the battery while the phone is booting, i wish, i should not have done. i could use it without the power button.
Click to expand...
Click to collapse
If you have not rooted your device, you should have you warranty, right? Take the phone back to the carrier, and tell them about your problem. o.o Sorry, I'm of no help, but you're in a horrible situation. Wanted to at least give a little help.

Same exact problem here.
2nd of August - mom's phone turned of and just would not boot or prompt at all. The modem heats up when power is turned on or connected.
Tried
The unbrickable methods (but the computer would not detect the device in any form)
A JTAG - I was able to write the recovery and bootloader - assembled the phone and it just won't boot or prompt
Need to try
Another battery to see if it solves the issue.
Removing the xOM5 resistor and converting to a development S5PC110

Tried another battery - no luck
Did the resistor removal and converted to a dev board - Unbrickable now detects the board!
trying to get the device into fastboot - will update
ru1dev said:
Same exact problem here.
2nd of August - mom's phone turned of and just would not boot or prompt at all. The modem heats up when power is turned on or connected.
Tried
The unbrickable methods (but the computer would not detect the device in any form)
A JTAG - I was able to write the recovery and bootloader - assembled the phone and it just won't boot or prompt
Need to try
Another battery to see if it solves the issue.
Removing the xOM5 resistor and converting to a development S5PC110
Click to expand...
Click to collapse

I had the same problem few months ago. Power button had died. While I was able to boot with remove battery and connect to charger option and I was rooted. But after a week I decided to take the phone to Samsung service center to get the power button replaced. My phone did not have warranty. Samsung took few hours to get the power button replaced and it costed me about $7. I think that's the easiest method. They did not have a stock of I9020 power button, so they fixed a I9023 power button.

Any update? I'm curious to see if you get it working. Had the same happen to my NS a few days ago and would like to see if I can get it going again so I can give it to my stepson.
Sent from my Galaxy Nexus using xda premium

I've given nexus s to samsung service. Actually, power button may be handled by replacing with new one, but with no hope, it will not come back when i read messages about mainboard failure. I will update news whenever it's possible.
we'll see.
I would like to hope it is kind of software matter.
Pls god give my nexus s back, i got extended 3500mah battery.
grrr....

anshumandash said:
I had the same problem few months ago. Power button had died. While I was able to boot with remove battery and connect to charger option and I was rooted. But after a week I decided to take the phone to Samsung service center to get the power button replaced. My phone did not have warranty. Samsung took few hours to get the power button replaced and it costed me about $7. I think that's the easiest method. They did not have a stock of I9020 power button, so they fixed a I9023 power button.
Click to expand...
Click to collapse
So with the hardware mod - instead of selecting Nexus S -> I tied the Galaxy S in unbrickable - first time I've seen the screen alive! - puts the phone into download mode and I can disconnect from the usb and it stays in download mode! .. when i tried to flash odin I get a "There is no PIT partition" error -> this ofcourse is with re-partition and bootloader update UNCHECKED
When I tried Heimdall it wouldnt let me flash without a pit file. So trying Heimdall 1.1.1 - I get Failed to Access device Error: -3
Any chance some one with an i9020T can do me a huge favor? Use Heimdall 1.3.2 - download your PIT file and upload it here?
reaching for string ends out here :/

@ru1dev
i`m in the exact situation right now...
did you solved your problem?

jokkergsm said:
@ru1dev
i`m in the exact situation right now...
did you solved your problem?
Click to expand...
Click to collapse
The power button had to be replaced. I shorted the connection when ever I had to press the power button during the boot sequence. That's how I fixed mine.

[Q] Bricked phone (in a weird way)

So it seems my phone has become a shiny paperweight. The thing is, I don't really understand why it happened. I've been reading how other people arrived at the same situation and although some symptoms are similar, I didn't do any of those things. I wasn't flashing anything, I didn't drop the phone etc
This is what happened: about 24 hours ago, I was using my phone as a GPS (google maps and waze) when it froze. No biggie, it had happened a few times before so I pulled out the battery, waited a few minutes, put the battery back and pressed the power button. The phone started as usual, it got past the HTC splash screen, the boot animation started. A few seconds (maybe 5) into the boot animation, out of reflex, I pressed the power button to turn off the screen. Don't ask why, dunno. As I've said, reflex. So the screen went black. And it stayed that way.
Since then I've been trying to bring it back to life. No luck yet. Here's the status of the phone:
Battery is not empty - when my phone froze yesterday it was about 80% full. I tried a different battery, no change
When I plug in the USB cable to charge it, the orange/green LED that usually lights up, well... doesn't
When I press the power button, the screen backlight turns on for 2 - 3 seconds, then turns off. Pressing VolDown+PWR does the same thing. I know it seems like a battery issue, but I'm pretty sure it isn't
The computer does not see the phone anymore when connected through an USB cable. 'adb devices' doesn't return anything and I don't see anything in the Device Manager (I was hoping for a QHSUSB_DLOAD but no such luck...)
The phone is a HTC Sensation 4G, HBOOT 1.17 (I think), S-OFF, rooted, was running InsertCoin 3.4.6/Android 2.3.5. As I've mentioned, I wasn't doing any of the things that usually lead to a bricked phone like trying to S-OFF/S-ON, flash a ROM etc. I'm currently reading the internets in an attempt to figure out what went wrong and how to fix it. These are the questions I'm trying to get an answer for:
When the phone boots, is it not in read only mode? At least when it gets to the boot animation part.... And if so, even if the power button is pressed... shouldn't the phone just turn off and that's it?
Since the phone seems to be as responsive as a... well, brick... If I send the phone to HTC to repair it, will they be able to tell it was S-OFF and all that?
Does this sound like something that JTAG could fix?
Thanks in advance for any help or info.

stealth.kid said:
So it seems my phone has become a shiny paperweight. The thing is, I don't really understand why it happened. I've been reading how other people arrived at the same situation and although some symptoms are similar, I didn't do any of those things. I wasn't flashing anything, I didn't drop the phone etc
This is what happened: about 24 hours ago, I was using my phone as a GPS (google maps and waze) when it froze. No biggie, it had happened a few times before so I pulled out the battery, waited a few minutes, put the battery back and pressed the power button. The phone started as usual, it got past the HTC splash screen, the boot animation started. A few seconds (maybe 5) into the boot animation, out of reflex, I pressed the power button to turn off the screen. Don't ask why, dunno. As I've said, reflex. So the screen went black. And it stayed that way.
Since then I've been trying to bring it back to life. No luck yet. Here's the status of the phone:
Battery is not empty - when my phone froze yesterday it was about 80% full. I tried a different battery, no change
When I plug in the USB cable to charge it, the orange/green LED that usually lights up, well... doesn't
When I press the power button, the screen backlight turns on for 2 - 3 seconds, then turns off. Pressing VolDown+PWR does the same thing. I know it seems like a battery issue, but I'm pretty sure it isn't
The computer does not see the phone anymore when connected through an USB cable. 'adb devices' doesn't return anything and I don't see anything in the Device Manager (I was hoping for a QHSUSB_DLOAD but no such luck...)
The phone is a HTC Sensation 4G, HBOOT 1.17 (I think), S-OFF, rooted, was running InsertCoin 3.4.6/Android 2.3.5. As I've mentioned, I wasn't doing any of the things that usually lead to a bricked phone like trying to S-OFF/S-ON, flash a ROM etc. I'm currently reading the internets in an attempt to figure out what went wrong and how to fix it. These are the questions I'm trying to get an answer for:
When the phone boots, is it not in read only mode? At least when it gets to the boot animation part.... And if so, even if the power button is pressed... shouldn't the phone just turn off and that's it?
Since the phone seems to be as responsive as a... well, brick... If I send the phone to HTC to repair it, will they be able to tell it was S-OFF and all that?
Does this sound like something that JTAG could fix?
Thanks in advance for any help or info.
Click to expand...
Click to collapse
It reminds me Desire S problem - fried emmc chip... If your phone has no valid warranty, I'm suggesting to see phone's internals and inspect emmc chip.

The phone still has warranty, I will try to have it repaired/replaced. The only thing I'm concerned about is the fact that it was S-OFF and running a custom ROM... And I don't have the knowledge or equipment to try to take it apart and fix it myself

If you have warranty just use it they won't be able to ckeck if phone was unlocked or not since it can't boot up.

[Q] HOX Won't Turn On with Sporadic Red LED

Yesterday, I was using the Navigation app on my phone. It was a busy day, so I think I had left the app running. In my previous experiences with the app, it stays on until I exit the app. Previously, I remember the phone running really hot.
Anyhow, yesterday sometime in the afternoon, I took my phone out and found the screen off. Pushing the power button didn't do anything. So I figure it probably had a drained battery and I plugged it in the wall to charge. About three or four hours later, I pushed the power button again - just to turn on my phone and see if I had any missed texts/calls. Nothing - the screen didn't turn on, but the red LED light was on. So I left it charging through the wall adapter, and went to go do some research about the problem.
Next morning the red LED was flashing. I tried the power button again, but nothing happened. Then I got a little panicky and tried the different button configurations I had read about: holding down the power button for x amount of seconds, holding down the power button and volume down button simultaneously - but again, nothing happened.
Fast forward to tonight - I'm not sure if my phone is charging or not, or if something else sinister is happening to it. I pushed the power button down about a half hour ago, and the red LED turned off. I then, plugged my phone into my computer, and I got a dialog pop-up that said "Device driver was not properly installed" with the driver name "qhsusb_dload".
Any idea what this issue is? Or could you point me to further info somewhere?
Any help is much appreciated!
PS. I got my HTC One X just about 2 and a half months ago at the end of November. My phone isn't rooted, and the most "advanced" thing I did with it was put ADWLauncher on it.

intellectualese said:
Yesterday, I was using the Navigation app on my phone. It was a busy day, so I think I had left the app running. In my previous experiences with the app, it stays on until I exit the app. Previously, I remember the phone running really hot.
Anyhow, yesterday sometime in the afternoon, I took my phone out and found the screen off. Pushing the power button didn't do anything. So I figure it probably had a drained battery and I plugged it in the wall to charge. About three or four hours later, I pushed the power button again - just to turn on my phone and see if I had any missed texts/calls. Nothing - the screen didn't turn on, but the red LED light was on. So I left it charging through the wall adapter, and went to go do some research about the problem.
Next morning the red LED was flashing. I tried the power button again, but nothing happened. Then I got a little panicky and tried the different button configurations I had read about: holding down the power button for x amount of seconds, holding down the power button and volume down button simultaneously - but again, nothing happened.
Fast forward to tonight - I'm not sure if my phone is charging or not, or if something else sinister is happening to it. I pushed the power button down about a half hour ago, and the red LED turned off. I then, plugged my phone into my computer, and I got a dialog pop-up that said "Device driver was not properly installed" with the driver name "qhsusb_dload".
Any idea what this issue is? Or could you point me to further info somewhere?
Any help is much appreciated!
PS. I got my HTC One X just about 2 and a half months ago at the end of November. My phone isn't rooted, and the most "advanced" thing I did with it was put ADWLauncher on it.
Click to expand...
Click to collapse
qhsusb_dload usually indicates a hard brick. take it for warranty repair. given what you've described most likely you've had a hardware failure of some sort.

Sounds like you've ended up in qualcom download mode somehow. When you held down power and volume down, was you're phone plugged in? I think I accidentally made it to qdl mode once when my phone was plugged into the wall. Try unplugging power, and press and holding power and volume down, see what happens.. Otherwise you may be able to get help from 18th.abn who seems to know quite a bit about the qualcom download mode. Good luck.
Sent from my One X using xda app-developers app

It pains me to read your post because I had the same exact thing months ago. The phone turned off while using navigation and never turned on again. At the time JET didn't exist so there was nothing I could do about it.
Look here and see if it might help your situation and maybe avoid a warranty repair
http://forum.xda-developers.com/showthread.php?t=1982442
I've seen this type of post a few times and makes me think that there's definitely something wrong with the evita that's bricking these phones all on their own. Maybe hardware like someone else suggested so maybe warranty repair might be safer.
Best of luck. :thumbup:

Thank you all for your help and suggestions. It appears my phone is dead, completely. I had high hopes, but now I think I'm wasting energy. I called HTC and they said they'd send me an email with ticket info to return it so they could fix it. But they never sent the email. Now I must chase after them and try to get them to fix my phone. Sigh. I would try JET, but I don't run Linux and don't think I'm as tech savvy as I should be to set it up.
Thanks again!

intellectualese said:
Sigh. I would try JET, but I don't run Linux and don't think I'm as tech savvy as I should be to set it up.
Click to expand...
Click to collapse
IMO, if you are bone stock (sounds like you are) its not worth it to mess with JET. Just send the phone to HTC (or your carrier, if they handle warranty matters - they are often easier to deal with than HTC). It may well be a hardware issue, that JET won't fix.

redpoint73 said:
IMO, if you are bone stock (sounds like you are) its not worth it to mess with JET. Just send the phone to HTC (or your carrier, if they handle warranty matters - they are often easier to deal with than HTC). It may well be a hardware issue, that JET won't fix.
Click to expand...
Click to collapse
Yea... if you are in qdl download.. sounds like a hardware failure..sending it back to HTC might be the only way to go..

Up and running again, but w/ new phone
Yup, I took it to my carrier (ATT) yesterday and they couldn't do anything with it, so they gave me new phone right there and then, which was great news. Bad news is I have to start from scratch. But at least I've learned to back up early and often.

Not sure if you could have done anything about this as it seems to be a hardware failure

S6 100% unresponsive with irreplaceable photos contained within... need options

Changing the thread around to reflect the current situation, new text at the bottom of the post.
While out to dinner with my family an hour or so ago, my phone suddenly stopped working. I had been checking some emails when the food arrived, so I pressed the power button to shut down the screen and set the phone to the side. About 30 minutes later, I tried to open my phone to continue where I had left off, only I got no response at all from the device. I immediately tried the normal troubleshooting actions (holding power button for 30+ seconds and attempting to go into recovery mode), but still got no response from the phone. I have since tried charging it at home with it's original quick charger, but even after 15 minutes on the charger, there isn't even a red light indicating it is charging. Is there anything that I can try to fix this on my own, or is it likely that I've got some technical fault that only Verizon can deal with?
Thanks.
PS: I'm 100% sure that no liquid came in contact with my phone during dinner. Even if I wasn't so sure, both the phone and case have been bone dry through the entire ordeal.
New situation:
The "techs" at Verizon were less than useless... While there, they tried fewer fixes than I was able to attempt before telling me that the only option they could offer is to replace the phone. The problem, as I've said a little lower in this thread, is that I've got some irreplaceable photos of my recently deceased cat of 19 years stuck on the phone that I never got the chance to back up before this event.
And so now I need options. I'm willing to do pretty much anything, up to and including tearing the phone apart to manually access the memory unit, but the end result absolutely has to be those photos recovered.

Did you do the hard reset combination (Power, Vol Down?) I've had the problem happen to me before. Usually, what happens is it will lock up when it is having memory issues, freeze, then if I'm lucky, it will come out of it. Otherwise I have to do a hard reset.
It hasn't happened yet since I've been on 5.1.1 but I've only been on that for 3 days or so.
Edit: Just in case you didn't know, the recovery combination is Power, Vol Up, and Home when the phone is actually off. When the phone freezes like that and you don't get a response it's still on but completely locked up until you power off the phone.
Sent from my Super Computer (1976) with Tap Tap Talkolution

DroidXrei said:
Did you do the hard reset combination (Power, Vol Down?) I've had the problem happen to me before. Usually, what happens is it will lock up when it is having memory issues, freeze, then if I'm lucky, it will come out of it. Otherwise I have to do a hard reset.
It hasn't happened yet since I've been on 5.1.1 but I've only been on that for 3 days or so.
Edit: Just in case you didn't know, the recovery combination is Power, Vol Up, and Home when the phone is actually off. When the phone freezes like that and you don't get a response it's still on but completely locked up until you power off the phone.
Sent from my Super Computer (1976) with Tap Tap Talkolution
Click to expand...
Click to collapse
I've tried soft reset (hold power only), hard reset, and recovery, all to no avail, and holding each for long after it's supposed to respond (at least 60 seconds).

Volume down and power should simulate a battery pull. If that does not work, I would recommend going to a Verizon store.
Give your name to the concierge.
When they call your name, try the Volume down + Power again.
It should work then.

Theodric58 said:
Volume down and power should simulate a battery pull. If that does not work, I would recommend going to a Verizon store.
Give your name to the concierge.
When they call your name, try the Volume down + Power again.
It should work then.
Click to expand...
Click to collapse
I'm really hoping they will provide more help than that. There are some pictures of my cat on the phone that I had to euthanize last week after 19 years that I never had the chance to back up.

treblesum81 said:
I'm really hoping they will provide more help than that. There are some pictures of my cat on the phone that I had to euthanize last week after 19 years that I never had the chance to back up.
Click to expand...
Click to collapse
I'm sorry about your cat.
It was more to the point that what doesn't work when you are on your own, will work perfectly when you take it to the technician.
I used to do tech support for phones and tablets. I've seen lots of instances where the customer tries something with me on the phone that they had tried multiple times before, and with me on the phone it works immediately. Try the key combos with it plugged in, with it plugged in to a different charger, with it plugged into your computer. If none of those work, then take it to Verizon.

Theodric58 said:
I'm sorry about your cat.
It was more to the point that what doesn't work when you are on your own, will work perfectly when you take it to the technician.
I used to do tech support for phones and tablets. I've seen lots of instances where the customer tries something with me on the phone that they had tried multiple times before, and with me on the phone it works immediately. Try the key combos with it plugged in, with it plugged in to a different charger, with it plugged into your computer. If none of those work, then take it to Verizon.
Click to expand...
Click to collapse
All of this was done before taking it to Verizon. All key combinations were tried unplugged then plugged into 3 different chargers and also my computer with 3 different cables and several different USB ports. When I went to Verizon, they tried the key combinations unplugged and then tried plugging it in and seeing if it would take a charge... hence the assertion that they tried less than I was able to attempt at home.

Time to find someone who can repair the phone locally. Any type of warranty or factory repair will cost you the pictures.

Sounds like it's safe to say the phone is beyond simple trouble-shooting. I found myself in a similar predicament last year when I busted the screen on my S4. I dropped my phone on some concrete steps and the screen (in addition to being shattered) went completely black, but I knew the phone was still working because I could still hear the person I was taking to on the phone lol.
I ended up replacing the phone through Verizon. They referred me to some third party company that agreed to replace the phone for $100 and sent me a replacement with a box to put the busted one in. At this point I found myself presented with a unique opportunity, given the fact that I had both a working S4 and my broken one.
Because I didn't have the chance to back up the phone before I lost access to it (it's pretty hard to unlock a phone without the screen) I looked up a guide on how to disassemble the S4 on YouTube in order to gain access to the motherboard. The whole process was relatively easy to carry out and I was able to disassemble both phones, switch the motherboards, backup the information I needed, and switch them back.
Sorry for the long-winded response. I realize this is a pretty drastic measure to take and that you may not have access to a second S6. It's also entirely possible that the motherboard on your phone is part of the problem so switching it wouldn't help much in that case (like I said, I knew my phone was still working despite the screen). Just wanted to offer another option =).

I am in a similar predicament, desperate to get my photos and videos back and have been watching your thread for some ideas. My 7 week old Verizon Samsung Galaxy S6 G920VVRU4BOG9, android version 5.1.1. ceased to do anything on Monday for reasons unknown. It is now back on but it has been wiped clean. I had to do a hard reset. Samsung & VZW tech support were not helpful. May I ask what model your phone is? Provided you are able to get yours back on, I'm wondering if you may have some success with some of the following:
Wondershare Dr Fone for Android
Asoftech Data Recovery
Kvisoft Data Recovery
Ease US data recovery.
I could not get them to work because you must first have a rooted phone to retrieve them and mine apparently can't be rooted. I apologize if this is redundant but I thought I'd throw that out there in case you might have a change of recovering those photos. I'm sorry for your loss. It's very hard to lose a beloved pet.

bricked S7?

Hi,
I think I have bricked my S7.
Yesterday I installed Superman Rom and everything was working fine until this afternoon.
I played a bit around and somehow my S7 got stuck and it seemed like i messed something up. I was in some kind of bootloop so i flashed everything new -Bootlaoder, Modem and Superman Rom.
Now I have a black screen and the LED is light up in blue.
I can't do anything. Tried to restart with Home Vol- and Power key but it doesn't work.
If I connect it to the Computer it won't be recognized.
Strange thing is, if I press the Power Key the computer recognizes Exynos8890 in the device manager, but only if I keep pressing the power key.
As soon as I release the power key the computer recognizes nothing...
Does anyone have an idea?

Try holding Volume Down & Home & Power until the phone reboots twice, keep the buttons pressed for 2 full reboots, and hopefully the 2nd one will get you back into download mode

Thank you for your help!
I tried that but it doesn't work.
It's strange because I can do what I want and nothing happens.
Black screen and blue light. It doens't even turn off or reboot...
Only thing what happens is that exynos8890 appears in the device manager as long as I keep pressing the power button.

Same problem as me?
http://forum.xda-developers.com/galaxy-s7/help/boot-loop-bricked-t3499109/post69596073#post69596073

Sounds different.
Because you are able to get into recovery and download. I'm not able to do that

alexx3333 said:
Sounds different.
Because you are able to get into recovery and download. I'm not able to do that
Click to expand...
Click to collapse
How long are you holding the button combination for?
Try 30 seconds+

I tried for several minutes, but the phone doesn't do anything.

I can only think you'll need to wait until the battery runs out, the phone shuts off, then when you charge it again, try the download mode button combo when you power it back on

Ok thank you.
I thought the same.
Unfortunately the battery was at 90% so I think it will take a few days/weeks until it dies...

alexx3333 said:
Ok thank you.
I thought the same.
Unfortunately the battery was at 90% so I think it will take a few days/weeks until it dies...
Click to expand...
Click to collapse
Connect the white Micro > Normal USB adapter that came with the phone to the MicroUSB port, and connect a power hungry USB device to it, I just tried with a USB desk fan and the phone powered it on spinning
That will drain the battery quickly

Great idea but it doesn't seem to work.
Looks like I have no power in the USB connection.
Seems like the phone is totaly frozen.
Ok so how it looks at the moment, my only choiches are wait several days until the battery dies (don't know how long this will take) or sending it to Samsung for a repair.
Thank you for your help!

Good luck, if I think of anything else I'll reply here, hope you get it sorted
EDIT - Did you try holding the power button while you had the USB device connected, to see if it provides USB power then?

Wow, the exact same thing literally happened to me yesterday.
I wasn't doing anything to the phone - it's completely stock and unrooted, and I wasn't messing with anything. At the time it happened, I scrolling through the task switcher when all of the screenshots of running apps suddenly became white squares. I tried pressing the home button but it didn't respond (though I could still scroll fluidly through the white squares). A few seconds later the screen went black and that was it. Dead dead dead. Totally bricked. The only response I can get is "Exynos8890" in the Device Manager when holding the power button, just like you.
This really sucks because I paid full cash and imported an international version, so I have no warranty. I'm off to the Samsung store to plead with them about honoring the warranty anyway, maybe if I offer some cash on top.
I suspect the storage chip failed. Yesterday before it died, I was downloading all of my images off of the SD card to organize them, and I noticed that about 5% of them failed to copy due to an unknown I/O error. Of course I assumed this was a corrupt SD card, not internal storage. I did manage to pull them all off (though some were damaged) through a combination of adb shell, dd, and adb pull. During the process the phone hard-locked a few times, but each time I was able to reboot via the VolDown+Power combo.
When the phone finally died for good, it was several hours after I had finished copying the photos and since hte last reboot. It had been working perfectly since then - I was browsing reddit, watching netflix, etc. However, given that I got the white squares in the task switcher right before it kicked the bucket, I think the internal storage was actually to blame, not the SD card. The white squares indicates that it was trying to fetch the screenshots off the disk and failing.
It's very odd that I cannot find any other instance of this kind of failure on the internet except this one thread, which happened on the exact same day that my phone died. Very strange.

*Detection* said:
Good luck, if I think of anything else I'll reply here, hope you get it sorted
EDIT - Did you try holding the power button while you had the USB device connected, to see if it provides USB power then?
Click to expand...
Click to collapse
Yes I have tried that but no power at all...
stoanhart said:
Wow, the exact same thing literally happened to me yesterday.
I wasn't doing anything to the phone - it's completely stock and unrooted, and I wasn't messing with anything. At the time it happened, I scrolling through the task switcher when all of the screenshots of running apps suddenly became white squares. I tried pressing the home button but it didn't respond (though I could still scroll fluidly through the white squares). A few seconds later the screen went black and that was it. Dead dead dead. Totally bricked. The only response I can get is "Exynos8890" in the Device Manager when holding the power button, just like you.
This really sucks because I paid full cash and imported an international version, so I have no warranty. I'm off to the Samsung store to plead with them about honoring the warranty anyway, maybe if I offer some cash on top.
I suspect the storage chip failed. Yesterday before it died, I was downloading all of my images off of the SD card to organize them, and I noticed that about 5% of them failed to copy due to an unknown I/O error. Of course I assumed this was a corrupt SD card, not internal storage. I did manage to pull them all off (though some were damaged) through a combination of adb shell, dd, and adb pull. During the process the phone hard-locked a few times, but each time I was able to reboot via the VolDown+Power combo.
When the phone finally died for good, it was several hours after I had finished copying the photos and since hte last reboot. It had been working perfectly since then - I was browsing reddit, watching netflix, etc. However, given that I got the white squares in the task switcher right before it kicked the bucket, I think the internal storage was actually to blame, not the SD card. The white squares indicates that it was trying to fetch the screenshots off the disk and failing.
It's very odd that I cannot find any other instance of this kind of failure on the internet except this one thread, which happened on the exact same day that my phone died. Very strange.
Click to expand...
Click to collapse
That sounds exactly like my Problem.
A faulty storage chip would also explain my Problems before the phone died for good.
The day my phone died I had some Problems. The phone was frozen from time to time until it got into the bootloop, but I thought I messed something up in the Rom because I did a lot of testing and the Combo also did work.
After reflashing the Rom everything seemed to be fine first until it died for good.
Yes it's strange, I also didn't find anything similar on the Internet.

I have learned my phone is from Nigeria. This should be a fun RMA process. FML

stoanhart said:
I have learned my phone is from Nigeria. This should be a fun RMA process. FML
Click to expand...
Click to collapse
Contact Samsung on twitter, unlikely they'll force you to RMA to Nigeria, they'll have service centres in your region

I managed to get Samsung Canada to refer me to a local service center. I drove 1.5 hours to go there today, the dude plugs it into a charger, and the damn thing just lights up like nothing ever happened. Now it's working fine, but I swear this thing was fully bricked before. The battery still had 73% charge when it came back alive...
I'm happy it's working now, but I'm worried it's just going to crap out again at any time.

Update: after the phone revived itself, it worked pretty well for a week. It locked up a few times, but I was able to reboot each time.
But, after a week, it hard-froze again. This time, it happened to be on charge while it froze so the green LED was on. It's been completely unresponsive for 2.5 weeks now, off charger, with the green LED on. I keep waiting for the LED to drain the battery, but it's taking forever. I'm losing hope that it will recover this time. I guess I'll re-start the process of getting in touch with Samsung, or alternatively, look for a replacement motherboard on eBay.
Does anyone know if the G930F motherboard fits into the G930FD body? I don't actually care about dual sim, but I'm concerned the SIM tray/slot won't work with the G930F motherboard.

Update:
so in the meantime the battery of my s7 died but that didn't change anything. I wasn't able to charge it after that so now it was completely dead.
So I contacted Sasmsung.
They replaced the motherboard and the USB connector on warranty.
Seems like it really was a hardware issue...

alexx3333 said:
Update:
so in the meantime the battery of my s7 died but that didn't change anything. I wasn't able to charge it after that so now it was completely dead.
So I contacted Sasmsung.
They replaced the motherboard and the USB connector on warranty.
Seems like it really was a hardware issue...
Click to expand...
Click to collapse
Hi,
Do you need Proof of Purchase for the warranty?
Thanks.