i had magisk installed with root working, no problem, then i tried to isntall gltools and saw an option to install with magisk, and thought that maybe it wont damage the phone. after i installed the module the phone went to boot loop. i tried with xperia companion wiht no result because i have bootloader unlocked, then i tried with flashtool and worked, but i didnt wiped anything, the phone started. but then i saw that magisk had no root , so i flashed again the kernel , but then boot loop again.
i already tried to open magisk but the gltools module isnt there.
any option beside formatting the phone? any thing i can delete....
Related
Sorry I'm on mobile! Poor formating and typing is all my fault
So I'm out of my mind trying to fix and find a guide to fix my issues. This is how it all started
I was running the latest magisk (20.1) and OOS (9.0.17), when I installed Vance through magisk. I didn't read the instructions all the way, so I installed the module, it worked, then I saw that you can uninstall the YouTube system apk then install Vance. I deleted the Vance on my next reboot AND uninstalled YouTube system app, and I got stuck rebooting my phone. I have TWRP installed on my phone, not flashed (I didn't know the issues with TWRP when I installed the zip through TWRP). When it got stuck booting, I flashed magisk Uninstaller and it fixed the issue. I tried to reinstall magisk 20.1, and I got the same issue, stuck at boot. So I was able to go home, and use the oneplus 6t manager found here on the forums, which roots with magisk 18.0, and, it worked! But I couldn't update to the new magisk without it freezing my boot. After some deliberation on it, I decided to wipe my phone to try and fix it, and TWRP was still installed, and all my issues still persisted. After this setback, I found fastboot rom also on xda, and got it working, did an Ota to 9.0.17 from 9.0.16. Everything was working, until I went into my recovery and it wiped my phone. I don't even know where to go from here and I need help. Any and all help would be appreciated!
Edit: I just local upgraded to android 10 oos, and it seems to be fine. I don't know yet fully because I'm not at my house!
Hello everyone,
I was just casually rooting my Moto G4 Plus, but as the title says, I was unable to install Magisk on it. This is what happened:
I unlocked the bootloader and flashed TWRP 3.2.1-0. No problems at all.
I flashed the latest Magisk .zip, which is 20.2.
I reboot my phone, and the screen stays completely pitch black. Not even the "your device can't be trusted" warning comes up. The phone is bricked.
I was able to unbrick it by flashing the uninstaller. After doing that, the phone booted up fine. (Without Magisk installed, obviously.)
I noticed that the installation instructions said that "Installing Magisk for the first time REQUIRES a full data wipe."
So, I wiped my data partition and flashed the Magisk .zip again. Same problem as before (won't boot), except this time when I try flashing the uninstaller, it fails because it cannot access the Data partition (probably because I wiped it, right?)
Anyways, has anyone had this problem too? Please let me know.
Update: Unbricked by flashing stock rom. Flashed ElementalX, and then Magisk. Everything is all good now haha
Yes even i had to face same issues so flashed stock rom . There must be issues with the updated magisk build.
Hi all
I experience kinda weird behaviour with my OP6T.
I wiped and upgraded to Android 10 a few days ago (10.3.1). I installed TWRP and immediatyl flashed Magisk using @mauronofrio all-in-one tool. I boot up, installed what I needed and all was going good.
By using the phone I noticed that in drawer there was 2 file manager app: one I think was from Google. So I downloaded an uninstaller and deleted it. After that I discovered that, without "File" (app name) I was unable to give folder access to Poweramp scan function (it was just saying the File app keep crashing).
I tried to install it again but nothing.
Now, the good stuff. Keep in mind root was working good. I also successfuly rebooted phone multiple time with no issues.
After I tried to install File app, I restarted my phone and, surprise, it keep stuck on bootloader warning screen for like 30 seconds and after it goes into recovery (TWRP).
I tried to flash recovery again together with Magisk but nothing. Same result (sometimes it wasn't even boot in TWRP but standard fastboot screen). In the end, I tried just flashing TWRP without Magisk and surprise: it booted. Without root of course.
I did some other tests, tried again (including trying to boot from slot B but that doesn't work and no decrypt message appear).
I don't understand what is going on.
What can I do further ? On Android 9 I experienced something like that but with a normal TWRP/Magisk flash it was returning all normal. It's strange because the advice from AIO says to flash TWRP and Magisk otherwise I brick the phone.
Recap:
Only TWRP installed on partiton A/B -> Phone boot with no root
TWRP (partion A/B) + Magisk (only partition A ?) -> Phone doesn't boot and go in recovery
Thanks
Maybe some modules? It's not a problem related to the tool, to the TWRP or Magisk, maybe you added some module that made the device crash at the start
mauronofrio said:
Maybe some modules? It's not a problem related to the tool, to the TWRP or Magisk, maybe you added some module that made the device crash at the start
Click to expand...
Click to collapse
Any way to see the installed modules from TWRP ? I also used Magisk Uninstaller but still nothing.
BTW, going to /data/adb/ I don't have any modules folder so I think nothing is installed.
rootgen said:
Any way to see the installed modules from TWRP ? I also used Magisk Uninstaller but still nothing.
BTW, going to /data/adb/ I don't have any modules folder so I think nothing is installed.
Click to expand...
Click to collapse
So maybe is something else
mauronofrio said:
So maybe is something else
Click to expand...
Click to collapse
Something or not, I think I will stick back to previous android version.
Just a question: why while flashing TWRP it says partion A/B are being patched while only A (or current boot) seems to correctly work (where by correctly work I mean asking for decrypt message is shown) ?
Any help is appreciated.
Thanks
rootgen said:
Something or not, I think I will stick back to previous android version.
Just a question: why while flashing TWRP it says partion A/B are being patched while only A (or current boot) seems to correctly work (where by correctly work I mean asking for decrypt message is shown) ?
Any help is appreciated.
Thanks
Click to expand...
Click to collapse
The installer patch both slots regardless of everything
Hmm, I might have missed it but after you flashed trwp to your phone did you reboot back to recovery then install root.. just asking..
A little background first, I have had my galaxy (sm-g975F exynos) rooted for some time now with magisk. I wanted to update the firmware, reroot and install TWRP in the process. Took me a few hours and only one mistake but at the end I was successful. This was 2 days ago and Ive been working on customizing ever since.
Now onto the problem, I noticed the camera app didn't work any more when I boot into magisk mode. When I boot in standard mode the camera works fine. I tried force quitting, rebooting, reverting to original settings, etc... and no change. I started reinstalling system apps I removed with debloat thinking I may have removed a system app that had an effect but again no change. I read somewhere that clearing/wiping cache may help so I booted into TWRP, went into advanced wipe and only wiped "cache". Now when I reboot into standard mode the phone works fine, but if I boot into magisk mode I cant get past the lock screen. Basically magisk mode boots fine but when I enter my pin it just goes back to lock screen. So I rebooted into standard mode and made it so there was no lock screen(no pin, no fingerprints, etc...) then I tried rebooting in magisk mode to see if this will get me past the lock screen and now it just bootloops in magisk mode only.
So my first problem is getting my phone back into magisk mode, my second problem is the camera. is there a safe way to reflash with TWRP or am I going to have to redo the whole process with odin?
Thank you in advance for any help, I have searched online but haven't found anyone that has had issues wiping cache with TWRP
update, tried downloading magisk zip from magisk manager, rebooted into TWRP and tried installing the zip, no change. wiped dalvik cache for kicks, no change.
update #2, also tried uninstalling or disabling root privilege apps such as novalauncher, liveboot and buttonmapper but I was only able to do this in non-magisk mode, again no change.
Update #... what # am I on?
So I started fresh, reinstalled stock firmware, reinstalled magisk and reinstalled TWRP. Phone is working fine except for the fact the camera doesnt work in magisk mode. I am now 100% positive this is due to magisk or TWRP. I will try and install another camera app to see if it works, but would still like to figure out how to get samsungs camera app to work in magisk mode.
So I decided to enter into safe mode which ultimately broke my magisk install. Same scenario as before, I can boot into non-magisk mode now but if I try and boot into magisk mode I cant get past lock screen. However while in safe mode and now non-magisk mode, the camera actually does work. So as it stands I can either have my phone rooted and not be able to use the camera or not have it rooted and be able to use the camera. If anyone has any suggested work arounds, please feel free to chime in. In the mean time I will start over again.
another update.
I reflashed stock firmware along with magisk. I now have root as well as a working camera, and yes the camera works in magisk mode and non-magisk mode. I am now looking to blame TWRP or multidisabler in breaking the camera. I know that having TWRP on a galaxy S10+ is fairly new to the market but I am surprised that I cannot find a single other report of someone elses camera not working after installing TWRP. I feel like I should keep trying things but I also have reflashed firmware, magisk, TWRP 3 times in the past 5 days and I just want a working phone with root. The only other ideas I had was to either give the camera root access or make the camera a system app. I dont see why I would/should need to do that though.
Moderator can you please change the title of this thread to "Camera not working after installing TWRP" please and thank you if it is possible.
I'm running Android 10 with EvoX rom and after last update of Magisk to 21.4 the phone is stuck on bootloop. After going to recovery and uninstalling Magisk I have the same problem, it's still in bootloop. What can I do to fix the problem?
Dirty flash ROM or if 1st step doesn't work factory reset and install everything
Same here. I don't want to do a factory reset.
I tried to:
- uninstall Magisk from twrp
- flash the boot.img of the rom
- flash the previous version 21.2 of magisk
but none of this worked!
I have the same Issue. Havoc 3.9., Magisk 21.4.
I tried to dirty flash the rom, uninstall magisk 21.4 via twrp, and flashing 21.2.
Didn't help. Occassionally I got into the system, but the screen is a bit more white than usually, I can type in my lock password, but after this, System UI fails.
Yesterday I flashed the fix for safetynet passing after the latest update, which made it work again, and I remember that at the relevant magisk forum, somebody mentioned that would affect System UI somehow. Now I am trying to repair the System UI to see if it works as a solution.
[email protected] said:
Yesterday I flashed the fix for safetynet passing after the latest update, which made it work again, and I remember that at the relevant magisk forum, somebody mentioned that would affect System UI somehow. Now I am trying to repair the System UI to see if it works as a solution.
Click to expand...
Click to collapse
What fix are you talking about? Where can I acquire it?
EDIT: In my case the bootloop was caused by the Systemless Xposed Framework module v90-beta2 by rovo89 (packaged by topjohnwu). Disabling that module allowed me to boot normally.
en_ha87 said:
I'm running Android 10 with EvoX rom and after last update of Magisk to 21.4 the phone is stuck on bootloop. After going to recovery and uninstalling Magisk I have the same problem, it's still in bootloop. What can I do to fix the problem?
Click to expand...
Click to collapse
Same problem occur with me ,i just unistall 21.4 and indtal 20.4 veraion but nothing happens then i just wait for 5-10 min on bootloop screen and it starts processing it's updating my new boot image ... This thing happens when i update my miui after completing the process i finally see my homescreen
Lars0n89 said:
What fix are you talking about? Where can I acquire it?
EDIT: In my case the bootloop was caused by the Systemless Xposed Framework module v90-beta2 by rovo89 (packaged by topjohnwu). Disabling that module allowed me to boot normally.
Click to expand...
Click to collapse
How can you install that Module from TWRP?
That i remember i never installed it, it's automatically loaded with magisk?
To solve this problem i had to format the phone, installing the OS again and also magisk v21.2. But Today i got the same problem... so maybe is not the versione of magisk. But I don't know of to solve it.
I tried also the sotck boot.img, but it stays some seconds on the boot screen of lineage OS and then reboot again stucking on Mi logo.
i also had to install stock rom, lost all the data on the phone. today i have to install custom rom, and will probably pass on the magisk, i don't need sh**t like this happening again.
I had to reinstall the rom from scratch, and needed to format data partition too. After flashing my ROM back, I installed magisk 21.2 and it works great.
I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system
flavioggl said:
I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system
Click to expand...
Click to collapse
Could you help me i got into a bootloop after doing the magisk direct update from the app. My discord is : SneezeOnYou2#8507
I believe that i have a backup in twrp just dont know how to flash or uninstall or what ever to do i dont want to lose my data. I can record my screen if you add me on discord.
flavioggl said:
I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system
Click to expand...
Click to collapse
Thank you, brother. It was a simple solution but I forget to do that. After wasting 2 hours finally able to solve the problem. Thanks again.