yashsingh1/xdaforums huggingface dataset:
[Moto G 4G Android Development] sdembiske:
For those of you wishing to update to the April '19 Security Patch, I've uploaded one of my unofficial builds that is based off the latest official build files (as far as I am able to ascertain), with no additional modifications by me. It's been tested for a couple of weeks now with no problems noted.

I recommend a

clean

flash, in particular, when going from an official build to an unofficial build - in TWRP wipe Cache, Dalvik cache, System and importantly

format

Data > Yes before flashing the appropriate Open Gapps. Do a nandroid backup first, including your data.

Download Link for lineage-14.1-20190408-UNOFFICIAL-peregrine.zip:

https://mega.nz/#!pbojkCxK!78rbe-nM5GsCNuYVoasl-DkPnoJW1VxBXINsWVayj8E

This is a 1-shot deal

, so if you wish to keep your phone or other peoples updated, I recommend you learn to build it yourselves: refer to post # 1210 for the full build instructions.

Enjoy,

S.
[Moto G 4G Android Development] banksio:
BTW the zip will actually not allow a dirty flash, a clean flash actually has to be done.
[Moto G 4G Android Development] Brotherofsun:
Could someone share the lineage-14.1-20190207-nightly-peregrine-signed.zip build for download?
[Moto G 4G Android Development] macmobile:
^Two months after the last update not available anymore. Is this a joke?
[Moto G 4G Android Development] sdembiske:
Members can cry, throw tantrums etc., but, the fact remains this rom no longer has a maintainer and the LineageOS team has removed the downloads as a result. A simple Google search will show most likely that there isn't an alternate download mirror available -

Note

: I stand corrected ... refer to post # 1224 for a link to a (private?) mirror that does have the Feb. '19 official build if that is really what you want but ...

To be clear, the ONLY differences between the February '19 Official update and the Unofficial April '19 rom update that I've uploaded in post # 1214 are:

1). One says Official and one says Unofficial - i.e., it's a bloody word.

2) One is updated to February '19 and one is updated to April '19 off of the original GitHub sources and servers, the same sources that the Official downloads accessed and used to build the rom. I.E., The Unofficial April '19 upload I've posted is actually MORE SECURE because it's security patches are right up-to-date.

3) The Official February '19 rom had the Lineage OTA download option (I suspect most users actually used this feature previously to update their rom, hence the trouble in getting a copy of the Feb '19 download zip) ... BUT ... the OTA update feature is useless now as there won't be any more Official updates until somebody picks up the ball and decides to do the work to maintain it. The Unofficial April '19 rom can't be updated by OTA because it's not uploaded to and supported on the LineageOS servers. So, no real difference at this point in this regard - result is the same, no OTA updates.

If anyone notes any

operational

differences with the April '19 Unofficial upload to the last Official Feb. '19 download, please comment or put the uninformed, less knowledgeable members minds at rest.

Thanks,

S
[Moto G 4G Android Development] macmobile:
^It hasn't anything to do with your built. It's about the service Lineage provides. And it seems as if it's very limited. This kind of bad user experience makes me avoid Lineage OS in the future altogether.
[Moto G 4G Android Development] _that:
Maybe you should demand your money back.
[Moto G 4G Android Development] IronTechmonkey:
Here is what it "has to do with".

Lineage is provided for free and the developers work on it on their own time for no pay amidst real lives which involve more important things than providing us with free software.

Peregrine has had a particularly good run of LOS development, more stable than most and outlasting many newer devices - thanks to our device maintainer (who also handled non-device-specific issues when they were reported from Peregine). Now even after all that we have another build thanks to [MENTION=6302635]sdembiske[/MENTION]. Wow! Awesome!

Anyone who is unhappy with the LOS offerings is free to become a maintainer and develop the ROMs, or to go get an I-Phone and complain to Apple about all the stuff that you can't do with it but can do with an Android.

It's an honor to have been ninja-ed by you, and so succinctly at that. :silly:
[Moto G 4G Android Development] macmobile:
No need to explain this to me. I've learnt my lesson. It's for free, so don't expect anything!
[Moto G 4G Android Development] florstat:
Is somehow possible to retrieve the last official build? Why lineageos remove them from repos and does not store them in some archive with others old builds?
[Moto G 4G Android Development] :
here is the last Image from 20190207
[Moto G 4G Android Development] liasom:
I see two separate zip files. Which one is the real file?
[Moto G 4G Android Development] IronTechmonkey:
If you look at the full file names (and sizes) you'll see that one is a .zip (> 300MB) file and the other is a .sha file (< 1MB) associated with the zip file. IIRC the sha file is to confirm the checksum to make sure the file zip file is valid. If you are not confirming checksums you only need the zip.
[Moto G 4G Android Development] liasom:
Yes on your info and I get that, but I see 4 files in total. 2 zips and 2 sha files.
[Moto G 4G Android Development] sdembiske:
TWO different dates X TWO files per date = FOUR ... look more closely and read carefully all the letters & numbers and it will all become clear ...
[Moto G 4G Android Development] liasom:
Oops! Sorry about that...
[Moto G 4G Android Development] Pupet_Master:
Wait, you are complaining about a team that was supporting a 6 year old device up to february 2019 where motorola it self stop supporting the phone back in 2016? Also work that was made by the cumunity free of charge for you to even help woth yoir bootloop?

Really? Want the latest security patch on a 5 year old phone that you are lucky that lineage provided for for us for that long
[Moto G 4G Android Development] macmobile:
^No, you clearly didn't get what I was trying to say. My point was: Why is there no download available anymore just two month after the last update? The device of my friend bootlooped and I couldn't find anything to download, neither the original build nor the one from February.

Guess what was made available in this thread because of people requesting the very same thing?
[Moto G 4G Android Development] Pupet_Master:
Think of Microsoft extended support. Once the extend support is done, you cant download an os anymore foram theyre system. Thats what happen with XP, Vista and soon will happen with 7. This ROM final version is more than 2 years old, they were just updating security as a extended support. Now that ots over, thw Jenkins server was alocated for another ROM. Every company does that
[Moto G 4G Android Development] macmobile:
At least they announce when their support will end. But who cares about Microsoft? Does it make this any better? No! How the hell could you rely on a Rom if it could disappear any day? You can't. And I got my answers in this thread. It's free, don't expect anything!
[Moto G 4G Android Development] Pupet_Master:
who said they didnt anounce? Im with this phone since 2015, once se got N final, they ankibced that it would go away at any time. It last a round 2 years after the announcement. For such an old phone, abyone know that se must keep the zip files as no onde support it.

---------- Post added at 15:01 ---------- Previous post was at 14:56 ----------

Also, there is a difference in first party support vs open source third party. Tour friend phone is mente to have stock lolipop from motorola, by that, you van always unbrick. Lineage is a comunity extension, not a product that you adquire. In last resorce you can get the source in github and compile tour own if you cant find a compiled zip
[Moto G 4G Android Development] IronTechmonkey:
Your desires are reasonable but your understanding of how such a communal effort goes is poor (and seemingly unteachable because you, at the expense of reason, are concerned only with what you want). Your insulting tone certainly does not make the ignorance and subsequent unreasonable expectations any more palatable.

As a guest in someone's home where you are fed at no expense to you and with no contribution from you for long after others have stopped feeding you, you complain about the food and service.

:|
[Moto G 4G Android Development] macmobile:
And I tell you: this is the big majority of people who download these kind of Roms, lol. In the end it's easy: Does Lineage OS want to serve these kind of people any better or not? If so, would it take a lot of effort? I don't think so.
[Moto G 4G Android Development] Libor1:
I still have the last LOS zip from February, can upload it, if that save your Moto G4G just let me know.

Odoslané z Redmi Note 3 pomocou Tapatalku
[Moto G 4G Android Development] IronTechmonkey:
What you want has passed (reasonably so) and now you are cr@pping all over a recent offering that is pretty special for a device this old. Please stop disrupting this thread, the point of which is development, which we rather amazingly recently had some of. There are other where you can grouse where it is actually on topic.

Bumping the latest available un official build: https://xdaforums.com/moto-g/4g-development/rom-cyanogenmod-14-0-t3469103/post79357003
[Moto G 4G Android Development] Pupet_Master:
People who want to be sure and support, or the pnes who dont know that they are doing (such as the ones who dont nanobackup or keep the ROM zip files stored) should stick to stock.

Any custom ROM is experimental and not oficial. The last Lineage was from febuary, se are almost in June. Ofcourse it wont be avaliable anymore. But then again, se have lineage pie and ppl who upload backups. In the end it took more research for you, but you managed to restore yournfriend phone.

I dont get the big deal, none of those ROMs are oficial, people should know that they are doing and runing in to before update.

Opensource work like that, its not a close source hardware that need to be noob friendly. Opensource is for the ones who unserstand that it will only be suported if maintainers still have the phone and wjen they dont, the servers will be alocated to something else. They dont have the money to keep it up on a dead device for only a few people
[Moto G 4G Android Development] macmobile:
I'm sorry, this topic got that much attention. Let's hope there's a little something for everybody to learn from this. Let's move on then! [emoji6]
[Moto G 4G Android Development] sdembiske:
For those of you wishing to update to the May '19 Security Patches, I've uploaded one of my unofficial builds that is based off the official build files with the security patches added.

A clean flash will have to be done when going from an official build to an unofficial build - in TWRP wipe Cache, Dalvik cache, System and importantly

format

Data > Yes before flashing the appropriate Open Gapps. Do a nandroid backup first, including your data - copy any data/media files (e.g., photos, videos etc.), on your SD card over to your PC. If you're coming from the April update I uploaded previously, you can do a dirty flash (wipe Cache, Dalvik cache & System), re-install Open Gapps, preferred root & Xposed (if required).

Download Link for lineage-14.1-20190505-UNOFFICIAL-peregrine.zip: https://mega.nz/#!sexF1AZK!t-jEta1EpkPJFVhY42ddPy-hUhrR_QslSNcWS4RQ08o

I do, however, recommend you learn to build it yourselves: refer to post # 1210 for the full build instructions.
[Moto G 4G Android Development] pigeons9:
Have been using this, thank you! Just curious, is this almost the same as the last official build from February besides the security patch? I assume LOS has left the peregrine code on their repos for now, is it still possible they may eventually remove it?
[Moto G 4G Android Development] sdembiske:
It's exactly the same except for the unofficial build title and the later updates added by LOS or added & committed from AOSP, undergoing a code review and verification process in LineageOS Gerrit before being put out for building. The only changes would be whatever 14.1 commitments have been made by either the LOS team or those added as part of the AOSP update process. I know the security patches are still being updated and added to LOS a bit later (the reason I know this, is that if one manually puts in the security patches (rather than repopicking the patch topic before it's pushed out) and then they are later pushed through after review and verification in LineageOS Gerrit, the ones added beforehand manually have to be removed and the build re-synced before re-building, so it's important to check the security update date after re-syncing, before manually updating the patches - by the middle of the month or so, the security updates should have been pushed through, so, ... at this stage, no reason to rush manually updating the security patches until one is sure they are no longer being pushed through). It's possible I guess that the Peregrine code could be removed eventually, but I don't think it's something to worry about at this stage. You can still build for many devices that are older - perhaps only the security patches are no longer being pushed through for those builds but haven't confirmed this.
[Moto G 4G Android Development] mukisa emma:
Good
[Moto G 4G Android Development] sdembiske:
For those of you wishing to update to the JUNE '19 Security Patches, I've uploaded one of my unofficial builds that is based off the official build files with the latest security patches added (refer to post # 1243 for further elucidation).

Note

: A clean flash will have to be done when going from an official build to an unofficial build - in TWRP wipe Cache, Dalvik cache, System and importantly format Data > Yes before flashing the appropriate Open Gapps. Do a nandroid backup first, including your data - copy any data/media files (e.g., photos, videos etc.), on your SD card over to your PC. If you're coming from the April or May updates I uploaded previously, you can do a dirty flash (wipe Cache, Dalvik cache & System), re-install Open Gapps, preferred root & Xposed (if required).

Download Link for lineage-14.1-20190605-UNOFFICIAL-peregrine.zip:

https://mega.nz/#!5fwUQArL!zTm34wUJBljRu1LALe-3mkn6qkcZlRYUoXLrJPx69e4

I do, however, recommend you learn to build it yourselves: refer to post # 1210 for the full build instructions.

* While a LOS 16.0 (Pie) build is available now that is operational (forget the LOS 15.1 build that's available, it's definitely not ready whatsoever in my opinion for prime time), there are some issues that can prevent one from using it as a Daily driver, IMO. Namely, it's is not being consistently worked on nor updated (including security patches that have been pushed through but have not been synced-in and the rom re-built) by the developer and there is a significant issue with notifications being inconsistent, failing to actually get pushed through at times. Not encouraging if you need or want to know when you have a text message ...
[Moto G 4G Android Development] Mitsch79:
Hi Guys,

Is there still someone out there using peregrine?

If so, maybe you could test our build and report back wether it's working or not. I actually don't own the phone but wanted to give my mother-in-laws phone the latest security updates.

The rom ist OTA-enabled and hostet here: https://los-legacy.de/peregrine/lineage-14.1-20190629-UNOFFICIAL-peregrine.zip

So in case there is a new build you will be able to update using the updater app as usual.

Just a hint for people moving from an official to an unofficial build, there are some howtos floating around on how to do this without the need to wipe everything.

Cheerz

Mitsch (www.los-legacy.de)
[Moto G 4G Android Development] wagmic:
Thanks i still have my moto g when i travel ans with Guy like You it work like a charm

I il test it
[Moto G 4G Android Development] sdembiske:
For those of you wishing to update to the JULY '19 Security Patches, I've uploaded one of my unofficial builds that is based off the official build files with the latest security patches added (refer to post # 1243 for further elucidation).

Note

: A full clean flash will have to be done when going from an official build to an unofficial build - in TWRP wipe Cache, Dalvik cache, System and importantly format Data > Yes before flashing the appropriate Open Gapps. Do a nandroid backup first, including your data - copy any data/media files (e.g., photos, videos etc.), on your SD card over to your PC. If you're coming from one of the unofficial updates I uploaded previously, I recommend you do a regular clean flash (wipe Cache, Dalvik cache & System), re-install Open Gapps, preferred root & Xposed (if required).

Download Link for lineage-14.1-20190705-UNOFFICIAL-peregrine.zip:

https://mega.nz/#!5Cx1BSKb!aZ7yYgsnaaA-KdH9_Dgp4th2UPStBUAFU7Sxu-8fLNc

Important

: After you flash this new build, unpair all your BT devices (headsets, keyboards, etc.) and try to pair them again.

I do, however, continue to recommend you learn to build it yourselves: refer to post # 1210 for the full build instructions.
[Moto G 4G Android Development] pigeons9:
Yes, they are some of us still using this phone ;) I just installed your build with latest TWRP. Format, wipe, no issues. Everything seems fine! All basic things work, F-Droid installed successfully. Still unable to enable encryption. This is ok, I assume this wont work on unofficial builds. Thank you for this :good:
[Moto G 4G Android Development] Mitsch79:
Thx a lot for your Feedback :)

As soon as the latest security patches have been merged to the sources i will build again. The new build will then be available via OTA update.

Cheerz
[Moto G 4G Android Development] Mitsch79:
Hey there, the ota update incl. the latest patches is available for download. In case you're already using my build you can simply use the updater app that's included with LineageOS. Otherwise you might want to download it from www.los-legacy.de.

Cheerz

Mitsch
[Moto G 4G Android Development] pigeons9:
Tried it out, OTA worked just fine :)

Thanks!
[Moto G 4G Android Development] phgurgel:
I am using it too. My bff phone. I'm using lineage 14 pretending to upgrade. But I need time to install latest twrp. PLEASE Co tinue the awesome work on my phone. Gratz for you time ppl.

Enviado de meu SM-J530G usando o Tapatalk
[Moto G 4G Android Development] rektal:
Thank you for keeping peregrine alive.

I am going to try this ROM. What should I wipe when I am on original LineageOS with January security patch?

Could you give me a hint?
[Moto G 4G Android Development] Mitsch79:
Cache and Dalvik Cache should be fine.

You should flash this one first https://androidfilehost.com/?fid=962187416754465877

This replaces the official certificates with the unofficials (test keys). Do not reboot after flashing this zip of you're data will become corrupted. Flash the rom afterwards.

Here's some more info about migrating between official and unofficial: https://wiki.lineageos.org/signing_b...-or-vice-versa

And as always, make a Backup before changing anything.

Cheerz
[Moto G 4G Android Development] Brotherofsun:
The correct link:

https://wiki.lineageos.org/signing_builds.html#test-keys-to-your-own-release-keys-or-vice-versa
[Moto G 4G Android Development] rektal:
Everything went smoothly. Peregrine works fine. Trebuchet launcher doesn't show my all apps. I don't know why? I use CPL launcher so it doesn't bother me. Great work.
[Moto G 4G Android Development] Paule_Phone:
Hi,

Where can I find this Information?

Many thanks in advance
[Moto G 4G Android Development] Mogster2K:
Scroll up to post #1255.
[Moto G 4G Android Development] Paule_Phone:
Thanks for the hind, but much more THANKS to Mitsch79 for providing a working ROM.

IMHO the work of Mitsch79 deserve a separate Thread and should explain the steps how to from official to unofficial better for nobs.

I was able to recover my MotoG from Boot loop -> too working, lost all private data because I'am unable to think enough forehand.

I would wish that we can prevent this for others through better documentation.

Thanks to all

Thomas
[Moto G 4G Android Development] IronTechmonkey:
Threads such as this are typically focused on the development the ROM rather than the particulars of the perquisites except perhaps to indicate what those prerequisites are. If I recall correctly I found those prerequisite instructions with the material regarding unlocking the bootloader rather than the ROM specific stuff.

That being said, for a mature device that has slipped of the list of officially supported LOS devices and received some unofficial development attention it makes sense to re-consolidate any instructions, but that is up to us rather than the creator of this thread.

To that end: One thing that is often done and has most likley been done previously in this thread (and just about any OS ROM thread) is that users such as us may post such instructions. If none can be found by searching the thread you could document what you did in - which in turn would be helpful to others. I'd be interested in learning about anything that you had to do that was not already documented (albeit in a scattered way).
[Moto G 4G Android Development] Paule_Phone:
I have no chance to do a decent documentation from Official LOS to unofficial LOS, because my Phone was soft broken before I tried something. The Phone was running TWRP and official LOS, I didn't know that I would be unable to access the internal SD card after flashing the unofficial ROM, therefore my saved data was lost. To make it clear I'm not blaming anybody here, it was my fault not studying enough beforehand.
[Moto G 4G Android Development] _that:
You could just have restored your backup. :confused:
[Moto G 4G Android Development] Mogster2K:
Is it enough to run the build using "brunch peregrine"? Is there any patching to be done? I made a successful build, but I don't know how to integrate security patches etc.
[Moto G 4G Android Development] sdembiske:
Congratulations on undertaking to build it yourself.

You can check the security patch date before you run 'brunch peregrine' in this folder and file:

/build/core/version_defaults.mk

- Open and scroll down through the version_defaults file (it's the bottom file in the build/core folder), until you see: PLATFORM_SECURITY_PATCH :=

The security patches are still being committed, i.e., pushed through (you just need to run the "repo sync" command for them to be synced in), so there is no need to manually update the security patches at this stage. Eventually they may not be pushed through, but I suspect at this point they will continue to be for some time. By the middle of the following month, the security patches should have been pushed through. You can check beforehand if they have been committed in the LineageOS Gerrit web site. As far as learning how to add the security patches yourself, I referred to where to get the how-to information in post # 1210.

Just to be clear though, the 'brunch peregrine' is where you actually build the rom. Until that process completes successfully, you haven't built it, you've just mixed all the ingredients in the bowl, so to speak.
[Moto G 4G Android Development] Mogster2K:
When you say "internal SD card", do you mean the emulated card, or an SD card formatted as internal/adopted storage?
[Moto G 4G Android Development] florstat:
Is it possible to verify if latest February rom linked in post #1224 is genuine?

Is this procedure the right one?

https://wiki.lineageos.org/verifying-builds.html
[Moto G 4G Android Development] _that:
That link looks right. However be aware of CVE-2019-1986, CVE-2019-1987, and CVE-2019-1988. Better use a later unofficial build with more fixes.
[Moto G 4G Android Development] florstat:
Ok. I built a 14.1 not more than three weeks ago ( not flashed yet ) but I' m thinking about installing latest official because someone in previous posts wrote that unofficial builds have problems with encryption.

Apart from that, do I have to worry about new bugs with my own build/ new security patches?