[MOD] 2013 Droid Ultra Family Ghost Patch (obsolete)

kitcostantino

Senior Member
Mar 21, 2011
1,695
1,000
143
Mayberry
This patch saves my Maxx

Edited again....this is what may be useful to me personally or anyone else with a Droid Maxx.
In this folder are the lib, etc, and user folders from /system along with build.prop
https://app.box.com/s/95iniovmmurlmurrftps maybe this is relavent here. Maybe not. ;)

I cannot express how grateful i am for this patch. i have been using the .8 patch on my XT1080M on AICP ghost nightlies with zero issues aside from the standard cm12 bugs. (have to toggle speakerphone on, then off for audio to work on outgoing calls. the only issue i have is my device not being recognized by websites i have used due to the variance in DROID MAXX and droid maxx or XT1080M versus xt1080m. i use flashify to swap recovery back to twrp, and really, it would be awesome to not have to fart with philz, but it becomes tedious to change updater-script on every nightly, hence this zip at least keeps me in the loop of cm12 progress. it is sad that my phone, which is, in fact, a developer edition from Motorola, has little to no support. thank you OP for keeping this up to date for now. I am going to boot back into twrp, restore my virgin stock, and upload the original build.prop to my box account. i will link it here in a few. hope that helps. If you need any other files from the stock 4.4.4 volte update, lmk.
Build.prop:
https://app.box.com/s/vio3kc47rt24v8bu81rf
 
Last edited:

Skrilax_CZ

Inactive Recognized Developer
Dec 20, 2009
1,240
2,397
0
All you have to do to see cm12 on any msm8960dt device (Droid ultra, Droid MAXX, Droid mini) is flash Philz recovery (In OP aka Original Post), flash cm12, flash gapps (I use 12/18 minimal, then add everything else I want) then flash the zip file in the OP. I can't confirm .12 on the Maxx(though I am sure it works as well or better than. 8), but I can confirm .8 with zero issues. You can grab the Flashify app from Play Store and flash like 3 times a day for free. I bought the paid version, but most likely ya wont use it more than twice in a day

Grab a ROM, grab the file, swap recovery, and boom, there ya are on CM12
First boot takes F-O-R-E-V-E-R but its worth it.
http://dwnld.aicp-rom.com/?device=ghost.
Or
http://download.cyanogenmod.com/?device=ghost&type=nightly

AICP is my preference so far. Can't wait to see a theme engine on either, though.
Or you can use the build directly for obake I posted a few posts above or wait some tome for obake nightlies.

I would like to see Cm12 as well. do you still need build. prop from an ultra? i have tried to download sources for cm12 but it fails. not really sure what the deal is.
At the moment, download sources for ghost via cm. Afterwards just "cd device/motorola", "git clone https://github.com/razrqcom-dev-team/android_device_motorola_obake", "mv android_device_motorola_obake obake" and then make a build with "brunch obake".
 
Last edited:

corebore

Senior Member
Jun 4, 2012
90
3
0
The only reason I'm not updating yet is that xposed is not compatible with art. I use the xposed additions module because I can't get used to having recents as my menu button and long press for home as my recents. If that can be changed in build.prop or something I would totally go for it.
 

Rottgrub

Senior Member
Apr 28, 2009
493
105
73
Or you can use the build directly for obake I posted a few posts above or wait some tome for obake nightlies.

At the moment, download sources for ghost via cm. Afterwards just "cd device/motorola", "git clone https://github.com/razrqcom-dev-team/android_device_motorola_obake", "mv android_device_motorola_obake obake" and then make a build with "brunch obake".
Just found your post with "cm-12-20150109-UNOFFICIAL-obake.zip" build in the CM11 Official thread. Trying it now.

Updates:
1: Install blows out on asserts. Neither TWRP (ghost) or Philz (ghost) provide the needed properties. (need to test Philz msm_8960dt)
2: Stuck on boot animation for 15m and counting. Seems to be boot looping.
 
Last edited:

Rottgrub

Senior Member
Apr 28, 2009
493
105
73
Oh, it's in the other thread, my bad. I actually use CM recovery in 5.0, (attached http://forum.xda-developers.com/showpost.php?p=58108872&postcount=114) because:
1) Moto X recoveries have device name "ghost", causing obake to bail
2) There is a patch req'd for 5.0 otherwise you'll get bootloop, and eventually FCs on gapps

Also, you have Droid Mini, right?
Droid Mini, yep. That would explain things about the recovery. Tried the one you linked, but ran into a little problem. Looks like the recovery partition is limited to 10485760 bytes on the Mini.
Code:
>mfastboot flash recovery recovery.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'recovery' (11416 KB)...
OKAY [  0.974s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
FAILED (remote failure)
finished. total time: 1.255s
 
Last edited:

Skrilax_CZ

Inactive Recognized Developer
Dec 20, 2009
1,240
2,397
0
Droid Mini, yep. That would explain things about the recovery. Tried the one you linked, but ran into a little problem. Looks like the recovery partition is limited to 10485760 bytes on the Mini.
Code:
>mfastboot flash recovery recovery.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'recovery' (11416 KB)...
OKAY [  0.974s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
FAILED (remote failure)
finished. total time: 1.255s
This is why you shouldn't do this late night :D. I uploaded the wrong recovery (for my LG Watch R), fixed, and it's under 10 MB (Droid Maxx has also 10 MB limit, it's right under it). Sorry.
 

Rottgrub

Senior Member
Apr 28, 2009
493
105
73
This is why you shouldn't do this late night :D. I uploaded the wrong recovery (for my LG Watch R), fixed, and it's under 10 MB (Droid Maxx has also 10 MB limit, it's right under it). Sorry.
Hehe, no problem. I flashed the correct recovery, and then flashed the 20140109 build you'd posted. Same boot loop, unfortunately. Do you happen to have any other build dates I could try? Might be something with this particular build.

Update: Just saw the bootloop post. I'll jump that hurdle in just a bit and let you know.
 
Last edited:

Rottgrub

Senior Member
Apr 28, 2009
493
105
73

Lordomn

Senior Member
Sep 15, 2012
742
323
0
somewhere in arkansas
Or


At the moment, download sources for ghost via cm. Afterwards just "cd device/motorola", "git clone https://github.com/razrqcom-dev-team/android_device_motorola_obake", "mv android_device_motorola_obake obake" and then make a build with "brunch obake".
@Skrilax_CZ I was wondering what vendor tree you were using to build? or are you just extracting from your own device? I have downloaded the sources for cm12 plus the ones needed for obake. i was just curious about the vendor sources if i should just extract from my device.

---------- Post added at 03:23 PM ---------- Previous post was at 03:11 PM ----------

@Skrilax_CZ I was wondering what vendor tree you were using to build? or are you just extracting from your own device? I have downloaded the sources for cm12 plus the ones needed for obake. i was just curious about the vendor sources if i should just extract from my device.
EDIT: nevermind i found it on github after i changed branches. thanks