[2017-10-23][7.1.2] LineageOS 14.1

[mrmazak]

Same error
With they recovery You provided above

Your erors are very , very different to each other.

your first error 7 shows it is from an issue mounting the /system partition.

your second error 7 shows it is because the recovery reports device model different then the rom is looking for.

I know the device type reported from the recovery is going to be wrong because that is the recovery I ported from the life-max phone, and did not change the device type.

the second error can be fixed by modifing the updater-script inside the rom zip file.
but the first error has me uncertain so far.

open the zip file. then open these folders
MEATA-INF
com
google
android

open updater-script

use notepad++ not standard windows notepad

put a # in front of the "assert"
so this line

assert(getprop("ro.product.device") == "p6601" || getprop("ro.build.product") == "p6601" || abort("E3004: This package is for device: p6601; this device is " + getprop("ro.product.device") + "."););

gets changed to this

#assert(getprop("ro.product.device") == "p6601" || getprop("ro.build.product") == "p6601" || abort("E3004: This package is for device: p6601; this device is " + getprop("ro.product.device") + "."););

 

[AndroidBR]

Same error
With they recovery You provided above

Oh crap. Have you tried to download the ROM again from a desktop and load it to your phone? It could be the zip file itself.

 

[khyr]

Oh crap. Have you tried to download the ROM again from a desktop and load it to your phone? It could be the zip file itself.

I don't know if anybody more is facing the same problema than me

 

[jianC]

I updated OP with zhaofengli/my version of TWRP recovery.

This one is guaranteed to have the correct partitions and device name to flash this rom and is compiled from omni rom source.

There seems to be several ports of TWRP out there with different device names.

Also updated OP with some more instructions per request..

 

[jianC]

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?

Installing a different camera app won't help us at all here because the camera libs (which all camera apps depend on) fail silently when loading.

 

[zombie_ryushu]

I'd like an update on the functionality of this ROM.

 

[initguru]

Great job, thanks op!
I'm wondering about bluetooth and gps functionality before installing this, does anybody try this?
I heard in other roms that gps disconnect continuously, so I would like to know that is fixed at least.

 

[AndroidBR]

Didn't want to pollute this thread, please forgive me for OT. But I wanted to let you guys know that some Walmart stores are doing a clearance sale on the Moto G5 Plus 4GB 64GB unlocked for all US carriers for just $154.
PM me if you want to find out if a local Walmart store still has them in stock. It's a great device with tons of custom ROMs and kernels from famous devs. Just wanted to share the love with you.

Back on topic, I'm really anxious to give this Nougat ROM a go on my R1 HD, but first I need to get my G5 up and going. I'll probably give you guys my feedback in a day or two.

Cheers!

 

[jabashque]

Bluetooth audio is broken; when connected to a bluetooth audio sink, any audio/video steam refuses to play until I disconnect from the bluetooth sink AND restart the app.
logcat and dmesg attached.

 

[jianC]

Bluetooth audio is broken; when connected to a bluetooth audio sink, any audio/video steam refuses to play until I disconnect from the bluetooth sink AND restart the app.
logcat and dmesg attached.

Thanks for the logs. I will look into the BT issue.

As for GPS, I have not tested long term stability. I tested with google maps and YGPS and I get a fix pretty quickly.

 

[zombie_ryushu]

This needs more attention than its getting. keep in mind all BLU Stock roms are vulnerable to the KRACK vulnerability. While I am glad that Nougat, and a version of Nougat that is patched against KRACK, runs on the R1 HD, the lack of a front facing camera is a huge non-starter. I use wired headphones, so while Bluetooth Audio would be nice. Its not explicitly a non-starter. As far as GPS goes, I use UnifiledNlp and Osmand~

 

[ruchg1]

Just a suggestion:

mmrazak's LineageOS 13 ROM has fully functional Bluetooth. It's actually better than stock because the Lineage ROM actually syncs with my Pebble and shows battery info for my Bluetooth headset.

Maybe you could look at the Bluetooth stack from that ROM?

 

[jianC]

This needs more attention than its getting. keep in mind all BLU Stock roms are vulnerable to the KRACK vulnerability. While I am glad that Nougat, and a version of Nougat that is patched against KRACK, runs on the R1 HD, the lack of a front facing camera is a huge non-starter. I use wired headphones, so while Bluetooth Audio would be nice. Its not explicitly a non-starter. As far as GPS goes, I use UnifiledNlp and Osmand~

I agree too. However devs only have so much time on their hands...

Just a suggestion:

mmrazak's LineageOS 13 ROM has fully functional Bluetooth. It's actually better than stock because the Lineage ROM actually syncs with my Pebble and shows battery info for my Bluetooth headset.

Maybe you could look at the Bluetooth stack from that ROM?

I don't have the source for that ROM. I'll see what I can do.

 

[zombie_ryushu]

I want to somewhat Clarify my stance. I see no reason the R1 HD can't run Nougat or Oreo. The problem is the Drivers for the camera. The issue is the drivers are binary blobs we don't have the source for. There are two solutions.
1. An open source driver.
2. Find Binary Blobs from another device, say the Blu R1 Tank and then extract the Binary blobs from that device and include them in the Rom for all other bulds... This requires the donation of a BLU Device running Nougat. But it should only require one device.
3. BLU Updates the R1 HD Stock Rom to Nougat. Likely not going to happen.

BLU is using this as a revenue stream. BLU has not issued a patch for Marshmellow based devices that protects them against KRACK. I don't believe they will. That would require them upgrading the R1 HD to Nougat. The message I am getting from BLU on this is: You want to be patched against KRACK? Buy a new device from us. Boy that makes me furious.

Option 1 would Future Proof the R1 HD. Option 2 would 'buy us time' to implement option 1. Maybe even do something about the BLU Studio 5.0CE I have.

 

[mrmazak]

I want to somewhat Clarify my stance. I see no reason the R1 HD can't run Nougat or Oreo. The problem is the Drivers for the camera. The issue is the drivers are binary blobs we don't have the source for. There are two solutions.
1. An open source driver.
2. Find Binary Blobs from another device, say the Blu R1 Tank and then extract the Binary blobs from that device and include them in the Rom for all other bulds... This requires the donation of a BLU Device running Nougat. But it should only require one device.
3. BLU Updates the R1 HD Stock Rom to Nougat. Likely not going to happen.

BLU is using this as a revenue stream. BLU has not issued a patch for Marshmellow based devices that protects them against KRACK. I don't believe they will. That would require them upgrading the R1 HD to Nougat. The message I am getting from BLU on this is: You want to be patched against KRACK? Buy a new device from us. Boy that makes me furious.

Option 1 would Future Proof the R1 HD. Option 2 would 'buy us time' to implement option 1. Maybe even do something about the BLU Studio 5.0CE I have.

Here is a good list of available roms from BLU for other devices, some of them are NOUGET 7.0 . Find one that you want to try and let us know how you do.

anxiously waiting for your fix. Much appreciated thanks in advance.

https://www.needrom.com/category/blu/

 

[zombie_ryushu]

Here is a good list of available roms from BLU for other devices, some of them are NOUGET 7.0 . Find one that you want to try and let us know how you do.

anxiously waiting for your fix. Much appreciated thanks in advance.

https://www.needrom.com/category/blu/

Okay so I didn't know the BLU R2 had been dumped. That has Nougat. Has a Nougat Rom for the R1 HD been built with the Camera Driver for the R2?

 

[mrmazak]

Okay so I didn't know the BLU R2 had been dumped. That has Nougat. Has a Nougat Rom for the R1 HD been built with the Camera Driver for the R2?

cannot / have not found any

and so far I can't even unpack any of the images from that link. They are all "official" and are signed images, not sure if that is the problem or what. But I usually use "Ext2explore" on windows to unpack system.img or SuperR kitchen on ubuntu to unpack images. But both of them fail with the images from the "official" blu roms I downloaded from need-a-rom

edit:
not only am I not able to unpack the system.img . But recovery.img and boot.img do not unpack.

 

[zombie_ryushu]

cannot / have not found any

and so far I can't even unpack any of the images from that link. They are all "official" and are signed images, not sure if that is the problem or what. But I usually use "Ext2explore" on windows to unpack system.img or SuperR kitchen on ubuntu to unpack images. But both of them fail with the images from the "official" blu roms I downloaded from need-a-rom

Okay, I may be ble to help here as this impacts something I found when I dumped a rom using SP Flash tool.. When SP Flash tool Dumps not just the System and user Partitions, but everything. The Preloader, the NVRAM, the Recovery, the System, and the User Partition. Its all one giant blob. The scatter file from the Rom dump is required to tell one Partition of the rom from another, using it, you then need to use the scatter file to tell dd where to start and stop cutting the system.img portion of the. The result is normally a complete image of an ext2/3/4 mountable image.

The scatter file is the key, without it, you can't tell where part of the rom starts and stops.

 

[mrmazak]

Okay, I may be ble to help here as this impacts something I found when I dumped a rom using SP Flash tool.. When SP Flash tool Dumps not just the System and user Partitions, but everything. The Preloader, the NVRAM, the Recovery, the System, and the User Partition. Its all one giant blob. The scatter file from the Rom dump is required to tell one Partition of the rom from another, using it, you then need to use the scatter file to tell dd where to start and stop cutting the system.img portion of the. The result is normally a complete image of an ext2/3/4 mountable image.

The scatter file is the key, without it, you can't tell where part of the rom starts and stops.

True scatter is needed for that situation but you can see in the photo, this rom is already seperated into individual files.

 

[zombie_ryushu]

Okay. think I have an explanation. The Superblock on the image is being offset by the signing data. It will take a hex editor to figure out where the Superblock has been moved to, in system-sign.img, then in Linux, it will be necessary to pass that offset to the mount command.