Hi all,
Just tried to flash the latest Magisk (16.0) from TWRP on my honor 8 running B360 and am now in a a bootloop.. Nothing new fixing this but does anyone know what version of magisk will work or why this could have happened? I'm keen to get it working!
Cheers
So I've tried to flash back to an unrooted rom and must've broken something because I now cannot get into TWRP at all. I fastboot flash version 3.1.1-1 which has worked for me countless times and fastboot says it flashes fine but when I try and boot into it with power+vol up the phone goes off for a second, vibrates, pauses for another second before vibrating again and then showing the device cannot be trusted screen. Has anyone ever had this? I'm not sure what else to try here (I also tried flash stock recovery and it does the same thing)
Edit: Got TWRP back, I think my device must be on an earlier version (even though it's corrupt). In case anyone else finds this, this thread helped me https://forum.xda-developers.com/honor-8/help/please-help-boot-enter-recovery-t3660408/page3
First of all: if after flash magisk and you have a bootloop, just flash the uninstall package from magisk website. This package revert back to the original kernel and uninstall magisk.
Second job: if you want to install magisk, first install magisk manager app. And before flash the magisk from twrp, in the magisk manager check the "Preserve force encryption" and "Preserve AVB 2.0/dm-verity". If this option (or just the first) not checked, the magisk flashing results is a bootloop.
Mumtaz77 said:
First of all: if after flash magisk and you have a bootloop, just flash the uninstall package from magisk website. This package revert back to the original kernel and uninstall magisk.
Second job: if you want to install magisk, first install magisk manager app. And before flash the magisk from twrp, in the magisk manager check the "Preserve force encryption" and "Preserve AVB 2.0/dm-verity". If this option (or just the first) not checked, the magisk flashing results is a bootloop.
Click to expand...
Click to collapse
Oh thanks for the info I didn't know that (have never used magisk) - I'll give it a go tomorrow!
JoshSnitz said:
Oh thanks for the info I didn't know that (have never used magisk) - I'll give it a go tomorrow!
Click to expand...
Click to collapse
Unfortunately it didn't work - resulted in the bootloop again
Latest stable v16 works fine.
What twrp version have?
You have the 3.1.1 openkirin version?
xuso77 said:
Latest stable v16 works fine.
What twrp version have?
You have the 3.1.1 openkirin version?
Click to expand...
Click to collapse
Yeah, using twrp-3.1.1-1-frd.img. Phone is EMUI 5.0, android 7.0 FRD-L09C432B360
Edit: I have the AL version with dual sim that I've re-branded. Could this be causing an issue?
I don't think so, but I don't know.
Can you try to flash the last magisk developer version, or wait for another user that rebranded the honor.
Good luck!
You have to use older version of Magisk. V16 only works on newer firmwares. Try v13 or v14, they both will work flawlessly.
hackslash said:
You have to use older version of Magisk. V16 only works on newer firmwares. Try v13 or v14, they both will work flawlessly.
Click to expand...
Click to collapse
Oh, I'll give it a go. Is it more reliable to just flash through fastboot or the zip through twrp?
Edit: Both v14 and 13 gives boot loop when flashed from twrp
Related
Hello XDA!
It's been a while since I did 'modding' on phones, I think I started with the OP1 back in 2014 but have not really been keeping up ever since. I am now on 5.1.5 and running official OOS with magisk and xposed for gravitybox.. Can I just disable magisk and xposed, do the OTA update and then re-enable or do I have to uninstall them fully? Or can I just do the OTA right now?
Sorry for what might be a really obvious answer.
Thank you!
You can do the OTA but if you want magisk (and then xposed systemless) i suggest you to install TWRP after update and you need in all cases to re-do root process
Hitman478™ said:
You can do the OTA but if you want magisk (and then xposed systemless) i suggest you to install TWRP after update and you need in all cases to re-do root process
Click to expand...
Click to collapse
Ahh I see. Because xposed is now systemless it doesn't matter if I leave it enabled right? Is the new official TWRP without any dangerous bugs?
Thanks for your swift reply!!
maybe to help you all
me: 5.1.5, unlocked bootloader, unofficial TWRP from thread by wuxianlin, magisk 16.4
my procedure was to change to official twrp which can be done easily by
downloading the twrp installer from official site, put to internal storage
flash twrp official installer
still in recovery, select reboot: recovery
flash magisk
boot system
now download full 5.1.6 signed flashable zip
recovery: flash 5.1.6
reflash recovery
reboot recovery
flash magisk
boot system
now you have rooted 5.1.6 with official twrp and magisk, no wipe needed
oneplus6 ha a/b partition. so if you installed magisk 16.4 already. just OTA. when it's done don't reboot yet. enter magisk manager, choose install on the second partition. reboot.
trivita said:
oneplus6 ha a/b partition. so if you installed magisk 16.4 already. just OTA. when it's done don't reboot yet. enter magisk manager, choose install on the second partition. reboot.
Click to expand...
Click to collapse
This will useful only if don't have TWRP, in other case you'll lose twrp in this way
---------- Post added at 15:21 ---------- Previous post was at 15:19 ----------
TheHighLife said:
Ahh I see. Because xposed is now systemless it doesn't matter if I leave it enabled right? Is the new official TWRP without any dangerous bugs?
Thanks for your swift reply!!
Click to expand...
Click to collapse
TWRP official has no bug, the only thing i don't know is if backup/restore is working fine, if you install ota via TWRP and then flash (without reboot) twrp.zip and magisk, after reboot you'll find out that system is exactly the same it was before updating
The only thing u need to disable before updates are overlays through substratum, I also remove any security like finger prints, face unlock and pin or patterns too just in case. Once u flash update u will have to reflash magisk and xposed too
trivita said:
oneplus6 ha a/b partition. so if you installed magisk 16.4 already. just OTA. when it's done don't reboot yet. enter magisk manager, choose install on the second partition. reboot.
Click to expand...
Click to collapse
Did anyone try this?
defsix said:
Did anyone try this?
Click to expand...
Click to collapse
i did this myself
idontcare abt the twrp at all
im perfectly fine with stock recovery
trivita said:
i did this myself
idontcare abt the twrp at all
im perfectly fine with stock recovery
Click to expand...
Click to collapse
Same as that. I'll give it a try next update.
Sent from my Brain using my Keyboard
How do you install to second partition? I only get install or uninstall Magisk (16.70) on the screen. i AM NEW TO MAGISK.
Hi, the title says almost all... I can't get past the TWRP screen on both official TWRP and Bluespark one, only solution is flashing Magisk but i have to remove it in order to use some Apps that detect it, any advice...?
Fastboot flash a 5.1.9 rom and update from there, if ur not gonna run magisk do you need twrp?
Did you try to use the latest Uninstaller?
whizeguy said:
Fastboot flash a 5.1.9 rom and update from there, if ur not gonna run magisk do you need twrp?
Did you try to use the latest Uninstaller?
Click to expand...
Click to collapse
I need twrp so I can flash magisk if I need it.
And yes, tried to use latest versions of Magisk and, obviously, the Uninstaller, every time I run the Uninstaller it just boot back to twrp.
Anyway I've solved by dirty flashing Pie, now it's working, thanks
Installation steps are as follow when updating from 9.0.2 to 9.0.3.
Flashed full zip from bluspark twrp
Immediately flash bluspark twrp zip after that
Reboot into recovery
Flashed Magisk v18 zip (Also tried v17.3 zip)
Reboot system
After that, boot animation is shown and followed by Shutting down dialog with my wallpaper behind it, then rebooted into TWRP itself. I cannot reboot into system until I flash full zip again, but I lost my root now. Above steps were used when I update from older version to 9.0.2 and it was ok at that time. Bluspark latest stable (3.2.3) was used. Any idea how to fix please? Thanks.
xtartrackR said:
Installation steps are as follow when updating from 9.0.2 to 9.0.3.
Flashed full zip from bluspark twrp
Immediately flash bluspark twrp zip after that
Reboot into recovery
Flashed Magisk v18 zip (Also tried v17.3 zip)
Reboot system
After that, boot animation is shown and followed by Shutting down dialog with my wallpaper behind it, then rebooted into TWRP itself. I cannot reboot into system until I flash full zip again, but I lost my root now. Above steps were used when I update from older version to 9.0.2 and it was ok at that time. Bluspark latest stable (3.2.3) was used. Any idea how to fix please? Thanks.
Click to expand...
Click to collapse
flash magisk uninstaller, then reinstall magisk v18 and add one module at a time to understand which one causes bootloop
It worked. Thank you!
Just a heads up next upgrade: disable all (except ROMs maybe) magisk mods, also disable substratum themes before updates. They can make your phone bootloop or system UI crash. Glad it works fine now
For me, flashing magisk uninstall and reinstalling v18 still didn't work. I had to install beta version 17.3 after flashing the uninstall, then I installed magisk manager when it successfully booted and finally updated to v18 through the manager. Not sure why v18 wouldn't work even after flashing magisk uninstall, but 17.3 worked.
I also had this problem on a fresh OS install. Had to install:
Magisk 17 then
Magisk 18 then
Magisk 19
This is a crazy bug
Sepero said:
I also had this problem on a fresh OS install. Had to install:
Magisk 17 then
Magisk 18 then
Magisk 19
This is a crazy bug
Click to expand...
Click to collapse
Have you tried magisk uninstaller and fresh start without any module? In my case one of my custom made module was causing problem because i didn't update it to latest template. Try one module at a time to find the culprit.
You need to disable all magisk modules before doing system update, otherwise it goes in auto shutdown and then you need to flash magisk uninstaller and then re-flash magisk
And remember to remove pin/password lock too
OFFTOPIC:
I have 9.0.3 + TWRP. What are exactly steps do nuke, clean, and reinstall 9.0.3? Need info about correct order and options on Format on TWRP.
Thank you.
Mord0rr said:
OFFTOPIC:
I have 9.0.3 + TWRP. What are exactly steps do nuke, clean, and reinstall 9.0.3? Need info about correct order and options on Format on TWRP.
Thank you.
Click to expand...
Click to collapse
Format DATA from TWRP then boot to system once and when it's ready you can reboot to twrp to install magisk if you want
Hi everyone,
I had recently upgraded to android 10 (clean flash) and installed TWRP and Magisk and everything was fine. However, one fine day, I performed a random reboot and my phone got stuck in a bootloop. I proceeded to boot into TWRP and flashed Magisk uninstaller and the phone booted again. But now, the problem is that every time I try to flash Magisk, I end up in the same bootloop. I am unsure how to get Magisk installed again and I don't want to Clean flash and set up the device all over again.
Please help me out XDA.
Thank you!
ImperatorShade said:
Hi everyone,
I had recently upgraded to android 10 (clean flash) and installed TWRP and Magisk and everything was fine. However, one fine day, I performed a random reboot and my phone got stuck in a bootloop. I proceeded to boot into TWRP and flashed Magisk uninstaller and the phone booted again. But now, the problem is that every time I try to flash Magisk, I end up in the same bootloop. I am unsure how to get Magisk installed again and I don't want to Clean flash and set up the device all over again.
Please help me out XDA.
Thank you!
Click to expand...
Click to collapse
Hello,
Which instruction did you follow?
What version of rom, twrp and magisk did you have? (maybe with file names).
strongst said:
Hello,
Which instruction did you follow?
What version of rom, twrp and magisk did you have? (maybe with file names).
Click to expand...
Click to collapse
Thank you for the response strongst!
I am using the 10.0.1 GM57AA build right now. Updated directly from 10.0.0 by flashing rom in local updater, then without reboot, flashed twrp installer and magisk in inactiv slot, in magisk iteslf (followed your guide and the one Kollachi had put up).
Magisk version is 20.1 and TWRP version is 3.3.1-70.
Everything was working fine for about two months before one reboot started causing the bootloop. (I made no other changes to magisk before this reboot)
Thanks!
ImperatorShade said:
Thank you for the response strongst!
I am using the 10.0.1 GM57AA build right now. Updated directly from 10.0.0 by flashing rom in local updater, then without reboot, flashed twrp installer and magisk in inactiv slot, in magisk iteslf (followed your guide and the one Kollachi had put up).
Magisk version is 20.1 and TWRP version is 3.3.1-70.
Everything was working fine for about two months before one reboot started causing the bootloop. (I made no other changes to magisk before this reboot)
Thanks!
Click to expand...
Click to collapse
Maybe you did have any magisk modules left?
Have you tried an older magisk version?
strongst said:
Maybe you did have any magisk modules left?
Have you tried an older magisk version?
Click to expand...
Click to collapse
Thanks for the fast response! Yes, I tried Magisk 19.3 ver but got the same issue.
ImperatorShade said:
Thanks for the fast response! Yes, I tried Magisk 19.3 ver but got the same issue.
Click to expand...
Click to collapse
And are there any magisk modules or mods left? It can be the reason for this.
Are there any errors within the log while flashing?
You have the twrp guacamole unified from mauronofrio 3.3.1-70, right? You can try 3.3.1-73 if you want.
There were no errors when flashing. But I'm not sure whether I had disabled Magisk Modules before flashing OxygenOS 10. Anyway, what would be the best way to untwrp and clean flash?
So I update my device in last OTA update, OOS version is oxygen OS 10.0.3.GM21AA
Twrp version is Twrp-3.3.1-74-guacamole-unified-Q (tried official and unofficial both)
Magisk 20.1.
Now when ever i flash Magisk device gose in to Fastboot (bootloop) & if i uninstall magsik with uninstall zip, device behave normal and boot into OOS system,
What is the problem and how to get Magisk again??
Do you have any modules installed?
aNGERY said:
Do you have any modules installed?
Click to expand...
Click to collapse
That's what I was going to ask. Sounds like a module issue to me.
Nambardar said:
So I update my device in last OTA update, OOS version is oxygen OS 10.0.3.GM21AA
Twrp version is Twrp-3.3.1-74-guacamole-unified-Q (tried official and unofficial both)
Magisk 20.1.
Now when ever i flash Magisk device gose in to Fastboot (bootloop) & if i uninstall magsik with uninstall zip, device behave normal and boot into OOS system,
What is the problem and how to get Magisk again??
Click to expand...
Click to collapse
RenovateIce ROM (9.0)?
Try: TWRP->Advanced->File Manager->/data->/adb->/modules->RIce module, or something like that-> folder icon->delete->(swipe) and Reboot->System
Nambardar said:
So I update my device in last OTA update, OOS version is oxygen OS 10.0.3.GM21AA
Twrp version is Twrp-3.3.1-74-guacamole-unified-Q (tried official and unofficial both)
Magisk 20.1.
Now when ever i flash Magisk device gose in to Fastboot (bootloop) & if i uninstall magsik with uninstall zip, device behave normal and boot into OOS system,
What is the problem and how to get Magisk again??
Click to expand...
Click to collapse
Try TWRP 70
Same thing happened to me, tried almost everything one could think of , even swapped active slots to no avail, eventually found thread on fastboot flashing back to stock and all was fixed. Probably was due to unremoved/undeleted magisk modules(as others have already stated), but once the phone boot loops had no way to get modules removed posthumously......also ran magisk uninstaller to try to resolve and no joy.....like is said after a day and a half just flashed it via fastboot flashing .bat files and all was swell....mines a converted GM1915 to 1917 .....good luck!