yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T Guides, News, & Discussion] BillGoss:
The post you linked is the full rom for the 3T. [MENTION=4405529]nvertigo67[/MENTION] was referring to the 3.
[OnePlus 3T Guides, News, & Discussion] :
Yes. Additionally I want to use the zips from otafsg1.h2os.com, because that's the ota download source.

In twrp dd the /dev/block/bootdevice/by-name/modem to a file. grep for Time_Stamp in this file. For 9.0.6 this should show a datr of 2019-11-04 21:20:14 for op3 or ~5min later for op3t.

dd if=/dev/block/bootdevice/by-name/modem of=/sdcard/Download/NON-HLOS.bin
strings /sdcard/Download/NON-HLOS.bin|grep Time_Stamp

Always check the console output and the recovery log, when you think something's wrong with flashing something.

EDIT:

9.0.5 and 9.0.6 have the same baseband version:

ingo@adler /usr/local/src/firmware-3t $ git checkout 9.0.5
ingo@adler /usr/local/src/firmware-3t $ strings op3t/firmware-update/NON-HLOS.bin |grep MPSS.TH.2.0.c1.9-00102-M8996FAAAANAZM-1.197095.1.1
"modem": "MPSS.TH.2.0.c1.9-00102-M8996FAAAANAZM-1.197095.1.198697.1",
MPSS.TH.2.0.c1.9-00102-M8996FAAAANAZM-1.197095.1.198697.1
ingo@adler /usr/local/src/firmware-3t $ strings op3t/firmware-update/NON-HLOS.bin |grep Time_Stamp
"Time_Stamp": "2019-07-31 19:47:38"
ingo@adler /usr/local/src/firmware-3t $ git checkout 9.0.6
ingo@adler /usr/local/src/firmware-3t $ strings op3t/firmware-update/NON-HLOS.bin |grep MPSS.TH.2.0.c1.9-00102-M8996FAAAANAZM-1.197095.1.1
"modem": "MPSS.TH.2.0.c1.9-00102-M8996FAAAANAZM-1.197095.1.198697.1",
MPSS.TH.2.0.c1.9-00102-M8996FAAAANAZM-1.197095.1.198697.1
ingo@adler /usr/local/src/firmware-3t $ strings op3t/firmware-update/NON-HLOS.bin |grep Time_Stamp
"Time_Stamp": "2019-11-04 21:25:29"

Getting Time_Stamp from the modem partition is the only way to tell, if it's 9.0.5 or 9.0.6. Baseband version is the same.
[OnePlus 3T Guides, News, & Discussion] Iceman248:
Thanks, it is indeed 9.0.6. I noticed my vendor security patch level is April 1, 2019 though. Is it supposed to be that? I would've figured that'd be a very recent date. I can't find anything with that date with this phone.

Edit:

I did find something with 4/1/2019 date, but it's from OOS 9.0.2 firmware, which I've never had at any point, plus LOS uses 9.0.4 I believe, so I don't know why I'm getting that date. I also have a patch that passes SafetyNet that changes my build date to 8/1/2019 for 9.0.5 firmware. It works, despite my firmware being 9.0.6 and my patch level being 9.0.4's 4/1/2019. Needless to say, this is rather confusing to me.

Edit 2:

I found thread about LOS needing 8/1/2019 fingerprint, which has been working, but date shows 4/1/2019, so I just don't understand why About Phone says that.
[OnePlus 3T Guides, News, & Discussion] :
First of all: build fingerprint and sec patch date arn't related to fw, but to the rom.

los-16 uses the build fingerprint from 9.0.5:

https://github.com/LineageOS/androi...mmit/0edef8d67e5e07307744797ec9404f54eb810b6d

To pass safetynet api you need sec-patch-2019-08-01_v02.zip after that the security patch date in the gui will show August 1st.

The 2019-04-01 is the vendor security patch level, which is still April 1st (https://github.com/LineageOS/androi...us3/blob/lineage-16.0/lineage_oneplus3.mk#L27 ).
[OnePlus 3T Guides, News, & Discussion] Iceman248:
Thanks. That patch does work, as well as the Magisk Props module I had been using, which stays working after dirty flash update, which apparently this script doesn't, so I was planning on going back to that.

However, the patch level doesn't show 8/1/2019 in settings. Shows the following in pic on LOS 17, which I'm currently running.
[OnePlus 3T Guides, News, & Discussion] :
I get "invalid attachment"...
[OnePlus 3T Guides, News, & Discussion] Iceman248:
https://imgur.com/a/YiW88Dw
[OnePlus 3T Guides, News, & Discussion] :
Strange. I've no idea. But I havn't messed with los-17.

Anyway, as long as it's passing safetynet... ;)

EDIT: perhaps it's cached, have you tried wiping caches and dalvik from recovery?
[OnePlus 3T Guides, News, & Discussion] :
For the op3 full 9.0.6 zip - here we are: https://www.oneplus.com/de/support/...ign=Sub+Networks&utm_term=78888&utm_content=0
[OnePlus 3T Guides, News, & Discussion] :
For completeness:

The unpacked rom I've made from the incremental update as described here is in branch op3-9.0.6-incr, the unpacked full rom is op3-9.0.6. The follpwing command diffs the complete rom but the META-INF directory:

ingo@adler /usr/local/src/oxygenos $ echo *
META-INF RADIO acct bin bugreports cache charger charger_log config d data default.prop dev etc firmware-update init init.environ.rc init.oem_ftm.rc init.rc init.recovery.qcom.rc init.usb.configfs.rc init.usb.rc init.zygote32.rc init.zygote64_32.rc mnt odm oem plat_file_contexts plat_hwservice_contexts plat_property_contexts plat_seapp_contexts plat_service_contexts proc product res sbin sdcard sepolicy sepolicy_debug storage sys system ueventd.rc vendor vendor_file_contexts vendor_hwservice_contexts vendor_property_contexts vendor_seapp_contexts vendor_service_contexts verity_key vndservice_contexts
ingo@adler /usr/local/src/oxygenos $ echo *|cut -d " " -f2-
RADIO acct bin bugreports cache charger charger_log config d data default.prop dev etc firmware-update init init.environ.rc init.oem_ftm.rc init.rc init.recovery.qcom.rc init.usb.configfs.rc init.usb.rc init.zygote32.rc init.zygote64_32.rc mnt odm oem plat_file_contexts plat_hwservice_contexts plat_property_contexts plat_seapp_contexts plat_service_contexts proc product res sbin sdcard sepolicy sepolicy_debug storage sys system ueventd.rc vendor vendor_file_contexts vendor_hwservice_contexts vendor_property_contexts vendor_seapp_contexts vendor_service_contexts verity_key vndservice_contexts
ingo@adler /usr/local/src/oxygenos $ git diff op3-9.0.6-incr op3-9.0.6 -- $(echo *|cut -d " " -f2-)
byte 0/0 (END)

Q.E.D.
[OnePlus 3T Guides, News, & Discussion] sadiq00786:
Please tell if i can upgrade directly from 9.0.4 to 9.0.6??
[OnePlus 3T Guides, News, & Discussion] :
Yes, you can
[OnePlus 3T Guides, News, & Discussion] :
Since the question is quite unspecific and the the information in OP should be sufficient to answer the above question, let me add to avoid misunderstandings: as long as you stay with 5.0.x bootloaders you can up- and downgrade as you like. Never change from 5.0.x bootloaders to 9.0.x bootloaders or vice versa.
[OnePlus 3T Guides, News, & Discussion] sadiq00786:
Thank you for the quick reply. How can i check my current firmware and bootloader? Please let me know.
[OnePlus 3T Guides, News, & Discussion] :
Stick to xda rule #1, please!

https://xdaforums.com/oneplus-3t/ho...re-barrier-t3941164/post80396741#post80396741
[OnePlus 3T Guides, News, & Discussion] qbnm:
data rescue after 5.0.x to 9.0.x update

Dear folks,

first of all, happy and healthy New Year to everyone!

I updated my OnePlus 3T with an encrypted data partition with unlocked bootloader from 5.0.x to 9.0.x and booted it, which lead to data loss. Then, it came out, that the backup I made before this is invalid (that HDD is gone forever) :(

I tried multiple versions of TWRP, but none of them could decrypt the partition for me - neither with the known PIN nor with "default_password".

Eventually, I did a full binary backup of it via "adb pull" and have a raw image (121,57 GB). A standalone Ubuntu Linux also detects this raw data as a partition, so I suppose, "adb pull" went well. Also I know the PIN of the phone.

Now, is there any chance to rescue the data from the data partition? If someone is interested in helping me, I am willing to donate a lot of $$$ to a one who gets the data back for me, because it was really important and I desperately want it back.

I am aware of the uncommercial nature of xda-developers.com and will therefore publish all general findings made during the data rescue research, so that everyone can profit from it.

Please, feel free to contact me to get the job. I’ll send you the partition dump and the PIN. Thank you. :fingers-crossed:
[OnePlus 3T Guides, News, & Discussion] :
We need more information: give a detailed description of the running setup you've started with and a detailed step-by-step description (including exact names of flashed zips) of what you've done from there.
[OnePlus 3T Guides, News, & Discussion] :
See OP: once you've booted an (5.0.x) encrypted setup with unlocked bl with 9.0.x bl, your data is gone. We doesn't know exactly what's happens on this first boot to mess up the encrypted data partition, but as a result the information in the encryption footer doesn't allow decrypting data again (a detailed analysis on this is in the official los-16 thread).

Theorethically the raw data of the data partition is still present in the image you've pulled, but I've no idea how to decrypt this, since the encryption footer (should be at the end of the image) is no longer valid.
[OnePlus 3T Guides, News, & Discussion] qbnm:
I just googled again and found this: android.stackexchange.com/a/216410. Unfortunately it doesn't sound promising :(

I suppose, the only theoretical way to decrypt the data would be to investigate the OnePlus firmware and find out, what exactly has gone wrong during the encryption footer migration and to try to recreate it or find a new correct password on this basis.

Though the overall chances seem low, I’ll keep the raw dump for unlimited time. The data will be important and relevant also after years pass by. So, if someone reads this in future and is willing to provide some (well-paid!) help with this Android / LUKS data reconstruction (in particular, the reconstruction of a corrupted Android encryption footer or possibly a brute-force method, should that be helpful, or some other measure to recover the partition data), please, don’t hesitate to write me. All general technical findings will be absolutely shared to the whole community with credits to the expert.

Every sharing of this posting with your fellow devs, who might be interested doing the quest is greatly appreciated and, should it lead to the deal, will also be rewarded! Thank you.
[OnePlus 3T Guides, News, & Discussion] tguadagno:
clean 3t, which way is best

hi, i have been searching, but i don't see that anyone has asked this question exactly...is there a way to use stock 9.0x firmware on a 3t and LineageOS if i DONT care about wiping? I have a 3T that i currently have Lineage 16 but not current because i am on 5.08 firmware. I could completely wipe phone, given that, would it work to flash stock OxygenOS on the phone (presumably to get 9.0 firmware) and then go through the procedure to install Lineage again?

thanks in advance
[OnePlus 3T Guides, News, & Discussion] :
Use twrp >=3.3.1-0, relock (will wipe complete userdata including /data/media like formating) bootloader and use https://github.com/nvertigo/firmware-3t/raw/master/archive/op3t/oxygenos-9.0.6-firmware-3T.zip

If you encounter selinux permissive afterwards use the modded fw.

This is immanent if you read the OP closely. ;)
[OnePlus 3T Guides, News, & Discussion] Ysfzone:
I'm confused !!

I'm on Havoc 2.9 with 9.0.5 firmware

how i can update to 9.0.6 firmware ??

i have OP3
[OnePlus 3T Guides, News, & Discussion] Viper The Ripper:
Flashing 9.0.6 FW :eek:
[OnePlus 3T Guides, News, & Discussion] :
Usually, this results from not reading the OP.

Stock fw or modded fw?

If you have a 5.0.x bl (aka modded fw) stay with it. If you use 9.0.x bl (aka stock or unmodded fw) stay with it.
[OnePlus 3T Guides, News, & Discussion] tguadagno:
hi, thanks for the quick reply. i think i am missing some steps in your reply. i am already using twrp. So, I would start by going into lineageos/dev options and relock the bootloader? then i reboot to twrp, load the 9.06 firmware? then wipe and sideload using adb the current lineageos and gapps?

is this right?

thanks again
[OnePlus 3T Guides, News, & Discussion] :
No.

What exact fw package do you run currently on your device? If you are on modded 9.0.5 fw, boot to twrp-3.3.1-0 or later, flash modded 9.0.6 fw and just reboot the installed rom. If you are on the unmodded stock 9.0.5 fw, boot to twrp-3.3.1-0 or later, flash unmodded stock 9.0.5 fw and just reboot the installed rom. If everything works update the rom according to rom's OP.

If you want to use stock fw and a locked bl, do so - then you don't need to use the modded fw and the instructions of this thread at all, just use the stock fw.
[OnePlus 3T Guides, News, & Discussion] tguadagno:
ok, sorry for the lack of info, I am currrently running lineageos 16 (pre 9.x firmware requirement) and stock 5.08 firmware. the system is unlocked (obviously) and i have twrp installed.

what I want is unmodded 9.06 firmware with lineagos 16 and am ok with wiping if i have to.
[OnePlus 3T Guides, News, & Discussion] :
Then this is the wrong thread.
[OnePlus 3T Guides, News, & Discussion] tguadagno:
sorry about that
[OnePlus 3T Guides, News, & Discussion] :
You'll find relock and fw update instructions in the official los-16.0 thread (in the postings; not in the OP) and partly in the official twrp thread.
[OnePlus 3T Guides, News, & Discussion] hyperorb:
I mistakenly updated from the system update. Now

TWRP is replaced by stock recovery

System says decryption unsuccessful

How to recover from here ? Appreciate any suggestions
[OnePlus 3T Guides, News, & Discussion] :
See OP:

All data on you userdata partition is irreversibly gone now.

I assume you are on oos 9.0.6, now.

fastboot flash twrp

boot the freshly flashed twrp (without!!!! booting oos in between)

allow twrp to make changes to system, adjust twrp settings to your likings and reboot to twrp

format data and reboot to twrp

change fs on data back to f2fs (formating data in step 4 will use ext4) and reboot to twrp

flash oos 9.0.6 and wipe chaches/dalvik

reboot to system
[OnePlus 3T Guides, News, & Discussion] hyperorb:
Steps 1-4 fixed the issue. Data is gone.

Thanks:good:
[OnePlus 3T Guides, News, & Discussion] :
I've just added a second sidenote to OP.
[OnePlus 3T Guides, News, & Discussion] RickyTr99:
Hi, I'm currently run Los 16 on Oreo FW and now i want to update with the Pixel Experience 10 or Nos 10.

So, these steps -->

-install custom fw

-reboot twrp

-wipes

-install rom and reboot

--> are rights?

Thanks
[OnePlus 3T Guides, News, & Discussion] Viper The Ripper:
Yes, the important thing to know is, if your device is or not encrypted... and you aren't so you are good to go.

Keeping your TWRP updated and doing backups are always recommended ;)
[OnePlus 3T Guides, News, & Discussion] RickyTr99:
thanks a lot, i'll update the twrp with the 3.3.1-0 and do a nandroid before installation.

But, just for curiosity, the thread talks about devices which are encrypted; why did you say that beacause i'm not encrypted i'm good to go? :confused:
[OnePlus 3T Guides, News, & Discussion] Viper The Ripper:
1. You claimed that you are not encrypted.

2. If you read carefully you understood that there's a issue updating our devices from OOS 5.0.8 (Oreo) to OSS 9.x (Pie). That error forces us to format our device in other to upgrade to the newest Android 9.X - encryption/keymaster aren't compatible any more.

3. The first ROMs that were developed based on Android 10 weren't compatible with Android < or = 9.X encryption, so you musted FORMAT /userdata partiton to remove it before flashing a new ROM...

Nowadays the trend has been reversed and most ROMs are including encryption support, so you can flash them even with an encrypted device.
[OnePlus 3T Guides, News, & Discussion] :
Please read the OP. If your device is NOT encrypted, for what reason do you want to flash the modded fw? It's all explained in OP.
[OnePlus 3T Guides, News, & Discussion] :
UPDATE

I've added another flavour of fw packages and added this to OP:
[OnePlus 3T Guides, News, & Discussion] :
The choice of formware has nothing to do with su and magisk. Keeping the data partition doesn't mean you don't need to wipe data on major version updates or rom changes.

If your device's data partion is encrypted, bootloader is unlocked and you go from 5.x to 9.x firmware, you need to format the data partition (not only wipe), which deletes the complete content of the data partition - with tne modded fw you do not need to format data (though I stromgly recommend wiping data: clean flash on major version updates or changing roms).
[OnePlus 3T Guides, News, & Discussion] jamames:
Reflash after updates?

Does the firmware with alipay removed need to be reflashed after updating the ROM?
[OnePlus 3T Guides, News, & Discussion] :
As explained in OP: the need of reflashing after updating the rom depends on the rom not on the flavour of fw. If the rom ships with fw (like oos) you need to flash the modded fw before rebootin, if the rom ships w/o fw (like all unified roms) there's no need to reflash the modded fw.
[OnePlus 3T Guides, News, & Discussion] ciarpame:
I'm running LOS 16 together with this modded firmware (v 9.0.6) and I'm planning to upgrade to LOS 17.1.

[MENTION=4405529]nvertigo67[/MENTION] what upgrade path do you suggest? Should I stay with this version or do you suggest to install the official firmware?

A question about the non-alipay flavour: does the linked version suffer from the performance problems you mentioned in another thread?

Thanks
[OnePlus 3T Guides, News, & Discussion] :
If you plan to fprmat the userdata partition use the unmodded fw - if you want to avoid formatting the userdata partition stay with the modded one.

Wiping data is still recommended for a major version update.

The lagging is due to ifaa jar is a boot jar and can only be removed at compile time from the rom; if removed at runtime the lagging is the result.
[OnePlus 3T Guides, News, & Discussion] ciarpame:
I'm not sure to understand

Here https://xdaforums.com/oneplus-3/how-to/guide-deblob-alipay-ifaa-tencent-soter-t4064893 there a is a script to remove alipay&C references from the ROM together with your contribution to fix the lag issue.

Is your non-alipay firmware an alternative to this script or should your firmware be used only together with an accordingly modified ROM in order to avoid the lags?

Here https://xdaforums.com/showpost.php?p=82003289&postcount=11 I read the you run "this combination without lag" but I don't get if is a combination of your non-alipay with plain LOS16 or LOS16 with the mentioned fixes at compile time.

Thank you for your help and patience.
[OnePlus 3T Guides, News, & Discussion] :
Again: the lag is due to the rom and doesn't relate to the fw. You can use the alipay/soter free fw with any rom with ifaa/alipay/soter. If you want a ifaa/alipay/soter free rom use such rom (nlos or hardened los) because this has to be done at compile time. If you want to remove ifaa/alipay/soter at runtime consult the other thread. You can't remove the ifaa jar w/o lagging.
[OnePlus 3T Guides, News, & Discussion] :
Op - update

I've made two minor chanhes to OP.

Installation instructions for OOS has this line changed:

From:

flash official twrp-3.3.1-0 and reboot to recovery (you can skip this, if you already use twtp-3.3.1-0, of course)

To:

flash official twrp-3.3.1-0 and reboot to recovery (you can skip this, if you already use twtp-3.3.1-0, of course - later twrp versions may also work, but twrp-3.3.1-0 has proofed to work)

Installation instructions for custom roms:

From:

flash official twrp-3.3.1-0 and reboot to recovery (you can skip this, if you already use twtp-3.3.1-0, of course)

To:

flash the twrp, recommended for the custom rom you are going to use
[OnePlus 3T Guides, News, & Discussion] :
Just to avoid misunderstandimgs, misconcepts and confusion.

Rom and firmware aren't the same. Modem is part of the firmware (modem and firmware is like apples and fruit; apples are part of fruit like modem is part of the firmware). Rom and firmware can't be put in the same flashable zip for unified rom zips, of course (firmware differ for op3 and op3t).

Firmware consits of this partitions (device dependent; different packages for op3 and op3t are needed):

oem_stanvbk

cmnlib64

cmnlib

hyp

pmic

tz

mdtp

aboot

devcfg

keymaster

xbl

rpm

LOGO

modem

dsp

bluetooth

The (unified custom) rom consists of these partitions:

boot

system

Non-unified roms (like oos) ship different packages fpr op3 and op3t, so the firmware can be included in these flashable zips. Unfied roms (same flashable zip for op3 and op3t) can't be shipped with firmware included as explained above.
[OnePlus 3T Guides, News, & Discussion] Primokorn:
How to know if I have 9.0.4 or 9.0.6 firmware? My basedband: MPSS.TH.2.0.c1.9-00102-M8996FAAAANAZM-1.197095.1.198697.1

Same question about the bootloader.

Androis system info apps mentions "unknown" as for the bootloader version... No version number when booting in the bootloader...

EDIT: just found the information in OP for the bootloader. Actually I didn't find the key word "version" so I posted... My bad!
[OnePlus 3T Guides, News, & Discussion] BillGoss:
You can check by looking at the timestamp in the modem partition (sde21) which is mounted as /system/vendor/firmware_mnt.

You can see the version name of various modules and the firmware release date in verinfo/ver_info.txt.

These are some of the ones for the OnePlus 3T:

9.0.5 timestamp: 2019-07-31 19:47:38

9.0.6 timestamp: 2019-11-04 21:25:29

Also, try searching this thread for firmware_mnt
[OnePlus 3T Guides, News, & Discussion] :
This is not about searching for keywords, it's about reading the OP. Posting a question BEFORE reading the OP of a thread is not very respectfull: there are reasons why I've spended quite some hours on the OP and try to keep it up to date.
[OnePlus 3T Guides, News, & Discussion] Primokorn:
I know I know... I'm on XDA for years and I (very) often read OP and follow the rules.

Unfortunately there are only 24 hours per day. Luckily searching such an information is definitely not my top priority.
[OnePlus 3T Guides, News, & Discussion] Xianno:
Still confused

Hi guys! I read OP multiple times but I'm still a little confused and don't want my data wiped. :/ Can you please help me out?

Reason why I'm here: after getting VoLTE and VoWifi to work with PDC I encountered a strange Bluetooth issue. I'm having no sound with Bluetooth during calls. Everything else is fine.

After restoring EFS backups, trying a factory reset and other even roms I think it might be a good idea to reset the modem/firmware. My last straw. :)

My situation: I'm on LineageOS 17.1, device is not encrypted (if twrp doesn't ask you for a PW that's the case right?), bootloader is unlocked, I'm on firmware 9.0.6 (checked with timestamp because fastboot doesn't show), full selinux support is present

Will my data be wiped if I flash your zips?
[OnePlus 3T Guides, News, & Discussion] :
Wrong. No boot passphrase doesn't mean you are unencrypted.

E.g.: https://xdaforums.com/oneplus-3/one...h-recovery-t3742894/post79471558#post79471558

You need to check in the running rom or in the twrp log.

First of all: don't flash my zips - just flash ONE single zip.

I can only repeat the information from the OP: if your bl is unlocked AND data is encrypted AND you switch tne bl from 5.x to 9.x (or vice versa) you will loose your data. If your bl is already 9.x chose a zip with 9.x bl and your data is safe.
[OnePlus 3T Guides, News, & Discussion] metroidnemesis13:
Too bad I didn't see the OP's thread first. Managed to lose access to my internal storage (don't give a damn about data partition).

Sounds like I'm hosed?

https://xdaforums.com/oneplus-3t/help/advanced-advice-internal-storage-t4163581