Database Develop

Startup Hang after Installing Magisk v18.0

Hey, all!
Had a notification this morning for the new Magisk Manager (6.1) and Magisk (18.0) release. I downloaded both and rebooted the phone (OnePlus 2), updating from 17.3 to 18.0 directly, which had no errors during the install. Now upon startup it hangs on the splash screen. I can get into recovery (TWRP) and I have tried to flash the latest Magisk Uninstaller but I'm greeted with an ERROR 1: Error Installing zip file '/sdcard/...' - Unable to unpack boot.img
Any help here? Thanks in advance!

SpikyAndroid3 said:
Hey, all!
Had a notification this morning for the new Magisk Manager (6.1) and Magisk (18.0) release. I downloaded both and rebooted the phone (OnePlus 2), updating from 17.3 to 18.0 directly, which had no errors during the install. Now upon startup it hangs on the splash screen. I can get into recovery (TWRP) and I have tried to flash the latest Magisk Uninstaller but I'm greeted with an ERROR 1: Error Installing zip file '/sdcard/...' - Unable to unpack boot.img
Any help here? Thanks in advance!
Click to expand...
Click to collapse
You can do dirty flash of your current ROM. That would simply replace the boot.img back to normal and then you can try flashing Magisk v18.0 again (if you want to)
Sent from my #FlagshipKiller3T using Tapatalk

DarkSJ1998 said:
You can do dirty flash of your current ROM. That would simply replace the boot.img back to normal and then you can try flashing Magisk v18.0 again (if you want to)
Sent from my #FlagshipKiller3T using Tapatalk
Click to expand...
Click to collapse
Thanks for the response, just about to do a dirty flash of the stock ROM. My memory doesn't serve me well, is it best to wipe Cache as well as Dalvik Cache, or just Dalvik Cache?
The recovery also stays as is, right?

Hello,
The same for me from 17.3 to 18.
I'm on Nexus 6 with stock ROM.

SpikyAndroid3 said:
Thanks for the response, just about to do a dirty flash of the stock ROM. My memory doesn't serve me well, is it best to wipe Cache as well as Dalvik Cache, or just Dalvik Cache?
The recovery also stays as is, right?
Click to expand...
Click to collapse
Yep the recovery should stay as it is. I would recommend wiping both Dalvik Cache & Cache. Also, do keep fastboot handy. TWRP survival really depends on the device. For my device (OnePlus 3T), the OOS overrides TWRP if no root solution is used or patched boot.img isn't used.
Sent from my #FlagshipKiller3T using Tapatalk
---------- Post added at 01:08 AM ---------- Previous post was at 12:55 AM ----------
StreamingMT said:
Hello,
The same for me from 17.3 to 18.
I'm on Nexus 6 with stock ROM.
Click to expand...
Click to collapse
Weird :/
Did you check the Magisk release thread for people facing similar issues? I'm still on v17.3.
I'm really reluctant to move to v18.0 after reading such things... Moreover, I always wait for feedbacks before trying out things that play with the boot.img's & stuff, because I already got /data partition of my last device corrupted [emoji52]
Sent from my #FlagshipKiller3T using Tapatalk

DarkSJ1998 said:
Yep the recovery should stay as it is. I would recommend wiping both Dalvik Cache & Cache. Also, do keep fastboot handy. TWRP survival really depends on the device. For my device (OnePlus 3T), the OOS overrides TWRP if no root solution is used or patched boot.img isn't used.
Click to expand...
Click to collapse
Alrighty! Just went ahead and did the flash and it successfully reboots! Tried to reboot into recovery to flash Magisk 17.3 and lo and behold TWRP is still there
Guess I'll wait until there has been an update or patch of some sorts if @StreamingMT is also getting this issue, maybe there are others too. Thanks for the help @DarkSJ1998

I will try to remember that @DarkSJ1998.
I was excited to have a new update, just got reckless...
Anyways, I replied to the official thread about the details, just search through it. I just restored my phone to the way it used to...
All my saves... Gone to trash.

SpikyAndroid3 said:
Hey, all!
Had a notification this morning for the new Magisk Manager (6.1) and Magisk (18.0) release. I downloaded both and rebooted the phone (OnePlus 2), updating from 17.3 to 18.0 directly, which had no errors during the install. Now upon startup it hangs on the splash screen. I can get into recovery (TWRP) and I have tried to flash the latest Magisk Uninstaller but I'm greeted with an ERROR 1: Error Installing zip file '/sdcard/...' - Unable to unpack boot.img
Any help here? Thanks in advance!
Click to expand...
Click to collapse
I had the same bootloop issue when I was reinstalling H2OS beta 21 in my OnePlus 5 today. I got it to boot again with Magisk 18.0 after:
1. Dirty flashing ROM. Now this is important Did not flash Magisk (yet).
2. Rebooting to Bootloader (fastboot) in TWRP (since no root, now stock recovery will reinstall).
3. Fastboot flashed TWRP. Booted to Recovery mode from Fastboot menu.
4. Flashed Magisk 18.0 in TWRP. Now this is important Only flashed Magisk, nothing else.
5. Rebooted to Recovery again instead of System to flash other stuff.
6. Rebooted system.
If course YMMV. The important thing was to not try to flash Magisk while flashing ROM.

Same here on a mi max 2, updated manager and magisk directly from app, now stuck in bootloop. im downloading my rom as im typing to restore stock boot image. will flash v17.1 instead.

I have 1 plus 5 with official H2OS and Magisk 17.1.
Today when after installed Magick 18 and reboot, it stuck at startup.
I try to flash TWRP using adb, but it give me error:
E:\Program Files\Android\platform-tools>adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
E:\Program Files\Android\platform-tools>adb kill-server
E:\Program Files\Android\platform-tools>
Click to expand...
Click to collapse

I too am having with latest magisk 18.0 my device is redimi 4x, on trying to update via magisk manager crashes with an error report, installed update using twrp now i get a error popup at start and magisk manger still shows am on 17.1 and tells to update, which crashes the app on trying

tmicrd68 said:
I had the same bootloop issue when I was reinstalling H2OS beta 21 in my OnePlus 5 today. I got it to boot again with Magisk 18.0 after:
1. Dirty flashing ROM. Now this is important Did not flash Magisk (yet).
2. Rebooting to Bootloader (fastboot) in TWRP (since no root, now stock recovery will reinstall).
3. Fastboot flashed TWRP. Booted to Recovery mode from Fastboot menu.
4. Flashed Magisk 18.0 in TWRP. Now this is important Only flashed Magisk, nothing else.
5. Rebooted to Recovery again instead of System to flash other stuff.
6. Rebooted system.
If course YMMV. The important thing was to not try to flash Magisk while flashing ROM.
Click to expand...
Click to collapse
Using Xiaomi Mi Max
Using your method and it work just took afew for it to boot back up :good:

netsonic said:
I have 1 plus 5 with official H2OS and Magisk 17.1.
Today when after installed Magick 18 and reboot, it stuck at startup.
I try to flash TWRP using adb, but it give me error:
Code:
E:\Program Files\Android\platform-tools>adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
E:\Program Files\Android\platform-tools>adb kill-server
Click to expand...
Click to collapse
Try 'Revoking USB Debugging' and restart the adb server. Then reinstate its authorization by plugging it back in with USB Debugging enabled. And just to check, make sure you run cmd as administrator, and ensure MTP is on.
huzeifa88 said:
I too am having with latest magisk 18.0 my device is redimi 4x, on trying to update via magisk manager crashes with an error report, installed update using twrp now i get a error popup at start and magisk manger still shows am on 17.1 and tells to update, which crashes the app on trying
Click to expand...
Click to collapse
Try flashing the uninstaller which you can get here. Then reinstall/reflash Magisk with a previous version that worked for you.

DarkSJ1998 said:
You can do dirty flash of your current ROM. That would simply replace the boot.img back to normal and then you can try flashing Magisk v18.0 again (if you want to)
Sent from my #FlagshipKiller3T using Tapatalk
Click to expand...
Click to collapse
It's possible only flash the stock boot.img (extracted from fastboot stock rom) with the TWRP?

otraver said:
It's possible only flash the stock boot.img (extracted from fastboot stock rom) with the TWRP?
Click to expand...
Click to collapse
I guess it's possible, but I'm not sure about that.... You can backup/restore boot.img from TWRP but I don't know if you can do this also... Do check it on the Internet.
Sent from my #FlagshipKiller3T using Tapatalk

DarkSJ1998 said:
You can do dirty flash of your current ROM. That would simply replace the boot.img back to normal and then you can try flashing Magisk v18.0 again (if you want to)
Sent from my #FlagshipKiller3T using Tapatalk
Click to expand...
Click to collapse
DarkSJ1998 said:
I guess it's possible, but I'm not sure about that.... You can backup/restore boot.img from TWRP but I don't know if you can do this also... Do check it on the Internet.
Sent from my #FlagshipKiller3T using Tapatalk
Click to expand...
Click to collapse
Don't work.
The cellular boot but stops in the Miui Screen with the unlocked symbol
I tried a dirty install of the rom but don't work
I need to install a clean global stock rom to boot correctly.

otraver said:
It's possible only flash the stock boot.img (extracted from fastboot stock rom) with the TWRP?
Click to expand...
Click to collapse
Actually, Magisk does a backup of stock boot.img before patching it, which lies stored in /data as ".img.gz.zip". Haven't looked for how to restore it yet; however, assuming it's a flashable zip, it can be restored via TWRP. Should check Magisk release OP to be sure...
Sent from my Moto Z2 Play using XDA Labs

The Analog Kid said:
Actually, Magisk does a backup of stock boot.img before patching it, which lies stored in /data as ".img.gz.zip". Haven't looked for how to restore it yet; however, assuming it's a flashable zip, it can be restored via TWRP. Should check Magisk release OP to be sure...
Sent from my Moto Z2 Play using XDA Labs
Click to expand...
Click to collapse
Doesn't look like a flashable zip too me. It stores a *.img file in it, which I think is flashable as an image from TWRP. But, I'm not 100% sure about it.
Great discovery though dude there
Sent from my #FlagshipKiller3T using Tapatalk

otraver said:
It's possible only flash the stock boot.img (extracted from fastboot stock rom) with the TWRP?
Click to expand...
Click to collapse
Hello, I do this with my Nexus 6, it's OK. Flash again Magisk (v17 not 18 for me) and all is OK for me.

Boot loop for me too after upgrading from v17 to v18 . I'm on Nexus 6. Any official information about this bug?
Fixed by installing TWRP then restored backup through TWRP and selected only boot image. I guess TWRP or me saved backup at some point, don't remember exactly. Will have to use v17 for now.

TWRP gets replaced by stock recovery

So I've used TWRP r16 and it throws an "Image not signed or corrupt" error as suggested by other users I ignored it, but everytime I reboot to system and try to get to recovery "no command" show's up meaning TWRP was replaced by stock recovery all help will be appreciated.
Thanks

Akash731 said:
So I've used TWRP r16 and it throws an "Image not signed or corrupt" error as suggested by other users I ignored it, but everytime I reboot to system and try to get to recovery "no command" show's up meaning TWRP was replaced by stock recovery all help will be appreciated.
Thanks
Click to expand...
Click to collapse
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed

pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
Hey thanks that worked.
But everytime I boot to system and boot to twrp the data gets encrypted and I can't access the files do you happen to know any solution for this?

Akash731 said:
Hey thanks that worked.
But everytime I boot to system and boot to twrp the data gets encrypted and I can't access the files do you happen to know any solution for this?
Click to expand...
Click to collapse
If you are on stock Rom, according to my knoweldge it is not possible to remove encryption, if you format your date in twrp for removing encryption then reboot to system you can see that the phone is again encrypted.
But in custom roms this doesnt happen.

pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
pradeeppk said:
If you are on stock Rom, according to my knoweldge it is not possible to remove encryption, if you format your date in twrp for removing encryption then reboot to system you can see that the phone is again encrypted.
But in custom roms this doesnt happen.
Click to expand...
Click to collapse
I don't want to try custom rom's as this is my main device guess I'm stuck with the encryption then thanks for your help. :good:
Edit:-
Tried TWRP r20 it decrypts fine thanks

pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
You don't have to flash Magisk after flashing TWRP. The two are unrelated.
After flashing TWRP you have to boot into recovery, not system. Once TWRP was started, you can reboot into system. No need for Magisk (unless you want Magisk anyway).

gewe said:
You don't have to flash Magisk after flashing TWRP. The two are unrelated.
After flashing TWRP you have to boot into recovery, not system. Once TWRP was started, you can reboot into system. No need for Magisk (unless you want Magisk anyway).
Click to expand...
Click to collapse
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867

pradeeppk said:
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
Click to expand...
Click to collapse
I am using stock ROM, and yes, also Magisk (installed later). IIRC Magisk is not needed for TWRP to work. When I receive the next OTA notification, I will test this.
The thread you are referring to is for a OnePlus 3T. For our device this is the thread: https://forum.xda-developers.com/moto-g5s-plus/development/recovery-twrp-3-1-1-r7-t3694910.
Since there is no official TWRP for the Moto G5S Plus, I took the following text from the TWRP page for the Moto G5S.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
Instead of that you can also use fastboot reboot-bootloader, and then from the bootloader start recovery.

pradeeppk said:
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
Click to expand...
Click to collapse
Two days ago I received a notification for an OTA update, containing the August 2019 security patches.
After going back to stock ROM, installing all the updates up to the latest, I installed TWRP. After booting into recovery, and then into system, and recovery again, TWRP was gone. Strange, I don't remember this happening before. Maybe I always installed Magisk before booting into system.
Bottom line: you were right, I was wrong. Thanks for pointing it out.

gewe said:
Two days ago I received a notification for an OTA update, containing the August 2019 security patches.
After going back to stock ROM, installing all the updates up to the latest, I installed TWRP. After booting into recovery, and then into system, and recovery again, TWRP was gone. Strange, I don't remember this happening before. Maybe I always installed Magisk before booting into system.
Bottom line: you were right, I was wrong. Thanks for pointing it out.
Click to expand...
Click to collapse
As like you said this is the first time in my life i need to flash magisk to stick twrp.
I usualy doesn't use root or custom roms, install twrp, remove unnecessary apps from stock system, replace host files with adaway hosts, replace or edit gps config files. and continue using stock.
This is the main routine from Android 1.5
(Samsung spica (i think it was the first Android phone from Samsung)).
It may be due to security reason stock kernel or system delete twrp.
When installing magisk it patch stock boot image, that may be the reason of twrp remains after flashing magisk.

How to install TWRP and Magisk on Redmi 8?

How to install TWRP and Magisk on Redmi 8?
I always end up in a bootloop and have to flash official rom over and over again.

I'm looking for installing twrp for the redmi 8 Olive, but still haven't found it. Where did you get yours?

ketogeno said:
How to install TWRP and Magisk on Redmi 8?
I always end up in a bootloop and have to flash official rom over and over again.
Click to expand...
Click to collapse
Same here bro

Maybe you guys need to flash the no verity zip file after magisk?
Not sure if that will do the trick tho.
How are you installing magisk without any official or unofficial twrp???

I'm another one lookingo for TWRP for Redmi 8 and still didn't find it.

I think you guys are looking for this https://c.mi.com/thread-1843805-1-0.html

TWRP.zip
Instructions from Altsec
Install TWRP from Redmi 8a
It's ONLY for redmi 8 with dispay Tianma !!!
Other display needed otg + mouse.
Attention! Unlocked Bootloader Required !!!
1. Download Attached file twrp.zip
2. Unpack to the root of the disk (I had C: \ TWRP \)
3. Restart the phone to fastboot mode (Volume - and Power at the same time)
4. In the folder we find flash.bat, run it, it will flash two files vbmeta and recovery
5. The device will reboot, after rebooting you can boot into the recovery manually Volume + and Turn On Simultaneously

куча лагов тврп заточено под 32 а редми 8 64 глючит оно
a bunch of lags of tvrp is imprisoned under the 32 kernel and the redmi 8 64 is buggy.
Does not install firmware in backup sistem does not fail with error apparently incompatibility is on

redmi 8 terp
I am not sure, but on cz.xiaomi page one admin take this link to redmi 8 twrp. I dont try it because i dont have unlock bootloader now.
Sorry i try to take link in here but this stupid server rules... "To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"
Go to miuios.cz to section redmi 8/8A, post MIUI CZ SK ROM + TWRP, you must be loged and in VMach3 post is this link.

I have only tried to boot mentioned recovery, but it was not working for me.
Code:
~/Downloads$ fastboot boot recovery-TWRP-3.3.1-1127-REDMI8-CN.img
downloading 'boot.img'...
OKAY [ 2.107s]
booting...
OKAY [ 2.121s]it
finished. total time: 4.228s
~/Downloads$
After automatic reboot started system. When manualy restarted phone booted to vendor recovery mode. No adb was available and any try to boot to system was failure - phone always booted to recovery mode. To boot to system I needed to select "wipe data" and then reboot to phone (but all previous data/configuration was deleted).

One more try with this Unofficial TWRP 3.3.1-1127 for REDMI 8 by wzsx150, this time it was success, everything was working smoothly.
Install from fastboot mode:
Code:
fastboot flash recovery recovery-TWRP-3.3.1-1127-REDMI8-CN-wzsx150.img
fastboot boot recovery-TWRP-3.3.1-1127-REDMI8-CN-wzsx150.img
my device:
Code:
fastboot getvar product
product: olive
Tested also with rom MIUI 11 xiaomi.eu without issues.

jkkk88 said:
One more try with this Unofficial TWRP 3.3.1-1127 for REDMI 8 by wzsx150, this time it was success, everything was working smoothly.
Install from fastboot mode:
Code:
fastboot flash recovery recovery-TWRP-3.3.1-1127-REDMI8-CN-wzsx150.img
fastboot boot recovery-TWRP-3.3.1-1127-REDMI8-CN-wzsx150.img
my device:
Code:
fastboot getvar product
product: olive
Tested also with rom MIUI 11 xiaomi.eu without issues.
Click to expand...
Click to collapse
Hi. Am I right, this TWRP is for China version of Redmi 8? I have Global version. Will it work for me?

mcichy10 said:
Hi. Am I right, this TWRP is for China version of Redmi 8? I have Global version. Will it work for me?
Click to expand...
Click to collapse
TWRP is language and version (global, china etc.) neutral. You have on first screen by first run button on right side at the bottom where you can select english language.

If you want root your phone with magisk, go directly to canary version. By stable version I got root only by adb, other apps were denied root access and freeze for a short time (for ex. Total commander beta).
On the other hand I was not able to use phone with not encrypted data with none of magisk version (stable or canary) even if I had "Preserve forced Encryption" unticked.
Code:
~$ adb shell getprop ro.crypto.state
encrypted
Tested on MIUI 11.0.4 by xiaomi.eu.

Unable to install official TWRP in Redmi 8, Miui 11.0.7. It installed. and then vanished when rebooted. and then boot looped. Had to flash original recovery and boot img to reboot.
Had made sure that I didn't boot to system after flashing TWRP. and boot to recovery instead. It flashed okay. Could use the root after installing Magisk. But on reboot, all was gone. Boot looped.

nugroho2 said:
Unable to install official TWRP in Redmi 8, Miui 11.0.7. It installed. and then vanished when rebooted. and then boot looped. Had to flash original recovery and boot img to reboot.
Had made sure that I didn't boot to system after flashing TWRP. and boot to recovery instead. It flashed okay. Could use the root after installing Magisk. But on reboot, all was gone. Boot looped.
Click to expand...
Click to collapse
Hello,
Did you reboot via button combo or fastboot reboot?
I read somewhere that Magisk is to be flashed before reboot.
Anyway, you will succeed.
I follow you because I am at 100 h to unlock.

soket1 said:
TWRP.zip
Instructions from Altsec
Install TWRP from Redmi 8a
It's ONLY for redmi 8 with dispay Tianma !!!
Other display needed otg + mouse.
Attention! Unlocked Bootloader Required !!!
1. Download Attached file twrp.zip
2. Unpack to the root of the disk (I had C: \ TWRP \)
3. Restart the phone to fastboot mode (Volume - and Power at the same time)
4. In the folder we find flash.bat, run it, it will flash two files vbmeta and recovery
5. The device will reboot, after rebooting you can boot into the recovery manually Volume + and Turn On Simultaneously
Click to expand...
Click to collapse
Thank you

Evolution x problem

So i installed/flashed evolution x rom OSS vendor using orangefox (unchecked the unmount system thingy)without any error
my phone is decrypted so first thing i did is
wipe the cache,data,system,vendor,dalvik/art cache then
Add the evo x rom to queue then next is the DFE.zip then after succesfully flashed i reboot to system it worked and played for hours then I was planning to install magisk and pressed the reboot to recovery then the problem begun always stuck at fastboot wont boot to recovery cant even shutdown the phone always starts at fastboot.
whats the problem? or did I do anything wrong??
right now im using stock rom again but i want to use custom rom.
Mi 9t pro global latest update.

I had the same problem with other ROM. Even after flashing recovery once again my phone couldn't exit fastboot. The cause could be a damaged boot partition, but I'm not 100% certain.

hash8bits said:
So i installed/flashed evolution x rom OSS vendor using orangefox (unchecked the unmount system thingy)without any error
my phone is decrypted so first thing i did is
wipe the cache,data,system,vendor,dalvik/art cache then
Add the evo x rom to queue then next is the DFE.zip then after succesfully flashed i reboot to system it worked and played for hours then I was planning to install magisk and pressed the reboot to recovery then the problem begun always stuck at fastboot wont boot to recovery cant even shutdown the phone always starts at fastboot.
whats the problem? or did I do anything wrong??
right now im using stock rom again but i want to use custom rom.
Mi 9t pro global latest update.
Click to expand...
Click to collapse
Fast Boot Issue solved. Only tested on K20 pro
Run this you will get your twrp back by pressing vol + while booting and Boot into recovery system also working fine
fastboot flash dtbo dtbo.img
dtbo file attached below

I have problem with fingerprint.
When I use in full screen brightness its work perfectly, but when my screen on low brightness fingerprint don't recognise.
Pls help.
K20 pro
Evolution x

hash8bits said:
So i installed/flashed evolution x rom OSS vendor using orangefox (unchecked the unmount system thingy)without any error
my phone is decrypted so first thing i did is
wipe the cache,data,system,vendor,dalvik/art cache then
Add the evo x rom to queue then next is the DFE.zip then after succesfully flashed i reboot to system it worked and played for hours then I was planning to install magisk and pressed the reboot to recovery then the problem begun always stuck at fastboot wont boot to recovery cant even shutdown the phone always starts at fastboot.
whats the problem? or did I do anything wrong??
right now im using stock rom again but i want to use custom rom.
Mi 9t pro global latest update.
Click to expand...
Click to collapse
i have the exact problem, just i used twrp (3.5.2_9-0-raphael-1)
flashing dtbo doesnt do anything :/
how can I get out of bootloop? stuck at fastboot...
thank you so much

oriped said:
i have the exact problem, just i used twrp (3.5.2_9-0-raphael-1)
flashing dtbo doesnt do anything :/
how can I get out of bootloop? stuck at fastboot...
thank you so much
Click to expand...
Click to collapse
flashed the latest fastboot version from https://xiaomifirmwareupdater.com/miui/raphael to bring the phone back to life.
same problem? repeat after me:
choose a fastboot version, click download and then scroll down to the fastboot version (.tgz file type, don't get confused as the first download button is recovery version again...). extract and copy to minimal adb & fastboot. run "flash_all.bat".
phone starts with miui
softbrick, soft brick mi9 t pro, fastboot, flash stock rom, bootloop fastboot, Redmi K20 Pro, Raphael
still wondering what caused that bootloop...

^_^[Help] Magisk 25.1 Miui 12.5 [PBRecovery]

I need help, i don´t know compilated the Magisk from Github, when flash source.zip, have a brick in the smartphone...
Anyonelse have the Magisk 25.1. zip for flash?
Sorry my english is very bad

1)unlock the bootloader or unbrick the phone and backup the data cause it will be lost
2)Download the Magisk-v25.1.apk not zip.
3)then open file manager and rename the Magisk-v25.1.apk to
Magisk-v25.1.zip.
4)boot to fastboot and flash twrp recovery img misc and vbmeta and boot to twrp.
5)then flash Magisk-v25.1.zip. and you are good to go

JuanitoDog said:
I need help, i don´t know compilated the Magisk from Github, when flash source.zip, have a brick in the smartphone...
Anyonelse have the Magisk 25.1. zip for flash?
Sorry my english is very bad
Click to expand...
Click to collapse
omg!

Raghaov said:
1)unlock the bootloader or unbrick the phone and backup the data cause it will be lost
2)Download the Magisk-v25.1.apk not zip.
3)then open file manager and rename the Magisk-v25.1.apk to
Magisk-v25.1.zip.
4)boot to fastboot and flash twrp recovery img misc and vbmeta and boot to twrp.
5)then flash Magisk-v25.1.zip. and you are good to go
Click to expand...
Click to collapse
Yes i have bootloader unlocked and last recovery Pich
black.
I try your intruccions, Thanks

Yes man you are the ****ing best of the world greatings four you forever come on!

is your device working fine now

This also happened to my redmi note 8 it soft bricked my device while attempting to flash magisk 25.1, . So I followed this thread and go back to version 24
https://forum.xda-developers.com/t/fix-for-the-system-has-been-destroyed-redmi-note-8-8t.4089955/