Hey guys, first of all sorry about my english, im french.
So my problem is: I tried rooting my Axon 7 A2017U many times, with different guides. I always end up with a softbricked phone, having to restore to stock using MiFlash.
My bootloader is unlocked, i have stock recovery and stock rom for now.
Whenever i flash TWRP, either the signed one (from @tenfar) or unsigned (and up to date) ones, i can't go past the menu saying something like "your phone cant be checked for corruption, please lock your phone [...]" it just freeze. i did read somewhere that i should flash chainfire's root or a special .zip that, i guess, disabled some check that could prevent booting a phone with unsigned stuff/edited system (after flashing TWRP, so it could boot) that didn't work out. i think i found that information in some LineageOS thread here on XDA.
My ultimate goal would be to get a rooted stock nougat 7.1.1, up to date TWRP recovery and to be able to switch to LineageOS to try it out soon.
For what it is worth, i rooted many phones over the years, so while i'm no expert, i should be able to follow most of the steps you give me.
Thanks alot!
What version of TWRP did you flash first?
I have the same root problem i can not install in twrp install in twrp ok but su application displays no root cause i have latest twrp
KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one
KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one
Okay. Download and flash this one alone via fastboot and see what happens. This is one the I personally use. It is required for any of the newer versions to work properly.
twrp-3.0.2-2-a2017u.img
You can choose to rename it to just recovery.img, then:
1. fastboot flash recovery recovery.img
or
2.
if you choose to work with the same filename:
fastboot flash recovery twrp-3.0.2-2-a2017u.img
Select reboot to recovery from the bootloader menu now and try again.
Either way, should work fine. I know you mentioned you knew the basics, but just want to be sure.
Also forgot to mention. If TWRP works but you still can't get your phone to boot, you need to follow this guide here
You can start from the part that says:
-----------------------------------------------------
UPDATING FROM B20_Boot / B20 / B27 / B29 / B15(N)
-----------------------------------------------------
Again, that's the ROM I personally use if I want to go back to stock, not the one from the ZTE site.
Gonna try it and give feedback. thanks for taking time to help!
edit: im downloading the rom from the link you shared.
like you said, i can get TWRP to boot but not the phone.
So if i use full stock from ZTE, it can't boot with modified recovery?
edit 2: i don't know what worked, i think it might be the bootstack. or the rom by DrakenFX. now i can boot to the rom with a TWRP recovery installed. It worked, but i soft bricked again trying to flash SuperSU. So now i'm retrying with an updated TWRP.
I haven't tried that yet, but I really suspect that's the reason you're having problems. I rarely use pure stock ROMs. Like you, I'm not an expert in Android Development so I can't tell you why. Just been a flashaholic for years so made a few observations.
Which supersu are you installing? If you're swiping to the right in twrp, you need to install the dm-verity zip or supersu 2.79. There's some issues with newer builds.
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.
lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable
Click to expand...
Click to collapse
Glad you're up and running root. :good:
lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.
Click to expand...
Click to collapse
Yeah, like I mentioned before that was the base TWRP you needed to flash first, before any of the newer ones. You weren't intended to use it indefinitely.
There's a lot of Dev love for our device now and support is growing ... exciting new ROMs cropping up. Don't hesitate to try them out.
Hello,
I'm having big problems flashing any ROM on my Oneplus 5 atm.
At the beginning of this month, I wanted to unroot my rooted Android 8.0 or 8.1 (One of them, it was OxygenOS, but not the newest version)+ Xposed Oneplus 5.
I got a couple of errors, most of the time error 7.
After hours, old and new recoverys (TWRP) from blu_spark, codeworkx and some xda user recoverys and diffrent OxygenOS versions i finally managed it to install a Oxygen version with Android 7.1.1 on the phone. The Problem was: I always got errors (Installation failed) when I wanted to intall Software Updates no matter if I tryed it by myself or with the official system update in android.
So and today the official beta build of OxygenOS for 9.0 released and I was so stupid and thought I can make this an easy one.
Now I'm sitting here since 9:30am and try to flash Android 9, or any Android except 7.1.1 (only Oxygen Versions). Most of the Time i'm getting ERROR:7, it doesnt matter with which Recovery or Build.
When I got this problem at the first Time, my Phone was shown as "" (The error was something like: This Package is for a "Oneplus 5" this is a "").
When I get this scentence now (not every Recovery is showing it) it says my Phone is a "OnePlus5T", but i have a Oneplus 5.
Also (maybe partly) important things are:
- I tryed to edit the updater-script and delete the assets lines but there were no asset lines. Tryed it anyways and it didnt work. (and i really dont want to try this again)
I tryed to google this error for hours and many people meant that this is the way to go but I dont belive it. Isn't there any way to rename my phone, if yes: what do I have to do? I have TWRP and access to the command prompt aswell. If anyone can successfully create the 9.0 beta without the assets I would be happy but i dont think that is the solution for my problem, just a workaround.
- I think the problem is just something about my devices name. The strange part is that it accepted 7.1.1. And this was 100% a Oneplus 5 ROM.
- 7.1.1 isnt the way to go for me anymore. I dont like android 7 and it has so old security patches..
- Fingerprint sensor and screen got replaced
thank you for reading this and maybe helping me. I dont have the best language skills, if you need more Information about my Phone, please ask
EDIT1: As I said, 7.1.1 is still successfull, i tryed it a couple of mins ago. no error 7 or sth
maybe you can try revert to fully stock setup{without TWRP) and update to pie?
I have problem with error 7 when i tried to flash latest open beta (pie). I didn't find any solution.... :crying:
petryrety said:
I have problem with error 7 when i tried to flash latest open beta (pie). I didn't find any solution.... :crying:
Click to expand...
Click to collapse
Make sure the download isn't corrupt or if you extract the compatibility.zip use a recommended tool.
I had this problem couple of months ago. I solved it by flashing an old os version then flashing stock recovery(I don't remember if I locked the bootloader). boot in to the phone and download and update through ota( I did 3 updates this way). Then install twrp and root. Now I can flash any oos update without error 7.
May work
This is a post I wrote for another thread. I have found that this method fixes the error 7 issue, and allows you to update all the way to Pie without issues. When updating to Pie, use 7-Zip, not winrar or any other non-recommended programs to remove compatibility.zip from the firmware archive before flashing. I found that winrar causes treble errors or error 7.
https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13
iwantademo123 said:
This is a post I wrote for another thread. I have found that this method fixes the error 7 issue, and allows you to update all the way to Pie without issues. When updating to Pie, use 7-Zip, not winrar or any other non-recommended programs to remove compatibility.zip from the firmware archive before flashing. I found that winrar causes treble errors or error 7.
https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13
Click to expand...
Click to collapse
Yeah, that's what I wrote here https://forum.xda-developers.com/oneplus-5/help/massive-problems-error7-t3878372/post78503983 and in flashing instructions for open beta and stable builds in their first posts.
strongst said:
Yeah, that's what I wrote here https://forum.xda-developers.com/oneplus-5/help/massive-problems-error7-t3878372/post78503983 and in flashing instructions for open beta and stable builds in their first posts.
Click to expand...
Click to collapse
That's good, It's good advice. I am just stressing to everyone in this thread, how important it is to follow that and use a recommended tool to remove compatibility.zip because removing compatibility.zip sounds very trivial thing, but it's actually really important to use a tool like 7-Zip that doesn't break the firmware in the process.
Also, the link to my other post ( https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13 ) should be detailed and comprehensive enough to help people with error 7 in other scenarios or that are trying to update to oreo or other stock firmwares too. This method restores the phone back to factory condition, including all the partitioning. Updating with a locked bootloader can fix a lot of update errors. I've found that after 5.1.5 it is safe to unlock the bootloader and take updates. But as you mentioned, for an unlocked bootloader, compatibility.zip needs to be removed from the firmware archive, and a tool such as 7-Zip must be used to do so as other archive managers break the update entirely (with error 7).
Good luck everyone trying to update, hope our advice helps :good:
So I flashed OOS 5.0.1 then went back to stock recovery. I then locked my bootloader. After which I booted into OxygenOS and updated it all the way to pie(took 3 OTAs). Now I've got a locked bootloader and pie but I'm wondering if the process to unlock the bootloader is the same or different now that there is a vendor drive?
TurtleSandals said:
So I flashed OOS 5.0.1 then went back to stock recovery. I then locked my bootloader. After which I booted into OxygenOS and updated it all the way to pie(took 3 OTAs). Now I've got a locked bootloader and pie but I'm wondering if the process to unlock the bootloader is the same or different now that there is a vendor drive?
Click to expand...
Click to collapse
The unlocking process of the bootloader is the same!
I am having the exact same problem, tried everything from above. Can get anything more recent than 7.1.1 on my oneplus 5. evrything else is error 7. Any update
mathgerm said:
I am having the exact same problem, tried everything from above. Can get anything more recent than 7.1.1 on my oneplus 5. evrything else is error 7. Any update
Click to expand...
Click to collapse
Please see here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post79938097
Hello All,
I picked up a OP 6T from Amazon and would like to run Lineage 16.0 and load GApps, along with a number of other apps. I have TWRP Fajita (bluespark) installed and can boot to it. I also have Lineage 16 flashed as my ROM on Slot A, to which I can also successfully boot. I have Mind the GApps .zip ARM64 version on internal storage root.
Prior to flashing Lineage, I also loaded Magisk, which is still there as an app.
In trying to load MtheGApps, I cannot get past encryption in TWRP. TWRP prompts for a password, but I have no idea what that might be. I've read (somewhere) that the password is the pin I defined for my opening screen in Lineage, which I know. That does not work. I also have fingerprint enabled and have defined a print. The pin and finger get me into lineage without any trouble.
All of this is on slot A. Slot B seems to holds an older T-Mobile ROM, which I booted at some point. Not really interested in that, so eventually, I'll want to know what to do with that slot. I'll also want to root Lineage.
Maybe I should start from scratch? ( not sure how to get back there). Any guidance greatly appreciated!
It's like that because you didn't format data. Also you can't have OOS on one slot, and an AOSP ROM on another slot.
Here's the LOS install instructions I've been posting / using for clean / first installs.
Note the part in the begining about using 9.0.17 or 10.3.1 depending on which version of LOS you are using. Don't mix Android 10 and 9. Any questions ask.
Also note when Magisk is flashed those instructions. You're close, just missed a couple steps.
Next Steps...
OhioYJ said:
It's like that because you didn't format data. Also you can't have OOS on one slot, and an AOSP ROM on another slot.
Here's the LOS install instructions I've been posting / using for clean / first installs.
Note the part in the begining about using 9.0.17 or 10.3.1 depending on which version of LOS you are using. Don't mix Android 10 and 9. Any questions ask.
Also note when Magisk is flashed those instructions. You're close, just missed a couple steps.
Click to expand...
Click to collapse
OK, finally getting back to this...
I currently have LOS 16 and twrp fajita 3.2.3-2 onboard, as well as Magisk Manager (but not magisk - shows red question mark and "magisk not installed" in Magisk mgr.).
I want to go to LOS 17, load gapps and root to remove redundant apps.
First, I need to I need to get back to stock ROM before anything else, right? I've downloaded 10.0.1-OnePlus6TOxygen_34_OTA_041_all_1911142208_af338-FASTBOOT.zip
I'll also need LOS 17.X, correct? I have this: lineage-17.1-20200104_020517-UNOFFICIAL-fajita.zip
I'll need the Q version of TWRP, right? Still looking for that. Is this version of TWRP specific to the OP 6T, or specific to Android 10? Other?
I'll need the ARM64 , Android 10 version of mindthegapps (mindthegaps supports A/B architecture, right?). Still looking for that. I've found "GApps", but not "mindthegapps". There's also "bitgapps". Should I consider this?
I'll need magisk manager. magisk uninstaller and magisk, correct? I have MagiskManager-v7.5.1.apk, Magisk-v20.3.zip and Magisk-uninstaller-20200110.zip. Not sure if these are the right ones..
I think the main thing I need help with is getting back to the stock ROM. Guessing that would be OOS10. Once I get there, there are lots of instructions around on how to get to LOS 17.
Thank you!!
NoBodyUKnow said:
OK, finally getting back to this...
Click to expand...
Click to collapse
Your version of TWRP could be part of the problem. This is the thread for the official maintainer, use these builds of TWRP even though they say "unofficial." Q is for Android 10, Pie is for Android 9. For LOS 17, download the 3.3.1-32 versions. Remember you are booting the img files, the Q version, you use the same installer for both versions of Android.
To go to LOS 17 you need Android 10 on both slots. Doesn't matter how you get there. 10.3.1 is the latest version from OP, so there is technically a newer version than what you downloaded.
Fastboot ROM page.
You have a few options:
- You can also update using TWRP, and flashing the OTA full ZIP. Just be aware, you need to flash the OTA zip, flash the TWRP installer, reboot to recovery, flash the OTA zip again. Reboot. At this point the phone won't boot, it will just go to stock recovery, wipe data (factory reset), and it should boot up into OOS. Then boot your TWRP img, install TWRP, boot to recovery, start the LOS install I linked to above.
- Use the fastboot ROM. Again as above this will require TWRP installation, etc.
- My least favorite, the MSMTool. My opinion, is the MSMTool should always be a last resort as it locks your bootloader. You can unlocking afterwards again, but if something goes wrong, it could be a bad thing. I just always try every other option before jumping to this one.
As for Gapps, I just use OpenGapps. At this point you don't even have to mess with their test or beta folders anymore. You can just select it from their homepage, and download Android 10 gapps. OpenGapps page, the 6T is Arm64, LOS17 is Android 10, I always use Nano
As for Magisk, yes 20.3. The uninstaller you don't really need as this will essentially be a clean install. The 20.3 zip will also install the Magisk Manager app.
Hopefully that clears some things up?
NoBodyUKnow said:
OK, finally getting back to this...
I currently have LOS 16 and twrp fajita 3.2.3-2 onboard, as well as Magisk Manager (but not magisk - shows red question mark and "magisk not installed" in Magisk mgr.).
I want to go to LOS 17, load gapps and root to remove redundant apps.
First, I need to I need to get back to stock ROM before anything else, right? I've downloaded 10.0.1-OnePlus6TOxygen_34_OTA_041_all_1911142208_af338-FASTBOOT.zip
I'll also need LOS 17.X, correct? I have this: lineage-17.1-20200104_020517-UNOFFICIAL-fajita.zip
I'll need the Q version of TWRP, right? Still looking for that. Is this version of TWRP specific to the OP 6T, or specific to Android 10? Other?
I'll need the ARM64 , Android 10 version of mindthegapps (mindthegaps supports A/B architecture, right?). Still looking for that. I've found "GApps", but not "mindthegapps". There's also "bitgapps". Should I consider this?
I'll need magisk manager. magisk uninstaller and magisk, correct? I have MagiskManager-v7.5.1.apk, Magisk-v20.3.zip and Magisk-uninstaller-20200110.zip. Not sure if these are the right ones..
I think the main thing I need help with is getting back to the stock ROM. Guessing that would be OOS10. Once I get there, there are lots of instructions around on how to get to LOS 17.
Thank you!!
Click to expand...
Click to collapse
OhioYJ said:
It's like that because you didn't format data. Also you can't have OOS on one slot, and an AOSP ROM on another slot.
Here's the LOS install instructions I've been posting / using for clean / first installs.
Note the part in the begining about using 9.0.17 or 10.3.1 depending on which version of LOS you are using. Don't mix Android 10 and 9. Any questions ask.
Also note when Magisk is flashed those instructions. You're close, just missed a couple steps.
Click to expand...
Click to collapse
NoBodyUKnow said:
Hello All,
I picked up a OP 6T from Amazon and would like to run Lineage 16.0 and load GApps, along with a number of other apps. I have TWRP Fajita (bluespark) installed and can boot to it. I also have Lineage 16 flashed as my ROM on Slot A, to which I can also successfully boot. I have Mind the GApps .zip ARM64 version on internal storage root.
Prior to flashing Lineage, I also loaded Magisk, which is still there as an app.
In trying to load MtheGApps, I cannot get past encryption in TWRP. TWRP prompts for a password, but I have no idea what that might be. I've read (somewhere) that the password is the pin I defined for my opening screen in Lineage, which I know. That does not work. I also have fingerprint enabled and have defined a print. The pin and finger get me into lineage without any trouble.
All of this is on slot A. Slot B seems to holds an older T-Mobile ROM, which I booted at some point. Not really interested in that, so eventually, I'll want to know what to do with that slot. I'll also want to root Lineage.
Maybe I should start from scratch? ( not sure how to get back there). Any guidance greatly appreciated!
Click to expand...
Click to collapse
OhioYJ said:
Your version of TWRP could be part of the problem. This is the thread for the official maintainer, use these builds of TWRP even though they say "unofficial." Q is for Android 10, Pie is for Android 9. For LOS 17, download the 3.3.1-32 versions. Remember you are booting the img files, the Q version, you use the same installer for both versions of Android.
To go to LOS 17 you need Android 10 on both slots. Doesn't matter how you get there. 10.3.1 is the latest version from OP, so there is technically a newer version than what you downloaded.
Fastboot ROM page.
You have a few options:
- You can also update using TWRP, and flashing the OTA full ZIP. Just be aware, you need to flash the OTA zip, flash the TWRP installer, reboot to recovery, flash the OTA zip again. Reboot. At this point the phone won't boot, it will just go to stock recovery, wipe data (factory reset), and it should boot up into OOS. Then boot your TWRP img, install TWRP, boot to recovery, start the LOS install I linked to above.
- Use the fastboot ROM. Again as above this will require TWRP installation, etc.
- My least favorite, the MSMTool. My opinion, is the MSMTool should always be a last resort as it locks your bootloader. You can unlocking afterwards again, but if something goes wrong, it could be a bad thing. I just always try every other option before jumping to this one.
As for Gapps, I just use OpenGapps. At this point you don't even have to mess with their test or beta folders anymore. You can just select it from their homepage, and download Android 10 gapps. OpenGapps page, the 6T is Arm64, LOS17 is Android 10, I always use Nano
As for Magisk, yes 20.3. The uninstaller you don't really need as this will essentially be a clean install. The 20.3 zip will also install the Magisk Manager app.
Hopefully that clears some things up?
Click to expand...
Click to collapse
It did clear some things up, thank you. However, I still end up at the Qualcomm CrashDump Screen of Death. this happens at the very end of the process, after the second load of LOS 17 and TWRP Installer, while rebooting to recovery from the TWRP .img. I'm going to list every step I take and all of the files I use. There are a couple of places where I'm not sure I'm doing the right thing, and/or the outcome of that step is not as expected.
1. Download all of files:
TWRP Q .img
TWRP Installer
OP OS 10.3.1 Fastboot ROM
lineage-17.1-20200223_133843-UNOFFICIAL-fajita.zip
First step is to flash Oxygen 10 and TWRP Recovery to both slots. I unpack the OOS Fastboot ROM zip on my laptop, boot to my 6t's bootloader and connect that to my laptop. After making sure ADB/Fastboot sees the device, I run "flash-all.bat" by clicking on it. This seems to load OOS just fine. The phone boots to OOS and I turn the phone off.
(I've done all of this several times and there are variants: I've tried becoming a developer and turning on the advanced boot options in OOS 10, but I don't think that matters, as long as I can get back to the bootloader or recovery. Let me know if that is incorrect).
At this point, your instructions say
"reboot to recovery, flash the OTA zip again."
I've tried moving the OOS fastboot zip file to my phone and flashing from TWRP, but that doesn't work. I get an error complaining of wrong format. It seems to me, a Fastboot ROM can only be flashed from adb/flashboot. Is that correct?
Therefore, I have been going back to the bootloader and re-flashing OOS 10 from adb fastboot again. After this step, contrary to your guidance above, the phone does indeed boot directly to OOS.... A loooong, what seems to be initial boot. I then turn off the phone.
I reboot to recovery again - and it is now the stock recovery - so I follow your guidance to factory reset from there. It does boot into OOS, and it is another looonnng boot. I then turn off the phone, return to the bootloader, flash the TWRP .img, install the TWRP installer and move on to the LOS 17 process linked to above.
Though I'm not sure it's necessary, I follow these steps from the beginning of he process:
Install 10.3.0 fastboot ROM again to start over, boot it once. Just to make sure everything is good.
- Reboot to fastboot.
- Boot the Q image of TWRP.
- Run the TWRP installer, reboot to recovery
Everything seems to work well, so I follow these steps, all from TWRP:
- Factory reset (This is the slider at the bottom in the wipe menu).
- Format data. (This is the button that says Format data in the wipe menu)
- Do NOT wipe cache, do not Wipe system, do NOT Wipe Dalvik / ART, do not add anything else, Just Factory Reset and Format Data. After doing those two Reboot to Recovery one more time. You must do this after formatting data.
I do all of the steps below, with no problems:
- Now transfer Lineage and TWRP to your phone, Windows / Linux should see TWRP fine as a media device when plugged in.
- Install Lineage
Just a note at this point, to highlight that this is done from TWRP, as opposed to using adb fastboot as with OOS10. This is what I've done with ROM's in the past; the fastboot ROM thing is new to me.
Next, I
- Run the TWRP Installer.
- Reboot to Recovery.
- Install Lineage (You need Lineage on both slots, so yes run it again)
- Run the TWRP Installer (yes again).
- Reboot to Recovery
This is where things go bad. In this reboot to recovery, the TWRP splash screen sits there for a long time, and then the Qualcomm CrashDump Screen of Death (QCDSoD) appears. If I hold the power button down for long time, the QCDSoD disappears and the phone reboots and starts to load LOS. Then, it switches to TWRP splash screen, and as before, end with the QCCDSoD.
I've been through this entire process maybe three times. Always the same outcome (you know what they say, about doing the same things and expecting different results...)
I did note, that on the OS Fastboot ROM page, there was some discussion of "Branded" phones, specifically T-Mobile phones. When I first got this phone, after loading TWRP, I swapped active slots. On the new, active slot, I booted the phone, and it was to a T-Mobile ROM. Not sure if that plays any part in all of this.
Appreciate your hanging with me. I'm going to rest my fingers
Is this a TMobile 6T?
NoBodyUKnow said:
OK, finally getting back to this...
I currently have LOS 16 and twrp fajita 3.2.3-2 onboard, as well as Magisk Manager (but not magisk - shows red question mark and "magisk not installed" in Magisk mgr.).
I want to go to LOS 17, load gapps and root to remove redundant apps.
First, I need to I need to get back to stock ROM before anything else, right? I've downloaded 10.0.1-OnePlus6TOxygen_34_OTA_041_all_1911142208_af338-FASTBOOT.zip
I'll also need LOS 17.X, correct? I have this: lineage-17.1-20200104_020517-UNOFFICIAL-fajita.zip
I'll need the Q version of TWRP, right? Still looking for that. Is this version of TWRP specific to the OP 6T, or specific to Android 10? Other?
I'll need the ARM64 , Android 10 version of mindthegapps (mindthegaps supports A/B architecture, right?). Still looking for that. I've found "GApps", but not "mindthegapps". There's also "bitgapps". Should I consider this?
I'll need magisk manager. magisk uninstaller and magisk, correct? I have MagiskManager-v7.5.1.apk, Magisk-v20.3.zip and Magisk-uninstaller-20200110.zip. Not sure if these are the right ones..
I think the main thing I need help with is getting back to the stock ROM. Guessing that would be OOS10. Once I get there, there are lots of instructions around on how to get to LOS 17.
Thank you!!
Click to expand...
Click to collapse
OhioYJ said:
It's like that because you didn't format data. Also you can't have OOS on one slot, and an AOSP ROM on another slot.
Here's the LOS install instructions I've been posting / using for clean / first installs.
Note the part in the begining about using 9.0.17 or 10.3.1 depending on which version of LOS you are using. Don't mix Android 10 and 9. Any questions ask.
Also note when Magisk is flashed those instructions. You're close, just missed a couple steps.
Click to expand...
Click to collapse
NoBodyUKnow said:
Hello All,
I picked up a OP 6T from Amazon and would like to run Lineage 16.0 and load GApps, along with a number of other apps. I have TWRP Fajita (bluespark) installed and can boot to it. I also have Lineage 16 flashed as my ROM on Slot A, to which I can also successfully boot. I have Mind the GApps .zip ARM64 version on internal storage root.
Prior to flashing Lineage, I also loaded Magisk, which is still there as an app.
In trying to load MtheGApps, I cannot get past encryption in TWRP. TWRP prompts for a password, but I have no idea what that might be. I've read (somewhere) that the password is the pin I defined for my opening screen in Lineage, which I know. That does not work. I also have fingerprint enabled and have defined a print. The pin and finger get me into lineage without any trouble.
All of this is on slot A. Slot B seems to holds an older T-Mobile ROM, which I booted at some point. Not really interested in that, so eventually, I'll want to know what to do with that slot. I'll also want to root Lineage.
Maybe I should start from scratch? ( not sure how to get back there). Any guidance greatly appreciated!
Click to expand...
Click to collapse
OhioYJ said:
Is this a TMobile 6T?
Click to expand...
Click to collapse
After a little research, it appears that it is a T-Mobile variant: the A6013. And, well.... I guess this may be a clue...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm guessing this is the source of my problem. Do you agree?
My research suggests the T-Mobile variant can be converted to "Global", but I'm wondering if it may just be more efficient to return this phone to Amazon with OOS 9 or 10 on it and buy the Global variant (A6010?)
NoBodyUKnow said:
I'm guessing this is the source of my problem. Do you agree?
My research suggests the T-Mobile variant can be converted to "Global", but I'm wondering if it may just be more efficient to return this phone to Amazon with OOS 9 or 10 on it and buy the Global variant (A6010?)
Click to expand...
Click to collapse
Yeap, you have a TMobile 6T. A TMobile 6T is not a Global 6T, and even a "converted" TMobile 6T is not a Global 6T. They still require special instructions at points, and do different things. The instructions above will work perfect for a Global 6T. They (TMobile 6Ts) tend to be cheaper, but tend to have some gotchas with them.
OhioYJ said:
Yeap, you have a TMobile 6T. A TMobile 6T is not a Global 6T, and even a "converted" TMobile 6T is not a Global 6T. They still require special instructions at points, and do different things. The instructions above will work perfect for a Global 6T. They (TMobile 6Ts) tend to be cheaper, but tend to have some gotchas with them.
Click to expand...
Click to collapse
Thanks! I like the 6T, so I guess I'm gonna get a Global. I'll get back to this, when I have that phone in-hand. Will slowly chug away on my Moto G6 until then. More to come...
Oh... Should I have any trouble putting an Oxygen 9 ROM ( or 10) on both slots without TWRP, before sending it back? Guess I'll need to re-lock the bootloader too.
NoBodyUKnow said:
Oh... Should I have any trouble putting an Oxygen 9 ROM ( or 10) on both slots without TWRP, before sending it back? Guess I'll need to re-lock the bootloader too.
Click to expand...
Click to collapse
You could always use a T-Mobile MSM Tool ?
Link
MSM Tools are usually my last resort as they relock the bootloader, but in this case, it's what you are after.
OhioYJ said:
Yeap, you have a TMobile 6T. A TMobile 6T is not a Global 6T, and even a "converted" TMobile 6T is not a Global 6T. They still require special instructions at points, and do different things. The instructions above will work perfect for a Global 6T. They (TMobile 6Ts) tend to be cheaper, but tend to have some gotchas with them.
Click to expand...
Click to collapse
NoBodyUKnow said:
Thanks! I like the 6T, so I guess I'm gonna get a Global. I'll get back to this, when I have that phone in-hand. Will slowly chug away on my Moto G6 until then. More to come...
Click to expand...
Click to collapse
OK... Back this this!
This is the what I ordered to replace the T-Mobile variant I had. It arrived yesterday. Is this the "global" model, or did I again purchase the wrong phone?
This phone is a dual sim, so it is definitely different from the one I had. Model number from System Info is A6010_41_200115.
Behavior is exactly as before. First, I'm loading the Android 10 version of the OP Oxygen Rom. After the second install of the OTA as advised below...
- You can also update using TWRP, and flashing the OTA full ZIP. Just be aware, you need to flash the OTA zip, flash the TWRP installer, reboot to recovery, flash the OTA zip again. Reboot. At this point the phone won't boot, it will just go to stock recovery, wipe data (factory reset), and it should boot up into OOS. Then boot your TWRP img, install TWRP, boot to recovery, start the LOS install I linked to above.
...rather than going directly to stock recovery, the phone DOES boot to OOS. To get to recovery, I go through the minimal necessary setup steps to access the settings, so I can activate developer mode, enable advanced reboot and enable USB debug. Then I reboot to recovery (stock), perform the wipe and reset. I then reboot to Fastboot and flash the TWRP .img using adb/fastboot on my PC. I then txfr the TWRP install .zip to root and install that. All of this SEEMS to go well, but again, there's that unexpected reboot to OOS as highlighted above.
Next, I move on to the LOS 17 load.
This goes well, until I complete the second load of TWRP Installer and reboot to recovery. When I execute that step, the TWRP splash screen appears and stays there for 30-45 seconds, and then turns to the QualComm CrashDump Mode Screen.
:crying:
I guess the first thing is to determine, If I have the correct phone ....
NoBodyUKnow said:
OK... Back this this!
This is the what I ordered to replace the T-Mobile variant I had. It arrived yesterday. Is this the "global" model, or did I again purchase the wrong phone?
This phone is a dual sim, so it is definitely different from the one I had. Model number from System Info is A6010_41_200115.
Behavior is exactly as before. First, I'm loading the Android 10 version of the OP Oxygen Rom. After the second install of the OTA as advised below...
- You can also update using TWRP, and flashing the OTA full ZIP. Just be aware, you need to flash the OTA zip, flash the TWRP installer, reboot to recovery, flash the OTA zip again. Reboot. At this point the phone won't boot, it will just go to stock recovery, wipe data (factory reset), and it should boot up into OOS. Then boot your TWRP img, install TWRP, boot to recovery, start the LOS install I linked to above.
...rather than going directly to stock recovery, the phone DOES boot to OOS. To get to recovery, I go through the minimal necessary setup steps to access the settings, so I can activate developer mode, enable advanced reboot and enable USB debug. Then I reboot to recovery (stock), perform the wipe and reset. I then reboot to Fastboot and flash the TWRP .img using adb/fastboot on my PC. I then txfr the TWRP install .zip to root and install that. All of this SEEMS to go well, but again, there's that unexpected reboot to OOS as highlighted above.
Next, I move on to the LOS 17 load.
This goes well, until I complete the second load of TWRP Installer and reboot to recovery. When I execute that step, the TWRP splash screen appears and stays there for 30-45 seconds, and then turns to the QualComm CrashDump Mode Screen.
:crying:
I guess the first thing is to determine, If I have the correct phone ....
Click to expand...
Click to collapse
So if I get this right, you're trying to install LOS 17 on your OnePlus 6T which is running OOS 10? Also you have the international variant.
DarthVader said:
So if I get this right, you're trying to install LOS 17 on your OnePlus 6T which is running OOS 10? Also you have the international variant.
Click to expand...
Click to collapse
He's got the China version this time, which I believe is minus a couple LTE bands (not a deal breaker necessarily, but not ideal). Does this change his install process since it would have originally had HOS on it?
Yes, but...
DarthVader said:
So if I get this right, you're trying to install LOS 17 on your OnePlus 6T which is running OOS 10? Also you have the international variant.
Click to expand...
Click to collapse
Yes, my goal is to have Lineage OS 17 (Android 10/Q) on a OnePlus 6T. Hopefully on the phone I have now, but on whatever 6T variant I need to get. I like the phone.
I tried before with a T-Mobile version of the A6013, and I could not get there. @OhioYJ offered some assistance and suggested the problem was the phone being a T-Mobile variant; that I needed a "Global" version. Therefore, I returned that phone and purchased an "International" A6010_41_200115. Is this the Global variant?
I've followed the processes detailed above on both phones and wound up at exactly the same place: The QUALCOMM CrashDump Mode screen. This happens after the second install of TWRP, when I reboot to Recovery.
In both cases, the phones came with OOS 9, and I'm updating to OOS10 via the Fastboot ROM before proceeding to LOS 17.
Is it possible to get to LOS 17 on the phone I have now?
Thanks!!!
OhioYJ said:
He's got the China version this time, which I believe is minus a couple LTE bands (not a deal breaker necessarily, but not ideal). Does this change his install process since it would have originally had HOS on it?
Click to expand...
Click to collapse
This would be the global variant, wouldn't it? An A6013 with both GSM and CDMA...?
Mine is an A6013, I checked the phone and original box. I bought mine straight from OnePlus. TMobile ones will only have a single IMEI. The "Real" 6T will be dual sim and have two separate, unique IMEI numbers.
NoBodyUKnow said:
This would be the global variant, wouldn't it? An A6013 with both GSM and CDMA...?
Click to expand...
Click to collapse
Do this. Download the latest OOS 10.3.2 from OnePlus's Website. As well as latest Unofficial TWRP Image and Installer. Grab the Q Image, not the Pie one. The latest TWRP version as of now is 3.3.1-32. Now Boot to TWRP. Flash the OOS ZIP File and then TWRP Installer. Reboot to Recovery and again flash the OOS ZIP and TWRP Installer. Once that's done, you can once again Reboot to Recovery. Now, flash the Latest LineageOS 17.1 ZIP file and TWRP Installer. Reboot to Recovery one last time and flash Gapps. After that Format Data and Reboot System. You should now hopefully boot into Android.
DarthVader said:
Do this. Download the latest OOS 10.3.2 from OnePlus's Website. As well as latest Unofficial TWRP Image and Installer. Grab the Q Image, not the Pie one. The latest TWRP version as of now is 3.3.1-32. Now Boot to TWRP. Flash the OOS ZIP File and then TWRP Installer. Reboot to Recovery and again flash the OOS ZIP and TWRP Installer. Once that's done, you can once again Reboot to Recovery. Now, flash the Latest LineageOS 17.1 ZIP file and TWRP Installer. Reboot to Recovery one last time and flash Gapps. After that Format Data and Reboot System. You should now hopefully boot into Android.
Click to expand...
Click to collapse
@OhioYJ
I did as you suggested. As with my first phone (a T-Mobile variant), when I perform the reboot to recovery after flashing LOS 17 and TWRP, the TWRP intro screen appears for a long time ( 30 seconds + ). When it finally disappears, the Qual. Crash Dump Screen appears. By holding the power button for about 10 seconds, the phone reboots to LOS. After booting, I can navigate within LOS, but a warning flashes for a few milliseconds, about every ten seconds. I was able to capture a screenshot of the warning from the video I just linked to:
This continues to occur: if I try to reboot to recovery, the TWRP screen appears, lingers and then changes to the Qual Crash Dump screen. At this point, when I hold the power button for about 10 seconds, the phone boots to LOS. When LOS is running, the warning continues to appear at regular intervals.
Thinking I may just go for another phone, preferably one that supports GSM and CDMA, but at least a US, non-T-mobile phone with all of the GSM Bands. They are a little pricey though.
Happy to try other things with this phone though, if it might help further understanding of these phones.
Looking for w Breakthrough...
@OhioYJ @DarthVader
Gentleman,
I hope this update finds you and your loved ones safe, in this scary time.
I am still trying to get LOS 17 on my OP 6T, and I Keep ending up at the same place.: Qualcomm CrashDump Screen. l'm using the fastboot ROM's, and using those does not completely align with this part of OhioYJ's instructions:
- You can also update using TWRP, and flashing the OTA full ZIP. Just be aware, you need to flash the OTA zip, flash the TWRP installer, reboot to recovery, flash the OTA zip again. Reboot. At this point the phone won't boot, it will just go to stock recovery, wipe data (factory reset), and it should boot up into OOS. Then boot your TWRP img, install TWRP, boot to recovery, start the LOS install I linked to above.
OhioYJ mentions "flashing the OTA Full .zip". The Fastboot ROM's have "OTA" in their labels and they are .zip files, but they will not flash in TWRP. They error out. They do run - and flash - from the bootloader, and this is what I've been doing. I'm guessing there are other, TWRP flasheable .zip files for the 6T. Maybe I should try those? Can't seem to find them. If so, can you point them out to me, please?
I humbly ask that you review this thread, looking closely at your guidance and my responses. I keep ending up at the same place - the Qualcom CrashDump Mode Screen.
Thanks!
NBUK
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
Hi
I fixed my oneplus 5 using MSMdownload tool. It put my phone on Android 7.1.1 with July 1st, 2017 security Patch and Oxygen OS 4.5.8, I have exhausted all the option to upgrade it to latest Android but it won't update. Every time I check for update it will show that it is up to date. I have also tried "local Upgrade" option but it shows installation failed.
Any work around this would be highly appreciated
Thanks
Aman
@lucider14 Just curious why you used the MSMDownloadTool from OxygenOS 4.5.8 and not the one for OxygenOS 9.0.11? You most likely won't see OTAs for Android 7 as it is now 4 Android Versions behind as of this week. Android 9.0.11 was the last official fully released OTA, OxygenOS 10.0.0 Hotfix is last official OTA OnePlus has released into the wild.
My phone waa bricked so had to use it. Please let me know if there is any workaround for this to update.
@lucider14 The workarounds I would try are:
Opt 1: Upgrade via zip file in Stock Recovery
Step 1: Download latest OTA from https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Step 2: Copy zip file to root of Phone storage
Step 3: Reboot into Recovery
Step 4: Install
Opt 2: Use Newer MSMDownloadTool:
Step 1: Download newest tool from here https://forum.xda-developers.com/oneplus-5/how-to/op5-collection-unbrick-tools-t3898870
Step 2: Reboot phone into EDL
Step 3: Run newer MSMDownloadTool
card13;83478941 [user=11104643 said:
@lucider14[/user] The workarounds I would try are:
Opt 1: Upgrade via zip file in Stock Recovery
Step 1: Download latest OTA from https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Step 2: Copy zip file to root of Phone storage
Step 3: Reboot into Recovery
Step 4: Install
Opt 2: Use Newer MSMDownloadTool:
Step 1: Download newest tool from here https://forum.xda-developers.com/oneplus-5/how-to/op5-collection-unbrick-tools-t3898870
Step 2: Reboot phone into EDL
Step 3: Run newer MSMDownloadTool
Click to expand...
Click to collapse
@lucider14 OOS 4.5.8 is pre-treble. You can't jump directly to Android 9 or 10. One of the OOS updates before Android 9 set up treble on our phones. I don remember exactly which one. You're best to use Opt 2 above, it will be easier.
Cheers!?
lucider14 said:
Hi
I fixed my oneplus 5 using MSMdownload tool. It put my phone on Android 7.1.1 with July 1st, 2017 security Patch and Oxygen OS 4.5.8, I have exhausted all the option to upgrade it to latest Android but it won't update. Every time I check for update it will show that it is up to date. I have also tried "local Upgrade" option but it shows installation failed.
Any work around this would be highly appreciated
Thanks
Aman
Click to expand...
Click to collapse
First,flash it 9.0.11 build and then OxygenOS 10.0.0 Hotfix..
And with https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater
I've had a similar problem and I thought I broke my phone, got pretty scared can't buy a new phone but need a newer android for my apps to work.
I came from freedom OS on android 7 so I never had the project treble on my phone and tried to flash new factory images, as a result, no newer TWRP recovery worked and I was unable to boot into anything other than the bootloader. I had the same error with Error 7, from what I can understand this is from a screwed up or non-existing "vendor" partition which says stuff like "this is a OnePlus 5" for newer factory images to install (factory image told me I didn't have a OP5), this never existed in android 7 or OOS 4.X.X. ScRuFFy7 is correct, the vender partition was created in OOS 5.1.4 (or OTA 037) and only when android is booting up, this took like 10 mins on mine. Once this vendor partition is correctly created you can flash newer TWRP recovery (I flashed 3.4.0) and newer factory images, like OOS 9.0.11 then to version 10. The built-in updater and stock recovery can update to the newer versions with the flashable zip files. For whatever reason OnePlus don't size the partitions in their zips so they make small changes from one version to the next so skipping specfic versions throws up errors in the future.
Screw it, I should document what I did in case I mess up my phone in the future and maybe be helpful to someone else in need, especially in this messed up and depressing time of the plague. But anyway this is what I did to get my phone back, I should point out I have no idea what I'm doing. Meaning I'm a N00b.
NOTE: this process Wipes all the data from the phone, so I hope you have backups right now.
Will need ADB, you can install This on windows, it's super easy and works thanks to mauronofrio. You can get the all in one tool too from here it's pretty handy and can format and decrypt from the bootloader, from mauronofrio? I think? This guy is pretty good. I got all old firmware from Here thanks to Some_Random_Username for the life line since OnePlus won't provide the old Zips anymore.
1) Boot to TWRP recovery if you have it installed (VOL DOWN + POWER). If not Boot to Bootloader (VOL UP + POWER) and flash TWRP Recovery. You can use TWRP 3.1.1 This one works on OOS 4.X firmware without giving me a Black Screen.
1a) To Flash the Recovery you can use the all in one tool to flash it or open up command prompt and use the Fastboot Flash [insert recovery file name here .img] command to flash it, you can find the FastBoot Flashing Method in the middle of this page for instructions.
2) Format Data. The Format Data button in TWRP recovery not the swipe to factory reset, because we're going back to scratch.
3) Flash OTA_006 (OOS 4.5.2) original firmware from the link above (says ota_006 in the middle of the loong file name)
4) Boot into android and use System Update in settings and stock recovery it just flashed to flash OTA_020 (OOS 4.5.15) by clicking on the cogwheel in the corner and choosing Local Update. [probably skippable I just wanted to make sure it works]
5) Boot into android again and install OTA_27 (OOS 5.0) with System Update again.
6) If it doesn't boot, go to Bootloader and flash TWRP. Once in the recovery and you go to install and if you find all the folders have random numbers and letters for names then the storage in encrypted.
7) Format to get rid of encryption (random name folders) then reboot to Recovery and Flash OTA_27 again and let it start fresh on OOS 5.0 to make sure it's still booting and working.
8) Once booted Flash OTA_037 (OOS 5.1.4) wait for vendor partition to be created (took 10 mins on my OP5), reboot to TWRP and format if folders are encrypted and reflash OTA_037 if needed.
Once booted into android this is the point where you should have the Vendor Partition already created by the factory image, you can go back into TWRP (flash TWRP if needed) and under Mount be able to see, mount/unmount a Vendor partition without errors. This should solve the Error 7 problem with factory images. A newer version of TWRP Recovery should work now, I installed 3.4.0 from mauronofrio Here. 3.4.0 works with android 10.0 so I was glad.
9) Boot android again and flash OTA_038 (OOS 5.1.5) just to make sure with stock recovery. [Probably skippable but I was a Paranoid Android at this point, just to make sure it still works]
10) Boot to android again and install OTA_042 (OOS 9.0.0) with System Update to keep making sure it works. [Again, I was Paranoid. Probably Skippable]
11) Boot to android again and install OTA_054 (OOS9.0.11) as last Android 9 update to have things set up ok.
12) Boot into Android again and install the latest android 10 from OnePlus (OTA_068) with System Update and the Stock Recovery, this is Android 10.0.0 and OOS 10.0.0. Things should work fine at this point but I doubt the check for update will get new oneplus updates. As of Sep 25, 2020 it is up to date. Technically.
I should add something else I discovered after. I found a flashable zip file from one of the lineage OS posts of a oneplus5_vendor_5.1.5.zip Here. You might be able to just use that to create the Vendor partition then just Flash one of the OOS 5.X Firmwares and go from there, I've not tried it so I'm not 100% sure but it's a possibility?
Hope this is helpful to someone at some point in time. for troubleshooting at least. Honestly really glad I have a working phone right now.