yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] laupuy:
1. Blu_spark twrp is made by eng.stk, not jcadduono.

2. He will not answer you

3. You Flash you Play you Lose, sorry, it's life :p

4. Stay encrypt and enjoy flashing whitout any problem!
[OnePlus 3 & 3T Cross Device Development] Sam Nakamura:
Word!!! :highfive:
[OnePlus 3 & 3T Cross Device Development] pidl:
[MENTION=4877941]rohit83[/MENTION] did you solve your problem? I also cant access my data anymore, i have no clue on how to fix that.
[OnePlus 3 & 3T Cross Device Development] Sam Nakamura:
Most probably you can't fix this, that's the point where you say "good bye" to your data partition and formate it, just restore your external backup of internal storage afterwards, you have one right? Playing with decryption leads to issues sometimes, it's best to be prepared...

Good luck
[OnePlus 3 & 3T Cross Device Development] pidl:
Well, first of all i dont have one thats the problem ^^ and second, i didnt play around with decryption whatsover. I simply sideloaded the official OTA of OOS 4.5.1, and ever since i cant get it to work :/
[OnePlus 3 & 3T Cross Device Development] Simba83:
I think the OTA OOS encrypts the partition when install ingen haspen to me, men since it puts its own recovery when it installs. I might be wrong but it happend to me once. Format and reinstalled worked fine since i always backup things before i crash them.

Skickat från min ONEPLUS A3003 via Tapatalk
[OnePlus 3 & 3T Cross Device Development] Sam Nakamura:
OK, it all depends on the modifications you did before flashing OOS... Hard to understand your issues without knowing what you did exactly and in what order, flashing OOS alone shouldn't be an issue, in my opinion this is even secondary because it won't solve your decryption problem, I personally never saw a solution for this other than formatting data partition...
[OnePlus 3 & 3T Cross Device Development] frittler:
Heay,

which version of the TWRP allows me to do the OTA Update to Oxygen OS 5.0?
[OnePlus 3 & 3T Cross Device Development] laupuy:
Small OTA: stock recovery

Full OTA: latest blu_spark twrp (v8.54)
[OnePlus 3 & 3T Cross Device Development] frittler:
What do you mean by "Small OTA" and "Full OTA"

I have installed a TWRP on my OnePlus 3T already and I want to know which version of the TWRP for the OnePLus 3T I need, if i just want to klick Update
[OnePlus 3 & 3T Cross Device Development] Uumas:
Flash the full ota. It's the zip that's over 1gb in size.
[OnePlus 3 & 3T Cross Device Development] laupuy:
You should search a little more...

IF you are root, OTA should be the full package zip (don't flash small/incremental OTA with TWRP, bootloop).

BUT if you clic "install", you will lose root and twrp by booting to stock kernel because stock recovery will replaces twrp (cf warning message).

SO download OTA full zip and move the file from /sdcard/.ota to /scdard and flash rom+root or rom+custom kernel (blu_spark) to keep TWRP.

;)

Edit.

And use blu_spark twrp v8.54 (latest), you will find it in blu_spark kernel thread, download tag
[OnePlus 3 & 3T Cross Device Development] frittler:
When I updated my device to 7.0, I also clicked "install" and haven't lost my TWRP.

Has anything changed?
[OnePlus 3 & 3T Cross Device Development] Sam Nakamura:
Whenever you flash a full OxygenOS version without a root package (magisk / SuperSU) which patches the stock kernel to prevent TWRP from getting overwritten or a custom kernel it's going to replace TWRP with stock recovery, not sure what and how you did what you did but that's a fact since Marshmallow but you're free to check yourself...

On the oneplus 2 (haven't checked on a 3) it was possible (in case you modified the system partition) to reflash the OOS version you were already on to get back a clean system partition, then it was possible to flash the small OOS OTAs via TWRP with no risk of bootloop or having TWRP replaced with stock recovery, so if you had a unaltered system partition (or reflashed existing OOS) and flashed the small OTA package it would result in that what was described by you (flashing update without losing TWRP) but that's the only possibility I'm aware of...
[OnePlus 3 & 3T Cross Device Development] aakarsh980131:
Worked like a charm!

This TWRP release literally saved me from bricking my phone. Kudos to the developer.:cowboy:
[OnePlus 3 & 3T Cross Device Development] tropicanapure:
Hello there,

I have 3.1.1-2 installed on the op3, but it seems the recovery is not compatible with the Oxygen OS 5.0 zip? I have been suggested (https://xdaforums.com/showthread.php?t=3710354) using an alternative version of twrp (blu_spark? Or something similar) but I am keen to wait for and use the official version.

Also, I have twrp 3.1.1-2. its just worked so far. But I noticed that the new "unified" builds are numbered 3.0.x? Which is the equivalent version number on the unified build please?

Also, having read pretty the last 25+ posts on this thread it is still unclear if the OOS 5 compatibility issue is known and a fix is in progress (I know asking for ETA is bad manners around here [emoji6]).

Thanks in advance!

{Oneplus 3/ OOS 4.5/ Magisk v14 (MagiskSu)}
[OnePlus 3 & 3T Cross Device Development] Nevermindthelabel:
Blu_Spark is not the official, but it should be. Everything just works smoothly, and it is unified.
[OnePlus 3 & 3T Cross Device Development] tropicanapure:
Link pls? Can't seem to find it via Google.

{Oneplus 3/ OOS 4.5/ Magisk v14 (MagiskSu)}
[OnePlus 3 & 3T Cross Device Development] BillGoss:
https://xdaforums.com/oneplus-3/oneplus-3--3t-cross-device-development/kernel-t3404970/
[OnePlus 3 & 3T Cross Device Development] Nevermindthelabel:
https://xdaforums.com/devdb/project/dl/?id=27381

Latest twrp there
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I'm running OOS 5.0. I installed TWRP (Blu Spark 8.54) and took a backup and then installed Blu Spark kernel r207 and took another backup. So now I had two backups: one pure stock, one with a custom kernel.

Sometime later I restored the stock system and boot (kernel) images. However the phone wouldn't reboot properly and ended up in bootloader mode.

I rebooted back into recovery and restored the system and boot images from the custom kernel backup and the phone rebooted normally.

I can also fix the problem by reflashing the OOS 5.0 installation zip.

So here's my question: why won't the phone reboot properly when I restore the system and boot images from the stock backup?

Other info: I'm not rooted, the phone is encrypted.
[OnePlus 3 & 3T Cross Device Development] Sam Nakamura:
Because you're not rooted or have a custom kernel, you just cannot boot pure stock with TWRP installed as it will trigger a safety mechanism of the stock kernel called DM-verity, there's a "no-dm-verity.zip" floating around the forums which would be the very least to flash if you plan to boot pure stock with TWRP recovery (otherwise root or custom kernel would prevent this) there're easy ways to get rid of the red dm-verity warning, just Google for the topic "dm-verity, oneplus 3"...
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Thanks Sam.

But there are a couple of things that don't make sense to me:

1. I don't get any dm-verity warnings either at initial boot or in bootloader mode.

2. Flashing the OOS 5.0 zip, which is effectively the same as restoring the 5.0 system and boot images works. Note: I've also stripped out the firmware from the 5.0 zip so it, in principle, is exactly like restoring system and boot.

Regarding the second point, I lose TWRP because the stock kernel restores the stock recovery. I was expecting the same to happen when restoring the system and boot from the backups. But that didn't happen - instead, the system failed to boot.

So I'm still unclear what's different between restoring a backup and flashing system and boot.
[OnePlus 3 & 3T Cross Device Development] Sam Nakamura:
Simple things first :)

Flashing the ROM is like setting it up new, like a fresh installment of windows, Linux, etc. while restoring means that all modifications and alterations, settings, themes and stuff are saved and restored (depending on the backed up partitions) in the condition you made the backup, in your case there shouldn't be much of a difference as you took the backup right after flashing in a clean and unaltered state but obviously it makes a big difference... That's why flashing the ROM zip works and the restoring not, seems you backed up some critical issues with your nandroid, something which prevents you from booting but I have no idea what the issue might be...

Stripping out the "firmware" cannot be compared as it's typically missing the boot & system image and contains rather the modem/radio stuff...

Yes, twrp gets lost if you flash OOS don't use root, custom kernel, or no dm-verity, which is actually good as it would otherwise trigger dm-verity...

But I got a feeling that I'm missing something here, maybe someone comes up with a good idea...
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Yes, that's how I'm feeling as well. If I was restoring data, then that's different. But just system and boot? On an unrooted phone?

Thanks for taking the time to reply. I'll play around a bit more.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Well, I think I have an answer.

The problem is caused by restoring the backup of the stock system image. And I believe that this is because restoring the system image flags it as having been modified. This triggers dm-verity (even though I get no message indicating this) and the phone won't boot but goes back to fastboot/bootloader.

Flashing the system leaves it untouched and doesn't trigger dm-verity.

As the device page on TWRP says:

"This device uses dm-verity!

This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab." https://twrp.me/oneplus/oneplus3t.html
[OnePlus 3 & 3T Cross Device Development] nicknacknuke:
i would really love to hear all your conclusion on how these system behaves...

i've stumbled upon several accidents similar like these before, with my 3 or 4 nandroid backups..lol..

also, what is the difference between system, and system images checkbox when you're trying to backup via twrp ?

thanks.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I'm now convinced that it is dm-verity that prevents dm-verity rebooting with a restored system image. The same thing happens to me if I have a modified system image, flash the stock boot image, then try to boot.

It seems to me that I'm not being presented with the dm-verity error message, just getting dumped back to bootloader/fastboot mode.

PS: the thing that really fascinates me now is that if I'm on stock OOS then I can make any changes I like to /system using TWRP and they get ignored. The phone boots up with the original copy. But if I flash TWRP again, I still see the modified version in /system. See my post https://xdaforums.com/oneplus-3t/help/2-copies-phone-t3712922/
[OnePlus 3 & 3T Cross Device Development] xpissio:
New TWRP up, 3.2.0-0.

Changelog:

-Allow restoring adb backups in the TWRP GUI (bigbiff)

-Fix gzip backup error in adb backups (bigbiff)

-Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)

-Better support for installing Android 8.0 based zips due to legacy props (nkk71)

-Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)

-Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)

-Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)

-v2 fstab support (Dees_Troy)

-Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)

-Various other minor bugfixes and tweaks
[OnePlus 3 & 3T Cross Device Development] laupuy:
Hi,

TWRP 3.2.0-0 is out

What's new in 3.2.0-0:

Allow restoring adb backups in the TWRP GUI (bigbiff)

Fix gzip backup error in adb backups (bigbiff)

Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)

Better support for installing Android 8.0 based zips due to legacy props (nkk71)

Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)

Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)

Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)

v2 fstab support (Dees_Troy)

Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)

Various other minor bugfixes and tweaks

source: https://twrp.me/site/update/2017/12/01/twrp-3.2.0-0-released.html

Download:

OP3: https://dl.twrp.me/oneplus3/

OP3T: https://dl.twrp.me/oneplus3t/

Edit.

arf, ninja'd by xpissio :D
[OnePlus 3 & 3T Cross Device Development] xpissio:
Hahah :D No problem, your post is better than mine. :p
[OnePlus 3 & 3T Cross Device Development] Spiralzz:
Can someone who's already flashed the latest (3.2.0-0) confirm that it works? I remember reading a few days ago that there were problems with the previous version...?

Thanks!
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Yes, it works. You can flash the Oreo system without any problems.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I believe there's a bug in official TWRP 3.2. It doesn't read the system's date/time and, therefore, generates timestamps for 1970.

Screenshot and logs attached.
[OnePlus 3 & 3T Cross Device Development] null0seven:
Few moments back...
[OnePlus 3 & 3T Cross Device Development] joshuous:
Hey man yes, you're right. I was doing bring up of my ROM from scratch, and I made the same observations and conclusion as you. As long as Dm-verity is working, all modifications to /system partition in recovery do not show up when booting to the actual system. We must disable Dm-verity completely in order for our changes to /system to persist beyond recovery.
[OnePlus 3 & 3T Cross Device Development] terragady:
I found out that lates twrp from blu_spark has problems with formating to f2fs but flashed 3.2 and I was able to format my data partition to f2sf
[XDA Assist] GuyInDogSuit:
Various ROMs, utilities, apps, etc. Would like to receive emails when they're updated so I don't have to check the threads every day.
[XDA Assist] :
Greetings and welcome to assist. Unfortunately assist is for guiding new members around the boards only, please ask your question here

https://xdaforums.com/showthread.php?t=1976627

all though I do think it is possible for devb threads

Thanks for understanding

Sawdoctor
[Xperia Z5 Q&A, Help & Troubleshooting] felipeacydc:
i notice this when im trying to play a game with vulkan on my xperia z5 with nougat.

does really support it?
[Xperia Z5 Q&A, Help & Troubleshooting] klemen241:
Well android 7 for z5 was recalled, so i guess is not officialy supported
[Xperia Z5 Q&A, Help & Troubleshooting] Sh4rkill3r:
Was recalled for a sound and video stutter. If not include vulkan drivers is not going to include it after fix

Enviado desde mi Sony Xperia Z5 utilizando Tapatalk
[Xperia Z5 Q&A, Help & Troubleshooting] felipeacydc:
too baaad!!!! i was very exited about testing vulkan on my Z5
[Xperia Z5 Q&A, Help & Troubleshooting] Mario.D:
Looks like z5 wont get support for vulkan api.

https://developer.qualcomm.com/software/adreno-gpu-sdk/gpu

Our gpu adreno 430 dont support that api.

Skickat från min E6653 via Tapatalk
[Xperia Z5 Q&A, Help & Troubleshooting] porshjosh:
The nexus 6p has the same gpu and supports vulkan
[Xperia Z5 Q&A, Help & Troubleshooting] Mario.D:
Yes i see that now.

Maybe qualcomm did google i special favor.

Skickat från min E6653 via Tapatalk
[Xperia Z5 Q&A, Help & Troubleshooting] felipeacydc:
it supouse that snapdragon 810 support Vulkan... am i wrong?
[Xperia Z5 Q&A, Help & Troubleshooting] :
Support Sony said that we will not have Vulkan API.

Perhaps in the future we will see support, but not the fact.

ow.ly/guHo308vgb9
[Xperia Z5 Q&A, Help & Troubleshooting] GreyLeshy:
People Adreno 430 supports Vulkan API on Nexus 6P, and this means that our smartphone also supports it. And there is firmware S. Team for HTC M9 which adds support for Vulkan.

I took out the Nexus 6P graphics driver but Vulkan doesn't work (OpenGL ES working).

Maybe someone knows how to enable support Vulkan API ?
[OnePlus 3T Themes, Apps, and Mods] Nishidh:
Features

- New accent colors in Light Theme: Wine, Navy Blue, Green (the default color in OOS 3.2.8)

- New accent colors in Dark Theme: White, Red and Lime (from OOS 3.2.8)

Instructions

1. Make nandroid before you flash this.

2. Download the zip and flash it.

3. Hit thanks and enjoy

Bugs

-While using dark theme the names of colours are not synced(Will not affect appearance)

For reporting bugs, please attach screenshots if possible

Compatibility

V7.0 for Open beta 2

Downloads

Ob2

Drive link(v7.0)

https://drive.google.com/file/d/0B6FY-XKZtgn4NmVwNjZWN2x4dkU/view?usp=drivesdk(beta)

Revert back to ob11(op3)/ob2(op3t)

https://drive.google.com/file/d/0B6FY-XKZtgn4eGFEWW52ZVVGcGs/view?usp=drivesdk(beta)

Do not get confused because ob11 on OnePlus 3 is same as ob2 on 3t

Credits

Thanks to [MENTION=4686073]ungeeked[/MENTION]

[MENTION=4970751]Rajeev[/MENTION]

[MENTION=7110443]Nishidh[/MENTION](me)

Hit the thanks button if my work helped
[OnePlus 3T Themes, Apps, and Mods] n.praveen13:
Invalid link. The file doesn't exist.
[OnePlus 3T Themes, Apps, and Mods] adanteon:
Just tested, the aroma installer is gone, which is kind of a downside, plus, it made my system settings crash every time I tried to open it..
[OnePlus 3T Themes, Apps, and Mods] MrMeeseeks:
This is for the open Beta's. I'm assuming you got it mixed up with this thread . That's why there is no aroma installer and you are getting the crashes.
[OnePlus 3T Themes, Apps, and Mods] ddaharu:
Thanks a lot for this. I'm glad that someone took the relay in this.

For those who want dark notification, the developer has no time for that. So you could try installing this substratum theme, if your rom supports it, and just theme the notification tray.

https://play.google.com/store/apps/details?id=com.r3ds.divinitytheme

(If stating this information here is breaking some rule let me know I'll remove it immediately)
[OnePlus 3T Themes, Apps, and Mods] adanteon:
Welp, seeing the same name and a superior version number got me a little confused, then... Thanks for the head up
[OnePlus 3T Themes, Apps, and Mods] MrMeeseeks:
I agree. It is confusing.
[OnePlus 3T Themes, Apps, and Mods] brmbjn:
who are success install it ?
[OnePlus 3T Themes, Apps, and Mods] :
How do you specifically theme the notification tray?
[OnePlus 3T Themes, Apps, and Mods] jotaandro:
please can you create file to work in 3.5.3 ??
[Sony Xperia M] extremetek:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

LineageOS is a free, community-built and open source distribution of Android. It's released after the CyanogenMod end of support.

Device-specific source code:

Device

Kernel

What's working/tested (by PecanCM):

RIL (Calls, SMS, Mobile Data)

Dual sim on M dual (check notes section)

Display

Camera (photos, camcorder)

Audio and video

Wifi

Bluetooth

OpenGL rendering

Sensors (accelerometer,compass,light,proximity)

Sdcard

Auto brightness

Notification led

Wifi,Bluetooth and USB tethering

NFC

GPS

Adoptable storage

Not working/untested:

Same as CM14.1

XDA:DevDB Information

LineageOS, ROM for the Sony Xperia M

Contributors

extremetek, PecanCM, FXP team and people who is working on Sony, CyanogenMod, CodeAurora Forum, CyanogenMod/Lineage

ROM OS Version: 7.x Nougat

ROM Kernel: Linux 3.4.x

ROM Firmware Required: Unlocked Bootloader

Based On: CyanogenMod

Version Information

Status: Testing

Created 2017-01-23

Last Updated 2017-01-22
[Sony Xperia M] Alvarote1998:
I have official CM14.1, can I install it without lost my data from apps, photos...?
[Sony Xperia M] e-bert:
Hi all. [MENTION=7702931]extremetek[/MENTION]: Will this be the official LineageOS thread for our device? Thanks for all your efforts.
[Sony Xperia M] rajveermalviya:
YES!!!!! Its here

Check out the official lineage os website

go to downloads of lineage os
[Sony Xperia M] e-bert:
Yes, thank you, I've seen that. But, where is the official discussion thread for these builds?
[Sony Xperia M] kh34d:
Here it is, https://xdaforums.com/showthread.php?t=3548563
[LeEco Le 2 Questions & Answers] zodiacDroid:
Can i flash s2.zip of Lineageos 7.1.1 file on indian x526?
[LeEco Le 2 Questions & Answers] Oppo_Raam:
Yes you can flash....
[LeEco Le 2 Questions & Answers] amitchhangani:
Yes you can, but there are bugs in it right now. So better at least wait for a week.
[LeEco Le 2 Questions & Answers] zodiacDroid:
I asked because developers not uploading s2ww.zips. for indian x526
[LeEco Le 2 Questions & Answers] amitchhangani:
Its a common rom for all le2 snapdragon 652 versions.
[LeEco Le 2 Questions & Answers] parthpwar:
i flashed it but sim cards are not detected
[LeEco Le 2 Questions & Answers] #sunny:
same problem i also faced, then i do clean flash and now its working both sim and volte also:good:
[Xiaomi Redmi Note 3 Questions & Answers] hyperorb:
I flashed EU GlobalDev 7.1.19 on my RN3 below

- UNofficial unlocked

- Alka Recovery

- Global Stable 8.0.6.0

Steps I followed

1) Backup data. Remove pin from current rom

2) Reboot to recovery

3) Wipe data, dalvik, cache

4) Flash EU ROM

5) Wipe data, dalvik

6) Flash SU

7) Flash Dalvik, Data

8) Reboot

It took 5 min. The rom booted fine but one issue

On boot SETTINGS force closed. I explored and found this post ( https://xdaforums.com/redmi-note-3/...dmi-note-3-t3404890/post67858903#post67858903 )

It mentions that by deleting /system/vendor/lib64/hw/keystore.msm8952.so the error went away.

However now I cannot set fingerprint as the settings force close if I try to set up the pin / pattern / password.

Can someone guide how to fix it.
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] akira6968:
Lemme start off by saying I've got a SM-N910P that's getting the fabled eMMC_write failed error.

Because of its intermittent behavior, it REALLY seems possible it's due to a corrupt file or sector of memory somewhere. Can't say for sure but I'd love to try everything I can, which leads us to...

I know of these portions of software that can be flashed(?) onto a phone:

ROM

modem

kernel

bootloader

EFS?

Pit (re-partition)

Am I missing anything at all? And most importantly... I know (think) these items, if flashed, have to match up to each other. Like, bootloaders matching roms matching kernels, etc... the hard part is figuring out what matches what in an attempt to flash and reformat and wipe as much as possible. It seems to vary what a ROM comes with- some with, some without bootloaders or kernels.... I dunno how to tell for sure??

Anyone got any insight on how to collect and complete these things? Pick any rom, doesn't matter... it's on PK1 at the moment, but had taken the official PL1 update before i flashed PK1 back onto it. It will boot sometimes, but always eventually crashes. If it has to be rolled back to LP, it is what it is lol.

I'm aware of wake-lock bandaid, and other odd suggestions that do not fix this issue. Cleaning house as much as possible just might work- and if it does, someone could be a hero. There's HUNDREDS of devices suffering out there after MM came out.