S3 4G wont start up - Android Q&A, Help & Troubleshooting

Hi guys im not sure where to post this so im just going to post it here. My s3 got stuck on the boot up samsung galaxy s3 screen so i pulled the battery out and restarted the phone and now it doesnt start up at all its stuck on this static screen i cant get to recover mode but i can get to download mode i was just wondering what the problem might be and if there is a way to fix the phone? I have attached a photo to show you what it looks like.

That's extremely odd. I've personally have had an issue with my old phone with the startup with it giving me a "Fail error", but I can suggest that when it does that, keep the battery out for 10-20 minutes to make sure it stays off. Then put it back in and turn on the phone and see what it does. If that doesn't work I suggest you just either send it in for a new phone or have someone look at it.

ive tried leaving the battery out overnight and still nothing could it be a corupt firmware issue because the phone was playing up before hand for a couple days where it would just freeze and would need to be turned off and on, so i did a full reset cleared everything through recovery mode.

Related

[Q] Problem after installing Jedi Mind Trick X1

So ive been using JMT since the v8 and ive never had a problem before. One night i decided to get the X1 and everything seemed to well..the next day i was chargin my phone and i noticed that the phone was off, the chargitng icon was not showing.
I turned to phone on and it would go halfway the splash screen and then it would go black.. then it would start vibrating the way it vibrates when u turn the phone on and it just does that. I tried doing a battery pull but everything that i put in the battery the phone turns on automaticly.
Ive tried going to recovery but it just wont go in. PC doesnt detect the phone and it looks like theres a 5 second gap before the phone does the same hthing over and over.
I dont know what to do because the phone doesnt let me do anything.No recovery,no nothing.
could somebody help me please?
what can i do!? any other ways to totally erase the whole phone! even if i have to fry the motherboard so i could get a replacement lol! but i dont want to do that tho that would be my last solution
it looks like you may need a jtag to fix the phone, it seems that the X1 may have bricked your phone.

[Q] Am I Eff'ed? Cyanrogenmod recovery phone brick?

Hey guys I'm new to the forums so I apologize if this is not in the correct location or I'm screwing up any forum rules. I have searched this topic for quite a while now, and though most evidence points towards my my phone being bricked i wanted to be sure..
That being said I am in a tight spot here. I really need my phone to be working right now and for some reason it crapped out on me.
I have a Samsung galaxy S II (Skyrocket or SGH i757, whichever is correct) with CyanogenMod installed. It had been acting strangely and was quite slow lately, probably due to the ridiculous amount of apps i had cluttering the memory. So i decided to make an attempt to wipe my data and start fresh. Not long ago i was looking around in the rom manager and got sucked into downloading the clockworkmod recovery TOUCH (which i think were my problem started.) So, I read online that in recovery mode there is a reformat option. So i decided to boot into recovery mode.
The phone turned off alright, but upon trying to reboot the only thing that appears is the "Samsung" screen then nothing but black. I tried then to drop the battery out and reboot. Nothing. Hard boot. Nothing. Even when the phone is off and i plug it in to charge, the charge screen will appear momentarily then disappear. I cant get into ANYTHING
So..... is it somehow bricked? Just from a reboot? It was working just fine before the reboot.....
I have been searching the net and these forums for a while now and haven't found anyone with the same problem. Again, I cannot boot into ANY mode nor will ANYTHING appear on the screen for more than a moment. Holding power and volume down does nothing. When i plug it into the pc it wont recognize........ is there anything i can do??.....
Sam
Smesj said:
Hey guys I'm new to the forums so I apologize if this is not in the correct location or I'm screwing up any forum rules. I have searched this topic for quite a while now, and though most evidence points towards my my phone being bricked i wanted to be sure..
That being said I am in a tight spot here. I really need my phone to be working right now and for some reason it crapped out on me.
I have a Samsung galaxy S II (Skyrocket or SGH i757, whichever is correct) with CyanogenMod installed. It had been acting strangely and was quite slow lately, probably due to the ridiculous amount of apps i had cluttering the memory. So i decided to make an attempt to wipe my data and start fresh. Not long ago i was looking around in the rom manager and got sucked into downloading the clockworkmod recovery TOUCH (which i think were my problem started.) So, I read online that in recovery mode there is a reformat option. So i decided to boot into recovery mode.
The phone turned off alright, but upon trying to reboot the only thing that appears is the "Samsung" screen then nothing but black. I tried then to drop the battery out and reboot. Nothing. Hard boot. Nothing. Even when the phone is off and i plug it in to charge, the charge screen will appear momentarily then disappear. I cant get into ANYTHING
So..... is it somehow bricked? Just from a reboot? It was working just fine before the reboot.....
I have been searching the net and these forums for a while now and haven't found anyone with the same problem. Again, I cannot boot into ANY mode nor will ANYTHING appear on the screen for more than a moment. Holding power and volume down does nothing. When i plug it into the pc it wont recognize........ is there anything i can do??.....
Sam
Click to expand...
Click to collapse
Did you check the incoming call. If you receive calls, then it's broken touchscreen. I have such a situation a year ago.

Galaxy S Relay 4G(SGH-T699) completely bricked?

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!

Rooting a s3 galaxy smartphone stuck on logo screen?

Hey guys,
I would be really considerate if any one of you can help me with this, there have been some problems with my phone. I noticed that after using it for long hours and once the battery goes down to 20%, the screen would suddenly freeze and it would be impossible to try to turn it off or click on anything, so what i would do is leave it for some few seconds until it shuts by itself or try to take out the battery and then plug it into a charger and then it would work fine. So I didn't think that it was a serious problem but lately, the same thing happened and I took out the battery, then i tried to turn it on but it just stuck on the logo screen and it wouldn't turn on at all.Also, if i try to charge it, it would show a grey battery icon with a loading picture on it and it doesn't show the usual green battery loading, I tried taking off the battery for some time and put it back on but it's always the same problem. I also erased the cache on the recovery mode but it's always showing no sign of working. I've been wondering if I rooted my phone, would the data be erased? and is there any chance of it working afterwards or maybe I should try something else? and what is the best solution to try: rooting the phone or doing the factory reset? I don't want to loose data...
I'll be honestly so grateful if anyone can recommend me something because I tried looking everywhere for this problem but with no results.
By the way, my phone is samsung s3 gt i9300.
Thank you a lot in advance.
Best regards,

s6 edge stuck in artifacted boot loop

Hey everyone,
A couple months ago I woke up and unplugged my phone and turned it on, and it was stuck in a boot loop with an odd blue refraction in the screen. (see photos). It's a fully unlocked S6 edge (SM-G925F) bought from Credo mobile in mid 2015, and worked more or less seamlessly (no root) until that night. It wont respond to any bootup commands including force battery cutoff and recovery mode, but it will enter download mode with the screen artifacting still visible. I had to travel, so I just briefly ran Odin and installed fresh firmware, but I didn't see any difference and OEM lock was on, so i couldn't do much more. I just threw it in my bag and figured I'd work on it later, and just used the GR3 backup phone from work.
2 months later I finally got to take a look at it, and i'm stumped. At first glance i just thought it was bootloader/data corruption, but now I'm not so sure. Any ideas? dirty wall power maybe?
Thanks!
Ceu
---EDIT- Will post pictures if helpful, but the forums wont let me post links until i have 10 posts. Thanks again!----
Hi!
I know this is probably not the answer you were hoping for but I have the exact same problem and instead of opening a new, identical post, I thought I'd tag along here.
My S6 Edge worked fine this morning, did nothing unusual. Went to class, checked the time five minutes later and found my phone in a boot loop. I did not turn it off before, I didn't do anything besides put it face down on the table next to me. Recovery mode is not accessible, I can not turn it off. I used SmartSwitch (twice) and Odin (4 times, different versions) to install fresh firmware I downloaded from sammobile.com. I always get a "PASS" so it should've worked. But it doesn't. Boot loop stays, nothing I try seems to work. Can anyone help us? I do not want to buy a new phone just because this stupid thing is stuck in a random boot loop.

Categories

Resources