So, anybody tried it up on obake? We've already did 1 part of the changes in CM, so it's now ready for adding obake back.
Or you can use the build directly for obake I posted a few posts above or wait some tome for obake nightlies.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.
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".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.
Just found your post with "cm-12-20150109-UNOFFICIAL-obake.zip" build in the CM11 Official thread. Trying it now.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".
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.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?
>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 nightDroid 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
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.This is why you shouldn't do this late night. 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.
Posted update in CM11 Droid thread.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.
@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.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".
EDIT: nevermind i found it on github after i changed branches. thanks@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.