Nexus 5 new screen is not working anymore - Nexus 5 Q&A, Help & Troubleshooting

Hello,
I had an accident and after that my Nexus 5 screen was broken. So I decided to buy an new one from Amazon (~60$) and I tried to replace the screen on my own.
Yesterday I replaced the screen with a YT-Video, then I charged my Nexus 5 an the "Charging-Symbol" showed up.
After that I left the house for 2 hours and when I came back (I left the Nexus at home for charging ofc.) I tried to turn on the phone and nothing happened.
Then I tried to press power and volume down to get into the boot-menu and this also worked and the screen showed everything perfectly (!) and then I tried to start my handy from the boot-menu.
Until then everything has worked well but during the start progress I noticed that the (starting-)animation is really slow and laggy, so I decided to try to reboot my phone by holding power off for around 10 secs.
I tried to start my phone one or two times more and tried to get into the boot-menu, restart bootloader, etc. and then I realized that my phone didn't even want to work anymore. I could(and can) neither get into the bootmenu nor simply start it...
Do you have any ideas?
What suprised me the most is that it stopped working so quickly, so I concluded that I replaced the screen right but anything else went wrong...
Please help me :/
PS:
USB-Debugging is turned off and I cant access my phone with my pc or anythin else

Leave the phone on the charger for about an hour and then try to get into the bootloader.
When my phone is in the process of booting and I force it to power off by holding down the power button, it will not power up until I either leave it on a charger for a bit or leave it power off for a bit, usually 5 to 20 minutes.

audit13 said:
Leave the phone on the charger for about an hour and then try to get into the bootloader.
When my phone is in the process of booting and I force it to power off by holding down the power button, it will not power up until I either leave it on a charger for a bit or leave it power off for a bit, usually 5 to 20 minutes.
Click to expand...
Click to collapse
Thanks, now I could get into my phone and enable USB-Debugging with much lock D)
My problem is, that my phone runs very unstable and shuts down often so I can't really work with it.
Do you know any solution and the more important question:
How can I save my data? I think, that I can save it anyhow if I enabled USB-Debugging with the bootloader and a pc, can't I?

Yes, you could pull the data from the phone using ADB commands.
You could also flash twrp to the phone. Once flashed, you could boot into twrp, mount the data partition, and copy data from the phone to the computer.
You could also use twrp to create a nandroid backup for safekeeping.
Is it possible that there is a loose connection in the phone? Have you tried disassembling and re-assembling?

audit13 said:
Yes, you could pull the data from the phone using ADB commands.
You could also flash twrp to the phone. Once flashed, you could boot into twrp, mount the data partition, and copy data from the phone to the computer.
You could also use twrp to create a nandroid backup for safekeeping.
Is it possible that there is a loose connection in the phone? Have you tried disassembling and re-assembling?
Click to expand...
Click to collapse
I have now moved on!
My charger cabel was broken but now I got a new one!
I can start my Nexus (with some issues) and it runs but sometims it still shuts down and always when I try to plug in my cabel into the Nexus the screen gets black (but on the side you can see that the screen is light up in some way, idk...)
Is there a reason for the heating and for the shut downs? :/

I'm not sure but it seems like the screen has suffered a hardware malfunction because you can see that the backlight is on but no image.

audit13 said:
I'm not sure but it seems like the screen has suffered a hardware malfunction because you can see that the backlight is on but no image.
Click to expand...
Click to collapse
And that means what?
And can I do anything for it? Maybe flash it or something?
Reset, etc..

With a hardware failure, there's nothing that software can fix. Did you try disassembling and re-assembling the phone?
With the old screen, can you see anything on screen? Did the phone power up and charge properly? If yes, put on the old screen to test the other components to see if it charges and powers up.

audit13 said:
With a hardware failure, there's nothing that software can fix. Did you try disassembling and re-assembling the phone?
With the old screen, can you see anything on screen? Did the phone power up and charge properly? If yes, put on the old screen to test the other components to see if it charges and powers up.
Click to expand...
Click to collapse
Yeah first sentence makes sence..
I swapped software and hardware, sry
my other screen doesn't work at all, completly destroyed...
The problem is that I can't imagine what should be the failure...
And yeah, I already tried disassembling and re-assembling it...
Still same problem

I have used cheap 3rd party screens to replace a few N5 phones and they quality is very inconsistent so I wouldn't be surprised if a 3rd party screen fails after a short period of use.

audit13 said:
I have used cheap 3rd party screens to replace a few N5 phones and they quality is very inconsistent so I wouldn't be surprised if a 3rd party screen fails after a short period of use.
Click to expand...
Click to collapse
Nahh but the screen works I think..
Everything looks clear etc and the screen wasn't really cheap with 65$-70$ I guess..
I think it's something else because my phone gets really on near the CPU and this can't be because of the screen...

Where did you get the screen?
If it gets really hot near the cpu, then something else is going on. Could it be possible that there is a short-circuit somewhere?
Since the value Canadian dollar has dropped, I'm also paying about $60 for what was a $40 screen.

audit13 said:
Where did you get the screen?
If it gets really hot near the cpu, then something else is going on. Could it be possible that there is a short-circuit somewhere?
Since the value Canadian dollar has dropped, I'm also paying about $60 for what was a $40 screen.
Click to expand...
Click to collapse
Yeah, I also thought about a short-circuit but I don't know how I can test this.
When I try to start my phone it fails like 4-5 times and then it works most of the time. The fail looks the following:
The "Google" logo appears and then suddenly the screen gets black, but not the "out"-Black (so that screen it out), I mean the "on, but black"-Black (hope u can understand.. xD)
During this 4-5 Tries my phone feels like 40°C-50°C (sry im from Germany, idk the conversion to °F value.. )
After this (I got the phone running one time for about 20 minutes) the phone doesn't heat up so much, if it starts right I think that the temparatur problem is over, but there is still the problem (also if the phone is running for 20 minutes) that it suddenly shuts down... :/
Sorry, idk much about canadian dollar, like I said im from germany and I payed around 65€
Google says, that this is around 67 (US-Dollar)

I don't know what to suggest other than either getting a new battery or new screen. Both items can be very expensive.

audit13 said:
I don't know what to suggest other than either getting a new battery or new screen. Both items can be very expensive.
Click to expand...
Click to collapse
Mhh, ok :/

Related

(solved-post #7) Bricked phone+black screen

I have been running the new cm9 ics ROM for about 2 days now, and had just got all my data and apps sorted and fully working. I sat down, watched some TV, and after 30 mins i checked my phone. Black screen ( i assume its locked) i tap the power button, nothing, again nothing. I now think i must have turned my phone off. I now hold the power button, nothing, again, nothing. I grab my charger, put my phone on charge and notice no orange or green light. I have repeatedly tried to revive my phone but nothing works. I don't know if its the software, battery, charger, Im so confused. Please if anyone has had the same problem, or has any suggestions, i would appreciate it very much. Thanks.
some extra details: i charged my phone over night the day before, so it shouldn't have died ( i know you shouldnt charge overnight, but i do :/)
i wasn't trying to flash anything or messing around with files, it was in my pocket.
i didn't drop it
Gaff3rs said:
I have been running the new cm9 ics ROM for about 2 days now, and had just got all my data and apps sorted and fully working. I sat down, watched some TV, and after 30 mins i checked my phone. Black screen ( i assume its locked) i tap the power button, nothing, again nothing. I now think i must have turned my phone off. I now hold the power button, nothing, again, nothing. I grab my charger, put my phone on charge and notice no orange or green light. I have repeatedly tried to revive my phone but nothing works. I don't know if its the software, battery, charger, Im so confused. Please if anyone has had the same problem, or has any suggestions, i would appreciate it very much. Thanks.
some extra details: i charged my phone over night the day before, so it shouldn't have died ( i know you shouldnt charge overnight, but i do :/)
i wasn't trying to flash anything or messing around with files, it was in my pocket.
i didn't drop it
Click to expand...
Click to collapse
Don't panic. Stay calm. The most of our ics roms suffer from reboots or freezes at this stage of development. Your phone simply froze, this can happen with screen on or turned off. If the three button combo (power and volume + -) does not work, You need to wait until the battery drains out.
if you pull the battery there is a chance to freeze your emmc chip and really brick your phone. If you connect the phone to PC before pulling the Batt there's a little lower risk. But I still don't recommend to do so. After your phone is running again, you should overvolt by 25 to hopefully prevent your phone from freezing again.
Ps.
Really, please stay calm, this happened to me about 20 times on ics roms and I'm not the only one.
Sent by my fingers to your head.
thanks, i will just wait then, is it normal that adb won't recognise the device? and also two things, how long roughly will it take to drain completely? and when it is completely drained, what do i do? charge as normal?
thanks a lot
Gaff3rs said:
thanks, i will just wait then, is it normal that adb won't recognise the device? and also two things, how long roughly will it take to drain completely? and when it is completely drained, what do i do? charge as normal?
thanks a lot
Click to expand...
Click to collapse
1. Yes, if it's frozen adb does not recognize the device
2. Depends on how much loaded your battery was. Could be between 1-12 hours
For me very often it didn't need that long, phone restarted by itself after some time.. (30 mins?) But sometimes I also had to wait long..
3.yes, charge normal
Edit: since your screen is off it could take even more than 12 hours
post your results
Sent by my fingers to your head.
Nothing yet i think i will have to wait to tomorrow
EDIT: 11:00 am GMT still nothing, it's been almost 24 hours; should I just keep waiting?
And is there any way to tell wether it's frozen, or the Emmc chip is broken? Thanks
Hey, I've been looking around the forums, and it seems to me that my phone's emmc chip is fine. I admit I did, in a panic, pull out the battery and re-insert it, but on other forums people with a 'fried' emmc chip can at least boot their phone, mine is just completely un-responsive, with a black screen and nothing, when you put it on charge. Am I right or could you shed some light on the problem?
Thanks
Gaff3rs said:
Hey, I've been looking around the forums, and it seems to me that my phone's emmc chip is fine. I admit I did, in a panic, pull out the battery and re-insert it, but on other forums people with a 'fried' emmc chip can at least boot their phone, mine is just completely un-responsive, with a black screen and nothing, when you put it on charge. Am I right or could you shed some light on the problem?
Thanks
Click to expand...
Click to collapse
Seems to me exactly like the freeze I and a bunch of others are suffering from. If you think you can take the risk, you could try pulling the battery.
1. Connect to PC first.
2. Pull battery.
3. Pull USB cable
4. Insert battery after few minutes
5. Try to reboot recovery with adb
As I said there is a chance of freezing your emmc. You might succeed, but you might totally brick your phone too. I'm not responsible, I told you the risk..
Sent by my fingers to your head.
I had a spare battery lying around, did what you said above, instead putting the other battery in and not going on adb, but nothing happened. I think I am going to have to try what you said above ^^^
Oh and once I have put the battery back in do I turn the phone on? It might sound stupid but I don't want to get it wrong :/
Alright a few details:
My phone connected to the computer with a battery in (I don't have a clue how full it is) is not recognised as a 'device with removable storage'
It won't charge (or the orange light won't come on)
Yes, to see if it's booting, I would suggest to turn it on
As I said, try to reboot via adb.
And I would recommend to reboot into recovery and flash another ROM or backup, you don't want to freeze your phone again today, do you?
Sent by my fingers to your head.
I've taken my bay out and am just waiting a few minutes :/
Alright it seemsbe booting, could be a boot loop though
Edit : it's working I'm on the home screen of cm9
You don't know how much I love you right now thanks so much for all the help (I didn't even need adb, it just booted normally 0.o)
Keep your fingers crossed
Edit: glad you already solved it.
You're welcome mate
Sent by my fingers to your head.
As I said, overvolt by 25 to hopefully prevent the phone from freezing again.
Or simply do flash a stable ROM. I would prefer this as I don't like to freeze my phone and brutally pull the batt
Sent by my fingers to your head.
I'm trawling through pages and pages of ROMs I think I will stick to stable ones now
If you want sense, try endymion, by far the best.
No sense - reaper, fastest ever.
Just my personal opinion.
Sent by my fingers to your head.
I may have not the thread in its entirety..
But did you try VolumeUp + VolumeDown + Power button combination.
Which can often reboot a hung/stuck phone?

[Q] Nexus 5 constantlly turning on and off

For quite a long time I did not make any change on Nexus ROM or applications, but yesterday my Nexus turns off while I was web browsing. I tried to turn it on but it refuses. It is only possible with USB cable plugged in, but then it constantly turns on for 1 second and then turns off, and this is going in endless loop as soon as USB cable is plugged in. But with unplugged cable NEXUS can not be powered on.
The video can be seen on this link
https://www.dropbox.com/s/cvyxii4ctm4aqgu/VID_20141110_190522.mp4?dl=0
Yesterday I somehow manage to get in recovery mode and I wipe cache and Nexus boot ROM, but after 30 minutes of usage it again turns of by itself. After that for more than 100 times I tried to get to recovery mode but I could not.
So, I think that my only chance to wipe cache and put new ROM is through ADB. But I do know how to do that. Can anyone help me?
P.S. I both my NEXUS in US, but I live in Croatia (EU) and Google tells that they can not make exchange for other NEXUS (although my phone is under warranty) because they can only do that for postal address inside US. Because I do not live there and any of my friends or relative will travel in US soon my only way to get my NEXUS working is through ADB.
sounds as your power button is "stuck'.
Try the LG RMA. Worked for me here in Belgium
brom25 said:
Try the LG RMA. Worked for me here in Belgium
Click to expand...
Click to collapse
Where did you both your Nexus, and in which country did you send RMA request?
DTFuser said:
For quite a long time I did not make any change on Nexus ROM or applications, but yesterday my Nexus turns off while I was web browsing. I tried to turn it on but it refuses. It is only possible with USB cable plugged in, but then it constantly turns on for 1 second and then turns off, and this is going in endless loop as soon as USB cable is plugged in. But with unplugged cable NEXUS can not be powered on.
The video can be seen on this link
https://www.dropbox.com/s/cvyxii4ctm4aqgu/VID_20141110_190522.mp4?dl=0
Yesterday I somehow manage to get in recovery mode and I wipe cache and Nexus boot ROM, but after 30 minutes of usage it again turns of by itself. After that for more than 100 times I tried to get to recovery mode but I could not.
So, I think that my only chance to wipe cache and put new ROM is through ADB. But I do know how to do that. Can anyone help me?
P.S. I both my NEXUS in US, but I live in Croatia (EU) and Google tells that they can not make exchange for other NEXUS (although my phone is under warranty) because they can only do that for postal address inside US. Because I do not live there and any of my friends or relative will travel in US soon my only way to get my NEXUS working is through ADB.
Click to expand...
Click to collapse
Shake your phone vigorously for a minute, I've been using that as a temp fix for a dodgy power button exactly as you've described
topgeardave said:
Shake your phone vigorously for a minute, I've been using that as a temp fix for a dodgy power button exactly as you've described
Click to expand...
Click to collapse
And what you did after shaking? I try but I did not helped.
DTFuser said:
And what you did after shaking? I try but I did not helped.
Click to expand...
Click to collapse
It usually helps the button back out again, I think you should RMA to LG, I'm sure they're worldwide. You could always open up the phone and try unsticking the power button if you can't be bothered sending it back.
topgeardave said:
It usually helps the button back out again, I think you should RMA to LG, I'm sure they're worldwide. You could always open up the phone and try unsticking the power button if you can't be bothered sending it back.
Click to expand...
Click to collapse
Power button is not what cause the problem. I found many reports about the same problem, like on this page
http://www.reddit.com/r/Nexus5/comments/29tr5n/nexus_5_wont_turn_on_google_screen_keeps_flashing/
but nothing which I tried did not helped. But certainly power button is not causing the problem.
When the problem appears for the first time I manage to get into recovery and wipe cache, and after that phone booted ROM. After 30 minutes of working phone turns off and now I'm not able to get even into recovery.
DTFuser said:
Power button is not what cause the problem. I found many reports about the same problem, like on this page
http://www.reddit.com/r/Nexus5/comments/29tr5n/nexus_5_wont_turn_on_google_screen_keeps_flashing/
but nothing which I tried did not helped. But certainly power button is not causing the problem.
When the problem appears for the first time I manage to get into recovery and wipe cache, and after that phone booted ROM. After 30 minutes ow working phone turns off and now I'm not able to get even into recovery.
Click to expand...
Click to collapse
Ah damn, sorry to hear mate. Go to LG, only solution you have left.
im in the same boat my phone was just working for the past since i had it and now just like 20 minutes ago it just shut off and now doing the constant turning on and off crap
and im rooted with the latest build from pac-man (a clean install), cant even get into the fast boot and recovery to recover to stock since its doing this bootloop thing
any more help would be amazing
Edited - problem fixed it was something up with the power button, got a couple hard wacks and it booted up perfect
meechieballer said:
im in the same boat my phone was just working for the past since i had it and now just like 20 minutes ago it just shut off and now doing the constant turning on and off crap
and im rooted with the latest build from pac-man (a clean install), cant even get into the fast boot and recovery to recover to stock since its doing this bootloop thing
any more help would be amazing
Edited - problem fixed it was something up with the power button, got a couple hard wacks and it booted up perfect
Click to expand...
Click to collapse
So, since shaking, hard wacks, and anyting physical did not helped after your post I dismantle my phone and without back plate and upper plate on chips my phone works perfectly. So it seems that upper plate which covers chips is the cause of the problem.
For me, not even disassembling has helped, so I bought another motherboard and put it into my phone.
Dancsi said:
For me, not even disassembling has helped, so I bought another motherboard and put it into my phone.
Click to expand...
Click to collapse
the problem occured and i found what it was my power button it wasnt staying in place like its tilting so now i got to buy a new button for it :/
As far as I remember, the button is soldered to the board, and can not be bought separately. I know the second thing for sure, since I was also only searching for a separate button in the beginning...

Nexus S [CM11] - hardbricked, no vigration, no computer detection!

My phone: Nexus S, 16Gb, Rom CM11, Android 4.4.4 (List of updates: https://download.cyanogenmod.org/?device=crespo)
My story
Yesterday, (about 9.00pm 13/12/2015) my phone got some laggy, so I powered him off. I left it there, 15 minutes later I came back, and I forgot that he had been powered off, so I thought it was just sleeping. I picked him up and press PowerButton. Nothing happended!
Then I got a look at CM rom, found that interesting is my Rom just got a new update at 2.00pm 13/12/2015. I think that my phone has auto-updated!!
In the past, sometime he behaved the same: PowerButton not respond. So, after that 1st press, about 5 sec later, I started to press the PowerButton repeatedly and rapidly, hopefully the phone would wake up.
But no, the reality was that he was being off. There were about 6-7 presses, I will describe slowly below (assume between each press is 0.2 sec):
1st and 2nd press: nothing happened
3rd press: the phone vibrated, and Google logo appeared
4th press: (I had no mean to continue pressing, but it was too fast, I couldn't stop) suddenly, the Google logo disappeared (so the logo stayed on screen just for about 0.2 sec; while normally, it should stay there for atleast 5 sec)
5th and 6th press: nothing happened!
And from then on, no more, anything happened.
What I tried
Hold PowerButton for even 1 minute: nothing happen!
Hold PowerButton + VolumeUP for even 1 minute: none!
Hold PowerButton + VolumeUPandDOWN for even 1 minute: none too!
Connect to charger (wall or pc): no Battery Animation show up! BUT the phone and Battery get warming up!
Take out the Battery for even 15 minutes, then put it back, and PowerButton: nothing!
And the phone not get recognized by PC too.
Sumary
No display
No vigration
No recognized by PC (because of this, I can not follow this method: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
More Information
In the past, the VolumeDOWN sometimes seems get stucked, cause the phone silent and auto boot to safemode, after many try to press and reboot, the phone may get out of safemode (because VolumeDOWN back to normal)
PowerButton sometimes not respond.
My Battery is not good, sometimes it drops too much! Eg: having 50%, after reboot, dropped to 3%, and start to increase slowly, max around 30% and become normally.
Hope you guys have some ideas! I still can't do anything, when the phone is not regconized by PC!!
Thanks for reading!
Thank you!
Hey,
2 things come to mind and I bet are both the problems. First off you need a new battery and you seem to know this, very cheap now a days but still buy a good one as cheap knock offs are abundant and don't support the power they say, try mugen, anker or stock oem
Also you need to replace power button, this phone was always notorious with bad ones, a new one is cheap but many often found just a loose connection so if you open up the phone, check the ribbon connections and then throw in that new battery all should be well, hopefully
Best of luck!
demkantor said:
Hey,
2 things come to mind and I bet are both the problems. First off you need a new battery and you seem to know this, very cheap now a days but still buy a good one as cheap knock offs are abundant and don't support the power they say, try mugen, anker or stock oem
Also you need to replace power button, this phone was always notorious with bad ones, a new one is cheap but many often found just a loose connection so if you open up the phone, check the ribbon connections and then throw in that new battery all should be well, hopefully
Best of luck!
Click to expand...
Click to collapse
Thank you. I'll try your suggest ASAP.
But I'm wondering, that do you think that CM Update maybe also a reason?
I kind of doubt it as that should only effect the software, if you were getting a bootloop or anything to that extant yeah, but being it won't power on at all I doubt it
thank you
Nope, I've seen these symptoms before - exactly the same thing. Dude, I think your phone is Superbricked.
I've got a stack of 3 Nexus S 4G's that have exactly the same problem - the eMMC card is trashed by a buggy "secure erase" implementation. See: https://wiki.cyanogenmod.org/w/EMMC_Bugs
My "working" one was working great, even set it up to sell on eBay, when I went to wipe its data with a factory-reset from the settings menus. When it shut down to reboot, I pulled the battery. That's what bricked it - because the eMMC was halfway through a background erase/rewrite procedure, it wiped out the boot loader somehow and completely bricked the phone. It now does precisely, exactly the same thing you describe - absolutely nothing, except when it's plugged in, it warms up after a while.
Best I can tell, the only way out from here is to use a JTAG device to reflash the chip, but even then, the eMMC itself might be "unbootable" (i.e. can't start up, can't be read or written, can't be reformatted/restored).
I just called it "end of life" for those phones and now they're just a sour reminder on my shelf
FalconFour said:
Nope, I've seen these symptoms before - exactly the same thing. Dude, I think your phone is Superbricked.
I've got a stack of 3 Nexus S 4G's that have exactly the same problem - the eMMC card is trashed by a buggy "secure erase" implementation. See:
My "working" one was working great, even set it up to sell on eBay, when I went to wipe its data with a factory-reset from the settings menus. When it shut down to reboot, I pulled the battery. That's what bricked it - because the eMMC was halfway through a background erase/rewrite procedure, it wiped out the boot loader somehow and completely bricked the phone. It now does precisely, exactly the same thing you describe - absolutely nothing, except when it's plugged in, it warms up after a while.
Best I can tell, the only way out from here is to use a JTAG device[/URL] to reflash the chip, but even then, the eMMC itself might be "unbootable" (i.e. can't start up, can't be read or written, can't be reformatted/restored).
I just called it "end of life" for those phones and now they're just a sour reminder on my shelf
Click to expand...
Click to collapse
thank you!!
my heart just stop breathing :'( :'(
God, I wish there were a solution to it. I'd really like to donate a phone to anyone that thinks they have the tools or skills to make a "how I did it" explanation - involving whatever tools/software are necessary - to bring these phones back and help us all. I bought 2 of those 3 phones as "for parts" on eBay, and it turned out that both of those phones appeared to have exactly this same issue (though one also had a cracked glass). I even verified the issue by swapping in my good phone's eMMC (at least on the NS4G, it's a swappable card module), and the boards booted up. I only needed the one for the good screen (as I had a good board but completely destroyed display panel) - and that's how I got my one working again.
Then, in the end, I accidentally stumbled upon the method by which the previous two phones were bricked - and now there are three. It seems like a fairly common problem. :/

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.

Screen + Storage Problem

Hello,
Let me make this as short as possible. I have a 3 and a half year old Nexus 5. Just got off a plane 6 hours ago, and when i wanted to check my Facebook the display looked like it failed. I had red vertical lines running up and down the stream and the brightness was extremely low even though the setting in the phone had not changed. All the while, the phone was also impossible to maneuver. I rebooted it, the problem persisted for 5 minutes, and then after a quick lock-unlock, it fixed itself.
About 10 minutes later, when I again tried to unlock my phone to check if things were okay, the display went completely black. If I connect the phone to a charger, the display gets a little illuminated like it's going to start but nothing actually happens, I cannot see anything on the screen. The phone is responsive, if I plug it into a PC it starts charging and the PC recognizes it, but I can't see absolutely anything but black on the screen. Now with the questions:
1) What type of problem do you think this is. Wiring, display, or dead phone and no repair possible? As a best guess at least.
2) Before I take the phone into a service, I would like to know if there's any way I can download the pictures and data I had stored on it that was not yet backed up. As I said, I was just returning from a trip and I have some pictures on it, and while the PC recognizes the phone, it is put automatically in USB Charge mode and not USB Mass Storage Device mode. The phone is NOT rooted and USB Debugging was enabled before it crashed. The phone is up to date with the latest firmware.
Thank you in advance.
Does the touch function work? Is the bootloader unlocked?
If yes to both, you could load twrp, boot into twrp, mount the data partition, and copy off files.
It sounds like a failed screen to me. Was the phone ever dropped or exposed to moisture?
audit13 said:
Does the touch function work? Is the bootloader unlocked?
If yes to both, you could load twrp, boot into twrp, mount the data partition, and copy off files.
It sounds like a failed screen to me. Was the phone ever dropped or exposed to moisture?
Click to expand...
Click to collapse
The screen is pitch black. If I touch the screen I can't feel anything or see anything, and I have no certainty I would be in the right menus. The only reaction I get is if I plug it in or reset it. The phone was never dropped, it is still in impeccable condition, no scratches or bumps. It wasn't exposed to moisture either, I wonder if the flight had anything to do with it, pressure and all.
So basically, apart from what you mentioned, there's no other way if my data is not backed up? I will be taking it in tomorrow, hoping for the best.
It's weird that this happened suddenly. The simplest solution may be to place the motherboard into another working phone.
You didn't answered about unlocked bootloader.
adrian.lupas said:
Hello,
Let me make this as short as possible. I have a 3 and a half year old Nexus 5. Just got off a plane 6 hours ago, and when i wanted to check my Facebook the display looked like it failed. I had red vertical lines running up and down the stream and the brightness was extremely low even though the setting in the phone had not changed. All the while, the phone was also impossible to maneuver. I rebooted it, the problem persisted for 5 minutes, and then after a quick lock-unlock, it fixed itself.
About 10 minutes later, when I again tried to unlock my phone to check if things were okay, the display went completely black. If I connect the phone to a charger, the display gets a little illuminated like it's going to start but nothing actually happens, I cannot see anything on the screen. The phone is responsive, if I plug it into a PC it starts charging and the PC recognizes it, but I can't see absolutely anything but black on the screen. Now with the questions:
1) What type of problem do you think this is. Wiring, display, or dead phone and no repair possible? As a best guess at least.
2) Before I take the phone into a service, I would like to know if there's any way I can download the pictures and data I had stored on it that was not yet backed up. As I said, I was just returning from a trip and I have some pictures on it, and while the PC recognizes the phone, it is put automatically in USB Charge mode and not USB Mass Storage Device mode. The phone is NOT rooted and USB Debugging was enabled before it crashed. The phone is up to date with the latest firmware.
Thank you in advance.
Click to expand...
Click to collapse
It's just the ribbon cable .You can change it by yourself it's too damn easy plus the cable is really cheap
It's either the flex cable or the LCD itself.
cheeze.keyk said:
It's either the flex cable or the LCD itself.
Click to expand...
Click to collapse
It was the LCD. I got a replacement LCD but now even with my brightness to the maximum, the phone still is darker than before. I also got a new battery in it. Is there an option to change the brightness that is hidden, or some kind of power saving option?
Thanks.

Categories

Resources