Related
NOTE, YES, THIS IS A LONG DRAWN OUT VERSION OF WHAT IS ACTUALLY VERY VERY QUICK PROCESS. This is for reference only. I know there are a few people out there just like me who probably had a few small hickups getting back to stock with the firmware. This is to help "spoon-feed" the instructions to you.
FYI NOTE - I originally did this for the Moto X back when I still had it. Video below was on a VZW Moto X back in September. I also did the EXACT same process when I received my MAXX two days ago. Exact same hardware, same process.
Two Methods-
Method 1 - RSD Lite
Method 2 - Manual Flash
If you cannot get RSD Lite to recognize your device, try Method 2, it works like a charm!
Downloads:
I assume you already have adb drivers if you're even here.....otherwise get them from the latest sdk here: http://developer.android.com/sdk/index.html
Moto Drivers (Motorola Device Manager): https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
RSD Lite (I used version 6.1.5): https://dl.dropboxusercontent.com/u/42057363/RSDLite_v6.1.x.zip - Extract and use 6.1.5
Stock Firmware: http://sbf.droid-developers.org/ thanks to Skrilax_CZ and Firmware Team
Moto Fastboot exe: https://drive.google.com/file/d/0B0dUKGxGylgNTk43eU0xc3VLekE/edit?usp=sharing - NOTE - YOU MUST UNZIP AND USE THIS WHERE MANUAL FLASH SAYS "mfastboot"
My Setup: Windows 8 machine <--obvious driver issues as usual
My Devices: VZW Moto X AND Droid MAXX
METHOD 1 - RSD LITE
Step One - Download and install RSD Lite. At the moment, I can't find where I got mine from, so anyone who wants to add a proper link to it would be appreciated. I used version 6.1.5 and it worked fine.
Step Two - proper driver installation. If you're like me, you probably at one point got drivers quasi-working but here's what I did that worked - download and install "Motorola Device Manager" and it *should* give you the proper drivers. This was necessary (maybe) because I could get adb to recognize my device, as well as fastboot, however RSD refused to see it. This install fixed that.
Step Three - download and install the proper firmware for your device. NOTE: You MUST MUST MUST choose the right firmware for your device or you will FUBAR your phone.....not my responsibility.
Step Four - Unzip your firmware zip file, open it up through the layers and find the file "VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF" or whatever version/carrier/build number file yours is, its the XML Document file. Right click -> Open with.. -> Notepad/word editor/XML Editor/wordpad and find the line:
<step operation="getvar" var="max-download-size" />
^^^You need to select this entire line and just delete it out of the file. This is the line that gives fastboot flash error. Select it, delete it, then resave the file an exit out of it. Done.
NOTE: This is required or the firmware flash will immediately fail giving a "failed flashing process. Unknown fastboot command. (getvar)"
-For the sake of security, and not messing with important files, I'd actually recommend zipping the file back up after this and keeping as your final version (once you've confirmed yours works correctly)
Step Five - Plug in phone, enable USB debugging, then "adb reboot bootloader" - this will boot you into fastboot mode so RSD will recognize your phone
Step Six - Run RSD Lite - note that some people have had trouble and have to right-click run as administrator. In RSD Lite, make sure phone shows up in slot 1 - mine shows up, under Model, just says fastboot, USB port type, info N/A, important part is that it shows as Connected in status. Select the three-dot browse file button, then you can go down into the unzipped file you created of the XML folder, and select the XML file that we just edited earlier (or select the rezipped package). Select open and flash. (or decompress and flash)
Step Eight - Profit
METHOD 2 - MANUAL FLASHING
Much easier AND don't have to deal with getting RSD Lite to work....
Note - this was done on VZW variant, and based on XML file of that particular firmware. Get these instructions from your firmware package XML file.
Note 2 - VERY IMPORTANT!!! - You MUST use mfastboot (Moto fastboot) for the system.img flash as its too large for standard Android fastboot to handle, your flash WILL fail if you use standard fastboot. Hence why it says "mfastboot" this is not a typo.
First simply boot into fastboot mode - manually OR adb reboot bootloader
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
Excellent guide, I'm not bricked but I'm pretty sure it will be useful for someone else!, thanks for your time and effort
Sent from my Nexus 7 using XDA Premium 4 mobile app
Nice guide. Used rsdlite and flashed stock. Just upgraded 4.4. Very satisfied with new version along with nova pro
Sent from my XT1080 using xda app-developers app
Question: will this method work if I flashed a custom radio? In other words, does this completely overwrite all pre-existing mods (custom bootloader, custom radio, system file mods)? Thanks!
allquixotic said:
Question: will this method work if I flashed a custom radio? In other words, does this completely overwrite all pre-existing mods (custom bootloader, custom radio, system file mods)? Thanks!
Click to expand...
Click to collapse
Yes it does, I'm using a custom radio too, I'm waiting for the kit Kat sbf
Sent from my Nexus 7 using XDA Premium 4 mobile app
allquixotic said:
Question: will this method work if I flashed a custom radio? In other words, does this completely overwrite all pre-existing mods (custom bootloader, custom radio, system file mods)? Thanks!
Click to expand...
Click to collapse
What kind of custom radio? Thought you couldn't flash that kind of stuff without an s off device?
Sent from my XT1080 using xda app-developers app
YoungSkeezy said:
What kind of custom radio? Thought you couldn't flash that kind of stuff without an s off device?
Click to expand...
Click to collapse
Just the radio that leaked that everyone thought was a test of AWS. The radio worked, but I didn't notice any higher speeds.
No, you don't need S-OFF to flash a custom radio.
will it work if i want to downgrade from 4.4 to 4.2 ?
No
YOU SIR...ARE THE MAN!!!!! worked flawlessly..i thought i had permanently bricked my replacement phone.. but thanks to you and another fellow who directed me to the FXZ files.. the new phone is up and running..and I can send the old one back!!!
Worked great. Not difficult at all.
Sent from my XT1080 using xda app-developers app
First of all, a lot of Thanks for this useful thread sir...
I am using DroidMAXX with Unlocked BL, rooted and customRecovery flashed... I can see the lines to flash boot image and recovery image. So on flashing this my phone's BL will be relocked and stock recovery will be flashed, isn't it. Later I can again unlock using the code, right? And I can use this method to receive OTA (for 4.4.2) right?
kanagadeepan said:
First of all, a lot of Thanks for this useful thread sir...
I am using DroidMAXX with Unlocked BL, rooted and customRecovery flashed... I can see the lines to flash boot image and recovery image. So on flashing this my phone's BL will be relocked and stock recovery will be flashed, isn't it. Later I can again unlock using the code, right? And I can use this method to receive OTA (for 4.4.2) right?
Click to expand...
Click to collapse
No, this will NOT re-lock your bootloader. It does flash the stock recovery and unroot you so you can receive an OTA.
OH... Thanks ji for the clarificaiton... So I can flash it and reroot by flashing twrp recovery? Why I am asking is I have messed with the active notifications and other Moto apps using Titanium Backup.. Now I want my root + Active Notifications back...
Thanks again, my friend...
kanagadeepan said:
OH... Thanks ji for the clarificaiton... So I can flash it and reroot by flashing twrp recovery? Why I am asking is I have messed with the active notifications and other Moto apps using Titanium Backup.. Now I want my root + Active Notifications back...
Thanks again, my friend...
Click to expand...
Click to collapse
yes, just flash twrp and reroot
I know that this won't work for downgrading from 4.4 to 4.2.2, but I'm wondering why not? What is making it so that this doesn't work? I'm thinking it has something to do with the new recovery that was flashed with the update, but I'm not sure.
Jay_P11 said:
I know that this won't work for downgrading from 4.4 to 4.2.2, but I'm wondering why not? What is making it so that this doesn't work? I'm thinking it has something to do with the new recovery that was flashed with the update, but I'm not sure.
Click to expand...
Click to collapse
Bootloader
akellar said:
Bootloader
Click to expand...
Click to collapse
Alright thanks for clarifying. My battery life is absolutely horrid, about 8 hours MAX per day before I need a charge, and it was never like this on 4.2.2 :/ 4.4's "Battery Saver" feature in WiFi settings never works anymore either, it just turns itself off the second I turn it on. Definitely some major bugs in this build, and I'm hoping they get fixed in the next update. If they don't, then I'm just going to pony up $300 for early termination and get an LG G2.
One more thing, this should work for restoring back to factory 4.4 on 4.4 then right? Maybe my update is broken and it just needs a clean install for the battery saver to work?
TechSavvy2 said:
First simply boot into fastboot mode - manually OR adb reboot bootloader
Code:
fastboot oem fb_mode_set
Click to expand...
Click to collapse
So I just send up sitting at "waiting for device" after executing that line. RSD won't recognize my phone either--tried different cables.
Thoughts?
Hi all!
Just a quick synopsis. I've held off for a while. I've read just about everything related as it's come across here over the past few weeks.
I've been perfectly happy with where I sat:
VZW Dev Ed, Rooted, TWRP, xPosed, Tehter & Gravity Box modules.
I'm not fond of ADB commands, etc. but can work my way through them.
Today, I decided to to take a quick stab at things (a little differently).
So, here's what I did:
1) Unfroze some bloat
2) Unistalled xposed Framework
3) USED Flashify to backup my TWRP
4) USED Flashify to install stock recovery
5) Downloaded OTA
6) Installed 4.4.2 update
7) It FAILED
So, I restored my TWRP recovery through Flashify; re-installed xPosed Framework; refroze the bloat and I'm back to where I was before.
The only thing that I really think might have caused the update to fail was the fact that I had AOSP Browser installed. (with its related installer)
So, that's my question here....opinions...would that cause the update to fail?
I've since tried to uninstall that browser with the related installer but it keeps getting hung and force closes when trying.
Opinions? (other than..."please, use ADB commands")
I'm assuming flashing my system ui might take care of that?
Thanks for ideas. I know I'll take the time to get it done "proper". Just haven't been pressed to do it yet.
Unfreeze everything and make sure the tether hack is reversed. I believe it tells you where it failed in recovery when it's doing its thing. I'm in the same boat as you, but I'm just going to wait until Moto releases the new image.
hlaalu said:
Unfreeze everything and make sure the tether hack is reversed. I believe it tells you where it failed in recovery when it's doing its thing. I'm in the same boat as you, but I'm just going to wait until Moto releases the new image.
Click to expand...
Click to collapse
Well, it's the tether module (not the hack)...so uninstalling xPosed would take care of that I'd think.
When Moto releases the new image...what's your plan? Able to flash that without losing data, etc?
Are you using the VZW specific stock recovery.img directly obtained from the Motorola website that you extracted yourself from the zip file you got there? I wouldn't necessarily trust any other stock recovery floating around.
Did you run the xposed cleaner zip or just uninstall it? It easier to just flash the system and recovery images via mfastboot. It takes two seconds assuming you have the Sdk installed and Moto drivers installed.
Sent from my Dev Edition Moto X
Dburgessme2 said:
Well, it's the tether module (not the hack)...so uninstalling xPosed would take care of that I'd think.
When Moto releases the new image...what's your plan? Able to flash that without losing data, etc?
Click to expand...
Click to collapse
Hmm double check that it checks for subscription when tethering to make sure it changed the files back?
I'm a little rusty with fastboot, but it doesn't wipe your data unless you ask it to:
Code:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
[B]$ fastboot erase userdata[/B]
$ fastboot erase cache
$ fastboot oem lock
So I think if you just don't do the fastboot erase userdata command your data is safe. I'll wait for someone with more experience to confirm that.
But even if that's not the case, I'll still wait because we have to fastboot for root and recovery anyways, might as well just do everything in one go.
Schaweet said:
Did you run the xposed cleaner zip or just uninstall it? It easier to just flash the system and recovery images via mfastboot. It takes two seconds assuming you have the Sdk installed and Moto drivers installed.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I only used the Uninstall from within itself. Where is the cleaner zip? Might have to do a search.
Thanks!
DB's Nexus 7
Roland Stone said:
Are you using the VZW specific stock recovery.img directly obtained from the Motorola website that you extracted yourself from the zip file you got there? I wouldn't necessarily trust any other stock recovery floating around.
Click to expand...
Click to collapse
Nope, I didn't extract it myself. I'll have to do that to make sure I've got the "real deal".
Thanks!
DB's Nexus 7
Dburgessme2 said:
I only used the Uninstall from within itself. Where is the cleaner zip? Might have to do a search.
Thanks!
DB's Nexus 7
Click to expand...
Click to collapse
It's the xposed disabler zip that is put in the root of your SD card when you install xposed.
Sent from my Dev Edition Moto X
Schaweet said:
It's the xposed disabler zip that is put in the root of your SD card when you install xposed.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Just flash it through recovery I assume?
DB's Nexus 7
Yes
Flashing the system and recovery images is still the most fail safe method. It doesn't erase your settings or data.
Sent from my Dev Edition Moto X
Flashing the stock recovery did the trick for me. No data loss either.
Sent from my Nexus 7 using xda app-developers app
awerner68 said:
Flashing the stock recovery did the trick for me. No data loss either.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
So, what method did you use to update? Fastboot/ADB commands or the "on phone" method I described in first post?
Easiest thing to do is fxz save data with HoM. If you don't have HoM set up you can modify the fxz XML. File to not erase user data and fxz. You should be able to update then. The fxz puts stock recovery back so you don't have to flash anything. Update install twrp root done.
Sent from my XT1080 using xda app-developers app
bigv5150 said:
Easiest thing to do is fxz save data with HoM. If you don't have HoM set up you can modify the fxz XML. File to not erase user data and fxz. You should be able to update then. The fxz puts stock recovery back so you don't have to flash anything. Update install twrp root done.
Sent from my XT1080 using xda app-developers app
Click to expand...
Click to collapse
So, fxz the 4.4.2 image for vzw 1060 through rsd lite? But remove "erase data" line from the xml file first. Then, TWRP recovery back (root). That about right?
I think the last thing I used rsd lite for was on old Droid X.
Any quick refresher would be appreciated.
Thanks!
DB's Moto X
Yeah that is pretty much it. As far as what line to delete I'm not sure I use HoM it does it all autmatically. Only tips I can give you is don't use USB 3 it doesn't work with rsd only USB 2 if you plug in your phone and don't see it in rsd change USB port. Make sure debugging is checked.
Sent from my XT1080 using xda app-developers app
bigv5150 said:
Yeah that is pretty much it. As far as what line to delete I'm not sure I use HoM it does it all autmatically. Only tips I can give you is don't use USB 3 it doesn't work with rsd only USB 2 if you plug in your phone and don't see it in rsd change USB port. Make sure debugging is checked.
Sent from my XT1080 using xda app-developers app
Click to expand...
Click to collapse
OK. And now I have to ask... What is HoM? (googled with no good results)
DB's Nexus 7
Dburgessme2 said:
So, what method did you use to update? Fastboot/ADB commands or the "on phone" method I described in first post?
Click to expand...
Click to collapse
I downloaded the .ZIP file and flashed it with TWRP. Using TWRP to replace itself.
HoM (House of Moto) its a script that allows you to do a full fxz or a save data fxz. It just makes fxz'ing easier here is the site
http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20-for-now/
Sent from my XT1080 using xda app-developers app
bigv5150 said:
HoM (House of Moto) its a script that allows you to do a full fxz or a save data fxz. It just makes fxz'ing easier here is the site
http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20-for-now/
Sent from my XT1080 using xda app-developers app
Click to expand...
Click to collapse
And, this HoM should work with the Vzw 1060 Dev Ed?
DB's Moto X
So far all the methods i've read require me to rsdlite or adb the factory fxz which I believe causes me to lose data.
nvertigo said:
So far all the methods i've read require me to rsdlite or adb the factory fxz which I believe causes me to lose data.
Click to expand...
Click to collapse
As far as I can figure, the only way would to use an app to backup the data, flash back to factory, re-root and restore the data. The OTA update will remove root access. I would do a backup with CWM first if possible.
nvertigo said:
So far all the methods i've read require me to rsdlite or adb the factory fxz which I believe causes me to lose data.
Click to expand...
Click to collapse
if you know what you actually changed with root permissions then you can just flash stock recovery onto the phone then remove all things root and put everything back to normal stock (like unfreezing things out of tibu or whatever) then take the ota. if you are not sure what you changed, you can flash recovery and system then take the ota (assuming you didn't flash new kernals or anything else major).
And if you just want to keep data then you can flash stock ota with rsdlite and remove the two entries that erase data and cache in the xml file. Then take the ota. or flash the fxz and remove the same data erasing entries in the xml
If you have an unlocked bootloader, just mfastboot stock recovery and stock system and take the OTA. You won't lose data. Then just reflash TWRP and root. Good to go.
If your bootloader is locked, then I have no idea.
Sent from my Dev Edition Moto X
Schaweet said:
If you have an unlocked bootloader, just mfastboot stock recovery and stock system and take the OTA. You won't lose data. Then just reflash TWRP and root. Good to go.
If your bootloader is locked, then I have no idea.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I am on a vzw dev edition. I have rooted and have twrp installed. I changed the boot animation and installed xposed. If I undo those 2 things does some have a step by step process for getting back to stock and taking the ota and then re installing twrp and rooting. I would greatly appreciate it.
robwege said:
I am on a vzw dev edition. I have rooted and have twrp installed. I changed the boot animation and installed xposed. If I undo those 2 things does some have a step by step process for getting back to stock and taking the ota and then re installing twrp and rooting. I would greatly appreciate it.
Click to expand...
Click to collapse
This is what I did.
1. Download 4.4 stock files from Motorola (you need to request access and they will email you the link)
2. Extract recovery.img and system.img from the stock image and place them in your platform tools folder ( or where fastboot and adb are located)
3. Update your SDK if it is out of date.
4. Download and put mfastboot in your platform tools folder (or where fastboot and adb are within your sdk directory)
5. Boot phone into fastboot mode
6. open a command prompt and change directory to your platform-tools folder and type the following (7 & 8)
7. fastboot flash recovery recovery.img
8. mfastboot flash system system.img
9. Reboot
10. Accept and install OTA
11. Reboot into fastboot mode
12. Reflash TWRP and root phone.
13. Reboot
14. Open Xposed and reinstall framework
15. Reboot
You would be good to go at that point. You would still need to reinstall your logo as it would be reset
If you already unlocked your phone and didn't change anything, you shouldn't have much trouble with the commands
Schaweet said:
This is what I did.
1. Download 4.4 stock files from Motorola (you need to request access and they will email you the link)
2. Extract recovery.img and system.img from the stock image and place them in your platform tools folder ( or where fastboot and adb are located)
3. Update your SDK if it is out of date.
4. Download and put mfastboot in your platform tools folder (or where fastboot and adb are within your sdk directory)
5. Boot phone into fastboot mode
6. open a command prompt and change directory to your platform-tools folder and type the following (7 & 8)
7. fastboot flash recovery recovery.img
8. mfastboot flash system system.img
9. Reboot
10. Accept and install OTA
11. Reboot into fastboot mode
12. Reflash TWRP and root phone.
13. Reboot
14. Open Xposed and reinstall framework
15. Reboot
You would be good to go at that point. You would still need to reinstall your logo as it would be reset
If you already unlocked your phone and didn't change anything, you shouldn't have much trouble with the commands
Click to expand...
Click to collapse
Thank you for your help. The only things I changed were and boot logo and xposed. I also freezer some apps but that is an easy fix. You di this on a vzw Dev edition as well?
Sent from my XT1060 using XDA Premium 4 mobile app
robwege said:
I am on a vzw dev edition. I have rooted and have twrp installed. I changed the boot animation and installed xposed. If I undo those 2 things does some have a step by step process for getting back to stock and taking the ota and then re installing twrp and rooting. I would greatly appreciate it.
Click to expand...
Click to collapse
robwege said:
Thank you for your help. The only things I changed were and boot logo and xposed. I also freezer some apps but that is an easy fix. You di this on a vzw Dev edition as well?
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you froze the OTA application, you need to unfreeze that first as you won't have root until after you take the OTA and then reinstall TWRP.
I have a VZW DE as well.
I'm not sure how the changed boot animation will affect the OTA.
Your safest bet is to just follow the process I wrote to ensure the OTA doesn't fail and create other problems. It really only takes like 5 minutes. It leaves your data intact, so you won't have to set it up again. It also leaves the Xposed app on your phone and you just need to open it and install it. All your modules will still be there and will work as they did before after a reboot.
Schaweet said:
If you froze the OTA application, you need to unfreeze that first as you won't have root until after you take the OTA and then reinstall TWRP.
I have a VZW DE as well.
I'm not sure how the changed boot animation will affect the OTA.
Your safest bet is to just follow the process I wrote to ensure the OTA doesn't fail and create other problems. It really only takes like 5 minutes. It leaves your data intact, so you won't have to set it up again. It also leaves the Xposed app on your phone and you just need to open it and install it. All your modules will still be there and will work as they did before after a reboot.
Click to expand...
Click to collapse
I kept the old boot animation file so I can just move it back.
Sent from my XT1060 using XDA Premium 4 mobile app
OK so then technically you can reinstall the old boot Ani, unfreeze all apps, disable xposed using the Xposed disabler zip that should be in your SD card root directory, and then flash stock recovery.
That should allow you to take the OTA as you would technically be stock at that point. I chose the other method to ensure I was 100% stock. This should get you to stock as well, but I guess I like to be certain.
Sent from my Dev Edition Moto X
Schaweet said:
OK so then technically you can reinstall the old boot Ani, unfreeze all apps, disable xposed using the Xposed disabler zip that should be in your SD card root directory, and then flash stock recovery.
That should allow you to take the OTA as you would technically be stock at that point. I chose the other method to ensure I was 100% stock. This should get you to stock as well, but I guess I like to be certain.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
OK. I think I will do your method instead. I will unfreeze the apps, install old boot logo and disable xposed just to be safe. Then I will do your method. Wish me luck.
Sent from my XT1060 using XDA Premium 4 mobile app
If you do my method with all the numbered steps, you don't have to mess with all the unfreezing and stuff. Flashing system.img overwrites all those changes for you.
Sent from my Dev Edition Moto X
Schaweet said:
If you have an unlocked bootloader, just mfastboot stock recovery and stock system and take the OTA. You won't lose data. Then just reflash TWRP and root. Good to go.
If your bootloader is locked, then I have no idea.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
You don't even need an unlocked bootloader, you can still flash stock images on a locked bootloader. Also the person obviously unlock the bootloader since TWRP is installed, unless I'm not aware of a way to install it without.
eksasol said:
Also the person obviously unlock the bootloader since TWRP is installed, unless I'm not aware of a way to install it without.
Click to expand...
Click to collapse
You are correct. You can only flash a custom recovery if your bootloader is unlocked. That is what unlocking your bootloader allows you to do - flash unsigned recovery files (i.e., custom recoveries) and obviously, TWRP is not signed by motorola. Then once you have a custom recovery, the custom recovery allows you to flash unsigned operating systems.
If your bootloader is locked, you cannot flash an unsigned recovery.
Schaweet said:
If you do my method with all the numbered steps, you don't have to mess with all the unfreezing and stuff. Flashing system.img overwrites all those changes for you.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I am looking at your steps. Number 8 says fastboot and not mfastboot. Is this a typo or the correct command? I entered it in a cmd prompt and it just said waiting for device. I checked and adb was seeing my device.
Sent from my XT1060 using XDA Premium 4 mobile app
---------- Post added at 01:40 PM ---------- Previous post was at 01:40 PM ----------
robwege said:
I am looking at your steps. Number 8 says fastboot and not mfastboot. Is this a typo or the correct command? I entered it in a cmd prompt and it just said waiting for device. I checked and adb was seeing my device.
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I meant step 7.
Sent from my XT1060 using XDA Premium 4 mobile app
robwege said:
I am looking at your steps. Number 8 says fastboot and not mfastboot. Is this a typo or the correct command? I entered it in a cmd prompt and it just said waiting for device. I checked and adb was seeing my device.
Click to expand...
Click to collapse
fastboot is fine to flash recovery but you need to be in bootloader mode to use fastboot. You need mfastboot to flash system since it is so large. But mfastboot will work to flash recovery, too.
adb doesn't work in bootloader mode and fastboot doesn't work when you are booted into system. So if adb is working for you, you aren't in bootloader mode (note: bootloader mode is also called fastboot mode since for fastboot to work, you need to be in bootloader mode).
Go back to step 5 - boot into bootloader mode. Just type adb reboot bootloader. That will put you in bootloader mode.
NightThyme said:
fastboot is fine to flash recovery but you need to be in bootloader mode to use fastboot. You need mfastboot to flash system since it is so large. But mfastboot will work to flash recovery, too.
adb doesn't work in bootloader mode and fastboot doesn't work when you are booted into system. So if adb is working for you, you aren't in bootloader mode (note: bootloader mode is also called fastboot mode since for fastboot to work, you need to be in bootloader mode).
Go back to step 5 - boot into bootloader mode. Just type adb reboot bootloader. That will put you in bootloader mode.
Click to expand...
Click to collapse
OK. So if I am understanding you correctly. I boot the phone into fast boot. Then type your reboot bootloader cmd. Then from there I can do step 7 and 8 as typed above I. The thread where 7 uses fastboot and 8 uses mfastboot?
Sent from my XT1060 using XDA Premium 4 mobile app
robwege said:
OK. So if I am understanding you correctly. I boot the phone into fast boot. Then type your reboot bootloader cmd. Then from there I can do step 7 and 8 as typed above I. The thread where 7 uses fastboot and 8 uses mfastboot?
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The commands are written correctly. You have to be in bootloader/fastboot mode. I thought I said that.
Edit. I did see step 5.
Follow every step you don't want a brick.
Sent from my Dev Edition Moto X
Schaweet said:
The commands are written correctly. You have to be in bootloader/fastboot mode. I thought I said that.
Edit. I did see step 5.
Follow every step you don't want a brick.
Click to expand...
Click to collapse
This.
If I wanted to go back to stock from an aosp based ROM could I use the mfastboot recovery and system method or do I ha e to rsd.... I'm unlocked btw
Sent from my Moto X using Tapatalk
Here is the a rooted boot and system img (rooted with busybox installed, no other modifications). Stock recovery and the modem
BUILD: LXE22.46-11
Flash in fastboot mode. If you don't know how I suggest you use Google.
To flash the system.img you will need mfastboot found here. https://mega.co.nz/#!4wAkGJxJ!x5O6w-3KzoS4Xedo_gCALNXt5swNEevmENvv4iHBGS4
You will need to split up the system.img to use.. this is for advanced users only..
Download Links can be found on my website: http://www.graffix.nyc/motox.php
DO NOT MIRROR
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it or it kills your neighbor's dog. Flash at your own risk. I am not responsible.... It was the other guy... I swear....
thanks brotha
Just realized that I had Better Battery Stats installed as a system app when I did the system img. I'm uploading a new one now
system.img link is back up
You should put this in the android development section
graffixnyc said:
Just realized that I had Better Battery Stats installed as a system app when I did the system img. I'm uploading a new one now
Click to expand...
Click to collapse
no worries. i always do my own pull of the system.img right after root. recovery.img is something i never pull since that's usually one of the first things readily available in sections due to it's small size and the necessity for having custom recoveries to flash user made zips (and needing to go back for OTAs).
Did you try to use mfastboot or fastboot? On the og moto x you have to use mfastboot to flash the system.
tigercranestyle said:
last edit:
had issue on my end with bad mfastboot. got a copy of v2 and install via mfastboot works.
thx op for files and matt for suggestion.
Click to expand...
Click to collapse
Glad it worked. Do you have a link to the mfastboot you got and I'll add the link to the op
Sent from my XT1095 using Tapatalk
Could anyone help me out? I ran into an issue when trying to flash the system.img. I get the following
errorload_file: could not allocate -1392508928 bytes
error: cannot load 'system.img'
I don't believe I'm doing anything wrong, but can someone please clarify?
Schultz_91 said:
Could anyone help me out? I ran into an issue when trying to flash the system.img. I get the following
errorload_file: could not allocate -1392508928 bytes
error: cannot load 'system.img'
I don't believe I'm doing anything wrong, but can someone please clarify?
Click to expand...
Click to collapse
Did you mfastboot? Must not fastboot for system only.
I did download the mfastboot and extracted it to my C drive. I tried throwing the system.img into that folder and flashing. Is that what you mean? If not could you please elaborate?
---------- Post added at 03:54 AM ---------- Previous post was at 03:37 AM ----------
Aha. I see. mfastboot breaks it up into manageable chunks. When I flashed it the first time I was impatient as it didn't give my any output for a bit. Apologies. Thanks so much!
Thanks so much for posting this! In what order do we flash these. Is there anyone's favorite tutorial out there to help?? Thanks
stu5797 said:
Thanks so much for posting this! In what order do we flash these. Is there anyone's favorite tutorial out there to help?? Thanks
Click to expand...
Click to collapse
It's doesn't matter which order you flash them in. There are plenty of tutorials on how to flash fastboot images, just do a Google search.
Sent from my XT1095 using Tapatalk
graffixnyc said:
Here is a system.img that is rooted with busybox installed (No other modifications), The stock Boot.img and the stock recovery.
BUILD: KXE21.187-42
Flash in fastboot mode. If you don't know how I suggest you use Google.
To flash the system.img you will need mfastboot found here. https://mega.co.nz/#!4wAkGJxJ!x5O6w-3KzoS4Xedo_gCALNXt5swNEevmENvv4iHBGS4
System: https://www.androidfilehost.com/?fid=95747613655040839
MD5:9b4e37afd99a92a69a00a6401023dc2c
Boot: https://www.androidfilehost.com/?fid=95747613655040774
MD5:d8be13fe97e1791023d7031789bf9f65
Recovery: https://www.androidfilehost.com/?fid=95747613655040773
MD5: a5673547c4a78b255cce3c64aa854a2b
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it or it kills your neighbor's dog. Flash at your own risk. I am not responsible.... It was the other guy... I swear....
Click to expand...
Click to collapse
Is there a way to unlock the software restricted LTE bands on the XT1095?
Sent from my A0001 using XDA Free mobile app
graffixnyc said:
Here is a system.img that is rooted with busybox installed (No other modifications), The stock Boot.img and the stock recovery.
BUILD: KXE21.187-42
Flash in fastboot mode. If you don't know how I suggest you use Google.
[/COLOR][/SIZE]
Click to expand...
Click to collapse
Please clarify my doubts...
My build number is same KXE21.187-42, but system version is "21.21.42.........en.EU retin". I did root this and it is working great, installed custom recovery and also xposed framework...
Now if I want stock recovery can I uninstall the Xposed and flash the stock recovery that has been provided here (and of course take an OTA)? Does that depends on build number alone, or something to do with system version also...?
Kindly enlighten me, there may be many posts regarding this issue, but I'm confused and need a confirmation...
ThnQ...
is the DL link dead for anyone else?
flashed the img thru fastboot and now i cant boot up. do not use this.
papi92 said:
flashed the img thru fastboot and now i cant boot up. do not use this.
Click to expand...
Click to collapse
Is your phone the pure edition?
Yes
I've flashed all images with no issue
Searched and didn't find any good links. I'm decent at figuring out how to normally do things, but I can't find a way to install 5.0.1 on my rooted Nexus 6? Anyone know how? I have TWRP installed and the stock ROM. Just wanted to deactivate encryption.
Use fastboot. There's a thread here full of info for it. Pretty easy to do, just needs to be done in the right order
Sent from my Nexus 6 using Tapatalk
Edit: see this thread: http://forum.xda-developers.com/showthread.php?t=2969137
Is it even worth the hassle to update from 5.0? What's the benefit?
I haven't really noticed anything. Newer radios and some bug fixes I believe.
Sent from my Nexus 6 using Tapatalk
this worked for me from the thread posted above:
HixVAC said:
1. Extract image-shamu-lrx22c.zip
2. Move the system.img from the extracted file into the same directory as fastboot
3. Move radio-shamu-d4.0-9625-02.55.04.img to the same directory as fastboot
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
Then proceed to take care of root if you had/want root
Click to expand...
Click to collapse
in my case I did this after the last reboot:
fastboot reboot-recovery
then I flashed the latest SU from chainfire and all was well. kept all my settings. had to let it optimize all the apps. If you are unencrypted you stay that way.
I did a nandroid backup in TWRP to an OTG drive and then used wug's toolkit to restore to stock with the google factory 5.0.1 image and then re-flashed TWRP and restored data from my nandroid. Worked perfectly. Hope this helps. Good luck