How To Guide Recovering from a Crash dump after updating.

Search This thread
This is my experience on recovering from an update that rebooted into a crash dump or potentially some other soft bricked state. I run a rooted NE2215 (NA/US) with Magisk (w/ modules) and the latest ROM version.

Causes: Starting with OOS12+ you can't do OTA updates then patch the boot loader in Magisk. If you do this you will be presented with a crash dump or some other unbootable state.

Recovery Steps:
  1. Power down the phone by pressing and holding the power button and releasing when it's off.
  2. Pres and hold all the buttons (Power, Vol+, and Vol-) untill it powers on.
  3. This should boot you into the previous slot with the previous version of OOS and effectively undoing the update.
If this doesn't work, then you have another issue that probably is more severe.

To properly update you need to get these two apps/apk "Oxygen Updater" and "System Update".
  1. Download the latest update (Full or Incremental) with "Oxygen Updater".
  2. Go into Magisk and disable all modules
  3. Restart the phone.
  4. Go into Magisk and restore images
  5. Install it with "System Updater".
  6. After it's finished Installing and asking you restart, don't. Instead go back into Magisk and install after OTA. Then restart.
  7. Re-enable modules after the restart and restart again.
 
  • Like
Reactions: Prant

g96818

Senior Member
Dec 27, 2014
731
302
Causes: Starting with OOS12+ you can't do OTA updates then patch the boot loader in Magisk.
yes you can.
only difference with your steps is disabling modules (which you don't have to do) and downloading the OTA file yourself. There's nothing wrong with that. You crash dumped because your phone likely downloaded a bad ota file or you didn't disable specific magisk modules that warned you to disable before updating or risk boot looping. You are still installing the ota and patching with magisk so this statement that you can't do the ota and patch with magisk is false.

+1 for giving people the directions to get out of a crash dump situation.
 
  • Like
Reactions: RealZac

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    This is my experience on recovering from an update that rebooted into a crash dump or potentially some other soft bricked state. I run a rooted NE2215 (NA/US) with Magisk (w/ modules) and the latest ROM version.

    Causes: Starting with OOS12+ you can't do OTA updates then patch the boot loader in Magisk. If you do this you will be presented with a crash dump or some other unbootable state.

    Recovery Steps:
    1. Power down the phone by pressing and holding the power button and releasing when it's off.
    2. Pres and hold all the buttons (Power, Vol+, and Vol-) untill it powers on.
    3. This should boot you into the previous slot with the previous version of OOS and effectively undoing the update.
    If this doesn't work, then you have another issue that probably is more severe.

    To properly update you need to get these two apps/apk "Oxygen Updater" and "System Update".
    1. Download the latest update (Full or Incremental) with "Oxygen Updater".
    2. Go into Magisk and disable all modules
    3. Restart the phone.
    4. Go into Magisk and restore images
    5. Install it with "System Updater".
    6. After it's finished Installing and asking you restart, don't. Instead go back into Magisk and install after OTA. Then restart.
    7. Re-enable modules after the restart and restart again.
    1
    Causes: Starting with OOS12+ you can't do OTA updates then patch the boot loader in Magisk.
    yes you can.
    only difference with your steps is disabling modules (which you don't have to do) and downloading the OTA file yourself. There's nothing wrong with that. You crash dumped because your phone likely downloaded a bad ota file or you didn't disable specific magisk modules that warned you to disable before updating or risk boot looping. You are still installing the ota and patching with magisk so this statement that you can't do the ota and patch with magisk is false.

    +1 for giving people the directions to get out of a crash dump situation.