yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T Guides, News, & Discussion] farscape1a:
I'm using the latest Blu also. I tried official TWRP, but that ended very poorly. It borked my PIN for recovery and I couldn't get in at all. I had to boot into fastboot and flash Blu from there. Then it let me back in and I reflashed OB22.
[OnePlus 3T Guides, News, & Discussion] farscape1a:
Well, I got rid of the issue for now. It's moreso a bandaid rather than a real "fix". I wiped the ENTIRE phone and decrypted the data partition. It booted fine now after flashing OB25. I don't like this solution and that's why I call it a bandaid. I'm not sure how we're the only 2 having this issue considering the phone's user base. If you decide to take this route also and after you decrypt the phone, you have to change the filesystem to EXT4 from F2FS. I didn't do that the first time and had to wipe again when I did the conversion. With F2FS, you only see 32 gig worth of storage. After converting to EXT4, it's all there.

Good luck!!! :good::fingers-crossed:
[OnePlus 3T Guides, News, & Discussion] thx84:
Have you noticed better performance with Bluetooth? I have the 128GB so I think this will be a weekend project
[OnePlus 3T Guides, News, & Discussion] fossean:
I had the same issue after flashing the later firmwares; I'm on OP3T running Nitrogen rom. I fixed it quite easily using the method detailed here https://is.gd/QF9Pts

You need to boot into TWRP and use the file manager to delete the various files storing pin details etc. in /data/system. (I'm using the latest Blu-Spark TWRP, 8.61, FWIW)

Saves a lot of time not having to reinstall :)

I can't recall for certain, but I'm pretty sure I also needed to revert to an earlier firmware. Hope this helps.
[OnePlus 3T Guides, News, & Discussion] farscape1a:
Everything should be faster and more responsive with the device decrypted (which it is, both). The reason is because with an encrypted device, the files needed by the system are first decrypted on the fly, stored in RAM while being used, and then encrypted again for storage. All of this takes system resources. With a decrypted device, all of that overhead isn't there.

I was looking for this everywhere! What I think I'm going to try this weekend (I'm going to backup again, first) is remove my PIN lock completely, then try to encrypt the phone again. If s**t goes sideways again, I'll crack open this link on a laptop and see if I can make it happen. If not, I guess I'm doing a full wipe again. Lol

I appreciate the link!!! :good:
[OnePlus 3T Guides, News, & Discussion] nicklefloss:
Yes you will have to reinstall the firmware
[OnePlus 3T Guides, News, & Discussion] casual_kikoo:
Firmware resides in a separate partition, independent of /system, so no, formatting /system won't lead to a firmware reflash.
[OnePlus 3T Guides, News, & Discussion] OSheden:
Some folks reply because they have the answer and others because they think they have the answer ;)
[OnePlus 3T Guides, News, & Discussion] nicklefloss:
I don't know exactly what his phone is doing, the best thing to do is to look at your partitions and make sure they are still there (with your firmware).

I have erased my partitions before and formatted my drive, then reinstalled them on my lg g2 before. It's a terrible pain.

If you have windows, what happens when you plug the device to the PC. Do you get a bunch of different drives saying they are ready and available for you to do something with them like drive c,d,e,f etc. If that happens you may have to reinstall firmware.
[OnePlus 3T Guides, News, & Discussion] OSheden:
It seems that you confuse firmwares and drivers.

BTW not a single issue on Manjaro Linux since I'm on Android.
[OnePlus 3T Guides, News, & Discussion] casual_kikoo:
You are mixing stuff.

When you see a bunch of partitions when connecting your phone to your Windows computer, your phone is probably in qhsusb_bulk mode. To get into this mode, you have to want to go into this mode.

So yeah, nothing to do in this thread.
[OnePlus 3T Guides, News, & Discussion] thomasnsr:
i have the same problem like you while trying to upgrade firmware from OB22 to OB23. Some post mentioned that update firmware should better be done by flashing the complete firmware (1.59gb or so). Personally I have not try that yet. But this could be a good way to avoid similar problem like this. I am about to try this way in a few weeks and report back. Thanks for bring up this issue.
[OnePlus 3T Guides, News, & Discussion] farscape1a:
That's actually when my problem started. I flashed OB23 and it all started to fall apart. I tried to flash the entire ~1.6 gig zip of OB25 also (latest BluSpark recovery), but it said there was no OS installed when I went to reboot. I ended up decrypting the whole phone and started from scratch (back up EVERYTHING first). I flashed OB25 a couple of times rebooting in-between, all is okay now. What I'm going to try next is disabling my pin/finger print lock, restarting in recovery, making sure all of the password files are gone, and then trying to re-encrypt from there. If that doesn't work, I'm just going to buy a 5T and move on. I've never had headaches like this with any phone in my past. It's starting to really piss me off...
[OnePlus 3T Guides, News, & Discussion] thomasnsr:
sadly to hear that, however oneplus pulled off the update of OB25 few weeks ago. Perhaps you can make sure if you are using the latest version. I am going to flash it soon after i finish some important tasks here. Good luck
[OnePlus 3T Guides, News, & Discussion] danmaman:
Has anyone the ob26 firmware. Zip flashable

Thanks
[OnePlus 3T Guides, News, & Discussion] arpit_nnd:
Waiting for the same.
[OnePlus 3T Guides, News, & Discussion] kamilmirza:
thread updated with Open Beta 26 (25th April 2018)

Open Beta 26
[OnePlus 3T Guides, News, & Discussion] farscape1a:
Okay. I finally found a few minutes to back up my phone again and try to re-encrypt. I disabled my PIN screen lock, went into recovery, deleted all of the PIN/password screen lock files, rebooted, re-encrypted, rebooted, re-entered my PIN/fingerprint, rebooted again, and all is well. I just rebooted again before posting this message and everything is fine. Maybe just deleting the screen lock files next time will do the trick and I won't have to go through that rigamarole. Lol :p

Edit: I just flashed OB26 and everything is 100%. Looks like it's all good. :good:
[OnePlus 3T Guides, News, & Discussion] jamescable:
All right so what would happen if I mix the radio/modem update from Oreo, with the firmware from nougat for a nougat ROM? I mean on pixel/nexus devices, you can flash any radio/modem of your choice on any android version with no issues, but I'm assuming as long as the firmware is correct it wouldn't matter for 3t?
[OnePlus 3T Guides, News, & Discussion] Sam Nakamura:
I would be careful with this, in our case not only the modem/radios are included in the firmware packages but potentially also stuff like the bootloader (bootloader is a standalone file on nexus / pixel devices, unlike the OP3), it's also important to understand that in regards to firmware "newer isn't necessarily better", to get the best user experience firmware and ROM should match, so check the ROM's OP for firmware suggestions if it's not ready included...
[OnePlus 3T Guides, News, & Discussion] kamilmirza:
thread updated with Open Beta 27 (15th May 2018)

Open Beta 27
[OnePlus 3T Guides, News, & Discussion] anshu4590:
I just flashed this rom. I m not getting VOLTE.

Correct me if i m wrong, I first flashed OB25 Firmware then this rom on it. But still i m not getting volte. Any solutions?
[OnePlus 3T Guides, News, & Discussion] Bearthquake:
... This isn't a ROM... Maybe read the thread title next time.

If you're on a different ROM, search in that thread instead.
[OnePlus 3T Guides, News, & Discussion] Sharfuddin Ahmed:
Did you find any fix Bro?
[OnePlus 3T Guides, News, & Discussion] anshu4590:
Yes buddy. It worked. Actually it was already working, its just VOLTE is not written on the status bar. That's why i thought VOLTE isn't working.
[OnePlus 3T Guides, News, & Discussion] pietrushnic:
I just tried Open Beta 27 and it looks like my OnePlus is bricked after flashing. No reaction to power buttons anything else.

What I did was:

1. Put zip file on /sdcard/

2. Go to TWRP

3. Install zip

4. Reboot

Any idea how to recover from that state? adb of course doesn't show the device.

EDIT: I tried recovery procedure and stucked on either Sahara error, either claims that my device is not OnePlus3T but OnePlus3. I will continue discussion on unbrick thread and if recover will try oldest firmware+modem.
[OnePlus 3T Guides, News, & Discussion] husainkm:
Did u try to long press power button shut it down nd den boot it up again... It should solve ur prob
[OnePlus 3T Guides, News, & Discussion] pietrushnic:
Yes, tried it many times. Long press for over 40s, then press volume up and connect to PC at this point device manager detects device, but MSM recovery application throws error. After trying many times I decided to use different MSM for OnePlus3 this makes phone bootable (I can enter menu and use fastboot), but without interaction it stay in boot loop, screen colors are also weird. I'm not sure if at this point I can utilize fast boot somehow.
[OnePlus 3T Guides, News, & Discussion] Doc Sniper:
Do you have the right recovery thread and software for the 3T ?

https://xdaforums.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306

And look for the edited XML files, then the DATA partition will not be deleted during recovery.

Edit: There seems to be a second unbrick page: https://xdaforums.com/oneplus-3t/how-to/unbrick-tool-3t-unbrick-data-babloo-t3737791
[OnePlus 3T Guides, News, & Discussion] pietrushnic:
No, I used this thread which was mentioned in the second post.

Let me try the procedure that you mentioned and I will get back to you.
[OnePlus 3T Guides, News, & Discussion] Doc Sniper:
Seems to be the same tool on both pages.

I used it twice and it worked well for my 3T.

Hope you succeed with your phone.
[OnePlus 3T Guides, News, & Discussion] pietrushnic:
I will continoue debugging here as unbricking topic is much more suitable. If I will recover device then I will post information about modem update.
[OnePlus 3T Guides, News, & Discussion] Doc Sniper:
Do you have a 3 or a 3T ?

You need different firmware and another unbrick tool for the two phones.

The two threads from above are only for the 3T !!
[OnePlus 3T Guides, News, & Discussion] pietrushnic:
I have A3003 which is 3T. Despite that my phone is identified by this MSM software incorrectly.
[OnePlus 3T Guides, News, & Discussion] Sam Nakamura:
A3003 could be both actually, model numbers are confusing on our devices, check out the screenshot, it's unfortunately not possible to tell if 3 or 3t from the model number alone...

Did I understand you correctly that this firmware despite being for your model bricked the device?
[OnePlus 3T Guides, News, & Discussion] pietrushnic:
That's surprising. Yes, this firmware bricked my device. I'm at the stage in which I can reach fastboot mode (this is after unbricking procedure that match OnePlus3), but platform behave weird (colors, brightness and inifinite loop).

---------- Post added at 09:32 PM ---------- Previous post was at 09:28 PM ----------

Ok, things start to look clearer. I get that phone as gift so didn't figure out this before, but I found box in which I get it and looks like I have OnePlus3 not OnePlus3T. That explains my problems and why recovery procedure for OnePlus3 partially worked. Any suggestions how to fix my mistake? Or I just should follow unbrick procedure for OnePlus3 and see what will happen?
[OnePlus 3T Guides, News, & Discussion] yannmrt:
For me OB27 working well.
[OnePlus 3T Guides, News, & Discussion] Uqbar:
I'd use the 1+3 unbricking procedure. If that's a 3, use the 3. If that's a 3T, than use the 3T.

The unbricking relies on

almost-bare-metal

.
[OnePlus 3T Guides, News, & Discussion] pietrushnic:
I managed to unbrick using OP3 procedure, but now have recent Oxygen Open Beta, which encrypted my drive and cannot install Lineage. I know there is the guide about that and will follow that, but have to say that Android modder life is hard :)
[OnePlus 3T Guides, News, & Discussion] Uqbar:
I also made a similar mistake long ago. Now I triple-check any file I flash. And, most important thing, I make sure I know exactly which device I am flashing to.

Glad to see you exiting from the tunnel, though.
[OnePlus 3T Guides, News, & Discussion] Sam Nakamura:
Usually the installer script should prevent you from flashing wrong firmware... :confused: it should detect your phone model and deny flashing

LineageOS works definitely on encrypted devices, that's pretty sure not the problem... Did you unlock the bootloader again? Cause the unbrick tool will automatically re-lock the bootloader
[OnePlus 3T Guides, News, & Discussion] Doc Sniper:
This safeguarding line in the original installer script is unfortunately always deleted in the firmware installers of this thread. This is how such accidents can happen. :silly:
[OnePlus 3T Guides, News, & Discussion] Sam Nakamura:
I usually prefer to backup via TWRP and clean flash full OOS for firmware, then I restore my backup, all in one session without booting OOS, takes 10 minutes longer but it is a safe thing...

The convenience of those flashable "firmware only packages" will probably never be risk free but maybe it's a good idea to incorporate this helpful line to the script that pulls the firmware and creates those packages, do you think this could be possible without too much of a hassle [MENTION=4369704]kamilmirza[/MENTION]?
[OnePlus 3T Guides, News, & Discussion] kamilmirza:
the safeguarding line is useless on unified ROM builds, because it gets values from getprop and unified ROM builds show OnePlus3 not 3T

its useful for OOS only
[OnePlus 3T Guides, News, & Discussion] Bearthquake:
No development background, but I have noticed that my device name by default in most ROMs is oneplus3, not 3T. Makes sense
[OnePlus 3T Guides, News, & Discussion] Doc Sniper:
You are right for the device model in unified ROMs, yes.

But sorry that's not true for the safeguarding line, because the line doesn't check the device, instead it checks (edit) whatever in the device (/edit) and that's different for the 3 and the 3T.

You can simply check this by executing getprop at the command line of TWRP.

Here a screenshot from my 3T (OS is newest LOS 15.1 + MicroG - without GApps):
[OnePlus 3T Guides, News, & Discussion] Sam Nakamura:
Are you sure about this?

I remember from the dci-p3 modding days that most (or all) 3's have a A3 Samsung display while 3t's (especially the early batches) have A3 but mostly A5 displays (which were used for the OP5 too), this means the method described by you would frequently generate false positive results...
[OnePlus 3T Guides, News, & Discussion] Doc Sniper:
I'm unsure if I'm right about this, but look at the screenshot in my post.

I have a 3T with A3 display and getprop("ro.display.series") says I have a 3T ?!

Edit: I guess with display (command is: getprop("ro.display.series") ) they mean "show" and not the screen ?!? ... but all these properties seem to be set by the recovery and are not taken from the ROM in system partition, because what should the recovery show when this information would be taken from an empty system partition ?
[OnePlus 3T Guides, News, & Discussion] kamilmirza:
*sigh*

getprop will vary from ROM to ROM

here's mine on Xtended

and i do have the latter display
[OnePlus 3T Guides, News, & Discussion] Doc Sniper:
*sigh* too - ask yourself, do you flash the firmware from your booted ROM ?

Use getprop at the TWRP shell please.

I'm short on time for the next few hours, but I will post a detailed TWRP source code analysis later.

I saw at the TWRP source that all these properties are set by TWRP, not the ROM.

So the line is working and shouldn't be deleted, later more.

---------------------------------------------------------------------

Here the promised details.

As said before, these values are set in TWRP, see below:

OnePlus 3 - China / North America model
property_set "ro.product.model" "ONEPLUS A3000"
property_set "ro.build.product" "OnePlus3"
property_set "ro.product.device" "OnePlus3"
property_set "ro.vendor.product.device" "OnePlus3"
property_set "ro.display.series" "OnePlus 3"

OnePlus 3 - Europe / Asia model
property_set "ro.product.model" "ONEPLUS A3003"
property_set "ro.build.product" "OnePlus3"
property_set "ro.product.device" "OnePlus3"
property_set "ro.vendor.product.device" "OnePlus3"
property_set "ro.display.series" "OnePlus 3"

OnePlus 3T - China model
property_set "ro.product.model" "ONEPLUS A3010"
property_set "ro.build.product" "OnePlus3"
property_set "ro.product.device" "OnePlus3T"
property_set "ro.vendor.product.device" "OnePlus3T"
property_set "ro.display.series" "OnePlus 3T"

OnePlus 3T - Europe / Asia model
property_set "ro.product.model" "ONEPLUS A3003"
property_set "ro.build.product" "OnePlus3"
property_set "ro.product.device" "OnePlus3T"
property_set "ro.vendor.product.device" "OnePlus3T"
property_set "ro.display.series" "OnePlus 3T"

OnePlus 3T - North America model
property_set "ro.product.model" "ONEPLUS A3000"
property_set "ro.build.product" "OnePlus3"
property_set "ro.product.device" "OnePlus3T"
property_set "ro.vendor.product.device" "OnePlus3T"
property_set "ro.display.series" "OnePlus 3T"

Above in the CODE section, the ro.build.product entry of every 3 or 3T is simply set to OnePlus3 as some of you wrote before already.

But the ro.display.series value is set to OnePlus 3 or OnePlus 3T correctly, so the safeguard entry makes sense and prevents bricked devices:

getprop("ro.display.series") == "OnePlus 3T" || abort("E3004: This package is for \"OnePlus 3T\" devices; this is a \"" + getprop("ro.display.series") + "\"."

For all who want so take a look a the TWRP source: https://github.com/TeamWin/android_device_oneplus_oneplus3/blob/android-8.1/init/init_oneplus3.cpp

For anyone who wants to test it:

- boot to TWRP please
- choose "Advanced"
- choose "Terminal"
- enter: getprop | grep "ro.display.series"
- or if you want a bit more information, enter: getprop | grep "OnePlus"

And post your output please - thanks.
[OnePlus 3T Guides, News, & Discussion] kamilmirza:
kudos for the in-depth details :good:

why bother if you can't even read the OP, just my 2 cents

EDIT: i reckon when i started making firmware packages with that line, it didn't flashed stating that i have 1+3 and not 1+3T

i think i should point out that i have zer0 programming skills, whatsoever, and there is always a room for improvement
[OnePlus 3T Guides, News, & Discussion] Doc Sniper:
Also thank you for the good work and the time you are investing to provide the people with the firmware ZIPs.

You're right, why do I care if people brick their phones? :D

I don't know, but it's a critical flash process and phones could end up bricked, so it should be as safe as possible.

Maybe the ro.display.series of older TWRP versions was set to 3, not 3T.

As I said, you are investing your time in providing people with these firmware files, which is great. :good:

I have experience with Linux, Bash Scripting and C ++ programming (...) and would like to help with such contributions as the safeguard.

More people should help, not just only "consume".

So don't get me wrong, all this isn't criticism, I just want to help. :angel:
[OnePlus 3T Guides, News, & Discussion] kamilmirza:
but still though, it shouldn't be this easy if one can't bother to read the OP or else face the consequences

yes, this might have been the case

certainly i'm not an expert on this matter and i'm always open to constructive criticism and feedback :highfive:

surely will try it again on the next build :fingers-crossed:
[OnePlus 3T Guides, News, & Discussion] StressFull:
[MENTION=4369704]kamilmirza[/MENTION] any chance of getting 5.0.3 firmware ?

... I should really learn how to do this ! :rolleyes:
[OnePlus 3T Guides, News, & Discussion] nahsha:
My understanding was that 5.0.3 is a gradual update from 5.0.2

Or can we go directly from 5.0.1?
[OnePlus 3T Guides, News, & Discussion] kamilmirza:
you can provide me full 5.0.3 ROM link
[OnePlus 3T Guides, News, & Discussion] pijas82:
http://otafsg.h2os.com/patch/amazon...n_28_OTA_064_all_1805171658_ec44c2132ded6.zip
[OnePlus 3T Guides, News, & Discussion] kamilmirza:
thread updated with 5.0.3 (25th May 2018)

5.0.3 - Stable

P.S I have added the safeguard line (which prevents from flashing other than 1+3T), can anyone test it on 1+3 only?

thanks to [MENTION=3288532]sniperle[/MENTION]
[OnePlus 3T Guides, News, & Discussion] nahsha:
Thanks, works great on 3t :)
[OnePlus 3T Guides, News, & Discussion] Witchaboy:
Hello. I am on Nitrogen OS version 22.05.2018.

I downloaded latest firmwares for stable and for beta.

Which one is the best? Also, where i can read about firmwares changelog?

Thanks in advance.
[OnePlus 3T Guides, News, & Discussion] Sam Nakamura:
There's no changelog necessary as it's just the firmware extracted from the official OxygenOS ROM, visit oneplus forums to read about it...

What's best for you depends on the ROM you're using or with which proprietary blobs it was built, therfore there's usually a suggestion in the OP, newest isn't necessarily the best but according to my experience it usually doesn't give issues to be on latest firmware, especially as there's no significant change anymore for the OP3/t...
[OnePlus 3T Guides, News, & Discussion] gFknQ:
[MENTION=4369704]kamilmirza[/MENTION], I'm asking directly this time :p

Cpu sticks at 0% on cool tool. I've tried multiple settings and read f.a.q. What am I missing?
[OnePlus 3T Guides, News, & Discussion] Doc Sniper:
As Sam Nakamura already wrote, there is no best, but if one uses LineageOS or a ROM based on LineageOS then it maybe makes sense to use the Open Beta firmwares because according to the links below LineageOS uses parts of the Open Beta sources.

https://review.lineageos.org/#/c/LineageOS/android_device_oneplus_oneplus3/+/209318/

https://review.lineageos.org/#/c/LineageOS/android_kernel_oneplus_msm8996/+/209913/
[OnePlus 3T Guides, News, & Discussion] kamilmirza:
it shouldn't :confused:

i can send you my settings data with Titanium Backup - HERE
[OnePlus 3T Guides, News, & Discussion] gFknQ:
Thank you so much. Glad I asked directly!
[OnePlus 3T Guides, News, & Discussion] gFknQ:
Unfortunately still get 0% no matter what. Maybe because underclock so much. Thanks for the help though. Won't worry you about it
[OnePlus 3T Guides, News, & Discussion] kamilmirza:
haven't experienced this before

maybe try any other kernel, i'm using Caesium

EDIT: you must be on SELinux Enforcing, try going Permissive
[OnePlus 3T Guides, News, & Discussion] pijas82:
I'm on last firmware stable with DU and everything fine here
[OnePlus 3T Guides, News, & Discussion] gFknQ:
You are correct sir, thank you
[OnePlus 3T Guides, News, & Discussion] Doc Sniper:
It's time for you early adapters again, new (ROM) Firmware OB28 announced :o

OxygenOS Open Beta 37 for the OnePlus 3 and 28 for the OnePlus 3T

https://forums.oneplus.com/threads/oxygenos-open-beta-37-for-the-oneplus-3-and-28-for-the-oneplus-3t.841924/
[OnePlus 3T Guides, News, & Discussion] kamilmirza:
looks like Open Beta 28 has been pulled from the official site

its was there an hour ago

LOL its back :silly:
[OnePlus 3T Guides, News, & Discussion] Doc Sniper:
Flashed the Firmware (only) some hours ago, everything working so far ...
[OnePlus 3T Guides, News, & Discussion] kamilmirza:
thread updated with Open Beta 28 (29th May 2018)

Open Beta 28
[OnePlus 3T Guides, News, & Discussion] sanketvala:
I am on stable oos 5.0.2 . Can I directly flash open beta 28?
[OnePlus 3T Guides, News, & Discussion] Sam Nakamura:
This isn't the full ROM thread, it's only the firmware (extracted from the full ROM), so please check the appropriate thread for your question, if you however meant the firmware only, then yes you can flash it over stable...
[OnePlus 3T Guides, News, & Discussion] sanketvala:
Thanks
[OnePlus 3T Guides, News, & Discussion] gFknQ:
Works fine on Bootleggers OnePlus 3t