yashsingh1/xdaforums huggingface dataset:
[BLU R1 HD Guides, News, & Discussion] Oscar_david:
Fbombs killed everyone on the thread! :D :D :D
[BLU R1 HD Guides, News, & Discussion] jrk190:
It's weird, no messages on this thread or in development, guess everyone is partying for labor day
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
Don't worry guys were still active and trying. Just nothing newsworthy to report. Still running into problems we don't know how to fix. Google isn't a big help either. Our current dilemma is something called libminui being missing and we don't know how to get it or make it.
[BLU R1 HD Guides, News, & Discussion] kal250:
I have no idea what I'm looking at and I'm sure your Google search skills are better than mine but just in case....... this is all I found....if it's useless sorry I wasted your time...

https://android.googlesource.com/platform/bootable/recovery/+/9905f3a^!/

http://xdaforums.com/showthread.php?t=1846651&page=168
[BLU R1 HD Guides, News, & Discussion] bullet25:
So the gist of what is going on right now is every time I try and build CM I run into the error that "libminui.a" is missing and needed for some other thing. As far as I can see "libminui.a" is not like the "import_includes"/"export_includes", files which can be empty, they are some special compressed file. I can't find "libminui.a" anywhere on the phone so I'm guessing its not a proprietary file. The best I can find is it is related to the/a recovery somehow. If I try building with target has no recovery tag it takes longer but still gets the "libminui.a" error. I tried cloning that google source but just having the files anywhere in the build directory or linked to from a .mk file causes CM to not even know how to start the build anymore.

Until I can get some kind of help about this "libminui.a" issue, there is no way I will be able to continue. I do not have the knowledge or skill to figure this out myself. I asked around in a few areas and have gotten no response.

Here are my device trees: https://github.com/Bullet25fxbx
[BLU R1 HD Guides, News, & Discussion] anbaude:
I found this posted elsewhere on the net. Maybe helpful?

"if you had libminui compile problems, ensure you are using feature-freeze (latest) hybris-11.0 manifest, and don't use latest kernel and device of one+ - try to match the dates	09:06

uhhimhere: from recovery"
[BLU R1 HD Guides, News, & Discussion] bullet25:
Can you link to where you found that please?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
a google word search of that text returns this irc chat from 2015

dont know if its where he got it from though. here it is confusing and out of context

https://www.google.com/url?sa=t&rct...Ocv0ZGFUq68xCwITw&sig2=PmNPVz-ma_FqVPLsvPTDRQ
[BLU R1 HD Guides, News, & Discussion] bullet25:
Yeah they aren't talking about CM with that log at all though.

Plus that hybris-11 thing just seems to be some guys branch he made for his devices. There's a couple of device trees all by the same guy that have hybris has a branch on github. Again looking like they are all related to SailfishOS
[BLU R1 HD Guides, News, & Discussion] anbaude:
Sorry, I supposed that would help. Just random googling and came across it. Looks like an IRC log from last year.

http://www.merproject.org/logs/#sailfishos-porters/#sailfishos-porters.2015-01-08.log.html
[BLU R1 HD Guides, News, & Discussion] calm_depression:
Anyone else noticing slowdowns with exposed enabled, its like the phone takes much longer for simple tasks, idk.
[BLU R1 HD Guides, News, & Discussion] Oscar_david:
Have you added a particular module lately? I have xposed installed with no issues at all. But I only have YouTube background play and gravity box installed.
[BLU R1 HD Guides, News, & Discussion] calm_depression:
Nope I have a ton of modules installed, its just something I decided to post about now. Like 20 lol, including gravity box, minmin guard, greenify, forcedoze etc
[BLU R1 HD Guides, News, & Discussion] Oscar_david:
Maybe it's to many??? Hehe.... Idk.
[BLU R1 HD Guides, News, & Discussion] triggerlord:
I think you've just got to many. I've got like three installed and there is no slowdown.
[BLU R1 HD Guides, News, & Discussion] bullet25:
Yeah, no, dude, that is waaaaay to many. Xposed already screws with the system in an unsupported way.
[BLU R1 HD Guides, News, & Discussion] :
Unsupported is an understatement. I'm a huge fan of Xposed, but especially when you're dealing with intrusive **** like GravityBox, there certainly are limits to what you can do without causing problems, especially in recent versions of Android.
[BLU R1 HD Guides, News, & Discussion] DarkBlood.:
Some modules slowdown the phone a bit
[BLU R1 HD Guides, News, & Discussion] kb3wmh:
Does anyone else have this problem? On my R1 HD, I've noticed that my status bar click has started updating only intermittently--to force it to update i have to rotate the screen. Could this be an issue with Xposed? I had gravity box with a few status bar tweaks, but disabled it to try and fix the issue, to no avail.

It seems to only happen when I need the clock most... ????

I'll probably try disabling Xposed to see if that fixes it.
[BLU R1 HD Guides, News, & Discussion] antmiu2:
Thank you for the noob proof guide, Worked on my 16gb prime version - using flashtool v5.1632
[BLU R1 HD Guides, News, & Discussion] :
It might be an issue with the Prime ROM? Are you running that? It could also be a documented issue with the status bar under a handful of Xposed Modules, GravityBox included. Try enabling the Force AOSP mode in GravityBox. That fixed some similar issues for me.
[BLU R1 HD Guides, News, & Discussion] kb3wmh:
Yeah, I have the Prime ROM. I removed the ads before the conversion was released and haven't felt a need to convert. I'll try the force AOSP option.
[BLU R1 HD Guides, News, & Discussion] :
Fair enough. I think Prime conversion is always worth it, no matter how much tweaking you've done to the Prime ROM, but maybe I'm biased. Fwiw, the Prime version has an altered systemui and keyguard that causes problems similar to the ones you described, so that could be entirely related.
[BLU R1 HD Guides, News, & Discussion] Javiefs:
I have a new update in version prime , V6.6

Enviado desde mi R1 HD mediante Tapatalk
[BLU R1 HD Guides, News, & Discussion] emc2cube:
I can confirm.

Update is dowloaded from http://hwfotadown.mayitek.com/ota/r....6_GENERIC_6.0_20160823-20201472826184648.zip
[BLU R1 HD Guides, News, & Discussion] RainofOranges:
What does the OTA contain? I still don't see one for my non-Prime. I'm honestly thinking about converting to the Prime version just for the OTAs.
[BLU R1 HD Guides, News, & Discussion] emc2cube:
August 2016 security patches and "Minor updates"
[BLU R1 HD Guides, News, & Discussion] RainofOranges:
Poking around the zip file, it's pretty small. The biggest patch is to Google Play Services, but there are lots of little patches here and there. Seems to be a boot.img patch as well, don't know what that could mean.

Edit: Out of curiousity, has anyone tried the local file option in the updater? What would happen if I loaded the OTAs in my non-Prime version?
[BLU R1 HD Guides, News, & Discussion] emc2cube:
Seems this update is doing some funky things. The file also reflash a fresh lk.bin which, I think, may relock the bootloader.

ui_print("start to update general image");
package_extract_file("lk.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/lk");
package_extract_file("secro.img", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/secro");
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo");
assert(package_extract_file("preloader_p6601.bin", "/tmp/preloader_p6601.bin"),
write_raw_image("/tmp/preloader_p6601.bin", "/dev/block/mmcblk0boot0"),
delete("/tmp/preloader_p6601.bin"));
set_mtupdate_stage("/cache/recovery/last_mtupdate_stage", "1");

After update on a cleanly restored 6.5 prime (system / boot) I ended up in a bootloop.

This eventually ended on a black screen and unresponsive phone, maybe bricked.

Will have to look into that later I guess but I would recommend caution.
[BLU R1 HD Guides, News, & Discussion] RainofOranges:
Yes my phone bootlooped too. I fixed it just fine.
[BLU R1 HD Guides, News, & Discussion] emc2cube:
What did you do to fix it?

Mine do not seem to like SPFT, it looks like it just turn on for a second before shutting down while trying to restore the roms. I do not even get a white screen, it stays black.
[BLU R1 HD Guides, News, & Discussion] RainofOranges:
Are you able to get into fastboot mode? In case you don't know how, hold volume up and power on, then select fastboot mode from the menu.
[BLU R1 HD Guides, News, & Discussion] emc2cube:
No fastboot access, or success in flashing via SPFT. Just a black screen.
[BLU R1 HD Guides, News, & Discussion] :
Mirrored in the usual place.

https://na.mirrors.coltondrg.com/coltondrg/r1hd/stockota/prime/

I recommend extreme caution with this update. It seems like Amazon might be trying to lock down the bootloader. I'm very curious to see what becomes of this. I just hope they didn't find a way to keep us from using SPFT like they have with the latest Fire tablet. I *think* that whatever they're using on the Fire tablet is something that could not be replaced by an update (or at all for that matter), but better safe than sorry. Now would be a good time to switch to non-Prime for anyone on the edge. Fwiw, it is also entirely possible that they're planning to replace the bootloader with one that actually checks the signatures of booting images, which will stifle future development as users who take the update will be unable to flash TWRP, or will be unable to boot it after flashing it anyway. I would hope that having an unlocked bootloader would prevent this from causing a problem, but knowing Amazon, they'll relock the bootloader too (or worse, make the bootloader ignore the unlock state). It remains unclear to me weather Amazon or BLU is in control here and exactly what is going on, but I suspect that this is almost entirely Amazon's doing (possibly with BLU's help) and if/when similar updates for the non-Prime are released, they don't have such weird things going on.
[BLU R1 HD Guides, News, & Discussion] RainofOranges:
I've had more luck with this phone using Linux, maybe try that if you're not already.
[BLU R1 HD Guides, News, & Discussion] :
This is very interesting. I wonder what could possibly be causing these bootloops? Did someone **** up? Does it bootloop everywhere, or just on our tweaked phones? Are there any modifications you did? (namely bootloader unlocking)? How long did you let it bootloop before this happened?

How did you fix it? Just using SPFT? How long did you let it bootloop before fixing it?

That sounds bad. I would tell you to try turning the phone completely off (hold volup and power for 12 seconds) in case it's still stuck on, but I imagine you either already tried that, or ruled it out.
[BLU R1 HD Guides, News, & Discussion] RainofOranges:
Writing how I did it now in this thread

---------- Post added at 10:26 AM ---------- Previous post was at 10:23 AM ----------

It looks like they updated the bootloader for whatever reason. It seems to ignore locked vs. unlocked status and the update is locked by default. This could explain why I had to re-unlock my bootloader and could also explain the boot loops, because the locked bootloader is looking for official and unmodified software and boot looping because it can't find unmodified software. When I used fastboot to boot TWRP and flashed the stock ROM with it, it booted just fine which seems to support this theory. After that I re-unlocked my bootloader and flashed TWRP, the Prime debloat, and SuperSU.
[BLU R1 HD Guides, News, & Discussion] emc2cube:
Yup, already tried. It bootlooped for a solid 10minutes. I forced it off and since then black screen, no response. Red LED shows up if plugged that's it.

It's possible that I got the preloader corrupted (as it's also updated with the OTA) and in this case I will probably have to exchange it.
[BLU R1 HD Guides, News, & Discussion] :
Really? The OTA replaces preloader? That is a huge point of concern here. It's now all but confirmed that Amazon is trying to lock down the preloader to stifle us. I've been saying this for a while now, but it is now almost suicidal to not do a non-Prime conversion right away. As for you, I would recommend sending the phone back and getting another one. I don't know about BLU or Amazon RMA policy on this, but I'm sure it is fair game (even after the 30 day period) since your phone was bricked by Amazon's retarded update.
[BLU R1 HD Guides, News, & Discussion] emc2cube:
I think so, but I could be mistaken:

assert(package_extract_file("preloader_p6601.bin", "/tmp/preloader_p6601.bin"),
write_raw_image("/tmp/preloader_p6601.bin", "/dev/block/mmcblk0boot0"),

And yes, I will wait a few days to see if someone smart come with a solution (or to drain the battery and try again in case it's stuck on while the screen is black) and then exchange it.
[BLU R1 HD Guides, News, & Discussion] DarkBlood.:
You can send the command "FASTBOOT" over usb to try to boot into fastboot mode
[BLU R1 HD Guides, News, & Discussion] Javiefs:
Yes, only minor update and security

Enviado desde mi R1 HD mediante Tapatalk
[BLU R1 HD Guides, News, & Discussion] :
Yep, that replaces the bootloader alright. That's really ****ty. I was hoping that was impossible (SPFT and Android wouldn't let me replace it whenever I tried)
[BLU R1 HD Guides, News, & Discussion] DarkBlood.:
While looking through the fastboot sources i found 2 interesting thing

MTK_USB2JTAG_SUPPORT - oem ap jtag

MTK_JTAG_SWITCH_SUPPORT - oem usb2jtag

Install Sig - install sig
[BLU R1 HD Guides, News, & Discussion] :
Yeah, a minor update that replaces the bootloader and probably stifles any chance of getting root again. DO NOT INSTALL V6.6!
[BLU R1 HD Guides, News, & Discussion] ariesgodofwar:
To facilitate reflashing of the inevitable bricked devices incoming which just bootlooped as a result of their OTA package?
[BLU R1 HD Guides, News, & Discussion] DarkBlood.:
I haven't looked into the commands, now I am trying to find the uart baudrate

Log baudrate 921600, 12000000 or 13500000

Meta baudrate??

---------- Post added at 07:17 PM ---------- Previous post was at 07:10 PM ----------

Should I make a list of all the fastboot commands?

---------- Post added at 07:52 PM ---------- Previous post was at 07:43 PM ----------

Fastboot commands

oem usb2jtag

oem ap_jtag

getvar

signature

flash

erase

continue

reboot

reboot-bootloader

download

oem p2u

oem reboot-recovery

oem append-cmdline

oem off-mode-charge

oem auto-ADB

oem unlock

oem lock

oem key

oem lks

boot

flashing unlock - same as oem unlock

flashing lock - same as oem lock

flashing get_unlock_ability
[BLU R1 HD Guides, News, & Discussion] RainofOranges:
No, I am on 6.6 and am rooted.
[BLU R1 HD Guides, News, & Discussion] :
How did you do it? Was the altered preloader not a problem for SPFT?
[BLU R1 HD Guides, News, & Discussion] RainofOranges:
SPFT still works fine with the preloader update. I flashed TWRP and then flashed SuperSU in it.
[BLU R1 HD Guides, News, & Discussion] :
Good, that's a relief, but I still want to caution people to be careful. I would like to know what is actually in that preloader update, which I unfortunately don't think we'll ever know. How about fastboot? Relocking that bootloader or worse, making it ignore the unlock status is still a valid concern. I'm glad that SPFT works and we can still boot unsigned images, but I still won't be taking the update until we learn more.
[BLU R1 HD Guides, News, & Discussion] RainofOranges:
Fastboot can still flash recoveries as well. But you're right about wanting to know why they had to update the preloader, I would also like to know. Luckily nothing bad has come from this update, however that can't be guaranteed for future updates knowing an OTA can update the bootloader and preloader. I've disabled OTAs on my phone, and I'll be looking through each OTA before updating.
[BLU R1 HD Guides, News, & Discussion] yaconsult:
These reports indicating that they may be moving to secure the phone more have encouraged me to order a backup phone now, rather than waiting and getting a phone that already has undesired updates that might keep me from flashing and rooting.

If I were to drop the phone and break the screen, I couldn't repair it for $60 so it's worth buying a backup to me. I've been very pleased with the phone's performance. I wish it had a better speaker, but $60!

But remember that you are only allowed to buy one of each model of prime phone per prime account. I had a friend order the first one on his prime account and so I just ordered the second on my account.
[BLU R1 HD Guides, News, & Discussion] emc2cube:
I will disagree on this one ;)
[BLU R1 HD Guides, News, & Discussion] RainofOranges:
Your update might have been corrupted, I think. I'll keep trying to find a solution for your issue.
[BLU R1 HD Guides, News, & Discussion] RainofOranges:
I may have to take back what I said about SPFT working with the new preloader from 6.6. Two cables known to be good, both are giving me this error.

Little bit of research shows that 0x7D4 is an error writing to the phone. Oddly enough, fastboot flashing still works, but I can't seem to get SPFT to work. Something was done to the preloader in the 6.6 update and it wasn't good.

Edit: fastboot confirmation

This is successfully flashing lopestorm TWRP with fastboot flash
[BLU R1 HD Guides, News, & Discussion] :
That's good, but it leaves the question: What changed? The only thing I can think right now is that something is being hidden and we need to be extremely careful.
[BLU R1 HD Guides, News, & Discussion] bullet25:
Knowing Amazon ALL Future OTAs should be installed at your own risk. They are very likely to lock down the phone more.
[BLU R1 HD Guides, News, & Discussion] :
Oh no, that's no good, I guess I should have refreshed the thread before my last post. I was about to go around putting my foot in my mouth, but now it appears that I don't need to. This will be interesting.
[BLU R1 HD Guides, News, & Discussion] DarkBlood.:
Flash the old preloader through fastboot
[BLU R1 HD Guides, News, & Discussion] RainofOranges:
Unless I'm mistaken there's no preloader file out right now. If I am mistaken then I'll gladly try that.
[BLU R1 HD Guides, News, & Discussion] DarkBlood.:
I will see the sources and tell you
[BLU R1 HD Guides, News, & Discussion] :
There is not, and you should not flash the preloader at fastboot. I can get you a preloader and instructions for flashing it, but you have to promise me that you won't hold a grudge if it bricks your phone.
[BLU R1 HD Guides, News, & Discussion] DarkBlood.:
Flashing the preloader through fastboot is not permitted

("flash preloader is not permitted.");
[BLU R1 HD Guides, News, & Discussion] :
Duh, you have to do it through Android.
[BLU R1 HD Guides, News, & Discussion] DarkBlood.:
Yes that will work with dd

---------- Post added at 12:09 AM ---------- Previous post was at 12:03 AM ----------

Mediatek made it so easy on them they change 1 variable from true to false and spflashtool is disabled:(
[BLU R1 HD Guides, News, & Discussion] RainofOranges:
I'd be willing to try, but if it does brick my phone then there's no recovering from that, is there?
[BLU R1 HD Guides, News, & Discussion] DarkBlood.:
There is on some phones
[BLU R1 HD Guides, News, & Discussion] kal250:
I knew I wasn't being paranoid, Amazon pushing out OTAs like nobody's business and OEM gets none!!! It's not about BLU only supporting flagships, it's BLU doing whatever Amazon wants them too, and BLU is not about to give up the partnership with Amazon, too many sales. We should stick with what we know is working until development is complete on some custom roms....
[BLU R1 HD Guides, News, & Discussion] DarkBlood.:
Don't worry I have flashed my preloader multiple times and i am typing from that phone at the moment

---------- Post added at 12:25 AM ---------- Previous post was at 12:25 AM ----------

Did you Bootloader get locked?
[BLU R1 HD Guides, News, & Discussion] kal250:
I dont know if it makes a difference, I have been using SPFT v5.1628(newest when phone released) there is a newer version v5.1632 now

http://spflashtools.com/windows/sp-flash-tool-v5-1632
[BLU R1 HD Guides, News, & Discussion] DarkBlood.:
Can you give me the V6.5 preloader?
[BLU R1 HD Guides, News, & Discussion] RainofOranges:
Tried again with the new version, still got the same error.
[BLU R1 HD Guides, News, & Discussion] kal250:
I knew they would eventually pull some shady BS
[BLU R1 HD Guides, News, & Discussion] DarkBlood.:
It could be the trustzone.bin
[BLU R1 HD Guides, News, & Discussion] emc2cube:
Yep that's the one I have too when trying to restore with SPFT.

Does your windows make the sounds of a peripheral being plugged/unplugged in a loop too? Mine does when I plug the phone and that's why I suspect that the preloader is corrupted, it sounds like the phone is booting and then shutting down a second later before rebooting, etc.

If someone have SPFT images for lk, preloader, trustzone or others from a previous version I can try on mine, it's already bricked anyway ;)
[BLU R1 HD Guides, News, & Discussion] DarkBlood.:
I think I know how to fix it but I will need my pc and that will happen after 1 week
[BLU R1 HD Guides, News, & Discussion] RainofOranges:
When mine was boot looping and it was plugged into my computer it made the plugged/unplugged sounds in a loop too, yes.
[BLU R1 HD Guides, News, & Discussion] DarkBlood.:
What does it appear as in the device manager
[BLU R1 HD Guides, News, & Discussion] RainofOranges:
It's not boot looping anymore so I don't know.
[BLU R1 HD Guides, News, & Discussion] DarkBlood.:
Open device manager connect it and it should appear under ports
[BLU R1 HD Guides, News, & Discussion] kal250:
I wonder how long it will be before current stock is depleted and 6.6 starts shipping?? Thinking of ordering another on a friends prime acct, but wont have funds for another week.... :rolleyes:
[BLU R1 HD Guides, News, & Discussion] :
No preloader was shipped with the 6.5 update. I can give you the 6.1 one.

---------- Post added at 09:59 PM ---------- Previous post was at 09:59 PM ----------

Don't think phones will ship with 6.6. It's possible, but I don't think it'll happen.

---------- Post added at 10:01 PM ---------- Previous post was at 09:59 PM ----------

When it's bootlooping? That's just the standard Android device connecting and disconnecting. The virtual Android USB interface is started pretty early in Zygote, so a bootlooping phone will often make the plug/unplug sound over and over again.
[BLU R1 HD Guides, News, & Discussion] DarkBlood.:
Ok v6.1 will do too
[BLU R1 HD Guides, News, & Discussion] :
I have images from 6.1. Can you get into Android or recovery in any capacity? You won't be able to flash anything if you have the SPFT error and you can't get into that. Can you get to fastboot?

---------- Post added at 10:04 PM ---------- Previous post was at 10:04 PM ----------

Doubt it.

---------- Post added at 10:07 PM ---------- Previous post was at 10:04 PM ----------

Thanks for bringing this to my attention. I have updated my mirror with the latest SP Flash Tools for Windows and Linux.

https://na.mirrors.coltondrg.com/coltondrg/r1hd/spft/
[BLU R1 HD Guides, News, & Discussion] DarkBlood.:
You can do "echo FASTBOOT > COM9" change com9 to the correct com port while the phone is booting and it will boot to fastboot
[BLU R1 HD Guides, News, & Discussion] :
No there isn't. If you're preloader is ****ed up, you're totally ****ed.

---------- Post added at 10:10 PM ---------- Previous post was at 10:09 PM ----------

No. I haven't taken the update (for obvious reasons). It doesn't appear to relock bootloaders or otherwise affect fastboot functionality, but it does break SPFT, which is very alarming.
[BLU R1 HD Guides, News, & Discussion] DarkBlood.:
fastboot signature sounds like an interesting command it allows us to add private signing keys to the lk
[BLU R1 HD Guides, News, & Discussion] kal250:
Are your uploads not complete? It shows a file size of 11k for each file?? Pretty sure thats not correct :laugh:

Update: It's fixed.