Related
If this is asked else were I apologies as I did a search but could not find anything. Short story, my Epic came unplugged before Odin3 finished. Now I cannot get the phone to power on. It will not go into download mode or recovery. I pulled the battery and hit vol. up and power, but nothing happens. I am just about sure there is no hope for the phone, but it is worth a shot. Does anyone know if it is possibly to fix a bricked phone that will not turn on?
Thanks
Will it go into download mode again? do a battery pull and try to go back to download mode. does the samsung logo show when you boot the phone?
I pulled the battery, and still nothing. When I try to power it never comes to life, no logo nothing its like I do not have a battery in it when I hit the power button, but the battery is fully charged.
Art2Fly said:
Will it go into download mode again? do a battery pull and try to go back to download mode. does the samsung logo show when you boot the phone?
Click to expand...
Click to collapse
Download mode: Slide out the kbd, hold the 1 key, press and hold the power button on the side until you get the download screen with the yellow caution triangle and the ditch digger guy...
Holding power and 1 also does nothing.
I think pulling the plug while ODIN is running is literally the only way you can brick this phone, other than running it over with a car.
Did you have full batterywhen you started? Does odin recognize the com port when you plug the phone in?
Sent from my SPH-D700 using XDA Premium App
I did have full batterywhen I did it, but I was using my laptop and went to move causing my phone to fall and become unplugged before it was finished. I just tried plugging in the phone again and nothing came up Odin did not recognize it.
I have had to unplug the phone while odin was running several times because it stopped progressing with the flash. I have been lucky enough to never have a total brick. I would suggest pulling the battery and hitting keys on the keyboard to ensure the power is completely drained, the putting in the battery while holding the 1 key and power.... Always does the trick for me.
You are making sure the phone its in download mode and odin is running before plugging your phone in, right?
Sent from my SPH-D700 using Tapatalk
Oh my; that sucks. I hope you can get it replaced without any issues.
Good luck, with the next one. Tie it to the desk during the Odin process.
You said you pulled the battery then hit Vol. Up and power...
To get into recovery you need to hit Vol. Down + Camera + Power (hope you had a Backup)
Even after pulling the battery it still will not come back to life. I was at the sprint store and told them that I was doing the over the air update and this is what happened. The tech told me that he has seen a few Epics turn into bricks because of the update went wrong. I will have a new one on Monday but it was worth a try to see if there was a fix since the phone they let me use sucks. Now I will be a little scared putting roms on my phone once I get my new one. Thanks for the help anyway.
Jase3040 said:
Now I will be a little scared putting roms on my phone once I get my new one. Thanks for the help anyway.
Click to expand...
Click to collapse
Don't be. What happened to you is next to impossible. If you don't chuck your phone around while Odining, it won't happen again.
k0nane said:
Don't be. What happened to you is next to impossible. If you don't chuck your phone around while Odining, it won't happen again.
Click to expand...
Click to collapse
Yes... ODIN + ADHD is not a good combination
Your phone is not bricked. I had this scenario happen to me. The way I got the phone working again is to take the battery out and then plug the USB cable in. At that point I was able to have the keyboard open, hold down the 1 key+power and the phone went in to dload mode. It worked for me, I am betting it would work for you.
I forgot to mention, leave the battery out of the phone while doing this.
Socos25 I have to say I had hope for this, but I still have the same problem…… however, still nothing but a blank screen that is darker then the bottom of the ocean.
I feel your pain, buddy.
I hate to admit it, but I did the same thing when my phone was 29 days old. In my case I think I started by using the wrong PID file and the process hung. I got worried and unplugged the phone after about 2 minutes. I tried every combination possible to get the phone to wake up but each time it got worse. There was no way to get it back into download mode.
I ended up taking it to a Sprint service center. The tech was sure he could reflash it, but after 20 minutes he came back and said it was dead. Since it was under 30 days they gave me a new phone. Thank you Sprint.
Anyway, I'm pretty nervous these days when using Odin. It IS possible to brick this phone using Odin (as we both know). When I use Odin now I triple check every step, do it on a laptop with a full battery, put the phone down and step away from it until it's finished.
It's likely that if you take it to a Sprint service center they will replace it for a $35 fee. That may be your only option at this point.
Thinking back.. Pull the battery, hold down the power button for like 10 seconds. Then with the battery out of the phone plug in the USB cable. try the 1+power button.
I am pretty sure tha is how I got mine back after I accidently dropped the phone when odin'ing. Does the LED light up when you plug in the usb cable?
I've pulled my phone over 20 times turing an ODIN process to try and brick it. It just doesn't happen with these Samsung phones. You may get stuck at the Samsung screen, but chances are if that you battery is either dead or you keyboard is broken. Cause through 5 phones with trading I can't seem to brick one.
Editing this as I'm desperate for help and things have moved on since I first posted, below is where I am up to post 11 of this thread.
I flashed Vegacomb b (exe), it restarted but stayed on the warning about paying for vegacomb for 10-15 minutes which didn't seem right so I held power for 6 seconds and it turned off. After that it would never turn on or go into recovery (I know all the methods, none worked).
Today I unhooked the battery, when I plug the battery back in the screen comes on for a second but then it's as it was, unresponsive. HOWEVER, if I plug the mains in with the battery disconnected then it immediately tries booting but still sticks at the warning (left for over 20 minutes). If I plug the battery in while on this screen then remove the mains it stays on. The power button is unresponsive through this so I still cannot get into recovery.
Any more ideas that haven't been mentioned?
I've tried well over 100 times to get into recovery but it's not happening
anyone willing to have a go at fixing (cheaply!) if I send them it?
Original Post:
Hi guys, just managed to (re?) install Vegacomb (b, from exe), it restarted but stayed on the white screen with the warning text about paying for Vegacomb for over 10 minutes so I held down the power button to turn it off, now I cannot do anything to boot it up (tried holding power button down from 0.5 seconds to 60 seconds!), it also won't boot into recovery. Is there anything at all that can be done to get this going?
cheers
OK, I've tried holding down back while plugging in (fully charged btw), tried all variations of button presses with back and power, with and without USB, with and without power cable.
Only got until 10PM (UK time) to get this sorted (it's now 6PM) so any help/advise would be appreciated
Flash back to modded stock then try again.
From modded stock go app drawer and run recovery
From recovery wipe data, cache then go advance then wipe dalvik
Then press back
Then install zip from SD
Choose vegacomb from whatever directory on your SD you copied it to then confirm
If you ain't Got Vegacombe zip then download it.
Or you could run the .exe again but the above is my preferred method.
Also you might need to download modded stock v2 if you ain't already got it.
Good luck.
intel007 said:
Flash back to modded stock then try again.
From modded stock go app drawer and run recovery
From recovery wipe data, cache then go advance then wipe dalvik
Then press back
Then install zip from SD
Choose vegacomb then confirm
If you ain't Got Vegacombe zip then download it.
Or you could run the .exe again but the above is my preferred method.
Good luck.
Click to expand...
Click to collapse
??
the Vega won't turn on and won't go into recovery, cannot flash anything, nothing comes up on PC, tried all variations of the back and power buttons (inc back, plug in power & usb, press power, leave 2 seconds and release back) over 100 times. it's like it's dead.
the only thing it does is show a blue LED when I plug the power cable in
I've read that if you got less than 50 or 60% battery it wont go into flash mode (back button 2 seconds - power & back 2 seconds)
Have you got enough battery cause mine takes half a day to charge.
intel007 said:
I've read that if you got less than 50 or 60% battery it wont go into flash mode (back button 2 seconds - power & back 2 seconds)
Have you got enough battery cause mine takes half a day to charge.
Click to expand...
Click to collapse
100% (solid blue LED), been on charge for over 24 hours
I'm baffled mate, I've had same issue couple of times but after 10mins or so I've always got it to power back on.
Bricked
I've had the same problem and although quite drastic, remove the rear cover and unplug the battery connection (the multipin one with red and brown/black wires).
With the mains plug out,i found that if you press volume up and power with the wires unplugged and leav eit for a few mins then use back + power it will start as you need it to.
It may take a few tries but i have managed to do it following this procedure about 7-8 times.
Hope this helps.
DAve
I had trouble getting into recovery when the Vega was 100% charged (i.e. charge led was solid blue). When I let it discharge a little so it was flashing with the charger plugged in, I managed to get into recovery then.
dmarchant said:
I had trouble getting into recovery when the Vega was 100% charged (i.e. charge led was solid blue). When I let it discharge a little so it was flashing with the charger plugged in, I managed to get into recovery then.
Click to expand...
Click to collapse
I can't discharge it though as it doesn't turn on, left it 14 hours from last night, back at work again now and it still says fully charged
got the battery disconnected now to give it a try
Disconnected battery for around 10 minutes, put it all back together, still can't boot or get to recovery
EDIT: it works when the battery is disconnected (goes to the Vegacomb warning screen but no further, cannot power off or get to recovery still)
any ideas?
Anyone got any ideas?
it's meant to be unbrickable from what I've read so there must be a way around it but I'm out of ideas!
its user error. remeber to put it into recovery mode you need the power cable plugged into it too as well as usb.
slybunda said:
its user error. remeber to put it into recovery mode you need the power cable plugged into it too as well as usb.
Click to expand...
Click to collapse
Cheers, but its not user error. I'm not that stupid
Hi, this may not help but i had trouble flashing the stock rom because of the battery being fully charged, could only get the screen to light up so left it over night and then went through the normal routine and got into recovery.
Bill
Hi there
Just one question, how do you know for sure it hasn't gone into nvflash mode?
I know what you are going through trying to get the ruddy thing into nvflash, it's a mare if you don't quite get that timing right but seeing as the screen doesn't light up when it's in nvflash what is telling you whether you are actually in it, other than the screen coming on to say you are not or relying on a windows message?
As I said I had the same problems many a time but I use Audi tool now to tell me if nvflash has started, I got it off the Modaco forum, but when you are in nvflash it actually tells you so rather than relying on perhaps windows to tell you it has happened
If you haven't come across the audi tool before then just do a search for it on Modaco, I don't know if they have got it here on XDA.
mmace said:
Anyone got any ideas?
it's meant to be unbrickable from what I've read so there must be a way around it but I'm out of ideas!
Click to expand...
Click to collapse
wow, i'm quite surprised by the number of people who are taking their batteries out when they think there is a problem. You should never need to do this unless it is actually faulty.
Ok yes the Vega is nearly indestructible I have had my in a complete mess many times and have never had to do anything that hard to recover. Some times it will be a pain to get into nvflash mode but this can always be done just have to be patient and know a couple of tricks.
If you have tried the back button and then the power a few times and nothing there is another method.
Instead unplug the power then hold the back button down, whilst holding down the back button plug in the power release the back button after a couple of seconds (I like to count to 5)
I am hoping that you already have the USB cable connected and the right drivers installed on your PC.
Billy..
If you need more help head over to TabletRoms and look in the Vega forum (sorry XDA guys just there is a lot of other useful information there)
wks said:
Hi, this may not help but i had trouble flashing the stock rom because of the battery being fully charged, could only get the screen to light up so left it over night and then went through the normal routine and got into recovery.
Bill
Click to expand...
Click to collapse
I've tired fully charged and letting the battery drain for 40+ mins after it's been on the "warning" screen
mitt69 said:
Hi there
Just one question, how do you know for sure it hasn't gone into nvflash mode?
I know what you are going through trying to get the ruddy thing into nvflash, it's a mare if you don't quite get that timing right but seeing as the screen doesn't light up when it's in nvflash what is telling you whether you are actually in it, other than the screen coming on to say you are not or relying on a windows message?
As I said I had the same problems many a time but I use Audi tool now to tell me if nvflash has started, I got it off the Modaco forum, but when you are in nvflash it actually tells you so rather than relying on perhaps windows to tell you it has happened
If you haven't come across the audi tool before then just do a search for it on Modaco, I don't know if they have got it here on XDA.
Click to expand...
Click to collapse
I have Audi, I also have Device manager open, I know 100% it's never gone into recovery mode sine I started with this problem.
BillyFish said:
wow, i'm quite surprised by the number of people who are taking their batteries out when they think there is a problem. You should never need to do this unless it is actually faulty.
Ok yes the Vega is nearly indestructible I have had my in a complete mess many times and have never had to do anything that hard to recover. Some times it will be a pain to get into nvflash mode but this can always be done just have to be patient and know a couple of tricks.
If you have tried the back button and then the power a few times and nothing there is another method.
Instead unplug the power then hold the back button down, whilst holding down the back button plug in the power release the back button after a couple of seconds (I like to count to 5)
I am hoping that you already have the USB cable connected and the right drivers installed on your PC.
Billy..
If you need more help head over to TabletRoms and look in the Vega forum (sorry XDA guys just there is a lot of other useful information there)
Click to expand...
Click to collapse
TabletRoms has been no help for me, there's been no reply at all for my problem but there has here and at MoDaCo. I pulled the battery as a last resort as NOTHING is working, I've tried all the tricks at least 2 dozen times, some a hundred +, including the one you mention
Well I don't want to teach you to suck eggs, but I take it you did use Audi to delete and replace your drivers.
And then when powering on the Vega you held the back button for 2 secs and then the back and power buttons for 6 secs to get the Vega detected?
For me I can only see that there can only be 3 other possible causes
1./ the back button is broken on the vega
2./ The USB port on your PC or on the Vega has gone up the swanee
3./ The USB lead is no good
The Vega may be unbrickable but if the back button or the USB port has had it then .....
Yeah, tried it, cheers.
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?
Earlier today, I completely drained my battery and turned it on again. It shut down after this due to the battery being on 0%. I plugged it into the charger and now it's in a boot loop, meaning it shows the "Samsung Galaxy S4" start up, then completely reboots. I can't seem to boot into recovery mode (PhilZ) and whenever I boot into download mode, the phone restarts after a while.
I'm running a CM 11 nightly from April and haven't had any problems. Can anyone help me get my phone going again?
JavierVW14 said:
Earlier today, I completely drained my battery and turned it on again. It shut down after this due to the battery being on 0%. I plugged it into the charger and now it's in a boot loop, meaning it shows the "Samsung Galaxy S4" start up, then completely reboots. I can't seem to boot into recovery mode (PhilZ) and whenever I boot into download mode, the phone restarts after a while.
I'm running a CM 11 nightly from April and haven't had any problems. Can anyone help me get my phone going again?
Click to expand...
Click to collapse
Hi
Check if power button is stuck....
MAX 404 said:
Hi
Check if power button is stuck....
Click to expand...
Click to collapse
I have determined that it is indeed a power button issue, as I can boot into download mode by just using volume down and the home button, but the power button isn't stuck or anything and is still clickable. Any ideas?
JavierVW14 said:
I have determined that it is indeed a power button issue, as I can boot into download mode by just using volume down and the home button, but the power button isn't stuck or anything and is still clickable. Any ideas?
Click to expand...
Click to collapse
Hi ,
you could try to clean it with a contact cleaner ( take battery out first) , do not use to much , watch out for the screen or take it to a service shop and have it replace, should not be too expensive
MAX 404 said:
Hi ,
you could try to clean it with a contact cleaner ( take battery out first) , do not use to much , watch out for the screen or take it to a service shop and have it replace, should not be too expensive
Click to expand...
Click to collapse
I don't really have any of that nearby, will have to take it for repairs. This should teach me to invest in a set of those small screw drivers
JavierVW14 said:
I don't really have any of that nearby, will have to take it for repairs. This should teach me to invest in a set of those small screw drivers
Click to expand...
Click to collapse
I never leave home without them !!
good luck.
Bought the necessary tools today, and I completely removed the button (not the soldered one) and the problem persisted, these are sad days. Samsung store refuses to fix it because of root.
JavierVW14 said:
Bought the necessary tools today, and I completely removed the button (not the soldered one) and the problem persisted, these are sad days. Samsung store refuses to fix it because of root.
Click to expand...
Click to collapse
Hi,
They should it has nothing to do with root ...is a hardware problem
Any way as you open it up try to clean it up with a contact cleaner ( specially made for electronics) or with some 70% solution alcohol , no battery let it dry , do not get soak the display , maybe is just dirt !!
JavierVW14 said:
Earlier today, I completely drained my battery and turned it on again. It shut down after this due to the battery being on 0%. I plugged it into the charger and now it's in a boot loop, meaning it shows the "Samsung Galaxy S4" start up, then completely reboots. I can't seem to boot into recovery mode (PhilZ) and whenever I boot into download mode, the phone restarts after a while.
I'm running a CM 11 nightly from April and haven't had any problems. Can anyone help me get my phone going again?
Click to expand...
Click to collapse
Hi！
Have you checked if the battery touch spots worked well？Maybe it‘s a hardware problem I think.Hope this can help you
745674567e said:
Hi！
Have you checked if the battery touch spots worked well？Maybe it‘s a hardware problem I think.Hope this can help you
Click to expand...
Click to collapse
Thanks to both you and Max for going through the effort of trying to help me out, I've hit that thanks button. I've fixed my problem by draining the battery (this takes forever in a boot loop), put the phone on charge and immediately went into the download mode. I exited the download mode and for some unknown reason it decided to actually work.
I've spent money on a tool kit and tweezers though (around $12 or 10 euros, I believe), but had the privilege of tweaking around on the inside, so that was a learning experience.
JavierVW14 said:
Thanks to both you and Max for going through the effort of trying to help me out, I've hit that thanks button. I've fixed my problem by draining the battery (this takes forever in a boot loop), put the phone on charge and immediately went into the download mode. I exited the download mode and for some unknown reason it decided to actually work.
I've spent money on a tool kit and tweezers though (around $12 or 10 euros, I believe), but had the privilege of tweaking around on the inside, so that was a learning experience.
Click to expand...
Click to collapse
That is the attitude mate !!
Any time
--- This may belong in the Xposed forum, I am uncertain. ---
Hello. Please forgive my ignorance regarding the technical aspects of methods discussed on these forums.
I have a Samsung Galaxy S4 GT-I9505 supplied by Vodafone Australia. This was received today as a replacement for a screen issue I had with my previous S4. On the previous S4, I had rooted using a Saferoot method as read about on this forum. Later I had installed Xposed to use Keepchat and everything was fine. Today I have rooted this replacement phone successfully using the same method, and then moved to install Xposed. The Xposed application required an update, the very first option in the app was red and suggested an update or a reboot, and the reboot did nothing, so I pressed update. The phone turned off but didn't restart. I tried the usual button presses and battery pulls and finally a simple power up using the standard power button started the phone up. It got as far as the lock screen I believe, before shutting down again. It is now unresponsive. It wont turn on, enter the boot menu (multi button holding method) or charge. I believe the battery is quite low at this point, and unable to charge, causing me some consternation. It has now been over 30 minutes with no response.
If anyone could provide a resolution to this issue, I would be extremely thankful.
Regards,
CaleS
Try and ask in this forum my friend good luck
http://forum.xda-developers.com/showthread.php?t=2265477
Hello again.
I have an update on my situation.
I left the phone on charge and it eventually turned on by itself. I played around with it for a while and it seemed OK. Eventually it turned off again. I had to pull the battery to get it to turn back on. After starting up again, getting to the lockscreen, it turned off again. This process repeated many times, until I got frustrated.
The next day I thought I'd try a factory reset via volume up + power, and the device managed to stay on long enough for this to complete. After the phone reset, I used it for a while and again it turned off. The same cycle continued.
Perhaps the phone is naturally faulty, despite my rooting attempt, as it was a refurbished model. I am quite happy to return it for another replacement under warranty, however I may not be able to do it as the device is rooted. I would gladly remove the root using stock firmware and Odin, however the phone resets after a few seconds of entering download mode.
Any advice?
Thanks.
Sounds to me you have a faulty power button. It's somehow stuck that's why it even reboots in download mode. It's a common problem for the S4. Try to wedge it or replace it.
if it is refurbished model it might as well be dead battery.
battery sensor detects "low battery" state and shutdown phone saying battery 0% - to protect battery against fully depleted state (damaging to max capacity or even impossible to charge at some point)
if you power it on again it will boot and say it has like 1% left and you will be able to use it for few more moments, but doing so will degrade your battery.
powering it on, going to lock screen for it to shutdown on its own again sounds like weak power source
imagine above scenario happening several times (previous owner of the phone kept "reviving" it after shutdown due to battery 0%)
that would resulted in battery able to hold only fraction of its standard power - allowing you to just boot your phone before it shuts down.
I had similar situation with my laptop battery (this one was on AC all the time) - battery was so damaged that laptop was shutting down at windows login screen - if booted on battery alone.
When booted on AC and unplugged it said 100% battery, that went down to 0% in a matter of around 2 minutes, when laptop shuts down.