Stuck in a reboot loop - T-Mobile Samsung Galaxy S6 Edge+

It's in a loop of starting up, loading to the home screen and then shutting down a few seconds later. While booting, in red text, the words "Kernel is not seandroid enforcing" is in the upper left corner. I tried to root it and it didn't work. I've tried a factory reset and still nothing. Now it takes me to the setup screen, yet still looping. I don't know what else to do and I need help. I've later found out that the text is normal, but since it's appeared, it is in constant rebooting.
Currently, I have a G928T firmware downloading from Sammobile which I hope I can use Odin to recover my phone. That's still got an hour left and I don't know if it will even work.
If there's anything else I can do, please say so, and if the firmware downloading is the only option, could you describe the process? I'd prefer that I not mess that up somehow.
After posting this (in the correct forum this time), I've calmed down enough to realize that there is another thread about this incident. I'll try the solution posted there for now.
That solution worked. I guess there's really not much need for this thread anymore, but if someone else were to have the same issue and find this thread, click here to go to the thread that fixed it.

As I read through your post I was getting ready to go and retrieve the copies of the files that I have and post them for you but I see that you've corrected your issues one thing I'd like to say to everyone if you do get into a situation where the phone is stuck since we don't have the battery pool anymore if you press the volume up/down home and power button the phone will briefly restart and then you can decide if you want to go into download mode from there or recovery or just let it try to boot up. Put that helps glad you got your issue fixed brother

Related

[Q] HELP!! New stock nexus ui crashed, stuck at boot animation

Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.
This is the hspa version.
svntsvn said:
Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.
Click to expand...
Click to collapse
The android icon you're referring to sounds like the stock recovery. In order to flash a ROM (even stock) from recovery mode, you'll need to load a custom recovery. This requires the device to be unlocked.
Not very often a stock setup needs to be restored. Generally, with the stock setup, only the /data partition is wiped (revert to factory default) and the issues are cleared. Not sure why a stock setup would need to be restore.
If you're still going to pursue reloading the system, without access to the normal android mode, the best route will be using fastboot. This can be done on a mac and the fastboot commands should be the same.
Hope that helps get a start!
This happened me earlier. I was able to factory reset it, which, unfortunately really annoyed me because I hadn't saved a backup..
Before the "Google" logo shows up, press and hold the power button and the volume up and down buttons.
Then go into recovery mode using the volume buttons.
When it reboots, you get that Droid with the hazard sign (which I know you're at, but just for the sake of others who need help) all you have to do is hold down the power button and WHILE it's held, press the volume up or down button and move to "Factory Reset". When you hold down the power button and press the volume rocker, a little menu will appear. It should only take a few minutes then.
Hope this helps. Apparently this is a WiFi issue. I'll definitely be keeping backups as of now..
I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.
svntsvn said:
I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.
Click to expand...
Click to collapse
I had the exact same problem happen last night with UI crashing and then the getting stuck at the boot animation. I was desperately searching online, looking to find a solution that didn't involve rebooting to factory setting and came across this post and did exactly what you did and it WORKED, very strange, I really wanna know what caused that!!!!
I've had the same problem with my Galaxy Nexus. I received it on December 21st, with stock 4.0.1 build. No root or unlock attempt at any time. On January 2nd I experienced this problems (UI process crash, screen not responding, reboot and stuck in boot animation).
The only solution was to do a factory reset and start over.
On January 10th same problem, same solution. Second factory reset.
I got the 4.0.2 OTA just two days after that. I thought that would resolve the problem. The phone seemed more stable, with less FC's and no trace of the UI crash. Indeed it lasted long...
Exactly until January 24th when I picked up the phone and seemed in the sleep of dead. Removed the battery, restarted the phone... and stuck in the boot animation.
Do you have any advice? Should I return the phone? Aside from those specific problems I am quite happy with the SGN and Android 4 in general. And I use it quite a lot (I have a very long train commute) without other problems.
Again...
It happened again!!
I don't know what to do anymore, this is not a usable phone when I have to reinstall and reconfigure every 3 weeks.
I may have found the problem
Well, not me exactly, but this bug report seems to fit the problem and the charging workaround. Seems to be a problem the file used to store the battery stats and draw the charge graph.
It also fits my usage (I try not to charge it up until 100%).
I can't post links to the forum, the issue is id number 24518 which you can find in code.google.com/p/android/

Useful advice for scenario: Blank TWRP + Bootloop After Rom Flash.

I had almost given up on my phone and was coming here to get some help.
As I was writing up this thread I had left my phone on the blank screen I'm about to describe.
then i noticed out of the corner of my eye the screen light up.
So my advice is, if you ever have this scenario happen it may take over 20 minutes for TWRP to even load.
This may not be something that can be duplicated, but hopefully it can be useful for someone who would panic about this like myself and keep trying things.
(I have a sneaky suspicion about my SD card now, I believe it may have become corrupted during the install.. breaking the rom.. and then making the phone hang while loading twrp.)
Mate - mt1-u06
(Ab)using TWRP v2.8.1.0
Thanks
So today I wanted to try out this:
http://forum.xda-developers.com/ascend-p6/ascend-mate/rom-omnirom-t3092487
and when I flashed it through twrp I did the install it was all successful but I forgot to wipe before rebooting (woops) So i thought hmm maybe it didn't need it,
so left it for a few minutes, realized this is a bootloop and needed to be done again.
So I was like okay I'll just shut it off and go back into recovery.
Did it like I normally would (power and the volume) and my heart kinda sank when I got a black screen (back-lit so you could tell it was still on).
weird usually it loads...
powered it off and let it load normally again to see if it was just taking a while to setup maybe to just get into the OS.
Nope 1 hour later nothing.
Have tried getting into recovery a million times but its still blank.
and to get the nooby stuff out of the way:
Fully charged before I did it and It wouldn't even turn on if it wasn't so that's kind obvious.
Mate - mt1-u06
using TWRP v2.8.1.0
Click to expand...
Click to collapse

Note 2 boot load loop fix - cause System Memory full

Hi everyone. This is the first time ive posted anything on here. I will try to fully describe my problem that i really need help to fix.
My wife got my old Note 2 is rooted and she got my
Dad's old unrooted Note 2. After deciding that she didnt want a rooted phone she decided to use my father's unrooted phone. Due to apps updating and the internal memory getting full she ingored the warning message not really realising the outcome. The phone eventually shut itself down and is stuck on the Samsung logo (boot loop). So i gave her my old rooted phone back because she said that it just died. The same happened to the rooted phone too.
I asked before what she did and i was told nothing it just died. So i had nothing to go on. It wasn't until a week later when I tried to sort the problem out she said the System Memory was getting full and a message came up warning of this. So now I believe the problem is that the on board memory has got full and the phone seized. Much like what happens to a PC when the main hard drive gets full!
When i attempt to boot the phone up the Samsung logo show and stays on, never booting up. This happens with both phones. When i hold the Home key, Power button and Up volume switch. The phone loads the first Part of the boot up and at the moment it goes to the system screen it goes blank for a split second and back to the start of the boot. No matter how many times i try it fails. So I can't Factory reset or erase anything because i can get to it that screen.
So I try something else. I press the Home button, Power button and the Down on the volume to access the Download mode. This works fine. So i used Odin to try to put Rom onto the phone hoping this will solve the problem. Both phones connects to Odin alright and I can set up ready to load a rom onto it, however when i press start on Odmin to do its job everthing starts ok but then it goes red with a Failed error message. This happens when i try this on both phones, I seem to be stuck no knowing what to do. I have tried using all the ports on my laptop (window 7) and that makes no difference. The same happens on both devices.
I think i need to clear the memory somehow but have no idea how to do it when i can only access Download mode. I would be very grateful for any help on this but if all else fail I will try to build up static on a ballon and see if putting the near will wipe the memory, lol. Only joking. Im desperate to sort this out.
Any ideas?
try to flash twrp with Odin and download mode. Then enter recovery, connect it to PC and make some space.
But I really doubt it, apps won't install even when you have 500Mb free, so I think it might be hardware problem

Galaxy tab S T-705 is stuck in boot screen and can't get into recovery

Hello, everyone. A couple of days ago, I dropped my tab s while I was sleeping. When I woke up, I found that it was stuck in a boot loop. Since, I've had this problem twice before, I wasn't worried since the problem solved itself by waiting it out. However, this time it is just stuck in this screen
imgur . com/a/sLA22(can't post links, sorry. Just delete that space after imgur. ) . I've tried to access the recovery mode to no avail, so I googled and tried to install TWRP. To do that, I've installed Odin and downloaded twrp tar file for my lte edition tablet. I believe that the installation went smoothly, imgur . com/a/JlVvz but no matter what I do, I just can't get into recovery using the volume up, home button, and power button combination. I have even flashed twrp multiple times. Please help me because I have no idea what to do.
P.S: My tablet runs stock marshmallow.
I solved it. I did more Googling and found someone who suggested to hit the area near the power button; I did just that in addition to taking off the SD card for no reason and let my tab charge to 100%. So, if you can't get into recovery, and your phone is stuck in the Samsung tab s screen, try what I did.

S4 mini bootloops on first startup screen

hi, my galaxy s4 mini just went off suddenly and refused to come up.
after several hours of trying everything possible to get it started,......it still didnt.
well, eventually it started to come up only when i plugged in the charger,.....it brings up the about to charge battery icon and then proceeds to power on by itself instead of just charging,
well this ends up in a bootloop at the first start up screen..........cant even stay up enough to get into recovery.
odin flashes/installs(Tried installing everything on my system with a .tar format out of frustration) wont complete because it doesnt get to enter the recovery mode.
Im just out of ideas..... please i need assistance.
by the way i have tried applying every solution ive come across on similar threads all to no avail.
for the record......i can only enter download mode and nothing else but bootloop
please i am in dire need of some assistance .......please anyone
please guys......im incommunicado at the moment
im literately sitting and looking at my screen waiting for someone anyone......please
Donbuzizie said:
im literately sitting and looking at my screen waiting for someone anyone......please
Click to expand...
Click to collapse
Are you saying download mode works properly?
power button could be stuck on, had you just pressed it when it happened?
download mode works very well,
I would have looked into the power button if it didnt.
power button is good
Donbuzizie said:
hi, my galaxy s4 mini just went off suddenly and refused to come up.
after several hours of trying everything possible to get it started,......it still didnt.
well, eventually it started to come up only when i plugged in the charger,.....it brings up the about to charge battery icon and then proceeds to power on by itself instead of just charging,
well this ends up in a bootloop at the first start up screen..........cant even stay up enough to get into recovery.
odin flashes/installs(Tried installing everything on my system with a .tar format out of frustration) wont complete because it doesnt get to enter the recovery mode.
Im just out of ideas..... please i need assistance.
by the way i have tried applying every solution ive come across on similar threads all to no avail.
for the record......i can only enter download mode and nothing else but bootloop
please i am in dire need of some assistance .......please anyone
Click to expand...
Click to collapse
Not the only one with this issue. Also looking around for a solution :/. Tried Removing the power button thinking that could be stuck and causing the loop(other people tried it and it worked for them but no luck my side)
How many years your phone have? Because mine, after 4 years of great work, suddenly went off from nothing like yours, and since that i've seen only some tries starting up well but didn't succeed. The day after, the phone didn't light up anymore and after 3 days of BSOD, lookin' for the solution on i don't even know how many topics online, i've decided to let him rest in peace and buy a new one. To me, there are timers inside phones that make them die after some time... maybe is only a my opinion, but it's strange that phones just shut off from nothing and then there is nothin' more to do. I only didn't tried the debrick.img method because i don't have a 16GB microSD card.

Categories

Resources