Rooted and ran https://forum.xda-developers.com/showthread.php?t=1947875 as a custom rom forever ago. Worked flawlessly no issues.
While trying to recover some old photos/messages from the phone. I had a couple random restarts due to macgyvering a different samsung battery at a close to 3.7Volts as the replacement battery I got forever ago was bloated and inop. I was able to salvage somethings but not everything before I decided to get stop getting frustrated and struggling and purchase a new correct OEM battery. After being unable to charge the battery either through the phone (had the dim blinking blue led) or external charger. Froze the replacement battery put it on my external charger and got it juiced up. When it was charged I threw it in the phone and got a black screen and solid blue LED while charging or trying to boot. I can get the led to flash by holding power and vol down, but then it just stays blue.
Power + Vol Down gets me nowhere, Power + Vol Up & Down same deal. So I bought a micro USB jig. Still nothing.
Tried ODIN3 v1.85, 3.13.1, Samsung Kies, some other Odin 1 touch. Can't get the phone to connect to pc or post a screen to recovery. Using Samsung USB Driver Version 1.5.65.0
So im trying to preserve the data that is hopefully remaining that I want, and get the device to boot.
I can only assume based on searching the forum, that my phone is hard bricked and potentially the only option to recover anything from it at this point is a JTAG. Or I'm SOL.
Related
Hey guys, I'm having a problem I thought you might be able to help me with.
I had my phone hooked to the charger. When I went back to it a few minutes later, the phone was powered off. There was also no charge LED lit either.
Now, I am not able to power the phone on at all. I get no LEDs when I plug it up.
I have tried taking the battery out several times. Has anyone else ran into this issue.
Also, I am not rooted, I am running on stock software.
You don't get the slash screen or anything?
Have you tried to get into recovery via adb?
We're you rooted / custom rom name?
You sound bricked
I do not get a splash screen or anything what so ever.
This phone has never been rooted. My original phone was, but after an issue with roaming and 3g I swapped it and decided not to root the new phone.
I have tried powering on with the volume button down, but still nothing. My pc does not recognize it at all when I plug it in either.
Also, I have tried 3 different charges and cables as well.
I had the same problems. I just weighted and mess with the power button and the battery. Steps that I did
1. hold the power button for like 5 second w/battery on phone
2. than while holding the p/button took the battery out and than put it back
I did this like 5 time, than it came on.I don't know what it was luck or what but it work for me. All of this happen before I rooted the phone.
Didn't work
Thanks for the input though.
It might just be dead. Maybe a power surge or something. idk.
Well, I finally got it working. It ended up being the battery. When it messed up, it was plugged into my g19 keyboard. This ended up completely draining my battery.
I swapped batteries with my friend to verify this. It than took over an hour to charge my battery to the point of the Orange led comming on.
Hello
I was on purity Rom 5.4.3 and franco kernel for some time now, with no problem at all.
Yesterday before going to sleep I did put the phone to charge, when I woke up i saw that it wasn't charged at all...
after searching in XDA i found the "hack" to lift the usb port with a fine screwdriver, and it helped. the guy said also to afterwards reboot the bootloader, and here started the mess...
after rebooting bootloader and then the system, directly after the bootanimation the screen would go black and the full battery with the flash sign would show. like when charging the device when power is off...
this would happen each time I tried to boot, or to go into recovery. The only stable state was fastboot, but from there on nothing would go.
I tried to go back to stock with GNEX toolkit but it wouldn't recognize the device while in fastboot, and on the screen in the last line was written: fastboot command read error -2147483647
In the meanwhile my device is off but plugged in. It's showing me again the charging symbol with the flash and the full battery, then swithcing to the charging animation for 2 cycles and then back to the full battery with the flash. meaning it's not really charging.
Also when i try to boot now, it's passing the bootanimtion, but while still at the end of the bootanimation, i can feel the phone vibrating before powering off, and i get also the message that i should connect the device to a charger...
Anyone has an idea what to do?
Thank You
Edit: now I somehow managed to boot, had 2% battery left but it wouldn't charge. so i tried to re-bend the usb port inside the phone like before...now the usb plug won't fit anymore, can't manage to get it inside..bended it too much? wrong? I'm getting crazy here
I'm not any kind of electronics technician, but if I was going to guess, I'd say that sounds like some kind of short in the micro USB pin. If that's the case you could take it to a small electronics repair shop and see if it can be repaired or replaced.
Sent from my Galaxy Nexus
Tragically my Note 2 (N7100) has failed me yesterday. I was on my way home with very little battery, with my phone in my pocket. When i plugged it in i noticed it had died and came up with the battery symbol. I tried powering it on with no success and it hasn't worked since. I have tried different cables, USB charging etc. The computer doesn't detect it when plugged in, I can't go into recovery or download mode and all I get is the red sensor light flashing faintly every few seconds when I press and hold the power button.
I've been doing some reading in the past 6 hours and it points to SDS but most people could get in recovery and all. Is this my case? Can I check the emmc version by opening the phone (never had warranty because I was foolish enough to buy this from someone).
I have flashed countless ROMs, never had a problem, never bricked, always fixed any quirks I had but this is a bit beyond me. I was on Omnirom 4.4.2...
DieZz said:
Tragically my Note 2 (N7100) has failed me yesterday. I was on my way home with very little battery, with my phone in my pocket. When i plugged it in i noticed it had died and came up with the battery symbol. I tried powering it on with no success and it hasn't worked since. I have tried different cables, USB charging etc. The computer doesn't detect it when plugged in, I can't go into recovery or download mode and all I get is the red sensor light flashing faintly every few seconds when I press and hold the power button.
I've been doing some reading in the past 6 hours and it points to SDS but most people could get in recovery and all. Is this my case? Can I check the emmc version by opening the phone (never had warranty because I was foolish enough to buy this from someone).
I have flashed countless ROMs, never had a problem, never bricked, always fixed any quirks I had but this is a bit beyond me. I was on Omnirom 4.4.2...
Click to expand...
Click to collapse
IF u cant go to download, recovery mode, and ge the red sensors light flashing, i think its 99% SDS problem.
U should go to the nearest Samsung Centre to confirm and fix it actually
Hello, my galaxy s3 died one day last year and I haven't been able to resurrect it since..inserting battery results in a vibration, samsung logo, then it dies until I pull the battery again. Today I had the sudden urge to try fixing it and got different results than I had previously. I cleaned a bunch of lint from the charging port and am now able to get a short red light flash when the phone is plugged in, followed by a vibration, then the battery charging logo, then death once again. Randomly I'll get the cyanogenmod bootup screen when repeating this cycle but for no longer than a second or two before the phone dies again. I've disassembled the phone and cleaned as much dust and crap as possible to no avail. Any recommendations? Could the power button be frozen? My samsung infuse had a stuck power button and would boot loop but my S3 doesn't seem to be boot looping. Just turning on then dying until I fiddle with the power button again.
I want to rule out sudden death...
I had a sudden death on a note 2.
Download a good compatible (with your baseband) ROM.
Fool with the phone. Like really. Keep trying to turn it on, try recovery mode. I fixed one of these. It wasn't quite the same but I still have it. And it works. If the screen wasn't cracked to hell I'd be on it.
Another option may be trying a debrick image on an external sdcard. You should use one based on the same modem and baseband installed on the phone when it last worked.
I've got a totally unresponsive G3 - it died on me unexpectedly. It had been a little "off" when I was setting it up - telling it to reboot sometimes required a VOLUME UP+DOWN+POWER to actually boot it up, had a tough time getting the LGFlashTool to work and ended up having to use imageprepGUI to achieve root/TWRP, had it trigger the "error: boot certification verify" trouble and had to walk it back with the Qualcomm drivers... anyhow, I finally got it all set up the way I wanted for one of my kids as a Christmas present and just after getting Lucky Patcher up and running (wiped the cache, installed a modded Google Play, etc) I asked my wife to charge it as it was on low power, around 10% or so. She plugged it in and...
Well, my son went to use it hours later and it was dead.
This thing is the deadest I've ever seen a phone. It doesn't respond to having a USB plugged in. I have two other LG G3s and swapped the batteries around - all of the batteries are charged and functional (including the one originally from the dead phone). It's the actual phone that appears dead. The LED doesn't respond to plugging in, there's no vibration on plugging it in, no combo of cables seem to work. Plugging it into a computer doesn't generate any response from my laptop or the phone.
I've brought phones and specifically LG G3s back from the underworld more than once, but this has me stumped. Any ideas? So far, Googling has offered up the following solutions:
1. Remove battery
Hold down power button 10s+ to drain phone entirely
Plug in battery
Allow to charge for 20min
Hold down power button for 10s+
2. Remove battery for extended period
Plug battery in
Turn phone on
I can tell you that method #1 doesn't work here. I'm about to try method #2... but I don't have a lot of hope.
Any other ideas?
I had that probleme 4 days ago, i fixed it by burning the internal memory with a Hair Drayer.
Don't burn the screen, you must burn only the emmc on the motherboard.