I am on miui 11.0.4 & no gravity kernel.
When i flash magisk & reboot it stays at poco loading screen. The phone just doesn't boot.
Any Solution?
agentliquid47 said:
I am on miui 11.0.4 & no gravity kernel.
When i flash magisk & reboot it stays at poco loading screen. The phone just doesn't boot.
Any Solution?
Click to expand...
Click to collapse
I'm having the same issue. When I flash magisk uninstaller, it boots properly.
paprazzi95 said:
I'm having the same issue. When I flash magisk uninstaller, it boots properly.
Click to expand...
Click to collapse
I figured it out. One of the magisk module was causing this problem so i deleted all modules using twrp file manager.
Here is what you can try
Open twrp. Go to advanced the file manager then data/adb/modules and delete all the module and reboot to system. Then open twrp again and flash magisk 20.3. No Bootloop.
agentliquid47 said:
I figured it out. One of the magisk module was causing this problem so i deleted all modules using twrp file manager.
Here is what you can try
Open twrp. Go to advanced the file manager then data/adb/modules and delete all the module and reboot to system. Then open twrp again and flash magisk 20.3. No Bootloop.
Click to expand...
Click to collapse
Hi.
The data/adb/ folder is empty. There is no module folder in it.
agentliquid47 said:
I am on miui 11.0.4 & no gravity kernel.
When i flash magisk & reboot it stays at poco loading screen. The phone just doesn't boot.
Any Solution?
Click to expand...
Click to collapse
yea i have really bad experience with this kernel, did you install DTS:X ? maybe this one make you bootloop, i do have this issue also.
DOYANMAIN said:
yea i have really bad experience with this kernel, did you install DTS:X ? maybe this one make you bootloop, i do have this issue also.
Click to expand...
Click to collapse
Yes dts x was causing the issue just delete dtsx using twrp fike manager and you are good yo go.
i have installed bromite systemless webview magisk module and tried to install it this has stooped the magisk manager to stop and i tried to reboot my device and it is stuck on boot loop, i have acessed twrp and deleted the module which has caused the bootloop but to my dismay i am still at boot lop can any one please help me
Related
Can anyone help me install ashyx's TWRP with magisk instead of super su? I've seen that it's been done on the TWRP thread.
I've installed TWRP, then flashed magisk but its not working, seems like I need to patch the boot.img but from my basic understanding that negates the point of magisk right?
Thanks in advance.
sp4r3h said:
Can anyone help me install ashyx's TWRP with magisk instead of super su? I've seen that it's been done on the TWRP thread.
I've installed TWRP, then flashed magisk but its not working, seems like I need to patch the boot.img but from my basic understanding that negates the point of magisk right?
Thanks in advance.
Click to expand...
Click to collapse
You have to install the Magisk zip with TWRP then the Magisk manager apk.
@sp4r3h did you manage to get it working?
@ashyx can you give me some more details?
This is what I tried.
1. Restore stock firmware
2. Flash TWRP
3. Choose Read Only
4. Install zip - Magisk
5. Reboot
Then I get the verification failed error. But from my understanding.. if I use your dm-verify patch then I can't pass SafetyNet?
Which kind of negates the point of magisk?
Thanks for your time.
Follow instructions in first post and flash magisk.zip instead of supersu.
Install magisk manager after system reboot.
napx said:
Follow instructions in first post and flash magisk.zip instead of supersu.
Install magisk manager after system reboot.
Click to expand...
Click to collapse
The manager was removed from the appstore. I'll try manually installing an APK.
napx said:
Follow instructions in first post and flash magisk.zip instead of supersu.
Install magisk manager after system reboot.
Click to expand...
Click to collapse
If I try patching the Magisk then I get the verification failed. If I patch the dm-verify then I can't pass SafetyNet.
Any ideas?
Magisk 12 can't pass SafetyNet anymore.
I also tried the beta Magisk 13.0 but I ran into the same error, so I can't even check if it can pass ...
Follow instructions in first post (in TWRP thread) and flash magisk.zip instead of supersu.
Install magisk manager after system reboot.
That works for me.
napx said:
Magisk 12 can't pass SafetyNet anymore.
Click to expand...
Click to collapse
Google Tweaked Some S**ta again
So What you Gotta do is -
1. Goto Magsisk Manager Settings
2. Enable Core Only and Magisk Hide and select the app (Also Disable the other two adblocker and BusyBox)
3. Reboot
Worked for me (Verified Snapchat and Then Undo all got root back)
But I did one my S4mini
I was just surfing and saw the post and Share it with you guys
Magisk
sp4r3h said:
Can anyone help me install ashyx's TWRP with magisk instead of super su? I've seen that it's been done on the TWRP thread.
I've installed TWRP, then flashed magisk but its not working, seems like I need to patch the boot.img but from my basic understanding that negates the point of magisk right?
Thanks in advance.
Click to expand...
Click to collapse
Well, I also like to try magisk because SU does not work proper. Is there a way to uninstall SU
without a wipe in TWRP ??
Hi. This might be interesting for ALL.. After me Tab hangs, I downloaded the latest OFFICIAL ROM from Samsung,
in my case "DBT-T825XXU1AQF3-20170713092645.zip"...
Extract and place AP, BL, CP and CSC. I decided not to use CSC-home.
Now, reboot.
Activate the developer-option and activate USB Debug.
Restart phone in download-mode (you will need 3 hands Menu, vol-down, power keys at the same time..
Again use odin. This time flash TWRP "twrp_3.1.0-1_sm-t825_AQD6.tar" as AP.
In ODIN, you might select the auto-reboot option because after flashing, you will only need to press
menu + vol-up keys.. Easier with two hands
Now proceed as already described in this thread (format data, wipe etc...) for rooting your tab, BUT (!!!!) do not use supersu. Use magisk "Magisk-v14.0.zip".
After flashing magisk, flash "no-verity-no-encrypt_ashyx.zip".
Now reboot and enjoy a rooted tab. This does not modify the knox counter, warranty is not void. I still use the original samsung firmware..
Lets see if a suitable custom ROM will show up soon. Would be nice if Lineage was available, for tab S3 and phone S8..
ashyx said:
raymondbernard
Need some help with magisk I downloaded the magisk v14.0 and it still says that it's not install just magisk manager is installed I'm trying to root a samsung sm-j320w8
---------- Post added at 03:06 PM ---------- Previous post was at 03:04 PM ----------
ashyx said:
You have to install the Magisk zip with TWRP then the Magisk manager apk.
Click to expand...
Click to collapse
Hey it's raymondbernard trying to get help from you about magisk manager app to root a Samsung sm-j320w8
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I installed systemless Xposed through magisk and it got my phone stuck in bootloop so I tried to fix it by using HWOTA8 and used the OTA.bat fixed the problem but when I installed Magisk again the problem happens again so is there anyway to delete all modules installed by Magisk from recovery?
CodeRida said:
I installed systemless Xposed through magisk and it got my phone stuck in bootloop so I tried to fix it by using HWOTA8 and used the OTA.bat fixed the problem but when I installed Magisk again the problem happens again so is there anyway to delete all modules installed by Magisk from recovery?
Click to expand...
Click to collapse
there is a mount magisk zip to flash in recovery. but don't have link ready, just search on google, should be easy to find
Is it possible that sound mods such as V4a, sauron, adm lib cause bootloop?
I uninstalled each of them individually in twrp, but it was still in bootloop.
Was this caused by youtube vanced apk along with microg plugin?
jaspad1710 said:
Is it possible that sound mods such as V4a, sauron, adm lib cause bootloop?
I uninstalled each of them individually in twrp, but it was still in bootloop.
Was this caused by youtube vanced apk along with microg plugin?
Click to expand...
Click to collapse
I'm using V4A as well as the youtube vanced modules, none of them caused any bootloops, the only bootloop i did get was probably only when i used the xposed module.
Here's what you should try, Install magisk manager for recovery mode module and delete every other module, then check them one by one, if they cause bootloops. Install a module, reboot, don't install another one. If you do get a bootloop at any instance, go to recovery mode and open up the terminal in advanced and type in : /data/media/mm then just follow on screen instructions and disable the module causing the bootloop.
franz said:
I'm using V4A as well as the youtube vanced modules, none of them caused any bootloops, the only bootloop i did get was probably only when i used the xposed module.
Here's what you should try, Install magisk manager for recovery mode module and delete every other module, then check them one by one, if they cause bootloops. Install a module, reboot, don't install another one. If you do get a bootloop at any instance, go to recovery mode and open up the terminal in advanced and type in : /data/media/mm then just follow on screen instructions and disable the module causing the bootloop.
Click to expand...
Click to collapse
I guess it was due to multiple mods i flashed in one go. Im with v4a and yt vanced now for almost two days no prob now..
jaspad1710 said:
Is it possible that sound mods such as V4a, sauron, adm lib cause bootloop?
I uninstalled each of them individually in twrp, but it was still in bootloop.
Was this caused by youtube vanced apk along with microg plugin?
Click to expand...
Click to collapse
I have also installed Magisk and Arise Magnum Opus and now i am in bootloop.
I tried to restore my previous backup, but it was not success.
The phone directly boots into FASTBOOT if i flash LOS16 fresh image and if i flash Magisk along with LOS16, it doesn't show any FASTBOOT but stays in bootloop.
The vendor partition have some weird amount of memory looks like 17592186043943MB!
Please help to recover the issue asap.
I installed YouTube vanced from magisk manager and rebooted directly into recovery and then flashed the notification icon enabler from TWRP and was then just bootlooping to TWRP. I uninstalled the notification enabler with the disabler given by the same website but the phone still bootlooped. I uninstalled YouTube vanced from TWRP terminal but the phone still bootlooped. Tried to restore a nandroid backup but in vain.
The only thing that seemed to be working was uninstalling magisk using the official uninstaller and the phone booted to system but I obviously lost root.
Had to flash the ROM through fastboot which formats the phone and then unlock , install TWRP and root again.
—Problem—
Boot loop... is there anyway to solve this problem without a reset?
—generel Infos—
Device: OnePlus 5 (rooted)
OS: oxygenos 9.0.3
Recovery: TWRP
Other: using EDXposed &
Nethunter Kernel
—the reason?—
I think it was the experimental setting in GravityBox Pie. There was a warning but I didn’t read it because ... I don’t know. The setting required a reboot but after that I stuck in the boot loop.
—what I ´ve tried—
I saw a guide on xda how to disable xposed modules via twrp. The problem was that I was using EDXposed. It was a different. But I deleted a similar file via twrp file manager ( /data/data/com.[IdontKnowTheExactPackgeName].xposed.manager/shared_prefs/[SomethingWithModules])
I tried to reboot but without success
I installed mm ( a for twrp to disable/enable magisk modules and more)
In mm I disabled the EDXposed Module und riru Core Module ( Im not sure if I was riru)
I tried to reboot but without success
I flashed magisk uninstaller and after flashing was done( magisk couldn’t restore boot image or something like that but the flash worked so I ignored it) I got the error: error creating fstab ( the same error occurred when wiping cache/dalvic)
I tried to reboot but without success
I wanted to flash EDXposed but it didn’t work because I haven’t magisk installed
So I flashed magisk again ( this solved the fstab error) and after that the EDXposed uninstaller. Both flashes worked
I tried to reboot but without success
Now I gave up and hope that you have an ansewer
Master Luca said:
—Problem—
Boot loop... is there anyway to solve this problem without a reset?
—generel Infos—
Device: OnePlus 5 (rooted)
OS: oxygenos 9.0.3
Recovery: TWRP
Other: using EDXposed &
Nethunter Kernel
—the reason?—
I think it was the experimental setting in GravityBox Pie. There was a warning but I didn’t read it because ... I don’t know. The setting required a reboot but after that I stuck in the boot loop.
—what I ´ve tried—
I saw a guide on xda how to disable xposed modules via twrp. The problem was that I was using EDXposed. It was a different. But I deleted a similar file via twrp file manager ( /data/data/com.[IdontKnowTheExactPackgeName].xposed.manager/shared_prefs/[SomethingWithModules])
I tried to reboot but without success
I installed mm ( a for twrp to disable/enable magisk modules and more)
In mm I disabled the EDXposed Module und riru Core Module ( Im not sure if I was riru)
I tried to reboot but without success
I flashed magisk uninstaller and after flashing was done( magisk couldn’t restore boot image or something like that but the flash worked so I ignored it) I got the error: error creating fstab ( the same error occurred when wiping cache/dalvic)
I tried to reboot but without success
I wanted to flash EDXposed but it didn’t work because I haven’t magisk installed
So I flashed magisk again ( this solved the fstab error) and after that the EDXposed uninstaller. Both flashes worked
I tried to reboot but without success
Now I gave up and hope that you have an ansewer
Click to expand...
Click to collapse
Try reflashing rom you are using again in recovery.so dirty flash over existing one
Sent from my LEX820 using Tapatalk
bilausdaniel said:
Try reflashing rom you are using again in recovery.so dirty flash over existing one
Sent from my LEX820 using Tapatalk
Click to expand...
Click to collapse
Still in boot loop ( I let it boot for 18 min )
Did you tried to disable xposed on booting?
There is key combination when system boots up, to disable xposed, and so all modules.
Go into recovery, and boot up again from there (normal boot), and when logo appears click at least 3 times power button, and xposed will understand it need to disable itself.
That should work.
And if you have some data in phone, you can make app backup from recovery and if you have files you can connect to PC and copy those files on PC.
I am currently having this problem. Some fully updated systems on some devices won't boot into safe mode. Among those devices are many Xiaomi Devices. I can only boot into fastboot mode.
I've got Orange Fox so theoretically I should be able to delete Riru, effectively disabling exposed, however, Orange Fox is asking for a decryption password and I can't access files to delete them.
ADB sideload failed.
Not sure if I can even do a wipe back to default state.
brasscupcakes said:
I am currently having this problem. Some fully updated systems on some devices won't boot into safe mode. Among those devices are many Xiaomi Devices. I can only boot into fastboot mode.
I've got Orange Fox so theoretically I should be able to delete Riru, effectively disabling exposed, however, Orange Fox is asking for a decryption password and I can't access files to delete them.
ADB sideload failed.
Not sure if I can even do a wipe back to default state.
Click to expand...
Click to collapse
go in twrp and to android/adb/modules.. module there reboot phone
bilausdaniel said:
go in twrp and to android/adb/modules.. module there reboot phone
Click to expand...
Click to collapse
delete that module in there
I'm looking for help getting Magisk installed on MIUI 12.1.1. If I use the boot.img and pass it to Magisk manager and flash it, the system just reboots to recovery after a few minutes.
Does anyone have it working or a recovery that works with 12.1.1 global?
moffa~ said:
I'm looking for help getting Magisk installed on MIUI 12.1.1. If I use the boot.img and pass it to Magisk manager and flash it, the system just reboots to recovery after a few minutes.
Does anyone have it working or a recovery that works with 12.1.1 global?
Click to expand...
Click to collapse
By "passing it to magisk", do you mean patching the boot.img and getting a magisk_patched.img? Do you have the latest magisk app? It's no longer called magisk manager (v22).
Edit: You probably just hot the patched boot from the wrong boot.img
Tulsadiver said:
By "passing it to magisk", do you mean patching the boot.img and getting a magisk_patched.img? Do you have the latest magisk app? It's no longer called magisk manager (v22).
Edit: You probably just hot the patched boot from the wrong boot.img
Click to expand...
Click to collapse
Hi, thanks for responding.
Yes, I mean I take the boot.img from the MIUI fastboot package and select it in Magisk (no longer manager). I then reboot to bootloader mode, then run "fastboot flash boot magisk_patched_sLsab.img " but after running fastboot reboot it just ends up in recovery mode.
The only way to recover is to use fastboot to flash the original boot.img back over
I finally figured out that I had magisk modules left over before the upgrade which broke everything. A factory reset wiping all data has fixed it.