yashsingh1/xdaforums huggingface dataset:
[OnePlus 2 Q&A, Help & Troubleshooting] Dodangus:
Before I describe my issue I'll let you know I've been looking up articles on how to solve this for weeks now. first post to XDA, so bear with me I'm new :)

I have two OPT, both have a similar problem, but one is working (I dare not try to mess with it) and the other I've already tried and tried and now I'm stuck in fastboot, no recovery, no OS.

I HAD an OS on it (Paranoid Android 6.0.1), but I couldn't factory reset, and I needed to, so that I could sell the phone. when I tried to factory reset through OS settings, it would boot loop until I hard reset the phone. I had no recovery apparently (IDK how I did that) but trying to install a recovery requires the "OEM Unlocking" setting to be checked. and for some reason it won't let me check the box. My working OPT phone has the same problem, the "Allow OEM unlocking?" box pops up, I select enable, and the toggle moves itself back to the grayed out selection. so I couldn't install a custom recovery, I can't do any formatting or erasing in fastboot either without that selection for some reason either. trying to only gives me a "FAILED (remote: device is locked. cannot erase images)" or "FAILED (remote: device is locked. cannot flash images)"

AND SO, I tried this (search google for "mega unbrick guide for a hard bricked oneplus 2". I can't post links apparently as it is my first post. it will be on the oneplus website) and now I have no OS. or at least I believe I have no OS because trying boot causes a bootloop. I've tried all the methods, but I'm assuming because my bootloader is locked, It failed with the "A2001_save_brick_mini" tool.

And so, all I have right now is bootloader. didn't have a recovery I guess, and now I think I don't have an OS. and I can't do anything in fastboot because is returns with a "FAILED" hehe. dang locked bootloader. I have no idea how both of these phones have locked bootloaders anyways, because I obviously unlocked the bootloader to install a custom ROM in the first place. did the bootloader relock itself, or maybe during the process of installing the ROM, the bootloader relocked? I'm not sure as I wasn't watching for that. the phones had booted with the new OS, and so I happily went along my business and didn't find out I had a problem until I tried to factory reset one of them.

no I have no phones now with similar problems, but at different stages of the same issue.

My ONE A2005 is working, but I can't toggle the "OEM unlocking". At least it has a working custom recovery (TWRP)

and MY ONE A2003 is stuck in fastboot (fastboot recognizes it via "fastboot devices" and I can reboot and "fastboot oem device-info") with what I believe to be no recovery or OS.

ask me any questions to further explain my predicament, and PLEASE offer me any things to try. I ave two phones to test different things with. I would prefer to keep the working one working though.
[OnePlus 2 Q&A, Help & Troubleshooting] DR_HAX34:
Have you tried the fastboot oem unlock command?
[OnePlus 2 Q&A, Help & Troubleshooting] Dodangus:
Ah yes, I forgot to write that in. That also results in a "FAILED (remote: unlock device to use this command)"

I can't unlock because of the OS, or perhaps lack of OS now; And I can't install a new OS or recovery because my bootloader is locked ;)
[OnePlus 2 Q&A, Help & Troubleshooting] Gaurav Rohilla:
use qualcomm recovery tool if you can't get any help. it'll restore your phone to 100% stock
[Android Q&A, Help & Troubleshooting] ugn10:
Hi,

What are the hardware requirements for Android 6 and Android 7?

My android device SoC Model is MT6592 whose core architecture is 8xARM Cortx-A7@1664 MHz and instruction set is 32-bit ARMv7. Also its board is ht1_107a_iball_mjk.

Will it support Android 6 and Android 7?

Regards

Ugn10
[Xiaomi Mi 5 Questions & Answers] Gadgetguy2005:
Hello all,

since the new Mi5S was launched, several places dropped the price on the Mi5.

What would be your recommendation - where is the best place to get it now? (I am in Canada, would go for the 64GB version and would need DHL shipping).

Thank you for any recommendations!
[Xiaomi Mi 5 Questions & Answers] Ulver:
I got mine from ibuygou.com
[Xiaomi Mi 5 Questions & Answers] nkt09:
I bought mine at Gearbest, for 260€. (3/32GB variant)

It's at a great price, and it comes to Europe via China without customs tax.
[Xiaomi Mi 5 Questions & Answers] mrsachou:
http://www.kimovil.com/en/where-to-buy-xiaomi-mi5-32gb

Look chepeast price
[Xiaomi Mi 5 Questions & Answers] Kedas:
How does that work without import tax?
[Xiaomi Mi 5 Questions & Answers] nkt09:
They have a Priority Line for certain countries. I'm from Portugal.

I think the package will come to England and then to Spain, that way enters the EU, so there's no taxes involved.
[Xiaomi Mi 5 Questions & Answers] iMaterial:
I saw someone selling it for €208, (the 64GB version) on Amazon.de, but the day after the price was €370 so it was probably an error.
[Xiaomi Mi 5 Questions & Answers] muff99:
Its on sale at gearbest, 64gb version for 305€, no additional taxes/customs fees. Will hopefully reach me in 5-10 days.
[Xiaomi Mi 5 Questions & Answers] troublecro:
Bought mine on vopmart .

No problems whatsoever,no taxes for EU.
[Xiaomi Mi 5 Questions & Answers] Ulver:
Good luck dealing with their modified MIUI ROM.
[Xiaomi Mi 5 Questions & Answers] iMaterial:
That didn't sound too good, there's a difference?
[Xiaomi Mi 5 Questions & Answers] Ulver:
Yeah, you run the risk of getting a non-offical MIUI build. So basically, you're stuck with that ROM and you're not able to update. Check en.miui.com, there's some tutorials on there on how to get back on official builds.
[Xiaomi Mi 5 Questions & Answers] iMaterial:
It's £277 on Amazon right now.

https://www.amazon.co.uk/gp/product...4&creativeASIN=B01IMOU2RG&smid=A167EEIELTDYTC
[Xiaomi Mi 5 Questions & Answers] marcel112:
When you have ADB and usb driver installed its not that hard using fastboot.

Like the man said there are several threads at en.miui.com how to.

If you like there are also variants that have multilanguage's at https://xiaomi.eu/community/

For that to work you need to unlock the bootloader if im right...
[Xiaomi Mi 5 Questions & Answers] muff99:
My phone arrived today (11 days from china to germany, not bad actually), and it really did contain a strange non-official global MIUI version.

Most tutorials suggest flashing a MIUI dev version in order to unlock the bootloader, but this did not work with this modified MIUI. That got me worried, actually.

However, after spending a few hours with it, I found that booting into EDL mode and using MiFlash with a fastboot-version of the latest official dev MIUI version did work (afaik the only variant that works with a locked bootloader). This probably won't work in the future, I heard that newer roms do not allow the EDL mode any more ... maybe in the future you need to use a special usb cable ("deep flash").

My brand new MI5 is now cleaned off that gearbest crap, and is running an official global dev rom. I am now waiting for my unlock confirmation.

More info on deep flashing and where to ge the official fastboot roms that work with EDL mode :

http://xiaomitips.com/guide/miui-deep-flash-engineering-cable-solution-to-non-edl-device/

http://en.miui.com/a-234.html
[Xiaomi Mi 5 Questions & Answers] Ulver:
Nice! Glad you got it working like it should. This is why whenever I buy a Xiaomi device I make sure the place I'm getting it from sends me a sealed untouched phone. It's so much easier to unlock the bootloader and get on a global ROM when you're on an official build.
[Xiaomi Mi 5 Questions & Answers] spaniard:
Goldway in Aliexpress, Mi5 64GB 281€ with Global ROM, has very good support from the shop in spanish forum.
[Xiaomi Mi 5 Questions & Answers] muff99:
I wrote a not-so-good review on the mi5 on gearbest, stating that I didn't like the modified rom on my shiny new sealed phone.

They came back to me and offered a full refund if I wanted to send it back, or gearbest store credit. I took the credit, since my MI5 is happily running CM 13. I though about sending it back and ordering a MI5S for a moment ... instead I just flashed the new falcon kernel and OCed it to 2.5 GHz myself, the effect is pretty much the same ;)

In general I completely agree with you, gearbest should at least give customers the choice:

Send out modified phones for the lazy western customer with a play store ready to go and clearly state this on the webpage, or keep them untouched as one would expect it to be (what xiaomi is actually going for by locking the bootloader in the first place).
[Xiaomi Mi 5 Questions & Answers] Ulver:
I'm surprised they offered you something. I was looking at other places to buy Xiaomi devices when I was looking to buy my Redmi Note 3. Vickmall.com seems pretty decent. They actually have an option to select what ROM you want, which looks pretty cool.

I would have kept the Mi5 too. You do have more options for ROMs and will get better support.
[Xiaomi Mi 5 Questions & Answers] Jogutierrez:
Xiaomi has an online mall mi.com/en
[OnePlus 3 Questions & Answers] mr.shme:
I am the same issues as the op in the thread here https://forums.oneplus.net/threads/voice-call-echo-issue-for-person-on-other-end-of-the-call.457774/.

Basically if my op3 is in a call the person on the other end of the call hears an echo of themselves. If I put it on speaker mode then the echo goes away. Does anyone else also have this issue? I'm running Sultans CM13 currently but I had the same issue while running OOS 3.2.6.

EDIT:

Just figured out a fix. Here is what my build.prop looks like now:

persist.audio.fluence.voicerec true

persist.audio.fluence.voicecall true

persist.audio.fluence.speaker true

ro.qc.sdk.audio.fluencetype fluence

After changing those I had to bump up the volume of the mics in the mixer_paths_tasha file:

Under this path: <path name="handset-stereo-dmic-ef">

I change the mics to this:

<ctl name="ADC5 Volume" value="20" />

<ctl name="ADC5 Volume" value="20" />
[OnePlus 3 Questions & Answers] verdiken:
does it work?

Can anyone confirm this helps?

I'm rather new to editing buildprop and i know i can set it back to the old values though would like to know what im changing and why. I've been digging on google a bit on the strings and basically what i got was that it has to do with noise cancellation (fluence). The actual meaning of changing (or need for) the "voicerec" string was never really explained anywhere.

Also:

why did you put <ctl name="ADC5 Volume" value="20" /> twice? its only on time in the file?

Did you mean another like "...DEC5..." (f.e.) as the second one?

greetz Ken
[Verizon Motorola Droid Turbo General] cure25:
Guys Motorola just released list of devices that will be officially supported for Android 7.0.Unfortunately Moto Turbo did not make into that list.Now i see no chances in future too Although Droid Turbo 2 made into that list
[Verizon Motorola Droid Turbo General] Septfox:
The Droid Turbo is still waiting on Marshmallow, let alone Nougat. Its international model, the Maxx, didn't even get MM until earlier this year. We'll probably be lucky if we get official MM at all.

Speaking of which, the Maxx isn't on the list either, which doesn't bode well. Probably going to have to wait and hope someone builds CM14 for our phone, if you want Nougat.
[Verizon Motorola Droid Turbo General] ChazzMatt:
CM14 (Nougat) will come for Quark

You are referring to this updated Nougat device list from Motorola:

http://motorola-blog.blogspot.co.uk/2016/10/n-is-for-nougat-android-70-is-coming-to.html

There was an earlier list 3 months ago, with more devices to be added at a "later date". Yeah, no Quark phones made the updated list.

Of course, the Droid Turbo XT1254 made the Motorola "Marshmallow" list back on October 2, 2015 but Verizon deigned not release it to Droid Turbo owners (yet or maybe ever).

That someone is our CM dev [MENTION=2228410]Skrilax_CZ[/MENTION], and he has already committed to that.

Quark got Lollipop before Motorola gave it to us (March 2014 vs April 2015), Marshmallow before Motorola gave it to us (February 2016 vs July 2016) and will get Nougat. He's just waiting until nightlies for any CM14 ROM starts rolling out.

20th September 2016, 12:34 AM

Then, after Quark CM14 -- especially the kernel work -- other ROMs can build on that framework. We have

7 custom Marshmallow ROMs for the Quark

(maybe 8 depending on how you count) -- they work on ALL Quarks, thanks to our CM dev. '

No reason we won't have just as many Nougat based ROMs. ;)
[Verizon Motorola Droid Turbo General] TheSt33v:
Here's hoping that CM14 fixes the signal issues of CM13
[Verizon Motorola Droid Turbo General] a_cipher:
I unlocked my bootloader (SU4TL-49) but now puzzled if I should wait for CM14 or install CM13 now...

I am new to installing a custom ROM and don't know if it is worth the time to install a soon-to-be outdated ROM.

Also, if the recommendation will be to still install now, which ROM to get. Just sick of Verizon and Motorola crap.

:confused:

Thanks
[Verizon Motorola Droid Turbo General] ChazzMatt:
Install now. CM13 (Marshmallow) was in "beta"/preview the first month. (And that "first month" for CM14 Quark ROM may not be until November.) Whereas CM12.1 (Lollipop) was rock solid. I didn't switch to a Marshmallow ROM for awhile, from CM12.1.

Go with the stable ROM (CM13) or other Marshmallow ROM for now. You can always change by end of the year.

You may even like Marshmallow Bliss or Resurrection Remix ROMs better than CM13. They seem to be the two most popular right now.
[Verizon Motorola Droid Turbo General] mrkhigh:
Edit: changed a word with a synonym so it would be understood without a negative connotation:

I'm typically a cyanogenmod fan and I used cm on this device since it was stable until a few weeks ago.

I'm currently rocking marshmallow Nexus experience rom, but before I go back to cm13 I'm going to try mokee.

Resurrection remix and bliss are filled with features. This is NOT a bad thing it is just features I hold little interest in and I keep finding myself just going back to cm.

Nexus experience doesn't screen cast right. Other than that it works great.

Cm13 doesn't pass Android pay or Pokemon go security checks. Rooting is NOT enough. So if you use either app my recommendation is Resurrection remix, Nexus experience or stock brazil marshmallow without volte

ALL Roms other than stock lollipop based Roms do NOT support volte (data during phone calls)
[Verizon Motorola Droid Turbo General] a_cipher:
ChazzMatt and mrkhigh,

I can't thank you enough for quick and detailed responses!

Sounds great, I'll do some more reading on those roms and decide which one to get.

Thanks!
[Verizon Motorola Droid Turbo General] NepoRood:
Bliss isn't "bloated", it has the smallest footprint of any ROM I've built or used. And it reboots in under 30 seconds, my Keurig isn't that fast. [MENTION=5747496]bhb27[/MENTION] is constantly working on RR, and it's the most popular/downloaded ROM we have, no doubt about it.

VoLTE is something you have to sacrifice in order to use a custom ROM. bhb is trying to fix that too, but unfortunately, he lives in Brazil and is not a VZW customer.

I know that you know what you're talking about (been around long enough to see that), but to say Bliss is "bloated"...
[Verizon Motorola Droid Turbo General] mrkhigh:
My apologies. You took it wrong... I said it was bloated with features.... Meaning lots and lots of features.

They are features I don't use. So for me they are by definition 'bloat' but i did then say that's not a bad thing.

Probably a poor choice of words since it is often used negatively. Kinda like the word ignorant sounds bad but it would be completely correct to say "I'm ignorant in Pascal coding."

Bliss is an amazing rom. Just like cm rr and mokee.

---------- Post added at 12:47 PM ---------- Previous post was at 12:41 PM ----------

Edited statement above so nobody else would mistake what I was trying to say. It now reads filled
[Verizon Motorola Droid Turbo General] NepoRood:
Words are funny like that, yes? Everyone has their own opinion when it comes to a custom ROM (good thing we have many to choose from, lol), I just misinterpreted your meaning of "bloat", so: My apologies to you as well :highfive:
[Verizon Motorola Droid Turbo General] kingersj1:
I've been considering leaving CM13 do I can use Android Pay and Pokemon Go(my son loves to play) which ROM do you recommend, Nexus experience or Brazilian stock? Which one is less hassle to get those apps working?
[Verizon Motorola Droid Turbo General] TheSt33v:
Neither. If you want those things, you'll need to install the latest official Motorola release for your Droid Turbo, and nothing else. The latest update to SafetyNet broke the workarounds that were used in CM-based ROMS (Brazilian stock never passed SafetyNet at all, even without root or xposed installed). I think suhide might still work, but only on a stock marshmallow ROM that passes SafetyNet, and we don't have that.

EDIT: Never mind. I might be wrong about all of that. Check out Resurrection Remix. The dev has added a companion app called iSu that works as of 3 days ago for hiding root (stock CM root, do not install SuperSU), and apparently it passes safetynet.
[Verizon Motorola Droid Turbo General] monsterlucifer:
JFYKI, I haven't tried out Bliss yet but I noticed that ROM size is 330mb for Bliss while RR is 273mb. I am quite satisfied with latest version of RR on XT1254.
[Verizon Motorola Droid Turbo General] TheSt33v:
The size of the system partition, if I'm not mistaken and assuming you have not manually resized it, is about 3 GB. So I'm pretty sure neither Bliss nor RR is going to fill that up anytime soon. But if you can somehow fill up that partition with mods that need over 10 times the space of the base OS, you are my hero.
[Verizon Motorola Droid Turbo General] monsterlucifer:
The system partition is 1.94gb and I haven't ever resized the partition. With stock based ROMs, I was struggling with space on system partition. You're correct that with almost everything installed that I need, there's still 500+mb available.
[Verizon Motorola Droid Turbo General] mrkhigh:
RR is your best bet. Use the iSU app and you can "keep" root

I'm currently using it due to that exact reason.

With nexus you'll have to simply "unroot" I left that ROM because face book kept locking up?!

And I would ASSUME the Brazil ROM would work out of the box since I do not believe it includes root.
[Verizon Motorola Droid Turbo General] mrkhigh:
Resurrection remix works just fine
[Verizon Motorola Droid Turbo General] mrkhigh:
Fwiw I think Brazil ROM no root would be a great choice as well. Nexus was buggy with Facebook for some reason but unrooted it passed safety net

Cm13 will NOT pass even unrooted. No idea why.
[Verizon Motorola Droid Turbo General] monsterlucifer:
Brazilian does not play nice with Xposed...
[Verizon Motorola Droid Turbo General] mrkhigh:
Odd.

Stock lollipop played nice.

But he probably didn't want xposed if he wants safety net compatibility.
[Verizon Motorola Droid Turbo General] TheSt33v:
The Brazil rom does not pass safetynet out of the box on an XT1254. I tested it myself. I even tested the unmodified Indian firmware that was graciously supplied by [MENTION=7109882]iiWoodstocK[/MENTION]. I suspect this has something to do with the modification of build.prop that occurs during the installation of the BHB kernel that is required to make it boot on an XT1254 (and, in the case of the Brazil rom, the build.prop modifications made by [MENTION=7109882]iiWoodstocK[/MENTION] to make it work on the XT1254). As far as I know, this modification is not necessary when you install it on a CM-based rom, which is why it doesn't break safetynet on those roms. Modded build.prop is one of the first things that safetynet checks.

As for why CM13 doesn't pass, I think that's because it has root built in, and even when it is disabled by the user, it is not hidden sufficiently for safetynet to miss it. BHB got around this in his CM-based rom using his iSu app and custom kernel.
[Verizon Motorola Droid Turbo General] TheSt33v:
Orly? My terminal disagrees.
[Verizon Motorola Droid Turbo General] iiWoodstocK:
Well, actually I suspect it might be due to how I made the ROM. Because the unmodified Indian ROM didn't have any build.prop edits. Unfortunately this is something out of my control. It also might be due to bhb27 kernel, dinner that is required in order for the ROM to work.
[Verizon Motorola Droid Turbo General] TheSt33v:
Well if I'm not mistaken, part of how you made the Brazil rom work was edit the build.prop, right? That's a safetynet disqualifier right there. And even if you didn't, if you pay attention to the install log when you flash BHB's kernel, you'll notice that it adds a line to build.prop. So even if the build.prop is unmodified (like the Indian rom), it gets modified when you flash the kernel.

I'm not saying that that's the only reason why it fails safetynet, but I do know that modded build.prop = instafail
[Verizon Motorola Droid Turbo General] iiWoodstocK:
OOOOOOHHH tru. Yea I did modify the build.prop on the Brazilian ROM to make it work, but I forgot the newer versions of bhb27 kernel also mod the build.prop

Wait, but didn't you test the Indian ROM with the old kernel too? Or am I remembering wrong...
[Verizon Motorola Droid Turbo General] TheSt33v:
I did. I just assumed that the older versions also modded build.prop. If that's not the case, maybe it has to do with a kernel/rom/device mismatch.
[Verizon Motorola Droid Turbo General] iiWoodstocK:
v2.0.0-8 (the one I recommended in the OP of my thread) is prior to the kernel also tweaking the build.prop
[Verizon Motorola Droid Turbo General] TheSt33v:
Ah okay. Well then the failure is not the fault of build.prop mods. I'm not sure what it is then, but it definitely still fails with that version.
[Verizon Motorola Droid Turbo General] mrkhigh:
You can replace cm13 root with SuperSU, then full unroot.

This makes it an unrooted ROM

It still doesn't work.

Unimportant though...

I had read before cm alone breaks safety net.

No idea if that is true, but it seems true.

Odd to me other cm based roms work.
[Verizon Motorola Droid Turbo General] TheSt33v:
If you remove the built in root, you are probably heavily modifying the system partition. Since safetynet compares the system partition to some sort of fingerprint of what it's supposed to be (no idea how that works), it makes sense that the absence of something that is "stock" to CM would cause it to fail. I've never understood why some CM roms pass though.
[Verizon Motorola Droid Turbo General] mrkhigh:
No idea

nexus experience works very similar

You can turn on and off root. It's based off of cm code

So it's probably the same method.

Fwiw: RR is iffy sometimes with turning off root.

Took a few reboots for safety net to pass using iSU.

Not sure why on that either.
[Verizon Motorola Droid Turbo General] mrkhigh:
safety net updated

You have your choice of lollipop stock right now I guess...
[Verizon Motorola Droid Turbo General] fmz0507:
I thought so too, but it turns out you only need to turn on selinux to get it to work again :) cheers
[Verizon Motorola Droid Turbo General] ChinaLiJun:
Thank you very much, ROM will support XT1254 products
[Verizon Motorola Droid Turbo General] monsterlucifer:
Makes me very happy to see this :D
[Verizon Motorola Droid Turbo General] ChinaLiJun:
Where can I download? ROM
[Verizon Motorola Droid Turbo General] monsterlucifer:
It's not available yet and [MENTION=3250376]ChazzMatt[/MENTION] already indicated ETA to be December.
[Verizon Motorola Droid Turbo General] ChazzMatt:
The Resurrection Remix Quak dev [MENTION=5747496]bhb27[/MENTION] is working on it. He apparently has a version that will at least boot. That link I in my post above has more screenshots he provided. I just used the most important one, showing the Android version. ;)

He said "Christmas", which is roughly a two-month ETA -- from October 27 - December 25.

It may come before then. Just don't pester him before December 25.