Database Develop

[Q] Having trouble upgrading to 4.4.2 stock on Verizon

I have a Moto X Developer Edition rooted on Verizon with TWRP 2.6.3.1 and stock Android 4.4 on it. I have been trying to upgrade to 4.4.2 without doing the OTA, and without having to reflash TWRP.
So far, I have been unsuccessful.
I have tried Blur_Version.140.45.5.ghost_verizon.Verizon.en.US.zip (approximate file size 150MB) from multiple sources as all the posts I read keep saying that is what works. I have also tried a ~650MB version I found somewhere. In addition, I tried the upgrade located here: sbf.droid-developers.org/phone.php?device=0 which is called VZW_XT1060_4.4.2-KXA20.16-1.25.2_CFC_1FF.xml.zip (It's the 4.4.2 upgrade listed under Verizon US).
All of these fail. In TWRP, about 2-3 steps after it verified md5, it simply says "Failed" with no explanation as to why.
Here is my question:
How can I upgrade to 4.4.2 without a data wipe, and without having to reflash TWRP?
I have no interest in going to a ROM, I want to stay stock, and if I must, I will reflash the recovery if I have to, but I *really* don't want to.

Flash stock recovery, take the OTA, flash TWRP again.
It's so simple, so painless, so quick and it will not wipe your data.

tcrews said:
Flash stock recovery, take the OTA, flash TWRP again.
It's so simple, so painless, so quick and it will not wipe your data.
Click to expand...
Click to collapse
I was hoping to avoid that (Yep, I really am that lazy...) but that's what I was going to do tonight if I couldn't get my hands on a .zip to flash.
Ironically, I bought the Dev Edition specifically so things like this would be easy.

It is easy.....just need to do it.
I support my sister, her husband and my wife (as well as my own) who all have Moto X's. 2 seconds to flash recovery, however long it takes for the OTA to install and reboot and then 2 seconds to flash TWRP again. Heck...I'd just leave the stock recovery in place since it's not needed if you don't plan on flashing any ROMs. The OTA doesn't even remove root.

tcrews said:
It is easy.....just need to do it.
I support my sister, her husband and my wife (as well as my own) who all have Moto X's. 2 seconds to flash recovery, however long it takes for the OTA to install and reboot and then 2 seconds to flash TWRP again. Heck...I'd just leave the stock recovery in place since it's not needed if you don't plan on flashing any ROMs. The OTA doesn't even remove root.
Click to expand...
Click to collapse
Oh, that last bit is good to know! Well, I think even if it did remove root, getting it back is easy on the DE.
I think you're right though, I probably won't install TWRP again, I specifically got the Moto X because I was tired of messing around with stuff when I all I want is a rooted, stock Android experience.

So, after several hours of messing with this, and thinking the stock recovery had gotten messed up because the instructions I had for getting in to it were wrong, I finally got the OTA installing...
and it fails.
I don't know why, I haven't seen the error (I'm not looking at the phone when it fails).
So... Awesome.

Taegost said:
So, after several hours of messing with this, and thinking the stock recovery had gotten messed up because the instructions I had for getting in to it were wrong, I finally got the OTA installing...
and it fails.
I don't know why, I haven't seen the error (I'm not looking at the phone when it fails).
So... Awesome.
Click to expand...
Click to collapse
Are there files out so you can just flash 4.4.2 with mfastboot? Would be easiest.

kj2112 said:
Are there files out so you can just flash 4.4.2 with mfastboot? Would be easiest.
Click to expand...
Click to collapse
I assume so, but I haven't found any instructions specifically saying how to do that, except for the ones that tell you how to return to stock without using RSD Lite.
Unfortunately, I don't know enough about how all this stuff works to be able to figure out which bits and pieces to put together to get upgraded without wiping my data.
What really pisses me off is that I specifically bought this phone so I wouldn't have issues like this, and here I am...
BTW: The only thing the error says is "Error". That's it, nothing else.

Taegost said:
I assume so, but I haven't found any instructions specifically saying how to do that, except for the ones that tell you how to return to stock without using RSD Lite.
Unfortunately, I don't know enough about how all this stuff works to be able to figure out which bits and pieces to put together to get upgraded without wiping my data.
What really pisses me off is that I specifically bought this phone so I wouldn't have issues like this, and here I am...
BTW: The only thing the error says is "Error". That's it, nothing else.
Click to expand...
Click to collapse
This guide has a return to stock section. It will tell you how to flash the stock firmware.
http://forum.xda-developers.com/showthread.php?t=2603358
Unfortunately the moto x is not a simple phone for tinkering with, like say a nexus, even the dev edition.
It can be easier once you do fully understand everything. Just gotta know what applies to you...meaning mostly the locked versus unlocked methods for everything.
After owning an s2, a moto x and now an n5 (n7 too...but I don't tinker with it really....its a family device) I've come to the mind set that for flashers and rooters.....nothing at all beats owning a nexus. Every other device has some limitations that a nexus won't have.

kj2112 said:
This guide has a return to stock section. It will tell you how to flash the stock firmware.
http://forum.xda-developers.com/showthread.php?t=2603358
Unfortunately the moto x is not a simple phone for tinkering with, like say a nexus, even the dev edition.
It can be easier once you do fully understand everything. Just gotta know what applies to you...meaning mostly the locked versus unlocked methods for everything.
After owning an s2, a moto x and now an n5 (n7 too...but I don't tinker with it really....its a family device) I've come to the mind set that for flashers and rooters.....nothing at all beats owning a nexus. Every other device has some limitations that a nexus won't have.
Click to expand...
Click to collapse
Yeah, that's the page I was talking about when I said I found the full instructions...
I specifically bought this phone because I didn't want to mess around with it like this, I just wanted to root it so I could use Titantium Backup and be done with it... and now I'm stuck at a halfway point.... Again...
I'll probably end up just doing the full wipe and manually flash to 4.4.2 (RSD Lite doesn't see my device... yay), since I have gone from my mute button not working (with 4.2.2), to a really bad echo for whomever I'm talking to when it's on speakerphone (Even when speakerphone is muted... THAT made for a fun conference call...).

Taegost said:
Yeah, that's the page I was talking about when I said I found the full instructions...
I specifically bought this phone because I didn't want to mess around with it like this, I just wanted to root it so I could use Titantium Backup and be done with it... and now I'm stuck at a halfway point.... Again...
I'll probably end up just doing the full wipe and manually flash to 4.4.2 (RSD Lite doesn't see my device... yay), since I have gone from my mute button not working (with 4.2.2), to a really bad echo for whomever I'm talking to when it's on speakerphone (Even when speakerphone is muted... THAT made for a fun conference call...).
Click to expand...
Click to collapse
Flashing stock and rooting on an unlocked Moto x is basically the same as a nexus. It really is simple, once you are familiar with fastboot.
I guess there are toolkits that automate everything....like Samsung's Odin, and there's a few for nexus....but it really doesn't help anyone learn. And that's kinda what this hobby is all about.
But, I am sorry you're having trouble. Not sure what else to add. The guides are there, and they work. Usually. I can't think of anything to add to whats already been said.
Hope it works out for you!

kj2112 said:
Flashing stock and rooting on an unlocked Moto x is basically the same as a nexus. It really is simple, once you are familiar with fastboot.
I guess there are toolkits that automate everything....like Samsung's Odin, and there's a few for nexus....but it really doesn't help anyone learn. And that's kinda what this hobby is all about.
But, I am sorry you're having trouble. Not sure what else to add. The guides are there, and they work. Usually. I can't think of anything to add to whats already been said.
Hope it works out for you!
Click to expand...
Click to collapse
I don't think I'm articulating my issue properly. I understand how to do everything in the guides you mentioned, they're a piece of cake. That doesn't solve my problem.
My problem is that I want to get to 4.4.2 WITHOUT wiping my data, but can't do the update via OTA or flashing in recovery. RSD Lite doesn't work either.
The ONLY option I have available to me is to manually push the update with fastboot, which I can definitely do with the instructions provided... But those instructions require me to wipe my data.
I know it's possible to apply the update with fastboot without requiring me to wipe my data, but I don't know enough about the inner workings to know which steps to skip, and which need to be modified, in order to make that happen.

Taegost said:
I don't think I'm articulating my issue properly. I understand how to do everything in the guides you mentioned, they're a piece of cake. That doesn't solve my problem.
My problem is that I want to get to 4.4.2 WITHOUT wiping my data, but can't do the update via OTA or flashing in recovery. RSD Lite doesn't work either.
The ONLY option I have available to me is to manually push the update with fastboot, which I can definitely do with the instructions provided... But those instructions require me to wipe my data.
I know it's possible to apply the update with fastboot without requiring me to wipe my data, but I don't know enough about the inner workings to know which steps to skip, and which need to be modified, in order to make that happen.
Click to expand...
Click to collapse
It says right at the bottom of the return to stock section in the guide I linked too.....you can skip
Fastboot erase user data
fastboot erase cache
Though if you have any problems after, you might have to do it again and do erase those, before spending time trying to figure out what's wrong.

kj2112 said:
It says right at the bottom of the return to stock section in the guide I linked too.....you can skip
Fastboot erase user data
fastboot erase cache
Though if you have any problems after, you might have to do it again and do erase those, before spending time trying to figure out what's wrong.
Click to expand...
Click to collapse
Wow... Attention to detail -5
Sorry about that, when I looked through that article, I skimmed through and saw that the "Return to Stock" section was (almost) identical to the other instructions I was reading...But I missed that last paragraph when I looked at the link you provided, the directions I was using referenced that article but did not include that last bit...
Thank you for your patients, I feel like a dumbass now *sheepish grin*

Taegost said:
Wow... Attention to detail -5
Sorry about that, when I looked through that article, I skimmed through and saw that the "Return to Stock" section was (almost) identical to the other instructions I was reading...But I missed that last paragraph when I looked at the link you provided, the directions I was using referenced that article but did not include that last bit...
Thank you for your patients, I feel like a dumbass now *sheepish grin*
Click to expand...
Click to collapse
No worries!! .
And sorry, its userdata. My keyboard split the words up.
---------- Post added at 11:16 AM ---------- Previous post was at 11:15 AM ----------
And, you may very well have issues doing that way. But its worth a shot first. If you do have issues, then you can erase those and repeat the process.

if using fastboot/mfastboot, I would still erase cache, as it doesn't touch your data/apps/config.
Another tip, use this mfastboot -> http://mark.cdmaforums.com/X-STUFF/Mfastboot-4.4.zip
or you can use RSDlite to flash the SBF, but there is a corresponding line for "erase data"
Two helpful links that will help explain what you saw...
Taking the OTA -> http://mark.cdmaforums.com/MotoX-OTA.html
various ways to Return to stock -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html

kj2112 said:
No worries!! .
And sorry, its userdata. My keyboard split the words up.
---------- Post added at 11:16 AM ---------- Previous post was at 11:15 AM ----------
And, you may very well have issues doing that way. But its worth a shot first. If you do have issues, then you can erase those and repeat the process.
Click to expand...
Click to collapse
Alrighty, well I was able to successfully flash to 4.4.2 using the Fastboot instructions. Flashed TWRP afterwards and got root right back. Now that I know, this won't be a trial in the future (fingers crossed!)
Thanks for your help and patience

[Q] Deleted system partition

I was wiping data and cache on twrp and I accidentaly deleted the system partition. The thing is, I was in the 4.4.3 brazil retail stock rom and I can't find this firmware to flash with rsd. So, what should I do?

Guilhermewpds said:
I was wiping data and cache on twrp and I accidentaly deleted the system partition. The thing is, I was in the 4.4.3 brazil retail stock rom and I can't find this firmware to flash with rsd. So, what should I do?
Click to expand...
Click to collapse
Oh boy....this is a tricky one.
The full STOCK 4.4.3 SBF for the Brazil Retail Rom has not been 'leaked' yet....
Be VERY careful or you could end up with a brick.
Here are my suggested instructions, but DO NOT FOLLOW THEM until another user comments and verifies that I have given you the correct method -- we are in uncharted territory here.
I would suggest downloading the ENTIRE stock 4.4.2 Brazil Retail SBF, extracting it, and running JUST the following commands:
mfastboot flash system system.img
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot erase cache
mfastboot erase userdata
THEN, reboot, and accept the 4.4.3 OTA to get you back on track. This SHOULD work, but wait for another user to verify my suggestions.
The thing is, you cannot flash gpt.bin from the 4.4.2 ROM. Fortunately, the bootloader version did not change, so if we can get you safely booted into 4.4.2, you SHOULD be able to accept the OTA and be back to 4.4.3 without any mismatched partition tables or bootloader.
I hightly suggest making a backup afterwards, so you can restore if something like this happens again...
I also suggest (as you have seen) erasing all userdata (and cache) because it is unknown what problems might arise if you flash the 4.4.2 system.img with your existing userdata.
Unfortunately, this means you will need to set everything up from scratch, but --better safe than sorry--.
Good Luck with this, and one last time - please wait for another experienced user to verify my methods. I do NOT want to be responsible for you bricking your device...
EDIT: Still no reply/confirmation. @KidJoe , @KJ , what do you guys think??

@Guilhermewpds and @samwathegreat
I would be careful.
even though the bootloader did not change between 4.4.2 and 4.4.3, the GPT.BIN (partition table) did. So there could still be issues when trying to "downgrade"
My gut reaction would be, try to flash only the system.img from the 4.4.2 SBF along with erasing userdata and cache, and if it works to get the phone up and running, make sure to NOT take any OTAs. Stick on that until the 4.4.3 SBF leaks, and then flash the SBF to get back to 4.4.3 and bring everything back in line.
keep in mind that erasing userdata will wipe the data and apps you've added to the phone, so I would flash system.img, see if the phone boots, copy any data from it that you can, and then go back and use mfastboot to erase userdata and cache.

I forgot to mention, but i have an unlocked bootloader, so I believe I could, for instance, install a 4.4.3 rom too, couldn't I? I just want to know what is the less risky thing to do in this situation

Guilhermewpds said:
I forgot to mention, but i have an unlocked bootloader, so I believe I could, for instance, install a 4.4.3 rom too, couldn't I? I just want to know what is the less risky thing to do in this situation
Click to expand...
Click to collapse
Although I hate to say it, in this case the less risky method would be to download the entire 4.4.3 SBF for the T-Mobile XT1053, and flash the entire ROM using either fastboot, or RSD Lite.
This should get you up and running in NO time, with much less risk. If and when the Brazil 4.4.3 SBF is released, you can flash it back on, if you want.
---------- Post added at 10:33 AM ---------- Previous post was at 10:30 AM ----------
KidJoe said:
@Guilhermewpds and @samwathegreat
I would be careful.
even though the bootloader did not change between 4.4.2 and 4.4.3, the GPT.BIN (partition table) did. So there could still be issues when trying to "downgrade"
My gut reaction would be, try to flash only the system.img from the 4.4.2 SBF along with erasing userdata and cache, and if it works to get the phone up and running, make sure to NOT take any OTAs. Stick on that until the 4.4.3 SBF leaks, and then flash the SBF to get back to 4.4.3 and bring everything back in line.
keep in mind that erasing userdata will wipe the data and apps you've added to the phone, so I would flash system.img, see if the phone boots, copy any data from it that you can, and then go back and use mfastboot to erase userdata and cache.
Click to expand...
Click to collapse
So exactly the same as my suggestion, except NOT accepting the OTA. Thanks for the input

Guilhermewpds said:
I forgot to mention, but i have an unlocked bootloader, so I believe I could, for instance, install a 4.4.3 rom too, couldn't I? I just want to know what is the less risky thing to do in this situation
Click to expand...
Click to collapse
I usually don't recommend flashing a full ROM/SBF from another carrier and/or model X.. There are a bunch of caveats to keep in mind which makes it risky.
Since you mention you are Brazil, do you have an XT1052, XT1058 or XT1053? My guess is XT1058.
The Only 4.4.3 SBF out there right now appears to be the T-Mobile USA (same as GSM Dev Edition) 4.4.3. You could try it.
If you have an XT1053, its less risky to flash the T-Mo USA SBF, but if your X is an XT1052 or XT1058, then know that the modems will be different and would change the process of flashing the T-MO SBF, or you will lose support of some frequencies.
---------- Post added at 10:54 AM ---------- Previous post was at 10:46 AM ----------
samwathegreat said:
So exactly the same as my suggestion, except NOT accepting the OTA. Thanks for the input
Click to expand...
Click to collapse
Kind of. But I suggested backing up before doing the erase userdata and left off the erase modemst1 & modemst2 because I'm not sure it is really needed.

KidJoe said:
Kind of. But I suggested backing up before doing the erase userdata and left off the erase modemst1 & modemst2 because I'm not sure it is really needed.
Click to expand...
Click to collapse
Modemst1 / Modemst2 = baseband cache partitions. Probably NOT necessary, but definitely can't hurt.
What a tricky situation
I can't think of a way to to express in any more urgency how important it is to not downgrade.....it is already stickied at the top of almost every subforum on here.....I just hate to see these guys end up bricking such a great phone
EDIT: and yes, ALL Brazil Moto X's are XT1058
EDIT2: I also want to point out that although I would normally NEVER recommend flashing another carrier's ROM...I feel it is irresponsible to advise users at it is "perfectly safe", without providing any disclaimer. Think about @bernardomendez181 , who blames another user on this forum for his phone getting bricked. He was advised that it was perfectly safe, and didn't even say "do it at your own risk". That gentleman ended up with a brick, sadly
BUT, you are already in a pickle here. Seems to me that flashing a ROM with the same version of GPT.bin is less risky than having mismatched versions, etc.
Also, @KidJoe, I very much value your advice, which is why I asked for you comment in the first place. Your advice and solutions seem well-thought-out and methodical. I appreciate the contributions you make to our community.

So, with the XT1058 being my variant, what would you guys do in my situation: flash the T-Mobile SBF with/without the modems or downgrade to 4.4.2?

Guilhermewpds said:
So, with the XT1058 being my variant, what would you guys do in my situation: flash the T-Mobile SBF with/without the modems or downgrade to 4.4.2?
Click to expand...
Click to collapse
NEVER DOWNGRADE attempt to 4.4.2 (i.e. once you have 4.4.3 on your phone do NOT fully flash a 4.4.2 SBF on your phone.)
It would be a "no brainer" if the 4.4.3 SBF for your XT1058 and carrier was leaked. Just flash the System.img from your carrier's 4.4.3 SBF.
BUT Your situation is tricky. Brazil XT1058 with 4.4.3, and you need to re-flash, BUT there is no Brazil XT1058 SBF available yet.
I think @samwathegreat and I are both in agreement that anything you proceed with at this point (since the Brazil XT1058 4.4.3 SBF hasn't leaked) will be RISKY!!!
There is the potential to brick your phone in the process, or in the future (when taking an upgrade or flashing back to stock), or might end up just being unstable until you can flash with the proper SBF!
That being said, I think what samwathegreat suggested in Post #2 might be the best course of action, but do NOT take any OTAs, instead wait until the full XT1058 4.4.3 SBF for your carrier leaks, or 4.4.4 SBF should it leak, then flash it to get your files back in line and matched up again. And remember that the erase userdata statement will clear your apps, files, etc from the phone, so back up first if you can! You might find some things that don't work properly (like those with 4.4.2 who flashed 4.4 system.img found that their Settings ->Security menu stopped working)
Flashing only parts of an SBF will put your phone in a state with mismatched files (i.e. files from different versions), so its an undesirable state. Take an OTA, in this state, and you will most likely brick, or possibly get lucky and have the OTA fail its validation checks and not attempt to install.
And I can also agree with samwathegreat's EDIT2 in post #7, that flashing a ROM with with same version GPT.BIN might be less risky than flashing just system.img of an older version and running with mismatched files. However, I've seen people successfully run with a lower system.img and do a FULL SBF back to the current rom version when it was released without bricking.
Then again, another option is flash the system.img from the T-Mobile 4.4.3 SBF, and run with that ( i would still recommend erase cache and erase userdata, and do NOT take any OTA's), and again flash the Brazil XT1058 4.4.3 SBF (or 4.4.4 sbf) if/when it leaks.

So I followed @samwathegreat guide and could put it running again. Thank you so much! The only problem that I've found is that I can't turn wifi on. There's something I could do to fix it or I'll have to wait for the brazilian 4.4.3 SBF?

Guilhermewpds said:
So I followed @samwathegreat guide and could put it running again. Thank you so much! The only problem that I've found is that I can't turn wifi on. There's something I could do to fix it or I'll have to wait for the brazilian 4.4.3 SBF?
Click to expand...
Click to collapse
I seriously doubt that your WiFi not working is a result of what we have done.
I have a very strong idea on what the problem is.
Are you rooted? Please use a the app "Root Browser" to find your /persist folder.
What files are inside?
I have a suspicion that somehow you formatted your persist partition.
Your persist partition should have (among other folders) the following files inside:
.bt_nv.bin
WCNSS_qcom_wlan_nv.bin
WCNSS_qcom_wlan_nv_calibration_persist.bin
WCNSS_qcom_wlan_nv_regulatory_persist.bin
I bet that you are MISSING your WCNSS_qcom_wlan_nv.bin file!
Let me know if you are missing that file. If so, I will send you a copy and your WiFi should start working again immediately. You can NOT get the file from any of the STOCK firmwares or SBF files, because the /persist partition is SUPPOSED to remain untouched between flashes, and is never supposed to be deleted.
Please advise.

samwathegreat said:
I seriously doubt that your WiFi not working is a result of what we have done.
I have a very strong idea on what the problem is.
Are you rooted? Please use a the app "Root Browser" to find your /persist folder.
What files are inside?
I have a suspicion that somehow you formatted your persist partition.
Your persist partition should have (among other folders) the following files inside:
.bt_nv.bin
WCNSS_qcom_wlan_nv.bin
WCNSS_qcom_wlan_nv_calibration_persist.bin
WCNSS_qcom_wlan_nv_regulatory_persist.bin
I bet that you are MISSING your WCNSS_qcom_wlan_nv.bin file!
Let me know if you are missing that file. If so, I will send you a copy and your WiFi should start working again immediately. You can NOT get the file from any of the STOCK firmwares or SBF files, because the /persist partition is SUPPOSED to remain untouched between flashes, and is never supposed to be deleted.
Please advise.
Click to expand...
Click to collapse
Well, I just checked and I do have those files. Everytime I switch the wifi on it switches back to off.

Guilhermewpds said:
Well, I just checked and I do have those files. Everytime I switch the wifi on it switches back to off.
Click to expand...
Click to collapse
Bummer. The missing file results in the same issue. This is likely due to running mismatched versions.
There is a third option that I failed to consider earlier. If you can find someone willing, with a Brazil xt1058 on 4.4.3, you could have them do a factory reset, erase cache, then do a twrp backup of JUST /system
EDIT: upon further review, it shouldn't be necessary for the person who does this for you to reset and erase cache. JUST making a twrp backup of /system should suffice, IF that user has not modified their /system partition.
You can then flash the backup from within twrp and be in good shape.
This will get you 100% back to stock 4.4.3 Brazil ROM, since the rest of your partitions are already on 4.4.3
This is by far the best option for you, but you will need to convince another user with the Brazil retail xt1058 to do this for you.
Good luck

I'm late to the party. Lol. No matter what I do, I am only getting Tapatalk or XDA premium notifications for a bit...then nothing. Lol. I have to uninstall them, then reinstall...and they work...for hours only. Can't solve it either. ?
Glad the X gurus got you running! Kudos guys! ?
Another example tho that downgrading is evil. Never do it.
All this happened when 4.4.2 came out as well.
Patience is the key. Wait for your OTA's guys. Don't flash other carriers, and don't downgrade. (I know other carrier firmware fixed this issue...but it was that or no phone.).
Glad its running!!

Guilhermewpds said:
Well, I just checked and I do have those files. Everytime I switch the wifi on it switches back to off.
Click to expand...
Click to collapse
If you are interested in trying to get someone to share a TWRP backup of /system, I suggest this:
Make a new post in Q&A Section with this title: [REQUEST] TWRP backup of /system on Brazil Retail XT1058 4.4.3
And explain why you need the backup. It is very likely that another user will do this for you! If you haven't already, read my edit in the previous post: they should NOT have to reset and clear cache.
Just make sure you point out that you ONLY want a backup from someone who has not modified their /system partition, and also make it very clear that you need a backup of JUST /system.
This is fairly easy to do with TWRP. The user who provides you with their /system backup will simply boot into TWRP, click "BACKUP", and UNCHECK everything EXCEPT "System".
Then you will copy this backup provided to you to your internal memory into your TWRP backup folder.
Then YOU will boot into TWRP, press "WIPE", click "Advanced Wipe", then check "Dalvik Cache, Data, Cache, and System".
Next, press RESTORE, and find the backup that you copied to your internal memory, and start the restore.
This should do it for you!!!! Good Luck, and hope you get the needed backup
These instructions were written by memory, so I hope I haven't left out any steps. If you get stuck, let me know and I'll try to help.

samwathegreat said:
If you are interested in trying to get someone to share a TWRP backup of /system, I suggest this:
Make a new post in Q&A Section with this title: [REQUEST] TWRP backup of /system on Brazil Retail XT1058 4.4.3
And explain why you need the backup. It is very likely that another user will do this for you! If you haven't already, read my edit in the previous post: they should NOT have to reset and clear cache.
Just make sure you point out that you ONLY want a backup from someone who has not modified their /system partition, and also make it very clear that you need a backup of JUST /system.
This is fairly easy to do with TWRP. The user who provides you with their /system backup will simply boot into TWRP, click "BACKUP", and UNCHECK everything EXCEPT "System".
Then you will copy this backup provided to you to your internal memory into your TWRP backup folder.
Then YOU will boot into TWRP, press "WIPE", click "Advanced Wipe", then check "Dalvik Cache, Data, Cache, and System".
Next, press RESTORE, and find the backup that you copied to your internal memory, and start the restore.
This should do it for you!!!! Good Luck, and hope you get the needed backup
These instructions were written by memory, so I hope I haven't left out any steps. If you get stuck, let me know and I'll try to help.
Click to expand...
Click to collapse
I tried asking in a brazilian forum for the Moto X, but it seems more likely to get it here. I've run out of thanks, so thank you once again. I really appreciate your assistance!

This is simple suggestions, but worth a shot.
WiFi won't stay on at all? Or does it turn off while connecting? If you are able to...try forgetting your WiFi network if it let's you....and sign in again.
Also, reboot your router/modem.
And try a factory reset if all that fails. Yes, all apps and data will be gone. But with a try.
Basic suggestions....but who knows, something might work.

samwathegreat said:
....There is a third option that I failed to consider earlier. If you can find someone willing, with a Brazil xt1058 on 4.4.3, you could have them do a factory reset, erase cache, then do a twrp backup of JUST /system
Click to expand...
Click to collapse
Duh, I completely forgot about that too... Its been a while since I did backup/restore in CWM/TWRP that it completely slipped my mind. :crying:

KidJoe said:
Duh, I completely forgot about that too... Its been a while since I did backup/restore in CWM/TWRP that it completely slipped my mind. :crying:
Click to expand...
Click to collapse
Yep, I understand. Since we are using the STOCK rom (mostly), I rarely use TWRP anymore. Back in my "HTC Droid Incredible" days, flashing all kinds of different roms, I used to use CWM backups on a daily basis....
Oh well. OP has made a request and hopefully someone will share soon.

I finally got it in a brazilian forum. Thank you, @samwathegreat, @KidJoe and @KJ for your assistance and guidance! I really appreciate your help!

How to flash from 1.32 to 1.40 without losing your freaking mind (requires S-Off)

So yeah the people in the Int'l forums got that 1.40 OTA and the ROM devs have updated their ROMs to the 1.40 base.
Of course, this means we T-Mobile users are absolutely screwed unless we too update to the 1.40 base since trying to flash anything with the 1.40 base will make us bootloop and cry and swear. Mostly cry...and swear.
So here's a quick guide on getting your device to the 1.40 base so you can actually flash those ROMs again. Here we go. Note: I'm not responsible if anything bad happens. I sympathize, but it's not my bad.
Prerequistes:
1. You need S-Off. That means you'll need to fork out $25 to Sunshine and get it done.
2. You need Minimal ADB and Fastboot. The link for that is here.
3. An external SD card large enough to hold one nandroid backup and one ROM.
4. You'll need to make a Nandroid backup for your protection.
Guide:
1. First thing's first. You'll need to download ANY 1.40-based ROM. It doesn't matter which one, whatever one you want. Put that on your EXTERNAL SD CARD. You can find those in the Android Development section of the HTC One M9 international forums. The link for that is here. I highly recommend one that boasts that it's compatible with T-Mo devices. I flashed one of the Int'l-only ones and lost mobile data. Had to download and install another ROM. Learn from my mistakes.
2. Next you'll need to pick up the 1.40 firmware. The one I used is linked here. You'll want to download the latest one.
3. Now we get to have some fun. Open up minimal adb and fastboot and put your One M9 into DOWNLOAD MODE. Type "fastboot devices" without the quotes to make sure your device is recognized. If not, you need to go download the HTC One M9 drivers (just download and install HTC Sync). Once fastboot recognizes your device, type this command:
Code:
fastboot oem writecid 11111111
That is eight 1's, by the way. This will make your phone capable of flashing just about any firmware. Be careful and don't flash everything you find on the Internet. Once done, reboot back into download mode if it's not already there.
4. Rename the 1.40 firmware you downloaded to "update.zip" (no quotes) and put it in the minimal adb and fastboot folder (usually under C drive in the program files x86 folder).
5. Okay kids, this is the hard part so pay attention. You're going to flash the update TWICE. Why? I'll explain in the moment. Type these commands in order:
Code:
fastboot oem rebootRUU
followed by:
Code:
fastboot flash zip update.zip
Now at this point you'll probably get something like "90 Fail" or "Fail 90". What's just occurred is that part of the update was flashed, but not all of it. Sometimes it'll un-**** itself and continue on its own but usually not. To fix it, simply type the command a second time:
Code:
fastboot flash zip update.zip
This should complete the flash.
6. Reboot back into your recovery. Mount any partitions that may not be mounted.
7. Flash the ROM you downloaded back in step 1. Make sure you wipe everything (system, data, cache, dalvik) before doing so.
8. Reboot and enjoy.
Now that should be it. If you have problems, you'll want to visit this thread and the thread you downloaded the 1.40 firmware from (linked above) because those guys seem to know what they're doing and I really don't.
From this point forward, you SHOULD be able to flash any 1.40 based ROM without issues or cheap fixes (like in the ViperROM...by the way, it was really awesome of them to include that fix, even if it was a cheap fix. Thanks guys!).
Also, a big thanks to NO ONE for writing this guide anywhere else. Good job, jackass. As per the norm, you don't have to thank me and I don't care if you copy/paste the guide somewhere else without giving me credit. Information is free.

Is there any way to keep WiFi calling? Do I need to flash a modern or radio?

Is the T-Mo version of this updated ROM expected to release soon ?

I tried this, but I got very little lte reception. I even tried flashing the T-Mobile radio image, and I still had bad LTE. I flashed the T-Mobile firmware and all is good with LTE. Has anyone else have this problem?

jbfountain said:
I tried this, but I got very little lte reception. I even tried flashing the T-Mobile radio image, and I still had bad LTE. I flashed the T-Mobile firmware and all is good with LTE. Has anyone else have this problem?
Click to expand...
Click to collapse
Flash the firmware and then the T-Mobile radio

ahrion said:
Flash the firmware and then the T-Mobile radio
Click to expand...
Click to collapse
Anyone try the 2.7 firmware with a TMO radio?

123421342 said:
Anyone try the 2.7 firmware with a TMO radio?
Click to expand...
Click to collapse
I've tried flashing a Tmo radio after flashing the new 2.7 firmware however I get a fail message (can't remember all the details). I was using a radio image from a thread in the General section of the International M9 forum... I was able to flash that same radio with the 1.40 firmware so who knows if there's something different now...

ahrion said:
Flash the firmware and then the T-Mobile radio
Click to expand...
Click to collapse
That's the way I did it, but still had bad reception until I flashed the T-Mobile firmware again.
---------- Post added at 02:11 PM ---------- Previous post was at 02:03 PM ----------
xHVGx said:
I've tried flashing a Tmo radio after flashing the new 2.7 firmware however I get a fail message (can't remember all the details). I was using a radio image from a thread in the General section of the International M9 forum... I was able to flash that same radio with the 1.40 firmware so who knows if there's something different now...
Click to expand...
Click to collapse
Go here http://forum.xda-developers.com/one-m9/general/recovery-flashable-radio-zip-t3122983. You can flash it using TWRP according to this thread. Let us know how you do.
Cheers

Prasad said:
Is the T-Mo version of this updated ROM expected to release soon ?
Click to expand...
Click to collapse
Expect something newer than 1.40 coming very soon. ? I'd share some screenshots but that's saying too much.
Sent From My HTC One (M9)

Rydah805 said:
Expect something newer than 1.40 coming very soon. I'd share some screenshots but that's saying too much.
Sent From My HTC One (M9)
Click to expand...
Click to collapse
so pretty much 2.7 TMO confirmed within a week?

Rydah805 said:
Expect something newer than 1.40 coming very soon. I'd share some screenshots but that's saying too much.
Sent From My HTC One (M9)
Click to expand...
Click to collapse
Really hoping for that newer version soon. From what I've heard, the improvements seen in 1.4 and 2.7 both make the phone much better to use. 1.32 is fine, but the thing really does heat up way too quickly, and others have said this problem is much less noticeable on newer firmwares.

guyverzero said:
Really hoping for that newer version soon. From what I've heard, the improvements seen in 1.4 and 2.7 both make the phone much better to use. 1.32 is fine, but the thing really does heat up way too quickly, and others have said this problem is much less noticeable on newer firmwares.
Click to expand...
Click to collapse
I've forgotten that this thing heats up. ? expect something very soon.
Sent From My HTC One (M9)

[Q&A] Droid Turbo XT1254 5.1 Rooted Images (+Xposed, other extras) / Upgrade from 4.

[Q&A] Droid Turbo XT1254 5.1 Rooted Images (+Xposed, other extras) / Upgrade from 4.
Q&A for Droid Turbo XT1254 5.1 Rooted Images (+Xposed, other extras) / Upgrade from 4.4
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Droid Turbo XT1254 5.1 Rooted Images (+Xposed, other extras) / Upgrade from 4.4. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

I followed instructions on the OP and keep getting a "No command" error when I try to boot into recovery (I've already let it boot to the set up screen already since some people have said that fixed it). Is there a way to fix this or did I somehow mess it up?

Biffins said:
I followed instructions on the OP and keep getting a "No command" error when I try to boot into recovery (I've already let it boot to the set up screen already since some people have said that fixed it). Is there a way to fix this or did I somehow mess it up?
Click to expand...
Click to collapse
Same thing for me...
Sent from my Droid Turbo

Biffins said:
I followed instructions on the OP and keep getting a "No command" error when I try to boot into recovery (I've already let it boot to the set up screen already since some people have said that fixed it). Is there a way to fix this or did I somehow mess it up?
Click to expand...
Click to collapse
getupandbeit said:
Same thing for me...
Sent from my Droid Turbo
Click to expand...
Click to collapse
At the recovery which reads "no command" hold power and press volume up.

Works on

What's going to happen if I push 5.1 and Android M comes out officially?
Am I better off holding until that time or is there a way to get there once I do all of this

Hello, Ive been reading on here about mofo for the last month, and Ive been waiting to see how lollipop goes over. After reading all the success stories, I bought mofo.
My phone has never been rooted, is there a specific guide for going to computerfreek274's loliipop image from a stock kitkat ? All the guides seem to assume Im already rooted on kitkat. Or should I root on kitkat first?
thanks

In the fastboot commands for this update, I notice that the command to flash radio.img is missing. Is this an oversight or is a flash of the radio partition not needed?
Thanks for all that you and Computerfreek274 contribute to this forum!!!

turpindm said:
In the fastboot commands for this update, I notice that the command to flash radio.img is missing. Is this an oversight or is a flash of the radio partition not needed?
Thanks for all that you and Computerfreek274 contribute to this forum!!!
Click to expand...
Click to collapse
The instructions in the main thread have were changed to reflect the latest files (you'll be flashing modem and a few others instead of radio). If you're using the guide that was linked, it hasn't been updated with the latest instructions yet.

firstEncounter said:
The instructions in the main thread have were changed to reflect the latest files (you'll be flashing modem and a few others instead of radio). If you're using the guide that was linked, it hasn't been updated with the latest instructions yet.
Click to expand...
Click to collapse
I am up an running I started experiencing data and voice signal issues - RIght now I have advanced calling I can talk and surf but the option is not in my Advanced Calling settings menu - but testing to see if the device holds signal for 1x communication. It keeps dropping the signal and never gets it backs a signal so I have been using my back up device for days now.

turk2333 said:
I am up an running I started experiencing data and voice signal issues - RIght now I have advanced calling I can talk and surf but the option is not in my Advanced Calling settings menu - but testing to see if the device holds signal for 1x communication. It keeps dropping the signal and never gets it backs a signal so I have been using my back up device for days now.
Click to expand...
Click to collapse
Make sure you haven't disabled the My Verizon app in order for the Advanced Calling menu to work correctly.
For radio issues, make sure you've downloaded the latest 5.1_images_v3.zip and used the fastboot commands in the main thread. You can run all those commands without reflashing your system.img just to make sure everything's up to date. If you're still having issues, I'm not sure what else you can try other than backing up everything and trying a data wipe.

firstEncounter said:
Make sure you haven't disabled the My Verizon app in order for the Advanced Calling menu to work correctly.
For radio issues, make sure you've downloaded the latest 5.1_images_v3.zip and used the fastboot commands in the main thread. You can run all those commands without reflashing your system.img just to make sure everything's up to date. If you're still having issues, I'm not sure what else you can try other than backing up everything and trying a data wipe.
Click to expand...
Click to collapse
seems stable now - I did two data wipes - was so many issues with the radio and I was like no way this cannot be fixed. I have nto left my office yet which will be the real test but right now all seems good.

turk2333 said:
seems stable now - I did two data wipes - was so many issues with the radio and I was like no way this cannot be fixed. I have nto left my office yet which will be the real test but right now all seems good.
Click to expand...
Click to collapse
I've had my phone get stuck on 1x a few times when using 4.4, so it's possible it's just a bug in the actual firmware.

firstEncounter said:
I've had my phone get stuck on 1x a few times when using 4.4, so it's possible it's just a bug in the actual firmware.
Click to expand...
Click to collapse
This is not being stuck this was no service at all would to G then I could not make calls or anything - totally screwed up - I have a new phone on the way from Assurion if this keeps happening. As I posted - I flashed all commands per instructions and that seem to do the trick I hope.

Thanks to everyone who keeps the updates updated... 23.11.39 Root went well... Thanks again!!!

Fastboot Command
Could someone please show me an example on how to flash files on the command prompt with adb. How do I direct it to the file location that I want to flash. Screen shot would be very helpful. Thank you for your time in advance.

Hi,
Can someone please explain something to me?
If the BL is locked on xt1254 but mofo somehow gets around it to enable flashing of rooted images.. What is stopping us from flashing a modified cyanogenmod or equivalent over?
Why do we need an unlocked bootloader if we can already flash modified images? Is there some check in place that prevents this? Or is this wip?
I'm obviously missing something!
Thanks guys
Sent from my Nexus 5 using XDA Free mobile app

Quick question
I am on stock 4.4.4 do i need "5.1 upgrade images (v3)" or "Rooted 5.1 system image (v2)" to get myself to 5.1 with root? And wifihotspot is enabled on all these images correct?

SkiiinZ said:
Hi,
Can someone please explain something to me?
If the BL is locked on xt1254 but mofo somehow gets around it to enable flashing of rooted images.. What is stopping us from flashing a modified cyanogenmod or equivalent over?
Why do we need an unlocked bootloader if we can already flash modified images? Is there some check in place that prevents this? Or is this wip?
I'm obviously missing something!
Thanks guys
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
because mofo can't write the kernel/boot partition
Sent from my XT1254 using Tapatalk

Tap053 said:
I am on stock 4.4.4 do i need "5.1 upgrade images (v3)" or "Rooted 5.1 system image (v2)" to get myself to 5.1 with root? And wifihotspot is enabled on all these images correct?
Click to expand...
Click to collapse
Either one should work if you follow the instructions but only the "extra" versions have tethering enabled. At this point, I'd use the image labeled "Extras 5.1 system image (rooted v2 + extras v4)". You can always start with the stock rooted, then dirty flash the extras version with mofo.
Sent from my XT1254 using Tapatalk
---------- Post added at 01:34 AM ---------- Previous post was at 01:29 AM ----------
Rag Man said:
Could someone please show me an example on how to flash files on the command prompt with adb. How do I direct it to the file location that I want to flash. Screen shot would be very helpful. Thank you for your time in advance.
Click to expand...
Click to collapse
Nowhere in the OP for this ROM does it mention flashing files with ADB. You can only flash the system image with the mofo tool. We do not have a custom recovery on the Turbo so you cannot flash ZIP files. We do not have a writable system partition so you cannot push files to it via ADB.
Fastboot is used to upgrade some of the other partitions to the 5.1 versions and is described in the OP.
Sent from my XT1254 using Tapatalk

[help] xt1775 (owens) need stock rom for us cellular version nprs26.58-45-3

I just picked up a Moto E4 plus Xt1775 (owens) US Cellular which had a rom NPRS26.58-45-3. I managed to unlock the bootloader but then i screwed everything up by flashing a rom made for the retail version. Anyway, moto apparently doesnt distribute very many stock roms and I hoping somebody out there would post or send me the stock rom version so I can get it back to normal. Moto does not have a Kies (Restore to factory software thingy) or post stock roms on their website for this model. I wish (thought) they had something like Kies .Lesson learned. anyway please help somebody.
What happened:
1. phone upgraded over ota to NPRS26.58-45-3 under stock.
2. Unlocked bootloader (went fine with Moto key)
3. FLashed Moto retail stock rom for 1775 Owens NPR26.58-25(could not flash gpt.bin because of error)
4. displays bad_key upon boot.
5. Lost imei info
6. flashed modem from sprint retail to get my imei back
Current status:
1. Displays "bad_key"
2. has stock NPR26.58-25 rom from the oem stock post
3. and sprint modem

First of all, the firmware your asking for is brand new, and not going to be available for a little while. You'll have to wait. I'm a little confused as to how or why you did what you say here, but I might be able to help. A little more info would be great though. When you flashed the retail firmware, did you flash the OEM partition? Another thing, did you flash twrp or do you still have stock recovery?

Goose03 said:
First of all, the firmware your asking for is brand new, and not going to be available for a little while. You'll have to wait. I'm a little confused as to how or why you did what you say here, but I might be able to help. A little more info would be great though. When you flashed the retail firmware, did you flash the OEM partition? Another thing, did you flash twrp or do you still have stock recovery?
Click to expand...
Click to collapse
Thank you Goose03 for taking the time to work through my post and any help will be appreciated.
I understand your confusion as to the how or why --because I really messed up here big time. Right now, I really do not know why I did this. If only I could go back in time.
I flashed according to the instructions found here: https://forum.xda-developers.com/moto-e4-plus/how-to/moto-e4-qualcomm-owens-completely-to-t3743441
and flashed line by line using Minimal ADB and Fastboot to assist in issuing the commands to my e4 plus
As I started the process, the 2nd command on the list "fastboot flash gpt gpt.bin" errored out... but for some reason I continued on down the line and the rest of the flashing commands worked.
Currently, I have the stock recovery, but I can install twrp if necessary.
The phone apparently works so I got that going for me, albeit with the "bad_key" screen before it works its way through the booting process.
I hope all this make sense. Once again, thanks for your assistance and patience, and I understand that i just may need to wait until the updated firmware eventually gets posted.

edfcmc said:
Thank you Goose03 for taking the time to work through my post and any help will be appreciated.
I understand your confusion as to the how or why --because I really messed up here big time. Right now, I really do not know why I did this. If only I could go back in time.
I flashed according to the instructions found here: https://forum.xda-developers.com/moto-e4-plus/how-to/moto-e4-qualcomm-owens-completely-to-t3743441
and flashed line by line using Minimal ADB and Fastboot to assist in issuing the commands to my e4 plus
As I started the process, the 2nd command on the list "fastboot flash gpt gpt.bin" errored out... but for some reason I continued on down the line and the rest of the flashing commands worked.
Currently, I have the stock recovery, but I can install twrp if necessary.
The phone apparently works so I got that going for me, albeit with the "bad_key" screen before it works its way through the booting process.
I hope all this make sense. Once again, thanks for your assistance and patience, and I understand that i just may need to wait until the updated firmware eventually gets posted.
Click to expand...
Click to collapse
I would say if it's working for you, let it be until the proper firmware for your device is released. You have a data connection and everything? I know the E4 perry USC firmware is slightly different than retail model firmware so I'm sure the same goes for your device also.The "bad_key" screen is what your bootlogo is changed to when you unlock the bootloader and haven't disabled dmverity. It's normal, don't worry about that.
Sent from my Moto E (4) Plus using XDA Labs