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:
Related
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.
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
Hello, so I wanted to root my phone. I went throught the process of unlocking my bootloader, after that the phone still booted up to the system.
Then I installed twrp, and at that point, the phone still booted up to the system. I believe my **** up happens on the next part, which is me putting supersu zip in the external sd of the phone, and then installing it through twrp, and now the phone wont go further than the Honor screen I can get to twrp and fastboot, I'm gonna try to install the stock recovery and stuff through abd now...
https://forum.xda-developers.com/honor-7/help/stuck-honor-logo-t3451993
Follow steps given in this thread, it will work.
Next time back up your phone using TWRP.
Also you are probably stuck in bootloop as you installed version of supersu that is not compatible. Use superSU 2.62 and it should work.
I managed to install TWRP and SuperSU 1.8 on my moto g3.When i clicked it,it gave the error 'superSU binaries are not installed'. Thinking I installed a wrong one, i went ahead and used the superSU for marshmallow.
Now the phone is stuck on bootloader warning page.
I managed to get it to fastboot and TWRP, but have no idea what to do next.
This is my first attempt at rooting and I don't know much.Thanks for help.
Hey guys, so I had the forced update to Android 10 about 1 month ago, and I lost root, which I didn't found about until I tried installing something today.
As this isn't my first time losing root I just followed the steps I always do on this guide (https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509) and I managed to successfully install TWRP, but the phone is now stuck on the orange MI logo when I reboot to system. Someone pls help!
Edit: For anyone curious, I just used the Fix Recovery Bootloop inside TWRP and it worked! I still don't have root tho...
Edit 2: After trying to flash Magisk installer for the second time I determined it to be the problem. Can anyone help me with that?
Use the magisk patched boot.img from here that corresponds with your firmware version and follow to guide to flash in fastboot https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509/page40
garylawwd said:
Use the magisk patched boot.img from here that corresponds with your firmware version and follow to guide to flash in fastboot https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509/page40
Click to expand...
Click to collapse
Just tried that, the phone is stuck again on the orange MI logo and now when I try to boot into TWRP it shows an android laying down with the message "No command" PLEASE HELP
garylawwd said:
Use the magisk patched boot.img from here that corresponds with your firmware version and follow to guide to flash in fastboot https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509/page40
Click to expand...
Click to collapse
Just tried that, the phone is stuck again on the orange MI logo and now when I try to boot into TWRP it shows an android laying down with the message "No command" PLEASE HELP.
Edit: I just flashed TWRP on flashboot and I was able to solve this. I can't still fond what's the issue with magisk tho.
SirAerion said:
Just tried that, the phone is stuck again on the orange MI logo and now when I try to boot into TWRP it shows an android laying down with the message "No command" PLEASE HELP.
Edit: I just flashed TWRP on flashboot and I was able to solve this. I can't still fond what's the issue with magisk tho.
Click to expand...
Click to collapse
What Magisk modules do you have installed? They might be preventing the phone to boot up.
_mysiak_ said:
What Magisk modules do you have installed? They might be preventing the phone to boot up.
Click to expand...
Click to collapse
Afaik the only module I HAD installed before the forced update was Smali patcher for POGO. But I can't check the modules now because the option isn't there in the manager.
SirAerion said:
Afaik the only module I HAD installed before the forced update was Smali patcher for POGO. But I can't check the modules now because the option isn't there in the manager.
Click to expand...
Click to collapse
Well, the module "only" patches framework from the phone, so you're trying to boot Android 10 system with Android 9 framework. It doesn't get uninstalled automatically even if you remove Magisk from boot image.
Either flash Magisk uninstaller from TWRP or flash correct patched boot file, connect phone to the PC, type in this command and reboot the phone.
adb wait-for-device shell magisk --remove-modules