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:
Related
NOTE, YES, THIS IS A LONG DRAWN OUT VERSION OF WHAT IS ACTUALLY VERY VERY QUICK PROCESS. This is for reference only. I know there are a few people out there just like me who probably had a few small hickups getting back to stock with the firmware. This is to help "spoon-feed" the instructions to you.
FYI NOTE - I originally did this for the Moto X back when I still had it. Video below was on a VZW Moto X back in September. I also did the EXACT same process when I received my MAXX two days ago. Exact same hardware, same process.
Two Methods-
Method 1 - RSD Lite
Method 2 - Manual Flash
If you cannot get RSD Lite to recognize your device, try Method 2, it works like a charm!
Downloads:
I assume you already have adb drivers if you're even here.....otherwise get them from the latest sdk here: http://developer.android.com/sdk/index.html
Moto Drivers (Motorola Device Manager): https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
RSD Lite (I used version 6.1.5): https://dl.dropboxusercontent.com/u/42057363/RSDLite_v6.1.x.zip - Extract and use 6.1.5
Stock Firmware: http://sbf.droid-developers.org/ thanks to Skrilax_CZ and Firmware Team
Moto Fastboot exe: https://drive.google.com/file/d/0B0dUKGxGylgNTk43eU0xc3VLekE/edit?usp=sharing - NOTE - YOU MUST UNZIP AND USE THIS WHERE MANUAL FLASH SAYS "mfastboot"
My Setup: Windows 8 machine <--obvious driver issues as usual
My Devices: VZW Moto X AND Droid MAXX
METHOD 1 - RSD LITE
Step One - Download and install RSD Lite. At the moment, I can't find where I got mine from, so anyone who wants to add a proper link to it would be appreciated. I used version 6.1.5 and it worked fine.
Step Two - proper driver installation. If you're like me, you probably at one point got drivers quasi-working but here's what I did that worked - download and install "Motorola Device Manager" and it *should* give you the proper drivers. This was necessary (maybe) because I could get adb to recognize my device, as well as fastboot, however RSD refused to see it. This install fixed that.
Step Three - download and install the proper firmware for your device. NOTE: You MUST MUST MUST choose the right firmware for your device or you will FUBAR your phone.....not my responsibility.
Step Four - Unzip your firmware zip file, open it up through the layers and find the file "VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF" or whatever version/carrier/build number file yours is, its the XML Document file. Right click -> Open with.. -> Notepad/word editor/XML Editor/wordpad and find the line:
<step operation="getvar" var="max-download-size" />
^^^You need to select this entire line and just delete it out of the file. This is the line that gives fastboot flash error. Select it, delete it, then resave the file an exit out of it. Done.
NOTE: This is required or the firmware flash will immediately fail giving a "failed flashing process. Unknown fastboot command. (getvar)"
-For the sake of security, and not messing with important files, I'd actually recommend zipping the file back up after this and keeping as your final version (once you've confirmed yours works correctly)
Step Five - Plug in phone, enable USB debugging, then "adb reboot bootloader" - this will boot you into fastboot mode so RSD will recognize your phone
Step Six - Run RSD Lite - note that some people have had trouble and have to right-click run as administrator. In RSD Lite, make sure phone shows up in slot 1 - mine shows up, under Model, just says fastboot, USB port type, info N/A, important part is that it shows as Connected in status. Select the three-dot browse file button, then you can go down into the unzipped file you created of the XML folder, and select the XML file that we just edited earlier (or select the rezipped package). Select open and flash. (or decompress and flash)
Step Eight - Profit
METHOD 2 - MANUAL FLASHING
Much easier AND don't have to deal with getting RSD Lite to work....
Note - this was done on VZW variant, and based on XML file of that particular firmware. Get these instructions from your firmware package XML file.
Note 2 - VERY IMPORTANT!!! - You MUST use mfastboot (Moto fastboot) for the system.img flash as its too large for standard Android fastboot to handle, your flash WILL fail if you use standard fastboot. Hence why it says "mfastboot" this is not a typo.
First simply boot into fastboot mode - manually OR adb reboot bootloader
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
Excellent guide, I'm not bricked but I'm pretty sure it will be useful for someone else!, thanks for your time and effort
Sent from my Nexus 7 using XDA Premium 4 mobile app
Nice guide. Used rsdlite and flashed stock. Just upgraded 4.4. Very satisfied with new version along with nova pro
Sent from my XT1080 using xda app-developers app
Question: will this method work if I flashed a custom radio? In other words, does this completely overwrite all pre-existing mods (custom bootloader, custom radio, system file mods)? Thanks!
allquixotic said:
Question: will this method work if I flashed a custom radio? In other words, does this completely overwrite all pre-existing mods (custom bootloader, custom radio, system file mods)? Thanks!
Click to expand...
Click to collapse
Yes it does, I'm using a custom radio too, I'm waiting for the kit Kat sbf
Sent from my Nexus 7 using XDA Premium 4 mobile app
allquixotic said:
Question: will this method work if I flashed a custom radio? In other words, does this completely overwrite all pre-existing mods (custom bootloader, custom radio, system file mods)? Thanks!
Click to expand...
Click to collapse
What kind of custom radio? Thought you couldn't flash that kind of stuff without an s off device?
Sent from my XT1080 using xda app-developers app
YoungSkeezy said:
What kind of custom radio? Thought you couldn't flash that kind of stuff without an s off device?
Click to expand...
Click to collapse
Just the radio that leaked that everyone thought was a test of AWS. The radio worked, but I didn't notice any higher speeds.
No, you don't need S-OFF to flash a custom radio.
will it work if i want to downgrade from 4.4 to 4.2 ?
No
YOU SIR...ARE THE MAN!!!!! worked flawlessly..i thought i had permanently bricked my replacement phone.. but thanks to you and another fellow who directed me to the FXZ files.. the new phone is up and running..and I can send the old one back!!!
Worked great. Not difficult at all.
Sent from my XT1080 using xda app-developers app
First of all, a lot of Thanks for this useful thread sir...
I am using DroidMAXX with Unlocked BL, rooted and customRecovery flashed... I can see the lines to flash boot image and recovery image. So on flashing this my phone's BL will be relocked and stock recovery will be flashed, isn't it. Later I can again unlock using the code, right? And I can use this method to receive OTA (for 4.4.2) right?
kanagadeepan said:
First of all, a lot of Thanks for this useful thread sir...
I am using DroidMAXX with Unlocked BL, rooted and customRecovery flashed... I can see the lines to flash boot image and recovery image. So on flashing this my phone's BL will be relocked and stock recovery will be flashed, isn't it. Later I can again unlock using the code, right? And I can use this method to receive OTA (for 4.4.2) right?
Click to expand...
Click to collapse
No, this will NOT re-lock your bootloader. It does flash the stock recovery and unroot you so you can receive an OTA.
OH... Thanks ji for the clarificaiton... So I can flash it and reroot by flashing twrp recovery? Why I am asking is I have messed with the active notifications and other Moto apps using Titanium Backup.. Now I want my root + Active Notifications back...
Thanks again, my friend...
kanagadeepan said:
OH... Thanks ji for the clarificaiton... So I can flash it and reroot by flashing twrp recovery? Why I am asking is I have messed with the active notifications and other Moto apps using Titanium Backup.. Now I want my root + Active Notifications back...
Thanks again, my friend...
Click to expand...
Click to collapse
yes, just flash twrp and reroot
I know that this won't work for downgrading from 4.4 to 4.2.2, but I'm wondering why not? What is making it so that this doesn't work? I'm thinking it has something to do with the new recovery that was flashed with the update, but I'm not sure.
Jay_P11 said:
I know that this won't work for downgrading from 4.4 to 4.2.2, but I'm wondering why not? What is making it so that this doesn't work? I'm thinking it has something to do with the new recovery that was flashed with the update, but I'm not sure.
Click to expand...
Click to collapse
Bootloader
akellar said:
Bootloader
Click to expand...
Click to collapse
Alright thanks for clarifying. My battery life is absolutely horrid, about 8 hours MAX per day before I need a charge, and it was never like this on 4.2.2 :/ 4.4's "Battery Saver" feature in WiFi settings never works anymore either, it just turns itself off the second I turn it on. Definitely some major bugs in this build, and I'm hoping they get fixed in the next update. If they don't, then I'm just going to pony up $300 for early termination and get an LG G2.
One more thing, this should work for restoring back to factory 4.4 on 4.4 then right? Maybe my update is broken and it just needs a clean install for the battery saver to work?
TechSavvy2 said:
First simply boot into fastboot mode - manually OR adb reboot bootloader
Code:
fastboot oem fb_mode_set
Click to expand...
Click to collapse
So I just send up sitting at "waiting for device" after executing that line. RSD won't recognize my phone either--tried different cables.
Thoughts?
Hi all!
Just a quick synopsis. I've held off for a while. I've read just about everything related as it's come across here over the past few weeks.
I've been perfectly happy with where I sat:
VZW Dev Ed, Rooted, TWRP, xPosed, Tehter & Gravity Box modules.
I'm not fond of ADB commands, etc. but can work my way through them.
Today, I decided to to take a quick stab at things (a little differently).
So, here's what I did:
1) Unfroze some bloat
2) Unistalled xposed Framework
3) USED Flashify to backup my TWRP
4) USED Flashify to install stock recovery
5) Downloaded OTA
6) Installed 4.4.2 update
7) It FAILED
So, I restored my TWRP recovery through Flashify; re-installed xPosed Framework; refroze the bloat and I'm back to where I was before.
The only thing that I really think might have caused the update to fail was the fact that I had AOSP Browser installed. (with its related installer)
So, that's my question here....opinions...would that cause the update to fail?
I've since tried to uninstall that browser with the related installer but it keeps getting hung and force closes when trying.
Opinions? (other than..."please, use ADB commands")
I'm assuming flashing my system ui might take care of that?
Thanks for ideas. I know I'll take the time to get it done "proper". Just haven't been pressed to do it yet.
Unfreeze everything and make sure the tether hack is reversed. I believe it tells you where it failed in recovery when it's doing its thing. I'm in the same boat as you, but I'm just going to wait until Moto releases the new image.
hlaalu said:
Unfreeze everything and make sure the tether hack is reversed. I believe it tells you where it failed in recovery when it's doing its thing. I'm in the same boat as you, but I'm just going to wait until Moto releases the new image.
Click to expand...
Click to collapse
Well, it's the tether module (not the hack)...so uninstalling xPosed would take care of that I'd think.
When Moto releases the new image...what's your plan? Able to flash that without losing data, etc?
Are you using the VZW specific stock recovery.img directly obtained from the Motorola website that you extracted yourself from the zip file you got there? I wouldn't necessarily trust any other stock recovery floating around.
Did you run the xposed cleaner zip or just uninstall it? It easier to just flash the system and recovery images via mfastboot. It takes two seconds assuming you have the Sdk installed and Moto drivers installed.
Sent from my Dev Edition Moto X
Dburgessme2 said:
Well, it's the tether module (not the hack)...so uninstalling xPosed would take care of that I'd think.
When Moto releases the new image...what's your plan? Able to flash that without losing data, etc?
Click to expand...
Click to collapse
Hmm double check that it checks for subscription when tethering to make sure it changed the files back?
I'm a little rusty with fastboot, but it doesn't wipe your data unless you ask it to:
Code:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
[B]$ fastboot erase userdata[/B]
$ fastboot erase cache
$ fastboot oem lock
So I think if you just don't do the fastboot erase userdata command your data is safe. I'll wait for someone with more experience to confirm that.
But even if that's not the case, I'll still wait because we have to fastboot for root and recovery anyways, might as well just do everything in one go.
Schaweet said:
Did you run the xposed cleaner zip or just uninstall it? It easier to just flash the system and recovery images via mfastboot. It takes two seconds assuming you have the Sdk installed and Moto drivers installed.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I only used the Uninstall from within itself. Where is the cleaner zip? Might have to do a search.
Thanks!
DB's Nexus 7
Roland Stone said:
Are you using the VZW specific stock recovery.img directly obtained from the Motorola website that you extracted yourself from the zip file you got there? I wouldn't necessarily trust any other stock recovery floating around.
Click to expand...
Click to collapse
Nope, I didn't extract it myself. I'll have to do that to make sure I've got the "real deal".
Thanks!
DB's Nexus 7
Dburgessme2 said:
I only used the Uninstall from within itself. Where is the cleaner zip? Might have to do a search.
Thanks!
DB's Nexus 7
Click to expand...
Click to collapse
It's the xposed disabler zip that is put in the root of your SD card when you install xposed.
Sent from my Dev Edition Moto X
Schaweet said:
It's the xposed disabler zip that is put in the root of your SD card when you install xposed.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Just flash it through recovery I assume?
DB's Nexus 7
Yes
Flashing the system and recovery images is still the most fail safe method. It doesn't erase your settings or data.
Sent from my Dev Edition Moto X
Flashing the stock recovery did the trick for me. No data loss either.
Sent from my Nexus 7 using xda app-developers app
awerner68 said:
Flashing the stock recovery did the trick for me. No data loss either.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
So, what method did you use to update? Fastboot/ADB commands or the "on phone" method I described in first post?
Easiest thing to do is fxz save data with HoM. If you don't have HoM set up you can modify the fxz XML. File to not erase user data and fxz. You should be able to update then. The fxz puts stock recovery back so you don't have to flash anything. Update install twrp root done.
Sent from my XT1080 using xda app-developers app
bigv5150 said:
Easiest thing to do is fxz save data with HoM. If you don't have HoM set up you can modify the fxz XML. File to not erase user data and fxz. You should be able to update then. The fxz puts stock recovery back so you don't have to flash anything. Update install twrp root done.
Sent from my XT1080 using xda app-developers app
Click to expand...
Click to collapse
So, fxz the 4.4.2 image for vzw 1060 through rsd lite? But remove "erase data" line from the xml file first. Then, TWRP recovery back (root). That about right?
I think the last thing I used rsd lite for was on old Droid X.
Any quick refresher would be appreciated.
Thanks!
DB's Moto X
Yeah that is pretty much it. As far as what line to delete I'm not sure I use HoM it does it all autmatically. Only tips I can give you is don't use USB 3 it doesn't work with rsd only USB 2 if you plug in your phone and don't see it in rsd change USB port. Make sure debugging is checked.
Sent from my XT1080 using xda app-developers app
bigv5150 said:
Yeah that is pretty much it. As far as what line to delete I'm not sure I use HoM it does it all autmatically. Only tips I can give you is don't use USB 3 it doesn't work with rsd only USB 2 if you plug in your phone and don't see it in rsd change USB port. Make sure debugging is checked.
Sent from my XT1080 using xda app-developers app
Click to expand...
Click to collapse
OK. And now I have to ask... What is HoM? (googled with no good results)
DB's Nexus 7
Dburgessme2 said:
So, what method did you use to update? Fastboot/ADB commands or the "on phone" method I described in first post?
Click to expand...
Click to collapse
I downloaded the .ZIP file and flashed it with TWRP. Using TWRP to replace itself.
HoM (House of Moto) its a script that allows you to do a full fxz or a save data fxz. It just makes fxz'ing easier here is the site
http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20-for-now/
Sent from my XT1080 using xda app-developers app
bigv5150 said:
HoM (House of Moto) its a script that allows you to do a full fxz or a save data fxz. It just makes fxz'ing easier here is the site
http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20-for-now/
Sent from my XT1080 using xda app-developers app
Click to expand...
Click to collapse
And, this HoM should work with the Vzw 1060 Dev Ed?
DB's Moto X
I updated to 4.4.2 on att with root but now I want factory reset to make sure its fresh so I can get maximum battery life. Anyway I can do that with going all the way back to stock through rsd? Since the stock recovery is not there from rooting.
Sent from my XT1058 using XDA Premium 4 mobile app
Why can't you factory reset with a custom recovery?
I have a locked bootloader. The stock recovery isn't there because the way I rooted my phone it removed it I believe.
Sent from my XT1058 using XDA Premium 4 mobile app
If I'm not mistaken, by taking the OTA, it flashed the stock recovery, which is why it re-enables write protection.
Why can't I factory reset through the settings then? The phone just reboots on any option I select.
Sent from my XT1058 using XDA Premium 4 mobile app
Well, I must be mistaken lol.
You could fastboot and erase userdata, davlik, and cache I think.
JJHunterx said:
Well, I must be mistaken lol.
You could fastboot and erase userdata, davlik, and cache I think.
Click to expand...
Click to collapse
So you don't have any recovery at all? Have you tried booting into recovery?
adb reboot recovery doesn't bring you to your recovery?
This is the message I get doing that:
Partition (recovery) security version downgraded
Fastboot reason: boot failure
Then I have the option to normal reboot, recovery, and factory, and two other options. Selecting the second or third does nothing and ends up just rebooting the phone.
Sent from my XT1058 using XDA Premium 4 mobile app
Bump
Sent from my XT1058 using XDA Premium 4 mobile app
Same problem here
Hopefully somebody can help. I rooted a while back but didn't use rsdlite because it didn't recognize my phone, couldn't get the drivers installed correctly. So I used the method with mfastboot I believe where I manually flashed all the files and had to change one file to att from Verizon for the radio I think. Its been a while and I don't remember the whole process so hopefully somebody can shine a light on a much simpler method of going back.
Sent from my XT1058 using XDA Premium 4 mobile app
If you rooted via the exploits here on xda (slap my Moto, etc) then it replaced your stock recovery with write protection disabled version of Android. You need to download an sbf and extract the recovery image and flash it via fastboot
-Eclipsed Moto X-
rocketsaucev2 said:
If you rooted via the exploits here on xda (slap my Moto, etc) then it replaced your stock recovery with write protection disabled version of Android. You need to download an sbf and extract the recovery image and flash it via fastboot
-Eclipsed Moto X-
Click to expand...
Click to collapse
Will I be able to do that even if my bootloader is locked? If so, I just find the correct 4.4.2 recovery.img and then flash via fastboot?
Sent from my XT1058 using XDA Premium 4 mobile app
dimasp6 said:
Will I be able to do that even if my bootloader is locked? If so, I just find the correct 4.4.2 recovery.img and then flash via fastboot?
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, you can fastboot commands with a locked bootloader. It shouldn't NEED to be your carriers sbf that you take the recovery from but it wouldn't hurt. If you know how to fastboot, you know to put the recovery image in the same directory as your fastboot
-Eclipsed Moto X-
rocketsaucev2 said:
Yes, you can fastboot commands with a locked bootloader. It shouldn't NEED to be your carriers sbf that you take the recovery from but it wouldn't hurt. If you know how to fastboot, you know to put the recovery image in the same directory as your fastboot
-Eclipsed Moto X-
Click to expand...
Click to collapse
Thank you so much I will try doing that.
Edit: well I downloaded the t mobile sbf and extracted it and took the recovery out since the att sbf is not out. When trying to flash it in fastboot I get a preflash validation error and it doesn't go through. Tried it multiple times.
Sent from my XT1058 using XDA Premium 4 mobile app
Well this is frustrating. Tried using mfastboot command instead of fastboot and still get the preflash validation error.
Edit: I feel like I messed up. After reading up on the internet I think I should have flashed the stock recovery before taking the ota update to 4.4.2 because now I am very limited on what I can do aside from unlocking my bootloader I guess.. if that's even still possible through the guy in China although I would rather prefer not to do that.
Sent from my XT1058 using XDA Premium 4 mobile app
dimasp6 said:
I updated to 4.4.2 on att with root but now I want factory reset to make sure its fresh so I can get maximum battery life. Anyway I can do that with going all the way back to stock through rsd? Since the stock recovery is not there from rooting.
Click to expand...
Click to collapse
The full SBF for ATT 4.4.2 hasn't leaked yet. When it does it will be put up on -> http://sbf.droid-developers.org/phone.php?device=0
Until then, an alternate way to reboot the phone in bootloader/fastboot mode, and issue the following commands...
mfastboot erase cache
mfastboot erase data
mfastboot reboot
If you are struggling to get into bootloader/fastboot mode... with your phone booted normally, usb debugging enabled, and ADB and its drivers properly installed and added to your PC's path... connect the phone to the PC via USB cable, open a command prompt and issue the following...
adb reboot bootloader
However, the OTA will only install if you have a stock recovery on your phone. The message about "Partition (recovery) security version downgraded" tells me you may have the Stock Recovery from 4.4 or 4.2.2 on your phone, rather than 4.4.2.
Since the ATT 4.4.2 SBF isn't out yet, try downloading the Verizon or T-Mobile 4.4.2 rom from -> http://sbf.droid-developers.org/phone.php?device=0 unzip it... and use fastboot to flash that recovery.img to your phone..
fastboot flash recovery recovery.img
---------- Post added at 06:18 AM ---------- Previous post was at 06:14 AM ----------
dimasp6 said:
Edit: I feel like I messed up. After reading up on the internet I think I should have flashed the stock recovery before taking the ota update to 4.4.2 because now I am very limited on what I can do aside from unlocking my bootloader I guess.. if that's even still possible through the guy in China although I would rather prefer not to do that.
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Correct. If you have a locked bootloader, and took the 4.4.2 update, you might retain root. but you lose the "Write Protection Disable" that MotoWpNoMo gave you.
On 4.4.2, there is no way to disable write protection unless you can unlock your bootloader. If you lose root, on 4.4.2 there is no way to root.
If you flash the 4.4.2 SBF you wont be able to root and disable write protection if you can't unlock your bootloader. And don't try to downgrade to 4.4 or lower.
If you have ATT, the Chinese web site was the only option to unlock your bootloader, however that seems to have ended.
KidJoe said:
The full SBF for ATT 4.4.2 hasn't leaked yet. When it does it will be put up on -> http://sbf.droid-developers.org/phone.php?device=0
Until then, an alternate way to reboot the phone in bootloader/fastboot mode, and issue the following commands...
mfastboot erase cache
mfastboot erase data
mfastboot reboot
If you are struggling to get into bootloader/fastboot mode... with your phone booted normally, usb debugging enabled, and ADB and its drivers properly installed and added to your PC's path... connect the phone to the PC via USB cable, open a command prompt and issue the following...
adb reboot bootloader
However, the OTA will only install if you have a stock recovery on your phone. The message about "Partition (recovery) security version downgraded" tells me you may have the Stock Recovery from 4.4 or 4.2.2 on your phone, rather than 4.4.2.
Since the ATT 4.4.2 SBF isn't out yet, try downloading the Verizon or T-Mobile 4.4.2 rom from -> http://sbf.droid-developers.org/phone.php?device=0 unzip it... and use fastboot to flash that recovery.img to your phone..
fastboot flash recovery recovery.img
---------- Post added at 06:18 AM ---------- Previous post was at 06:14 AM ----------
Correct. If you have a locked bootloader, and took the 4.4.2 update, you might retain root. but you lose the "Write Protection Disable" that MotoWpNoMo gave you.
On 4.4.2, there is no way to disable write protection unless you can unlock your bootloader. If you lose root, on 4.4.2 there is no way to root.
If you flash the 4.4.2 SBF you wont be able to root and disable write protection if you can't unlock your bootloader. And don't try to downgrade to 4.4 or lower.
If you have ATT, the Chinese web site was the only option to unlock your bootloader, however that seems to have ended.
Click to expand...
Click to collapse
Thanks I will try that. Weird thing is I was able to upgrade to 4.4.2 without the stock recovery.
Edit: mfastboot erase cache worked but erase data did not. I got a message saying invalid partition name data, FAILED (remote failure) and then finished with a total time. The problem with simply flashing the stock recovery from a 4.4.2 T-Mobile sbf through fastboot is that I get the security version downgraded message. I'm not sure what else I could try.
Sent from my XT1058 using XDA Premium 4 mobile app
dimasp6 said:
Thanks I will try that. Weird thing is I was able to upgrade to 4.4.2 without the stock recovery.
Click to expand...
Click to collapse
You had to have some sort of stock recovery on there.. The OTA will only install via stock recovery. If you don't have stock recovery on the phone, you'll get stuck in a boot loop of it trying to install.
Now, its possible to modify the OTA file to install from say TWRP or CWM recoveries, but with a locked bootloader, you can't flash them onto the phone, and you can't flash a modified OTA file..
So that is why I'm thinking you have the stock recovery from an older rom than what is on your phone... especially with the "security version downgraded" message. Its very likely you have mismatched file/partition versions on your phone. If that is the case, its a very dangerous place to be, as doing the wrong thing could cause your phone to brick.
Hey guys
My N6 received the OTA update 2 days ago, I live in Australia and my device is rooted. I have downloaded the update then tried to restart and install for the first attempt, and off course it fails because am rooted. I have flashed the stock recovery.img and redownloaded it again, another failure. I have downloaded the OTA for the 3rd time and went to cache folder and took the "update.zip", then tried to flash it using TWRP and it failed. I have also tried the adb sideload and also failed. Below there is the pictures for the sideload procedure. What is puzzling me is that my phone build is "LMY47I" and what I receive is "LMY47Z" , so how can I apply this "update.zip" without wiping my system, I am already running on the stock image but it's rooted. I hope someone can help me out here, thanks everyone.:good::good:
I'm not sure you can be rooted on lollipop to take updates. That could be the problem. Try unrooting.
flash your current versions stock system.img. Lollipop updates don't patch files like the older updates, it does block level patching of the /system so you can't have any changes or the update will fail. On previous versions you could add files to /system and an update would patch the stock /system files and not care you had added other files. Now they patch at the block level so you can't add/delete files, you have to have a 100% untouched /system to take an update.
Download the factory image of what your phone is currently running. Fastboot flash the system.img and then take the OTA. You can then root after updated.
You could also just download the LMY47Z factory image and flash the bootloader, boot.img and system.img and be good to go (root again after). As long as you don't flash the userdata.img or wipe data you retain all your settings/apps/files.
vampire_8_7 said:
Hey guys
My N6 received the OTA update 2 days ago, I live in Australia and my device is rooted. I have downloaded the update then tried to restart and install for the first attempt, and off course it fails because am rooted. I have flashed the stock recovery.img and redownloaded it again, another failure. I have downloaded the OTA for the 3rd time and went to cache folder and took the "update.zip", then tried to flash it using TWRP and it failed. I have also tried the adb sideload and also failed. Below there is the pictures for the sideload procedure. What is puzzling me is that my phone build is "LMY47I" and what I receive is "LMY47Z" , so how can I apply this "update.zip" without wiping my system, I am already running on the stock image but it's rooted. I hope someone can help me out here, thanks everyone.:good::good:
Click to expand...
Click to collapse
You don't.
YOU obtain the full factory system image from https://developers.google.com/android/nexus/images
doitright said:
You don't.
YOU obtain the full factory system image from https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
tcrews said:
flash your current versions stock system.img. Lollipop updates don't patch files like the older updates, it does block level patching of the /system so you can't have any changes or the update will fail. On previous versions you could add files to /system and an update would patch the stock /system files and not care you had added other files. Now they patch at the block level so you can't add/delete files, you have to have a 100% untouched /system to take an update.
Download the factory image of what your phone is currently running. Fastboot flash the system.img and then take the OTA. You can then root after updated.
You could also just download the LMY47Z factory image and flash the bootloader, boot.img and system.img and be good to go (root again after). As long as you don't flash the userdata.img or wipe data you retain all your settings/apps/files.
Click to expand...
Click to collapse
Thanks tcrews
I still have the stock image for the 5.1 om my PC so if I used fastboot to flash the system and radio and bootloader, this won't delete any of my apps or my system??
vampire_8_7 said:
Thanks tcrews
I still have the stock image for the 5.1 om my PC so if I used fastboot to flash the system and radio and bootloader, this won't delete any of my apps or my system??
Click to expand...
Click to collapse
Hey doitright
So I can download the 5.1.1 (For Sprint, USC ONLY) (LMY47Z) even tho its saying US Only, and this was the one I received on the system update!!!
vampire_8_7 said:
Thanks tcrews
I still have the stock image for the 5.1 om my PC so if I used fastboot to flash the system and radio and bootloader, this won't delete any of my apps or my system??
Click to expand...
Click to collapse
To "restore" your system to stock, you just need to flash the system.img and recovery.img to take the OTA. To "update" your system to the next version with factory images you would flash bootloader, restart the bootloader, flash the radio, restart the bootloader then flash boot.img and system.img and then reboot the phone. Re-root after.
All Done
Thanks to everyone, all done now, and special thanks to "tcrews" all sorted out now mate, I used fastboot to flash 5.1 (recovery, bootloader, boot and system) then did the same thing for the 5.1.1. I didn't lose any data or apps all working perfectly fine. I had to "Root" the device after, then flashed the "Xposed Firmware". :good: :good:
Yes, thanks as well! I had this issue when the OTA showed up on my Nexus 6 yesterday. Did what vampire_8_7 indicated above, and everything is working with no loss of data or apps. Thanks everyone!
Hi Guys,
very sorry to bump this thread, but i've been trying for 2 days now to follow your instructions to update to 5.1.1 and its failing.
i have a rooted 5.1 using TeamWin software and custom ROM (LMY47D)
can i get a step by step on how to flash the 5.1.1 OTA ?
i tried to reflash 5.1 stock and it failed as well, no idea if i'm doing something wrong.
thanks in advance.
mar1nasr said:
Hi Guys,
very sorry to bump this thread, but i've been trying for 2 days now to follow your instructions to update to 5.1.1 and its failing.
i have a rooted 5.1 using TeamWin software and custom ROM (LMY47D)
can i get a step by step on how to flash the 5.1.1 OTA ?
i tried to reflash 5.1 stock and it failed as well, no idea if i'm doing something wrong.
thanks in advance.
Click to expand...
Click to collapse
You cannot flash the OTA. You can only flash stock. I also have no idea if you're doing something wrong. Probably though, that is usually the case.
vampire_8_7 said:
Hey guys
My N6 received the OTA update 2 days ago, I live in Australia and my device is rooted. I have downloaded the update then tried to restart and install for the first attempt, and off course it fails because am rooted. I have flashed the stock recovery.img and redownloaded it again, another failure. I have downloaded the OTA for the 3rd time and went to cache folder and took the "update.zip", then tried to flash it using TWRP and it failed. I have also tried the adb sideload and also failed. Below there is the pictures for the sideload procedure. What is puzzling me is that my phone build is "LMY47I" and what I receive is "LMY47Z" , so how can I apply this "update.zip" without wiping my system, I am already running on the stock image but it's rooted. I hope someone can help me out here, thanks everyone.:good::good:
Click to expand...
Click to collapse
- Fastboot erase system
- Fastboot flash system system.img
- Fastboot flash boot boot.img if you have a custom kernel
- Fastboot flash recovery recovery.img if you have a custom recovery
- Fastboot erase cache and then fastboot flash cache cache.img.
Reboot and sideload the OTA and that should do it because you still have have modified system files on your phone.
mar1nasr said:
Hi Guys,
very sorry to bump this thread, but i've been trying for 2 days now to follow your instructions to update to 5.1.1 and its failing.
i have a rooted 5.1 using TeamWin software and custom ROM (LMY47D)
can i get a step by step on how to flash the 5.1.1 OTA ?
i tried to reflash 5.1 stock and it failed as well, no idea if i'm doing something wrong.
thanks in advance.
Click to expand...
Click to collapse
Hey mate
The idea is to go complete stock before you flash any OTA, and this can be achieved by just flashing the "System.img" and the "bootloader.img" file to you device.
DON'T FORGET TO TAKE A FULL BACKUP Note: This warning above is more precaution thing, and this method never wiped any data but its good to have the backup always.
You need to download the official stock image for your device, if you have that's fine keep reading through.
Factory Images
You have to extract the image and get the "system.img" and "bootloader.img"
Copy and Paste the "System.img" and "bootloader.img" files in the fastboot folder.
Open the cmd as admin navigate to the directory where the fastboot resides, then start typing these commands.
fastboot flash bootloader bootloader-XXXX.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
fastboot flash system system.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
Now you have to copy (Boot.img , bootloader.img, system.img and the radio.img) from the OTA image you have and paste it in the fastboot folder, then you will run the previous 2 commands in addition to these 2 commands below.
fastboot flash radio radio-XXX-XXX.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
After performing this you should have 5.1.1 on your device without wiping any of your personal data or apps.
vampire_8_7 said:
...
Click to expand...
Click to collapse
Thanks a million for the step by step. i think my stock 5.1 is the issue. i'll download the factory image and try again now.
cheers,
EDIT: just finished, and it seems my old 5.1 image was crap. i downloaded a new factory image and did what you mentioned above. now running 5.1.1 and all my old data is there. thanks again, appreciate your time.
mar1nasr said:
Thanks a million for the step by step. i think my stock 5.1 is the issue. i'll download the factory image and try again now.
cheers,
EDIT: just finished, and it seems my old 5.1 image was crap. i downloaded a new factory image and did what you mentioned above. now running 5.1.1 and all my old data is there. thanks again, appreciate your time.
Click to expand...
Click to collapse
No Problems bro. Happy to hear that it worked. XDA is always the place where you can get help
another update for those using TWRP.
TWRP recovery 2.8.7.0 cannot decrypt data for recovery mode, and the 5.1.1 udpate comes encrypted. only way to decrypt is to factory wipe if your device is encrypted and the patternlock/pin doesnt work.
TWRP released 2.8.7.1 yesterday that fixes this issue. this saved me from factory wipe and starting from scratch. also no data needed to be wiped.
^^ just in case anyone is running into the same issue.
cheers,
mar1nasr said:
another update for those using TWRP.
TWRP recovery 2.8.7.0 cannot decrypt data for recovery mode, and the 5.1.1 udpate comes encrypted. only way to decrypt is to factory wipe if your device is encrypted and the patternlock/pin doesnt work.
TWRP released 2.8.7.1 yesterday that fixes this issue. this saved me from factory wipe and starting from scratch. also no data needed to be wiped.
^^ just in case anyone is running into the same issue.
cheers,
Click to expand...
Click to collapse
All official updates encrypt.
tcrews said:
To "restore" your system to stock, you just need to flash the system.img and recovery.img to take the OTA. .
Click to expand...
Click to collapse
Hi,
Can I ask for more details how to flash the system.img and recovery.img ? From where to download it and how to flash?
I have rooted Nexus 6 5.1 Verizon
Thanks
ikirilenko said:
Hi,
Can I ask for more details how to flash the system.img and recovery.img ? From where to download it and how to flash?
I have rooted Nexus 6 5.1 Verizon
Thanks
Click to expand...
Click to collapse
I always place these img`s in the /android/sdk/platform-tools/ folder, or extract them and right-click/shift copy to path. Then with cmd in fastboot erase system then flash system system.img and fastboot flash recovery recovery.img. Dowloadlink below in my signature Phantasmagoria and extract the downloaded file until you see the img`s.
gee2012 said:
Then with cmd in fastboot erase system then flash system system.img
Click to expand...
Click to collapse
Out of curiosity, why do you erase system first?
Below are the instructions for using MoFo to flash the AT&T XT1097 to 5.1. The rooted image has a modified build.prop file for free tether. Thanks go to @Slack3r for making the ext4 image and @btdownloads7 for developing the root method.
Since this is a 5.1 image, in order to get it to boot, you need to do the following BEFORE flashing the 5.1 system image:
1) Download the stock 5.1 files and extract them:
https://mega.co.nz/#!bN0BjKbI!zzq5b9wZBo-XFGNkcWtgw7mnXZgC5BWrEC-GZcGLELo
2) Using a root file explorer (like ES Explorer with root enabled), delete everything in /data/dalvik-cache and /cache - YOU MUST DO THIS!
3) Reboot into bootloader mode and run the commands below to flash the following stock 5.1 files for the XT1097:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash recovery recovery.img
Do NOT flash the 5.1 bootloader (motoboot.img) or partition table (gpt.bin) - if you do, you will not be able to use MoFo ever again!!!!!
4) Download the rooted 5.1 image from here, extract it and flash it using MoFo.
https://mega.co.nz/#!ct8DlQxQ!DRMC_TvCcUk7V-FjCBfjsmIoOvw_f0WEdM7gx2waqzM
MD5 of the unzipped file = 146B6A65D925B985857A2F28D4294765
Note that with the XT1096 we had issues if we tried to boot into recovery after initially flashing the 5.1 system image so instead of booting into recovery and wiping cache where you might get weird flashing dead androids, we had to boot into system first.
Obviously if you want Xposed or anything else in the image, someone will need to add it in.
Thank you!
Those of us already rooted with mofo on 5.0.2 need to return to stock 5.0.2 first, correct?
Casyis said:
Thank you!
Those of us already rooted with mofo on 5.0.2 need to return to stock 5.0.2 first, correct?
Click to expand...
Click to collapse
No, the instructions as written in the OP are complete. Like the instructions say, you need to do step 2:
2) Using a root file explorer (like ES Explorer with root enabled), delete everything in /data/dalvik-cache and /data/cache - YOU MUST DO THIS!
Then you can flash the rest of the 5.1 stock files for your device EXCEPT for the bootloader (motoboot.img) and partition table (gpt.bin). Then use MoFo to flash the rooted 5.1 image for your device.
Thanks for clarifying.
I followed the instructions precisely, and the phone won't power up normally. It goes into recovery, and the android icon with exclamation just flashes intermittently. I'm unable to enter options to wipe cache. I can boot into recovery by holding volume down, but normal startup presents this behavior.
Any ideas?
EDIT: I chose BP Tools in boot options, and now the phone at least appears to be booting normally -- currently optimizing apps.
EDIT 2: Okay, so selecting BP tools evidently kicked the phone into booting normally. Looks like everything is just as it should be. Not sure what happened here, but in the end everything is good. Thank you (everyone involved) for getting this done for us!
Casyis said:
Thanks for clarifying.
I followed the instructions precisely, and the phone won't power up normally. It goes into recovery, and the android icon with exclamation just flashes intermittently. I'm unable to enter options to wipe cache. I can boot into recovery by holding volume down, but normal startup presents this behavior.
Any ideas?
EDIT: I chose BP Tools in boot options, and now the phone at least appears to be booting normally -- currently optimizing apps.
EDIT 2: Okay, so selecting BP tools evidently kicked the phone into booting normally. Looks like everything is just as it should be. Not sure what happened here, but in the end everything is good. Thank you (everyone involved) for getting this done for us!
Click to expand...
Click to collapse
This was happening with the XT1096 - you have to get it into system before recovery. You likely hit the wrong button and ended up in recovery instead of system. But once you get it into system, then it is fine.
Thanks again @JulesJam I am downloading now! Do you notice a big performance difference in 5.1? Will be nice to finally kill these memory bugs, so major thanks for that!
The OS is much snappier than 5.0.2. You can tell by going into multitasking and seeing how quickly the tiles load. Very, very nice. No re-draws at all yet since I flashed.
Step 2 implies that I'm already rooted. If I'm not, I assume I need to start with Step 0: Root the device with a 5.0 IMG?
What all would I need to fastboot flash from the stock files to return to stock @JulesJam ? My company just started using AirWatch service to get company email. Problem is airwatch will not work with root. Unfortunatly I will have to lose the ability to use MoFo.. Any help with this is greatly appreciated. Thanks!
bamachevrolet said:
What all would I need to fastboot flash from the stock files to return to stock @JulesJam ? My company just started using AirWatch service to get company email. Problem is airwatch will not work with root. Unfortunatly I will have to lose the ability to use MoFo.. Any help with this is greatly appreciated. Thanks!
Click to expand...
Click to collapse
FYI - like it says in the MoFo Noob Guide - MoFo trips the root checker and it is not able to be undone by flashing back to stock. I don't know how AirWatch works, but if it looks at the qe, then it will see you as rooted even if you aren't.
First thing I would do is flash back to 5.0.2 by flashing the stock 5.0.2 firware (link is in the MoFo Noob Guide)
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1 (repeat this for all of the sparsechunks)
then boot into recovery and wipe the cache. Then boot into system. I believe it will need to downgrade the sensor firmware so allow that to happen.
Then boot into bootloader mode and see if your software status still says modified or not. Then boot into recovery and see what your qe status is. If after that your software status is still modified and your qe is still 1/1, I would do a factory reset and see if that corrects it. It probably won't though.
You will then have to decide whether or not you want to take the 5.1 OTA because your phone is going to want to upgrade. Instead of taking the 5.1 OTA which will upgrade your bootloader and partition table, you have the option of flashing stock 5.1 everything but the motoboot.img and gpt.bin. That would keep you stock 5.1 but still keep your bootloader and partition table on 5.0.2 so that if you wanted to sell the phone later, you could sell it with a copy of MoFo that still works. I put this out there because idk how AirWatch works and if flashing back to stock doesn't change your software status from modified or your qe from 1/1, you may not be able to use AirWatch, idk.
Thank you so much for the detailed explanation @JulesJam . Unfortunately I followed the instructions to the T and didn't run into any issues until I tried to boot into recovery. I got the dead android with a line under saying "no command". So I tried running system first. I got through the boot animation and then a black screen. I let the black screen sit for 30 min and nothing happened. I had the exact issue when installing 5.1, I was able to get it to boot using BT tools. Unfortunately this is not working now. I get the same black screen after the boot animation. I tried multiple times with no luck. I can however still get into fastboot without issues
Any ideas how I can get 5.0.2 to boot? Thanks again!
bamachevrolet said:
I get the same black screen after the boot animation. I tried multiple times with no luck. I can however still get into fastboot without issues
Any ideas how I can get 5.0.2 to boot? Thanks again!
Click to expand...
Click to collapse
For sure you flashed the 5.0.2 logo.bin, boot.img and all of the 5.0.2 system sparsechunks? That sounds like the system partition was not flashed properly.
Perhaps the 5.0.2 system files you have are corrupted? Are you sure the files you have are the stock 5.0.2 files for the AT&T XT1097?
bamachevrolet said:
I got the dead android with a line under saying "no command". !
Click to expand...
Click to collapse
That's OK as long as he is not flashing. When you have the dead android, go ahead and press and hold power then tap volume up to get into recovery and wipe the cache.
Thank you! I was able to get into recovery to wipe cache, but still won't boot.
I downloaded 5.0.2 from your noob guide, and flashed everything in the order of your first replied post. I am going to start over, just in case I missed something.
Don't think it matters but the sparsechunk starts at 0 in the AT&T file. I flashed the sparschunks in order, and in my case 0-8.
bamachevrolet said:
Thank you! I was able to get into recovery to wipe cache, but still won't boot.
Click to expand...
Click to collapse
How long do you let the blank screen sit before you try to get into bootloader mode? I remember sometimes it takes awhile for it to boot.
Also, the dalvik-cache may need to be wiped too. That would require a factory reset to do it so you could boot into recovery and do a factory reset. Unless there is some way to wipe the dalvik-cache from bootloader mode.
bamachevrolet said:
Don't think it matters but the sparsechunk starts at 0 in the AT&T file. I flashed the sparschunks in order, and in my case 0-8.
Click to expand...
Click to collapse
That's fine. I wasn't sure what number they started with.
bamachevrolet said:
I downloaded 5.0.2 from your noob guide, and flashed everything in the order of your first replied post. I am going to start over, just in case I missed something.
Click to expand...
Click to collapse
And after you do, let it sit at the blank screen for awhile to make sure that it isn't an issue of needing time to boot up. If it still won't boot, try the factory reset.
Thank you so much @JulesJam !!! I'm booted to stock 5.0.2 now. I did have to do a factory reset, but not too big of a deal. Unfortunately I forgot to backup my 48 tasker profiles...lol. So glad to have it back up. Thank you again!!!
---------- Post added at 11:06 AM ---------- Previous post was at 11:01 AM ----------
[/COLOR @JulesJam do you have a donation link?
bamachevrolet said:
Thank you so much @JulesJam !!! I'm booted to stock 5.0.2 now. I did have to do a factory reset, but not too big of a deal. Unfortunately I forgot to backup my 48 tasker profiles...lol. So glad to have it back up. Thank you again!!![
Click to expand...
Click to collapse
Glad it worked out, sucks about the tasker profiles though. So it seems like the dalvik-cache has to be wiped, too. I will note that in the future people should delete the contents of the dalvik-cache folder before flashing back to the earlier version of the software.
Does your software status still say modified in bootloader mode? What is your qe when you boot into recovery?
bamachevrolet said:
@JulesJam do you have a donation link?
Click to expand...
Click to collapse
No but thanks for the offer. If you want to donate, please donate to the ASPCA.