I would like to thank Hashcode and xlightwaverx for their work on making this type of update method possible. Without Hashcode, Motorola devices wouldn't be nearly as fun to play with as they are today.
We will need to definite a few terms, because this is not going to be the most user-friendly way of upgrading your Motorola Android device.
OMAP - The brand of the manufacturer Texas Instruments for a select set of processors. This is used in the older generation of Motorola devices referred to in this guide and includes: DROID Bionic XT875, DROID 3, DROID 4 XT894, DROID RAZR XT912, and DROID Xyboard (aka XOOM 2).
Snapdragon- The brand of the manufacturer Qualcomm for a select set of processors. I will be referring to this for these devices: Photon Q 4G LTE, Atrix HD MB886, DROID RAZR HD XT926, DROID RAZR M XT907, RAZR HD XT925, and RAZR M XT905/201M.
Safestrap - A custom recovery for rooted, but locked bootloader devices by Hashcode. You can download it from here. It has variants for both OMAP and Snapdragon devices. This is used to 'flash' custom ROMs and other 'flashable' zip files.
Flash - A generic term for installing something to the device. You will see this used like so: "Flash ____ ROM using Safestrap" which just means to install the ROM's zip file to the device, using Safestrap by Hashcode.
Fastboot - A 'mode' for Motorola Android devices (and some other Android devices) for 'flashing' firmware files. Getting into this mode will vary by device, but generally you must select it from the Boot Menu. To get to the Boot Menu, the phone must be completely turned off. Then:
Hold down both Volume keys and the Power key until the Boot Menu comes up on the screen.
Use the Volume Down key to scroll down the list, and select the 'AP Fastboot' or 'Fastboot' mode from the list, the name varies by device.
To leave Fastboot, hold down the power button for a second or two. At any time your device is stuck or forzen in any mode and you cannot perform a Battery Pull, you can use the button combination of Power + Volume Down keys for 8-10 seconds and the device will power off.
Moto-Fastboot - For OMAP devices, you must use the Motorola version of Fastboot called 'Moto-fastboot'. I have renamed it for this guide's sake to 'fastboot'. The only difference between this and regular 'Fastboot' is the executable will flash large files in parts rather than in one time. This is required for OMAP based Motorola devices.
Firmware - Sometimes called 'SBF' files because of the format used prior to Motorola Android devices with a 4G LTE radio in them, these are generally .XML.ZIP files which contain the software of your device. The "Firmware Team" finds these files and uploads them to a website maintained by Skrilax_CZ. Having this firmware in the hands of normal users lets us repair devices and return them to complete factory settings, or even upgrade them completely in some cases.
Path - This is a computer term relating to what your Command Line or Terminal application will see when you type in a command. I will not be assisting with setting up your Path mainly because its Operating System specific.
You can find a Windows guide for setting up the Path here, by tucstwo of DroidRzr.com.
Now that these are defined, lets move to some required Downloads.
Fastboot - for OMAP
Fastboot - for Snapdragon
It should be obvious, but you only need the download for your device type. See the definitions if you don't know your device type.
The goal of this guide is to show you how to upgrade your rooted Motorola Android device to the latest update without breaking your ability to downgrade, and without breaking your root. Hopefully it won't be too difficult.
Some things must be true for this to work on your device:
Your device is rooted and has Safestrap installed.
Your device's new OTA Update has Firmware availiable for that new update.
If these are both the case, then you are in luck. This same process should work similarly for both OMAP and Snapdragon based Motorola Android devices.
Download the new firmware. Every time a new firmware is released, it goes on the Droid-Developers SBF website.
Extract the firmware .xml.zip to a folder, we can call this the folder whatever we like. You need two things from this folder:
boot.img
radio.img OR NON-HLOS.bin
Once you have those, you will then need to find a Stock ROM, or any ROM based off of the new OTA Update version. A Stock ROM is a .zip usually created by someone like Hashcode using a System Pull from a device and turning it into a flashable .zip for people to use as a backup.
With the Stock ROM, the boot.img, and the radio.img (or NON-HLOS.bin) collected, put the Stock ROM .zip onto your external storage. If you don't have external storage, internal should be fine too. Move the boot.img and radio.img (or NON-HLOS.bin) to the folder where your fastboot is located. These will then be in your Path if fastboot already is.
I had previously mentioned you need to be rooted and to have Safestrap installed, if you haven't done them you MUST do them now or the rest of this process will not work.
Boot your phone into Fastboot mode. I explained how in the definitions.
Using your computer's Command Line or Terminal application with the proper Path setup for fastboot.
Enter the following commands for OMAP devices:
Code:
fastboot flash boot boot.img
fastboot flash radio radio.img
Enter the following commands for Snapdragon devices:
Code:
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
Now reboot your device, and enter Safestrap. Depending on which version of Safestrap these instructions may be a little different but the outcome will be the same.
Flash the Stock ROM from your external or internal storage, from where-ever you have placed it from the previous steps. Note that you may need to enable another ROM SLOT for being able to flash any .zip files.
Once the Stock ROM is flashed, reboot into your brand new OTA Updated phone which is rooted (assuming the Stock ROM was, 99% of the time they are) and you have retained the ability to flash back to an earlier firmware. Congrats!
So this mean 4.2 is coming soon lol
Sent from my MB886 using xda premium
sickkside13 said:
So this mean 4.2 is coming soon lol
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
I have no idea, you'd have to check Motorola update tables.
sickkside13 said:
So this mean 4.2 is coming soon lol
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
How did you even come to that conclusion?
Thanks for the guide Matt
Is it possible to change the xml and system image to use a already rooted 4.1.2 system instead and flash with rsd? just curious if it would work.
Sent from my DROID RAZR HD using xda app-developers app
xrxregenxrx said:
Is it possible to change the xml and system image to use a already rooted 4.1.2 system instead and flash with rsd? just curious if it would work.
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
Nope cause of the signature check I'm assuming
Sent from my MB886 using xda app-developers app
EcHoFiiVe said:
Nope cause of the signature check I'm assuming
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
+1
Related
A newer version is now available: Unofficial TWRP 2.5.0.0 for DROID RAZR HD XT926 & RAZR HD XT925, thanks to mattlgroff.
---------
DISCLAIMER
USE THIS SOFTWARE AT YOUR OWN RISK.
I AM NOT RESPONSIBLE IF YOUR PC OR PHONE OR ANY EQUIPMENT ATTACHED GET DAMAGED / BROKEN / UNUSABLE.
I AM NOT RESPONSIBLE IF YOU SOMEHOW GET IN TROUBLE, HURT OR INJURED.
PURPOSE
The purpose of this thread is to provide XT925 owners with links and instructions on how to install the TWRP v2.2.2.1 custom recovery (touch version).
CREDITS
I take absolutely no credits at all for this. I don't know who ported TWRP for the XT925. All links and instructions come from this post from m.pierce. Many thanks to him/her.
REQUIREMENTS
- A Motorola RAZR HD XT925 with an unlocked bootloader
- Fastboot command line executables for Windows, Linux and Mac
- The TWRP recovery image
- [Optional] The Root.zip package (i.e install this package through the recovery to root your device)
INSTRUCTIONS
1/ Boot up your device in Fastboot Mode (while your device is on, hold Vol-/Vol+/Power buttons for a few seconds until the screen turns black, then release Power. Another few seconds later comes up the boot menu. Release Vol-/Vol+, then quickly press Vol- a few times to highlight "Fastboot" then Vol+ to trigger it).
2/ Back to your computer, make sure your fastboot files and the recovery image are in the same directory in order to proceed with the flashing, then run the fastboot command from a console/terminal:
Code:
fastboot flash recovery twrp-hdrecovery.img
That's it, you're done! From then on, you can use the custom recovery to make nandroid backups, install zipped package files, install custom ROMs, ...
For instance, if you want to root the currently installed ROM, you would install the Root.zip package.
HOW TO SWITCH TO THE CUSTOM RECOVERY?
While your device is on, hold Vol-/Vol+/Power buttons for a few seconds until the screen turns black, then release Power. Another few seconds later comes up the boot menu. Release Vol-/Vol+, then quickly press Vol- a few times to highlight "Recovery" then Vol+ to trigger it.
Enjoy!
Does this root.zip work for the jellybean fr leak?
Sent from my XT925 using xda app-developers app
royalbloodvi said:
Does this root.zip work for the jellybean fr leak?
Sent from my XT925 using xda app-developers app
Click to expand...
Click to collapse
Didn't test on JB leak, but I believe it does.
madmonkey57 said:
Didn't test on JB leak, but I believe it does.
Click to expand...
Click to collapse
No it doesnot once you flash it will boot once but after that if you try to come to it later it will show the droid guy with a red exclamation mark.
yalkowni said:
No it doesnot once you flash it will boot once but after that if you try to come to it later it will show the droid guy with a red exclamation mark.
Click to expand...
Click to collapse
Maybe you could try to apply CWM-SuperSU-v0.98.zip. It was reported to work on the official JB OTA.
I love Twrp.
I encountered an error trying to flash cm10 by epinter, but I got a problem " assert error getprop status 7" or something like that. Any idea on what should I do? I Googled and all the answers were "use cwm", but I hate it.
Thanks in advance!
Sent from my XT925
Royalfox said:
I love Twrp.
I encountered an error trying to flash cm10 by epinter, but I got a problem " assert error getprop status 7" or something like that. Any idea on what should I do? I Googled and all the answers were "use cwm", but I hate it.
Thanks in advance!
Sent from my XT925
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=34189431&postcount=11
madmonkey57 said:
http://forum.xda-developers.com/showpost.php?p=34189431&postcount=11
Click to expand...
Click to collapse
I don't have Linux on any PC. Any other suggestions?
Sent from my XT925
Royalfox said:
I don't have Linux on any PC. Any other suggestions?
Sent from my XT925
Click to expand...
Click to collapse
Maybe 7zip for windows.
madmonkey57 said:
Maybe 7zip for windows.
Click to expand...
Click to collapse
Can't this be done on the phone?
Sent from my XT925
Royalfox said:
Can't this be done on the phone?
Sent from my XT925
Click to expand...
Click to collapse
Not that I know of...
madmonkey57 said:
Not that I know of...
Click to expand...
Click to collapse
Okay I did it with winzip, deleted the assert line and I got able to finally flash cm10. Thanks a lot pal!
Sent from my XT925
Royalfox said:
Okay I did it with winzip, deleted the assert line and I got able to finally flash cm10. Thanks a lot pal!
Sent from my XT925
Click to expand...
Click to collapse
Glad it worked.:highfive:
Thanks to eagleeyetom for the sticky :good:
I get the Droid with a red exclamation mark when trying to boot this. I followed the prompts exactly as required.
I have an XT925 running 4.1.2.
Thoughts?
krucifix85 said:
I get the Droid with a red exclamation mark when trying to boot this. I followed the prompts exactly as required.
I have an XT925 running 4.1.2.
Thoughts?
Click to expand...
Click to collapse
Any message on the device or the command line when flashing the recovery file?
yalkowni said:
No it doesnot once you flash it will boot once but after that if you try to come to it later it will show the droid guy with a red exclamation mark.
Click to expand...
Click to collapse
This version does seem to work properly on my unlocked 926: http://goo.im/devs/Hashcode/vanquish/twrp-2.4.4.0-recovery-vanquish.img
It can consistently reboot to recovery now without the droid guy and without having to reflash TWRP. It even works with the Quick Boot apk.
For newly unlocked VZW Droid RAZR HD folks (xt926):
I've added the motorola specific fastboot binaries to my goo.im area:
http://goo.im/devs/Hashcode/vanquish/fastboot
Pick your OS and download the files to somewhere that you can run them from. Then place the recovery file in that same dir. Run the fastboot flash from a command window cd'd to that dir.
Also for XT926 users: I added a new build of TWRP 2.5.0.0 in the main folder for vanquish:
http://goo.im/devs/Hashcode/vanquish/
Enjoy.
Sent from my DROID RAZR HD using Tapatalk 2
Hashcode said:
For newly unlocked VZW Droid RAZR HD folks (xt926):
I've added the motorola specific fastboot binaries to my goo.im area:
http://goo.im/devs/Hashcode/vanquish/fastboot
Pick your OS and download the files to somewhere that you can run them from. Then place the recovery file in that same dir. Run the fastboot flash from a command window cd'd to that dir.
Also for XT926 users: I added a new build of TWRP 2.5.0.0 in the main folder for vanquish:
http://goo.im/devs/Hashcode/vanquish/
Enjoy.
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
Very nice. Excited about my phone again.
Hashcode said:
For newly unlocked VZW Droid RAZR HD folks (xt926):
I've added the motorola specific fastboot binaries to my goo.im area:
http://goo.im/devs/Hashcode/vanquish/fastboot
Pick your OS and download the files to somewhere that you can run them from. Then place the recovery file in that same dir. Run the fastboot flash from a command window cd'd to that dir.
Also for XT926 users: I added a new build of TWRP 2.5.0.0 in the main folder for vanquish:
http://goo.im/devs/Hashcode/vanquish/
Enjoy.
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
Hi Hashcode. The 2.5.0.0 does not have the ability to use External SD for backup storage as the 2.4.4.0 does.
EDIT: Sorry, I stand corrected.
2.5.0.0 does have the option to backup to external SD. It's toward the bottom. It's a grey bar that says "Storage: Internal Storage." You tap that and you can switch it to Micro SD card."
THANKS for your support for the XT926 now that we're unlocked!
Additional: I was successful on my unlocked XT926 using 2.4.4.0 to backup existing stock rom, flash a different rom, then restore the original stock rom. I would use 2.5.0.0. but as I said it does not seem to support the External SD card. Also, when flashing the new rom I had to mount /system by checking in off in the settings. I was mistaken. 2.5.0.0 is fine. It does have the Ext SD option.
(Unlocked bootloader only!!!)How to make your ATRIX HD become a Droid Razr HD/Razr HD (flash XT926/XT925 stock rom on MB886)
do it at your own risk
First of all: you must do this on a bootloader Unlocked ATRIX HD MB886, ATT or Bell no matter.
1.download both stock roms for MB886 and XT926/XT925 from enclosed address.
for ICS(build 7.7.1Q).
MB886 stock Rom
http://sbf.droid-developers.org/dinara/7.7.1Q-144_MB886_MR1-22_SIGNED_CFC.xml.zip
XT926/XT925 stock Rom(XT926 or XT925 on your choice)
http://sbf.droid-developers.org/vanquish/VZW_XT926_4.0.4-7.7.1Q-144_VQW_S3-34-25_CFC.xml.zip
http://sbf.droid-developers.org/van...022.0R_LSAVNQICSTELSTRA_P025_A045_CFC.xml.zip
also works on JB stok roms, do it the same way but be sure to download the both JB stok roms and use JB wifi files to fix wifi issue
2. unzip stock Roms to each folder
3. copy 3 files from MB886 rom folder to XT926/XT925 stock Rom folder.
files name: boot.img; device_tree.bin; emmc_appsboot.mbn. just copy and overwrite the existed files.
4. flash the edtied XT926/XT925 rom with RSD as normal flashing.
a) if you are flashing XT926 on MB886: please use attached 7.7.1Q-XT926_fastboot.xml.zip, unzip and placed on XT926 Rom folder
b) if you are flashing XT925 on MB886: please use attached 7.7.1Q-XT925_fastboot.xml.zip, unzip and placed on XT925 Rom folder
5. as normal flash. wait until phone flash completed, and every thing works just fine except WIFI for XT926.and there is way to solve.
Way to fix WIFI on XT926(MB886 with XT926 rom),
1.root your phone use http://forum.xda-developers.com/showthread.php?t=1943851
2.download attached XT925_ICS_prima.zip or you can copy them from any XT925 ICS ROM, file name prima_wlan.ko and cfg80211.ko
3.unzip and copy the 2 files into system/lib/modules/prima use rootexploer tool, overwrite and change the file permission as original
4.reboot you phone
Trouble shooting:
if you mistake flashed the stock XT926/XT925 rom without modify it or in wrong way. now you will have no screen, please don't worry,
the rom actually can work beyond you can see it. connect the phone with a HDMI cable to monitor or TV.
you can see the screen,but.....without touch.
you can do it with HDMI or blind
to force the phone reset and enter fastboot: push the Vol- and the power key the same time wait for 10 second, then release the power key and waite 2 second then release the Vol-
connect the phone with usb cable, now you can find the adb device on your computer. (repeat if you can not see adb device on your computer)
go into MB886 stock Rom folder and use fastboot command to flash the 3 files manually.
fastboot flash aboot emmc_appsboot.mbn
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot reboot
now you got your screen back
Cool trick
Amazing news if you're a Bell customer.
We can already run their ROMs, somewhat. Does this flash replace any GSM radios?
Markyzz said:
Cool trick
Amazing news if you're a Bell customer.
We can already run their ROMs, somewhat. Does this flash replace any GSM radios?
Click to expand...
Click to collapse
of course it does
Cambridge2009 said:
of course it does
Click to expand...
Click to collapse
you can just flash the modem from the Droid Razr Fastboot files, I think it works (although badly) as I did get signal intermittantly (I am on a AT&T atrix)
you can flash the ICS radio on the JB rom if you are inclined to do so as well.
files like the modem will flash onto a AT&T Atrix HD but the signal is very poor
Please anyone doing this with a developer edition get your unlock key to one of our hackers.
Sent from my MB886
How is the camera.Does it work well?
I'm kinda new to unlocked bootloaders (been using lock VZW moto devices since the D2G)...
I'd like some help in getting my new RAZR i running at it's best. I think I know the steps, but I'm still missing some things... I know I need to...
1. Unlock bootloader via Moto's website
2. CWM by turl1 (is the November 2012 version the most recent, or am I missing something? How do I flash this .img file?)
3. Do I need to root or can I just flash a new ROM from CWM?
4. I think I'd like to tryout Omar-Avelar's 4.1.2 ROM, it looks really good.
I've rooted and rommed several devices (D2G, Droid Pro, D3, GNex, RAZR M, DX), but looking at all the info I can find on the RAZR i, I just keep getting more confused.
Please help, guys! I'd really love to just flash the hell out of this phone when I get it tomorrow and not worry about it anymore :good:
I dropped VZW and my RAZR M, and bought a RAZR i for Straight Talk... a day later Motorola announces that they want to make new phones that are smaller, indestructible, and stock Android. My vision for the perfect phone (except I'd like a slide out QWERTY)... but I'm still excited to show Intel some smartphone love. Is that why the rest of you are here?
Anyways, thanks in advance guys!
1. There is a nice guide by mattlgroff how to unlock the bootloader
http://forum.xda-developers.com/showthread.php?t=1928551
Just read the OP and follow the steps.
2. I don't know if there is a newer image, but the image you found will work too.
After you have unlocked the bootloader, reboot into fastboot mode and connect to your pc. Open the command-line in the directory with the fastboot.exe (if you use Windows) (you get the required files from mattlgroff's thread). Then copy your cwm image file in the same folder and type the following command:
fastboot flash recovery <name of your cwm image>.img
Then press enter and wait until the flash process finished.
3. There is no need to root. Just flash custom rom(which are prerooted) via cwm.
4. It's your choice
Hoping the best, sorry for bad English.
Gesendet von meinem Motorola RAZR i - gerootet & unlocked
cupioscire said:
1. There is a nice guide by mattlgroff how to unlock the bootloader
http://forum.xda-developers.com/showthread.php?t=1928551
Just read the OP and follow the steps.
2. I don't know if there is a newer image, but the image you found will work too.
After you have unlocked the bootloader, reboot into fastboot mode and connect to your pc. Open the command-line in the directory with the fastboot.exe (if you use Windows) (you get the required files from mattlgroff's thread). Then copy your cwm image file in the same folder and type the following command:
fastboot flash recovery <name of your cwm image>.img
Then press enter and wait until the flash process finished.
3. There is no need to root. Just flash custom rom(which are prerooted) via cwm.
4. It's your choice
Hoping the best, sorry for bad English.
Gesendet von meinem Motorola RAZR i - gerootet & unlocked
Click to expand...
Click to collapse
Thanks for your help!
I got my RAZR I unlocked, CWMed, and ROMed.
It's much smoother than my RAZR M is. Looking at them side by side, you can also see that the RAZR M's display is a little bit yellowed compared to the RAZR I. I thought they were exactly the same.
Anyways, thank you for the help!
any guide for unlock bootloader and install CWM in razr d3
Sent from my XT919 using XDA Premium 4 mobile app
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?
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