I have a Verizon moto x unlocked currently running 4.4.2 with twrp installed. If I understand correctly I can't take the OTA because I don't have a stock recovery.
Has anyone uploaded a flashable update yet?
Sent from my XT1060 using Tapatalk
A quick look around the forums would've answered your question.
nhizzat said:
A quick look around the forums would've answered your question.
Click to expand...
Click to collapse
No it didn't but thanks for the help.
Sent from my XT1060 using Tapatalk
If you click yourself on over to the Moto X General forum, you'll see this thread titled "[FXZ] Moto X 4.4.4 212.55.26 (XT1060)" which has 10k+ views,163 posts, and is at the very top of the first page right below the stickies. The last reply in that thread was posted tonight at 9:29pm. Between 9pm and the time you posted this thread, there were 8 replies posted so the thread has been at the very top of the General forum.
You've been a member here for nearly 4 years and have made nearly 1k posts in that time, there are no excuses. Could I have been more helpful by answering your question? Of course. However, when the answer to your question can be found that easily, why should I bother? It's obvious you didn't bother to look, because there's no way you could've seen "[FXZ] Moto X 4.4.4 212.55.26 (XT1060)" and not click on it.
Asks about updating a Verizon Moto X to 4.4.4, skips the thread which has all of the key words in the title.
nhizzat said:
If you click yourself on over to the Moto X General forum, you'll see this thread titled "[FXZ] Moto X 4.4.4 212.55.26 (XT1060)" which has 10k+ views,163 posts, and is at the very top of the first page right below the stickies. The last reply in that thread was posted tonight at 9:29pm. Between 9pm and the time you posted this thread, there were 8 replies posted so the thread has been at the very top of the General forum.
You've been a member here for nearly 4 years and have made nearly 1k posts in that time, there are no excuses. Could I have been more helpful by answering your question? Of course. However, when the answer to your question can be found that easily, why should I bother? It's obvious you didn't bother to look, because there's no way you could've seen "[FXZ] Moto X 4.4.4 212.55.26 (XT1060)" and not click on it.
Asks about updating a Verizon Moto X to 4.4.4, skips the thread which has all of the key words in the title.
Click to expand...
Click to collapse
And then you waste all that time typing that out, instead of just linking him to what he needs to find? I hate responses like yours. Instead of "did you do a search" why not just not reply at all? Lame.
This is the post with all the info: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
I am in the same boat as OP. I first flashed to stock 4.4.2, but I don't think you need to with the FXZ from that thread.
dhoppy said:
I am in the same boat as OP. I first flashed to stock 4.4.2, but I don't think you need to with the FXZ from that thread.
Click to expand...
Click to collapse
You are correct. With this FXZ, one can flash from *any* version straight to 4.4.4, unlike OTA's which are "incremental" in nature.
No need to flash stock recovery, either. :good:
Thanks for the actual response! I did see that thread, but I'm not familiar with fxz, I looked it up and it appeared to be for a Windows only toolkit. Am I mistaken? Can this be flashed in twrp?
I have been on xda quite a while and it's quite common for real information to be lost in posts because people jam them up with useless bickering and shaming instead of real information. The moto x posts seem to be lost in the thousands of Combinations of downgrades upgrades and write protection combos that people have. I'm used to phones with unlocked bootloaders, where someone usually posts a stock rom that you can flash. I haven't found that here.
Sent from my XT1060 using Tapatalk
T-Keith said:
Thanks for the actual response! I did see that thread, but I'm not familiar with fxz, I looked it up and it appeared to be for a Windows only toolkit. Am I mistaken? Can this be flashed in twrp?
I have been on xda quite a while and it's quite common for real information to be lost in posts because people jam them up with useless bickering and shaming instead of real information. The moto x posts seem to be lost in the thousands of Combinations of downgrades upgrades and write protection combos that people have. I'm used to phones with unlocked bootloaders, where someone usually posts a stock rom that you can flash. I haven't found that here.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
RSD Flasher is a java program, should run anywhere, but I don't know about RSD Lite.
I extracted the FXZ file, and then flashed it manually because RSD Lite won't run on USB 3.0, but fastboot will. I don't know if it is supposed to work that way, but seems to be working for me. I'm in the process of rooting right now.
T-Keith said:
Thanks for the actual response! I did see that thread, but I'm not familiar with fxz, I looked it up and it appeared to be for a Windows only toolkit. Am I mistaken? Can this be flashed in twrp?
I have been on xda quite a while and it's quite common for real information to be lost in posts because people jam them up with useless bickering and shaming instead of real information. The moto x posts seem to be lost in the thousands of Combinations of downgrades upgrades and write protection combos that people have. I'm used to phones with unlocked bootloaders, where someone usually posts a stock rom that you can flash. I haven't found that here.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
dhoppy said:
RSD Flasher is a java program, should run anywhere, but I don't know about RSD Lite.
I extracted the FXZ file, and then flashed it manually because RSD Lite won't run on USB 3.0, but fastboot will. I don't know if it is supposed to work that way, but seems to be working for me. I'm in the process of rooting right now.
Click to expand...
Click to collapse
I can help you with this....
First, @T-Keith , I came across your post after @dhoppy had just answered your question, pointing you to the fxz thread.
Second, T-Keith, you can absolutely flash this in Linux OR Mac (let me know which you are running, and I'll help with both the tools and commands necessary).
It will take only a couple minutes to complete and your data will be left intact.
Linux
Sent from my Nexus 7 using Tapatalk
T-Keith said:
I have a Verizon moto x unlocked currently running 4.4.2 with twrp installed. If I understand correctly I can't take the OTA because I don't have a stock recovery.
Has anyone uploaded a flashable update yet?
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
I'm sorry, I'm jumping in late but...
IF you are on 4.4.2, and pretty close to stock (i.e. Xposed disabled, system files not modified, etc. so that the manifest checks inside the OTA will not fail) then you can just use mfastboot to flash stock recovery and take the OTA.
If the OTA hasn't been pushed to your device yet, but it has leaked (like the 4.4.4. OTA for Verizon) and you want install it, see -> http://mark.cdmaforums.com/MotoX-SideloadOTA.htm
This process will NOT impact your data or apps.
If you are TOO far from stock... then just return to stock by flashing the full SBF/FXZ for your phone. If the 4.4.4 FXZ/SBF has leaked for your phone, then just flash it using RSDLite, mFastboot(manual steps), or other tool. This will likely wipe your data, apps and settings and put you back to stock.
KidJoe said:
I'm sorry, I'm jumping in late but...
IF you are on 4.4.2, and pretty close to stock (i.e. Xposed disabled, system files not modified, etc. so that the manifest checks inside the OTA will not fail) then you can just use mfastboot to flash stock recovery and take the OTA.
If the OTA hasn't been pushed to your device yet, but it has leaked (like the 4.4.4. OTA for Verizon) and you want install it, see -> http://mark.cdmaforums.com/MotoX-SideloadOTA.htm
This process will NOT impact your data or apps.
If you are TOO far from stock... then just return to stock by flashing the full SBF/FXZ for your phone. If the 4.4.4 FXZ/SBF has leaked for your phone, then just flash it using RSDLite, mFastboot(manual steps), or other tool. This will likely wipe your data, apps and settings and put you back to stock.
Click to expand...
Click to collapse
The new Leaked FXZ is a "KEEP DATA" FXZ - Moto Made it this way (thanks Moto!!). Unless someone explicitly runs "fastboot erase userdata" or uses a different tool to erase userdata, it's just as good (BETTER) than taking the OTA. :good:
T-Keith said:
Linux
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
OK, have you managed to do it already? My response was from last night, so if you have already managed to flash it, I don't want to go finding the tools and spend a few minutes writing up a guide for you. Confirm (quickly) if you still need it, and I'll write it right up for you, if so.
KidJoe said:
I'm sorry, I'm jumping in late but...
IF you are on 4.4.2, and pretty close to stock (i.e. Xposed disabled, system files not modified, etc. so that the manifest checks inside the OTA will not fail) then you can just use mfastboot to flash stock recovery and take the OTA.
If the OTA hasn't been pushed to your device yet, but it has leaked (like the 4.4.4. OTA for Verizon) and you want install it, see -> http://mark.cdmaforums.com/MotoX-SideloadOTA.htm
This process will NOT impact your data or apps.
If you are TOO far from stock... then just return to stock by flashing the full SBF/FXZ for your phone. If the 4.4.4 FXZ/SBF has leaked for your phone, then just flash it using RSDLite, mFastboot(manual steps), or other tool. This will likely wipe your data, apps and settings and put you back to stock.
Click to expand...
Click to collapse
Yeah I have xposed installed, and twrp. So that might be a good option. Is there anyway to test that? It looks like rsdlite and mfastboot are Windows tools, can I just use adb fastboot?
Sent from my XT1060 using Tapatalk
T-Keith said:
Yeah I have xposed installed, and twrp. So that might be a good option. Is there anyway to test that? It looks like rsdlite and mfastboot are Windows tools, can I just use adb fastboot?
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
...He's offline. Do you want me to help you? I HAVE all the linux tools, and know how to do this. KidJoe only uses Windows...
EDIT: @T-Keith : Well....here's the info anyways. Use it if you want..
1. Download the FULL FXZ from here: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
2. Extract it
3. Download the attachment that I was so kind as to attach here for you (you MUST use this variant of fastboot - for Linux) Extract THIS fastboot to same folder as the FXZ files (possibly need to change permissions +x)
4. Boot phone into bootloader mode (AP Fastboot Mode): Unplug phone, power off. Hold Down VOL DOWN + POWER
5. Execute the following commands IN ORDER:
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
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot reboot
DONE! And your data should still be intact....if you would PREFER to wipe your data, add the following command BEFORE "fastboot reboot"
fastboot erase userdata
Thanks. Does this method work with twrp then?
Sent from my XT1060 using Tapatalk
T-Keith said:
Thanks. Does this method work with twrp then?
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Definitely! (so long as you are UNLOCKED)
AFTER you complete EVERTHING in my instructions...and you boot into android successfully...and confirm everything works:
Just reboot BACK into the BL, and
fastboot flash recovery twrpfilename.img
(get the latest version here: http://techerrata.com/browse/twrp2/ghost )
then immediately afterwards, type:
fastboot reboot-bootloader
then VOL DOWN to RECOVERY, and VOL UP to select it. (you HAVE do this immediately after flashing TWRP or it won't stick and will revert back to stock recovery...for unknown reasons. As long as you boot into TWRP IMMEDIATELY after flashing it, it sticks forever...)
When you go to exit TWRP, it will ask you if you would like to install SuperSU installer. Tell it YES! Then once rebooted, you will have an icon for SuperSU Installer. Click it, and select "PLAY STORE" method. Done. Rooted. 4.4.4
Any idea if this will work with an encrypted phone? I believe the data partition is the only one encrypted. Mine is throwing an error trying to install the OTA. This looks like a promising second option.
PhilD41 said:
Any idea if this will work with an encrypted phone? I believe the data partition is the only one encrypted. Mine is throwing an error trying to install the OTA. This looks like a promising second option.
Click to expand...
Click to collapse
When installing the OTA via stock recovery (i.e. have OTA.zip on the /SDCard, boot to stock recovery, select install update and pick the OTA.zip) it will tell you exactly why the install is failing.
With the phone being encrypted, I would only consider doing the OTA. Doing an FXZ will over write the system and other partitions, any phone encryption settings will likely be lost.
If you do try FXZ, please copy your data to your PC FIRST!!!! just in case!!
samwathegreat said:
...He's offline. Do you want me to help you? I HAVE all the linux tools, and know how to do this. KidJoe only uses Windows...
DONE! And your data should still be intact....if you would PREFER to wipe your data, add the following command BEFORE "fastboot reboot"
fastboot erase userdata
Click to expand...
Click to collapse
Thanks samwathegreat!!! That worked like a champ. Flashed the set, flashed TWRP, rooted, installed xposed and updated my build.prop. Data and encryption untouched and working as expected. Thanks again for the assistance!!!
PhilD41 said:
Thanks samwathegreat!!! That worked like a champ. Flashed the set, flashed TWRP, rooted, installed xposed and updated my build.prop. Data and encryption untouched and working as expected. Thanks again for the assistance!!!
Click to expand...
Click to collapse
Thanks for the update. I'm very glad it all worked out
TO ANYONE ELSE WHO COMES ACROSS THIS THREAD:
The VZW 4.4.4 FXZ is ****NO LONGER**** A "keep data" FXZ. If you download the FXZ now, you will need to modify the XML file and remove the line containing "erase userdata" if you want to prevent all of your data from being erased.
Just to clear it up: The original leaked FXZ was indeed a keep-data FXZ and did not have the lines for erasing userdata.
NOW that the new official FXZ has leaked, it DOES contain the erase userdata command.
Other than the slightly modified XML (used for flashing), ***ALL OF THE PARTITIONS ARE EXACTLY THE SAME***
So anyone who used the "old" FXZ - Don't worry! You are NOT using a outdated version, and you don't need to flash the new one. They are 100% identical aside from the additional command to erase userdata.
Related
I'm currently rooted and am running only Xposed Mods with a few root apps. How can I unroot my phone and get the stock recovery back onto my Moto X so that I can take OTA's again without wiping all of my data? What files do I need to download/flash and how do I do it? I've searched around, but it just got me even more confused.
bd1212 said:
I'm currently rooted and am running only Xposed Mods with a few root apps. How can I unroot my phone and get the stock recovery back onto my Moto X so that I can take OTA's again without wiping all of my data? What files do I need to download/flash and how do I do it? I've searched around, but it just got me even more confused.
Click to expand...
Click to collapse
Someone correct me if I'm wrong, but I believe that flashing the stock system will remove all the changes you've made with root/xposed modules, and flashing the stock recovery should essentially get rid of root (I think).
I don't know precisely where to get all the files, but if you find them around, you can push them using ADB.
If you're like me and are okay with losing everything on the phone, go ahead and use RSDLite (it requires ADB). It's easy-ish to use, and there's even a video tutorial that covers everything after installation of all the files.
You need to use fastboot to push system.img and recovery.img from the version of the OS you're currently running. See here for a list of OS images:
http://sbf.droid-developers.org/ghost_rcica/list.php
See this thread for a link to a fastboot.exe that'll work:
http://forum.xda-developers.com/showthread.php?t=2527287
See this thread for a quick overview and link to more detailed info:
http://forum.xda-developers.com/showthread.php?t=2525495&page=4
jonnythan said:
You need to use fastboot to push system.img and recovery.img from the version of the OS you're currently running. See here for a list of OS images:
http://sbf.droid-developers.org/ghost_rcica/list.php
See this thread for a link to a fastboot.exe that'll work:
http://forum.xda-developers.com/showthread.php?t=2527287
See this thread for a quick overview and link to more detailed info:
http://forum.xda-developers.com/showthread.php?t=2525495&page=4
Click to expand...
Click to collapse
Thanks for the info and links. I'm currently downloading the OS that I'm currently running (VZW OTA update in my case), but I have one question: How do I use fastboot? When I double click that .exe nothing happens.
bd1212 said:
Thanks for the info and links. I'm currently downloading the OS that I'm currently running (VZW OTA update in my case), but I have one question: How do I use fastboot? When I double click that .exe nothing happens.
Click to expand...
Click to collapse
You need to install the Android SDK and the platform tools, then boot your phone into fastboot mode. You need to run a command line to flash the IMGs. It's explained in the links.
meant2live218 said:
Someone correct me if I'm wrong, but I believe that flashing the stock system will remove all the changes you've made with root/xposed modules, and flashing the stock recovery should essentially get rid of root (I think).
I don't know precisely where to get all the files, but if you find them around, you can push them using ADB.
If you're like me and are okay with losing everything on the phone, go ahead and use RSDLite (it requires ADB). It's easy-ish to use, and there's even a video tutorial that covers everything after installation of all the files.
Click to expand...
Click to collapse
I was under the impression that we cannot do a factory reset or we won't get the soak test OTA pushed to our phones. That's what the soak test post said atleast. Something along the lines of "DO NOT FACTORY RESET or you will not receive the OTA"... don't want to quote it directly since I'm under an NDA, but it was something like that. Did I misunderstand? If I use the Moto X toolkit or RSDLite to revert back to stock is that different than a factory reset?
jonnythan said:
You need to install the Android SDK and the platform tools, then boot your phone into fastboot mode. You need to run a command line to flash the IMGs. It's explained in the links.
Click to expand...
Click to collapse
I've got the Android SDK install and ADB is setup. I'm pretty familiar with ADB. I moved the motorola fastboot.exe into platform-tools and I know how to put the phone into fastboot mode. What I don't understand is what I need to do once I've got the system.img file and the recovery.img file. I'm still reading all of the links so I might not have gotten to the part where it explains what to do, so forgive me for that.
bd1212 said:
I've got the Android SDK install and ADB is setup. I'm pretty familiar with ADB. I moved the motorola fastboot.exe into platform-tools and I know how to put the phone into fastboot mode. What I don't understand is what I need to do once I've got the system.img file and the recovery.img file.
Click to expand...
Click to collapse
Right from my third link:
Next, you need to put the phone into "fastboot mode" as described above, also make sure usb debugging is enabled in the developer menu settings. Then download the FW for your phone found (follow what i said in regards to the other persons post below), then unzip that, put the system and recovery image in the same directory that your fastboot and adb is in, then run these commands from the cmd prompt
fastboot flash system system.img
fastboot flash recovery recovery.img
then your done, you can type
fastboot reboot
Click to expand...
Click to collapse
jonnythan said:
Right from my third link:
Click to expand...
Click to collapse
Yep, just got to that part lol. Having some trouble downloading the VZW file. My current download just stopped with a network error and the website that is hosting the files keeps saying service unavailable and to contact the website administrator. Weird. I'm blaming it on my college's ****ty wireless network.
Edit: Yup, for some reason the wifi at the school decided it need me to input my credentials to re-login for the 6th time today to verify who I am and allow me internet access.
Edit 2: The things I'd do to have a stable connection... Once again, the download failed halfway through because the damn connection at this college sucks. This is infuriating.
jonnythan said:
Right from my third link:
Click to expand...
Click to collapse
Is there anyway you (or someone else) could upload the VZW OTA update file to Google Drive or Dropbox for me? This download is going way to slow to the point where I can't even finish it before my connection craps out. Or can you (or someone else) just upload the system.img and recovery.img files for me?
bd1212 said:
Is there anyway you (or someone else) could upload the VZW OTA update file to Google Drive or Dropbox for me? This download is going way to slow to the point where I can't even finish it before my connection craps out. Or can you (or someone else) just upload the system.img and recovery.img files for me?
Click to expand...
Click to collapse
Uploading now, but it'll take a bit. Big file.
jonnythan said:
Uploading now, but it'll take a bit. Big file.
Click to expand...
Click to collapse
Thanks man. You don't even know how much I appreciate this.
Which one of the two is the camera update for vzw?
Where do you get stock recovery?
EDIT: Sorry, Nevermind. I probably extract it from the zip.
Sent from my XT1060 using xda app-developers app
any one using the rogers and know when will the update for 4.4?
yghrv said:
any one using the rogers and know when will the update for 4.4?
Click to expand...
Click to collapse
I gave up weeks ago waiting for the rogers(robbers) update, flashed the tmobile sbf 4.4 firmware on my unlocked boot loader moto. The way I see it we're probably last to receive the update, US done , now South Americian carriers, so assume sometime in January
Sent on my Moto X
flashallthetime said:
I gave up weeks ago waiting for the rogers(robbers) update, flashed the tmobile sbf 4.4 firmware on my unlocked boot loader moto. The way I see it we're probably last to receive the update, US done , now South Americian carriers, so assume sometime in January
Sent on my Moto X
Click to expand...
Click to collapse
disappoint about that, the first Moto X was saled with Rogers and then turns out to be the last one to update....
Also running the dev edition/retail firmware - it is totally the way to go. Forget about Rogers. I suspect Motorola already compiled 4.4 for them and they are sitting on it like they did the camera update. The only feature the Rogers firmware will likely offer is LTE on/off in the menu. I can't think of anything else it has going for it.
Running the retail version also gets rid of the carrier name in the upper left which is just silly to have anyway.
Should I unlock my bootloader? What does the warranty cover anyways?
alu0506 said:
Should I unlock my bootloader? What does the warranty cover anyways?
Click to expand...
Click to collapse
Well if the hardware was to fail such as the headphone jack breaking, ram going bad, speaker crapping out etc it would be covered under warranty. Once you request the bootloader unlock key that is gone. I figured since my phone was solid for more then a month and being I bought it used anyway I didn't have much to lose by unlocking the bootloader. For me it was the right move, used phones are getting cheaper on craigslist everyday if it does break and has to be replaced.
Yeah, I just checked. It doesn't cover physical damages so I'm gonna unlock the boot loader and maybe flash the Dev version.
Sent from my XT1058 using Tapatalk
alu0506 said:
Yeah, I just checked. It doesn't cover physical damages so I'm gonna unlock the boot loader and maybe flash the Dev version.
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
Sounds good - any problems or questions let me know!
Steve-x said:
Sounds good - any problems or questions let me know!
Click to expand...
Click to collapse
Got it unlocked! What should I flash.... hmmm....
alu0506 said:
Got it unlocked! What should I flash.... hmmm....
Click to expand...
Click to collapse
Try this first:
http://sbf.droid-developers.org/download.php?device=0&file=2
Works well on my Rogers phone, if you decide to flash one of the kitkat customs roms, you need the kitkat modems
Sent on my Moto X Running Beanstalk 4.4.2
Steve-x said:
Try this first:
http://sbf.droid-developers.org/download.php?device=0&file=2
Click to expand...
Click to collapse
What is it exactly? Is it pre-rooted or should I flash supersu?
alu0506 said:
What is it exactly? Is it pre-rooted or should I flash supersu?
Click to expand...
Click to collapse
It is the retail/dev edition 4.4 kitkat rom. It is 100% stock as released by Motorola, you can root it after installing.
alu0506 said:
What is it exactly? Is it pre-rooted or should I flash supersu?
Click to expand...
Click to collapse
Its not a ROM but the stock firmware, it flashes the boot loader, stock recovery, modems and system files after it boots you can then flash twrp recovery for kitkat and flash supersu
Sent on my Moto X Running Beanstalk 4.4.2
Oh no.... I made have made a little oops.
I flashed everything and then selected normal powerup.
Booted to the warning screen, vibrated and got stuck...
[EDIT 1] GOT IT TO BOOT TO BOOTLOADER WOOT FLASHING AGAIN
[EDIT 2] Reflashed again... is it supposed to be at the warning screen for a long time after first reboot?
If you're in the bootloader I'd flash it again, may have been a failure in the data transfer.
Steve-x said:
If you're in the bootloader I'd flash it again, may have been a failure in the data transfer.
Click to expand...
Click to collapse
I redownloaded it and reflashed and IT BOOTED! YAY! THANK YOU!
process
What's the exact process to flash this file. Do I need custom recovery first? If you could list the steps for me that would be awesome.
gthompson75 said:
What's the exact process to flash this file. Do I need custom recovery first? If you could list the steps for me that would be awesome.
Click to expand...
Click to collapse
Well this is what I did:
Step 1. Download the latest drivers and adb/fastboot
If you already have the android adk installed, go to https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481 and download and install the latest drivers. Otherwise try this http://forum.xda-developers.com/showthread.php?t=2588979. I have never used it before but it looks like it should install both adb/fastboot and their corresponding drivers.
Step 2. Download mfastboot.exe
Go to https://drive.google.com/file/d/0B-SutxHydqfNczVMVXNtRVI4ZW8/edit?usp=sharing and download the file. This is motorola fastboot. You use it in place of the fastboot that came with the android sdk. For some reason, the fastboot that comes with the android SDK seems to not work when flashing some things. Download the file and save it somewhere.
Step 3. Download the Retail/Dev 4.4 rom
Thanks Steve-x for showing me this!
http://sbf.droid-developers.org/download.php?device=0&file=2
Download this file and unzip it.
Step 4. Unlock the bootloader
Go to https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a/action/auth and follow the instructions to have a unlock code mailed to you. Remember, this will void your warranty AND WILL WIPE YOUR DATA. REMEMBER TO DO A BACKUP! I DIDN'T AND IT WAS A REALLY BAD MISTAKE.
Step 5. Flash the Retail/Dev rom
Remember that mfastboot.exe file that you downloaded earlier? Well it’s time to put it to good use. Copy (or move) the file to the directory where the rest of the Retail/Dev 4.4 rom files are located. (The zip that you extracted earlier, the one with the “system.img” in it?)
Now that you've done that, open “TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_CFC.bat” with your favorite plain text editor. (Use notepad if you have no favorite) We have to make it so that instead of using the standard android fastboot.exe to flash the files, it uses the mfastboot.exe. So, just edit the first line, “SET fastboot=fastboot.exe”, to “SET fastboot=mfastboot.exe”. Save and close it up.
Now, put your Moto X into bootloader mode if it isn't already. Power it down and then press the power and volume down buttons simultaneously until it powers on. Connect the usb cable to the computer, and wait for the pc to recognize everything. Now double-click on the “TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_CFC.bat” and it will start flashing.
After it is complete, turn the phone on by selecting “Normal Powerup” on the device. To navigate around the bootloader, use the volume down arrow key to select the option and the volume up key to execute it. If everything went correctly, your Moto X show powerup and boot into Android 4.4!
I think thats everything. If you need help please do ask!
---------- Post added at 05:17 PM ---------- Previous post was at 05:14 PM ----------
gthompson75 said:
What's the exact process to flash this file. Do I need custom recovery first? If you could list the steps for me that would be awesome.
Click to expand...
Click to collapse
Oh right, if you want a custom recovery and root, this thread explains the process nicely http://forum.xda-developers.com/showthread.php?t=2603358
Thanks,
alu0506 said:
Well this is what I did:
Step 1. Download the latest drivers and adb/fastboot
If you already have the android adk installed, go to https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481 and download and install the latest drivers. Otherwise try this http://forum.xda-developers.com/showthread.php?t=2588979. I have never used it before but it looks like it should install both adb/fastboot and their corresponding drivers.
Step 2. Download mfastboot.exe
Go to https://drive.google.com/file/d/0B-SutxHydqfNczVMVXNtRVI4ZW8/edit?usp=sharing and download the file. This is motorola fastboot. You use it in place of the fastboot that came with the android sdk. For some reason, the fastboot that comes with the android SDK seems to not work when flashing some things. Download the file and save it somewhere.
Step 3. Download the Retail/Dev 4.4 rom
Thanks Steve-x for showing me this!
http://sbf.droid-developers.org/download.php?device=0&file=2
Download this file and unzip it.
Step 4. Unlock the bootloader
Go to https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a/action/auth and follow the instructions to have a unlock code mailed to you. Remember, this will void your warranty AND WILL WIPE YOUR DATA. REMEMBER TO DO A BACKUP! I DIDN'T AND IT WAS A REALLY BAD MISTAKE.
Step 5. Flash the Retail/Dev rom
Remember that mfastboot.exe file that you downloaded earlier? Well it’s time to put it to good use. Copy (or move) the file to the directory where the rest of the Retail/Dev 4.4 rom files are located. (The zip that you extracted earlier, the one with the “system.img” in it?)
Now that you've done that, open “TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_CFC.bat” with your favorite plain text editor. (Use notepad if you have no favorite) We have to make it so that instead of using the standard android fastboot.exe to flash the files, it uses the mfastboot.exe. So, just edit the first line, “SET fastboot=fastboot.exe”, to “SET fastboot=mfastboot.exe”. Save and close it up.
Now, put your Moto X into bootloader mode if it isn't already. Power it down and then press the power and volume down buttons simultaneously until it powers on. Connect the usb cable to the computer, and wait for the pc to recognize everything. Now double-click on the “TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_CFC.bat” and it will start flashing.
After it is complete, turn the phone on by selecting “Normal Powerup” on the device. To navigate around the bootloader, use the volume down arrow key to select the option and the volume up key to execute it. If everything went correctly, your Moto X show powerup and boot into Android 4.4!
I think thats everything. If you need help please do ask!
---------- Post added at 05:17 PM ---------- Previous post was at 05:14 PM ----------
Oh right, if you want a custom recovery and root, this thread explains the process nicely http://forum.xda-developers.com/showthread.php?t=2603358
Click to expand...
Click to collapse
Thank you for the detailed info. When updates come out will we get them rogers or tmob/retail
Long story, but I lost my /system folder on my stock Att xt1058 running 4.4.2.
I have an unlocked bootloader.
Can anyone upload to a Dropbox, or somewhere else, just the system partition so I can restore via nandroid on TWRP? Otherwise I am stuck waiting for the SBF, since I can no longer downgrade.
Thanks
Sent from my Moto X using Tapatalk
Well...
This is untested, but it is a flashable zip that I made from a dump of my ATT 4.4.2 /system. The kernel is included within the zip, but it is not automatically flashed, and you will need to use fastboot to flash it. (I intended this to be used with safestrap..)
165.44.1.ghost_att: http://www.androidfilehost.com/?fid=23329332407581236
Let me know if this flashable zip works. I will post it with the instructions for locked bootloaders...
Will work on this in a few hours.
Just so I am clear, flash zip in recovery, pull boot.img out of the zip, and flash boot.img manually via fastboot. Right?
Sent from my Moto X using Tapatalk
cpetersen2791 said:
Will work on this in a few hours.
Just so I am clear, flash zip in recovery, pull boot.img out of the zip, and flash boot.img manually via fastboot. Right?
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
Exactly.
I see it was downloaded 9 times before me. I didn't have any luck with both TWRP and Philz's recovery. Flash stalled on "extracting system files" for 5+ minutes.
I would take the entire TWRP backup if you can upload that.
UPDATE: I deleted the boot.img out of the zip file, and it flashed, then manually flashed boot.img.
UPDATE 2: No radio, nor wifi to connect...Suggestions? I feel i am so close!
Ctrl-Freak said:
Well...
This is untested, but it is a flashable zip that I made from a dump of my ATT 4.4.2 /system. The kernel is included within the zip, but it is not automatically flashed, and you will need to use fastboot to flash it. (I intended this to be used with safestrap..)
165.44.1.ghost_att
Let me know if this flashable zip works. I will post it with the instructions for locked bootloaders...
Click to expand...
Click to collapse
OMG, I think this file will help me to rescue my brick!!!!!
Can I manually flash this firmware on my device using fastboot tool?I have no idea about what safestrap is,please no hate.
It's still a WIP, after flashing, I didn't have radio. Will work on that tomorrow. If we get it going, I'll post something, with Ctrl-Freak's approval.
Sent from my Moto X using Tapatalk
Ctrl-Freak said:
Exactly.
Click to expand...
Click to collapse
I download your zip and find out this is not a firmware...OTZ
I can only wait until the sbf file released.
cpetersen2791 said:
UPDATE 2: No radio, nor wifi to connect...Suggestions? I feel i am so close!
...
It's still a WIP, after flashing, I didn't have radio...
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
I can say that the 4.4 modem works fine with 4.4.2. Are you running a 4.4.x modem? If so, you might be experiencing "the radio" problem (One symptom, is that it shows "unknown" in status.)
This radio problem has plagued me in safestrap. No matter what 4.4.x rom I tried to flash, if I was already running 4.4.x, I could not TWRP /system, fastboot boot.img and keep a working radio. I had no idea the problem might persist with an unlocked bootloader's TWRP.
In the past, to fix the radio problem, I always need to downgrade to 4.2.2 (using fastboot->system, boot, modem and recovery.) Then I root, safestrap, load 4.4.x rom using safestrap's TWRP, then fastboot radio and kernel. After that the radio problem disappears.
However... Other people seem to be successful by doing a factory reset in safestrap's TWRP. For instance, look at these instructions: http://forum.xda-developers.com/moto-x/development/rom-krypton-v1-1-4-13-2014-t2716657
Safestrap Version
-If you are already on 4.4.2 then boot into Safestrap and factory reset, do not wipe the system then install to the STOCK slot.
-If your not on 4.4.2 then go here and follow the instructions from my stock rom thread http://rootzwiki.com/topic/116025-ro...52-kitkat-442/ I don't feel like reposting them in here.
Click to expand...
Click to collapse
Previously, I looked at a rom that was intended for the above instructions. That rom basically did the same as mine: It formatted and loaded /system.
Ctrl-Freak said:
I can say that the 4.4 modem works fine with 4.4.2. Are you running a 4.4.x modem? If so, you might be experiencing "the radio" problem (One symptom, is that it shows "unknown" in status.)
This radio problem has plagued me in safestrap. No matter what 4.4.x rom I tried to flash, if I was already running 4.4.x, I could not TWRP /system, fastboot boot.img and keep a working radio. I had no idea the problem might persist with an unlocked bootloader's TWRP.
In the past, to fix the radio problem, I always need to downgrade to 4.2.2 (using fastboot->system, boot, modem and recovery.) Then I root, safestrap, load 4.4.x rom using safestrap's TWRP, then fastboot radio and kernel. After that the radio problem disappears.
However... Other people seem to be successful by doing a factory reset in safestrap's TWRP. For instance, look at these instructions: http://forum.xda-developers.com/moto-x/development/rom-krypton-v1-1-4-13-2014-t2716657
Previously, I looked at a rom that was intended for the above instructions. That rom basically did the same as mine: It formatted and loaded /system.
Click to expand...
Click to collapse
Those are all Verizon Radio's. Do you think I can grab the ATT version 4.4 radio and manually flash? I have that sbf available. Or will the Verizon work in an ATT xt1058
cpetersen2791 said:
Those are all Verizon Radio's. Do you think I can grab the ATT version 4.4 radio and manually flash? I have that sbf available. Or will the Verizon work in an ATT xt1058
Click to expand...
Click to collapse
Sorry. I wasn't telling you to get that rom or the Verizon radio, I was pointing out that a factory reset in TWRP may help with the radio issue.
Long story, but I lost my /system folder on my stock Att xt1058 running 4.4.2.
Click to expand...
Click to collapse
So I am guessing that you took the OTA to originally get to 4.4.2. You should already be running that modem. If that is true, I would not change it.
Ctrl-Freak said:
So I am guessing that you took the OTA to originally get to 4.4.2. You should already be running that modem. If that is true, I would not change it.
Click to expand...
Click to collapse
I factory reset prior to installing, should i wipe /system as well? I am running AOSP roms (PAC) now, and there is no problem with the radio.
I took the OTA, so I dunno what the radio problem would be. Wifi wouldn't turn on either, so i dunno if it's just a radio issue.
i am fortunate to be unlocked bootloader, so i got a copy of the GPE xt1053 posted here as well, and it appears it will work. I think i am gonna try to flash that, then your files w/o a wipe. How does that sound? Unless you got other ideas.
cpetersen2791 said:
I factory reset prior to installing, should i wipe /system as well? I am running AOSP roms (PAC) now, and there is no problem with the radio.
I took the OTA, so I dunno what the radio problem would be. Wifi wouldn't turn on either, so i dunno if it's just a radio issue.
i am fortunate to be unlocked bootloader, so i got a copy of the GPE xt1053 posted here as well, and it appears it will work. I think i am gonna try to flash that, then your files w/o a wipe. How does that sound? Unless you got other ideas.
Click to expand...
Click to collapse
I do not fully understand the radio/wifi issue, so all of my ideas would be trial and error. Give your plan a go and let us know. I would love to know what causes this issue, as a solution should help us using safestrap.
Another thought. Maybe I have to flash the radio, even though I haven't changed. Kind of like flashing the boot.img. I haven't changed that either, but it had to be flashed to boot.
Do you know where I can grab the radio IMG? Can't seem to find it around.
I supposed I can pull it from Att 4.4 sbf. Which files tho, just the Non-hlos.bin file? I don't have the xml here @ the office so I don't know what to look for.
Thanks again for your help
Sent from my Moto X using Tapatalk
Ctrl-Freak said:
I do not fully understand the radio/wifi issue, so all of my ideas would be trial and error. Give your plan a go and let us know. I would love to know what causes this issue, as a solution should help us using safestrap.
Click to expand...
Click to collapse
Found this...
it's OS 4.4 (140.44.5), will that run into the brick issue?
Hi all!
Sorry for bothering you. I'm a complete noob and I've bought my XT1097 just 4 days ago. I just want to request to some of the hard core guys here if you can do a noob friendly guide describing the process to transform a XT1097 or XT1092 into a the Pure Edition XT1095. I know there is a tiny explanation in one post, but as I told you, I'm a noob and for what I've read if you don't do the right thing you loose signal.
I just love so much this phone and is brand new, and I don't want to break it
Thanks so much in advance :fingers-crossed:
You have to find it yourself. If you're not able to find guides that already exists then you really shouldn't try to flash your device.
Judge584 said:
You have to find it yourself. If you're not able to find guides that already exists then you really shouldn't try to flash your device.
Click to expand...
Click to collapse
No man, is not that I can not find it. There is none yet...the one that is around there is not clear and "noob friendly", that is why I'm requesting a "noob friendly" one...
Anyways, sorry of my request bothered you, I'm just asking politely for help, that is all.
Cheers man
You don't bother me but all information is already here, it's not that hard. All you have to do is learn, and if you have never flashed a device before it should take no more than a day to figure out how it works.
I will happily try and help you out -- everyone is new at one point or another. Give me about a day or so to try and compile the resources I personally used when I did mine!
justblais said:
I will happily try and help you out -- everyone is new at one point or another. Give me about a day or so to try and compile the resources I personally used when I did mine!
Click to expand...
Click to collapse
Thanks a lot man!!! No rush, take your time. Thanks again!
you could use the multitool
flashing the stock PE xt1095 from there worked for me
however you need to be prepared in case you brick your device by any chance
try downloading android emulator and play around with it first (just a suggestion)
nicromant said:
you could use the multitool
flashing the stock PE xt1095 from there worked for me
however you need to be prepared in case you brick your device by any chance
try downloading android emulator and play around with it first (just a suggestion)
Click to expand...
Click to collapse
Thanks man! you had the XT1097 before converting it with the multi tool?
yes it was a retail latam xt1097 with the tool you can convert it to xt1095 and flash the OTA you just need to be cautious with the modem section of it otherwise you will need to reflash again using fastboot and the std retail image with adequate version for your device
I'm pretty sure this post should do the trick, however make sure you use your correct modem as the one posted there is for the XT1092.
benjamin.j.goodwin said:
I didn't get the OTA through my phone, just flashed it.
I did have a modem issue so lost all signal but I fixed it. If you can live without it for a while then you should be fine.
Here is what I did.
0. Download Multi-Tool, XT1092 Modem, Lollipop OTA
1. Enable USB debugging.
2. Use the Multi-Tool to go back to KK stock, full wipe option. *this will most likely **** up your modem, don't worry*
3. Reboot with the stock, enable USB debugging again.
4. Move the OTA zip to your SD card on your phone.
4. Use a CMD window in the Multi-Tool directory to 'adb reboot recovery' if you use Mac './adb reboot recovery'
5. Once in recovery press volume up for three seconds, then press the power button along with it. A menu should appear.
6. Navigate to 'apply update from zip' or whatever it says, not the ADB option.
7. It should flash. Once it's done, reboot. You won't have signal still but don't worry. All in good time.
8. Factory reset after the first boot, don't sign in or anything.
9. Once you have booted again after the reset enable USB debugging again.
10. Reboot to bootloader so 'adb reboot bootloader' or if Mac './adb reboot bootloader'
11. Let's get our signal back.
12. Unzip the contents of the XT1092 modem zip. You will need to type the following:
Code:
'mfastboot flash modem NON-HLOS.bin'
'mfastboot erase modemst1'
'mfastboot erase modemst2'
'mfastboot flash fsg fsg.mbn'
13. Then 'fastboot reboot'
NB: To do points 12 and 13, you will be best to copy the relevant files from the Multi-Tool into the XT1092 modem unzipped directory.
You should now have Lollipop. Root if you want after. It's essentially official too. I did amend my build.prop after as it does state XT1095 as the device which is wrong.
Click to expand...
Click to collapse
Same steps can be applyed to a XT1097? Just have to extract the correct modem firmware for my device?
Thanks!
Edit: Sorry, just skimmed through the text and didn't saw this was mentioned already.
Another question though, doing this procedure needs an unlocked bootloader? Even if not, this qualifies as a awaranty void?
Thanks any way for the gruide!
danielcbit said:
Same steps can be applyed to a XT1097? Just have to extract the correct modem firmware for my device?
Thanks!
Edit: Sorry, just skimmed through the text and didn't saw this was mentioned already.
Another question though, doing this procedure needs an unlocked bootloader? Even if not, this qualifies as a awaranty void?
Thanks any way for the gruide!
Click to expand...
Click to collapse
you do need an unlocked bootloader as far as I understand... I wanted to try it but backing up my modem files first... at least that required an unlocked bootloader, so I decided not to try it yet...
use TWRP it is better to upgrade to preserve baseband and modem cfg, however you can also use full fastboot flashing and reinstall your modem settings, i used twrp and no major issues so far...
I am trying to apply an update that was pushed to my Verizon Nexus 6. I was using Nexus Root Toolkit V2.0.5 developed by Wug, to do the unroot and re-lock the boot loader. It went fine no issues, have the correct build of android plugged into the toolkit. Rebooted, and I used root checker to verify that root is gone, and it is not, it is still rooted. I can unroot using supersu, and root checker confirms that root is gone. After locking the bootloader, I go and try to apply the update and it still fails. I am able to restart the phone and use it, but I do not understand what is going on with it. Anybody have any thoughts?
FireMedic1234 said:
I am trying to apply an update that was pushed to my Verizon Nexus 6. I was using Nexus Root Toolkit V2.0.5 developed by Wug, to do the unroot and re-lock the boot loader. It went fine no issues, have the correct build of android plugged into the toolkit. Rebooted, and I used root checker to verify that root is gone, and it is not, it is still rooted. I can unroot using supersu, and root checker confirms that root is gone. After locking the bootloader, I go and try to apply the update and it still fails. I am able to restart the phone and use it, but I do not understand what is going on with it. Anybody have any thoughts?
Click to expand...
Click to collapse
for the couple thousandth time it has been mentioned here, you can not apply an update if any stock files have been changed. with you having root at one point, your files have been changed. and to really unroot, you have to flash a factory image. otherwise, even tjough you unrooted, your files are still changed.
simms22 said:
for the couple thousandth time it has been mentioned here, you can not apply an update if any stock files have been changed. with you having root at one point, your files have been changed. and to really unroot, you have to flash a factory image. otherwise, even tjough you unrooted, your files are still changed.
Click to expand...
Click to collapse
Yeah hey thanks hadn't seen that a million times or so. I know updates cannot be flashed while rooted or unlocked. I am trying to unroot by flashing a factory image and it is not taking, no errors come up in the log and it reboots fine.
FireMedic1234 said:
Yeah hey thanks hadn't seen that a million times or so. I know updates cannot be flashed while rooted or unlocked. I am trying to unroot by flashing a factory image and it is not taking, no errors come up in the log and it reboots fine.
Click to expand...
Click to collapse
are you using fastboot while you are in your bootloader? oh, and you need an unlocked bootloader as well.
simms22 said:
are you using fastboot while you are in your bootloader? oh, and you need an unlocked bootloader as well.
Click to expand...
Click to collapse
Yes I am. I had locked the bootloader and tired to apply the update and that didn't work. I currently have an unlocked boot but did not root yet, was waiting for feedback from here.
FireMedic1234 said:
Yes I am. I had locked the bootloader and tired to apply the update and that didn't work. I currently have an unlocked boot but did not root yet, was waiting for feedback from here.
Click to expand...
Click to collapse
ok, boot into the bootloader, connwct via usb to your computer, the type fastboot devices. at that point, it should list your phone via a number. if it does, then its all connected right. then you can flash the factory image, but do not use the flash-all script, flash them all individually.
Ok thanks, Does it work the same if you do it through Wugs tool, clicking the flash stock + unroot button, and letting it run the scripts?
FireMedic1234 said:
Ok thanks, Does it work the same if you do it through Wugs tool, clicking the flash stock + unroot button, and letting it run the scripts?
Click to expand...
Click to collapse
ill be honest.. its best to do it the first time manually. that way you learn to do things that can fix your phone in the future, plus tool kits can and fo mess up occasionally, which make things hard to fix. i tell everyone that they can use toolkits, but they wont learn anything and will remain clueless. if you already know what you are doing, then tool kits are fine
I concur. I have used "the" toolkit to see what happens. Have had multiple failures using toolkit and always had to revert to fastboot to fix. Might as well use fastboot up front. Saves a lot of time and headaches.
simms22 said:
ill be honest.. its best to do it the first time manually. that way you learn to do things that can fix your phone in the future, plus tool kits can and fo mess up occasionally, which make things hard to fix. i tell everyone that they can use toolkits, but they wont learn anything and will remain clueless. if you already know what you are doing, then tool kits are fine
Click to expand...
Click to collapse
Gotcha thanks again!
When I try to flash system.img it errors out saying it is not there, but it is. any thoughts?
FireMedic1234 said:
When I try to flash system.img it errors out saying it is not there, but it is. any thoughts?
Click to expand...
Click to collapse
You can drag and drop or copy/paste the image into the command line.
FireMedic1234 said:
When I try to flash system.img it errors out saying it is not there, but it is. any thoughts?
Click to expand...
Click to collapse
are you flashing with flash-all or are you flashing each image individually. dont use flash-all, flash them individually.
Share a screen print of the command prompt, with the command you executed, and the error message?
was doing the flash-all. is the command "fastboot flash system system.img" minus the quotes? If that doesn't work I will try and drop and drag see if that works
FireMedic1234 said:
was doing the flash-all. is the command "fastboot flash system system.img" minus the quotes? If that doesn't work I will try and drop and drag see if that works
Click to expand...
Click to collapse
Yes.
FireMedic1234 said:
When I try to flash system.img it errors out saying it is not there, but it is. any thoughts?
Click to expand...
Click to collapse
You don't need to put the system.img there. Please do read general > sticky roll-up thread > adb and fastboot...
...some time.
I guess my issue was in my head. I am so damn concerned that I am going to do something wrong and brick the phone that I am afraid to run the commands. I just flashed the system.img had it write in 4 different parts.... and it worked fine, rebooted and everything.... so far.
FireMedic1234 said:
I guess my issue was in my head. I am so damn concerned that I am going to do something wrong and brick the phone that I am afraid to run the commands. I just flashed the system.img had it write in 4 different parts.... and it worked fine, rebooted and everything.... so far.
Click to expand...
Click to collapse
Yes the flash-all.bat can't break up the image. Has something to do with how it sees the partition. Have heard that fastboot in SDK 23+ has fixed this problem. Have not confirmed as I do each individually anyway depending on what I want to do.
---------- Post added at 12:13 PM ---------- Previous post was at 12:07 PM ----------
Only way you're gonna possibly brick is flash wrong image to wrong partition. Not sure that even that can be corrected with fastboot as long as the one you bork isn't the bootloader.