yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] KefkaticFanatic:
Have a sort... of bug report? Maybe it's not the fault of this, but I figured I'll post about it somewhere.

Installed systemless root, worked great. Installed xposed, worked great. Snapchat is obnoxious and doesn't let you log in if you have xposed installed, ok no problem. I ran the xposed uninstaller script.

After running xposed uninstaller, xposed was uninstalled. I was able to log in to snapchat, great. I then go back and reinstall xposed, and everything seems ok.. and then I realized SuperSU is missing, with nothing able to get root. I try redoing the systemless root install, supersu install, and finally the xposed install in that order, like I had previously, however, no matter what I try, I cannot seem to revive SuperSU. The strange this is that Titanium Backup appears to still work just fine, and Xposed Modules still seem to work ok. When I run some app that had not been granted superuser before however, i.e. Rashr, it will sit forever trying to gain root until timing out.

I'm just going to go ahead and nuke everything and start again and I'm sure it'll work fine, this time doing my pre-xposed stuff BEFORE I install it in the first place, but it seems like some odd issue and I dont know if it's the fault of the xposed uninstall script or some strange artifact of this systemless root install.
[X Style (Pure) Android Development] samwathegreat:
SuperSU no longer requires any "systemless root install" -- I'm guessing you mean flashing the modified boot image?

You don't have to do this anymore. Restore (flash) the original boot image, then flash the supersu from the beta thread here:

http://xdaforums.com/showpost.php?p=64161125&postcount=3

It will automatically modify the boot image for systemless.

It sounds like you are trying to install an old version of SuperSU along with your modified boot image...
[X Style (Pure) Android Development] DroidForLife33:
So with the new Supersu zip Android pay will work?
[X Style (Pure) Android Development] samwathegreat:
AFAIK, no. But once xposed is installed, AP won't work. Just a matter of time before Google patches safetynet to detect systemless root anyways.
[X Style (Pure) Android Development] DroidForLife33:
Okay. I'm me to the mxp. I've had lg g3 ,note 3 and other phones. Just want to make sure i know the proper steps before I root.
[X Style (Pure) Android Development] KefkaticFanatic:
That would have been an easy solution, but unfortunately not.

I ""installed"" or however you want to call it systemless root via the OP of this thread, with the kernel patch + supersu zips in sequence. The error occurred as I mentioned, and then I tried reflashing both zips again. I haven't tried anything more recent than the 2.56 in the OP, so perhaps I can try that, but just redoing a full install makes root work again .-.
[X Style (Pure) Android Development] DroidForLife33:
Did you have any luck getting it to work? And if so which su did you install? I'm reading the threads trying to figure out the best way before I my bootloader.
[X Style (Pure) Android Development] KefkaticFanatic:
So, it worked for me the first time just using the zips in this thread, and it did again the second time. What broke everything for me is when I ran the xposed UNINSTALL script. After that, I had to do the whole revert-to-stock over again and start from scratch. Perhaps I could have just flashed the stock marshmallow, but I figured I might as well nuke everything...

I haven't tried any of the newer supersu builds that that other thread had. I can confirm that my current build, which is coming from stock LP (via the return-to-stock package in another thread), OTA to stock MM, then rooting, works perfectly with the two zips in the OP.
[X Style (Pure) Android Development] DroidForLife33:
Thanks for your hard work on this.
[X Style (Pure) Android Development] DroidForLife33:
Could you shoot me a link for the multiwindow mod?
[X Style (Pure) Android Development] real_milux:
Hello everybody, and thanks alnikki25k for this early patches.

Unfortunately, I found this thread a bit late, and therefore assume that I'm maybe better off with the new automated SuperSU 2.6x, right?

However, the following thread confused me a bit, because a lot of people seem to have WiFi problems after rooting:

http://xdaforums.com/moto-x-style/general/root-moto-x-style-xt1572-br-marshmallow-t3259380

Did anybody here experience something like this?

Has anybody here rooted a unbranded XT1572 EU-Version using the 2.6x SuperSU, and can confirm the (non)existence of the WiFi problems?

Best regards and thanks in advance!
[X Style (Pure) Android Development] dlarge:
No problems for me. Wifi is working as before.
[X Style (Pure) Android Development] EVR_PR:
Has anyone tried Beta_SuperSU v2.65 and had no problems? I'm currently on v2.62.3 and it's been working flawlessly so far, so don't want to risk it if its bringing problems. TIA.
[X Style (Pure) Android Development] real_milux:
OK, that's nice. :)

Can you please tell me the exact model and SuperSU version that has been used?
[X Style (Pure) Android Development] dlarge:
Xt1572 eu, unbranded. BETA-SuperSU-v2.62-3-20151211162651.
[X Style (Pure) Android Development] eejayyeahuuh:
In TWRP we are to keep the device read only, correct?
[X Style (Pure) Android Development] dlarge:
Yes, at least that's what I did.
[X Style (Pure) Android Development] NOSTALGIA:
sorry for the delay

added to index

[INDEX] Moto X Pure Resources Compilation Roll-Up
[X Style (Pure) Android Development] real_milux:
Don't do it! In general, I advise everybody not to try any SuperSU > 2.62.3!

I tried out the new 2.66 yesterday, it detected the ROM as capable for "system method", modified the system, and afterwards the XT1572 didn't start anymore.

I had to recover the NANDroid system backup and patch the boot with 2.62.3, that one worked like a charm.
[X Style (Pure) Android Development] meisen84:
Anyone else experience problems with apps randomly asking for permissions even after you've already set them? I only have this problem with MM when I root via this method. Is it a known issue?
[X Style (Pure) Android Development] real_milux:
What exactly do you mean with "permissions"?

Is your question specifically about the su permission, or do you mean something else? Which apps are affected? Examples?

In case of the former, no, I can't confirm these issues.

However, some apps had problems to gain root access after the first boot. I solved this by rebooting my device one more time, then it was gone.
[X Style (Pure) Android Development] meisen84:
By " permissions" I mean the new "access" prompts MM has. For example, every time I launch the stock camera app it asks to access storage. Or Chrome asks to "update permissions" to download a file every time I try. This only happens after I root with this method.
[X Style (Pure) Android Development] livewiremaxx:
So I have had a terrible time with this, And Im not to knew at this even though its been a while since I have done rooting.

1. I unlocked bootloader, that went ok.

2. Installed TWRP, Worked great

3. Made a backup, worked great (thank god)

Now Here is where its gotten sticky and I have done this over and over different ways and no luck.

1. Did the OP method using systemless_root.zip and SuperSU v2.56

- Root wasnt done, SupeSU wants to update binary etc... before it will finish installing. Wont do it in Play, if trying via TWRP it just puts TWRP into a reboot loop and nothing.

2. So I run backup restore and try again, but this time using the newer SuperSU that people taled about being SuperSU-v2.62-3-2015121116265

- Problem with this now is the phone just will not restart, It gets into the Moto logo and just sits there.

3. So then I redo it again, restore from back up and try with a different version of SuperSU and just same results.

Oddly the only combo that let my phone restart was using systemless, and then the 2.56 but I cant get root that way.

Right now I am putting a stock 6.0 onto the phone, even though I had started pretty much from scratch after bootloader was unlocked and then trying these steps again.

Anything anyone can suggest?

Thanks

Update: YThat is what it took - a stock build and not a back up build and then 2.62. Got it in there and working now finally. Was a bit more work than I had hoped for.

Thanks everyone for the great work on this thread.
[X Style (Pure) Android Development] dmb219:
I've had those issues too with a fresh install. I've found that v2.62 intalls ok. After 2.62 is installed, the latest 2.66 can be installed for whatever benefits that provides, not sure.
[X Style (Pure) Android Development] livewiremaxx:
Yep, you are right that is what it took - a stock build and not a back up build and then 2.62. Got it in there and working now finally. Was a bit more work than I had hoped for.

Thanks everyone for the great work on this thread.
[X Style (Pure) Android Development] real_milux:
No, I didn't experience anything like that. As nobody else answered, I guess that applies for most other people as well.

It sounds like the database for the new privileges is somehow corrupted or made read-only after root, very strange thing...

Have you tried the SuperSU 2.62.3 with unmodified stock boot and system?
[X Style (Pure) Android Development] meisen84:
I haven't. Do you know where there is an unmodified stock boot I can flash first without having to reflash the whole ROM? I have the 6.0 boot.img from the xt1575 firmware thread. I flashed it and didn't loose root as I thought I would. Maybe that want it? Thanks!
[X Style (Pure) Android Development] nibunnoichi:
With this system-less root method being in beta, I'm not sure I'm comfortable going through with this. Is there any progress on a normal root for the XT1575 on Marshmallow? Or is there a reason why "normal root" is not possible?

It took one week after the MXPE was released for regular root to be possible. Now it's 2 months after Marshmallow was pushed, and there's still no reliable non-beta rooting method? How can this be?
[X Style (Pure) Android Development] Tech_Savvy:
Forget what ppl say... Flash 2.66 amd be happy.. It works like its always worked the only difference is... If for some reason you flash a different kernel you have to flash it again after you flash the new kernel
[X Style (Pure) Android Development] JOSE89178:
How did you flash 2.66? And can you use TWRP with this?
[X Style (Pure) Android Development] Tech_Savvy:
download the zip from chainfires website and then flash it with twrp..
[X Style (Pure) Android Development] lafester:
We had a modified kernel the same day mm was released. No longer needed but still we have had regular root since day 1.
[X Style (Pure) Android Development] dmb219:
For me 2.62 works with an unrooted ROM. 2.66 gets stuck at the Moto screen & doesn't boot. While I'm typing I see 2.67 beta is up, haven't tried it. Anyway, if you have trouble, try 2.62.
[X Style (Pure) Android Development] dirtyhank:
Same here, 2.62 works perfectly on XT1572 (Stock MM) but any other later version (including 2.67) gets stuck at the M logo. No big deal though, since 2.62 seems to be working just fine.
[X Style (Pure) Android Development] fdc77:
read here, expecially "Notes on 2.64+"

http://xdaforums.com/showpost.php?p=64161125&postcount=3

autodetect feature is broken on our device, i have reported to chainfire and send to him a stock kernel copy but problem persist.
[X Style (Pure) Android Development] DroidForLife33:
Delete
[X Style (Pure) Android Development] franksoneplus:
So, if I'm on marshmellow , stock , and I simply flash the kernel patch and the systemless root, I should gain root access correct ? I'm looking to flash xposed , so if anyone can also help with pointing me in that direction, that would be great. BTW I have TWRP installed , and have backups of the clean system, so if anything goes wrong , a quick restore and I'm golden right ? Sorry for the noob questions, I just don't want to mess this up.

---------- Post added at 09:08 PM ---------- Previous post was at 08:20 PM ----------

Did you just get normal SuperSU , that version and flash via TWRP ? Did you flash any kernels or anything else ?
[X Style (Pure) Android Development] real_milux:
Hey franksoneplus,

As discussed numerous times, you don't need a separate kernel patch, as version 2.62 automatically patches the boot image for you.

I have a European XT1572, and did the following to root and install Xposed:

Flashed SuperSU-v2.62-3

Rebooted phone and waited until it was entirely started; checked root access. (I don't know how this can happen, but another user who failed to do this before Xposed flashing reported his phone to be soft-bricked...)

Rebooted to TWRP, installed xposed-v79-sdk23-arm64

I can say that everything runs perfectly smooth for me, however, be aware that you lose OTA when flashing Xposed, because it modifies the system partition!
[X Style (Pure) Android Development] psxmail:
Hi I am confused, I flashed Beta-superSU 2.62 as it was recommanded to get a root systemless without bootloop or every thing elses.

This evening I get a update of superSU to 2.65 via playstore and it asked me to update the binary. I aply it and reboot

And now every thing is working well !!
[X Style (Pure) Android Development] StreetkillnHD:
when flashing systemless root i get error dumping/splitting image failed aboring
[X Style (Pure) Android Development] real_milux:
Yes, same here.

I assume that the new version automatically detects the systemless root and renews the content of the boot partition with the new SuperSU binary.

I was also positively surprised that yesterday's update didn't soft-brick the system. ^^

---------- Post added at 10:38 AM ---------- Previous post was at 10:38 AM ----------

Custom kernel?
[X Style (Pure) Android Development] StreetkillnHD:
custom kernal like Frankenclark??
[X Style (Pure) Android Development] real_milux:
Precisely.

System-Root patches the kernel (boot partition) and seems to be incompatible with Frankenclark.

If Frankenclark does not enforce SELinux in strict mode, but uses permissive mode, you might not need systemless root.

In your case I would do a full NANDroid backup of all partitions (especially boot and system) and then try the most recent version of SuperSU (2.65 or higher), which performs a normal system-based root when supported. You can even try to enforce system partition rooting, read the SuperSU threads about how to set the configuration flags for that.

Edit: If this doesn't work, you should ask the makers of Frankenclark whether they can recommend you another rooting technique.
[X Style (Pure) Android Development] Note 3 Chicago:
I'm on systemless root with frankenclark...no problems here.
[X Style (Pure) Android Development] Senshi34:
This took me a few tries but I got everything working. I returned to stock with the tool posted in the roll up thread. For some reason my wi-fi wouldn't turn on. Flashed the modem to fix that and took the 6.0 update. Then my hotspot wouldn't work. Tried a few fixes but no luck since I couldn't get root to work. If I got wifi and hotspot to work I couldn't get root or TWRP to work and vice versa. Started over and eventually I got to 6.0 and the security update that came out a few days ago. Flashed TWRP, and also Beta SuperSU 2.62-3 (I know there are other versions but in the beginning of the thread, this had the most success). I tried Android Pay but it fails the security check, so now I'm going to install Xposed.

My issue was probably reading all the guides and grabbing all files and using them on the wrong guides. This guide worked for me, now I'm on systemless root, on Marshmallow with the latest security update. I'm using XT1575 on Verizon and tethering works with no modifications. I'm going to install some apps and make a backup using TWRP and make sure that the backup works (had an issue with "read-only" backup before).

Thanks everyone for the help.
[X Style (Pure) Android Development] psxmail:
Did you insytall Xposed on your systemless root ?
[X Style (Pure) Android Development] Senshi34:
Yes, I did. It was painless and issue free.
[X Style (Pure) Android Development] Fast_Zombie:
Hi everyone. Today I've decided to update my phone with that security patch, that came out couple of weeks ago. I've wiped my phone, installed MM factory image and updated with OTA zip. But when everything had been done, I wasn't able to root it in any way. Neither systemless script, nor up-to-date beta SuperSU zip won't work. Systemless script aborts at the very beginning with "Dumping/splitting image failed." error. I have my bootloader unlocked and the latest TWRP installed. Although, TWRP won't stick after reboot, every time I boot to bootloader, stock recovery replaces TWRP. What am I doing wrong and what possible steps I may attempt to install TWRP and root my device? My wild guess is that I should install TWRP and let it make /system changes possible. There was this option when I first installed it, but when I tried to install it again, there was no such option.

Everything worked fine before this update, I've used this exact thread to root my device.

UPD: I've managed to install TWRP with the option to make changes in /system partition. But systemless script still aborts with the same error.
[X Style (Pure) Android Development] Hitti2:
You have a few things going on.

1) Try 2.62-3 from http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344/post64161125#post64161125

2) Then flash with 3.67 from above.

And for twrp.

Don't reboot the phone normally, use the volume buttons to highlight recovery and press the power button to select it. This will stop the stock OS from patching it with the stock recovery in boot. Once you've booted into TWRP like this once, you can reboot normally.

http://xdaforums.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808

Pulled from above 2. How To Install A Custom Recovery On Your Device

Sent from XT1575, Stock 6.0 MM, Systemless root
[X Style (Pure) Android Development] Fast_Zombie:
Thank you! This method worked for me like a charm.
[X Style (Pure) Android Development] Hitti2:
If it wasn't for [MENTION=2614896]DaMadOne[/MENTION]

http://xdaforums.com/moto-x-style/g...ity-update-t3323126/post65542890#post65542890

He's the one to really thank. I'm just passing the knowledge.

Sent from XT1575, Stock 6.0 MM, Systemless root
[X Style (Pure) Android Development] GrandAdmiral:
So I have run into a problem getting into TWRP. I flashed it over with no problem and entered TWRP with no issue prior to rebooting the phone (even made a nandroid backup). I'm now trying to get back into TWRP so I can flash SU and I get an error that simply says "no command". Any idea what this could be?
[X Style (Pure) Android Development] Jay794:
Has this been tested on 6.0.1?
[X Style (Pure) Android Development] FunkeeC:
http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
[X Style (Pure) Android Development] gideon prabhu g:
I am using samsung grand prime.. can i hav a update on marshmallow update ??
[X Style (Pure) Android Development] rusticoar:
Verify Systemless root

When I first rooted my phone I attempted to go the systemless route. I had some trouble along the way and so I took some slightly different steps to root. At one point I switched from read only to read/write, though I never booted the system in read/write, to my recollection. So how do I verify that I haven't tripped anything and that I do truly have systemless root?
[X Style (Pure) Android Development] franksoneplus:
So I guess I rooted before the update as I had to flash a modified version of the stock ROM to root. It was just the easiest way.. Who needs OTA any way ?
[X Style (Pure) Android Development] TRRDroid:
This doesn't work on my XT1572 with Android 6.0.1. I used SuperSU 2.62 before and it still gives you root access on the latest update but causes multiple system apps to crash permanently and SIM card and Bluetooth doesn't work anymore.
[X Style (Pure) Android Development] Bracewar:
I have the same issue on a clean install. Just did RSD Lite and I have kernel 3.10.84-perf-g329ac5f.

Any suggestions?
[X Style (Pure) Android Development] Sherrillface:
Yes because of no command I cannot do jack with this phone and it's the whole reason I bought it what a waste I hate this been trying to get twrp for a month fudge
[X Style (Pure) Android Development] kunal kayal:
Sir can you please help me out to ROOT my MOTO X STYLE (XT1572) ( INDIAN VARIANT with dual sim support ) running MARSHMALLOW which is fully BOOTLOADER UNLOCKED ..i have tried every single version of SU ....when i tried to install it in my phone gets Brick(it stuck on big M logo while booting) each n every time i do this process .sir do you have a strong solution to this problem please help me out...﻿
[G4 Q&A, Help & Troubleshooting] Evnul000:
Does anyone have this problem? I go to settings then storage. When I press apps in storage my settings app crashes. Any help here?
[Nexus 6P Q&A, Help & Troubleshooting] Casimov:
Got the 6P, love the phone, but Im having an issue. Whenever Im in a call, and Im using a wired headset/headphones (mic and earphones), I can hear the microphone. Meaning, I can hear myself. If I tap the microphone, I can hear it too. And the thing is, its much louder than the sound of the person Im on the call with. It makes calls quite frustrating because I can hear the mic rubbing up against my shirt more than I can ever hear the other person. Whats going on here? Anyone else have this problem? Ive tried several different mics and its all the same issue. Is this a problem with the phone? I just bought it, should I return it?
[Nexus 6P Q&A, Help & Troubleshooting] keljai:
I don't have such issue but it was recently made aware that when using the speaker it causes "noises". Not sure if ota updates will fix it or not. If I were you and you are within the return policy, do it and order another one. Perhaps you got a lemon?
[Sony Xperia Z Ultra] Gr1ffo:
Hi all. I have been trying to install the [ROM][5.1.1_r26][OFFICIAL] Resurrection Remix® Lollipop v5.5.9 - Togari [11/20] Final.

I have to post the problem here as I don't post enough. ( trust me. I research the **** out of everything so I don't have to annoy developers ).

Anyway this is the log I get......

Installing '/external_sd/My Stuff/Resurrection-Remix-LP-v5.5.9-20151120-togari.zip'...

Checking for MD5 file...

Skipping MD5 check: no MD5 file found

I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts

I:Legacy property environment initialized.

script aborted: This package is for device: C6802,C6806,C6833,C6843,togari; this device is tianchi.

This package is for device: C6802,C6806,C6833,C6843,togari; this device is tianchi.

I:Legacy property environment disabled.

E:Error executing updater binary in zip '/external_sd/My Stuff/Resurrection-Remix-LP-v5.5.9-20151120-togari.zip'

Error flashing zip '/external_sd/My Stuff/Resurrection-Remix-LP-v5.5.9-20151120-togari.zip'

Updating partition details...

I:Data backup size is 0MB, free: 5683MB.

I:Unable to mount '/usb-otg'

I:Actual block device: '', current file system: 'auto'

...done

I know it's and was a standard C6833 as I use to be able to install roms before.

Anybody know of a way to change it back or have any ideas. Greatly appreciated everyone.
[Sony Xperia Z Ultra] Ben Ling:
Open the updater-script and delete the lines with those C68XX numbers

Btw Tianchi is the codename for T2 Ultra isn't it?
[Sony Xperia Z Ultra] RealityFails:
Its the code name for the t2. I think he wants to flash a zu ROM to it. Not sure if it'll fully work, you might end up with a soft brick or an unresponsive touch screen.
[Sony Xperia Z Ultra] Ben Ling:
Don't ever flash a different ROM for your device as it may hard brick your device!
[Sony Xperia Z Ultra] Gr1ffo:
Thanks all. I fixed the problem. Dumbo me installed Nuts TZU recovery first. Did some reading, removed it all and installed the correct zu recovery and all is okay. I can now install all the roms I want. :D
[Sony Xperia Z Ultra] Klaos3000:
Lol wat... The T2 has a Snapdragon 400 with an adreno 305. Installing a Z Ultra recovery won't let you flash Z Ultra ROMs...
[Android Apps and Games] AFN:
This thread is a duplicate, please delete it,

Created accidently