I need some help and stump and any resolution. I don't have a clue on what going on. This started today.
Basically, what is happening the phone is rebooting after successfully booting into OS ('m getting to my homescreen). The reboots will occur anywhere from five seconds to five minutes. Also, the phone connect's to Sprint service, but only not very long. I see the LTE indicator than nothing.
I've tried reflashing roms that were working over the last few days, which are CM11 nightlies for 8/6, 8/5, 8/4. I also flashed classic NE2, which was workig last week.
I'm not sure what happened, but I was on CM11 nightly for Aug 6, 2014 with Plasma Kernel 2.53. CPU set at 2.0, governor Performance. I set the charge input to 2.0 amps. Anyway, I was in the car, listening to SiriusXM on a Mini Jamebox. The phone froze. This had been occuring when driving the phone would freeze since I had it happen while on the road with MLB at Bat, and NFL Game Pass; i just assumed it had to deal with something when the phone was switching from 4G to 3G or vice versa. I didn't think anything about it. When I got to my destination, pulled the batter, rebooted phone. Fired up the SIriusXM app, phone rebooted; this has happened before, but not all the time. Now, the phone is booting, but before I could finish entering the lock screen PIN, phone rebooted, and keep rebooting.
I then did a full wiped as if going to install a new rom (factory resent in recovery) and reflashing CM11 8/6, but now it's in a boot loop at the CM logo screen. Same thing again, but flashed CM11 8/5, same thing. Tried it again, but left the phone, and after about three or four hours, phone was still on the CM logo. I then tried a factory reset but flashed the ME Classic. Had a lot of boot loops at Samsung and Android splash screens, Tried it again, but this time I got to the homepage, but no cell service. Tried it again, same result. Then I tried a reset and flashed CM 8/6 with GAPPS, no Plasma Kernel. Phone booted. But no reboots within about five minutes. Also, only connects to sprint briefly. I see LTE, then disappears.
The phone is charging, since at one point, it was down to 4%, but charged to 86% while I was napping.
I'm not sure what's going on since the problems seems to consistent on both TW and CM.
THe only thing I didn't try was doing a full restore, which I think puts the phone back to 4.1.2, and then rerooting or taking the OTA and rerooting.
Update 1
Well, I've been able to flash both TW Classic NE2 rom and CM11 8-6-14 roms and maintain sprint connection and no reboots. I didn't test the TW NE that much, because I flashed CM11. I would start setting up the rom with the apps I like, and how I like the phone setup. When I go to reboot, it ends up in boot loop around the Samsung splash screen, and thus not going pass bios.
I've been having trouble flashing the roms though. I'm using Philz Touch 6 ver 6.48.6 as recovery. I do full data/factory wipe (usually two or three times). Then try installing a rom. It starts installing, goes about an sixteenth of the process bar and then the phone reboots; and usually sticks on the Samsung Logo screen.
On a side note, I tried rebooting the phone after a factor reset, expecting some kind of message about no OS installed or booting back into recovery. Unfortunately, it just sticks on the Samsung Logo screen, except one time where it went back to recovery.
I don't have a clue what's going on with the phone.
Try using philz 6.07.9
Sent from my GT-N7105 using XDA Premium 4 mobile app
jlmancuso said:
Try using philz 6.07.9
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the replay. I actually was using that version before that. I was updated to the latest version because the phone was rebooting while trying to flash roms.
I tried changing the recovery to TWRP 2.7.1.0, but unfortunately the phone rebooted when it started flashing, so I don't think it finished flashing. I end up in boot loop at the Samsung Logo screen.
So, I odin NE2 Stock Restore tarball. It fixed the boot loop issue because it put in a working boot image. Unfortunately, no connection to Sprint. It's also rebooting too. I tried re-odining the firmware, but same result.
I'm downloading the official firmware from Samsung and going to try odining it. It's going to take about an hour to download. I may try using Odin 3.07 instead of 1.85
I'm just not sure what's going on. I'm thinking something with the hardware may have been damaged since, but not sure exactly how. The phone never got that hot. It got warm because of the display being on. The battery still holds a charge that lasts a while, but nowhere near like when it was new.
update 3:
I tried Odin 3.07 and the firmware from Samsung; this ended up being the same file as the NE2 stock recovery. No change.
The phone is doing some different behavior; don't know if new, but I'm noticing now nonetheless. I'm able to Odin the firmware. While still connected to the PC, the phone boots up. But will reboot within five minutes, usually within three minutes. If the phone is not connected the PC via USB cable, the phone will boot loop around the Samsung Logo. The battery currently has a 83% charge. If I connect the USB cable from the PC to the phone, it'll boot up. Still does the reboot later. Sometimes the phone doesn't reboot; it just shuts off and then shows battery charge display. If I have the USB connected, boot into phone, and then disconnect the USB cable, the phone immediately reboots. This also occurs if I disconnect on the Samsung Splash screen after the bios boot.
May be worth noting, the phone right now is completely stock on TW 4.4.2, non-rooted.
Update 4:
Not much more information. I'm still having the issue with the phone doing the boot loop with only battery power. I tried connecting the phone to the phone charger, and it stays on. If I pull the USB cord out, phone immediate reboots and goes into a boot loop.
I connected the phone to the home internet, and I'm I do have some Sprint service for phone. No data connect access.
I'm still using the firmware from Samsung, so completely stock with knox and unrooted.
I also tried the http://forum.xda-developers.com/showthread.php?t=2591898, but did not work. Got a fail, and check failed on the phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Update 5:
I hooked the phone up the wall(AC) charger. The booted and stayed on for over two hours with no reboots. I had connection to the Sprint cell service, but no data connection.
I think I may have a bad battery since when I disconnected the phone from the charger, it immediately rebooted and went into boot loop. I'm not sure if I had a new battery if I will still get the reboot. I think the no data connect can be fixed. I have flashed roms after the initial issue and was able to get data connection.
spoke too soon. Overall, if plugged into a wall charger, the phone stays on with no reboots. But earlier today, I did have a some reboots after turning it on and it froze a couple times.
I'm not sure, but I'm thinking maybe the phone is going, or already is, going bad. I'm not sure how to check to confirm.
I was able to check to see how if the phone works off an external battery. I didn't work with a Durcell MyGrid. I thini it's has a 3.2A capacity and outputs 5V.500mha.
I tried with an Ander that has 10A compacity. I don't recall the output, but it has a swithc for 5V and 12V, and was on 12V. The phone was able to boot and stayed on. It did shut off when I call myself and hung up. I didn't thoroughly check it, but looks like the battery has gone bad.
On top of it, I have the phone plugged into the wall charger for the last twenty minutes and has not charged with the display on. it's remained at 95%.
Side question, anyone know if the NOte 3 battery is interchangable with the Note 2's? I have a coworker who is willing the switch batteries for a few minutes to see what happens between the phones.
I'm home in my normal stomping grounds. Apparently my phone can connect to LTE, but no 3G. Today, briefly, it said it was connected to 3G, but when I tried to use anything that was internet based, such as Google Play, nothing would connect. I'm not sure it that was because the area was congested, or the phone. I usually could connect, but it would be a little slow.
lovekeiiy said:
I was able to check to see how if the phone works off an external battery. I didn't work with a Durcell MyGrid. I thini it's has a 3.2A capacity and outputs 5V.500mha.
I tried with an Ander that has 10A compacity. I don't recall the output, but it has a swithc for 5V and 12V, and was on 12V. The phone was able to boot and stayed on. It did shut off when I call myself and hung up. I didn't thoroughly check it, but looks like the battery has gone bad.
On top of it, I have the phone plugged into the wall charger for the last twenty minutes and has not charged with the display on. it's remained at 95%.
Side question, anyone know if the NOte 3 battery is interchangable with the Note 2's? I have a coworker who is willing the switch batteries for a few minutes to see what happens between the phones.
Click to expand...
Click to collapse
it sucks just order one from amazon for about 10 bucks. pretty cheap. and to answer your question no note 3 battery would not fit note 2. note 3 battery is a bit larger.
coolwater22 said:
it sucks just order one from amazon for about 10 bucks. pretty cheap. and to answer your question no note 3 battery would not fit note 2. note 3 battery is a bit larger.
Click to expand...
Click to collapse
That was my thought as well. I googled to find out and apparently the Note 3 has four contact terminals versus the three of the Note 2.
lovekeiiy said:
That was my thought as well. I googled to find out and apparently the Note 3 has four contact terminals versus the three of the Note 2.
Click to expand...
Click to collapse
Just order a replacement battery. You can even order an extended battery to give you that extra juice if you want XD
I replaced the OEM with an Anker 3100mAh battery. Phone now boots with no issues and stays on. I think it may be just a smidge small because if I toss the phone on, say a counter, it will shut off. No issues with power since I've been using it; it's only been a few days.
I'm still having issues with connecting to 3G. I think I need to reflash the modem because I tried reflashing when I was issues with the phone, and the phone rebooted in the middle to the flash. Thus, I need to root the phone, install a custom recovery so I can do what I think. Luckily for me, for the most part, I spend most of time in areas where I get LTE.
lovekeiiy said:
I replaced the OEM with an Anker 3100mAh battery. Phone now boots with no issues and stays on. I think it may be just a smidge small because if I toss the phone on, say a counter, it will shut off. No issues with power since I've been using it; it's only been a few days.
I'm still having issues with connecting to 3G. I think I need to reflash the modem because I tried reflashing when I was issues with the phone, and the phone rebooted in the middle to the flash. Thus, I need to root the phone, install a custom recovery so I can do what I think. Luckily for me, for the most part, I spend most of time in areas where I get LTE.
Click to expand...
Click to collapse
A small piece of paper wedged between bottom of battery and phone will help with that. Just trim to fit after you know it is tight.
Sent from my SPH-L900 using XDA Premium 4 mobile app
won't connect to 3G
The title is slightly misleading Basically, the phone won't connect to 3G. It does here and there, but usually it only connects briefly. Enough to see the 3G indicated, but disconnects. Aftera few minutes of this, it will finally connect. The speeds are really slow, even for 3G.
I can connect to LTE with no problems. Speeds are where I expect and have experienced.
The phone use to swith to LTE and 3G with no problem. If I streaming a video, it would continue with no problem. The biggest issues, per se, it wouldn't switch back to LTE when I got back into a LTE area. Now, when I hit a non-LTE area, I lose data connection.
Plus, I've been getting a lot of 1G connections, where I was normally getting 3G.
I tried reflashing the NE2 modem, twice actually. No changes. I haven't been able to find much for any solutions. I'm currently running CM11
Related
UPDATE:
Turns out my phone is not completely dead.
If I plug it into the computer, it registers a sound indicating a USB is connected,
but not more than 2 seconds later, it sounds again (the sounds of a USB error, Ba, dum, dum)
When I look at device manager, I see: Omap4440 quickly, but then it goes away. This recycles about 8 times and then it just stops.
I read that this might be due to the phone constantly rebooting.
The screen never turns on. I can't get into the bootloader since the screen is dead.
The only problem now is how can I go about this?
-----------------------
I had more than 90% battery because I just unplugged it. I did a reboot to clear any background apps (like restarting a computer, right?) and it just never came back on.
I placed it into my pocket for that minute while it was rebooting but I never watched as the screen went off. When I took it out of my pocket, it was a dead screen.
I already tried volume + power. And/also holding power itself for a while.
Plugging it back into the charger doesn't do a thing. No charge. Screen remains dead. No vibration is present to indicate the phone at least came on.
What is going on here?
My only conclusion is my jacket may have created a static field which caused a short when I pulled it out. Could this be possible? Especially since there are 3 contact points for the dock on the sides?
Using a GSM version if that matters.
lemonspeakers said:
I had more than 90% battery because I just unplugged it. I did a reboot to clear any background apps (like restarting a computer, right?) and it just never came back on.
I placed it into my pocket for that minute while it was rebooting but I never watched as the screen went off. When I took it out of my pocket, it was a dead screen.
I already tried volume + power. And/also holding power itself for a while.
Plugging it back into the charger doesn't do a thing. No charge. Screen remains dead. No vibration is present to indicate the phone at least came on.
What is going on here?
My only conclusion is my jacket may have created a static field which caused a short when I pulled it out. Could this be possible? Especially since there are 3 contact points for the dock on the sides?
Using a GSM version if that matters.
Click to expand...
Click to collapse
try pulling the battery out for 3+minutes, then put it back in and try booting.
Sorry that happened to ya. I would plug it in and keep it plugged in for a solid hour, then try booting it up. I had that happen to me on a previous Android....HTC EVO. I was rooted and just died (even though it said it had plenty of battery). For some reason it lied and was actually out of juice bigtime.
Rooted custom ROMS have known bugs, albeit extremely minute bugs. Give it a try and report back.
Happens every now an then with most galaxy nexus users, battery pull always fixes it, no need to wait 3 minutes, out an straight back in works for me then hit power on button an you will get the vibe an boot.
Sent from my Galaxy Nexus using xda premium
slayr76 said:
Happens every now an then with most galaxy nexus users, battery pull always fixes it, no need to wait 3 minutes, out an straight back in works for me then hit power on button an you will get the vibe an boot.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
yeah, i know what you mean because it has happened to me before plenty of times. But this, it's different. It's practically dead and all methods i've tried has not seem to work. I'm seriously out of ideas.
So it's been charging over night and the phone is still dead and wont turn on.
I've even replaced it with a spare battery which I know is at least 90% full.
Anyone? I'm so sad why my nexus just died like that.
rebump... =-( I am so that it just died with no reasons as to why... I've had zero problems with it!
You could attempt an OMAPFlash on it, then reload the factory image via fastboot.
That works for me about 90% of the time in GNex repair situations such as this.
Good luck.
Any water indicators showing water damage? If not, start contacting your provider / insurance / Samsung about a replacement.
Replacement man!
Sent from my Galaxy Nexus using Tapatalk 2
simms22 said:
try pulling the battery out for 3+minutes, then put it back in and try booting.
Click to expand...
Click to collapse
Simms is that you from the nexus s? If so, can't wait to see you uploading a quadrant shot of your next over clocked phone.
Op, plug it to a computer and check what happens. Otherwise call for a replacement.
Does this mean I will get a refurbish model? Can anyone quickly explain to me the process to get a new GN and the time it took for you to get your replacement?
If the power button itself is at fault, you can send a power on signal by plugging in the phone with no battery installed and then with the wire still plugged in insert the battery. This method requires no button input whatso ever
Edit , i used to do this by accident all the time while flashing htc devices. Not sure if samsungs hardware offers the same troubleshooting functionality and im not at a wire right now to test the theory. But its worth a shot.
Sent from my Galaxy Nexus using Tapatalk 2
I had something with these symptoms about 4 days into owning my phone.
The way I fixed it was booting into ODIN mode (vol down & power). The only way out of that one is also a battery pull.
Sorry: I meant to say: battery pull, ODIN, battery pull, then it turned on again normally.
android01 said:
If the power button itself is at fault, you can send a power on signal by plugging in the phone with no battery installed and then with the wire still plugged in insert the battery. This method requires no button input whatso ever
Click to expand...
Click to collapse
Already tried it. Does not work.
m.is.for.michael said:
I had something with these symptoms about 4 days into owning my phone.
The way I fixed it was booting into ODIN mode (vol down & power). The only way out of that one is also a battery pull.
Sorry: I meant to say: battery pull, ODIN, battery pull, then it turned on again normally.
Click to expand...
Click to collapse
I'll give this one a try. But I never thought a combination like that would revive a dead phone. I mean, it's dead as if it was just a children's toy with no electronic board inside. No power even though all 3 battery I tried have at least 90% charge. MY Charger is not defective as it works with my other phones.
Naezor said:
You could attempt an OMAPFlash on it, then reload the factory image via fastboot.
That works for me about 90% of the time in GNex repair situations such as this.
Good luck.
Click to expand...
Click to collapse
Won't work since I can't even turn on the phone. Computer doesn't see it (Obviously because it can't power on).
krze said:
Any water indicators showing water damage? If not, start contacting your provider / insurance / Samsung about a replacement.
Click to expand...
Click to collapse
Indicators show no water damage. This was in my pocket. Unless I pee'ed in my jacket, it shouldn't be wet there.
Thanks for the help guys, but I'm running out of ideas. There's only so much you can do with a phone that cannot turn on. =(
Turns out my phone is not completely dead.
If I plug it into the computer, it registers a sound indicating a USB is connected,
but not more than 2 seconds later, it sounds again (the sounds of a USB error, Ba, dum, dum)
When I look at device manager, I see: Omap4440 quickly, but then it goes away.
I read that this might be due to the phone constantly rebooting.
The screen never turns on. I can't get into the bootloader since the screen is dead.
The only problem now is how can I go about this?
Basically, what you're seeing means the phone is still alive, but the firmware is corrupted.
Try this thread, and particularly this post.
No idea if it works or not.
http://forum.xda-developers.com/showpost.php?p=25849293&postcount=20
m.is.for.michael said:
Basically, what you're seeing means the phone is still alive, but the firmware is corrupted.
Try this thread, and particularly this post.
No idea if it works or not.
http://forum.xda-developers.com/showpost.php?p=25849293&postcount=20
Click to expand...
Click to collapse
I just tried it. I used the program. I'm stuck on this part for 20 minutes every time after 5 different attempts.
Any clue?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is this a hard brick or a soft brick?
This sounds like hardware failure to me. Drop the phone at all, ever? If not, could just be faulty hardware.
Honestly the Galaxy Nexus seems to be of poorer build quality (internals, screen, back cover, etc) than every other Android phone I've ever had. Not that I don't love my Nexus, just an observation.
Sent from my Galaxy Nexus using xda premium
So I'm watching tv, and I plug in my phone to charge it a bit because the GPS had gotten stuck on this morning and I burned my battery down to 40%. All of a sudden I hear it buzzing over and over again...like a reboot loop.
So I pull it out of the charger, pull the battery and let it try to boot. Gives the samsung screen for a moment, then flickers, and again to the reboot loop. Holding down power for 10 sec makes it do the same thing, I can't force it into recovery or DL mode without it bootlooping either! At one point I was able to get to the download mode screen, but just 3 seconds and the screen goes black, and back to bootlooping.
I literally did nothing to it. Only thing I did different today was the GPS got stuck (which it has done before), I rebooted the phone, then when it booted again I went ahead and just shut off the GPS. But this was like 20 minutes before this started happening.
So what can I do? Right now its plugged into my computer charging while off, seems to be the only thing it can do without bootlooping.
Running CM9.1 Nightly 9/3 with included kernel and LC8 radio (I think)
zander21510 said:
So I'm watching tv, and I plug in my phone to charge it a bit because the GPS had gotten stuck on this morning and I burned my battery down to 40%. All of a sudden I hear it buzzing over and over again...like a reboot loop.
So I pull it out of the charger, pull the battery and let it try to boot. Gives the samsung screen for a moment, then flickers, and again to the reboot loop. Holding down power for 10 sec makes it do the same thing, I can't force it into recovery or DL mode without it bootlooping either! At one point I was able to get to the download mode screen, but just 3 seconds and the screen goes black, and back to bootlooping.
I literally did nothing to it. Only thing I did different today was the GPS got stuck (which it has done before), I rebooted the phone, then when it booted again I went ahead and just shut off the GPS. But this was like 20 minutes before this started happening.
So what can I do? Right now its plugged into my computer charging while off, seems to be the only thing it can do without bootlooping.
Running CM9.1 Nightly 9/3 with included kernel and LC8 radio (I think)
Click to expand...
Click to collapse
My first guess is your battery is shot. i was gonna recommend the power button failure but if its staying off it might not be that. but id let it charge fully then try to boot up.
Thanks, oddly after a bit of messing around finally got it to boot up. Immediately backed up in CWM....seems to be acting OK now. Idk what happened...
i'll guess, the USB connector got short-circuited when you plugged in, and it caused a cascade failure that fried the SD card or something else inside the phone
there was a factory defect back then with the old SGS 1 (i9000m) model, they fixed that after the 3rd batch, everyone with an old phone from 1st and 2nd release batches, were able to exchange i for a new one.
however in your case, that's not a factory defect, but you plugged it wrong (my guess)
because it has happened to me before when i plugged it in, but the battery was still not charging even after several minutes, yet the phone was getting really really hot
then i unplug, and plug it back in and got the sound feedback "tuu tuud" and then it was actually charging after a few minutes
the first time around even though the charging icon changed, there was no feed back sound, and that was the key, it was not plugged in properly.
so after that time, i always made sure to verify to make sure the phone was plugged in properly and not just relay on he visual icon.
check back after a few minutes, to make sure the phone doesn't get very hot, and it actually increased 1%
It happened again today! After a full charge overnight and no problems for the day up to a little while ago, I opened my email app, it froze, then proceeded to start boot looping. I'm in class so I don't have my computer to try to bring it out of it...so yeah that sucks...
I do remember when I got it to charge yesterday it showed it was charging for 20-30 minutes, but after I "revived" it, I found it hadn't charged at all.
I have been using a Nokia USB cable to charge my phone since I got it, because it was longer than the cheapie Samsung cable that came with it...but it hasn't ever caused problems before. And it charged just fine last night.
How long is the warranty on these things thru tmobile? I may just swap it out while I still can.
Also on an unrelated note, I upgraded to the LG3 radio because I was meaning to anyways...
I pulled it out of it again! This time I held the power button while putting the battery in, when it vibrated I let go, it vibrated again, showed the Samsung logo, and then booted like normal
May I ask what rom are you currently on?
datrapstar said:
May I ask what rom are you currently on?
Click to expand...
Click to collapse
CM9.1 nightly 9/3 with included kernel
It did it a third time during class while it was in my pocket, the power button trick didn't work this time, I had to pull the battery after the samsung logo, plugging it back in to get it to boot...but...
near the end of the CM9 boot animation, when it vibrates and the auto brightness kicks in, it started it again! I have yet to revive it...
This is a bit upsetting because I had just got CM9 the way I liked it and I don't exactly have the time right now to mess with warranty and a new phone...I would like to fix it.
There are about 20 different threads on here on how to revert to stock...let me as a last ditch try to revert to stock and see if it keeps doing it...unless somebody has any ideas...
I was working in recovery mode, i super-wiped my phone to see if installing a ROM from scratch would help, and my phone even does it in recovery mode. Warranty time.
So whats the fastest way to restore to stock? Who knows how long I will have after reviving it before it breaks again.
zander21510 said:
I was working in recovery mode, i super-wiped my phone to see if installing a ROM from scratch would help, and my phone even does it in recovery mode. Warranty time.
So whats the fastest way to restore to stock? Who knows how long I will have after reviving it before it breaks again.
Click to expand...
Click to collapse
Here you go!!
http://forum.xda-developers.com/showthread.php?p=30832325
Sent from JMT Goodness
Well, finished playing stupid for T-Mobile, in two weeks I will have my replacement T989. Now all that's left is returning this thing to stock before it starts acting up again.
And my temporary replacement phone?
HTC Dream, aka the G1, the first Android phone! Lol what a difference...GB feels like a dinosaur...
http://forum.xda-developers.com/showthread.php?t=1513359
[HOWTO]Restore to Stock/Recover from a Bad Flash. Could try the last 3 pages on this thread. That will help you go back to stock without an issue. Hell might make you wanna keep your phone if you can get it to work again.. good luck
Sent from my SGH-T989 using xda app-developers app
datrapstar said:
http://forum.xda-developers.com/showthread.php?t=1513359
[HOWTO]Restore to Stock/Recover from a Bad Flash. Could try the last 3 pages on this thread. That will help you go back to stock without an issue. Hell might make you wanna keep your phone if you can get it to work again.. good luck
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Thanks! got it all done, back to ugly, ugly stock lol...and just when I thought maybe I would have to brick it myself it did the reboot thing again...so pulled the battery and there it sits factory reset.
I'm using Jellybeast rom for a couple weeks now: http://forum.xda-developers.com/showthread.php?t=1885619
I plugged my phone in to my charger at work today, which is a regular occurrence. After about 20 minutes I checked on the charge level and found the phone to be really warm/hot. I unplugged it and let it sit for a while. Still hot at that point so I rebooted it and it would never get past the Galaxy S2 progress bar screen. Pulled the battery and left it out for my 1 hour drive home.
I'm at home now and put my SIM card into my Vibrant and my S2 still won't boot. It's also still getting warm when I try to boot it.
Is my S2 hosed at this point? I have the insurance on it, but would hate to lose my data on the internal SD. I really don't want to reset or flash a new ROM on it right now.
Edit: Pulled battery and plugged into charger. It's vibrating every couple seconds. No response to any button presses.
exoplasm said:
I'm using Jellybeast rom for a couple weeks now: http://forum.xda-developers.com/showthread.php?t=1885619
I plugged my phone in to my charger at work today, which is a regular occurrence. After about 20 minutes I checked on the charge level and found the phone to be really warm/hot. I unplugged it and let it sit for a while. Still hot at that point so I rebooted it and it would never get past the Galaxy S2 progress bar screen. Pulled the battery and left it out for my 1 hour drive home.
I'm at home now and put my SIM card into my Vibrant and my S2 still won't boot. It's also still getting warm when I try to boot it.
Is my S2 hosed at this point? I have the insurance on it, but would hate to lose my data on the internal SD. I really don't want to reset or flash a new ROM on it right now.
Edit: Pulled battery and plugged into charger. It's vibrating every couple seconds. No response to any button presses.
Click to expand...
Click to collapse
Not positive, but for some reason sounds like you are in a bootloop, or soft bricked.
You can wait and see what others say, but you may need to try to get into download mode and Odin flash stock....and go from there.
I've had the vibrate problem a couple times, usually after a bad flash of some sort tho. Fixed it with Odin.
Sent from my cell phone telephone....
I had a similar problem when ever I would use cm10. So I just used Odin and went back to stock... I think im done flashing for a bit...honestly I think your might have to use Odin homie.
Sent from my SGH-T989 using xda premium
Hi everyone,
So I've had many problems with my phone (Galaxy S3 by Videotron) ever since I rooted it (5 days ago). It started by simply turning off on its own and taking a lot of time to boot back up. Today, it started doing bizarre things: for instance it wouldn't boot at all unless I tried many many times (it would get stuck at the Samsung logo). Also, when I managed to boot it, the touchscreen wouldn't work very well when I used the keyboard (i.e. if I pressed 'a', it would press 'n' for example and so forth).
So I decided I wanted to master reset it, but whenever I restarted the phone to get into recovery mode, I managed to get there but once it got stuck on the android icon. So I took off the battery and ever since began my huge problems. After that I just couldn't get it to boot back up (always getting stuck at the samsung logo). So I had to take off and replace the battery many times, and now there is absolutely nothing that makes it even get to the samsung logo. I tried the download mode, recovery mode, plugging it on the computer, taking off the battery and plugging the USB: absolutely nothing helps, it's as if the phone is just dead. At this point I have lost any hope If anyone has a suggestion on what I could do, I would be super grateful! And if it is impossible to get it back to work, please let me know also so I don't get any hopes.
TL;DR: Phone doesn't boot at all: nothing shows up when I try to boot it, even in recovery mode and download mode. Same thing if I try to plug it to a computer.
Thanks a lot
PS. Forgot to mention, the phone was charged before it stopped working.
re: dead phone
zimo11 said:
Hi everyone,
So I've had many problems with my phone (Galaxy S3 by Videotron) ever since I rooted it (5 days ago). It started by simply turning off on its own and taking a lot of time to boot back up. Today, it started doing bizarre things: for instance it wouldn't boot at all unless I tried many many times (it would get stuck at the Samsung logo). Also, when I managed to boot it, the touchscreen wouldn't work very well when I used the keyboard (i.e. if I pressed 'a', it would press 'n' for example and so forth).
So I decided I wanted to master reset it, but whenever I restarted the phone to get into recovery mode, I managed to get there but once it got stuck on the android icon. So I took off the battery and ever since began my huge problems. After that I just couldn't get it to boot back up (always getting stuck at the samsung logo). So I had to take off and replace the battery many times, and now there is absolutely nothing that makes it even get to the samsung logo. I tried the download mode, recovery mode, plugging it on the computer, taking off the battery and plugging the USB: absolutely nothing helps, it's as if the phone is just dead. At this point I have lost any hope If anyone has a suggestion on what I could do, I would be super grateful! And if it is impossible to get it back to work, please let me know also so I don't get any hopes.
TL;DR: Phone doesn't boot at all: nothing shows up when I try to boot it, even in recovery mode and download mode. Same thing if I try to plug it to a computer.
Thanks a lot
PS. Forgot to mention, the phone was charged before it stopped working.
Click to expand...
Click to collapse
Just because it was charged before it stopped working it does not mean it's charged now so
beg, borrow or steal a new or used fully charged battery and see if you can go into recovery.
OR buy a external battery charger and charge the existing battery.
If you cannot afford a battery charger then beg borrow or steal one.
If you cannot beg, borrow or steal a battery then what I am about to tell you will sound very
strange... but here it goes, this test will let you know if your phone is bricked or not.
Remove the battery and put it into the freezer for at least a couple hours.
Remove the battery from the freezer and wipe all the moister off of it.
Replace the battery in the phone and simply try to turn the power on.
If anything comes up on your screen like the ANDROID logo or anything else it means your phone is NOT bricked
and it means that it needs a fully charged battery to continue to fix whatever the issue is you are having with the phone.
If nothing comes up on the screen and its totally blank black screen then the phone is bricked and needs to be Jtag'ed.
It costs between $30 to $60 bucks to send it to a cell phone shop and have it fixed. There are many of them on eBay.
Good Luck!
-
I've been away from the Xperia S forums for about 4 months now, since my Xperia S died. I've been using a Samsung Galaxy S II, but i'm pretty tired of it, don't like amoled screens, battery issues, constant reboots, radio problems and it goes on and on.. SO I want to try to revive my Xperia S.. Here is what happened:
4 Months ago, I had just finished flasing a Paranoid Android ROM (4.4.2 KK) and was setting up the phone, had just finished installing some apps and was testing some CPU Governors, I/O Schedulers and things like that, running AnTuTu and Quadrant benchmarks. In the middle of an AnTuTu bench, the phone just shut down (with about 50% battery left) and woudn't turn on again. When connecting the charger, the LED woudn't light up, the phone wouldn't vibrate, Vol Up + Power wasn't working, coudn't enter recovery/download modes. Hard bricked. So I opened up the phone and removed the battery, tryed plugging in again and nothing, so I left the battery outside the phone for a couple of days. After that, I made a quick "short circuit" with the batter, about 1/2 seconds, and plugged it back in, connected the charger and the phone came back to life. Now I could enter fastboot mode, so I re-flashed the stock .96 using Flash Tool, re-rooted, and re-flashed a newer build of Paranoid Android and everything was working fine again. I managed to backup all my photos and documents, and left the phone charging overnight while downloading some apps from the Play Store. When I woke up: dead again, but this time it's different. When I connect the charger the RED LED lights up, but it turns off after a couple of minutes. The rest is exactly the same: can't enter recovery, can't boot, can't fastboot, Vol Up + Power isn't working.. So I took off the battery and tryed a short circuit again, but this time nothing happend.. The first time the the cables heated up quickly and this time nothing happened. So I don't know what exactly is going on. Is the battery completely dead (2 years old phone)? Or is my device unable, somehow, to charge the battery? If there is no charge at all, the short circuit won't work.
Anyone with any experience or any guess? I'm searching for a new battery so I can test it but it's kind of expesive here, about 60USD. I can't stand the SGS2 anylonger, and I'm not buying any phone until the Snapdragon 810 shows up.
I'm having a similar problem: After installing uCyan everything except the battery drain (irrational jumps in the curve) seemed to work. Then at some point the phone died and now is in a charging (red light, some minutes), bootup loop. Sometimes it reached the sys to then instantly die again. I was able to get into TWRP when I fortunately saw the next bootup. But the battery is too low to get stock or any other recovery back. So everything seems broken. I have tried with two USB cables. The phone/battery is over 2 years old.
If any further actions could help, please let me know. Would also love to revive this phone.
ChriMo said:
I'm having a similar problem: After installing uCyan everything except the battery drain (irrational jumps in the curve) seemed to work. Then at some point the phone died and now is in a charging (red light, some minutes), bootup loop. Sometimes it reached the sys to then instantly die again. I was able to get into TWRP when I fortunately saw the next bootup. But the battery is too low to get stock or any other recovery back. So everything seems broken. I have tried with two USB cables. The phone/battery is over 2 years old.
If any further actions could help, please let me know. Would also love to revive this phone.
Click to expand...
Click to collapse
try the rubber band trick from here.
Ok I will try rubber band trick then. I think I already did it two times. I would have liked to avoid flashing the stock.ftf back and then doing again the unlocking, rooting and custom ROM flashing.
ChriMo said:
Ok I will try rubber band trick then. I think I already did it two times. I would have liked to avoid flashing the stock.ftf back and then doing again the unlocking, rooting and custom ROM flashing.
Click to expand...
Click to collapse
I thought You hadn't done that. You don't need to unlock bootloader again even if You flash stock ftf. And if You intent to flash a Kitkat or Lollipop based ROM, then You can simply skip rooting and all and follow the method from here.