Related
Hey,
I've been getting constant Magisk Manager crashes every time I try to run it even after multiple "full wipes" (except internal sdcard data) and I can't even get the logs because it doesn't let me access them and there's no folder with logs in them. What am I supposed to do? I already flashed the stock kernel and it didn't fix it. My ROM is the XtreStoLite and I'm using a Galaxy S6 920F. What could be causing it to crash even after "full" wipes?
Thanks
EDIT: Additionally, I can install Magisk without any problem in recovery but whenever I try to run an app that requires root rights, it shows the "Magisk Manager stopped working" error
I just did a complete wipe of literally everything I had on my phone, internal storage included and installed the rom back and magisk manager still crashes... what the hell?
Edit: Installed a logcat app to look at the logs when it crashes and here is the important part, I think:
E/AndroidRuntime(13780): Process: com.topjohnwu.magisk, PID:13780
E/AndroidRuntime(13780): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.topjohnwu.magisk/com.topjohnwu.magisk.SplashActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.res.Resources android.content.Context.getResources()' on a null object reference
Click to expand...
Click to collapse
Edit 2: Alright I've no idea what's wrong but v4.1 works fine, v4.2 crashes all the time even though it was working literally yesterday. Welp, whatever
Im on Resurrection Remix and when I install a Rom update, the managers "loses the root" too, I download the zip (and flash it) again and its a lucky strike if when the phone reboots, the magisk returns to normal and regain the root.
GolpeadorMágico said:
Im on Resurrection Remix and when I install a Rom update, the managers "loses the root" too, I download the zip (and flash it) again and its a lucky strike if when the phone reboots, the magisk returns to normal and regain the root.
Click to expand...
Click to collapse
That does not sound like the issue in the OP...
After a ROM update you'll have to flash the Magisk zip again, since the ROM most likely also updates the boot image, thus removing the Magisk modifications (including MagiskSU).
Didgeridoohan said:
That does not sound like the issue in the OP...
After a ROM update you'll always (well, almost) have to flash the Magisk zip again, since the ROM most likely also updates the boot image, thus removing the Magisk modifications (including MagiskSU).
Click to expand...
Click to collapse
So you are saying that I have to flash it in the same process, all together*, not flash, reboot and later flash the magisk zip?
*(Flash> mount rom zip+gapps+magisk)
GolpeadorMágico said:
So you are saying that I have to flash it in the same process, all together*, not flash, reboot and later flash the magisk zip?
*(Flash> mount rom zip+gapps+magisk)
Click to expand...
Click to collapse
You can boot up after updating, to make sure it's working and then flash Magisk. Doesn't really matter...
I usually flash the update, custom kernel and lastly Magisk zip, all in one go.
Didgeridoohan said:
You can boot up after updating, to make sure it's working and then flash Magisk. Doesn't really matter...
I usually flash the update, custom kernel and lastly Magisk zip, all in one go.
Click to expand...
Click to collapse
Oks. that´s is how I usually do it. I´m going to try again.
Guys, I´m sorry for the double post but I reinstaled it and nothing, the magisk managers says that the phone is not rooted.
***NEW: The problem is busybox. Uninstall it, reinstall magisk and problem solved.
I've let the MagiskManager upgrade Magisk from 14.x to 1.50. Then I rebooted the phone, and then it was stuck at the pulsating SAMSUNG logo.
So, next step would be obvious: get into TWRP and install Magisk 14.0.
And so I did, and so it failed. This time I got a bootloop. The "Galaxy S7 powered by Android" thing appears for a few seconds, and then vibrates and starts over. And over, and over, and over.
So then, I "installed" the Magisk Uninstaller. Thinking to get rid of all traces of Magisk that introduced this problem in the first place.
So I did, and now I'm back at the first problem: stuck at booting.
Then installing Magisk 14 AND wiping cache&dalvik: boot loop
Then I installed the uninstaller again, then Magisk 15, and wipe the cache&dalvik. And it's back at being stuck while booting again.
Brilliant. What do I do to fix this?
Are you using a custom ROM, or a port ROM, or a custom kernel?
It's all stock, except for it being rooted.
I'm having the same issue. Canadian S7 W8, Stock ROM with root, Magisk 14, upgraded to 15 using direct install through magisk manager.
Yes, exactly that. No offense, but that's helping neither yourself nor me nor anyone else. Have you been able to figure anything out?
Maybe how to produce some kind of log output?...
Same thing happened to me just now. Never would have thought that upgrading through the Magisk app would cause this. I've tried all of the above and have also tried installing v 12.0 but still no dice.
I even tried a factory reset and still no dice. This is seriously infuriating.
Guess I will have to reflash everything and start fresh. If anyone else has any other ideas I'm all ears.
I'd like to know what the phone is actually *doing* when it's stuck. How can we get to know this?
`fastboot logcat` and `adb logcat` both keep waiting for a device that will not connect. Something does connect, christ knows what, but certainly no adb or fastboot device.
@fattyspecial
"reflash everything and start fresh" can you explain what exactly this comprises? What should I do?
thany2 said:
I've let the MagiskManager upgrade Magisk from 14.x to 1.50. Then I rebooted the phone
...
What do I do to fix this?
Click to expand...
Click to collapse
Mate 8 running 7.0 stock except rooted, running Magisk 14, did the same thing and I'm in the same boat. Have also tried removing magisk, reinstalling 14 no dice. Have not factory reset yet (trying everything else before that step) but it looks like it won't help.
thany2 said:
I'd like to know what the phone is actually *doing* when it's stuck. How can we get to know this?
`fastboot logcat` and `adb logcat` both keep waiting for a device that will not connect. Something does connect, christ knows what, but certainly no adb or fastboot device.
@fattyspecial
"reflash everything and start fresh" can you explain what exactly this comprises? What should I do?
Click to expand...
Click to collapse
Completely reflash the entire stock rom with ODIN and then re-root and reconfigure my entire phone. About the biggest bother imaginable.
I'm trying to re-flash only a new boot.img (or new kernel) through twrp right now. If I can get that to work I'll let you know right away.
---------- Post added at 03:10 AM ---------- Previous post was at 02:29 AM ----------
FIXED IT!
Ok here's what I did. Maybe not a perfect solution but I am out of bootloop and phone is working and root is working too.
I had to install a custom kernel. I'm guessing this replaces the corrupted boot.img file. So you will need to be rooted and have a custom recovery like TWRP.
Go to https://forum.xda-developers.com/galaxy-s7/development/kernel-tgpkernel-t3462897 and scroll down to the part that says: DOWNLOAD VIA ANDROIDFILEHOST for N version and download the zip file.
Transfer the TGPKernel zip to your external SD card (either with android file transfer if on mac like me or with an SD card reader).
Flash the zip in TWRP.
It will take a LONG time to reboot. Don't worry.
I chose to install root with Magisk and it ended up updating it to v15.0 and so far everything seems to be working well.
Hope this helps. That took a long time to figure out. Time for bed.
Ok, I'm still not in that loop... yet.
Ok, I'm still not in that loop... yet.
I selected installing the 15.0 Magisk zip file (from 14.0) using direct install, then did the reboot and I'm stuck at the pulsating SAMSUNG logo.
Can I do the same fix of fattyspecial without loosing anything on the S7?
I did the exact Magisk 15.0 zip update on my LG Nexus 5, with no problem, in less than a minute.
I'm still not in that loop... yet.
ct1aic said:
Ok, I'm still not in that loop... yet.
I selected installing the 15.0 Magisk zip file (from 14.0) using direct install, then did the reboot and I'm stuck at the pulsating SAMSUNG logo.
Can I do the same fix of fattyspecial without loosing anything on the S7?
I did the exact Magisk 15.0 zip update on my LG Nexus 5, with no problem, in less than a minute.
Click to expand...
Click to collapse
Ok, I tried that soluction and it worked. I didn't loose anything and I have now Magisk 15.0 installed and still rooted/SafetyNet OK
Thanks, fattyspecial .
Happy New Year.
Rui
If you can' t solve download Magisk Uninstaller https://forum.xda-developers.com/attachment.php?attachmentid=4370032&d=1514240372
and Magisk 14.0 https://forum.xda-developers.com/attachment.php?attachmentid=4264532&d=1504713887
Then reboot in Twrp (hope you have it) and flash
1 uninstaller
2 14.0
I had the magisk 14.5 and I installed the 15 via twrp on top, and it updated normal. Is there a problem updating this way?
@fattyspecial
I don't see why installing a custom kernel is a viable fix. Or a good idea. It seems random.
Maybe you can explain why this is a fix, and how the stock kernel makes the phone bootloop?
@Tribal123
I think you will find I've already tried it. I appreciate your contribution, but please do read my topic start.
Same here, updated from v14 to v15 and got a nice bootloop.
Huawei Mate 8 with Nougat (stock) and TWRP.
EDIT:
Solved!
Flashed my stock boot.img backup through TWRP, then booted my phone and downloaded v14, flashed v14 through TWRP, booted my phone again and downloaded v15 with Magisk Manager app and checked "Preserve AVB 2.0/dm-verity" and then tapped "Install" using "Direct Install (recommended)"
thany2 said:
@fattyspecial
I don't see why installing a custom kernel is a viable fix. Or a good idea. It seems random.
Maybe you can explain why this is a fix, and how the stock kernel makes the phone bootloop?
@Tribal123
I think you will find I've already tried it. I appreciate your contribution, but please do read my topic start.
Click to expand...
Click to collapse
Because a custom kernel disables dm-verity. There's an issue, mainly on Samsung devices, with the dm-verity detection in Magisk v15.0. It's under investigation...
Meanwhile, flash a dm-verity disabler together with Magisk v15.0 and you should be good to go.
I'm fairly certain you need a custom kernel. I'm also on the S7 and without one I've always boot looped, I think it has to do with dm-verity.
EDIT: I didn't notice there was a second page so I guess I didn't really say anything new, oh well, sorry!
ct1aic said:
Ok, I tried that soluction and it worked. I didn't loose anything and I have now Magisk 15.0 installed and still rooted/SafetyNet OK
Thanks, fattyspecial .
Happy New Year.
Rui
Click to expand...
Click to collapse
Awesome! Glad it worked. Happy new year.
---------- Post added at 04:22 AM ---------- Previous post was at 04:15 AM ----------
thany2 said:
@fattyspecial
I don't see why installing a custom kernel is a viable fix. Or a good idea. It seems random.
Maybe you can explain why this is a fix, and how the stock kernel makes the phone bootloop?
@Tribal123
I think you will find I've already tried it. I appreciate your contribution, but please do read my topic start.
Click to expand...
Click to collapse
Hey man. I'm just telling you what worked for me. If you don't want to try it then don't.
fattyspecial said:
Completely reflash the entire stock rom with ODIN and then re-root and reconfigure my entire phone. About the biggest bother imaginable.
I'm trying to re-flash only a new boot.img (or new kernel) through twrp right now. If I can get that to work I'll let you know right away.
---------- Post added at 03:10 AM ---------- Previous post was at 02:29 AM ----------
FIXED IT!
Ok here's what I did. Maybe not a perfect solution but I am out of bootloop and phone is working and root is working too.
I had to install a custom kernel. I'm guessing this replaces the corrupted boot.img file. So you will need to be rooted and have a custom recovery like TWRP.
Go to https://forum.xda-developers.com/galaxy-s7/development/kernel-tgpkernel-t3462897 and scroll down to the part that says: DOWNLOAD VIA ANDROIDFILEHOST for N version and download the zip file.
Transfer the TGPKernel zip to your external SD card (either with android file transfer if on mac like me or with an SD card reader).
Flash the zip in TWRP.
It will take a LONG time to reboot. Don't worry.
I chose to install root with Magisk and it ended up updating it to v15.0 and so far everything seems to be working well.
Hope this helps. That took a long time to figure out. Time for bed.
Click to expand...
Click to collapse
Hello,
Here is the problem I personnaly had (solved now !) :
Initially, my wife had a G930F (samsung galaxy S7) and a Custom 7.0 rom (i think it was the "AlexNDR.G930FXXU2DRAG" rom...but I'm not sure at all because it was installed several months ago or even years) with TWRP as recovery and Magisk as root.
I saw that Magisk not working (since when ? I don't know because it was not my phone). So, I tried to update it via the Magisk application (the initial goal was to use then Titanium Backup).
Logically, the phone then rebooted to install the Magisk update... except that a Boot Loop appeared.
I then tried many things :
1° Downgrade or Upgrade the TWRP recovery to 3.0.0.0; to 3.2.2.0 and to 3.5.2.9.0 (thes recovery .img files are here: https://eu.dl.twrp.me/herolte/)
=> It didn't work, and the bootloop continued (but, at the end, i keep the TWRP v.3.5.2.9.0)
2° I tried to uninstall and reinstall Magisk
(cf. the "Custom Recovery" tuto here : https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root)
=> Failure. Still the BootLoop... (either with the .zip v19.1 or the .zip v23)
nb: I even tried to donwload other magisk files but still the same bootloop (cf.https://forum.xda-developers.com/t/collection-of-magisk-modules-v2.3575758/page-13#post-72542167)
4° I tried to change the kernel by using TGPKernel (https://forum.xda-developers.com/t/...2-30-tgpkernel-v6-15-5-3-18-140-esd2.3462897/)
=> Failure, the bootloop remained...
5° Finally, I found a solution :
a° I downloaded the rom "G930FXXU2DRAG_DevBase_v4.6.zip" (via the following tutorial here : https://forum.xda-developers.com/t/...vbase-v7-4-encryption-support-jul-10.3592914/)
, more exactly at the following location : https://androidfilehost.com/?fid=818070582850489124
b° Then, as indicated in the tuto (https://forum.xda-developers.com/t/...vbase-v7-4-encryption-support-jul-10.3592914/), I renamed the .zip downloaded on my PC to "G930FXXU2DRAG_DevBase_v4.6_rescue.zip" (ps: so, i add "..._rescue.zip)
c° After that, I copied the file "G930FXXU2DRAG_DevBase_v4.6_rescue.zip" on my micro SD.
d° In the recovery I finally installed the file "G930FXXU2DRAG_DevBase_v4.6_rescue.zip" and the phone restarted after a long time (or maybe 5 minutes, I didn't watch).
=> End of the bootloop and all data was preserved!!!
Scroll down over this post to see anwer!
Hey there! I just got my Xiaomi Mi8 from HK Goldway at Aliexpress. It came with its bootloader already unlocked and a Global ROM flashed.
I wanted to install Magisk but failed horribly . I've already done that to several phones (my last one was a Moto X Play, and it worked without major complications). But with this one, it seems I can't get past the bootlogo.
Stock Fastboot image used:
dipper_global_images_V9.5.13.0.OEAMIFA_20180714.0000.00_8.1_global
This is what I've tried so far:
First try
Flashed TWRP for Mi8 version 0711.
Flashed Magisk.
Got a bootloop.
Reflashed stock image via Fastboot.
Second try
Booted (not flashed) TWRP.
Tried to install latest global weekly from this thread.
Also got a bootloop.
Reflashed stock image via Fastboot.
Third try
I thought that those flashable ZIP firmwares were too small for them to be a full-fledged OS. So I went and downloaded this other one. Global version.
I read somewhere that I needed to format data before flashing a new image, so I did.
Booted TWRP.
Formated data (not Wipe)
Installed that ZIP from TWRP and booted correctly.
Booted TWRP again and flashed Magisk.
Got bootloop.
Back to stock image via fastboot.
Last try
Booted TWRP.
Formatted data.
Installed MIUI via TWRP.
Without rebooting, flashed Magisk and no-verity-opt-encrypt-6.0.zip.
This got past bootlogo ("Unlocked" message changed to "powered by Android") but got stuck there. Not booting at all.
Right now I'm back to the last try, booting MIUI successfully but without Magisk nor no-verity-opt-encrypt.
I kinda have no more ideas left. I understand this is a new device but I can't understand why people claim the have been able to install Magisk and I can't! Other thoughts were, maybe they were running MIUI 10 Beta and it only works with that version? I'm unsure about that.
Can someone lend me a hand? What am I missing?
Thank you!!
EDIT: FIX!
Over here, user @richardyusan helped me out with an extra step.
What I did:
Installed Magisk V16.7.
Installed DM-VERITY AND FORCED ENCRYPTION DISABLER.
Performed fastboot format userdata.
Rebooted.
And I got my phone booting with Magisk Installed!
Even though I couldn't install any module, (every install claimed I needed Magisk v15+). I read some threads and with a Magisk Direct re-install (from its app) I got Magisk downgraded to v16 and everything worked perfectly!
Hope this works out for everyone having this problem!
have you tried to use Magisk 16.4,
if not, try to follow this guide:
https://www.theandroidsoul.com/xiaomi-mi-8-root/
gulp79 said:
have you tried to use Magisk 16.4,
if not, try to follow this guide:
https://www.theandroidsoul.com/xiaomi-mi-8-root/
Click to expand...
Click to collapse
Thank you for the fast reply!
I followed that guide and tried these steps:
fastboot boot mi8-twrp-3.2.2.img
Unencrypted via Pattern
Flashed Magisk v16.4 + DM verity disabler file
Reboot
But I'm still stuck at "powered by Android" bootlogo.
Normally it boots within 5 seconds but now it's taking forever. I'll wait a few minutes to see what happens.
I'm attaching some screenshots of the install process.
Padlite said:
Thank you for the fast reply!
I followed that guide and tried these steps:
fastboot boot mi8-twrp-3.2.2.img
Unencrypted via Pattern
Flashed Magisk v16.4 + DM verity disabler file
Reboot
But I'm still stuck at "powered by Android" bootlogo.
Normally it boots within 5 seconds but now it's taking forever. I'll wait a few minutes to see what happens.
I'm attaching some screenshots of the install process.
Click to expand...
Click to collapse
Ok,
but if you install Magisk 16.4, don't install also DM verity disabler.
DM verity disabler is needed if you don't want to root (see poin 14 in the linked guide).
Hope it works...
gulp79 said:
Ok,
but if you install Magisk 16.4, don't install also DM verity disabler.
DM verity disabler is needed if you don't want to root (see poin 14 in the linked guide).
Hope it works...
Click to expand...
Click to collapse
If I only flash Magisk 16.4, then phone shows "Powered by Android" and instantly reboots into stock recovery.
Only way to get it back booting, is performing fastboot flash boot boot.img from stock dipper_global_images_V9.5.13.0.OEAMIFA_20180714.0000.00_8.1_global image
I read somewhere about official and unofficial bootloader unlock. I didn't unlock the bootloader myself. Maybe it has something to do with it?
PS: Anyone had any luck using Magisk with MIUI 9.5.13?
Did you try with a newer magisk version ? ... 16.7 was released 15 day ago
https://github.com/topjohnwu/Magisk/releases
Direct link: https://github.com/topjohnwu/Magisk/releases/download/v16.7/Magisk-v16.7.zip
It´s a good practice to use magisk_uninstaller before flash new one if you had problems.
Direct link: https://github.com/topjohnwu/Magisk/releases/download/v16.7/Magisk-uninstaller-20180719.zip
Please tell us if it´s works
Seems that also others users have this problem
https://forum.xda-developers.com/showpost.php?p=77234924&postcount=6312
punk84z said:
Did you try with a newer magisk version ? ... 16.7 was released 15 day ago
https://github.com/topjohnwu/Magisk/releases
Direct link: https://github.com/topjohnwu/Magisk/releases/download/v16.7/Magisk-v16.7.zip
It´s a good practice to use magisk_uninstaller before flash new one if you had problems.
Direct link: https://github.com/topjohnwu/Magisk/releases/download/v16.7/Magisk-uninstaller-20180719.zip
Please tell us if it´s works
Click to expand...
Click to collapse
I just tried that. Uninstalling and re-installing v16.7. Although it seems now it's doing a few more steps, I'm still getting the recovery bootloop.
Install log screenshot attached.
gulp79 said:
Seems that also others users have this problem
https://forum.xda-developers.com/showpost.php?p=77234924&postcount=6312
Click to expand...
Click to collapse
Exactly that. Maybe we'll need to wait for a supported Magisk version. I'm still wondering what's the difference between our Mi8's that some can get Magisk working and some not. ?
I am running Magisk stable and tmiui 10 from Xiaomi. Eu without any problems.
I have a Mi 8 se and i install the eu rom boot the phone , reboot to twrp wipe and factory reset and installed magisk 16.4 .this is how works for me
i have the same problem too..when using china stable rom 16.7 magisk can be installed successfully tried many times...
flashing global version seems to have this issue...
tried all this steps too but no luck in global rom...
Padlite said:
Hey there! I just got my Xiaomi Mi8 from HK Goldway at Aliexpress. It came with its bootloader already unlocked and a Global ROM flashed.
I wanted to install Magisk but failed horribly . I've already done that to several phones (my last one was a Moto X Play, and it worked without major complications). But with this one, it seems I can't get past the bootlogo.
Stock Fastboot image used:
dipper_global_images_V9.5.13.0.OEAMIFA_20180714.0000.00_8.1_global
This is what I've tried so far:
First try
Flashed TWRP for Mi8 version 0711.
Flashed Magisk.
Got a bootloop.
Reflashed stock image via Fastboot.
Second try
Booted (not flashed) TWRP.
Tried to install latest global weekly from this thread.
Also got a bootloop.
Reflashed stock image via Fastboot.
Third try
I thought that those flashable ZIP firmwares were too small for them to be a full-fledged OS. So I went and downloaded this other one. Global version.
I read somewhere that I needed to format data before flashing a new image, so I did.
Booted TWRP.
Formated data (not Wipe)
Installed that ZIP from TWRP and booted correctly.
Booted TWRP again and flashed Magisk.
Got bootloop.
Back to stock image via fastboot.
Last try
Booted TWRP.
Formatted data.
Installed MIUI via TWRP.
Without rebooting, flashed Magisk and no-verity-opt-encrypt-6.0.zip.
This got past bootlogo ("Unlocked" message changed to "powered by Android") but got stuck there. Not booting at all.
Right now I'm back to the last try, booting MIUI successfully but without Magisk nor no-verity-opt-encrypt.
I kinda have no more ideas left. I understand this is a new device but I can't understand why people claim the have been able to install Magisk and I can't! Other thoughts were, maybe they were running MIUI 10 Beta and it only works with that version? I'm unsure about that.
Can someone lend me a hand? What am I missing?
Thank you!!
Click to expand...
Click to collapse
i allso hade that problem
wen i got my phone it was with global rom
then i flashed twrp
didt like they said
wipe dalvik cache an cache an factory reset
flashed miui eu rom
then flashed twrp again rebooted into recovery
flashed magisk 16.4
ended up in staying on android logo
then i try format data an didt it all again
still android logo an nothing more
well then i didt what i allways didt on my other devices
i wiped dalvik cache
cache
data
system
then i flashed eu rom
an twrp again rebooted into recovery again
then flashed magisk 16.4
rebooted system an now it booted up
REMEMBER to manke a backup before flashing all off thise things otherwice u wont have the option to go back if something goes wrong
-fluffy- said:
i allso hade that problem
wen i got my phone it was with global rom
then i flashed twrp
didt like they said
wipe dalvik cache an cache an factory reset
flashed miui eu rom
then flashed twrp again rebooted into recovery
flashed magisk 16.4
ended up in staying on android logo
then i try format data an didt it all again
still android logo an nothing more
well then i didt what i allways didt on my other devices
i wiped dalvik cache
cache
data
system
then i flashed eu rom
an twrp again rebooted into recovery again
then flashed magisk 16.4
rebooted system an now it booted up
REMEMBER to manke a backup before flashing all off thise things otherwice u wont have the option to go back if something goes wrong
Click to expand...
Click to collapse
Well maybe the critical step is to wipe everything, including System.
Did you Format anything instead of Wipe this last try?
Also, could you please share a link from that working MIUI rom?
Thank you!
Sorry for double-posting, but I wanted to notify you I GOT IT!
Over here, user @richardyusan helped me out with an extra step.
What I did:
Installed Magisk V16.7
Installed DM-VERITY AND FORCED ENCRYPTION DISABLER.
Performed fastboot format userdata
Rebooted
And I got my phone booting with Magisk Installed!
Even though I couldn't install any module, (every install claimed I needed Magisk v15+). I read some threads and with a Magisk Direct re-install (from its app) I got Magisk downgraded to v16 and everything worked perfectly!
Here are some screenshots!
Padlite said:
Sorry for double-posting, but I wanted to notify you I GOT IT!
Over here, user @richardyusan helped me out with an extra step.
What I did:
Installed Magisk V16.7
Installed DM-VERITY AND FORCED ENCRYPTION DISABLER.
Performed fastboot format userdata
Rebooted
And I got my phone booting with Magisk Installed!
Even though I couldn't install any module, (every install claimed I needed Magisk v15+). I read some threads and with a Magisk Direct re-install (from its app) I got Magisk downgraded to v16 and everything worked perfectly!
Here are some screenshots!
Click to expand...
Click to collapse
Is Google Assistant ("OK Google") working for you now as well?
I just flashed magisk v16.0 over the Miui 8.7.26 build and it booted without issues.
japancakes said:
Is Google Assistant ("OK Google") working for you now as well?
Click to expand...
Click to collapse
I just checked and no. If I go to Google Settings -> Voice, Voice Match is disabled because "This feature is currently unavailable for this language". Even though it's set to English UK. Maybe there is some Magisk Module to enable it?
Thanks, followed these steps and it got magisk going on the recent global release. Only difference was i had to use fastboot erase userdata.
Padlite said:
Scroll down over this post to see anwer!
EDIT: FIX!
Over here, user @richardyusan helped me out with an extra step.
What I did:
Installed Magisk V16.7.
Installed DM-VERITY AND FORCED ENCRYPTION DISABLER.
Performed fastboot format userdata.
Rebooted.
And I got my phone booting with Magisk Installed!
Even though I couldn't install any module, (every install claimed I needed Magisk v15+). I read some threads and with a Magisk Direct re-install (from its app) I got Magisk downgraded to v16 and everything worked perfectly!
Hope this works out for everyone having this problem!
Click to expand...
Click to collapse
Hey guys im a toal newbie to this whole flash theme but Ive purchased a mi8 and i would like to use GooglePay and so on, could someone give me a step by step tutorial , how to install all this stuff on my device ?
Padlite said:
Sorry for double-posting, but I wanted to notify you I GOT IT!
Over here, user @richardyusan helped me out with an extra step.
What I did:
Installed Magisk V16.7
Installed DM-VERITY AND FORCED ENCRYPTION DISABLER.
Performed fastboot format userdata
Rebooted
And I got my phone booting with Magisk Installed!
Even though I couldn't install any module, (every install claimed I needed Magisk v15+). I read some threads and with a Magisk Direct re-install (from its app) I got Magisk downgraded to v16 and everything worked perfectly!
Here are some screenshots!
Click to expand...
Click to collapse
well i didt not flash dm-verity an mine pass saftynet
Hi,
I need some help
Today I successfully installed the newest stable Xiaomi.eu-ROM on my finally unlocked Mi8, using TWRP from here: https://forum.xda-developers.com/mi-8/development/recovery-twrp-3-2-3-1110-t3869729
TWRP is working flawlessly, but I didn't succeed in making root with Magisk to work.
What I did:
- I booted into TWRP
- formatted data
- rebooted back into TWRP
- flashed DM-verity disabler from here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
- flashed Magisk v18.0 right after from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
- wiped dalvik cache
- rebooted the phone
But everytime I did it, I didn't had root access (checked with Root Checker app) when the phone finally booted up to MIUI 10.1.2.0 (PEACNFI).
I even didn't have Magisk Manager showed up.
Can you tell me what I did wrong? I don't have a clue
Thanks a lot and best regards
Mischa
what does magisk manager tell you about your magisk installation status?
Strange thing...
After I rebooted the phone, there was no Magisk Manager nor the phone was rooted, what I checked with Root Checker app.
Then I used it a couple minutes before it became really laggy. My chosen theme disappeared back to stock theme, scrolling was nearly impossible and the screen went black.
I was not able to wake up the display again, so I held down the power button a couple seconds until the phone rebooted.
Now I saw that the Magisk Manager was installed, without me doing anything else than rebooting after the phone got unusable.
Weird, right? I read that there might be lags after installing Magisk, but that it's going to be like that was surprising.
Anyway, I have root now, TWRP works, Magisk v18 is installed. Now I only have to find some must-have-modules, e.g. like stereo-mod.
BTW, could it be that Netflix isn't working on rooted phones? I always get error 14 saying that the Netflix-service is not reachable even though I have internet connection.
hey dude i know this isnt a guide
but i followed your kind of direction after spending the whole afternoon and few hours in the evening to figure how to root this phone and finally it worked (so far)
thanks a lot my man
and i didnt even format after flashing twrp i hope it didnt **** up my phone
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.