After rooting my device with Magisk, everything seemed to work fine, but I wanted the Camera2 API and the Magisk module I found here didn't work (according to the Camera2 API probe app), so I decided to try the Pix3lify module. BIg mistake, because now my phone is stuck in a boot loop! I think Pix3lify was meant for Android Oreo, so I'm not doing that again. Going into recovery and factory resetting doesn't fix the boot loop issue, and neither does resetting the cache partition from that menu.
So my question is, how do I fix my Samsung Galaxy A12 boot looping issue? And preferably, I would also like to unroot it and lock the bootloader, like how it was when it was first brought and not modded, so I don't have any more problems like this. Thanks in advance!
ASOwnerYT said:
After rooting my device with Magisk, everything seemed to work fine, but I wanted the Camera2 API and the Magisk module I found here didn't work (according to the Camera2 API probe app), so I decided to try the Pix3lify module. BIg mistake, because now my phone is stuck in a boot loop! I think Pix3lify was meant for Android Oreo, so I'm not doing that again. Going into recovery and factory resetting doesn't fix the boot loop issue, and neither does resetting the cache partition from that menu.
So my question is, how do I fix my Samsung Galaxy A12 boot looping issue? And preferably, I would also like to unroot it and lock the bootloader, like how it was when it was first brought and not modded, so I don't have any more problems like this. Thanks in advance!
Click to expand...
Click to collapse
go to sammobile and download your file and flash them back on odin you can check on youtube how to do it
Related
Has anyone gotten Magisk to work on DP2? Whenever I flash it through TWRP the phone just ends up in a bootloop with the "G" logo. I know the problem is with Magisk (I've tried Magisk 16.1-16.4) and not with TWRP because when I installed TWRP by itself the phone booted fine. However, once I flashed Magisk I ended up getting stuck in a bootloop again. Any help would be greatly appreciated!
akablasian said:
Has anyone gotten Magisk to work on DP2? Whenever I flash it through TWRP the phone just ends up in a bootloop with the "G" logo. I know the problem is with Magisk (I've tried Magisk 16.1-16.4) and not with TWRP because when I installed TWRP by itself the phone booted fine. However, once I flashed Magisk I ended up getting stuck in a bootloop again. Any help would be greatly appreciated!
Click to expand...
Click to collapse
Working here.. on magisk version 16.4. Have not changed from stock kernel and had only added my google account at that point.. not sure what else to tell you. Try booting it a few times, magisk seems to cause it to get stuck sometimes for me on 8.1, probably same problems on 9.
Magisk and its SU are working fine -- Systemless Ad Block however does not seem to be.
sulpher said:
Working here.. on magisk version 16.4. Have not changed from stock kernel and had only added my google account at that point.. not sure what else to tell you. Try booting it a few times, magisk seems to cause it to get stuck sometimes for me on 8.1, probably same problems on 9.
Click to expand...
Click to collapse
Thanks for trying to help. I tried rebooting it several times but had no luck. However, I just decided to try wiping data during the DP2 installation and now it seems to have worked.
My OP6 is on a custom rom (havoc) + rooted and today morning i got a app update for Magisk. So i did the update then install it via magisk manager (direct) then restarted the phone. Now my phone is stuck on "phone is starting". I can go to settings menu by quick settings. That's it. I
have been suffering from this phone is starting / android is starting issue for a time to time for different phones. Sometimes it works by a simple restart, sometime by installing a new launcher and sometime factory reset. Worst case scenario,i have to flash the entire rom. Today i fix it by rebooting to twrp > selinux context fix. So my question is
1. What exactly is causing this issue? Apparently this is juts not related to OP6
2. Is there a permanent fix for this?
Im afraid to restart my phone because of this.
Use magisk uninstaller, boot system, go back to twrp and flash magisk.
whizeguy said:
Use magisk uninstaller, boot system, go back to twrp and flash magisk.
Click to expand...
Click to collapse
So this is because of magisk?
crazykas said:
So this is because of magisk?
Click to expand...
Click to collapse
Not necessarily:
https://forum.xda-developers.com/showpost.php?p=79114770&postcount=11
I decided to root my Oneplus 6 (10.30.1) yesterday and everything went fine using TWRP 3.3.1.17 mauronofrio and Magisk 20.3.
Today I wanted to installed EdXposed which I did by going in to Magisk Manager, install Riru, reboot, install EdXposed and then reboot.
However, after installing EdXposed my phone would not boot, it would just hang on the loading screen.
I forced a reboot in to TWRP recovery and proceeded to restore my nandroid backup. This only made things worse.
When i try to boot I get the unlocked bootloader warning, it tries to boot in to the OS for about one second, then back to the bootloader warning screen and so on and so on.
I can still boot in to TWRP with Vol down + Power and i've tried wiping data and i've tried 'fix recovery bootloop' in the advanced settings but neither has worked.
Could someone kindly help fix this? I dont mind if i have to reinstall a stock Rom and lose root etc. I just want my phone back
Thanks
Goooober said:
I decided to root my Oneplus 6 (10.30.1) yesterday and everything went fine using TWRP 3.3.1.17 mauronofrio and Magisk 20.3.
Today I wanted to installed EdXposed which I did by going in to Magisk Manager, install Riru, reboot, install EdXposed and then reboot.
However, after installing EdXposed my phone would not boot, it would just hang on the loading screen.
I forced a reboot in to TWRP recovery and proceeded to restore my nandroid backup. This only made things worse.
When i try to boot I get the unlocked bootloader warning, it tries to boot in to the OS for about one second, then back to the bootloader warning screen and so on and so on.
I can still boot in to TWRP with Vol down + Power and i've tried wiping data and i've tried 'fix recovery bootloop' in the advanced settings but neither has worked.
Could someone kindly help fix this? I dont mind if i have to reinstall a stock Rom and lose root etc. I just want my phone back
Thanks
Click to expand...
Click to collapse
Use the msm tool to recover your device...
Try booting into the mauronofrio twrp recovery from fastboot. Then wipe the system partition and reinstall your rom.
Then boot mauronofrio twrp again from fastboot and install the zip, and reboot to recovery.
Install custom kernel, Magisk.
Uninstall edexposed
People reply here with no clue and advise to just restore stock. How is this a solution and how did not OP think of it themselves?
This is too little too late, but maybe it helps someone else:
Unofficial TWRP for Android 10 is glitchy. E.g. nanodroid backups are not restoring properly. Given current A/B mess this is not at all surprising.
Solution: wipe everything, reinstall *same* lineageOS version as before, flash same gapps as you had, and if you took the nanodroid backup after magisk, install it as well.
Don't boot yet!
Restore the backup *partially*, e.g. only the data partition.
This should work.
Or, emh, it did for me with some minor glitches. But even Google Authenticator didn't notice spoofing (otherwise RIP my accounts). So, i definitely recommend trying this workaround.
I installed Magisk via twrp(Temp version). and installed a bunch of modules.
Then I decided to complexly uninstall Magisk. I've done that from the Magisk Manager apk(The Complete Uninstall button)..
The phone rebooted and stuck into the phone logo with red danger logo. which means perhaps the boot img is missing ?
I should have uninstalled the modules first, which might have caused this issue..
Now, I Flashed Magisk again via Temp twrp, but now few apps keeps crashing, even after uninstalling and installing them.
i don't have the stock bot image, otherwise i guess i can do fastboot boot boot.img to escape the boot issue after uninstalling Magisk from the app
Note : i tried flashing the uninstall zip file from twrp but that didn't work, Magisk framework still exists !
What should i do now ?
My HTC is the duel sim version (Asia) and i'm using Magisk 22 latest version
Have you tried cleaning dalvik cache?
XDHx86 said:
Have you tried cleaning dalvik cache?
Click to expand...
Click to collapse
I did, No luck. The reason I'm trying to unRoot my device is because a mobile banking app is detecting Magisk. the app keeps crashing after i add it to the Magisk hide menu
Coldz0 said:
I did, No luck. The reason I'm trying to unRoot my device is because a mobile banking app is detecting Magisk. the app keeps crashing after i add it to the Magisk hide menu
Click to expand...
Click to collapse
If it is just the banking app then you can get "MagiskHide" and "Safety Net Fix" modules from magisk.
If your phone stuck in bootloop or other apps are still crashing then you have to wipe dalvik cache again.
If you still need to unroot for whatever reason then try this:
Try updating magisk first then clicking uninstall from magisk manager
Try manually flashing uninstaller.zip from TWRP
Try flashing the uninstaller as a module as stated in this post
Finally if it's still no use, then you can factory reset the device and it will remove the root
XDHx86 said:
If it is just the banking app then you can get "MagiskHide" and "Safety Net Fix" modules from magisk.
If your phone stuck in bootloop or other apps are still crashing then you have to wipe dalvik cache again.
If you still need to unroot for whatever reason then try this:
Try updating magisk first then clicking uninstall from magisk manager
Try manually flashing uninstaller.zip from TWRP
Try flashing the uninstaller as a module as stated in this post
Finally if it's still no use, then you can factory reset the device and it will remove the root
Click to expand...
Click to collapse
I'm on the last version of Magisk. I tried to uninstall it from the app but it stuck at the boot logo with danger logo.
I also tired to flash multiple zip files but still Magisk exists after reboot.
That leaves me with last option. Factory reset. s it safe to do it even with magisk installed ? because the boot img is patched and when i try yo restore the original boot img, it just don't exist in Magisk !
Coldz0 said:
I'm on the last version of Magisk. I tried to uninstall it from the app but it stuck at the boot logo with danger logo.
I also tired to flash multiple zip files but still Magisk exists after reboot.
That leaves me with last option. Factory reset. s it safe to do it even with magisk installed ? because the boot img is patched and when i try yo restore the original boot img, it just don't exist in Magisk !
Click to expand...
Click to collapse
No if it is a patched boot image then you'll have to flash the stock one.
Factory resetting a patched image puts the device in a bootloop.
XDHx86 said:
No if it is a patched boot image then you'll have to flash the stock one.
Factory resetting a patched image puts the device in a bootloop.
Click to expand...
Click to collapse
Yes. This is what i was afraid of. I don't have the stock boot img. if you can help me with that, it will be great, my phone firmware (htc/imedugl_00401/htc_imgedugl 9/PQ2A. 190205.003/1088647.3)
Coldz0 said:
Yes. This is what i was afraid of. I don't have the stock boot img. if you can help me with that, it will be great, my phone firmware (htc/imedugl_00401/htc_imgedugl 9/PQ2A. 190205.003/1088647.3)
Click to expand...
Click to collapse
You can find your device's ROM here (Literally first google results..):
HTC website
HTC dev center
GetDriodTips (Only for U12+)
**Disclaimer:** I don't own any of those ROMs and I don't hold responsibility whatsoever should you brick your phone or anything goes awry.
had exactly the same issue and exactly due to the same reason (I hate those pseudo-secure banking apps).
I couldn't wipe dalvik as TWRP is still not available for my P5.
But it was fixable really easy by reflashing the patched boot.img:
run command "fastboot flash boot magisk_patched.img"
btw I'm still looking for a solution for that stupid banking app.
I tried the above mentioned "magisk hide" and "safety net fix" and tried hiding the app itself but all that does not help.
Can we delete magisk and still use the phone rooted ? Or will it unroot my phone if magisk is removed. I’m planning to sell my s10 and the buyer does not want the application.
Good information from GetDriodTips (Only for U12+). Thank you.
Hey there,
so I've rooted my S10 (SM-G973F) with magisk about 3 months ago, and it worked fine for quite a long time.
Just recently I tried to install the magisk LSPosed module, after about a week I rebooted my phone and was stuck in a bootloop.
I tried to access my Phone via adb but I couldn't fix it, then reflashed the Stock Firmware hoping it would fix it, which actually did, just to be stuck without root now.
Every time I try to flash magisk via Odin, my phone won't boot up properly and displays the message "OS couldn't be loaded" or similar.
If I then Flash the Stock Firmware again, everything works just fine.
Please let me know if you have any idea of how to fix this problem.
(Sorry if I posted this in the wrong place or something, I'm new here)
You probably flashed a recent firmware with a more restrictive security system. The only thing that keeps your device from booting is that it checks boot.img for modifications, you can wait for magisk update (or use canary builds), or try a custom kernel, if it can boot, then flash magisk.