yashsingh1/xdaforums huggingface dataset:
[BLU R1 HD Guides, News, & Discussion] vampirefo:
You can unlock the bootloader, mine is unlocked, I assume you are referring to the OEM unlock in developers option that's available in non prime, I already made that work on my phone 6.6 firmware.

That is just the settings.apk, I made the non prime settings.apk work on my custom 6.6 ROM which I run on my phone.

That was the only advantage non prime had over prime, that advantage no longer exists as either phone can do it.

Yes you can't flash the 6.6 preloader.
[BLU R1 HD Guides, News, & Discussion] tawrus80:
Did you find out if a Prime 6.1 image is needed? If so, am I backing up the partitions per this post? Else, point me to what I should do.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
I think there is already backups available. It is always a good idea to make one for yourself anyway.

Sptf can Mae the readback, but you need to enter the start address and length in hexadecimal format for all 24 partitions though.

You can also use miricle box, if your on Windows. Here is a thread describing all about it

https://forum.hovatek.com/thread-13347.html

The drivers for miricle box are a little different than spft and require driver signing verification to be turned off, then manually installed.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
He never got back to me so I'll just assume it's needed. Send a link to the partitions when they're backed up. Thanks for doing this!
[BLU R1 HD Guides, News, & Discussion] Chukie022:
sorry for my english. the led is only charger? or notification also?
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
Both
[BLU R1 HD Guides, News, & Discussion] theredbaron1834:
Both, however, only red and green lights.
[BLU R1 HD Guides, News, & Discussion] DarkBlood.:
With a custom ROM you can add orange
[BLU R1 HD Guides, News, & Discussion] theredbaron1834:
Is there a custom rom yet?

Also, I thought you could not change the brightness, even though there is a setting to do it, It was always max brightness. That plus the red being much brighter made orange not show up.

Is this not the case? What did you use?
[BLU R1 HD Guides, News, & Discussion] DarkBlood.:
I don't even own the phone but orange should be possible I got purple on my other mtk device by combining red and blue.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
There are difficulties but we are making progress. We think its more of a driver thing than TrustZone thing now, but then again we are all noobs at this.
[BLU R1 HD Guides, News, & Discussion] theredbaron1834:
The problem is that the red is so bright compared to the green, so it still comes out as red. Plus, it seems ti be an on off thing, no real brightness settings, so :(.

Ah. Been trying to follow via the dev threads here, but last I read it was trustzone stuff.

Best of luck to you guys.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
I mean all this is a guess, were new to this...
[BLU R1 HD Guides, News, & Discussion] yaconsult:
A custom rom is NOT going to add more colors! It is a hardware limitation in the LEDs themselves. They used cheap, simple on-off single brightness LEDs. You can control the hardware directly from the shell as described by Colton, linked below, and turn them on and off yourself with simple commands.

The phone has only red and green - no blue - lights and, even worse, the lights are only either on or off - no programmable degrees of brightness or intensity. And the brighter red and dimmer green on together looks 98% red so you can't tell the difference between red and "orange" unless you watch it very closely from a small distance while you change it. For me, the difference is not useful at all.

Colton lists the commands to turn the lights on and off and to different brightness levels on your phone here: http://xdaforums.com/r1-hd/help/notification-light-to-green-red-colors-t3447123 You have to be running as root to write directly to the hardware.

For usable notifications, you've got very bright red and nowhere near as bright green and each can be either all the way on or all the way off. These are the hardware LED limitations of this phone.

For a few cents more, they could have used a full Red-Green-Blue LED with adjustable levels for each color to give a huge number of available colors. http://cdn2.xda-developers.com/images/smilies/confused.gif
[BLU R1 HD Guides, News, & Discussion] DarkBlood.:
If Amazon decided to be bi**es then you can have problems with trustzone they can run anything in there, but I don't think they are that paranoid about people removing the ads.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
I disagree. They cut the price of this phone in half for prime users, with the hope they will be making back that revenue through lockscreen ads. They could theoretically lose half their investment if everyone did what we'd done.
[BLU R1 HD Guides, News, & Discussion] Chukie022:
hey, I have my blu r1 hd yesterday, the phone is good for cost 60 $, my phone is ROM 6.1 version,

which it is the best version? 6.1?6.4?6.5?

thx (sorry, my english is %$·&·$%)
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
Amazon firmware has newer security updates, but I'd say if you want to stick with Amazon firmware don't go past 6.5, as 6.6 makes SPFT not work, meaning you can't root. There is also vanilla firmware (what we can V12), but it has older security patches. You can flash back and forth between Amazon and vanilla firmware whenever you want, so honestly it's up to you. Amazon firmware has newer security updates, but has a bit more bloat you'd need to remove initially and has no option in the settings to enable bootloader unlock (although there is a workaround by [MENTION=4246643]Tomsgt[/MENTION]). Vanilla firmware is "safer" in my opinion in terms of being able to use SPFT, but isn't as up-to-date when it comes to Android's monthly security updates.

It's really up to you, as long as you don't take the official update to 6.6 you will be fine. I believe [MENTION=2472806]vampirefo[/MENTION] has made a 6.6 update flashable in custom recovery that does not disable SPFT (so you'd need to have root and custom recovery before installing it), but he's the expert on that.

EDIT: As a side note, even after you root/bootloader unlock, still don't take the official 6.6 OTA. It's a pain to get back down to old firmware from there.
[BLU R1 HD Guides, News, & Discussion] joeybear23:
Thinking about getting these for each of my kids. I don't need root, etc, but I would like to drop the lockscreen ads.

Does this have full access to the Play store and can a 3rd party lockscreen app keep ads away?
[BLU R1 HD Guides, News, & Discussion] shah_vm:
it does have full access to play store. I have not tired 3rd party lock screen app but amazon ads on lock screen are not that bad.
[BLU R1 HD Guides, News, & Discussion] joeybear23:
Thanks!
[BLU R1 HD Guides, News, & Discussion] yaconsult:
No problem with play store, but amazon is locking down the phones with updates. My suggestion would be to convert the phone to the OEM version of the software using Colton's excellent guide: http://xdaforums.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499 This gives you the ability to root the phone and will remove the ads on lockscreen and allow you to reflash the phone to restore it or if future software become available, like cyanogenmod.

If you leave the Prime version of the software on the phone and it gets updated automatically or manually, you will lose the ability to root or flash or recover the phone - and, the ads will most likely come back again.

Also, it's important to note - each amazon prime account is only allowed to buy ONE of each model of amazon prime phone. So, you could buy one 16 GB and one 8 GB, but you can't buy two 16 GB or two 8 GB. If they didn't have limits, lots of people would buy a bunch just to resell at a profit. Also, it doesn't make sense to buy the 8 GB model when you get twice the memory and twice the storage for only $10 more. I wanted to get a second one as a backup so I had a friend with prime buy it and have it shipped directly to me and I paid him for it.
[BLU R1 HD Guides, News, & Discussion] hawki:
Screen overlay issues and 6.6

So 2 questions, so does version 6.6 make this completely unrootable? Or just unrootable for now?

And 2 I can't seem to figure out this screen overlay message that keeps popping up. Makes some apps that I want to use, unusable.

Any help would be much appreciated.
[BLU R1 HD Guides, News, & Discussion] DarkBlood.:
Everything is hackable for enough time. Someone will probably find exploit.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
6.6 disables the VCOM port used to connect this thing to SPFT (we don't even know how), and SPFT was used before to write TWRP recovery directly to memory addresses bypassing the bootloader, and then from TWRP you could flash SuperSU to root. So the current method of root is unavailable as we have no way of flashing TWRP without access to SPFT. Our other option would be to find an exploit in Android or the kernel itself, like in the good old days of rooting, but I don't know how hard that is with Marshmallow and the 3.18 kernel. Can 6.6 be rooted? As [MENTION=7494374]DarkBlood.[/MENTION] stated, most likely. How long will it take to figure it out? Who knows.

Screen overlay is any app that draws over the screen. If you have a screen dimmer (like I use at night) disable that before granting permissions as that counts as an overlay.

EDIT: While you can't take an OTA if you are rooted, you can take an OTA with an unlocked bootloader, and doing so will not relock the bootloader. If you've previously unlocked the bootloader on an older firmware and then installed 6.6, you could then theoretically flash TWRP through fastboot and then re-root (since the bootloader would be unlocked you could use fastboot to flash a recovery instead of having to bypass the bootloader with SPFT). However I do not recommend doing this, I'd say just stay with Vanilla v12 firmware, or with Prime 6.5 or older.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
Potentially good news for you 6.6'ers out there, [MENTION=5312578]mrmazak[/MENTION] has found a way to POTENTIALLY unlock the bootloader through fastboot on 6.6 firmware. This method was taken from the Honor 5X (running marshmallow firmware) and involves removing google accounts and factory resetting. Right now he is testing to see if it works (so none of you guys have to risk factory resetting your phone and losing your data for potentially nothing). If all goes well expect a thread with instructions from him that goes into more detail.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
So he installed the ota 6.6 update?
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
He apparently has another R1 where he did. Waiting to hear back from him still.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
UPDATE: Turns out he didn't want to update to 6.6, but he did do it on 6.1 and it worked. He was able to unlock bootloader through fastboot with no scripts or SPFT. We're waiting for another tester, and theoretically this should work on 6.6 as well.

So far this is looking promising :)
[BLU R1 HD Guides, News, & Discussion] vampirefo:
6.1 and 6.6 is a big difference, in theory I suspect it won't work, would be great if it did.

6.1 could always unlock bootloader, 6.6 no one has so far.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
i am currently updateing my phone to 6.6 and will test myself

the update gave me a bootloop. but i was able to get it booted to fastboot and did the unlock. it worked.

dont know why it boot looped though
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Was the bootloader unlocked before?

Anyway great job, hopefully this will help out a lot of people.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
no i had relocked it and verified with fastboot getvar all

and in unlocked and relocked and now unlocked again.

appearently the

only trick is to not have a lock pin on phone when you do it and have no google account setup

only bummed that spft is not working. maybe now i will test my preloader update i made before.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Great discovery, this should really help a lot of people, and should be made a sticky, I am sure most new people coming to this forum has upgraded already to 6.6.

So your sticky will be their first step.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
for those of you following along. I have recently updated my phone to 6.6 (on purpose).

unlocked the boot loader.

and installed twrp.

flashed my modified update to roll back the bootloader.

the script needs some refinement before release but it was pretty straight forward.

did back and forth from v12 to v6.1 to v6.6 back to v12 and repeat.

trying to verify if eveything is as expected. and maybe not so simple. it seems that even though getval all shows bootloader is locked before updateing to 6.6 the update causes a boot loop. And going to fastboot and giving getvar all shows that device is already unlocked. that is why the boot loop.

so the unlock command is excepted but appearently because it was unlocked before it didnt realy re-lock.

none the less it did take the oem unlock without the switch in dev options and it appears all 's it will take to test it out is a factory reset., that is needed for the unlock anyway. seems harmless. either it will do the unlock or it will say failed.
[BLU R1 HD Guides, News, & Discussion] kal250:
Great work!!! I wonder if this solves the argument of a future OTA, here comes 6.7 -_-
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
Keep in mind, when mazak issued the final command to unlock bootloader it said it failed, but when doing a getvar it showed that it actually did unlock. So don't trust what fastboot has to say initially, and to confirm it works see if getvar says your bootloader is unlocked.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
Boot loader said unlocked, and would boot other partitions but said no permission to flash boot partition

---------- Post added at 11:44 AM ---------- Previous post was at 11:02 AM ----------

Um. I didn't have failed message when unlocking that went normal and gave pass message.

What I had was after screwing up the boot partition with a bad update script I had a fail to write boot partition while trying to fix it but I could boot the partition.

So it looks like it was only half unlocked.

I messed up boot partition by rolling back the preloader. The roll back worked I got use of spft. But something in the update made boot loop. I got out of loop by restoring back to v12. It took full restore(all 24 partitions), just boot and system did not take .
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
But you found a way to go from 6.6 to other firmware, which is a monumental discovery. Bravo!
[BLU R1 HD Guides, News, & Discussion] Gizmosis350k:
LTE downstreams and the IoE (cont'd)

[/COLOR]

Bro, I'm telling you I finally used LTE yesterday for the first time in my life. SMH. I GOT SPEEDS. faster than any fixed connection i have used in my lifetime. I am still baffled smh

As you folks know by now I'm in Jamaica, and Digicel is outmaneuvering CWNetworks at their own game.

HSPA off-peak speeds lmao (this is like, 4 in the morning everyone is sleeping)

10mb d / 1mb u

And LTE drivetime/in-house (albeit at the freaking head office/commerical district)

Words fail me _ _
[BLU R1 HD Guides, News, & Discussion] fuzzy_:
Very nice speeds there. If I see anything as good as that in my area anytime soon I will be surprised.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
Update on the 6.6 unlock, this isn't working the way we expected. Mazak (original tester) relocked bootloader and upgraded to 6.6, but was caught in a bootloop after doing so. From there he was able to unlock the bootloader. It seems that everyone else that started on 6.6 or did not get a bootloop is not able to do the method we had laid out successfully. We are currently looking into it in the R1 public group chat to try and figure this out.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
this linked post sums up the initial find for unlocking bootloader on 6.6 and followed by the ending fail :(:(

http://xdaforums.com/showpost.php?p=69001072&postcount=38

in summary I re-locked my bootloader and did the ota update to 6.6. I was then able to do oem unlock. But it seem as that was really only because it was unlocked before.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
I always believed once you unlock your bootloader it can't ever be truly relocked.

That's why there is a warning unlocking bootloader voids warranty, if the bootloader really could be locked back no need for the warning.
[BLU R1 HD Guides, News, & Discussion] Chukie022:
How to unroot completly my device? I unistall with superuser app but i cant play pokemon go :(
[BLU R1 HD Guides, News, & Discussion] joeybear23:
So I got this in the mail on Saturday. Amazing device for the price.

My daughter is ecstatic, and likes it way more than the Galaxy S2 that she had, and the MM build is very smooth.

No need to root, etc, so I can't comment on that, but so far she is loving it and I am thinking about getting another one for my other daughter.

By the way, Amazon says the purchase restriciton is 7 days. You have to wait 7 days between purchases to get more than one of these.
[BLU R1 HD Guides, News, & Discussion] yaconsult:
That's interesting... It's been more than a month since I got mine and the second one is showing $109.95 for the price of a prime version blu r1 hd. Has anyone else been able to buy two for the prime price on the same account?
[BLU R1 HD Guides, News, & Discussion] n3kf:
Mine was about six weeks ago and it shows presently as $59.95 for me.
[BLU R1 HD Guides, News, & Discussion] ytsejam1138:
You are permitted to buy one 16GB and one 8GB at the Amazon subsidized price. After that, the site will let you put it in your cart at the subsidized price but when you go to checkout it will delete the item.
[BLU R1 HD Guides, News, & Discussion] yaconsult:
OK - that makes more sense, although it would be less confusing to tell you that when you put it in the cart, instead of when you check out.

I know I had read that you could only buy one of each model of amazon prime phone and that's what I've been telling people. This applies to the Prime versions of Blu and Motorola phones.
[BLU R1 HD Guides, News, & Discussion] joeybear23:
Almost exactly 7 days to the minute from my last order and Amazon just let me order a 2nd Blu R1 HD, exact same model and discounted price with ads.
[BLU R1 HD Guides, News, & Discussion] yaconsult:
Maybe they changed their policy recently? I know that someone posted that they dropped theirs and called amazon about buying a replacement and were told that they couldn't buy a second prime phone of the same model.
[BLU R1 HD Guides, News, & Discussion] Javiefs:
Nah, I just tried to buy one from 11 de julio and will not let me buy nothing

Enviado desde mi R1 HD mediante Tapatalk
[BLU R1 HD Guides, News, & Discussion] mrmazak:
Do you mean you made changes to the settings apk or , used the non-prime apk. Either way is that apk in the Roms you have released.

I am still tring to run exploits, and if that settings apk was out, I can try to slip it in if I get an exploit to give me access.

So far I have tried few ways to use the non-prime settings apk. And each time has failed. Either with persistent message settings has crashed or just stuck on boot animation, and not able to boot.

I beleive these problems are permission related, I hope you can shed some light on this for me. Thanks
[BLU R1 HD Guides, News, & Discussion] Jep56:
I would love to figure how to move apps to SD card. Any ideas?
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Can't you just click on the app in settings and move it?

---------- Post added at 12:20 PM ---------- Previous post was at 12:18 PM ----------

I used the non prime settings apk, as it supports OEM unlock, also the settings apk in ZenUi ROM I ported, provides OEM unlock.
[BLU R1 HD Guides, News, & Discussion] Jep56:
There's no options in settings to move apps.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Works for me.
[BLU R1 HD Guides, News, & Discussion] joeybear23:
Is your SD card mounted?
[BLU R1 HD Guides, News, & Discussion] Jep56:
Yes it's mounted as portable storage. Should it be mounted as internal storage?
[BLU R1 HD Guides, News, & Discussion] joeybear23:
I cannot say for sure, but it works for me and mine is mounted as internal storage. I do know that changing how it is mounted willlll wipe any data already on the card, so you will want to copy it to your computer first.
[BLU R1 HD Guides, News, & Discussion] Jep56:
Re-mounted as Internal...works fine...thanks
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
Development update, today we found some interesting things for the MT6735 board in general. [MENTION=6928202]KazuDante[/MENTION] happened to stumble across a GitHub repo for a supposed leaked 7.0 kernel for the 6735 (kernel 3.18.19, so the same as ours). Personally, I'm not sure if we can use this for our build as the 6735 is USUALLY running 64 bit software and ours runs 32. So this probably means the kernel leaked is a 64 bit kernel that we won't be able to work with directly (our proprietary blobs needed for building are 32 bit). We may be able to pull some code from it for a potential N/CM14 build, but we probably won't be able to use the entire thing.

Here's a link to the repo:

https://github.com/olegsvs/android_kernel_ark_benefit_m7_nougat

Some other links he found:

https://github.com/olegsvs/android_kernel_cyanogen_mt6735

https://github.com/olegsvs/android_device_cyanogen_mt6735-common

https://github.com/olegsvs/android_vendor_ark_benefit_m7/tree/cm-13.0?files=1

https://yadi.sk/d/uT9g9DRat6dDH

Other than this stuff I don't think there's any news to report for the actual building of the ROM the guys are working on, but if I'm wrong here feel free to correct me.
[BLU R1 HD Guides, News, & Discussion] bullet25:
Just to add:

And unfortunately the kernel trees do not have defconfigs for the p6601 and integrating the mt6735 common tree still causes a bootloop at the blu logo. Our device is able to do 64bit but the stock ROM does not have 64bit blobs so we are not able to do anything with 64bit. We have to stick with 32bit.

I am personally, at this point, in way over my head.
[BLU R1 HD Guides, News, & Discussion] raderator:
Phone is gone from Amazon

https://www.amazon.com/gp/product/B01H2E0J5M

I know some have caught fire.
[BLU R1 HD Guides, News, & Discussion] yaconsult:
Very interesting development - especially since it was the #1 best seller in unlocked phones. Amazon has often removed things when there have been complaints and then brought them back after the issues have been resolved. Maybe the Note 7 recalls and its banning from flights has made them more cautious when there are reports of melting phones. Or maybe Amazon wants Blu to upgrade them all to 6.6 before they will sell them?

I guess we'll just have to wait and see what happens. I am now glad that I went ahead and picked up a spare already.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Our device is unable to boot 64bit, only 32bit, has nothing to due with ROM has to due with lk.bin.

Our lk.bin only boots 32bit.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
Are you serious right now
[BLU R1 HD Guides, News, & Discussion] kb3wmh:
I just noticed that it isn't on Amazon, at least as of when i wrote this

EDIT: i saw some one else posted this
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
Dude this is friggin awesome, not only do we all have another Note 7, we have a sort of Pre-Ban R1 (if they are to fix anything and release it again). Be proud all of you bought it when you did, even if you have 6.6.
[BLU R1 HD Guides, News, & Discussion] kb3wmh:
Ha. But seriously, should i be worried? I can't find any reports of fire online. I like this phone, but i don't like it enough to risk property.