Magisk v.16 and new module install failure - Magisk

So it was a nice monday morning and I decided to try out some magisk module on my coolpad note 3 lite running madOS8.1. After the reboot it got hang on Oreo logo, as it has happened before and usually what I do is force restart the device so I tried to force restart it using power button but it again hang in the same point. Now I tried factory reset it but I think I didn't performed it the right way ends up downloading madOS and Gapps again to flash using twrp. As I installed quite a few modules at once so can't say which one caused it but the thing I want to know is how can I prevent it to break again. Is it possible to remove a magisk module from twrp? Or is there any other way to save my *ss

whoiam55 said:
So it was a nice monday morning and I decided to try out some magisk module on my coolpad note 3 lite running madOS8.1. After the reboot it got hang on Oreo logo, as it has happened before and usually what I do is force restart the device so I tried to force restart it using power button but it again hang in the same point. Now I tried factory reset it but I think I didn't performed it the right way ends up downloading madOS and Gapps again to flash using twrp. As I installed quite a few modules at once so can't say which one caused it but the thing I want to know is how can I prevent it to break again. Is it possible to remove a magisk module from twrp? Or is there any other way to save my *ss
Click to expand...
Click to collapse
You can remove a module via recovery (mount magisk, magisk manager for recovery)... Or just flash your unpatched boot.img to disable magisk then you can remove the module from the manager itself.
Sent from my MI 5 using Tapatalk

teddy0209 said:
(mount magisk, magisk manager for recovery)... Or just flash your unpatched boot.img
Click to expand...
Click to collapse
From your reply it seems that mount magisk and magisk manager for recovery are magisk module? And where can I find my unpached boot.img (I'm a beginner ) and yes thanks for the reply.

whoiam55 said:
From your reply it seems that mount magisk and magisk manager for recovery are magisk module? And where can I find my unpached boot.img (I'm a beginner ) and yes thanks for the reply.
Click to expand...
Click to collapse
You can find the latter in the download section, the first on the compilation of modules... Your unpatched boot.img/stock boot.img, you can find it inside your room zip, from your twrp backup if you did backup prior to installing magisk. Magisk also creates a backup of the boot.img before patching if I'm not mistaken.
Edit: It's under /data
Sent from my MI 5 using Tapatalk

teddy0209 said:
Magisk also creates a backup of the boot.img before patching if I'm not mistaken.
Edit: It's under /data
Click to expand...
Click to collapse
So your are saying that if it stuck on boot then I can go back to TWRP, select /data/boot.img and flash it to boot partition?
One more think suppose I install *X* module and it succeed, then I install *Y* module and it failed to boot. Now I flashed boot.img as written above will it contain *X* module or just a fresh boot.img?
Thanks again for the reply.

Related

Magisk v15.2 not installing

Hello
Okay i flashed my mobile with new OTA
after i try to install magisk but getting error that "Magisk manager stopped" after zip downloaded
i dont know why that happening
after zip downloaded getting black window then pop up shown about error
i think it cant patch boot img properly
in my old rom it works properly, but after flashing it did not work
thank you....
Try installing it in recovery
I sometimes get that majisk stopped toast on just about any ROM and just about any majisk release. I just ignore it. I have no idea of the what or why. Haven't noticed it affecting anything.
Yes. It's happening to me too. Does it work if I flash this update with twrp?
rabin69x said:
Yes. It's happening to me too. Does it work if I flash this update with twrp?
Click to expand...
Click to collapse
Did you read the responses above? It was already suggested to try that.
After installing magisk 15.2, magisk manager 5.5.3 stuck at the splash screen for me. What's wrong ?
rabin69x said:
Yes. It's happening to me too. Does it work if I flash this update with twrp?
Click to expand...
Click to collapse
I always flash builds from TWRP.
Eng.Raman said:
After installing magisk 15.2, magisk manager 5.5.3 stuck at the splash screen for me. What's wrong ?
Click to expand...
Click to collapse
Having the exact same issue on a pixel xl. Tried on 7.1 and 8.1, both with the same result.
I never use manager. Always TWRP, and can people start searching and using the support thread for questions, logs, and bugs instead of keep making a hundred useless threads of the same thing, can't install, can't install modules, etc. That's what support thread for. Thanks.
I am using MIUI 7.12.28 (latest) on Redmid 3S and I can flash magisk 15.2 using TWRP normally but when the phone restart, i go to magisk manager and it shows that magisk is not installed
I tried flash many time but the same problem happen
When i tried to flash magisk 14.0, it works. what is the problem here o_o
hungragezone said:
I am using MIUI 7.12.28 (latest) on Redmid 3S and I can flash magisk 15.2 using TWRP normally but when the phone restart, i go to magisk manager and it shows that magisk is not installed
I tried flash many time but the same problem happen
When i tried to flash magisk 14.0, it works. what is the problem here o_o
Click to expand...
Click to collapse
If updating, why not use direct method?
madbat99 said:
If updating, why not use directethod?
Click to expand...
Click to collapse
No, i am flashing from start
I just flash new miui (full wipe, factory reset)
and i also try to update from Magisk manager but when the flash screen appear, magisk manager force close (I already tried to clear data of Magisk manager and tried to update again but no success)
Now i can have root with Magisk 14.0 but when i tried to update to 15.2 using TWRP, it just disappear lol
(Flashing normally, no error, restart phone, go to magisk manager -> magisk is not installed )

Stuck in boot loop after installing Magisk

I had SuperSU installed (but I needed to hide the root from some apps), and I installed Magisk with the Direct Install method with succes.
I reboted and now is stuck in a boot loop...
What can I do to fix it?
I'm using a Galaxy Note 3 (Android 5) with stock firmware.
https://didgeridoohan.com/magisk/Magisk#hn_Moving_from_another_systemless_root_solution_to_MagiskSU
Edit:
https://didgeridoohan.com/magisk/Magisk#hn_Bootloop
And of course the rest of the guide:
https://didgeridoohan.com/magisk
I didn't know I have to backup my boot.img file
I'm searching for my original boot.img file from the firmware right now, but until the download is complete (15 hours :| ), I'm trying to flash the magisk uninstaller and use it with twrp terminal.
Didgeridoohan said:
Edit:
https://didgeridoohan.com/magisk/Magisk#hn_Bootloop
Click to expand...
Click to collapse
Thank you!
Solved it!
I flashed the Magisk uninstaller (Magisk-uninstaller-20180921.zip from https://github.com/topjohnwu/Magisk/releases) with TWRP, and it worked!

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.

[GUIDE] [TOOL] TWRP Installer + Root Redmi 8 (Olive)

TWRP INSTALLER FOR REDMI 8
​
I want to share my tool for installing TWRP for Redmi 8.Tested on MIUI 11 Global 11.0.10.0 (PCNMIXM). Always take a backup of your data before doing this modifications. I'm not responsible if something went wrong and do it at your own risk!!!
About this tool:
Includes Official TWRP for Redmi 8
Includes ADB and Fastboot
Easy to Use
Files:
TWRP Installer for Redmi 8 - https://androidfilehost.com/?fid=8889791610682873743
Magisk Zip - https://magisk.me/zip/
How to Install TWRP & Root:
Unlock the Bootloader.
Connect your phone with USB cable and put the Magisk zip file to your internal or SD Card
Turn off your device and reboot into fastboot by pressing Vol down and Power button
Extract the TWRP installer zip file
Open TWRP_Installer.bat
Press Enter to proceed
Then press any key to install the TWRP and wait to finish
Press any key again , it will automatically boot into TWRP
Go to Install
Find the Magisk Zip File then flash
Reboot and your done
Congratss!!! You successfully install TWRP and Root your Redmi 8
Notes:
You need to Flash the Magisk after you install the TWRP. So that it will not back to stock recovery and the TWRP is now your permanent recovery.
You can also change the TWRP that I use on this tool. Go to the installer folder and delete the recovery.img then paste the recovery that you want and rename it to "recovery.img"
Credits:
XDA
Xiaomi Redmi 8 Developers
TWRP
Google
THANK YOU FOR USING MY TOOL!!! HAVE A NICE DAY AND GODBLESS ​
I've followed every step im this guide with no errors but after reboot after flashing magisk phone boots to normal mode, nothing different other than magisk manager installed and root checker says phone not rooted. Any idea?
GreenGremlim said:
I've followed every step im this guide with no errors but after reboot after flashing magisk phone boots to normal mode, nothing different other than magisk manager installed and root checker says phone not rooted. Any idea?
Click to expand...
Click to collapse
Did you try to flash it again on TWRP? Or try to open the Magisk Manager App and go to Superuser and allow the root access on the root checker app
MattPRZ said:
Did you try to flash it again on TWRP? Or try to open the Magisk Manager App and go to Superuser and allow the root access on the root checker app
Click to expand...
Click to collapse
Yes tried flash again even did a factory reset and restarted all over and after flashing on twrp I dont have the magisk manager app
Edit: I downloaded and installed magisk manager app but says magisk is not installed.
GreenGremlim said:
Yes tried flash again even did a factory reset and restarted all over and after flashing on twrp I dont have the magisk manager app
Edit: I downloaded and installed magisk manager app but says magisk is not installed.
Click to expand...
Click to collapse
Maybe the root was gone after reset... Flash again the Magisk zip file or install it via the magisk manager
When I first install the magisk , I wait couple minutes and then the magisk manager appears
MattPRZ said:
Maybe the root was gone after reset... Flash again the Magisk zip file or install it via the magisk manager
Click to expand...
Click to collapse
I am trying to install via the magisk manager but I can't seem to see the right option I have tried download only zip file (dont know waht to do next) and also select and patch a file, where i select the downloaded zip file but I get an unssuported/unknown image format and then installation failed
GreenGremlim said:
I am trying to install via the magisk manager but I can't seem to see the right option I have tried download only zip file (dont know waht to do next) and also select and patch a file, where i select the downloaded zip file but I get an unssuported/unknown image format and then installation failed
Click to expand...
Click to collapse
Uninstall that magisk manager , reboot to twrp and flash again the magisk zip file , in my case I wait couple minutes then magisk manager appear
MattPRZ said:
Uninstall that magisk manager , reboot to twrp and flash again the magisk zip file , in my case I wait couple minutes then magisk manager appear
Click to expand...
Click to collapse
Uninstalled, rebooted and flashed again but magisk manager still doesnt appear, I am gonna restart phone and give leave it alone a couple of hours, will let you know how it goes.
MattPRZ said:
Uninstall that magisk manager , reboot to twrp and flash again the magisk zip file , in my case I wait couple minutes then magisk manager appear
Click to expand...
Click to collapse
GreenGremlim said:
Uninstalled, rebooted and flashed again but magisk manager still doesnt appear, I am gonna restart phone and give leave it alone a couple of hours, will let you know how it goes.
Click to expand...
Click to collapse
Update, after restarting phone and not using it for a copuple hours magisk manager still doesnt appear. Question; how to install magisk from magisk manager? Might try install it with the apk I downloaded from magisk manamger website.
GreenGremlim said:
Update, after restarting phone and not using it for a copuple hours magisk manager still doesnt appear. Question; how to install magisk from magisk manager? Might try install it with the apk I downloaded from magisk manamger website.
Click to expand...
Click to collapse
Maybe the magisk is now Installed , but if the magisk manager still not appear , install the magisk manager with the latest version
MattPRZ said:
Maybe the magisk is now Installed , but if the magisk manager still not appear , install the magisk manager with the latest version
Click to expand...
Click to collapse
Installed latest magisk manager, it shows magisk not instaled.
GreenGremlim said:
Installed latest magisk manager, it shows magisk not instaled.
Click to expand...
Click to collapse
That's strange... I never face that problem
Maybe the only solution is download and flash the magisk uninstaller , so that it will remove all the magisk files , and repeat the flashing of magisk
MattPRZ said:
That's strange... I never face that problem
Maybe the only solution is download and flash the magisk uninstaller , so that it will remove all the magisk files , and repeat the flashing of magisk
Click to expand...
Click to collapse
Ok will try that, thanks.
MattPRZ said:
That's strange... I never face that problem
Maybe the only solution is download and flash the magisk uninstaller , so that it will remove all the magisk files , and repeat the flashing of magisk
Click to expand...
Click to collapse
GreenGremlim said:
Ok will try that, thanks.
Click to expand...
Click to collapse
Made another hard reset to phone and I am going to try this https://c.mi.com/thread-3159753-1-1.html will keep you posted.
MattPRZ said:
That's strange... I never face that problem
Maybe the only solution is download and flash the magisk uninstaller , so that it will remove all the magisk files , and repeat the flashing of magisk
Click to expand...
Click to collapse
GreenGremlim said:
Ok will try that, thanks.
Click to expand...
Click to collapse
GreenGremlim said:
Made another hard reset to phone and I am going to try this https://c.mi.com/thread-3159753-1-1.html will keep you posted.
Click to expand...
Click to collapse
So, after ahard reset tried again following yor guide, still not rooted, after that I flashed stock rom to have a clean install and tried the tutorial I posted using a stock boot image patched with magisk and still no root. Is it possible that I am having no luck and you managed to root yours because of different stock roms i.e. Global vs China or Russia roms?
GreenGremlim said:
So, after ahard reset tried again following yor guide, still not rooted, after that I flashed stock rom to have a clean install and tried the tutorial I posted using a stock boot image patched with magisk and still no root. Is it possible that I am having no luck and you managed to root yours because of different stock roms i.e. Global vs China or Russia roms?
Click to expand...
Click to collapse
You flash stock rom via Mi flash tool? Maybe because of the rom that you use... I only tested on Global
MattPRZ said:
You flash stock rom via Mi flash tool? Maybe because of the rom that you use... I only tested on Global
Click to expand...
Click to collapse
Yes I flash stock rom via MiFlash tool, and my rom is Global like yours so that is not the issue. Still haven't figured what's wrong.
GreenGremlim said:
Yes I flash stock rom via MiFlash tool, and my rom is Global like yours so that is not the issue. Still haven't figured what's wrong.
Click to expand...
Click to collapse
Try other magisk version
MattPRZ said:
Try other magisk version
Click to expand...
Click to collapse
Any particular version in mind?
GreenGremlim said:
Any particular version in mind?
Click to expand...
Click to collapse
Try the lower versions like 20.3 , 20.2 and others

Stuck in Download mode bootloop after updating from v20.x to v21.x

Phone Model no : Samsung Galaxy S6 / SM-G920F
Security patch date: 01.10.2017
Android version: 7.0
Root status: Yes
Hey guys,
I rooted my phone several weeks ago for the first time via odin and everything went fine. I installed TWRP and Magisk and everything worked out.
Today I was trying to update Magisk from v20.x to v21.x with the inapp option, but now im stuck in a bootloop to download mode, screen says "Downloading... do not turn off target".
Even if I turn the phone off with Power + Home + Vol Down its just restarting right away and getting stuck in the same screen again.
Im still able to enter TWRP Recovery, but I dont know what to do to end the download mode problem when trying to start the phone.
I actually dont know/understand much about that stuff, so I dont know which other info I need to provide.
Is there something I could do without going through the whole flash/root process again?
should i try to delete magisk and install it again? if yes, how do i do it?
Help would be appreciated.
n00btuber said:
Phone Model no : Samsung Galaxy S6 / SM-G920F
Security patch date: 01.10.2017
Android version: 7.0
Root status: Yes
Hey guys,
I rooted my phone several weeks ago for the first time via odin and everything went fine. I installed TWRP and Magisk and everything worked out.
Today I was trying to update Magisk from v20.x to v21.x with the inapp option, but now im stuck in a bootloop to download mode, screen says "Downloading... do not turn off target".
Even if I turn the phone off with Power + Home + Vol Down its just resarting right away and getting stuck in the same screen again.
Im still able to enter TWRP Recovery, but I dont know what to do to end the downloading problem when trying to start the phone.
I actually dont know/understand much about that stuff, so I dont know which other info I need to provide.
Is there something I could do without going through the whole flash/root process again?
should i try to delete magisk and install it again? if yes, how do i do it?
Help would be appreciated.
Click to expand...
Click to collapse
I don't know much about your device but if you can enter TWRP, it's not that bad. First what you can try is to download Magisk uninstaller and flash it in TWRP from USB. However, I don't know what can you do to update Magisk safely. Would be best if you can check your device forum or ask the question there
Lord Sithek said:
I don't know much about your device but if you can enter TWRP, it's not that bad. First what you can try is to download Magisk uninstaller and flash it in TWRP from USB. However, I don't know what can you do to update Magisk safely. Would be best if you can check your device forum or ask the question there
Click to expand...
Click to collapse
Looked like my device forum is pretty dead, which is why I asked the question here again. Thanks for the fast respone
Its probably not possible to just install a Magisk version again and overwrite the current one, probably need to uninstall first and then install it again?
There is a Magisk Module Uninstaller and a Magisk Uninstaller. Are those different things or just the same?
How to Uninstall Magisk Module Using TWRP Recovery | MagiskRoot
Uninstall Magisk Module using TWRP Recovery or Offline whenever you stuck into bootloop. Magisk Module Uninstaller and Magisk Manager for Recovery methods.
magiskroot.net
How to Uninstall Magisk From Android [2 Easiest Method]
Are you facing issues with Magisk? You can uninstall magisk from your phone with these simple and easy steps.
magiskmanager.com
Because the 2nd guide says in the end
Keep in Mind – Whenever you use TWRP as a method to uninstall Magisk, it is imperative to flash the Magisk Module Uninstaller Zip onto your device.
Does this mean I need to do the magisk module one first?
@n00btuber Do not trust those websites. They're in no way official and are just trying to get adc revenue from Magisk's popularity. If you're really unlucky they'll also provide you with malicious zips...
Only download stuff from John's GitHub:
https://github.com/topjohnwu/Magisk
If you need to uninstall Magisk use the uninstall zips from the above linked Github repo, and if you need to uninstall modules (but those will also be removed by the Magisk uninstaller) you can do that directly from TWRP:
https://www.didgeridoohan.com/magisk/Magisk#hn_Uninstalldeletedisable_modules_from_recovery
A lot of times you can just flash another Magisk version over your installed one, but there are times where you do need to uninstall first. Since you have TWRP it can't really hurt to just try flashing whatever Magisk zip you want and it it doesn't work you can just use the uninstaller first.
One other thing to try would be the Canary release, mainly to see if you're affected by any bugs that is present in the current stable release but has been fixed upstream. You'll find the Canary app in the same Github link above.
Didgeridoohan said:
@n00btuber Do not trust those websites. They're in no way official and are just trying to get adc revenue from Magisk's popularity. If you're really unlucky they'll also provide you with malicious zips...
Only download stuff from John's GitHub:
https://github.com/topjohnwu/Magisk
Click to expand...
Click to collapse
Ok.
Was trying to use the uninstaller from his GitHub.
Trying to flash it leads to
"Updater process ended with ERROR:1
Error installing Zip file .....
Updating partition details"
So what to do now?
Trying to just flash any Magisk version to overwrite the current one leads to the same result.
I think it says Unsupported/Unknown image format
Your TWRP might be bugged/incompatible. I'd reflash your stock boot image and then patch the file manually (you'll find the instructions for that on GitHub as well).
Didgeridoohan said:
Your TWRP might be bugged/incompatible.
Click to expand...
Click to collapse
But TWRP worked fine when installing magisk the first time, I even tried the same zip folder I used to install it back then, but it wont work anymore.
Didgeridoohan said:
I'd reflash your stock boot image and then patch the file manually (you'll find the instructions for that on GitHub as well).
Click to expand...
Click to collapse
However, whats my stock boot image and how to reflash it? Cant find a guide for that on GitHub.
Would a Factory Reset wipe all Magisk stuff and my TWRP Partition as well?
Does anyone know what is going on between Magisk and Google? It seems Google has removed Magisk Manager from the Play Store AGAIN! What's more, I downloaded and installed the apk but when I try to use it to install the latest Magisk the install fails. Tried installing the Magisk zip via TWRP, and while it doesn't show any errors, I still don't have root.
Ok I really need some more help @Didgeridoohan
Meanwhile I tried to reinstall TWRP from within TWRP. There was no error so I think it should have worked, but didnt solve the problem.
As soon as I try to boot the system it directly boots download mode and gets stuck in it. The volume buttons wont work or do anything as they are supposed in download mode.
Im still able to get into TWRP, but I still dont know what to do to stop this crashed download mode that starts over and over again.
When trying to flash the magisk uninstall it states "cannot access /data", when trying to flash a magisk installer it states "unsupported/unknown image format"
I dont care about Magisk right now though, I can root and install magisk again as soon as im able to clear the download mode problem. I was just trying this because trying to update magisk from within magisk manager has caused this download mode problem to appear.
Just tell me please how to fix that or how to factory reset my phone so it is able to boot regular again.
Thank you
n00btuber said:
Ok I really need some more help @Didgeridoohan
Meanwhile I tried to reinstall TWRP from within TWRP. There was no error so I think it should have worked, but didnt solve the problem.
As soon as I try to boot the system it directly boots download mode and gets stuck in it. The volume buttons wont work or do anything as they are supposed in download mode.
Im still able to get into TWRP, but I still dont know what to do to stop this crashed download mode that starts over and over again.
When trying to flash the magisk uninstall it states "cannot access /data", when trying to flash a magisk installer it states "unsupported/unknown image format"
I dont care about Magisk right now though, I can root and install magisk again as soon as im able to clear the download mode problem. I was just trying this because trying to update magisk from within magisk manager has caused this download mode problem to appear.
Just tell me please how to fix that or how to factory reset my phone so it is able to boot regular again.
Thank you
Click to expand...
Click to collapse
Sounds to me like you need to reflash your ROM, not TWRP. According to your OP, you're running Android 7, but it doesn't say if it is stock or a custom ROM.. If it is stock, then use Frija.exe to download the ROM and then flash th AP, BL and HOME_CSC md5 files with Odin. If it is a custom ROM, use TWRP to flash the ROM and gapps. DO NOT try to flash Magisk. Right now there seems to be a problem with Google disabling Magisk. Wait till it is resolved before attempting to get root.
@n00btuber Dirty flashing your ROM is most likely the way to go, just like described above.
But @lewmur, what do you mean by "Google disabling Magisk"? If you're talking about SafetyNet there are ways around that (and it doesn't affect root)...
Didgeridoohan said:
@n00btuber Dirty flashing your ROM is most likely the way to go, just like described above.
But @lewmur, what do you mean by "Google disabling Magisk"? If you're talking about SafetyNet there are ways around that (and it doesn't affect root)...
Click to expand...
Click to collapse
I not talking about safety net. Look in Play Store for Magisk Manager. It is no longer there. And even if you download and install the apk, it won't install Magisk. Flashing Magisk from TWRP doesn't give root privileges. This just happened yesterday.
lewmur said:
I not talking about safety net. Look in Play Store for Magisk Manager. It is no longer there. And even if you download and install the apk, it won't install Magisk. Flashing Magisk from TWRP doesn't give root privileges. This just happened yesterday.
Click to expand...
Click to collapse
The Magisk Manager hasn't been on the Play Store for years... Edit: reference - https://forum.xda-developers.com/t/magisk-the-magic-mask-for-android.3473445/post-72508849
Nothing of what you describe has anything to do with Google "disabling Magisk".
Didgeridoohan said:
The Magisk Manager hasn't been on the Play Store for years... Edit: reference - https://forum.xda-developers.com/t/magisk-the-magic-mask-for-android.3473445/post-72508849
Nothing of what you describe has anything to do with Google "disabling Magisk".
Click to expand...
Click to collapse
That 's my mistake. Play Store would put up a lot of "Magisk Manager" stuff, but I never really tried any of it because flashing Magisk would give me the Manager. But even that "stuff" no longer shows up.
Butt Magisk Manager still won't install Magisk. It will download the zip file, but when it attemps to install it, it get an error saying Unsupported/Unknown image format. If I flash it from TWRP, and then open Magisk Manager, it still says N/A under Installed for Magisk.
lewmur said:
Then why won't Magisk Manager install Magisk. It will download the zip file, but when it attemps to install it, it get an error saying Unsupported/Unknown image format. If I flash it from TWRP, and then open Magisk Manager, it still says N/A under Installed for Magisk.
Click to expand...
Click to collapse
That will be an incompatibility between Magisk and your device and has nothing to do with Google (blame your OEM for doing weird stuff instead).
Thanks for the help guys, had to flash the ROM, now its working again.

Categories

Resources