Latest Magisk messed up my boot. Can I recover without losing everything?

[¿GotJazz?]

Hi - I tried updating Magisk this morning, and it semi-bricked my OP7P. When I rebooted my phone, I got stuck in FastBoot Mode.

I'm running the latest Android 10 OOS.

My first step at that point was to do a fastboot boot twrp-3.4.0-0-guacamole.img to get into Recovery Mode. That worked, and I tried switching to my SLOT B to boot from.

That seemed to work at first ... but not really.

While my OP7P appeared to be booting from Slot B, it was stuck in a boot loop, with the OOS boot screen "circling electron dot" rotating very, very slowly. After about 5 minutes, I gave up on that.

So, I did another fastboot boot twrp-3.4.0-0-guacamole.img to get into Recovery Mode again, and did a backup of all the partitions (Boot, System Image, Vendor Image, Data, Modem, and EFS) and saved that off.

Now that I backed up all my previous partitions, is there a way for me to get my OP7P back to where it was before I corrupted my boot with Magisk? Can I just recover the Boot Partition from a previous TWRP backup? Or, reinstall some stock image of OOS, reinstall TWRP 3.4.0.0, and then recover some of the partitions I just backed up?

I'm going to hold off until I hear a response back ... I'm afraid if I take any other steps at this point, I could cause irreparable damage - if I haven't already.

¿GJ?

 

[ghost323]

Twrp --> flash your boot.img (with "payload dumper" it can be extracted from the full OTA update file)
Then flash twrp.zip, reboot in to twrp, flash magisk.zip (21.4 or 22), wipe dalvik cache
Reboot and provit ;-)

Ps: for magisk22, rename magisk22.apk to magisk22.zip

 

[¿GotJazz?]

Thanks, @ghost323 ! You're a lifesaver!

That is exactly the answer I was looking for, and my OP7P is operational again without any issues.

I'm bookmarking this page, and also putting some notes into my Android stuff for future reference ... Though, I hope I don't have to reference it again.

¿GJ?

 

[biglo]

Twrp --> flash your boot.img (with "payload dumper" it can be extracted from the full OTA update file)
Then flash twrp.zip, reboot in to twrp, flash magisk.zip (21.4 or 22), wipe dalvik cache
Reboot and provit ;-)

Ps: for magisk22, rename magisk22.apk to magisk22.zip

Not all super heroes wear capes! Thank you so much!

 

[naveen_reloaded]

it is asking which parttition to flash , Boot / System image./ Vendor / ramdisk..

which one to select ?

 

[naveen_reloaded]

I flashed boot.img to "boot" and flashed twrp.zip

Was on Havoc OS.

Tried to rebooting , it booted into another slot i think , didnt mount the parition. So had to reboot again .. but this time it went to bootloop again with animation.

Now i cant able to go into twrp or fastboot.

Have ti soft bricked ? Atleast took a backup when i was inside TWRP.

can someone help me ? When i boot (not turned off) , it is showing as " Unknown USB Device (Device Descriptor Request Failed)"

 

[ghost323]

Boot partition is correct. Did you reboot in twrp and then installed the magisk.zip?

 

[naveen_reloaded]

OK tried vol down and power -- it booted into twrp , but both slots dont show or mount OS parition

 

[ghost323]

Install your magisk.zip then try a restart. If you have a bootloop, go back to twrp, change the slot (a / b), install magisk.zip and restart again.

 

[ghost323]

Plan B: install your current firmware via twrp (as if you were doing an update).
Then flash twrp.zip
Then restart again directly in twrp
Then flash magisk.zip
Then delete dalvik cache
Then restart into the system

Good luck

 

[naveen_reloaded]

i cant mount or its not showing "sdcard"

 

[naveen_reloaded]

its not showing sdcard , also you said to flash the boot.img , when i did it asked me where .. I select "Boot" parititon , is that correct ?

 

[naveen_reloaded]

I think i am in X parition where its not showing SDcard content or data ..

really bad day.. didint think magisk would wreak the phone for so many. Atleast they should stop this upgrade for time being.

 

[ghost323]

Sorry i'm @ work...
WTF?!
Have you already tried a USB stick? Maybe this will be shown to you if you have the right cable.

 

[naveen_reloaded]

Thanks for the replies.. Even from work..
I dont even know which partition i am in. I tried to reboot into recovery and its working. From there i went to change from slot a to b and its showing
unable to mount /data/media/TWRP/ .twrps

Problem is i cant able to mount "data".

 

[naveen_reloaded]

also dm-verity is not disabled in my op7pro , is that causing any issue ?
For now it seems TWRP doesnt know where "data" is , thats is what i am thinking.

Shall i flash twrp again using "tool all in one" ?

 

[naveen_reloaded]

when i try to reboot into "bootloader" , it doesnt show "bootloader version" , Baseband version.

just putting it here to identify the issue.

 

[naveen_reloaded]

when booting up into twrp , its not asking for my PIN , so its not mouting the normal parition. it is going into some other partition from which it cant mount data/media - sdcard because of encryption.. my guess..

 

[naveen_reloaded]

I was able to pull the recovery.log.. please let me know if that could be any help

 

[naveen_reloaded]

I think its the partition which is not loading,i think just dirty flashing the ROM should work , but for that i need to mount the data/media/sdcard or internal storage right ? Or will not help ?

I once again flashed TWRP through "TAIO"tool and it flashed on both slot A and slot B.

Looking into log here :

I:Switching packages (splash)
=> Linking mtab
I:Setting active slot B
=> Processing /etc/twrp.fstab for SAR-detection
I:Reading /etc/twrp.fstab
I:Done processing fstab files
I:SAR-DETECT: SAR System detected
=> Processing /etc/twrp.fstab
I:Reading /etc/twrp.fstab
I:Processing '/boot'
I:Processing '/system'
I:Created '/system' folder.
I:Processing '/system_image'
I:Processing '/vendor'
I:Processing '/vendor_image'
I:Processing '/metadata'
I:Processing '/data'
I:FBE contents 'ice', filenames 'aes-256-cts'
I:Flag identified for processing, but later unmatched: 36
I:Processing '/firmware'
I:Created '/firmware' folder.
I:Processing '/misc'
I:Processing '/modem'
I:Processing '/bluetooth'
I:Processing '/dsp'
I:Processing '/efs1'
I:Processing '/efs2'
I:Processing '/efsc'
I:Processing '/efsg'
I:Processing '/op2'
I:Created '/op2' folder.
I:Processing '/usbstorage'
I:Created '/usbstorage' folder.
I:Done processing fstab files
I:Setting up '/data' as data/media emulated storage.
I:Can't probe device /dev/block/sda19
I:Unable to mount '/data'
I:Actual block device: '/dev/block/sda19', current file system: 'ext4'
I:Can't probe device /dev/block/sda19
I:Unable to mount '/data'
I:Actual block device: '/dev/block/sda19', current file system: 'ext4'
I:Backup folder set to '/data/media/TWRP/BACKUPS/b2562ef9'
I:Settings storage is '/data/media'
libc: Unable to set property "ro.crypto.state" to "encrypted": error code: 0xb
libc: Unable to set property "ro.crypto.type" to "file": error code: 0xb
e4crypt_mount_metadata_encrypted: /data 0
key_dir/key: /metadata/vold/metadata_encryption/key
Key exists, using: /metadata/vold/metadata_encryption/key
Using Keymaster HAL: 4 from QTI for encryption.  Security level: TRUSTED_ENVIRONMENT, HAL: android.hardware.keymaster@4.0::IKeymasterDevice/default
begin failed, code -62
Upgrading key in memory only: /metadata/vold/metadata_encryption/key
upgrade_key failed, code -38
I:Unable to decrypt metadata encryption
libc: Unable to set property "ro.crypto.state" to "encrypted": error code: 0xb
libc: Unable to set property "ro.crypto.type" to "block": error code: 0xb
E:Unexpected value for crypto key location
E:Error getting crypt footer and key
Updating partition details...
I:App found at '/system_root/system/priv-app/twrpapp'
I:Can't probe device /dev/block/sda19
I:Unable to mount '/data'
I:Actual block device: '/dev/block/sda19', current file system: 'ext4'
I:Unable to mount '/usbstorage'
I:Actual block device: '', current file system: 'vfat'
...done
I:Can't probe device /dev/block/sda19
I:Unable to mount '/data'
I:Actual block device: '/dev/block/sda19', current file system: 'ext4'
Unable to mount storage
I:Unmounting main partitions...