I'm having problems getting my phone past the bootup screen. It first loads the logo then goes to the animated logo then the rethink possible animation and then finally gets stuck on the glowing samsung logo. It then shuts off and redoes the loop a couple of times until it stops with the battery charge up screen and freezes there until I remove the battery.
History: Purchased an att phone for the mb to replace my original phones because it had the insane chip. Had to root it to be able to unlock the phone with my carrier(telus). Since I was in it I flash the DN4 custom rom and everything needed into the phone. The phone functioned fine for about a month and then frequent freezes and restarts started happening. Near the end, the phone was stuck in a boot loop, loading into the DN4 animation boot screen then shutting itself off then on again to endlessly repeat the loop.
Present: At first I was able to get into TWRP and tried some things in there but nothing happened. When there I notice it stated "internal memory 0"-not sure if this means anything.
I was able to flash the saved recovery file from TWRP. Once I did that I could no longer go in TWRP and now have to use the samsung install/recovery.
I have since flashed the stock rom several times with odin and also wiped data/factory reset many times still does the same in bootup. Tried flashing TWRP into phone using odin 3.07 but failed.
What should be my next move? Pretty new at this so I may be missing something very simple or perhaps a dead phone???
Finally got the phone to boot up and run fine. It seems everything was good except the battery was acting up.
Next step is to get the battery to charge when phone is off.
I'll post this question in new thread.
Related
So, I flashed yesterdays CM10.2 and had no problems, up until today. I was in class, using twitter, set the phone down, and looked back at it 5 minutes later to find it shut off. I restarted it, figured no big deal, it turned off again. I thought there was a problem with that nightly so I flashed back an older, more stable one(still 10.2). It booted up, and shut off again. Now, though, the phone boots up, shows Samsung, then shows the GS3 and CM logo, then just goes into a loop from there. I went to recovery and tried to wipe, which, oddly, the phone restarted again. Luckily I was able to get in and wipe data before a new reboot, but even that didn't fix it. I rebooted into recovery again, and it said something like "root access available" and asked me if I would like to use root, which I didn't get the chance to fully read because it restarted again. When I am able to successfully boot into recovery though, I get a warning saying "no file_contexts", this could be it?
I've already tried to flash back stock Touchwiz with Odin, but it keeps failing to do so. Any help with this?
EDIT: After successfully booting up a CM10.1 backup, I've begun to believe the power button is broke, because the power menu will randomly popup, followed by a shut down.
It's called SDS sudden death syndrome it's very common on the S3. It's a failure of the power button. It's a defect. If your phone is newer than a year old put it back to stock and take it to sprint.
Remember search is your best friend, Have a great day!
I have been having some issues. I know their are countless boot loop threads and have read and tried most of them.
To start off I have re flashed to newest 5.0.1 firmware. Odin will complete and show me a pass. When it reboots it will get half way through the android boot and just stop and reboots.
Tried the recovery wipe and clear cache
The question is can a bad battery throw signs that seem like a bootloop. Unplugged it will just loop the Samsung logo. If I plug it in it will bring up the Samsung logo and reboot to battery charge symbol.
I can only access the recovery when it's plugged in also. If it's not plugged in it will bring up the "booting recovery" for a second and then reboot to Samsung screen.
I don't have an extra battery to try but want to know if that would cause this issue.
update
Even though I didn't get any help I ended up changing the battery and it booted right up. Another saved note 4. ???
I was playing pokemon go and I got a facebook messenger message, and my phone just crashed and started boot looping at the Galaxy note ii screen. I tried going into the recovery and deleting the cache and factory resetting it, tried flashing it with ODIN, and nothing seems to be fixing it. I've tried flashing it to the stock rom too, but that seemed to make things worse? Now half the time when I try and turn it on it it wont turn on unless I plug it in or remove and put back the battery, when I try charging it when it's off it turns on and I can see the battery screen, but it freezes either when loading or when the animation plays. There's no red light and I'm not even sure it's charging.
I can get to the CWM menu and the recovery menu, I did have the Nandroid backup files but it seems like I mistakenly deleted it, so that's an option. I tried flashing it with different firmwares and it doesn't seem to make a difference. The first time I flash it it usually goes to the T-Mobile splash screen, which plays the little animation and sound but stays at that screen. Any Ideas?
I tried reflashing it another few times and now I actually got into the setup screen and got to the home screen. It charges somewhat normally but it still boot loops when I start it. When I plug the charger in when it's looping it boots fully and I got to the point where I installed an update. Not I'm stuck in a loop on the T-mobile splash
Try a new battery.
Bell-wether said:
I was playing pokemon go and I got a facebook messenger message, and my phone just crashed and started boot looping at the Galaxy note ii screen. I tried going into the recovery and deleting the cache and factory resetting it, tried flashing it with ODIN, and nothing seems to be fixing it. I've tried flashing it to the stock rom too, but that seemed to make things worse? Now half the time when I try and turn it on it it wont turn on unless I plug it in or remove and put back the battery, when I try charging it when it's off it turns on and I can see the battery screen, but it freezes either when loading or when the animation plays. There's no red light and I'm not even sure it's charging.
I can get to the CWM menu and the recovery menu, I did have the Nandroid backup files but it seems like I mistakenly deleted it, so that's an option. I tried flashing it with different firmwares and it doesn't seem to make a difference. The first time I flash it it usually goes to the T-Mobile splash screen, which plays the little animation and sound but stays at that screen. Any Ideas?
Click to expand...
Click to collapse
Did you try Samsung Kies' emergency recovery option yet?
Hey guys,
So I've been running on stock EPD1 and everything had been running smoothly. Last night my phone randomly shut down, even though it was at full battery. After trying to restart it, I got stuck in almost a boot loop. It would boot, and during the Samsung animation, it would freeze and restart. This would happen twice until the phone gave up I guess and the phone stays at a black screen with either a constant blue LED, or a blinking whitish-purple LED. I have tried using ODIN to flash back to stock EPD1 and EPF1. Both were successful in ODIN, but didn't solve anything. I can flash TWRP, but flashing any ROMs doesn't help. Wiping Data, System, Cache, and formatting hasn't done anything as well. I also used the Smart Switch and Kies emergency software recovery and initialization features. Again, both said they were successful, but didn't change anything. Sometimes the boot gets to the point where it says "Android is optimizing apps," but once that finishes, it crashes again. Am I 100% screwed? Thanks to anyone that can offer some advice.
Small update: After using the emergency recovery feature in Kies once more, the phone booted to the green "Android is starting..." screen and it counted through 35 apps and said it was starting. It crashed at that point. Not sure if that's progress.
i followed this guide
teamandroid.com/2016/03/08/update-tmobile-galaxy-note-2-t889-android-601-resurrection-remix-marshmallow-custom-rom/2/
and it worked perfectly until yesterday
the other day i looked at my phone and it formatted and restarted on its own. i didnt really lose much.
so i accepted it and reset up all my apps and such, and then when my phone died and i charged it
it got stuck in boot loop forever
i tried wiping both cache and reboot recovery it skips boot loop long enough to load up but as soon as i see my homescreen for a second it boot loops again.
so then i tried completely formatting the phone over which worked until this morning when i woke up my phone was dead. swapped batteries and turned it on. booom boot loop again.
is there any advice on what i should do?
im able to format it and get it working again if something needs installed etc
but i want to stop this from happening again
Q: is it possible that a certain app i downloaded is forcing the boot loop? i dont see why it would because ive had all the same apps for months and it just happened out of no where.
i appreciate any help, id just like to know why in the world its happening, and what the best course of action would be
im thinking maybe restore it back to factory firmware and unrooting and starting the process all over again
i seen something for 7.1 would that be better?