[MOD] 2013 Droid Family: Moto X 5.1 Patch

[jaydotelloh]

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.

For anyone else wondering, you can flash the patch normally in TWRP, it just has to be on the storage. This presents a bit of an issue if you did the erase userdata command though since it formats the /data/ partition. You wont be able to mount /data/ in TWRP after doing the erase userdata either so you just have to let it boot up normally (it booted just fine for me without applying the patch and has on-screen buttons for navigation). It will re-build the partitions and then you can drag and drop the patch to your storage, reboot to TWRP and flash it.

So after 1-1/2 days of running this, i'm fairly happy except for Moto Display not working. I'm currently using acdisplay as a temporary solution, but would love to know if anyone else has seen this issue. Hopefully when the "official" update for the Droids comes out I can re-flash that and get moto display working again.

Oh, also, if anyone is wondering, the xposed alpha build is working fine for me as well.

 

[jaydotelloh]

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.

Curious if you got this working. Everything is working on mine except Active display, is this functional for you?

 

[Rottgrub]

Curious if you got this working. Everything is working on mine except Active display, is this functional for you?

So, there are two different active display models. Motorola's version doesn't work, but the one built into LP does. Disable active display from the Moto app, and turn on:

System Settings > Display > Ambient Display

Works well.

 

[jaydotelloh]

So, there are two different active display models. Motorola's version doesn't work, but the one built into LP does. Disable active display from the Moto app, and turn on:

System Settings > Display > Ambient Display

Works well.

Thanks for the reply!

Yea, I knew there was ambient display also, but I was wondering if Moto's Active display was working. As long as it's not just me, then I can wait patientlly until the official files are made available for the Maxx/Ultra.

 

[jdrogers84]

Am I wrong in assuming this needs an unlocked bootloader? Am I stuck on 4.4.4?

 

[Rottgrub]

Am I wrong in assuming this needs an unlocked bootloader? Am I stuck on 4.4.4?

Knowledge Requirements:
- Read the first post for comprehension before posting.

Other Requirements: (Do a search before you ask...)
- Droid Ultra series device with unlocked bootloader.

 

[MArtyChubbs]

Looks like this hack is the closest thing to the 5.1 update our ultras will never get. Thank you dev and shame on you Verizon...

Sent from my XT1080 using Tapatalk

 

[a-m13]

Could someone who has some spare time (and a good connection) provide the system.img file once 5.1 with patch is installed ? If I remember its size is approximately 2GB. I would like to do some tests on locked bootloader

 

[kude87]

What would it entail to make this (if possible) into a flashable zip?

 

[mrroks]

What is it?:
A small driver patch to better support running the new Moto X 5.1 stock ROMs on the 2013 Droid Ultra series phones (Mini, Ultra, Maxx). Now also patches the libstagefright vulnerability in these stock ROMs.


What's been tested?:
- Droid Mini, w/ T-Mobile: LTE, 4g, 3g, 2g, calling
- Wireless 2.4ghz, Bluetooth audio and calling.
- Video acceleration, audio, haptic feedback, camera.
- Deep sleep, power management, and wireless charging.
- Normal day to day usage for ~2 weeks now. No crashes, no problems.


YOU ACCEPT RESPONSIBILITY FOR ANY AND ALL REPERCUSSIONS BY CHOOSING TO USE THIS INFORMATION
- If you have ANY doubts about the risks, definitely don't use this.

Knowledge Requirements:
- Read the first post for comprehension before posting.
- Read and understand the instructions before trying to follow them.
- Know how to use mfastboot to flash an FXZ.
Other Requirements: (Do a search before you ask...)
- Droid Ultra series device with unlocked bootloader.
- Stock Moto X 5.1 FXZ (I used xt1053 version).
- Current TWRP for Ghost (I used 2.8.7.0).


Instructions:

1: Unzip the Moto X FXZ to a directory on your computer.

2: *** DELETE "motoboot.img", and "gpt.bin"! DO NOT FLASH THEM!!! ***
THESE TWO FILES CAN PERMANENTLY DAMAGE OR BRICK YOUR DROID!!! DELETE THEM!!!

3: Reboot into bootloader for fastboot.
4: mfastboot flash your boot, logo, system, modem, fsg, and TWRP recovery
5: mfastboot erase modemst1, modemst2, userdata, cache, customize, and clogo
6: Use volume controls to boot directly to recovery. If you boot to OS by accident, you'll need to reflash recovery.
7: Let TWRP make changes to your system image to prevent recovery being overwritten.
8: In TWRP select "Install from adb", and then run "adb sideload Droid-MotoX-5.1_Patch.zip" from your computer.
9: Reboot device, and let TWRP install SuperSU.​

Observations:
- First boot can take a long, long, time, and may hang. If it's still booting after 10-15 minutes, give it a reboot (PWR & VOL-).
- Your device will think it's a Moto X after reboot. This is normal.
- I highly recommend disabling the Motorola Update Service. The patch doesn't do this for you.
- No idea if this works with other Moto X stock ROM versions.

Notes:
- This is done in my free time, and isn't something I intend to support.
- Don't PM me directly for help! Ask in the thread.
- If you don't have enough post count to post in DEV, you probably shouldn't use this patch.

Bugs:
- None that I've seen so far.

Changelog:
- Initial release
- Added libstagefright patched libs from this thread.

** Please search the forum or Google your question before posting. Thanks! **

idk why im having bootloop .. i tried flashing stock ultra firmware with rsd still same ? just haiving the bootlogo help ? :'(

 

[corebore]

Okay, just wondering just to verify. Does this work on the Verizon 2013 models?

Sent from my DROID Mini using Tapatalk

 

[kitcostantino]

Well, after reading this https://plus.google.com/+DavidSchuster/posts/Gu6pVe4ukXj
I feel like its time to take the plunge on this patch and try to salvage some usability from this phone.
@corebonethe phrase [MOD] 2013 Droid Family: encompasses the 3 from 2013... Droid Mini, Droid Ultra, and Droid Maxx. You (obviously) must have an unlocked bootloader and flash a Moto X version that will function with your carrier. Personally, I am pretty happy with Dirty Unicorns last LP build. However, I think I am going to do this mod and look for Moto X Verizon ROMs. (If that works... Maybe I'm misunderstanding...) Thank you to all who have made this phone live this long.

Edit: has anyone who uses Verizon used this? http://forum.xda-developers.com/devdb/project/dl/?id=14435

 

[bigv5150]

Well, after reading this https://plus.google.com/+DavidSchuster/posts/Gu6pVe4ukXj
I feel like its time to take the plunge on this patch and try to salvage some usability from this phone.
@corebonethe phrase [MOD] 2013 Droid Family: encompasses the 3 from 2013... Droid Mini, Droid Ultra, and Droid Maxx. You (obviously) must have an unlocked bootloader and flash a Moto X version that will function with your carrier. Personally, I am pretty happy with Dirty Unicorns last LP build. However, I think I am going to do this mod and look for Moto X Verizon ROMs. (If that works... Maybe I'm misunderstanding...) Thank you to all who have made this phone live this long.

Edit: has anyone who uses Verizon used this? http://forum.xda-developers.com/devdb/project/dl/?id=14435

I did this today for ****s and giggles I have a dt2 now but wanted a fully functioning 5.1 so I updated. Everything works as stock. I put in my sim card and it gets full bars. I used the Verizon FXZ here http://firmware.center/firmware/Motorola/Moto%20X%20%281st%20gen-2013%29/Stock/XT1060%20Verizon/ and followed the directions.

Sent from my Motorola Droid Turbo 2 using XDA Labs

 

[kitcostantino]

I did this today for ****s and giggles I have a dt2 now but wanted a fully functioning 5.1 so I updated. Everything works as stock. I put in my sim card and it gets full bars. I used the Verizon FXZ here http://firmware.center/firmware/Motorola/Moto X (1st gen-2013)/Stock/XT1060 Verizon/ and followed the directions.

Sent from my Motorola Droid Turbo 2 using XDA Labs

Lol. I'm on a s***** and giggles day for phones. Updating my Droid Bionic to MM on Res Remix. Charging the HTC Rezound. Gearing up to flash my droid Maxx, though I am pretty happy with Dirty Unicorns. Gotta break in my win 10/Linux mint laptop with some mfastboot. The Maxx is still a great device. I wish moto would offer a trade in for a MXPE for the Maxx. Highly unlikely, but hopefully they just unlock the bootloaders.

EDIT: I procrastinated, but finally am doing this.

 

[corebore]

Lol. I'm on a s***** and giggles day for phones. Updating my Droid Bionic to MM on Res Remix. Charging the HTC Rezound. Gearing up to flash my droid Maxx, though I am pretty happy with Dirty Unicorns. Gotta break in my win 10/Linux mint laptop with some mfastboot. The Maxx is still a great device. I wish moto would offer a trade in for a MXPE for the Maxx. Highly unlikely, but hopefully they just unlock the bootloaders.

I don't know, after a few years without a notification light it kind of is nice now.

Sent from my XT1060 using Tapatalk

 

[Rottgrub]

idk why im having bootloop .. i tried flashing stock ultra firmware with rsd still same ? just haiving the bootlogo help ? :'(

5: mfastboot erase modemst1, modemst2, userdata, cache, customize, and clogo

First boot can take 5-10 minutes.

 

[corebore]

5: mfastboot erase modemst1, modemst2, userdata, cache, customize, and clogo

First boot can take 5-10 minutes.

I had to get the few files from the stock fxz that you said we should remove because it wouldn't stop bootlooping during the warning screen.

Edit: It took a lot of guessing. Also, you should quote the mfastboot commands so people don't miss it somehow lol.

Sent from my XT1060 using Tapatalk

 

[mrroks]

5: mfastboot erase modemst1, modemst2, userdata, cache, customize, and clogo

First boot can take 5-10 minutes.

thanks but im over with it .. flashed the last kitkat firmware and everything was normal and yeah bootloader is still unlocked

 

[kitcostantino]

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!

idk why it was such a PITA, but with your help @johnnywong , i finally got this to work. Thank you, seriously.

 

[Johnny Wong]

idk why it was such a PITA, but with your help @johnnywong , i finally got this to work. Thank you, seriously.

Glad it worked for you!

Sent from my DROID MAXX using Tapatalk