[help] xt1775 (owens) need stock rom for us cellular version nprs26.58-45-3 - Moto E4 Plus Questions & Answers

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

Related

[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] PLEASE HELP! Accidentally Wipe System w/ TWRP on Moto X (Dev Ed.) (Verizon)

So I recently bought a moto x developer edition off of craigslist and I was updating my phone to kitkat, when I tried to install it took me to the Team Win Recovery Project page. I did not realize someone had already tried to root the phone. Anyway, I accidentally wiped the system rather than factory resetting the phone and now my phone is stuck on the "warning bootloader unlocked page". Just wondering If there is a way to go back to the stock OS. I should mention that know the bare minimum when it comes to this so any help is really appreciated. I really only bought the phone out of necessity!
Use this guide, look for returning to stock section. You can only flash the same or higher Android version that was on it before. Downgrading can end up in a brick.
http://forum.xda-developers.com/showthread.php?t=2603358
yayayesi said:
So I recently bought a moto x developer edition off of craigslist and I was updating my phone to kitkat, when I tried to install it took me to the Team Win Recovery Project page. I did not realize someone had already tried to root the phone. Anyway, I accidentally wiped the system rather than factory resetting the phone and now my phone is stuck on the "warning bootloader unlocked page". Just wondering If there is a way to go back to the stock OS. I should mention that know the bare minimum when it comes to this so any help is really appreciated. I really only bought the phone out of necessity!
Click to expand...
Click to collapse
Come on Vzw users! A twrp system.img! There could be one posted somewhere. BTW any rooted phone even w/o an unlocked boot can generate one using Online Backup in play!
http://forum.xda-developers.com/moto...ready-t2762382
aviwdoowks said:
Come on Vzw users! A twrp system.img! There could be one posted somewhere. BTW any rooted phone even w/o an unlocked boot can generate one using Online Backup in play!
http://forum.xda-developers.com/moto...ready-t2762382
Click to expand...
Click to collapse
Well..I'd like to help out, I too own a XT1060..but have not updated, (purposely) to KK..still on Jelly Bean..
sorry I can't help..
Sent from my 4.4.4_21.11.56_peregrine
(Unlocked) XT1045 Moto G 4G LTE #1
http://waynekent.com/page6.html
"Praise Jah" YOU people.!
KJ said:
Use this guide, look for returning to stock section. You can only flash the same or higher Android version that was on it before. Downgrading can end up in a brick.
http://forum.xda-developers.com/showthread.php?t=2603358
Click to expand...
Click to collapse
Hopefully this is my last question! I seem to finally have everything downloaded and in the right folder. I even reinstalled the drivers. I'm currently on the cmd prompt and input the first line.
and received a "<bootloader> Variable not supported" message, sending 'partition' okay but writing 'partition' failed <remote failure> I currently have the device on the "AP Fastboot Flashmode" (S) screen.
Not really sure whats wrong at this point
Does "fastboot devices" return your serial number?
If all you wiped was system, perhaps try just flashing the system.img with mfastboot.
You definitely have the same firmware you were on? Or was it a custom ROM?
Thing is, we have no idea what was previously done to the phone.
You may be better served using rsdlite for a fresh start.
yayayesi said:
Hopefully this is my last question! I seem to finally have everything downloaded and in the right folder. I even reinstalled the drivers. I'm currently on the cmd prompt and input the first line.
and received a "<bootloader> Variable not supported" message, sending 'partition' okay but writing 'partition' failed <remote failure> I currently have the device on the "AP Fastboot Flashmode" (S) screen.
Not really sure whats wrong at this point
Click to expand...
Click to collapse
Is that the getvar? Do not flash it.
You are better off just editing it out of the XML & use RSD-Lite
KJ said:
Does "fastboot devices" return your serial number?
If all you wiped was system, perhaps try just flashing the system.img with mfastboot.
You definitely have the same firmware you were on? Or was it a custom ROM?
Thing is, we have no idea what was previously done to the phone.
You may be better served using rsdlite for a fresh start.
Click to expand...
Click to collapse
Yes it does return a serial number. T0620060PD
I don't think it was custom I think it was just 4.2 and when I tried to do a system update to 4.4, that's when I wiped the system.
So I could flash rsdlite instead of 4.4? Is there a link for that?
aviwdoowks said:
Is that the getvar? Do not flash it.
You are better off just editing it out of the XML & use RSD-Lite
Click to expand...
Click to collapse
yes I believe so. Thats the reading I get on the device anyway.
It seems both of you recommend rsdlite. Either you know of a guide page with instructions on how to do that?
This is my first time messing with anything this in depth.
Thanks!!
yayayesi said:
yes I believe so. Thats the reading I get on the device anyway.
It seems both of you recommend rsdlite. Either you know of a guide page with instructions on how to do that?
This is my first time messing with anything this in depth.
Thanks!!
Click to expand...
Click to collapse
found this link, do you think it could work?
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
yayayesi said:
found this link, do you think it could work?
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Click to expand...
Click to collapse
Yup
KJ said:
Yup
Click to expand...
Click to collapse
Failed flashing process. 2/1i7 flash partition "gpt.bin"
The device says:
downgraded security version.
update gpt_main version failed.
preflash validation failed for GPT
....do I just have the wrong firmware downloaded or is this thing already bricked
Ive got it! Thank you so much for all the help it was much appreciated! I don't feel like quite the noob now seeing as the phone still lives, but I definitely won't be trying that again any time soon! haha.
Oh, and for reference it seemed that all I needed to do was 4.4.4 rather than just 4.4.
Thanks again!

[Q&A] [GUIDE] Lollipop for XT1064 (CANADA ONLY)

Q&A for [GUIDE] Lollipop for XT1064 (CANADA ONLY)
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 [GUIDE] Lollipop for XT1064 (CANADA ONLY). 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!
confirmed to be working on dual sim xt1068>xt1064 on WIND. Network + Data + SMS works. Thanks
Canadian 5.0 install troubleshooting!
Hello fellow Canucks!
If you're having problems with following NexusChrist's Canadian install guide I have a few pointers. I was also getting the 'downgrade' error. To fix this (and a few other issues) I ended up using mfastboot (available HERE)
After getting msfastboot installed I then went and followed the steps to flash the initial USA firmware but instead used the provided Canadian firmware. Unless you purchased your Moto G2 and DIDN'T do the initial update (small 'bug fixes' for 4.4.4) you probably have to do this to avoid the upgrade problem?
If you guys have any questions please ask! I am by no means a pro but also not a nub. I find that I learn best when having to figure them out!
Thank you! It worked great for me, but I was initially stuck in system.img_sparsechunk part
The US version of 4.4 zip in the link has sparsechunk.0 to sparsechunk.3, therefore I had to start with "fastboot flash system system.img_sparsechunk.0" first instead of sparseschunk.1
tylerhorsman said:
Hello fellow Canucks!
If you're having problems with following NexusChrist's Canadian install guide I have a few pointers. I was also getting the 'downgrade' error. To fix this (and a few other issues) I ended up using mfastboot (available HERE)
After getting msfastboot installed I then went and followed the steps to flash the initial USA firmware but instead used the provided Canadian firmware. Unless you purchased your Moto G2 and DIDN'T do the initial update (small 'bug fixes' for 4.4.4) you probably have to do this to avoid the upgrade problem?
If you guys have any questions please ask! I am by no means a pro but also not a nub. I find that I learn best when having to figure them out!
Click to expand...
Click to collapse
I still get the downgrade error
brianshayne said:
I still get the downgrade error
Click to expand...
Click to collapse
Ignore the 'error'. Yes, your phone will display a notice about downgrade but as long as mfastboot says "OK", it's OK. As long as the phone doesn't spit out a different error, you should be good to go.
I know at first I thought that the downgrade message was it stopping but noticed that mfastboot was still saying "OK", so I kept going and it all worked out!
Give that a try. Remember, if you've already installed the OTA released in Canada for 4.4.4 (at the same time as 5.0 started roll out in USA) then you have to flash the older Canadian ROM that is included in this guide FIRST! Then you can flash to the USA 4.4.4, THEN you can flash the USA 5.0. Hope I've helped some, happy flashing!
---------- Post added at 10:41 PM ---------- Previous post was at 10:32 PM ----------
Keppay said:
Thank you! It worked great for me, but I was initially stuck in system.img_sparsechunk part
The US version of 4.4 zip in the link has sparsechunk.0 to sparsechunk.3, therefore I had to start with "fastboot flash system system.img_sparsechunk.0" first instead of sparseschunk.1
Click to expand...
Click to collapse
Yes good thing to point this out. I also noticed this and automatically started with the '0' sparsechunk. :good:
Yup, that's what I ended up doing. Only seeing this now, but have been on Lollipop since the evening after I made that post Forgot to followup. Silly phone, y u do dis?
I guess when I saw HAB check failed, I thought it was broken. But I just kept flashing away.
Moto G 2nd gen Canada - Flashed to 5, no network connection
I have followed the instructions and successfully have lollipop, but as noted above, have lost cellular data. I am having trouble downloading the original stock from the link above in order to get networking going. Can someone post a firmware for Canada, either to help me get networking back, or to return to factory? Please help.
I thought I was all over this, but I'm clearly over my head.
Worked perfectly! I doubt this will receive OTAs though right?
Nice info thanks
fastboot flash system system.img_sparsechunk1
you started with
fastboot flash system system.img_sparsechunk1
but I got error in this step, i checked files
first system file is fastboot flash system system.img_sparsechunk.0
I started to flash first 0 then 1 , 2 , 3
phone started but it doesn't take signal!!!??!
Any idea?
---------- Post added at 05:40 PM ---------- Previous post was at 05:20 PM ----------
realgmovo said:
confirmed to be working on dual sim xt1068>xt1064 on WIND. Network + Data + SMS works. Thanks
Click to expand...
Click to collapse
I think there are two different X1064. First one comes with WIND mobile which is DualSim and another one from Staples which is single sim.
This Rom should be for Wind. I have Single sim x1064 and it doesn't take signal from my provider(Bell). Frequency problem and different stock roms.
helllllllp
Obsolete
awesome... one more thing..
So, once OTA hits Canada, do i just flash the original 4.4 room with the same commands and then get back to OTA? Would rather not have to manually flash all updates once available, just was chomping at the bit for lollipop. Can anyone post how to reverse to stock?
In terms of experience: was incredible for a week. Started getting severe slowdowns and memory issues, lag. Restored to factory (meaning 5 with Canadian modem) and works great again. Will report if starts lagging again after a week. Love lollipop. Wind Mobile second gen motto g in Canada
worked for me
So, a little touch and go, but was ultimately successful. Ran for a week before ram and redraw issues made me flash again. After a second week, the bugs were enough that I restored to stock. Looking forward to an official ota, hopefully straight onto 5.02, with bug fixes, but thanks so much for this guide. Got a taste of lollipop, am even more excited, and I've learned tons about how my phone actually works. Way more comfortable flashing and playing with ROMs. Great guide, thank you. BTW, anyone know when moto g is getting the damn ota already? Lol
Obsolete
HELPP
attempted the 5.0 walk through. seriously confused, head is spinning and im tierd. managed to go back to 4.4.4 with no service possibly running american firmware. will anyone please tell me how to go back to 4.4.4 for WIND cant find it anywhere, only telus or US xt1034
Thanks!
This worked for me too! I did it all from Mac OS X but it was easy enough to see how to do it there. I had to flash the modem to get calls and texts working. Thanks for the great tutorial!
Obsolete
@Gus.Ottawa does it take a while to load up when you first flash this? Just curious.... Also, you don't happen to have those modem files kicking around anywhere do you?
shorteh said:
@Gus.Ottawa does it take a while to load up when you first flash this? Just curious.... Also, you don't happen to have those modem files kicking around anywhere do you?
Click to expand...
Click to collapse
Yes, it takes something like ten minutes after you see the blue M logo (I never timed it), also takes a long time after a factory reset.
I'm not 100% sure if you need to flash NON-HLOS.bin from the RETCA firmware, but the file is too big to attach on here.
If you have no signal, first try flashing fsg.mbn from RETCA:
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
If still no signal, then flash the two files:
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
If you have the bandwidth, I highly recommend you download and keep the two RETCA firmwares, so you can extract the modem files, or in case you ever wanted to downgarde back to KitKat:
https://mega.co.nz/#F!29RX1L6I!gfxcXgqkAhf5GDhr_aPGYg
Always use mfastboot.

[Q] Q: Recovery Images? ADB sideloading official rom?

I am trying to resurrect a Sprint XT1056 (2013) that won't boot anymore. I can still get into recovery and use ADB to sideload files. The last version of the OS (official) was 4.2.2 (pre-camera I believe). All the roms I find say they won't work because it ran into the "wrong" version (even 4.22, 4.4, etc). The bootloader is locked.
I tried to use the Moto Toolkit (1.4.4), but the links for the auto-downloading within the app are broken.
Any assistance would be greatly appreciated. I have rooted and flashed HTC and Samsung phones in the past, but this phone seems to have a lot of "caveats" to say the least.
Thanks!
DDD
drduranduran said:
I am trying to resurrect a Sprint XT1056 (2013) that won't boot anymore. I can still get into recovery and use ADB to sideload files. The last version of the OS (official) was 4.2.2 (pre-camera I believe). All the roms I find say they won't work because it ran into the "wrong" version (even 4.22, 4.4, etc). The bootloader is locked.
I tried to use the Moto Toolkit (1.4.4), but the links for the auto-downloading within the app are broken.
Any assistance would be greatly appreciated. I have rooted and flashed HTC and Samsung phones in the past, but this phone seems to have a lot of "caveats" to say the least.
Thanks!
DDD
Click to expand...
Click to collapse
You will need to flash the factory images via mfastboot. There is return to stock tutorials on here in the threads.
Travisdroidx2 said:
You will need to flash the factory images via mfastboot. There is return to stock tutorials on here in the threads.
Click to expand...
Click to collapse
Ok, but I still don't have proper Sprint images. Some of the tutorials tells me to edit an .xml file and it doesn't exist. Others mention a SBF file and I don't see that either. I have nothing to use with mfastboot. Also, I am trying to figure out the exact build on this phone and what I need to get. According to most of the data on xda, it seems like I should dump the exact same version first and then OTA from there (trying to put it back to stock).
Can retail users use the moto X dev images? Any other sites that actually have Sprint images? Seems like there's much less out there for Sprint....
http://support.sprint.com/support/a...oX:FindAndUpdateTheSoftwareVersionOnYourMotoX
shows the last update I have on it is: 13.11.3Q2.X-69-3-8
I should put the same on? or try and push the next one: KXA20.16-1.32
Again, I can't seem to find these specific Sprint roms.... ugh
drduranduran said:
http://support.sprint.com/support/a...oX:FindAndUpdateTheSoftwareVersionOnYourMotoX
shows the last update I have on it is: 13.11.3Q2.X-69-3-8
I should put the same on? or try and push the next one: KXA20.16-1.32
Again, I can't seem to find these specific Sprint roms.... ugh
Click to expand...
Click to collapse
Late last night I found an image. Used mfastboot and now the device lives again.

Soft Bricked XT1097

Hey everybody,
I was on CM14.1, no issues, but decided to flash back to 6 and made the stupid mistake of trying to go straight with the standard motorola image. Now I am able to load the bootloader mode but cant do much after that. None of the partitions work, nor I can get data from bootloader info (tried retreieving flashing info to no avail). I am trying to find something I can use. Anyone has a suggestion?
Would you mind detailing which steps you took to flash? I think I know what your problem is, but I want to be sure first.
zstricky said:
Would you mind detailing which steps you took to flash? I think I know what your problem is, but I want to be sure first.
Click to expand...
Click to collapse
Sure!
- Got unlocked bootloader and installed cm14.1
- Decided to revert back to stock so downloaded 6.0 system image.
- instead of deleting the got.bin line from flashfile.xml I went to rsd and tried flashing it. It errored out and this took me where I am.
There is a flashable stock rom zip, but assuming you want to just use the official image that you already have you'll need to flash with fastboot. I saw that you posted on the thread 'return to stock etc'. Follow those fastboot steps, but be aware that there is a major omission: the instructions only go to system.img_sparsechunk.8, but there are 9 of those files and the phone will not boot if you only flash 8. As you go through fastboot flashing I think there will be a couple files that will give errors. Do an internet search on the error output line, but if I remember correctly the files that won't flash are no big deal and didn't affect my phone when I went ahead and ignored the errors.
I did man... The problem is... Something trully god messed up here. I am now getting hard stops related to aboot failures. I saw something similar on the xt1033 forums but we miss those same files.

Categories

Resources