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!
Related
My boss rooted his LG G2-D02 and installing CM 12.1 in the process. Now, after knowing that CM 13 was already released, he downloaded a copy of it and immediately flashed it onto his phone. He got a problem with Gapps and DL-ed a problematic version which caused the notification,"Unfortunately, Setup Wizard has stopped" to pop up repeatedly. We had tried following a few advices from this website but to no avail.
1.) We already tried using Force Stop and Disable under Apps->(Show system apps)->Setup Wizard (CM). I had also tried giving it app permissions, but all app permissions were already available.
2.) The only option is to flash CM 12.1 back again but it can't be done. My boss set the default recovery app to Cyanogenmod's own recovery program, which had limited functions, so I can't
also use TWRP ATM.
3.) My boss also tried something on ADB but to no avail
4.) Factory reset didn't also solve the problems.
I'm almost running out of solutions... Perhaps, I can use a helping hand from brighter minds in this community.
TIA
I'm using cloudyg2 v3.3 because cm13 has got a lot of bug for example
-I can't proceeded to music
-systtem has stopped once a hour
-I can't close touching vibration
I can't remember now but cm13 has got really much bug (yeah my english is very bad,I know this)
Now system is stable and battery is very very good but still İ can't scretch to music
So I just updated Magisk from v11 to v12 and my phone is totally douched up. After rebooting there's an "Unable to use fingerprints" message at the bottom of the screen, the touch screen is janky and my unlock pattern no longer works. The screen goes to sleep randomly too and then comes on without being touched. On the off occasson that the unlock pattern DOES work, the screen loads with no icons, just the page dots and status bar with my wallpaper and nav buttons. Uninstalled Magisk and got the same. Rebooted after uninstall, same thing. I guess I'll be reflashing the ROM, but this is a huge pain in the ass. :/
This isn't a question--more of an answer. DO NOT UPDATE to v12. If you did and have trouble, downgrade to 11.x.
I can second this. Updated to 12.0 and my phone started rebooting randomly and fingerprints started not working. Thought it was something with the rom so clean flashed it again, all was fine till I updated Magisk again. Downgraded to 11.6 and so far no more reboots and fingerprint works.
that's odd. it is working great for me. (currently using Weta 4.9.2 and Tilde's latest kernel + latest magisk manager and magisk 12.0 zip flashed)
Def breaks the systemui and causes the device to repeatedly crash on the ls997.
Was how it acted on pre 11.0 builds for us on v20.
Im testing with the dev on magisk now.
Updated to the latest, no issues here on RR with original kernel.
xxxrichievxxx said:
Updated to the latest, no issues here on RR with original kernel.
Click to expand...
Click to collapse
yeah aosp versus stock lg os act differently
i believe last time ls997 was the only one really having issues, but its breaking ui on the ls997
don't do it
I updated also, put phone in a never-ending 30 seconds to reboot. Had to restore.
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
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 everyone,
To flash the last rom (nightly ) of LineageOS ( in Oreo,from the 2 february), i had to put the firmware 5.1.7. After flash this firmware i was able to flash the ROM but it makes my phone extremely slow and with screen issues (i can still use the tactile but the screen doesnt follow).
I restored but the problem stills then i put le last stable ROM from Oneplus on android pie (9.0.3). It is a bit better (still really slow) and after a moment i get now like a white noise (same as on TV but with color moreover) by wink ( was more and more often on Google Maps), I had to reboot cause i couldnt use more my phone.
Thanks you in advance !
Ps : I've got TWRP from siankatabg and i'm not rooted , if you want me to send log tell me how pls.
Up :good:
When you were flashing did you used this instructions?
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Flash codework's TWRP for Pie. After that reboot into recovery, wipe everything down and use clean flash instructions for your OTA. It should be able to fix any issue you were having. If not let me know.
Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.
Raidenne said:
Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.
Click to expand...
Click to collapse
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.
Ebeninyo said:
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.
Click to expand...
Click to collapse
My issues seem gone since few weeks with the last OTA (it very rarely happens now). I don't know what caused that even if i use my backup.
Thanks for your support !