I patched the kernel for 7.1.1 on Qualcomm Moto E4 Plus. This is useful to get Magisk fully working with modules and settings that can be saved.
I compiled the fix from the released kernel source: MMI-NPR26.58-25
Here are the unsigned boot.img and zImage, use whichever one suits your fancy to patch the kernel.
Download boot.img
Download zImage
Edit: I've uploaded a build for the regular Qualcomm Moto E4 here.
Installation:
You should backup your Boot in TWRP before installing, that way you can restore if something goes wrong.
If you have Magisk installed, you'll want to patch the boot.img using Magisk Manager. Just tap install, and patch boot rom image. Then copy the patched file back to your computer to flash it.
Easiest way is to flash the boot.img while in fastboot:
Code:
>fastboot flash boot /path/to/downloaded/boot.img
Did not work, phone would not boot after flash, had to restore stock kernel.
TheJAYpoop said:
Did not work, phone would not boot after flash, had to restore stock kernel.
Click to expand...
Click to collapse
Hmm, having tried it myself, I see that without patching the image with magisk from inside magisk manager, it seems the rebuilt boot image does not work. But it does work after it's been patched in magisk, so you can try that.
Here's a link that's already been patched with Magisk 14.6 beta: https://drive.google.com/open?id=13vaUgq22fNnVnWqq5ai9kGC1KsO3ZEmJ
SeanStar said:
Hmm, having tried it myself, I see that without patching the image with magisk from inside magisk manager, it seems the rebuilt boot image does not work. But it does work after it's been patched in magisk, so you can try that.
Here's a link that's already been patched with Magisk 14.6 beta: https://drive.google.com/open?id=13vaUgq22fNnVnWqq5ai9kGC1KsO3ZEmJ
Click to expand...
Click to collapse
That worked perfectly, awesome!
TheJAYpoop said:
That worked perfectly, awesome!
Click to expand...
Click to collapse
Merry Christmas! Enjoy the full Magisk experience, it was really bothering me when I got this phone about half a week ago.
Nice, I was planning on doing this after Christmas. Saved me the trouble. Merry Christmas to you too! It worked fine just flashing the patched img with TWRP. Want to save me the trouble of doing one for the regular E⁴ also?
GetOffMyLawn&!+¢#{$ said:
Nice, I was planning on doing this after Christmas. Saved me the trouble. Merry Christmas to you too! It worked fine just flashing the patched img with TWRP. Want to save me the trouble of doing one for the regular E⁴ also?
Click to expand...
Click to collapse
If you point me to the kernel source you specifically want patched, I can make it. You'll have to test it for me though, as I don't own the regular E^4.
SeanStar said:
If you point me to the kernel source you specifically want patched, I can make it. You'll have to test it for me though, as I don't own the regular E^4.
Click to expand...
Click to collapse
That would be great. I'll pm you a link since I can't post links yet. I've been spending all my spare time trying to get data working properly on both devices. I have no problem testing it.
Sent from my Moto E (4) Plus using XDA Labs
Qualcomm Moto E4 f2fs fix for perry 7.1.1 (Built and patched from NCQ26.69-48 source) kernel boot image for anyone that wants it is linked below. Thanks to GetOffMyLawn&!+¢#{$ for testing. See the OP for installation instructions, and please remember to make backups of your stock Boot.
Download:
unsigned boot.img
zImage
SeanStar said:
Qualcomm Moto E4 f2fs fix for perry 7.1.1 (Built and patched from NCQ26.69-48 source) kernel boot image for anyone that wants it is linked below. Thanks to GetOffMyLawn&!+¢#{$ for testing. See the OP for installation instructions, and please remember to make backups of your stock Boot.
Download:
unsigned boot.img
zImage
Click to expand...
Click to collapse
Thank you very much for taking the time to do this! Especially today. Just to point out how I installed the kernel, I simply flashed it as an img with TWRP, flashed the no dmverity/forceencrypt zip, then flashed Magisk V15.0 that was just released. It stayed on the n/a screen a minute then bootlooped a couple times, but it eventually booted just fine, so be patient with it. I had the latest Boost firmware installed and Magisk v14.6 at the time. Enjoy!
Sent from my Moto E (4) Plus using XDA Labs
Thanks @SeanStar for the regular e4 boot.img. you rock bro. Works great. Tested, successful
@SeanStar would you mind uploading the source to your kernel, like maybe on a GitHub repo or something? I'm working with a friend who has the owens and I'm trying to see if we can get a more functioning Lineage 14.1 on here
jasonmerc said:
@SeanStar would you mind uploading the source to your kernel, like maybe on a GitHub repo or something? I'm working with a friend who has the owens and I'm trying to see if we can get a more functioning Lineage 14.1 on here
Click to expand...
Click to collapse
Though the kernel I am currently working on is slightly modified more than what is provided here, the OP only has the fix for the f2fs loopback issue, as described here: https://forum.xda-developers.com/showpost.php?p=70492947&postcount=8793
You can download the stock kernel build source from Motorola's own repository here: https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NPR26.58-25
Also, I admit that I'm currently in the process of porting Lineage 14.1 to this phone, but it may take more time than I had originally planned for. It's not a priority for me at the moment, especially considering how much I like the stock rom.
SeanStar said:
Though the kernel I am currently working on is slightly modified more than what is provided here, the OP only has the fix for the f2fs loopback issue, as described here: https://forum.xda-developers.com/showpost.php?p=70492947&postcount=8793
You can download the stock kernel build source from Motorola's own repository here: https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NPR26.58-25
Also, I admit that I'm currently in the process of porting Lineage 14.1 to this phone, but it may take more time than I had originally planned for. It's not a priority for me at the moment, especially considering how much I like the stock rom.
Click to expand...
Click to collapse
Well dang, I'm working on porting lineage 14.1 to this thing too. Maybe we should join forces.
And moto's source is in a zip file, I was hoping I could get one that was unzipped and in a github repo already, for easy syncing when trying to build Lineage 14.1
Thank you for your work. I agree that stock isn't too bad with root magisk and Xposed working fine. But lineage is pretty tasty! I will shoot you both a PM if I can assist in any way
@SeanStar check out these screenies everyone:
Sent from my Moto E (4) Plus using XDA Labs
GetOffMyLawn&!+¢#{$ said:
@SeanStar check out these screenies everyone:
Click to expand...
Click to collapse
I'm not sure if they're still doing updates for this phone from what I've heard, but if they do this would be very nice.
SeanStar said:
I'm not sure if they're still doing updates for this phone from what I've heard, but if they do this would be very nice.
Click to expand...
Click to collapse
That sucks to hear, but although I do actually like stock on this device, that's why I build custom ROMs. Budget Motorola's never get updated more then a few times. Hopefully it will get added for future devices and ones that don't get abandoned at least.
Sent from my Moto E (4) Plus using XDA Labs
SeanStar said:
Qualcomm Moto E4 f2fs fix for perry 7.1.1 (Built and patched from NCQ26.69-48 source) kernel boot image for anyone that wants it is linked below. Thanks to GetOffMyLawn&!+¢#{$ for testing. See the OP for installation instructions, and please remember to make backups of your stock Boot.
Download:
unsigned boot.img
zImage
Click to expand...
Click to collapse
Hey @SeanStar would it be possible for you to do this on the latest update for the kernel on the E4 Perry please?? The reason being is this one can't be used on the latest update of the firmware, it fails to boot all the way up.
EDIT: The latest is NCQ26.69-56
PimpMy5Ton said:
Hey @SeanStar would it be possible for you to do this on the latest update for the kernel on the E4 Perry please?? The reason being is this one can't be used on the latest update of the firmware, it fails to boot all the way up.
EDIT: The latest is NCQ26.69-56
Click to expand...
Click to collapse
Considering there is no kernel source for NCQ26.69-56 on MotorolaMobilityLLC github, you're SOL, there's no easy way to patch it without the source. Sorry bud.
EDIT: I wouldn't try to downgrade either, I'm sure they updated the baseband. You'll probably knockout your service if you even try.
Related
Team Win Recovery Project for d605
upstream source v2.6.3.0 build
Source
found no bugs in nandroid backup and restore
Only some false translated touch event issues at terminal emulator.
Install: flash the file in CWM:
Download zip file
Give more happiness to your tutorial!
Thanks good man,
We've waited a long time,
CWM is good,but TWRP......
Ty again.......
This is happening omg
Edit: waiting for some feedback before installing, someone PLEASE try installing paranoid android using this
It works good, but not solve Paranoid black screen problem.
Maydar said:
It works good, but not solve Paranoid black screen problem.
Click to expand...
Click to collapse
R.I.P.
Thanks for informations, happy that is working for you. I know, tutorial is a bit short
If you have CWM, then you just backup whole rom, and then youre good. That zip overwrites only recovery partition
RaawrItsTomi said:
This is happening omg
Edit: waiting for some feedback before installing, someone PLEASE try installing paranoid android using this
Click to expand...
Click to collapse
Nice work man! Thanks for this
Sent from my LG-D605 using CM11 V11
Good job, I think it would be great if you gave link to the source code you used to build it in the OP. I think it's required by Original Development section to include the source?
PA
TWPR is working perfectly whit pa
Do you plan to make an update to current version?
I can update it for you if you want. I don't have the device though so I need a good english talker to give me some info about the device.
EDIT: I ported latest TWRP for your device. Need someone who can test it and tell me if it's good. Do not worry worse it can happen is not boot. No hard-brick dangers.
Sorry for long silence everyone, now isnt need for update. So maybe latter or if someone find bugs in my build.
Can I install future builds by Varcain with this? Or I'd have to install the new CWM?
I think that it will work with new builds...
Sent from my LG-D605 using XDA Free mobile app
Does it (TWRP) have Loki integrated like CWM? If no then it won't work - unless you lokify the boot.img inside zip manually. I am switching to new release method and it also depends on recovery being able to Lokify the boot.img when needed.
Thanks, you need to patch that boot.img. I was thinking that every roms would be already patched before compresion.
Sent from my LG-D605 using XDA Free mobile app
I will be thankful for pushing code at github, so we can stay up to date. If you decide to not publish your updates, I can reinvent wheel and make some ugly hack, that do same work in TWRP.
Varcain said:
Does it (TWRP) have Loki integrated like CWM? If no then it won't work - unless you lokify the boot.img inside zip manually. I am switching to new release method and it also depends on recovery being able to Lokify the boot.img when needed.
Click to expand...
Click to collapse
I messed my building tree so badly, that i need start from scratch once more time. I made no changes to twrp source. Only few setting at BoardConfig.mk
but if its required, here it is: http://frame.jailbrake.cz/recovery.zip
Varcain said:
Good job, I think it would be great if you gave link to the source code you used to build it in the OP. I think it's required by Original Development section to include the source?
Click to expand...
Click to collapse
This is my version of TWRP built for the 2015 Moto X Play. It should work fine, but using it is a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery. To enter fastboot mode, turn off your device, hold PWR and VolDn for 3 seconds, then let go.
Differences between upstream TWRP and my fork:
My original green theme
No SuperSU
No TWRP app
No HTC Dumlock cruft
Updated pigz compressor (slightly faster and more tolerant of corruption)
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
To permanently flash it:
Code:
fastboot flash recovery twrp.img
The download is up on the downloads tab.
XDA:DevDB Information
TWRP, Tool/Utility for the Moto X Play
Contributors
vache, squid2
Source Code: https://github.com/sultanqasim/android_device_motorola_lux
Version Information
Status: Stable
Current Stable Version: 3.2.3-r1
Stable Release Date: 2018-08-16
Created 2015-09-05
Last Updated 2018-08-16
Reserved
2015-09-17 :
-Fix flashing custom zips
Gr8!!
Is this actually built for X Play? I know it sounds silly but there's no kernel source yet is there? Or do we not need that to build recovery?
Sent from my Vodafone Smart ultra 6 using Tapatalk
Yes it's build for X Play, based on G 2015 device tree. I'm using MSM8916 generic kernel from Motorola, modded by @squid2 (https://github.com/sultanqasim/android_kernel_motorola_msm8916)
Ahh that's great. Thanks for this my device should be delivered tomorrow so I'll be definitely using this.
We will still need kernel source for cm12 etc though surely?
Sent from my Vodafone Smart ultra 6 using Tapatalk
TWRP working fine here on XT1562
I'm making a stock TWRP Backup + some partition dump
Next move will be starting playing with CM12.1
ephumuris said:
Ahh that's great. Thanks for this my device should be delivered tomorrow so I'll be definitely using this.
We will still need kernel source for cm12 etc though surely?
Sent from my Vodafone Smart ultra 6 using Tapatalk
Click to expand...
Click to collapse
Yes i think we'll have to wait for kernel sources to get a working custom.
Already build one (SOKP) but cannot get it to boot (with stock kernel or msm8916 kernel)
Shreps said:
TWRP working fine here on XT1562
I'm making a stock TWRP Backup + some partition dump
Next move will be starting playing with CM12.1
Click to expand...
Click to collapse
can you please upload your dumps and backups if there are ready for it?
i have a broken XT1562 without a nandroid or other backups...
thanks
Thanks for this Vache! However, just to let you know this is still showing as Moto G 2015 when plugged into my PC whilst in recovery - not sure if that's normal or not?
skdubg said:
can you please upload your dumps and backups if there are ready for it?
i have a broken XT1562 without a nandroid or other backups...
thanks
Click to expand...
Click to collapse
Hi,
check this : http://moto.shreps.fr/?dir=Moto X Play (lux)/rom/stock_XT1562_EMEA-retfr/ZY2223RWB8
Shreps said:
Hi,
check this : http://moto.shreps.fr/?dir=Moto X Play (lux)/rom/stock_XT1562_EMEA-retfr/ZY2223RWB8
Click to expand...
Click to collapse
Hopefully they have a XT1563 full backup soon as well. Cheers.
Vibration and screen brightness are not working
Btw the stock firmware is out : http://www.filefactory.com/file/4ivu9kooeesf/?code=275
this one is for xt1563 CA
XMoDuLeSx said:
Vibration and screen brightness are not working
Btw the stock firmware is out : http://www.filefactory.com/file/4ivu9kooeesf/?code=275
this one is for xt1563 CA
Click to expand...
Click to collapse
@vache
Try adding these to the defconfig: https://github.com/sultanqasim/andr..._twrp2/arch/arm/configs/ext_config/lux.config
EDIT: I made a dedicated defconfig that you can try for this recovery: https://github.com/sultanqasim/andr...p2/arch/arm/configs/msm8916-minilux_defconfig
Wow thanks for your great work. Soon, we'll be able to get custom kernel to go with the stock firmware. We will probably get better performance with a properly tuned CPU governor. I'd also love to see CM12 being ported but the Moto firmware is already really good. In fact, I'm not sure if I could live without the added feature like Moto Voice and Moto Assist.
squid2 said:
@vache
Try adding these to the defconfig: https://github.com/sultanqasim/andr..._twrp2/arch/arm/configs/ext_config/lux.config
EDIT: I made a dedicated defconfig that you can try for this recovery: https://github.com/sultanqasim/andr...p2/arch/arm/configs/msm8916-minilux_defconfig
Click to expand...
Click to collapse
@squid2 Did you used the lux_defconfig in ext_defconfig ?
Already tried with those addition, the phone boot but i have no RIL. (Stock ROM)
Ill post a new reco with this kernel.
EDIT : Published a new version, with the new kernel config, that fix brightness and vibration.
Shreps said:
Hi,
check this : http://moto.shreps.fr/?dir=Moto X Play (lux)/rom/stock_XT1562_EMEA-retfr/ZY2223RWB8
Click to expand...
Click to collapse
So flashing this restores functionality on a XT1562?
And another thing, if your TWRP version is working when I fastboot boot it, is it guaranteed that it'll work when I fastboot flash it? And another thing: Is there a possibility to backup stock recovery, just in case TWRP doesn't work properly? I tried booting your TWRP version and backing it up but that didn't work (duh.)
Best wishes
derelektrischemoench
derelektrischemoench said:
So flashing this restores functionality on a XT1562?
And another thing, if your TWRP version is working when I fastboot boot it, is it guaranteed that it'll work when I fastboot flash it? And another thing: Is there a possibility to backup stock recovery, just in case TWRP doesn't work properly? I tried booting your TWRP version and backing it up but that didn't work (duh.)
Best wishes
derelektrischemoench
Click to expand...
Click to collapse
Stock Recovery is also available on my backup.
And yes, if TWRP is working while booting it, should work also fine when flashing it.
Be sure to use the latest version by @vache
Ok thx.
And another thing, I made a backup of my recovery partition via ls -al /dev/block/platform/7824900.sdhci/by-name
followed by
dd if=/dev/block/mmcblk0p32 (the partition that had the name "recovery"assigned in the output of the first command)
and got a nice recovery.img written to my sdcard.
Now from my understanding, in case something goes wrong with TWRP i should be able to restore my stock recovery via fastboot flash recovery nameoftheimagethatidumped.img, is that correct?
Greetz DeM
squid2 said:
@vache
Try adding these to the defconfig: https://github.com/sultanqasim/andr..._twrp2/arch/arm/configs/ext_config/lux.config
EDIT: I made a dedicated defconfig that you can try for this recovery: https://github.com/sultanqasim/andr...p2/arch/arm/configs/msm8916-minilux_defconfig
Click to expand...
Click to collapse
Got it booting, my repack method was wrong. All seems to work fine now.
Now trying to build a custom ROM.
Hey guys, I have no idea what I'm doing, so I'm wondering if anyone else has compiled a flashable Aosp or near-aosp build of android 7.0? I'm currently on PureNexus, and I'm looking for a very minimal ROM as it's the only way to reduce the lag on this low memory device we all know and love (hate?). Thanks!
Sent from my ONEPLUS A3003 using Tapatalk
jaju123 said:
Hey guys, I have no idea what I'm doing, so I'm wondering if anyone else has compiled a flashable Aosp or near-aosp build of android 7.0? I'm currently on PureNexus, and I'm looking for a very minimal ROM as it's the only way to reduce the lag on this low memory device we all know and love (hate?). Thanks!
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
I'm 100% with you on this. Minimum is best. I was wondering where the homecooked 7.0s are too.
Way too soon for a stable aosp build.
You'll probably see a flashable, pre-rooted stock rom appear first. Often these are tweaked, debloated etc so can be quite minimal.
Experimental aosp builds will likely emerge soon too but if you're the type to moan about roms not appearing fast enough and the low memory of a device you bought then you likely won't like bugs either. Maybe wait for a bit.
I wanna post mine - but GApps FC (some location provider error) and I am looking for a fix. This commit didn't fix it and I thought it might!
https://github.com/bshiznit/platform_frameworks_base/commit/4f18c68e03b996dab5df4d586db9c9af5647445a
Anyway - if there is interest (and it looks like there is) I might post as WIP this evening...
bshiznit said:
I wanna post mine - but GApps FC (some location provider error) and I am looking for a fix. This commit didn't fix it and I thought it might!
https://github.com/bshiznit/platform_frameworks_base/commit/4f18c68e03b996dab5df4d586db9c9af5647445a
Anyway - if there is interest (and it looks like there is) I might post as WIP this evening...
Click to expand...
Click to collapse
https://github.com/opengapps/opengapps/wiki/Notes-for-Android-7.0 this may help
USBhost said:
https://github.com/opengapps/opengapps/wiki/Notes-for-Android-7.0 this may help
Click to expand...
Click to collapse
Thanks! It's unclear from that if there is something I can cherry-pick, or what Any thoughs from a fellow dev?
@jaju123, @Jeff_in_LA, @astralbee, @USBhost threw my WIP build up under Android Development:
http://forum.xda-developers.com/nexus-9/development/rom-t3451480/
bshiznit said:
@jaju123, @Jeff_in_LA, @astralbee, @USBhost threw my WIP build up under Android Development:
http://forum.xda-developers.com/nexus-9/development/rom-t3451480/
Click to expand...
Click to collapse
Cool, thanks!
Jeff_in_LA said:
Cool, thanks!
Click to expand...
Click to collapse
You bet - just remember it is a work in progress
No worries. I appreciate all the hard work you did on this.
USBhost said:
https://github.com/opengapps/opengapps/wiki/Notes-for-Android-7.0 this may help
Click to expand...
Click to collapse
I got a bare bones up and working w/ Opengapps but I can't get root to work. Tried latest SuperSu but no go. It tries to install as systemless and then fails not sure why Never did that on my MM builds
@USBhost You see anything in my git repos??? Basically the same as my MM builds.
Attaching some twrp screenshots and recovery.log below.
If anyone can help it would be appreciated.
Thanks
fhem said:
I got a bare bones up and working w/ Opengapps but I can't get root to work. Tried latest SuperSu but no go. It tries to install as systemless and then fails not sure why Never did that on my MM builds
@USBhost You see anything in my git repos??? Basically the same as my MM builds.
Attaching some twrp screenshots and recovery.log below.
If anyone can help it would be appreciated.
Thanks
Click to expand...
Click to collapse
dont try v2.78 SR1
try only the v2.78
PS its not your fault
other ROMs have the same problem (the ones i tried)
USBhost said:
dont try v2.78 SR1
try only the v2.78
PS its not your fault
other ROMs have the same problem (the ones i tried)
Click to expand...
Click to collapse
Thanks but get same result --> I have attached another twrp recovery.log at bottom. It shows whats happening w/ su flash. I think LOL.
I had stock rooted but now am trying to get my aosp build up and running w/ no luck rooting. I am going to start over clean w/ fastboot stock w/o root and then try installing aosp rom and rooting.
I am also having the problem w/ twrp unhooking sometimes --- d**n N9 is very finicky!!!
Thanks for the help.
http://hastebin.com/usowulowal.diff
fhem said:
Thanks but get same result --> I have attached another twrp recovery.log at bottom. It shows whats happening w/ su flash. I think LOL.
I had stock rooted but now am trying to get my aosp build up and running w/ no luck rooting. I am going to start over clean w/ fastboot stock w/o root and then try installing aosp rom and rooting.
I am also having the problem w/ twrp unhooking sometimes --- d**n N9 is very finicky!!!
Thanks for the help.
Click to expand...
Click to collapse
You can also just try flashing the stock boot.img
And then flash SuperSU
USBhost said:
You can also just try flashing the stock boot.img
And then flash SuperSU
Click to expand...
Click to collapse
Ok finally got some time to play ---- fastboot is my friend LOL!!!
I used fastboot to wipe and start over w/ a clean tab -----> Only way I get root with my rom at current build is using twrp ---> flash my rom w/ stock boot image, flash supersu sr1 2.78 ---> bootup got root. That's all I can find that works. @USBhost Do you have an N k that allows root??? Do you have any idea what is going on with this??? BTW --- Trying to install as system install causes bootloop for me. So the only option I have at the moment is supply stock boot image and systemless root and w/ the rom. PITA
This LineageOS 14.1 ROM is built from source for Blu R1 HD.
Some features of this LineageOS 14 rom are:
- Hardware rendered LiveDisplay (no UI lag in night mode)
- Android security patches up to October
- Security hardened kernel (including BlueBorne bluetooth patches)
- Kernel patched for Nougat (Nougat compatible SELinux)
- No Chinese spyware
Credits:
zhaofengli (major thanks for getting the rom booting + hotspot/GPS fix, among other things!)
vampirefo
danielhk (GPS fix)
DeckerSu(Initial device tree, MTK patches)
Sources:
Code:
[URL=https://github.com/blumonks/android_device_blu_p6601]Device Tree[/URL]
[URL=https://github.com/blumonks/android_kernel_mediatek_mt6735]Kernel Source[/URL]
[URL=https://github.com/blumonks/android_p6601]Build Manifest[/URL]
[URL=https://github.com/blumonks/twrp_device_blu_p6601]Recovery device tree[/URL]
Downloads:
LineageOS 14.X Downloads
TWRP Recovery
Click to expand...
Click to collapse
Installation Guide:
1) Flash TWRP recovery (See downloads)
Code:
fastboot flash twrp-3.1.1-0-p6601.img
This TWRP recovery has a different device name than previous versions of TWRP.
2) Boot into recovery (Hold vol up when booting and use vol keys to select recovery)
3) If coming from a non lineageOS rom, please format system, data, and cache in recovery before flashing this rom. Otherwise stale files from previous roms may cause bugs.
5) Flash lineage rom
6) Flash gapps (obtain here: http://opengapps.org/)
Current bugs:
Camera does not work. It is still under active research and development.
Bluetooth
Github Issue Tracker (Please do not open duplicate issues)
Please note that support will be limited.
UPDATED BUILD 24 AUG 2020.
If anyone is still using this device, here is an updated build with the August 2020 Android Security Bulletin & all merged LineageOS changes since October 2017. MAKE SURE YOU FLASH USING THE TWRP IN THE ORIGINAL POST! You can flash over any builds in this thread, the camera still doesn't work and I have no interest in fixing it.
https://www.mediafire.com/file/dbdmk...p6601.zip/file
https://gofile.io/d/vTddMJ
Vulnerability said:
Nice! Can't wait to test it! Any screenshots?
Click to expand...
Click to collapse
It's the same as any other lineage rom. Updated OP.
How well does Bluetooth Audio work? Does it make you sound like a Chipmunk?
Is enforcing SELinux supported? Or only permissive?
EDIT: Don't worry I saw the issue tracker post
I'm gonna try this rom
It's nice to see development alive!!!
Hope you could a finally fix the broken camera
Does anyone know anything about the KRACK vulnerability?
zombie_ryushu said:
How well does Bluetooth Audio work? Does it make you sound like a Chipmunk?
Click to expand...
Click to collapse
I don't know, nor do I have the accessories to test it. I would appreciate if you could try it and report back.
zombie_ryushu said:
Does anyone know anything about the KRACK vulnerability?
Click to expand...
Click to collapse
Yes.. Please see download link for latest rom. It includes the KRACK security fixes from lineageOS.
jianC said:
I don't know, nor do I have the accessories to test it. I would appreciate if you could try it and report back.
Yes.. Please see download link for latest rom. It includes the KRACK security fixes from lineageOS.
Click to expand...
Click to collapse
Thanks for the updated version.
Urg, but I just finished downloading the original release
jianC said:
I don't know, nor do I have the accessories to test it. I would appreciate if you could try it and report back.
Yes.. Please see download link for latest rom. It includes the KRACK security fixes from lineageOS.
Click to expand...
Click to collapse
Does this fix also apply to the LineageOS 13.x Rom? I need the Front facing camera working, and that works under Marshmellow and not Nougat.
Just wanted to thank you for your hard work and dedication on this ROM project and wish you good luck with the camera as well.
Not that I find the camera on the R1 HD all that useful as it takes pretty lame photos, but the lack of camera is basically the only thing keeping me from ditching Blu software altogether.
I really hope you manage to get a 100% operational LineageOS for the R1 HD.
Yesterday I called Amazon and complained about the software that collected our personal information and data and submitted it to Blu headquarters in China. They said that I could return the phone for a full refund so at this point I am seriously contemplating doing that. The only problem is that I don't have a backup phone.
The lack of resources from MTK based processors is such a deal breaker. I was not aware it would be so difficult to get development going for it when I bought my phone last year.
Now I'm contemplating getting an used phone with better development support after I return my R1 HD.
I really wanted to wait until OnePlus released their new device with a better display and hopefully a near bezel less display and at least IP67 water resistance. That's the reason why I didn't go for the OP5. The upside-down screen was also another one.
If you could get the camera working in LOS than I'd hold on to my R1 HD for a a while longer. But I'm not keeping my hopes up... Just being realistic. Haha!
Thanks again!
Thanks for your support!
As of now, I've been studying the leaked MTK camera sources for other devices and using IDA to see what extra symbols and logic the stock libcameraservice.so and libcamera_client.so has. It appears that replacing these two libs was the key to fixing camera in cm-13 ports.
Thank you!
Oh, I didn't know camera support was fixed for CM 13 on the R1 HD. Maybe I didn't see it here. But I'd much rather have a non Blu version of Android with all security patches even if it's just on marshmallow.
Three days ago I just realized that Blu had a frigging app collecting my personal data and sending it back to China.
It had sent over 5.9MB of data since July 21st. I think it's a lot of data for text only transmissions.
Anyhow, I've been seeing people using Footej on other ROMs in which they could not get the camera working with stock camera app. Is that what you mean by getting the camera to work?
Stuck here guys!!!
Which recovery version do I have to install to properly flash this rom?
khyr said:
Stuck here guys!!!
Which recovery version do I have to install to properly flash this rom?
Click to expand...
Click to collapse
Dang! That's old! I guess devs should be more organized in doing a walk through with links to the files and recoveries needed to flash their awesome work.
Here's mine that I've just uploaded to zippy. I think it's the latest available and should be compatible with all ROMs.
Please report back with your findings and opinions on the ROM.
Please try to use both SIM cards to see if they work okay.
http://www8.zippyshare.com/d/p4HMiDRq/41954/R1_Port_3.1-TWRP.img
khyr said:
Stuck here guys!!!
Which recovery version do I have to install to properly flash this rom?
Click to expand...
Click to collapse
Which version of the ROM is installed on it now? Modified or stock? Which recovery is on the phone? Stock or TWRP?
I can't post pictures but it gives me an error saying that the package is for p6601 and the updated twrp image says device is Life_Max
frosted.efizzle said:
I can't post pictures but it gives me an error saying that the package is for p6601 and the updated twrp image says device is Life_Max
Click to expand...
Click to collapse
Did you download and flash the image I've just shared above?
AndroidBR said:
Did you download and flash the image I've just shared above?
Click to expand...
Click to collapse
Same error
With they recovery You provided above
Thanks for your support!
Intro(Skip at your wish xd):
Hello guys, it's kind of frustrating that our 4a 5G don't get much love here(in custom ROM development perspective) as Pixel 5 as it's not really a "main" variant.
For myself, I love Pixel devices for Google releases "proper" device tree and most necessary stuff, but still it require quite some time for me to get things right and a working ROM build, hell, to be honest, I spent like about 30 hrs already as this is my first time to use AOSP tree + vendor blobs from Google site to build ROMs)
Despite the lack of previous experience, the first build that I'm releasing here, is working quite well, I haven't discovered any (device-specific) bug just yet, anyway, let's continue
Click to expand...
Click to collapse
Instructions:
0. Make sure your bootloader is unlocked
1. Download ROM zip from the link below, and grab Magisk patched boot.img inside the folder as well if you want root access
2. Reboot to bootloader
2.5. Flash updated bootloader.img and radio.img from Google site
3. Use `fastboot -w update LineageOS_microG-bramble-(BUILD DATE HERE)-userdebug-signed.zip` to flash
and yes, you can omit the "-w" parameter if you're not flashing for the first time, aka just updating from previous release
4(optional). Hopefully after flashing you'll be booted into LineageOS, reboot to bootloader again,
and flash the Magisk patched boot.img extracted from the 7z file with `fastboot flash boot magisk_patched.img`,
reboot after finished
5. Enjoy!
Click to expand...
Click to collapse
Features:
1. MicroG integrated nicely (Thank OmniROM dev([email protected]) for the repo)
2. Replaced default WebView with Bromite WebView
3. Default DNS was set to UncensoredDNS in framework overlay
4. Removed unnecessary prebuilt APKs
Click to expand...
Click to collapse
Download
Contacts:
Telegram:
Channel for Pixel 4a 5G related stuff
Group for Pixel 4a 5G discussion
Special thanks: @kdrag0n , @akhilnarang for helping me with issues when I couldn't get my build working
XDA:DevDB Information
LineageOS 18.1 - microG Edition, ROM for the Google Pixel 4a 5G
Source
ROM
Kernel
Contributors
dic1911
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
ROM Firmware Required: Current
Based On: LineageOS
Version Information
Status: Testing
Created 2020-11-29
Last Updated 2020-12-16
Current Known Issue
1. Some minor bubble notification glitch, ROM side issue.
2. Video call is unstable, crashes in about ~10 minutes after the call starts (untested in latest update, may be fixed)
3. If mobile data doesn't work after update, try select/set APN manually(select whatever APN first, then select the correct one after)
Reserved
Awesome, thank you!
I've never heard of the MicroG before so just looked that up. I'm loving that philosophy so I'm definitely gonna be checking that out! Thanks! My pixel is arriving tomorrow so after playing around with it first, I'll try out your ROM once there's more responses from others here.
Hey thx for the ROM is a A11 Version planned?
I'll wait for Android 11 version
Dimontiman said:
Hey thx for the ROM is a A11 Version planned?
Click to expand...
Click to collapse
warrencoakley said:
I'll wait for Android 11 version
Click to expand...
Click to collapse
LineageOS 18.0 is Android 11, but XDA didn't update the option menu so I chose Android 10.
View attachment 5144565
Took a while for this thread to pop back up after forum migration..
Thanks for the awesome work
Is anyone using this ROM as their daily driver? I'm still reluctant to risk my warranty
I guess I will roll the dice and give it a go. Anyone know if this will affect my e-sim with Google Fi?
Thank you, dic1911 for being so awesome to bring first rom to Bramble, which is almost brand-new! I appreciate your work and we are really glad for it.
Joegrizz said:
I guess I will roll the dice and give it a go. Anyone know if this will affect my e-sim with Google Fi?
Click to expand...
Click to collapse
It won't affect Google Fi.
Thanks. It looks great and runs good but I’m obviously missing something. I tried installing GApps via ADB side load and no matter which size Nikhil version I attempt to install, I get an error there’s not enough memory. I’ve rebooted after flashing to the rom and also done a factory reset to no avail. What am I missing? I’ve also tried it with and without the patched boot.img.
tgilmore16 said:
Thanks. It looks great and runs good but I’m obviously missing something. I tried installing GApps via ADB side load and no matter which size Nikhil version I attempt to install, I get an error there’s not enough memory. I’ve rebooted after flashing to the rom and also done a factory reset to no avail. What am I missing? I’ve also tried it with and without the patched boot.img.
Click to expand...
Click to collapse
Use systemless WeebGapps via Magisk:
t.me/WeebGAppsChannel
Does this rom use seedvault like mainline lineageos? Or is google backup in here even with microg?
Crashdown1994 said:
Is anyone using this ROM as their daily driver? I'm still reluctant to risk my warranty
Click to expand...
Click to collapse
Warranty? Should not effect that. I wouldn't think it would. Bootloader is unlockable and google even gives the option to flash aosp vanilla(no google) or public (official google rom) with their flashing tool (via chrome browser).
Are Pixel-Exclusive features such as Now Playing, Live Captions, Call Screening, Adaptive Sound, Screen Attention included and working?
Any issues getting safetynet to pass?
GoldElocks said:
Are Pixel-Exclusive features such as Now Playing, Live Captions, Call Screening, Adaptive Sound, Screen Attention included and working?
Any issues getting safetynet to pass?
Click to expand...
Click to collapse
This is Lineage... You install this one to get privacy and free yourself from Gapps. You might be able to get most features running, but then you just can stay with stock - privacy is then gone again...
letrain02 said:
Does this rom use seedvault like mainline lineageos? Or is google backup in here even with microg?
Click to expand...
Click to collapse
SeedVault is builtin system app for all LineageOS builds, no matter it's official or not, if it's not there in someone else's build, either it's removed by the builder or the build is too old.
So yes, SeedVault is in my build, but there's no guarantee that it works with any apps just like Google Backup(which I found pretty much useless in my case)
PS. I'm not really as active as I was on xda since about 2 years ago, please join Telegram for more updated stuff
PPS. I released GCam extracted from stock ROM and modified to make it work on LineageOS(and pretty much any custom ROM with right stuff baked in), and yes, you'll need to flash updated build from my Telegram channel (It's more convenient for me to upload to Telegram as the storage space there is unlimited)
LineageOS 18.1 is up!
Now with December security patch, grab it from the link in OP