[MOD] 2013 Droid Family: Moto X 5.1 Patch

[a-m13]

Moto X 5.1 VZW FXZ seems to be available :

http://www.theandroidsoul.com/download-verizon-moto-x-android-5-1-update-fxz-firmware-84184/

But I didn't succeed in extracting the system.img file.

 

[Johnny Wong]

Moto X 5.1 VZW FXZ seems to be available :

http://www.theandroidsoul.com/download-verizon-moto-x-android-5-1-update-fxz-firmware-84184/

But I didn't succeed in extracting the system.img file.

The system.img is in that zip file from the link you've enclosed. However, when I flashed it, the phone booted up as KitKat 4.4.4 and immediately asked if I wanted to update. I almost took the bait but quickly held the power and volume down to go back into TWRP recovery. That was close, don't know what would have happened if it tried to update the bootloader with the Moto X one. Probably a nice little brick. So, I guess I'll wait for the official Droid Maxx version but it looks like if you want it, you'll have to update to the newest bootloader. I was wondering why I was unable to sideload the Moto X 5.1 Patch, kept giving me an error, it was because I wasn't on Lollipop, LOL.

Edit: Disregard, LOL, I think I grab the wrong files. I updated my Moto X DE to LP 5.1 via OTA the other day, but RSD back to stock before and I think I just flashed those files instead. I've been drinking..... let me try again.. LOL

Edit2: Ok, now I know what you are talking about. Tried to mfastboot system.img and it is saying not enough space. Interesting!

Edit3: Googled it really quick, and using the -P switch it is flashing. So, mfastboot flash system system.img -P

Edit4: Still won't let me sideload the patch successfully and it is bootlooping. I'm going to flash an older modem file because I've tried to flash Moto X LP modem files before and it caused bootloops.

Edit5: Yup, flashing an older Maxx modem file worked (I flashed radio_23255.127.76.00R from VZW_XT1080_4.4.4-SU5.23). I accidentally dirty flashed the VZW LP 5.1 ROM over my Exodus 5.1.1 and it actually booted up. Everything seems to be working, just need to figure out why I couldn't sideload the patch so I can disable the extra buttons, if not, I'll use GravityBox to do it (I think it can...).

Edit6: Got the patch to flash, guess I should have read the instruction which said use the newest Ghost TWRP, I had an older version of the Obake TWRP installed. Dirty flash was a great little accident because all my apps are intact. Smart Lock was broken somewhere along the way with the newer nightly builds of Exodus was fixed by the VZW Moto X 5.1 ROM. Everything seems to run great, will report back if anything changes. Otherwise, case closed, great success!

 

[a-m13]

I'm trying to include directly the patch in the system.img. I have a locked bootloader so that's way harder for me :x
Edit : I managed it in extracting System.img with ImgExtractor. Now the phone is being flashed for 5 hours, it should be done in 4 hours... I miiight work. Damn I hate that locked bootloader !

 

[Johnny Wong]

Been playing around with the Moto X VZW LP 5.1 ROM for the last few days using the patch here. The patch is perfect, however, the ROM has some serious battery draining issue. It seems to stem from the fact that both wifi and cell radios remain active even if wifi is connected. Tried a number of things to rectify that issue but was unsuccessful. I think it may have to be the fact that the radios that came with the ROM can't be flashed (causes bootloop) so I'm forced to use the old KitKat radios. I'll revisit after the official Droid Maxx LP ROM arrives, for now, I'm enjoying the Exodus ROM.


Sent from my iPad using Crapatalk

 

[Rottgrub]

Been playing around with the Moto X VZW LP 5.1 ROM for the last few days using the patch here. The patch is perfect, however, the ROM has some serious battery draining issue. It seems to stem from the fact that both wifi and cell radios remain active even if wifi is connected. Tried a number of things to rectify that issue but was unsuccessful. I think it may have to be the fact that the radios that came with the ROM can't be flashed (causes bootloop) so I'm forced to use the old KitKat radios. I'll revisit after the official Droid Maxx LP ROM arrives, for now, I'm enjoying the Exodus ROM.


Sent from my iPad using Crapatalk

I find it interesting that the Vzw Moto X LP radio is causing you to boot loop. I am using the TMobile LP radio for the Moto X and it boots and runs fine. No weird battery drain, etc. Maybe try that. The T-Mobile ROM should support service under Verizon properly.

Cheers.

 

[Johnny Wong]

I find it interesting that the Vzw Moto X LP radio is causing you to boot loop. I am using the TMobile LP radio for the Moto X and it boots and runs fine. No weird battery drain, etc. Maybe try that. The T-Mobile ROM should support service under Verizon properly.

Cheers.

Not working for me, still bootloop. Probably due to my old bootloader, still on 30.B6.

 

[Rottgrub]

Not working for me, still bootloop. Probably due to my old bootloader, still on 30.B6.

Ahh, yeah. That can cause all sorts of strangeness. Any reason you don't update it to the latest 4.4.4 Droid BL?

Cheers.

 

[Johnny Wong]

Ahh, yeah. That can cause all sorts of strangeness. Any reason you don't update it to the latest 4.4.4 Droid BL?

Cheers.

LOL, really don't have a good reason, will update now. Guess it was a hold over from Sunshine.

Edit1: Updated bootloader to 4.4.4 SU6-7 (30.BA) and flashed VZW Moto X LP 5.1 modem files, no bootloop. Will play around with the ROM for a few days again, see if the battery life improves.

 

[jaydotelloh]

Hey guys, I'm trying to follow along here, but am I am to understand that you guys have succesfully used this patch and the VZW Moto X FXZ's to flash lollipop on the ultra/maxx?

If so, what exactly are the steps? I'm currently on 4.4 (19.5.3) on my VZW Droid MAXX, unlocked bootloader with sunshine. Is it possible for someone to create a stand-alone flashable ROM for this?

Wish I was still using my Galaxy Nexus sometimes. Booted it up the other day and flashed a LP rom with out any issue just to play with it. Moto is making me very said with it's support on the 2013 flashships.

 

[Johnny Wong]

Rottgrub's instructions are pretty spot on. You are flashing everything from the VZW Moto X LP 5.1 ROM minus the gpt and motoboot files. You then flash his patch to turn on the capacitive buttons. I'm currently stuck with the VZW Moto X LP 5.1 ROM because it seemed to have disabled "OK Google" voice detection from a much deeper level than my comprehension because when I reflashed to the Exodus ROM, I lost that OK Google voice detection even though everything is indicating that it is turned on. But specifically for you, you'll want to update to the most current Droid MAXX bootloader or you'll probably experience bootloops like I did after I flashed the modem. So, flash the gpt and motoboot files from 4.4.4 SU6-7 and then manually flash each of the files using mfastboot (minus the gpt and motoboot files from the Moto X ROM) remembering to use the -P switch when flashing system.img.

If you need help using fastboot then follow this guide: http://forum.xda-developers.com/showthread.php?t=2580060 But I didn't use the erase userdata command, think that wipes your storage.

 

[jaydotelloh]

Rottgrub's instructions are pretty spot on. You are flashing everything from the VZW Moto X LP 5.1 ROM minus the gpt and motoboot files. You then flash his patch to turn on the capacitive buttons. I'm currently stuck with the VZW Moto X LP 5.1 ROM because it seemed to have disabled "OK Google" voice detection from a much deeper level than my comprehension because when I reflashed to the Exodus ROM, I lost that OK Google voice detection even though everything is indicating that it is turned on. But specifically for you, you'll want to update to the most current Droid MAXX bootloader or you'll probably experience bootloops like I did after I flashed the modem. So, flash the gpt and motoboot files from 4.4.4 SU6-7 and then manually flash each of the files using mfastboot (minus the gpt and motoboot files from the Moto X ROM) remembering to use the -P switch when flashing system.img.

If you need help using fastboot then follow this guide: http://forum.xda-developers.com/showthread.php?t=2580060 But I didn't use the erase userdata command, think that wipes your storage.

Thanks for the reply! So i'm assuming once i flash the 4.4.4 bootloader I will no longer be able to boot 4.4. I.e., I will have to flash the newer bootloaders and flash the Moto X 5.1 files from the fxz all in one step?

My steps will be:
1. flash motoboot.img from 4.4.4 SU6-7
2. flash gpt.bin from 4.4.4 SU6-7
3. flash boot, logo, system, modem, fsg, and TWRP from 5.1 fxz
4. erase modemst1, modemst2, cache, customize and clogo (i'm omitting the erase userdata command here, if possible).
5. boot directly to recovery
6. choose install from ADB, then run adb sideload droid-motox-5.1_patch.zip
7. reboot

Do these steps seem correct?

If something goes wrong is it still possible to re-flash the 4.4 bootloader and restore my TWRP backup?

 

[Johnny Wong]

Thanks for the reply! So i'm assuming once i flash the 4.4.4 bootloader I will no longer be able to boot 4.4. I.e., I will have to flash the newer bootloaders and flash the Moto X 5.1 files from the fxz all in one step?



My steps will be:

1. flash motoboot.img from 4.4.4 SU6-7

2. flash gpt.bin from 4.4.4 SU6-7

3. flash boot, logo, system, modem, fsg, and TWRP from 5.1 fxz

4. erase modemst1, modemst2, cache, customize and clogo (i'm omitting the erase userdata command here, if possible).

5. boot directly to recovery

6. choose install from ADB, then run adb sideload droid-motox-5.1_patch.zip

7. reboot



Do these steps seem correct?



If something goes wrong is it still possible to re-flash the 4.4 bootloader and restore my TWRP backup?

Your steps are solid. Note that if you put the motor-5.1_patch.zip into your phone, you can flash it directly from TWRP. Also, ensure you use the version of TWRP listed in the OP or the patch may not install. I don't know if it is possible to install 4.4 on the 4.4.4 bootloader. So hopefully 5.1 will be your cup of tea or the best you can do is probably run 4.4.4 SU6-7. Good luck!



Sent from my iPad using Crapatalk

 

[jaydotelloh]

Your steps are solid. Note that if you put the motor-5.1_patch.zip into your phone, you can flash it directly from TWRP. Also, ensure you use the version of TWRP listed in the OP or the patch may not install. I don't know if it is possible to install 4.4 on the 4.4.4 bootloader. So hopefully 5.1 will be your cup of tea or the best you can do is probably run 4.4.4 SU6-7. Good luck!



Sent from my iPad using Crapatalk

Excellent. Performing all my backups now just in case. Thanks for the help!

 

[nukeruss]

What does this mean "remembering to use the -P switch when flashing system.img." I can easily do everything else, I just don't know what the -P switch is.

 

[Johnny Wong]

What does this mean "remembering to use the -P switch when flashing system.img." I can easily do everything else, I just don't know what the -P switch is.

mfastboot flash system system.img -P


Sent from my XT1080 using Tapatalk

 

[jaydotelloh]

Your steps are solid. Note that if you put the motor-5.1_patch.zip into your phone, you can flash it directly from TWRP. Also, ensure you use the version of TWRP listed in the OP or the patch may not install. I don't know if it is possible to install 4.4 on the 4.4.4 bootloader. So hopefully 5.1 will be your cup of tea or the best you can do is probably run 4.4.4 SU6-7. Good luck!



Sent from my iPad using Crapatalk

So, I was able to flash and boot 5.1, but my home button does not work, and the quick action drop down is not present. Any ideas?

Also appears moto display is a little wonky and not showing icons/previews. The lockscreen is only present if using something other than slide to unlock.

hmm, i'm going to try a wipe and see if that clears things up.

edit: did a "factory" reset in TWRP, re-flashed the patch and rebooted. This time it took me through set-up assistant and now the home button and quick action drop down works. Moto display is still funky, not showing the icons of notifications, but the lock screen seems to be working now too. it's getting late, so i'll probably deal with it and try to trouble shoot the moto display issue tomorrow at work .

 

[Johnny Wong]

So, I was able to flash and boot 5.1, but my home button does not work, and the quick action drop down is not present. Any ideas?

Also appears moto display is a little wonky and not showing icons/previews. The lockscreen is only present if using something other than slide to unlock.

hmm, i'm going to try a wipe and see if that clears things up.

Are you talking about the capacitive buttons? And the recent apps menu? (Pictured)

If your capacitive buttons are not active then the patch didn't install properly. The recent apps menu button, the far right, you have to remap the key. The patch file doesn't have that button mapped to that menu. Read the prior post to get the name of that file, I mentioned it in my post and some others mentioned it on page 1 or 2. I can't think of it off the top of my head and I'm watching the Big Brother finale, LOL.

Sent from my XT1080 using Tapatalk

 

[jaydotelloh]

Are you talking about the capacitive buttons? And the recent apps menu? (Pictured)

If your capacitive buttons are not active then the patch didn't install properly. The recent apps menu button, the far right, you have to remap the key. The patch file doesn't have that button mapped to that menu. Read the prior post to get the name of that file, I mentioned it in my post and some others mentioned it on page 1 or 2. I can't think of it off the top of my head and I'm watching the Big Brother finale, LOL.

Sent from my XT1080 using Tapatalk

No, the back button and the recents button were working, but the home was not working. Wiping data fixed it, but the moto display is still messed up. I can touch where the ring would show up, but it doesn't show the preview or the icon. I just updated the app in the play store but no luck.

 

[nukeruss]

Anyone have an updated build.prop for a droid maxx or can tell me what I need to change to make one myself?

 

[nukeruss]

Is there anyway to add these updates manually. For some reason I cannot get my computer to recognize my phone in adb while trying to use adb sideload feature.

Disregard. I finally googled the right questions and found out how to manually update the adb driver while in adb sideload mode.