[GUIDE][osprey][merlin]How to root ANY Moto G 2015 model on Marshmallow

Search This thread

acejavelin

Recognized Contributor
Sep 3, 2009
6,837
3,325
Lincoln, ND
Google Pixel 5a
Thanks a lot!
After flashing XT1541_OSPREY_RETEU_2GB_6.0.1_MPI24.107-55-2_cid7 and after rooting I get stuck on unlock warning screen.
I flashed SuperSU from here https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
And its working for now!

And TWRP is permanent.


:good:

EDIT: This thread should be in here
https://forum.xda-developers.com/2015-moto-g/general/moto-g3rd-gen-roms-kernels-mods-fixes-t3216945
also!
Glad it works... BTW, that thread is ancient, the OP hasn't been updated since October of 2015
 

umo4u

Senior Member
Jan 16, 2013
243
47
Redmi K20 Pro
hello.after doing everything what is said above device is stuck at moto logo.
my model is xt1550
android version is latest official
twrp is 3.0.2 r5
supersu version zip 2.79
kindly i need assistance
 

sanchith.hegde

Senior Member
Oct 12, 2015
105
12

Attachments

  • Screenshot_20170211-163037.png
    Screenshot_20170211-163037.png
    69.9 KB · Views: 151

asr1191

New member
Mar 31, 2017
4
0
I think I messed up :[

I have an Indian XT 1550, 6.0.1 Marshmallow, 1 March 2016 Security Patch.

Here's what I did:
Firstly, I downloaded and booted(not permanently installed) the TWRP version 3.1.0-r1.
Then proceeded to take a backup.
After that, I did NOT download the latest version of SuperSU, instead I downloaded the file that OP linked that was verified to work.
Then I installed the SuperSU without putting the SYSTEMLESS flag. (I got a bit too excited and accidentaly forgot about it. :( )
I realized the mistake when I saw that it failed to create the ramdisk backup.
I let it reboot and saw that there was no apparent difference when my phone booted up.
I boot up TWRP again. echo'd the systemless to .supersu. Then flashed SuperSU 2.78 (from OP link) again. Ramdisk backup failure again.
I didnt let it reboot, and then proceeded to install the SuperSU 2.62-3 Beta, since this guy is using the same model as my phone.
While flashing SuperSU 2.78 it said creating ramdisk backup and then said failure, aborting even after you said to enable writes to system. Never mind I tried again with 2.62-3 beta. And then updated via Play Store to 2.78.

And one more info for other members, on XT1550 Indian model bought from Flipkart, only 2.62-3 BETA worked for me. This is for other Indians planning to root their phones

No errors this time, I thought it was OK. I let it boot up. Bam. com.motorola.ccc has stopped working. also googleplay services. I can't load my homescreen anymore. But thankfully I can use Settings, and connect to my WiFi.

Then, I decided to restore my backup. I booted up TWRP again, and hit Restore. I had ticked all boxes when I backed-up. So it's above 4GB in size. It finished restoring and then I rebooted. Sadly, the problem persists. Still no homescreen and com.motorola.ccc stopped working.. Some apps are updating in the background. I tapped on the notifications and it opened the play store for me through which I can open apps. But that's the only way now.

I tried restoring a couple of times, and installing the latest 2.7.9 version of SuperSU with and without SYSTEMLESS installation.
SuperSU 2.7.9 System Installation went up all the way to "Starting up apps" , but got stuck at that. Rebooting the phone made it stuck at the Motorola stitching animation. Lastly, I did a systemless 2.7.9 which gets me back to the no homescreen problem. I'm not sure where to go from here... :[

Please help. @acejavelin

EDIT: There's almost no apps installed at this point, not even keyboards. Using the inbuilt speech recognition, I was able to download keyboard, and then downloaded the google now launcher. Strangely.. There's no apparent problem now.. I even downloaded the Root Checker app, which tells me the phone's rooted now.

If you think there's no problem now.. My intention to root was to get LineageOS. Shall I give it a try lol?

EDIT2: There's still some functionality that's not working.. Like the voice recognition thing that was added in Marshmallow.. it says "Google App has stopped working". Is there a way to fix the issue?
 
Last edited:

acejavelin

Recognized Contributor
Sep 3, 2009
6,837
3,325
Lincoln, ND
Google Pixel 5a
@asr1191 Open TWRP, wipe system, then restore your TWRP backup, clear caches and data, and reboot. Give it time, as long as it isn't looping (completely restarting to initial boot logo) just leave it sit... It could take 15 or even 25 minutes or more to boot first time.
 

sanchith.hegde

Senior Member
Oct 12, 2015
105
12
I have an Indian XT 1550, 6.0.1 Marshmallow, 1 March 2016 Security Patch.

Here's what I did:
Firstly, I downloaded and booted(not permanently installed) the TWRP version 3.1.0-r1.
Then proceeded to take a backup.
After that, I did NOT download the latest version of SuperSU, instead I downloaded the file that OP linked that was verified to work.
Then I installed the SuperSU without putting the SYSTEMLESS flag. (I got a bit too excited and accidentaly forgot about it. :( )
I realized the mistake when I saw that it failed to create the ramdisk backup.
I let it reboot and saw that there was no apparent difference when my phone booted up.
I boot up TWRP again. echo'd the systemless to .supersu. Then flashed SuperSU 2.78 (from OP link) again. Ramdisk backup failure again.
I didnt let it reboot, and then proceeded to install the SuperSU 2.62-3 Beta, since this guy is using the same model as my phone.


No errors this time, I thought it was OK. I let it boot up. Bam. com.motorola.ccc has stopped working. also googleplay services. I can't load my homescreen anymore. But thankfully I can use Settings, and connect to my WiFi.

Then, I decided to restore my backup. I booted up TWRP again, and hit Restore. I had ticked all boxes when I backed-up. So it's above 4GB in size. It finished restoring and then I rebooted. Sadly, the problem persists. Still no homescreen and com.motorola.ccc stopped working.. Some apps are updating in the background. I tapped on the notifications and it opened the play store for me through which I can open apps. But that's the only way now.

I tried restoring a couple of times, and installing the latest 2.7.9 version of SuperSU with and without SYSTEMLESS installation.
SuperSU 2.7.9 System Installation went up all the way to "Starting up apps" , but got stuck at that. Rebooting the phone made it stuck at the Motorola stitching animation. Lastly, I did a systemless 2.7.9 which gets me back to the no homescreen problem. I'm not sure where to go from here... :[

Please help. @acejavelin

EDIT: There's almost no apps installed at this point, not even keyboards. Using the inbuilt speech recognition, I was able to download keyboard, and then downloaded the google now launcher. Strangely.. There's no <u>apparent</u> problem now.. I even downloaded the Root Checker app, which tells me the phone's rooted now.

If you think there's no problem now.. My intention to root was to get LineageOS. Shall I give it a try lol?

EDIT2: There's still some functionality that's not working.. Like the voice recognition thing that was added in Marshmallow.. it says "Google App has stopped working". Is there a way to fix the issue?

Well, I hope that info I shared helped you. Yeah as acejavelin said, you should allow it for some time to boot up properly.
 

asr1191

New member
Mar 31, 2017
4
0
@acejavelin, @sanchith.hegde thanks for your support :3

But I already kinda installed LineageOS... And apart from Setup Wizard crashing... Nothing seems to wrong till now.. (^__^;) Even root works fine.
If I choose to go back.. Then I'll post updates... Sorry.. ><"
 

sanchith.hegde

Senior Member
Oct 12, 2015
105
12
@acejavelin, @sanchith.hegde thanks for your support :3

But I already kinda installed LineageOS... And apart from Setup Wizard crashing... Nothing seems to wrong till now.. (^__^;) Even root works fine.
If I choose to go back.. Then I'll post updates... Sorry.. ><"

OK. IMO a very very stable ROM for our device is from Ground Zero ROMs (GZR). I suggest you try their ROM. It's very stable. In the end, this is my personal opinion. :)
 

asr1191

New member
Mar 31, 2017
4
0
By the way, @acejavelin , why does the home screen and stuff still "stop working" even though I restore to a previous backup? I tried that after wiping caches/dalvik and stuff..

Also, I'm kinda sure I sat for 25 mins when the phone was stuck at "Starting apps".
 

Arpan22

Senior Member
Jun 23, 2016
98
0
Guys this has been a frustrating issue.When I turn my screen off my phone soft reboots.It happens on every rom.When i install the first 6.0.1 stock rom it freezes after every 5 minutes and reboots.Plz help me.This phone has turned useless,i am using aicp 12 and i have to keep my screen on and it doesnt last 5 hours.
 

KrisM22

Senior Member
Sep 12, 2010
3,966
1,323
many ways to guide, many ways to heal
Guys this has been a frustrating issue.When I turn my screen off my phone soft reboots.It happens on every rom.When i install the first 6.0.1 stock rom it freezes after every 5 minutes and reboots.Plz help me.This phone has turned useless,i am using aicp 12 and i have to keep my screen on and it doesnt last 5 hours.

You are spraying these posts everywhere - please don't do that.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 21
    This guide covers ALL Moto G 2015 models (including the G Turbo) that can be bootloader unlocked and have TWRP available, it doesn't matter if it is the XT1540, XT1541, XT1543, etc., the method is identical. In fact, this method will work on all 2015 and 2016 series Moto phones running Marshmallow, including the Moto E, X, G3, G4, and Z.

    Please read completely and make sure you understand each step and how to do it, if you don't get something search the thread or ask an open question.

    tl;dr version for advanced users: Skip to "How to do it" section

    I am writing this tutorial because there are still lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto G3, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.

    I will only cover the details of rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread.

    Prerequisites:

    1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
    NOTE: Performing this prerequisite will give you all the tools (fastboot) and drivers needed to continue, and wipe your device, meaning erase all your information and programs. Make sure to backup any important data first. This step will also permanently void your warranty once an unlock code has been issued by Moto, it doesn't matter if you even use it, your warranty is done.

    2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See TWRP for the Moto G 2015 or TWRP for Moto G Turbo.

    3) You need a copy of the latest STABLE SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device.

    4) Reboot and start TWRP recovery, the method you use to do this doesn't matter (boot or flash).

    How to do it:

    Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...

    In TWRP, go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:

    Code:
    echo SYSTEMLESS=true>>/data/.supersu

    Now press enter (there is no confirmation returned), then exit and press the Home key. Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).

    Why do I have to do this???

    For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.

    Hope this is helpful to someone!

    As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.

    DISCLAIMER: I am not responsible for anything that happens... Your device, your responsibility, no matter what happens... Although all the information here has been tested and is known to work with no issues except where noted, things occasionally can and do go wrong and we cannot foresee every possible scenario or circumstance.

    If you need assistance, we need detailed information about what what's going on and what you have tried to do... Please provide details including:

    1) Device model number and Android version
    2) TWRP version
    3) SuperSU version
    4) Output of 'cat /data/.supersu' from TWRP terminal

    And a copy of recovery.log if possible, and any other pertinent information you can think of. Without specific information there is nothing that I can do to assist you and request for help may be ignored.

    Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.

    EDIT: I no longer own or use this device, but will keep this thread open and will check it periodically for assisting the few people left out there who haven't rooted their Moto G 2015 yet. :)
    2
    I have no doubt whatsoever, I did something wrong through the process, that why I wanted to make sure everyone knew regardless the systemless install, and echo command would be needed, also SuperSu updated the binary, from within the apk app to the aforementioned version as soon as I restarted.

    So do we not need "Busybox Installer"?
    installed as it would not install from the apk app, I also had read elsewhere that if you wanted "Xposed" would have to be flashed within my recovery, rather than installed as I always had with the apk previously

    Sent from my MotoG3 using XDA-Developers mobile app

    I am able to install busybox from the busybox (stericsson) app, though not tried in stock rom. And, the xposed is needed to be flashed from the recovery, the xposed installer also says that.[emoji4]

    Broadcasted from Zeta Reticuli
    1
    After successful flashing super su it is not showing in app drawer , should I flash it again
    SuperSU should show up in the app drawer after a successful flash.

    Make sure you enabled changes to system, did the terminal command, and when you flash the zip for SuperSU watch the recovery log, it should say something about "systemless". If not, please attach a copy of recovery.log file
    1
    See this.i don't know
    Hmm... looks like it patched the boot.img successfully. Try installing the SuperSU app from the Play Store and see if it says the binary is properly installed.

    I haven't tried this with the 2.77beta yet, I know it had some changes specifically for the Note 7 because Samsung tried to make it unrootable (but failed), I have been using the latest stable build of 2.76
    1
    but you can still get rid of the ads right?
    Partially and temporarily... Each update "fixes" it so they are back. Honestly, most people just pay the extra $50 to avoid the hassle.

    There are specific threads describing the ins and outs of removing the ads in the G4 & G5 areas.