Galaxy s2 with official rom stuck on boot. Goes to setup only on charging.

[Android Central Question]

Hi I have a serious problem with my galaxy s2 that stack on startup. I have put only the official android update, several years ago, deployed from Samsung(jelly bean).I tried flashing with Odin,got success message but nothing changed.the strange is that I can only go into setup mode when it's on charging mode and only through electricity socket and not through USB cable. Any ideas would be much appreciated, I don't know what other alternatives can I try, i have already try reset option, but got the same problem.
Is there any possibility buying a new battery to solve the problem?
Thanks a lot.

 

[Njellybean]

Sorry for the error on the title can't edit it after posting!

 

[B. Diddy]

Welcome to Android Central! I corrected the typos in your title. I'm not sure how much I can help, but can clarify -- what setup mode are you referring to (the one that only shows up when you're plugged into a wall outlet)? Are you talking about Download Mode, or the Android Recovery Menu?

 

[Njellybean]

Hi,thanks for the response,sorry, I meant the recovery mode,the one that is displayed with vol.up&down pressed with power button also pressed.but right now I can't display it at all
only the download option is displayed.
When in wall outlet it seems to be in an endless loop between battery icon and android icon.
When not in a wall outlet it's like dead.

P.S. is it possible to try installing cyanogen rom through Odin (odin seems to be the only communication i had with the world!!! In my previous attempts)? If it is technical possible, do you think it's worth trying or is gonna mess things even more?

thanks a lot

 

[B. Diddy]

If you're only able to do anything when plugged into an outlet, my guess is that the battery is failing -- try a new or different battery.

Sorry, but I don't have any experience with Cyanogen or using Odin. Hopefully someone else can weigh in!

 

[Njellybean]

Hi thank you very much for the responses. I'll do that with the battery and see...

Any other ideas are welcome

 

[Njellybean]

The problem was indeed the battery! Got a new one and the firmware update was finished and the phone is back & alive! Too pitty I had wiped everything out.
It's a pitty that such a mainstream OS(?) or the manufacturer(?, I'm not sure who is responsible for these failures to handle them) of the device hadn't predict a special error code for battery failure as on PCs for example there are many system errors that can be read through different beeps sequence or through different led lights. It would save my data.
Anyway...