yashsingh1/xdaforums huggingface dataset:
[BLU R1 HD Guides, News, & Discussion] Dark_Balor:
I decompiled the APK, this is the android manifest of the GBA app from mediatek:

<?xml version="1.0" encoding="utf-8" standalone="no"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android" android:sharedUserId="android.uid.phone" package="com.mediatek.gba" platformBuildVersionCode="23" platformBuildVersionName="6.0-1478669896">
<uses-permission android:name="android.permission.INTERNET"/>
<uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED"/>
<uses-permission android:name="android.permission.READ_PRIVILEGED_PHONE_STATE"/>
<application android:label="@string/app_label" android:name="GbaApp" android:persistent="true">
<service android:name="GbaService"/>
</application>
</manifest>

I found this post about GBA: http://xdaforums.com/showthread.php?t=1430405 and of course https://en.wikipedia.org/wiki/Generic_Bootstrapping_Architecture

The name of the application is GBA Service. I can see in the different string that it gather the IMEI of the device which would make sense when trying to authenticate a device on a VoLTE network.

It would seem to be linked with VoIP which would surely explain the VoLTE feature added.

Edit: it not even an app, it seems to only contains xml file, configuration files with different ports.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Yours is larger than mine, yours is prior to 6.6 update.zip
[BLU R1 HD Guides, News, & Discussion] mrmazak:
It was what 6.1 downloaded
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Anyone have the 7.4.2 boot.img, they could upload?

edit, I was able to patch the one I had, so now i have what I need.
[BLU R1 HD Guides, News, & Discussion] Tiggam:
I'd like to move to 7.4.2 but I'm currently on converted V12 how can I accomplish this without locking my bootloader? I would like to keep TWRP and root.

Looks like vampirefo is working on it.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
It looks like [MENTION=2472806]vampirefo[/MENTION] is. I stripped out the lines in the update script that do the boot image and preloader and trust zone things, but not sure the rest of the system patches are needed. And i don't think I will be able to find out. I have Att so band 12 dosent effect me.

I put the stripped down script on github to share.

https://github.com/mrmazakblu/R1-HD_v7_UPDATE_SCRIPT

I think that more can be removed to get just the lte band 12 by itself, But updating the system apps might be a good thing to do.

Update;

Updated ROM has been published. Not really any need to mess with this update any more.

http://xdaforums.com/r1-hd/development/prime-stock-rom-6-5-flashed-via-twrp-t3455532

Thanks to [MENTION=2472806]vampirefo[/MENTION] for his quick work.
[BLU R1 HD Guides, News, & Discussion] KazuDante:
Notice something , before with the older version i could switch aroud the boot.img and that did not affect the rom but with 7.4.2 if you switch boot mobile network does not work. But using the 7.4.2 boot on the older version does not affect them.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
That is cause the kernel is different, the kernel source we have is now no longer any good, we can't build this kernel from our current kernel source.
[BLU R1 HD Guides, News, & Discussion] KazuDante:
I quickly assumed that too and requested the source code of the new kernel...hope i get it
[BLU R1 HD Guides, News, & Discussion] kb3wmh:
It looks like Blu Phones have another backdoor...

http://arstechnica.com/security/201...und-preinstalled-on-3-million-android-phones/

From what i can tell, this is different from the one earlier this week.
[BLU R1 HD Guides, News, & Discussion] raderator:
R1 HD not listed. I've always been on the latest update so not too worried.

https://www.kb.cert.org/vuls/id/624539
[BLU R1 HD Guides, News, & Discussion] dorkydroid:
hey guys, i have the prime version with rooted and unlocked 6.0 still on it. i have twrp installed. can i flash the 7.4.2 rom directly over it through twrp or will that cause problems with all the 6.0 stuff that was never upgraded? and is this 7.4.2 a true nougat rom?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
Defiantly not nougat.

It is still 6.0 just version 7.4.2. Of the Amazon package. It is not an OS upgrade just "security" updates.
[BLU R1 HD Guides, News, & Discussion] Autolounge:
Any word on a Nougat update? I read rumours that Blu supposedly promised it.
[BLU R1 HD Guides, News, & Discussion] theredbaron1834:
From what I have heard, they are know for making promises and then not delivering. A very BOLD stance....
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Unlikely, if they do it will come with a preloader that makes the device unlockable.

Meaning no root, no removing ads.
[BLU R1 HD Guides, News, & Discussion] Ricardianos:
I have the amazon stock version with the last update. Is it impossible to root it and get rid of the ads now?

Enviado desde mi R1 HD mediante Tapatalk
[BLU R1 HD Guides, News, & Discussion] ariesgodofwar:
Use the 7.4.2 version here, no ads http://xdaforums.com/r1-hd/development/prime-stock-rom-6-5-flashed-via-twrp-t3455532/page1

See the OP on Page 1
[BLU R1 HD Guides, News, & Discussion] Ricardianos:
Thanks for the answer men but what do you mean with "the OP"?

Edit: my phone don't have custom recovery such as twrp or other. Is stock, new.

Enviado desde mi R1 HD mediante Tapatalk
[BLU R1 HD Guides, News, & Discussion] ariesgodofwar:
OP=Original Post(er). You would need to unlock bootloader and install custom recovery to use.
[BLU R1 HD Guides, News, & Discussion] Autolounge:
Go to the very first page. Op means the person who opened the thread.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
I was sent a link by [MENTION=4939713]lopestom[/MENTION] containing some interesting files for the R1 as well as other BLU phones:

http://220.243.199.35/hwfotadown.mayitek.com/ota/root_data02_1/TINNO/tinno6735_6.0/

(For files pertaining to us, go the the R1_HD folders. We may also be able to use some stuff in the P6607 directory as well, according to the user that sent this.)

I haven't searched them too deep yet, but from what I've found so far they contain interesting firmwares, or at least hints to firmwares. I saw in the 10UU directory files regarding not only the 6.1 and 6.4 prime firmwares we already know about, but some things about supposed 6.4.1 and 6.3 Amazon firmwares as well. Some of these files, like the 6.3 ones, are what the server calls "selftest" files, and considering they're less than 1mb in size, I doubt they're actual firmware, rather maybe some sort of checksum. Others, like some regarding 6.4.1, seem to be OTA-update sized zip files.

The 11UU folder contains vanilla firmware files: not only the V12 we know and love, but supposedly a full OTA file (not full firmware, just an update) for V6 vanilla firmware that's about 70mb, as well as more selftest's from firmware versions V6, V9, V10, and V12.

Update: Antonio said this site doesn't contain any leaked files or anything, just a repo for where OTAs are saved (as I figured after exploring a bit more). Anyone can access this site, so no need to quickly download and save anything as our access won't be cut off since we aren't going anywhere we aren't supposed to. While OTA update zips probably aren't all that useful, we can now access some OTAs we've never heard of before, like Prime 6.4.1 and Vanilla V6.
[BLU R1 HD Guides, News, & Discussion] raderator:
Just ported to Red Pocket (ATT) , $150/yr for 1K mins and texts and 1 GB. 14mbps, hotspot works. Tmo also available (Verizon too but not for our phone). This is the perfect el cheapo plan for the perfect el cheapo phone. $12.50/month.

http://www.ebay.com/itm/131593551826

There was a $15 coupon but I missed it. May come back.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Sounds interesting, I use straight talk myself, have used it for years.

I may look into this though for a second phone.
[BLU R1 HD Guides, News, & Discussion] 0xd0gf00d:
It seems that the v17 ROM for the non prime version is out. Is it safe to update it will it lock the bootloader and I should use an alternative?
[BLU R1 HD Guides, News, & Discussion] vampirefo:
No ideal, haven't seen it.
[BLU R1 HD Guides, News, & Discussion] 0xd0gf00d:
Just saw the update today using auto update on my debranded phone.
[BLU R1 HD Guides, News, & Discussion] rwvolfan:
I used Colton's to convert to OEM to V12. Then I installed modified 7.4.2. a couple days ago. Everything seems great. But my phone just downloaded an update. I haven't installed it. There's an icon in upper left of screen saying new version available. Not sure what to do.
[BLU R1 HD Guides, News, & Discussion] MDKAOD:
I just got a system update on my Prime -> Stock R1. (BLU_R0011UU_V17_Generic_6.0_20161115-1444)

VoLTE & Band 12 support as well as Android Security Updates according to the patch notes.
[BLU R1 HD Guides, News, & Discussion] Tiggam:
I got the same notification, I'm a little worried about taking it but I want this update.
[BLU R1 HD Guides, News, & Discussion] emc2cube:
[MENTION=6680544]bibikalka[/MENTION] V12 to V17 OTA direct download link:

http://hwfotadown.mayitek.com/ota/r...17_GENERIC_6.0_20161115-14441479825306011.zip

To everyone, I would suggest you to wait until contents of the update are analyzed before applying it. It does patch a new preloader, lk, uboot etc. They have a different md5 than ones in Prime V7.4.2 but better be careful.
[BLU R1 HD Guides, News, & Discussion] AsteriskAmpersand:
Got update v17 today on my stock r1 hd 2gb model with twrp, currently it is patching and making progress in twrp recovery. Will update after everything is finished.

In a bootloop, can get into fastboot to restore backup though.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
One user in hang outs thread has taken the update. It did remove use of sp flash tool. And took OEM unlock out o developer options. But he was unlocked before and after update it went to boot loop and stayed unlocked but went secure. So doing OEM unlock brought it back usable again.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Basically this is just prime 7.4.2 update.
[BLU R1 HD Guides, News, & Discussion] bullet25:
Looks like we are going to need a TWRP flash-able zip that doesn't update the preloader, uboot, lk, etc.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Yes, I will be making one.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Well I updated my phone to V17 just now, doing a little testing. I am using my own safe method, upgrade via TWRP, I didn't directly upgrade via OTA.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
stock_V17_OEM_rom.zip has been upload and download link has been added.
[BLU R1 HD Guides, News, & Discussion] emc2cube:
So to try to understand a little the various partitions roles, which part of the OTA update script should be removed to be "safe"?

My guess is that we need to prevent at least preloader_p6601.bin, lk.bin, logo.bin, secro.img, trustzone.bin, uboot.img to be patched but is removing lines such as

package_extract_file("lk.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/lk");

enough or do they need to be replaced by something else?
[BLU R1 HD Guides, News, & Discussion] vampirefo:
I manually patch on my Linux, I don't risk my phone. Once I have applied the patch on my Linux I then build a twrp installable ROM, install that ROM on my phone if all goes well I then upload that ROM.

I never run OTA on any device I have, I download the OTA, and unpack it, then I take a stock ROM, that the OTA is for, then apply the patch on my Linux. Once patch is successful, I build a flashable ROM, install on my phone, then patch boot.IMG.

Run several test, install several times then upload ROM.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
Just to add my two cents here. I agree with [MENTION=2472806]vampirefo[/MENTION], his methods are solid. But to try and answer some of your question.

Preloader handles system loading from power off to the next stage the "lk"(little kernel).

Preloader is the part that controlls sp flash tool. So don't update

Lk is the bootloader. The menu you see when you hold power up and power. And it is also in control of fastboot mode.

They changes something is lk also. (When in fastboot mode used to be able to use "fastboot reboot" and phone would reboot. With new lk.bin (u-boot) "fastboot reboot" does nothing). So do not change this.

Logo.bin is the image you see on Screen while power on before the boot animation, also the battery charging image you see when changing with phone off. Should be ok to allow this one to change.

Secro.img has in part something to do with the file structure of nvram "imei". And since the baseband is updated to include band 12 and volte it might be good to allow this o e to change also.

One part you did not mention that should be avoided is the Sig folder. And the line that applies signatures to the system and recovery. (I did not look at this v17 update yet, but based on the past OTA this line was there)

Trustzone still has me little confused what it is for. Bit has to do with such things as useing Android pay and similar services that need a secure environment inside

There may be more concerns too. Like the settings app being updated. It has removed the option from developers options menu to select oem unlock.
[BLU R1 HD Guides, News, & Discussion] emc2cube:
Thanks [MENTION=2472806]vampirefo[/MENTION] and [MENTION=5312578]mrmazak[/MENTION] for the infos

Yes I agree that the methods are solid, but as the TWRP script basically only restore a fresh /system and boot.img I'm trying to understand what the script is actually doing with all the other partitions and what's going on, more for my own curiosity than anything else.

So far:

- lk / uboot: I'm still confused by the weird way the OTA seems to unpack uboot as a lk.img then write it to a lk folder while a little later it will flash lk.bin from the OTA package to /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/lk

- secro: is patched by the OTA but not by the TWRP script. May be a problem if required for band 12 then?

- logo: is patched by the OTA but not by the TWRP script. Not sure it matters much.

- preloader: I already got it that it was the anti-sptf and definitively not to be updated, so all good on this one

- trustzone: I had no idea of what it was used for, or what's going on during OTA with these tee1 and tee2 "switching". It do not seem to be required to update it at least to boot (as TWRP script don't update it)

As for signing, yes it's there in V17 for boot. I would assume we need to keep it applied for the boot.img to work properly?

There is also a recovery.sig file but it do not seem to be used by the OTA (instead it's patching /system/etc/recovery.sig) and OTA actually removes "/system/recovery.img" that was present in V12.

I should try to look in details how to install a R1 rom on a linux (I'm on a mac so if you guys have a ready to use tutorial / file / virtual machine that you can share hit me in PM, else I will google that a week end at some point)

I commented out a few lines in the OTA updater-script file that basically *should* perform a safe upgrade. If you have a safe way to try it out by renaming it (removing .txt extension required to upload it here) and replacing the original one from the OTA let me know how it goes. Please no one try it on their phone, it will probably fail / brick it!

It should then be easy to see what happens if secro / logo and trustzone are changed, if you have a safe way to try on linux.

Out of topic:

It seems the V17 update "officially" turn OTG support off by updating /system/etc/permissions/android.hardware.usb.host

<permissions>
<!--<feature name="android.hardware.usb.host" />-->
</permissions>
[BLU R1 HD Guides, News, & Discussion] 0xd0gf00d:
So I had converted my prime version to non prime version leaving other things as is. Can someone point me how to install twrp so that I can safely use the modified ROM in http://xdaforums.com/r1-hd/development/prime-stock-rom-6-5-flashed-via-twrp-t3455532 ?
[BLU R1 HD Guides, News, & Discussion] Tiggam:
This thread should help
[BLU R1 HD Guides, News, & Discussion] mrmazak:
isn't this an added file to turn on the feature?

i could not find that file on my current v12.

i also made a "work in progress" modified updater-script, put it on github to make notes on why parts are taken out. There is no guarantee this is safe or even if it will work. I just put it on here for those who insist on tampering with things, and do not like to use proven safe methods others have already posted.

https://github.com/mrmazakblu/R1-HD_v17_UPDATE_SCRIPT
[BLU R1 HD Guides, News, & Discussion] vampirefo:
<! Disables it.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
ok.

then there could also have been changes made to "/system/framework/com.android.future.usb.accessory.jar" that can effect the usb host too.?
[BLU R1 HD Guides, News, & Discussion] vampirefo:
I haven't look into, but it could be.
[BLU R1 HD Guides, News, & Discussion] emc2cube:
True, but adding it manually (without <!-- and --> ) was helping for some apps to use USB OTG. But even with this you had to use some powered hubs etc and was quite unreliable (never worked in TWRP either).

I don't think we will ever get a proper USB OTG function as it seems there is an actual hardware limitation, nothing can be powered by the R1 micro USB port.
[BLU R1 HD Guides, News, & Discussion] bibikalka:
Is this actually confirmed ? It'd be easy to update secro via SPFT later, but is there any impact on band 12 ? I am not using Tmobile, so cannot test ...

Agreed, this weirdness is puzzling. I have looked at this a bit as well. What is interesting is that this "double" update of LK started to happen when they started updating the preloader partition. The "double" update was not present in V6.1 to V6.4 OTA, for example. One theory is that it may be doing something to "unlock" the preloader area for writing, I recall there were issues when attempts were made to write to the preloader area in TWRP. Another theory is that it's just sloppy programming, since I've compared uboot.img to lk.bin, and they are identical within the same length, but lk.bin is slightly longer, and seems to have some non-zero data right at the end. Is this just junk, or does it get used for something ? ...
[BLU R1 HD Guides, News, & Discussion] mrmazak:
"The secro.img contains the routines to copy a valid copy of NVRAM into data partition (if not exists)" quoted from http://bbs.elephone.hk/thread-3709-1-1.html

I think that they are doing the double write so they can apply the signature. The last line before the second write to lk is "apply signature"
[BLU R1 HD Guides, News, & Discussion] bibikalka:
OK, but it seems to work just fine without the 2 updates in V6.4 update (from V6.1):

assert(run_program("/system/bin/dd", "if=/dev/zero", "of=/proc/driver/mtd_writeable", "bs=3", "count=1"));
assert(package_extract_file("uboot.img", "/tmp/lk.img"),
write_raw_image("/tmp/lk.img", "lk"),
delete("/tmp/lk.img"));
apply_sig(package_extract_file("sig/boot.sig"), "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/boot");
show_mtupdate_stage("/cache/recovery/last_mtupdate_stage");
ifelse (
less_than_int(get_mtupdate_stage("/cache/recovery/last_mtupdate_stage"), "3") ,
(
if less_than_int(get_mtupdate_stage("/cache/recovery/last_mtupdate_stage"), "2") then

ui_print("start to update alt loader image");
package_extract_file("trustzone.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/tee2");
set_mtupdate_stage("/cache/recovery/last_mtupdate_stage", "2");
endif;

I think the double update is just sloppy work ...
[BLU R1 HD Guides, News, & Discussion] 0xd0gf00d:
Sorry if this was discussed but is there a way to disable the BLU warranty prompt? I have a debranded phone and am not sure if I want to register for warranty through the app ☺
[BLU R1 HD Guides, News, & Discussion] Tiggam:
If you are rooted, it can be uninstalled.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
Is anybody using adaway with v17 ?

I had been using the app for years. , But with v17 I could not get it to recognize root, then after fresh install of both newest versions of SuperSU and the adaway app it saw root, but always fails to write the host file. (/System/etc/host)
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Probably need permissive boot.img to allow correct mount system correctly.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
I was thinking that, so I tried selinux mode changer(same app I used to make FM radio work), did not help. I tried the boot image from v12 I stead of the patched one for v17, did not help.

Do You think it could be a metadata permission set differently?

This seems to be similar to the root problems I was reading about from other posts relating to a file manager not able to create files in /.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
I think permissive boot.img and system root should fix it.

Unusually I don't use rooted cell phones, but will root this one with V17, permissive boot.img and system root, I really don't care for systemless root.

To see if my guess is correct or not.
[BLU R1 HD Guides, News, & Discussion] KazuDante:
is there a sure way or resizing the system partition to at least make it 3gb ?
[BLU R1 HD Guides, News, & Discussion] Tiggam:
Where can I get a permissive boot.img?
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
I think that requires a different kernel, I.e. one that is permissive by default, and last I was involved with that we were unable to make one of our own to fit that need.

If you need /system to be mounted to install AdAway, you can try manually mounting /system through a terminal app before attempting to install it, maybe it'll work as a temporary workaround or something:

In a terminal emulator app, after typing "su" to get root permissions for the terminal session, type "mount -o remount,rw /system", and after it does this see if the ad blocker app will install correctly.

EDIT: You can also do this through adb from a computer, just enable debugging on the phone and access the shell with "adb shell" on your computer before trying (and once you're in the shell, type "su" to get root permissions for the shell session)
[BLU R1 HD Guides, News, & Discussion] Tiggam:
Thanks and all, however I was wondering for different reasons.

I'm fairly familiar with adb and cli. Already have adaway set.
[BLU R1 HD Guides, News, & Discussion] theredbaron1834:
I am not on the latest rom, but am on the latest adaway. It added the ability to work systemlessly. You might want to play around with the settings, see if tinkering with that could help.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
I wasn't able to put check mark into the menu option for systemless superSu.
[BLU R1 HD Guides, News, & Discussion] 0xd0gf00d:
Tmobile uses LTE in my area. Before the upgrade to v17, v12 used to connect with LTE. However, since the upgrade it always connects via 4G. I noticed that the option to use LTE for calls was missing for SIM1. So I switched to using SIM2 (and put Freedompop SIM in SIM1) but despite choosing the option to use LTE for data as well as voice, the phone always connects to 4G. Has someone encountered this and any workaround? (FWIW phones connect to Band 4 here)
[BLU R1 HD Guides, News, & Discussion] mrmazak:
After seeing several posts on the adaway thread, problem seems to be with other devices too. But strange that the app works fine on v12 and not v17. They are both Android 6.0.
[BLU R1 HD Guides, News, & Discussion] calm_depression:
havent been keeping up with this forum how has progress been over the last 2 months. Also happy holidays everybody