root my stock unrooted rom

[Sushilsingh]

hi guys.....
i had recently unroot my moto g3 and install stock root to use my jio sim.
but i really miss the root access so, is there any way to to have root access.
when i flash supersu it will get stuck into bootlogo and will not proceed.
i waited for half an hr but no sign of booting up
anyone have a way to get root access to stock rom plzz help........

 

[jatintomar]

Just flash this super user zip file
http://forum.xda-developers.com/attachment.php?attachmentid=3655401&d=1456122222

 

[HelpMeruth]

is supersu installing systemless?
make sure to do this first in twrp terminal: "echo SYSTEMLESS=true>>/data/.supersu"

 

[acejavelin]

hi guys.....
i had recently unroot my moto g3 and install stock root to use my jio sim.
but i really miss the root access so, is there any way to to have root access.
when i flash supersu it will get stuck into bootlogo and will not proceed.
i waited for half an hr but no sign of booting up
anyone have a way to get root access to stock rom plzz help........

You already have an existing thread on this problem, and were told what needs to be done and where to go to get that information and additional assistance... Why are you not using the resources that were given to you previously? There is no magic fix, something was done incorrectly or you are using the incorrect files.

The answer and all support you will need are in this thread: http://forum.xda-developers.com/2015-moto-g/general/guide-how-to-root-moto-g-2015-model-t3448572

 

[Sushilsingh]

You already have an existing thread on this problem, and were told what needs to be done and where to go to get that information and additional assistance... Why are you not using the resources that were given to you previously? There is no magic fix, something was done incorrectly or you are using the incorrect files.

The answer and all support you will need are in this thread: http://forum.xda-developers.com/2015-moto-g/general/guide-how-to-root-moto-g-2015-model-t3448572

buddy i just install a clean XT1550_OSPREY_RETASIA_DS_2GB_6.0.1_MPI24.107-55_cid7_subsidy-DEFAULT_CFC.xml.zip
stock rom and twrp twrp-osprey-3.0.2-r1.img as you told.
and that command also
echo SYSTEMLESS=true>>/data/.supersu
cat /data/.supersu
it shows systemless=true
and installed latest supersu SR1-SuperSU-v2.78-SR1-20160915123031.zip from its official site
after that i wipe cache and dalvik.
i reboot it.
and its get reboot without supersu (root) permission.
what should i do?

 

[acejavelin]

buddy i just install a clean XT1550_OSPREY_RETASIA_DS_2GB_6.0.1_MPI24.107-55_cid7_subsidy-DEFAULT_CFC.xml.zip
stock rom and twrp twrp-osprey-3.0.2-r1.img as you told.
and that command also
echo SYSTEMLESS=true>>/data/.supersu
cat /data/.supersu
it shows systemless=true
and installed latest supersu SR1-SuperSU-v2.78-SR1-20160915123031.zip from its official site
after that i wipe cache and dalvik.
i reboot it.
and its get reboot without supersu (root) permission.
what should i do?

So you fastboot flashed the ROM and verified it booted successfully (an initial boot is essential prior to rooting, it sets up the RAM disk and other boot image things the first time), rebooted, flashed TWRP (3.0+) and backed up, did the echo command and flashed SuperSU 2.78 SR1 and it still failed?

Flash the 2.62-3 beta of SuperSU https://download.chainfire.eu/751/SuperSU/ it forces systemless install regardless of detected options. You can update normally in the Play Store, then update the binary in the app.

One of those two methods will work, if it doesn't then you have something more going on then meets the eye or there is a piece of information you are not giving us. This is a tested and working process on every single known Moto G 2015 variant.

BTW, clearing cache and dalvik is not required when rooting, you are just increasing the time it takes to boot for no reason.

 

[Sushilsingh]

So you fastboot flashed the ROM and verified it booted successfully (an initial boot is essential prior to rooting, it sets up the RAM disk and other boot image things the first time), rebooted, flashed TWRP (3.0+) and backed up, did the echo command and flashed SuperSU 2.78 SR1 and it still failed?

Flash the 2.62-3 beta of SuperSU https://download.chainfire.eu/751/SuperSU/ it forces systemless install regardless of detected options. You can update normally in the Play Store, then update the binary in the app.

One of those two methods will work, if it doesn't then you have something more going on then meets the eye or there is a piece of information you are not giving us. This is a tested and working process on every single known Moto G 2015 variant.

BTW, clearing cache and dalvik is not required when rooting, you are just increasing the time it takes to boot for no reason.

well, all the things get installed successfully but even the installation of supersu.zip file also
but it always reboot without any root access or supersu app
i try to install supersu from playstore but it wont help much
after that i tried BETA-SuperSU-v2.62-3-20151211162651.zip this version
and this version does the job
thanks buddy, i really appreciate your help.

 

[saga02]

So you fastboot flashed the ROM and verified it booted successfully (an initial boot is essential prior to rooting, it sets up the RAM disk and other boot image things the first time), rebooted, flashed TWRP (3.0+) and backed up, did the echo command and flashed SuperSU 2.78 SR1 and it still failed?

Flash the 2.62-3 beta of SuperSU https://download.chainfire.eu/751/SuperSU/ it forces systemless install regardless of detected options. You can update normally in the Play Store, then update the binary in the app.

One of those two methods will work, if it doesn't then you have something more going on then meets the eye or there is a piece of information you are not giving us. This is a tested and working process on every single known Moto G 2015 variant.

BTW, clearing cache and dalvik is not required when rooting, you are just increasing the time it takes to boot for no reason.

Thanks, thats works for me..! i tried 3 time until work

PD: (when you root, install recovery or unlock bootloader without enough time happens this kind of things)..