yashsingh1/xdaforums huggingface dataset:
[BLU R1 HD Guides, News, & Discussion] :
Please read the original post. You obviously are not paying attention to what I am saying here. I have no interest in continuing this discussion because I would like to use this thread to help users who are actually using the guide that I've released. If you read the original post and understood what this is for, you would know the actual reason why I didn't release a TWRP image. This is a STOCK ROM, as in RETURNING YOUR PHONE TO THE OUT OF BOX STATE, as in NOT ALTERED IN ANY WAY, INCLUDING CUSTOM RECOVERY. The primary purpose of this guide is to convert the device between the Prime and non-Prime variants of the phones. The secondary purpose is to restore the device to a completely stock unmodified state.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
Wow that got heated. Let's try and answer this another way that maybe will not get things to such a argument.

The reason this is not set up as a twrp flash able zip is simply because, as the thread title States "restore 100% stock image " as in an out of the box condition.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Twrp does the samething, But I got the real answer already, the OP simply lacks the knowledge no big deal though.

I try and work with upcoming devs, but those that are to arrogant, and lack basic Android and twrp knowledge are simply unteachable.

As in the another thread, I explained how to compile R1HD kernel source, and those that are teachable have their own kernel, people must be teachable, OP isn't.
[BLU R1 HD Guides, News, & Discussion] bullet25:
[MENTION=2472806]vampirefo[/MENTION] I think you are missing the point that the prime phone has a locked bootloader that is NOT unlockable as the "fastboot oem unlock" command does not work and can't install TWRP very easy. This method changes a prime phone to a non prime phone which has an UNLOCKABLE bootloader because the "fastboot oem unlock" command works. The tools from [MENTION=5355478]ColtonDRG[/MENTION] make use of SPFT which can write the non prime ROM directly to the prime's memory. Its okay to disagree with which version you think is better but please keep insults and bashing out of this. Everyone is entitled to their own opinion. Colton and many other users, including myself, believe that the non prime version is better than the prime one.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
I have no problem with your post, but to say or imply twrp can't do the samething, or deny that non prime isn't a downgrade is simply a lie.

To be honest this thread is a lie, what the OP is doing is only replacing three files, eg flashing three partitions, which is a long way from making this phone completely stock.

Anyone that has done an upgrade must flash every partitions that was changed, this method only flashes system, boot, recovery, doesn't restore even close to full stock.

Only if you changed system, boot, recovery can this method restore to stock, twrp can do that and more, simply checkout what twrp can backup, you will notice it's way more than three partitions.

Anyway nothing is gained from this thread, people are told they are upgrading to non prime, which is the opposite, they are told this method restores their device to 100 percent stock, which it doesn't, it restores three partitions any modifications beyond those three partitions, this method doesn't help.
[BLU R1 HD Guides, News, & Discussion] :
I did not imply it was an upgrade, I implied that it was a conversion, which it is. It is a conversion (NOT a downgrade) that most people will want to take. This is subjective, and you're pretending that nuance does not exist. I flashed the partitions that are likely to be changed. I have an image of all partitions, but right now we still have not confirmed if it is safe to flash all of those partitions. Current evidence suggests that it isn't. I made it clear in the OP that this is the case. If you read it you would know that. As for TWRP, it is capable of flashing these partitions, yes, but for the purposes of this guide, that is actually less convenient. As for nothing being gained, thirty five hundred downloads disagree. I know you probably either won't read this or will purposely ignore my points. I just want to make sure the record is straight.
[BLU R1 HD Guides, News, & Discussion] The Android Attorney:
What i tried before was having TWRP installed first, no root yet, and then encrypt so i can be rooted and encrypted aswell like other devices allow. I reflashed the stock firmware, no modification whatso ever and it seems to have encrypted no issues. I guess this phone is one exception to that rule of TWRP first, then encrypt, then flash supersu.
[BLU R1 HD Guides, News, & Discussion] :
I didn't know there was a general rule of flashing TWRP first. :P But yeah, in this case, encrypt first using my APK, then install TWRP and root. :) I will update the root guide post with a notice about rooting. :D
[BLU R1 HD Guides, News, & Discussion] clu1688:
Lost in Post #2, how/which Adb?ally?

I completed steps in Post #1, all worked fine, and thanks for the instructions!

FYI, I started with a Win7 PC, had very hard time to install the drivers. I gave up and used a Win8.1 and driver installation was breeze. After that, all worked good and smooth.

I am trying to follow Post #2, and downloaded "minimal adb fastboot ver 1.3.1". I ran the command, first time I got this on DOS window:

*daemon not running, starting it now on port 5037*

* daemon started successfully*

error: device '<null>' not found.

Then I ran the same command the 2nd time, I got this:

error: device '<null>' not found.

Help please, did I use the correct adb tool? or I misunderstood totally?

Noob in need of help,
[BLU R1 HD Guides, News, & Discussion] :
I used the adb binary from the Arch Linux repositories. I also produced success with the adb binaries from the Ubuntu 16.04 repositories, the Debian Jessie repositories, and the Homebrew (for Mac) binaries. Honestly, you should be using the latest official adb binaries. On Windows, I personally use the binaries from the official Android SDK. I'm not familiar with the tool you did use, but honestly any recent version of adb should work OK. The issue you are having can be caused by a multitude of factors. Drivers, not having the USB Debugging box ticked, etc, etc, etc. Please verify that you followed the guide carefully.
[BLU R1 HD Guides, News, & Discussion] :
[MENTION=5312578]mrmazak[/MENTION] pulled it straight off of his brand new non-Prime phone when he got it out of the box. There is no official source.

EDIT: I take pride in the quality and authenticity of my releases. I would not have released that if I didn't trust the source completely.
[BLU R1 HD Guides, News, & Discussion] ytsejam1138:
I followed your guide and was successful at turning my Prime 16GB phone into an an OEM. However I noticed after flashing that in Settings>About Device>Custom Build Version it lists the device as an 8GB variant due to the model number being R0011UU and not R0031UU. Will this having any impact on receiving future OTA updates? Could I just edit the build.prop and change every R0011UU listed to R0031UU without any repercussions?
[BLU R1 HD Guides, News, & Discussion] kal250:
It has no effect
[BLU R1 HD Guides, News, & Discussion] ytsejam1138:
Awesome, thanks.
[BLU R1 HD Guides, News, & Discussion] clu1688:
OK I made a tiny progress. :)

I got a new set of adb files so I tried again. When I ran "adb reboot bootloader", I could put the phone in fastboot mode. But then I ran "fastboot oem unlock", it replied with "<waiting for device>." This happened to both of ADB sets of files. I put in CTRL-C to break it and rebooted the phone up, no problem except I failed to complete the fastboot command.

Any ideas? advice? Thanks,
[BLU R1 HD Guides, News, & Discussion] :
Sounds like more driver trouble. On Linux you have to run fastboot as root, but I doubt that's your problem.
[BLU R1 HD Guides, News, & Discussion] :
The 8 GB and 16 GB models have the same software, so the custom build number always reflects 8 GB model no matter what (this is true of both variants). That image was actually pulled off a 16/2 phone.

Edit: Also, changing those build.prop settings will make you unable to take OTAs. No other issues with that though.
[BLU R1 HD Guides, News, & Discussion] :
The hardware is bad. Replace it.
[BLU R1 HD Guides, News, & Discussion] FerociousAndroid:
Hello,

Anyone have a solution for installing the "MTP USB Device" driver for Win7 32-bit...? I've tried several things and just fails... :(

Thx
[BLU R1 HD Guides, News, & Discussion] kal250:
Have not personally tried as I have Windows 10, butI did download and extract, appears to be a valid file

http://mtkusballdriver.com/download/mtk-usb-v1-0-1
[BLU R1 HD Guides, News, & Discussion] ytsejam1138:
If that doesn't work, with the phone plugged into your PC, Go to Device Manager and find the device with the yellow exclamation. Right Click, and choose Properties > Update Driver > Browse My Computer for Driver Software > Let me pick from a list of device drivers on my computer > Android > MTP USB Driver.
[BLU R1 HD Guides, News, & Discussion] 33korzhello:
where battery life better, prime or non prime version?
[BLU R1 HD Guides, News, & Discussion] FerociousAndroid:
Thanks but didn't work. I'll try it on my Win10 32-bit when I get home later. :good:
[BLU R1 HD Guides, News, & Discussion] kal250:
If you going to use Windows 10, use these drivers

https://www.androidfilehost.com/?fid=24591000424943663
[BLU R1 HD Guides, News, & Discussion] :
Didn't measure, but it seems better on non-Prime.
[BLU R1 HD Guides, News, & Discussion] kofman13:
interested in getting this phone and trying the process. are there any downsides of converting prime into OEM? it doesnt get updates? are they important?
[BLU R1 HD Guides, News, & Discussion] :
It will get updates if/when BLU releases them. BLU has said to me on Twitter directly that the July security patch is coming eventually, and they've told other users that Android N is coming.

I personally highly recommend converting to OEM, but you will have to weigh out the advantages with the disadvantages and determine what is important for you. For me, the lack of that one security patch is a minimal problem, and the advantages far outweigh it. Of course, if you later come to regret switching, nothing is stopping you from converting it back the other way.

https://twitter.com/BLU_Products/status/773196078183288832
[BLU R1 HD Guides, News, & Discussion] classynopal:
Just tried this and I got it to work completely, thanks!

A few things that may help newcomers with the drivers on Windows 7...

Firstly, download the Android SDK and install everything on there (you probably don't have to but I did for the drivers).

Secondly, download MTK_USB_ALL 1.0.1 (look for it as I'm new to this and can't link).

install both of those now turn your phone off, plug it in, hold vol. up and power button at the same time and let Windows do it's thing. If the drivers don't install go to Device Manager and select the drivers manually yourself using the stuff you just downloaded.

Now continue to root your phone etc...

While rooting your phone, mostly the bootloader part you're going to have to manually select the driver for "Android" to the Android driver folder on the SDK each time it reboots the fastboot. It's weird but it works...
[BLU R1 HD Guides, News, & Discussion] :
Oh interesting. You had to turn the phone on in fastboot mode in order to install the drivers? That seems complicated, but I can't complain if it works. I will verify your steps and post them in a guide later if that's OK with you. I also have posted a link below to the driver pack you mentioned, and I will mirror this on my site eventually.

https://androidmtk.com/download-mtk-usb-all-drivers
[BLU R1 HD Guides, News, & Discussion] yaconsult:
I just use this program from XDA to install adb, fastboot and drivers: http://xdaforums.com/showthread.php?p=48915118#post48915118

Similarly, on linux you only need the android tools, not the SDK. On fedora, the package is called android-tools and other distributions have similar packages available.

The SDK (Software Development Kit) is huge and you only need about one percent of it. You only need the whole thing if you are writing android programs or building new ROMs for android.
[BLU R1 HD Guides, News, & Discussion] :
Yes, Android Tools (or more officially, Android Platform Tools) are part of the Android SDK. Many Linux distributions package them separately for good reason, which I believe I mentioned. You can also find independently packaged Android Platform Tools on XDA as well, but the only official way on Windows is by installing the SDK.
[BLU R1 HD Guides, News, & Discussion] classynopal:
Yes. It was very weird, and gave me many headaches. I'm not great at writing up tutorials so that's the best I can do. If I did it again I would write down my steps in order, buts that just from what I could remember... :(

Hope it will help others using Windows 7 64 BIT
[BLU R1 HD Guides, News, & Discussion] br1anwarr3n:
looking for boot.img, and system.img

[*]Extract the system image into the same folder you put SPFT in. The three files (boot.img, recovery.img, system.img) should be in the same folder as all the other SPFT

After extracting the system image into the folder that spft was extracted to I cannot find boot.img, and system.img
[BLU R1 HD Guides, News, & Discussion] anbaude:
So I've followed your guide and haven't made any other significant changes other than installing xposed.

I have a Prime 16/2 converted to OEM as per your guide. Is there something I need to do to disable OTA updates on the OEM version?
[BLU R1 HD Guides, News, & Discussion] buffal0b1ll:
Freeze/disable the Wireless Updates app. That's all it takes.
[BLU R1 HD Guides, News, & Discussion] :
You can remove the Wireless update and FotaProvider app if you want to (or just freeze them both if you don't want to remove them), but we're not as worried about OEM updates coming down the line blocking anything.
[BLU R1 HD Guides, News, & Discussion] :
It will unfreeze itself at boot. You also have to freeze FotaProvider
[BLU R1 HD Guides, News, & Discussion] DarkBlood.:
Non prime the ads drain battery
[BLU R1 HD Guides, News, & Discussion] :
Not much. Yes, Prime has more daemons that drain the battery more. Yes, my battery life is noticeably better. Blaming that specifically on the ads without any hard evidence is intellectually dishonest. In fact, I would wager that even on a Prime device with the ads removed the official way (by paying the extra $50) the battery life would not be impacted at all because not only does the Amazon Offers daemon still run in the background, but there are a handful of other extra daemons that run in the background. There could also be a barrage of other totally unrelated factors at play here too.
[BLU R1 HD Guides, News, & Discussion] jffwarner0:
So, I just got this phone as the Prime edition after dealing with a $15 smartphone for the past few years... So far, I'm very pleased with it, as I enabled Developer Options and force close the ads on every reboot.

However, I remember how nice my old phone became after I rooted it. So, I'm debating that for the R1 HD as well. I think my first step would be to convert it first, but I have a couple of concerns.

The first concern is that I just downloaded the latest update to the Prime version using Wireless Update. Will that prevent me from converting the phone properly?

The second is that if I do convert it, will I be locked out of some apps due to the device appearing as "flashed", or will it be nondistinguishable to apps? I'm particularly concerned about this because of a throwaway SIM card that doesn't work for flashed or rooted devices.

And lastly, if I need to use the manufacturer's warranty at all after conversion, will I be able to convert it right back without them being able to tell?

Thank you in advance for the help!
[BLU R1 HD Guides, News, & Discussion] :
If the update is the V6.6 update, yes. You will be unable to convert. You will also be unable to really do anything with it unless you rooted and unlocked the bootloader at an earlier date. We are investigating the prospect of reversing the damage from the V6.6 update without root, but as of right now and the foreseeable future, V6.6 is bad news. As for the device appearing as "flashed", I think it won't, but not promising anything here. As for the manufacturers warranty, the only physical difference between the two is a model number on the back, and I highly doubt that the manufacturer will care to even investigate the software/hardware that closely, so you probably don't even need to convert back, but if you want to, yes, you can.

If you have taken the V6.6 update and you're really regretting it now, you should still be able to get it replaced. If it's within the first 30 days, you can just go on Amazon and tell them that something doesn't work quite right and they'll replace it without issue, and if it's past the 30 days, doing the same via Amazon's customer support personnel should also work. Just remember to be as vague as possible. The new one you get should be running good ol' 6.1 so you can convert right away.
[BLU R1 HD Guides, News, & Discussion] jffwarner0:
I knew I should've checked this out before I downloaded. I hate dealing with returns, so I might just deal with it and hope that a workaround is found at some point. I still have a couple of weeks to figure that out for sure though.

As for the flashing bit, no one's reported issues with apps? The only that comes to mind with that is SnapChat (which I don't use, but could use it to check).

If a workaround is found and I do the conversion, I shouldn't lose my apps and app data, correct?
[BLU R1 HD Guides, News, & Discussion] :
Yes, it should be theoretically possible to keep app data between conversions, but not officially supported and some bugs may arise.

As for flashing, I think I've seen one report that said they had an issue with an app claiming that the phone was rooted and wouldn't work. The only thing I know for sure about that report is that the user said their phone was not rooted, and I don't remember which version of software they were running (think it was prime) or if they converted (think it wasn't)
[BLU R1 HD Guides, News, & Discussion] kal250:
I would be advising people to get it replaced ASAP, it wont be long before they start requesting "additional details" or advising customer service to scrutinize resquests. I use Amazon for shopping quite frequently, but after the support experience from the fire phone, and all the excuses, I will never buy another Amazon Fire product....
[BLU R1 HD Guides, News, & Discussion] jffwarner0:
Ok, that's good. Sorry for the questions, it's been a couple of years since I messed with rooting and I remember soft-bricking that phone at one point because I was rushing.

If a workaround is found, will it posted in this thread?
[BLU R1 HD Guides, News, & Discussion] :
Absolutely. Keep an eye on the general board though. It's easy to miss single posts in big threads like this one. I will mention you if I remember to do it.
[BLU R1 HD Guides, News, & Discussion] :
That's a reasonable point. I hope it doesn't come to that, but I could see it. Maybe Amazon will learn a lesson from this... Probably not.
[BLU R1 HD Guides, News, & Discussion] anbaude:
Hmm, I'm not seeing on my converted phone I'm not seeing a Wireless Updates app or anything called FotaProvider

---------- Post added at 05:14 AM ---------- Previous post was at 05:06 AM ----------

Ok, scratch that. In Settings > Apps when I enable "Show System Apps" or whatever I can disable Wireless Updates but not FotaProvider. Will I need to use a third party tool for that? Any suggestions if so?
[BLU R1 HD Guides, News, & Discussion] buffal0b1ll:
Root the device. Use TiBU or CCleaner to disable Fota Provider
[BLU R1 HD Guides, News, & Discussion] theredbaron1834:
Disable vs uninstall, which is better? I made backups before removing, should I reinstall and just disable?
[BLU R1 HD Guides, News, & Discussion] buffal0b1ll:
It's up to you. I disable. Deleting them imo has no advantage as it frees up no usable space because they're on the system partition.
[BLU R1 HD Guides, News, & Discussion] theredbaron1834:
I am no where near a dev, but I do like to play around in system. Adding apps, moving things, just over all tinkering with things (right now messing with things to try and get louder sound). Plus I like to have "my" set of apps installed on format, etc.

Granted, df shows 868.9mb on /system, so I guess I have plenty of space. I guess it is just that my first android device had about 3mb of free space by default, so I got use to clearing system of stuff I don't use (especially since fdroid use to be able to use system privilege to install apks, thus I wanted it there).
[BLU R1 HD Guides, News, & Discussion] guliver365:
I just got the amazon Prime, without even login into the phone I did the first part of the guide without any issue { got window with a large green checkmark} by flashing prime-stock-oob.tar.gz bur now I am at system blu_R0010UU-v6.1Generic 17-06-2016 14 5-53 the wireless update want to go to 6.6 so Now I am not sure If I am really converted to the generic.

Is it safe to let it upgrade or can I convert it to a non prime generic ? what is the latest firmware for generic?
[BLU R1 HD Guides, News, & Discussion] kal250:
The flash must not have been successful 6.1 is Prime, OEM is 1.2, do not update to 6.6 did you follow the guide completely?
[BLU R1 HD Guides, News, & Discussion] guliver365:
I think so, since that I just flashed the oem version over the previous one now my system is BLU-R0011UU_V12_GENERIC 27-06-2016

So I do not understand what is the difference between normal-stock-oob.tar.gz and prime-stock-oob.tar.gz since the goal is to remove the add why do we need the prime version for? I guess I am confused.
[BLU R1 HD Guides, News, & Discussion] kal250:
One is subsidized by Amazon(though I'm not sure I would call it subsidized, considering the ad revenue they get) and one is not.
[BLU R1 HD Guides, News, & Discussion] fuzzy_:
normal stock...no ad version

prime stock..... ads version

I think prime is there in case you want to change it back to prime.
[BLU R1 HD Guides, News, & Discussion] SqueezyCheez:
I ran through this process with my new BLU phone and got the "installing to device" message that worked its way through for about five to ten minutes... but now it's at the main screen again and I never got a green checkmark. Is it good for me to go?
[BLU R1 HD Guides, News, & Discussion] Manucr:
How to Uninstall Amazon Apps after make the phone NON PRIME

How can I unistall the amazon aps after to flash the NON PRIME Stock. I try but it seens to be unpossible
[BLU R1 HD Guides, News, & Discussion] kal250:
{Delete}
[BLU R1 HD Guides, News, & Discussion] guliver365:
An other no so smart question I installed SuperSu no problem great guide, do I need to keep OEM unlocking checked tin order to access TWRP?
[BLU R1 HD Guides, News, & Discussion] :
NO! The non-Prime version comes with a handful of Amazon apps too. Some of them are removable (you'll know if you try), but the others you'll either just have to disable, or root and remove. Running these debloating scripts on non-Prime is not safe.
[BLU R1 HD Guides, News, & Discussion] :
See post above
[BLU R1 HD Guides, News, & Discussion] :
Don't think that box does anything particularly interesting after unlocking, but no reason to uncheck it either.