yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Q&A, Help & Troubleshooting] ambig88:
So I flashed the factory images back onto my phone and I got data back. I guess there is a strange bug in the latest nightly of CM13. Of course, I haven't been able to go to an area where I have poor reception. Now I have to find a ROM that offers the LiveDisplay feature CM13 offered. :( I like my screen to be a bit colder than what Huawei calibrates their displays to.
[Nexus 6P Q&A, Help & Troubleshooting] fast69mopar:
I knew there was something in the CM13 based ROM's that was causing you to lose data. Also, If you use a custom kernel like Elemental or Elite you can control the screen colors and make it how you like it. Give Pure Nexus a try. It's a super nice ROM. The dev is awesome. He does great work. Maybe give Chroma a shot. Also, you could try Resurrection Remix. It's a CM based ROM but it may not give you the data issues. It's worth a try. Lemme know what works. Good job on getting the factory images flashed and getting data back too.
[Android Q&A, Help & Troubleshooting] karan555:
i have an intex aqua power plus(mt6582m) with custom rom "exception os"

by using this custom rom, gps only using mobile data to get my location in any service or app

i am having wifi active, and no mobile data, but this custom rom's gps forcely use data and eat my balance whenever i am turning on gps, i want to make it use only wifi.:confused:

:rolleyes:also having that same issue in my previous phone gionee ctrl v4s(mt6582) lollipop stock rom
[Android Q&A, Help & Troubleshooting] febry_valdy:
It's better to disable the cell data before activating the wifi, so the GPS won't eat ur cellular data.
[Android Q&A, Help & Troubleshooting] karan555:
data connection is always off, that gps forcely use it like a ghost
[Android Q&A, Help & Troubleshooting] karan555:
I researched myself and found out that placing that sim in sim slot 2 instead of slot 1, solved my issue????
[Sprint LG G4] momo254:
I got a G4 yesterday and got a working sim card and finally added to my sprint account and working. The minute I start to mess with the phone, I get hit with the bootloop. I've searched many threads and tried reflashing the ZVB tot file through LGup and lgflashtool and no success (download fail with lgflash and antirollback with lgup). I can get into recovery mode and wiping and factory resetting the phone doesn't do anything either. Can anyone please help? This is literally the 2nd G4 I've gotten in the last week due to the first one being tied to someone elses account. Go ebay..
[X 2014 Android Development] rtrotsky:
Even if I am on stock I have to flash boot*.img?
[X 2014 Android Development] glauberlima:
Since your device already has the untouched stock boot you don't need to flash anything. :)
[X 2014 Android Development] jbaumert:
I seem to be having trouble installing the "Systemless Xposed". It errors out with - ! Failed: Unable to extract zip file!

I have verified "systemless root - ver 2.76" and tried re-downloading the zip. Any thoughts?
[X 2014 Android Development] glauberlima:
Could you provide your recovery.log from TWRP so we can see the detailed logging information?

You can pull it from your device by running the following command in command prompt:

adb shell cat /tmp/recovery.log | clip

This will copy recovery.log contents to the clipboard. Paste it into notepad then save and attach here.
[X 2014 Android Development] glauberlima:
Hi [MENTION=4831054]vpxf[/MENTION]

The unmodified boot.img is a requirement for SuperSU as it tries to patch the boot image on-the-fly during the install process (by the time you flash it using TWRP). If the image is not in its original state, SuperSU will fail to install in systemless mode.

Regarding your question about custom ROMs compatibility I don't know if the SafetyNet checking will pass/fail. That's a good test to perform. :)
[X 2014 Android Development] jbaumert:
I've attached the log. I did notice "unzip: zip flags 1 and 8 are not supported".

NOTE: I was able to flash the 85.7 version found in the second post of the "Systemless Xposed" thread. The newest 86.2 is the one giving me troubles.
[X 2014 Android Development] bertolehm:
As glauberlima found out in the other thread, you need to re-zip the xposed installer with 7-zip (that's what i used at least) and the install will work.
[X 2014 Android Development] glauberlima:
As stated by [MENTION=4910885]bertolehm[/MENTION] I've discussed in the other posts the exactly same issue with the zip installer you have reported [MENTION=4681892]jbaumert[/MENTION]. Take a look at them:

http://xdaforums.com/showpost.php?p=67792193&postcount=1193

http://xdaforums.com/showpost.php?p=67805517&postcount=1233

Regarding your device being systemless rooted check with SafetyNet Helper Sample app. If everything turns green you are good :)
[X 2014 Android Development] glauberlima:
** Duplicated **
[X 2014 Android Development] oyoyl:
Thanks for the tutorial.

The first boot fails, ok ; but how long is the second boot ?

I wait a long time (around 15 minutes) blocked at the first screent (static moto logo) and I stop it, reboot and reinstall my backup. I panic a little
[X 2014 Android Development] glauberlima:
Which variant is your X?
[X 2014 Android Development] oyoyl:
XT1092
[X 2014 Android Development] glauberlima:
15 minutes... That's definitely too much.

I'm about to update this guide with my new findings so If you don't mind I'd like to suggest you this:

Repeat the steps but this time skip the update to latest version. After the reboot access SuperSU. It should display a message regarding your su needs update. Accept it.

Make sure your nandroid backup is up to date.
[X 2014 Android Development] oyoyl:
Same thing, but it's possible that my boot image is not up to date and I have no other boot backup to test.

I have only a complete backup (boot + system without root), perahps I'll try later with complete restore ...

Thanks
[X 2014 Android Development] guilhermoaraujo:
Something went wrong, the root works fine, but when I run the SafetyNet test, I got "CTS profile match: false", I just want to keep the OTA upgrades working, if I did something wrong, is there any way to unroot and do the systemless root again?? Thankss
[X 2014 Android Development] davidurc02:
Hi! Hey, I followed the steps and my MotoX got stuck when rebooting after flashing. I'm trying to enter fastboot with power+Volume down but no luck so far, any idea? I hope you can help me!
[X 2014 Android Development] glauberlima:
OK. Just leave a reply by the time you have the result of your test. :D
[X 2014 Android Development] glauberlima:
One of your installed apps modified system partition. Did you test on a completly stock image?
[X 2014 Android Development] glauberlima:
Is your variant XT1097?

Sometimes it's hard to enter bootloader mode. Here's what I do when this situation happens to me:

Press and hold the famous combination (VL D + POWER), count to 5 then release.
[X 2014 Android Development] gmlaw:
Thanks for posting these instructions.

For anyone who does not wish to install TWRP, you can still use this method. Just download a TWRP image for your device, and start it one-time-only by putting your phone into bootloader mode and running

fastboot boot <path-to-img-file>

from your computer. After that, continue following OP's instructions.
[X 2014 Android Development] davidurc02:
Update on my case

Hello again,

Thanks for your quick reply, I was able to enter fastboot when in bootloop using the usual combination. The only detail is that the phone would always reboot when I held the keys for 5 secs, so I held them down for about 20 secs (during turn off, reboot, etc) and I got the fasboot menu.

Yes, my variant is MOTO XT1097, Vitara.

The only things I had modified before this guide were unlocking my bootloader and installing TWRP.

I flashed both versions 2.67 and 2.76 just like the instructions said but I got stuck in a bootloop. I restored my phone last night using the backup I created using TWRP. Today I retried rooting my phone but only using the 2.67 version and I got the bootloop again.

The only step I didn’t follow was running these commands because I honestly don’t know where to run them. I can run the others in cmd when I’m in “\platform-tools”

adb shell "echo SYSTEMLESS=true>/data/.supersu"

adb shell "echo BINDSYSTEMXBIN=false>>/data/.supersu"

I’d appreciate any help or ideas you have.

Thank you very much!
[X 2014 Android Development] oyoyl:
I had some troubles :

- I restored an old boot + an old system backup => my phone swith off during animation

- I restored my current boot + my current system backup => my phone swith off during animation too !

- I restored a factory system => my phone is blocked on first moto logo !

- I panic ...

- I wiped all data, and restore my latest system image => my phone is ok ! ouf

So I tried to root systemless :

- I checked SafetyNet before : passed

- I followed your instructions => Everything seemed ok (first boot failed but the second was ok) but SafetyNet gives "CTS profile match: false".

However when I launch TitaniumBackup, I have a warning popup which confirmed that SuperSu is mount on an other partition
[X 2014 Android Development] glauberlima:
You have to type those commands in Command Prompt with your device connected to your computer. Make sure the option USB debugging is turned on otherwise the commands won't work.

If you don't enter the commands SuperSU will install into system partition and fail as it requires a prepatched boot img.

TL;DR Type the commands if you want to succeed :good:
[X 2014 Android Development] glauberlima:
I'm wondering if Google has updated something at their side that now makes the check fail.

I will perform a factory reset in my device to check if it's really happening.
[X 2014 Android Development] jbaumert:
[MENTION=4943126]glauberlima[/MENTION] - Have you tried Magisk Universal systemless interface yet? Myself and another Moto X 2014 user tried and it resulted with the phone booting directly to the bootloader with an error. (A reflash of the stock boot.img restored function). Just curious if you had any luck with it?
[X 2014 Android Development] glauberlima:
Hi [MENTION=4681892]jbaumert[/MENTION] I haven't tried it yet.

What error message is being displayed?
[X 2014 Android Development] jbaumert:
"Fastboot Reason: Fall-through from normal boot mode"

The flash seems to work fine, but when rebooting it goes directly to the bootloader (no boot logo displayed).
[X 2014 Android Development] glauberlima:
Based on my own experience this indicates that boot.img has been modified and won't be able to proceed to normal startup. Then system fallbacks to bootloader.

Perhaps Magisk's author [MENTION=4470081]topjohnwu[/MENTION] can shed some light on this issue. Meanwhile I will install it here as well. :)
[X 2014 Android Development] davidurc02:
Solution to my problem

Hello everyone,

Thank you for your help! I was able to root my phone a couple of days after I last posted. Sorry to take this long to answer back.

My phone was in bootloop and I had to install the factory image but I couldn't do it with the one I got from this post by that time, I can see you already updated that factory boot image, so I believe that one works now. Anyway, I used the one I got from the following thread:

http://xdaforums.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105

Image: "new-root-boot-6.0-xt1097.zip"

I followed the steps you gave us here again and it worked correctly, but I only installed SuperSU v2.67.

Pd: One of my problems was that I couldn't enter fastboot menu when my phone was in a boot loop, but I solved it by pressing power+Vol down for about 20 seconds (Maybe I exaggerated, but it worked).

Pd: SuperSU App asks me to update the SuperSU binary, should I do it? Is it necessary?

Thank you all again for this post and for answering our questions!
[X 2014 Android Development] oyoyl:
Anyone have the latest sotck boot img for xt1092 ?

Thanks
[X 2014 Android Development] oyoyl:
Ok I found the full image on this great site :

https://firmware.center/firmware/Motorola/Moto X (2nd gen-2014)/Stock/XT1092/

I join the boot img, tested, it works perfectly.
[X 2014 Android Development] glauberlima:
Sorry for the delayed reply.

You can update it. Even more it's highly recommended to do it.

Once you have flashed the zip new-root-boot-6.0-xt1097.zip from Junior's thread I have to say you performed a system root not a systemless. :)
[X 2014 Android Development] Red_81:
Does the Software Status on the bootloader screen stay Official or does it show modified?
[X 2014 Android Development] Teh_Chuz:
All this truble just to play pokemon go... haha. I'll try it after. Rigth now i don't have a OTG cable, so i can't make backups. Thank you very much.

I still don't really understand how it works and what "systemless" means. Im just a "flasher" user :C
[X 2014 Android Development] Red_81:
Bad news.... Pokemon Go detects system-less root.
[X 2014 Android Development] theoblackhawk:
So, as other users pointed out the SafetyNet helper app is giving me an error message as well and I had everything stock and clean before root my phone

That been said I think that Google updated something on their side that now identify the systemless root mode too :(
[X 2014 Android Development] Nixoman:
XT1092

Hey guys i need help. Recently bought this xt1092 variant, and has been updated to 6.0 already. Now, thing is i cant unlock bootloader, it says on Moto site that my device is not supported. But i think this variant is Pure edition.

Anyway, can i use this method if my bootloader is locked?

If i cant, how to unlock it? (iv searched 1000 of threads and forums, no luck)
[X 2014 Android Development] Red_81:
Suhide by chainfire is working to hide root from pokemon go. Make sure to follow the instructions and use the newest version of twrp or flashfire.

http://xdaforums.com/apps/supersu/suhide-t3450396/page74
[X 2014 Android Development] theoblackhawk:
Do you know if it's working with regular Xposed (not the systemless one) installed too? Couldn't find that particular information in the thread...
[X 2014 Android Development] Cokol:
Tested and working on XT1097 (unlocked bootloader)

- Reverted to Full Stock Rom

- Flash TWRP

- Boot once

- Reboot to recovery

- Format Data partition

- Flash systemless enabler zip, then supersu 2.67, then supersu 2.78SR1, then xposed systemless 86.2, then suhide 0.53

- Profit (Pokemon GO + Root + Xposed). SafetyNet Helper says it passes the test.

Hope this helps
[X 2014 Android Development] theoblackhawk:
Well, like I said I could not find any information about suhide + Pokemon GO working with regular Xposed (not systemless one) and for now I don't have the time to flash stock ROM and go through the whole process again, so I think I will stay without playing a bit more :/

But thanks anyway :)
[X 2014 Android Development] mastarifla:
I thought suhide was supposed to be before installing supersu? :/

Edit: Nevermind, this semi-changed with the latest revision, they still want you to uninstall the older version of suhide if you have it installed though...

Also as a heads up, you are probably better off first restoring your stock boot.img, don't be like me who just tried running the SU and Xposed uninstallers, that doesn't seem to work...
[X 2014 Android Development] danielcepa:
Does this method work with the latest may update for xt1092? :confused:

Screenshot attached, there is a new kernel build.

Edit:

It works great !

used fastboot boot twrp-2.8.7.1-victara.img to keep the original recovery installed

disabled the modification of system files, from the twrp bootup screen

installed enabler, supersu 2.67, supersu 2.78, adaway systemless - all works

thanks a lot !
[X 2014 Android Development] dylantep:
I followed all the steps but when I flash xposed systemless 86.2 I get an error that says unable to extract zip file! Also safetynet test shows cts profile match: false. Any ideas what could cause this? Thanks for any help
[X 2014 Android Development] mastarifla:
When you open up the Adaway app does it actually fully load?

I had issues with SuperSU 2.78, it wouldn't show anything when I opened the app, I had to go back down to 2.76 in order to open/use Adaway :/
[X 2014 Android Development] danielcepa:
Works. Its the latest version from june 26.
[X 2014 Android Development] joao2c:
One question :flash the boot.img in a custom rom works? Do the process in a custom rom only with flash this boot.img. Anyone try this?

Enviado de meu XT1095 usando Tapatalk
[X 2014 Android Development] FiliBrushedRed:
Could you suggest a way to backup my system xposed modules/settings? I wouldn't like to start all over :(
[X 2014 Android Development] anubus45:
Tangentially related here. I spent the better part of yesterday trying to use these methods and those listed in this thread to try to achieve systemless root with CM13. From what I was able to gather, it looks like the only reason SuperSU is unable to patch it is that the boot partition that comes with the current CM nightlies is compressed using LZMA instead of GZIP, and as such, when trying to install SuperSU in systemless mode, it fails when it tries to unpack the ramdisk and aborts the operations. I believe that repacking the boot.img in a GZIP format should allow SuperSU to patch it correctly (the drop-in replacements I tried allowed it to patch, but the boot images weren't meant for CM, so they failed to boot). My own attempts to repack it were unsuccessful, though I have very little experience in actually building/recompiling, so I'm wondering if anyone else has dev skills to try properly repacking the boot image from one of the CM13 Nightlies using GZIP instead of LZMA?
[X 2014 Android Development] glauberlima:
Main post updated!

As of SuperSU-v2.78-SR3 boot image patching works as expected. There's no need to manually patch boot image nor install an older SuperSU before install the latest one. Just install the latest one and that's it!

Thanks to [MENTION=631273]Chainfire[/MENTION]!
[X 2014 Android Development] glauberlima:
I've updated the post. Give it a try and let me know if it works.
[X 2014 Android Development] jbaumert:
Maybe this method could be applied to Magisk, so it could work on Moto devices?
[X 2014 Android Development] glauberlima:
I am checking with Magisk's dev. :)
[X 2014 Android Development] jbaumert:
Tried the 2.78-SR3 SU and it failed to patch the boot.img on my XT1093 (running MM rom based off the XT1095 ver).
[X 2014 Android Development] demonshouter:
i have a xt1096 running 1095 august patch, unrooted and unmodified stock, tried this method and get stuck at boot logo. any idea? thanks

edit: succeed after flash systemless root enabler..thank you so much
[X 2014 Android Development] glauberlima:
Did you revert to stock untouched boot image before installing SuperSU 2.78 SR3?

What about my zipped "systemless enabler", did you flashed it before SuperSU too?
[X 2014 Android Development] jbaumert:
Yep, restored stock boot image and used enabler. I wonder if there is some difference between the XT1095 and the XT1097 boot images that would prevent it from working?
[X 2014 Android Development] glauberlima:
Repeat the process but this time do not reboot. As soon as the SuperSU flashing operation finishes keep your phone connected to computer and extract the TWRP log by running this command at Command Prompt:

adb shell cat /cache/recovery/log | clip

This will copy log contents to clipboard. Save it and attach here.

If you don't have ADB installed I recommend this one: http://xdaforums.com/showthread.php?t=2317790
[X 2014 Android Development] jbaumert:
So, I did manage to get systemless root when I tried it the second time. Not sure what I did wrong originally. I also tried systemless xposed (86.2), but after flashing I kept getting an error that xposed was installed, but my active. Honestly, standard root and xposed works fine for me, I just like to "experiment".
[X 2014 Android Development] glauberlima:
I use the same config: systemless SuperSU + regular Xposed Framework.

There's no stable systemless Xposed framework available yet.

Good to hear it worked for you. (y)
[X 2014 Android Development] jbaumert:
I have to ask though. Why use a systemless SuperSU if you end up writing to system with the standard Xposed?
[X 2014 Android Development] glauberlima:
Because Xposed is something optional and there's still hope for a systemless version :)
[X 2014 Android Development] thewailer:
My phone is full stock, can unlock BL, install patch, then systemless root+xposed+adaway and after all relock BL? Not gonna install twrp just boot the image also not gonna change anything in /system
[X 2014 Android Development] ordnas888:
xt 1092 august 2016

So if I understand right ... with xt1092 with patch August simply from gapps twrp the two files ... without giving more shell commands? xt1092 stock bootloader locked. else but with twrp can do backup only system and boot?? Thank you
[X 2014 Android Development] Charlita:
Hi [MENTION=4943126]glauberlima[/MENTION], hi everyone! I'm a pretty new Moto X 2nd Gen user, just have it for the last few days, so I apologize if I say anything very basic, but I guess this is the best moment for me to express my doubts and impressions: when you know already a lot about your device, like you all, it's pretty easy to oversee what's still important for beginners.

I've ended up coming to this thread after checking first the root procedure from Júnior, the first one on Google results. Previous owner never updated the phone, so it started to ask me for updates on Android, 3 at total, if I remember it well. Let the phone do them all while I was reading, but as the last one was August's update, got a bit worried, I've searched a bit more and found this important and valuable thread.

So I went for this. It seemed (and it is!) pretty easy, my untouched and reset phone was a candidate.

And then I got confused. In my previous experience, TWRP, CM must always be flashed... then I've learnt in TWRP's site and other threads that I could just fastboot boot (although it just gave me errors). Neither here nor on TWRP's install guide there's any mention of expected errors. I wasn't able to fastboot boot or fastboot flash recovery.

I've searched a lot (I guess) before presuming I should unlock my bootloader (still not sure if I should have done it, as you mentioned the need for an "original untouched stock state"). So, my first question and suggestion: is one always supposed to unlock the bootloader to follow the procedures here, if it shows Device: Locked? If you could slightly add something about it, I guess it'd be pretty valuable for newcomers.

Anyway, I've unlocked the bootloader, still couldn't fastboot boot, but this time was able to fastboot flash recovery. As the bootloader unlock resets the phone, I've made a Nandroid anyway (in case I could brick it), but that obviously only contained the phone's original state. I presume that only phones previously with TWRP installed can benefit from this?

Never got this or any other icon in my app drawer. Don't know if it's a version thing, didn't find any configuration, but hope it's just a visual glitch. Maybe it could be worthy to add that it might not happen?

And it worked! Installed Titanium Backup (my main daily reason for being rooted) and all okay! Although it keeps me bugging about not having USB debugging on, when in fact it is.

It didn't, but I got the blue screen result. Not really sure if that's bad or not.

Anyway, my phone is rooted and working beautifully. Instead of Moto logo, obviously I have now the unlocked bootloader warning, which doesn't bother me at all. It was just some fearful decision as I didn't know if I was about to lose my "original untouched" status. Great thread and super easy way to get rooted! Again, thanks [MENTION=4943126]glauberlima[/MENTION]!
[X 2014 Android Development] glauberlima:
This could produce undesirable results since the unlocked bootloader is a requirement for rooted phones. But to tell you the truth I cannot predict the results of this "experiment". :)

Anything wrong in keeping your phone's bootloader unlocked? I'm just curious...