yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
op3/t has no vendor partition: you need to mount system and change all paths beginning with "/vendor" to "/system/vendor".

---------- Post added at 15:40 ---------- Previous post was at 15:27 ----------

In the logs I've seen, there is not only livedisplay hal crashing, but other hals as well. It seems to me that this relates to some boot timing differences over different boots, depending when hwservicemanager is started - if hardware service manager comes up to late quite some hals (among others also livedisplay) are constantly crashing. Perhaps late start of hwservicemanaher is a followup error from something even more different. Removing livedisplay changes the boot up sequence and it's timing, as using a third party launcher or uninstalling magisk does for others. configstore seems to play in here, too. But I don't completely umderstand, if crashing hwcservice is the cause fpr configstore to crash, or vice versa.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Thanks buddy.

Changed all Mount and Unmount entries from 'vendor' to 'system'

Added '/system' beginning of all Paths

Downloaded and extracted my current ROM build for both my devices and compared paths for the three files mentioned in the Script:

The manifest.xml is the same for both, (except for the /system addition), but the other two have a different filename. For example, 'vendor.lineage.livedisplay@2.0-service.oneplus3' instead of 'vendor.lineage.livedisplay@2.0-service.oneplus_msm8996'

With all that corrected, the zip flashes properly, phone boots and Livedisplay is now hobbled in the same way as my OP5.

Success!

This is of course on crDroid, so i just need to check paths/filenames on a LOS build to make sure it's all the same. (I expect it will be)

BRB. :)

---------- Post added at 16:15 ---------- Previous post was at 15:29 ----------

If you'd really like to test:

https://xdaforums.com/oneplus-3t/how-to/testing-phone-starting-fix-los-based-t3949366

Thanks! :good:
[OnePlus 3 & 3T Cross Device Development] anavarro8794:
What is the HD notification I'm getting on the top left corner on the statusbar? Is there a way to remove it?
[OnePlus 3 & 3T Cross Device Development] H. K. ROY:
have anyone faced this issue? on los16-20190716
[OnePlus 3 & 3T Cross Device Development] Dirk:
I assume you also have the 'SIM 1 is HD capable' message in the Notification shade? I thought every ROM had adopted the modified ims.apk by now, that removes that notification. Not surprised though if LOS hasn't.

Simplest solution for rooted users:

https://play.google.com/store/apps/details?id=com.aboutmycode.NotificationsOff&hl=en

Guide for manual modification:

https://xdaforums.com/yureka/development/mod-device-hd-capable-notification-t3551145

Edit: BTW it means VoLTE is available.

Is it like that on all themes? (Light/Dark) Any mods installed? (Substratum, xposed, etc)

What build?

Last clean flash?
[OnePlus 3 & 3T Cross Device Development] H. K. ROY:
[MENTION=1763460]Dirk[/MENTION] ,I use automatic (wallpaper based) theme, no mods only magisk for root, build-20190716 & I always make a clean flash (wipe cache, delvik, system).

for info ,the issue was resolved after a reboot. if i can reproduce it i will make sure to share logs.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Thanks. LOS could do with a 'restart systemui' option. That usually shakes things like this loose without needing a restart.

That said, restarts are where Boot Animations are seen so everyone should restart as much as possible. And make sure they have a cool Boot Animation to watch while they do it! :p
[OnePlus 3 & 3T Cross Device Development] H. K. ROY:
cheers to RR boot animation for a healthy nap :p
[OnePlus 3 & 3T Cross Device Development] Dirk:
:D
[OnePlus 3 & 3T Cross Device Development] kousik:
Just me or lineage-16.0-20190717-nightly-oneplus3-signed.zip (dirty flashed) is going in crash loop for others too? Came back to lineage-16.0-20190709-nightly-oneplus3-signed.zip ...
[OnePlus 3 & 3T Cross Device Development] :
No problems at all with recent nightlies, no boot loops, ... Have you updated via internal OTA updater?
[OnePlus 3 & 3T Cross Device Development] machuidel:
I did not update my One Plus 3 for about 2 months. Now when I want to do an update it says: "Modem firmware from OxygenOS 9.0.2 or newer stock ROMs is prerequisite to be compatible with this build". Now I read somewhere that I have to go back to the official ROM (wipe my device in the process) and from there I will be able to upgrade. Is there a way around it?
[OnePlus 3 & 3T Cross Device Development] kousik:
That's a mistake I did, but then went back to TWRP and flashed the zip once again from /data/lineageos_update but same result (guess the damage has been done). Looks like internal one doesn't handle encrypted stuffs well.
[OnePlus 3 & 3T Cross Device Development] kousik:
https://xdaforums.com/showpost.php?p=79769445&postcount=2516 may be of help here.
[OnePlus 3 & 3T Cross Device Development] Dirk:
The totally painless way is to use the modified firmware from here:

https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164

Flash that followed by the ROM and you're done.
[OnePlus 3 & 3T Cross Device Development] :
The only way to get this corrected is to flash back a nandroid backup or to set up a clean flash
[OnePlus 3 & 3T Cross Device Development] coolrich1234:
I have installed LOS 16, but my device now doesn't pass Safety Net. Any recommendations?
[OnePlus 3 & 3T Cross Device Development] Dirk:
1) Relock your Bootloader

2) Custom Kernel with Pie Blob support

3) Magisk

4) NLOS
[OnePlus 3 & 3T Cross Device Development] fsanyee:
failed update

Hi,

about two weeks ago I installed twrp-3.3.1-0 and LOS 20190706 on my 3T (from OOS latest), I was happy until today, when I downloaded and installed the latest image with the updater app (20190719). the phone do not boot since, it starts, I unlock the encryption and in a couple of minutes I'm in the TWRP menu. I tried to install the downloaded image from there also, but I have the same outcome. After sideload, it just boots forever, without any reboots.

What can I do ? (other than wipe and start from scratch)
[OnePlus 3 & 3T Cross Device Development] Dirk:
Just a 'hail mary' suggestion, but try flashing the modified firmware+ROM manually in TWRP.

https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164
[OnePlus 3 & 3T Cross Device Development] :
Read the threadT! ota broken, nobody willing to supply logs and do a simple check. Update manually for now.
[OnePlus 3 & 3T Cross Device Development] fsanyee:
Sorry, the first post mentions ulocked BL and upgrade from 5.0.x to 9.0 problems, but that's not what I did. I have never unlocked the bootloader before OOS 9.0.4, or installed any other OS.

OOS 9.0.4 > BL unlock > TWRP 3.3.1 > LOS 20190706 > opengapps nano > setup > encrypt > update to LOS 20190719 broke.

Update: Now the system boots after: wipe System and Cache > install LOS, opengapps. I had to setup google accounts again and reinstall some google apps like gmail and play music, because they were crashing. Everything else seems to work.
[OnePlus 3 & 3T Cross Device Development] k1chy:
Thank you so much for this zip. I was able to enable VoLTE on Lineage OS finally. Searched for a solution in the thread and was able to locate this zip. Tried it, worked great. Thank you once again.
[OnePlus 3 & 3T Cross Device Development] big_marcolino:
Thank you very much. Works fine
[OnePlus 3 & 3T Cross Device Development] ElmirBuljubasic:
Can someone explain to me why the **** did my phone erase all the data After a simple reboot? Ffs
[OnePlus 3 & 3T Cross Device Development] Fritzy62:
Travelling at the moment but I'll gladly try and produce some logs once I get back. I'll ping you when I get back home so you can outline what you need.
[OnePlus 3 & 3T Cross Device Development] anavarro8794:
in build 7/18/19, an app crashed on startup and after that, no app was able to open after. I turned off my screen and then I turned it back on, my Additional Buttons settings reset itself. Anything like this happen to anyone?
[OnePlus 3 & 3T Cross Device Development] realtos:
does it matter what it does on a week old build? update and then post if problems? dont see need to post about old builds thou
[OnePlus 3 & 3T Cross Device Development] :
Great! This only makes sense, if data is encrypted; before diving in the debugging mutt, I would like to make sure it's the right mutt. So, before getting logs, it would be great to exclude twrp: just try an ota with 3.2.3-10 (or 3.2.3-1 - don't use -1 for formatting!).
[OnePlus 3 & 3T Cross Device Development] Dimberr:
Hi, I have an issue with display (color changed, all stretched or white stripes and artifacts, see here https://youtu.be/0_cDrY1HgUU )

My display hw is s6e3fa3 (was changed after the original was broken) and in stock OOS it works perfectly without any issue, also I remember in LO 15 it worked with some custom kernels, so I suppose it can be fixed some way.

Can you look at it?

(I use standard option in Livedisplay and also tried DCI-3 and RGB -> same issue).

No custom kernels, no xposed, not even root, only clean latest linegeos build
[OnePlus 3 & 3T Cross Device Development] :
Because of some thanks I thought latest script could also be usefull for others. See this topic.
[OnePlus 3 & 3T Cross Device Development] Fritzy62:
Will do. I'll be back near my pc in 2 weeks time. (want to make a backup "just in case" first)
[OnePlus 3 & 3T Cross Device Development] Mata99:
I can't use google pay in phisical shops. I haven't got the root. How can I fix?
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
Read this thread.

Round about at least the last 30 pages.
[OnePlus 3 & 3T Cross Device Development] Mata99:
Deleted
[OnePlus 3 & 3T Cross Device Development] Dirk:
:)

Or even the last one or two. Post #2916 was the last time this was asked. Answered on the very next post.
[OnePlus 3 & 3T Cross Device Development] MTKnife:
Camera Crashes

I've been installing custom ROM's for years, and I've searched all over, but I can't figure this one out.

I just installed Lineage 16.0 on my 3T, upgrading from a Nougat ROM (yes, I should have upgraded a long time ago, but getting unbroken blocks of time is difficult with small children around). After reading up for a few days, I did what I took what I thought was the right series of steps....

I upgraded TWRP to 3.3.1.

I upgraded the firmware using this file from this thread: https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164.

I rebooted into recovery, wiped Dalvik, cache, system, and data, then installed Lineage.

I rebooted again into recovery, then installed GApps.

Everything seems to be working normally, but I occasionally get a notice that the camera is crashing--the camera app seems to work fine, but I get the notice. Any suggestions?
[OnePlus 3 & 3T Cross Device Development] whosthebadman:
I'm a novice-level user, and I've been able to research and learn my way out of missteps in the past. But today I goofed in a way I've never encountered before. I am stumped, and I need some help or ideas.

My OnePlus 3t is on LOS15.1, no Gapps package, and TWRP is 3.2.1-0.

After standing idly by, waiting for LOS 16.1 smoke to clear and bugs to be ironed out, I decided this morning to get ready to upgrade. I had done the following this morning:

created fresh TWRP recovery file (System+Data partitions only)

freshest nightly LOS16 build zip moved to phone - addon SU moved to phone

"Stable9.0.3+Firmware_Modem_Oneplus+3T" zip moved to phone

Here is where I messed up:

After reading about the "just flash the modem 9.0.3 firmware with your LOS16 zip" method, I mistakenly flashed ONLY the "Stable9.0.3+Firmware_Modem_Oneplus+3T" zip , and rebooted.

System Reboot yields a black screen with "Decryption unsuccessful" at the top...

I power off, and boot into Recovery/TWRP, thinking "I'll just restore to my backup from this morning and start over".

Nope. TWRP boots to the "Mount - Decrypt Data" screen. I push the Cancel button, and Swipe To Allow Modifications (behaves as though I just installed TWRP). At the main TWRP screen, i push the Restore button... and there is no backup file to load.

I can navigate to Install, and thought "well I can try to go through with the LOS 16 install" but I'm not able to find what directory the files are stored in.

What are my options?

I really don't mind a wiped phone, and starting there, except for one thing: I'd REALLY like to salvage my app data.

is there any way to revert to my backup made this morning?

if so, how?

if not, then is it possible to recover my app data, somehow?
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
Why didn't you read the OP, and the last pages from this thread? first of all you should update your recovery to the latest version... you flashed the Pie FW, and now you MUST FORMAT DATA via TWRP unless your userdata partition keep corrupted :eek: ...

You can go back to 5.0.x FW and restore your backup: Did you copy your backup to an external drive (pc/usb)?
[OnePlus 3 & 3T Cross Device Development] whosthebadman:
so far, that's right. I know I goofed. I know.

You lost me here. But no matter... what's done is done. If there is a remedy, a method to get back to my device as it was before I flashed the 9.0.x fw, then I want to try it.

No, of course I did not backup to USB, or I'd have simply restored by now. I'll try flashing the 5.0.8 fw, then.

So, about how to get out of this mess.

flash TWRP 3.3.1-0

... then reboot to recovery, reboot to fastboot

... ?

If I would flash LOS16 and modded 9.0.4 fw (I cannot link it since I'm new)... would that decrypt my existing data, and leave me with my backup from this morning intact?
[OnePlus 3 & 3T Cross Device Development] sky321:
[MENTION=5091734]dianlujitao[/MENTION]

Probably it‘s a good idea to update the OP. Think FW >9.0.2 is needed currently.
[OnePlus 3 & 3T Cross Device Development] :
If you have no backups saved on usb-otg or any otjer external device, the content of userdata is gone - unrevertable. You need to reformat and reencrypt the userdata partition.

The barrier from 5.0.x fw to 9.0.x fw is karmatic: users with good karma (done their homework before updating the fw) will be fine, users with bad karma (all kinds of trial'n'error guys, aka: users who havn't read before blindly and unkonwingly updated the fw) will loose their data...

This very thread contains an awesome collection of resources: https://xdaforums.com/showpost.php?p=79777086&postcount=2570 (this is not everything needed to read, but a great starting point!)
[OnePlus 3 & 3T Cross Device Development] whosthebadman:
I only flashed a modem fw, not the entire OOS.

Maybe you can help my understanding, but isn't the data still in my device, in a partition that hasn't been wiped? Otherwise, why would others be able to flash the very same fw (along with LOS16) and not lose any data in the upgrade?

what steps do you suggest I use? You mention reformatting and encryption, but I've never "reformatted" anything with twrp. Only wipe and flash.

Wipe System partition

Flash LOS16 + modded 9.0.8 fw

.... ?
[OnePlus 3 & 3T Cross Device Development] :
I've answered that already:

BTW: don't mix wipe and format when reading the resources!
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
A backup in a external device, that was THE METHOD TO SAVE/RESCUE your old data :( ... I'm so sorry for you

Oreo and Pie ROMs have a different encrytion keys, therefore it's a bit dangerous not to have your data in good standing if you want to update.

I recommend you keep the last stable pie firmware (9.0.4.) in order to avoid future troubles. Almost All custom versions have migrated to the latest and stable new FW blobs... So, if you want to stay on the custom ROM side, don't go back to 5.0.8 FW
[OnePlus 3 & 3T Cross Device Development] whosthebadman:
Firstly, I want thank you for answering for the reckless amateur du jour.

I'll put all questions in one place, at the bottom of this post.

Whether it's with or without my LOS15.1 data, I'll end up on LOS16. My only decisions left are:

(1) How can I do/try anything that may salvage my LOS15.1 data, and THEN ... (2) get to LOS16 from where I am at today (described above)

There are 2 things I haven't made clear that I'd like to put out there, in case there is any creative solution:

The firmware I flashed over my LOS15.1 was only the modem fw (9.0.3). File size was 48k, and was not a full OOS zip. I can't link to it (I'm too new) but I got this idea (and zip) from a site called AndroidExplained, who outlined a method of (flash modem fw + LOS16) = keep your data and upgrade with less hassle. it's at androidexplained com/oneplus-3-upgrade-modem/

I do have a previous backup on external storage, but it's from 8mos ago.

I'm further into uncharted waters than I've been in CM/LOS days, and even after reading the threads referenced above, I cannot be sure, so I have to ask:

Does this information in the above 2 bullet points help me at all, or enable any workaround(s) that would salvage any data?

Is it true that flashing the 9.0.3 modem fw zip (and no other zips), then rebooting, has permanently altered my existing data somehow?

Is it possible that wiping System, then flashing (OOS 5.0.8 + LOS15.1) possibly yield a result?

Failing all else, is there some way to use TWRP to access or extract, from where I am at today, any data files at all?

Sounds like I will need a full wipe, and to start from zero.

But before I resign myself to that, I want to explore any possible alternatives to saving some data.

I can live without app settings, even contacts, ... but there are some notes I took in 1 app that are invaluable. I would go to great lengths to scrape those notes, before I start over and do things the right way.

Thanks again.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
You can try the third option. You don't have anything to loose. But I personally don't know ANY person who could recover the encrypted /data files after flashing the firmware 9.X

And yes: Only the firmware has destroyed the data. The new firmware has new encryption keys that aren't compatible with the "old" encrpyted data (like [MENTION=4938641]Viper The Ripper[/MENTION] already mentioned). And for this fact the data gets irreversible damaged

App data, Pictures, or your Notes. It doesn't matter - it's all on /data. Either you can rescue it all or it's all gone.
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
Hi whosthebadman,

your Data is lost. Really. You can't do anything about it, it is too late. Really!

I am unhappy with the situation, too, that we need the buggy 9.0.x firmware to get the latest LineageOS updates. But for poor that's what we have to take. It was the maintainers decision.

Really, your data is lost.

No.

Yes.

No.

"Any" data: yes. But not that data you are asking for.

What you should do now is:

1. Install latest TWRP: LINK

2. Reboot to TWRP

3. Install latest stable Firmware v9.0.4 (be SURE to pick the right one - there are variants for OnePlus 3T and OnePlus 3!!!): LINK

4. Reboot to TWRP

5. Format Data as ext4

6. Reboot to TWRP

7. Wipe everything (everything except USB)

8. Install LineageOS: LINK

9. Install OpenGApps (the right package is preselected for you!): LINK

10. Install the SU arm64 addon (root): LINK

11. Wipe Dalvik & Cache

12. Reboot system

A small hint for the future: Don't be the first to try new things. Bookmark this thread! Read here first! If possible daily!

xda dev is the first source! Other websites that talk about things like these are always outdated.
[OnePlus 3 & 3T Cross Device Development] :
This is factually wrong, but may the cortect answer for [MENTION=10055355]whosthebadman[/MENTION] - see below.

Matter of fact: as long as you don't update the bootloader and the keymaster partitions you are fine. If you only flash the modem partition everything will work like before.

On the other hand [MENTION=10055355]whosthebadman[/MENTION] may refer to firmware as modem - who knows.... [MENTION=10055355]whosthebadman[/MENTION]'s questions clearly show, he hasn't worked his way through the recources... Then again your answer is correct.

Anyway, you are absolutly correct about the loss of data! From the resources [MENTION=10055355]whosthebadman[/MENTION] was given:
[OnePlus 3 & 3T Cross Device Development] whosthebadman:
Also from the resources that whosthebadman was given:

in the same post:

It is very possible to perceive conflicting information, even in the span of 1 post.

It seems that although I followed the sequence you describe, I rebooted to recovery and found my data had been lost.

Someone like me who admittedly does not know better, looks for instructions. In the absence of LineageOS For Dummies, I did the best I could. There simply is no way for a user like me to know everything I do not know, and so I did not know I somehow made a mistake.

Users like me wish to have your level of understanding, and that it were possible to read 3 or 5 threads on this forum, and gain such mastery. Even having done read those resources, I find it difficult to understand without advice, that a mistake has been made. Where does that leave us? Is updating from LOS15.1 -> LOS16 for devs only? Perhaps.

Updates from CM13 -> LOS14, and LOS14 -> LOS15 were fairly casual-user-friendly (updating drivers/firmware). Somehow I knew much less, and yet made fewer (and smaller) mistakes. LOS15 -> LOS16 has been a different experience, a higher-maintenance release as evidenced by posts (and entire threads) devoted to unanticipated consequences. I won't be the last, and it's a learning experience. Thanks for "helping" me, none the less.

Let's check my premises:

Is it possible that my 3T was not encrypted?

In another OP3T thread here I saw a picture of a screen that I did not ever see, with my own device.

It is here, with a broken link: dl.xda-developers com/4/6/9/0/6/7/9/21_January_2019_121152_pm_AEDT.jpg?key=LMmSNVxXm-p8stXavWRH6g&ts=1564433058
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=10055355]whosthebadman[/MENTION]:

The two quotes at the beginning doesn't have conflicting information: if you stick with the 5.0.x bootloader and keymaster (which the modded fw does), the first quote doesn't apply, because the first quote clearly refers to firmware and not to oxygenos-9.0.4-bl-km-5.0.8-firmware (which is the modded fw)....

Also: if bootloader and keymaster arn't chanhed to 9.0.x you won't loose data (this is a matter of fact) - what you describe happens only if you boot once(!) a 5.0.x encrypted device with 9.0.x bootloader and keymaster. Now your data is unrevertable gone - no matter if you follow the instructions of https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164 there after.

You may feel comfortable with this attitude: "Users like me wish to have your level of understanding, and that it were possible to read 3 or 5 threads on this forum, and gain such mastery. Even having done read those resources, I find it difficult to understand without advice [...]". I hope you understand, that I'm not your "search, compile and explain"-engine. If you don't understand the information in the resources, IMHO it's your job to fill the knowledge gaps (all information to do so is here on xda). This two attitudes seem completely incompatible to me.

This isn't bad, it just means my answers will never satisfy you, and your (from my point of view: answered many times) questions will annoy me. So the best for both of us is me stopping answering you.

Good luck
[OnePlus 3 & 3T Cross Device Development] punio4:
Do any of the devs even look at the official issue tracker?

Some issues have been open for months on end without even being acknowledged.
[OnePlus 3 & 3T Cross Device Development] realtos:
so? how is that of your concern?
[OnePlus 3 & 3T Cross Device Development] djplus:
[MENTION=3456089]nvertigo[/MENTION] you are right Every member must go through few posts and understand whats happening with current users and perhaps backup of critical data is the first step every member must take while dealing with custom roms.