My phone started to act really strange. If I'm turning my phone off, and trying to turn it on again, the phone going into loop, can't reboot it. Fixed only after wiping Delvik Cashe and Cashe, and reflashing the ROM.
But after reboot my phone going into loop again and I need to do the same steps by wiping and reflashing.
Also, when my phone is booting I've checked the root and phone is rooted but after some time root disappearing and says there is no SU binary.
Can somebody give me some advice what I need to do to fix it?
Thank you!
Have you tried another kernel? What kernel and SuperSU are you using?
Sent from my SM-N910P using Tapatalk
samep said:
Have you tried another kernel? What kernel and SuperSU are you using?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Twice tried kernel from Stockish ROM and also tried kernel root by freeza. Still losing root but not at the first but after some time the phone works.
SuperSu is the same. 1.50 beta and stable
antila said:
Twice tried kernel from Stockish ROM and also tried kernel root by freeza. Still losing root but not at the first but after some time the phone works.
SuperSu is the same. 1.50 beta and stable
Click to expand...
Click to collapse
Same kernel. It's not stable for me either. I know a couple of users are using the Chainfire patch on stock kernel and have maintained root longer than me.
I'm basically on it as well after patching the stock kernel to get the backup and su image installed; I setup with SuperSU 2.64 beta systemless root.
You could extract the stock kernel, flash it in a zip for kernel flash it and patch it with SuperSU 2.64 or Odin stock tar and patch it or try a permissive kernel like AEL, Emotion or Plasma kernel for Lollipop 5.1.1
Sent from my SM-N910P using Tapatalk
Related
Hello guys,
I recently attempted to flash the googy max kernel on my GT-I9505 and was successful. After doing so, i rebooted my device just for the sake of it(i don't imagine that rebooting can lose you root access). After rebooting, i attempted to use stweaks and it said that it didn't have root access. I then went ahead and opened up SuperSU and to my horror, it said :
"there is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to android 4.3, you need to manually re-root-consult the relevant forums for your device!"
I then googled the problem and many users advised to flash the latest SuperSU zip using cwm recovery. I tried that twice but still didn't gain back root access. After that, i tried rooting my device again using CF-Autoroot using odin but still, i did not regain root access. Further, CF-Autoroot flashed the stock recovery and i lost cwm too...(makes it even worse) and i can't flash cwm because now i am not rooted! Root checker also says this device does not have proper root access. I would really appreciate help to regain root access! Thanks in advance.
I'm using a GT-I9505 running CM11 M9 snapshot build.
A recovery has nothing to do with root. So you don't need root to flash a recovery.
If you flash CF-root then you lose the google max kernel.
In the kernel thread they say that supersu 2.01 works. So try that version.
Thanks for the reply mate, will get back to you when I've tried it
footballrocks91 said:
Thanks for the reply mate, will get back to you when I've tried it
Click to expand...
Click to collapse
I would download Philz Touch Recovery.. because you can reroot your system easily when you got root before.
Tried flashing SuperSU 2.01 but it didn't work... Will now try the philz way
I tried the philz way and then installed SuperSU from the play store but still I keep getting the same message! I'm running out of options I guess! What to do?? Please help
footballrocks91 said:
I tried the philz way and then installed SuperSU from the play store but still I keep getting the same message! I'm running out of options I guess! What to do?? Please help
Click to expand...
Click to collapse
You go to Philz Settings and than click ReRoot system?
hey guys....
after a while, i contacted my brother and he advised me to re flash cm
i did so and flashed the latest superu and i gained back root access! (phew) i appreciate all the help you guys provided me. Thanks a lot xda and you guys!
This happened to me to so I just flashed KT again..... Well I just wanted to try googy but nvm I'll stick to kt
aram90 said:
This happened to me to so I just flashed KT again..... Well I just wanted to try googy but nvm I'll stick to kt
Click to expand...
Click to collapse
i'm still wondering...should i try googy max again ??
footballrocks91 said:
i'm still wondering...should i try googy max again ??
Click to expand...
Click to collapse
Have you downloaded the right one? For TW and CM there are different googymax kernels
Hi.
I have used crDroid and I have wanted to uninstall system app, so I needed to root. All proces of rooting has been fine (by Odin), but after reboot operating system does not start and I have not got TWRP! Thank you for all your help to me!
Kubex52 said:
Hi.
I have used crDroid and I have wanted to uninstall system app, so I needed to root. All proces of rooting has been fine (by Odin), but after reboot operating system does not start and I have not got TWRP! Thank you for all your help to me!
Click to expand...
Click to collapse
Of course it will not boot. crDroid is rooted by default.
You probably tried to flash cf-auto root and that's ONLY for stock roms. Never ever use it for custom roms because every custom rom has standard root.
Because crDroid is based on CM you probably have to enable root in developer settings or flash the latest supersu trough TWRP.
You need to reflash your rom to get your rom booting again though.
Thank you!
Lennyz1988 said:
Of course it will not boot. crDroid is rooted by default.
You probably tried to flash cf-auto root and that's ONLY for stock roms. Never ever use it for custom roms because every custom rom has standard root.
Because crDroid is based on CM you probably have to enable root in developer settings or flash the latest supersu trough TWRP.
You need to reflash your rom to get your rom booting again though.
Click to expand...
Click to collapse
my sph-l720t wont tun on past logo screen after teying to root. how can i fix this? thanks Dallas
Duwhop31 said:
my sph-l720t wont tun on past logo screen after teying to root. how can i fix this? thanks Dallas
Click to expand...
Click to collapse
No idea. You haven't told us how you tried to root.
So I just updated to the latest xt1644 Nougat JP25.93.14-4 and am having an issue installing TWRP and getting it to stick. I installed it and even did a backup, but once I boot to System and then back to bootloader, and finally to recovery, it goes back to stock recovery. Also I am unsure of how to root this device now with Nougat. I've seen on a few sites differing methods. One site had a download for what they called a root package and it was a SuperSU 2.76 version. Another site said to use Phh SU and just install TWRP and then flash Phh. I don't want to mess anything up, can someone point me in the right direction since it seems everything in this forum is for a device other than the XT1644. Lastly, is it possible to revert back to Marshmellow using fastboot, or is that now not possible? I have unlocked my bootloader, obviously. Thanks.
After flashing TWRP you have to manually boot to TWRP without booting to system first. For rooting you have to flash ElementalX or Vegito Kernel and then flash SuperSU v2.79 SR3 or Magisk v12
.
tywinlannister7 said:
After flashing TWRP you have to manually boot to TWRP without booting to system first. For rooting you have to flash ElementalX or Vegito Kernel and then flash SuperSU v2.79 SR3 or Magisk v12
.
Click to expand...
Click to collapse
I did manually boot it. I went back to bootloader, then choose recovery again and it goes back to TWRP. After I boot to system is when the issue occurs. If I go back to bootloader after booting to system, that is when I have the problem. Once I try to go into recovery again it goes to stack recovery. I am trying to install TWRP 3.0.2.0 Athene.
robn30 said:
I did manually boot it. I went back to bootloader, then choose recovery again and it goes back to TWRP. After I boot to system is when the issue occurs. If I go back to bootloader after booting to system, that is when I have the problem. Once I try to go into recovery again it goes to stack recovery. I am trying to install TWRP 3.0.2.0 Athene.
Click to expand...
Click to collapse
try latest twrp 3.1.0
I got it working. I had originally set it to read only and I think that was the issue. Reinstalled it and mounted system and then choose to allow modifications. It then worked. Now onto root, we will see how that goes.
Sent from my XT1575 using Tapatalk
tywinlannister7 said:
try latest twrp 3.1.0
Click to expand...
Click to collapse
When rooting do you still do the little systemless trick or is that already accounted for. Does the elemental X kernel play well and is it nice and stable? Thanks for the info.
Sent from my XT1575 using Tapatalk
robn30 said:
When rooting do you still do the little systemless trick or is that already accounted for. Does the elemental X kernel play well and is it nice and stable? Thanks for the info.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
If you're using SuperSU v2.79 SR3 beta ( https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133), this already is configured for systemless, and if you're going for SuperSU, that's the version I recommend. Any versions below 2.79 SR3 appear to have created boot issues on Nougat (or required the echo systemless command to work).
ElementalX (1.0.4 stock is what you want) is stable and is essential for rooting. Don't try to root your device without flashing a custom kernel like ElementalX or vegito, else if you try to root the stock Nougat kernel, you'll likely trip anti-root kit/anti-rooting security (dm-verity, I recall?) and will prevent your device from booting. By flashing ElementalX or vegito, you'll bypass that security.
A useful checklist to follow is in this guide here: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 Having a newer version of TWRP shouldn't matter (and in fact may present less issues). With step 6, you may choose to flash either magisk or SuperSU as mentioned by tywinlannister7 (I've not had experience with phh superuser, so cannot comment). If, at some point in the future, you wish to swap rooting methods, I'd suggest following the recommended unrooting procedure for your existing root manager (e.g. unrooting from the SuperSU app settings, or flashing the magisk uninstaller, check their respective pages on XDA) before changing root managers. I've used the aforementioned checklist to root a XT1642 on Nougat without issue.
As for downgrading your system to Marshmallow if you so choose, that is possible. Verify the MM firmware you need (a selection for XT1644, retus channel devices, is here https://mirrors.lolinet.com/firmware/moto/athene/official/RETUS/) and use that firmware with a guide like this: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961 If you're using fastboot rather than mfastboot, replace mfastboot in the provided script with fastboot.
EDIT - no worries @pastorbob62 - good to have another member verifying information
robn30 said:
When rooting do you still do the little systemless trick or is that already accounted for. Does the elemental X kernel play well and is it nice and stable? Thanks for the info.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
NO! NO! NO! Do not use the systemless root method. That is for Marshmallow ONLY!. You will not be able to boot into the system after trying that and you may have to go all of the way back to flashing stock from fastboot to fix it.
ElementX-G4 kernel plays well with Nougat stock. I ran it with stock Nougat for a couple of weeks on my XT1625 without any major issues. So flash it from TWRP. Be sure you have the correct version. Then boot to system to check it out. Next reboot to TWRP and flash SuperSU 2.79. Boot back to the system. It will probably boot a couple of times before the system comes up. Don't panic. You should be good to go.
Edit: Sorry echo92. I was typing my reply at the same time you were. :good:
echo92 said:
If you're using SuperSU v2.79 SR3 beta ( https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133), this already is configured for systemless, and if you're going for SuperSU, that's the version I recommend. Any versions below 2.79 SR3 appear to have created boot issues on Nougat (or required the echo systemless command to work).
ElementalX (1.0.4 stock is what you want) is stable and is essential for rooting. Don't try to root your device without flashing a custom kernel like ElementalX or vegito, else if you try to root the stock Nougat kernel, you'll likely trip anti-root kit/anti-rooting security (dm-verity, I recall?) and will prevent your device from booting. By flashing ElementalX or vegito, you'll bypass that security.
A useful checklist to follow is in this guide here: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 Having a newer version of TWRP shouldn't matter (and in fact may present less issues). With step 6, you may choose to flash either magisk or SuperSU as mentioned by tywinlannister7 (I've not had experience with phh superuser, so cannot comment). If, at some point in the future, you wish to swap rooting methods, I'd suggest following the recommended unrooting procedure for your existing root manager (e.g. unrooting from the SuperSU app settings, or flashing the magisk uninstaller, check their respective pages on XDA) before changing root managers. I've used the aforementioned checklist to root a XT1642 on Nougat without issue.
As for downgrading your system to Marshmallow if you so choose, that is possible. Verify the MM firmware you need (a selection for XT1644, retus channel devices, is here https://mirrors.lolinet.com/firmware/moto/athene/official/RETUS/) and use that firmware with a guide like this: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961 If you're using fastboot rather than mfastboot, replace mfastboot in the provided script with fastboot.
EDIT - no worries @pastorbob62 - good to have another member verifying information
Click to expand...
Click to collapse
Thanks for all the information, it is very much appreciated. Thanks to pastorbob62 as well. This information will be very useful.
Sent from my XT1575 using Tapatalk
pastorbob62 said:
NO! NO! NO! Do not use the systemless root method. That is for Marshmallow ONLY!. You will not be able to boot into the system after trying that and you may have to go all of the way back to flashing stock from fastboot to fix it.
ElementX-G4 kernel plays well with Nougat stock. I ran it with stock Nougat for a couple of weeks on my XT1625 without any major issues. So flash it from TWRP. Be sure you have the correct version. Then boot to system to check it out. Next reboot to TWRP and flash SuperSU 2.79. Boot back to the system. It will probably boot a couple of times before the system comes up. Don't panic. You should be good to go.
Edit: Sorry echo92. I was typing my reply at the same time you were. :good:
Click to expand...
Click to collapse
One other thing, can I back up the stock kernel? Or at least find it somewhere for download. Is this something I can backup using TWRP? Thanks again.
Sent from my XT1575 using Tapatalk
robn30 said:
One other thing, can I back up the stock kernel? Or at least find it somewhere for download. Is this something I can backup using TWRP? Thanks again.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Got it figured out. Backing up my boot.img via TWRP ensures my stock kernel is safe. Already installed elemental X and SuperSU and all went perfectly smooth. Thanks again for the links.
Sent from my XT1575 using Tapatalk
robn30 said:
Got it figured out. Backing up my boot.img via TWRP ensures my stock kernel is safe. Already installed elemental X and SuperSU and all went perfectly smooth. Thanks again for the links.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
You are very welcome. Glad you got it figured out and all is working well. :good:
Hey guys... I know I am late to the thread but if you see this, can you inform me how can I receive updates afterwards? I currently have twrp with elementx kernel and Magisk. And there is a security patch out for the phone. How can I install that?
1emrys1 said:
Hey guys... I know I am late to the thread but if you see this, can you inform me how can I receive updates afterwards? I currently have twrp with elementx kernel and Magisk. And there is a security patch out for the phone. How can I install that?
Click to expand...
Click to collapse
Generally you'd have to revert back to a clean stock ROM, no TWRP, no ElementalX, no magisk. The stock ROM also needs to be in a read only state (no modifications allowed in TWRP) and cannot be debloated (OEM partition needs to be untouched).
You could revert back to a TWRP backup made before you flashed ElementalX, provided you did not let TWRP make modifications. You'd also have to find a stock recovery (if you flashed TWRP), and restore a stock logo.bin as well if you flashed a custom logo.bin to hide the bootloader warning. Then, you should be able to apply OTA/security updates. Attempts to apply OTA updates with TWRP on your device will likely fail and leave you in a soft bootloop unless you boot via the bootloader. You could try this to break the bootloop: https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
The easiest and safest method I've found is to re-flash the stock ROM you have. Ensure this is the same firmware as you currently have and the latest firmware that you've flashed onto your device (don't downgrade your firmware if possible). You can re-flash without erasing your data by omitting the fastboot erase userdata command. However, I would recommend you back up your device anyway (e.g. in TWRP) and any important files, as although this procedure should not affect your data with that command omitted, any firmware flash has the possibility of affecting your device stability. That may require a factory reset/device wipe to fix. Backing up your data should be standard policy when it comes to flashing anything affecting your device's system/underlying firmware.
After re-flashing the stock ROM, you should be able to apply the OTA update.
Thanks a lot for the detailed answer. I really appreciate people like you. [emoji3]
Sent from my Redmi Note 3 using Tapatalk
I used the Nexus Root Toolkit to load the latest factory image LMY49J by Flash Stock + Unroot. I then rooted with the latest SuperSU. After that, every time I rebooted the tablet it would start with Optimizing Apps x of xxx. I did searches on all the forums and tried a few of the suggestions such as wiping the cache and restarting but nothing corrected the problem. I finally ended up using fastboot to restore the stock factory image and it booted without optimizing. Then I flashed TWRP Recovery and rebooted. No optimizing. I flashed SuperSU and rebooted. The optimizing problem was back. Does anyone know why rooting with SuperSU 2.82 is causing the Optimizing Apps for every reboot? I am at the end of my patience with this problem. I've never had any issues with root before.
I do remember reading a while back that su 2.8x have problems.
Try flashing 2.79.
Sent from my YD201 using Tapatalk
Which twrp version are you using? Most recent ones don't have correct SELinux support. You may want to try a pre-3.0 TWRP.
rufy93 said:
I do remember reading a while back that su 2.8x have problems.
Try flashing 2.79.
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
That was going to be my next step.
rufy93 said:
I do remember reading a while back that su 2.8x have problems.
Try flashing 2.79.
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
I've tried TWRP 3.0 and 3.1. If flashing SuperSU 2.79 doesn't work, I may try an earlier version of TWRP.
I actually have not rooted my Nexus 10 using the recovery zip file, I always found the autoroot much more convenient.
I suggest you could try it.
https://autoroot.chainfire.eu
A short scroll down the page you can find the Nexus 10 link.
https://download.chainfire.eu/290/CF-Root/CF-Auto-Root/CF-Auto-Root-manta-mantaray-nexus10.zip
To install using Autoroot:
Open the zip, extract the CF-Auto-Root-manta-mantaray-nexus10.img in the images folder
Reboot to bootloader
Run:
Code:
fastboot boot CF-Auto-Root-manta-mantaray-nexus10.img
Flashing SuperSU 2.79 didn't work. Not much left to try except going back to an earlier version of TWRP or the previous factory image for mantaray.
I'll look into using Autoroot instead of flashing with TWRP.
Thanks everyone for the replies.
Try the TWRP 3.0.2 from this link: http://forum.xda-developers.com/showthread.php?p=66364970
This is the one I use.
twrp 2.8.7.0 fixed the problem for me
mike163 said:
Flashing SuperSU 2.79 didn't work. Not much left to try except going back to an earlier version of TWRP or the previous factory image for mantaray.
I'll look into using Autoroot instead of flashing with TWRP.
Thanks everyone for the replies.
Click to expand...
Click to collapse
got the same problem, downgraded to twrp 2.8.7.0, supersu to 2.79 and it stopped 'optimizing'.
So I reverted to the cited versions of SuperSU (2.79) and TWRP(2.8.7.0). Nexus 10 continues to optimize apps on start up. Scanno's image not available to try _ no mirror it says in that link. Any thoughts. Note: I'm a newbie.
Recently i had a hard brick i had to do a recovery from. So far ive got everything back to working order with latest TWRP installed and everything is working with no problems since. But now I try to install Magisk through TWRP, have the latest version and Magisk manager installed, after its finished it dosent boot. I have to restore from my latest backup after. Also same thing happened when trying to install SuperSu. Anyway to fix this?
What firmware or ROM are you currently running, and what version of magisk are you using?
kwebber321 said:
Recently i had a hard brick i had to do a recovery from. So far ive got everything back to working order with latest TWRP installed and everything is working with no problems since. But now I try to install Magisk through TWRP, have the latest version and Magisk manager installed, after its finished it dosent boot. I have to restore from my latest backup after. Also same thing happened when trying to install SuperSu. Anyway to fix this?
Click to expand...
Click to collapse
Before you root your device, you must replace your stock kernel.
Most people use ElementalX.
https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836/page192
Flash ElementalX through twrp, go through setup and then flash magisk. You'll do good.
If you're confused about ElementalX setup, go through installation tutorials.
Cheers.
ALPH000 said:
Before you root your device, you must replace your stock kernel.
Most people use ElementalX.
https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836/page192
Flash ElementalX through twrp, go through setup and then flash magisk. You'll do good.
If you're confused about ElementalX setup, go through installation tutorials.
Cheers.
Click to expand...
Click to collapse
Is there a custom kernel known to be compatible with the stock Pie ROM?
harryspar said:
Is there a custom kernel known to be compatible with the stock Pie ROM?
Click to expand...
Click to collapse
Do you mean the stock Oreo firmware? We don't have stock Pie
If so, there's ElementalX 3.0.1 https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836 or Loony: https://forum.xda-developers.com/moto-g4-plus/development/3-10-108-loony-kernel-t3726793
echo92 said:
Do you mean the stock Oreo firmware? We don't have stock Pie
If so, there's ElementalX 3.0.1 https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836 or Loony: https://forum.xda-developers.com/moto-g4-plus/development/3-10-108-loony-kernel-t3726793
Click to expand...
Click to collapse
For Nougat, stock kernel is not rootable.
You have to replace it with elementalx kernel and then flash magisk.
However, when talking about Oreo stock firmware,
Situation gets inverted.
When flashed magisk with ElementalX 3.0.1, phone will not boot up.
And, stock kernel can be easily rooted by simply flashing magisk.
So, there is no need of ElemenralX kernel for rooting Oreo stock ROM unless you need it.
You're correct. I meant Oreo.
On my device it never works. Not on the stock kernel, or elemental, or loony.
It boot loops until I run the Magisk uninstaller.
harryspar said:
You're correct. I meant Oreo.
On my device it never works. Not on the stock kernel, or elemental, or loony.
It boot loops until I run the Magisk uninstaller.
Click to expand...
Click to collapse
Hmm, that's odd - are you using magisk 19.3 or a recent version of magisk? When you flashed magisk, did you wipe cache before rebooting?
Is this behaviour observed on completely stock firmware (i.e. you've restored back to full stock Oreo, including a clean stock boot kernel)?
echo92 said:
Hmm, that's odd - are you using magisk 19.3 or a recent version of magisk? When you flashed magisk, did you wipe cache before rebooting?
Is this behaviour observed on completely stock firmware (i.e. you've restored back to full stock Oreo, including a clean stock boot kernel)?
Click to expand...
Click to collapse
I think so. I will double check.
I actually don't need Magisk - my goal is to install Xposed. So in theory I could just try a different superuser. I'm just used to Magisk.
harryspar said:
I think so. I will double check.
I actually don't need Magisk - my goal is to install Xposed. So in theory I could just try a different superuser. I'm just used to Magisk.
Click to expand...
Click to collapse
I hope you get xposed working on Oreo - if you do get magisk functioning, maybe this xposed plugin could work? https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Else there's edxposed https://forum.xda-developers.com/xposed/list-xposed-modules-android-pie-ed-t3892768 though I have no idea if xposed functions on stock Oreo.