yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T Guides, News, & Discussion] armagedon06788@gmail.com:
New Oxygen OS 9.0.3 Update (Bug Fix) for the OnePlus 3 and 3T

Changelog

Bug Fix

• Fixed issue of parallel WhatsApp can't login

System

• Updated system to Android™ 9 Pie™

• Brand new UI for Android Pie

• Updated Android security patch to 2019.4

• General bug fixes and improvements

Do Not Disturb mode

• You can now customize the time range in the new Do Not Disturb mode

New Gaming mode 3.0

• Supported displaying text content of the heads up notifications

• Added notification for 3rd party calls

Phone

• Dialer now supports Google Duo

Camera

• Supports Google Lens to provide you with powerful image recognition experience

Official link: https://otafsg1.h2os.com/patch/amaz..._28_OTA_083_all_1905250211_59a0293f9d252b.zip
[OnePlus 3T Guides, News, & Discussion] abhatia1435:
OxygenOS 9.0.3 update is up!

Download Links:

Official:https://otafsg1.h2os.com/patch/amaz..._28_OTA_083_all_1905250211_59a0293f9d252b.zip

G-Drive mirror:https://drive.google.com/uc?id=15qFgMB6DK7YOw82Zh-TzkxAyIZ67ub38&export=download
[OnePlus 3T Guides, News, & Discussion] votz11:
[MENTION=4954690]Siddk007[/MENTION] seems that 9.02 + 19.3magisk + last HolyDragon kernel for OOS work without probs until now, I'm on it , try it..
[OnePlus 3T Guides, News, & Discussion] Some_Random_Username:
Mirrored on AFH: https://www.androidfilehost.com/?fid=6006931924117890145

MD5: e404e142ad5d0b77d1a67a7dec6baf3b
[OnePlus 3T Guides, News, & Discussion] ManuelR9:
Hello! Someone has already tried it?
[OnePlus 3T Guides, News, & Discussion] Jay_1212:
How to flash this zip ? right now i m on sky dragon os please anyone can help me ?
[OnePlus 3T Guides, News, & Discussion] :
Whats wrong with OP's directions? https://xdaforums.com/showpost.php?p=75026509&postcount=3

Please honor xda rule #1: https://xdaforums.com/announcement.php?a=81
[OnePlus 3T Guides, News, & Discussion] Sudhangshu:
Hey guys i need to know how can i downgrade my oneplus 3t from oos 9.0.3 to 9.0.2, im on stock rom with locked bootloader and no root no custom recovery. Thanks a lot in advance.
[OnePlus 3T Guides, News, & Discussion] immi803:
Dirty flash of 9.0.3 over 9.0.2 goes fine? Anyone?
[OnePlus 3T Guides, News, & Discussion] Sudhangshu:
Yeah no problem, btw I'm totally stock, hope you get it...
[OnePlus 3T Guides, News, & Discussion] Rebel_00XCV:
Can I flash OS 9.0.3 over 9.0.2 without losing my data?

Unlocked bootloader, TWRP, rooted with magisk.

Edit: Successfully updated with TWRP.
[OnePlus 3T Guides, News, & Discussion] xclub_101:
I am a little surprised since the bootloader has changed again, and last time to have everything fine in TWRP the older (5.08 I believe) bootloader was needed as a separate firmware package?
[OnePlus 3T Guides, News, & Discussion] Rootax:
Here I was on 9.0.2 with the 5.0.8 package that allow the upgrade without losing everything.

I upgraded to 9.0.3 by flashing the rom, and then the 5.0.8 package again (then twrp again, magisk, blablabla). If I didn't, I'm pretty sure the bug causing a full format from 508 to 902 would have happened...
[OnePlus 3T Guides, News, & Discussion] Siddk007:
OP updated. Let me know if any changes are required with installation steps for this new OOS 9.0.3
[OnePlus 3T Guides, News, & Discussion] xclub_101:
My feeling exactly!

I am however curious if we might not want a new package with 5.08 bootloader but with some of the other firmware that might have been updated in 9.03 (modem maybe?)
[OnePlus 3T Guides, News, & Discussion] Rootax:
In a perfect world yes, we should take the firmware from the 9.0.3 rom and make this package again. I didn't, and it's still working great. I don't know if they changed anything at the firmware level with this update...
[OnePlus 3T Guides, News, & Discussion] :
All partition images of fw (but RADIO/static_nvbk.bin) partitions have changed:

git diff 9.0.2 9.0.3 firmware-update/ RADIO/
diff --git a/firmware-update/BTFM.bin b/firmware-update/BTFM.bin
index 84beba93..a75db126 100644
Binary files a/firmware-update/BTFM.bin and b/firmware-update/BTFM.bin differ
diff --git a/firmware-update/NON-HLOS.bin b/firmware-update/NON-HLOS.bin
index 1eb56f88..7b8ded82 100644
Binary files a/firmware-update/NON-HLOS.bin and b/firmware-update/NON-HLOS.bin differ
diff --git a/firmware-update/cmnlib.mbn b/firmware-update/cmnlib.mbn
index e759102f..740a0478 100644
Binary files a/firmware-update/cmnlib.mbn and b/firmware-update/cmnlib.mbn differ
diff --git a/firmware-update/cmnlib64.mbn b/firmware-update/cmnlib64.mbn
index a2fd656c..256c1eaf 100644
Binary files a/firmware-update/cmnlib64.mbn and b/firmware-update/cmnlib64.mbn differ
diff --git a/firmware-update/devcfg.mbn b/firmware-update/devcfg.mbn
index 5855e8d2..124f6cb5 100644
Binary files a/firmware-update/devcfg.mbn and b/firmware-update/devcfg.mbn differ
diff --git a/firmware-update/emmc_appsboot.mbn b/firmware-update/emmc_appsboot.mbn
index c0c8b170..98460cb5 100644
Binary files a/firmware-update/emmc_appsboot.mbn and b/firmware-update/emmc_appsboot.mbn differ
diff --git a/firmware-update/hyp.mbn b/firmware-update/hyp.mbn
index 604802ea..46861424 100644
Binary files a/firmware-update/hyp.mbn and b/firmware-update/hyp.mbn differ
diff --git a/firmware-update/keymaster.mbn b/firmware-update/keymaster.mbn
index 86fc07b0..6f56fa42 100644
Binary files a/firmware-update/keymaster.mbn and b/firmware-update/keymaster.mbn differ
diff --git a/firmware-update/pmic.elf b/firmware-update/pmic.elf
index 13ce097b..98e3814e 100644
Binary files a/firmware-update/pmic.elf and b/firmware-update/pmic.elf differ
diff --git a/firmware-update/rpm.mbn b/firmware-update/rpm.mbn
index 01ae9a4a..f7a58c5e 100644
Binary files a/firmware-update/rpm.mbn and b/firmware-update/rpm.mbn differ
diff --git a/firmware-update/tz.mbn b/firmware-update/tz.mbn
index edaca535..2ef84924 100644
Binary files a/firmware-update/tz.mbn and b/firmware-update/tz.mbn differ
diff --git a/firmware-update/xbl.elf b/firmware-update/xbl.elf
index 5e43d921..cd7dab31 100644
Binary files a/firmware-update/xbl.elf and b/firmware-update/xbl.elf differ

For the modded 9.0.3 fw package see: https://xdaforums.com/oneplus-3t/how-to/firmware-beta-10-t3631166/post79690946#post79690946

BTW: let's discuss fw-only tooics in the fw thread: https://xdaforums.com/oneplus-3t/how-to/firmware-beta-10-t3631166
[OnePlus 3T Guides, News, & Discussion] bmwbasti:
Followed this experience and got stuck with "corrupted data"...

I went from 5.0.8 to 9.0.2 with the modded FW and then went straight to 9.0.3 as nobody mentioned

that the modded FW package has to be used afterwards.

I should have known it but (as it is now) my data is completely gone, but worse, i can`t get any OOS to run on my device anymore :(

Perhaps somebody can help me.

OOS prompted me to format data as it is corrupted.

I didn´t want to do this, so i went back to TWRP but i couldn`t decrypt my data anymore.

So i restarted the phone once again and let OOS format data when it was prompted.

Afterwards i wanted to immediately restore my TWRP backup, which i took before.

TWRP showed a message, that my backup was taken with f2fs filesystem while now it`s used ext4 and the restored backup won`t

boot that way.

So i changed filesystem in TWRP to f2fs again (i think OOS has formated and changed the filesystem to ext4) and wanted to restore my TWRP

backup. It´s gone through succesfully but the phone won´t boot, the OnePlus logo is shown and the phone goes straight to bootloader.

So i decided to try, if i can flash and run OOS 9.0.3 directly but this doesn`t work either.

I formated data several times now , and flashed OOS 9.0.3, but the phone stays for half an hour in "spin the two points" screen.

Please help me to get my phone working again :(

PS.: I´m using TWRP 3.3.0.1 if this matters. My bootloader is unlocked and i`m comming from OOS 5.0.8 respectively OOS 9.0.2 to which the update

from 5.0.8 with modded FW package went flawlessly...
[OnePlus 3T Guides, News, & Discussion] reinipic:
Maybe you should add the procedere for dirty flashing.

When you have a running 9.0.2 Rom, wipe cache, dalvik cache, flash Rom 9.0.3, flash magisk and reboot. Reinstall TWRP (because stock recovery is running). Finished. Works perfekt for me - no problems and runs like hell.

Greets, reinipic

P.s. rooted and unlocked Bl.
[OnePlus 3T Guides, News, & Discussion] :
Read my explenation on how and why I've made the modded fw: the issue with the need of reformatting is due to an updated bootloader and keymaster. The modded fw keeps the 5.0.8 bootloader and keymaster to avoid this. As soon as the 5.0.8 bootloader and keymaster is replaced by the bootloader and keymaster from >=9.0.0, you'll run into the reformatting issue.

The last sentence should be selfexplaining, if you've read my original posting.

Rollback: flash the exact fw you've used before (in your case modded 9.0.2) and restore your nandroid. If you have no nandroid, flash 9.0.2 rom, followed by modded 9.0.2 fw. Check if data can be decrypted again. If so, flash 9.0.3 rom followed by 9.0.3 modded fw.

You don't need to have access to userdata (to follow above steps), if you place rom and modded fw (see above) on an external usb mass storage device, or use sideloading in twrp.

I guess you are using twrp >=3.3.0-0. The system restore is known to be broken (see twrp thread for details). Either backup/restore system as image, or reflash the rom build you've taken the nandroid from (followed by the modded fw).

This is fs independent. I really guess it's the well known 3.3.x-x system restore bug.

In twrp:

format data (this will give you userdata with ext4)

change fs to f2fs

reboot to twrp

if you have your last nandroid on external mass storage device:

clean flash 9.0.2 rom followed by modded 9.0.2

boot to system (nomneed for setup; only needed to get back encryption - takes some time on first boof)

when the first time setup starts, reboot to twrp (switch off, and power on with vol- and power)

restore your nandroid

(dirty) flash 9.0.2 rom again

flash modded 9.0.2 fw

reboot to system (if it works now: reboot to twrp, flash 9.0.3 rrom followed by modded 9.0.3 fw)

if you have no nandroid:

clean flash 9.0.3 rom

reboot to system (will take some time, since encryption is done while first booting)
[OnePlus 3T Guides, News, & Discussion] bmwbasti:
Hi nvertigo67,

thanks for your help.

But sadly i´ve done (most) of this but my 3T won`t come back to an usable state :(

And to the time i upgraded from 9.0.2 to 9.0.3 there didn't exist a posting with a modded

fw so i trusted the the one that pointed that he just flashed fw and magisk afterwards and it worked :(

Short form of what i did: Took a nandroid (with 5.0.8), updated to 9.0.2 fw and flashed your modded 9.0.2 fw afterwards (no problems here), the phone booted well to 9.0.2,

downloaded the 9.0.3 fw and flashed it in TWRP, flashed Magisk 19.3 afterwards, wiped Dalvik and cache , went into decryption error afterwards, tried to get back to TWRP, got the error message that

userdata can`t be decrypted, booted back to OOS and hit the "format" button, that was showed by OOS.

And now nothing works.

My data is totally gone (as i wiped the device several times by now), that´s really bad for shure but the phine just simply won`t boot anymore :(

I have done your "in twrp" steps now several times but my phone stucks for 31 minutes with the swirling points....

I read that it´s somehow possible to restore apps + data from an nandroid with Titanium backup, so this would be some kind of good again,

but even for that i have to have a runnig device and it seems as if my 3T won´t get to that status anymore and i don´t know why.

Does system have to stay ext4?

And no, i´m really using TWRP 3.3.0.1 if it matters ;)
[OnePlus 3T Guides, News, & Discussion] dcop7:
Hi,

I'm trying to understand the need of the modded fw. For what I understand it is because people have unlocked bootloader and encripted. If the bootloader is unlocked, flashing 5.0.8 or clean flash 9.0.2, booting it will ask to format everything (oneplus created the requirement that in order to update from oreo to pie the bootloader needs to be locked? I saw that in the community build this is true, but not in stable version)?

If anyone clean flash straight to 9.0.2 without restoring anything with an unlocked bootloader, they are good to go without any modded fw? Even updating for future versions (like 9.0.3)?
[OnePlus 3T Guides, News, & Discussion] :
Read my originalmposting on modded fw.

BTW: I made an error with the modded 9.0.3 fw. It's fixed now. Redownload.
[OnePlus 3T Guides, News, & Discussion] dcop7:
This one?

I did read that before my first post. What I understand, this only applies the people wanted to flash 5.0.8 to community beta because of the precondition that the bootloader should be locked. But what about stable? What exactly are the conditions that this modded fw is needed?
[OnePlus 3T Guides, News, & Discussion] :
No.

If you want to avoid reformating and reencrypting, you need to keep 5.0.8 bootloader and keymaster. That's all.

9.0.2 is not community beta!

Also this is not only for 5.0.8 fw -> 9.x.x, but in every case you want to keep the 5.0.8 bootloader and keymaster. Ergo if you are on 5.0.8 fw, or modded 9.0.1 (community beta) or modded 9.0.2 fw and want to keep 5.0.8 bootloader and keymaster you need the modded 9.0.3 fw.
[OnePlus 3T Guides, News, & Discussion] bmwbasti:
I´m really really confused now.

No matter what i do, i can`t get any OOS version to run on my 3t after my failed update to OOS 9.0.3.

But Lineage gets installed without any problems.
[OnePlus 3T Guides, News, & Discussion] Sudhangshu:
Guys is there a way to switch back to previous oos build,....?
[OnePlus 3T Guides, News, & Discussion] ParallaxY:
Is your app permission page look like this ? I mean it white and have a teal accent color even though i'm using dark mode on my OOS 9.0.2
[OnePlus 3T Guides, News, & Discussion] dcop7:
So, if I would like to stay encrypted, I don't need this. I have unlocked bootloader and I'm encrypted. I've clean flash 9.0.2 without problems. So, for what I understand, I don't need the modded fw. Thanks.
[OnePlus 3T Guides, News, & Discussion] bmwbasti:
Guys, i don`t want to hurry, or be rude or something, but i really need urgently help :(

It´s not possible to install any version of OOS anymore and i don`t know why and i don`t know what to do.

It´s not even poosible to restore a nandroid that i took yesterday...
[OnePlus 3T Guides, News, & Discussion] Rootax:
Sorry about that :/ If what I did doesn't work, I don't know what esle you can try.
[OnePlus 3T Guides, News, & Discussion] :
That's the problem: you did "most" of that. As long as you doesn't have tried exactly that, you can't say it's not working. I suggest you try word by word exactly either [MENTION=3764254]Rootax[/MENTION] directions or my directions. It's important to keep the order of the steps and not leaving one step out.

You've said you can install plain los. Can you encrypt with plain los (with 5.0.8 fw, of course)? Have you ever formated with twrp 3.2.3-0? To me this looks like the missing encryption footer issue, when there is no space reserved on userdata for the encryption footer the initial encryption of oos fails, which gives you the endless bootloop.

EDIT: If everything else fails, you can always use the unbrick tool: https://xdaforums.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
[OnePlus 3T Guides, News, & Discussion] beardymarrow:
I also used this procedure successfully (from rooted 9.0.2 with unlocked bootloader), but I didn't reflash twrp. As long as you don't reboot between installing 9.0.3 and magisk it stays.
[OnePlus 3T Guides, News, & Discussion] reinipic:
You are right! I forgot to say, that I rebooted between installing;) Anyway, fine when it works for you too.

Greets, reinipic
[OnePlus 3T Guides, News, & Discussion] bmwbasti:
You´re definitely wrong ;)

I followed your steps, and Rootax´s steps, EXACTLY...

And that several times but it sadly helps nothing :(

The only thing, i didn`t do until now, isto try an older TWRP version as you mentioned now.

But i did all other things step by step exactly and nothing.

Way the worst is that not even restoring my nandroid works. I know, that almost all of my data is gone, but at least getting back appdata would be some kind of

less punishing as there is collected data of (partly) more than six years.

And i have already seen the unbrick tutorial, but for me, as a guy that flashes my device for years, won`t come to my mind, what could be bricked

at my device when LOS (to be honest i don`t know which fw was flashed, but it should be 5.0.8) runs without problem (yes, it`s encrypted).

In the meantime i got OOS 5.0.8 to run again :eek:

I don´t know how it went, but it runs.

But only 5.0.8. Even if 5.0.8 is fully set up, i can`t upgrade to 9.0.2, then the "loadloop" appears again.

What is very strange is that i can`t choose my Google Drive backup from my 3t, when i set it up.

In Google Drive app i can see my 3t backup from yesterday but in setup only a backup of my tablet is shown.

Very strange, i don´t get the problem at all :(
[OnePlus 3T Guides, News, & Discussion] :
If encryption is working on los, the encryption footer is definetly in place. You can forget about the suggestion to use 3.2.3-10.

This is indeed very strange. Maybe some detail which is non-default, like fs on cache... The advantage of the unbrick-tool is, everything is reset to defaults - even those we've forgotten to check.

BTW: did you checked the recovery log (from 9.0.x flash) for strange entries? Did you check the downloaded file?

md5sum for OOS:

9.0.2: b4d333c8bb1608ed4b26fd2b2213619b OnePlus3TOxygen_28_OTA_082_all_1905110010_f09a2bfe8e361d.zip

9.0.3: e404e142ad5d0b77d1a67a7dec6baf3b OnePlus3TOxygen_28_OTA_083_all_1905250211_59a0293f9d252b.zip
[OnePlus 3T Guides, News, & Discussion] bmwbasti:
Could f2fs in Cache cause that kind of problems?

As another User wrote meine at night top check this.

To be honest, i never looked for the filesystem on cache as i never changed something there.

So ist should be like system and cache ext4 and data f2fs?

Edit: But now it's strange, that encryption in OOS works (i have to put in my code at boot) butin TWRP data can't be decrypted anymore.

Even putting in the correct code gives an "unable to mount" as result.
[OnePlus 3T Guides, News, & Discussion] Rootax:
Yeah I don't believe the stock oos kernel supports cache being f2fs. Only /data should be f2fs
[OnePlus 3T Guides, News, & Discussion] :
OOS 9 requires ext4 on cache:

git checkout 9.0.3
HEAD ist jetzt bei ba4d9ff9 OxygenOS 9.0.3.
grep '/cache' $(find * -name \*fstab\*)
system/vendor/etc/fstab.qcom:/dev/block/bootdevice/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1 wait

Maybe you can add an f2fs entry to system/vendor/etc/fstab.qcom, but using f2fs on cache slows down things (you can test on los i.e.).

OOS shipped stock config (also on 5.x, 4.x and 3.x) is/has been system & cache on ext4 and data on f2fs. I'm really surprised 5.x is running on f2fs on cache for you, but this wasn't intended by the OnePlus devs.
[OnePlus 3T Guides, News, & Discussion] koentdm:
I keep getting an bootloop, followed the exact instructions.
[OnePlus 3T Guides, News, & Discussion] sandeep_kumar:
Do not miss any step as in OP.

1) remember to format the phone in TWRP

2)reboot back to TWRP

3)Flash the ROM and Magisk simulaneously by selecting add more zip option.

4)Wipe your caches at last

5)Reboot

I did not find any bootloops in this process, you must not have too.
[OnePlus 3T Guides, News, & Discussion] bmwbasti:
I won`t add or delete something in files that i don`t even know the meaning off ;)

So now i formated everything as i should (system and cache ext4, data f2fs) and am trying to restore my nandroid to actually get my

appdata back.

But it doesn`t look good. At least i can`t remember that a restored OOS needs 15 minutes or more to boot up :(

OK, after 25 minutes of booting the device is powerign up but it seems as if i made the noob error and forgot to remove password/fingerprint before

making the backup in TWRP :(

And (i had this one time before) my old password seems not to be legit anymore.

I remember i could delete some files in TWRP filemanager to remove password and fingerprint but i don`t get asked for my pasword to decrypt data in TWRP and can`t mount data...

Damn, it seems as if everything is goin wrong :( :( :(
[OnePlus 3T Guides, News, & Discussion] mikica023:
I would like to root my 3t locked bootloader, stock recovery, 9.0.3. Is this procedure good, if its not please correct me?

1. unlock bootloader

2. flash twrp 3.3.1.0

3. from twrp flash magisk 19.3

4.reboot

Do I need to delete cache / dalvik somewhere? Do I need to format partitions? Thanks in advance for help.
[OnePlus 3T Guides, News, & Discussion] :
Before restoring anything, try getting 9.0.3 booting first. Don't do the secomd step before the first one.

If you can't get 9.0.3 working in the first place, don't restore any data.

That being said, if you can't get 9.0.3 up and running, use the unbrick tool to get your device stock again. The unbrick tool undoes all the little changes you've done to the device and don't remember or that you don't consider to need undoing (like fs on cache).

After 9.0.3 is up and running, you can take actions to get userdata restored.
[OnePlus 3T Guides, News, & Discussion] bmwbasti:
Ok, so i´ll try 9.0.3.

I really thought that there was no chance of restoring appdata that was backuped with 5.0.8.

EDIT: 9.0.3 up and running :) :) :)
[OnePlus 3T Guides, News, & Discussion] :
I've hoped that after fixing cache. Happy it's working for you, too, now!

I'm a friend of clean flashing on major version bumbs. Some side effects of migrating may show up later - some times very late, like on the next migration.

Anyway: some backup tools (for titanium I know for sure, but others proberbly too) support reading twrp backups and restoring single apps (a group of or all) with data. I'd recommend restoring them (the most important) one by one with a reboot inbetween, to check if one of them is causing the endless boot.
[OnePlus 3T Guides, News, & Discussion] bmwbasti:
Many thx for your and Rootax´s help, again :)

I´ve read that Titanium is capable of restorung apps from an nandroid and i´ve tried it yesterday, when i got 5.0.8 running again.

It shows all apps and it´s possible to choose them for restoration, but then Titanium only says "restore sucessfull" but nothing gets restored :(
[OnePlus 3T Guides, News, & Discussion] :
I haven't used that function for years... Maybe you'll find something usefull here: https://xdaforums.com/tags.php?tag=titanium+backup Or you may contact the titanium dev directly: https://matrixrewriter.com/android/ or getsupport@titaniumtrack.com

EDIT: to restore the userdata completely with twrp it's important to use the same twrp version, which was used to create the nandroid. In the twrp thread are reports on failed restores with 3.3.x-x for 3.2.3-10 nandroids - perhaps...
[OnePlus 3T Guides, News, & Discussion] DarkSJ1998:
I've been using TitaniumBackup Pro since years & have noticed one thing. Yes it is capable of restoring app data from Nandroid Backups, but not all of them. It can't restore anything from a compressed Nandroid Backup. Moreover, when I tried restoring it, it failed to restore data for some apps... But most of the app data could be retrieved.

And also, you need to install the app manually & then you can restore data only using TitaniumBackup & it will work. TitaniumBackup isn't able to install the app as well as data both at the same time from a Nandroid Backup, atleast that's what I've observed in these 5-6 years of experience with TitaniumBackup ;)
[OnePlus 3T Guides, News, & Discussion] bmwbasti:
Guys, thank you all, you are simply the best :)
[OnePlus 3T Guides, News, & Discussion] isitmeor:
any way/advice to go back to 5.x

just 2 hours on screen is a no go for me I am a bit disappointed to say the least
[OnePlus 3T Guides, News, & Discussion] Sudhangshu:
I have been asking the same thing for quite some days and no one aswered it hope they listens yours and answers it so we both get it.