I did root through this topic: https://forum.xda-developers.com/moto-g5s-plus/development/root-moto-g5s-plus-t3673287
Everything worked fine, I unlocked the bootloader, I installed TWRP informed on the topic, but instead of Magisk, I used SuperSU, downloaded the latest version on the site and flashed via TWRP ... When Android starts, the SuperSU icon is there, the application works for a few minutes, when I open again, this appears: https://ibb.co/iosWeR
What can it be? I've already tried: reinstalling root, doing the whole process again, installing another version of SU.
Related
I have a OnePlus One mobile.
I have rooted it installed multirom on it everything was working fine .
Then i installed cyan hacker rom using twrp and multirom.
But after two days when i rebooted device into stock(internal) rom Super Su stopped working .
I was getting error "Super Su binary not found and super su can't install it).
i tried everything removed old Super Su ,flashed new one but same problem.
Tried disabling and enabling it but same problem.
But in my cyan hacker ROM when i checked i found "Your device has root access"using Root Checker app but in my stock rom it is showing as your device does not has root access.
When i am opening Multirom app it is showing you don't have root access.But in twrp recovery i have that multirom utility there and it's working fine.
I don't know what to do whether my device is rooted or not.
Shall i need to unlock the bootloader again and perform same activity of rooting again.
Please help.
I recently decided to root my oneplus one. However i ended up flashing a custom rom (cm12 Lollipop) before flashing the supersu binary. I downloaded the latest version of supersu and copied it onto the root of the phone and flashed it via recovery countless times. But for some reason, after i boot the phone back up and open supersu, it just lags and then displays a black screen. I downloaded it from the playstore as well, but it just won't open. Root checker says its not rooted, despite having a custom rom installed. What do i do?? Please help
You don't need to install SuperSU on CM12, superuser is built into Privacy Guard. Perform a full wipe and flash CM12 + gapps again without installing SuperSU and you should be fine.
Transmitted via Bacon
Works Now
Thanks! It took a while but i got it working thanks to you..
No worries [emoji106]
Transmitted via Bacon
Hi,
So I got my new LG G2 a few days ago. I want to install CM12l, so I rooted with avicohh's root script and installed twrp manager. TWRP manager should have installed twrp, but whenever I try to boot into recovery, it says "demigod crash handler error". I tried installing CWM on top via rom manager, same issue. i gave up with CM and tried to install Xposed, which cannot install the framework due to being unable to do process 58 and 54, i'll try to provide a log cat. Saurik's winterboard for theming also had issues. i then tried downgrading to stock kitkat from lollpop, but the kdz method couldn't find my device (adb is working, it connects my phone as a drive each time) and the tot method says ready but never does anything. the guide i used is here:http://forum.xda-developers.com/showthread.php?t=2432476. i was downgrading then to use autorec, a tool to install twrp automatically, but it says it only runs on kitkat.
autorec:http://forum.xda-developers.com/showthread.php?t=2715496
if anyone could help me either to get to CM12, TWRP, Kitkat, or xposed, that would be great. thanks so much in advance.
hi guys.....
i had recently unroot my moto g3 and install stock root to use my jio sim.
but i really miss the root access so, is there any way to to have root access.
when i flash supersu it will get stuck into bootlogo and will not proceed.
i waited for half an hr but no sign of booting up
anyone have a way to get root access to stock rom plzz help........
Just flash this super user zip file
http://forum.xda-developers.com/attachment.php?attachmentid=3655401&d=1456122222
is supersu installing systemless?
make sure to do this first in twrp terminal: "echo SYSTEMLESS=true>>/data/.supersu"
Sushilsingh said:
hi guys.....
i had recently unroot my moto g3 and install stock root to use my jio sim.
but i really miss the root access so, is there any way to to have root access.
when i flash supersu it will get stuck into bootlogo and will not proceed.
i waited for half an hr but no sign of booting up
anyone have a way to get root access to stock rom plzz help........
Click to expand...
Click to collapse
You already have an existing thread on this problem, and were told what needs to be done and where to go to get that information and additional assistance... Why are you not using the resources that were given to you previously? There is no magic fix, something was done incorrectly or you are using the incorrect files.
The answer and all support you will need are in this thread: http://forum.xda-developers.com/2015-moto-g/general/guide-how-to-root-moto-g-2015-model-t3448572
acejavelin said:
You already have an existing thread on this problem, and were told what needs to be done and where to go to get that information and additional assistance... Why are you not using the resources that were given to you previously? There is no magic fix, something was done incorrectly or you are using the incorrect files.
The answer and all support you will need are in this thread: http://forum.xda-developers.com/2015-moto-g/general/guide-how-to-root-moto-g-2015-model-t3448572
Click to expand...
Click to collapse
buddy i just install a clean XT1550_OSPREY_RETASIA_DS_2GB_6.0.1_MPI24.107-55_cid7_subsidy-DEFAULT_CFC.xml.zip
stock rom and twrp twrp-osprey-3.0.2-r1.img as you told.
and that command also
echo SYSTEMLESS=true>>/data/.supersu
cat /data/.supersu
it shows systemless=true
and installed latest supersu SR1-SuperSU-v2.78-SR1-20160915123031.zip from its official site
after that i wipe cache and dalvik.
i reboot it.
and its get reboot without supersu (root) permission.
what should i do?
Sushilsingh said:
buddy i just install a clean XT1550_OSPREY_RETASIA_DS_2GB_6.0.1_MPI24.107-55_cid7_subsidy-DEFAULT_CFC.xml.zip
stock rom and twrp twrp-osprey-3.0.2-r1.img as you told.
and that command also
echo SYSTEMLESS=true>>/data/.supersu
cat /data/.supersu
it shows systemless=true
and installed latest supersu SR1-SuperSU-v2.78-SR1-20160915123031.zip from its official site
after that i wipe cache and dalvik.
i reboot it.
and its get reboot without supersu (root) permission.
what should i do?
Click to expand...
Click to collapse
So you fastboot flashed the ROM and verified it booted successfully (an initial boot is essential prior to rooting, it sets up the RAM disk and other boot image things the first time), rebooted, flashed TWRP (3.0+) and backed up, did the echo command and flashed SuperSU 2.78 SR1 and it still failed?
Flash the 2.62-3 beta of SuperSU https://download.chainfire.eu/751/SuperSU/ it forces systemless install regardless of detected options. You can update normally in the Play Store, then update the binary in the app.
One of those two methods will work, if it doesn't then you have something more going on then meets the eye or there is a piece of information you are not giving us. This is a tested and working process on every single known Moto G 2015 variant.
BTW, clearing cache and dalvik is not required when rooting, you are just increasing the time it takes to boot for no reason.
acejavelin said:
So you fastboot flashed the ROM and verified it booted successfully (an initial boot is essential prior to rooting, it sets up the RAM disk and other boot image things the first time), rebooted, flashed TWRP (3.0+) and backed up, did the echo command and flashed SuperSU 2.78 SR1 and it still failed?
Flash the 2.62-3 beta of SuperSU https://download.chainfire.eu/751/SuperSU/ it forces systemless install regardless of detected options. You can update normally in the Play Store, then update the binary in the app.
One of those two methods will work, if it doesn't then you have something more going on then meets the eye or there is a piece of information you are not giving us. This is a tested and working process on every single known Moto G 2015 variant.
BTW, clearing cache and dalvik is not required when rooting, you are just increasing the time it takes to boot for no reason.
Click to expand...
Click to collapse
well, all the things get installed successfully but even the installation of supersu.zip file also
but it always reboot without any root access or supersu app
i try to install supersu from playstore but it wont help much
after that i tried BETA-SuperSU-v2.62-3-20151211162651.zip this version
and this version does the job
thanks buddy, i really appreciate your help.
acejavelin said:
So you fastboot flashed the ROM and verified it booted successfully (an initial boot is essential prior to rooting, it sets up the RAM disk and other boot image things the first time), rebooted, flashed TWRP (3.0+) and backed up, did the echo command and flashed SuperSU 2.78 SR1 and it still failed?
Flash the 2.62-3 beta of SuperSU https://download.chainfire.eu/751/SuperSU/ it forces systemless install regardless of detected options. You can update normally in the Play Store, then update the binary in the app.
One of those two methods will work, if it doesn't then you have something more going on then meets the eye or there is a piece of information you are not giving us. This is a tested and working process on every single known Moto G 2015 variant.
BTW, clearing cache and dalvik is not required when rooting, you are just increasing the time it takes to boot for no reason.
Click to expand...
Click to collapse
Thanks, thats works for me..! i tried 3 time until work
PD: (when you root, install recovery or unlock bootloader without enough time happens this kind of things)..
Hey guys, had a little problem pop while while setting up my moto 9 g plus.
I have already successfully rooted and verified it on my phone once, and after flashing stock rom, it says in Root Checker App it says "Sorry! Root access is not properly installed on this device.
I thought once successfully rooted, you did not have to worry. I flashed the stock rom, used adb to remove some basic bloatware, and started installing some apps. I already flashed magisk and it shows it is installed successfully, as well as xposed framework, but when I tried to give root access to youtube vanced, it wouldn't let me. That's when I downloaded the root checker again and seen this message.
Anyone have any idea why this happened and how I can fix it? If I need to root my phone again, it's just that I don't know where to begin because I've done it all once. I already have done all the steps to have twrp and magisk. Where do I go from here to get the root verified again?
Thanks!
As soon as you re-flash a ROM all modifications you applied to existing ROM are gone.
jwoegerbauer said:
As soon as you re-flash a ROM all modifications you applied to existing ROM are gone.
Click to expand...
Click to collapse
So where do I go from here? (I edited my main message with a little more info).
Yesi Trotamundos said:
Hey guys, had a little problem pop while while setting up my moto 9 g plus.
I have already successfully rooted and verified it on my phone once, and after flashing stock rom, it says in Root Checker App it says "Sorry! Root access is not properly installed on this device.
I thought once successfully rooted, you did not have to worry. I flashed the stock rom, used adb to remove some basic bloatware, and started installing some apps. I already flashed magisk and it shows it is installed successfully, as well as xposed framework, but when I tried to give root access to youtube vanced, it wouldn't let me. That's when I downloaded the root checker again and seen this message.
Anyone have any idea why this happened and how I can fix it? If I need to root my phone again, it's just that I don't know where to begin because I've done it all once. I already have done all the steps to have twrp and magisk. Where do I go from here to get the root verified again?
Thanks!
Click to expand...
Click to collapse
Already solved...I did verify root after flash and installing magisk, but I did not realize that the security patches would cause screw up root. Just had to reflash magisk and root verification works again.