I have been running the last CM13 official nightly since it was released (Nov 21, 2016) with very few issues, but have had some instability here and there, so I figured I'd throw together a build that contains all of the fixes that came after that. I've been running it for only a day now, so I can't guarantee stability. I'm also not providing any support for this or building any more, I just figured someone else out there might want the same. I also have no plans to do a hiaeuhl version since I can't test it. But if there's enough desire for it, I suppose I could be convinced since it wouldn't take too much time since I still have the VM, though I'll eventually wipe it. This is pretty much pure CM with no cherry picks or modifications except for one. I removed Gello since the certificate is no longer valid and it won't pass build tests. Not to mention no one should use an unsupported browser in general.
For installing, I recommend wiping your system partition, and then installing this as well as the gapps if you so desire. Gapps are not included since this is pure CM13. Wiping data shouldn't be necessary if you were running the Nov 21 nightly of CM13, but any other you might want to wipe data as well.
If you have problems, I probably can't help. Make sure you back up before installing.
https://drive.google.com/open?id=0B0zTcaThkt3UclJzbjJDVW5mcHc
Related
Just tried to update my ROM from temasek v146 to 147, which is basically like updating from CM11 nightly from the 6th of october to the 11th.
I use this as a reference cause it uses the same base with a few additions.
After the update I noticed that google search kept crashing and that I couldn't do a voice search anymore.
I thought that this was the only problem and flashed again with new gapps and even did a clean install with latest slim gapps, but nothing helped.
When I restore my back up with CM based source from the 6th (temasek v146) everything works fine again.
Any ideas what might have caused this?
I have been flashing this afternoon trying to find a ROM that meets the following needs (without going into too much detail), but have not been able to find one that will will work without bootloops.
Basically, I am looking for a CM12 5.0 ROM that supports the AK kernel with working encryption. BlissPop has been badly buggy for me since late February, and I just tried with Temaseks 8.8 (last android 5.0.X version, still supports exposed) twice. First time tried to encrypt after flashing latest AK kernel and UKM zip, but my OPO would just reboot without encrypting. Then I tried flashing on a new clean install after encryrpting, and got a bootloop. I have also tried this on some other ROMs, even some F2FS ones but it didn't work (I don't think encryption works with F2FS).
Any help would be greatly appreciated. I can give more details as necessary. I never post on XDA, but I am by no means a novice to Android or flashing.
Hi everyone, I'm new to all Android development and have tried to build CM 14.1 from source for my Oneplus One.
I ran into some ninja related errors and ended up disabling that in order to get a successful build.
I also had some issues with Gello (v40) causing failures so I edited that out from bacon.mk.
After my fixes I can build the ROM without issues, but when I flashed it to upgrade from 11/22 to 11/23 the CyanogenMod Version listed in my settings shows 11/22 nightly instead of 11/23. There are two log errors when flashing, but I've seen this with basically every 7.0 ROM I have flashed thus far. Otherwise there are no errors when flashing.
I noticed that my ROM for 11/23 is 334.21 MB while the nightly on CM's website is 399.16 MB. I'm not sure why the large discrepancy. I can't imagine Gello would affect it that way
Any help would be appreciated!
Thanks
Edit: So my .zip does have 2 noticeable effects:
1. Browser is installed after flashing
2. Data doesn't work (not sure if this is a bug in 11/23 or my build specifically)
I restored my 11/22 backup after this because I need data.
I recently made a terrible mistake in toying with downgrading back to Marshmallow from Nougat which resulted in the sad hard-bricking of my device. The Nougat bootloader somehow allowed stock Marshmallow to boot and when I decided to accept a security OTA, it must have patched the bootloader and didn't notice that the bootloader was the incorrect version. The second that OTA had applied, my poor MXP had died and it never turned back on. So now I'm here to present a couple of things I feel that I should drop off before I leave this device forever because I had a couple of projects in the works that might be cool for you all to check out.
I have one build of Lineage 15 that I slapped together using HashBang173's kernel and device config and the other sources provided by the Android Oreo WIP page. The last time I was able to get it to boot, it had some serious Bluetooth force closing problems, but there were a ton of changes since I last made a new build. I was never able to see any sort of improvement since I couldn't flash and test the build so if you're looking to try out this build, be my guest. Just flash at your own risk as usual and if you do, you will have to erase userdata before you will be able to wipe anything in TWRP again due to some bug that crashes TWRP.
My second build is for a Nougat build of PureNexus. I was getting really antsy while waiting for a build to come in from HashBang that he mentioned that he'd make a while ago, but since that never ended up coming, (as far as I know) I made one myself. I slapped this build together with the PureNexusProject-Mod sources, I haphazardly put together my own device config, and the build succeeded. However, with the same sad result, I was never able to run this build myself and I have it here abandoned. Again, try it at your own risk because I have put no testing into this at all.
I'm very saddened to leave this device because I really loved everything about it, (minus some of the motorola inconveniences along the way) and I put so much into my little device over the past two years. I guess it's about time to move on anyways :crying:
BUT WAIT, there's more. I have been able to revive my Moto X Pure using this thread over here: https://forum.xda-developers.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860
I'm constantly checking the thread to help people who are running into problems. It was a godsend to me so I'm more than willing to help others
Download
I just installed your Lineage 15 build. Bluetooth keeps crashing, and camera doesn't work. I managed to stop bluetooth crash by deleting it from system files. Thanks for your work and I hope to see more from you.
By all means, read @Neffy27 's FAQ if you are starting out. even as a refresher for stuff you may have forgotten.
-But do think a bit about what you are doing:
-Do not modify your phone unless you are willing to toss it into the trash, as that could well be the result, no matter how well planned.
-Always have a spare on hand. I used my old Moto G3 when my MZP died suddenly. Worked just fine. You know, things really haven't changed all that much since Gingerbread...
-If you are going to be getting the latest OTA stuff by doing a full flash you might want to reflect on just how much, or little, you would gain. We all like to think that if we have the latest security patch we are somehow more safe, though I don't believe I have ever heard of a phone being affected by something just because it is not on the latest patch. I was running my old Moto z play on an aug '18 (if I remember correctly) patch with no problems up until a few weeks ago when it was done in by an expanding battery envelope which cracked the display. Consider, also, that many of the custom roms that are available are not updated at all - it takes a ton of work to try to get/keep a custom ROM current, AND working! Yet you never hear of viruses or the like.
- Be aware that if you modify ANYTHING on your phone, even as little as a new boot logo to cover up the unlocked bootloader message, you will prevent your phone from taking any further OTA updates. Some mods, like adding TWRP, may still allow it to try to download and install an OTA, but when it reboots to finish that install, it will fail since it needs to re-boot through stock recovery to complete. And it will continue offering you that update.
- There is a difference between the partition structure in our phones on 8.x, and those on 9. 9 is not full Treble, only a "partial" Treble, and really only the addition of a second set of partitions which OTA updates can use to update the system - instead of modifying the single partition set, it modifies the other (a or b) set and boots to that on update completion. If it fails it can always boot the other set. Theoretically! Makes it safer than the old way of doing OTA updates, but this may cause problems if you try to flash a 2 partition set phone with a single partition set ROM. I don't believe anyone has run any experiments on this, so YOU, when you flash things without thinking about the situation, may get an unusable phone. I do not know the answer here. If you read these forums which detail other's problems, you may trod a bit more hesitantly!
-The idea here is to have fun, and sometimes to experiment with new things. To a newbie, losing the use of a $200 phone can be a tough life lesson. Let's help them out by helping them to be cautious!
Agreed. I've been running stock with January 2018 patch, TWRP installed and Magisk for root and successful safety net bypass.
I'm looking to see if running Lineage will help streamline any update processes. It looks like they have their own recovery too.
Maintaining root has become a pain in my ass the past few years.
Sent from my moto x4 using Tapatalk
SR3TLAW said:
Agreed. I've been running stock with January 2018 patch, TWRP installed and Magisk for root and successful safety net bypass.
I'm looking to see if running Lineage will help streamline any update processes. It looks like they have their own recovery too.
Maintaining root has become a pain in my ass the past few years.
Sent from my moto x4 using Tapatalk
Click to expand...
Click to collapse
I would be careful about lineage as folks don't seem to be able to get back to stock from it.
I agree about maintaining root. I will likely just stay on stock with this one.