Any time I flash a new module in Magisk, when the phone reboots everything crashes (i.e. Google has stopped working, system UI has stopped working, clock has stopped working, etc etc)
Everything will crash and then my phone will constantly reboot. I don't know how I fixed it but I got Viper and YouTube Vanced to work, but anytime I try flashing a new module, it will break Viper and start crashing and restarting again until I hard reset or just wait it out.
Any suggestions? I know that I flashed whatever TWRP is in the 11g root tutorial but there was a new TWRP made for the LG G6. Maybe if I flashed that one or does that not have anything to do with this?
Any suggestions would be appreciated
Magisk is up to date.
roger.hernandez91 said:
Any time I flash a new module in Magisk, when the phone reboots everything crashes (i.e. Google has stopped working, system UI has stopped working, clock has stopped working, etc etc)
Everything will crash and then my phone will constantly reboot. I don't know how I fixed it but I got Viper and YouTube Vanced to work, but anytime I try flashing a new module, it will break Viper and start crashing and restarting again until I hard reset or just wait it out.
Any suggestions? I know that I flashed whatever TWRP is in the 11g root tutorial but there was a new TWRP made for the LG G6. Maybe if I flashed that one or does that not have anything to do with this?
Any suggestions would be appreciated
Magisk is up to date.
Click to expand...
Click to collapse
What modules are you using? I've had it happen quite a bit for me but I figured out what the issue was.
beany23 said:
What modules are you using? I've had it happen quite a bit for me but I figured out what the issue was.
Click to expand...
Click to collapse
It happens with any module, but I've successfully got several installed and working such as viper, Greenify, YouTube vanced, Emoji one, Google product sans font, and Magisk Google DNS
What was the issue and how'd you fix it?
roger.hernandez91 said:
It happens with any module, but I've successfully got several installed and working such as viper, Greenify, YouTube vanced, Emoji one, Google product sans font, and Magisk Google DNS
What was the issue and how'd you fix it?
Click to expand...
Click to collapse
Easy. Uninstall magisk wipe cache 3 times then reboot recovery again then flash magisk 16.4 beta should fix your issue. Remember to download magisk 16.4 first then follow the above steps.
beany23 said:
Easy. Uninstall magisk wipe cache 3 times then reboot recovery again then flash magisk 16.4 beta should fix your issue. Remember to download magisk 16.4 first then follow the above steps.
Click to expand...
Click to collapse
When you say wipe cache 3 times, what do you mean by that? Go into recovery and wipe and keep rebooting three times?
Also, what method did you use to get into recovery each time and to flash Magisk?
roger.hernandez91 said:
When you say wipe cache 3 times, what do you mean by that? Go into recovery and wipe and keep rebooting three times?
Also, what method did you use to get into recovery each time and to flash Magisk?
Click to expand...
Click to collapse
No, you just need to go into recovery and wipe cache 3 times back to back to back. You can use the file manager in TWRP to check the cache after wiping to see if its clear. If it is, reboot to recovery and flash Magisk. If you have anymore issues let me know.
Metabolic12 said:
No, you just need to go into recovery and wipe cache 3 times back to back to back. You can use the file manager in TWRP to check the cache after wiping to see if its clear. If it is, reboot to recovery and flash Magisk. If you have anymore issues let me know.
Click to expand...
Click to collapse
Yes quick question, did you use Magisk uninstaller package from thread or just uninstall Magisk directly from the app?
Confused on how to uninstall Magisk without encrypting my device or loosing my boot or messing anything like that up
Also, wipe Dalvik cache and cache or just cache only?
Okay I guess I'm going to:
Boot into laf TWRP recovery
Flash Magisk uninstall zip
Wipe cache three times
Reboot into recovery
Flash Magisk v16.4 beta
Reboot system
Profit.... hopefully
Metabolic12 said:
No, you just need to go into recovery and wipe cache 3 times back to back to back. You can use the file manager in TWRP to check the cache after wiping to see if its clear. If it is, reboot to recovery and flash Magisk. If you have anymore issues let me know.
Click to expand...
Click to collapse
Great well I can't uninstall Magisk from recovery
Still getting error that TWRP can't mount /system
Can anybody help?
roger.hernandez91 said:
Great well I can't uninstall Magisk from recovery
Still getting error that TWRP can't mount /system
Can anybody help?
Click to expand...
Click to collapse
Sure you can. Magisk doesn't root the system so all of the files you need to discard are in /data and /cache. You need a copy of the stock kernel in image format, if Magisk didn't make a back up. I gotta say bro, I haven't uninstalled Magisk or tried, so I don't know what's going to happen when you do this.
If your phone force encrypts after flashing the kernel, you may be screwed and have to format data and lose everything. This could possibly also brick your device beyond help. Since you can't mount your system in TWRP, if for some reason it fails encryption or DM-Verify into a bootloop, from the LAF or recocery modification, it won't boot. At least, not until you find a way to mount the system, which I think will be near impossible.
With that being said, if you decide to move forward you can either wipe data and cache or remove the files one by one. Your choice.
Well I gotta say, I've had a hell of a day fixing this thing. System partition got wiped somehow and had to fight to get my backup restored, thankfully I had one. Basically came back from the dead. Ended up wiping my entire internal storage to get TWRP to shut the hell up about decrypting, flashed new recovery again, flashed Magisk v16.4 beta, and now I'm good to go. Didn't have any of the issues mentioned above. And now I'm not having /system mounting problems or the force quits upon flashing a new mod. Everything seems good.
Appreciate y'all. You guys are awesome for taking the time to help.
roger.hernandez91 said:
Okay I guess I'm going to:
Boot into laf TWRP recovery
Flash Magisk uninstall zip
Wipe cache three times
Reboot into recovery
Flash Magisk v16.4 beta
Reboot system
Profit.... hopefully
Click to expand...
Click to collapse
Don't do it from laf twrp flash the latest h872 recovery and do the steps u posted
beany23 said:
Don't do it from laf twrp flash the latest h872 recovery and do the steps u posted
Click to expand...
Click to collapse
Nah man I actually did have to do it from laf recovery because it wasn't working from regular recovery. Had to flash it from both and also formatted data and I was good to go. I got it all figured out.
Related
Hi everyone,
When I first received my phone a few days ago, I unlocked and rooted it. But then I noticed I wasn't passing safetynet so I unrooted it.
Eversince, when I try to reroot it, it won't boot. It stays stuck on the boot animation (I waited up to 20 minutes).
If I reflash the ROM, it boots. If I reflash the ROM, wipe davlik & cache, and root, it stays stuck on the boot animation.
So my guess was that it was not ROM related, nor cache related, so it must be caused by something on my data partition. But I don't want to wipe it if I have another way to fix it.
Any idea on what might be preventing my phone from booting when I root it?
Thanks!
after root do you have flashed superSU?
RotesMeerJogger said:
after root do you have flashed superSU?
Click to expand...
Click to collapse
Well I flashed superSU to root the phone!
But when I do it, it won't boot.
Probably image got corrupted, Download the zip of the rom "oxygen os zip", clean flash it through recovery, try to root again
Daman5202 said:
Probably image got corrupted, Download the zip of the rom "oxygen os zip", clean flash it through recovery, try to root again
Click to expand...
Click to collapse
When I flash if without root it boots perfectly, are you sure about the image being corrupted?
gigaboss said:
When I flash if without root it boots perfectly, are you sure about the image being corrupted?
Click to expand...
Click to collapse
As you said "it stucks on boot", many times the phone gets stuck on boot when the image is corrupted , its called soft brick. Try downloading the zip file of os, flash it through recovery. The img is probably facing some errors while booting with root access. Are you nougat user? 7.1? And are you using default recovery?
As most people have said here already, in general this should work. So which version of oxygenos are you running? And what recovery? Also, after flashing Supersu, you should not wipe caches as far as I know (forgot the source). Re-download the image, and flash it and directly after flash supersu (both in twrp) and your problem should be solved.
donny110 said:
As most people have said here already, in general this should work. So which version of oxygenos are you running? And what recovery? Also, after flashing Supersu, you should not wipe caches as far as I know (forgot the source). Re-download the image, and flash it and directly after flash supersu (both in twrp) and your problem should be solved.
Click to expand...
Click to collapse
OK I am sorry I was not clear enough, this is exactly what I have been doing!
I have TWRP, when I only flash the 3.5.4 OOS it works perfectly. When I flash OOS 3.5.4 and superSU it doesn't boot.
So the image doesn't seem corrupted, I re-downloaded it.
Is it clearer?
gigaboss said:
OK I am sorry I was not clear enough, this is exactly what I have been doing!
I have TWRP, when I only flash the 3.5.4 OOS it works perfectly. When I flash OOS 3.5.4 and superSU it doesn't boot.
So the image doesn't seem corrupted, I re-downloaded it.
Is it clearer?
Click to expand...
Click to collapse
Have you cleared caches before the flash? And are you using the Full OOS 3.5.4? And I assume the most recent Supersu? I did exactly that 2 days ago. Using the full OOS zip that is in one of the threads here on XDA (can't link on phone right now).
Btw. It can bootloop a few times and take awhile once you flash both.. If that doesn't work I guess it's beyond my knowledge. You might want to try if the same thing happens with 3.5.3
gigaboss said:
Hi everyone,
When I first received my phone a few days ago, I unlocked and rooted it. But then I noticed I wasn't passing safetynet so I unrooted it.
Eversince, when I try to reroot it, it won't boot. It stays stuck on the boot animation (I waited up to 20 minutes).
If I reflash the ROM, it boots. If I reflash the ROM, wipe davlik & cache, and root, it stays stuck on the boot animation.
So my guess was that it was not ROM related, nor cache related, so it must be caused by something on my data partition. But I don't want to wipe it if I have another way to fix it.
Any idea on what might be preventing my phone from booting when I root it?
Thanks!
Click to expand...
Click to collapse
I don't have my 3T yet to verify, but did you flash the zip which disables encryption and dm-verity?
EDIT: From the TWRP thread, step 10: http://forum.xda-developers.com/oneplus-3t/development/recovery-twrp-oneplus-3t-t3507308
Any update to this? I have the exact same problem; clean flash 3.5.4 OOS (tried it via twrp, adb sideload and MsmDownloadTool) then flash SuperSU via twrp (tried multiple SuperSU versions) and all results in sitting at the boot animation. I've let it sit for 2 hours and it never gets beyond boot animation. No matter what, I can't get SuperSU to work. However, I have no problem getting phh superuser to boot up. Any idea why SuperSU won't boot for me?
__McB__ said:
Any update to this? I have the exact same problem; clean flash 3.5.4 OOS (tried it via twrp, adb sideload and MsmDownloadTool) then flash SuperSU via twrp (tried multiple SuperSU versions) and all results in sitting at the boot animation. I've let it sit for 2 hours and it never gets beyond boot animation. No matter what, I can't get SuperSU to work. However, I have no problem getting phh superuser to boot up. Any idea why SuperSU won't boot for me?
Click to expand...
Click to collapse
I got to the bottom of my problem (but did not solve it somehow) by formatting and trying every possibility. I lost all my data :crying:
So here is what happens:
-I start with a clean ROM, root it, install kernel, everything works fine EXCEPT for safetynet that won't pass even with root switch
-I try to install suhide 0.55, the phone won't start anymore (stays on boot animation, tried to wait all night)
AND HERE IS THE WEIRD THING.
-If I dirty flash the rom to start over, it boots, if then I flash SuperSU, it won't boot!! As if suhide was still in the data partition and preventing the phone from booting!!
So it means that if I try to install suhide once, I am not able to boot with root anymore... I need to format my data partition and start all over again.
Hmm. My issue is slightly different, I guess. I'm not even attempting suhide, just SuperSU. No matter what, I can't boot up once I flash SuperSU. Guess I'll give it another try with the new 2.79 sr2 and oos4.
Thanks!
__McB__ said:
Hmm. My issue is slightly different, I guess. I'm not even attempting suhide, just SuperSU. No matter what, I can't boot up once I flash SuperSU. Guess I'll give it another try with the new 2.79 sr2 and oos4.
Thanks!
Click to expand...
Click to collapse
Did you have any luck with this? I'm having the same issue. Flash the 4.0.2 update and boots fine. Flash SuperSU or phh (I've tried both!) and I just sit at the boot animation for hours until I get angry and restore nandroid to 3.5.4.
hyperblau said:
Did you have any luck with this? I'm having the same issue. Flash the 4.0.2 update and boots fine. Flash SuperSU or phh (I've tried both!) and I just sit at the boot animation for hours until I get angry and restore nandroid to 3.5.4.
Click to expand...
Click to collapse
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
I had a similar issue with my op3t after root it, I wipe data but it won't start, I just flash the zip 5.1 no verity opt encrypt and should be work fine without flashing supersu:good:
hyperblau said:
Did you have any luck with this? I'm having the same issue. Flash the 4.0.2 update and boots fine. Flash SuperSU or phh (I've tried both!) and I just sit at the boot animation for hours until I get angry and restore nandroid to 3.5.4.
Click to expand...
Click to collapse
No, never got it working. Upgraded to 4.0.2 and never looked back.
Maybe you already tried this version.. Otherwise...
Hello,
I have a problem with my 3T. I updated magisk yesterday via magisk manager from 11.2 to 11.5. After the update my screen was completely black, the funny thing is if I press my power button long enough the reboot menu pops up. I can boot into recovery, the bootanimation is working but the ROM itself isn't visible.
I tried reflashing magisk via recovery, ROM+magisk via recovery, ROM via recovery and uninstalled magisk via recovery. Nothing works, the last thing I can try is a complete factory reset.
Does anyone has maybe an idea what else I can do?
I would appreciate any form of hint
yup i had the same thing, used the brick recovery tool and was fine but when i re unlocked the bootloader i forgot it wipes internal data and lost all my pics music and titanium backups. Very annoyed to say the least.
EuEra said:
yup i had the same thing, used the brick recovery tool and was fine but when i re unlocked the bootloader i forgot it wipes internal data and lost all my pics music and titanium backups. Very annoyed to say the least.
Click to expand...
Click to collapse
That solved my issue, didn't realize that I really bricked my device. Sadly it wiped my data also!
Thanks for your advice!
I've experienced this about 3 times over the last 4 months, and had to restore a full backup each time. Basically afraid to do anything with Magisk at this point. This really needs to be fixed.
It's probably because the Magisk updater is interfering with the kernel.
Every time Magisk is updated, I always dirty flash my current ROM and flash the new version of Magisk over it. I can then flash a custom kernel and everything still works flawlessly.
Anova's Origin said:
It's probably because the Magisk updater is interfering with the kernel.
Every time Magisk is updated, I always dirty flash my current ROM and flash the new version of Magisk over it. I can then flash a custom kernel and everything still works flawlessly.
Click to expand...
Click to collapse
I did that when i switched from official to open beta, and everything went fine, then i installed a module, rebooted and got blackscreen again
Anova's Origin said:
It's probably because the Magisk updater is interfering with the kernel.
Every time Magisk is updated, I always dirty flash my current ROM and flash the new version of Magisk over it. I can then flash a custom kernel and everything still works flawlessly.
Click to expand...
Click to collapse
It's not the kernel, the black screen has occurred twice when just installing a module with no modifications to /boot.
dre-z said:
Hello,
I have a problem with my 3T. I updated magisk yesterday via magisk manager from 11.2 to 11.5. After the update my screen was completely black, the funny thing is if I press my power button long enough the reboot menu pops up. I can boot into recovery, the bootanimation is working but the ROM itself isn't visible.
I tried reflashing magisk via recovery, ROM+magisk via recovery, ROM via recovery and uninstalled magisk via recovery. Nothing works, the last thing I can try is a complete factory reset.
Does anyone has maybe an idea what else I can do?
I would appreciate any form of hint
Click to expand...
Click to collapse
Fix for me was to boot twrp, manually wipe system, data, caches etc (NOT internal storage box), then clean install the OS in twrp. Keeps your data and encryption then.
Just happened again. Ugh. Anybody manage to recover their existing data partition from this?
---------- Post added at 01:21 PM ---------- Previous post was at 01:15 PM ----------
I think this is the fundamental issue: https://github.com/topjohnwu/Magisk/issues/185
I've not experienced anything like this on my OP3T. I did see something similar on my Nexus 6 a couple of times, but could never quite get a grip on what caused it (I had a lot of other issues with that device ).
Is there any particular module that has been known to cause the issue (for testing)?
Didgeridoohan said:
I've not experienced anything like this on my OP3T. I did see something similar on my Nexus 6 a couple of times, but could never quite get a grip on what caused it (I had a lot of other issues with that device ).
Is there any particular module that has been known to cause the issue (for testing)?
Click to expand...
Click to collapse
Nope, I've had this happen with multiple modules, including App Systemizer, ad-free YouTube, and OP3/T channel bonding enabler. Based on the file size changes in magisk.img, I legitimately think that the linked GitHub issue is the root cause. I think the only consistent repro is to flash different versions of modules while rebooting repeatedly.
Problem might be corrupted magisk.img during resize.
vemacs said:
Just happened again. Ugh. Anybody manage to recover their existing data partition from this?
---------- Post added at 01:21 PM ---------- Previous post was at 01:15 PM ----------
I think this is the fundamental issue: https://github.com/topjohnwu/Magisk/issues/185
Click to expand...
Click to collapse
I had the same issue when trying to install xposed 87.1 through MagiskManager (black screen and repeated vibration).
On my J5 I just removed the battery and booted into twrp, then I uninstalled magisk with the uninstall-zip, wiped dalvik an cache, rebooted once and everything works.
I reinstalled magisk in twrp and installed xposed 87.0 through the material xposed-installer and everything works.
No data loss.
The issue on GitHub was closed with a comment saying that it's likely fixed in latest Magisk (13.1). FWIW I haven't seen it occur after running 13 beta for a while.
My op3 was bricked again today after the update. Funny thing is, this time I had not installed any module. So the problem doesn't seem to be fixed.
pls someone should help me i tried to root my android v10 infinix note8i with magisk patch boot img file using adb fastboot when i tranfer the file and reboot the phone is not booting and not gettig into recovery mode, just blank screen when a turn on pls help me out with solution
same but my problem is kind of stupid because someone rooted my phone in another way and magisk says it is installed and needs updating but it is actually not and the biggest problem is when i unroot my phone the stupid rmm locks gets enabled and boom i can't open twrp recovery because it is not an offical binary so i got stuck there i flashed a stock rom got it fixed but i still can't do it
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
I'm trying to instal Magisk 19.3 through Magisk Manager Version: v7.3.4
and getting this error:
Device platform: arm64-v8a
Coping image to cache
unpacking boot image
!unsupported/unknown image format
!installation failed
Any ideas how to solve it?
I have used Stable Magisk Version: v19.3 (also tried Beta Magisk Version: v19.4)
Maybe something's wrong with the boot image? Try to re-download magisk stable zip and reintall it via TWRP.
@LogicalMaverick, tried to download it again from this thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 but still the same error message
I did try to install in TWRP mode and also from the Magisk Manager and still not working.
When I install in TWRP mode the result is the phone is getting into loop mode and the only way out if it is to uninstall it
try to wipe data after flashing magisk before booting to system
Kzak25 said:
try to wipe data after flashing magisk before booting to system
Click to expand...
Click to collapse
Yeah, for me there are 2 ways:
1. Wipe data after flashing magisk before booting system
2. Complete phone setup first after installing new ROM, and then boot into recovery, then you're good to install magisk
Kzak25 said:
try to wipe data after flashing magisk before booting to system
Click to expand...
Click to collapse
Didn't work. Still getting to the same issue where the phone is stuck in bootloop and the only way out of it is to uninstall Magisk
What phone are you using?
cohenelad said:
Didn't work. Still getting to the same issue where the phone is stuck in bootloop and the only way out of it is to uninstall Magisk
Click to expand...
Click to collapse
are you on stock or custom ROM (if stock what MIUI Ver)
Kzak25 said:
are you on stock or custom ROM (if stock what MIUI Ver)
Click to expand...
Click to collapse
I'm on stock ROM.
Was on MIUI 10.3.2 Now I'm on 10.4.8.
Tried to install Magisk on bot ROM through TWRP and didn't work.
Tried also through Magisk manager and didn't work
When I installed TWRP on my phone it asked if I want to give it permission to modify the system or to leave it read only mode.
I choose read only mode as I thought it will be easier to get OTA updates.
Maybe that's the reason Magisk cannot be installed correctly ?
TIA for your help
cohenelad said:
I'm on stock ROM.
Was on MIUI 10.3.2 Now I'm on 10.4.8.
Tried to install Magisk on bot ROM through TWRP and didn't work.
Tried also through Magisk manager and didn't work
When I installed TWRP on my phone it asked if I want to give it permission to modify the system or to leave it read only mode.
I choose read only mode as I thought it will be easier to get OTA updates.
Maybe that's the reason Magisk cannot be installed correctly ?
TIA for your help
Click to expand...
Click to collapse
Yeah i think you should give TWRP all permission when you boot into it the first time
you can re-flash TWRP and try again
reboots to fastboot
Kzak25 said:
Yeah i think you should give TWRP all permission when you boot into it the first time
you can re-flash TWRP and try again
Click to expand...
Click to collapse
I can flash over twrp. then it says no rom installed so flash over magisk-error unknown image. this is a fresh download tried 3 new downloads same error. use adb sideload to flash rom. successful do the reboot and it reboots to fastboot. what do i do
Any ideas? It just give me an error 1. Tried several versions and still the same problem.
Is it not needed anymore?
After installing the rom or magisk you must restart from the twrp in recovery mode and voila, you can install. in fact I cannot install 2 things in a row, I must install 1 at a time, restarting in recovery mode
17007501 said:
After installing the rom or magisk you must restart from the twrp in recovery mode and voila, you can install. in fact I cannot install 2 things in a row, I must install 1 at a time, restarting in recovery mode
Click to expand...
Click to collapse
Tried it several times. Wiped cache etc and restarded the phone. Nothing helps.
Try this https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389/amp/
17007501 said:
Try this https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389/amp/
Click to expand...
Click to collapse
EDIT: Nope Flashing was fine but after the reboot i get a bootloop with only mi logo showing.
So now what?
you can try entering twrp, format data and flash dm
17007501 said:
you can try entering twrp, format data and flash dm
Click to expand...
Click to collapse
Nope. Not working
Use LR twrp, there's "script" file
Boot into recovery
Format data, keep in recovery
Transfer script and flash
Reboot to recovery
Transfer ROM, GAPPS, Magisk, and script
Flash ROM, GAPPS, then script
Reboot to recovery
Flash Magisk then script
Reboot to recovery
Format data, keep in recovery
Transfer script and flash
Reboot to recovery
Reboot to system
I actually had the same error. instead of booting, I flashed the LineageOS ROM I wanted to load and it worked fine.
Perhaps some phones do not have this check ? For me it's a Galaxy S9. I have TWRP 3.5.x now and LineageOS 18.1 and no message of knox tripped or anything yet. Not rooted yet though