Related
After installing MedroM I got this problem and couldn't connect to google account and every google app would crash if I tried to log in, so I flashed b161 and I still have this problem, even after numerous factory resets, has this ever happened to anyone ?
Yes, it is happening to other guys around here...
In fact is happening to all who flash B160/B161 firmware...
Is not possible to flash any firmware previously to B160/B161.
Workaround is to unlock bootloader, flash twrp, root it, reflash oeminfo for your device,
and after that you can flash another firmware again.
gtdaniel said:
Yes, it is happening to other guys around here...
In fact is happening to all who flash B160/B161 firmware...
Is not possible to flash any firmware previously to B160/B161.
Workaround is to unlock bootloader, flash twrp, root it, reflash oeminfo for your device,
and after that you can flash another firmware again.
Click to expand...
Click to collapse
i'm in the same situation, i tried to do what you've said, but twrp says that the installation failed. how can I have play store working again? please help, this situation is driving me crazy!
i'm on c900 b161.
I had the same issue. I did a clean flash of the new 161 update and that made my device a C900. I have a Eurpoean model (T-Mobile Germany).
After 2 days of trying different stuff, here's what gave me a functional device with TWRP and Root back:
-Back up any data you want to keep, obviously.
-Reflash stock ROM (put UPDATE.APP on your dload/ folder on the separate SD card, then boot into the update function by turning the phone off and then holding Vol+, Vol-, Power. Just wait until it's finished.
-Unlock Bootloader again
-Download the Toolkit: http://forum.xda-developers.com/huawei-p9lite/development/europe-vns-l31-toolkit-bootloader-t3432873
-Flash TWRP through the toolkit
-Boot TWRP and root
-In Android, enable ADB
-In the Toolkit, go to Dual Sim>Individual and select the appropriate custom.bin and oeminfo.img from the thread of the toolkit. For my European one it was L31 SS C432. Press flash and grant Root permissions on your phone.
-Turn off your phone and flash the stock ROM again like in step 1.
-If you want root, you need to unlock the Bootloader again, flash TWRP and then root it from there.
DON'T WIPE ANYTHING IN TWRP OR YOU WILL HAVE TO START ALL OVER AGAIN!
Don't ask me how I know.
Hope this saves someone from wasting their time with this nonsense like I have.
No need to touch the oem stuff, just extract the boot.img and system.img and flash through adb, for dat you need bootloader unlocked and fastboot drivers then you can downgrade firmware and fix your sign problem or just wait for a new firmware
raffabraz said:
No need to touch the oem stuff, just extract the boot.img and system.img and flash through adb, for dat you need bootloader unlocked and fastboot drivers then you can downgrade firmware and fix your sign problem or just wait for a new firmware
Click to expand...
Click to collapse
That would be much simpler, I didn't consider that. Would you mind writing up a guide?
I've had the same issue and have resolved it pretty easily,
i did the following steps ;
- download both medrom versions
- do full factory reset
- install medrom v1
- do all settings of google etc
- reboot recovery and install v2
- wipe dalvik and reboot
-- all works now except for the forceclose on facebook
ps : this answer is also in the thread ( not as extended as this but it's there )
Edit : some other apps are Force closing to, my guess is that there's a shared resource of some kind that's corrupted or something..
sirlex said:
I've had the same issue and have resolved it pretty easily,
i did the following steps ;
- download both medrom versions
- do full factory reset
- install medrom v1
- do all settings of google etc
- reboot recovery and install v2
- wipe dalvik and reboot
-- all works now except for the forceclose on facebook
ps : this answer is also in the thread ( not as extended as this but it's there )
Edit : some other apps are Force closing to, my guess is that there's a shared resource of some kind that's corrupted or something..
Click to expand...
Click to collapse
Force closing is caused by the oeminfo in my experience. Can you check in the "About Phone" section which build number your phone currently has? Should be something along the lines of "VNS-L31C432B161" where C432 indicates the region code.
since I am Running MEDROM v2 it shows just that. However , I do know it is based on b161
HeavyHDx said:
I had the same issue. I did a clean flash of the new 161 update and that made my device a C900. I have a Eurpoean model (T-Mobile Germany).
After 2 days of trying different stuff, here's what gave me a functional device with TWRP and Root back:
-Back up any data you want to keep, obviously.
-Reflash stock ROM (put UPDATE.APP on your dload/ folder on the separate SD card, then boot into the update function by turning the phone off and then holding Vol+, Vol-, Power. Just wait until it's finished.
-Unlock Bootloader again
-Download the Toolkit: http://forum.xda-developers.com/huawei-p9lite/development/europe-vns-l31-toolkit-bootloader-t3432873
-Flash TWRP through the toolkit
-Boot TWRP and root
-In Android, enable ADB
-In the Toolkit, go to Dual Sim>Individual and select the appropriate custom.bin and oeminfo.img from the thread of the toolkit. For my European one it was L31 SS C432. Press flash and grant Root permissions on your phone.
-Turn off your phone and flash the stock ROM again like in step 1.
-If you want root, you need to unlock the Bootloader again, flash TWRP and then root it from there.
DON'T WIPE ANYTHING IN TWRP OR YOU WILL HAVE TO START ALL OVER AGAIN!
Don't ask me how I know.
Hope this saves someone from wasting their time with this nonsense like I have.
Click to expand...
Click to collapse
Thank you so much , you saved my phone !!
Fllashing stock rom again isnt necessary , just flash the oeminfo, reboot, they will tell you an encryption password, so you have to do a factory reset AND DONE !
simo255 said:
Thank you so much , you saved my phone !!
it doesn't need to reflash stock rom again, just flash the oeminfo, reboot, they will tell you an encryption password, so you have to do a factory reset AND DONE !
Click to expand...
Click to collapse
Interesting, when I tried to do a factory reset after that screen, it always failed.
HeavyHDx said:
Interesting, when I tried to do a factory reset after that screen, it always failed.
Click to expand...
Click to collapse
You have to flash the stock recovery to do a Factory reset
medRom v2 fix
Hi all.
I think i found solution for Google login issue.
I use European VNS-L21-C432B161 dual sim phone with lattest rom.
I flashed medRom v2 with full wipes.
Ofcourse i Can not log in Google Services.
Today i download 3 Google apk files. Installed and it works.
Sorry. I cant post ling on XDA now.im newbie
Link in My profils.
There is instruction how i do:
1. Installed Gmail apk and login.
2. Installed Android System Web Wiev apk.
3. Installed Google Play Service apk
Proof: in My profils description in Youtube
Download Files: watch in YOUTUBE description.
Hope helps for someone.
Could someone provide me the correct oeminfo and custom.bin for a European/German model? C432? The images inlcuded in the toolkit don't work for me, it still crashes or can't communicate with the google server
Deddline said:
Hi all.
I think i found solution for Google login issue.
I use European VNS-L21-C432B161 dual sim phone with lattest rom.
I flashed medRom v2 with full wipes.
Ofcourse i Can not log in Google Services.
Today i download 3 Google apk files. Installed and it works.
Sorry. I cant post ling on XDA now.im newbie
Link in My profils.
There is instruction how i do:
1. Installed Gmail apk and login.
2. Installed Android System Web Wiev apk.
3. Installed Google Play Service apk
Proof: in My profils description in Youtube
Download Files: watch in YOUTUBE description.
Hope helps for someone.
Click to expand...
Click to collapse
Installing Android System Web View apk from apkmirror solved the problem for me (arm + x86 package). Thank you
HeavyHDx said:
I had the same issue. I did a clean flash of the new 161 update and that made my device a C900. I have a Eurpoean model (T-Mobile Germany).
Click to expand...
Click to collapse
I got my P9 Lite from Congstar in Germany. I didn't knew, that the device would be branded by Telekom. I flashed the B161 and couldn't connect to any google account. Thankfully updating the webview apk via apk mirror solved this problem. But this leaves me with 2 questions and maybe you could answer these...?
1) Do you know which stock rom would work the best with my device (VNS-L31 without the possibility to use two sim cards ) and where I could download this stock rom.
2) Is the B161 supposed to work fine after solving this issue or are there other problems with it?
I would be really happy if someone of you could help me. :good:
MartinMo said:
1) Do you know which stock rom would work the best with my device (VNS-L31 without the possibility to use two sim cards ) and where I could download this stock rom.
2) Is the B161 supposed to work fine after solving this issue or are there other problems with it?
Click to expand...
Click to collapse
1) The best stock ROM would either be, well, the stock ROM, or the Revolution ROM.
2) I've had some strange behavior with Relay for Reddit and frequent crashes of WhatsApp when sending messages. Right now I'm on Lineage OS 14.1 and it's really great. Camera's a bit slow, but otherwise I love it. I missed stock Android.
HeavyHDx said:
1) The best stock ROM would either be, well, the stock ROM, or the Revolution ROM.
Click to expand...
Click to collapse
Isn't Nougat still a beta...? I'm looking for a stable stock version of EMUI...
HeavyHDx said:
2) I've had some strange behavior with Relay for Reddit and frequent crashes of WhatsApp when sending messages. Right now I'm on Lineage OS 14.1 and it's really great. Camera's a bit slow, but otherwise I love it. I missed stock Android.
Click to expand...
Click to collapse
Thank you, tomorrow I'll test if Whatsapp working fine or not, that's important for me. Is Lineage 14.1 the most stable Lineage version?
Nougat is still in beta, yes. The full version is expected to come out within the next few weeks.
14.1 refers to the Android version which is 7.1.1. They adopted CyanogenMod's naming scheme. You'll still need to update LineageOS to get bugfixes and such. The dev releases a new update every 2 or 3 days, just check their website periodically.
Deddline said:
Hi all.
I think i found solution for Google login issue.
I use European VNS-L21-C432B161 dual sim phone with lattest rom.
I flashed medRom v2 with full wipes.
Ofcourse i Can not log in Google Services.
Today i download 3 Google apk files. Installed and it works.
Sorry. I cant post ling on XDA now.im newbie
Link in My profils.
There is instruction how i do:
1. Installed Gmail apk and login.
2. Installed Android System Web Wiev apk.
3. Installed Google Play Service apk
Proof: in My profils description in Youtube
Download Files: watch in YOUTUBE description.
Hope helps for someone.
Click to expand...
Click to collapse
Installed Android System Web Viev .apk did the trick for me, too. muchos gracias.
Hey fellows, recently i bought a xiaomi a1 on gearbest, i tried to set up but i can't, suddenly all apps being crashing, saying "google stops working" "youtube stops working" and reboots and setup starts again,
Already i tryied:
Flashing with xiaomi tool, with diferent releases of android nougat
Flashing manually with fastboot and scripts
Flashing the persist partition
Flashing twrp roms (bootloop)
And after all tried keeps saying "google stops working" "com.android..." stops working and reboots again
I cant get a clue if is software problem or hardware
The phone is new and can't use it
Showcase here: https://youtu.be/vkywaMjfc-0
Sorry for my bad english
Do you have the stock image from Xiaomi and did you do "clear all data and lock bootloader"?
ProchyGaming said:
Do you have the stock image from Xiaomi and did you do "clear all data and lock bootloader"?
Click to expand...
Click to collapse
the roms that i downloaded are from the xiaomi site and lock the bootloader after flashing, also wipe with twrp
germanmtzmx said:
the roms that i downloaded are from the xiaomi site and lock the bootloader after flashing, also wipe with twrp
Click to expand...
Click to collapse
Did you just boot or flash the TWRP??
ProchyGaming said:
Did you just boot or flash the TWRP??
Click to expand...
Click to collapse
only boot, i thought that was a gapps problem but, i tried to install open gapps but was unsuccessful
germanmtzmx said:
only boot, i thought that was a gapps problem but, i tried to install open gapps but was unsuccessful
Click to expand...
Click to collapse
What Android version are you on now ?
ProchyGaming said:
What Android version are you on now ?
Click to expand...
Click to collapse
7.1.2
can you tell me how clear all data from the phone and do a fresh install ???
germanmtzmx said:
7.1.2
can you tell me how clear all data from the phone and do a fresh install ???
Click to expand...
Click to collapse
http ://en.miui.com/forum.php?mod=viewthread&tid=807252&extra=page%3D1&mobile=2
Miflash tool, don't wipe with twrp and dont install gapps, just do everything they tell you to do in that link. When you open miflash tool, you should have 3 options on the bottom right corner, choose the clean data and keep unlocked, you can re-lock the bootloader manually later.
Mizuru said:
http ://en.miui.com/forum.php?mod=viewthread&tid=807252&extra=page%3D1&mobile=2
Miflash tool, don't wipe with twrp and dont install gapps, just do everything they tell you to do in that link. When you open miflash tool, you should have 3 options on the bottom right corner, choose the clean data and keep unlocked, you can re-lock the bootloader manually later.
Click to expand...
Click to collapse
i already followed, but keeps rebooting by itself even with edl mode and miflash, i thought that the problem gone but suddenly the bootloop appears also ota notification for android oreo appears but i can't update, when starts to download the update the phone crashes
Hello devices status
apps keep crashing and phone reboots by itself
your phone mi a1 or mi 5X ?
if you mi a1 you download from here ??
corect
ajegile said:
your phone mi a1 or mi 5X ?
if you mi a1 you download from here ??
corect
Click to expand...
Click to collapse
yes, I downloaded it from there and it's a1
http://bigota.d.miui.com/7.8.23/tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794.tgz
Hello brother download and flashing clean and lock selective testing
No twrp flash
No opengapps flash
Testing 7.8.23 clean and lock
Byramklc said:
http://bigota.d.miui.com/7.8.23/tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794.tgz
Hello brother download and flashing clean and lock selective testing
No twrp flash
No opengapps flash
Testing 7.8.23 clean and lock
Click to expand...
Click to collapse
I will try and show you the results
germanmtzmx said:
I will try and show you the results
Click to expand...
Click to collapse
Okey bro my telegram +905394461388
the gapps still crashing and the phone restarts when i close the messages of "the n app stops working"
Hello I succeed in rooting my phone a few days ago but some moto fonctions doesn't work well (fingerprint,rotate,moto display stop each time)and I couldn't desinstall apps ans install theme icones while I was superuser.So I decide to restore stock and reinstall TWRP and supersu.But TWRP doesn't load after to start phone and I tried install many img with any problems (see OK all time) but Twrp menu never appears (maybe a pb due to Elementx install for rooting before? I don't now for the moment).I'm looking for......
What surprises me is the fact that I always have "status modified" on bootloader while it would be "official".And It is in yellow as when Twrp was installed.Restore stock doesn't erase all datas for custom recovery?Stock works normally.Did Twrp removed completely???Did you have an explanation for tis issue?
My stock firmware is which I downloaded from motorola website.I attempt factory reset,wipe cache etc .....nothing
I would try another method to restore (with 2 others firmware).
Tonton Biscotte said:
What surprises me is the fact that I always have "status modified" on bootloader while it would be "official".And It is in yellow as when Twrp was installed.Restore stock doesn't erase all datas for custom recovery?Stock works normally.Did Twrp removed completely???Did you have an explanation for tis issue?
My stock firmware is which I downloaded from motorola website.I attempt factory reset,wipe cache etc .....nothing
I would try another method to restore (with 2 others firmware).
Click to expand...
Click to collapse
Maybe you flashed the wrong firmware. Flash this one with the guide:
https://forum.xda-developers.com/mo...ck-rom-npjs25-93-14-4-march-1-t3608138/page99
Also this is the wrong forums to ask.
I am unable to report this. Please any moderator shift this thread
Tonton Biscotte said:
Hello I succeed in rooting my phone a few days ago but some moto fonctions doesn't work well (fingerprint,rotate,moto display stop each time)and I couldn't desinstall apps ans install theme icones while I was superuser.So I decide to restore stock and reinstall TWRP and supersu.But TWRP doesn't load after to start phone and I tried install many img with any problems (see OK all time) but Twrp menu never appears (maybe a pb due to Elementx install for rooting before? I don't now for the moment).I'm looking for......
What surprises me is the fact that I always have "status modified" on bootloader while it would be "official".And It is in yellow as when Twrp was installed.Restore stock doesn't erase all datas for custom recovery?Stock works normally.Did Twrp removed completely???Did you have an explanation for tis issue?
My stock firmware is which I downloaded from motorola website.I attempt factory reset,wipe cache etc .....nothing
I would try another method to restore (with 2 others firmware).
Click to expand...
Click to collapse
You can flash latest official firmware that is posted in second post to solve firmware related issues..
After flashing, you will not get official status back, it will remain modified..
To get official status back, you need to have OTA update, which is possible only when Motorola releases OREO or SECURITY PATCH, but currently no any method will work... (Also not sure about security update )
NEVER DOWNGRADE AND TAKE OTA UPDATE, IT WILL BRICK YOUR DEVICE.
I forgot to precise I was under Android 6.0 (MM) but it 's frustrated I don't have a signature now.Ok I had to try to update to Androit 7.0 (Nougat) but it failed.I restore a stock and update it with OTA but it doesn't install it.
So I reinstall one more time but I flash partition and bootloader with one tuto of XDA even if it isn't advised.
I think install of Elementx has caused troubles because Update and Twrp install worked perfectly before.
I don't know what 's the problem
just use MsmDownloadTool V4.0.exe to recovery my op5 to oos, but the version is quite low as Android 7.1.1.
checked the system update, it told me up to date. which is of course not true.
tried to clean the cache of google framework service and oneplus framework service, still nothing in updating.
tried installed oxygen updater, and download 3 update zip from 7.1.4, 8, last version of 8, but each time I use local install in system uploading, then reboot to recovery, it shows me "failed". none of version works.
I even tried to install in recovery, wipe cache and data or just wipe data, then install from internal disk, none of the file works, even don't have any popup fail notice, just go back to file chooser interface.
I can still go back to system by switch off and on again.
How can I upgrade the old version of android in my oneplus 5?
original:
used use lineages os with Twrp, and I would like to flash to original oxygen.
download full rom zip in https://www.oneplus.com/uk/support/softwareupgrade/details?code=PM1574156143164
copied to phone disk
went to twrp
wipe Dalvik, System, Data, and Cache
then tried to install the full rom zip, but met "no Digest File found" error
found it must be twrp old, so I download new one in https://dl.twrp.me/cheeseburger_dumpling/twrp-3.4.0-0-cheeseburger_dumpling.img.html
copy to phone and flash it to recovery.
select "reboot to recovery"
then problem coming: I can only see the oneplus logo with powered by Android. it won't go any further.
I am not sure any thing wrong during my processing, but maybe 2 things:
1, I wiped the system
2, I didn't clean the screen lock pin before I flash
so, my question here is, if possible I can flash the original oxygen os in this situation?
if positive, could you please give me a step by step instruction?
by the way, the zip rom I download from oneplus site isn't have the "flash-all" script.
please please help me .
First install OxygenOS 5.1.4 based on Android Oreo and boot to that version to create /vendor partition for Treble support
Pierre02 said:
First install OxygenOS 5.1.4 based on Android Oreo and boot to that version to create /vendor partition for Treble support
Click to expand...
Click to collapse
thanks! it works! i'm at 5.1.2 then i install OxygenOS 5.14 (OnePlus5Oxygen_23_OTA_037_all_1807181258_7b4b6.zip) then after that I install OnePlus5Oxygen_23_OTA_042_all_1812232102_a034988b.zip and then the last and the latest OnePlus5Oxygen_23_OTA_068_all_2006012224_c7a6016.zip android 10.
Please help. I bought a phone with Beta installed. I wanted to switch to the original system. So I screwed up something so using the MsmDownloadTool tool I wanted to use it by uploading everything from scratch. I fell into the Chinese H2Os system. I searched again and I already have the original ColorOS based on Android 9. But I can't update it to 10. What do I have to do? Oh .... the bootloader is unlocked ...
uno0 said:
Please help. I bought a phone with Beta installed. I wanted to switch to the original system. So I screwed up something so using the MsmDownloadTool tool I wanted to use it by uploading everything from scratch. I fell into the Chinese H2Os system. I searched again and I already have the original ColorOS based on Android 9. But I can't update it to 10. What do I have to do? Oh .... the bootloader is unlocked ...
Click to expand...
Click to collapse
Use an EDL Flasher (unbrick tool) here on XDA
Pierre02 said:
First install OxygenOS 5.1.4 based on Android Oreo and boot to that version to create /vendor partition for Treble support
Click to expand...
Click to collapse
thanks for replying
I had figure out my problem.
it seems the rom I flashed using MsmDownloadTool had something wrong,
I've changed another one, it shows me the update from the first start after flashing.
uno0 said:
Please help. I bought a phone with Beta installed. I wanted to switch to the original system. So I screwed up something so using the MsmDownloadTool tool I wanted to use it by uploading everything from scratch. I fell into the Chinese H2Os system. I searched again and I already have the original ColorOS based on Android 9. But I can't update it to 10. What do I have to do? Oh .... the bootloader is unlocked ...
Click to expand...
Click to collapse
if you are directly flash to coloros android 9 from lower version other than android 8, it might be the problem you won't got the update in the system. It might be have issue in wifi or gps as well, which I bet you didn't well test yet.
that's all about the system partitions messed up. regarding my understanding.
solution is simple, but time consuming:
you have to flash an original rom using msmdownloadtool, make sure that rom will have update notification in the system menu of settings. then upgrade from there one level up each time, till to the android 10. (chinese version do have 10 available)
than, you can download oxygen os android 10 to flash on the coloros android 10 (hydrogen os android 10) you just done the upgrade, don't forget wipe data/cache before flashing.
hope that's helps.
netzkie said:
thanks! it works! i'm at 5.1.2 then i install OxygenOS 5.14 (OnePlus5Oxygen_23_OTA_037_all_1807181258_7b4b6.zip) then after that I install OnePlus5Oxygen_23_OTA_042_all_1812232102_a034988b.zip and then the last and the latest OnePlus5Oxygen_23_OTA_068_all_2006012224_c7a6016.zip android 10.
Click to expand...
Click to collapse
Kindly tell me in steps you follow m stuck in 4.5.8 version with download links
After flashing back oxygen os to both slots I can't download all my apps. Putting the phone to download google backup(like apps and such) it fails to install over 40 apps out of 170 and when trying to update apps, playstore says that the app which I'm trying to update needs SD card or other media device with sufficent space while i have over 90gb free. I have also tried to use the unbricking tool with no luck. WhatsApp doesn't want to restore either. I've also tried to download ota file with chrome and chrome says also that I don't have enough space.
Try fastboot
You should try flash again with fastboot-ROM
Thevili03 said:
After flashing back oxygen os to both slots I can't download all my apps. Putting the phone to download google backup(like apps and such) it fails to install over 40 apps out of 170 and when trying to update apps, playstore says that the app which I'm trying to update needs SD card or other media device with sufficent space while i have over 90gb free. I have also tried to use the unbricking tool with no luck. WhatsApp doesn't want to restore either. I've also tried to download ota file with chrome and chrome says also that I don't have enough space.
Click to expand...
Click to collapse
Use msm tool instead...i got this issue when came back from custom rom! Some partition is messing up
Thevili03 said:
After flashing back oxygen os to both slots I can't download all my apps. Putting the phone to download google backup(like apps and such) it fails to install over 40 apps out of 170 and when trying to update apps, playstore says that the app which I'm trying to update needs SD card or other media device with sufficent space while i have over 90gb free. I have also tried to use the unbricking tool with no luck. WhatsApp doesn't want to restore either. I've also tried to download ota file with chrome and chrome says also that I don't have enough space.
Click to expand...
Click to collapse
I had the same problem after make a oos reinstall with a .bat I download, I solved the problem copying all the internal memory to my pc and making a full wipe (internal memory included) and a reinstall via fastboot with the .bat
maybe copy and wipe the internal memory and reinstall the rom can solve the problem, if not I can upload the fastboot unbrick .bat I use to gdrive and you can try a reinstall it is oos pie 9.0.17 but you can always update to oos 10
So, I got it to working with msm-tool. It went back to oos 9.0.16 and then I upgraded to oos 10.3.5, resetted again, and got everything working. But now I think that I got the Indian version or something, because I have red cable club and oneplus cloud there, I live in Finland so obviously they aren't working here. Can I somehow get the international version of oos?
For anybody reading this in the future, this is actually caused by invalid decryption keys. It's possible to have Android boot but not successfully decrypt data. In this state the phone will boot but no applications will install and saving files won't work correctly.
Simply wiping data should fix the issue, but there's always the MSM tool for when things go really wrong.
use fastboot roms to refresh your device and remove data encryptions
Thevili03 said:
So, I got it to working with msm-tool. It went back to oos 9.0.16 and then I upgraded to oos 10.3.5, resetted again, and got everything working. But now I think that I got the Indian version or something, because I have red cable club and oneplus cloud there, I live in Finland so obviously they aren't working here. Can I somehow get the international version of oos?
Click to expand...
Click to collapse
International/global same thing. There are twrp flashable OOS that are global for 6t here: https://forum.xda-developers.com/oneplus-6t/how-to/oneplus-6t-global-repo-oxygen-os-builds-t3865396
Next time you want to roll back to OOS from a custom rom:
Boot twrp
Flash OOS 10.3.5 global from that link
Flash twrp installer zip
Flash finalize zip
Format data (remember this wipes everything)
Reboot system.
You will not have this issue if you install that way.
Then if you want root boot twrp and flash magisk , reboot system.
Also if you ever have to use Msm tool again you can use the last Android 9/pie twrp by mauronofrio. The twrp he compiled just before Android 10/Q twrp started.. You can use that twrp and just flash OOS 10.3.5 global rom after you run Msm tool. That way updating won't take so long. That's what I did and had no issues. Just don't ever downgrade OOS via TWRP or you'll brick.