[ROM][UNOFFICIAL][7.1.2]Lineage-14.1 for Blu Life Max

vampirefo · May 21, 2017

As with any rom you flash any damage is your own fault, and it voids you warranty.

LineageOS is a free and open-source operating system for smartphones and tablet computers, based on the Android mobile platform. It is the successor to the highly popular custom ROM CyanogenMod.

This rom is for blu Life Max 32bit, it could be ported to similar devices I won't be providing any help in doing that.

What works:
Radio
Bluetooth
calls
messages
audio
wifi
tethering
video playback

Known issue:
fingerprint scanner not working.

You need to use BTmomo app for sound over bluetooth
https://play.google.com/store/apps/details?id=com.bedoig.BTmono&hl=en

to install download rom and flash via twrp.
place lineage-14.1-20170511-UNOFFICIAL-Life_Max.zip on sdcard reboot to twrp
factory reset
install lineage-14.1-20170511-UNOFFICIAL-Life_Max.zip
reboot to system.
this rom will take a while on first boot.

TWRP download
https://www.androidfilehost.com/?fid=529152257862728300
Rom download
https://www.androidfilehost.com/?fid=673368273298953959
you needs to install gapps.

http://opengapps.org/

rom has built in root just need to enable it.

Security Patch May 5 2017

Credits :
@DeckerSU
@oleg.svs
@Ruslan_3
@xen0n
@fire855
@SamarV-121
@Mysteryagr
@vampirefo

Note!!!
Coming from stock rom you have to format data via fastboot, cause stock rom is force encrypted.

Factory reset does nothing, you have to wipe internal sdcard, done via fastboot, then boot into TWRP and wipe data also.

boot into bootloader

fastboot format userdata
fastboot format cache
fastboot boot Life_Max_31_recovery.img

in recovery
format data
type yes

now data partition is fixed, if you ever flash your backed up stock rom, you will need to repeat this as your data partition will become encrypted.

To me it's just common practice to use fastboot format userdata
fastboot format cache before installing any rom, it's required anytime you use a rom that was encrypted, the partition needs to be deleted and rebuilt non encrypted.

SamarV-121 · May 12, 2017 at 4:03 AM

Great @vampirefo

nervehammer · May 13, 2017 at 1:57 AM

nice work , keep it up

mrmazak · May 14, 2017

needed to get another phone. since my R1-HD test phone has decided to no longer turn on after flashing the updated v8.3 trustzone.bin . So I ordered this one.

I might be late on this question, I read a post earlier, but cant find it now, where you said recovery needs to be booted only. This thread makes me think you got past that problem?

**EDIT**
I still look forward to receiving this new phone and using your custom rom, but I just repaired my other phone. LOL now I guess I will have 2 testing phones.

vampirefo · May 14, 2017

mrmazak said:
needed to get another phone. since my R1-HD test phone has decided to no longer turn on after flashing the updated v8.3 trustzone.bin . So I ordered this one.

I might be late on this question, I read a post earlier, but cant find it now, where you said recovery needs to be booted only. This thread makes me think you got past that problem?

Correct this recovery can be flashed to phone, Blu disabled touch in recovery, I was able fix that once they finally gave me the kernel source.

This is the first recovery for Blu Life Max that touch works after flashing to phone, the other recoveries touch won't work once flashed to phone.

Sent from my Life Max using Tapatalk

mrmazak · May 17, 2017 at 11:08 PM

vampirefo said:
Correct this recovery can be flashed to phone, Blu disabled touch in recovery, I was able fix that once they finally gave me the kernel source.

This is the first recovery for Blu Life Max that touch works after flashing to phone, the other recoveries touch won't work once flashed to phone.

Sent from my Life Max using Tapatalk

Received max phone today.
First thing after making a backup with miracle was to unlock and boot then flash" Life_Max_31_recovery.img"

booting it worked good but flashing I lost touch.?

vampirefo · May 17, 2017 at 11:32 PM

mrmazak said:
Received max phone today.
First thing after making a backup with miracle was to unlock and boot then flash" Life_Max_31_recovery.img"

booting it worked good but flashing I lost touch.?

Redownload try again, I reuploaded.

in recovery

adb shell

cat /proc/version

Code:

cat /proc/version
Linux version 3.18.19 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Wed May 3 13:02:36 EDT 2017

mrmazak · May 18, 2017

vampirefo said:
Redownload try again, I reuploaded.

in recovery

adb shell

cat /proc/version

Code:

cat /proc/version Linux version 3.18.19 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Wed May 3 13:02:36 EDT 2017

this is what I had.

Code:

C:\Users\Mr>adb shell cat /proc/version Linux version 3.18.19 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Thu Feb 16 15:07:10 CST 2017

opps that was not while in recovery

re-downloading now

new uploaded version touch works.

Code:

C:\Users\Mr>adb reboot recovery

C:\Users\Mr>adb shell cat /proc/version
Linux version 3.18.19 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Wed May 3 13:02:36 EDT 2017

---------- Post added at 06:53 PM ---------- Previous post was at 06:40 PM ----------

ROM install went just fine.

still need to add gaps.

on open gapps page, there is note next to 7.0 and 7.1 versions that say a patched rom is needed for proper web view.

is this 7.1 patched?

vampirefo · May 18, 2017 at 12:37 AM

mrmazak said:
this is what I had.

Code:

C:\Users\Mr>adb shell cat /proc/version Linux version 3.18.19 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Thu Feb 16 15:07:10 CST 2017

opps that was not while in recovery

re-downloading now

new uploaded version touch works.

Code:

C:\Users\Mr>adb reboot recovery C:\Users\Mr>adb shell cat /proc/version Linux version 3.18.19 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Wed May 3 13:02:36 EDT 2017

---------- Post added at 06:53 PM ---------- Previous post was at 06:40 PM ----------

ROM install went just fine.

still need to add gaps.

on open gapps page, there is note next to 7.0 and 7.1 versions that say a patched rom is needed for proper web view.

is this 7.1 patched?

I don't know what web view is, unless it comes with Lineage OS source, it's not included.

Sent from my Life_Max using Tapatalk

mrmazak · May 18, 2017 at 1:28 AM

vampirefo said:
I don't know what web view is, unless it comes with Lineage OS source, it's not included.

Sent from my Life_Max using Tapatalk

needed to start over again. I tried to do factory reset from in settings. And it just keeps booting to recovery.
I wiped, advanced wiped, formatted /data. It always just reboots to recovery.
Currently re-installing lineageos14 and hope it fixes whatever the factory reset flagged.

It finished faster than I can type.
Th re-install failed to fix the loop.

I needed to boot factory recovery to finish the factory reset, now its going again.

Is this something I should have known not to do?

vampirefo · May 18, 2017

mrmazak said:
needed to start over again. I tried to do factory reset from in settings. And it just keeps booting to recovery.
I wiped, advanced wiped, formatted /data. It always just reboots to recovery.
Currently re-installing lineageos14 and hope it fixes whatever the factory reset flagged.

It finished faster than I can type.
Th re-install failed to fix the loop.

I needed to boot factory recovery to finish the factory reset, now its going again.

Is this something I should have known not to do?

Coming from stock rom you have to format data via fastboot, cause stock rom is force encrypted.

Factory reset does nothing, you have to wipe internal sdcard, done via fastboot, then boot into TWRP and wipe data also.

boot into bootloader

fastboot format userdata
fastboot format cache
fastboot boot Life_Max_31_recovery.img

in recovery
format data
type yes

now data partition is fixed, if you ever flash your backed up stock rom, you will need to repeat this as your data partition will become encrypted.

Sent from my Life_Max using Tapatalk

mrmazak · May 18, 2017 at 2:23 AM

vampirefo said:
Coming from stock rom you have to format data via fastboot, cause stock rom is force encrypted.

Factory reset does nothing, you have to wipe internal sdcard, done via fastboot, then boot into TWRP and wipe data also.

boot into bootloader

fastboot format userdata
fastboot format cache
fastboot boot Life_Max_31_recovery.img

in recovery
format data
type yes

now data partition is fixed, if you ever flash your backed up stock rom, you will need to repeat this as your data partition will become encrypted.

Sent from my Life_Max using Tapatalk

I went through and did "fastboot format userdata" and "fastboot format cache" . Did format in recovery also.
And tried one more time in settings to do factory reset. Got the same situation. again needed to boot factory recovery to release the final cached command that is preventing system from loading.

Are you able to do factory reset from settings, and it works?

vampirefo · May 18, 2017

mrmazak said:
I went through and did "fastboot format userdata" and "fastboot format cache" . Did format in recovery also.
And tried one more time in settings to do factory reset. Got the same situation. again needed to boot factory recovery to release the final cached command that is preventing system from loading.

Are you able to do factory reset from settings, and it works?

No ideal why you are having problems, no I have never tried factory reset from settings. what is the final cached command?

mrmazak · May 18, 2017 at 2:39 AM

vampirefo said:
No ideal why you are having problems, no I have never tried factory reset from settings. what is the final cached command?

still doing google search to learn how to find that out.

when it boots into stock recovery it shows android on back and "erasing" then automatically reboots. like a reset should

vampirefo · May 18, 2017

mrmazak said:
still doing google search to learn how to find that out.

when it boots into stock recovery it shows android on back and "erasing" then automatically reboots. like a reset should

when you boot twrp can you mount system, data, cache?

I just fastboot boot stock recovery, I am not having that problem I am not sure what's going on as my stock recovery opens up and waits for me to use it. You are sure your bootloader unlocked? and you allowed stock recovery to wipe data?

here is my stock recovery https://www.androidfilehost.com/?fid=817550096634770056

upload yours.

mrmazak · May 18, 2017

vampirefo said:
when you boot twrp can you mount system, data, cache?

I just fastboot boot stock recovery, I am not having that problem I am not sure what's going on as my stock recovery opens up and waits for me to use it. You are sure your bootloader unlocked? and you allowed stock recovery to wipe data?

here is my stock recovery https://www.androidfilehost.com/?fid=817550096634770056

upload yours.

I probably am not explaining what is happening too well.

1. from inside lineageOS => settings => backup & reset => Factory data reset

2. this should bring up recovery (whatever recovery is installed) and wipe data and cache
.
.
but it is only rebooting to recovery (my case that is twrp), and stays there .
now , when I select reboot => system it just reboots again to recovery. Tried multiple times.

if i select wipe then reboot again it reboots to recovery.

3. at this point I select reboot bootloader and boot factory recovery.
==>>stock files

4. when stock recovery boots it goes straight to android , open belly and says "erasing" , then it reboots back to OS

I assume there must be a cached command that twrp cannot deal with yet.

the problem described in this thread is similar but i think the solution is going to be different.

https://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386

vampirefo · May 18, 2017 at 11:14 AM

Seems to me the best ideal would be not to use factory reset from settings, if you want to do this then just keep stock recovery installed.

Sent from my Life_Max using Tapatalk

mrmazak · May 19, 2017

vampirefo said:
Seems to me the best ideal would be not to use factory reset from settings, if you want to do this then just keep stock recovery installed.

Sent from my Life_Max using Tapatalk

I didn't leave it alone there.

I went back to stock blu rom. and tried factory reset from inside that rom, with your twrp. And it did the wipe and rebooted like it should have. And FYI, my data was encrypted when I went back to stock, and your twrp successfully de-crypted it

So I think that points to lineageOS, as the source of this bug. And not twrp.

being able to factory reset is not really a big deal, I just seem to be hanging up on this.

mrmazak · May 19, 2017 at 4:34 PM

Thank you for making this recovery and rom.

Have a beer in me

vampirefo · May 21, 2017 at 3:26 PM

mrmazak said:
I didn't leave it alone there.

I went back to stock blu rom. and tried factory reset from inside that rom, with your twrp. And it did the wipe and rebooted like it should have. And FYI, my data was encrypted when I went back to stock, and your twrp successfully de-crypted it

So I think that points to lineageOS, as the source of this bug. And not twrp.

being able to factory reset is not really a big deal, I just seem to be hanging up on this.

I have updated twrp recovery and included a bail out script, bootloop fix script if you like.
twrp recovery is now 3.1.1

use either twrp terminal or terminal from pc.
while in recovery

type

/sbin/para.sh

press enter

now do what ever you want in twrp then reboot to system.

this will prevent twrp from bootlooping.

[ROM][UNOFFICIAL][7.1.2]Lineage-14.1 for Blu Life Max

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member