Related
I have searched multiple threads, on here and the rest of the intertubes, I haven't found anything that helps. Most of the tips I have come across deal with flashing in Odin, Roms, etc. I don't think any of those really apply here( I could be wrong about that)
Here is my problem....My wife's vibrant running stock 2.1(Not sure why she isn't running something more current) is acting up. She hasn't had any problems with it before, and there was no event that would point to these problems being a symptom.
It does the following -
Won't turn on.
Gets stuck at The Vibrant screen... Then shuts off.
Gets stuck at the TMO screen... Then shuts off.
Gets to "Scanning Media"... Then shuts off.
Gets to the Galaxy S screens and seems to be in a loop for about 45 seconds...Then shuts off
Gets to home screen, for about 20 seconds, this is as far as I can get...Then shuts Off.
All of these happen interchangeably and seemingly without any sort of reason or rhythm.
What I have tried -
Battery, sim, and sd out and restart
Change battery, with my Vibrant. My vibrant works fine with both.
Tried to update firmware with Kies... phone shuts down before any progress is made.
Not sure what else to do, but I would be willing to try just about anything.
Thanks
Sounds like it could be hardware, but you could try reflashing it with Odin. I'd suggest first just getting it into download mode while plugged into USB. If it shuts down while just sitting there while plugged in, I'd consider that hardware.
That's not looking good.
You could try flashing a CWR (Clockwork Recovery) zip and seeing if some of the normal cleaning techniques do anything (wipe cache, wipe dalvick cache, and fix permissions). The file and some tips on CWR can be found here http://forum.xda-developers.com/showthread.php?t=849028
You don't have to root to flash CWR. You can just do that one by itself. One thing to note is that you may have to do the reinstall packages step twice from the recovery menu. The second time would take you into CWR.
Having CWR on there would be nice since you can try some other things like flashing a different kernel to see if that helps. I'd recommend using Odin to flash the stock bootloader as well just as something else to try.
Thanks for the idea. I have been wanting to try it, but I could not get the phone to stay on or enter recovery.
Like I said I was willing to try anything, so when a friend said, throw it in the freezer for a few minutes, I was skeptical. But it works. As long as the phone is cold, it will turn on, make phone calls, etc. Usually for about 3-4 minutes. Then it warms up and shuts off. The only way to get it back on is another trip to the freezer.
Does anyone have any idea, what my issue could be? And how to fix it?
Thanks.
That's definitely hardware. Could be a bad solder joint, fixable, but it sounds more like a chip that is unstable at room temperature. I suggest you buy one with a bad screen cheap and make one good phone out of them. Adam Outler, the Unbrickable Mod guy, might have some ideas.
Last night my phone started bootlooping very frequently. I was running the CM10 built with Samsung source that was posted in this section for a while with absolutely no problems, when suddenly the phone shut off and started doing short, quick vibrations repeatedly. Like the vibration that the phone makes when it first turns on and shows the Samsung logo. I pulled the battery but it continued once I put the battery back in. Eventually I got it to boot but soon after it booted it started again. I am now running Blackjelly v1, and though less frequent, the problem still persists...does anyone have any idea what could be causing this?
zefir738 said:
Last night my phone started bootlooping very frequently. I was running the CM10 built with Samsung source that was posted in this section for a while with absolutely no problems, when suddenly the phone shut off and started doing short, quick vibrations repeatedly. Like the vibration that the phone makes when it first turns on and shows the Samsung logo. I pulled the battery but it continued once I put the battery back in. Eventually I got it to boot but soon after it booted it started again. I am now running Blackjelly v1, and though less frequent, the problem still persists...does anyone have any idea what could be causing this?
Click to expand...
Click to collapse
Mine did the same thing... It was crazy...Nothing I did fixed it... Flashed away at any 4.2.2 Rom and It was consistent bootloop... Decided to take phone apart and clean power button (read somewhere power button gets stuck) Same issue bootloop... I odined back to stock...bam it worked...now the capacitive buttons don't work... So after booting stock I flashed TWRP recovery and attempted to flash 4.2.2 rom to no prevail, I am only capable of flashing BlackJelly v1 any other rom sends me into (App is upgrading screen after boot after apps say Starting Apps bootloop) nonstop bootloop...
I honestly wonder if my phone is the only phone that will not accecpt 4.2.2 roms...
kaljr1980 said:
Mine did the same thing... It was crazy...Nothing I did fixed it... Flashed away at any 4.2.2 Rom and It was consistent bootloop... Decided to take phone apart and clean power button (read somewhere power button gets stuck) Same issue bootloop... I odined back to stock...bam it worked...now the capacitive buttons don't work... So after booting stock I flashed TWRP recovery and attempted to flash 4.2.2 rom to no prevail, I am only capable of flashing BlackJelly v1 any other rom sends me into (App is upgrading screen after boot after apps say Starting Apps bootloop) nonstop bootloop...
I honestly wonder if my phone is the only phone that will not accecpt 4.2.2 roms...
Click to expand...
Click to collapse
It's now bootlooping like crazy. It'll turn on for like 5 minutes and then go right back to bootlooping. My USB port is kinda screwy so it's hard to odin anything. I'm at a loss for what to do.
zefir738 said:
It's now bootlooping like crazy. It'll turn on for like 5 minutes and then go right back to bootlooping. My USB port is kinda screwy so it's hard to odin anything. I'm at a loss for what to do.
Click to expand...
Click to collapse
I had boot looping problems several times now. For me, it's always been sticky power button. One time, I forgot it had that problem at work and looped for 30 minutes. I just take out the battery for about an hour, then get the power button unstuck. My button gets stuck at the bottom of the button, so I can normally mess with the top part to fix it.
So the issue has escalated even further now. It is a sticky power button, i believe, but now when the phone tries to turn on it shows both samsung logos and then shuts right back off and refuses to turn on again unless i do a battery pull...I'm not even sure if it's turning off, actually. It turns on immediately after inserting a battery into the device. But right now I have a fancy brick.
Definitly a power button issue
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Similar Issue
My phone started doing a crazy bootloop just out of the blue last night. I have never had a problem. I took the battery out to put my memory card back in. I'd been using it for my digital camera. This is not out of the ordinary. I do it all the time. But after I replaced the card, battery and cover it started this continuous boot loop. Sometimes it will go to the main screen and allow me to perform some functions, but then it goes right back to the bootloop. I am running the Padawan JB rom. I did the complete wipe, factory reset and re-flash. But it still did the bootloop. The only time it does NOT exhibit this issue is when the phone is on the charger. Then and only then it works perfectly. Is it the battery? Why will it bootloop without the charger and work fine when on the charger?
It is probably your battery
cayjominara said:
My phone started doing a crazy bootloop just out of the blue last night. I have never had a problem. I took the battery out to put my memory card back in. I'd been using it for my digital camera. This is not out of the ordinary. I do it all the time. But after I replaced the card, battery and cover it started this continuous boot loop. Sometimes it will go to the main screen and allow me to perform some functions, but then it goes right back to the bootloop. I am running the Padawan JB rom. I did the complete wipe, factory reset and re-flash. But it still did the bootloop. The only time it does NOT exhibit this issue is when the phone is on the charger. Then and only then it works perfectly. Is it the battery? Why will it bootloop without the charger and work fine when on the charger?
Click to expand...
Click to collapse
The Note won't run without a proper battery installed. I had the problem where I swapped out my dead battery for a fully charged one (I do this everyday) and all of a sudden it kept bootlooping.I spent a few hours, when I got home, flashing it back to stock etc to no avail. I could get into download mode, and download to my hearts content but when I tried to boot the phone, it looped. Samsung, samsung, samsung....
I swapped back my, now charged, spare and BAM it booted into stock android no problem. I think my first (stock samsung battery actually) is finished. Or at least has some serious issues, and the phone refuses to boot with it in but my spare (Anker battery) works fine.
I hope this works for you's, it did for me
---------- Post added at 03:27 AM ---------- Previous post was at 03:25 AM ----------
Also, if I had just charged my phone using my working battery, I would have saved myself some serious grief, and hours wasted. Here's to hoping you don't too!
What happen before the problem presented itself was me being on Kik, reading my messages there. After reading all of them, I went out of the program, and onto my app drawer. Suddenly, the screen became all black. I tried pressing the power button, with no luck. I then disconnected my phone from the charger, pulled the battery, put it back in and then tried the power button, still no luck. (I also tried booting to both recovery and download modes. No luck).
Before this happened, the phone wasn't hot (at all), so this isn't due to overheating. It's also not an app misbehaving, as I haven't installed anything new in ages, and what I do have installed are apps from well-known developers/companies, so it's not malware either.
The phone itself was running on DorimanX kernel (a month or so old release) with Resurrection Remix 4.0.5. It was also underclocked to 800mhz.
Does anyone know if I can fix it? (I did a search, and noone had THIS exact problem so I haven't tried much)
~November
If the phone won't even boot you're probably SOOL. Try King Rat's hotboot method (search) where you try to jumpstart the phone with the charger minus the battery. Maybe even try another battery (at least you'll have a spare when you get it fixed.
If it doesn't boot, there's not really anything anyone here can say/suggest. There are no miracle fixes in these situations.
I'm new to this site so if this thread is in the wrong place, please redirect me to the appropriate section.
A couple days ago, my GSR had shut off for no reason that I could find, and would not turn on (even to try to boot in recovery mode) for 2 hours(it would go into the boot screen but would then shut off after 5-7 seconds of "booting up"), when suddenly it started working again. I couldn't figure out why it stopped working or why it suddenly starting working again. I even changed batteries but that didn't influence anything. Then, exactly (I mean exactly) 24 hours later at the same time, it shut off again. This time, it won't even show the boot logo, and instead says, for less than a second "Movinand checksum confirmation fail." It is rooted, but has been rooted for almost a year with no real modifications done to the device and no previous issues that I noticed. I have tried changing batteries, trying different chargers, replacing the SIM and SD, and tried booting into recovery but has no effect because it shuts off before I can even do anything to it. I've seen a lot of places say wipe cache partition by going into recovery mode, but that's just not possible with what is going on. I try every other hour to see if it has somehow started working again, but now won't even show the "movinand checksum..." message. It is charged because it has been plugged in most of the time that this has been going on. It's not water damaged, I have never dropped it, and it hasn't been exposed to any intense heat or coldness ever in its life. I'm at a loss here, not sure what to do, as it seems I've tried nearly everything. I'm welcoming any suggestions you may have, as well as answering any questions about the situation.
In Need of Dire Help! Galaxy S Relay 4G(SGH-T699) Completely Bricked?
XmashMAN said:
I'm new to this site so if this thread is in the wrong place, please redirect me to the appropriate section.
A couple days ago, my GSR had shut off for no reason that I could find, and would not turn on (even to try to boot in recovery mode) for 2 hours(it would go into the boot screen but would then shut off after 5-7 seconds of "booting up"), when suddenly it started working again. I couldn't figure out why it stopped working or why it suddenly starting working again. I even changed batteries but that didn't influence anything. Then, exactly (I mean exactly) 24 hours later at the same time, it shut off again. This time, it won't even show the boot logo, and instead says, for less than a second "Movinand checksum confirmation fail." It is rooted, but has been rooted for almost a year with no real modifications done to the device and no previous issues that I noticed. I have tried changing batteries, trying different chargers, replacing the SIM and SD, and tried booting into recovery but has no effect because it shuts off before I can even do anything to it. I've seen a lot of places say wipe cache partition by going into recovery mode, but that's just not possible with what is going on. I try every other hour to see if it has somehow started working again, but now won't even show the "movinand checksum..." message. It is charged because it has been plugged in most of the time that this has been going on. It's not water damaged, I have never dropped it, and it hasn't been exposed to any intense heat or coldness ever in its life. I'm at a loss here, not sure what to do, as it seems I've tried nearly everything. I'm welcoming any suggestions you may have, as well as answering any questions about the situation.
Click to expand...
Click to collapse
Edit, 11/12/2014: As of today, I managed to get myself into ODIN mode, but will only stay in ODIN mode for about
5 seconds before it shuts off. I can repeatedly do this as much as I want, but does not change anything to how long before it shuts off. I've tried rebooting through adb reboot-bootloader, but since my pc cannot find my device, I get this error "error: device not found". I made sure the drivers are installed, as they needed to be for me to even root my phone, but still no other results.
Also, when I take the battery out and put it back in, it vibrates as if it will boot up, but then red text saying "Movinand checksum..." comes up for a split second, then vibrates again with the same text. Then I can't do anything else until I remove the battery. I'm thinking about getting a JIG that will force it into download mode or recovery mode if one even exists.
XmashMAN said:
Edit, 11/12/2014: As of today, I managed to get myself into ODIN mode, but will only stay in ODIN mode for about
5 seconds before it shuts off. I can repeatedly do this as much as I want, but does not change anything to how long before it shuts off. I've tried rebooting through adb reboot-bootloader, but since my pc cannot find my device, I get this error "error: device not found". I made sure the drivers are installed, as they needed to be for me to even root my phone, but still no other results.
Also, when I take the battery out and put it back in, it vibrates as if it will boot up, but then red text saying "Movinand checksum..." comes up for a split second, then vibrates again with the same text. Then I can't do anything else until I remove the battery. I'm thinking about getting a JIG that will force it into download mode or recovery mode if one even exists.
Click to expand...
Click to collapse
The jig is for getting the phone into Download Mode, but I don't believe it's any help in keeping it there. If the phone won't stay in Download Mode, even with a charged battery, then I fear the phone is a lost cause. The only other thing that might help at this point would be a JTAG service, if it's available for that device like it is for the more popular Samsungs.
es0tericcha0s said:
The jig is for getting the phone into Download Mode, but I don't believe it's any help in keeping it there. If the phone won't stay in Download Mode, even with a charged battery, then I fear the phone is a lost cause. The only other thing that might help at this point would be a JTAG service, if it's available for that device like it is for the more popular Samsungs.
Click to expand...
Click to collapse
I'm not sure what I did, but I'm able to stay into ODIN mode for as long as I want. I'm still unable to boot into recovery. Is it possible to restore my phone through ODIN?
Sorry, I misunderstood. I thought you had said it reboots while in Download Mode. If it stays there, then that's definitely the 1st thing to try.
es0tericcha0s said:
Sorry, I misunderstood. I thought you had said it reboots while in Download Mode. If it stays there, then that's definitely the 1st thing to try.
Click to expand...
Click to collapse
Well, it stopped turning off while in download mode just recently. I'm just not sure what caused it. Also, I noticed that the battery I had in my phone when it first started shutting off is slightly bloated. I'm not sure if it's serious enough, but I know that bad batteries bloat, and they can potentially cause issues with your device. But I put my default battery in, but it didn't change anything in regard to the movinand error.
The Galaxy S Relay 4G can be a very odd challenge.
XmashMAN said:
Well, it stopped turning off while in download mode just recently. I'm just not sure what caused it. Also, I noticed that the battery I had in my phone when it first started shutting off is slightly bloated. I'm not sure if it's serious enough, but I know that bad batteries bloat, and they can potentially cause issues with your device.
Click to expand...
Click to collapse
Wow! I'm just making a note here as a marker I can return to and follow up on. This seems almost the worst that anyone can deal with. If the person that made this post just so happens to still be around, or for anyone who may be unfortunately dealing with such an issue, I have an either or "possible" fix, yet haven't been in this particular situation. There are repair files for this device I would assume could be used for this. I'm dropping them, and the last official Samsung software issued for the SGH T699. If I so much as even get a hint my device is going in this direction, I usually flash in the original firmware if and when I can. Back it up and flash it again just to make sure I have a clean build. I can work with stock. It's hard to work with a brick. This device can be very strange so far with any results I'm getting. Which is odd to me on one level because I've haven't had as much difficulty with any of my other devices such as I'm having with this one. I always try to be prepared for any eventuality before I start working on "any" device. I'd call it a very important suggestion, especially for this Galaxy S Relay 4G, to prepare yourself, it's going to be a fun ride!
Hello!
Had my N9 for almost 4 years now! About a year in, I started experiencing the white-static-screen-high-pitched-screech issue that many of you have described, but disconnecting and reconnecting the battery connector solved the issue. As of late, I have been running stock Android N.
Recently, I have been starting to experience the issue again, as well as trouble booting up. The problem has gotten much worse over the past two weeks or so, to the point where I cannot fully start up -- the Google logo shows, the start-up animation starts playing, but usually doesn't make it very far before the animation freezes and the screen goes black. I can access the boot menu and Recovery mode though. Going into Recovery mode and explicitly "powering down," letting it sit for a bit, and then starting up sometimes makes it all the way to the OS, but it shuts down by itself shortly after. I cleaned and reconnected the battery connector, but that did not help. I just tried a factory reset, but that doesn't seem to have fixed the issue -- my device is wiped, but if I can get into the OS, it just shuts down as before. If I don't explicitly "power down" and let it sit, the battery does run down, which makes me think that rather than crashing when it freezes, it's still running, or trying to.
Any suggestions? Thanks!
weirdo16 said:
Hello!
Had my N9 for almost 4 years now! About a year in, I started experiencing the white-static-screen-high-pitched-screech issue that many of you have described, but disconnecting and reconnecting the battery connector solved the issue. As of late, I have been running stock Android N.
Recently, I have been starting to experience the issue again, as well as trouble booting up. The problem has gotten much worse over the past two weeks or so, to the point where I cannot fully start up -- the Google logo shows, the start-up animation starts playing, but usually doesn't make it very far before the animation freezes and the screen goes black. I can access the boot menu and Recovery mode though. Going into Recovery mode and explicitly "powering down," letting it sit for a bit, and then starting up sometimes makes it all the way to the OS, but it shuts down by itself shortly after. I cleaned and reconnected the battery connector, but that did not help. I just tried a factory reset, but that doesn't seem to have fixed the issue -- my device is wiped, but if I can get into the OS, it just shuts down as before. If I don't explicitly "power down" and let it sit, the battery does run down, which makes me think that rather than crashing when it freezes, it's still running, or trying to.
Any suggestions? Thanks!
Click to expand...
Click to collapse
Have you tried replacing the battery with a new one?
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Have you tried replacing the battery with a new one?
Click to expand...
Click to collapse
Thanks! I've considered it, but the battery seems like it's OK -- it holds a charge when powered off, and the voltage still seems pretty high (~4.1v) Are there any other ways to tell if the battery might be bad, how do you tell? Has anyone determined if the white-screen-screeching issue is caused by the battery itself, or the battery connector?
weirdo16 said:
Thanks! I've considered it, but the battery seems like it's OK -- it holds a charge when powered off, and the voltage still seems pretty high (~4.1v) Are there any other ways to tell if the battery might be bad, how do you tell? Has anyone determined if the white-screen-screeching issue is caused by the battery itself, or the battery connector?
Click to expand...
Click to collapse
I have the same issue on my n9 but put it out to pasture so I never tried to replace it. I have seen others on here who have and it seemed to work. But, it also seemed that they couldn't find a real good replacement and the replacement battery didn't last that long.
Sent from my [device_name] using XDA-Developers Legacy app
I'm having the exact same problem. No matter what I flash it always get stuck at the bootanimation. Sometimes it doesn't even get past the initial Google logo bootscreen. I can never fully boot to the OS, though.
redsmith said:
I'm having the exact same problem. No matter what I flash it always get stuck at the bootanimation. Sometimes it doesn't even get past the initial Google logo bootscreen. I can never fully boot to the OS, though.
Click to expand...
Click to collapse
Have you tried updating to the lastest factory images from Google? They include additional pieces of firmware than just the OS and many ROMs are built with certain factory builds in mind. The firmware and ROM need to match. The kernel also needs to match. And if you're going to a completely different ROM, you need to factory reset. Or at least, it's a good idea to. Not all ROMs will boot without a factory reset.
gk1984 said:
Have you tried updating to the lastest factory images from Google? They include additional pieces of firmware than just the OS and many ROMs are built with certain factory builds in mind. The firmware and ROM need to match. The kernel also needs to match. And if you're going to a completely different ROM, you need to factory reset. Or at least, it's a good idea to. Not all ROMs will boot without a factory reset.
Click to expand...
Click to collapse
Yes, I flashed the latest factory image. I even flashed the first one (5.0). No matter what I try, it always get stuck at the bootanimation. Same thing with custom ROMs. I suspect something's wrong with the data partition, but not even wiping and formatting does the trick.