Bootloop after latest Magisk Update....now no root!
This popped up, so i updated.....been on that Rom for ages and i'm not a newbie....but 1 hour later STILL white LG logo!!!
pretty please help me out?
Not sure what to tell you, but I've been on 20.4 for a while now with no issues (VS996 if that matters).
I'd suggest going back into TWRP, reinstalling Magisk (maybe an older version like 18.3 as I've heard newer versions sometimes have issues), then letting Magisk update to 20.4 from there once you're back in. I recall that I think I had to do that when I first installed this ROM... I had to install Magisk a few times for it to "take". I may have even used Magisk Uninstaller before installing it the last time.
Related
Hello is there a way to root the stock mm rom?
If I flash the super su binaries manually will it work? i've already got my TWRP installed on my device.
thanks for your help (if you help me )
SuperSU version 2.65-3
Yes you can root it but it is BETA
So don't expect it to work perfectly like it does on Lollipop.
There was security changes in Android that made things different on MM.
I advise people be extra cautious when planning on Rooting with MM.
There is a bunch of topics created on how to do this (i made one for example)
What you HAVE to do is get a special version called SuperSU "systemless" installed
this is a new way to get root on that was made because of security changes on Marshmallow.
Don't just start flashing things on your phone with out researching first or you may brick your phone.
I know i did that myself LOL
Then realize because the new Root works different then you may have some app's now not work properly.
For example make sure you use the most current updates if you use Stericson's BusyBox (35 pro or 41 free or higher)
Research and read on it then make sure to only use the Flashable zip format's shared by chainfire.
Don't just install APK's.. he tells you this on his pages over & over.
xpmule said:
Yes you can root it but it is BETA
So don't expect it to work perfectly like it does on Lollipop.
There was security changes in Android that made things different on MM.
I advise people be extra cautious when planning on Rooting with MM.
There is a bunch of topics created on how to do this (i made one for example)
What you HAVE to do is get a special version called SuperSU "systemless" installed
this is a new way to get root on that was made because of security changes on Marshmallow.
Don't just start flashing things on your phone with out researching first or you may brick your phone.
I know i did that myself LOL
Then realize because the new Root works different then you may have some app's now not work properly.
For example make sure you use the most current updates if you use Stericson's BusyBox (35 pro or 41 free or higher)
Research and read on it then make sure to only use the Flashable zip format's shared by chainfire.
Don't just install APK's.. he tells you this on his pages over & over.
Click to expand...
Click to collapse
Thanks, i know just installing the APK won't do anything, actually after posting this i tried the latest version of the systemless root, and my phone bricked, it wouldn't even show me the boot logo, and in the bootloader I didn't have a baseband version, thank god I had a back up
I'm now following your post and i'm going to try and root my phone after i'm done backing it up, btw do you know if xposed works with this systemless root? I want to use gravity box so I can add a few tweaks to the stock rom... and I also want to unnintall system apps with titanium backup, but these aren't that important as the tweaks..
Not too sure never used Xposed but i was Google searching and found a fix from guys for the Moto-G
I had to use, BETA-SuperSU-v2.62-3-20151211162651.zip
Newer versions failed to patch the bootloader and do a systemless install.
Use a newer one and then look in the TWRP console (after flashing from TWRP)
You can see on newer versions it simply does a normal install.
So if it does NOT patch your Bootloader for you then your screed.. bricked !
Re-Install the firmware then..
SO far installing BETA-SuperSU-v2.62-3-20151211162651
worked to get the Bootloader patched and the systemless version installed.
Then before exiting TWRP i have flashed over-top (with out restarting) BETA-SuperSU-v2.67-20160121175247
Get them from here..
EXPERIMENT: Root without modifying /system #2: Automation
Supposedly updating to 2.71 Beta is suppose to work.
But i am sketchy about it and 2.67 is for sure working good.
I just tried tonight 2.71 beta updating over-top via TWRP
and i think it was ok i guess.. i have not tested it much though.
(not sure if it will auto-patch the bootloader on a fresh install on it's own with out needing an old version first)
Get 2.71 here.. Note, i am sure chainfire said he merged those older versions into 1 beta version now.
[BETA][2016.03.30] SuperSU v2.71
You have to make sure you have these versions downloaded and ready on your SD card before you start fiddling..
Because if you are on MM and you install and it does not tell you in the console log you got your bootloader patched
..you got a brick on your hands when you reboot LOL
NOTE:
2.65 stable (on Play Store) will NOT work for Marshmallow guys.. it's too old etc.
I really don't know what to do.
I have a rooted nexus 5 running stock 5.1.1 with xposed framework. The installed SuperSU version is 2.79 and works fine. But, Google play keeps asking me to update SuperSu. The updated SuperSu version that then installs is 2.82. If I go ahead and install it, every reboot takes 30 minutes as every installed app gets "optimized".
Fortunately I had a recent twrp nandroid backup that restored things to normal.
I am aware that the developers know SuperSu 2.80 and 2.81 had problems but for me 2.82 still has problems. Chainfire seems to think that 2.82 has resolved the problems, but it hasn't. I sent him an email and tried to post on the SuperSu forum but my message was deleted, I guess because someone thought I had not read the sticky about the 2.80-1 problems.
I tried to find the SuperSu 2.79 apk to download as a safety but found there exist several versions of it and I don't know where to find the correct version.
For now I am sticking with 2.79 but how do I stop the play store from continuingly asking to update SuperSu which I might accidentally reinstall.
Finally, how do I make Chainfire aware of the persistent problems with 2.82?
Thank you.
Got Magisk installed, one minute its working the next its not..
Whats it doing? Constantly telling me theres a update, 16.00 which is what I have installed
I check in the magisk app and sometimes it says magisk is installed, and then its not...
Wish I could sort it once and for all
Dstruct88 said:
Got Magisk installed, one minute its working the next its not..
Whats it doing? Constantly telling me theres a update, 16.00 which is what I have installed
I check in the magisk app and sometimes it says magisk is installed, and then its not...
Wish I could sort it once and for all
Click to expand...
Click to collapse
Clear data of magisk or reflash it. Try the latest 16.2
Had to reflash it a dozen times already, will try 16.2 then didnt know there was new one, my manager always tries downloading 16.0 over and over
Hi, something peculiar is happening: I successfully rooted my US998 V30+ several months ago and never had any issues. Since one/two weeks, after boot I suddently lose root - when the phone roots, magisk 17.1 works, greenify (with root) works, etc.. after a couple of minutes all root related stops working, Magisk tells me that it needs to be installed, greenify tells me that it needs a rooted phone to work..
is this related to a new version of magisk? Any suggestions on what to do?
charliebigpot said:
Hi, something peculiar is happening: I successfully rooted my US998 V30+ several months ago and never had any issues. Since one/two weeks, after boot I suddently lose root - when the phone roots, magisk 17.1 works, greenify (with root) works, etc.. after a couple of minutes all root related stops working, Magisk tells me that it needs to be installed, greenify tells me that it needs a rooted phone to work..
is this related to a new version of magisk? Any suggestions on what to do?
Click to expand...
Click to collapse
Maybe related. Did you completely uninstall the older Magisk before installing the new one?
ChazzMatt said:
Maybe related. Did you completely uninstall the older Magisk before installing the new one?
Click to expand...
Click to collapse
I completely, to 100% did not. I'll try today.
Thanks!
Hi, how do I keep magisk and keep my realme gt rooted after an OTA? Last time I had an OTA I updated and my root + magisk were gone, I had to make a backup of my phone and reroot and reinstall magisk. I don't want to go through that process again, and on magisk there is an option to install to inactive slot, but I am scared to try it since this is my only phone and if its bricked then i'm screwed, and it doesn't seem like anyone else has tried it. My PC was reset so I would have to get all the adb and fastboot drivers and stuff all over again and I would probably mess something up somehow. I need root because I use Google Pay often.
My phone is a Realme GT 5G converted from CN to EU, with Magisk 24.3 (not alpha I switched from alpha to stable)
after going through this:https://topjohnwu.github.io/Magisk/ota.html I can't even do the Magisk app → Uninstall → Restore Images step since it comes up with an error message saying something isn't found
Thanks if anyone can help
kjpern said:
Hi, how do I keep magisk and keep my realme gt rooted after an OTA? Last time I had an OTA I updated and my root + magisk were gone, I had to make a backup of my phone and reroot and reinstall magisk. I don't want to go through that process again, and on magisk there is an option to install to inactive slot, but I am scared to try it since this is my only phone and if its bricked then i'm screwed, and it doesn't seem like anyone else has tried it. My PC was reset so I would have to get all the adb and fastboot drivers and stuff all over again and I would probably mess something up somehow. I need root because I use Google Pay often.
My phone is a Realme GT 5G converted from CN to EU, with Magisk 24.3 (not alpha I switched from alpha to stable)
after going through this:https://topjohnwu.github.io/Magisk/ota.html I can't even do the Magisk app → Uninstall → Restore Images step since it comes up with an error message saying something isn't found
Thanks if anyone can help
Click to expand...
Click to collapse
for sure you need https://developer.android.com/studio/releases/platform-tools