Bootloop after SuperSU update

Search This thread

Flapjack

Senior Member
Aug 17, 2007
1,273
110
Samsung Galaxy S23 Ultra
Hopefully someone can help. There was an update on Google Play today for the Chainfire SuperSU. I ran the update, clicked the message that I needed to update the binary, chose TWRP (I'm on 2.8.7.0), and the phone rebooted. After booting, it went into recovery, tried to run something (I wish I had written it down), and rebooted again. It did this again and again, looping about 10 times before I finally held the power button. At that point, the phone tried to boot normally, but never went past the boot animation (waited about 30 minutes).

I can still get into recovery, luckily... I just don't know what I should do at this point. I am running the stock MM, just debloated.
 

jason2678

Senior Member
Jul 1, 2014
1,008
552
St. Paul
Before you do anything else, try wiping cache and dalvik from TWRP. Sometimes you get lucky and that's all it takes to stop a bootloop.
 

Flapjack

Senior Member
Aug 17, 2007
1,273
110
Samsung Galaxy S23 Ultra
I was able to fix the issue by booting into recovery, copying the latest supersu zip to internal storage via MTP, and installing the zip manually. Once that was done, the phone finally booted all the way.

From which SuperSU version did you run the update?
The update was from the newest one in the store. It came up just like any other app update does. The funny thing is, when I went back to look at the latest version in Play, it was definitely older. I wonder if it was pulled.

Before you do anything else, try wiping cache and dalvik from TWRP. Sometimes you get lucky and that's all it takes to stop a bootloop.
I had tried all that. It's usually the first thing I do when I have issues like that.
 
  • Like
Reactions: jason2678

woshinoob

New member
Mar 11, 2016
3
0
Hey, i am using a note 4 . Currently my phone is in recovery mode and is boot looping. It would boot for 2 secs then reboot again. i cant exit the recovery mode at all the clear any cache or stuff. I may have misclicked the normal boot and clicked the TWRP after updating supersu. Is there a fix for it?
 

Flapjack

Senior Member
Aug 17, 2007
1,273
110
Samsung Galaxy S23 Ultra
I guess I'm not sure what you mean. You can't get "past" recovery mode? When you reboot (without button intervention), what happens? Does it try to load the OS partition, then reboot? Can you press whatever button combo the Note 4 has to get into recovery (as opposed to booting the phone normally?

Not sure how much help I can be, as I've never had a Note. I got off the Samsung train after the S4. I've had enough of locked bootloaders, bloatware, and crappy UIs. It's a shame, too.... as I really like their hardware.
 

woshinoob

New member
Mar 11, 2016
3
0
I guess I'm not sure what you mean. You can't get "past" recovery mode? When you reboot (without button intervention), what happens? Does it try to load the OS partition, then reboot? Can you press whatever button combo the Note 4 has to get into recovery (as opposed to booting the phone normally?

Not sure how much help I can be, as I've never had a Note. I got off the Samsung train after the S4. I've had enough of locked bootloaders, bloatware, and crappy UIs. It's a shame, too.... as I really like their hardware.

Hey man tks for replying so promptly though. I think i know what went wrong. Just that i don't know how to fix it. My phone is now recovery booting through TWRP. But i don't remember having TWRP. Is there a way to change the boot to normal?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    I was able to fix the issue by booting into recovery, copying the latest supersu zip to internal storage via MTP, and installing the zip manually. Once that was done, the phone finally booted all the way.

    From which SuperSU version did you run the update?
    The update was from the newest one in the store. It came up just like any other app update does. The funny thing is, when I went back to look at the latest version in Play, it was definitely older. I wonder if it was pulled.

    Before you do anything else, try wiping cache and dalvik from TWRP. Sometimes you get lucky and that's all it takes to stop a bootloop.
    I had tried all that. It's usually the first thing I do when I have issues like that.