yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T Guides, News, & Discussion] GoMati:
It's oxygenos-9.0.6-no-alipay-firmware-3T.zip, shall I use another one?

EDIT1: used oxygenos-9.0.6-bl-km-5.0.8-no-alipay-firmware-3T.zip, still no bueno

EDIT: just to add: if I go back to 8.0, then everything shows 128gb just fine!
[OnePlus 3T Guides, News, & Discussion] pedritopl:
Happened to me as well few years ago...

I'm not 100% sure, but AFAIR fix could have been to format/check data partition in TWRP afterwards.
[OnePlus 3T Guides, News, & Discussion] satanas17:
Something maybe wrong with the supposed 3T file, don't know more...

Maybe trying another source...
[OnePlus 3T Guides, News, & Discussion] GoMati:
How can I do that? Just for future reference :)

By the way: oxygenos-9.0.6-bl-km-5.0.8-no-alipay-firmware-3T.zip seemed to work for some reason - I installed LineageOS afterwards without problems. Maybe the other one is problematic? ¯\_(ツ)_/¯

Thanks for all help, guys!
[OnePlus 3T Guides, News, & Discussion] Xydia:
Hi BillGoss,

I don't see any vendor folder under /system.

Neither does the OP tips below:

First `/system/vendor` doesn't exist. I only have `/system/usr`.

The two grep commands return nothing. Note that it should be `cut -d ' '` with one space not two or else there's an error:

cut: the delimiter must be a single character
Try 'cut --help' for more information.

Second the dd command returns:

adb shell dd if=/dev/block/bootdevice/by-name/aboot | strings | grep "compiled at"
LK compiled at Nov 4 2019 21:21:15
16384+0 records in
16384+0 records out
8388608 bytes transferred in 0.296 secs (28339891 bytes/sec)

UPDATE 1:

I successfully ran `cat ...verinfo.txt` after restarting from TWRP to LineageOS and running `adb root` and `adb shell <first command listed above>`.

Second question, is the firmware the value listed under "modem"?

{
"Image_Build_IDs": {
"adsp": "ADSP.8996.2.7.1.c3-00009-00121-1.195481.2",
"apps": "LA.UM.7.5.r1-04000-8x96.0-1.194866.1",
"boot": "BOOT.XF.1.0-00306-M8996LZB-1",
"btfm": "BTFM.RM.4.3.c3-00023-QCABTFMSWPZ-1.115618.3",
"common": "MSM8996.LA.2.0.3-00015-STD.PROD-1.194469.1.194866.3",
"cpev2": "CPE.TSF.1.0-00035-W9335AAAAAAAZQ-1",
"glue": "GLUE.MSM8996.2.0-00022-NOOP_TEST-1",
"modem": "MPSS.TH.2.0.c1.9-00102-M8996FAAAANAZM-1.197095.1.198697.1",
"rpm": "RPM.BF.1.6-00153-M8996AAAAANAZR-1",
"slpi": "SLPI.HB.1.0-00310-M8996AZL-1",
"tz": "TZ.BF.4.0.1-00386-M8996AAAAANAZT-1.194469.1.194866.2",
"video": "VIDEO.VE.4.4-00060-PROD-1",
"wapi": "WLAN.ADDON_RM.3.0-00013-CNSS_RMZ_WAPI-1",
"wigig": "WIGIG.SPR.2.1-00032-WIGIGSWZ-1",
"wlan": "WLAN.RM.4.3.c3-00041-QCARMSWPZ-1.118899.1.193442.3"
},
"Metabuild_Info": {
"Meta_Build_ID": "MSM8996.LA.2.0.3-00015-STD.PROD-1.194469.1.194866.3",
"Product_Flavor": "asic",
"Time_Stamp": "2019-11-04 21:25:29"
},
"Version": "1.0"
}

UPDATE 2:

Looks like "2019-11-04 21:25:29" is listed under the JSON path ".Metabuild_Info.Time_Stamp" which corresponds to 9.0.6.

Perfect. I'm all set. Hoping that my firmware is the custom one from the OP.
[OnePlus 3T Guides, News, & Discussion] Xydia:
Hi nvertigo67,

I have some questions relating to upgrading to the latest keymaster and enabling SELinux:

What is the difference between these two binaries?

* https://github.com/nvertigo/firmwar...s-9.0.6-bl-km-5.0.8-no-alipay-firmware-3T.zip

* https://github.com/nvertigo/firmwar...op3t/oxygenos-9.0.6-no-alipay-firmware-3T.zip

What does "bl-km" mean?

I tried to follow your instructions with the non-"bl-km" variant and SELinux is still disabled.

UPDATE 1:

I was able to successfully enable SELinux following your original steps (Plus a few notes). My story:

1. Boot into TWRP and flash https://github.com/nvertigo/firmwar...3t/oxygenos-9.0.6-bl-km-5.0.8-firmware-3T.zip (Sadly I will not retest with No Alipay due to fear!)

2. Reboot into TWRP. Warning! I cannot decrypt some partition!

3. Wipe "Allow system modifications", and format data

4. Reboot into TWRP

5. Flash Lineageos nightly

6. Wipe cache/davlik

7. Reboot into Lineageos system

8. ???

9. Settings app > Privacy > Trust shows SELinux Enforcing!
[OnePlus 3T Guides, News, & Discussion] youkon:
did you find out, what the abbreviation "bl-km" means?

also, I do not understand completely, what changes were made compared to the original firmware, except no-ali, sota
[OnePlus 3T Guides, News, & Discussion] elgab:
bootloader keymaster or something like that

the bl-km could be used to upgrade firmware from inferior version without losing data.

I always prefer clean flashes, or start from pure stock, so i used the zip without that bl-km.
[OnePlus 3T Guides, News, & Discussion] elgab:
It seems @nvertigo67 is gone from github, anyone has some info?

I was just looking for the firmware 3 zip without the chinese blobs, I forgot to archive it myself :(
[OnePlus 3T Guides, News, & Discussion] :
That dpends on your current setup and the target setup you want to have. It also depends on the behaviour of your bootloader: some users have expirienced selinux issues with the 9.0.x bl. See the roms thread for expectable issues with the unmodded fw, to make an educated decission. It's not aboiu what you should flash, but about what you want to flash after considering all options and impacts.
[OnePlus 3T Guides, News, & Discussion] Naudiz:
Atm I see no reason why anyone would want to flash the unmodded FW. It's too dangerous.

I considered trying it yesterday. But after witnessing that a Backup for my whole /data partition takes roughly a full hour (yes, it's quite filled up), I decided, it's not worth the risk to end up with a permissive SELinux. So I stick to modded FW for the time being.

Also all the information about potential problems is way too scattered. You literally have to search through dozens of pages of different rom-threads. It's really no fun dealing with the current FW.
[OnePlus 3T Guides, News, & Discussion] :
In deed, the possible issues are widely spread, the issues themselfs as well as the threads. I you like to make a summary I'll be happy to link it in OP!
[OnePlus 3T Guides, News, & Discussion] ParanormalBat:
Thank you for putting this thread together, finally got the 9.0.4 update running on my 3T, Now I'm just hoping the battery life settles in and that the modded firmware always works for future builds.
[OnePlus 3T Guides, News, & Discussion] :
After trying to put the above in my own words in OP (and ending up in usng your words... ;) ), I've decided to link the above posting in the first paragraph of the OP. I hope this is ok for you.
[OnePlus 3T Guides, News, & Discussion] Dirk:
No problem at all. Glad to help. :)
[OnePlus 3T Guides, News, & Discussion] pijas82:
You are amazing , thanks
[OnePlus 3T Guides, News, & Discussion] brmbjn:
if i want to install magisk without twrp

boot.img using patched boot.

what boot to use ? boot 5.0.8 or 9.0.4 ?
[OnePlus 3T Guides, News, & Discussion] :
What do you mean by "boot"? I've always used magisk with twrp. I don't get the the question.
[OnePlus 3T Guides, News, & Discussion] Immortalis:
It doesn't matter, boot.img is tied to the ROM, not firmware
[OnePlus 3T Guides, News, & Discussion] brmbjn:
so i can use boot.img from 9.0.4 for make boot_patched.img at magisk.
[OnePlus 3T Guides, News, & Discussion] Immortalis:
Firmware has nothing to do with this, you take the boot.img from your ROM.

Why do you make things harder, when you can just flash Magisk zip via TWRP?
[OnePlus 3T Guides, News, & Discussion] :
[MENTION=6511605]brmbjn[/MENTION]: may I kindly remeber you to answer my question and elaborate yours a bit more, please.

I think you are traped by a misconcept. bootloader and boot image are two completely different animals. Since bootloader as well as boot image are available for 5.0.8 and for 9.0.x your question is not understandable. Every additional (guessed) answer just increases the probability of missunderstanding.
[OnePlus 3T Guides, News, & Discussion] jesrani:
Hi, maybe this is not the correct thread to ask this question but I got good support from OP earlier hence asking here:

I have OnePlus3T and am currently on OOs9.0.4 with unlocked bootloader, rooted with Magisk and encrypted with PIN.

I was earlier on 5.0.4 and dirty flashed to 9.0.3 and then to 9.0.4 and hence I have modified firmware. Though I am very happy with OOs I am having some battery drain and think a clean flash is better. Hence thought of trying RR with Pico OpenGApps rather than OOs. Hopefully it will work for all my requirements. I want to know the procedure for clean install of RR on this modified 9.0.4 firmware.

I will restore my user apps and data with TiB. I regularly use Bluetooth tethering and hope that will work in RR also.

If anyone has a better opinion about another ROM other than RR please do let me know.
[OnePlus 3T Guides, News, & Discussion] :
Just follow the first time installation instructions of the rom you want to flash.

If you ask me for a rom recommendation, I would opt for NLOS, of course. I'm using NLOS as daily driver since two and a half years - currently with Magisk-19.3.
[OnePlus 3T Guides, News, & Discussion] :
Did you read the posting of [MENTION=1763460]Dirk[/MENTION] I've quoted? Learn to quote, please.

EDIT: (lost while cut'n'paste from otner thread)

Yes, you can use the modded fw without encryption. Originally I made the modded fw to avoid the need of reformating and reencrypting, but real life has shown that there are more issues this package can workaround.
[OnePlus 3T Guides, News, & Discussion] reliant_turbo:
If I want to remain rooted do I flash magisk between steps 4-5 or 5-6 in the OxygenOS instructions in the original post? Or do I get it all installed and then reboot to TWRP and then flash magisk?

I’m thinking it doesn’t matter but I figured I’d ask before I goof up my phone.

Thanks

Brian
[OnePlus 3T Guides, News, & Discussion] :
I would go for between 5-6, but I completely agree, that is shouldn't make any difference at all.
[OnePlus 3T Guides, News, & Discussion] reliant_turbo:
Thanks.

Brian
[OnePlus 3T Guides, News, & Discussion] reliant_turbo:
Install went without a hitch. On pie now.

I did have my root directory 100% full though after the install so adaway didn't have room to write the hosts file. So I deleted Google play videos, Google play music, (don't use them) and maps and duo, rebooted and then reinstalled maps and duo as user apps. Now I have 100mb free in root for any files my root apps need to install.

Thanks,

Brian
[OnePlus 3T Guides, News, & Discussion] :
I'm happy it worked as you've expected.

One word on the partitions and filesystems:

You've removed files from the system partition mounted on /system. The root filesystem is a loop fs (similar to a ram disk) populated from a cpio archive in the boot partition on each reboot (changes wouldn't persist a reboog).

Though this is from nlos, the partitioning scheme is the same:

adb shell grep -e rootfs -e by-name/system /proc/mounts
rootfs / rootfs ro,seclabel,size=2840892k,nr_inodes=710223 0 0
/dev/block/platform/soc/624000.ufshc/by-name/system /system ext4 ro,seclabel,relatime,discard 0 0
[OnePlus 3T Guides, News, & Discussion] reliant_turbo:
So are you saying apks in system/app/ should return after a reboot because they didn't. They are gone.

Brian
[OnePlus 3T Guides, News, & Discussion] :
Please see my previous posting: /system is a "real" partition; / (aka rootfs) is a cpio archieve restored at every boot. apps are in tne system partition not in the root partition. Your idea apps are sitting in the rootfs is just wrong.
[OnePlus 3T Guides, News, & Discussion] reliant_turbo:
Ok.

So that is why the app is still installed on the phone even though I deleted something from somewhere that gave me enough space to allow adaway to be enabled?

I don't totally understand.

So the "system" folder in my screenshots is different from the system partition?

Brian
[OnePlus 3T Guides, News, & Discussion] :
One last time:

the rootfs (/) is a ramdisk populated on boot from an cpio archive. If you remount rw touch a new file and delete i.e. the file sepolicy and finally reboot the new file is gone and the removed file is present again, because THE ROOTFS IS RESTORED EACH TIME THE DEVICE STARTS UP.

The filesystem mounted on /system is a normal ext4 filesystem, which is actually mounted ro. If you remount /system rw, touch a new file delete i.e. the directory /system/app/YouTube/ and reboot, Youtube is still gone and the new file is still present.

If you have not enough space to add to /system/etc/hosts you need to delete from /system, lile Yuotube in the above example.

If you've "deleted something from somewhere that gave me enough space to allow adaway to be enabled?" I can't tell you, something is deleted from somewhere. Your question is not detailed enough to mean anything.
[OnePlus 3T Guides, News, & Discussion] reliant_turbo:
If you say the same thing over and over the same way and I don't understand completely then I'll just have to look for other examples online to get my mind around the concept.

I deleted the apks from the first 4 folders in my 1st

screenshot. My second screenshot shows the APK for duo being missing.

Let's just let this end because I'm not making the correlation between the ramdisk and the physical system directory and why you brought it up and how I incorrectly defined what I did..... And we are bogging down your otherwise positive thread.

I'll use your examples to look up something more visual (not just textual) of what's going on that I'm not getting.

Thanks

Brian
[OnePlus 3T Guides, News, & Discussion] :
There is no correlation between root filesystem and system filesystem. You mixed that up, when stating you removed apps from the root filesystem.You can't remove apps from the root filesystem, because they live in the system filesystem.

A pathname is a pathname. /proc/mounts shows you which filesystems are mounted to which pathnames. This is textual information...
[OnePlus 3T Guides, News, & Discussion] Perceval from Hyrule:
Thanks very much, I updated easily my modem firmware (using the latest TWRP of course) with no loss in order to install latest LineageOS nightly ("Modem firmware from OxygenOS 9.0.2 or newer stock ROMs is prerequisite to be compatible with this build - Error 7"). I wasn't sure the Error 7 was this one, as it could be the asset file (detecting OP3T and not the OP3... had to edit that several times on previous nightlies).

Just flashed it, wiped caches, it just rebooted fine. Thank you again for your efforts, I do appreciate :)
[OnePlus 3T Guides, News, & Discussion] Sjhingan:
Hi, Running os5.0.8 with TWRP and magisk on op3t, build A3003. Followed your method exactly as described using the modded firmware. Just added flash magisk between steps 5 and 6. However as soon as i try to boot into system the phone automatically reboots into recovery. Any idea what i could have done wrong or what i can double check. THX
[OnePlus 3T Guides, News, & Discussion] :
Though I've thought oxygenos 5.0.8 would run with the modded fw, it's not the setup I've thought of. Use the modded 9.0.4 fw with oxygenos 9.0.4.

If that still fails, skip installing magisk (you can do that later, after checking 9.0.4 is booting with the modded fw).

If you need further assistence please remember to attach recovery logs of flashing oxygenos and the modded fw.
[OnePlus 3T Guides, News, & Discussion] Sjhingan:
So instead of using "oxygenos-9.0.4-bl-km-5.0.8-firmware-3T" i should use a modded 9.0.4 fw? can you please post a link please for that fw? also in your post dated june 30th you posted an update using 5.0.8 fw. shouldnt this work with modded firmware? thx in advance.
[OnePlus 3T Guides, News, & Discussion] :
In your previous posting, you've stated you are running oxygenos 5.0.8 with the modded 9.0.x fw:

Don't do that. Use the plain, unmodded (rom shipped) 5.0.8 fw with oxygenos 5.0.8. Use oxygenos-9.0.4-bl-km-5.0.8-firmware-3T only with oxygenos 9.0.4.
[OnePlus 3T Guides, News, & Discussion] Sjhingan:
I think im not explaining it correctly so i'll try again. Im currently running os 5.0.8 and android 8.0. Trying to update to 9.0.4 using your modded fw. Followed all the steps in your procedure but cant boot into system coz phone automatically reboots into recovery.

To my understanding once i dirty flash 9.0.4 ROM and then flash your modded fw it should work, but not in my case.

Could you maybe list out the steps i need to take similar to how you did in the OP?

Thanks for your patience.

P.S: just noticed that OEM unlock was not checked in dev settings. does that have any effect?
[OnePlus 3T Guides, News, & Discussion] :
OK, that should work.

Pleasd honor:
[OnePlus 3T Guides, News, & Discussion] Sjhingan:
So just to update in case someone faces this issue, didnt install magisk this time and did manage to boot into system. Pie ran smoothly BUT could not boot into TWRP and kept booting into custom recovery. Could only boot into TWRP thru fastboot cmd. So for now back to 5.0.8 unless something better comes along. thx nvertigo!
[OnePlus 3T Guides, News, & Discussion] :
You need to enable oem unlock in dev opts to keep twrp instead of stock recovery. I don't understand "could not boot into TWRP and kept booting into custom recovery". twrp is the custom recovery. What do you mean by "custom recovery" in opposition to twrp?

Is your bootloader locked or unlocked? If it's locked magisk 19.3 and before will fail to boot, because the magisk zip is signing the boot image (not boot loader!!!) with aosp test keys instead of aosp keys. For more information:

https://xdaforums.com/showpost.php?p=79838315&postcount=321

For a hotfix:

https://xdaforums.com/showpost.php?p=79833922&postcount=2737 (flash directly after flashing magisk)

The magisk issue is not related to firmware in any way. If it's not the above, you may want to ask in the magisk thread.
[OnePlus 3T Guides, News, & Discussion] Sjhingan:
OEM unlock enabled, bootloader unlocked. i meant to say cannot boot into TWRP and keep booting to stock recovery. I could only boot into TWRP by fastboot cmd. Will check out the links you posted.
[OnePlus 3T Guides, News, & Discussion] :
If the bootloader is unlocked:

Boot twrp with fastboot. Flash twrp from within the fastboot twrp. Reboot to recovery (should be twrp). Reboot to system. Reboot to recobery (should still be twrp).
[OnePlus 3T Guides, News, & Discussion] Sjhingan:
You seem to be right, the issue is related to Magisk installation. Everything works until Magisk installation. Will search in MAgisk threads. Thx for your help.
[OnePlus 3T Guides, News, & Discussion] DavidXanatos:
For me majisk 18.1 worked just fine
[OnePlus 3T Guides, News, & Discussion] DamienCassou:
Which version is my bootloader

My phone: OnePlus A3003

My system: LineageOS 20190612 and TWRP 3.3.1-0, encrypted

My goal: use OTA updates on LineageOS again

My problem: OTA updating LineageOS fails (it seems to be a common issue)

From what I have read, it seems I have to update the phone's firmware

and it seems this thread is the way to go. The first requirement is:

I don't know what version my bootloader is and I don't know what a

keymaster is. When I reboot my phone to the bootloader, I get:

FASTBOOT MODE
PRODUCT_NAME - msm8996
VARIANT - MTP UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - 1f... (omitted)
SECURE BOOT - enabled
DEVICE STATE - unlocked

As you can see, there is no version attached to the bootloader

entry. Before installing LineageOS, I updated OxygenOS quite a few

times but I don't remember when was the last update. Moreover, I wiped

my phone before switching to LineageOS.

What should I do please?
[OnePlus 3T Guides, News, & Discussion] :
It's twrp, not los: https://xdaforums.com/oneplus-3/one...eplus-3-3t-t3866517/post80009157#post80009157

Use twrp-3.2.3-10 if ota auto-flashing matters for you.

The only way to determine the boptloader's version is to know it. It depends on what fw you've flashed last (remener oos comes with fw included!).

The keymaster partition holds that part of the fw, which is used to do key operations. Key operations are used i.e. for encryption or storing fingerprints.

How should I know, if you don't know what you've done to your device? I suggest a clean flash. Maybe you need to reformat data.

BTW: wiping doesn't effect fw in any way.
[OnePlus 3T Guides, News, & Discussion] brmbjn:
update from 5.0.8 to 9.0.4

with

- 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)

- take a nandroid

- (dirty) flash OxygenOS 9.0.x rom's flashable zip

- without rebooting(!) flash

for Oneplus 3T: oxygenos-9.0.4-bl-km-5.0.8-firmware-3T.zip

for Oneplus 3: oxygenos-9.0.4-bl-km-5.0.8-firmware-3.zip

- without rebooting(!) flash twrp-3.3.1-0 again

- wipe cache and dalvik

- reboot to system and enjoy OxygenOS 9.0.x!

how about from 9.0.4 to 9.0.5 ?
[OnePlus 3T Guides, News, & Discussion] sky321:
There are coming a lot of keymaster changes with the next LOS16 build https://www.lineageoslog.com/16.0/oneplus3

Does this effect our original firmware (oneplus fw 9.0.x) trouble?
[OnePlus 3T Guides, News, & Discussion] :
If you talk of https://review.lineageos.org/q/topic:%22legacy-keymaster1-fix%22, you can just ignore the changes, because we use keymaster 3.

BTW: the bootloader/keymaster trouble relates to firmware (closed source), not to the open source roms.

9.0.5 update: later today, I'm still downloading the two zips. modded fw updated to 9.0.5 as well as OP.
[OnePlus 3T Guides, News, & Discussion] vikd007:
Clean flashed the latest havoc today with 9.05 firmware on op3, fingerprint scanner is broken, selinux is permissive, any solution?
[OnePlus 3T Guides, News, & Discussion] :
Please share the recovery.log of flashimg the fw package and of flashimg the rom after the reboot (copy /sdcard/recovery.log to /sdcrad/recovery.log.fw befote taking the second log of rom flashing). Your issue looks like you are using the stock fw instead of the modded fw.
[OnePlus 3T Guides, News, & Discussion] vikd007:
Correction........ Working fine now and very smooth & stable

---------- Post added at 08:11 PM ---------- Previous post was at 08:09 PM ----------

I actually used nandroid backup after clean flash tht caused the issue
[OnePlus 3T Guides, News, & Discussion] :
I can't understand why people call a setup with a restored nandroid a "clean flash". Clean flashing solves many issies because incompatible apps and settings are removed. Restoring the old setup on a clean flash is obviously no clean flash any more, but (regarding apps and settings) the very same as a dirty flash...

Anyway, I'm happy it's working for you, now.