Hello guys! I know it's a common issue, but when I reboot my phone there's roughly a 50% chance it gets stuck on the boot screen and I have to reboot. It's surely caused by Magisk, but has someone found a fix already?
The bricks got more frequent and really annoying when I began to install some modules (Xposed, Viper ecc.). Sometimes it takes even 2-3 reboots to start my phone properly, and sometimes it boots without recognizing my sim card.
Is there a fix for this, or do I have to live with it?
Happened to me too. Got rid of magisk for now so running stock un rooted until this gets sorted. Haven't ran into the issue since un rooting.
BetaPix said:
Hello guys! I know it's a common issue, but when I reboot my phone there's roughly a 50% chance it gets stuck on the boot screen and I have to reboot. It's surely caused by Magisk, but has someone found a fix already?
The bricks got more frequent and really annoying when I began to install some modules (Xposed, Viper ecc.). Sometimes it takes even 2-3 reboots to start my phone properly, and sometimes it boots without recognizing my sim card.
Is there a fix for this, or do I have to live with it?
Click to expand...
Click to collapse
Xposed is not yet stable for Oreo. So just get rid of that first. Moreover, it depends on what Magisk version did you flash. V16.0 is the latest stable version and you are recommended to flash it only. I have been using magisk for a long time on both stock and custom rom and never had an issue.
Rowdyy Ronnie said:
Xposed is not yet stable for Oreo. So just get rid of that first. Moreover, it depends on what Magisk version did you flash. V16.0 is the latest stable version and you are recommended to flash it only. I have been using magisk for a long time on both stock and custom rom and never had an issue.
Click to expand...
Click to collapse
I flashed 16.0 too, but I have to say the issue became real even before I installed Xposed. Guess it's something Magisk-related
Try older Magisk, for example 15.3.
Same to me. Just reboot and it´s fine.
BetaPix said:
Hello guys! I know it's a common issue, but when I reboot my phone there's roughly a 50% chance it gets stuck on the boot screen and I have to reboot. It's surely caused by Magisk, but has someone found a fix already?
The bricks got more frequent and really annoying when I began to install some modules (Xposed, Viper ecc.). Sometimes it takes even 2-3 reboots to start my phone properly, and sometimes it boots without recognizing my sim card.
Is there a fix for this, or do I have to live with it?
Click to expand...
Click to collapse
Same. I don't have Xposed or other mods, so I think it's a Magisk's issue.
Made over 20 reboots in order to find the"right" combination of substratum themes the last two days.only 2-3 times i had stucked in reboot. I have magisk, xposed ,gravitybox .
Huh, I get this sometimes too. So it's Magisk v16 you say?
TrueMS said:
Try older Magisk, for example 15.3.
Click to expand...
Click to collapse
Good idea, will give that a go. I don't use any modules anyway, only use it for Safetynet-friendly root.
Same problem here.
I Will follow the topic.
Double post, Sorry!
With beta magisk v16.4 my mi A1 boot normaly...with v16.0 must force reboot 3 times out of 5
laugeek57 said:
With beta magisk v16.4 my mi A1 boot normaly...with v16.0 must force reboot 3 times out of 5
Click to expand...
Click to collapse
Currently testing 16.4b and no boot issues atm!
Must have been topjohnwu's boot operations code change.
Thank you really much
Related
I have come across a very annoying bug with cm12.1 version for 550m...everytime I reboot the phone gets stuck in bootloop almost all the time...half of the time it keeps optimizing apps and then gets stuck at starting apps and other half it just gets stuck in bootloop...it has made installing xposed modules so difficult since it takes me 4-5 rebbots to get even strted with my phone after downloading a module...can anybody help please...
I have no problem with rebooting on my 550. It sometimes hangs on starting apps on first boot after flashing, but turning off and back on solves this (except with broken 0819 build). Xposed may be the cause of your problem - the devs have said countless times that it is not supported and not recommended. If you want to use xposed, you are better off staying on stock or using super zen.
Xposed causes this on CM. It's not supported.
Sent from my serial terminal
Maybe the MediaScanner is going crazy.
I was having the exact same issue as you.
Try to reboot your phone until cyanogenmod boots successfully and run this command on terminal app or adb.
It will disable media scanning on boot.
su
pm disable com.android.providers.media/com.android.providers.media.MediaScannerReceiver
if you want to run cm with xposed.... then run the initial (first) build of cm12.1... Xposed is well supported
Hey everyone.
Like many Android users, I've been struggling to find a ROM and systemless root combo that passes SafetyNet (ever since Pokemon GO 0.37 update). I eventually found a ROM that can be unrooted cleanly (AryaMod S7 Edge port), and managed to get SafetyNet working via Phh's Superuser (first with Magisk + r251, now using hidesu version r266).
However, I soon ran into a problem: The systemless root appears to be causing my phone to bootloop. There seems to be a gradual degradation of the bootimage somehow caused by systemless roots; my phone would work fine for a while, then gradually apps would force close or the phone would freeze. If I try to reboot, the phone then gets stuck in a boot loop (which occurs before the ROM even starts loading). I am very sure this is caused by an error in the bootloader because this bootloop behavior persists through nandroid restore or clean ROM installations. The only way to fix it is to flash the stock bootloader via ODIN.
I noticed a few users in the dev threads of ROM's I've tried reporting the same issue, but in the dev thread for Phh's Superuser there seems to be a lack of mention of this issue (likely model-specific, as I am using Phh's Superuser on my wife's Note 4 and her phone isn't bootlooping). Just wondering if anyone has experienced the same problem and found a solution?
Try the TMobile forum .
Sent from my SM-N930F using XDA-Developers mobile app
I also have an N900T, and magisk v7 + phh is working fine for me if I don't install any extra systemless modules. When I installed the better battery stats module, I started getting bootloops, so there are definitely some issues with it.
Magisk is still being worked on, so it's probably only at alpha or beta status right now. Hopefully it will get more stable in the future.
btw.. I'm running the latest stock Samsung 5.0 rom (N900TUVSFPH3), which has the latest bootloader, since it seems the most stable to me.
Hello there, I've been using the V20(H918) for a little while now and was running WETA Rom 4.8.5 with Magisk 11.0. When Magisk 12.0 released after rebooting and being on for a minute or 2 my phone would suddenly go back to the T-mo splash screen as if it were soft rebooting and then would repeat this process. I thought it might have been a download or flash issue so I tried wiping and doing a fresh install but if I ever restarted the device the same issue would appear. I've tried selecting or deselecting a majority of the options in the aroma installer for WETA but nothing seems to work. The rom seems to work fine with SuperSU installed so I'm thinking it might be something about the way my phone is set up but I haven't been able to pinpoint exactly what it is and I really would like to use Magisk for the hide feature. Based on the thread it doesn't seem like there should be any issues and I'm unable to ask my question directly in the thread. I'm not very experienced with these kinds of things so I'm sorry if I'm not being specific enough or if the solution is obvious. Thanks for anyone's help and time with this issue!
survivingarch said:
Hello there, I've been using the V20(H918) for a little while now and was running WETA Rom 4.8.5 with Magisk 11.0. When Magisk 12.0 released after rebooting and being on for a minute or 2 my phone would suddenly go back to the T-mo splash screen as if it were soft rebooting and then would repeat this process. I thought it might have been a download or flash issue so I tried wiping and doing a fresh install but if I ever restarted the device the same issue would appear. I've tried selecting or deselecting a majority of the options in the aroma installer for WETA but nothing seems to work. The rom seems to work fine with SuperSU installed so I'm thinking it might be something about the way my phone is set up but I haven't been able to pinpoint exactly what it is and I really would like to use Magisk for the hide feature. Based on the thread it doesn't seem like there should be any issues and I'm unable to ask my question directly in the thread. I'm not very experienced with these kinds of things so I'm sorry if I'm not being specific enough or if the solution is obvious. Thanks for anyone's help and time with this issue!
Click to expand...
Click to collapse
alot of people have this problem with 12.0 flash the 11.0 and dont update
survivingarch said:
Hello there, I've been using the V20(H918) for a little while now and was running WETA Rom 4.8.5 with Magisk 11.0. When Magisk 12.0 released after rebooting and being on for a minute or 2 my phone would suddenly go back to the T-mo splash screen as if it were soft rebooting and then would repeat this process. I thought it might have been a download or flash issue so I tried wiping and doing a fresh install but if I ever restarted the device the same issue would appear. I've tried selecting or deselecting a majority of the options in the aroma installer for WETA but nothing seems to work. The rom seems to work fine with SuperSU installed so I'm thinking it might be something about the way my phone is set up but I haven't been able to pinpoint exactly what it is and I really would like to use Magisk for the hide feature. Based on the thread it doesn't seem like there should be any issues and I'm unable to ask my question directly in the thread. I'm not very experienced with these kinds of things so I'm sorry if I'm not being specific enough or if the solution is obvious. Thanks for anyone's help and time with this issue!
Click to expand...
Click to collapse
Im currently running weta rom with magisk 12.0 on my h918. However there are 2 possible differences between yours and mine. 1) you are not in the latest version of weta rom 4.9.4. 2) you are probably flashing the stock kernel that comes in the weta aroma installer. Try with konvergent or another kernel other than the one from weta rom. (as soon as i flashed the weta kernel my phone was experiencing the dame thing yours did , then after i flashed konvergent back it came back to normal)
jinkerz9430 said:
Im currently running weta rom with magisk 12.0 on my h918. However there are 2 possible differences between yours and mine. 1) you are not in the latest version of weta rom 4.9.4. 2) you are probably flashing the stock kernel that comes in the weta aroma installer. Try with konvergent or another kernel other than the one from weta rom. (as soon as i flashed the weta kernel my phone was experiencing the dame thing yours did , then after i flashed konvergent back it came back to normal)
Click to expand...
Click to collapse
Did what you said and everything seems to be running smoothly, thanks very much for your help! Hoping a more updated kernel that doesn't force SuperSU and works with magisk comes out soon!
I don't know what is wrong with my phone, I've searched the web for answers only to find nothing, I've asked in other threads and got no answers, I need help. So basically my issue is Magisk on my Mi A1 this issue happens with both 16.0 and 16.4, on the stock Mi A1 rom occasionally when I reboot my baseband and IMEI is unknown and when I reboot it fixes it's self temporarily I know this is not an issue with EFS partition as when I uninstall Magisk everything is fine and on custom ROMs I don't get this issue but a whole other different one. Also on the stock ROM Magisk causes bootloops sometimes which is fixed by rebooting.
When I use Magisk on a custom ROM I get a different issue, whenever I use Magisk to do anything on my device it causes an issue where sometimes when I power off my device it shows the boot animation before powering off.
I'm really sick and tired of these issues and any help would be really appreciated.
I have the same issue with the no imei/baseband in stockrom with magisk
created a thread like you asking for a solution, got not answers, not sure if is because not enough people mod this device or is something else
I for once as soon as I got it, unlocked bootloader and installed magisk and xposed, everything else is stock
issue still persist, you need to reboot again for imei/baseband to comeback
Sent from my Nexus 6 using Tapatalk
CrazyAndroidModder said:
I don't know what is wrong with my phone, I've searched the web for answers only to find nothing, I've asked in other threads and got no answers, I need help. So basically my issue is Magisk on my Mi A1 this issue happens with both 16.0 and 16.4, on the stock Mi A1 rom occasionally when I reboot my baseband and IMEI is unknown and when I reboot it fixes it's self temporarily I know this is not an issue with EFS partition as when I uninstall Magisk everything is fine and on custom ROMs I don't get this issue but a whole other different one. Also on the stock ROM Magisk causes bootloops sometimes which is fixed by rebooting.
When I use Magisk on a custom ROM I get a different issue, whenever I use Magisk to do anything on my device it causes an issue where sometimes when I power off my device it shows the boot animation before powering off.
I'm really sick and tired of these issues and any help would be really appreciated.
Click to expand...
Click to collapse
If you want people to help you, you need to give more details. A logcat maybe.
Rowdyy Ronnie said:
If you want people to help you, you need to give more details. A logcat maybe.
Click to expand...
Click to collapse
I'm currently running a custom rom and I've discovered that the issue I'm facing there has nothing to do with Magisk, its when I open an app like Titanium backup, even unrooted the app want root permissions causes the boot animation at power off, anyway I'll make a logcat when I get chance.
Hi folks, my stock 6T just offered me the 9.0.12 update. I'm holding off for now as everything works well on 11, but interested to hear experiences.
My only gripe with 11 is idle battery drain that occurs after about 48 hours post boot; no drain problem before that.
Sent from my ONEPLUS A6013 using Tapatalk
Battery life is amazing! (end sarcasm)
Everything seems to be fine
No issues here...installed early Monday morning.
Tried Canada and Germany VPN but nothing yet... Will wait for OTA
Still waiting OTA
Sent from my ONEPLUS A6013 using Tapatalk
Frankenscript said:
Hi folks, my stock 6T just offered me the 9.0.12 update. I'm holding off for now as everything works well on 11, but interested to hear experiences.
My only gripe with 11 is idle battery drain that occurs after about 48 hours post boot; no drain problem before that.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
Region/country? Tia!
I have the OnePlus 6T McLaren edition, I'm in the U.S.A and have a T-Mobile SIM in it (but it's not the T-Mobile version of the phone). I got notified of the update about an hour ago. It detected my phone was rooted so it downloaded the full version of the upgrade, not just a patch file. It then auto-installed the update just fine (I haven't modified my recovery). It booted up just fine and everything is looking good. I did a few simple test calls and loaded a few apps, nothing looked out of the ordinary. I can't speak to battery life or performance though.
I'm now using a direct-launched TWRP to re-flash the ElementalX 3.10 kernel and the Magisk 18.1 zip files (to hide the unlocked bootloader from the OS and also have root back with the ability to hide root from various programs). Those are the only 2 mods I've ever installed on this phone and they've proven solid.
Sometimes reading mode fails to work.... I restarted the phone and worked perfectly
My device bootloops with RescueParty into TWRP with 9.0.12. I believe Magisk is the cause of the problem because as soon as I flash it in TWRP, the device will immediately bootloop into TWRP with RescueParty. The only way to recover was to flash the 9.0.12 boot.img to both boot partitions. So if you plan to use Magisk and Magisk modules, you might want to stick on 9.0.11 for now.
theDUD3 said:
Region/country? Tia!
Click to expand...
Click to collapse
U.S. Indiana on AT&T
Sent from my ONEPLUS A6013 using Tapatalk
Seems really good here. No complaints. Gaming is much smoother and wifi seems much more stable for me too. I like it
Can't believe how fast I got the update. With a "Google" phone I had to wait weeks even over a month sometimes and sideloading on Windows 10 is a PITA when it decides not to find the phone even though it did only a few minutes ago.
Deleted
No issues yet did mine yesterday in Maine USA with German VPN on T-mobile/AT&T sims
parker.stephens said:
My device bootloops with RescueParty into TWRP with 9.0.12. I believe Magisk is the cause of the problem because as soon as I flash it in TWRP, the device will immediately bootloop into TWRP with RescueParty. The only way to recover was to flash the 9.0.12 boot.img to both boot partitions. So if you plan to use Magisk and Magisk modules, you might want to stick on 9.0.11 for now.
Click to expand...
Click to collapse
Yup, experiencing the same issue currently. Gonna follow what you did for now :good:
Did you extract the boot.img from the update file or is it here somewhere? I tried looking .. didn't find it.
Jok3r10 said:
Yup, experiencing the same issue currently. Gonna follow what you did for now :good:
Click to expand...
Click to collapse
You guys could try uninstalling magisk from TWRP, and reflshing it. It worked for me after struggling with the bootloop.
AleiATCG said:
You guys could try uninstalling magisk from TWRP, and reflshing it. It worked for me after struggling with the bootloop.
Click to expand...
Click to collapse
Did you do it with the latest magisk?.. 18.1?
Jok3r10 said:
Yup, experiencing the same issue currently. Gonna follow what you did for now :good:
Did you extract the boot.img from the update file or is it here somewhere? I tried looking .. didn't find it.
Click to expand...
Click to collapse
I used a python script to extract the image from the update .zip. Also reinstalling Magisk does nothing to solve the issue. 18.0 I know worked in 9.0.11, I only ran 18.1 for a little while. Neither fix the issue.
A quick update, it seems that @AleiATCG's suggestion worked for me. I uninstalled Magisk using their uninstaller and reinstalled Magisk 18.1 and voila.. I booted into the rom.