yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] mrmazak:
Thank you for making this recovery and rom.

Have a beer in me
[Miscellaneous Android Development] vampirefo:
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.
[Miscellaneous Android Development] dynoDev:
Does anyone have the stock ROM that they are willing to upload?
[Miscellaneous Android Development] mrmazak:
The stock system image is 2.5 GB

I can upload as image (that way symlinks and permissions stay in tact)

But to what end are you looking for as far as stock rom.
[Miscellaneous Android Development] dynoDev:
Being the idiot that I am I flashed Lineage without making a backup of my stock ROM. I like Lineage and will likely stick with it but it would be nice to have a copy of the stock ROM in case I want to go back for whatever reason.
[Miscellaneous Android Development] mrmazak:
Ok then the system.img and stock boot.img can both be flashed with TWRP will do.

I need some time to let upload finish to post a link. And I'm not at PC now , so tonight will add system to my life max folder on file host, that I posted earlier.

And if you go back to stock. And want to root systemless root works by just installing SuperSU with an override set in TWRP, because the install detects wrongly that system mode will work. And system mode will not allow phone to go past the boot animation. (Dm verity in boot)

To get systemless to install need to use an override.

From recovery--> advanced--> terminal-->. Type

echo "SYSTEMLESS=true" > /data/.supersu

Stock images are here ==>link
[Miscellaneous Android Development] dynoDev:
Thanks mazak! I really appreciate it. One thing I notice is that when I go back to Marshmallow my fingerprint scanner still doesn't work. This happens with the stock ROM and Vampirefo's version of Lineage 13 for this device. I'm guessing there is something obvious I'm missing but everything else seems to work except the fingerprint scanner which strikes me as odd.
[Miscellaneous Android Development] mrmazak:
Strange. Mine worked when I went back to stock. Did you also go back stock boot? And wipe data.
[Miscellaneous Android Development] dynoDev:
I think I did. Are you aware of a specific order that needs to be followed? From Lineage 14 I went into TWRP and wiped the data then flashed the stock boot and system files. It hung on the boot animation for a while then encrypted the files then rebooted into the stock system. Looks normal except for the fingerprint. I'll play with it some more and see if I can figure it out.
[Miscellaneous Android Development] mrmazak:
No special order.

In lineage trying to open the fingerprint sensor setting makes the settings app crash, that is how it is characterised not to work.

What is symptom of not working for you back on stock?
[Miscellaneous Android Development] dynoDev:
My mistake, it does work with the stock ROM. I am also able to make my phone crash/restart in Lineage 14.1 by going into the fingerprint settings twice in a row.
[Miscellaneous Android Development] mrmazak:
[MENTION=2472806]vampirefo[/MENTION] is this link of any use?

It has links to many (32 bit kernel) rom links for mt6737. And says there is a fix directions for fingerprint. I only browsed it from phone so did not get deep into the contents.

https://w3bsit3-dns.com/forum/index.php?showtopic=776302&st=200

I am not able to make sense of the "fix" that is described in there. I did find the "patch" that is mentioned as a download, but it was suspicious an iso file which had another zip inside, then an exe inside there. I had opened them in anti-virus sandbox but still didn't trust to open it further.

**Update

I found in the stock boot.img ramdisk something that "might" be missing from lineagaOS

Ueventd.rc has a section for fingerprint in the stock version.

I am trying to see it adding that section will help.

If so I will document it

the new boot.img change did not seem to work

to document anyway

the following lines are in ueventd.rc from stock boot.img but not in the 14.1 boot

#add by chenxuanyu for HD_GF66xx FINGERPIRN
/dev/gf66xx-spi 0666 system system

# wpf add for MA_A121N FINGERPRINT
/dev/madev0 0666 root root
/dev/elan_fp	0666 root root

**update 1.1

I don't know what this could mean, but. With the lines above added into the ramdisk file. the fingerprint sensor seems to get warm.

default.prop

could this line help?

ro.support_gf368_fingerprint=1

I will have to try.

I dont like testing on my daily. I might buy a second max to continue.
[Miscellaneous Android Development] vampirefo:
I updated my LineageOS 13, compiling Slimrom now with upload those later to needrom.
[Miscellaneous Android Development] mrmazak:
Nice , My second max should be here Saturday, will like to try those out.

Have been using this 14.1 and back to stock all week , and really like the fingerprint in stock. But I keep finding more questionable things with the stock rom, I do not like.

1.camera app needs permission to make phone calls and send texts

2. when i do a factory reset there are four junk (empire, zcamera, canddy pop, ) apps that show up in app drawer, there is no app folder for them, they are getting installed by an app called "IgniteBluOEM" --- google shows me "Ignite" is a adware generator

/rant

I have slim-rom on my fire tablet and I haven't felt the need to change anything on that and its running 5.1.1 , so I think I will like very much to try yours on this phone.
[Miscellaneous Android Development] vampirefo:
All my 6.0 ROMs fingerprint scanner works on, won't work on any 7.0 ROM.

Yes Blu loves the adware/spyware stuff.

Update both roms have been uploaded as well as latest TWRP

https://www.needrom.com/author/vampirefo/
[Miscellaneous Android Development] mrmazak:
Is it a description problem or is the fingerprint scanner an issue on the slim-rom?
[Miscellaneous Android Development] vampirefo:
Fingerprint scanner works just fine on slimroms.

I am running slimroms on my phone right now, fingerprint scanner is working just fine.
[Miscellaneous Android Development] mrmazak:
Thanks. The description on need-a-rom says it is an issue.
[Miscellaneous Android Development] vampirefo:
It was suppose to say no known issues, anyway removed that line.
[Miscellaneous Android Development] SamarV-121:
Is YouTube Videos work fine? [MENTION=2472806]vampirefo[/MENTION]
[Miscellaneous Android Development] vampirefo:
I have slimsrom installed right now, and yes YouTube works just fine, I am watching Epic Rap Battles of History right now.
[Miscellaneous Android Development] dynoDev:
[MENTION=2472806]vampirefo[/MENTION] I flashed your slimrom and everything works except the fingerprint scanner. If I go back to stock the scanner works again. I was having the same problem with Lineage 13. If I go to set up a fingerprint it doesn't register when I touch it. In stock it vibrates when touched and asks you to move your finger and touch again. On Lineage13/slim I get no response. I was wondering if this could have anything to do with the kernel version? In the pictures on needrom you show the Nov 23 2016 kernel but when I install I get a kernel from yesterday. If i flash the stock boot.img I show the Nov 23 kernel but still do not get functionality. Any suggestions of what I might look into?

Has anyone else gotten the fingerprint scanner to work outside of stock?
[Miscellaneous Android Development] vampirefo:
I don't know what your problem is, fingerprint scanner works just fine on slimsrom, CM13, and any other android 6 rom something is wrong with your phone, you should return it or it's user error.

The kernel date would be may 25 or may 26 2017.

Stock boot.img wouldn't work correctly on a custom ROM, stock boot.img is for stock ROM, sounds more and more like user error.

cat /proc/version
Linux version 3.18.19 (vampirefo@vampirefo-OptiPlex-760) (gcc version 5.3.1 20160401 (optimized) (UBERTC-5.3.x) ) #1 SMP PREEMPT Fri May 26 20:10:05 EDT 2017

Here is slimsrom boot.img

https://www.androidfilehost.com/?fid=889764386195902318
[Miscellaneous Android Development] vampirefo:
Here is pics of slimsrom just now taking a fingerprint.

This is the last post on slimsrom, this thread is about Lineage OS 14.
[Miscellaneous Android Development] dynoDev:
If you boot into the factory test mode (with power off, hold vol down then press power) does the fingerprint test work?
[Miscellaneous Android Development] vampirefo:
Of course not, cause it's not enabled in custom ROMs, that is only for stock ROM.
[Miscellaneous Android Development] mrmazak:
I just received my second life max in mail today. It has different version from first one.

Do you want the new boot.img?
[Miscellaneous Android Development] vampirefo:
V15?

My stock ROM was already updated to V15, or do you have a different version that V15?
[Miscellaneous Android Development] vampirefo:
I already have that version.
[Miscellaneous Android Development] mrmazak:
oh. no

My first one was at v14. I didnt know there was an update
[Miscellaneous Android Development] vampirefo:
Yep, update came out sometime ago.

All my ROMs use V15 blobs, that's what fixed the camera in my earlier ROMs. V14 blobs made camera have a pink tint, V15 blobs fixed that.

This link and pic shows when I got the V15 update.

https://xdaforums.com/showthread.php?p=72226094
[Miscellaneous Android Development] mrmazak:
I even saw that post. Butdidnt put it together there was an update on the max, I thought you somehow used the R1 update blobs to fix it.

Anyway. Can you show me the updater-script from the update please.

I want to copy the "set_metedata section" to make a flash file back to stock. I think it can be made smaller than the system.img I have been using
[Miscellaneous Android Development] vampirefo:
I didn't save it, I didn't see any need for it, you can flash your V14 and then run update, it will download the update for you.
[Miscellaneous Android Development] mrmazak:
Is there a benefit to this ROM being built as an emulator?

or is that what is needed to have fingerprint scanner,maybe.
[Miscellaneous Android Development] vampirefo:
Some of the scanner files aren't compatible with android 7.
[Miscellaneous Android Development] mrmazak:
I just meant to ask about , in build prop on "ro.build.characteristics=emutator"

And in settings instead of "about device" it says "about emutated device"
[Miscellaneous Android Development] vampirefo:
Those mean nothing, when building rom, one can put anything here

example

ro.build.characteristics=default

ro.build.characteristics=phone

ro.build.characteristics=tablet

ro.build.characteristics=airplane

if nothing is specified then LineageOS just uses emulator
[Miscellaneous Android Development] sdt1:
Help unlocking bootloader

First, thanks [MENTION=2472806]vampirefo[/MENTION] for making Android 7.1 possible on the BLU Life Max! Although, I really do like my fingerprint scanner, I'm hopeful that can be made active again in future. Second, I can't find any reliable information regarding how to unlock the bootloader. From what I have read, it seems the bootloader has to be unlocked before you can root. And, root is necessary before you can flash the new ROM. The tutorial in this thread seems to start after the bootloader is unlocked, or at least after TWRP is installed. I can't figure out how to get TWRP installed?? So, would you be able to list all the steps for a newbie like me from start to finish? I would be very grateful. Also, I tried Kingroot and Kingo Root prior to finding this thread, neither of which worked on the BLU Life Max, and left me with malware on my PC....
[Miscellaneous Android Development] mrmazak:
This phone , unlocking bootloader is just done the "official" way. No hack or trickery needs to be done.

1. become developer on device and enable developer options.(open settings, scroll down to about phone, tap build number 7-9 times, go back one menu, now above "about device" there is developr options)

2> enable adb

3. enable oem unlocking

4. open cmd or terminal and type "adb reboot bootloader" (assumeing you have adb and fastboot setup on pc)

5, phone should have rebooted, now verify connection by typing "fastboot devices" (should get response on terminal with fastboot and the device serial number)

6. type "fastboot oem unlock" (this will factory reset device and wipe the date partition)

6a. you will need to interact with device and push volume up to confirm the unlock

6b. when this completes, type "fastboot reboot"

7. just skip through setup device with setup wizzard

8. become developer again and enable usb debuging again

9. adb reboot bootloader

10. fastboot boot (enter the location of your downloaded recovery img)(you can drag the file from explorer to the terminal window and the path will be filled in)

11. twpr recovery should have booted

12. DO NOT modify system at this point!!!!!

13. make FULL backup of all partitions(optional - by preference)

14. now you have a functioning recovery and have not changed phone at all

15. next after verifying recovery boots and works on your phone. will flash the recovery

16. adb reboot bootloader

17. fastboot flash recovery (enter the location of your downloaded recovery img)(you can drag the file from explorer to the terminal window and the path will be filled in)

18. this step is to try and make sure the stock recovery does not overwrite the new twrp

18a. fastboot boot (enter the location of your downloaded recovery img)(you can drag the file from explorer to the terminal window and the path will be filled in)

18b. when recovery boots fully "adb reboot recovery"

19. now when twrp boots it should have screen asking if you want to allow system modification. swipe to yes.(each time you format userdata. or do factory reset will have this screen again)

No need to install supersu to root prior to flashing new rom because root is done on the /system partition or /boot and both get replaced when installing rom.

from here down the directions on the OP and the needrom site with the rom file take over.
[Miscellaneous Android Development] mrmazak:
Blu has released a phone with the same process or as this one, it has fingerprint sensor and android 7

http://www.bluproducts.com/devices/r2-lte/

Problem is it seems there is no listing of where to buy it yet.

Here is hoping that the libs from it will help get fingerprint and Bluetooth working on this one
[Miscellaneous Android Development] vampirefo:
Bluetooth works just fine, fingerprint needs correct libs from Android 7.
[Miscellaneous Android Development] mrmazak:
Doesn't Bluetooth only work if you force it be in mono instead of stereo?
[Miscellaneous Android Development] sdt1:
This R2 LTE looks promising. When you click the "Buy Now" button it returns to the same. I called BLU customer support to see if A) there is a planned OTA upgrade to Nougat for the Life Max , and B) if the R2 LTE is available for purchase, and if so, where. As expected, BLU customer support is useless. I was connected with someone in the Philippines who barely spoke English, and gave me the run around. The end result after explaining myself over and over again, there will be NO upgrade to Nougat for the Life Max, and they have no idea where the R2 LTE will be sold! LOL!

---------- Post added at 09:19 AM ---------- Previous post was at 09:16 AM ----------

This is what I thought too. It's fine to use BT in mono for a phone call, but not ideal for listening to music.

---------- Post added at 09:22 AM ---------- Previous post was at 09:19 AM ----------

Thank you for this step-by-step [MENTION=5312578]mrmazak[/MENTION]! Much appreciated! One last bit -- where should I look for the adb and fastboot install for my PC? I found the minimal adb and fastboot available from [MENTION=3558630]shimp208[/MENTION] here on xda, so I thought I would try that. https://xdaforums.com/showthread.php?t=2317790
[Miscellaneous Android Development] mrmazak:
I usually point people to this adb and fastboot. 15 second setup.

https://xdaforums.com/showthread.php?t=2588979
[Miscellaneous Android Development] sdt1:
Thanks [MENTION=5312578]mrmazak[/MENTION]. I wound up using the minimal adb and fastboot I had quoted, and it worked flawlessly, as did your instructions. Cheers.
[Miscellaneous Android Development] sdt1:
Thank you to [MENTION=2472806]vampirefo[/MENTION] and the entire lineage team for this OS! So far, it's working flawlessly. If/When the fingerprint reader and stereo BT libs become available for this OS, can it be installed over top of (like GApps), or will it have to be a wipe and install? I ask because the automatic updates in Settings > About > System Update gives an error saying unable to connect, despite having internet connection wi-fi or cell data.

One other issue I've noticed, is that when charging with power off, the screen does not sleep, and the battery image doesn't show the percent charged? Also, what happens if BT Mono isn't installed or running? BT is still on and connecting to devices -- would there just be no sound?

Lastly, I noticed that all apps with ability to use fingerprint scanner for security, still recognize that a fingerprint scanner is installed. If the hardware is recognized, why can't it be made to work?
[Miscellaneous Android Development] mrmazak:
The hardware is not recognized. But the boot image and kernel are setup for fingerprint. So system notified apps , by certain config files, that there is a fingerprint sensor. That's why apps report the sensor.
[Miscellaneous Android Development] clu1688:
HELP Please.

I just rooted another phone yesterday and in that excitement I tried the same method on Blu LIfe Max.

When I started I did not read this post and now I am in some trouble. Hope to get some help here, please. I really like this Blu Life Max and wanted so bad to root it to get rid of ads.

Here is what I did prior to reading this thread/guide: (reference to post #57 by mrmazak.)

I did all the way to Step 6a without problems, then, I did not follow step 6b, thus did not become a developer again and did not enable debugging again.

then I used fastboot to flash custom recovery img, this one, TWRP_Max_recovery.img

then I saw the touch didn't work. When I shut it down, and turn it on, it starts boot looping.

I have tried to use Vol and Power buttons to get in TWRP recovery, but however I tried, it goes into boot loop every time.

I have attached some photos here to show the booting screens in the process.

Please advise on how I can send command to the phone again, and make it work, many thanks,
[Miscellaneous Android Development] mrmazak:
This thread is for lineage-14.1 the [MENTION=2472806]vampirefo[/MENTION] has made. So this is off topic. Unless you are trying to install his rom, and got in this situation.

I assume your boot looping is flashing the twrp screen. And that would be because you did not reboot after the oem unlock. The reboot is needed and is needed to be done with factory recovery(at least to make is easier it should be done with factory, so it updates the sec.conf partition)

because you straight away flashed twrp, and the broken version, at that. The needed factory wipe of data did not happen.

You should be able to restore factory recovery with sp flashtool.

If that was the only problem. then if you flash the stock recovery back with sp flash tool, and reboot it should factory reset and be ok, then once rebooted you can do the twrp and rom install.
[Miscellaneous Android Development] clu1688:
Thanks mrmazak!

I didn't mean to hijack this thread. I was reading this threat for knowledge. Honestly I was not planning to use this ROM until I read the security/privacy issues with stock ROM (e.g. Camera has excessive permission etc.) This made me worried and I am now thinking to flash this ROM to get rid of Blu/Chinese OEM apps. (I don't care finger print scan anyways)

My question is, the phone is off, and if I turn it on (cannot turn it into Recovery by using buttons), it will go into boot loop. How do I use PC to send command to the phone?

I tried adb devices with phone off, phone is not listed.

Again would appreciate expert advice!

Update:

I will download the SP flash tool tonight and give it a try. I assume sp flash tool would work with the phone even when the phone is off?
[Miscellaneous Android Development] clu1688:
Today's news.

https://www.cnet.com/news/these-cheap-phones-are-costing-you-your-privacy/#

Can I assume Lineage ROM will not have the ADUP's hidden apps?

Thanks,
[Miscellaneous Android Development] mrmazak:
Did it help
[Miscellaneous Android Development] clu1688:
[MENTION=5312578]mrmazak[/MENTION],

It should, but unfortunately not yet. I have spent 3 hours tonight and still have "MTP USB Device" problem, thus SP Flash Tool cannot push the file to the phone.

I use Windows 7 64bit Dell. VCOM driver seems OK, but cannot fix the "MTP USB Device" problem.

I need to borrow another laptop which might have working drivers from R1HD time.

Thanks for asking, would appreciate any tips,
[Miscellaneous Android Development] mrmazak:
well you shouldn't have mtp usb devices when phone is off and connecting to sp flash. vcom is only driver you need set up for flash tool.
[Miscellaneous Android Development] clu1688:
Update,

On a different laptop with Win7, driver installation is strange, at one time it says VCOM driver is OK, and MTP USB Device is OK, but asked me to reboot. After reboot the MTP USB Device says not working.

Anyhow, I ran the FP FLash Tool, load it up, clicked DOWNLOAD, nothing happens for like 2-3 minutes, (no progress bar), the there is a pop-up message (see attached). The message says: "CHIP TYPE NOT Match ,,,,,"

As a noobie, i am at wits end. This is beyond my level. Would very much appreciate some expert advice! Thanks,
[Miscellaneous Android Development] vampirefo:
This phone is a 6737 not a 6735 so it's a mismatch, wrong scatter file.
[Miscellaneous Android Development] mrmazak:
Thats the scatter file miricle box gave. But you are right it has wrong chip type.

I can try it on my phone to veriy if it works.

edit:

yeah it did not work. I tried myself with (MT6735 -the way it does work in miricle box, MT6737- the way sp flash recognizes the chip, and MT6737M- the way it is listed in build.prop) none have worked.

This is turning out to be a flaw with this phone. -- No hardware button combo to boot to fastboot mode. (if could boot directly to fastboot mode -sp flash tool not needed)

I have susscsefully used miricle box to both back up and restore this phone. I have used sp flash tool to test backup (read) but am having trouble makeing the download (flash) to work . The scatter error message keeps coming

I was using version 5.1548 of flash tool. It loaded scatter file with all three chip type names. And gave BB_chip type mismatch.

I updated to newest version of spflash tool. 5.1712 and it gives message that MT6737 is not supported by flash tool. , so that must be the problem.

I beleive the only option is to use miricle box to get you back running again.

https://forum.hovatek.com/thread-13894.html
[Miscellaneous Android Development] Infra.Red:
Video Recording on Stock camera works?
[Miscellaneous Android Development] vampirefo:
Use this one, I find hand making them works better.

https://www.androidfilehost.com/?fid=745425885120752338
[Miscellaneous Android Development] mrmazak:
My testing failed three times.

I used the file as you supplied scatter set to 6737m

then set to 6737

then set to 6735
[Miscellaneous Android Development] vampirefo:
Works just fine for me, I use Linux version

USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
connect DA end stage: 2, enable DRAM in 1st DA: 0
COM port is open. Trying to sync with the target...
DA Connected
executing DADownloadAll...
download speed: 15.65Mbps.
Disconnect!
comboTimeout index(3) saved.