Android Enthusiasts Stack Exchange is a question and answer site for enthusiasts and power users of the Android operating system. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Okay so I've had my s3 for quiet a while but never actually used it properly until today.

First issue was it didn't get past the samsung boot logo, it showed the carriers boot logo( three UK) followed by the samsung one but didn't go any further.

I thought oh crap I guess it's time for a reset. I do the usual factory reset through recovery mode. But noticed that it started saying E:/ removed or something.

Now not only no network carrier to be seen but stuck in samsung i9300 screen. Boot loop.

Next action fire up Odin and see if I can use the link on XDA ( to get back and downloaded THREE different firmware as I wasn't sure of which one to download as I couldn't access my settings.

Next thing I know Odin says pass but it is on this constant loop of green android man and samsung!!! I removed the cable and closed Odin but still stuck on it. I can't access recovery mode only download mode.

What do I do guys?!

P.s all this time I had no root installed

share|improve this question
I don't understand why you kept the phone if it never worked. And what are you flashing with ODIN, are you sure you flashed the correct firmware? – Ryan Conrad Feb 23 '13 at 4:55
First issue was it didn't get past the samsung boot logo that's not the first issue, first issue is what were you last doing before it broke. Phones don't just break for no reason, they don't just suddenly get into boot loop unless you're doing something else. Had you have installed a custom ROM? Were there an OTA update? Did you had an unproper shutdown while doing these? Is it a new phone or a used one when you bought it? – Lie Ryan Feb 23 '13 at 6:05
@RyanConrad I kept the phone because I never had the chance to use it properly. – Anish B Feb 23 '13 at 10:18
@LieRyan Its a new phone, I didn't know if there was an OTA update as it wasn't used for over 3 months. No custom rom was installed at all. I don't remember doing any improper shutdowns however I thought if there was that Samsung would have some way of recognising this...? – Anish B Feb 23 '13 at 10:20
It wont boot now because you probably flashed the wrong version. You need to flash the correct version. – Ryan Conrad Feb 23 '13 at 14:42

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.