TWRP compatible with Android 12? - OnePlus 8T Questions & Answers

Hey Everyone,
I'm looking to try LOS 19.1 for the first time on my new OP8T.
I always see TWRP as a suggestion for the best custom recovery, but on the download page "twrp-installer-3.7.0_11-0-kebab.zip" is the file name. I'm confused, as the 11-0 means it's for Android 11, but I saw that TWRP 3.7.0 is supposed to support Android 12.
Can I use TWRP for installing LOS 19.1 on Android 12 or should I use the LOS-recovery?
And if I do, can I still use Magisk (on their page they say to use TWRP)?
Sorry for this newbie question. Thanks in advance!!
All the best

The official TWRP doesn't support A12.
Use the unofficial one from https://forum.xda-developers.com/t/...in-recovery-project-8t-9r-2022-07-27.4473983/

henschn3435 said:
Hey Everyone,
I'm looking to try LOS 19.1 for the first time on my new OP8T.
I always see TWRP as a suggestion for the best custom recovery, but on the download page "twrp-installer-3.7.0_11-0-kebab.zip" is the file name. I'm confused, as the 11-0 means it's for Android 11, but I saw that TWRP 3.7.0 is supposed to support Android 12.
Can I use TWRP for installing LOS 19.1 on Android 12 or should I use the LOS-recovery?
And if I do, can I still use Magisk (on their page they say to use TWRP)?
Sorry for this newbie question. Thanks in advance!!
All the best
Click to expand...
Click to collapse
3.7.0 is recovery release version and 11-0 means it's for Android 11.

BillGoss said:
The official TWRP doesn't support A12.
Use the unofficial one from https://forum.xda-developers.com/t/...in-recovery-project-8t-9r-2022-07-27.4473983/
Click to expand...
Click to collapse
The download link in that unofficial one forum OP presents a lemonade (Oneplus 9) TWRP...
Am I missing something? @BillGoss : do you have the download link for an OOS12 supported Oneplus 8T TWRP (that preferably can make (and restore) backups since Orangefox one can't make backups (it errors))?

Dior DNA said:
The download link in that unofficial one forum OP presents a lemonade (Oneplus 9) TWRP...
Am I missing something? @BillGoss : do you have the download link for an OOS12 supported Oneplus 8T TWRP (that preferably can make (and restore) backups since Orangefox one can't make backups (it errors))?
Click to expand...
Click to collapse
It works on both the 8T and the 9 9R. If you want to be sure try to boot into it before flashing.

Dior DNA said:
The download link in that unofficial one forum OP presents a lemonade (Oneplus 9) TWRP...
Am I missing something? @BillGoss : do you have the download link for an OOS12 supported Oneplus 8T TWRP (that preferably can make (and restore) backups since Orangefox one can't make backups (it errors))?
Click to expand...
Click to collapse
TheNewHEROBRINE said:
It works on both the 8T and the 9. If you want to be sure try to boot into it before flashing.
Click to expand...
Click to collapse
If you look at the title of that thread you'll notice that it says "TeamWin Recovery Project (8T / 9R)".
So, yes, it's for both the 8T and 9R (lemonades) but not the 9 (lemonade).

BillGoss said:
If you look at the title of that thread you'll notice that it says "TeamWin Recovery Project (8T / 9R)".
So, yes, it's for both the 8T and 9R (lemonades) but not the 9 (lemonade).
Click to expand...
Click to collapse
OK thanks ! lemonade versus lemonades ... I did not know about this subtle name difference
The recovery image boots indeed. I would like to make backups...
Unfortunately the backup (of LOS 19.1) fails with similar message as Orangefox with:
createTarFork() process ended with ERROR: 255

Dior DNA said:
OK thanks ! lemonade versus lemonades ... I did not know about this subtle name difference
The recovery image boots indeed. I would like to make backups...
Unfortunately the backup (of LOS 19.1) fails with similar message as Orangefox with:
createTarFork() process ended with ERROR: 255
Click to expand...
Click to collapse
Can you share the full log?

TheNewHEROBRINE said:
Can you share the full log?
Click to expand...
Click to collapse
sure, give me another day ...I just deleted the Orangefox and TWRP directories

Dior DNA said:
OK thanks ! lemonade versus lemonades ... I did not know about this subtle name difference
The recovery image boots indeed. I would like to make backups...
Unfortunately the backup (of LOS 19.1) fails with similar message as Orangefox with:
createTarFork() process ended with ERROR: 255
Click to expand...
Click to collapse
That happens if you have files under /data/fonts/files/, but you would need to check the recovery.log to confirm that is what's causing the problem.

BillGoss said:
That happens if you have files under /data/fonts/files/, but you would need to check the recovery.log to confirm that is what's causing the problem.
Click to expand...
Click to collapse
Thanks all! One should perhaps forbid files under /data/fonts/files/ ... After deleting those, I could finish both (unofficial) Orangefox and (unofficial) TWRP backup just fine. Agreed, this does not 100% prove ERROR root cause but sure does consistently correlate. So now maybe one should harden custom recovery images to avoid the trap, especially since the trap seems to be a known one by some people (like @BillGoss).

BillGoss said:
That happens if you have files under /data/fonts/files/, but you would need to check the recovery.log to confirm that is what's causing the problem.
Click to expand...
Click to collapse
BTW, do you know the reason why files inside fonts/files folder prevent backup process from going?

Rootk1t said:
BTW, do you know the reason why files inside fonts/files folder prevent backup process from going?
Click to expand...
Click to collapse
No, I never understood what the problem was with those files.

BillGoss said:
No, I never understood what the problem was with those files.
Click to expand...
Click to collapse
When installing ota zips from TWRP, оne should restore stock boot and recovery because checks are inside ota zips?

Rootk1t said:
When installing ota zips from TWRP, оne should restore stock boot and recovery because checks are inside ota zips?
Click to expand...
Click to collapse
Correct, but only in incremental updates.
But I don't think the current TWRP can process OOS incremental updates - the last time I tried I got an error.

BillGoss said:
Correct, but only in incremental updates.
But I don't think the current TWRP can process OOS incremental updates - the last time I tried I got an error.
Click to expand...
Click to collapse
BillGoss said:
Flashing OTA zips - both full and incremental. Note: incremental OTAs need stock boot and recovery installed so make sure you flash these before starting the install, otherwise it will fail.
Click to expand...
Click to collapse
Has something changed from your post?

Rootk1t said:
Has something changed from your post?
Click to expand...
Click to collapse
Lol! I think I'm going senile!
Given that I tend to test before making statements like the one you quoted, I'd say that that is correct for the 1-4 version of TWRP.
But it may not be true for 1-5 as I've found some issues with it (eg, fastbootd doesn't work) and I've not fully tested flashing otas with 1-5.

BillGoss said:
Lol! I think I'm going senile!
Given that I tend to test before making statements like the one you quoted, I'd say that that is correct for the 1-4 version of TWRP.
But it may not be true for 1-5 as I've found some issues with it (eg, fastbootd doesn't work) and I've not fully tested flashing otas with 1-5.
Click to expand...
Click to collapse
Thanks for letting us know

Rootk1t said:
Thanks for letting us know
Click to expand...
Click to collapse
I went hunting and I found the conversation where I flagged the problem with flashing OTAs on the latest TWRP (on the TWRP development site):
I wanted to test using TWRP to install an OTA zip on OOS 12. The first time I tried I got an error because it was expecting the current version to match those of C.33 but they didn't - even though I was on C.33. So I used `resetprop` to set the proper values and then it sort of worked, but still gave errors.
I was using the latest version (1.5 or 220827) of TWRP.
Click to expand...
Click to collapse
And now I'm wondering how correct my statement about flashing OTAs working on the previous version. I'll have to do some more digging to see if I can find solid proof of OTA working on TWRP 12 v1.4.
Update: I found where I tested flashing OTAs on TWRP 12. That was back on 220805. That was before 1.4 came out (220818). But I didn't expect that this function would get broken, so I never actually tested on 1.4.

BillGoss said:
I went hunting and I found the conversation where I flagged the problem with flashing OTAs on the latest TWRP (on the TWRP development site):
And now I'm wondering how correct my statement about flashing OTAs working on the previous version. I'll have to do some more digging to see if I can find solid proof of OTA working on TWRP 12 v1.4.
Update: I found where I tested flashing OTAs on TWRP 12. That was back on 220805. That was before 1.4 came out (220818). But I didn't expect that this function would get broken, so I never actually tested on 1.4.
Click to expand...
Click to collapse
So as i understood correctly flashing OTAs in TWRP is broken on v1.4 and works on prior versions?

Related

[RECOVERY] [F1f-Spectrum] [TWRP-3.1.1-0] For Project Spectrum Bootloader ONLY!

This is an unofficial port of TWRP Recovery for the Oppo F1F on Project Spectrum Bootloader. Much Thanks and credit goes to the TWRP team, Lineage team, and brinleyaus for making this possible. This will allow flashing of modification zips (eg. supersu, magisk, xposed, etc) over the top of Project Spectrum or flashing spectrum based ROMS.
Instructions:
Already running Project Spectrum
- If you haven't already unlocked you bootloader you will need to go into SETTINGS > ABOUT PHONE and tap BUILD NUMBER 7 times to unlock DEVELOPER OPTIONS, Then go into SETTINGS > DEVELOPER OPTIONS and enable them, also enable ADB DEBUGGING and OEM UNLOCK. Now reboot into fastboot (adb reboot bootloader) and run fastboot oem unlock.
- Install this image file through fastboot (If you are unsure of this step follow one of the many tutorials about installing TWRP through fastboot)
On ColourOs with TWRP
- Do a full wipe first or the install will fail. (In TWRP hit WIPE then swipe to factory reset.) Do a backup first as you will lose data.
- Flash this zip file through twrp and then hit "wipe dalvic and cache", then hit HOME then REBOOT then RECOVERY. (rebooting to the new recovery will ensure the recovery sticks) then Flash any Spectrum based rom or restore any Spectrum based backup. NOTE the ColorOs system and boot.img will still be there but wont boot so you MUST flash or restore a Spectrum based rom before you reboot to system.
Reserved.
MiniBlu said:
Reserved.
Click to expand...
Click to collapse
Battery can't charge full!! Help ?
Added file and instructions to OP to flash Spectum bootloader,firmware and twrp From ColorOs TWRP.
Thank.link from androidfilehost is slowly. I using wifi
Sent from my F1w using XDA-Developers Legacy app
MiniBlu said:
Added file and instructions to OP to flash Spectum bootloader,firmware and twrp From ColorOs TWRP.
Click to expand...
Click to collapse
The TWRP is not the 3.1.1
It is the 3.0.1
khannz7 said:
The TWRP is not the 3.1.1
It is the 3.0.1
Click to expand...
Click to collapse
Which file are you talking about, I just checked the links and the flashable zip was actually pointing to the full ROM which defiantly has the 3.1.1-0 version. (I just fixed the link to point at the bootloader, firmware and twrp zip.) Are you rebooting to recovery after flashing to make it stick?
MiniBlu said:
Which file are you talking about, I just checked the links and the flashable zip was actually pointing to the full ROM which defiantly has the 3.1.1-0 version. (I just fixed the link to point at the bootloader, firmware and twrp zip.) Are you rebooting to recovery after flashing to make it stick?
Click to expand...
Click to collapse
The PS 1
Yeah doing it right....But it is the same old twrp 3.0.1 mentioned somewhere in the G+ forums....
Never mind ....did you get the port to work
khannz7 said:
Yeah doing it right....But it is the same old twrp 3.0.1 mentioned somewhere in the G+ forums....
Never mind ....did you get the port to work
Click to expand...
Click to collapse
Which ps1 g or zip?
I have just checked. None of the files I have posted are the old version. They are all the newest 3.1.1-0 version.
No not yet.
MiniBlu said:
I have just checked. None of the files I have posted are the old version. They are all the newest 3.1.1-0 version.
No not yet.
Click to expand...
Click to collapse
I have installed the full ps rom with twrp but what I got is not 3.1.1 it is the 3.0.1
+
Maybe I could help you somewhere with the port
I have to remove the sd card and then re-insert it then it received. who can solve it? The battery will charge too long to fill up
khannz7 said:
I have installed the full ps rom with twrp but what I got is not 3.1.1 it is the 3.0.1
Click to expand...
Click to collapse
OK, I'll download it and check, maybe I uploaded from the old folder. Hope not 6.5 hours to upload it.
MiniBlu said:
OK, I'll download it and check, maybe I uploaded from the old folder. Hope not 6.5 hours to upload it.
Click to expand...
Click to collapse
I would love to help you with the port and maybe I could get something new to learn:fingers-crossed:
Phucan2017 said:
I have to remove the sd card and then re-insert it then it received. who can solve it? The battery will charge too long to fill up
Click to expand...
Click to collapse
No one. If you don't like it stick with ColorOs or Lineage.
khannz7 said:
I would love to help you with the port and maybe I could get something new to learn:fingers-crossed:
Click to expand...
Click to collapse
Not just yet, just got to work out the ramdisk changes needed to get ported roms to boot properly with spectrum kernel, then I'll share the info with you and then let the porting begin.
MiniBlu said:
No one. If you don't like it stick with ColorOs or Lineage.
Not just yet, just got to work out the ramdisk changes needed to get ported roms to boot properly with spectrum kernel, then I'll share the info with you and then let the porting begin.
Click to expand...
Click to collapse
Cool
I did that. But for oppo f1 this rom is not finished yet but there are still many bugs. I return coloros
Just used the spectrum zip and worked flawlessly.(from other thread oops) Thanks alot.
How to go back to coloros ? Do i need to flash stock recovery ?
Sent from my F1f using XDA Labs
the_reds2000 said:
How to go back to coloros ? Do i need to flash stock recovery ?
Sent from my F1f using XDA Labs
Click to expand...
Click to collapse
No, Read the OP of this thread. There is a zip (and instructions) to return to ColorOs Bootloader,firmware and TWRP. From there you can flash any TWRP flashable ColourOs based Rom (ColorOs or LineageOS) or restore backups from them.
Which root method will be used for this?

[XT1575] TWRP Recovery Image for Stock MXP 7.0 Nougat NPH25.200-22

Stock Android 7.0 (Nougat) for the Moto X Pure 2015 XT1575 US NPH25.200-22
TWRP Recovery Image (Includes /boot and /system only)
**Factory reset after restore is advised.**
https://drive.google.com/drive/folders/0B2lKWOIH0bTqc29NbVNWWWhsYVE?usp=sharing
**Not tested coming straight from stock 6.0 MPH24.49-18-16.**
I did an incremental OTA upgrade from stock 6.0 MPH24.49-18-8.
Use at your own risk. If you have TWRP installed your warranty is void anyway. I'm not responsible for bricking your device.
worked great for me 18-16 thanks really appropriate the work
Hi
and thx for sharing.
I have unlocked booloader and rooted, can I just flash this one with twrp?
thx in advance
the-light said:
Hi
and thx for sharing.
I have unlocked booloader and rooted, can I just flash this one with twrp?
thx in advance
Click to expand...
Click to collapse
Yes. Root is nonconsequential. You really just need twrp.
Can i just flash it over TruPureX Android 6?
(I guess i can, just want to be sure)
Where can I find Android 7 modem to flash separately?
Will it work with Android 6 modem?
newHere:) said:
Can i just flash it over TruPureX Android 6?
(I guess i can, just want to be sure)
Where can I find Android 7 modem to flash separately?
Will it work with Android 6 modem?
Click to expand...
Click to collapse
No Nougat modem is available until the flashable (non OTA) full stock 7.0 rom is made available from Motorola. This is not likely to happen. No issues have been mentioned running this update on a 6.0 modem. Not sure what the advantages are honestly. I never had problems with bt, wifi, or calls with the 6.0 modem firmware.
Create a backup beforehand and you can always go back to it.
hi i noob, i speak spanish.
I have moto x pure clark xt1575, android 6 no root, i install twrp an unlock bootloader.
I try to install this "ota" room, but fail. i restore back up and now the phone follow work
mphs24.49-18-16.
Need help how instal android 7 official, or only way custom room "lineage 14"
Thanks.
Can I flash this over Lineage OS 14.1 after a full wipe?
acoupleofdroids said:
worked great for me 18-16 thanks really appropriate the work
Click to expand...
Click to collapse
Hi talk about u experience
Greetings, it counts as you did, I have android 6.0 mphs24.49-18-16 and I can not update. Phone with bootloader unlocked and with twrp, no root
I get "invalid ZIP file format" using TWRP 3.1.1-0 on an XT1575. Was running lineageOS 14.1 but I wiped system and data before trying to install the zip. On my laptop I can open the ZIP fine and extract the files, but that doesn't help.
bussemac said:
I get "invalid ZIP file format" using TWRP 3.1.1-0 on an XT1575. Was running lineageOS 14.1 but I wiped system and data before trying to install the zip. On my laptop I can open the ZIP fine and extract the files, but that doesn't help.
Click to expand...
Click to collapse
See this thread :
https://forum.xda-developers.com/moto-x-style/general/guide-xt1575-update-to-nph25-200-22-t3680477
The OP will need to comment - he may be coming from a rooted stock ; at least according the the thread noted above - if you have installed a custom ROM ; there are other steps besides just trying to flash this
I have NOT tried the OP's method or the referenced thread - so I cannot really speak from experience ; just pointing out other resources that have additional information -
Will this work with XT1572? Just confirming.
This is not a traditional TWRP zip file. It is a backup file. You need to unzip it and put it in the backup directory. You then restore backup, choose the nph25-200-22. . . directory, and away you go!
stevejohnson42 said:
See this thread :
https://forum.xda-developers.com/moto-x-style/general/guide-xt1575-update-to-nph25-200-22-t3680477
The OP will need to comment - he may be coming from a rooted stock ; at least according the the thread noted above - if you have installed a custom ROM ; there are other steps besides just trying to flash this
I have NOT tried the OP's method or the referenced thread - so I cannot really speak from experience ; just pointing out other resources that have additional information -
Click to expand...
Click to collapse
kelru2000 said:
This is not a traditional TWRP zip file. It is a backup file. You need to unzip it and put it in the backup directory. You then restore backup, choose the nph25-200-22. . . directory, and away you go!
Click to expand...
Click to collapse
Ah, sure, OK, that makes sense, just wish that had been explained somewhere. I'll give that a shot tonight, thanks!
bussemac said:
Ah, sure, OK, that makes sense, just wish that had been explained somewhere. I'll give that a shot tonight, thanks!
Click to expand...
Click to collapse
Success? Some people have reported bootloops due to a firmware problem. I'd like to know how it went.
ptn107 said:
Success? Some people have reported bootloops due to a firmware problem. I'd like to know how it went.
Click to expand...
Click to collapse
Well it worked, sort of. It booted to stock but it wasn't stable and the play store kept crashing, I tried all the usual stuff for that, clear services & play store data, uninstall updates, finally tried a factory reset and now I'm stuck in TWRP bootloop, even if I reinstall this image.
So very much YMMV.
bussemac said:
Well it worked, sort of. It booted to stock but it wasn't stable and the play store kept crashing, I tried all the usual stuff for that, clear services & play store data, uninstall updates, finally tried a factory reset and now I'm stuck in TWRP bootloop, even if I reinstall this image.
So very much YMMV.
Click to expand...
Click to collapse
Thankfully the 7.0 stock firmware is available now. I wiped and clean flashed it and it works perfectly.
https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
the link is dead
someone can help, sharing a new link? thank you

Safe to updated rooted and unlocked honor 6x on emui 4.1 via ota update?

Title says it all. I have a rooted and unlocked honor 6x on 4.1 and iust got a prompt for an update to 7.0/emui 5.
I've got the Chinese twrp version installed.
ctenc001 said:
Title says it all. I have a rooted and unlocked honor 6x on 4.1 and iust got a prompt for an update to 7.0/emui 5.
I've got the Chinese twrp version installed.
Click to expand...
Click to collapse
its ok you can, but make sure you have Stock recovery installed not the TWRP
ctenc001 said:
Title says it all. I have a rooted and unlocked honor 6x on 4.1 and iust got a prompt for an update to 7.0/emui 5.
I've got the Chinese twrp version installed.
Click to expand...
Click to collapse
Unroot it, flash stock boot.img and stock recovery.img and proceed wit OTA
shashank1320 said:
Unroot it, flash stock boot.img and stock recovery.img and proceed wit OTA
Click to expand...
Click to collapse
Not necessary!
You just have to flash stock recovery!
gaebzn said:
Not necessary!
You just have to flash stock recovery!
Click to expand...
Click to collapse
If you are rooted, it wont boot and go to erecovery with a prompt that your data partition was damaged. You can give it a go
shashank1320 said:
If you are rooted, it wont boot and go to erecovery with a prompt that your data partition was damaged. You can give it a go
Click to expand...
Click to collapse
Wasn't so on my last updates... what are you rooted with? Magisk or supersu?
gaebzn said:
Wasn't so on my last updates... what are you rooted with? Magisk or supersu?
Click to expand...
Click to collapse
It applies to both. SuperSu and Magisk. I am rooted with SuperSU. There is already a thread on Magisk which states for this. And being a SueprSu user for years, I have seen this myself on my BLN-AL10B375 to B379 and BLN-L21C185C360 to BLN-L21C185C365.
shashank1320 said:
It applies to both. SuperSu and Magisk. I am rooted with SuperSU. There is already a thread on Magisk which states for this. And being a SueprSu user for years, I have seen this myself on my BLN-AL10B375 to B379 and BLN-L21C185C360 to BLN-L21C185C365.
Click to expand...
Click to collapse
Just remembered I updated via dload...sorry...my fault...maybe thats why it worked.
But thank you! I will try the b368 with your guide!
I'm a bit ashamed now?
Edit: do you have stock boot.img for b365?
gaebzn said:
Just remembered I updated via dload...sorry...my fault...maybe thats why it worked.
But thank you! I will try the b368 with your guide!
I'm a bit ashamed now?
Edit: do you have stock boot.img for b365?
Click to expand...
Click to collapse
In repository thread you will get on main page or last 2-3 pages. @RedSkull23 has shared it.
Yes, dload replaces stock boot and recovery so that will work.
Been gone through many ups n down with 6X so i know many things now
No need to be ashamed, these are tricky and sometimes hard to remember as we try 10 things at a time
If need b367 then here
https://forum.xda-developers.com/ho...covery-boot-img-request-t3707216/post74649229
shashank1320 said:
In repository thread you will get on main page or last 2-3 pages. @RedSkull23 has shared it.
Yes, dload replaces stock boot and recovery so that will work.
Been gone through many ups n down with 6X so i know many things now
No need to be ashamed, these are tricky and sometimes hard to remember as we try 10 things at a time
If need b367 then here
https://forum.xda-developers.com/ho...covery-boot-img-request-t3707216/post74649229
Click to expand...
Click to collapse
Thank you mate!
shashank1320 said:
In repository thread you will get on main page or last 2-3 pages. @RedSkull23 has shared it.
Yes, dload replaces stock boot and recovery so that will work.
Been gone through many ups n down with 6X so i know many things now
No need to be ashamed, these are tricky and sometimes hard to remember as we try 10 things at a time
If need b367 then here
https://forum.xda-developers.com/ho...covery-boot-img-request-t3707216/post74649229
Click to expand...
Click to collapse
Got a weird problem. If i flash this boot.img for 365 I can't enter my phone. It boots up, i can enter my pin, but the encryption password doesn't work! It's very strange, cause I've never changed it since first setup! Any idea? Or do you have another boot img for b 365? Thanks
gaebzn said:
Got a weird problem. If i flash this boot.img for 365 I can't enter my phone. It boots up, i can enter my pin, but the encryption password doesn't work! It's very strange, cause I've never changed it since first setup! Any idea? Or do you have another boot img for b 365? Thanks
Click to expand...
Click to collapse
My boot.img provided in repository thread is for BLN-L21C432B365 build, as listed in OP and in my post there; what's your build number? An unmatching build could be the cause of this. For example, recovery for BLN-L21C432B365, differs from BLL-L21C130B365 - the B365 at the end is equal, but the build variant is different and so incompatible
RedSkull23 said:
My boot.img provided in repository thread is for BLN-L21C432B365 build, as listed in OP and in my post there; what's your build number? An unmatching build could be the cause of this. For example, recovery for BLN-L21C432B365, differs from BLL-L21C130B365 - the B365 at the end is equal, but the build variant is different and so incompatible
Click to expand...
Click to collapse
My buildnumber is exactly the same. Very strange. Can an installed busybox be responsible for those things?
gaebzn said:
My buildnumber is exactly the same. Very strange. Can an installed busybox be responsible for those things?
Click to expand...
Click to collapse
You may try uninstalling the busybox and then retry to see if it works.

Android 10 Open Beta twrp not asking for password

So I upgraded to android 10 open beta and now viper4android keeps asking to install the drivers and twrp isnt asking for my password so I cant access storage or anything from twrp
I am on twrp 3.3.1-4
Did you try removing the password from your current rom.
Robert235 said:
Did you try removing the password from your current rom.
Click to expand...
Click to collapse
Just tried and still nothing it comes up with swipe to allow modifications and I do that but internal storage is still 0
That's Strange, I remember both on the OnePlus 6 and OnePlus 7 Pro when switching from stock ROM to AOSP having a password used to cause issues with twrp. I wonder if the new version of twrp installer will work.
I wanna try a factory reset but it wont let me
D.Va said:
I am on twrp 3.3.1-4
Click to expand...
Click to collapse
Your on the wrong twrp version.
Flash the latest unofficial twrp.
twinnfamous said:
Your on the wrong twrp version.
Flash the latest unofficial twrp.
Click to expand...
Click to collapse
I would but I can't and I've never had issues with the official twrp builds I personally think it's just the beta causing some weird encryption bug
D.Va said:
I would but I can't and I've never had issues with the official twrp builds I personally think it's just the beta causing some weird encryption bug
Click to expand...
Click to collapse
Why can't you?
The unofficial is maintained by the same person as official.
Also it's not a bug. It's the change in encryption /decryption. So if you won't use unofficial then you can wait patiently for official to update there source and build.
twinnfamous said:
Why can't you?
The unofficial is maintained by the same person as official.
Also it's not a bug. It's the change in encryption /decryption. So if you won't use unofficial then you can wait patiently for official to update there source and build.
Click to expand...
Click to collapse
I can't cause my twrp is showing Internal Storage as 0 and won't mount stuff and I can't wipe
The unofficial twrp comes with a .img file and zip. Use a PC to boot into the .img with fastboot then use that booted image which should allow decryption and flash the zip.
D.Va said:
I can't cause my twrp is showing Internal Storage as 0 and won't mount stuff and I can't wipe
Click to expand...
Click to collapse
Do you have magisk installed?
Use the twrp installer zip.
twinnfamous said:
Your on the wrong twrp version.
Flash the latest unofficial twrp.
Click to expand...
Click to collapse
Solved. NVM, it just popped out as soon as I asked the stupid question.
Can you please tell me where can I find the unofficial twrp? It's like a freaking unicorn, evading my desperate searches.
stefanaroman88 said:
Solved. NVM, it just popped out as soon as I asked the stupid question.
Can you please tell me where can I find the unofficial twrp? It's like a freaking unicorn, evading my desperate searches.
Click to expand...
Click to collapse
Look here. https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322

Is it safe to update OnePlus 6 on Oreo 8.1.0 OxygenOS 5.1.11 directly to android 10?

I had problems on pie so downgraded to Oreo. Now I'd like to update to android 10. Is it safe to go straight from Oreo to android 10? How can I keep root? Will my data be wiped?
Also I tried updating first using twrp but got an error. Can someone explain what happened? I will attach a screenshot
You're posting in the wrong section, and probably using the wrong TWRP. I would use MSM tool in your place, and yes, it will wipe your internal storage, so backup
Floodland said:
You're posting in the wrong section, and probably using the wrong TWRP. I would use MSM tool in your place, and yes, it will wipe your internal storage, so backup
Click to expand...
Click to collapse
Would it be safe to make a nandroid backup with the current twrp version I use? Version 3.2.2-0
Also would it work if I tried to flash an older more compatible version of twrp?
First you have to update to OOS 9.0.9 and then to OOS 10. See the following threads:
https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213 (Instructions)
https://forum.xda-developers.com/oneplus-6/how-to/official-oxygenos-5-1-5-ota-oneplus-6-t3794232 (OOS Full zip downloads)
If you do everything correctly, you will not lose any settings or files on internal storage. But please make backups before continuing.
Also, you posted this in the wrong forum section. Maybe a mod can move it.
Flaxe said:
First you have to update to OOS 9.0.9 and then to OOS 10. See the following threads:
https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213 (Instructions)
https://forum.xda-developers.com/oneplus-6/how-to/official-oxygenos-5-1-5-ota-oneplus-6-t3794232 (OOS Full zip downloads)
If you do everything correctly, you will not lose any settings or files on internal storage. But please make backups before continuing.
Also, you posted this in the wrong forum section. Maybe a mod can move it.
Click to expand...
Click to collapse
So despite the error I got using twrp to flash an update, would it be safe to make a nandroid backup using the same version? Would I be able to restore it if I had to?
OnePlus6is7 said:
So despite the error I got using twrp to flash an update, would it be safe to make a nandroid backup using the same version? Would I be able to restore it if I had to?
Click to expand...
Click to collapse
I assume you got the error because you have an old TWRP version and you tried to flash OOS 10 directly. I don't know for sure if the nandroid will work with a new TWRP version, but I'm guessing it will work (otherwise you can just boot old TWRP and restore nandroid).
It's very difficult to actually brick the OnePlus 6, so even if you would do something wrong and end up in a boot loop, there's probably an easy way to fix it.
If I remember correctly, this is basically what I did:
Uninstall all Magisk modules (but not Magisk itself). Uninstall substratum themes etc, if you use any.
Boot into TWRP. Flash OOS 9.0.9.
Flash new TWRP version (for example twrp-3.3.1-14)
Follow section B from the link I sent earlier.
Flaxe said:
I assume you got the error because you have an old TWRP version and you tried to flash OOS 10 directly. I don't know for sure if the nandroid will work with a new TWRP version, but I'm guessing it will work (otherwise you can just boot old TWRP and restore nandroid).
It's very difficult to actually brick the OnePlus 6, so even if you would do something wrong and end up in a boot loop, there's probably an easy way to fix it.
If I remember correctly, this is basically what I did:
Uninstall all Magisk modules (but not Magisk itself). Uninstall substratum themes etc, if you use any.
Boot into TWRP. Flash OOS 9.0.9.
Flash new TWRP version (for example twrp-3.3.1-14)
Follow section B from the link I sent earlier.
Click to expand...
Click to collapse
Thanks for the help. Just one more thing. I read somewhere it was possible to update twrp through twrp. When I got to install image part, there were some options one of them was supposed to be "recovery image" as far as I remember. But in my version in place of that there was something called vendor image. What does that mean? Can I update twrp by flashing a zip file through the current twrp?
OnePlus6is7 said:
Thanks for the help. Just one more thing. I read somewhere it was possible to update twrp through twrp. When I got to install image part, there were some options one of them was supposed to be "recovery image" as far as I remember. But in my version in place of that there was something called vendor image. What does that mean? Can I update twrp by flashing a zip file through the current twrp?
Click to expand...
Click to collapse
Yes, if you already have TWRP installed, you can install the new zip from your current TWRP. But remember if you had Magisk installed before, to reboot TWRP and flash Magisk again.
I followed what you said. It all worked out. I now have latest twrp, android 10 and root. thank you very much.

Categories

Resources