yashsingh1/xdaforums huggingface dataset:
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] RainofOranges:
I don't think any OTAs have affected any debloat methods that involve root. There's another thread on here that has a TWRP flashable .zip file that debloats the Prime ROM amazingly (and doesn't require root). I highly recommend that over manually removing everything with root and Titanium Backup. Even though I bought the non-Prime version, I run the Prime ROM because of the security updates.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
You can open an OTA and see exactly what it is doing, this has nothing to due with amazon, Blu is updating the phone and applying security patches as they said.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] KazuDante:
so 6.6 is just security patches and nothing more?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
Ok this makes sense, flashing all the way back to 6.1 and flashing this update would cause problems, as the patch is from 6.5 to 6.6.

Meaning you need to be using 6.5 to install this OTA.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] RainofOranges:
That's stupid that they allowed me to download it in the first place from the official OTA updater if I wasn't on 6.5 then.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] kal250:
I have opened the zip and examined the updater script, and it just seems odd to me that BLU has only updated the prime variant(no doubt at Amazon's request, too maintain their contract). Why update preloader and bootloader?? I'm probably over reacting but just seems funny to only update prime, when hardware is identical, seems minor to adjusf for a non prime OTA, which we have yet to see. No offense intended. Im not really a pro at this stuff, but I am concerned.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] RainofOranges:
This makes me want to keep the Prime ROM on my phone, only for the updates. I hope the OTAs come to the OEM ROM sometime.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] kal250:
I went from 6.1 to 6.5 skipping 6.4, but possible 6.6 was an incremental update.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
Doesn't seem fun or odd at all to me, My family has 5 Blu phones.

Blu makes several similar phones and only updates the flagships, the other are the sinkers they rarely get updates.

This is common practice from blu, that's why I got prime I wanted the flagship.

Of the 5 phones I have only two receive updates the other three don't.

In the end non prime users will simply switch over to the flagship prime.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
I just got time to install 6.6 OTA, LMAO BLU was sneaky, anyway enjoy your day.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] mrmazak:
You can't leave it like that.........

How were they sneaky?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Alex19Gam:
can i install the ColtonDRG non prime rom via twrp wiping data to convert my prime rom with removed the ads To OEM version??

this doesn't block the bootloader? this zip replace the system i guess, true?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] kal250:
I believe as long as you can get into fastboot to load TWRP and wipe data/restore backup. I don't think its going to replace bootloader or preloader if you updated to 6.6, but that should not matter. I make no promises and standard disclaimer applies, I am not responsible for bricked or broken devices.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] RainofOranges:
Just a note: to boot a recovery through using the "fastboot boot recovery.img" command from your computer the bootloader has to be unlocked already.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] kal250:
Does 6.6 relock? I have seen conflicting reports, Colton, I believe suggested bootloader remains unlocked, I think your report was you were relocked but succesfully unlocked again.... What a pain this latest OTA turned out to be, glad I waited....
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] RainofOranges:
I think it does, I had to run fastboot oem unlock again after updating to this so I could run TWRP.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Alex19Gam:
yes, i have twrp installed but i'm on ota 6.4, i hadn't updated yet, i don't care too much those ota updates if it will risk my phone to brick

i just ask if that rom only will change my system to OEM and don't change the recovery and bootloader
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
Bootloader is relocked, phone won't boot after applying OTA update until you unlock bootloader. If you have in the past unlocked your bootloader.

The new bootloader checks each partition, if any have been changed it blocks the phone from booting.

To get around this start phone press power and volume up, boot to selector choose fastboot then unlock bootloader, reboot your phone will then boot into recovery and format data, then phone can boot.

The sneaky part is you have to unlock the bootloader to boot, even though bootloader displays it's unlocked, and you lose your data cause data partition must be formatted, if you backed up your data via twrp to micro sdcard you can then reinstall your data so no problem, if no backup data is lost.

I have applied the update twice, once through stock recovery and once through twrp results are the same.

Twrp can install the OTA, just like the stock recovery can.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
If you flash either rom I uploaded, only system and boot.img are changed, I don't understand downgrading your phone, but it's your phone.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Alex19Gam:
It's downgrading? I just want to flash a stock rom without the ads of amazon, if ur rom don't have it, I can use that
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
If you flash non prime it's downgrading, if you flash stock prime rom you have ads, simple solution is just remove ads from 6.6

That's what I did have the most updated software with no ads.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
I will start providing updated ROMs, next ROM will be 6.6, the ROM will be just like these ROMs system and boot.img only replaced, that way no one loses the ability to use splash tool.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] viktorfk:
It says no mirrors when I try to download your TWRP recovery [MENTION=2472806]vampirefo[/MENTION], please help :(
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] RainofOranges:
There is a large banner at the top of the page that might help you.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] viktorfk:
Damn... didn't notice, I feel so dumb now haha, guess I'll just wait, thanks a lot [MENTION=7221761]RainofOranges[/MENTION] :D
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] RainofOranges:
It's all good, everyone overlooks things sometimes :)
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
I am currently uploading stock 6.6 rom, and will also upload modified 6.6 rom.

stock 6.6 rom is stock 6.6 rom minus the preloader_p6601.bin, lk.bin, logo.bin, secro.img, trustzone.bin, uboot.img from 6.6, so this rom is safe to use.

modified 6.6 rom is the same as stock 6.6 rom, plus amazon stuff removed, so no ads, updater is disabled also.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] ytsejam1138:
Just upgraded from V12 to 6.6. Thanks vampirefo.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] n3kf:
Assume I can move from 6.5 to this safely? Thanks for the great work. It's appreciated.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
Yes, you can go from any version to 6.6 as long as you can use twrp.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] AndroidBR:
Thank you so much for making 6.6 available to us all!

I have just dirty flashed your custom ad free 6.6 ZIP with TWRP on top of the the debloated, ad free 6.5 ROM that was made available by RootJunkie a while back.

Everything seems to be working properly. :)

My only question: what are the apps / systems apps that are safe to be uninstalled? There's a lot of MTK stuff, location em2, ygps, logs, fotaprovider, thermal manager, myos version, schedule power on off, product info, user dictionary, vCalendar, MTK battery warning, partner bookmarks, MTK float menu... I just want to remove everything not needed for the system to run properly and unhindered.

Would you guys be able to tell me which one of these are safe to uninstall?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
The Modified 6.6 is what I run on my phone, I haven't nor do I recommend removing any more apps.

I only removed Amazon stuff, the rest of the apps don't bother me, battery life is at it's best for me.

Phone runs smoothly, 6.6 update made the phone a little better, worked out the kinks in the software.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] jacewt:
Fabulous! I installed on my 6.5 with no issues. I also did the twrp google debloat script and everything was fine. Thank you so much.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] kal250:
Ok, I have successfully flashed over 6.6 stock(safe) via TWRP. Had to reroot. The issue I am experiencing is System app remover(root) fails on uninstall as does Solid Explorer fail to delete app folder(after granting root privileges). I seem to recall having this issue once before and required a clean install of everything from a fresh SPFT flash. I assume it a permission issue, just not sure how to correct. Solid Explorer supports systemless root as well as system app remover. Any suggestions?? I'm currently back on OEM V12 from TWRP backup and things just "work" again......
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
I don't use those apps, I use es file manager, but if you want to delete something, simply open the ROM remove what you want zip ROM and flash via twrp.

I really don't understand why people flash ROMs then try to uninstall stuff, when they can simply open the ROM before they flash remove or add whatever they want before flashing the ROM.

The ROMs I provide can be modified to one's own preference before installing.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] AndroidBR:
I've removed some of the built in apps without any error messages or random force close.

But I did notice that after using the phone for a while, the CPU cores don't idle in their offline / power save feature. They fluctuate at the 300 MHz mark, never going offline as they should. No matter if I force close every single app in the phone. I witnessed this exact same issue with 6.5 as well.

Has anyone else noticed something similar?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
I don't pay any attention to the CPU's so can't say.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] AndroidBR:
Also, AdAway stopped working after I flashed your 6.6 modded zip. Somehow it won't allow the host file to be written on the system.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
AdAway is from play store?

Edit Googled app installed working just fine, host file installed no problem.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] AtomicFizzle:
I'm on 6.6 and I still have some offline time.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] AndroidBR:
O

Thanks for your posts guys.

There's definitely something wrong with the device. I don't think it's the hardware, so more than likely it's something that went corrupt since my other 6.5 debloated ROM without Amazon ads that I flashed through MTK image loader.

Looks like I'm going to have to do a full wipe on my phone. As I said before, I've dirty flashed your 6.6 on top of another tweaked out 6.5 ROM so... I think that's my problem right now... Sighs... Here we go again...!

Can I do a full wipe and install your 6.6 zip file on TWRP without any problems?

Edit:

Last night I completely wiped my phone, including internal SD (which might have been a huge mistake).

Then I flashed your 6.6 modded zip and latest SuperSU in the end and rebooted. Everything seems to be working properly with the exception of AdAway. It loads and asks for root, but for some reason it is unable to write the recompiled hosts file. I don't know what's going on with it.

Could you guys help me out?

Thank you!

Edit 2: still don't know what's wrong with my phone regarding AdAway being unable to work.

Regarding the CPU cores, after 3h of up time the CPU cores are locked again in tandem. They all froze on the same frequency ranging from 300 MHz up to 1300 MHz. On CPU-Z it shows all 4 cores awake, so no suspend / offline estate when there are no apps running on background.

Only if I reboot the phone they will return their normal estate, that is only one core awake at 300 MHz while the other ones are offline when no apps are being used or there's any demand from the CPU. This is really annoying. Cause the battery drains a lot faster if I don't reboot the phone.

Edit 3: About root and AdAway - all I had to do was to install BusyBox and problems solved. Yeah I know, that was an easy fix.

About the CPU cores not idling in their offline state, I'm considering getting it replaced just to make sure I didn't get a defective unit.

What do you guys think?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] cococchio:
I am having problems copying the hosts file in AdAway? How did you fix it?

EDit

I installed a different BusyBox from GooglePlay and everything worked as described
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
I just installed CPU Z, with no apps running just CPU Z, CPU 0 is 299 other 3 are stopped.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] AndroidBR:
Exactly... I'm guessing there's a physical issue, internally with my device's CPU. Or it's just the way the kernel is supposed to be operating. For example, mpdecision is disabled or hotplugging is enabled by default after a little while. After a few hours of up time all CPU cores are awake, idling at 300 MHz. The only way of fixing that is to reboot the device.

I'm still getting lots of deep sleep time with my phone, the only problem is that the CPUs aren't switching to offline with the screen on.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] AtomicFizzle:
I think I see what you mean. I started CPU Z right after it booted up. After the startup stuff completed (which had all 4 at max), CPU 4 went offline, then 3, then 2 and it stayed that way while I was watching. Then I came back a few minutes later and all 4 are locked together and no offline while I'm watching.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] AndroidBR:
This... - that's exactly what's happening with my phone.

Depending on the app that I'm using, the CPU locks up all cores in tandem and even after I close all apps (force close) the CPU cores will not go back to the offline state. I think it's a glitch in the kernel...

The app that has been doing this the most with wakelock is AllCast. I use it to stream mp4 files to my Chromecast. After I close the app and force close it, the CPU cores will not return to the offline - power save state.

After a reboot everything goes back to normal with 1 core at 300 MHz and 3 cores going offline - until - I open AllCast once again... Then they all lock up once again at the same speed forever, until I reboot the phone...

Could you guys try this from your end?

There's several apps that will allow you to check this:

CPU-Z

CPU Spy

DevCheck

Wakelock Detector

PS: screenshot shows 4 cores idle (no apps running in the background) at 300 MHz... :(

Cheers!
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
My guess you are testing interactive governor, when you should be testing on demand.

Interactive governor steps up and down, if cores are ran at max it takes a while to return to offline several minutes.

Switch to ondemand, I use powersaver myself.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] AndroidBR:
Believe me, I've tried that too, switching governors did nothing.

Like I said, after I'm done using AllCast, there's nothing I can switch in the kernel settings that will make the CPU cores go back to offline (power save mode). Unless I happen reboot the phone, all cores will remain stuck at 300 MHz when phone is idle.

Even when the phone seems to be entering deep sleep, which by the way, only works when the phone is unplugged from the charger...

It appears that the kernel is buggy on the R1 HD... Apparently AllCast is the only app that triggers that with this particular device.

I can run AllCast all day long on my Nexus 5 and nothing of this nature happens to it, when I close all apps the phone idles normally, with 3 offline cores. And my Nexus 5 enters deep sleep when charging.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] AtomicFizzle:
I'm not using AllCast. How did you determine that app was triggering this condition for you? I didn't start any apps other than CPU Z and still noticed it happening after a minute or so.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] AndroidBR:
You read my previous message with the app list, right?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] AtomicFizzle:
Yes. I have messed with most of the tools, but don't see how you make the correlation. Also I couldn't find "DecCheck"

Are you saying that if you disable or uninstall AllCast that this will never happen for you? Like I said, I do not have that app installed at all.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] AndroidBR:
Well, it's not a correlation. It's a fact. The moment I run AllCast on my R1 HD all four CPU cores lock up on the same speeds. Which is fine. But when I'm done using the app, I close it, even proceed to force close it to no avail - all cores remain locked "awake" at 300 MHz. It's probably a glitch in the kernel with this particular app.

The only way to fix this is a reboot.

Haven't found any other apps that does the same thing on my R1 HD.

It's possible that it has something to do with accessing larger files (only reading) the external SD card. I have no idea, but it's a possibility.

This morning I've rebooted the phone and it's almost noon and all cores are operating normally when idle. 1 core at 300 MHz, 3 cores "offline".

The app name is DevCheck by flar2. I also use his EX Kernel Manager.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] wilberzone18:
this method can convert non-prime prime?

this method can convert non-prime prime?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
Yes.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] AtomicFizzle:
I rebooted this morning too and used it lightly throughout the day. The issue never occurred, CPUs 2-4 would ramp down and go offline when the screen was on and I was not doing something intensive. 9 hours of it working as it should. I tried running various apps to see if I could recreate the issue. I noticed the CPUs stuck at 4 after watching a video within the embedded browser in Feedly. I rebooted a few minutes after and now it's locked again just a few minutes later. The only apps I have run are 3C Toolbox Pro & Tapatalk. I'm using 3C for CPU monitoring in the notification bar, since I already paid for that one a while ago and it's something it can do. I have also tried force killing all running apps with the 3C app but it doesn't make any difference. All 4 cores get stuck active.

So it's really not clear what's triggering this for me yet... But I am wondering too if the kernel is maybe just a little buggy. Probably most people wouldn't notice or care, I guess.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] AndroidBR:
Yep, it's happened to me as well. Didn't run AllCast at all today, but currently my cores are locked in tandem... Not a single core is being allowed to enter their respective "offline" mode. This thing really blows...

It's probably a glitch in the kernel in the way it controls mpdecision and hotplugging. That's what we get with a MediaTek powered device that costs 60 bucks. I'd never pay more than that for a phone like this.

For what it's worth I'm pretty happy with the phone.

But no custom kernel and ROMs plus this glitch with the original kernel, it's pretty much a burner phone for me.

Thank you so much for taking the time to look into this. I really appreciate it.

At least now I know I'm not the only one suffering from this and that it's not a hardware related problem.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] wilberzone18:
thanks, when I get the cell proves this method
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] AndroidBR:
I thought Stagefright had been fixed with Android 6.0... Our devices are still vulnerable... WTF was Amazon thinking and what are they doing to solve this...?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] RawSlugs:
If I'm on 6.5 prime, systemless root, no ads,

What's best zip to update to 6.6?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
Modified 6.6, currently I am running custom ZenUI ROM, but as far as stock rom goes modified 6.6 would be my recommendation.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] lycsky:
Hello,

May I know if this is an update to 6.6 or to flash a new ROM that will wipe out phone's data/app?

Thank you.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
You don't have to wipe data, if you go to stock 6.6 if you used modified then you should wipe data, you don't have to but should.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] lycsky:
Thanks!

I am currently on 6.4 from this thread. So I think I should wipe data/app if I want to flash your 6.6 version?

http://xdaforums.com/r1-hd/development/blu-r1-hd-remove-amazon-ads-ota-updates-t3427303
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
You should be able to flash modified 6.6 without wiping data. Seeing you are running a modified version already.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] afuller42:
Credits [MENTION=5355478]ColtonDRG[/MENTION]

[MENTION=4939713]lopestom[/MENTION]

[MENTION=5186178]bluefirebird[/MENTION]

[MENTION=4843777]onlykhaz[/MENTION]

[MENTION=4239374]ss2man44[/MENTION]

[MENTION=3963379]AtomicFizzle[/MENTION]

[MENTION=2472806]vampirefo[/MENTION]

Thanks for your work on this device
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Jep56:
Thanks for the work. My phone will not let me mount a USB drive.Stickmount dies not see it. When in TWRP, it won't let me select USB to mount. Suggestions?

---------- Post added at 08:32 AM ---------- Previous post was at 08:11 AM ----------

Also, does not seem to read my micro SD. Just says "checking"
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
My Samsung 64bit micro sdcard works just fine, never tried USB stick.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] kal250:
Likewise I had a PNY Elite 64GB, seen it just fine, what brand SD are you using??
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Dark_Balor:
The BLU can't power any usb key or any other kind of device it's micro-usb port. You need to use a OTG cable connected to a powered source to make the BLU see anything.

You can find online some Y OTG Cable made for this, to power the external device.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] crazy_bdog:
dirty flashed via internal sd card (lopestrom twrp) from ColtonDRG v12 to modified 6.6 with no issues. was having in call volume problem in v12 and so far everything working perfect in modified 6.6. might do clean flash if I find some time to reinstall apps. thanks vampirefo!
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] Jep56:
How do I create a short cut for a document?