yashsingh1/xdaforums huggingface dataset:
[BLU R1 HD Guides, News, & Discussion] kal250:
Use 7zip, i used 7 zip, it extracted 1 file, which i had to use 7zip on again to get the 3 images, lol like a zip in a zip, if that makes sense ;)

---------- Post added at 10:53 PM ---------- Previous post was at 10:50 PM ----------

Agreed, it's still a shame that BLU leaves their customers hanging. I can see at their price point, but even at that, if your going to market a re-badged phone, at least hire a few developers to throw a few updates out there, would do wonders for their image.

---------- Post added at 11:01 PM ---------- Previous post was at 10:53 PM ----------

Just follow Colton's guide, I think people are getting confused trying to do either a mix of root junkys method with others. If you follow Colton's guides then I don't believe you will experience any issues. If your using windows I recommend the following drivers

https://www.androidfilehost.com/?w=files&flid=68715
[BLU R1 HD Guides, News, & Discussion] 36dbldz:
I just got the device today just to get my feet wet with rooting. I have a oneplus 3 and like it stock so I'd rather get comfortable on a non daily driver that was not too expensive. If yall hook up anything I'll try it just to learn be it a custom ROM or anything. I'll be watching
[BLU R1 HD Guides, News, & Discussion] ibleo02:
I got it to work by using Android Handshaker from the app store. Don't know why Android File Transfer won't work with this device.
[BLU R1 HD Guides, News, & Discussion] bmac6996:
quick thanks.. Was able to turn this to the OEM version. No more Amazon ads. For that, awesome deal. Pretty quick and painless to do. Good work.
[BLU R1 HD Guides, News, & Discussion] terragone:
Well, phone #2 flashed without any problems. ¯\_(ツ)_/¯
[BLU R1 HD Guides, News, & Discussion] jumphour:
Hi. I got my R1 HD the other day, and used this guide to flash the stock non-Prime files, unlock BL and TWRP/root. It worked out great. The next day, I got my new 64GB microSD card, and decided I wanted to start fresh and then do a nandroid backup and Titanium Backup on the card. When I factory reset in the Android settings, I lost root and my computer (well, 2 of them) wouldn't see the phone any longer in fastboot mode. So that freaked me out.

I then started from scratch with this guide, again flashing the non-Prime ROM, unlock BL and TWRP/root, which worked. I was all excited! Got all my apps on there, and everything is working good. But again, now the computer no longer sees the device in fastboot mode. It does see it when it's booted normally. I think I maybe have a driver issue? I installed a MediaTek driver I found somewhere (oh, up a couple posts....kal250.....I right-clicked the .inf one, install, it asked to open it, I said yes, and that's it...not sure what was supposed to happen), but that didn't seem to help. Any ideas? Or should I just not touch it at ALL, unless I want to start the entire process over. I mean, it's rooted and working, so.... :confused:
[BLU R1 HD Guides, News, & Discussion] Gizmosis350k:
That is indeed strange, but i look forward to the assistance that will be given : )
[BLU R1 HD Guides, News, & Discussion] CircularApex:
Hello, what is the source of normal-stock-oob.tar.gz. ? How was it obtained? Is there any official source we could get it from? Thank you!
[BLU R1 HD Guides, News, & Discussion] kal250:
Any pointers or guides i can review, to help me at least bring over the security updates to OEM converted prime. I'm not completely giving up hope, but it seems the hype is subsiding. I don't wanna see development stall, but I understand people have their own priorities, I would like to contribute what I can. But I admit my skillset with Linux and Android are lacking. I have been researching Mediatek, no wonder they name their rom mappings a scatter, that's how good Google is with mediatek info..... scattered
[BLU R1 HD Guides, News, & Discussion] :
No. I have some plans for porting the security updates over, but it is very complicated, and we've yet to determine that it will be ultimately worth it.
[BLU R1 HD Guides, News, & Discussion] kal250:
Thanks, for the hard work!!
[BLU R1 HD Guides, News, & Discussion] Qdhcjv:
Will I still get some form of OTA updates with this? I want to receive that Band 12 patch that is on its way.
[BLU R1 HD Guides, News, & Discussion] kal250:
Assuming BLU sticks to what they said, they are notorious for not delivering on previous "promises". If BLU sends out an OTA for non Prime, you should get it, barring the usual exceptions, i.e. root, etc..
[BLU R1 HD Guides, News, & Discussion] billownz:
On my second phone, I get the same error in two machines with two different cables. Do you think they patched it?

Scanning USB port...
Search usb, timeout set as 3600000 ms
add@/devices/pci0000:00/0000:00:14.0/usb2/2-2

add@/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.0

add@/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.1

add@/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.1/tty/ttyACM0

vid is 0e8d

device vid = 0e8d

pid is 2000

device pid = 2000

com portName is: /dev/ttyACM0

Total wait time = -1471752421.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
Connect BROM failed: S_UNDEFINED_ERROR
Disconnect!
BROM Exception! ( ERROR : S_UNDEFINED_ERROR (1001)

[HINT]:
)((ConnectBROM,../../../flashtool/Conn/Connection.cpp,85))
[BLU R1 HD Guides, News, & Discussion] :
I know they didn't. Try rebooting your computer.

EDIT: Oh, just read that you tried two computers. That is certainly odd. I'll check on it, but I'm still certain that it hasn't been patched.
[BLU R1 HD Guides, News, & Discussion] :
Yes. You will receive any updates that are released for the OEM version. Weather or not there will be any updates to get remains to be seen.
[BLU R1 HD Guides, News, & Discussion] zipsulman:
This worked great for me.

---------- Post added at 02:42 PM ---------- Previous post was at 02:07 PM ----------

After hours wasted mucking around trying to do this. These instructions worked like a charm. I give these my endorsement 100%
[BLU R1 HD Guides, News, & Discussion] Sizzlechest:
Got a brand spanking new phone. Didn't even power it on. Followed directions to convert it from Prime to OEM and worked perfectly. Booted it, unlocked the bootloader and installed SuperSU. Only deviation for me was an inability to sideload through TWRP. Instead, I copied SuperSU to the internal memory and used the Install feature of TWRP like every other phone I've rooted. Seems to have worked just fine.
[BLU R1 HD Guides, News, & Discussion] :
I prefer to use the sideload features, but I am aware that they don't always work. Perhaps I will update the guide.
[BLU R1 HD Guides, News, & Discussion] Gizmosis350k:
Amaze

All i know is, I owe Mr.DRG dinner because I now have my masked 16/2 enroute this is going to be my /FIRST/ phone running a current version of android with okay specs and lots of potential.

Sir you are working miracles down south in the coal mines :highfive::good:
[BLU R1 HD Guides, News, & Discussion] :
Hey, I'm just dropping in here to let you all know that I have released an APK that will launch the encryption activity for those of you who want to encrypt your newly converted phone! Just install and launch. Encryption will not work if your phone is rooted.

http://mirrors.coltondrg.com/coltondrg/r1hd/goodies/com.coltondrg.android.r1hd.encryption-v1.apk
[BLU R1 HD Guides, News, & Discussion] Gizmosis350k:
Awesome, i'll be sure to try it once i receive my personal daily driver :cool:
[BLU R1 HD Guides, News, & Discussion] The Android Attorney:
The reason you lost root is cause its System-less root. So it doesnt touch the system partition. Also, as for not being recognized in fastboot mode, try uninstalling the drivers, then reintalling.
[BLU R1 HD Guides, News, & Discussion] jumphour:
Thanks for explaining the systemless root thing. I'm still lost about the driver problem. Not sure how to delete one. I right-clicked on the phone in Device Manager, and deleted the device, tried plugging it again, and it comes up with what looks like the same driver it had before. Then my Moto X Pure wasn't being seen by my computer, so I reloaded those drivers because I actually HAD the correct drivers for that right from Motorola. I give up on the R1 HD and ADB in fastboot mode for now. I'm just using it as is, until there are flashable ROM's I can just do in TWRP.
[BLU R1 HD Guides, News, & Discussion] Tariq Attique:
Download links are down? or is it just me?
[BLU R1 HD Guides, News, & Discussion] J.Stapleton:
Same here
[BLU R1 HD Guides, News, & Discussion] RJQXCV:
ur sites down mate
[BLU R1 HD Guides, News, & Discussion] :
Yes, it appears a package update (or something) brought down my Nginx instance. It's back up now. Sorry for any inconvenience.

And on another related note, I now have a second mirror at http://na.mirrors.coltondrg.com/

Enjoy!
[BLU R1 HD Guides, News, & Discussion] anbaude:
So this should work for my 16/2gb blu r1 hd prime version that I received? It's an R0030UU.

This is my first android device. I'm brand new to android, always had an iphone before. I have a pretty good idea of what's going on in the process, but I want to know that this method will work. I'm a long time linux guy, for what it's worth, so I'm fairly tech proficient. I will also be using Linux SPFT - anything weird that's linux specific that I should know about? Would it be better to do this on windows?

I will say this: This will be my second root attempt. Following the methods laid out by another user's youtube video, I hard bricked the first r1 hd. I got a BROM error and seemed to kill it dead. So, second time's the charm, I hope.

Also, I haven't even turned this one on yet. Should I upgrade the device prior to doing this?

---------- Post added at 08:20 PM ---------- Previous post was at 07:30 PM ----------

Alright, so I've re-read the main post, and read the entire thread. Looks like Linux should be a breeze considering that's what Mr.DRG uses.

And I likely won't even give the phone a first boot. Again, this was mentioned in the OP.

I'm going to reread everything later and I'm going to attempt this later tonight. Thank you for the through guide. Wish me luck. I'll let you know how it turns out.
[BLU R1 HD Guides, News, & Discussion] dekoba:
DR

Hello! I tried this and ive stumbled a fair bit but I think im getting closer. Encounter a BROM ERROR when I attempt to flash,

---------------------------

Smart Phone Flash Tool

---------------------------

BROM ERROR : S_DL_GET_DRAM_SETTING_FAIL (0x13BE)

[EMI] Obtain DRAM Failed!

[HINT]:

Please check your load matches to your target which is to be downloaded.

---------------------------

&OK &Help

---------------------------

A quick google search turns up (cant post links) which states that this is a problem with the txt file (the scatter file?). Anyone encountered this and figured out how to move past?
[BLU R1 HD Guides, News, & Discussion] kal250:
This has been happening to several people as of late do you have the 8gb or 16gb model?

Im wondering at this point if there are a couple different hardware versions of the mainboard or something going on here??
[BLU R1 HD Guides, News, & Discussion] dekoba:
I have the 16gb model. I think it must be a driver issue. workaround for me was to make an ubuntu thumbdrive and rerun everything through linux. worked the first time with no hiccups and was actually faster than screwing around with windows drivers. I think tomorrow im gonna just partition off my HD and install ubuntu to dual-boot.
[BLU R1 HD Guides, News, & Discussion] td1010:
Hi Colton,

Thanks for the stock ROM, I'm now free from the Amazon ad screens!

One question though (and sorry if you already answered it). Your encryption post says that it won't work if the phone is rooted. Does this mean that you can either have encryption or root but not both? Or do we have to encrypt or root first, then do the other?

Thanks for the great work!
[BLU R1 HD Guides, News, & Discussion] anbaude:
Ok, I followed your guide to a T and it worked beautifully. Not bad for my first run with Android. It wasn't difficult at all with your very specific guide.

I did have to do some linux udev usb magic so that SPFT would see my phone properly, following this guide corrected the issue. I also needed to install a more recent version of adb to sideload. I'm on Debian Jessie.

Thank you again for providing this wonderful guide!
[BLU R1 HD Guides, News, & Discussion] kal250:
I believe you can encrypt then root
[BLU R1 HD Guides, News, & Discussion] Tech Critic:
I wanted to see if anyone could confirm this for me, as I have yet to see anyone state specifically *how* this method works, or in other words why it's possible.

AFAIK the phone has a locked bootloader, and the phone has a hardware based bootloader signature check that must be passed in order to load the bootloader (or a portion of it), so if the bootloader doesn't have the proper signature, the boot process will fail.

If the above is in fact true, and we can flash the standard Blu non-prime ROM onto the phone without first unlocking the bootloader or rooting, that must mean that the two versions of the ROM have the same signature? So the standard Blu ROM will boot on the phone because it passes the signature check, not because we're exploiting a vulnerability?

This makes sense to me, since it would be in Blu's best interest not to deliver different hardware to Amazon due to manufacturing burden and the reduction of flexibility in how the phones can be distributed. This way Blu can decide to sell the phones that were manufactured for Amazon to another party if the deal falls through etc.

Can anyone confirm?

I'm also curious as to whether we will always be able to use this method to switch to the non-Prime ROM even after updates to the Prime ROM aimed at skirting our efforts. If I am correct about the above, the only way I know of that Amazon could accomplish that is if there are efuses in the bootloader which blow upon an update and permanently prevent the older bootloader/OS from flashing or booting once flashed. AFAIK, this device does not have efuses that we know of? Is there another way that they could prevent a downgrade by flashing?

Any enlightenment would be much appreciated!
[BLU R1 HD Guides, News, & Discussion] AngryToe:
I'm trying this now, and I'm pretty sure I did it right. After pressing download and then plugging in my phone, it starts installing. A new "device setup" window came up and the SPFT window has all of the text grayed out. After waiting for 40 minutes, the device setup seems very close to being done, because the bar is almost all green except for a small part at the end. But, nothing else is happening, even after 40 mins have gone by. What could the problem be? Can someone respond? Thanks
[BLU R1 HD Guides, News, & Discussion] kal250:
Did you install the drivers before hand? It sounds like windows detected hardware after SPFT started?? It only took about 3-5 minutes my first flash.
[BLU R1 HD Guides, News, & Discussion] AngryToe:
Yeah, I fixed it. I just unplugged the phone and restarted the process. It works great so far, thanks anyway.
[BLU R1 HD Guides, News, & Discussion] gt5401b:
progress on the SPFT?

When I tried to use the SPFT to flash my R1 HD, after 30+ minutes it shows no sign of finishing. How do I know if it is working and I need to wait longer? Any log files that I can read?

I copied all my files in a usb drive and running SPFT from it. It is said that it only takes 10+ minutes and then I will see a large green check mark. How do I know that the application is not just hang? Everything works great until step 10 in "flashing your phone"
[BLU R1 HD Guides, News, & Discussion] gt5401b:
I finally resolved the issue:

Use a Windows 10 machine (or VM), follow the step as the original post. Make sure you have the correct driver by turning on the R1 HD, plug it in USB port and see that windows recognize it (you can browser the data in R1 HD). Then shutdown the device and following the original post.

Another thing to remember is once flash tool is started and you clicked download, and only then connect R1 HD (which is powered off). At this moment, you will see the bottom bar showing progress. If there is no progress showing up, the application (flash tool) will time out in about 45 minutes?.

Once all works out, you still have to uninstall amazon widget to disable some of the ads bring up by this app (Amazon Widget)

Window 7 does not have the driver for R1 HD. You have to use Windows 10 to do this.
[BLU R1 HD Guides, News, & Discussion] thirdlobe:
Thanks for all your hard work on this. I had the previous root/bloat removal/image and it worked well but got a little sluggish after a while and for some odd reason the clock stopped working on the home screen but it worked on all the apps that time stamped anything.

Either way I was able to do this today pretty seamlessly and the phone works brilliantly!

Flashed & rooted = :)
[BLU R1 HD Guides, News, & Discussion] :
Glad it worked out. I had to follow that guide as well to get it working on Arch Linux. It worked out of the box for me on Debian and Ubuntu. I suppose I should mention this in the OP.
[BLU R1 HD Guides, News, & Discussion] :
Solution: Don't use Winbloze.

Using SPFT inside a virtual machine is dangerous. If you're having driver issues, my first recommendation is to do it on hardware on Linux.
[BLU R1 HD Guides, News, & Discussion] td1010:
I managed to encrypt before I rooted (can't say for sure though - the only clue I had was that I had to enter a password whenever the phone started) but after I rooted I'm not prompted for a password anymore. Does this mean I'm not encrypted and if so how do I encrypt?
[BLU R1 HD Guides, News, & Discussion] patientzero:
Yeah -- I'm surprised this person got anything to work at all through a WinVM. I've never had any luck that route.

Also, your tutorial is amazing. I've been doing this for years and this was among the best I've ever seen. Worked on the first try.
[BLU R1 HD Guides, News, & Discussion] kal250:
Not sure, never have encrypted my phone, i don't even use a password. So not really sure. I'm just going by previous statements on previous posts that encryption survives root. Someone else may need to chime in on this one to verify, sorry
[BLU R1 HD Guides, News, & Discussion] raegz:
Help me!

Hello, excellent tutorial but I do the process but the phone remains in logo and reboots in an infinite loop
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Curious why this isn't done via twrp?

Just three files are being changed system, boot, recovery.

All could be done via twrp.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
You are correct. But this way the tutorial works with phone out of box. No need to put twrp in first and root.

But in theory you can write a update script, a binary file, and use twrp. Just remember you needed to use spft at some point anyway, to get twrp installed, so why not just use that.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
You don't need to install twrp.

fastboot boot twrp

twrp would make swapping Roms faster without need of computer, if twrp was installed on phone.

Also no need for update script, twrp can flash system.img, boot.img, recovery.img just fine as long as you use twrp to make system.img.

Now in zip format a update script is needed.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
OK all true, dint think about making the backup that way. But I beleive fasfoot boot twrp will not work with locked bootloader.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Correct need to unlock bootloader, to fastboot twrp.

Oh well I was just curious, everyone does things differently.

I am on stock prime rom, unlocked bootloader, rooted.

I fastboot boot twrp to make backups.

I made two stock backups, one as soon as I got phone, second one right after 6.5 update.
[BLU R1 HD Guides, News, & Discussion] The Android Attorney:
thanks for this guide!

but i am having trouble with the encryption APK. the phone reboots, but i am not prompted a password or anything. i go to twrp, and i can still see everything. I am not rooted. i reflashed the non-prime firmware and did a factory reset.
[BLU R1 HD Guides, News, & Discussion] td1010:
I see the same thing.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
I use prime version, go to settings > security > encryption.

What does it show?

Mine says encrypt phone, meaning it's not encrypted.
[BLU R1 HD Guides, News, & Discussion] The Android Attorney:
i converted it to the non-prime version. For some reason, the encryption option was left out. but the APK provided doesn't work.
[BLU R1 HD Guides, News, & Discussion] :
No. You obviously misunderstand what this is for.
[BLU R1 HD Guides, News, & Discussion] :
There is no encryption option in the OEM stock ROM. This is well documented. Please read the thread. I have released an APK to access the encryption options. Again, read the thread.
[BLU R1 HD Guides, News, & Discussion] :
My APK doesn't work? Can you describe how it doesn't work? It works fine for me.

EDIT: Apoligies, I didn't read the thread correctly, and I missed your prior description of how it doesn't work. Update explaining what's wrong below.

Did you install TWRP? Encryption does not require a password. It uses your lockscreen passcode, and if you don't have one, things are encrypted without a passcode. The way Android encryption works, the phone is encrypted with a secure key that is stored in a separate area of the phone. If your phone has a lockscreen passcode, the area where the encryption key is stored is encrypted using that passcode. If you do not have one, it is encrypted using a generic hardware key. When you change your passcode, this encryption key's encryption is also updated.

If the system is altered in any way, including but not limited to root, and possibly including TWRP, you will be unable to encrypt. Also, there is a bug in the firmware where the phone's encryption process is a little broken. Instead of displaying encryption progress, while the phone is encrypting, you will just see a sort of corrupted version of the lock screen that you are unable to interact with. If you see this, don't panic, and DO NOT force your phone to power off. You can lose data if you do. Just wait for the phone to finish encrypting and power off by itself. You should also remove the encryption app after successfully encrypting your phone, because running it twice could have unintended and unknown side-effects.
[BLU R1 HD Guides, News, & Discussion] :
As far as I know, there is no way to decrypt your phone without wiping your data, so unless you did wipe your data, it's probably still encrypted. Encryption uses your lockscreen passcode, so if you do not have a lockscreen passcode, that explains why you are not prompted for a passcode. Rooting after encryption should theorhetically work fine, but obviously there are no guarantees in that situation.
[BLU R1 HD Guides, News, & Discussion] :
Did you receive an error from SPFT at any point? Did you unplug your phone or have your computer power off? Did you root the phone or install TWRP? Your description of the problem is way too vague and lacks too many details to make any determination. If you're bootlooping, that is a good sign that it's not bricked permanently. My suggestion is to simply re-run the first part of the guide again to restore the stock ROM.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Just curious, no big deal, I will probably release Prime 6.5 in twrp format.
[BLU R1 HD Guides, News, & Discussion] :
Why?
[BLU R1 HD Guides, News, & Discussion] futuraforce:
Can anyone confirm this working using Win7?

Can anyone confirm this working on a Win7 machine? I was all set till I read this post. I am in the process of downloading Ubuntu just in case.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Variety, this is the only device I own or know about, that is rooted, bootloader unlocked, has twrp recovery yet not one rom, not one available to be flashed via twrp.

So to kick things off, a flashable stock should work just fine.