Database Develop

?? What do i use to ROOT Verizon DE stock.. I am confused..

I have rooted every phone i've had and for some reason the MOTO X is confusing me! The phone is a bone stock developers Ed. 4.2.2 pre camera.
I am confused as to which jcase method to use or if there is another option.
I am guessing PwnMyMoto 1.4.3 verizon. but i'm not sure.
Any help would be fantastic.
Thanks,
J

ejason said:
I have rooted every phone i've had and for some reason the MOTO X is confusing me! The phone is a bone stock developers Ed. 4.2.2 pre camera.
I am confused as to which jcase method to use or if there is another option.
I am guessing PwnMyMoto 1.4.3 verizon. but i'm not sure.
Any help would be fantastic.
Thanks,
J
Click to expand...
Click to collapse
PwnMyMoto and jcase's methods are for locked bootloaders. You first need to unlock your bootloader. Then you need to decide if you want to take the OTA to 4.4 or not because once you upgrade to 4.2.2 post-camera, you can never downgrade to 4.2.2 pre-camera without bricking your device.
If you want to upgrade to 4.4, here are the instructions to unlock and gain root:
[STEP-BY-STEP INSTRUCTIONS] Unlocking and Rooting a Dev Ed Moto X Running Kit Kat
I have read of others who kept the 4.2.2 bootloader and other partitions and just selectively flashed those partitions they wanted as each new upgrade's sbf firmware was released. I don't know what advantages there are to doing that.

ejason said:
I have rooted every phone i've had and for some reason the MOTO X is confusing me! The phone is a bone stock developers Ed. 4.2.2 pre camera.
I am confused as to which jcase method to use or if there is another option.
I am guessing PwnMyMoto 1.4.3 verizon. but i'm not sure.
Any help would be fantastic.
Thanks,
J
Click to expand...
Click to collapse
It's a Developer Edition. Take all the updates available (4.2.2 camera update, 4.4 and now 4.4.2). Get the unlock code from Motorola and unlock your bootloader. Once that is done, flash twrp recovery and then install root via twrp.
Very simple on Dev Editions just because you can unlock the bootloader and flash an alternate recovery (twrp, cwm, etc..).

I agree. Unlock your bootloader (Doesn't void warranty on Developer Edition), flash TWRP recovery, then boot to TWRP and install/flash SuperSU. And it doesn't matter what ROM version you're running. (there is a TWRP for 4.2.2 and one for 4.4/4.4.2).
As mentioned, the bootloader included in the android versions can prevent you from downgrading the rom version. (i.e. bootloader in 4.4.2 prevents you from downgrading to any previous ROM). Why would you want to downgrade? If you have a locked bootloader, you'd want to downgrade to be able to use the root processes needed when you have a locked bootloader. But if you have an unlocked bootloader, because you can flash an alternate recovery (not possible with locked bootloader) and root no matter what ROM version you have installed, the only reason to downgrade would be if you encounter a bug you can't deal with that isn't present in the older roms.
because 4.4.2 fixes the exchange and bluetooth issues, and doesn't introduce anything new, its suggested you update to 4.4.2 if you have an unlocked boot loader (4.4.2 isn't rootable on locked bootloaders and may not be, so its recommended that those with locked bootloaders who want to root stick with 4.4).

KidJoe said:
I agree. Unlock your bootloader (Doesn't void warranty on Developer Edition), flash TWRP recovery, then boot to TWRP and install/flash SuperSU. And it doesn't matter what ROM version you're running. (there is a TWRP for 4.2.2 and one for 4.4/4.4.2).
I didn't know there was a different TWRP for 4.2.2.
As mentioned, the bootloader included in the android versions can prevent you from downgrading the rom version. (i.e. bootloader in 4.4.2 prevents you from downgrading to any previous ROM). Why would you want to downgrade? If you have a locked bootloader, you'd want to downgrade to be able to use the root processes needed when you have a locked bootloader. But if you have an unlocked bootloader, because you can flash an alternate recovery (not possible with locked bootloader) and root no matter what ROM version you have installed, the only reason to downgrade would be if you encounter a bug you can't deal with that isn't present in the older roms.
because 4.4.2 fixes the exchange and bluetooth issues, and doesn't introduce anything new, its suggested you update to 4.4.2 if you have an unlocked boot loader (4.4.2 isn't rootable on locked bootloaders and may not be, so its recommended that those with locked bootloaders who want to root stick with 4.4).
Click to expand...
Click to collapse
From what i have read 4.4.2 isn't rootable at all. Even if you have an unlocked bootloader. Is that correct?
Great info, thanks.
I thought that the Verizon DE already had an unlocked bootloader? Or is it like an HTC where i have to go the the MOTOROLA webite and get a code?
I did something like that for an HTC ONE i have on straight talk. I unlocked the bootloader from the HTC website, then installed TWRP, and then rooted and its running a 4.4.2 ROM that is great.

ejason said:
From what i have read 4.4.2 isn't rootable at all. Even if you have an unlocked bootloader. Is that correct?
Click to expand...
Click to collapse
Incorrect. You can do whatever you want with the DE, regardless of what version of Android you're on.
Sent from my Moto X

ejason said:
I thought that the Verizon DE already had an unlocked bootloader? Or is it like an HTC where i have to go the the MOTOROLA webite and get a code?
Click to expand...
Click to collapse
There are directions on a 1 page pamphlet that came with your VZW DE on how to unlock the bootloader.
Sent from my Dev Edition Moto X

ejason said:
I thought that the Verizon DE already had an unlocked bootloader? Or is it like an HTC where i have to go the the MOTOROLA webite and get a code?
Click to expand...
Click to collapse
It is all in that step-by-step link I gave you above.

Ok, so i have my phone unlocked, updated to 4.4 and for some reason i can not flash the TWRP.
I get the error (bootloader) variable not supported!
Any ideas.
I have tried both mfastboot and fastboot and i get nothing.
I also moved all files into another folder and CD into that folder and still the same error.
Can i install the TWRP with goo manager?

ejason said:
Ok, so i have my phone unlocked, updated to 4.4 and for some reason i can not flash the TWRP.
I get the error (bootloader) variable not supported!
Any ideas.
I have tried both mfastboot and fastboot and i get nothing.
I also moved all files into another folder and CD into that folder and still the same error.
Can i install the TWRP with goo manager?
Click to expand...
Click to collapse
did it finish flashing? mine says that when i flash a recovery also, but it flashes.
after you flash it dont reboot, just go into recovery (volume down to move the selection, volume up to execute)
then select reboot system, and it will ask if you want to root.

ejason said:
ok, so i have my phone unlocked, updated to 4.4 and for some reason i can not flash the twrp.
I get the error (bootloader) variable not supported!
Any ideas.
I have tried both mfastboot and fastboot and i get nothing.
I also moved all files into another folder and cd into that folder and still the same error.
Can i install the twrp with goo manager?
Click to expand...
Click to collapse
ok, thanks for everyones hellp. Done and done..

Getting back to 100% stock after SlapmyMoto

I just unlocked my bootloader via the "chinese" unlock code...How to I get back to 100% stock after having been rooted via SlapMyMoto?
As I understand, the slapmymoto method replaces the recovery. Can I just flash the stock recovery back over it? Should I SFB back to 4.2.2 post camera then OTA back to 4.4?

JJHunterx said:
I just unlocked my bootloader via the "chinese" unlock code...How to I get back to 100% stock after having been rooted via SlapMyMoto?
As I understand, the slapmymoto method replaces the recovery. Can I just flash the stock recovery back over it? Should I SFB back to 4.2.2 post camera then OTA back to 4.4?
Click to expand...
Click to collapse
Full restore to stock would be to SBF back to appropriate version.
To just flash a recovery, simply download one, move it to ADB folder then run
Code:
fastboot flash recovery nameofyourfile.zip

asuhoops8628 said:
Full restore to stock would be to SBF back to appropriate version.
To just flash a recovery, simply download one, move it to ADB folder then run
Code:
fastboot flash recovery nameofyourfile.zip
Click to expand...
Click to collapse
If I SBF back to 4.2.2 will that flash the stock recovery and allow me to OTA to 4.4 no problem?

JJHunterx said:
If I SBF back to 4.2.2 will that flash the stock recovery and allow me to OTA to 4.4 no problem?
Click to expand...
Click to collapse
Yes, if you use RSDLite to flash a SBF you are flashing the full stock rom, recovery, boot, etc.
If you want to be on stock 4.4, why not just use RSDLite to flash the 4.4. SBF?

KidJoe said:
Yes, if you use RSDLite to flash a SBF you are flashing the full stock rom, recovery, boot, etc.
If you want to be on stock 4.4, why not just use RSDLite to flash the 4.4. SBF?
Click to expand...
Click to collapse
For some reason, I didn't think 4.4 had a SBF...Found it. Thanks.

I am rooted 4.4 and got an unlock code.
Seems like the most straightforward method to get to fully rooted (with r/w) on 4.4.2 would be to SBF 4.4 to return to full stock. Take the OTA to 4.4.2, then unlock.
Is there a way to root without a custom recovery? I was under the impression that it was much more simple with an unlocked bootloader. The guides I've seen for installing TWRP are certainly much more simple than the SlapMyMoto process, but I thought it was as simple as just installing SuperSU or putting the APK in /system or something. I guess I was mistaken on that part.
Thanks!

fury683 said:
I am rooted 4.4 and got an unlock code.
Seems like the most straightforward method to get to fully rooted (with r/w) on 4.4.2 would be to SBF 4.4 to return to full stock. Take the OTA to 4.4.2, then unlock.
Is there a way to root without a custom recovery? I was under the impression that it was much more simple with an unlocked bootloader. The guides I've seen for installing TWRP are certainly much more simple than the SlapMyMoto process, but I thought it was as simple as just installing SuperSU or putting the APK in /system or something. I guess I was mistaken on that part.
Thanks!
Click to expand...
Click to collapse
You can unlock your BL regardless of what version of android you are on. I just wanted to get back to stock so slapmymoto was no longer active (which is kinda a workaround for root imho, but it works and does its job.)
To root with an unlocked bootloader, all you have to do is download the TWRP img file and the supersu.zip file. Push the supersu.zip to your SD card. Use fastboot to flash TWRP img file. Boot into the recovery you just flashed and install the supersu.zip file. Bam you're rooted.

fury683 said:
I am rooted 4.4 and got an unlock code.
Seems like the most straightforward method to get to fully rooted (with r/w) on 4.4.2 would be to SBF 4.4 to return to full stock. Take the OTA to 4.4.2, then unlock.
Is there a way to root without a custom recovery? I was under the impression that it was much more simple with an unlocked bootloader. The guides I've seen for installing TWRP are certainly much more simple than the SlapMyMoto process, but I thought it was as simple as just installing SuperSU or putting the APK in /system or something. I guess I was mistaken on that part.
Thanks!
Click to expand...
Click to collapse
Well, you can unlock your bootloader at any time once you have the unlock code. The Android version on your phone doesn't matter.
Flashing TWRP, booting to it and installing SuperSU is how you root with an unlocked bootloader. (for full details see -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 which makes it seem like a longer process than it is.) That process is as easy as it gets, and works no matter what ROM you are on.
If you want to be on 4.4.2, and going to use RSDLite to flash an SBF anyway, the most straight forward way would be to flash the 4.4.2 SBF, then Root by flashing TWRP, booting to it, and installing SuperSU.

KidJoe said:
Well, you can unlock your bootloader at any time once you have the unlock code. The Android version on your phone doesn't matter.
Flashing TWRP, booting to it and installing SuperSU is how you root with an unlocked bootloader. (for full details see -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 which makes it seem like a longer process than it is.) That process is as easy as it gets, and works no matter what ROM you are on.
If you want to be on 4.4.2, and going to use RSDLite to flash an SBF anyway, the most straight forward way would be to flash the 4.4.2 SBF, then Root by flashing TWRP, booting to it, and installing SuperSU.
Click to expand...
Click to collapse
Thanks. Can I SBF with 4.4.2 even thought I'm still on 4.4? Or do I need to do 4.4 SBF, OTA to 4.4.2 then unlock and do TWRP/root?
Thanks again.

fury683 said:
Thanks. Can I SBF with 4.4.2 even thought I'm still on 4.4? Or do I need to do 4.4 SBF, OTA to 4.4.2 then unlock and do TWRP/root?
Thanks again.
Click to expand...
Click to collapse
No matter what rom is on your phone right now, if you have the bootloader unlock code, you can unlock. You don't have to be on a special version to unlock your phone's bootloader once you have the code.
The OTA's are incremental updates. They require pre-requisites be in place or they fail. You must be on a specific previous ROM, and "step up." They check for specific files/version/check sums to be on your phone before they install. If your phone doesn't match the version the OTA is looking for, or a particular file on your phone doesn't match what the OTA is looking for, the OTA will fail. To put it another way... to take the 4.4.2 OTA, your phone needs to be on 4.4. To take the 4.4 OTA, your phone needs to be on the 4.2.2 w/camera fix version. To take the 4.2.2 w/camera fix OTA, your phone needs to be on the initial shipping ROM version.
SBF's are complete roms containing every file/partition/modem for that version. You can flash the 4.4.2 SBF directly over any other ROM version. It wont stop you.
Just remember when flashing an SBF, there is a line in the XML that RSDLite uses that controls whether it wipes your data or not when flashing. (The thread about returning to stock using RSDlite explains it.) BUT since the process of unlocking your bootloader will factory reset your phone which wipes the data anyway...RSDLite erasing your data isn't a problem if you do it right before or right after you unlock your bootloader.

KidJoe said:
No matter what rom is on your phone right now, if you have the bootloader unlock code, you can unlock. You don't have to be on a special version to unlock your phone's bootloader once you have the code.
The OTA's are incremental updates. They require pre-requisites be in place or they fail. You must be on a specific previous ROM, and "step up." They check for specific files/version/check sums to be on your phone before they install. If your phone doesn't match the version the OTA is looking for, or a particular file on your phone doesn't match what the OTA is looking for, the OTA will fail. To put it another way... to take the 4.4.2 OTA, your phone needs to be on 4.4. To take the 4.4 OTA, your phone needs to be on the 4.2.2 w/camera fix version. To take the 4.2.2 w/camera fix OTA, your phone needs to be on the initial shipping ROM version.
SBF's are complete roms containing every file/partition/modem for that version. You can flash the 4.4.2 SBF directly over any other ROM version. It wont stop you.
Just remember when flashing an SBF, there is a line in the XML that RSDLite uses that controls whether it wipes your data or not when flashing. (The thread about returning to stock using RSDlite explains it.) BUT since the process of unlocking your bootloader will factory reset your phone which wipes the data anyway...RSDLite erasing your data isn't a problem if you do it right before or right after you unlock your bootloader.
Click to expand...
Click to collapse
After unlocking though, flashing the system.img from an SBF file and a custom recovery brings you basically back to "stock" (excluding the custom recovery) so you don't have to use RSDLite, correct?

EvanVanVan said:
After unlocking though, flashing the system.img from an SBF file and a custom recovery brings you basically back to "stock" (excluding the custom recovery) so you don't have to use RSDLite, correct?
Click to expand...
Click to collapse
For the most part, you can use mfastboot to flash just system.img and recovery.img, this will get those two parts back to stock, which is often enough to allow you to take an OTA update, however, if you've touched any other part, your phone wont be 100% stock. And then, how long does it take for the OTA to install and reboot? Now, in fury683's case, the phone is on 4.4 and he wants to go to 4.4.2. But if the phone was on say either of the 4.2.2 versions and he wanted to go to 4.4.2, then you'd also have multiple OTA's to install.
Using the full SBF and RSDlite will flash all parts, gets you to 100% stock, and immediately on the version you want. I don't know everything that SlapMyMoto and MotoWpNoMo touch, so I can't say for sure if flashing system and recovery are enough to totally remove them, or just remove enough to allow you to take an OTA.
System.img takes the longest to flash via either mFastboot or RSDLite, the rest are really quick, so the time spent using RSDLite to flash everything isn't that much more than manually flashing just system.img and recovery.img via mfastboot.
So considering that the mfastboot oem unlock does a factory reset anyway (so data is going to be lost), and flashing with RSDlite flashes all parts as 1 batched operation (i.e. you don't have to individually execute mfastboot lines...) using RSDLite can get you to the final destination, and ensure 100% stock, more easily.

I did mine last night from 4.4. I unlocked, got a clean 4.4 , took ota, flash twrp, install su. If you do in the right order shouldn't take more than 30 mins to be up and running again. If you use Titanium backup be sure to pull your files to computer before doing the bootloader unlock.

KidJoe said:
No matter what rom is on your phone right now, if you have the bootloader unlock code, you can unlock. You don't have to be on a special version to unlock your phone's bootloader once you have the code.
The OTA's are incremental updates. They require pre-requisites be in place or they fail. You must be on a specific previous ROM, and "step up." They check for specific files/version/check sums to be on your phone before they install. If your phone doesn't match the version the OTA is looking for, or a particular file on your phone doesn't match what the OTA is looking for, the OTA will fail. To put it another way... to take the 4.4.2 OTA, your phone needs to be on 4.4. To take the 4.4 OTA, your phone needs to be on the 4.2.2 w/camera fix version. To take the 4.2.2 w/camera fix OTA, your phone needs to be on the initial shipping ROM version.
SBF's are complete roms containing every file/partition/modem for that version. You can flash the 4.4.2 SBF directly over any other ROM version. It wont stop you.
Just remember when flashing an SBF, there is a line in the XML that RSDLite uses that controls whether it wipes your data or not when flashing. (The thread about returning to stock using RSDlite explains it.) BUT since the process of unlocking your bootloader will factory reset your phone which wipes the data anyway...RSDLite erasing your data isn't a problem if you do it right before or right after you unlock your bootloader.
Click to expand...
Click to collapse
Thanks for your help. The process was much less painful than I expected. Aside from downloading the SBF file, whole process to SBF, unlock, flash TWRP and root took about 20 minutes.
Working great now!
Thanks again

[Q] [Q} AT&T Moto After Sunshine

I haven't don it yet getting all the info I need before hand.
1) After I unlock the bootloader will I be able to flash the most recent update for 4.4.4 or will I just be able to unfreeze the OTA and still keep root?
2) If I loose root since I now have an unlocked bootloader I'm just a SuperSU flash away from root, right?
3) Since I'm still on 4.4.2 will I have any issues if I need to flash back to it?
Anything else I might have missed that is important either from mistakes or just general knowledge I missed would be appreciated. Thanks and Good Night everybody!

Icon000 said:
I haven't don it yet getting all the info I need before hand.
1) After I unlock the bootloader will I be able to flash the most recent update for 4.4.4 or will I just be able to unfreeze the OTA and still keep root?
Click to expand...
Click to collapse
After you unlock the bootloader, treat your device like a developer edition. I would just flash the full 4.4.4 image files for your device to bring it up to the latest version without worry of it failing because of modifications you may have made to the system (root, etc..).
2) If I loose root since I now have an unlocked bootloader I'm just a SuperSU flash away from root, right?
Click to expand...
Click to collapse
With an unlocked bootloader you can flash an alternate recovery like CWM or TWRP. These recoveries will allow you to flash SuperSU to gain root.
3) Since I'm still on 4.4.2 will I have any issues if I need to flash back to it?
Click to expand...
Click to collapse
Just like every other Motorola device (developer or not), you can not flash backwards. If you move to 4.4.4 you can NOT go back to 4.4.2.

tcrews said:
After you unlock the bootloader, treat your device like a developer edition. I would just flash the full 4.4.4 image files for your device to bring it up to the latest version without worry of it failing because of modifications you may have made to the system (root, etc..).
With an unlocked bootloader you can flash an alternate recovery like CWM or TWRP. These recoveries will allow you to flash SuperSU to gain root.
Just like every other Motorola device (developer or not), you can not flash backwards. If you move to 4.4.4 you can NOT go back to 4.4.2.
Click to expand...
Click to collapse
Great explanation! :good:

tcrews said:
After you unlock the bootloader, treat your device like a developer edition. I would just flash the full 4.4.4 image files for your device to bring it up to the latest version without worry of it failing because of modifications you may have made to the system (root, etc..).
With an unlocked bootloader you can flash an alternate recovery like CWM or TWRP. These recoveries will allow you to flash SuperSU to gain root.
Just like every other Motorola device (developer or not), you can not flash backwards. If you move to 4.4.4 you can NOT go back to 4.4.2.
Click to expand...
Click to collapse
Why do you recommend flashing 4.4.4 over accepting the OTA? I still want to be able to use the additions originally provided by Motorola. I didn't seen a rom built on Moto Stock. Did I miss it?

Flash the stock 4.4.4 ROM that is for your device.
What's better...4.4.2 with patches to make it 4.4.4 (via an OTA) or just the full 4.4.4 (via the full 4.4.4 install) without the need for patching to make it 4.4.4?
Oh well...it looks like there isn't a FULL 4.4.4 for AT&T Moto X released yet....just 4.4.2. Flash the full 4.4.2 then take the OTA update to 4.4.4 and then flash TWRP to get root.
AT&T 4.4.2
http://sbf.droid-developers.org/download.php?device=0&file=849
You can just flash the system.img from the download with mfastboot to revert any changes you did (root, etc..) so that the OTA can be installed successfully. You'll just want to get fully updated before flashing an alternative recovery like TWRP.

[Q] Downgrade system image

I know it can be done, as long as you don't OTA after. If I were to downgrade to 4.4.4 or 5.0.2 with 5.1 bootloader, would that offer a software method to root and unlock or no?
Edit: Welp, I answered my own question... I can't even flash anything because of sig checks.

darknessrise1234 said:
I know it can be done, as long as you don't OTA after. If I were to downgrade to 4.4.4 or 5.0.2 with 5.1 bootloader, would that offer a software method to root and unlock or no?
Edit: Welp, I answered my own question... I can't even flash anything because of sig checks.
Click to expand...
Click to collapse
I am looking for a downgrade without removing the bootloader . just that there's no way .

Maliktor said:
I am looking for a downgrade without removing the bootloader . just that there's no way .
Click to expand...
Click to collapse
The bootloader can not be downgraded. That would cause a brick. I'm looking for a way to downgrade the system/boot images to 4.4.4 so I could root to get an unlock on the bootloader via sunshine.

darknessrise1234 said:
The bootloader can not be downgraded. That would cause a brick. I'm looking for a way to downgrade the system/boot images to 4.4.4 so I could root to get an unlock on the bootloader via sunshine.
Click to expand...
Click to collapse
You can at least try using Kingroot to root the device for now, and wait till Sunshine is compatible with Lollipop.
With "mofo" you can flash firmwares to the phone on a locked bootloader, I wonder if there is a way to flash just system.img using mofo. Maybe ask that at their thread.

eksasol said:
You can at least try using Kingroot to root the device for now, and wait till Sunshine is compatible with Lollipop.
With "mofo" you can flash firmwares to the phone on a locked bootloader, I wonder if there is a way to flash just system.img using mofo. Maybe ask that at their thread.
Click to expand...
Click to collapse
Mofo does not work with 5.1 bootloader and kingroot does not work with 5.1. Sunshine is updated to unlock so long as you have root but I cannot find root method for 5.1.
Edit: Okay, so I'm seeing that some people HAVE downgraded their system image but eventually had a brick from OTA flashing BL. How do you downgrade the system image? If I can get to 4.4.4, I can root and unlock and go back to 5.1.

Android pay no longer works after MM upgrade [unlocked bootloader, but not rooted]

Hi all:
After upgrading my unlocked-but-still-rooted Turbo to Motorola stock Marshmallow, my Android Pay no longer works; I get the message about Android not be able to verify etc. From what I understand, SafetyNet now checks for unlocked bootloaders, not just root. Also, from what I understand, Sultanxda found a workaround by modifying the Android kernel, which they have working on the OP3.
Does anyone know if anyone is working on this for the original Turbo, and/or could someone kindly point me in the right direction?
Thanks in advance.
Workaround info: https://www.xda-developers.com/sult...otloader-check-on-latest-cm13-builds-for-op3/

phraxen said:
Hi all:
After upgrading my unlocked-but-still-rooted Turbo to Motorola stock Marshmallow, my Android Pay no longer works; I get the message about Android not be able to verify etc. From what I understand, SafetyNet now checks for unlocked bootloaders, not just root. Also, from what I understand, Sultanxda found a workaround by modifying the Android kernel, which they have working on the OP3.
Does anyone know if anyone is working on this for the original Turbo, and/or could someone kindly point me in the right direction?
Thanks in advance.
Workaround info: https://www.xda-developers.com/sult...otloader-check-on-latest-cm13-builds-for-op3/
Click to expand...
Click to collapse
Some of the CM-based ROMs floating around address this issue, but there is no way to use stock marshmallow with an unlocked bootloader and pass safetynet. So if you want android pay, your options are to stay on SU4TL-49 or install one of the CM-based ROMs that have implemented a workaround.
I got around this issue by using my credit card company's app instead of Android Pay. It allows me to do wireless payments everywhere Android Pay is accepted, but it only checks for root. It does not use safetynet.

Too late for you now, but recently someone in this forum updated to Marshmallow radio, but did NOT flash the Marshmallow bootloader. They were already using custom ROM. Others using that ROM who flashed Marshmallow bootloader no longer pass safetynet, but that person does. The conclusions is an unlocked Marshmallow bootloader or newer is what Safetynet looks for?
And yes, I've flashed both Marshmallow bootloader and radios over both my daily XT1225. I could only test the theory by breaking out my new-in-box third Quark, which have for emergency back-up -- and is which still probably on Kitkat.
While I previously had the older Google Wallet, Android Pay for me is not as important as controlling my own phone as I please. My phones will always be rooted. And in the Moto Quark, unlocking the bootloader is necessary for permanent root, whereas it's not necessary in some other phones -- like LG. But whatever needs to be done to root my phones, I will. And if Android Pay is not possible, so be it. I always carry my wallet when I go out somewhere. Pulling out my phone, pulling out my wallet, what's the difference?

phraxen said:
Hi all:
After upgrading my unlocked-but-still-rooted Turbo to Motorola stock Marshmallow, my Android Pay no longer works; I get the message about Android not be able to verify etc. From what I understand, SafetyNet now checks for unlocked bootloaders, not just root. Also, from what I understand, Sultanxda found a workaround by modifying the Android kernel, which they have working on the OP3.
Does anyone know if anyone is working on this for the original Turbo, and/or could someone kindly point me in the right direction?
Thanks in advance.
Workaround info: https://www.xda-developers.com/sult...otloader-check-on-latest-cm13-builds-for-op3/
Click to expand...
Click to collapse
So actually there is a way to get safetynet working again. All you have to do is flash the SU4TL-49 bootloader and wipe cache. I'll be posting the bootloader separately when I get a chance, but if you don't want to wait that long, download the full firmware package here: https://mega.nz/#!i84inDgI!IM_A_IpLlKfGpC90S2DPB6g9t8rVkhO8heE4o_WpdMI, extract bootloader.img and flash using fastboot.
fastboot flash motoboot bootloader.img
fastboot erase cache
EDIT: Here is a flashable zip that will flash the bootloader for you for those who are so inclined. Make sure to wipe cache and dalvik/art cache in TWRP afterwards: https://mega.nz/#!6logEaIQ!q8qPJw65Upt38Hxiu1JyxErmwbgL7CBzuGzzPC0C9pQ
EDIT 2: And here is the bootloader.img taken from the SU4TL-49 package if fastboot is your weapon of choice: https://mega.nz/#!iogRGIrQ!ixpZGw1cR90jLxe9r8EAt76SGNoSqVqSv1iu0v14QCc

TheSt33v said:
So actually there is a way to get safetynet working again. All you have to do is flash the SU4TL-49 bootloader and wipe cache. I'll be posting the bootloader separately when I get a chance, but if you don't want to wait that long, download the full firmware package here: https://mega.nz/#!i84inDgI!IM_A_IpLlKfGpC90S2DPB6g9t8rVkhO8heE4o_WpdMI, extract bootloader.img and flash using fastboot.
fastboot flash motoboot bootloader.img
Remember to wipe cache afterwards.
Click to expand...
Click to collapse
I'm confused... isn't that downgrading the bootloader?

ChazzMatt said:
I'm confused... isn't that downgrading the bootloader?
Click to expand...
Click to collapse
Yes it is. And as long as your bootloader is unlocked, no harm no foul. I thought that downgrading the bootloader was the one thing that you couldn't do even if it was unlocked, but I just did it and I'm passing safetynet now, so I guess I was wrong.
If anyone wants proof I'm on the SU4TL-49 bootloader, I can take a picture when I get home. I don't know of a way to get a picture of the bootloader screen using only my phone.

TheSt33v said:
Yes it is. And as long as your bootloader is unlocked, no harm no foul. I thought that downgrading the bootloader was the one thing that you couldn't do even if it was unlocked, but I just did it and I'm passing safetynet now, so I guess I was wrong.
Click to expand...
Click to collapse
Learn something new everyday. Wow.
You just can't downgrade a locked bootloader, eh?
Thank you!
When I get home will try Lollipop bootloader on my XT1225.
The custom ROM guys will love this, then.

ChazzMatt said:
Learn something new everyday. Wow.
You just can't downgrade a locked bootloader, eh?
Thank you!
When I get home will try Lollipop bootloader on my XT1225.
The custom ROM guys will love this, then.
Click to expand...
Click to collapse
I seem to remember trying this a long time ago using TWRP, and TWRP was unable to flash the older bootloader. It works fine through fastboot though. I'm going to do some more investigation when I'm not at work to see if I can get TWRP to do this. That would be easier for most people.
Also, I thought the latest iSu already got around this issue. That's what BHB's command line patch thing is for. But it will certainly make things easier!

TheSt33v said:
I seem to remember trying this a long time ago using TWRP, and TWRP was unable to flash the older bootloader. It works fine through fastboot though. I'm going to do some more investigation when I'm not at work to see if I can get TWRP to do this. That would be easier for most people.
Also, I thought the latest iSu already got around this issue. That's what BHB's command line patch thing is for. But it will certainly make things easier!
Click to expand...
Click to collapse
I was on the latest bootloader and just flashed the .47 bootloader because of major radio issues. I flashed from TWRP and have been doing it since the .49 update.

gumbi2647 said:
I was on the latest bootloader and just flashed the .47 bootloader because of major radio issues. I flashed from TWRP and have been doing it since the .49 update.
Click to expand...
Click to collapse
Interesting. I've noticed that TWRP randomly has issues with flashing things on my phone for some reason, and a reboot often fixes the issue. Maybe I just got unlucky that one time, but if that's the case, I'll have a flashable SU4TL-49 bootloader up a few minutes after I get home.

TheSt33v said:
Interesting. I've noticed that TWRP randomly has issues with flashing things on my phone for some reason, and a reboot often fixes the issue. Maybe I just got unlucky that one time, but if that's the case, I'll have a flashable SU4TL-49 bootloader up a few minutes after I get home.
Click to expand...
Click to collapse
IF you can flash through TWRP, then clearing caches is no problem in TWRP. IF we must use ADB, please include instructions to also clear caches that way, in any write-up -- if that's what you mean?
Or you do you mean flash bootloader in ADB, then immediately boot into TWRP and clear caches -- before booting back to system?

ChazzMatt said:
IF you can flash through TWRP, then clearing caches is no problem in TWRP. IF we must use ADB, please include instructions to also clear caches that way, in any write-up -- if that's what you mean?
Or you do you mean flash bootloader in ADB, then immediately boot into TWRP and clear caches -- before booting back to system?
Click to expand...
Click to collapse
ADB is not involved. Only fastboot.
The way I did it on my phone (XT1254 unrooted, unlocked, 100% stock MM) exactly was this:
1. Make note of BL version on bootloader screen.
2. fastboot flash motoboot bootloader.img using the SU4TL-49 bootloader.
3. Reboot bootloader
4. Confirm that the BL version has changed (it did)
5. Reboot to system.
6. Tried safetynet (failed)
7. Reboot to stock MM recovery menu
8. Wipe cache, reboot to system
9. Tried safetynet (passed), added a bunch of cards in Android Pay without issue
I'm assuming that wiping cache using other methods will be just as effective, but I don't know that for sure.

TheSt33v said:
ADB is not involved. Only fastboot.
The way I did it on my phone (unrooted, unlocked, 100% stock MM) exactly was this:
1. Make note of BL version on bootloader screen.
2. fastboot flash motoboot bootloader.img using the SU4TL-49 bootloader.
3. Reboot bootloader
4. Confirm that that BL version has changed (it did)
5. Reboot to system.
6. Tried safetynet (failed)
7. Reboot to stock MM recovery menu
8. Wipe cache, reboot to system
9. Test safetynet (passed)
I'm assuming that wiping cache using other methods will be just as effective, but I don't know that for sure.
Click to expand...
Click to collapse
Which version of TWRP are you using? I heard the 04 update has some issues. I have been on 03 forever.

gumbi2647 said:
Which version of TWRP are you using? I heard the 04 update has some issues. I have been on 03 forever.
Click to expand...
Click to collapse
04, so that could be it.

I post this around XDA, new bootloader add a new prop line
it add
[ro.boot.flash.locked]: [0]
And I patch that with this
https://www.androidfilehost.com/?fid=745425885120696423
with will change that to
[ro.boot.flash.locked]: [1]
Just use adb command
Code:
getprop | grep ro.boot.flash.locked
to check.
and then cts will not fail so is not really need to downgrade for now, There is the chance that Moto will change the boot.img so it can't boot on old bootloader, that did not happens yet on quark but others Moto device is need latest bootloader with latest ROM.
But then again may never be a update from Moto to this device.
So as long Moto did not make another patch flash this in TWRP and test with latest bootloader
https://www.androidfilehost.com/?fid=745425885120696423
of course that will not fix any other CTS fail like xposed or ROOT
So let me know if that helps if not it may be somethings else that can also be patched.

TheSt33v said:
So actually there is a way to get safetynet working again. All you have to do is flash the SU4TL-49 bootloader and wipe cache. I'll be posting the bootloader separately when I get a chance, but if you don't want to wait that long, download the full firmware package here: https://mega.nz/#!i84inDgI!IM_A_IpLlKfGpC90S2DPB6g9t8rVkhO8heE4o_WpdMI, extract bootloader.img and flash using fastboot.
fastboot flash motoboot bootloader.img
fastboot erase cache
Click to expand...
Click to collapse
Thanks for this. I'll give it a shot and let you know how it turns out.

bhb27;70506510So as long Moto did not make another patch flash this in TWRP and test with latest bootloader
[url said:
https://www.androidfilehost.com/?fid=745425885120696423[/url]
of course that will not fix any other CTS fail like xposed or ROOT
So let me know if that helps if not it may be somethings else that can also be patched.
Click to expand...
Click to collapse
Thanks! Flashing that works just fine. So now we have 2 options.

bhb27 said:
I post this around XDA, new bootloader add a new prop line
it add
[ro.boot.flash.locked]: [0]
And I patch that with this
https://www.androidfilehost.com/?fid=745425885120696423
with will change that to
[ro.boot.flash.locked]: [1]
Just use adb command
Code:
getprop | grep ro.boot.flash.locked
to check.
and then cts will not fail so is not really need to downgrade for now, There is the chance that Moto will change the boot.img so it can't boot on old bootloader, that did not happens yet on quark but others Moto device is need latest bootloader with latest ROM.
But then again may never be a update from Moto to this device.
So as long Moto did not make another patch flash this in TWRP and test with latest bootloader
https://www.androidfilehost.com/?fid=745425885120696423
of course that will not fix any other CTS fail like xposed or ROOT
So let me know if that helps if not it may be somethings else that can also be patched.
Click to expand...
Click to collapse
That worked for me. I was able to add a debit card without getting the error.
Thanks to you and TheSt33v.

ChazzMatt said:
IF you can flash through TWRP, then clearing caches is no problem in TWRP. IF we must use ADB, please include instructions to also clear caches that way, in any write-up -- if that's what you mean?
Or you do you mean flash bootloader in ADB, then immediately boot into TWRP and clear caches -- before booting back to system?
Click to expand...
Click to collapse
Have you tried this using TWRP and if so did everything go well
Sent from my XT1254 using Tapatalk

joekitch said:
Have you tried this using TWRP and if so did everything go well
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
I have not personally tried it yet. Someone else can answer if they have?