[Q] Latest MM Rom With Security Patches - Nexus 6P Q&A, Help & Troubleshooting

Hi All. Right, basically I don't know if this is the right place to post this but I'm looking for an up-to-date Marshmallow ROM with maybe the latest security patches installed. I've tried building RR with success but no SIM detected and my limited knowledge of Linux and building I cannot fix the issue. I'm looking somewhere along the lines of Lineage OS 13 or RR and at a push, AOSP.
If anyone can help or point me in the right direction then that would be extremely helpful as there are some very talented people here!
Thanks for your help guys!!

The last version of RR for 6.0.1 from 12/16 is still available...
https://forum.xda-developers.com/nexus-6p/development/rom-resurrection-remix-t3408504
... which I believe has the latest MM security patch from 9/16 (MTC20L).

redduc900 said:
The last version of RR for 6.0.1 from 12/16 is still available...
https://forum.xda-developers.com/nexus-6p/development/rom-resurrection-remix-t3408504
... which I believe has the latest MM security patch from 9/16 (MTC20L).
Click to expand...
Click to collapse
Thank you for the info. I'll take a look as I do like RR a lot

Related

Need help.

Hi i'm minicm.
Hi guys, I have a question.
There is still some rom that is 6.0 or 7.0 (not 7.1) that has the security patch before March 2017, probably you ask yourself What for? It's because from the patch of March the simulated Locations no longer work and it helps me a lot.
Someone still has one of these roms with patch February 2017 or earlier as a LineageOs 14 (7.0) Cm (6.0) or some other that meets these requirements although I already pored Omnirom, Pac-rom and did not convince me much.
If you still have them, could you host them and pass them to me? Please and thank you.
minicm94123 said:
Hi i'm minicm.
Hi guys, I have a question.
There is still some rom that is 6.0 or 7.0 (not 7.1) that has the security patch before March 2017, probably you ask yourself What for? It's because from the patch of March the simulated Locations no longer work and it helps me a lot.
Someone still has one of these roms with patch February 2017 or earlier as a LineageOs 14 (7.0) Cm (6.0) or some other that meets these requirements although I already pored Omnirom, Pac-rom and did not convince me much.
If you still have them, could you host them and pass them to me? Please and thank you.
Click to expand...
Click to collapse
Check my CyanogenMod 13, it has security patches from December 2016.
XTutorials said:
Check my CyanogenMod 13, it has security patches from December 2016.
Click to expand...
Click to collapse
HAHA,lol thanks, i will try it, and there's no a LOS14.0 with those security patchs?
I'm going to try the Cm13.
minicm94123 said:
HAHA,lol thanks, i will try it, and there's no a LOS14.0 with those security patchs?
I'm going to try the Cm13.
Click to expand...
Click to collapse
No, there is no los 14.0 with old security patches.

No fingerprint after December modem update

Hello everyone, I'm on pocaropa's Oreo MIUI 10 port after downgrading from 10.0.3 Pie to April firmware. If I flash April to November Modem I have fingerprints but no signal (despite to have or not a valid IMEI number), If I flash 10.0.2 or 10.0.3 Modem (PIE) I have signal but no fingerprints. On stock Android pie 10.0.3 I have fingerprints and signal. I want to stay on MIUI, do anyone have any hints of what's going on?
Thanks.
whats going on is you putting diesel in petrol engine
.:Addicted:. said:
whats going on is you putting diesel in petrol engine
Click to expand...
Click to collapse
Serious replies please. Thanks.
Shouldn't you be asking this in the ROM's thread?
manpildo said:
Shouldn't you be asking this in the ROM's thread?
Click to expand...
Click to collapse
Already done that, I posted here too because someone might have the same problem with other ROM. Thanks for the advice
I can confirm that the problem occurs in any other ROMs. I've read a comment from @joeyhuab about PIE updated blobs present in Pixel Experience and LOS 16.0 by @flex1911 ROMs. Now the question is, can we port those blobs to custom ROMs based on OREO? Something in the December and January firmware is preventing the fingerprint sensor to work on OREO based firmwares.

7.1.1 stock rom?

So I was making my own debloated stock Nougat and found a 7.1.1 full firmware, anyone tried it?
It is XT1680_POTTER_7.1.1_NPN25.137-92_cid50_subsidy-LATAM_regulatory-DEFAULT_CFC.xml.zip
That's not the latest Nougat full rom, there are others here:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
The latest nougat at that link is the NPNS25.137-92-14 one. However, you could also pop over to my TWRP Flashable Nougat stock rom thread and grab the latest latest one there, NPNS25.137-93-18 (August 2018 security patch) and debloat from there.
https://forum.xda-developers.com/g5-plus/development/twrp-flashable-stock-builds-t3813351
NZedPred said:
That's not the latest Nougat full rom, there are others here:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
The latest nougat at that link is the NPNS25.137-92-14 one. However, you could also pop over to my TWRP Flashable Nougat stock rom thread and grab the latest latest one there, NPNS25.137-93-18 (August 2018 security patch) and debloat from there.
https://forum.xda-developers.com/g5-plus/development/twrp-flashable-stock-builds-t3813351
Click to expand...
Click to collapse
I know it isn't the latest, I'm using November security patch because after that HAL3 is broken, if you enable it then Moto Camera breaks, same happens for cedric. I was just asking if potter really has available 7.1.1 stock because I never saw it, maybe the name is just wrong and it's 7.0
Fedray said:
I know it isn't the latest, I'm using November security patch because after that HAL3 is broken, if you enable it then Moto Camera breaks, same happens for cedric. I was just asking if potter really has available 7.1.1 stock because I never saw it, maybe the name is just wrong and it's 7.0
Click to expand...
Click to collapse
Oh, gotcha, was a bit presumptuous there wasn't I.
I never knew of 7.1.1 either, so I guess the best way to check is to download it and either extract the build prop or flash it.
NZedPred said:
Oh, gotcha, was a bit presumptuous there wasn't I.
I never knew of 7.1.1 either, so I guess the best way to check is to download it and either extract the build prop or flash it.
Click to expand...
Click to collapse
You damn right, thanks for the idea!
Fedray said:
You damn right, thanks for the idea!
Click to expand...
Click to collapse
There has never been a 7.1.1 stock firmware for potter, that's a fact. So it must be a wrong name, wrong firmware or something like that.
The 7.0 builds ending on 92-x are for the US, the ones ending on 93-x are for Europe and the rest.
As posted above there are TWRP flashable builds of the latest available versions.
@thuanprs23: This is an English speaking forum so please post in English, use Google translator if needed. You're free to post in your home language as long an English translation is posted too.
Sent from my Moto G5 Plus using XDA Labs

[GUIDE] Fix fingerprint

Because many users are repeatedly asking this and everyone needs to answer again and again, I write it up here:
This is only true for Oreo and later Custom ROMs! For nougat refer to post #3 by @TheFixItMan (thanks for the tip that users still use nougat )
You can choose between this ways (doing both is wasted time!)
- Have stock Oreo installed before flashing your ROM (for most users not an option because they already have the issue)
- Flash https://github.com/nift4/nift4.github.io/releases/tag/cedric-fp-fix over your existing custom ROM
Yes, it's so easy
do you have the fix for Lineage os 14.1, i tried this ine didn't work for me. :s
Pedro_r said:
do you have the fix for Lineage os 14.1, i tried this ine didn't work for me. :s
Click to expand...
Click to collapse
Download stock nougat firmware and flash just the following two parts
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
For fingerprint to work you need to have a base stock firmware that matches the base of the rom you are using - so in the case of lineage 14.1 that is nougat
The zip file in the op contains oero files so is for people who never bothered flashing oero firmware when they flashed an oero based custom rom
OP should explain what the zip file does (flashes the two files I've mentioned but from oero firmware) to help people understand the issue
TheFixItMan said:
Download stock nougat firmware and flash just the following two parts
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
For fingerprint to work you need to have a base stock firmware that matches the base of the rom you are using - so in the case of lineage 14.1 that is nougat
The zip file in the op contains oero files so is for people who never bothered flashing oero firmware when they flashed an oero based custom rom
OP should explain what the zip file does (flashes the two files I've mentioned but from oero firmware) to help people understand the issue
Click to expand...
Click to collapse
I explain, thanks for the tip
Hi,
I have a motog5 xt1676.
I was on Nougat and I updated to Carbon Rom (after trying with lineage 17, same issue) and i have to choices:
-Doing nothing and people can hear me when i am in speakerphone but the fingerprint doesn't work.
-I patch with the first link for orea then the fingerprint work but people can't hear me when i'm in speakerphone.
Patching with nougat files does nothing...
Is there a way to edit the fix or to make a fix myself avoiding the speaker issue ?
I though to change build.prop or a way to change the way sound is mixed during call but i did'nt test changing all lines.
Do you have an other idea ?
A fix for pie ? ( Carbon is Pie when Pie is cooked too much time =D )
Thank you,
Pierre Archer
The ROM: CARBON-CR-7.0-OPAL-RELEASE-cedric-20200920-0426
piecraxe said:
Hi,
I have a motog5 xt1676.
I was on Nougat and I updated to Carbon Rom (after trying with lineage 17, same issue) and i have to choices:
-Doing nothing and people can hear me when i am in speakerphone but the fingerprint doesn't work.
-I patch with the first link for orea then the fingerprint work but people can't hear me when i'm in speakerphone.
Patching with nougat files does nothing...
Is there a way to edit the fix or to make a fix myself avoiding the speaker issue ?
I though to change build.prop or a way to change the way sound is mixed during call but i did'nt test changing all lines.
Do you have an other idea ?
A fix for pie ? ( Carbon is Pie when Pie is cooked too much time =D )
Thank you,
Pierre Archer
The ROM: CARBON-CR-7.0-OPAL-RELEASE-cedric-20200920-0426
Click to expand...
Click to collapse
As explained
If your stock rom firmware is nougat I suggest updating it to oreo to use pie custom rom
Read my post above (post number three) for full explaination
Any other issues is probably a rom issue - I don't even think carbon rom is actively supported for this device. Use lineageos/Mint os from dev section
TheFixItMan said:
As explained
If your stock rom firmware is nougat I suggest updating it to oreo to use pie custom rom
Read my post above (post number three) for full explaination
Any other issues is probably a rom issue - I don't even think carbon rom is actively supported for this device. Use lineageos/Mint os from dev section
Click to expand...
Click to collapse
Thank you !
Sorry, I midunderstood, I understand better now.
Then installing oreo stock ROM add more "compatibility files" to link with a pie ROM from nougat.
Lineage os is not officially supported on motog5 device, thats why i looked for carbon. But the unofficial lineage os for motog5 look like as frequently updated as "official" carbon rom. I dont know if Carbon updates are caring of hardware details and if they are released without real adaptation. Lineage os pay probably more attention to hardware because motog5 is not officially supported by lineage... Idk...
Thank you,
Pierre Archer
piecraxe said:
Thank you !
Sorry, I midunderstood, I understand better now.
Then installing oreo stock ROM add more "compatibility files" to link with a pie ROM from nougat.
Lineage os is not officially supported on motog5 device, thats why i looked for carbon. But the unofficial lineage os for motog5 look like as frequently updated as "official" carbon rom. I dont know if Carbon updates are caring of hardware details and if they are released without real adaptation. Lineage os pay probably more attention to hardware because motog5 is not officially supported by lineage... Idk...
Thank you,
Pierre Archer
Click to expand...
Click to collapse
Don't be concerned too much about the terms official and unofficial
Nearly all lineageos roms will start off as unofficial - it's users who build it. It's only when they are submitted to lineageos and they add it to their build server it becomes official but its the same device tree.
The only reason the lineage os rom has not been made official is because the camera is not fully working like it is in stock rom so it doesn't meet the criteria to be submitted

The Osprey Oracle

The Osprey Oracle​
It's been a while.
If you don't know me, I was active here a few years ago and created the FAQ thread.
I got out of the community for a while but I'm amazed at how strong the osprey development still is, so I plan to Frankenstein my model up to a 16GB/2GB and get back into it. So in that spirit, I want to go back to my RC roots and create a thread for everyone with the most up-to-date info to help keep this device alive.
I've called it the Osprey Oracle as it's more catchy than Moto G 2015 Oracle, but Merlin stuff will be here too.
My general philosophy in compiling this is to create a database of currently maintained or at least recent development, to enable users to find a ROM that is secure and supported. This means, more specifically, ROMs which are still being updated with the latest security patches; this is why you'll find some older versions such as Nougat in this list, because some very generous members are still compiling them with these patches. That means lots of things will be missing, however; if you disagree and would like a fuller, more historical database, let me know.
GUIDES:
To learn how to unlock bootloader, root, etc., I'll point you first towards my own FAQ Thread as it's all in there
For repairs, check out ifixit; eBay is the best place to buy parts
RECOVERIES:
Official TWRP 3.x.x-x for osprey
Unofficial TWRP 3.x.x-x for osprey/merlin with support for separate vendor partition
Unofficial red themed TWRP 3.x.x-x for osprey
ROMS:
Android Q
Official LinageOS 17.1 for osprey
Official crDroid 6.x for osprey
Unofficial LineageOS 17.1 for merlin
Official MalluOS 1.x for osprey
Unofficial MalluOS 1.x for merlin
Unofficial FlokoRom v 3.0 for osprey
Pie
Unofficial LineageOS 16.0, hardened w/ microG or just security patches
Unofficial LineageOS 16.0 for osprey
Official Resurrection Remix 7.0.2 for osprey
Official crDroid 5.x for osprey
Unofficial Resurrection Remix 7.0.2 for merlin
Everything below is no longer updated but kept for reference:
Oreo
Unofficial LineageOS 15.1
Nougat
Unofficial LineageOS 14.1, hardened w/ microG or just security patches
Unofficial LineageOS 14.1
Non-Android
Sailfish OS for Osprey
Stock (Lollipop - Marshmallow)
Motorola ROM Collection
Thank you very much for your thread.!!!
It is what I was looking for. I am trying to make quicker a relative´s Moto G 2015 and your thread has been very useful.
Warm greetings.
Good list but can you include the 14.1 stock images
I think under Nougat you should also include the link to the Stock 14.1 LinageOS + patches. Not everyone is concerned about Google and replacing them with microG.
Personally I've found sticking with Android 7.1 is best with this model of phone. Everything works out of the box, and it doesn't slow down.
Thread: https://forum.xda-developers.com/2015-moto-g/orig-development/rom-unofficial-cyanogenmod-14-t3466246
JohnSmithXT885 said:
I think under Nougat you should also include the link to the Stock 14.1 LinageOS + patches. Not everyone is concerned about Google and replacing them with microG.
Personally I've found sticking with Android 7.1 is best with this model of phone. Everything works out of the box, and it doesn't slow down.
Thread: https://forum.xda-developers.com/2015-moto-g/orig-development/rom-unofficial-cyanogenmod-14-t3466246
Click to expand...
Click to collapse
Just added, didn't realise anybody was still building it with the latest patches. fyi MSe1969's microG build simply provides the option of using microG if you want, you still have the choice to then actually install the microG apps or just flash GApps as normal.
Interesting, I've been very happy on Android 10.0 but as I don't use GApps that's a significant resource reduction before any other apps are installed, of which I don't have many. Recently upgraded my Osprey to the 2GB RAM version as well, which helps.
It's great we have so many options though, all the way from 7.1 - 10! Which is what I hope this thread will show and help members with.
Is Lineage OS 17.1 official now? I can see it on the Lineage OS website.
contructor0 said:
Is Lineage OS 17.1 official now? I can see it on the Lineage OS website.
Click to expand...
Click to collapse
Oh yeah it is! Thanks for reminding me, will update the list
Hey all, a chance for opinions if anyone has any before I go ahead:
In terms of Pie ROMs, LineageOS 16 (as well as the hardened micro G version) and Resurrection Remix 7 are no longer updated. The former is a few months old but the latter getting on for a year. So not terrible in terms of security updates compared to an OEM, but given that TheForce is still maintaining a crDroid Pie ROM would people be happy with me going ahead and removing LineageOS and Resurrectiong Remix from the list? Other option is to add a 'Pie' heading to the 'no longer updated' list I've added to the bottom? I want the main point to be that you can see secure and updated ROMs easily at the top but I understand people are interested in tinkering so might want them there for archival purposes.
That aside, just added FlokoRom, another one TheForce is maintaining, and MalluOS. Decent smattering of 5 up-to-date Android 10 ROMs for the Moto G3 now! Pretty amazing.
HTCDreamOn said:
Hey all, a chance for opinions if anyone has any before I go ahead:
..
would people be happy with me going ahead and removing LineageOS and Resurrectiong Remix from the list? Other option is to add a 'Pie' heading to the 'no longer updated' list I've added to the bottom? I want the main point to be that you can see secure and updated ROMs easily at the top but I understand people are interested in tinkering so might want them there for archival purposes.
Click to expand...
Click to collapse
I think it would be nice to keep old roms listed, for historical reasons.
In my case, I'm still on resurrection remix 5.7.4 (MM 6.0.1) with squid kernel 23. It's running nicely, and I'm still reluctant to upgrade it because I'm afraid of losing some functionality (camera and viper4Android both are doing great in this Rom and kernel)
Thanks for maintaining this list. I'd like it to also include a list of kernels
Cheers
gg2001 said:
I think it would be nice to keep old roms listed, for historical reasons.
In my case, I'm still on resurrection remix 5.7.4 (MM 6.0.1) with squid kernel 23. It's running nicely, and I'm still reluctant to upgrade it because I'm afraid of losing some functionality (camera and viper4Android both are doing great in this Rom and kernel)
Thanks for maintaining this list. I'd like it to also include a list of kernels
Cheers
Click to expand...
Click to collapse
Hmmm I'll think about kernels, main reason I hadn't is because there aren't any still maintained, and none for ROMs post Oreo afaik. Would go against the ethos of the list and I don't want to get into just making a massive archive, when you get the same effect searching "kernel" in the dev forums. Whereas with ROMs it can be tricky for new users to differentiate which are currently maintained, getting security updates etc.
HTCDreamOn said:
Hmmm I'll think about kernels, main reason I hadn't is because there aren't any still maintained, and none for ROMs post Oreo afaik. Would go against the ethos of the list and I don't want to get into just making a massive archive, when you get the same effect searching "kernel" in the dev forums. Whereas with ROMs it can be tricky for new users to differentiate which are currently maintained, getting security updates etc.
Click to expand...
Click to collapse
Isn't smartpack kernel currently maintained? (by someone in the Brazilian osprey group in telegram. It's currently in version 12.1 iirc and it's for Oreo, Pie and Q)
I understand that mixing kernel list here may be a little excessive, specially when most of them are abandoned.. but then it took me some time to get to smartpack kernel, because in xda it appears as abandoned, but it's currently maintained.
HTCDreamOn said:
so I plan to Frankenstein my model up to a 16GB/2GB and get back into it.
Click to expand...
Click to collapse
May I ask how you're going to do that? I've been interested in doing that for a long time, I have a 16GB/1GB version and I'd love to upgrade to a 16GB/2GB SoC.
AhReLocazo said:
May I ask how you're going to do that? I've been interested in doing that for a long time, I have a 16GB/1GB version and I'd love to upgrade to a 16GB/2GB SoC.
Click to expand...
Click to collapse
I just bought a 16GB/2GB osprey with a smashed screen (so v cheap) and swapped the motherboard. I suppose rather than upgrading it, I replaced the phone itself and performed a screen repair... depends how you want to look at it aha. It's a very easy phone to take apart though, just be careful with your plectrum when you pry the screen off because if you do it too quickly you can end up with bright spots / dead pixels where you've accidentally pulled the exterior glass away from the LCD. A soldering iron makes a good pseudo-heat-gun if you don't have one of those to melt the screen glue.
HTCDreamOn said:
I just bought a 16GB/2GB osprey with a smashed screen (so v cheap) and swapped the motherboard. I suppose rather than upgrading it, I replaced the phone itself and performed a screen repair... depends how you want to look at it aha. It's a very easy phone to take apart though, just be careful with your plectrum when you pry the screen off because if you do it too quickly you can end up with bright spots / dead pixels where you've accidentally pulled the exterior glass away from the LCD. A soldering iron makes a good pseudo-heat-gun if you don't have one of those to melt the screen glue.
Click to expand...
Click to collapse
Oh I didn't think about a mobo replacement, easier than a SoC replacement I was thinking hahaha
The G3 wasn't sold by carriers where I live so it would be pretty difficult to find a 2GB/16GB model. I guess I'll try ebay or similar.
Regarding the bright spots, for some reason mine has some even though it wasn't taken apart.
I'll try doing the same as you, wish me luck finding a donor device hahaha
Thanks for the reply!
Can you add these MERLIN ROMs to the list -
Project Sakura 2.Q (support is dropped now but its just a month old)
link - https://sourceforge.net/projects/projectsakura/files/merlin/
https://projectsakura.xyz/download.html
MalluOS 1.3 Chicken
link - https://forum.xda-developers.com/2015-moto-g/development/rom-malluos-1-3-chicken-t4162203
CrDroid v6.9 ( there is no xda thread )
link - https://androidfilehost.com/?fid=8889791610682922059
Charlie-117 said:
Can you add these MERLIN ROMs to the list -
Project Sakura 2.Q (support is dropped now but its just a month old)
link - https://sourceforge.net/projects/projectsakura/files/merlin/
https://projectsakura.xyz/download.html
MalluOS 1.3 Chicken
link - https://forum.xda-developers.com/2015-moto-g/development/rom-malluos-1-3-chicken-t4162203
CrDroid v6.9 ( there is no xda thread )
link - https://androidfilehost.com/?fid=8889791610682922059
Click to expand...
Click to collapse
Thanks, I'm not adding Project Sakura because I won't list ROMs that get 1 release and no further development. I think I'll give crDroid a miss also as there is no thread.
I'll add MalluOS though, thanks.
HTCDreamOn said:
Thanks, I'm not adding Project Sakura because I won't list ROMs that get 1 release and no further development. I think I'll give crDroid a miss also as there is no thread.
I'll add MalluOS though, thanks.
Click to expand...
Click to collapse
Understandable , also about Project Sakura the maintainer (me) dropped it because the Gapps survival script wasn't working while dirty flashing , users would have to wipe system partition completely and then re-flash the Rom and Gapps package or the device would bootloop. To make sure nobody loses their data I chose to drop official support the last OTA wasn't pushed either. OTA updates might have worked but then i wouldn't be able to test the Rom first myself for errors (by dirty flashing).
Thank you.
Edit: I don't want you to include the link but just wanted to tell you why the development was dropped.

Categories

Resources