Database Info

[ROM][UnOfficial]CyanogenMod 13 Semi-Nightlies for the Verizon Galaxy S3 (d2vzw)

CyanogenMod and D2VZW: Marshmallow Love!
To Make this easy, I am going to copy a bit of the common sense information Master Cylinder put up for the release of Lollipop, same basics apply here!
Huge thanks to Invisiblek for making these builds for us!
Thanks to Master Cylinder for all the super useful information!
De-unified Marshmallow builds for the Galaxy S3 line. This is for the Verizon variant (SCH-I535) only
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 which is designed to increase performance and reliability over stock Android for your device.
Notes:
Please Use Firmware: VRBMF1
and
Modem/Baseband Version: NE1 (Also, see "Notes - Possible Bugs" section below)
(EDIT: The following statement might not be true. It happened to one user. Unsure about circumstances...)If you have recently downgraded firmware from 4.3 to 4.1.2, DO NOT flash the MF1 firmware. You'll brick your device!
If you know you never took the 4.3 OTA, then you can flash the firmware and modem to your hearts content.
CWM Recovery addicts: Please seriously consider giving up CWM and come on board with what works for sure with 5.1.x and up, TWRP. Problems have been coming up with CWM users so if you have one, that's were to start. Hopefully there's a 12-step program somewhere for y'all
Google apps addon:
Open GApps opengapps.org They have many options for you to choose from based on your needs. Updated daily.
>>>WARNING!!<<< The first time one installs Open GApps, you have to do it with a ROM update (or reinstall current ROM) AND manually wipe the system partition first. Then install the ROM and the GApps normally, then wipe Dalvik and Cache. After that, you can flash them anytime. (More info on Website.) ALSO, for now, don't install Webview as it might not work. There is an "Android System Webview" in the Play Store that will work.
I personally don't use GApps on my Daily Driver, I have a second S3 on Wi-Fi only that I put GApps on, and I use it to basically keep all my apk files up to date. When they get updated, I move the updated apk to my main phone!
I went to opengapps.org, went to Platform: ARM, then to Android: 6.0, and then to Variant: pico. Invisiblek made sure he warned me to do a clean install of the ROM, then Immediately flash the GApps package, then Wipe Dalvik and Cache, then boot. He said NOT to try to install ROM, then add GApps later otherwise bad things can happen! Obviously pick the flavor of GApps that suits your needs!
This page will be a work in progress, so please don't yell if something is missing. I just got the OK to share this with others and wanted to get it out there for you to enjoy. I have been playing with it for the last 24 hours and it is ROCK SOLID in my opinion. I haven't found any issues yet! Daily Driver for me for certain. If you have issues, please post them for discussion below!
Firmware and Modem thanks to Invisiblek
Download - MF1 firmware with NE1 modem Combo: http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip (md5sum: 7a49bb13c1160f4d4a89488127684b5b)
And without further delay, the link you all want! : http://www.invisiblek.org/roms/cm-13.0/d2vzw/
BUGS:
Need to possibly load a different File Explorer to access SD Card (DoctorImpossible)
Access to camera is not functioning correctly (DoctorImpossible) *EDIT 11-23 build camera works, camcorder fix coming next build!
Outgoing text messages show "not sent", but actually send fine. (Stealth111)
Incoming phone calls do not show caller information (Stealth111)
**When you get your ROM installed and up and running, please be kind and put a small post with information about your install so we can get as much info gathered as possible. (ROM build you installed, Recovery type/version, Clean install, or Dirty (and if dirty, over what version did you flash), what GApps package you installed(exact one please) as well as when you installed it (if on same initial install as ROM, or differently). And lastly maybe the firmware/modem combo you are running. Thanks!
***IMPORTANT INFORMATION*** If you are going to flash to cm-13.0-20151121-UNOFFICIAL-d2vzw or later build, there have been some database changes. InvisibleK has provided a flashable zip file to accommodate nuking your old telephony and settings databases. Nandroid or backup files as needed if you want, as I seem to remember doing this with CM before, and clearing the database wiped texts and call logs I believe. This only needs to be done 1 time, the first time you flash any build from 11-21 on. After you have done this once, you are good to go moving forward, you will be upgraded to the new databases. If you do not flash the "Nuke_It" zip file, you will get phone FC's and a "No SIM Card" error message. So whether upgrading, dirty flashing or whatever, reboot into recovery, flash the ROM, and BEFORE you boot, flash the following zip!
Nuke IT Database Wiper
Profit!
Enjoy!
Stealth111

For Future Use
First

For Future Use
Second

Stealth111 said:
Second
Click to expand...
Click to collapse
First!! To download from here ... I see you've got an OpenGApps link, but it says a patch has to be used. I think I saw it mentioned on a thread somewhere (when I was tracking you to see where you got the build, which didn't lead me anywhere, but then I remembered our old friend invisiblek!)
And thanks a million for starting this thread!!!:good::good::good:

Master Cylinder said:
First!! To download from here ... I see you've got an OpenGApps link, but it says a patch has to be used. I think I saw it mentioned on a thread somewhere (when I was tracking you to see where you got the build, which didn't lead me anywhere, but then I remembered our old friend invisiblek!)
And thanks a million for starting this thread!!!:good::good::good:
Click to expand...
Click to collapse
I personally don't use GApps on my Daily driver, I have a second S3 on Wi-Fi only that I put GApps on, and I use it to basically keep all my apk files up to date. When they get updated, I move the updated apk to my main phone!
I went to opengapps.org, went to Platform: ARM, then to Android: 6.0, and then to Variant: pico. Invisiblek made sure he warned me to do a clean install of the ROM, then Immediately flash the GApps package, then Wipe Caches, then boot. He said NOT to try to install ROM, then add GApps later otherwise bad things can happen! Obviously pick the flavor of GApps that suits your needs! I'll add this bit up-top as well! I don't know anything about a patch though..
Stealth111

Stealth111 said:
I personally don't use GApps on my Daily driver, I have a second S3 on Wi-Fi only that I put GApps on, and I use it to basically keep all my apk files up to date. When they get updated, I move the updated apk to my main phone!
I went to opengapps.org, went to Platform: ARM, then to Android: 6.0, and then to Variant: pico. Invisiblek made sure he warned me to do a clean install of the ROM, then Immediately flash the GApps package, then Wipe Caches, then boot. He said NOT to try to install ROM, then add GApps later otherwise bad things can happen! Obviously pick the flavor of GApps that suits your needs! I'll add this bit up-top as well! I don't know anything about a patch though..
Stealth111
Click to expand...
Click to collapse
Thanks. I also misread the notation at OpenGApps, which said that need a "ROM" with the patch to allow Google services permissions. Also, there are some posts I've found about fixing permissions after boot then reinstalling GApps, but I won't post that here in case it misleads. I'll be the guinea pig as I've dloaded and backed up and ready to jump out the window!

Stealth111 said:
CyanogenMod and D2VZW: Marshmallow Love!
Firmware and Modem thanks to Invisiblek
Download - MF1 firmware with NE1 modem Combo: http://www.invisiblek.org/firmware/d..._NE1_modem.zip (md5sum: 7a49bb13c1160f4d4a89488127684b5b)
And without further delay, the link you all want! : http://www.invisiblek.org/roms/cm-13.0/d2vzw/
Enjoy!
Stealth111
Click to expand...
Click to collapse
Hello and thank you for providing us, S3 users, with the chance to try the long awaited Marshmallow ROM.
I downloaded the ROM a minute ago, but unable to download the MF1 firmware and NE1 modem, via link. I keep getting:
Error 404: Server be all like
Am I doing something wrong? If not... What next?

I just finished booting it. It seems pretty nice, and I only noticed a few things. The boot time was around half an hour as usual with lollipop. I did notice that there wasn't any camera app preloaded and I couldn't access my sd card through the file explorer (I chose not to format my sd card as internal and I gave the file explorer root access).

Ghost Protocol said:
Hello and thank you for providing us, S3 users, with the chance to try the long awaited Marshmallow ROM.
I downloaded the ROM a minute ago, but unable to download the MF1 firmware and NE1 modem, via link. I keep getting:
Error 404: Server be all like
Am I doing something wrong? If not... What next?
Click to expand...
Click to collapse
Yes, @Stealth111 you've copied the text from the CM12 OP but that won't work for links EDIT: that are truncated in a post. You have to manually copy the link, ex: right click on the link (if you're using a computer,) copy link location of whatever, and insert it manually.
Here is the working link: http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip
On another note: I couldn't get my install to function past the first couple of screen in setup. com.android.phone fc avalanche stops all progress. Wiped and installed 3 times with no success. Running NE1 modem (after flashing and booting with ML1 the first time.)

Doctorimpossible said:
It seems pretty nice, and I only noticed a few things. . I did notice that there wasn't any camera app preloaded and I couldn't access my sd card through the file explorer (I chose not to format my sd card as internal and I gave the file explorer root access).
Click to expand...
Click to collapse
I also can't access the camera even after installing a new camera app. A new file explorer took care of my sd card issues however.

@ Master Cylinder, thanks for the heads up on the link, I have fixed it in the OP. For ****s and giggles, trying wiping and installing just the ROM, and then wipe Dalvic and Cache and see how it goes. Maybe a GApps issue. Also, goes without saying, make sure the MD5 from the download matches to verify you got a good DL..
@Doctorimpossible, glad you were able to sort out the access issue. I install ES File Explorer right away, so I didn't notice the issue. Good catch. These are the types of thing we need to sort out as quickly as possible to get this thing rolling! I will say that my initial boot only took about 5 minutes, but again, I did not load ANY GApps.

Master Cylinder said:
Yes, @Stealth111 you've copied the text from the CM12 OP but that won't work for links EDIT: that are truncated in a post. You have to manually copy the link, ex: right click on the link (if you're using a computer,) copy link location of whatever, and insert it manually.
Here is the working link: http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip
On another note: I couldn't get my install to function past the first couple of screen in setup. com.android.phone fc avalanche stops all progress. Wiped and installed 3 times with no success. Running NE1 modem (after flashing and booting with ML1 the first time.)
Click to expand...
Click to collapse
So is this a hit or miss when flashing or not?

Ghost Protocol said:
So is this a hit or miss when flashing or not?
Click to expand...
Click to collapse
I have installed it on 4 devices myself with no issues. They were all with TWRP 2.8.7.0, clean installs, data wiped, ROM only install, and wiped caches before first boot. DoctorImpossible also has installed it and is up and running. I don't know what GApps he is running (if any). I will add to the OP asking people to put what they did/used for successful installs.

Stealth111 said:
@ Master Cylinder, thanks for the heads up on the link, I have fixed it in the OP. For ****s and giggles, trying wiping and installing just the ROM, and then wipe Dalvic and Cache and see how it goes. Maybe a GApps issue. Also, goes without saying, make sure the MD5 from the download matches to verify you got a good DL..
@Doctorimpossible, glad you were able to sort out the access issue. I install ES File Explorer right away, so I didn't notice the issue. Good catch. These are the types of thing we need to sort out as quickly as possible to get this thing rolling! I will say that my initial boot only took about 5 minutes, but again, I did not load ANY GApps.
Click to expand...
Click to collapse
I tried that just now for the 4th crapout, and there's no MD5 that I can see, but I'm gonna dload the ROM again to my lap and push it over and try again.
Ghost Protocol said:
So is this a hit or miss when flashing or not?
Click to expand...
Click to collapse
Of course! It's the first unofficial build for us.

Stealth111 said:
I have installed it on 4 devices myself with no issues. They were all with TWRP 2.8.7.0, clean installs, data wiped, ROM only install, and wiped caches before first boot. DoctorImpossible also has installed it and is up and running. I don't know what GApps he is running (if any). I will add to the OP asking people to put what they did/used for successful installs.
Click to expand...
Click to collapse
I used the GApps linked in the description with the stock option and flashed using TWRP 2.8.7.0. I rebooted from 5.1.1, factory reset, manually wiped system, flashed the rom, then flashed GApps, wiped the cache, rebooted, rebooted again and flashed xposed (which works by the way!)

Master Cylinder said:
I tried that just now for the 4th crapout, and there's no MD5 that I can see, but I'm gonna dload the ROM again to my lap and push it over and try again.
Of course! It's the first unofficial build for us.
Click to expand...
Click to collapse
Here is the MD5 from my file if it helps!
192BD2F6A83BCA791E0AFE9570134058

Doctorimpossible said:
I used the GApps linked in the description with the stock option and flashed using TWRP 2.8.7.0. I rebooted from 5.1.1, factory reset, manually wiped system, flashed the rom, then flashed GApps, wiped the cache, rebooted, rebooted again and flashed xposed (which works by the way!)
Click to expand...
Click to collapse
Yuppers! Exposed for Android 6
Thanks for the report!
Fingers crossed for Master Cylinder!!

Stealth111 said:
If you have recently downgraded firmware from 4.3 to 4.1.2, DO NOT flash the MF1 firmware. You'll brick your device!
Click to expand...
Click to collapse
how do i know if i have the right one ? it was a while since i rooted and flashed my phone.
thanks.
Sent from my SCH-I535

Jaws4God said:
how do i know if i have the right one ? it was a while since i rooted and flashed my phone.
thanks.
Sent from my SCH-I535
Click to expand...
Click to collapse
There's no way to tell, but you're probably okay. How did you flash your ROM? This is to warn people that the recent post for a procedure to "Downgrade" from their locked bootloader 4.3 OTA that all of us avoided because we were already rooted, etc. This new method has only been around since this summer, so if you have been rooted in the years category, you're probably okay.
Besides, it may even not be a problem if one had done that new method.

Master Cylinder said:
There's no way to tell, but you're probably okay. How did you flash your ROM? This is to warn people that the recent post for a procedure to "Downgrade" from their locked bootloader 4.3 OTA that all of us avoided because we were already rooted, etc. This new method has only been around since this summer, so if you have been rooted in the years category, you're probably okay.
Besides, it may even not be a problem if one had done that new method.
Click to expand...
Click to collapse
all i rememeber was downgrading from h2 to h1 to get root access.. then flashed CM12.1 on top of that ..
Sent from my SCH-I535

[ROM][XC][N][7.1][WEEKLY]OmniROM

XC/KUGO/F5321 OmniROM BUILDS
NOUGAT 7.1
DOWNLOAD WEEKLY
CURRENT ISSUES ON OFFICIAL:
1. Encryption is broken
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm8952/tree/android-7.1
BUGS REPORT
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
CHANGELOG:
https://changelog.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
[/CENTER]
XDA:DevDB Information
[ROM][XC][N][7.1][WEEKLY]OmniROM, ROM for the Sony Xperia X Compact
Contributors
oshmoun
Source Code: https://github.com/omnirom
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Created 2017-03-06
Last Updated 2017-06-11

reserved

New WEEKLY build released. This build contains rootless theme support through substratum (downloadable from the playstore)

The issues posted in op are still present?

yes they are, those issues mainly relate to sonyxperiadev project, which is the base of the bring-up of Xperia X Compact on omni.
The issues need to be resolved there, then they will also be resolved for omni

oshmoun said:
XC/KUGO/F5321 OmniROM BUILDS
NOUGAT 7.1
DOWNLOAD WEEKLY
CURRENT ISSUES ON OFFICIAL:
1. Incall speaker volume is not controllable
2. Slight incall echo on receiving side
3. Double tap to wake doesn't work
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm/tree/android-7.1
BUGS REPORT
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
CHANGELOG:
https://changelog.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
[/CENTER]
XDA:DevDB Information
[ROM][XC][N][7.1][WEEKLY]OmniROM, ROM for the Sony Xperia X Compact
Contributors
oshmoun
Source Code: https://github.com/omnirom
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Created 2017-03-06
Last Updated 2017-03-06
Click to expand...
Click to collapse
screenshot Please

eymentuna said:
screenshot Please
Click to expand...
Click to collapse
Ok i will add some screenshots when possible, but please don't quote the first post next time

Flashed your rom yesterday. I got the same problem as with the aosp rom, my x compact frequently loses mobile network connection. Today I had no connection for several hours. Had to reboot 4 times to gain network connection. Though I don't know if the restarts fixed it. Plus I often only have hspa or 3g connection, this is strange. This doesn't happen on 7.0 or earlier ROMs.

Micka84 said:
Flashed your rom yesterday. I got the same problem as with the aosp rom, my x compact frequently loses mobile network connection. Today I had no connection for several hours. Had to reboot 4 times to gain network connection. Though I don't know if the restarts fixed it. Plus I often only have hspa or 3g connection, this is strange. This doesn't happen on 7.0 or earlier ROMs.
Click to expand...
Click to collapse
Maybe you have your APN settings setup incorrectly?
Other than that, this rom does not replace the modem partition so that should be the same as on stock. Not sure where your issue would come from if not from APN

Thank you I will take a look at the apn settings (didn't ever change anything there though)

flashed your ROM but i find that the two big cores frequently turned off which is causing lags
it might be something wrong with the interactive governor I guess

jeremy.wang said:
flashed your ROM but i find that the two big cores frequently turned off which is causing lags
it might be something wrong with the interactive governor I guess
Click to expand...
Click to collapse
That doesn't seem wrong. The big cores will only go online if they're needed. They stay offline most of the time. That still shouldn't cause stuttering though.
Just checked here and big cores go online on high cpu loads as expected.

Is F2FS supported? I didn't see it listed anywhere and the changelog link in the op just loads the Omni homepage.

TadMSTR said:
Is F2FS supported? I didn't see it listed anywhere and the changelog link in the op just loads the Omni homepage.
Click to expand...
Click to collapse
F2fs is not supported, because fstab is explicitly requiring ext4 partitions.

oshmoun said:
F2fs is not supported, because fstab is explicitly requiring ext4 partitions.
Click to expand...
Click to collapse
Is F2FS something you could add without too much difficulty? I use it with some Nexus 7 2012 and Asus TF201 tablets and it appears to make a difference. Not sure how noticeable it would be on the XC though. I completely understand if adding F2FS support is not something you want to focus your time on.
Thanks for your work on this rom. I get my XC in the mail tomorrow and I'll be loading Omni pretty soon after.

TadMSTR said:
Is F2FS something you could add without too much difficulty? I use it with some Nexus 7 2012 and Asus TF201 tablets and it appears to make a difference. Not sure how noticeable it would be on the XC though. I completely understand if adding F2FS support is not something you want to focus your time on.
Thanks for your work on this rom. I get my XC in the mail tomorrow and I'll be loading Omni pretty soon after.
Click to expand...
Click to collapse
Honestly i haven't checked if it's feasible or not. Main issue is that this is my daily driver so i can't experiment with it to such levels.
I'd suggest you setup your device on omni, then maybe i can upload a custom build with f2fs support for you to build. Assuming f2fs is possible on XC of course, which is something I'll check soon

Got Omni loaded and was trying out encryption. It kept boot looping. On one of the loops I briefly saw the Omni logo. All the other times just the Sony boot screen, the LED would light blue/purple then turn red as the phone restarted. I know setting up encryption will cause several reboots but this didn't seem to be working correctly. Does Omni on the XC support encryption currently?

TadMSTR said:
Got Omni loaded and was trying out encryption. It kept boot looping. On one of the loops I briefly saw the Omni logo. All the other times just the Sony boot screen, the LED would light blue/purple then turn red as the phone restarted. I know setting up encryption will cause several reboots but this didn't seem to be working correctly. Does Omni on the XC support encryption currently?
Click to expand...
Click to collapse
Hmmm, haven't tested encryption.
Can you try booting to twrp to see if that at least works? That way we know the issue does not lie in the kernel

oshmoun said:
Hmmm, haven't tested encryption.
Can you try booting to twrp to see if that at least works? That way we know the issue does not lie in the kernel
Click to expand...
Click to collapse
Yea twrp works. Had to go into recovery to restore my backup. It appears the encryption process did start as the first restore had the boot loops. It was only after I formatted the data partition that the restore worked and I could boot back into Omni without issue. I do have Magisk installed for systemless root so not sure if that is part of the problem. The next time I try I'll remove Magisk first.
Update: Did some searching and it looks like Magisk might be the cause. Some people have reported that encrypting the device before putting Magisk on works.
Update 2: Did a clean install of Omni after formatting all partitions. Still getting the boot loops so Magisk wasn't the cause. Some boots only have the Sony logo. Other timers the Omni logo does appear but then it restarts.

TadMSTR said:
Yea twrp works. Had to go into recovery to restore my backup. It appears the encryption process did start as the first restore had the boot loops. It was only after I formatted the data partition that the restore worked and I could boot back into Omni without issue. I do have Magisk installed for systemless root so not sure if that is part of the problem. The next time I try I'll remove Magisk first.
Update: Did some searching and it looks like Magisk might be the cause. Some people have reported that encrypting the device before putting Magisk on works.
Update 2: Did a clean install of Omni after formatting all partitions. Still getting the boot loops so Magisk wasn't the cause. Some boots only have the Sony logo. Other timers the Omni logo does appear but then it restarts.
Click to expand...
Click to collapse
Please do the following:
1. Boot up device after trying to encrypt
2. After device crashes at start and reboots, directly boot up twrp with volume buttons
3. Using adb, get all files under/sys/fs/pstore and upload
I hope they was understandable, and thanks for investing time in this

[ROM][EXPERIMENTAL][XT897][JBBL][crDroid][Nougat]crDroid 7.1.2

DO NOT FLASH GAPPS! untill your second attempt and you have had a "play".
How I built it:
Set up a virtual Box (on Win7 64b) to build Lineage OS 14.1 (followed their instructions)
Source: https://github.com/crdroidandroid/
I used a working device tree (ie local manifest) from my working LineageOS 14.1 Build machine for an XT897 (for me I use the touch drivers for an XT907, but not in this build)
Basically, I have done no "magic" here, it all just kinda worked. up to a point as its pretty buggy. BUT IT BOOTS!
I also have a ResurrectionRemix 7.1.2 with similar issues.
This is an experimental build of crDroid 3.6, Android version 7.1.2, an experimental build for a non-official device (ie xt897).
I personally do not have an xt897, but an xt907. Since its relatively simple to port xt8907 ROMs to an xt907, I tried building crDRoid (and RR). It looks OK untill i flash GApps (i use Open GApps pico, and also tried a few others to no success)
The good
It's crDroid!
It's Nougat!
It Builds
It Boots!:highfive:
It has all the eyecandy!:angel:
It feels really "snappy"
The bad
If you flash Gapps it falls to pieces in a never ending cycle of crashes!:crying:
It is buggy even without GApps​
Since I do not own an xt897, I cannot test this zip (as is) personaly, and hope someone with an xt897 will try the zip (with GApps) and let me know if they too get the same FC's I get on an xt907.
What I hope is that if the same errors occur on an xt897, that either a developer working on crDroid ( @neobuddy89) or the maintainer of the LOS xt897 device @kabaldan) will see this thread and any logcat's posted and be able to easily identify what is wrong and needs to be changed top make it work? And whatever fixes it for an xt897 does the same for an xt907.
Credits: All credits go to @kabaldan (for the xt897 official LOS device maintenance), crDroid contributors (multiple but I often see @neobuddy89 updating the source) & all the many LOS contributors and Cm maintainers before them.
Almost forgot, Flash this ZIP at your own risk, the responsibility is all yours, it is provided as-is, with no garantees or whatever and I will not be held resonsible for any damage to your device or its data etc etc etc
Installation:
1) Download the ZIP
2) Boot into TWRP recovery
3) Make a nandroid (you will definitely be going back) And remember, a nandroid is NOT 100%! if you don't understand this, maybe trying this is not for you.
4) Wipe system/data/cache/dalvik
5) Flash update package (ie install the zip)
6) DO NOT INSTALL GAPPS! (try the whole process again including the wipes with GApps, if you dare...)
7) Reboot to system
Please get some logcats and post them on hastebin/pastebin etc etc NOT HERE, only the links. Hopefully we can fix it and have some highly customisable nougat ROM's for our devices. And the steps to make it work may also be helpful for the next Android iteration.
Download Link: https://clicknupload.org/yxtmx1ac75pw
And please post how you go with this ROM, I would like to know if its as flakey on an xt897 as it is on an xt907.

For any photon Q users, format /data to f2fs other wise this rom will refuse to work correctly. Otherwise, great work DiamondJohn!

Galaxyninja66 said:
For any photon Q users, format /data to f2fs other wise this rom will refuse to work correctly. Otherwise, great work DiamondJohn!
Click to expand...
Click to collapse
Yeah, forgot I did this thread. Probably because it appears to have had such little interest/response.
DiamondJohn said:
DO NOT FLASH GAPPS! untill your second attempt and you have had a "play".
Click to expand...
Click to collapse
If you format your data partition to fs2fs, then this may actually be usable as a daily, with GApps installed. It cleared all the issues with my xt905/907. I do not have a photon Q to test it on personally.

The Download link seems broken, get it back up and I'll give it a go

Removed

rahimali said:
It has been replaced by XT905/XT907 version which you can find here
Click to expand...
Click to collapse
No, it has not replaced, as the xt905/907 version will not completely work on an xt897 (hardware keyboard being the obvious difference), and even if the screen drivers are replaced, I changed the device tree to align more to an xt907 and moved away from the xt897. The above build was specifically for an xt897. I built it in the days before I knew about formatting the data to F2FS, to see if I could build for an xt897, since it was an official LOS device.
Since I got the RAZR M (ie 907/905) up and running (simply format data to F2F), and at the time there appeared to be VERY little interest in this build, I never really looked back, and don't even know which of my historical builds were the one for this thread. Sorry, but you were a little late to the party. :crying:

Hi does anyone know if this rom or maybe the atrix hd lineage rom could be flashable on the razr hd xt925? I know that radio and storage is different as well as the recovery, so I ask if anyone tried or knows how it be feasible

elbart88 said:
Hi does anyone know if this rom or maybe the atrix hd lineage rom could be flashable on the razr hd xt925? I know that radio and storage is different as well as the recovery, so I ask if anyone tried or knows how it be feasible
Click to expand...
Click to collapse
Unless you specifically have an XT897, you would be better off with an XT907; if it can be modded/flashed onto an xt925.
https://forum.xda-developers.com/dr.../crdroid-3-8-nougat-xt907-xt905-jbbl-t3697571
I think there may even be a post by someone else with an XT925 or 926. If not in that thread then maybe in one of my other XT907 ROM threads.

Any news on those bugs? I'd be especially interested in ResurrectionRemix 7.1.2. @DiamondJohn

Shani Ace said:
Any news on those bugs? I'd be especially interested in ResurrectionRemix 7.1.2. @DiamondJohn
Click to expand...
Click to collapse
My XT905 (which I built for using a modified XT897 device tree), has died, so I don't build it anymore.

DiamondJohn said:
My XT905 (which I built for using a modified XT897 device tree), has died, so I don't build it anymore.
Click to expand...
Click to collapse
Oh I see, thanks for the quick reply though!

DiamondJohn said:
My XT905 (which I built for using a modified XT897 device tree), has died, so I don't build it anymore.
Click to expand...
Click to collapse
Shani Ace said:
Oh I see, thanks for the quick reply though!
Click to expand...
Click to collapse
It did just occur to me, that with some minor changes to any of the ROM zips I created for the XT907 (including RR), you could run them on an XT897. Basically, after you flash the ROM (after changing the assert/check that its an XT907) you need to switch the two screen driver files (atmxt-r1.tdat & atmxt-r2.tdat) and grab the Assanti APK (ie the physical keyboard) from another ROM. Basically a reverse of what I suggested to do for a port from XT897 to XT907 https://forum.xda-developers.com/droid-razr-m/development/how-to-port-lineage-13-0-6-01-to-t3607500
Good luck, and be sure to share if you do it.

DiamondJohn said:
It did just occur to me, that with some minor changes to any of the ROM zips I created for the XT907 (including RR), you could run them on an XT897. Basically, after you flash the ROM (after changing the assert/check that its an XT907) you need to switch the two screen driver files (atmxt-r1.tdat & atmxt-r2.tdat) and grab the Assanti APK (ie the physical keyboard) from another ROM. Basically a reverse of what I suggested to do for a port from XT897 to XT907 https://forum.xda-developers.com/droid-razr-m/development/how-to-port-lineage-13-0-6-01-to-t3607500
Good luck, and be sure to share if you do it.
Click to expand...
Click to collapse
Oh ok, good to know, thanks! I'll save that info for later in case I need it.
Saw an official Lineage 14.1 version for the XT897 so I'll probably try that first once I get a Photon Q again.

Lineage OS 14.1 Release 1 (uploaded January 17 1025pm eastern)

Release 1 is posted.
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
******************************Start of dev stuff************************************************************
kernel sources based off of LG K10 devs msm8916 caf kernel sources (since its basically the same device) here:
https://github.com/touchpro/android_kernel_lge_msm8916
all the device and vendor trees are based off of teamregular's/LG K10 devs work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos14
vendor: https://github.com/touchpro/android_vendor_lge-lineageos14.1
*********************End of dev stuff*********************************************************************
Feel free to create other custom roms based on the trees above!
I would recommend using my TWRP 3.2.0-0 here to flash it: https://androidforums.com/threads/update-twrp-3-2-0-built-from-source-12-8-17.1103219/
what works:
everything as far as I can tell
The rom zip:
https://androidfilehost.com/?fid=746010030569947653
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 7.1)
THIS DOESNT COME STOCK WITH SU!
Download it here: https://download.lineageos.org/extras
(choose the option for su (arm) and 14.1)
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!

beta 2 uploaded
dt2w works, bluetooth audio works, camcorder works.
wifi still partially broke and is a wip. after that its on to lineage os 15 for the h631

wifi works now and the end? of lineage 14.1 dev is here. everything seems to work now
release 1 is posted in the op.

Awesome work! I've finally got me a full featured daily driver

I still got my OG Stylo lying around somewhere. Guess I'll give this ROM a try...

After attempting to reboot after installing, I got a "Kernel Crash!" error. Now my Wi-Fi won't work after restoring a Nandroid backup. Good thing the OG Stylo isn't my primary phone, anymore.
EDIT: I just realized Bluetooth is busted, too.
EDIT 2: After reading from sources outside of XDA, the firmware should have definitely been on v20k before flashing this. Oh well. I might check into attempting to fix the issues, one day.
But ever since I moved on to the OnePlus 5, I only use the OG Stylo as an alarm clock. As long as that still functions, at least it won't end up in the dumpster.

Gave this ROM a go. VERY pleased! WiFi had a hiccup but now working. I can connect to Bluetooth but can not hear audio. Any others come across this? I'm on the metro version of the Stylo.
Thanks in advance.
Z
Sent from my LG-H631 using Tapatalk

I have a MS631 (MetroPCS).
S/W : MS63120p
Is it possible to install and any plan to post Official Release (14.1 or 15 later)?
Thanks..

This is cool... hoping to get a Google-less minimal fernsprecher going, but this time (compared to your other 14.1 build) I can't see any providers-- just 'error while searching for networks.' Now I'm guessing the reason is the same in both cases-- I started from wrong official ROM. Can anyone point to a 63120k kdz? All the old links I found yet are dead
ed: Tried to prove to myself that a kdz was even useful. I have a few wrong kdz sitting around still-- 10j, 20b, 20l. LG Flash Tool wouldn't actually change anything, ever, no matter what. ("Consult your system administrator". Well, he's me... baka.) And LGUP looked like it was doing great the first time, right up until it gave me back a shiny brick (QHSUSB__BULK), so ...maybe later?
:: phasepalm ::
ed-2: found https://lg-firmwares.com/lg-ms631-firmwares/ so now all I have to do is get QFIL to do anything.

I love this OS. I removed the Nexus launcher and installed the new pixel 2 launcher in its place though. Every now and again I have to disconnect and reconnect Bluetooth. But that's not really a problem for me. WiFi sometimes drops but reconnect. I can't wait for the new lineage OS.

Any update?

pnaralove said:
Any update?
Click to expand...
Click to collapse
Nope, because the OP's phone was destroyed.
On another note: I was also able to get my OG Stylo up and running again with LG Bridge yesterday, with the latest official update (Marshmallow). I might try this ROM again, one day.

Revenant Ghost said:
Nope, because the OP's phone was destroyed.
On another note: I was also able to get my OG Stylo up and running again with LG Bridge yesterday, with the latest official update (Marshmallow). I might try this ROM again, one day.
Click to expand...
Click to collapse
Thank you for the reponse
Please let me know how it is after you try this ROM.

won't boot all the way through, logcat without complete boo
whoshotjr2006 said:
Release 1 is posted.
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
******************************Start of dev stuff************************************************************
kernel sources based off of LG K10 devs msm8916 caf kernel sources (since its basically the same device) here:
https://github.com/touchpro/android_kernel_lge_msm8916
all the device and vendor trees are based off of teamregular's/LG K10 devs work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos14
vendor: https://github.com/touchpro/android_vendor_lge-lineageos14.1
*********************End of dev stuff*********************************************************************
Feel free to create other custom roms based on the trees above!
I would recommend using my TWRP 3.2.0-0 here to flash it: https://androidforums.com/threads/update-twrp-3-2-0-built-from-source-12-8-17.1103219/
what works:
everything as far as I can tell
The rom zip:
https://androidfilehost.com/?fid=746010030569947653
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 7.1)
THIS DOESNT COME STOCK WITH SU!
Download it here: https://download.lineageos.org/extras
(choose the option for su (arm) and 14.1)
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!
Click to expand...
Click to collapse
Hello, everything seems to be fine but it won't boot all the way through. Also I am still a noob and am wondering how to get a logcat without being able to get all the way into the operating system? Any help would be appreciated

whoshotjr2006 said:
Release 1 is posted.
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
******************************Start of dev stuff************************************************************
kernel sources based off of LG K10 devs msm8916 caf kernel sources (since its basically the same device) here:
https://github.com/touchpro/android_kernel_lge_msm8916
all the device and vendor trees are based off of teamregular's/LG K10 devs work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos14
vendor: https://github.com/touchpro/android_vendor_lge-lineageos14.1
*********************End of dev stuff*********************************************************************
Feel free to create other custom roms based on the trees above!
I would recommend using my TWRP 3.2.0-0 here to flash it: https://androidforums.com/threads/update-twrp-3-2-0-built-from-source-12-8-17.1103219/
what works:
everything as far as I can tell
The rom zip:
https://androidfilehost.com/?fid=746010030569947653
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 7.1)
THIS DOESNT COME STOCK WITH SU!
Download it here: https://download.lineageos.org/extras
(choose the option for su (arm) and 14.1)
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!
Click to expand...
Click to collapse
hi, me again.. I finally got my phone back to totally stock from the LG Bridge. How do I get the v20 K that you were sitting on to try and get lineage on my phone now at this point. Thanks in advance

gameplayerdo2 said:
hi, me again.. I finally got my phone back to totally stock from the LG Bridge. How do I get the v20 K that you were sitting on to try and get lineage on my phone now at this point. Thanks in advance
Click to expand...
Click to collapse
Like I said, I finally found https://lg-firmwares.com/lg-ms631-firmwares/ and v20k is on there but no promises unless you can find the known good MD5 hash somewhere. I couldn't just try it because again, this ms631 is bricked in 9008-mode.

derpendicular said:
Like I said, I finally found https://lg-firmwares.com/lg-ms631-firmwares/ and v20k is on there but no promises unless you can find the known good MD5 hash somewhere. I couldn't just try it because again, this ms631 is bricked in 9008-mode.
Click to expand...
Click to collapse
Hey there I got it. What I did was I hooked up to LG Bridge and let LG do the repair from the upgrade repair button and it got my phone back to square one which was fine. From there i unlocked the bootloader and booted from TWRP 2.8.7.1 image file and then once inside TWRP I installed version TWRP 3.2.0-0 recovery from the zip file. At that point I then was able to do an advanced wipe and wipe out the system and then do the lineage install from there. Once that worked I wiped it out and installed CyanogenMod just to see if it will go on as well and it did. So I went back and wipe that out and put the lineage OS back on there with the opengapps and it's running flawlessly! I also installed magisk to root it and everything is running fine. The only thing I miss from the LG part of the software was the knock on knock off feature. And I downloaded a tap on tap off app for that but you can't use any other locks with it. but I'm good, and thanks! Because I hated that stock operating system with all the bloatware even though MetroPCS didn't have as much garbage as the T-Mobile or other versions but still now I can control Play Store and everything else. I in fact use APK pure to get most of my apps if I can find the software there.

Hey I got my LG g Stylo and might use it again with lineage on it. I need to understand you're flashing a nougat custom rom over a mm stock room and it works? Also, I have 20o and in reading I see 20k is the requirement? Hope to hear feedback, thanks in advance. And can anybody tell me how they got twrp 3.0.2 on the stylo? I can't seem to do it with an unlocked bootloader via adb.

elwhiteboy01 said:
I need to understand you're flashing a nougat custom rom over a mm stock room and it works? Also, I have 20o and in reading I see 20k is the requirement? Hope to hear feedback, thanks in advance. And can anybody tell me how they got twrp 3.0.2 on the stylo? I can't seem to do it with an unlocked bootloader via adb.
Click to expand...
Click to collapse
Your best bet is (very likely) to back up stuff and wipe it all out. I use SMS Backup Restore, manually export contacts, copy the files to SD, etc. Then to answer your other question-- root using apk from Kingroot.net which works but it loses root every time you reboot. So before you do, you can use Flashify to flash TWRP onto recovery, also run TitaniumBackup once and put everything on SD card. Then with TWRP running you could install SuperSU zip onto the stock rom and it actually sticks, but you would (make yet another backup and) wipe the phone before starting fresh with Lineage and then restoring your stuff piecewise. That was last year, though, might have forgotten something. Like it's hard to remember but I *think* you can skip the Kingroot & Flashify routine altogether, just reboot to fastboot and on the computer 'fastboot boot twrp-x.x.x.x.img' to boot it once-- even though it won't flash it directly. Then 'adb push twrp-x.x.x.x.img /sdcard' and then inside TWRP, flash it using [Install Image] under [Install] instead of the usual zip file. HTH

derpendicular said:
Your best bet is (very likely) to back up stuff and wipe it all out. I use SMS Backup Restore, manually export contacts, copy the files to SD, etc. Then to answer your other question-- root using apk from Kingroot.net which works but it loses root every time you reboot. So before you do, you can use Flashify to flash TWRP onto recovery, also run TitaniumBackup once and put everything on SD card. Then with TWRP running you could install SuperSU zip onto the stock rom and it actually sticks, but you would (make yet another backup and) wipe the phone before starting fresh with Lineage and then restoring your stuff piecewise. That was last year, though, might have forgotten something. Like it's hard to remember but I *think* you can skip the Kingroot & Flashify routine altogether, just reboot to fastboot and on the computer 'fastboot boot twrp-x.x.x.x.img' to boot it once-- even though it won't flash it directly. Then 'adb push twrp-x.x.x.x.img /sdcard' and then inside TWRP, flash it using [Install Image] under [Install] instead of the usual zip file. HTH
Click to expand...
Click to collapse
The phone is bricked now. I did a fastboot boot twrp and installed magisk zip. Then installed flashify and flashed twrp image. Then formatted data and installed the lineage os and it didn't go through. I was in a hurry so I didn't backup the stock ROM. And so I pulled the battery and put it in download mode and flashed kdz. And when it finished the screen went black and shows no signs of life no matter what I do.

[ROM] LineageOS 14.1 UNOFFICIAL h631

Latest release
Built from whoshotjr2006/touchpro's sources with minimal changes. All credit to original devs.
I'm not going to commit to regular updates but I'll try to do occasional ones.
Recommend using this TWRP (also stolen from touchpro).
Installation:
Enable developer options in stock ROM (tap build number a bunch of times)
Enable 'Advanced Restart' in developer options
Hold power button, select restart, restart to bootloader
Use fastboot to unlock bootloader
Use fastboot to flash TWRP recovery
Reboot to recovery using fastboot command
Wipe everything in TWRP, format data, and factory reset
Push ROM to /sdcard/ and install
Optionally push Gapps and/or LineageSU and install
Boot and enjoy (first start might take a while)
Tested on a T-Mobile LG G Stylo, all seems well.

As far as I can tell, everything is working fine. You should be able to dirty flash if you are using another Lineage 14.1 build but I haven't tested it.

It's awesome to see others making roms for this device again, but do you think you will be able to make a oreo rom though? ?

ItzBluestone said:
It's awesome to see others making roms for this device again, but do you think you will be able to make a oreo rom though? ?
Click to expand...
Click to collapse
The LOS14 tree is still getting security updates and will run a lot faster than LOS16. I could build an Oreo ROM but there's little chance of finding the vendor FW needed to get camera, bluetooth, etc working properly.

jsheradin said:
The LOS14 tree is still getting security updates and will run a lot faster than LOS16. I could build an Oreo ROM but there's little chance of finding the vendor FW needed to get camera, bluetooth, etc working properly.
Click to expand...
Click to collapse
oh, well that's unfortunate...

So what is different? Just security updates?

This ROM breathed new life into my old MetroPC version of this phone (2GB/16GB)!
I bought this phone two years ago refurbished and carrier-unlocked (other than banned on MPC) off Amazon. Looked brand new. I just installed a new battery last month. Original battery wore out.
ROM works beautifully. Nice to be free of the factory cruft. Also, the TWRP from your OP works much better than the one I had been running. (Neither TWRP reads the current time/date through.)
I had been rooted with SuperSU, now I'm rooted with Magisk. I flashed mini Gapps 7.1.
I have not tested NFC yet.
Thank you for this ROM and your post!

My TMo h631 will not take the image. During the install it will kernel panic and throw an error.
I do factory reset, wipes, formats but still no go.
Anyone knows how I can fix it?

Will this work fine on the LGM631?