• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Phone stuck on either battery logo or device logo!!

katries

Lurker
Aug 28, 2016
8
2
I've had a few problems with my phone before but it had always solved itself within a day but just a couple of days ago, my phone has been stuck on either the phone's battery logo or the device logo.
20160828_124726.jpg
20160828_124703.jpg

When I tried to wipe my cache via the recovery menu but it keeps on redirecting me to Odin Mode??

I've tried more than enough to remove my battery, put it back in then restart or taking out my sim card & SD card then restart or just letting it charge but it just won't boot up.

It's never happened before but it just might be that my phone is really old since it's a Galaxy Note 2 and I've been using it for 4 years now.

I don't want to fully factort reset it since I have really important things in the device, any ideas?
 

Attachments

  • 20160828_124703.jpg
    20160828_124703.jpg
    266.5 KB · Views: 239
Its called a boot loop. Let's try to get it fixed shall we.
A GT-N7100. I need about 5 more digits. Will you please boot into recovery and look at the top for a full model number. Post it if you find it.

Sorry I cant even make it to recovery because it always directs me to the odin mode and when it's on Odin mode, it just says the model is GT-N7100

but behind the battery pack, it says

Model : GT-N7100
FCC ID : A3LGT7100
SSN : -N7100GSMH

i dont know if that helps
 
Upvote 0
So it dosent make it to recovery?
What was it doing before it started acting like this?
with the device completely off try holding both voulme up & down+power for 15 sec. then release but quickly press volume up & down+power for an additional 5 more sec.,may have to try a couple times,but this might not solve the problem.

before this, it was working just as normal, laggy and freezes up sometimes which i considered normal as it was 4 years old.

also, i had charged my phone at a beach that had working sockets before this issue happened. i dont know if its just my phone thats not used to other sockets?

i tried what you told me but it still kept on looping back to the device logo
 
Upvote 0
Hi, there are about 75 different variations of the n7100. The variations depend on locale and service provider. You say you were on a beach so that narrows it down to about 73;). With the power turned off, hold volume up+home+power until you see some fine writing at the top, release. This should take you into recovery mode. Keep trying. At the top you will see a model #. Or alternatively you could tell me where you live and who your carrier is. ;)
 
Upvote 0
Hi, there are about 75 different variations of the n7100. The variations depend on locale and service provider. You say you were on a beach so that narrows it down to about 73;). With the power turned off, hold volume up+home+power until you see some fine writing at the top, release. This should take you into recovery mode. Keep trying. At the top you will see a model #. Or alternatively you could tell me where you live and who your carrier is. ;)

I tried what you did and thankfully, it directed me to recovery mode.

it says on the top:

KOT49H.N7100XXUFNL1

20160829_152643.jpg
 
Upvote 0
OK. Great job. We are nearly there. 25 left. Here is the list. This is important. This effects wireless connectivity.
2015-08-11 Taiwan (WAN) 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Morocco (MED) 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Morocco (MAT) 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Saudi Arabia 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Algeria 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Morocco (MWD) 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 South Africa 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2016-05-02 Libya 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 South Africa (Vodafone) 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Morocco 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Saudi Arabia (JED) 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Saudi Arabia 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Saudi Arabia 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 United Arab Emirates 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Nigeria 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Tunisia 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Egypt 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Tunisia 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Turkey 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Afghanistan 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Mauritania 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Kenya 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 United Arab Emirates 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Pakistan (PAK) 4.4.2 N7100XXUFNL1 N7100OJVFOD1 YES
2015-08-11 Kenya 4.4.2 N7100XXUFNL1 N7100OJVFOD1 YES
2015-04-16 Iran 4.4.2 N7100XXUFNL1 N7100OJVFOA1 YES

You could also try the wipe cache partition option. If that doesn't work then factory reset. I'm afraid any internal data will be lost unless the cache wipe gets you booted to Android.
 
Last edited:
  • Like
Reactions: Jfalls63
Upvote 0
OK. Great job. We are nearly there. 25 left. Here is the list. This is important. This effects wireless connectivity.
2015-08-11 Taiwan (WAN) 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Morocco (MED) 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Morocco (MAT) 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Saudi Arabia 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Algeria 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Morocco (MWD) 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 South Africa 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2016-05-02 Libya 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 South Africa (Vodafone) 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Morocco 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Saudi Arabia (JED) 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Saudi Arabia 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Saudi Arabia 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 United Arab Emirates 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Nigeria 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Tunisia 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Egypt 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Tunisia 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Turkey 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Afghanistan 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Mauritania 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Kenya 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 United Arab Emirates 4.4.2 N7100XXUFNL1 N7100OJVFOD1 NO
2015-08-11 Pakistan (PAK) 4.4.2 N7100XXUFNL1 N7100OJVFOD1 YES
2015-08-11 Kenya 4.4.2 N7100XXUFNL1 N7100OJVFOD1 YES
2015-04-16 Iran 4.4.2 N7100XXUFNL1 N7100OJVFOA1 YES

You could also try the wipe cache partition option. If that doesn't work then factory reset. I'm afraid any internal data will be lost unless the cache wipe gets you booted to Android.

I had to wipe the cache a few times before it finally functioned. It's more laggy than before but even I can't complain now that it's finally working again. Thank you!!
 
  • Like
Reactions: Jfalls63
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones