yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) General] ChazzMatt:
The problem with your information is it's wrong.

Several Motorola Marshmallow firmware in various Moto phones need beta 2.62 SuperSu for initial root. Only that beta version will work, after which you can then update to latest SuperSu.

Using so-called stable or even newer SuperSu will cause bootloops. Only that older beta SuperSu works on many Motorola Marshmallow firmware.

We discovered it in the Moto Quark phones, as well as Kinzie, and here's a thread for 2015 Moto G3:

How to get root 2015 Moto G3 With Stock Android Marshmallow 6.0 (XT1541)

https://xdaforums.com/2015-moto-g/general/root-how-to-root-moto-g-2015-android-t3320113

I wrote the bootloader unlock and rooting guide for the 2014 Moto XT1225 and Moto XT1250 (Moto Turbo/Moto Maxx).

UPDATED GUIDE: How to unlock your MOTO MAXX/MOTO TURBO bootloader/install TWRP/root

https://xdaforums.com/showthread.php?t=3455341

Months later when the sibling Quark Droid Turbo XT1254 was updated to Marshmallow, that beta SuperSu requirement still applied.

[GUIDE] How to unlock your Droid Turbo bootloader, install TWRP and gain root access

https://xdaforums.com/showthread.php?t=3292684

Also applies for 2015 Kinzie, the Moto X Force (sibling to the Droid Turbo 2)...

[ROOT][INFO][MARSHMALLOW] How to Root Moto X Force 6.0 [TESTED]

https://xdaforums.com/droid-turbo-2/general/root-how-to-root-moto-x-force-6-0-t3282151

and probably many other Motorola phones.
[X Style (Pure) General] ResistanceIsFutile:
You did see the title right "Please Clarify"

I'm not the original author of the guide and was only seeking to understand the directions in the guide itself with the use of a correct SU version. It's so nice to see you understood that.

As why you quoted my post and replied to it - and then to say my information was being wrong - it was mostly of my asking questions anyway, you do realize this - so what's mis-informative as being wrong. I never did read just what it was you meant to where what I had said was wrong.

The whole Guide - then your meaning? Or only #3 of the Prerequisites and the note there after "Unless otherwise stated, do not use a beta version for rooting Moto devices. SuperSU versions with even numbers are stable versions, while odd numbered versions are beta editions."

Still again I'm not the author, maybe you should talk [MENTION=2001582]acejavelin[/MENTION] .

Thinking I'd read something somewhere and then put it into brackets was only to understand or even in guessing what could of been happening here to the directions in the guide in seeking a proper SU?

So what's wrong with asking questions and trying to put some logic to what else is found along the same lines of reasoning with the guides directions?

I do thank you for the positive information you offered here.

To ask questions and try to understand isn't being wrong - is it really :)
[X Style (Pure) General] acejavelin:
I stand by my guide(s), they have been used to root dozens, maybe hundreds, of Moto devices.

In general, the beta SuperSU is not needed for most 3rd and 4th generation Moto devices running Marshmallow, the current stable release works fine if you create the .supersu file correctly. That said, there are some troublesome devices where the 2.62-3 beta works although investigation into the few I've been able to access almost always are due to user error.

[MENTION=3250376]ChazzMatt[/MENTION] The methods shown in my first post are tested and have worked for lots of users... The beta SuperSU is not necessary in 95% of the phones my guide(s) is written for, including the Moto G 3rd and 4th generation devices and the Moto X Pure/Style, plus other devices like the Moto Z from feedback I have gotten from users
[X Style (Pure) General] ChazzMatt:
No, I did not see that. I was quoting you and your post. That's why the words showed up when I quoted you. If you quoted someone else it was not clear, especially on a mobile app view.

If you did not write that I apologize but still stand by my opinion that information is not correct, especially for Motorola devices on Marshmallow.

---------- Post added at 11:14 AM ---------- Previous post was at 11:10 AM ----------

I beg to differ. [MENTION=2376614]jcase[/MENTION] of the Sunshine team asked us for information on how to root Marshmallow stock firmware for the Quark (Droid Turbo). He had tried other methods, other versions of SuperSu and he's quite experienced (an understatement).

I am only showing it's NOT user error when people trying to root on stock Marshmallow and some Motorola phones cannot succeed with latest SuperSu. Only that beta SuperSu version works for several Moto phones on stock Marshmallow.

Just FYI for anyone having issues.
[X Style (Pure) General] acejavelin:
I didn't write a guide for Quark... :)

I can attest the method in this thread works for many Moto devices since SuperSU 2.72, and continues to work on current versions. I am not saying it will work on all Moto devices, but it has been tested in several.
[X Style (Pure) General] ResistanceIsFutile:
Gentlemen, [MENTION=2001582]acejavelin[/MENTION] and [MENTION=3250376]ChazzMatt[/MENTION].

You both have been active on XDA for sometime and given readers helpful information, then again where you disagree is somewhere here in Motorola phones and Marshmallow. That's fine with me as I truly don't know. Then I'd like to see you both keep an open mind to the other for a specific exchange of ideals of these phones.

Would it be safe to say you both have achieved good results on certain Motorola phones with Marshmallow that you each had experiences in or herd from others using your methods. Then if one method doesn't work in a certain Moto model on Marshmallow, giving advise to try the other guys findings of his methods could help in these cases.

I'm not going to take sides as like I said I truly don't know - but you can count on it, if I and others run into trouble, that's probably our best resolve to at least try the others one method.

I hope this encounter has been a bridge to you both and nothing less than to help all Moto users/owners.

Peace on XDA
[X Style (Pure) General] acejavelin:
I think [MENTION=3250376]ChazzMatt[/MENTION] and I are good... I didn't think we were being hostile in any way, just each trying to help in own way. If it was taken any other way, I apologise.
[X Style (Pure) General] ResistanceIsFutile:
I too

I to offer my apologies to you both if something I did caused the confusion.

I can read something into nothing sometimes and do feel bad if I started it in someway.

XDA is a world stage of knowledge being exchanged by the nano-second and I try to grow with everything I read.
[X Style (Pure) General] ChazzMatt:
We're OK. :good:

I had subscribed to this thread since a friend was asking about the Moto X Pure and I was doing research.

But I am very aware that beta SuperSu 2.62 seems to be the only way to root at least three different series of Motorola phones on Marshmallow:

2015 Moto G3,

the 2014 Quark (Moto Turbo XT1225, Droid Turbo X1254, Moto Maxx XT1225) and

2015 Kinzie (Moto X Force).

I wrote the guide on one of those and am in close contact with the writer of one of the others. And perhaps there may be more?

So, this morning on a mobile app when I read in a post what seemed like a blanket statement -- I was wrong upon re-reading -- I stated what I knew from experience and research on Motorola phones, particularly with Marshmallow.

But I was wrong because of this:

The caveat is "unless otherwise stated" -- which I admit I glossed over. ;) So, maybe for the Moto X Pure/Style, you don't need a beta SuperSu, but for some other Moto phones (on Marshmallow) you do... And that clearly falls into the "unless otherwise stated" category. :good: Therefore I was wrong to write a reply as strongly as I did. I apologize.

Again, [MENTION=2001582]acejavelin[/MENTION] is the expert on Moto X Pure/Style. I've never touched one.
[X Style (Pure) General] acejavelin:
Yeah, I may need to edit that... the point of that statement dealt with a specific beta version of SuperSU that was specifically for the Note 7 and caused issues (bootloop) when trying to flash it to a Moto.

To be honest, I am planning on re-writing all my root guides soon, or maybe creating new one, using Magisk which seems a WAY easier way to root now days. I've tested it with clark (Moto X Pure), super simple... still need to test on osprey/merlin, harpia, and athene devices though.

My daily is a Moto X Pure, but I have a couple other Moto's in my "spares" drawer... Moto G 2015 (osprey) is my main mess around device.
[X Style (Pure) General] PassatSport15:
I am on SuperSU 2.79, it's a beta version. No issues at all, when I flashed.

Now I am wondering as to what I should look for, issue wise.

Should I just flash the SuperSU 2.78?

Thanks

Sent from my Portable
[X Style (Pure) General] acejavelin:
No... 2.79 is latest official release. For some reason the old odd-even rule doesn't apply any more.

You're good, leave it as is if it's working.
[X Style (Pure) General] PassatSport15:
Yes, I will leave it alone. The installation was flawless!

Thank you! Great info on this thread..Keep up the fabulous work.

Sent from my Portable
[X Style (Pure) General] ResistanceIsFutile:
That's good to know and that this guide is still confirmed for the Moto X Pure XT1575, when my short Retailers warranty on this used Moto X I've bought is up - I'll be right here doing it and report my results for the threads benefit.

I know [MENTION=2001582]acejavelin[/MENTION] and [MENTION=3250376]ChazzMatt[/MENTION] are both great contributors on XDA and respected in their own rights - both were being right as to what each one was saying, but not catching on to the understanding in the meaning of the other one - at first.

A simple mis-understanding here - that I hope I hadn't impacted.

It's really good to know that all ends well.

I have a friend working on a TWRP flashable .zip for the most current version of Stock Android 6.0.1 Marshmallow for the xt1548 (Moto G3 2015). Trying to offer it as debloated, zipaligned, pre-rooted, injected with the SuperSU & BusyBox binaries. The ROM to be configured for TextNow subscribers, with APNs, ERI.xml and network settings preset, the TextNow system app & libs to be installed.

Then found himself trying to ironing out a small detail on the modified ramdisk/kernel in boot.img for the baked in systemless root. Both himself and a tester bootlooped on first boot. Turns out it was related to root binaries and boot image support of the stock kernel, as he noted.

Then he notes: as previously discussed on a different thread in this forum, the newer SuperSU systemless root binaries cause perpetual bootlooping and some corruption to the ramdisk in boot.Iimg. The only resolution I've found - a totally solid solution - is to flash the older SuperSU v2.62 Beta version with an older build of TWRP recovery (2.8.7.0). I now have all booting issues remedied and with full systemless root and BusyBox binaries installed.

I wonder if this discussion - he mentions (above) was [MENTION=3250376]ChazzMatt[/MENTION] revelations.

I did mention to him the Magisk [MENTION=2001582]acejavelin[/MENTION] mentioned to me in another thread.

Which my friend says - Magisk may very well be the wisest alternative.

That was before he decided to better avoid issue, he will post the ROM and a link for systemless SuperSU, so that users can achieve root themselves once the ROM has been flashed.

Why all this, I hope is to mean that YES some Moto's have problems gaining Root, and users as well as developers alike face issues when seeking or contributing in the community. There's not just only one phone model being sold but many, and even a one Root method that is guaranteed to work for every phone model.

Every developers contribution has a potential to helping many, be an inspiration to many more to rock the status quo of what's out there.

I only wished I was a fraction as good as some threads authors I've read of here, and in being able to troubleshooting as I see it - is where all progress comes from besides the great ideals given here on XDA that stimulate everyone of us in the community. Thank you Gentlemen for your contributions!
[X Style (Pure) General] Drackula2000:
Anyone know if this will fix the phone missing the ICCID causing no signal? I bought a phone that must have been rooted and returned to stock relocking the Boot loader. I have flashed back to stock and updated to 6.0 but still can't get data. Do I need to reunlock and root to get it working? Or can you edit the ICCID?
[X Style (Pure) General] acejavelin:
Why do you think it's been flashed? Easy to tell, in the bootloader what is the status #?
[X Style (Pure) General] Drackula2000:
Status code is 0 But The line qe0/1 indicates the device was previously rooted. Just because the phone is not unlocked now, doesn't mean it wasn't previously unlocked. According to Motorola forums member I don't think I can post links yet.
[X Style (Pure) General] Drackula:
https://forums.lenovo.com/t5/Moto-X...ID-unknown/m-p/3626088/highlight/false#M18538 does that really mean this device was unlocked? And if so will reunlocking and following this guide get my iccid back to data? I don't want to unlock if it's not been do before.
[X Style (Pure) General] acejavelin:
Status code 0, never been unlocked... 1 is relocked and 3 is unlocked. There is no way to edit or change this. Your device has never been rooted.
[X Style (Pure) General] Drackula2000:
Actually When I got the device the bootloader showed status modified, Can that mean it was unlocked at some point?
[X Style (Pure) General] acejavelin:
As far as we know, the bootloader status code cannot be modified manually... If it is 0 then it has never been unlocked, if someone relocked the bootloader it would be a status code of 1.

It is possible someone (unsuccessfully) attempted to root with something like Kingoroot and tripped the modified flag, but that is the only thing I can think of short of a bad internal storage chip.
[X Style (Pure) General] Drackula:
So then for this device is it worth trying this method to get the iccid back?
[X Style (Pure) General] acejavelin:
Hmm... The ICCID is embedded in the SIM, not the phone. This sounds like a bad SIM assuming your phone have a valid IMEI number.
[X Style (Pure) General] Drackula:
Oddly in factory mode I can see that its reading the sim.

http://imgur.com/gallery/KOSxL
[X Style (Pure) General] acejavelin:
Have you done a factory reset in stock recovery or tried a different SIM, preferably from a different carrier?

What firmware and radios do you have? A mismatch of kernel and radio stack can cause this... Go to Setting - About Phone and scroll to the bottom and take a screenshot please.
[X Style (Pure) General] Drackula:
https://drive.google.com/open?id=0B37tulj9AtPOX1Rfay1EOG1TT1U Screenshot The odd thing is it knows there is a voicemail on the phone, I can't call it or do anything with it but it knows there is a pending VM. I will pull a sim from another device later today and retest. Factory resetting now same after factory reset, Sees VM no data. Different Sim got APN settings to pop up. NO service still cant find networks, Rebooted and lost those settings now.
[X Style (Pure) General] acejavelin:
You are on a very old version, over a year old but you have newer radios somehow... Consider a complete flash with the latest version available. Factory reset first in stock recovery and perform a complete flash with the most current image.
[X Style (Pure) General] Drackula:
updated post, flash latest as in flash 6.0 official from moto? And do I need to unlock to do so or can I flash official without it? XT1575	01-SEP-16	MPH24.49-18_18	is on the moto site

Found your sig link for the return to stock and relock trying that now with 6.0 FW
[X Style (Pure) General] PassatSport15:
Hmmm..

Make sureyou have the proper sim card. Only reason, I suggested that is because my Note 5 sim, nano sim card.

Basically the same som card but I couldn't use that sim card. Just an fyi, wasn't sure if this jas anything to do with ur issue.

Did T-Mobile hooked that up or did you swap sim cards only.

Sent from my Portable
[X Style (Pure) General] Drackula:
The tmo sim is just a burner I used a cricket and it worked for a moment, and let me see apn settings but after reboot nothing, Just flashed while locked the stock 6.0 from the above and still no data.
[X Style (Pure) General] PassatSport15:
You need to give them your imei & serial number.

It's an unlocked phone, they need to update that in their database. I would try that, I bet that's the issue.

Especially, that your not getting data.

That's all sim - voice & data..

That sim needs to be activated on their end and you will get a ota signal which updates the prl and configuration.

Sent from my Portable
[X Style (Pure) General] Drackula:
Thats not how GSM works really.
[X Style (Pure) General] PassatSport15:
Ok, just a suggestion..good luck

Sent from my Portable
[X Style (Pure) General] Drackula:
Well it's give me the ideas to get the update numbers*228 but that doesn't work. I do have APN settings now though. Any calls say radio off.
[X Style (Pure) General] aybarrap1:
While you are correct, I have had to give AT&T my IMEI once or twice in the past to get my data working. Of course AT&T is notorious for granular control on their networks. Most of their branded phones remove the option to select network bands (I.e. disable LTE) as an example.
[X Style (Pure) General] PassatSport15:
*#*#3282#*#*

Passaword: 000000

Actually it won't work, you need to be on a tower network.

Sent from my Portable
[X Style (Pure) General] acejavelin:
OK, I said this once and I will say it again a little more bluntly... DO NOT USE THE ONE ON MOTO's WEBSITE, it is old... it is the FIRST RELEASE of Marshmallow for this device. The more you try to use Moto's website as a resource here, the worse it will get. Why they call it 24.49-18_18 is beyond me, it is the original 24.49-18 ROM.

The most current factory image release we have available as I write this for the Pure is 24.49-18-8 (Sept 1, 2016, security patch update), At this time we have no newer image, you can attempt to flash it to at least bring the radio and kernel into line, which MIGHT allow the device to activate.

AT&T has no issues with any IMEI except at initial activation to verify feature capability, and asking CS to just use that can do XXX will get you activated (this is how I had Visual Voicemail on both my Moto G 2015 and Moto X Pure).

Never use *228 on a GSM device, it will at best do nothing, at worst it will corrupt your APN information. PRL's are not used in GSM like they were years ago.
[X Style (Pure) General] Drackula:
Thanks Ace I used the direct links from the return to stock thread and that's gotten me to get APN settings. But the device shows radio off when making calls or it says turn off airplane mode.
[X Style (Pure) General] acejavelin:
Reflash the radio stack... verify you get an OKAY at each piece...

fastboot flash modem NON-HLOS.bin

fastboot erase modemst1

fastboot erase modemst2

fastboot flash fsg fsg.mbn

If you get an OK at each step and the APN shows up, IMEI is valid, and the kernel/radio match (which they should if you flashed the ROM correctly), then there is something else wrong...
[X Style (Pure) General] Drackula:
Will do thanks for your help I really appreciate it! I'll have to buy you a ?

---------- Post added at 08:56 PM ---------- Previous post was at 08:26 PM ----------

Well that was a no go, All ok but still radio off and can't find networks to connect to, This has been progressing. How do I tell if they match? Should I move this to another thread?
[X Style (Pure) General] acejavelin:
fastboot flash boot boot.img

From same image... Or just flash the full image again, and verify you get an Okay after each step.
[X Style (Pure) General] Drackula:
Sadly same thing. No change. Full flash with locked boot OK on all but there are only 8 sparse chunks not 9 like others.
[X Style (Pure) General] acejavelin:
That's fine, as long as you flashed the number that matches your image.

I'm running out of ideas here, other than a new SIM... This looks exactly like my phone did when I started H2O Wireless until I called them and had them active my SIM (even though I had done it online).

Sorry, running out of ideas...
[X Style (Pure) General] PassatSport15:
Sent from my Portable
[X Style (Pure) General] Knight-Rider:
So there's no way of resetting the counter even if you unroot correct?
[X Style (Pure) General] acejavelin:
Correct... It will forever show a status of 1 (relocked) or 3 (unlocked).
[X Style (Pure) General] Knight-Rider:
Thanks.
[X Style (Pure) General] Drackula:
So for funs I unlocked the bootloader, Flashed twrp installed SU systemless, Flashed a rom and now it doesn't see the sim at all. No apn again. This is a tough one.
[X Style (Pure) General] acejavelin:
Using the method in the first post?
[X Style (Pure) General] Drackula:
Followed it to the end. Was getting a phone..com error when trying to access APN settings. Seemed like a bug possibily due to the gapps I used that replaced a few things. So followed your back to stock guide and only error I got was preflash validation. I have 3 of these all same symptoms. My next thought is to try CDMA workshop to restore the iccid. Lenovo wanted 140 each to repair if all else fails I'll replace the boards for 75 ish each and come out ahead. Pretty sure after looking at the qpst tool they lte bands are missing. Now to understand how to enable them.
[X Style (Pure) General] mt021322:
with a nougat updates coming,.how to remove this root?btw thanks for your this root method,it's work for me,.
[X Style (Pure) General] ChazzMatt:
Don't take the OTA update. You can wait and install full firmware once it's available, via RSDLite or ADB.

You will lose root flashing the new full firmware, but no need to remove root before then.

In some forums, people will even post TWRP flashable versions of the full firmware. Then, just re-root.

I never take OTA updates, as they are just partial firmware. IF there's bugs or something goes wrong you are in a world of trouble. You often can't return to older firmware and need to wait for the full firmware release anyway. It's just safer to wait. For instance

this guy is having problems.
[X Style (Pure) General] mt021322:
ok,thanks for your advise sir