yashsingh1/xdaforums huggingface dataset:
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] krbvroc1:
Mine said Android version 6.0 under About Device.

---------- Post added at 12:07 AM ---------- Previous post was at 12:02 AM ----------

Nope - did factory reset and flashed - did not work still looping the logo. One very odd thing - if I interrupt the looping and goto fastboot mode and I run 'fastboot boot boot.img' (where boot.img is from coltons normal-stock-oob.tar.gz v12), the phone boots into v17. But once I reboot it is back to the looping unless I manually run fastboot. Any idea why or how to recover?

My phone was encrypted - not sure if this somehow caused issues.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] shawnchalfant:
I just want CM, tired of this crap version of thiers.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
Your more than likely gonna need to do "fastboot OEM unlock" again.

Then "fastboot format userdata"

The update applies new signatures and that makes the phone try to do a secure boot, and having bootloader unlocked is not able to do secure. You can verify by doing "fastboot getvar all" near end of output look for

"bootloader unlock: yes"

And

"Secure: yes"

This combination usually does boot loop like you have. Doing unlock again gets you

"Secure: no"

Then it needs to do format userdata. Either with stock recovery or "fastboot format userdata" if custom recovery is installed.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] krbvroc1:
Yes, it seems that secure:yes was set and after I ran the unlock that got out of the bootloop. However I reinstalled my magisk and superuser (via twrp) and the device just does have root. could this new ota have done something to remove root even though it worked before.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
I do not know what is happening to your phone now. I think you formated and installed vampirefo's released rom, after an actual ota.

Vampirefo rom does have root so it is looking like the supersu you are using. just use the same supersu as this forum has suggested.

supersu v2.76
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] krbvroc1:
You are probably correct... After the actual ota and the bootlooping, and then running the flashing unlock command, I flashed his boot.img. (not the system or recovery). It occurred to me that maybe the problem was the phone was already rooted, but in this post he says, 'This is a Prime stock 6.5 rom, this rom comes from my phone, not rooted unmodified stock rom.' So I took that to mean he did not root it. Which thread references the supersu as this forum has suggested?...While troubleshooting I looked and could not find anything. Granted this has been a frustrating process and I have tried many things. The SPFT not working anymore caused me grief. Amazon has issued me a refund so I am considering returning the device (I have only had it 2 months). As someone who paid extra for the OEM version I shouldn't have to suffer any lockdown.

Is there somewhere for me to get the v17 stock boot.img instead of vampireinfos so I can return to native?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Tiggam:
Regular boot image is in this update post.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] krbvroc1:
I had already looked at that post. I unzipped that update.zip file and did not find any boot.img in the zip file. There was only a boot.img.p patch file. Am I missing something?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Tiggam:
Sorry about that, I took a quick look and you are right.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Unscedeo:
I'm pretty sure there is a fix to this, but...

I just flashed vampirefo's V17 stock ROM. I used to be on Stock V12. I flashed the V17 ROM after clearing system, internal, data, and cache (clean flash).

I just flashed it yesterday, but when I went to change my boot animation through Solid explorer (I gave my explorer root) it gave me an error saying "Unable to remount the file system under /system". So I thought this was just related to the the explorer, but when I tried it with Amaze, nothing happened to the files, so it didn't work. I also tried to adblock with AdAway, and I got an error.

Everything that I mentioned before was working on the Stock V12 ROM. I don't know if it's a formatting issue, or what, but I really need help with this.

Screenshots are posted below, and any help would be appreciated.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mmigliore:
Prime 6.5/6.6/7.4.2 OEM V12/V17 flashed via Twrp recovery.

I guess I'm staying on 7.42 for now. It's running fine rooted and xposed on that. I was just wondering if I would lose ability to root. If I would it's not worth it to go to V17, at least at this point to me. And, I did no OTAs, if that matters.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Tiggam:
So the differences between v12 and v17 are:

Security updates

Band 12 LTE

Removal of OEM Unlocking and Navbar settings menu items

Substratum themes no longer work

Are the security updates actually vital?

I'm no developer, I've ported exactly one rom before, but there seems to be space for some sort of composite rom.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
You can go back to v12 or use any version you want, V17 just brings non prime up to prime level of security.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Tiggam:
I know, I keep twrp backups of v12, and 6.6 as a just in case. Just wondering if the security patches can be achieved without loosing other features.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
Would require a lot of work, for so little gain, decomiple setting apk and find the difference and rebuild them, I have no interest in doing it.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Tiggam:
I wasnt' asking you to do it, just curious as to what was involved. That was answer enough. And you have certainly done a ton I'm already thankful for.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
i realize it is same thing. Little gain lots of work. but,

I comented(removed) the patch lines that are related to setting.apk, setting_provider.apk, and settings.jar.

would that be enough to achieve the desired security update without the loss of options in settings or is there also some new settings that are needed to enable volte as well.? I don't know.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
Not the same, you can't get the new features of V17, by using V12 apps, you would need to decompile each, find the features you want from V12 or V17 add them to V12 or V17 app.

My guess doing it your way, phone won't boot, as the V12 apps don't have the correct signature as V17 apps.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
Where is the nav bar settings?

edit

Never mind I see it under display.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
I did roll back settings app, now OEM unlocking is displayed.

I don't know what this nav button everyone is talking about is, where is it at?

edit

Never mind I see it under display.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
I have Navigation bar working under display.

I also have OEM unlocking working under Developer options.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Tiggam:
You are awesome, thank you.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
Settings_V17.zip has been added to OP, flash via twrp.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] stormy1777:
Sorry for the basic question here :) I have a rooted/twrp'ed R1-HD flushed with: BLU_R0011UU_V12_GENERIC, running great.

Got the OTA prompt suggesting to move to: BLU_R0011UU_V17_GENERIC_V6.0-20161115-1444

I'm interested to move to V17 for the security updates (oct/2016).. however, in this original post, only this file has V17 in the name:

stock_V17_OEM_rom.zip

Is this the one to install using TWRP?

There are also these files:

1) Modified_rom_R1HD_7.4.2.zip

2) Modified_rom_R1HD_6.6.zip

will these also get me to V17?

Looking at their build.prop file it seems an OLDER (?) version:

ro.tcustom.build.version=BLU_R0010UU_V7.4.2_GENERIC

meaning, BLU_R0010UU_V7.4.2_GENERIC seems older compared to say: BLU_R0011UU_V17_GENERIC, by "R0010" vs" "R0011" as well as the "V7.4.2" vs "V17".

Can someone explain what these 3 roms are? what is the "best" to install via TWRP?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Tiggam:
Best depends on what you need. V17 is new, for non-prime but is essentially the same as the prime 7.4.2, in that it include security updates.

You can use v17 or 7.4.2 depending on your preferences
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] yaconsult:
But it also says that it contains the VoLTE update, which is a big deal for t-mobile users - much better interior range on the lower frequency band 12.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mmigliore:
Doesn't 7.42 have that too, or does that just add T-Mobile Band 12 update?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Tiggam:
Both 7.4.2 and v17 have band 12 and volte.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] afuller42:
I cant seem to get the v17 rom rooted either normal methods. phhsuperuser installs but has no icon and cannot be enabled in magisk manager but the module shows up there. tried the latest supersu and that installs fine in twrp but again when booting back into the rom it just bootloops or same as above issue of no icon/root

I'm a htc guy myself and this device is very foreign to me but ive see stuff like "recovery-rootcheck" file and stuff like that in this rom zip and never seen that before, maybe that has something to do with it but like I said I have no cluee to this devices inner workings

I also notice that magisk busybox option does not stay enabled after reboot. so it seems stuff is not being written properly to the system
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Unscedeo:
Yeah, the exact same thing happens to me on V17. But the weird thing is that Titanium Backup can remove system apps (such as some as the Amazon apps), so that means we can access the /system folder and remove things but oddly enough not change or add things to it.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mmigliore:
Thanks -- sticking to 7.42.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] keredini:
I have the same problem, except i am not on V17, I'm on 7.4.2. AdAway won't work, and Substratum won't work either (I tried manually adding the overlay column into /system/vendor, but even then i had to do it all in TWRP and it still didn't work). Basically anything trying to write to /system seems to be hosed.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Tiggam:
Not sure about AdAway, but I have Substratum working on v17 by adding the overlay folder., never got it to work on 6.6 or 7.4.2..
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] RawSlugs:
How can I remove updates from 7.4?

Is it safe in flash if I'm rooted? Do I lose root?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] keredini:
How did you add the folder? Did Solid Explorer not complain that it couldn't mount system: "Unable to remount the file system under /system" is the exact message it shows.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Tiggam:
[IMG="Amaze creating a folder in system"]http://cyanix.tech/xda/amaze.png[/IMG]

I used Amaze file manager to create the folder, I tried solid just now and it gave me the same error.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] RawSlugs:
I'm on stock Amazon 6.1 rooted whats safest way to update
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Tiggam:
Read the first post.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] RawSlugs:
I did and I'm a little confused, what's v17 settings for?

All I need is to flash is the rom?

I downloaded 7.4.2 (I didn't even know this update came out)...

Also, what about a dirty flash?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Tiggam:
v17 settings in the stock update removes Navbar and OEM unlocking settings. The v17 settings zip restores them.

Flash the rom with TWRP.

Dirty flash has worked fine for me across versions.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] RawSlugs:
Is that for 7.4.2 prime variant or just stock v17 rom?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Tiggam:
V17 only
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] antharr:
So I am assuming that V17 OEM does not contain the Chinese backdoor that existed in the original firmware.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] RawSlugs:
Check the version app it has
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] AndroidBR:
Modified_rom_R1HD_7.4.2.zip (Modified_rom is stock 7.4.2 rom minus the preloader_p6601.bin, lk.bin, logo.bin, secro.img, trustzone.bin, uboot.img from 7.4.2, as well as amazon apps, no ads, updater enabled, so this rom is safe to use.)

https://www.androidfilehost.com/?fid=313042859668275704

>>>Update ENABLED?<<<

stock_V17_OEM_rom.zip minus the preloader_p6601.bin, lk.bin, logo.bin, secro.img, trustzone.bin, uboot.img

https://www.androidfilehost.com/?fid=457095661767119968

>>>I'm wondering if we should simply ditch the Amazon original ROM altogether and simply move to stock OEM... Is there any reason why we should stick to the Amazon one?<<<

Settings_V17.zip , This is settings from v12 ported to V17 to allow OEM unlocking and Navigation bar.

https://www.mediafire.com/?ui1r5w1khg8k5j7

>>>I'm still confused with this Settings file is necessary. Could you please explain why you've made that available?<<<

Thank you so much for your hard work my friend! ;)
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] afuller42:
Amazon version will get faster updates it seems. I converted to oem though.

The settings file is needed for exactly what it says, it enables oem unlock and the navigation bar in settings, without the file they are gone
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] KazuDante:
here is another CM14.1 running on a 32bit MT6735 (just like the R1 HD) https://github.com/vitek999/android_device_oukitel_orange/releases/tag/v-0.1

https://github.com/olegsvs/android_device_archos_persimmon/releases/tag/32_7-1-1-cm-14.1_0.6

if anyone could help me figure out why the system partition is not mounting.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] kostar:
Is there another host do download this from?

Androidfilehost shows error: Sucuri CloudProxy - Backend Server timeout.

Modified_rom_R1HD_7.4.2.zip (Modified_rom is stock 7.4.2 rom minus the preloader_p6601.bin, lk.bin, logo.bin, secro.img, trustzone.bin, uboot.img from 7.4.2, as well as amazon apps, no ads, updater enabled, so this rom is safe to use.)

https://www.androidfilehost.com/?fid=313042859668275704

stock_V17_OEM_rom.zip minus the preloader_p6601.bin, lk.bin, logo.bin, secro.img, trustzone.bin, uboot.img

https://www.androidfilehost.com/?fid=457095661767119968
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Tiggam:
Working fine for me
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] yaconsult:
I've been away for a while. Have downloaded the V17 rom and settings files from this thread. What is the installation sequence, please? Flash both at the same time? Or flash the rom and reboot before flashing settings? Is doing a factory reset or wipe required, and, if so, at what step? My phone currently has Colton's OEM V12 rom, unlocked, rooted, xposed, gravitybox, etc.

Also, are there any reports of VoLTE actually working on T-Mobile? I couldn't find any on the forum - just some posts about it NOT working. Thanks!
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Tiggam:
Flash rom, then settings. You can dirty flash if you so desire, you will have to reflash SuperSu, and xposed. I don't know about VoLTE as I don't use it and Band 4 is most popular round here.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] anbaude:
I'm still running Colton's original non-prime 6.0 from back in september or so, so I'm looking to update.

This is my first Android phone and I was able to root it without issues using his guide. I'm somewhat unclear on some of the things in this thread, though.

What exactly is the difference between Modified_rom_R1HD_7.4.2.zip and stock_V17_OEM_rom.zip? What does v17 even reference? Are both images from Blu? Are they fully compatible and fully rootable?

Thanks for this guide. I'm going to do as much studying up on this before I flash it.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Tiggam:
Both are from Blu. 7.4.2 and v17 are essentially the same. Both have security updates, Band 12 and volte, both will also change your bootloader and take away the ability to use SPFT.

There is a safe version of both in the first post, use those if you want to retain root and such.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] anbaude:
I think I'm beginning to understand after reading your post and more of the thread.

so v17 = non-prime, 7.4.2 = prime?

And actually, now looking at the OP subject that seems obvious now... Thank you!
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Tiggam:
Correct, v17 is non-prime and 7.4.2 is prime.

No problem and just remember, Do Not Take The OTA!
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] yaconsult:
So removing xposed before dirty flashing is not necessary because we're replacing the rom, right?

And the version of twrp I have from Colton's non-amazon flash is fine for doing this flashing, I presume?

Steps

0. Boot into twrp

1. Flash vampire's v17

2. flash vampire's settings

3. flash supersu

4. PROFIT!

Reboot

5. flash xposed and gravitybox
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] anbaude:
Does 7.4.2 mean that it's Nougat?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Tiggam:
No. 6.0
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] anbaude:
I see. In just completed a dirty flash. Everything seems to be working so far, haven't done thorough testing though.

As others have reported, it appears to have stopped adaway from functioning.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Tiggam:
AdAway works here, try the permissive boot.img
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
For adaway I needed to have working "toolbox". The v17 patched "toolbox" no longer does a r/w mount of system. So I restored the v12 version and it worked. But [MENTION=2472806]vampirefo[/MENTION] has pointed out is would be better to just add "busybox" to replace the "toolbox". He was able to just build busybox and put it into /system/xbin. But I did an install o busybox from play store then did the install of symlinks from within the app and it works.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Tiggam:
Play store BusyBox is one of the first things I install, maybe this is why I didn't run into the AdAway problem.

When setting up the new unit I installed AdAway first and it failed to apply the hosts file.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] anbaude:
Reinstalling BusyBox fixed the AdAway issue!

Any reason for play store BusyBox? I've prefer the idea of uncrippled fdroid version.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] RawSlugs:
Is there some other IMG besides system that does something with wifi? I have problems starting wifi (it instantly turns off)

On 7.4.2 rooted, Xposed

Any ideas??????
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Tiggam:
I have no idea, I have the pro version so it's my default
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Gizmosis350k:
Okay, the Prime 6.6 brought some strange issues, RAM management and freezes? But i think the 7.4 stock should be fine
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] ulises.rodriguez:
Since you have mentioned that you are on 7.4.2 Firmware, I would like to know which method do you have used to successfully root your BLU R1 HD phone?

I am asking, because I just received the latest Firmware: BLU_R0010UU_V7.4.2_GENERIC, and would like to root my phone, but would like to use the quickest and most secure method.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] RawSlugs:
I rooted on 6.1 using SP flash tool and flashed 7.4.2 from the first post using twrp
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] imsoenthused:
Hi. I installed the 7.4.2 modified rom from the original post on this thread and everything is working great, EXCEPT! I have some stupid amazon echo dot wallpaper on my lock screen and no way to change it. I just figured it was worth asking here if there is an easy solution, or should I just deal with it until the cyanogenmod gets mature enough for daily use?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
The app that made the lock screen ads is gone when flashing this ROM, but the ads image is stored in the data area of phone. I forget the post that told us where that file is stored, but the information is somewhere in the forum.

But you can also do a factory reset/ wipe and that will remove the image too.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Kirby Baker:
Hi everyone. I've got this phone and used root junky's information to go from 6.1 to 6.5, root and remove ads. I'd like to remove the bloatware from amazon and get to the latest version, which I believe I have quoted above? Am I understanding that the file above has no ads, and no amazon apps, and the updater will not install new versions if/when they come out?

Also, am I safe to use this method on my phone as is? Or should I revert back to a stock image non-rooted, and start from scratch?

Last question, is there a benefit to moving over to OEM? I don't need VoLTE. But I would like to be on the latest and greatest version, at least until a stable alternative ROM is out. Sorry for the noobish questions, been gone from android for 5 years now, and trying to get back in the swing of things.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] imsoenthused:
Thanks. I totally spaced out and only wiped the cache/dalvik. Going back and doing a proper wipe fixed it.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] kfn:
sorry
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
Yes, you can delete any app, not referenced via update script

Error 5 means nothing to me, you need to pull recovery.log it should tell you what the problem was.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] kfn:
yes sorry about this, fixed.

actually I also deleted apps under /system/vendor I believe they were referenced but all good
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] kfn:
Hello two more questions about old settings app from V12 on V17.

Yes I read about Navigation Bar but cant figure what is useful for?

Would it make device safer to disable OEM unlocking in settings?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
1 the nav bar settings is a visual preference setting. some people like the back button on the left (where it belongs like in a book or browser you go back to the left) some like the samsung style of back button on the right.

2. OEM unlock slider option and "safer". Difficult opinion to make , as far as "safer"

ok lets look at it like this:

if your phone is lost or stolen, yes having oem unlocked phone would allow who ever finds your phone to use fastboot and get around your lock code and use the phone. But that would force them to also factory reset it. So your data would be gone., and they would have your phone able to use it.

on the other hand if you had oem unlock off and had a bad update loaded to your phone you might end up with a bricked device that you would no longer be able to use.

and now to the point that makes all this explanation pointless. In order to even be using this modified rom in the first place you must be oem unlock anyway, so it really does not matter.. If you run custom or modified rom you must be unlocked.