yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
Since "clean flash" as well as "full wipe" are used in different meanings by different people, tell the exact steps and a detailed description of your previous setup.

What fw do you use?

What's the configuration of the bootloader (locked or unlocked)?

What filesystems do you use for userdata and cache?

Which recovery are you using?

Which rom zip are you using?

Which additional packages are you using (gapps, magisk and whatever)?

Always give the detailed version, please. Please don't answer these posting only partitially.

---------- Post added at 15:11 ---------- Previous post was at 15:07 ----------

If you need help, be a bit moe precise and give the necessary information. The above staement is shortened that much, that it results in nonsense... It's literally impossible to boot to system after wiping the system partition!
[OnePlus 3 & 3T Cross Device Development] h4rl4n:
Ok, then:

1) Latest available firmware for PIE roms

2) Bootloader unlocked

3) never changed filesystems so i guess default

4) TWRP 3.3.3

5) Latest official LOS nightly

6) Open nano gapps for 9 roms (arm64) + latest magisk 19.7

I came from Nitrogen os. Downloaded rom and gapps, performed full wipe (dalvik, cache, system, data) and then flashed rom and gapps
[OnePlus 3 & 3T Cross Device Development] G-Ray:
1) FW 9.0.5

2) Bootloader unlocked

3) EXT4, encrypted

4) TWRP 3.3.1

5) tried to flash lineage-16.0-20190831-nightly-oneplus3-signed.zip over 20190823

6) open_gapps-arm64-9.0-pico-20190831.zip

I resolved the issue, from TWRP I uninstalled Magisk, reflashed lineage-16.0-20190831-nightly-oneplus3-signed.zip, then flashed the very latest opengapps. (open_gapps-arm64-9.0-pico-20190831.zip)

Edit: My guess is that flashing newer opengpps resolved the issue.
[OnePlus 3 & 3T Cross Device Development] h4rl4n:
But i don't think magisk is the issue, so what are we missing?
[OnePlus 3 & 3T Cross Device Development] G-Ray:
I can't be sure, but in my case I think reflashing latest LineageOS build + newer opengapps (my best guess) + wiped cache did the trick.
[OnePlus 3 & 3T Cross Device Development] h4rl4n:
ah but now if you try to reinstall magisk you go back into loop
[OnePlus 3 & 3T Cross Device Development] :
There is no twrp-3.3.3. Both of you arn't able to give the version of gapps. "Latest" is always prune to misunderstandings - it can change from the time you've written to the time it's read; or you or your recipient has a different status of what is "latest".

The both of you can't imagine how annoying begging for information really is. (Note to myself: stop answering postings with insufficient information, finally!)

Magisk-19.3 (stable channel) works great for me.
[OnePlus 3 & 3T Cross Device Development] G-Ray:
[/COLOR]

Just flashed Magisk and it still works. So I really think flashing opengapps (open_gapps-arm64-9.0-pico-20190831.zip) + wiped cache have resolved my issue. I guess you already tried these steps ?
[OnePlus 3 & 3T Cross Device Development] :
Magisk (and/or Magisk-modules) are known to break updates sometimes. Uninstalling Magisk and Magisk-modules, updating, booting to system, booting to twrp and installing magisk and Magisk-modules again is the well known workaround/fix.

Back on Magisk 14 (or 13 - doesn't recall exactly) the recommended method of installing magisk on a clean flash has been: flash rom, boot rom, finish first time setup, boot to recovery and flash Magisk. Though it's the urtent recommendation to flash Magisk in one shot after rom and gapps, I still use the old recommendation for two and a half years on different devices and never had a single problem.

Also using a newer (or older, for that matter) opengapps package may solve issues (considering the last pages of this thread, there might be some broken builds last week). I always prefer a seldom (compared to opengapps) updated, well maintained and more tested (due to the longer phases of "currency") package like MindTheGapps over auto build nightlies like opengapps. If I need to use opengapps (i.e. if no other package is available for a new android release) and have found a working package, I stick to it. If it comes to arm64 nano package I'm still using 20181209.... ;)
[OnePlus 3 & 3T Cross Device Development] syntesys:
Hi all,

I opened a new issue on lineageos GitLab. Hoping to see the problem resolved, because I cannot flash nothing but lineageos on /system.
[OnePlus 3 & 3T Cross Device Development] :
Can you share the link, please? I can't find it: oneplus3
[OnePlus 3 & 3T Cross Device Development] syntesys:
https://gitlab.com/LineageOS/issues/android/issues/1137
[OnePlus 3 & 3T Cross Device Development] :
Strange:
[OnePlus 3 & 3T Cross Device Development] syntesys:
I've seen that the issue is opened with confidentiality checked. I asked to change the confidentiality to off, so you can see the issue
[OnePlus 3 & 3T Cross Device Development] :
This assumption (which you present as a matter of fact again here) has been falsified already by yourself:

https://xdaforums.com/showpost.php?p=80163848&postcount=3100

Obviously you ACTUALLY CAN flash additional packages to /system!

Claiming an already proofed to be wrong guess again and again doesn't help to solve your issue.
[OnePlus 3 & 3T Cross Device Development] syntesys:
Obviously I can flash, but I want to use it with OpenGapps, Magisk, Cerberus and other stuff I want to install on my op3t.

This reply was written not for complete my investigation , but getted there just for not rewrite all...
[OnePlus 3 & 3T Cross Device Development] :
You need to understand, that "because I cannot flash nothing but lineageos on /system" is not a short or summerized version of I can't "use it with OpenGapps, Magisk, Cerberus and other stuff"; but "because I cannot flash nothing but lineageos on /system" is misleading everybody, who tries to help you?

If you are in need of help misleadig the people, who are willing to look at your issue isn't usefull.
[OnePlus 3 & 3T Cross Device Development] jakito:
I just dirty flashed 20190831 over 20190825 and nothing bad happened. I have magisk, unlocked bootloader and encrypted storage. I also used the open_gapps-arm64-9.0-pico-20190702.

I have f2fs in every partition supported by LineageOS (don't remember which one's are...
[OnePlus 3 & 3T Cross Device Development] ayamstr:
Airtel Volte working for anybody ?
[OnePlus 3 & 3T Cross Device Development] :
You've still not changed the confidentiality (you need to do it yourself): https://docs.gitlab.com/ee/user/pro...l_issues.html#modifying-issue-confidentiality
[OnePlus 3 & 3T Cross Device Development] tshredder:
I also got bootloop after latest update.

twrp 3.3.1-0, flashed Lineage 20190703 via the updater. Only gapps, no other add-ons.

Now it doesn't boot anymore. Either it reboots to recovery, or it just sits with the lineage animation playing for ever (I tried waiting >1 hour).

I can get dmseg through adb from recovery, is that helpful?
[OnePlus 3 & 3T Cross Device Development] :
Read the thread, before posting: current twrp is not working for automatic flashing!!! You can fetch the update with updater, but you need to flash manually. This is a bug in twrp as explained already.
[OnePlus 3 & 3T Cross Device Development] tshredder:
Sorry I did read but didn't find a solution other than possibly full wipe. I have always done manual flash, just this time did I try the updater. I tried manually flashing after it failed of course.

I didn't find a nice solution by reading back in the thread which is why I asked. I ended up cleaning /system, which forces a full re-install of the phone. Not ideal, but yes, I do have a workable phone again.

Just to summarize if others come after:

- boot to recovery

- adb push latest lineage and opengapps

- format/wipe system and cache

- install lineage and mindthegapps, using opengapps doesn't work as noted in the thread.

- reboot and start recovery process...
[OnePlus 3 & 3T Cross Device Development] :
You need to improve your reading skills: each and every correct bit of information of this postimg has been given in the thread already! (Did you even try to thread search for update and read the first page of hits and tneir followups? https://xdaforums.com/showpost.php?p=80009239&postcount=2970 https://xdaforums.com/showpost.php?p=80051544&postcount=2992 https://xdaforums.com/showpost.php?p=80166223&postcount=3116)

"I ended up cleaning /system, which forces a full re-install of the phone." is nonsens, of course. Wiping data or formating data requires a full reinstallation, Wiping system just requires to reflash gapps and mods, but no complete reinstallation.
[OnePlus 3 & 3T Cross Device Development] love4chat:
So how's lineage 16 working on opo3?

A review would be good
[OnePlus 3 & 3T Cross Device Development] Imotep95:
That's too old.

https://review.lineageos.org/q/project:LineageOS%252Fandroid_device_oneplus_oneplus3+branch:lineage-17.0
[OnePlus 3 & 3T Cross Device Development] :
Just a simple theming question and probably an good reason why... but why is the set aosp keyboard theme not already used on startup when password must be given in?

Now it is ugly grey, but dark theme is set in Android...
[OnePlus 3 & 3T Cross Device Development] :
Do you talk of the secured boot password? If so:

Because only the Baron of Münchhausen is able to pull himself by his own hair out of the bog...

App related settings are stored under /data. /data is encrypted. The password is needed to decrypt dta. Data is needed to read aosp keyboard app's settings...
[OnePlus 3 & 3T Cross Device Development] :
Haha, sounds like I was not very clever... :D:D

Could have known myself ofcourse but thanks for clarifying ;)
[OnePlus 3 & 3T Cross Device Development] veasNN:
Nice ROM but...

So I have recently installed the Nightly 16.0 build in my OnePlus 3 and found out Dual SIM doesnt work. As far as I have seen it the second SIM tries to connect to the same network as the first SIM but the SIM cards are in different networks so the second SIM never works for me. Does anyone know how to fix it or should I use another ROM?
[OnePlus 3 & 3T Cross Device Development] legendavey:
That doesn't sound right. You should clean flash the ROM with the recommended firmware and check if it works. If it's still broken, check if it works on stock OOS.
[OnePlus 3 & 3T Cross Device Development] veasNN:
The latest OOS (9.0.5) was installed and Dual SIM worked fine there.
[OnePlus 3 & 3T Cross Device Development] realtos:
omg is he already workin on 17? thats serious dedication. huge thumps up [MENTION=5091734]dianlujitao[/MENTION]
[OnePlus 3 & 3T Cross Device Development] PiereMallao:
At the momemt i use LineageOS 15.1 on my oneplus3. I have problems with wifi. Sometimes the device lost the wifi connection when display is locked. Is this also a Problem with LineageOS 16?
[OnePlus 3 & 3T Cross Device Development] veasNN:
For me using Lineage 16 in a OnePlus 3 there arent any WiFi problems.
[OnePlus 3 & 3T Cross Device Development] realtos:
i never had any problems with wifi, 15.1 nor 16
[OnePlus 3 & 3T Cross Device Development] PiereMallao:
I have this problems from the first day i used LineageOS on the oneplus3. Sometimes at night wifi connection is lost so that my podcatcher cant update my podcast.
[OnePlus 3 & 3T Cross Device Development] syntesys:
I don't have permissions to change confidentiality. I tried it but nothing; I asked for it but I hadn't response.
[OnePlus 3 & 3T Cross Device Development] Pahom-ka:
Increase call volume

Hello!

I'm using OnePlus 3T A3003 with lineage-16.0-20190907 build and last radio firmware.

When talking (GSM or SIP or Viber, Whatsapp, Telegram), the volume is very low, how to increase talk volume? I know about /etc/mixer_paths.xml file, but in this system i don't found this file, but i found /system/vendor/etc/mixer_paths_tasha.xml file, maybe this file is need to correct?

I found in internet instructions for changing settings in this file, but not one don't work.

How to increase the talk volume?

/system/vendor/etc/mixer_paths_tasha.xml is here
[OnePlus 3 & 3T Cross Device Development] :
https://review.lineageos.org/c/Line...eplus3/+/238058/1/audio/mixer_paths_tasha.xml

Be carefull, I'm pretty sure this can physically damage the speaker. I've never suffered from low in call volume, but with this patch applied, disortion starts at about 50% volume - with 100% volume this patch probably would have damaged the speaker.

BTW: I know of at least two users, who solved the low in-call volume by cleaning the mesh in front of the speaker.
[OnePlus 3 & 3T Cross Device Development] Pahom-ka:
Thank you for your help!:good: It's work for me. I'm write 92, no 95.

PS. I have 2 oneplus 3T (32 gb and 64gb), and each have this problem with Lineage OS.
[OnePlus 3 & 3T Cross Device Development] galaxykeks:
Hi guys, I am wondering if I missed smth.

I had a clean flash on the build of 28th august. I did a update today and now my OP3T is not booting anymore.

I get to the boot password, i enter it, then i see "starting Android" and the startup animation. At some point the phone vibrates and rebootes.

Any ideas?
[OnePlus 3 & 3T Cross Device Development] Dirk:
How did you do the update and what build of TWRP are you using?
[OnePlus 3 & 3T Cross Device Development] galaxykeks:
Hi Dirk,

it's twrp-3.3.1-0-oneplus3.img.

At first i tired with the build in update mechanism.

After this didn't work, I tried also flashing it via twrp. Also no success.

I also tried the build of the 7th september. Same result.

Since I didn't find any recent post with problems, i am wondering if i missed something obvious :eek:
[OnePlus 3 & 3T Cross Device Development] rohan164:
[MENTION=4405529]nvertigo67[/MENTION]

is there any problem/cons if i install twrp-3.2.3-0 or twrp-3.2.3-10?

because i want updater to work properly.
[OnePlus 3 & 3T Cross Device Development] galaxykeks:
ohh i completely forgot about that. :rolleyes:

The thing is, also dirty flashing does end in a boot loop.

i didn't flash around for quite a while, so i lost my training :D

Any chance to recover without starting fully from scratch?
[OnePlus 3 & 3T Cross Device Development] helderfp:
If you flashed first via ota the only way to solve that is to wipe system and then flash ROM via twrp, it happened to me, and it was the only way to solve
[OnePlus 3 & 3T Cross Device Development] galaxykeks:
Thanks for the advise. I did this, but the phone is booting since over 15 min.

This seems a bit long. I will wait a bit more and see.

If anything changes i will report back.
[OnePlus 3 & 3T Cross Device Development] :
Just dirty flashing stoped working to recover from this situation. You need to

wipe system, dalvik and cache

since wiping system is (by default) a fprmat operation, I recommend a reboot to recobery at this point

flash rom

If you have used gapps, flash the exactly same zip as that you've used on setup

reboot to system

if this works, you can boot to recovery and flash additional packages like Magisk - if 5. doesn't work: clean flash

[MENTION=5996692]rohan164[/MENTION]

You can use twrp-3.2.3-10 (prefered) or twrp-3.2.3-0 without any addotional actions if your bootloader is unlocked. If your bootloader is locked, you can try to modify the boot image signer zip I've posted some weeks ago, to sign the recovery image instead of the boot image (not tested).
[OnePlus 3 & 3T Cross Device Development] galaxykeks:
Hi nvertigo67, also thank you for taking the time to answer me.

This morning i had the chance to search for old discussions on this thread and found a discussion about that.

And before reading your thread, i did almost what you said.

Previously i also had magisk deinstalled without success, what i did in the end was: (in case someone runs into the same trap)

- reboot to twrp 3.3.1

- wiped system only

- flashed latest nightly (10.09.19)

- reboot (which did never end)

- back to recovery

- flashed latest gapps mini (11.09.19) + magisk

- wiped cache + dalvik

- reboot

and it worked. it thought me that i should follow this thread more frequently again :D

Yesterday late evening i had the ingenious idea, shortly before going to bed to flash the OTA. Later my son cried and i had no chance to browse the thread. i probably could have solved it on my own with more time.

Still thanks for your support guys! (even though it was a old/ known issue)
[OnePlus 3 & 3T Cross Device Development] chotaire:
This also didn't work for me. Will boot forever. Hopefully I will be able to restore from TWRP backups. When is this issue going to be addressed?
[OnePlus 3 & 3T Cross Device Development] :
That twrp-3.3.1-0 can't handle automatic flashing? When the patch I've referenced earlier in this thread is merged.
[OnePlus 3 & 3T Cross Device Development] djplus:
Inbuilt OTA update is working fine with twrp 3.3.1.0

even it retains magisk and gapps.
[OnePlus 3 & 3T Cross Device Development] :
Tell that to the users reporting rescue partys from automatic flashing via Updater.apk with twrp-3.3.1-0 on the last 10 pages...

See also: https://xdaforums.com/showpost.php?p=80009157&postcount=2969 and https://xdaforums.com/showpost.php?p=80009157&postcount=2970
[OnePlus 3 & 3T Cross Device Development] punio4:
The only way I could update was via Lineage Downloader, but it kinda died yesterday.
[OnePlus 3 & 3T Cross Device Development] vinoxflame:
does manual flashing of update(rom zip) doesn't work for you?
[OnePlus 3 & 3T Cross Device Development] punio4:
It does suddenly.
[OnePlus 3 & 3T Cross Device Development] CodesCodger:
It no longer recognizes lineageos for some reason
[OnePlus 3 & 3T Cross Device Development] :
I wonder, why LineageOS is the only ROM that doesn't work at all on my OP3T? I'm trying to install latest nightly (tried some different builds) using TWRP 3.2.3-1 (tried also latest with the same result). Firmware installed from OOS 9.0.5. After i flash it phone just shows bootanimation for about 10 minutes and then goes back to recovery. But any other ROM (e.g.. Pixel Experience) works like a charm. Any suggestions?
[OnePlus 3 & 3T Cross Device Development] djplus:
What was your previous setup ?
[OnePlus 3 & 3T Cross Device Development] :
Latest Pixel Experience, but also tried previously to flash straight after I unlocked bootloader on OOS 9.0.5. Result is the same - goes back to recovery.
[OnePlus 3 & 3T Cross Device Development] Master_TC:
[MENTION=4608528]alexius89[/MENTION]

What I would do:

1. Install latest TWRP: LINK

2. Reboot to TWRP

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

4. Reboot to TWRP

5. Format Data as ext4

6. Reboot to TWRP

7. Wipe everything (everything except USB)

8. Install LineageOS:

9. Install OpenGApps

10. Wipe Dalvik & Cache

11. Reboot system
[OnePlus 3 & 3T Cross Device Development] Blamz:
Go to TWRP - Wipe - Format Data - Type YES - reboot to TWRP. Then proceed with your normal flashing of firmware, rom, gapps and magisk. Should boot now.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Stop using 3.2.3-1 for a start. Whatever problems you're having now are only going to get worse when you realise you've broken encryption for good. (see below)

Good advise. Just not with 3.2.3-1. That will break the encryption footer. If this has already been done format again with 3.2.3-0 to fix it. (later builds will not fix a broken footer)

I suggest EXT4 for compatability reasons.

As to what TWRP is good for daily use.... If OTA is important to you, 3.2.3-10 iirc or if you update manually then the latest has the benefit of being able to relock the Bootloader without Data loss. (Good option for passing Safetynet without the need for a custom Kernel or Magisk).
[OnePlus 3 & 3T Cross Device Development] :
So I tried that. Flashed TWRP 3.2.3-0 instead of previous one, formatted data (fs was already ext4) then usual steps as described earlier. Nothing changed - still goes back to recovery after bootanimation. :confused:
[OnePlus 3 & 3T Cross Device Development] :
Please describe all steps taken to flash los en detail (including the exact version of all software used!). Please show us the recovery logs from flashing fw and los (be aware to copy /sdcard/recovery.log to /sdcard/recovery-fw.log before rebooting to recovery, flashing los and saving the second recovery.log).
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Do you install any apps to /system/priv-app ?
[OnePlus 3 & 3T Cross Device Development] :
I suggest to wait for the detailed description and the two recovery logs. Questions like yours are answered implicitly then.

BTW: read this thread, it's proofed that installing to /system/priv-app is NOT!!! the culprit.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
For me it was, i always installed Cerberus to priv-app but since the permissions whitelist was set to enforce (https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/251804) it always ended in a bootloop (and thats totally understandable when reading this page https://source.android.com/devices/tech/config/perms-whitelist)
[OnePlus 3 & 3T Cross Device Development] :
My fault. I thought you were referencing to gapps, which always install parts in priv-app. I always assume that if we talk of clean flashes, only rom and gapps are installed; but you are right: for all people clean flash has a different meaning...

Exactly these misunderstandings made my asking for a detailed description of all steps, all exact versions of al used software and complete logging of all steps... ;)

EDIT:

You can still install third party apps to priv-app without bootloop, of course. You just need to do it the same way the gapps flashable zips do: add /system/etc/permissions/privapp-permissions-Cerberus.xml with your Cerberus installation rountine (or zip).
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
Sometimes I download the LineageOS image on one OP3T and send it later to another OP3T by bluetooth.

The transfer takes about 2 hours. Why is it so slow?
[OnePlus 3 & 3T Cross Device Development] felagund:
Because you do it over a technology not suitable for such transfers.

There are apps for sharing - some share over WiFi.
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
No, that can't be the answer.

Bluetooth must not be that slow...
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
No problem. :)

And thanks for the hint, I'll use it and adjust my installation script. :good:
[OnePlus 3 & 3T Cross Device Development] :
650 MB in 2 h is roughly 0.7 Mbit/s. According to https://en.wikipedia.org/wiki/Bluetooth_Low_Energy (table at the middle of the page; see Application throughput) this looks reasonable to me.

You need to consider the 2.4 GHz bands are busy due to wifi. The more 2.4 GHz wifi APs are active, the less speed you effectivly get (on bt as well as on wifi).

Basically [MENTION=2725640]felagund[/MENTION] is right: if you want to transfer larher files, bt is not the technology of choice.

May I ask, which speeds you expect to get from bt?
[OnePlus 3 & 3T Cross Device Development] realtos:
then find the answer urself then? what a arrogant comment
[OnePlus 3 & 3T Cross Device Development] Imotep95:
https://youtu.be/JmvCpR45LKA

Use Google before posting such things. Read, learn.
[OnePlus 3 & 3T Cross Device Development] legendavey:
Unfortunately, this issue also affects the build with LA.UM.7.6.r1-03600-89xx.0 - had a friend who hasn't upgraded test it with his headset. I'm not too sure about that commit either, but I won't be able to test my own personal build till the weekend. :(
[OnePlus 3 & 3T Cross Device Development] racenrich:
hello all.

Just wanted to say been running this ROM since Friday and all has been pertty good. no i havent run the entire system, but for daily useage no issues.

the ear bud issue above isnt affecting me, using the original buds from OP3.

Only issue i have come across is on the keyboard i cant use the microphone to talk to text...did i miss a setting somewhere? any info would be great.

Good job on this build.

Cheers,

Rich K
[OnePlus 3 & 3T Cross Device Development] :
https://xdaforums.com/oneplus-3/one...1-20180223-t3754855/post78313837#post78313837