Database Develop

[Q] No CF-Auto-Root for XT1064? XT1063 works fine?

Hi,
I just got a new Moto G, but it's the XT1064 version. I'd like to root, but it seems there's no XT1064 option for CF-Auto-Root from Chainfire. Should I use the XT1063 one?
http://autoroot.chainfire.eu/
motorola XT1063 titan_retuglb titan_umts MSM8226 msm8226 KXB21.85-17 4.4.4 11 720 230 Download a71b95caf989138032a5c4f0dad83519 2 387
Thanks

Sakura90 said:
Hi,
I just got a new Moto G, but it's the XT1064 version. I'd like to root, but it seems there's no XT1064 option for CF-Auto-Root from Chainfire. Should I use the XT1063 one?
http://autoroot.chainfire.eu/
motorola XT1063 titan_retuglb titan_umts MSM8226 msm8226 KXB21.85-17 4.4.4 11 720 230 Download a71b95caf989138032a5c4f0dad83519 2 387
Thanks
Click to expand...
Click to collapse
I have had a huge amount of frustration attempting to root the XT1064 over the past couple of days. If you're not afraid of reflashing your phone then you can try it but I highly doubt you'll be able to get it to work.
You can easily upgrade it to Lollipop with "official" firmware, but rooting has given me bootloop after bootloop.
After purchasing the Moto G XT1064 and spending 8+ hours trying to update and root the phone and remove all of the Motorola crapware, I eventually gave up. Right now I have version 22.11.6 installed, which is named "Blur_Version.21.11.17.titan_retuaws.retuaws.en.US.zip", it makes sense to include the old version number, but they should at least call it "Blur_Version_from.21.11.17.titan...".
I really wish Google would REQUIRE manufacturers to release a stock android rom and an easy way to flash it with every consumer Android phone sold. Then developers could focus on improving the phone instead of millions of programmer-hours wasted on trying to remove the crapware and get it updated.
If you're a developer who wants a clean phone and don't want to waste dozens of hours screwing with flashing roms, just get a GPE or Nexus device, it's not worth saving $200. It's a great phone, but if you were looking for a phone that is easy to develop with, this doesn't seem like the right one. After my Droid X I swore off non-nexus devices, but the Amazon sale got me.
A couple of people claim to be able to get UPDATE-SuperSU-v2.16.zip working, (yes, SuperSU v2.39 exists now, it probably won't work though), but many more people (including myself) were not able to get it working.
Good luck! Please report back if you find a good solution, I'm guessing that many people are tired of the hoops we have to jump through to get a non-crapware stock Andorid device.

The seller kindly told me he can exchange my XT1064 for an XT1063, as rooting is my first concern (need to get Japanese fonts on it). So I hope to easily root with CF-Auto-Root now. I'll get my new phone in two days. I'm already crossing my fingers . Rooting should be a readily available option by the manufacturer, just like Motorola offers you to unlock the bootloader. Otherwise you're extremely limited. For example, to change a font. Samsungs let you do it in the original firmware, something as basic as this should already be in stock Android. And at least ext2 support, it's a Linux FS from 1993. We are stuck with crappy FAT32.
Btw, I just found this tweet by Chainfire: https://twitter.com/chainfirexda/status/533298320647925760
@ChainfireXDA are you going to be doing a CF-Auto-Root for the moto g xt1064? or will the one for the 1063 work? @Bobboman_2000 1063 version should work
Can you try it on the XT1064? I don't know the risk, but if you say you can reflash the firmware, maybe you can go back?

Sakura90 said:
The seller kindly told me he can exchange my XT1064 for an XT1063, as rooting is my first concern (need to get Japanese fonts on it). So I hope to easily root with CF-Auto-Root now. I'll get my new phone in two days. I'm already crossing my fingers . Rooting should be a readily available option by the manufacturer, just like Motorola offers you to unlock the bootloader. Otherwise you're extremely limited. For example, to change a font. Samsungs let you do it in the original firmware, something as basic as this should already be in stock Android. And at least ext2 support, it's a Linux FS from 1993. We are stuck with crappy FAT32.
Btw, I just found this tweet by Chainfire: https://twitter.com/chainfirexda/status/533298320647925760
@ChainfireXDA are you going to be doing a CF-Auto-Root for the moto g xt1064? or will the one for the 1063 work? @Bobboman_2000 1063 version should work
Can you try it on the XT1064? I don't know the risk, but if you say you can reflash the firmware, maybe you can go back?
Click to expand...
Click to collapse
I'll probably try it tonight. Will let you know the result.
You can change the file systems using: TWRP2.7.1.1-titan-motog-2014.img as your recovery.
I agree about the manufacturers. I thought it was growing pains in the early days of Android but we millions of us have to waste several hours trying to get decent security, privacy, and performance out of our phones. All anybody wants is stock Android.

Great if you try, I've seen no feedback of someone using it on XT1064. Won't changing the recovery affect future OTA updates? I was thinking of trying Stickmount with NTFS-3G. It only needs rooted device.

Sakura90 said:
Great if you try, I've seen no feedback of someone using it on XT1064. Won't changing the recovery affect future OTA updates? I was thinking of trying Stickmount with NTFS-3G. It only needs rooted device.
Click to expand...
Click to collapse
I was able to get 5.0 rooted. Not with CF Auto Root though.
I used TWRP2.7.1.1-titan-motog-2014.img and BETA-SuperSU-v2.38.zip but SuperSU had to be put on my internal storage.

Can you go back to stock recovery after installing SuperSU? As to have future OTA updates. I'm mean, only use TWRP for rooting.

derekm_ said:
I was able to get 5.0 rooted. Not with CF Auto Root though.
I used TWRP2.7.1.1-titan-motog-2014.img and BETA-SuperSU-v2.38.zip but SuperSU had to be put on my internal storage.
Click to expand...
Click to collapse
You put SuperSU on internal storage because that's the only way TWRP can flash it or because that's the only way you could get root (I.e., flashing from external storage didn't work)?
I have tried both CFAutoRoot and flashing SuperSU from external storage. SuperSU resulted in bootloop. AutuRoot worked but I couldn't power off my phone without the next power up throwing things into a bootloop. I chose not to leave my phone on all the time, so flashed a non-root backup.
I haven't tried flashing SuperSU from internal storage. So maybe that's something to try.

Root w/ Encryption

I did a couple of searches and came up empty but I am wondering if any ROM developers are working with encryption and root?
When I had my Galaxy S5 (Tmobile) it was first encrypted. I recall then once I rooted it I was no longer able to encrypt the device. I think there may have been some workarounds but they were pretty cumbersome to say they even worked at all.
I'm wondering if any developers are working that angle and if so should my inquiry be presented to developer of said ROM?
I also realize that encrypted devices do tend to read a bit slower than those no encrypted but I think I can live with that.
Please advise.
Best,
Hiatt

cwhiatt said:
I did a couple of searches and came up empty but I am wondering if any ROM developers are working with encryption and root?
When I had my Galaxy S5 (Tmobile) it was first encrypted. I recall then once I rooted it I was no longer able to encrypt the device. I think there may have been some workarounds but they were pretty cumbersome to say they even worked at all.
I'm wondering if any developers are working that angle and if so should my inquiry be presented to developer of said ROM?
I also realize that encrypted devices do tend to read a bit slower than those no encrypted but I think I can live with that.
Please advise.
Best,
Hiatt
Click to expand...
Click to collapse
Hello Hiatt,
Thanks for using XDA Assist. What specific device do you currently have? There are so many devices here and each might deal with your question differently. I moved your other thread to off topic since it was referring to iPhones, but this one seems to have a more specific device in mind.
Thanks,
coal686

I presently have a Tmobile Galaxy S6 which is rooted and running Sick as Hell (version X).
From what I have read and heard it seems as though root and encryption together don't always play well together.
Also, it was the other post of mine that mentioned iPhones (the one about factory resets and eDiscovery).

cwhiatt said:
I presently have a Tmobile Galaxy S6 which is rooted and running Sick as Hell (version X).
From what I have read and heard it seems as though root and encryption together don't always play well together.
Also, it was the other post of mine that mentioned iPhones (the one about factory resets and eDiscovery).
Click to expand...
Click to collapse
Lol, that's what I said. The other post was more about the iPhone issue so I moved it to off-topic. Since you have a Galaxy S6, I'll move this thread there so people with that device can give you a more personalized answer.

I don't think that having root is an issue with encryption. I Had my S5 encrypted only problem was a ui crash when entering the boot password. That was specific to the rom I was using and simply had to enter password 1 or 2 characters at a time between errors.
But I do think there may be a problem with custom recovery and encryption.
My S5 was verizon, thus still locked bootloader and used safestrap to get to a custom recovery which wasn't always active.
I would talk to someone with a lot more knowledge then I about this further. But pretty sure just having root is not a problem the recovery is where you can have issues

cwhiatt said:
I did a couple of searches and came up empty but I am wondering if any ROM developers are working with encryption and root?
When I had my Galaxy S5 (Tmobile) it was first encrypted. I recall then once I rooted it I was no longer able to encrypt the device. I think there may have been some workarounds but they were pretty cumbersome to say they even worked at all.
I'm wondering if any developers are working that angle and if so should my inquiry be presented to developer of said ROM?
I also realize that encrypted devices do tend to read a bit slower than those no encrypted but I think I can live with that.
Please advise.
Best,
Hiatt
Click to expand...
Click to collapse
Hi there,
Root + Encryption can work together as long as no custom recovery involved, so if you get your root by exploit instead of installing custom recovery almost 99% chance you can have your phone encrypted while preserving the root privilege.
My case explained here : http://forum.xda-developers.com/galaxy-note-3/general/success-root-encryption-t3372958

I didn't have a problem with encryption and root. The only problem that I had was that my Galaxy S6 Edge needed to be encrypted before root. I could not encrypt my phone with the "stock" rooted kernel. Once I was encrypted, I could install TWRP and root via supersu systemless root.
Once I had root, I would use flashfire to back up and install because TWRP could not read the DATA partition since it was encrypted. For some reason, it seems once the phone has been decrypted, the data partition could be backed up with flashfire, and I would be able to restore a backup as well.
This is where I ran into issues. If you are flashing a custom rom that will require you to wipe data, your device will lose encryption. Because I can be somewhat of a crack flasher at times, and that I am too lazy to deal with having to re-encrypt and reinstall all my settings, I just opted to stick with an unencrypted phone.
Hopefully at some point, TWRP will be compatible with encryption so that lives will be easy for us crack flashers..until then, I will probably stick with an unencrypted device unless I just want to stick with a stock rom, or a custom rom that I can load up and not have to wipe data every time there is an update.

Working 4g after flash.

I have the Sprint version of the g5 s plus. I have tried every way of flashing a rom that I can think of (all wipes rom then gapps magisk, magisk then gapps, rom and no gapps or magisk, etc.). I cannot manage to keep 4g after flashing. I have backed up my efs with twrp and tried restoring it. Nothing. I've used fastboot to flash nhlos erase modems1&2 flash fsg. I tried *#*#463whatever to turn it back on and nothing. I've checked all settings and tried all things I know of. Still nothing. The only way I can get/keep 4g is by using stock rooted which I hate. . Is this just a specific problem to my type of phone or is there something I'm missing? Is there a different firmware or modem I could use or something? Any thoughts or ideas would be great cause I'm stumped.

always6s said:
I have the Sprint version of the g5 s plus. I have tried every way of flashing a rom that I can think of (all wipes rom then gapps magisk, magisk then gapps, rom and no gapps or magisk, etc.). I cannot manage to keep 4g after flashing. I have backed up my efs with twrp and tried restoring it. Nothing. I've used fastboot to flash nhlos erase modems1&2 flash fsg. I tried *#*#463whatever to turn it back on and nothing. I've checked all settings and tried all things I know of. Still nothing. The only way I can get/keep 4g is by using stock rooted which I hate. . Is this just a specific problem to my type of phone or is there something I'm missing? Is there a different firmware or modem I could use or something? Any thoughts or ideas would be great cause I'm stumped.
Click to expand...
Click to collapse
You're not the only one. I'm just happy I was never on Sprint. Worked with someone who had same issues - no resolution but to keep stock. Maybe when moto releases Oreo it'll be different. Good luck!

Phazmos said:
You're not the only one. I'm just happy I was never on Sprint. Worked with someone who had same issues - no resolution but to keep stock. Maybe when moto releases Oreo it'll be different. Good luck!
Click to expand...
Click to collapse
I really hate that but I think ur right brother b

Try this
It fixed my 4g problem

rygle said:
Try this
It fixed my 4g problem
Click to expand...
Click to collapse
I shall try and see

always6s said:
I have the Sprint version of the g5 s plus. I have tried every way of flashing a rom that I can think of (all wipes rom then gapps magisk, magisk then gapps, rom and no gapps or magisk, etc.). I cannot manage to keep 4g after flashing. I have backed up my efs with twrp and tried restoring it. Nothing. I've used fastboot to flash nhlos erase modems1&2 flash fsg. I tried *#*#463whatever to turn it back on and nothing. I've checked all settings and tried all things I know of. Still nothing. The only way I can get/keep 4g is by using stock rooted which I hate. . Is this just a specific problem to my type of phone or is there something I'm missing? Is there a different firmware or modem I could use or something? Any thoughts or ideas would be great cause I'm stumped.
Click to expand...
Click to collapse
Sorry, just saw this. I'm the Sprint user Phazmos mentioned. The problem is whatever source, base, proprietary blobs, etc., that the developers on here all seem to be using for the 3rd-party ROMs doesn't seem to know anything about Sprint. I had this problem a long time ago with a Sprint Samsung Galaxy Note 2 phone, where even with the official CyanogenMod ROM, it had no working Sprint carrier settings in the ROM. From the Note 2 I moved on to a Nexus 6 (unlocked) and didn't have these issues, but the 3rd-party ROM support for the Nexus 6 was vastly superior to what is for the G5S Plus. I get all excited every time a new ROM is released (especially an "official" one), but then I know not to even try it after just reading the initial post and seeing that they used the exact same base that all the other devs used. I've posted the issue on several ROM threads now, but it's typically just ignored (I don't think they know how to solve it). I'm actually considering buying a 32GB version of this phone (maybe a refurbished one) and giving it to a better known dev team (like Dirty Unicorns, PureNexus, etc.) so they can put out a more stable, quality ROM for us, but I'm also just thinking about moving on to a different phone instead. I'm not getting off Sprint since they're the only carrier that has unlimited everything still. Sprint isn't the problem anyway -- it's who is developing most (all) of our ROMs. Even if Moto finally releases an Oreo update for this phone, it will most likely be 32-bit, and then we'll have to get our phones back to stock unrooted, which is not only a pain in the posterior, but doesn't always work.

always6s said:
I shall try and see
Click to expand...
Click to collapse
No use this ****

internetpilot said:
Sorry, just saw this. I'm the Sprint user Phazmos mentioned. The problem is whatever source, base, proprietary blobs, etc., that the developers on here all seem to be using for the 3rd-party ROMs doesn't seem to know anything about Sprint. I had this problem a long time ago with a Sprint Samsung Galaxy Note 2 phone, where even with the official CyanogenMod ROM, it had no working Sprint carrier settings in the ROM. From the Note 2 I moved on to a Nexus 6 (unlocked) and didn't have these issues, but the 3rd-party ROM support for the Nexus 6 was vastly superior to what is for the G5S Plus. I get all excited every time a new ROM is released (especially an "official" one), but then I know not to even try it after just reading the initial post and seeing that they used the exact same base that all the other devs used. I've posted the issue on several ROM threads now, but it's typically just ignored (I don't think they know how to solve it). I'm actually considering buying a 32GB version of this phone (maybe a refurbished one) and giving it to a better known dev team (like Dirty Unicorns, PureNexus, etc.) so they can put out a more stable, quality ROM for us, but I'm also just thinking about moving on to a different phone instead. I'm not getting off Sprint since they're the only carrier that has unlimited everything still. Sprint isn't the problem anyway -- it's who is developing most (all) of our ROMs. Even if Moto finally releases an Oreo update for this phone, it will most likely be 32-bit, and then we'll have to get our phones back to stock unrooted, which is not only a pain in the posterior, but doesn't always work.
Click to expand...
Click to collapse
I feel ur pain brother. I can't drop Sprint for the same reasons and it seems like it's always something. I do appreciate the info on why they aren't working. It seems like there would be more devs on Sprint tho just cause of the unlimited data. Idk. I habe since moved onto using the moto z2 force. Same problems are occurring with it. I am running a DU rom that I'm downloading the update to now and hopefully it will have working 4g. I wasn't even really aware of the DU team or any others that weren't on xda till recently. I wish there was a good spot like xda that had all of them.

Rooting the Moto E4 Plus (Boost Mobile)

I have a moto E4 Plus that I bought from my carrier Boost Mobile and I was wondering, once my warranty is up and over with I was going to root it and get the full experience of android but I don't know if I can do that for my phone.
My phones model is: Moto E4 Plus (I couldn't find anything in settings about it other than this)
Bought from Boost Mobile
Has 2GB of RAM, Storage or (ROM) is 16 GB, Display is 1280x720 HD, Version is PVTB, SKU XT1776, Camera is Back 13 MP & Front is 5 MP.
Build Number: NCRS26.58-44-6
Security Patch Level: March 1,2018 (I actually just updated it to this)
Android Version is 7.1.1
Thats all but I want to do this with root
1. Have TWRP or ClockworkMod (prefer TWRP)
2. Have a custom ROM LineageOS or Cyanogen Mod
3. Have access to root apps

Absolutely! I'm running one as well..
Sent from my Moto E (4) Plus using Tapatalk

I've done it three times. I suggest you get your unlock code from Motorolla now. You don't have to unlock your phone yet if you are concerned about the warranty. However, it might be a good idea to get it now in case Boost decides to make their prepaid phones ineligible to be unlocked. I believe Verizon prepaid Moto E4 Plus phones cannot receive the unlock code.
Follow this guide here. It's pretty easy. Only wrinkle was wiping the phone after first booting with TWRP. You need to reboot back into TWRP a second time in order to successfully wipe.

Doesn't getting your unlock code from Motorola void your warranty if you use it or not?

As @imneveral0ne mentioned, getting your unlock code voids warranty. I'd hold off until your ready

That warning is toothless. It's illegal for a company to void your warranty due to the 1975 Magnuson-Moss Warranty Act. They cannot force you to waive your rights if you modify your device if it's over $15. This has come up before and the response from Motorolla is basically this:
Unlocking the bootloader will show your warranty as void.
However, if an unrelated physical material failure should occur, such as a bad volume rocker or a failed speaker, it will be covered if the phone shows no signs of physical abuse. The key is that the problem can't be traced to software or abuse.
These same principles apply to Extended Warranty.
Click to expand...
Click to collapse
If the phone is damaged due to you unlocking it, you're screwed. If the issue is unrelated to the phone being unlocked, then they will honor the warranty. That's what the law says basically.

Sizzlechest said:
That warning is toothless. It's illegal for a company to void your warranty due to the 1975 Magnuson-Moss Warranty Act. They cannot force you to waive your rights if you modify your device if it's over $15. This has come up before and the response from Motorola is basically this:
If the phone is damaged due to you unlocking it, you're screwed. If the issue is unrelated to the phone being unlocked, then they will honor the warranty. That's what the law says basically.
Click to expand...
Click to collapse
What I got from that was that Motorola will be happy to help with a hardware issue (like pwr & vols) but that anything related to software is all on us. So if you don't like the way something works, flash another ROM or go "Completely Back to Stock)

bcrichster said:
What I got from that was that Motorola will be happy to help with a hardware issue (like pwr & vols) but that anything related to software is all on us. So if you don't like the way something works, flash another ROM or go "Completely Back to Stock)
Click to expand...
Click to collapse
Yes. Also, if your mobile carrier or Google decides to ban your phone because it's unlocked, don't come crying to Motorola.

Sizzlechest said:
Yes. Also, if your mobile carrier or Google decides to ban your phone because it's unlocked, don't come crying to Motorola.
Click to expand...
Click to collapse
Meh..
1. - Not stressing Google, I'm working on an F-Droid build anyways. Heck, PAOSP has F-Droid (I think).
2. - This was just a $70 phone, I'll get something else if I have to. But I prefer Root and Custom ROMs to stock almost any day.
Sent from my Moto E (4) Plus using Tapatalk

Don't get me wrong. None of those things will happen. It's just Motorola covering their asses with legalese.

is there a bloteware list for the e4plus i want to earease all i can!

sinr764 said:
is there a bloteware list for the e4plus i want to earease all i can!
Click to expand...
Click to collapse
All the bloatware is in the oem partition. You can't access it through the OS without having the partition mounted r/w which you have to modify the fstab.qcom in the kernel to do. To do that, tou need to unpack, modify and repack the kernel. Only other way is to do it through the file manager in TWRP. I can give you a debloated oem.img you can flash if I knew what firmware version your phone is running.

xt1900-1 root privileges

I have a Moto G X4 xt1900-1 Amazon variant. Motorola gave me the key to unlock the bootloader and I've been able to achieve root access (for the most part), but only after rolling back to 7.1.1 and using a modified boot.img. There's still a few things I can't do because despite all efforts the system and vendor partitions remain encrypted and for some operations can't be accessed or mounted.
From what I've read, the Amazon variant is particularly tenacious at keeping those partitions encrypted, thus denying access at the deepest levels. But even in this forum I'm getting conflicting information. One person says the bootloader cant be unlocked (I had no problem there). Another who bought one directly from Amazon says twenty minutes after returning home the bootloader was unlocked and it was rooted. Most of what I've read, however, says root level is not achievable with the Amazon variant.
My Question - Is this behavior limited only to the Amazon variant of this unit?
I need to find out because I really like this phone and am thinking of getting a different variant. I can't afford a new one so I'm going with used. I've seen Android One and Verizon variants that claim to be unlocked (for the purpose of using them with any carrier), but of course there is no information relating to root level privileges.
If I may request, please don't ask me questions about the methods I used, for I have no further inclination or intention of trying any more. I would just like to get a variant that is known to be rootable - if there is such a thing. I do understand that Magisk, TWRP, the Xposed platform, and the like are still playing catchup with Oreo and Pie, but I believe they will eventually get it and am willing to wait.
Thank you

I think the android one and retail versions have unlockable bootloaders. See the FAQ thread by Neffy27.
It's odd that the system and vendor partition are encrypted, and that your can't see them with root access. Maybe I'm misunderstanding what you mean.

If you have unlocked your bootloader, you likely don't have the Amazon variant (even though it may have been purchased through Amazon). Android One and Retail firmwares are interchangable - you don't even need to unlock bootloader to switch. I personally have the Android One branded phone, but have stock Retail firmware on it currently.
https://forum.xda-developers.com/moto-x4/help/moto-x4-f-q-s-thread-t3814393

Drive is encrypted
Well, I watched the video. The way he installs TWRP is exactly how I've tried it a dozen or more times already. But after it's installed, and I boot into TWRP recovery, and then select to install something (anything), the contents which show up on the SD card are encrypted - about 14 folders with long randum characters, and when I open any of them, they're empty. It just seems like the SD card has been encrypted. Is it possible it had been previously encrypted? And if so (probably when hell freezes over) how can it be unencrypted without the key? I've used TWRP before to partition sd cards, so I know how to do that. Maybe I should split the card into 2 partitions, then wipe that out and take it back to 1 partition. If it is encrypted, that should surely destroy any encryption currently present.
I forgot to mention that when using TWRP from an image on my PC, the SDcard isn't encrypted. But, installations from there mostly fail or send the thing into boot loops or a frozen start up screen.