yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T Guides, News, & Discussion] mike.sanders:
A month ago I acted too fast and flashed the official 9.0.4 firmware when I wanted to update my Resurrection Remix (RR) 7.0.2 custom ROM on my encrypted OP3T and it complained about needing firmware v9.

My data was gone and I had to completely reinstall my phone. By now everything works again (incl. SELinux "enforcing"), but the device is not encrypted.

Today I finally found the time to update my wife's OP3T using the modded 9.0.5-bl-km-5.0.8-firmware and everything worked fine: current RR installed, no data loss, device still encrypted, SELinux "enforcing". So first a big THANK YOU for the modded firmware and the info in this thread.

Now I'd prefer to change my own phone back to encrypted, but am afraid this may give trouble with the official / unmodified firmware.

Can someone tell me if it would be safe to flash the modded 9.0.5-bl-km-5.0.8-firmware-3T.zip over the already installed official 9.0.4 firmware? Or does that make no sense and I might just go ahead and enable encryption with the "official" firmware?

Second question: my daughter also has a OP3T which I bought as a used device a month ago. I first OTA-updated OxygenOS to the latest available version which already included some 9.0.x firmware (don't exactly know which), and only afterwards unlocked / rooted / switched to RR 7.0.2.

Everything looks good and the device is reported as "encrypted" - however, even if I boot to TWRP I am never asked to enter the decryption key but can read files (RR ZIPs etc.) from sdcard?! That's not how it worked on my device and still works on my wife's device so I wonder if my daughter's device really is encrypted?!

Can anyone explain that to me?

Thanks!

- mike
[OnePlus 3T Guides, News, & Discussion] :
If you have no problems with the stock 9.0.x bootloader (i.e. selinux is enforcing, sensors working), I would stay with it.

If you decide to change to the modded fw (i.e. to have the same setup on all three devices), do the encryption AFTER changing to the modded fw.

If you don't use secured boot, the encryption passphrase is set to "default_passsord". The rom as well as twrp know about "default_password" and try to mount the encrypted data partition with "default_password" before bothering with the passphrase dialog.

To enable secured boot set your lockscreen passphrase again, and when asked if the boot process should be passphrase protected answer "yes".
[OnePlus 3T Guides, News, & Discussion] mike.sanders:
Thanks for your answers. I think I understand the situation better now.

Having the same setup on all three devices is indeed what I was looking for but I now believe that it would require too much effort because I would need to re-install at least one device completely (cf. below).

I'll try to sum up the situation and the consequences that follow from it for my three devices. Might be a bit verbose, but I'm still not completely sure about the relevancy of the different factors. I hope somebody might recognize his / her situation and find this helpful.

All three devices are OEM unlocked and have latest available TWRP (3.3.1) on them.

Device 1:

was encrypted when using firmware 5.0.x (flashed by myself)

was updated to modified firmware 9.0.5 from this thread without data loss

is still encrypted and working fine

Should a future ROM (updated Resurrection Remix or whatever) require a newer firmware I need to find a modified version of that firmware with bootloader and keymaster still from firmware 5.0.x. Otherwise - i.e. when flashing stock firmware - data will be gone and the device has to be set up again from scratch.

Device 2:

was encrypted when using stock firmware 9.0.x (installed via OxygenOS OTA update)

is now encrypted and working fine with stock firmware

Should a future ROM (updated Resurrection Remix or whatever) require a newer firmware I probably need to use the then-current stock firmware (but still scan XDA forums beforehand just in case we have a situation again like with the transition from v5.0.x to v9.0.x ;) ).

Device 3:

was encrypted when using firmware 5.0.x

was updated to stock firmware 9.0.4 (flashed by myself) with complete data loss

is now unencrypted but working fine with stock firmware

I can encrypt it again and go ahead using the stock firmware - essentially the same situation for future updates as for device 2.

Or I can flash the modified firmware and afterwards encrypt it. If I encrypt first and then flash the modified firmware, data will be gone and the device has to be set up again from scratch. Then it's essentially the same situation for future updates as for device 1.

For now, the only action I'll take is that on the next RR update on device 3 I will wipe system partion, install RR without Magisk, reboot, encrypt, go to recovery again and finally install RR again but with Magisk.
[OnePlus 3T Guides, News, & Discussion] rbn51:
So i followed the steps for the Custom Rom Version.

Now everything seems working fine but my Wifi and Bluetooth doesnt work. MAC Adress seems to be corrupt (02:00:...)

But it dont think my EFS Partition is damaged, because SIM is working and IMEI is showing. I restored an old EFS Backup but this doesnt help as well.

Someone has the same issue or could help me, im a little bit in trouble :D
[OnePlus 3T Guides, News, & Discussion] :
This doesn't seem to be an firmware issue. If I remember correctly the wlan mac address is randomized when booting the rom.

Maybe it's enough to reset the network settings, or the kernel needs updating - but that's just guessing without detailed setup information.

At least you are not alone. This seems to be quite common for quite some time:

https://www.google.com/search?sourc...hUKEwiGkdDwlIXkAhVMkMMKHXE7BKcQ4dUDCAc&uact=5
[OnePlus 3T Guides, News, & Discussion] melasuda:
Alright I'm ****ed. I flashed the wrong firmware and not booting my phone it says can't decrypt and must be restored, which takes me back to TWRP and asks me for a password which I do not know. What do I do?
[OnePlus 3T Guides, News, & Discussion] :
Format data in twrp (optional: change fs to f2fs) and encrypt data after first time setup in the rom.
[OnePlus 3T Guides, News, & Discussion] thomasnsr:
Thank you very much for making our life easier my friend, it is very kind of you to prepare the modded FW and how to install for us. I feel very lucky to have op3t. I follow your instruction of custom roms, and now enjoy the new FW. :highfive:
[OnePlus 3T Guides, News, & Discussion] hyperorb:
:good::good::good: ***

Easy Breezy

*** :good::good::good:

Steps I followed

- Backup all data, cleaned unwanted files

- Prerequisites / Downloads -

--- [Firmware] Downloaded oxygenos-9.0.5-bl-km-5.0.8-firmware-3.zip

--- [Recovery]Upgraded blu_spark twrp 8.61 to 3.3.1 via Official TWRP app

--- [ROM] Downloaded 9.0.5 FULL rom OnePlus3Oxygen_16_OTA_085_all_1907311947_108e7e9

--- [MAGISK] Downloaded v19.3 zip

- Boot to TWRP

- Wiped data (as i wanted to start fresh) [YMMV]

- Flashed ROM

- Flashed modded firmware

- Flashed TWRP

- Wiped dalvik/cache

- Reboot to recovery

- Flashed Magisk

- Wiped dalvik/cache

- Reboot to recovery (extra step .. just to make sure)

- Reboot to system

Thank you very much OP. :highfive: After a gap of over an year I thought of upgrading OP3 from 5.0.8 to 9.0.5. I was overwhelmed with so many posts regarding encryption , pie rom flashing issues etc. But your solution gave new life to my old OP3.

I find 9.0.5 very responsive on my device. Thanks again
[OnePlus 3T Guides, News, & Discussion] ml700:
Hi

So im on oxygenos 4.5.1 aka 7.1.1

If i want to update to this modded frimware do i need to flash the oxyhenos 5.0.x

And if so what is the best one to flash without losing the Data
[OnePlus 3T Guides, News, & Discussion] que.no:
I flashed directly from 7.1.1 (not even the latest) with this modded firmware, without any problems. The steps what I did was:

- reboot to TWRP, and flash the newest one

- wipe data (NOT format) + system

- flash OOS Pie

- flash this modded firmware

- flash newest TWRP again

- flash Magisk if you want to

- wipe dalvik/cache

- reboot

After that, a couple of minutes of loading, the phone booted, with all of my files on the internal storage

Edit: of course the apps will be gone, but the most of them will be restored by Google Play
[OnePlus 3T Guides, News, & Discussion] ml700:
Thanks man

I will do it :)
[OnePlus 3T Guides, News, & Discussion] pdeadm:
I am on the latest beta of Android 8.0. beta 39, 180704. Does this guide aplly to me? Has anyone given a try?

Bootloader unlocked, twrp, magisk are installed.

Thanks,

Pavlos
[OnePlus 3T Guides, News, & Discussion] :
Go ahead. (firmware-wise, I don't know if ob39 is updateable to 9.0.5)
[OnePlus 3T Guides, News, & Discussion] Simplified Helper:
You are a gentleperson and a scholar

Worked. like. a. charm.

Thank you!

Already got burned once with wiped data updating LOS nightly earlier this year once it needed newer modem firmware.

Cheers.
[OnePlus 3T Guides, News, & Discussion] Sjhingan:
Dont know if anyone else has experienced this but i am able to boot into system after following all steps and rooting with MAgisk but my phone is buggy and i face issues like sim not being detected and not being able to open settings as it keeps crashing. Any ideas?
[OnePlus 3T Guides, News, & Discussion] :
With these informations you give, I would say, clean flash (delete: system, data, cache, dalvik cache before) of the ROM, GApps, ... is the way to solve your problems
[OnePlus 3T Guides, News, & Discussion] :
Like [MENTION=2044343]accuphase[/MENTION] states: too less information. At least: which exact version of which rom do you try to update to which exact version? Have you tried uninstalling Magisk (which version)?
[OnePlus 3T Guides, News, & Discussion] Sjhingan:
Updating from 5.0.8 to 9.0.5 and MAgisk 19.3. Uninstalling magisk fixes all issues except sim is not detected.
[OnePlus 3T Guides, News, & Discussion] :
Can you delete just all network settings in oos 9.0.x (I'm no oos expert)? If so, delete network settings.

Reinstalling Magisl-19.3 after everything works should do no harm to your setup.
[OnePlus 3T Guides, News, & Discussion] Sjhingan:
Everything works great untill install Magisk. But i need a rooted phone...so still on 5.0.8 for now.
[OnePlus 3T Guides, News, & Discussion] :
This is not related to the firmware, but to oos 9.0.x rom. You may find something helpful in the oos thread (I think I rmember problems with some versions of the manager app). The beta Magisk thread may shine some light on this, too.
[OnePlus 3T Guides, News, & Discussion] Ihe87:
Hi all,

is it save to flash 9.0.5 on top of 9.0.2 Firmware without data gets lost?

TIA

Greets
[OnePlus 3T Guides, News, & Discussion] :
Modded fw on top of 5.0.x or on top of a previous fw from this thread. Don't use modded 9.0.5 on top of stock 9.0.2 fw.
[OnePlus 3T Guides, News, & Discussion] Ihe87:
Thanks for quick reply.

I want to flash stock 9.0.5 on top of stock 9.0.2.

No modded FW.

So everything should be good?
[OnePlus 3T Guides, News, & Discussion] :
Yes.
[OnePlus 3T Guides, News, & Discussion] NMe84:
If I try to install Magisk after following your guide my OP3 won't boot anymore, it just keeps spinning the logo on startup. If I flash the OTA update and your firmware again after that it boots just fine of course but I would like to get my root working again as well. Can you tell me what I should look into? Is this likely to be something with OxygenOS, your patch or Magisk? From what I can tell everyone else in this thread can actually boot their phone after installing Magisk.

Thanks for your nice solution to this upgrade problem by the way. :)
[OnePlus 3T Guides, News, & Discussion] :
It's not the fw. If you look around in the oos thread and the Magisk thread there are some users, with issues with Magisk and oos 9.0.5 - I'don't now if they solved it. Have you tried flashing Magisk after a successfull boot to system and waiting some minutes to settle (and enabling and authorising adb - to get a log if it's still not booting)? Have you tried an other Magisk version?
[OnePlus 3T Guides, News, & Discussion] NMe84:
I tried Magisk 19.3, 19.2 and the latest Canary build. I just tried flashing 19.3 again after having used the phone for a couple of days (so it definitely settled) and I got the same result so sadly that's not it either.

Thanks for pointing me in the direction of adb logging, I made a log file and ran into this:

--------- beginning of crash
09-13 17:03:02.758 1272 1272 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main
09-13 17:03:02.758 1272 1272 E AndroidRuntime: java.lang.NoClassDefFoundError: Failed resolution of: Landroid/util/BootTimingsTraceLog;
09-13 17:03:02.758 1272 1272 E AndroidRuntime:	at com.android.server.SystemServer.<clinit>(SystemServer.java:153)
09-13 17:03:02.758 1272 1272 E AndroidRuntime:	at java.lang.Class.classForName(Native Method)
09-13 17:03:02.758 1272 1272 E AndroidRuntime:	at java.lang.Class.forName(Class.java:453)
09-13 17:03:02.758 1272 1272 E AndroidRuntime:	at com.android.internal.os.RuntimeInit.findStaticMain(RuntimeInit.java:336)
09-13 17:03:02.758 1272 1272 E AndroidRuntime:	at com.android.internal.os.RuntimeInit.applicationInit(RuntimeInit.java:409)
09-13 17:03:02.758 1272 1272 E AndroidRuntime:	at com.android.internal.os.ZygoteInit.zygoteInit(ZygoteInit.java:912)
09-13 17:03:02.758 1272 1272 E AndroidRuntime:	at com.android.internal.os.ZygoteInit.handleSystemServerProcess(ZygoteInit.java:506)
09-13 17:03:02.758 1272 1272 E AndroidRuntime:	at com.android.internal.os.ZygoteInit.forkSystemServer(ZygoteInit.java:730)
09-13 17:03:02.758 1272 1272 E AndroidRuntime:	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:833)
09-13 17:03:02.758 1272 1272 E AndroidRuntime: Caused by: java.lang.ClassNotFoundException: Didn't find class "android.util.BootTimingsTraceLog" on path: DexPathList[[zip file "/system/framework/services.jar", zip file "/system/framework/ethernet-service.jar", zip file "/system/framework/wifi-service.jar", zip file "/system/framework/com.android.location.provider.jar"],nativeLibraryDirectories=[/system/lib64, /system/vendor/lib64, /system/lib64, /system/vendor/lib64]]
09-13 17:03:02.758 1272 1272 E AndroidRuntime:	at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:169)
09-13 17:03:02.758 1272 1272 E AndroidRuntime:	at java.lang.ClassLoader.loadClass(ClassLoader.java:379)
09-13 17:03:02.758 1272 1272 E AndroidRuntime:	at java.lang.ClassLoader.loadClass(ClassLoader.java:312)
09-13 17:03:02.758 1272 1272 E AndroidRuntime:	... 9 more

I'll try and see if I can find anything related to that and if I can't find a solution I'll ask around in those other threads. Thanks. :)
[OnePlus 3T Guides, News, & Discussion] NMe84:
I'm still having issues with the above and I'm considering doing a factory reset. And if I'm doing that anyway I guess it's a good idea to get rid of this modded firmware too and just use the unmodded OTA. Is that just a matter of flashing the OTA, then returning to fastboot and flashing the stock recovery and finally booting into that to do a factory reset? Or are there more steps to it? Or should I just do a clean flash instead and be done with it? The first post in this thread mentions re-encrypting, is that something I need to consciously do or will that happen by itself if I just wipe everything before flashing?
[OnePlus 3T Guides, News, & Discussion] animeallen:
Am I the only who does not understand step 5 for custom roms? Sorry.

5. (dirty) flash your preferred, 9.0.x firmware needing custom rom (if your rom doesn't need 9.0.x firmware, stay with 5.0.8)

Am I supposed to flash a 9.0.5 firmware or a custom rom? Or both?
[OnePlus 3T Guides, News, & Discussion] BillGoss:
It's assuming you're updating your existing rom to one that needs the 9.0.x firmware. So it's saying dirty flash the rom. If you're not updating, then just skip this step.
[OnePlus 3T Guides, News, & Discussion] :
If the rom you want to use needs 5.0.x fw, stay with 5.0.x fw.

At 5. you have already flashed the fw in step 3. "flash your preferred, 9.0.x firmware needing custom rom" refers to the rom, that needs 9.0.x fw.
[OnePlus 3T Guides, News, & Discussion] Dirk:
Finally updated my ROM build from Oreo requirement to Pie requirement. Least annoying big update i've had to do. Thanks OP. :good:

(Latest TWRP/Unencrypted/crDroid/Dirty Flash)
[OnePlus 3T Guides, News, & Discussion] renndachserl:
Can I use this modded fw to got safely from 9.0.2 to 9.0.5? Lost my data twice this year (from 5.x.x to 9.0.1 and also from 9.0.1 to 9.0.2) and don't want to run into the triple.

From 9.0.1 to 9.0.2 I tried installing some kind of a modded firmware but dont really remember which it have been. How can I check which fw / bl and km is installed?

I am encrypted /w open bootloader and root

Best Regards!
[OnePlus 3T Guides, News, & Discussion] :
I've answered that so many times...

The ONLY!!! step that yields to loss of data is updating the bl from 5.0.x to 9.0.x or downgrading the bl from 9.0.x to 5.0.x.

If you use my modded fw, you just don't change the bl.

If you use the stock fw for updating, you've updated the bl from 5.0.x to 9.0.x.

I.e.: if you update from 5.0.x to 9.0.1 with stock fw, you've chenged the bl from 5.0.x to 9.0.x (resulting in dataloss). If you update stock 9.0.1 fw to modded 9.0.2 fw, you've changed the 9.0.x bl back to 5.0.8 bl (resulting in dataloss).

This is explained in OP already:

If you don't remember what you've flashed, you can extract the modem and bl partitions with dd . You can pipe the result to strings and grep for "Time_Stamp" respectively "compiled at".

ingo@adler /usr/local/src/oxygenos $ adb shell su -c "dd if=/dev/block/bootdevice/by-name/modem"|strings|grep Time_Stamp
"Time_Stamp": "2019-07-31 19:47:38"
194560+0 records in
194560+0 records out
99614720 bytes transferred in 9.328 secs (10679108 bytes/sec)
ingo@adler /usr/local/src/oxygenos $ adb shell su -c "dd if=/dev/block/bootdevice/by-name/aboot"|strings|grep "compiled at"
LK compiled at Dec 6 2018 00:53:31
16384+0 records in
16384+0 records out
8388608 bytes transferred in 0.564 secs (14873418 bytes/sec)

This needs to be compared with the fw package: Unzip the fw zip in question and "strings|grep" on firmware-update/NON-HLOS.bin (for modem) and firmware-update/emmc_appsboot.mbn for bl. Do this for all fw packages in question, until you've found the exact strings you've gotten with dd. The one with both strings matching is the currently installed package.

The above example is https://github.com/nvertigo/firmwar...3t/oxygenos-9.0.5-bl-km-5.0.8-firmware-3T.zip

If you don't use a unix like os (i.e. win) use MinGW or cygwin to get strings and grep.
[OnePlus 3T Guides, News, & Discussion] renndachserl:
Thank you so much for repeating it one more time :) I think I got it now and as my investigation with dd shows, I might have downgraded the bootloader again after the upgrade from 9.0.1 to 9.0.2 which explains the data loss:

/mnt/c/adb$ adb.exe shell su -c "dd if=/dev/block/bootdevice/by-name/modem"|strings|grep Time_Stamp
"Time_Stamp": "2019-05-11 00:01:51"
$ dd if=firmware-update/NON-HLOS.bin|strings|grep Time_Stamp
"Time_Stamp": "2019-05-11 00:01:51"

/mnt/c/adb$ adb.exe shell su -c "dd if=/dev/block/bootdevice/by-name/aboot"|strings|grep "compiled at"
LK compiled at Dec 6 2018 00:53:31
$ dd if=firmware-update/emmc_appsboot.mbn|strings|grep "compiled at"
LK compiled at Dec 6 2018 00:53:31

I found the identical Time_Stamp / compiling date in the oxygenos-9.0.2-bl-km-5.0.8-firmware-3T.zip which is on your github archive.

So the conclusion is:

Flash OOS 9.0.5 and don't reboot

Flash oxygenos-9.0.5-bl-km-5.0.8-firmware-3T.zip

Should it work without data loss this way?

So that i stay with the 5.08 bootloader file. And until I'm ready for a data wipe I have to follow this procedure with every new OOS update.

Many thanks again!

BR, Marco
[OnePlus 3T Guides, News, & Discussion] :
Yes.

Again: yes. That's exactly what I would do myself, if I wouldn't need to test future modded versions before release.
[OnePlus 3T Guides, News, & Discussion] papakitou:
Hello, i am currently using Havoc rom with 5.0.8 FW. I would like to update or even try Skydragon latest Pie rom. If i flash this modded firmware im good? I will perform clean flash, maybe internal storage too
[OnePlus 3T Guides, News, & Discussion] :
Flash modded fw, reboot to recovery and wipe system, data (without wiping media) and cache. Flash rom as recommended in OP of the rom you are going to flash. Encryption (if enabled) will persist.
[OnePlus 3T Guides, News, & Discussion] Primokorn:
Just flashed your modded firmware on Skydragon - Pie - before upgrading to MSM Xtended XQ (Android 10).

No issue at all. I'm encrypted.

Thanks a lot.
[OnePlus 3T Guides, News, & Discussion] ela1103:
could you share

modded firmware on Skydragon - Pie link
[OnePlus 3T Guides, News, & Discussion] Viper The Ripper:
Why?

Use the latest modded FW files for your device op3/3t > 9.0.5 FW.

Please read carefully the OP, you can find ALL files, links, info... there, don't need to post it thousand times.
[OnePlus 3T Guides, News, & Discussion] :
UPDATE: op3t: 9.0.6

I've update the stock fw and the modded fw for op3t:

Stock 9.0.6: https://github.com/nvertigo/firmware-3t/raw/master/archive/op3t/oxygenos-9.0.6-firmware-3T.zip

Modded 9.0.6: https://github.com/nvertigo/firmwar...3t/oxygenos-9.0.6-bl-km-5.0.8-firmware-3T.zip

I'll update OP as soon as I've completed the fws for op3.

Thanx to [MENTION=4954690]Siddk007[/MENTION] and all users reporting links to his OOS thread. Without those links neither the stock fw packages nor the modded fw packages would be completed that quick.
[OnePlus 3T Guides, News, & Discussion] bwagner.ash88@gmail.com:
How do I flash the new 9.0.6 oxygen update on my rooted 3t coming off of a custom ROM?
[OnePlus 3T Guides, News, & Discussion] :
This is not the oos update, but only the firmware. Read at the OP for installation instructions.
[OnePlus 3T Guides, News, & Discussion] mvalda01:
Sorry if it has been asked before - I couldn't find anything anyway. Custom Q roms mostly don't support encryption, so an average Q user is not encrypted. This breaks your conditions to flash the modded FW, does it? For example, I'm on Q PE with your modded 9.0.5 FW, not encrypted; can I just follow the guide you posted on OP to update on 9.0.6 FW or will I have issues? Thank you [MENTION=4405529]nvertigo67[/MENTION]
[OnePlus 3T Guides, News, & Discussion] :
If your device isn't encrypted, you can switch between modded fw and stock fw without data loss. If you don't expirience any other issues (i.e. selinux always permissive on enforcing roms), I'd recommend to stick with stock fw.

I also recommend to stick with that version of the fw, that is used as ase for the blobs - as long as the devs doesn't explicitly tell something else in OP, though newer fws (newer then the blobs) will mostly work. Custom roms, that use los-17 blobs (https://github.com/TheMuppets/proprietary_vendor_oneplus/commits/lineage-17.0/oneplus3/proprietary ) as base are still based on 9.0.4. The same goes for most los-16 based roms.
[OnePlus 3T Guides, News, & Discussion] mvalda01:
Thank you very much for your detailed and exhaustive answer.
[OnePlus 3T Guides, News, & Discussion] Clark789:
Hi folks,

in the OP there are instructions, how to use the firmware for updating OOS (i'm coming from 5.0.8). But there is no reference made for Magisk in the end. Isn't it necessary to flash it again? I thought so... Especially, if i will use a custom kernel...

Regards

Clark
[OnePlus 3T Guides, News, & Discussion] :
Use your usual update routine. I.e. flash rom, flash magisk, (optional: flash some funny boot image and/or system altering packages), flash custom kernel. Just make sure to flash the modded fw right after flashing the oos rom (which contains the stock fw, sic!).
[OnePlus 3T Guides, News, & Discussion] kamilmirza:
i thought full zip was available and I grabbed it from HERE :confused:

is it not?
[OnePlus 3T Guides, News, & Discussion] Iceman248:
Where can I check the current firmware I have. I installed 9.0.6 from 9.0.5, but the baseband version is still the same, so I don't know if it didn't go through or what.