yashsingh1/xdaforums huggingface dataset:
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] EsromTech:
BEANSTALK 7.1.1 ROM

​

Camcorder fix

Clock customization works

Fully customizable

LineageOS 14.1 based

Quicker system animations

Trimmed down fat and excess bloat

Option to enable all widgets

Numerous extra lockscreen options

LCD Density

Custom original BeanStalk Wallpapers by skyliner33v

Custom BeanStalk bootanimation by skyliner33v

3-minit battery support

Clock and date options

Contextual Header - Original and Polygraphic

Battery styles - Includes specific colors and styles. Also includes battery bar

Do not disturb option

Show notification count

Recent screen options

Customizable navigation bar

Use Omniswitch as default recents

Slimrecents

Lots of Lockscreen customizations

Built-in screen record

Toast animations

App Circle bar

Gesture Anywhere

Disable FC warnings

Disable Immersive message

Force expanded Notifications

Configure scrolling cache

Build.prop MOD options to enable/disable tweaks as preferred

Less frequent Notification sounds options

CRT screen off/on options to specify how the animation shows

Enable/disable wake up on charge option

Superuser fully embedded into the build and accessed from settings menu

CM Performance options and features

Hide superuser icon

Developer options and advanced reboot enabled by default

Numerous cherry-picks and improvements throughout the build, baked into the

awesomeness of existing CM layout.

Numerous other options hiding throughout the build. For a full list of changes and features, please

be sure to checkout change log below.​

* Download ROM and latest GAPPs.

* Copy ROM and GAPPs from above to internal storage.

* Reboot into recovery

* Full wipe and format is ALWAYS suggested to avoid odd issues.

* Flash ROM and then flash GAPPs.

* Reboot and enjoy the BeanStalk goodness.​

Downloads

Last Build Harpia

XDA:DevDB Information

BeamStalk Nougat, ROM for the Moto G4 Play

Contributors

EsromG5

Source Code: https://github.com/LineageOS/android_kernel_motorola_msm8916

ROM OS Version: 7.x Nougat

ROM Kernel: Linux 3.10.x

ROM Firmware Required: Custom Recovery

Based On: CyanogenMod, AOSP

Version Information

Status: Testing

Created 2017-02-01

Last Updated 2017-02-01
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] facuarmo:
Testing.
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] Exedion:
Oms?
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] fireball0093:
Everything seems to be working fine on the unlocked XT1607. A bit laggy once in a blue moon but nothing really of concern at all
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] pyrolad:
The download link is dead!
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] Outfield303:
volte works ? tell me ASAP
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] Ashutosh Sundresh:
The ROM itself is not available
[Moto G4 Play ROMs, Kernels, Recoveries, & Other De] Outfield303:
Links are DEAD from months! [MENTION=4730968]EsromG5[/MENTION] Please Update the links
[LineageOS Questions & Answers] nezlek:
As more Lineage OS builds come on line and multiple "nightly" update builds for devices start to appear, one of the issues users may face is the how and why of installing them. The Lineage UPDATER states that it will reboot to the device's recovery to install the update, but that doesn't guarantee anything. If that recovery happens to be, for example, TWRP 3.0.2.0 on an LG v410 tablet, all that might happen is you might find yourself, as I did, staring at a TWRP screen with NOTHING happening. The goal of this thread is to give Lineage users a place to consolidate their experience-based knowledge of how to handle this - other than re-flashing the whole thing -for whatever device(s) they may have.
[LineageOS Questions & Answers] broly10000:
It will probably be the same as for my L900 with CM13 were I have to download the update, reboot into TWRP and update manually.
[LineageOS Questions & Answers] jhedfors:
Are you able to navigate to the download directory in TWRP?

/data/data/org.lineageos.updater/app_updates
[LineageOS Questions & Answers] nezlek:
This is far from the worst thing that has ever happened, but WHAT, for instance WOULD be the recoveries that DO allow for automated updates? In my case, I downloaded the new nightly to the root directory my SD Card and let fly, and everything worked, but that seems rather not elegant.
[LineageOS Questions & Answers] jhedfors:
Automated updates work fine for me. It automatically boots onto TWRP, applies the update, and reboots.

Might be a device-specific issue. I am on the OnePlus One, and the same TWRP version (of course made for my device).

I am guessing that perhaps there is an issue reading or writing the recovery script.
[LineageOS Questions & Answers] nezlek:
Interesting. Sure didn't work for me this a.m. but as I said, far from the end of the world. I also think the "nightly" is going to morph into the "weekly" and that will be fine, too. I have yet to find anything that doesn't work to my satisfaction aside from not automatically picking up my Wi-Fi at boot - not exactly a deal breaker :D
[LineageOS Questions & Answers] jhedfors:
BTW, are you able to navigate to that directory in TWRP?
[LineageOS Questions & Answers] nezlek:
Oops. Right after I clicked on send I realized I didn't answer your question!!

Yes, and the zip file is there, but nothing happened. As I said, far from fatal.
[LineageOS Questions & Answers] davidd105:
I updated my opo (Bacon) with the nightly ota download and most recent twrp, after reboot I had lost my home screen (2 of 3 pages remained) and several of the apps that I had dragged to those screens.. didn't work well for me. I let the ota reboot into twrp and it seemed to proceed without troubles until the opo came back to life. (finished booting)
[LineageOS Questions & Answers] broly10000:
Galaxy S5 SM-G900T here. Wiped my phone and installed lineage-14.1-20170131-nightly-klte-signed.zip with open_gapps-arm-7.1-stock-20170131 the day it came out and it has been good so far, no crashes or freezes and all apps work good except FolderMount, no biggie. Tried to install lineage-14.1-20170207-nightly-signed.zip and is giving me an "error 7 can't install this package on top of incompatible data". Any way to fix this without factory reset? Doesn't make sense to factory reset every week for an update.

Update: Tried to reflash lineage-14.1-20170131-nightly-klte-signed.zip and got the same error. So something must have changed. The only thing I can think of is I have SU 2.79 installed.

Update 2: Removed root, restored boot and same continues. I dont want to wipe on every update.
[LineageOS Questions & Answers] nezlek:
Well, now semi-automatic at any rate.

Are you able to navigate to the download directory in TWRP?

/data/data/org.lineageos.updater/app_updates

First, sincere THANKS to jhedfors for this priceless bit of wisdom :D

Getting better. Still no "automatic update" but the latest "nightly" build did fire up TWRP, and put the update zip file into the aforementioned folder, and after that, installing it was the proverbial snap. I can't speak for everyone, but I would find no horror in the folks at Lineage giving in to reality and calling the "WEEKLY" as opposed to "NIGHTLY" builds.

Hey, since the only device I happen to have running Nougat at the moment also happens to be the OLDEST device I use on a regular basis, the Complaint Department shall remain CLOSED on this one. :angel:
[LineageOS Questions & Answers] drunkahol:
I have an LG G3 (d855) with working LineageOS. The updater downloads OK and the zip is indeed in /data/data/org.lineageos.updater/app_updates, but TWRP refuses to do anything about it on reboot. I can browse to the folder manually, but it does feel that something isn't firing to get TWRP to perform the install automatically.

What is the trigger for TWRP to install a specific Zip on reboot?

D
[LineageOS Questions & Answers] JohnnyDvanC:
For me, One Plus 3, automatic updates don't work. Also manually installing the latest

https://mirrorbits.lineageos.org/full/oneplus3/20170214/lineage-14.1-20170214-nightly-oneplus3-signed.zip gives me an error:

Checking for MD5 file...

Skipping MD5 check: no MD5 file found

Zip file is corrupt!

Updating partition details...

...done

Any idea?

I did a migration via experimental build coming from cm13 then updated to lineage 14, which worked OK.

But since then I cannot update the daily builds.
[LineageOS Questions & Answers] Darkwing_Duck:
I have the "same" issue on a Nexus 6.

The updater tells me I have an update, I ok it to download. Once done, I click install, gets into recovery and stops.

Still in the recovery, if I try to manually install from the downloaded location (data/data/...), it says zip failed.

I reboot and try opening that zip on a PC and sure enough, Windows thinks it is corrupt also.

If I re-download manually from "https://download.lineageos.org/shamu" that copy opens fine on the PC and when moved to the phone (data/data/...) installs fine.

There is something corrupting the zip when the updater does its thing. ;-(

Note: This isn't a migration, I have just been updating "nightlies".
[LineageOS Questions & Answers] LGG2_Lin:
Stuck in the TWRP...

Hi everyone, in trouble :/...I have got an LG d802 and updated TWRP from 2.8.7 to 3.0.2-1, then did a boot/system backup of the current cm 13.0 and after that the "experimental" update (as described in the recent update & builds post on lineageos) from cm 13.0 to lineage 14.1 which worked.

I decided to use lineage updater to go to the latest nightly as described which must have failed (booted in TWRP an did nothing...). When installing the 14.1 nightly manually, TWRP 3.0.2-1 showed two error lines with "unknown command".

Since then I'm stuck in TWRP.

Restore of cm 13.0 backup was not possible with neither TWRP 3.0.2-1 nor 2.8.7, no errors, just wouldn't boot. I can't even find any cm 13 build... to try to back which would be an option of course.

I did wipe the system then, lineage expermental + nightly or just nightly can be installed "successfully" with TWRP 3.0.2-1 and 2.8.7 with no errors there anymore, but also the system won't boot.

Please, please help (and/or redirect me to the right thread), what can I do? Thank you!
[LineageOS Questions & Answers] nezlek:
First, you can ignore the two errors in TWRP

I've gotten them with each update I've installed, but in my case - an LG v410 tablet - I have successfully, if manually, installed three updates so far, with a few peculiarities. "Automatic" is just a nine-letter word concerning updates at this point. I can live with that.

One - it is going to download it to /data/data in the tablet's storage no matter WHAT I do. I can live with that.

Two - I seem to have to download the update at least two times before the Lineage updater accepts the fact that it is there. I can live with that, too.

Three - a "getting there and almost what I want with no major glitches" Nougat build is much preferred to a KitKat build that LG couldn't give a rat's rear end about supporting, and I can DEFINITELY live with that. :D

But, back to YOUR problem with being stuck in TWRP. Worst case disaster recovery scenario - ANY chance you have a non-Lineage ROM you can revert to and start over from THERE? Realize what a pain that is going to be, but... When I still had CM 12.1 on it, I once did that out of desperation when nothing else seemed to be able to get it to boot. WHY such a laborious process fixed it I have NO IDEA, but better to have a working mystery than a well understood paperweight.

I ASSUME you have respectable backups of your data, etc.. so that loss of TIME is your major issue ?? Also assume you've wiped the caches, etc..?? You COULD try offloading your data, wiping data, and reloading.

It also seems to take a LONG time to reboot after an update. Can I assume you are at least getting to the Lineage animated LOGO screen or are you hanging in TWRP itself?
[LineageOS Questions & Answers] LGG2_Lin:
I'm hanging in TWRP, also did wipe data before. I found a full 13.0 backup, selected all but Data because of storage space..."successful"...still system won't boot... :D

(Power Off in TWRP doesn't even work, just reboots, if that is of any help...)...A wild guess...file system issue maybe?
[LineageOS Questions & Answers] nezlek:
Yikes

As reasonable a guess as any, I suppose. I admit I've never had TWRP refuse to power off if nothing else, no matter how badly I had screwed things up (often spectacularly) elsewhere.

ASSUME you've tried the hold the power button until it shuts off, after which it should have booted to Android when powered on trick. Or, assuming you can do so, pull the battery?

Perhaps your bootloader is the culprit. Can you just re-flash that?
[LineageOS Questions & Answers] jeensg:
I got stuck in TWRP Recovery Boot-Loop. Already had the issue before with cm14.1 beginning of december. Didn't they fix the bug or is it another one?

For the specs: I got a Nexus 4 - mako.

I did this FIX and it booted up again as it was before: https://xdaforums.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386

What's now correct update? Download and dirty install manually in TWRP?
[LineageOS Questions & Answers] nezlek:
Thanks for the post

:good:

I've NEVER encountered that issue so glad to see someone has figured out a more elegant solution. I suspect your CM 14.1 problem is / was device (build for it) specific, as NONE of my CM / Lineage devices has ever done any such thing and they've all been updated several times in the last month.

In every case, however, I 've had to MANUALLY install the update zip file from within TWRP. Far worse things have happened and since I drive a stick shift car anyway, what the problem? :eek:
[LineageOS Questions & Answers] LGG2_Lin:
The dd commands "worked", now I'm stuck with the lineage boot animation ;D
[LineageOS Questions & Answers] :
If u guys face problems while updating ROM (dirty flash) and u still want it data partition unwiped,then u have only one solution left...use titanium backup and backup user app+data...and do a clean flash of the latest update and restore the same using titanium backup!!

U r good to go ???
[LineageOS Questions & Answers] LGG2_Lin:
Thanks, I already did a data wipe. It's not about backup, it's about an unusable device.
[LineageOS Questions & Answers] Safal Oraon:
Automatic and Semi Automatic update both have issues

Automatic update just opens twrp recovery and does nothing and if I try to locate and install the update thereafter then update installs (no error) but I think in the process everything gets corrupted because after installing the update and clicking reboot system now phone reboots to twrp recovery instead of the Android system(updates lineageos) after that I tried to restore the backup of the previous nightly build and backup gets restored and when I reboot the system again the **** ! I'm welcomed by the recovery and then I have tried everything wiped and new installation but same problem. The only way to solve this is by going to fastboot mode and connect phone to pc and via fastboot fresh install the stock boot.img , droidboot.img , recovery.img(stock recovery) and then open the stock recovery and install the stock original Android; then again unlock bootloader, then again install custom recovery(twrp in this case) , then again fresh install the lineageos updated ROM. And that's not the end of pain, now in the process as usual all my apps+data gets lost and I've to reinstall all my apps and setup my device's settings according to me. This is really frustrating and with weekly updates doing all these **** every week is like worst case scenario.

If anyone knows (I'm not asking for the automatic ota safe method) just tell/enlighten me with the manual method to update the lineageos without losing my apps+ data and device's settings because that is the decision of true update!!

If I had to install the UPDATE by wiping up every partition and reinstalling everything from scratch that's not an update that's called fresh installing of ROM via flashing.

Please if anyone knows the better way help me out, thanks in advance.
[LineageOS Questions & Answers] wieman01:
My OTA update does not work either. I upgrade by downloading the latest package with Chrome and installing it with TWRP (package is located in the Download folder). The OTA only gave me error messages.

Perhaps this works for you too.
[LineageOS Questions & Answers] Safal Oraon:
Do I need to flash experimental zip even when updating from official nightly build to new official nightly build ?? Please reply

And if yes where is the link of experimental zips
[LineageOS Questions & Answers] jhedfors:
No. Only coming from unofficial is it needed.
[LineageOS Questions & Answers] wieman01:
Just download the latest build from the Lineage website using a browser and install it through TWRP. That is the safest method right now.
[LineageOS Questions & Answers] MatheusOliveira:
Weekly Updates

Good Morning, everyone.

I'm a new Lineage OS user, so sorry if this is a dumb question, but I need to know: I have a Lineage OS 14.1 image installed (01/2017) and want to install a nightly update (02/23/2017). Can I open TWRP and install de downloaded .zip file without any wipe, over the current image? All my configuration files and media will be maintained?

Sorry again and thank you all for your attention.
[LineageOS Questions & Answers] wieman01:
Hi! Just download the latest Nightly using a web browser and install it via TWRP. All your settings and data will be preserved, I have done this a few times in the last weeks. No problems so far.

The OTA update function does not work well for me though, that is why I download the latest image from Lineage's website.
[LineageOS Questions & Answers] nezlek:
No such thing as a dumb question

You can download the update from Lineage and install it over your current ROM w/o loss of data or other stuff - ASSUMING - your current ROM is NOT the initial 'experimental' release. If that is the case you need to wipe and do a clean install first, and DO BACK UP EVERYTHING first if you need to, using something like Titanium Backup (possibly the best 5 bucks you may ever spend on an Android app IMHO). The other thing you are likely to run into is that updates may or may not be 'automatic'. Some of us are so blessed, others not. Already a few posts here about manually putting an update in place. Good lick.
[LineageOS Questions & Answers] MatheusOliveira:
Ok. I was not a blessed one about this.. I've made the download and my current ROM is not the 'experimental' release, so I will do the update tonight. One last thing: I don't need to install GApps again, ok?

Thank you for all.

Ps: If possible, tell me how is my English level, cause I'm not a native speaker and I'm trying to improve my skills with the language.
[LineageOS Questions & Answers] wieman01:
No, Gapps will no longer be required.
[LineageOS Questions & Answers] jhedfors:
You can dirty-flash official LOS14.1 nightly over official LOS14.1 nightly, no problem. Wiping dalvik/cache is usually a good idea, but not necessary.

Not quite true. The experimental release is SUPPOSED to be flashed over with nightly. That said, it is experimental, and it may not work, leaving you to clean install if it doesn't. However, the poster already indicated that they have a nightly version installed, so it should not be an issue (assuming that it is official version). :)
[LineageOS Questions & Answers] Ibuprophen:
I believe that the following link can be very helpful regarding your issue:

[ANNOUNCEMENT] Important Lineage/LineageOS Information To Know... by Ibuprophen

I wish you the best of luck!

Peace and Love!

Peace and Love!

~Ringo Starr~

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...

********************************************

**IF I WAS HELPFUL IN ANY WAY THEN**

**PLZ THANK ME WITH A THUMBS UP!**

********************************************
[LineageOS Questions & Answers] raikou95:
Same thing happens with my moto g2015 but with the update released today.

update downloaded, restart from the updater

the recovery starts the process it shows the md5 error (wich is common) and then it goes back to the main menu.

i cant see the update file in the recovery folder
[LineageOS Questions & Answers] jojhonny:
unable to update with weekly updates

app crash when opened from protected apps , i have the reopen the app to get to the lock screen

i had rapid charging when i was on CM13 but not it doesnt seem to work.

would be grateful for your help

Device one plus one

Lineage OS : 14.1-20170213-Nightly-bacon

Kernel : 3.4.112-lineageos-g887123d
[LineageOS Questions & Answers] shantahan:
New Unofficial can dirty flash over old unofficial?

Hi! I compiled an unofficial build for my device (mondrianwifi - Samsung Galaxy Tab Pro 8.4), and clean installed it, wiping my old CM build. That worked great. My first time compiling on my own.

However, when I try to dirty flash a new unofficial build that I've compiled, TWRP will flash it and say it worked, but when I reboot into LineageOS, it acts like nothing changed. It doesn't do the "upgrading apps" thing, and in Settings->About Device, it still reads the old build number.

I haven't found anything about dirty flashing unofficials over each other, but assumed it would work just like dirty flashing "official" nightlys. I would like to avoid clean installing all the time. Any info would be appreciated! Thanks.
[LineageOS Questions & Answers] tguadagno:
All, I wanted to share my experience. I have 2 devices on Lineageos 14.1

The first is a Z00A (Asus zenphone2) and i have no issue with the nightly updates, they work just fine.

My other phone is a d2att (Samsung sIII) and it has never been able to update. I just tried to apply the latest weekly out today and same as always I press the "update button", it boots into TWRP (3.0.2.0) and goes to the TWRP home menu...no update/no error. I have to download the updates separately and then apply manually. I would be happy to provide any info needed to help fix this problem, any solution on the horizon?

thanks for dev efforts!
[LineageOS Questions & Answers] nezlek:
Joy in Mudville

I am pleased to report that, at least for me, the update issue appears to have been completely resolved after installing the new (3.1.0.0) TWRP release. Obviously this may not apply to ALL devices having update issues, BUT the last "nightly" (weekly, OK, ask me if I really CARE what they call it so long as it WORKS) 14.1 update installed directly without a hitch on an LG 410 tablet. Life is Good, indeed. :good:

This leads me to a rather tentative conclusion that if there is a TWRP 3.1.0.0 release for the device it question, it (famous last words) SHOULD BE "problem solved." I can't really test that hypothesis with my other in-house devices, as they are using unofficial builds of either LOS, TWRP, or both, and automated download of updates does not occur for them at all, but I suspect that any feedback from the rest of you running devices with official builds would be really valuable.
[LineageOS Questions & Answers] thorost:
I can confirm this works with TWRP 3.1.0-0 beta on LG G4 (H815), too.
[LineageOS Questions & Answers] Bailx:
just a note on all this, if you read the instructions, you are only supposed to go from cm to lineage on the same version (ie cm14.1 -> lineage14.1) it states to upgrade from cm13 -> cm14.1 first, then onto lineage14.1

anyone having trouble should just do a clean install, while it's possible to do those upgrades, it leaves the door open to too many glitches/conflicts from test ones i did
[LineageOS Questions & Answers] belrik:
Is TWRP supposed to automatically flash the new image with 3.1.0.0 and latest weekly build? On jfltexx and not working for me.