Magisk patched recovery boot freeze - Huawei P20 Pro Questions & Answers

I somehow managed a while back to patch EMUI 9.10.387 with Magisk and got it to boot every time with the patched image without having to press power + vol+. All was fine...
Then, I stupidly updated Magisk modules (running v23) and pressed "reboot now" after the upgrade instead of powering off and rebooting. The phone went into a bootloop then I managed to boot to erecovery without recovering the phone. After that the phone booted normally BUT without magisk.
Since then, I have flashed several times the recovery (fastboot flash recovery_ramdisk xxx") with previously working recovery_ramdisk images. After flashing, when holding power + vol+ the phone displays the "short" warning message (there is a long one displaying options) boots but then gets stuck at the Huawei logo.
Now I can only boot the phone without holding vol+ and then it does boot but without magisk.
Any idea about what happened and how to get magisk back?

I forgot to add that strangely all standard Huawei apps I had removed (pm uninstall) are back: mirror, huawei wallet...etc.

I think I found the culprit. Since the issue appeared after updating magisk, I assume one module must have caused the issue. I found a guide on how to delete magisk modules from TWRP (google it).
I flashed TWRP, booted into TWRP and used the file manager. One issue: data is encrypted and so the folders displayed garbage AND instead of deleting /data/adb/modules I deleted a bunch of folders in /data/adb...
Once done I rebooted and reinstalled Magisk: it asked to install more stuff, confirmed and rebooted. All fine.
Don't touch a working system!

Related

[Q] Bricked after TWRP backup?

Following a YouTube video, code 4dwguHoxTvo, I think I might have bricked my tablet.
I ran the script provided at rootjunkysdl, got USB drivers working, and booted into TWRP recovery. I made a backup, but the guy in the video doesn't mention that you need pico gapps until he's already doing it. So I rebooted to copy over pico and now I'm in a reboot loop. "=> Normal boot" with the Amazon logo.
On bootup it shows up in device manager under Other as "MT65xx Preloader", then disappears when it reboots again.
If I hold power and both volume buttons I get "=> Fastboot mode..." but I don't know if I can do anything w/ that.
How did this happen if I didn't flash anything, just backed up?

Z3C does not have a device name anymore in the twrp

I have the weird problem, that my device seems to have no device name anymore, which causes that when I am trying to install a rom it tells me:
"This package is for device: D5803, D5833, z3c, aries; this device is ."
What I tried to fix it:
Trying several twrp kernels (different versions), did not change anything except that on some versions it said that my device is called "" (as device name only two question marks were shown instead of nothing)
Flashing again the kernel I used before and trying to install the old rom, which caused the same error message
Trying many other kernels, including the 3 latest versions of nailyk, the latest kernel directly from twrp, the kernel included in omnirom zip
I tried to flash again the default sony rom via Emma. Flashing of the default worked and I was able to use it, but as soon as I flashed again a twrp rom my device did put out the error message when I tried to install a rom.
What did I do before that happened:
I tried to flash carbonrom (https://get.carbonrom.org/device-z3c.html) onto the device, the version which was released on the 10th April (seems to have been deleted), the recovery menu did not pop up it just restarted several times (I should mention here, that I was never able to boot into the recovery via keys or adb (just the normal system did boot up when I used the command). I only were able to enter the recovery on other kernel images, when no system was installed and the recovery just popped up). So I tried to flash the recovery of the version which was released on the 5th of April, it did change nothing.
Then I tried installing omnirom (https://forum.xda-developers.com/z3-compact/orig-development/oreo-unofficial-omnirom-t3696536) using the kernel from "https://releases.nailyk.fr/twrp/". I finally was able to boot into the recovery and to install omnirom. It worked perfectly, but I forgot to install the gapps, so I reflashed the kernel (because of the boot into recovery problems I mentioned before, to get back into the recovery). When I tried to install the gapps nano, after I reinstalled omnirom it said, that my architecture was not supported (I downloaded the right one (arm 32bit)). Then I tried to install gapps stock. Same error. I read online that it was a bug of newer twrp, which caused that problems on some systems. So I tried a few versions of nailyks kernel and the version 2017-11-21 installed my gapps and I was able to flash them. At that point I tried to flash carbonrom via nailyks kernel (I was able to install the 5th April version. The 10th April version had an endless installation (actually I think the real installation never did start)) and then using the included kernel from the zip to boot. And it did not boot. So I flashed again nailyks kernel. I think after that the problem happened (I am not absolutely sure if I tried something else before that happened (I am forgetting many things)).
Also I shut mention that I wiped Dalvik / ART Cache, System, Cache, Data Internal Storage two times instead of just Dalvik / ART Cache
About carbonrom, that build was faulty. It's been fixed with the newer one.
Which keys do you press to boot into recovery?
marcogiannetta said:
About carbonrom, that build was faulty. It's been fixed with the newer one.
Which keys do you press to boot into recovery?
Click to expand...
Click to collapse
I tried the volume up as well as the volume down button several times as soon as the notification light turned purple. I even tested the camera button. It never booted into recovery mode. And also when I tried entering the recovery via adb I had no luck. It just rebooted.
00pflaume said:
I tried the volume up as well as the volume down button several times as soon as the notification light turned purple. I even tested the camera button. It never booted into recovery mode. And also when I tried entering the recovery via adb I had no luck. It just rebooted.
Click to expand...
Click to collapse
Try to completely shutdown your phone (press power + volume up until it vibrates three to four times), press power + volume down until it vibrates, then release power button. TWRP screen should appear.
That's the way I've been entering TWRP since I unlocked my boootloader.
marcogiannetta said:
Try to completely shutdown your phone (press power + volume up until it vibrates three to four times), press power + volume down until it vibrates, then release power button. TWRP screen should appear.
That's the way I've been entering TWRP since I unlocked my boootloader.
Click to expand...
Click to collapse
Also with that tip I am unable to boot into recovery. I noticed that the notification light turns from purple to orange, before it restarts (it might just be restarting because no os is installed right now)
00pflaume said:
Also with that tip I am unable to boot into recovery. I noticed that the notification light turns from purple to orange, before it restarts (it might just be restarting because no os is installed right now)
Click to expand...
Click to collapse
That's really weird. How do you flash recovery?
There are two ways:
-fastboot flash recovery recovery.img
-fastboot flash fotakernel recovery.img
I don't remember the one I used, but you could try both.

OS wiped mistakenly, Not getting into download mode with Power + Volume Down + Bixby buttons.

Hi, I had mistakenly wiped the OS while wiping out the data while trying to flash no-verity-opt-encrypt (error 1). System was stuck in boot loop, with only Samsung Logo displayed. No amount of Power+Volume Down + Bixby buttons could get out of the boot loop.
Solution: As I was able to boot into TWRP (only application left in phone), rebooted into download mode from TWRP, managed to flash into stock firmware and this time successfully rooted the phone using magisk after successfully flashing Disable_Dm-Verity_ForceEncrypt latest version instead of no-verity-opt-encrypt which keeps failing due to error 1.

Galaxy note 9 restarts randomly after magisk updation.

My Galaxy Note 9 running on Custom rom had no problems.. Just updated the magisk( module not magisk manager app) to latest version and direct installed (as recommended by magisk) after that my phone having following problems.
1.No action on pressing reboot on magisk after flashing. As reboot not working magisk is not getting updated also..
2.Power off and restart options stopped working.. Phone is not powering off or restarting by any means using physical buttons or software options.
3. Phone is restarting automatically in every 10 minutes.
4. Can't enter in to twrp recovery as phone is not powering off its gets restarted randomly very quickly..
Can someone help to get out of this.
Minzlife said:
My Galaxy Note 9 running on Custom rom had no problems.. Just updated the magisk( module not magisk manager app) to latest version and direct installed (as recommended by magisk) after that my phone having following problems.
1.No action on pressing reboot on magisk after flashing. As reboot not working magisk is not getting updated also..
2.Power off and restart options stopped working.. Phone is not powering off or restarting by any means using physical buttons or software options.
3. Phone is restarting automatically in every 10 minutes.
4. Can't enter in to twrp recovery as phone is not powering off its gets restarted randomly very quickly..
Can someone help to get out of this.
Click to expand...
Click to collapse
as soon as before showing samsung note9 logo, press and hold the button combination vol up + bixby + power.
keep it pressed the entire time. at one point you will able to enter the TWRP

Unable to enter Recovery mode after reboot from twrp or stock recovery.

Moin,
My phone was one day suddenly unable to boot into system nor Recovery, but could still enter fastboot.
Took me a while to figure out that USB Hubs let flash attempts fail too. (you can watch the drama in my older posts)
Now i was able to flash System back into a workable state and it looks like that recovery is also successful flashed.
BUT...i can enter recovery only ONCE per Vol - and Power on Button.
i have NO OTHER WAY to enter Recovery at all. i have no reboot option in system (LOS 18.1).
In fastboot/adb command and after one succsesfull reboot per keys, it always stuck after the Sony logo into a black screen. i then have to restart it into system with Vol+ and Power (one vibration) or shut down with vol+ and power for 6 seconds (three vibration) to get it either into fastboot (Vol+ and USB connect) or system again. then i have to flash it again to get into TWRP once. i tryed the latest twrp version (3.7.0) and one older version (3.3.1) that had once worked until the phone broke.
Any idea what is going wrong here. i have already try to completly wipe everything from the phone and try to fix SEL Linux in twrp. nothing seems to work. Did i miss something?
/€: Now it is again in the full broken state. recovery nor System won't boot anymore and end in a black screen.
/€²: Found the Problem: my lilca zip was polluted with altered files i forgot about.

Categories

Resources