LineageOS13-port-R1-HD (camera-mostly- works)

[mrmazak]

Should I redownload and flash 5.2? Was there a recent update made? I got an alert and I see a date of 11-02 for the latest update but I'm not sure what it is. Thanks.

No,

I just had to edit the OP. I had a link in there to rom this was ported from. And that link was to "needrom" , and appaerently it is not allowed to link to needrom

 

[armivzla]

No,

I just had to edit the OP. I had a link in there to rom this was ported from. And that link was to "needrom" , and appaerently it is not allowed to link to needrom

Is this ROM more stable or at least better than the stock ROM?
With regard to the kernel, does not have any type of retouching or overclock?
And the battery?

Sorry so many questions

 

[mrmazak]

Is this ROM more stable or at least better than the stock ROM?
With regard to the kernel, does not have any type of retouching or overclock?
And the battery?

Sorry so many questions

Really dont have much opinion on it.

I have not used this phone is a while.

There is none of the spy programs hiding from BLU in this one (just the ones from google, LOL)

 

[seungbaekm]

Anyone knows why it failed?
My BLU currently installed TWRP 3.1.1. version and LineageOS 14(no camera works).
I tried to flash V5.2 ROM, but keep fail. Re-download and tried to flash, but again failed.

 

[mrmazak]

Anyone knows why it failed?
My BLU currently installed TWRP 3.1.1. version and LineageOS 14(no camera works).
I tried to flash V5.2 ROM, but keep fail. Re-download and tried to flash, but again failed.

yes. thats because the recovery you are using. and the mount point used in the install script.

I just went through this for these different recoveries on this forrum. some ported some built . any way

you can open the zip file up and make changes to the file

here is the path inside the zip.

\MATA-INF\com\google\android\upadater-script

Change the lines that has this:

format("ext4", "EMMC", "/dev/block/platform/mtk-msdc.0/by-name/system", "0", "/system");
mount("ext4", "EMMC", "/dev/block/platform/mtk-msdc.0/by-name/system", "/system", "max_batch_time=0,commit=1,data=ordered,barrier=1,errors=panic,nodelalloc");

To this

format("ext4", "EMMC", "/dev/block/mmcblk0p20", "0", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p20", "/system", "max_batch_time=0,commit=1,data=ordered,barrier=1,errors=panic,nodelalloc");

And then at bottom also change these lines

package_extract_file("boot.img", "/dev/block/platform/mtk-msdc.0/by-name/boot");

To this

package_extract_file("boot.img", "/dev/block/mmcblk0p7");

Those changes will make this work in all (5 i think) of the recoveries on this forum.
If that sounds to difficult you could flash the ported 3.1.1 recovery (it is linked in the OP of this thread). That is the one I was using when I made and tested these LM13 port installs.

 

[seungbaekm]

yes. thats because the recovery you are using. and the mount point used in the install script.

I just went through this for these different recoveries on this forrum. some ported some built . any way

you can open the zip file up and make changes to the file

here is the path inside the zip.

\MATA-INF\com\google\android\upadater-script

Change the lines that has this:

format("ext4", "EMMC", "/dev/block/platform/mtk-msdc.0/by-name/system", "0", "/system");
mount("ext4", "EMMC", "/dev/block/platform/mtk-msdc.0/by-name/system", "/system", "max_batch_time=0,commit=1,data=ordered,barrier=1,errors=panic,nodelalloc");

To this

format("ext4", "EMMC", "/dev/block/mmcblk0p20", "0", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p20", "/system", "max_batch_time=0,commit=1,data=ordered,barrier=1,errors=panic,nodelalloc");

And then at bottom also change these lines

package_extract_file("boot.img", "/dev/block/platform/mtk-msdc.0/by-name/boot");

To this

package_extract_file("boot.img", "/dev/block/mmcblk0p7");

Those changes will make this work in all (5 i think) of the recoveries on this forum.
If that sounds to difficult you could flash the ported 3.1.1 recovery (it is linked in the OP of this thread). That is the one I was using when I made and tested these LM13 port installs.

I re-flashed TWRP in the OP.
It works. Thanks.

 

[renzofronte]

Hi!!! i need rom in spanish pleaseeeee

 

[jasonmerc]

Hi!!! i need rom in spanish pleaseeeee

Go to settings and change language?

 

[PowSniffer0110]

Hi!!! i need rom in spanish pleaseeeee

Yeah what the hell you taking about

 

[zombie_ryushu]

Frustrations with LineageOS

While I happen to have a TWRP enabled R1 HD, I'm getting extremely frustrated. I'm using the LineageOS 13 Rom, and have gotten no updates for KRACK. Everyone is moving back to the Bootloader Unlocked Stock Rom versions, and the Camera still doesn't work under LineageOS 14.1. I'm probably going to give up soon and move to another device from Le Eco, or something that is easier to support.

I'd be willing to stay with LineageOS 13.x longer if I could get patches for KRACK. I lack the development resources to build my own Roms.

 

[majikfox]

This ROM is dead.

404 on the github.

Admin please close the thread.

 

[mrmazak]

This ROM is dead.

404 on the github.

Admin please close the thread.

Your right i should remove the link to github, but it is a ported rom, not a build. So GitHub was only where i was tracking changes made (swapped files). There was no build trees anyway.

 

[majikfox]

Your right i should remove the link to github, but it is a ported rom, not a build. So GitHub was only where i was tracking changes made (swapped files). There was no build trees anyway.

Thanks for the update, the link is working now.

 

[joedajoester]

I have an amazon r1 hd running an v8.4 rom with ads removed. I have twrp installed and am rooted but i want to try this rom out. Can i just wipe system/data and flash it with gapps or does it matter which version i am on before flashing? I want to make sure because this isn't like my pixel 2 where nothing really matters when it comes to flashing and recovering from a bad flash is easy.

 

[Darkyputz]

Soooo...
I installed this v5.2 now on my phone and it solved me a few issues, but mostly the WLAN is back up and reliable...
Camera works just fine...besides the video function, but hey...i rather have WLAN then video capture...
So thx to everyone for this awesome build...
As a small tip, i had to get the nano gapps since with stock i got the pixel loader failing every time...
But now i am up, happy again with my phone...best 52 bucks spent so far @joedajoester
I cleaned/wiped data, davlik,cache and system...after i backed all up to make sure i have a way back
I also had to unpack the recommended trwp 3.11 since the installer did not like the zip file, but with the img file it worked like a charm

 

[pfederighi]

Hello.

While I realize development has ended, perhaps someone has a solution to the problem I'm experiencing with this ROM. Video playback in web browsers is messed up, kind of like scrambled/copy protected video from the old days of analog cable TV. It doesn't matter what web browser is used. It doesn't affect everything. For example, videos hosted on YouTube exhibit this behavior while those hosted on Vimeo do not. The actual YouTube app works just fine.

Anyone have any ideas?