I am using one Moto E 2015 4G (XT1524) European Edition, I have unlocked the bootloader, and managed to flash the TWRP recovery image via fastboot.
Before I flash the CM12.x ROM, I need to install SuperSU.zip, however, when I entered the recovery mode, only "no command" shows up, I can do nothing about this situation.
I tried to install SuperSU through Google Play Store; when I open it, it says "There is no SU binary installed, and SuperSU cannot install it........ If you just upgraded to Android 5.0, you need to manually re-boot ...."
Following what it says, I re-booted the phone, but the SuperSU app still shows the above message when I open it.
What should I do right now? Thank you!
It sounds like your root didn't take. The "no command" recovery is stock. And, if su binary isn't installed, it generally means root didn't take.
Sent from my MotoE2(4G-LTE) using Tapatalk
Related
This is the scenario that i have encountered during rooting my htc one XL for fun. But i have encountered a problem of SuperSU binary "installation failed" when trying to update the binary.
Here i am going to share the solution that have been tried out accidentically.
Premises:
Device : HTC One XL ( i think other device may also counter this problem too when they trying to root with the ZIp version SuperSU apk.
Device's bootloader is unlocked (HTC required, i dont think samsung need this step)
recovery mode Clockworkmod is installed (i think all devices need this mod in order to install apk in the sd_card)
SuperSU apk is installed in recovery mode by install app in the sd_card
Consequence:
The superSU is installed successfully in the phone, you can see the app located in the home screen.
When you try to click in the app, it prompt it requires to update some binary files of the phone. however it will just return "Installation Failed".
Your root access is not stable.
For example:
You might contain root access by using root browser (on google play)
But you couldn't "su" in the linux terminal emulator (on google play)
Also you couldn't "su" by using android shell in the android sdk tools's .adb shell
Solution:
Below is the steps i performed and it is worked.
Update the latest version SuperSU in the google play
Afterwards, it will prompt the binary update screen again
Choose the Txxx/CWB instead of Normal
My device cannot automatically boot up the recovery mode, thus i manually started the recovery mode
binary will be updated when you go in recovery mode
Importance Note:
Actually I am not success in point 5 (binary will be updated when you go in recovery mode).
It means that the binary doesn't update when SuperSU is still the latest version (updated on google store).
and if you have also encountered this circumstance. reboot in the phone again, in the latest version of SuperSU, selected update binary by Txxx/CWB, and then uninstall the latest version of SuperSU by normal apps uninstallation (you can never able to uninstall the old version SuperSU in the phone normally because its installed in the recovery mode).
Now you can boot into the Recovery mode, it will update the binary automatically, And you can grant the actual root access for your phone after reboot the phone again.
Do you think this will work for the Note 3 running 4.4.2 ? for some reason as of now on verizon note 3 there seems to be no fix for the supersu not updating binary on the new kitkat 4.4.2 im rooted using towelroot i let it update the binary once and i never opened it again to avoid it asking me to update again then failing ... so to avoid uninstall and reinstall i just let it do its magic once and never touch it again... it will update the first run but once you reboot .. youre f you also want to make sure you delete the file su in system/xbin/su then uninstall and install fresh to get this to update you binary .. but you can never open it again or it will ask to update and fail ... however all apps asking to grant permisson will be granted so apon screen pop up and your prompt to allow .... but i am however going to try this just dont know if i should choose the txxx/CWB as apose to normal
No Luck to me too.
I did what the top comment said but Super SU still says it needs to update binaries. I am using Version 2.65.
Hey guys,
Just got a new Moto E 2015 (XT1527) and tried rooting it but when I tried flashing TWRP via bootloader, I can't load it.
I've unlocked the bootloader per Motorola's instructions but still can't get to TWRP. I can get to the open Android robot if I restart the phone, and boot back into the bootloader. Undernearth the open Android robot, it says "No commands" and I can't pop up any menus, regardless of what recovery img I flashed.
Any ideas? Would love to root this phone!
Thanks.
My Phone is Lenovo P70 running in Lollipop. TWRP recovery is installed. I've updated Supersu through playstore. Then Supersu suggested me to update binary. I've selected normal mode. It showed successful and the phone should be rebooted. I clicked reboot and I got stuck in Bootloop for 2 min. I just tried to Open recovery. But no use and the phone is not responding now. Any way to make it working.....?
I rooted my phone about a year ago, but did not installed Xposed. Now that I'm going to do it, I can't figure out what custom recovery I'm using, or if I'm even using one. I clearly remember installing cwm or twrp, but when I go to the recovery section of the fastboot menu, it displays an opened android logo with an exclamation mark and text that says 'No command'.
Can anyone help me figure out what's happening? I'm using moto e first generation.
Flash again TWRP via ADB
:good:
I have used king root app, and flashify to flash twrp recovery so i can root with magisk .
After i flashed twrp ,and tried to enter into recovery i get :
security error: this phone has been flashed with unauthorized software
Primary i have used the twrp app to make a back twrp image ,the app itself failed flashing it ,and after ,, success" from flashify i still have the error.
PS: i have developers opinions and OEM turned on .
_________________'_________________
I have find out that my bootloader is locked and that was the reason for the error