Related
I tried to load up the new gingerbread roms from my current one. I downloaded its content and tried to install it via clockwork.
I first deleted system, logo, and cache followed up by a restore format. When trying to download the new rom, I was getting a weird error that was stopping me from completing the full installation. So basically was in a chokehold because I didn't have any backup files or another working rom in the sd at that time. I just restarted the phone and it for a few times was stuck on the M screen, but now its just green led when I plug it into the computer usb. When plugging it into the outlet, it imediately turns on stuck on the M screen and shuts off when unplugging as if the battery isnt charging at all.
Sounds like ur going to have to sbf.
Sent from my DROIDX using XDA App
bigshotrob22 said:
Sounds like ur going to have to sbf.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
thats the problem.. i got the X.340 sbf and the program aswell but I cant get into bootloader mode. is there an alternative way to sbf?
Did u pull the battery for 30 seconds and then hold the volume buttons + power to put it n bootloader
Sent from my DROIDX using XDA App
Could be your battery same thing happened to me try using a friends battery your battery could be dead and it no longer charges
Sent from my DROIDX using XDA App
bigshotrob22 said:
Did u pull the battery for 30 seconds and then hold the volume buttons + power to put it n bootloader
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
bootloader is such a rare occurance for me, i just had it come out but it was flashing low battery. the thing is, im not quite sure if its charging if i have it plugged into the computer. when i have it plugged into an outlet, the M splash screen comes up so i'm worried that draining the power..
edit: now it flickers for a split second, am i supposed to hold on to it til something shows up? been like 1 minute
i dont think bricking phone blows your battery. at least i hope it doesnt, was working fine before.
Plug it in without the battery if a question mark comes up you ned to use another battery cuz it won't charge in boot loader and the boot loader should pop up right away hold power volume down and camera button it takes about three seconds
swyped from my DROIDX using XDA App
well its basically the same thing. when plug into the outlet it shows the m splash screen with or without the battery.
when its plugged into the compuiter however, its just flickers once. when it is done with the battery in, the led is on forever
EDIT: OBSERVATION
when on the wall, it is actually charging, but REALLY slowly because of the fact that the splash screen stays on. found this out because i had it in for30 min and then tried to connect mit to my comp with bootload and it loaded for a few minutes with the low battery flashing.
is version 320 the latest?
Okay. so it isnt charging as I though because its not working at all... problem is, I dont know if it truly is a battery defect. If I were to Buy a new battery, how would i know if it is charging if it doesnt boot and just stays stuck on the M logo screen?
perhaps I should by a battery charger where i take the battery out and charge it through there? because my bootloader always gives me the same low battery.
Do you have any friends with the same phone? There is also a macgyver (spelling?) Method of doing this by cutting the USB cable open and attaching the cable ends to the battery. However I would only do this if you're really desperate
i just really need make complete sure that this phone is INFACT dead battery
when not plug, it doesnt turn on what so ever with a white spark on the led.
when plugged nto outlet the logo shows but i isnt charging because it isnt booting
when plugged into the computer it is a solid green which i think represent a dead or a low battery state(can someone back thisup?)
Your battery is dead, as in drained, but should work fine once you get your phone to a bootable state again. The problem is that, in the state your phone is in, there's no charging capabilities. Bootloader won't do it, neither will sitting at the M logo. So, you just need to find someone with a compatible battery to let you use it to SBF your phone. Then, boot the phone up completely, and let your battery charge to at least 50-60% before trying to install a ROM. Preferably, I'd go with a full charge, just in case you end up in a similar situation again.
This is nothing to freak out over, you'll be fine.. the only problem you have is that your battery has no juice, as confirmed by the low battery warning in the bootloader, when you successfully got it to load.
raziel36 said:
Your battery is dead, as in drained, but should work fine once you get your phone to a bootable state again. The problem is that, in the state your phone is in, there's no charging capabilities. Bootloader won't do it, neither will sitting at the M logo. So, you just need to find someone with a compatible battery to let you use it to SBF your phone. Then, boot the phone up completely, and let your battery charge to at least 50-60% before trying to install a ROM. Preferably, I'd go with a full charge, just in case you end up in a similar situation again.
This is nothing to freak out over, you'll be fine.. the only problem you have is that your battery has no juice, as confirmed by the low battery warning in the bootloader, when you successfully got it to load.
Click to expand...
Click to collapse
thanks for the reassuring comment, however, i think i need to bootload.
i accidently did the partition hat formats everything.. cant recall if it was under clockwork because it didnt have the same interface, i was all light blue text with an ok button on the left corner. Anyway, i've completely destroyed the phone as in no roms no factory.
can I possibly get a dock to charge this battery and then get into bootloader for an sbf session
? Even if I did have battery, im pretty sure i just hover at the logo screen
jinho11050 said:
thanks for the reassuring comment, however, i think i need to bootload.
i accidently did the partition hat formats everything.. cant recall if it was under clockwork because it didnt have the same interface, i was all light blue text with an ok button on the left corner. Anyway, i've completely destroyed the phone as in no roms no factory.
can I possibly get a dock to charge this battery and then get into bootloader for an sbf session
? Even if I did have battery, im pretty sure i just hover at the logo screen
Click to expand...
Click to collapse
There's a usb trick u can try. Google it.
Sent from my DROIDX using XDA App
jinho11050 said:
thanks for the reassuring comment, however, i think i need to bootload.
i accidently did the partition hat formats everything.. cant recall if it was under clockwork because it didnt have the same interface, i was all light blue text with an ok button on the left corner. Anyway, i've completely destroyed the phone as in no roms no factory.
can I possibly get a dock to charge this battery and then get into bootloader for an sbf session
? Even if I did have battery, im pretty sure i just hover at the logo screen
Click to expand...
Click to collapse
You definitely need to use the bootloader, and I was implying that in the first reply(SBF'ing requires going into the bootloader). If you had a stand-alone battery charging cradle/dock, that should do the trick. Just make sure to let the battery charge sufficiently. I've successfully gotten an SBF completed, starting with only 30% battery. SBF takes about 7 minutes on my laptop(not that I've timed it, but I usually light up a smoke when I start the process lol). So, as long as the battery is charged enough to no longer give the "Low Battery" warning in the bootloader, you should be fine.
You got your usb cable and put the ends where the battery goes that's how I got mine working try it
Sent from my DROIDX using XDA App
froyli said:
You got your usb cable and put the ends where the battery goes that's how I got mine working try it
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
al the tips or just red for pos and black for neg
Positive and negative google it before you do it
Sent from my DROIDX using XDA App
okay im having another issue with bootloader.. the program detecs it but i canot start the process.. am i missing something?
EDIT: finally got sbf working after renaming it.
All my threads have been in a form of technique difficulty question and the answer I get from the community were VERY helpful. thank you everyone
jinho11050 said:
okay im having another issue with bootloader.. the program detecs it but i canot start the process.. am i missing something?
EDIT: finally got sbf working after renaming it.
All my threads have been in a form of technique difficulty question and the answer I get from the community were VERY helpful. thank you everyone
Click to expand...
Click to collapse
Glad you got it working! Nearly everyone on here has needed help, at one point or another, and that's what makes Android so great... the community.
Sent from my DROIDX using XDA App
Just got my nexus 4, and after it was left in cwm for about 10 minutes (while I was making breakfast) it went to a black screen and now just the red led notification led is flashing whenever plugged in, and on my mac in system profiler it shows "composite device", any suggestions?
Thanks!
nycbjr said:
Just got my nexus 4, and after it was left in cwm for about 10 minutes (while I was making breakfast) it went to a black screen and now just the red led notification led is flashing whenever plugged in, and on my mac in system profiler it shows "composite device", any suggestions?
Thanks!
Click to expand...
Click to collapse
Is your device hot to the touch?
Sent from my Nexus 4 using xda premium
20 second press on power button
No luck
Sent from my HTC One X using xda premium
Don't know if you want to do this, but you can open the phone and disconnect and reconnect the battery connector...
What was your battery level, I know in other devices some times the CPU(s) run at full speed in recovery allowing for quicker flashing this could discharge the battery rapidly. Also a flashing red LED when plugged in normally means the phone is charging but doesn't have enough charge to reliably turn on, leave it plugged in for about 15 minutes and try turning it on again.
Try holding down the VOL + and - keys along with the powerbutton (after turning it off by holding down the power button for an extended time) and see if you can get into fastboot. My friend's Nexus 4 kept bootlooping after he unlocked the bootloader but booted straight to CWM after, not letting it erase userdata first.
Net.silb said:
Don't know if you want to do this, but you can open the phone and disconnect and reconnect the battery connector...
Click to expand...
Click to collapse
I have no problem doing this, the phone seems easy to disassemble, looks alot like a overgrown iPhone 4, 2 screws on the bottom. I just hope its an easy slide, I don;t want to mar it in case I have to exchange it.
jakejm79 said:
What was your battery level, I know in other devices some times the CPU(s) run at full speed in recovery allowing for quicker flashing this could discharge the battery rapidly. Also a flashing red LED when plugged in normally means the phone is charging but doesn't have enough charge to reliably turn on, leave it plugged in for about 15 minutes and try turning it on again.
Click to expand...
Click to collapse
I thought this as well, its been plugged in for at least an hour now.
Oh and now I don't even get the red led!
good times..
I've got the exact same issue. Plugged it in last night to charge and this morning it wouldn't turn on. Plugged and unplugged it and the red LED starts flashing. After a minute or so I'm getting the battery charge animation on the screen - so the red LED is power related. Now to see if it actually charges up and boots.
Hi nycbjr. I have seen a similar issue posted here, but I can't find the thread at the moment, try searching. If I remember correctly then he got it working by holding power, volume keys and then plugging in the charger.
nycbjr said:
I have no problem doing this, the phone seems easy to disassemble, looks alot like a overgrown iPhone 4, 2 screws on the bottom. I just hope its an easy slide, I don;t want to mar it in case I have to exchange it.
I thought this as well, its been plugged in for at least an hour now.
Oh and now I don't even get the red led!
good times..
Click to expand...
Click to collapse
Try a different charger?
Unlucky
Get a Free £5 On a GiffGaff sim
Called google, they are sending me another one advanced replacement, so I can send the bad one back at me leisure.
Good customer service!
Qhsusb_dload
nycbjr said:
Called google, they are sending me another one advanced replacement, so I can send the bad one back at me leisure.
Good customer service!
Click to expand...
Click to collapse
Hi!! I have the exact same problem, unfortunately the phone is bricked! Does anyone know how to fix this? I saw a video on youtube Nexus 4 - JTAG Brick Repair Service
CalogeroIndorato said:
Hi!! I have the exact same problem, unfortunately the phone is bricked! Does anyone know how to fix this? I saw a video on youtube Nexus 4 - JTAG Brick Repair Service
Click to expand...
Click to collapse
If u are fully bricked JTAG is the way to go.
Sent from my Nexus 4 using Xparent BlueTapatalk 2
Here seems to be a similar thread, maybe you'll find help there.
http://forum.xda-developers.com/showthread.php?t=2111947
I thought I'd clean up the OP for folks who got here with similar issues as me since it seems more common than we'd like.
Scenario:
Phone does not turn on without the charger or USB plugged in.
When plugged in, it boot loops at the Google logo (i.e. turns off at the logo, and reboots) and gives what is beginning to be referred to as the the 'red LED of death'--where the LED just blinks read.
The bootloader is accessible when plugged in. But trying to boot into recovery causes a loop. If you try to enter recovery, the phone has to turn off then boot back into recovery. But turning off means that when it turns on it will loop at the Google logo. So, booting into recovery is NOT an option.
Download mode is also accessible when plugged in.
Since the bootloader is accessible, it is possible to flash the factory image to the phone, however, doing so does not resolve the boot loop, nor does it allow the phone to turn on without being plugged in.
Fixes which have worked for some people
Instructions in this post worked for a couple people. NOTE: you have to be able to get into the bootloader for this to work.
One person who left it in download mode plugged into the PC (which was off) overnight, and somehow the problem was resolved. Thread here.
Here's a post in this thread from a user who was able to get it booting up again by leaving it on the charger for a bit.
You fool.
abnormalreply said:
In sum: I started using the Faux kernel with AOKP. OC'd to 1.6Ghz and started Antutu. Phone crashed and now it doesn't boot. When I plug in the charger, there's the battery icon with the lighting bolt which I think indicates that the battery is dead. But it's not dead, it was around 95% when I started Antutu. So, it's constantly turning on and off showing that battery icon while plugged in, but doesn't start up. Anything I can do about this?
Also, the computer only detects it briefly, before the phone turns off again, so ADB/fastboot/toolkit seems out of the question, because it doesn't stay detected long enough to do anything.
Click to expand...
Click to collapse
Tape the power button down so it goes into a power cycle. Leave it until the battery is totally dead. Then plug it into the wall outlet, let it fully charge. Then try turning it on.
Sent from my Nexus 4 using xda premium
Your computer only detects it briefly? perhaps it'll detect it if you boot into Bootloader mode (not sure if you were able to from reading the OP)
Press and hold volume down, volume up, and power until the device boots. If you successfully enter Bootloader mode you can find steps on how to return to stock here: http://forum.xda-developers.com/showthread.php?t=2010312
overhauling said:
Your computer only detects it briefly? perhaps it'll detect it if you boot into Bootloader mode (not sure if you were able to from reading the OP)
Press and hold volume down, volume up, and power until the device boots. If you successfully enter Bootloader mode you can find steps on how to return to stock here: [/QUOTE]
Yeah, it would be nice if...en if I get into the bootloader for a second.
Click to expand...
Click to collapse
abnormalreply said:
In sum: I started using the Faux kernel with AOKP. OC'd to 1.6Ghz and started Antutu. Phone crashed and now it doesn't boot. When I plug in the charger, there's the battery icon with the lighting bolt which I think indicates that the battery is dead. But it's not dead, it was around 95% when I started Antutu. So, it's constantly turning on and off showing that battery icon while plugged in, but doesn't start up. Anything I can do about this?
Also, the computer only detects it briefly, before the phone turns off again, so ADB/fastboot/toolkit seems out of the question, because it doesn't stay detected long enough to do anything.
Click to expand...
Click to collapse
i am on the same boat. i already contacted CSR anh they will send me a new one. after flash new kernel and start antutu, the n4 crashed and completely dead.
I'm pretty sure the battery with the lightning bolt means its charging.
Sent from my Nexus 4 using Tapatalk 2
ntt1409 said:
i am on the same boat. i already contacted CSR anh they will send me a new one. after flash new kernel and start antutu, the n4 crashed and completely dead.
Click to expand...
Click to collapse
Omg.. you don't need a replacement. Stop trying to load roms and kernals if you do not know how.
sent via xda premium with nexus 7
Ulver said:
I'm pretty sure the battery with the lightning bolt means its charging.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, but it's already full charged. Even if I leave it on the charger for a while, it still doesn't start up
KonstantinKeller said:
Tape the power button down so it goes into a power cycle. Leave it until the battery is totally dead. Then plug it into the wall outlet, let it fully charge. Then try turning it on.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I would say try this to drain the battery. Then charge it and see what happens.
So how exactly did the phone brick? Just so everyone here knows what not to do. Is it the kernel that caused it since its still in experimental stages?
Sent from my Nexus 4 using xda premium
abnormalreply said:
In sum: I started using the Faux kernel with AOKP. OC'd to 1.6Ghz and started Antutu. Phone crashed and now it doesn't boot. When I plug in the charger, there's the battery icon with the lighting bolt which I think indicates that the battery is dead. But it's not dead, it was around 95% when I started Antutu. So, it's constantly turning on and off showing that battery icon while plugged in, but doesn't start up. Anything I can do about this?
Also, the computer only detects it briefly, before the phone turns off again, so ADB/fastboot/toolkit seems out of the question, because it doesn't stay detected long enough to do anything.
Click to expand...
Click to collapse
Have you tried reflashibg or using your nan droid back up from the recovery console?
Just because our won't not does not mean it is bricked.
It is really ticking me of that many people do not even have our phones and you are exchanging because of ignorance. Surely all these exchanges must impact stock. I know they keep extras but how many?
Stop messing with things you know nothing about until you at least learn..
sent via xda premium with nexus 7
abnormalreply said:
Yeah, it would be nice if I could get into the bootloader :/
But as I mentioned, it 'thinks' the battery is dead so it just keeps turning on and off even if I get into the bootloader for a second.
Click to expand...
Click to collapse
That's the point. It'll turn on and off until the battery is ACTUALLY dead. Then, charge it fully, and try to start it.
Dude this happened to me last night! Same ROM kernel combo! And fired up an tutu after ocing point is this should not be happening just made a thread and seen this here! Freaky! I'm telling u people beware something is up for sure been doing this a long time never seen this before
First if you have an unlocked bootloader, your replacement won't be free. As soon as Google gets it and realizes it's unlocked they will charge you full price for your replacement.
Second, Nexus devices are next to impossible to brick. There is probably a way to reset the device. I would try first unplug the device from your computer or charger and try holding the power button for a full 15-20 seconds. Then try booting into bootloader or recovery. If that doesn't work, try holding volume up and power for 15-20 seconds. If that doesn't work, try volume down and power for 15-20 seconds. And if that one doesn't work try holding all 3 down for 15-20 seconds. This sounds like a problem that would more than likely be fixed by removing the battery and rebooting. Since this doesn't have a removable battery there has to be a built in 'hard reset' that will power cycle the phone.
I am willing to bet there is a way to get this working. I guarantee if I had it here in front of me I could.
Also, like someone else has said before, if you are a not good at diagnosing problems, troubleshooting problems, fixing this kind of stuff on your own and adb/fastboot, it makes no sense to be using experimental software on your device. Especially if you plan on pushing its boundaries by overclocking and running benchmark software. If I were you, after you get this straightened out, wait a while until stuff is more ppolished and tested better.
So, by sheer luck, I was able to get into the bootloader and have it stay on. I was then able to use the toolkit (option 9) to flash the google factory stock image. This completed successfully, and I was also able to re-lock the bootloader, but I still have the same problem as I did before: battery charging icon and constant reboot. So, it's completely stock now and the issue is still there. Would it be reasonable to assume that the issue isn't software and I somehow got a hardware failure?
Yo hold power down then plug USB in then right after hold all three button .like after u plus in USB while holding power button then at same time hold volume buttons also this is how I got into download mode.....but.....phone was not detected and comp SD there was a driver failure. But yes dude phone was charged. And I had same exact combo as u I mean same exact. This is why it is freaky. Aokp was fine all day then when I flashed faux test kernel and fired up antutu I just had a flash then nothing. Not blaming anyone of course it was me who chose to flash after all this is custom software and I love these guys work just wish I knew what did it ....like what actually did it
Richieboy67 said:
Omg.. you don't need a replacement. Stop trying to load roms and kernals if you do not know how.
sent via xda premium with nexus 7
Click to expand...
Click to collapse
Seriously... thousands of people waiting for the phone to become available, and people who deserve to have their phone bricked are getting 2nds for free.
abnormalreply said:
So, by sheer luck, I was able to get into the bootloader and have it stay on. I was then able to use the toolkit (option 9) to flash the google factory stock image. This completed successfully, and I was also able to re-lock the bootloader, but I still have the same problem as I did before: battery charging icon and constant reboot. So, it's completely stock now and the issue is still there. Would it be reasonable to assume that the issue isn't software and I somehow got a hardware failure?
Click to expand...
Click to collapse
I was able to do the same thing but it would vibrate then see Google for a sec then nothing and back to a blinking red light....dude this is crazy I can't. Believe this happened to another person the same exact way
dammit. And I was just going to try this combo. Guess that's gonna be a no go.
Last ditch effort is to unscrew the two t5 screws at the bottom and do a real battery pull. Probably wont work, but what do you have to lose?
So this is my first post because I can normally find what I'm looking for, except for in this case.
First off my phone, Galaxy S4 Model SGH-I337 running Android 4.2.2 rooted. No custom rom installed, i.e. Cyanogenmod. I recently bought some new batteries and a new charger which I had been using for about two weeks before my problem arose.
I came home one night plugged my phone in to charge and woke up to find it unresponsive. I tried a battery pull and found my phone turns on for about 3 seconds showing the samsung custom screen with the padlock only to shut off again. Same thing happens not matter how many times I perform a battery pull. I tried plugging into my computer but the phone is not detected.
I tried a battery pull and booting into safe mode and debugging mode but the phone just shuts off after 3 seconds no matter what.
I'm not sure if this is a true hard brick since when I perform a battery pull the phone starts and the buttons seem to work, at least enough to enter safe or debugging mode.
I have not seen any threads where the phone momentarily turns on after battery pull only to shut off quickly.
Has anyone run into this problem before and is there anyway to fix it???
billbusby said:
So this is my first post because I can normally find what I'm looking for, except for in this case.
First off my phone, Galaxy S4 Model SGH-I337 running Android 4.2.2 rooted. No custom rom installed, i.e. Cyanogenmod. I recently bought some new batteries and a new charger which I had been using for about two weeks before my problem arose.
I came home one night plugged my phone in to charge and woke up to find it unresponsive. I tried a battery pull and found my phone turns on for about 3 seconds showing the samsung custom screen with the padlock only to shut off again. Same thing happens not matter how many times I perform a battery pull. I tried plugging into my computer but the phone is not detected.
I tried a battery pull and booting into safe mode and debugging mode but the phone just shuts off after 3 seconds no matter what.
I'm not sure if this is a true hard brick since when I perform a battery pull the phone starts and the buttons seem to work, at least enough to enter safe or debugging mode.
I have not seen any threads where the phone momentarily turns on after battery pull only to shut off quickly.
Has anyone run into this problem before and is there anyway to fix it???
Click to expand...
Click to collapse
The phone didn't brick itself. So, if you didn't do anything to it and just found it that way (as you said), I would think it is a hardware problem either with the phone or the battery. Have you tried a different battery? If you rule out a defective battery, I would say it is a hardware problem with the phone.
This used to happen to skyrockets due to stuck power button
Sent from my SGH-I337 using Tapatalk
RK said:
This used to happen to skyrockets due to stuck power button
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
This right here ^
My friend has a T-Mobile GS4 and same thing happened to him. It would only turn on when he would pull the battery and put it back in, but it would turn off soon after. Turns out his power button was jammed. He went and go it replaced.
Try this: Pull your battery and put it back in. If your phone turns on momentarily without you pressing anything then the power button is the problem.
Are you able to enter download mode..or recovery?
Sent from my GT-I9500 using Tapatalk
mrao said:
Are you able to enter download mode..or recovery?
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
No i can't enter either because the phone shuts off after 3 seconds no matter what I do
PurpleBottle said:
This right here ^
My friend has a T-Mobile GS4 and same thing happened to him. It would only turn on when he would pull the battery and put it back in, but it would turn off soon after. Turns out his power button was jammed. He went and go it replaced.
Try this: Pull your battery and put it back in. If your phone turns on momentarily without you pressing anything then the power button is the problem.
Click to expand...
Click to collapse
Is there any way I can take the phone apart and fix this? I don't think returning the phone is an option since my phone is rooted.
billbusby said:
Is there any way I can take the phone apart and fix this? I don't think returning the phone is an option since my phone is rooted.
Click to expand...
Click to collapse
Your exact problem just happened to me. Were you able to fix it? I'm dying to know!
billbusby said:
Is there any way I can take the phone apart and fix this? I don't think returning the phone is an option since my phone is rooted.
Click to expand...
Click to collapse
There's disassembly guides/videos if you want to try, you could search that and just take a look at the mechanism.
Sent from my SGH-I337 running Light ROM
in my face, my phone turned off on me.
im on mf9
rooted.
samsung logo comes up for a second, then disappears.
download mode appears for a second, then disappears.
battery icon appears for a second, then disappears.
ran through a bunch of threads here, even looked at other phones with similar problems.
been at this since the morning, its now 4:30.
looking for some help.
phone does not stay on, and does not go into download mode.
was working PERFECTLY the day before.
Thanks
BreakTheLaw said:
in my face, my phone turned off on me.
im on mf9
rooted.
samsung logo comes up for a second, then disappears.
download mode appears for a second, then disappears.
battery icon appears for a second, then disappears.
ran through a bunch of threads here, even looked at other phones with similar problems.
been at this since the morning, its now 4:30.
looking for some help.
phone does not stay on, and does not go into download mode.
was working PERFECTLY the day before.
Thanks
Click to expand...
Click to collapse
Sounds like a hardware issue almost.
I would maybe try connecting the phone via USB to pc. Pull battery and and replace. Then try booting into download mode. Open Odin and check if the device is recognized.
Sent from my SPH-L720 using Tapatalk
doesnt sound like a brick... truth being, its almost rare " hard bricking " samsung galaxys.. soft bricking is very common.. i bricked a HTC EVO a few years ago... symptoms: press power.. blue light blinks and the shuts off.... pop out batt, plug in, usb to pc....all do nothing....
sounds like somehow there is a batt problem.... TAKE OUT BATT... LAY it on a super flat serface.. now try and spin it!!! or does it rock around like its uneven?... means the batt is swollen in the middle and is no good... that maybe ur prob.
Sent from my SPH-L720 using xda app-developers app
chris-allen said:
doesnt sound like a brick... truth being, its almost rare " hard bricking " samsung galaxys.. soft bricking is very common.. i bricked a HTC EVO a few years ago... symptoms: press power.. blue light blinks and the shuts off.... pop out batt, plug in, usb to pc....all do nothing....
sounds like somehow there is a batt problem.... TAKE OUT BATT... LAY it on a super flat serface.. now try and spin it!!! or does it rock around like its uneven?... means the batt is swollen in the middle and is no good... that maybe ur prob.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
thanks.
battery spins like a turntable.
both my batteries spin like a stripper actually.....
i have used 3 different computers, countless usb cables and ports.
i used my friends battery to make sure it wasnt my batteries, phone still doing the same thing.
its so odd.
it was working perfectly fine.
now when i put the battery in, it automatically turns on, but only for a split second.
then it turns off.
i know its not suppose to turn on automatically, but i cant even get it into download mode because it shuts off within seconds.
im at a loss
Well.. if you have insurance, call them and tell them the device just stopped working... they will fedex you another overnight.. all for a 100.00 deductable....thats a way out.
Sent from my SPH-L720 using xda app-developers app
I have seen similar stories from people that had defective power buttons. what if you hold the vol down button when you insert the battery, does it behave differently?