XT1064 Lollipop Root

Status
Not open for further replies.
Search This thread

sweethruvers893

Senior Member
Oct 16, 2013
67
19
Did you have your boot-loader unlocked before your install of Lollipop?

I had to re-lock mine to install the OTA and I just finished unlocking it again. I think it's stuck on a bootloop. I'm also not able to boot into Android recovery. Any ideas?

EDIT: Nevermind; sorry for the mistake. It's booting back up.
 
Last edited:

savoca

Inactive Recognized Developer
Oct 28, 2011
1,784
5,703
Pasadena
downloads.codefi.re
Google Pixel 7
Did you have your boot-loader unlocked before your install of Lollipop?

I had to re-lock mine to install the OTA and I just finished unlocking it again. I think it's stuck on a bootloop. I'm also not able to boot into Android recovery. Any ideas?

No I just uninstalled Xposed, restored stock recovery, took the OTA and moved on. You may have to restore factory firmware from fastboot.
 
  • Like
Reactions: sweethruvers893

sweethruvers893

Senior Member
Oct 16, 2013
67
19
No I just uninstalled Xposed, restored stock recovery, took the OTA and moved on. You may have to restore factory firmware from fastboot.

Thanks for your help. So we just flash the .img, flash SuperSu from the site, and fastboot flash recovery? Thanks again.

EDIT: Uh, I'm not booting past the unlocked bootloader screen after flashing your .img.

EDIT 2: I'm just a person that worries a lot. Gave it a few minutes to load and it works. Thanks. Really sorry to discredit you.

EDIT 3: Thanks man.

LYnDCjK.png
 
Last edited:

NekoNieves

Member
Oct 18, 2014
41
37
FL
I can't seem to get root, I flash superSu after the boot img but still no root :(
edit: nevermind I figured it out thanks!
 
Last edited:
L

luckiesjohnny

Guest
Which Version of SuperSU are you flashing?

2.16?
Beta 2.17 or 2.19?

Greetz
 

savoca

Inactive Recognized Developer
Oct 28, 2011
1,784
5,703
Pasadena
downloads.codefi.re
Google Pixel 7
Hello.

Are you using chainfires method as described here https://plus.google.com/app/basic/stream/z13fjtr4voemxt4ph04cjl1aoor5ezninhc

Does this method set all selinux permissive or just the part that will allow the root daemon to be called at init?

Also have you tried modifying the hosts file? Does it work?

Sent from my XT1064 using XDA Free mobile app

All I did allow the su daemon to init from the ramdisk - similar to how custom ROMs implement this.

Which Version of SuperSU are you flashing?

2.16?
Beta 2.17 or 2.19?

Greetz

Did you use these?
90948cf5c618f3dd3c3c8bd9f4b217a8 *TWRP_2.8.0.1_Titan_v2.img
75470360687a16f08289d81bc58f1130 *UPDATE-SuperSU-v2.16.zip
They worked fine for me on 4.4.4, just like verification for the "warm fuzzy."

Yes to the TWRP, (though we should make it an official build :( )

And 2.16 worked for me but I am currently using this: http://imgur.com/nYiwW7L :)
 
Last edited:
L

luckiesjohnny

Guest
Thanks a lot.
I've tried it already with 2.19 and it worked fine.
 

Bobboman

Senior Member
May 13, 2010
226
24
ok... so how do i get past the whole mismatched partition size block that has also kept me from flashing a custom recovery?
 

Bobboman

Senior Member
May 13, 2010
226
24
yea i figured that out...however now i can't even boot my moto g to anything but the bootloader

thank god i have the 4.4.4 stock files on my laptop, time to get flashing...anyone got a link to the most recent version of supersu?
 

Bobboman

Senior Member
May 13, 2010
226
24
blah i think i bricked my phone, i cant get past the moto logo, but i can get into the bootloader, not that helps anything
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 27
    Step 1: Download this: http://downloads.codefi.re/savoca/root/titan
    Step 2: fastboot flash boot xt1064_lollipop_boot.img
    Step 3: Flash SuperSU

    http://imgur.com/jJO86tC
    4
    So, after 2 days of intense debugging, both me and Chainfire have run out of ideas. It is a very complex issue. We don't have a clue as to why the firmware loading fails for the GPU some of the times with su installed. There is no plan of action as of now. The only way it can be debugged better is if Chainfire gets a hold of Moto G 2014 himself. Sorry, don't have a better news to share...:(

    If it will help, with development, and everyone gain Root access..have him (CF) contact me, I will send him my device.!!

    If he wishes to continue..If not..I certainly understand..

    Almost new XT1064 on KK..

    Exclusive Moto user since 1989..
    XT1080M Droid Maxx Developer Edition
    http://waynekent.com/page6.html
    "Praise Jah" YOU people.!
    3
    Making some progress in determining the cause of the bootloops. You can follow the SU BETA thread at http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/page27#post57933574

    Basically, it looks like adreno driver initialization is hitting an error when the system is rooted. It fails to load the firmware and kernel panics, causing the reset to happen. It looks like /system is unmounted at exact that time by SU for some reason. So, its a race condition, which we win once in 7 or so boots! Hang on for more! I am close.
    2
    I told him this on the IRC. May be he will get in touch with on PM.

    Chainfire has ordered one for himself and he will get it in few days. There is hope of getting a stable root on this device in couple of weeks...:)
    2
    I just tried flashing SuperSU 2.35 on a clean install of 5.0. It's a no go; stuck in a boot loop as with 2.27 BETA. Hope this save some of you guys some trouble/time.