[Q] Developer Edition and Updates

[Q] Developer Edition and Updates - Moto X Q&A

Hey all,
Sorry for the extremely basic question, I have just been away from Android and flashing ROMs for so long I forgot some really basic stuff. I have a Verizon developer edition with the bootloader unlocked and am currently on Eclipse 3.1.2. I kept getting a Verizon OTA notification and ignoring it, but the other night I accidentally pressed the update button. Now my device keeps rebooting into TWRP. I am kinda glad because I was putting off updating for way too long. So I have a few options as I understand it.
1) Use fastboot files to update to the latest version (4.4.4). I can't find developer edition SBFs (http://sbf.droid-developers.org/phone.php?device=0), do I just use the standard Verizon version?
2) Restore the stock ROM backup I made with TWRP and just use the Verizon OTA.
Is there a downside to either one? Is either one inherently better?
Thanks in advance guys, my life has been pretty heavy recently and I can't believe I lost this basic knowledge.

I_EAT_BABIES said:
Hey all,
Sorry for the extremely basic question, I have just been away from Android and flashing ROMs for so long I forgot some really basic stuff. I have a Verizon developer edition with the bootloader unlocked and am currently on Eclipse 3.1.2. I kept getting a Verizon OTA notification and ignoring it, but the other night I accidentally pressed the update button. Now my device keeps rebooting into TWRP. I am kinda glad because I was putting off updating for way too long. So I have a few options as I understand it.
1) Use fastboot files to update to the latest version (4.4.4). I can't find developer edition SBFs (http://sbf.droid-developers.org/phone.php?device=0), do I just use the standard Verizon version?
2) Restore the stock ROM backup I made with TWRP and just use the Verizon OTA.
Is there a downside to either one? Is either one inherently better?
Thanks in advance guys, my life has been pretty heavy recently and I can't believe I lost this basic knowledge.
Click to expand...
Click to collapse
There is nothing different about the Dev edition SBF vs. the regular XT1060 SBF. Use the standard Verizon version.
Definitely use Option 1. You are at risk of bricking if you choose option 2.
Normally, I would say just SKIP the command "fastboot erase userdata" (to preserve all of your data and apps), but since you are on a custom ROM, you may have issues. You can try it anyways -- if anything goes wrong, just flash the entire SBF again, INCLUDING the fastboot erase userdata command (which will erase everything) and all well be well.
Make sure you use mfastboot instead of regular fastboot.

samwathegreat said:
There is nothing different about the Dev edition SBF vs. the regular XT1060 SBF. Use the standard Verizon version.
Definitely use Option 1. You are at risk of bricking if you choose option 2.
Normally, I would say just SKIP the command "fastboot erase userdata" (to preserve all of your data and apps), but since you are on a custom ROM, you may have issues. You can try it anyways -- if anything goes wrong, just flash the entire SBF again, INCLUDING the fastboot erase userdata command (which will erase everything) and all well be well.
Make sure you use mfastboot instead of regular fastboot.
Click to expand...
Click to collapse
Thanks man! I was going to use RSD for the SBF files, is that not a good idea?

I_EAT_BABIES said:
Thanks man! I was going to use RSD for the SBF files, is that not a good idea?
Click to expand...
Click to collapse
Perfectly fine...but it will erase everything.
Unless, of course you unzip the SBF, edit the XML file with notepad (or similar) and remove the entire line that says "erase userdata".

samwathegreat said:
Perfectly fine...but it will erase everything.
Unless, of course you unzip the SBF, edit the XML file with notepad (or similar) and remove the entire line that says "erase userdata".
Click to expand...
Click to collapse
Hmm, I think I'll just leave it in there and get a perfectly clean install. Thanks for the help man, I cam back in to my room to restore to my old backup and read your response. You potentially saved me from bricking my advice. Thanks!

I_EAT_BABIES said:
Hmm, I think I'll just leave it in there and get a perfectly clean install. Thanks for the help man, I cam back in to my room to restore to my old backup and read your response. You potentially saved me from bricking my advice. Thanks!
Click to expand...
Click to collapse
You are welcome. A few other thoughts: the potential to brick only comes if either the bootloader or partition table are mismatched. This can happen during a failed OTA install.
In addition to that, even if you DID restore the twrp backup successfully, you still couldn't take the OTA. Remember: STOCK recovery is required to accept any OTAs. It would have continued to boot-loop.
Once you finish with RSD Lite, just use fastboot to flash custom recovery back on. Use the latest version of TWRP, find it here: http://techerrata.com/browse/twrp2/ghost
Just: fastboot flash recovery twrp_file_name.img
Then, IMMEDIATELY afterwards, type: fastboot reboot-bootloader
Next, VOL DOWN to highlight recovery, and VOL UP to boot into it.
If you don't immediately boot into TWRP after flashing it, it won't "stick" (we don't know why...but as long as you do this, it will stick permanently, or until you flash something else to recovery).
As you probably already know, as soon as you go to exit TWRP it will offer to root for you.
Good Luck! Update us to success.
P.S. -- Sent you a PM.

I tried this with the VZW imgs and now I get the unlocked bootloader warning. I don't recall getting that before, thoughts?
I assume it's because the imgs are not developer edition ones.

onepoint said:
I tried this with the VZW imgs and now I get the unlocked bootloader warning. I don't recall getting that before, thoughts?
I assume it's because the imgs are not developer edition ones.
Click to expand...
Click to collapse
The unlocked warning is no big deal I get it on my 4.4.3 GSM Developer Edition.

onepoint said:
I tried this with the VZW imgs and now I get the unlocked bootloader warning. I don't recall getting that before, thoughts?
I assume it's because the imgs are not developer edition ones.
Click to expand...
Click to collapse
Nope, it's not. Likely, you had flashed a new logo.bin that "masked" the unlocked bootloader warning. Once again, the images are no different. Not one single byte different. None.
If you dislike (I like it, personally) the unlocked BL message, simply flash a replacement logo.bin.
See here for details: http://forum.xda-developers.com/moto-x/general/4-4-3-remove-unlocked-bootloader-message-t2548566
I realize that it says it is for 4.4.3, but it should be fully compatible with 4.4.4 as well.
And one more time: EVEN THE DEV EDITION shows the "unlocked bootloader message" when unlocked. Completely normal. Only flashing a replacement logo.bin will prevent it from showing up.

Related

[Q] Please help in unbricking Atrix HD MB886

Hi
I have been playing around with my Atrix HD for quite a while now, installing almost all custom roms out there for MB866 (Found Gummy and Carbon to be the best, batakang and holoblur never worked for me).
Restored back to stock using RSD Lite many times (after editing the xml file, no problems)
The bootloader was of course unlocked during "all that".
Now here is the problem. After restoring to stock 4.1.1 (98.4.20.MB886.ATT.en.US) using RSD Lite, I updated to 98.5.38.MB886.ATT.en.US (small 6.2 MB Update recently released).Worked fine till here.
Then I downgraded to ICS and it also worked fine. What made things worse was when I checked for updates via About Phone--> System Updates and it prompted for an Update 98.4.20.MB886.ATT.en.US (the same i used to flash via RSD). But when the download finished, the phone is permanently stuck in fastboot mode with the following message:
----------------------------------------------
AP Fastboot Flash Mode (s)
10.9B(*) (sha-2e68372, 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is LOCKED. Status Code:0
Battery OK
Transfer Mode: USB Connected
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read Failure
Invalid CID Status 0x69
No SP Partition found
Fastboot Reason: Invalid GPT
----------------------------------------------
You can see the phone is locked and RSD Lite doesent work at all giving "phone returmed fail" or " invalid partition error (battery is charged atleast 70%).
Any help in restoring the phone to "something" will be highly appreciated.
One of the problem is that i cannot find stock files for the latest 98.5.38.MB886.ATT.en.US update anywhere
Secondly is there any way to unlock Bootloader in fastboot?

capricorn85 said:
Hi
I have been playing around with my Atrix HD for quite a while now, installing almost all custom roms out there for MB866 (Found Gummy and Carbon to be the best, batakang and holoblur never worked for me).
Restored back to stock using RSD Lite many times (after editing the xml file, no problems)
The bootloader was of course unlocked during "all that".
Now here is the problem. After restoring to stock 4.1.1 (98.4.20.MB886.ATT.en.US) using RSD Lite, I updated to 98.5.38.MB886.ATT.en.US (small 6.2 MB Update recently released).Worked fine till here.
Then I downgraded to ICS and it also worked fine. What made things worse was when I checked for updates via About Phone--> System Updates and it prompted for an Update 98.4.20.MB886.ATT.en.US (the same i used to flash via RSD). But when the download finished, the phone is permanently stuck in fastboot mode with the following message:
----------------------------------------------
AP Fastboot Flash Mode (s)
10.9B(*) (sha-2e68372, 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is LOCKED. Status Code:0
Battery OK
Transfer Mode: USB Connected
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read Failure
Invalid CID Status 0x69
No SP Partition found
Fastboot Reason: Invalid GPT
----------------------------------------------
You can see the phone is locked and RSD Lite doesent work at all giving "phone returmed fail" or " invalid partition error (battery is charged atleast 70%).
Any help in restoring the phone to "something" will be highly appreciated.
One of the problem is that i cannot find stock files for the latest 98.5.38.MB886.ATT.en.US update anywhere
Secondly is there any way to unlock Bootloader in fastboot?
Click to expand...
Click to collapse
"fastboot oem fb_mode_clear" should get it to stop booting into fastboot mode
The problem is the gpt partition is security locked and one of the fastboot commands thrown is to lock the phone into fastboot mode for every boot until the flashes are done. The command above is the one used to revert the first one (fastboot oem fb_mode_set if you're curious). Your bootloader isn't, or shouldn't I should say, locked again. The RAZR HD does the same thing if you directly flash a fastboot without removing the bad partitions and commands for unlocked phones flashing non-stock fastboots. The bad ones are the gpt partition and the oem fb* commands....there are a lot of guides that explain this and Mythtools (in AHD Developer forums) will do it all for you.

skeevydude said:
"fastboot oem fb_mode_clear" should get it to stop booting into fastboot mode
The problem is the gpt partition is security locked and one of the fastboot commands thrown is to lock the phone into fastboot mode for every boot until the flashes are done. The command above is the one used to revert the first one (fastboot oem fb_mode_set if you're curious). Your bootloader isn't, or shouldn't I should say, locked again. The RAZR HD does the same thing if you directly flash a fastboot without removing the bad partitions and commands for unlocked phones flashing non-stock fastboots. The bad ones are the gpt partition and the oem fb* commands....there are a lot of guides that explain this and Mythtools (in AHD Developer forums) will do it all for you.
Click to expand...
Click to collapse
fastboot oem fb_mode_clear doesnt work, i tried it before as well, mythtools also cannt help as device status is locked and if rsd cannt flash it i believe myth also cannt.and the reason i say its locked is because it does not respond to any oem command.
it probably got locked after the ota which failed
if i could find fxz for 98.5.38.MB886.ATT.en.US, it may be restored otherwise is there any way around to unlock bootloder from fastboot??
these are the only two options i can think of amoungst which later is has the least probability.......

capricorn85 said:
fastboot oem fb_mode_clear doesnt work, i tried it before as well, mythtools also cannt help as device status is locked and if rsd cannt flash it i believe myth also cannt.and the reason i say its locked is because it does not respond to any oem command.
it probably got locked after the ota which failed
if i could find fxz for 98.5.38.MB886.ATT.en.US, it may be restored otherwise is there any way around to unlock bootloder from fastboot??
these are the only two options i can think of amoungst which later is has the least probability.......
Click to expand...
Click to collapse
There isn't an fxz for that update yet. The one I would be able to make wouldn't include the correct gpt partition because I've flashed the Nextel fxz and none of the other gpt partitions from our stock fxz's will flash on my phone (there's a security lock on that partition). Though I know that between two or three of us here on xda, an fxz could be made with all the correct partitions from the update.
If you're positive that you were unlocked then just flash the Bell or Nextel 4.1.2 fxz's. They're not vulnerable to the heartbleed exploit which is the main reason that AT&T released the 98.5 update to begin with.
Have you tried "fastboot continue"? You might get lucky and the phone will at least boot up. And tried booting to recovery? Boot menu?
You can only unlock the bootloader from a rooted, running phone with ADB enabled. Can't do it in recovery or fastboot mode (unless you have a developer edition).

skeevydude said:
There isn't an fxz for that update yet. The one I would be able to make wouldn't include the correct gpt partition because I've flashed the Nextel fxz and none of the other gpt partitions from our stock fxz's will flash on my phone (there's a security lock on that partition). Though I know that between two or three of us here on xda, an fxz could be made with all the correct partitions from the update.
If you're positive that you were unlocked then just flash the Bell or Nextel 4.1.2 fxz's. They're not vulnerable to the heartbleed exploit which is the main reason that AT&T released the 98.5 update to begin with.
Have you tried "fastboot continue"? You might get lucky and the phone will at least boot up. And tried booting to recovery? Boot menu?
You can only unlock the bootloader from a rooted, running phone with ADB enabled. Can't do it in recovery or fastboot mode (unless you have a developer edition).
Click to expand...
Click to collapse
i tried bell's 4.1.2 earlier thinking the same as you said,but didnt work either, wont boot to recovery or boot menu.....
fastboot continue also takes to the old prompt...

capricorn85 said:
i tried bell's 4.1.2 earlier thinking the same as you said,but didnt work either, wont boot to recovery or boot menu.....
fastboot continue also takes to the old prompt...
Click to expand...
Click to collapse
IIRC, the Nextel (Mex Retail) is the highest version we have unless the new AT&T one supersedes it.
I've only seen this issue one other time over at the RAZR HD forums. With the latest KK OTA they had, his failed and the phone booted to a similar screen you have. Nothing has worked for that guy yet that I'm aware of (haven't checked in about a week now).
Have you tried manually flashing an fxz, not with RSD or Myth (though Myth does flash manually via a script but it skips the gpt partition, IIRC). I'd start with the ATT fxz and if it fails manually then I'd flash the Nextel one...after that I'm out of ideas.

skeevydude said:
IIRC, the Nextel (Mex Retail) is the highest version we have unless the new AT&T one supersedes it.
I've only seen this issue one other time over at the RAZR HD forums. With the latest KK OTA they had, his failed and the phone booted to a similar screen you have. Nothing has worked for that guy yet that I'm aware of (haven't checked in about a week now).
Have you tried manually flashing an fxz, not with RSD or Myth (though Myth does flash manually via a script but it skips the gpt partition, IIRC). I'd start with the ATT fxz and if it fails manually then I'd flash the Nextel one...after that I'm out of ideas.
Click to expand...
Click to collapse
Came here after trying all that
Tried manually flashing but the phone returns FAIL on EVERY command, same with myth tools it executes but nothing really happen in the phone, dont know what went so wrong with the OTA
i am just confused if i should let it be or keep trying until i find a solution
COuld battery charge level be the problem, when it all started it was more than 70 percent and i didnt keep it on for long. it says battery ok but dont know whats the exact battery level as fastboot oem battery-status or voltage level are also restricted

Well, it seems that skeevydude told you all I want to say

Solved: Using Nextel (Mex Retail)
Thanks all for your replies
The device is alive now after restoring to Mexican Retail using RSD (editing the xml file and deleting ONLY the two lines having getvar)
Myth Tools never worked, RSD DID!
BTW the mexican retail is much much better than the ATT version because:
It gets rid of the ATT bloatware
SPecially the att address book
Hotspot is working out of the box
its speedier
android version is upgraded (4.1.2 instead of 4.1.1)
provides an option of manually switching to 2g/3g
and much more
thanks skeevydude, nextel was the last option remaining anyway...........and it automatically fixed the gpr issue

capricorn85 said:
Thanks all for your replies
The device is alive now after restoring to Mexican Retail using RSD (editing the xml file and deleting ONLY the two lines having getvar)
Myth Tools never worked, RSD DID!
BTW the mexican retail is much much better than the ATT version because:
It gets rid of the ATT bloatware
SPecially the att address book
Hotspot is working out of the box
its speedier
android version is upgraded (4.1.2 instead of 4.1.1)
provides an option of manually switching to 2g/3g
and much more
thanks skeevydude, nextel was the last option remaining anyway...........and it automatically fixed the gpr issue
Click to expand...
Click to collapse
Isn't it already stated somewhere that if you are going to downgrade or change versions, you need to delete those lines anyways?

palmbeach05 said:
Isn't it already stated somewhere that if you are going to downgrade or change versions, you need to delete those lines anyways?
Click to expand...
Click to collapse
Yes it is, but thats only for upgrade, if downgrading the gpt line also need to be deleted, as i was not downgrading, only those two were required to be deleted which need to be specifically mentioned to avoid confusion

capricorn85 said:
Yes it is, but thats only for upgrade, if downgrading the gpt line also need to be deleted, as i was not downgrading, only those two were required to be deleted which need to be specifically mentioned to avoid confusion
Click to expand...
Click to collapse
I told ya Mex Retail would work....

skeevydude said:
I told ya Mex Retail would work....
Click to expand...
Click to collapse
It is worth a shot for me too!
I have RSDLite and attempted to flash. It gives me error about unknown <getvar>. Deleted those line(s) according to another post I found.
Then everything passes but I am stuck on the Fastboot Flash Mode?
God I will be happy when uncle same gets through with my son so he can help is ole man, lol.
---------- Post added at 06:14 PM ---------- Previous post was at 05:55 PM ----------
PROGRESS! I recalled skeevydude saying to stay alway from front USB ports and moved to back one and I now also have the Mex Retail version working. What a relief.
Now the bearing question is should I move on to another version like carbon or holoblur?
If ok to stay with this version, meaning will NOT get busted out by AT&T by using hotspot?
What do you recommend skeevydude?
Thank you so so so much.
Woody

Mexico Retail link
can someone provide me any link of Mexico Retail stock rom? Please.

ErickST18 said:
can someone provide me any link of Mexico Retail stock rom? Please.
Click to expand...
Click to collapse
http://sbf.droid-developers.org/phone.php?device=7

quasihellfish said:
http://sbf.droid-developers.org/phone.php?device=7
Click to expand...
Click to collapse
Thanks man

Pleas hlep me for alive my set thanks advance
dear i have a working phone MB886 with jellybean 4.1.1 unfortunately i flash the custom ROM of kitkat but set is dead i tired to alive the phone with myth tools rsd lite but no success my phone boot-loader locked i try to unlock the boot loader but nothing please anybody send ma working link of flash file Mexican or any other which are flash with rsd lite easily i am very thankful of that plzzzzzzzzzzz customer on my neck sorry for my bad English

shamshadhashmi said:
dear i have a working phone MB886 with jellybean 4.1.1 unfortunately i flash the custom ROM of kitkat but set is dead i tired to alive the phone with myth tools rsd lite but no success my phone boot-loader locked i try to unlock the boot loader but nothing please anybody send ma working link of flash file Mexican or any other which are flash with rsd lite easily i am very thankful of that plzzzzzzzzzzz customer on my neck sorry for my bad English
Click to expand...
Click to collapse
Please stop whining and being pathetic and actually search for moto sbf files. A new site popped up and comes up very easily. No need to make us die of laughter at someone begging for an sbf like a guy begging to get with a girl b/c he's thirsty. Smh lol
Sent from my ATRIX HD using XDA Free mobile app

need working link of file
i search everywhere but no file found i need file if anybody have so please share with me or upload thanks

quasihellfish said:
http://sbf.droid-developers.org/phone.php?device=7
Click to expand...
Click to collapse
Need 4.1.1..where can I find it? Tyvm

[Q] Locked/Unrooted Phone Decided to Brick Itself

I'm not entirely sure how to troubleshoot this problem, but here goes...
I was charging my phone and it just attempted to reboot itself. I saw it in the corner of my eye and figured "oh well, let it finish". It never finished, and it seems it won't get past the boot screen.
I entered Fastboot mode. Device is still locked. It also states that the charger is connected, regardless of whether it is or isn't. Additionally, I cannot access Recovery or Factory, instead receiving the following error:
No valid PIV block in SP for system
piv validation failed (system)
Boot up failed
Click to expand...
Click to collapse
Anyone know what's going on here? Did my phone really just brick itself?
Edit: I apologize if my first post goes against any of the rules here. I've searched for a similar thread, but mostly found cases in which people failed to root and are receiving this message. I have some minor experience with rooting a Motorola Droid, Verizon Droid Incredible 2 and a Nexus 10. I was hoping to do the same with this phone, but it came with 4.4.2 already installed.

Don't take my word for it, but if you Google no valid piv moto x....it doesn't look good.
Then again if you read through some of the stuff you find, even other phones with issue....perhaps you'll stumble on a fix.
Last moto x thread I read with that error was solved by a replacement unfortunately.
Hope you find a fix, or can send it in. Your warranty should be in tact if its locked and unrooted.

As kj mentioned, seek a replacement under warranty. If you are really looking to fix yourself. Unlock the bootloader and flash the latest stock ROM via fastboot.
I'd only try that if you can't get a warranty replacement cause unlocking the boot loader will kill your warranty unless you have a Dev edition

SymbioticGenius said:
As kj mentioned, seek a replacement under warranty. If you are really looking to fix yourself. Unlock the bootloader and flash the latest stock ROM via fastboot.
I'd only try that if you can't get a warranty replacement cause unlocking the boot loader will kill your warranty unless you have a Dev edition
Click to expand...
Click to collapse
He doesn't need to unlock his bootloader to try to fastboot flash the lastest stock rom...
The Stock rom will flash just fine even locked because it's signed with release keys.
Try it!

samwathegreat said:
He doesn't need to unlock his bootloader to try to fastboot flash the lastest stock rom...
The Stock rom will flash just fine even locked because it's signed with release keys.
Try it!
Click to expand...
Click to collapse
Thanks! I was hesitant to flash anything on this phone because I read people who had 4.4.2 were at risk of bricking their phones... but now that you've said it, it feels so obvious. I'll give this a try. Is there a standard go-to place for the stock ROM?

ed0421 said:
Thanks! I was hesitant to flash anything on this phone because I read people who had 4.4.2 were at risk of bricking their phones... but now that you've said it, it feels so obvious. I'll give this a try. Is there a standard go-to place for the stock ROM?
Click to expand...
Click to collapse
You can find the sbf files (stock rom) here: http://sbf.droid-developers.org/phone.php?device=0
If you were on 4.4.2 before you bricked MAKE SURE you flash the 4.4.2 rom, and not a previous version.
Also remember that aside from a BL unlock, there will be no way of obtaining ROOT after this.
Download the correct file for your carrier and try to flash with RSD lite. Let us know what happens.
EDIT:
You can find a great guide here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Now that guide was made before 4.4.2 so it doesn't warn you not to flash a previous version. You've been warned... If you flash a pre-4.4.2 rom, you'll likely be perma-bricked.
Anyways, try the RSD Lite method. PAY CLOSE ATTENTION TO STEP 4 - editing the xml file
If for some reason that doesn't work, let us know what carrier you are on and we can help you with manual flashing commands for your specific carrier.
Since you ARE able to get into fastboot mode, I'm hopeful that this may work for you.
And finally, if you have problems with RSD lite, make SURE you have the USB drivers installed, and try another USB port if necessary.
Good Luck.

samwathegreat said:
You can find the sbf files (stock rom) here: http://sbf.droid-developers.org/phone.php?device=0
If you were on 4.4.2 before you bricked MAKE SURE you flash the 4.4.2 rom, and not a previous version.
Also remember that aside from a BL unlock, there will be no way of obtaining ROOT after this.
Download the correct file for your carrier and try to flash with RSD lite. Let us know what happens.
EDIT:
You can find a great guide here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Now that guide was made before 4.4.2 so it doesn't warn you not to flash a previous version. You've been warned... If you flash a pre-4.4.2 rom, you'll likely be perma-bricked.
Anyways, try the RSD Lite method. PAY CLOSE ATTENTION TO STEP 4 - editing the xml file
If for some reason that doesn't work, let us know what carrier you are on and we can help you with manual flashing commands for your specific carrier.
Since you ARE able to get into fastboot mode, I'm hopeful that this may work for you.
And finally, if you have problems with RSD lite, make SURE you have the USB drivers installed, and try another USB port if necessary.
Good Luck.
Click to expand...
Click to collapse
Hey, thanks for the effort! Unfortunately, it looks like my phone is completely bricked. I tried with RSD Lite, after making sure to edit the XML, and it failed when trying to flash the first file. "Failed flashing process. 2/17 flash parition "gpt.bin" -> Phone returned FAIL."
Figured I'd try with fastboot, and no luck there either.
Code:
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.978s
Looks like I'm gonna have to use my warranty. Thanks for taking the time to reply, though!

I didn't have the same issue but I did just RMA my X for another reason and got a brand new 2014 X, was expecting a refurbished phone and was surprised to get a new one. They shipped it next day air that same day which also surprised me.

ed0421 said:
Hey, thanks for the effort! Unfortunately, it looks like my phone is completely bricked. I tried with RSD Lite, after making sure to edit the XML, and it failed when trying to flash the first file. "Failed flashing process. 2/17 flash parition "gpt.bin" -> Phone returned FAIL."
Figured I'd try with fastboot, and no luck there either.
Code:
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.978s
Looks like I'm gonna have to use my warranty. Thanks for taking the time to reply, though!
Click to expand...
Click to collapse
Usually (not always) when it errors out on gpt.bin, its because you're trying to flash a pre-4.4.2 image.
Hate to ask, but are you absolutely sure you downloaded the 4.4.2 rom?
And when you tried the manual method....you are executing the commands one at a time, right? Which part does it fail on? Flashing recovery? Because I see an error right above it - something about failed to erase....but erase what?
Good luck with your exchange if you must send it back...
-samwathegreat

samwathegreat said:
Usually (not always) when it errors out on gpt.bin, its because you're trying to flash a pre-4.4.2 image.
Hate to ask, but are you absolutely sure you downloaded the 4.4.2 rom?
And when you tried the manual method....you are executing the commands one at a time, right? Which part does it fail on? Flashing recovery? Because I see an error right above it - something about failed to erase....but erase what?
Good luck with your exchange if you must send it back...
-samwathegreat
Click to expand...
Click to collapse
100% certain I downloaded the 4.4.2 rom, unfortunately. Flashing manually, it fails from the very first flash attempt. Only setting the oem fb_mode_set goes through without failure. Thanks for your help throughout this whole ordeal, it's very much appreciated

ed0421 said:
100% certain I downloaded the 4.4.2 rom, unfortunately. Flashing manually, it fails from the very first flash attempt. Only setting the oem fb_mode_set goes through without failure. Thanks for your help throughout this whole ordeal, it's very much appreciated
Click to expand...
Click to collapse
Really dumb question but when flashing... Are you using the command fastboot or mfastboot?
I had all kinds of errors and thought I was bricked too until I used mfastboot. Then everything went perfect. Moto uses their own version of fastboot.exe that's included in the sbf/fxz or whatever they are called now. Even the XML file states fastboot as the command but never worked for me. Just a thought.

Expert opinion needed in going back to Stock

Hi Guys,
I am in a bit of a problem. My Moto X has unlocked bootloader and rooted with custom recovery (twrp). So i can't update to 4.4.4 from OTA so i want to unroot and lock my bootloader (going back to everything stock).
I tried this method but it failed at first two steps.
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot oem lock
i recommend wiping your device also but that is up to you if you dont want
to then skip the next two commands and just type the reboot command
fastboot erase userdata
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
The firmware which i am trying to install is:
"Android 4.4.2 Blur_Version.161.44.32.ghost_sprint.Sprint.en.US ghost_sprint-user-4.4.2-KXA20.16-1.32-37-release-keys-cid9.xml"
My fastboot/bootloader with the error i am getting along with My phone information is attached below.
Need your help what should i do now.

Usama Ahmed said:
Hi Guys,
I am in a bit of a problem. My Moto X has unlocked bootloader and rooted with custom recovery (twrp). So i can't update to 4.4.4 from OTA so i want to unroot and lock my bootloader (going back to everything stock).
I tried this method but it failed at first two steps.
The firmware which i am trying to install is:
"Android 4.4.2 Blur_Version.161.44.32.ghost_sprint.Sprint.en.US ghost_sprint-user-4.4.2-KXA20.16-1.32-37-release-keys-cid9.xml"
My fastboot/bootloader with the error i am getting along with My phone information is attached below.
Need your help what should i do now.
Click to expand...
Click to collapse
You should NOT re-lock the bootloader. Leave it unlocked. The phone will update just fine with unlocked BL. Just flash back to stock (what ever version you have on the phone now), then take the new OTA update.
Afterwards you can re-root if you want to.
Once again: You do NOT need to lock the BL - for any reason.
EDIT: Just looked at your pictures. Your phone is in BAD shape -- you should have never attempted to downgrade. This will be difficult to recover. I suggest asking for help in the "debricking" thread in the General sub-forum.
Good Luck.
It looks to me like you WERE on the 4.4.4 or above bootloader, and you flashed just the 4.4.2 system and boot.img at some point. Now, going back to full 4.4.2, you have downgraded the Bootloader and partition table. That is a no-no.

samwathegreat said:
You should NOT re-lock the bootloader. Leave it unlocked. The phone will update just fine with unlocked BL. Just flash back to stock (what ever version you have on the phone now), then take the new OTA update.
Afterwards you can re-root if you want to.
Once again: You do NOT need to lock the BL - for any reason.
EDIT: Just looked at your pictures. Your phone is in BAD shape -- you should have never attempted to downgrade. This will be difficult to recover. I suggest asking for help in the "debricking" thread in the General sub-forum.
Good Luck.
It looks to me like you WERE on the 4.4.4 or above bootloader, and you flashed just the 4.4.2 system and boot.img at some point. Now, going back to full 4.4.2, you have downgraded the Bootloader and partition table. That is a no-no.
Click to expand...
Click to collapse
I have bought the phone in this shape so i don't know what the previous owner did to it. What if i use donot touch bootloader but just use Super SU (Full Unroot) option to unroot and flash stock recovery img from "ghost_sprint-user-4.4.2-KXA20.16-1.32-37-release-keys-cid9.xml" file, then will i be able to install OTA update of 4.4.4?

Usama Ahmed said:
I have bought the phone in this shape so i don't know what the previous owner did to it. What if i use donot touch bootloader but just use Super SU (Full Unroot) option to unroot and flash stock recovery img from "ghost_sprint-user-4.4.2-KXA20.16-1.32-37-release-keys-cid9.xml" file, then will i be able to install OTA update of 4.4.4?
Click to expand...
Click to collapse
Don't take the OTA. Just try to flash the full 4.4.4 SBF!
You can find the full 4.4.4 Sprint SBF at one of the links here: http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347

samwathegreat said:
Don't take the OTA. Just try to flash the full 4.4.4 SBF!
You can find the full 4.4.4 Sprint SBF at one of the links here: http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347
Click to expand...
Click to collapse
Ok i am getting a little scared right now. I don't want to brick my device. I have found one firmware which i think should be okay to go with.
ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip
Do you think i should go with it? Is their any chance of getting bricked? I have posted my system information picture above so you can see if it will be compatible with it.

Usama Ahmed said:
Ok i am getting a little scared right now. I don't want to brick my device. I have found one firmware which i think should be okay to go with.
ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip
Do you think i should go with it? Is their any chance of getting bricked? I have posted my system information picture above so you can see if it will be compatible with it.
Click to expand...
Click to collapse
The previous owner has left you with mismatched partitions. This state is known to be at risk of bricking....
Your safest option is to attempt to flash the 4.4.4 SBF (yes you linked the right file), but even this is not without risk. It might work perfectly fine, and you might end up having to de-brick it.
Wish I could give you a more definite answer, but anything other than flashing the full 4.4.4 SBF is very dangerous. Even flashing the entire 4.4.4 SBF has some risk.
Good Luck.

samwathegreat said:
The previous owner has left you with mismatched partitions. This state is known to be at risk of bricking....
Your safest option is to attempt to flash the 4.4.4 SBF (yes you linked the right file), but even this is not without risk. It might work perfectly fine, and you might end up having to de-brick it.
Wish I could give you a more definite answer, but anything other than flashing the full 4.4.4 SBF is very dangerous. Even flashing the entire 4.4.4 SBF has some risk.
Good Luck.
Click to expand...
Click to collapse
Thanks alot for your help. If you think there is even a slight chance of hard brick than i will stay with the current rom i have.
One last question, I you were in my position, would you go for flashing 4.4.4 SBF or would you just leave it as it is?

Usama Ahmed said:
Ok i am getting a little scared right now. I don't want to brick my device. I have found one firmware which i think should be okay to go with.
ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip
Do you think i should go with it? Is their any chance of getting bricked? I have posted my system information picture above so you can see if it will be compatible with it.
Click to expand...
Click to collapse
@samwathegreat is correct. You are trying to downgrade, hence the errors and problems. The key here is the screen shot of AP Fastboot, where the second line shows 30.B7 which is the bootloader for 4.4.4. So at this point, you only want to flash a 4.4.4 SBF, and never flash anything lower.
That does appear to be the correct 4.4.4 if you have a 2013 or First Gen... Sprint X.
I suggest you flash using mFastboot with the extra steps as listed in Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html However, if you are unsuccessful doing that, then you're going to need to visit the Unbricking thread and see if that can help you get fixed up.

KidJoe said:
@samwathegreat is correct. You are trying to downgrade, hence the errors and problems. The key here is the screen shot of AP Fastboot, where the second line shows 30.B7 which is the bootloader for 4.4.4. So at this point, you only want to flash a 4.4.4 SBF, and never flash anything lower.
That does appear to be the correct 4.4.4 if you have a 2013 or First Gen... Sprint X.
I suggest you flash using mFastboot with the extra steps as listed in Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html However, if you are unsuccessful doing that, then you're going to need to visit the Unbricking thread and see if that can help you get fixed up.
Click to expand...
Click to collapse
Hi KidJoe! Thanks for your reply. What can i post to confirm if i have chosen the right SBF for my phone (Yes it is Moto X First-Gen).
This is the file i am downloading right now. "ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip"
And if i flash it with what you mentioned, is their a chance of bricking my device?
BTW i try to flash "ghost_sprint-user-4.4.2-KXA20.16-1.32-37-release-keys-cid9.xml" with the same method you posted which resulted in error due to the problem you mentioned above.

Usama Ahmed said:
Hi KidJoe! Thanks for your reply. What can i post to confirm if i have chosen the right SBF for my phone (Yes it is Moto X First-Gen).
This is the file i am downloading right now. "ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip"
And if i flash it with what you mentioned, is their a chance of bricking my device?
Click to expand...
Click to collapse
Your first screen shot in Post 1 shows your phone has 161.44.32.ghost_sprint.Sprint.en.US. In other words, Sprint rom. So you should be able to flash the Sprint 4.4.4 you found.
Ideally you want to look at the FINE PRINT on the bottom of the back of the phone. It will have a model, like XT1056, XT1060, XTT1049, XT1053, etc. The other option, if you have the original box, check the label on the end of it. If the IMEI number printed on the label, matches what phone shows in its menus, then that label on the box should also tell you the model (the box for my Verizon X has MOTXT1060DEV on the bar code label.), Since you got yours used, its VERY important you confirm that is the original box when trying to use the box to confirm the model number!
As for risks of bricking... well, that is an unknown. There have been MANY bricks caused when users got them selves into the situation your phone is in. There is no 100% risk free process to try and recover. And that is why there are so many warnings telling people to NOT DOWN GRADE!!!
What I'm suggesting has worked, but you are correct, there is still a chance to brick. Taking an OTA in the state your phone is in also has a risk of bricking. Anything you try and do at this point also have a risk of bricking.
Usama Ahmed said:
BTW i try to flash "ghost_sprint-user-4.4.2-KXA20.16-1.32-37-release-keys-cid9.xml" with the same method you posted which resulted in error due to the problem you mentioned above.
Click to expand...
Click to collapse
Yes. The phone will ERROR if you try to flash an older GPT.BIN which is what you are encountering. (bootloader version indicates you had 4.4.4 on your phone, including its GPT.BIN and Bootloader).
The problem is this...
The Phone's previous owner had a FULL 4.4.4 ROM flashed to the phone. They attempted to downgrade. Since GPT.BIN and MOTOBOOT.IMG can not be downgraded, they did only PARTS!! Now the phone has mismatched bootloader, partition table and other parts compared to the older "System" and such which are installed.

KidJoe said:
Your first screen shot in Post 1 shows your phone has 161.44.32.ghost_sprint.Sprint.en.US. In other words, Sprint rom. So you should be able to flash the Sprint 4.4.4 you found.
Ideally you want to look at the FINE PRINT on the bottom of the back of the phone. It will have a model, like XT1056, XT1060, XTT1049, XT1053, etc. The other option, if you have the original box, check the label on the end of it. If the IMEI number printed on the label, matches what phone shows in its menus, then that label on the box should also tell you the model (the box for my Verizon X has MOTXT1060DEV on the bar code label.), Since you got yours used, its VERY important you confirm that is the original box when trying to use the box to confirm the model number!
As for risks of bricking... well, that is an unknown. There have been MANY bricks caused when users got them selves into the situation your phone is in. There is no 100% risk free process to try and recover. And that is why there are so many warnings telling people to NOT DOWN GRADE!!!
What I'm suggesting has worked, but you are correct, there is still a chance to brick. Taking an OTA in the state your phone is in also has a risk of bricking. Anything you try and do at this point also have a risk of bricking.
Yes. The phone will ERROR if you try to flash an older GPT.BIN which is what you are encountering. (bootloader version indicates you had 4.4.4 on your phone, including its GPT.BIN and Bootloader).
The problem is this...
The Phone's previous owner had a FULL 4.4.4 ROM flashed to the phone. They attempted to downgrade. Since GPT.BIN and MOTOBOOT.IMG can not be downgraded, they did only PARTS!! Now the phone has mismatched bootloader, partition table and other parts compared to the older "System" and such which are installed.
Click to expand...
Click to collapse
The model no written on back is XT1056. Just to be sure i have also attached the picture below. I am currently downloading "ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip".
Should i go for all these cmds?
mfastboot getvar max-download-size
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot reboot
Click to expand...
Click to collapse
Also in this process, is their chance of my phone dead?
Will these cmds also lock my bootloader or should i just leave it unlocked? As currently my phone has unlocked bootloader and is rooted.
A step by step (maximum safe steps) for flashing would be greatly appreciated.

Usama Ahmed said:
The model no written on back is XT1056. Just to be sure i have also attached the picture below. I am currently downloading "ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip".
Should i go for all these cmds?
Also in this process, is their chance of my phone dead?
Will these cmds also lock my bootloader or should i just leave it unlocked? As currently my phone has unlocked bootloader and is rooted.
A step by step (maximum safe steps) for flashing would be greatly appreciated.
Click to expand...
Click to collapse
XT1056 is Sprint. So ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip is the right ROM to use.
use EVERY COMMAND AS STATED in the link. If successful, all parts will be back in line, and consistent.
As I said, yes there is a chance you can brick your phone. Many other things can brick your phone while you are in this state too. There is no 100% "Safe" and "guaranteed to not brick your phone" process when you are in this state.
This process will NOT lock your bootloader. And samwathegreat already told you there is no need to re-lock it.

KidJoe said:
XT1056 is Sprint. So ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip is the right ROM to use.
use EVERY COMMAND AS STATED in the link. If successful, all parts will be back in line, and consistent.
As I said, yes there is a chance you can brick your phone. Many other things can brick your phone while you are in this state too. There is no 100% "Safe" and "guaranteed to not brick your phone" process when you are in this state.
This process will NOT lock your bootloader. And samwathegreat already told you there is no need to re-lock it.
Click to expand...
Click to collapse
Ok then i will be trying it right now and see what happens.

Thanks alot to @samwathegreat and @KidJoe. I have successfully updated my Moto X to 4.4.4 KitKat. I hope it had solved mismatched bootloader, partition table and other parts as mentioned by @KidJoe.
Attachment of process is below.

Usama Ahmed said:
Thanks alot to @samwathegreat and @KidJoe. I have successfully updated my Moto X to 4.4.4 KitKat. I hope it had solved mismatched bootloader, partition table and other parts as mentioned by @KidJoe.
Attachment of process is below.
Click to expand...
Click to collapse
Screen shot starts when system.img is flashing, so as long as the commands above that were also done and didn't error out, you are good!

Excellent support here! @samwathegreat and @KidJoe are GREAT!

KidJoe said:
Screen shot starts when system.img is flashing, so as long as the commands above that were also done and didn't error out, you are good!
Click to expand...
Click to collapse
Sorry i didn't realize that. Yes everything part was flashed without error otherwise i wouldn't go further.

But i am in a new problem now. My sim card is not working now. It says "Your SIM card does not allow a connection to this network". If anyone can help regarding that or if i can flash something to make it work.

Usama Ahmed said:
But i am in a new problem now. My sim card is not working now. It says "Your SIM card does not allow a connection to this network". If anyone can help regarding that or if i can flash something to make it work.
Click to expand...
Click to collapse
it appears you're not using sprint as your carrier... So You may now have to run this process to SIM unlock -> http://forum.xda-developers.com/moto-x/general/guide-success-sim-unlock-sprint-xt1056-t2825155

KidJoe said:
it appears you're not using sprint as your carrier... So You may now have to run this process to SIM unlock -> http://forum.xda-developers.com/moto-x/general/guide-success-sim-unlock-sprint-xt1056-t2825155
Click to expand...
Click to collapse
Yes i am not using sprint as my carrier. Thanks alot for the help again. I will try this now and post the result.

[Q] REPUBLIC XT1049 Custom ROMs

I have a Republic Wireless Moto x (XT1049) with an unlocked bootloader, and knowing how rare it is (literally 0 support on any thread/site/country), I'm still going to ask a few questions, maybe start a band of RWers with unlocked Moto Xs that will only survive by sticking together/cuddling for warmth.
Before anyone starts to disbelieve me, I do have an xt1049 (not confusing it) with an unlocked bootloader (not confusing it with simply being rooted). I achieved this by purchasing a $25 license for SunShine by the jcase crew, and it worked wonderfully for whoever is out there, looking to unlock you xt1049. Why did I want to fork out 25 bucks for this? I started to hate the grind with towelpieroot+xposed every time I turned my device on, plus things like Viper4Android (among others) don't work well with temp roots, plus no write protection off, which has its purposes.
So on to my questions, (1) are there any custom ROMs designed for XT1049? (Probably no, so before you tell me no, (1a) are there any that work with my model?)
(2) If no one knows 1 or 1a, theoretically, what would happen if I flashed a ROM, say, CM 11/12, onto my phone? Please, to avoid a clutter of responses that consist of "idk probs no," have some level of confidence before answering.
For the theorists, Republic has a bunch of republic things going on in the background for the plural wifis to work correctly, how would these services (wifi calling/stuff) be affected, but also how would more universal things (moto x line specifically, but universal across carriers)? I don't know a whole lot about carriers because I have a serious phobia of letter combinations like CDMA and LTE, but to help understanding the "universal things" I mentioned, looking at the CM11 download page, one ZIP file can be used to flash the XT1053, XT1056, XT1058, XT1060, XT1055, you get the point. OK you got me, to refine it down,(3) I'm just trying to get a complete understanding of what would happen without trying it. I might/probably/would try it some other day, I have a load of college on my plate so if I have to undo anything (another question: (4) would I be able to revert to republic stuff if I have the correct zip, or what would have to go wrong so that I wouldn't be able to get to my bootloader/recovery?) I don't pay my phone bill, and my pops would be pissed if he read this so that's why I might not want to test it, but if there is a way to return I will be ballsy anyway.
(5) A question that I've had for a while but I never needed it answered, bootloaders remain unlocked after an update, right? My old phone (RIP HTC design 4g ) lost support at 4.2 and I never updated it the entire time it was rooted/unlocked. My moto on the other hand has 4.4.4 coming out soon and yeah I don't know the answer to it. I think it's implied it stays unlocked, but no one ever says it directly...
Well, thanks if you made it this far! And I would link whatever I could but I am a new user to this site and I'm restricted, you can just look up Sunshine jcase if interested.

Hi, this is my first time posting on xda, so I apologize ahead of time if I don't do it correctly. I'm also very interested in what can be done with a Republic Wireless Moto X (2013) in order to update to 4.4.4 and still be able to use TowelPieRoot and Xposed. I also looked at the SunShine unlocker but have not tried it yet. I'm currently on 4.4.2 and I just go the update notification today for 4.4.4 (much later than my wife's phone, which does not have TowelPieRoot or Xposed). Just wondering if you had any success with updating and still remaining unlocked and able to use TowelPieRoot and Xposed. Thanks for any feedback!

Unlocked boot loader...
Today I unlocked the boot loader on my Republic Wireless XT1049, since they were trying to force me to upgrade to android 4.4.4 from 4.4.2, and I realized that running Sunshine on 4.4.2 would be my last opportunity for unlocking the boot loader, before upgrading. I haven't yet rooted or updated to 4.4.4. Have either of you upgraded to 4.4.4 android with an uplocked boot loader, and re-rooted? Is there anything different about root in 4.4.4 vs 4.4.2, if you have an unlocked boot loader? Would the "Rooting Unlocked Bootloader" instructions in this guide work in android 4.4.2 and/or 4.4.4? Or, would Sunshine SUInstaller make that unnecessary? (Hopefully SUInstaller would work in 4.4.4...)

I'm on 4.4.2 with an unlocked bootloader from when the china man was giving out unlock codes. Having my code guarantees that I can unlock my bootloader even after locking it again for an update. I'm not sure how Sunshine works but be careful before taking the 4.4.4. update and do lots of research before doing anything to your device.
To answer some questions:
CM11 and CM12 will flash fine. The problem you'll have is a loss of phone functionality. With Republic, their app is baked into their custom ROM. But you can use it like a tablet and get a feel for what lollipop will look like on our phone. Make sure you have a nandroid backup or you'll lose everything. CM11 requires a wipe before it will install and CM12 requires you have CM11 (at least it did the last I checked) so you'll want to make sure you have a backup so you can get your working RW ROM back. Otherwise you'll have to flash the Stock RW ROM and start from scratch.
I've done lots of digging and have been able to get the Republic app working on CM11 and CM12 but the functionality is still missing. My tweaks allow texts on CM11 but it's from the "hidden number" not the RW number and the formatting is messed up upon receiving a message. Calls don't work at all on either ROM.
I posted a thread in General with my instructions to get the app working. I'm hoping someone with more ROM knowledge than myself can take a look at the RW Stock ROM and see what else needs to be moved into a CM ROM to give us functionality. I tried moving everything over and skipping duplicates and now I've seriously messed my phone up and will likely have to relock, unlock, flash TWRP and hope I can restore from my TWRP backup.
I've only tried CM11 and CM12, I have no idea how another ROM will affect our phone. Chances are you'll end up in an endless boot after flashing. You could brick the phone though, or end up in a situation like I'm currently in.

bstevens23 said:
I'm on 4.4.2 with an unlocked bootloader from when the china man was giving out unlock codes. Having my code guarantees that I can unlock my bootloader even after locking it again for an update. I'm not sure how Sunshine works but be careful before taking the 4.4.4. update and do lots of research before doing anything to your device.
Click to expand...
Click to collapse
Thanks for the warning about upgrading. I still haven't decided to allow my phone to upgrade to 4.4.4 android, but the most immediate issue I face with not upgrading is that my phone automatically downloaded the update, and now it is incessantly prompting me to install it. I have found any way to stop the annoying prompting. I would rather wait before updating, because there are always details you don't know about such upgrades, and I have no pressing need for the upgrade, except that ultimately I would like to be able to root my phone, also allow for writing to the system partition, so that recording calls would be possible.
You raise a good point in mentioning your capability to lock and unlock the boot loader. As far as I know Sunshine only unlocks the boot loader. I haven't seen that it provides any code or other means for re-locking it. It is also my understanding that technically there are 3 possible locking states of the boot loader. The factory state not only being locked but also indicating that it was never unlocked. It's my understanding that once a boot loader is unlocked, it can be re-locked, but never restored to the factory locked state that indicates it was never unlocked. That said, I don't know whether it matters if the boot loader is unlocked when running the Republic Wireless upgrade. In other threads I had read claims that once a boot loader is unlocked, that it should remain unlocked after OS upgrades, and as such, in a state that would allow for rooting. But, I am far from an expert on that.
bstevens23 said:
To answer some questions:
CM11 and CM12 will flash fine. The problem you'll have is a loss of phone functionality. With Republic, their app is baked into their custom ROM. But you can use it like a tablet and get a feel for what lollipop will look like on our phone. Make sure you have a nandroid backup or you'll lose everything. CM11 requires a wipe before it will install and CM12 requires you have CM11 (at least it did the last I checked) so you'll want to make sure you have a backup so you can get your working RW ROM back. Otherwise you'll have to flash the Stock RW ROM and start from scratch.
I've done lots of digging and have been able to get the Republic app working on CM11 and CM12 but the functionality is still missing. My tweaks allow texts on CM11 but it's from the "hidden number" not the RW number and the formatting is messed up upon receiving a message. Calls don't work at all on either ROM.
I posted a thread in General with my instructions to get the app working. I'm hoping someone with more ROM knowledge than myself can take a look at the RW Stock ROM and see what else needs to be moved into a CM ROM to give us functionality. I tried moving everything over and skipping duplicates and now I've seriously messed my phone up and will likely have to relock, unlock, flash TWRP and hope I can restore from my TWRP backup.
I've only tried CM11 and CM12, I have no idea how another ROM will affect our phone. Chances are you'll end up in an endless boot after flashing. You could brick the phone though, or end up in a situation like I'm currently in.
Click to expand...
Click to collapse
I hope there will be others who are willing to collaborate in your endeavors to reverse engineer the ROM that you are working on. Are you pursuing that because nobody has been able to root a Republic Wireless XT1049 on android 4.4.2 with a ROM? It seems that the original poster found some way to root 4.4.2 with his unlocked boot loader. I would be interest to know how he did that.

gxdaspark said:
Thanks for the warning about upgrading. I still haven't decided to allow my phone to upgrade to 4.4.4 android, but the most immediate issue I face with not upgrading is that my phone automatically downloaded the update, and now it is incessantly prompting me to install it. I have found any way to stop the annoying prompting. I would rather wait before updating, because there are always details you don't know about such upgrades, and I have no pressing need for the upgrade, except that ultimately I would like to be able to root my phone, also allow for writing to the system partition, so that recording calls would be possible.
You raise a good point in mentioning your capability to lock and unlock the boot loader. As far as I know Sunshine only unlocks the boot loader. I haven't seen that it provides any code or other means for re-locking it. It is also my understanding that technically there are 3 possible locking states of the boot loader. The factory state not only being locked but also indicating that it was never unlocked. It's my understanding that once a boot loader is unlocked, it can be re-locked, but never restored to the factory locked state that indicates it was never unlocked. That said, I don't know whether it matters if the boot loader is unlocked when running the Republic Wireless upgrade. In other threads I had read claims that once a boot loader is unlocked, that it should remain unlocked after OS upgrades, and as such, in a state that would allow for rooting. But, I am far from an expert on that.
Click to expand...
Click to collapse
I have yet to update to 4.4.4 because I've heard of people having problems with Messenger after the update. I'm waiting to see how my wife's phone functions on it before I make the leap and get the stock recovery back to take the OTA. Until then, I get the obnoxious update warning constantly as well. I could probably freeze the app with Titanium, we'll see if it bothers me enough in the next few days. I'm not sure if the bootloader will need to change for the update as I've only ever had 4.4.2 since I was bootloader unlocked. I know flashing the stock recovery is needed and I feel like that may require a relocked bootloader. As far as I know, from a software/OTA side at least, relocked and locked are equal. Republic/Moto would care about relocked but I don't think the system throws any flags for taking stock software updates because of it.
I hope there will be others who are willing to collaborate in your endeavors to reverse engineer the ROM that you are working on. Are you pursuing that because nobody has been able to root a Republic Wireless XT1049 on android 4.4.2 with a ROM? It seems that the original poster found some way to root 4.4.2 with his unlocked boot loader. I would be interest to know how he did that.
Click to expand...
Click to collapse
I'm pursuing this because I want CM12 to test out Lollipop since I have no idea when Republic is going to push it out to us. I haven't heard of Sprint getting soak tests yet and we're typically 2-3 months behind Sprint. Waiting until May when Google I/O takes place will be difficult for me, especially if they break their current trend and announce the next version of Android.
My goal is much more ambitious than just CM12 though. I got the Republic app to recognize CM11 as native, meaning if someone can figure out which radio portions I'm missing and get the phone functioning as if it were the Republic ROM, we would not be restricted to just the stock ROM/software anymore. I've been an Android user for a few years now and I've always had the ability to flash whatever I wanted if it was available for my device. Since joining RW, I'm extremely restricted. I have 1 ROM option, which is only helpful because it allows Xposed. But I no longer have the ability to test the newest version of Android whenever I please, or to give a custom ROM a spin if I feel like it. If we can figure out what makes the RW ROM function properly, that wouldn't be a restriction anymore. That's my goal.
Unfortunately, I have no idea what I'm doing. The best I can do is compare files and try pulling random things. I'm hoping someone with more ROM knowledge will be able to take a look at the RW ROM and see which pieces I'm missing. I feel like CM12 is going to be a bit more complicated though, and might not be possible at this time. We'll see though. I know something is getting screwed up with the MEID because the Republic app doesn't recognize an MEID at all. How to go about fixing that? Beyond me.

step-by-step, 4.4.4 root
I think the steps would be: first Sunshine, then 4.4.4 OTA, then root, then Xposed. Is that correct? After I unlock with Sunshine, will my phone still prompt me to update to 4.4.4? Or do I need to need to download 4.4.4 and then flash it? After Sunshine, do I FIRST need to flash 4.4.2 custom recovery? If so, where can I get that? I should probably get a copy of that anyway, even if I don't need it now.
It seems pretty easy overall, but I think I need to refer to a step-by-step guide to make sure I do all of this correctly. If I start the guide below, can you please be so kind as to make corrections for me? Add, remove, or change steps? Thanks!!! Here it goes, this is my best guess at the steps I need to take:
1. Go to theroot.ninja and complete the unlock process.
2. Download and install Android SDK on PC (installer_r24.1.2-windows.exe).
3. Download and install Motorola Device Manager on PC.
4. Get mfastboot.exe and place it in the same directory as fastboot (fastboot is in the \sdk\platform-tools subdirectory of the Android SDK).
***Do I just drag this .exe to the said folder on my PC?***
5. Get the TWRP for Moto X 4.4 custom recovery for kit kat and place it in the same directory as fastboot.
6. Enable USB debugging and download SuperSU
7. Double check to make sure USB debugging has been enabled. Put your unlocked Moto X into bootloader mode by pressing the Volume Down button and then the Power button. Hold for about 3 seconds and release and you should be in bootloader mode. Connect your Moto X to your PC via a USB cable.
8. Open a command prompt on your PC and change directory to the folder where mfastboot.exe is.
9. At the command prompt type: mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img to flash the custom recovery to your Moto X.
***Is this the version of TWRP I need to root 4.4.2? What about 4.4.4? Or do I just flash the 4.4.4 OTA on top of 4.4.2?***
10. After the custom recovery has been flashed to your Moto X, at the command prompt type: fastboot reboot-bootloader to reboot into the bootloader.
11. Unplug your device from your PC. Then get into recovery mode by pressing the Volume Down button to highlight recovery mode and pressing the Volume Up button to select the recovery mode.
12. You should now have booted into the Team Win Recovery Project custom recovery. Click on Install to install SuperSu. Scroll down to find the sdcard and select it. Then scroll down to download and select it. Select the SuperSU zip file and swipe to install.
*** I also saw this:
"For new users who have only unlocked their bootloaders, flashed TWRP and rooted, then only make use of apps like RootExplorer, QuickBoot(reboot), Adfree, Wifi Tether for Root, etc.. that do NOT modify /System, the easiest way to take the OTA is to...
download the SBF/FXZ for your carrier and the Software Version currently on your phone. Do NOT use a lower Software Version, or the SBF/FXZ for another carrier or you will risk bricking your phone!!!
unzip it.
boot the phone into fastbootAP/bootloader mode
use mfastboot to flash the recovery.img to your phone - mfastboot flash recovery recovery.img
immediately reboot into fastbootAP/bootloader - mfastboot reboot-bootloader
select recovery.
once you've entered stock recovery, you can reboot back into normal system.
take the OTA when it gets to your phone.
you will likely remain rooted, and its optional to flash your custom recovery back on there via mFastboot
However, if you are running Xposed, did a wifi tethering hack, edited build.prop, DELETED bloat from your phone, your phone will fail the OTA Update's validation checks and it will fail. In that case, you can boot back into fasbootAP/Bootloader mode, use mfastboot to flash system.img (mfastboot flash system.img ) from the SBF/FXZ you already downloaded and unzipped. then reboot ( mfastboot reboot ), and try the OTA again. You will need to re-root by flashing custom recovery (like twrp), and re-install SuperSU."
***Is there any way to break down the whole thing into simpler steps???*** THANKS!!!

PackerDroid said:
I think the steps would be: first Sunshine, then 4.4.4 OTA, then root, then Xposed. Is that correct? After I unlock with Sunshine, will my phone still prompt me to update to 4.4.4? Or do I need to need to download 4.4.4 and then flash it? After Sunshine, do I FIRST need to flash 4.4.2 custom recovery? If so, where can I get that? I should probably get a copy of that anyway, even if I don't need it now.
It seems pretty easy overall, but I think I need to refer to a step-by-step guide to make sure I do all of this correctly. If I start the guide below, can you please be so kind as to make corrections for me? Add, remove, or change steps? Thanks!!! Here it goes, this is my best guess at the steps I need to take:
1. Go to theroot.ninja and complete the unlock process.
2. Download and install Android SDK on PC (installer_r24.1.2-windows.exe).
3. Download and install Motorola Device Manager on PC.
4. Get mfastboot.exe and place it in the same directory as fastboot (fastboot is in the \sdk\platform-tools subdirectory of the Android SDK).
***Do I just drag this .exe to the said folder on my PC?***
5. Get the TWRP for Moto X 4.4 custom recovery for kit kat and place it in the same directory as fastboot.
6. Enable USB debugging and download SuperSU
7. Double check to make sure USB debugging has been enabled. Put your unlocked Moto X into bootloader mode by pressing the Volume Down button and then the Power button. Hold for about 3 seconds and release and you should be in bootloader mode. Connect your Moto X to your PC via a USB cable.
8. Open a command prompt on your PC and change directory to the folder where mfastboot.exe is.
9. At the command prompt type: mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img to flash the custom recovery to your Moto X.
***Is this the version of TWRP I need to root 4.4.2? What about 4.4.4? Or do I just flash the 4.4.4 OTA on top of 4.4.2?***
10. After the custom recovery has been flashed to your Moto X, at the command prompt type: fastboot reboot-bootloader to reboot into the bootloader.
11. Unplug your device from your PC. Then get into recovery mode by pressing the Volume Down button to highlight recovery mode and pressing the Volume Up button to select the recovery mode.
12. You should now have booted into the Team Win Recovery Project custom recovery. Click on Install to install SuperSu. Scroll down to find the sdcard and select it. Then scroll down to download and select it. Select the SuperSU zip file and swipe to install.
*** I also saw this:
"For new users who have only unlocked their bootloaders, flashed TWRP and rooted, then only make use of apps like RootExplorer, QuickBoot(reboot), Adfree, Wifi Tether for Root, etc.. that do NOT modify /System, the easiest way to take the OTA is to...
download the SBF/FXZ for your carrier and the Software Version currently on your phone. Do NOT use a lower Software Version, or the SBF/FXZ for another carrier or you will risk bricking your phone!!!
unzip it.
boot the phone into fastbootAP/bootloader mode
use mfastboot to flash the recovery.img to your phone - mfastboot flash recovery recovery.img
immediately reboot into fastbootAP/bootloader - mfastboot reboot-bootloader
select recovery.
once you've entered stock recovery, you can reboot back into normal system.
take the OTA when it gets to your phone.
you will likely remain rooted, and its optional to flash your custom recovery back on there via mFastboot
However, if you are running Xposed, did a wifi tethering hack, edited build.prop, DELETED bloat from your phone, your phone will fail the OTA Update's validation checks and it will fail. In that case, you can boot back into fasbootAP/Bootloader mode, use mfastboot to flash system.img (mfastboot flash system.img ) from the SBF/FXZ you already downloaded and unzipped. then reboot ( mfastboot reboot ), and try the OTA again. You will need to re-root by flashing custom recovery (like twrp), and re-install SuperSU."
***Is there any way to break down the whole thing into simpler steps???*** THANKS!!!
Click to expand...
Click to collapse
Were you able to break this down into simpler steps? Did the steps work for you?

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?

Database Develop

welcome