yashsingh1/xdaforums huggingface dataset:
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Mae7:
So cameras working or not, You mentioned it's hanging?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
It works when you first boot, but after short time it will no longer connect.

Appears to happen more if the selfie side is on. (i never remember if that is front or back)
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] pas7771:
do I flash this rom with system mounted in twrp or umounted? then I need to mount the partition before reboot.

I'm so confused...
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
you shouldnt have to touch the mount

99.9% of the time, unless you are doing stuff in terminal from recovery , the mount screen should look like the photo attached
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] kormend:
So I got rom flashed and gapps loaded all seems fine except wifi won't turn on/connect and also I have no network access via sim1/sim2, flashed slimrom 6 got same outcome, now trying to recover my previous stock rom....

Update stock rom recovered and wifi/network access is restore, so not sure why either Slimrom6/Lineage not allowing wifi/network access, under the system settings IP are showing blank on sim 1/2 and wifi.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
I disabled stock camera and installed open camera now. It has not "hug-up" again since. So as long as this trend holds up, I will just add a note to disable camera. And I do not have gapps, (gapps replaces camera, I do not know if that newer app is better)
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] pas7771:
Ok great I flashed the rom like the picture but still. it always go back to recovery. I tried installing from the internal and from the micro sd card

wipe everything, did all flashing again still it boot in recovery.

my phone is a PRIME BLU R1 HD v 6.6 unlocked successfully with tool V11

what you guys thing I should do now to get at least something going?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
you also had some problem with flashing wrong recovery. right.

perhaps you should also format /data.

from twrp => wipe menu => lower right corner button "format data" => must type "yes" to confirm.

then will need to install from micro sd card. Just in case remove sdcard before format
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] pas7771:
yes, I re-flashed the recovery image from fastboot..

Could I have a boot img partition corrupt ?

I did all the wipe possible, format the data with "yes" re-flashed the rom and still it goes back to recovery

any other solution I can use?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
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
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] armivzla:
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
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
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)
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] 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.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
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.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] seungbaekm:
I re-flashed TWRP in the OP.

It works. Thanks.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] renzofronte:
Hi!!! i need rom in spanish pleaseeeee
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] jasonmerc:
Go to settings and change language?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] PowSniffer0110:
Yeah what the hell you taking about
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] 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.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] majikfox:
This ROM is dead.

404 on the github.

Admin please close the thread.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
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.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] majikfox:
Thanks for the update, the link is working now.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] 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.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] 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 [MENTION=4789334]joedajoester[/MENTION]

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
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] 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?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] sctanf:
I am trying to download this rom but can't find any download links?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] jasonmerc:
I think there's a magisk module for disabling DRM or reworking it or something. I don't have this ROM anymore so I can't test for myself but if you can find it in magisk manager give it a try

I do want to say this too, even though this phone's pretty much dead I can't believe all the attention it got over the years and how it held on for as long as it did
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] pfederighi:
Background (not needed, feel free to skip):

Well, it turns out that no mods or different libraries are needed. I finally figured out that the problem was only related to VP9 decoding. After much searching I found that the MTK VP9 decode library is buggy and some had discussed if there were ways to disable it so that the media library would default back to the Google back end. There was some discussion about deleting references in XML files. Whatever ROM that was for didn't have the files in the same place as CM 13. I did some searching and found two files, commented some stuff out, rebooted, and everything works well.

Solution:

You will need root to be able to edit the files. After saving your changes, you will need to reboot.

Edit /system/etc/media_codecs_mediatek_video.xml and comment (surround with <!-- and -->) or delete the block:

<MediaCodec name="OMX.MTK.VIDEO.DECODER.VP9" type="video/x-vnd.on2.vp9" >

<Limit name="size" min="16x16" max="1280x720" />

<Quirk name="requires-allocate-on-input-ports" />

<Quirk name="requires-allocate-on-output-ports" />

<Feature name="adaptive-playback"/>

<Limit name="concurrent-instances" max="8" />

</MediaCodec>

Edit /system/etc/media_codecs_performance.xml and comment or delete the block:

<MediaCodec name="OMX.MTK.VIDEO.DECODER.VP9" type="video/x-vnd.on2.vp9" update="true">

<Limit name="measured-frame-rate-320x240" range="100-200" />

<Limit name="measured-frame-rate-640x360" range="100-200" />

<Limit name="measured-frame-rate-1280x720" range="50-100" />

<Limit name="measured-frame-rate-1920x1080" range="50-100" />

</MediaCodec>
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] pfederighi:
Here you go. https://drive.google.com/file/d/1wf-5-eJgY0bSqul3_Z68CEB-0ghDjuGM/view?usp=sharing

Thoughts:

Don't forget to make the edits from my previous post so videos play correctly.

Via a kernel manager (like SmartPack) I find that turning on "Schedule workqueues on awake CPUs to save power" and setting I/O "Read-ahead" memory to 384kB - 512kB makes for a smoother experience.

I was never able to get MicroG to fully work. OpenGApps nano works fine.

Netflix doesn't like the ROM even if you have root disabled in Developer Options. Maybe Magisk with its hide option will work. I don't use it enough on my phone to care. Versions less than 5.0 don't care about root and still connect to Netflix's server just fine.

Versions 10.x to 10.62.0 of Google Maps will crash when starting navigation. The recent updates seem to work fine.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] sctanf:
Thank you!
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] pfederighi:
You're welcome.

Something I forgot to mention, if you haven't figured out or read about it already, the Live Display option in this ROM is software based. By default it's on. Turning Live Display off will dramatically improve graphics performance.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] arfelix28:
I am not able to download this file. Cannot find the file. Anyone can help me?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
Sorry for this trouble. I no longer have this file either, I left it here in the "download" tab of this xda project. Last year when. Xda redid their website it must have been lost.

It was a dead project anyway though. I'll look through some of my old hard drive backup images, see if I have an archive
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] pfederighi:
See posts 199, 200, and 202.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
Sometimes while tryimg to fix problems , more problems are made.

Lets try a test next before making more changes.

you said install of rom completed in recovery, And came to complete screen. It should have been almost 5 minutes.

I want you to try to boot from fastboot.

1. unzip the rom file you just flashed.

2. make phone boot into fastboot mode.

3. open terminal window/ command promt

4. open the folder you unzipped rom into

5. in terminal type "fastboot boot "

6. make sure there is a space after the word boot

7. click and drag on the boot.img from unzipped rom folder--drag it into the terminal window

8. the line should look similar to this

"C:\Users\Mr>fastboot boot C:\android\bluR1HD\Slim--6.0.1-R1-HD-Port\boot.img"

9. press enter

let me know what happens
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] pas7771:
@ mrmazak Thanks a lot for your help.

Ok I'm trying your step above will get back soon...

Thanks

---------- Post added at 05:46 AM ---------- Previous post was at 05:13 AM ----------

Okay I did exactly to step 9 and I use your new release 3 rom and boot img

and It still go to recovery flashed the rom, flashed pico gapp, fastboot the boot.img like you wrote and

still it boot into recovery.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
That does not even seem possible. the command given was "fastboot boot boot.img" and your phone is going to recovery.?

You did not do "fastboot flash boot boot.img" did you ?

suggest you do the recommendations from the other thread and boot into stock recovery, to see if a cached format command is hanging you up.

attached is stock recovery.

unzip it and

"fastboot boot C:\Users\*\Downloads\recovery.img"

[need to replace * with your user name]

boot into image NOT flash
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] pas7771:
This is what I did :

C:\adb>fastboot devices

C:\adb>fastboot devices

GEFYSCOJTG6H7SYH fastboot

C:\adb>fastboot boot C:\adb\lineage-13.0-R1-HD-Port-2\boot.img

downloading 'boot.img'...

OKAY [ 0.787s]

booting...

OKAY [ 0.047s]

finished. total time: 0.837s

---------- Post added at 06:18 AM ---------- Previous post was at 06:10 AM ----------

Okay I got the android recovery Blu/full_p6601/p6601

6.0/MRA58K/1466146428

what should I do now.. >> wipe data/factory reset?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
I had a similar problem (no matter what was flashed always boot to recovery) with a different phone. Problem was caused by corrupt misc partition. Booting to stock recovery automatically did a factory reset and fixed it. On that other phone [MENTION=2472806]vampirefo[/MENTION] made a script built into the recovery to help recover from that problem. The fix was to run a command .sh that clears the para/ misc partition.

I am not sure if that same script or command will also work fro this phone,

I have attached the script but caution you to only try it if you know what you are doing.

Try my suggestion to boot into stock recovery. and i will check back tonight when I get home to see if further help is needed.

In the mean time try to detail what you did to get into this problem to begin with. Something obviously went wrong, and the more detailed you can be the more likely the problem will be found.

Vague references with out detail are pointless.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
yes , then reboot fingere crossed lol
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] pas7771:
I did the wipe data/factory reset.

Then it booted to twrp > flashed the rom again and pic gapp and >> it always reboot to recovery again.

something is hanging somewhere... lol

Thanks mrmazak for your help

" On that other phone [MENTION=2472806]vampirefo[/MENTION] made a script built into the recovery to help recover from that problem. "

maybe I need that script to recover my problem. :good:

I saw your script above "para.sh.txt" but I'm not sure what it does and how to apply it
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
just to take some dought out of the equasion, do not flash gapps.

go to wipe>advanced wipe> select all except the removeable sd card> swipe

go back to twrp home screen and install from sdcard rom only
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] kormend:
Any idea why I'm losing network/wifi after install is done? I've done complete wipe and no change....
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
Not exactly. I mean something could be missing in the apns.config explaining the missing cell data, depending on you carrier. But wifi should work.

Will look into it if it becomes a confirmed problem
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] pas7771:
Hello [MENTION=5312578]mrmazak[/MENTION]

I tried a bunch of fastboot command to earase the phone partitions > userdata, system, cache and when booting to twrp

and going to the file manager there is still a lot of files and directory's left?

maybe there is a hidden partition or something or maybe twrp doesn't have the right to wipe?

I'm so confused on that phone. maybe [MENTION=2472806]vampirefo[/MENTION] as well could have an insight if not to busy?

Thanks

Look like the phone might not be wipe properly or twrp is installed in a weird partition that cannot install properly?

I'm not quite sure?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
I am trying to be patient and help. But you are taking extra steps without answering the questions put out. Like please detail the steps that got you to where you are , before making further damage by doing wrong steps, like formating in fastboot.

There will always be files in the directories when searching with recovery. Recovery it self loads files.

I do not have any thing for you to try untill I can understand what was already done.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] pas7771:
Ok I used the tool v11 to unlock the Blu HD R1 v 6.6 PRIME bootloader and went trough the 1, 2, 3, 4 steps succesfully

then in twrp recovery I wiped data, cache, system to start fresh for a new rom and then it went downhill since... anything I flash comeback to twrp recovery.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] roboman2444:
GApps camera definitely works better. No issues after the first reboot.

Also, I haven't been able to get the microphone to work. Using a wired microphone on some cheap headphones works fine, but the builtin one does not produce any sound. Perhaps it isn't switching to the internal mic when not detecting headphones? Based on what I get from sound analyzer, that could be a possible issue.

Reboot didn't fix it.

I will flash the update3 and see if that helps.

EDIT: Update3 didn't fix.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
In between each step. Did your phone work?

Did you wipe all the partitions in twrp, the first time you booted into it. Or did you reboot to Android first?

Also back to first question, you said steps 1 -4. There must be a reboot between these two steps and stock recovery must do a factory wipe. I suspect this is where your problem is.

You have the stock recovery. I suggest you do

"fastboot flash recovery stock-recovery.img" (put full path and proper file name for recovery)

Then repeat the unlock.

"fastboot oem unlock"

Then reboot. (Either with "fastboot reboot" if it works, or long press power button.

This should make stock recovery wipe the phone.

Next "fastboot boot twrp.img" (use full path and file name for recovery image)

Swipe to allow system modification. And then install ROM.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] pas7771:
I flashed the stock recovery and did the oem unlock, then wipe system/data on stock recovery then boot the twrp image

then flashed the rom>> it rebooted in recovery again ( stock recovery)

I noticed the the phone has a 6.0/MRA58K < should be a 6.6/MRA58K could they is is a newer stock-recovery.img?

When I flash the rom in twrp it last 30sec should this be couple minute?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
you should have it. I had you do test with it before. and you told me it loaded and everything..!

you did factory reset with it,

https://xdaforums.com/showpost.php?p=72669116&postcount=23
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] pas7771:
I flashed the stock recovery and did the oem unlock, then wipe system/data on stock recovery then boot the twrp image

then flashed the rom>> it rebooted in recovery again ( stock recovery)

I noticed the the phone has a 6.0/MRA58K < should be a 6.6/MRA58K could they be is a newer stock-recovery.img?

When I flash the rom in twrp it last 30sec should this be couple minute?

Also on stock recovery doing a Root integrity check return as FAIL..
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
no 30 seconds is not correct.

6.0/MRA58K is correct. It is not reletive to version 6.6

please show me picture of phone screen during and after rom install. I want to see all mesages

there is also a recovery log that you might need to pull, later
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] pas7771:
here it is in the attachement
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] pas7771:
here is a kernel log and recovery log form twrp
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
did you verify the md5 of your downloaded lineageOS-13-port.zip?

this line in the log seems to suggest file damage.

minzip: zlib inflate call failed (zerr=-3)
minzip: Can't extract entry to file.
minzip: Error extracting "/system/lib/libvp9dec_sa.ca7.so"

The following clip is from my last slim install, but is a common format for the log

Creating filesystem with parameters:
Size: 2801795072
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 10688
Label:
Blocks: 684032
Block groups: 21
Reserved block group size: 167
Created filesystem with 11/171024 inodes and 22436/684032 blocks
minzip: Extracted 1499 file(s)
created [/system/app/Bluetooth/lib]
created [/system/app/Bluetooth/lib/arm]
created [/system/priv-app/DefaultContainerService/lib]
created [/system/priv-app/DefaultContainerService/lib/arm]
.....
.....
keeps going, but clipped here
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
I got the microphone fixed. and removed the stock camera app. Added open camera to priv-app. seems to be more stable.

still do have not gotten video recorder to work.

I have not put sim card in yet. so do not know about that

uploading v3.5
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
THIS IS NOT THE WHOLE STORY

please tell everything you did and in the order you did it.

Your first post is about google play services crashing. This means you had the rom installed and running. Although it had some problem it did boot and not just going straight to recovery.

https://xdaforums.com/showpost.php?p=72660984&postcount=25
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] pas7771:
Hello [MENTION=5312578]mrmazak[/MENTION]

You right the really whole story is confused on my part and I unfortunately can't remember all the step by step I did.

but it all started with this rom > Slim--6.0.1-R1-HD-Port-x-3.3.zip > it flashed all right but the google play kept crashing..

and I wiped again flashed again then I went to try another roms .. but none really flashed and the phone rebooted to recovery all the time.

UP until today, since the slim rom flashed once I tried the new version > Slim--6.0.1-R1-HD-Port-x-3.5.zip > and to my surprise

IT DID.. no GAPP but It did flashed all right.

I will try the pico gapp and see.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
oh, thats good.