( Discontinued ) LineageOS-Port{Beta-4} For the R1_HD ( Discontinued ) - BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel

Discontinued
!!!!PLEASE READ THIS SECTION BEFORE PROCEEDING TO FLASH THIS ROM!!!!
This is based of @vampirefo 's LineageOS , with my tweaks as I now use the port section to test and share with others to help the original LineageOS by @vampirefo to gain fixes
What works : so far , Ril(sim cards) , Bluetooth , Wifi , Audio , Microphone , HotSpot , Rotation .
Bug: Camera (really hard to fix)
P.S- THIS IS NOT A DAILY DRIVER READY ROM , THIS IS PURELY EXPERIMENTAL AND FOR THE JOY OF IT. DONT COME TO ME IF SOMETHING WENT WRONG . FEEL FREE TO REPORT MAJOR BUGS , BY MAJOR WE ( THE R1 HD'S ROUNDTABLE TEAM ) MEAN BUG AND GLITCHES THAT HINDER A NORMAL DAY 2 DAY USAGE OF THE ROM....SMALLER BUGS WILL BE LOOKED AT LATER IF POSSIBLE.
THANKS TO THESE DEVS THIS WOULD HAVE NOT BEEN POSSIBLE:
THANKS TO :
@CyanogenMod
@oleg.svs (REALLY BIG THANKS TO HIM)
@DeckerSU (ANOTHER REALLY BIG-UPS TO HIM)
@OceanLaber over at 4PDA.ru
@niklabs
@vampirefo
@ THE R1 HD'S ROUNDTABLE TEAM
System : Nougat 7.1.1
Kernel : 3.18.19
OS : LineageOS 7.1.1
FULL WIPE/CLEAN WIPE BEFORE FLASHING ROM AND GAPPS
!!!!!! Advance Wipe : Dalvik , system , cache , data , internal
then go back to twrp main menu , go to mount and uncheck system , go back to twrp main menu again
then go to reboot and choose recovery to reboot back to recovery.
Afterwards proceed to flash rom and gapps as usual!!!!!!
**Download Link is automatically updated to recent release**
Download : https://www.androidfilehost.com/?fid=457095661767128973 <<---- Beta 4
Gapps : http://opengapps.org/
Choose Platform: Arm
Android : 7.1
Variant : Its your choice. ( You can choose Micro version to enable Google Assistant )
PLEASE DON'T TELL ME THAT THE CAMERA DOES NOT WORK , WE ALL KNOW THAT IT DOES NOT
Enjoy!!

---

KazuDante said:
Ive Been looking around to find new roms that i could port to the R1HD. Ive ported about 5-8 roms that work on the R1 HD but only 2 works flawlessly but the others have a camera issue ( camera not connecting ).
Now ive found a x32-bit CM14.1 for the MT6735 , that works on the device that it was built for. Of course I quickly went to attempt to port it but no luck as of now. The issue seems to be that the /system partition is not mounted correctly in regards to our boot image .
Here are the links for those who want to look at it with us ( R1 HD's Round Table )
Where i saw the post : https://vk.com/smart_rom (scroll down a little bit and you guys will see cm14.1 mt6735, they even made a 64bit now)
Where the test builds are posted and also the sources : https://github.com/olegsvs/android_device_archos_persimmon/releases (now they are testing Resuretion Remix 5.8.XX)
It just to prove that MT6735 can also be running Android 7 as well.
As a team we can make this happen and bring new life to the R1 HD.
Update : Now a Resurection Remix 5.8 is also running on the MT6735 x32. ---> https://vk.com/wall-77256552_14248
Click to expand...
Click to collapse
Can you post links for the working Roms? I have been searching for a working Roms for quite some time and I can't manage to find one, don't know how you did it!

---

I will re-download and fix them to re-upload but only the one that everything works including the camera.
Sent from my BLU R1 HD using Tapatalk

---

Here one i ported but the camera does not work : https://drive.google.com/file/d/0BzU6b7lzLmttNjVEX0VqdU9OMTg/view?usp=drivesdk
Sent from my BLU R1 HD using Tapatalk

---

Are there any with a working camera that you could post?

---

Yes there is one that everything works , i will upload it soon , my only network access is this phone and im low on credits to get more data.
Sent from my BLU R1 HD using Tapatalk

---

Great!! Let me know if you get 14.1 up and running. I'm a huge cm fan and would love the nougat features! Thanks in advance for your hard work.

---

Great!!! Uyeee!!
Finally we are getting Nougat
UPDATE
STUCK IN SETUP WIZARD
Keyboard is fc
+++Fixed+++
But is Android marshamallow rom port
Can wait to try any cm 14.1 build
For our Phone
Cheers
Keep THE good job

---

quick update,found another CM14.1 thats compiled for a MT6737 device with a 3.18.19 kernel , i'm going to test it out because one of the port i made was also from a MT6737 device.

---

khyr said:
Great!!! Uyeee!!
Finally we are getting Nougat
UPDATE
STUCK IN SETUP WIZARD
Keyboard is fc
+++Fixed+++
Bit is antes Android marshamallow rom port
Can wait to try any cm 14.1 build
For our Phone
Cheers
Keep THE good job
Click to expand...
Click to collapse
aospkeyboard.....during setup avoid anything that requires you to type anything just skip them , then once pass that go to settings->about phone to activate develloper mode , then go to developer mode to enable usb debugging , then on your computer head over to apkmirror to download google keyboard or GBoard(new name for google keyboard), once downloaded open CMD(command prompt) or terminal (for mac n linux users ) type adb install ( then drag the downloaded keyboard in this spot of this message with just 1 space apart from last typed word wich is install in our case then hit enter)........once the install is complete head back to setting then language & input and switch it to GBoard or something else if you decided to get a different keyboard.

---

with the new cm14.1 that i found today thats built for a 3.18.19 this time actually mount's the system partition and now im able to grab logcats and dmesg ect.... right now what im seeing are egl/mali errors......but i really think we could use that source and use our binary files to build the r1 its own cm14.1 tree

---

other devs check update 2 in OP.

---

Modifying an updater-script from a different device and ROM would not necessarily work. IIRC, The Galaxy S2 and Galaxy S Blaze 4G was able to do that, but in this instance, with different phone hardware, this would not work. Luckily, you did not get bricked from doing this. Unless you are completely building from source, with the R1 files, these dirty ports will take a hefty amount of time. I recommend building a device tree and start building with the kernels that either you have found, or have been created on this forum.

---

xWolf13 said:
Modifying an updater-script from a different device and ROM would not necessarily work. IIRC, The Galaxy S2 and Galaxy S Blaze 4G was able to do that, but in this instance, with different phone hardware, this would not work. Luckily, you did not get bricked from doing this. Unless you are completely building from source, with the R1 files, these dirty ports will take a hefty amount of time. I recommend building a device tree and start building with the kernels that either you have found, or have been created on this forum.
Click to expand...
Click to collapse
from my experience with porting , modding the updaterscript doesnt cause much threat since i remove any other potential threats to the device and of course i dont flash the boot.img that's for the other device....pretty much i modded the updaterscript just to that it flashes the rom to the right partitions for the device im flashing , yesterday was the first time i ported a kernel (boot.img-kernel) from another device's boot.img and it booted the R1, the only thing that did not work was the sim cards since the kernel was compiled with a different driver that was for the other device. it even added in the settings menu a fingerprint option (of course did not work) even tho the R1 does not have a fingerprint sensor. so my conclusion was that the other device is pretty much a clone of the R1 with a slight difference in some hardware , the purpose of the kernel port was to see if it will boot the r1 wich it did but more is the fact that the other device has a defconfig for a 64bit version as well wich the R1 does not and building a 64bit kernel for the r1 would allow me to port over so many more roms. I really wish the devs of this community would take interest in this because this would change the R1 alot.

---

KazuDante said:
from my experience with porting , modding the updaterscript doesnt cause much threat since i remove any other potential threats to the device and of course i dont flash the boot.img that's for the other device....pretty much i modded the updaterscript just to that it flashes the rom to the right partitions for the device im flashing , yesterday was the first time i ported a kernel (boot.img-kernel) from another device's boot.img and it booted the R1, the only thing that did not work was the sim cards since the kernel was compiled with a different driver that was for the other device. it even added in the settings menu a fingerprint option (of course did not work) even tho the R1 does not have a fingerprint sensor. so my conclusion was that the other device is pretty much a clone of the R1 with a slight difference in some hardware , the purpose of the kernel port was to see if it will boot the r1 wich it did but more is the fact that the other device has a defconfig for a 64bit version as well wich the R1 does not and building a 64bit kernel for the r1 would allow me to port over so many more roms. I really wish the devs of this community would take interest in this because this would change the R1 alot.
Click to expand...
Click to collapse
C,Mon Devs

---

F2FS?
KazuDante said:
Ive Been looking around to find new roms that i could port to the R1HD. Ive ported about 5-8 roms that work on the R1 HD but only 2 works flawlessly but the others have a camera issue ( camera not connecting ).
Now ive found a x32-bit CM14.1 for the MT6735 , that works on the device that it was built for. Of course I quickly went to attempt to port it but no luck as of now. The issue seems to be that the /system partition is not mounted correctly in regards to our boot image .
Here are the links for those who want to look at it with us ( R1 HD's Round Table )
Where i saw the post : https://vk.com/smart_rom (scroll down a little bit and you guys will see cm14.1 mt6735, they even made a 64bit now)
Where the test builds are posted and also the sources : https://github.com/olegsvs/android_device_archos_persimmon/releases (now they are testing Resuretion Remix 5.8.XX)
It just to prove that MT6735 can also be running Android 7 as well.
As a team we can make this happen and bring new life to the R1 HD.
Update : Now a Resurection Remix 5.8 is also running on the MT6735 x32. ---> https://vk.com/wall-77256552_14248
Update 2 : here is the boot image i used to get the CM14 system partition to be up and allowed me to use a few adb/shell commands ,this by any mean does not mean that CM14.1 booted properly , theres alot of issues , i could not as of now even get the boot animation to load . this is purely experimental. : https://drive.google.com/file/d/0BzU6b7lzLmttSThpX3ctbHNkcFU/view?usp=sharing
And heres the CM14 i downloaded and tested it : https://github.com/DeckerSU/android_device_smart_surf2_4g/releases/tag/0.2alpha
Also of other dev out there are going to take a crack at it the initial updaterscript wasnt correct so replace it with this updaterscript : https://drive.google.com/file/d/0BzU6b7lzLmttVVh0NUQxWjRNODg/view?usp=sharing
this is yet another step foward for R1 HD.
P.S THIS DOES NOT BOOT , DONT FLASH IT IF YOU DONT KNOW WHAT YOU ARE DOING, I AM NOT RESPONSIBLE FOR ANY DAMAGES THAT MAY OCCUR. YOU HAVE BEEN WARNED . (4DEV ONLY NOT USERS)
Click to expand...
Click to collapse
Why not create Support for F2FS IN DATA PARTITION
This Will increase perfomance a Lot AND running cm14.1 64bits
This device Will fly!!!

---

khyr said:
Why not create Support for F2FS IN DATA PARTITION
This Will increase perfomance a Lot AND running cm14.1 64bits
This device Will fly!!!
Click to expand...
Click to collapse
for that we first need x64 kernel and x64 twrp....thats if R1 bootloader allows x64 kernels

---

KazuDante said:
for that we first need x64 kernel and x64 twrp....thats if R1 bootloader allows x64 kernels
Click to expand...
Click to collapse
What about F2FS ?
IT IS POSSIBLE TO GET IT?

---

khyr said:
What about F2FS ?
IT IS POSSIBLE TO GET IT?
Click to expand...
Click to collapse
Unless we can actually compile a fully working rom for the R1 , for f2fs to properly work both rom and kernel has to support it..that also includes the twrp.
As of now we still can't figure out whats missing that's stopping a compiled rom for our device (ex. cm13 from @vampirefo and @bullet25 )to boot.

---

Damn! What do you think about Lenovo k80m
4GB ram 64G storage
Intel Atom procesador it Is worth it Upgrade from Blu R1 this Phone Is stock in kit kat 4.4.4
http://m.gsmarena.com/lenovo_k80-7216.php
I know this Is a off topic question
But Is just $139 AND you got 64GB of storage AND 4G ram
The zenfone 2 4GB RAM it Is in the same pricetag but Is only 16GB storage