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?
Currently on VZN, XT1060, MotoX, DEV unlocked bootloader, TWRP, SuperSU:
version: 4.4
kernel: [email protected]#1
system: 140.45.5.ghost_verizon.Verizon.en.US
build: 13.11.1Q2.X-69-3
NO ROM And I only changed two items:
1. VzwEntitlementService.apk via [http://forum.xda-developers.com/showthread.php?t=2536166] by changing the originalVzwEntitlementService.apk to VzwEntitlementService.apk.bak
2. Remove bootloader warning image
Question: for the 4.4.2 update (hopefully coming soon)
1. Can I just get the 4.4.2 update via OTA with my current setup
2. Or do I have a to flash back to stock
Thank you much.
and I'm new to xda.
you need to flash the stock recovery and then run the OTA. after it installs flash your custom recovery back.
dray_jr said:
you need to flash the stock recovery and then run the OTA. after it installs flash your custom recovery back.
Click to expand...
Click to collapse
Thanks, if someone has an unlocked bootloader but is not rooted and they removed the bootloader unlocked message using the command:
fastboot flash logo logo.bin
and used a logo.bin file that has the original kitkat 4.4 logo in it, can they take the OTA without doing anything else?
Also, when you flash the stock recovery, you become unrooted and so then if you flash your custom recovery after the OTA, you reroot, right?
Are you supposed to wipe the davlik/cache or anything else like that before you take the OTA?
Cozume said:
Thanks, if someone has an unlocked bootloader but is not rooted and they removed the bootloader unlocked message using the command:
fastboot flash logo logo.bin
and used a logo.bin file that has the original kitkat 4.4 logo in it, can they take the OTA without doing anything else?
Also, when you flash the stock recovery, you become unrooted and so then if you flash your custom recovery after the OTA, you reroot, right?
Are you supposed to wipe the davlik/cache or anything else like that before you take the OTA?
Click to expand...
Click to collapse
as for the logo i am not sure i think you should be ok .
as for when you flash the stock recovery yes you loose root but when you reflash the custom recovery if you still dont have root just reinstall SuperSU and you will be good to go,
and anytime i flash something i always wipe the cache/davlik
dray_jr said:
and anytime i flash something i always wipe the cache/davlik
Click to expand...
Click to collapse
really so when I flashed my custom recovery to root for the first time, I should have wiped that?
Cozume said:
really so when I flashed my custom recovery to root for the first time, I should have wiped that?
Click to expand...
Click to collapse
you dont have too but it is recommended
dray_jr said:
as for when you flash the stock recovery yes you loose root but when you reflash the custom recovery if you still dont have root just reinstall SuperSU and you will be good to go
Click to expand...
Click to collapse
Hmm, I have a VZW DE, unlocked bootloader, flashed TWRP then SuperSU to get root, then flashed the stock recovery and still have root. I honestly can't remember if I re-rooted after flashing back to stock recovery, but I don't think that I did. Are you saying that flashing to stock recovery should have unrooted the phone? What does it mean if it didn't? I hope I'm remembering correctly.
I'd like to be able to get the OTA 4.4.2 update from VZW when available but I keep reading it's not possible with root. How do I remove root if reflashing the stock recovery didn't do it? I'm coming from a GNex which was much simpler so I want to make sure I'm prepared for the OTA when it arrives. Thanks!
Melarsa said:
Hmm, I have a VZW DE, unlocked bootloader, flashed TWRP then SuperSU to get root, then flashed the stock recovery and still have root. I honestly can't remember if I re-rooted after flashing back to stock recovery, but I don't think that I did. Are you saying that flashing to stock recovery should have unrooted the phone? What does it mean if it didn't? I hope I'm remembering correctly.
I'd like to be able to get the OTA 4.4.2 update from VZW when available but I keep reading it's not possible with root. How do I remove root if reflashing the stock recovery didn't do it? I'm coming from a GNex which was much simpler so I want to make sure I'm prepared for the OTA when it arrives. Thanks!
Click to expand...
Click to collapse
OK,listen and listen closely, by far the best way to accept the ota is flash stock recovery and also flash your system.img, I don't care what other folks say, I've been here for 3 ota's , this will prevent any chances of having issues when accepting the ota. You may also flash Verizon's sbf firmware when available, the later is what I prefer
Sent on my Gummy running Lenoto X
flashallthetime said:
OK,listen and listen closely, by far the best way to accept the ota is flash stock recovery and also flash your system.img, I don't care what other folks say, I've been here for 3 ota's , this will prevent any chances of having issues when accepting the ota. You may also flash Verizon's sbf firmware when available, the later is what I prefer
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Got it, that's what I'll do when the time comes. Thanks!
flashallthetime said:
OK,listen and listen closely, by far the best way to accept the ota is flash stock recovery and also flash your system.img, I don't care what other folks say, I've been here for 3 ota's , this will prevent any chances of having issues when accepting the ota. You may also flash Verizon's sbf firmware when available, the later is what I prefer
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Could I do a TWRP backup of /data and just flash the entire system back to new, take the OTA and TWRP restore /data?
Or does /data contain some stuff that is linked to the version of Android I did the backup with?
fbiryujin said:
Could I do a TWRP backup of /data and just flash the entire system back to new, take the OTA and TWRP restore /data?
Or does /data contain some stuff that is linked to the version of Android I did the backup with?
Click to expand...
Click to collapse
Why would you need to do that? /data isn't going anywhere in the process of flashing system and recovery and then taking an OTA
piccit said:
Why would you need to do that? /data isn't going anywhere in the process of flashing system and recovery and then taking an OTA
Click to expand...
Click to collapse
I thought it might be different because I'm rooted, and encrypted.
fbiryujin said:
Could I do a TWRP backup of /data and just flash the entire system back to new, take the OTA and TWRP restore /data?
Or does /data contain some stuff that is linked to the version of Android I did the backup with?
Click to expand...
Click to collapse
You can try to restore your data after you upgrade, there is no guarantee you won't have any issues but it won't be a huge problem, you'll just have to factory reset. It no different when you flash a custom ROM , if the developer uses a new base then often they request you to do a clean fresh install, otherwise you'll have issues
Sent on my Gummy running Lenoto X
flashallthetime said:
You can try to restore your data after you upgrade, there is no guarantee you won't have any issues but it won't be a huge problem, you'll just have to factory reset. It no different when you flash a custom ROM , if the developer uses a new base then often they request you to do a clean fresh install, otherwise you'll have issues
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
I'm not using a custom ROM though.
fbiryujin said:
I'm not using a custom ROM though.
Click to expand...
Click to collapse
I understand that, try it and see what happens, you might be OK restoring your data , no harm in trying
Sent on my Gummy running Lenoto X
flashallthetime said:
I understand that, try it and see what happens, you might be OK restoring your data , no harm in trying
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
So far no official update available to me even after flashing the stock image from Moto. My biggest goal here is to find a way to backup and restore nandroids from the encrypted phone.
Flash and relock Moto X manually
No lie my a$$hole did pucker up though the whole process but... success woohoo!
I followed the instruction on Motorola website [https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images] one thing I did not have is 'Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory)' had to do some searching; came across [http://forum.xda-developers.com/showthread.php?t=1138092] Thanks for that.
DETAILS (So this is what I was working with):
VZN, XT1060, MotoX, DEV unlocked bootloader, TWRP, SuperSU:
version: 4.4 | system: 140.45.5.ghost_verizon.Verizon.en.US | build: 13.11.1Q2.X-69-3
Did this on my Mac, NOT on PC
Steps:
1. got recovery image
2. got Motorola fastboot utility from | http://forum.xda-developers.com/showthread.php?t=1138092 moto-fastboot-osx.zip
3. used the fastboot from Darwin folder
4. follow steps from motorola website, but did not oem lock [$ fastboot oem lock]
5. last step reboot [$ fastboot reboot] a$$hole pucker up
But success, everything booted up properly even had the warning bootloader unlocked image
There was one point when it got to the Verizon boot image; it took abit longer a$$hole pucker up but finished booting.
Then phone went through the setup process (like new).... It's Miller time!
Come on 4.4.2 update via OTA
_slam said:
No lie my a$$hole did pucker up though the whole process but... success woohoo!
I followed the instruction on Motorola website [https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images] one thing I did not have is 'Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory)' had to do some searching; came across [http://forum.xda-developers.com/showthread.php?t=1138092] Thanks for that.
DETAILS (So this is what I was working with):
VZN, XT1060, MotoX, DEV unlocked bootloader, TWRP, SuperSU:
version: 4.4 | system: 140.45.5.ghost_verizon.Verizon.en.US | build: 13.11.1Q2.X-69-3
Did this on my Mac, NOT on PC
Steps:
1. got recovery image
2. got Motorola fastboot utility from | http://forum.xda-developers.com/showthread.php?t=1138092 moto-fastboot-osx.zip
3. used the fastboot from Darwin folder
4. follow steps from motorola website, but did not oem lock [$ fastboot oem lock]
5. last step reboot [$ fastboot reboot] a$$hole pucker up
But success, everything booted up properly even had the warning bootloader unlocked image
There was one point when it got to the Verizon boot image; it took abit longer a$$hole pucker up but finished booting.
Then phone went through the setup process (like new).... It's Miller time!
Come on 4.4.2 update via OTA
Click to expand...
Click to collapse
I just want to make sure that when you did this all it did was remove root and replace the bootloader, not any data or settings you had on your phone. That is the only thing that worries me before I decide to do the 4.4.2 update.
_slam said:
Currently on VZN, XT1060, MotoX, DEV unlocked bootloader, TWRP, SuperSU:
version: 4.4
kernel: [email protected]#1
system: 140.45.5.ghost_verizon.Verizon.en.US
build: 13.11.1Q2.X-69-3
NO ROM And I only changed two items:
1. VzwEntitlementService.apk via [http://forum.xda-developers.com/showthread.php?t=2536166] by changing the originalVzwEntitlementService.apk to VzwEntitlementService.apk.bak
2. Remove bootloader warning image
Question: for the 4.4.2 update (hopefully coming soon)
1. Can I just get the 4.4.2 update via OTA with my current setup
2. Or do I have a to flash back to stock
Thank you much.
and I'm new to xda.
Click to expand...
Click to collapse
1) You don't need to do much. Revert the Entitlement hack you did, you need the one that came on the device, not a hacked one.
2) Flash the stock recovery back to your phone. You'll need the stock recovery to install the OTA. Just do it the same way you flashed TWRP to your phone but use the stock recovery.img file from the 4.4 .sbf ( http://sbf.droid-developers.org/download.php?device=0&file=5 )
You will NOT lose root flashing the stock recovery, you will NOT lose root taking the OTA.
After updating, use Xposed and the Moto Tether module for tethering instead of using a hacked version of the app.
shadowmonk36 said:
I just want to make sure that when you did this all it did was remove root and replace the bootloader, not any data or settings you had on your phone. That is the only thing that worries me before I decide to do the 4.4.2 update.
Click to expand...
Click to collapse
If you have the Dev edition from VZW, it's simple to install the OTA.
This is what I did as I had root and xposed installed.
1. Download 4.4.2 file from XDA and cut and paste it from download folder to root of sdcard
2. Flash stock 4.4 recovery image via fastboot.
3. Flash 4.4 system image using mfastboot (must use mfastboot)
4. Boot into recovery
5. Apply update and selected the OTA zip.
6. Reboot
7. Power down and boot back into fastboot.
8. Flash TWRP, allow it to root, reboot.
9. Reinstall Xposed framework.
All my data and settings were still there. Even my xposed modules reactivated. No additional setup and my phone was exactly the same but had 4.4.2.
Only caveat is only do this if you've never installed other OS's and have only taken official OTAs from VZW. You need to be on the right bootloader. Don't brick your phone.
Sent from my Dev Edition Moto X
Hi all,
Is there any difference, if I'm with Art or Dalvik for receiving the update?
I don't receive the update yet, still in 4.4.2 and I use Art,
I'm questioning if with Dalvik can get earlier?
Br
Sent from my XT1052 using XDA Free mobile app
If your device is getting the update, it doesn't matter which runtime, ART or Dalvik, you are running. You'll get it when you get it.
Sent from my XT1060 using XDA Premium 4 mobile app
sylarm said:
Hi all,
Is there any difference, if I'm with Art or Dalvik for receiving the update?
I don't receive the update yet, still in 4.4.2 and I use Art,
I'm questioning if with Dalvik can get earlier?
Br
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
I noticed you're using 1052. I'm not 100% but I thought the current soak test was only for XT1060
sylarm said:
Hi all,
Is there any difference, if I'm with Art or Dalvik for receiving the update?
I don't receive the update yet, still in 4.4.2 and I use Art,
I'm questioning if with Dalvik can get earlier?
Br
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
As already advised, it doesn't matter. But please be sure to post in the correct sub-forum next time. Questions belong in Q&A, NOT General. See the 2nd stick post at the top of the General Sub-forum...
sylarm said:
Hi all,
Is there any difference, if I'm with Art or Dalvik for receiving the update?
I don't receive the update yet, still in 4.4.2 and I use Art,
I'm questioning if with Dalvik can get earlier?
Br
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
Me to Still waiting for OTA for my XT1052(Rooted).... I could not find the OTA Capture zip
treyf711 said:
I noticed you're using 1052. I'm not 100% but I thought the current soak test was only for XT1060
Click to expand...
Click to collapse
Moto X (XT 1052) phones in India have already started receiving the 4.4.4 update
Here in Portugal nothing, and this update I is missing here, to fix the S. O. Battery drain.
At least I hope so...
Sent from my XT1052 using XDA Free mobile app
yekollu said:
Moto X (XT 1052) phones in India have already started receiving the 4.4.4 update
Click to expand...
Click to collapse
Have you seen anyone having the 4.4.4 on an Indian X? Moto announced about the update kinda quickly.
devilsdouble said:
Have you seen anyone having the 4.4.4 on an Indian X? Moto announced about the update kinda quickly.
Click to expand...
Click to collapse
Yep!!! Not much of a cosmetic difference though. Phone appliccation looks a little different, there is the new alert app and also the Google+ app (with accompanying Photos)
Not much difference compared to 4.4.2 I hope it gives better battery life. light user interface of dialer, camera tweaks, added pause button in video recording.
Sent from my XT1052 using XDA Free mobile app
Update 4.4.4 Xt1052
Today morning, when i woked up and checked my phone, there was a update notification of 4.4.4. I was pretty much exicted looking that and i start the update process.
Now when the download was completed i clicked on Install the update, phone automatically powered off and rebooted into the TWRP and does nothing with that update. I selected that zip update file from cache folder and failed to install from TWRP as well. Then i rebooted the phone and after some time like 1 minute phone again rebooted into TWRP this time i removed CACHE so that next time the phone will not reboot and it works fine but i can't install the update
Please tell me how should i update now from 4.4.2 to 4.4.4, , if you did on your rooted moto x. I only unlocked bootloader and din't change the rom. Rom is still the same which i got at the time of purchase
vijayid_94 said:
Today morning, when i woked up and checked my phone, there was a update notification of 4.4.4. I was pretty much exicted looking that and i start the update process.
Now when the download was completed i clicked on Install the update, phone automatically powered off and rebooted into the TWRP and does nothing with that update. I selected that zip update file from cache folder and failed to install from TWRP as well. Then i rebooted the phone and after some time like 1 minute phone again rebooted into TWRP this time i removed CACHE so that next time the phone will not reboot and it works fine but i can't install the update
Please tell me how should i update now from 4.4.2 to 4.4.4, , if you did on your rooted moto x. I only unlocked bootloader and din't change the rom. Rom is still the same which i got at the time of purchase
Click to expand...
Click to collapse
........flash back 4.4.2 stock recovery.....
samwathegreat said:
........flash back 4.4.2 stock recovery.....
Click to expand...
Click to collapse
Bro i had mentioned that i din't changed the rom, its already the stock one which i got with it. I had just unlocked the bootloader.
Do i still need to go to Stock
vijayid_94 said:
Bro i had mentioned that i din't changed the rom, its already the stock one which i got with it. I had just unlocked the bootloader.
Do i still need to go to Stock
Click to expand...
Click to collapse
Stock ----recovery----. You specifically said it rebooted into TWRP - which means you HAD to have flashed custom recovery. So flash stock recovery back on - from the 4.4.2 sbf of your carrier:
fastboot flash recovery recovery.img
and assuming you haven't made any significant modifications to /system, the OTA will install without issue. You data will be intact.
Recovery does not = ROM. Two different things.
Correct! Stock recovery must be present or the OTA update will fail.
If you have Xposed with any module you must remove them too.
Flashed stock recovery and still unsuccessful with 4.4.4 OTA upgrade
This is for Verizon Developer's Moto X with an unlocked bootloader.
I forgot that I loaded TWRP on my wife's phone so I tried to take the update and it failed. I also had the modified vzwentitlement.apk loaded so that she could use native tethering. So here's what I did:
- Deleted the modified vzwentitlement.apk
- Removed the ".bak" from the original vzwentitlementservice.apk.bak and the vzwentitlementservice.odex.bak files
- Unrooted the phone using SuperSU's Permanent Unroot option in settings (not sure that was required but didn't want to take any chances
- Downloaded and unzipped the Moto X 4.4.2 from the Motorola firmware site
- Copied the unzipped recovery.img to the Minimal ADB and Fastboot directory
- Flashed the stock recovery back to the phone
I did all that and the phone went into recovery with the little green Droid guy with the hatch open. The blue progress line got about halfway done when the phone rebooted and said it was unsuccessful.
Any ideas what I'm missing? I'd hate to have to flash back to 4.4.2 and lose all her settings, but I will if no one has any better suggestions.
benjamin1492 said:
This is for Verizon Developer's Moto X with an unlocked bootloader.
I forgot that I loaded TWRP on my wife's phone so I tried to take the update and it failed. I also had the modified vzwentitlement.apk loaded so that she could use native tethering. So here's what I did:
- Deleted the modified vzwentitlement.apk
- Removed the ".bak" from the original vzwentitlementservice.apk.bak and the vzwentitlementservice.odex.bak files
- Unrooted the phone using SuperSU's Permanent Unroot option in settings (not sure that was required but didn't want to take any chances
- Downloaded and unzipped the Moto X 4.4.2 from the Motorola firmware site
- Copied the unzipped recovery.img to the Minimal ADB and Fastboot directory
- Flashed the stock recovery back to the phone
I did all that and the phone went into recovery with the little green Droid guy with the hatch open. The blue progress line got about halfway done when the phone rebooted and said it was unsuccessful.
Any ideas what I'm missing? I'd hate to have to flash back to 4.4.2 and lose all her settings, but I will if no one has any better suggestions.
Click to expand...
Click to collapse
Use the FXZ instead. It is a "keep data" FXZ which means that all here data and apps will be intact. It will require re-flashing TWRP, and re-rooting afterwards. You will also need to re-do the entitlement hack. It's very easy. You can use RSD Lite, and you should be back up and running with everything intact in less than 15 minutes from start.
The FXZ method does not use a manifest since it replaces your partitions completely - except for /data (where all your apps and settings are stored).
http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
Hey guys.
I had download stock recovery for my Moto X.
The zip contain many files as seen into the image below.
Please someone tell me the procedure of flashing them into my phone. I don't know actually how to go now. Do i need to wipe all the data from the phone or just have to wipe system only.
Is the below commands are enough or i have to do some other things as well.
adb reboot bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
Sent from my XT1052 using XDA Free mobile app
samwathegreat said:
Use the FXZ instead. It is a "keep data" FXZ which means that all here data and apps will be intact. It will require re-flashing TWRP, and re-rooting afterwards. You will also need to re-do the entitlement hack. It's very easy. You can use RSD Lite, and you should be back up and running with everything intact in less than 15 minutes from start.
The FXZ method does not use a manifest since it replaces your partitions completely - except for /data (where all your apps and settings are stored).
http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
Click to expand...
Click to collapse
That did the trick, or at least a variation of it did the trick. The post said that the new 4.4.4 FXZ actually DID wipe date, so I followed the RSD Flasher instructions but kept data with a fresh 4.4.2 flash instead. Then I downloaded the 4.4.4 OTA. This time it took. I have re-rooted and got my tether hack back in place. Thanks for all your help.
vijayid_94 said:
Hey guys.
I had download stock recovery for my Moto X.
The zip contain many files as seen into the image below.
Please someone tell me the procedure of flashing them into my phone. I don't know actually how to go now. Do i need to wipe all the data from the phone or just have to wipe system only.
Is the below commands are enough or i have to do some other things as well.
adb reboot bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
Fastboot flash recovery recovery.IMG
Should be sufficient. If you still can't take the ota, then also do:
mfastboot flash system system.img
Now you should be able to accept the ota without losing data. You will need to flash TWRP back and re-root.
If anything goes wrong, you will run all the commands you listed but that WILL erase all of your data.
Good luck :good:
This does work to upgrade from 4.4.2 to 4.4.4 and there was no data/setting loss. I am running Verizon, developer phone, rooted, with xposed. Here are the directions I used:
1. disable Xposed - I just went to the app and uninstalled it
2. boot into bootloader/fastboot - connect your computer to the phone via USB. Then push the down volume and power at the same time. This will take you to the bootloader/fastboot
3. flash stock recovery (fastboot flash recovery yourfilename.img) - to do this (and to flash stock system) you need the motorola fastboot files and you will need to use the command prompt on the PC. for directions and download for the fastboot files check out this link - http://www.addictivetips.com/android/root-moto-x-install-cwm-recovery-complete-guide/ To actually download the stock recovery and stock system files you can download them here (look for 4.4.2 verizon - http://sbf.droid-developers.org/phone.php?device=0. I actually pasted the recovery.img/stock.img files into the windows fastboot folder and accessed CMD prompt from there to flash them. I flashed recovery then moved onto stock. I did not reboot until both were done.
4. flash stock system (fastboot flash system yourfilename.img)
5. reboot (stay in the CMD prompt and type - fastboot reboot)
6. update via OTA
7. reboot
You are now stock unrooted 4.4.4, so just re-apply root the same way you did the first time:
1. boot into bootloader/fastboot - you should be able to follow the directions from above to do this now
2. flash custom recovery - you should be able to follow the directions from above to do this now. Note that I tried CWM and it didnt work until I used TWRP. - download the latest version here and stick in the same fastboot folder you were using above - http://teamw.in/project/twrp2
3. boot to recovery - make sure you do this from the bootloader/fastboot screen. To do it, press down until you get to recovery then up to actually select it. I kept pressing power to select which doesnt actually select it.
4. flash SuperSU - this should be on your phone from the first time you rooted. If doing a new root you will need to get it first.
5. reboot
6. re-enable Xposed - i just reinstalled it and all of my settings were back
7. reboot
- BAM you are done!
I'm curious to see if this works the same for unlocked non developer edition Moto X's on VZW too
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
dhoppy said:
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
Click to expand...
Click to collapse
Multiple reports all over the forum say YES. (must flash stock recovery back, FIRST -- OR just use the FXZ and don't worry about having to flash stock recovery...)
Also, to the OP: questions belong in Q&A, not General. See the 2nd Sticky post at the top of the General forum....please post in the correct forums in the future...
I have a vzw DE
I took the 4.4.4 FXZ file from the other thread and just flashed it, no prep, didn't disable xposed.I was flashing in fastboot, not recovery, so its not checking for intact files. Then had to twrp/root and re-enable xposed.
But if you want to take the OTA then your procedure would be good.
Ryphez said:
I'm curious to see if this works the same for unlocked non developer edition Moto X's on VZW too
Click to expand...
Click to collapse
There is no difference whatsoever between an unlocked dev edition and any other unlocked X. The ONLY difference is the dev edition keeps its warranty when you unlock.
Whats the best twrp for root on 4.4.4
Mickoou said:
Whats the best twrp for root on 4.4.4
Click to expand...
Click to collapse
How about the latest version from the official source? Here: http://techerrata.com/browse/twrp2/ghost
It will root for you. Just flash w/fastboot, then "fastboot reboot-bootloader", then VOL DOWN to RECOVERY, and VOL UP to select it. When you go to exit, it will offer to install SuperSU Installer. Once booted, launch SuperSU Installer, and select Play Store method.
dhoppy said:
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
Click to expand...
Click to collapse
No, you should be the guinea pig for all of us.
I can confirm that this works. I did it. I did not lose any data. It took about 20 minutes total. I already had everything installed otherwise you are looking at about 45 minutes.
The only reason to flash stock system.img before taking an OTA is if you made so many changes to system files you can't remember them to undo them. i.e. you modified your system so much that flashing system.img is the fastest way back to stock so it passes the validation checks of the OTA.
I thought there is an Xposed disabler (in the xposed thread) that you can run rather than uninstalling?
That being said.. this information has been the same for EVERY OTA Update. You have to flash stock recovery for the OTA to install, and your system can't be modified too much or it will fail the validation checks built into the OTA.zip. (i.e. there is a manifest file that checks for specific files and their check sums before it will flash the ota).
IF you are close enough to stock (like I am... stock, unlocked, rooted, with adfree, wifi tether for root, greenify, Quick boot, and a few other apps that require root), you can just flash stock recovery and take the OTA.
IF you are close enough to stock... you can also use the following... WITHOUT a PC... i.e. you haven't modified system too much, etc.
Place stock recovery.img, the latest TWRP img, the latest SuperSU.zip and the OTA.zip on your phone's DOWNLOAD folder.
Install Rashr.
Use Rashr to to flash stock recovery (select other from storage, and select your stock recovery). When it completes, pick the option to reboot to stock recovery.
From stock recovery, install the update zip and reboot the phone.
After the update install process is complete, use Rashr to flash TWRP (again, other from storage and pick your TWRP). When prompted, reboot into recovery (so twrp sticks). When in TWRP, select reboot to system.
If you lost root, reboot into TWRP recovery and install SuperSU.zip
KidJoe said:
The only reason to flash stock system.img before taking an OTA is if you made so many changes to system files you can't remember them to undo them. i.e. you modified your system so much that flashing system.img is the fastest way back to stock so it passes the validation checks of the OTA.
I thought there is an Xposed disabler (in the xposed thread) that you can run rather than uninstalling?
That being said.. this information has been the same for EVERY OTA Update. You have to flash stock recovery for the OTA to install, and your system can't be modified too much or it will fail the validation checks built into the OTA.zip. (i.e. there is a manifest file that checks for specific files and their check sums before it will flash the ota).
IF you are close enough to stock (like I am... stock, unlocked, rooted, with adfree, wifi tether for root, greenify, Quick boot, and a few other apps that require root), you can just flash stock recovery and take the OTA.
IF you are close enough to stock... you can also use the following... WITHOUT a PC... i.e. you haven't modified system too much, etc.
Place stock recovery.img, the latest TWRP img, the latest SuperSU.zip and the OTA.zip on your phone's DOWNLOAD folder.
Install Rashr.
Use Rashr to to flash stock recovery (select other from storage, and select your stock recovery). When it completes, pick the option to reboot to stock recovery.
From stock recovery, install the update zip and reboot the phone.
After the update install process is complete, use Rashr to flash TWRP (again, other from storage and pick your TWRP). When prompted, reboot into recovery (so twrp sticks). When in TWRP, select reboot to system.
If you lost root, reboot into TWRP recovery and install SuperSU.zip
Click to expand...
Click to collapse
Thanks for the tip. I believe I did it the way I mentioned because last time gravity box didnt have a wifi tether available so I had to modify the system files. this time I didnt touch them.
Flashing system.img is imo the smartest move to ensure the OTA takes. It's worth it as it only takes a minute and you don't have to even think about what you changed. Plus, it doesn't delete your data.
You are in there flashing stock recovery anyway, might as well.
Sent from my Dev Edition Moto X
Schaweet said:
Flashing system.img is imo the smartest move to ensure the OTA takes. It's worth it as it only takes a minute and you don't have to even think about what you changed. Plus, it doesn't delete your data.
You are in there flashing stock recovery anyway, might as well.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
+1 :good:
Schaweet said:
Flashing system.img is imo the smartest move to ensure the OTA takes. It's worth it as it only takes a minute and you don't have to even think about what you changed. Plus, it doesn't delete your data.
You are in there flashing stock recovery anyway, might as well.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I'm getting an error while attempting to flash the system.img. I don't remember the exact wording but it was something like "data exceeds download buffer". I flashed the recovery.img without issue. I tried to take the OTA and it gets halfway through and craps out with the red exclamation triangle... Any ideas?
zoid_99 said:
I'm getting an error while attempting to flash the system.img. I don't remember the exact wording but it was something like "data exceeds download buffer". I flashed the recovery.img without issue. I tried to take the OTA and it gets halfway through and craps out with the red exclamation triangle... Any ideas?
Click to expand...
Click to collapse
Are you using mfastboot to flash system.img? You can't use regular fastboot. Just search for mfastboot.
Sent from my Dev Edition Moto X
Schaweet said:
Are you using mfastboot to flash system.img? You can't use regular fastboot. Just search for mfastboot.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Thank you Thank you.... That was it.
dhoppy said:
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
Click to expand...
Click to collapse
1.6 SU was the only issue I had, I got the latest and had no issue
http://download.chainfire.eu/supersu
KidJoe said:
[*]Place stock recovery.img, the latest TWRP img, the latest SuperSU.zip and the OTA.zip on your phone's DOWNLOAD folder.
Click to expand...
Click to collapse
Where do I get the stock recovery.img file?
Thank you!
fede_arg said:
Where do I get the stock recovery.img file?
Thank you!
Click to expand...
Click to collapse
The OP tells you in the very first post...
Hi Nexus 6 experts -
My Nexus 6 arrived today, so of course the first thing I did was follow this thread to unlock the boot loader, gain root, and TWRP:
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Now I'm reading about how this breaks OTA updates, and after 30 minutes of looking for the right answer across the forums, I'm in need of some more accurate advice.
1. Is this the right location for downloading factory images?
https://developers.google.com/android/nexus/images
Part of my confusion stems from the fact that my build number for 5.0 is currently LNX07M, and the one listed for 5.0 is LRX21O. Does this matter at all? Could I flash the files from 5.0.1 (LRX22C) without any issue?
2. In order to flash 5.0.1, is this the right procedure to follow?
http://forum.xda-developers.com/showpost.php?p=57411133&postcount=75
I'm looking for how to flash the right images in the right sequence with fastboot, as I'd rather not use any toolkits. The aforementioned post flashes the radio image, then the system image. Is anything else missing there?
3. I'm assuming I need to re-flash root again after this point - is the version listed in the beginners guide still applicable?
Since I've had the phone for all of 2 hours I'm trying my best not to brick it. Any insight would be appreciated, thanks!
EDIT: Download the factory images from the google link above and extract everything. The first extraction renders the radio and bootloader images, along with a zip file. Extract the zip file and you'll find the boot, cache, recovery, and system images. Using fastboot is easy:
fastboot flash <type> <filename>
example:
fastboot flash system system.img
As far as I can tell, <type> is specific to every file. Very easy, only takes a few minutes, and you only need to flash what you need.
Yes Lollipop requires 100% stock for OTA updates now. But OTA is overrated
1. Yes indeed. thats the right place. Wasn't LNX07M the pre-release developer preview?
2. The image contains a flash-all script for windows and linux, but this will wipe data (unless you remove the -w i believe) but I prefer to flash individually.
flashing Radio isnt essential but you will probably want to try it at least. You also want to flash the system and boot images (boot image is the kernel). Then flash SuperSU from recovery. I know OTA's have a script that replace your recovery on first boot if you dont immediately root. I havent flashed a factory image for a whiole so not sure if these have them too, so just a word of caution there.
3. I tend to go for the latest from the beta thread personally, but there is no hard going for older versions except that some things might not gain root properly due to the changes with SElinux etc
Hey thanks rootSU - this is exactly what I was looking for! Once I run through that process I'll add the details to my original post.
So I am on LRX210, rooted and am running twrp recovery. Sounds like I should download the 5.0.1 image and flash the boot, cache, recovery, system, and radio files individually, correct?
Any specific order?
scotbotmosh said:
So I am on LRX210, rooted and am running twrp recovery. Sounds like I should download the 5.0.1 image and flash the boot, cache, recovery, system, and radio files individually, correct?
Any specific order?
Click to expand...
Click to collapse
I only flashed a few of the files, like boot, system and radio. Recovery will remove twrp so you don't want that. Order doesn't seem to matter.
im on 5.01 decrypted boot img...if 5.02 comes out all i do is flash an xda modded 5.02 img boot decrypted file and all the other files except for userdata.img to save all my data and files/settings right? no neeed to revert back to stock, update to ota official 5.02, blah blah ...
cobyman7035 said:
im on 5.01 decrypted boot img...if 5.02 comes out all i do is flash an xda modded 5.02 img boot decrypted file and all the other files except for userdata.img to save all my data and files/settings right? no neeed to revert back to stock, update to ota official 5.02, blah blah ...
Click to expand...
Click to collapse
Yeah you shouldn't need to revert/unroot and use the OTA. Just flash what you need from the factory image. System is the only major one to flash, boot would be the kernel, so use whatever you need for the decrypted version.
I'm assuming userdata overwrites /data which would wipe your files and apps.