i have moto g 1st gen.
i have successfully unlocked the bootloader from motorola site. After that i flashed cwm recovery from windows and using the recovery first i flashed SUPERSU and then the rom SLIMSABER. The rom successfully installed and then i installed titanium backup it says cant access the root folder. I opened supersu it says SU BINARIES ARE NOT PROPERLY INSTALLED . REROOT MANUALLY.
PLEASE HELP
THANKS
Did you update SuperSU on Play Store?
yes i have updated supersu from playstore
please help
thanks
DavaySuka said:
Did you update SuperSU on Play Store?
Click to expand...
Click to collapse
yes i have updated supersu from playstore
please help
thanks
Maybe you should download the flashable zip of supersu from chainfire site then flash it through your custom recovery, and i think you better use twrp recovery, it's more updated. Hope this could help you...
Flash zip in custom recovery: https://download.chainfire.eu/396/supersu/
In January I installed SuperSU 2.6.2-3 in accordance with this forum. Interestingly, today I received notification from the Playstore to update SuperSU to 2.65 (dtd Feb 01, 2016). I don't know why I received this notification from the Playstore since I did not install from there and did not receive this notification much earlier. Also, I assume updating to 2.65 through the Playstore would not be a good idea.
Chainfire has recently decided that SuperSU 2.65 was Stable. Only Stable versions get pushed to the Play Store, so that's why you got an update. I believe it will be safe to install, but be sure to make a backup via TWRP first.
Funcionando en Moto g 2015 xt1543 México [MM]
Probé la actualización y todo bien ? OK
TVD1903 said:
Chainfire has recently decided that SuperSU 2.65 was Stable. Only Stable versions get pushed to the Play Store, so that's why you got an update. I believe it will be safe to install, but be sure to make a backup via TWRP first.
Click to expand...
Click to collapse
But my first SuperSU flash was 2.65. And like many others on this forum who did the same, this version soft bricked my phone (stuck on unlocked boot loader screen). Are you saying 2.65 is safe to install on top of 2.6.2-3 but not safe as an initial install?
MrTooPhone said:
But my first SuperSU flash was 2.65. And like many others on this forum who did the same, this version soft bricked my phone (stuck on unlocked boot loader screen). Are you saying 2.65 is safe to install on top of 2.6.2-3 but not safe as an initial install?
Click to expand...
Click to collapse
I think so yes, as the new version was designed as a version to be compatible with every version of Android an to be installed over older versions. Do make a backup though, and if you are afraid, just don't do it. It won't hurt to stay on an older version for a while. You can install the update to the app because that will not immediately install the actual SuperSU update. Do not accept the prompt when opening the app for updating the binary in that case though.
TVD1903 said:
I think so yes, as the new version was designed as a version to be compatible with every version of Android an to be installed over older versions. Do make a backup though, and if you are afraid, just don't do it. It won't hurt to stay on an older version for a while. You can install the update to the app because that will not immediately install the actual SuperSU update. Do not accept the prompt when opening the app for updating the binary in that case though.
Click to expand...
Click to collapse
So what version of SuperSU do you have installed? How did you install that version? On top of a previous version or a fresh TWRP flash?
MrTooPhone said:
So what version of SuperSU do you have installed? How did you install that version? On top of a previous version or a fresh TWRP flash?
Click to expand...
Click to collapse
I am using a Custom ROM with SuperSU built-in. I have however also used the Stock ROM with SuperSU v2.65, installed using TWRP.
Got the same notification, updated fine, updated also su binaries (asked by the app) and - everything works fine. Stock 6.0.
Well I was reluctant to try based on my first experience flashing 2.65. But I accepted the update via Playstore, SuperSU updated the binaries, rebooted, and all is still good.
I would assume all those rooting the G3 MM for the first time should use 2.62-3 then upgrade to 2.65.
MrTooPhone said:
I would assume all those rooting the G3 MM for the first time should use 2.62-3 then upgrade to 2.65.
Click to expand...
Click to collapse
This is how I did mine when following the thread :
[GUIDE] [OSPREY] [MM] Install TWRP, Root and Xposed successfully on 6.0
Installed 2.62-3, then just received the 2.65 from the app store. No problems here either. Not sure about the TWRP update from 2.8.7 r7 to the 3.x.x versions though, but I am getting the impression that due to extensive changes it is not a good idea.
pjc123 said:
This is how I did mine when following the thread :
[GUIDE] [OSPREY] [MM] Install TWRP, Root and Xposed successfully on 6.0
Installed 2.62-3, then just received the 2.65 from the app store. No problems here either. Not sure about the TWRP update from 2.8.7 r7 to the 3.x.x versions though, but I am getting the impression that due to extensive changes it is not a good idea.
Click to expand...
Click to collapse
I have had no issues backing up with twrp-osprey-3.0.0-r2.img. I have not tried restoring yet.
I see there was an update yesterday again from the play store (version 2.79). Has anyone tried it? I am on stock, root, with TWRP (3.0.2-r1). I see I am falling behind on TWRP as well, seeing it is at 3.0.2-r5.
pjc123 said:
I see there was an update yesterday again from the play store (version 2.79). Has anyone tried it? I am on stock, root, with TWRP (3.0.2-r1). I see I am falling behind on TWRP as well, seeing it is at 3.0.2-r5.
Click to expand...
Click to collapse
don'tn worry ... the update works perfectly ...
..::Matr!x::.. said:
don'tn worry ... the update works perfectly ...
Click to expand...
Click to collapse
Thanks.
pjc123 said:
I see there was an update yesterday again from the play store (version 2.79). Has anyone tried it? I am on stock, root, with TWRP (3.0.2-r1). I see I am falling behind on TWRP as well, seeing it is at 3.0.2-r5.
Click to expand...
Click to collapse
I have received several updates since 2.62-3. All have installed from playstore just fine including 2.79. As an initial installation, I think 2.62-3 was the only one that installed as systemless without forcing a systemless installation. Once you have a successful installation, all updates should be as well.
Sorry I'm not able to help you but you can help me. I soft brick my Moto g xt2541 twice due to different super su and wrong recoveries . Can you please provide me links u used to root. My issue is listed here. http://forum.xda-developers.com/2015-moto-g/help/unable-to-root-moto-g-2015-1-gb-model-t3523471 your help is much appriciated
Sent from my MotoG3 using Tapatalk
mirpuri said:
Sorry I'm not able to help you but you can help me. I soft brick my Moto g xt2541 twice due to different super su and wrong recoveries . Can you please provide me links u used to root. My issue is listed here. http://forum.xda-developers.com/2015-moto-g/help/unable-to-root-moto-g-2015-1-gb-model-t3523471 your help is much appriciated
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
I followed these directions eleven months ago for the initial unlock bootloader, TWRP recovery and root, using the versions of SuperSU and TWRP listed, however I did not install Xposed.
http://forum.xda-developers.com/201...twrp-root-xposed-t3294588:confused::confused:
I have since updated to:
SuperSU 2.79
TWRP 3.0.2-r1
Caveat: My phone is a XT1540.
Anyone had any luck getting root on Stock marshmallow? I flashed 2.67 Super bu couldn't get past the splash screen
Moto G User said:
Anyone had any luck getting root on Stock marshmallow? I flashed 2.67 Super bu couldn't get past the splash screen
Click to expand...
Click to collapse
As suggested in this thread, I flashed superSu BETA v2.62-3 (zip format) with the TWRP (3.0.0r2.
After that, updated superSu (apk) from the play store.
Then launched the app, and let it update the su-binary.
And now, supersu v2.65 is working like a charm on my stock Marshmallow XT1541 rom (XT1541_OSPREY_RETEU_2GB_6.0_MPI24.65-33).
rom-g said:
As suggested in this thread, I flashed superSu BETA v2.62-3 (zip format) with the TWRP (3.0.0r2.
After that, updated superSu (apk) from the play store.
Then launched the app, and let it update the su-binary.
And now, supersu v2.65 is working like a charm on my stock Marshmallow XT1541 rom (XT1541_OSPREY_RETEU_2GB_6.0_MPI24.65-33).
Click to expand...
Click to collapse
Thanks for the help. Got it working
So my unlocked Google Pixel was rooted until I recently received the NHG47K OTA update and now it is not....
SuperSU is showing installed, but when I open it up, I get a message saying that "There is no SuperSU binary installed and SuperSU cannot install it."
I didn't expect to lose root as I don't believe I ever actually authorized the OTA update to get installed... just woke up one day to find that my phone is no longer rooted.
Can someone please recommend the most efficient method to regaining root from here?
Thanks
pstgh said:
So my unlocked Google Pixel was rooted until I recently received the NHG47K OTA update and now it is not....
SuperSU is showing installed, but when I open it up, I get a message saying that "There is no SuperSU binary installed and SuperSU cannot install it."
I didn't expect to lose root as I don't believe I ever actually authorized the OTA update to get installed... just woke up one day to find that my phone is no longer rooted.
Can someone please recommend the most efficient method to regaining root from here?
Thanks
Click to expand...
Click to collapse
Boot to twrp and reflash the SU binary.
With the new OTA build, do I need an updated TWRP.img file and/or a newer SU binary?
pstgh said:
With the new OTA build, do I need an updated TWRP.img file and/or a newer SU binary?
Click to expand...
Click to collapse
Questions go in the "Google Pixel Questions & Answers" section.
Always use the latest of both unless you read otherwise - for example, if you read the TWRP thread, you'll see a lot of people have trouble with RC2, so just stick with RC1.
pstgh said:
With the new OTA build, do I need an updated TWRP.img file and/or a newer SU binary?
Click to expand...
Click to collapse
Boot to TWRP RC1, then install SU RC3. Assuming you don't want TWRP permanently installed.
I try all method to install supersu (flash suppersu through TWRP, both slot A and B; install all version supersu, from many site: appure, apphere, appvn), none of these work. Anyone has any ideas how to install for Razer's rooted?
Anyone same me?
What software version are you on?. And are you on three network
parky169 said:
What software version are you on?. And are you on three network
Click to expand...
Click to collapse
Razer phone's os is Android 7.1 "Nougat". It was root with magisk follow this guide:
PHP:
https://forum.xda-developers.com/razer-phone/how-to/twrp-magisk-fullproof-guide-razers-wifi-t3756137
Now, I try install supersu both: google play store and
PHP:
https://apkpure.com/supersu/eu.chainfire.supersu
but when I try update supersu su binary update, it always fails.
anyone please help me.
Is it the latest global version or three branded latest version?. I found that the latest software version from three fails ever time, the latest global software works first time.
If you install the magisk 16,it won't ask to update binaries.
parky169 said:
Is it the latest global version or three branded latest version?. I found that the latest software version from three fails ever time, the latest global software works first time.
If you install the magisk 16,it won't ask to update binaries.
Click to expand...
Click to collapse
I install cheryl-global-851.zip & rooted by magisk v16. so that mean we don't need supersu?
Magisk has supersu embedded
parky169 said:
Magisk has supersu embedded
Click to expand...
Click to collapse
thank you.