Hi everybody,
i think my Nexus 4 died yesterday Was listening to music while i was in the workshop, suddently music stopped and the display wont turn on again. Tried to restart it a couple times but nothing happend. Than put it on the charger for a while, than my computer. There, it showed the charging animation if your phone is completly shutdown and when i pushed the start button it booted up quiet normaly, but "optimised" my apps again. After unlocking the Sim card, i pushed the homebutton and it crashed again. Since than, no picture on the screen anymore. It starts up(vibration from boot) and is even recognised via usb "remove mako" but i couldn flash a stock image with the nexus toolkit, it stucks in "waiting for device".
Was running CM 12.1 from end of june.
Is there anything i can test if my LCD died, or flash a stock rom without any displayinformation?
Best regards from me and my good old Nokia E51, which is no back in Service again.
Basher
Can you get in recovery mode or anything else accessible with button combinations? What happens when you hold power and volume down and up together for a couple of seconds? Try holding them for 10 secs.
Related
I've had my nexus 7 for about 3 weeks now. Was working great until last night. I haven't altered it such as rooting or custom ROM since I bought it. Besides some apps I have installed via the play store, it can be considered very very factory stock.
Battery was low and it started the automatic shut down because the battery level hit the critical point. It shut down and then I plugged it back in and turned it back on. It was halfway through the boot up (showing the multi-colored X) and the screen went blank and I heard what could be a farting sound, then nothing.
I've tried holding down the power button for more than 30 seconds (timing it on my watch) and I've tried the power button and both volume up/down buttons in the same manner. Nothing.
I let it charge overnight on the factory charger with factory cable. No change.
I opened the back up and disconnected the battery for a few minutes then reconnected. No change.
I plugged it into my computer and it detects and I was able to install the drivers for "Asus Transformer Prime APX Interface". If I hold the power button for 10 seconds while it is connected to my PC the PC detects that the device is disconnected and then reconnected about 5 seconds later. So the device does something.
I tried using the android-sdk to communicate with the device but nothing. ADB doesn't detect the device, fastboot doesn't either.
At this point, I'm thinking the device is as hard bricked as can be but hopefully someone here can tell me otherwise. If I don't get a response within a week, I will be attempting to get a replacement - my wife bought it brand new for me from a private seller on eBay, so I don't have an actual store to return it to.
Hi! I managed to hard brick my galaxy s7 edge and i wanna see if someone here knows if its hard bricked or soft.
Got root and had renovate rom 2.0 ( n7 port) then i wiped my phone and flashed renovate 3.3 (s7 edge stock)
my phone worked fine on startup and i started to restore my old apps through gmail. i thought it would take a while so put my phone in my pocked and let it be fore about 20 minutes then when i took it up it was complete dead. i had about 67% before it died i tried everything (vol up down home all together) for at least 15+ sec. had it charge over the night ( i noticed that the phone didnt get warm or any leds shown) in the morning i tried everything again and nothing. when i connect my phone to my computer i hear the connect sound and then it disconnect a sec later. if i hold power button down and connect it ( and dont release power) my computer recognize it as onyx8890 and if i release powerbutton it disconnects. cant boot it in any way whatsoever. so what do you think? its only a week old thats the worst part of it!
I have left it to the store I bought it from for warrantable but its still rooted and have a rom on it. well if its complete dead they cant see if its rooted so thats one good thing.
still want to hear you opinion
sorry for bad english
so, from what I understand, u cant boot into any mode, are u even able to see something on screen? (logo, boot screen, etc.) U can try JIG (it somehow make any samsung device go to download mode). otherwise idk.
Hi guys, I have the same problem with my S7 Edge.
Can anyone help?
OK. So I managed to recover my phone.
The phone was dead because of a software crash(nothing on display, no LED light, power+vol. down for reset not working) and when connected to my PC - nothing (just a connect and after 1 sec. a disconnect sound).
But if I kept the power button pressed without letting go, my PC would detect the phone as exynos8890.
I tried to keep pressing the power+vol. down while connected to PC and I realized that the combo worked because after ~7 seconds the phone would disconnect and reconnect itself (but still as exynos8890).
But I tried a different approach. While connected to the PC I tried to keep on pressing power+vol. down. And I could hear that it disconnected and reconnected. But I did not let go of the buttons. And again a connect and disconnect. And again. And after literally 5 minutes of the buttons kept pressed down without letting go and countless reconnects there was finally a change. The disconnect sound was not heard after the connect sound. At that point I stopeed pressing the buttons and when I looked at the phone I could see that the battery icon appeared. Since the phone was connected to my PC, after 1 min. the battery started charging (it was charged 31%). And after that my phone booted fine.
wow
Hi I have just bought an s7 which turned out to be a Korean G930L but I cant get any response out if it apart from the 2 bottom leds and and the blue one. No response from trying to get into recovery or download mode, basically a black screen though it does vibrate on what i think is start up. It is found by pc and Odin and charges ok, I can tell as I can see properties on pc. But no other response. Is it possible that the previous owner tried to root it using non korean rom or TWRP? Any advice on how to fix either getting TWRP on or screen to light up. I am sorry for being so vague I have pulled it apart and checked all of the connections, screen, motherboard etc but nothing. Or chuck it out or put back on eBay. I tried your idea but it only booted once in that 5 minute period so I tried without it plugged in and rebooted several times but still no screen response.
Hi there,
My Note 4 started playing up 3 weeks ago, it started to lag, freeze and reboot. I managed to bring it back to function as my daily driver (handy as I didn't have another phone!) with the Wake Lock app. Sometimes when I'd try to boot it up, it would be glitchy and it would take a while to fire up again, most often I'd have to boot into TWRP and wipe the cache, but then it would be fine. The wake lock app was set to auto run and all was good, apart from a major hit in battery life.
Today I started to set up my replacement N910F (bought used). It too was running stock MM, I'd rooted this one too and installed xposed. All was going well until I went to remove the sd card from the first phone. When I went to reboot.....nothing.
I tried to remove the battery and hold down the power button and then try again. Nothing. Tried holding down the power button for a few minutes with the battery removed and then trying again. Nothing. I even tried holding it down for a couple of minutes, putting the battery in for 10 mins and then trying to power it up. Nothing.
It doesn't show up on my PC or with Odin. Nothing happens when I plug it into the charger. I've tried 3 different batteries. All with the same end result. Nothing. :crying:
Is there ANYTHING I can do?
woldranger said:
Hi there,
My Note 4 started playing up 3 weeks ago, it started to lag, freeze and reboot. I managed to bring it back to function as my daily driver (handy as I didn't have another phone!) with the Wake Lock app. Sometimes when I'd try to boot it up, it would be glitchy and it would take a while to fire up again, most often I'd have to boot into TWRP and wipe the cache, but then it would be fine. The wake lock app was set to auto run and all was good, apart from a major hit in battery life.
Today I started to set up my replacement N910F (bought used). It too was running stock MM, I'd rooted this one too and installed xposed. All was going well until I went to remove the sd card from the first phone. When I went to reboot.....nothing.
I tried to remove the battery and hold down the power button and then try again. Nothing. Tried holding down the power button for a few minutes with the battery removed and then trying again. Nothing. I even tried holding it down for a couple of minutes, putting the battery in for 10 mins and then trying to power it up. Nothing.
It doesn't show up on my PC or with Odin. Nothing happens when I plug it into the charger. I've tried 3 different batteries. All with the same end result. Nothing. :crying:
Is there ANYTHING I can do?
Click to expand...
Click to collapse
Could be battery is dead or your device is hard bricked.
You might wanna see link below to unbrick method
http://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
Trex888 said:
Could be battery is dead or your device is hard bricked.
You might wanna see link below to unbrick method
http://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
Click to expand...
Click to collapse
It's not the battery as I've tried the 3 that were working with the phone originally, and I've just tried the one form the "new" phone.
After looking through the link, that doesn't look like an option - the phone needs to be detected by the pc. Mine was connecting fine earlier, so I know it's not a lack of drivers. I makes a noise when plugged in, but then isn't shown.
woldranger said:
It's not the battery as I've tried the 3 that were working with the phone originally, and I've just tried the one form the "new" phone.
After looking through the link, that doesn't look like an option - the phone needs to be detected by the pc. Mine was connecting fine earlier, so I know it's not a lack of drivers. I makes a noise when plugged in, but then isn't shown.
Click to expand...
Click to collapse
It should be detected in device manager under ports section.
If the pc makes a sound when the device is connected, that means the device is fine. You can try the debrick method given on my thread.
Try it and report.
Reporting Via N910G
Don't ask me how but.....it suddenly came to life this morning! I put a battery in it and tried to go into recovery, and voila! No rhymne nor reason to it but she's up and running for the mo!
Thanks for the suggestion yashthemw but thankfully I've not had to try it!
I have a galaxy s4 (i9500) and got it in used condition, a year ago. Never suspected a single problem in it.
Today I powered off my mobile for charging then after 25 minutes I took it off. I held the power button then I saw my boot logo(Where there is written Samsung Galaxy S4 GT-i9500). That logo kept showing as usual for 2 seconds and screen went black and again that logo appeared for 2 seconds and screen gone black and again it appeared, so, I'm stuck in kinda loop not a bootlooop exactly(maybe because bootloop refers to being stuck on boot screen while in my case its boot logo). I then removed the battery and inserted it back after an hour and as soon as I inserted it back the mobile itself turned on as if I held power button but this time again I was stuck in that loop. Moreover when I tried going into download mode, I didn't even need to hold the power button along with the volume down and home, it itself proceeded to confirmation screen of odin mode. And after that confirmation screen appeared saying that whether I really want to boot into download mode, disappeared itself after like 3 or 4 seconds even though I didn't press any key. And in case I press vol up key confirming to boot to download mode, then it again takes me to that loop. I'm too much confused . I can't even flash the firmware as it won;t boot to download mode neither am I able to boot into recovery.
Now do u really think the problem might be the power button(Which is maybe stuck in the state of pressed).
Or else it can be the battery coz my battery is also just average not too good?
I also inserted the command( in build.prop file) for enabling nav. bar and the code was correct but I never rebooted after inserting that. this was the first time I rebooted after that.
SOrry for some bad English.
Do you have something like this? I'm now having problem with getting my phone back to work...
https://youtu.be/HxnV-tn2vpA
From what you say it seams like power button problem, try to start the phone and connect it to the charger. When it start take out the battery, it will be powered by charger and you will eliminate battery problem.
Hello,
As a newcomer to the forums, I'd like to ask for some help. I tried some of the methods described in several posts, to no avail. The situation is this:
Yesterday, I forgot my Defy+ on my desk and the alarm went of at 21:00 as programmed. It went for about 30 mins after that it was cancelled by default. I switched the wifi on and the phone restarted. In fact it stuck in a restart loop, mostly with the Motorola logo on screen. I took the battery out, kept it for like 30 mins, popped it back in and it went to the recovery console with the exclamation mark and the little droid icon. It stayed there for 30 sec, after that it went dark. Now this happened before so I did not panic and tried the battery swap again.
However, this time the phone is silent. Dead. If I plug it into a PC it gives me the notification sound (like when you pull out a usb drive from your PC) and the battery still gives out 3.7V.
No reaction for pressing the power button or volume up/down or any combination of that.
My question is: Is there a way to revive my beloved phone or is it just a piece of history now?
Additional info: Yes, it was a stock Defy+ with Android 2.3.4.
Any help is appreciated!
Update
Update: When I plug it into a PC with the Volume- button pressed down, a white LED starts to light until I disconnect it. During this if I try to enter bootloader mode, the PC recognises it as an unknown device and immediately prompts me to reconnect it.
Any ideas?